PG5 2.1 and PG5 2.2 with S-Bus communication library 2.7.370, why the S-Bus communication on the master PCD stops either after a certain time or after the download of the program?

FAQ #102008

Problem description:
If on the S-Bus FBox ‘SASI S-Bus Master’, ‘SASI S-Bus extended’, ‘SEND’ or ‘RCV’ the communication mode ‘on Event’ or ‘on Sampling time n’ was selected then after the update of the PG5 communication library to the version 2.7.370, the S-Bus communication of the ‘SEND’ or ‘RCV’ FBox stops after a certain time or after the download of the new compiled program and no S-Bus data’s are exchanged anymore to the S-Bus slaves.
This problem occurs on all possible communication channels like RS485 or Ethernet.
The communication works well, if on the above mentioned FBoxes the communication mode was set to ‘On each cycle’ or ‘on data change’.

Detail information about the behavior:
Communication stops after a certain time:
The communication stops after 24 days after a power on of the PCD because the PCD internal millisecond systemcounter which is used for the event transmission has reached his maximum value and will be reseted to the value 0. Due of an error on the FBox library, this situation leads then to the communication failure.

Communication stops after the download of the new compiled program:
The library 2.7.370 internally uses a register which was not used before.
Depending of the value stored in the past in this register it’s possible that the S-Bus communication runs well or stops after the download of the program.

Solution:
Either configure the communication mode in the ‘old’ FBox to ‘On each cycle’ or ‘on data change’ or use the S-Bus communication FBox library 2.7.380 or newer.
The error is fixed in the FBox library 2.7.380, means the ‘event’ or ‘on sampling time’ communication runs well.