updated for system release 2023.1.0

docs/index.md

@@ -13,19 +13,19 @@ It monitors a DU and RU through periodic health checks and uses the control inte
 
 
 ## 2. Releases
-This document is released together with the system release 2022.4.0. 
+This document is released together with the system release 2023.1.0. 
 This system release contains 
 
 | component    | version                        |
 |--------------|--------------------------------|
-| RIC          | 6.2.0                          |
-| CU CHART     | 5.2.0                          |
-| CU APP       | R3.4.2_ichtegem                |
-| DU           | 2023-02-14-q4-patch-release-01 |
+| RIC          | 6.3.0                          |
+| CU CHART     | 5.3.0                          |
+| CU APP       | R4.1.0_jupiler                 |
+| DU           | 2023-05-08-q1-patch-release-01 |
 | L1           | 8.7.4                          |
-| BNTL650      | 0.5.3                          |
+| BNTL650      | 0.7.0                          |
 | BNTL550      | 0.5.2/0.6.0                    |
-| cell wrapper | 2.0.0                          |
+| cell wrapper | 2.2.0                          |
 | DU/RU        | 5.1.0.30736                    |
 
 ## 3. Dashboard

docs/logs-collection/index.md

@@ -10,7 +10,7 @@ As part of radio related issues debugging. Please run below commands on the radi
 ```bash
 ssh [email protected]
 cat /etc/benetel-rootfs-version
-cat /tmp/radio_status
+cat /tmp/logs/radio_status
 reportRuStatus
 radiocontrol -o G a
 radiocontrol -o D s

docs/modifying-ran650-or-ran550/index.md

@@ -6,11 +6,6 @@ This section is exclusively applicable to the user/customer that intends to use
 
 ### 1.1. Configuring Center Frequency
 
-Take into account that adjusting the center frequency will require applying the change on the RU and on the DU.
-
-- The RU will take the Center Frequency in MHz, both on RX and TX to be witten in the EEPROM
-- The DU will take the center Frequency in MHz, Which will be configured via the Cell Wrapper.
-
 #### 1.1.1. Finding a Proper Frequency
 
 There are several limitations on the Frequencies that can be selected:
@@ -42,47 +37,7 @@ This Frequency, however does not meet the **GSCN Synchronisation requirements**
 
 #### 1.1.2. Applying The Frequency Change
 
-**Apply on the RU:**
-
-- Create a file change_freq.sh with below content in the RU
-```bash
-#!/bin/bash
-
-if [ -z "$1" ]; then
-  echo "Please provide frequency in MHz in with the format XXXX.XXX as an argument"
-  exit 1
-fi
-
-registercontrol -w 0xC036B -x 0x88000088
-eeprog_cp60 -f -x -16 /dev/i2c-0 0x57 -w 0x174:0x01:0x3$(echo $1 | cut -c1)
-eeprog_cp60 -f -x -16 /dev/i2c-0 0x57 -w 0x175:0x01:0x3$(echo $1 | cut -c2)
-eeprog_cp60 -f -x -16 /dev/i2c-0 0x57 -w 0x176:0x01:0x3$(echo $1 | cut -c3)
-eeprog_cp60 -f -x -16 /dev/i2c-0 0x57 -w 0x177:0x01:0x3$(echo $1 | cut -c4)
-eeprog_cp60 -f -x -16 /dev/i2c-0 0x57 -w 0x178:0x01:0x2E
-eeprog_cp60 -f -x -16 /dev/i2c-0 0x57 -w 0x179:0x01:0x3$(echo $1 | cut -c6)
-eeprog_cp60 -f -x -16 /dev/i2c-0 0x57 -w 0x17A:0x01:0x3$(echo $1 | cut -c7)
-eeprog_cp60 -f -x -16 /dev/i2c-0 0x57 -w 0x17B:0x01:0x3$(echo $1 | cut -c8)                    
-eeprog_cp60 -f -x -16 /dev/i2c-0 0x57 -w 0x17C:0x01:0x3$(echo $1 | cut -c1)
-eeprog_cp60 -f -x -16 /dev/i2c-0 0x57 -w 0x17D:0x01:0x3$(echo $1 | cut -c2)
-eeprog_cp60 -f -x -16 /dev/i2c-0 0x57 -w 0x17E:0x01:0x3$(echo $1 | cut -c3)
-eeprog_cp60 -f -x -16 /dev/i2c-0 0x57 -w 0x17F:0x01:0x3$(echo $1 | cut -c4)
-eeprog_cp60 -f -x -16 /dev/i2c-0 0x57 -w 0x180:0x01:0x2E
-eeprog_cp60 -f -x -16 /dev/i2c-0 0x57 -w 0x181:0x01:0x3$(echo $1 | cut -c6)
-eeprog_cp60 -f -x -16 /dev/i2c-0 0x57 -w 0x182:0x01:0x3$(echo $1 | cut -c7)
-eeprog_cp60 -f -x -16 /dev/i2c-0 0x57 -w 0x183:0x01:0x3$(echo $1 | cut -c8)
-registercontrol -w 0xC036B -x 0x88000488
-```
-- For our example where the center frequency required is 3751.68MHz, run the script by:
-```
-./change_freq.sh 3751.680
-```
-- To validate the command is successful run below:
-```bash
-eeprog_cp60 -q -f -16 /dev/i2c-0 0x57 -r 372:8
-```
-
-**Apply on the DU:** (Through the cell wrapper)
-
+(Through the cell wrapper)
 - From the dashboard go to "RAN Overview" then "5G"
 - From the DU/RU list, find the cell to be changed and Click on "configuration".
 - For our example where the center frequency required is 3751.68MHz which is ARFCN 650112. Fill that in the "DL ARFCN" and click submit.
@@ -94,39 +49,9 @@ eeprog_cp60 -q -f -16 /dev/i2c-0 0x57 -r 372:8
 
 ### 1.2. Configuring Cell TX Power
 
-Take into account for an optimum operation, changing the RU Transmission Power require applying a change on the RU and on the DU.
-
-- The RU will take new attenuation values (this will be explained next), both for ANT1 and ANT3 which will be witten in the EEPROM
-- The DU will take the new transmission power into account as well, Which will be configured via the Cell Wrapper.
 By default RAN650 is configured with 35dBm and RAN550 is configured with 25dBm.
 
-**Apply on the RU:**
-
-- To adjust the power of the RU the attenuation settings on the RU would need to be changed: To increase the power the attenuation must be reduced and to decreasing the power, the attenuation must be increased.
-- Important: The the current attenuation values on the RU must be saved as they are unit specific and used to make sure that the unit is transmitting on the needed power. (Please note these are in mdB)
-For ANT1: ```eeprog_cp60 -q -f -16 /dev/i2c-0 0x57 -r 780:5```
-For ANT3: ```eeprog_cp60 -q -f -16 /dev/i2c-0 0x57 -r 1060:5```
-- Assuming as an example the RAN650 unit had for ANT1 16000 anf for ANT3 15730 and we want to reduce the output power by 10dB.
-- Then the new attenuation values for ANT1 and ANT3 must be 26000 and 25730 respectivily.
-- Modify the below script with the last digit of each value and run it on the RU.
-```bash
-registercontrol -w 0xC036B -x 0x88000088
-#ANT1
-eeprog_cp60 -f -x -16 /dev/i2c-0 0x57 -w 0x30C:0x01:0x32
-eeprog_cp60 -f -x -16 /dev/i2c-0 0x57 -w 0x30D:0x01:0x36
-eeprog_cp60 -f -x -16 /dev/i2c-0 0x57 -w 0x30E:0x01:0x30
-eeprog_cp60 -f -x -16 /dev/i2c-0 0x57 -w 0x30F:0x01:0x30
-eeprog_cp60 -f -x -16 /dev/i2c-0 0x57 -w 0x311:0x01:0x30
-#ANT3
-eeprog_cp60 -f -x -16 /dev/i2c-0 0x57 -w 0x424:0x01:0x32
-eeprog_cp60 -f -x -16 /dev/i2c-0 0x57 -w 0x425:0x01:0x35
-eeprog_cp60 -f -x -16 /dev/i2c-0 0x57 -w 0x426:0x01:0x37
-eeprog_cp60 -f -x -16 /dev/i2c-0 0x57 -w 0x427:0x01:0x33
-eeprog_cp60 -f -x -16 /dev/i2c-0 0x57 -w 0x428:0x01:0x30
-registercontrol -w 0xC036B -x 0x88000488
-```
-
-**Apply on the DU:**
+(Through the cell wrapper)
 
 - From the dashboard go to "RAN Overview" then "5G"
 - From the DU/RU list, find the cell to be changed and Click on "configuration".
@@ -150,4 +75,4 @@ Below are some useful checks to confirm the status of the RU after the reboot.
 
 - The RAN650 or RAN550 units usually take from 4~6 mins to boot up after a power cycle. The status of the RU boot up will be printed in a file during boot up. It can be checked by: 
 
-```tail -F /tmp/radio_status```
+```tail -F /tmp/logs/radio_status```

mkdocs.yml

@@ -1,4 +1,4 @@
-site_name: Accelleran 5G O-RAN System - 2022.4.0 release
+site_name: Accelleran 5G O-RAN System - 2023.1.0 release
 
 site_url: https://accelleran.github.io/ran-operation-guide/
 theme: