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.

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: 

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:

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:

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.

Table input status:

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.

Table output status:

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

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

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!

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.

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.

Profibus and Profi-S-I/O 

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

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.

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

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

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

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

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


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

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

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

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

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

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

  

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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


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

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

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

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

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

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

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

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

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

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

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

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

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

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


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

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

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

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

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

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

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

Solution
The solution is:

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

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

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

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

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

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

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

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

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

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

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

by

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

if you want to define 200 connections in the SWebConnect.

Remarks

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

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

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


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

Solution

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

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

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

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

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


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

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

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

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

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

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

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

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

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

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

PG5 does not change the TAPI settings of Windows.

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



 

PG5 does apply the following rules:

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

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

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

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


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

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

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

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

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

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

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

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

The value has to be >=1  

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

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

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

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

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

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


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

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

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

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

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

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

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

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

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

As URL you have to use the name:

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

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

On the example below the station name was modem.

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

The example project is stored in FAQ #100567

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

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

Anti virus Cilling version 12 on a PC with Window XP

After stopping this anti virus the problem is solved!

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

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

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

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

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

• Fupla

• Graftec

• SEdit

• WebConnect

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

-  The stopped service is marked as stoped.

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

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


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

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

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

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

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!

On a 64 Bit OS system, after an update for Java to version 1.7.0_65 (July 2014), the Applet doesn't start anymore and the Browser shows just a blank page.

This trouble is caused because of incompatibility between 32 and 64 Bit components (OS, Browser, Java version).

Possible behavior:
- On a 64 Bit OS system with 32 Bit Browser, the applet doesn't start anymore in the Browser.
- The applet works and starts without any problem on 32 Bit Systems and 32 Bit Browser and 32 Bit Java.
- The applet works and starts without any problem on 64 Bit Systems and 64 Bit Browser and 64 Bit Java.

The used Browser (32/64 Bit) will define which Java version (32/64 Bit) will be installed.
Today, 24.07.2014, IE exists in a version for 32 and 64 Bit. Official Chrome and Firefox is only available as 32 Bit version. The 64 Bit versions are in beta-phase.

The below table shows the version compatibilies.

We did tests with Firefox, Internet Explorer and Chrome

Possible solutions
- Use for example the Internet Explorer 64 Bit, which is normally already installed on Windows OS with the 64 Bit Java runtime. You'll find the IE 64 Bit version under C:\Program Files\Internet Explorer\iexplore.exe
- You can downgrade the Java runtime to the version 1.7.0_55 (available in the attachment below).

How to know which version of IE and Java is used
For IE:
On the IE go to the Help --> About Internet Explorer, window and look for "64-bit Edition"
If it is absent you are running the 32 bit version of IE.
32-Bit IE:

64-Bit IE

For Java:
How to know if the 32 or 64 bit version of the Java is used?
On the dos command window do type:
java -version
On the 64-bit version there will be the text
....64-Bit Server VM
Where on the 32-bit version there is nothing written about the 32-bit version
32-Bit Java

64-bit Java

On a pop up window the message ‚Missing Application-Name manifest attribute for: x.x.x.x/IMasterSaia5_15_02.jar is shown.

If the web pages where created with older versions of the web-editor of PG5 2.0 and PG5 2.1 or the web editor of PG5 1.4 then it’s possible that this error does occur.

The new java applet which does solve the problem is integrated in PG5 2.1.300 or later.

Symptom:

The web page is not displayed and the follwoing window is shown

Solutions for applications where the java applet IMasterSaia5_15_02.jar or IMasterXX7_5_15_02.jar with version < 5.15.0231 is used:

Solution:
There are 3 differnt solutions:
Solution 1: Define on Java a exception for the PCD's which does contain the old *.jar file
Solution 2: Replace the old *.jar file on the PCD with a new one
Solution 3: Set the security level on java to the level 'medium'

Solution 1: Define on Java a exception for the PCD's which does contain the old *.jar file
Quick solution to be able to display the web pages again without the need to update the java applet on the PCD:
To do this you have to open Java from the control panel.


Browse to the securty tab and there click to the button 'Edit Site List':


On the next window do enter for each PCD which does contain the old *.jar file the IP address in the format
xxx.xxx.xxx.xxx and click to the button 'add'.


After this there will be a warning window like this:


The IP addresses are schown then in the security tab in the section 'exception site list'



Solution 2: Replace the old *.jar file on the PCD with a new one
Do download the IMasterSaia5_15_02.jar version 5.15.0231 or later 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.
If the java applet is used in the PG5 web builder, then do copy the new java applet in the web and html folder of your PG5 project and do compile again the web builder and the PG5 project and do download the project to the PCD.
Do copy also the two files in to the S-Web editor 5.15.02 directory so that this jar files are also used for new projects.
This java applet version 5.15.0231 or later does contain the new manifest.

Solution 3: Set the security level on java to the level 'medium'
Quick solution to be able to display the web pages again without the need to update the java applet on the PCD:
To do this you have to open Java from the control panel and on the security tab and there
put the security level on the java control panel to the level 'medium'.

Please note, that this solution is only an intermediate solution which helps to display again the web-page.
To avoid any security issues it’s necessary to set back the security level to 'high' as soon as possible and to replace the java applet as described above.

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:

When I load the content of my remote PLCs Webserver I get a pop-up window with a security information and following warning: "The application's digital signature has expired".

Symptom
When I load the content of my remote PLCs Webserver I get a pop-up window with a security information and following warning: "The application's digital signature has expired". I can now choose between "Run" or "Cancel".



Reason
The certificate (digital signature) of SBC IMasterX_XX_XX file expired on January 3rd 2013. That's why the internet browser is prompting you with this warning, if you're using a version 5_15_02 or older of the IMaster-file.

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 jar 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:



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 solution for applictions where any version of the IMasterSaia/IMasterXX7 applet is used. 
Please check the box "Always trust content of this publisher" and click "Run". There are absolutely no security risks when running SBC IMaster-file.

On the alarm list of the alarm web-page not existing alarms are displayed as active without text (only "-").

The displayed ghost alarms aren't used at all in the project or they aren't anymore used as the project was modified!

