PDBeal
Member
Hey,
Have a very strange problem. I have contact the Siemens Hotline, several Siemens App Engineers, KepWare, and anyone else I through could help, but nobody has had any luck figuring out was is going on. Here's the setup:
A 316-2DP with a CP343-1 module. The CP343-1 module has an ip address of 10.0.0.14, and the PC running the OPC server has an ip address of 10.0.0.1. This is a completely isolated network. The 316-2DP also has 2 OP17 attached via the MPI interface, and about 12-15 slave Profibus modules attached through the Profibus interface.
The MPI address are listed as below:
CPU - 2
CP343 - 3
Main OP17 - 5
Remote OP17 - 6
The PC is running KepWare KepServer and is configured to use the Siemens TCP/IP driver. For some strange reason, I loose my OPC communications from my PC to the PLC for no apparent reason, and the only way to regain communication is to STOP the CPU and wait a sec or two, then go back to RUN.
At first I wasn't sure what was going on. I've tried several different things. The CP343-1 card was replaced with a new one. System ran for 2 weeks reading data, then stopped again on Monday Feb 7th, 2005. First though was connection resources. I reconfigured the connection resources to allow 2 PG, 4 OP, and 4 S7 Standard communications which still leaves 2 available connection for the Other communications. (Other communications name pulled from SIMATIC Manager Communications tab of the online Module Information of the CPU 316-2DP. After downloading the new configuration, I was able to establish a connection for 20 minutes of type OP.
Under Kepserver I can configure the type as PC, OP, or PG. According to KepWare I can have 4 connections to a CP343-1 module, 2 of PC, 1 OP, and 1 PG. When I restart the CPU from RUN to STOP to RUN, I can connect and read data over an OP type of connection. However, this only lasts about 20 minutes. I can maintain a connection of PG, but this connection is not stable as every coupld of minutes it will drop off then return.
Has anyone seen this problem before, or have any ideas how this can be resolved? Disconnecting the OP17s make no difference, nor does disconnecting all the Profibus devices and Operator interfaces. WinCC also cannont communicate with the PLC. Siemens Hotline and KepWare are both researching this problem without much luck as of yet.
Any Ideas?
Have a very strange problem. I have contact the Siemens Hotline, several Siemens App Engineers, KepWare, and anyone else I through could help, but nobody has had any luck figuring out was is going on. Here's the setup:
A 316-2DP with a CP343-1 module. The CP343-1 module has an ip address of 10.0.0.14, and the PC running the OPC server has an ip address of 10.0.0.1. This is a completely isolated network. The 316-2DP also has 2 OP17 attached via the MPI interface, and about 12-15 slave Profibus modules attached through the Profibus interface.
The MPI address are listed as below:
CPU - 2
CP343 - 3
Main OP17 - 5
Remote OP17 - 6
The PC is running KepWare KepServer and is configured to use the Siemens TCP/IP driver. For some strange reason, I loose my OPC communications from my PC to the PLC for no apparent reason, and the only way to regain communication is to STOP the CPU and wait a sec or two, then go back to RUN.
At first I wasn't sure what was going on. I've tried several different things. The CP343-1 card was replaced with a new one. System ran for 2 weeks reading data, then stopped again on Monday Feb 7th, 2005. First though was connection resources. I reconfigured the connection resources to allow 2 PG, 4 OP, and 4 S7 Standard communications which still leaves 2 available connection for the Other communications. (Other communications name pulled from SIMATIC Manager Communications tab of the online Module Information of the CPU 316-2DP. After downloading the new configuration, I was able to establish a connection for 20 minutes of type OP.
Under Kepserver I can configure the type as PC, OP, or PG. According to KepWare I can have 4 connections to a CP343-1 module, 2 of PC, 1 OP, and 1 PG. When I restart the CPU from RUN to STOP to RUN, I can connect and read data over an OP type of connection. However, this only lasts about 20 minutes. I can maintain a connection of PG, but this connection is not stable as every coupld of minutes it will drop off then return.
Has anyone seen this problem before, or have any ideas how this can be resolved? Disconnecting the OP17s make no difference, nor does disconnecting all the Profibus devices and Operator interfaces. WinCC also cannont communicate with the PLC. Siemens Hotline and KepWare are both researching this problem without much luck as of yet.
Any Ideas?