@José-Quintanilla WP7610 or RC7611 should work for you

@Moodsh00 Were you able to successfully attach and configure the additional payload? Can you also share which gimbal did you attach? I am also in the phase of attaching a ~900g Gimbal to the Sentinel and I'm trying to see if that's possible.

@Amisha-Bhaskar However, it won't revert to 0 if you change it. The parameters that you update are saved in the file /data/px4/param/parameters. Do you have that file in your filesystem?

@elfowl currently, we have to use a proprietary Qualcomm toolchain to generate camera binaries... we would need to add this setting. Our goal is to open up this area such that we can all customize as needed but we don't have this functionality yet. The framework we are using is in general setup for phone manufactures to add a sensor or two to a phone to known locations, so we are kind of hacking it to allow folks to add numerous types to up to 6 locations, which involves removing some onion layers

@bgaudel said in Stereo camera and UVC server compatiability: 2b03:f781 Here are the instructions for how to use voxl-uvc-server. Make sure you are correctly specifying the resolution and frame rate. The Stereolabs ZED doesn't output 640x480 30fps. https://docs.modalai.com/voxl-uvc-server/

@Dongoo-Lee The code is open source. You are free to modify it to do whatever you want. https://gitlab.com/voxl-public/voxl-sdk/services/voxl-streamer

Any rough guidance here would be great. As you can see in the related posts there are quite a few others interested in this.

We figured it out, the answer is explained in this reply to another question: https://forum.modalai.com/post/9575

@modaltb Hey, thanks for the quick reply. Unfortunately, none of these work for us since it seems exposing one port prevents us from accessing another (I also can't find a ref to buy the M0130). We found a workaround by having a USB hub on the m0125 instead of going over the native uart.

@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.

@Praveen We provide the docker image so that you do not have to build it. It is just a tool that is needed to build some of our software packages. As long as it is doing that then there is no need to update it.

@Maxim-Temp hi, I'm facing the same issue, did you manage to solve this?

Hello @Kashish-Garg-0 we have a curve that is "motor voltage vs rpm", meaning that for a desired RPM, it tells the ESC what average motor voltage should be applied. The average motor voltage is defined as battery_voltage * motor_pmw_duty_cycle. The battery voltage in this curve is in millivolts. Since you are typically controlling the desired RPM, as a user you do not need to worry about what "throttle" or voltage to apply - the ESC does this automatically in order to achieve the desired RPM. this calibration curve is used as a feed-forward term in the RPM controller. The ESC does support an "open loop" type of control where you specify the power from 0 to 100%, which is similar to a standard ESC, but PX4 does not use that ESC control mode. By the way, you can test the ESC directly (not using PX4) using our voxl-esc tools (https://gitlab.com/voxl-public/voxl-sdk/utilities/voxl-esc/-/tree/master/voxl-esc-tools) which works directly on VOXL2 or a standalone linux PC (or mac). voxl-esc-spin.py has a --power argument where you specify the power from 0 to 100, which translates directly to the average duty cycle applied to the motor. Here is the calibration for the Starling V2 motor / propeller that we use: https://gitlab.com/voxl-public/voxl-sdk/utilities/voxl-esc/-/blob/master/voxl-esc-params/mavic_mini_2/mavic_mini_2.xml?ref_type=heads#L63 Also, you can take a look at this post to see how to interpret those parameters a0, a1, a2 : https://forum.modalai.com/topic/2522/esc-calibration/2 We also have some dyno tests for this motor / propeller : https://gitlab.com/voxl-public/flight-core-px4/dyno_data/-/blob/master/data/mavic_mini2_timing_test/mavic_mini2_modal_esc_pusher_7.4V_timing0.csv . We are not sure how accurate that is, but it can be used as a starting point. @James-Strawson can you please confirm that is the correct dyno data for the Starling V2 motors? Alex

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

@majjam Okay, so I'm guessing that you are using 0.9.5 then? The only known issue with those Holybro GPS units was the baudrate thing. Some units are not set at 115200 so the command to start the gps with that baudrate will fail on units with a different baudrate setting. Changing the start line to remove the forced 115200 and let the driver choose the correct baudrate on it's own was the resolution of that issue. Beyond that we are not aware of any other issues. Can you verify that the M8N unit is working on another platform? Can you use an oscilloscope on the M8N UART TX line and see any activity?

@Vinny @wilkinsaf Thank you for your responses. This clarifies a lot of my questions.