22.1.5         Waiting for Connection To SCADA Node

If you get the message, "Kernel on scada node is not running", it might be as simple as the SCADA Node is “stopped”. You can use the "Start Node" hyperlink if your system engineer makes that available to you.



The good news is you are talking to the Project Node.  If you have Multiple Projects or multiple Nodes, it may be that you are trying to connect to a SCADA Node or Project that is off line.

For a Multiple Node System:

a.      Try selecting Start View for a different SCADA Node or Project. You may have to try all of those listed.  There maybe only one “real project” and one “real SCADA node”, but an engineer has configured others for testing of future commissioning. 

b.      Try selecting Start Node.  You should do this if you know which Node should be running in which project. 

                                                  i.      To Start a Node, you will be prompted for username and password. You will need an administrator (admin) or Project User name and password to start a node.

Figure 22.5 Start Node - admin or Project User Login

If you get the message,  “Waiting For Connection to SCADA Node”, it may be that the SCADA node is restarting after a download.  Or, it may be the network connection is unavailable. The last possibility is that the primary and secondary TCP ports (4592 and 14592 are the defaults) are blocked by a firewall or router. These require you contact your network administrator.  You could try pinging the SCADA node (if you know it's IP Address, see 22.1.3 Check the Deploy file from Web browser client ). More realistically you could try section 22.1.7 Firewall or blocked TCP ports

Figure 22.4 Waiting for Connection to SCADA Node.