LiPo sensor not working when connected to TD SR10

[Richrfl]

I would like to think I am doing something wrong, but I found some issues with the TD SR, and I will go one at a time.
I have this MLVSS, that I was using with the SR10 Pro and SR10 Plus, that does not want to work with the TD SR10. I double-checked the wiring, as in the S series they are using a Molex to a single connector, and followed the RX manual to be sure I did not have the wrong wiring. With that said, one thing that caught my eye was that when I hook up the battery, the LED flashing frequency does not change (like the battery is not connected), but when I use one of the other receivers, with the same or other battery the sensor works normally. Obviously (with the TD SR) the sensor is never detected by the telemetry discovery in the TX.
I did another test. I assigned the S.Port to Pin 10. Now the LED flashing slowed down when I connected the battery, but the telemetry still did not discover the sensor.
Please, if someone has a TD SR and an MLVSS can confirm if it is having the same problem or not?
I wonder if with the addition of internal vario in the TD SR there is not a sensor address issue.

 

[HENNY]

I would like to think I am doing something wrong, but I found some issues with the TD SR, and I will go one at a time.
I have this MLVSS, that I was using with the SR10 Pro and SR10 Plus, that does not want to work with the TD SR10. I double-checked the wiring, as in the S series they are using a Molex to a single connector, and followed the RX manual to be sure I did not have the wrong wiring. With that said, one thing that caught my eye was that when I hook up the battery, the LED flashing frequency does not change (like the battery is not connected), but when I use one of the other receivers, with the same or other battery the sensor works normally. Obviously (with the TD SR) the sensor is never detected by the telemetry discovery in the TX.
I did another test. I assigned the S.Port to Pin 10. Now the LED flashing slowed down when I connected the battery, but the telemetry still did not discover the sensor.
Please, if someone has a TD SR and an MLVSS can confirm if it is having the same problem or not?
I wonder if with the addition of internal vario in the TD SR there is not a sensor address issue.

When you say the RX did not discover the FLVSS, did you go to the Telemetry page and click on discover new sensors. On my Flvs it finds a sensor called "LIPO" if you scrol down the list, you can then use it as voltage sensor. There is also a lua script by a third party called "Zavionix Widget" Google will find it.

I never have any issues with this sensor.

 

[Richrfl]

My device is an MLVSS, and sure enough I enable discovery and went to the last device in the table, where normally will appear a new sensor. I do not think that the Zavionix will find anything at all, given that the transmitter is not talking with the sensor and therefore there is no voltage data. Now, when you are making reference to your FLVSS, do you have it connected to TD SR Rx?

 

[Richrfl]

Tomorrow I will try a different sensor and see what happens. This issue has nothing to do with the transmitter nor the sensor, but with the receiver TD SR, its configuration or anything I am missing.

 

[HENNY]

Tomorrow I will try a different sensor and see what happens. This issue has nothing to do with the transmitter nor the sensor, but with the receiver TD SR, its configuration or anything I am missing.

Can you take a picture of your connection to the sensor and the RX. The two sensors are the same except the older VLFSS is a 6 cell monitoring device and FLVS 8 cell.

 

[Richrfl]

Can you take a picture of your connection to the sensor and the RX. The two sensors are the same except the older VLFSS is a 6 cell monitoring device and FLVS 8 cell.

Here it goes

 

[Richrfl]

Anyways, the problem is not the sensor, as it works with the other RXs. TD SR is the focus of the problem either in the TD SR itself or a configuration I have wrong.

 

[Richrfl]

The problem is that the TD SR 4pin connector does not support S.Port telemetry and a regular port must be configured as S.Port.
Problem solved