Datalogic Controller SC6000 User manual

REDS
Redundancy System
INSTALLATION MANUAL

DATALOGIC S.p.A.
Via Candini 2
40012 - Lippo di Calderara di Reno
Bologna - Italy
REDS Redundancy System
Ed.: 09/2008
ALL RIGHTS RESERVED
Datalogic reserves the right to make modifications or improvements without prior notification.
Datalogic shall not be liable for technical or editorial errors or omissions contained herein, nor for incidental
or consequential damages resulting from the use of this material.
Product names mentioned herein are for identification purposes only and may be trademarks and or
registered trademarks of their respective companies.
© Datalogic S.p.A. 2008
30/09/08

CONTENTS
1INTRODUCTION.......................................................................................................... 4
1.1 Overview ...................................................................................................................... 4
1.2 Basic Concepts ............................................................................................................ 4
1.3 System Components.................................................................................................... 4
1.3.1 Controller...................................................................................................................... 4
1.3.2 Lonworks Network........................................................................................................ 4
1.3.3 Presence Sensor and Encoder .................................................................................... 5
1.3.4 Redundancy Cable....................................................................................................... 5
2INSTALLING A REDUNDANT SYSTEM..................................................................... 6
2.1 Redundant SC6000 Reading Station Layout ............................................................... 6
2.2 Required Parts ............................................................................................................. 7
2.3 Redundant System Installation..................................................................................... 7
2.4 Notes............................................................................................................................ 8
2.5 Presence Sensors and Encoders................................................................................. 9
2.5.1 Presence Sensors mounting........................................................................................ 9
2.5.2 Normal package detecting............................................................................................ 9
2.5.3 Small package detecting.............................................................................................. 9
2.5.4 PS Line....................................................................................................................... 10
2.5.5 Encoders mounting .................................................................................................... 10
2.6 Redundancy Scanner Connections............................................................................ 11
2.6.1 T-Label station............................................................................................................ 11
2.6.2 L-Label station............................................................................................................ 12
2.7 REDS Parameters Configuration ............................................................................... 13
2.7.1 Master Working Controller REDS configuration......................................................... 13
2.7.2 Master Protecting Controller REDS configuration...................................................... 14
3REDS REDUNDANCY SYSTEMS............................................................................. 15
3.1 Diagnostic Procedures............................................................................................... 15
3.1.1 Startup........................................................................................................................ 15
3.1.2 Runtime...................................................................................................................... 15
3.1.3 Switch Over................................................................................................................ 15
3.1.4 Role Conflicts............................................................................................................. 15
3.2 Configuration.............................................................................................................. 16
3.2.1 Topology Parameters................................................................................................. 16
3.2.2 IP Addresses.............................................................................................................. 16
3.2.3 Alignment of the Configuration on the Protecting Controller...................................... 16
3.3 Standby-Active Switch Over....................................................................................... 17
3.3.1 Validation of the Diagnostic Information..................................................................... 17
3.3.2 Validation of the Parcel Error Count Condition........................................................... 18
3.4 WEB Sentinel Interface.............................................................................................. 18
3.4.1 WebSentinel Standard/Redundancy and Related Diagnostics.................................. 18
3.5 Host Interface............................................................................................................. 19
3.6 Power Supply............................................................................................................. 19
3.7 Dual Ethernet ............................................................................................................. 20
3.8 Genius Configuration Parameters.............................................................................. 20
3.9 Diagnostic Error Messages........................................................................................ 22
3.9.1 SC6000 error message syntax:.................................................................................. 22
3.9.2 SYNCHRONIZED Slave (Scanners) Error message syntax:..................................... 22

