Awesome thanks man… I did a impractical range test via a drone with a Tbeam straped to it. I set it to med and sender 30, ill go back and look cause im probably missing something but it only updated location every every 6 mins but sent a message every 30, I asume the advanced setting in the app override whatever sender is default to, if thats how it works. Also is there away i çould have it report elevation too? I brought it up to 1300 feet just for fun but it was anticlimactic.
I can send texts back and forth when the plugin is disabled, so they’re talking, but no CSV is being generated on the receiver after ~30 mins. Both OLEDs seem to be counting up maybe? I see “seq 20” on both at this point.
Note that I didn’t capitalize the commands, this is just how they’re written in the --info output.
I considered backing down to v1.1.x, but then the meshtastic commands fail with “you need newer firmware.”
A quick scan of the docs showed that restarting is not mentioned as a requirement for using the plugin. When I pull together documentation for the main site I’ll make sure to include that step! But if you have time to add it so I don’t forget, let me know!
I swear I unplugged them. But the receiver unit does have a battery installed, so it’s possible it never shut down completely? But it was showing the “seq nn” string, so at least some of the config was working, just no file. Odd.
Hi - just tried out the plugin today on two tbeams running 1.2.28 - worked very nicely. With no special antennas I managed 17km. This is further than I have managed when sending messages - often only 8km (using 1.1.50 and the iOS app). Should there be some reason for this? Or is this just an accident of where I went today and line of sight issues? Incidentally the spreadsheet recorded measurement was in metres - can I make this km? I did wonder if I could set the send rate to say 15 mins and actually show the lat/lon on my receiver OLED - so acting like a beacon from which I could see where the sender was while they were moving? I guess this depends a lot on how long the gps needs for a lock to get an accurate position? Great Plugin - thanks.
hello, i want to test RangeTestPlugin.
I am using T-beam v1.1 and the rev. is 1.2.45
I can’t find the rangetest.csv and the membary can’t change. it keeps 47690 Bytes
I have tried some methods, but not work.
Some tbeams arrive with a strange memory configuration that messes with the range test plugin, try flashing the spiffs firmware file first and then the regular file and the range test plugging should work as expected when configured