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
84248members
353348posts

[Imported] Point Configurations

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.

Solved
sbeadle
Janeway Janeway
Janeway
0 Likes
1
424

[Imported] Point Configurations

>>Message imported from previous forum - Category:ClearSCADA Software<<
User: ROVSCADAENGINEER, originally posted: 2019-04-17 23:13:04 Id:410
I am wanting to see the point configuration for several datapoints on the server. One being that the alarm severity is set to 1000 being critical across several points. Yet I can only seem to raise this column on the CDBCONFIGCHANGES in the columns of FieldName. If I run a query on the history I can see the old and new value. I am just wanting to see the current configuration of each point. I know you can be crafty with this by using join function etc. However is there a way I can just query the current configuration of a large set of points?


Accepted Solutions
sbeadle
Janeway Janeway
Janeway
0 Likes
0
423

Re: [Imported] Point Configurations

>>Responses imported from previous forum


Reply From User: dmercer, posted: 2019-04-17 23:25:42
If you're trying to do this with points for different types, you would look in the schema for a common type that they all inherit from that includes the fields that you want. Eg. for any simple digital point you can use CPointDigital. I can't tell you what your WHERE clause should be since I don't know how your database is set up, but I imagine that you want to do something like this:

`SELECT FullName, State0Severity, State0SeverityType, State1Severity, State1SeverityType
FROM CPointDigital
WHERE FullName LIKE '%Something%'`

 


Reply From User: ROVSCADAENGINEER, posted: 2019-04-18 00:11:52
Your a saviour dean. Thanks!


Reply From User: adamwoodland, posted: 2019-04-28 22:26:13
Also note that if you can't find a common parent table, you can also use UNION to merge tables. There are a couple of ways to do this, i.e.

SELECT [Columns] FROM Table1 UNION Table2

In which case columns need to exist in both tables, or the more flexible but more cumbersome:

(SELECT [Columns] FROM Table1) UNION (SELECT [Columns] FROM Table2)

The number of columns need to match, and the data type for the column also needs to match, but you can also just specify '' or 0 to 'fill the gap'

See Answer In Context

1 Reply 1
sbeadle
Janeway Janeway
Janeway
0 Likes
0
424

Re: [Imported] Point Configurations

>>Responses imported from previous forum


Reply From User: dmercer, posted: 2019-04-17 23:25:42
If you're trying to do this with points for different types, you would look in the schema for a common type that they all inherit from that includes the fields that you want. Eg. for any simple digital point you can use CPointDigital. I can't tell you what your WHERE clause should be since I don't know how your database is set up, but I imagine that you want to do something like this:

`SELECT FullName, State0Severity, State0SeverityType, State1Severity, State1SeverityType
FROM CPointDigital
WHERE FullName LIKE '%Something%'`

 


Reply From User: ROVSCADAENGINEER, posted: 2019-04-18 00:11:52
Your a saviour dean. Thanks!


Reply From User: adamwoodland, posted: 2019-04-28 22:26:13
Also note that if you can't find a common parent table, you can also use UNION to merge tables. There are a couple of ways to do this, i.e.

SELECT [Columns] FROM Table1 UNION Table2

In which case columns need to exist in both tables, or the more flexible but more cumbersome:

(SELECT [Columns] FROM Table1) UNION (SELECT [Columns] FROM Table2)

The number of columns need to match, and the data type for the column also needs to match, but you can also just specify '' or 0 to 'fill the gap'