@Darshit-Desai No, the Sentinel propellers would not likely fit. You should use the recommended propellers or risk serious damage.

@sansoy said in voxl-inspect-qvio error: IMU_MISSING: dt(ms) | T_imu_wrt_vio (m) |Roll Pitch Yaw (deg)|features|quality| state| error_codes | @sansoy what is the output of voxl-inspect-imu? It looks like qvio is not receiving the data from the imu server. Did you configure imu-server? Or is this all out the box for the m500?

Hi @Kashish-Garg - you can either just create your own ~/.bashrc and put what you need in there, or you can reflash the system which I would recommend doing. Zach

@tom we are in a situation where we have 2 identical boards. one board has a working flight control board and the other has a working VOXL. is there any way we can use them together for the time being?

@Riccardo-Franceschini All good, glad you got it fixed!

@Alex-Kushleyev That fixed it for me. Thanks again for the help!

@modaltb Thanks, despite the delay, for the response! I only have one last question in this regard: is it possible to rotate the stereo ov7251 by 90 degrees or currently it is only possible to flip them by 180? This info would help me a lot. Thanks!

@Moderator I see, thank you for the clarification - I think I was confused because I saw the HW info returned Flight Core V2. I will try to run everything from /data/ , but I was initially worried about path errors because the other ROS packages and Python dependencies appeared to be installed in root. Will update here.

@tom Yeah definitely not ideal, actually setting up an orange pie on linux right now to handle the flashing in the future, haha

@hmlow , I know your post was a while ago.. But I wanted to add some detail. Going to 15Hz is going to reduce the maximum exposure (duration of emitted IR signal) to about 1/3 of the maximum which would be for 5Hz. This is due to the fact that maximum power output remains the same and increasing FPS means less power is emitted during each frame. Longer exposure / IR pulse means the sensor can achieve higher signal to noise ratio and pick up returns at longer distances. So that would make sense that you may see less phantom obstacles at 15hz compared to 5hz, if these obstacles are indeed coming from multi-path returns (weaker / shorter IR signal has less chance of being picked up by the sensor)

@Darshit-Desai what do you have set for ekf2_aid_mask. The fact that you cannot go into position mode means something is barring you from moving into position mode, aka a specific parameter. If your QVIO quality is good, then a parameter in your PX4 isntance is off.

@Pooyan Interesting, systemd is ideal way for it to be running

@Moderator For the LTE Modem on the Sentinel will the Modem cover European bands for operation? (normally there is US and European Variant). Do you have any LEPTON Thermal sensor ready for the Sentinel without disabling or modify the drone? Will a USB connection to the drone simply be viewed as an additional camera (FLIR C5) in the OS or will we have to solder the connections on the flight controller?

@kerct But I would strongly suggest moving to SDK 1.1.2. It's very hard for us to support customers using older SDK versions.

@Isaac-Stephan-Remy please pull down the most recent iteration of https://gitlab.com/voxl-public/voxl-sdk/utilities/voxl-mpa-to-ros2/-/tree/dev and build within the qrb5165 docker image and deploy the deb. This will allow you to convert UVC 422/UYVY images from the MPA to ros2. In the meantime I am working on the fix for ros1 as well. Zach

@Moderator Great, thanks!

@Moderator I was thinking details, like at what speed and altitude etc.?

Hi @tcg6000 We understand your urgency, and an RMA will take some days to complete on our end. I can provide you with a part number, but you need to be aware of a couple things: We will not just check and replace (as needed) the TVS diode, we will run a full factory test and check for other issues. Should any arise that seem to be related to the over-voltage, we will fix and credit accordingly. If we could not find the root cause of other potential downstream failures, we will replace the ESC(s) Please note soldering to replace parts will void any warranties on that board, S/N M2300000M81. And if you decide to do that on the other one, please share that S/N. So, if you do replace those parts yourself, and you find you still have other issues, we cannot honor the warranty and RMA credits I just mentioned above. Basically, replacing parts now makes the whole process "at your own risk". That part number, should you still wish to replace on your own is (here is a digikey link): https://www.digikey.com/en/products/detail/littelfuse-inc/SMF4L17CA/10710004 If you review the specs, you'll note it starts to conduct ~19V, hence why @21V if it was sustained, effectively looked like a short circuit to the power supply, and the TVS was exposed to the condition long enough to short it out too... (at least that is my opinion) I will follow-up internally on that free replacement power supply order today. I'll try to make sure it get's processed today or tomorrow. Let us know what you decide, and if you do replace it, let us know if that fixed everything for you. Thanks! Vinny

@tom Thank you so much. It is done.

@Darshit-Desai when you are subscribing to /hires_large_color or /hires_large_grey are you planning to do some kind of image processing on these image messages in ROS? These are huge 4k images and I'm not sure how much the ros CV bridge can handle. One option is to resize the images since that typically complements image processing for whatever consumer subscribes to these image topics and will result in a speed up. Rectification also can be used to reduce the image warp. Another option is to play with the image sensor encodings and find something more manageable in ROS and computational power required.