Apparently the anit virus software "Avira Premium Security Suite" can lead to the fact that Fupla can no longer store a file (and instead the error "Error 46: Disk full" is displayed).

Symptom
It is no longer possible to store a Fupla file and "Error 46: Disk full" is displayed (despite the fact that there is some space left on the disk).

Reason
This problem could be provoked by the current version of the anti-virus software "Avira Premium Security Suite".

Solution
Due to the fact that disabling the software does not solve the issue (the security suite needs to be uninstalled in order to be able to store the Fupla files again), it is recommended to configure Avira to allow the execution of the following PG5 tools. Therefore please configure the application filter from the security suite accordingly (in the Avira Guard menu "Expert mode" --> ProAktiv --> Application filter). Please add the follwing applications: 

• SPM.exe (Project Manager)
• SFup32.exe (Fupla Editor)
• SGraph32.exe (Graftec Editor)

Remark
This FAQ is a translation from the original version in German, FAQ 101630.

In some cases this error has been reported after the installation of the Patch 15 for PG5 1.4.300.

Symptom
After the installation of patch 15 for PG5 1.4 (with subsequent change of the language of the FBoxes) the following error messages are shown when opening Fupla:
S-FUP: Error 161: New macro name '_COMSTN2' is not part of library.
S-FUP: Error 161: New macro name '_COMTXB3' is not part of library.
S-FUP: Error 161: New macro name '_COMRXB3' is not part of library.
S-FUP: Error 161: New macro name '_COMRXBM3' is not part of library.
S-FUP: Error 161: New macro name '_COMTXB3Q' is not part of library.


Reason
This error is caused by the fact that some files (with the extension *.idx) located in language specific folders in the library path of PG5 have not been overwritten by the patch 15. In case the error is indicating "_COM..." macros, the files belong to the FBox family "S-Bus Communication" (SFupCom). A possible reason for this situation could be that the files present on the PC have been write protected, hidden or that the creation date of the files has been newer than the one contained in the patch.

Solution
In order to solve this issue, please install the S-Bus Communication library 2.6.150 or later (this will install the library again including all the files in the language dependant sub folders).
The S-Bus communication library can be downloaded from the support page in the section "Software"-->"PG5" --> "PG5 1.4" --> "FBox libraries":

If a Fupla page is "disabled" (in its properties under "Advanced") it still gets compiled but the code on the PCD will be overjumped.

Although a user program page in Fupla editor is disabled it can generate errors and warnings. This is due to the fact that all pages get compiled even if disabled.
During compilation the disabled part gets a preceding jump instruction. Once loaded into the PCD this instruction directly jumps to the end of the disabled code part. So albeit the disabled code is present in in the final user program it will never be executed.

It is possible to use the interrupt inputs (Int0 = i 8100; Int1 = i 8101) of a PCD2.M5xxx or PCD3.Mxxxx as normal input without using the corresponding interrupt XOB.

Symptom
When using I8100 or I8101 in Fupla they are high ("1") even no tension is applied on them; the visualized states of these inputs in a fupla page don't correspond to the real state on the contact Int0 and Int1.

Reason
The reason for this situation is that Fupla does not correctly show the states.

Solutions

• Work-around
  In Fupla page you can add an "Binary Move" Fbox and use the output of this one as state of input 8100 (8101) as shown below  
  
• In PG5 2.0 this problem is corrected in PG5 2.0 SP1 (PG5 2.0.150)
• For PG5 1.4 no correction is foreseen; the work-around explained above can be used in order to visualize the states of the I/O.
  
  

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

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

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

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

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

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

If the last patch for the analogue library 2.6.100 was installed, the "Info" button will not show the help of the FBox anymore.

Symptom
If the last patch for the analogue library 2.6.100 was installed (downloaded from the support site between May 4 and August 4 2009), the "Info" button will not show the help of the FBox anymore.

Problem
There is an error in the help file of the analogue library 2.6.100.

Solution
Please download and install the FBox library again. The library version 2.6.100 available on the support site since August 4 2009 is corrected and installs the help file, too. 

There is no FBox that allows to calculate the power of a number.

This is possible to build a combination of Fbox to be able to calculate easily the power of a number.

With the following relations:

a=x^y
ln(a)=ln(x^y)
ln(a)=y*ln(x)

and

a=exp(y*ln(x))


The following example is the operation 3^4.

The Saia PCD® instruction set does support the natural logarithm Ln (hyperbolic, base e, floating point instruction FLN). Logarithms to any other base like 10 (Log10) can be calculated with the method described below.

The Ln of x can be divided by the Ln of the desired base: Log n (x) = Ln(x) / Ln(n)

Example in case the logarithm with the base 10 is needed:

Log10(x) = Ln(x) / Ln(10)

The value of Ln(10) (=2.302585093) can be stored in a constant or variable so it does not need to be recalculated each time a Log10 is required.

The FBox from the family "Communication": "Transmit Integer" offers the possibility to choose Clock as Destination. How does this work correctly?

The station address parameters of the FBox "Transmit Integer" are to be entered as usual.
As "Destination" choose Clock. The "Destiation Address" Field has no influence in this case; any address will work.

Two input registers are needed. The first one contains HMS and the second one contains the Day. Use the FBox "Read Time" from the family "Time related" to read the clock from the PCD. The registers with the contend HMS and Day can then be transmitted to the second PCD. In this case the format is correct.

It will as well work if the "Read time" FBox is directly connected to the Inputs of the Send FBox.

 

Remarks

• In case the clock is to be synchronized on a whole network, the usage of the FBox "Broadcast Clock" is recommended.
• It is also possible to send the time from a SCADA system to the PCD. In this case, the format of the clock FBox inputs can be read in the online help of the FBox "Read Time". 

In Fupla the situation can occur that symbols (e.g. generated by the "DDC Suite" FBoxes by using the functionality "Add predefined symbols") disappear and are blocked for new usage.

Symptom
Symbols (e.g. generated by the "DDC Suite" FBoxes by using the functionality "Add predefined symbols") can disappear and are blocked for new usage.

Reason
The reason for this phenomenon is a bug in the Fupla-Editor.

Solution
The version 1.4.308 of the SFup32.exe resolves this problem. This version is available in the "Patch 7" for PG5 1.4.300 which can be downloaded from the support site (section "Product information" --> "Software" --> "PG5").

The "Advanced Text Mail Initialisation" FBox indicates an error, what can be the reason?

Note that e-mail server can react in different ways. Some servers will accept non valid e-mail addresses as sender.

The "Send SMS Indirect" F-Box version 2.5.300 does generate the following warning on PG5, and the "$R, $L, @L…." syntax in the texts which should be sent as a SMS are not interpreted correctly:

Symptom
The "Send SMS Indirect" FBox version 2.5.300 generates the following warning during a build:

Warning in the message window of during a build PG5:
Warning 6: Send SMS. text convertion not possible with indirect text number.

And the "$R, $L, @L…." syntax in the texts which should be sent as a SMS are not interpreted correctly.

Solution

The bug is fixed on the version 2.5.302 of the Modem FBox Library. This library can be downloaded from the support site.

According to the info message the ICC activity time 00:00 means unlimited. If this time is configured it is not possible to go online anymore

Problem
According to the info message an ICC activity time of 00:00 means unlimited. However, if this is chosen, it is not possible to go online anymore. After the connect, the line is disconnected immediately.

Reason
Do to security reasons an unlimited activity time is not supported. If the line is never disconnected, it can lead to high costs and the PCD can not be connected by another station any more.
The info message is incorrect and will be corrected in future versions of PG5

Solution
Do not choose ICC activity time 00:00. The maximum value to enter is 23:59.

When building a PG5 project created with PG5 version older than PG5 1.4.200, the build could fail because of undefined symbols.

Symptom
When an older project created with a previous PG5 version is build within PG5 1.4.200, a lot of error messages are generated telling to replace EIB Fboxes or symbol not defined.
The generated error messages could look like these:


Reason
This problem occurs because of a problem in the EIB library version 1.5.160. An old version of the EIB RCV Switch FBox does use a symbol that is not available any more.

Solution
Please install the attached version of the EIB library or a newer one (>2.5 1669).

After changing the language in the FBox Selector of Fupla, the message "Error 160: Replaced macro _ENERGH104S is part of family definition" appears.

Symptom
After having changed the language of the FBoxes in the FBox Selector of PG5 1.4.200 Fupla, the following message appears: "Error 160: Replaced macro _ENERGH104S is part of a family definition.


Reason
This problem is related to the language versions in which the library SFupBase has been distributed (not all files have correctly been updated).

Solution
Install the latest SFubBase library (SFupBase25143.exe) which contains all the languages (it size is bigger than 1 MB, not like for example $25141). This library can be found in the PG5 section under "Patches for PG5 1.4.200"

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.

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

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

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

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

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

Install the corrected Alarming library 103001in attachment!

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. 

This FAQ explains the possibilities in case a PG5 project is not available but still an existing application needs to be modified.

Disassembling in general
PG5 includes a tool for disassembling code running on a PCD. This tool (the "Disassembler") allows the conversion of uploaded (or just compiled) code that is in "binary" form to its representation in Instruction List (IL).
The resulting code is identical to the code executed by the PCD but it is not equal to the source files from which the project was built. The main differences are

