Hello Tridge,
I uploaded the 2.78 beta1 to my Pixhawk and it seems to have solved my previous problems. However, now I can’t set the Battery Volts and Current. As near as I can tell, the pin assignment is off, causing MP to give a message that pin assignment failed.
Thanks for any help.
Also, if there is a more appropriate place to report on Beta FW, please advise.
Thanks,
Steven
This is a perfectly good place to post Qs on the beta 
What pin values did you try to set? I don’t know why MP would say a pin assignment failed, as you can set any number you like in _PIN variables (at least up to 127). Only some numbers will actually work, but setting others shouldn’t give an error.
On a Pixhawk I’d expect BATT_VOLT_PIN to be set to 2 and BATT_CURR_PIN set to 3 if you are using a 3DR power brick. Is that what you set?
Cheers, Tridge
[/quote]
This is a perfectly good place to post Qs on the beta 
What pin values did you try to set? I don’t know why MP would say a pin assignment failed, as you can set any number you like in _PIN variables (at least up to 127). Only some numbers will actually work, but setting others shouldn’t give an error.
On a Pixhawk I’d expect BATT_VOLT_PIN to be set to 2 and BATT_CURR_PIN set to 3 if you are using a 3DR power brick. Is that what you set?
Cheers, Tridge[/quote]
Hi Tridge,
Let me be more clear. After loading the beta FW, I was attempting to set up the battery and current parameters in the Initial Settings, Optional Hardware, Battery Monitor. When I tried to enter either Pixhawk or the 3DR PM, I would get this pin error message. So I went to the full parameters list to check the pin assignments, the same as you mentioned above and they were correct. However, I still had no battery V/I showing on the MP HUD. I did a reset/clear in terminal and got things working. BUT when I go to the Battery Monitor setting screen, it will accept nothing for sensor type EXCEPT Other. Bottom line is, I now have V/I showing on the HUD but not with the correct inputs on the Battery Monitor screen. It’s no biggy but since it was beta, I thought I would give you the feedback.
Best,
Steven
It sounds like this may be a MissionPlanner bug, not a APM:Plane bug.
Maybe ask in the GCS section of the forum, or see if an MP update may have fixed it?
Cheers, Tridge