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

Reason:

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

 

 

Solution:

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

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

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

Remark:

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

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

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

 

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

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

The below table shows the version compatibilies.

Windows OS	Browser	Java version 1.7.0_65	Function
32 Bit	32 Bit	32 Bit	OK
64 Bit	32 Bit	32 Bit	not OK
64 Bit	64 Bit	64 Bit	OK

We did tests with Firefox, Internet Explorer and Chrome

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

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

64-Bit IE

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

64-bit Java

 

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

 

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

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

 

Symptom:

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

Reason:
On older versions of the files IMasterSaia5_15_02.jar and IMasterXX7_5_15_02.jar (version < 5.15.0231) there where some missing information’s which the new version of java now does check.

The problem is fixed since the version 5.15.0231 of the IMasterSaia5_15_02.jar/ IMasterXX7_5_15_02.jar file.
PG5 2.1.300 or later does include the corrected java applet.

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

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

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


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


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


After this there will be a warning window like this:


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



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

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

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

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

 

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

 

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



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

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

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



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

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

 

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

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

 

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

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

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

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

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

 

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

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

 

Reason:

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

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

 

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

 

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


Possible reason
The licence for Web Editor Advanced is missing!

Possible solution
Update your PG5 licence with Web Editor Advanced!

 

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

 

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

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

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

• 0 ==> No init phase message displayed

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

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

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

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

 

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

 

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

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



just below the line

example of html-code


Alternative solution
use WebEditor 5.15.03 or WebEditor 8 once available.

 

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

 

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

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

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

 

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

 

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

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

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


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

 

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

 

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

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

 

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

 

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

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

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

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

The minimum required versions are:

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

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

 

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

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

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

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

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

MB Panel version	Minimal firmware	Remarks
PCD7.D4xxD (SVGA)	1.18.12	-
PCD7.D4xxV (VGA)	1.18.28	first internal firmware version: 1.18.12
PCD7.D4xx_ (QVGA)	not supported

Screenshot for example project

Restriction:

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

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

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

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

 

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

 

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

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


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

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

 

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

 

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

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

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

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

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

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

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

 

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

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

 

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

 

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

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

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

 

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

 

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



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

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

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

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

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

 

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

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

 

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

 

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


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

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

 

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

 

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


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

 

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

 

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


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

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

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

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

 

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

 

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

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

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



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


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

 

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

 

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


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

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

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


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

 

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

 

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

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

Reason
The HVC FBoxes "Set-point ramp" and "Set-point slide" from PG5 2.0 did not contain all the A-Symbols (they have been removed because the displayed value has been wrong).

Solution
Please update your PG5 2.0 Heavac library to version 2.6.151 (this library is not by default in PG5 2.0 SP1) or later.

 

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

 

 

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

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

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

 

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

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

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

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

 

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

 

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

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

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

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

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

 

 

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

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

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

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

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

 

When compiling a project in PG5 the error message: "more than 383 elements in DB" appears. How can this problem be solved? And where does it comes from?

 

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

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

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

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

 

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

 

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




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

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

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




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

 

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

 

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

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

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

 

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

 

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

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

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

 

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

 

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

 

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

 

 

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

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

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

 

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

 

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

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

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

 

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

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

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

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

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

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

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

Remarks

• When working with PG5 2.0.110 or later the S-Web Editor together with all required FBoxes mentioned in this FAQ are already installed. Examples for PG5 2.0 are available under:
  "General information" --> "Getting Started" --> "Program Examples" --> "PG5 2.0" --> "Web and HMI"
• When working with PG5 1.4.300 the S-Web Editor together with an example, the required FBoxes and firmware versions for PCD2.M5xx0 and PCD3.Mxxx0 can be downloaded from the support site from section
  Software --> PG5 --> PG5 1.4 --> PG5 1.4 Suite (scroll down until "Web Editor 5.14.27 package")
• The versions mentioned above are the first versions that support the according feature. As the versions all are backward compatible, it is recommended using the last version rather than downgrading a system to the version indicated above.
• The first name of this FAQ was "Which functionality is supported in which Web Editor, Micro Browser and firmware version?"

 

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

 

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

New features

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

Corrections

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

---

S-Web Editor package 5.14.27 (August 2009)

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

New features

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

---

Remark

The S-Web Editor together with the required FBoxes can be downloaded from the support site from section
Software --> PG5 --> PG5 1.4 --> PG5 1.4 Suite (scroll down until "Web Editor 5.14.30 package")

 

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

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

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

 

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

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

1 errors, 0 warnings

Solution
There are two possible solutions 

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

 

 

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

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

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

 

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

 

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

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

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

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

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

 

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

 

 

 

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

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

 

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

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

 

 

The following text definition option has to be used:


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

 

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

 

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

 

 

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

 

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

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

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

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

Example for the use of the session containers

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

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

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

The functionality was tested with

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

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

 

 

 

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

Internal Error: PCDBrowseForSymbolDlg2()

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

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

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

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

 

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

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

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

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

 

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

 

 

Error message displayed on the S-Web-Editor

Bug fix to allow storing the page:

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

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

 

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

 

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

 

 

 

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

 

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

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

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

 

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

 

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

 

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

"MB_VERSION"	shows version of the xml configuration file
"MB_APP_VERSION"	shows version of the MicroBrowser
"MB_OS_VERSION"	shows version of the OS
"MB_PLATFORM"	shows the platform name, is one of the following "uBT", "uBCE", "uBXP", ...
"MB_SCREEN_WIDTH"	shows the width of the screen
"MB_SCREEN_HEIGHT"	shows the height of the screen
"MB_IpAddress"	shows the IP address of the panel
"MB_Subnet"	shows the subnet mask of the panel
"MB_Gateway"	shows the gateway address of the panel
"MB_Volume"	this container is used to get and set the volume in percent
"AUTOINCRCO"	this container is incremented on every period
"BLINKCO"	is AUTOINCRCO modulo 2
"MB_InactivityCounter"	this container counts up every second. It is reset to 0 on any mouse or key actions of the user
"MB_StartProcess"	this container is used to write the name of the application to start
"MB_ExeToTop"	this container is used to write the name of the program to bring on the top
"MB_BringWindowToTop"	this container is used to write the name of the window, or a part of it, to bring the application on the top. writing "_self" will bring the MicroBrowser on top
"MB_WakeUp"	write 1 to wake up the computer and to stop the screen saver
"MB_Backlight"	write 0 or 1 to turn off/on the display or the LCD backlight
"MSGBOX_NR"	show the number of messages appended in the message box
"MessageBoxCO"	show the text in message box
"MB_UpdateAfterPpoWrite"	write "0" or "1" to improve the reaction time after writing on any PPO
"MB_UpdateAfterCoWrite"	write "0" or "1" to improve the reaction time after writing on any CO
"@MODAL_FOREGROUND"	write "0" or "1" to disable or enable the modal foreground teq
"@LANGUAGE"	to write the name of the new CSV file to load
"@MB_FKEY_EVENT"	show the last function key proceed
"@MB_FULL_REDRAW"	write "0" or "1" to disable or enable the full redraw mode
"_KEYPAD"	used by the keypad teq to edit the value
"_KEYPAD_DEST_NAME"	used by the keypad teq to save the name of the destination to write
"_KEYPAD_DEST_TYPE"	used by the keypad teq to save the type of the destination to write
"_KEYPAD_SHIFT"	used by the keypad teq as caps-lock
"_KEYPAD_OPEN"	used by the keypad teq to open a new keypad
"_KEYPADCLOSE"	used by the keypad teq to close the keypad, or to switch between alpha-pad and numeric-pad
"_KEYEVENT"	by the keypad teq to append new characters used
"_KEYPAD_TF_FOCUS"	used by the keypad teq to select the editable text field after closing the keypad
"MB_PERCO_0"	Persistent container  0 stored in "uBrowsCo.xml"
"MB_PERCO_1"	Persistent container  1 stored in "uBrowsCo.xml"
"MB_PERCO_2"	Persistent container  2 stored in "uBrowsCo.xml"
...
"MB_PERCO_19"	Persistent container 19 stored in "uBrowsCo.xml"

 

