I was using the DMC-2143 via RS232 but I'm trying Ethernet because I can apparently dedicate one handle to command/response and another to unsolicited messages, which I want to use as a way to flag LabVIEW that a script is done executing.
I have established a connection from my PC to the controller and can send commands through the connection just fine. However, in Galil Suite, when I try to connect to my device, the option comes up as a UDP connection. I can go into bookmark and edit it to TCP and connect but when I send the command 'TH' within the terminal it tells me that handle A is TCP while B is UDP. So I close out of B and try to reopen it under TCP, but upon sending that command, the terminal tells me that handle B is already open. I then check with 'TH' again and B is open under UDP again. Am I doing something wrong?
Also, if I try to open up, say, handle C, it will inconsistently open up handle D or some other handle.
Thank you
MattK on 06/24/2015 - 15:55
Hello jmartz,
When GalilSuite connects to a controller it will open two separate UDP connections. One for solicited traffic and one for unsolicited traffic. This is in contrast to GalilTools (and the GalilTools COM library) which opens a TCP connection for solicited traffic and a UDP connection for unsolicited traffic.
So in order to further help you troubleshoot, I would like to know if you are using our GalilTools API in LabVIEW or are you establishing a raw socket connection? If using the COM library and GalilSuite simultaneously to connect/disconnect you may see handles appearing to jump around. If opening a socket connection to the controller you will need to manually create these connections and route messages appropriately.
Can you provide some additional detail as to your system set up and communication scheme? If you would prefer to email me you can do so at mattk at galilmc dot com.