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.

The product range PCD7.D7xx will be discontinued in 2011/2012 (we expect to be able to deliver the actual range until end of 2012); the repair service is guaranteed until end of 2015.

Together with the product range PCD7.D7xx (also known under the name "VT also the following products (cables and the programming software for the "ESA Panels") are discontinued:

• PCD8.D81W (VTWIN) 
• Q-CVPLC04202
• Q-CVPLC01402
• Q-CVCOM11102
• Q-CVCOM25F8M
• Q.CVCOM25F9M
• Q.CVAD25M9M

Remark
The products of the PCD7.D7xx range do have an equivalent product code in the form of VTxxx:       
      PCD7.D790................VT50   (0500 00000)
      PCD7.D795................VT60   (0600 00000)

      PCD7.D700................VT150W (150W 00000)
      PCD7.D706................VT150W (150W 000DP)

      PCD7.D710................VT170W  (170W A0000)

      PCD7.D720................VT190W  (190W A0000)
      PCD7.D725................VT190W  (190W AP000)
 
      PCD7.D730................VT300W  (300W A0000)
      PCD7.D735................VT300W  (300W AP000)

      PCD7.D740................VT310W  (310W A0000)
      PCD7.D745................VT310W  (310W AP000)

      PCD7.D750................VT320W  (320W A0000)
      PCD7.D755................VT320W  (320W AP000)

      PCD7.D760................VT555W  (555W A0000)
      PCD7.D761................VT155W  (155W 00000)
      PCD7.D761ET..............VT155W  (155W 000ET)
      PCD7.D763................VT525W  (525W 00000)
      PCD7.D763ET..............VT525W  (525W 000ET)
      PCD7.D765................VT555W  (555W AP000)
      PCD7.D766................VT555W  (555W AP0DP)

      PCD7.D770................VT565W  (565W A0000)
      PCD7.D771................VT505W  (505W 00000)
      PCD7.D771ET..............VT505W  (505W 000ET)
      PCD7.D772................VT505W  (505W 000DP)
      PCD7.D775................VT565W  (565W AP000)
      PCD7.D776................VT575W  (575W APS00)
      PCD7.D776ET..............VT575W  (575W 0PSET)

      PCD7.D785................VT585W  (585W APS00)
      PCD7.D786................VT585WB (585W BPT00)
      PCD7.D786ET..............VT585WB (585W BPTET)
      PCD7.D787................VT595W  (595W APT00)
      PCD7.D787ET..............VT595W  (595W 0PTET)

      PCD7.D788................VT585W  (585W APT00)

      PCD7.F779................VTPROFI/DP (VTPROFI/DP)

The article 450748150 is no longer available from Saia-Burgess Controls AG as the according displays have been phased-out. However, this article can be bought from other providers (it is a Lithium battery 3.6V 1/2 AA).

Possible battery types instead of 4 507 4815 0:

Standard

• Type LS14250 from Saft

Alternatives

• ER 1/2AA S from Varta 
• ER3 STC from Maxell 

Since the production 16/07/2010 the displays PCD7.D761, PCD7.D763, PCD7.D771 have a new boot version it is required to use as well the new FW version contained in the latest PCD8.D81W Version 5.22 programming tool.

This new boot and FW correct problem of frozen screen as describt in FAQ 101196!

 The latest programming tool version is available under:

sbc-support.ch/download/pcd8_d81w_v5_22.zip

Remarks
If we download a project / firmware with the latest PCD8.D81W V 5.22 to a panel containing the older boot (display older than 16/07/2010) it will request the calibration at each start up.

So it is necessary to update the boot first as descript in FAQ 101196 (link below)!

The programming tool PCD8.D81W (VTWIN) is not supported on the Microsoft Windows7 operating system.

The software PCD8.D81W has been written at a time Windows7 did not exist and therefore it is not compatible with Windows 7 or Vista. At the moment there are no plans for changing the software in order to be supported on Windows 7 or Windows Vista.
However it is possible to install PCD8.D81W V5.22 (VTWIN 5.22) on Win7 PCs and work with it but you might be faced to some restrictions!
Known restriction:
The german characters "ä", "ö", "ü" aren't display in the editor and on the screen!
Workaround install another font for example Arial instead of ESA font (see attached document)!
Remark
Please note that the software Polymath from ESA is not compatible with the PCD7.D7xx displays from SBC. The only solution in order to program these displays without any restriction is not to use Windows7 or Windows Vista.

Yes, bu the resources have to transfer from the S-Bus driver to the Ether-S-Bus driver. See the description below

Procedure for the conversion of a PCD8.D81W project

1. Open the project and move the SBC S-Bus driver from ASP to MSP.

2. Convert the panel from Vxxx rev 4 to VTxxx ETH.

3. Drag and drop the driver "SBC Ethernet S-Bus" to the Ethernet port.

4. Open the project editor (double click on the VT icon).

5. Export variables into a CSV format file. 

6. Run Excel and open the CSV file.

7. Change the name of the source device into SBC:Ether-S-Bus_a (default name in VTWIN project).

8. Save and close the CSV file.

9. Import the CSV file in your project
   The  source device of the variables should now have changed.

10. Adjust the addresses of the memory areas.

11. Compile the project.

12. Close the VTWIN project editor.

13. Delete the driver "SBC S-Bus" from the MSP port.

14. Save the project.

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

The FBox library is attached to this FAQ

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

The display has a frozen screen (can be black if in standby mode) and can't be operated.

After a powerup the project's start page is displayed but it might be that the touch screen doesn't respond, because the calibration has been lost.

Solution
The booter and the firmware need to be updated.
If it isn't possible to force the display in transfer mode (download mode) it is necessary first to recalibrate the screen following the description. See FAQ 100868 (see link below).
All displays produced since 16/07/2010 have the new booter.

Procedure to update booter and firmware
If you use PCD8.D81W software version 5.22 skip to point 4 directly or point 5 if the display has already a new booter:

1.  Download the files attached to this FAQ and unzip the archives.
2. Copy the bootloader files 'BT525MTF.FIL' into the following folder:
   'C:\Program Files\SAIA\PCD8.D81W_51x\\boot\'
3. Copy the firmware files "VT525W.BIN" into the following folder:
   'C:\Program Files\SAIA\PCD8.D81W_51x\\firmware\'
4. The boot has to be sent via the bootloader download utility. In PCD8.D81W (programming tool; select the menu TOOLS / BOOT UPDATE-AUTOMATIC), enter the password 371013 and follow the instructions.
5. Open the project, compile it again and download it to the panel and active the download option 'Update operating unit firmware'. Remark: during the download the Boot version is desplayed: version 3.9
6. When the download has finished, after a powerup of the panel, please verify that the new firmware version is
   - 1.13 for PCD7.D763

Remark
Please note that the PCD8.D81W version 5.22 (VTWIN 5.22) CONTAINS this new booter and FW version!
It can be downloaded with this link:
sbc-support.ch/download/pcd8_d81w_v5_22.zip
It is mendatory to use this new FW only on panel having this new booter!

The 7.5" STN VGA displays PCD7.D776 and PCD7.D776ET have been discontinued and phased-out in November 2009.

As the manufacturer of the displays PCD7.D776(ET) has discontinued these types, SBC has phased out these products by November 2009.
As replacement product the MB Panel PCD7.D410VTCF is recommended.

Repair service
The repair service for the above mentioned displays will be maintained until 31.12.2013.

Remark
The ESA reference for the concerned displays is VT 575W APS00SA and VT575W OPSETSA.

When a PCD7.D7xx display visualizes the resources from several PCD stations (more than 3) over Ether S-Bus, some stations don't respond or respond with the ressources from other stations!

Symptom
When a PCD7.D7xx display visualizes the resources from several PCD stations (more than 3) over Ether S-Bus, some stations don't respond or respond with the ressources from other stations!
The PCD7.D7xx has been programmed with PCD8.D81W version 5.12 or 5.18.

Reason
This pheonomenon is caused by a wrong handling of MAC addresses in the Ether-S-Bus driver from the panel, the MAC addresses of the IP stations are not correctly updated.

Solution
By updating the driver of the concerned panel, the described behaviour can easily be corrected. Therefore please:

• download the attached version of the Ether-S-Bus driver (tcp_sbus.BIN)
• unzip it and copy it to:
  C:\Program Files\SAIA\PCD8.D81W_518\firmware\
• Compile the project and download it to the panel

It is possible that gaps in trend from logs are visible in the browser if the "load info & data" of the macro "Trend" is executed after a longer time interval than the data memory size available in the PCD allows to store!

Symptom
It is possible that "holes" in "HDLog to DB" trends are visible in the browser if the "load info & data" of the macro "Trend" is executed after a longer time interval than the data memory size available in the PCD allows to store!


Reason
The trend data's loaded from the PCD are stored temporarily on the memory of the Web browser.
The gaps can occur if the displayed time range on the browser is bigger than the data logging ringbuffer on the PCD.

Example
The log date size is 100 KByte data with a frequency of 1 log per seconds.
As 1 KB is 1024 bytes, there are 102400 bytes (100 x 1024 bytes) available for the trend.
1 log entry including time stamp (date/hour/value) takes 8 bytes.
As result, the available DBs on the PCD are filled up after 12800 seconds (102400 bytes / 8 bytes) which corresponds to 3h and 33 minutes. 

If the "load info & data" is executed at at 8.00 PM and again at 12.00 PM, a gap of 26.66 minutes will be displayed between the two ranges of logs.
At 8.00 PM the data's from 4.26.66 PM to 8.00 PM are loaded from the PCD, stored in the temporary memory of the browser and displayed on the browser.
At 12.00 PM, the data's from 8.26.66 PM to 12.00 PM are loaded from the PCD, added to the data's loaded before at 8.00 PM and stored in the temporary memory of the browser.
All data's (from 08.00 PM and 12.00 PM) are then displayed on the browser.
No recorded data is available between 8 and 8.26.66 PM because the data recorded in this period has been overwritten by the ringbuffer on the PCD.

Note
If the browser is restarted or if a "clear Log" is exectuted then the gap disappaers because the temporary memory of the browser is cleared and trend shows only the last data's (3h33.33) uploaded from the PCD!

It might happend that the touch area of a PCD7.D7xx panel doesn't respond anymore: In this case most likely the calibration has been lost and the touch area has to be recalibrated. In many cases the loss of the calibration can be avoided by a boot and firmware update (see related link below)!

Procedure for recalibrating the touch screen

• Switch off the panel
• Open the back cover (4 screws)
• Locate the single jumper J1 or J5 also indicated with C
• Move the jumper on the position C
• Swicth the power on
• Calibrate the screen with a fine pointer (on the cross 3 times)
• Swich the power off
• Move the jumper to the inital position
• Close the cover
• Switch the panel on

More details about the calibration with drawings for each panel type are available in hardware manual 405_1200_037 which is availbale on the PCD support page:
www.sbc-support.ch/pcd7/dxxx/d7xx/pcd7d7xx.htm


Important
Always use the latest PCD8.D81W version: the actual version is 5.22. In this version some boot / firmware versions have to be updated, see related link to the FAQs 100823 and 100716!

The display has a frozen screen (can be black if in standby mode) and can't be operated. After a powerup the project's start page is displayed but the touch screen doesn't respond, because the calibration has been lost!

Solution
The firmware (PCD7.D761) needs to be updated! The firmware update is done when downloading the project to the panel when the option "Update operating unit firmware" is activated.
If the display can't be forced in transfer mode (download mode) it might be necessary first to recalibrate it as explain in FAQ 100868 (see link below).
Use the latest PCD8.D81W 5.18 version which contains the newest FW!
If you haven't le possibility to use this version and you have the version 5.12 you can also add the new Fw in attachment. So, please execute the following steps:

• Download the files attached to this FAQ and unzip the archives.
• Copy the firmware files "VT155W.BIN" into the following folder:
  "C:\Program Files\SAIA\PCD8.D81W_512\\firmware\"
• Open the VTWIN project, compile it again and download it to the panel and active the download option "Update operating unit firmware".
• When the download has finished, after a powerup of the panel, please verify that the new firmware version is: 1.13.

New: Use the actual programming tool version PCD8.D81W V 5.18 which contains already the new firmware version. So no need to copy the fw files in attachment!

If alarms are activated on a PCD7.D776, it might happened that the screen loses its contrast over the operating time (it become darker and it is very difficult to see properly)!

• Update the boot loader by using PCD8.D81W; function "TOOL" --> "BOOT UPDATE" à automatic, use the code 371013.
• Open the project, compile again and then re-download the project.

Procedure for resolving the problem on a PCD7.D776 Rev. 2
In this case the device needs to be returned to your local Saia-Burgess Controls AG sales office for applying a hardware modification.

Remarks

Only in the programming tool version V 5.18 and newer, the new firmware and boot versions for the PCD7.D776 are included!

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

A VT Win project which had a size of a few MBytes becomes after storing more then ten time bigger (100-200MBytes).

Problem
The size of the project increase after storing to a really hughe size.

Reason
If unicode fonts are used which are not present in the PC the project can become so big because each character has to be stored as bitmap.

Solution
Check the fonts you are using and change to a font which is installed on the PC.

Notebooks without RS232 COM-ports need a USB-Port and a USB to RS converter in order to connect a PCD over a serial line. Our experiences has shown that the driver software from some USB to RS-232 converters do not work in all cases (or not at all). This is why SBC tested various converters.

Please refer to the following list of converters which have been tested and found to be working fine with PG5 1.4, 2.0 and PCD8.D81W (for programming PCD7.D7xx displays, version V4.68 and later).

• Moxa UPort 1110 (RS232) and Moxa UPort 1130 (RS422/485)
  Works on Windows XP and Windows Vista for PG5 1.4 and PG5 2.0
  www.distrelec.ch
  
  
• BAFO BF-810   www.bafo.com
  works on Windows 98, 2000, XP
  
  
• ICP-DAS "I-7560"  www.redacom.ch
  
                               
• Converter USB2.0 to serial #61460 from www.delock.com
  tested on Windows XP, Vista and Windows7 (for Win7 the latest driver is required, see attachment)
  

Remark
Please note that a PCD8.K111 PGU programming cable is still required in order to connect in PGU mode to a PCD (the USB to serial converter does "create" an RS232 port on the PC but it does not cross the Rx/Tx lines which is necessary for RS232 connections).

It is possible setting the clock of the terminals by passing a command from the PCD to the command area of the terminal.

There is an FBox library that was built for this task and eases the handling of the command area and the exchange of the data to be transferred.

Functional description
In general the clock of the intelligent terminals PCD7.D7xx can be set by writing the according command into the command area. The command area is an array of registers that are periodically read (and end interpreted) by the terminal (masters of the communication).
The attached FBox library is designed to interface with the command area of the intelligent terminals of the series PCD7.D7xx.
Please refer to the help for detailed instructions and examples.

Supported functions of the attached library
The attached library does not only allow setting the clock of the PCD7.D7xx but does also allow writing all other supported commands to the terminal. Depending on the type of the terminal this is e.g. deleting the alarm buffer, forced jump to a specific page/sequence, reading the status area etc. Please refer to the ESA manual for a list of the functions supported by your terminal.

Installation
For installing this library, copy the files of the attached archive into the folder "Libs\Usr" in your PG5 installation directory (default C:\Program Files\SAIA-Burgess\PG5 1_3\Libs\Usr\) and reopen Fupla.

Note
Please note that the FBox library can only work if the command area on the intelligent terminal is defined and the addresses of the command area is set correctyl on the terminal as well as in the FBoxes.

On a Profi S-Bus network when PCD7.D76_ terminals are connected to PCD3.Mxxx or PCD2.M480 PLC's over Profi S-Bus, the terminal loses the communication after some time and get even frozen. This problem is corrected in the new boot, FW and driver. The PCD8.D81 V 5.09 is needed , the attached files have to be copied in it (see procedure below).

It is also necessary to update the PCD3.Mxxx and PCD2.M480 FW with the version PCD3.Mxxx_023.blk / PCD2.M480_$27 or newer! Ask the PCD technical support or your representation for it!

Attached you can find the new boots, firmwares and driver that resolve the problem with the Profi-S-Bus network.
The booter file " BT155MTF" and BT525MTF have to be copied in the following folder
C:\Program Files\SAIA\PCD8.D81W 5.09\Boot

NEWS: In the latest version PCD8.D81W V 5.12 contains all thoses updated FWs, drivers and boots! Ask the technical support or your representation for it!

Since the version V5.07, it is possible to import the global symbols from a Saia PG5® project. Because the online help doesn't explain the import procedure correctly, you can find a corrected version attached to this FAQ!

If you need an update of your VTWIN version to this beta version, please contact your local Saia-Burgess Controls AG representative.
The beta version 5.09 is now available!

Newer intelligent terminals PCD7.D7xx do support Profi-S-Bus communication. This FAQ contains a document that describes the wiring for this communication.

In general the Profi-S-Bus communication is handled over the MSP port of the terminal. The attached document contains information regarding cable specifications, wiring information and possible lengths for the communication between a PCD and a VT.

Additial notes
No bridges on the 25 pin D-Sup (MSP port) are required.
Minimal version of the programming tool (PCD8.D81W or VTWIN) is 4.82. 

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!

Even it seems possible to configure Fkeys for up to 31 terminals in Menu Structure of the HMI Editor, it isn't supported!

Symptom
FKeys (PCD7.D79x, PCD7.D231, PCD7.D232), LEDs (PCD7.D232), Buzzer (PCD7.D23x) and the popup of the alarm buffer (all displays) are not supported in RS 485 Bus Terminals Topology!

Reason
Because the RS485 Bus Terminal Topology does use a specific protocol which does not support special telegrams such as the one used for accessing the LEDs or for evaluating the F-Keys, these features are not supported on RS485 networks. In case the LEDs, the F-Keys or the buzzer is required, please connect the display with RS232 to the PCD. 

Probably through the download the FW wasn't installed properly. The terminal is blocked and stays in a loop, rebooting constantly.

Solution: After the 1st check page, when the screen displays "Wait for boot forced", press the screen in diagonal in order to put it in transfer page. Download than the programme and the firmware again!

After this operation the terminal should be return to work properly.

In order to connect PCDs and PCD7.D7xxET terminals on a remote TCP/IP network the use of an ISDN router possible. Internal tests have proven that this is no problem.

In order to get an overview of possible problems that might occur while setting up and working wiht a remote IP network connected via two ISDN routers or an ISDN TA (terminal adaper) and an ISDN router the following  constellations were set up:

§ix100165§

§ix100166§

In this test we used two AR140 ISDN routers (model number: AT-AR140S-513) of the manufacturer Allied Telesyn. This routers do have an integraded 4-port hub and a firewall (that wasn't tested in our test).

We didn't encounter problems for this constellation and found the following test results:

• It is possible to download projects of the PCD8.D81W (VTWIN) to PCD7.D7xx equipped with an Ethernet interface without someone on site

• The connection is established automatically in case of the use of two ISDN routers

• It is possible to download PG5 projects to PCDs (Ether-S-Bus stations) having an Ethernet interface

• A connection can also be established by first activating a dial-up connection and then adding a route (while the tests the added route over a Dial-up connection was removed at disconnecting)

• The networks can be defined by the user (no DHCP is required) on either network constellation

• Proxy servers and already existing network functions aren’t affected if properly configured (exception is the setup procedure of the ISDN routers due to the need of DHCP and set proxy addresses onto the routers!)

• All cables in the installation aren’t crossed (since the internal hub of the routers do feature an uplink which has to be set to “Hub” in case the connection PC-Router is going over an hub (hub-hub connection which would require a crossed cable if no uplink port were available))

For further information please refer to the test report (attached to this FAQ, file "ISDN-Router.pdf").

If the screen has not been touched for a long time, the screen of the display stays blocked. Only a powerup does reactive it!

In order to avoid this situation, it is necessary updating the boot with the programming tool PCD8.D81W.

Boot update procedure 

• For PCD8.D81w (VTWIN) version 4.81 (but older than V5.12), please copy the attached firmware files into the directory Firmware of the PCD8.D81W! Since version of PCD8.D81W  V 5.12  these new FWs are already included!
• In the PCD8.D81W software, choose the function "Tools" --> "Boot update" --> "Automatic"
• Enter the following code for the update
  371013
• Put the terminal im transfer mode
• Leave all settings with default values: Baudrate 9600...
• For more details see in the software manual under Boot Update.
• After the update of the boot, the programme and the firmware have to be re-downloaded to the terminal!

Remarks
If the displays PCD7.D785 / D788 are produced from june 2005 only the Firmware update is necessary (no boot update is needed)!
NEW: The new FW for PCD7.D785 / D788 is for all terminals (Rev. 4 or newer and Rev. 3 or older)

The "PCD driver" of the PCD7.D7xx terminals is not supported by all PCD systems.

Symptom
When the communication driver "PCD driver" is used in a PCD8.D81w project, the communication works on the PGU Port (port 0) of a PCD2.M110 (or a PCD2.M120) but not on the following systems: PCS1, PCD2.M150/M170/M480/M5xx0 or on a PCD3.

Reason
The PGU mode of recent PCD systems is no longer based on the P800 communication protocol (which uses the obsolete communication protocol "Mode D"). The recent PCD2 and the PCD3 use S-Bus on Port 0, and the PCD driver on the terminal uses P800 protocol. Because the PCD7.D7xx terminals use the P800 protocol if the "PCD driver" is selected, the communication does not work on systems developed after the PCD2.M110/M120.

Solution
So there are 2 solutions possible:

• Use the S-Bus driver on the terminal (recommended): In this case the project has to be adapted accordingly and an S-Bus connection cable is to be used (according to our Workshop Documents).
• Only for PCD2.M150 and PCD2.M170: Modify your communication cable (Pin 6 should not be used, Pin 6 of PGU port =0). In the PCD program you need to add a "SASI Slave Mode D" with the parameters: RS 232, 9600, Parity, 7-E-1.
  This solution can only be applied on PCD2.M150 and M170 systems, but not on other systems (because the Mode D is no longer supported).
  See attached document for wiring information in this case.

The PCD7.D7__ET offer the possibility to download the programme over Ethernet, the display switch automatic to download mode. This functionality exist already on the display produce after may 24th 2004. For the display produce before that date a Boot update has to be done first.

Use the menu "Tools" / Boot update / automatic of the PCD8.D81W V4.73 software, use the numerical code: 371013 and follow the instruction. Attention: keep the default setting baurate of 9600 Bauts for the download.

Afterward a FW download may be needed.

Some of the PCD7.D7xx terminals are available with a Profibus DP option, but this solution is obsolete and we recommend other solutions

The Profibus DP option has the disadvantage that the terminal is a slave and the PCD must organize the data transfer. This means

• that an FB per terminal is running in the PCD, which that is creating a significant CPU charge
• that the reaction time after user interactions on the terminal gets slow

We therefore recommend other solutions:

• Profi-S-Bus is to solution to be used together with new Classic products like the PCD2.M480 and PCD3.Mxxxx, it allows to have several terminals and PCD's on the same bus and the terminals are active participants
• MPI is the alternative for xx7 PCD's
• Ether-S-Bus or Serial-S-Bus connections are very often an alternative as well
• an ESANET network is sometimes interesting, but requires an independent network among the terminals. One terminal acts as Server for the others (Clients). The Server terminal must have two serial ports, one of which connected to the PCD via S-Bus, the other connected to ESANET

The Touch Screen Terminal loose the calibration from time to time.

If you remark this problem on your terminal, it will be nessesary to update the bootloader. This is possible with the version of PCD8.D81W VTWIN 4.73 (or newer).

Bootloader Download:
Choose in VTWin: Tools/Boot update/Automatic
All settings should have default values. Baudrate 9600...
Code for download: 371013
After this bootloader update you have to calibrate your terminal like describen in the manual and download the FW (see FAQ 100195)

A PCD7.D7xx Terminal can access several PCD's in an S-Bus network, it is as well possible to have one gateway station in the network and access PCD's that are located in a subnet. The response timeout has to be adapted accordingly.

If the PCD7.D7xx Terminal has to access S-Bus participants that are behind a gateway station, they are defined in the PCD8.D81W software as if they were in the same network. As passing a gateway station adds delay to the communication, the timout value (default 500 ms) has to be significantly increased (in the terminal) according to chapter 6.6 of the S-Bus manual. With PCD8.D81W versions until 4.66 the timeout can only be defined for the whole network, later versions allow to define the timout per station. The timout settings of the gateway and slave stations stay usually untouched.

There are a couple of common causes in case of a lack of communication. Please take care of the points mentioned below.

There are basically three sources of errors:

• the wiring: check the attached workshop document for details, remember that in most of the cases 3 bridges are necessary on the MSP. Without these bridges there is no communication
• the kind of protocol selected: always use S-Bus, don't forget to check whether the S-Bus Station address configured in the PCD8.D81W Software does match with the S-Bus address of the PCD(s)
• serial port settings: the PCD7.D7xx Terminals use S-Bus Parity Mode and are always master, per default at 9600 baud. Make sure the serial port of the PCD is configured or assigned in S-Bus Parity Slave Mode in the right baudrate

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.

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

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

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

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

PG5 1.4: (Windows XP) 

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

PG5 2.0: (Windows XP)

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

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

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

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

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

PG5 does not change the TAPI settings of Windows.

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



 

PG5 does apply the following rules:

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

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

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

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


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

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

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

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

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

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

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

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

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

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

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

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

Hints

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

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

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

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

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

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

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

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

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

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

Setup of the SCommDrv.exe On the client PC :

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

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

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

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

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

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

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

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

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

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

Remarks

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

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

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

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

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

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

Remarks

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

nslookup

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

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

§ix100292§

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

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

Criterias to choose an ADSL Router

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

Zyxel Prestige 650 ME-I

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

Zyxel Prestige 650 H-I

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

Devolo Microlink ADSL Modem Router

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

General Remarks

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

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

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

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

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

The issue is fixed on PG5 2.3.193

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

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

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

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

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

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

An Error message will be displayed.

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

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

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

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

To solve the issue:

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

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

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

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

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

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

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

Yes, it is available under:

play.google.com/store/apps/details

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

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

No, the LonWorks devices PCD2.F240, PCD3.F2400 and PCD7.R582 are no longer available.

The production of the LonWorks interface devices PCD2.F240, PCD3.F2400 and the LonWorks memory device PCD7.R582 was discontinued at the end of 2021 and the devices are no longer available.

As a replacement, we recommend the usage of BACnet.

In einem Pop Up Fenster erscheint die Meldung “Missing Application-Name manifest Attribut for:

Symptom:

Die gewünschte Webseite wird nicht angezeigt, stattdessen erscheint das nachstehende Fenster

Ursache:
Sun stellt die Sicherheits-Zertifikate für Java immer nur für 2 Jahre aus.
In älteren Versionen der Dateien IMasterSaia5_15_02.jar und IMasterXX7_5_15_02.jar (Version < 5.15.0229) wurden Informationen nicht angegeben die die neue Version von Java nun prüft.

Lösung:
Das Problem wurde mit der Version 5.15.0229 der IMasterSaia5_15_02.jar/ IMasterXX7_5_15_02.jar Datei behoben.
PG5 2.1.300 oder höher enthält das überarbeitete Java Applet. Der Austauch des Applet wird im FAQ 101878 beschrieben

Als vorläufige Lösung ist die Freigabe der IP- Adresse der PCD in Java Version 1.7.0_51-b13 möglich.

Dazu öffnen Sie aus der Windows- Systemsteuerung



Die Java Konsole



und gehen Sie dort auf die Registerkarte "Sicherheit". Hier gehen Sie auf Siteliste bearbeiten



Drücken Sie die Taste "Hinzufügen"
Geben Sie die IP- Adresse der PCD/ PCD'n im Format xxx.xxx.xxx.xxx ein.
Bestätigen Sie den Sicherheitshinweis mir "Fortfahren"



§ix101618§

Wenn Sie den Browser neu Starten wird die Webseite aus der PCD angezeigt.

In einem Pop Up Fenster erscheint die Meldung “Missing Application-Name manifest Attribut for: x.x.x.x/IMasterSaia5_15_02.jar&;

Wurden die Webseiten mit älteren Versionen des Web- Editor in PG5 2.0 und PG5 2.1 oder dem Web- Editor in PG5 1.4 erstellt ist es möglich das dieser Fehler auftritt.

Das neue Java- Applet das diesen Fehler behebt ist ab PG5 2.1.300 im Web- Editor integriert

Symptom:

Die gewünschte Webseite wird nicht angezeigt, stattdessen erscheint das nachstehende Fenster

Die Lösung für Anwendungen in denen das Applet IMasterSaia5_15_02.jar oder IMasterXX7_5_15_02.jar in der Version < 5.15.0229 verwendet wurde:
Laden Sie die IMasterSaia5_15_02.jar Version 5.15.0229 oder höher von unserer Support Homepage, Bereich PG5 2.0/S-Web Editor und ersetzen Sie die existierende *.jar Datei in Ihrem Projekt Verzeichnis und/ oder auf der PCD mit der neuen Datei.
Wird das Java Applet im PG5 Web- Builder verwendet kopieren Sie das neue Java Applet in das Web- und HTML- Verzeichnis Ihres PG5 Projektes. Führen Sie einen neuen Compile im Web- Builder und PG5 Projekt durch und laden Sie das Projekt in die PCD.
Kopieren Sie die beiden Dateien ebenfalls in das S-Web Editor 5.15.02 Verzeichnis damit diese in neuen Projekten Verwendung finden.
Dieses Java Applet Version 5.15.0229 oder höher enthält das neue Manifest.