Page 1 of 1

2.6.1 Bug SBUS

Posted: Mon 21. Jan 2019 10:25:07
by radiazione
Hello everyone, I bought a Spirit Pro (here in Italy) and at first connection with my pc, I upgraded it to 2.6.1
I connected an OpentTx via Sbus.
There was a BIG problem : the fbl unit does not see any communication on ch 3.
After 3 days of trials...I tried another sbus tx + rx, same result. Elevator does not move.

I installed 2.6.0 and wow... ch 3 is present now :)

Bad news is that the unit fries tail servo for error in limit travel (that I've not seen,pointing all my attentions at that malefic dead swashplate.

I suggest you to create a repository for previous version of software, I found the old version by luck ...substitute file download name with ....2.6.0 ending letter name eheh


Now I have to resolve why the trex 450 pro has tail out of control but I have setted up normal stabilisation.... :(

bye!

Re: 2.6.1 Bug SBUS

Posted: Mon 21. Jan 2019 10:55:05
by denis747
I have OpenTx using sbus and all my channels work ok on version 2.6.1. Strange that yours isn't!

Sent from my SM-G950F using Tapatalk

Re: 2.6.1 Bug SBUS

Posted: Mon 21. Jan 2019 11:14:00
by ZeXx86
Hello,

I am afraid, but there is no change regarding Channel 3 in 2.6.1.
We can retest it immediately, but there are already thousands pilots flying with the same version without any issue.

Could you reflash back to 2.6.1 to see if the problem reappear?

Re: 2.6.1 Bug SBUS

Posted: Mon 21. Jan 2019 12:44:41
by radiazione
Yes, I have flashed 2.6.1 3 times, with the same results...
I've flashed 1.3 and all was right.
Then I have flashed 2.6.0 and it is ok, but then I have not tried to reflash 2.6.1
I tried Frsky and Flysky tx and rx, strange behaviour...
I can try to reflash 2.6.1

Re: 2.6.1 Bug SBUS

Posted: Wed 23. Jan 2019 0:03:01
by p.i.engineer
Is your throttle channel assigned in the channel menu?

I'm using a r xsr in sbus mode, working great.

Re: 2.6.1 Bug SBUS

Posted: Sun 03. Feb 2019 1:10:26
by helinut
I had similar problems when starting my setup. I found that creating a new model in OpenTX with AETR channel order resolved my problem.