Hi @taiwohazeez,

The " /fmu/in" prefix is used for sending data to the autopilot - you're never going to receive data from the autopilot listening to that topic.

Look at the "/fmu/out" topics to see messages coming from the autopilot.

Best,
Ted

@Jetson-Nano The issue is that those messages were commented out in msg/CMakeLists.txt. The reason for that is that there is a limit in PX4 of 256 different types and there are too many. CAN isn't supported on VOXL 2 so those messages were commented out. If you want to use our fork on FCv2 you can uncomment those messages and comment out some of the VOXL 2 specific messages that aren't used on FCv2. For example:

ParameterClientResetResponse.msg ParameterClientSetValueRequest.msg ParameterClientSetValueResponse.msg ParameterServerSetUsedResponse.msg ParameterServerSetUsedRequest.msg ParameterServerSetValueRequest.msg ParameterServerSetValueResponse.msg

@andrevs01 You can see the PX4 start up script in /usr/bin/voxl-px4-start. You can see the streams being configured there.

@Jetson-Nano Can you please start a new thread for this new topic?

@Vinny

Thank you for the update — I hope you had a great vacation!

As you mentioned, I’ve submitted an inquiry through your contact form. Once I receive a response from your team, I’ll follow up with the necessary details and additional data as needed.

Thank you for your continued support.

@wilkinsaf

Yes this is definitely possible You would need to modify flow-server and possibly feature-tracker to ensure this is pointed at the right pipe Might also need a bit of calibration here and there Have not tested having multiple versions of flow-server, but should be possible. Would need to ensure this works with a downard facing tof for accurate height estimate

To get a rough draft of this working, would take ~2 days

@Alex-Kushleyev would you be able to help troubleshoot this error with the rear tracking camera?

@Jetson-Nano It's a parameter that you can set to any number you want. In QGC you can look at the joysticks tab and see as you press each button which number it is. Then set the parameter to that number.

@Alex-Kushleyev Hey, thanks for the response! It fixed the crashing issue, and I can see frames being processed by running 'voxl-inspect-cam -a', but viewing the boson feed on the web portal shows a blank (black) video feed. I copied the config snippet into my file (swapping out the camera for the correct one). Something interesting to note is that even though I configured the camera for 30fps in FLIR software and on VOXL end, it seems to only be streaming about 11-12 fps. Maybe something is wrong on the camera side?

Hey @Alex-Kushleyev how can I get on that mailing list for the ModalAI sanctioned mast? I designed and 3DP two mounts and used a carbon fibre rod, along with a copper laminate board and seen great improvement in GPS count (see image and screenshot).
Did a couple test flights with this set up and everything ran smoothly. I'll have a better peace of mind with an official mast though.

Looking forward to your response!

mast.PNG matandemi.PNG

@Alex-Kushleyev

Thanks for the advice! Sorry for the delay in following up. Dan and I are on the same team and I currently have the physical drone in my possession.

I've attached a video of what the motor spinning actually looks and sounds like. The motor you see is actually a replacement, and the behavior is the same. It appears we may actually have an ESC issue or an issue at the connection point between the motor wires and ESC.

The video shown is the result of running:

voxl2:/usr/share/modalai/voxl-esc-tools$ python3 voxl-esc-spin.py --id 1 --power 15

Modal AI Starling 2 Max - Motor Spin Test Video

When running the voxl-esc-verify-params.py script, the output shows that params are all matching:

voxl2:/usr/share/modalai/voxl-esc-tools$ python3 voxl-esc-verify-params.py Detected Python version : 3.6.9 (default, Mar 10 2023, 16:46:00) [GCC 8.4.0] Found voxl-esc tools bin version: 1.9 VOXL Platform: M0054 Detected RB5 Flight, VOXL2 M0054 or M0104! INFO: Scanning for ESC firmware: /dev/slpi-uart-2, baud: 2000000 Sending library name request: libslpi_qrb5165_io.so Sending initialization request INFO: ESC(s) detected on port: /dev/slpi-uart-2, baud rate: 2000000 INFO: Params from ID 0 match ../voxl-esc-params/D0012_Starling_MAX/esc_params_m0129_f2203_5_1500kv_7x3.7x3.xml INFO: Params from ID 1 match ../voxl-esc-params/D0012_Starling_MAX/esc_params_m0129_f2203_5_1500kv_7x3.7x3.xml INFO: Params from ID 2 match ../voxl-esc-params/D0012_Starling_MAX/esc_params_m0129_f2203_5_1500kv_7x3.7x3.xml INFO: Params from ID 3 match ../voxl-esc-params/D0012_Starling_MAX/esc_params_m0129_f2203_5_1500kv_7x3.7x3.xml INFO: Success! Params in all ESCs are valid and identical.

Any thoughts on next steps here?

I've had almost the exact same thing happen but I think ours got hot enough to desolder a part (see pictures). Feels like a manufacturing issue. Is there a way to send it in for an RMA/replacement/etc?

Here is more info:

We have a FC2.

The FC2 is brand new (purchased within the last couple months).

We did the following:

connected the USB cable '10' to J3. connect a known working micro-usb cable to my laptop running QGC. didn't here the usual windows 'new usb device sound'

This was the first time we connected this board. We didn't see any LED's turn on within a second or two so we picked it up by the corners and noticed it was VERY hot.

We quickly disconnected everything.

We inspected the board and found a component on the bottom looks like it shifted off it's solder pads. See attached picture. We didn't inspect the board before hadn

What could have caused this? Especially given a few others have had this.

Thanks!

PXL_20250801_213400321.jpg

@Alex-Kushleyev, were you able to update the dev build of voxl-camera-server to encode the ar0144 color streams?