more quick actions
minimize quick actions
Topic starter
Hello guys,
One of our customer uses Lonworks communication in the architecture of two redundant server.The customer told me when two servers running at the same time, two Servers often lost connection with many DDCs. If one server running, only few DDCs lost connection.
The multinetwork configuration is OK.
LNS version：3.25
PcVue:10.0.16002 SP1
Anyone can give some advises? thanks.
BR,
Mark
Posted : 16/12/2015 2:36 pm
redundancy is impossible with lonworks...
Posted : 16/12/2015 3:37 pm
Topic starter
Thank you.
but Why?
BR,
Mark
Posted : 17/12/2015 2:19 pm
It's a limitation of the LonWorks protocol.
Posted : 17/12/2015 2:46 pm
Topic starter
So if the customer insists to use redundant PcVue server station, any good way to solve this problem?
Can we use Scada basic function LNS("startnetwork","networkname") and LNS("stopnetwork","networkname")?
BR,
Mark
Posted : 17/12/2015 3:12 pm
The limitation is not on PcVue, the limitation is on db side. It's true since the begining of lonworks.
Posted : 17/12/2015 3:21 pm
Yes, Sylvain is correct.
But, just to be accurate Sylvain, it's like this since the beginning of Lonworks but I heard LNS has implemented new services (since 3.2 if I am not mistaken) allowing the redundancy but we never implemented them in PcVue.
@Mark, the limit is that you can't have 2 active Lon DB on the same network managing the same devices...
Using the LNS instruction is not sufficient. If you stop the PcVue LNS network you must also stop the Lon DB and the only way is to kill it. That's really not clean...
By the way I did it on 1 project long time ago and it worked :whistle:
Nico
Posted : 17/12/2015 4:53 pm
Perhaps, Jacques could have more information.
Posted : 17/12/2015 4:55 pm
It is like we have the same discussion coming back every 6 months about this subject.
Everything in the configuration HMI of PcVue would have been ready if only Echelon could manage redundancy transparently and natively but due to the LonWorks Server limitation it can not be implemented at all.
Maybe in some very specific cases it can SEEM to work, we do not and we can not validate any solution as long as this limitation exists.
This is what we have to say to our customers (Echelon LNS Server limitation, that's all).
I let Development team correct my post if what is written above is wrong.
Edouard
Posted : 17/12/2015 7:23 pm
Topic starter
thanks all of you.
The customer tried SCADA Basic function LNS(), and it seem to work. and the customer take this way. :cheer:
Posted : 22/12/2015 2:28 pm