The old seeker documentation can be found in the docs source here : https://gitlab.com/voxl-public/support/documentation/-/blob/master/docs/999-Hidden/51-seeker.md (gitlab should render the markdown). Please let me know if there is anything else that you cant find.
Alex
Hi @Mason-N ,
OK, let me check again. Can you measure the diameter of the propellers that you have (it should be two types, it looks like) and let me know?
Alex
@LuisRzdearbulo-0 Can you provide a link to the documentation that you are referring to? What type of simulation are you looking to do?
The ICM42688 is an IMU and there is already one of those on the VOXL2 so you don't need that external one. The RM3100 is supported by ArduPilot. If it is not detecting it then we need to do some troubleshooting. First is to double check the wiring to make sure that the i2c pins for the RM3100 are correctly routed to the i2c pins on J19. You said dev board 6 pin UART. A UART should be only TX and RX (And power and ground for the external board) so only 4 pins. Are the other 2 pins for sure the i2c lines for the RM3100? And what pins are you connecting to on the VOXL2 J19 connector? Perhaps put a scope on those lines to see if you can detect activity. Make sure COMPASS_ENABLE is set to 1. You can limit which magnetometers that ArduPilot searches for on initialization by setting the COMPASS_DISBLMSK parameter. Make sure all bits are set except for the RM3100 bit (bit 16) to force it to only look for RM3100. Bus speed should be 400 kHz by default.
Hello @Gerhold-Ten-Voorde ,
This is not related to the quality, but instead, it is a supply chain decision.
Alex
@Plingaas02 Regarding odometry in voxl-mavlink-server, it will not modify timestamps on this message. There will be, potentially, VIO odometry messages going to the flight controller from voxl-vision-hub via voxl-mavlink-server and flight controller odometry messages being routed out to the GCS and to the onboard stream. The odometry messages coming from PX4 will have the DSP monotonic timestamp which is different than the Linux monotonic clock and these will drift with respect to each other over time. PX4 runs the timesync service so it can correct the incoming messages from VIO.
@jbiscan21 , yes you can add the TOF sensor to Starling 2 Max, but you will also need a new front plastic mount that will hold the hires and tracking cameras as well as the new TOF sensor.
You can order the mount (which will be a drop in replacement for the original camera mount) with the TOF sensor. If you do want to proceed with the TOF sensor + plastics order, we will need to double check that all the necessary screws are included. You would need to send an email for a custom order to start this off and mention this thread and that we need to include mounting hardware. https://www.modalai.com/pages/contact-us
(related post : https://forum.modalai.com/topic/5157/c29-configuration)
See more detailed pictures.
Alex
@jbiscan21 , sorry i am surprised that we don't have a photo of the Starling 2 Max with the TOF mounted. Please see below. The TOF sensor is oriented vertically on the front face, right next to the front hires and tracking cameras.
If you need to mount the sensor somewhere else, you can use an available extension flex (it only works for the TOF V2 sensor) : https://www.modalai.com/products/msu-m0170
@leandro , yes we do have M0195 boards available. Please send us a contact inquiry to get a custom order (https://www.modalai.com/pages/contact-us).
The connectors J01, J23, J45 and J67 are not populated - we do not have a build with those connectors. You would need to add them yourself.
Also, we are currently not (yet) officially supporting the ToF pills on this board, there is limited internal testing being done. We may be able to provide limited support for that. If you are interested, i can find out what the status of this effort is.
MCBL-00128 we have is only 75mm, unfortunately.
There is a way to make the TOF V2 work on VOXL2 mini, however it is a bit of a hack (which temporarily enabled a transition to the new TOF V2 while using old camera connectors, which did not provide enough power).
Note that if you use M0195 camera front end (or M0188), then you will not be able to use the TOF V2 because both camera connectors on voxl2 mini would be used up.
What's included in M0169 kit (from our shop page linked above)
@pmeras , the connector specs are provided here : https://docs.modalai.com/micro-coax-user-guide/ . Specifically, the connector part number is DF56C-26S-0.3V(51).
You can find some more information regarding the cable pinout for our hires camera here : https://docs.modalai.com/M0186/
We do not manufacture custom cables, just the ones used in our VOXL camera ecosystem.
Alex
