Hello,
I have a valve setup in the field on Analog Output Hart Card.
I am getting intermittently ( approx every 15 minutes Not Communicating With Device) warning alarms, but the valve is still working (off the 4-20mA signal) and controlling.
1. From the HART Statistics screenshot, what does Timeout Errors mean?
2. Does the Not Communicating with Device warning mean I am losing the HART communication with the Device?
This is the 2nd AO card I placed the valve on and the same issue. The previous AO card was giving me I/O failure and the 4-20mA was loss so the valve will go to fail state. This also was intermittently. To get valve working again, we reset the power to valve.
Also, I am unable to connect to device with AMS
Any ideas what could be causing this issue? Thank you
In reply to Kris Chandrashekar:
In reply to Rens :
In reply to Jonas Berge:
Hello Jonas thanks for the reply here are the message from our delta V friend, Looks like all these devices (Panametrics XMT868) appearing in AMS as one (FIT59114-02). I didn’t check all of them but several random ones were the same. Also when you open device list by device type and module there is only one flow meter in it. When you try to open it in AMS for configuration sometimes different flow meters is opened (you can see it by configured tag inside the device). In DeltaV everything is fine. When I try to run Auto-sense HART Device it shows correct flow meter for each channel (CHARM). Also HART communication statistics and devices status in DeltaV Diagnostics shows that there are no issues. I mentioned that “Device ID” inside flow meter configuration is 0 for device I was able to communicate with from AMS. we did random check in the field with HART communicator and confirm that all of checked flow meters have “Device ID” = 0. As for me it doesn’t look right.
That is very good check and your feeling is right. It is not Right. You caught the root cause of your problem. HART device ID need to be unique and can't be 0 per HART specification. You need to contact the Vendor to request them to change each one of these devices.
Devices with id of 0, there are unwanted issues you will run into such as what you are seeing.
You will see this issue in a AMS type of application because it needs something to differentiate these devices.
DeltaV is OK through CHARM is because it is individual charm is communicating with each device with one HARTmodem to each device.