
AMS DEVICE MANAGER 7.0 RELEASE NOTES

--------
CONTENTS 
--------
1.  New features
2.  Hardware and software requirements
3.  Supported FOUNDATION fieldbus devices
4.  FOUNDATION fieldbus device installation 
5.  Supported HART devices
6.  HART devices (and device revisions) no longer supported
7.  Device issues
8.  Supported HART multiplexers
9.  Other supported HART I/O interfaces
10. Supported HSE linking devices 
11. Supported documenting calibrators
12. Calibration/calibrator issues
13. Control system interface issues
14. Supported operating systems
15. Operating system issues
16. Supported PCs
17. Supported peripherals
18. Peripherals issues
19. Installation and upgrading issues
20. Removing (uninstalling) AMS Device Manager
21. Database/SQL Server
22. Distributed AMS Device Manager systems 
23. Handheld Communicator Interface
24. AMS Device Manager Web Services
25. AMS Asset Portal
26. SNAP-ON applications - installation
27. SNAP-ON applications  issues
28. Selected open discrepancies
                                                                               

---------------
1. NEW FEATURES
---------------
- The DeltaV System Interface now supports fieldbus devices along 
  with HART devices. They can be configured in AMS Device Manager 
  and their alerts can be recorded in the AMS Device Manager 
  database and displayed in Alert Monitor.

- The DeltaV System Interface now supports DeltaV Safety 
  Instrumented Systems (SIS). A new security permission has been
  added that controls users ability  to write to SIS devices on 
  unlocked logic solvers.

- The Ovation System Interface now supports fieldbus device alerts
  along with HART devices. The alerts can be recorded in the AMS 
  Device Manager database and displayed in Alert Monitor.

- A new FOUNDATION fieldbus High Speed Ethernet (FF HSE) interface
  that supports the Rosemount 3420 FIM.

- A new interface to a Remote Operations Controller (ROC Interface).

- Ability to connect devices to any station in a distributed system.

- Ability to access all devices in a distributed system from any 
  station.

- Calibration support for fieldbus (temperature, pressure, and 
  analytical) devices.

- Enhanced flow verification and external lab support for flow 
  devices.

- Enhanced intelligent calibration support for switches.

- Enhanced polling on certain HART multiplexer networks.

- Dynamic Variable Monitoring with certain HART multiplexers for
  faster updates to OPC Clients.

- Display of AMS ValveLink SNAP-ON Application Performance 
  Diagnostic Alerts.

- Support for the CEAG remote I/O system in the HART Over PROFIBUS
  System Interface. For details on older service bus versions, see
  the download section of 
  http://www.ceagah.de/products/lbfb/fb8203/en/fds.html and for 
  the more modern HART via Profibus version see the download 
  section of http://www.ceagah.de/products/lbfb/fb8205/en/fds.html.

- Support for the Spectrum CONNECTS multiplexer in the HART 
  Multiplexer System Interface.

- Support for Microsoft Windows XP Professional, Service Pack 1A 
  and Service Pack 2 (English version only); Windows Server 2003, 
  Standard Edition; Windows 2000 Professional, Service Pack 4; 
  Windows 2000 Server, Service Pack 4.

- Additional HART and fieldbus devices.

- Ability to launch device manuals (PDFs).

- Ability to launch the CSI 9210 Rev 2 Users Manual (.PDF) by 
  manually right clicking the devices context menu and selecting
  Help.


-------------------------------------
2. HARDWARE AND SOFTWARE REQUIREMENTS
-------------------------------------
It is recommended that you upgrade to Acrobat Reader 7.0.2 to 
enable full functionality of PDF viewing in AMS Device Manager.

See the AMS Suite: Intelligent Device Manager Installation Guide 
for hardware and software requirements for AMS Device Manager and 
its supported system interfaces.

AMS Device Manager users will need to re-license their software if
they use the following:

  - AMS ValveLink SNAP-ON Application, since all AMS ValveLink tag 
    count enforcement is now done by ValveLink and not AMS Device 
    Manager. Current ValveLink users must re-license after upgrading
    to AMS Device Manager 7.0; otherwise they will default to 5 
    FieldVue tags.

  - AMS Device Manager 6.x Client Stations.

  - HART over PROFIBUS interface.

  - Ovation System Interface.

  - New system functionality.


----------------------------------------
3. SUPPORTED FOUNDATION FIELDBUS DEVICES
----------------------------------------
The FOUNDATION fieldbus device types and device revisions supported
in AMS Device Manager 7.0 can be found in 
PDF Documentation/SupportedDeviceList.pdf on the AMS Device Manager
7.0 installation CD1.

They are automatically installed on both new and existing AMS
Device Manager workstations during installation. 

-------------------------------------------
4. FOUNDATION FIELDBUS DEVICE INSTALLATION
-------------------------------------------
To install a new FOUNDATION fieldbus device type that was not
delivered on the 7.0 installation CD:

1. Shut down the AMS Device Manager application and servers before
   performing this procedure. 

2. On an AMS Device Manager Server Plus or an AMS Device Manager
   Client SC, copy the device files to the following location:
 	
   AMS\Devices\FF\<mfg_id>\<dev_type_id>

   where <mfg_id> is the manufacturers six-digit hexadecimal 
   identification number, and where <dev_type_id> is the device 
   types four-digit hexadecimal identification number.  

3. If .fhx and .alm files were not provided, generate them, as 
   follows:

   a. Start|Run.
   b. Enter "cmd" in the Open field of the Run dialog box.
   c. At the command prompt enter "C:". Press Enter.
   d. Type "CD AMS\Bin". Press Enter.
   e. Type the following:

   AmsFFFhxGen d <drive>:\AMS\Devices\FF <drive>:\AMS\Devices\FF\
   <mfg_id>\<dev_type_id>\<filename>.cff v 8.3

where <drive> is the drive letter where you installed AMS Device 
Manager, and <filename> is the name of the .cff file. Press Enter.

4. In the same command prompt window as step 2, type the following:

   AmsMrgGen <drive>:\AMS\Devices\FF\<mfg_id>\<dev_type_id>\
   <filename>.fhx m i
   
    Press Enter. The .mrg and .ini files are generated. 

5. Rename your ddinstal.ini file in the \AMS\Devices folder to 
   ddinstal_KEEP.ini.  

6. Copy the ddinstal.ini file from the \AMS\Devices\FF\<mfg_id>\
   <dev_type_id>\ folder to the \AMS\Devices folder.

