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.

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

[Imported] Data Logging control with limited point usage

EcoStruxure Geo SCADA Expert Forum

Find out how SCADA systems and networks, like EcoStruxure Geo SCADA Expert, help industrial organizations maintaining efficiency, processing data for smarter decision making with IoT, RTU and PLC devices.

Janeway Janeway

[Imported] Data Logging control with limited point usage

>>Message imported from previous forum - Category:Scripts and Tips<<
User: mchartrand, originally posted: 2018-10-23 15:28:56 Id:170
This is a re-posting from the obsoleted (October 2018) "Schneider Electric Telemetry & SCADA" forum.


Ok forgive me if this is a rookie question, but here goes.
Internally on the controller I have a Data Log array that logs all valve positions any time one of them opens or closes. We are forced to keep 300 lines at 16 points per line. Over 150+ wells this is a significant number of points. The option I am exploring is the ability to pull only the top 5-10 lines of the array for each well, and do a compair by date and time. Any new lines would then be stored in a log on ClearSCADA. We cant just instigate the log solely on ClearSCADA because if coms are lost we could potentially miss an instance.
Im hoping someone has an example they wouldnt mind me looking at that could help clarify how to go about scripting this or can point me to an existing thread that I have missed.
Thanks for your help, Rick_**


A slightly different way of doing it, which would handle temporary loss of comms between ClearSCADA and the ontroller, would be to use DNP3 with event logs.

This will store the timestamped data, and keep it until ClearSCADA has confirmed that it has received it. There are a few DNP3 setting that will need to be checked for this to work correctly.

You could optionally also pack the bits into a 16 or 32 bit word, which will make converting it back to a log on the ClearSCADA side a bit easier.


The only issue I can see with that, is that currently Im pulling it into a "non-Configurable" spreadsheet format for reporting purposes. The events log, as far as I understand, can be sorted and trimmed to only show specific transactions.
I know its possible to set up a specific Query against those events, but can I use these same settings you are talking about when coming from an AB controller? Im not really sure how to go about setting up the Controller side of it for this._**


I found the following when I googled ClearSCADA and DLog which is what they are on a Scadapack 3xx.