Page 1 of 1
2.4.2 strange thing
Posted: Sat 08. Jul 2017 12:58:52
by alchemy66
Hi, I just updated my 2 helicopters to v2.4.2 .my 450 pro updated just fine and after I had cycled the power and checked all settings all was as it should be. However, when I was updating my 380 the swashplate suddenly went fully over on the aileron. I allowed the update to finish and cycled the power. On checking settings it had changed the swash type from 120° reversed to 120° and also removed the throttle from channel 1. I went through the whole settings and those seem to be the only changes. Its all fine now but good job I checked everything. So even though you are advised that all settings should remain I would check it anyway just to be sure.
Re: 2.4.2 strange thing
Posted: Sat 08. Jul 2017 20:00:20
by ZeXx86
Hi,
the problem is really strange, but it is very likely not related with version 2.4.2 at all.
It was rather coincidence with other issue, but if you will update again (or even downgrade) you will see that nothing will change.
The problem could occur if you for example load some settings or start the setup wizard or you were configuring using BT module and connection was unstable.
But in any case it should not happen.
We have did hundreds of updates/flashing and it never happened. Please try to focus if you have not did any of mentioned actions before or after the update.
Re: 2.4.2 strange thing
Posted: Sun 09. Jul 2017 1:45:44
by alchemy66
Hmmm,, I did one helicopter, no issue, then the next straight away. No Bluetooth module, wasn't changing any settings or using the wizard. All I did with both was this, power my transmitter, connect the spirit to the laptop, power the spirit and run the update. that's it. One after the other. First one the 450 no issues. Then the 380, and what happened is exactly as I described in original post. I'm not bothered, I always check my settings after an upgrade. Just thought you should know.
Re: 2.4.2 strange thing
Posted: Mon 10. Jul 2017 7:42:12
by ZeXx86
Thank you very much for the details.
We will be investigating, but as of now nobody else reported the issue. Yes, it should mean no issue for usage.