Hi @Abdulla-Ayyad No we don't. Sorry. We prioritize our Voxl based ecosystem.

@tom Curriously, it does not seem to accept -p 0000, which was our pin. We changed it to 1234, which is accepted, but that didn't help with the issue, and it acted identically to providing the wrong pin. quectel-CM -p 0000 [03-02_13:02:16:064] Quectel_QConnectManager_Linux_V1.6.0.24 [03-02_13:02:16:064] unknow -p '0000' quectel-CM -p 1234 [03-02_13:02:39:300] Quectel_QConnectManager_Linux_V1.6.0.24 [03-02_13:02:39:305] Find /sys/bus/usb/devices/2-1.1 idVendor=0x2c7c idProduct=0x800, bus=0x002, dev=0x003 [03-02_13:02:39:307] Auto find qmichannel = /dev/cdc-wdm0 [03-02_13:02:39:307] Auto find usbnet_adapter = wwan0 [03-02_13:02:39:307] netcard driver = qmi_wwan, driver version = 22-Aug-2005 [03-02_13:02:39:308] Modem works in QMI mode [03-02_13:02:39:325] cdc_wdm_fd = 7 [03-02_13:02:39:399] Get clientWDS = 15 [03-02_13:02:39:430] Get clientDMS = 1 [03-02_13:02:39:462] Get clientNAS = 4 [03-02_13:02:39:494] Get clientUIM = 1 [03-02_13:02:39:526] Get clientWDA = 1 [03-02_13:02:39:557] requestBaseBandVersion RM502QAEAAR11A04M4G [03-02_13:02:39:686] requestGetSIMStatus SIMStatus: SIM_PIN [03-02_13:02:39:718] requestGetProfile[1] 3gnet/carl/1234/1 [03-02_13:02:39:749] requestRegistrationState2 MCC: 238, MNC: 20, PS: Detached, DataCap: UNKNOW [03-02_13:02:39:781] requestQueryDataCall IPv4ConnectionStatus: DISCONNECTED [03-02_13:02:39:781] ifconfig wwan0 0.0.0.0 [03-02_13:02:39:803] ifconfig wwan0 down

The modules support different LTE bands for different cellular network regions EMEA is Europe, Middle East, Asia NA is North America

Thanks, BTW, i've checked it with the help of a team mate and this is the correct FOV orientation for the sensor (not the measurements): [image: 1683797119162-e05f360a-d319-4564-a99d-b38286d36f7c-image.png] Keep in mind that the Graphics Industry Standard is W x H and you have H x W = 85ºX106º and should be W x H = 85ºx106º (for this position in the picture) Also, W x H = 85ºx106º vs Horizontal x Vertical = 100ºX80º on the different images can cause confusion with the different orientations and values. I would suggest to use the same ratings on both pictures. This is the correct HxV position of the sensor: [image: 1683798333107-4a3d84ec-ea53-4d7c-bde8-9f30dd96a861-image.png] Eloi

Thanks @Chad-Sweet I'll give that a shot.

@andrespalomino if the lens is really loose, then the lens could loose focus as it gets rattled with vibes. Verifying that below is your camera: [image: 1683728564550-oem-m0025-2-resized.jpg] When you state that you can get the focus good on the ground but when flying looses the focus, do you mean you can see it gradually getting worse over time or all of a sudden? How far are you viewing the feed? Also, how high are you flying? Do you see a difference when you are closer to objects or lower to the ground?

VOXL 2 Mini is powered at 3.8V and VOXL 2 is powered at 5V. So, there will be a slight hardware change for the Mini ESC to support VOXL 2. We do plan to have that as an option in the next month or so. It is a PCB stuffing option for 5V

Hi @mark , At this time there's nothing in the config file that can alter the color, but we are attempting to get color tuning going such that we can tweak these settings. Right now it's not something we know how to do quickly (yet!), so please bear with us while we get to this (although it's likely over summer time frame).

The mount is M12*0.5 1/2.3" Everything you see in the picture is included [image: 1682092505962-3eb36eda-9258-403c-a5a1-4ac7784a0abe-image-resized.png]

Thank you for the replies, they are very helpful! I was wondering if you had mechanical info on the lens mounting fixture? I could not find more info about that. Does it come with the IMX678? Does any M12 lens fit into it? Any mechanical drawings/models?

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