Dx6i calibration problem

[discoferret]

Hi, Ive been using my DX6i on Phoenix without a problem for over a year now. I've had no problems calibrating it, but when I came back from the field on Monday I went on Phoenix and the TX had lost calibration. The heli was all over the place. I then tried to recalibrate and now I'm having trouble with Channel1. It only uses half the travel on channel 1. I thought It might be the TX so I took the real heli out to see if the TX had had it and the heli flew fine. Any ideas?

[murph]

Have you selected a blank model form the tx memory? If you are using the same model as your heli then that might be the problem?

[discoferret]

Yeah I have a seperate model loaded on TX just for Phoenix. Which has been on there for over a year. Just started playing up when I tried to use it.

[bolders]

Hi mate

I would check the DX6i is functioning correctly (check the pots are giving good output etc)

Choose an empty model memory and then reset it to defaults (this should reset ATV points, trims, sub trims etc to zero)

Switch model to HELI if it is not already.

Then go into the MONITOR screen in the SETUP list.

Move all your sticks to their extents and check that the pointers are moving the full distance i.e. 1 notch in from either end. Also check that the pointers are all at the centre point of the scale when all sticks are centred

This wont be the case for channel 5 though as this is controlled by the GYRO switch

If this isnt the case recheck all atv, subtrims etc are zeroed. If they are then I would give Horizon a call as it maybe a faulty pot.

Just a thought but have you checked to see if your DX6i was affected by the product recall on faulty pots.

Have a look here

Spektrum RC: Spektrum DX6i Recall Consumer Notice

[discoferret]

Ive checked to see if my DX6i was affected by the recall a while ago and it wasnt. Ive just done what you said and the model that I've been using on the TX for over a year wont travel the full distance on the monitor screen on the channel that Im having problems. Ive now created a new model and its has solved the problem. I dont know why I didnt think of that in the first place. Thanks for that.