CIPer
TM
MODEL 50 CONTROLLER
–
INSTALLATION AND COMMISSIONING INSTRUCTIONS
43
31-00233-02
Engineering and Commissioning
Required Preparations
In order to access (with a laptop or PC) the CIPer Model 50 controller via Ethernet/IP for the first time, the default pass-
words are used. For IP connections, you may employ any one of the following two options:
Option 1: USB 2.0 Device (recommended)
This USB 2.0 Device interface is the recommended interface for downloading applications and firmware via WEBs N4. An
"A-Male to B-Male" USB cable is required.
Figure 33: A-male to B-male USB cable
For access via USB, the CIPer Model 50 controller has a permanent default IP address 192.168.255.241.
Your PC's IP address must match the CIPer Model 50 controller's default IP address subnet: We recommend
using DHCP or "Obtain an automatic IP address".
Option 2: Standard Ethernet Interface
The default IP address of Ethernet interface 1:
192.168.200.20
The default IP address of Ethernet interface 2:
192.168.201.20
In any case, your PC's IP address must match the CIPer Model 50 controller's default IP address subnet
(255.255.255.0).
Behavior of Outputs during Download
Table 17. Behavior of outputs during firmware download / application download
Analog, binary, and floating
outputs
Output behavior during firmware
download
Output behavior during application
download
Outputs of Panel I/O modules
As soon as "receive heartbeat" (the value
of which CANNOT be altered using WEBs
N4) expires, outputs go to safety position.
As soon as "receive heartbeat" (the value
of which CANNOT be altered using WEBs
N4) expires, outputs go to safety position.
Outputs of L
ON
W
ORKS
I/O
modules
As soon as "receive heartbeat" (the value
of which can be altered using WEBs N4)
expires, outputs go to safety position.
As soon as "receive heartbeat" (the value
of which can be altered using WEBs N4)
expires, outputs go to safety position.
Onboard I/Os
After the configured time-out, go to
safety position.
After the configured time-out, go to
safety position.
NOTE
These behaviors were determined using a test application with a cycle time of 10 seconds. A value update was
triggered every 10 seconds.
