search

paulmandal / atak-forwarder

Forwards packets to/from ATAK over an off-grid communication layer
MIT License
404 stars 42 forks source link

Watchdog time out. no COT showing up in atak #143

Closed jake19k closed 1 year ago

jake19k commented 1 year ago

Hello,

Names jake new to github. been attempting to get atak-forwarder running on a couple devices.

2 T-beam v1.1 firmware 1.3.45 Mestastic App 1.3.45 Atak 4.7.0.4 latest atak-forwarder for 4.7.0.

first up thanks in advance for taking a look at this.

Meshtastic is working on both devices as I can see and message each of the devices connected to each tbeam. did a couple few hundred meter range tests and sent successful messages in meshtastic back and forth. worked like a charm.

I loaded up atak-forwarder in ATAK configured it following the instructions and s2 undergrounds video on youtube. ensured regions were set in meshtastic and atak, created the channel name and scanned the qr with the other device. ive gotten both nodes to show up when the forwarder icon is touched however no positions show up no points when broadcast do not make it to the other device. Every so often I'll get a atak message that it's discovered the other device but the icon immediately goes grey. Checking the logging in the forwarder plugin window I see a watch dog checking for message status update timeout. Ive used 3 separate numbers matching firmware, meshtastic app, atak forwarder and atak versions with the same result. I am sure im overlooking something but I've stared at the problem from my end for so long I think I've lost some perspective. any assistance i could get would be appreciated

jake19k commented 1 year ago

Refreshed t-beams with 1.2.65 installed 1.2.65 app and everything works now. Interesting that thats specific firmware and app combo I tried. I'm sure I messed something up the first time I did it.