Botched acquisition, packets lost /out of sync: bad ack[nack at 'scan' wait] from server
It seems the server/client have gone out of sync. From the latest logs of the server in SCT I get:
2023-10-27 17:25:29,838 Fri Oct 27 17:25:14 2023: 20231027T172519: OK
2023-10-27 17:25:34,517 **** scan ok ****
2023-10-27 17:25:34,517 acquiring...
2023-10-27 17:25:37,661 linearizing...
2023-10-27 17:25:39,344 alpha...
2023-10-27 17:25:39,593 **** meas ****
2023-10-27 17:25:39,594 computing distances...
2023-10-27 17:25:44,970 Fri Oct 27 17:25:29 2023: 20231027T172534: OK
2023-10-27 17:25:49,504 **** scan ok ****
2023-10-27 17:25:49,504 acquiring...
2023-10-27 17:25:59,632 timeout: error 9097
2023-10-27 17:25:59,632 Fri Oct 27 17:25:44 2023: Botched acquisition, 9097 packets lost
2023-10-27 17:25:59,632 **** meas ****
2023-10-27 17:25:59,633 Fri Oct 27 17:25:59 2023: out-of-sync Fri Oct 27 17:25:59 2023:scan message received
2023-10-27 17:26:04,507 **** scan ok ****
2023-10-27 17:26:04,507 acquiring...
2023-10-27 17:26:14,633 timeout: error 9097
...On the FESA I see
...
[ALA??] [ALA$]
[ALA=] [ALA=*]
out of sync: bad ack[nack at 'scan' wait] from server
out of sync: bad ack[nack at 'scan' wait] from serverThis seems to be triggered in the cyclic receive measurements after requesting the laser scan, but tbc.