Flashing Codes
 

Ok Chaps,

Having succesfully upgraded my DV4 module to v2.63, I've now hit another problem.

I'm using a micro 10 receiver with gyro and its running on v2.50 (according to the release history there seems no reason to upgrade the receiver). All appears to be working normally on the ground (not flown since upgrade of Tx module) except that after about 30 secs from turning on the red Error LED flashes 3 on/ 1off. Having checked in Gigacontrol its definitely not a tx or rx battery threshold limit The expanation sheet for the flashing codes suggests that it is the gyro under recalibration, but the flashing just continues until I turn off the tx, prior to that the gyro appears to be doing what its supposed to.


Any suggestions please.

Hi,

as far as I know, gyro calibration takes place when you power on the RX and the TX, thus they have an connection. Then leave the RX untouched for a few seconds an the Gyro(s) are set and red LED blinking on the RX stops. I am not sure but it sounds that you have a flashing red LED on the DV4 ? This can not be the gyro since this is only displayed at the RX side.

I have no RX older than v2.56 and have already upgraded 10 of my 17 WEA RXs to v2.63m from TINY to GIZMO no prob. I in your place would do the RX upgrade whenever there is one... never had bad expirience with this practise...

Do a Backup of the RX first, as config data is stored in the RX. After update, restore the config with GC and as always, recheck all functions. Will be interesting if the "problem" you mentioned is gone with that. By the way:

Changelog for the Micro reads: V2.63 20130711 verbessungen beim Gyro => enhancements for GYRO operation


best regards

tom

Tom,

Thanks for the information, I've now upgraded the receiver to v2.63 and the flashing (which was on the DV4 module) has now stopped.
Interestingly, even though I had saved the original model configuration and then reloaded it, after rebinding a couple of the channels no longer worked. I could see the input on the x axis but there was no output on the y axis. On one channel there was an output which had reversed itself and reversing the channel, or the sevo, in Gigacontrol had no effect. After a while I discovered that if I unassigned the faulty channel and then reasigned it, the output returned to normal.
Hopefully no other gremlins will creep in, but everything right now appears to be working ok.
Thanks again for your help.

Hi,

we came yet back from the flyingfield.Have flown our CARF EXTRA with Micro10 G3. Update from 2.58 to 2.63 was prior made. No Probs with the Gyros or anything. Flight in the sky until it was only a "dot". Didnt even partly lost the back-channel... all went well. Nevertheless we did also check all functions after the upgarde but did nor find any inconsistence. Maybe the config from 2.50 to 2.63 is a "long jump" and there have been new parameters introduced. But when I understand you right, approx. 90% of the config was restored OK, or ?

best regards

Tom

Tom,
Yes, eight of the 10 channels worked ok, but on the two that didn't the faults were not the same. I also upgraded another micro 10 receiver and got similar results, that is most of the configuration would be reinstated but again a couple of channels would not work correctly. One was on a landing light, which had reversed itself. I thought that it would be easy to fix by just reversing the servo or channel output in Gigacontrol. When I did this, the output reversed for about a second and then went back to where it wanted to be!

Once I had discovered that unassigning and then reassigning the channel corrected the fault, I did this to each of the other faulty channels on both receivers and all is now working as it should again............weird!

Interestingly, before finding out how to fix the faults I moved the servo plugs to unaffected channels so that the model reacted as it should to the transmitter commands. I took one of the planes flying yesterday and had 5 flights with no ill effect, so apart from the individual channels showing faults, everything else worked normally.

As you say, perhaps the upgrade from v2.50 to v2.63 was a 'long jump' (both receivers were on v2.50 initially). All is working correctly now but its something for users to remember if after an upgrade they find that one or two channels are not behaving as they should.

I contacted Jens Ackermann at Weatronic, by email, and got a prompt reply asking for additional information , so he is on the case.

I want to confirm the order:
1- install the newest GC software in the PC.
2- Use the new GC to connect with the TX/RX (still using older firmware). The do a save in the local PC of the current setting in the Tx/RX.
3- Do #2 with all the RX that need to be updated
4- Proceed with the TX firmware update
5- Proceed with the RX firmware update
6- Open GC and send to the TX/RX the seetings saved in step #2 above.
Did I got it right?

Yes that is correct. The new firmware on tx should even be backwards compatible to rx newer that 2.33 if you need to store setting on rx'es later.