Closed zosko closed 3 years ago
How are you transmitting the telemetry to your tracker?
I'm using a R9M with ACCST Flex Firmware. It works fine with U360GTS.
I use ACCESS LBT, maybe problem is ACCESS not allow SPort anymore, maybe i can downgrade R9M2019 to ACCST firmware and try it.
Same problem here. I have an R9M Lite Pro and it comes only in ACCESS version. Telemetry not working with that module. As soon I pop in the crossfire, it is working fine. So I guess it is not working with R9M (ACCESS) because FrSky changed some things in the telemetry stream. I would really appreciate if support for ACCESS telemetry would be added.
Also I've found out that this App is able to read my build-in bluetooth telemetry stream: https://github.com/CrazyDude1994/android-taranis-smartport-telemetry?fbclid=IwAR0HFt5bSc1tBTD5SEV3RenQuxW_0wtxeLIOn3rF4jxECHOHBcpcQnxj8Bo
Please log data on 115200 and 460800 and put here.
@zosko any progress on this? That also might help: https://www.rcgroups.com/forums/showpost.php?p=44636915&postcount=1005
@skaman82 no success, but i have made mu own tracker with ground station https://github.com/zosko/iNavTelemetry https://github.com/zosko/R9M_Inav_antenna_tracker
but however, see that code, from RC group i will make a test, seems that will be solution :)
Some new findings: ACCESS Documentation (PXX2 Protocol): ACCESS.protocol.docx
• S.PORT pin is not used anymore for communication. Instead PXX pins are used. Communication speed is 450000 baud (inverted). (at least on my x-lite)
• INTERNAL Bluetooth seems to transfer data differently on my x-lite at 115200 baud - still working fine with https://github.com/CrazyDude1994/android-taranis-smartport-telemetry seems the old protocol - but it is not working with the u360gts unfortunately
I have logged the communication protocols of both (PXX and internal Bluetooth UART). Here are the results: BT-and-PXX.logicdata.zip
About the Internal BT Module - I found a quick DIRTY fix. It seems that CRC has changed. Due to the failed CRC checks in frskyx.c all data is blocked. After commenting this out:
if (!checkSportPacket(packet)){
telemetry_failed_cs++;
//return; < ignore failed crc an go on
}
it seems to work fine. So it needs just an alternative CRC check method. I will raise a separate issue for this.
Is it actually working? I want to build a tracker with R9M2019 Access but I don't know if it get fixed.
Is this tracker working with Taranis X9D+ 2019 and R9M2019 external module ? I have problem to make tracker, i have try ghetto tracker but that not support S.Port. Currently i have issues to get S.Port telemetry from my taranis, because is different from old taranis.
There are working examples with old R9M and old taranis but on new version that is problem i think.
Is any have tested on new taranis and r9m access is it working ?