@voxltester Great! Glad you got it working.
ModalAI Team
-
RE: VOXL2 J19 QUP3posted in Ask your questions right here!
-
RE: VOXL2 J19 QUP3posted in Ask your questions right here!
@voxltester In order to execute on the DSP side you have to have
qshellbefore the command. When you have it you get the error that command is not found. That's probably because the driver has not been built into the DSP image. It only seems to be on the apps side. -
RE: VOXL2 J19 QUP3posted in Ask your questions right here!
@voxltester slpi_proc = SLPI = SSC = DSP. I think the only option at this point is to attach an oscilloscope and verify the signals.
-
RE: starling 2 max qvio vs open-vins performance issuesposted in Ask your questions right here!
You should be able to download it and install it, as our betas are now public.
@Muqing-Cao said in starling 2 max qvio vs open-vins performance issues:
do we have to change the configs file to the startling-specific configs after update?
Not necessarily, unless you changed the default values. The new SDK installation will prompt you to identify your platform.
-
RE: starling 2 max qvio vs open-vins performance issuesposted in Ask your questions right here!
@Muqing-Cao
Please update it to the latest version, 1.6.3.PS: 1.6.3 is still in Beta phase, but it should be released soon
-
RE: VOXL2 J19 QUP3posted in Ask your questions right here!
@voxltester i2cdetect is looking for i2c ports on the apps processor so it isn't useful for this where we are trying to use DSP i2c ports. It shows an error message. Can you add the
-Xoption to see if that resolves that error condition? -
RE: starling 2 max qvio vs open-vins performance issuesposted in Ask your questions right here!
Can you confirm your SDK version?
-
RE: Camera Calibrationposted in FPV Drones
@taiwohazeez , when you run the camera calibrator, are you providing the correct size of the checkerboard? it looks like you are using 8x6 in the image above (number of inner corners).
Alex
-
RE: CANT ACCESS CAMERAposted in FPV Drones
Can you please confirm that you only inspected several pipes using the command:
voxl-inspect-cam tracking_down tracking_front tracking_rear tof_ir hires_small_colorAlso please use
voxl-inspect-cputo check if the cpu is overheating during your testing.Additionally, are you able to provide output of
voxl-camera-server(running in the foreground) when the pipes start disappearing?If you are able to update to the latest SDK (1.6.x) , it may be easier for us to support, as 1.4.5 is 7 months old.
Alex