Professional Documents
Culture Documents
Manual de Transferencia de Datos de AMS Machinery Healt Manager
Manual de Transferencia de Datos de AMS Machinery Healt Manager
Page 1 of 106
9210 Transmitter
The Data Import Configuration program can also be used to create a DeltaV or Ovation configuration file for the CSI
6500. When imported into DeltaV / Ovation, this file will automatically configure the control system to read data from
the CSI 6500 Protection monitors.
Installation
NOTE: When installing AMS Machinery Manager software, the boxes for Data Import Client and Data Import Server
need to be checked. This requires the data import functionality to be enabled in the enable.tbl file. These options will
not be available unless they are purchased and enabled. The serial program can be used to determine which programs
are licensed.
mk:@MSITStore:C:\RBMsuite\sys\helpmsg\DIAGNO~1.CHM::/MODBUS.html
18/05/2016
Data Transfer
Page 2 of 106
Administration
In order to run the Data Import program, a user must be given the proper access permissions. To configure access,
after installation, when logged in as Administrator, run the RBM Network Administration program.
In the RBMadmin window, highlight the desired user in the User Configurations list, and then select Edit User from
the User drop down menu.
mk:@MSITStore:C:\RBMsuite\sys\helpmsg\DIAGNO~1.CHM::/MODBUS.html
18/05/2016
Data Transfer
Page 3 of 106
Edit User
If the Data Import program is enabled in the Enable.tbl file (listed as "Modbus Import for Networks" in the serial.exe
program), the Modbus Import for Networks item will be listed on the Package" tab.
mk:@MSITStore:C:\RBMsuite\sys\helpmsg\DIAGNO~1.CHM::/MODBUS.html
18/05/2016
Data Transfer
Page 4 of 106
Serial.exe
Permissions
On the Policies tab, the three Data Import programs must be listed.
Highlight a user, then right click in the Policies window and select Add Policy. You can select all three to add at once.
mk:@MSITStore:C:\RBMsuite\sys\helpmsg\DIAGNO~1.CHM::/MODBUS.html
18/05/2016
Data Transfer
Page 5 of 106
Another approach is to highlight a policy under Policies in the tree, then in the window to the right, right click and add
the user.
Policies
When a user account has been enabled for data import, the Modbus Data Import menu will appear in the main
menu bar.
Main Menu
From the Modbus Data Import menu, select the Config option to open the Data Source Configuration window for
configuring the data import.
mk:@MSITStore:C:\RBMsuite\sys\helpmsg\DIAGNO~1.CHM::/MODBUS.html
18/05/2016
Data Transfer
Page 6 of 106
NOTE: Only one instance of the Data Source Configuration program can be run at one time, even in a network
installation.
Add Server
The Data Import Server runs on a PC as a Service named "CSI Data Import Services".
The Add Server button is used for linking to multiple instances of the data import server. For best network
performance, these instances may be installed on remote computers that are near the devices they monitor. Using the
Add Server button, these instances can be consolidated and displayed in a common Device Hierarchy tree. This list of
servers resides on the NetAdmin server.
NOTE: The use of multiple data import servers requires multiple software licenses to be defined in the Enable.tble file.
NOTE: When linking to a CSI 9420 wireless vibration transmitter on the DeltaV system, the Data Import Server must
be installed on a DeltaV Application Station that has access to both the control network (where the 1420 Smart
Wireless Gateway is located) and the seperate network (where the AMS Machinery Health Manger database is located).
NOTE: If a firewall exists between the PC running the Data Import Server and the PC running the CsiMtdbMgr
Database server, then port 10060 must be open to allow data to flow.
Add Device
Highlight the server in the Device Hierarchy tree, and click the Add Device button
in the top left corner. Or,
from the Edit menu, select Add, then Device. Or, right click on the server and select "Add", then "Device".
mk:@MSITStore:C:\RBMsuite\sys\helpmsg\DIAGNO~1.CHM::/MODBUS.html
18/05/2016
Data Transfer
Page 7 of 106
Device Hierarchy
mk:@MSITStore:C:\RBMsuite\sys\helpmsg\DIAGNO~1.CHM::/MODBUS.html
18/05/2016
Data Transfer
Page 8 of 106
mk:@MSITStore:C:\RBMsuite\sys\helpmsg\DIAGNO~1.CHM::/MODBUS.html
18/05/2016
Data Transfer
Page 9 of 106
Trend Tab
mk:@MSITStore:C:\RBMsuite\sys\helpmsg\DIAGNO~1.CHM::/MODBUS.html
18/05/2016
Data Transfer
Page 10 of 106
The Trend tab defines the storage of single point values such as Overall or 1x Peak/Phase. The Storage Strategy can
be set to collect data at defined intervals and to store data at either defined intervals, upon a change in the alarm
state, or both.The defaults for Trend data are a Collection Rate of once per minute and a Storage rate of once per 8
hours or upon change in alarm state.
Waveform Tab
The Waveform tab defines the storage of time-waveform data. Once imported, frequency spectra can be generated
from the waveform data for detailed analysis. Waveform data can be turned off, or set to store at a defined interval.
The default is a Storage rate of once every 24 hours.
Other Tab
If "Timestamp Applied to Data when Received by Server" is selected, the imported data will be stored with the
date/time stamp from the current PC clock time when the Modbus data is received. If "Timestamp Applied to Data in
Device" is selected, the imported data will be stored with the date/time stamp from the CSI 6500 system clock when
the data was acquired.
If the "Synchronize Device Time from Server every __ seconds" box is checked, the Data Import software will
periodically send an update to the CSI 6500 clock to keep it synchronized with the PC clock. The default time
mk:@MSITStore:C:\RBMsuite\sys\helpmsg\DIAGNO~1.CHM::/MODBUS.html
18/05/2016
Data Transfer
Page 11 of 106
Group - Identification
Group - Storage Settings Tab
mk:@MSITStore:C:\RBMsuite\sys\helpmsg\DIAGNO~1.CHM::/MODBUS.html
18/05/2016
Data Transfer
Page 12 of 106
Data storage can be configured here, as described earlier at the Device level. Edits made at this level of the tree only
affect the individual Group and its subcomponents. If the Use Default boxes are checked, the Group will inherit its
storage settings from the parent Device. If these boxes are unchecked, the Group settings will not be affected by
changes made at the Device level.
mk:@MSITStore:C:\RBMsuite\sys\helpmsg\DIAGNO~1.CHM::/MODBUS.html
18/05/2016
Data Transfer
Page 13 of 106
During the Auto-Discovery process of a 6500, a Data Source (Value) entry is automatically created for various CSI
6500 data values.
With an individual Data Source (Value) highlighted in the Device Hierarchy tree, the lower left window becomes the
Data Source (Value) pane, and the following tabs are displayed:
mk:@MSITStore:C:\RBMsuite\sys\helpmsg\DIAGNO~1.CHM::/MODBUS.html
18/05/2016
Data Transfer
Page 14 of 106
The Equation field displays what conversion equations are being applied to the data.
Change Equation
The Data Import software automatically inserts an equation to perform a required integer to floating-point conversion
(typically a divide by 100) on the ModBus data from the CSI 6500. If the Convert Metric Units to U.S. Units box is
checked when adding the Device, an additional conversion equation is automatically entered here. Other additional
conversion equations can be added here as well.
The Get Value button on this window provides a quick one-time read and conversion of the value to confirm if the
equation is converting the incoming value as desired.
Click Close to close and save the Equation window.
mk:@MSITStore:C:\RBMsuite\sys\helpmsg\DIAGNO~1.CHM::/MODBUS.html
18/05/2016
Data Transfer
Page 15 of 106
Get Value
Acquisition begins automatically. Note that this test produces a high rate of Data Import requests to the Device. Click
Stop to pause acquisition. Click Start to continue. The Raw Value is displayed, along with the Processed Value with the
conversion equations applied.
For the CSI 6500, this window also displays status LEDs. If the Channel Clear LED is green, the channel is OK/Clear. If
the Channel Clear LED is gray, the channel is not OK/Clear.
If the Hardware Alarm LED is gray, there is no alarm. If this LED is red, either an Alert or Danger alarm limit has been
exceeded on the associated channel.
NOTE: The conversion equation can be modified while "Get Data..." acquisition is running. This allows the result of
equation changes to be seen in "real time".
Click Done to close the window.
mk:@MSITStore:C:\RBMsuite\sys\helpmsg\DIAGNO~1.CHM::/MODBUS.html
18/05/2016
Data Transfer
Page 16 of 106
NOTE: Clicking the red X symbol will provide the option to remove mapping links or entirely delete the item.
mk:@MSITStore:C:\RBMsuite\sys\helpmsg\DIAGNO~1.CHM::/MODBUS.html
18/05/2016
Data Transfer
Page 17 of 106
Delete Device
Waveform - Identification
The ID and Description fields are populated automatically. These fields can then be edited as desired.
The Type field displays the waveform data units type for reference.
The Associated Channel Offset is a programming reference, indicating where the waveform data is located in the
Modbus output. Starting with zero, two waveform blocks are reserved for each monitor in the tree.
mk:@MSITStore:C:\RBMsuite\sys\helpmsg\DIAGNO~1.CHM::/MODBUS.html
18/05/2016
Data Transfer
Page 18 of 106
mk:@MSITStore:C:\RBMsuite\sys\helpmsg\DIAGNO~1.CHM::/MODBUS.html
18/05/2016
Data Transfer
Page 19 of 106
Retrieve Data
The Min/Max Value boxes show the lowest and highest amplitudes on the plot.
The Values Count box indicates the number of samples in the waveform.
The Show Velocity/Displacement Waveform buttons will display the plot in different units, as converted by the
software.
The Show Spectrum button will display a spectrum calculated from the waveform.
If the Waveform is mapped to a measurement point in the database, the waveform and spectrum can be stored by
clicking the Save to Database button.
Click Done to close the window.
Refresh Device
If the CSI 6500 configuration is changed, the Refresh Device command can be used to import the updated device
information, without having to completely delete the device and then Add it back.
If possible, existing mappings and conversion equations will be retained. However, some user changes may be lost as
the information about the device hierarchy is updated. For example, if the data units have changed the point mappings
will be deleted.
mk:@MSITStore:C:\RBMsuite\sys\helpmsg\DIAGNO~1.CHM::/MODBUS.html
18/05/2016
Data Transfer
Page 20 of 106
Refresh Device
The Refresh Device command also provides the option to add or remove the Metric to English units conversion
equations. Clicking Yes will leave the units as they were originally configured. Clicking No will either add or remove the
conversion equations in order to switch the units type.
Add Device
Highlight the server in the Device Hierarchy tree, and click the Add Device button in the top left corner. Or, from the
Edit menu, select Add, then Device. Or, right click on the server and select "Add", then "Device".
Device Hierarchy
The Device Type window will open. Use the drop down list to select 1420 Smart Wireless Gateway.
mk:@MSITStore:C:\RBMsuite\sys\helpmsg\DIAGNO~1.CHM::/MODBUS.html
18/05/2016
Data Transfer
Page 21 of 106
NOTE: The 1420 Smart Wireless Gateway connection type uses HART communication protocol. HART communication
is required for automating the 1420 data import configuration, as well as for Waveform and Spectrum import. If the
1420 is not enabled for HART, it can still be connected using the Other device type selection. The Other device type
requires manual configuration, and does not have the option to import Waveform/Spectrum data.
NOTE: The 1420 firmware versions 3.9.5 and later have improved data transfer speed for Spectrum/Waveform
transmission.
Enter the IP address of the 1420 Smart Wireless Gateway.
The Port Number must match what is defined in the 1420. The default Port is 20004 for HART UDP and 20005 for
HART TCP. The 1420 can be configured to use either protocol.
Click OK to add the new device.
The Data Import server will attempt to automatically discover the configuration of the 1420 and add it to the Device
Hierarchy tree. The tree will automatically be populated with the wireless transmitters, sensors, and parameters as
they are configured in the 1420.
These entries can be reviewed by expanding the Device Hierarchy tree as shown below.
mk:@MSITStore:C:\RBMsuite\sys\helpmsg\DIAGNO~1.CHM::/MODBUS.html
18/05/2016
Data Transfer
Page 22 of 106
mk:@MSITStore:C:\RBMsuite\sys\helpmsg\DIAGNO~1.CHM::/MODBUS.html
18/05/2016
Data Transfer
Page 23 of 106
During the auto-discovery process, the ID and Description fields are populated automatically with the Hostname of
the 1420 Smart Wireless Gateway. The ID field is for reference only. The Description field can be edited as desired.
Changes made to this field do not get written back to the 1420.
The Type field indicates the type of Device, for reference.
The Start and Stop Data Collection buttons are available on this tab, along with the Data Collection status. The Start
and Stop functions are also available under the Edit Menu, or by right-clicking a Device in the tree.
NOTE: The Data Import server runs independently from the Data Source Configuration program. Once data collection
has been started, the Data Source Configuration program can be closed, and the Data Import server(s) will continue to
run.
Trend Sub-Tab
mk:@MSITStore:C:\RBMsuite\sys\helpmsg\DIAGNO~1.CHM::/MODBUS.html
18/05/2016
Data Transfer
Page 24 of 106
Waveform Sub-Tab
Spectrum Sub-Tab
mk:@MSITStore:C:\RBMsuite\sys\helpmsg\DIAGNO~1.CHM::/MODBUS.html
18/05/2016
Data Transfer
Page 25 of 106
Group - Identification
The ID and Description fields are populated here automatically from the LONG TAG field in the CSI 9420 DD. The ID
field is for reference only. The Description field can be edited as desired. Changes made to this field do not get written
back to the 9420.
mk:@MSITStore:C:\RBMsuite\sys\helpmsg\DIAGNO~1.CHM::/MODBUS.html
18/05/2016
Data Transfer
Page 26 of 106
The Type field indicates the type of the Group. For example, a CSI 9420 Vibration Transmitter.
Other Tab
mk:@MSITStore:C:\RBMsuite\sys\helpmsg\DIAGNO~1.CHM::/MODBUS.html
18/05/2016
Data Transfer
Page 27 of 106
mk:@MSITStore:C:\RBMsuite\sys\helpmsg\DIAGNO~1.CHM::/MODBUS.html
18/05/2016
Data Transfer
Page 28 of 106
mk:@MSITStore:C:\RBMsuite\sys\helpmsg\DIAGNO~1.CHM::/MODBUS.html
18/05/2016
Data Transfer
Page 29 of 106
Spectrum Identification
The Spectrum ID and Description fields are populated automatically. These fields can then be edited as desired.
mk:@MSITStore:C:\RBMsuite\sys\helpmsg\DIAGNO~1.CHM::/MODBUS.html
18/05/2016
Data Transfer
Page 30 of 106
The Type field indicates whether the imported data will be a normal Velocity spectrum or a PeakVue spectrum.
Frequency Resolution
20 Hz / line
10 Hz / line
5 Hz / line
2.5 Hz / line
If the Store Analytical Spectrum option is selected, a high resolution spectrum will be transmitted/stored instead of
the thumbnail. A warning is displayed that this will consume more battery life, due to the larger amount of data being
transmitted.
By default, the high resolution spectrum is a 1000 Hz Fmax / 1600 line spectrum (which is a resolution of 0.625 Hz /
line) with no averaging.
If the CSI 9420 is configured to allow AMS Machinery Manager to make changes, the Use Averaging box will be
editable. If this box is checked, then the 1000 Hz Fmax high resolution spectrum will only be 800 line resolution (1.25
Hz / line), but will use 4 averages. Note that the thumbnails are always averaged.
mk:@MSITStore:C:\RBMsuite\sys\helpmsg\DIAGNO~1.CHM::/MODBUS.html
18/05/2016
Data Transfer
Page 31 of 106
500 Hz
Thumbnail Fmax
1000 Hz
600 Hz
300 Hz
150 Hz
500 Hz
300 Hz
150 Hz
75 Hz
Thumbnail Resolution
20 Hz / line
10 Hz / line
5 Hz / line
2.5 Hz / line
10 Hz / line
5 Hz / line
2.5 Hz / line
1.25 Hz / line
mk:@MSITStore:C:\RBMsuite\sys\helpmsg\DIAGNO~1.CHM::/MODBUS.html
18/05/2016
Data Transfer
Page 32 of 106
mk:@MSITStore:C:\RBMsuite\sys\helpmsg\DIAGNO~1.CHM::/MODBUS.html
18/05/2016
Data Transfer
Page 33 of 106
Waveform Identification
The Waveform ID and Description fields are populated automatically. These fields can then be edited as desired.
The Type field indicates whether the waveform is defined as a normal Acceleration waveform or a PeakVue waveform.
mk:@MSITStore:C:\RBMsuite\sys\helpmsg\DIAGNO~1.CHM::/MODBUS.html
18/05/2016
Data Transfer
Page 34 of 106
mk:@MSITStore:C:\RBMsuite\sys\helpmsg\DIAGNO~1.CHM::/MODBUS.html
18/05/2016
Data Transfer
Page 35 of 106
Get Value(s)
Single trend values can also be acquired on demand by right clicking on a Data Source (Value) and selecting Get Value
(s). This will begin rapidly retrieving trend data values.
mk:@MSITStore:C:\RBMsuite\sys\helpmsg\DIAGNO~1.CHM::/MODBUS.html
18/05/2016
Data Transfer
Page 36 of 106
Multiple trend values can be acquired simultaneously by selecting Get Value(s) at a higher level of the tree.
Refresh Device
Its important to note that after the initial auto-discovery of a 1420 Smart Wireless Gateway, any configuration
changes to the 1420 (e.g. with a 375/475 communicator or with AMS Device Manager) will not automatically be
updated in the Data Import program.
If the 1420 configuration is changed, the Refresh Device command can be used to import the updated device
information, such as the Update rate and alarm limits, without having to completely delete the device and then Add it
back.
This command can be executed by right clicking the 1420 in the Device Hierarchy tree and selecting Refresh Device, or
by highlighting the 1420 and selecting Refresh Device from the Edit menu.
If possible, existing mappings will be retained. However, some user changes may be lost as the information about the
device hierarchy is updated. For example, if the data units have changed the point mappings will be deleted.
mk:@MSITStore:C:\RBMsuite\sys\helpmsg\DIAGNO~1.CHM::/MODBUS.html
18/05/2016
Data Transfer
Page 37 of 106
Add Device
Highlight the server in the Device Hierarchy tree, and click the Add Device button in the top left corner. Or, from the
Edit menu, select Add, then Device. Or, right click on the server and select "Add", then "Device".
Device Hierarchy
The Device Type window will open. Use the drop down list to select either Rosemount 3420 Fieldbus Interface
Module or Other.
mk:@MSITStore:C:\RBMsuite\sys\helpmsg\DIAGNO~1.CHM::/MODBUS.html
18/05/2016
Data Transfer
Page 38 of 106
mk:@MSITStore:C:\RBMsuite\sys\helpmsg\DIAGNO~1.CHM::/MODBUS.html
18/05/2016
Data Transfer
Page 39 of 106
mk:@MSITStore:C:\RBMsuite\sys\helpmsg\DIAGNO~1.CHM::/MODBUS.html
18/05/2016
Data Transfer
Page 40 of 106
For a 16 bit value (which has 2 bytes or 1 word) with byte order A,B:
A,B = None (no swapping)
B,A = Swap Bytes (simply reverses the byte order)
A,B = Swap Words (only one word so nothing to swap)
B,A = Swap Bytes within Words (only one word, so this is the same as byte swapping)
Trend Sub-Tab
mk:@MSITStore:C:\RBMsuite\sys\helpmsg\DIAGNO~1.CHM::/MODBUS.html
18/05/2016
Data Transfer
Page 41 of 106
Other Sub-Tab
For the Other device type, an additional Other sub-tab is displayed. The selection of whether to use Extended Modbus
addressing was made previously during the Add Device step. If at some time later this needs to be changed, the
checkbox is available for update on this tab.
mk:@MSITStore:C:\RBMsuite\sys\helpmsg\DIAGNO~1.CHM::/MODBUS.html
18/05/2016
Data Transfer
Page 42 of 106
With a Group highlighted in the Device Hierarchy tree, the lower left window becomes the Group pane, and the
following tabs are displayed:
mk:@MSITStore:C:\RBMsuite\sys\helpmsg\DIAGNO~1.CHM::/MODBUS.html
18/05/2016
Data Transfer
Page 43 of 106
Group - Identification
The ID and Description fields can be edited as desired to identify the group.
The Type field indicates the type of the Group. For example, CSI 9210 or Other.
mk:@MSITStore:C:\RBMsuite\sys\helpmsg\DIAGNO~1.CHM::/MODBUS.html
18/05/2016
Data Transfer
Page 44 of 106
mk:@MSITStore:C:\RBMsuite\sys\helpmsg\DIAGNO~1.CHM::/MODBUS.html
18/05/2016
Data Transfer
Page 45 of 106
mk:@MSITStore:C:\RBMsuite\sys\helpmsg\DIAGNO~1.CHM::/MODBUS.html
18/05/2016
Data Transfer
Page 46 of 106
mk:@MSITStore:C:\RBMsuite\sys\helpmsg\DIAGNO~1.CHM::/MODBUS.html
18/05/2016
Data Transfer
Page 47 of 106
mk:@MSITStore:C:\RBMsuite\sys\helpmsg\DIAGNO~1.CHM::/MODBUS.html
18/05/2016
Data Transfer
Page 48 of 106
Get Value(s)
Data values can be acquired on demand to test the data import configuration settings. Right click on a Data Source
(Value) and select Get Value(s). This will begin rapidly retrieving trend data values.
mk:@MSITStore:C:\RBMsuite\sys\helpmsg\DIAGNO~1.CHM::/MODBUS.html
18/05/2016
Data Transfer
Page 49 of 106
Multiple trend values can be acquired simultaneously by selecting Get Value(s) at a higher level of the tree.
Database, Area, and Equipment levels are displayed in the top right Database Hierarchy window pane.
When the Database level of the tree is highlighted, the bottom right window pane becomes the Database pane, and
the Database Server name and path location are displayed. Company name and Load keywords can be edited in this
pane.
mk:@MSITStore:C:\RBMsuite\sys\helpmsg\DIAGNO~1.CHM::/MODBUS.html
18/05/2016
Data Transfer
Page 50 of 106
Database Hierarchy
When the Area level of the Database Hierarchy tree is highlighted, the bottom right window pane becomes the Area
pane, and the Area ID and Description can be edited.
mk:@MSITStore:C:\RBMsuite\sys\helpmsg\DIAGNO~1.CHM::/MODBUS.html
18/05/2016
Data Transfer
Page 51 of 106
Equipment pane. Here, the Equipment ID, Description, Reference RPM, Speed Conversion Factor, and Speed/Load
type can be edited.
mk:@MSITStore:C:\RBMsuite\sys\helpmsg\DIAGNO~1.CHM::/MODBUS.html
18/05/2016
Data Transfer
Page 52 of 106
When a single Value is dropped onto a Machine, a single Measurement Point is created under the Machine. When a
higher level of the Device Hierarchy tree is dropped onto a Machine, multiple Measurement Points are created under
the Machine.
NOTE: Attempting to drag an entire CSI 6824(R) configuration onto a single machine may exceed the measurement
point limit for one machine. In this case, create a second machine to accommodate the additional data source values,
or select only the desired data source values individually from the CSI 6824(R).
mk:@MSITStore:C:\RBMsuite\sys\helpmsg\DIAGNO~1.CHM::/MODBUS.html
18/05/2016
Data Transfer
Page 53 of 106
mk:@MSITStore:C:\RBMsuite\sys\helpmsg\DIAGNO~1.CHM::/MODBUS.html
18/05/2016
Data Transfer
Page 54 of 106
mk:@MSITStore:C:\RBMsuite\sys\helpmsg\DIAGNO~1.CHM::/MODBUS.html
18/05/2016
Data Transfer
Page 55 of 106
mk:@MSITStore:C:\RBMsuite\sys\helpmsg\DIAGNO~1.CHM::/MODBUS.html
18/05/2016
Data Transfer
Page 56 of 106
The Baseline Date/Time is automatically updated when a new baseline value is set.
Start Collection
To start data collection, select a Device in the Device Hierarchy tree, then click the Start Data Collection button on the
Device - Identification tab. Or, right click the device and select Start Collection. Or, select Start Collection from the Edit
menu.
NOTE: Since the data is stored under Points in the Database, the user cannot start data collection for a device until at
least one data source under the device is mapped to a point.
mk:@MSITStore:C:\RBMsuite\sys\helpmsg\DIAGNO~1.CHM::/MODBUS.html
18/05/2016
Data Transfer
Page 57 of 106
Stop Collection/Storage
The Stop Collection function will stop data collection/storage for the Device.
Data storage can also be stopped at an individual Group level, by right clicking a Group and selecting Stop Storage.
This will allow edits to be made to the Group, such as changing the storage interval, without affecting data
collection/storage for the rest of the Device. Data storage can be restarted by right clicking the Group again and
selecting Start Storage.
NOTE: When Data Storage is stopped on an individual Group, it will be highlighted in yellow along with the Device
Hierarchy branches above it.
mk:@MSITStore:C:\RBMsuite\sys\helpmsg\DIAGNO~1.CHM::/MODBUS.html
18/05/2016
Data Transfer
Page 58 of 106
Pause Storage
Remap to New Database
mk:@MSITStore:C:\RBMsuite\sys\helpmsg\DIAGNO~1.CHM::/MODBUS.html
18/05/2016
Data Transfer
Page 59 of 106
Remap to New Database is used when a database gets too full and needs to be archived. In this case, a new database
is typically created from a .CVB template file and the old database is archived. The data import mappings are stored in
a separate file on the Data Import Server (under: RBMnet\RBMsuite\config\DataImport) and will still be mapped to the
old database. The Remap function remaps the data import links to the new database.
Right-click on the old database and select Mark Mappings, then right-click on the new database and select Move
Mappings. From the popup dialog, select Create Missing Data Import Nodes First. This process will merge data import
related nodes from the old database into the new database. Then it will move the mappings from the points in the old
database to points in the new database.
Reload
When the Data Import Configuration program is open, and the contents of the database / area / equipment / etc. are
modified using another program, the changes do not automatically appear in the Data Import Configuration program.
The Reload command will cause the new contents to be displayed in the Data Import Configuration
program without having to exit and restart the program.
Show Mappings
Right-clicking any level of the Database Hierarchy tree, and selecting Show Mapping, will display a list showing how
the measurement points are mapped.
In a related function, as points are selected in the Database Hierarchy tree, the Device Hierarchy tree will
automatically jump to the mapped Value.
mk:@MSITStore:C:\RBMsuite\sys\helpmsg\DIAGNO~1.CHM::/MODBUS.html
18/05/2016
Data Transfer
Page 60 of 106
Show Mapping
mk:@MSITStore:C:\RBMsuite\sys\helpmsg\DIAGNO~1.CHM::/MODBUS.html
18/05/2016
Data Transfer
Page 61 of 106
mk:@MSITStore:C:\RBMsuite\sys\helpmsg\DIAGNO~1.CHM::/MODBUS.html
18/05/2016
Data Transfer
Page 62 of 106
mk:@MSITStore:C:\RBMsuite\sys\helpmsg\DIAGNO~1.CHM::/MODBUS.html
18/05/2016
Data Transfer
Page 63 of 106
mk:@MSITStore:C:\RBMsuite\sys\helpmsg\DIAGNO~1.CHM::/MODBUS.html
18/05/2016
Data Transfer
Page 64 of 106
Enter the Name of the DeltaV Area where the Control Modules will be imported.
Select whether to create a new Area, or merge with an existing Area.
NOTE: If creating a New Area, this Area will need to be assigned to the DeltaV workstations before the alarms will
appear in those workstations. Also, it will need to be assigned to the Continuous Historian to store trend data. These
steps are not automated by the import process. If merging with an existing Area, the Area will likely already have the
appropriate assignments.
Select whether using DeltaV physical I/O cards, or the Mynah Virtual IO Module (VIM).
Select the DeltaV IO card slot position number to be used.
(For the VIM, select whether it is configured to emulate Cards 57-60 or 61-64.)
(NOTE: For a physical IO card, the configuration is limited to one serial port, with 16 datasets.)
CAUTION: With the Mynah VIM, if the number of datasets created will exceed the limit of the selected card position,
the configuration will spill over into the next card position. In this case, make sure that the next card position is also
available with no existing configuration.
Select whether or not the IO is to be configured for redundancy.
The Alert and Danger alarm limits for the Main Values will be copied from the CSI 6500 channels to DeltaV control
module function blocks. The drop down lists can be used to select (or type in) the desired alarm priority, or to disable
the alarms in DeltaV. CSI 6500 Alert alarms will become DeltaV Hi/Lo alarms, and Danger alarms will become
HiHi/LoLo alarms. The alarm priority can also be specified or disabled for CSI 6500 Channel OK and Monitor Error
alarms.
NOTE: These alarm limits are dynamically updated. If the limits are changed in the CSI 6500 (and the CSI 6824
communication module is refreshed) the limits will automatically be updated in DeltaV.
NOTE: If a CSI 6500 channels alarm outputs are not configured as active, these alarms will not be configured in
DeltaV.
Click Next to continue.
Select Monitors
Select the CSI 6500 monitors to configure in DeltaV. One or more Datasets will be configured in DeltaV for each
selected monitor.
mk:@MSITStore:C:\RBMsuite\sys\helpmsg\DIAGNO~1.CHM::/MODBUS.html
18/05/2016
Data Transfer
Page 65 of 106
Select Parameters
Select the data types to configure in DeltaV.
mk:@MSITStore:C:\RBMsuite\sys\helpmsg\DIAGNO~1.CHM::/MODBUS.html
18/05/2016
Data Transfer
Page 66 of 106
mk:@MSITStore:C:\RBMsuite\sys\helpmsg\DIAGNO~1.CHM::/MODBUS.html
18/05/2016
Data Transfer
Page 67 of 106
Specify Filename
Select the filename and pathname location for creating the DeltaV .fhx import file.
mk:@MSITStore:C:\RBMsuite\sys\helpmsg\DIAGNO~1.CHM::/MODBUS.html
18/05/2016
Data Transfer
Page 68 of 106
Browse
Click Finish to create the import file.
Import to DeltaV
Browse to the .fhx import file and import.
After importing, right click the controller and select Download / Controller.
Connect the CSI 6824 communication module to the DeltaV controller via a Mynah VIM or Serial I/O card.
mk:@MSITStore:C:\RBMsuite\sys\helpmsg\DIAGNO~1.CHM::/MODBUS.html
18/05/2016
Data Transfer
Page 69 of 106
VIMNET Explorer
mk:@MSITStore:C:\RBMsuite\sys\helpmsg\DIAGNO~1.CHM::/MODBUS.html
18/05/2016
Data Transfer
Page 70 of 106
New IO VIM
A VIM icon will be added to the VIMNET tree, with four virtual DeltaV serial cards.
Right click the VIM icon and select Commission
mk:@MSITStore:C:\RBMsuite\sys\helpmsg\DIAGNO~1.CHM::/MODBUS.html
18/05/2016
Data Transfer
Page 71 of 106
Select the VIM to commission from the Decommissioned VIMs list. Click OK.
To link the VIM to the CSI 6824 communication module, right-click one of the virtual serial ports and select Add
device.
Set the Device Address to match the Modbus slave device address of the CSI 6824.
mk:@MSITStore:C:\RBMsuite\sys\helpmsg\DIAGNO~1.CHM::/MODBUS.html
18/05/2016
Data Transfer
Page 72 of 106
Set the Protocol to RTU TCP. The Port number should typically be 502 for Modbus
Leave the Number of Simultaneous Messages set to 1.
To configure a single VIM, select Simplex Device.
To configure two VIMs for redundant operation with two CSI 6824R communication modules, select Redundancy with
No Switching IP and enter the IP address of the second CSI 6824R.
Click OK, then OK again.
The CSI 6824 will then appear in the VIMNET tree as a new device.
mk:@MSITStore:C:\RBMsuite\sys\helpmsg\DIAGNO~1.CHM::/MODBUS.html
18/05/2016
Data Transfer
Page 73 of 106
NOTE: Each port can support up to 16 DeltaV datasets. If importing more than 16 datasets, repeat the CSI 6824
device configuration on multiple ports/cards as needed, using identical configuration settings for each device.
Right click the VIM icon and upload the configuration to the VIM hardware.
mk:@MSITStore:C:\RBMsuite\sys\helpmsg\DIAGNO~1.CHM::/MODBUS.html
18/05/2016
Data Transfer
Page 74 of 106
The .fhx import also creates Control Modules with Function Blocks for each selected value. This is used for scaling the
values, defining alarm limits, and assigning a meaningful tag name to each value. The Control Modules are
automatically assigned to the Controller.
Datasets
The Serial IO card(s) are added to the DeltaV controller IO branch in DeltaV Explorer.
For a Mynah VIM, all four cards are added. NOTE: For redundant configurations, these are 57, 59, 61, and 63.
Datasets
The Serial IO card is automatically configured:
mk:@MSITStore:C:\RBMsuite\sys\helpmsg\DIAGNO~1.CHM::/MODBUS.html
18/05/2016
Data Transfer
Page 75 of 106
Datasets are added for each data type selected from the CSI 6500.
mk:@MSITStore:C:\RBMsuite\sys\helpmsg\DIAGNO~1.CHM::/MODBUS.html
18/05/2016
Data Transfer
Page 76 of 106
Datasets Added
The data type and Dataset Tag name are configured.
mk:@MSITStore:C:\RBMsuite\sys\helpmsg\DIAGNO~1.CHM::/MODBUS.html
18/05/2016
Data Transfer
Page 77 of 106
Control Modules
A control module is created in the specified Area for each of the selected CSI 6500 monitors.
mk:@MSITStore:C:\RBMsuite\sys\helpmsg\DIAGNO~1.CHM::/MODBUS.html
18/05/2016
Data Transfer
Page 78 of 106
CSI 6500 main data values are configured using Analog Input function blocks. The block inputs are automatically
linked to the proper Dataset registers.
The data values are properly scaled using the XD and OUT scale parameters.
Alarm limits are configured, named, and enabled in the function blocks.
Alarms are dynamically updated by bringing in the alarm limits from the CSI 6500 in separate linked function blocks.
The alarm state registers are also optionally read directly from the CSI 6500 as Input Parameters that are fanned out
with Boolean logic blocks into individual alarms.
The channel fault states are also read from the CSI 6500 as Analog Input blocks. Since CSI 6500 channel OK states
are normally 1 to indicate OK and 0 to indicate a fault, they are inverted with a Not function block so that 0 indicates
OK and 1 indicates a fault. Channel fault alarms are then created.
The control modules are assigned a graphical Faceplate and Details display.
Complete descriptive text information for each CSI 6500 monitor and channel is added as text input parameter blocks,
which will be displayed on the faceplate.
The control modules are automatically assigned to the controller.
In the DeltaV Operate Run program, clicking a CSI 6500 alarm in the alarm banner will open a faceplate view of the
data, with no additional configuration required.
A DeltaV Dynamo Set is available to easily assign additional CSI 6500 bargraph or value box displays to graphic
screens.
Default function block / input parameter / alarm name examples
mk:@MSITStore:C:\RBMsuite\sys\helpmsg\DIAGNO~1.CHM::/MODBUS.html
18/05/2016
Data Transfer
Page 79 of 106
These names are created automatically with a fixed naming convention within each Control Module. This fixed naming
convention facilitates the linking of Faceplate and Dynamo templates within the DeltaV Operate Run graphics program.
MV1
MV1_ALARMS
CH1_NOT_OK_ALM
NA_PK_1
NB_PK_1
NA_PH_1
MULTVAL
NGL_1
MV1_HI_ALM
MV1_LO_LO_ALM
MV1_AL-P_ALM
MV1_DG-N_ALM
Faceplate Displays
mk:@MSITStore:C:\RBMsuite\sys\helpmsg\DIAGNO~1.CHM::/MODBUS.html
18/05/2016
Data Transfer
Page 80 of 106
Clicking a CSI 6500 alarm, in the DeltaV Alarm Banner, will open the associated faceplate. The faceplate is associated
with the specific control module (one per CSI 6500 monitor) where the alarm was generated.
The faceplate displays information from several data sources within the control module. Descriptive information
includes zone name (if used), control module name, CSI 6500 monitor ID and Description, followed by channel
descriptions and channel IDs.
The Main Values are displayed with units. The bargraph fill level represents the Main Value in proportion to the
configured measuring range, which is also shown. The Alert and Danger alarm limit levels are indicated by triangular
markers.
If the CSI 6500 Channel OK and Monitor Error states are imported to the DeltaV Control Modules, then the background
of the Main Values will be colorized gray to indicate Good or maroon to indicate Bad. If the state values are not
imported, the background color will remain gray.
Any alarms within the control module will be displayed in the alarm window.
The Unit name (if used) is displayed below the alarm window.
The left hand button at the bottom of the faceplate opens the Details display. This display includes details on module
errors. Module errors are indicated by a blue line flashing underneath this button.
The second button is to open a Primary Control picture. By default this button is not assigned to any picture.
The third button opens a live trend display of the monitor data.
mk:@MSITStore:C:\RBMsuite\sys\helpmsg\DIAGNO~1.CHM::/MODBUS.html
18/05/2016
Data Transfer
Page 81 of 106
The fourth button opens the control module in the Control Studio program.
The fifth button opens a historical trend plot in the Process History View window.
The last button on the right acknowledges all alarms in the control module.
Dynamos
CSI 6500 Dynamos provide a convenient way to add graphical data display elements to a picture.
To add a Dynamo to a graphic, first launch the DeltaV Operate Run program.
The program starts in Run mode. Switch to Configure mode by pressing the <Ctrl><W> key combination.
Open the desired graphic from the Pictures folder.
Or, create a new blank picture from the Templates folder. Select a template picture that matches the size of your
display screen resolution (e.g. Main1280 or Main1680).
mk:@MSITStore:C:\RBMsuite\sys\helpmsg\DIAGNO~1.CHM::/MODBUS.html
18/05/2016
Data Transfer
Page 82 of 106
Open the template, then select File / Save As to save it with a new picture name. Click in the middle of the picture to
highlight the instructional text, and press delete to remove it.
With the desired picture open, next open the MHM Dynamo Set.
Click the desired Dynamo and drag it from the Dynamo Set window onto the desired graphic Picture window. Select a
dual bargraph or value box for dual channel CSI 6500 monitors. Select a single bargraph or value box for CSI 6500
monitors configured to calculate a single value (e.g. Smax or Tandem).
mk:@MSITStore:C:\RBMsuite\sys\helpmsg\DIAGNO~1.CHM::/MODBUS.html
18/05/2016
Data Transfer
Page 83 of 106
mk:@MSITStore:C:\RBMsuite\sys\helpmsg\DIAGNO~1.CHM::/MODBUS.html
18/05/2016
Data Transfer
Page 84 of 106
The Browse window opens. Confirm the Object Type is set to Module Parameters. Browse to the desired Area, then
click once to highlight the desired Control Module. At this point, instead of browsing down further into the control
module, simply click the Apply Now button.
mk:@MSITStore:C:\RBMsuite\sys\helpmsg\DIAGNO~1.CHM::/MODBUS.html
18/05/2016
Data Transfer
Page 85 of 106
mk:@MSITStore:C:\RBMsuite\sys\helpmsg\DIAGNO~1.CHM::/MODBUS.html
18/05/2016
Data Transfer
Page 86 of 106
The Bargraph Dynamos include Channel Descriptions, Main Values / Units, and Channel OK states. The bargraph fill
level represents the Main Value in proportion to the configured measuring range, which is also shown. The Alert and
Danger alarm limit levels are indicated by triangular markers.
The Value Box Dynamos include Channel Descriptions, Main Values, and Units.
If the CSI 6500 Channel OK and Monitor Error states are imported to the DeltaV Control Modules, then the background
of the Main Values will be colorized Gray to indicate Good or Maroon to indicate Bad. Also, the Channel OK LEDs will
be lit up in green to indicate Good or grayed out to indicate Bad.
If the State values are not imported, the background color and the OK LEDs will both remain Gray.
The Bargraph fill is colorized Green, Yellow, or Red based on the Alarm State of the Control Module function blocks
(MV1, MV2, or MV3). The Value Box borders and the measurement point Locator Boxes are also colorized Yellow or
Red to indicate alarm state.
Note that if the picture window is not sized correctly for the monitor resolution, it will get stretched or compressed.
This will cause the bargraph alarm limit position markers to be vertically shifted and incorrectly displayed.
Clicking on a Dynamo opens the faceplate display of the assigned Control Module.
Misc.
The Channel IDs/Descriptions, Measuring Range, and Units are not updated dynamically. If these values are changed
in the CSI 6500, they must either be imported again or manually entered in DeltaV.
Configure Controller
mk:@MSITStore:C:\RBMsuite\sys\helpmsg\DIAGNO~1.CHM::/MODBUS.html
18/05/2016
Data Transfer
Page 87 of 106
The Ovation import file will automatically create Analog Points for each of the CSI 6500 data values. Before importing
these measurement points, the controller I/O device needs to be configured in Ovation.
In Ovation, under the desired controller drop, select which of the five I/O Devices to use and set the I/O Device type to
Modbus Master.
mk:@MSITStore:C:\RBMsuite\sys\helpmsg\DIAGNO~1.CHM::/MODBUS.html
18/05/2016
Data Transfer
Page 88 of 106
Device Hierarchy tree, right click the CSI 6500 device and select Create Import File, then For Ovation...
mk:@MSITStore:C:\RBMsuite\sys\helpmsg\DIAGNO~1.CHM::/MODBUS.html
18/05/2016
Data Transfer
Page 89 of 106
Enter the I/O Device and PLC Host Index that were chosen in Ovation.
Select whether to transfer the CSI 6500 alarm limits to the Ovation measurement point configurations.
Select which of the 4 Hi and 4 Lo Ovation alarm levels to associate with the CSI 6500 Alert and Danger alarms (NOTE:
4 is the highest alarm severity in Ovation).
Select which priority level 1-8 to associate with each CSI 6500 alarm type (NOTE: 1 is the highest alarm priority in
Ovation).
Click Next to Continue.
Select Monitors
Select the CSI 6500 monitors to configure in Ovation.
mk:@MSITStore:C:\RBMsuite\sys\helpmsg\DIAGNO~1.CHM::/MODBUS.html
18/05/2016
Data Transfer
Page 90 of 106
Select Monitors
Selecting/Deselecting the top box, will select/deselect all monitors.
The monitors are listed by Monitor ID and Description. Hovering the mouse pointer over a monitor will display the
monitor type.
Click Next to continue.
mk:@MSITStore:C:\RBMsuite\sys\helpmsg\DIAGNO~1.CHM::/MODBUS.html
18/05/2016
Data Transfer
Page 91 of 106
The Export column allows individual values to be removed from the import file.
The Parameter column lists the type of data value being exported from the CSI 6500.
The Type column lists the type of object being imported into Ovation.
The Rack ID column allows global editing of all names. It will copy a change to all names below the selected row, until
it encounters a different ID.
The Module column also allows editing of multiple names. It will copy a change to all names below the selected row,
until it encounters a different ID.
The Name column allows custom editing of the entire tag name.
mk:@MSITStore:C:\RBMsuite\sys\helpmsg\DIAGNO~1.CHM::/MODBUS.html
18/05/2016
Data Transfer
Page 92 of 106
Clicking the Browse button automatically inserts the default file name and correct extension type. Edit the filename if
desired, and/or click Save.
Browse
Click Finish to create the import file.
mk:@MSITStore:C:\RBMsuite\sys\helpmsg\DIAGNO~1.CHM::/MODBUS.html
18/05/2016
Data Transfer
Page 93 of 106
Run Command
The CSI 6500 Analog Points will be added to the Ovation database.
NOTE: To later import an update using the same point names, omit the n flag which will allow duplicate point names
to be overwritten.
Download to Controller
Use the Download / Clear / Load process to load the database changes to the controllers.
If changes have been made to the controller configuration, such as configuring one of the five I/O devices to be a
Modbus Master, the Download and Clear commands are required first before using the Load command.
When simply adding new Analog Points to an existing controller configuration, for example after importing an updated
CSI 6500 import file, only the Load command is required.
CAUTION: An Ovation Administrator should be consulted before using the Download / Clear commands, as this
process involves clearing and rebooting the controllers which will interrupt their operation.
To download controller configuration changes, right click the controller Drop and select Download.
mk:@MSITStore:C:\RBMsuite\sys\helpmsg\DIAGNO~1.CHM::/MODBUS.html
18/05/2016
Data Transfer
Page 94 of 106
The Download step must be completed twice, once to download the Primary Drop and again to download the
Secondary Drop.
Select the Primary or Secondary Drop in turn, then click the Finish button.
mk:@MSITStore:C:\RBMsuite\sys\helpmsg\DIAGNO~1.CHM::/MODBUS.html
18/05/2016
Data Transfer
Page 95 of 106
Immediately after performing the Download step, right click the controller Drop and select Clear. This will clear the old
configuration information from the controllers and cause them to reboot.
mk:@MSITStore:C:\RBMsuite\sys\helpmsg\DIAGNO~1.CHM::/MODBUS.html
18/05/2016
Data Transfer
Page 96 of 106
The Clear step must be completed twice, once to clear/reboot the Primary Drop and again to clear/reboot the
Secondary Drop.
Select the Primary or Secondary Drop in turn, then click the Finish button.
A final confirmation prompt is displayed before the clear/reboot is performed. Click the OK button to continue.
To load the Analog Point configurations, wait until the controllers have rebooted (which can be confirmed with the LED
displays on the controller hardware) then perform a Load command.
Right click the controller Drop and select Load.
The Load step must be completed twice, once to load the Primary Drop and again to load the Secondary Drop.
Select the Primary or Secondary Drop in turn, then click the Finish button.
mk:@MSITStore:C:\RBMsuite\sys\helpmsg\DIAGNO~1.CHM::/MODBUS.html
18/05/2016
Data Transfer
Page 97 of 106
mk:@MSITStore:C:\RBMsuite\sys\helpmsg\DIAGNO~1.CHM::/MODBUS.html
18/05/2016
Data Transfer
-Sets
-Sets
-Sets
-Sets
-Sets
-Sets
-Sets
Page 98 of 106
mk:@MSITStore:C:\RBMsuite\sys\helpmsg\DIAGNO~1.CHM::/MODBUS.html
18/05/2016
Data Transfer
Page 99 of 106
mk:@MSITStore:C:\RBMsuite\sys\helpmsg\DIAGNO~1.CHM::/MODBUS.html
18/05/2016
Data Transfer
mk:@MSITStore:C:\RBMsuite\sys\helpmsg\DIAGNO~1.CHM::/MODBUS.html
18/05/2016
Data Transfer
Select the desired macro from the Available macros list. In the right hand window, enter the CSI 6500 measurement
point names for each variable. After assigning the point names, click OK, then click on the graphic diagram to insert
the macro.
When adding the Single Channel Bargraph or Value Box macro to a graphic, assign the point names as follows:
$D1 = Channel (1 or 2) Main Value
$D2 = Channel (1 or 2) OK/Clear Status
$D3 = Monitor Error Status
mk:@MSITStore:C:\RBMsuite\sys\helpmsg\DIAGNO~1.CHM::/MODBUS.html
18/05/2016
Data Transfer
When adding the Dual Channel Bargraph or Value Box macro to a graphic, assign the point names as follows:
$D1 = Channel 1 Main Value
$D2 = Channel 1 OK/Clear Status
$D3 = Channel 2 Main Value
$D4 = Channel 2 OK/Clear Status
$D5 = Monitor Error Status
-When adding the Channel 3 Bargraph or Value Box macro to a graphic, assign the point names as follows:
$D1 = Channel 3 Main Value
$D2 = Channel 1 OK/Clear Status
mk:@MSITStore:C:\RBMsuite\sys\helpmsg\DIAGNO~1.CHM::/MODBUS.html
18/05/2016
Data Transfer
-When adding the Measurement Point Locator Box macro to a graphic, assign the point name as follows:
$D1 = Channel (1, 2, or 3) Main Value
Download Changes
After changes are made to graphics screens, they must be downloaded to the Worksation.
mk:@MSITStore:C:\RBMsuite\sys\helpmsg\DIAGNO~1.CHM::/MODBUS.html
18/05/2016
Data Transfer
mk:@MSITStore:C:\RBMsuite\sys\helpmsg\DIAGNO~1.CHM::/MODBUS.html
18/05/2016
Data Transfer
Open the graphic in the Graphics program to view. Note if changes are made while the graphic is running, the screen
must be refreshed to view the changes.
of the Main Values is colorized black to indicate Good or magenta to indicate Bad, based on the
Monitor Error states. Also, the Channel OK LEDs will be lit up in green to indicate Good or grayed out
If communication is completely lost with the CSI 6824(R), the values/colors will freeze but the quality
bad data.
The bargraph fill is colorized green, yellow, or red based on the main values compared to the alarm limits of the
measurement points. The Value Box borders and the measurement point Locator Boxes are also colorized yellow or red
to indicate alarm state.
mk:@MSITStore:C:\RBMsuite\sys\helpmsg\DIAGNO~1.CHM::/MODBUS.html
18/05/2016
Data Transfer
mk:@MSITStore:C:\RBMsuite\sys\helpmsg\DIAGNO~1.CHM::/MODBUS.html
18/05/2016