7. Copy the .alm file from the \AMS\Devices\<mfg_id>\FF\<dev_type_id>\
   folder to the \AMS\Devices\DevAlmMsgs\ folder.

8. Start Add Device Type Manually from the Windows taskbar: 

   Start|Programs|AMS Device Manager|Add Device Type Manually

9. Follow the prompts. On the Get Source dialog box, browse to 
   the \AMS\Devices folder. Complete the Add Device Type Manually
   wizard.

10. Delete the file ddinstal.ini from the \AMS\Devices folder.
  
11. Rename the file ddinstal_KEEP.ini to ddinstal.ini.

If you are installing a new device type onto a distributed AMS 
Device Manager system, you need to install the new device files 
on each of the AMS Device Manager PCs in the distributed system,
as follows:

1. Copy the device files (both the original files and the files 
   created in steps 3 and 4) from the PC above to the next PC. 
   Copy the files into the appropriate folder: AMS\Devices\FF\
   <mfg_id>\<dev_type_id>

2. Execute steps 5-11 above.


-------------------------
5. SUPPORTED HART DEVICES
-------------------------
The HART device types and device revisions supported in AMS Device
Manager 7.0 can be found in PDF Documentation/
SupportedDeviceList.pdf on the AMS Device Manager 7.0 installation
CD1.

They are automatically installed on both new and existing AMS 
Device Manager workstations during installation. 

AMS Device Manager only supports HART DD functionality up to HART
revision 5. Do not load any Device files/DDs that include HART 
revision 6 functionality. 

Any product safety or device description updates issued after an
AMS Device Manager version is released must be installed after the
initial installation.

All other compliant HART revision 3 or greater devices not 
specifically mentioned in this list are supported as Generic devices.

----------------------------------------------------------
6. HART DEVICES (AND DEVICE REVISIONS) NO LONGER SUPPORTED
----------------------------------------------------------
Support for the following devices has been discontinued in AMS Device Manager:

Manufacturer	   Device Name	    	   Device, DD Rev    When Discontinued 
------------	   ------------	   	   --------------    -----------------
DeZURIK            POSITIONER         	   1,DDRev 3  	     v7.0
Elcon Instruments  2700e multiplexer       2,DDRev 1  	     v7.0
Moore Products     60D Valve Positioner    2,DDRev 1	     v7.0
Siemens SITRANS    F Ultrasonic Flow Meter 1,DDRev 1	     v7.0
Besta              CLS4-20 		   1.1	    	     v6.0
Rosemount	   3144P		   3,DDRev 1  	     v6.0
Rosemount	   81C/3081C	      	   1	    	     v5.0
Analytical


If you have any Besta CLS4-20 devices in AMS Device Manager, these
are the effects:

- They will appear in AMS Device Manager as Generic devices.

- For their historical configurations, you will only see the fields
  that apply to Generic devices.

- For their Audit Trail events, the event details will display the 
  variable name from the Device Description vs. the variable label, 
  and for enumerated values the value will be displayed but not
  its corresponding text.  

- For Alert Monitor, you will no longer receive the "More" status 
  alerts for these devices.


----------------
7. DEVICE ISSUES 
----------------
- Access the Foundation support website to search for other known
  issues: http://www.emersonprocess.com/Systems/support/index.asp 

- Device configuration change bit not set for some devices: 
  This issue involves device configuration changes to the following 
  HART devices used on a HART-communicating control system:

       - Rosemount 3044c Rev. 1
       - Rosemount Analytical 3081 Conductivity Rev. 1

  Normally, to ensure that all configuration changes made to a 
  device are captured by the control system, all devices with 
  changed configurations should set their configuration change bit 
  to flag the change. Setting the configuration change bit allows 
  the control system to request configuration upgrades.

  The HART devices listed above have exhibited inconsistent 
  behavior in setting the configuration change bit when a device 
  configuration change is made.

  The source of the problem is in the HART device, not AMS Device 
  Manager. Because the configuration change bit is not set for the
  device, the control system is not always made aware that a change
  to the device's configuration has occurred. A device that does 
  not have the configuration change bit set can affect control of 
  the plant processes, as the control system could be using 
  obsolete data to control the process. 

  To prevent process control from being affected by the problem 
  with these devices, you should verify that changes made to the 
  device have been uploaded to the control system. The Apply 
  Parameter Modifications message box that is displayed when 
  applying changes to device parameters reminds you to verify the 
  changes.

- Do not use a front slash (/) character in the Manufacturer,
  Model, Revision, or Serial Number fields for a conventional
  device if you plan to use Drawings and Notes for the device.

- Perform a Scan New operation on your network if an unknown 
  device is displayed after performing a database Restore operation. 

- If the transfer, OK, Cancel, Apply, and Help buttons on the 
  Configuration or Compare Configurations windows are obscured 
  by a tab, either use the Tab key to navigate to them and 
  the Enter key to execute them, or press Esc to exit the 
  window without making changes. (Note that even if the buttons 
  are only partially obscured, you still may be unable to click 
  them.)

- On the Hardware tab of the Resource block of some fieldbus 
  devices, changing the restart parameter to "defaults" changes 
  the fieldbus device tag and address for this device, causing 
  AMS Device Manager to be unable to communicate with the device.
  Recommission the device back to its previous device tag and 
  address.

- Use the Configure dialog box to edit parameters.

E&H PROMASS 63:
- On the Pulse/Freq Output tab on the Configuration or
  Compare Configurations windows, changing the Operation mode
  from Frequency to Pulse and applying the change will result
  in AMS Device Manager being unable to read the Pulse Value and 
  Pulse Width. AMS Device Manager will report a CM Response Code 
  error whenever it tries to read these variables. This error is 
  due to a device error, not an AMS Device Manager error. If 
  another interface (other than the HART interface) is used to 
  change the Operation mode to Pulse, such as the device's local
  interface, the device will correctly accept it. If the HART
  interface is used to change this parameter via AMS Device 
  Manager, the device will not correctly implement the change. 
  Once AMS Device Manager is used to change the mode to Pulse,
  if the device is power cycled, when it comes back up it will 
  correctly report the values for Pulse Value and Pulse Width.

Fisher FIELDVUE DVC5000 Rev. 2 and 3: 
- The DVC5000 revision 3 does not support Dynamic Variable 
  Monitoring.

Masoneilan SVI Controller:
- The Configuration window has no OK or Apply buttons; changes 
  must be committed by selecting Download Configuration from the 
  device context menu.

- When performing a compare/replace operation on Masoneilan SVI 
  device, you must manually replace the device and manually enter
  the configuration properties.

