ZeXx86 wrote:
Just turn your radio on and then check the telemetry screen. Do you see both Channel A and Channel B?
No need to turn the Spirit unit or anything else.
This is hardcoded directly in their protocol to show both always.
Spirit unit has no control over what is being displayed or said.
No, that is incorrect. (In more ways than I'm going to mention here.)
The message format to which you linked tells the flight controller how to send the data. The flight controller should also send the "no data" sentinel value for fields when there is no data for that. For instance, if you have only 1 battery pack, you should send the data for it in the three "_A" fields. If you do not have data for a field, then you must insert the correct value to hide that data or the values you are sending will be displayed.
For this sensor, the "no data" value is 0x7FFF, which if included in all "_B" fields will tell the transmitter to hide that field.
The field which controls whether the B channel is displayed at all is current_B. If current_B == 0x7FFF then the data will be hidden. Anything else and it will be shown.
Quote:
The Spirit unit can only change Capacity/Current data in this where both channels are filled according this structure.
And also there were no changes for years in that area as you can see in the History of this document.
We would be glad to know what we can do differently. As far as is described in their documentation it is not possible for Flight Pack Capacity telemetry page.
Any contact for Spektrum developer would be appreciated.
I would not look at those documents for comprehensive change log information. While the raw format was developed years ago, changes to make specific sensors usable have been occurring throughout the history of the products and are documented more in the transmitter change logs than in these "getting started" documents. These are not comprehensive, detailed specifications detailing all behavior. They will get you started, but you need to actually use the transmitter to see what it will do for each sensor. You may also note that endian is not specified and it varies from sensor to sensor depending on who created the sensor and when, so you actually have to have a transmitter to see how it displays.
I'm glad to hear that you would like to know how you can improve your product to work properly with the transmitters.
Feel free to PM me with questions. We work regularly with BetaFlight, MSH, and other FC developers as well as with turbine ECU vendors and other third-party sensor vendors such as Smoke-EL. If you would like to read more on how the telemetry works, I have numerous posts in the RCGroups "Radios" and "DIY Electronics" forums on the subjects.
Andy
