Keep in mind, VOXL 2 Mini is just a reduced CSI port version of VOXL 2. We even retain the same hardware notations of "J6" and "J7" that align the same electrically and functionally with "J6" and "J7" of VOXL 2.
@Darshit-Desai We do not have a ready to fly reference yet. VOXL 2 Mini and the VOXL ESC Mini both support the industry standard 30.5mm mounting hole pattern, so you should be able to find a frame to fly.
J9 and that LED are "mostly" independent.
J9 is our USB-C port, whereas that LED is indicating the VBUS power is present for J3 USB host port.
There are several things that might make this LED turn off:
SW control, using GPIO_157. That controls the power switch for J3, so if that is set LOW, it will disable the VBUS on J3.
J3 is only able to source ~900mA max current. If you are indeed using J3 and not J9, please check your device is not pulling too much current. If you are using an actual 1S battery, as the voltage drops, so will the current capabilities. So, if you are pulling too much, you are putting a droop into the VBUS. If you are running a fan on 5V and a magnetometer unit at 5V, that also takes away from the max capability as listed here: https://docs.modalai.com/voxl2-mini-connectors/#power-inputoutput-important-note
If you are loosing ADB, that is indicative of a board reset or a short on the USB-C port. This is where the Moderator's comments come into play as well. Clearly a reset will cycle power on both J9 USB-C and J3 USB Host ports. A short on USB-C may force the power mgmt chips to cycle power as well.
Are you able to send a picture of your setup, including your power supply to VOXL 2 Mini? That will help us guide you further.
OK, here is the clarification regarding camera IDs and sensormodule file names and the general process for camera detection on VOXL2 platforms
all the camera-related drivers are located in /usr/lib/camera
the index at the end of sensormodule.bin filename, such as 0 in com.qti.sensormodule.imx678_0.bin is only used to distinguish the files - the actual index at the end is not being used for anything
each sensormodule.bin file contains a camera_id parameter, which is read by the camera framework after loading the .bin file
the camera_id is then used by the Kernel to look up the specific port information to be used for communication with the specific camera, including (but not limited to): i2c (cci) bus id, mipi interface id, reset pin and others. This information is mapped to each camera port in the Linux Device Tree.
with the above information (all basically mapped to a single camera ID), the camera framework knows how to turn on the camera, which bus to use for i2c communication and which mipi port to receive the image data from
after obtaining the port information, the camera framework uses other information in sensormodule.bin to detect the camera (query the WHOAMI register for camera identification). If the camera is detected, it is considered to be available for the camera framework to use (not much else is happening until you actually open the camera using the voxl-camera-server, for example). The camera framework also loads the list of available streaming modes which is also contained in the sensormodule.bin
after the camera is queried / identified, it is then powered off
when voxl-camera-server is started, it sees all the cameras that the camera framework already detected and their corresponding resolutions / modes. Based on the voxl-camera-server.conf, the appropriate cameras are turned on again and set to stream at the desired resolution / fps.
lastly, for each camera type, there is a single .so dynamic library (for example com.qti.sensor.imx678.so) which contains functions for converting desired exposure and gain values into the register values that need to be sent to the camera.
With all of this in mind, renaming a sensormodule.bin should achieve nothing because the actual id / number at the end of the file is not used for the camera ID parameter, it is only used for differentiating the files.
If there is still an outstanding request to connect IMX678 camera to a port that is currently not supported, please let us know, we can generate and test the new sensormodule.bin files and release them (assuming there are no other unexpected issues)
@Trinadh Can you edit the file /etc/modalai/voxl-px4.conf and set GPS=NONE, RC=EXTERNAL, POWER_MANAGER=NONE, DISTANCE_SENSOR=NONE, and OSD=DISABLE. After updating that file and rebooting does the CPU utilization change at all?
Following on my request. Are you planning to integrate support of the lte device? Timeline?
Hello Team Modalai,
any feedback on this topic?
As the Starling also integrates the Voxl2 it seems at bit like the Voxl 2 mini is more of a future product that needs much more work to be ready. So regarding weight and size savings it could be a great product...
That USB-C follows the pinout you can get from the device spec.
We list the MPN of the connector here: https://docs.modalai.com/voxl2-mini-connectors/#summary
I must caution that you need to plan on failure here. That connector will take a lot of heat to remove and you risk damaging a lot of the surrounding components.
We will obviously not be able to offer any RMA or credit for boards that have been through this potential process.