Replies to This Discussion

Permalink Reply by Simon on August 6, 2011 at 3:07am

I also have a APM1280 and I get the same thing so I dont think its a hardware issues unless its the oilpan.

 

I am using the APM Planner 1.0.49 with the firmware it uploads to the board.

• ▶ Reply

Permalink Reply by Simon on August 6, 2011 at 3:11am

Also if I upload the SkyWalker pram file from google code the altitude is about 1500m out.

 

Seems weird

• ▶ Reply

DeveloperPermalink Reply by Michael Oborne on August 6, 2011 at 3:19am

try doing an erase from the cli, and re setup.

• ▶ Reply

Permalink Reply by Simon on August 6, 2011 at 3:33am

thanks for the quick reply.

 

Just erased it and quickly configured a few setting and rebooted it. Worked fine. Everything looks good.

 

Then I uploaded the attached file and the same problem happened. I did the same thing with the SkyWalker file dloanloaded from Google code and that causes the same error.

 

 

Attachments:

• SkyWalker.param, 2 KB

• ▶ Reply

Permalink Reply by Simon on August 6, 2011 at 4:01am

Seems to only happen when I upload a file.

• ▶ Reply

Permalink Reply by Jesper Rooth on August 6, 2011 at 9:15am

Hi Simon

 

This is the third thread about the same issue in three days. My thread. Reset button (clears waypoints)

Lets work together to see what could be causing this problem. I also identified one possible cause with uploading the Skywalker parameter file. Something is not compatible with the parameter file and the latest version of Mission Planner. Still searching.

Apart from the parameter problem. Have you also had the same problem as described in this thread? autopilot goes crazy. Full throttle and nose down.

 

Regards,

Jesper

• ▶ Reply

DeveloperPermalink Reply by Michael Oborne on August 6, 2011 at 5:42pm

ive found the problem when restoring from a param file. if the file was saved under a diffrent version of apm, it reset on next reboot. i will be adding a check/ignore in the next planner version "SYSID_SW_MREV" is the issue

• ▶ Reply

Permalink Reply by Justin on August 10, 2011 at 10:47pm

The skywalker config file has SYSID_SW_MREV 8 in it, but the current code wants to see 9.

If it sees 8 != 9 then it prints

"EEPROM format version %d not compatible with this firmware (requires %d)"

and erases all the parameters.

• ▶ Reply

DeveloperPermalink Reply by Michael Oborne on August 10, 2011 at 10:52pm

in the newest planner this is now ignored, so should not be an issue

• ▶ Reply

ModeratorPermalink Reply by Hai Tran on August 10, 2011 at 7:46am

I had the same problem after loading the skywalker param file.

I did notice that the stabilize P values on the skywalker param is a lot higher that default is that correct or a legacy value?

• ▶ Reply

3D RoboticsPermalink Reply by Chris Anderson on August 10, 2011 at 7:48am

Yes, the Skywalker P values should be higher, as shown in that config file. The default PID values are all very conservative, and are meant to fly any aircraft okay. On most aircraft you would tend to raise them as you tune for optimal performance.

• ▶ Reply

ModeratorPermalink Reply by Hai Tran on August 10, 2011 at 7:49am

So 3.2 or something like is ok fr skywalker? The default is only like 0.8

• ▶ Reply

• ‹ Previous
• 1
• 2
• Next ›
• Page