You try to access a File on the Web-Server of the PCD with the HTTP protocol e.g. with an Internet Browser. The Web-Server responds with the Error message File not found. (HTTP 404 Not found)

Problem
The Web-Server can't find the file although it is visible with FTP access.

Reason
This happens because the file system has just been formatted with the Memory management FBox before.


Solution
After formatting the file system with the Memory Management FBox it is necessary to switch off / on the PCD (remove 24V). For PCD3.R600 flash memory modules there is also another solution the SD-card can be removed and reinserted. After this operation the file can again be accessed with HTTP protocol.

Note
This inconvenience will remain on FW versions <= 1.16.xx but it will be corrected for future firmware versions. It won't be necessary anymore to switch off / on the PCD.

By using the CGI interface from the PCD it is easy to read or write values from a PCD over Ethernet (or using SBC.Net WebConnect).

In  Excel select the cell where the PCD MEDIA shall be visible: Then select New web query from : Data /Import External Data / New Web Query
In the new Web Query window  write the cgi command readVAL in the address window.

Example
First select the desired position in the Excel sheet where the value shall be displayed. Then open "New Web Query..." and enter: 

• In case of the use with WebConnect: 
  localhost/pcd_name/cgi-bin/readVal.exe .
  
  
   
• case of direct http connection: 
  IP_Address_of_PCD/cgi-bin/readVal.exe . 
• To write: IP_Address_of_PCD/cgi-bin/writeVal.exe _to_write
  
  After the PCD has been connected, select the value which shall be displayed (and define under "Options" whether it shall be updatd regularly).

  

  Note: attached is an excel example, to write values into the PCD a dynamic link  has been used.You have to write the desired PCD value in the cell and to update the value into PCD, clik in the link "write value".

The first generation of PCDs with integrated S-Web server did not support http-direct (e.g. the PCD1.M125, PCD1.M135, PCD2.M150, PCD2.M170, PCD2.M480) . Therefore the access of the S-Web Server must be realized using the free software "S-WebConnect" which is to be installed on a PC (accessing the PCD using e.g. Ether-S-Bus). Alternatively, an MB Panel can also access the S-Web Server (e.g. using Ether-S-Bus).

However, it is important to know that only one S-Bus client can access the S-Web Server over Ether-S-Bus at the same time!

Problem
By desing the S-Web Server of a PCD can only be accessed by one S-Bus connection per physical port (Serial-S-Bus, Profi-S-Bus, Ether-S-Bus). As result it is possible to access the S-Web Server over Serial-S-Bus and in parallel over Ether-S-Bus, but it is only possible to have one Ether-S-Bus Master which connects the S-Web Server.

That means it is not possible to access the S-Web Server of a PCD at the same time with the S-WebConnect (Ether-S-Bus) and the MB panel (Ether-S-Bus) because in this case the S-Web Server is accessed 2 times trough the same physical port (Ethernet Port).

Work around 
Here you can use the Web Connect as frontentd. The S-WebConnect will serialize the web requests and therefore avoid two parallel connections.

• The WebConnect creates only 1 connection to the Eternet Port of the PCD (Ether-S-Bus to a PCD1.M135 for example)
  --> there is no problem, because only one connection was created
• With the MB panel, instead to accessing the WebServer of the PCD directly (with the Ether-S-Bus protocol), the MP panel can be accessed indirectly via the S-WebConnect.

Example
For this example the following configuration is to be done in the MB panel configuration:

• HTTP direct
• Remost host IP of the PC (where the WebConnect is installed)
• as html file to open, you have to write: WebConnect_Connection_Profil/File_Name.html (htm)

For more information please refer to the manual for the "Web Server Classic" (26/790).

If a webconnection is established over modem with the current Webconnect 2.0.18.2 the webpages is displayed, otherwise the values are missing.

Problem
If all files except the .tcr file are stored in C:\Webpages the values are not displayed when connecting over modem. It is always necessary to execute a reload.

Reason
The reason is, that if the htm or html file is stored local in C:\Webpages the webconnect does not establish the connection with the PCD imediatly, since all necessary data is available offline.

Solution
To solve this problem the htm or html file has to be downloaded to the PCD using the Webbuilder (.wsp).

Additional information:
All files that are stored in C:\Webpages has to be stored in a subfolder with the name of the connection.

The SBC.Net WebConnect does provide an own driver for S-Bus Communication for most of the communicaiton methods (Ether-S-Bus, Serial-S-Bus and Profi-S-Bus). However, in some cases the SComm driver is required. This FAQ indicates where the WebConnect is looking for the drivers.

How to find out whether WebConnect knows about the SComm driver?
If you can not select e.g. "Ether-S-Bus (SComm)" as communication driver as "Connection Type" in WebConnect (see below), your WebConnect can not find the SComm:

If "Ether-S-Bus (SComm)" is available, the WebConnect found a running Scomm:


When does the WebConnect need the SComm driver?
The SComm driver is required if one of the following questions has to be answered with "Yes":

• Is a USB connection to the PCD system required?
• Is a Modem connection to the PCD system required?
• Is there an other application (PG5, OPC Server or Visi+) using the same serial communication port (e.g. RS232) in parallel to the WebConnect software?

Where does WebConnect look for the SComm driver?
WebConnect 2.0.x.x. checks the following 3 Registry entries and looks in the locations where the value of the entry is pointing for the SComm driver:

• My Computer\HKEY_LOCAL_MACHINE\SOFTWARE\SAIA-Burgess\PG5\2.0\Global\AppsDir
• My Computer\HKEY_LOCAL_MACHINE\SOFTWARE\SAIA-Burgess\PG5\1.4\Global\AppsDir
• My Computer\HKEY_LOCAL_MACHINE\SOFTWARE\SAIA-Burgess\SAIA Communication Driver\1.4\Global\AppsDir

For checking whether these entries exist, open the Windows Registry Editor by selecting "Run..." from the Windows "Start Menu" and typing "regedit".

What to do if I don't have a SCommDll?
In case on your PC there is no Scomm installed (which is the case with a stand-alone installation of WebConnect 2.0.16.4), please install the last version of the SBC.Net WebConnect (which can be found on the support site under Software --> WebConnect or on the PG5 Controls Suite CD). Please first uninstall the previous version and then install the last version. 

In some special cases (e.g. if the WebConnect system tray icon has been disabled) it may be necessary to figure out which port the WebConnect is using for answering requests (the listener port).

Where to find the WebConnect settings?
SBC.Net WebConnect 2.x does store all its configuration settings in the file "SBC.Net.settings.xml" file which is stored in its installation path. This can be

• When installed together with PG5 1.4:
  c:\Program Files\SAIA-Burgess\Saia.Net_2_x_x_x\Saia.Net.settings.xml
• When installed with PG5 2.0:
  c:\Program Files\SAIA-Burgess\PG5_20\SWebConnect\Saia.Net.settings.xml
• When installed with PG5 2.1:
  c:\Users\my_name\AppData\Local\SBC\SBC.Net\Saia.Net.settings.xml

In the configuration file, look for the expression
webserver_settings port="81"
which defines the port where the WebConnect "listens" for requests.
 

Note
This FAQ is only from interest in case the "common" way for configuring WebConnect can not be used. Otherwise, just use the common way by

• selecting "Configure..." from the context menu (right-click) of the WebConnect icon in the system tray:
  
• or by typing the URL localhost/setup (the default port for WebConnect) 

When using the SBC.Net WebConnect on a PC or an eXP Panel you have to "terminate" the WebConnect task every time you shut down the PC.

Symptom
When the SBC.Net WebConnect (version 2.x or later) is running on a PC or eXP Panel the system does not shut down immediately after clicking "Shut Down.." from the Windows Start Menu. Instead, a Window indicating "End Program - SBC.Net.exe: This program is not responding. To return to windows..." is shown. As soon as any button on this Window is clicked, WebConnect and the system is shutting down as expected.


Reason
The reason for this behaviour is that the WebConnect software (in detail it is the "system tray icon" task) does not get the information (from the Windows OS) that the system is shutting down until the user has clicked a button on the window mentioned. This information (that the system is shutting down) is only sent from Windows to the SBC.Net WebConnect after the user has klicked a button on the window.
As result, WebConnect does not shut down until a button on the window is clicked.

Solution
In order to avoid this behaviour, it is possible to disable the "system tray icon task". If this task is not running, it does not need to be stopped and the problem is avoided. On the other hand, there is no indication in the system tray that WebConnect is running.
In order to disable the "system tray icon", proceed as following:

• Right-click the WebConnnect icon and select "Configure..." 
  
• Click on the "Settings" button at the right side of the configuration page of WebConnect
  
• Select "Show Advanced Settings"
  
• In the "Loader" section, unselect the "System Tray Admin"
  
• Restart the SBC.Net WebConnect 
• Unload the ScommXX7 from its context menu in the system tray. This is only necessary once (the xx7 driver has been loaded because WebConnect checked all available drivers while disabling the system tray icon).
  

