Binding JR RG731BX/XG14 with J-log 2.6

[ravegarden]

Hi

Does anyone know how binding should be done when using a J-log 2.6 with telemetry connected to the sensor port a RG731BX receiver?

I have pulled out the red wire between J-log and receiver as per J-log instruction.

If I bind as normal and then after successful binding connect the J-log 2.6 to the receiver then on next power up the receiver believes that a new binding should be done.

Thanks and best regards,
Thomas

[dl7uae]

Hi Thomas!

Has JLog already supply voltage if the receiver is powered up - or at least is getting supply voltage in parallel with the receiver?

I'm asking because voltage-less electronics is unpredictable, its impedance. This receiver seems to think to read LOW on the SENS Port signal pin at power-up.

No idea if your problem is caused by the power-up sequence receiver./.JLog or if the cause is some variation in the hardware of this receiver compared to... XG8 for example.

A pull-up resistor on SENS signal pin, let's say... 10kOhms against + R/C voltage, may help.

[ravegarden]

Thank you Tom!

Providing the J-log with power parallel with the receiver solved the issue

Best regards,
Thomas

[bradg]

Originally Posted by ravegarden

If I bind as normal and then after successful binding connect the J-log 2.6 to the receiver then on next power up the receiver believes that a new binding should be done.

Connecting JLog to receiver with the connector reversed (SIG to GND and GND to SIG) also causes this. I'll save you the time of asking how I know, I did it.

Brad G

[mdu6]

The JLog site seems to indicate that the telemetry interfaces to JR DMSS is not easy and refresh rate etc is slow.

Can someone comment on the current capabilities of the JLoG to JR DMSS telemetry ?

thanks,

[Vinger]

I have no problem with three helis, all Kontronik ESC's. Fly to capacity with alarms set in the TX. All the other parameters read as normal as well, volts, rpm, amperage etc.

[mdu6]

thanks - which DMSS receiver are you using with what FBL unit ?

Also - I see some power-up problem on Jive-Pro/Kosmik JLoG combination that are solved with the use of UltraGuard/Opti - have you encounter this problem (not DMSS related of course)

[dl7uae]

This telemetry is ok so far. Only, transmitter firmwares are slow in following the protocol (sensor) specifications.
Data update rate is rather slow in relation to the bus speed (250kBaud, more than half the speed of I²C) but not slower than most other systems. Example: Graupner/SJ HoTT updates every 200ms per sensor in binary mode (800ms in text mode), 1 second if all five sensors (types) are in use at the same time. JETI's non-bus connection runs at 9.6kBaud only.

JR's uptime time is fix at 160ms, a complete cycle of 16 addresses. Some sensors are polled at variable times of up to 16ms from address to address, so up to 256ms per cycle So far this is not slow but rather slow in relation to bus speed.

Your new question: you speak about the "power-up BEC bug", a design flaw, a typical chicken-or-egg problem. Processor has to control the BEC but its power supply (startup) depends on the output voltage of the BEC. BEC is free running for at least 100ms after power-up, especially the 1st 10ms are critical. Crazy voltage could affect supplied electronics of any kind.
An Opti BEC Guard with its "voltage lockout" (one of many security functions) would be the solution, goes between BEC output and supplied electronics in the model. JLog is supplied from Guard's output then (via its "JIVE port"), the plus wire in the harness KOSMIK/Jpro--JLog has to be cut then.

Just try your luck with your specific copy of such ESC 1st. It can something happen but it does not always.

[Vinger]

RG712BX receivers.