Topics created by Anubhav

@Anubhav No, the Qualcomm Flight RB5 Reference drone uses the Thundercomm QRB5165 SOM. The Sentinel has the same QRB5165 using VOXL 2 and is built with the same sensor configurations as the Qualcomm Flight RB5.

VOXL 2 has the same computing power as the Thundercomm RB5 SOM, but a much broader support for different image sensors.

@Anubhav The J19 ports are only mapped to the SLPI DSP. You cannot access them directly from the applications processors. Are you running PX4 on VOXL2? If not then you can use libqrb5165_io (https://gitlab.com/voxl-public/voxl-sdk/core-libs/libqrb5165-io) to access the SLPI DSP UARTs from the applications processors.

Hi @Moderator, @modaltb

Any update on the configuration of tracking camera in HW Sensor ID- 3. Camera Server crashes whenever i connect tracking camera in HW sensor ID-3 (J7U) but in the camera server configuration, SDK 1.0 (C-06, C-14 , C-16, C-17 ) configurations shows that the tracking camera is connected to J7U.
Can you please give me update on this?

@modaltb I seem to be having the same issue of the flight core power cycling when battery is plugged in. therefore, esc calibration fails

@Anubhav Great!

@Chad-Sweet - I have the same issue. How to enable the 4K resolution for IMX412 that we bought for $349 USD from you?

I am facing the same issue. How can I account for this noise? Are there any parameters to tune to filter the sensor output on the voxl2 side?
@Anubhav did you solve this issue?

Hi @modaltb,

We were making a mistake of connecting the mavros with the UART which is being used by mavlink server, hence creating the traffic in communication. Now we are connecting mavros with VVPX4 and it's working fine.

Thanks.

Hi @Anubhav ,

Docker should natively work on VOXL2... so the voxl-configure-docker-support shouldn't be used at all on VOXL2....

Should be able to use this directly: https://docs.docker.com/engine/install/ubuntu/

If VOXL2 isn't booting... you can reflash with the platform release, and please just don't run voxl-configure-docker-support (and we need to fix this script to not run on VOXL2.....)

To reflash:
https://docs.modalai.com/platform-releases/#install

I'm not 100% sure but I think you can check if you have publish /mavros/companion_process/status with component value 196 correctly, it should be publish by px4 avoidance automatically if your setup is good.

Hi Alex,

I have noticed following things:

When I am using camera-configuration of stereo+tracking, camera server is not stopping after enabling and starting dfs server. When I am using camera-configuration of tof+stereo+tracking, camera server is stopping after enabling and starting dfs server. Tof sensor is working fine when not using dfs server.

So, the problem of camera server getting stop with the configuration of tof+stereo+tracking and after enabling and starting dfs server a hardware issue?

Does collision prevention works without the depth from stereo server instead just with the depth from tof sensor?

Thanks!
Anubhav

@Anubhav

same issue here,

have you figured it out?

@Zachary-Lowell, Yes I am leveraging iris_vision in hitl_hiris.world file. Isn't it required to fly drone in VIO mode in simulation considering there is no GPS?

That degradation is voxl-portal reducing the resolution because its data link bandwidth is reduced. If you are using Wifi, can you try better wifi coverage or less interference?

If you want unchanged video files for processing, try voxl-logger

Hi @Anubhav , That's very odd that J8 is not working. It's a hard short to the 5V power subsystem that feeds the board. There is no limitation I can see that would prevent that.
I know for Spektrum based receivers, there is a specific 3.3V power sequence and bit-wiggling that occurs for binding (through Flight Core J12), so I'm not sure if your receiver is expecting something similar and does not like the "always on" 5V on M0018 J8 and J9.
The 4G LTE modem M0030 ports J5 and J6 are safe to use. They expose a 500mA limited 5V to those pins. They are USB2 ports @500ma, with USB HS data on pins 2/3, and DGND on Pin 4.
They are turned on sometime after power-on once the hub enumerates with Voxl, so I wonder if that delay ON time is what is helping your receiver bind and communicate properly.
You might be venturing into a Software domain which I am not an expert in, so if just knowing that J5 and J6 are "safe" and this works for you, then great!
If not, we may need to pull in some SW folks to dig deeper.
Thanks!
Vinny

Hey @jamiek,

I can't give an exact timeline on the next stable voxl-mapper release, but it should be coming very soon with a lot of major improvements!

The dev release for mapper does require the dev versions of its dependencies as well, including voxl-portal and voxl-vision-px4 so that may be why you are hitting a white screen with that version.