-
Notifications
You must be signed in to change notification settings - Fork 371
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
Waypoint following via ros2 #242
Comments
Hello @Astik-2002 the first thing I would flag as potentially challenging going from fly.py to a publisher/subscriber implementation is that the first one is in lock-step (time is explicitly advanced for both the sim and the controller) while the second might have fall out of synch depending on how your threading and ros2 executor are set up. |
Hi @JacopoPan. I was able to get some sort of path following, but the UAV still crashes after following the paths. I tried tuning the PID, and the results are 'workable' in fly.py, but not with ros2. My final goal is to get it to follow a path generate via rrt* algorithm to avoid obstacles. An example of such a path is this: Can you share how to fix to out-of-sync issue in path following? |
tbh, I'd try to run the simulation in lockstep with the controller with a service/client implementation rather than using publisher/subscriber topics |
Hello @JacopoPan Can you share if there's a way to generate a 360degree point cloud in gym-pybullet-drones? I'm currently using the depth image and camera intrinsic to generate the pcd, but I have a limited 60degree fov only. I tried generating multiple view and projection matrices in baseaviary for each direction (front-back, left and right), but cannot figure out how to stich them to generate a panoramic pcd. |
Hi @Astik-2002 I have never done that myself but you can look at the Bullet discussion forums directly to find attempts to address the same issue bulletphysics/bullet3#4040 |
Hello @JacopoPan corridor_finder_planner2.mp4There's still huge tracking error between UAV trajectory (red) and desired path (green). Rn, the simulation stepping and control both are in the same ros node (my code can be seen here). Can you share how to fix this? I tried on native fly.py, and the performance is same, meaning this is no longer a synchronization issue (I think). Thanks |
Hi @Astik-2002 the camera view is defined here gym-pybullet-drones/gym_pybullet_drones/envs/BaseAviary.py Lines 180 to 181 in 3d7b12e
You can dynamically adjust it following to the PyBullet docs in the .step() methods, if you desire
For the tracking performance, I can't see the video but have you considered tuning the PID gains (assuming you are using gym-pybullet-drones/gym_pybullet_drones/control/DSLPIDControl.py Lines 37 to 43 in 3d7b12e
|
Hello. In this code, I'm trying to get the uav to hover at a waypoint ( [0.1,-0.3,0.5] ) via the computecontrolfromstate function
The UAV just flips whenever I try to run the code. however, if the waypoints are given according to the fly.py example (travel in a circle) or if the uav is made to hover at init point at a different height, it doen't flip. What's the reason for this?
The text was updated successfully, but these errors were encountered: