...
The device configuration is following:
Slot | Subslot | Module |
1 | 1 | „I Signed8" – 1 Byte Input data |
2 | 1 | „O Signed8" – 1 Byte Output data |
3 | 1 | „I Signed16" – 2 Byte Input data |
4 | 1 | „O Signed16" – 2 Byte Output data |
Table 37 Example configuration
Record Index | Data |
0x7000 | 3 byte of parameter data (read/write) |
The GSDML file for this example is located beside the application code:
"goal\appl\2015013_irj45\ac\01_pnio_io_mirror\gsdml"
...
This example requires a DHCP server to obtain an IP address. The device configuration is following:
Assembly ID | Size | Properties |
150 | 32 | Output Data |
100 | 32 | Input Data |
151 | 10 | Configuration Data |
Table 38 Example configuration
...
By default no IP address is set. Using a configuration tool (e.g. Industrial Communication Explorer) a valid configuration must be provided. The device configuration is following:
Slot | Subslot | Module |
1 | 1 | „64 bytes Input" – 64 byte input data |
2 | 1 | „64 bytes Output" – 64 Byte Output data |
Table 39 Example configuration
...
This example configures a static IP address at startup, which is 192.168.0.100. Any reconfiguration with the management tool will be overwritten after restart. The device configuration is following:
Assembly ID | Size | Properties |
150 | 32 | Output Data |
100 | 32 | Input Data |
151 | 10 | Configuration Data |
Table 40 Example configuration
...
By default no IP address is set. Using a configuration tool (e.g. Industrial Communication Explorer) a valid configuration must be provided. The device configuration is following:
Slot | Subslot | Module |
1 | 1 | „I Signed8" – 1 Byte Input data |
2 | 1 | „O Signed8" – 1 Byte Output data |
3 | 1 | „I Signed16" – 2 Byte Input data |
4 | 1 | „O Signed16" – 2 Byte Output data |
Table 41 Example configuration
...
This example implements an EtherCAT slave.
Configuration
Index | SubIndex | Name | DataType | Description |
0x200c | 0x00 | application object | UINT32 | example object |
0x200d | 0x00 | application object | UINT32 | example object |
0x200e | 0x00 | application object | UINT32 | example object |
0x200f | 0x00 | application object | UINT32 | example object |
0x6200 | 0x01 | Write State 8 Output Lines (SI1) | UINT8 | digital output data |
0x6200 | 0x02 | Write State 8 Output Lines(SI2) | UINT8 | digital output data |
0x6411 | 0x01 | Write Analog Output 16 Bit (SI1) | UINT16 | analog output data |
0x6411 | 0x02 | Write Analog Output 16 Bit (SI2) | UINT16 | analog output data |
0x6000 | 0x01 | Read State 8 Input Lines (SI1) | UINT8 | digital input data |
0x6000 | 0x02 | Read State Input Lines (SI2) | UINT8 | digital input data |
0x6401 | 0x01 | Read Analog Input 16 Bit (SI1) | UINT16 | analog input data |
0x6401 | 0x02 | Read Analog Input 16 Bit (SI2) | UINT16 | analog input data |
Table 42 EtherCAT example mappable objects
...
By default no IP address is set. Using a configuration tool (e.g. Industrial Communication Explorer) a valid configuration must be provided. The device configuration is following:
Slot | Subslot | Module |
1 | 1 | „64 bytes Input" – 64 byte input data |
2 | 1 | „64 bytes Output" – 64 Byte Output data |
Table 42 Example configuration
...
This application registers for firmware update events. It thus gets informed about events when the firmware of the communication module is updated.
...
17_mbtcp_
...
simple_io
...
Purpose
This example is based on the application 01_pnio_io_mirror, but adds the Media Redundancy Protocol (MRP).
Configuration
By default no IP address is set. Using a configuration tool (e.g. Industrial Communication Explorer) a valid configuration must be provided. The device configuration is following:
...
Slot
...
Subslot
...
Module
...
1
...
1
...
„64 bytes Input" – 64 byte input data
...
2
...
1
...
„64 bytes Output" – 64 Byte Output data
Table 42 Example configuration
The GSDML file for this example is located beside the application code:
"goal\appl\2015013_irj45\ac\16_pnio_io_mirror_mrp\gsdml"
Usage Hints
...
Modbus Simple I/O Example with basic Data Types: This example defines regions for every writeable data type and creates several data objects. Read-only objects (Input Register and Discrete Inputs) are provided by the application itself, read/write objects are provided by the stack.
The Data Regions are defined at the file goal_appl.h by APPL_COIL_REGION_START and APPL_HOLD_REG_REGION_START. The Indices of the Objects are defined similiarly by for e.g., APPL_DISC_INPUT_X.
18_opcua_basic
This application provides a simple demo for an OPC UA server. It features several data objects, methods and events. Please see the main documentation for specific OPC UA information.
19_opcua_extended
This application provides an extended demo for an OPC UA server used for the official conformance test. It features almost every data object, methods and events. Please see the main documentation for specific OPC UA information.
http_01_get
Purpose
This example shows usage of the web server. It shows implementing GET-request support.
Configuration
This example uses the configured IP address of the cc module. Check the Management Tool to get the IP address.
Usage Hints
Open the URL HTTP://<DEVICE-IP>:8081, where a simple web page is shown.
http_02_post
Purpose
This example shows usage of the web server. It shows implementing POST-request support.
Configuration
This example uses the configured IP address of the cc module. Check the Management Tool to get the IP address.
Usage Hints
Open the URL HTTP://<DEVICE-IP>:8080, where a simple web page is shown. There a small amount of data can be uploaded to the application.
http_03_list_res
Purpose
This example shows usage of the web server. It shows supporting of hirachical urls.
Configuration
This example uses the configured IP address of the cc module. Check the Management Tool to get the IP address.
Usage Hints
Open the URL HTTP://<DEVICE-IP>:8080, where a simple web page is shown. It provides several sub pages shown on the main page.
...
This example shows usage of the web server. It shows supporting of basic authentication.
Configuration
This example uses the configured IP address of the cc module. Check the Management Tool to get the IP address.
Usage Hints
This example creates 4 pages with separate authentication data:
URL | Credentials |
HTTP://<DEVICE-IP>:8080 | index:level0 |
HTTP://<DEVICE-IP>:8080/page1.html | page1:level1 |
HTTP://<DEVICE-IP>:8080/page2.html | page2:level2 |
HTTP://<DEVICE-IP>:8080/page3.html | page3:level3 |
When opening one of the listed urls the provides login credentials are required.
| Note |
|---|
This example modifies credentials of authentication level 0. If those settings are stored permanently in the CC module, firmware update will fail with default credentials. Reset settings to default value "" using the Management Tool. |
http_05_template_cm
Purpose
This example shows usage of the web server. It shows implementing GET-request support with templating for CM variables.
Configuration
This example uses the configured IP address of the cc module. Check the Management Tool to get the IP address.
Usage Hints
Open the URL HTTP://<DEVICE-IP>:8080, where a simple web page is shown. It demonstrates template replacement of template usage with CM variable reference.
The string [CM:12, 0] will be replaced with the IP address of the device.
...
This example shows usage of the web server. It shows implementing GET-request support with templating for a list.
Configuration
This example uses the configured IP address of the cc module. Check the Management Tool to get the IP address.
Usage Hints
Open the URL HTTP://<DEVICE-IP>:8080, where a simple web page is shown. It demonstrates template replacement of template usage with list support.
http_07_template_table
Purpose
This example shows usage of the web server. It shows implementing GET-request support with templating for a table.
Configuration
This example uses the configured IP address of the cc module. Check the Management Tool to get the IP address.
Usage Hints
Open the URL HTTP://<DEVICE-IP>:8080, where a simple web page is shown. It demonstrates template replacement of template usage with table support.
A table of sensors with different sensor values is generated.
net_01_udp_receive
Purpose
This example shows usage of the UDP. It shows implementing a echo server on a specific UDP port.
Configuration
This example sets the IP address 192.168.0.100/24.
Usage Hints
Using netcat the udp server can be tested. Just type some text, and the server will reply this message.
| Code Block |
|---|
netcat -u 192.168.0.100 1234 Testing the echo server using UDP! Testing the echo server using UDP! |
net_02_tcp_client
Purpose
This example shows usage of the TCP as a client. It shows how to connect to a TCP server.
Configuration
This example sets the IP address 192.168.0.100/24.
It expects a TCP server on a remote server with IP address 192.168.0.10 on port 1234.
Usage Hints
Using netcat a tcp server can be provided. Once the application runs, the client will send the following messages.
| Code Block |
|---|
netcat -l 192.168.0.10 1234 TESTSTRING 0TESTSTRING 1TESTSTRING 2TESTSTRING 3TESTSTRING 4 |
net_03_tcp_server
Purpose
This example shows usage of the TCP as a server.
Configuration
This example sets the IP address 192.168.0.100/24.
Usage Hints
Using netcat a connection to the TCP server can be established. Just type some text, and the server will send the following messages.
...