The FBox 'MP Single' does indicate a Error and the code 23 (Timeout error) is displayed on the FBox.

This might happen when importing an older PG5 project (PG5 1.4.300 or 2.0) which work fine before in PG5 2.1.3x0.

Of course also this might happen with a brand new project created with PG5 2.1.3x0.

 

Reason:
An error was introduce in the Belimo library version 2.7.154!

Solution
Use the Belimo library version $2.7.304 in attachment or newer!

Remark:
This error was not present in PG5 2.0.xxx Belimo library 2.6.xxx
In PG5 2.1.xxx in the Belimo library version 2.7.155 an additional freeze bit was implemented to avoid inter-characters gaps when for example MP-Bus and Bacnet are used on the CPU.
If this new functionality is needed also on a PG5 2.0.xxx project please use the Belimo library 2.6.224 or newer available on our support site under:

www.sbc-support.com/en/product-category/archive/software/saia-pg5r-controls-suite/pg5-20/fbox-libraries/

 

In case a current transformator and a transfomer ration other than 1 (5:5) is used for measuring the energy with an AWD3 (with Serial-S-Bus interface) the FBox from the library 2.6.156 or older do not correctly display the current.

 

Symptom
The current displayed in the FBox is not correct if a current transformator is used for measuring the energy with an AWD3 (with Serial-S-Bus interface). Instead of e.g. 50 Ampere, 5.0 Ampere are displayed.
 
