You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- What steps will reproduce the problem?
1. Configure and enable a joystick to output "ardupilot mega" data.
2. Select the "serial data" tab. Optionally, connect the GCS to a virtual
serial port and grab the data output from the GCS.
3. Move the joystick's controls and observe the data output in the serial
monitor or serial port sniffer.
- What is the expected output? What do you see instead?
The expected output (as far as I understand) is a serial stream of a
RC_CHANNELS_RAW mavlink message. This stream should be composed by a start sign
(0x55), a Payload length (0x12), Packet sequence, System ID, Component ID
(those 3 values are irrelevant at the moment), the comes the Message ID (that
should be 0x23).
What it is in the real output is a Message ID of 0x46. But, curiously, in a
previous release of this GCS this message was formatted well (with a message ID
of 0x23).
Another fact is that in a previous release of GCS the message ID was correct,
and the payload length was assigned a value of 0x11 (17 bytes), and in the
current release this value has changed to 0x12 (18 bytes). I think the correct
value should be 0x11 (17 bytes), as the payload for this message is composed by
8 16bit-values plus 1 8bit-value.
- What version of the product are you using? On what operating system?
The problem is in version lite-1.3.16
- Please provide any additional information below.
Original issue reported on code.google.com by [email protected] on 15 Jul 2011 at 12:00
The text was updated successfully, but these errors were encountered:
Original issue reported on code.google.com by
[email protected]
on 15 Jul 2011 at 12:00The text was updated successfully, but these errors were encountered: