Just a quick revisit to this topic to describe my workaround solution. The main issue is that it is not possible to run 2 wifi connections simultaneously. So ideally I would have bought the Bluetooth version and connect to the mount via bluetooth but time travel is not possible
Instead I have tried two possible solutions. One is to mount a Raspberry Pi running INDI on the RA axis. This connects to the mount with the USB cable and connects to the main INDI box (Aaeon Up on the OTA) through wifi via an access point. (INDI allows chaining of devices). I had a few issues in this configuration which I thought were either earth loops or RF interference between the mount, Raspberry Pi and Aaeon being in close proximity.
So the second option was to move the Raspberry Pi off the mount and connected it to the access point by LAN cable. It connects to the mount via Wifi. This was more reliable but still a bit patchy. Then on a hunch I disabled the onboard wifi of the Raspberry Pi and used a dongle instead. This has proved to be much more reliable. I suspect the wifi chip on Raspberry Pi is unstable or noisy and may also have been the cause of the issues when it was attached to the mount. More testing is needed for that. But with this setup, latency is just a few milliseconds anyway. In other words, once a guide image has been taken, transferred to the computer and the correction calculated, its just a few more milliseconds to send the guide command to the mount. In my mind this is immaterial when the guide expsoures are around 1000 milliseconds.
Now I'm just waiting for a clear night to test it thoroughly.