Hello,
I have a memory hole!
On startup we could see quite often actually the famous message:
"no response from subcribe request, timeout=20s"
I know it's a "normal" message appearing when too many and/or too slow devices are involved.
How to settle this issue? By changing the time-out or by saying to PcVue to make asynchronous startup...
I remember there is something to configure either on sv32.ini or varconf.dat but I can't find this information... 🙁
Hi,
About sv32.ini or varconf.dat, parameters definition is in the developers memory (hope there is no hole).
A work around could be to start communication thanks to a scada basic program.
Hope it helps you.
Thanks Brice,
Your post reminded me that I found the solution but didn't update this post!
In COption.dat (not sv32.ini actually) you can see the following options:
[WATCHVARSEXT]
PacketSize=500
TimeoutEnable=1
Timeout=20
[WATCHVARSEQT]
PacketSize=100
TimeoutEnable=1
Timeout=20
[WATCHVARSOPC]
PacketSize=100
TimeoutEnable=1
Timeout=20
[WATCHVARSDDE]
PacketSize=100
TimeoutEnable=1
Timeout=20
[WATCHVARSLNS]
PacketSize=50
TimeoutEnable=1
Timeout=20
[WATCHVARSBACnet]
PacketSize=100
TimeoutEnable=1
Timeout=20
So, you can disable this time-out or increase it.