1 INTRODUCTION
1.1 OVERVIEW
The REDS function replicates the SC6000 controller, the presence sensor and the encoder
devices. The scanner network is not replicated as it already implements a form of redundancy.
1.2 BASIC CONCEPTS
REDS is based on the following:
• The redundant station can be logically seen as the combination of two separate stand-alone
stations connected through a “redundancy cable” (Lonworks + serial). The redundancy cable
connects the two Lonworks network halves and allows controller-to-controller communication
to exchange data that will be used to supervise and manage the role the controllers play in the
system.
• The companion controllers run the same software and configuration, except for one parameter
that assigns their topology role (Working/Protecting).
• The supported operating mode is “PackTrack”.
• The scanner network is fully managed by the Active controller. At initialization time the
scanners are informed about which controller they have to communicated with.
• Both the controllers distribute their own encoder to all the controlled scanners, however the
scanners only use the encoder from the Active controller and send their data only to it.
• The scanner replacement is always managed by the Active controller.
1.3 SYSTEM COMPONENTS
1.3.1 Controller
Two controllers are present in the Lonworks network. One of them acts as an Active unit and the
other as a Standby. In the event of failure, of either the active unit or of its local resources
(presence sensor, encoder), or of Parcel error count conditions, a Standby-Active “switch over” is
performed that guarantees system service after a short off-duty interval.
1.3.2 Lonworks Network
A single Lonworks network (split into two halves) is present that interconnects all the scanners to
both the controllers. The network is fully managed by the active controller.

1.3.3 Presence Sensor and Encoder
Each controller has its own presence sensor and encoder. The scanners use the active controller’s
encoder signal. No presence sensor signal is used by the scanners (only PackTrack mode is
supported).
1.3.4 Redundancy Cable
A dedicated cable (Lonworks + Serial) is used both to interconnect the two halves of the Lonworks
network and exchange redundancy data.

2 INSTALLING A REDUNDANT SYSTEM
2.1 REDUNDANT SC6000 READING STATION LAYOUT
to Host ETHERNET
SC6000 VAC INPUT
CAB-SC6103
AUX CAB-SC6013
Power/Net
PWO
Working
Controller Extended I/O
CAB-SC6003
LONWORKS
ENCODER
CAB-810x PS
PS Aux
BTK8100
CAB-810X
CAB-810x CAB-810x
DS8100A
DS8100A
DX8200A DX8200A
CAB-PWO 03
Redundancy
to Host ETHERNET
VAC INPUT
SC6000
CAB-SC6013
Power/Net
PWO
Extended I/O
CAB-SC6003
Protecting
Controller LONWORKS ENCODER
CAB-810x PS
PS Aux
BTK8100
CAB-810X CAB-810x
CAB-810x
DS8100A
DS8100A
DX8200A DX8200A
Example Redundant SC6000 Reading Station Layout

2.2 REQUIRED PARTS
Other than the various scanners used for the reading station, the following parts are necessary to
construct the redundancy station:
Name Description Part Number
SC6000 SC6000-1200 Universal Controller, Ethernet 935701000
PWO-480 J-box power unit 110/230 VAC 24 V 480 W 93ACC1767
CAB-SC6013 25p cable SC6000 to PWO PWR/NET, 3 m
(for Power/Net connections) 93A051337
CAB-SC6003 25p cable SC6000 to PWO I/O, 3 m
(for Extended I/O connections) 93A051338
CAB-SC6103 9p cable SC6000 to PWO, 3 m
(for serial connections if used) 93A051294
CAB-PWO 03 17p cable PWO to PWO, 3 m
(for redundancy) 93A051295
BTK-8100 Bus terminator kit (5 pcs) 93ACC1090
CAB-8101 17-pin scanner/scanner connection cable 1.2 m 93A051020
CAB-8102 17-pin scanner/scanner connection cable 2.5 m 93A051030
CAB-8105 17-pin scanner/scanner connection cable 5 m 93A051040
PH-1 Photocell kit - PNP 93ACC1791
OEK-2 Optical Encoder (Cab 10 meters + Spring) 93ACC1770
2.3 REDUNDANT SYSTEM INSTALLATION
1. Install the two SC6000/PWO groups, each with its own Encoder and PS, using the cables and
accessories listed in the parts table (standard hardware configuration). See the relative product
Reference Manual.
2. Install the scanner branches distributed equally between the two PWOs. See the relative
product Reference Manual and see the paragraph 2.6 Redundancy Scanner Connections of
this manual.
3. Connect the CAB-PWO 03 Redundancy cable between the two PWOs.
4. Decide which SC6000/PWO group will be Working Controller and which will be Protecting
Controller. Consequently set the PWO-480 switches as shown in the table below.
Topology Role LON TERM IN3 REDUNDANCY SRC SEL
Working ON ON PWR PWR 1 1 1 1 1 1
RE RE
STD STD
Protecting ON ON PWR PWR 1 1 1 1 1 1
RE RE
REV REV
Scanners 8K TERM 8K BYP
8k only ON ON OFF OFF
6k only OFF OFF ON ON
Both 6k and 8k OFF OFF OFF OFF
5. Power up the system and perform a Restore Default with Environmental Parameters on both
SC6000s: With Genius
 Menu Bar  Device Menu  Send with Options  select
