BSAP Ethernet Time Sync Error Messages

No Valid Time Sync IP Address

To use Ethernet BSAP time sync, on the Ethernet tab of the BSAP Protocol object, one or the other of the Time Sync IP Address 1 or Time Sync IP Address 2 fields must be set to the IP address of the host computer on which ACM is running. If neither of these fields is set to the correct IP address, the message to write the new time to the device will not be sent, and you will see this error message:

2020/10/07 15:15:58.256,Error,asiBSAP.197,BSAP Durango,*** No valid Time Synch IP Address is configured.

Ack MEX or SEQ Mismatch

Many Ethernet BSAP devices have a bug that makes them set the MEX and/or sequence number to the wrong value in Time Synch Ack messages.

This will be logged as an error by ACM:

2017/09/25 08:08:43.590,Error,asiBSAP,BSAP Durango,Time Synch Ack MEX mismatch: expected 12, received 77.

2017/09/25 08:08:43.590,Error,asiBSAP,BSAP Durango,Time Synch Ack SEQ mismatch: expected 3, received 16707.

Since this usually doesn't mean that the Time Sync messages failed, our driver doesn't retry them. However, if the Time Sync message does fail, this can't be determined from the Time Synch Ack. If the Time Sync message succeeds, a few seconds later you should see the BSAP device exchanging handshaking messages with the time sync thread, like this:

2017/09/25 08:08:43.964,Info,asiBSAP,TimeSynchThread,[192.168.1.22:1235] R: 01 00 0C 00 00 00 1E 3A 00 00 AC 72 00 00 F0 C0 03 00 74 FD 0B 90 4C F7 06 10 24 9D 05 10

2017/09/25 08:08:43.964,Info,asiBSAP,TimeSynchThread,[192.168.1.22:1235] RTU Time is: 2017-09-25 08:09:16

2017/09/25 08:08:43.964,Info,asiBSAP,TimeSynchThread,[192.168.1.22:1235] Host Time is: 2017-09-25 08:08:43

2017/09/25 08:08:43.964,Info,asiBSAP,TimeSynchThread,[192.168.1.22:1235] S: 01 00 0C 00 00 00 1E 3A 00 00 AC 72 00 00 F0 C0 03 00 74 FD 0B 90 4C F7 06 10 24 9D 05 10 02 00 0C 00 00 00 1E 3A 00 00 AC 72 00 00 F0 C0 03 00 1E 3A 00 00 8B 72 00 00 E0 9C 41 00

Log Viewer Filtering

If you're using the Log Viewer filter to display only messages being logged by a particular BSAP device, you will not see the time sync thread handshaking messages. Because multiple devices may use the time sync port, and the handshaking messages don't contain a device address, there's no way to log these messages with the device name.

Troubleshooting Failed Time Sync Messages

If you don't see the Time Sync thread handshaking messages, first check that the settings in the BSAP device and in ACM are configured as described in BSAP Ethernet Time Synchronization.

Another possible problem is that some BSAP device ports can't accept Time Sync messages or can be programmed to reject them. To fix this, either connect to a different port on the device or reprogram the port being used to accept Time Sync messages.

These ControlWave system variables, if set to TRUE, will cause the Time Sync message to be ignored:

@GV._TS_INHIB
@GV._NHP_IGNORE_TS

These ControlWave system variables, if set to TRUE, will cause the Time Sync message to be ignored on the specified port (P1, P2, P3, etc.):

@GV._P1_TS_DIS
@GV._P2_TS_DIS
@GV._P3_TS_DIS etc.