Posts made by Chad Sweet

@m4v3r @tom Have you looked at this thread? Seems similar

https://forum.modalai.com/topic/247/how-am-i-able-to-change-from-wifi-to-lte-connection?_=1634754422256

Those are the specs from the vendor, we don't have any more information, sorry. The intensity image is published in MPA so you could perform a calibration on it to find out more details.

Have you followed the tutorial at https://docs.modalai.com/mavros ?

No, but the code for that utility can be found here, seems like a great feature to add!

Also, QGroundControl likely logs that same information

The M0026 IMX377 has an M12 mount lens. There are hundreds of compatible lenses out there for that module.

Some folks have used the SD Card, though it's really slow. The recommended approach would be to build it off target, compress it, then copy it over to target

We have never seen this and cannot reproduce. We have not tried 1.12, but stock 1.11 on flight core should behave as any other px4 hardware platform as far as the ekf_aid_mask is concerned

Can you share your full parameters file and associated log files? Maybe you have other parameters that are conflicting

Sorry for the late reply, were you able to fix this? Based on more recent posts maybe reloading the Flight Core Firmware fixed the issue?

Have you followed the mavros tutorial here?

Please see post here

It looks like the AR8020T uses SRXL2 protocol which is not yet supported in PX4.

Mostly for redundancy. In reality only one is typically used. If developers wanted to take advantage of two for fusion they could

Please see post here

Please see post here

Each PCB is thoroughly tested prior to shipment. If your PCB is no longer responding to ADB or Wi-Fi, it is likely the system flash is corrupted, or "bricked". Please follow the instructions here to fix.

With flash, like what is used on VOXL, removing power while the kernel is writing will result in corruption and bricking of the board. It can happen during development when a lot of changes are being made on the board and then power is removed.

To prevent system partition flash corruption:

• run poweroff before removing power: $ poweroff -f
• Use the /data partition for file storage

Linux has a setting for how often the flash is committed to reduce the risk, but of course there could be different side effects. You can see a writeup on the topic here, as it is common in all of this type of single board computers

Your smartphone fixes this by making you press the poweroff button before shutting off power and does not have a removable battery.

We test all of our PCBs thoroughly before they are shipped. We do ship the PCBs bare though, which means they are susceptible to ESD and other damage. We really can't warranty against how different people may handle the PCBs.

We publish handling instructions that are also shipped with the PCBs, found here

An issue many run into with Flight Core is that they plug USB into the Spektrum port and fry the board.

The RMA diagnostic process is for ModalAI technicians to spend time looking into the root cause of the failure, and then provide analysis on what to do next.

Your video points to a bad camera configuration. The tracking camera cannot produce the resolution that VLC is receiving.

Some possibilities:

• The tracking camera is not properly connected
• The tracking camera is plugged in backwards
• There is another process that is accessing the tracking camera preventing voxl-camera-server from accessing. If you tried the old ROS packages, this could be an issue.
• voxl-configure-cameras does not match what is actually installed. You need to specify the installed configuration, not a subset of what you want to use.

Can you reboot and make sure no other processes are accessing the cameras?

Did you purchase a flight deck? All of this would be pre-configured and tested prior to shipping, so maybe you installed new software?

It is difficult to see exactly what you are trying to do without sharing the commands you are calling.

If the package is not supported, you should try using Ubuntu in a Docker running on VOXL. See the docs here: https://docs.modalai.com/docker-on-voxl/

In general, Ubuntu is easier to use if you are not comfortable creating your own packages, and the performance is typically on par or better as it is a pure 64-bit OS