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

[Imported] Inversion of points and consequent convertion of codes to suit.

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
358

[Imported] Inversion of points and consequent convertion of codes to suit.

>>Message imported from previous forum - Category:Scripts and Tips<<
User: ROVSCADAENGINEER, originally posted: 2019-06-14 00:53:10 Id:448
the help menu "Configure any Physical Binary Input Point Properties" discusses the option of inverting a point state.

I Have noticed that within code referencing point names. if the point name is updated this is then carried to any code that is referencing that point name, animations and logic I have found.

However when referencing state descriptions logic does not update. this needs to be done manually.

When point is inverted on the system would it be obvious to state that all codes referencing that point on the system will also need to have the point inverted in the code.


Accepted Solutions
sbeadle
Janeway Janeway
Janeway
0 Likes
0
357

Re: [Imported] Inversion of points and consequent convertion of codes to suit.

>>Responses imported from previous forum


Reply From User: ROVSCADAENGINEER, posted: 2019-06-14 04:24:39
So I have been using the inverted point now on points that are configured directly to binary points on the RTU's. it doesn't seem to be working correctly? Is there something I am not doing right? I am configuring binary input points. the state just remains as a 0 when I invert it nothing happens.? any support help with this would be great.

 

Reply From User: ROVSCADAENGINEER, posted: 2019-06-14 04:34:17
It is my understanding that you won't see the state change on the SCADA server end as this only changes the output to the inverse at the station.


Reply From User: BevanWeiss, posted: 2019-06-18 11:52:59
This is an eNET Point only option. You will only see the change when you download the configuration to the eNET RTU and the configuration takes affect.
It is really for digital input points when you want to use inverse logic (i.e. when you have an input that is 'Mains Failed', but the actual input is a '1' for 'healthy'). If you tick the box, then the Database Point state is inverted from the Physical state.

See Answer In Context

1 Reply 1
sbeadle
Janeway Janeway
Janeway
0 Likes
0
358

Re: [Imported] Inversion of points and consequent convertion of codes to suit.

>>Responses imported from previous forum


Reply From User: ROVSCADAENGINEER, posted: 2019-06-14 04:24:39
So I have been using the inverted point now on points that are configured directly to binary points on the RTU's. it doesn't seem to be working correctly? Is there something I am not doing right? I am configuring binary input points. the state just remains as a 0 when I invert it nothing happens.? any support help with this would be great.

 

Reply From User: ROVSCADAENGINEER, posted: 2019-06-14 04:34:17
It is my understanding that you won't see the state change on the SCADA server end as this only changes the output to the inverse at the station.


Reply From User: BevanWeiss, posted: 2019-06-18 11:52:59
This is an eNET Point only option. You will only see the change when you download the configuration to the eNET RTU and the configuration takes affect.
It is really for digital input points when you want to use inverse logic (i.e. when you have an input that is 'Mains Failed', but the actual input is a '1' for 'healthy'). If you tick the box, then the Database Point state is inverted from the Physical state.