Possible reason for ONE+ (H) to stop sending data
Posted: Tue Aug 31, 2021 8:10 pm
Hi all,
I have an unit of ONE+ (H model) and installed with the latest version of telelogger from git. I followed the instructions including recompiling the libraries this week, and left it on OBD port of a vehicle - it worked pretty ok for the first few hours, then it just remain "silent" with the following std. output (from teleserver, not from the console of the unit):
What could possibly make the unit stop sending any updates, or could the unit "hang" and requires a "hard reset"? Anyone with experience please help thanks.
I have an unit of ONE+ (H model) and installed with the latest version of telelogger from git. I followed the instructions including recompiling the libraries this week, and left it on OBD port of a vehicle - it worked pretty ok for the first few hours, then it just remain "silent" with the following std. output (from teleserver, not from the console of the unit):
Code: Select all
Reply sent:1#EV=7,RX=82,TX=82*5F
42 bytes from 13.121.10.224| [1] #83 3425 bytes | Samples:0 | Device Tick:3745705
Ping received
Reply sent:1#EV=7,RX=83,TX=83*61
42 bytes from 13.121.10.224 | [1] #84 3467 bytes | Samples:0 | Device Tick:3745705
Ping received
Reply sent:1#EV=7,RX=84,TX=84*63
42 bytes from 13.121.10.224| [1] #85 3509 bytes | Samples:0 | Device Tick:3745705
Ping received
Reply sent:1#EV=7,RX=85,TX=85*65
42 bytes from 13.121.10.224 | [1] #86 3551 bytes | Samples:0 | Device Tick:3745705
Ping received