ModalAI Forum

@Aaky After that much use it could very well be ESD damage. It seems unlikely we would be able to fix via RMA.

@Alex-Kushleyev Can you please look into this or tag someone who can help me solving this type of networking related issue?

@Alex-Kushleyev Thanks for detailed information and analysis. I am going ahead with further testing with this ESC as per your suggestion. I have changed my propulsion system as follows: Emax Eco II seroes 2306 2400kv motor, propeller Gemfan 5177 and 15000 mah 4S battery. Here is my file with ESC calibration : https://drive.google.com/file/d/1uzbx9MGwF1EvRqJx6tXBqqc-j3XZSgu_/view?usp=sharing All the motor directions are checked and they are correct as per airframe reference. My UAV is able to takeoff a bit but at around 0.5 meters it again decreases its altitude and then after scratching the surface is flipping over. Here is the logs : https://review.px4.io/plot_app?log=08691d7d-887d-41d8-b00d-d543febeea59 Can you spot is my ESC configuration wrong or anything I am missing in PX4 configuration? This flip happened twice in a row and all motor direction are verified to be correct since UAV is able to takeoff. Also any advantage of RPM vs PWM control in VOXL ESC PX4 parameter setup? Also my voxl2 is unpside down so I have set ROLL_180 in Autopilot orientation, but is this creating some problem anywhere is unknown since I can see yaw reset EKF2 estimator flag set as soon as I takeoff.

Hello @Aaky , If you have a new motor / prop, please follow these instructions for initial tuning : https://gitlab.com/voxl-public/voxl-sdk/utilities/voxl-esc/-/blob/master/voxl-esc-tools/calibration.md?ref_type=heads We don't have this specific motor / propeller combo, but if you send a link where I can purchase these, I would be happy to do a tuning pass and some testing for you. Alex

@Aaky voxl-tflite-server is a wrapper for TensorFlow Lite. So, anything you can get to work in standard TensorFlow Lite you should be able to get working in voxl-tflite-server https://ai.google.dev/edge/litert

@Aaky great to hear, from my experience when the board is booting directly to fastboot it is often a power issue

@tonygurney , yes. Please see the comment about pin availability and pin numbers here : https://gitlab.com/voxl-public/voxl-sdk/utilities/voxl-esc/-/blob/master/voxl-esc-tools/voxl-esc-pwm.py?ref_type=heads#L17 Please note that running voxl-esc-pwm.py script will use the serial port and cannot be done concurrently with PX4. This is a standalone tool, unlike voxl-send-esc-pwm-cmd tool, which sends a message to voxl-px4 and the pwm control message is then forwarded to the ESC by the voxl_esc px4 driver. Alex

@modaltb I also want to check the stock availability of new TOF sensor over here. Is this TOF camera available for shipping currently? I cant see that on website so wanted to check with you.

@Aaky Should be fine. I fly with actual RC in HITL all the time.

@Aaky, I see what you are asking. What is needed is the python binding to the C function int pipe_server_get_num_clients(int ch) , which is defined here pympa_create_pub already is set up to return the MPA channel number, so we would just need to use that channel number of checking the number of clients. I can implement this, but it will need to wait a few days. That is a good feature to have. If you would like to try implementing it yourself, you can add the bindings to : https://gitlab.com/voxl-public/voxl-sdk/utilities/voxl-mpa-tools/-/blob/pympa-experimental/tools/pympa.cpp (add call to pipe_server_get_num_clients) in a similar way how other functions are called. add the actual python wrapper to: https://gitlab.com/voxl-public/voxl-sdk/utilities/voxl-mpa-tools/-/blob/pympa-experimental/tools/python/pympa.py then finally, when you call pympa_create_pub, save the pipe id and then pass it to check for clients. Alex

@Eric-Katzfey Thanks Eric. I will try this out and let you know soon.

@Moderator Thank you. This clarifies everything.

@Eric-Katzfey This sounds like perfect plan. I would implement this and get back for any queries. Thank you Eric!

@Aaky , we are working on resolving the GPS detection issue related to uart baud rate changes - if forcing the baud rate works reliably then just stick with that !

@Aaky Well, unfortunately it isn't obvious what is going wrong. You will have to start by disabling everything and when px4 comes up reliably start enabling things to find out the culprit.

@Aaky You'll have to use a nightly build of the SDK, here's a link to the latest one: https://storage.googleapis.com/platform-nightlies/voxl2/voxl2_SDK_nightly_20241208.tar.gz Keep in mind that these builds are untested so we can't promise any functionality

@Aaky , the mixer should never output a value lower than mixer min (while armed).

@Aaky, yes if you change the camera configuration, just follow the same process: copy correct sensorbin (with correct slot id) to /usr/lib/camera/ as previously discussed confirm the camera is detected using voxl-camera-server -l update camera config xml with correct camera ids - the camera id’s will start with zero and increment by 1 for each camera. The camera id assignment happens in order of the camera slot id. Slot id is mapped to the physical connector. You may want to remove unused sensorbins from /usr/lib/camera just to avoid any confusion. You can always get them back from /usr/share/modalai/chi-cdk