VFU1076 Posted February 5 Report Share Posted February 5 Hi all, I am running into a communication issue that I am not over familiar with. My customer has a V700 communicating via Modbus TCP with an Exlar Servo motor. Once the run bit is high the equipment starts operating and then it sporadically stops due to a communication failure between the controller and servo drive. I have replaced cables, checked wires and everything seems to be normal. As mentioned, it does not happen frequently, the equipment runs for an hour or so and then it stops. At times, it seems to be happening more often so I'd say every 10 minutes or so. After speaking with my customer, they said they have been building the same equipment for a long time and the program has never changed. I was confused as I thought that there was probably something in the code causing the issue, but it seems like it could be hardware too. Anyhow, I uploaded the program and everything seems to be correct in it. I would personally do a few things in a different way, but as my customer said the program has never changed and they have been building the same equipment for years. I noticed that the programmer used socket # 3 (TCP/IP Sock init) for the TCP communication, however the local port linked to that socket is the port 20259 which is stored in a MI 215 operand. In the help menu says that port # 20257 is the default port for socket # 3. Would this be causing the communication issue my customer is experiencing? I have attached a pdf of the vlp project and hopefully that helps. The routine is called "COMMS MODBUS TCP" which is the routine that uses the socket for the TCP communication. Thanks in advance for your help. Cheers! COMMS MODBUS TCP.pdf Quote Link to comment Share on other sites More sharing options...
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.