DX7 probs

[joehelicopter]

1.The TX sometimes boots up with a blank screen
2.The TX somtimes boots up with an inverted display
3.The AR6100 rx is glitching badly on the throttle/collective stick
4.The AR7000 rx needs to be bound too often
5.The lil' chikkin doody antennas suck cause they break off :arggg:
I hope Horizon is going to do something about the antennas-they look like unprofessional CRAP...as for the other probs I'll post when I get it back from the repair shop.....never crashed but the throttle/collective stuff will scare the Holy Reebus outta ya :alcohol
JoeHelicopter

[LITHIUMSTATIC]

Send it in to be repaired or replaced.

[DavidH]

Send it in to be repaired or replaced.




...as for the other probs I'll post when I get it back from the repair



Seems he has already sent it in

[joehelicopter]

Update!!! :banana
Got the Dx7,AR6100,and AR7000 back last Eve..
The repair notes said the 6100 was updated to v-2 firmware-there is now a sticker on it.
the AR7000 antennae were re-soldered..Gratis--Thanks Horizon.All under warranty.
I plan on flying a couple packs in the CP PRO this AM so I will post again and let you Guys know if there are any issues. :smokin:

[joehelicopter]

OHHH BOYYYY do we have problems :arggg: :BSS
The AR6100 rx is completely unflyable--my CPPRO chased me across my warehouse ......very dagerous...
I am going to tryt theAR7000 next in the CPPRO-
Hey my Bothers this is really sucking :soapbox I have been flying this radio with no probs since December-now it's scaring me-so I will post again after trying the AR7000
:arggg:

[joehelicopter]

Once again-the CP is unflyable with the AR7000......very scary dangerous....
this is :BSS I clearly described the problem to Spektrum's repair dept---I'm screwed-I am getting massive glitches on the collective and glitches to the collective if I input a down elev/ff input-same prob on both recievers---DUH :dontknow You think they checked the tx?Sounds like I got an update without a thorough chek of the problem I described... :FThat I asked for the system to be checked.If I had been flying my TREX600,I am sure I would have gotten hit...I am calling Spektrum Immediately...
Is anyone else experiencing this collective glitch???? :arggg:

[joehelicopter]

OK>>>>>>>>>>
Just talked to horizon.
They think the problem is the stock 3in1 unit.
They are sending a free replacement tomorrow.
Nice guys on the phone and seem interested in helping so A+ there.
I just hope I'm on the right track with the problem :alcohol :motz cause I gotta fly...... :fly

[Filby]

Can you explain a bit more? So this had nothing to do with the Tx or receivers?

[LITHIUMSTATIC]

The 3-1 on those Blade CP's can malfunction. I've had to run from it about twice. Bought a new 3-1 and all was well.

[Filby]

So this whole thread about the DX7 and the AR7000 and the AR6100 being stuffed is completely crap? Maybe the title should be changed: Blade CP probs. Because my first impression was that the DX7 has some catastrophic problems!

[joehelicopter]

Well I thought the symptoms were related to my early non upgraded AR6100-then I had the same probs with the AR7000-so when I get a new 3 in 1 I will let you know if the problem is solved.
The probs really resembled a radio interference issue that I have had with 72 mhz stuff in the past :...:

[DavidH]

So this whole thread about the DX7 and the AR7000 and the AR6100 being stuffed is completely crap?



1.The TX sometimes boots up with a blank screen
2.The TX somtimes boots up with an inverted display



With those two things happening, I would surely think it was a radio problem when other things started happeing. They may not be catastrophic problems, but just those two would make me suspect it is radio with anything else that was going on.

David

[rstacy]

1.The TX sometimes boots up with a blank screen
2.The TX somtimes boots up with an inverted display
3.The AR6100 rx is glitching badly on the throttle/collective stick
4.The AR7000 rx needs to be bound too often
5.The lil' chikkin doody antennas suck cause they break off :arggg:


1&2 are not related to 3&4
I have had 1&2 happen. No big deal. Just cycle the power switch.

The AR6100 rx is completely unflyable
Once again-the CP is unflyable with the AR7000

And that is how you know it isn't the receivers. Most likely not the DX7 system at all. I suppose the 3 in 1 is as good a place as any to start.

A friend of mine was getting hit on his Spectrum Rex. It certainly looked to be radio hits. Ill jump to the end of the story where he finally found that the Hitec servos were causing the hits. Replace all 3 servos with 281s and it never hiccuped again.

[joehelicopter]

Yes-It appears the 3 in 1 is "spiking"under load and since I had issues with the Tx screen I was worried that the probs were Tx related-as both recievers were affected,but the 3 in 1 was still driving the tail motor very well-also ,all the gyro and servo wires provide a loop in the electrical system so a component going bad has multiple paths to distribute the spikes---it's been "trial by error" all the way with the CPPRO$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$ :hammer

[DavidH]

I had issues with the Tx screen I was worried that the probs were Tx related-as both recievers were affected,but the 3 in 1 was still driving the tail motor very well-also ,all the gyro and servo wires provide a loop in the electrical system so a component going bad has multiple paths to distribute the spikes---it's been "trial by error" all the way with the CPPRO

I would say 90% of the pilots would also think it was transmitter or receiver related if there is any problem of any kind with the transmitter. I know with 20 years of doing this, that would have been my first thought.

David

[GMRO]

All the problems I see listed here are not all related to the same causes.