Remark
If the system tray icon is not shown, it is not possible to call the WebConnect configuration page directly from the context menu of the icon. For figuring out the port WebConnect is using on a PC, please refer to FAQ 101126 (link below).

I'm using SWebConnect on my PC or on the MicroBrowser Software to browse my web-project. My start-page (i.e. start.htm) and all my other files of the web-project (except *.tcr) are hold in the local 'Webpages' directory on my harddisk drive (PC) or on the local flashcard (Web-Panel). But my start-page's not displayed. The default Firmware page or the error message 'start.htm file not found' is displayed instead.

Symptom
SBC.Net WebConnect is used on a PC or on the MicroBrowser Software. The start-page (e.g. start.htm) and all the other files of the web-project (except *.tcr) are stored locally in the "Webpages" on the harddisk drive (PC) or on the local flashcard (Web-Panel).
But when typing the URL in the browser, the start-page is not displayed. Instead, the default firmware page (on a PC) or the error message 'start.htm file not found' (when using the uBrowser on a CE panel) is displayed.

Reason
The reason for this behaviour is that the browser requests the start.htm page from the WebConnect, and WebConnect first requests this page from the PCD. The PCD itself already has the default firmware page, because there is no "user specified" start.htm.

Solution
The solution is:

• Create in the 'Webpages' directory a subdirectory with the name of the defined and used SWebConnect connection
• Put all the project-specific files (except *.tcr, which must be loaded into the user program of the PCD) into this subdirectory.
• Configure the "Search Order" to "Local then PCD":
  
• In the browser on in the uBrowser, configure the full path of the start page (e.g. localhost/MyConnection/start.htm) and not only the URL to the PCD (localhost/MyConnection/).

As a PCD system does feature various "Internet communication features" (Web Server, Ether-S-Bus, SMTP etc.), it suggests itself to connect it to the Internet using e.g. an (A)DSL router. This FAQ is aimed to explain some key-points to be considered for accessing a PCD over the Internet.

General introduction
For connecting a PCD to the internet using an ADSL router, the principal understanding of the functionality and tasks of a router need to be understood. In a second step, the communication protocol for the connection is to be defined because
every of the following protocols does require other configurations of the router. The attached document tries to explain the router functionality and tries to point out relevant information for connecting a PCD to the Internet and realizing the communication over the following protocols:

• http direct (for accessing the Web Server of the PCD, don't forget the password protection of the Web Server)
• Ether-S-Bus (not recommended unless you are using a secure VPN connection)
  - for programming the PCD with PG5
  - for connecting a PCD which does not feature http direct with WebConnect)
• SMTP (for sending EMails from the PCD)

For each of these protocols, please refer to the corresponding chapter in the attached document.

Important remark concerning security
Please consider the fact that the connectivity of a PCD on the internet does also mean that everyone can connect to the system. Therefore the interfaces over which the PCD can be reached from the internet need to be protected additionally (if the web server can be reached from the internet and no security is implemented, everyone can e.g. modify Register values on the PCD which can lead to malfunction of the application).

We therefore recommend whenever possible to use a VPN connection rather than just forwardig ports.
If this is not possible:

• Enable the password protection of the S-Web server (this can be configured in the PG5 Device Configurator)
  Note that the password macro in the Web Editor does NOT secure the access to the media of the PCD (but only the access to the Web Editor Pages)
• Remove the default user "root" from the FTP server (can also be done in the PG5 Device Configurator)
• Do not enable Ether-S-Bus unless the PCD is connected over a VPN connection only (because even with the password protection of S-Bus will still allow everyone to modify media values as e.g. Register Values)

By default there are 12 listener sockets defined on the Web Server of a PCD. This means that simuntaneously 12 Web browsers can communicate with the S-Web server. The connection of a 13th browser would be disconnected directly. This number can be extended to 24 listener sockets in the Device Configurator from PG5 2.0 SP1 or later. This means that there's still an upper limit. There's a way to define this 'unlimited' number of connection.

You can define all the possible connections to the PCD, i.e in HTTP direct mode, in the S-WebConnect running on the host PC. In this way, all the different Browsers requests and connections are tunneled through the S-Web Connect. There's only one point you have to pay attention: Per default, the S-Web Connect limits to define a maximum of 15 connections. But you can adjust this limit in the 'Saia.Net.settings.xml' configuration file that is installed in the SWebConnect folder. Simply edit manually the line

<component id="SaiaBurgess.SCS.WebServer">

by

<component id="SaiaBurgess.SCS.WebServer" maxConcurrentRequests="200">

if you want to define 200 connections in the SWebConnect.

Remarks

• Please be careful with this feature when using it with a CE-Panel because of the small RAM memory.
• Never allow more than 15 connections for WebConnect on a CE-Panel.
  

Also it is possible connecting the Web Server of a PCD3.T760 using WebConnect 2.x, it is not automatically possible downloading a new I/O configuration.

Symptom
After having connected to the WebServer of a PCD3.T760 RIO, it is possible identifying e.g. the firmware version. But it is not possible to download a new I/O configuration (e.g. for monitoring/writing the I/Os without a Profibus DP or Profi-S-I/O master). After clicking the button "Download", the button "Start Monitoring" remains inactive.


Reason
The reason for this behaviour is that WebConnect 2.x does cash the content of the page by default. The refreshing method in the Web connect settings, section "setting webconnect" is set default to "Cache fill once".

Solution

• If it is possible, just update the SBC.Net WebConnect to version 2.0.16.4 or newer (please contact your local SBC support for the latest version). Starting with this version, the pages are never cached, if the connection type is "RIO". 
• In case SBC.Net WebConnect older than version 2.0.16.4 is used, change the WebConnect Caching strategy from "Fill Once" to "Don't cache pages from the PCD".

If during the installation of PG5 1.4 or SBC.Net Web-Connect there is an Error message: "Error 1606. Could not access network location WINDIR\system32", there could be two reasons for the cause.

Symptom
During the installation of PG5 1.4 on a PC with Windows 7 or SBC.Net Web-Connect on general there is following Error message:
Error 1606. Could not access network location WINDIR\system32

Possible reason 1
You have started the setup file of SBC.Net Web-Connect from a external server.
It’s not allowed to start the setup file of SBC.Net Web-Connect from an external server.

Solution 1
To solve the problem, copy the setup file of SBC.Net Web-Connect to your PC and start the setup file of SBC.Net Web-Connect locally on your PC.


Possible reason 2
You try to install PG5 1.4 on a PC with Windows 7.

Solution 2
It's very important to exactly follow the document "Installation Guide for PG5 1.4.300 on Windows 7 (64 bit)" out of the FAQ #100710 "Is PG5 1.4 compatible with Microsoft Windows Vista and Windows 7? ". In details to change the installation folder of PG5 1.4. Instead of "…\Saia_Burgess\PG5 1_4" add an underscore in "PG5_1_4".

Yes, this is possible and makes sense when connecting with the same PC to several Webservers.

Problem
When accessing several CPU's with the same Webconnect it would be comfortable to create subfolders.

Solution
Data which should be available for all CPU's like the IMaster.jar can be placed directly in the Webconnect folder. For each station you can create a subfolder with the name of the connection for this station (e.g. "station1" ; "station2" ; "station3" etc.)

In these subfolders you can place all files which are only for this station. When accessing station1, the URL is: localhost/station1

If you make a online modem connection with PG5, OPC-Server, S-Web-Connect or Visi+ to a PCD then the modem settings of the TAPI (Telephony Application Programming Interface) are used.

TAPI is a Windows standard interface and the TAPI settings are accessible under the control panel, “phone and modem options”.
There you have the possibility to adapt different modem parameters like baud rate, data protocol and so on.

The channel settings menu of PG5 allows modifying the modem parameters of TAPI settings which are used without that the TAPI settings of Windows are changed.

Please not that the channel settings menu of PG5 does store the modified TAPI settings in the registry of Windows under the key name:
HKEY_LOCAL_MACHINE\SOFTWARE\SAIA-Burgess\PG5\x.y\Channels\S-Bus Modem\TapiSettings

PG5 does not change the TAPI settings of Windows.

The registry entry mentioned above is updated after that you have open the menu point “configure line” and you have stored the configuration settings of the modem.



 

PG5 does apply the following rules:

- If PG5 don’t have any entry on the registry key mentioned above or if the registry key mentioned above don’t exist, then PG5 does use the default TAPI settings (defined under the control panel, “phone and modem options”) of the selected modem.

- In the other case PG5 does use the modified TAPI settings stored under the registry key mentioned above.

Yes, this is possible in WebConnect 2.0 (distributed together with PG5 1.4.200) and later. Unforunately, the indication in the WebConnect configuration page is somehow missleading (because it is written IP address, and no indication of an URL is given).

How to provide the IP address of a PCD as URL?
Instead of the IP address, also a URL can be entered:


This notation can be used for Ether-S-Bus connections and for http connections.

It's possible to open or close a connection of S-Web-Connect (WebConnect 2.x) to a PCD with the use of a URL address:

To change the state of the connection of S-Web-Connect you can use the following URL:

If the CE panel is rebooted the configured stations in SWebConnect get lost.

