SIMATIC Modbus/TCP PN and SIMATIC Modbus/TCP PN Red The products “SIMATIC Modbus/TCP CP” and “SIMATIC Modbus/TCP CP Red” are released for Standard CPUs, F CPUs and H CPUs. Refer to the technical data of your CPU for the available local data. Note the amount of local data required for the Modbus block. When using SIMATIC Modbus/TCP CP V4.3 you must use the blocks with FC10 “AG_CNTRL” (from the Current directory). S7-300 CPUs FW V3.2 and higherS7-400 CPUs FW V6.0 and higher Table 2 shows the CPs for which the following products are released.ĦAV6676-6MB00-6AX0 (packet)6AV6676-6MB00-6AD0 (download) SIMATIC Modbus/TCP CP and SIMATIC Modbus/TCP CP Red
#Profinet communication between plc license
The license cannot be transferred from one CPU to another. All Modbus/TCP blocks are multi-instance capable. Here the standard functions of the SIMATIC S7 library are used (AG_SEND and AG_RECV for communication via CP, T blocks for communication via the integrated PROFINET interface of the CPU). Native TCP connections are established for Modbus communication between SIMATIC stations and other Modbus devices. Unilateral or bilateral redundancy can be established depending on the partner. If a connection breaks down, the block automatically switches to another connection (can be parameterized in “SIMATIC Modbus/TCP CP Red” and “SIMATIC Modbus/TCP PN Red”). The sample CFC projects were created with PCS 7 V7.1 SP2 and PCS 7 V8 respectively.īlocks with the Redundancy function provide the option of establishing redundant communication. All Modbus/TCP blocks are released for PCS 7 V7.1, PCS 7 V8 and PCS 7 V9.x. The “SIMATIC Modbus/TCP PAC” product reads out the values of the base type 3 and the energy meters. The “SIMATIC Modbus/TCP CP”, “SIMATIC Modbus/TCP PN”, “SIMATIC Modbus/TCP PN Red” and “SIMATIC Modbus/TCP Red” products support function codes 1, 2, 3, 4, 5, 6, 15 and 16.
The following technical data applies for the SIMATIC Modbus/TCP blocks.īoth Server mode and Client mode are supported. If you have any idea to why this would be the case let me know what you think.This entry provides the technical data of the SIMATIC Modbus/TCP blocks and information about the CPUs and CPs for which the SIMATIC Modbus/TCP blocks are released. Both are set up the same minus address and naming convention. Well here is where is gets weird I have multiple Kuka robots one of them is communicating fine with the device and one is not. This would be caused by a configuration error on the Profinet setup. These errors pretty much mean that it does not recognize the Profinet device and there is an error transmitting the IO back and forth to between the two devices. Once the IO is mapped to its corresponding output I have a KSS00099 “Error on reading /writing PNIO-CTRL” and a KSS11000 “Device ac3 could not be started within 20000ms”.
When I start to map the IO in Work-Visual 6.0 it starts to have troubles. The PLC recognizes the device and communicates over safety this verifies that both he PLC can see the Robot and the Robot can see the PLC. The issue I am having is I have a Kuka robot that is using Profinet communication to send IO back and forth between itself in and the PLC.
#Profinet communication between plc software
Kuka Robot Software 8.5.8 Kuka Controller KRC4 PLC Siemens Profinet Version KRC4-Profinet_5.0
0 kommentar(er)