Agreed Ray, all it takes is 1 bad servo or cheaper quality ESC and you can induce issues. RF link is solid but the Spektrum RX's do not act as filters. You are seeing servos and ESC's act up all on their own which spike other components. This signal is not a glitch in the RF link or coming from the TX and RX. This is not the radios fault. I've see 450 size helis shut off, that is loose power to the main motor only, as the pilot landed. All servos worked and the auto or hard landing was totally controlled. Else if in failsafe or lock out you would not have been able to land. I’ve see this a few times at my indoor flying field. It was traced back to the ESC brand having an issue with static re-boots and it would shut off the main power output side to the motor while leaving the BEC side still powering the RX. Good as the pilot landed. We duplicated this a few times. Go to ID UP and fly around and without warning or else the heli would just loose motor power. Heli was landed as all the other servos worked. ESC was dead until the RX power was cycled and the ESC re-booted per its normal sequence. This was not a thermal issue on the ESC just a static hit that shut it off. This was while indoors in a humid arena. Took the same heli outside and it did not shut off. Back inside and vio-la it did it again. ESC caused it.

If your DX7 AR7000 RX is requiring re-binding you have a different problem. Per the GUID design the RX does not lose the bind to TX. It is an impossible feat. HOWEVER, if a pilot somehow accidentally pressed the BIND button on the back of the TX the TX looses the RX's info in that model memory. This means you have to re-bind the RX to the TX so the TX and RX GUID are re-established and made part of the model memory info the TX stores. All it takes is a bump of sorts of the BIND button while you turn on the TX for this to happen. No issue if the TX is on and you accidentally press the BIND button as this scenario is for range testing. GUID is not lost at this point. You still don’t want to do that if you are flying since your TX’s output signal is lower and you could lose link with the model as the range is being CUT by a lot. So if you use a TX tray and or let your buddy hold your TX to check it out or set your TX on a flat table and the BIND button gets pressed at the same time you turn-on the TX for just a moment BIND is lost. Don't blame the RX for losing the bind on its own; this is NOT what is occurring.

I've never had to re-bind my Spektrum RX's to my DX7 once. Unless I wanted to change the failsafe servo positions or move a model to a different memory location in the TX. And I only did this once or twice. Past that all my models work and experience NO BIND loss issue.

Added info: This would be the same with Spektrum brand modules too. If you accidentally pressed the BIND button on it while turning on the TX without the RX BIND plug in place you will lose the GUID info too. As a result is appears as the RX lost the bind. Again this is not what is occurring it is being erased as the system was put into the BIND sequence by an accidental pressing of the BIND button.

If you don't think it can happen try it on the bench.

I hope this helps.

[joehelicopter]

To that I say that Spektrum has made note of bad bind switches in the TX....
I have been an RCer since 1970....started with Helis in 1973...
I suffer not from a lack of experience :Bang
but I am suffering for a lack of reliable components-
:arggg: AND BY THE WAY!!Spektrum needs to move that Bind switch to the front of the transmitter-with a cover over it when not in use!It is a HUGE safety issue if you think about it.I have my Tx Tray cut out so the switch can't be depressed :smokin:

[Skiddz]

My experiences with the DX7 thus far have been - for lack of a more PG-rated term - disappointing and unsafe.

See my thread in the 2.4g forum regarding the 401/dx7/ar6100 setup and my thread in the main forum entitled "Dilemma".

[joehelicopter]

OK,I think I have tracked the problem down...
The E Flite ESC for the brushless 370 motor seems to be the Culprit!
I am sending all the electronic components from the CP PRO to horizon today.I noticed this weekend that both of my programable esc will not accept programming anymore so I think the problem is there! :smokin:

[Skiddz]

You trying to program with a linear throttle curve? Anything other than linear won't work for programming.

[Jermo]

I fly two T-Rex450SE's. One with the AR7000 and the other with an AR6000. I've never had to rebind either and I've never experienced a glitch with the TX. There IS a verified software issue with the AR6100. You can send it in for a software update.

If you're having ongoing issues with your TX coming on in odd modes and/or having to re-bind I'd definately send it all in for repair. I realize it's a pain but you really need reliablity and these systems are typically very stable.

[DavidH]

There IS a verified software issue with the AR6100. You can send it in for a software update.




Got the Dx7,AR6100,and AR7000 back last Eve..
The repair notes said the 6100 was updated to v-2 firmware-there is now a sticker on it.

[ChasHeliCop]

I started out with a CP Pro..... come to find out, my 3n1 unit was bad the entire time right out of the box, I learned to fly with it chasing me around the yard. Horizon replaced it, but I already bought my Trex :mrgreen: Another thing, put some shrink wrap around the base of the antenna on the DX rx, and see my gallery for windshield washer tubing around the antenna to keep it off the CF, I was getting glitches before I did that. Fuel line would work too.

[joehelicopter]

OK!!!!!!!!!! :banana I just got all new servos-a new esc-a new 3in1-reassembled and test flown this AM.
EVERYTHING IS WORKING GREAT :clappp :smokin:
NOOOOO GLITCHES :smokin:
So I tracked the problem to the 20 amp ESC spiking--just in case I put a ferrite ring on the ESC reciever side plug-everything is HAPPY HAPPY JOY JOY!!!!!!
JoeHelicopter Flies Again :fly
The guys at Spektrum took good care of me!!!!!!