Nomad Connection Issues

If you click on the {Troubleshoot} button on ETCnomad, does it list your Ion as an available master? If so, select it in the list, then click {Change Master}. If it does not show up, there are some additional things to check:

• Make sure both devices are running the same language/keyboard language.
• Can the Ion ping your Mac?
  • If not, then your IP settings are not correct.
• Make sure MultiConsole is enabled in Shell>Settings>Network>Interface Protocols
• Do you have Firewall enabled on your Mac?
  • If so, are you able to turn it off?

If you click on the {Troubleshoot} button on ETCnomad, does it list your Ion as an available master? If so, select it in the list, then click {Change Master}. If it does not show up, there are some additional things to check:

• Make sure both devices are running the same language/keyboard language.
• Can the Ion ping your Mac?
  • If not, then your IP settings are not correct.
• Make sure MultiConsole is enabled in Shell>Settings>Network>Interface Protocols
• Do you have Firewall enabled on your Mac?
  • If so, are you able to turn it off?

Under troubleshoot it does not come up. I'll go through and check the other things tomorrow and see if I can get it working! 

IPs are correct and Multiconsole is enabled on both.

I decided to let my Nomad sit on searching for master and after about 5-10minutes, it decided to connect and sync, though the connection was very slow. ..?

Any ideas what might be causing this sporadic behaviour and slow connection?

It's running though a gigabit TP-Link switch and into a (consumer) router /WAP. 

When you say WAP, does that mean that you're connections through WiFi? This isn't officially supported...

I have been connecting over WiFi, yes. I was unaware this is unsupported. I'll have a go with an Ethernet dongle tomorrow, though I'm still curious what's causing such bad performance over WiFi, I've had it work perfectly on 2.8 

WiFi is inherently half-duplex. There is a lot of latency switching between sending and receiving. The multiconsole protocol is chatty and requires a lot of handshaking. It wants (needs?) full-duplex.

For understanding WIFI technologies:
- you can't reserve any bandwidth for your application
- many technical solution use the same frequencies (depending on regions)
  - Bluetooth
  - DECT
  - WDMX
  - inhouse WLAN
  - wireless mouse and keyboard
  - Smartphones which permanently tries to connect to WLAN (meanwhile the biggest problem)
  - Smartphones working as an Access Point
  - ...
- all this applications shares at least the same 'free of use' frequency bandwidth 
- there is a limit of connection over the same bandwidth, if reached the connection bandwidth going down
Therefore, 'Real Time' applications are at least not stable using wireless technologies and will never be.