Default Parameters + Environmental Parameters
 OK
6. Disconnect the Protecting Controller from the PWO.

7. Completely configure the Working Controller as follow:
a. Configure the Lonworks Networks using Network Wizard in Genius™. All Slaves will be
automatically configured in PackTrack™ Operating Mode.
b. Configure all Scanners for Code Selection, and send them the configuration.
c. Perform PackTrack Calibration and Mirror Calibration on all the scanners.
d. Configure the Redundancy Parameters on the SC6000 as described in paragraph 2.7.1
Master Working Controller REDS configuration of this document.
e. Configure the SC6000 for Code Selection, Data Formatting and all the necessary
parameters.
f. Send the configuration to the Working Controller with Options + Environmental
Parameters as follow: Genius
 Menu Bar  Device Menu  Send with Options 
select Environmental Parameters
 OK
NOTE
Wait for the system to respond. The Working Controller is ready when
the Net Mask appears on the SC6000 display.
Perform the DARP™ procedure as described in the SC6000
Reference Manual.
8. Power down the system, Disconnect the Working Controller from the PWO and connect the
Protecting Controller to the PWO, power up again the system.
9. Configure the Protecting Controller as described in the paragraph 2.7.2 Master Protecting
Controller REDS configuration of this document.
NOTE
Wait for the system to respond. The Protecting Controller is ready when
the message Protecting/Stand by appears on the SC6000 display.
Perform the DARP™ procedure as described in the SC6000
Reference Manual.
10. Power down the system connect the Working Controller to the PWO and Power up again the
system.
2.4 NOTES
NOTE
Both SC6000s must have the:
 Same Software release.
 Same Configuration.
NOTE
In case of SC6000 replacement for a REDS configuration, after
substituting the compact Flash and powering up the system (as
described in the SC6000 Reference Manual), wait for the system to
come up completely then power down the system and then power up
again.

2.5 PRESENCE SENSORS AND ENCODERS
2.5.1 Presence Sensors mounting
Both photocells must give to the controllers the same information at the same time, so some
precautions must be taken:
 The photocells must detect the same number of objects.
 The photocells must detect the same length of the object.
 If it is possible, avoid to mount the photocells at the beginning of the conveyor belt
because the packages should jump passing from one belt to the other.
There are two possibility to connect the two photocells.
2.5.2 Normal package detecting
The first possibility is to put the two photocells one above the other as show in the picture above.
This is the easiest and preferred way because the PS Line parameters and the Pack/Track origin
XYZ=0 are equal for both SC6000. In this case it is not possible to detect lower packs with both
photocells because they are at different height, one over the other.
2.5.3 Small package detecting
PS Line (mm)
XYZ=0
PS Working PS Protecting
If lower packages must be detect, it is possible to mount the two photocells side by side as show in
the picture above.
In this way it is possible to detect lower packs with both photocells because they are at the same
height, but there is a different position along the Y coordinate between the two SC6000. In this
case the Scanners Pack/Track Calibration must be taken from the Working photocell, see the
coordinate origin XYZ=0 on the picture above, and the following parameters must be set:
SC6000 Working Operating Modes PS Line (mm) = 0
SC6000 Protecting Operating Modes PS Line (mm) = negative value

2.5.4 PS Line
2.5.5 Encoders mounting
Both encoders must give to the controllers the same information at the same time, so some
precautions must be taken:
 The Encoders must be mounted on the same belt.
 The Encoders switch setting and wheels dimension must be the same.
 Make sure that both Encoders wheels have the right touching pressure on the belt in order