Reason
In case a transformer ratio other than 1 is used the AWD does send the current as [Ampere] (if the tratio is 1:1 the current is in the format x.x Ampere.
The FBox library version 2.6.156 (or 2.5.156 for PG5 1.4) and older do not consider this difference.

Solution
This problem will be corrected in the next FBox library version. 

 

Yes, the EnOcean radio receivers from Omnio, APG03U-RS485-Eno (unidirectional version) and APG03B-RS485-Eno (bidirectional version) are supported by the FBox library for EnOcean from Saia-Burgess Controls AG.

 

Points to be considered when using the Omnio radio receivers
The expreiences during the pilot phase have shown that: 

• It is important to use the EnOcean ID filter of the Omnio receivers
• In dependance of the version of the receiver, an according FBox version is to be selected (sending Acknowledge telegrams or not, see FAQ 101453)
• It is not possible to mix receivers from Omnio and Thermokon on the same RS485 bus. 

Can I order the Omnio receivers from Saia-Burgess Controls AG?
No, please order these devices from Omnio directly as Saia-Burgess Controls AG is no longer able to provide these products (unfortunately these products are still listed in the price list for 2010/11).

 

In case the PG5 2.0 FBox library version 2.6.150/151 (or PG5 1.4 version 2.5.100/101) is used the change from "autonomous" to "slave" mode does not work correctly. This problem is corrected in the PG5 2.0 FBox library version 2.6.165.

 

Symptom
After having changed the operation mode of a PCD7.L60x Room controller from "autonomous" to "slave" the output values for the heating and cooling signal are not stable (in fact they are changing between the values from the master and the ones calculated by the room controller). In this situation the Room controller is not working correctly.
After changing back from "slave mode" to "autonomous mode" the fan speed is blocked to to the level from the master.

Reason
This is a bug of the FBox library for the PCD7.L60x. The bug is present in the first FBox library version supporting SW 1.12 (PG5 1.4: 2.5.100; PG5 2.0: 2.6.150).

Solution
Please update the FBox library to the version listed below:

• PG5 1.4: FBox library version 2.5.165 or later
• PG5 2.0: FBox library version 2.6.165 or later

The output of the L60x Room Controller FBox switches from 1 to 0 when the temperatur setpoint is modified. This phenomenon appears on the new hardware V2.0 and SW 1.12!

 

Symptom
The output of the L60x Room Controller FBox switches from 1 to 0 when the temperatur setpoint is modified. This phenomenon appears on the new hardware V2.0 and SW 1.12!

Reason
The software version 1.12 does not identically treat the state of the occupancy input in case of changed setpoints (written by the PCD).

Solution
A new FBox library version takes this different behaviour of the room controller into account; please use the below mentioned FBox library which is available on the support site!
FBox library which solves this issue:

• PG5 2.0: 2.6.151 or later
• PG5 1.4: 2.5.101 or later

The memory requirement of a "HDLog to File" FBox (log in csv format) is calculated as follows:

Possible records = 50% of memory capacity (in bytes) / required characters per record (in bytes). Further on the maximum amount of files per file system is to be considered (around 850 files per SD card).

 

Memory available on a 1 GByte SD card
1 GB SD Card (PCD3.R600 with PCD7.R-SD1024) has 1’073’741’824 bytes
Note: It is not recommended to fill the SD card completely; in general we recommend only using 50% of the available memory in case data is written (and deleted) regularly.
Further on the maxumum amount of files per SBC file system is 900 in total, and every directory counts as 20 files (because the folder "WEBPAGES" and "CONFIG" always exists, the maximum amount of files which can be created on a SD card is around 850 (860 to be precise).

Memory requirement of log files
The memory requirement of files created by the "HDLog to File" FBox (log in csv format) is calculated as follows:
Possible records = 50% of memory capacity (in bytes) / required characters per record (in bytes)

Examples

• Writing 30 values to an SD card
  In case 30 values are to be recorded:
  Each value has an average number of six characters (exp. 123,4).
  Each HD Log File FBox requires 30 characters for the date and timestamp.
  So 30 record sets, subdivided into 3 FBoxes requires about 270 bytes per record (rounded about 300 bytes per record, including date and time stamps).
  1 GB SD Card (PCD3.R600 with PCD7.R-SD1024) = 1’073’741’824 bytes
  This results in about 3,500,000 entries. Due to the fact that you should not fill the SD card over 50% there remain effective 1'700'000 entries.
  At a recording interval of 5 minutes the SD card has space for about 16 years, given one file per month is generated (--> 16 years * 12 files/year * 3 FBoxes = 576 files)
  
  

  Remark regarding this example
  In case one file is generated per week, after around 5.5 years it won't be possible creating more files because of the maxumum number of files per file system has been reached (5.5 years * 52 files/year * 3 FBoxes = 858).

  
  
• Writing 3 values to a PCD7.R550 memory card
  In case 3 values are to be recorded:
  Each value has an average number of six characters (exp. 123,4).
  Each HD Log File FBox requires 30 characters for the date and timestamp.
  So 3 record sets can be recorded with one FBox and requires 48 bytes per record (rounded about 50 bytes per record, including date and time stamps).
  1 PCD7.R550 module = 4'000'000 bytes
  This results in about 80'000 entries. Due to the fact that you should not fill the SD card over 50% there remain effective 40'000 entries.
  At a recording interval of 1 minute the memory module has space for about 1 month (28 days) 

 

In case the dynamic space of registers is defined below 1000 or above 9999 the FBox HD Log to file cannot create the Logfiles correctly

 

Problem
If the dynamic space of registers is defined <1000 or >=10 000 the FBox HD Log to File is not able to create the Logfile correctly. The FBox is using interpreted text with $R commands. Due to a problem in the FBox this won't work for registers below 1000 since they only have 3 digits $Rxxx and the interpreted text needs 4 digits. Also in case the dynamic space is defined above 9999 the interpreted text won't work correctly, because the last digit is cut off by the firmware.

Solution
At the moment the dynamic space has to be defined >=1000 and <10 000 otherwise the FBox HD Log to File will not work correctly. The FBox library will be corrected for a dynamic space below 1000. To define the dynamic space above 10 000 a correction in the firmware will be necessary. As soon as a correction is available, this FAQ will be updated.

 

With PG5 1.4.300 it is possible that after the installation of a library (e.g. the HDLog library) PG5 indicates a message such as "S-FUP: Warning 28: Family 'HDLog.def' already defined in 'c:\Program Files\ ... \Libs\App\HDLog.def"

 

 

Symptom
When opening the Fupla Editor a message window with a text similar to this one gets displayed:

S-FUP: Warning 28: Family 'Historische Datenaufzeichnung' already defined in 'c:\program files\SAIA-Burgess\PG5 1_4\Libs\App\HDLog.def", file 'c:\program files\ ... \Libs\Usr\HDLog.def' will be not loaded.
S-FUP: Error 161: New macro name '_HDA_FILE_V22' is not part of library

Reason
In the past some libraries (HDLog in this example) which were located in the User-section of the FBox library were moved to the "app" (Application tab of the FBox Selector) section. As the old files weren't deleted the library is defined twice.
Concerned are the libraries "HDLog" and "RoomControler PCD7.L6x".

Solution
In order to avoid this message the FBox libraries need to be deleted from the "Usr" Folder. The FBox library consists of all files with the name *.def (HDLog.def in this example) which are located in the folder
c:\Program Files\SAIA-Burgess\PG5 1_4\Libs\Usr\
and all the sub-folders. Alternatively to deleting the files maunally, you can also use the attached batch file to rename the outdated files in your installation.

 

The TME Ethernet Thermometer can be connected over Modbus TCP to a PCD that supports Modbus.

 

Problem
Since the documentation for this thermometer is very limited regarding Modbus it is only possible to connect it via reverse-engineering. This is why we did a test.

Solution
The thermometer has a Web-Interface. With the base IP address it is possible to connect to the thermometer and set an IP address that corresponds to the network.
Afterwards the thermometer can be connected to the network. The temperature is available over Modbus TCP on "Input Register" 0. It is a 16 bit signed value. If more than one thermometer is in the network, each thermometer needs a different IP address, since they all have UID 1. A small demo project for the SBC-Modbus and Engiby-Modbus solution is attached to this FAQ.
In the attached PG5 program example the thermometers have the addresses 172.16.1.66 and 172.16.1.64.

Status Register
The following "Input Register" 1 contains the status of the thermometer. It is 0 if the thermometer is working correctly and it changes to 1 in case of error. If necessary you can read 2 "Input Registers" 0 and 1. The first will contain the temperature and the second the status.

 

In the most cases the "Sasi ..." FBox can be used (which is recommended due to the fewer possibilities for wrong configuration). However, there are some specific reasons for using the FBox "Sasi S-Bus extended"

 

The "SASI S-Bus Extended" FBox has to be used only in 3 following cases:

1. If you need to configure the S-Bus timing by using this FBox
   (-> Timeout -> TS-Delay -> TN-Delay -> Break length )
2. If you want to disable the "Secure S-Bus Data mode"
3. If you want to de-assign the communication port during runtime
   --> ATTENTION: in this case it is not possible to re-assign the port as GATEWAY (master) port (see FAQ 101399)
   

There are several reasons to use the FBox "SASI S-Bus Extended" (see FAQ 101400). But there is a limitation that it is not possible to use this FBox for re-assigning a port as Gateway master port on Saia PCD® COSinus systems.

 

Symptom
When re-assigning a Gateway master port using this FBox (or even in IL with the instruction SASI) it is not possible to assign the same port as Gateway master port after it has once been unassigned. This is the case if there is a falling and later on a rising edge on the input "Sasi" of the FBox "SASI S-Bus extended". On the second attempt to assing the port as gateway master port the FBox will get an error and the FBox LED becomes red:

• In the case you configure the GATEWAY funtion (in the device configurator and in the "SASI S-bus Extended" Fbox )
• The 1rst rising edge on the "SASI" input assigns the communication port (as serial master gateway)
  --> the Master-Slave communication works well.
• A falling edge (state "1" to "0") on ths "SASI" input de-assigns the corresponding communication port
  --> no communication is possible
• If you apply a 2nd rising edge on the "SASI" input, it will put the "SASI S-Bus Extended" FBox in ERROR. 
  A "Cold Start" is required in order to (re-)assign the communication port as serial Master Gateway port.

Reason
IT IS NOT ALLOWED TO DE-ASSIGN A MASTER GATEWAY PORT (an to re-assign it again) on Saia PCD® COSinus systems (PCD3, PCD2.M5, PCD1.M2 and PCD2.M480). This phenomenon is based on the internal mechanism how the firmware assigns the port. It has not been observed before the usage of the FBox "SASI S-Bus extended" as there are very few (if at all) reasons for un- and re-assigning a port as gateway master port.


Solution
In the case you configure the GATEWAY function (in the device configurator and in the "SASI S-Bus Extended" FBox )
WE RECOMMEND YOU TO CONNECT THE "SASI" TO A BINARY CONSTANT "1".

In this way the above mentioned problem will not occur. Please let us know in case you have an installation where it is required to re-assign a port in runtime as gateway master port.

 

The main application of this FBox is replacing a DX system by a PCD without the need to replace all the XT extensions, too. Therefore the FBox library for the Johnson Controls JCI N2-Bus is designed to connect XT 9100 extension modules (where the PCD is the master and the XT9100 is the slave).

 

General
The main application of this FBox is replacing a DX system by a PCD without the need to replace all the XT extensions. The FBoxes do support the N2 bus but not the N2 Open protocol.

Master functionality of the FBoxes
The FBox library for the JCI N2-Bus is mainly designed to connect XT 9100 extension modules (where the PCD is the master and the XT9100 is the slave).
Additionally it is possible to read out single items (but not data structures such as e.g. schedulers) from other devices (such as DX) as well, given this device has the connected port initialized as slave (the PCD is the master).

Slave functionality
The slave functionality has been implemented to provide a possibility to exchange data on the N2-Bus between PCDs, but it is not possible to connect a PCD to a SCADA system from JCI or to a JCI NAE or NCM controller (because this SCADA or NAE is first of all reading a Johnson ID together with a specific set of parameters, which the PCD does not provide; if the ID and the specific set of parameters is not received by the SCADA or NAE, no furhter communication will be executed by the JCI SCADA or the NAE).

 

The online paramters of the "Call SMS" FBox should be adapted in runtime. Per example inserting another destination for the "Call SMS" FBox. For some reason the updating of the callnumbers is not working. The values are overwritten by the offline parameters imediatly.

 

Problem
The phone numbers in the "Call SMS" FBox can normally be overwritten in runtime. Means that a user can change the destination phone numbers. If the "Ini" input of the "Modem Driver 18" FBox is permanently high and the option "Evaluate Ini Input" is set to "In runtime" the online parameters are each cycle overwritten by the offline parameters.

Reason
Due to a malfunction of the FBox the Ini Input is not only reacting on a rising edge but always. Therefore the Modem FBoxes are initializing each cycle and all parameters are reset to the initial parameters (offline parameters)

Solution
As a workaround change the "Evaluate Ini Input" to at startup or insert a dynamize FBox in front of the Ini input. A correction has been implemented in the Modem FBox Library and is present in the following two versions (and later versions, too):

• PG5 1.4
  Modem FBox library version 2.5.304
• PG5 2.0
  Modem FBox library 2.6.102 or higher

The FBox libraries can be downloaded from the Support page in the section "Software" --> "PG5 x" --> "FBox Libraries". 

 

Yes, Modbus is supported by the firmware of recent Saia PCD® systems (on all ports, including the ones on F2xx modules since beginning of 2011) or by a dedicated FBox driver.

 

General
There are two possibilities to use Modbus on SBC CPUs (Classic versions).

• The new FBox library for Modbus "Modbus SBC Version" which takes advantage of the Modbus implementation directly in the Saia PCD® COSinus firmware.
  Available for PCD1.M2, PCD3 and PCD2.M5 with firmware version 1.10.16 or more recent (for using on F2xx modules, in minimum FW 1.14.23 is required).
• The Modbus FBox Library from our partner ENGIBY which is available since several years (www.engiby.ch) and supported also by PCD systems previous to the PCD3, PCD2.M5xxx and PCD1.M2xxx families (e.g. PCD2.M1x0, PCD2.M480 or PCD1.M1xx).

Remarks

• In order to use the firmware implementation of Modbus on PCD2.F2xxx or PCD3.F2xx modules, the following prerequisites need to be fullfilled:
  - minimal PCD firmware: 1.14.25 (1.14.23 does support the F2xx modules, but
    communication errors can occur)
  - minimal hardware version of the F2xx(x) module: version D (delivered since beginning 2011) 
• The FBoxes for "Modbus SBC Version" are available for download from the support site since July 2009.
  In PG5 2.0.110 and later the "Modbus SBC Version" is installed by default. Please note that a licence is required for this library.
  

 

When placing an FBox "PCD7.D120" it is not possible to build the project anymore with PG5 1.4.300 due to a syntax error.

 

Symptom
When placing an FBox "PCD7.D120" it is not possible to build the project anymore. On build the error message "Error 31: C:\Program Files\SAIA-Burgess\PG5 1_4\Libs\Std\sfupdis5.srx: Line 323: Syntax error" is shown and the build fails.

Reason
The error message is shown because of an error on the SFup base library which is distributed with PG5 1.4.300.

Solution
To fix the error please install the library S-Fup Base Library version 2.6.100 or higher (installer file "S-Fup Base Library_V2_6_100_ml.exe").
This FBox library can be obtained from the support site www.sbc-support.ch (Section "Software"-->"PG5"-->"PG5 1.4"-->"FBox libraries").

 

The fan optimizer COU24-A-MP from Belimo is used together with VAV controllers. However, this device is optimizing the fan based on a signal given from the VAV and can not be addressed and controlled by a PCD (or another DDC master) over the MP Bus.

 

General
Since the fan optimizer does optimize the fan speed based on the signal given from the VAV controller (e.g. from the VRP-M) there is no need (and no possibility) to send any information to this device over the MP Bus. Therefore there is no FBox for the fan optimizer (seen from the PCD, the fan optimizer is "invisible"). The fan optimizer does not have/use an address on the MP bus.

Remark
The task for optimizing the fan can also be done by the user program on the PCD.

 

Due to incompatible communication parameters used by the Omnio "RS232/485 to EnOcean" converters the FBox library version 1.0.0 is not working in every situation with the converter from Omnio.

 

Symptom
The communication between a PCD and an Omnio “RS232/485 to EnOcean” converter does not work with the EnOcean FBox library version 1.0.0.

Reason
The communication protocol/parameters which is used by the Omnio "RS232/485 to EnOcean" converter is not the same as for other "RS232/485 to EnOcean" converters (e.g. the one from Thermokon).

Solution
Since the EnOcean F-Box Library 1.0.20 the FBox "EnOcean Init" does feature an adjust parameter called "manufacturer". This selection will then adapt the communication protocol of the PCD.

 

Only FLS devices with automatic supports MP-Bus communication.

A new FBox library is needed

 

Problem
1. There is a confusion in the actual catalogue about which FLS devices supports MP-Bus.
2. Actual FLS devices need the FBox library 2.5.303E or higher.

Solution
1. The correct statment is, that only FLS devices with automatic supports MP Bus communication. Future catalogues will be corrected.
2. Note that 2.5.303E is not an official version, please ask the support team if you need this library. The next official version will contain this correction.

 

If the PCD2.F2610 or PCD3.F261 Dali communication modules are used:

There is no need to use a Tridonic interface.

The whole DALI configuration is done with the Dali F-Box over the F2610/F261 modules

 

If the DALI communication is done over the serial line of the PCD and a external DALI interface:

For the programmation of the lights in the DALI network Tridonic offers a tool.

Additionaly an USB interface is necessary.

For the communication with the PCD a serial interface is needed.

 

If the DALI communication is done over the PCD2.F2610 or PCD3.F261 DALI communication module:
The configuration of the Dali device can be done over the PG5 F-Boxes and/or the Web-page.
There are F-Box for the addressing, and configuration of the Dali devices as for the definition of groups and scenes.
There is no need to use a external tool.

The solution with the PCD2.F2610/PCD3.F261 does replace the solution with the external DALI interface from Tridonic.

If the DALI communication is done over the serial line of the PCD and a external DALI interface:

Preparation of the Dali devices:
To use a DALI device with the PCD it is necessary to set some parameters in advance.
At least the device address has to be configured.
Additionally it is possible to create groups and scenes. If some devices are in a group, it is possible to switch them off/on together etc.
For this configuration you will need a tool from TRIDONIC, which is freeware www.tridonicatco.com an USB interface order number 24138923 and the power supply order number 24034323 from TRIDONIC. Note that the serial interface is not supported by the new configuration tool and the old tool is not available anymore.

PG5 programming and operation:
In PG5 there are FBoxes available for DALI.
The DALI Bus has to be connected to a serial port on the PCD. Therefore you will need the SCI interface from TRIDONIC: order number 24033463. This device is not listed in the TRIDONIC catalogue because it is not supported by the current programming tool, otherwise it is still available and not obsolete.

Updates

• 18.12.2010
  Please note that there is also an SCI2 interface available (which will replace the SCI1 interface).
  The SCI2 interface is not supported by the FBox library.
  When ordering an interface, please specify that you need a SCI1 interface (which will be available until summer 2011 at least). 
• 12.05.2010
  The tool for the configuration of the DALI lamps over the serial interface is available again on the TRIDONIC homepage. Search for WinDim in orderr to find it.

Yes it is possible to deactivate the "secure S-Bus Data Mode".

 

Introduction
In some special cases it can be desired to deactivate the "secure S-Bus Data Mode". This is possible by adding a specific parameter to the SASI text.

Usage
The additional parameter is placed after the parameter "destination register" (the "destination register" is R20 in the example below)

TEXT 0 "UART:9600;MODE:SM2,R20,0;DIAG:F0,R0"

Default value is 1 (Secure Data Mode activated)!
When the SASI text does not have this option or does have an option different than zero, the "secure S-Bus Data mode" is activated.

The option has to be a constant.

This option is only available for the SM2/GM mode.

Firmware dependency
Minimum firmware supporting the possibility to deactivate the "secure S-Bus Data" mode can be found in the table below (systems not listed in this table do not support this option).

PCD type	minimal Firmware version
PCD1.M1x5	0F0
PCD2.M150	0F0
PCD2.M170	0F0
PCD2.M5xx0	1.10.16
PCD3.Mxxx	1.10.16
PCS1	0F0

 

Usage in Fupla
For Fupla users the version 2.6.101 of the communication library does feature a new parameter in the FBox "Sasi S-Bus extended" to activate and deactivate the secure S-Bus Data mode (mode "Data No Secure"):

Availablility of the FBox

• For PG5 1.4 the FBox library 2.6.101 is available from the support site
• PG5 2.0.110 contains this version by default
  

The VRP-M is a universal variable air volume controller (universal VAV controller). For connecting this controller to a PCD over the MP Bus the FBox "MP Actuator VAV" is to be chosen.

 

General
Since the VRP-M is used for controlling the air volume the FBox to be used for accessing and controlling this device is the "MP Actuator VAV". This FBox allows to pass the required volume as input (the VRP-M will calculate the required position of the damper by itself).


Remarks

• It is not possible to command the position of the damper from the user program (except to close (input "Cls") or open (input "Opn") it completely)
• In case a VRP-M STP (for constant pressure) is used, the same FBox can be used and the input "Vol" is given as % in pressure instead of volume as for the VRP-M VAV

After the installation of the version 1.4.300 of the "JCI N2-Bus" FBox library, it is no longer possible to build the Saia PG5® project but the error message "Protected library used: _SBC_JCI_N2BUS" is shown.

 

Symptom
After having installed the version 1.4.300 of the FBox Library for the JCI N2-Bus (and having done the steps explained in FAQ 100973), it is no longer possible building the PG5 project. At the end of the build process, the following message is shown:

Linking: _CPU1.obj + Source.obj + Untitled1.obj + Untitled2.obj + _TCPIPDBX.obj
Fatal Error 391: Protected library used: _SAIA_JCI_N2BUS

Reason
The reason is that this library requires a specific license (user.key file which is to be registered from menu "Help"-->"Register Software..."). The FBox library which has been available on the support site until June 2008 has by mistake not requested this license.

Solution
Please contact your local Saia-Burgess Controls AG Sales office for obtaining the license for the JCI N2-Bus.

 

This FAQ contains the updating procedure in case the JCI N2-Bus library is updated to version 1.4.300 (and an older version of this FBox library has been installed).

 

Symptom
After having installed the version 1.4.300 of the FBox library "JCI N2-Bus", Fupla always reports Warning 28:

CPU 'CPU1 - PCD3.M3330 - IPNode 0, Station 11' Activated
S-FUP: Warning 28: Family 'JCI N2-Bus' already defined in 'C:\Program Files\SAIA-Burgess\PG5 1_4\Libs\App\JCI_N2_Bus.def', file 'C:\Program Files\SAIA-Burgess\PG5 1_4\Libs\Usr\JCI_N2_Bus.def' will be not loaded.

Reason
The reason for this warning is that previous versions of the N2-Bus library have been installed to the "User" folder of the FBox Selector. Because this library will be installed by default in future PG5 versions, the target folder has been changed to the "Application" folder.
If a previous version has been installed in the "Usr" folder and the new version 1.4.300 has been installed to the "App" folder, PG5 detects the same library installed twice and therefore informs the user with the Warning 28:...

Solution
In order to avoid this doubled presence of the library, please uninstall the previous version which is installed in the "Usr" folder. This can be done by deleting all files named with "JCI N2 Bus.*" and "JCI_N2_Bus.*" from the folder:
c:\Program Files\SAIA-Burgess\PG5 1_4\Libs\Usr\

Remark
In case you are working with the override libraries, please make sure that the new library is installed in the "Libs/App" folder from your project and that the according library files are deleted from the "Libs/Usr" folder in your project.

 

There are error messages displayed for each old FBox that it should be replaced.

 

Problem
After installing the new version of the Belimo library which allows to have more than one MP-Bus Master in a Fupla file, it is not possible anymore to build the old projects.

Reason
The MP-Bus Belimo library 2.5.300 and 2.5.301 had an incompatibility with older MP-Bus Versions. The library 2.5.300 was distributed with PG5 1.4.300.

Solution
Please update your MP-Bus FBox library version to version 2.5.302 or higher. The latest version of the FBox library can be downloaded from the support site in the section "Product information" --> "Software" --> "PG5" --> "FBox libraries".

 

The DALI FBoxes offer the possiblility to access the lights with broadcast (every light on the bus), short (just a single light) or group (a defined group of lights). This different addressing is only possible if the lights are configured.

 

Problem
DALI lights can only be accesed using broadcast commands. How is it possible to address the lights?

Solution
The addressing of the lights is possible using the tool from TRIDONIC www.tridonicatco.com. Additionally the serial communication modul from TRIDONIC is needed. Either the communication modul for the serial port which can be used for the PCD communication as well, or the more comfortable module for USB communication which can not be used on the PCD. Otherwise the USB programming tool offers more possibilities. It is per example possible to change the addressing of the lights. With the serial tool the addressing is random and cannot be adapted by the user.

Important to know
The WinDim tool from TRIDONIC which must be used for the addressing and group/scene configuration is addressing the groups and scenes from 1 to 16. In fact on the bus the addresses are from 0 to 15. As well our F-Boxes are working with addresses from 0 to 15. So keep in mind that if you configure a group/scene in the WinDim tool you have to use the address -1 in the F-Boxes. Per example: WinDim address: group 3, FBox address: group 2

A short description and a program example is available on request from pcdsupport.

 

A broadcast to the DALI Bus does reach all lights/devices on the bus. But how is it possible to create groups and how can individual devices be addressed?

 

Problem
If the FBoxes are sending broadcast messages, all lights on the bus will be switched on or off at the same time. But usually it is more convenient to address single lights or even better groups of devices.

Solution
DALI offers the possibility to have light-groups and to address each light individually. In order to configure the addresses of each light and to build groups, a configuration tool from the light manufacturer is required.

 

The library of the "RAG Einzelraumregelung" (for the obsolete product PCD7.L71x) is not distributed with recent PG5 versions. In case a project is to be updated and this FBoxes are still needed, please download it from this FAQ.

 

Symptom
After importing an old PG5 project containing the FBoxes for the obsolete PCD7.L71x room controllers, not all FBoxes are found. During the build, PG5 prints the following error messages:
Compiling: D:\Projects\PG5_1_4_Projects\CustomerCPUs\MyProject\MyFupla.fup
S-FUP: Error 65: MyFupla.fup: Page 1(47,28-1): FBox not in library.
After double-clicking the error messages, Fupla opens and e.g. an FBox "PCD7L712" or "EZRCOM2" like in the screenshot below is shown:


Reason
As the products PCD7.L71x are obsolete, the according FBoxes are not installed by default (in order to avoid confusion with the current, similar products).

Solution
Download the library from this FAQ and launch the self-executable "Ragezr.exe". It will extract the library files directly into the same folder as the "Ragezr.exe" is stored. Cut these files and paste them in the folder "c:\Program Files\SAIA-Burgess\PG5 1_4\Libs\Usr\" (for PG5 1.4).
Once this is done, you'll be able to compile the project.

Additional information
The library contained in "Ragezr.exe" contains the following Fupla Macros: _EZRCOM2, _RAGEZR, _RAG12, _RAG11, _RAG10.

 

The new EIB FBox library 2.5.142 (distributed together with PG5 1.4.200) does support the FT1.2 interface (also known as BCU2). Further on also EIBnet/IP (also known as KNXnet/IP) is supported with this library.

 

Supported interfaces
The interfaces listed below are supported by the library version 2.5.142 and higher. The version 2.5.142 is distributed together with PG5 1.4.200.

BCU1
Using the standard BCU1 interface, this well known driver FBox now has been extended to reinitialize the communication by triggering a re-poll all inputs and re-send all outputs using a single trigger input into the driver FBox.

In case communication problems are encountered, the EIB driver FBox can be exchanged with the EIB Extended where specific options are available to tune the interaction with the BCU.

Note: It is NOT recommended to use a BCU1 interface anymore if a higher bandwidth is expected OR if NO telegrams from EIB should get lost! Instead choose a FT1.2 (BCU2) or an KNXnet/IP (EIBnet/IP) solution (see below) for those projects!

FT1.2 (also known as BCU2)
A new driver FBOX for the SIEMENS Gamma Instabus Interface 5WG1 148-1AB04 using the FT1.2 protocol is available from the EIB library version 2.5.142 on. Since this protocol is far more performant than the one specified for the BCU1, no more telegrams are expected to be lost even if the PCD is well charged so Fupla is running below 30 cycles per second.

Note: This solution is recommended for installations without Ethernet and for those where the BCU1 solutions fails to meet the expectations.

KNXnet/IP (also known as EIBnet/IP)
As of today this driver FBox has been tested with the SIEMENS Gamma Instabus Interface 5WG1 148-1AB21. Field tests have also reported that the same FBox can be used with the SIEMENS Gamma Instabus Router 5WG1 146. No more serial cable is needed since the Ethernet port will be connected to the EIB Interface/Router.

Note: This solution is the recommended solution for all new installations with Ethernet!

Other new features of library version 2.5.142

• All driver FBoxes now have two additional trigger inputs. With them the initial polling or sending commands at startup (to be configured in each RCV/Send FBox) can be forced anytime at running time. This is very useful if a communication problem, such as a partial power outage and power return has been detected.
• When the communication interface is to be changed in an existing project, such as the migration from a BCU1 to a BCU2 or KNXnet/IP (EIBnet/IP) , ONLY the driver FBox needs to be replaced! All other EIB FBoxes do not need any modification!

ETS requirements
In order to have the latest components available it's recommended to use ETS3.0 Patch A. The component libraries for ETS can be found on the respective manufacturers home pages.

 

If a existing customer buy a new PG5 library (e.g. the S-Web Editor Advanced) and he had already a licence number for a Modbus library, does he need a new licence number from Engiby?

 

 

No, in case the customer name (user name) has NOT been changed it isn't needed to get a new licence number from Engiby because the licence number from Engiby checks the user name in the User Key.

 

When choosing the dynamic registers above 8191 on a PCD2.M5xx0, a PCD2.M480 or a PCD3, this error message can appear in case FBoxes are used which apply "indirect instructions".

 

Symptom
A build in PG5 1.4 failes with error 335:
Error 335: Komm.obj (432): JPI: __stc_C0001_00_01_02: Invalid register number
A build in PG5 2.0 failes with error 2035:
Error 2035: Komm.obj (432): TFRI: PCD.HDA.MacWrk.Reg: Invalid register number, max is 8191 for register indirect instructions

Reason
The problem is that 'register indirect' instructions (SASII, TFRI, STXMI, SRXMI etc.) do not allow register addresses above 8191. As these instructions are used by many FBoxes (Modem-Driver, HDLog or the HMI Editor), the last address of the "Dynamic Space" for registers must not be higher than 8191.

Solution

• In case plenty of registers are available:
  When using indirect instructions with dynamic addresses, the dynamic address range must not exceed the address 8191. This configuration is made in the "Sofware Settings" (PG5 1.4) or "Build Options" (PG5 2.0) of the according CPU/Device:
  PG5 1.4:
  
  PG5 2.0:
  
• In case no more registers are available, try the following procedure
  - Execute a "Clean files" of the CPU/Device
  - Rebuild the project
• In case a simple "Clean files" does not help,
  - Execute a "Clean Files"
  - Check which library causes the problem
  - Modify the "Link order" in order to link the program which contains the TFRI as first program
  - Open the Fupla and export and then delete pages/blocks which do not cause the problem
  - Rebuild the project
  - In case the build is successful: Add the previously removed blocks
  - In case the build still fails: continue to execute the "Clean files" and remove more Fupla blocks/pages

 

We have received the information that on an application it was not possible to access with PG5 version 2.1.420 over serial line (RS232) in PGU or S-Bus mode to the PCD and the message: Error 99: Can’t open port comx was shown in the debugger.

The reason why it was not possible to access the PCD was the fact, that the com port was used from another application at the same time.

The application which have used the same serial port was the software SoMachine from Schneider Electric.

Solution:
To be able to go online in this situation, it’s necessary to stop the software SoMachine from Schneider Electric.

 

Yes it’s possible to update the initial values of a DB with the actual online values of the PCD.

To do this just open the DB when PG5 is online with the PCD and right mouse click, then select the option 'Upload' from the context menu.

Remark:
In PG5 it’s possible to define the initial values of a DB.
This initial values are downloaded with the application program and are used as first time values if the DB is loaded the first time or after a restore of the program

Example
Definition of the initial values:

Actual online values:

Upload function:

 

DB with new initial values:

 

 

If the S-Bus communication over TCP/IP between PCD’s does not work, then do check on the TCP/IP settings table of the PG5 project manager that the field “use” is checked for each line (device) which have to communicate over S-Bus TCP/IP.

It’s possible that after an import of a PG5 1.4 project in to PG5 2.0 the field “use” on the TCP/IP settings table is unchecked and therefore the communication over S-Bus TCP/IP doesn’t work.

 

 

 

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.

 

As PG5 is an important topic there is a seperate PG5 folder in the root of the FAQ Manager.

 

 

If the Control interval (ASS/ABI-CI) is set to 0 then the error flag will be set to high after the SASI instruction.

The Control interval (ASS/ABI-CI) is defined on the following menu of the PG5 Profibus-FMS configurator:

Edit Station, Channel List, Header

 

 

On Profibus Network it is important to use the right cable and connector as the communication speed goes up to 12 Mbautes!

Those cable and connectors are used in Profibus DP, FMS, Profis S-Bus, Profi S-IO and MPI!

 

Wiring and Network termination should be as follows:

1	Shield
3	RxD/TxD-P
4	CNTR-P
5	DP GND
6	DP +5V
8	RxD/TxD-N
9	CNTR-N

§ix100234§

<dir><dir>

Supplier for 9-pole Profibus D-Sub connectors to connect PCD controllers to Profibus networks:

ERNI Elektrotechnik AG, Brüttisellen, Switzerland:

● ERbic junction, horizontal grey: Erni Ref. 103648
(junction fitted with series inductance of 110 nH)

● ERbic junction, horizontal grey:
with PG connector: Erni Ref. 103663
(junction fitted with series inductance of 110 nH)

● ERbic termination, horizontal yellow: Erni Ref. 103649
(junction fitted with series inductance of 110 nH
plus termination resistors of 390 Ω and 220 Ω)

</dir></dir> 

§ix100228§
ERNI ERbic connector

The cable should be approved by the Profibus norm DIN 19245:

Attached 2 pdf files (both in french and german) of a swiss cable supplier Volland AG 8153 Rümland / Switzerland;

Ref.:    01 0217 0220 cable for fixed installation
            01 0271 0022 fexible cable

Note:    
If the bautrates isn't greater than 187,5 bautes (for ex. Profi S-Bus with PCD3.M3xx / PCD7.D7xx) you can use other more advantegeous cable, especially if the network segment is shorter than 600 meters!
See attached document "Annexe1 CI 2005_11"

 

The first document describes the configuration between UNIGYR PRU and PCD2

For mounting and installation instructions we refer to the SBC Manuals PCD2 26/737

The second document describe an PG5 Version 1.3 example for the communication between the PCD2 and UNIGYR PRU

 

 

 

 

   for more Help or application support you can connect:

   A&P Kieffer Omnitec Sàrl

   59, avenue Pasteur / BP 317

   L-2013 Luxembourg

   Tel.:  (+352) 474848-258

   Mail: martin.theis@kiffer-omnitec.lu

 

 

 

 

There are confusing screw terminal identifier terminologies around. Depending on the manufacturer the identifiers used are in conflict to the identifiers you can find in SBC manuals.

 

General
RS-485 is a Bus-system, therefore the signal wires shall not be crossed.

Converter	PCD
Rx-Tx (or D)	Rx-Tx
/Rx-/Tx/ (or /D)	/Rx-/Tx

Sometimes "+Data" and "-Data" can be found on devices. Then "+Data" propably has to be connected to "/Rx-/Tx" (or /D) and "-Data" to "Rx-Tx" (or D).

Converters
Some products form other manufacturers (p.e. RS232 - RS485 converters) are often inversly indicated. Therefore it is sometimes necessary to cross the wires.

Converter	PCD
Rx-Tx	/Rx-/Tx/
/Rx-/Tx/	Rx-Tx

Profibus and Profi-S-I/O 

Profibus	Colour	PCD7.T160	D-Sub 9pin on PCD	Port 2 on PCD3.M3 and M6
A=RxD /TxD-N	green	D	pin 8	D
B=RxD /TxD-P	red	D/	pin 3	/D

Example for the port 3 of the PCD3.M5540 as Serial-S-Bus
RS485 connection (Serial-S-Bus) between PCD3.M5540 port 3 (S-Net D-Sub used as RS485 Serial-S-Bus) and PCD2.M5540 port 2 (connector block X3):

PCD3.M5540 (D-Sub "S-Net", port 3)	PCD2.M5540, X3, port2  equipped with a PCD7.F110
pin 3	terminal 2
pin 8	terminal 1

 

When the 4 channels analog carte PCD2.W745 is used on a PCD3.T760 RIO module 6 registers are available on the master station. It is important to know that the 2 first registers contain the diagnostic bits of the 4 inputs channels!

 

How to interpret those 2 diagnostic registers (anal_16 and anal_17) ?
The first 2 bytes (low bytes) gives the diagnostic bit of 2 analog channels (1 byte per channel) as indicated in the following screenshot:


Signification of each bit (from right to left):

 

In some cases it is possible that a PCD7.F7500 is not correctly detected on a PCD2.M5540 with hardware version 'C' without modification '6'.

Symptom
The Profibus Master module PCD7.F7500 does not work while commissioning. During start-up of the PCD the Error LED is lit and in the history the message "PROF DP FAIL 000" is added (see screenshot from a diagnostic file below):

Reason
In some specific cases the PCD2.M5540 does not detect the PCD7.F7500. As result, the module can not be configured and the Error LED of the PCD is lit.
The PCD2.M5540 hardware version C with modification 3,5,6 contains a modification of the CPLD which assures that the module PCD7.F7500 it detected correctly.

Solution
Please use the PCD7.F7500 module with a PCD2.M5540 with the hardware version/modification "C 3,5,6"or newer.

In case you are concerned by this case and your PCD has an older version (e.g. version/modifications "C 3,4,5"), you need to replace the PCD2.M5540 with a newer one.

Remarks

• If the PCD2.M5540 is running with a PCD7.F7500 there is no need updating the hardware, even if the modification above is not applied (because the problem does only occur on some combinations of CPU and F-module
• Since May 2011 the PCD2.M5540 delivered by Saia-Burgess Controls AG have the modification 6 or later applied.

The maximum of exchanged data over a Profibus DP interface (or Profi-S-I/O) interface is depending on the system (the amount is not the same for a PCD7.F750 or a PCD3).

 

PCD7.F750 placed on a PCD2.M1x0 (non SBC-NT)
The Profibus DP manual states that the maximal amount of exchanged data per PCD7.F750 is 2942 bytes.

PCD3, PCD2.M5 or PCD2.M480 and PCD1.M2 (SBC-NT)
The limitation mentioned above does not apply for SBC-NT systems where the maximal amount of exchanged data is 2048 bytes.

 

When configuring a W525 module using the Device Configurator or the Profi-S-I/O (or Profibus DP) Network Configurator, the PCD2/3.W525 does need two registers for the analogue outputs and 8 registers for the analogue inputs.

 

The significations of the registers are the following:

Output registers: 

Register	Bit 31..16	Bit 15..0
n		Value CH0 Output
n+1		Value CH1 Output

Description of the output registers:

Value CH0..1 (Register n, n+1)
This registers (Bit 0 to 15) does contain the analogue output value of the corresponding analogue output. It's a 12 Bit value.

Input registers:

Register	Bit 31..16	Bit 15..0
n		Value CH0 Input
n+1		Value CH1 Input
n+2		Value CH2 Input
n+3		Value CH3 Input
n+4		Load Current/Voltage
n+5		Status Module
n+6		Status Input
n+7		Status Output

Description of the input registers:

Value CH0..CH3 (Register n...n+3)
This registers (Bit 0 to 15) does contain the analogue input value of the corresponding analogue input. It's a 14 Bit value.

Load_Current / Load_Voltage (Register n+4)
On this register (Bit 0 to 15) the actual current or voltage value is displayed.

• current in [μA] (0..20'000)
• voltage in [mV] (0..10'000) 

Status Module (Register n+5)
This register (Bit 0 to 15) does contain the actual status of the module

Table module status:

Bit	Description
15:14	Reserved
13	Error on the output channel CH1
12	Error on the output channel CH0
11	Error on the input channel CH3
10	Error on the input channel CH2
9	Error on the input channel CH1
8	Error on the input channel CH0
7:5	Reserved
4	Communication: Illegal Command. Is set to 1 if the module receive a not know instruction.
3	Communication: packet too long. Is set to 1 if during the communication a data byte (CMD/Data = 0) is received although a commando byte should be received (CMD/Data = 1)
2	UExt too low. The voltage of the external power supply is to low!
1	UExt Fail.
0	No Response.

Status Input (Register n+6)
This register (Bit 0 to 15) does contains the status of the input channels CH0..CH3.
The status of each input channel is displayed on 4 bits.

Status Input:  

Bit	Description
Bit 0..3	CH0 Status
Bit 4..7	CH1 Status
Bit 8..11	CH2 Status
Bit 12..15	CH3 Status

Table input status:

Bit	Description
3	Over Temperature
2	Not Calibrated
1	Over Range
0	Under Range

Status Output (Register n+7)
This register (Bit 0 to 15) does contain the status of the two output channels CH0 and CH1.
The status of each output channel is displayed on 6 bits.

Status Output:      

Bit	Description
Bit 0..5	CH0 Status (LOW BYTE)
Bit 8..13	CH1 Status (HIGH BYTE)

Table output status:

Bit			Description
CH0		CH1
5		13	Load Resistance too high. Only for outputs in current mode. Occurs typically if the output circuit is open
4	12		Load Resistance too low. Only for outputs in voltage mode. Occurs typically in case of short circuit
3	11		Over Temperature
2	10		Not Calibrated
1	9		Over Range
0	8		Under Range

On our Profibus DP Master modules and CPUs there are two LEDs available:

RUN = Yellow

ERROR = Red

 

Modules and CPUs
The LEDs RUN=Yellow and ERROR= Red are present on the following modules:
PCD7.F750
PCD7.F7500
PCD3.M654x: On this CPU the LEDs are below the cover. Otherwise you can see them if you open the blue cover that covers the battery-module, M1-, M2-Slot and the RUN Stop/switch. Through the little gap where the cover is cliped in, the LEDs are visible:



Status of the LEDs:
ERROR LED:
The ERROR LED is switched on for approximately 1 sec during startup. If the module is working correctly the error LED is switched of afterwards. In case the error LED is switched on or blinking the Profibus DP module has a serious problem that is most probably related to the hardware itself.

RUN LED:
The RUN LED is normally blinking after startup. If it is blinking fast (~10Hz), the Profibus communication is not running correctly. In case the Profibus communication works well, the RUN LED is blinking slowly (~1Hz). If the communication is not working properly, more information is available in the history of the PCD. Check the history of the PCD for Profibus DP FAIL errors (see list below for the meaning of these messages). If there is no entry in the history regarding the DP functionality, you can check the diagnostic flags and diagnostic registers. More information about the Profibus diagnostic is available in the manual Profibus DP 26/765. The manual is at the moment not up to date. Only the PCD7.F750 is mentioned. Otherwise most of the information in this manual like diagnostic information is valid for the PCD3.M654x and PCD7.F7500 as well. We are working on a new version.

PROF DP FAIL xxx (or PROF S-I/O fail if Profi-S-I/O is used)
ERR# Description
0 Key word MODE: not found
0 Wrong mode specified
0 Key word CONF: not found
0 DBX key word not specified
0 DBX number error
0 DBX number to large
0 DBX does not exist
0 Key word DIAG: not found
0 Flag or output key word not specified in DIAG
0 Error in address of diag flag or output
0 Range error diag flag or output
0 Register key word not specified in DIAG
0 Range error diag register
1 PROFIBUS-DP HW card not present
2 Error in instruction
3 DBX structure error
4 DBX type not for DP master (no PROFIBUS DBX)
5 FW-DBX version not compatible
6 No IN RING message after timeout on initialization
7 Semaphore error for data exchange (info to PCD support)
8 DBX error: data transfer function not implemented
9 Incompatible PCD7.F750 and PCD hardware

 

The Profibus DP-DP Coupler 6ES7 158-0AD00-0XA0 from Siemens is used to exchange data between two Profibus DP Master devices. The coupler itself acts as Profibus DP Slave and is to be connected to two different Profibus networks. It will copy the "input" of one side of the coupler to the "output" of the other side. This device is used by several customers and works with Profibus DP masters from SBC.

 

Important points when commissioning the 6ES7

• It is important that the modules on both sides of the DP/DP coupler do have an identical size
  When defining the modules, make sure that the size of the modules is identical on both "sides" (networks) of the coupler. Make sure that the "input" area of one side corresponds to the "output" area of the other side.
• The diagnostic bit in for the coupler has several possible meanings:
  - It can indicate "no communication"
  - or it can indicate a configuration mismatch (e.g. different size of the modules)
  - or it can indicate that no communication is running on the onter "side" of the coupler

The diagnostic flag Slave_Err does indicate that at least one Profibus slave has an error.

The error could be that the slave(s) is/are not connected to the Profibus network or that the slave(s) is/are connected to the Profibus network but do have diagnostic information’s.

 

That means that it's possible that a DP or Profi-S-IO Slave does communicate correctly but the diagnostic flag SLAVE_ERR and the corresponding bit on the diagnostic register Base+x is set to high because the slave does send a diagnostic information (for example overload on the output driver) to the master.

The concerned slave(s) number(s) is/are shown on the diagnostic register Base+3.. base+6.

To know the reason for the slave error on the application program it's necessary to perform a scon instruction # 1 "read slave diagnostic data" as described on the manual 26-765.

 

The configuration of the two devices has to match.

 

Problem
On the Saia side the DP configuration is made using the DP-network configurator and definig the modules to exchange. The CP 342-5 communicates using FC's.

Example
In the Siemens programming tool the FC 1 is used for sending data to the master. FC 2 is used for receiving data from the master. FC 3 and 4 can be used for diagnostic and control.
Example Siemens:
      CALL  FC     1
       CPLADDR:=W#16#100
       SEND   :=P#DB119.DBX0.0 BYTE 64
       DONE   :=M100.1
       ERROR  :=M100.2
       STATUS :=MW102

CPLADDR: Is the address of the CP 342-5 in hexadecimal (Decimal=256). This has to be defined in the Siemens Hardware Configuration.
SEND: Is the data to send. In this case the data is located in DB119. The amount of data to send is 64 Bytes.
DONE: Indicates if the function was executed
ERROR: Indicates errors
STATUS: Shows the actual status. For more information refer to the Simatic Manager help.

Example Saia:
On the Saia side we have to configure the same amount of BYTES. Since the Slave sends 64 BYTE the configuration on the SAIA site has to be 64 BYTES as well.
There are two possibilities:
32 word AI constcy complet: in this case the data is mapped to registers
or
64 bytes AI constcy complet: in this case the data is mapped to flags.

The same structur can be used if the Siemens Slave receives data from the master:

Example Siemens:
      CALL  "DP_RECV"
       CPLADDR :=W#16#100
       RECV    :=P#DB119.DBX100.0 BYTE 64
       NDR     :=M200.1
       ERROR   :=M200.2
       STATUS  :=MW202
       DPSTATUS:=MB204

Example Saia:
32 word AO constcy complet
or
64 bytes AO constcy complet

 

Description of a possible malfunction in relation with a DP/Belimo gateway (device S-HER-UN-DP-Belimo Gateway from the company A-M-Systeme)

 

Description of a possible malfunction in relation with a DP/Belimo gateway (device S-HER-UN-DP-Belimo Gateway from the company A-M-Systeme): 

• Profibus-DP network with a PCD as DP master and a DP/Belimo gateway as DP slave
• DP communication woks fine.
• After a download of the application program to the PCD or a restart cold of the PCD the DP/Belimo gateway does show an error message on his display "SPS stopped" and the Error LED of the DP/Belimo gateway is blinking.
  The DP/Belimo gateway is not able to receive and send DP messages.
• On the DP diagnostic of the PCD there is no indication that the DP slave does not work but it’s not possible to read/write information’s from/to the DP/Belimo gateway.
•  A power off/on of the DP/Belimo gateway or the PCD does solve the problem. 

The problem was on the FW of the DP/Belimo gateway and was fixed on the FW 1.24d of the DP/Belimo gateway.

FW versions < 1.24d could have this problem. 

To update the FW of the DP/Belimo gateway please contact your DP/Belimo gateway supplier.

 

On the master PCD the I/O mapping to Register 4096 until Register 16'383 for RIO-networks (Profibus DP or Profi-S-I/O) doesen't work on PCD3 and PCD2.M480 and PCD2.M5xx0 systems with firmware version 1.08.23.

 

Symptom
When using addresses between 4096 to 16383 on the maser PCD for reading/writing medias of Profibus-DP / Profi-S-I/O slaves, no values can be read from these slaves. The relevant registers are not updated by the Profibus or S-I/O task in this case.
This problem does only occur with firmware versions 1.08.xx until version 1.08.31; it is therefore even possible that a project correctly runs until the firmware of the Profi-S-I/O or Profibus DP master PCD has been updated. 

Reason
The reason for this behavior is an incorrect mapping on the Profibus-DP / Profi-S-I/O master done by the firmware of the CPU. This behaviour has been introduced in version 1.08.xx (pilot versions already in 1.07.xx) and is solved in version 1.08.34 and later.

Solution
Please update the firmware of your

• PCD3 to 1.10.16 or later
• PCD2.M5 to 1.10.16 or later
• PCD2.M480 to 1.08.53 or later

If this is not possible for some reason, only use adresses R 0 - R 4095 to map the modules. 

 

The S-Net Configurator distributed with PG5 until version PG5 1.4.130 does impose too strong limitations regarding the amount of modules in the configuration. As result the maximal size of exchanged data can not be reached.

 

Symptom
When trying to configure a Profibus DP or a Profi-S-I/O master station that will exchange more than 160 bytes in- and output data with Profibus DP slaves, the consistency error message
Slave 2 "Slave" :
        Error 601: Configuration too large. Try removing some modules.

appears. Therefore it is not possible configuring the maximal amount of exchanged data.

Reason
There S-Net Configurator does calculate the limits according a very old version of the module PCD7.F750. In this old version (a pilot version) of the module much less memory for the data exchange has been available.

Solution
This wrong calculation of the maximum exchanged data is (will be) corrected in PG5 SP1.4.140. In case you need to configure the network with PG5 SP1.4.130, please contact your local sales office and request an appropriate version of the S-Net configurator (SNet32.exe).

Additional note
The Profibus DP manual states that the maximal amount of exchanged data per PCD7.F750 is 2942 bytes. This limitation does not apply for Saia PCD® COSinus systems (PCD2.M480, PCD3, PCD2.M5xxx or PCD1.M2) where the maximal amount of exchanged data per Profibus DP Master is 2048 bytes.
Note that the maximal amount of exchanged data per Profibus DP Slave is 244 bytes.

 

To communicate with a Siemens Slave it is necessary to place the modules Kennung generell 1-3.

 

    

 

If you change the baudrate in a SNet the new parameters must be downloaded with "Download hardwaresettings".

Rebuild and download also all programs.

 

 

 

 

Yes they are and starting in PG5 1.4 these modules are included in the S-Net Configurator by default. When using PG5 1.3 an import of a recent version of the GSE (or GSD) file is necessary. The firmware of the PCD3.T760 must be V 1.019 or later.

 

Problem
In the S-Net Configurator of PG5 1.3 (DP or S-I/O) the modules PCD3.W800, PCD3.A810 and PCD3.A860 are not implemented.
 
Reason
The mentioned modules are not implemented because at the time PG5 1.3 has been released the modules have not been available.

Solution
Upgrade the firmware of the PCD3.T760 to V 1.019 or later and with right-mouse-click on the T760 device in the SIO-configurator 'Remove Device ...' , delete the actual GSE-file. Then, import the new GSE file into the S-Net Configurator. Note that the new GSE file has to be named exactly 'PCD3.T760'. If the name is different, the S-I/O configurator will not use the new version. Old projects will also work correctly with the new GSE file.

 

When measuring e.g. the temperature of a Pt1000 sensor with a W-module mounted on a PCD3.T760, the sensor type can be configured in the SBC Network Configurator. If this is done this way, negative temeratures are not interpreted correctly on the PCD. Instead of negative values, very high values around 65000 are shown.

 

Symptom
The temperature values read from the PCD3.T760 aren't negative but very high (around 65000). Positive values read are interpreted correctly. All modules that do offer the possibility of reading temperature values are affected (PCD3.W220, PCD3.W340, PCD3.W350, PCD3.W360, PCD3.W745).

Reason
The reason for this phenomenon is the fact that the values transmitted over Profibus DP or Profi-S-I/O are signed 16-bit values. These values are copied directly into the signed 32-bit registers of the PCD. Due to the lack of a transfer function that converts the negative values (and copies the sign bit from the 16th to the 32th bit), the negative 16-bit values aren't correctly interpreted when copied into a 32-bit register.

Solution

An according transfer function has been implemented in the firmware of recent PCD systems. For configuring this transfer function, select the checkbox "Signed" in the Profi-S-I/O (or Profibus DP) Network Configurator as in the screenshot shown. The minimal PG5 version to use this functionality is PG5 1.4.120. The first pilot firmware version supporting the discussed transfer function is $27 for PCD3 and $29 for PCD2.M480.

Firmware versions supporting the transfer function (systems not listed in this table do not support the transfer function mentioned):

PCD System	minmal Firmware version
PCD1.M135	0E3
PCD2.M150	0E3
PCD2/4.M170	0E3
PCD2.M480	030
PCD2.M5xx0	1.08.19
PCD3.Mxxx0	031

On other systems than the ones listed above the following workarounds are possible:

• Reading the raw values from the W-modules (1:1) and then converting these values e.g. in Fupla by using the FBox "20-point-conversion". A table for this conversion accroding to the applied module and senser type can be requested from pcdsupport@saia-pcd.com
• Converting the read temperature values at the very beginning of the COB 0. Because the read values are copied to the PCD registers always right before the start of the execution of the COB 0, this will convert the values always just after the writing into registers. All following COBs created by the user will have the correct values read from the PCD3.T760. An example code for this method is attached to this FAQ. This file also contains guide how to introduce this function into an existing project.

 

No, the GSD-Files are different. They have a different identification. The PCD2.M170 needs the GSD-File PCD2_Slave (SAIAcd20.gsd), otherwise the PCD4.M170 needs the PCD4.M170_Slave (SAIAcd40.gsd)

 

 

 

On Profibus Network it is important to use the right cable and connector as the communication speed goes up to 12 Mbautes!

Those cable and connectors are used in Profibus DP, FMS, Profis S-Bus, Profi S-IO and MPI!

 

Wiring and Network termination should be as follows:

1	Shield
3	RxD/TxD-P
4	CNTR-P
5	DP GND
6	DP +5V
8	RxD/TxD-N
9	CNTR-N

§ix100234§

<dir><dir>

Supplier for 9-pole Profibus D-Sub connectors to connect PCD controllers to Profibus networks:

ERNI Elektrotechnik AG, Brüttisellen, Switzerland:

● ERbic junction, horizontal grey: Erni Ref. 103648
(junction fitted with series inductance of 110 nH)

● ERbic junction, horizontal grey:
with PG connector: Erni Ref. 103663
(junction fitted with series inductance of 110 nH)

● ERbic termination, horizontal yellow: Erni Ref. 103649
(junction fitted with series inductance of 110 nH
plus termination resistors of 390 Ω and 220 Ω)

</dir></dir> 

§ix100228§
ERNI ERbic connector

The cable should be approved by the Profibus norm DIN 19245:

Attached 2 pdf files (both in french and german) of a swiss cable supplier Volland AG 8153 Rümland / Switzerland;

Ref.:    01 0217 0220 cable for fixed installation
            01 0271 0022 fexible cable

Note:    
If the bautrates isn't greater than 187,5 bautes (for ex. Profi S-Bus with PCD3.M3xx / PCD7.D7xx) you can use other more advantegeous cable, especially if the network segment is shorter than 600 meters!
See attached document "Annexe1 CI 2005_11"

 

The serial ports of the PCD2.M480 does allow to communicate up to 115 kB/s.

 

The PCD2.M480 does support the following baudrates:

• For the ports 2,3  and 4,5 following combination of baud rates are not allowed on the same  PCD2.F5xx:
  19,2 kBaud and 38,4 kBaud
• On the port 1 it’s not possible to use the S-Bus party Master mode.
• Mode D is not supported.

The Profibus DP configurator of PG5 1.3 (older than SP1.3.120) does create configuration files that don't run on a PCD2.M110/120 equipped with FW 080 and older.

 

Symptom
The Profibus DP Module can't be initialised. The error LED is lit instead and "PROFIBUS FAIL 000" is entered in the History of the PCD. Profibus DB Master and Slave configurations are concerned.

Reason
The reason for this problem is that the Profibus DP configurator (coming along with PG5 1.3.100 or SP1.3.110) will store the configurations in DBX 4. This address isn't available in FW versions up to 080 (since only 4 DBX are available, address 0 included).

Solution

• Either update to the latest official FW for the PCD2

• Or Update to PG5 SP1.3.120 (or higher)

 

There are basically two tools that are required to solve communication issues on Profibus based networks (like Profi-S-Bus, Profi-S-IO, Profibus DP):

• an oscilloscope to locate hardware related problems (see related topics for more information)

• a protocol analyzer specialized for Profibus based networks

The protocol analyzer we recommend is ProfiTrace (www.profitrace.com) with the Oscilloscope Option. This analyzer bases on an up to date hardware and software concept and is easy to use. The oscilloscope option allows to observe telegrams of specific stations on the oscilloscope, ProfiTrace is generating the necessary trigger signals.

In Switzerland ProfiTrace is represented by  Berner Fachhochschule, Hochschule für Technik und Informatik, please refer to labs.hti.bfh.ch/index.php for more details.

 

 

If a DP slave has a bus interruption in the space of watchdog time, the master station (PCD7.F750)

doesen’t refresh automatically the diagnostic flags and registers.

 

In PG5 SP1.2.130 the analogue module PCD3.W745 isn't implemented. To be able to configure the PCD3.W745 on a PCD3.RIO the latest *.gsd file is required.

 

The corresponding *.gsd file is available on the Support Site under "Browse by product Code/PCD3/Txxx/Txxx".

Ad the new modules using the funtion "Ad device" of the menu "Library" of the SNet32.

 

Depending the PCD type there are up to 3 interfaces to connect the PCD to a Profibus DP or a Profi-S-I/O (or FDL in general) network.

 

Please consult the table below for the correct connection of the Profibus cables:

The Profibus network has to be terminated on both sides of it in one of the following ways:

1. Termination boxes that are placed at the begining and end of the line topologie (solution that should be preferd):

2. For baudrates up to 1.5 Mbaud the termination can also be realized directly on the first and last device of the network. Note that there are also specific connectors with housings with come with the resistors already equipped.

3. For higher baudrates the second solution is not suitable. Inductances has to be add to the termination:

Yes, it's possible.

During the import of the *.GSD or *.GSE file to the Profibus-DP configurator you can select in which groupe you want to store the new file.

You can select the existing groups or you can write a name in to the selection text. This will then create a new group on the device list of the Profibus-DP configurator.

 

Yes, it's possible.
During the import of the *.GSD or *.GSE file to the Profibus-DP configurator you can select in which groupe you want to store the new file.
You can select the existing groups or you can write a name in to the selection text. This will then create a new group on the device list of the Profibus-DP configurator.

<?xml:namespace prefix = v ns = "urn:schemas-microsoft-com:vml" /><shapetype id="_x0000_t75" stroked="f" filled="f" path="m@4@5l@4@11@9@11@9@5xe" o:preferrelative="t" o:spt="75" coordsize="21600,21600"> <stroke joinstyle="miter"></stroke><formulas><f eqn="if lineDrawn pixelLineWidth 0"></f><f eqn="sum @0 1 0"></f><f eqn="sum 0 0 @1"></f><f eqn="prod @2 1 2"></f><f eqn="prod @3 21600 pixelWidth"></f><f eqn="prod @3 21600 pixelHeight"></f><f eqn="sum @0 0 1"></f><f eqn="prod @6 1 2"></f><f eqn="prod @7 21600 pixelWidth"></f><f eqn="sum @8 21600 0"></f><f eqn="prod @7 21600 pixelHeight"></f><f eqn="sum @10 21600 0"></f></formulas><path o:connecttype="rect" gradientshapeok="t" o:extrusionok="f"></path><?xml:namespace prefix = o ns = "urn:schemas-microsoft-com:office:office" /><lock aspectratio="t" v:ext="edit"></lock></shapetype>

 

If GSD files are imported in to PG4/PG5 then this files are stored in a SBC specific format in the files dpdv.dat and dpsaiadv.dt.

If you want to use the imported GSD files on a other PC (with Saia PG5®) or on a other PG5 version then you have to copy the files dpdp.dat and dpsaiadv.dat from the old PC to the new PC

 

It's possible to add non SBC Profibus-DP devices to our PG4/PG5 Profibus-DP configurator. This *.GSD or *.GSE files can be added with the option "library, add device" to the device list of the Profibus-DP configurator.
During the import, the information of such *.GSD or *.GSE files are copied from the *.GSD/GSE files in to the SBC specific files dpdv.dat and dpsaiadv.dat which are located in the PG4/PG5 main folder.

If you like to use the stored *.GSD/GSD information on a other PC or on a newer version of PG5 then you have to copy this two files (dpdv.dat and dpsaiadv.dat) from the old PC to the new PC/PG5.

Note:
For PG4 and PG5 (The user himself has to save the files in to the backup project, and have to restore the files manually.

With PG5 V1.3 the files dpdv.dat and dpsaiadv.dat are saved together with the project during the backup of the project.
A restore of such projects will compare the content of the files dpdv.dat and dpsaiadv.dat stored on the PG5 main folder and the content of the saved dpdv.dat/dpsaiadv.dat and complete the files on the PG5 main folder with the additional information's stored on the saved files.

 

There are confusing screw terminal identifier terminologies around. Depending on the manufacturer the identifiers used are in conflict to the identifiers you can find in SBC manuals.

 

General
RS-485 is a Bus-system, therefore the signal wires shall not be crossed.

Converter	PCD
Rx-Tx (or D)	Rx-Tx
/Rx-/Tx/ (or /D)	/Rx-/Tx

Sometimes "+Data" and "-Data" can be found on devices. Then "+Data" propably has to be connected to "/Rx-/Tx" (or /D) and "-Data" to "Rx-Tx" (or D).

Converters
Some products form other manufacturers (p.e. RS232 - RS485 converters) are often inversly indicated. Therefore it is sometimes necessary to cross the wires.

Converter	PCD
Rx-Tx	/Rx-/Tx/
/Rx-/Tx/	Rx-Tx

Profibus and Profi-S-I/O 

Profibus	Colour	PCD7.T160	D-Sub 9pin on PCD	Port 2 on PCD3.M3 and M6
A=RxD /TxD-N	green	D	pin 8	D
B=RxD /TxD-P	red	D/	pin 3	/D

Example for the port 3 of the PCD3.M5540 as Serial-S-Bus
RS485 connection (Serial-S-Bus) between PCD3.M5540 port 3 (S-Net D-Sub used as RS485 Serial-S-Bus) and PCD2.M5540 port 2 (connector block X3):

PCD3.M5540 (D-Sub "S-Net", port 3)	PCD2.M5540, X3, port2  equipped with a PCD7.F110
pin 3	terminal 2
pin 8	terminal 1

 

On the Web-Editor8 it is possible to ‘transfer’ the user name and the password with the help of session containers, if a url jump to another PCD is executed.

This ‘transfer’ is used to avoid that the user has to enter again the user name/password on the other PCD/Web-Project and works very well on Java and on SBC MB panels.  

But if the Web-Editor8 project is displayed as HTML5 web page then it’s no more possible to transfer the user name/password between different PCD’s and the user has to enter after each url jump his user name/password.

The restriction is not on the Web-Editor8 but on the HTML5 Web-Browser.
Although the HTML5 Web-Browser would have SessionStorage properties, the content of the SessionStorage is cleared in the Browser after each url jump.
Look like that the deleting was introduced to avoid security issues on the Web-Browser

The single sign-on (SSO) authentication which would be suitable for this is not supported in the PCD.

Means that the only solution for HTML5 web pages is, that the user have to enter after each url jump his user name and password to access the web-pages stored on the PCD.

HDLog in WE8: why the navigation in WE8 View including a HDLog-Template  is very slow?

Problem:

You have a WE8 Project containing a view with a HDLog Template. If you display this Page with a Browser (IE/Firefox) the navigation is very slow. If you display this Page with the MB-App for windows or with a MB-Panel, the navigation works OK.

 

Solution:

Open the Device Configurator and check the Parameter “HTTP 1.0 Downgrade Enabled”. This Parameter must be disabled. If this is not the Case, you have to set it to “No”.

During Trend display on an MB Panel the following error message appears. "Out of memory heap 3"

Reason:

The MB Panel memory is divived in different partition called "heaps". The size of each available heap has a default value which can be increased when needed

 

 

Solution:

Acces to the MB Panel parameters by pressing a few seconds on the touch screen

Go to "System/Special/memory" here you see how much memory is used in each heap

By pressing "Setting" (at the page bottom) you access to the available Heap size where each one can be modified. Increase the Heap 3 to maximum 4096 (if needed).

Remark:

Don't increased the size of the other Heap is not necessary. The maximum MB Panel memory size can't be exceeded!

After update to Java Version 8 Update 45 and with the IMaster Java Version 5.15.03 you get this new message window.

 

 

 

Until now we have not e new IMaster Version neither there is a possibility to hide this window.

But you can use our MB App for Windows and you will not get this Window. See Link for more information.

Google released Chrome 42 and with it it disabled all NPAPI plugins by default. This means for us that the IMaster Java Applet will no longer run in Chrome by default.

 

 

Your Webproject look like this:

For now (until the end of 2015) the NPAPI can be re-enabled. To do so open chrome://flags/#enable-npapi in Chrome, click the ‘Enable’ link under ‘Enable NPAPI’ and restart your browser.

 

For more information please check the following Link http://www.java.com/en/download/faq/chrome.xml

If one updates in the Browser his HDLog Trends using the “Reload” button, the new historic trends are well loaded. Nevertheless, the focus of the view is not automatically set to the right, most actual, time. One always needs to scroll to the right to see the most actual logs.                 

With a very small, but precise modification, you can modify the behavior of the “Reload” button. This way, you will force the focus of the displayed trend to the most actual values. No need to scroll to the right in the time-axis anymore.

Here is the description how to proceed.

WebEditor 5:
- Ungroup the used macro from the family “SBCHDLogTrendMacro”
- Select the button “Reload”
- Go into the tab “Actions Set Variables”
- Modify the content of the “Value” field to write the constant “REINIT2” into the specific Container
  variable
- Regroup the macro and make out a template of this macro. So you can re-use it in your next projects

WebEditor 8:
- Select the macro of the family “SBCHDLogTrendMacro”
- Select the “Reload” button through the “Document Outline” window
- In the “Actions” tab you can see which function is called by the button
- Select this function
- Modify the function to do a “Write” “Constant” “REINIT2” into the internal variable
  “ROFST_AvCrvAction_INDCO.”
- You can create a new template out of this macro to be able to re-use it in your next projects
Side effect of "REINIT2":
The command "REINIT2" deletes all in the Browser cached Trends. All the cached Trends of the instance/macro, where the command "REINIT2" is executed will be deleted. This means, that all the Trends of the macro are newly loaded. This results in longer loading times as usually expected.

Please pay attention:
This solution works very well for the actual MicroBrowser Windows Applications (min. V138.2) and the MicroBrowser Panels. BUT, this mechanism doesn’t work with computer browsers that are using the Java Applet. The command “REINIT2” is simply ignored by the Applet v5.15.03. SBC will have to provide this feature in a next Applet version.

If on the Web-Editor8 a container variable is copied from the Web-Editor8 help file with copy paste in to the Web-editor8 painter, then it’s possible that not only the name of the variable is copied but also an invisible 'CR''LF' character.

In such a case, the container variable name does not correspond to the required name and the special action of this container variable is not performed.

 

Example with the container variable 'MB_InactivityCounter'
Copy form the Web-Editor8 file


Paste in the Web-Editor8 painter.


How to find out such variables?
Open the wvar file and check the ‘internal variables’ Tab.
The line of a variable which does have a at the end of the name is shown as a double size line.
Means that on the first line the name of the variable is shown and on the second line empty line is shown.



How to solve the problem?
On the wvar file do click with the right mouse key to the concerned variable and select rename.


On the next window put the cursor at the end of the variable name and press the Backspace button of your keyboard (the invisible will be deleted) and on the next step select all places where the variable should be replaced.


After the update the new and the old variable are shown in the wvar file and after clicking to the update button only the variable without is shown on the screen.

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.

 

It’s possible, that during the development of the web page in the web-editor8, a copy/paste of a PCD variable name in to a edit field of the web-editor8, does insert at the end of the PCD variable name a (non visible) 'CR''LF' character.

This 'CR''LF' character leads then to situation that the value of the PCD variable is not displayed during runtime and in the field the text ‘no such component found’ is shown.

 

How to find out if this 'CR''LF' character is present in the variable?
Do open the *.tcr file (located in the bin folder of the web-editor8 project) with an external text editor.

Each PCD variable should be displayed in one line as following:
My_symbolic_var_name;PDP,,PCD_absolute_address,Format; ; ;Format displayed on web-browser; ; ;

For example:
The register 2538 does contain the actual time of the PCD in the format HH:MM and does have the name 'Actual_time'.
In the *.tcr file, this variable should be shown as:
Actual_time;PDP,,R2538,D; ; ;HH:MM; ; ;

If a variable is displayed like this (splitted in two lines) in the tcr file:
Actual_time
;PDP,,R2538,D; ; ;HH:MM; ; ;

Then there is a 'CR''LF' character at the end of the variable name.

Ho to solve the problem?
In web-editor8, on the concerned edit field do change the text type from PCD to INT (so the field content will be cleared) and change again back to the type PCD.
Browse or enter the variable name like Actual_time with the keyboard
(do not use copy and paste of the name)
Compile the project and do check the tcr file with an external text editor.
Now the variable should be displayed in one line.
Actual_time;PDP,,R2538,D; ; ;HH:MM; ; ;

Remark:
Make attention also to not user the copy/paste function if you use the container offset option and you want to insert the internal variable name.
Actual_time+@COFF_my_offset@

 

Web pages stored on the PCD which where displayed without problems on the web-browser of the PC does show a Java warning message after the update of Java to the Java version 7, (update 6 or 7).

 

Symptom
If you want to display a web page on the browser of the PC then the following warning is shown on the screen:

Because there are a lot of the same warnings that appear, you have the impression that the click to Yes or No has no effect but in fact there is another identical message that will appear afterwards. There will be about 30 of these messages. This warning will appear independent of the version of the jar-file that is used in the project.

Solution for applications where the java applet IMasterSaia5_15_02.jar or IMasterXX7_5_15_02.jar is used:
Do download the IMasterSaia5_15_02.jar version 5.15.0229 (with date from the 16.09.2013) stored on our homepage, section PG5 2.0/S-Web editor and do replace the existing .jar files in your project directory and/or to the PCD with the new one.
Do copy also the two files in to the S-Web editor 5.15.02 directory so that this files are also used for new projects.
This java applet version 5.15.0229 or later does contain the new certificate.

How to detect the version of the IMasterSaia5_15_02.jar file?
Display the web-editor web page on the browser and do open the java console.
There the version of the java applet is shown as following:
§ix101566§


For PG5 2.1. 
Since the version $2.1.053 of PG5 2.1, the two jar files which does fix the problem are installed together with the S-Web Editor 5 and the S-Web Editor 8

Possible workaround for applictions where any version of the IMasterSaia/IMasterXX7 applet is used. 
A workaround for this problem is do change the following settings in the Java Control Panel.
The Java Control Panel can be found under Settings -> Control panel of the Windows operating system.
On the folder 'Advanced' so select the option 'Security, Mixed code (sandboxed....)' to 'Enable - hide warning and run with protections'
Close the browser and re-open the browser.


Remark
The same workaround is also available for Mac Computers which have Java from Sun Microsystems installed.

 

It is possible to change the favicon (icon in the tab of a browser) to your own wishes, in the following FAQ it is described how to proceed.

 

You can generate a favicon from your or your customers logo to be represented in the tab of the browser, as default a SBC web logo is displayed:



On the internet you can find tools to convert a picture (*.jpeg, *.png*.gif…) to a file called “favicon.ico”. This file is 16x16 pixel small, therefore it is recommended to use a simple logo. (favicon-generator.org)

The favicon icon must have the file name favicon.ico and has to be added in the webserver, either on a flash memory (folder: /webpages) or in the *.wsp file (Webeditor 5). After this is added in the web server the tab of the browser should look different:



For Webeditor8 you must set up the following options:



If the Webeditor program has to be downloaded to the program memory of the PCD (into a dbx), this can be done with the following webbuilder options:

In a WebEditor project we select to display a page that contains a SBCHDLogTrendMacro e.g. RemoteOffSavedTrdMinimal.

The trends are not displayed, but an error message appears that CSV-Files could not be loaded.

 

 

Symptom
The Applet tries to load the csv-file Filename_D120118.csv, but in the Fupla HDLog File FBox you haven’t configured to create data files per day, but per week or per month. The letter "D" in the csv files stands for "D"aily log file. Other combinations are also possible, as the applet would try to load the file Filename_W01201.csv or Filename_M1202.csv. But, perhaps, it was not configured this way round in the FBox. "W" stands for weekly file and "M" for monthly file creation.

Reason
This happens if you change afterwards the setting of the parameter "create data" in the HDLog FBox but you have already placed the Macro from SBCHDLogTrendMacro before in the Webeditor project. It's the same behaviour in PG5 1.4 and PG5 2.0.

Solution
After changing the parameter "create data" e. g. from day to week, you must delete the Trend macro that belongs to this FBox in the WebEditor project and replace it. The WebEditor feature "Project/Reload HDLog Files ..." doesn't solve this situation. After rebuild /download of the project the problem is solved.

 

When displaying a certain teq view, the MicroBrowser (MB Panel, CE Panel, iPhone & iPad App) stops working and displays the error message "file not found xxxx.teq" where 'xxxx.teq' is the name of the teq view from which the jump was executed. This problem occurs due to an invalid 'PLC-ID' inside a Macro used on the concerned teq view when compiled with a Web Editor 5.15.0200.

 

Symptom
All macros edited or created with a version between and including 5.14.30 and 5.15.0200 contain an invalid PLC-ID, this leads to either an error in the Message Box “Invalid PLC-ID” or to the fact that the MicroBrowser freezes when jumping to another page. When the MicroBrowser blocks, the message “file not found xxxx.teq” is indicated, where “xxxx.teq” is the name of the teq view from which the teq view jump was initiated.

Solution
Build the Web Editor project with a Web Editor 5.15.0221 or more recent, this eliminates the error.
The Web Editor 5.15.0221 is part of the PG5 2.0.220.

Remark
If it is not possible updating PG5 or the S-Web Editor, the option "Force Teq Files Saving as…" in the menu "Project Configurations" --> "Build Options" can be disabled in order to avoid the problem.


Other possible cause
The text PPO used for the password for ex. level1Pw, level2Pw, etc have no Format defined in the PPO list (Web-Editor 5) or der WVAR (Web-Editor 8) file.
They have to be defined with the Format "STRING"!

 

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.

 

When displaying the alarm page on VGA Web Panel this error message appears in message window and the alarms aren't display!                 

It has always been possible to configure password levels in the Settings tab of the Web Builder. This configuration has been moved from the Web Builder to the Device Configurator if when le firmware version "From 1.14.00 or more..." is selected in the Device Configurator!

 

Symptom
The Webserver password levels (1 to 4, for no access over only readable to full access) configured in the Web Builder are no longer active after having updated the PG5 project and the PCD firmware to version 1.14.23 or more recent (and in the Device Configurator the option "Firmware from 1.14.xx or more recent" is selected).

Reason
Until FW 1.14.00 the password configuration was done over the Web Server Setting window:

Since the FW 1.14.00 the configuration of the web server passwords can also be done over the Device Configurator from PG5 2.0.150 or later with the following parameters:


Remark
As the configuration in the Device configurator has priority even if you have selected "Advanced parameters: NO" the configured passwords in Web Builder settings won't be working.
The configuration isn't loaded in the same place into the PCD memory as where the WebBuilder settings are loaded.

Solution
For new projects (on PCD1.M2, PCD2.M5 and PCD3 systems) we recommend to use the Device Configurator for the configuration of the webserver passwords. Therefore, configure the password over the Device configurator by choosing: "Advanced Parameter: Yes" (see screenshot above).

For "older" projects where the webserver passwords configuration has been done over the Web Builder settings the following possibilities exist:

• move the configuration from the Web Builder to the Device configurator or
• change the Device Configurator to FW Version parameter to "Before FW 1.14.00" (even the PCD has a FW version >= 1.14.00)

FAQ #101004 describes how to launch the Microsoft IE in the kiosk mode. But without additional settings the scrollbars are always displayed on the browser.

 

By default, the Webpages are displayed in the browser with a small border all around the web page. This effect forces the web pages to be slightly bigger than the specified size of the S-Web application defined in the S-WebEditor. That's the reason why the scrollbars of the browser are automatically displayed to access the entire web page.

How to disable the scrollbars?
If you don't want these scrollbars you can disable the automatically added borders by manually including a line in your "Start.htm" file.
This line sets the margin to "0" and disables the scrollbars.

Procedure
Open your "Start.htm" file in a text editor (e.g. Notepad) and manually add the line as shown in this attached screen capture:

 

Since the FTP server of the PCD has been developped, SBC suggested to use the freeware FTP Client Filezilla to access the PLC Filesystem.

Lately and with newest FileZilla versions we received several reports that there are difficulties with the FTP Client FileZilla (e.g. that the IMasterSaia.jar was not completely downloaded).

 

Symptoms
There were problems while downloading several files in parallel to the PLC Filesystem. And sometimes it wasn't even possible to download the IMaster.jar file, because there was infinite repetition of downloading from side of the FTP Client Filezilla. After a restart of the PC, FileZilla worked again properly.

Reason
Unfortunatley these phenomenons were often not reproducible in Murten and appear to be random. Therefore it is very difficult to pinpoint the reason for the problems.

Conclusion
As these problems are only concerning few installations we do not intend to "forbid" the usage of the the FTP Client FileZilla together with the PCD FTP Server. However, in case you are faced with the above mentioned problems we suggest to use another the FTP Client. One client with which we made very good experiences during the past yars is the one coming with the shareware "Total Commander" (shareware). "Total Commander" also exists as portable version.

In some cases increasing the timeout in Filezilla to 60 seconds helps.

Update 03.07.2013
On FileZilla there is an option to limit the transfer speed.
Switching on this speed limitation does allow loading without problems files to the PCD.

To enable the speed limit, click on the tachometer symbol (on the bottom right corner of the FileZilla window)


On the next window do select the option "Enable speed limits" and do set the values to 100/20 KiB/s.

 

The following error appears when attempting to open the web builder in a windows XP 32bits System.

"No license found on this computer, will run in DEMO mode." after the installation of PG5.2.0

 

 

Symptom
The following error appears when attempting to open the Web Builder from PG5 2.0 (on a Windows XP PC, 32bit):

“No license found on this computer, will run in DEMO mode. Limit is 2 HTML pages on the project”

Reason
The cause of this problem is that the library "SCRRUN.DLL" was not registered in Windows for some reason.

Solution
The SCRRUN.DLL can be registered by using the command "REGSVR32" from Microsoft Windows. "REGSVR32" (Microsoft© Register Server) is a command-line utility present in the Windows operating systems for registering and unregistering DLLs and ActiveX controls in the Windows Registry. The missing scrrun.dll is a Microsoft Script Runtime DLL Library.

Procedure for registering SCRRUN.DLL

• Open a Command Prompt (Start Menu --> Run --> COMMAND) and press ENTER
• Change directory to the WINDOWSSYSTEM: For XP systems, this is normally the folder:
  C:/WINDOWS/SYSTEM32
• Type the following command:
  REGSVR32 SCRRUN.DLL and then press ENTER
• You should see a successful confirmation message. If not, make sure you typed the command correctly (and that the command is executed in the correct directory).

If you open the standard status page on a PCD there are some additional parameters shown which aren't obvious.

 

You can display the status page of a PCD with the URL
(address of PCD)/status.htm



Please find the necessary informations in the following text.

Speed:
Time assigned to the Web Server task in milliseconds.
Range: 1..15
Default: 5
Requirements: PCD3Mxxxx, PCD2M5xxx, Firmware > 1.10.00

Priority:
Priority of the TCP Web communiction driver in the Web Server.
Range: 1..12 (1 means highest, 12 lowest priority)
Default: 10 (standard port) and 5 (command port)
Requirements: PCD3Mxxxx, PCD2M5xxx, Firmware > 1.10.00

 

The memory requirement of a "HDLog to File" FBox (log in csv format) is calculated as follows:

Possible records = 50% of memory capacity (in bytes) / required characters per record (in bytes). Further on the maximum amount of files per file system is to be considered (around 850 files per SD card).

 

Memory available on a 1 GByte SD card
1 GB SD Card (PCD3.R600 with PCD7.R-SD1024) has 1’073’741’824 bytes
Note: It is not recommended to fill the SD card completely; in general we recommend only using 50% of the available memory in case data is written (and deleted) regularly.
Further on the maxumum amount of files per SBC file system is 900 in total, and every directory counts as 20 files (because the folder "WEBPAGES" and "CONFIG" always exists, the maximum amount of files which can be created on a SD card is around 850 (860 to be precise).

Memory requirement of log files
The memory requirement of files created by the "HDLog to File" FBox (log in csv format) is calculated as follows:
Possible records = 50% of memory capacity (in bytes) / required characters per record (in bytes)

Examples

• Writing 30 values to an SD card
  In case 30 values are to be recorded:
  Each value has an average number of six characters (exp. 123,4).
  Each HD Log File FBox requires 30 characters for the date and timestamp.
  So 30 record sets, subdivided into 3 FBoxes requires about 270 bytes per record (rounded about 300 bytes per record, including date and time stamps).
  1 GB SD Card (PCD3.R600 with PCD7.R-SD1024) = 1’073’741’824 bytes
  This results in about 3,500,000 entries. Due to the fact that you should not fill the SD card over 50% there remain effective 1'700'000 entries.
  At a recording interval of 5 minutes the SD card has space for about 16 years, given one file per month is generated (--> 16 years * 12 files/year * 3 FBoxes = 576 files)
  
  

  Remark regarding this example
  In case one file is generated per week, after around 5.5 years it won't be possible creating more files because of the maxumum number of files per file system has been reached (5.5 years * 52 files/year * 3 FBoxes = 858).

  
  
• Writing 3 values to a PCD7.R550 memory card
  In case 3 values are to be recorded:
  Each value has an average number of six characters (exp. 123,4).
  Each HD Log File FBox requires 30 characters for the date and timestamp.
  So 3 record sets can be recorded with one FBox and requires 48 bytes per record (rounded about 50 bytes per record, including date and time stamps).
  1 PCD7.R550 module = 4'000'000 bytes
  This results in about 80'000 entries. Due to the fact that you should not fill the SD card over 50% there remain effective 40'000 entries.
  At a recording interval of 1 minute the memory module has space for about 1 month (28 days) 

 

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).

 

In case the dynamic space of registers is defined below 1000 or above 9999 the FBox HD Log to file cannot create the Logfiles correctly

 

Problem
If the dynamic space of registers is defined <1000 or >=10 000 the FBox HD Log to File is not able to create the Logfile correctly. The FBox is using interpreted text with $R commands. Due to a problem in the FBox this won't work for registers below 1000 since they only have 3 digits $Rxxx and the interpreted text needs 4 digits. Also in case the dynamic space is defined above 9999 the interpreted text won't work correctly, because the last digit is cut off by the firmware.

Solution
At the moment the dynamic space has to be defined >=1000 and <10 000 otherwise the FBox HD Log to File will not work correctly. The FBox library will be corrected for a dynamic space below 1000. To define the dynamic space above 10 000 a correction in the firmware will be necessary. As soon as a correction is available, this FAQ will be updated.

 

In some situations it is possible that the FBox "HDLog to File" is writing the same values several times (even if no change of value has been detected) to the *.csv file.

 

Symptom
When viewing the file creatd by the "HDLog to File" FBox it can be observed that in some cases several lines have been created (despite of the fact that the values did not change or the cyclic writing has not been due).

Reason
In case a "Write to file" command has been executed (and thus the buffer has been written to the file) and no new values have been written to the buffer, browsing the trends on the S-Web project could lead to re-writing the same (last) value to the file.

Solution
The FBox library version listed below do avoid the re-writing of an already written entry to the *.csv file.

• PG5 1.4.300: HDLog to file FBox library version 2.1.040
• PG5 2.0.110: HDLog to file FBox library version 2.6.150

There are different formats of GIF-files which need to be considered as not all formats/features are supported by SBC S-Web products.

 

In general there is a differentation between the GIF-file formats "87a" and "89a". The version "89a" includes all features from the version 87a but adds new features such as the possibility to provide animated graphics.
On all SBC products the format "87a" is fully supported while some features from the format "89a" are not supported on all devices (e.g. PCD7.D4xx).

Supported features on a MB Panel PCD7.D4xx

• Transparent GIF, if within the GIF less than 256 separate colours are used.
• GIF interlaced and non-interlaced – The GIF is drawn however in one go after full reception.

Restrictions related to *.gif files on the MB Panel

• Due to hardware relations, the QVGA Panel will not be able to display transparent GIFs
  
• Only the VGA Panel supports transparent GIFs in which case on the transparent pixel either the background or the inner colour setting is shown if this is configured. This inner colour drawing is also drawn on the full painter area and shown on the transparent pixel in the GIF image part that is below the outline under a dotted/dashed outline.
• A 3D border is not used.
• No split canvas / background and image frame handling (single full frame). For the canvas size the frame size is taken.
• No multi frame / image GIF file support (no animated / sequenced GIF). 
  For sequenced GIF file the first frame is taken. This may only partly display the wanted image.
  Note: The animated GIF macro from the S-Web Editor bases on a sequenced display of GIF files. The single gif files are not animated.
• No full colour support of the used 24 bit colours out of the given colour table.
  - On the VGA 16 Bit in a RGB 5-6-5 bit scheme is used, on the QVGA 8 Bit in a 3-3-2 Bit scheme is used.
  - For the colour rounding a grey scale nearest value is taken.
  - On the VGA the GIF uncompressing and this rounding can be checked using the screen dump feature
    that dumps the used RGB16, 5-6-5 code pixel code in an uploadable  uncompressed BMP16 file.
• No GIF meta information support, no GIF coded text support.

When using a GIF-files in format "89a" (incl. animation) the following phenomenons can be observed:

• everything works fine in the Applet 5.14.27 displayed on a PC

• display works, but no animation is done on a VGA MB Panel PCD7.D4xxV with firmware 1.12.11 and newer
  

• display doesn't work at all and only a rectangle with a red cross is displayed on a VGA MB Panel PCD7.D4xxV with firmware 1.12.11 and newer

Here are some possibilities how to generate or convert any type of picture into GIF format "87a"

• "GIMP": use the free graphical editor "GIMP" and save any picture as *.gif. If necessary select "fit picture" to not save an animated GIF when you're prompted. Just to be sure to generate a GIF file of format "87a".
  Get the most actual version of "GIMP" from the download website www.gimp.org/downloads/
  
• "Imagemagick": use the portable version of the conversion tool "Imagemagick" and run a batch-file to convert a whole directory of GIF-files into "87a" formatted GIF files.
  Download the portable version from www.imagemagick.org/script/binary-releases.php
  Copy the attached batch-file and the expanded zip file of "Imagemagick" into one directory. Also copy all *.gif files to be converted into the same directory.
  Start the batch file with a doubleclick. The converted GIF-files will be stored in a new directory named "gif87".
  

As soon as a curve is added to the HDLog to file macro it is not possible to compile the project anymore.

 

Problem
In Fupla the FBox HDLogFile was placed. In WebEditor the file is added under Project configuration and the according macro is added to a teq file. As soon as you add one trend-curve to the macro it is not possible anymore to compile the project. An errormessage similar to the message below appears:

Error 2009: WEB_PG.obj: Unresolved external symbol: __stc_id_0000C_var_00___SG_COB_Daten
Reason
This problem happens, if in Fupla the option "Use predefined symbols" is not activated. Since the HDLog FBox has internal symbols it is necessary to activate this option, to have the proper functionality.

Solution
Activate the option in Fupla under View/Options. In PG5 2.0 you have to activate the options:
Use predefined symbols: Yes
Delet internal: Yes
In PG5 1.4 you have to activate the options:
Use predefined Symbols
Delete internal symbols when the FBox removed

Then in the fupla you have to:
-right clic on the Fbox "HDLog" and choose "Add Predefined Symbols..."
-save the file

Then in the Web Editor you have to:
-remove the macro "HDLog"
-delete and select one more time the file *.HDF in the menu Project ->Configuration
-add the macro "HDLog" ,choose "Keep For All"

 

The alarm texts generated by DDC Suite are quit long and are in some cases not complete displayed with the default alarming macro. There's a description in FAQ #100711 how to modify the columns width. This FAQ contains an example which applies well to the screen dimensions of a VGA MB Panel PCD7.D4xxV.

 

Step-by-step example Web Editor 5

• In the Web-Editor 5 open the page with the alarming macro
• Double click the alarming macro, so that the window "GROUP" opens
• Select the tab "Cross Ref". In the cross reference list select entry "STRING "#sp;…."".
  The start position of the individual columns are defined in this string in the order: 
  StateColour, ID, Alarm text, Time on, Time off, ACK/NAK, Counter.
• Replace the default string by this string: "#sp;120,0,5,71,120,90,95\n" and don't forget to click 'update' to validate the changes.

Step-by-step example Web Editor 8

• In the Web-Editor 8 open the page with the alarming macro
• Rightmouse click in the alarming macro, choose "Cross Reference"
• Choose in the upper part for the "Filter by type" ALL
  
• Select in the Cross Ref Table the column with the Type "STRING "#sp;…."".
  The start position of the individual columns are defined in this string in the order: 
  StateColour, ID, Alarm text, Time on, Time off, ACK/NAK, Counter.
• Replace the default string by this string: "#sp;120,0,5,71,120,90,95\n"
  §Ix101640§
  

• The numbers entered stand for the percentage of the total width of the alarm list where the according column starts. So the "ID" column starts at 0% of the whole width of the alarm list, and the "Alarm text" starts at 6% of the whole width fo the list etc.
  The value 120 will disable the according column (in this example the "StateColour" and the "TimeOff").

As result, the alarm list will be drawn like the below attached screenshot:
§Ix101641§

Remark
Please note that the S-Web Editor 5.14.27 or later is required for this configuration (otherwise the "\n" will not work)

 

You can extend the HDLog FBox to log a maximum of 10 trend variables. If you want to log more than 10 trends, you'll have to place several HDLog FBoxes.

 

The HDLog FBox you place has to get a unique reference name. Because the CSV-file, that contains the maximum of 10 trend variables, is combined to this unique name. If you want to log more than 10 trends, you'll have to place an additional HDLog FBox with another unique name referenced. Because these additional 10 trends are logged into a second CSV-file combined to the second unique name. This means, that in one single CSV-file you can log a maximum of 10 trends.

 

There are some very useful recommandations / restrictions that should be respected when engineering an S-Web Editor project for VGA MicroBrowser Touch-Panels PCD7.D4xxV.

• The maximum size of a GIF-picture is 256 kB
• The maximum dimensions of a GIF-picture is 638 x 478 pixels
• It's recommended to use text fields that are around 20% larger than the text that is displayed in the S-Web Editor. For more details, please refer to the user's guide of the MB Panels on the support site.
• The maximum size of a displayed offline trend is 1024 kB
• A maximum of 512 painter objects can be displayed on one TEQ-view. Please note that also a simple line counts as an object. As reference: the "offline-trend" macro uses 40 objects
• According our experience, there can be displayed up to 320 registers or 500 flags on one single TEQ with reasonable speed
• One line in a TCR-file must not exceed 128 characters. This affects the choice of the size of a variable
• In a CSV-file, one line must not exceed 128 characters when programming in ASCII code, and 64 characters when programming in Unicode/UTF-16

When you use HTML tags in csv-file with the S-Web Editor 5.14.27, unused tags in *.csv files are detected (and the S-Web Editor asks whether to delete these lines in order to increase the performance of the panel in runtime).

 

In normal use you don't even remark this feature, because it's done in background when you delete a macro, for example.

Remark when using indexing
However, if you add on your own some HTML tags (i.e. when indexing variables with an expression like e.g. ...@Index_PPO@), the S-Web Editor detects that there are HTML tags that don't belong to any macro. It therefore asks you whether you want to remove these tags with the message:
'WARNING found HTML tags in csv files that are no more used in actual project. Do you want editor to delete those HTML tags?'
--> If you work with the above mentionned indexed variables, remember to click 'No'!

Remark
In the next service pack of the S-Web Editor (Version 5.14.30) this warning will have an option to hide.
This version is available in Service Pack 1 for PG5 2.0 (PG5 2.0.150). For PG5 1.4 the S-Web Editor version 5.14.30 can be downloaded from the support site.

 

The new WebServer 2 implemented in the PCD3 and PCD2.M5xxx supports caching and therefore the loading of the Java Applet can be avoided when reloading web pages. From firmware version 1.10.16 on you can profit of the caching possibility of the Java Virtual Machine.

 

How to activate caching?
To activate caching on the Java Virtual Machine you select on your local computer 'Start -> Settings -> Control Panel -> Java'. In the tab 'General', click on 'Settings' and under 'Temporary Internet Files' check the box for 'remain temporary internet files on the computer'.

Remark
Please note that in case an older firmware than 1.10.16 is loaded on the PCD, it might be that values of the web project are not refreshed correctly (see FAQ 100708).

 

When building a project with HDLog FBoxes the build fails with the message "Down.wsc Line xxxx Symbol not defined_stc_id_0016_var_00" or similar can be caused by an incorrect setting in the Fupla options.

 

Symptom
After having used the FBoxes from the family "Historical Data Logging" in a Fupla program for the use with a Macro for HD Log from file in the Web Editor the build fails. The error message indicates that symbols are not defined.

Reason
The HD Log FBoxes is creating automtically internal symbols for the use in the Webeditor macros. These symbols should be created automatically when adding the FBox to a project. If this is not the case the symbols are missing on build time and therefore lead to the error mentioned above.

Solution
you have to activate some options in the Fupla: Under View/Options:

• Use predefined Symbols
  If this is unchecked the FBox symbols are not created when adding the FBox. Make sure this optoin is checked!
• Delete the internal symbols when the FBox removed
  If this is unchecked the internal symbols stay in the symbol list, even if the FBox is removed from the project. It is recommended to have this option checked, too.
  

Remark
If the FBox is already part of the project you can add the internal symbols to the symbol list with right click on the FBox and choosing "Add predefined symbols".

 

When trying to compile an S-Web Editor project on a PC running a Chinese Windows the error message "DBX initialization data too big" is displayed and the build fails.

 

Symptom
When trying to compile an S-Web Editor project on a PC running a Chinese Windows the error message "DBX initialization data too big" is displayed and the build fails.

Reason
Due to a restriction of older versions of the S-Web builder it wasn't possible to compile a PG5 project containing an S-Web Builder project on a PC running a Chinese version of Microsoft Windows.

Solution
Since the version 2.0.100 of the S-Web builder it is possible to compile PG5 projects which contains a Web-Builder file on a PC with Chinese Windows.

Remark
Please note that the version Web Builder version 2.0.100 does not support "non ASCII characters" like for example Chinese characters on the *.htm/html or *.tcr files.
This means that it isn't allowed to define:

• a PPO name in the S-Web Editor which does contain a "non ASCII character" or
• a "PDP,,"-syntax wich contains a "non ASCII character" within an htm/html file

Where can I get the S-Web Builder version 2.0.100?
Please contact your local Saia-Burgess Controls AG representative.

 

Webpage doesn't get displayed at all when selecting an incorrect "base ppo name" in the trend macro.

 

Problem:
When trying to open the webproject the java applet is not loaded and the error message in the Java console is:
java.lang.ClassNotFoundException: IMasterSaia5_xx_yy.class.

Possible Reasons:
Wrong "Base PPO Name" selected.

Solution:
You have to enter the symbol name of the "Data DB" output of the "HD Init" F-Box.

 

In order to prevent that someone do copy the web pages which are stored on the file system (memory module) of the PCD, it’s possible to convert the content of the web-pages in a DB of the PCD with the use of the web-builder tool.

 

For S-Web editor project’s we do recommend to convert the *.teq files in the web-builder.

 

 

Using an indirect connection of the web-connect software on the CE web-panel (PCD7.D5xxx) it’s possible that a remote PC is able to load the web-pages stored on the PCD/PCS.

 

 

Requirement
On application the PCD/PCS is connected over serial line to a CE web-panel and the end user wants to display the web-pages stored on the PCD/PCS on the CE web-panel and on a remote PC.

Solution
With the help of the web-connect SW on the CE web-panel it's possible that the any PC on the TCP/IP network is able to establish an indirect TCP/IP connection to the web application stored on the PCD/PCS and to display the web application on the browser of the remote PC.

Open the web-browser on the remote PC and type the IP address of the CE web-panel, the connection name defined on the web-connect software and the name of the startpage in the navigation bar of the browser.
Example: 172.16.1.64/pcs/start.htm

172.16.1.64=IP address of the panel
pcs=web-conncect connection name
start.htm=name of the start page

Remarks
Instead of a CE web-panel there can as well be an ordinary PC, connected over the web-connect software to the PCD / PCS. The procedure is the same.
It is not possible to use a Microbrowser QVGA panel for this kind of connection.
The Microbrowser VGA panel doesn't support this functionality at the moment; but it's planned for the future.

 

When using text PPOs they have to be defined as STRING in the PPO list. Otherwise this can cause strange errors.

 

Problem
When opening the Web Application some strange characters are displayed on top of the page followed by a warning button inside the java applet.

The error message in the Java console is:
"java.lang.ClassNotFoundException: IMasterSaia5_14_00.class"
or similar.

Reason
Text PPO have to be declared as STRING in the PPO list. If there is no definition it won't work.

Solution
Define all text PPO as STRING in the PPO list.

 

The WebServer2 is a re-implementation of the previous WebServer on Saia PCD® COSinus systems and of course compatibel to the previous version.

 

History
The first implementation of a Web Server on PCD systems has been realized around the year 2000. With growing experience additional features and higher performance have been requested. In order to fullfil this requirement, the WebServer has been re-implemented (with the result of the WebServer2).

What is new in the WebServer2?
In general the WebServer2 is functionally compatible to the previous implementation. In addition the following new features are supported:

• HTTP 1.1 support
• HTTP caching is supported. As result the in FAQ 100708 is no longer to be applied; It is recommended to enable the caching for the JVM (option "keep temprary files on PC") when working with the WebServer2.
  
  Remark: If the caching is not enabled, you will not profit from the supported caching; it will then work as it has before with the previous WebServer. 
• Better performance
• Parallel acces to files is properly supported (acces is no longer interrupted if another client loads the IMaster applet)
• Multiple Web clients can access the Web Server on the same physical interface with (Ether-S-Bus or Profi-S-Bus)
• Easier understandable error messages
• When texts are entered, the length of the text is specified (and no longer filled up with space characters)
• The WebServer2 does provide more information on the default page and has a nicer look. By viewing this page it is easy figuring out whether the WebServer2 is running on a PCD
  

  View of previous WebServer	View of WebServer2

Firmware (FW) supporting the WebServer2
The table below indicates the first firmware versions supporting the WebServer2. Systems not listed in this table do not feature the WebServer2.

PCD system	pilot FW version	production FW version
PCD2.M480	1.09.38*)	-
PCD2.M5xx0	1.09.38*)	1.10.16
PCD3	1.09.38*)	1.10.16

^*) Please note that in the first pilot firmware not all features have been supported.

Remark
The only incompatibe difference between the previous WebServer and the WebServer2 concerns users that use the "HTML forms":

• The previous Web Server used:
  %%TAG%
• The WebServer2 expects (the "value" is no longer automatically added by the Web Server):
  value=%%TAG%

An example for the HTML forms on the WebServer2 can be found in the attached document.

 

This Time Allocation has only an influence on the old systems PCD2.M1x0. For all new NT systems like PCD3.Mxxx and PCD2.M5xxx it has no influence.

 

Web Server Time Allocation:
In the Webbuilder under Settings it is possible to choose the "Web Server Time Allocation". You can choose between "Low", "Medium" and High" Priority. This will change the priority of the Webproject. With high priority the Webproject is treated more often. Otherwise the program on the CPU will be slower.

Important:
This setting has only an influence on the old systems PCD2.M1x0. For the new NT systems like PCD3 and PCD2.M5xxx it doesn't has any influence.

 

In some cases the address bar of the Windows Internet Explorer (IE7) is not desired and shall be removed.

 

To hide the address bar on the Windows Internet Explorer or to put IE7 into fullscreen mode just execute the following steps:

• Open "Run..." from the Windows start menu
• Type: "gpedit.msc"
• On the new displayed window "Group policy" browse to the menu:
   User Configuration\Administrative Templates\Windows Components\Internet Explorer\
  There are many options here which you can enable.
• If you enable 'enforce full screen mode' then that will hide and disable everything except the status bar.

The error message is shown, if the browser on the PC does need a java applet and the java applet is not loaded.

Web-Pages which are created with the S-Web editor does need a java applet.

 

Problem
On the webpanel (Microbrowser) the webpage is visible and works fine, because the java applet is integeated in to the firmware of the webpanel.
But if the webpage is displayed on the browser of the PC, then the browser needs to load the specifc java applet to be able to display the webpage correctly.
If the browser is not able to load the Java applet then the follwoing error message is displayed on the Java console:
java.lang.ClassNotFoundException: IMasterSaia5_xx_yy.class.

Reason
The reason for this behavior is, that the browser on the PC is not able to find the IMasterSaia.jar file.

Solution
Add the IMasterSaia.jar file to the PCD either by selecting the file in the web-builder or by copying the file over FTP to the flash card of the PCD.
In case Webconnect is used for the connection it can as well be placed in the Webpages folder on the PC.
 

 

If on a web-page with trending or alarming after clicking the button "Save Logs to file" the Web-Application is no more reacting then it’s possible the Java security settings are the reason of this trouble.

 

Symptom
The Web application running on a PC (e.g. in the Internet Explorer) does no longer work after the button "Save Logs to file" has been clicked.

Reason
In this case it is very likely that the security settings of the browser does not allow the Java virtual machine (VM) to access the file system.

Solution
Please refer to the chapter "Java Security Settings (For Microsoft VM)" in the attached extract of the manual of the S-Web Editor. Alternatively, you can also refer to the on line help of the S-Web Editor (refer to chapter "Java Security Settings (vor Microsoft VM)")

 

During the use of the Internet Explorer on a Panel eXP, it can happen that the values of the PCD are not refreshed during several minutes.

 

Symptom
The values of PCD medias (PPOs) shown on a eXP Web Panel (PCD7.D6xxx) are freezed from time to time for a couple of minutes. If during this time a page is changed, no values are shown at all. This phenomenon can be observed when using the Web Editor 5.13.00. This can happen after several hours of service.

Reason
This freeze of the values is caused by a problem in the Java Applet IMasterSaia5_13_00.jar distributed together with the Web Editor 5.13.00.

Solution
To solve this problem, please load the new Applet 5.13.00 (attached to this FAQ) into your web project.

 

This error message appears if the used firmware on the CPU does not support the "active and non ACK" filter for the S-Web alarming functionality (e.g. a PCD2.M150 with firmware 0D3).

 

Symptom
Instead of the alarm list of the S-Web alarming macro, the message "Failed to get data on alarm.exe" is displayed on the alarming page.

Reason
The reason is that the macro tries receiving the alarms filtered by the "active and not acknowledged" state of the alarms. This does only work if this feature is implemented in the according firmware.

Solution
Please update the firmware (FW) of your PCD system to the firmware supporting the according feature (see table below).

System	minimal FW
PCS1.Cxxx	0E3
PCD1.M1x5	0E3
PCD2.M150	0E3
PCD2/4.M170	0E3
PCD2.M480	1.08.21*)
PCD2.M5xx0	1.08.19
PCD3.Mxxx0	1.08.23*)

