Just to inform for now. See firmwares R66 and 76 in download. Details later. Feel free to try it out, it’s simple to get it running. You need to use JLC 18.104.22.168 or later for configuration of JLog2.
Connect the COM interface of JLog2 to the JR receiver port SENS. Use a Y harness if you have more sensors besides JLog2. The cable needed is the same as for Multiplex, JETI and HoTT telemetry. No need for JSend or any other additional interface. – Do not forget to select “JR” as telemetry type in JLC.
Each sensor type in JR telemetry has a unique address, so each type must be unique on the sensor bus. JLog2 represents three types: TEMP, RPM and POWER (F-PACK). Do not connect sensors of the same type in parallel.
Sensor displays in transmitter’s firmware seems not to be complete yet in terms of available sensor types following the protocol specification which also knows about sub-sensors as in a sensor of type POWER.
Here’s what is available and used by JLog2 yet. SPEED may follow if needed by another JLog2 firmware.
JR’s telemetry in DMSS does not know about alarms by sensors. Alarm thresholds are set in the transmitter only. RPM: Configure the pole count of your motor in JLC. JLog2 gives the motor rpm into the telemetry. Use “OPTICAL” or “MAGNETIC” as rpm sensor type in transmitter’s setup. If you like to see rotor rpm then simply setup for gear ratio in the transmitter. – F-PACK C (mAh): JLog2 sends the cumulated mAh. What you need to setup in the transmitter is a) the nominal capacity of your battery and b) the remaining percentage of the nominal capacity at which the transmitter should generate an alarm. I observed that there is a sligth delay before the alarm appears, for example: Nominal capacity is 2000 mAh and alarm threshold at 20% == 400 mAh. The alarm appears a bit later, around 300 mAh. Keep that in mind for your setup. – As for all other six telemetry systems JLog performs “CAPALARMSTOP”. If throttle<10% here JLog sends 0 mAh to stop the alarm generated by the transmitter. If throttle goes above 10% the real value of the cumulated mAh re-appears.
Because the sub-sensor capability of POWER is not yet supported by transmitters there is no display for Ubec, Ibec, Throttle, PWM and JLog-own sensors available. Ubec is represented by the RX voltage in the telemetry, the receiver as a sensor.
TEMP is tFET, the power FET temperature of the ESC, JIVE or Castle Creations.
My thanks AKmod Switzerland!
Oct-25 2013: Modified CAPALARMSTOP
Every telemetry in JLog performs CAPALARMSTOP. What is CAPALARMSTOP? If throttle goes below 10% (or pwm with a KOSMIK) an active capacity alarm (mAh) will be stopped. So no alarm after landing.
Some telemetry systems, as JR, do not provide that a sensor can send alarms, the terminal (transmitter) generates alarms by itself. JLog needs to know (by config -> JLC) which alarm threshold is set in the transmitter. More exactly: In transmitter you setup the nominal capacity and the alarm threshold on that capacity in percent remaining. Thus, if you set 1000mAh nominal capacity and threshold on 20% in the transmitter, then set the threshold in JLC to 8 (800mAh). – CAPALARMSTOP will stop the alarm now if throttle<10%, 15 seconds stop (the full nominal capacity appears in transmitter’s display, so it stops alarming), 15 seconds alarm (real remaining capacity in display). There is a delay in transmitter between triggering an alarm condition and beep beep, the delay is 10 seconds. Therefore the effective sequence is, if throttle<10% and JLog knows about an active alarm condition by the mAh threshold set in JLC: 15+10=25 seconds pause, 5 seconds alarm (6 beeps).
If you do not want the alarm stop – simply set the mAh threshold in JLC to zero.