Strange Behaviour on T-BEAM

Hi All,

during our experiments we noticed a strange behaviour of our T-Beam board with FW 1.2.23 and python API 1.2.23.

Leaving the t-beam connected to the serial port after some hours the device stops receiving other nodes.

Sometime happens that the data received is not consistent.

As you see in the image the nodes are received in the future.

---- MESHTASTIC INFO OUTPUT ----
pi@raspberrypi:~ $ meshtastic --info
Connected to radio

My info: { “myNodeNum”: 84749992, “hasGps”: true, “numBands”: 10, “firmwareVersion”: “1.2.23”, “rebootCount”: 31, “messageTimeoutMsec”: 300000, “minAppVersion”: 20200, “maxChannels”: 8 }

Nodes in mesh:
{‘num’: 84749992, ‘user’: {‘id’: ‘!050d2ea8’, ‘longName’: ‘TOJNS01_2ea8’, ‘shortName’: ‘TJ1’, ‘macaddr’: ‘PGEFDS6o’, ‘hwModel’: ‘TBEAM’}, ‘position’: {‘latitudeI’: 450749295, ‘longitudeI’: 75214743, ‘altitude’: 358, ‘batteryLevel’: 100, ‘time’: 1617899786, ‘latitude’: 45.074929499999996, ‘longitude’: 7.5214742999999995}, ‘lastHeard’: 1617899786}
{‘num’: 84751072, ‘user’: {‘id’: ‘!050d32e0’, ‘longName’: ‘TOJNS00_32e0’, ‘shortName’: ‘TJ0’, ‘macaddr’: ‘PGEFDTLg’, ‘hwModel’: ‘TBEAM’}, ‘position’: {‘time’: 1617900379, ‘raw’: time: 1617900379 }, ‘lastHeard’: 1617899774, ‘snr’: -6.0}
{‘num’: 84749772, ‘user’: {‘id’: ‘!050d2dcc’, ‘longName’: ‘TOJNS03_2dcc’, ‘shortName’: ‘TJ3’, ‘macaddr’: ‘PGEFDS3M’, ‘hwModel’: ‘TBEAM’}, ‘position’: {‘latitudeI’: 450748154, ‘longitudeI’: 75212801, ‘altitude’: 396, ‘batteryLevel’: 16, ‘time’: 1617844055, ‘latitude’: 45.0748154, ‘longitude’: 7.521280099999999}, ‘lastHeard’: 1617844034, ‘snr’: 11.5}
{‘num’: 3186668756, ‘user’: {‘id’: ‘!bdf0b4d4’, ‘longName’: ‘TOGEU03_b4d4’, ‘shortName’: ‘TG3’, ‘macaddr’: ‘fJ698LTU’, ‘hwModel’: ‘TBEAM’}, ‘position’: {‘latitudeI’: 451376000, ‘longitudeI’: 76368000, ‘altitude’: 260, ‘time’: 1617717324, ‘latitude’: 45.1376, ‘longitude’: 7.6368}, ‘lastHeard’: 1617841244, ‘snr’: -0.25}
{‘num’: 476282860, ‘user’: {‘id’: ‘!1c637fec’, ‘longName’: ‘Andrea 7fec’, ‘shortName’: ‘A7’, ‘macaddr’: ‘EFIcY3/s’, ‘hwModel’: ‘TBEAM’}, ‘position’: {‘latitudeI’: 453840501, ‘longitudeI’: 77107518, ‘altitude’: 357, ‘time’: 1617844039, ‘latitude’: 45.384050099999996, ‘longitude’: 7.7107518}, ‘lastHeard’: 1617844699, ‘snr’: -9.25}
{‘num’: 84685784, ‘user’: {‘id’: ‘!050c33d8’, ‘longName’: ‘Castellamonte 33d8’, ‘shortName’: ‘C3’, ‘macaddr’: ‘PGEFDDPY’, ‘hwModel’: ‘TBEAM’}, ‘position’: {‘latitudeI’: 453840211, ‘longitudeI’: 77108248, ‘altitude’: 346, ‘batteryLevel’: 82, ‘time’: 1617843901, ‘latitude’: 45.3840211, ‘longitude’: 7.710824799999999}, ‘lastHeard’: 1617843997, ‘snr’: -9.75}
{‘num’: 3186666700, ‘user’: {‘id’: ‘!bdf0accc’, ‘longName’: ‘iw1gfv accc’, ‘shortName’: ‘ia’, ‘macaddr’: ‘fJ698KzM’, ‘hwModel’: ‘TBEAM’}, ‘position’: {‘latitudeI’: 453818073, ‘longitudeI’: 77157174, ‘altitude’: 372, ‘batteryLevel’: 92, ‘time’: 1617842501, ‘latitude’: 45.3818073, ‘longitude’: 7.7157174}, ‘lastHeard’: 1617844392, ‘snr’: -6.5}
{‘num’: 2443044956, ‘user’: {‘id’: ‘!919de85c’, ‘longName’: ‘Andrea e85c’, ‘shortName’: ‘Ae’, ‘macaddr’: ‘UAKRnehc’, ‘hwModel’: ‘TLORA_V2_1_1p6’}, ‘position’: {‘batteryLevel’:
22}, ‘lastHeard’: 1617835406, ‘snr’: -6.75}
{‘num’: 86829844, ‘user’: {‘id’: ‘!052ceb14’, ‘longName’: ‘TOKGA01_EB14’, ‘shortName’: ‘TK1’, ‘macaddr’: ‘PGEFLOsU’, ‘hwModel’: ‘HELTEC’}, ‘position’: {‘latitudeI’: 450373000,
‘longitudeI’: 76456000, ‘altitude’: 220, ‘time’: 1617842633, ‘latitude’: 45.037299999999995, ‘longitude’: 7.6456}, ‘lastHeard’: 1617842641, ‘snr’: -8.5}

Preferences: { “positionBroadcastSecs”: 400, “sendOwnerInterval”: 9, “lsSecs”: 2000, “wifiSsid”: “ik1jns”, “wifiPassword”: “0099887766”, “region”: “EU865”, “locationShare”: “LocEnabled”, “gpsUpdateInterval”: 400 }

Channels:
PRIMARY psk=default { “modemConfig”: “Bw125Cr48Sf4096”, “psk”: “AQ==” }


what could be the root cause of this?

Regards

2 Likes