Sometimes it's quite useful to have a link to all the PPO variables one uses in the WebEditor. There's a PPO list of the WebEditor used global variables. And one can also generate a Cross-Reference-File that lists all the *.teq-files and the PPO variables used in these *.teq.

 

In the WebEditor you can generate under 'Project' -> 'Generate Cross Reference file' this Cross Reference list. It's saved in the 'Web' folder of your working CPU and is called *CrossRef.txt. You can open this file with a Text-Editor and search for your variables and find out where they're used in your WebEditor project.

 

It is possible to close the MicroBrowser Software with a special button action programmed in the WebEditor.

 

In case you run the MicroBrowser Software in Kiosk Mode 2 or higher and you want to permit a special user (special logged in) to access the Windows CE Desktop without using a keyboard to close the MicroBrowser (uBroswser) Software.
 
How to close the uBrowser with a button?
Copy the value "killme" into the special Container "MB_StartProcess". This will close the actual running MicroBrowser Software (see screenshot below). This button can easily be hidden and protected when not logged in.

 

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.

 

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!

 

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 instruction CODEBASE allows to define where the java applet file "IMasterSaia_x.jar" shall be searched and loaded from.

This allows storing the java applet file "IMasterSaia_x.jar" on a Web-Server somewhere on the network (Intranet or Internet) and not on the PCD.

 

Update 20.10.2014
Sun has changed the security behavior of Java since the Java version 1.7.0_51-b13.
Since the codbase instruction is also in this security 'area' it's necessary to allow the access to the external web-sever which hosts the IMasterSaia_x.jar file on the java settings as described in the FAQ#101878.

The instruction
The instruction CODEBASE has to be written on the html file generated from the S-WebEditor.
After a "Build All" on the S-Web-Editor you have to edit manually the *.htm or *.html file from the "html" folder of your PG5
project and you have to modify the following entry:
APPLET ARCHIVE="IMasterSaia5_14_30.jar" CODE="IMasterSaia5_14_30.class" ALIGN="BOTTOM" WIDTH="640" HEIGHT="480"

to:
APPLET ARCHIVE="IMasterSaia5_14_30.jar" CODEBASE="sbc-support.com/faq/general/applets" CODE="IMasterSaia5_14_30.class" ALIGN="BOTTOM" WIDTH="640" HEIGHT="480"

After the keyword CODEBASE you have to specify the TCP/IP address or URL of the Web-Server which does store the java applet file "IMasterSaia_x.jar".

Example
In the example above the file "IMasterSaia5_14_30.jar" is loaded from the WebServer sbc-support.com, from folder /faq/general/applets/.

Every Web-Application which is connected to the Internet could now use the file "IMasterSaia5_14_30.jar" located on this Web-Server.

If you have no internet access and you have a second PCD in the network in which the .jar File is loaded. Then you have to change in the html file the text to CODEBASE="xxx.xxx.xxx.xxx" (x = ipaddress of PCD with the .jar File)

Remarks

• Please note that each "Build All" in the S-WebEditor will reset the modifications in the *.html and the file needs to be modified again manually.
• In case you do not yet have an own server which hosts the applets, you could use for your tests the applet which is present on the sbc-support.com server in folder: www.sbc-support.com/faq/general/applets/
  The following applets are currently present in this folder:
  - IMasterSaia5_14_27.jar
  - IMasterSaia5_14_30.jar
  - IMasterSaia5_15_02.jar
  - IMasterSaia5_15_03.jar
  - IMasterXX7_5_14_27.jar
  - IMasterXX7_5_14_30.jar
  - IMasterXX7_5_15_02.jar
  - IMasterXX7_5_15_03.jar
  Please note that Saia-Burgess Controls AG can not ensure a 100% availabiliy of these files which can create service interruptions of the web project. By using the link to these files you agree to the fact that SBC refuses any responsability for service interruptions and damages created in consequence and reserves the right to remove the files from the location described above without notice.

To enter e value in to an edit field it's possible to use only a numeric keyboard instead of the alphanumeric keyboard.

 

Instead to edit a value with the “original” alphanumeric keyboard of the CE-Panel it’s possible to edit the value with the use of a alphanumeric keyboard: 
  

You have to make the following steps: 
Add the file keypad.teq to your Web-Editor project. (With the menu point: Project, add to project, file). 
The file keypad.teq could be found on the dirctory
C:\Program Files\SAIA-Burgess\Web Editor 5_13_00\QVGATeqlib\KEYPAD.TEQ

On the CE-Panel you have to modify the file “uBrowser.xml” stored on the folder “storage card/microbrowser”.
There you have to change the parameter sip "1"  to
"0"

After restarting the microbrowser on the CE-Panel the numeric keyboard “keypad.teq” will be used instead of the alphanumeric keyboard of CE-Panel. 

Remark about the difference between the “original” alphanumeric keyboard of CE-Panel and the numeric keyboard “keypad.teq”:

- If you do edit a value with the “original” alphanumeric keyboard of CE-Panel then the “original” alphanumeric keyboard of CE-Panel is placed on the foreground of the Web-Page and the Web-Page in the background (which does contains the edit filed) is still visible.

-  If you do edit a value with the numeric keyboard “keypad.teq” then the numeric keyboard “keypad.teq” is placed on the foreground of the Web-Page and the Web-Page in the background (which does contains the edit filed) is not visible.

 

You have to use a special comparison condition “<” then “1” (less then value 1) in the option “Hide and Disable Painter” of the painter properties.

 

The S-Web Editor allows hiding elements depending on the value of the PCD variable.
This is done with the option “Hide and Disable Painter” on the painter properties.

If you do use a comparison condition “=” and for example you want to check if a flag of the PCD has the value 0 or 1 then during runtime the MB-Display or CE-Panel have to read first the value of the PCD flag.
As soon as the MB-Display knows the status of the flag the condition of the comparison is checked and the depending of the result, the painter does hide the painter or not. 
The MB-Display or the CE-Panel does show the painter until he knows the status of the flag.
This behavior lead to the situation, that the painter is shown shortly on the MB-Display or the CE-Panel. 

To avoid this behavior you have to use the comparison condition
“<” then “1” (less then value 1)
instead of the condition
“=” then “1” (equal then value 1) in the option “Hide and Disable Painter” of the painter properties. 

Please note that this behavior occurs only on:
-          MB-Display (PCD7.D4xx)
-          CE-Panel if the Microbrowser is used. (PCD7.D5xxx)

 

Yes, this is possible by using a container variable.

 

Procedure for accessing PCD resources in a Web Page indexed
In the S-Web Editor you have to add the content of a container variable to the basis address of the PCD resource as following:
Depending of the version of the Web-Builder it's possible to use the symbolic ressource name of PG5.

For all versions of the Web-Builder: 
PDP,,PCD_Address+@COFF_Container_name@,d

The signification of this syntax can be found in the following table:

PDP,,	Start of the Syntax Process data point
PCD_Address	Base address of the PCD resource
+@COFF_	Start delimiter for the name of the container variable
Container_name	Name of the container variable
@	End delimiter for the name of the container variable
,d	Format of the resource

Only for Web-Builder with version > 2.0.31: 
PG5_Symbol_name+@COFF_Container_name@,d

The signification of this syntax can be found in the following table:

PG5_Symbol_name	Symbolic Name of the PCD resource
+@COFF_	Start delimiter for the name of the container variable
Container_name	Name of the container variable
@	End delimiter for the name of the container variable
,d	Format of the resource

During runtime of the Web project, the content of the container variable is added to the base address of the PCD media. 

Example
You have defined 2 container variable with the name “First_pointer” and “Second_pointer”.
The container “First_pointer” does contain the value 10.
The container “Second _pointer” does contain the value 5. 
If you do write the following PPO name on the S-Web Editor items “static text” or “edit box”, then you will have the following results:

