If anyone has any issues or logs to analyze please post them here. I've also updated the Wiki to detail out all of the AP mission scripting commands. If any command doesn't work as expected please post that here as well.
You can also post issues to the Bug list here: http://code.google.com/p/arducopter/issues/list
BTW, I just updated the Firmware version so settings will be cleared. You'll have to redo the level, radio, compass, etc for this version. This is to ensure no bad EEPROM values cause conflicts in flight.
I barely tested the v44 now there v45 you are fast Jason....will try to load it and test it soon as the weather clears out. By the way what does flip do?
the broken switch notes that we can use the yaw to go cli and flight mode, is this still being used? I plan to enable it as its troublesome to have a cover removed just to a flip the switch. Just curious how is it different from the arm/disarm or if this is enable disarm + CLI / arm + fly
Here is a log of my second test fly with 2.0.45.
Strangely, i got an error at the end of log download inside Mission Planner, saying that lat and longitude should be between -180 and +180.
This is the second time i got this error. I got it with 2.0.44 as well.
Seems like the log is corrupted, GPS data for example is fully wrong.
We should have something like this :
GPS, 56147250, 11, 48.2704390, 4.0287061, 11.8000, 127.9000, 363, 34181
But as soon as we get CTUN data in the log, GPS is corrupted :
line 33428 : GPS, 57314250, 12, 48.2704620, 4.0288911, 477.7900, -17948998.0000, 281, 0
Is it a log only problem ? I'm not sure about this, because the loiter test i did was uncessfull. As soon as i engaged Loiter, the multi did fly in a direction and changed height, instead of trying to stay in the same place. So i disengaged Loiter fastly.
I looked at this log and the GPS error is really odd. Was this all from the same flight? It seems like data that was written by another version and the data set had changed.
Your loiter looked bad, but it seemed to be working. Just needs some tuning. Maybe adjust Nav_P up or down with your CH6 proportional control.
Another firmware version ? I thought that a full erase was issued when a new firmware version was released ?
How does work the log write system ? A new log is created at each motor arm ? What if the log become full ? is it overwritten from the file start ?
Would it be possible to include a time stamping inside logs (from GPS time) and a flight number (according to motor arms), so that we can know for sure.
I join a log of my first fly, running ACM 2.0.44, with same GPS problem and same Mission planer download error :
Good data :
GPS, 55153750, 6, 48.2849240, 4.0695729, 0.3400, 110.3000, 0, 13437
Bad data :
GPS, 70379000, 1, 13.6103860, -50.3157500, -335544.3100, -18958254.0000, 3584, 640
@Greg, curious what do you mean you have remove comments from config.h for ALT_HOLD I dont remember that being changed in the GIT also I rather set things on APM_config.h than changing config.h (just preference) I cant test yet the v45 as its still raining but I will try it out just want to make sure I am seeing what you see
Greg: Tested Alt hold on 2.0.45 with only the Mission Planner setup. No recompiling in Arduino. I set up Stabilize, Alt Hold, and Loiter from the Mission Planner successfully. Simple mode set up is more complicated and I did not test it today.
Heino: Good to know about the Alt Hold on 2.0.45 setup in MP. I must figure out the change to simple mode setup. I assumed I could click on the Simple check box in the MP mode menu but perhaps not? I am not seeing expected params values for the mode setup in MP. I plan to fire up Ardunio and go back to old fashioned manual complies until I understand if I am reading the values correct in the params field after the changing mode settings in MP.
afernan had an excellent post in this thread about setting up simple mode - that I just haven't had time to really setup yet. I've been flying the MP download yesterday and had some trouble with simple mode setup in 0.44 so I didn't spend timing looking at the code to figure it out in 0.45.
In 0.44 I just clicked the options in MP and they did not work for me and I think this post explains that issue.
It´s on page 9 of "Arducopter 2.0.44" post. I´ve already tested on 2.0.45 and it works fine.
In sumary, if you want to have 6 modes in your Tx, using two channels (ch7, two position switch and Ch5, three pos), you must do the following:
1) in APM_config.h (line 32) activate:
# define CH7_OPTION CH7_SIMPLE_MODE
2) Then, whith the Ch7 switch position high it´s possible to acces to SIMPLE, that is,you can tick this option in the MP and it will work. If you tick SIMPLE in the three oftions corresponding to Ch7 low, it won´t have any effect, obviously.
Tip.Use "reverse" in your Tx or in the MP>radio>tunning to get your preffered Ch7 position.