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
84604members
353879posts

Invalid Alarm for IEC 60870-5 104 Analog Input Point

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.

arichardsen
Crewman
Crewman
0 Likes
1
507

Invalid Alarm for IEC 60870-5 104 Analog Input Point

Hi,

 

I'm currently configuring som Analog Input points using the IEC 60870-5 protocol. From the Alarm limits setup it's possible to set severity and description for the "Invalid" state, however no matter what I set I can't get the alarm to appear in the alarm banner.

Point quality is changing when I'm enabling the InValid flag in the 104 protocol simulator, but no alarm appears.

 

Simulator is FreyrSCADA-IEC-60870-5-104-Server and I'm running Geo SCADA Expert 2019 July 2020 Update


Any idea on what I'm doing wrong?

Thanks in advance

1 Reply 1
BevanWeiss
Spock
Spock
0 Likes
0
478

Re: Invalid Alarm for IEC 60870-5 104 Analog Input Point

I'm likely to be a bit in the dark on this, since I don't really use 60870-5-104 at all.

 

If you're confident that the 'outstation' is indeed generating an appropriate Invalid state indication for this analog input, then you could enable the IO logging, and get the log of the raw data coming in.

Then you could run that back through the drivers log translator.

If you run the driver executable and pass in /translate:{log file} on the command line then it will normally spit out some HTML files which are reasonably digestible [if it doesn't work first time, then I might have goof'd the syntax, and /? should help]

 

You'd ideally want to find some indication in that of the outstation sending in the Invalid state.  Based on that you could probably raise a support ticket with your local Tech Support.

 

It's possible that there is a bug in Geo SCADA, or it's possibly a miss-configuration.. or even just that this is the expected behaviour and Invalid states mean different than what we would normally expect (I believe this has been the situation for me recently with a DNP3 Analog Point... so it's possibly the same situation with the 60870-5 points)


Lead Control Systems Engineer for Alliance Automation (VIC).
All opinions are my own and do not represent the opinions or policies of my employer, or of my cat..