@crowley stinger is our FPV drone solution: https://www.modalai.com/products/stinger-vision-fpv?variant=48373207695664

We offer various levels of kit that can include goggles, transmitter, etc.

@fhaltmayer It's not something we've explored

@greg_s Great! Sounds good

@Rupesh Apologies for the late reply
It looks like there’s an issue with how the AprilTag system is relocalizing the drone. In my tests, the z-value appears to be misinterpreted, which could explain why your drone was climbing in altitude to correct its height estimate. We’re actively working on a fix.

@Sam-Kiley
Correction on my statement above. Holybro Ultralight F9P seem to perform better due to their antenna setup (RCP Helical Antenna) rather than L2. L2 isn't fed into the NMEA like I originally thought.

@owf226 As soon as PX4 thinks it has taken off then it is trying to level the drone but can't since there are no propellers on the drone. So, it keeps increasing the speed of the motors on the side that needs to come up. That all seems normal to me.

Hi @Riccardo-Benedetti and @paul-foley ,

This issue is not common. There is a potential condition (which we are going to look into) when a MPA client crashes and does not close the pipes properly, the MPA server side will keep the allocated resources open. If the client crashes repeatedly, eventually there will be no more memory for the Kernel to allocate for the new pipes.

Please check to make sure that you have no client processes that are subscribing to image streams and are crashing and restarting (perhaps restarting automatically by systemd). It is possible that a process that is not your test app is misbehaving for some reason and is causing this memory leak by continuous crashing and re-starting.

Also, what if you just use voxl-inspect-cam to inspect the single camera stream and no other camera clients running, does the same issue happen?

Alex

@tom Thank you for your quick response. Do you have a model with these dimensions and technical specifications that is also waterproof, or is it possible for you to develop one? Thank you again in advance for your response.

Hi @will-huang-oksi
Are you willing to share some pics? Might be a cabling issue (GND loop or lack of a common GND), or some other intermittent connection causing your problems.
It really is hard to debug without seeing the setup.

Thanks!
Vinny

Ok thanks, I can parse the raw data. I guess I was expecting the csv to contain the data as well

@emarcphera Huh, interesting. Okay, thanks for posting the update!

Hi @Jetson-Nano
Here is our info for Doodle Labs support:
https://docs.modalai.com/cable-datasheets/#mcbl-00085
Sorry it's buried in a cable page, but it makes the case clear (we think) how to support Doodle 🙂
b1fa4a9a-f883-4566-b3e2-ae9ab14b7264-image.png

regarding probing USB signals, unless you had a USB decoder on the scope, I do not think that will prove anything useful. You may be better off running usbview:
Windows:
USBTreeView by Uwe Sieber — uwe-sieber.de/usbtreeview_e.html
It shows enumeration hierarchy, configuration descriptors, endpoints, VID/PID, power requirements, etc.
Linux equivalent:
Use usbview — it’s essentially the same utility (GTK front-end to lsusb).

Hope that helps!

@jameskuesel , it looks like EIS was merged to the main branch shortly after SDK 1.5.0 was released.

If you have not updated you camera server, please do so : https://docs.modalai.com/camera-video/electronic-image-stabilization/#latest-source-code . You may also need to update libmodal-pipe library.

Alex

@Jetson-Nano Regarding question #1, Yes, you can attach an external FC over the UART.

@dvz ,

The lens in the MSU-M0149 camera module should come with IR filter installed, which means that you will not be able to detect IR light.

You can test with an IR LED or a phone that has an IR scanner (many phones do) or explicitly check for the filter by unscrewing the lens.

The IR filters installed in the lenses inside MSU-M0149 are not designed to be easily removable. Attempting to do so will void the warranty and may cause damage to the camera / lens or personal injury. Small pieces of the glass filter could come loose. Do not do it.

I just tried to remove the IR filter and i was able to remove it, the filter was broken in process. I unscrewed the lens from the lens holder. The adhesive holding the lens in lens holder, if present, is not permanent and can be scraped off if needed. Then I used a sharp point of an x-acto knife to pry the IR lens off. See images below.

We do not have an option to purchase M0149 camera without an IR filter.

However, a newer version of this camera (https://www.modalai.com/products/msu-m0166) has an option to select a lens without IR filter. Please note that M0166 camera uses different (ucoax) cables and adapters for connecting to VOXL2, so this is something to consider if you do decide to switch.

If you would like to purchase a lens without IR filter (it is very similar to the one in MSU-M0149, but without IR filter, similar overall specs), please send us a request, the part number is JSD5501-C0 (mention no IR filter, just in case). This is the lens shipped with M0166 with no IR filter option. https://www.modalai.com/pages/contact-us

Warning : Attempting to remove the IR filter will void the warranty and may cause damage to the camera / lens or personal injury
m0149_ir_filter_removal1.jpg

m0149_ir_filter_removal2.jpg