Meriam MFC5150 HART Communicator Manual - Manual (Page 38)

32
4.5 Using Generic HART
® Communication
The Generic HART ® Communication mode starts automatically when HART ® communication is initiated
with a device for which no Device Specific DD (device object file) is stored in the handhelds flash memory.
When this occurs, line two of the display will indicate “Generic” and the device tag number.
In general, the Generic HART ® mode operates similarly to its device specific DD counterpart (see HART ®
Communication section of this manual for more details). However, the communicator does not display Device
Specific related communication menus or options when in the Generic communication mode. For example, the
Zero and Sensor trim menu options (normally executed by Device Specific commands) are not displayed for
pressure transmitters without DD support.
4.6 Managing Device Configuration Files
The current parameter settings for a connected HART ® device can be stored into a file on the uSD system
card for later use. This file can then be used in duplicating settings to a new device of the same model,
restoring settings to a repaired device, and for documentation purposes. What parameters are stored is
defined by the manufacturer of the HART
® device.
If the Commit Changes button is illuminated, the communicator parameters should be committed
to the device before storing or retrieving a configuration. If the parameters are not committed and the
user chooses to store the parameters, the user is warned that the parameters do not match the device. If
the user decides to continue with the store the file is marked as “As Modified”. Any online modifications
to parameters done prior to restoring a configuration that were not committed to the device are lost, if
those parameters are in the stored configuration.
.
Selecting the Configuration Options button will bring up a list of configuration actions.
To store a device configuration, the user selects Configuration Store.
Dialog boxes direct the user to the appropriate actions:
1. The user is prompted for a file name. The default file name is the tag parameter defined in the device. The
user may change this to any file name not currently in use for this device model. Unsupported characters are
grayed-out and ignored. If the user picks a name already in use, the communicator gives them an option of
cancelling or overwriting the current file.
2. If the configuration has not already been marked as “As Modified”, the user has to choose a configuration
type. The choices are “As Found” (device settings before modification) or an “As Left” (device settings after
modification).
The configuration file is saved in the communicator uSD card memory and can be restored to update any
transmitter of the same model and revision.
To restore a device configuration, the user selects Configuration Restore. The configuration files are
segregated by device model and revision. When a restore is requested, only the configurations that
pertain to the model of the connected device are presented. The user chooses a file and selects Accept
(࿌). This will restore the stored parameters to the communicator’s
parameter cache. The parameter
changed indicator beside affected parameters will appear, and the Commit Changes button is illuminated.