J-Log.eu - Forum

Of course, I have cut the red wire in the other side and I can read English without Google.

Thank you very much.

Ok.

Still no success with my search for a Futaba sensor in my chaos.

At least, after some annoying stress with the usb converter connection, I managed it to update the ESC (06/120). From version 41 to 54.

Result is that I can say: What you experience there (vids) does not happen here.

-----

Please try what happens when you disconnect one of the two ground wires, at port 2 or 4. It must be a ground loop.
It will not make it really better to use only one of two ground lines on apparently different voltage level. But one death have to died. It may "cure" it.
Try with both ground lines, one at a time.

The other thing with the SBS in parallel is a different topic/occasion.
Please try a simple Y harness.

_________________
Tom

OK, I will try it.

Diese Hub ist mWn ein völlig "stumpfsinniger Y-Adapter" - ohne jede Elektronik.

Es wird ja auch nur als "S-Bus Hub" bezeichnet soweit mir bekannt - und nicht als "S-Bus2 Hub"

Ja eben, dass er nur als "S-Bus Hub" (ohne "2") bezeichnet wird, machte ihn mir verdächtig.

_________________
Tom

Hi Tom

I find that:
(1). If SBS-01T is connect together at power on , the S32 "always" (100%) successful to work . But I need to disconnect SBS-01T to recieve S32 data on my T16.
(2). If no SBS-01T at power on , S32 sometimes enter to blue LED blink mode(not work) , at this time ,when I connect the SBS-01T , S32 LED return to normal (work)! but back to (1) issue , I still need to disconnect SBS-01T to recieve S32 data on my T16.

How about disconnecting one of the two ground wires, one at a time?

It IS a ground loop, the observation w/ the SBS proves it.

Where is the "slave" line of the BEC connected to? (ESC with BEC?)
It is no good idea to provide such a 2nd output with ground wire and not to add some words of guidance about the risk itvolved with that. "Slave" BEC output is an invention from Kontronik..
"Slave" should always be connected to the same point as "master", so no signifikant resistance between both GND points. Just pull the "slave" and look what happens.

-----
Telemetry (here s.bus2) and ESC and many other things are entirely parallel, time and event driven processes in S32, so independent of each other.
You can experiment with: Supply S32 through a 3rd port, port 3, just a servo line from port 3 to a point where RC voltage (BEC) comes from.
Now disconnect port 4, reconnect, disconnect... and you can observe the behavior of S32 on hand of the blue LED - provided, the receiver had seen the Tx already, started to serve s.bus2.

The green LED should constantly and with stabil frequency flash, never get lost on the ESC (data).

_________________
Tom

Finally.. I found two Futaba sensors. If you only look into moving boxes, do not trust yourself to make an orderly drop..

TEMP125-F1713 (seems to be defective internally, always -20°C) and VARIO-F1712 (works).
Both in addition to S32 registered to the Tx. TEMP got on slot 14 (did not manage to assigned 25 to it), VARIO on 19-20.

All sensors keep working. No strange behavior when the Rx does not serve s.bus2 already.

I did not recall, saw now again (after yrs): Hey, for what a hub? My Futaba sensors are made for daisy chain, each have a (male) connector at the other end.

_________________
Tom

Hi Tom

I found the bug .
Which slot you set for FUTABA sensor?
If I set the external sbus2 sensor to slot number ( 24 ~ 31 ) , the receiver can not receive S32 data successfully.
Now, I set the FUTABA sensor to slot 19 and they can work together !
In addition, I have try both FUTABA sbus hub and Y cable , the same result.

Great!

Strange that is does not work on a higher slot. Will test w/ my TEMP125, give the logic analyzer something to eat..
I observed something similar strange if TEMP was registered to a free slot in between, "mixed" into slots used by S32. Sensors of S32 registered to slots after the one used for TEMP stopped to update (timeout ----). That did not happen when VARIO got mixed into.
So it looks like the firmware of TEMP is causing a problem. The LA will make us smarter.

Just checked the reg in my Tx: After some experimenting TEMP125 external sensor is currently on slot 19 and VARIO on 20-21. So both after slots S32 is registered to.
It works, only that my TEMP always only delivers data for minimum (-20°C) - but it does that on any slot.

----
..and how about the "LED show" when the Rx is not speaking s.bus2 already (have not seen the Tx yet)? Still there or gone?

_________________
Tom