Replies: 2 comments 3 replies
-
|
This usually indicates that the communication to the CF(s) doesn't work. Could you provide the content of |
Beta Was this translation helpful? Give feedback.
-
|
Thank you so much for the quick response. We also suspected that it was the connection with the CF that was the problem. Therefore changed to the 2M bandwidth instead of the 250K aswell as updated the CF. We are currently only running one CF with the URI E7E7E7E701. Only drone 1 is selected in chooser.py and as we said before we managed to get battery level from chooser.py. But we are still having the timeout problem. Below is the crazyflies.yaml. here is the crazyflies.yaml `crazyflies:
|
Beta Was this translation helpful? Give feedback.
-
|
Hello again! small update, we tried with a brand new flashed crazyflie 2.1 instead of the 2.0 we used before. However we still have the same problems as before. |
Beta Was this translation helpful? Give feedback.
-
|
What is your full URI? The Crazyswarm only supports the 2M bandwidth. Once you have the URI, you can also try the crazyflie_tools, e.g., |
Beta Was this translation helpful? Give feedback.
-
|
It works! |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi,
We are having problems when trying to launch hover_swarm.launch. We are using qualisys with libobjecttracker and we can read our position when launching mocap_helper. When using chooser.py we can see the battery level and reboot the drone successfully. Therefore we assume that we have a connection to the drone as well as the motion capture system. Both the crazy radio and the drone is running the latest software. Below is the output from the terminal when running hover_swarm.launch.
We saw that someone had the same issue but it was not resolved, do you know what is causing the error or do you have any suggestions on how to trouble shoot the problem?
It would be greatly appreciated!
`fs-as2@fsas2-HP-ProBook-640-G1:~/tsfs12/crazyswarm$ roslaunch crazyswarm hover_swarm.launch
... logging to /home/fs-as2/.ros/log/7ba8b3e2-3c84-11ec-8e10-c4d9879035e4/roslaunch-fsas2-HP-ProBook-640-G1-6543.log
Checking log directory for disk usage. This may take a while.
Press Ctrl-C to interrupt
Done checking log file disk usage. Usage is <1GB.
started roslaunch server http://fsas2-HP-ProBook-640-G1:45421/
SUMMARY
PARAMETERS
NODES
/
crazyswarm_server (crazyswarm/crazyswarm_server)
crazyswarm_teleop (crazyswarm/crazyswarm_teleop)
rviz (rviz/rviz)
auto-starting new master
process[master]: started with pid [6553]
ROS_MASTER_URI=http://localhost:11311
setting /run_id to 7ba8b3e2-3c84-11ec-8e10-c4d9879035e4
process[rosout-1]: started with pid [6564]
started core service [/rosout]
process[crazyswarm_server-2]: started with pid [6571]
process[crazyswarm_teleop-3]: started with pid [6572]
process[rviz-4]: started with pid [6573]
[ INFO] [1635930025.914287983]: Wait for services...
[ INFO] [1635930025.915857611]: waitForService: Service [/emergency] has not been advertised, waiting...
[ INFO] [1635930025.977977100]: waitForService: Service [/emergency] is now available.
[ INFO] [1635930025.979879489]: Manager ready.
ch: 1
terminate called after throwing an instance of 'std::runtime_error'
what(): timeout
[crazyswarm_server-2] process has died [pid 6571, exit code -6, cmd /home/fs-as2/tsfs12/crazyswarm/ros_ws/devel/lib/crazyswarm/crazyswarm_server __name:=crazyswarm_server __log:=/home/fs-as2/.ros/log/7ba8b3e2-3c84-11ec-8e10-c4d9879035e4/crazyswarm_server-2.log].
log file: /home/fs-as2/.ros/log/7ba8b3e2-3c84-11ec-8e10-c4d9879035e4/crazyswarm_server-2*.log
[rviz-4] process has finished cleanly
log file: /home/fs-as2/.ros/log/7ba8b3e2-3c84-11ec-8e10-c4d9879035e4/rviz-4*.log
^C[crazyswarm_teleop-3] killing on exit
[rosout-1] killing on exit
[master] killing on exit
shutting down processing monitor...
... shutting down processing monitor complete
done
`
Beta Was this translation helpful? Give feedback.
All reactions