@Vinny Thank you for reverting back, I will follow the steps you mentioned along with the ESD safe method.

@Alex-Kushleyev Ok great. Thanks.
One more question, to configure VIO/QVIO for a custom frame with a single (downward) camera, how should I go about following the documentations?

I am starting with https://docs.modalai.com/open-vins/

However I came across this:
"This documentaion will assume that there are some steps that have already be taken. ...Assuming that we are working with between two and three camera tracking."

are there different procedures for a system with single camera? Also a high-level roadmap on how to go about configuring VIO/QVIO for a custom frame would be appreciated in case information is in multiple places in documentation. Thank you for your support.

@Vinny Got it. Thanks!

Hi @18257581
Sometimes our newer boards are lacking in full documentation, so thanks for your patience.
We have not publicly posted our uCoax pinouts and not sure yet if we plan to. For now it is required to use our full solution which is host adapters, cables, and sensor boards.
I'll bring it to the team. But, we are unlikely to open this up since in order for us to test the components, which are very fragile, they need to be bundled together and not separated, so it would actually cost us more (costing our customers more) to test units individually for customer designs.
Only the Coax cable we sell individually and that is pinned 1:1 with all 26 conductors present unlike some of the other COTS FPV systems.

However, for JST and other cable-to-board and board-to-board connectors, yes, we need to get that listed.
The pinout on J4 of M0201 (the replacement for M0153) is in the same Dronecode inspired format we use at ModalAI for UART + I2C, but in this case since it is not UART, it is 2 GPIOS.
So,
Pin 1 = 3.3V
Pin 2 = GPIO_1 (Undefined/Unavailable/Reserved for Future Use)
Pin 3 = GPIO_2 (Undefined/Unavailable/Reserved for Future Use)
Pin 4 = GIMBAL_I2C_SDA (3.3V Logic Levels, 2.2K pull-up resistor present)
Pin 5 = GIMBAL_I2C_SCL (3.3V Logic Levels, 2.2K pull-up resistor present)
Pin 6 = GND

Thanks @aheyne for alerting us.
I had made the updates to our site and the 3D models are now there.
Let us know if you need any more help.
Thanks!

https://docs.modalai.com/pcb-catalog/

@mkriesel This cable will help if you do not already have one: https://docs.modalai.com/cable-datasheets/#mcbl-00091
Quick Edit/add: I just noticed our team never had these listed on our shopify site, so they are adding them soon! Thanks!

@Sam-Kiley , yes, every Starling 2 / MAX is going to have M0173 board installed and needs to use the option 1.

Alex

@psafi the html file is saved in the same folder where you run voxl-esc-spin* scripts if you have --enable-plot 1 . on VOXL2, the plot wont show up on screen, since there is no screen attached to VOXL2 (which would work on a linux pc), but it will be saved to html. In order to save to html, you will need to have plotly installed. You may first need to install pip3

apt update apt install python3-pip pip3 install plotly --upgrade

Alex

@Moderator got it. Thanks!

Hello All - I will be trying to recraete this issue in the coming days - will keep you all posted.

@Alex-Kushleyev ,

Thank you for the clarification!

We will change the service and see if it meets our needs.

Regards,
Jacob

@ysc , I am glad that the camera is working, but could you clarify what you changed to make it work? You should be able to get higher resolution and FPS if everything is working properly.

Also, if the logcat outout is not showing up, it is probably because the logging from camera pipeline is disabled in the following file : /vendor/etc/camera/camxoverridesettings.txt:

systemLogEnable=0

If that is set to zero, you can just comment out that parameter and try again.

Alex

@Federico-Wyrwal , thank you for the reply. More debugging would be needed to figure out the root cause and it looks like you already submitted an RMA for the inspection / repair, so we will take care of it. Thank you.

Alex

Yes, Hadron is working when plugged into J6 of VOXL2 Mini with default kernel.

You just need to have the following sensormodule files in /usr/lib/camera/:

com.qti.sensormodule.boson_0.bin com.qti.sensormodule.ov64b40_1.bin

And instead of gpio6, you need to use gpio30 to enable the CCI mux, so that communication with the EO camera is enabled:

voxl-gpio -m 30 out voxl-gpio -w 30 1

I will update the Hadron documentation..

Alex

Detections is pertinent to voxl-tflite-server and onboard computer vision on yolo, NOT on april tags.

Hi @VictorG
Our team went back and quarantined all units again and we have some working.
I'll request they get shipped today, otherwise very soon!!
Again apologies for all the delays, distractions, and stress on this!!
Thanks for your patience.

If anyone is struggling to find the pMDDL2450 info that arrives with the Starling 2 Max + Microhard option (mine didn't come with any documentation) here is the RF configuration. By default the Max arrived with the radio turned off. I have paired mine with a pMDDL2450-ENC module connected to a laptop running QGround / MissionPlanner.

One way to access the settings without having an external radio module to pair is ssh port forwarding. Make sure you're connected to the drone / have setup your VOXL WIFI settings then ssh into the VOXL using ssh -L 8443:192.168.168.1:443 root@192.168.8.1

You can then access the microhard landing page at https://localhost:8443

My pMDDL2450 has the following default settings for the radio:

c59d1c08-fd0f-4ce9-b40e-ec413952ce4d-image.png

@Moderator Hi I'm just trying to find a good way to deploy to multiple devices via a "golden image" type setup. Is there a way to do that. Should I just follow the rules for the custom kernel instructions and add a custom bitbake layer onto that?