@Sam-Kiley Yeah, try dpkg --force-all -i <package-name>

Hello @Rowan-Dempster ,

I am assuming that you are using non-raw preview stream (YUV) at resolution around 4000x3000 and similar resolution for the large encoded stream. Then the ROI stream is the downscaled version of the preview stream (please correct me if I am wrong).

I just tested this setup using IMX412 camera, and using the following branch (which I believe you used as a starting point):

https://gitlab.com/voxl-public/voxl-sdk/services/voxl-camera-server/-/tree/feature-add-c2d-select-roi-src/

It seems to be running just fine. Please test using the above branch and then if that works, then it's possible that you have some changes that cause an issue. Also try disabling all other cameras and seeing if the issue goes away.

| Pipe Name | bytes | wide | hgt |exp(ms)| gain | frame id |latency(ms)| fps | mbps | format | hires_roi | 1382400 | 1280 | 720 | 33.00 | 4035 | 3752 | 53.3 | 30.0 | 331.8 | NV12 | hires_large_encoded | 723 | 4056 | 3040 | 33.00 | 4035 | 3751 | 80.6 | 30.0 | 0.4 | H265 (P)

If the camera server from the above branch does not work, please provide the following details;

what camera you are using voxl-camera-server.conf config section for that camera (assuming other cameras do not interfere)

Alex

@swickliff Interesting, have you had success with this hardware setup before?

@ashwin I took a look at the Qualcomm developer site. My installation of Qualcomm Package Manager (QPM) 2.0 no longer works but they now say to use Qualcomm Software Center. So I was able to download and install v1.14.0 of that and by searching for "Hexagon" I was able to find the download link for "Qualcomm(R) Hexagon™ SDK 4.x"

@Alex-Kushleyev It's a 3rd party camera that is not supported by ModalAI.

@Moderator That's exciting, I'll be on the lookout. Thanks!

Hello @JoeAR_21 ,

The debug log shows that the transition from the sinusoidal spin-up to closed-loop (based on back-emf) control is not working. There are several safety checks to prevent a bad motor from spinning up and the checks happen during this transition.

Most likely the motor windings or leads are compromised, either one of the phases is disconnected or there may be a short between two phases.

If you have a milliohm meter, you could accurately verify the phase resistance. A disconnected phase can be verified using a regular multi-meter by checking pairwise resistance between the 3 phases (should be the same and close to zero (in the range of 200-300 mOhm), depending on the specific motor used).

While an ESC issue is also possible, however, it is less likely to occur during a crash, unless the ESC was mechanically damaged.

Alex

Hello @hgutier ,

Can you please provide output of voxl-camera-server -l, which will scan all the connected cameras? You can just list the top part, something like this (just an example). Please note that this command will stop the background camera server service, if it's running, which can be restarted using systemctl start voxl-camera-server or just rebooting voxl2.

voxl-camera-server -l DEBUG: Attempting to open the hal module DEBUG: SUCCESS: Camera module opened on attempt 0 DEBUG: ----------- Number of cameras: 3 DEBUG: Cam idx: 0, Cam slot: 0, Slave Address: 0x0020, Sensor Id: 0x0214 DEBUG: Cam idx: 1, Cam slot: 1, Slave Address: 0x0030, Sensor Id: 0x0356 DEBUG: Cam idx: 2, Cam slot: 2, Slave Address: 0x0034, Sensor Id: 0x0077

Also, please list the following contents:

ls /usr/lib/camera/*sensormodule*

We will just double check that the software is set up correctly to use the TOF module.

Thank you

Alex

Actually, can y'all provide the easiest path forward that supports just the tracking camera + hi-res front facing camera + FLIR Hadron?

That setup would be ideal

@IlkkaN
I was able to find to ubun1.0 & ubun2.0 packages (qrb5165-ubun-1-0_hlos_dev_cam-sdk-master etc). Chromatix api & parser were found under lu.um.1.2.1 -folder (apps_proc/src/vendor/qcom/proprietary/chi-cdk).
With those files I was able to parse imx412 ready-made binary (com.qti.tuned.imx412_fpv.bin) and create my own project based on that which actually work in our device (according to QC QCS8250/Spectra480 can be used to tune QBR5165).

However there is no Chromatix project under \chi-cdk\oem\qcom\tuning for neither imx412 nor imx678. Also no tuning binary for imx678 at all.
Do you have Chromatix projects for those modules and/or can you provide imx678 tuning binary?

From James (the guy who set the parameter)

feel free to increase it. Starling 2 Max has a very high power to weight ratio so I artificially calmed it down by limiting throttle

@kestrelsystemsbp Take a look at Python MPA interface: https://gitlab.com/voxl-public/voxl-sdk/core-libs/libmodal-pipe/-/tree/dev/python?ref_type=heads

@KnightHawk06 That is the source, yes.

It seems that a similar functionality has been shown in an experimental python branch: https://gitlab.com/voxl-public/voxl-sdk/utilities/voxl-mpa-tools/-/blob/pympa-experimental/tools/python/pympa-resize.py. Is this a recommended way to go about this (if so, how do I get these libraries and their C-bindings onto my voxl2) or is there an easier approach?