Interesting IP communication
Just a quick note here. I was at a job the other day tryin to get an ESCIENT fireball comunicating over ethernet. The problem had been that things would be communicating just fine and some sort of interenal hiccup with the ESCIENT would effectively kill the socket we were using. The problem was that AMX had no way of knowing whether or not the socket was still communicating with the device. So a friend of mine and I were tasked to write some code that would ensure that we always had good comunication. After several permutations we finally got some code writen that would ceck for COMMS every 10 seconds or so and with no reply would close the socket, wait for the offline event to occur, then reopen the socket. We noticed that even with the ESCIENT physicaly unplugged that NetLinx would still open the socket, there was infact no way to tell wether or not the socket was actually communicating to the device. It's a little early in the morning for me to explain all this, but I just wanted to see what other AMX programmers do to ensure that they have good comms over ethernet to a device. Any thoughts?