EN2PB-R Profibus Node Diagnostics
My understanding about the Profibus Protocol is there is Diagnostic Information that should be part of each Nodes transmission? It doesn't appear the the Gateway (or Configuration Manager SW?) maps this info into the PLC Data Type. Is there a newer version of the Configuration Manager that might do this? (I have V1.0.1.10)
-
Hi Howard,
That does not appear to be latest firmware. The latest firmware is 1.4.03.
It can be downloaded from the HMS-EN2PB-R Product Page.
There was a bug fix regarding the diagnostic data in 1.2.1.0, but I'm not sure this data gets automatically mapped to the Input data (if that is where you are looking for it).
Please try the update and let me know what you find. If you continue to have problems, I can look into this further. In your response, please include the GSD file for the node in question.
Best Regards,
Kyle
0 -
So is the Firmware the Hardware Firmware version.... and is the "Configuration Manager" part of the "Firmware"?
0 -
Can you provide the serial number so I can check which version of firmware it shipped with?
There are update instructions in the PDF included in the firmware file. The firmware is the hardware firmware version, not part of the configuration manager.
0 -
I am remote so I can't access the equipment... It is pretty old (2018?)
0 -
Do you have someone on site that can connect to the USB port? The firmware update requires the USB connection.
0 -
I do not... I'll be onsite Probably next Wed. and provided I can access the equipment I could get that info.
In the Mean time getting back to What I want...
In the Mass Flow Controller (I sent the GSD file via e-mail)... per the Manual:There should be two Diagnostic Bytes as part of the DPV0 Cyclical data exchange
Is this info ignored by the EN2PB? If not, where will it end up (or how do I access it)
0 -
Hi Howard,
I did not receive the GSD file. Can you attach it to your response? If for some reason you don't want it to be public, you can create a support ticket here.
I imagine that these two bytes just need to be mapped to Input data. We should be able to figure it out with the GSD file.
0 -
How do you attach files?
0 -
sent via a ticket
0 -
I got it. I will probably have to get back to you on Monday. Taking a quick look at it, this is all I see that can be mapped:
0 -
Can you send the devices documentation where you got that info?
0 -
sent under the Ticket
0 -
Do you have DPV1 activated under the Object Properties?
0 -
Also make sure all the alarms are enabled under parameter assignment:
0 -
This video has some information about reading the Diagnostics: https://youtu.be/it8e3Sd5yJA
0 -
I did try to "enable Alarms" in the parameters, and also checked the DPV1 box....
But that check box doesn't Un-Gray any of the other items on that Tab:
And doesn't result in any additional "mapping" in the Module Defined Tags....
0 -
Any Thoughts?
0 -
I'm not sure why it won't let you enable the alarms. I will escalate the case to the Anybus engineers and see if they can figure out why.
0 -
Hi Howard,
You will need to contact the supplier or manufacturer of the device. If the diagnostics are part of the cyclic data, they need to provide a correct GSD file that allows you to select a module with that data. The device has a specific module for each specific cyclic I/O data, and it seems like there is no module for the cyclic diagnostics.
0 -
So there is this "CIP" section in the HMS users manual:
Can this be used to get the Diag Data via a Msg Instruction?
Not clear on how this would be set up....
Below is My stab at it:0 -
Hi Howard,
I found another case where another customer spent a lot of time trying to get this work but was unsuccessful.
Essentially, this is what they found:
> The Anybus Gateway was an HMS-EN2PB-R, the PLC was a ControlLogix with 1756-L71 (FW 30.014) processor and ENBT (FW 6.006) Ethernet IP Module and the Profibus Slave was an ABB Aztech 600 Fluoride Analyser.
> Reading cyclic data from the connected Profibus node worked fine. But the problem was reading/writing acyclic data (Class 2) from the Profibus node.
> We tried every feasible combination of values in a CIP message –
> Specifically, we couldn’t get this message to work –
But some of the other commands did work. We then using a Profitrace (Profibus DPv1 Master) to look at the Profibus messages-
1. Successfully established PROFIBUS DPV1 communication with the ABB Analyser using our PROFITRACE.
2. Initiated DPV1 messages from the HMS-EN2PB-R linking device using the Get_Atrribute_Single function.
However, we've encountered a slight discrepancy in the default Send_Timeout settings. The HMS linking device has a default Send_Timeout of 1000 ms, while the PROFITRACE is set to 5000 ms.The ABB analyser prefers a Send_Timeout of 6960 ms, closer to our PROFITRACE setting. Due to the discrepancy with the HMS linking device's Send_Timeout, the ABB analyser aborts the communication.
> TLDR - Essentially, it timeouts and the connection is closed.
> We would like to try to increase the timeout on the HMS-EN2PB-R, but it was getting a bit too complicated, so we gave up. We tried with a timeout of 5000ms on our USB->Profibus to poll the Slave, and that worked.
0
Please sign in to leave a comment.
Comments
21 comments