^*) On PCD3 and PCD2.M480 systems the "active and not acknowledged" filter has already been implemented in previous versions, but has been improved this indicated version.

 

The alarm appears correctly but the alarm text is missing.

 

Possible Reasons: 

• The name (name and reference) of the Fbox Alarming is too long. It can be maximum 20 chars. 
• The alarm texts should be in a .csv file but the file was not created
• The csv file was created but the alarm texts where not adapted correctly. The formatting has to be as in the example below:
    A.Alarm.ThisAlarmList.MyName_1;First Alarm
    A.Alarm.ThisAlarmList.MyName_2;Second Alarm
    A.Alarm.ThisAlarmList.MyName_3;Third Alarm
  The first part should not be modified. The part after the ; is your alarm text and can be adapted as you like
• In Project/Project configuration/Project-Applet advanced the option HTML Parameters in csv file is not activated or it is activated but the csv file containing the alarm list is not chosen in the field "csv file".
  

Yes, it is possible to store the web pages (.teq, .htm, .html, IMaster.jar, .gif etc.) on the panel instead on the CPU itself.

 

In general it is possible storing data (pictures, files) directly on the Web Panel. The only file which always needs to be stored on the PCD is the file with the extension tcr. Depending on the panel, specific techniques and storage folders are available:

Micorbrowser Panel PCD7.D4xxx (MB Panels)
Data can be stored on the onboard Flash memory "M1_Flash" (in the folder M1_FLASH/WEBPAGES). This data is to be downloaded over an FTP connection (further information can be found in the manual SBC FTP Server and SBC Flash File System, 26/855).
Quickguide:

 

