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

@zauberflote1 I am no longer having this issue. I have been flying with OpenVins for some time, and I was sometimes seeing drift in the vio estimate, and I was wondering what are the best configs to use. for vio_cams.conf and voxl-open-vins-server.conf?

@Myles-Levine Nevermind, I got it working through the voxl interface instead of Qgroundcontrol. Thank you.

@jameskuesel Thanks! Merged

@taiwohazeez HI There,

What SDK version are you using. Anything over version 1.5.3, we recommend using the openvins VIO implementation rather than Qvio.

Typically a different XYZ value from actual indicates VIO reset during flight. What you want to try 1st is a bench test to confirm vio is set up correctly. Essentially power up the drone on a level surface, then connect to it and bring up voxl-portal (http://<ip of the drone>) and goto the VIO page. The page will show the drone in local space (0,0,0 xyz) if you pick up the drone and move it in a 3D plus pattern the vio page in portal should reflect that. If it does not, then we a configuration issue.

@Eric-Katzfey And this is also handy: https://www.sparkfun.com/breadboard-to-jst-ghr-04v-cable-4-pin-x-1-25mm-pitch.html

Ok, I was actually able to get J10 to work as an SPI port by following this thread. I was also able to get video feed from the lepton on slot #2 on the M0188 with this approach. I still don't know if using the devcfg.mbn file from SDK ver 1.0.0 is really the "proper" thing to do, it feels like it could lead to issues down the road. An official answer regarding J10 in SPI mode would be greatly appreciated.

@Alex-Kushleyev

The drone is wired up according to the diagram, could you explain what you mean by the pin1 location?

Here is the output for voxl-camera-server -l

starling (D0005):~$ voxl-camera-server -l existing instance of voxl-camera-server found, attempting to stop it DEBUG: Attempting to open the hal module DEBUG: SUCCESS: Camera module opened on attempt 0 DEBUG: ----------- Number of cameras: 1 DEBUG: Cam idx: 0, Cam slot: 3, Slave Address: 0x00E2, Sensor Id: 0x7750 DEBUG: Note: This list comes from the HAL module and may not be indicative DEBUG: of configurations that have full pipelines DEBUG: Number of cameras: 1 ====================================

Here is the contents of /usr/lib/camera

starling (D0005):~$ ls -l /usr/lib/camera total 6612 -rwxr-xr-x 1 root root 9912 Oct 22 03:46 com.qti.eeprom.cmk_imx577.so -rwxr-xr-x 1 root root 9904 Oct 22 03:46 com.qti.sensor.ar0144.so -rwxr-xr-x 1 root root 5808 Oct 22 03:46 com.qti.sensor.boson.so -rwxr-xr-x 1 root root 5816 Oct 22 03:46 com.qti.sensor.cmk_imx577.so -rwxr-xr-x 1 root root 5816 Oct 22 03:46 com.qti.sensor.cmk_imx577_flip.so -rwxr-xr-x 1 root root 9904 Oct 22 03:46 com.qti.sensor.imx214.so -rwxr-xr-x 1 root root 9912 Oct 22 03:46 com.qti.sensor.imx214_flip.so -rwxr-xr-x 1 root root 9904 Oct 22 03:46 com.qti.sensor.imx335.so -rwxr-xr-x 1 root root 5808 Oct 22 03:46 com.qti.sensor.imx377.so -rwxr-xr-x 1 root root 9912 Oct 22 03:46 com.qti.sensor.imx412_fpv.so -rwxr-xr-x 1 root root 9904 Oct 22 03:46 com.qti.sensor.imx664.so -rwxr-xr-x 1 root root 9904 Oct 22 03:46 com.qti.sensor.imx678.so -rwxr-xr-x 1 root root 9912 Oct 22 03:46 com.qti.sensor.imx678_flip.so -rwxr-xr-x 1 root root 9912 Oct 22 03:46 com.qti.sensor.imx678_mod.so -rwxr-xr-x 1 root root 5808 Oct 22 03:46 com.qti.sensor.irs1645.so -rwxr-xr-x 1 root root 5808 Oct 22 03:46 com.qti.sensor.irs2975c.so -rwxr-xr-x 1 root root 9904 Oct 22 03:46 com.qti.sensor.ov64b40.so -rwxr-xr-x 1 root root 9904 Oct 22 03:46 com.qti.sensor.ov7251.so -rwxr-xr-x 1 root root 9912 Oct 22 03:46 com.qti.sensor.ov7251_front_left.so -rwxr-xr-x 1 root root 9920 Oct 22 03:46 com.qti.sensor.ov7251_front_left_flip.so -rwxr-xr-x 1 root root 9920 Oct 22 03:46 com.qti.sensor.ov7251_front_right.so -rwxr-xr-x 1 root root 9920 Oct 22 03:46 com.qti.sensor.ov7251_front_right_flip.so -rwxr-xr-x 1 root root 9912 Oct 22 03:46 com.qti.sensor.ov7251_fsin.so -rwxr-xr-x 1 root root 9912 Oct 22 03:46 com.qti.sensor.ov7251_fsout.so -rwxr-xr-x 1 root root 9912 Oct 22 03:46 com.qti.sensor.ov7251_rear_left.so -rwxr-xr-x 1 root root 9920 Oct 22 03:46 com.qti.sensor.ov7251_rear_left_flip.so -rwxr-xr-x 1 root root 9912 Oct 22 03:46 com.qti.sensor.ov7251_rear_right.so -rwxr-xr-x 1 root root 9920 Oct 22 03:46 com.qti.sensor.ov7251_rear_right_flip.so -rwxr-xr-x 1 root root 9904 Oct 22 03:46 com.qti.sensor.ov9782.so -rwxr-xr-x 1 root root 9912 Oct 22 03:46 com.qti.sensor.ov9782_front_left.so -rwxr-xr-x 1 root root 9920 Oct 22 03:46 com.qti.sensor.ov9782_front_left_flip.so -rwxr-xr-x 1 root root 9920 Oct 22 03:46 com.qti.sensor.ov9782_front_right.so -rwxr-xr-x 1 root root 9920 Oct 22 03:46 com.qti.sensor.ov9782_front_right_flip.so -rwxr-xr-x 1 root root 9912 Oct 22 03:46 com.qti.sensor.ov9782_rear_left.so -rwxr-xr-x 1 root root 9920 Oct 22 03:46 com.qti.sensor.ov9782_rear_left_flip.so -rwxr-xr-x 1 root root 9912 Oct 22 03:46 com.qti.sensor.ov9782_rear_right.so -rwxr-xr-x 1 root root 9920 Oct 22 03:46 com.qti.sensor.ov9782_rear_right_flip.so -rw-r--r-- 1 root root 149272 Feb 10 17:39 com.qti.sensormodule.imx214_2.bin -rw-r--r-- 1 root root 674736 Feb 10 17:39 com.qti.sensormodule.irs1645_0.bin -rw-r--r-- 1 root root 142472 Feb 10 17:39 com.qti.sensormodule.ov7251_3.bin -rw-r--r-- 1 root root 957344 Oct 22 03:46 com.qti.tuned.cmk_imx577.bin -rw-r--r-- 1 root root 835464 Oct 22 03:46 com.qti.tuned.cmk_ov9282.bin -rw-r--r-- 1 root root 931864 Oct 22 03:46 com.qti.tuned.default.bin -rw-r--r-- 1 root root 957344 Oct 22 03:46 com.qti.tuned.imx412_fpv.bin -rw-r--r-- 1 root root 793816 Oct 22 03:46 com.qti.tuned.ov9782.bin -rw-r--r-- 1 root root 882376 Oct 22 03:46 com.qti.tuned.sony_imx335.bin drwxr-xr-x 2 root root 4096 Oct 22 04:04 components starling (D0005):~$

@Moderator said in Blue Zorro specs?:

COTS Radiomaster Zorro

Oh interesting that its 1w 915mhz! ok that's so cool. But 2k right?

@Moderator Thanks for the quick response!

Which helper would you recommend for outdoor flight configuration with GPS? I see there are several available for different variations.

An added detail: we need good relative altitude measurements at low altitudes for our custom precision landing solution.

@jbhines929 Hi JB, sorry you are running into issues.

One quick thought, is to update the Orqa goggles firmware - https://orqafpv.com/downloads . There were issues at one point, but we have been updating them in the factory recently before shipping

To further isolate, can you plug a different display into the VRX DisplayPort output? Or, try to connect ADB to the VRX? that would let us know if it's a Goggles or VRX issue. (sounds like goggles if they are clicking)

You can always submit an RMA here: https://modalai.com/rma

@Alex-Kushleyev This was what I got when opening the file in SolidWorks:
a3f8d672-9ddc-465e-85c5-f40e6203ce29-image.png

I found a symlink mismatch in the file tree... pushing M073 PCB board with M0172 connector.

Anyway, it is solved now:

8f13ae56-bfcd-4829-8bd1-e238097e9bb0-image.png

Thank you.

Regards,
Jacob

@jon For MONOTONIC the apps side uses the slpi version so that they are in sync. Your application should use apps MONOTONIC. PX4 will convert it using timesync.

@joshuagaus Sorry, but SBUS is not supported. That option will be hidden in future SDK releases to prevent confusion.

@jimbow77 those drones are for aeronautical research. we recommend installing a dronetag or similar

@voxltester said in Microdds not working with Microhard modem:

Do you have any ideas on how to resolve this?

There might be a dependency in the service file - I would recommend taking a look at the file in /etc/systemd/system/voxl-microdds-agent.service and see if there are any dependencies on having WLAN devices plugged in - I am under the impression there is not that dependency, but there is a conflict on which interface you want the dds to start on - so ideally you can add in which interface you wish to leverage into the service file.

Zach

@clange It is technically possible as Stinger is supported by the same VOXL SDK as all of our products. It would likely be a lot of software development to make it happen though

@tejasram The source code is here: https://gitlab.com/voxl-public/voxl-sdk/services/voxl-tag-detector. Perhaps try changing #define MAX_TAG_LOCATIONS 64 in locations.h.