AMS 12.0 with MUX MTL 4841 and NPort 6450 from MOXA

Hi all,

When I was as Plantweb Eng. I installed a couple of AMS DM with Comtrol, now I received a call from another FSO about an architecture they are trying to install with an AMS v12.0

They have the transmitters connected to an MTL4841 and the output of this MUX is connected to a NPort 6450 from MOXA, and then connected to DeltaV, but they have a lot of communication problems with AMS DM, is this a valid architecture?

As far as I know the MOXA converter is not approved for the AMS DM, could this be the cause of the communication failures?

Please advise.

frmezano

• 26 Aug 2014 3:31 PM
• Cancel

3 Replies

• Tinh Phan

  

  • 27 Aug 2014 3:52 AM

  You may want to check to see if the HART transmitter connected to the MTL4841 is a HART 5 version protocol.  If it is, there is a release note from AMS that

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

  What model is the MOXA PERIPHERALS?

  • Cancel
• Jonas Berge

  

  • 27 Aug 2014 6:38 AM

  In reply to Tinh Phan:

  Are you able to tell if the communication problem is between AMS-DM and the HART MUX (affecting all devices equally/simultaneously) or is it between the HART MUX and the HART devices (only affecting some devices)? What error messages are you seeing in the software? Could you share a screen capture?

  HART7 devices would be an issue as Thin noted – usually HART7 devices on a HART5 system appear with “generic” access, but it could be a particular MUX does not let the communication pass at all

  Troubleshoot from the ground up, starting with power, then communication, and lastly system integration

  

  Device not powering on

  I suppose you have already checked the basics:

  • LCD display on?
  • Power supply OK
  • System I/O card OK
  • Safety barrier OK if any
  • Shorts
  • Wrong connection
  • Measure voltage at terminals (different for each device) at 20 mA to make sure loop resistance is not excessive or too many devices in series of the loop
  • Measure auxiliary power if any

  Device not found

  • Make sure it is a HART device
  • HART protocol version HART5 or HART7
  • Device address (shall be 0 in 4-20 mA point-to-point topology)
  • Computer port configuration
  • HART master configuration
  • 250 ohm resistor (for transmitters)
  • Measure noise/ripple (ground loop due to moisture,
  • Loose connections
  • HART compatible barrier
  • Signal level
  • Low system AO card impedance

  Displays with generic access

  • HART protocol version HART5 or HART7
  • Missing DD files
  • Missing system files

  Write error

  • Write protection jumper
  • Master conflict

  Cheers,

  Jonas

  • Cancel
• TommyE

  

  • 27 Aug 2014 12:24 PM

  See attached…

   

   

   

  From: frmezano [mailto:bounce-frmezano@community.emerson.com]
  Sent: Tuesday, August 26, 2014 10:32 AM
  To: AO@community.emerson.com
  Subject: [EE365 Asset Optimization Track] AMS 12.0 with MUX MTL 4841 and NPort 6450 from MOXA

   

  Hi all,

  When I was as Plantweb Eng. I installed a couple of AMS DM with Comtrol, now I received a call from another FSO about an architecture they are trying to install with an AMS v12.0

  They have the transmitters connected to an MTL4841 and the output of this MUX is connected to a NPort 6450 from MOXA, and then connected to DeltaV, but they have a lot of communication problems with AMS DM, is this a valid architecture?

  As far as I know the MOXA converter is not approved for the AMS DM, could this be the cause of the communication failures?

  Please advise.

  

  AMS and Moxa.pdf

  

  nport_ia-51505250.pdf

  Tommy Elkins

  John H. Carter Co., Inc.

   

  • Cancel