@modaltb Is there any specific SDK we could check for the working of Range-Finder with?
Latest posts made by Jetson Nano
-
RE: Intergrating VL53L1x Range Finder with VOXL2
-
RE: Intergrating VL53L1x Range Finder with VOXL2
This is the wiring diagram of the sensor with the USB Expansion Board.
-
VOXL2 VIO Losing features
Hey, @James-Strawson @Eric @Alex-Kushleyev
I'm using a VOXL2 on a custom airframe build with external FC. For VIO, I'm relying on a ov7251 tracking camera.
-
In the QVIO server, whenever I initialise the server, features are detected and the overlay displays 100%. But when the drone takes-off in stabilized mode, the features displayed in the overlay starts randomly blinking and reappearing.
-
During flight, when the drone is shifted to position mode also, the same cycle of features blinking and reappearing repeats with the overlay displaying 1% or -1%, making the drone drift, losing position.
-
In the concurrent flights, on ground despite reinitialising the server services, the QVIO server overlay shows -1% or 1% due this effect.
Also, I have been testing the system with earlier SDKs (ie. 0.9.5, 1.0.0, 1.1.0). But I have been the observing the above mode of losing features in later SDKs only( ie. 1.2.0, 1.3.0).
Sharing a drive link, where I have uploaded the screencapture of the same issue.
-
-
Haze over ov7251 Tracking Camera.
Hey @Alex-Kushleyev @James-Strawson
I'm using a Starling 2 with VOXL 2 setup on a custom airframe build. I'm currently testing the setup with SDK release 1.2.0.
In the initial testing, in the QVIO server as from the input pipeline was displaying a clear display of features. But over time, the QVIO server output feed has been blurry with a kind of haze being formed around camera frame as seen in the feed. This reduces the features being captured, and the drone loses VIO many a times ultimately loosing position.
Is there any way we can clear this haze and initialise the QVIO server?
Note: Also checked if it was a physical damage to the Lens or hardware but hardware seems to be fine.
-
RE: Intergrating VL53L1x Range Finder with VOXL2
@modaltb I tried detecting in all i2c bus, 0 to 5, it wasn't detected, I got three devices in 4, but it was UU and I think it is the cameras.
-
RE: Intergrating VL53L1x Range Finder with VOXL2
@modaltb It is not detecting any sensors, I check the sensor with another FC with PX4 which support VL53L1X and it was detected there.
-
RE: The GPS is not working on auto-start
@Captain-7th Once you connect the drone to QGC, it'll show some mode in the top left, you can click on that to change to a different mode. When you click on the ready to fly message on the top, it'll show an button called arm for arming the drone.
https://docs.qgroundcontrol.com/master/en/qgc-user-guide/fly_view/fly_view.html#arm
-
RE: Attempt to reduce drift with the help of stereo camera
Hey @Eric-Katzfey @modaltb @James-Strawson,
In voxl-qvio-server, I'm planning to use one of the ov7251 camera module from the stereo pair as tracking camera. How do I edit and define the extrinsics and instrinsics for the same in the voxl-qvio-server config file?
-
Multiple Camera support for VIO
@Chad-Sweet @Eric-Katzfey @modaltb Is there any release of SDK or any upcoming SDK where you are planning support for two or more tracking camera input simultaneously for VIO. i.e., consider a forward and a rear tracking camera being used simultaneously for the qvio servers with the M0173 board?