Topics created by jcai

@jcai, I just tested this. I do see that "Removed 1 sessions" message comes in after ~1 min after the first disconnect, but my second session is not interrupted when this happens.

Please make sure you are using the latest version of voxl-streamer (you can try from nightly dev build). Also, something to double check, whether the two sessions are coming from the same or different port (maybe if you are using vpn or something, there new session starts from the same client port).

Alex

Awesome, thanks!

Update: the filter was absolutely the difference maker

25427486-6567-4848-a3ad-b4992ec64ffb-image.png

@modaltb As far as I can tell, I'm building a perf kernel. These are my changes:

MODAL_REPO_BRANCH=v1.8.02 in bin/qrb5165-common.sh

I've added the following lines to ./lu.um.1.2.1/apps_proc/poky/meta-voxl2-bsp/recipes-kernel/linux-msm/files/fragments/m005x.cfg:

CONFIG_MACVLAN=y CONFIG_VLAN_8021Q=y

And then building:

./qrb5165-build.sh -m M0054

Hi @jcai ,

I am not sure about this one.. If a higher kernel version is required and the existing driver does not actually work, then maybe it is not a big surprise! 🙂

the kernel module is in the build, as specified in the config file here : https://gitlab.com/voxl-public/system-image-build/qrb5165-kernel/-/blob/qrb5165-ubun1.0-14.1a/arch/arm64/configs/vendor/kona-perf_defconfig#L328

Some info about the driver : https://gitlab.com/voxl-public/system-image-build/qrb5165-kernel/-/blob/qrb5165-ubun1.0-14.1a/arch/arm64/boot/dts/vendor/bindings/net/microchip,lan78xx.txt

You could try to pull source code from updated driver for this device from a newer kernel, drop it into the voxl2 kernel build and build the kernel with new driver. I think some users on this forum were able to do something similar with another device (not ethernet adapter).

Maybe try another ethernet adapter? 🙂

For example,

voxl2-mini:/$ lsusb -t /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 10000M |__ Port 1: Dev 2, If 0, Class=Vendor Specific Class, Driver=ax88179_178a, 5000M voxl2-mini:/$ ethtool eth0 Settings for eth0: Supported ports: [ TP MII ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Half 1000baseT/Full ... Speed: 1000Mb/s Duplex: Full ... voxl2-mini:/$ iperf -c <my desktop machine ip> ------------------------------------------------------------ Client connecting to <my desktop machine ip>, TCP port 5001 TCP window size: 85.0 KByte (default) ------------------------------------------------------------ [ 3] local <my voxl2 local ip> port 52708 connected with <my desktop machine ip> port 5001 [ ID] Interval Transfer Bandwidth [ 3] 0.0-10.0 sec 339 MBytes 284 Mbits/sec

Did not quite get 1 gig (about 300Mbit/s), maybe there is a bottleneck somewhere, but maybe that will work for you..

Alex

Yes, Hadron is working when plugged into J6 of VOXL2 Mini with default kernel.

You just need to have the following sensormodule files in /usr/lib/camera/:

com.qti.sensormodule.boson_0.bin com.qti.sensormodule.ov64b40_1.bin

And instead of gpio6, you need to use gpio30 to enable the CCI mux, so that communication with the EO camera is enabled:

voxl-gpio -m 30 out voxl-gpio -w 30 1

I will update the Hadron documentation..

Alex

@Alex-Kushleyev Thanks, everything looks alright now that I've removed the other cameras from the config file

@Alex-Kushleyev Yup, editing kona-perf_defconfig looks to have worked, thanks!

@jcai It should then be rtsp://192.168.1.222:9976/live. Ah, but you don't want that live part on the end?