• The missing symbol names; All symbols are addressed statically in the dissected code (while symols in the symbol manager can have "dynamic" addresses distributed at build time)
• All comments are missing in the disassembled code (because they aren't downloaded to the PCD)
• Code can only be disassembled to IL. It is not possible disassembling code back to Fupla or to a HMI file!
• Jump labels are missing (the jumps are directly addressed) in the dissected code
• Assembler directives (like $IF etc.) aren't present in the dissected code (they were evaluated at build time)

Can I reverse-engineer a disassemled project?
Depending on the tools used for the creation of the program and on the complexity of the program this task quickly becomes practically impossible. Disassembling and reverse-engineering e.g. a Fupla program is nearly impossible (well, if you spend hundreds of hours and you understand the tasks of your application very well, you maybe could manage reverse-ingeneering a Fupla project).
The problem is that an FBox can create completely different code which is built in dependence of the target system, options set in the adjust window etc. Further on there can be differences between each version of one and the same FBox (because new features are implemented and bug fixes are applied).

In 99 % of all cases it is far more effective re-engineering an existing project in case the source files are not available.

Can I modify an existing project (e.g. a setpoint)?
Modifying e.g. a setpoint means also identifying and reverse-engineering the relevant part of the code. If only a setpoint needs to be modifyed, it is possible searching for all code parts that load this value to a register. Once all these parts are found the relevant part of the code needs to be identified and modified. Even if this modification is successful still the whole project is only present in "pure" IL and further modifications will require at least as much work (if it will be possible at all). Modifications in this way are only recommended for advanced experts.
In case not only the setpoint but the behaviour of one part of a program needs to be modified the complexity most likely is already too high (at least if the program was written in Fupla or similar).

Due to a problem in PG5 (Fupla and Watchwindow) the values read by certain analogue modules can occasionally be corrupted while beeing online with the PCD.

Symptom
While beeing online with the PCD, input values of analogue input modules jump to wrong values. The problem occurs occasionally and the value shown while the error case is not predictable (but it often is always the same value). The problem occurs when beeing online with Fupla and/or the PG5 Watch Window.
When beeing online with Fupla only, the problem can disappear when viewing another Fupla page.
All analogue modules with the exception of intelligent analogue modules (W745, W720, W3x5, W525 and W6x5) can be concerned by this problem.

Reason
The reason for this problem is a problem in the "Synchronous Data View" of Fupla and the WatchWindow. When using the "Synchronous Data View" and viewing a digital input or output, PG5 automatically does read the following 31 I/Os, too. In case the addresses of an analogue module are read by this automatism, a value corruption can be the result.
Affected PG5 1.4 versions (older versions than PG5 1.4 aren't affected because the "Synchroneous Mode" was not implemented):

• PG5 1.4.100
• PG5 1.4.110
• PG5 1.4.130
• PG5 1.4.200 

PG5 1.4.120 does contain a correction that avoids this problem.

Solution
This problem can be fixed by installing PG5 SP 1.4.300. The latest version of the PG5 can be found on the support site (www.sbc-support.ch) in the section "Product information" --> "Software" --> "PG5"

Some F-Boxes in PG5 1.4 are generating symbols which are maybe also used in the project.

Symptom
On build the following error (or similar) appears:
Error 395: sfupanl5.srx: Local and global symbols have same name but different type/value: RTEMP1

Reason
The Fupla analogue library is generating symbos which are often used in projects for normal symbol names:
- cTemp
- fData (Array of 8)
- fError
- fTemp (Array of 8)
- fTout
- kFlashTime
- kTimeout
- rActch
- rBase
- rHighByte
- rLowByte
- rTemp (Array of 5)
- rTout

If an analogue F-Box is placed p.ex. PCD2.W34, PCD2.W3x5, PCD2.W6x5 etc. some of these symbols are used by the F-Box. Other symbols in the project with the same names will cause a conflict. The error message above or similar will appear on build and the build will fail.

Solution
A correction in the PG5 1.4 library is necessary. Therefore please update your PG5 (to version 1.4.110 or newer).
In case it isn't possible for you to update your PG5 you can change the symbol names mentioned above (which are used in your program) in order to avoid this conflict.

PG5 V1.4.100 first edition has a error in the analog module library (library version v2.5.100):

All analog FBoxes generate an error on build of the project.

Symptom
A build of the project fails with the error message
Error 165: TestFupla.fbd: Line 71: PCD2.W340 Old Fbox NOT anymore supported., in Block: BL 425E2C0E, Page: 1, FBox: PCD2.W34

Reason
This error is caused by a bug in the FBox library for the analogue modules. The version affected is V2.5.100 (distributed with PG5 1.4.100).

Solution
In order to fix this problem, please download the patch available in the PG5 section of the support site. This patch will install a fixed version of the FBox library (V2.5.101) for the analog library.

Note
If you have downloaded PG5 1.4.100 from the support site after February  21th 2006, your installation is not affected by this bug.

Analog input Fboxes with individual callibration have the following parameters; Mode, range and offset to be adjusted. The following formula helps to adjust those paramters

In order to use this formula the paramter mode has to be kept to default value: R-0

Range = (Ymax - Ymin) . Imax                        Y = Fbox output value 
                  (Imax - Imin)                                I   = Analog carte input value (mA, mV)

Offset = Ymax - Range               

Example: the sensor gives 4...20 mA and we want to display a value from 0...500 m3 using a PCD4.W300 card!

Range = (500- 0) . 20 mA    =      625            
                (20mA -4 mA)                                

Offset = 500 - 625 = - 125              

In order to achieve a high and constant data throughput with S-Bus, the following guidelines can be helpful for the programmer of S-Bus communication.

S-Bus in Fupla

• Fupla handles all Transmit- and Receive FBoxes equally. By default, all requests are handled cyclically and are serialized automatically.
  This means that the value of an alarm flag is sent as often as the value of an outside temperature (that generally doesn't change within minutes).
   
• S-Bus communication is always commanded by the user program. The performance can be influenced by the cycle time of the user program.
  Given the cycle time of the user program is 300 ms, in maximum one telegram will be sent every 300 ms, too.
   
• Every FBox creates one telegram per communication cycle.
   
• A telegram can hold up to 128 bytes (array of 32 registers or 128 flags).
  The transmission of a telegram that contains 128 bytes doesn't take much longer than the transmission of a telegram with 1 bit data (the times are depending on the baud rate).
  On the other hand, sending two telegrams take double the time than sending one telegram.
  This results in the fact that the performance is rather depending on the amount of  telegrams than on the bytes transmitted.

Conclusions

• Send multiple medias with one FBox whenever possible.
  Use the FBoxes "Transmit- respectively Recive quick".
   
• In order to increase the communication performance, it is recommended sending slowly changing values in intervals.
  
  One possible solution for this could be two or more send- or receive FBoxes that are enabled alternatively (see fupla page above). Make sure the enable time of each of these FBoxes is at least equal to the communication cycle. 
   
• Transmit In- and Outputs as flags (in an array). Or, even better, map them into registers.
  This way telegrams (and therefore communication time) can be spared.
   
• Use the "S-Bus station (-IP)" FBox in order to avoid massively higher communication cycle times in case of a slavestation failure!
  This FBox does not constantly send telegrams to a station known as missing but only in intervals (after a short- or long reconnect time). Also refer to FAQ 100496 in case PCD7.Lxxx modules are used.
   
• For receiving slowly changing values consider using the FBox "Receive Integer Multiple" (only PG5 1.4 and higher)

Depending on the project not all or only few of these actions can/should be taken.

In some cases the introduction of "Application Symbols" (A-symbol, such as A.HVC.FBoxName.Error) may be required for a created FBox. These symbols will be available (but not modifiable) in the "System" tab of the Symbol Editor.

How can an A-symbol be used?
The A-symbols are special global symbols and similar to the System Symbols (S-symbols). The can be used in all program files belonging to the according CPU of the project. A part of the symbol (a group name after the registered prefix) is defined by the Fupla programmer. This is done by defining an FBox name that will be used to build the A-symbol specific to the FBox.
Since the symbols are written and used by the according FBox, they are not ment to be modified by the user program!
§ix100344§

How can an A-symbol be created?
It can only be created if the FBox is designed to do it (e.g. most of the Heavac FBoxes).
If this is the case, it is sufficient to give the FBox a name (right mouse click on the FBox and select "FBox properties..."). After the next Build, the according A-symbols will be available.

According to the help the format of the clock holiday is MM:DD (Month day). Otherwise it is not possible to enter p.e 12.30

Problem
When entering a date like 12.30 the following error message appears:

 §ix100290§

Reason
The help for the F-Box is wrong. In fact the format is DD.MM (Day Month)

Solution
Enter the date in the format DD.MM and it will work (p.e 30.12 for 12. December).

Each new F-Box has the name Module. That is the reason for the multi-defined symbols.

Problem
If more than one F-Box PCD2.W745 is placed in a project the following errors will appear:

Reason
The reason is that each new F-Box has the name Module. Therefore it creates Multi-defined symboles.
§ix100277§

Solution
Each F-Box has to have a different name. Rename the second F-Box p.e in Module1 etc. In future versions of PG5 this F-Box will not have a default name since it is not necessary.

It might occur that a build of a Fupla file generates "Operand errors" and the build fails. In this case a "Clean files" most likely will help.

Symptom
During a project build while the linking process an error message as listed below appears:
Operand errors:
Error 320: Fupla.fbd: Line 4: Invalid FB parameter: CFB _HEAVAC._FB._REG1: Param 2. See module heavac5.srx: Line 919
Error 320: Fupla.fbd: Line 5: Invalid FB parameter: CFB _HEAVAC._FB._REG1: Param 3. See module heavac5.srx: Line 927
Error 320: Fupla.fbd: Line 4: Invalid FB parameter: CFB _HEAVAC._FB._REG1: Param 2. See module heavac5.srx: Line 919
Error 320: Fupla.fbd: Line 5: Invalid FB parameter: CFB _HEAVAC._FB._REG1: Param 3. See module heavac5.srx: Line 927
This problem still remains after a "Rebuild All". 

Reason
This error message is generated because an internal, project related symbol table is corrupted. As long as PG5 recognizes that this file is present, it won't be re-generated (and therefore will cause the same error again and again).

Solution
In order to resolve this problem, a "Clean Files" of the "Symbol information files" can be executed. The "Clean Files"-window is opened from the menu "CPU", "Clean Files...".

Additional note
The "Clean Files" for the symbol information files will re-allocate all dynamically distributed symbols!

spare registers

When using PG5 1.3.120 and having installed the old library "Heavac Dialog", the "S-FUP Error 161: New macro name '_HEAINI6' is not part of library" could appear when opening the Fupla Editor.

Symptom
When opening a Fupla file, the following message is shown: "S-FUP: Error 161: New macro name '_HEAINI6' is not part of library."
§ix100212§
most likely, this message is followed with the indication that Fupla couldn't open the desired file:
§ix100213§

Reason
This error is caused by a bug in the library Heavac Dialog that is installed by executing the library Installer "HeaDl0D23140SP.exe". The problem only occurs if this library is installed and a new version of the Heavac library is installed, too.

Solution
The problem is easy to fix. In order to do so,

• Open the file:
  C:\Program Files\SAIA-Burgess\PG5 1_3\Libs\App\HEAVDL0.sxg with e.g. Notepad

• Change the line 4 from
  _Dl0Vers=_HeaIni6 to 
  _Dl0Vers=_HeaIni7
  (Don't change anything else in this file! this would lead to unpredictable behaviour of Fupla!)

• Save the file and re-open the Fupla Editor

This problem will be fixed in the next version of the Fupla libraries.

On the attempt of resizing some FBoxes in Fupla SP1.3.120 (delivered with PG5 1.3.120) a "SAIA ASSERT failed..." error message will pop up.

Therefore it isn't possible resizing all resizeable FBoxes with this Fupla version.

Symptom

SAIA_ASSERT failed at line 105 in d:\data\Projects\PG5_1_3\sfupvar.cpp:
IsInvertable()

Solution
The problem is to be fixed by running the attached patch. Please make sure that the PG5 is not running while installing the patch.

Important note
The attached patch does only work for PG5 SP1.3.120 and resolves only the problem described above.
Do not install this patch it if you have installed an other version of PG5 1.3!

In case the parameters of the "Validity scope" of the Heavec-Init FBox are set to the value "External" but no Heavec-Init FBox having these parameters set to "Public" is present (linked) in the CPU, the build will fail due to unresolved externals.

The error message of PG5 Project Manager will look similar to the list below:

Solution
The problem can easily be solved by setting the "Valitity scope"-parameters to the appropriate setting ("Local" does always work).

The Fbox internal variables can be defined by user. This is done in the Fbox parameters window (click on the key button, defined by user) give a base address and a name can also be given there. The symbol editor create than a local symbol with an array. Eg; PID HVC Fbox has 24 registers as internal variables, the name could be "internalRegName R [24]!

So it isn't easy to acces in fupla directly each register!

The best way is to make system sysmbols out of these internal variables.
How to do: Give the FBox a name (click right on the FBox, chose Properties et type a name. Eg: PID1. So after a build the system symbols are created with the names:
A.HVC.PID1.Action
A.HVC.PID1.Disable
etc..

In this way each symbol can be access individualy.

If a supervision has to access them a static address is necessary, this address has to be given in the FBox parameter window as descript above

When using PCD1 with a flash additionnal memory, after program download the CPU goes in halt, with the error: checksum fail if the CPU name starts with a number and/or contains an accent (eg: 1er étage)!!

Accent in CPU and file name should not be used, also CPU name should not start with a number!

This problem occurs on PCD1.M130  with a 1 Mbits flash memory (FW 075 and 080). It occurs also on the PCS1.

Note: If a Ram memory is used there is no problem!

Solution: Change the CPU name, no starting with a number and containing no accents!
A correction should be done in PG5 1.3  and / or in the FW.

If the symbol editor's option "Add symbols to global table" in PG5 1.3 is checked, a message saying that this is a very bad programming practice will be displayed. Some of the reasons for this statement are listed here:

• When exporting fupla pages or when adding files (Fupla, IL or Graftec files) of an other CPU the globals contained in these programs won't be imported to the CPU.

• The programs get less modular

• The global symbols may be accessed by any module. In some applications this does make sense. On the other hand it may be dangerous (e.g. in context of adding a module that already has existing symbols defined)

• Drag & Drop in symbol structure doesn't work for global symbols

• After changing one global symbol, all modules have to be rebuilt (takes more time).

As listed above there is only one case in which it does make sense define a global symbol. This case is if the symbol must be accessible in more than one modules (e.g. Fupla and HMI Editor). If this case isn't given, it is strongly recommended not defining a symbol as global (or public which means the same)!

At the end of sending character the MC5 mode does switch faster the RTS signal.

Mode MC4 and MC5 are used to communicate in character mode on RS485 Interface.

The MC4 and MC5 mode are low level mode which will set the RS485 driver/receiver in drive mode only during the transmission of information's (character/text) and will be default to receive at any other time.

However the RTS signal and the XBSY and TBSY Flag work differently on MC4 and MC5 mode:

• For MC4 mode:
  - The RTS is reseted between one bit time and 1 ms after the send of last sending character
  - The XBSY/TBSY flags are reset between 0 and 1 ms after the end of the last sending character.

• For MC5 mode:
  - The RTS is reseted between one bit time after the send of last sending character
  - The XBSY/TBSY flags are reset between 0 and 1 ms after the sending of the second to the last character.
  - It's possible that the XBSY/TBSY flags are set to 0 at the begin of the sending of the last character

Diagram showing the difference between MC4 and MC5

§ix100137§

To use the MC5 mode at least following FW versions are needed:

To use the mode MC4 or MC5 on Fupla you have to select on the FBox "Sasi Text" or "Sasi Modus C" on the FBox adjust window the parameter "RS Type" to:
RS 485 for mode MC4
RS485 short timing for mode MC5

§ix100138§

If a S-BUS master IP is placed in a fupla file you will absolutely need a second CPU in this project. Otherwise the FBox won't work due to a SASI error.

If ther is a S-BUS master-IP FBox in the program of  your CPU and no second CPU (equipped with an IP interface) is part of the project (or at least entered in the IP-table), the PCD will get a SASI error because the PCD can not communicate.
The reason for this behavior is the lack of any other known IP address except of the address of the CPU itself.

To avoid this problem in case you need to have only one single CPU per project the IP table of the partner station(s) have to be exported and then imported in the concerned CPU.
Note that this has to be done also vice versa in order to avoid the same error on the other stations.

For IL programmers: The same problem occurs with the IL instruction SASI in the mode IPM.

If a Fupla program is modified and downloaded the FBox adjust parameters of the end user will get lost. Therefore it is very important to backup (read) the FBox Parameters of the existing Fupla file before you change/modify the Fupla file.

Read FBox Adjust Parameters:
The option "Read FBox Adjus Parameters" of Fupla Editor's "Online" menu will upload all FBox online parameters of the Fupla file. The online values of the parameters will be copied into the adjust parameter field of the FBox (same behaviour as the button "<"). This will store all settings made by the end user of the PCD. After the next build of the project these values will be used as initialisation values for the Fupla program.  

Write FBox Adjust Parameters:
This option will copy the values of the adjust field in the Fupla program to the online values of the according program running on the PCD. This means that the values edited by the user will be overwritten by the values present in the Fupla file opened with the Fupla Editor (SFup). This function does the same as the button ">" in the FBox Adjust parameter windows.

When moving PG4 projects to PG5 where the FBox library HVC/CVC/HLK Dialog is used in the PG5 project, then the FBoxes have to be installed manually (because the mentioned library isn't automatically installed with PG5).

Symptom

In a PG5 1.4 or 2.0/2.1 Fupla program there are some FBoxes crossed because the FBoxes with the macro prefixes _Dl0xxx are not available. E.g. the FBox _DL0EDI2I such as shown in the screenshot below (the macro prefix can be displayed by showing the "Advanced info" from the context menu. 


Reason
The FBoxes of the library "HVC/CVC/HLK Dialog" aren't automatically included into the installation of the PG5 1.4 and 2.0/2.1. This is because the program for controlling displays (PCD7.D1xx and PCD7.D2xx) now may be done by using the HMI Editor, which is much more comfortable and efficient. Also all displays are supported by the HMI Editor.

Solution
In case the FBoxes of this library are already used in an existing (PG4 or PG5)-project it is possible to install the "CVC Dialog" library also in PG5 1.4 or PG5 2.0.

• PG5 2.1
  Download the file from this FAQ and execute the file
• PG5 2.0
  The executable installation file (HeaDlg_V26100.saiazip) is placed in the folder /PG5 Stand Alone/S-Libraries/Fboxes/ of the PG5 2.0 installation CD.
• PG5 1.4.300
  The executable installation file (HeaDl0_23141.exe) is placed in the folder /Pg5/libs/Old/ of the PG5 1.4 installation CD.

Remark concerning PG5 1.4 on Windows7 (64 bit)
Unfortunately the PG5 1.4 installer for the Dialogue FBoxes can not copy the files to the right directory. Therefore the files need to be extracted manually:

• Rename the installer file from HeaDl0_23141.exe to HeaDl0_23141.zip
• Unzip the files
• Copy the files to the folder where the libraries are installed
  by default c:\Program Files (x86)\SAIA-Burgess\PG5 1_4\Libs\App\

The main difference is the different range of values for this two types "Constant" (type "Const" in the Symbol Editor) and "K Constant" (type "K" in the Symbol Editor).

The difference can be explained with the structure of a codeline, which has the length of 32 bit:

All informations of each codeline are stored into 32 Bit (4 byte). Since the first codeline needs 18 bits  for instruction (e.g. ADD) and media code (K, R, I,...), there are 14 bits left which can - in case the media code is K - be used for the value of the "K constant". Therefore the value range of the "K constant" is 0..16383.

A "K constant" is marked by the media code (bits 14 and 15 are high) and so it can be used instead of e.g. a register (given the instruction supports it).

Note that the "K Constant" can only be used as parameter for instruction that requires a media code.

Load instructions (LD, LDL, LDH) only accept "Constants" without mediacode for its second codeline. See below:

Since on the second codeline of the LD instruction no media type is allowed but only a value is possible, the whole 32 bit of the codeline may be used as the value (-2'147'483'648..2'147'483'647) of this constant.

Note that the "Constant" only can be used with Load Mnemonics; further on it never can not be passed to an FB as parameter.

After moving windows (e.g. Project Tree of Project Editor) it can occur that the window disappears. In this case selecting them in the "View" menu doesn't help to make them visible again.

The problem is caused by impossible position definition in the registry.
To solve the problem it is recommended to delete the corresponding Registry entry. The Registry entries (folders) will be generated again at next launch of the corresponding tool; the positions of the windows will be default positions.
Make sure the PG5 isn't running while deleting the registry entries!

The Windows tool REGEDIT is fully sufficient for this operation. It is to be called under the Windows start menu by selecting "Run..." and typing REGEDIT.
Please find below the registry entries for the corresponding window to be deleted:

Project Manager:

Project Tree Winow:
HKEY_CURRENT_USER/Software/SAIA-Burgess/PG5/<version>/<version>SPM/ToolsBar-Bar5
</version>Message Window:
HKEY_CURRENT_USER/Software/SAIA-Burgess/PG5/<version>/<version><version>SPM/ToolsBar-Bar6</version></version>

Fupla Editor:

Symbol Editor Window:

HKEY_CURRENT_USER/Software/SAIA-Burgess/PG5/<version>/<version><version><version>SAIA Fupla Editor/DockWindows-Bar6
Page Navigator window:</version></version></version>

HKEY_CURRENT_USER/Software/SAIA-Burgess/PG5/<version>/<version><version>SAIA Fupla Editor/DockWindows-Bar7
FBox Selector window:</version></version>

HKEY_CURRENT_USER/Software/SAIA-Burgess/PG5/<version>/<version><version>SAIA Fupla Editor/DockWindows-Bar8</version></version>

In some cases it might be necessary to delete the whole upper directory "SAIA Fupla Editor"!

<?xml:namespace prefix = o ns = "urn:schemas-microsoft-com:office:office" />

Please note that the creation of a backup of the whole registry is strongly recommended whenever the registry is modified by the user.

The instruction SYSRD/SYSWR and the equivalent Fbox Write / Read EEPROM needs 20 ms to be executed, so if used in an XOB 0 they haven't the necessary time to be completed! It won't work.

Global symbols of an added Fupla or IL file won't be imported automatically into the corresponding CPU. Also when importing a Fupla export file the globals won't be imported.

The global symbols (from file _Global.sy5) used in a program file won't be imported using the "Add File..." task of PG5. Only the local symbols of the concerned Fupla file are added (by importing the file <filename>.sy5).
It won't help to use the import/export Fupla pages functionality.</filename>

This isn't a bug since it is dangerous to add global symbols into a CPU automatically.

As workaround you either could 

• export the globals from the source file to e.g. an excel file, delete the unused symbols in the excel sheet and import the symbols into the added file or
• doubleclick all the global symbols in the added Fupla (will add the symbol to the symbol table). Consider the fact that there could be a symbol with the same name in your previously existing file! In this case the ressource would be accessed by different modules!
• copy the whole source CPU and delete all unused files (and symbols).   

In case a text with more than 512 bytes is sent with a firmware older than 1.14.23 the according text has not been sent correctly.

Symptom
When sending a text with a length of more than 512 bytes on a PCD3 or a PCD2.M5 with a firmware older than 1.14.23 the text which is sent is not correct.
In case the text to be sent contains sub-texts which are introduced using interpreted text (e.g. the $Lnnnn) and the final length to be sent is more than 512 bytes, the same phenomenon can be observed.

Solution
Please update the firmware of your PCD to version 1.14.23 or later.

In some cases, usually after a lot of backups which have been executed, the error bit 7 (flash task already started) or 8 (flash error) is set with firmware older than 1.14.23.

Symptom
A backup DB to flash (IL instruction "copy TEXT/DB to flash card", SYSWR 3000 or 3100) fails and the error bits 7 and/or 8 are set. This error remains, even after waiting several minutes without re-attempting a backup to flash.

Solution
This problem is corrected in firmware 1.14.23 or later. Please update your PCD firmware in order to solve this problem.

No, as such a definition would be ambiquous as the square brackets are used to define an array but also as indication of the offset inside an array.

Explanation
The square brackets are used for the following cases:

• The definition of an array of symbols is done by using the square brackets behind the media type in the symbol definition:
  BaseSymbol EQU R [ArraySize]
• The square brackets are also used for the definition of an offset inside an array:
  SymbolInsideArray EQU R BaseSymbol[Offset]
  alternatively
  SymbolInsideArray EQU R BaseSymbol+Offset
  

In case of a definition of an array inside an array, it would not be clear which square brackets shall contain the offset (inside the first array) and which one shall contain the size of the new array. Using a definition such as "the first square bracket contains the offset" does not work either, as in case of the "+" notation there would not be a second square bracket.

Therefore the following code will lead to the error message below the code:


Assembling: Untitled1.src
Error 1057: Untitled1.src: Line 43: Symbol is not an array: SymbolInsideArray1: SymbolInsideArray0
1 errors, 0 warnings

Remarks

• In PG3 it was possible to create such nested arrays (because the syntaxt for the definition has been more restricted.
• In early versions of PG5 there has not been an error in case of such an ambiquous definition (but most likely the result has not been what the programmer expected).
• PG5 2.0 does abort the build with the error 1057 (see above) in case the

For writing data to files on the PCD file system and for sending SMS or EMails it is possible to enter the content of medias (registers, flags etc.) into the text to be written or sent. This is done by placing e.g. a $R0100 into the text to be sent. At the time of writing, the "$R0100" will be replaced by the content of the register 100.

While in the beginning only points could be used as seperators in interpreted texts, it is also possible using the comma as separator with recent firmware versions. In this case, instead of a point a comma is to be used:


Firmware dependencies
The comma separator can be used starting with the following firmware versions:

Yes, this is possible by calling the system function (CSF) "IPGetLocalConfig".

Introduction
For having the possibility to read the current IP configuration from the user program, a specific System Function has been added to the firmware. This function does return the IP address, the subnet mask as well as the default gateway (each address in one register). The returned value contains the full IP address in one register (each byte or the register contains one octed of the IP address):

Example
This System Function is part of the IPD Library. In order to use these functions, the file "IPLib.inc" is to be included to the source file where the function is called. This can be done with the line:

$INCLUDE "IPLib.inc"

The IP configuration can then be read in th following way:

Returned IP address (hex):               0xAC100179h
IP address in "Dot-decimal notation": 172.16.1.121 (0xACh = 172, 0x10h = 16, 0x01h = 1, 0x79h = 121)

Firmware versions supporting the GetLocalIPConfig
Please refer to the table below for the first firmware versions that support the "IPGetLocalConfig" function.

Remark
The include file "IPLib.inc" from PG5 1.4.300 and earlyer versions needs to be updated in order to "know" this feature. Therefore please download the file "IPLib.inc" attached to this FAQ and replace the existing file from PG5 which is located in the "Libs/App" of PG5:

c:\Program Files\SAIA-Burgess\PG5 1_4\Libs\App\IPLib.inc

The PCDs now support copying texts into other texts. The formats (@,$,...) are supported in the source text as well, which allows to enter the content of register directly into a text.

List of the minimal FW which is needed to support the copy text to text functionality:

  Instruction CopyText: 

 
*² 16383 Register are only available on NT-Systems (PCD2.M4.., PCD2.M5.., PCD3.)
                other PCD’s have maximal 4095 registers.  

Description of the parameter of the instruction CopyText:   

  
Description of the function CopyText: 
CopyText starts with rewriting of the whole destination text string with spaces (0x20).
If the Destination is too short, not the whole text is copied, but as many characters as possible. 
The count register contains the number of copied characters.
If the source length is smaller or equal to the destination length the number of copied character is equal to the source length, all character are copied, and no error indication and the error flag is set.

If the source length exceeds the destination length the number of copied character is equal to the destination length, not all character are copied, and error code 12 with error flag is set.  

The Error Flag of the PCD is set if any error occurs ( for example "Destination too short", "Destination not writable", "Source is a DB", "Wrong Parameters", "Text or DB doesn't exist", "Source = Destination", ... )

List with the error values for the ErrorCode

The CSF exists with error on wrong media type of the ErrorCode Parmater, and on all indicated errors. 

Note :
The Destination text/db must be writable ( RAM resident ) and the user has to include the ApplicationLib.inc before using this csf. 

Example:
Source text:
Text 100 “Alarm on station 10, @L0100. Motor is to hot. Temperature is $R0110°C.
Please call $L0020” 

Register 100 has the value 2
Register 0110 has the value 220
Text 2 “Section B”
Text 20 “John at the number 044 345 32 32” 

The Register 100 contains the pointer to the sub-text.
If the Register 100 has the value 2 then the text 2 is inserted on the position @L0100. 
After copying the source text to the destination text, the destination text will be the following:
“Alarm on station 10, Section B. Motor is to hot. Temperature is 220°C. Please call John at the number 044 345 32 32” 

The PG5 Example can be downloaded from this FAQ.

When calling an FB, the parameters should be given as an Array of flags. On compining there is an error message: "missing fb parameters displayed".

Problem
The code below does not work. On compiling / linking the error message "missing FB parameters" is displayed.              
COB 0
    0
CFB 1
    Arrayflag
ECOB

You may wonder about surprising results when programming in IL with XOR and OR operations.

It's good to know the philosophy behind.

IL-programmer will wonder why the ANL of flag 2 operation in the below picture will result in a high accu state.

§ix100500§

One have to understand that XOR and OR operations work like "open paranthesis" for arithmetic calculation.
If you want to apply the result of the XOR and OR operation, one have to "close paranthesis" by programming
an OUT on a dummy flag and testing the state of this flag by a STH as shown in the example below. Now, the
ANL of flag 2 operation results in a low accu state.

§ix100501§

Especially when writing FBoxes it might be useful to fill a PCD text with e.g. the name of an FBox. This can be achieved by using the ".s" postfix.

Possible usage
The example below shows how a the content of a macro parameter can be placed into a PCD text.

Example
Below an example of the usage of the ".s" postifix:

The resulting text in the PCD will be:

       TEXT 100 "Hello world !"

A file was uploaded and disassembled. Nothing has changed in the program code but compiling is not possible.

Problem
An uploaded and disassembled project can not be build anymore. The error message below appears:

Error 387: Multi-defined Unique Program Identifier DB 3999

Reason
On build PG5 generates a DB 3999 automatically. If a program is uploaded and disassembled the generated DB 3999 is present in the program code. When trying to build the program again, PG5 generates a new DB 3999 but the DB already exists.

Solution
Delete the DB 3999 in the uploaded source. It will be generatet again on build.

Remark
Starting with PG5.1.4 there will also be a DBX 9. This DBX does also identify the program and will be exisitng in a disassembled file. Please also remove (or skip) this section in the disassembled file.

In some cases the ASCII table can be useful for generating projects with PG5. E.g. for applying the "Root vaiable ASCII" from the HMI Editor.

Where can the ASCII table be found?
The ASCII table can be found in the "SBC Instuction List Help" file. This help can be opened

• from the IL Editor, Menu "Help" or
• directly from the Saia PG5® installation directory C:\Program Files\SAIA-Burgess\PG5 1_3\SASM32.HLP.

A program that handles H-modules does most likely include FBs (that are provided together with the PG5 Contols Suite). If a project was created with an older version of the programming tool, also the FB's provided with the older programming software were used. This may cause problems because of incompatibilities of the FB calls.

To get around of this problem it is recommended to copy the used FBs directly into the CPU directory of the concerned project. This way the use of the correct FB version is guaranteed.

If in a file the directive "$INCLUDE filename.ext" is recognised, PG5 will first search in the CPU directory itself and if the specified file isn't present there, the default FB directory will be searched.
The default FB directory (PG5 wide) is defined in the "Directories" of the "Options..." in the PG5 Project Manager menu "Tools".
A further way of specifying the FB directory (CPU wide) is using the "Directories" tab of the CPU Settings (requires the checkbox "Use Override Libraries" to be checked). In this case, the PG5 wide directory specification doesn't take effect any more.

However, since the Override Libraries might have to be adjusted if the project is transfered to anoder PC (eg. a Laptop) or the whole FB's provided by a newer version of PG5 has to be downgraded if a project is imported to a newer PG5 version, the it is the easyest and most secure way if the FB's are always directly stored in the project itself.

The IL Editor SEDIT features a block select mode which allows selecting columns instead of lines of the code. It may be used by simply pressing the "Alt"-key while selecting a code region.

If the symbol editor's option "Add symbols to global table" in PG5 1.3 is checked, a message saying that this is a very bad programming practice will be displayed. Some of the reasons for this statement are listed here:

• When exporting fupla pages or when adding files (Fupla, IL or Graftec files) of an other CPU the globals contained in these programs won't be imported to the CPU.

• The programs get less modular

• The global symbols may be accessed by any module. In some applications this does make sense. On the other hand it may be dangerous (e.g. in context of adding a module that already has existing symbols defined)

• Drag & Drop in symbol structure doesn't work for global symbols

• After changing one global symbol, all modules have to be rebuilt (takes more time).

As listed above there is only one case in which it does make sense define a global symbol. This case is if the symbol must be accessible in more than one modules (e.g. Fupla and HMI Editor). If this case isn't given, it is strongly recommended not defining a symbol as global (or public which means the same)!

In case you are using the EQU instruction for defining your symbol names and also have enabled the Symbol Editor, it might occur that there are symbols added to the Symbol Table without your intention.

In PG5 there is the option "Use Symbol Table" set by default. As further option the "Automatically add entered type/values to Symbol Table" is also enabled. This causes PG5 to enter e.g. an FB to the symbol table, also if it already is definde with the instruction EQU. During the build PG5 will detect a multidefined symbol and the following error message will appear in the message window:

Error 41: df.sy5: Line 3: Multi-defined symbol: testfb
Error 41: df.src: Line 1: Multi-defined symbol: testfb

To avoid this conflict the option "Automatically add entered type/values to Symbol Table" mentioned above should be disabled. This is to be done in the menu "Options..." of the menu "Tools" in the IL editor (SEdit).
It is sufficient to disable only this option, the Symbol Table still can be used without any further problems.

If a S-BUS master IP is placed in a fupla file you will absolutely need a second CPU in this project. Otherwise the FBox won't work due to a SASI error.

If ther is a S-BUS master-IP FBox in the program of  your CPU and no second CPU (equipped with an IP interface) is part of the project (or at least entered in the IP-table), the PCD will get a SASI error because the PCD can not communicate.
The reason for this behavior is the lack of any other known IP address except of the address of the CPU itself.

To avoid this problem in case you need to have only one single CPU per project the IP table of the partner station(s) have to be exported and then imported in the concerned CPU.
Note that this has to be done also vice versa in order to avoid the same error on the other stations.

For IL programmers: The same problem occurs with the IL instruction SASI in the mode IPM.

The compiler sets automatically the correct constant type if it don't match to the instruction.

In PCDs instruction set there are two different types of constants: The 32 bit long "Constant" and the 14 bit long "K Constant" (For more accurate information read the FAQ #100123 to this topic) which are used in a different way:

• Some instructions (e.g. the LOAD instructions LD, LDL and LDH) requires a value without a media code. In this case only a "Constant" can be inserted. A "K Constant" wan't fit here because "K" is a media type.

• Other instructions (e.g. the CMP-instruction) requires a media code. In this case only the constant of type "K Constant" can be used. The "Constant" has no media code so it wan't fit here.

Despite this rules it is possible to use this constant types in your IL code as you want. This is only possible because the compiler replaces the wrong constant type by the right one automatically. For instance:

In IL following lines are written:

The code which will be downloaded into PCD after compilation looks like this:

The automatic correction of wrong constant type works also for the parameterdefinitions of a FB-Call. I.e. it is possible to define a "K Constant" as parameter of a FB call despite inside this FB the refering parameter is calling by an instruction which doesn't allow a parameter of type "K Constante":

Of course the correction can not be done if the defined FB-parameter is called twice inside the FB and the allowed constant-type is different. In this case PG5 version >=1.3 will abort the compilation with an error message "FB parameter has bad context":

Note that in PG5 versions < 1.3 the compiler will not detect the conflict what will cause strange behaviour of your PCD!

The main difference is the different range of values for this two types "Constant" (type "Const" in the Symbol Editor) and "K Constant" (type "K" in the Symbol Editor).

The difference can be explained with the structure of a codeline, which has the length of 32 bit:

All informations of each codeline are stored into 32 Bit (4 byte). Since the first codeline needs 18 bits  for instruction (e.g. ADD) and media code (K, R, I,...), there are 14 bits left which can - in case the media code is K - be used for the value of the "K constant". Therefore the value range of the "K constant" is 0..16383.

A "K constant" is marked by the media code (bits 14 and 15 are high) and so it can be used instead of e.g. a register (given the instruction supports it).

Note that the "K Constant" can only be used as parameter for instruction that requires a media code.

Load instructions (LD, LDL, LDH) only accept "Constants" without mediacode for its second codeline. See below:

Since on the second codeline of the LD instruction no media type is allowed but only a value is possible, the whole 32 bit of the codeline may be used as the value (-2'147'483'648..2'147'483'647) of this constant.

Note that the "Constant" only can be used with Load Mnemonics; further on it never can not be passed to an FB as parameter.

The instruction SYSRD/SYSWR and the equivalent Fbox Write / Read EEPROM needs 20 ms to be executed, so if used in an XOB 0 they haven't the necessary time to be completed! It won't work.

The IL instruction DSP (display value on PCD7.F530 display) is not supported on Saia PCD® COSinus systems. When downloading it to a Saia PCD® COSinus system, the PCD will not go in RUN and give an error message such as "Invalid instruction" (e.g. a PCD2.M480), "Precompiler error" or "Invalid OPCODE" (on a PCD3.M5xx0 with firmware 1.10.16).

Why is the DSP instruction not supported on Saia PCD® COSinus systems?
Since it isn't allowed or even possibe to mount a PCD7.F530 card on a Saia PCD® COSinus system (e.g. a PCD2.M480, a PCD2.M5xx0, a PCD3 or a PCD1.M2xx0) the instruction for accessing the display of the PCD7.F530 is not supported by the CPU.

Remarks

• The PCD7.F530 can't be mouned on a PCD2.M170 or on a PCD2.M480 because it could cause a short circuit on the internal bus connector placed right under the slot B1.
• If a user program containing a DSP instruction is downloaded the PCD2.M480 won't run the program and the error message "Halt reason: invalid instruction" will be entered in the CPU's History.

Global symbols of an added Fupla or IL file won't be imported automatically into the corresponding CPU. Also when importing a Fupla export file the globals won't be imported.

The global symbols (from file _Global.sy5) used in a program file won't be imported using the "Add File..." task of PG5. Only the local symbols of the concerned Fupla file are added (by importing the file <filename>.sy5).
It won't help to use the import/export Fupla pages functionality.</filename>

This isn't a bug since it is dangerous to add global symbols into a CPU automatically.

As workaround you either could 

• export the globals from the source file to e.g. an excel file, delete the unused symbols in the excel sheet and import the symbols into the added file or
• doubleclick all the global symbols in the added Fupla (will add the symbol to the symbol table). Consider the fact that there could be a symbol with the same name in your previously existing file! In this case the ressource would be accessed by different modules!
• copy the whole source CPU and delete all unused files (and symbols).   

The reason for the error message is not clear and there is no multi-defined symbol in the new transition.

Problem
When adding a new transition (with a "Wait time" FBox) to an existing project an error appears on build:

Assembling: praca.sfc

If you have build, download a program into the PCD and when you try to open the graftec file you get the message: Everithing is OK ! Can't open the active transition.

This a Graftec bug which happen when the SBs have dynamique adresses. It can be solved by giving a static adresse to the DBs or use the next Sgraf file (not yet available)

An existing Graftec file can't be open. The CPU of the PC show up to 100% performance!

Solution
Delete the directory "SBC Graftec Editor" in the Registry under HKEY_CURRENT_USER/Software/SAIA-Burgess/PG5//

Procedure

• Close PG5
• Over the Windows "Start" button chose "RUN" menu, type "Regedit" and press enter
• Select HKEY_CURRENT_USER/Software/SAIA-Burgess/PG5//
• Delete the directory "SAIA Graftec Editor"
• Open PG5 and the Graftec file

On a build of a Profibus-DP or Profi-S-IO configuration file which contains a DP or S-I/O slave which has a huge configuration (more than 255 Byte) then this error message is shown.

Symptom
The PG5 project can not be built; the error message which leads to a failure of a build is:
Error 1096: DBX initialization data too big

Reason
The maximum size of the data mapping or the configuration of a Profibus-DP or S-IO Slave is 255 bytes.
If the data to configure a slave is more than 255 bytes the error message "Error 1096: DBX initialization data too big" is shown after the assembling of the *.sio or *.dp file.

Solution
To solve the problem please decrease the number of installed modules on the concerned slave.
To know which slave is concerned have a look at at the listing file of the Profibus-DP (*.dp) or Profi-S-IO (*.sio) configurator with a text editor. Maybe you have to enable the creation of listing files beforehand (in the PG5 Project Manager menu "Options" --> "Build" --> "Create listing files").
In this listing file search the error message (or hit the F4 key) and three lines above the error message you can see the name of the concerned DP or S-IO slave.

Example
Example of the listing file for the Slave 3:

0-1042                                                  ;Slave 3
0-1043                                                  @1:4            ;type
0-1044                                                  @1:272          ;size
                                                           ^
**** Error 1096: Profibus Network.src: Line 1044: DBX initialization data too big

The PCD3 Compact (PCD3.M2xxx) is available in the Network configurator from PG5 2.0 but not in the one from PG5 1.4 300.

Problem
It is generally possible to programm and configure a PCD3.M2xxx compact with PG5 1.4 as long as the PCD3 Compact is not used as Profi-S-I/O Master because the PCD3.M2 is not available as Profi-S-I/O master in PG5 1.4 300.

Solution
This problem can be avoided by programming the PCD3 Compact with PG5 2.0; in the Network Configurator from PG5 2.0 the PCD3.M2xxx is available.

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

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

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

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

FW versions < 1.24d could have this problem. 

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

If the master is a PCD2 with a PCD7.F750 the maximal configuration is 2942 Bytes I/O. When adding a SBC Slave to the network this limite is reduced to 2048.

Problem
A SBC Slave should be added to an existing configuration. The configuration already uses 2304 Bytes. When adding a Saia Burgess Slave the error "Configuration too large" appears. Otherwise the configuration is not really to large since the master is using a PCD7.F750 card. In this case the maximum I/O is limited to 2942.

Reason
When adding a SBC Slave to the network the maximum I/O is limited to 2048 due to a bug in the S-Net configurator.

Solution
This problem was corrected and will be implemented in the next version of PG5 1.4. If someone needs an urgend fix, contact the pcdsupport to get a corrected version.

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

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

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

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

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

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

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

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

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

Yes it is possible to be Master on the Profibus DP Master modul PCD7.D750 and Slave on the Profi S-I/O port. Otherwise there is a bug in PG5 which generates an error on compiling.

Problem
There is a SIO and a DP file linked in the project. The current station is Slave in the SIO-Network and Master in the DP-Network. On build the error message below appears:

multi defined blocks
DBX2 in modul xxx.dp

Reason
Due to an error in PG5 1.3 the SIO configurator creates a DBX 2 and also the DP configurator creates a DBX 2.

Solution
The problem will be corrected in PG5 1.4. If you need a bugfix version for PG5 1.3 please conntact the support and we will send you the version $1.3.129. The workaround for PG5 1.3.120 is:
- Go to the folder where your project is stored (p.e C:/PG5 Projects) and search your current project where the problem appears.
- Open the folder of the CPU where the problem appears
- Search for the src File of the SIO configuration. If the name of your SIO file is: "..\CPU1\SIOConfig.sio" you have to search for "SIOConfig.src".
- Open the src file and search for DBX 2. You will find it twice in the file. Rename DBX 2 to DBX 1.
- Make a build (not a rebuild all)

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

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

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

Solution

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

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

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

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

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

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

Solution

• Either update to the latest official FW for the PCD2

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

If the file dpdv.dat is read only, the Network Configurator will fail on the attempt to add a new Device to the device library. The error message "Error 214: Cannot crate file: C:\Program Files\SAIA-Burgess\PG5 1_2\DPDV.DAT" will be shown.

There is also the second message : "Error 219: Cannot add device to the library".

§ix100177§ §ix100178§

To resolve this problem, just uncheck the "read only" checkbox in the Properties window of the file dpdv.dat.

While removing the write protection make sure PG5 is closed! If it isn't, a program crash of the SNet32 (PG5 Network Configurator) could be the result. In some cases it even may happen that the file dpdv.dat will be destroyed!

In PG5 1.3 this problem is solved in the way that a message will tell the user that the file dpdv.dat is write protected. Also the Network Configurator won't crash any more.

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

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

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

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

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

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

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

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

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

The text terminals PCD7.D23x do support the Cyrillic alphabet starting with firmware version 040 while the display mounted on the PCS1 does not support Cyrillic.

Minimal hardware and firmware
The usage of Cyrillic characters require the following (or later) versions

• PCD7.D23x
  Hardware version "F" and firmware version "040" on the PCD7.D23x. Systems with older hardware or firmware can not be updated (because the CPU mounted does not support the extended functionality).
• PCS1.Cxxx
  The text terminal mounted on a PCD1.Cx does not support the Cyrillic alphabet because the processor installed does not support it. At the moment there are no intentions to add support for Cyrillic for the text terminals of the PCS1.

Remarks

• In case Cyrillic is required in combination with a PCS it is recommended using the PCD7.D23x which can be connected to PCS systems without an internal display.
• Please note that together with the HMI Editor an additional tool to change the Windows® ANSI code page is required for realizing the PG5 project for Cyrillic characters on a PCD7.D23x.

The used of the internal flag S.HMI.ALACLEAR works but there is always 1 alarm left in Buffer and the only way to clear it is to download the user programme again. This situation is caused due to a specific "unhappy"configuration of the "alarm Buffer".

Reason
The problem is caused because the option "Buffer mark: Start" has been chosen. Below you can see the parameter setting constellation which leads to this misfunction:

Solution
Change to: "Buffer mark End":

It is advised to use the default setting whenever possible.

Remark
Due to the fact that this problem is caused by the constellation of the above shown parameters of the alarm buffer configuration it is very likely it exists since the first release of the HMI Editor. There is no modification which works around this situation planned.

A non standard resolution of the PC screen does affect the play menu of the HMI editor.

If you have such shifted play menu on the HMI editor of PG5 then you have to adapt the resolution of your PC screen.


To modify the resolution of your screen make the following:

Click on a free space on your desktop screen.
Select properties.
On the display properties window select the tab settings.
On the settings tab click on the button advanced.
On the advanced settings window select the tab general
On the general tab select “normal size” on the DPI setting field.
After the restart of the PC the play windows of the HMI editor will be displayed correctly.

An incompatibilty between old hardware versions of the PCD7.D23x and the HMI Editor distributed together with PG5 1.4.200 can cause the PCD7.D23x to jump back to the root menu while browsing the menu structure.

Symptom
While browsing the PCD7.D23x, all of the sudden the display jumps back to the root menu. It is possible that this behaviour has not been present until PG5 1.4.200 has been installed and the project has been compiled/built with this version. The higher the baud rate between the PCD and the display, the more often this behaviour can be observed. The hardware version of the display concerned is older than version D.

Reason
This problem is caused by an incompatibilty between older chipsets used in the PCD7.D23x and the HMI Editor 1.4.210. The character sent by older displays (in case they are not ready to respond to a request) causes the HMI program to jump back to the root menu.

Solution
The HMI Editor 1.4.301 and the corresponding library distributed with PG5 1.4.300 do solve the problem. (The correction has been implemented in HMI Editor library version 1.4.213)
Additionally, no baudrate higher than 9600 is recommended for hardware version C.

Remark
Please also refer to the FAQ 100832 linked below for further information.

Pressing the enter button has no effect, it isn't possible to enter in the HMI structure. In PCD7.D23_ the root menu displays the PCD hardware clock showing that the communication is OK, but to enter into the structure it might be possible only by pressing quickly 10 to 15 time the enter button.

This problem can be noticed with project made with an earlier PG5 version or with new project too with PG 5 1.4.200.3 !

The temporary solution is to deactivat the Icons in tag Status Bar:



The correction is now available in SP PG5 1.4.300!

In HMI editor it is possible to acknowledge the alarms over the user programme in 2 different ways.

1. The easiest way it is using the general aknowledge flag s.hmi.GNRLACK with is available in system symbol, by default when the general acknowledge flag is set to 1 all alarms are acknowledged. Use a dynamisation as follow (no other settings are necessary in HMI Editor)
   
2. If it is neccessary to acknowledge each alarm individually then a NAK flag has to be defined for each alarm.
   
   This NAk flag is set to 1 when the alarm comes, so it has to be reset as follow:
   
   Attention: Use a different NAk flag for each alarm!

This error appears if resources used in the HMI Editor do not exist in the FUPLA global symbol list.

Problem
Error 42: Symbol not defined:_SHMI... appears on build:

Error 42: Anzeige_UG_1.hsr: Line 570: Symbol not defined: _SHMI._SD.F_Boiler_2oben, in macro: _shmi_obj_inst_record (17)

This error is caused by an FBox reference which does not exist

Problem
The error 31 appears on build:

Error 31: Anzeige_UG_1.hsr: Line 333: Syntax error, in macro: _shmi_menu_record (4)

Reason 

1. An FBox reference defined in the HMI Editor does not exist in the corresponding FUPLA File.
2. The FBox referencing is missing in the HMI Editor. 

Solution

1. Adapt the FBox reference in Fupla
2. Complete the FBox referencing in the HMI Editor
   
   

There is a bugfix to correct the error "Text loss in Standby Menu"

Install HMI Library $1.4.213 and HMI Editor $1.4.215.

Affected Version: HMI Editor    V 1.4.210 and SHMI Library V 1.4.210 
In the Standby by menu the line 7 and 8 loose the text once you save and close the HMI Editor project with the mentioned versions.

Please contact support@saia-pcd.ch
to get the bugfix version HMI Library $1.4.213 aund HMI Editor $1.4.215

There is a bug in the HMI LIb 1.4 210 which is part of PG5 1.4 200 when icons are used. If the icons are deleted from the project (in Object Attribut / Icons) the display work again normaly!

 Solution:

Update the HMI Library with the $ version 14211 in attachement

If the HMI Editor project uses multipoint topologie with RTS-CTS and a display isn't connected, a wrong indexing in the HMI library may overwrite internal registers so that in some case the error LED maybe ON! If the use registers are not overwritten by the application it might create strange behaviour!!

The tool NG-trace from Engiby offers the possibility to read out the alarm buffer. For further information please contact engiby.

www.engiby.ch 

This problem was related to a font unsed by the HMI-editor 1.4.170 which was not supported by every Windows system.

Problem
When opening the HMI-Editor the error message: "index out of bounds" appears and the HMI-editor doesn't open.

Reason
This problem was present with HMI-editor 1.4.170 and some Windows systems. The HMI-editor was using a font which is not present in every Windows system.

Solution
Install the HMI-editor 1.4.190 (part of the PG5 1.4.130 package) or a higher version. 

In some cases a other possible solution could be to set the Fonts size of the display properties of the PC to "normal"
- right mouse click on the desktop, menu properties, appearance.

This error occurs if the installed HMI Editor version does not match the current projects HMI library version. This often happens during the rebuild of a DDC Suite project which was originally created with an older PG5 or HMI Editor version.

Reason

As already explained in FAQ #100351, this error is caused by an incompatibility between the actually installed HMI Editor and the HMI library version of the current project. While it may help to deactivate the override libraries in the project's software settings, this approach is not suitable for DDC Suite projects, since these projects heavily depend on override libraries!

Solution

Copy all files shmi*.* from the default library folder (e.g. C:\Program Files\Saia-Burgess\PG5 1_4\Libs\Std) to the respective override library folder. The actual path can be looked up on the "Directories" tab within the Software Settings dialog. After copying all the shmi*.* files and doing a rebuild in PG5, the error message should be gone.

Please note: These steps are necessary for each and every single DDC Suite project, because with DDC Suite all FBoxes and further libraries are stored locally within the project!

Due to an error in the HMI Editor 1.4 this error can appear when using HMI Editor <1.4.190.

Problem
It is not possible to build the project. The following error message appears:    

Error 42: C:\Program Files\SAIA-Burgess\PG5 1_4\Libs\Std\shmi5.srx: Line 7538: Symbol not defined: _SHMI._INT.LED

Reason
There is an error in the official version of the HMI-Editor 1.4 which can cause this error.

Solution
Update the HMI Editor and the libraries to the version 1.4.190 or newer. Ask the pcdsupport-team to send you the latest version of the librarie.

The scroll bar and some menu lines are missing in HMI editor

Problem
When creating a HMI project which has more lines than could be displayed at one page the scroll bar does not appear like usual. Some menu lines get lost.

Reason
On installation of the HMI editor the question: "Do you want to keep Win32 files which are newer" appears. If the question is answered with Yes (keep the newer files) the HMI editor will not work properly.

Solution
Uninstal the HMI editor an instal it again. Choose: replace the Win32 files.

The custom standby menu of the HMI Editore features an entry called "Variable" and "Variable ASCII". These variables allow showing values and short texts (4 characters) defined by the user on the root menu. These values and texts are updated durig runtime.

The Root Variable
The root variable shows the content of the register S.HMI.ROOTVARx on the root menu in the defined format. For using this root variable, click the button "Edit Root Menu" in the "Menu Structure" tab and select the standby menu "Custom Standby".
After the next build, you will see the system Symbol S.HMI.ROOTVARx in the symbol table of this CPU. The value of this register will be shown in the root menu.

The Root Variable ASCII
This kind of root variable will show the 4 bytes of the register S.HMI.ROOTVAR3 or 4 in ASCII format. This allows displaying short texts (4 characters).
The user has to define this bytes in the register in his program (it is not possible editing the text directly in ASCII).
If the test has to change (e.g. depending on an application status), the different characters are to be loaded accordingly. The screenshot below shows a possible fupla program that changes the content of the S.HMO.ROOTVAR4 based on the value of the register "TextSelector".
§ix100313§
All characters used are defined as K-constants in ASCII representation (hex format in this example but can also be the corresponding decimal value).
The register "TextSelector" selects the character at the inputs of the "Mux integer selection" FBoxes (standard family "Integer") that is written to the output of these FBoxes.
The FBox "Move-in Byte" (standard family "Move-In / -Out") finally assembles the four selected characters (in four different registers) into the register S.HMI.ROOTVAR4. This register can be displayed in the HMI Root display.

After the download of a file the message "Ram Text not in Ram" appears instead of the menu line.

Reason
The problem is probably related to wrong Software Settings.

Solution
Go to Settings/Software and click on the button "Set Default". Rebuild and Download the project.

As the HMI Editor uses a library called SSTree.ocx that can also be used by other applications, version incompatibilities can cause problems on either of the concerned applications.

Problem
The tree with the HMI internals is no more displayed properly. Almost the whole tree is missing:

§ix100294§

Reason
The HMI-Editor is using a file called SSTree.ocx. If per example the siemens product catalogue CA01 is installed, this software will overwrite the SSTree.ocx with a newer version which is not compatible with the HMI-Editor. Therfore the tree of the HMI-Editor will not be displayed properly anymore.

Solution
The file SSTree.ocx is normaly located under WINNT/system32. To make the two softwares run on the same computer it is necessary to copy the SSTree.ocx installed with the HMI-Editor in the directory where PG5 is installed and which contains also the HMI.exe (p.e: C:\Program Files\SAIA-Burgess\PG5 1_3\)
The SSTree.ocx installed with the other software (p.e: Siemens product catalogue CA01) has to be copied in the directroy where this sofware is installed (p.e: C:\Program Files\Siemens\CA01_CH_DEU\catalog\). The SSTree.ocx in the directory system32 has to be deleted.

If a project with HMI-Trend Objects was created in an older version of PG5 (<1.3.120) this error can occur.

Problem
When building the HMI Project  with trend functions, the following error shows up and a build is not possible.

Reason
- The reason can be, that the project was created in an older version of PG5 (<1.3.120). The advanced objects had only four parameters in the first versions, otherwise now they need five parameters.
- An other reason can be when using registers instead of constantes for the parameters 2, 3 and 5.

Solution
- Import the new advanced object in the HMI Editor under Objects/Import/Standard Libraries/SHMIADO.ado. Now the Advanced Object Trend has five parameters instead of four.
- The parameters : Base address (2), Array size (3) and refresh (5) has to be constantes and not registers

If the option "warn on symbols with same type or value" is activated, the HMI editor will probably create several warnings.

Problem
The option "warn on symbols with same type or value" can be activated under Settings/Software/Advanced for easily finding multi-defined symbols. If this option is activated and a HMI-File is linked, it will generate several warnings (example below):

Warning 13: Symbols with same types and values
R 2008: Symbol 'S.HMI.PASS_0', Module: ii.hsr
R 2008: Symbol 's.hmi.PASSWORDLIST', Module: ii.hsr
R 2022: Symbol 's.hmi.ROOTVAR', Module: ii.hsr
R 2022: Symbol 'S.HMI.ROOTVAR_1', Module: ii.hsr

Reason
The HMI Editor creates an Array of Registers / Flags and the First Flag has therefore the same adresse as the whole Array (Array R 2008[10]; Register 2008).

Solution
These warnings can be ignored. They will not cause any malfunction or problems.

If the Display PCD7.D23x is configured in BUS Mode RS 485 the backlight is never on at the first page.

If all alarms are acknowleged the General Acknowleg Flag should disappear. It can happen, that a flag is still high and therefore it doesn't disappear.

Problem
The General Acknowleg Flag does not disappear even if there are no more alarms pending.

Reason
On download are not all flag correctly set to 0. Therefore it can happen that a flag is misinterpreted as pending error.

Solution
The problem will be corrected in PG5 1.4. You can avoid that problem by making a clear flag after the download. Otherwise if you need a urgent fix you can contact the support to get a Bugfix Version for PG5 1.3.

If a program is slow (p.e 6 cycles/sec) the program on a D23x terminal won't work properly anymore. Changing pages can cause problems.

When using the default settings of the HMI Editor the maximal amount of digits that can be shown are 5 digits per line. If more then 5 digits are to be shown the HMI elements can be configured to be represented on two lines.

For displaying more than 5 digits for the value of an object, set the option "Lines per element in Object" to "2 lines". This option can be found in the "Settings" tab of the HMI Editor.
As result, the elements will occupy 2 lines where the value to be shown will be represented on the second line with maximal 9 digits. Further on, also the units configured for the elements will be shown on the display.

Angle brackets '<' and '>' used in HMI texts may cause assembler errors and should therefore not be used in menus and objects.

Angle brackets '<' and '>' within texts have a special meaning as control characters for the assembler. So if angle brackets are used in HMI menu or object strings, this may cause different assembler errors, e.g.:

Error 88: hmi-test.hsr: Line 230: Unexpected closing bracket '>'
Error 42: hmi-test.hsr: Line 230: Symbol not defined: _SHMI._SD.Max
Error 100: hmi-test.hsr: Line 57: Illegal use of reserved word: Test

If such an error message is displayed during assembly, the menu and object strings within the HMI Editor should be checked for angle brackets.

To quickly find the text containing angle brackets, the referenced .hsr file can be opened with a text editor. The regarding text is located at the line number given by the error message. Please note, however, that the text must be edited within the HMI Editor, because the .hsr file is automatically re-generated when compiling in HMI editor!

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

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

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

When an element is configured as Integer with the format ##### (without dot) the value of the register is wrongly displayed on the terminal. This is a FW bug in the actual version of the PCD3.M_ and PCD2.M480.

This problem occurs with all FW version up to:

PCD3.M_         #13         (that means also 010, #11, #12)

PCD2.M480     #23         (that means also 020, #21, #22)

Solution
Please update the firmware of your PCD to the versions listed below (or later):

• PCD3.Mxxx0  FW 1.08.23
• PCD2.M480:  FW 1.08.19

During the the build of the project, PG5 checks whether the HMI library is up to date with the version of the HMI with which the HMI project was created. If this is not the case, the build will be aborted with the message below.

Symptom
The (red marked) message
Fatal Error: HMI: Wrong library version: 12130. Must be 13042 or higher
is listed in the PG5 message window and the build fails (the version numbers may have different values, depending on the versions installed on your PC)

Reason
As mentioned above, the library version used for this build is not up to date with the HMI Editor. A common reason for this is that "Override libraries" (libraries that aren't stored in the defaul directory of the PG5 installation).

Solution
Have a look at the Software settings of your CPU. Make sure that the checkbox "Use library override directories" in the tab "Directories" is not checked! 

The functions:

- close buffer when empty

- move cursor down by screen

are not working correctly

There is a wrong file SHMI.LIN in the library directory

The first installation CD's of PG5 1.3.100 probably have a wrong SHMI.LIN file, that creates this error on build. If you have this error: Open C:\Program Files\Saia Burgess\PG5 1_3\Libs\Std\SHMI.LIN with the Text Pad or an other editor. You have to change the line: Version=V1.3.100,13000 to : Version=V1.3.100,13100.
Afterwards it will work fine.

There are different status (p.e off/on/auto) it is possible to scroll, otherwise when pressing enter the status always jumps back to "off"

The problem is, that you can choose a object format or a object status. If you have chosen a format before and then you choose a status afterwards the format has to be set back to "none". Otherwise it will never work properly.

The installation guide of PG5 describes how to install the HMI Editor properly, but in some cases the message "some system files are out of date..." appears repeatedly even if following the procedure of the installation guide.

Symptom: the message mentioned above does appear repeatedly even after letting the setup program of the HMI Editor replacing the necessary files and rebooting the computer
If the PC has WIN 2000 it needs SP4, in some cases WIN 2000 SP 3 caused this symptom too.

Cure: install or reinstall the latest service pack for your operating system, then run the setup program of the HMI Editor again
            If using WIN 2000 installed SP 4

Error messages like:

1. Error 42: Display.hsr: Line 255: Symbol not defined: _HEAVAC._BID.._BIDSTR, in macro: _shmi_menu_record (4)

or

2. Unresolved Externals:

_HEAVAC._BID.Rt_Ueberwachung_Klasse_hinten._BIDSTR in module Display.obj

1. If the message "Symbol not defined: _HEAVAC... " is shown on build, the F-Box reference in HMI Editor is missing.

2. If the message "unresolved externals..." is shown on build, the option "Objects for HMI Editor" is not activated in the corresponding F-Box

Traditionally terminals were connected to the HMI Editor via RS 232 with Handshake, which is still the safest way. If more than one terminal has to be put on the same line or when the terminals are at large distances you can create RS 485 networks, but there are some restrictions. If you need only one terminal but at a large distance, RS 422 is the best choice as it offers the same functionality as when using RS 232.

To create an RS 485 network of terminals using the HMI Editor, procede as follows:

• choose a terminal that supports RS 485, for instance the PCD7.D23x. The PCD7.D79x terminals can as well be connected via RS 485, but as they don't have an automatic key repeat function, it is tedious to change setpoints with these terminals, so the PCD7.D23x are the better choice
• configure the station address and baudrate in the setup of the terminal(s)
• choose the "bus terminals" topology in the HMI Editor
• define all terminals using the same addresses as you configured before
• define the standby, busy and login menus

When working with the "bus terminals" topology the dialogue on the terminals is as follows:

• all terminals display the standby menu per default
• when the user pushes a button the relevant terminal goes to the login menu, all other terminals go the busy menu and cannot be used until the terminal in use is freed
• the login screen can contain the entry of a password. After entering the password the terminal goes into the "normal" menu structure

This is not a bug as it was forseen like that. Some customers wish it would be better to have the alarm acknowledgement protected by password! Unfortunatly it isn't possible with the actuel HMI Version 1.2 130, because when an alarm occurs it is automaticaly displayed on the screen and anyone can acknowledge it on the status line of the displayed alarm.

Once the date has been modified with the knob of the display PCD7.D230, it is not possible to set again the value 00.00! The smallest editable value is 01.01.!

There is a bug in the HMI Library 1.2.130, the Lib 1.2.134 correct this problem! Ask Saia-Burgess Controls AG or your representation for this corrected Library version.

When changing the value of an HMI Object element, the value is set to a wrong value (e.g. 287463286). It isn't possible to set the correct value for this object element.

Symptom
When changing the value of an Object element, the value is set to an absurd value (e.g. 287463286). It isn't possible to set the correct value for this object element.

Reason
This behaviour is caused by a wrong format (often floating point instead of integer value) of the limits for the concerned object element. Because the PCD compares an integer value with a floating point value, the result is wrong and the PCD sets the limit value (which is stored in floating point format). This leads to the strange, very big value.

Solution
To fix that problem make sure that the limits (Min and Max) of the object line do have the same format as the value to be limited. It isn't allowed to limit an integer value by value specified as floating point value. Therefore it isn't possible to use the range -99.9 ... 99.9 for an integer value.

Remark
Note that most values used and set by the HCV library seem to be floating point values because of the division by 10 (e.g. 1000 is interpreted as 100.0%) but actually still are integer values that have to be limited by integer values, too.

Example
The HCV range of 0..100% has to be limited in the HMI by the minimum (=0) and the maximum (=1000).

The cursor of the PCD7.D23x is displayed as "ü". Probably also other special characters are not shown correctly.

Symptom
The cursor of the PCD7.D23x is displayed as "ü". Probably also other special characters are not shown correctly. (And PG5 1.2 is used.)

Reason
This phenomenon is related to the character set chosen in the "settings" tab of the HMI Editor. Since the PCD7.D23x terminals do support all character sets by default, there is no need any more to set the character set to a specific language. If this still is done the result will be that some special characters aren't displeyed correctly.

Solution
To correct the problem, just set the character set in the HMI Editor "Settings" tab to "Default".

Remark
This FAQ is no longer relevant if PG5 1.3 or later is used.

Globals Symbols without name were not imported from HMI Editor.

Global symbols can be imported to the HMI Editor. Otherwise, if the symbols have no name, HMI Editor couldn't import them.

These symbols will not be imported:
§ix100063§ 

These symbols will be imported:
§ix100064§

The symbol editor allows the possibility to initialise ressources using the syntax :=100 (for a Register) in the column "Adress/Value" but when the CPU goes in RUN the register value is overwritten by a value initialisation in the HMI Editor!

Reason
In an earlier version of the HMI Editor it was possible to give an initial value to the resources using the following window (2x click on the symbol) in the HMI Editor. This value is written in the resource when the CPU goes in RUN!

Now it isn't any longer possible to modify those global symbol inside the HMI Editor because this practice prooved to be confusing and created more probelms than it solved.

Solution
In order to delete the HMI initialisation of the ressource in the HMI Editor the following work around is needed;

• create a new HMI Editor file in another empty CPU
• import the HMI Project into this new one; Menu (in the new HMI file): File/Import (click: select all + Ok)
• open the window above in the Object Attribut / Ressource with 2 x click on the ressource
• delete the initialisation, click: ok
• save and compile the HMI file
• import this modified HMI file into the original CPU; Menu: File/Import (click: select all + Ok)

This FAQ explains how PG5 1.4 and 2.0 handles the addresses of dynamic resources like flags and registers.

In PG5 it is possible to use dynamically addressed resources, for some applications it is necessary to know how these are handled.

When are the "dynamic" addresses assigned?
In general PG5 starts at the beginning of the dynamic address range (which can be defined in the "Build Options" of the CPU) and uses continuous increasing addresses. The sequence with which the resources are addressed is not directly given by the place of their appearance or index in the name.
Once an address has been assigned to a symbol, this symbol will keep its address until

• it is deleted or 
• a "Clean Files" is executed. 
• The device (CPU) is renamed 

In which case are addresses re-used?
When resources are deleted, the (previously) used addresses are freed directly after a new build. This means that new added resources will use the same address another symbol had before. In some cases this can cause some problems e. g. when other devices or software accesses dynamic addressed symbol by their real address.

Conclusion
For this reason, resources which are accessed from the exterior should always be addressed statically. 

No, as such a definition would be ambiquous as the square brackets are used to define an array but also as indication of the offset inside an array.

Explanation
The square brackets are used for the following cases:

• The definition of an array of symbols is done by using the square brackets behind the media type in the symbol definition:
  BaseSymbol EQU R [ArraySize]
• The square brackets are also used for the definition of an offset inside an array:
  SymbolInsideArray EQU R BaseSymbol[Offset]
  alternatively
  SymbolInsideArray EQU R BaseSymbol+Offset
  

In case of a definition of an array inside an array, it would not be clear which square brackets shall contain the offset (inside the first array) and which one shall contain the size of the new array. Using a definition such as "the first square bracket contains the offset" does not work either, as in case of the "+" notation there would not be a second square bracket.

Therefore the following code will lead to the error message below the code:


Assembling: Untitled1.src
Error 1057: Untitled1.src: Line 43: Symbol is not an array: SymbolInsideArray1: SymbolInsideArray0
1 errors, 0 warnings

Remarks

• In PG3 it was possible to create such nested arrays (because the syntaxt for the definition has been more restricted.
• In early versions of PG5 there has not been an error in case of such an ambiquous definition (but most likely the result has not been what the programmer expected).
• PG5 2.0 does abort the build with the error 1057 (see above) in case the

There is a hidden feature of the Symbol Editor (SSE) that allows statically addressing a bunch of symbols (by incrementing the address of a base symbol). This feature can be very handy in case the addresses of several symbols need to be distributed or re-distributed.

Problem
There are several symbols in the symbol editor which do have addresses which need to be re-defined. A reason therefore could be that these symbols need to be read by e.g. a SCADA system or just for a better organisation of the symbols.

Solution

• Provide a basis address for the addresses you want to distribute.
• Save the file (you don't have to close the file, just press "CTRL+S")
• Select the symbols you would like to re-address
• Push the key combination "ALT+CTRL+F9": First push the Alt-key, then push the Ctrl-key while still holding the Alt-key pressed, and then push the F9-key (while both other keys are still pressed)

Remarks

• This feature does only apply to symbols of the same media type as the first selected symbol does have.
• In PG5 2.0 it is possible to address several symbols in a sequence by "dragging" the address field (like in Excel)
• For PG5 1.4: On some PC's it is necessary to push additionaly the Shift Key: Alt+shift+Ctrl+F9. If the procedure described above dosn't work on your system. It might be necessary to push shift as well.

Due to a bug in PG5 SP1.4.130 it is not possible drag-and-dropping symbols from the symbol editor (SSE) to the Watch Window. If a symbol is dragged to the Watch Window the address of the symbol is not shown but "invalid address" instead.

Symptom
It is not possible to drag a symbol from the Symbol Editor to the Watch Window. Concerned is the Symbol Editor (SSE) that can be shown in the Fupla Editor or in the IL Editor (SEdit).

Reason
This is a bug in PG5 SP1.4.130.

Solution
This problem can be fixed with the patch 1 for PG5 1.4.130. This patch is available on the support site in the section "Product Information"-->"PG5" or from the FAQ listed below.

Workaround (in case the patch mentioned above cannot be applied)
It is still possible drag-and-dropping a symbol from the "Data List View" in the PG5 Project Manager to the Watch Window:

• Display the "Data List View" (select "Data List" from the PG5 Project Manager menu "View")

• In case too many symbols are shown, select "Filter..." from the context menu of the Data List (right mouse click)

• Apply a meaningful filter (e.g. using wild cards like MySym* or by choosing only e specific "Module")

• Drag and drop the desired symbols from the (filtered) "Data List" to your Watch Window

When working with PG5 V1.4.100 (first edition), changed public symbols are not updated in all project files.

Symptom
Modified public symols aren't updated in all modules of the project.
The version of SPM (Project Manager) is 1.4.100 (the version of the project manager is indicated in the "About SPM" window from the menu "Help")

Reason
This problem is caused by a bug of the project manager.

Solution
In order to solve this problem, replace the application SPM.exe in the installation folder of PG5 (C:\Program Files\SAIA-Burgess\PG5 1_4\Spm.exe) with the attached version (1.4.101).

Note
Only customers that have downloaded PG5 from the support site between 14.02.2006 and 16.02.2006 are concerned by this problem. The actual version available in the PG5 section of the support site contains a patch that fixes this problem.

In some cases the introduction of "Application Symbols" (A-symbol, such as A.HVC.FBoxName.Error) may be required for a created FBox. These symbols will be available (but not modifiable) in the "System" tab of the Symbol Editor.

How can an A-symbol be used?
The A-symbols are special global symbols and similar to the System Symbols (S-symbols). The can be used in all program files belonging to the according CPU of the project. A part of the symbol (a group name after the registered prefix) is defined by the Fupla programmer. This is done by defining an FBox name that will be used to build the A-symbol specific to the FBox.
Since the symbols are written and used by the according FBox, they are not ment to be modified by the user program!
§ix100344§

How can an A-symbol be created?
It can only be created if the FBox is designed to do it (e.g. most of the Heavac FBoxes).
If this is the case, it is sufficient to give the FBox a name (right mouse click on the FBox and select "FBox properties..."). After the next Build, the according A-symbols will be available.

Until PG5 version 1.2, the symbol editor always prompted the user to decide what to do if a symbol that is imported has the same media and address as an already existing resource. In PG5 1.3, the default behaviour is importing the new resource as it is. This may generate multi-defined symbols.

Symptom
When importing a symbol (from e.g. an excel sheet) that has the same media and address as an already existing symbol, it will be added to the symbol table. The result is, that this symbol is multi-defined as there still remains the "old" symbol.

Reason
By default, PG5 doesn't check any more whether the imported symbols (media and address) were already existing.

Solution
In order to cause PG5 to check the imported resources for multi-defined symbols, the according option is to be activated. This setting is found in the "Symbol Editor Options"-window. This window can be opened in from the menu Symbols --> Advanced --> Options... The relevant checkbox is named "Check for multi-defined resources after import".
§ix100271§
Once this option is enabled, PG5 will prompt the user wheter the imported, multi-defined resource shall be renamed or skipped.

Attached to this FAQ you will find a document that describes the symbol naming conventions to be obeyed by PG5 users (and especially by FBox developers).

Further on, the document contains a summary over the scopes of the different symbol types as well as a summary over their declarators.

fWhy is it important to follow the symbol naming conventions?
PG5 itself as well as FBox- and FB-libraries do work with symbols. In order to avoid symbol collisions, a programmer is urged to follow some simple rules that guarantee that the user-defined symbols and the PG5 internal and FBox specific symbols do not conflict (e.g. do have the same name but not the same values).
These rules are described in the attached document. Additionally, this document does also point out the reserved words and symbol names that mustn’t be used by users or FBox developers.

Why is it important to consider the scope of symbols?
Depending on the type of a symbol, it is "visible" in a defined region (local in a program file, global in a CPU or local in a macro). Especially when developing FBoxes, an uncorrect choice of the used symbol types will cause errors such as "Multidefined symbols".

Why mustn't a user use symbol names (and macro names) from the SBC scope?
Please note that in case you have used an FBox Macro name that belongs to the range of the SBC symbols (e.g. _sfup_blablabla) and by accident we introduce a new FBox with this name in the next PG5 version, you will receive errors from Fupla (The macro with the name _sfup_blablabla is defined twice...) and all your project with your FBox won't be functional any more! You'll have to re-write all your projects in this case.

If the symbol editor's option "Add symbols to global table" in PG5 1.3 is checked, a message saying that this is a very bad programming practice will be displayed. Some of the reasons for this statement are listed here:

• When exporting fupla pages or when adding files (Fupla, IL or Graftec files) of an other CPU the globals contained in these programs won't be imported to the CPU.

• The programs get less modular

• The global symbols may be accessed by any module. In some applications this does make sense. On the other hand it may be dangerous (e.g. in context of adding a module that already has existing symbols defined)

• Drag & Drop in symbol structure doesn't work for global symbols

• After changing one global symbol, all modules have to be rebuilt (takes more time).

As listed above there is only one case in which it does make sense define a global symbol. This case is if the symbol must be accessible in more than one modules (e.g. Fupla and HMI Editor). If this case isn't given, it is strongly recommended not defining a symbol as global (or public which means the same)!

In case you are using the EQU instruction for defining your symbol names and also have enabled the Symbol Editor, it might occur that there are symbols added to the Symbol Table without your intention.

In PG5 there is the option "Use Symbol Table" set by default. As further option the "Automatically add entered type/values to Symbol Table" is also enabled. This causes PG5 to enter e.g. an FB to the symbol table, also if it already is definde with the instruction EQU. During the build PG5 will detect a multidefined symbol and the following error message will appear in the message window:

Error 41: df.sy5: Line 3: Multi-defined symbol: testfb
Error 41: df.src: Line 1: Multi-defined symbol: testfb

To avoid this conflict the option "Automatically add entered type/values to Symbol Table" mentioned above should be disabled. This is to be done in the menu "Options..." of the menu "Tools" in the IL editor (SEdit).
It is sufficient to disable only this option, the Symbol Table still can be used without any further problems.

It may occur that during a build the error message "Error 41: _Global.sy5: Line 147: Multi-defined symbol: Status22" causes a fail of the build. In case you are absolutely sure you don't have any multi defined symbols and if you do address your symbols with relative adresses, have a look at this FAQ.

If this problem shows up, double click on the error message in the messge window of PG5 Project Manager. The result is that the symbols will be shown in the symbol window of PG5 Project Manager.

Now have a look at the address field. In case the addresses of the red marked symbols (causing the errors) is relatively addressed, make sure that the relative address is a backward reference and not a forward reference. This means that the symbol that is the base address of the "problem causing" symbol must be listed before the relatively addressed symbol.
If this isnt the case, drag and drop the "base address"-symbol before the relatively addressed symbol, safe the global symbols and rebuild the project.

This problem is solved in PG5 1.3.

The main difference is the different range of values for this two types "Constant" (type "Const" in the Symbol Editor) and "K Constant" (type "K" in the Symbol Editor).

The difference can be explained with the structure of a codeline, which has the length of 32 bit:

All informations of each codeline are stored into 32 Bit (4 byte). Since the first codeline needs 18 bits  for instruction (e.g. ADD) and media code (K, R, I,...), there are 14 bits left which can - in case the media code is K - be used for the value of the "K constant". Therefore the value range of the "K constant" is 0..16383.

A "K constant" is marked by the media code (bits 14 and 15 are high) and so it can be used instead of e.g. a register (given the instruction supports it).

Note that the "K Constant" can only be used as parameter for instruction that requires a media code.

Load instructions (LD, LDL, LDH) only accept "Constants" without mediacode for its second codeline. See below:

Since on the second codeline of the LD instruction no media type is allowed but only a value is possible, the whole 32 bit of the codeline may be used as the value (-2'147'483'648..2'147'483'647) of this constant.

Note that the "Constant" only can be used with Load Mnemonics; further on it never can not be passed to an FB as parameter.

Global symbols of an added Fupla or IL file won't be imported automatically into the corresponding CPU. Also when importing a Fupla export file the globals won't be imported.

The global symbols (from file _Global.sy5) used in a program file won't be imported using the "Add File..." task of PG5. Only the local symbols of the concerned Fupla file are added (by importing the file <filename>.sy5).
It won't help to use the import/export Fupla pages functionality.</filename>

This isn't a bug since it is dangerous to add global symbols into a CPU automatically.

As workaround you either could 

• export the globals from the source file to e.g. an excel file, delete the unused symbols in the excel sheet and import the symbols into the added file or
• doubleclick all the global symbols in the added Fupla (will add the symbol to the symbol table). Consider the fact that there could be a symbol with the same name in your previously existing file! In this case the ressource would be accessed by different modules!
• copy the whole source CPU and delete all unused files (and symbols).   

Due of a firmware error it's possible that on the history of the PCD3.M5340 there is an entry "Resistors Fail".

Symptom
When trying to enable the termination resistors of port 3 of a PCD3.M5340 (produced beginning of 2012) the entry "RESISTERS FAIL" is entered in the PCD history.

Reason
If this error is shown in the PCD history, then it isn't possible to use the RS485/RS422 termination resistors for the port #3 of the PCD3.M5340 (RS485/RS422 port on the 9-pole D-Sub connector) due to a firmware restriction.

Solution
Please update the PCD firmware to version 1.16.60 or later. This firmware can e.g. be found in the lates BACnet firmware maintenance package.

Remark
The communication on the port #3 is possible without problems given the termination of the bus is realized externally.

In case a backup from/to the flash card (e.g. a PCD7.R500) can not be executed (due to the reasons listed below) this following message is displayed by PG5: "Failed to copy to/from Flash. Check Flash memory or card is fitted?"

Possible reason
It is most probably due to the fact that the flash memory doesn't contain a user programme or the contained configuration isn't compatible with the PCD.
For example the configuration might contain an IP Adress but the PCD doesn't have an Ethernet port!

Possible solution 

• use the flash memory on the suitable PCD
• or try to download a new user programme / configuration from the PCD
  -> flash card (Project Manager menu "Online" --> "Flash Memory" --> "Copy program to flash"
• or delete the content of the  Flash memory using the press Run/Halt button beside the USB connector. Therefore press longer than 1 minute (until the Red/Green LED is flashing at 2 hz) at power up as described in the manual 26/789 chap. 3.19.1

If PG5 1.4.300 and a software from Nokia or Microsoft Mobile are installed on the same PC, it can occur that program files generated from PG5 add-on tools (HMI Editor, Web Editor, BACnet Configurator etc.) cannot be deleted and renamed any more.

Symptom
It is not possible deleting or renaming a file created with a PG5 Add-on tool (like e.g. the HMI Editor, Web Editor or BACnet configurator). Windows gives an error message like "File can not be deleted/renamed because it is beeing edited.
When attempting to rename a CPU, an error message saying "The CPU cannot be renamed or deleted. A program file is open" (see below):


Reason
This problem is caused by the fact that a Nokia (or Microsoft Mobile) application responds to one of the PG5 messages which makes it look like an add-on tool.

Solution
Attached to this FAQ a patched version of the PG5 Project manager can be found. Please replace your existing file "SPM.exe" (located in the folder "c:\Program Files\SAIA-Burgess\PG5 1_4\Spm.exe") with the unzipped SPM.exe from this FAQ.

Note
The patch attached to this FAQ does only apply for PG5 1.4.300!

This is a bug in PG5 1.4 200 assembler.

This is corrected with the attached file.
Unzipp and copy it in C:\Program Files\SAIA-Burgess\PG5 1_4\

On PCD2.M480 it might happen that when a Online connection went offline and OnLine again that it doesn't work again: a message "No response" appears! In order to be able to connect again, it is necessary to plugg out and in again the programming cable PCD8.K111.

This phenomenon is related to the way the DSR signal is managed on the serial port of your PC/Laptop! We have noticed this problem on some Dell Desktops.

Solution
Please use PG5 1.4.300 in order to avoid this problem (at least version 1.4.200.1 is required).

Old V1.2 ".im5" files are not compatible with V1.3 and later if they were uploaded from a PCD containing Flash or EPROM memory, because the code/text in Flash or EPROM was not uploaded if the PCD contained Flash or EPROM memory.

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. 

After an aborted installation of PG5 1.4.130 it can occur that PG5 has lost its "Application Directory" path setting. As result an error message "Applications Directory not configured" is showed if PG5 is launched.

Symptom
The following "SBC Project Manager" error message is displayed if PG5 is launched:

Reason
Due to a bug the PG5 installer deletes the directory settings if an installation of PG5 is aborted (and there has already been a PG5 1.4.xxx installed on the PC).

Solution

A PCD equipped with a PCD7.F655 (firmware version 041 or newer) can request its IP configuration from a DHCP server. For enabling this feature a special registry key for PG5 needs to be created.

What are the prerequisites to use DHCP?
This functionality depends on the firmware version of the PCD7.F655 and can only be used with PG5 1.4.110 and newer. For PG5 1.4.120 a special registry key needs to be created for the configuration to be available.

How to enable DHCP configuration in PG5 Hardware Configurator?
For that the DHCP configuration can be selected a new registry key needs to be created:

• Open the Microsoft Registry Editor (from the Windows Start menu select "Run...", type "regedit" and run it by clicking "OK")

• In the Registry Editor browse to the key:
  HKEY_LOCAL_MACHINE\SOFTWARE\SAIA-Burgess\PG5\1.4\Global\

• On the right side of the window right-click the mouse and select "New" --> "String Value"

• Name this new String Value with "AllowDHCP". Note that this string is case sensitive!

• Double click this new String Value and in the appearing "Edit Sting" window enter "Yes" as Value Data. Also this string is case sensitive!

• Close the Registry Editor and (re-)start PG5. You should now have a new checkbox called DHCP in the TCP/IP tab of the Hardware Configurator.

Why is a special registry key needed?
We have introduced this feature hidden because the DHCP client functionality can only be used in special situations. In fact this configuration does only make sense if the PCD does only send requests but nobody needs to access it over Ethernet. If there are other devices that need to access the PCD (having received a dynamical IP address), these devices need to get the address of the PCD via another tool which is not part of the PG5 Controls Suite.

The PCD CPUs can be protected with a password. Once the CPU is password protected it is not possible reading its hardware or user program any more.

How can I protect my PCD with a password?
The protection is done by configuring a password in the hardware settins and downloading this configuration (make sure you have enabled the "Password" in the download window).

How can I remove the password?
There are two possibilities to remove the password from the PCD:

• You can re-download the hardware configuration (with the password protection in the Hardware Settings unchecked). Again, make sure you have enabled the "Password" in the download window. You will be prompted for the password when downloading the new configuration.
• You can clear the whole memory of the PCD or the PCS. Doing so will not only remove the password but will erase the whole configuration and user program of the PCD! The "Clear Memory..." function can be found in the menu "Online" of the PG5 "Online Configurator".

Restrictions

• The procedure "Clear Memory..." does not yet work for all CPU types (e.g. the PCD3 memory can not be cleared with this function). (An alternative way could be removing the battery and removing the power supply in case the user program is stored in RAM).
• The minimal PG5 version featuring the "Clear Memory..." function is PG5 1.4.120.

PG5 program files can't open with actived Antivir guard.

Symptom
A full active firewall software Avira Antivir blocks PG5 functionality. 

Reason
The software Antivir doesn't recognize PG5 as harmless software and therefore blocks the execution of parts of PG5 which leads to misfunction of PG5.

Solution
In the Antivir guard configuration exclude the PG5 installation path (default "C:\Program Files\SAIA-Burgess\PG5 1_4\" for PG5 1.4)

When using CSF instructions in a PG5 1.4.110 project, it can occur that a build fails due to the error "Too many FB parameters (max is 255)".

Symptom
A "rebuild all files" of a project containing CSF instructions failes sometimes (not always and the line where the error occurs is not always the same, either). The error indicated in the message window of PG5 Project manager is:
Error 56: SimpleFile.src: Line 100: Too many FB parameters (max. is 255)
On the other hand, a "Build changed files" of the same project is working properly.

Reason
The reason for this problem is a bug in the Saia PG5 Build Utility (SAsm32.dll).

Solution
You can either install the patch attached to this FAQ or you can introduce a (never called) FB before the CSF causing problems. An example for introducing such a non-called FB could be the following:

This problem is solved in the next Service Pack of PG5 1.4

It might occur that a build of a Fupla file generates "Operand errors" and the build fails. In this case a "Clean files" most likely will help.

Symptom
During a project build while the linking process an error message as listed below appears:
Operand errors:
Error 320: Fupla.fbd: Line 4: Invalid FB parameter: CFB _HEAVAC._FB._REG1: Param 2. See module heavac5.srx: Line 919
Error 320: Fupla.fbd: Line 5: Invalid FB parameter: CFB _HEAVAC._FB._REG1: Param 3. See module heavac5.srx: Line 927
Error 320: Fupla.fbd: Line 4: Invalid FB parameter: CFB _HEAVAC._FB._REG1: Param 2. See module heavac5.srx: Line 919
Error 320: Fupla.fbd: Line 5: Invalid FB parameter: CFB _HEAVAC._FB._REG1: Param 3. See module heavac5.srx: Line 927
This problem still remains after a "Rebuild All". 

Reason
This error message is generated because an internal, project related symbol table is corrupted. As long as PG5 recognizes that this file is present, it won't be re-generated (and therefore will cause the same error again and again).

Solution
In order to resolve this problem, a "Clean Files" of the "Symbol information files" can be executed. The "Clean Files"-window is opened from the menu "CPU", "Clean Files...".

Additional note
The "Clean Files" for the symbol information files will re-allocate all dynamically distributed symbols!

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§

test SBUS station / CPU

don't load a programm in the wrong Sbus station or CPU

When using PCD1 with a flash additionnal memory, after program download the CPU goes in halt, with the error: checksum fail if the CPU name starts with a number and/or contains an accent (eg: 1er étage)!!

Accent in CPU and file name should not be used, also CPU name should not start with a number!

This problem occurs on PCD1.M130  with a 1 Mbits flash memory (FW 075 and 080). It occurs also on the PCS1.

Note: If a Ram memory is used there is no problem!

Solution: Change the CPU name, no starting with a number and containing no accents!
A correction should be done in PG5 1.3  and / or in the FW.

By default the DB 3999 is used as "unique program identifier". In some special cases it might be necessary to change this address. This FAQ describes how this is done.

Changing the address of the Unique Program Identifier (UID)
The unique program identifier of a CPU can be chagend by a special "Additional Build Option" to be edited in the tab "Advanced" of the "Softare Settings" in the PG5 project. In this field, enter:
/UIDDB=n
where n is the desired address (0..3999) of the UID.

It may occur that a build fails because of a "dynamic space overflow for type ...". This message is created by PG5 due to a too small range of ressources that PG5 can distribute dynamically.

To increase the amount of ressources open the Software Settings Window (or double click on the red error message in the message window of PG5 Project manager) and select the concerned tab. A dynamic space overflow can occur for all media types like registers, flags, timers, counters etc.

Now increase the dynamic space by editing a smaller number as first address for Registers, Flags, Counters, Texts or DB's.
In case you run into a dynamic space overflow for Timers you have to increase the last timer in both fields, the "Last Timer" and "Dynamic Space, Timers, Last Address".

Example such an error message:

Fatal Error 368: Auto-allocation/dynamic space overflow for type: R

If the download of the HW settings or the program has been aborted or interrupted, it is possible that the signature or the Flash EPROM got corrupted. This causes the PCD to interprete the user memory chip as RAM chip and therefore it isn't possilbe any more to write the Flash user memory.

Symptom
After an interrupted or aborted download of the hardware settings or the user program it isn't possible to download the hardware settings. The common error messages of PG5 are:

• "PCD memory write error" (after attempt to download correct HW settings or program)
• "The configured Code/Text Memory size is incorrect, it should be 448KB." (after attempt to download uploaded HW settings).

To figure out whether your mounted Flash has a wrong signature written in, either upload the HW settings or open the Online Debugger and type "DM[Enter]"(Display Memory Map).
In case it says that there is RAM mounted but you know that it is a Flash chip, this chip is concerned of the problem described here.

Reason
Once the signature in the header of the Flash user memory is corrupted it isn't possible any more to write this chip using the PCD. Since the PCD interpretes the mounted chip as RAM it also tries to write it like RAM (what will fail...).

Solution
The only way to reuse this user memory is to erase it using an EPROM burner like GalepIV or similar. Once the Flash is ereased and mounted again, the PCD will recognise an empty chip and test whether it is RAM or Flash memory. Once the Flash is recognised the chip will receive the correct Flash signature in it's header.

Note
Please note that also wrong jumper positions of the memory size or the memory type (RAM, Flash or EPROM) can cause the same symptom (because also in this case the PCD tries to write on the flash with the wrong procedure). In this case the problem can be solved by switching the jumpers to the right position (according to the memory mounted).

After moving windows (e.g. Project Tree of Project Editor) it can occur that the window disappears. In this case selecting them in the "View" menu doesn't help to make them visible again.

The problem is caused by impossible position definition in the registry.
To solve the problem it is recommended to delete the corresponding Registry entry. The Registry entries (folders) will be generated again at next launch of the corresponding tool; the positions of the windows will be default positions.
Make sure the PG5 isn't running while deleting the registry entries!

The Windows tool REGEDIT is fully sufficient for this operation. It is to be called under the Windows start menu by selecting "Run..." and typing REGEDIT.
Please find below the registry entries for the corresponding window to be deleted:

Project Manager:

Project Tree Winow:
HKEY_CURRENT_USER/Software/SAIA-Burgess/PG5/<version>/<version>SPM/ToolsBar-Bar5
</version>Message Window:
HKEY_CURRENT_USER/Software/SAIA-Burgess/PG5/<version>/<version><version>SPM/ToolsBar-Bar6</version></version>

Fupla Editor:

Symbol Editor Window:

HKEY_CURRENT_USER/Software/SAIA-Burgess/PG5/<version>/<version><version><version>SAIA Fupla Editor/DockWindows-Bar6
Page Navigator window:</version></version></version>

HKEY_CURRENT_USER/Software/SAIA-Burgess/PG5/<version>/<version><version>SAIA Fupla Editor/DockWindows-Bar7
FBox Selector window:</version></version>

HKEY_CURRENT_USER/Software/SAIA-Burgess/PG5/<version>/<version><version>SAIA Fupla Editor/DockWindows-Bar8</version></version>

In some cases it might be necessary to delete the whole upper directory "SAIA Fupla Editor"!

<?xml:namespace prefix = o ns = "urn:schemas-microsoft-com:office:office" />

Please note that the creation of a backup of the whole registry is strongly recommended whenever the registry is modified by the user.

This converter is not suitable for application where its RTS signal is driven by a PC (PG5 and Visualisation system). The different RTS-handling with Win XP / Vista cause problems. A stable connection can't be garanteed.

You find on the market intelligent RS 232 - RS 485 converter appropriated for PG5 and supervision. For swiss customer the following adapter is avalable from Distrelec: I-7520A Manufacturer: ICP-DAS

www.distrelec.ch

www.distrelec.ch

www.icpdas.com/products/Remote_IO/i-7000/i-7520a.htm

If the time of the PC you are working on, or the time of the server where the project files stored is behind the time that the project has been build or saved the last time, the project manager thinks that another build is required. The problem appears especially when moving a project from one computer to another.

Cure:

• set the clock of the PC or server
• or import the CPU's in a new project

Note: If some of the files of a project are write protected this can produce simliar effects. A common source of write protected files are copies on CD's, as all files on a CD are write protected. Make sure you store backups and transfer projects in zipped format, like this the write protection does not harm.

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

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

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

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

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

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

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

Problem:

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

Solution:

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

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

Reason:

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

Solution:

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

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

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

Remark:

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

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

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

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

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

Your Webproject look like this:

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

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

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

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

Here is the description how to proceed.

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

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

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

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

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

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


Paste in the Web-Editor8 painter.


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



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


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


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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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


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

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


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

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

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



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

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



For Webeditor8 you must set up the following options:



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

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

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

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

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

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

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

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

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

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


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

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

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

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


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

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

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

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

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

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

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


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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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


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

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

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

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

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

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

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

Procedure for registering SCRRUN.DLL

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

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

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



Please find the necessary informations in the following text.

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

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

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

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

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

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

Examples

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Supported features on a MB Panel PCD7.D4xx

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

Restrictions related to *.gif files on the MB Panel

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Step-by-step example Web Editor 5

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

Step-by-step example Web Editor 8

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Possible Reasons:
Wrong "Base PPO Name" selected.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

  View of previous WebServer	View of WebServer2

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

The alarm appears correctly but the alarm text is missing.

Possible Reasons: 

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

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

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

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

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

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

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

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

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

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

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

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

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

PDP,,R100+@COFF_index@

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

Ressource_name_of_PG5+@COFF_index@

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Solution

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

Remarks

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

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

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

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

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

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

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

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

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

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

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

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

Solution
There are two possible solution in this case:

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

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

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

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

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

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

Install the corrected Alarming library 103001in attachment!

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

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

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

Solution
Update the firmware to 030 or $2A

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

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

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

Solution
Switch off the debug option.

§ix100456§

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

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

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

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

Negativ values are not displayed correctly in a Web Application

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

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

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

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

Web Editor 5.07 Project with Microbrowser V1.5.07.074

URL Jump doesen't work!

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

    Contact PCD Support

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

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

Examples

• Thisismygif.gif (11 charakters=ok)

• Thisteqistoolong132.teq (19 charakters=too long)

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

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

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

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

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

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

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

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

uBrowser.xml

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

"Storage Card/Micro-Browser/"

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

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

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

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

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

§ix100303§

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

§ix100304§

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

§ix100305§

Define the Excel cell where you want to store the table

§ix100306§

This error appears if the itq file is empty.

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

Reason
The itq file is empty

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

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

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

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

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

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

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

Solution:

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

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

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

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


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

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

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

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

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


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

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

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

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

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

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

  

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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


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

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

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

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

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

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

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

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

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

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

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

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

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

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


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

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

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

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

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

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

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

Solution
The solution is:

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

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

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

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

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

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

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