@cbay I got it working by swapping it to ID's 0-3 (2 on the hires lines).

Any known issues with doing this for use in VIO?

Hi Hope yall are well,

I am currently working on getting 4 Ar0144's connected to M0188 and running. As of now all 4 seem to be starting up in voxl Camera server, But ID0 and ID 6 (the ones that should be a combo of eachother) don't seem to be sending frames. If I change what cameras are on what port the new cameras on 2 and 3 start working and 0 and 6 still dont work (showing its a driver/board issue not connector or camera issue)

We had this working previously but cant seem to get it working again. Cameras are plugged into J0, J2, J3 and J6 as was previously recommended.

Here is our Custom Config

#!/bin/bash

################################################################################
#
# This file allows setting of custom camera configurations by defining what
# sensors are plugged into which port.
#
# There is no guarantee that any arbitrary configuration will work. Only the
# predefined camera configs at https://docs.modalai.com/voxl2-camera-configs/
# are supported.
#
# each slot can be one of the following sensors:
#
# pmd-tof
# pmd-tof-liow2
# ov7251
# ov7251-combo
# ov9782
# ov9782-combo
# ar0144
# ar0144-fsin (for use with m0173 and Starling 2 only)
# ar0144-fsin-combo (for use with m0173 and Starling 2 only)
# ar0144-12bit
# ar0144-12bit-fsin (for use with m0173 and Starling 2 only)
# ar0144-12bit-fsin-combo (for use with m0173 and Starling 2 only)
# imx214
# imx412
# imx412-fpv (low latency mode)
# imx678
#
#
# When using a combo mode pair, you must also add a JX_COMBO_MODE field which
# specifies is the pair is to be set up as either a stereo pair ordered
# left-right, right-left, or treated as two independent cameras. If you are
# using a combo-mode flex but only physically connect one of the two cameras
# then select "single" it does not matter which one you connect.
#
# For example:
# J6_LOWER_COMBO_MODE="left-right"
# J6_LOWER_COMBO_MODE="right-left"
# J6_LOWER_COMBO_MODE="independent"
# J6_LOWER_COMBO_MODE="single"
#
# when running "independent" combo mode, also add a NAME2 field for the second cam
# e.g J6_LOWER_NAME2="tracking_rear"
#
# for all sensors except TOF, you can specify a "rotate" flag to
# rotate the image 180 degrees e.g. J6_LOWER_ROTATE="true" or "false"
# for stereo pairs (e.g. ov7251 combo or ar0144-slave-strereo) you can specify
# "rotate-first-only" or "rotate-second-only" to only rotate one, other wise
# when setting the rotate option to "true" both will be rotated.
#
#
# Once configured, this file should live in /data/modalai/custom_camera-config.txt
# then run voxl-configure-cameras custom to load it in
#
#
# cp /usr/share/modalai/voxl-camera-server/custom_camera_config.txt /data/modalai/
#
# We also suggest changing your /data/modalai/sku.txt file to have a camera
# config term "CC" such as MRB-D0005-4-V2-CC
################################################################################


J6_LOWER_SENSOR="ar0144-fsin-combo"
J6_LOWER_NAME="tracking_0"
J6_LOWER_NAME2="tracking_6"
J6_LOWER_ROTATE="false"
J6_LOWER_COMBO_MODE="independent"

J6_LOWER_COMBO1_SENSOR="ar0144-fsin-combo"
J6_LOWER_COMBO1_NAME="tracking_6"
J6_LOWER_COMBO1_ROTATE="false"


J6_UPPER_SENSOR=""
J6_UPPER_NAME=""
J6_UPPER_ROTATE=""


J7_LOWER_SENSOR="ar0144"
J7_LOWER_NAME="tracking_2"
J7_LOWER_ROTATE="false"
J7_LOWER_COMBO_MODE="single"


J7_UPPER_SENSOR="ar0144"
J7_UPPER_NAME="tracking_3"
J7_UPPER_ROTATE="false"


J8_LOWER_SENSOR=""
J8_LOWER_NAME=""
J8_LOWER_ROTATE="false"


J8_UPPER_SENSOR=""
J8_UPPER_NAME=""
J8_UPPER_ROTATE="false"

@cbay This may be a stretch but I do think it has something to do with the difference between voxl-fpv-px4 and voxl-px4. Can someone explain the differences between them

@cbay Reflashing seems to have fixed it, so it isnt a hardware problem and is instead a firmware issue. I am loading custom drivers into voxl-px4, any clue how that can affect it

Been working with the VOXL2 Mini for awhile, communicating with I2C devices using QUP0 on J19. Today ran into an issue of communication and I2C probing failing, finally figured it out to be my SDA line being shorted by the VOXL. I tried different cables, different I2C devices and a seperate VOXL2 Mini, all of them had the SDA line shorted on one mini, and pulled high as is proper on the other.

I see no visible damage on the voxl2 mini and nothing has happened that could've caused this. Any information would be greatly appreciated, specially as if this mini cant use that I2C bus anymore it is useless for our purposes.

Cheers
Carson

@Alex-Kushleyev Found the reason why it was skipping. In /px4-firmware/src/lib/parameters/CMakeLists.txt there is a line that skips all modules that match 'pwm_out'. I was able to disable that for PCA9685. Once I disabled the module.yaml file being skipped it worked. No need for the .c file (which makes sense, that is just the old way to do the .yaml)

@Alex-Kushleyev My issue is the params arent loaded from the YAML file of the driver, so I can't set and save them. I get errors whenever I try to run param set.

Any help on making sure this drivers module.yaml file gets loaded properly

@cbay https://github.com/modalai/px4-firmware/blob/main/src/drivers/pca9685_pwm_out/module.yaml here is where I think the params are

@cbay Checked out a older tag on voxl-px4 and was able to build and install.

When I run the driver I get an error revolving around its Freq, I understand you dont work with the driver so I doubt yall will have info about it.

What I am looking for is how to get the necessary Px4 parameters to show up, as they dont seem to be included properly

@cbay Most of the way through the build process, was able to sort it out including the necessary edits to the PCA driver. Issue I am running into is both the dev and master branches of voxl-px4 require a newer version of libfc-sensor (1.0.9 and 1.0.10 respectively) then what is included in 1.6.2 of the SDK.

I am not sure how to upgrade this library