Hi everyone,
I've recently updated the firmware and flashed my apm 2.7 board. All went well, until I couldn't arm the motors with the lipo connected. It would only arm under apm. I got it sorted anyway, by re calibrating everything under MP. I had problems with APM Planner software.
Anyway... Everytime I go under the MP terminal (and APM Planner) I get mumbo jumbo after I connect under terminal.
Is there anyway to remove this? I cant even re flash or compassmot.
Cheers
Replies
Thanks for your reply Craig. I have managed to get my APM working again. Upgrading the firmware is a bad idea. I totaly down graded back to 2.72. (Possibly the original firmware when i bought it) And bang.. it all worked.. BUT I still had a connection error. But It still all works as I installed the last STABLE version.
I am currently testing the loiter GPS before I get back to this post and let you know.
However I thought I would test the loiter with default settings and the quad just lowered down trying to land, until i raised the throttle to bring it back up. So at the moment I am getting the logging data from the APM and loading it into the Log Calibration. I have used the other calibrating features but I'm yet to test this logging out.
Does anyone feel they get better results using the log Calibration?
Bump: Down grading to an older version... would this solve the problems I'm having? The APM board is a 2.72. me thinks.
There is no Terminal in APM:Copter 3.2-Dev build you are using. It has been removed to save space for other firmware features.
It may be 3.3-Dev, but the image is so low res it hard to tell. If you are running 3.3/2-Dev I hope you are a dev.
Bill's right. I should have had a closer look at the screenshot. As he says, there is no terminal / CLI in the version you ave there. If you load the released 3.1.5 version the CLI is still there
Oh yes.. I also saw the same problem again when I flashed to Version 2.9. Since going back to the original flashed version that came with the board i have not seen this weird code under the CLI again.
The Board I have is a RC_Timer APM 2.72
Actually upgrading to 3.2 when we release it will be a great idea. We have replaced most of the CLI functions with MAVlink commands and saved a lot of memory.
Bill, I am currently trying to Verify the arducopter sketch to the board.
But the sketch is too big.
I've tried to DISABLE options under the APM_Config.h and also have tried another program tools called MHV AVR Tools. Is there another way? I have no idea how to use MHV.
My board is ArduPilot Mega 2+
You need to read the runes here http://dev.ardupilot.com
and in paticular http://dev.ardupilot.com/wiki/building-the-code/
That link will explain how to install and setup the right tools for your platform you are using to get better code size that will upload.
PS: I'm not sure if master will fit. ArduCopter-3.2 branch will fit on APM2.x platform. So you may need to check that one out.
Okey.. The weekend has been not been great. Been on the computer for the past 20 hours trying to get this apm ready as how i first bought it months ago.
1. I have flashed it successfully. Me thinks. I used ArduCopter 3.1. (Had probs with the latest version)
2. I ran into probs uploading the quad hex file on the APM. I tried the stable version. 2.71. It took awhile to try and read what version of the board I have. Then it hung 80% of the way trying to upload the hex file on the APM. After that it says I lost connection. But it than went into the next setup stage such as calibrating with no probs.
3. Now after setting everything up with parameters etc, the motors will not arm outside of mission planner. I've read so much about this in other forums but each problem is unique. I've tried many ways to fix it.
I think i better get a Naza. wopps, should i say that under the post? I'm tired..
Today i will try 2 more times with a lower flashed version ArduCopter. Any suggestions?
The board I have is a APM 2.72 I don't think that version is correct.
Thanks Bill for this. I'm trying to cram all this in my head as I read this dev codec stuff. It's going to take months to work it out for me. I have down graded to the ArduCopter 3.2 platform. Now I get a few other errors i dont know what to do about it.
Should I start another post or use this post?
When i verify the code, it now says:
no matching function for call to "AP_MotorsQuad::throttle_pass_through(g.rc_3.radio_in);
And a few times it still came up with file size too big.
-
1
-
2
of 2 Next