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
@Leo-Allesch , actually we do have a very limited quantity of the TOF V1, so hopefully that would avoid doing the re-design of the camera mounts and flex routing.
Please reach out to https://modalai.com/contact for a custom order. you probably should get one or two of M0135 as well.
Alex
So it seems like the VOXL2 ports (J6L, J7L, J7U) seem to be functioning (when tested with the hires or tracking camera and a working M0135)?
Can you please provide more information on your requirements: VSLAM and target detection. Both can be done without TOF sensor. TOF sensor is often used to help with obstacle detection / avoidance in indoor environments.
The easiest way to add the new TOF sensor to your drone would be to use the following:
The connection for the new TOF module to VOXL2 would look like this :
VOXL2 <-> M0172 <-> M0177 <-> M0178 <-> IRS2975 TOF sensor
You are right that the cable routing may be an issue, you would likely need to update the mounting bracket for the camera as well.
I am going to double check if we have any TOF V1 left at all.. will get back to you soon.
Replacement M0135 (if you need):
Alex
@Dan-Jennings , M0181 can be used to enable a Boson and another hires or tracking camera (or Hadron combo), see diagram below. You would need to use the kernal variant 1.0.1 (same one used for M0173, which I am assuming you are already using).
So basically, you can use any standard config C26-C29 + two more cameras connected to VOXL2 J8. Please note that VOXL2 J8 shares CCI (i2c) buses with J6 and J7, so you have to be a little careful about what cameras you connect to J8 to avoid i2c address conflicts. I am going to put together some more information on that soon. But if you are adding a Hadron or Boson + IMX412 to J8, there will be no conflict.
Please let us know if you have any other questions.
Alex
@voxltester said in Microdds not working with Microhard modem:
Is there any one who is an expert on the microhard and network setting?
You will need to reach out to microhard for config setup on that front.
@Nitin-Varma-Vegesna said in Apriltag relocalization not relocalizing?:
@Nitin-Varma-Vegesna Is there any release that is known to work for April Tag Detection?
https://gitlab.com/voxl-public/voxl-sdk/services/voxl-tag-detector
The dev branch is the most recent - I have to check with the engineering team on this as I am unsure the priority of april tag detection and positioning based off it. Will relay back