You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I noticed that the utility that I created in powershell to convert the Ethos logs to .gpx format, doesn't work anymore after Beta 3.00. The powershell import function fails to import the csv because there are 2 RX columns.
It appears that there are 2 RX telemetry in Ethos now with the Beta 3.00 TW GR6 receiver telemetry. They seem to get detected as the same name "RX" when you delete all telemetry and then detect new sensors. One is for 'Int 2.4G' and the other is for 'Int Lora' that is shown in the Telemetry screen. In the logs though, You can't tell which is which as they are both named just 'RX'. This also causes some utilities that import Excel (like the powershell csv import function) to not be able to load the CSV file.
Any chance the Lora RX telemetry could be "RX Lora" similar to what was done with the RSSI Lora? This would allow us to distinguish which 'RX' is for Lora and which is for 2.4G and would also stop problems of importing into powershell csv object.
The text was updated successfully, but these errors were encountered:
I noticed that the utility that I created in powershell to convert the Ethos logs to .gpx format, doesn't work anymore after Beta 3.00. The powershell import function fails to import the csv because there are 2 RX columns.
It appears that there are 2 RX telemetry in Ethos now with the Beta 3.00 TW GR6 receiver telemetry. They seem to get detected as the same name "RX" when you delete all telemetry and then detect new sensors. One is for 'Int 2.4G' and the other is for 'Int Lora' that is shown in the Telemetry screen. In the logs though, You can't tell which is which as they are both named just 'RX'. This also causes some utilities that import Excel (like the powershell csv import function) to not be able to load the CSV file.
Any chance the Lora RX telemetry could be "RX Lora" similar to what was done with the RSSI Lora? This would allow us to distinguish which 'RX' is for Lora and which is for 2.4G and would also stop problems of importing into powershell csv object.
The text was updated successfully, but these errors were encountered: