Turns out, I have to use the udpout string and after mavutil.mavlink_connection, I have to send a heartbeat packet from the GCS.
EDIT: I also found this method only works if you only run this after you connect to the FC via MissionPlanner first. After this initial connection, I may disconnect and then use pymavlink. So dont bother with this issue. TCP is fine
I noticed that an update will be required in Mission Planners Initial Tune Parameters to address the parameters name change for the ATC_ACC_x_MAX parameters. As this is a step in the AMC it will require some revision also. And the values being refactored will have to be considered.
AMC is ArduPilot firmware version aware.
Yes, at some point I will add the code to convert an AMC project from ArduPilot 4.6 into a AMC project from ArduPilot 4.7.
It can be done automatically, because AMC will see the the files on the HDD mention 4.6 and the FC is running 4.7. That will trigger a dialog to convert the old files into new ones in a different directory. That is a planned feature for the next couple of weeks.