If you could run camera server manually with additional debug prints (i.e. voxl-camera-server -d 0) and paste the output here, you'll be able to see more info about whats going on that'll make it easier to debug

@Eric-Katzfey yep it worked! Thanks for the quick reply.

@Alex-Gardner thank you very much

@Chad-Sweet Thanks Chad, and I will double-check the detail with OmniVision then.

Hi James,
Thank you for your help!
I am yet to inspect the VOXL flight deck for the connectors.
I would like to test out the new branch.

Thanks and regards,
Mohammed Naveed

Hi Jeff,

There's not so much a minimum height as a minimum amount for it to see. If you look at our seeker platform, the tracking camera is only 3cm above the ground, but to compensate for this the drone sits leaning back so that the camera is angled slightly upward when it's landed. If your drone sits on the body and the camera is facing down, you won't be able to take off with VIO, so you'll need to find some combination of height off the ground and angle that allows the camera to see a decent amount of its field of view in order to take off successfully.

@Eric-Katzfey Got it working about 50% of the time. It seems like most of the time it is just the uvc server trying to connect. I am going to see if I can create a service file around it. Maybe restarting on fail will get it to work with a bit of delay in between.

A bandaid for the issue, but at least it will work

@RichieRich , It's great to know about it. Thanks!

I will then try to update to see how it goes 😉

@RichieRich ,
I may find an issue with one of the batteries (the blue one in the above pic). I was trying to charge it with 4S 14.8v, 3.3A settings, but the charger tells that the blue one is recognized as only 3S and breaks the charging every time. It's quite weird why the charger tests the battery as a 3S setting. The green one works well, and no CPU error happened after fully charging.

So, I think I may have to contact the battery provider to double-check the quality of the blue one. Since the blue one cannot charge at the time, I may not be able to test this error with logs. I will get back if the battery provider could advise me how to charge it.

Hi @RichieRich , I fixed the issue as I disordered the instruction. Anyways, thanks so much 😉

@Matt-Turi thanks so much!

Thanks! I think there was some confusion about which connector to plug into, but that clarifies it. Also, any reason why the RB5 ships with a different antenna type than the VOXL?

@Eric-Katzfey Thanks, all right I will have a look at it then.

I believe you should just be able to clone boost and perform a make install inside the docker. You can then save the state of that docker so you don't need to repeat that step later.

@czarsimon omx has a very limited set of input formats. I would add format NV12 (or NV21) to your caps filter in between videotestsrc and omx.

@JoeC Seems like it is an SD card issue. I was able to recreate the problem when using a SanDisk Extreme 32GB card. But when using a SanDisk Ultra 16GB card everything works fine.

@James-Strawson thanks for the suggestions!

Hi @mohammednaveed ,
It seems I couldn't access the log of the crash anymore, because I didn't put sdcard to save the log. I also updated the firmware after the crash, so the previous logs were wiped out. Anyways, I will share the log next time if I get crash again. Thanks.

Hi @mohammednaveed ,
I tried clicking on refresh, but nothing happened. Anyways, I already updated the firmware and put sdcard in. So, I will not miss out on the logs again. Thanks.