• Configure an IP address on the panel.
• Open an FTP client (active FTP mode) and connect to the MB Panel
  Username: root
  Password: rootpasswd
• Download the files to the folder "M1_FLASH/WEBPAGES" 
• If the same files are present also on the PCD, specify "Search files first local".

The MB Panel will search these files independently on the configured communication type to the PCD (http direct, Serial-S-Bus etc.)

CE Panel PCD7.D5xxx / eXP Panel PCD7.D6xx
On a CE- or eXP panel data can only be stored locally if the WebConnect software is used. In this case, data can be stored on the storage card in the Webpage folder (the folder location can be configured in WebConnect). Hint: whenever possible, use the http direct protocol, where WebConnect 2.0 and later can act as proxy.

 

Yes, it is possile storing files directly on the flash File System of an MB Panel. By doing so, the page will be displayed faster because these files do not need to be transferred over the communication interface.

 

Can I store any file of the Web Project on the MB Panel?
In fact, all the files of the Web-Editor project can be saved locally on the panel except the *.tcr file. This file contains the definition of the global variables of the PCD (PPO variables) and must remain in the user program of the PCD (added to the project by using the Web Builder). All the other files can be stored on the local Flash Card of the WebPanel.
 
How to store the files to the MB Panel?
The files can be transferred via an FTP connection (user: "root", password "rootpasswd") to the "M1_FLASH" directory of the MB Panel file system. For further information regarding accessing the file system of the MB Panel, please refer to the manual 26/855 (Manual File System) which can be found on the support site (www.sbc-support.ch) in the product section for the PCD3.

