8000 Crazyswarm not publishing data to all (/cf#/pose) pose messages · Issue #397 · USC-ACTLab/crazyswarm · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Crazyswarm not publishing data to all (/cf#/pose) pose messages #397

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

Open
sabdi1 opened this issue Jun 22, 2021 · 5 comments
Open

Crazyswarm not publishing data to all (/cf#/pose) pose messages #397

sabdi1 opened this issue Jun 22, 2021 · 5 comments

Comments

@sabdi1
Copy link
sabdi1 commented Jun 22, 2021

Hello,

Currently when I run Crazyswarm using the Loco Positioning System, crazyswarm only publishes data to the ROS topics for the last two crazyflies. For example, if I've selected crazyflie 1,3,and 4 via chooser.py, the pose messages that are being published are /cf3/pose and /cf4/pose. The topics for the pose messages for the other crazyflies are visible via rostopic list, data is just not being published to them.

Is there somewhere in the launch file or elsewhere where I may have accidentally set a restriction on the number of crazyflies or the messages to be published?

Thanks,

@whoenig
Copy link
Contributor
whoenig commented Jun 24, 2021

There is no intentional restriction that I am aware of. However, the bandwidth is rather limited. Could you try changing the update from 10 to 100 in https://github.com/USC-ACTLab/crazyswarm/blob/master/ros_ws/src/crazyswarm/src/crazyswarm_server.cpp#L662? At the same time, you may also try reducing the ping time to 1ms in https://github.com/USC-ACTLab/crazyswarm/blob/master/ros_ws/src/crazyswarm/src/crazyswarm_server.cpp#L1016.

Are all your CFs using the same radio (i.e., are they on the same channel). It might be an option to use two radios (and thus, 2 channels) instead.

@sabdi1
Copy link
Author
sabdi1 commented Jun 30, 2021

Hello I made the recommended alterations to the code and found that when I ran 4 cfs, 3 had their poses published and when I ran 8, 2 cfs had their poses published.

Yes, as of right now, all cfs are using the same radio. Ideally, I'd fly all 10 cfs with the same radio. My understanding was that Crayswarm had the capability to fly up to 15 cfs per radio, hence the 45 drone display with 3 Crazyradios. Is there a separate repository with variables preset that allow for that shown capability?

@whoenig
Copy link
Contributor
whoenig commented Jun 30, 2021

The 15 CFs per radio are for broadcast communication only; the demonstration uses the code in this repository (although in an older version). You are using point-to-point communication, which requires a significantly higher bandwidth. We didn't do much testing for this mode and the Crazyswarm is not yet optimized for it, i.e., the scheduler is not fair, but my guess is that you can have around 4 CFs per radio, depending on the frequency etc. I am working on moving to crazyflie-link-cpp under-the-hood, which will resolve the scheduling problems (I have no concrete timeline for this, though). The new scheduler should avoid issues you are seeing, that some CFs do not receive any data.

@uhvardhan
Copy link

Hello,

I was wondering if you were able to find a solution for this. I want to control 8 CFs using 3 different radios. Let's say:
CFs 1,2,3 -> Channel 120
CFs 4,5,6 -> Channel 110
CFs 7,8 -> Channel 100
I am currently using Loco Positioning System, so I would like to save the poses of all CFs in a bag file. This should theoretically work right - as in I should be able to do it?

@sabdi1
Copy link
Author
sabdi1 commented Feb 2, 2022

I don't see why not. As long as you've enabled logging in the launch file, have enough radios, and have the allCrazyflies.yaml set properly, I don't see a reason this wouldn't be possible.

jpreiss pushed a commit to jpreiss/crazyswarm that referenced this issue Mar 16, 2024
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

3 participants
0