lpgbt_control_lib issueshttps://gitlab.cern.ch/lpgbt/lpgbt_control_lib/-/issues2022-02-03T10:09:12+01:00https://gitlab.cern.ch/lpgbt/lpgbt_control_lib/-/issues/12BERT Timeout to be dynamic2022-02-03T10:09:12+01:00Daniel Hernandez MontesinosBERT Timeout to be dynamicIn [lpGBT line 1310](https://gitlab.cern.ch/lpgbt/lpgbt_control_lib/-/blob/master/lpgbt_control_lib/lpgbt.py#L1310), the timeout is not dynamically set depending on the meas_time based time. This should be changed as for every BER going ...In [lpGBT line 1310](https://gitlab.cern.ch/lpgbt/lpgbt_control_lib/-/blob/master/lpgbt_control_lib/lpgbt.py#L1310), the timeout is not dynamically set depending on the meas_time based time. This should be changed as for every BER going above 32 M clock cycles we exceed the timeout.https://gitlab.cern.ch/lpgbt/lpgbt_control_lib/-/issues/9Unified, machine-digestible status reporting2021-11-09T16:21:57+01:00Stefan BiereigelUnified, machine-digestible status reporting(Request via piGBT)
It would be nice to have a way of getting status results (locked EPRX channels, phase shifter configuration etc) in a machine-digestible form, instead of just the strings the current `*_status` methods return. Also, ...(Request via piGBT)
It would be nice to have a way of getting status results (locked EPRX channels, phase shifter configuration etc) in a machine-digestible form, instead of just the strings the current `*_status` methods return. Also, we should keep a consistent way of obtaining the string representation and the logging wrappers.
Affected methods:
* `log_pusm_status`
* `phase_shifter_status`
* `eprx_group_status`
* `(log_eprx_group_status)`
* `(log_all_eprx_groups)`
* `eptx_group_status`
* `(log_eptx_group_status)`
* `(log_all_eptx_groups)`
* `eclk_status` (log_ counterpart is missing!)
* `gpio_status`
* `(log_gpio)`
* `chip_status`
* `eprx_ec_status`, `eptx_ec_status` currently missing (requested by Nour)