Sensor conflict

[48thFleet]

This may be one of those" if it works, don't complain" questions.
I am setting up my Tandem Xe and I can not get rid of the Sensor Conflict warning in my telemetry settings. I am updated to 1.4.14 and am using ACCST X8R receivers, two, with one set up for telemetry while the other is not. I am using three modules, all FrSky. A GPS and two 40 amp current sensors, FAS40S, each set with it own unique ID #.
All the sensors read out appropriately. The two current sensor read current separately. BUT, I continue to receiver the Sensor Conflict warning. The warning remains even with the GPS disconnected.
In a moment of inspiration, I found that I could shut the warning off in the Settings menu (whew). But the question remains, why does it alarm if the module are all working correctly? BTY, the GPS even gives me Lat/Long in my basement...impressive! Also, I am only scratching the surface(surface ship driver, pun intended), but Ethos is a very impressive system. Better than OTX and Horus.
Thanks

 

[HENNY]

This may be one of those" if it works, don't complain" questions.
I am setting up my Tandem Xe and I can not get rid of the Sensor Conflict warning in my telemetry settings. I am updated to 1.4.14 and am using ACCST X8R receivers, two, with one set up for telemetry while the other is not. I am using three modules, all FrSky. A GPS and two 40 amp current sensors, FAS40S, each set with it own unique ID #.
All the sensors read out appropriately. The two current sensor read current separately. BUT, I continue to receiver the Sensor Conflict warning. The warning remains even with the GPS disconnected.
In a moment of inspiration, I found that I could shut the warning off in the Settings menu (whew). But the question remains, why does it alarm if the module are all working correctly? BTY, the GPS even gives me Lat/Long in my basement...impressive! Also, I am only scratching the surface(surface ship driver, pun intended), but Ethos is a very impressive system. Better than OTX and Horus.
Thanks

If you go to the telemetry page you should be able to see which sensor is creating the conflict. How did you set up the FAS40S to have different unique ID's as this sounds like your issue. If you remove one of the current sensors does the conflict go away.

 

[48thFleet]

I used a FrSky servo channel setter to ensure unique ID's of duplicate sensors, ie the FAS40S. I tried deleting all sensors and re-discovering them. No go. When one FAS40S is removed the alarm goes away. The GPS does not effect the alarm.
On the telemetry page, all sensors indicate different ID's.
It is a little baffling because I have used these on my X9E's running OTX and not had an issue. ( OTX does not ave a sensor conflict alarm so I don't know if it was detecting one.
All that said, all of the sensors operate properly, each FAS40S indicates a separate battery voltage and amp draw( one on each motor). Beyond that I have a GPS with speed, distance and Lat/Long, and all of the "house" sensors.
It is easy enough to shut off the alarm, but this does seem a little like the "no Bind" loop that had been encountered with OTX.
Thanks for your input.