to avoid detaching that produce different speed.

2.6 REDUNDANCY SCANNER CONNECTIONS
Reliability and robustness of the system can be improved by connecting scanners together in a
particular way. In case of failure for the redundancy cable, which connects the two PWOs together,
the active device only sees the scanners physically attached to the relative PWO. In this case, the
best result will be achieved if the scanners in question read as much as possible over the entire
reading area. A possible solution to fulfill this is to connect scanners alternatively.
2.6.1 T-Label station
Sc8
Protecting
Working
Sc6
Sc4
Sc2
Sc7
Sc5
Sc3
Sc1
Protecting
Working
110-220 Vac
CAB-SC6003
CAB-SC6013
Host
Encoder 1
Presence sensor 1
CAB-810x BTK-8100
110-220 Vac
Presence sensor 2
CAB-810x BTK-8100CAB-810xCAB-810x
CAB-810x
CAB-SC6013
Host
CAB-PWO 03
Encoder 2
CAB-SC6003
CAB-810xCAB-810x
CAB-810x
Sc7Sc5Sc3 Sc1 Sc8
Sc2 Sc4 Sc6

2.6.2 L-Label station
Sc2
Sc5
Sc4
Working
Sc3
Sc6
Protectin
g
Sc1
Sc7 Sc8
Working Protecting
110-220 Vac
CAB-SC6003
CAB-SC6013
Host
Encoder 1
Presence sensor 1
CAB-810x
CAB-810x CAB-810x CAB-810x BTK-8100
110-220 Vac
Presence sensor 2
Sc1 Sc3 Sc5 Sc7 Sc2 Sc4 Sc6 Sc8
CAB-810x BTK-8100CAB-810xCAB-810x
CAB-810x
CAB-SC6013
Host
CAB-PWO 03
Encoder 2
CAB-SC6003

2.7 REDS PARAMETERS CONFIGURATION
2.7.1 Master Working Controller REDS configuration
After the Net and Scanner setting, complete the Working configuration as follow:
1. Redundancy Parameters Reds Functionality = checked.
2. Redundancy Parameters Topology Redundancy = Master Working.
3. Data Communication settings Built-in Ethernet Line Parameters IP_address
Active = insert the IP address of your Master Working.
4. Data Communication settings Built-in Ethernet Line Parameters IP_address
Stand-by = insert the IP address of your Master Protecting.
NOTE
 The IP_address Active must be different to the IP_address Stand-by.
 The two IP_address must be on the same sub-net.
5. Data Communication settings Built-in Ethernet Line Parameters IP_netmask
= insert the IP netmask.
6. If it is necessary set parameter: Data Communication settings Built-in Ethernet 
Line Parameters IP_ gateway = insert the IP gateway.
7. If it is necessary set parameter: Data Communication settings Built-in Ethernet 
Line Parameters IP_ dns1 = insert the IP dns1.
8. If it is necessary set parameter: Data Communication settings Built-in Ethernet 
Line Parameters IP_ dns2 = insert the IP dns2.
For the use of WebSentinel it’s necessary to set the parameters below:
9. Data Communication settings Built-in Ethernet Services SentinelClient
Enable = checked.
10. Data Communication settings Built-in Ethernet Services UserSocket#3
Status = checked.
NOTE
When an UserSocket# is used with WebSentinel, Data Tx must be
unchecked.

11. Digital I/O Setting Digital Output Lines Setting Output 6 Use = Redundancy.
NOTE
Only one Controller (the Working or the Protecting) will have the OUT-6
On. This output is used to inform the Host about which is the Active
Controller:
 OUT-6 On = Controller is Active
 OUT-6 Off = Controller is in Stand By
