After the Reyrolle IO Server (i.e. CSTRDC1132.EXE) is installed, a small amount of configuration is required. Configuring the Server automatically creates a CSTRDC1132.CFG file which holds all of the topic definitions, as well as the communication port configurations. This file will automatically be placed in the directory which is specified via the "Configuration File Path".
To perform the required configurations, start up the program.
The application windows to the IO Server consists of a
menu line with 3 main menus . Each main menu will be as follows:
| Main menu | Sub menu |
| Configure | Com Port Settings |
| Topic Definition | |
| Server Settings | |
| Help | Browse Help File |
| About CSTRDC1132 |
Each of the configuration menu items are explained in the following chapters.
Please note : Screen shots used in this help file relates to a IO server with the name CstJDx9132 but all information also applies to the Reyrolle IO server named CstRDc1132.
To configure the communication
ports, invoke the /Configure/Comm Port Settings command. The
"Communications Port Settings" dialogue box will appear:
The following describes each field in this dialogue box:
Com Port
This field will display the communication port for this configuration.
Reply Time-out
This field is used to enter the amount of time (in seconds) the Reyrolle Controls network using the selected communication port will be given to reply to commands from the Reyrolle IO Server This time-out is sustained only when a Reyrolle Controls networks fails to respond. When the Reyrolle Controls networks is responding normally, there is no penalty.Note: the default value of 3 seconds should be sufficient for most configurations.
Parity
Parity for Reyrolle relay must be "None" or "Even" . "Even" is the default recommended value.
Stop Bits
Stop bits for Reyrolle relays must be "1" and cannot be changed.
Byte Size
Byte size for Reyrolle relays must be "8" and cannot be changed.
Baud Rate
Baud rate for Reyrolle relays can be configured according to requirements. The default recommended baud rate is "9600".
Once all entries have been made, select 0K to process the configuration for the communication port.
The user provides each Reyrolle
relay node with an arbitrary name which is used as the DDE topic name for
all references to that network.
Only ONE topic can be defined for each relay on the Reyrolle network.
To define the Topics (nodes), invoke the /Configurationf/Topic Definition command. The topic list dialogue box will appear:
To modify an existing topic, select the topic name and
click on Modify.
To define a new topic, click on Add.
It's also possible to double click
on the topic name
instead of using Modify.The "Topic Definition" dialogue box will
appear:
The following describes the field in this dialogue box:
Topic Name
This field is used to enter a Topic Name. (The same DDE Topic Name is entered in the InTouch "DDE Access Name definition" dialogue box described in the section "Using the DDE Server with InTouch The topic must be a unique name that is matched by the DDE clients (for example InTouch).
Poll Rate
This field tells the server how often it will try to update all the items defined under this topic. Please note that the DDE server is always doing its best. The IO server is able to process about 10 messages per second using 9600 baud serial link. If the pollrate is too low the IO server will still only manage 10 messages per second. The recommneded poll rate for LARGE systems(i.e. 64 relays or more) is 1000 ms (the default rate). A poll rate of 100ms is recommended for smaller systems.
Address
The address (written as a decimal integer value) of the node in the Reyrolle Controls network we want to communicate with. This is usually defined by a dip switch setting on the relay node or can be configured using the MMI panel push buttons on the relay.
Topic Type
The only topic type supported is the DC100 an can not be changed.
Comm Port...
If a communication port was previously defined for this
node, its identification will appear to the right of this button .If no
communication port has been defined, click on this button to associate the topic
with a communication port (additional topics may be associated with this same
port at a later time).
A number of parameters which
controls the internal operation of the Server can be set. In most cases,
the default settings for these parameters provide good performance and do not
require changing.
However, they can be changed to fine-tune the Server for a specific environment.
To change the Server's internal parameters, invoke the /Configure/5erver Settings command. The " Server Operational Parameters" dialogue box will appear:
The following describes each field in this dialogue box:
Configuration File Path
This field is used to specify the path (disk drive and directory) in which the Reyrolle server will save its configuration file. IO Server will use this path to load the configuration file the next time it is started. Note: Only the path may be modified with this field .The configuration file is always named CSTRDC1132.CFG .
Note: There is no limit to the number of configuration files created although each must be in a separate directory. When using the Reyrolle IO Server with InTouch it is good practice to place the configuration file in the application dIrectory.
Note: Each time the CSTRDC1132.CFG file is saved the old configuration file is saved as CSTRDC1132.CBK .
Protocol Timer Tick
This field is used to change the frequency, where the
Server checks for work to do. This should take approximately 2 to 4 times the
fastest rate desired to update data from the Reyrolle Controls Node. The default
setting is 50 msec which is the shortest period that can be configured.
NetDDE being used
Default value is unchecked. Must only be selected if DDE clients and IO servers are communicating over a LAN.
Start automatically as a Windows NT service
(Windows NT only) Default value is unchecked. Selecting this option will enable IO server to start up automatically as an NT service.
The Wonderware logger program is
primarily used for receiving error messages (default behavior), but can also be
used in a debugging situation to find out what is really happening inside the IO
server.
The Wonderware logger will log messages according to the options selected by right clicking the mouse button when the IO server icon appears in the Windows status bar.

Please note that when messages
are written to the Wonder Logger program this will slow down the performance of
the IO server.
If the configuration file does
not currently exist, or there has been a change in the configuration of the
Server, the Server will display the "Save Configuration" dialogue box:
This dialogue box displays the path where the Server is
going to save the current configuration file. The path may be changed if
necessary. Also, the path can optionally be recorded in the WlN.INI file by
selecting the "Make this file default
configuration" option. Doing so will allow the Reyrolle IO Server to
find the configuration file automatically each time it is started.
Note: There is no limit to the number of configuration files that may be created, although each must be in a separate directory.
The IO server will display the status of messages configured for active points in its status window ( main window) The window will display the status of active messages as "DUE" until the message has been serviced during the current polling cycle.
Click on Add. The "DDE Access Name Definition" Dialogue Box will appear:
Note: When New is selected, this dialogue box will be blank when it initially appears. Data has been entered here to illustrate the entries which are made.
The following fields are required entries when entering a DDE Access Name Definition:
DDE Access Name
Enter an arbitrary name which will be used in InTouch tagname definitions to refer to the topic (Reyrolle Controls Node). (It is generally advisable that the same name defined for the Reyrolle topic is used here.)
IO Application/Server Name
Enter the application name, CSTRDC1132.
DDE Topic Name
Enter the name defined for the topic in the Reyrolle IO Server to identify the Reyrolle Controls node the IO Server will be accessing.
Note: This will usually be the same as the "DDE Access Name" although if desired, they may be different. However, the "DDE TopIc Name" must be the same name used when the topics were configured in the Reyrolle IO Server program. (Refer "configure topic" section for further details.)
Request Initial Data
This option should not be selected when the DDE application is a Wonderware IO Server (CSTRDC1132 is based on the Wonderware DDE Server Toolkit and is hence a Wonderware IO Server). With nonWonderware DDE Servers, this option may be need to be selected if the server does not send data immediately when a window appears on the screen.
Wait for Change
This option should be selected when the DDE application is a Wonderware IO Server.
Advise All Items
Selecting this option will cause the Reyrolle IO server to poll for all Reyrolle points that are defined in the tagname database, regardless of whether they are visible. This option MUST be selected for each topic configured for the Reyrolle relay network.
Advise only active items
This option must not be used.
Polling of Reyrolle relay events and measurands becomes enabled when the following tag names are configured :
Note: Each topic must have these two points configured to enable polling of all other points
To define the tagnames associated with the new "DDE Access Name", invoke the /Special/Tag Name Dictionary...command (In WindowMaker).
Click on New and enter the Tagname.(The tagname defined here is the name InTouch will use. The Reyrolle Server does not see this name.)
Select a tag type by clicking on the Type button. The "Choose tag type"
dialogue box will appear:
To access Reyrolle items, the type must be DDE discrete, DDE Integer,
DDE Real or DDE Message. Select the DDE type.
The "Details" box for the tagname will appear:
Select the Reyrolle topic (Reyrolle network node) by clicking on the DDE Access Name:...button. The "Select a DDE Access Name dialogue box will appear:
Select the appropriate topic name and click OK. (If the DDE Access Name has not been defined as previously described, click on New and then define the DDE topic now.)
The "Details" dialogue box will appear displaying the selected DDE Access Name:
For integers and reals fill in the Min EU, Max EU, Min Raw and Max Raw fields. These fields control the range of values which will be accepted from the Server and how the values are scaled. If no scaling is desired,Min EU should be equal to Min Raw and Max EU should be equal to Max Raw.
Enter the Reyrolle item/point name to be associated with this tagname in the Item field in the "Details" box:
(Refer to the Item (Point) Naming section below for complete details.)
Where applicable, the Use Tagname
as Item Name option may be selected
to automatically
enter the tagname in this field.
Note: The tagname can only be used if it follows the conventions
listed
in the "Item (Point) Naming " section
in this document.
Once all entries have been made, click on the Save button, (in the top of the dialogue box) to accept the new tagname. To define additional tagnames click on the New button. To return to the WindowMaker main screen, select Done.
The Reyrolle IO Server supports two groups of item
(point) names.
Items for the measurands (prefix
"MEA") and items for events (prefix "EV").
Tag names are in accordance with the following Reyrolle publications:
TABLE I
APPENDIX B - CLASS 2 MEASURANDS
| Tag no. | Information No. | Valid Frame Type | COT | Description |
| MEAI | 144 | 3 | 2,7 | Measurand I |
| MEAV | 145 | 3 | 2,7 | Measurands V |
| MEAP | 146 | 3 | 2,7 | Measurands P |
| MEAIN | 147 | 3 | 2,7 | Measurands In |
| MEAQ | 146 | 3 | 2,7 | Measurands Q |
| MEAVEN | 147 | 3 | 2,7 | Ven |
| MEAIL1 | 148 | 9 | 2,7 | IL1 |
| MEAIL2 | 148 | 9 | 2,7 | IL2 |
| MEAIL3 | 148 | 9 | 2,7 | IL3 |
| MEAVL1 | 148 | 9 | 2,7 | VL1 |
| MEAVL2 | 148 | 9 | 2,7 | VL2 |
| MEAVL3 | 148 | 9 | 2,7 | VL3 |
| MEAF | 148 | 9 | 2,7 | f |
Note: COT = Cause of Transmission
TABLE 2
APPENDIX C - ARGUS STANDARD EVENT CODES
| Standard codes: FUNCTION TYPE = 160 | ||||
| TAG NO. | EVENT | CODE | GI | TYPE |
| EVRESFCB | Reset FCB | 2 | no | 5 |
| EVRESCU | Reset CU | 3 | no | 5 |
| EVSTR | Start/Restart | 4 | no | 5 |
| EVARCPRG | ARC in Progress | 16 | yes | 1 |
| EVLERRES | Leds reset | 19 | no | 1 |
| EVTRPTST | Trip Test | 21 | yes | 1 |
| EVSETCHG | Settings Changed | 22 | yes | 1 |
| EVSETGRP1 | Setting Group 1 selected | 23 | yes | 1 |
| EVSETGRP2 | Setting Group 2 Selected | 24 | yes | 1 |
| EVSETGRP3 | Setting Group 3 Selected | 25 | yes | 1 |
| EVSETGRP4 | Setting Group 4 Selected | 26 | yes | 1 |
| EVIP1 | Input 1 | 27 | yes | 1 |
| EVIP2 | Input 2 | 28 | yes | 1 |
| EVIP3 | Input 3 | 29 | yes | 1 |
| EVIP4 | Input 4 | 30 | yes | 1 |
| EVTRPFAIL | Trip Circuit Fail | 36 | yes | 1 |
| EVGRPWARN | Group Warning | 46 | yes | 1 |
| EVAL | Alarm | 47 | yes | 1 |
| EVASTR | A-Starter | 64 | yes | 2 |
| EVBSTR | B-Starter | 65 | yes | 2 |
| EVCSTR | C-Starter | 66 | yes | 2 |
| EVEFSTR | E/F-Starter | 67 | yes | 2 |
| EVGENTRP | General Trip | 68 | no | 2 |
| EVAGENTRP | A-General Trip | 69 | no | 2 |
| EVBGENTRP | B-General Trip | 70 | no | 2 |
| EVCGENTRP | C-General Trip | 71 | no | 2 |
| EVGENSTR | General Starter | 84 | yes | 2 |
| EVCBF1 | Circuit Breaker Fail 1 | 85 | no | 2 |
| EVPFGHTRP | P/F General Highset Trip | 91 | no | 2 |
| EVEFGENTRP | E/F General Trip | 92 | no | 2 |
| EVEFGHTRP | E/F General Highset Trip | 93 | no | 2 |
| EVCBAREC | CB On By Auto-Reclose | 128 | no | 1 |
| EVRECBLCK | Reclose Blocked | 130 | yes | 1 |
APPENDIX D - ARGUS PRIVATE EVENT CODES
| Private Reyrolle codes: FUNCTION TYPE = 164 | ||||
| TAG NO. | EVENT | CODE | GI | TYPE |
| EVDL | Data Lost | 0 | no | 1 |
| EVALSSTR | A-Lowset Starter | 1 | no | 2 |
| EVBLSSTR | B-Lowset Starter | 2 | no | 2 |
| EVCLSSTR | C-Lowset Starter | 3 | no | 2 |
| EVEFLSSTR | E/F-Lowset Starter | 4 | no | 2 |
| EVALSTRP | A-Lowset Trip | 5 | no | 2 |
| EVBLSTRP | B-Lowset Trip | 6 | no | 2 |
| EVCLSTRP | C-Lowset Trip | 7 | no | 2 |
| EVEFLSTRP | E/F-Lowset Trip | 8 | no | 2 |
| EVADLTRP | A-Delayed Trip | 9 | no | 2 |
| EVBDLTRP | B-Delayed Trip | 10 | no | 2 |
| EVCDLTRP | C-Delayed Trip | 11 | no | 2 |
| EVEFDLTRP | E/F-Delayed Trip | 12 | no | 2 |
| EVAHS1TRP | A-Highset 1 Trip | 13 | no | 2 |
| EVBHS1TRP | B-Highset 1 Trip | 14 | no | 2 |
| EVCHS1TRP | C-Highset 1 Trip | 15 | no | 2 |
| EVEFHS1TRP | E/F-Highset 1 Trip | 16 | no | 2 |
| EVAHS2TRP | A-Highset 2 Trip | 17 | no | 2 |
| EVBHS2TRP | B-Highset 2 Trip | 18 | no | 2 |
| EVCHS2TRP | C-Highset 2 Trip | 19 | no | 2 |
| EVEFHS2TRP | E/F-Highset 2 Trip | 20 | no | 2 |
| EVSFSTR | SEF/REF Starter | 21 | yes | 2 |
| EVSFLTRP | SEF/REF Lowset Trip | 23 | no | 2 |
| EVSFS1TRP | SEF/REF Stage 1 Trip | 24 | no | 2 |
| EVSFS2TRP | SEF/REF Stage 2 Trip | 25 | no | 2 |
| EVAHS1STR | A-Highset 1 Starter | 26 | no | 2 |
| EVBHS1STR | B-Highset 1 Starter | 27 | no | 2 |
| EVCHS1STR | C-Highset 1 Starter | 28 | no | 2 |
| EVEFHS1STR | E/F-Highset 1 Starter | 29 | no | 2 |
| EVAHS2STR | A-Highset 2 Starter | 30 | no | 2 |
| EVBHS2STR | B-Highset 2 Starter | 31 | no | 2 |
| EVCHS2STR | C-Highset 2 Starter | 32 | no | 2 |
| EVEFHS2STR | E/F-Highset 2 Starter | 33 | no | 2 |
| EVCBO | Circuit Breaker Open | 34 | yes | 1 |
| EVSETGRP5 | Setting Group 5 Selected | 35 | yes | 1 |
| EVSETGRP6 | Setting Group 6 Selected | 36 | yes | 1 |
| EVSETGRP7 | Setting Group 7 Selected | 37 | yes | 1 |
| EVSETGRP8 | Setting Group 8 Selected | 38 | yes | 1 |
| EVCBF2 | Circuit Breaker Fail 2 | 39 | no | 2 |
| Reserved for future use | 40 | |||
| EVCBCLSF | CB Close Fail | 41 | yes | 1 |
| Reserved for future use | 42 | |||
| EVCDDB1S | CD DB1 state | 43 | yes | 1 |
| EVIP5 | Input 5 | 45 | yes | 1 |
| EVIP6 | Input 6 | 46 | yes | 1 |
| EVIP7 | Input 7 | 47 | yes | 1 |
| EVIP8 | Input 8 | 48 | yes | 1 |
| EVIP9 | Input 9 | 49 | yes | 1 |
| EVOP1 | Output 1 | 51 | yes | 1 |
| EVOP2 | Output 2 | 52 | yes | 1 |
| EVOP3 | Output 3 | 53 | yes | 1 |
| EVOP4 | Output 4 | 54 | yes | 1 |
| EVOP5 | Output 5 | 55 | yes | 1 |
| EVOP6 | Output 6 | 56 | yes | 1 |
| EVOP7 | Output 7 | 57 | yes | 1 |
| EVOP8 | Output 8 | 58 | yes | 1 |
| EVOP9 | Output 9 | 59 | yes | 1 |
| EVOP10 | Output 10 | 60 | yes | 1 |
| EVOP11 | Output 11 | 61 | yes | 1 |
| EVFWDA | Forward A | 62 | yes | 2 |
| EVRVSA | Reverse A | 63 | yes | 2 |
| EVFWDB | Forward B | 64 | yes | 2 |
| EVRVSB | Reverse B | 65 | yes | 2 |
| EVFWDC | Forward C | 66 | yes | 2 |
| EVRVSC | Reverse C | 67 | yes | 2 |
| EVFWDE | Forward E | 68 | yes | 2 |
| EVRVSE | Reverse E | 69 | yes | 2 |
| EVTRPCAL | Trip Count Alarm | 70 | yes | 1 |
| EVCBMAL | CB Maintenance Alarm | 71 | yes | 1 |
| EVFOE | Frequent Operations Exceeded | 72 | yes | 1 |
| EVDTCA | Delta Trip Counter Alarm | 73 | yes | 1 |
| EVWVS | Waveform Stored | 80 | no | 1 |
| EVRCI | Remote Control Interrupted | 81 | no | 1 |
| EVTRPLCK | Trip and Lockout | 82 | no | 1 |
| EVCLRC | Close and Reclaim | 83 | no | 1 |
| EVTRPREC | Trip and Reclose | 84 | no | 1 |
| EVCBC | Circuit Breaker Closed | 85 | yes | 1 |
| EVCLLI | Close and Lockin | 86 | no | 1 |
| EVRECDEL | Reclose Delay | 87 | yes | 1 |
| EVRECL | Reclaim | 88 | yes | 1 |
| EVLCK | Lockout | 89 | yes | 1 |
| EVFWDSEF | Forward SEF | 90 | yes | 2 |
| EVRVSSEF | Reverse SEF | 91 | yes | 2 |
| EVCLPCK | Cold load pickup | 100 | yes | 1 |
| EVCLTRP | Cold load trip | 101 | no | 2 |
| EVLCHKTRP | Line check trip | 102 | no | 2 |
| EVARCSTRA | ARC Start A | 103 | yes | 1 |
| EVABCKT | A backup time | 104 | no | 1 |
| EVABCKTRP | A backup trip | 105 | no | 1 |
| EVEXTRPB | External trip block | 106 | yes | 1 |
| EVSEFOF | SEF off | 110 | yes | 1 |
| EVAARCOF | All ARC off | 111 | yes | 1 |
| EVPFARCOF | P/F ARC off | 112 | yes | 1 |
| EVEFARCOF | E/F ARC off | 113 | yes | 1 |
| EVSEFARCOF | SEF ARC off | 114 | yes | 1 |
| EVAINOF | All inst off | 115 | yes | 1 |
| EVPFINOF | P/F inst off | 116 | yes | 1 |
| EVEFINOF | E/F inst off | 117 | yes | 1 |
| EVSEFINOF | SEF inst off | 118 | yes | 1 |
| EVHLWORK | Hot line working | 119 | yes | 1 |
| EVSCCTR | Scada control | 120 | yes | 1 |
| EVGENAL1 | General alarm 1 | 121 | yes | 1 |
| EVGENAL2 | General alarm 2 | 122 | yes | 1 |
| EVGENAL3 | General alarm 3 | 123 | yes | 1 |
| EVGENAL4 | General alarm 4 | 124 | yes | 1 |
| EVGENAL5 | General alarm 5 | 125 | yes | 1 |
| TAG | Info NO | ID |
| MEAIAP | 0 | IA (PRIMARY) |
| MEAIBP | 1 | IB (PRIMARY) |
| MEAICP | 2 | IC (PRIMARY) |
| MEAIEP | 3 | IE (PRIMARY) |
| MEAIAS | 5 | Ia (SECONDARY) |
| MEAIBS | 6 | Ib (SECONDARY) |
| MEAICS | 7 | Ic (SECONDARY) |
| MEAIES | 8 | Ie (SECONDARY) |
| MEAIAN | 10 | Ia (xIn) |
| MEAIBN | 11 | Ib (xIn) |
| MEAICN | 12 | Ic (xIn) |
| MEAIEN | 13 | Ie (xIn) |
| MEASUM2 | 23 | Sum I^2 |
From InTouch the state of the Reyrolle Controls node may be read by defining a tagname and associating it with the topic configured for the Reyrolle Controls node and using Status as the Item name.
From Excel, the status of the Reyrolle Controls node
communications may be read by entering the following formula in a cell:
=Reyrolle/topic/STATUS
Where topic is the topic name
which you would like to monitor the status of.