Replies to This Discussion

Permalink Reply by Omar Achraf on November 27, 2011 at 2:00pm

I had the same problem with my APM 2560 and Arduplane 2.26.

I them entered in console mode, did the reset then all tests. After that, i switched to flight mode, I compile and loaded the APM 2.26 through Arduino 22 and did all setup through APM Planner.

All works after these steps. But after unplug the batteries and plug again, the problem returns. By doing the steps above It works again and if unplug the batteries,next time I plug the problems repeats.

I them return the load to APM 2.24 for while.

• ▶ Reply

DeveloperPermalink Reply by Doug Weibel on November 27, 2011 at 10:24pm

The logging functionality changed between 2.24 and 2.26, and the new logging system may have trouble in some cases with existing logs.

 

Try this:  Downgrade to 2.24.  Erase logs.  Upgrade to 2.26.  This may take care of your problem.

• ▶ Reply

Permalink Reply by Omar Achraf on November 28, 2011 at 9:44am

Thank You Doug,

 

I did what you suggested and It worked. 

How much time APM on is required to fullfill the log space?

• ▶ Reply

Permalink Reply by Omar Achraf on November 29, 2011 at 4:07am

Hi, I have more feedbacks. I configured the modes and failsafe for 2.26  exactly the same way I did for 2.24:

   1=RTL; 2=Loiter; 3 and 4= Stabilize; 5=FBW-A; 6=Manual;

    Failsafe (throtle) = 1 with PWM threshold = 950 (RX was bind to produce 903 when out of signal and 1100 with 0 throtle);

 

what happens:

   Nothing happens when selecting RTL or Loiter in APM 2.26.

   By turning off DX6i transmiter, there is no RTL engaged. By turning on Again, APM 2.26 the motor starts spining.

   

 

Radio is DX6i with 5 modes set as explained in the APM manual pages.

These settings works with 2.24. I load 2.24 again as well did all the settings agains to check. Did 2 times to see if I forgot something to check.

I did not fly yet. I`m back to 2.24 again.

 

regards, Omar

• ▶ Reply

DeveloperPermalink Reply by Doug Weibel on November 29, 2011 at 12:45pm

Omar,

 

There was an eeprom configuration change between 2.24 and 2.26, so your eeprom settings may be corrupt.  I do not remember any changes to the failsafe functionality in that period.  Recheck all your parameter values related to failsafe and make sure they store correctly.

• ▶ Reply

Permalink Reply by Fred Forbes on November 28, 2011 at 7:15pm

Doug.it worked for me too.  Thanks!

 

I uploaded APM 2.24 and it worked.   Then I went back to 2.26 and, surprise, it worked also.

I couldn't erase the log because I had to disable CLI to fit the software in the ATmega 1280

The only remaining question mark is that after initialization the B led is on continuously

• ▶ Reply

Permalink Reply by Fred Forbes on November 29, 2011 at 10:32am

Ignore my comment re the B led.  I looked at the instructions again and B led on continuously is the correct operation

• ▶ Reply

Permalink Reply by Paul Feely on December 1, 2011 at 1:24pm

Glad I came across thread as was starting to rip setup apart suspecting h/w issue. Same problem but fix not working for me...

 

Downgrade to 2.24, system good. CLI,logs,erase.

Upgrade to 2.26 thro' Planner, after first reset same problem (no ABC lights). CAn't access by MAVlink but CLI still good for all tests etc. however 'logs' and it hangs so problem seems to be with log.

 

Is there something else I should do to clear out logs between version (other than CLI, logs, erase. Reboot then upgrade through planner)

 

Thanks, Paul

• ▶ Reply