Originally Posted by
wfield0455
Actually that would be something in the receiver was sending data that the Xicoy telemetry unit didn't understand and as a result handled incorrectly. That is still 100% a Xicoy firmware bug. Jeti uses these interfaces to send telemetry data, firmware upgrades, etc. If a 3rd party vendor designs a device intended to connect to that interface it's 100% on them to understand everything that can be sent across that interface and ensure that it's always handled correctly so that they don't encounter these types of problems.
Actually this particular issue that we found only happening in this particular customer, was tracked to the JetiBox emulator operation, sending to the ecu random keystrokes. The Jetibox is a feature of Jeti radios allow to navigate through the menus of the ecu from the transmitter, it transmits keystrokes from transmitter buttons. The ecu reacted the same as if someone was clicking on the ecu buttons, so a particular keystroke sequence could upset the ecu parameters. We never arrived to know if the TX was sending these keystrokes on its own, or was noise. The Jeti protocol is robust, except the Jetibox buttons, that is a single byte transmission without any protection (CRC, checksum, etc) so the random noise in a particular installation could be randomly interpreted as a keystroke.
As said, seen only once.
Gaspar