Reason:
Depending of the number of alarms which are defined on the alarm init FBox, PG5 does reserve an array of alarm flags (for example 300).
It’s possible that on the PG5 program not all alarms of this array are used.
There might be also gaps between used alarms, according to the parameters of the Alarm Header Fboxes used!

This behavior of ghost alarms on the alarm web-pages occurs, if the unused flags are set to 1.
This could happen, if a project was modified and for example on the old project an alarm was set to 1 and this alarm doesn’t exist anymore on the modified project.

Solution:
Find out the start address and the array size of the alarm flag array on the Fupla symbol editor.
Reset all the alarms flags with the degugger, using the command Write Flag 4758 Count 300 0:
In this case the Flag 4748 is the base address of 300 alarm flags.
For your case you have to use your base address and your array size.

or
add a program code in the XOB 16 (cold start) to reset all the alarms at startup:

                XOB    16
                SEI      K  0                                                   ; load the index register 0
LOOP1:    RESX   F   A.Alarm.ListeAlarmeGen.Flags      ;Reset Alarmflags + index
                INI      K   300                                               ; Increment the index register 
                JR        H  LOOP1                                           ; Jump to loop1 as long as index < 300
                EXOB
  Use this code only once, because otherwise all alarms are cleared after each startup of the PCD.

On the MB Panel (PCD7.D4xx ), there is no entry on the alarm list and the message above is displayed.

If the web project is displayed on the Internet Explorer then the alarms are shown correctly on the alarm list and there is no error message!

Reason:

The special characters like "é,é,ö,à, etc.." aren't supported as reference for the alarm macro on the MB panel (PCD7.D4xx).
But it's possible to use special characters for the alarm messages.
Please refer to the FAQ #101427 about this.

Solution:
Modify the name in the Alarm FBox (Alarm SWeb) in that way, that no special characters are used.
Also on the csv file which does contains the alarm messages do not use special characters on the left side of the semicolon sign!
For DDC-Suite applications: Do re-generate the DDC_Alarming.csv file with the help of the ddc Add-on tool after changing the name of the FBox which does contains alarms.

A HDlog macro has been added in a project but it isn't possible to enter the variables because the option to Add a "SBC HDlog files" in the Project Configuration window (Menu: Project / Project Configuration.. ) is missing!!

Symptom
The "Project Configuration window" appears as following (without the HDLog files section):


Possible reason
The licence for Web Editor Advanced is missing!

Possible solution
Update your PG5 licence with Web Editor Advanced!

When opening the start page of a web editor project the list of files being loaded are displayed in the browser. If this is not desired one hide or adapt this behaviour using a new HTML Tag since PG5 2.0.220 (in fact the S-Web Editor 5.15.0221 is required)!

Procedure
The start-html file is to be modified in order to influence this behaviour. This can be done in the following way:

• Open the start.htm file (or however your html file from the S-WebEditor is called) from the folder /WEB inside the PG5 Project (not from the folder HTML) using a text editor
• Below the "End Tag2" line at the end of the file, add the line with the InitPhaseMessageLevel:
  The result will be:
  
