S32 and T18SZ not registering sensors anymore

[MrEmail]

Send you a PM because its getting really specific and with too much noise which isn't pleasant in the forum so after we have done a breakdown analyses we can put the solution here

[dl7uae]

Ok, but nothing yet.

[MrEmail]

Originally Posted by dl7uae

Ok, but nothing yet.

Hmm will check again. I thought I send it.

Verstuurd vanaf mijn SM-G928F met Tapatalk

[dl7uae]

Checked again: Nothing received.

You could use my email alternatively, found in the imprint of j-log.eu

To avoid wear of our fingers we can also make a call. I'm "dl7uae" in skype. Because this is my Ham call-sign nobody else should use this nick.

[MrEmail]

Send you an email but I have to say I was tired and didn't want to mail last night also pending skype :-)

[dl7uae]

All's well that ends well. For onlookers.

It turned out that there must be some damage at the "sig" pin of port 4. (special signal inverting chip behind for Futaba s.bus2 or FrSky s.port)

It can read - but apparently sometimes not.
It could also be that an output signal is sometimes not readable to a connected peer (transmitter at registering, receiver).

Emil got a "unit #2" that works, of course.
"Unit #1" what caused our confusing discussion here, stays for every other use case except of Futaba s.bus2 (or FrSky s.port) because of the suspected "half-damage" of port 4.

Shit happens..

[MrEmail]

I have to say I got excellent support from you Thomas and that is an understatement. The second unit works perfectly and this weekend it already has flown giving me perfect telemetry results.

Sent from my AOSP on Manta using Tapatalk