Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error with crazyradio2.0 #264

Closed
Kaijun101 opened this issue Jul 17, 2023 · 11 comments
Closed

Error with crazyradio2.0 #264

Kaijun101 opened this issue Jul 17, 2023 · 11 comments
Assignees

Comments

@Kaijun101
Copy link

Hi,

When I used crazyradio2, I received the error: LIBUSB_ERROR_TIMEOUT.
Can you advise on this error?

@whoenig
Copy link

whoenig commented Jul 17, 2023

FYI: We don't have a Crazyradio2 in the lab yet, so this hasn't been tested on our side.

@Kaijun101
Copy link
Author

Oh thanks a lot for the info! :)

@Kaijun101
Copy link
Author

Hi @whoenig, since now crazyradio2.0 is the de facto radio for the crazyflie system, will there be plans to support this as well?

@whoenig
Copy link

whoenig commented Jul 20, 2023

Yes of course. I think Kimberly did some brief tests and it should already work with the cflib backend. We'll order some this week and test it with the (default) cpp backend.

@Kaijun101
Copy link
Author

Kaijun101 commented Jul 21, 2023

Cool, do let me know of the outcome. I'm curious to see if there is the error mentioned above.

@whoenig whoenig self-assigned this Jul 25, 2023
@knmcguire
Copy link
Collaborator

Hi! I've kinda started an issue about this already a while ago: #245. It contains a quick and dirty fix if you are in a hurry, or else we can wait for wolfgang

@whoenig
Copy link

whoenig commented Jul 27, 2023

I have the same issue as @Kaijun101. Broadcast itself seems to work (verified by running the broadcast_example in crazyflie_link_cpp) standalone. The error comes from crazyflie_link_cpp and it looks like it might be caused by having a connection without broadcast and one with broadcasts open at the same time (which was no issue with the Crazyradio PA).

The draft PR that makes crazyflie_link_cpp examples pass is in bitcraze/crazyflie-link-cpp#35.

@e0538382
Copy link

Currently, I have also been trying to get CrazySwarm2 to work with CrazyRadio2 and face problems running the provided examples hello_world where the version of the crazyradio2 firmware is rejected. I tried to fix it by commenting out the version control block: #245. However, the same error message still pops up as seen in the log below.

May I ask if there is any alternative fix for this or did we miss any step for building the file (colcon build --symlink-install)?

[crazyflie_server-4] terminate called after throwing an instance of 'std::runtime_error'
[crazyflie_server-4] what(): Issue with connection radiobroadcast://*/80/2M. Your radio with firmware 3.2 does not support broadcast communication. Please upgrade your Crazyradio firmware!
[ERROR] [crazyflie_server-4]: process has died [pid 15020, exit code -6, cmd '/home/ryan/ros2_ws/install/crazyflie/lib/crazyflie/crazyflie_server --ros-args -r __node:=crazyflie_server --params-file /tmp/launch_params_x0cf7z3c --params-file /tmp/launch_params_jtlmd2_1'].

One more thing is that I also tried the teleop example and although no error message pops up, despite us sending in the input, the crazyflie does not seem to respond to it.

@whoenig
Copy link

whoenig commented Sep 28, 2023

Some of the submodules weren't properly updated - I just pushed a fix. Perhaps you can update (see https://imrclab.github.io/crazyswarm2/installation.html#updating) and try again? Note that you need the latest crazyradio2 firmware from https://github.com/bitcraze/crazyflie-link-cpp/files/12429056/crazyradio2-CRPA-emulation.zip (see bitcraze/crazyflie-link-cpp#37).

@e0538382
Copy link

e0538382 commented Oct 3, 2023

Thank you so much! I have managed to run the hello_world and figure8 examples after updating, will let you know if I face any other problems

@whoenig
Copy link

whoenig commented Oct 3, 2023

Great - thanks for the confirmation. I think with that we can close this issue.

@whoenig whoenig closed this as completed Oct 3, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants