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.

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’

For connecting a PCD to the internet a router is required. In case this router "knows" a DynDNS service, it is possible to find this this router by name.

The attached document contains an example of a step by step procudure for configuring dynamic DNS on a router (which "knows" DynDNS).

Remarks

• Note that the choice of the router or the DynDNS service from this document is sheer coincicence and does not mean that only this router works with PCD systems.
• Saia-Burgess Controls AG can not give support for the router configuration or the DynDNS setup. For support request regarding the router functionality or DynDNS please contact the according provider. 

The use of DNS (Domain Name Service) is very convenient for remembering the address of a host (e.g. a PCD3 connected to the internet with a DSL router). However, in some cases it is necessary to know the IP address of this host rather than the domain name.

How to translate the URL of a host to its IP address?
This task can be done by the tool "nslookup" which is installed on every Windows system:

• Open the DOS console (from the "Windows Start menu" select "Run..." and type in "cmd") 
• Type in the the instruction
  nslookup myname.dyndns.com.
  
  (don't forget the point after the URL)

As response you will receive the IP address of the requested name. In the screenshot above the IP address of the host "durrer.dyndns.tv" is 83.222.146.209.

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)

The settings of the ADSL router which we do use in Murten are shown on the attached document.

Depending on your configuration and your needs you have to adapt the settings of the ADSL router.

The instruction nslookup allows to find out the TCP/IP address of a public e-mail server.

To know the e-mail address of a public e-mail server enter the following string on the command window of windows.

nslookup

After this you have to enter the smtp address of the e-mail server.
(On the example below it's the address smtp.green.ch)

The TCP/IP address of the e-mail server is shown on the next line below the name of the smtp server.
(On the example below it's the address 81.221.250.52)

§ix100292§

For our Webserver Demo installation we have worked with different ADSL Routers, none of which was perfect.

Our Webserver Demo installation is connected to the Internet via an ADSL Link on an ISDN line, which is provided by www.green.ch. This provider offers fixed IP addresses for a good price and can be recommended vividly to all Swiss Customers.

Criterias to choose an ADSL Router

• you need to know whether an analogue or ISDN version is required (depends on the telephone line)
• it must support "nailed up connections", which means that if the internet connection is not closed periodically and if for some reason the connection gets lost anyway, the Router re-establishes the connection
• it should contain a firewall
• it should support address translation, so you can route telegrams to port 80 to the PC with WebConnect and telegrams to port 5050 to a PCD directly. Other ports should be blocked inwards
• an integrated switch is quite useful

Zyxel Prestige 650 ME-I

• does not support nailed up connections, so you need to run a software on the frontend PC which simulates Web traffic (for instance come.to/StayAlive ), to make sure the installations stays available from outside. Without such a tool the Router closes the Internet connection after a while and you cannot access the frontend PC or PCD anymore until you create Web traffic on the PC
• user friendly configuration tool

Zyxel Prestige 650 H-I

• nice product with rich features, 4 Port Switch, supports nailed up connections. Didn't work in our installation, Web traffic was only possible from the LAN to the WAN, but not vice versa, independent of the firewall configuration
• user friendly configuration tool 

Devolo Microlink ADSL Modem Router

• nice product with rich features, 4 Port Switch, supports nailed up connections. Blocks periodically in our installation, a power down / power up is necessary to re-establish the Internet connection. Since we cut the supply of the unit for a moment at noon, the product works fine...
• very bad documentation, configuration tool is not user friendly, not suitable for people that configure an ADSL Router for the first time

General Remarks

• we bought standard low price Routers, which are designed to let a workgroup share an Internet connection. With the Webserver we use the product the other way around, which can cause problems with some products
• do not expect to get useful support from the suppliers of ADSL Routers in this class. If the product does not work in your installation, it is worth returning it and try another model from the same or from another manufacturer
• using an output of the PCD to cut the supply of the Router periodically has proved to be a good idea. The cheap routers are usually used in an environment where somebody can interact easily in case of problems (private use at home), for Webserver applications in the field this is not always that easy

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.