Syntax in the S-Web Editor	Following PCD resource are accessed
PDP,,R100+@COFF_First_pointer@,d	Register 110
PDP,,R100+@COFF_First_pointer@+@COFF_Second_pointer@,d	Register 115
PDP,,DB20+@COFF_First_pointer@.2+@COFF_Second_pointer@,d	DB 30 element 7

with symbolic ressource name of PG5:
(Name of the PG5 ressource: My_Reg with address 200) 

Syntax in the S-Web Editor	Following PCD resource are accessed
My_Reg+@COFF_First_pointer@,d	Register 210
My_Reg+@COFF_First_pointer@+@COFF_Second_pointer@,d	Register 215

 

If the alarm text is too long, the active alarms are not displayed at all (only in Microbrowser CE versino 1.5.10.82c and older).

 

 

Symptom
Active alarms are not displayed by the Microbrowser running on a Windows CE panel (PCD7.D5xxx). The "Microbrowser CE" version used is 1.5.10.82c or older. Additionally, the alarm texts are rather long and maybe unicode characters are used.

Reason
The maximal length of an alarm line in the Microbrowser CE is 128 bytes (including invisible characters). In case unicode characters are used, it is possible that the visible text can only be 43 characters. (Note that unicode characters with code > 0x7f do require 2 or 3 bytes per character to be mapped).
Until and including version 1.5.10.82c, the Microbrowser CE doesn't show texts that exceed 128 bytes lenght. Later versions do/will show only the characters that are present in these 128 bytes.

Solution
Shorten the alarm texts for that they fit in 128 bytes.

 

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

 

There are several reasons listed below why your start page may not be displayed

 

- No virtual Java machine installed at all. We need a virtual Java machine to display dynamic
web pages. On never Windows virtual Java machine isn't installed anymore, because .Network
based. Get the actual version from www.java.com

- The versions of IMasterSaia5_xx_xx.jar on the PCD (or in the WebConnect folder) and the
one used in the WebEditor project don't match.

