We’re interested to deploy Herelink as an agnostic robot controller that is not drone specific.
Are we able to use the wireless link to pass any arbitrary data between the controller and receiver?
It appears that this is ethernet enabled? Is the existing ethernet packet design and process for interacting with the wireless link documented?
The herelink will act as a transparent bridge for any ethernet traffic.
Ie
Ethernet into the air unit
USB eth dongle into the GCS unit. And any traffic in one end appears on the other
Interacting with the air unit is possible, but mainly via Mavlink.
Depends on what you require
It’s possible to route as well if needed.
Excellent update.
Is there any more detailed documentation on this? Is there a port associated with sending data down the link? A specific Ethernet format?
Mavlink is just serial with some wrappers right? We’d prefer not to have to use mavlink because we aren’t sending those specific drone related data packets…
Our main concern is audio. Is audio already included in the rtsp for the video?
We’ve been going down this same path with the mk32 for siyi. No one is supporting audio?? We all need it. 
Thanks for your help. Herelink is sounding better and better.
Is there any more detailed documentation on this? Is there a port associated with sending data down the link? A specific Ethernet format? “ethernet” is the answer. its a layer 2 bridge.
you dont need to touch mavlink if your not using the onboard uart. (assuming all your traffic is ethernet)
no, currently there is no audio input on the air unit.
i do have some custom modifications to add a usb audio adapter on the air unit however, that has been tested. but this is not in any public area. as there is a need to a otg cable and usb audio adapter to work.
was your need one way audio? or 2 way?
This is making more sense.
Ultimately we need two way audio.
I’d be interested to know about this usb audio adapter.
Otherwise I assume we would likely pursue an SBC that handles the audio and made it available on the network…then customize the controller side app to get that audio out the speakers…and vice versa for the other direction with the Android device sending audio down, extracting it and getting it to a speaker on the robot side.