Done in version 11.1

2 new system variables.
SYSTEM.LOCALHOST.KEY.OK - 1 if plugged, otherwize 0.
SYSTEM.LOCALHOST.WarningLevel - set to 0 if the dongle is present, set to 1 after first warning, set to 2 after second warning.

Done in 10.0 SP2 Update also.

When SYSTEM.LOCALHOST.WarningLevel = 3 PcVue exit
there is 2 hours Between two warnings in PcVue 11.0 and upper.
there is 10 hours Between two warnings in PcVue 10.SP2 and lower.

I am suprised to see that there are only two hours between two warnings in PcVue 11.

If the first warning is displayed at 9PM, the second at 11PM, PcVue exits at 1AM. When the operator will arrive at 8AM, he doesn't understand why PcVue doesn't work...

With 11.0 and upper version, when you remove the dongle or if the dongle is inacessible, PcVue exit after 4 hours.
If you increase this duration, some peoples could use PcVue without dongle after the starting up.

First case :

2015/01/30,18:05:10.141,6,I,,1,,2,Clé absente
2015/01/30,18:05:11.662,6,I,,1,,2,Clé de protection, attention numéro = 1 WARNING1
2015/01/30,20:05:10.240,6,I,,1,,2,Clé de protection, attention numéro = 2 WARNING2
2015/01/30,22:15:10.124,6,I,,1,,2,Sortie demandée : clé absente Exit request
2015/01/30,22:15:10.438,4,I,,1,,2,CIMWAY,Stop, CIMWAY STOP
2015/01/30,22:15:10.548,6,I,,1,,2,Clé de protection, attention numéro = 3 WARNING3
2015/02/02,08:21:10.127,6,I,,17040,,2,Sortie à cause d'un problème de clé PcVue exits
2015/02/02,08:22:01.452,3,W,,3072,,2,Connexion client->serveur rompue, Serveur02_0C -> Serveur01_0S
2015/02/02,08:22:01.452,3,I,,3188,,2,WinSock erreur = 10053 WSAECONNABORTED
2015/02/02,08:22:01.452,3,I,,3238,,2,Le logiciel a causé l'arrêt de la connexion
2015/02/02,08:22:01.452,3,W,,3074,,2,Connexion serveur->client rompue, Serveur02_0S -> Serveur01_0C
2015/02/02,08:22:01.671,6,m,,1, ,2,End of project

Is it normal that CIMWAY stop but PcVue does not exit?
Domnique, can you explain?

A very important information from Dominique which should be reviewed and formated as a kb article later:

Now the networking right is tested in version 11.0 and upper. Without the networking right (also called WinNet) the networking doesn't work.

The consequences:
1. No networking feature in demonstration mode.
2. If you replace a dongle with networking right by a dongle without networking right, the networking stop to work.
3. On project migration, if the networking right is not present the networking doesn’t work.

Tests:
1. Run PcVue without dongle
a) If the project doesn’t contains networking configuration, there is no modification on the behavior of PcVue. There is no error message in event viewer.
b) If the project contains networking configuration, after starting the networking manager you have the message below in event viewer and Trace.log and MacroTrace.log.
2013/10/08,12:12:39.464,3,W,,11162,,1,Networking cannot be started: insufficient licence right

2. Run PcVue with a dongle which not contains networking right.
a) If the project doesn’t contains networking configuration, there is no modification on the behavior of PcVue. There is no error message in event viewer.
b) If the project contains networking configuration, after starting the networking manager you have the message below in event viewer and Trace.log and MacroTrace.log.
2013/10/08,12:12:39.464,3,W,,11162,,1,Networking cannot be started: insufficient licence right

If a remote station tries to connect you have the message below in event viewer and Trace.log and MacroTrace.log.
2013/10/08,15:53:15.309,3,W,,11164,,1,Server->client connection VARSERV1_0S -> VARSERV2_0C rejected because of insufficient licence right
2013/10/08,15:53:15.309,3,W,,3074,,1,Server->client connection abort, VARSERV1_0S -> VARSERV2_0C

Replace the dongle without networking right by a dongle with a networking right and click on the button “Read key” in the about dialogue box, you have the message in event viewer and Trace.log and MacroTrace.log. 2013/10/08,15:59:34.417,6,I,,1,,1,Key on, licence number=46096
And as the networking is authorized you have the client/server OK connection messages like these in the event viewer and Trace.log and MacroTrace.log:
2013/10/08,15:59:34.904,3,W,,3068,,1,Client->server connection OK, VARSERV1_0C -> VARSERV2_0S
2013/10/08,15:59:34.918,3,I,,1,,1,First connection with server VARSERV2_0S
2013/10/08,15:59:45.512,3,I,,3070,,1,Server->client connection OK, VARSERV1_0S -> VARSERV2_0C
2013/10/08,15:59:45.576,3,I,,1,,1,First connection with client VARSERV2_0C
-> The networking work normally.

3. Run PcVue with a dongle which contains networking right
a) the project contains networking configuration. Start PcVue. The connection are established. You have in event viewer and Trace.log and MacroTrace.log the messages below:
2013/10/08,16:08:18.342,3,W,,3068,,1,Client->server connection OK, VARSERV1_0C -> VARSERV2_0S
2013/10/08,16:08:18.362,3,I,,1,,1,First connection with server VARSERV2_0S
2013/10/08,16:08:26.456,3,I,,3070,,1,Server->client connection OK, VARSERV1_0S -> VARSERV2_0C
2013/10/08,16:08:26.514,3,I,,1,,1,First connection with client VARSERV2_0C

Replace the dongle with networking right by a dongle without a networking right and click on the button “Read key” in the about dialogue box, you have the message in event viewer and Trace.log and MacroTrace.log.
2013/10/08,16:17:26.924,6,I,,1,,1,Key on, licence number=39352
2013/10/08,16:17:26.927,3,W,,3072,,1,Client->server connection abort, VARSERV1_0C -> VARSERV2_0S
2013/10/08,16:17:26.928,3,I,,3188,,1,WinSock error = 10053 WSAECONNABORTED
2013/10/08,16:17:26.928,3,I,,3238,,1,Software caused connection abort
2013/10/08,16:17:26.929,3,W,,3074,,1,Server->client connection abort, VARSERV1_0S -> VARSERV2_0C
2013/10/08,16:17:56.942,3,W,,11164,,1,Server->client connection VARSERV1_0S -> VARSERV2_0C rejected because of insufficient licence right
2013/10/08,16:17:56.942,3,W,,3074,,1,Server->client connection abort, VARSERV1_0S -> VARSERV2_0C
-> All existing connection are broken.

Replace the dongle without networking right by a dongle with a networking right and click on the button “Read key” in the about dialogue box, you have the message in event viewer and Trace.log and MacroTrace.log. 2013/10/08,16:23:21.559,6,I,,1,,1,Key on, licence number=46096
And as the networking is authorized you have the client/server connection OK messages like these in the event viewer and Trace.log and MacroTrace.log:
2013/10/08,16:23:21.831,3,W,,3068,,1,Client->server connection OK, VARSERV1_0C -> VARSERV2_0S
2013/10/08,16:23:27.114,3,I,,3070,,1,Server->client connection OK, VARSERV1_0S -> VARSERV2_0C
-> All re-work normally.

BR

DL