Control configuration changes not reflected on drone? about ardrone_autonomy HOT 2 CLOSED

Thanks for debugging this issue @mikehamer . I personally found this issue a couple of month ago, but I have not looked into it with details.

Regarding the "ARDrone SDK 2 Developers Guide" (Multiconfiguration) Section (in addition to what you said), there are four types of configurations:

• CAT_COMMON : This is the default category, common to all applications.
• CAT_APPLI : This setting will be saved for the current application (regardless of the
device it is running on).
• CAT_USER : This setting will be saved for the current user (regardless of the application).
For more information about users, see the user section of this documentation. (User cate-
gory is also called "profile" category).
• CAT_SESSION : This setting will be saved for the current flight session (regardless of
application/user).

First time that I implemented the rosparam based configuration, I did not pay attention to this fact and considered all params CAT_COMMON.

This is my suggested roadmap to fix this problem:

1. Group all configurations used by the driver into above categories.
2. Find the problems for each group.

This is what have been found so-far:

• I think that "CAT_SESSION" configuration should be sent to the Drone after initialization, I am not sure if they are applied correctly now.
• As you found out, "CAT_USER" configuration is not being applied at all.
• I think "CAT_COMMON" is OK.
• I think (with less confidence) that "CAT_APPLI" is OK as well.

from ardrone_autonomy.

Fixed in my pull-request #26

from ardrone_autonomy.