36 • Fieldbus Controller
Fieldbus Controller 750-841
3 Fieldbus Controller
3.1 Fieldbus Controller 750-841
This chapter includes:
3.1.1 |
Description...................................................................................... |
38 |
3.1.2 |
Hardware......................................................................................... |
39 |
3.1.2.1 |
View......................................................................................... |
39 |
3.1.2.2 |
Device Supply.......................................................................... |
40 |
3.1.2.3 |
Fieldbus Connection ................................................................ |
41 |
3.1.2.4 |
Display Elements ..................................................................... |
41 |
3.1.2.5 |
Configuration and Programming Interface .............................. |
42 |
3.1.2.6 |
Operating Mode Switch ........................................................... |
43 |
3.1.2.7 |
Hardware Address (MAC-ID).................................................. |
44 |
3.1.3 |
Operating System............................................................................ |
45 |
3.1.3.1 |
Start-up..................................................................................... |
45 |
3.1.3.2 |
PLC Cycle ................................................................................ |
45 |
3.1.4 |
Process Image ................................................................................. |
47 |
3.1.4.1 |
Example of a Process Input Image........................................... |
49 |
3.1.4.2 |
Example of a Process Output Image ........................................ |
50 |
3.1.4.3Fieldbus specific Process Data Architecture for MODBUS/TCP51
3.1.5 |
Data Exchange ................................................................................ |
63 |
3.1.5.1 |
Memory Areas.......................................................................... |
64 |
3.1.5.2 |
Addressing ............................................................................... |
66 |
3.1.5.3Data Exchange between MODBUS TCP Master and I/O
Modules.................................................................................... |
69 |
3.1.5.4Data Exchange between Ethernet IP Master and I/O Modules 71
3.1.5.5Data Exchange between PLC Functionality (CPU) and I/O
Modules.................................................................................... |
72 |
3.1.5.6Data Exchange between Master and PLC Functionality (CPU)73
3.1.6 |
Starting up an ETHERNET TCP/IP fieldbus node......................... |
78 |
3.1.6.1 |
Note the MAC-ID and establish the Fieldbus Node ................ |
78 |
3.1.6.2 |
Connecting PC and Fieldbus Node .......................................... |
79 |
3.1.6.3 |
Determining IP Addresses ....................................................... |
79 |
3.1.6.4 |
Allocating the IP Address to the Fieldbus Node...................... |
80 |
3.1.6.5 |
Testing the Function of the Fieldbus Node.............................. |
83 |
3.1.6.6 |
Deactivating the BootP Protocol.............................................. |
84 |
3.1.7 |
Programming the PFC with WAGO-I/O-PRO CAA...................... |
85 |
3.1.7.1 |
WAGO-I/O-PRO CAA library elements for ETHERNET ...... |
89 |
3.1.7.2 |
IEC 61131-3-Program transfer................................................. |
90 |
3.1.7.3 |
Information on the web-based management system ................ |
93 |
3.1.8 |
LED Display ................................................................................... |
96 |
3.1.8.1 |
Blink code ................................................................................ |
96 |
3.1.8.2 |
Fieldbus status.......................................................................... |
97 |
3.1.8.3 |
Node status............................................................................... |
98 |
3.1.8.4 |
Fault Message via Blink Code from the I/O-LED ................... |
99 |
3.1.8.5 |
‘USR‘-LED ............................................................................ |
100 |
WAGO-I/O-SYSTEM 750 ETHERNET TCP/IP
|
Fieldbus Controller |
• 37 |
|
Fieldbus Controller 750-841 |
|
3.1.8.6 |
Supply voltage status ............................................................. |
100 |
3.1.9 |
Fault behavior ............................................................................... |
100 |
3.1.9.1 |
Fieldbus failure ...................................................................... |
100 |
3.1.9.2 |
Internal bus fault .................................................................... |
101 |
3.1.10 |
Technical Data .............................................................................. |
102 |
WAGO-I/O-SYSTEM 750 ETHERNET TCP/IP
38 • Fieldbus Controller 750-841
Description
3.1.1 Description
The WAGO 750-841 Programmable Fieldbus Controller (PFC) combines the functionality of an ETHERNET fieldbus coupler with the functionality of a Programmable Logic Controller (PLC). When the PFC is used as a PLC, all or some of its I/O modules can be control locally with the use of WAGO-I/O- PRO CAA. WAGO-I/O-PRO CAA is an IEC 61131-3 programming tool that is used to program and configure the 750-841 PFC. I/O modules which are not controlled locally, can be controlled remotely through the 10/100 Mbps ETHERNET Fieldbus port.
When power is applied to the PFC, it automatically detects all I/O modules connected to the controller and creates a local process image. This can be a mixture of analog and digital modules. The process image is subdivided into an input and an output data area.
The data of the analog modules is mapped first into the process image. The modules are mapped in the order of their position after the controller. The digital modules are grouped after the analog modules, in the form of words (16 bits per word). When the number of digital I/O’s exceeds 16 bits, the controller automatically starts another word.
The controller has 512 KB of program memory, 128 KB of data memory, and 24 KB of retained memory. The programmer has access to all fieldbus and I/O data.
To be able to send/receive process data via ETHERNET, the controller supports a series of network protocols. For the exchange of process data, the MODBUS TCP protocol and the Ethernet/IP protocol are available. However, the two communication protocols cannot be used together.
The protocol HTTP, BootP, DHCP, DNS, SNTP, FTP, SNMP and SMTP are provided for the management and diagnosis of the system.
The programmer has the option to use function modules for programming clients and servers for all transport protocols (TCP, UDP, etc.) via a socketAPI.
Library functions are available to extend the range of programming functions. The IEC 61131-3 library "SysRTC.lib" enables integration of a buffered real time clock with date (1 second resolution), alarm function, and a timer. In the event of a power failure, this clock is powered by an auxiliary supply.
The controller is based on a 32-bit CPU and is capable of multitasking (i.e., several programs can be run at the same time).
The controller has an internal server for web-based applications. By default, the controller’s built-in HTML pages contain information on the configuration and status of the PFC, and can be read using a normal web browser. In
WAGO-I/O-SYSTEM 750 ETHERNET TCP/IP