DSMX Not Binding?

[WildWake]

I've just rebound my Vortex with DSMX satellites a few times.

Here is what you should be doing:

First, if using DSMX satellites then make sure they both really are DSMX, not one DSMX and one DSM2.

When binding select 'DSMX' in the Datapod, then '2 Sats' at which point both satellites should have rapidly flashing lights.

Up to this point the DSX9 should be turned off.

Now turn on the radio with the bind button held down and it should go into bind mode.

The lights on the satellites should both go solid at which point you can release the button on the TX and you should see a message confirming the bind is complete on the Datapod.

In my case the light on one satellite went solid but the other one just went out, I kept the button down on my DX8 until it ended the bind process itself, a moment later the second satellite light came on solid then the Datapod reported the bind as complete.

Thanks for all you help Mark, this is exactly what I was doing, all day,,,
tried different leads, sats... tried the sats on other helis..
by the end of the day half the guys I was flying with could not fly as they had sat missing of there heli's or unbound.. Thanks Guys...

[WildWake]

Did you hold the bind button on the back of the tx then switch the tx on ? If your just pushing the button Ur only reducing the power and not putting it into bind mode.

Yes, held in bind button in before turning on tx... then released when sats were a solid light..

[WildWake]

If I set my DX8 to DSMX 11ms it will not BIND to a DSM2 Reciever, a TX is able to use either DSM2 or DSMX but you still have to select the correct format.

To the Original Poster, try and bind again but hold the antenna an inch away from the receiver.

Only just seen this, will try in a bit, only just got back from the field..

[WildWake]

That isn't correct.

All you are choosing in the radio is your preferred binding options. During the bind process the radio will ask the receiver to bind using those preferences but if the receiver is not capable of that it will tell the transmitter what it can manage and the pair of them negotiate down to what they can both manage.

The options in the radio are important, so you can force the bind to use 22ms even if both RX and TX are capable of 11ms so you can use analogue servos, or you can force DSM2 mode if you want to.

You most certainly do not have to pick the 'correct' mode to match the receiver, that happens automatically.

I just did it myself to check I'd not forgotten how it works

TX set to DSMX/11ms bound to a DSM2 receiver not capable of 11ms and the bind correctly reported DSM2/22ms

Thanks for info, but the JR DSX9 was released before DSMX, with no update facility..

[Andy from Sandy]

Thanks for info, but the JR DSX9 was released before DSMX, with no update facility..

So then

Only just seen this, will try in a bit, only just got back from the field..

You won't be able to do this then

If I set my DX8 to DSMX 11ms it will not BIND to a DSM2 Reciever, a TX is able to use either DSM2 or DSMX but you still have to select the correct format.

Did you read Angelos's post and have you followed the same procedure you did originally at home to get the sats to bind?

[WildWake]

Here is the question... If it bound at home why did you need to rebind at the field? I suspect you that went to fly at the sat was not linking (not going steady red) which is how it all started. If that's the case I would be very interested to see if it works again after you take it home it it gets warm and in drier air. I've seen sats before that didn't work in the cold but were fine indoor after they are left to acclimatise.

-Angelos

I was going to try and talk to you about this, I have noticed that you have been following the post on here as well as the other forums with Great input & guidance.

Last night, I bound the sats, but only one would give a solid light...
servos would move fine and respond as you would expect, then I think it was when I was levelling the swash they started to go intermittent, I could be at bottom stick on the pitch give it full stick and it could take 10 seconds to respond, as If I had not connection..
I did see the post about cold weather, but have not read it yet.
I will give it a couple of hours to get to room temp and try to bind the DSMX's again, the thing is the DSM2's bind in seconds.
I must say I love the Data Pod, it is so easy & clear to see for the size, a fellow flyer had the Gt5 when it came & we both struggled to read it.

[WildWake]

Andy, Re post #20, I was writing post #21 as you posted

[waveydavey]

Same thing today as you Tye, DSMX sats, DX7 Tx and the same worrying trend. In the end I just flew the damned thing and it was fine. I had what I consider to be reduced range on the sats which were fine with both V Bar and BeastX but blinking and then solid, one would drop and the whole radio would go to failsafe. I did think the cold too but I'm yet to be convinced

