Looks like DroneKit needs better GPS fix or something like that - can you help me how to debug this behavior? Only thing I get from APM in this case is 'Flight mode change failed'.
I thought that DroneKit sends same commands as MissionPlanner. Can I see raw commands sent to APM from MissionPlanner and Dronekit, so I can compare betweem them?
Need to upgrade your drone? I think good tools are needed
Recommend a good soldering iron or soldering station ! Suggestions of soldering iron kits for beginners!
Lightweight design, easy to install and use, easy to remove and store, comfortable control handle, high-efficiency heating end, simple control interface. It is a favorite tool for electronic engineers and electronic maintenance enthusiasts.
It can work in DC 12-24V. OLED screen display, key temperature adjustment, external independent power supply. In DC 19V 40W state, 15 seconds temperature rise to 300 ℃.
https://sequremall.com/collections/soldering-irons/products/sq-001-mini-soldering-iron
ERROR:dronekit:Exception in message handler for HEARTBEAT. I guess it may be a problem on the jmavsim side (wrong copter type?), but I don't know. Can you help me ? Thank in advance =
and then I am a beginner in this field (I know programming in c and c ++ because I am a computer scientist) I wanted to know is it possible that I start to program controller firmware for drone directly ?
another question is there a solution to program firmware and then test them in a virtual environment (without assembling a drone each time)
Hope you're feeling well
I realized that with the drone flying using a dronekit script, logs are not being saved on the pixhawk sd card for that flight.
I was wondering if there is a way to change it to normal, which means saving logs on the sd card for further debuggings.
Any help or comment is appreciated
Thank you all
I run this command in the console
python multivehicle.py --simulation-count 2 --extra-connection udpout:localhost:9432
i received the following output :
Creating simulator (SITL) 0 SITL already Downloaded and Extracted. Ready to boot. Creating simulator (SITL) 1 SITL already Downloaded and Extracted. Ready to boot. 0: Launching SITL (['-I0', '--model', 'quad', '--home=-35.363261,149.165230,584,353']) 0: Connecting to its vehicle 1 Exception in thread Thread-1: Traceback (most recent call last): File "/usr/lib/python3.8/threading.py", line 932, in _bootstrap_inner self.run() File "/usr/lib/python3.8/threading.py", line 870, in run self._target(self._args, **self._kwargs) File "multivehicle.py", line 63, in change_sysid_target vehicle = dronekit.connect(connection_string, wait_ready=True, target_system=1) TypeError: connect() got an unexpected keyword argument 'target_system' 1: Launching SITL (['-I1', '--model', 'quad', '--home=-35.363181000000004,149.165230,584,353']) 1: Connecting to its vehicle 1 Exception in thread Thread-4: Traceback (most recent call last): File "/usr/lib/python3.8/threading.py", line 932, in _bootstrap_inner self.run() File "/usr/lib/python3.8/threading.py", line 870, in run self._target(self._args, **self._kwargs) File "multivehicle.py", line 63, in change_sysid_target vehicle = dronekit.connect(connection_string, wait_ready=True, target_system=1) TypeError: connect() got an unexpected keyword argument 'target_system' Waiting for thread... Waiting for thread... Sleeping a little to let SITLs go away... Launching SITLs Starting mavlink_hub thread Hub thread starting Attempting connect to (udpout:localhost:2345) Creating connection (tcp:127.0.0.1:5760) Creating connection (tcp:127.0.0.1:5770) Creating connection (udpout:localhost:9432) Creating connection (udpin:localhost:2345) Opening connection to tcp:127.0.0.1:5760 Opening connection to tcp:127.0.0.1:5770 Opening connection to udpout:localhost:9432 Opening connection to udpin:localhost:2345 Traceback (most recent call last): File "multivehicle.py", line 117, in <module> mav = dronekit.mavlink.MAVConnection(connection_string) AttributeError: module 'dronekit' has no attribute 'mavlink' Connection (udpout:localhost:9432) timed out Connection (udpin:localhost:2345) timed out Opening connection to udpout:localhost:9432 Opening connection to udpin:localhost:2345 Connection (udpout:localhost:9432) timed out Connection (udpin:localhost:2345) timed out Opening connection to udpout:localhost:9432 Opening connection to udpin:localhost:2345 Connection (udpout:localhost:9432) timed out Connection (udpin:localhost:2345) timed out Opening connection to udpout:localhost:9432 Opening connection to udpin:localhost:2345 Connection (udpout:localhost:9432) timed out Connection (udpin:localhost:2345) timed out Opening connection to udpout:localhost:9432 Opening connection to udpin:localhost:2345
what's the problem ?
Hello, I have problem on communication raspberry pi to pixhawk cube orange with dronekit. When I use Q_Enable_Mode=1 (VTOL Mode) and SERIAL2_BAUD=921, LOG_BACKEND_TYPE=2 SERIAL_PROTOCOL=921 these error appear on rpi 3 ;
“from dronekit import connect
vehicle connect(”/dev/ttyUSB0", wait_ready=True, baud=921600)
"
raise APIException(“mode (%s, %s) not available on mavlink definition” % (m.custom_mode, m.base_mode))
APIException: mode (11, 89) not available on mavlink definition
ERROR:dronekit:Exception in message handler for HEARTBEAT
Traceback (most recent call last):
File “/usr/local/lib/python2.7/dist-packages/dronekit/init.py”, line 1531, in notify_message_listeners
fn(self, name, msg)
File “/usr/local/lib/python2.7/dist-packages/dronekit/init.py”, line 1223, in listener
dronekit = 2.9.2
pymavlink = 2.4.9
How can I overcome this issue can you help ?
Note: It doesnt come up when Q_ENABLE = 0.
1 reply
Hello, I have been trying to run a simple dronekit code but have been running into quite a few problems. Firstly I was unable to change the flight mode using the mavproxy command line and the dronekit code but by adding a snippet in the mavutil.py file I was able to change the code in the mavproxy.py command line. Running dronekit sitl works and changes the modes but when I try to run the same code on the actual drone it give me the following error in dronekit command windows
WARNING:autopilot:Flight mode change failed
and this error in the mavproxy UI
Got COMMAND_ACK: DO_SET_MODE: UNSUPPORTED
@mh2024 I am using Arducopter 3.6.12 on my actual drone. I also tried it with 4.0.7 but that did not solve the issue either.
The reason I downgraded to 3.6.12 is because 2 years ago, this exact code worked then. I even tried downgrading dronekit, mavproxy and its dependencies but that gave other problems such as completely refusing to arm. The vehicle.armed always echoed False.
i'm using this code for GUIDED_NOGPS mode https://github.com/dronekit/dronekit-python/blob/master/examples/set_attitude_target/set_attitude_target.py
after my copter armed, instead of taking off it disarmed again
what should i do?
