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
During some testing I wanted to test the response with some I term, where the PITCH_RATE_I is accepted, but changes to ROLL_RATE_I and YAW_RATE_I are not recognized.
When running rosservice call /emifre/param_load_from_file ~/pixy.yaml I get the response Parameter PID_PITCH_RATE_I has new value 0.1, but nothing for ROLL_RATE_I and YAW_RATE_I.
Also, if I download the param file again with rosservice call /emifre/param_save_to_file ~/pixy.yaml the ROLL_RATE_I and YAW_RATE_I are 0 while the PITCH_RATE_I has the expected result.
Is there perhaps some bug in the configuration code of these parameters?
OS Version
Ubuntu 16.04, ROS Kinetic
git tag (master, stable, v1.0, etc..)
Current release v1.2.0
@dpkoch, could this be related to the issue that we've seen that every time we change any parameter, rosflight_io responds that the ARM_CHANNEL has a new value (even if it never changes)?
During some testing I wanted to test the response with some I term, where the
PITCH_RATE_I
is accepted, but changes toROLL_RATE_I
andYAW_RATE_I
are not recognized.When running
rosservice call /emifre/param_load_from_file ~/pixy.yaml
I get the responseParameter PID_PITCH_RATE_I has new value 0.1
, but nothing forROLL_RATE_I
andYAW_RATE_I
.Also, if I download the param file again with
rosservice call /emifre/param_save_to_file ~/pixy.yaml
theROLL_RATE_I
andYAW_RATE_I
are 0 while thePITCH_RATE_I
has the expected result.Is there perhaps some bug in the configuration code of these parameters?
OS Version
Ubuntu 16.04, ROS Kinetic
git tag (master, stable, v1.0, etc..)
Current release v1.2.0
parameter file (
rosservice call /param_save_to_file
)Compiler version (
arm-none-eabi-gcc --version
)N/A
Hardware configuration (MAV type, flight controller version, connected sensors)
NAZE based flight controller
The text was updated successfully, but these errors were encountered: