Nomad in Client mode

urban79

Active Member
We have an Element in use that I'm trying to use Nomad with as a designer console and rfu. I had it working a month ago with no issues, but now I cannot get it to find the console at all.
Things I've double checked:
Both nomad and the console are on the same version of software and library version.
Nomad is in Element mode, rather than Eos.
The computer is connected in the correct IP address range and subnet mask.
I can access the console from OSCRfr without difficulty.
Nomad can control the system as the primary client, so I know it's getting to the network correctly.

The only thing I can think of that's changed is that we added an SQ into the ecosystem for control, however removing it from the network does not give me access back.

I do plan on calling ETC support, but this doesn't rise to the level of an emergency after-hours call, and I haven't been in while they're open long enough yet.

Thoughts? Any weird things I should check?

Thanks!

Chris
 
Do you have multiple interfaces/(wifi) on your nomad computer? It might be routing traffic the wrong direction.
Can you ping the IP of the console from your nomad computer?
 

Users who are viewing this thread

Back