- When you address your PCD via HTTP-direct by simply browsing with the IP-Address
(i.e. 172.16.1.141) then per default the page start.htm will be displayed. If your project
doesn't contain this start.htm file, then the default start.htm from the firmware, with "Login/Logout",
"PCD Status" and "Variable Lists", is displayed. If your *.htm/*.html start file has another name
then you'll have to address it with it's name i.e. 172.16.1.141/mystart.htm

- Your start page (*.htm or *.html) is not in the user programm of the PCD, not on the Flash Card
of the PCD and not in the WebConnect folder.

- Your *.teq file you defined as your main-teq file in the WebEditor project is not in the user programm
of the PCD, not on the Flash Card of the PCD and not in the WebConnect folder.

 

There are some nice features that can be executed when actioning the WebEditor Buttons

 

URL jump to another PCD and open this page in a new Browser tab by using the "_new" argument. Condition is, that
the start page of the WebEditor project in the other PCD is called "start.htm". So, the name of the start page can be neglected.


URL jump to a www-address and open this page in a new Browser tab by using the "_new" argument


Open a *.PDF-File from the local Flash-Card with a non-Micro-Broswer panel in a new tab of the browser


Open a *.PDF-File from the local storage card with a Micro-Browser software running on a CE Windows touch panel.
Starts the PDF-Viewer in a new Micro-Browser Process


Opens from the CE-Panel in the Micro-Browser the Internet Explorer in a new window and giving the URL to open
directly as an argument / parameter. Starts the Internet Explorer in a new Process



Check if the user browses with a Micro-Browser or with a non-Micro-Browser to implement respective actions in
the WebEditor project. Display / hide buttons, actions of the button, etc

Check the Container variable "@MB_OS_VERSION". It contains the value "0" if you browse with a non-Micro-Browser
or the respective version of the Micro-Browser

 

Yes, it is possible to add a new curve in an existing trending diagram during runtime of the web page using a new field.

 

If you want to add a new curve on an online trending of the Web-Editor during runtime of the web page, you have to use the button "New" on the online trend macro.

If the symbolic name of the new data curve does exist in the *.tcr file (means that this symbolic name is used on the Web-Editor project) then it's possible to enter this sybolic name in to the field.
If the symbolic name does not exist in the *.tcr file then you have to enter the new curve paramter as PDP,,R100,d syntax (example for the register 100)

The other three fields can be used to define the min. and max value of the new curve as the color for the new curve.

If you want to know which symbolic name does exist in the *.tcr file you can upload the file directly on the web-browser by writing the *.tcr name on the address field of the web-browser.

 

If you work with 'Filezilla' or other FTP clients, to access the FTP server on SBC PCD® systems take care about this remark about the active or passive FTP connection.

PCD FW < 1.22.xx does support only the FTP active mode.

PCD FW >= 1.22 xx does support the FTP active and passive mode.

 

You can download this freeware on www.filezilla.de in the version that fits with your operating system.
It's Multilanguage and comes along with some nice features as 'Drag&Drop', 'Upload/Download Queue', 'Keep-Alive-System'.

There's only one detail you have to be aware when you use the PCD FW < 1.22.xx:
You must use 'Filezilla' in the 'active' mode.
Per default 'Filezilla' runs in 'passive' mode and therefore it's necessary to change the connection to 'active' mode as described in the user manual for 'PCD3.R600' in the chapter 'Examples for connecting the PCD® FTP-Server' under 'Filezilla'.

If you use the PCD FW >= 1.22.xx you can also use 'Filezilla' in the 'passive' mode!

 

All the application is working correct with no error indication, nevertheless, the Alarms aren't displayed in the Web Alarming list. The list remains blank and no columns are visible as on the picture below.

 

Symptom
All the application is working correct with no error indication, nevertheless, the Alarms aren't displayed in the Web Alarming list from the Alarming Macro. When displayed on a PC with the Internet Explorer or Firefox, the list remains blank and no columns are visible as on the picture below.

When displayed on a VGA MB Panel with firmware 1.12.05, the error message "Error -51: .../alarm.exe?-6&sta failed!" is displayed in the Message Box teq view. 

Reason
This phenomenon can be caused by an incorrect format configuration of the PPO "A.Alarm.ThisAlarmList.MyName", "A.Alarm.AllgemeineAlarmliste.MyName" (or however your Alarmlist is called). This PPO must have the format "STRING" and unfortunately not all S-WebEditor versions do automatically define this format.

If the format is empty or not equal "STRING", the alarmlist will not work correctly.

Solution
Define the format "STRING" for the AlarmList PPO and rebuild the S-WebEditor project. Once the S-WebEditor project is rebuilt, execute a "Rebuild All..." in the PG5 Project manager and download the project (the *.tcr file must be updated on the PCD; this file is concerned by the modification of the format).

 

The FBox SWeb Alarm Init is green but no alarms are displayed on the AlarmingOff.teq displayed in the Web Application. Check what SWA alarming library version you have. This problem is known in the version SWA alarming_V1_3_000_ml.exe.

 

 Solution:

Update the library with this version:  SWA alarming_V1_4_200_ml.exe which is available in PG5 1.4 200! After the installation of the new library the FBox SWeb Alarm Init has to be replaced by the new one.

Remark: This library is available on the PG5 1.4 200 installation CD under: \Fbox libs\C\

 

As those fupla librairies aren't used by all customer there aren't installed automatcaly in fupla editor during PG5 installation. They have to be installed manually from PG5 installation CD.

 

The libs HDLog_V1_3_00x_ml.exe and SWA alarming_V1_x_xxx_ml.exe are located in PG5 installation CD under: \Fbox libs\C\

After the installation thoses libraries are located in the FBox selector under User.

 

In some cases (e.g. in a Web Editor project for a QVGA MB Panel) the widths of the columns of the alarming macro are not convenient. In this case it's possible to adapt the columns width of the alarming macro by following the procedure described in this FAQ.

 

Modifying the column width in alarming macro
In case the specified widths of the columns in the alarming macro is visually not fitting, these widths can be modified.

• In the S-Web-Editor 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.

• Adjust column width. The numerical values correspond to the percentage of the entire width, according to which the column is to begin. If a column is to be hidden, the value “120” is to be entered.
  So if the first two values are “120“, the columns “StatusColour“ and “Alarm ID“ are not displayed. The column “Alarm text“ starts at the beginning (with 0% of the width), followed by “Time on“ with 58% of the width etc. 

Remark
This explanation together with other useful information can be found in the Getting Started example "Getting started with the QVGA MB Panel" on the support site (Section "General Information" --> "Getting Started" --> "Program examples" --> Web- and HMI).

 

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

If the text passed to the FBox "HDLog Bin" (from the FBox library "Historic Data Logging" version 1.3.000) is a global symbol a build of the project fails due to a "Multi Defined Blocks"-Error.

 

Symptom
A build of a PG5 project containing the FBox "HDLog Bin" from the FBox library "Historic Data Logging" fails if the symbol entered on the face of the FBox is a global symbol. The error message shown in the message window of the PG5 Project Manager is:

Multi-defined Blocks:
TEXT/DB MyText (4001) in modules: 'Fupla.obj' '_Global.obj'
Linkage complete. 1 errors, 0 warnings.

Reason
This is a bug in PG5 SP1.4.130 and will be corrected in the next release of PG5.

Solution
As solution until the next version of PG5 is released please do not declare the text entered on the face of the FBox as "global" symbol.
In case the same text is also used in another program module, provide a static address to this text and refer to this static address from the other module where the same text is used.

 

Together with PG5 SP1.4.130 a new version of the "Historic Data Logging" FBox library has been distributed. Due to a small bug the FBox "HDLog Init" causes this error on build of the PG5 project.

 

Symptom
On build of a PG5 project that contains an FBox "HDLog Init" from the FBox library "Historic Data Logging" version 1.3.000 the following message is shown:

Assembling: Fupla.fbd
Warning 2: C:\Program Files\SAIA-Burgess\PG5 1_4\Libs\Usr\HDLOG.lib: Line 1279: Parameter "Name" not used in macro "_HdaInit"

Reason
This is a small bug in the FBox "HDLog Init" and means that an internal parameter is not used (because there is no reason to use it). However, the FBox code should avoid this message.

Solution
This warning can be ignored. The functionality of the FBox or the project is not influenced.
The next release of the library will avoid this warning. 

 

The PG5 Controls Suite package available on the support page was not complete during the three two weeks (until 1 February 2007) it was online. The release notes of the S-Web-Editor 5.10.00 as well as the the macro library for the S-Web-Editor were missing.

 

Description
Customers who have downloaded the PG5 Controls Suite (PG5 SP1.4.130) before the 1 February 2007 are missing the Release Notes of the S-Web-Editor 5.10.00 as well as the macro library for the S-Web-Editor.
Further on there have been some broken links on the Index page of the package.

 

Solution
The missing files are available on the support site in the PG5 section. Please download these files and complete your installation.

Note
The available package on the support site has been corrected.
This FAQ does not concern you if you have downloaded the package after 1 February 2007 or if you have received the PG5 SP1.4.130 on a CD. 

 

The values of persistent containers are stored permanently on the file system. If you close MicroBrowser the values of the persistent containers are not lost.

 

The value of the container variables of the S-Web-Editor are not stored if the web application is closed.

If you want to store values of container variables, you have to use the persistent container variables. (MB_PERCO_0 to MB_PERCO_19)

This is very useful if you want to save language settings for example. The persistent containers have no specific purpose, you can use them for your own needs.

The container variables are stored permanetly on the file system of the following web panels:

- MicroBrowser Panel:          PCD7.D4xx
- Windows CE Web Panel:     PCD7.D5xxx

On the other web panels it is not possible to store persistent container variables.

On the Windows CE web panel PCD7.D5xxx the persistent container variable are stored on the file "uBrowsCo.xml“ on the directory "StorageCard/Micro-Browser/“ of the flash card of the web panel.

 

Yes, it's possible to store the last used language and to restore this stored langauge during startup of the Web-Panel

 

To store the last used language you have to make the following steps on the S-Web-Editor:

Create a own page where you select the language which you want to use.
To select the language you have to use a button whit the functionality "Set Variable on mouse down" where the Container Variable @LANGUAGE is written with the language specific *.csv file name.

On the same page, place a macro "EventP_wrCo2Co_onLostFocus_x“ or „EventP_wrCo2PPO_onLostFocus_x".
This macro will write the container variable @LANGUAGE in to a persistent container or in to a PCD variable if the page is leavead.

On the start page of the Web application place a macro:  „EventP_wrCo2Co_onGainFocus_x“ or „EventP_wrPPO2Co_onGainFocus_x".
This macro will copy the content of the persistent container or the PCD variable in to the container variable @LANGAUGE  if the page is called. 

Please note, that if you do store the Container variable @LANGUAGE in to a PCD variable this will invoke the behaviour that all Web-Panel which does access the Web-Application on the PCD do use the same language during startup.

If you do store the @LANGUAGE in to a persisten Container this will lead to the situation, that each Web-Panel could have stored his own, different langauge. 

 

On a CE Web-Panel it's possible to use also the persistent container variable.

 

    Its possible to use the persistent container variable MB_PERCO_0 to MB_PERCO_19, which are availabe on the S-Web Editor, also on the CE-Web Panel.

 

The value of this persistent container variable are stored on the flash card of the CE Web-Panel on the following folder:
„StorageCard/Micro-Browser/“
in the file "uBrowsCo.xml"

 

When using alarming the alarmlist has to be defined as STRING in the PPO list. Otherwise this can cause errors.

When using OfflineTrend the resource used as Base PPO Name has to be a register if it is a DB it causes a wrong pointing and this error message is created.

 

Problem
When opening the Web Application the warning button is displayed and when clicking on the button the message: "TEQ file parse first char error file" is displayed.
 

Reason
1) If alarming is used the error can be caused by the alarmlist. The alarmlist has to be defined as STRING in the PPO-list. If there is no definition it won't work.
2) Another reason for this error can be that a text in the page is not defined as STRING.
3) If Offline Trend is used and a DB is choosen as Base PPO Name (instead a Register) a wrong pointing is created in the Web builder file (xxx.tcr).
4) If in the PPO list, a register variable has the format STRING

Solution
Define the alarmlist / text as STRING in the PPO list.
Define a register as Base PPO Name in the Offline Trend Macro (in Tag Macro Offline Trend)
Don't define a register as STRING

 

For "non Saia PCD® COSinus systems" the option "Encode Special Chars" must be unchecked within:

S-Web Editor 5 > Project Configuration > Project - Applet Advanced

S-Web Editor 8 > Project Configuration > Runtime - General

 

Symptom
Instead of the PPO values, "No Message" is shown in the Web Editor Project. The PCD used is one of the following types:

• PCD1.M1x5
• PCD2.M15x or PCD2/4.M17x
• PCS1.Cxxx

Reason
If the option Encode Special Chars on the Applet Advanced tab of the Project Configuration dialog within S-Web Editor is checked, the Java applet encodes certain characters (e.g. comma) when ordering PPO values at the web-server.
Unfortunately such an encoded order is not properly interpreted by CPUs other than PCD3 or PCD2.M5xxx.

This problem can only occur if someone has manually checked the Encode Special Chars option, because this option is unchecked per default.

Solution
To solve the problem, proceed as following 

1. uncheck the option "Encode Special Chars"
   (For S-Web Editor 5)
   

             (For S-Web Edtior 8)
            

1. execute a Build All in the S-Web Editor
2. execute a Rebuild All in PG5 Project Manager
   
3. download the updated program to the PCD
4. restart the Web-Browser to ensure that the Java applet is actually reloaded, since some VMs use a kind of caching mechanism otherwise

Formating problems may prevent the displaying of texts which are defined inside CSV files.

 

The SBC Web-Editor allows to define texts (so called "HTML tags" and alarm descriptions) inside of one or more CSV files. This is especially powerful when designing multi-language applications, but may also be handy for single-language applications with many different alarms.

Be careful when editing the CSV files

When editing the CSV files, it is very important to maintain the exact format of the file. Every line starts with an ID sequence which must not be changed, otherwise the applet or Micro-Browser will not find the regarding entry anymore. Only the part after the separator character (e.g. the semicolon) is allowed to chance. Please do not substitute the separator character with another character, it won't work!

Potential problems when using spreadsheet programs

Special attention is necessary when editing the CSV file with a spreadsheet program, because these programs tend to change the file formating. Microsoft Excel, for instance, could change the separation character without any warning, depending on the actual language settings of your system. It has also been reported by customers, that Excel makes CSV file entries invalid by adding quotes or double-quotes around texts. Please be aware that these are only examples: Things like these can also happen with other programs!

CSV editing tips and tricks

After saving a CSV file that has been edited with a spreadsheet program, you should open the CSV file with Notepad (or any other "plain" text editor) to double check, if the format is still valid. Best editing results are achieved by using an advanced text editor like UltraEdit, Programmer’s Notepad, EditPad Pro etc. Unicode should be supported by the editor when creating or editing files with special character sets, e.g. asian, cyrilic characters.

 

Please check PPO format definitions in Web-Editor if some or all GIF graphics or TEQ views are not displayed, although the regarding files are available within the PLC's RAM or flash memory.

 

When using PPOs which are texts variables within the PLC, it will always lead to problems if the PPO format is not defined properly. The possible effects reach from missing some TEQ views and/or GIF graphics, to not loading the web-application at all!

So if you run into such strange behavior of a web-application, you should carefully check that all text PPOs are really set to STRING format within Web-Editor's PPO list. Please note, that it is not OK to leave the format property empty in case of texts!

 

In order to use the FKEYs of the uBrowser Panel it is necessary to add button on the web pag and configure the function key accordingly. Hereby the description:

• place a button on your teq file. Or outside the teq file so the button can't be activated on the touch screen, in this case make your teq file bigger (menu: Project / Teq view configuration) and give for example Height 280 instead of 240!
• Within the Button parameters, In tag "Function Key" typ the following syntax: FKEY_1 (to FKEY_12) according to your need
• Configure the other parameters depending of the needed action as usual for any other button
• If the button is placed on the touch area you might need to make it invisible, so in the tag "General" of the ajust parameters window deactvated the 2 options: Has Internal Color and Has Outfite Color

In the WebEditor it's possible to display also non-ASCII character set text using "HTML TAG" in combination with a *.csv file.

§ix100428§

§ix100429§

§ix100430§

On the attached example you can see, how the RTC of the PCD could be displayed and modified on a Web-page.

Also it's possible to know, if the PCD is running or is stoped.

 

 

To read the RTC of the PCD the FBox "Read Time" have to be used.
To know the date, the ouptut "Day" of the FBox have to be dived with 1000000.

 

§ix100390§

On the S-Web editor the symbol Clock_HMS have to be defined as format HH:MM:SS
The Clock_Date has the format DD.MM.YY

To write the RTC of the PCD the FBox "Write Time" have to be used.

§ix100391§

On the S-Web editor the symbol Write_HMS have to be defined as format HH:MM:SS
The Write_Date has the format DD.MM.YY

To know if the PCD is running or not the FBox Load timer is used.

§ix100392§

Each cycle the timer is loade with a value 10. If the PCD is not running, then the timer does elaps to 0.
Checking the value of the timer on the Web-Editor allow to know if the PCD is running or not
Timer > 5: PCD is running
Timer = 0: PCD is stoped.

 

 

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

 

The FBox "HDLog Init" from the family "Historic data logging" can cause a problem during the build of the according project. The Error message is "Constant out of range".

 

Symptom
A build of the Project fails due to the error message
Operand errors:
Error 336: new_hda.obj (806): CMP: __CSTART__: Constant out of range
This problem disappears if the Fupla containing the Inizialize FBox "HDLog Init" from the FBox family "Historic data logging" is not linked. This FBox is used for the creation of trends in the Web-Editor.
The FBox macro is called _HDAINIT and the version number is 10201 (right-click on the FBox and select "Advanced info" in order to see this information).

 

Reason
This problem is caused by a bug in the FBox, when the FBox code lies below a certain (high) memory address. Therefore, the problem normally only occurs in larger programs.

Solution
In order to avoid this problem the Fupla file that contains the Inizialize FBox "HDLog Init" has to be placed at the very beginning of the "CPU Link Order" (menu "CPU"-->"Link Order..."). Additionally, it may become necessery to place the "HDLog Init" FBox on the first few pages of the Fupla file. (Hint: To move up a Fupla page/block, use Ctrl+Up in the Page Navigator).
This bug will be fixed in the first Service Pack of PG5 1.4

 

In case your browser shows some text before and after the Web-Editor applet, it might be that at least one of your PPOs has the configured format "string" but is in fact a numeric value.

 

Symptom
Your browser shows strange texts such as "GENERATED FROM PLC EDITOR by ININET Solutions GmbH on Friday, November 25, 2005--> " before the applet (showing the pages generated with the Web-Editor). After the Applet, some other strange characters can appear.
§ix100321§

 

Reason
The reason for this phenomenon most likely is the fact that a numeric PPO does have the format "string" configured.

Solution
In order to solve this problem, open the window "PPO Initialisation". The "Init PPO..." is to be found in the menu "Project" of the Web-Editor. In this window, check the format definitions of the used PPOs. Make sure all integer medias (registers etc.) do not have the format "string" configured! 

 

The Web Editor does show the pictures in exactly the size it is imported. The Web Editor itself cannot resize pictures. This means that the picture is to be modified using another appropriate tool (e.g. Gimp or Adobe Photoshop). After the picture is resized, re-import it (change the source in the Repaint tab to the new picture).

 

 

If you want to visualise a Webpage at the 0,0 position of your browser in full screen mode without scrollbars, you'll need to add some extra html commands on your start-htm/html file of the Webproject in the body tag. The following code has been tested in the Microsoft Internet Explorer (IE) and Firefox 3.0.

 

 

 

Remark
Note that the Web Editor does not set these parameters automatically and these commands have to be added manually every time after generating the HTML page.

 

If there is a missing PPO in a Web-Editor project, a build from PG5 will fail with the error 31.

 

Symptom
During the build of the PG5 project a line as below will appear in the PG5 Project Manager's message window and the Build will fail.
Assembling: Web panel.wsc
Error 31: Web panel.wsc: Line 1915: Syntax error
1 errors, 0 warnings

 

Reason
The syntax error is generated by a PDP tag in the *.wsc file that doesn't contain a PCD ressource. The reason therefore most likely is found in the Web-Editor project: There could be a Painter with an empty PPO entry.

Solution
In order to solve this problem, open your Web-Editor Project and watch out for newly introuced painters. Systematically check the painters and verify that every pointer that modifies or depends on  a PPO does also have a valid entry!
The situation that causes the error looks like the image below:
§ix100273§

 

If the S-Web Editor detects a painter (graphical object in the view) that does have invalid dimension or position, a warning message will be shown. This message does also offer to correct the invalid values by setting default values...

 

Symptom
A message window as below does appear on opening a teq-view or when a pointer in the teq-view is selected:
§ix100247§
WARNING checked painter's sizes from teq view : MyView.teq is out or ranges. Do you want the PLCEditor to size it to painter default sizes?

 

In case a polygon or polyline is concerned, a second message window will pop up after the user has agreed to set the size to default values (often several times):
§ix100248§
CSpiderControlEditorDoc::CheckPainterSizeAndPositionInViewRanges() the painter with false sizes is a polygon or polyline so it will not be resized. Please make that correciton manually.

Reason
One common reason for this problem is that there exists a polygon or a polyline that do have a dimension of 0 or 1 pixels (so they are not visible). The S-Web Editor recognizes that there is an invalid object (painter) and therefore asks the user whether is should set the painter to its default values.
Since a polygon or a polyline doesn't have a "default" shape or size, the S-Web Editor isn't able to set the default size and informs the user with the second message.
Since the object(s) that cause the problem are most likely invisible, the user won't correct the dimension(s) of these painter(s) and therefore the S-Web Editor will complain about the same painter(s) again and again (which ends up in an endless clicking orgy for the user).

Solution
In order to get rid of this warnings, it is recommendet to delete the faulty painters. To do so, please follow the procedure below:

• Select all your painters in the view (place the mouse on the upper left part of the view and move the mouse with pressed left button to the lower right area of the view)

• Group all painters (right mouse click and select Group)

• Open the cross reference list (select the group and then right mouse click and select Cross Ref...)

• Look for polygons or polylines in the list of painters. If you find one, double click it and check the position and the dimensions. If the the values do not look reasonable (e.g. a dimension of 0 or 1 pixel), note down the coordinates of this painter.

• Close the Cross Reference and ungroup the selection

• Now find the invalid painters based on the coordinates you've written down. The coordinates of a selected painter are shown in the "Painter configurations" window on the left side. Once found, delete the faulty painter(s).

• Save your teq-view after this procedure. Repeat the procedure in case there are more faulty painters.

Hint: On small views you might be able to find the faulty painter by only selecting all painters and looking for single points (that could be a painter with no dimension).

 

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.

 

Timing problems when reading web pages from the PCD Web Server may cause the text "No Message: " to be shown instead of the values of the PPOs. The timing is depending on the communication type/speed between the WebConnect and the PCD (with the Web Server) and the settings for the Web Server itself.

 

This FAQ tries to point out in which case which setting is relevant and how to adjust these settings in order to resolve the problem of the "No Message" shown in the teq-views of a Web Editor project.

 

There are generally three different timing settings relevant for reading the values of PPOs of a Web Editor project:

• The priority of the Web Server task on the PCD (set in Web Builder)
• The response Timeout of the S-Bus Connection (set in WebConnect)
• The communication timeout (Request timeout) (set in the Web Builder) 
• The refresh period of the applet (set in Web Editor project)

The priority of the Web Server on the PCD

This setting is responsible for the CPU time the Web Server of the PCD. The higher the priority the more time the PCD CPU will have in order to resolve the PDP tags (in Web Editor called PPOs) and paste the value of the requested PCD medias into the RAM Disc (which then will be sent to the applet in order to show the vaue on the web browser). On the other hand, other task such as communication and executing of the user program will get less time and therefore will be slowed down a bit. If you are confronted with the "No Message: " shown in your web browser when viewing a teq-view, incerase the priority of the Web Server task on the PCD! If this doesn't help, you might set it back in order to increase the performance of the other tasks of the PCD. This setting is to be found in the Settings of the Web Builder. In this example the PCD will work on the "normal" user program during 21 ms and for 4 ms it will handle the web server task.

The S-Bus timing of the Web

In the WebConnect Setup page (where the connection to the PCD is configured, localhost/setup) you will find a "Response Timeout". Every time the WebConnect sends a telegram to a PCD, it will wait for an answer until the time specified here will be elapsed. This response timeout is mainly to be regarded in relation to a gateway station or modem communication. For modem connections a minimal timeout of 4 seconds is recommended.

The Communication timout (request timeout) of the Web-Builder

With the key combination +"saia" the normally  hidden advanced menu of the Web Builder can be entered. The communication timeout in this menu is relevant in gateway- and modem communications and should be higher than the response timeout mentioned above. As rule of thumb this timeout should be double as high as the response timeout of WebConnect. The reason for this timeout is the fact that WebConnect needs to request several S-Bus telegrams until one page will be completely transfered from the PCD to the PC. The communication timeout is the maximal time between two such requests. If this timeout elapses the web server will reset the transmission and the page will not be shown completely.

The refresh period of the Web Editor applet

This parameter will configure the applet to refresh the values of the PPOs. If this parameter is to be edited in the "applet params" in the window "Project Configurations..." (placed in the menu "Project"). If this value is too small, the applet will request the data (from WebConnect) as soon as it got the response form the request sent before. However, in order to reduce the communication load of the network (between WebConnect and PCD) it is recommended not to edit a too short period here.

In the "applet params" in the Window "Project Settings..." of a Web Editor project a checkbox named "Order per view" is placed. This FAQ describes the reason for this option and how it can be used.

 

The option "Order per view"
The option "Order per view" will cause the Web Editor to allocate the requested PPOs sorted by teq-file. The result will be that only the PPOs used for the actually shown page on the web browser will be requested from the Web Server of the PCD. This reduces the amount of exchanged data (by default all PPOs of the whole Web Editor project are requested as soon any page (*.teq) is requested). As result, timing problems may be solved this way (because less transfer allows a shorter timing).
§ix100326§

The influences on the memory needed on the PCD
The allocation of the PPOs per page (teq-view) will increase the memory amount needed on the RAM Disk of the Web server (also see FAQ 100299). The size of the additionally needed memory is depending on the number and type of the PPOs located in the teq-views. There is no easy calculation for this space required. Therefore it is recommended testing this option and this way figuring out whether the option "order per view" is suitable for resolving the problem with the message "No Message:".

Maximal count of teq-views
Further on, there is a restriction of the maximal amount of page-specific PPO ranges on the RAM Disk. Also this maximal amount is depending on the space available on the RAM Disc.

 

• For a PCD2.M170, a PCD2.M480 or a PCD3.Mxxxx the maximal count of teq-views is 12

• For a PCS1 this option may not be used (becuase of too little memory available)

If more teq-views than listed above are present in your Web Editor project, the option "order per view" must not be used!
In case you are concerned by the problem of the "No Message" shown instead of the value of the PPOs in your web browser, try to increase the RAM Disk size (see FAQ 100299) and, if this doesn't help, increase the applet refresh period  (see FAQ 100300).

Minimal firmware versions
Note that not all FW do support this feature. Please refer to FAQ 100299 that contains a list of the minimal FW version required for this option. The use of the "order per view" functionality on a FW that doesn't support this fuction may crash the PCD!

Important Note:
If any of the "Project Settings" parameters (the "Order per view" is one of them) was modified, the "generate htlm" function must be called afterwards!

 

As big as possible...

In relation to the use of the Web Editor, it is important to choose the highest possible RAM Disk size of the PCD Web Server. A too small RAM Disk size may lead to the message "No Message: " instead of the value to be shown by the Web Editor applet.

 

What is the purpose of the RAM Disk?
A browser (or the java-applet running in the browser) is requesting PCD variables (PPO, e.g.registers, timers, flags etc.) using the CGI-functions "OrderVal.exe" and "ReadFile.exe". The requested items or files are stored in the ramdisk. Web project created with the Web-Editor are applying these functions.
§ix100327§

 

Why should the RAM Disk size be set to the maximal size?
The size of the files stored in the ramdisk is depending on the amount of the PCD variables. If the ramdisk of the PCD Web Server is too small for holding all values of the PPOs used in a Web Server project, the result will be that not all PPO values will be sent on a request by the Web Editor applet. This will lead to the "No Message: [Unit of the PPO]" shown in the Web Browser. In this case the entry "WEB RAM TOO SMALL" will be written into the history of the PCD.
If too many PPOs are requested, systems equipped with older firmware versions than indicated in the table below even can crash!
The configured size of the ramdisk won't affect the performance of the PCD (or the memory available) in any way.

 

Firmware requirement
The maximal ramdisk size is depending on the PCD type. The maximal amount of PPOs that can be stored in the ramdisk is depending on the firmware (FW; Operating System of the PCD). Please refer to the following table that indicates the minimum FW version for the concerned PCD/PCS type.
Note that the amount of PPOs that can be stored on ramdisk (indicated in the last two columns) is only valid if there is only one file in the ramdisk (this is the case if the option "Order per view" is not checked!).

 

Where is the size of the ramdisk size configured?
The RAM Disc size is to be specified in the Web Builder that is used to generate the file downloaded to the PCD/PCS. In PG5 version up to SP1.3.110 the size of 4 kBytes is set by default (the Web Builder distributed together with later versions of PG5 will have a bigger default value) .
For accessing the settings for the RAM Disk size,

• open the Web Builder

• push the button "Settings..."

• while the window Web-Server Settings is open, press the key <control> and type in "saia" (keep the Control-key pressed). </control>

Now you should see additional settings, among them also the parameter "RAM Disk size [kBytes]". In this field, enter the value listed in the table above for your CPU.

Note
Don't edit a value bigger than listed in the table above; otherwise the FW will allocate the minimum value to the RAM Disk size (2 kByte).
After having changed this parameter, press the "OK"-button, generate your Web Server project and in PG5 Project manager, execute a "rebuild all" and then downlaod your project again.

If this doesn't fix the "No Message: ", please also refer to FAQs listed below:

 

On web pages generated by the Web Editor containing many PPOs it may occur that the PPO values aren't shown but "No Message: ge" (instead of "ge" the unit unit of the PPO may be shown as well) is displayed. Read this FAQ to learn more about the reasons for this behaviour.

 

This problem is caused by the fact that the Web Server of the PCD/PCS doesn't respond to the request sent by the Web Editor applet (within the defined time). One or both of the reasons listed below may cause this problem:

 

• The RAM Disk size of the PCD Web Server is too small
• The read period of the applet is too short

To resolve the problem it is recommended to try the following steps:

• Make sure the length of the web-project name (including the point and extention) does not exceed 24 characters.
  Example: The name "Thisismyprojectname12.prj" is too long.
• Increase the RAM Disk size (FAQ 100299).
• If possible, use the option "Order per view" (FAQ 100300).
• Set a higher priority for the Web Server of the PCD (100301).
• Uncheck the "Order per view" but leave the higher priority for the Web Server.
• If none of those changes resolve the problem, contact your local SBC representative.
  In order to find the communication problems, the support team will need a Tracewin record that contains the telegrams sent/received by the WebConnect. Please record such a file (FAQ 100268 contains further information) before you contact the support.

The single steps are described in the related FAQs (please refer to the links at the end of this FAQ).

Please note that in any way it is strongly recommended to use the latest firmware (FW) for your PCD/PCS. Please refer to the table in FAQ 100299 for the minimal and the optimized FW version for your PCD/PCS system.

 

Strange symbol names similar to "aaaaaaabc" in a Web Editor project are most likely the result of *.teq file confusion.

 

 

 

The reason could be *.teq file confusion. If the *.teq files from the "web" folder of the PG5 project are copied into the "html" folder by the user, the Web Editor project won't work correctly. This FAQ entry explains why...

 

As mentioned the identically named *.teq files of the html and the web folder aren't identical. The difference is to be explained by the replacement of symbol names (present in the version of the "web" folder) by "short symbol names" that are present in the *.teq files of the "html" folder. This substitution is done in order to reduce the name lenght and therefore avoiding too long symbol names in the downloaded project.

 

The substitution of the names is proceeded when saving the files into the Web Editor. At this moment the files of the folder "web" are copied into "html" and additionally the names of the *.teq files are replaced while this copy process.

Symptoms indicating *.teq file confusion:

• If you copy the *.teq files from the "web" directly into "html", you'll be able to build and download the file. The problem will be that the symbols won't be displayed correctly and you won't be able to modify any PCD medias since the link between the "short symbol names" and the PCD ressources is broken (due to missing short symbol names).
  
• The "short name" of the symbols looks similar to "aaaaaabc". So in case you recognise such symbol names while working with the Web Editor, you most likely accidentaly copied a *.teq file from the "html" folder into the "web" folder.

How to avoid *.teq file confusion?

Just always start the Web Editor form PG5 and always store your files by using the "Save all" button on the Toolbar of the Web Editor.

 

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:

*.html file:	If this (main) page is accessed, IE won't be able to display it and will show a message like "This page can not be displayed".
*.tcr, and *.itq	Will cause a "no response" of Web Connect and block the communicaiton interface of the PCD!
*.teq	Not possible to give names containing spaces.

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.

 

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.

Yes, it’s possible to re-use existing PG5 projects which were created with an older version of PG5 on PG5 2.3.192

 

The attached document describes changes on Fupla or Web-Editor8 projects which could be necessary if an existing PG5 project should be used on PG5 2.3.192

 

 

The handling of the @CO_ and @COFF_ expressions on the Web-Editior8 has been changed on PG5 2.3.192.

More information can be found on the attached document.

 

 

If the Fupla project contains ‘Alarm advanced’ FBoxes then since PG5 2.3.192 it’s mandatory to place a ‘Plant Code’ FBox on the Fupla project.

The ‘plant code’ FBox must be placed before the first ‘Alarm advanced’ FBox.

On older PG5 version the ‘Plant Code’ FBox was not mandatory.

 

More information can be found on the attached document.

 

On the Web-Edtior8 of PG5 2.3.192 it’s no more allowed to access PCD variables with an expression PCD_variable+n.

Instead the Expression PCD_variable.n needs to be used.

More information can be found on the attached document.

  

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.

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.

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

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

A correct properties view looks like this:

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

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

On a CE Web panel, it could be usefull to start an application, in order to generate a sound for example.

 

 

 

It is possible to use a predifined internal variable that allows WebEditor to start a Process.

As example, you can play a song using mediaplayer.

 

 

 

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!

The lenght of the symbolic name of the PCD text variable which is used in the 'dir' field of the F-Box 'HDLog File 3.0' and does point to the location of stored csv file is limited to 39 characters. If the symbolic name of this variable is to long, then the trends curbs are not displayed and the error message is shown.

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’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@

 

The MB panel can't access the web page stored on the PCD:

'start.htm not found' or similar is displayed but the browser on the PC can display the web page.

A warning message on the PC browser is displayed when the MB panel try to access the server.

 

Possible Error message given by the java machine:

In Web Editor 8 it's easy to share with other programmers your own template librairies with well structured and good organized subfolders.

 

Arrange your proprietary libraries
Save and arrange your proprietary macros in your libraries window of Web Editor 8.
Do create subfolders to increase lucidity.


Export your macros
Select all the macros you want to export by using the 'CTRL' key. Right-mouse-click on one of the macros and select the 'Export x elements...' functionality. You can export all the macros into one single *.zip file that you can exchange with other programmers or save on a server to get other programmers syncronised with your library updates.

Import the macros
If you want to import macros you simply right-mouse-click and choose the 'Import...' functionality in the libraries window of Web Editor 8.

The installation path of each library is saved in the *.xtml file and used for the export and import purpose.

 

Due of an error in the alarming templates included in the Web-Edtior8 it’s not possible to select a single alarm in the online and offline alarming template and therefore to acknowledge or delete alarms from the list.

The error was fixed in the version 8.2.0.917 of the Web-Edtior8 (included in the SP1 for PG5 2.1.300)

 

Symptom:
On the web-browser or on the microbrower display it's not possible to select a single line in the web alarming template.

Solution:
Do install a newer version of the Web-Editor8 (at least the version 8.2.0.917)

Open the web-project in the Web-Editor8, delete the alarming template from the web page, drag and drop the alarming template from the library in to the web-page and insert the Alarming PPO name in to the template.
Compile and load the web-page in to the PCD.

 

The web-editor 8 does have a new user access control which does allow defining up to 100 users.

For each user it’s possible to define an own password, start page and language.

 

It’s necessary that on the user defintion window, on the language row there have to be a language seleted for each user.

If the language is not selected on this row, then the login on the web page doesn’t work.

 

If there is no language selected on the user definition then the login on the web page doesn't work


To be able to select a language you have to define the language(s) on the translations window of the Web-Editor 8 by clicking on the ‘Configure languages’ button and adding the languages which you want.



After this do save and close the translation window and the user window and do open again the user window and there to select for each user a language.


After this do compile and load the project in to the PCD and the login should work correctly.

 

If for example on the S-Web editor a register value is defined with the format DEC.1 with the

limit min. value 10.0 and

limit max value 50.0.

If now this page is displayed in the browser and you want to modifiy the value with the value 20.0,

then the error message 'Value out of bounds 10.0..50.0' is displayed and it's not possible to modify the value.

 

Reason:

On the S-Web Editor it's NOT possible to define limit values with . (Dot) values (DEC.1, DEC.2.....)!

Solution:

Modify the limit value as

min 100 (for 10.0) and

max 500 (for 50.0)

If you want to enter the value 20.1 on the browser do enter the value 20.1.

 

On WebEditor 8 with version 8.0.19.434 or older it possible to destroy the web project in that way, that’s no more possible to open the project.

 

During the opening of the WebEditor 8 project the following error message is displayed:
‘Object reference not set to an instance of an project'
‘Der Objektverweis wurde nicht auf eine Objektinstanz festgelegt'

Reason of the error:
If a WebEditor5 project is imported and if on this project there where some function's then this function's are displayed in the function editor of WebEditor8 as function "write source to.."
[means the function which are selectable in the function editor as ‘advanced' functions].

If now this function is set to the scope "project" then it's no more possible to re-open the web-editor project a second time and the WebEditor8 project is destroyed and it's no more possible to re-use the project.

The same behavior does occur if a function on the WebEdtior8 does include an ‘advanced' function and if this function is set to the scope "project".

Possible solutions:
- Use a WebEditor8 version > 8.0.19.434
- Do not set the function scope to ‘project' if the function does include ‘advanced' functions
- if you need to set the function scope to ‘project' the use the ‘standard' functions instead 
  to use the ‘advanced' functions on the WebEdtior8.

 

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

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

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

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

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

MB Panel version	Minimal firmware	Remarks
PCD7.D4xxD (SVGA)	1.18.12	-
PCD7.D4xxV (VGA)	1.18.28	first internal firmware version: 1.18.12
PCD7.D4xx_ (QVGA)	not supported

Screenshot for example project

Restriction:

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

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

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

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

 

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

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

 

 

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

‘An error occurred during the connection to the sever’

A modification on the configuration file should fix the issue.

Error description:

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

Solution:

To solve the issue perform the following steps.

Close the PG5 update manager.

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

Search at the end of the file the string:

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

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

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

Save the file and restart the PG5 Update manager.

 

If the error persists then please check:

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

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

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

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

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

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

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

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

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

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

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

We regret any inconvenience caused.

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

Update on 08.04.2020:

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

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

 

 

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

Detail information:

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

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

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

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

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

 

Error description:

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

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

Solution:

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

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

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

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

 

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

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

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

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

Introduction

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

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

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

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

---

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

---

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

Fupla:

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

  
  

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

  
  

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

  
  

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

 

Web-Editor8:

• Generation of HTML 5 compatible web pages

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

 

Improvements:

Device Configurator:

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

 

FBox libraries

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

  
  

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

  
  

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

  
  

DDC Suite

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

And other improvements and bug fixes

---

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

Windows Start menu

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

Device configurator:

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

Fupla:

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

Web templates and Web Editor 8:

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

Wiring Check Tool:

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

---

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

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

And other improvements and bug fixes

---

New features of PG5 2.1.310

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

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

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

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

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

And other corrections.

---

New features of PG5 2.1.300

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

And some other improvements and bug fixes

---

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

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

And some other improvements and bug fixes

---

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

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

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

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

---

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

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

 

---

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

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

 

---

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

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

---

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

• Support of the PCD1.M2160

---

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

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

---

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

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

 

---

New features of PG5 2.0.110 (first official release)

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

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

The new features in detail

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

 

---

Restrictions of PG5 2.0 and PG5 2.1

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

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

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

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

The error doesn’t occur if:

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Symptoms

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

 

Reason

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

 

Solution

Is described in FAQ 101994

In PG5 2.2.220 the Error is fixed

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

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

A correct properties view looks like this:

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

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

Line length equal to 0 will be deleted from fupla

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

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

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

During programming, everything would work fine.

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

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

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

Here is the view after compiling and reopening the fupla

 

 

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

 

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

 

Please download the patch from here

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

default path is:

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

 

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

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

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

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

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

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

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

 

 

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

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

There is no problem if:

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

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

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

The FBox library is attached to this FAQ

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

 

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

PG5 Version

Win '95

Win '98

Win ME

Win NT

Win 2k

Win XP

Vista

Server 2008

Windows 7

Windows 8

Windows 8.1

Windows 10

Windows 11

1.0.xxx

B or higher

Second Edition

Yes

SP5 or higher

Prof. SP4

No

No

No

No

No

No

No

No

1.1.xxx

B or higher

Second Edition

Yes

SP5 or higher

Prof. SP4

No

No

No

No

No

No

No

No

1.2.xxx

B or higher

Second Edition

Yes

SP5 or higher

Prof. SP4

Yes

No

No

No

No

No

No

No

1.3.xxx

B or higher

Second Edition

Yes

SP5 or higher

Prof. SP4

Yes

No

No

No

No

No

No

No

1.4.300

No

No

No

No

Prof. SP4

Yes

Yes*

Yes*

Yes*, ***

Yes*, ***

No

No

No

2.0.150

No

No

No

No

No

Yes (SP2,SP3)

Yes **

Yes **

Yes **

Yes **

Yes **

No

No

2.1.xxx

No

No

No

No

No

Yes (SP2,SP3)

No

No

Yes **

Yes **

Yes **

No

No

2.1.430

No

No

No

No

No

No

No

No

Yes **

Yes **

Yes **

No

No

2.2.100

No

No

No

No

No

No

No

No

Yes (SP1)

Yes

Yes

No

No

2.3.1xx

No

No

No

No

No

No

No

No

Yes (SP1)

No

No

Yes

No

2.3.195

No

No

No

No

No

No

No

No

Yes (SP1)

No

No

Yes

Yes

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

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

Detail information:

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

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

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

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

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

 

Error description:

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

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

Solution:

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

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

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

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

 

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

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

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

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

Introduction

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

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

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

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

---

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

---

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

Fupla:

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

  
  

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

  
  

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

  
  

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

 

Web-Editor8:

• Generation of HTML 5 compatible web pages

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

 

Improvements:

Device Configurator:

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

 

FBox libraries

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

  
  

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

  
  

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

  
  

DDC Suite

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

And other improvements and bug fixes

---

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

Windows Start menu

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

Device configurator:

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

Fupla:

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

Web templates and Web Editor 8:

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

Wiring Check Tool:

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

---

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

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

And other improvements and bug fixes

---

New features of PG5 2.1.310

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

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

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

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

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

And other corrections.

---

New features of PG5 2.1.300

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

And some other improvements and bug fixes

---

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

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

And some other improvements and bug fixes

---

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

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

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

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

---

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

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

 

---

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

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

 

---

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

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

---

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

• Support of the PCD1.M2160

---

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

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

---

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

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

 

---

New features of PG5 2.0.110 (first official release)

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

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

The new features in detail

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

 

---

Restrictions of PG5 2.0 and PG5 2.1

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

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

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

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

The error doesn’t occur if:

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Symptoms

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

 

Reason

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

 

Solution

Is described in FAQ 101994

In PG5 2.2.220 the Error is fixed

Line length equal to 0 will be deleted from fupla

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

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

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

During programming, everything would work fine.

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

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

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

Here is the view after compiling and reopening the fupla

 

 

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

 

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

 

Please download the patch from here

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

default path is:

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

 

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

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

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

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

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

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

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

 

 

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

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

There is no problem if:

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

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

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

The FBox library is attached to this FAQ

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