Remark
The directory "INTFLASH" shouldn't be accessed by the user and no data should be saved in this directory.

 

Yes, if you use version 2.0.31 of the Web-Builder or later you can access to variables like Ressource_name_of_PG5[2].

 

 

With the old Web-Builder it was not possible to use symbolic PG5 resource names if on the Web-Builder the container offset where used.

On the old Web-Builder you have to use the following syntax:

PDP,,R100+@COFF_index@

 

Since the version 2.0.31 of the Web-Builder it is possible to use the symbolic name of the PG5 like

Ressource_name_of_PG5+@COFF_index@

 

 

 

The old version of the Web-Builder supports only registers with addresses < than 10000 (4 digit values).

Register addresses > than 9999 are supported since the version 2.0.31 of the Web-Builder.

 

 

 

Yes it is possible to use a kind of life sign on the XP, CE and MB Web-Panel (created with the S-Web-Editor) and to read this life sign on the PCD.

This allows to know if the connection between the PCD and Web-Panel is ok and if the Web-Application on the Web-Panel is running.

 

 

To insert the life sign you have to use the container variable @BLINKCO on the S-Web-Editor.
During runtime this container toggles each refresh period between 1 and 0 on the XP, CE or MB Web-Panel.
To transmit the container @BLINKCO to the PCD, you have to copy the container to a PCD variable and you have to check on the PCD application programm, that the PCD variable does toggling cyclically.

