Docker MAVSDK cannot find camera
We are trying to use a docker container to run a recording code that will save the Hires camera data. When we start up our code the aircraft won't see the camera on the M500. Any suggestions on how to help MAVSDK see the camera?
@Steve-Sager Are you running
@tom I am not able to turn on the voxl-streamer. I have it enabled, but the process will not run, any suggestions on how to unlock it?
@Steve-Sager What is the output of
@tom Actually, I was able to fix the problem with the voxl-streamer not running by using voxl-configure-streamer -i hires.
We are still not able to see the camera with our docker mavlink image though.
The following screen shot is what is happening...
@Steve-Sager Based on the output from
voxl-configure-streamer, it looks as though the video is on port
8900while your app seems to be looking at port
@tom the 14551 port is looking for our aircraft to run the docker, should we change that to the video port 8900?
@Steve-Sager I don't know anything about this app that you are running. Is the application itself trying to take in the video? If so, what port is it expecting the video to be on?
@tom okay so following the steps here https://docs.modalai.com/voxl-vision-px4-telemetry/ I should be able to connect to the aircraft over mavlink using a docker image that is requesting information from the mavlink server. We want to pull IMU telemetry data and hires image data to train an AI with, we are then going to use said AI to re-fly the obstacle course based on our first human pilot flight. Should we be using the port 14550 or 14551 for this?
@Steve-Sager If you're just looking to train the model you can use voxl-logger to save the hires images and then pull them off later (this would be done outside the docker)
@tom How exactly would I go about doing that with voxl-logger, step-by-step?
voxl-loggerrequires that you have camera server running so that it can pull frames from
/run/mpa/hires, then you'll follow the docs here: https://docs.modalai.com/voxl-logger/
voxl-logger --cam hiresto save frames to the
You can then pull your frames off of VOXL from that directory for training purposes.
@tom thank you for responding to my question regarding how to setup voxl-logger, we followed your instructions and recorded some data.
I noticed that the capture rate of the sensors is extremely high (around 1000+ hertz) and the video capture rate is about 30 hertz. Is there any way that we can get these data collection rates to be more synchronized? Is there a way to limit the imu frequency to ~30 hertz?
right now we are using a command that looks something like....
voxl-logger --cam hires -i imu1
I would try out the "-k" option