Rosemount Analytical OXT4000 Rev. 1:
- In some instances, the 4-20mA analog output signal cannot be 
  trimmed to within approximately 10% of the signal low level 
  range using the D/A Trim Method. As an interim solution, use 
  the D/A Trim method to gradually trim the analog output signal 
  to about 4.5mA. For a more permanent solution, call Rosemount 
  Analytical customer service at 1-800-433-6076.
  
Rosemount 3144:
- Transferring a configuration from a Rosemount 3144, Device 
  Revision 3, DD Revision 1 from a 275 HART Communicator to AMS 
  Device Manager is not allowed. If your 275 Datapack or Module has that
  revision, AMS will display a message, and the configuration will not 
  appear under the 275 HART Communicator icon in AMS Device 
  Manager. Transferring a 3144P Rev 3, DD Rev 1 configuration from
  AMS Device Manager to the 275 HART Communicator will also be 
  prevented. You must update your DD revision to Rev 2 or higher 
  to allow the transfers.

Rosemount 8712/8732 DD Rev 2 - 
- AMS Device Manager may be busy for up to a minute or may loose
  communication with the device after performing a self test method. 

Rosemount 3095MV Rev. 2
- If the 3095MV Rev. 2 is set to have 4-20mA output represent 
  "Total Flow" and "StdCum" units are selected, you will find the
  calibration management units will display "InH2O" in Test Data 
  Entry of As Found/As Left for (Field Device) calibration. There 
  are two recommended ways to calibrate the 3095MV Rev. 2 device: 

  1. Run Flow Verification using the totalizer.
  2. (more accurate) Run Field Device Calibration on the transmitter
     with the PV set to Gauge (GP), Absolute (AP), or Differential
     (DP). In these cases the test can be run with an intelligent 
     calibrator.

Samson SN3780:
- If you are having trouble seeing Samson SN3780 valves when using 
  a HART modem in AMS Device Manager, try disconnecting and 
  reconnecting, or try a different brand of HART modem.

------------------------------
8. SUPPORTED HART MULTIPLEXERS
------------------------------
The following Hart Multiplexer interfaces in AMS Device Manager 
support these manufacturer/models: 

Manufacturer   Model   Max. Channels  Supports Enhanced Polling   More Info.*
------------   -----   -------------  -------------------------   ----------
ARCOM	       H-Port       32	             Yes 
ELCON	       1700         32               Yes                  See C
ELCON	       2700A        32               Yes		  See C
P+F/ELCON      2700E        NOT SUPPORTED     -			  See D
P+F/ELCON      2700F        32               No                   See E
P+F/ELCON      2700G        32               Yes                  See F
P+F            KFD2-HMM-16  256	             Yes		  See E, G, H
P+F	       KSD2-GW-xxx  Service Bus	     Yes		  See I
MTL	       4841-AMS	    256		     No			  See J, K
MTL	       4841-AMSv7   256		     Yes  		  See J
MTL	       8000/8512    256	             No			  See K
Spectrum       CONNECTS	    256		     No 		  See L

* Issues A and B apply to all multiplexers.

Supported HART multiplexer issues:

A. If AMS Device Manager is configured for a Comtrol RocketPort
   Serial Hub device that is currently unavailable, AMS Device 
   Manager may hang when attempting to access a device connected 
   to a HART modem. As a workaround, remove the multiplexer network 
   from AMS Device Manager (in the Network Configuration utility) 
   and then re-add it when needed again.

B. When you use the Tag Naming Utility to rename the AMS tags for
   HART devices to their corresponding HART tags, descriptors, or
   messages, keep in mind that HART multiplexers are treated as 
   devices in AMS Device Manager and thus will also be renamed.

C. ELCON 1700, 2700A and P+F KFD2-HMM-16 (32-CHANNEL) MULTIPLEXERS:
   - Appear as ARCOM multiplexers.

D. ELCON 2700E MULTIPLEXERS:
   - The 2700E multiplexer is not supported. Contact your local 
     Emerson sales office for upgrade options.

E. ELCON 2700F AND P+F KFD2-HMM-16 MULTIPLEXERS:
   - The Elcon 2700F and P+F KFD2-HMM-16 multiplexers behave 
     differently than the other multiplexers in duplicate device ID
     situations. When duplicate devices are attached to these 
     multiplexers, the duplicate device ID icons are not displayed
     and only one of the duplicate devices will show up in the 
     multiplexer hierarchy. AMS Device Manager cannot determine 
     that multiple devices have the same device ID. However, AMS 
     Device Manager does recognize that the multiplexer thinks it
     has more devices than what it is telling AMS Device Manager 
     in its device list, and AMS Device Manager logs this 
     information in the Windows Event Log.

   - The 2700F multiplexer is shipped with default polling. 
     Customers with 2700F multiplexers who wish to use enhanced 
     polling should contact P+F about upgrading to a 2700G.

F. P+F/ELCON 2700G MULTIPLEXERS:
   - The P+F/Elcon 2700G must be upgraded with firmware version 7 
     or later to work correctly with AMS Device Manager version 7.0
     enhancements. A P+F firmware upgrade utility and firmware file 
     are available on CD2. The firmware upgrade utility must be 
     used with caution; see the PEPPERL&FUCHS\Elcon Firmware 
     Upgrade Utility Considerations readmefirst.txt file on CD2 for
     more information. The most recent version of the firmware 
     upgrade utility and firmware file can be found online by 
     navigating the P+F website: http://www.elconhis.com/.


G. P+F KFD2-HMM-16 MULTIPLEXERS, FIRMWARE VERSIONS 5 - 9:
   - Revisions 5 - 9 of the P+F KFD2-HMM-16 multiplexer are not 
     supported. Contact your local Emerson sales office for upgrade
     options.

H. P+F KFD2-HMM-16 MULTIPLEXERS:
   - The P+F KFD2-HMM-16 should be upgraded with firmware version 
     16 or later to work correctly with AMS Device Manager version
     7.0. The firmware upgrade utility must be used with caution; 
     see the PEPPERL&FUCHS\Elcon Firmware Upgrade Utility 
     Considerations readmefirst.txt file on CD2 for more 
     information. The most recent version of the firmware upgrade 
     utility and firmware file can be found online by navigating
     the P+F website: http://www.elconhis.com/.    

   - By default, AMS Device Manager does not enable enhanced 
     polling on the P+F KFD2-HMM-16 multiplexer. Contact technical
     support personnel at http://www.emersonprocess.com/Systems/
     support/index.asp to enable the enhanced polling feature.

   - Appears as HART Multiplexer 255-way.

