Originally Posted by davidmc36

https://www.gravesrc.com/evolution-r...y-adapter.html

Thanks, but I would rather not import from the US.

Originally Posted by sxjack

Has anybody got a design for ... an interface to go between the tacho output on an Rcxel ignition unit and the rpm input on a TM1000?

An opto with a 1k current limiter on the input and the output between signal and ground of the TM1000's rpm input seems to work (it gives me 45 Hz when plugged into a receiver servo output). I put a few hundred ohms in the output circuit, but it is probably not required.

******

Hi sxjack.
Did you get your enquiry resolved?
If not I may be able to give you a hand with it.
I am not far from your location

Originally Posted by ak7466

Did you get your enquiry resolved?

My RPM interface works. A FET, an opto and two resistors.

Hello everyone,
I own a DX8 Gen1(2012) and recently run it with a 4651T SRXL2 receiver.
With the old AR8000 and TM1000 I got the RxV displayed.
With the new 4651T I no longer see RxV.
I have a question regarding the I2C addressing of the RxV. Has this ever changed?
I run the receiver on an openXsensor_RP2040 board, and get all telemetry sensors and the 8 PWM channels that are possible from the transmitter, except RxV.
Best regards,
Torsten

Originally Posted by Satcomix

Hello everyone,
I own a DX8 Gen1(2012) and recently run it with a 4651T SRXL2 receiver.
With the old AR8000 and TM1000 I got the RxV displayed.
With the new 4651T I no longer see RxV.
I have a question regarding the I2C addressing of the RxV. Has this ever changed?
I run the receiver on an openXsensor_RP2040 board, and get all telemetry sensors and the 8 PWM channels that are possible from the transmitter, except RxV.
Best regards,
Torsten

During my SRXL2 tests with a dx18, if I remember well, I have never seen RxV value.
My be a old firmware issue?

Originally Posted by pierrotm777

During my SRXL2 tests with a dx18, if I remember well, I have never seen RxV value.
My be a old firmware issue?

Hello Pierre,
if it was a firmware bug it should not work with AR8000 and TM1000. Just tested again. It must be a different I2C Adress, i think.
With the new 4651T SRXL2 receiver I also get all the possible telemetry data, like Airspeed, Altitude, GPS, Voltage, Current on the DX8 Gen1 that the oXs_RP2040 makes available to me.
Greeting,
Torsten

Originally Posted by Satcomix

I own a DX8 Gen1(2012) and recently run it with a 4651T SRXL2 receiver.
With the old AR8000 and TM1000 I got the RxV displayed.
With the new 4651T I no longer see RxV.

That's because they are different hardware with different intended uses.

The TM1000 has the sensor for bus voltage built into it. It is intended for "dumb" systems to gain telemetry.

The SPM4651T is intended to be used with flight controllers that provide the bus voltage reports to them. If your FC provides the proper data to the receiver, the receiver will happily transfer the data to the transmitter

I have a question regarding the I2C addressing of the RxV. Has this ever changed?

No. However, it is not a standard packet for transmission by itself over RF. Instead, it is separated from the QoS packet inside the transmitter for display.

What packet is your FC using to hand the data to the receiver?

Andy

Originally Posted by AndyKunz

That's because they are different hardware with different intended uses.

The TM1000 has the sensor for bus voltage built into it. It is intended for "dumb" systems to gain telemetry.

The SPM4651T is intended to be used with flight controllers that provide the bus voltage reports to them. If your FC provides the proper data to the receiver, the receiver will happily transfer the data to the transmitter



No. However, it is not a standard packet for transmission by itself over RF. Instead, it is separated from the QoS packet inside the transmitter for display.

What packet is your FC using to hand the data to the receiver?

Andy

Hello Andy,
many thanks for the answer.
I don't use an FC (flight controller) but a sensor board, the openXsensor_on_RP2040 (oXs_RP2040) from MStrens.
With this SRXL2 telemetry sensor board with SBUS support for 16 PWM channels, I can transmit all possible IDs that are mentioned in the spectrum specification.
I am currently receiving Airspeed, Altitude,PowerBox and GPS on my old DX8 Gen1 through this board.
I'll look again at the scripts from the build and if I don't understand something I'll ask you for spectrum specific stuff and MStrens for programming oXs.
Greetings,
Torsten

OK. So you aren't getting RxV back because you aren't populating the message, and this receiver does not have the hardware to measure it itself.

Andy

Originally Posted by AndyKunz

OK. So you aren't getting RxV back because you aren't populating the message, and this receiver does not have the hardware to measure it itself.

Andy

Hello Andy,
it is exactly as you described it. But i could simply add the ID to the frame of oXs (QOS) and then I would have to see RxV as well. We'll see.
Best regards,
Torsten

This is not something that requires any changes on our side.

Andy

Has anyone got any details of the telemetry packets used by Smart Batteries on SRXL2?

I have been doing some inspection and I am seeing the following data from a 3200mAh 3S battery:

42,  0,  0, 1A,  0,  0,  0,  0,  0,  0, 32, 10, 34, 10,  0,  0
42,  0, 10, 1A, 32, 10, 34, 10, 32, 10, FF, FF, FF, FF, FF, FF
42,  0, 80,  0,  0,  0,  0,  0,  0,  0,  0,  0,  0,  0,  0,  0
42,  0, 90,  0,  0,  0,  0,  0,  0,  0,  0,  0,  0,  0,  0,  0

I don't know what line 1 relates to, possibly 0x1032 and 0x1034 are the min and max cell voltages for calculating imbalance. This implies that some of the other overall values may be in here too? It could be that 0x1A is the overall temperature value as that is 26.

Line 2 correlates to the Cell voltages for the 3S, plus 3 sets of 0xFFFF for not present, this leaves a mystery 10 and 1a. I guess that the 0x10 might be a packet selection index?

I believe that the 3rd and 4th lines are likely for more cell voltages? There are certainly 3 columns in the display of cell voltages on the transmitter.

The data on the transmitter at this time was:
Volts: 12.4V
Temp: 27C
Remaining: 100%
Current: 0.0A (This battery seems to report current as consistently 0.0)
Imbalance: 1mV
Cycles: 5
Cell 1: 4.15
Cell 2: 4.15
Cell 3: 4.15

Any thoughts?

We have not published the message format.

Andy