I am working on support in AirSim DroneServer for DJI flight controllers that use the Onboard-SDK (Linux only) which includes N3,A3 and most Matrice series (Compatibility)
Here is the work-in-progress master branch on GitHub (working project codename "Rosie")
I have basic RPC Multi-rotor API functionality working and a new version of DroneServer that takes into account the differences in startup for DJI Onboard-SDK compared to PX4.
Supported RPC commands include takeoff, land, movetoposition,path,rotate,etc. Video is not supported yet and I do not have the hardware to test it.
I am just starting on the Unreal simulation support but it appears that the simulation model is quite different.
I have some questions about what it will take to work towards a PR of such magnitude.
Is Linux-only support for DJI Onboard-SDK a non-starter for eventually merging to the master for AirSim? Because DJI Onboard SDK only supports Linux I created a new project with AirSim as a submodule instead of working inside of AirSim fork. I can work towards reintegrating the multi-rotor implementation back into the fork if this would be allowed.
Is it acceptable to submit PR to merge a multi-rotor implementation to AirSim branch that supports RPC client-server (DroneServer) without supporting Unreal-Unity simulation? If a branch in the main repo could be used for work-in-progress it might be more prominent for drumming up contributions/testing.
This issue has been automatically marked as stale because it has not had activity from the community in the last year. It will be closed if no further activity occurs within 20 days.
I am working on support in AirSim DroneServer for DJI flight controllers that use the Onboard-SDK (Linux only) which includes N3,A3 and most Matrice series (Compatibility)
Here is the work-in-progress master branch on GitHub (working project codename "Rosie")
AirSim-Onboard
Please let me know if you have any feedback.
I have basic RPC Multi-rotor API functionality working and a new version of DroneServer that takes into account the differences in startup for DJI Onboard-SDK compared to PX4.
Supported RPC commands include takeoff, land, movetoposition,path,rotate,etc. Video is not supported yet and I do not have the hardware to test it.
I am just starting on the Unreal simulation support but it appears that the simulation model is quite different.
I have some questions about what it will take to work towards a PR of such magnitude.
Is Linux-only support for DJI Onboard-SDK a non-starter for eventually merging to the master for AirSim? Because DJI Onboard SDK only supports Linux I created a new project with AirSim as a submodule instead of working inside of AirSim fork. I can work towards reintegrating the multi-rotor implementation back into the fork if this would be allowed.
Is it acceptable to submit PR to merge a multi-rotor implementation to AirSim branch that supports RPC client-server (DroneServer) without supporting Unreal-Unity simulation? If a branch in the main repo could be used for work-in-progress it might be more prominent for drumming up contributions/testing.
Thanks