I. P+F KSD2-GW-xxx MULTIPLEXERS:
   - By default, AMS Device Manager does not enable enhanced 
     polling on the P+F KSD2-GW-xxx multiplexer is shipped with 
     default polling. Contact technical support personnel at 
     http://www.emersonprocess.com/Systems/support/index.asp to
     enable the enhanced polling feature.

   - Contact technical support personnel at 
     http://www.emersonprocess.com/Systems/support/index.asp for
     information on implications.

   - Appears at HART Multiplexer 255-way.

J. MTL 4841-AMS MULTIPLEXERS:
   - MTL recommends customers with MTL 4841-AMS multiplexers, who 
     wish to use enhanced polling, contact MTL about upgrading to 
     an MTL 4841-AMSv7 multiplexer. You will either have to return
     the MTL 4841-AMS multiplexer to MTL for reprogramming or 
     replace your existing multiplexer with a new MTL 4841-AMSv7.

K. MTL 4841/4842 AND 8000 MULTIPLEXERS:
   - Support only HART Rev. 5, and therefore do not recognize some 
     device types supported by AMS Device Manager. 

L. SPECTRUM CONNECTS MULTIPLEXERS:
   - If you have a Spectrum CONNECTS multiplexer you will need to
     have additional software installed on your PC. Contact 
     Spectrum for details (www.spectumcontrols.com).

   - When identifying new devices or changes to the list of devices
     connected to the Spectrum CONNECTS multiplexer, perform the 
     following procedure:

   1. Add or remove the device from the multiplexer.

   2. Wait 3 minutes for the Spectrum Connects multiplexer to 
      identify the new devices or changes to the list of connected 
      devices.  

   3. Reset the multiplexer from right-click context menu.

   4. Perform a Rebuild Hierarchy operation. The device will appear
      or disappear as appropriate.

--------------------------------------
9. OTHER SUPPORTED HART I/O INTERFACES 
--------------------------------------

The following other I/O interfaces are supported in AMS Device Manager:

Manufacturer   Model   			System Interface		More info.
------------   -----   			---------------------	   	----------
ABB 	       S900    			HART Over PROFIBUS 
ABB    	       S800    			HART Over PROFIBUS     	  	See A 
CEAG 			     		HART Over PROFIBUS
MTL 	       8000 1/1			HART Over PROFIBUS		See C
MTL	       8000 Mark 2 BIM	        MTL				See C
MTL            8000 Mark 2 eBIM	        MTL				See C
P+F	       RPI KSD2-GW-PRO 	        HART Over PROFIBUS 
STAHL 	       I.S. 1 			HART Over PROFIBUS
STAHL	       I.S. 1 (Service Bus)	STAHL				See B
STAHL	       ICS			STAHL				See B
STAHL	       VOS 200			STAHL				See B
STAHL	       I.S. pac 9192		STAHL				See B 
Turck 	       Excom 			HART Over PROFIBUS


Other supported HART I/O interface issues:

A. The ABB S800 is currently in the testing phase. Contact your 
   local Emerson sales office for more information.

