Solid state equipment has operational characteristics differing from those of electromechanical equipment. Safety Guidelines for the Application,
Installation and Maintenance of Solid State Controls (publication SGI-1.1
http://literature.rockwellautomation.com
) describes some important differences between solid state equipment and hard-wired electromechanical
devices. Because of this difference, and also because of the wide variety of uses for solid state equipment, all persons responsible for applying this
equipment must satisfy themselves that each intended application of this equipment is acceptable.
In no event will Rockwell Automation, Inc. be responsible or liable for indirect or consequential damages resulting from the use or application of this
equipment.
The examples and diagrams in this manual are included solely for illustrative purposes. Because of the many variables and requirements associated
with any particular installation, Rockwell Automation, Inc. cannot assume responsibility or liability for actual use based on the examples and
diagrams.
No patent liability is assumed by Rockwell Automation, Inc. with respect to use of information, circuits, equipment, or software described in this
manual.
Reproduction of the contents of this manual, in whole or in part, without written permission of Rockwell Automation, Inc., is prohibited.
Throughout this manual, when necessary, we use notes to make you aware of safety considerations.
available from your local Rockwell Automation sales office or online at
Identifies information about practices or circumstances that can cause an explosion in a hazardous environment, which may
lead to personal injury or death, property damage, or economic loss.
Identifies information that is critical for successful application and understanding of the product.
Identifies information about practices or circumstances that can lead to: personal injury or death, property damage, or
economic loss. Attentions help you identify a hazard, avoid a hazard, and recognize the consequence.
Labels may be on or inside the equipment, such as a drive or motor, to alert people that dangerous voltage may be present.
Labels may be on or inside the equipment, such as a drive or motor, to alert people that surfaces may reach dangerous
temperatures.
Allen-Bradley, Datasite, Rockwell Automation, and TechConnect are trademarks of R ockwell Automation, Inc.
Trademarks not belonging to Rockwell Automation are property of their respective companies.
Preface
Read this preface to familiarize yourself with the rest of the manual. It provides
information concerning:
• who should use this manual
• the purpose of this manual
• related documentation
• conventions used in this manual
Who Should Use this
Use this manual if you are responsible for designing, installing, programming,
or troubleshooting control systems that use DataSite controllers.
Manual
You should have a basic understanding of electrical circuitry and familiarity
with relay logic. If you do not, obtain the proper training before using this
product.
Purpose of this Manual
Related Documentation
Related publications for DataSite controllers
Pub. TitlePub. NumberDescription
DataSite Electronic Flow Meter and Remote Terminal Unit
Installation Instructions
DataSite Electronic Flow Meter and Remote Terminal Unit
Hardware User Manual
This manual is a reference guide for the software tools that accompany the
DataSite controller, namely DS Settings, DS FloConfig, and DS DNP3. These
tools can be used to configure and monitor the DataSite controller. This
manual describes the procedures you use to install and use the tools.
The publications listed in this table contain more information on the DataSite
controllers.
1758-IN001
1758-UM001
Information on how to install a DataSite controller.
Information on how to install and wire a DataSite controller.
Customized Function Blocks for DataSite Reference
Manual
DataSite Screen Builder user documentation available on
the DataSite CD and from http://www.isagraf.com
DataSite Workbench user documentation available on the
DataSite CD and from http://www.isagraf.com
Modbus Protocol Specifications available from
www.modbus.org
Allen-Bradley Programmable Controller Grounding and
Wiring Guidelines
Application Considerations for Solid-State Controls SGI-1.1
iiiPublication 1758-UM002D-EN-P - October 2010
1758-RM001
—Information on using the DataSite Screen Builder to create
—Information on using the DataSite Workbench to develop
—Information about the Modbus protocol.
1770-4.1
Description of the customized function blocks used for
programming DataSite controllers using the DataSite
Workbench software.
graphical user interfaces.
multi-process control projects for use with DataSite
controllers.
In-depth information on grounding and wiring Allen-Bradley
programmable controllers.
A description of important differences between solid-state
programmable controller products and hard-wired
electromechanical devices.
iv
Related publications for DataSite controllers (Continued)
Pub. TitlePub. NumberDescription
National Electrical Code - Published by the National Fire
Protection Association of Boston, MA.
Allen-Bradley Publication Index SD499—A complete listing of current documentation, including
This chapter provides information on the configuration settings utility,
DS Settings.
Use this tool to configure the 1758-RTU DataSite
controllers only.
1
Introduction
DS Settings is a configuration software for 1758-RTU DataSite controllers.
DS Settings provides the following functions:
• PC Communication Settings
This function lets you set up the communication mode and parameters
for the DataSite controller to be connected to the PC via the serial port
or the Ethernet (TCP/IP) port.
• Controller Communication Settings
This function lets you set up the controller parameters, such as serial
port parameters or Ethernet parameters, and low-power settings.
• Scan Settings
This function lets you configure Modbus master serial messages to
Modbus slave devices.
• Event Settings
This function lets you configure four types of real-time clock (RTC)
interruption events, namely system events, alarm events, calendar events
and time events.
13Publication 1758-UM002D-EN-P - October 2010
• Controller Debug
This function lets you use test registers and retrieve data from the
DataSite controller for online or offline debugging of the user programs
you have written for the controller in DataSite Workbench.
2. Enter the project name, for example, DS_RTU.prj.
3. Click OK.
The New Project dialog box appears.
The new project file, DS_RTU.prj in this example, is created in
C:\Program Files\Rockwell Automation\DS Settings\DS Settings
Project.
The file is opened in the project browser.
Publication 1758-UM002D-EN-P - October 2010
Save a Project
Follow this step to save a project using its current file name.
• From the File menu, choose Save.
The project file, DS_RTU.prj is saved in the current location. In this
example, it is C:\Program Files\Rockwell Automation\DS Settings\DS
Settings Project.
Follow these steps to save the project into a different file.
The DataSite controller can be connected to the PC via the serial port or the
Ethernet (TCP/IP) port. Use PC Communication Settings to set up the
communication mode and parameters for this connection.
Follow these steps to configure PC Communication settings:
1. From the Tools menu, choose PC Communication Settings.
The PC Communication Settings dialog box appears.
2. From the Connection Type pull-down menu, choose the type of
communication port used between the PC and the DataSite controller:
• For Ethernet communication mode, choose TCP/IP Server.
• For Serial port communication mode, choose your PC’s COM port
3. If you have chosen TCP/IP Server, set up the parameters for the
TCP/IP connection.
Parameters for TCP/IP Communication
ParameterDescriptionDefault Value
Station numberStation corresponding to the DataSite
controller communication Ethernet port.
1
IP addressIP address corresponding to the Ethernet
communication port of the DataSite
controller. The address is in the format,
xxx.xxx.xxx.xxx, made up of four octets with
each octet ranging between 0 and 255.
4. If you have chosen a COM port, set up the parameters for the serial port
connection.
Parameters for Serial Port Communication
ParameterValue range
Station number1…247
Baud rate (bps)2400, 4800, 9600, 14400, 19200, 38400, 56000, 57600
Timeout (1 s)1…10
Delay time (1 ms)0…3000
5. To confirm the PC settings and close the window, click OK.
To cancel the configuration and close the window, click Cancel.
When you click OK, the system will automatically save the
PC settings into a default file. The file name is
PC Communication Parameter.cfg, located in the current
project directory.
Use Controller Communication settings to set controller parameters, such as
serial port parameters or Ethernet parameters, and low-power settings.
Follow this step to open the Controller Communication Settings dialog box.
• From the Tools menu, choose Controller Communication Settings.
The Controller Communication Settings dialog box appears.
The file, Controller Communication Parameter.esy, located in the
current project directory, is displayed in the project browser file pane.
You can also double-click the
Controller Communication Parameter.esy file in the project
browser file pane to open the PC Communication Settings
picture.
The Information box displays a status message after each software
operation. For example, if a file is loaded successfully, the message,
"Load from file successful" appears in the Information box.
COM2), None
Master/Slave stateMaster, Slave
DuplexFull, Half
Baud rate2400, 4800, 9600, 14400, 19200, 38400, 56000, 57600
ParityEven, Odd, None
Data bits7, 8
Stop bits1, 2
Port typeRS232, RS485
Timeout (in units of 10 ms)1…1000
Delay time (in units of 10 ms) 0…300
3. To save the settings and close the Serial Ports Settings dialog box, click
OK.
To close the dialog box without saving the settings, click Cancel.
4. Click Download.
The new settings are applied to the DataSite controller.
The following sections provide more information on some of the parameters
for the serial port.
Protocol
When customizing the communication protocol, it is recommended that you
set the protocol as "None". You can then use flags in DataSite Workbench to
program the customized communication protocol. The flags corresponding to
each serial port are shown in the following table:
Flags in DataSite Workbench for serial ports
FlagDescription
US1_RXUS1 receiving task for US1 customized protocol
US2_RXUS2 receiving task for US2 customized protocol
The serial port scan block can be configured in the master state to acquire data
from the slave serial communication equipment connected in a certain time
interval. In the slave state, the DataSite controller can receive commands from
the host, generate and return response message. For more information, see the
Configuration Example
Timeout
In the master state, timeout is the maximum length of waiting time after a
command is sent. No new commands are sent while waiting for a response. If
no response is received after timeout, an error message box will be displayed to
inform you. You will then be prompted to send a new command.
on page 50.
Verify the protocol setting. If you set the protocol as
"None", the scan and the trigger scan function blocks will
not run properly even if the Master/Slave state is set
correctly.
Timeout is not applicable in other states.
Delay Time
In the master state, delay time is the maximum length of waiting time for the
next send command after one send/receive cycle is completed. This setting
can help prevent communication errors caused by a slower response of the
slave communication equipment connected.
In the slave state, delay time is the maximum length of waiting time for a
response to be returned after a command is received. This setting can help
prevent communication errors caused by a slower response of the master
communication equipment.
3. To save the settings and close the TCP/IP Settings dialog box, click OK.
Register IP Settings
The subnet mask and default gateway settings allow you to determine the
DataSite controllers that you want to establish communication with in the
network. This allows you to manage your network more efficiently.
To close the dialog box without saving the settings, click Cancel.
The options in the Power Enable group allow you to shut the power supply to
some parts of the DataSite controller to lower power consumption.
Follow these steps to lower power consumption.
1. Under Power Enable in the Controller Communication Settings dialog
box, clear the check boxes for the parts that can go to sleep:
• COM1 port
• Ethernet port
• LED indicators
If you are still using a port, do not clear its check box under
Power Enable. Otherwise, communication may be
interrupted. For example, when the DataSite controller is
communicating via the Ethernet port, do not shut the
power supply of the Ethernet port.
2. Click Download.
The settings are applied to the DataSite controller.
Follow this step to load the settings. This will load the last saved configuration
of the DataSite controller parameters.
• Click Load.
Alternatively, you may double-click the file, Controller Communication
Parameter.esy, from the file pane of the project browser or choose
Controller Communication Settings from the Tools menu.
If the file is loaded successfully, the message "Load from file successful"
will appear in the Information box.
For integrated modules such as the DataSite controller, the master ports can
directly read/write parameters by accessing the fixed Modbus registers. We
need to set scan blocks of US1 and US2 only when we want to access other
pieces of equipment connected with the two serial ports (COM1, COM2).
Use Scan Settings to match the register addresses of the 1758 controller with
those of the serially connected equipment.
A custom function block that can be triggered in the user
program to provide Modbus Master read/write functions is
also available. For more information, see the DataSite
Customized Function Blocks Reference Manual,
1758-RM001
.
Understand the Scan Blocks
Every scan block corresponds to a scan task. The maximum number of scan
tasks is 128. This table lists the description of each item in a scan block.
Scan block parameters and their descriptions
Scan Block ParameterDescription
Block typeScan block data category
Module AddrModbus slave station number of serial communication
equipment connected with COM1 or COM2.
Signal typeSignal register category
Scan timeRead/Write interval
Master RegisterRegister address where data is saved in the controller,
decided by the user.
Slave RegisterYou can set the read/write data register address of the
slave communication equipment according to the parameter
form of the slave communication equipment register.
Reg_NumThe number of read/write data registers.
Err_CntThe number of times the scan block fails to communicate.
Err_StateScan block communication state.
If the Err_State value is 1, it means the communication has
failed. A value of 0 indicates that the communication is OK.
RemarkUser comments.
You can enter a note or a tip for the scan block. Note that
this field will not be downloaded to the DataSite controller.
When the address of the master or slave register does not map to the signal,
the following error will appear.
Scan Time
Scan time refers to the read-write time interval of a scan block. You can use
the trigger scan function for COM port by programming the function block
COM_MSG in DataSite Workbench.
The following units of time are available. Note that ms represents
milliseconds, s seconds, m minutes, and h hours:
The scan time is equal to the value multiplied by the unit selected. For
example, if the value entered is "3" and the unit selected is "500 ms", then the
scan time is 3 x 500 ms = 1500 ms as shown in the following dialog box. This
means that the current scan block will be executed every 1500 ms.
Scanning starts when the DataSite controller is powered, and it continues
according to the scan time you have set.
Master Register
This is the start address of the register on the DataSite controller. Data is saved
into the master register starting from this address. The address range is
determined by the signal type.
Slave Register
This is the start address of the register on the slave equipment for reading data
from and writing data to. The controller will read data from or write data to the
slave equipment from this address. The address range is determined by the
signal type.
Reg_Num
The number of read/write data registers that follow the start register address
of the master register and the slave register. For example, if Reg_Num is 10,
the Master Start_Register is 40001 and the Slave Start_Register is 41001, this
means there are 10 master registers with register addresses running sequentially
from 40001…40010, and 10 slave registers with register addresses
41001…41010.
Publication 1758-UM002D-EN-P - October 2010
Remark
This field lets you enter a note or a tip for the scan block. This information can
be saved onto the PC but unlike other parameters, it will not be downloaded to
the DataSite controller. The maximum string length for this field is 90
characters.
These two parameters do not require user configuration. If you set up a scan
block successfully, two columns for these parameters will be added in the scan
block list automatically.
The Err_Cnt value represents the number of times the scan block fails to
communicate with the slave device. After the scan block is configured, if there
is no connection with the slave device or if communication fails, this value will
be incremented by 1 after each scan cycle.
This value is an indication of the status and efficiency of the communication.
For example, if the value keeps incrementing, this means that the
communication has failed. This could be due to a faulty physical connection
between the DataSite controller and the slave device, or due to incorrect
parameter settings. In addition, a low value indicates a more efficient
communication.
If the Err_State value is 1, it means the communication has failed. A value of 0
indicates that the communication is OK.
Follow these steps to open the Scan Settings dialog box.
• From the Tools menu, choose Scan Settings.
The Scan Settings dialog box appears. The file, Scan Block
Parameter.scn, located in the current project directory, is displayed on
the project browser file pane.
You can also double-click the Scan Block Parameter.scn file
in the project browser file pane to open the Scan Settings
dialog box.
You can also use the shortcut menu for Insert, Delete, Copy and Paste
functions.
Follow this step to use the shortcut menu.
• Right-click the row you want to apply the function to.
The shortcut menu appears.
Here is an example.
Publication 1758-UM002D-EN-P - October 2010
Load the Scan Settings
This function enables you to load the scan settings from the file buffer.
This allows you to verify the configuration while the DataSite controller is
offline.
Follow this step to load previously saved scan settings.
• Click Load.
The last saved Scan Block Parameter configuration is loaded from the
file, Scan Block Parameter.scn and the message, "Load from file
successful", appears in the left corner of the status bar.
This function saves the scan settings into a file buffer on the PC.
Follow this step to save scan settings.
• Click Save.
The settings are written to the file, Scan Block Parameter.scn and the
message, "Save into file successful", appears in the left corner of the
status bar.
Upload the Scan Settings from the Controller
Follow this step to upload (read) scan settings from the DataSite controller.
The controller needs to be online before you can upload the settings.
• Click Upload.
Download the Scan Settings to the Controller
Follow this step to download (write) scan settings to the DataSite controller.
The controller needs to be online before you can download the settings.
• Click Download.
Clear the Error Count
Follow this step to clear the error count in the scan blocks.
• Click Clear Err_Cnt.
Close the Scan Settings Dialog Box
Follow this step to close the Scan Settings dialog box.
By configuring a scan block as a US1 or US2 block, we can read from and
write to the equipment connected with the DataSite controller.
For example, we can take two DataSite controllers connected via RS232 serial
communication, with COM1 of one DataSite controller as the master station,
and COM1 of the other controller as the slave station. The master station can
read/write the slave station’s signal via the serial communication between the
two stations.
The following subsections provide you with one way of configuring the
DataSite controllers in this example.
Step 1: Configure the Controller Communications Settings for the Modbus
Master Station
Step 4: Read Master registers to verify communication between Master
station and Slave station
00001…00004 are the DO signal registers of the slave
DataSite controller, and 00100…00103 are the configured
slave registers corresponding to DO signal registers of the
slave DataSite controller.
Use HART Settings to configure and send HART command messages.
Customized function blocks that can be triggered in the
user program to provide HART read/write functions are
also available. For more information, see the DataSite
Customized Function Blocks Reference Manual,
1758-RM001
.
Open the HART Settings Dialog Box
Follow this step to open the HART Settings dialog box.
• From the Tools menu, choose HART Settings.
The HART Settings dialog box appears. The file,
HART Block Parameter.hrt, located in the current project directory is
displayed on the project browser file pane.
You can also double-click the HART Block Parameter.hrt
file in the project browser file pane to open the HART
Settings dialog box.
This table provides a description of the column headers in the HART Settings
dialog box.
Description of HART block parameters
HeaderDescription
NO.Serial number of each HART scan block.
HART ChannelChannel for the HART interface module to send commands to. The
effective range is 0…2.
•The HART0 channel supports multi-branched HART scan, and the
data of up to 13 pieces of HART equipment can be scanned.
•The HART1 and HART2 channels are point-to-point scan, and not
only do they support HART protocol communication, they also
support standard 4…20 mA signals.
AddressCommunication address of the HART equipment. The effective
CommandHART command to be sent to the HART equipment. The effective
value of each HART command is as follows:
•Read Unique Identifier: 0
•Read Primary Variable:1
•Read P. V. Current And Percent Of Range: 2
•Read Dynamic Variable And P. V. Current: 3
•Read Transmitter Variables: 15
•Read Primary Variable Output Information: 33
•Reset Configuration Changed Flag: 38
•Read additional Transmitter Status: 48
•Read Transmitter Variable Information: 54
Scan TimeTime cycle of scanning HART equipment data.
Effective range is 50 ms…50 hours.
Send RegisterRegister for storing command data.
Effective range is 40003…49999 for 1758-RTU controllers and
40003…47999 for 1758-FLO controllers.
Return RegisterRegister for storing command response data.
Effective range is 40003…49999 for 1758-RTU controllers and
40003…47999 for 1758-FLO controllers.
Unit RegisterRegister for storing the unit of HART equipment data returned.
Effective range is 40003…49999 for 1758-RTU controllers and
40003…47999 for 1758-FLO controllers.
HART State AddrRegister for storing HART equipment state returned.
Effective range is 40003…49999 for 1758-RTU controllers and
40003…47999 for 1758-FLO controllers.
Err_CntNumber of times an error occurs.
After the HART scan block is configured, if there is no connection
with the slave device or if communication fails, this value will be
incremented by 1 after each scan cycle. This value is updated
whenever Upload is clicked.
Err_StateError state of HART scan block configuration.
If the Err_State value is 1, it means the communication has failed.
A value of 0 indicates that the communication is OK.
HART scan data blocks are configured in sequence and
each block has a corresponding number. The maximum
number of modules is 128.
When one data block is an empty block, all the blocks
configured after this empty data block will be invalid.
Some of the variables read from HART equipment are 32-bit floating-point
values. Every floating-point value is stored in two continuous data registers.
The higher 16 bits of this value will be stored in the register with a higher
address and the lower 16 bits of this value will be stored in the register with a
lower address. For example, if a 32-bit double precision IEEE floating point
number, such as 1234.5678 is to be stored, two registers, such as register 40108
and register 40109 can be combined to store the number. In hexadecimal,
1234.5678 is 449A 552B. The DataSite controller will store 449A in register
40109 and 522B in register 40108.
Registers Used in HART Commands
The following table lists the number of registers used in each HART command
for the four register types, namely Send, Return, Unit and HART state.
Number of registers used in each HART command
CommandDescriptionNumber of registers
Send registerReturn register Unit registerHART state
register
0Read Unique Identifier 01002
1Read Primary Variable0212
2Read P. V. Current And Percent Of Range0402
3Read Dynamic Variable And P. V. Current01042
15Read Transmitter Variables01002
33Read Primary Variable Output Information41242
35Write Primary Variable Range Values9002
38Reset Configuration Changed Flag0002
40Enter/Exit Fixed Primary Variable Current
Send register+0, 1 = Actual fixed Primary Variable current level, units of
Return registerNot used
Unit registerNot used
HART state register+0 = state 0
Command44
PurposeWrite Primary Variable Units
Send register+0 = Primary Variable units code, 8-bit unsigned integer
Return registerNot used
Unit registerNot used
HART state register+0 = state 0
Command48
milliamperes (float point)
+1 = state 1
+1 = state 1
PurposeRead Additional Transmitter Status
Send registerNot used
Return register+0, 2 = device specific status, 8-bit unsigned integer
+1 = Transmit variable limits units code, 8-bit unsigned integer
+1 = state 1
from the Slave to the Master, 8-bit unsigned integer, between 5
and 20
+1 = state 1
Variable and Command
Each piece of HART equipment is designed differently. For example, when
you use command 3 to read variables from HART equipment, the four
dynamic variables returned may have different meanings, and not all four
variables may be valid. Refer to the documentation for the HART equipment
for more information. See also the table, Description of HART commands
.
Response Message
The response message of a piece of HART equipment contains the Err Num
and Err State values. The Err Num value indicates the number of times
communication with the HART equipment has failed. The Err State value
indicates whether communication with the HART equipment is a success or
failure. An Err State value of 0 means that communication with HART
equipment is successful. An Err State value of 1 means that the
communication with HART equipment has failed.
You can also read the response code from the HART equipment. It is stored
as two bytes in the state register which you have configured in the HART scan
block. If bit 7 in the first byte is 1, this byte is bit-mapped and all the
communication errors are displayed in this byte. If bit 7 in the first byte is 0,
this byte is not bit-mapped and the meaning is determined by the value of bit 6
through bit 0.
First byte when bit 7 = 0 (Command Response) (Continued)
BitDescription
11This bit can mean any of the following:
•Upper range value too high—Upper range value is greater than the upper sensor limit.
•Excess correction attempted—Correction attempted is outside of the permissible limits of the field device.
•In multidrop mode—When in multidrop mode, this command cannot be performed. The analog output is deactivated and
cannot be used when the polling address is set to a value within the range of 1…15.
•Invalid sensor type code—Sensor type code selected is not valid.
•Invalid sensor material code—Sensor material code selected is not valid.
•Invalid base volume units code—Base volume units code selected is not valid.
•Invalid base flow units code—Base flow units code selected is not valid.
•Flow rate set point too high—Value entered for the flow rate set point is too high.
•Density low limit too high—Value entered for the density low limit is too high.
•Access denied—Access to this part of the memory is not allowed.
•Invalid transmitter variable code.
•Invalid item number.
•Invalid wetted material code.
•Standard deviation too large.
•D2 too high—Value of the second density data is too high.
•Instrument in sample mode.
•Invalid calibration point.
•Flow rate factor too high.
•Invalid analog output HOLD code.
12This bit can mean any of the following:
•Upper range value too low—Upper range value is less than the lower sensor limit.
•Invalid characterization—Characterization of the sensor is not valid.
•Invalid number of wires—Number of wires on the sensor is not valid.
•Invalid calibration point units code—Units code sent with the calibration point is not valid.
•Invalid calibration location code—Calibration location code selected is not valid.
•Invalid base time units code—Base time units code selected is not valid.
•Flow rate set point too low—Value entered for the flow rate set point is too low.
•Incorrect format—Format of the parameter entered is not correct.
•Density low limit too low—Value entered for the density low limit is too low.
•Write to ROM attempted—Writing of data to read-only memory is attempted.
•Invalid units code.
•Invalid sensor connection code.
•Invalid trim points units code—Units code sent with the trim point is not valid.
•Invalid trim location code—Trim location code selected is not valid.
•Invalid base mass time units.
•Invalid base volume time units.
•Standard deviation too small.
•Standard factor format.
Publication 1758-UM002D-EN-P - October 2010
First byte when bit 7 = 0 (Command Response) (Continued)
BitDescription
12
(Continued)
•D2 too low—Value of the second density data is too low.
•Invalid command number.
•Invalid density units and calibration point.
•Flow rate factor too low.
13This bit can mean any of the following:
•Upper and lower range values out of limits—Upper and lower range values are outside of their limits.
•Range and sensor type not entered—Before characterization, range and sensor type need to be entered.
•Invalid number of bytes—The Number of Bytes parameter received in this command is not valid.
•Invalid meter option—Meter option selected is not valid.
•Special sensor not available—Calibration for special sensor is not available.
All bits 0 (when a communication error is reported in
the first byte).
5hex 20Cold start
4hex 10More status available
3hex 08Analog output current fixed
2hex 04Analog output saturated
1hex 02Nonprimary variable out of limits
0hex 01Primary variable out of limits
Insert a HART Scan Block
Follow these steps to insert a HART scan block.
1. In the HART Settings dialog box, select the row where you want to
insert the scan block to and click Insert. Alternatively, you can
double-click the row.
Note that you cannot insert data after an empty data block.
The Edit dialog box appears. The NO. box displays the serial number of
the current HART scan block.
Effective values of HART commands
Effective ValueHART CommandsEffective Value
0Read Unique Identifier
1Read Primary Variable
2. From the HART Channel pull-down menu, choose a channel for the
HART interface module to send commands to. The effective range is
0…2.
• The HART0 channel supports multi-branched HART scan, and the
data of up to 13 pieces of HART equipment can be scanned.
• The HART1 and HART2 channels are point-to-point scan, and not
only do they support HART protocol communication, they also
support data collection of 4…20 mA. You should set the HART
address as 0.
3. In the Address box, specify the communication address of the HART
equipment. The effective range is 0…15.
4. From the Command Num pull-down menu, choose the HART
commands to be sent to the HART equipment. This table shows the
effective value of each HART command.
2Read P. V. Current And Percent Of Range
3Read Dynamic Variable And P. V. Current
15Read Transmitter Variables
33Read Primary Variable Output Information
35Write Primary Variable Range ValuesOnly Use in HART TRIG block
38Reset Configuration Changed Flag
40Enter/Exit Fixed Primary Variable Current Mode Only Use in HART TRIG block
44Write Primary Variable UnitsOnly Use in HART TRIG block
48Read additional Transmitter Status
54Read Transmitter Variable Information
59Write Number Of Response PreamblesOnly Use in HART TRIG block
5. In the Scan Time box, enter the number of units and select the time unit
Command 0 must be configured for each HART device in
order for the other commands to work.
to specify the time cycle of scanning HART equipment data.
For example, if you enter "1" for the number of units, and select
"(500 ms)" for the time unit, the scan time will be 1 x 500 ms = 500 ms.
This means that the current HART scan block will be executed every
500 ms.
6. In the Send Register box, define the register for storing command data.
7. In the Return Register box, define the register for storing command
response data.
8. In the Unit Register box, define the register for storing the unit of
HART equipment data returned.
9. In the HART State Addr box, define the register for storing the HART
equipment state returned.
The register range is 40003…49999 for 1758-RTU
controllers, and 40003…47999 for 1758-FLO controllers.
See Description of HART commands
on page 58 for more
information on the Send, Return, Unit, and HART State
Addr registers.
10. Click OK.
The Edit dialog box is closed and the settings are saved to the new
block.
Use the Multi_Paste function to paste a HART scan block to multiple rows.
This function works in the same way as the Multi_Paste function in the Scan
Settings dialog box. For details, see Paste a Scan Block to Multiple Rows
page 45.
on
Use the Shortcut Menu
You can also use the shortcut menu for Insert, Delete, Copy and Paste
functions.
Follow this step to use the shortcut menu.
• Right-click the row you want to apply the function to.
This function enables you to load the HART settings previously saved in a file
buffer on the PC. This allows you to verify the settings while the DataSite
controller is offline.
Follow this step to load HART settings from the file.
• Click Load.
If the settings are loaded successfully, the status bar will display the
message, "Load from file successful".
Publication 1758-UM002D-EN-P - October 2010
Save the HART Settings
Follow this step to save the HART settings into a file buffer on the PC.
• Click Save.
If the settings are saved successfully, the message, "Save into file
successful" will be displayed in the status bar. The settings are saved to
the file, HART Block Parameter.hrt, by default.
Set and get an alarm event at 8:30 a.m. every day.
1. In the Event Settings dialog box, select the Alarm Enable, Hour,
Minute, and Second check boxes. Enter the time in the Hour, Minute,
and Second boxes, and then click Download. Another method is to use
EV_CLK_CFG and EV_RTC_SET to configure the alarm event.
2. Use EV_GET to read the RTC return value and check bit 3 for the
alarm event. Bit 3 will be set to ‘1’ when the RTC event occurs.
Example for a Calendar Event
Set and get an event that occurs at 0 seconds, 0 minutes, 0 hours on the first
day of every month.
1. In the Event Settings dialog box, select the Calendar Enable check box
and click Month. Then, click Download. Another method is to use
EV_CALE_CFG and EV_RTC_SET to configure the event.
Publication 1758-UM002D-EN-P - October 2010
2. Use EV_GET to read the RTC return value and check bit 2 for the
second event. Bit 2 will be set to ‘1’ when the second event occurs.
Set and get an event that occurs at 0 seconds, 0 minutes of every hour.
1. Select the Time Enable check box and click Hour in the Event Settings
dialog box. Then, click Download. Another method is to use
EV_TIME_CFG and EV_RTC_SET to configure the event.
2. Use EV_GET to read the RTC return value and check bit 1 for the
second event. Bit 1 will be set to ‘1’ when the second event occurs.
Configure a System Event
Follow this step to configure a system event.
• To enable an event interruption with an interval of 1s, select the Second
Event check box.
When you select this check box, the system will provide an interruption
signal every second. You can program the EV_GET function block in
DataSite Workbench to retrieve the interruption signals according to
your application requirements.
2. Select the check box for the date/time attribute you want to set.
3. For each check box you have selected in step 2, enter the date/time
Alarm events are enabled.
value in the corresponding box.
The alarm event will be executed based on the frequency you set.
For example, if you set Month as 1, Day 20, Minute 3, and Second 5, the
alarm event will be executed annually at the third minute and fifth
second of every hour on January 20.
Configure a Calendar Event
Follow these steps to configure a calendar event.
1. Select the Calendar Enable check box.
Calendar events are enabled.
2. Select one of the options: Year, Month, Week.
The option you select determines how frequently the calendar event
routine will be executed.
• Year
Annually, on January 1, at 0 hours (midnight), 0 minutes, 0 seconds, a
corresponding calendar interruption task you have written in
DataSite Workbench is executed.
• Month
On the first day of every month at 0 hours (midnight), 0 minutes, 0
seconds, a corresponding calendar interruption task you have written
in DataSite Workbench is executed.
Publication 1758-UM002D-EN-P - October 2010
• Week
On the Monday of every week at 0 hours (midnight), 0 minutes, 0
seconds, a corresponding calendar interruption task you have written
in DataSite Workbench is executed.
2. Select one of the options: Minute, Hour, Midday, Midnight.
The option you select determines how frequently the time event routine
will be executed.
• Minute
At 0 seconds of every minute, a corresponding time break task is
executed in the application program written by users.
• Hour
At 0 seconds, 0 minutes, hourly, a corresponding time break task is
executed in the application program written by users.
• Midday
At 0 seconds, 0 minutes, 12 hours (noon), daily, a corresponding time
break task is executed in the application program written by users.
• Midnight
At 0 seconds, 0 minutes, 0 hours (midnight), daily, a corresponding
time break task is executed in the application program written by
users.
Upload Event Settings from the Controller
Follow this step to upload (read) the event settings from the DataSite
controller. The controller needs to be online before you can upload the
settings.
• Click Upload.
Download Event Settings from the Controller
Follow this step to download (write) event settings to the DataSite controller.
The controller needs to be online before you can download the settings.
Follow this step to save the event settings into the file, Event Parameter.evt, on
the PC.
Load the Event Settings
• Click Save.
If the settings are saved successfully, the message, "Save into file
successful" will appear in the status bar of the Event Settings dialog box.
If you have made any changes in the Event Settings dialog
box without saving them, the changes will be discarded
once the saved settings are loaded from the file.
Follow this step to load event settings from the file, Event Parameter.evt.
• Click Load.
If the settings are loaded from the file successfully, the message, "Load
from file successful" will appear in the status bar of the Event Settings
dialog box.
Close the Event Settings Dialog Box
Follow this step to close the Event Settings dialog box.
The Controller Debug function allows you to use test registers and retrieve
data from the DataSite controller for online or offline debugging of the user
programs you have written for the controller in DataSite Workbench.
Note that you can use this function to view a DataSite register value. Only
DataSite registers can be monitored. DataSite Workbench internal variables
cannot be monitored unless they are written into a DataSite register.
Open the Controller Debug Dialog Box
Follow this step to open the Controller Debug dialog box.
• From the Tools menu, choose Controller Debug.
The Controller Debug dialog box appears, and the file, Controller
Debug.rgf, located in the current project directory is displayed in the
project browser file pane.
When you are debugging in the online mode, register data is refreshed at
regular intervals. You may change this interval according to your requirements.
Follow these steps to set the scan time.
1. Click Offline to go to the offline mode.
This value can only be set when you are in the offline
debugging mode.
2. In the scan time box, enter a value for the desired time interval.
The default interval is 100 ms.
3. Click Online to go to the online mode.
Add a Register Group
Follow these steps to add a group of registers.
1. Click New Group.
The New Group box appears.
2. Enter a name for the new group.
3. Click OK.
The new group is added and listed in the Register Group box.
3. In the Start_Addr text box, enter the address for the register.
4. In the Reg_Cnt text box, enter the number of registers you want to add.
If you are adding more than one register, the Start_Addr value will be
the address for the first register. Subsequent registers will have
consecutive addresses.
5. From the Type pull-down menu, select a register type from the
following options:
• Unsigned16 bit unsigned int
• Signed16 bit signed int
• Float Point32 bit float number
• HexadecimalHexadecimal form
• Binarybinary form
• ASCIIASCII code form
• BOOLBOOL type
If the selected register type does not map to Start_Addr, this error
message appears. Click OK and reselect the register type.
6. Click Add.
If the register address you entered is invalid, this error message appears.
Click OK and re-enter the register address.
All the states of controller are showed by a 16-bit code. For details, see the
following tables.
Error codes
Error CodeMeaning
0x0001Hardware register error
0x0002Data FLASH error
0x0100HART communication error
0x0200US1 communication error
0x0400US2 communication error
If more than one error occurs, an "OR" operation will be performed on the
codes. For example, if both US1 and US2 communication errors occur, the
error code will be 0600. If all errors occur, the code will be 0703.
Initialization state codes
Initialization State CodeMeaning
0x0001Test communication.
0x0002Initialize communication parameters.
0x0004Clear the DataSite Workbench application.
0x0008Initialize registers.
0x0100Initialize file system.
0x0200Initialize DNP3.
If more than one initialization state exists, an "OR" operation will be
performed on the codes. For example, a code of 0x0102 means that test
communication and initialization of communication parameters are in
progress.
DS Workbench Status codes
DS Workbench Status CodeMeaning
0001DataSite Workbench is running.
0000DataSite Workbench is stopped.
Clear Error Codes
Follow this step to clear the error codes of the controller.
All settings will be downloaded into the controller.
4. Click Run, and exit the local connection.
Test the Communication
Follow these steps to obtain the communication settings of the DataSite
controller, such as baud rate of the serial port, and the IP address of the
Ethernet port.
1. Set the controller into the Service mode.
2. Select the Communication Test check box.
3. Click Set.
All settings will be downloaded into the controller.