While this information is presented in good faith and believed to be accurate,
Honeywell disclaims the implied warranties of merchantability and fitness for a
particular purpose and makes no express warranties except as may be stated in its
written agreement with and for its customer.
In no event is Honeywell liable to anyone for any indirect, special, or consequential
damages. The information and specifications in this document are subject to
change without notice.
This document was prepared using Information Mapping® methodologies and
formatting principles.
UDC 2300, UDC 3000, UDC 3300, UDC 5000, UDC 6000, and UDC 6300 are U.S.
trademarks of Honeywell Inc.
Information Mapping® is a registered trademark of Information Mapping, Inc.
The UDC manual for RS422/485 ASCII communications option contains the following sections:
Section 1–Overview
Section 2–Installation
Section 3–Establishing Communications
Section 4–Read and Write Operations
Section 5–Reading, Writing, and Overriding Parameters on UDC 3000
Versa-Pro Controllers
Section 6–Reading, Writing and Overriding Parameters on UDC 5000
Ultra-Pro Controllers
Section 7–Reading, Writing, and Overriding Parameters on UDC 6000
Process Controllers
Section 8–Reading, Writing, and Overriding Parameters on UDC 6300
Process Controllers
Section 9–Reading, Writing, and Overriding Parameters on UDC 3300
Process Controllers
Section 10–Reading, Writing, and Overriding Parameters on UDC 2300
Process Controllers
Section 11–Operating the Controller with Communications Option
Section 12–ASCII Conversion Table
Section 13–Cable Specifications
Communication between your computer and the UDC Controller is accomplished for one piece of
information (parameter) at a time. Each parameter has an associated identifying code.
The Identifying Code and Format Code will be listed along with information pertaining to that
parameter.
The identifying codes are grouped in the same order as they appear in the controller configuration
prompts.
Table 1-1 lists the rules and regulations of configuration protocol.
Table 1-1Rules and Regulations for Configuration Protocol
ProtocolRule
Data Type
Transactions
ReadRead transactions can be performed in either UDC state:
WriteWrite transactions can only be performed in the Slave
BusyFollowing any Write message, a Busy indication is
ReadyA Ready transaction is required as the next message
Transaction LimitsIn a Write transaction, only single items are permitted to
The configuration protocol permits reading or writing of
data type transactions such as PV, SP, or Output, as well
as configuration type transactions such as Tuning,
Algorithm selections, etc.
Monitor or Slave.
mode.
returned.
request to determine if the information received was
correct.
be written, however, for Read transactions, single or
multi-item parameters may be requested.
Loopback
Checksum
Controller Address
Keyboard
Configuration
Loopback protocol is also provided for link tests. With this message
exchange you can test the Communications link between your computer
and the controllers on the link. The host computer sends a series of ASCII
characters to the desired device, and the device returns the characters it
received to the host computer.
There is an optional transaction called "Checksum" which is used to
increase security on the RS422/485 link. Used with any message
exchange, it enables both your computer and controller to detect messages
that have been interrupted by line noise.
Each controller will have its own specific address. If you have a 2 loop
controller, there will be a specific address for each loop.
Address, Baud Rate, and Parity are keyboard selectable as well as Shed
Time, Shed Mode, and Output Level.
The Installation section (Section 2) of the UDC Product Manual contains
information and drawings required to mount and wire the controller. Refer
to the Controller Product Manual for appropriate information regarding
the basic installation requirements.
When installing and wiring the controller, follow the practices that
conform to all local codes and ordinances. In addition, be aware of the
precautions you should take to avoid electrical noise.
Electrical noise is unwanted electrical signals that provide undesirable
effects. Digital equipment is especially sensitive to the effects of electrical
noise. The controller has built-in circuits to reduce the effects of this
noise.
For information concerning further reduction of electrical noise, refer to
"How to Apply Digital Instrumentation in Severe Electrical Noise
Environments" – in the UDC Controller Product Manual or Honeywell
Document 51-52-05-01.
This section contains the following information:
TopicSee Page
2.1Introduction
General
Electrical Noise Protection
5
5
5
2.2RS232 to RS485 Converters6
2.3Using a Black Box Converter
Wiring the Black Box converter and the link
Wiring connections
Link devices terminal connections
2.4Using a Westermo Converter
Wiring the Westermo converter and the link
Configuring the Westermo converter and the link
Wiring connections
Link devices terminal connections
Up to 16 devices on an RS485 link can be connected to your computer by
installing a Black Box or Westermo RS232 to RS485 converter between
the RS232 port on your computer and the devices on the RS485 link.
These devices include:
• UDC2300, UDC3000, UDC 5000, UDC3300, UDC6000, or
UDC6300 Controllers with an RS485 Communications Option
Table 2-1 lists the specific information needed to procure either of these
converters.
Table 2-1Converters
ArrangementDescription
Black Box
Converter
Using the RS232 port and a Black Box RS232 to RS485
converter installed between the RS232 port and the first
device on the link.
This converter is available from . . .
Black Box Corp
Pittsburgh PA..
Westermo
Converter
(Europe)
Model
IC109A - Stand alone RS232 to RS485/422 converter
with opto-isolation
Using the RS232 port and a Westermo RS232 to RS485
converter installed between the RS232 port and the first
device on the link.
The Westermo converter can be ordered from a
Honeywell sales office, Part Number 46210088-001.
A 2 meter shielded cable with Female/Male DB9/DB25
connectors for use between the PC communication port
and the Westermo box is also available,
Part Number 46210061-002
1Install an appropriate Serial Communication Connector between the
Computer serial port and the RS232 input connector of the Black Box
converter.
interfacing signals.
2Connect one wire to terminal 2 (–).
3Connect other wire to terminal 1 (+).
4Connect a 120 ohm resistor across 1 and 2.
5Set the jumpers on the Black Box converter Printed Circuit Board as
Figure 2-2 shows the recommended switch setting for the WESTERMO
converter.
Figure 2-3 shows the wiring diagram and terminal connections for wiring
the RS485 Westermo converter.
Follow the procedure in Table 2-4 to configure and wire the Westermo
converter.
Table 2-5 shows the terminal designation for the devices on the link.
Table 2-4Westermo Converter Configuration and Wiring Procedure
StepAction
1Install an appropriate Serial Communication Connector between the
Computer serial port and the RS232 input connector of the Westermo
converter. See the Westermo data sheet for the required interfacing
signals.
2Configure the switch settings on the Westermo converter as shown in
Figure 2-6.
3Connect the shield to terminal 5. See Figure 2-3.
4Connect one wire to terminal 3 (–).
5Connect other wire to terminal 4 (+).
6Connect a 120 ohm resistor across terminals 3 and 4.
7Create a chain of up to 16 Devices by connecting them with shielded
twisted pair wiring (Belden 9271 Twinax or equivalent) to a maximum
total length of 4000 feet(1250 meters).
(See Section 13—Cable Specifications.)
REFER TO TABLE 2-5 FOR TERMINAL DESIGNATIONS OF THE
DEVICES ON THE LINK
Section 3 – Establishing Communications and Testing
3.1Preparing the Controller for Communications
Introduction
Synchronization
Configurable
parameters
Each controller on the RS422/485 Communications link must be
configured at the controller level for certain parameters before
communications between the Host and the Controller can be
accomplished.
Before you attempt to exchange messages between your computer and the
controllers on the RS422/485 link, you must set up the controller for the
same form of data transmission that the host computer’s RS422/485
interface uses. This is called Synchronization.
You must match the controller Baud Rate and Parity with that of your
computer.
Table 3-1 is a list of parameters that should be configured, their
definitions, range of settings or selections, the procedure for entering the
information into the controller is found in Table 3-2.
Table 3-1Communications Parameters
ParameterDefinition
Communications
State
Enables or disables the Communication function in the
controller.
Communications
Address
ShedTerm used to describe a point in time when the controller,
Shed TimeThe number selected will represent how many sample
DuplexSelection made for transmission type. Two-wire
TX DelayConfigurable response delay timer allows you to force the
This is a number that is assigned to a controller (limited
to 15 controllers) that will be used during
communications. This number will be its address on the
link (address 0-99).
If your controller has two loops, each loop must have its
own individual address (i.e. Loop 1, #6; Loop 2, #7).
which had been working as a slave, reverts to an
independent, stand alone controller using its own inputs,
configuration data and control mode. Shed will happen
when a controller is in slave, the shed is not zero, and the
communication stops.
periods will elapse before the controller sheds from
computer control. Each period equals 1/3 second. 0 = No
shed.
transmission is half duplex. Four-wire transmission is full
duplex.
UDC to delay its response for a time period of from 1 to
500 milliseconds. Compatible with the host system
hardware/software.
3.1Preparing the Controller for Communications, Continued
Parameters,
continued
Table 3-1Communications Parameters, Continued
ParameterDefinition
Shed Controller
Mode and Output
Level
Shed Setpoint
Recall
This selection determines the mode of local control
whenever the controller is SHED from the slave mode.
• Last Mode and Output – The controller will return to
the same mode (Manual or Automatic) and Output
level that it was in before shed.
• Manual Mode, Last Output – The controller will return
to manual mode and the last output level it was in
before shed.
• Manual Mode, Failsafe Output – The controller will
return to manual mode at the output level selected at
ID code 40 – Failsafe Output Value.
• Shed to Automatic Mode – The controller will return to
automatic mode.
This selection determines what setpoint will be used if the
controller is shed from the communications link.
• TO LSP – The controller will use the last local setpoint
stored.
• TO CSP – The controller will store the last computer
setpoint and use it at the Local Setpoint (LSP1, LSP2,
or LSP3, whichever is in use).
ParityTransmitting each ASCII character requires 8 bits:
• 7 bits for the character code
• 1 bit (the eighth) for Parity, which may represent either
ODD or EVEN parity.
Thus, the controller can accommodate your computer's
choice of parity (odd or even) and perform parity checks
on your computer's data transmission. The controller will
return STATUS CODE 04 if it detects incorrect parity.
Baud RateThis is the transmission speed in bits per second. In
order to communicate properly, the controller must be set
to the same Baud Rate as your computer. The Baud
Rate selections are: 300, 600, 1200, 2400, 4800, 9600,
or 19,200.
Communication
Units
Communications
Setpoint Ratio
Communications
Setpoint Bias
This selection determines how the controller values are
expressed during communications:
Percent of span or Engineering units.
Ratio value for computer setpoint. The range is from
-20.00 to +20.00.
Bias value for computer setpoint. The range is from
3.1Preparing the Controller for Communications, Continued
Procedure
The procedure in Table 3-2 tells you what keys to press on the controller
keyboard, the upper and lower display indications, and the range of
settings available to you.
Not all prompts may be available for your particular controller.
Use ▲▼ to make adjustments to the range of setting or selection.
Table 3-2Controller Procedure for Communication Parameters
StepPressLower DisplayUpper Display
Range of Setting
or Selection
1
2
SET
UP
FUNC
COMMUN
successive presses of the [FUNCTION] key will sequentially display all the
functions and their values or selections.
To program your computer for communication with the various
controllers on the link, you write input and output statements to send and
receive ASCII character strings to and from the controller. (See ASCII and
Hexadecimal conversion table in Section 12.) You treat the controller like
any I/O device.
To send a request, you program your computer to output the appropriate
character string to the controller.
To get a response, you program your computer to input the expected
character string from the controller.
The following programming statements show how you would output a
request message and read the resulting response. This example is written
in Fortran and uses the following assignments:
• I/O Channel 5 for your computer's RS422/485 Transmit Data Line.
• I/O Channel 6 for your computer's RS422/485 Receive Data Line.
• I/O Channel 7 for your computer's printer or terminal.
Table 3-3 lists the programming statements for this example.
Table 3-3Programming Statements
StepStatementAction
Sending the
Request
Getting the
Response
Displaying
the
Response
10 Write (5,20)
20 Format (“XXXXXXX”)
30 Read (6,40) Reply
40 Format (12)
50 Write (7,60) Reply
60 Format (12)
Writing the character string the
character string XXXXXXX to I/O
channel 5 which transmits the
character string XXXXXXX to the
controller.
Reading the character string at I/O
Channel 6 which receives data
from the controller into reply.
Writing the contents of Reply to I/O
Channel 7, a printer or terminal.
Your computer communicates with the UDC controllers using the
RS422/485 link. Each communication takes place as a message exchange:
Your computer sends a request message (ASCII characters), and then
waits for the resulting response from the controller involved (ASCII
characters). Figure 3-1 shows how this occurs.
Figure 3-1Message Exchanges
Read request
Host
Host
Response
Write request
Busy
Ready
Status of Last
Transaction
UDC
UDC
23092
Sending requests
Your computer is the host, it initiates a message exchange. The UDC
controllers are respond-only devices.
When you send a Read request, the UDC responds with the data
requested. If you write configuration or override data into a UDC, the
UDC responds with a Busy message (0082xx). The host should send a
Ready message at which time the UDC will respond with a status of the
write transaction. Communication with a single UDC should not be faster
than 1/3 second.
Until the UDC completes processing of the data, any subsequent valid
message received is answered with a busy response.
Your computer queries a controller and indicates the communication
function, or operation, that the controller should perform by sending a
request message. Request messages are composed of standard fields,
separated by commas. Each field contains a certain kind of information,
which you must enter in order to have a valid request message.
Request message
fields
Figure 3-2 shows the request message fields and the selections that may be
entered into each field. Table 3-4 lists these selections and their
definitions.
Figure 3-2Request Message Fields
,,,,,
Station
Address
A two digit device
address – 01 to 99
NOTE: Two loop
controllers will have an
address assigned to
each loop. Specify the
specific address for the
loop with which you
want to communicate.
Comma
Delimiter
required to separate fields
Protocol Field
4204 –
selects checksum
protocol
0204 –
ignores checksum
UDC Status (hexadecimal)—see matrix below
– REQUEST –
=
Single Byte Decimal – unsigned (digital configuration list) – for
11
Parameter codes 128 to 255
=
Single Byte Decimal – unsigned (extended
41
list) – for Parameter codes 128 to 158 in extended configuration
Oxford Floating Point (analog configuration list) – for Parameter
=
18
codes 001 to 125
Oxford Floating Point (extended
=
48
Parameter codes 001 to 021 in extended configuration
ASCII Text (Loopback only)
=
DD
ASCII Text (Analog configuration list for parameter
=
I D
I D Code #103 - Totalizer value (UDC6300, UDC 3300 only)
Data Type Field
CRLF
Checksum Field
HH=2-digit Hex
representing
Data Field
READ – Item no. only
WRITE – Item no., value
READY – 000
LOOPBACK – ASCII text
analog configuration list) – for
calculated checksum
digital configuration
UDC State and Mode
0 = Slave, Manual
2 = Slave, Toggle between LSP/RSP*
4 = Slave, Automatic
6 = Slave, No Change
E = Monitor, No Change
Change from RSP to LSP or LSP to RSP
*
READ only in Monitor Mode
**
READ and WRITE in Control Mode
Used after WRITE to verify data transaction
Table 3-4 is a list of selections for the request message fields and their
definitions.
Table 3-4Request Message Fields Definitions
SelectionDefinition
Station AddressA two digit device address – from 01 to 99 – that
identifies the specific controller you are addressing. You
must assign a unique station address to each controller
on the link.
For a 2 Loop controller, two distinct addresses must be
configured. One address is used to designate Loop 1;
and one is used to designate Loop 2. Either address may
be used for transactions which are loop independent.
See "Preparing the Controller for Communications" in this
manual. A UDC will not respond to address 0 since the
address results in a disconnect.
Protocol FieldA four digit number that selects whether or not you are
going to use a Checksum Protocol (for increased data
security) with your message exchange.
• 4204 selects Checksum Protocol
– see “Checksum Protocol”
UDC State and
Mode
Protocol Class and
Operation Code
• 0204 ignores Checksum Protocol
Any sequence utilizing other than 4 or 0 in the first digit
results in an error with an error message returned.
A hexadecimal number that determines what state you
want the UDC to be in (monitor or slave) and the mode of
operation desired (manual or automatic). You can also
change the controller setpoint from Local setpoint to
Remote setpoint or vice-versa.
ATTENTION
mode will not be indicated in the response until the next
transaction.
A hexadecimal number that allows you to do a Loopback
or do a READ, WRITE, or READY transaction.
Table 3-4Request Message Fields Definitions, Continued
SelectionDefinition
Data Type FieldA two digit number that specifies the format, or data type,
of each of the parameters that can be accessed in the
UDC controller.
11 =Single Byte Decimal (unsigned) – used with
configuration protocol for digital parameter code
numbers 128 through 255.
41 =Single Byte Decimal (unsigned) – used with
configuration protocol of extended digital
parameter code numbers.
18 =Floating Point Format – used with configuration
protocol for analog parameters code numbers 001
through 125.
48 =Floating Point Format – used with configuration
protocol for extended analog parameter code
numbers.
DD = ASCII Text – Used with loopback protocol only.
I D = ASCII Text – Used with configuration protocol for
Analog Parameters ID Code #103 |
(UDC 6300, UDC 3300 only)
Data FieldThe data in this field is determined by the type of request:
• READ – three digit parameter code which identifies a
particular parameter for which you want to know the
value or selection.
• WRITE – three digit parameter code, which identifies a
particular parameter you want to change, a comma (,),
and the value or selection you want to enter.
• READY – three zero's (000) – used in conjunction with
a write request. Sent after a write request to verify that
the information transmitted was received.
• LOOPBACK – ASCII Text
Checksum Field
(Optional)
Carriage
Return/Line Feed
This field is a one byte hexadecimal value (two ASCII
characters) representing the binary sum, ignoring carries,
generated by adding the ASCII code for each character
in the message exchange, up to but not including the
checksum and the CR and LF characters.
• No Characters = No Checksum
• HH = two digit hexadecimal number representing the
calculated checksum
Terminates a message. The message will not be
exchanged unless used in this order (CR LF).
The response message tells your computer the present status of the
operation initiated by the request message. Response messages are
composed of standard fields, separated by commas.
Response message
fields
Each field contains a certain kind of information. Figure 3-3 indicates the
response message fields and lists the information that could be returned in
each field.
Figure 3-3Response Message Fields Information
– RESPONSE –
,,
Request Message Status Code
00 =
Request message received successfully
01 =
Data Type Code invalid
02 =
Request is invalid
04 =
Checksum protocol indicates a problem or a
parity error
UDC Status Code
UDC functioning properly and has performed the
00 =
operation
UDC received invalid data and aborted the operation
01 =
UDC is busy (Ret'd on WRITES)*
02 =
UDC cannot perform requested operation in current
04 =
mode
UDC performing Autotune or Accutune
06 =
UDC unable to perform request at present time (may
07 =
occur during writes to EEProm or when unit is in set up)
UDC error status has changed (device dependent status)
Table 3-5 is a list of the information contained in the response message
and their definitions.
Table 3-5Response Message Fields Definitions
Type of
Information
Request Message
Status Code
UDC Status CodeA two digit code that indicates whether or not the UDC
UDC State and
Mode
A two digit code that indicates whether or not the present
request message was successfully processed. For
detailed explanations and recovery procedures for these
codes, refer to ‘Request Message Status Codes” in this
section.
controller addressed is working correctly and has
performed the requested operation. For detailed
explanations and recovery procedures for these codes,
refer to “UDC Status Codes” in this sections.
A hexadecimal number that indicates whether the UDC
controller's present state is "Slave" or "Monitor" and
whether it is in Manual or Automatic mode using the
Local setpoint or Remote setpoint.
ATTENTION
mode will not be indicated in the response until the next
transaction.
Any change made in UDC State or Control
Definition
Alarm StatusA hexadecimal number that indicates the status of Alarm
#1 and #2 or both. It indicates when the Alarm is on or
has changed state since last communication. The change
of state indicator is a backup to the on/off state indicator.
If an alarm goes from off to on then off in between
consecutive communications, the on/off would not show
it. The change of state flag would show that it had
happened.
Data FieldThis field always returns the identifying number for the
parameter in the request message and the value for that
parameter (either an integer or field floating decimal
point).
Optional
Checksum Field
This field is a one byte hexadecimal value (two ASCII
characters) representing the binary sum, ignoring carries,
generated by adding the ASCII code for each character
of the response message, ignoring parity, up to but not
including the checksum. It is returned for 4204 requests
only. See “Checksum Protocol” in this section.
The codes, listed in Table 3-6, indicate whether or not the request message
was successfully processed. A suggested recovery procedure is listed for
those that indicate an error.
Table 3-6Request Message Status Codes
Request
Message
Status Code
00The request message was
successfully processed.
01Request message format
invalid.
02Request is invalid. The
controller addressed does not
support the requested
operation.
04Checksum indicated in the
request message differs from
the checksum the UDC
calculated. Or UDC has
detected incorrect parity for
character transmitted in
request.
All the controllers on the link return the UDC Status Codes listed in
Table 3-7. A suggested recovery procedure is listed for those that indicate
an error.
Table 3-7UDC Status Codes
UDC
Status
Code
00UDC functioning properly and
has received the message
correctly.
01UDC has received invalid data
from the computer and did not
perform the requested
operation.
02UDC is busy until the data
received is processed.
04UDC cannot perform the
requested operation in its
current mode.
ExplanationExampleSuggested Recovery
Data error: Configuration item
number incorrect, data out-ofrange or incorrect.
Returned after each write
when a controller is
processing a change to
configuration database.
1. Request error, request
illegal, request incorrect in
present state (Calib).
2. Requested illegal mode
change.
3. Data received in wrong
format.
Not applicable.
Check the UDC’s configuration
and limits.
1. Do ready request to see if
information received.
2. Wait, then re-send
request.
Check configuration with last
request. Check data field and
data type field.
The optional Checksum Protocol is used to increase security on the
RS422/485 link. This protocol enables both your computer and your UDC
to detect messages that the RS422/485 link has transmitted inaccurately.
Thus, this protocol makes the RS422/485 communications link more
reliable.
Failure to use checksum protocol could make the undetected error rate for
the RS422/485 link unacceptable for your process control application.
You can use the checksum protocol with any message exchange. The
UDC uses the protocol to check the transmission of request messages.
Your computer uses the protocol to check the transmission of response
messages.
When a message exchange includes checksum protocol:
• Your UDC can tell, with high probability, if the ASCII code in the
request message has changed during transmission from your computer.
• Your computer can tell, with high probability, if the ASCII code in the
response message has changed during transmission from the UDC.
To use Checksum Protocol, you change the format of the request message
as shown in Figure 3-4 as follows:
• You use a 4204 in the request format.
• You insert a 2-digit Hexadecimal number that represents the checksum
that you have calculated from the ASCII codes in the request message
as explained in “Calculating the Checksum”. See Section 12 for an
ASCII Conversion table and a Hexadecimal Binary table.
Figure 3-4Request Format for Checksum Protocol
ASCII code for these characters is added
to calculate the checksum
,
Address
Protocol Field
UDC Status
Data Type Field
Operation Dependent Data
CHECKSUM
Carriage Return
Line Feed
3.7Checksum Protocol (for Data Security), Continued
Calculating the
Checksum
Table 3-8 lists the procedure for calculating the checksum. See Figure 3-5
for an example.
Table 3-8Calculating the Checksum Procedure
StepAction
1Take the binary sum, ignoring carries generated by the most
significant bits, of the ASCII code for each of the message’s
characters, ignoring parity, up to but not including the CHECKSUM
field and the CR and LF characters. The final sum should be an 8-bit
binary number. See Section 12 for ASCII Conversion table and
Hexadecimal to Binary table.
2Convert the four least significant bits of this sum to the equivalent
hexadecimal digit. This becomes the least significant digit in the
CHECKSUM field.
3Convert the four most significant bits of this sum to the equivalent
hexadecimal digit. This becomes the most significant digit in the
checksum field.
3.7Checksum Protocol (for Data Security), Continued
Success or failure
After receiving a request that uses checksum protocol, the UDC calculates
the checksum of the characters received and compares this to the
hexadecimal number stated in the checksum field. Depending on whether
the checksums agree, the UDC returns either the “success” or “failure”
response. Figure 3-6 indicates what happens when checksum protocol
is used.
3.7Checksum Protocol (for Data Security), Continued
Success response
If the checksums agree – and no other problems are encountered – the
UDC returns the success response beginning with Request Message Status
Code 00. Figure 3-7 indicates this response.
Figure 3-7“Success Response” Message Fields
"success" response
0 0CR LF
Request Message
Status Code
UDC Status Code
UDC State and Mode
Alarm Status
Operation Dependent Data
CHECKSUM
Carriage Return
Line Feed
3.7Checksum Protocol (for Data Security), Continued
Failure response
If the checksums disagree, UDC ignores the request and returns the failure
response Request Message Status Code 04. To recover, your computer
repeats the operation. Figure 3-8 indicates this response.
Figure 3-8“Failure Response” Message Fields
"failure" response
Request Message Status Code
(checksum protocol indicates a problem or parity error)
The failure response may also show that there is a problem with the UDC.
In this case, the response would be:
Request message status code (CHECKSUM O.K.)
UDC Status Code (01 through 07 indicating an error)
UDC State and Mode
Alarm Status
Checksum (for the 4 previous characters)
04
00CR LF
CR LF
23089
Checksum Calculation
ATTENTION
After receiving a response that has checksum protocol, your computer
should perform the checksum calculations on the characters received, and
compare the results to the checksum in the response message. If the
checksums disagree, your computer should repeat the operation.
If there is a problem with the UDC itself, a UDC Status Code indicating
an error will be returned.
Shed happens when the controller, which has been working in "Slave,"
reverts to "Stand Alone" mode. Upon receiving a "Slave" message, the
controller resets the "SHED TIMER." If this timer expires before the next
valid message, the controller goes to stand alone operation. When the host
reconnects with a valid message, the response will indicate as 8 at the
third digit to indicate a restart after shed.
Thus SHED acts as a safeguard in case the computer or communications
link fail. If something prevents the computer from communicating with
the controller the device returns to the local control mode. The local
operator is then able to regain control over the controller and operate it by
the keyboard.
Shed Time works like a timer. The number selected will represent how
many sample periods there will be before the controller sheds from
computer control. You can configure the shed time to be one that is
between 1/3 second and approximately 83 seconds. 0 = No Shed.
This determines the mode of local control whenever the controller is shed
from the communication link.
This determines what setpoint will be used if the controller is shed from
the communications link.
How to enter this
information
Refer to “Preparing the Controller for Communications” in this section for
these selections and procedure for entering the information into the
controller.
Making sure all the
UDC 2300/3000/3300
controllers are on-line
Loopback message
exchange
Request message
Once you have established communications between the UDC
2300/3000/3300 controller and your computer and understand the message
exchange, it is a good idea to test communications to all the controllers on
the RS422/485 link. The LOOPBACK operation is an easy way to do this.
By including the appropriate address in the loopback operation, you can
send a series of characters from your computer to any device on the link.
After receiving these characters, the device addressed "echoes" back the
same characters. By comparing the characters sent to those returned, you
can tell whether communications are working correctly.
With this message exchange, you can test the communication link
between your computer and any controller.
• In the request message, your computer sends a series of characters to
the desired device.
• In the response message, the device returns the characters it received to
your computer.
Table 3-9 is an example of the Loopback Request Message with or
without the checksum.
Table 3-9Example of Loopback Request Message
ProtocolMessage Format
With ChecksumAA,4204,E8,DD,123456789ABC,CS CR LF
(12 characters max.)
Without Checksum AA,0204,E8,DD,123456789ABCDE, CR LF
When your computer sends a request message but doesn’t receive a
response, a message (either the request or the response) has been lost on
the link. As shown in Figure 3-9, problems in your computer, the link, or
the controller could cause a message to get lost.
Depending on how your programming handles messages, a lost message
could hang up your programming forever. Suppose your programming
uses a high-level language input command (in Fortran, READ) to retrieve
response messages from the input device or buffer fed by the link. Upon
executing this input command, your computer goes to the input device to
retrieve the response message and waits there until the data arrives. If a
message is lost, the message exchange is never completed. Thus, the input
command is left waiting for a response message that will never arrive.
As you can see, you must design your programming to handle the
possibility that the messages will get lost on the link. Make sure that your
programming includes a timing routine that detects the lost message and
aborts the pending input command.
Figure 3-9Lost Messages
Computer
executes
routine to send
request
message
A problem in your
computer or the RS
interface stops the
transmission of data
on the RS links
REQUEST
A problem in the RS
link stops the
transmission of data
Controllers can't process the request because –
• Your computer has changed Baud rate or parity.
Therefore, the controller is synchronized for data
transmissions different from those your computer
is now using.
3.10Recovering from Communications Failures, Continued
Timing message
exchanges to detect
lost messages
The flowchart in Figure 3-10 shows how to time a message exchange so
that you can tell if a message has been lost. (This is only an example, not
the suggested method.) Like all timing routines, this one includes a wait
and a read interrupt (in Basic, a PEEK) rather than a standard input
command.
Figure 3-10Timing a Message Exchange and Checking for a Response
Send the request message.
Wait the appropriate amount of time
On time out, check for the response message.
If controller has not responded,
If controller has responded,
process response message.
3.10Recovering from Communications Failures, Continued
Wait
Read Interrupt
How long to wait
Timing routine
The WAIT is the amount of time that your computer will wait for a
response before assuming that a message has been lost. If the response
doesn’t appear in the allotted time, your computer should retry the request
– up to three times. If your computer still hasn't gotten a response, your
programming assumes that communications on the link have failed and
calls the recovery or alarm routine.
The READ interrupt merely checks that input device or buffer for data,
instead of waiting indefinitely until data arrives.
Before you can program a timing routine, you must determine how long to
wait for a response. This wait must be at least as long as the response time
for the longest message exchange when executed at your computer's baud
rate. Also note that after the UDC has completed sending a response to
your computer, it will require up to 1/3 second of additional processing
time before it is ready to accept any new request message. If your
computer sends a request to the UDC while it is still busy processing the
previous request, it will respond with a BUSY status. Your computer can
handle this situation by re-trying the request.
Once you have established the appropriate wait time, you can program the
timing routine. To do so, you loop an instruction until the desired wait
time has elapsed, as shown in the figure on the previous page.
This timing routine is the simplest one you could program. But, it is not
efficient – your program waits the same amount of time for the shortest
message as the longest. You devise a more efficient routine, such as a loop
that checks for the response message each time "X" increments.
The Read operations (Data Retrieval) allow your computer to read data
from any controller on the RS422/485 link. Data retrieval for each
operation is accomplished through a message exchange between your
computer and the device you are addressing.
You can request the data for only one identifying code at a time, but, the
response may be a single variable or a three variable type depending on
the code used.
Read transactions can be performed in either UDC state: Monitor or Slave.
ATTENTION
Any change made in UDC state or control mode will not be
indicated in the response until the next transaction.
The parameters being read will be either Analog (codes 1 through 125) or
Digital (Codes 128 through 255) value or selections so that all Read
message formats must adhere to the standardization rules shown in the
tables that follow.
The Analog identifying Codes are codes 001 through 125. Each of these
codes are read using the Request and Response formats shown in tables
4-1 and 4-2.
Table 4-1 lists the request format with or without checksum, for Analog
I.D. Codes 001 through 125.
Where:
AA=Station Address (Each loop of a 2-loop controller has a
unique address – see "Message Exchange")
X=UDC State and Mode (Hex – see "Message Exchange")
NNN=Identifying Code for Analog Parameter (001 to 125)
CS=Checksum Value (2 digit hex – see "Checksum")
CR=Carriage Return
LF=Line Feed
Table 4-1Analog Parameter Request Format
Format TypeFormat
With ChecksumAA, 4204, X4, 18*, NNN, 0, CS CR LF
Without Checksum AA, 0204, X4, 18*, NNN, 0, CR LF
*Use 48 for extended anal og configuration I.D. codes (001 to 043), UDC 3300,
UDC 6000, UDC 6300 only.
Table 4-2 lists the response format, single or three variable with or
without checksum, for Analog I.D. Codes 1 through 125.
Where:
OO=UDC Type Error (00 = No Error)
SS=UDC Status
M=Mode (Hex – see "Message Exchange")
A=Alarm Data (Hex – see "Message Exchange")
NNN=Identifying Code for Analog Parameter
DDD.D =Floating Point Value
CS=Checksum (two digit hex – see "Checksum")
CR=Carriage Return
LF=Line Feed
Figure 4-1 is an example of a Read Analog Parameter message exchange;
specifically, Read the value of heat gain; Analog I.D. Code 001.
Figure 4-1Read Analog Parameter Message Exchange
request
Address
Protocol Field (without checksum)
UDC State and Mode
E = monitor, no change
4 = configuration, read
Data Type Code for Analog
Identifying Code for Heat Gain
Place Holder for Data Values
response
No UDC Error
No Change in Status
Monitor
No Alarm
Heat Gain Identifying Code
Value of Heat Gain
The Digital identifying codes are Codes 128 through 255. Each of these
codes are read using the Request and Response formats shown in Tables
4-3 and 4-4.
Table 4-3 lists the request format, with or without checksum, for digital
I.D. Codes 128 through 255.
Where:
AA=Station Address (Each loop of a 2 loop controller has a
unique address – see "Message Exchange")
X=UDC State and Mode (Hex – see "Message Exchange")
MMM=Identifying Code for Digital Parameter (128 to 255)
CS=Checksum Value (two digit hex – see "Checksum")
CR=Carriage Return
LF=Line Feed
Table 4-3Digital Parameter Request Format
Format TypeFormat
With ChecksumAA, 4204, X4, 11*, MMM, 0, CS, CR LF
Without Checksum AA, 0204, X4, 11*, MMM, 0, CR LF
*Use 41 for extended digital configuration I.D. codes (128 to 158), UDC 3300,
UDC 6000, UDC 6300 only.
Table 4-4 lists the response format, with or without checksum, for digital
I.D. codes 128 through 255.
Where:
OO=UDC Type Error (00 = No Error)
SS=UDC Status
M=Mode (Hex – see "Message Exchange")
A=Alarm Data (Hex – see "Message Exchange")
MMM=Identifying Code for Digital Parameter
DDD=Digital Value (always 3 characters)
CS=Checksum (2 digit hex – see "Checksum")
CR=Carriage Return
LF=Line Feed
Table 4-4Digital Parameter Response Format
Format TypeFormat
With ChecksumOOSSMA, MMM, DDD, CS CR LF
Without Checksum OOSSMA, MMM, DDD, CR LF
Example
Figure 4-2 is an example of a Read Digital Parameter message exchange;
specifically, read the algorithm selection: digital I.D. Code 128 and
maintain or change the UDC state to slave.
Figure 4-2Read Digital Parameter Message Exchange
request
Address
Protocol Field (without checksum)
UDC State and Mode
6 = slave, no change in mode
4 = configuration, read
Data Type Code for Digital
Identifying Code for Algorithm Selection
Placeholder for Data Value
response
No UDC Error
No Change in Status
Monitor
No Alarm
Algorithm Selection Identifying Code
PID-B
NOTE: Change to slave will not be noted until the next message exchange.
The Write operations allow your computer to write data type transactions
such as Overriding the PV, Setpoint, inputs as well as writing
configuration data such as Tuning Parameters, Algorithm Selection,
Setpoint Ramp Information, etc. to the controller.
Write transactions can only be performed in the Slave Mode.
In a Write transaction, only single items are permitted to be written.
A Ready transaction is required to determine if the information was
received.
Following any Write, a Busy indication is returned.
Table 4-5 lists the steps for the Write message exchange.
Table 4-5Write Message Exchange Steps
StepAction
1Do a Write request to change a parameter (see Table 4- 6).
2Receive a Busy response (see Table 4-7).
CAUTION
ATTENTION
3Send Ready request to see if the information has been processed
(see Table 4-8 ).
4Receive an “Is Ready” response (see Table 4-9 ).
5Do a Read request to check the value (OPTIONAL).
The data stored in non-volatile memory is expected to be retained for 10
years. However, additional writes will degrade the retentivity of the
non-volatile memory.
Any change made in UDC State or Control Mode will not be indicated in
the response until the next transaction.
The analog identifying codes are codes 001 through 125. The Write
request and response formats are shown in Tables 4-6, 4-7, 4-8, and 4-9.
Table 4-6 lists the write request format with or without checksum for
Analog I.D. Codes 1 through 125.
Where:
AA=Station Address (Each loop of a 2 loop controller has a
unique address – see "Message Exchange")
X=UDC State and Mode (Hex – see "Message Exchange")
NNN=Identifying Code for Analog Parameter (001 to 125)
DDD.D =Floating Point Value (see note 1)
CS=Checksum Value (two digit hex – see "Checksum")
CR=Carriage Return
LF=Line Feed
Table 4-6Write Request Format for Analog I.D. Codes
Format TypeFormat
With ChecksumAA, 4204, X5, 18*, NNN, DDD.D, CS CR LF (see note 1)
Without Checksum AA 0204, X5, 18*, NNN, DDD.D, CR LF (see note 1)
*Use 48 for extended anal og I.D. codes 001 through 043, UDC 3300, UDC 6000, or
UDC 6300 only.
Note 1Floating point values may look like this:
DDDD.DDD.DDD.DDD.DDD
-DDD.D-DDD.-DD.DD-D.DDD
They must have four characters and one decimal point as shown, negative
sign as an extra characters.
If the controller did not process the information, the controller will return
a four digit status code indicating an error in the third and fourth digit. See
“Status Codes.”
Table 4-7 lists the busy response that can be received, with or without
checksum, after a Write request that indicates a good write:
Where:
M=Mode (Hex - see “Message Exchange”)
A=Alarm Data (Hex – see "Message Exchange")
CS=Checksum (two digit hex – see "Checksum")
CR=Carriage Return
LF=Line Feed
Table 4-7“Busy” Response
Format TypeFormat
With Checksum0002MA, CS, CR LF
Without Checksum 0002MA, CR LF
After receiving a “Busy” response, enter a “Ready” request. Table 4-8 lists
the “Ready” request format, with or without checksum.
Table 4-8Ready Requests
Format TypeFormat
With Checksum03, 4204, 66, 11, 0, CS CR LF
Without Checksum 03, 0204, 66, 11, 0, CR LF
Figure 4-3 is an example of a Write of an analog parameters message
exchange; specifically to change the gain value from 5 to 10; analog I.D.
Code 001.
Figure 4-3Write Analog Parameter Message Exchange Example
request
Address
Protocol Format (without checksum)
UDC State and Mode
6 = slave, no change
5 = configuration, write
Data Type Code for Analog
Identifying Code for Gain
Gain Value of 10
busy response
ready request
03,0204,66,11, 0 CR LF
03 , 0204 , 65 , 18 ,010.0 , CR LF
8200
00
001 ,
is ready response
Request message received successfully
UDC functioning properly and performed operation
Control state, Automatic LSP Mode
No Alarm
(OPTIONAL) Do a READ operation for Code 001 to verify change to 10.
The digital identifying codes are Codes 128 through 225. The Write
request and response formats are shown in Tables 4-10, 4-11, 4-12, and 4-
13.
Table 4-10 lists the Write request format, with or without checksum, for
digital I.D. Codes 128 through 255.
Where:
AA=Station Address (Each loop of a 2 loop controller has a
unique address – see "Message Exchange")
X=UDC State and Mode (Hex – see "Message Exchange")
MMM=Identifying Code for Digital Parameter (128 to 255)
DDD=Digital Value (always three characters)
CS=Checksum Value (two digit hex – see "Checksum")
CR=Carriage Return
LF=Line Feed
Table 4-10Write Request Format for Digital I.D. Codes
Format TypeFormat
With ChecksumAA, 4204, X5, 11*, MMM, DDD, CS CR LF
“Busy” response
Without Checksum AA, 0204, X5, 11*, MMM, DDD, CR LF
*Use 41 for extended digital I.D. codes 128 through 159, UDC 3300, UDC 6000, or U DC
6300 only.
If the controller did not process the information, the controller will return
a four digit status code, indicating an error in the third and fourth digit.
See “Status Codes.”
Table 4-11 lists the busy responses that can be received with or without
checksum, after a write request that indicates a good write:
Where:
M=Mode (Hex - see “Message Exchange”)
A=Alarm Data (Hex – see "Message Exchange")
CS=Checksum Value (2 digit hex – see "Checksum")
CR=Carriage Return
LF=Line Feed
With ChecksumOOO2MA, CS, CR LF
Without Checksum OOO2MA, CR LF
“Ready” request
“Is Ready” response
After receiving a “Busy” response, enter a “Ready” request. Table 4-12
lists the “Ready” request format, with or without checksum.
Table 4-12Ready Request
Format TypeFormat
With Checksum03, 4204, 66, 11, 0 CS CR LF
Without Checksum 03, 0204, 66, 11, 0 CR LF
This is the response to the Ready request. Table 4-13 lists the “Is Ready”
response formats, with or without checksum.
Where:
SS=UDC Status
M=Mode (Hex - see “Message Exchange”)
A=Alarm Data (Hex – see "Message Exchange")
CS=Checksum Value (two digit hex – see "Checksum")
CR=Carriage Return
LF=Line Feed
Table 4-13“Is Ready” Response
Format TypeFormat
With Checksum00SSMA, CS, CR LF
Without Checksum 00SSMA, CR LF
To check the value of a change, do a “Read” for the particular (I.D. Code)
you have changed.
4.6Write Digital Parameters, Continued
Example
Figure 4-4 is an example of a Write of a digital parameter message
exchange; specifically, to change the setpoint ramp time to 60 minutes
(Code 174).
Figure 4-4Write Digital Parameter Message Exchange Example
request
Address
Protocol Format (without checksum)
UDC State and Mode
6 = slave, no change
5 = configuration, write
Data Type Code for Digital
Identifying Code for SP Ramp Time
SP Ramp Time in Minutes
busy response
03 , 0204 , 65 , 11 ,060 , CR LF
8200
00
174 ,
ready request
03,0204,66,11,000,0 CR LF
is ready response
Request message received successfully
UDC functioning properly and performed operation
Control state, Automatic LSP Mode
No Alarm
(OPTIONAL) Do a READ operation for Code 174 to verify change.
This section contains information concerning reading, writing, and
overriding parameters on the UDC 3000 Controllers. There are two types
of parameters:
• Data Transfer—these parameters include reading control data, option
status, and reading or changing setpoints or outputs.
• Configuration Data—all the configuration data is listed in the order in
which it appears in the controller.
Each type of parameter has the identifying codes listed with it. Follow the
message exchange rules listed in “Read and Write Operations.”
This section contains the following topics:
TopicSee Page
5.1Overview55
5.2Reading Control Data57
5.3Option Status58
5.4Miscellaneous Read Only’s59
5.5Setpoints61
5.6Using a Computer Setpoint62
5.7Overriding Input 163
5.8Canceling the Override64
5.9Reading or Changing the Output65
5.10Local Setpoint/PID Set Selection and Setpoint Ramp
Status
• Whenever analog parameters 001 through 107 (those that can be
changed via Communications) are changed, a write cycle occurs
immediately after receipt of the message.
Override Parameters
• Override analog parameters 123, 124, and 125 (computer setpoint,
output, and input) are not stored in non-volatile memory and can be
changed as frequently as desired with no effect on non-volatile memory
retentivity, but the controller must remain in slave mode.
68
69
71
74
75
76
78
79
81
82
83
Digital Parameters
• Whenever digital configuration parameters 128 through 250 are
updated via communications, the non-volatile memory is updated as
soon as the message is received.
Doing a Read of I.D. Code 185 listed in Table 5-2 will tell you which of
the available options are enabled/installed or disabled/not installed.
Table 5-2Option Status
Parameter
Description
Option Status
(read only)
The data field in the response message will be a decimal number from
0 to 255. Convert the decimal number to binary as shown in Figure 5-1 to
determine which options are or are not active.
Figure 5-1Option Status Information
0 to 255
Convert decimal to binary
Identifying
Code
Format
Code
Range or Selection
18511See Figure 5-1
Input 2
Digital Inputs
Input 2
Adaptive Tune
Set Point
Programming
Not Applicable
Not Applicable
Not Applicable
0 = disabled
1 = enabled
0 = not installed
1 = installed
0 = not installed
1 = installed
0 = not installed
1 = installed
0 = not installed
1 = installed
EXAMPLE:
Binary
023
0
0
Input 2 – enabled
Digital Inputs - installed
Input 2 – installed
Set Pont Programming - Installed
5.4Miscellaneous Read Only’s - UDC 3000, Continued
Error status
definitions
Table 5-4 lists the UDC error status codes and their definitions.
Table 5-4Error Status Definitions
Status
Code
001Emergency ManualIndicates that the output of the unit which
002FailsafeError occurs whenever the control
004Working Calibration
Checksum Error
008Configuration Checksum
Error
ErrorDefinitions
has been in slave operation, is under
manual control, locally. Error remains
until local control is relinquished at the
controller.
reverts to failsafe operation and remains
as long as the condition exists.
Indicates that an error exists in the
working calibration data. Re-select the
inputs to load factory calibration data or
field calibrate the inputs.
Error exists in the configuration data.
Verify configuration data at the keyboard.
Checksum will be recomputed by
stepping the controller through the status
tests.
016Parameter Limit IndicatorA limit condition exists on one of the
following: PV, RV, Input 1, Input 2, Input
3, Computer Setpoint. User must
determine EXACT limit condition and
correct.
032Hardware FailureIndicates either a RAM test failure or
Input 1, Input 2, Input 3 failure on two
consecutive conversions.
064Restart After ShedError occurs whenever a shed of slave
override is performed. Error is reset
following a WRITE command to I.D.
Code 255 (064).
128Configuration /Calibration
Memory Changed
Error occurs whenever shed,
configuration, or calibration changed.
Also occurs whenever there is a change
of state in 001, 002, 004, 008, or 016.
Error is reset following a WRITE
command to I.D. Code 255.
You can use two separate setpoints in the UDC 3000 Controller. The
identifying codes listed in Table 5-5 allow you to select which setpoint
you want to use and to enter a value in Engineering Units or Percent
(whichever is selected at Code 161) for that setpoint via communications.
Make your selection using I.D. Code 173 and enter the value for the
setpoint chosen using I.D. Code 39 (SP 1) or 53 (SP 2).
Table 5-5Setpoint Code Selections
Parameter
Description
Local Setpoint #13918Value within the setpoint
Local Setpoint #25318Value within the setpoint
Local Setpoint
Select
Identifying
Code
17311000 = Local Set
Format
Code
Range or Selection
range limits
range limits
Point #1 only
001 = 2nd Local Setpoint
via keyboard or
communications*
Associated
parameters
*I.D. Code 131—second input function must be set to 0 (LSP).
Refer to Table 5-6 for the codes required to display or change any of the
parameters associated with setpoints.
5.6Using a Computer Setpoint (Overriding Controller
Setpoint) -
Overview
I.D. codes
Shed
Override display
UDC 3000
You can use a setpoint generated from the computer to override the
setpoint being used by the controller.
The value generated by the computer will have ratio and bias applied by
the controller.
Use the identifying code in Table 5-7 to enter the computer setpoint.
The computer setpoint override will continue until "SHED" from
communications occurs or the controller is placed into monitor mode
through communications. Doing periodic "SLAVE READS" within the
shed time will allow the override to continue until communication is
stopped and shed time elapses.
ATTENTION
indefinitely or until the Override is canceled. (See Override selection
I.D. Code 183.)
When SP is overridden, the left most digit in the upper display
becomes a "C."
0 Shed (code 154) allows the Override to continue
Associated
parameters
Table 5-7Computer Setpoint Selection
Parameter
Description
Computer Setpoint12518Within the Setpoint Range
Identifying
Code
Format
Code
Range or Selection
Limits in Engineering Units
or Percent.
Refer to Table 5-8 for the codes required to display or change any of the
parameters associated with the computer setpoint.
Table 5-8Computer Setpoint Associated Parameters
ParameterCode
Setpoint Limits007, 008
Local Setpoint #1039
Local Setpoint #2053
Local Setpoint Selection173
You can override the Input 1 value in the controller using I.D. Code 124
as shown in Table 5-9.
When you override the PV, the first digit in the upper display
becomes a “C.”
Table 5-9Input 1 Override Code
Parameter
Description
Override Input 112418Within the input 1 limits in
Identifying
Code
Format
Code
Range or Selection
Engineering Units or
Percent (whichever is
selected at I.D. Code
161).
The Override to Input 1 will continue until “SHED” from communications
occurs or the controller is placed into monitor via communications. Doing
Reads within the shed time will allow the override to continue until Reads
are stopped and shed time elapses (I.D. Code 154).
ATTENTION
0 Shed allows override to continue indefinitely or until
override is canceled. (See Override Selection, I.D. Code 183.)
Associated
parameters
Refer to Table 5-10 for the codes required to display or change any of the
parameters associated with Input 1.
Table 5-10Input Override Associated Parameters
ParameterCode
High/Low Range Values (Read Only)029,030
Temperature Units (Read Only)129
Input 1 Type (Read Only)168
Transmitter Characterization
5.10Local Setpoint/PID Set Selection/Setpoint Ramp Status
- UDC 3000
Overview
Read
Write
Identifying Code 250 lets you monitor or make selections for:
• Tuning Parameter Set #1 or #2
If Tuning Sets selection is “two keyboard” code 171 = 001
• Local Setpoint #1 or #2
If ”2 Local Setpoints” is selected 131 = 0, 173 = 1
• Run or Hold Setpoint Ramp or a Setpoint Program Data
If SP Ramp or SP Program is enabled 178 = 1 Program, 178 = 2 Ramp
Table 5-14 is a table of numbers that could be returned by the UDC 3000
controller. When a Read is requested for this I.D. Code (250) you can
determine which parameters are active from this table.
To Write information to the controller, select what parameters you want
from Table 5-14 and enter the associated number in the data field of the
Write request.
For example:
• Maintain TUNING SET #2
• Maintain LOCAL SET POINT #1
• CHANGE A SET POINT PROGRAM TO RUN
READ 250 response is 020 or 022
WRITE 250 (023), Response Busy
READ 250 Response is 023
Note: some of the numbers are Read only.
Table 5-14LSP/PID Set Selection and Setpoint Ramp Status
Listed on the following pages are the identifying codes for the parameters
in the various setup groups in the UDC 3000 controller. The table below
lists the setup groups and the table number in which they are listed. Most
of the parameters are configurable through the Host. Some are READ
ONLY and are indicated as such and cannot be changed.
Do a Read or Write (see “Read/Write Operations”) depending on your
requirements using the identifying code and format code listed in the
tables. The range or selection available for each range is listed in the
tables.
5.11Configuration Parameters - UDC 3000, Continued
Options
Table 5-22 lists all the I.D. Codes and ranges or selections for the function
parameters in the setup group “OPTIONS.”
Table 5-22Setup Group-Options
Parameter
Description
Digital Input #118611
Identifying
Code
Format
Code
Range or Selection
0 = None
1 = To Manual
2 = To Local Setpoint #1
3 = To Local Setpoint #2
4 = To Direct Action
5 = To Hold
6 = To PID 2
7 = PV = Input 2
8 = To Run
9 = Reset SP Program
10 = Inhibit PID Integral (I)
Action
11 = To Manual Failsafe
12 = Disable Keyboard
13 = To Automatic
14 = To Timer
15 = To Auto/Manual Station
This section contains information concerning reading, writing, and
overriding parameters on the UDC 5000 Ultra-Pro Controller. There are
two types of parameters:
• Data Transfer—these parameters include reading control data, option
status, and reading or changing setpoints or outputs.
• Configuration Data—all the configuration data is list in the order in
which it appears in the controller.
Each type of parameter has the identifying codes listed with it. Follow the
message exchange rules listed in “Read and Write Operations.”