Yes it’s possible to connect a PCD directly to the internet, but you have to protect your PCD against unauthorised access or cyber-attacks.

To protect the PCD against unauthorised access or cyber-attacks, it’s imperatively needed to take some protective measures.

Information about protective measures can be found on the support hp

If you need a PCD with cyber security levels SL3+ and based on ANSI ISA 62443 then checkout our PCD3.M6893 (QronoX PCD), this PCD was developed for cybersecure applications.

Information's can be found here.

Problem

In relation with the DeviceTemplate, there can be a problem on the Saia PCD Supervisor, which occurs after an automatic logout, a restart of the station or a restart of the web server.

In this case only the last visited page is displayed, but without the DeviceTemplate menu

The reason for this is, that the Niagara web server sets a cookie called "niagara_origin_uri" with the latest visited ord.

This cookie is valid until page is closed or reloaded. he deviceTemplate cannot prevent this from happening.

The problem occurs in all Saia PCD Supervisor versions.

Depending on the last visited page and the settings in the supervisor, the image may look like this or similar:

Correct it looks like this:

Workaround

The "niagara_origin_uri" is not set if Same Site option is configured to "none" in a Secure context (HTTPS).

Niagara

1. Go to "Station -> Config -> Services -> WebService".

2. Set the Option "Same Site" to "None".

3. And make sure that HTTPS is active

Browser

1. Clear all cookies at least for the Niagara webpage.

- How to in in Chrome

- How to in Firefox

- How to in Edge

Note: 
You must connect via HTTPS to the Niagara-Webserver, if not the solution may not work or the page may not work at all. (May depend from the browser).

This will only work with the following Browser versions (or newer versions):

PC:

- Google Chrome 80

- Edge 86

- Firefox 69 (See  note below)

- Internet Explorer (Not supported!)

- Opera 71

- Safari (Not supported!)

Mobil:

- WebView Android 80

- Chrome Android 80

- Firefox Android (Not supported!)

- Opera Android 60

- Safari auf iOS (Not supported!)

- Samsung Internet 13

Note:

Firefox for PC has not yet the option "Secure required" for the "SameSite=None" attribute by default (will be default in the future).

1. It need to be configured by typing "about:config" into the address bar

2. Search for "SameSite"

3. Set "network.cookie.sameSite.laxByDefault" to true.

4. Set "network.cookie.sameSite.noneRequireSecure" to true.

No

Saia-Burgess Controls devices and software are not affected from Domain Name System (DNS) vulnerabilities published with the report name NAME:WRECK

-

No, SBC devices are not affected from the Ripple20 zero-day vulnerabilities since none of our products uses the TCP/IP software library developed by Treck, Inc.

Yes it’s possible to display the texts for the operator of the Saia PCD Supervisor in English, German or French.
Please note, that only the texts for the operator will be displayed in German or French, but the texts for the developer will be still in English.

More information can be found on the support homepage of the Saia PCD Supervisor.

If the PC where Saia PCD Supervisor is running, was powered off without shutting down the Saia PCD Supervisor then it’s possible that after power on of the PC, the platform daemon used from Saia PCD Supervisor will not start automatically during system restart.
It’s necessary to start the platform daemon for the Saia PCD Supervisor manually.
The attempt to start the daemon via a batch script didn't work either.

A modification on the registry could solve the problem.

Solution:
The problem is not in relation with the platform daemon used from the Saia PCD Supervisor but it’s a problem in relation of the Windows internal timings between window services.

To solve the problem, the following modifications on the registry entry of the concerned PC should be done.

Make the following steps:
1.
In Windows, go to Start > Run > and type regedit
2.
Navigate to: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control
3.
With the control folder selected, right click in the pane on the right and select new DWORD Value
4.
Name the new DWORD: ServicesPipeTimeout
5.
Right-click ServicesPipeTimeout, and then click Modify
6.
Click Decimal, type '180000', and then click OK
7.
Restart the computer
If this in insufficient, try setting to 300000