● SFC 14 "DPRD_DAT"
● SFC 15 "DPWR_DAT"
SFC 81 "UBLKMOV" (for copying up to 512 bytes of data)
It should also be understood that if OCM Communication by Priority is configured, the communication will not be changed at the loop control point
Quantities are continuously copied to/from working memory in blocks of up to 240 bytes. Therefore, it should be done while the user program is running
Copy the data.
Quantity name
① Analog input and analog output
② Digital input
③ digital output
3.2 SNMP Communication Service
availability
SNMP V1, MIB-II communication services can be used with integrated PROFINET interfaces and using version 2.2 or later
Firmware for the CPU.
Stats
SNMP (Simple Network Management Protocol) is the standard protocol for TCP/IP networks.
3.3 Open communication over Industrial Ethernet
demand
● Since STEP 7 V5.4 + SP4
Feature
Cpus with integrated PROFINET interfaces support over industrial Ethernet starting with firmware V2.3.0 or V2.4.0
Open communication function (referred to as: Open IE communication)
Open IE communication provides the following services:
● Connection-oriented protocols
- TCP compliant with RFC 793, connection type B#16#01, firmware V2.3.0 and later
- TCP compliant with RFC 793, connection type B#16#11, firmware V2.4.0 and later
- ISO-on-TCP compliant with RFC 1006, firmware V2.4.0 and higher
● No connection protocol
- UDP compliant with RFC 768, firmware V2.4.0 and later
Attributes of the communication protocol
The following protocol types are included in data communication:
● Connection-oriented protocols:
These protocols establish a (logical) connection to a communication partner before the data transfer and then after the transfer is complete
The connection needs to be closed. When the security of data transmission is particularly important, connection-oriented protocols are used. Usually pass
Multiple logical connections can be established over a single physical cable.
FB for open communication over "Industrial Ethernet" supports the following connection-oriented protocols:
- TCP compliant with RFC 793 (connection types B#16#01 and B#16#11)
- ISO-on-TCP according to RFC 1006 (connection type B#16#12)
● No connection protocol:
These protocols can work without establishing a connection. This means there is no need to establish and terminate connections to remote partners
Answer. Connectionless protocols do not require confirmation to transmit data to remote partners; Therefore, data transmission is not secure.
FB for open communication over industrial Ethernet supports the following connectionless protocols:
- UDP compliant with RFC 768 (connection type B#16#13)
How to communicate with Open IE?
To allow the exchange of data with other communication partners, STEP 7 provides the following FB and under Communication Blocks in the Standard Library
UDT:
● Connection-oriented protocols: TCP, ISO-on-TCP
- FB 63 "TSEND" for sending data
- FB 64 "TRCV" for receiving data
- FB 65 "TCON" for connection
- FB 66 "TDISCON" for disconnection
- UDT 65 "TCON_PAR", whose data structure allows the connection to be parameterized
● No connection protocol: UDP
- FB 67 "TUSEND" for sending data
- FB 68 "TURCV" for receiving data
- FB 65 "TCON" for establishing local communication access points
- FB 66 "TDISCON" for parsing local communication access points
- UDT 65 "TCON_PAR", whose data structure can be parameterized to local communication access points
- UDT 66 "TCON_ADR" with remote partner addressing parameter data structure
Operator controls and indicators for CPU 313C-2 DP
Quantity name
email:1583694102@qq.com
wang@kongjiangauto.com