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

@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

@SHofmeester Another thing I just thought to try:: run sudo dmesg -wH and see if you see the VOXL enumerate when you plug it in to your machine

@omer You can do joystick control w/ QGroundControl

@david-moro Awesome! Glad we were able to get this resolved Thinking about it more, this makes a lot of sense. A higher resolution camera is going to be ultra-precise in its pixel-to-world mapping meaning small inaccuracies in the grid would probably cause the model to blow up. I'll make a note to make this very clear on our documentation. Don't hesitate to reach out if you have any other questions. Best of luck!! Thomas

@tom Awesome! Thank you for your fast reply! I appreciate it.

@Eric-Katzfey okey, tomorrow I will try to set up a local network with a router and I will let you know!

Apologies @vipul-kadam The forum has been finicky with me lately This is the link that was supposed to be posted. https://docs.modalai.com/sentinel-functional-description/

@tom I turned off the encryption on the modem that I can access, but I did not see any changes. I will also contact Microhard about this issue.