jLog GW & Jive & HoTTv4

[TomasN]

According documentation Jive should report I-BEC but I can't find it in logged data from telemetry (jLog as GAM, tx Graupner MZ-18). Do I something wrong or I-BEC is not available with HoTT telemetry?

[dl7uae]

doc
We have no Ibec in the pseudo graphical displays of "GAM" or "ESC" by JLog, only in text display (mode):



We must economize with the displays. I thought Ibec were here not so important compared to other values.

Both, Imot and Ibec are very unsteady, hard to observe in a numeric display.
Only max values will be of "online interest":



Purchase a logging (FULL) enabling key and enjoy the wobbly things afterwards.

[TomasN]

I'm using logging capability of my transmitter so paying another 60EUR for I-BEC logging (and maybe higher value samplerate) is quite expensive for me. I'm not interesting in "online viewing" of this parameters but logging it by trasmitter. I hoped that I-BEC is reported as some "Hott variable" similar as PWM is reported as "height" and throttle as "climb". It appears that there are some "free" variables of HoTT protocol which can be used for this purpose. I assume that I-BEC from "text HoTT mode" can't be logged by transmitter and also text mode is slower than binary...

[dl7uae]

I know that you all are on the trip of saving money.

I feel w/ you (that's a lie ), just give me the ID of your device (found in version.txt, 2nd line) and R2 will be happy to help protect your account.

Logging in a transmitter is not a substitute:
- We intentionally give integrated values into displays (for the human eye) whereas data for logging should not be integrated.
- There is more "derived data" in JLog's log (max values, alarms, power etc)
- Data repetition frequency is lower than w/ local logging.
- Transmission errors can appear which are not eliminated.
- Log viewing: It depends too much on the radio brand, not interchangeable between users of different radio systems.