Skip to end of banner
Go to start of banner

Commissioning Modular Gateway Ethernet/IP with CODESYS

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 15 Current »

Here you will find a technical description of how to configure the KUNBUS gateway Ethernet/IP with CODESYS.

System overview

these devices have been used for this application note

  • KUNBUS Gateway Ethernet/IP

  • Revolution Pi Core 3 (3+, S) or Connect (+, S)

please connect your devices as shown in the illustration below

Preparation

Please follow the instructions of the checklists:

 /etc/dhcpcd.conf shown in line 50-52
# A sample configuration for dhcpcd.
# See dhcpcd.conf(5) for details.

# Allow users of this group to interact with dhcpcd via the control socket.
#controlgroup wheel

# Inform the DHCP server of our hostname for DDNS.
hostname

# Use the hardware address of the interface for the Client ID.
clientid
# or
# Use the same DUID + IAID as set in DHCPv6 for DHCPv4 ClientID as per RFC4361.
# Some non-RFC compliant DHCP servers do not reply with this set.
# In this case, comment out duid and enable clientid above.
#duid

# Persist interface configuration when dhcpcd exits.
persistent

# Rapid commit support.
# Safe to enable by default because it requires the equivalent option set
# on the server to actually work.
option rapid_commit

# A list of options to request from the DHCP server.
option domain_name_servers, domain_name, domain_search, host_name
option classless_static_routes
# Respect the network MTU. This is applied to DHCP routes.
option interface_mtu

# Most distributions have NTP support.
#option ntp_servers

# A ServerID is required by RFC2131.
require dhcp_server_identifier

# Generate SLAAC address using the Hardware Address of the interface
#slaac hwaddr
# OR generate Stable Private IPv6 Addresses based from the DUID
slaac private

# Example static IP configuration:
interface eth0
static ip_address=192.168.168.70/24
#static ip6_address=fd51:42f8:caae:d92e::ff/64
#static routers=192.168.0.1
#static domain_name_servers=192.168.0.1 8.8.8.8 fd51:42f8:caae:d92e::1

# Example static IP configuration:
interface eth1
static ip_address=192.168.1.100/24

# It is possible to fall back to a static IP if DHCP fails:
# define static profile
#profile static_eth0
#static ip_address=192.168.1.23/24
#static routers=192.168.1.1
#static domain_name_servers=192.168.1.1

# fallback to static profile on eth0
#interface eth0
#fallback static_eth0

# Prioritize wlan0 routes over eth0 routes.
interface wlan0
        metric 100

Create a CODESYS Project

Implementation

Note:

  • The older version 1.2.1.0 is used here, as CODESYS version 3.5 SP17 is used. If SP18 is used, the latest version 1.3.0.0 must be selected.

PROGRAM PLC_PRG
VAR
	status: BYTE;
	res1: BYTE;
	res2: BYTE;
END_VAR
Output_EthernetIP_GW:=33;
Output_EthernetIP_Exclusive:=44;

res1:=Input_EthernetIP_GW;
res2:=Input_EthernetIP_Exclusive;
  • No labels