ArduPilot / ArduPilot/MAVProxy
MAVProxy Attribute Error
- Dominant language
- Python
- Stars
- 595
- Forks
- 773
- Avg merge
- 2d 6h
- Merged PRs (30d)
- 18
Description
Hello Tridge,
When I send a MAVLink message such as set_position_target_local_ned or rc_channels_override which have a target_system and/or target_component field, I get AttributeError: 'MPStatus' object has no attribute 'target_system. After examining the MAVProxy.py code, I see no target_system attribute in the MPStatus object. Have these attributes been deprecated in the latest version? If so, what is a suitable message to replace set_position_target_local_ned or rc_channels_override? I am using droneapi to craft the message and if I comment out the hasattr() statements in the fix_targets method of api.py, I can get by the attribute errors but the code I am using to send vx, vy and vz commands using the droneapi message_factory command and set_position_target_local_ned_encode within SITL causes the copter to oscillate back and forth wildly (pitch and roll in the console goes crazy). If you have any ideas, I would appreciate it.
Thanks,
Tim
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with MAVProxy.py to inspect MPStatus and api.py at fix_targets, then reproduce the AttributeError using the reported MAVLink messages in SITL. Check how droneapi message_factory sends set_position_target_local_ned and rc_channels_override. Done means the reported messages no longer raise the attribute error and the SITL movement commands behave as expected.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100