I am sorry to hear this. I would be happy to review any Wireshark capture that you may have of the connection procedure.
I would recommend reducing the complexity of the system to just one controller connected to the PC on a dedicated network. From here add complexity until the cause of the fault is found.
Have you had the opportunity to try the same connection procedure with the GalilTools software? The controller discovery is slightly different in the two software packages.
In the GalilSuite connections windows, you can manual add a book mark to a known IP address to circumvent the discovery routine. Please try to connect in this manner.
You are welcome to follow up with me via e-mail if you prefer (roger p at galil dot com).
rogerp on 02/26/2014 - 14:08
tbrailsford,
I am sorry to hear this. I would be happy to review any Wireshark capture that you may have of the connection procedure.
I would recommend reducing the complexity of the system to just one controller connected to the PC on a dedicated network. From here add complexity until the cause of the fault is found.
Have you had the opportunity to try the same connection procedure with the GalilTools software? The controller discovery is slightly different in the two software packages.
In the GalilSuite connections windows, you can manual add a book mark to a known IP address to circumvent the discovery routine. Please try to connect in this manner.
You are welcome to follow up with me via e-mail if you prefer (roger p at galil dot com).
I look forward to hearing from you.