beautypg.com

Asset management solutions (ams), Installation, Operating – KROHNE BM 100 HART User Manual

Page 5: 4 asset management solutions (ams)

background image

BM100 Remote Operation - HC 275 / AMS

Dev.-Rev. EE, DD-Rev. 03

© 2000 KROHNE Meßtechnik D-47058 Duisburg

Page

5

4 Asset Management Solutions (AMS)

4.1 Installation

Refer to the “AMS Installation Guide” (Fisher Rosemount): “Installing Modems” (section 5)

and “Wiring Diagrams” (appendix B).

AMS Configuration:

If the BM100 Device Description is not already installed on the AMS System an
BM100 Device Installation Kit“ (on floppy disk / CD-ROM from KROHNE) is needed.
For installing the DD with the Installation Kit refer:

AMS 1.3: to the “AMS Installation Guide” (Fisher Rosemount), section 3 ➪ “Installing Device
Descriptions for Field Devices”
“Manually Installing Device Types” ;
AMS 1.4: to the “AMS User’s Guide” (Fisher Rosemount), section 4 ➪ “Adding New Device
Types to AMS”
“Install Device Types Manually” .

4.2 Operating

Refer to the BM100 Menu Tree AMS (Attachment B).
Some additional comments follow:

To “open” service functionality the user has to register as specialist. To do this, one should

invoke the “Service Code” method from the Device Context Menu and enter the correct service
password. Note, that after the Device Connection View is reopen (or the same method is invoked
with improper service password) specialist authorization is lost, and all service
parameters/functions (D/A trim, Linearity calibration, Reset user EEPROM, Reset factory
EEPROM
) again become inaccessible.

As opposed to the HC275, handling of the Strap Table within AMS can be carried out in two

ways: besides the old scheme (Strap table input, Strap table suppress methods) it can be
controlled directly, from the three configuration displays. Due to transmitter implementation
peculiarities some steps should be sequentially undertaken to create or change the table from
configuration displays. The matter is that all the changes in table elements are initially
accumulated in instrument RAM. The trigger event that launches the table’s burning into
EEPROM, is Command #143 (Write Conversion Table Point Number) that deals with a single
parameter, being the ‘Number of points’ variable (configuration display “Strap Table, 1-20”).
Just this command initiates the check of complete table and in case ‘twas successful – activates
the burning procedure. Worth noting that as soon as every table point depends on the ‘Number
of points
’ variable (in terms of VALIDITY clause), the latter is always written to instrument
before the points’ set. Hence while augmenting table the user will always be prompted “Error
‘Table not monotonous’ happened writing ‘Number of points’”. Only after this response the
table (changed elements) is copied to the instrument RAM. To burn it into EEPROM one have
to “change” again the number (say, 10 to 10, or 4 to 4) and press ‘Apply’ again. All the
commentaries above can be summarized as follows:

1. If the number of points is changed (with or without changes of the table contents), the user

should ignore the first possible error response after pressing ‘Apply’ (‘Table not monotonous’
happened writing ‘Number of points’), “change” the number of points again to desirable one
(i.e. reenter exactly the same value) and again press ‘Apply’.

2. If the number of points is preserved but some table items are changed, the user should press

‘Apply’ (thus transferring changed items to device), then reenter the number of points (as above)
and press ‘Apply’ again - otherwise the updated point(s) will be “in play” until the first power
reset.