CitectSCADA Web Server/Client

[jgreenewv]

Does anyone have any first-hand experience setting up CitectSCADA Web Server and Web Client deployments? I've got everything deployed, and I can access the project over the network, but it doesn't show data from the running project, and apparently isn't pulling the Web Client license across, as the Web Client shuts down after a couple of minutes with an error of "No protection key found or no licence available from network." Thanks in advance.

Joe

[jgreenewv]

Update:

After tweaking some settings, it looks like the license is now transferring, as the Web Client will start up and run properly (it's been up now for over an hour.) However, so far the Web Client is still not showing alarms and data from the Web Server. Thanks again.

[Marsupilami]

Hello,

i have only done some tests with the webclient, and from your explanation everything seems ok.

Only one common mistake comes to mind (it is one that happens often when making a test setup). The tags you are trying to visualise are not memory tags ?? if they are you should make them disk tags, memory tags are independent for each machine, also for a display client.

Regards

Marsupilami

[jgreenewv]

Hello,

i have only done some tests with the webclient, and from your explanation everything seems ok.

Only one common mistake comes to mind (it is one that happens often when making a test setup). The tags you are trying to visualise are not memory tags ?? if they are you should make them disk tags, memory tags are independent for each machine, also for a display client.

Regards

Marsupilami

Ok, I took your advice and switched everything to disk tags. That did not seem to make a difference, so I got a PLC hooked up with a test program, and now I am pulling data across the network. However, the alarms still do not appear to be working properly. Did you do any testing with different alarm groups, and how they work on the web client end? On the Tools page, I am showing the web client connecting to the Alarm server. Thanks for the help.

Joe

[Marsupilami]

Hello,

I didnt specificly test the alarms over here but i do remember that they worked without a problem.

maby if you could give a more detailed description of the problem i could be able to help you.

Regards

Marsupilami

[jgreenewv]

Marsupilami,

Basically, I am connected to a master PLC with CitectSCADA, the master PLC is polling two remote sites. I have three alarm groups set up, one for each PLC (master and two remotes). The alarms are logging and displaying properly on the Server, but not on the Web Client. According to the Tools page on my CitectSCADA server, the Web Client is successfully connecting to the Alarms server. However, as i said, none of the alarms are showing up on the Web Client end of things. Thanks.

Joe

[Marsupilami]

Hmmm,

I can't think of a reason that would cause such problem ... if the connection for the io data is ok then the connection for the alarms should also be just fine.

i was thinking that maby you wre using Alarm tags, but if the alarms dont show on a standard alarm page then i am out of options.

i can only say that it should work...

but now as i am typing this, a thougth comes to mind!.

on the server is the data directory correctly set? if the directory does not exist the alarms won't work. if the directory exists, you should check if there are files there with the name query0, query1 (i have seen up to 3 files there but one should be enough) and so on. the CTAPI interface uses these files to get the alarms from the server and send them trough.


Greetz,

Marsupilami

[jgreenewv]

Ok, I've got everything working now with one exception. I just sent this up to the Citect User List also. On my overview screen, I've got an icon representing my three PLCs. The alarms for each PLC are separated into different alarm categories. I'm using the AlarmFirstCatRec function to pop up a red box around the icon if that particular PLC alarm category has an active alarm. This works fine on the server end, but the box stays on all the time on the web client end. I scanned through the Web Client guide again to make sure I didn't overlook it, but that function isn't listed as not working with Web Client. Thanks again for all your help on this.

Joe

[Marsupilami]

Hello,

thats quite normal, the function "AlarmFirstCatRec" only works on a alarm server, wont work on any display client, even when it is a normal display client.

You can however run a task on the alarm server and use the "AlarmFirstCatRec" function there and put the status in disk tags. then you can use the disk tags to visualise the status.

Another solution is to use a remote procedure call ("MsgRPC") to call the function on the alarms server.

Greetz,

Marsupilami

[jgreenewv]

That's what I was suspecting. I'll try your disk tag recommendation and see if that works. Thanks.

Joe

[jgreenewv]

Marsupilami,
It's working perfectly now. Thanks for all your help. I'm quite impressed with the Web Client operation, I just wish Citect would improve some of their documentation to reflect all of the functions that won't work, the configuration details, etc. Oh, well. Thanks again.

Joe