Welcome to the new Schneider Electric Community

It's your place to connect with experts and peers, get continuous support, and share knowledge.

  • Explore the new navigation for even easier access to your community.
  • Bookmark and use our new, easy-to-remember address (community.se.com).
  • Get ready for more content and an improved experience.

Contact SchneiderCommunity.Support@se.com if you have any questions.

Close
Invite a Co-worker
Send a co-worker an invite to the Exchange portal.Just enter their email address and we’ll connect them to register. After joining, they will belong to the same company.
Send Invite Cancel
84589members
353857posts

Questions about MODBUS TCP Output Module

EcoStruxure IT forum

A support forum for Data Center Operation, Data Center Expert, and EcoStruxure IT product users to share knowledge on installation, configuration, and general product use.

DCIM_Support
Picard
Picard
0 Likes
16
967

Questions about MODBUS TCP Output Module

This question was originally posted on DCIM Support by Yang Gao on 2017-08-15


I understand that MODBUS TCP Output Module is a optional add-on and must be purchased prior to use. Before purchasing it, I have a few question about it.

If I understand correctly, DCE MODBUS TCP Output Module is acting as network gateway for third party network management system. For third party network management system to query DCE devices, NMS communicates with DCE with MODBUS protocol and given device's slave ID. I understand one device must have unique slave ID. The question is: can multiple devices (same type of devices) use one same slave ID?

The reason for the questions is that we have about 200 APC rack-mounted ATSs. We don't want the third NMS to poll each device and report each device's alarm and status. We want the third party NMS to poll DCE which gives one aggregated alarm and status of all ATS devices. In another words, all ATS devices act as one  combined ATS device from the third part NMS point of view.

(CID:123348192)

16 Replies 16
DCIM_Support
Picard
Picard
0 Likes
11
967

Re: Questions about MODBUS TCP Output Module

This answer was originally posted on DCIM Support by Steven Marchetti on 2017-08-15


Hi Yang,

The Modbus output module in DCE is as you know a software module. It does however act similarly to a hardware gateway. Every device you have wired to a gateway would have it's own slave address. In this case, up to 247 slave outputs. The only way DCE can output a series of devices as a single slave ID is if the devices themselves are being monitored by DCE as a single device.

 

Thanks,

Steve

(CID:123348207)

DCIM_Support
Picard
Picard
0 Likes
0
967

Re: Questions about MODBUS TCP Output Module

This comment was originally posted on DCIM Support by Yang Gao on 2017-08-15


How can DCE monitor a series of devices as a single device?

(CID:123348215)

DCIM_Support
Picard
Picard
0 Likes
0
967

Re: Questions about MODBUS TCP Output Module

This comment was originally posted on DCIM Support by Steven Marchetti on 2017-08-15


That's up to the devices themselves. DCE can monitor SNMP. If all devices roll up under the same network card for SNMP, DCE sees them as a single device.

DCE can monitor Modbus (but then you may not need the output module). As is the case above, if the main unit can have other devices roll up underneath and show DCE a single slave, DCE outputs a single slave.

Totally at the mercy of the device there.

(CID:123348218)

DCIM_Support
Picard
Picard
0 Likes
0
967

Re: Questions about MODBUS TCP Output Module

This comment was originally posted on DCIM Support by Yang Gao on 2017-08-15


Each APC ATS is a SNMP device with its network card. They can not be roll up under the same network card.

 

Can DCE output module defines a device group (with 200 ATS units under it) as one slave?

(CID:123348220)

DCIM_Support
Picard
Picard
0 Likes
0
967

Re: Questions about MODBUS TCP Output Module

This comment was originally posted on DCIM Support by Steven Marchetti on 2017-08-15


No,

As I stated previously:

It does however act similarly to a hardware gateway. Every device you have wired to a gateway would have it's own slave address.


DCE acts like this. Every device has it's own slave address. 

Modbus output for SNMP or Modbus in.

Each monitored node is a single output slave address.


The only difference is NetBotz. To make it worse, if you're using NetBotz, each pod is a slave address. That''s fine if you're looking at the bot directly but DCE also breaks the NetBotz up into pods. 

 

1 SNMP IP monitored =  1 modbus slave output

1 Modbus slave monitored = 1 modbus slave output

1 NetBots device monitored = 1 slave address per pod.

 

(CID:123348223)

DCIM_Support
Picard
Picard
0 Likes
0
967

Re: Questions about MODBUS TCP Output Module

This comment was originally posted on DCIM Support by Yang Gao on 2017-08-16


How many concurrent TCP/IP connections are supported by DCE between DCE and 3rd party NMS?

(CID:123348628)

DCIM_Support
Picard
Picard
0 Likes
0
967

Re: Questions about MODBUS TCP Output Module

This comment was originally posted on DCIM Support by Steven Marchetti on 2017-08-16


Hi Yang,