B. STAHL MULTIPLEXERS:
   - You may not be able to use AMS Device Manager to communicate 
     with a HART device connected to a STAHL I.S. pac multiplexer
     at the same time a 275 HART Communicator or 375 Field 
     Communicator is connected to that device loop. See your STAHL
     representative for further details.

   - Documentation for the RS-485 DIP switch settings for some
     STAHL multiplexers is incorrect, or does not reflect the
     actual 1-to-1 range for address range listed in AMS Device 
     Manager. These STAHL multiplexers are off by 1 in respect to
     the binary configuration normally encountered (with DIP switch
     1 on STAHL selected, the RS-485 address would be 0 in AMS 
     Device Manager. The binary DIP switch select range goes up 
     sequentially (2=1, 3=2, etc.)

   - Baud rate must be set to 9600; the 19.2K option is not 
     currently supported by STAHL.

   - STAHL multiplexers should only be installed on the STAHL host
     system interface. 

C. MTL 4841/4842 AND 8000 MULTIPLEXERS:
   - Support only HART Rev. 5, and therefore do not recognize 
     some device types supported by AMS Device Manager. 


---------------------------------
10. SUPPORTED HSE LINKING DEVICES
--------------------------------
- Rosemount 3420 Field Interface Module


------------------------------------
11. SUPPORTED DOCUMENTING CALIBRATORS
------------------------------------
- Fluke 702, 743*, 744*
- Druck DPI605, DPI615, MCX 2, Unomat TRX-II
- Rosemount P330, P370, T460, T490
- Beamex MC5*
- Transmation 195, 196, 197
- BETA Calibrators (BetaFlex*, BetaGauge II, and MasterCal 922)
  that support protocol 13 or later.

* The drivers for these calibrators support downloading of switch
  data.

The following calibrators support downloading of test definitions
for fieldbus devices:
- Fluke 743, 744
- Beamex MC5 


---------------------------------
12. CALIBRATION/CALIBRATOR ISSUES
---------------------------------
- Do not configure a calibrator to use COM Port 10. It causes
  the PC to hang. 

- Before using AMS Device Manager calibration management for a 
  device, make sure the device has been scanned at least once so 
  that the necessary information is in the database. If you attempt
  to calibrate a device before it has been scanned, you will get 
  an error message.

- Do not use any single quotes (') in the name of a Test Scheme.

- The calibrator memory is not cleared when overriding a route 
  status to Available, if no calibration test results are in the
  calibrator at the time of the override.

- Non-ASCII characters, such as the following, typically do not
  show up on calibrators:
           (ALT + <0223>)
           (ALT + <0252>)
           (ALT + <0232>)

Rosemount P330 and Druck DPI605 calibrators: 
- Do not use a colon (:) or slash (/) in AMS tag names.

- Errors are not calculated correctly by the calibrator when the 
  transfer relationship of a device is square root. After checking 
  the calibration route into AMS Device Manager, the errors will be
  calculated correctly. 

- When the PC system time is set to GMT+1, local time is displayed 
  instead of GMT+1. This is also the case for Audit Trail, the 
  Calibration History dialog box, the Calibration History report, 
  and the Calibration Status report.

Rosemount T460 and Druck MCXII calibrators:
- Do not use AMS tag names greater than 19 characters.

Rosemount 370 calibrator:
- This calibrator may appear as a Druck DPI 605 calibrator. 

Fluke 743/744 calibrator:
- The calibrator driver does not support manual entry of input on
  test definitions with square root relationships/transfer 
  functions.

-----------------------------------
13. CONTROL SYSTEM INTERFACE ISSUES 
-----------------------------------
All:
- Whenever you make a change to network cables or IP addresses 
  in your control system network, you need to delete and re-add the
  system interface in AMS using the Network Configuration utility
  (Start|Programs|AMS Device Manager|Network Configuration). 

- A maximum of 50 system interface networks can be installed on an
  AMS Device Manager station.

Ovation:
- If you have multiple Ovation networks installed on an AMS Device
  Manager station, you can only enable fieldbus support for one of them.

- AMS Device Manager 7.0 is compatible with Ovation System Software
  level 2.3 and 2.4.  

- Fieldbus gateway supports a maximum of 16 fieldbus devices open
  concurrently in AMS Device Manager.

DeltaV:
- AMS Device Manager 7.0 can be installed on the following DeltaV
  versions 7.3, 7.4, 8.1 and 8.3 workstations:
  Application Station (Server Plus or Client SC)
  ProfessionalPLUS (Server Plus or Client SC)
  Maintenance Station (Server Plus or Client SC)
  Professional Station (Client SC only)
  Remote Professional Station (Client SC only)

- You can use AMS Device Manager 7.0 to access and maintain 
  fieldbus devices connected to DeltaV systems. Prior to enabling 
  fieldbus device support, read Managing fieldbus devices 
  connected to DeltaV systems in Books Online regarding the 
  important considerations for using AMS Device Manager and DeltaV
  together to maintain fieldbus devices.

To enable fieldbus device support for a DeltaV network in AMS 
Device Manager, see "Enable/disable fieldbus device support for a 
DeltaV network" in Books Online. 

- As of AMS Device Manager 7.0, you are required to know the 
  DeltaVAdmin password to your DeltaV system. The DeltaVAdmin 
  password is configured in the Network Configuration utility.

PROFIBUS:
- For the PROFIBUS System Interface to work on Windows 2000 when 
  T+H components are installed on an AMS Device Manager PC, you 
  must either add AmsServiceUser to an Administrator group (see 
  the AMS Suite: Intelligent Device Manager Installation Guide) or
  change the T+H server component to allow full control.

RS3: 
- Using the Autocalibrate function, firmware 5 DVC on an RS3
  system can take significantly longer than the dialog box states.

ALSTOM: 
- The ALSTOM System is no longer supported, as of AMS 6.5.

See the SNAP-ON APPLICATIONS - ISSUES section for AMS ValveLink 
software issues.


-------------------------------
14. SUPPORTED OPERATING SYSTEMS
-------------------------------
AMS Device Manager 7.0 is supported on the following operating 
systems:
- Windows XP Professional, Service Pack 1A*, and Service Pack 2 
 (English version only)
- Windows Server 2003, Standard Edition**
- Windows 2000 Professional, Service Pack 4*
- Windows 2000 Server, Service Pack 4**

- AMS Device Manager is fully supported on an English operating 
  system. AMS Device Manager is tested on a variety of other 
  language operating systems. Minor changes were implemented to 
  support core product functions on Windows XP Traditional Chinese.
  Contact your local Emerson sales office for more details.

*  For Terminal Services, only Remote Administration mode is 
   supported in these operating systems.

** For Terminal Services, both Remote Administration mode and 
   Application mode are supported on these operating systems.


---------------------------
15. OPERATING SYSTEM ISSUES
---------------------------
- Users must be members of either the Power Users or the 
  Administrators user group to run AMS Device Manager.

- If you do not change any of the default security permissions 
  for the Power Users or Administrators groups, users can be 
  members of either one of those groups and can run AMS Device 
  Manager without any problems. If you change the default 
  permissions, your users may have problems using certain AMS 
  Device Manager functions. 

- The "Use simple file sharing" option must be turned off. 

- When operating AMS Device Manager on a PC with Windows XP and 
  Service Pack 2, some changes to Windows Firewall settings may 
  be required. 

See the AMS Suite: Intelligent Device Manager Installation Guide 
for more details on operating system security.


-----------------
16. SUPPORTED PCs
-----------------
Emerson Process Management will attempt to support AMS Device 
Manager on any computer model for which both Microsoft and the 
computer's manufacturer support Windows XP. However, Emerson 
Process Management does not recommend using "Value" or "Economy" 
type computers with AMS Device Manager; we recommend a higher-end
or premier line of computers for best performance.


-------------------------
17. SUPPORTED PERIPHERALS 
-------------------------
- Keithley M1000 RS-232/485 converter
- Westermo MA-44/MA-45 RS-232/485 converter
- ACTiSYS IR2000UL USB to IRDA converter
- Comtrol Device Manager RTS RS-485 to Ethernet converter
- Comtrol RocketPort Serial Hubs (SI 8-port and IA 2-port models)
- Socket SL0703-81 dual serial port I/O PCMCIA expansion card
- MACTek VIATOR HART RS-232 serial modem
- MACTek VIATOR HART USB modem 
- SeaLevel COMM+ 8 expansion board (ISA or PCI bus)


----------------------
18. PERIPHERALS ISSUES
----------------------
- Do not disconnect a USB HART modem while AMS Device Manager is
  running.

- HART Modems are not supported on Ethernet Serial Hubs or 
  Serial Device Servers.

- Do not install more than one HART modem on an AMS Device
  Manager Station.

MACTek VIATOR HART USB Modem:
- Before disconnecting the modem you must unconfigure the COM port, 
  or AMS Device Manager will hang.

Comtrol RocketPort Serial Hubs:
- You must be an administrator to access the multiplexer network
  via a Comtrol RocketPort device.


-------------------------------------
19. INSTALLATION AND UPGRADING ISSUES 
-------------------------------------
- Shut down AMS Device Manager Web Services on the Server
  Plus Station and also on the AMS Device Manager Web Client
  Station prior to installing AMS Device Manager. 

  You can do this by performing the following procedure on 
  the Sever Plus Station and the AMS Device Manager Web 
  Client Station:

  1. Launch Internet Information Services (IIS)
  2. Select Default Web Site in the menu tree.
  3. Click Action | Stop. 
  4. Close IIS.
  5. Upgrade or re-install AMS Device Manager.
  6. Once AMS Device Manager installation is complete, launch IIS.
  7. Select Default Web Site in the menu tree.
  8. Click Action | Start to re-start web services.
  9. Close IIS.

- It is recommended that you run the Verify/Repair database 
  operation before upgrading AMS Device Manager versions. In some
  instances, it may be necessary to run Verify/Repair several times, 
  until there are 0 records recreated, 0 records repaired, and 0 
  records discarded.

- If the required Service Pack for Windows XP is not already 
  installed on your PC, you need to install it before installing
  AMS Device Manager. 

- See the AMS Suite: Intelligent Device Manager Installation Guide
  for Domain Controller security requirements.

- During AMS Device Manager installation, it may take up to several
  minutes after a reboot before a dialog box appears showing the 
  next installation step.

- If you cannot get the license server to work after entering your 
  license codes, verify that your TCP/IP network settings are 
  completely defined and correct. 

- If you receive the message "Unable to connect to server" after
  starting AMS Device Manager, verify that you have correctly 
  installed TCP/IP network support on your system. Contact your
  network administrator for help in setting up your network.

- After upgrading from a previous AMS Device Manager version, 
  perform a Rebuild Hierarchy operation followed by a Scan New 
  operation on all system interface networks.

- You may need to remove an earlier version of AMS Device Manager 
  when upgrading to a new version. See the AMS Suite: Intelligent
  Device Manager Installation Guide for more information.

See the AMS Suite: Intelligent Device Manager Installation Guide,
located in the PDF Documentation folder on AMS Device Manager 7.0 
installation CD1, for installation instructions and installation 
troubleshooting hints.


----------------------------------------------
20. REMOVING (UNINSTALLING) AMS Device Manager
----------------------------------------------
See the AMS Suite: Intelligent Device Manager Installation Guide 
for information on when it is necessary to uninstall AMS Device 
Manager.

UNINSTALL NOTES:
- Make sure you back up your database before uninstalling
  AMS Device Manager.

- SNAP-ON applications must be uninstalled separately, and 
  must be uninstalled before uninstalling AMS Device Manager. 
  Uninstall them by using Add/Remove programs in the Windows 
  Control Panel.

- If you want to uninstall SQL Server also, for AMS Device Manager
  6.0 and higher, uninstall AMS Device Manager first and then SQL 
  Server.

- After uninstalling AMS Device Manager, the \AMS folder will still
  exist, with these remaining files: the AMS Device Manager license
  file (\AMS\Db\License.dat), and database backup files 
  (\AMS\Bin\*.ams_bckup and *.ams_bckup_svn).

- Contact technical support personnel if you have the PC name set 
  to 15 characters or greater and are trying to uninstall AMS 6.0 
  or upgrade to AMS Device Manager 7.0. 


------------------------------------------
21. DATABASE/SQL SERVER
------------------------------------------
- After restoring a database (using the Restore operation), perform
  a Rebuild Hierarchy operation followed by a Scan New operation on 
  all system interface networks.

- You cannot back up your database directly to a network drive. To
  create a backup on a network drive, back up the database to a 
  local drive and then copy the backup file to the network drive. 

- If you stop SQL Server during an AMS Device Manager session, you
  will be warned that this will impact the AMSServerStarter service,
  and the AMS Device Manager Server icon will disappear from the 
  Windows taskbar status area. To get this icon to reappear, 
  restart the AMSServerStarter service from the Windows Control 
  Panel, or reboot the PC. (Restarting SQL Server will not cause
  the icon to reappear.)

- Restoring a database can take extended period of time Due to a 
  documented Microsoft bug (810885), the AMS Device Manager restore
  operation may be delayed by internal SQL Server messages. Because
  there is no wait cursor, it may appear that the operation is 
  locked up, however, the Restore operation will complete after the
  SQL messages cease.


------------------------------------------
22. DISTRIBUTED AMS DEVICE MANAGER SYSTEMS
------------------------------------------
- All PCs must use the same Windows operating system family. 

- Merging of Drawings/Notes from 6.0/6.1 into 7.0: only the 
  computer that becomes the Server Plus Station will have 
  Drawings/Notes. Contact your local sales office for more 
  information.

- If using workgroups rather than a DNS network, PC names must
  be manually added to the host table of each PC in the 
  distributed network.

- When you remove stations from the network, make sure 
  you remove them from the Station Configuration on the AMS Device 
  Manager Server Plus Station.
 (Start|Programs|AMS Device Manager|Station Configuration).

- After adding an AMS Device Manager Station (using Station 
  Configuration), you must shut down and restart AMS Device Manager
  on the Server Plus Station, if AMS Device Manager is running.


-----------------------------------
23. HANDHELD COMMUNICATOR INTERFACE
-----------------------------------
- Possible 275 device configuration transfer issue:
  It is possible to transfer a corrupt device configuration 
  from the 275 HART Communicator containing a data pack 100
  and Module Revision 3.6 (or lower) into the database. This
  corrupt device configuration could then be downloaded to a
  HART device connected to AMS, thus affecting the device's 
  operation. This same corrupt configuration could also be 
  downloaded to a 275 HART Communicator with Module revision 
  4.5 or 4.6 and then be downloaded to a HART device with the
  same potential effects.

- Any AMS Device Manager customer who has all of the following 
  should be concerned:
(1) AMS Device Manager application 
(2) an AMS Device Manager / 275 Interface Kit 
(3) 275 HART Communicator data pack 100 
(4) 275 HART Communicator with Module Revision 4.4
(5) a second 275 HART Communicator with module revision 3.6.
Also, any AMS Device Manager customer who has 1-5 above, and 
(6) a 275 HART Communicator with module revision 4.5 or higher.

The following steps would allow propagation of the problem:

In a 275 HART Communicator with Module Revision 4.4, a 'Full' 
configuration must be saved from a connected field device with an 
affected Device Description. See the table below. This 
configuration must be stored in the data pack 100.  This data 
pack 100 must then be removed and loaded into a 275 HART 
Communicator with module revision 3.6 or lower. This 
configuration must then be edited, and then saved. A computer 
running AMS Device Manager must be connected via the serial link, 
and the same configuration must be uploaded to AMS Device Manager.
This configuration will now be corrupted. If this corrupted 
configuration is then sent from AMS Device Manger to the field 
device, the operation of that field device could be affected. If
this configuration is sent via the serial link from AMS Device 
Manager to a 275 HART Communicator with module revision 4.5 or 
higher, that configuration will still be corrupt. If this corrupted
configuration is then sent from the 275 HART Communicator to the 
field device, the operation of that field device could be affected.

Preventive Action:

Update all 275 HART Communicators to module revision 4.6 or higher.

Do not transfer the data pack 100 with any configurations created 
using a 275 HART Communicator with module revision 4.4 to a 275 
HART Communicator with module revision 3.6 or lower.

Affected Device Descriptions Table
-----------------------------------------------------------------
Manufacturer		Common Name		Model seen on 275
-----------------------------------------------------------------
Rosemount		2088			2088
Rosemount		2090			2090
Rosemount		3051			3051
Rosemount Analytical	54ph/ORP		54pH/ORP
ABB Kent-Taylor		600T			600T
Bopp&Reuther Heinrichs	UST 1			UST 1.0
Endress+Hauser		Cerabar S		CERABAR S
Endress+Hauser		Deltabar S		DELTABAR S
Endress+Hauser		Micropilot		FMR130
Rosemount		Probar			ProBar
Rosemount 		Probar UC		ProBar UC
Drexelbrook		Universal III		UNIV. III
Honeywell		ST3000			ST3000


-----------------------------------
24. AMS DEVICE MANAGER WEB SERVICES
-----------------------------------
AMS Device Manager Web Client Station and Web Services will not
work on a Domain Controller.

See the AMS Suite: Intelligent Device Manager Installation Guide 
for AMS Device Manager Web Services installation and requirements 
information.


--------------------
25. AMS ASSET PORTAL
--------------------
- If the name of an Area, Unit, Equipment Module, or Control Module 
  in the Plant Locations hierarchy in AMS Device Manager contains 
  an apostrophe, AMS Asset Portal will be unable to obtain AMS 
  Device Manager information.

- AMS Asset Portal users need to replace the stylesheets (that 
  display AMS Device Manager data) in
  ../AMSAssetPortal/Data_Source/AMSDataProviderService/StyleSheets

  Style sheets, AMSDataProviderServiceAlerts.xsl, and
  AMSDataProviderServiceEvents.xsl, are installed with the AMS 
  Device Manager product in C:\AMS\Db\xml\Stylesheet. They should 
  be copied from their AMS Device Manager location to the AMS Asset
  Portal location above.

- When upgrading, you must reconfigure your AMS Device Manager 7.0
  data source in AMS Asset Portal Manager. The new Web Services URL
  is: http://<PCname>/amsdevicemanagerws/amsdataproviderservice.asmx. 


---------------------------------------
26. SNAP-ON APPLICATIONS - INSTALLATION
---------------------------------------
You must always install the latest versions of the SNAP-ON
applications (including the AMS ValveLink SNAP-ON application) 
after installing AMS Device Manager. 

SNAP-ON applications can be installed on all station types. 

If you experience problems launching a SNAP-ON application 
after uninstalling and reinstalling it, check your system Path
to make sure all path designations are separated by a semicolon. 
(Note: You do not normally need to uninstall SNAP-ON applications
except when you uninstall or upgrade AMS Device Manager.) 


---------------------------------
27. SNAP-ON APPLICATIONS  ISSUES
---------------------------------

- To launch a SNAP-ON, the Windows user must be configured in AMS
  Device Manager User Manager, and have Device Write privileges. 

MV Engineering Assistant:
- When you perform a drag and drop of a device icon in AMS Device
  Manager, the flow configuration (.mv file) is not included. You 
  need to download or copy the .mv file to the transmitter as a 
  separate step. 

- Engineering Assistant will present an error or crash when 
  encountering device communication failures. 

Plugged Line Diagnostics (PLD):
- When an AMS tag name is changed, PLD will display the old tag
  name instead of the new name until the device is removed from the
  PLD configuration and re-added.

- Contact your Emerson sales office for information on devices that
  support the Liquid Flow application and to receive the Process 
  Applications Best Suited for the Plugged Line Diagnostics SNAP-ON
  application in the AMS Suite: Intelligent Device Manager white 
  paper.

Root Cause Diagnostics (RCD):
- When an AMS tag name is changed, RCD will display the old tag 
  name instead of the new name until the device is removed from
  the RCD configuration and re-added.

FlowScanner
- When security is enabled in FlowScanner, the FlowScanner and 
  AMS Device Manager logins must match. If they do not match, you
  will receive an error message stating there was an invalid user 
  attempt. If this error message occurs, you must perform the 
  following:

  1. Login to AMS Device Manager as "admin" to use the FlowScanner
     SNAP-ON application.

  2. Launch FlowScanner and either disable the FlowScanner security 
     setting or set-up your user logins in FlowScanner to match the
     logins in AMS Device Manager. 

AMS ValveLink SNAP-ON:
- DeltaV System Interface: With AMS Device Manager 7.0, it is 
  recommended that you use the AMS ValveLink SNAP-ON application
  for maintaining both HART and fieldbus FIELDVUE digital valve 
  controllers. (See "Managing fieldbus devices connected to DeltaV
  systems" in Books Online for more information.) the AMS ValveLink
  SNAP-ON application is supported with DeltaV I/O and PROVOX I/O,
  but not with RS3 I/O. AMS ValveLink Performance Diagnostics are
  supported for the DVC6000 but not the DVC5000, on all DeltaV 
  versions that support the AMS ValveLink SNAP-ON application. 
  Advanced Diagnostics are supported for both the DVC5000 and 
  DVC6000 on certain DeltaV versions.

- PROVOX System Interface: Performance Diagnostics are supported 
  for the DVC6000 but not the DVC5000, on all PROVOX versions that 
  support the AMS ValveLink SNAP-ON application. Advanced 
  Diagnostics are supported for both the DVC5000 and DVC6000 on 
  certain PROVOX versions.

- HART Over PROFIBUS System Interface: Performance Diagnostics
  may not be supported for the DVC5000 connected to remote I/O 
  subsystems. Advanced Diagnostics may not be supported for the
  DVC5000 with some remote I/O subsystem versions. Contact T+H for
  a list of remote I/O subsystems supported by the HART Over 
  PROFIBUS System Interface, and for information on which remote
  I/O subsystems support  AMS ValveLink diagnostics.

- FIELDVUE DVC5000 Revision 2 and 3: The temperature units may 
  transfer incorrectly when using the transfer arrows in the 
  Compare dialog box on the Inputs tab.

- The AMS ValveLink SNAP-ON Application is not supported through
  the RS3 System Interface. 

- When you are running ValveLink diagnostics on a DVC5000, AMS 
  ValveLink SNAP-ON must be the only system communicating with 
  the valve. Before running any valve diagnostics, ensure that no
  other AMS Device Manager system, handheld communicator, or other
  HART application is attempting to communicate with the same valve.
  (This may require shutting down other HART-based applications.)

- Data from AMS ValveLink SNAP-ON v 6.0.x can not be imported to 
  AMS Device Manager. First upgrade to ValveLink 7.2 before 
  importing.

- As of AMS 6.0, the AMS ValveLink SNAP-ON Application is launched
  by right-clicking a DVC device icon and selecting "ValveLink".

- Occasionally, on initial launch, the AMS ValveLink SNAP-ON 
  Application window will appear behind the AMS Device Manager 
  window.

- Do not rename an AMS tag while the AMS ValveLink Application
  is running. If you rename an AMS tag while the AMS ValveLink 
  Application is running, Performance Diagnostic alerts will not
  be recorded in AMS Device Manager's Audit Trail and Alert Monitor.
  You must shut down and restart the AMS ValveLink Application after
  renaming an AMS tag or refresh the device list within the AMS 
  ValveLink Application.

See the readme file provided with each SNAP-ON Application for 
additional items.


-------------------------------
28. SELECTED OPEN DISCREPANCIES
-------------------------------

The following list contains some of the more common discrepancies 
seen in AMS Device Manager. Some issues listed may be intermittent.
This is not a complete list. If a workaround is available, it is 
referenced by a W. Foundation Support provides more information 
about these discrepancies.

14830	Rosemount T460 Calibrator will not accept devices with tags
        over 19 characters.

19199	Modems, HART Communicators, and Calibrators cannot be 
        configured beyond a 9 port limitation

19589	Starting up too quickly after exiting AMS Device Manager 
        causes errors

19603	Print preview on Compare Configuration displays one date/time

19624	With certain Windows security settings, licensing error 
        when logging in after every reboot
	
19680	Able to add a Calibrator without choosing a Com Port; 
        calibrator will not communicate.

19977	Configurations are applied using the context menu of 
        Masoneilan SVI Rev-2

19993	Druck P370 calibrator will not work with negative 
        calibration values.

20182	W - AMS Device Manager shows old configuration data from 
        AMS ValveLink SNAP-ON

20230	AMS Device Manager displays the standard DeltaV controller
        icon for Remote I/O Controller

20539	Communication problems when using Comtrol Device Master RTS
        with Black Box ME540A-ST optical converter

20688	Calibration with less test points entered than test scheme 
        allows will fail

20972	DeltaV Remote I/O controller is not clearing the 
        configuration change flag

21206	Renaming a network component requires a Scan New operation

21334	Conventional device serial number greater than 25 
        characters disables Drawings/Notes

21588	Next Calibration Date of 1/1/70 is not allowed, but error 
   	message indicates it should be

21627	Device with unconfigured HART date causes problems with AMS
	Device Manager

21645	PC times must be synchronized to avoid problems clearing 
	fieldbus entry in Alert Monitor

21653	Alert from device on CEAG I/O is not being cleared from 
	Alert Monitor

21654	Tag Search does not work for certain CEAG criteria

21665	Corrupt Windows event viewer file causes problems with AMS
	Device Manager

21705	Test Data Entry -Trip Point & Reset Trip Column - Accepts 
	Invalid Values

21713	Parameter transfer buttons do not appear under certain 
	conditions

21724	Internal AMS Device Manager SQL Server passwords are 
	changeable, but are reset to as-shipped password by Restore
	operation

21738	User Configurations with special characters do not accept
        device parameters

21763	Multiplexer loop numbers are not displayed in numerical 
 	order

21833	W - Communication problems when using HART Rev 3 device 
	with Ovation Analog Input

21850	Comparing a fieldbus device to itself does not work with 
	drag and drop

21858	HART modem set as secondary master will erroneously clear
	config changed bit

21920	Test data entry allows a "Finish at" value to be different
	than Test Scheme value

21972	Rebuild Hierarchy events not being logged until host system
	services installed

22041	AMS Device Manager may fail calibrations that intelligent
	calibrators may pass

22182	Web Services Get Calibration Data method does not return 
	HART tag data

22283	AMS Device Manager 6.x will not completely uninstall if 
	computer name is longer than 14 characters

22319	Certain Network Policies may prevent AMS Device Manager 
	from running

22403	Calibrator usernames longer than 20 characters cannot be 
	used in AMS Device Manager

22422	Disabled users show in technician selection list for route
	check-in

22516	Configuration change may not update tab color when using 
	Terminal Services

22545	Changes made on 275 won't save on left-hand side of compare
	configurations window

22561	Valve Signature (AMS ValveLink) with DVC5000 does not work
	with MTL8000 multiplexer

22563	AMS Device Manager Installation should not warn user on 
        Windows 2003 Server SP1

22574	Device connected to Elcon1700 and in Alert Monitor prevents
	comm w/Handhelds

22613	Generic Export file does not include AMS tag names with 
	leading spaces

22627	Changing Final Assembly Number on HART Rev 3-5 device 
	causes problems

22657	Devices do not show up under MTL8000 after Rebuild Hierarchy

22674	Pepperl + Fuchs 2700F multiplexer does not display 
	duplicate devices

22686	AMS Device Manager cannot access MTL multiplexer 
	configuration when in "MTL mode"

22759	PROFIBUS System Interface does not work on Windows 2000 
	when T+H components installed on AMS Device Manager PC

22773	AMS Device Manager is incompatible with Siemens Milltronics
	DolphinPlus software

22790	Running diagnostics with AMS ValveLink SNAP-ON Application
	via modem limits other PC tasks

22840	Uninstalling Ovation Gateway requires re-installation of 
	AMS Device Manager

22841	Missing license file for Plugged Line Diagnostics SNAP-ON
        Application causes run-time error

22890	Drawings/Notes inoperable when periods in serial # of 
	conventional device

22893	Hot-swapping a Comtrol Serial Hub device while AMS Device 
	Manager is running causes blue screen

22915	Choosing OK to all options in Verify/Repair can sometimes 
	delay cleaning of DB

23178	AMS Device Manager must be reinstalled after uninstalling 
	DeltaV

23252	Drag/drop of fieldbus device onto a fieldbus device in 
	Calibration Route (for the purpose of comparing the two) 
	not allowed

23369	Audit Trail does not contain entries for scanned fieldbus
	blocks which are unchanged

23415	Devices may not appear on 2700F multiplexer; resetting 
	multiplexer resolves the issue

23814	Using blank password with AMSPasswordUtility.exe causes 
        licensing error

23824	Leading spaces on AMS tag names will not be displayed in
        Alert Monitor

23842	ValveLink terminates after right-clicking on Progress 
        dialog box after import from ValveLink







