Telemetry Input - Also Jeti Bat Voltage
Hello MSH Electronics,
I have a Scorpion Tribunus ESC and a Jeti transmitter. To maximise the telemetry parameters that I can store, the ESC telem goes direct to the Jeti receiver. My transmitter logs both the Ikon sourced and Tribunus sourced telem in the same Jeti log files.
I tried to implement the new "Min V To Go" item in my Ikon 2 BT however it always gives the low voltage alert as the Ikon is not sensing ESC Battery Voltage.
To get the Tribunus ESC to transmit telemetry to Jeti, I need to set the communication protocol of the ESC to "Jeti ex bus".
To get the Ikon to read ESC telemetry I would have to set the communication protocol to “Unsc Telem”.
What I'd like to do is use a Y lead to send the ESC telemetry to both the Jeti transmitter and the Ikon 2 simultaneously so that I can get all the benefits.
Would it be possible for the Ikon to read "Jeti ex bus" telem feeds in the future?
I am running firmware 3.4.000. I realise that it is not the latest but will wait for the identified issues to be resolved before updating.
Attached are config file, events file and recent flight log.
Thanks for considering.
The EX Bus protocol is bidirectional and the UARTs connected to the CH5 or CH6 ports are unidirectional. Therefore, what is asked is not possible.
By connecting the ESC unsc telemetry to the flight controller, which then transmits the telemetry data selectable in Parameter Setting of the DIAGNOSTIC section to the receiver, you can receive all ESC parameters exactly as if you connect the ESC EX Bus telemetry directly to the receiver.
We would therefore like to understand what problems there are with this configuration so that we can find another solution.
Thanks for the prompt reply.
The reason that I went this way is so that I can maximise the telemetry data that I can log. When I used to source the Tribunus data direct into Ikon, then I had less available parameters for other items. I was hoping that it was technically possible as I note that you can accept the "Also Jeti Temperature Sensor Telemetry".
Since we have recently received from Jeti an undocumented "trick" to overcome the limit of 15 telemetric parameters that can be transmitted at the same time, we will do some tests and verifications and if we succeed, when the telemetry of an ESC is selected, in addition to the two/three parameters of the receivers and the 12 parameters selectable in the DIAGNOSTIC Parameter Setting, the telemetric parameters of the selected ESC will also be transmitted.
Would this be a satisfactory thing worth devoting several hours of testing, development and final testing for?
Thanks for the update.
I would really appreciate any enhancements that can be made.