To copy the container @BLINKCO to a PCD variable use the macro “EventP_wrCo2ppo_onRepaint_.tlb” of the S-Web-Editor.
You can place the macro on a background page and use the same background page on all your Web-Pages.

To avoid that the life sing is not toggling during the time that the Web-Pages “MsgBox.teq”, “ALPHAPAD.TEQ” or “KEYPAD.TEQ” are shown on the screen, you have to insert the macro “EventP_wrCo2ppo_onRepaint_.tlb” also on this pages.
Please note that you have to insert the macro directly on this three pages.
It’s not allowed to use a background or foreground page on this three pages.

Remark:
If several Web-Panels does display the same Web-Application of the same PCD then on the PCD the life sing will be overwritten from all Web-Panels and it’s not possible to detect if one Web-Panel is no more working.

 

The use of two ports allows the user to make a prioritization of the web-requests.

 

If http-direct is used, then the Web-Server on the PCD3 and PCD2.M5 CPU’s is accessible over two different socket ports. The default ports are socket port 80 and 81.

It's possible to change the port number with the use the Device Configurator of PG5 2.0 (SP1 or later). To change the port number see the FAQ 101464.

Working principle
The use of two ports allows the user to make a prioritization of the web-requests.
If for example there are 4 devices (A, B, C and D) which do access the S-Web server of the PCD then the user could force the device A, B and C to access the port 80 of the PCD and the device D does access the port 81 of the PCD.
In such a case the requests of the devices A, B and C are queued in the Web-Server socket queue 80 and the request of the device D is queued in the Web-Server socket queue 81. The web server on the PCD does treat both ports evenly.

