J-Log.eu - Forum

En------
Attachment is my current device circuit diagram, sometimes the S32 blue light flashes continuously after power on, and sbus2 does not return data. Sometimes it works normally after power on, and sometimes it takes 5 to 30 seconds for the sbus2 to work normally after power on. .
However, if the 16SZ transmitter is turned on at the end (after the s32 is turned on), the S32 will be able to operate normally.
In the forum I saw that someone had asked the same question, but there does not seem to be a standard solution.

De----(by Google translate)
Anhang ist mein derzeitiges Geräteschaltplan, manchmal blinkt das blaue S32-Licht nach dem Einschalten weiter und sbus2 gibt keine Daten zurück Manchmal kann der normale Betrieb nach dem Booten und manchmal nach 5 bis 30 Sekunden nach dem Booten nur normal funktionieren .
Wenn jedoch der 16SZ-Sender am Ende eingeschaltet wird (nachdem der s32 eingeschaltet wurde), wird der S32 fast immer funktionieren.
Im Forum habe ich gesehen, dass jemand die gleiche Frage gestellt hat, aber es scheint keine Standardlösung zu geben.

hardware version 3.0.4
firmware bootloader:1.10 app:1.69

video :
https://www.youtube.com/watch?v=Zb-81vl9yBs
https://www.youtube.com/watch?v=QbEWL90h72M

Hi!

Nice, really good translation by Google.

I will answer tomorrow, sorry. Do not recall yet what I answered to the mentioned similar question from another user, and where it was..

_________________
Tom

Hi Tom,

There is another problem.

I added a FUTABA SBS-01T sensor to sbus2 together, and set the SBS-01T start slot at 25 .

It seems that there is a conflict between the two communications, s32 data can not be successfully transmitted back to the transmitter , if SBS-01T is removed during operation, s32 data will resume normal reception.

Hi Alan! Greetings direction island.

Generally:

You have used the default way of setup of S32 with your transmitter, so registered S32 to the transmitter, S32 in the butt of the transmitter?
Ok, please post your setup, - three options:
- a log file (config to be found in the header of the file)
- corresponding screenshot of S32terminal
- or the file export of your config to a file named S32c.pdf (it is no PDF, the extension just to make its use as attachment in a forum simple)

-----

2nd topic first (SBS01T):

This regards to my request for your config. To S32 assigned sensor time slots (Futaba s.bus2) are shown there as well. (Additional question: Which time slot shows your transmitter as assigned to the SBS?)
Futaba never ever explained the (stupid) principles behind s.bus2 and the registration concerning BOTH (OF a sensor, TO the transmitter) to users.
Instead, years ago they started to put some extra confusion on top. Measure: to deliver each Futaba sensor pre-registered (assigned time slot). Manually selectable sensors in a transmitter have the same pre-registration.

So, what can happen (and will happen if you'd connect two pre-registered Futaba sensors of the same type): Time slot collision.

This is option a) for a reason that it does not work with your SBS in parallel to S32. But: time slot collision cannot be the cause if you have registered the SBS to your transmitter as you did with S32.

Option b): You are using an "Futaba S-bus Hub", - and not a simple Y harness to connect both, multi-sensor S32 and SBS, in parallel to the s.bus2

I never had such thing (S.bus Hub) in my hands. https://www.desertaircraft.com.au/shop/futaba-s-bus-hub-w-cable.html
It looks and sounds to me as if that thing is NOT a simple Y harness than active electronics.
So.., what's the difference between s.bus (the hub is for) and s.bus2? Yep, s.bus is unidirectional whereas s.bus2 is bidirectional, - an s.bus plus data from connected slave devices (as sensors) in the opposite direction as to the receiver.
Does a lamp light up? It may be that this s.bus hub acts as repeater / signal amplifier in one direction only, receiver to servos. So no chance to pass sensor signals through.
Please try a simple Y cable.

...Getting too much in a single post, tbc in next one..

_________________
Tom

Now on topic #1:


