Closed jaycedowell closed 6 months ago
Several other "SERVER_" monitor points are broken as well.
And "BOARD_*_TEMP" is also broken.
It's different now:
240227 16:06:26 60367 57986612 T 213275 1 NDP RPT GLOBAL_TEMP_MAX|
240227 16:06:26 60367 57986612 T 213275 2 NDP RPT GLOBAL_TEMP_MAX|
240227 16:06:33 60367 57993189 T 213275 6 NDP RPT <class 'TypeError'>: must be real number, not dict_values|
BOARD_* seems to work-ish, although it doesn't unpack correctly for some reason:
240227 16:08:51 60367 58131223 T 213279 1 NDP RPT BOARD_1_TEMP_MAX|
240227 16:08:51 60367 58131223 T 213279 2 NDP RPT BOARD_1_TEMP_MAX|
240227 16:08:51 60367 58131352 T 213279 3 NDP RPT B_Z�|
SERVER_* is in a similar boat:
240227 16:10:23 60367 58223721 T 213299 1 NDP RPT SERVER_1_TEMP_MAX|
240227 16:10:23 60367 58223721 T 213299 2 NDP RPT SERVER_1_TEMP_MAX|
240227 16:10:26 60367 58226792 T 213299 3 NDP RPT B�|
Update: They are called BOARD and SERVER*. With the correct names they unpack correctly.*
:tada::
240227 16:29:54 60367 59394915 T 213451 1 NDP RPT GLOBAL_TEMP_MAX|
240227 16:29:54 60367 59394915 T 213451 2 NDP RPT GLOBAL_TEMP_MAX|
240227 16:29:58 60367 59398195 T 213451 3 NDP RPT B�|
I found this in the MCS scheduler log today:
It seems to happen every time "GLOBAL_TEMP_MAX" is polled.