Hi, Trex 600N with Spektrum.

Everything was fine last weekend. Flew about 4 tanks, brought it home, cleaned it, on the shelf. Powered it up tonight to check throttle linkage. Red led on unit lights up, but sats not. unit (obviously) not responding to TX. Tried to rebind without success.

Since then I've tried everything I can think of :
Different sat and cable. I've even did the bind thru an AR8000 and then connected it to the unit.
I've unplugged all the cables except power and USB.
I've do a number of factory resets. I've reloaded both 1.3.0 and 1.3.1 and then the saved banks.
I've done a factory rest and gone through the wizard.
I've tried different models on my TX. Even a brand new model.
Check TX with another heli - Spirit Pro and one with "another" FBL - all is fine.
No response.

How do I get it to bind again please ?

Hi,

can you see if the LED on your satellite blinks when you are connecting the battery?

If it happened on its own, then there may be two possibilities:
a) cable or connection to the unit is wrong
b) satellite forgot its binding data for unknown reason (this should not really happen)

Satellite (if it was bound with some profile in TX) has tu turn LED on always when it is under power.
So unit is not necessary at all for this.

If you bind it for example with AR8000 and then connect it directly to the unit, LED on the satellite must be ON. If not, then it is definitively point a).

_________________
Spirit System developer

Hi,

At power up, I get two slow blinks and then the LED stays solid red.

I've tried different power sources ( 6v regulated, 2s LIPO ) in different ports.
I've tried a number of different sats and cables, working on other helis.
If I bind the sat with the AR8000, it powers up on the Spirit, nut still no TX reaction.

The unit keeps saved settings. If I do a reset and go thru the wizard, or I load saved banks, the values are there after power cycle.

Everything looks normal, except for the sat communication part to the TX.

How to fix please ?

Hi,

if you can see that LED on the satellite stays on, then it is sending data by the cable and you should see response.
If this is not the case as you have said, then cable must be broken or connector in the unit is not holding well.

When you are testing it with AR8000 you have to set Receiver type as PWM, save the settings and restart the unit.
If there is Spektrum satellite directly in the unit, it must be configured to Spektrum DSM2/X. Again, when you are changing receiver type, settings must be saved and unit restarted.

_________________
Spirit System developer

Hi, thanks for the patience and support !

Spirit shows and saves DSMX.
I use the AR8000 to bind the sat to the model on the tx and then connect the sat to the Spirit. At first power up, the sat comes on and stays on, but no TX response.
If I put the bind plug in the PID port and power up, the sat fast blinks. Then do bind in TX. Bind fails, sat goes off. (doing all the quirky DSMX stuff of bind for near, far etc, etc)

4 different sats and cables. Tried to bind to different models in the TX. Tested TX on some of other helis - one is Spirit Pro on the gasser - all good.

Stuck. Help please ?

You are totaly wrong, how you can bind satelite on ar8000 and then you it separately? Are you kidding me? Please read manual again...everything is described step by step.

You havebto bind satelite with spirit, dont use ar8000

_________________
DX9 - Chase 360 - Spirit

Can you please read my initial post carefully and slowly again ?

Daview: You are welcome. I am sure that we will solve it.


If I am not wrong, do you mean as PID port SYS or ELE/PIT/AIL ports?

So with bind plug you can see that the satellite is blinking. Do you use SYS or ELE/PIT/AIL port?

Did you tried to change DSM protocol type and frame rate in your transmitter? For example when you use SYS as a bind port, then it should be configured to DSM2 11ms.

Do you remember when the problem occured for the first time?

_________________
Spirit System developer

Hi, ELE/PIT/AIL port - unplug the gov sensor to get there. It's for DSMX !!

Indeed, I have not tried to bind with DSM2. (bind plug in SYS port and change in the tx) I will try this shortly and report.

Hi, solved, thank you for the efforts and support.

Not sure how / why it went wrong in the first place. couldn't think of anything else to try, so I reverted the software and firmware back to 1.2.0 and it took the bind. Then moved up to 1.3.0 and now it is at 1.3.2.

All seems to be fine. I will go through the settings carefully and also check it without blades first before flying.