@Alex-Kushleyev
Was the source of this noise ever found?
My solution with the starlings was to just use the F9P ultralight, but those are also very expensive. They must just work well because of the L2 support, since L1 is almost fully being jammed by voxl2.
Thanks
I am also messing around with Ardupilot on a fixed wing, and wondering if any sort of voxl-io conf is needed for passthrough the PWM and CRSF RC? in a previous SDK, I believe there was a voxl-io-server, which no longer exists in 1.5 SDK, from what I can tell.
I have upgraded the firmware and followed along with the rest of the thread.
Thanks for any info.
Ok thanks, I will select "0" here:
and just for my understanding, every starling 2 and starling 2 max has that M0173 board inside of it? I thought I looked at the drones to check this, but didn't notice it I guess.
Thanks for this info.
Although I will probably start a new thread, would this config affect the use of the VOXL-io board. I am trying to use voxl-ardupilot + voxl-io on J4, but its not detected via voxl-2-io
Thanks
I am trying to setup a VOXL2 board with the C-04 camera config shown here:
https://docs.modalai.com/voxl2-camera-configs/#c-06-tof-hires-and-tracking-d0005-starling
I flashed a newer version of voxl sdk and setup as VOXL2-board only as shown below:
────────────────────────────────────────────────────────────────────────────────
system-image: 1.8.02-M0054-14.1a-perf
kernel: #1 SMP PREEMPT Mon Nov 11 22:47:44 UTC 2024 4.19.125
────────────────────────────────────────────────────────────────────────────────
hw platform: M0054
mach.var: 1.0.1
SKU: MCCA-M0054-CC-T0-M0-X0
────────────────────────────────────────────────────────────────────────────────
voxl-suite: 1.4.5
Trying to follow the guide, the first issue I see is that voxl-configure-cameras only gives me the following options:
26 - M0173 Starling 2 IMX412 + dual AR0144
27 - M0173 Starling 2 PMD IMX412 triple AR0144
28 - M0173 Starling 2 Max dual IMX412 + dual AR0144
29 - M0173 Starling 2 Max PMD + dual IMX412 + dual AR0144
30 - M0173 Starling 2 Prototype dual PMD + dual IMX412 + dual AR0144
36 - M0173 Seeker V5+ IMX412 + dual AR0144
37 - M0173 Seeker V5+ IMX412 + dual AR0144 + Boson
46 - M0173 Seeker V5+ IMX664 + dual AR0144
47 - M0173 Seeker V5+ IMX664 + dual AR0144 + Boson
I just did C for custom config
Given this, I started trying to manually follow the others guides and adding the binaries manually and using config helper:
https://docs.modalai.com/voxl2-image-sensors/
I ran:
camera-server-config-helper tracking:ov7251:2 hires:imx214:3
cp /usr/share/modalai/chi-cdk/imx214/com.qti.sensormodule.imx214_3.bin /usr/lib/camera/
cp /usr/share/modalai/chi-cdk/ov7251/com.qti.sensormodule.ov7251_2.bin /usr/lib/camera/
When I run voxl-camera-server -l I only see 1 camera detected, and it seems to be the ov7251, but then I then run the config helper with just he tracking cam, the voxl-camera-server still fails to start the camera. I am not in a place right now to swap cameras to see if its hardware, but just want to make sure I am doing the config and mapping correctly.
Especially since, when I look at the qrb5165-configure-camera script, the mapping from HWID to bin makes zero sense to me, especially for C-04:
https://gitlab.com/voxl-public/voxl-sdk/services/voxl-camera-server/-/blob/sdk-1.0.0/scripts/qrb5165-configure-cameras?ref_type=tags
Any input is appreciated. I think I had been thorough with your docs up until now, but still no luck.
I did wget from the voxl2 over wifi to get the package in / directory. dpkg -i on that results in this error:
voxl2:/$ dpkg -i voxl-mainline-px4_1.16.0-1.0.2-202505070835_arm64.deb
Selecting previously unselected package voxl-mainline-px4.
(Reading database ... 105523 files and directories currently installed.)
Preparing to unpack voxl-mainline-px4_1.16.0-1.0.2-202505070835_arm64.deb ...
Unpacking voxl-mainline-px4 (1.16.0-1.0.2-202505070835) ...
dpkg: error processing archive voxl-mainline-px4_1.16.0-1.0.2-202505070835_arm64.deb (--install):
trying to overwrite '/data/px4/etc/extras/actuators.json.xz', which is also in package voxl-px4 1.14.0-2.0.94
dpkg-deb (subprocess): decompressing archive member: lzma write error: Broken pipe
dpkg-deb (subprocess): cannot copy archive member from 'voxl-mainline-px4_1.16.0-1.0.2-202505070835_arm64.deb' to decompressor pipe: failed to write (Broken pipe)
dpkg-deb: error: <decompress> subprocess returned error exit status 2
Errors were encountered while processing:
voxl-mainline-px4_1.16.0-1.0.2-202505070835_arm64.deb
I currently have voxl-ardupilot and voxl-px4 stopped and disabled.
Any ideas on this?
Eric, Thanks, yeah I suspected that it was some sort of version thing with px4 where they support it now.
Could you explain what the difference between mainline px4 and what I probably have loaded? or is it just because the VOXL SDK 1.4.1 is slightly behind?
Thanks
I am using the Holybro F9P Ultralight with the starling 2 max but am not able to get gps data from the F9P. This is in relation to this post, trying to get around the self-jamming gps issue on the voxl2 with modem stack:
https://forum.modalai.com/topic/4226/starling-2-max-no-gps-data/44
I have voxl-px4.conf GPS set to auto, so then it runs px4-qshell gps start.
When I look at the px4 logs, I see this being repeated:
May 02 20:57:54 m0054 voxl-px4[1746]: INFO [muorb] SLPI: u-blox firmware version: HPG 1.51
May 02 20:57:54 m0054 voxl-px4[1746]: INFO [muorb] SLPI: u-blox protocol version: 27.50
May 02 20:57:54 m0054 voxl-px4[1746]: INFO [muorb] SLPI: u-blox module: ZED-F9P
May 02 20:57:54 m0054 voxl-px4[1746]: INFO [muorb] SLPI: GPS UART baudrate set to 115200
May 02 20:57:54 m0054 voxl-px4[1746]: INFO [muorb] SLPI: Got ack to initial CFG_VALSET!
There is never outputted this line: (Which form other forum posts seems to indicate a real successful connection):
INFO [uORB] Advertising remote topic sensor_gps
Also, my px4-listener sensor_gps says:
voxl2:/$ px4-listener sensor_gps
never published
and then px4-qshell gps status outputs in the logs:
May 02 20:57:33 m0054 voxl-px4[1746]: INFO [muorb] SLPI: qshell gotten: gps status
May 02 20:57:33 m0054 voxl-px4[1746]: INFO [muorb] SLPI: arg0 = 'gps'
May 02 20:57:33 m0054 voxl-px4[1746]: INFO [muorb] SLPI: arg1 = 'status'
May 02 20:57:33 m0054 voxl-px4[1746]: INFO [muorb] SLPI: Main GPS
May 02 20:57:33 m0054 voxl-px4[1746]: INFO [muorb] SLPI: protocol: UBX
May 02 20:57:33 m0054 voxl-px4[1746]: INFO [muorb] SLPI: status: NOT OK, port: 6, baudrate: 115200
May 02 20:57:33 m0054 voxl-px4[1746]: INFO [muorb] SLPI: sat info: enabled
May 02 20:57:33 m0054 voxl-px4[1746]: INFO [muorb] SLPI: rate reading: 0 B/s
May 02 20:57:33 m0054 voxl-px4[1746]: INFO [muorb] SLPI: Ok executing command: gps status
I also went into the u-center with the F9P and made sure that ubx was a protocol for in/out.
voxl-ardupilot doesn't have any issues connecting, so wondering if this is just a px4 gps driver issue specific to the voxl setup. I am on voxl-suite 1.4.1
Any advice on this? Thanks for any info
Hello, we purchased some standalone voxl2's + 5G modem carrier boards with quectel modems in the past. I forget exactly, but I believe we received these Quectels from Modalai when they were sold together on the website (i might be remembering incorrectly).
More recently, we purchased the Starling 2 Max and the 5G modem boards (without a modem). We plan to use some Quectel RM502N-GL like we have in the past. Today, it was discovered that the old 5G carrier boards detect the quectel on lsusb, while the new ones do not at all. I narrowed it down to the new 5G modem carrier boards and even have the following photo showing resistors are different. Do you know if there is a compatibility change that wasn't made clear on the website?
The board on the left works with quectel
Let me know what you figure out. Is your 3D filament something like Onyx, that has some sort of carbon in it?
probably around 8 satellites on average. Sometimes going up to 10. I also had difficulty getting any satellites after a reboot a few times. It took multiple minutes to see anything at all.