Hi @austin-c
yeah, and it will not.
There are dozens of changes between the two boards.
It's just easier and cheaper to order the correct version. We have no documents showing how to convert it is simply not doable for the cost and risk and time.
Not the news you wanted, but please trust me on that one. 
Hi @jimbow77 , @oasisartisan ,
I updated the voxl-camera-server on a branch to save the tof v2 calibration to a file. Here is the commit : https://gitlab.com/voxl-public/voxl-sdk/services/voxl-camera-server/-/commit/f7aadc13246df35757498ee8c2633897864d47ff .
Are you able to build the camera server from this branch?
https://gitlab.com/voxl-public/voxl-sdk/services/voxl-camera-server/-/tree/save-tof-v2-lens-cal
We will review the changes more thoroughly a bit later and we can merge them to dev..
On my drone, the calibration file (which will include the serial number of the TOF sensor) is created when running camera server:
cat /data/misc/camera/irs2975c_8E7F-3715-16E7-2CA0_lens.cal
VERSION:1.0:VERSION
#px,py,cx,cy,tan-coeff[0..1], rad-coeff[0..n-1]
120.985 87.9267 101.435 101.435 0.000431714 -0.000511291 -0.0315991 -0.0224586 0.00496448
Alex
@Demarconius Yes, we can achieve ~50ms glass to glass using our VRX and voxl-vtx software service on the UAS-side.
https://docs.modalai.com/vrx-ground-unit-developer-guide/#doodle-labs
@jbhines929 Please fill out the RMA form to get the process started. If it is due to manufactures defect it is covered under warranty and no diagnosis fee will be charged.
@brandon there are likely a number of things going on
If the drone sits idle for a period of time, the sensors heat up (accel and baro). When the props start spinning, the temperature drops causing significant drift. If you let the props spin for 10 or 20s cooling off the board, that can help
I would guess after 30-60s of flight, the altitude stabilizes. That is the temperature of the sensors stabilizng.
The latest SDKs have temperature compensated calibration for IMU and baro. Try calibrating accel and baro and see if that helps.
https://docs.modalai.com/calibrate-baro/
https://docs.modalai.com/calibrate-imu/
The GPS on Starling 2 Max has been tricky. We do have a new GPS on the way that looks promising, and hope to make it available in the next 2mo.
Hi @wetherbeej
Oh yikes..
You should really work with us on that change. There is a high likelihood to damage your VOXL 2 and the MEMs sensors are likely all broken now from the extra reflow cycles.
Flash provisioning is all done over QFIL tools, not PCAT.
@Andrew-Jong , we are able to reproduce the error that you are seeing. I believe that you may need to set up a virtual display in order to get this to work. You could try doing so using Weston compositor, which would normally run if the display was available. Please try it and let us know if you are able to get it to work (or not).
You would need to create a config file /etc/xdg/weston/weston.ini
and try running it manually like this :
weston --idle-time=0 --config=/etc/xdg/weston/weston.ini
a sample config file might look something like this:
# configuration file for Weston
[core]
idle-time=0
repaint-window=15
[output]
name=virtual-1
mode=on
We have not tested this yet, but hopefully it's a good start.
Alex
https://www.modalai.com/products/m0155
https://www.modalai.com/products/m0188 (fixed link)
https://www.modalai.com/products/m0194
If you need M0195, you can contact us directly for a custom order (it's not in the shop yet).
Alex
Please see some responses below:
i2c_geni a84000.i2c / 884000.i2c: i2c error :-107
This is likely due to a service that is enabled for a sensor that's not present, so the service is restarting and trying to detect the sensor.
voxl-rangefinder-server is not running and also voxl-lepton-server. you can disable the service using systemd : systemctl disable voxl-rangefinder-server.CAM_ERR: CAM-SENSOR: cam_cci_i2c_read: 35 rc = -22
this one is usually present when you have a sensormodule driver in /usr/lib/camera for a camera that is not actually plugged in, so the probe fails. Double check the cameras that you have plugged in vs sensormodules peresent in the directory above. However, this is usually harmless, if all of your cameras are working properly.
Pin conflict.. We will double check that, but GPIO 130 is on a Board to Board connector that you are most likely not using, so that should not be an issue.
VIO performance..
Please let us know if you have any other questions.
Alex
@oasisartisan , I just checked the API for the TOF sensor and it seems we can get the lens calibration. I would need to make a change in the voxl camera server to try it. Please give me a few days..
Alex