Closed dave032285 closed 3 years ago
This issue has been mentioned on Meshtastic. There might be relevant details there:
https://meshtastic.discourse.group/t/new-plugin-rangetestplugin/2591/66
Its actually a feature request. Did i post in the worng place?
On Tue, Mar 23, 2021, 11:53 PM Kevin Hester @.***> wrote:
This issue has been mentioned on Meshtastic. There might be relevant details there:
https://meshtastic.discourse.group/t/new-plugin-rangetestplugin/2591/66
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/meshtastic/Meshtastic-device/issues/758#issuecomment-805494577, or unsubscribe https://github.com/notifications/unsubscribe-auth/AD43APTZGPPUUZO27KWCVXLTFFV5PANCNFSM4ZWQDFHQ .
@dave032285 no worries - that message wasn't really from me - it was just a bot and a side effect of your forum post linking here ;-)
This is done.
Elevation and SNR fields (or headers) are backwards in the CSV
Elevation and SNR fields (or headers) are backwards in the CSV
Thank you. I opened a bug for this.
Reporting elevation during the range test would be sweet. I guess it would be practical use for someone setting up on a mountain or something, personally im mounting meshtastic devices to my drones for impractical range testing. Maybe not impractical. But not real world testing. Unless it was for an emergency of some sort. Youd have an idea of how high you need to be to reach specific areas,
Please - if you just have a question (i.e. not a bug report or a feature proposal), post in our forum instead.
Describe the bug A clear and concise description of what the bug is.
To Reproduce Steps to reproduce the behavior:
Expected behavior A clear and concise description of what you expected to happen.
Screenshots If applicable, add screenshots to help explain your problem.
Device info:
Smartphone information (if relevant):
Additional context Add any other context about the problem here.