[Imported] Scadapack 535 E RTU- Workbench v6.5 Software - Add I/O Device


[Imported] Scadapack 535 E RTU- Workbench v6.5 Software - Add I/O Device

>>Message imported from previous forum - Category:SCADAPack RTU<<
User: mchartrand, originally posted: 2018-10-18 19:39:31 Id:134
This is a re-posting from the obsoleted (October 2018) "Schneider Electric Telemetry & SCADA" forum.


I am currently working on a water infrastructure project in which Scadapack 535E RTU is used to poll PLC at regular internals via modbus TCP/IP and sends this data to SCADA(ClearSCADA) via DNP3.
Scadapack 535E RTU is assigned as Modbus Client and PLC as Modbus Server for Modbus TCP/IP comms. We are using E-configurator to set up basic configurations and Workbench to create IEC61131-3 Application. We are not using any of the physical I/O in the RTU.
I am stuck up with some basic questions while programming:
1. How do I map MODBUS register(16 bit) to RTU derived points in scadapack Workbench software? I have added MTCP_INT_READ and MTCP_INT_WRITE devices in the workbench resource to access Modbus registers.
2. Is it possible to read 16 bit MODBUS register and map individual bit to RTU derived points?
3. Do I need to add DNP points in point database of E-Configurator?
4. Once mapping (Modbus-DNP3 points) is done in RTU, how do I make these points available to SCADA?
Note that we are not using the modbus scanner feature in E-configurator. Hence all mapping should be done in Scadapack Workbench itself. Many thanks in advance._**


Is there a particular reason that you're not using the Modbus Scanner functionality?
It would be the ideal way to perform this functionality.

If you're not using the Modbus Scanner functionality, then you would want to configure IO Boards / IO Devices within ISaGRAF / SCADAPack Workbench.

If you want to address the bits individually, then you shouldn't be using the MTCP_INT_READ/WRITE IO Devices, but should instead be using the MTCP_BOOL_READ/WRITE devices. Then you just specify the right Input Register / Holding Register location as the address.

If you want these then exposed as DNP3 points for SCADA you would need to create these DNP3 points in E-configurator, and then create the appropriate IO devices for the RTU points in SCADAPack Workbench (and assign them the appropriate values from your Modbus variables).
This is what makes the Modbus Scanner the simpler approach... you can just configure the Modbus Scanner for the range of points needed, and it handles all the rest.


Thanks for your detailed reply.I was initially under the impression that individual bits packed in 16 bit registers cannot be mapped to DNP3 binary points in Point database of the RTU when using modbus scanner feature in e-configurator.
I at last mapped modbus registers as binary points in RTU directly using modbus point scanners in e-configurator. Yeah, it is much more simpler than using IO Devices, adding variables, mapping them and again wiring the variables to IO Devices. But I did all these steps before realizing that E-Config can manage all these in single step. sigh._**