Replies to This Discussion

Permalink Reply by dr1ce315 on July 10, 2012 at 4:39pm

The process for downgrading the firmware seems a bit scary, but I'm pretty sure it's a firmware problem, can anyone confirm a working hexa+ with 2.6 firmware?

• ▶ Reply

3D RoboticsPermalink Reply by Chris Anderson on July 10, 2012 at 6:18pm

I fly with a hexa and 2.6. No problems at all.  Almost certainly a setup issue with your gear. Double check your prop directions, and run the Motors test in the CLI.

Also make sure your RC controller isn't in heli mode. 

• ▶ Reply

Permalink Reply by dr1ce315 on July 10, 2012 at 10:21pm

Thanks for the confirmation, before I went through the whole arduino downgrade route possibly having compilation errors (as I've read), although, I've used Arduino a bit in the past.

I read I should possibly try to do a EEPROM reset via CLI.

I'll report how it goes, and if anyone else has any ideas please let us know...  Thanks =)

• ▶ Reply

3D RoboticsPermalink Reply by Chris Anderson on July 10, 2012 at 10:25pm

Why are you using Arduino? The MP will just load the code for you (and make sure you're actually using the hexa version)

• ▶ Reply

Permalink Reply by dr1ce315 on July 11, 2012 at 10:34am

MP will only load the latest hexa code on the board.  I wish there were a way of uploading individual firmware via MP, but I can't find one, and in my perusing of Google I read the only way to downgrade is by compiling the sketch with Arduino, and uploading it manually.  I've uploaded 2.6 (and older versions, when they were current, in the past) via MP, and it works great, but there is no "downgrade firmware" or "manually upload" firmware feature in MP that I can find.  Also I would be absolutely positive I was uploading the correct hexa Sketch via Arduino but since you confirmed that 2.6 IS working with your hexa, then I'm going to assume it's not a firmware error.

I'm going to test the motors with CLI and double verify the controller isn't in heli mode as you suggested.  I'm also going to erase all the params in the EEPROM, and start fresh.

Hopefully today will make some progress...

BTW, Are you using APM1 or APM2 with your hexa?

• ▶ Reply

3D RoboticsPermalink Reply by Chris Anderson on July 11, 2012 at 10:36am

Why do you want to load an earlier version of the software? 

I fly with APM 2.

• ▶ Reply

Permalink Reply by dr1ce315 on July 11, 2012 at 10:47am

I wanted to downgrade the software because it was working correctly about a month and a half (or two) ago. I should also say that we did upgrade the motors and ESCs in that time period, but the ESC's have all been calibrated, etc, and as I said the wiring has been triple checked. 

I'm wondering if the problem is that I have APM1 instead of APM2...  Should it matter?  I thought I read some people with APM1 boards were having some problems with the 2.6 code?

• ▶ Reply

Permalink Reply by dr1ce315 on July 11, 2012 at 1:16pm

Alright everyone, seems like a factory reset fixed the problems.  For anyone who doesn't know how to do this, click on terminal, and get a CLI prompt.  Then type "setup" then then type "reset", and type Y for confirmation.  After waiting about 5 minutes I reloaded the latest firmware again, re-calibrated my radio, level, flight modes, configuration, and viola, everything seems to be bench testing perfectly.  Time to try the real flight =)

Thanks for the replies Chris

• ▶ Reply