Problem
After a restart or reboot of the CE panel the stations configured in SWebConnect get lost .

Reason
The stations are only saved after a timeout of 2 minutes (120 000 ms) or if SWebConnect is closed before shuting down the panel.

Solution
Close SWebConnect before shutting down the panel or make the timeout shorter (p.ex. 1sec). This can be done in the SWebconnect.settings.xml file.

<?xml version="1.0" encoding="utf-8"?>
<scssettings version="1.0">
<components>
    <component id="SaiaBurgess.SCS.Configuration">
            <configuration_settings autoUnloadTime="120000" />
    </component>

The value has to be >=1  

The S-WebConnect 2.x (distributed together with PG5 1.4.300) does require the Microsoft .Net Framework 2.0. If the .Net Framework is not installed the S-WebConnect 2.x fails to start.

Symptom
When trying to lauch the S-WebConnect 2.x distributed and installed together with PG5 V 1.4.200 (or PG5 1.4.300) it does not start. Instead an window with the content "SWebConnect.exe - Application Error: The application failed to initialize properly (0x0000135). Click on OK to terminate the application" appears.

Reason
The S-WebConnect 2.0 requires the Microsoft .Net Framework 2.0. In case the framework is not installed, the S-WebConnect fails to start.

Solution
Install the Microsoft .Net Framework 2.0 or later. The installer for the .Net Framework 2.0 is called "dotnetfx_2_0.exe" and can be found on the PG5 1.4.300 CD in the folder "PG5\Windows\".

The default web page of the PCD "variable list" does need a java applet (varlist.jar). This applet is not located on the PCD by default and therefore it isn't possible to display the variable list on the browser.

Symptom
Instead of showing the "variables list", the browser just remains white and the error message "Applet varlist notinited" is displayed in the status bar of the browser (see screenshot below). The problem only occurs when beeing online using http-direct (WebConnect does install the "varlist.jar" by default in the folder C:/WebPages).


Reason
To be able to display the web-server variable list on a http direct connection, you need to store the java applet varlist.jar either on the PCD. The default page "Variable List" (varlist.htm) does only call this applet, but the applet is not stored in the PCD by default.

Solution
Store the "varlist.jar" on the PCD. The following locations are possible:

• If a flash module dedicated to file system is present, the applet "varlist.jar" can be stored on this module in the folder "xx_FLASH/WEBPAGES/"
• Or the "varlist.jar" can be added to the PG5 Web-Builder file of the project

If you have installed Web-Connect SW on the PC then you can copy the file varlist.jar from the folder C:\WebPages\. If you don't have installed the Web-Connect SW then you can download the varlist.jar from this FAQ.

Yes, this is possible. In the modem settings there is the option "auto disconnect after x minutes". Just below there is a radio button with the choices "when idle" or "always, do not reconnect"

Reason for this option
The option discussed in this FAQ can be very useful to avoid outrageous telephone bills due to a forgotten browser window that is online with a remote PCD.
By default, the WebConnect is disconnecting the line after 3 minutes the line is in idle (which means no data is transferred). Because a Web Editor project does refresh its content automatically, the modem would never disconnect. The result is that the line stays connected until someone does close the web browser. If the user forgets about this, he'll be surprised the next time he opens his phone bill...

Configuration
In order to force the WebConnect to disconnect a modem connection to a PCD after a certain time, chose the option "always, do not reconnect" in the modem settings window:
§ix100398§
The disadvantage of this setting is that the line will be disconnected also if the user would like to stay online longer than the configured time. In this case he has to re-connect to the page.

It's possible to close a modem connection of a S-Web project with the use of special URL link. this FAQ is valid for WebConnect 1.x.

If it's necessary to close a modem connection of a S-Web project on the Web-Browser directly on the web page which was created with the S-Web editor then on the S-Web editor you have to define a button with the action "URL-Jump".

As URL you have to use the name:

/setup?page=mainsetup&btn=disconnect&oname=STATION_NAME

where the name "STATION_NAME" have to be replaced with the name of the station which was defined on Web-Connect.

On the example below the station name was modem.

Please note that after the disconnection of the modem communication no more data are updated on the Web-Browser.

The example project is stored in FAQ #100567

The Web pages loaded on a PCD are displayed properly but the variables valus are missing! The Java consol in Internet Explorer doesn't managed to open the file xxx.ITQ, the following error message appears: Parse Tek file error, first jar should be C, D or E but it is .....

In this case, a run off version of an antivirus was creating the problem:

Anti virus Cilling version 12 on a PC with Window XP

After stopping this anti virus the problem is solved!

The problem can have different causes, see also the link below!

The PG5 Controls suite is only available for Windows OS. But a software like e.g. WMWare can be used in order to install Windows on a Linux machine. This allows to use PG5 on the Linux machine (running in the emulated Windows environment).

Since the functionality of PG5 in such a situation is depending on the base functionaliy of the combination VMWare/Windows, we cannot guarantee the proper functionality of all the PG5 Controls suite tools.

The following applications have been tested and were found working properely with VMWare Workstation 5:

• PG5 (online connections tested: USB, Ethernet, RS232)

• Fupla

• Graftec

• SEdit

• WebConnect

Since the Windows environment is not directly accessing the hardware of the PC, a reduction of performance is to be expected.

Yes, the port number can be changed! After starting the WebConnect-SW an icon appears in the Task bar of your Windows-OS. Double-click on this icon and change to tab "Server Port" of the appearing window "Server Options" where you can change the Port.

Normally HTML-request are sent via Port 80 and therefore the Port number shouldn't be changed! If you change it for some reason anyway, you have to extend the URL with ":<Port number>". E.g.: If you changed the Port number as described from 80 to 81and the URL was before 127.0.0.1/PCD/start.html, the URL must now be 127.0.0.1/PCD/start.html.

It is recommended to use the Sun "Java(TM) 2 Runtime Environment, Standard Edition 1.4.2_04" (or higher) that comes along with the PG5 CD. The Java(TM) Plug-in installation file is located in the folder "S-Web/Java Runtime Environment" on the Saia PG5® Controls Suite CD (PG5 CD).

In the first official version of the Web Editor it is possible to generate files having spaces in their names. This causes problems while accessing these files on the PCD.

The results when trying opening these files are either a "no response" of the WebConnect or a "This page can not be displayed" of the Internet Explorer.

If the whole web project created with the Web Editor has a name containing space character, most files of this project will have the same name by default.
Since in this case most files have to be renamed, it isn't recommended to provide names with spaces to Web Editor projects.

The files that cause problems are listed below together with a short description of the results they cause:

In order to get a working Web Editor project the files listed above mustn't contain any space characters!

In future versions of the Web Editor it won't be possilbe any more to introduce space characters into these file names.

It's possible that on WIN-XP Systems the IIS (Internet Information Service) does use the port 80 and will answer to all requests on this port.

Stopping the IIS does allow to use the SBC Web-Connect SW correctly.

If after the start of the SBC WebConnect SW on a WIN-XP PC the message below appear on the screan, then it's possible that the problem is related with the use of the IIS (Internet Information Service) on this PC.

The IIS is a Web-Server service which runs on the PC and does use the port 80 (same port as used from the WebConnect SW). If ISS is running then it's not possible to use the Web-Connect SW on the port 80. You have to stop the IIS to be able to use the WebConnect SW.

To know if the IIS run's on the PC make the follwoing steps:
- Start the Web-Browser
- Set the address to 127.0.0.1
- If the following screen appears then the IIS is installed and runns on the PC.

To stop the IIS:
-  Click on "start", "settings", "control panel"
-  Select "Adminstrative tools"
-  Select "Internet Information Services"
-  Select "Your computer name", "Web-Sites", "Default Web-Site"
-  Now you can stop the IIS by selecting the Stop button (See picture below, marked with red circle)

-  The stopped service is marked as stoped.

By placing files in the local folder of the PC or PC's where WebConnect is running, you can optimize the performance of the Web application.

General
The SBC.Net S-WebConnect software is a free software (provided with the PG5 Controls Suite) which allows accessing the Web Server of PCD systems which do not support "http-direct" (direct access to the Server over TCP/IP). Beside the "translation" from http to e.g. Ether-S-Bus, the S-WebConnect can also be used to store files directly on the PC running the S-WebConnect. Because these files do not need to be transferred from the PCD, the performance for serving these files can be increased significantly.


Files to be placed in the PCD
The following files must be placed in the PCD. Note that these files must be part of the WebBuilder file in the PG5 project.

