Closed knmcguire closed 7 months ago
Design-wise I suggest that this is an extra tool that only works if the server is not running, otherwise it's going to be very difficult to implement properly (especially for the cpp backend).
I'm not sure if this can actually work with the server running, at least on the cflib side. On the other hand.,.. I'm wondering what the added benefit of making it a particular ROS tool 🤔 It can also be something that is implemented in the cflib as a swarm flashing tool itself and then more projects can benefit.
Perhaps just the fact that there is a flashing node running, and that services can be used to indicate different crazyflies or perhaps a whole yaml file?
It would be handy to have a swarm flashing utility integrated into crazyswarm2 (also for the stablab efforts https://github.com/bitcraze/crazyflie-testing/issues/25).
Something like this we have as .sh files here or as part of the crazyflie-testing repo. However, for crazyswarm2 it might be fruitful to have this based on the crazyflie.yaml file.