Replies to This Discussion

Permalink Reply by Cliff-E on June 24, 2012 at 5:00pm

Are you saying you enabled MavLink 1.0 in the code and recompiled? If so, let's look at the code (GCS_Mavlink)....

mavlink_msg_sys_status_send(chan,
        control_sensors_present,
        control_sensors_enabled,
        control_sensors_health,
        0,                                                 <------------- load always zero!
        battery_voltage1 * 1000, // mV
        0,                                                  <---------- current always 0!
        battery_remaining,      // in %
        0, // comm drops %,
        0, // comm drops in pkts,
        0, 0, 0, 0);

There's your problem (it's always zero cause it's not implemented yet), and considering you successfully compiled it, you have 2 choices: add a method to calculate the current youself (and resubmit to the devs--the spirit of open source :) ). or 2. you can add it as a bug if you really need it and see how the devs schedule it in for a version release. The again, if you implement it, I'm not sure if Mission Planner will read it (since it not implemented yet).

• ▶ Reply

DeveloperPermalink Reply by Andreas M. Antonopoulos on June 24, 2012 at 5:52pm

There is a bug report related to a scaling issue on battery_remaining from Andrew Fernie, which also adds "current" to the status. The code just got added to the repository a few minutes ago.

https://code.google.com/p/ardupilot-mega/source/detail?r=a190e9509b...

• ▶ Reply

DeveloperPermalink Reply by Michael Oborne on June 26, 2012 at 2:50am

current will be added in the next planner version.

• ▶ Reply