As per my initial comments:

...up to 247 slave outputs


Steve

(CID:123348660)

DCIM_Support
Picard
Picard
0 Likes
0
967

Re: Questions about MODBUS TCP Output Module

This comment was originally posted on DCIM Support by Yang Gao on 2017-08-18


Steve, my last question was about concurrent network connections. 1 network connection not = 1 slave device.

Do you think 3rd party NMS can establish 247 concurrent network connections with DCE?

(CID:123349831)

DCIM_Support
Picard
Picard
0 Likes
0
967

Re: Questions about MODBUS TCP Output Module

This comment was originally posted on DCIM Support by Steven Marchetti on 2017-08-18


Hi Yang,

 

Sorry I misunderstood.

There are no tested limits to the number of network connections to the server. It's all about resources. If you're trying to pull a single register from 100 devices or 100 registers from a single device, the OS will use about the same amount of resources. If you have 100 different modbus systems polling DCE, that may add more overhead to the network and system. The limit to the number of connections or polls of devices is mostly environmental   and will differ from system to system. System resources, number of devices, number of registers, etc are different on every install.


Steve

(CID:123349837)

DCIM_Support
Picard
Picard
0 Likes
0
967

Re: Questions about MODBUS TCP Output Module

This comment was originally posted on DCIM Support by Yang Gao on 2017-08-30


Steve,

Back to your comments below:

"The Modbus output module in DCE is as you know a software module. It does however act similarly to a hardware gateway. Every device you have wired to a gateway would have it's own slave address. In this case, up to 247 slave outputs. The only way DCE can output a series of devices as a single slave ID is if the devices themselves are being monitored by DCE as a single device"

Is it possible that we request a customized DCE feature which creates a virtual device (representing a number of physical devices) and output the virtual device as a slave ID to 3rd party over the MODBUS output module?

 

 

(CID:124520922)

DCIM_Support
Picard
Picard
0 Likes
0
967

Re: Questions about MODBUS TCP Output Module

This comment was originally posted on DCIM Support by Steven Marchetti on 2017-08-30


Hi Yang,

 

Such a request is not necessary. You can create virtual sensors using either averages (for temperature etc) or totals for other numeric values for APC and/or 3rd party sensors such as watts shown here:

Choose the different sensors (make sure if you're adding sensors, you don't add each outlet in a PDU and then the total for that PDU. 

You then name it and choose a folder to put the sensor in. You'll have it listed in the folder itself as well as under virtual sensors

You can then assign it a slave address and associate values with registers (only 1 sensor in a virtual sensor)

As noted previously, please remember there are only 247 potential slave outputs.

 

Steve

(CID:124520983)

DCIM_Support
Picard
Picard
0 Likes
0
967

Re: Questions about MODBUS TCP Output Module

This comment was originally posted on DCIM Support by Yang Gao on 2017-08-30


The virtual sensor is for sensors with numeric values.

In our case, we want to monitor ATS states which are not numeric values as below

DCE may solve our problem if the virtual sensor can do logic operation on non numeric values.

 

(CID:124521014)

DCIM_Support
Picard
Picard
0 Likes
2
967

Re: Questions about MODBUS TCP Output Module

This answer was originally posted on DCIM Support by Steven Marchetti on 2017-08-30


Hi Yang,

 

You're correct, there is no option for a virtual sensor/device for state or to use multiple device sensors on a virtual sensor. I do not believe this is something they're looking into as they're likely looking to increase the number of output slave IDs first which would potentially cause less need for such a virtual device. IN any case, there is an option in the menu atop the EcoStruxure IT Help Center page under "resources" I believe where you can enter an enhancement request in your own words. Perhaps it's better that way so you can specify what you're looking for. Please note that such a request doesn't mean that the feature will make it into the product.


Steve

(CID:124521020)

DCIM_Support
Picard
Picard
0 Likes
0
967

Re: Questions about MODBUS TCP Output Module

This comment was originally posted on DCIM Support by Yang Gao on 2017-08-30


Steve,

Is there a Schneider group or person whom we can contact and set up a meeting to discuss the requirement, implementation and cost share, etc? A group of people in my company are interested in such as features and would like to  discuss with Schneider.

In your example, if you create more than one virtual sensors, can you add all virtual sensors into one slave address?

(CID:124521034)

DCIM_Support
Picard
Picard
0 Likes
0
967

Re: Questions about MODBUS TCP Output Module

This comment was originally posted on DCIM Support by Steven Marchetti on 2017-08-30


Hi Yang,

 

I would suggest calling your local Schneider tech support or sales group as they would have a better idea on cost. Your local tech support can assist on technical issues.

As for the specific question on virtual sensors, each virtual sensor is it's own slave ID as I noted previously and they can not be combined.


Steve

(CID:124521042)

DCIM_Support
Picard
Picard
0 Likes
0
967

🔒 Closed

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