[WildWake]

Same thing today as you Tye, DSMX sats, DX7 Tx and the same worrying trend. In the end I just flew the damned thing and it was fine. I had what I consider to be reduced range on the sats which were fine with both V Bar and BeastX but blinking and then solid, one would drop and the whole radio would go to failsafe. I did think the cold too but I'm yet to be convinced

Dave, at least its not just me...
Dsm2 sats were spot on... no problem,,,
It was about 2 to 4 degrees at the field today,
I did manage to get it in the air with the DSM2's,
Big mistake...
I turned the gov off in N as I just wanted to get a hover as the light was fading (about 5pm)
did not have any expo set ect, just the basic set up,
I've only just got my "A", & consider myself very very very in experienced, I stopped flying the 600n the beginning of last year when I cot my 500 leccy,
as I was about 3 foot from the ground I hit throttle cut instead of hold, as soon as I released I sent the heli shooting up about 20 foot plus, going all over the place due to no expo,
I hit hold, it came down,,, broken skids and a stiff tail slider.. Blade all good/ no canopy fitted.. how lucky was I??

I have got to say it was very locked in and responsive, just need to tame it/ make it docile..

[Mark_T]

Same thing today as you Tye, DSMX sats, DX7 Tx and the same worrying trend. In the end I just flew the damned thing and it was fine. I had what I consider to be reduced range on the sats which were fine with both V Bar and BeastX but blinking and then solid, one would drop and the whole radio would go to failsafe. I did think the cold too but I'm yet to be convinced

I've just done a few more tests, not sure how much this helps, but I set the DX8 to force DSM2 mode.

Using 2 DSMX satellites I repeated the bind process several times.

Several times I was able to get a situation where 1 satellite was bound properly and the other one was either showing no light at all or was blinking slowly.

After about 10 binds with mixed results it then started binding reliably every time. Not sure why that would be as I kept the radio in the same position for all tests, about 30cm away from the satellites.

During the bind process the general behavior was always the same though in that one satellite would go solid almost immediately, the other one would go out then as the bind process terminated on the DX8, the 2nd satellite would turn on the solid light.

For those having problems, is the Datapod confirming that the bind has been successful even when it hasn't, or is it giving you the 'Do not fly' warning?

[WildWake]

I've just done a few more tests, not sure how much this helps, but I set the DX8 to force DSM2 mode.

Using 2 DSMX satellites I repeated the bind process several times.

Several times I was able to get a situation where 1 satellite was bound properly and the other one was either showing no light at all or was blinking slowly.

After about 10 binds with mixed results it then started binding reliably every time. Not sure why that would be as I kept the radio in the same position for all tests, about 30cm away from the satellites.

During the bind process the general behavior was always the same though in that one satellite would go solid almost immediately, the other one would go out then as the bind process terminated on the DX8, the 2nd satellite would turn on the solid light.

For those having problems, is the Datapod confirming that the bind has been successful even when it hasn't, or is it giving you the 'Do not fly' warning?

Thanks Mark, I'm just starting try a few ideas, I'll try what you have done & let you know the results.

[Mark_T]

... forgot to mention, all tests conducted in the warmth and comfort of my work room ...

[waveydavey]

Thats what we were seeing today Mark, either one would connect and go solid the other would either blink or do nothing. When rebinding sometimes it would bind no problem other times it would take ages and either sat would go solid first with the other one following. Sometimes it would link immediately sometimes a minute or so would pass with only one binding, it would then hop from one to the other with every time it done it the VX1 would flash red as if the link had been lost. I had the failsafe on the throttle set to 0 so I would constantly get the throttle jumping as the bind was lost. It flew fine though

[Mark_T]

Hmm... I'm sure Angelos will get to the bottom of this quickly enough, but I may be tempted to switch to my 8FG until it is sorted though

Also, in fairness, I've not noticed the same problem when using the DX8 in DSMX mode so perhaps I'll go do a few more bins and see what happens ...

[KevDavies]

surely this is an advert for futaba?? As much as I used to love my DX7 im going off them very quick! I can see a 8fg coming my way soon!