Connect data sensor from DCIM server (DCE 7.2) to other SCADA server

[anthichi]

As my question, how can i export the sensor data from Data Center Expert 7.2 server (DCIM) to other SCADA server.  I have two Supervisor system, one is DCIM and other with modbus RTU device support , now how could we use other server to supervise the device/ sensor which added into DCIM. I also search some solution like using "Modbus Tcp output module", is there other way to connect ? which is the best ? Thank you.

[APC_Steve · Accepted solution]

Hi @anthichi ,

We don't have a Scada specific option. We do have the modbus TCP output module AP95MODBUS:

https://www.se.com/ww/en/product/AP95MODBUS/struxureware-data-center-expert-modbus-tcp-output-module...

With that, you can output data from up to 247 NetBotz Pods or other devices that DCE is currently monitoring. You would need some kind of 3rd party Modbus TCP to RTU gateway. I know we have none officially supported by StruxureWare Data Center Expert but I can't say what may work for your situation, sorry.

Thanks,

Steve

[anthichi]

Thank for supporting,

I had read that the modbus TCP output module AP95MODBUS only collect the Field device and transfer to DCE but cannot export vice versa, so that we can not collect and export data from devices inside DCE server to other system, is it right ?

p.s: can you send me the userguide of AP95MODBUS module anyway ?

[Shaun]

Hi @anthichi,

This functionality is documented in the user guide, https://schneider-electric.app.box.com/s/uuy2x4fr4wfsvfy2gxkn4qttwqp9vubi

Starting on page 289 - the system calls it "Building Management System Integration".  There's no separate manual for AP95MODBUS, this is just the license to enable this functionality.

To be clear - the DCE can poll data from modbus field devices over modbus-tcp (or via an ethernet gateway that presents the device as modbus-tcp to the DCE) - this functionality is standard and does not require the AP95MODBUS license.  So in this usage, the DCE is acting as a modbus client/master to your monitored devices.

The integration that's enabled by the AP95MODBUS is modbus-tcp output, which allows you to map values from device sensors to modbus registers, so an external system can read them from the DCE via modbus-tcp.  These sensors can be from snmp devices or modbus devices that the DCE monitors, or from virtual sensors created on the DCE (eg, to sum the energy usage of several monitored devices).  So in this usage, the DCE is acting as a modbus server/slave to another modbus master.

The other method to read data from the DCE is using the web services API - this does not require an additional license, but usually requires some custom middleware to make it available to your SCADA system.

[ATrabert]

It may also be worth noting that we do have an application note for how to use/integrate with DCE using the DCE modbus tcp output module

https://www.se.com/us/en/download/document/SPD_JRUK-7R4L9N_EN/ 

Be aware you can only have up to 247 slave addresses, and as far as I know, you can only assign 1 address per devices/virtual sensor.  So in large implementations, you may have to be selective on which devices you output as modbus or have to use another integration method.