Problems with CRU onu address (LTU calibration)

Dear experts,

I have problems during the TTC-PON network calibration. I took calibration instructions from [https://twiki.cern.ch/twiki/bin/viewauth/ALICE/GettingStartedLtu#Calibration]

I have received some logs during initialization of ATB board by using command “ttcpon fit.net init” :

ilogger: info level set: 20
10-10-19 23:52:44 - ttc_pon - INFO: Start maina.py fit.net init
10-10-19 23:52:44 - ttc_pon - INFO: TtcPonNet init fit.net
ipbuswrap.Init: using STATIC /root/mycfg/alice_cf.xml connection file…
=== ATBoard(atb_24) instance…
OLT1: atb_24 standalone
ONU1: CRU:1
Use x (i.e. ONUx in 1st column) for ONUaddress in CLI…
Si5343x:si5345, opening /afs/cern.ch/user/a/alicetrg/public/git/ctp3-ipbus_latest/boards/cfg/pll_in1_stdalone_c00.hpy…
agrees with PLL
Si5345: config ok, mode: s
olt.config_fine_phase_measurement disabled.
ONUfromctp not present (standalone mode).
OLT1 reset tdomux:emu …
oltreset ok, (1.50 s): waitmask: 0x6 status:0x7
olt setmux: olt1 i2cmainttcmux:1…
olt.setmux 0x74:0x0 …
mux 0x74:0x0 ok.
olt.setmux 0x76:0x10 …
mux 0x76:0x10 ok.
monitor_sfp i2cmainttcmux: 1
10-10-19 23:52:47 - ttc_pon - INFO: ---------------------------------------------------------
10-10-19 23:52:47 - ttc_pon - INFO: Transceiver diagnostic monitoring
10-10-19 23:52:47 - ttc_pon - INFO: SFP digital diagnostic monitoring implemented
10-10-19 23:52:47 - ttc_pon - INFO: SFP internally calibrated diagnostic interface
10-10-19 23:52:47 - ttc_pon - INFO: ---------------------------------------------------------
10-10-19 23:52:47 - ttc_pon - INFO: Vendor Name : GO!FOTON
10-10-19 23:52:47 - ttc_pon - INFO: Vendor Part Number : SOGX6292-PSGB
10-10-19 23:52:47 - ttc_pon - INFO: Vendor Serial Number : 65861181200019
10-10-19 23:52:47 - ttc_pon - INFO: ---------------------------------------------------------
10-10-19 23:52:47 - ttc_pon - INFO: Diagnostic reading:
10-10-19 23:52:47 - ttc_pon - INFO: Temperature : 27.2 degC
10-10-19 23:52:47 - ttc_pon - INFO: VCC : 3.2 V
10-10-19 23:52:47 - ttc_pon - INFO: Tx_bias_cur : 88.4 mA
10-10-19 23:52:47 - ttc_pon - INFO: Tx_Pwr : 5.6 dBm
10-10-19 23:52:47 - ttc_pon - INFO: Rx_Pwr : -40.0 dBm (AVG)
10-10-19 23:52:47 - ttc_pon - INFO: ---------------------------------------------------------
OLT set_tx_phase_aligner(0, 0) done, was: [37, 0.03125]
OLT1 reset tdomux:emu …
oltreset ok, (1.50 s): waitmask: 0x6 status:0x7
OLT get_tx_phase_aligner_status: [100, 0.09375]
OLT set_rx_phase_aligner(0, 0) done, was: [0, 0.09375]
OLT1 reset tdomux:emu …
oltreset ok, (1.50 s): waitmask: 0x6 status:0x7
OLT get_rx_phase_aligner_status: [0, 0.09375]
10-10-19 23:52:50 - ttc_pon - INFO: Finished TTC-PON maina.py

This logs seems to be good.

But after calibration of the ttcpon network by command “ttcpon fit.net fullcal”, I have received some warnings related to CRU onu address:

fullcal for ONUs: [1] in: atb_24_olt_config
oltreset NOT DONE before the start of fullcal
olt setmux: olt1 i2cmainttcmux:1…
olt.setmux 0x74:0x0 …
mux 0x74:0x0 ok.
olt.setmux 0x76:0x10 …
mux 0x76:0x10 ok.
lenonulist: 1
10-10-19 23:54:15 - ttc_pon - INFO: OLT PART NUMBER:SOSO629292-PSGB
10-10-19 23:54:15 - ttc_pon - INFO: OLT trying to detect ONU ADDR 1…
10-10-19 23:54:15 - ttc_pon - WARNING: ONU 1 NOT detected
10-10-19 23:54:15 - ttc_pon - INFO: No ONU was detected, calibration routine will be finished
[olt|onu]_1_atb_24 config files saved.
Clearing sticky bits…
10-10-19 23:54:15 - ttc_pon - WARNING: Error OLT2ONU_RD in onu_errmon_clear(0)
10-10-19 23:54:15 - ttc_pon - WARNING: Error OLT2ONU_RD in onu_phymon_clear
Clearing flags on olt…
ONUs flags not cleared…
10-10-19 23:54:15 - ttc_pon - INFO: Finished TTC-PON maina.py

It seems that ttcpon network doesn’t see CRU onu address, but I have set onuaddress=0x1 in roc-config file. Is this problem on CRU side? What we have to check for solving this issue?

Best Regards,
Artur Furs

Ciao Artur,
which hardware and firmware version are you using?
If you have a PRODUCTION card with an official release of the firmware the PON upstream doesn’t work.
This will be fixed with the next release of the firmware.

Anyway the TRIGGER communication still works fine, so you will be able to receive clock and triggers.
Currently the UPSTREAM is not used, so ignore the error for the time being.

Regards

Dear Filippo,
we are using CRU with FW version: 20190709-123752-43069c64
and LTU ttcpon version is 101

Best Regards,
Artur Furs.