Megaplanner does not report motor 5 output. (Hexa setup)

[GoogleCodeExporter]

Arducoper NG or ACM?
What steps will reproduce the problem?

Run megaplanner Ac2 sensor, radio window.

AC2 Sensor Radio Window does not report motor 5 output value. Motor 6 is 
reported correctly. (Hexa setup).

What is the expected output? What do you see instead?

Expected output is normal Motor 5 value reports.

What version of the product are you using? On what operating system?

ACM 2.0.22
Megaplaner 0.4.38

Please provide any additional information below.

I've seen this bug since a couple weeks.

Original issue reported on code.google.com by olivier....@helidream.fr on 4 Jun 2011 at 2:58

[GoogleCodeExporter]

same on the new planner?

Original comment by jasonshort on 6 Jun 2011 at 4:37

[GoogleCodeExporter]

same on the new planner?

Original comment by jasonshort on 6 Jun 2011 at 4:37

[GoogleCodeExporter]

Same problem with Planner version 1.0.0

Original comment by olivier....@helidream.fr on 6 Jun 2011 at 11:38

[GoogleCodeExporter]

ive sent an email to jason about this one.

Original comment by Meee...@gmail.com on 7 Jun 2011 at 12:24

[GoogleCodeExporter]

Original comment by Meee...@gmail.com on 7 Jun 2011 at 12:43

• Changed state: Accepted

[GoogleCodeExporter]

Here is the Mavlink code:

case MSG_RADIO_OUT:
{
    mavlink_msg_servo_output_raw_send(
            chan,
            motor_out[0],
            motor_out[1],
            motor_out[2],
            motor_out[3],
            motor_out[4],
            g.rc_5.radio_out,
            g.rc_6.radio_out,
            motor_out[7]);
    break;
}

Here is the Hexa output:
CH_1
CH_2
CH_3
CH_4
CH_7
CH_8

I could map this anyway you like. I just thought the Mavlink message had a 
limited number of fields. 
I can even setup different outputs based on frame types. Let me know.

Jason

Original comment by jasonshort on 21 Jun 2011 at 4:56

[GoogleCodeExporter]

I would map like this :

CH_1 -> motor_out[0],
CH_2 -> motor_out[1],
CH_3 -> motor_out[2],
CH_4 -> motor_out[3],
CH_7 -> motor_out[4],
CH_8 -> motor_out[5],
CH_9 -> motor_out[6]);
CH_10 -> motor_out[7]);

Eventually do not transmitt unusefull motors, to save bandwith in the radio 
link.

Any possibility to transmitt the frame type through Mavlink, so that the GCS 
can adapt their graphic presentation ?

This would save code lenght in the APM and give a better GUI at the GCS side 
(could use frame drawings with motors at the right places).

After thinking a bit more, the GCS know the frame type, because we choose it at 
the firmware upload time. So it could keep it to present a nice and adpated 
motor panel.

Original comment by olivier....@helidream.fr on 21 Jun 2011 at 8:35

[GoogleCodeExporter]

hello,

Can you see my last reply on that post ?

http://www.diydrones.com/forum/topics/apm-planner-arducopter-first?xg_source=act
ivity

Thanks

Original comment by Theo.Anu.sun on 27 Jun 2011 at 3:56

[GoogleCodeExporter]

Another note on the APM. I could not find the appropriate place to add this so 
I apologize.

Not sure if it has been mentioned but the new APM Planner does not zoom 
properly on the east coast of the United States. Not sure if anyone cares but 
it makes it hard to plan without good resolution. I cannot zoom in closer that 
about 100 to 300 meters(not sure exactly) but I guess it has soimething to do 
with resolution to sea level conversion. If you take a home position of 39.2665 
and -73.8662 you will see what I mean.

Original comment by bill.snyder.bs@gmail.com on 4 Jul 2011 at 6:34

[GoogleCodeExporter]

Original comment by jasonshort on 19 Sep 2011 at 12:22

• Changed state: Done