MODBUS tag

[DCIM_Support]

Hi, it is posible to show a name, tag or another information to identify a  MODBUS device in alarms or reports and not only IP adress

(CID:126165000)

[DCIM_Support]

Hi Sergio,

You can create custom properties for devices. These can be seen and used as columns in the different views and can also be configured in reports. As for alarms, you can use the short e-mail message and use any custom text you'd like (there are no macros at this time to include custom properties). You might have to create a custom alarm action for each individual modbus device though to add that property.

Thanks,

Steve

(CID:126165015)

[DCIM_Support]

ok, i agree, but we have a lot MODBUS device ☹️, did you know if there is a plan to implement this function in the future?

(CID:126165038)

[DCIM_Support]

Hi Sergio,

To start with, many devices don't have labels that we can automatically pull via Modbus. A custom property in that event would be the only way and would have to be manual. After thinking about it, maybe being able to add a label during discovery (you have to add them individually anyway) would resolve both of these issues.

I totally understand and I agree that customers with many modbus devices have to do a lot of work to get this type of configuration. I know of no current plans for this but I can add this as an enhancement request.

Just an FYI, adding a request doesn't mean the enhancement will actually make it into the product.

Steve.

(CID:126165050)

[DCIM_Support]

perfect, i appreciate that, thanks for your help.

(CID:126165078)

[DCIM_Support]

Hi Sergio,

And if instead of the "MODBUS" tag to identify TCP/IP Modbus devices use the tag "Slave", which is present in the name of any TCP/IP Modbus device in DCE (usually)?

With respect.

(CID:126165267)

[DCIM_Support]

Hi, Spezialist, that can work, how can i do that?

(CID:126165600)

[DCIM_Support]

Did not quite understand your question. I'll try to answer.

For example, in my DCE-server all TCP/IP Modbus devices have a name, for example:

"192.168.1.45 - Slave 1"
"192.168.1.45 - Slave 2"
"192.168.1.45 - Slave 3"

"192.168.1.55 - Slave 1"
"192.168.1.55 - Slave 2"
etc.

With respect.

(CID:126165605)

[DCIM_Support]

ok, but in my case , only one MODBUS device is conected by IP number, all are "Slave 1" . It is difficult for users identify a specific device whit this information.

(CID:126165616)

[DCIM_Support]

Hi Sergio,

I understand you.

Well, if it's not difficult for you, you can show a screenshot from the Device View of your DCE-server with real examples of TCP/IP Modbus device names. Maybe I can help...

With respect.

(CID:126165657)

[DCIM_Support]

sure...

(CID:126165663)

[DCIM_Support]

Hi Sergio,

Ok, i.e. you see in the screenshot what I expected to see and wrote about: any TCP/IP Modbus device (Power meter or Generator) has an "IP-address - Slave number" Label. Then back to your original question:

Hi, it is posible to show a name, tag or another information to identify a  MODBUS device in alarms or reports and not only IP adress

That is, any TCP/IP Modbus device can be uniquely identified by its Label, which is displayed in all alarms, reports, etc. Yes, I understand that this is not very informative, but such are the limitations of all Modbus devices.

Then my question is: for an example of your screenshot, for example, any Power meter or Generator how would you like to identify a TCP/IP Modbus device? How do you think this should be?

With respect.

(CID:126165681)

[DCIM_Support]

we need a name tan can identify the device like "Generador Agencia San Jose",all equipment is installed in remote locations, and the the technicians will only recive email notifications on te road, like the SNMP devices, i think

(CID:126165683)

[DCIM_Support]

Hi Sergio,

I completely understand you -- this topic has already been discussed here on HELP CENTER EcoStruxure IT.

Therefore, here is my tip/lifehack 😀: as a rule, you probably use standard HTML-based E-mails in your DCE-server Alarm Actions settings. During each generation of a new alarm (but not Return To Normal state), the table in the E-mail contains information about the "Notification Policy". Therefore, I propose for each of your TCP/IP Modbus devices (or groups of devices, if they are geographically located in one place) to create a separate "Notification Policy" with a name that accurately identifies the geographical location of this device or group of devices:

Thus, your service personnel who receive only alarm E-mails from DCE-server will know exactly the location of the equipment, i.e. then what you need 😀.

I realize, that this can be time-consuming if you have a huge number of TCP/IP Modbus devices. But this is a real solution to the existing problem for you. Since using Custom Property for devices does not solve your problem, for example, the custom property value "Nombre" from you screenshot still does not appear in alarm E-mails (even when using macros).

With respect.

P.S.: I think you will also be interested in my topic , and for me -- the answer to my question 😉.

(CID:126169287)

[DCIM_Support]

Hi, thanks Spezialist and Steven.

we will try both options,

but I think there is a lack of MODBUS device functions that should be improved.

 Anyway, I thank you for your time and dedication 😀.

(CID:126166196)

[DCIM_Support]

If you have any questions, please ask.

I was glad to help 😀.

(CID:126166735)

[DCIM_Support]

This question is closed for comments. You're welcome to start a new topic if you have further comments on this issue.