GucciMechie (Customer) asked a question.
I'm unable to activate the WebVisu server on a P2CSD-622. Any help would be appreciated.
Trying to follow the second quick-start tutorial. It's been 2 days... I've checked all that I could think off. I can ping the PLC just fine, the web browser returns a "refused to connect" message, and that's that.
I was told it might be a license issue? But the license manager won't talk to the PLC either, says the device doesn't support that service.
Other than that the first quick-start program ran fine, but I can't proceed any further without getting WV to run.
Thanks
The "refused connection" to my knowledge is usually from trying to access the cpu on the wrong port.
I would double check you are using the correct port number which is by default 8080 (443 for https).
The P2CDS-622 WebVisu is licensed so I don't believe that would be the issue.
Yup tried with the correct port numbers .
I get that it's licensed, but that error on the licensing manager could be related? If somehow it's broken, maybe the build-in license is not activating? here's the screen shot
Yeah I just tried that too and got the same message. You can use the Device License Reader to check the licenses. Should be right under the Manager in tools.
It will remove the project on there so make sure you have it backed up.
ok, this worked, and yup the license is there.
So back to square 1.
I don't think it's networking, since everything else works, I can ping ok, etc. If the server process is up, what else can it be?
Can you check the logs to see if the webserver started successfully. This will be located on your Device(P2CDS-622) --> Log tab on the left side.
Just to note, the cpu must be in run mode to connect to webvisu. If you have an existing error that is preventing the cpu to go to run mode then the webserver will not be started.
there are two errors in the log file. Seem to be certificate related. I regenerated it. But they're still there.
Most of my web access tests were with http://...:8080 though.
(meanwhile, thanks for the help!)
No problem :-).
The certificate error can be resolved by creating a new one in View --> Security Screen. But it shouldn't affect the webserver.
Website Reference Link
From your logs it looks like the Webserver hasn't been started. If you look at my logs it should have a message for Webserver started.
I know it's redundant but double check and make sure the cpu is in run mode. The run switch needs to be in the up position. If it's down (stop mode) you won't be able to put it into run mode via Codesys run button.
Nothing is redundant at this point, I'm clearly missing something trivial...
I did regenerate that cert, the problem persists.
The PLC is in run mode, I ran the first quick-start program no problem
Can I make the log more detailed to see why the server is not starting?
You can try going to the PLC Shell and use the following command. Do a stop and run transition to see if any new logs appear from CmpWebServer.
logsetfilter [CmpWebServer] 0xFFFFFFFF
As a thought...
Certificates are time sensitive. Make sure that each device has an accurate time/date.