• Build in WebEditor and then PG5 and finally download the modified htm(l) page of the project
  (new line will not be overwritten on Build of the Web Editor because it is below the "!- End Tag2"

Remarks
The folllowing values can be used to select the behaviour while loading the pages: 

• 0 ==> No init phase message displayed

• 1 ==> ALL init phase loading filexx messages are displayed

• 2 ==> Only message text "Loading..." is displayed at init phase

• 3 ==> loads an image and displays that image during init phase (the loading image may also slowdown if a bigger image is used)
  If the Option 3 is selected, the image file name can be defined by the following parameter:
  

Please note that the minimal version of the IMasterSaia.jar is version 5.15.02 delivered with PG5 2.0.220 (it will not work if IMasterSaia5_15_02.jar from PG5 2.0.210 is loaded). The size of the file to be used is 371.9 kByte.

If you run on your PCD7.D61xxTL010 eXP panel with 512 MB main memory the internet explorer and use the applet 5.15.02 (or later) with standard *.html settings of the WebEditor, you might face the following error message "Windows - Out of Virtual Memory – Your system is running low on virtual memory" at the moment the applet is started.

Reason
With the default settings of the S-Web Editor 5.15.02 the applet tries to allocate too much memory.

Workaround
The task is to modify the size of the allocated memory used by the applet. This setting's defined in the *.html file of the WebEditor project. We have to add this supplementary initialization at a place that the WebEditor doesn’t overwrite during the Build all process. Add the line



just below the line

example of html-code


Alternative solution
use WebEditor 5.15.03 or WebEditor 8 once available.

In case the PG5 Control Suite is not installed the S-Web Editor has to be licensed by copying the file "user.key" into a specific folder. This FAQ contains a procedure for licensing the S-Web Editor without PG5.

Please follow the procedure below in order to install an license your copy of the S-Web Editor.

• Install the S-Web Editor
  The installer can be downloaded from the support site or is available on the DVD of the PG5 Controls Suite in the folder
  \PG5 Stand Alone\S-Web Editor\
• Create the following folder manually and copy your "USER.key" to this folder:
  For Windows XP:
  c:\Documents and Settings\All Users\Saia-Burgess\PG5_20\LocalDir\USER.key
  For Windows 7:
  c:\Users\Public\Saia-Burgess\PG5_20\LocalDir\USER.key
• Please execute the executable "RegKey52.exe" from the installation directory of the S-Web Editor: 
  c:\Program Files\SAIA-Burgess\PG5_20\Web Editor 5_xx_xx\RegKey52.exe

After having executed these steps the WebEditor is licensed according your User.key file.

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"!

The "Alarming 2" feature comes along with some new functionalities as for example alarms in groups and priorities. But, this groups and priorities are not correctly displayed using the Alarming v2.6.166 FBox Library.

Problem
Groups and priorities of the alarms in "Alarming 2" feature are all set to "0".
There's a bug in the actual FBox Library "Alarming v2.6.166".
If you don't enable the Eventlist functionality in the "Alarm2 SWeb" FBox, your "Alarming 2" alarmlist will behave like a traditional "Alarming 1" alarmlist. This means, it'll not care about the group- and priority-definitions. A "0" is indicated for groups and priorities instead of the real numbers.

Solution
Until a new version of the FBox Library will correct this issue and if you want to use the "Alarming 2" feature without implementing an Eventlist, you can apply following workaround:
- enable the Eventlist in the "Alarm2 SWeb" FBox
- minimize the generation of creating Event-files my choosing to create a file only each month
- but anyway, you'll have to specify a Flash file system for the logs
- clear to "0" all the alarms in the Eventlist-columns of your Alarming Configuration file.

There's a new S-Web Alarming functionality available in Fupla and the S-Web Editor 5.15.02. It's called "Alarming 2". This new feature adds functionality but is more complex to use. Therefore it should only be used in case this new functionality is explicitely required.

The "Alarming 2" feature is available for conditional use for customers that absolutely need the new features listed below:

• Event handling
• Short and long alarm texts
• Alarm texts on 2 lines
• Alarm texts in short and detailled form
• Alarm help texts
• Alarms in groups and priorities
• "Alarming 2" isn't yet an automatic progress. There are some steps to be done by manually by the user.

You'll find a "User Quick-Guide", a Demo-Project and template files to startup your first project using these features. These files are stored in the folder "Alarming 2 documentation" at the place where you installed the WebEditor version 5.15.02.

i.e.: C:\Program Files\Saia-Burgess\PG5_20\Web Editor 5_15_02 

The minimum required versions are:

• PG5 2.0.210 and later (PG5 1.4 is not supported) 
• PCD firmware: 1.16.45
• FBox Library: 2.6.164
• S-WebEditor version: 5.15.02
• CE and XP MicroBrowser: min. 1.5.15.118
• VGA and SVGA MicroBrowser Panel: 1.18.28

Please also respect the PCD hardware dependency; a recent PCD3 firmware version that is required (see firmware download page). The "Alarming 2" feature is only supported on Saia PCD® COSinus PLCs (PCD1.M2, PCD2.M5, PCD3 but not on PCD2.M480).

In some cases it is necessary to re-load a Web Project project on a PCD7.D4xxx MB Panel (e.g. if the project stored on the PCD has been modified). This can of course be done by powering off and on the PCD7.D4xxx, or it can be realized by writing in to a specific container " uBT_Reboot "

Introduction
In some cases it is necessary to re-load a Web Project project on an MB Panel (e.g. if the project stored on the PCD has been modified). This can of course be done by powering off and on the PCD7.D4xx, but in this case someone need to be present to manually do so. Alternatively there is the possibility to initiate a reboot (which causes a reload of the proced) by writing the container "uBT_Reboot" to value "1".

Example
Attached to this FAQ you can find an example for PG5 2.0.210 which contains a small Fupla file together with a small S-Web Editor project.

• In this project it is possible to restart the MB Panel directly (with a button to write the container uBT_Reboot to "1")
• Alternatively it is possible to write a PPO (Timer) with a button to the value of 10 seconds. The binary state of this timer is copied in the Fupla file to a flag, and this Flag is copied to the container uBT_Reboot with the macro "Write source to destination (on repaint)" which is located on the same page.
• If in the Fupla program the same timer (Web.Roboot_Timer) is written to a value of around 10 seconds, the reboot will take place witout someone touching the MB Panel (given the macro "Write source to destination (on repaint)" is executed on the panel).

Firmware and hardware requirements
It is possible to use the container uBT_Reboot since the hardware version C of the MB-Panel.
In order to use the container uBT_Reboot for rebooting the MB Panel the following minimal firmware is required:

Screenshot for example project

Restriction:

1.- Since FW version 1.22.xx due to the internet security the remote access to the panel is on OFF mode.
2.- The only panels where it is possible to re-activate such remote access are : PCD7.D412DTPx and PCD7.D4xxxT5F. All the others (a part from someOEMs) do not allow any access at all.
3.- The remote access can be reactivated by removing the parameter in the setup menu (MANUALLY) under System/Special/FTP Server/Remove default user as "not checked" and for sure the parameter on/off "active".
4.- On the pWeb-Panel like PCD7.D4xxxT5F or PCD7.D443WT5R, the uBT_Reboot instruction does write all PCD medias like register, flag, DB, timer and counter to 0.
To avoid the writing to 0 of all PCD medias to 0, use the attached Webeditor-8 template in your Webeditor-8 project.

The template ‘Reload new project’ can be used on all Web-Panels with FW 1.22.xx or newer:

To use the template just import the template Reload new project.xtml (attached to this FAQ) in the Webeditor8 libraries and place the template on the web-page on which the reboot should be performed.

Description of the webeditor8 template ‘Reload new project’
The template reload a new downloaded web application on the HMI device.
Use the property dialog of the template to configure.
Parameter ‘Reload project if 1’: If the selected Variable (INT/PCD) is set to “1” the function is executed.
Parameter ‘Jump to URL’: Name of the html file used for the application if known, if not you can let it empty. In case it is empty, the default configured start page on the device will get loaded.
After successfully execution, the variable defined at Reload project will be set to “0”
The template does replace uBT_Reboot instruction but will not clear the medias of the pWeb Panels.

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.

The "Action Mode" "Broadcasted Action" never was supported by SBCs MicroBrowser Panels (PCD7.D4xx) and could be used only with the applet-based Browsers. In order to eliminate this incompatibility (different behaviour on different browsers) it was decided to limit the "ActionMode" to "Consumed Action" only.

What is the broadcast mode?
A S-Web Editor button is in some purposes too limited for executing mutiple action possibilities. To enhance this lack, programmers placed multiple buttons on top of each other. So, clicking the topmost button also executed the actions attached to all the buttons underneath. This behaviour was possible while using in the WebEditor the "Action Mode" "Broadcasted Action".

Why is it no longer available in the S-Web Editor 5.15.02?
This behaviour worked fine in all Applet-based Browsers. But was newer supported in any SBC MicroBrowser Webpanels. Therefore, to eliminate this incompatibility, SBC fixed the "Action Mode" in WebEditor version 5.15.02 and newer to "Consumed Action".

What to do?
If you want to continue programming using the "Action Mode" "Broadcast Mode" you have 1 possibility:

• continue to program your project with WebEditor version 5.14.30 in mode "Broadcasted Action"

Otherwise, if you want to profit of the newest WebEditor features of version 5.15.02 and newer, you'll be constrained to use the "Action Mode" "Consumed Action". So,

• modify your project structure to be compatible to "Consumed Action" mode or
• replace your multi-action-buttons of your actual project with a special macro that emulates the multi action feature of your several buttons. Please contact the SBC support team to receive this macro.
  
  

When an “EventP_Logout_onTimeout_5_13_40.esm” macro is placed (i.e.) in the background Teq view, it jumps also to the defined Teq view, after the inactivity time ran out, even if you haven't been logged in.

Problem
When an “EventP_Logout_onTimeout_5_13_40.esm” macro is placed in the background Teq view, it jumps also to the defined Teq view, after the inactivity time ran out, even if you haven’t been logged in.
Also the container “userLevel” is set to “0” but it was anyway.

Solution
You have to disable the automatic log-out feature on timeout if you're not really loged-in. So, right mouse-click on the logout macro and then choose “Cross Ref…”, a dialog box opens. In the second tab (General) it is possible to disable the group on condition. Click on “Disable Group” and “On Condition”, afterwards it is possible to configure the condition. As Type, choose “Container” and name it “userLevel” it is the same that is used in the login macro. Then chosse “<” and value “1”, like it is shown in the picture below.

When configuring in the WebEditor a macro, using the macro user interface, the error message "ERROR while generating Macro's Temp folder" appears. Why this?

Symptom:
You want to configure in the WebEditor a macro, that uses the new macro user interface, and following error message appears: "ERROR while generating Macro's Temp folder".

Possible reason:
The reason is always, that the folder with the name "MacroLibTempFiles" isn't present in your local WebEditor installation folder on your programming computer. This folder is needed to handle the macro dialogue user interface and isn't always installed by PG5. Especially not with the actual PG5 2.0.200 SP2.

Solution:
Create the empty folder "MacroLibTempFiles" manually, directly in the root of your present WebEditor installation, like shown in the below picture.

In the new WebEditor 5.15.02, included with the PG5 2.0 Service Pack 2, there is a bug when using the new alarming macros, resulting in "Unresolved external symbol" on next build.

Symptom
In the new WebEditor 5.15.02, included with the PG5 2.0.200 there is a bug when using the Alarming macros. After having inserted the macro "MacroAlarmingDefOnline_5_14_05" or the "MacroAlarmingDefOnline_5_15_02" two PPOs are generated automatically: maxPPO2 and minPPO2.
On the next build these symbols which should not be added to the PPO list result in following error message: "Unresolved external symbol"



Reason
Due to an error in the macros the minimal and maximal values of the macro are added as PPO.

Solution
Please install PG5 2.0.210.0 or a later version of PG5 2.0.

Workaround (if the update of PG5 is not possible)
A workaround to work with the new Web Editor until a new version is available is the following:

1. Change the PPO Listname format to "DEC", then you can remove the Min and Max values of this PPO.
2. Click Ok, and open again the PPO window, now these two PPOs have disappeared.
3. Change again the format of the Listname PPO to String , then you can compile the project  without having this error.

With Service Pack 2 of PG5 2.0 (PG5 2.0.200) the S-WebEditor version 5.15.02 is installed. This Editor comes along with new alarming features (Alarming 2) like alarm lists with priorities and Event handling.

Firmware dependencies
All these new features are supported in browsers when using the IMasterSaia5_15_02.jar file. The actual official firmware version 1.12.17 for Micro Browser displays does not yet support these new Alarming features.
Therefore a firmware version 1.18.xx will be needed; this version is actually in preparation for begin of 2012.

Remark
This FAQ will be updated as soon as the according firmware is available.

With the Web Editor version 5.15.02 (installed together with PG5 2.0 SP2; PG5 2.0.200) the button "Select" is missing when using the dialog "Replace" to select a group name for the macro Find/Replace feature.

Symptom
The Macro Find/Replace itself does work but the button to select a group name is missing:


Reason
This is a bug of the S-Web Editor 5.15.02 which is distributed with PG5 2.0.200. It is corrected with PG5 2.0.210.

Solution
Please install PG5 2.0.210 which contains a correctio of the S-Web Editor.
In case it is not possible to install the new version, the following workaround can be applied:
Before clicking the button, select a PPO from the list below (it is important it is a PPO and not e.g. an HTML tag):

Wenn openning the Tag "Project-TeqConfiguration" and "Project-Build Advanced" some options are missing (see screen shut below).

Reasons:
Those options aren't accessible because the licence used is a S-Web Editor basic!


The missing options aren't needed in the Web Editor Basic package

In case you would like to use the icons from the HEAVAC S-Web Demo or from the DDC Suite template projects you can download them from the support site.

How do these icons look like?
Below you can find a screenshot from the HEAVAC S-Web Demo:


Where from can I get these symbols?
The symbols which are used for the HEAVAC S-Web Demo and the DDC Suite template projects can be downloaded from the support page, see link below.
In the archive you'll find several versions of each symbol (various sizes, and always one *.gif and one *.jpg).

Can I use these icons for my projects or are they copyright protected?
You can use these icons; they have been designed by Saia-Burgess Controls AG and are intended to be used together with the S-Web Editor or Visi.Plus.

Are the symols according to DIN or SIA?
In case the symbols are not identical, SBC tries to provide both versions; the one according to SIA and the one according to DIN.

What can I do in case I'm missing a symbol in this library?
In case you are missing a symbol in the library, please send an eMail to support@saia-pcd.com; in most cases we'll add the icon you desire.

Spaces in texts get displayed as "+" when the option "Encode Special Chars" in the Web Editor is disabled or if a 'old' version of the IMasterSaia5_15_02.jar file is used.

Symptom
After entering text in a text field of a webproject the spaces between words get displayed as plus signs ("+").

"this is a text" results in
"this+is+a+text" being displayed

Solution
Please enable the option "Encode Special Chars" in the project configuration of the Web Editor. This option must always be enabled when the web project will be running on a NT system. (And it mustn't be enabled when running off a old/non-NT-system!)



The 'old' IMasterSaia5_15_02.jar applet does generate the same kind of error.
Do use at least the IMasterSaia5_15_02.jar file with date 05.02.2013, downloadable from the support homepage, section software PG5 Suite 2.0.220.


Remark
Do not enable the "Encode special characters" on the following systems: PCS1, PCD2.M150, PCD2.M170, PCD1.M135.

Wenn building an S-Web Editor project this message may appear in case at least one macro used in this project is more recent than the onces from the S-Web Editor 5.13!

Symptom
The following message is shown on each build of the S-Web Editor project:


Reason
This message indicates that during the build of the project the "Teq format" is converted to an old version (the original files remain, but the files copied to the "html" folder are modified to the old format). This is only necessary in case the project shall be displayed with an older Micro Browser runtime.
In detail the option "Force Teq Files Saving as 5_13 Format" is only required in case the project shall be displayed on one of the following hardware/firmware combination:

• PCD7.D4xx (QVGA) MB Panel with firmware older than 1.10.45
• PCD7.D4xxV (VGA) MB Panel with firmware older than 1.01.04
• WinCE panel (PCD7.D5xxx) with a uBrowser version older than 1.5.13.100
• Win Mobile uBrowser version older than 1.5.14.106
  

In case one of these versions is used (and it is not possible to update the firmware or uBrowser version), please select the following checkbox in the S-Web Editor menu "Project" --> "Project configuration...":


In case the firmware or uBrowser versions are up-to date, just unselect the above checkbox in order to get rid of the message indicated at the beginning of the FAQ.

After an update of the project from PG5 1.4 to PG5 2.0 (if in the S-Web Editor project a Heavac template "Set-point ramp" or "Setp-point slide" is used) the symbol A.HVC.FBox_Name.SetPt can be missing.

Symtpom
After an update of the project from PG5 1.4 to PG5 2.0 (if in the S-Web Editor project a Heavac template "Set-point ramp" or "Setp-point slide" is used) it is possible that the error "Unresolved external symbol: A.HVC.FBox.SetPt" is displayed and the build fails.

Unresolved Externals: A.HVC.FBox.SetPt in modules: 'WEB.obj'

In case special characters are used in an S-Web project to be displayed on an MB Panel (e.g. in the alarm list) a corresponding font files which allows to displayed the specific characters is to be loaded.

In the application where the alarming functionality is used there are 2 ways to defined the texts of the alarm (here below):

1. In the *.csv file which is edited with the S-WebEditor and to use with Alarm SWeb Init Fbox or Alarm PCD Init FBox
   --> Here you can write in the CSV file special chars as cyrillic, japanese and other ... (contact your local SAIA Burgess sales office for specific font files)
2. Or in the PCD directly (through the Symbol Editors or a *.src file) to use only with the Alarm PCD Init FBox
   --> In this way only ASCII characters are supported

A S-Web Editor project can be displayed in two resolutions (using the autoscaling feature). In case the original size is downscaled it is possible that some gif files are not displayed properly (or at all) on VGA MB panels. QVGA MB Panels do not support the autoscaling feature.

Problem
On a PC with a usual web browser the page is displayed correctly. On the VGA MB panel (PCD7.D4xxV) some gifs are missing. The project was created and afterwards the scaling functionality was used for downscaling to the VGA resolution 640 x 480.

Reason
If a gif has a bigger size than the maximal resolution of the VGA panel (640 x 480) the panel cannot display the gif picture. The VGA MB panel is not able to scale it down if the original gif is bigger than 640 x 480 (per example 800 x 50).

Solution
Store the *.gif in a size not bigger than 640 x 480. To avoid such problems it is recommended to use the scaling feature only as up-scaling for S-Web Editor projects/pages.

Additional information: How to find the reason for such a problem?
If a gif is not properly displayed and you don't know the reason you can connect to the panel over FTP. In the folder UBT_FS a file LOG.txt is available. On the last lines of this file you can find the reason for the problem (with firmware version 1.12.11 or later).
Example
"nGif, not valid GIF: Too large image size: name_of_the_gif.gif"

To implement the HDLog feature you'll have to respect some minimal mandatory versions of PG5 library and PCD firmware

Symptom
On build of the PG5 1.4 project (implementing the HDLog feature) an error message in the following style is shown:
Fatal Error 12: C:\Programme\SAIA-Burgess\PG5 1_4\Libs\App\HDLOG.lib: Line 40: Can't open $INCLUDE file: FileSysMac.lib

Reason
The FBox libraries are most likely not compatible. In order to be able to build your project, please update the FileSystem FBox library of your PG5 1.4 for that they are compatible with the HDLog FBoxes.
Minimal FBox library versions (which supports the HDLog to File feature):

• HDLog FBox library 2.1.030 or newer
• FileSystem library $2.5.307 (PG5 1.4) 2.6.100 (PG5 2.0) or newer
• PCD Firmware 1.10.16 (but we recommend 1.10.28 or newer in order to profit from the most recent features in the file system)

In a Web Editor project with HDLog File macro the following error messages appear during the connection to the PCD Webserver:

File not found: Filename_D0111018.csv. Actually 30 files are not found (past month)

Symptom
The Applet tries to load the csv-file of the actual day from the Web-Server of the PCD by means of HTTP protocol. The Web-Server can't find the requested file and replies with "File not found". The applet counts 30 days back and asks for these files. None of the files can be found. The webserver can't find the file of the actual day although it is visible with FTP access.

Reason
This happens in case the file system has just been formatted with the Memory management FBox before. In this case the Web Server does not know that it shall re-search the folder on the formatted flash.

Solution
After formatting the file system with the Memory Management FBox it is necessary to switch off / on the PCD (remove 24 V). For PCD3.R600 flash memory modules there is also another solution the SD-card can be removed and reinserted. After this operation the files can be seen again by the Web-Server and the error message from the Applet will disappear.

Note
There could be other reasons for the same behavior of the Applet. (Error messages File not found). But in these cases the file would not be visible over FTP. It may be that the command for the WriteFile operation was not yet given or there were other errors with the File writing operation (e.g. Flash device not present)

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 compiling a project in PG5 the error message: "more than 383 elements in DB" appears. How can this problem be solved? And where does it comes from?

Problem
It is not possible to compile the project. The error message "more than 383 elements in DB" appears on build of the project in PG5.

Reason
DBs in the extension memory do have more than 383 elements (these DBs do have address 4000 and above). All other DBs (address 0 to 3999) only can have up to 383 elements. The alarming and trending FBoxes need DBs with more than 383 elements (RAM DBs located in the extension memory).

Solution
This error message can appear if there is no extension memory configured or if there is no extension memory available (on a PCD2.M150 per example).
For the PCD3 and PCD2.M5 the solution is to configure the "Hardware Settings" with default values and download the hardware configuration with memory allocation. Afterwards open the "Software Settings" and set the values to default.

Remark
On "non-Saia PCD® COSinus" CPUs like the PCD2.M150 you will need extension memory otherwise it would not be possible using the alarming FBoxes since those require  DBs with more than 383 elements.

While it is well known how to generate scalable HTML-files with the S-Web Editor and how to use them with the different MicroBrowser resolutions. But it is not well known that it is also possible to use different HTML start-files for different "non MicroBrowsers".

Replace your per default generated start HTML-file by a HTML-file containing this small java-script code in the body-part.




if (screen.width==640||screen.height==480) //if 640x480 VGA
window.location.replace("Start.htm")

else if (screen.width==1024||screen.height==768) //if 1024x768 XVGA
window.location.replace("XVGAStart.html")

else //if all else
window.location.replace("Start.htm")




This code is browsing to the respective HTML-file corresponding to the resolution of your Web-Browser.

When showing an online trend in a PCD7.D4xx MB Panel (both VGA and QVGA versions) the time stamp displayed is wrong. Instead of the correct time, a date in 1970 is indicated.

Symptom
When showing an online trend in a PCD7.D4xx MB Panel (both VGA and QVGA versions) the time stamp displayed is wrong. Instead of the correct time, a date in 1970 is indicated.

Reason
The reason for this incorrect time is that the PCD7.D4xx do not feature an internal clock.

Solution
With the MB Panel firmware 1.18.28 and later this problem is solved. The clock of the PLC is then transmitted to the web panel.

When using the "HDLog to file" FBoxes the caching of the Java Virtual Machine (JVM) is to be disabled.

Symptom
When using the "HDLog to file" feature, on the first loading the logged trend, the trends are displayed correctly. But on a reload of the trends to display more recent trend curves, no refresh is done. The browser (running the Java Virtual Machine) only reads the cached memory (instead of re-reading the files on the PCD).

Reason
Theoretically the WebServer 2 (implemented on PCD3 and PCD2.M5 systems with FW 1.10.16 or later) supports caching by the JVM. But the new feature "HDLog to file" feature does not yet support chaching. If this feature is used, please disactivate the caching in JVM.

Solution
Please desactivate the caching feature of the JVM as described in FAQ 100708 when using the "HDLog to file" FBoxes and macros.

When the two files KEYPAD.TEQ and ALPHAPAD.TEQ have been copied from the uBrowser Panel into the Web Editor project the extensions appear in capital letter (.TEQ) , in order to be correctly interpreted (in the java applet) it has to be in lower case letters (.teq)!

Solution
In Web Editor rename the KEYPAD.TEQ and ALPHAPAD.TEQ in KEYPAD.teq or ALPHAPAD.teq (Right-click on the file / Rename..).

In general the small red button with the "Warning" written on it indicates an error. When clicking the button, the message box should appear and indicate a detailed desctiption of the error.

Symptom
The small button with the "Warning" written on it appears in runtime of a web project, but no error message is shown when clicking it.
§ix101025§

Reason
This behavior can be observed if the file "MsgBox.teq" is not present in the Web Project, or if the file can not be found.

Solution
In order to have the message box shown, include the file "MsgBox.teq" (either in the WebBuilder project, or on a flash file system in the folder /WEBPAGES/).

You know how to create log-files on the PCDs flash file system with the HDLog FBoxes. But how can you handle the saving and deleting of the historic files in most efficient way without generating undeleted and unused files?

To work most efficient with the HDLog feature in combination with flash file system it's good to know some background ideas from the developpers side. The best would be to describe this idea directly in an example:

• you define to save daily your logs in a file on the flash file system
• take care of the size of this daily generated file. You're able to send via e-mail attachments of 1 MB size
• you have to define the size of the historic buffer of daily files. You define this size with the parameter 'delete file older than ...' of the HDLog FBox
  if you put for example '30' into this parameter you'll have a total history buffer of 30 files representing the last 30 days on your flash file system
• in this case you have to trigger on your own and manually the 'DelFile' entry of the FBox every day. The file older than 30 days will then be deleted from the file system. Otherwise you risk to have undeleted and unused files on your flash card in the future so you'll always have a historic buffer of 30 days. When you log the 31st day, then the 1st day will be erased
• The "DelFile" commands are to be triggered in a sequential way (the output "DelRdy" of the first FBox shall trigger the "DelFile" input of the next and so on:
  
  

Since the S-Web Editor version 5.13.00 many new functionalities have added. These new features also need to be supported by the Web Panel and the some of them by the PCD firmware, too. This FAQ contains a matrix which indicates the required firmware versions for the new features of the S-Web Editor 5.14.27 released in August 2009.

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.

New Web-Editor 5.14.27 functions	MB Panels (FW version)		Win CE Panel (uBrowser)	Win Mobile (uBrowser)	PC/Laptop eXP Panel (IMaster.jar)
	QVGA	VGA
Autoscaling up-scaling		1.12.01	1.5.13.100	1.5.14.106	5.14.27
Moving (X/Y) painter objects	1.10.45	1.01.04	1.5.13.100	1.5.14.106	5.14.27
Polygon rotate feature	1.10.45	1.01.04	1.5.13.100	1.5.14.106	5.14.27
"Tacho" macro	1.10.45	1.01.04	1.5.13.100	1.5.14.106	5.14.27
HD Log trending to PCD File System *)		1.12.01	1.5.14.105	1.5.14.106	5.14.27
New Login/Jump macros	1.10.45	1.01.04	1.5.13.100	1.5.14.106	5.14.27
New CopySourceToDestination macros		1.12.01	1.5.14.105	1.5.14.106	5.14.27
New macro dialogs (new TEQ file format "h")	1.10.45	1.01.04	1.5.13.100	1.5.14.106	5.14.27
Online trend with correct time		1.18.28		1.5.14.106

*) Please note that the following FBox libaries for PG5 1.4.300 are required for the HDLog trending to file system: HDLog 2.1.030 and FileSys $2.5.307. Both versions are included in the package available from the support site. The FBoxes delivered with PG5 2.0.110 do not need to be updated.

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

Web-Editor functions	PCD3 Mxxx0	PCD2 M5xx0	PCD2 M480	PCD1.M135 PCD2.M1x0 PCS1	PCD3 Mxxx7	PCD2 M5xx7	PCD2.M487 PCD2.M1x7
Web Server 2	1.10.16	1.10.16			1.10.17	1.10.17
Autoscaling Moving (X/Y) painters Polygon rotate
HD Log trending to file system	1.10.51	1.10.51
New Login/Jump macro New TEQ file format "h"
Online trend on MB Panels with correct time	1.10.16	1.10.16			1.10.17	1.10.17

Remarks

• When working with PG5 2.0.110 or later the S-Web Editor together with all required FBoxes mentioned in this FAQ are already installed. Examples for PG5 2.0 are available under:
  "General information" --> "Getting Started" --> "Program Examples" --> "PG5 2.0" --> "Web and HMI"
• When working with PG5 1.4.300 the S-Web Editor together with an example, the required FBoxes and firmware versions for PCD2.M5xx0 and PCD3.Mxxx0 can be downloaded from the support site from section
  Software --> PG5 --> PG5 1.4 --> PG5 1.4 Suite (scroll down until "Web Editor 5.14.27 package")
• 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?"

Since May 2010 a new S-Web Editor version is available on the support site. The main differences of this version are listed in this FAQ.

S-Web Editor package 5.14.30 (May 2010)
The following features are new compared to the S-Web Editor 5.14.27. Please note that not all features are available for all PCD systems and/or Web Panels. For more detailled information, please refer to FAQ 101273

New features

• The applet IMasterSaia5_14_30 is now certified
• Possibility to specify the target frame in the URLJumpOnMouseDown macro
• New format "String-i" for display of texts containing formatted data (e.g. $Rxxxx)
• New display formats for time and date within the alarming macro (e.g. dd.mm.yyyy hh:mm:ss)
  Please note that this new format selection is not yet supported on the MB Panels. This FAQ will be updated once a firmware is available.
• Speed improvement when opening Macro dialogs of in large projects
• In case the font is not defined for a painters, the font will automatically be inserted (Arial) on save
• Warnings ("found HTML Tags which are no longer used" and "Warning while updating project's MacroLibTemp for:" on project build can now permanently be disabled by pressing the button "Cancel"
• Improved workflow when working for modifying Macros

Corrections

• When inserting an Alarming macro, the PPO "Alarmlist" will automatically be defined as String in the PPO Initialisation list
• Error when opening the Macro Dialog on Windows7 and Windows Vista is corrected
• Password macro "PasswordDialog_UserLevel_5_13_40" created a dialog timeout when selecting PCD texts
• FTP Download from the S-Web Editor displays correct error messages

• Historical data logging to the flash file system is supported (for PCD3.Mxxx0 and PCD2.M5xx0)
• New, intuitive dialog for configuring macros
• Auto-scaling is availble for using the same project for differenct screen resolutions
• Painter objects can be moved based on PPO values
• Polygons can be rotated
• New Tachometer macro
• Extended Login- URL- and TEQ-jump macros

In case a build of a PG5 project containing the "HDLog File" FBoxes fails with the compiler error "Symbol not defined: __stc_id_00000_..." there are two possible reasons:

1. A wrong version of "HDLog File" FBoxes causes a compiler error when used with a trending macro in the Webeditor.

2. Some internal symbols for the FBoxes were not correctly generated

Symptom
On build of PG5 project the following compiler error is shown and the build is aborted:

Error 42: Kokeilu.wsc: Line 1658: Symbol not defined: __stc_id_00003_var_00

1. old version of FBox library
   Please download and install the newest webeditor package or "HDLog File" FBoxes (version 2.1.030 ml.zip) found on the support site.
2. missing internal symbols
   - In Fupla editor right click on the FBox "HDLog File"
   - choose "Add Predefined Symbols" then "Ok"
   - then make a "rebuild all" in PG5 project manager
   - if the message error still appears, do the following steps (here below)
   - in the web editor delete the macro "RemoteOffSaved..." you've already inserted
   - insert these macros again from scratch
   - add desired curves to the macros
   - "Build All" in web editor
   - Do a "rebuild all" in PG5 project manager
   

Symptom
When building the WebEditor project after generating the HTML-file, the build fails with following error message:
'a renamed file was not found'
As result it isn't possible to build the WebEditor project at all. This behavior has been observed on PCs with installed virus scanner named "Trend Micro Internet Security Pro" (version 17.1.1250).

Reason
Apparently the virus scanner prevents the Web Editor to complete the build of the WebEditor project by denying access to the *.htm/*.html file of the project.

Solution
The actually only solution to successfully build of the WebEditor project in this case is to disactivate this virus scanner during engineering with WebEditor. 

The browser or microbrowser does cash the loaded offline trend lines into an own memory. This leads to the behavior that on the browser more data points than stored on the PCD memory can be displayed.

With the FBox HDLog (integer or binary) it is possible to define the size of the trend which is logged. This size does define the reserved memory for one offline trend curve/line within the memory of the PCD. Every data point of the trend does occupy 8 Byte of memory space.

Example
If a size of 1 kByte is defined for a trend line, the PCD does store 128 trend values for this line.
If the buffer is filled up, then any new value will overwrite the oldest one (if the option "Ringbuffer" is selected).

Every time an offline trend is loaded from the PCD into the web browser or microbrowser then the loaded trends curves are stored in the memory of the web browser or microbrowser.
If after a certain time the same trend is loaded again in to the web browser or microbrowser then the new values are added to the existing memory of the web browser or microbrowser.

This leads to the situation that on the web browser or microbrowser more information is stored than availbale in the memory of the PCD.

Remark
To delete the trends stored in the memory of the web browser or microbrowser, just click to the button "Clear logs".

No it isn't possible to display a register content or a sub text (with the instruction $Rxxxx or $Lxxxx) in the alarmlist of the S-Web editor.

The reason why this isn't possible is the fact that the database of the PCD which does store the alarm events does not contain the alarm text (which may change if the content of the Register $Rxxxx does change) but only a number (pointer) of the alarm.

If on the web browser an alarmlist is shown, then the java applet does load the alarm database from the PCD and afterwards the java applet does insert the alarm text from the csv file or from the PCD texts.

If on the FBox "LogToFile" the text which contains the directory name and the file name does have a configuration option "fixed length" then it's not possible to store information on to the file system.

For both of the texts only the option "Default" has to be set.

The following text definition option has to be used:


Remark
An example for using these FBoxes can be found in the "Getting Started" area on the support site.

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.

Yes, since the S-Web editor 5.14.10 (currently in pilot phase) it's possible to transfer container variable information from one web application to another web application.

Older versions of the S-Web editor (version < 5.14.10, currently still in pilot phase) doesn't support the possibility to save container variable information's (like for example the actual used password level) in the web browser and to re-use this information's in an other web application of different PCD's.
Every time that the *.html/htm file was loaded in the browser/microbrowser all information's stored on the container variables where cleared and set to the default values.

For installations where web applications of several PCD's are displayed on the same browser/microbrowser it could be useful that some information's stored on the container variables of one web application "A" could be used on a web application "B" of a different PCD.

Since the S-Web editor version 5.14.10 it's possible to write/read container variable information's from one web application to/from the clipboard of the browser/microbrowser. The information's are stored in to special "session containers".
There exists 20 session containers named:
"_NOINITSESSCO_0" to "_NOINITSESSCO_19"

This session containers are relative to the session of the browser/microbrowser and are only cleared if the browser/microbrowser is closed.
Any new launched browser will generate a new session and will have here own session containers.
The option "File New Tab" or "File New Window" of the browser will not make a new session and therefore the "old" session containers will be used on those windows.

Example for the use of the session containers

The user is connected with the browser/microbrowser to the web application on the PCD "A" and do enter the password. If he now do connect to the PCD "B" and do load the web application of the PCD "B" then the password level should be used directly on the web application of the PCD "B" whiteout that the user needs to reenter the password.

To read/write the container variables to/from the session containers it's possible to use all functions of the S-Web editor which does allows reading/writing of container variables like:

• Edit Box
• Text field
• "Actions set variable" of the button
• Makro "copy container to container on lost focus/ on gain focus/ on repaint".

The functionality was tested with

• Saia PCD® MB Display QVGA (PCD7.D4xxx) with FW 1.08.05
• Saia PCD® MB Display VGA (PCD7.D4xxV) with FW 1.01.01
• Saia PCD® MB Display CE (PCD7.D5xx) with MB version 1.5.12.095
• IE 6, IE 7
• Firefox 3.0.6

In case symbols can not be selected from the S-Web Editor but a message window with the content "CPU '.' has no global symbols" is displayed the path to the S-Web Editor (which is automatically installed with PG5 2.0.110 or later) might be wrong.

Symptom
It is not possible to select the global symbols as PPOs from a PG5 2.0 project in the S-Web Editor. A message window shows up instead of a table with the symbols to be selected:

Internal Error: PCDBrowseForSymbolDlg2()

Reason
This phenomenon can be observed in case the path the the Add-on tool S-Web Editor is not correctly set (and points to the S-Web Editor from PG5 1.4 instead of the one from PG5 2.0).

Solution
Please make sure that the path to the S-Web Editor is correctly configured. Therefore please

• Close the S-Web Editor
• Open PG5 2.0 and select "Add-on Tools..." from the menu "Tools" of the PG5 2.0 Project Manager
• Make sure that path to the S-Web Editor is correct. In case the path does not point to the S-Web Editor which is installed in the directory
  c:\Program Files\SAIA-Burgess\PG5_20\Web Editor 5_14_30\Web-Editor.exe
  please correct the path as shown in the screenshot below:
  
  

If a S-Bus communication is used between the PCD3 or PCD2.M5xx0 and the MB VGA panel (PCD7.D457Vxxx and PCD7.D410Vxxx) then it may not be possible to write to the PCD variables (depending of the firmware installed on the MB VGA panel).

Symptom
If the connection between the PCD3 or a PCD2.M5xx0 (with firmware 1.09.38 or newer) and the MB VGA panel is realized with S-Bus (Serial S-Bus over RS232/RS485 or Ether S-Bus) and if the MB VGA panel (PCD7.D457Vxxx and PCD7.D410Vxxx) has installed the firmware (FW) 1.01.00 (or older) then it isn't possible writing a PCD variable from the MB VGA panel (edit box or button).

Reason
With this firmware combination writing is not possible with the edit box or with the button of the S-Web-Editor.

Solution
To solve the problem it's necessary to use a FW later than 1.01.00 for the MB VGA panel or a firmware older than 1.09.38 for the PCD3 or PCD2.M5xx0.
This FAQ will be updated as soon as a new firmware for the VGA panels is available.

Remark
If the connection is realized with "http direct" or if the PCD3 or PCD2.M5xx0 firmware is older than version 1.09.38 there is no problem to write to the PCD variables. Systems other than the PCD3 or PCD2.M5xx0 are not concerned.

If the user likes to store a web page then sometime the error message shown below is shown in the S-Web-Editor and it’s not possible to store the web-page.

Error message displayed on the S-Web-Editor

Bug fix to allow storing the page:

• Open the S-Web-Editor
• Open the concerned *.teq file
• Save the file with a different name by the use of the menu "File, Save as"
• Include the new filename in the Web-Editor project with the menu "Project, Add to project, File" and select the new filename.
• The new file is now shown in the left window in the "Project Files Tree Window" of the S-Web-Editor.
• Delete the old file by selecting the file on the "Project Files Tree Window" of the S-Web-Editor and clicking the right mouse key. Select "Remove/Delete from project".
• Save the project
• Close the S-Web-Editor

Re-open the project and change the new file name to the old file by selecting the file "Project Files Tree Window" of the S-Web-Editor and clicking the right mouse key. Select "Rename file".

Any user defined container variable of the S-Web Editor has a size of 255 Bytes.

Means that any user defined container variable uses 255 Bytes of the memory and has the capacity to contain a 255 Byte value.

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

With these container variables you can control the behaviour of the Micro-Browser, get panel specific information, launch and control applications which run in parallel to the Micro-Browser, control hardware features (e.g. audio, LCD back light) and write local data to the panel.

Please take note that especially the hardware related settings depend on the specific hardware platform and are not allways available; the XSCALE CPU (PCD7.D5xxxTXxxx) doesn't support audio.

See below mentioned a list of container variables for the Windows CE Micro-Browser: