Topics created by hmlow

@hmlow we're still working through the product details of what should be included in the kit. We will try to get something into beta this week

@Alex-Kushleyev I'll glue it back in place myself. Thanks!

@Eric-Katzfey said in Starling infinite loop switching between Position and Manual mode:

And if you start voxl-camera-server and then put it into position mode is that okay?
Not immediately. The longer the system was in the endlessly switching state the longer it takes for it to recover even after voxl-camera-server is started. Can be in the order of minutes.

My guess is that you stopped voxl-camera-server but not some of the other services that depend on it like voxl-qvio-server, voxl-vision-hub, etc. and so they are sending erroneous data to px4 which confuses it.
During this weird behavior I have attempted to turn off all other services that might be doing this, which includes the 2 that you have mentioned. The only exception is voxl-mavlink-server which obviously I can't turn it off but after restarting it, it's still weird behavior is still present.

You are, obviously, trying some non-standard stuff here.
Yes I do understand that. I'm just wondering why it appears only when the WiFi interface is used for communication and not when cellular 5G is used...

Also, with respect to the RC, make sure you set RC=EXTERNAL in /etc/modalai/voxl-px4.conf so that the RC drivers are not started needlessly.
Ok will do so thanks

@hmlow I was flying over the weekend, and saw some inconsistencies as well tbh. The quality of the QVIO was reporting not as high as it was in version 0.9.5 SDK release. I will ask the devs and see what they say.
First, I need to compile some logs from voxl-qvio.

@Eric-Katzfey

Thanks for the clarification!

The source code in voxl-streamer where the gstreamer elements are configured is here. You could likely modify the code to achieve what you are looking for

Google found this Stack Overflow topic, there may be better resources out there as well

@swickliff No, it hasn't. Supposedly all of this is fixed in latest mainline but we haven't tested it. But we do have a mainline build available to try: http://voxl-packages.modalai.com/dists/qrb5165/dev/binary-arm64/voxl-mainline-px4_1.16.0-1.0.0-202502271326_arm64.deb

@Eric-Katzfey It work! Thank you!

@Thomas-Patton thanks for looking into this.

The random crash that I described in my second message in this thread is not related to the OS on which I run putty on. The crash happens on the VOXL2, sometimes even before I SSH in.

@Eric-Katzfey thanks for the 2 fixes in a single package! Will try it out and report back tmr

@Alex-Kushleyev sounds good. thanks

@hmlow Glad it worked! For future reference, the imx214_flip driver should be available internally from SDK 1.1 (system image 1.7) onwards. Rather than downloading from the above links, after SDK 1.1 is released the procedure will be as follows:

rm /usr/lib/camera/com.qti.sensormodule.imx214_3.bin cp /usr/share/modalai/chi-cdk/imx214-flip/com.qti.sensormodule.imx214_flip_3.bin /usr/lib/camera

Hello @hmlow, have you been able to solve this issue? or are you still facing similar issues with the camera-server with sdk 1.0?

The code where quality is computed can be found here: https://gitlab.com/voxl-public/voxl-sdk/services/voxl-qvio-server/-/blob/master/server/quality.h

We're sorry if that happened. Someone from operations will reach out

@hmlow ,

I know your post was a while ago.. But I wanted to add some detail.

Going to 15Hz is going to reduce the maximum exposure (duration of emitted IR signal) to about 1/3 of the maximum which would be for 5Hz. This is due to the fact that maximum power output remains the same and increasing FPS means less power is emitted during each frame. Longer exposure / IR pulse means the sensor can achieve higher signal to noise ratio and pick up returns at longer distances.

So that would make sense that you may see less phantom obstacles at 15hz compared to 5hz, if these obstacles are indeed coming from multi-path returns (weaker / shorter IR signal has less chance of being picked up by the sensor)

@Vinny Great!
So happy to hear about that. Looking forwards to its availability on store soon.

Warm regards,
Jyothish.