• *.tcr file (if the S-Web Editor is used). This file contains the PCD ressource list to be read.
• All *.htm/*.html pages containing tags for reading PCD ressources. Also these files need to be part of the WebBuilder file.
• Recommended: start.htm (if the start.htm file is not stored on the PCD, the search option "Local then PCD" (see screenshot below) of the S-WebConnect must be selected; otherwise the default page from the PCD firmware is displayed).
  

Files that can be placed in the local folder on the S-WebConnect PC
In general all files except the above mentioned can be stored in the local folder of the frontend PC.

Hint
In case several sub stations do contain different files, these files can be stored in a sub-folder of the C:\WebPages. In this case, the sub-folder must have the same name as the station configured in S-WebConnect  (in the example above this would be PCS_WebServer). Please note that S-WebConnect version 2.0.x.x or higher is required for this feature.

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.

Yes, the product Saia PCD® COSinus (PCD8.DNET-SUITE) does also contain the SBC S-Bus libraries (S-Bus Master and/or S-Bus Slave) based on the Microsoft .Net framework.

How is the Saia PCD® COSinus structured?
The Saia PCD® COSinus contains different components (S-Bus Master, S-Bus Slave, an interface for CGI calls to the PCD Web Server etc.) for easy integration of the communication interface for PCD systems into Windows applications. All the components are based on the Microsoft .Net framework.

This product (PCD8.DNET-SUITE) does contain the required libraries, documentation, examples (programmed in C#, C++ and VB) as well as access to updates and new features.

How do I get the Saia PCD® COSinus Suite?
The Saia PCD® COSinus Suite is an official product from Saia-Burgess Controls AG and can be optained from your local SBC representative (or support@saia-pcd.com)

Remarks

• The product Saia PCD® COSinus can't be found yet on the support homepage www.sbc-support.ch (the TI will be uploaded soon).
  
• The Saia PCD® COSinus suite is the replacement for the inofficial SCommDll toolkit which has been available until November 2007. The SCommDll toolkit is discontinued and is no longer available.
  

In PG5 2.3.175, due to a bug in Web-Editor8 when compiling the Web-Editor8 project (as HTML5 or Hybrid solution), all horizontal and vertical lines of the Web-Editor project were ‘crooked‘ by 1 pixel and this information was stored in the Web-Editor project.

The bug was fixed in PG5 2.3.192 but unfortunately Web-Editor projects compiled in PG5 2.3.175 as HTML5 or Hybrid solutions, have to be reworked manually in PG5 2.3.192 (or newer).

The information about the issue and how to solve the issue is described on the attached document on the chapter ‘Web-Editor8; Horizontal and vertical lines are displayed with an offset’

Due of an error on PG5 2.3.192, the Web-Editor login macro does not work well if the web page is displayed on SBC Microbrowser Web-Panels or Windows Microbrowser App.

The issue is fixed on PG5 2.3.193

If on the Web-Editor8 included in PG5 2.3.192, an ifCondition statement was used on the function editor, then the ifCondition was not behaving correctly and does not correctly execute the code on the condition.

Such ifConditions statements are used very often on our Web-Editor macros, for example on the login macro.

Issue happens only on Web-Editor project which were compiled with PG5 2.3.192 and if the web-pages are displayed on Microbrowser runtimes (SBC Microbrowser web-panels or Windows Microbrowser App)

There is no issue if the web-page is displayed as HTML5.

To solve the issue, use PG5 2.3.193 or a newer version of PG5.

Since early 2018, Apple and Android have changed the rules for the checking the licensing of their Apps. If the device is not connected to Internet for a period of time, the license on the device is disabled and it’s no longer possible to use the App until the device is reconnected to the Internet/App store and the device is re-licensed.

An Error message will be displayed.

Unable to Verify App
A connection to the App Store is required for the first launch of ‘SBC Micro Browser’ on this iPad.
Please connect to the internet and try again.

Before 2018 it was possible to install and license once the application on the devices and then operate the devices without Internet connection in offline mode.

Since early 2018, the device needs to connect from time to time to Internet to verify the license on the App store.
If this check is not performed in a regularly, then the license on the device will be disabled and it will be no longer possible to use the App until the device is connected again to Internet/App store and the device is relicensed.

This are Apple/Android rules over which SBC has no control.

To solve the issue:

For Android and iOS devices:
The Web-Editor 8 which is included in PG5 2.3 (or newer) allows the generation of HTML5 compatible web pages.
To avoid this problem, the web pages stored in the PCD can be displayed in a 'standard web browser' in HTML5 format on the Android or iOS device instead of using an MB app.

For Android devices:
Status august 2018: not possible to use the MB-App for longer time in Offline mode:
SBC will provide an MB-App that allows the Android devices to run in offline mode without Internet connection.
This FAQ will be updated as soon as the new version of the MB-App will be available.

For iOS devices:
Longer use of the MB-App on the devices in offline mode without an Internet connection will remain not possible.

It could happen that the message 'File not found' is shown on the microbrowser app on your smartphone/handheld when trying to display the web-pages stored on the PCD.

When you make frequently logs and create a file only every week it is possible that you get the message “File is too big for the heap” on the Micro Browser App on the Android smartphone/tablet.

It's possible to increase the Heap by modifying the file uBrowser.xml which is stored on the smartphone/tablet.
To do this connect the smartphone to the computer and export all config files with the app menu button (Options-> Export Files to SD card).
The config files are saved in the internal flash in the folder “Download”. 
Take the file uBrowser.xml and copy it to the computer, open the file and mofify the parameters.
After that save the file in the same folder “Download” of the smartphone and import all config files with the app menu button (Options-> Import Files from SD card) 
For info, since V.1.5.15.131 (26.04.2013) of the Micro Browser App, the default heap sizes are defined like that:

// Heap for memory allocation of painter objects
#define MYHEAPSIZE1_KB          2048
// Heap for memory allocation of HTML tags and CO
#define MYHEAPSIZE2_KB          2048
// Heap for Macro Offline Trends and HDLog Trends (4MB instead of 1MB)
#define MYHEAPSIZE3_KB          4096
// For Macro online trends (4MB instead of 1MB)
#define MYHEAPSIZE4_KB          4096

Yes, it is available under:

play.google.com/store/apps/details

In a usual Web-Browser (IE, Firefox, Chrome, Safari etc.) running on a PC, the content of the PCD WebServer is displayed by simply typing the IP-Address of the PCD into the URL field. With iPad-, iPhone-, iPod- and Android Apps, the procedure is slightly different.

With iPad-, iPhone-, iPod- and Android Apps it is mandatory to type as well "http://" before the IP-Address of the PCD.

No, for PCD3.T665/T666/T668 devices, it is not possible to define own FTP users, the Service key and the web-server password on the PG5 device configurator.

It’s possible to access to the PCD3.T665/T666/T668 with FTP by using the default FTP user and password.

In some cases, it’s possible that the PG5 Update manger is not able to connect to the server and on the PG5 Update manager the following information is displayed:

‘An error occurred during the connection to the sever’

A modification on the configuration file should fix the issue.

Error description:

In some cases, it’s possible that the PG5 Update manger is not able to connect to the server and on the PG5 Update manager the following information is displayed:
‘An error occurred during the connection to the sever’

Solution:

To solve the issue perform the following steps.

Close the PG5 update manager.

Open with a text editor the file:
c:\Users\my_name\Documents\SBC\PG5 Update Manager\DataBase\FileLocation.xml

Search at the end of the file the string:

'tuple namespace="UpdateWebServiceSoap" localname="Main" base="Absolute" uri="https://update.dev.saia-pcd.com/UpdateWebService.asmx" /'

Remove the .dev syntax from the URL so that the string looks like this:

'tuple namespace="UpdateWebServiceSoap" localname="Main" base="Absolute" uri="https://update.saia-pcd.com/UpdateWebService.asmx" /'

Save the file and restart the PG5 Update manager.

If the error persists then please check:

1.
That the correct FileLocation.xml file was modified.

File which need to be modified is stored here:
c:\Users\my_name\Documents\SBC\PG5 Update Manager\DataBase\FileLocation.xml

You don’t have to modify this file:
c:\Users\my_name\SBC\PG5 Update Manager\DataBase\FileLocation.xml

2.
If the folder c:\Users\my_name\Documents does not exist on your PC,
then it could be, that you are using a mirror software like for example OneDrive to mirror the content of the ‘Document’ folder to the cloud.

In this case search the location of the ‘Document’ folder used by the mirror software and there you should find the FileLocation.xml file

Example of possible paths:
C:\Users\my_name\OneDrive\Documents\SBC\PG5 Update Manager\DataBase\FileLocation.xml or C:\private$\home\my_name\Documents\SBC\PG5 Update Manager\DataBase\FileLocation.xml

You can search for the file FileLocation.xml and modify the file which is stored on the path: …\....\Documents\SBC\PG5 Update Manager\DataBase\FileLocation.xml

Unfortunately, the e-mail forwarding service offered by SBC is currently not available.

For this reason, it is currently not possible to send e-mails from Saia PCD via Hostpoint.ch.

We are working to make the service available again as soon as possible.

In the meantime, please use other alerting channels if necessary.

We regret any inconvenience caused.

-----------------------------------------------------------------------------------------------

Update on 08.04.2020:

The e-mail forwarding service offered by SBC is available again.

Means that it’s again possible to send e-mails from Saia PCD via Hostpoint.ch.

Due of security reasons, we were forced to change the location of the PG5 Update manager server from:
the old PG5 Update manager server: http://update.sbc-support.ch
to a new PG5 Update manager server: https://update.saia-pcd.com

Detail information:

The url to access the PG5 update manager server is hardcoded in the PG5 update manager application running on your PC and all PG5 update manager applications with versions < 1.6.0.12 access the old server, where all version >=1.6.0.12 access the new server.

All available PG5 and Firmware updates for PG5 2.1, 2.2 and 2.3 are now stored on the new server https://update.saia-pcd.com

On the old server http://update.sbc-support.ch there is ‘only’ an update of the PG5 update manager application.

Until the old server is running, then all access from PG5 update manager application (with version < 1.6.0.12) of PG5 2.1, 2.2 and 2.3 will point to the old PG5 update manager server and will allow the user to download the new PG5 update manager application.

But it could be, that in the future the old PG5 update manager server is no more available and this fact could lead to the situation, that some PG5 2.1, 2.2 or 2.3 versions are no more able to access to the new PG5 update manager server because the PG5 update manager application on the PC was not updated to a PG5 update manager application with version >=1.6.0.12

Error description:

In such a case the following error message would be displayed on your PG5 update manager

Can’t connect to the server.
Check your connection to the server.
Current Uri: https://update.saia-pcd.com/UpdateWevService.asmx
or
The server return an exception.
Try again later and if the error persists, contact SBC-Support.

Solution:

To be again able to access with your PG5 update manager application of your PG5 2.1, 2.2 or PG5 2.3 to the PG5 update manager server it’s necessary to perform the following steps:
1.
Open Control Panel, then Programs and Features
Select the PG5 Version (i.e PG5 Suite V2.2.230), then Press “Change Button”
Uninstall all update managers of PG5 2.1, 2.2 and 2.3.
 

2.
Select “Modify” Option, then press “Next”
 

3.
Uncheck “Update Manager” CheckBox, then press “Next” and Continue

4.
Do the same for each installed PG5 Version >= PG5 2.1

5.
Install Standalone Version 1.6.0.12 (or later) of Update Manager

 
The Setup “Setup PG5 Update Manager.exe” is stored on the support homepage as part of PG5 2.3:
https://www.sbc-support.com/en/software/saia-pg5r-controls-suite/saia-pg5r-23-suite/parts-of-pg5-23-suite/

Since February 2018 PG5 2.3 is available on the support site for download.

This FAQ features a short summary of the arguments for PG5 2.3 and shall help to decide whether to work with PG5 2.3, 2.2, 2.1, 2.0 or with PG5 1.4.

Introduction

PG5 2.3. is based on PG5 2.2 and is a extension of PG5 2.1.

In PG5 2.0 major improvements have been made in the user interface, symbol management, symbol editing and device configuration.

Due to the important innovations and the Microsoft .Net Framework as base of PG5 2.0, the upgrade step from PG5 1.4 to PG5 2.0 is substantially more important than for example, an update of PG5 1.3 to 1.4. Therefore it is strongly recommended to read the "What's new" document in the PG5 2.0/PG5 2.1/PG5 2.2/PG5.2 section on the support site carefully before starting to work with PG5 2.0/PG5 2.1/PG5 2.2/PG5 2.3.

In general, new features will only be implemented in PG5 2.3 but no longer in PG5 2.2, PG5 2.1, PG5 2.0 and PG5 1.4.

Shall I use PG5 2.3, PG5 2.2, PG5 2.1, PG5 2.0 or PG5 1.4 for my next project?
We recommend using PG5 2.3 for new projects in order to profit from new functionalities.
Since PG5 1.4 will be further available as it is, no reason exists to convert all existing projects immediately.
PG5 2.0 PG5 2.1 and PG5 2.2 projects can be used in PG5 2.3 (but it's not possible to re-use PG5 2.3 projects in PG5 2.2/2.1./2.0)

New features of PG5 2.3.113 (first official release)
The following short list gives an overview of the new features and improvements which have been realized in PG5 2.3:
Detailed information could be found on the support page, section PG5 2.3 New features or on the document "What's new on PG5 2.3 (available in English, German and French) also on the support home page:

Fupla:

• Symbol Editor completely rewritten to allow a easier and faster Symbol handling
  
  • Easier dragging from symbols to FUPLA from anywhere on the line
  • Better performance
  • New ways to create multiple symbols at once
  • New multi-edit features
  • Group Comments
  • New Quick Search for symbols
  • New Filter options
  • Improved Symbol Error detection
  • Undo / Redo for all symbol operations

  
  

• Symbol import conflict resolution window for more control when importing symbols
  
  • Shows conflicts when importing symbols from Text (Excel etc.), or from files
  • Conflicts can be detected based on names or adresses
  • Symbols can be edited to resolve conflicts

  
  

• New adjust parameter window for speed up commisioning
  
  • Combines the best out of the old and new adjust parameter window
  • No open or close, information's are automatically displayed when you select a new FBox
  • Directly edit Online Parameters (saves a lot of mouse clicks) while keeping the original source values
  • History of changes can be displayed from the FBox
  • Possibility to hide parameters like BACnet options

  
  

• New Template Import for speed up PLC programming
  
  • Way faster import of templates
  • New possibilities for Indexing (Absolute / Relative)
  • One place to do Find & Replace for all tabs

Web-Editor8:

• Generation of HTML 5 compatible web pages

  • Generation of HTML5 output from existing SBC Web Editor projects
  • Projects are up to date with latest browser technology
  • Possibility to generate from Web Editor8 Java, or HTML5 or Java and HTML5 compatible web pages

Improvements:

Device Configurator:

• New devices
  The following devices have been integrated into the Device Configurator:
  
  • PCD7.LRL2-P5:        Programmable Room Controller with 16 I/O's 2 x RS485
  • PCD7.LRL4-P5:        Programmable Room Controller with 24 I/O's 2 x RS485
  • PCD7.LRL5-P5:        Programmable Room Controller with 24 I/O's 2 x RS485
  • PCD7.LRS4-P5:        Programmable Room Controller with 14 I/O's 2 x RS485
  • PCD7.LRS5-P5:        Programmable Room Controller with 14 I/O's 2 x RS485

FBox libraries

• Standard Alarming FBoxes
  
  • Alarming Improvements for Standard & DDC Suite FBoxes in that way, that no manual creation of files needed anymore
  • New Alarm List Advanced FBox to provide all nessecary Informations to send out Alarms via Email, SMS etc.
  • New Alarm FBoxes with the possibility to use PCS, define Alarmtexts and Groups, Prio directly in the FBoxes
  • Processes Alarm state changes from DDC Suite and Standard Alarm FBoxes and puts them into a queue for sending them out via Email, SMS
  • Several options to filter for Group, Prio
  • Alarm Format format can be adapted to customer needs

  
  

• DDC Suite System Alarm FBox
  
  • Automatically detect Alarms in the referenced Systems (AHU01,AHU02 etc)
  • Possibility to define Groups and Priorities
  • Automated collective Alarm for complete systems without placing any additional FBox like OR
  • Acknowledge Alarms per System

  
  

• New Enocean EEP Profile FBoxes
  
  • With the new set of EEP FBoxes you can use every Enocean Device that is compliant to a EEP Profile
  • No dedicated FBoxes for devices are needed in future
  • Easy configuration for different type of devices inside of the FBoxes

  
  

DDC Suite

• News
  
  • Support for BACnet Rev. 14. - projects can be easily upgraded
  • Support for Alarming 2 with Groups & Priorities
  • Fast and easy engineering with 38 predesigned templates for FUPLA, Web & Visi.Plus
  • Templates for AHU incl. Humidification, Dehumidification, Air Quality etc.
  • Automatic sending of Alarms via SMS, Email without engineering effort

And other improvements and bug fixes

New features of PG5 2.2.130
The following short list gives an overview of the new features and improvements which have been realized in PG5 2.2.130:
Detailed information could be found on the support page, section PG5 2.2 New features or on the document "What's new on PG5 2.2 (available in English, German and French) also on the support home page:

Windows Start menu

• In the Windows Start menu, the Saia PG5 version 2.2.130 applications are accessible directly under the folder ‘PG5 Suite V2.2.130’ and no more under the folder ‘Saia Burgess Controls’.
  This change has been made in order to be compatible with the Windows 10 start menu that’s accept only one level of folder.

Device configurator:

• PCD3.M3160: Power CPU with 512kByte program memory, 128MByte intflash, USB, Ethernet, 4 IO slots not expandable
• PCD3.M3360: Power CPU with 512kByte program memory, 128MByte intflash, USB, Ethernet, 4 IO slots, expandable up to 64 IO modules.
• PCD3.M5360: Power CPU with 2MByte program memory, 128MByte intflash, USB, Ethernet, RS-232, 4 IO slots, expandable up to 64 IO modules.

Fupla:

• Status indicators of unconnected FBox binary outputs in online mode.
• Probe format of binary connections is automatically defined.
• Double click for defining a new connection from an FBox input/ouput or a connector in selection mode.
• Several corrections in the online mode for indicating the correct states and values.
• Several corrections in the handling of adjust parameters.
• Possibility to connect register float to register input of an FBox.
• Various other corrections.

Web templates and Web Editor 8:

• New templates for the E-Line RIO modules.
• Various corrections in the web templates for user management and trending and also in the Web Editor 8.

Wiring Check Tool:

• Support for the 3 new PCD3 power CPU.
• Support for the PCD1.M2220-C15 E-Line CPU.
• Support for the programmable E-Line modules – PCD1.F2611-15, PCD1.G1100-C15, PCD1.G3600-C15, PCD1.G3601-C15, PCD1.W5300-C15.
• Various corrections.

New features of PG5 2.2.100 (first official release)
The following short list gives an overview of the new features and improvements which have been realized in PG5 2.2:
Detailed information could be found on the support page, section PG5 2.2 New features or on the document "What's new on PG5 2.2 (available in English, German and French) also on the support home page:

• Improvements of Fupla
  - New internal structure
  - Undo/Redo
  - Page edition and graphical interface
  - Find and replace
• Web Editor 8.0
  - Multipage templates
  - Support of SVG pictures
  - Rotation of pictures
  - Run button
  - New web-templates
• BACnet Exlporer BACeye
• Wiring check tool
• Support of new devices like  
  - PCD1.M2220-C15:   E-Line CPU with 2 slots for IO or communication modules.
  - PCD2.M4160:          CPU with 4 slots for IO or communication modules.
  - PCD2.M4560 :         CPU with 4 slots for IO or communication modules and connector for extension
                                    modules. 

And other improvements and bug fixes

New features of PG5 2.1.310

• Project Manager:
  A warning is displayed when opening a project made with an older version of PG5.

• WebEditor 8:
  Contains all the corrections done in the patch 1 for PG5 2.1.300, especially concerning the templates where the format, min and max value are now correctly added to the project.
  The object that serves as reference when doing align operations has a different selection outline color.
  Several bug fixes to improved stability and correctness over the whole application.

• Fupla:
  Improvements in the ‘Update FBoxes’ procedure:
  for a lot of FBox, the automatic update was not possible and the message ‘Invalid structure, please review the structure and make enough place around the FBox’ was displayed.
  For such cases, the function has been improved and the update will occurs automatically.
  The function ‘Create FBox from Page’ correctly creates the FBox.

• Symbol Editor:
  In some special cases, it was not possible to drag & drop symbols to the Fupla page. This issue has been corrected.

• BACnet Configurator / Compiler:
  The function ‘Upload/Merge’ is now working correctly.

And other corrections.

New features of PG5 2.1.300

• Updated user interface, help, FBox libraries and documentation
  The Saia PG5® Suite has been updated according the new company logo and the new product names.
  New ‘SBC’ installation folder name and ‘SBC’ folder for the projects and libraries
  
  
• WebEditor 8
  New translation editor in order to easily handle multi-language web projects
  Enhancements in the ‘Library’ window
  Possibility to define default fore-/background view at project level
  
  
• Device Configurator:
  Support new IO modules   
  - PCD2/3.W380
  - PCD2.G200
  - PCD7.W600
  - PCD7.R610
  
  
• Fupla
  Define groups and separators in the Page Navigator view
  Several enhancements to the ‘Page Import’ feature
  
  
• Cross-reference
  The ‘Cross-reference List’ window now shows the symbols used in the BACnet Configurator,
  the Web Editor 8 and the symbols defined in the LON Configurator
  
  
• Library Manager
  Possible to copy only the actually used libraries into the Project folder
  
  
• HTTP Downloader
  Support of ‘Service Key’ and download over portal – HTTP reverse

And some other improvements and bug fixes

New features of PG5 2.1.210 (Patch 1 of PG5 2.1.200)
Projects done with the version 2.1.200 will be fully compatible with the version 2.1.210.
The following new features and modifications have been implemented in the patch 1 for PG5 2.1.200:

• Project Manager
  - RIO and device names can now begin with a digit
  - In the TCP/IP setting table, device is not shown if Ether-S-Bus is disabled
   
• Device Configurator
  - Corrections in Ethernet configuration for PCD3.M6860 and in media mapping for the PCD2/3.H222
   
• Web Editor 8
  - New Templates DDC Suite 2.0 (Italian) and DDC Suite 2.5 (German / English)
  - Update of Icon Gallery from version 2 to 3
  - New string operations
  - New IMaster SBC 5.15.02: 
    Since the latest Java update from Oracle ( 1.7.0.25-b17) a warning appeared (“missing permission”)
    when a Web-Editor page is displayed in the browser.
    With the new IMaster 5.15.0229 it is fixed. 
    This new IMaster is compatible with Web Editor 5 and the new Web Editor 8.
  - Fixes issue where:
    - 'Show View' in a WE5 project could wrongfully be imported as Jump Back action
    - condition priority was incorrectly compiled
    - Variable format, min and max values are now correctly added when inserting a template
• Fupla
  - Does not crash when clicking on DDC Suite BACnet FBoxes
  - On low memory platforms, adding template does not remove existing Fupla pages
  - Correct an issue concerning counter in ladder diagram
  - For non NT-PCD's, Online values of connections between F-Boxes are set in a randomly way. FAQ101859
• Graftec
  - External symbol declarations are correctly defined in Graftec files
• Assembler
  - Time types, for example ‘T#123s’, can now be ‘public’
  - Predefined max number of flags is now 8191 for PCD2.M170
• HTTP Download
  - Allow support for web server and user key protection mechanism
• DDC Add-on
  - Allow updating BACnet configuration without erasing the clients object
  - Some adaptations regarding the scheduler object
• PG5 Project Generator
  - The PG5 project is now restored when the project update is cancelled by the user.

And some other improvements and bug fixes

New features of PG5 2.1.200
The following new features and modifications have been implemented in PG5 2.1.200:  

Since PG5 2.1.200 the Device Configurator has been adapted following the protection rules for PCDs that are accessible over Internet.
To prevent unwanted access to PCD data and files, default settings and password specifications for the Web Server and the FTP Server have been modified.
The following IP-protocols are disabled by default on the deivce configurator of new PG5 projects:
- S-Bus over TCP/IP
- FTP
- HTTP (Web-Server)

PG5 projects made with precedent version of PG5 2.1 are upward compatible with PG5 V2.1.200, but not back again
Once a project has been opened with PG5 V2.1.200, it is not possible to open it again with the previous versions.
As this new version contains no major changes regarding the project structure and files structure, including WebEditor8, we recommend upgrading PG5 2.1 to version 2.1.200.

• PG5 Device Configurator
  - The following IP-protocols are disabled by default on the deivce configurator of new PG5 projects:
     - S-Bus over TCP/IP
     - FTP
     - HTTP (Web-Server)
  - The user has to turn on the appropriate IP protocols deliberately in the Device Configurator and possibly
     activate the passwords for the access protection.
  - The current FTP standard user "root" with the associated password is no longer enabled by default.
  - A new service key which facilitate and secures the access for example of the Web editor 8 to the PCD.
    The service key replaces the FTP username and FTP password and the web server password.
  - IP filter which allows filtering of incoming IP packets 
    The filter allows to define which IP addresses are allowed to access the PCD or for which IP addresses
    the access to the PCD should be forbidden.
  - Easy definition of indexed symbols in Symbol view on the media mapping
  - Export of Device Configurator information towards Excel Files
    PCD3.Mxx60: Media Mapping for Interrupt Input
• WebEditor 8
  - Role-based user management and access control with with a simple user identification template
  - Download of Web-Editor 8 projects to password protected PCD
  - Find usages of functions, conditions PCD and internal variables in the whole project
  - Renaming variables in the whole project
  - Easy editing of elements without touching the mouse
  - Displaying HDLog trends as discrete (binary) curbe
  - New actions and bit comparison.
• Project Manager
  - The Backup and Restore features have been improved for better handling of project containing
     Smart RIO networks, backup/restore of Common Files, and to backup selected devices instead of the entire project
   
• Project Generator
  - Predefined Templates
  - Import of On-board module I/O symbols and multiple Media Mappings
• Fupla
  - Update all FBoxes in one Fupla File
  - In the ‘Page Navigator’ view, it is possible to assign a color for the each page
  - FBox ID 
    In the new DDC suite 2.5 suite, the BACnet configuration is generated from the FBox in using a unique
    FBox ID as link between the FBox and the generated BACnet object
   
• FBox libraries
  - IP-Filter FBoxen allowing access to the IP filtering functions at runtime
  - Free generation of building ID keys in FBoxes for BACnet and alarming
  -  ‘Summer time’ which indicates winter or summer time
  - Parameter settings for DALI devices
  - Corrections on several F-Boxes

New features of PG5 2.1.100.100 Patch 1
The following new features and modifications have been implemented in the patch 1 for PG5 2.1.100:  

• Web Editor 8.0
  - Help is now available in German and French
  - Images used in foreground, background or embedded views are now correctly shown.
  - Changing download options no longer forces rebuild
  - Changing bar graph grow direction from horizontal to vertical or vice versa also flips width & height
  - Over 40 other stability, usability improvements and bug fixes.
• Fupla
  - The 'Replace' function replaces now all adjust texts.
  - Pressing the 'Ctrl' + Space key in a connector for editing symbol show correctly the window for choosing existing symbols.
  - Template libraries done with older version are correctly restored.
• LON IP
  - The generated configuration is now correctly handled by the PCD.
• HTTP Download
  - It is now possible to download the program into the ‘INTFLASH’.
• Ethernet RIO
  - Support for COSinus version 1.20. This will allow the use Ni 1000 L&S sensor on PCD3.T665/6.
• DDC Add-on
  - The alarm texts are also generated for the Web Editor 8
• Project Generator
  - Add standard templates for an easy import from the 'PCD Konfigurator' tools.
• And some other improvements and bug fixes

New features of PG5 2.1.100 (first official release)
The following short list gives an overview of the new features and improvements which have been realized in PG5 2.1:
Detailed information could be found on the support page, section PG5 2.1 New features or on the document "What's new on PG5 2.1 (available in English, German and Frech) also on the support home page :

• Update Manager
• Web Editor 8.0
• Project Generator - Excel-Import
• Improvements of Fupla
  - Cyclical transmission of S-Bus telegrams
  - HTTP file transfer library
  - Display the history of Adjust window
  - S-Monitoring library
  - IP address to text conversion FBox
• Improvements on the Device Configurator
  - Support for Ni 1000 L&S temperature sensor
  - Monitoring and logging of meter data
• Support of new devices like  
  - PCD7.D457VT5F: 5.7’’ programmable panel
  - PCD7.D410VT5F: 10’’ programmable panel
  - PCD7.D412DT5F: 12’’ programmable panel
  - PCD3.M6860: controller with 2 Ethernet interfaces
  - PCD1.M0160E0: e-controller
  - PCD1.M2110R1 room controller
  - PCD1.M2160: PCD1 controller
  - BACnet MSTP module PCD2.F2150 and PCD3.F215
  - LON TP/FT-10 module PCD2.F2400 and PCD3.F240
• Flag and register extension to 16384 flags and 16384 registers (requires firmware 1.20.25 or later)
• Download backup file via HTTP
• Download in Run for PCD1.Mxxx0 and PCD3 +
• MIB File Generator for SNMP
• New User licensing and developer registration

New features of PG5 2.0.220 
The following new features have been implemented in PG5 2.0.220:

• New FBoxes for the new PCD7.L79xN
• New FBoxes for EnOcean devices from Sensortec
• The EIB/IP driver now allows modifying the IP address of the gateway in runtime
• S-Web Editor has been updated to version 5.15.0221

New features of PG5 2.0.210 
The following new features have been implemented in PG5 2.0.210:

• Support of the PCD1.M2160

New features of PG5 2.0 Service Pack 2 (PG5 2.0.200)
The following new features have been implemented in PG5 2.0 SP2:

• Support of smart Ethernet RIO PCD3.T665|T666
• Device Configurator: New media mapping window for all I/O slots
• New FBox classification according functionalities in Fupla
• Fupla Unicode support for Russian computers
• Web-Editor Release 5.15.02
• Full support of 64 bit Windows systems

New features of PG5 2.0 Service Pack 1 (PG5 2.0.150)
The following new features have been implemented in PG5 2.0 SP1:

• Support of up to 14335 flags for PCD3 and PCD2.M5 (requires firmware 1.14.23 or later), see FAQ 101447
• The FTP Server, S-Web Server as well as IP Enhancements (DHCP, DNS, SNTP) can now be configured directly in the Device Configurator (requires firmware 1.14.23 or later), see FAQ 101464
• Support of new hardware (PCD1.M2120, PCD3.Mxx60 and Bluetooth modules (PCD2/3.F160 and PCD2.F2/3.F2xx equipped with a F160)
• Improved German help texts in the Device Configurator

New features of PG5 2.0.110 (first official release)

The following short list gives an overview of the new features and improvements which have been realized in PG5 2.0:

• Improved user interface with Desktop docking and Multi Document Interface
• Hardware configuration with Device Configurator
• New Symbol handling and Excel-like Symbol Editor
• New FBox properties window for fast editing
• IL Editor with FB and CSF selector analogue to the FBox Selecor in Fupla
• Graftec supports templates
• Library Manager for organizing the libraries used in the project
• Watch window with trending functionality

The new features in detail

• Improved user interface
  o Desktop Docking functionality in order to have a framework
     behaviour between the Project Manager and the different
     editors (Fupla, Graftec, S-Edit).
  o Thanks the docking window function, the position of the
     components (Symbol Editor, FBox Selector) can be positioned
     according the user preferences.
  o Ability to open several source files at the same time (MDI,
     multi-document interface).
  o Use of standard components in the different editors in order
     to make the handling easier and effective.
   
• Hardware configuration
  The Device Configurator, already available in the last service pack of PG5 1.4 is now fully integrated into the PG5 2.0. This configurator gives an overview of the IO, communication and memory slot according to the specific device. Thanks the new IO handling functionality (process image) implemented in the PCD3 and PCD2.M5xx0 firmware, digital and analogue values can be directly mapped in the PCD media, without using FBoxes or FBs.
  Additionally, the Device Configurator features a label creator and calculates the current consumption of the configured modules.
   
• Symbol handling and symbol editor
  The symbol handling has been totally re-designed, including the symbol editor. The symbols are stored in the source code files to make file copying easier. The symbol editor has been improved with features similar to Excel, the possibility to defined more information associated with the symbols, tags, and improved sorting and filtering functions.
   
• Fupla Editor
  The user interface of the Fupla Editor has been improved with a new FBox selector with filter function, new FBox properties and adjust parameter windows. The Fupla Editor also includes the new symbol editor window. It is also possible to open more than one Fupla file in the same instance. It is also possible to copy and paste adjusts parameters from one FBox to another similar FBox.
   
• IL Editor
  The IL Editor contains a new selector window where the installed FB and CSF libraries are shown. With a simple drag and drop, the user can add the FB or CSF calls, including information about the required parameters into his code. 
  The following new PCD3- and PCD2.M5 features are supported:
  o "temporary data" (TEQU) has been introduced in order to reduce the number of resources used inside FBs or macros.
  o Support for IEEE and IEEE double arithmetics
   
• Graftec Editor
  Graftec templates can be created in order to re-use code in an easy way and to improve the development time. The new smart cursor functionality speeds up the diagram design. The interaction between Graftec and the IL and Fupla editors has been improved, including the debugging.
   
• Library Manager
  The new Library Manager gives an overview of the installed FBox, FB and CSF libraries and offers the possibility to copy library into the project in order to have a backup file that includes the libraries.
   
• Watch Window
  Trend functionality has been added in the Watch Window. The user can visualize digital or analogue values and check online the behaviour of the controlled system.

Restrictions of PG5 2.0 and PG5 2.1

Not all hardware and communication features are supported by PG5 2.0/PG5 2.1.
For installations containing the following products, PG5 1.4.300 will be available in future.

• PCD4 and PCD6 CPUs
• Profibus FMS
• Serial-S-Bus RIO Configurator (e.g. for PCD1.T240)

Due to an error on the PG5 2.2.230 BACnet compiler, PCD resource addresses changes (Reg-ister/Flags/DB’s/Text address change of existing symbols) on existing PG5 projects are not detected from the PG5 BACnet compiler and therefore the changed PCD resource addresses are not taken in account in the PCD after the download of the modified program.

Concerned products:
All PCD’s with FW 1.28.xx or later where BACnet revision 14 is used and where modified PG5 2.2.230 projects are loaded to the PCD.

The error doesn’t occur if:

• the PCD doesn’t contain a BACnet program.
• BACnet revision 9 features are used on PG5 2.2.230.
• PG5 2.3.xxx is used
• PG5 2.1 / PG5 2.0 or PG5 1.4 is used.

Error description:
Due to an error on the PG5 2.2.230 BACnet compiler, PCD resource addresses changes (Reg-ister/Flags/DB’s/Text address change of existing symbols) on existing PG5 projects are not detected from the PG5 BACnet compiler and therefore the changed PCD resource addresses are not taken in account in the PCD after the download of the modified program.

Detail information:
The PG5 BACnet compiler generate a checksum (CRC) over all PCD resources. This CRC is checked by the PCD firmware after the program download or the restart of the PCD to detect if the BACnet configuration has changed.
If the CRC has changed, then the PCD firmware forces the BACnet stack to reload the BACnet configuration in the PCD.
If the CRC has not changed then BACnet configuration is not loaded again in to the BACnet stack.
The error consists in the fact, that on PG5 2.2.230, the BACnet compiler doesn’t uses the PCD resource address for the CRC calculation and therefore a PCD resource address change of already existing PG5 resources doesn’t generate a different CRC.

The change of PCD resource addresses (Register/Flags/DB’s/Text addresses change of exist-ing symbols) could occur at any time to all, from PG5 automatically allocated PCD resources, if an existing PG5 2.2.230 project is modified or if the user changes manually allocated address of existing PG5 resources.

Error behavior:
The above described error lead to the situation that after the download of a modified PG5 ap-plication to the PCD, the BACnet Stack on the PCD uses still the old PCD resource address of PG5 resources instead of the new one.
This error could invoke a malfunction of the application program running on the PCD for PCD resources which are used/handled from the BACnet stack.

This behaviour could result to the situation that the application program on the PCD doesn’t work correctly and could create/provoke a randomly unexpected/unwanted functionality of the PCD application program.

Error correction:
The error will be fixed in PG5 2.2.234 or newer PG5 2.2 versions.
PG5 2.2.234 or newer should be available at the beginning of 2018.

Workaround for PG5 2.2.230:
The recalculation of the CRC can be forced by the user, if after each build something is changed manually in the BACnet configurator.
For example, a text string for the ‘Description’ or the ‘Location’ item on the BACnet configurator where the name could added with an underline ‘_’.
The new calculated CRC will then force the BACnet stack to load the new configuration.

Example to force the recalculation of the CRC:
Old Value for Location was ‘Murten’                  New Value for Location is ‘Murten_’

Due to an error on the E-Line S-Bus communication library < 1.2.110, the S-Bus communication stops after a certain time, if the communication mode ‘on Event’ or ‘on Sampling time n’ has been selected on the S-Bus communication FBoxes

Problem description:
If on the S-Bus FBox ‘SEND’ or ‘RCV’ the communication mode ‘on Event’ or ‘on Sampling time n’ was selected then after the update of the PG5 E-Line S-Bus communication library < 1.2.110, the S-Bus communication of the ‘SEND’ or ‘RCV’ FBox stops after a certain time and no S-Bus data’s are exchanged to the S-Bus slaves.
This problem occurs on all possible communication channels like RS485 or Ethernet.

The communication works well, if on the above mentioned FBoxes the communication mode was set to ‘On each cycle’ or ‘on data change’.

Detail information about the behavior:
Communication stops after a certain time:
The communication stops after 24 days after a power on of the PCD because the PCD internal millisecond systemcounter which is used for the event transmission has reached his maximum value and will be reseted to the value 0. Due of an error on the FBox library, this situation leads then to the communication failure.

Solution:
Either configure the communication mode in the ‘old’ FBox to ‘On each cycle’ or ‘on data change’ or use the E-Line S-Bus communication library 1.2.110 or newer.
The error is fixed in the FBox library 1.2.110, means the ‘event’ or ‘on sampling time’ communication runs well.

Due to an error on the communication library 2.7.370, the S-Bus communication stops after a certain time or after the download of the program, if the communication mode ‘on Event’ or ‘on Sampling time n’ has been selected on the S-Bus communication FBoxes

Problem description:
If on the S-Bus FBox ‘SASI S-Bus Master’, ‘SASI S-Bus extended’, ‘SEND’ or ‘RCV’ the communication mode ‘on Event’ or ‘on Sampling time n’ was selected then after the update of the PG5 communication library to the version 2.7.370, the S-Bus communication of the ‘SEND’ or ‘RCV’ FBox stops after a certain time or after the download of the new compiled program and no S-Bus data’s are exchanged anymore to the S-Bus slaves.
This problem occurs on all possible communication channels like RS485 or Ethernet.
The communication works well, if on the above mentioned FBoxes the communication mode was set to ‘On each cycle’ or ‘on data change’.

Detail information about the behavior:
Communication stops after a certain time:
The communication stops after 24 days after a power on of the PCD because the PCD internal millisecond systemcounter which is used for the event transmission has reached his maximum value and will be reseted to the value 0. Due of an error on the FBox library, this situation leads then to the communication failure.

Communication stops after the download of the new compiled program:
The library 2.7.370 internally uses a register which was not used before.
Depending of the value stored in the past in this register it’s possible that the S-Bus communication runs well or stops after the download of the program.

Solution:
Either configure the communication mode in the ‘old’ FBox to ‘On each cycle’ or ‘on data change’ or use the S-Bus communication FBox library 2.7.380 or newer.
The error is fixed in the FBox library 2.7.380, means the ‘event’ or ‘on sampling time’ communication runs well.

Fbox Update of the E-Line Library causes Problem with I/O refresh in Fupla

Symptoms

PG5 2.2.140 with E-Line Fbox Library V2.1.100.
After the automatical Fbox Update in the Fupla Editor, the Projekt will be Rebuilded and downloaded into the PCD without Errors.
Checking the Funktions Online, there is no Refresh for the States of Inputs and Funktion for the Outputs visible.
An Kommunikation Error is not indicated.

Reason

An Error in the PG5 2.2.140 does not perform a clean update

Solution

Is described in FAQ 101994

In PG5 2.2.220 the Error is fixed

Together with the official PG5 2.2.140, Web Editor 8.3.0.740 was released.
On this version there is a bug that lead to the situation that the properties window is empty or tabs of the properties window are not visible if the user does click on the layers in the document outline view.
If this happens, the Web Editor 8 must be closed and re-opened again.
There is a bug-fix version, Web Editor 8.3.0.749

The correction is also included in the web-editors which are supplied together with PG5 2.2.200 or later.

A correct properties view looks like this:

After the error the action tab is no more visible in the properties:

Steps to proceed in order to use the new Web Editor 8.3.0.749:
1. Download the Web Editor 8.3.0.749 from the support homepage as a self-extract file on your
    computer.
2. Rename the actual Web Editor 8 folder under "C:\Program Files (x86)\SBC\
    PG5 V2.2.140". For example into "WebEditor8_old". You will need admin rights.
3. Start the self-extract file and choose as target: "C:\Program Files (x86)\SBC\
    PG5 V2.2.140"
5. Web Editor 8.3.0.749 will now be launched as standard Web Editor with PG5 2.2.140.

Line length equal to 0 will be deleted from fupla

A function added in fupla of the version 2.2.140 create an error when the line lenght is equal to 0.

This could happened to all project made with version 2.2.xx.

The problem does occurs when connectors are directly connected to the Fbox as following

During programming, everything would work fine.

--> The problem does occurs when a fupla is reopen. During opening, a function does check the line lengh and does delete if lengh = 0.

In addition to this, no error would be displayed for the unconnected labels.

In that case, only the missing Fbox input would create an error.

Here is the view after compiling and reopening the fupla

In occurrence,  as this wrong behavior could create big hidden problems, it is highly recommended to install the hotfix 1.

This problem has been corrected in the hotfix 1 for 2.2.140. and will be included from version of PG5 2.2.200

Please download the patch from here

Unzip the folder and replace these files in the installation folder of your PG5 2.2.140 version

default path is:

c:\Program Files (x86)\SBC\PG5 V2.2.140

--> Once the Fupla program is open click on "Save all".

If you have had such open connection in the program, "incomplete network errors" will appear during the compilation. Simply reconnect the disconnected connections showed by the red arrow. 

The PG5 hotfix files allow us to supply you corrections/enhancements of PG5 components in an easy and fast way.

Actually the PG5 update manager is able to handle only installation packages files and therefore it’s not possible to use the PG5 update manager for the distribution of single files.

For this reason the hotfix files are actually only available on the support homepage.

Due of a error in PG5 2.2.130 it's not possible to map in the BACnet configurator analogue values to PCD medias.

This error is fixed since the Hotfix 1 of PG5 2.2.130 or since PG5 2.2.140

Due of an error in PG5 2.2.130 it’s no more possible to manipulate/force the F-Box internal adjust parameters from scada or web page of the 2 above mentioned F-Boxes and therefore it’s not possible to use the override functionally of the F-Boxes.

The problem does occur only, if one of the two above mentioned F-Boxes are new placed in a Fupla page in PG5 2.2.130 and if the F-Box does contains ‘user defined internal static variables’ and the definition of the ‘user defined internal static variables’ was done over the ‘right mouse click menu’ ‘Adjust Parameters’

There is no problem if:

• The project was taken over from PG5 2.1 and on this project in the F-Boxes there was a user defined or a system defined variable.
•  The F-Box is placed new in Fupla of PG5 2.2.130 and the internal symbols are ‘system defined’

Correction is done in the Hotfix 1 for PG5 2.2.130 or since PG5 2.2.140

The FBox library regarding the exchanges of datas with the Panels ESA (PCD7.D7xx) and PCD controllers is available for PG5 2.0 and can be used also in PG5 2.1, PG5 2.2 and PG5 2.3.

The FBox library is attached to this FAQ

On PG5 2.1, PG5 2.2 and PG5 2.3 a warning will be shown on the library manager 'BAD VERSION NUMBER' but it's possible to use the FBoxes in Fupla without problems

PG5 and Windows are both in continuous progress, so there may be incompatibilities between different versions. The table below gives an overview about the supported versions.

*) For further information regarding the compatibility of PG5 1.4 with Microsoft Windows Vista, Windows Server 2008 and Microsoft Windows 7/8 please refer to FAQ 100710.
**) Please refer to FAQ 101128 or 101195 for more information regarding the 64 bit version of Window Vista and Windows 7/8
***) The BACnet Configurator from PG5 1.4 is not compatible with the 64bit version of Windows7/8