@garret Oh, nice! Glad it's working now!

@dvz https://gitlab.com/WondesenB/voxl-tag-detector

HI @teddy-zaremba
That is the correct approach. We have no mentions of direct servo support from VOXL 2 or any HW. All servos, just like an ESC, need power from an independent battery source not from VOXL 2.
Thanks for clarifying here on the Forum.

@Gary-Holmgren you have saved at least one other person 🙏

@mrawding good afternoon, i see that your topic is quite old, but I am struggling with px4 firmware build and was wondering if you ever managed to successfully build your px4 firmware ? If you have done it recently, I would appreciate a helping hand in this topic: https://forum.modalai.com/topic/4539/voxl2-hitl-sim-with-gazebo-in-docker-vtol-frame-support/13?_=1751379111988

@Ligma We designed the VRX to be compatible with any off the shelf HDMI input display.

We have used HDZERO goggles with the VRX so you should have no issues there

The latest firmware for M0065 can be found on gitlab here

or directly on voxl2 in /usr/share/modalai/voxl2-io-tools/firmware/

Once updated, the firmware will be detected as version 2. The previous version 1 is no longer supported due to several bugs.

Alex

@smiley ,

The Boson and Hadron are supported the same way by the VOXL2 camera pipeline (same drivers, camera server settings). You just need to use the correct cables / interposers for connecting the sensor depending on the selection of Boson or Hadron. There is no distinction at all from the VOXL2 SW and it does not know whether a standalone Boson or Boson inside Hadron is connected.

Please let me know if you have any other questions.

Alex

@george-kollamkulam

Where are you getting the image / ROS2 packages? Is this an image that ModalAI maintains?

Just looking at the error, it seems like it can't find the yaml-cpp package. It could be that it's not installed correctly or something's wrong in your CMakeLists.txt. It looks like the yaml-cpp readme has some info for including it in your CMake project.

If you're using camera_calibration_parsers from image common, it might be worth bringing the issue up there.

Let me know if that helps,
Ted

@Vinny Sorry thought I had responded, thanks!

@Eric-Katzfey - Brilliant idea- thank you.

@ashwin This path should be on your host machine, in the modal-qdl repo's directory

@justin-sentinel By default the stinger won't have an IP connection out of the box, it would take a bit of tweaking to get it enabled. Can you send a link to the page you're referencing to make sure I'm understanding the context?

@LucasW to answer my own question, VOXL supports 5 GHz. This can be verified by running iw list and looking at the supported channels.

The /data/misc/wifi/wpa_supplicant.conf file does not seem to take effect when trying to specify frequencies, for instance (for 5 GHz channels 36, 40, 44, and 48:

country=ch ctrl_interface=/var/run/wpa_supplicant network={ ssid="my-ssid" bssid=00:00:00:00:00:00 freq_list=5180 5200 5220 5240 scan_freq=5180 5200 5220 5240 proto=RSN key_mgmt=WPA-PSK pairwise=CCMP TKIP group=CCMP TKIP psk="my-pwd" }

The only way I found to connect to 5 GHz is to disable the 2.4 GHz radio entirely on the router. Otherwise, the connection defaults to 2.4 GHz.
On the router, it is also better to set a fixed channel (e.g., 36) rather than letting it be automatic. In auto mode, the robots could not connect systematically to the network.

Note also that my question was wrong in the sense that the hostapd.conf files are used to generate the access point, not to connect in station mode.

These are maybe considerations that could be added to the technical doc @Chad-Sweet ?

Hello @Alex-Kushleyev @Eric-Katzfey

I am looking to control the servo via PX4.
Essentially, it will be a command either from the RC or GCS to open / close the servo motor.

But, if that is infeasible, I can make it work via an API on the CPU / Linux on VOXL 2 to be controlled via SSH.

Regards,
Ashwin