Quite logical. The only thing what sounds strange to me: The blue LED should not flash (as long as you have not configured/connected a device to S32's "data bus", like a CVS16 for example) than light up constantly.

Two facts to be considered:

#1) The blue LEDs acts as indicator to be in registration protocol, or, more exactly with respect to the data shows behind, s.bus2 protocol not be seen by S32. The registration protocol used by the transmitter is quite different from s.bus2 protocol spoken at the corresponding receiver port. S32 is automaticaly switching between both, tries to determine to which one connected yet. Only, (many things are quite stupid with Futaba's "inventions") in registration protocol the transmitter does not say any word until you hit a button in the registration ("sensor") menu. -- Btw - important to know: You always have to hit twice "register". It's required to let a pause of about a second between both hits. Otherwise the transmitter will not see a sensor responding!
So, the blue LED constantly light up means: "Me, S32, I do not see any s.bus2 traffic, so I assume to be in the butt of a transmitter. To me, S32, it is quite clear that it may be that I'm just hanging in the air with my port 4 set up for s.bus2."

#2) Receiver just powered up. After powerup it had never seen the transmitter it once was bound to. Receiver: "Only, once my transmitter has been seen I start to speak s.bus2 on my corresponding port. Afterwards the transmitter can be switched off but I will continue to talk to s.bus2 in this boot (power) session." So S32's blue LED goes off.

As mentioned, that observed flashing of S32's blue LED (as long as the Rx does not speak on its s.bus2 port) is a bit strange. That simply means that S32 frequently switches between both protocols (registration (Tx) and s.bus2 (Rx)) because sometimes it receives something on its serial line.
...Looks like we have kinda ground loop in the setup.. "Ground loop" means different (non-zero!) voltage level on ground wires (in servo lines) connected to each other - leads to signal voltage offset on the 1-wire line (sig pin at S32 port 4) forming the s.bus2 interface.
This is not really important as long as everything is working once the receiver starts to talk to the s.bus2.

_________________
Tom

Hi Tom
Thanks for your support.

1. I attached the s32 pdf file. thank you.

2. I can set(change) the sensor (time) slot from my transmitter by directly connect the sensor to sbus2 port which on the back side of FUTABA transmitter , so , I set the SBS01T to slot 25 to avoid any conflicts. When S32 and SBS01T put together , my transmitter always receive SBS01T data on slot 25 stably but the data from S32 is "freeze".

2(b). I am very sure the FUTABA sbus hub is only a Y cable inside the box because I have disassemble it before . I attach the photo below.

A bit too late.. I just watched the videos: It seems there IS a wiring problem like a ground loop!

Not only that strange light up of the blue LED than also the data protocol between ESC and S32 gets stuck again and again (green LED).

Hmm.. In my background such a setup is laying around and working all the time. Tribunus 120 (ok. rather oooold firmware, need to make an update), S32, R7008, T14SG.
Blue LED constantly on (no data on s.bus2), green LED constantly flashing (talking to the ESC).

_________________
Tom

Ahh, alternative sensor compilation without "Roxxy ESC". Is the bug still existent in the firmware of a T16 (an other models) - that, although registration of the standard compilation with two times "ESC" works, the transmitter crashes if you select a "Roxxy ESC" display? (My "friend" renamed "ESC" to "Roxxy ESC" and made a bug.. It certainly was not his decision that renaming - than from the marketing. )

Yes, I see, there is no time slot collision with the SBS. (Btw why SBS? There are so many options w/ S32 for several temperature sensors.)

The interior of the hub: Sorry, I can not really recognize anything. You are sure not to have seen any electronics inside of it?

_________________
Tom

Just remembering that I own some Futaba sensors myself. Will try them together with S32.

It only will get hard to find them.. We had to move to another house in autumn 2016 (after 17 yrs on the one before). I'm still living between many boxes in my lab, everything mixed up crazy way (chaos) because I had to continue to work instantly..
(Special problem is the main project I have since summer 2015, leaving "almost" no time for "hobbies" in the RC like JLog. This project is a mobile phone for visually impaired people, mainly blind ones. See the attached video, more intended as kinda fun on a corresponding platform used by the involved developers. The "fun" does not work for them as certainly not for you as well, they do not speak German. https://owncloud.antarus.com/index.php/s/7YxOblfRrViCGMw)
"Gehst Du nicht an's Handy ran, zieh ich Dir die Eier lang." Try your luck w/ google translator again.

_________________
Tom

Still searching for a Futaba sensor here in my lab, turning everything (boxes..) upside down ...
Will give the Tribunus then also an update - and switch to your Futaba sensor compilation with my S32.

Btw, before I continue "my style": Do you use English the "native way" here or by help from Google? I'm asking because the translator does not like complex sentences, not well-proportioned sentences I am known that I like to use them (in both languages).

S32 port 2: I hope the red wire is cut the other end.

_________________
Tom