@Chad-Sweet Thanks for your support!

We do not have any digital zoom implementation, sorry It sounds like something that would be straightforward to build using opencv

@Eloi Hi Eloi, We only support B key on that design and do not support any plug in adapters like your link. There is strong certainty that it will not work. B key vs A/E key is not just a pin block difference, but several electrical differences exist as well (voltage settings and port options). B key is largely defined for modem devices which run on 1S "vbat" and A/E key devices largely for WiFi or I/O devices which run at 3.3V.

Thank you for the help! Will update this post when we are finished testing.

Hi, I believe that voxl-streamer will attempt to stream the hires camera by defualt, if you'd like to stream a different camera, you can change this by modifying /etc/modalai/voxl-streamer.conf and change which configuration is used (or through the command line at runtime)

@Sem-Andeweg We're taking a look. I think the "t:" is missing from https://gitlab.com/voxl-public/voxl-sdk/services/voxl-uvc-server/-/blob/dev/src/main.c#L224

@Henry-Cappel let me send an email to kick things off

@Chad-Sweet My region operating bands in India are 4,30 and 1. All these bands match with modem since I was using the modem since past few months successfully. All of sudden it has stopped working. What inference can we derive from above logs? My region code are getting fetched correctly but registration isn't happening for Sim cards. I have tried multiple sim cards as well but no success. Can it be hardware issue? Is there any way to factory reset modem? How to debug this further?

@tangotoo Awesome, thanks for the feedback.

There is no standard pin-out for MIPI-CSI. It is specific to the PCB design. It is not possible to use 3rd party modules unless they are designed specifically to be compatible. Is there a specific sensor or characteristic you are looking for? We can use that information for future roadmap considerations.

No flow control.... really just need GND, Rx, Tx

@Alex-Kushleyev Thank you for your reply. I used MSU-M0026-1-01. When changing to Green-ish, the gain becomes 69 (sorry, no snapshot). I have a few other snapshots. [image: 1662688247773-786fdb6c-da16-4177-a18b-147b99df3493-image.png] [image: 1662688265282-7b8f9d28-eba0-4764-b840-f295ceae19c1-image.png]

Perfect thank you! I have the sensor up and running.

We can specify which stereo camera should be calibrated using, 'voxl-calibrate-camera stereo_front -s 6x8 -l 0.038'

We do not have any experience at this point with Microhard's meshing algorithm. You could reach out to Microhard?

Hi Andrew, This is great info, thanks for clarifying. Unfortunately, our current product offerings do not support the "Pixhawk" style APM ADC inputs for current and voltage monitoring. However, I would bet that you could find source code for an Arduino or STM project where these ADC values have been converted to appropriate PX4 I2C digital formats that you can then feed into our products. Keep in mind, the I2C bus needs to be at 5V and you should provide the I2C pullups on your converter module (anything from 10K to 4.7K works well for our I2C translator). Thanks! Vinny

By default on all M0090 variants, all the transceiver/buffer circuits which take the 1.8V Kernel Debug UART to 3.3V TTL for J6 are DNI'd (not populated). The only thing that can be done is to probe on raw circuit pad locations for TX and RX to get the signals at a 1.8V level. Here are those snapshots to help guide you should you wish to pursue that route: [image: 1658427255298-637f7086-e575-4be7-a94f-4eaea8658da8-image.png] However, the ICs are located on the bottom side of the PCB, so when mated with Voxl2, you cannot probe directly, which would require soldering on wires to the PCB pads. That would likely violate any warranties on this specific PCB if you did that. [image: 1658427443052-0049d0fe-caea-4884-8da0-2364d45c2302-image.png]

Hello @DarkKnightCH , the mixer file does not only define the AUX1 and AUX2. Please note this line, which specify the configuration of a quadrotor in X orientation : https://github.com/modalai/px4-firmware/blob/1.11.3/ROMFS/px4fmu_common/mixers/quad_x.main.mix#L1 , specifically R: 4x

@Alex-Kushleyev When using RPM control, the mapping between thrust and RPM is usually an almost perfect quadratic, so you should probably use THR_MDL_FAC = 1 to make it quadratic. However, let me double check that last point.. The value of this parameter should not change when you change motor / propeller, since thrust is almost always a pure quadratic vs rpm. Hi @Alex-Kushleyev , did you manage to find out if THR_MDL_FAC should be set to 1 or should i calibrate the thrust curve? PX4's docs specified in https://docs.px4.io/v1.12/en/config_mc/pid_tuning_guide_multicopter_basic.html that if the ESC is a RPM-controlled one, no tuning is required: For PWM controllers, 0.3 is a good default (which may benefit from further tuning). For RPM-based controllers, use 1 (no further tuning is required as these have a quadratic thrust curve). But i noticed from ModalAI's reference params (eg Seeker's https://gitlab.com/voxl-public/flight-core-px4/px4-parameters/-/blob/master/platforms/v1.12/Seeker/Seeker_v1_param_rev_A.params) that the you guys did a calibration regardless # Dyno test shows this model should be 0.90 1 1 THR_MDL_FAC 0.90 9

@Chad-Sweet Ok thanks for your time.