more quick actions
minimize quick actions
Data Acquisition
4
Posts
2
Users
0
Likes
22
Views
Topic starter
Hello,
Do you know if by default a general interrogation is sent when a sector is activated in the IEC 60870-104 driver?
My customer has configured his sector like this:
When he activates the sector it appears that no interrogation is sent. There is no message although all traces are activated. Is this the expected behavior? If no, what is the best way to workaround this?
Maybe putting an event onto System.[104Network].[104Device].[104Sector].On and calling a Scada Basic function that triggers the general interrogation?
Posted : 18/12/2012 7:15 pm
I have no experience with this protocol but:
1. It looks like a bug
2. Did you try to activate GI periodic request. Maybe, somehow, it will unblock the situation....
3. About the work around, it looks ok but, according to the help: The command SECTOR_GI sends a request for the values of non-cyclic variables.
I am afraid most of the variables will stay NS COM isnt?
Posted : 19/12/2012 7:59 am
Topic starter
1. It looks like a bug
According to César it was designed like this. The general interrogation is only sent when the sector is activated for the first time (usually at project startup). But I must admit that I do not really see a benefit in that.
2. Did you try to activate GI periodic request. Maybe, somehow, it will unblock the situation....
I did not really try. But the general interrogation on a cyclic basis is exactly what my customer tried to avoid in order to reduce network load.
3. About the work around, it looks ok but, according to the help: The command SECTOR_GI sends a request for the values of non-cyclic variables.
I am afraid most of the variables will stay NS COM isnt?
Well, I think this is exactly what my customer wants. He is interested in the messages that are buffered on the device during the time when no direct communication is active. I think it is one of the primary purposes of the general interrogation to collect this kind of data.
Posted : 19/12/2012 8:35 pm
Topic starter
1. It looks like a bug
For your info: This issue (SPR #17479) has been fixed in 10.0sp2 and 11.0.
Posted : 13/03/2013 10:13 pm