12. Operating Modes Minimum Distance Between Packs (mm) = 200.
13. Operating Modes Minimum Pack Length (mm) = 200.
14. Operating Modes Window Dimension (mm) = 200.
NOTE
This three parameters above are very important in order to avoid
Glitch and packs too short or too near not realistic as you can see in
the picture below.
200 mm
Glitch or
p
ack too short
15. Send the configuration to the Working Controller: Send with Options + Environmental
Parameters.
16. Save the configuration on the PC.
2.7.2 Master Protecting Controller REDS configuration
Starting from the Default, complete the Protecting Controller configuration as follow:
1. Load the Configuration of the Working Controller from the PC.
2. Change only the parameter: Redundancy Parameters Topology Redundancy =
Master Protecting.
3. Send the configuration to the Protecting Controller: Send with Options + Environmental
Parameters.

3 REDS REDUNDANCY SYSTEMS
3.1 DIAGNOSTIC PROCEDURES
The messages exchanged by the controllers over the redundancy cable are of two different types:
1. Notification of the redundancy role
2. Diagnostic status (presence sensor and encoder status)
Notifications are used both at initialization time and runtime (cyclic notifications).
Diagnostic status exchange (cyclic) conveys diagnostic data and is used only by the Standby
controller to validate the status of the active controller.
In order to enhance system reliability, in the event the response to the diagnostic polling is missing
over the serial channel, the request is redirected to the Lonworks network.
3.1.1 Startup
The initial status is determined from a lookup table that summarizes the description of all the
possible startup scenarios. The status assigned at startup depends on the assigned topology role,
redundancy role notifications, status of each controller at the moment of the role negotiation
(startup, initialization, runtime).
If the controllers are rebooted, the role negotiation algorithm has no memory about the role each
controller played before being powered down.
3.1.2 Runtime
During normal operations the controllers cyclically exchange data over the redundancy cable
(cyclic role notifications, cyclic encoder and presence sensor diagnostics).
The Standby controller compares its own presence sensor and encoder diagnostics to validate the
role of the Active controller.
Also the Active controller monitors the status of the Standby controller in order to raise an alarm
that alerts about the unavailability of the back up system.
3.1.3 Switch Over
The decision to switch over is taken by the Standby controller when it is sure that taking over
improves the overall performance of the whole system.
3.1.4 Role Conflicts
A role conflict may occur under various circumstances. In the event of a role conflict an automatic
negotiation will lead to the automatic correction of the configuration and definition of the correct
roles.

3.2 CONFIGURATION
If compared with a stand-alone station, no additional settings are needed on the slave scanners
when the REDS function is used. All the parameters related to REDS function have to be set on
the active SC6000 as described in the following. A simple procedure (see par. 3.2.3 Alignment of
the Configuration on the Protecting Controller) is needed to align the reserve SC6000.
3.2.1 Topology Parameters
Two new configuration parameters are defined in the SC6000:
• TOPOLOGY ROLE
(values: Working/Protecting): this parameter is operator assigned and strictly connected to the
Lonworks address of the controller (0: Working, 63: Protecting). It represents the role statically
assigned to a controller: “Working” for the main controller and “Protecting” for the reserve
controller.
• REDUNDANCY ROLE
(values: Active/Standby): this parameter is read-only and represents the role that the controller
dynamically plays in the redundant system at a certain moment.
When TOPOLOGY ROLE is set to “Working”, REDUNDANCY ROLE is set to “Active” by default.
When TOPOLOGY ROLE is set to “Protecting”, REDUNDANCY ROLE is set “Standby” by default.
3.2.2 IP Addresses
The companion controllers have different IP address values and the parameter tree of each
controller contains the IP addresses of both of them. In order to manage the interface to any
external host computer (Sentinel PC, Genius PC or generic host) when a switch over occurs, two
separate policies have been defined to select the IP address when switching over:
• if the parameter IP Address Selection Rule is set to TOPOLOGY ROLE, the IP address seen
by the external host changes after switching over (the topology role is static).
• if the parameter IP Address Selection Rule is set to REDUNDANCY ROLE, the IP address
seen by the external host remains unchanged after switching over.
It has to be noticed that the IP address selection rule is unique for all the possible external hosts
(Sentinel PC, Genius PC or generic host).
3.2.3 Alignment of the Configuration on the Protecting Controller
The Protecting controller must explicitly receive the same configuration as the Working controller,
except for the values of the parameters TOPOLOGY ROLE.

