Hello all. I'm having a tough time arming my motors. I was following the Configuration section of the Arducopter 2 wiki and made it all the way to ESC Calibration*. I tried automatic calibration, but when I tried to test it as described at the bottom of the instructions, the motors wouldn't arm or spin. So I tried calibrating again a few times, but no avail. Then I noticed my green "A" LED wasn't lighting while in fly mode. It lights solid when in CLI mode, and during the ESC calibration the A-B-C LEDs were lighting in sequence as expected. I did some poking around the forums here and found a few other related** posts***, but none of the posted solutions seemed to work. I even tried "letting it sit over night" a few times. :P
I know my motors work, since I can drive them individually by connecting the ESC's servo header to my RC's throttle output. I know the motors will also run in unison as I accidentally left the throttle low during one ESC calibration attempt. I found out during that flub that the motors will all spin uniformly if I give it a little throttle.
I don't know if this is related, but I'm also having trouble connecting to APM Planner (1.0.20) in flight mode for the flight data and related tabs. The firmware and terminal tabs both work fine. When I hit the "Connect" button, it eventually times out and complains that MAVlink was not present in the data stream. Connecting works flawlessly and instantly in the Terminal. The terminal reports my ArduCopter version as 2.0.30 Beta, firmware version 102.
Does anyone know what's going on? I've been trying to figure this out all week now.
In general MAVLink connect issues mean that your IMU isn't booting up, which is usually due to a hardware issue. If you got to the Mission Planner Help tab and click the box to enable the console, and then close and restart, you can see the bootup messages. This is the normal text that precedes a successful MAVlink connection.
Chris - Yes I have tried this and never got past the repeating timeout CRC errors. I've gone and run the componenet level tests from within the Arduino IDE and have the following results:
I'm reading code now to determine if I can see if it hangs here.
Great minds think alike eh? I was PMing you when you posted here. You should load the Arduino IDE if you haven't already Its pretty straighforward.
Next download AC2 latest version to disk manually so you know where it is, then run the Arduino IDE. and then Load the software: File > Examples > APM_BPM085 > APM_BPM085_test.
You need to compile it (press CTRL+R). This takes a few seconds. Then click the load icon at the top of the window.
Finally, when it is loaded, press the terminal button to open a terminal to the USB connected 'copter. (set to 37800 baud). The results will show in that window.
Clear as mud !
Thanks Paul! I ran various component tests, all with passing results. Or at least I got sane data out of them.
When the A light blinks you can arm your motor. Auto-calibration for the GPS can delay things by 30 seconds if you don't have a GPS installed. I'm sure not having a PWM signal going to the board can prevent the main loop from starting too.
I would like to add a little info to this posting:
I have just got finished testing an oilpan / APM which was returned with a fault which I believe is the same as a few people have reported here, I have tested the AP in the mission planner with both the ACM and APM codes and the result is the same, I get the time out issue with the MAV link and in the terminal window I only get this message:
NOTE: You must disconnect and move the slider switch when done to use other tabs
Opened com port
Init ArduPilotMega 2.2.1
Free RAM: 2179
load_all took 1952us
using 2465 bytes of memory
The code will not progress beyond this point.
The loading of the code in mission planner & verification seems to work just fine on both codes tested.
I have also loaded the code 2.12 from the IDE and had the same issue but have seen this message:
Init ArduPilotMega 2.0
Free RAM: 2614
EEPROM blank - all parameters are reset to default values.
Switch was in the “servo” position throughout both trials listed above.
I know we don’t all have a few test APM’s, however I do have a few here, and have found using another two known working Oilpan the fault will disappear and the code loads without issue.
I have also been speaking with Tim on the phone today about the issue he has logged with me and posted about a few comments back, it sounds as if he has the same fault as the boards I have been testing for another customer, I’m waiting on Tim to confirm that he has the same message in the “terminal” of the mission planner, I will have his boards here in the next few days and will run the same tests, I think I will find the same as with those tested already today.
I will update this information as and when I have more information.
I just tried the latest AC2 code via the latest APM mission planner and now the mavlink connects OK. Until I tried this combination of software firmware, I was getting the standard timout commands in the console.
Now, the artificial horizon acts as it should in the flight data tab with the exception of the compass which I haven't set up yet. I'll be setting this up tomorrow night and will let you know how it goes.
Try giving this a go and let me know how you get on.
Also a massive thanks to Martint for the excellent customer service.
Glad to hear that worked for you, Tim! I'm curious what version numbers you have for Mission Planner and AC2. I just updated this morning with MP 1.0.24 (build 1.0.4201.29409) and AC 2.0.33 Beta. However, MAVlink still times out, and the "A" LED never lights.
Just curious, does the sequence of motor/esc chirps mean anything? Or are the chips just reminders that the system is energized?
Sorry about the late reply, had to work late last night and didn't get a chance to work on the copter.
I'm using 2.0.33beta for the firmware and for the APM Mission planner its 1.0.26 build 1.04.4203.31490.
What is interesting is that I couldn't connect again this evening again, I restarted both the laptop and the APM board (unplugged battery as well) and now everything seem ok again. This may be due to a bad solder joint somewhere(!). I'm going to get the iron out this weekend and go over everything again to see if I can connect consistently.
About the beeps, em, I have to declare I'm not too sure. There's an awful lot to read in this arducopter business, so I took the easy way out and purchased an ESC programming card off ebay for about 8 UK pounds (about $12). I have to say it was totally worth as I know there's no messing about with calibrating them and they seem to work perfectly so far.
If you want to find out what all the beeps mean, I would suggest a quick bit of googling for the ESC programming card manual for you particular flavour of ESC. I'm using Turnigy Plushes and the link to it is here: http://www.hobbywing.com/upload/manual/ESC_e.pdf
I'll let the forum know how I get on after some more tests this weekend.
Great to see you are back on track, if you have any other issues please do let me know!