1 | initial version |

I haven't used these platforms myself, but `32.7`

sounds like the upper limit for a signed, integer math 16-bit variable (`-32768`

to `32767`

, shifted 3 sign. digits). Perhaps a known issue / upper limit?

2 | No.2 Revision |

I haven't used these platforms myself, but `32.7`

sounds like the upper limit for a signed, integer math 16-bit variable (`-32768`

to `32767`

, shifted 3 sign. ~~digits). ~~digits (`/ 1e3`

) -> `-32.768`

to `32.767`

). Overflow would then result in what you are describing. Perhaps a known issue / upper limit?

3 | No.3 Revision |

I haven't used these platforms myself, but `32.7`

sounds like the upper limit for a signed, integer math 16-bit variable (`-32768`

to `32767`

, shifted 3 sign. digits (`/ 1e3`

) -> `-32.768`

to `32.767`

). Overflow would then result in what you are describing. Perhaps a known issue / upper limit?

Btw, just noticed this: you mention `deg/s`

. Are you sure that is the correct unit? ROS standardised on radians and radians/sec. The msg docs for asctec_hl_comm/mav_ctrl fi also explicitly state everything is in SI units.

Edit: ah, apparently `ctrl_test`

accepts `deg/s`

units to be used for this (here).

ROS Answers is licensed under Creative Commons Attribution 3.0 Content on this site is licensed under a Creative Commons Attribution Share Alike 3.0 license.