In the example above the requests of the device D are treated about every 3rd cycle. The requests of the device A, B or C are treated about every 7th cycle.

 

The index of the Alarmlist FBox does always start with 1 (and not with 0). If more than one Alarmlist FBox is in use, the index has to be adjusted in the following way:

 

Example:
The first FBox is an Alarm 10 F-Box and has the Index 1
The second FBox has in this case Index 1+10 = 11
If the second FBox is an Alarm 20 FBox, the third FBox has Index 1+10+20=31

 

Once the used password page has been activated, the password page cannot be deactivated any more until next reboot.

 

In order to deactivate the Web server password page, switch off the PCD (with power off/on). Note that a new program download and/or a CPU coldstart does is not sufficient for resetting the password page.

 

If a negative value (for instance -0.7) should be displayed on the CE panel, there is just -.7 visible. The zero is missing. A new microbrowser version is solving the issue.

 

Reason
This was a problem in the Microbrowser distributed with the image $2.0.27.0.

Solution
Install the new Microbrowser 1.5.10.091d or newer. Ask the support team for the latest version. Replace the Microbrowser.exe and in the Windows folder mfcce400.dll

 

Since the first version of the Web Editor has been released there has been many functionalities added. In parallel, new functionality has been added in PCD firmware, Micro Browser Panels (MB Panels PCD7.D4xxx), CE Panels (PCD7.D5xxx) as well as on eXP Panels (PCD7.D6xxx). This FAQ contains a function matrix that gives further information regarding the added functionalities and dependencies.

 

Introduction
The various features of pages created with the Web Editor do require functionalities of the PCD firmware as well as of the panels/PC systems used. Depending on the panel or PC, these functionality needs to be implemented in:

• The PCD firmware itself. The PCD firmware can be downloaded from the according product section on the support site.
• The firmware (of an MB Panels if used). The MB Panel firmware can be downloaded from the product section PCD7.D4xx from the support site.
• The image (if a CE- or eXP panel is used). The according image can be downloaded from the product section PCD7.D5xxxx (CE) or PCD7.D6xxx (eXP) from the support site.
• In the IMasterSaiaxxx.jar (for the usage of a web browser running on a PC). The IMasterSaiaxxx.jar is distributed together with the Web Editor and will be copied into the PG5 project by the Web Editor. The Web Editor itself can be downloaded from the Application overview page "S-Web" on the support site.

Supported features by panels and the Web Editor
The table below shows the first version of the Web Editor supporting various features. Additionally, the required version of the panel operating system is shown, too.

Web-Editor functions	Web Editor	MB Panels QVGA (FW version)	Web-Editor (MB version)	eXP Panels (IMaster.jar )	PC/Laptop (IMaster.jar)
New PG5 Symbol selector with group support	5.13.00	-	-	-	-
New Macro format incl. gif & PPO min/max & unit	5.13.00	-	-	-	-
Validation of user entered values for date & time for PPOs	5.13.00	1.07.00	1.5.10.082c	5.13.00	5.13.00
New Alarming macros for 3.5" MB Panel with F-key operation	5.13.00	1.08.01	-	-	-
New filter "Active or NAK" in Macro DefOnline Alarming	5.13.00	1.07.00	1.5.10.082c	5.13.00	5.13.00
Alarming & Trending Date/Time display format configurable	5.13.00	1.07.00	1.5.10.082c	5.13.00	5.13.00
Browser resp. applet loads only 1 page				5.10.00	5.10.00
Alarming (with extension for ACK by user program)	5.07.00	1.07.00	1.5.10.082c	5.07.00	5.07.00
Support of Unicode character set (only for the display of texts in the browser by the use of "HTML tags")	5.07.00	V1004	1.5.10.082c	intern. JVM required	intern. JVM required
Multi line painter	5.07.00	V228	V1.5.072	5.07.00	5.07.00
Web-Editor zooming	5.07.00			5.07.00	5.07.00
Hide & disable group	5.07.00	V228	V1.5.072	5.07.00	5.07.00
Support of  Web-Editor version 5.07.00 (without usage of trending, alarming and Unicode characters)	-	V228	V1.5.072	5.07.00	5.07.00
Trending	5.03.00	1.07.00	1.5.10.082c	5.03.00	5.03.00
Autom. page change	5.03.00			5.03.00	5.03.00
Password 4 levels	5.03.00			5.03.00	5.03.00
TableControl	5.03.00			5.03.00	5.03.00
ComboBox	5.03.00			5.03.00	5.03.00
Unicode with cyrillic Windows	5.13.00	1.08.02	1.5.10.082c	5.13.00	5.13.00
HTML support (e.g. frameset for navigation)	-	No	No
Support for SD-card (backup and restore; clone and restore from clone)	-	1.08.01	-	-	-

The version 1.5.10.082c of the Micro Browser for CE panels is distributed with the following images for the CE panels:

• For PCD7D.5xxxTMxxx (CELERON): version $1.0.3.0
• For PCD7D.5xxxTXxxx (XScale):     version $2.0.27.0

Supported features by PCD firmware
The table below shows the first version of the PCD systems supporting various features.

Web-Editor functions	PCD3.Mxx0	PCD2.M480	PCD2.M170	PCD2.M150	PCD1.M135	PCS1.Cxxx	PCD3.Mxx7
Trending	020	039	020	0D0	0A2	0B3	1.440
Alarming (ACK possibility by user program)	039	039	0E3	0E3	0E3	0C0	1.511
New filter "Active or NAK" in Macro DefOnline Alarming	1.06.38	1.08.21	0E3	0E3	0E3	0E3	1.08.04
Nbr. of data points > 1500 (max. 1500 data points/page)	020	1.08.21	020	0D0	0A2	0B3	1.440
Nbr. of pages > 32	020	1.08.21	020	0D0	0A2	0B3	1.440

Remark
The versions mentioned above are the first versions that support the according feature. As the versions all are backward compatible, it is recommended using the last version rather than downgrading a system to the version indicated above.
The first name of this FAQ was "Which functionality is supported in which Web Editor, Micro Browser and firmware version?"

 

When connecting over a network (VPN), the default timeout can be to small. It is possible to change this timeout by adding an configuration file.

 

Symptom
The WebServer is accessible over the local network and works well. But when connecting over e.g. a VPN or over the internet, the pages are not displayed (or only some times). The error message Applet IMasterSaia not inited can appear.

Reason
This can happen due to the timeout of the WebServer. By default the http connection is reset by the PCD after a timeout of 1 second with firmware older than 1.14.xx (with firmware 1.14.xx and later, the default timeout is 3 seconds). In some cases the "old" timeout of 1 second is not long enough while 3 seconds shoud be ok in all cases.

Solution

• Firmware 1.14.23 with PG5 2.0.150 (SP1) with or later
  Starting with firmware 1.14.23 and PG5 2.0.150 (Service Pack 1) it is possible to configure the S-Web Server directly with the Device Configurator and this configuration can be downloaded over S-Bus (download configuration in the Device Configurator):
  
  Before this is possible, please configure the firmware version to "From 1.14.00 or more recent" in the properties of the PCD type (see screenshot below).
  A change of the configuration is active right after the download of this configuration (given no http connection is already open; the parameters of open connections are not changed on the fly).
• Firmware older than 1.14.xx
  The timeout can be configured in the Web server configuration file on the PCD. The name of the file must be: "WEBSocketConfig.txt" and it has to be placed either in the M2_Flash/Config folder or it has to be downloaded with the WebBuilder.
  The file has to be present at boot time, this means that you have to restart (power off /on) the PCD for that the configuration is interpreted. An example file is attached to this FAQ. When placing this file the timeout will be 10 seconds.

Remarks

• As soon as PG5 2.0.150 or later is used and the configuration of the device is set to "Firmware 1.14.xx or newer", the configuration will be downloaded via the Device Configurator. This configuration has a higher priority than the WebSocketConfig.txt.
• In case you already have configure the PCD in the old way (with the WebSocketconfig.txt) and you would like to keep it that way even after a firmware upgrade, please select "Before the version 1.14.00" and download this configuration; this will cause the Device Configurator to delete its configuration files even if the firmware used on the PCD is newer than 1.14.00:
  

Since the Micorbrowser does not support every function of the Internet Explorer it can be necessary to open the Internet Explorer for some specific operations.

 

Problem
The Microbrowser cannot handle everything that the Internet Explorer does.

Reason
Since the Microbrowser was reduced to a minimal browser to make it faster, it is not possible to add all option that other browsers have.

Solution
It is possible to call another tool which is installed on the panel per example the Internet Explorer. This can be done with the container variable MB_StartProzess. As value the tool to open and the URL has to be entered (iexplore www.ininet.ch; with image 2.0.xx it is isample ininet.ch ).

 

New F-Boxes per example for the trending / alarming where installed in PG5. After the installation the F-Boxes are still not available in Fupla.

 

Problem
New F-Boxes where installed. The installation seemed to be successful, otherwise the F-Boxes are still not available.

Reason
Check if the F-Boxes are really installed (p. ex. C:\Program Files\SAIA-Burgess\PG5 1_4\Libs\Usr). If they are present there, check in the Software-Settings of your CPU under Directory if "Use Library Override Directoryes" is activated.

Solution
If the files are not present, copy / install them again
If the "Use Library Override Directoryes" is activated, deactivate it or copy the files to the corresponding path.

 

After installing or upgrading the Sun Java Virtual Machine Version 6 (resp. 1.6) the SBC Java applet for S-Web applications (IMasterSaia*.jar) does not update PPO values anymore. To fix this refreshing problem, either use a recent firmwae or disable the file caching for java files.

 

Symptom
At the beginning of April 2007, Sun Microsystems started to distribute it's updated Java Virtual Machine, now called Java Platform Standard Edition 6 which is in fact version 1.6.0. After this version is installed, the Java applet used with S-Web application does not work properly anymore. While setting PPO values via Buttons or Edit Boxes still work, the actual PPO values are not updated/refreshed.

Reason
This problem is caused by the fact that version 6 / 1.6 activates the file caching for java files, which was normally deactivated in former Java versions. To solve the PPO update problem within the SBC applet, the file caching for java files has to be disabled again!

Solution
There are two possible solution in this case:

• Recommended solution
  Use a recent firmware version, later than 1.10.16 for PCD3 or PCD2.M5xxx. This firmware version contains the new Web Server 2 which supports the caching mechanism used by the Java Virtual Machine.  
