Param List sending

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Try getting the param list.
2. at the moment the list length is hard coded to 256 and the param index is 
(eeprom offset???)

it should be a param count and a index based from 0

current code Mavlink_common.h

            mavlink_msg_param_value_send(chan,
                                         (int8_t*)param_name,
                                         value,
                                         256,   <-- should be param count
                                         vp->meta_get_handle()); <-- should be param index.

Original issue reported on code.google.com by Meee...@gmail.com on 15 Feb 2011 at 11:35

[GoogleCodeExporter]

Original comment by Meee...@gmail.com on 15 Feb 2011 at 11:36

• Added labels: Type-AP_VarIntegrationIssue
• Removed labels: Type-Defect

[GoogleCodeExporter]

The AP_Var parameter store doesn't actually know how many parameters there are 
(parameters can actually come and go at will), and not all of them can be 
reported via MAVlink as it stands.

There's also no contiguous, indexed array of parameters - it would require too 
much memory to keep it as such.  The smallest unique handle that can be vended 
for an AP_Var is 32 bits in size (type ID + memory address).

With that said, we can probably managed this on the front end in the MAVlink 
code; it won't be entirely pretty (read, slow-ish).

Original comment by DrZip...@gmail.com on 16 Feb 2011 at 5:20

[GoogleCodeExporter]

This issue is dead, isn't it?

Original comment by dewei...@gmail.com on 14 Mar 2011 at 10:01

[GoogleCodeExporter]

id say yes

Original comment by Meee...@gmail.com on 15 Mar 2011 at 11:20

[GoogleCodeExporter]

Original comment by dewei...@gmail.com on 21 Mar 2011 at 3:28

• Changed state: Fixed