Timeout error when setting a parameter

[wsilva32]

When I try to set a parameter (for example RC1_TRIM) in my python script I receive the following message after a 2 second delay:

timeout setting RC1_TRIM to 1500.000000

However, when I check the value in MAVProxy the value has been set correctly. I found that this message is generated by mavset() in mavparm.py in pymavlink, so perhaps it is a bug there. For now I have commented out these lines (24-35) in mavparm.py to avoid having to wait 2 seconds for each parameter set.

[themfx]

Hi, I'm having the same issue at the moment. Did you have any luck solving it?

I am trying to limit the throttle (using v.parameter['THR_MAX'] = 0). This gives the same timeout error as you've written, although it does actually change THR_MAX to 0. However, future identical commands do not work (e.g. setting THR_MAX back to 100) - the code just hangs when you ask it to make the change.

[hamishwillee]

@mrpollo I am assigning this to you. I detected the same problem when attempting to get parameter-change notification in #78

[tcr3dr]

I investigated the issue. I'm almost positive this is caused by race conditions caused by threading. Spin-waiting on two separate threads for parameter confirmation causes a lot of "BAD DATA" messages to pop out nondeterministically.

A fix for this is targeted for the next major DKPY release, which should fix our threading situation.

[tcr3dr]

Once this is fixed, test_12.py should be improved with the relevant asserts.

[hamishwillee]

This is fixed in DKPY2 - tested on 2.0.0b5