@Chad-Sweet Got it. So driver from Immervision in ISP Auto-exposure and Auto white band control mode needs to be utilized instead of Modalai's auto exposure algorithm. Am I right? Immervision is providing driver for Qualcomm RB5 dev kit from Thundercomm, will that driver work over VOXL2 as it is?

@Aks I was told by Microhard Support that this usually indicates a hardware problem that requires repair or replacement, but they also suggested to try reapplying the system firmware. Reapplying the firmware for the modem seems to have worked for my case.

@modaltb thanks for the response. Hope it will make it in :).

@Alex-Kushleyev Thank you so much for your response. We tested ESC with some other motor and found out RPM and power was exceeding 10000 RPM / 60% power and everything seems to be good with ESC. Our motor must be damaged or there is some problem. I will consider your feedback for motor selection as well. Thank you!

@Abdulla-Ayyad I would use one of these cameras [image: 1676388804266-9096b792-780f-4437-afa8-8716dc399117-image.png] Hi-res pointing down. If you do not have a port available with your current configuration you can always digest with a UVC camera. More information on that here: https://www.modalai.com/pages/image-sensors?_pos=1&_sid=c1e39cd13&_ss=r

@Byron_Ch As long as it is the mini OEM module (snapshots shown below), it'll work. I know they had a few offerings when the 2x2 MIMO first came out that exceeded that, but any module using that format will work from a hardware perspective. [image: 1676217000495-screenshot_20230212-074745_drive.jpg]

Hi @Byron_Ch , Thanks for your patience. Yes, you are correct, but I wanted to add a few notes. we are happy to review any schematic you make. If you want that, let us know and we can reach out to you using the email you registered with on this forum. the VBUS on V2 can supply a total of 2A, but due to pin limits (1A per pin) if you think you'll need that full 2A sustained (it's ok for burst/in-rush), I would use the 5VDC_IN rail (output of the eFuse) instead of VBUS, but you'll still need to use VBUS as the "host detect" function. you can start from our Altium package to get a jump start on connectors, pinouts, and pcb outline with mounting holes and connector placement here: https://docs.modalai.com/voxl2-connectors/#add-on-board-to-board-design-package And I would still keep the J5 mate even if you don't need any signals. You can pick up the GNDs and it will provide a solid mechanical function providing two points of contact. on your plug in board, be sure to do a 3D fit check. There are some high components on V2 and you need to pay attention to any high components on the back side (with the connector mates) of your design. V2 3D is here: https://storage.googleapis.com/modalai_public/modal_drawings/M0054_VOXL2_PVT_SIP_REVA.step Let us know if you have any other questions. We want to see your plug in board succeed the first time!

Hi Vinny, Got it, very thank.

Ok, we will find out if we can do it ourselves, or just find another m9 lens.

@jconk If you're struggling with an issue you are more than welcome to create a post here with a description of the problem, things you've tried, things that aren't working, etc. and we will gladly help you resolve your issue. It seems as though this is your first post on this forum meaning you haven't reached out previously. We want people to succeed using our platforms and our team monitors this forum every day providing solutions.

Hi @황인호 Correct, we no longer carry/sell/support that design as noted here: https://docs.modalai.com/hdmi-input-accessory-datasheet/ ** Note: ModalAi’s HDMI accessory has been discontinued and is no longer available ** Let me know if you have any more questions about this. Thanks!

The distance, or baseline, is a part of the extrinsic calibration process https://docs.modalai.com/calibrate-cameras/

@tom Tom, Thanks for the Saturday reply! I' know I won't be able to ping the device's IP from the internet, just like I can't ping my phone or any other cellular device. They're inside the carrier's NAT'd subnet. I get that. But I cannot ping any public ip FROM the device. At the end of that old thread, he shows the Voxl pinging 8.8.8.8 and getting a response. I still don't, after following all of the suggestions in that thread. Like I said, I can get a DNS response if I ping a hostname, just no response to the ICMP from the host. Things that might help me: Another SIM from a different carrier or (or carrier's reseller, as most of the IoT SIM providers tout using ATT, T-Mobile and Verizon's networks, but have their own APN's..) to try. I'm working on that. In the meantime, coming from my early beginnings jockeying Hayes modems from DOS 3.3 running a BBS (Bulletin Board System, the pre-internet way we communicated..) I'm familiar with the Hayes AT command set (or used to be..) so I'd like a document (that I can't find on the Sierra site) listing my modem's AT command set so I can dig deeper into this problem myself. The Tailscale VPN looks nice and may be the simplest route (at a cost, and once I can actually talk to the outside world with this thing..) but I'm linking to a good video for you guys to look at. This guy is pretty savvy, and what he's doing here works. Without a VPN I might add.. The reverse SSH tunnel is quite interesting. Worth a look. https://www.youtube.com/watch?v=IokyotAGbJI

@Vinny Thanks Vinny! Just trying to maximize the versitility of my investments! Same way you guys do when you use the same board for both products! I'll leave it alone...

Hi @Byron_Ch , Our schematics are not open sourced, but we make every effort to make sure you have all the info you need. What information are you missing to be able to do your own schematics? We will also offer a review of your schematics as a courtesy if you wish. Side note: several customers did not successfully make their own flex cables for these image sensors and often come to us to make a custom flex after their attempt. All we need is a 2d flattened outline (.dxf) and we can handle the rest. Food for thought. If you think you want to go that route, let us know and we'll email you. Thanks

@Vinny Thanks that does! So I made a new wire and it worked! It turns out my issue was that because I created a custom USB 2.0 to 4 pin JST connector I had too much exposed wiring. USB apparently requires a ton of shielding around all the wires to work which I did not know until now. Thanks for all the help with clarification

Hi @Eloi , Thanks for the feedback, our website is out of date and the the MCBL-00029 should have been included, let me work with our team and we'll get you a cable in the mail to resolve, I'll send an email to your address here.

Great, thank you so much! Will keep my eyes open.

Thank you for a kind reply.