Hi,
in the ESC telemetry all values are correct shown in FR-Sky ETHOS exept "RBOX C2". This value shows "mAh or Ah" instead of the "BEC Voltage [V]" - provided by ESC Telemetry from Spirit.
Here described: http://manual.spirit-system.com/index.p ... _telemetry
FR-Sky told me that ETHOS is automatically selecting the correct values regarding the sensor data. There is no correction possible by myself like in OpenTX. I would ask you to change this to show automatically the right value and dimension like described in the manual and done in the other telemetry values that are correct.
BR Bernhard
Wrong dimension of telemetry sensor RBOXC2 in FR-Sky ETHOS
It is not technically possible to change the variable type. It is pre-programmed in the Ethos, similarly as OpenTX. It is displayed correctly by Ethos. But used intentionally by Spirit to save bandwidth of the SPort and not to send more than needed variables.
The only solution is to send different telemetry variable. With future updates this shouldnt be a problem, especially when new FPort is much faster.
The only solution is to send different telemetry variable. With future updates this shouldnt be a problem, especially when new FPort is much faster.
Spirit System developer
-
Bernhard.F
- Posts: 41
- Joined: Mon 14. Sep 2020 14:49:54
- Location: Glonn, Bavaria, Germany
Do you plan to implement the F-Port Protocol for the Spirit2 as well in the future? Because my receivers can be changed.
-
Bernhard.F
- Posts: 41
- Joined: Mon 14. Sep 2020 14:49:54
- Location: Glonn, Bavaria, Germany
Hi, there is a new answer from the developers from Ethos in GitHub.
It would be great if you can have a look. It is a similar case where the DIY sensor can not distinguish between the values comming form Spirit2.
https://github.com/FrSkyRC/ETHOS-Feedba ... ssues/1472
You are using the "reserved" Sensor ID from Redundancy boxes
There are no problems mentioned from users regarding compatibility issues
so it seems your sensor does not "emulate" the red.box sensor data in a correct way.
In other words: it's not a problem of ethos.
I would recommend you use "public" and not reserved Sensor ID's
You don't give hints about your sensor, most are based on Arduino HW
would advice to read some of the following links
https://github-wiki-see.page/m/yaapu/Fr ... ocol-specs
https://www.frsky-rc.com/wp-content/upl ... OTOCOL.PDF
https://www.rcgroups.com/forums/showthr ... nfigurable
It would be great if you can have a look. It is a similar case where the DIY sensor can not distinguish between the values comming form Spirit2.
https://github.com/FrSkyRC/ETHOS-Feedba ... ssues/1472
You are using the "reserved" Sensor ID from Redundancy boxes
There are no problems mentioned from users regarding compatibility issues
so it seems your sensor does not "emulate" the red.box sensor data in a correct way.
In other words: it's not a problem of ethos.
I would recommend you use "public" and not reserved Sensor ID's
You don't give hints about your sensor, most are based on Arduino HW
would advice to read some of the following links
https://github-wiki-see.page/m/yaapu/Fr ... ocol-specs
https://www.frsky-rc.com/wp-content/upl ... OTOCOL.PDF
https://www.rcgroups.com/forums/showthr ... nfigurable