Herelink Ethernet

Hi all,

I’m trying to get ethernet pasthrough working. I’m running on the Beta Channel, SRU01200616 on the ground unit and the corresponding version on the air side.

I understand a ethernet adapter with a R8152/8153 chip is required, I have have a ANKER A7610011 and a Cable Matters 202023-BLK for testing. Both use the correct chip according to the Amazon comments, although its very hard to get the information directly from the manufactures.

On the ground side I have a generic OTG adapter, and have tested it with a USB stick. On the airside I have a OTG charging pass through cable, this allows to power the adapter (and the airside, and cube, I’m not sure if that is a good idea).

I undstand with a adapter on both ends it should be a transparent link but I cant seem to get it working.

It does have to be said that I am a complete beginner with regard to networking stuff such as this.

@iampete - where did you get this information about ethernet passthrough feature? Is it documented somewhere?

so the basics look good to me, the next trick is getting adb access to confirm (gcs)

here is a new bootimage for the GCS unit to make the R8152/53 detect. https://drive.google.com/file/d/1MGFAqC1zXrdnO2yEGhaigW-xktIx2cHj/view?usp=sharing (GCS unit bootimage with R8152)
the stock image includes
AX8817X
AX88179_178A
NET1080

to update the boot image via usb (i asume you have adb access already/developer mode)

adb reboot bootloader
fastboot flash boot boot.img
fastboot reboot

Next we enable adb via tcpip, but first we need to enable this via usb

adb shell
setprop persist.adb.tcp.port 5555
reboot

then after the reboot, get the ip of the GCS unit (eg 10.0.0.99)

adb connect 10.0.0.99
adb shell

you should get the shell again
do a

ifconfig

and check if eth0 exists

Now verify we can adb into the air unit
once you have adb to the gcs unit, power on the air unit and do a

adb shell (gets you into the gcs unit)
adb connect 192.168.0.10
adb -s 192.168.0.10:5555 shell

this should now get you into the air unit.

Next
try running a

/bin/busybox brctl show

under interfaces you should see vxlan1 and eth0

optimus:/ $ /bin/busybox brctl show
bridge name bridge id STP enabled interfaces
br-vxlan 8000.00e04c360345 no vxlan1
eth0

also run

ping 192.168.144.10
ping 192.168.144.11

these are the bridge endpoint ip’s

during testing, make sure the screen stays on on there GCS unit, otherwise power saving features limit background data flow (most likerly setting i have not found yet)

ive just confirmed that this is working ok. one possible caveat. if you home network is using 192.168.0.x, things may not work.

3 Likes

Thanks Michael,

After installing adb, I managed to verify both ends are detecting the adapters, I swapped to a AX88179 (I think) based adapter on the ground side. The ground side sees this:

ifconfig

And the air side:
ifconfig air

Both clock up some RX and TX bytes if I plug into a network. However I can’t connect via the link. (would be not be surprised if there is a PEBKAC).

Interestingly the ground side will shows up on the network, and I can ping it:

network

However the air side does not.

when you say ground side? thats the wifi ip ground side?

taken via herelink ethernet


i have uplink BW set to 1.4mhz and down set to 10mhz (non default)

I have it working!

Cant quite do 4K YouTube, but 1440p no problem, Wifi is only slightly faster on my old laptop. (I am not also streaming from a camera, I suspect that would slow this down)

I suspect I was having a couple of issues.

firstly the second Ethernet port on my desktop was not connecting, maybe due to the first already being connected to the same network (no doubt this is fixable but I’m a networking newb).

Secondly /bin/busybox brctl show was only showing eth0 if it was conected at boot. But it still shows up in ifconfig if you plug it in after the fact.

So, booting both ends with compatible adapters already plugged in has resulted in it ‘just working’ adb is useful to debug, but I didn’t actually have to change anything with it.

Now to see if I can get the camera working…

1 Like

Correct they must be booted with Ethernet plugged in ,as there are things run at startup to setup the bridge

Hi Michael,

If you find the time, kindly add a how to first steps in a post or wiki.
Until now, we used to have a mikrotik routerboard, an ethernet switch and a capable wifi card along with the herelink to accomplish the same scenario onboard the drone.
Thats a really super good to have capability for ethernet talking payloads, as well as simplifies the 4G add-on.

Best regards,
Dimitris Stefanakis,
UcanDrone

assuming all you want is a transparent link between the 2 Ethernet adapters, all you need to do it plug it in, and boot the air and gcs unit, all the setup is done by default.

the key is getting the correct adapters, and verifying those details are what ive listed above.
ive been testing with RTL8152 adapters, but you need to update the GCS unit to use these, other than that, it should be plug and play, just make sure they are plugged before power on.

Thanks Michael! We have updated all our clients Herelinks, but haven’t heard for the Ethernet adapter compatibility.
This feature must advertised as hell!!!
I’ll check my adapters for RTL8152 and maybe upload a showcase vid.

Best,
Dimitris

I have quite a section of adapters here now, maybe we should start a comparability list, like the one for cameras.

1 Like

I have the camera working, just had a loose connection.

The camera gives a rtsp stream, I can view it on a PC connected to the Ethernet on the ground side. It looks like QGC on the Herelink can view rtsp streams, but it cant connect, maybe because the like is transparent?

I guess that is also linked to how one would use the Herelink hot spot on the ground side rather than Ethernet?

correct, its transparent and independent of the Herelink video. it is possible to make it visible, via some routing changes

@iampete can you better explain your setup (camera, connections)? Do your camera has native RTSP output? why do you need a full IP bridge? I ask because it’s an interesting setup

Yeah, the camera is basically a IP security camera, it has native RTSP.

Bit of a tangent, but my understanding is that IP style cameras are quite common due to the licencing cost associated with having a HDMI connection.

The setup is very basic.

Camera ethernet out -> USB OTG adapter -> herelink air -> herelink ground -> USB OTG adapter -> PC ethernet in

I can then logon to the Cameras webpage and point it about, zoom in ect. You can also just view the RTSP stream.

this is a very interesting thread, because of growing popularity of RTSP camera in industrial sector and ethernet cable is handy. I would like the air unit had an integrated ethernet port to avoid clumsy converters etc… or at least an USB-C port, since handles power more reliably

@Michael_Oborne What changes in routing need to be made? You could provide accurate information.

i cant give details for a setup without alot more info from you.

however there is another thread


talking about having a rtsp camera connected via ethernet and viewing it on there herelink GCS