The Seeker has been used for that sort of work in the past, though the customer is still expected to develop the swarming application. You can see this article here as an example. The configuration of Seeker depends on how the customer intends to approach the problem. If you plan to communicate with the robots over cellular / LTE, then that is the option to choose. There is WiFi built in for short range communications. A controller is recommended for emergency take-over, but not explicitly required. Please develop using extreme caution as unpredictable behavior can occur. We have some safety tips at https://modalai.com/safety

@hmlow Great, thanks for looking into that!

Hi @janis_blank , A quick browse of those range finders showed some with I2C interfaces. Now, we don't have all drivers possible starting in PX4, so this might not work out of the box. Here's the drivers available: https://github.com/modalai/px4-firmware/blob/modalai-1.11/boards/modalai/fc-v1/default.cmake#L17 There's a spare I2C port though likely available on the hardware for you, J13 on FlightCore: https://docs.modalai.com/flight-core-datasheets-connectors/#j13---i2c-display--i2c2-bus--safety-switch-connector You may need to enable drivers and then alter startup to get to work, here: https://github.com/modalai/px4-firmware/blob/modalai-1.11/boards/modalai/fc-v1/init/rc.board_sensors But in theory using I2C you should be able to get data from the range finders (it wouldn't be integrated into voxl-* tools, rather just used by PX4 though)

Hi @janis_blank , In theory yes, it's 3.3V TTL with 5V power supply on that connector. There are MAVLink baud rate settings and mode that you may need to configure. We sell the FlightCore stand alone, which is a low cost way to test the theory out as well, but I'm not seeing a huge risk on the system connection.

@Eric-Katzfey I can see color video by using voxl-streamer -c hires-logo. Thank you.

@Adrian-Hidalgo I just sent an email to the address you gave. Thanks again!

@Nathan-Ni, What setup do you have? M500, Flight-Deck? What version of software are you on? It seems like vio isn't starting up hence the 0,0 in x & y. You can try: systemctl restart voxl-qvio-server You can also try: systemctl restart voxl-vision-px4 If those don't reset qvio then a power-cycle is the best bet to reset it. The error code is mentioning low features. Is there enough lighting and feature for the cameras to see? If you haven't already checked out our setup guide: https://docs.modalai.com/voxl-m500-getting-started/#confirm-connection-with-qgroundcontrol What method are you using to connect to QGC?

https://docs.modalai.com/voxl-tag-detector/

Hi @stevet Late to reply, and thanks so much for your instruction! It's great news for M1 developers like me I will have a try if it works well, and let you know then.

@Rowin There is a new forum post here: https://forum.modalai.com/topic/889/how-to-stream-hires-camera-at-vga-resolution-and-simultaneously-capture-4k30-to-a-file that explains how to get beta access to a new package with the capability to stream from the hires camera at VGA resolution while simultaneously capturing HD 4k30 to a file.

There is a new forum post here: https://forum.modalai.com/topic/889/how-to-stream-hires-camera-at-vga-resolution-and-simultaneously-capture-4k30-to-a-file that explains how to get beta access to a new package with the capability to stream from the hires camera at VGA resolution while simultaneously capturing HD 4k30 to a file.

@Jagatpreet-Nir We test with SanDisk Ultra 16GB cards. We have tried other cards and have seen failures so not all cards will work.

@Nathan-Ni In your picture you show that voxl-streamer is already running. Then you launch another instance from the command line and get a failure. This is most likely due to not specifying a different port for the new instance. Documentation is here: https://docs.modalai.com/voxl-streamer/#viewing-output-from-multiple-connected-cameras

@tom Yes! we were able to make a connection! Thank you @tom

Thanks @Chad-Sweet for your reply. So I did not try the PID method, but instead used a new 3S lipo battery to replicate the previous flight behaviour. The first test was a huge success and the drone flew well even while facing the other sides. But further tests, the power avionics issue has come back again and the tests are now inconsistent. Sometimes it flies well and sometimes its going haywire, but almost getting the avionics power low issue every time. Could this be the power module issue? Anyway I've ordered power module and my next step is to replace with a new power module and test. But is there anything that you could suggest?

Thanks for your reply! I am confused on what Pin 7-10 are on the VOXL Flight. Looking at the H-RTK where would the SAFETY_SWITCH, SAFETY_SWITCH_LED, VDD_3v3 and BUZZER connect to on the J7 port?

@Matt-Turi Thanks! I had tried this one previously, but I'll give it another go with your recommendations.