Originally Posted by Confuzshuz

I have the same PID. I did not need to send it in for the firmware upgrade.

Does your pid match in your serial number?

Originally Posted by indoorheli

Does your pid match in your serial number?

oooh...good call. I just checked and it does not. My serial starts with HC008X.

Looks like the guys might be right about the PID thing.

Originally Posted by tmsn

Today I had three planes lose contact with my DX8 for about 4 seconds while airborne. One using AR7000, one AR6200, one AR8000.....All three have been flown dozens of times before with no issues, all have different power systems, and everything had plenty of charge to go through each session, including the DX8.

I lost contact with my 57" 3DHS Extra (AR6200), but luckily I was high up and level, so it kept gliding until I regained control a few seconds later. Crash-landed a large foamy EDF Jet (AR8000) after I lost control close to the ground, but I regained control just before it was about to crash and managed to send it into a bush for a soft crash with little damage. But I lost control of my Kyosho FW190 (AR7000) while approaching for a landing and caused serious damage to it. Not sure if it is repairable.

Anyone else experiencing something like this with their DX8?

Yes. And others too. I am having a recurring brownout issue. Did you look to see if was a brownout ? or signal loss ? orange or red led's ?

Originally Posted by GoneFusion

Yes. And others too. I am having a recurring brownout issue. Did you look to see if was a brownout ? or signal loss ? orange or red led's ?

Blinking Orange LEDs, all there times... I never had anything like this happen with my DX7...

Originally Posted by Confuzshuz

out of curiosity, are you using airware 2.0?

Nope, just the previous version.

Originally Posted by tmsn

Blinking Orange LEDs, all there times... I never had anything like this happen with my DX7...

Thats not good as its the exact same problem here. Jayrat has same problem too. I know he sent it in but i don't think they have returned it yet ?

I get flashing orange (brownout) too. Tried 4 diff ESC, same problem.

I have narrowed it down to a Rx (AR7600) that faults with DX8 but cannot get it to fault on DX7se. I had the satellite on the AR8000 go once as well but only once and only the sat. Go figure.

I don't know what advice to give you except send it back for them to check.

Andy. Are you guys listening about this issue yet ?

Originally Posted by Confuzshuz

oooh...good call. I just checked and it does not. My serial starts with HC008X.

Looks like the guys might be right about the PID thing.

I think it might be the 009x PID's that were possibly updated to the 011X PID that have the issue.

Originally Posted by tmsn

Today I had three planes lose contact with my DX8 for about 4 seconds while airborne.
Anyone else experiencing something like this with their DX8?

Sounds similar to what has happened with mine, except add in loss of bind as well.

any reports on performance with v2.0? any birds falling from the sky or are they staying up there?

Problem from Eu version, 1.4 flashed 2.0
A flying friend damaged 2 servo's while still on the table!
He was trying out delta mix with flaps,
The servos tried to turn beyond their physical limits, damaged gear.

On a landing approach you just dont want suddenly the flaps messed up!

He also reported strange behaviour of the user menus,
sounds to me like a bad flash.

- Are the servo limits not checked after processing?

- is there a CRC of Hash check of the firmware after flashing to check if flashing went ok?

I am quite reluctance now to buy one yet.
Like M$ have to wait for SP1?

Looks like they have put a lot or resources into DSMX (commerical hit)
and field testing of the opdates itself are a bit lagging..?

Originally Posted by indoorheli

Sounds similar to what has happened with mine, except add in loss of bind as well.

Thats more than four just on this forum with the same fault.....and no fix !
Im getting frustrated to the max.

Originally Posted by jshall755

In case you're in a bind and really need to change the throttle timer threshold value before the next update times out, here is a workaround.

1. Export your model(s) to the SD Card.
2. Open the appropriate .spm file in a text editor. (Use notepad to be safe, other editors often save extra formatting data. You may also want to create a backup copy of the file before editing.)
3. Locate the <Timer> section near the end, then find the Thresh= line below.
4. Change the threshold value. (I'm not sure of the exact scale, but 10% is -819 and 13% is -758. I assume it's related to the -100 to 100 scale on the monitor screen. Take a look at some of your other models' values for references.)
5. Save the file.
6. Select your model from the system menu, then import the model from the card. It will overwrite the currently selected model.
7. Verify the threshold percentage in the Timer menu.

Jay

Thanks Jay, That's much appreciated. I'll give it a go.

Trevor

Originally Posted by K5054

There is a DX10 as well as a DX10t coming ?

Good question!
VP

I'd rather prefer a software update for the DX8 to have 10 channels. Like the Futaba T8FG

I have the HA011X that needs to be returned.

I purchased the DX8 in December and returned it in January because of binding problems.

Is there a trick to binding ?
Cause if there is I can't figure it out.

I thought it was turn on transmitter then turn on reciever.
But sometimes it takes me a few try's to get it to bind.

I try turing on the reciver as soon as I turn on the transmitter.
I try waiting for the transmitter beep then doing it.
I try waiting for the Spectrum logo bars to show then doing it.
I try waiting for it to show the model info and then doing it.

Sometimes I have to repeat the above a few times.
So at the moment I can't tell if there is a trick to it or not.


However once it has connected.
I f I turn off my transmitter and turn it back on again it re-binds almost instantly.