• In case it is not possible updating the firmware of the PCD, disable the caching of files in the Java Virtual Machine. Therefore go to the control panel and open the settings for "Java". At the bottom of the "General" tab, click on the Button "Settings..." within the "Temporary Internet file" group. Now the dialog "Settings for temporary files" should be openend (see screenshot below).
  
  Disable the the file caching by untick the checkbox and clear the file cache by clicking the "Delete files..." button. Close all opened dialogs with "OK" and restart your Web-Browser. Now, the SBC applet and your S-Web application should work properly again (but the whole applet will be reloaded every time when opening the web page).
  

With Internet Explorer 6 it was possible to access the PCD3 FTP server. IE7 does not support this anymore

 

Problem
The FTP server can only be accesed with per example: "ftp://root@172.16.1.65". Otherwise when browsing to another folder the connection is always borken because the root@ get lost. It is necessary to add the root@ for each folder changing.

Reason
Microsoft does not support the FTP functionality with the IE7.

Solution
Use another FTP client: Fillzilla (Freeware), Total commander or go back to

 

When the input Clear of the FBox 10 Alarm get high this FBox and the Alarm SWeb Init FBox show no values and it doesn't work properly! It also can happen that the PG5 closes and PCD get in a strange state.

 

Install the corrected Alarming library 103001in attachment!

 

After a few houres or days the PCD3 goes in HALT with a BUS ERROR.

 

Problem
The PCD3 goes in HALT with a BUS ERROR after a few hours or days. After a power off / on it works again for a while

Reason
This can happen if many accesses to the WebServer are executet and a firmware <030 or <$2A is in use.

Solution
Update the firmware to 030 or $2A

 

The page is properly displayed but the values are not refreshed anymore.

 

Problem
After a few hours the Internet Browser is not refreshing the page anymore. The only solution is to restart the Browser.

 

Reason
If the debug option is activated in Web Editor, Project/Project configuration this will fill up the Java consol and after a few houres it is not possible to handle it anymore and the Browser will freeze. This debug option is not activated by default. It can be helpful at the beginning of a project but in runtime it should be switched off again.

Solution
Switch off the debug option.

§ix100456§

 

The page is properly displayed but instead of the values from the PCD a syntax error is indicated.

 

Problem
Everything works fine, only the values from the PCD are not displayed. It appears a syntax error instead.

 

Reason
This can happen if the file .tcr is not loaded on the CPU. The two files .tcr and .itc should not be copied to the flash memory card or in the C:\Webpages folder. They have to be implemented in a WebServer Project (.wsp) and downloaded to the CPU. If they are on the flash card or in the Webpages folder this can cause the problem desibed above.

Solution
Create a WebServer Project (.wsp) -file in your PG5 project, if it is not already existing. Add the .tcr and .itq file and "Generate" the file. Make a rebuild all and download the project to the CPU. Note that the WebServer Project (.wsp) has to be linked in the project, while the WebEditor Project (.prj) don't has to be linked.

 

Negativ values are not displayed correctly in a Web Application

 

Problem
Negativ values are displayed as 1.-44 instead of -1.44. The format is not correct

 

Reason
There are two different problems. On problem was in the microbrowser version for CE-panels and the otherone was in the Java-Applet of the Web-Editor (IMaster.jar).

Solution
The problem is fixed for the Microbrowser CE panels in the version V1.5.076b7 which is now installed on the delivered panels.
The problem with the IMaster.jar is fixed in the WebEditor version 5_10.

If you need a new Microbrowser or WebEditor Version contact the support team support@saia-pcd.com

 

 

Web Editor 5.07 Project with Microbrowser V1.5.07.074

URL Jump doesen't work!

 

    Web projects built with WebEditor 5.07 need the Microbrowser Version V 1.5.076b7.

    Contact PCD Support

 

The maximal lenght of all file names in a Webproject is 18 characters (without extention). Special characters and spacees are not supported.

 

Problem
It is possible to define file names with more than 18 characters and special characters or spaces. Unfortunately these cases are not catched by the WebEditor. However, the Web Editor project will not work properly if a file (*.teq, *.gif etc.) has a name that is more than 18 characters. It might be that the file is not downloaded at all and is therefore missing in your project (the 18 characters do not include dot and extention).
If a *.teq file has a file name longer than 18 characters it is possible that the PPO values are not read from the PCD ("no message" is shown instead). It is also possible that only a part of the PPO values is shown.

 

Examples

• Thisismygif.gif (11 charakters=ok)

• Thisteqistoolong132.teq (19 charakters=too long)

• New Gif.gif (Space is used= not allowed!)

• Hällö.teq (Special character used=not allowed!)

 

All files in the Web project should be defined according to this rules including the Webproject itself.

 

This is related to a firmware problem in the PCD3 FW 018. Update to the next official version.

 

 

 

On a PCD Web Panel CE it's possible to display the Web application with two different tools, either the Internet Explorer or the Micro Browser.

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

It's possible to display the MicroBrowser page on the PCD Web Panel CE in full screen mode.

That mean that now scroll bar on the right side and on the bottom of the display is visible

 

If you want to display the content of the MicroBrowser page in full screen mode then you have to open the file:

uBrowser.xml

which is located on the flash card of the PCD7.D5xx terminal on the folder:

"Storage Card/Micro-Browser/"

with a text editor and you have to modify the entry: <kiosk>0</kiosk>

<kiosk>0</kiosk> = full screen mode is not actiavated
<kiosk>1</kiosk> = full screen mode is actiaved, this is the first version of full screen mode. Not all functions are supported
<kiosk>2</kiosk> = full screen mode is actiaved, this is the new corrected version of full screen mode.
<kiosk>3</kiosk> = full screen mode is actiaved, this is a special full screen mode. It is not possible to get to the windows desktop of the panel without a keyboard connected.

If you are creating a new project we recommend to use the kiosk 2 mode. Otherwise if you have created a projekt with kiosk 1 and you are happy with it, there is no need to change.

 

 

Excel ofers a powerfull function to store the content of Web-Pages (tables) which where stored in the PCD in to Excel sheets

 

To store a Web-Page content like the example below in a Excel sheet you have to perform the following steps:

§ix100303§

Open Excel. Select menu point "Data, Import External Data, New Web-Query".

§ix100304§

On the address field, browse to your Web-Page which is stored on the PCD.
Select the page and the table which you want to store in to Excel.

§ix100305§

Define the Excel cell where you want to store the table

§ix100306§

 

 

This error appears if the itq file is empty.

 

Problem
The following message appears when generating a Webbuilder Project: 
§ix100272§

 

Reason
The itq file is empty

Solution
Generate the Webbuilder Project without itq file or open the corresponding Web-Editor project, click on the icon ID=, o.k / yes. Save the file. Now the Webbuilder Project will no more show this error message.

 

If you try to connect to the the WEB Server of a PCD2.M170, PCD2.M150 (pilot FW) or a PCS1 and no WEB Server project has been downloaded, the following error is displayed: "Error 4 -Invalid page indentifier in the PCD answer".

 

 

On the "older" system it is necessary to download a Web Server project (even if it is empty) into the PCD in order to be able to access to the default SBC WEB Pages!

On the Saia PCD® COSinus systems (PCD3, PCD2.M5 and PCD2.M480) this problem doesn't occur!

 

The web page is properly displayed but instead of the variable value the text "No component selected" appears.

 

Symptom
The webpage is properly displayed but instead of the variable value the text "No component selected" appears. Probably some modifications have been done on the web pages in the Web Editor and it has been compiled and downloaded. The graphical modification are updated but the the variable value don't apear!

Reason
The message "No component selected" indicates a wrong or missing tag definition for the value to be displayed. One common reason for this message is that only a part of a Web Editor project has been updated.

Solution:

Make a "Save all" in the Web Editor before compiling the PG5 project and download the project! Don't forget updating also the files which are stored on a Flash module (WEBPAGES folder) and/or in the folder "WebPages" from WebConnect.

 

All PCD systems developed since the year 2000 contain a Web Server for diagnostic purpose and allow to download customized pages. This is very useful for maintenance purpose and for simple visualizations.

Web Technology is an endless topic, so it is important to start at the right end.

 

S-Web Editor
In general we recommend using the PG5 Add-On tool "S-Web Editor" for the creation of web projects for the visualisation of the PCD medias (Registers, Flags etc.). The S-Web Editor is distributed on the PG5 Controls Suite CD and can also be downloaded from the support page (www.sbc-support.ch). As you can see below, the S-Web Editor is a WYSIWYG Editor:


CGI interface
In case the Web Server shall be accessed from e.g. a Visual Basic application, the PCD resources can also be read and written via CGI calls. In this case, the SBC.Net Suite offers specific libraries which provide the interface from your application to the Web Server of the PCD. The SBC.Net Suite is based on the Microsoft .Net Framework. Please contact your local Saia-Burgess Controls AG Sales office for more information.

Writing your own html code
Of course it is also possible to write your own *.htm/*.hmtl pages containing tags for displaying PCD resources, but the engineering effort is significantly higher if this way is chosen. Please refer to the Web Server manual for more information (the support given by Saia Burgess and its representatives will be limited to the content of this manual).

 

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

 

 

In case more than 32 PCDs are to be connected to a PC using serial connections (with one COM port for every PCD station) PG5 needs to be configured to allow more than 32 COM ports to be used by the SComm driver.

 

By default the number of accessible ComPort is limited to 32 Com ports. The reason therefore is that with more than 32 COM ports is has been observed that the process which allows to scan the available Com Port on the PC could take up to 1 minute (and more...), depending on the system or devices used. This phenomenon can be observed by clicking the "Setup" button in the dialog box of the "Online Settings" in PG5.

Procedure for increasing the maximum number of Com Ports
=====================================================

PG5 1.4: (Windows XP) 

1. Close all SBC-Software
2. Open the Registry Editor: from the Windwos start menu select "Run...", type "regedit" and click "OK"
3. Browse to --> HKEY_LOCAL_MACHINE --> SOFTWARE --> Saia Burgess --> PG5 --> 1.4 --> SCommDrv
4. In this folder (... --> SCommDrv) create or modify the "PcdLastCom" DWord variable with a value greater than 20 hex (32 dec) for example 40 hex (64 dec)
   This new value represents the maximum number of accessible/scanned ComPorts by PG5

PG5 2.0: (Windows XP)

1. Close all SBC-Software
2. Browse to the folder "C:\Documents and Settings\All Users\Application Data\Saia-Burgess\PG5_20\"
3. Open the file "SCommSettings.ini" and modify the value of the "PcdLastValue" (for example write 64) and save this file under the same format.
   This new value represent the maximum number of accessible/scanned ComPort by PG5
   
   

 

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.

 

Due to a problem of Windows XP and Windows Server 2003, the SCOMMDRV.EXE can exhaust all available memory when using "socket communication" (Ether-S-Bus). The memory leak is related to the "Windows XP Themes" and Microsoft provides a patch for this problem.

 

Symptom
When using the Microsoft Windows XP Theme (see screenshot below), the Scommdrv.exe leaks memory every time a Ether-S-Bus (Socket) connection to a PCD is disconnected. This can lead to a system crash when all available memory is exhausted.


Reason
This problem occurs because of a bug in the implementation of the new Windows XP theming interface. MFC applications leak GDI objects on computers that are running Windows Server 2003 or Windows XP.

Solution
Please refer to the link below which points to the Microsoft Support page which explains the probelm and from where a patch can be downloaded.

Note
This problem concerns all applications using the SCommDrv.exe and communicating with Sockets (--> PG5, OPC Server etc.). WebConnect 2.x is only concerned if the SComm driver is selected.

 

There is a serious problem with AMD Athlon 64 X2 processors. The timing functions in the BIOS have a bug and can cause the SComm fail with strange status.

 

Symptom
On a PC equipped with e.g. an AMD Athlon 64 X2 processor it is possible that the SComm driver fails with strange status messages. We have observed this problem on AMD Athlon 64 X2 processors produced in 2006 but the problem can potentially happen on all multi-core processors.

Reason
There is a serious problem with some series of AMD Athlon 64 X2 processors. The timing functions in the BIOS have a bug and can cause the SComm fail with strange status. The problem seems to be related to the variable clock rate feature of the CPU.

Solution
Microsoft and AMD had to fix this problem. Please refer to the links attached to this FAQ and apply the mentioned update on your system if necessary.

How to detect if your CPU is affected?
There is a simple test program that allows to detect if a CPU is affected. Procede as follows:
- store the attached dll vb6fr.dll in your /windows/system32 folder unless it is already present there
- run the attached projet.exe and go to the second screen. If everything is OK the fourth value in form1 is a rather stable value in the order of 350, if you have a negative or very big value the CPU is affected by the problem

 

You can't connect over any channel to a PCD by using the SCommDll . The software firewall softwares "Zone Alarm Security", "Windows Defender" or "Bitdefender" block the SComm funktionality on PC's running MS XP.

 

Symptom
If the ScommDll is launched, the PC won't react on key strikes for more than 40 sec. After this time, an error message is displayed saying "SCommDll error, Socket not installed or wrong server IP number".

Reason
The software firewall "Zone Alarm Security" blocks the ScommDll (The SCommDll communicated to the SCommDrv over an IP stream on port 7000 that is blocked).

Solution
Zone Alarm must be uninstalled; only deactivating won't work in most cases. This phenomenon was only observed on Windows XP. On W2k it seems that the ScommDll works also with ZoneAlarm activated.
In case the Bitdefender is used either disabling or appropriately configuring should help.

Hints

• The behavior descripted above does also apply to many other Personal Firewalls (aka Desktop Firewalls, Internet Security Suites etc.). So if socket communication does not work, these security tools should be checked.
• Most Personal Firewalls can be configured by so called "rules", which allow to open certain ports for one or more applications. So instead of totally disable or uninstall der firewall software, it may be a better solution to define apropriate firewall rules which allow SCommDrv to communicate anyway.
  For the relevant PG5 parts SCommDll.dll and SCommDrv.exe to work the TCP port 7000 needs to be enabled on the local host!

It is possible to connect a PCD over a server. This means that the PCD is connected to a remote PC (server).

PG5 on the local PC will connect the SCommDrv on the remote PC and therefore reads the medias of the PCD connected to the remote PC.

 

• Run ScommDrv.exe on the server by double clicking the file in the installation directory of PG5 server installation.

• Once the icon is visible in the taskbar, open it (context menu of the icon, right mouse button)

• Select tab “Setup”. Set checkbox “Load on startup” (this will cause SCommDrv to be launched on system boot. This is required for that the clients can connect to it)

• Set “Server IP Address” to the interfaces address on which the clients are connected

• Set “Local IP Address” to the same interface, save and close the SCommDrv and unload it (context menu of the icon in the taskbar).

• Restart SCommDrv.exe (this is required for that the new settings will be read and applied)

Now the server is ready to answer to requests from clients (himself included) to establish a connection to a PCD connected to it’s interfaces. Several clients may connect one or several PCD’s at the same time.
The SCommDrv.exe must be running in order to answer these requests.

Setup of the SCommDrv.exe On the client PC :

• Run the SCommDrv.exe. This may be done by establishing a (PGU-)connection or
  by doubleclicking the SCommDrv.exe on the server’s share.

• Open the SCommDrv window by selecting “Open” in the context menu of the SCommDrv icon in the taskbar and select the tab “Setup”

• Set the option “Unload on last close” (recommended, but not necessary)

• Set the “Server IP Address” to the address of your server

• Apply and Close. Then unload the SCommDrv (context menu of SCommDrv icon in the taskbar)

 

Once the ScommDrv on the client is unloaded it won’t be visible any more in the taskbar since it isn’t started any more. Only the SCommDll.dll will be launched by PG5 in order to connect a PCD and connect to the SCommDrv located on the server.
To reset/modify the changed settings you have to open the SCommDrv.exe manually by double clicking it in the client PG5 installation directory.

 

Note that the port 7000 of the concerned (Ethernet) interface on the server mustn’t be blocked by any firewall.

Since the connection to the PCD on IP will be established over port 5050, make sure this won’t cause any problems, either.

 

Standard properties:

 

§ix100423§

 

If you want to use the S-Bus OPC-Server and PG5 on the same PC then you have to make attention to use the correct version of the S-Bus OPC-Server which fit with the corresponding version of the scommdll.

Nerveless it’ possible to run for example the S-Bus OPC-Server v 2.02.09.01 on a PC where PG5 V1.3 was installed.
In this case the S-Bus OPC-Server doesn’t have to use the scommdll of PG5 V1.3 but he has to use the scommdll (V 1.2) stored on the S-Bus OPC-Server installation package.
If PG5 and the OPC-Server use two different version of the scommdll then it’s not possible to go online with a PCD simultaneously with both tools.
To install the scommdll which is stored on the S-Bus OPC-Server installation package, during the installation of the S-Bus OPC-Server you have to select “Install SBC communication driver”.

 

If the SBC S-Bus OPC server was launched by a request of an OPC client located on another machine, the SCommDll (or SCommDrv) is not available for the user working on the PC where the OPC server is running.

 

 

This problem is caused by the fact that the Merz SBC S-Bus OPC Server (SaSBus.exe) was launched under the "Interactive User". As result the SaSBus as well as the SCommDrv and SCommDll will not appear in the system tray of the user (logged in). Nevertheless an instance of the SCommDll is running (under the "Interactive User") and it can't be started again by the logged in user.

 

The error messages will be something like "The driver is not available" or "Another instance of the driver is already running".

As workaround the logged in user has to launch the SaSBus before the OPC client will request data from the OPC server. Once the SBC S-Bus OPC server is started by the logged in user, it won't be started a second time by the Interactive User and therefore it will be possible to communicate over the same SCommDrv (logged in user and OPC Server).

 

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’

 

 

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.