2x TD-MX with HW 1.5 and FW 1.0.12 (In Ethos bound as RX1 and RX2, but also tried RX1 and RX3)
RB25s with FW 20230509
GPS Sensor ADV
Telemetry converter (RDT) for Jetcat ECU´s
What happened:
i got a fully working plane
i then updated the firmware of the internal module from my X20s from 2.2.1 to 2.2.6
after that i got many sensor lost , sensor recovered and sensor conflict warnings
i thought that the reason is that I did not update the TD-MX receivers, too => so I updated the receivers from 1.0.7 and 1.0.9 to the newest 1.0.12 on both
after that the errors were still there
not knowing which firmware is on the RB25s I updated it as well to 20230509
I tried to delete the sensors in Ethos and newly discover them numerous times now, but it does not work.
But I found some interesting things/bugs:
after I unplugged the batteries and all lights from the receivers and sensors went out I STILL got RSSI and the receiver telemetr value which cycled through 0 to 2
when I discovered the sensors in Ethos with everything connected it discovered new sensors "endlessly" (i stopped after about 2 minutes as it got more and more)
As I was curious how that is possible I picked out one sensor that was available multiple times ans checked the IDs:
But it happens with multiple sensors, for example the temperature sensors and the ADCx sensors.
It is really annoying as the plane setup worked flawlessly before the update(s).
Hardware:
What happened:
The problem seems similar to this: https://github.com/FrSkyRC/ETHOS-Feedback-Community/issues/2629
I tried to delete the sensors in Ethos and newly discover them numerous times now, but it does not work.
But I found some interesting things/bugs:
after I unplugged the batteries and all lights from the receivers and sensors went out I STILL got RSSI and the receiver telemetr value which cycled through 0 to 2
when I discovered the sensors in Ethos with everything connected it discovered new sensors "endlessly" (i stopped after about 2 minutes as it got more and more)
As I was curious how that is possible I picked out one sensor that was available multiple times ans checked the IDs:
But it happens with multiple sensors, for example the temperature sensors and the ADCx sensors.
It is really annoying as the plane setup worked flawlessly before the update(s).