3.3 STANDBY-ACTIVE SWITCH OVER
The switch over is the situation that leads to a swapping of the role that the controllers play in the
redundant system.
The Standby controller is responsible for the decision to switch over as a final result of the
evaluation of the local and remote diagnostics or of parcel error count conditions.
This is how the switch over takes place:
1. The Standby controller notifies to the active controller the need to switch over. The notification
is sent over serial line and, alternatively over the Lonworks.
2. The Active controller sets its internal redundancy role to Standby, responds with an
acknowledge, issues an alarm of occurred switch over and restarts.
3. The Standby controller sets its internal redundancy role to Active and resynchronizes the
scanner network.
4. No requests are sent by the Standby controller to the scanners. The new initialization will
inform the scanners about which controller is active and where it has to take the encoder signal
from.
3.3.1 Validation of the Diagnostic Information
The validation of the role of the active controller is cyclically performed by the Standby controller,
based on the local and remote presence sensor and encoder diagnostics comparison. A failure in
the validation procedure leads to the switch over.
Because of the difficulty of determining in a simple way the conditions of “best encoder value” and
“best presence sensor value”, the validation implemented at this stage of the project takes into
account the following diagnostic events:
Diagnostic
Error Number Meaning
[130] Encoder Failure Timeout: no encoder signal for more than the programmed
timeout.
[131] Presence Sensor Failure: presence sensor failure
[132] No Phase Timeout: no reading phase for more than the programmed timeout.
[135] Encoder Failure: no encoder signal after two consecutive presence sensor events.
Using the above data allows the detection of the failure of the resources and, based on this
information it is possible to state the following:
• The Standby controller is able to validate the active controller’s presence sensor if the errors
131 and 132 are not present
• The Standby controller is able to validate the active controller’s encoder if the errors 130 and
135 are not present

On the Standby controller, the comparison of the local/remote data is based on a table that
summarizes the configuration of the validating rules that contains the following parameters both for
the encoders and for the presence sensors:
• Validation procedure enabling/disabling flag.
• Pending alarm validation filter (number of consecutive times the alarm is notified from the
Standby to the Active controller).
For more information about Diagnostics messages see the Parameters HELP in Genius.
3.3.2 Validation of the Parcel Error Count Condition
The validation of the role of the active controller is also performed by the Standby controller, based
on a parcel error count condition (comparison between Standby and Active controllers). A failure in
the validation procedure leads to the switch over.
A parcel error count condition is determined by the following parameters:
• Max Consecutive Lost Parcels: The Standby controller recognizes nmore consecutive Parcels
than the Active controller. Error number [163]
• Max % Of Lost Parcels (Out Of 100 Parcels): The Standby controller recognizes nout of 100
Parcels counted that the Active controller has not counted. Error number [165]
These error conditions do not generate diagnostic alarms since they cannot immediately determine
whether the fault is related to the presence sensor or the encoder. The two conditions are however
registered with their specific error numbers in the debug log as cause for the switch over.
For either condition, Sentinel signals simultaneous presence sensor and encoder faults.
After the switch over is concluded, the Standby (ex-Active) controller will establish whether the fault
is due to the presence sensor or the encoder. This may not be possible for particular cases: i.e.
Encoder Timeout, PS Timeout parameter combinations; slow conveyor speeds, percentage error
count condition.
3.4 WEB SENTINEL INTERFACE
WebSentinel ignores the redundant architecture and connects only to the controller that is currently
active. This is the only practical scenario with the current implementation of WebSentinel and
means that the only possible policy for the IP address association in the event of a switch over is to
the controller redundancy role (“seen” IP address remains unchanged after switch over).
3.4.1 WebSentinel Standard/Redundancy and Related Diagnostics
The companion controllers must be configured so that their IP address is associated to their
redundancy role, this way Sentinel always “sees” the same IP address regardless of which
controller is active.
WebSentinel interfaces only to the active controller and has no knowledge about the Standby
controller and its IP address.
In the event of a switch over, WebSentinel will connect to the new active controller.
Two separate operating modes are possible:

