Hello,
I would like to make error weighting to take into account if some of our clients are alive or not.
Could you please help me.
We have redundant SCADA system with XML-RTSP clients.
I want to make error weighting to take into account if some of those clients are alive or not.
I have DPs for one of those clients:
System1:Asterisk.IntegrServer.alive
System1:Asterisk.IntegrServer.timestamp
System1:Asterisk_2.IntegrServer.alive
System1:Asterisk_2.IntegrServer.timestamp
"Asterisk" is used for "Host1", and "Asterisk_2" for "Host2".
Asterisk client calls functions in ctrl script that sets actual time of last time client sent "I_am_alive" (timestamp).
There is control script that checks if client sent "I_am_alive" every 6 seconds.
DP "alive" is set to true if client "checked_in", and false if it did not "checked_in" in last 6sec.
This control script that checks if client is alive is running on both redu servers, and checks both clients (Asterisk and Asterisk_2).
In config.redu file in config path of WinccOA 3.12 threre is:
($host1) fwdDP = "SysVijenac:Asterisk.IntegrClient.timestamp"
($host2) fwdDP = "SysVijenac:Asterisk_2.IntegrClient.timestamp"
In the System_overview - Error State there is defined DPE: Asterisk.InetgrClient.alive != TRUE.
The problem is following:
If Asterisk_2.IntegrClient.alive is in state false, both redu servers takes this as an error state.
While, if Asterisk.IntegrClient.alive is in state false, only left (host1) redu server takes this as an error state.
Please help me solve this problem.
Did I make a mistake in system design or is it something else?
Thanks in advance,
Vedad Ramovic
Forwarding DataPoints for error weighting
- vedadramovic
- Posts:121
- Joined: Mon Apr 07, 2014 10:36 am
Forwarding DataPoints for error weighting
- fmulder
- Posts:330
- Joined: Wed Feb 03, 2010 9:46 am
Re: Forwarding DataPoints for error weighting
I have two suggestions:
* I don't believe you should have a system name in your forwarddp
* You might check the function 'getReduDp'. Make sure that your datapoint is actually recognised as a redu datapoint
* I don't believe you should have a system name in your forwarddp
* You might check the function 'getReduDp'. Make sure that your datapoint is actually recognised as a redu datapoint
- vedadramovic
- Posts:121
- Joined: Mon Apr 07, 2014 10:36 am
Re: Forwarding DataPoints for error weighting
Hi Frenk,
thank you for suggestions,
I deleted systemname, but it did not help.
function getReduDP returns true only if DP is Asterisk_2, on right and left side server.
sReturnReplicaDP1 and sReturnReplicaDP2 returns Asterisk and Asterisk_2 (as if there is good redundant DP).
I still have a problem: If Asterisk_2 is false, it causes error state on both server.
If Asterisk == false error state is only on left side server (host1).
Best regards,
Vedad
thank you for suggestions,
I deleted systemname, but it did not help.
function getReduDP returns true only if DP is Asterisk_2, on right and left side server.
sReturnReplicaDP1 and sReturnReplicaDP2 returns Asterisk and Asterisk_2 (as if there is good redundant DP).
I still have a problem: If Asterisk_2 is false, it causes error state on both server.
If Asterisk == false error state is only on left side server (host1).
Best regards,
Vedad
- vedadramovic
- Posts:121
- Joined: Mon Apr 07, 2014 10:36 am
Re: Forwarding DataPoints for error weighting
Hi Frenk,
After erasing DPs that where in error weighting table and afterwords adding those again, this issue was no longer present.
Thank you for your suggestions and will to help.
Best regards,
Vedad
After erasing DPs that where in error weighting table and afterwords adding those again, this issue was no longer present.
Thank you for your suggestions and will to help.
Best regards,
Vedad