Since I didn't have this problem with 2.5.02, I looked at the difference in code and noticed the new line in system.pde - setcommandMux.
I tried commenting out the "setcommandMux" and the GPS achieved lock in manual mode. I'm playing around some more this weekend, but I wanted to post my findings since I have the older shield board.
Thanks,
Heino R. Pull
heyno@heino.com
switch(control_mode)
{
case MANUAL:
// setCommandMux();
break;
case AUTO:
break;
case STABILIZE:
break;
case FLY_BY_WIRE:
break;
case RTL:
return_to_launch();
break;
case LOITER:
break;
}
Replies
I have another question as well. Under the attitude tab. If you look at stabilize only it reads something like
if Throttle in ==0
then servo_out = Throttle cruise;
Should it not be if the throttle is enabled?
Then second question, might not be the right place to post it but...
Should the second jumper on the arduboard also be soldered underneath the board to read throttle? When i started they did not have the second jump wire, i see know however that it has been added... Might that explain why, when i switch to stabilize it cuts throttle and only glides?
I re-looked at the files it should have read:
I've zipped up what I was working with last night and attached here. I'm running with the throttle directly attached to the receiver for now so I think I've got the throttle set correctly and I'm also testing with the RBF jumper attached/unattached to see what happens.
Heino
Ardupilot_25_03hrp.zip
The mux functionality is implemented differently for each shield. You may have the shield set wrong in the header file or it could be a bug. Could you zip up your files including the header and post them here to verify?
Thanks,
Jason