Herelink Ethernet

HereLink
72

yes I tried different things

  • 192.168.144.0
  • 192.168.144.1
  • 192.168.144.10
  • 192.168.144.11
  • 192.168.0.10
  • 192.168.0.11

edit :
after few more tests I dont realy know why it was not working first time but now it looks to work with 192.168.144.11 as gateway

73

again this is by design, your use case does not make sense. and has no practical use the way you have drawn it.

there is no plan to add any spanning tree to the bridge.

i think either your not showing the entire story, or im missing the reason you need this in the first place

74

the only way to see that ip from the GCS unit is to use ethernet out on the GCS unit. the ip range is not routed via wifi etc.

75

I’m sorry but when trying with a USB<->ETHERNET on the remote it’s not working never
but when connecting PC on Android acess point it’s working great

76

Actualy, we need bonding(active-backup) on two side.Wired connection will be main and wifi connection is backup. Are there any way to do this. Because our vehicle is indoor-ground-vehicle and sometimes wireless connection is lost. In such cases, we want to use the wired connection.

77

I am using the Ethernet function for talking to the companion computer that is on the drone. But I want to eliminate some parts for weight saving. Our current setup:

Herelink Air unit -> USB to ethernet adapter -> USB to ethernet adapter -> Linux companion computer (without JR45 eth socket)

This system works perfectly, but it takes weight and space and it looks quite stupid, because it is just micro USB to micro USB with 2 of the same USB to ethernet adapters in between with a very short ethernet cable. Is there a way to make this smarter? Like using just micro USB to micro USB? With some changes in Linux?

78

Good Day

Try using UAVCast Pro( Introduction - UAVcast-Pro) licence key for 1 year is only 39 USD with a companion computer such as RasPi to reduce weight and get a LTE 4G setup for your drone application !!

79

I have set up a manual route on my pc that is connected to the hotspot: sudo ip route add 192.168.144.0/24 via 192.168.43.1 dev wlp0s20f3. A bit disappointed to see your reply that its not possible, how come I can access 192.168.144.10/11 but not my payload at 32?

80

192.168.144.11 would likely work
but 192.168.144.10 will not. reason being is that device has no default route, and is designed that way, to prevent any traffic leaking from the air unit to places it does not need to talk too. ie any traffic from that device will use valuable bandwidth that would otherwise be used for video or telemetry.

you could however add a default route to the air unit, and it would work.
create a file /sdcard/init.sh on the air unit and add

ip route add default via 192.168.144.11

81

Thanks for getting back to me, that makes sense except that I am able to both ping and connect to adb of both the air unit and the ground unit without any extra /sdcard/init.sh. See this screenshot:

Screenshot_20230425_065117

As you can see I can also ping the payload from the remote Ground unit adb shell.

What I am trying to achieve is to connect laptop->WiFi-> (GCS) i.e. 192.168.43.1->192.168.144.11 → Air unit 192.168.144.10 → On board computer 192.168.144.32.

82

Hi Philip, have you got this to work after this post? I have the same problem, the final connection of pinging from laptop to the payload pi is not successful.

83

To those who still have issues, here is what we do to get it work:

  1. The physical system is as follows: laptop->WiFi-> (GCS) i.e. 192.168.43.1 (GCS hotspot)->192.168.144.11(Heralink Ground unit) → Air unit 192.168.144.10 → On board computer (Pi or laptop) 192.168.144.x.
  2. Adb to air unit, then get the root authority, change it to act as route by enter the following command:
    adb shell
    $ sysctl net.ipv4.ip_forward
    net.ipv4.ip_forward = 1
    $ su
    '# ip route add 192.168.43.0/24 via 192.168.144.11
    RTNETLINK answers: File added
    '# exit
    $ exit
  3. Ssh to onboard computer(pi for me) with ethernet cable or wifi, and change its netplan configuration(or dhcpcd.conf if using Pi OS instead of ubuntu) to include: the air unit as gateway, and the hotspot of GCS as route:
    sudo nano /etc/netplan/60-static-ip.yaml
    network:
    version: 2
    ethernets:
    eth0:
    dhcp4: no
    addresses: [192.168.144.41/24]
    gateway4: 192.168.144.10
    nameservers:
    addresses: [8.8.8.8, 8.8.4.4]
    routes:
    – to: 192.168.43.0/24
    via: 192.168.144.10
  4. Now save and apply the change: ‘sudo netplan apply’, ping from Pi to the hotspot: 192.168.43.1, if successful, then you can go back to your ground laptop, connect the GCS hotspot, and ping back to pi successfully.
  5. The key is that GCS doesn’t route the Pi, and we can’t configure it since its Android OS is closed and hard to root, but the air unit is open to root (with command ‘su’), so we can use its port as the route to pass data to the hotspot then to the ground laptop.

PS: you may encounter an issue of eth not connecting when the Microusb of airunit is plugged to the laptop for adb, which blocks the eth, just unplug it and move on.

1 Like
84

Hi
Good detailed info.
Can this be utilized for Herelink v1.0 where we could get an airlink IP using a usb to ethernet adaptor connected on the Airlink unit.

85

Hi jacob,

We are using Heralink 1.1, which has an ethernet port, and we didn’t buy Heralink 1.0. And as far as i understand, the previous discussion in this page is with the setup you describe, and it doesn’t hurt for you guys to try, right?

1 Like