Standard: no diagnostic digital input information about the Standby system is reported:
Input 1 = PS – No presence sensor signal for an interval that is too long
Input 2 = ENC – No encoder signal for an interval that is too long
Redundancy: diagnostic digital input information about the Standby system is reported. The digital
input diagnostic information of the active controller is replaced with the diagnostics of both the
controllers (3 inputs Active + 4 inputs Standby + 1 input for communication)
Input 1 = PWA – Failure of the power supply of the active unit
Input 2 = ENA – Failure (or warning) of active unit’s encoder signal
Input 3 = PSA – Failure (or warning) of active unit’s presence sensor signal
Input 4 = PWS – Failure of the power supply of the standby unit
Input 5 = ENS – Failure (or warning) of standby unit’s encoder signal
Input 6 = PSS – Failure (or warning) of standby unit’s presence sensor signal
Input 7 = SBC – Failure of standby unit controller
Input 8 = RSL – Failure of the communication over the redundancy serial line
Note: in the event the Standby unit is down (or missing), the status of all its resources is declared
OK, except for the Standby controller itself.
3.5 HOST INTERFACE
Each controller can connect to the host computer through various serial and Ethernet ports.
• If the serial port is used, the host computer has to explicitly manage the switch over, keeping the
communications with the active controller. In this case, the reserved redundancy digital output
can be used to determine which controller is playing the active role.
• If the Ethernet port is used, two ways of interfacing to the host computer are possible according
to the IP address selection policy (the same as Sentinel Interface):
 If the IP address is associated to the topology role (Working/Protecting), after the switch
over the host computer sees the data coming from a different IP address. It will have to
explicitly manage the switch over keeping the communications with the active controller. In
this case, the reserved redundancy digital output can be used to determine which controller
is active.
 If the IP address is associated to the redundancy role (Active/Stand-by), after the switch
over the host “sees” the data coming from the same IP address, but it could experience
(and should manage) a temporary disconnection due to the timeout needed to refresh the
ARP table on the host TCP/IP stack that remains linked to the MAC addresses of the host
itself.
Various alarms can be sent by REDS to the host computer through the standard communication
ports, based on the standard SC6000 diagnostics.
3.6 POWER SUPPLY
Two separate paralleled power supplies are present to supply power both to the controllers and the
scanners. Under normal load conditions, the failure of one of the power supplies is tolerated by the
system. Voltage monitoring is present and used to generate alarms, however it does not affect the
switch over policy.

3.7 DUAL ETHERNET
Each controller (Dual Ethernet models) is able to interface to the host computer through two
different Ethernet networks. The dual Ethernet is intended to allow the physical replication of the
connection to the host computer, however dual Ethernet is not managed by REDS.
3.8 GENIUS CONFIGURATION PARAMETERS
Parameter Values (default) Function
Redundancy Parameters Redundancy Role Parameters
Reds Functionality Enable/Disable Enables/disables REDS
(only available to “Supervisor” –
read-only for “User”)
Sentinel Operating Mode Standard/Redundant Sentinel Agent operating mode.
Standard: if the system is
redundant, no diagnostic digital
input information about the
Standby system is reported
Redundant: diagnostic digital input
information about the Standby
system is reported. The digital
input diagnostic information of the
active controller is replaced with
the diagnostics of both the
controllers (4 inputs Active + 4
inputs Standby)
Topology Redundancy Role Master Alone/Master Working
/Master Protecting Topology Role. Explicitly connected to the Lonworks
address of the controller (0:
Working, 63 Protecting). The
selection of Topology Role to
Working/Protecting implies the
default value Active/Standby for
the Redundancy Role (read-only)
IP Address Selection Rule Redundancy Role (A/S)
/Topology Role (W/P) Defines the IP address selection
policy for the interface to both
Sentinel and the Host:
Topology Role: fixed IP address
Redundancy Role: variable IP
depending on the dynamic role
Redundancy Parameters
\Redundancy Switch
Parameters
Active/Standby switch over
configuration parameters
Check Presence Sensor
Failure Enabled/Disabled Presence sensor diagnostics affects the switch over
Presence Sensor Failure
Event Filter 1-10; (2) Number of times the alarm must be repeated before the switch over
occurs
Check Encoder Failure Enabled/Disabled Encoder diagnostics affects the