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

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

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

 

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

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

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

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

 

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

 

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

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

 

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

 

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

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

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

 

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

 

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

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

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

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

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

 

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

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

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

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

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

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

 

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

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

Examples

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

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

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

 

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

 

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

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

 

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

 

 

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

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

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

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

 

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

 

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

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

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

 

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

 

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

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

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

 

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

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

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


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

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

 

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

 

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

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

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

 

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

 

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

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

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

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

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

 

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

 

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

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

Remarks

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

 

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

 

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

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

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

 

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

 

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

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

 

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

 

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

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

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

 

Only FLS devices with automatic supports MP-Bus communication.

A new FBox library is needed

 

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

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

 

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

There is no need to use a Tridonic interface.

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

 

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

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

Additionaly an USB interface is necessary.

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

 

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

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

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

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

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

Updates

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

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

 

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

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

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

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

The option has to be a constant.

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

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

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

 

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

Availablility of the FBox

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

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

 

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


Remarks

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

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

 

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

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

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

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

 

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

 

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

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

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

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

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

 

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

 

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

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

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

 

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

 

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

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

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

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

 

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

 

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

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

 

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

 

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


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

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

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

 

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

 

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

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

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

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

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

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

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

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

Other new features of library version 2.5.142

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

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

 

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

 

 

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

 

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

 

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

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

Solution

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

 

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

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

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

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

 

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

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

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

Example
Definition of the initial values:

Actual online values:

Upload function:

 

DB with new initial values:

 

 

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

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

 

 

 

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

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

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

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

PG5 does not change the TAPI settings of Windows.

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



 

PG5 does apply the following rules:

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

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

 

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

 

 

Yes, starting in the Heavac FBox library version $2.6.153 for PG5 2.0 (or $2.5.318 for PG5 1.4) the FBox "Fan Optimizer PI" features the option to start with a initialization value.

 

Minimal FBox library versions where an initialisation value for the "Fan Optimizer PI" can be provided:

• PG5 2.0: Heavac library version $2.6.153 or newer
• PG5 1.4: Heavac library version $2.5.318 or newer
  

With the HVC FBox 'Clock write' one can set the internal time and date of the PCD.

 

You can apply time and date to the FBox and write those settings into the PCD by triggering the 'EnT' and 'EnD' entries of the 'Clock write' FBox. Notice, that it's not possible to enable time and date instantaneously together with one flag. Time and date have to be enabled one after the other. This FAQ's valid until this phenomenon is corrected with a PG5 version or a specific Firmware.

 

Depending on the resistive temperature detector type and the analogue input module, various combinations are possible which are not all listed in the FBox or the manuals.

 

In general an analogue input module designed for measuring the resistance of an NI1000 or PT1000 sensor can also measure the resistance of e.g. an NI1000 Landis & Staefa (L&S) or an NTC10 sensors (and many more). However, the FBox does not necessarily feature the option for configuring the relevant sensor type. In this case, the digital value of the input module can be read in the mode "1:1" and based on this value, the temperature can be calculated (or more precisely: interpolated) by using the FBox "Conversion 20 point" from the FBox Family "HVC General".
The according values which are to be filled in the "Conversion 20 point" FBox can be obtained from Saia-Burgess Controls AG.

Which combinations are possible?
In general it is important that the resistance range for which the analogue input module is designed for does fit the resistance range of the sensor for the temperature range to be measured. It is even possible to apply e.g. a parallel resistance in order to shift the resistance measured to a range which can be measured by the analogue input module. Below you can find some often used combinations of analogue input modules and special tempearture sensors:

• NTC10k sensor with PCD2/3.W340 together
• NTC10kPre sensor with PCD2.W220Z02 or PCD3.W220Z03
• NTC20k Honeywell with PCD2.W220Z02 or PCD3.W220Z03 
• Ni1000 L&S with large temperature range on PCD2/3.W220 or PCD2/3.W340
• Ni1000 Tk 5000 with PCD2/3.W360
• Ni200 DIN 43760 with PCD2/3.W350
• Potentiometer 1kOhm on PCD2/3.W220
• Potentiometer 2kOhm on PCD2/3.W340
• Staefa T1 with PCD2/3.W220
• QAC 31 with PCD2/3.W220
• KTY10-6 on PCD2/3.W220 or PCD2/3.W340 (temperature range -45..50°C)

Where from do I get the values for the conversion?
Please send a mail which contains the specific type of your sensor (if possible, provide the resistance table of the sensor) and the definition of the temperature range you need to measure to support@saia-pcd.com.

 

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.

 

The PI controllers of the Heavac library was modified in the version step from PG5 1.1 to PG5 1.2. This seems a bit disturbing on the first sight. This FAQ explains the changes and their reasons.

 

Explanation
For historical reasons, the "old" PI controller from PG5 version 1.1 and before didn't have the same parameters as the rest of the controllers of the Heavac library. Among others, the only way to set the ampification factor was the option "Amplification F_p" whle the option "X_p range" was absent. This didn't really fit into a library dedicated to the building automatisation, where the "Xp range" is the common specification for the proportional factor of a P controller.
An additional weakness of the old PI controller from PG5 1.1 was the missing dead range of the FBox. There was also a rather complicated specification of the minimal- and maximal percentage of the I-portion of the controller output.
In order to increase the functionality and to reduce the complexity of the PI controller, its implementation got changed.

 

Points to be considered when updating the FBox
Since not only the interface but also some default values were changed, the following points are to be considered when applying the new version of the PI controller:

• The new default value for the proportional factor is "Xprange" and not any more the "Amplification Fp"
  (formula for conversion: Xp = ( Ymax - Ymin ) / Fp).

• The new FBox does have a default dead range of 1% (in order to have the same behaviour as the old FBox had, choose 0%).

• The default value for the integration time Ti is 999.9 seconds in the new FBox while it was only 60 second for in the old FBox (in order to avoid a too agressive controller behaviour with default values, the default value was increased).

Are all existing FBoxes in the existing Fupla programs to be modified?
No, Fupla will leave already existing FBoxes as they are; they will work as before (also after an update of PG5 the old file can be compiled and the old FBox implementation will be used).
Note that PG5 will not insert the old FBox any more. Once an (old) FBox is deleted, the only possibility is using the new version.

 

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.

 

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:

Assembly complete. Errors: 0 Warnings: 0
Linking: _2_M150.obj+IP_Watchdog.obj+fuplafile.obj+
_Global.obj+_TCPIPDBX.obj+heavac5.obj
Lib files: sfuplib3.obl
To: 2_M150.pcd 2_M150.map

Unresolved Externals:
_HEAVAC._SAMPLING._ONESEC in module fuplafile.obj
_HEAVAC._PERFORM._CYNUMBER in module fuplafile.obj
_HEAVAC._RESET._EXEC in module fuplafile.obj
_HEAVAC._SAMPLING._OVERRUN in module fuplafile.obj
_HEAVAC._SAMPLING._INTERVAL in module fuplafile.obj
_HEAVAC._RESET._SIGNALING in module fuplafile.obj
_HEAVAC._SAMPLING._FIRSTSMPL in module fuplafile.obj
_HEAVAC._SAMPLING._SAMPLE in module fuplafile.obj

Linkage complete. 8 errors, 0 warnings.
Build failed. Total errors: 8 Total warnings: 0
==========================================================

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

 

The FBoxes of the Modem- or Heavac-library (HVC, CVC or HLK FBoxes) must be placed in a cyclically called program block (but not in an XOB or SB!). The reason for this restriction is the initialisation procedure and the internal code structure of the libraries.

 

Since the initialisation of the adjust parameters of the FBoxes is done in the first program cycle, the concerned FBox must be processed while this program cycle.

A further point to be considered it the fact that some of the FBoxes do need several program cycles until their task is processed (e.g. FBoxes for reading analogue input values do only process one channel per program cycle).

As result of those facts it is absolutely necessary that the FBoxes of the HVC and Modem library are processed cyclically in an COB. Also a permanently called FB or PB is possible.
It is not allowed to place FBoxes of the HVC or Modem library in a XOB or in an SB! If they are placed in a XOB the initialisation isn't guaranteed; if they are placed in a SB the code of the FBoxes don't work correctly.

 

the HVC reset option applies to the adjust parameters of the HVC FBoxes. Depending on the mode selected the adjust parameters modified by the end user will be reset to the values entered in the Fupla program.

 

The reset function applies to the adjust values of all FBoxes that belong to the HVC library or the DDC Suite library.
In normal (default) case the values programmed in the FBoxes are set on every startup of the PCD. In case either the end user or the programmer has modified the online values, these modifications will be lost on next startup (or rising edge of the Res input if the "Evaluate Reset Input" was set to "In Runtime").
This behavior does make sense if the values never were initialized or if the programmer did upload the adjust parameters into his program and downloaded it again.
In case the PCD was powered off for an other reason, it may be annoying for the end user because he has to re-adjust all his settings.
This annoyance easily may be avoided by correctly using the Reset options!

In the HVC Init FBox there is the option "Evaluate Reset Input" which refers to the input  "Res" of the input.
The possible selections are "At Startup", "In Runtime" or "Never". The option "At startup" could be used together with an Input connected to the FBox. If the PCD is started while this input is high, the reset will be executed. On "normal" boots of the PCD the values modified by the end user won't be changed.

Further on there is the option "Automatic Reset" which is by default "activated". This causes the program to reset the adjust parameters on startup after a download of the program by PG5.
If the reset input is used, this option won't be used anymore and can be switched to "not activated".

 

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\

Sometimes it is necessary that the callnumber can be changed in runtime from a webproject, hmi, visualisation... Since the phone numbers are stored in hexadecimal the number can not be easily overwritten.

 

Problem
A phonenumber should be changable in runtime, per example the destinations of the "Call SMS" FBox. Since the phone numbers are stored as hexadecimal values they cannot be overwritten without a conversion.

Solution
The modem library offers FBs for the conversion of the phonenumber. The following FBs are available (after placing the "Modem18" FBox in a Fupla and having rebuilt the program once):

• s.mdm.hextoasc Convert Phone number from HEX to ASCII in 2 reg
• s.mdm.hextotxt Convert Phone number from HEX to ASCII in text
• s.mdm.asctohex Convert Phone number from ASCII 2 reg to HEX
• s.mdm.txttohex Convert Phone number from ASCII 2 reg to HEX

More information about this FBs can be found in the help of the FBox "Update Callnumber". A small example for the use of this FBs is available on request.

 

Yes, the FBox Family "Modem" features an FBox "Read GSM Level".

 

This FBox allows reading the signal quality of the GSM signal.

The Output of the F-Box is a signal quality value (possible values are 0 to 31 and 99)

• Value 0 is the worst
• Value 31 is the best
• Value 99 indicates that the signal level is not known or not detectable

Information about the signal quality

Marginal - Values of 9 or lower.
At these sort of levels, it is very likely that you may suffer low throughput and disconnects due to cell loading/breathing.

Workable under most conditions - Values of 9 to to 14.
Could suffer poor throughput and disconnects due to cell loading/breathing.
Probably worth considering an outdoor gain type antenna.

Good - Values between 14 and 19.
Normally no problem holding a connection with this sort of level (even with cell breathing).

Excellent - Values above 19.
Should not be affected by cell breathing/loading.

 

In some special cases an adaption of the initialization strings used by modem FBox library are required. This FAQ explains the necessary steps for such an adaption.

 

For adapting the strings which are used for a specific modem (by an FBox), the file "modmbase.dat" is to be adapted. The procedure explained in this FAQ involves copying the file "modmbase.dat" into the "CPU directory". By doing so, the modification does only apply for the CPU but not for all programs (with the advantage that the modification will not be removed the next time the Modem FBox library is installed).

• Add the file "modmbase.dat" to the CPU in the PG5 project (right-click the folder "Program Files" and select "Add Files...").
  
• Browse th the file "modmbase.dat" which can be found in the folder:
  c:\Program Files\SAIA-Burgess\PG5 1_4\Libs\App\modmbase.dat
  
  Note that you have to select "All files *.*" as "File Type"
• Once the file is added to the project, open it by double-clicking it (note that this file shall not be "linked" but only present).
  
  It may be that the ".dat" files are not associated to a program; in this case, select "Notepad.exe" as program for opening the modmbase.dat which is a text file.
• Search the section which defines the strings for your modem (the Q.M716-KS1 in this example):
  
  Select the section beginning with the line after "$elseif..." until the last line before "$elseif..." and copy it into the clipboard.
• Search the section [User 1] and replace the section starting below ;; [User 1] until the last line before the next "$elseif..." with the content of the clipboard (the string definition for the modem to be edited).
  
• Edit the string which you want to change:
  
• Save and close the file "modmbase.dat"
• In the modem driver FBox (Modem 18), select the modem type "User 1" instead of the original one:
  
• Save and rebuild your PG5 project.

Remark
If the file "modmbase.dat" which is stored in the FBox library folder (c:\Program Files\SAIA-Burgess\PG5 1_4\Libs\App\modmbase.dat) is modified, this procedure will principally also work. But please note that the next time the FBox library is installed (or its language is changed), the modified file will be overwritten with the original one.

 

In the adust window of the FBox "Call SMS" the actual- and the "last end"-status of the SMS transmission is shown if PG5 is online with the PCD. These states are directly shown as string for better readability. This FAQ contains the according values of the register in the PCD.

 

 

When visualizing this status on a SCADA system such as Visi.Plus, the translation form the read value to the according string must be done. The tables below shows the possible values and their meanings (strings):

 

"Last End" status of "Call SMS" FBox

	Value	String
	0	Standby
	4	Error
	5	Lost
	6	Abort
	9	End
	20	End OK
	21	Error Code
	22	End No OK

 

"Actual Status" of "Call SMS" FBox

	Value	String
	0	Standby
	2	Connect
	4	Error
	5	Lost
	6	Abort
	9	End
	19	Waiting
	40	Command
	322	Call SMS
	800	Call
	900	Aborted

 

 

The modem library offers the possibility to use the modem for an online connection and alternatively for giving commands using DTMF. In this case the PCD has to decide whether the incoming call is a data call (for an online connection) or a voice call (for the DTMF driver). The switching between those call types may cause some problems, depending on the quality of the signal that is transmitted (sent) by the calling modem.

 

Symptom
If the modem default standby mode in the Modem 14 FBox is set to "DTMF+PGU", no online connection is possible any more. Instead, the PCD does activate the DTMF driver also when trying to go online with PG5.

Reason
In versions of the modem library delivered before PG5 1.3.120, the decision for the switching was made based on a carrier frequency transmitted by the modem.
This method seems to be depending on varoius influences such as the level of the carrier frequency of both of the involved modems, line quality etc.

Solution
Since the old method failed in some cases, a new option was introduced:
Instead of configuring the default modem mode for a voice call (and then listening for a data carrier frequency), the default mode can be switched to data mode (and after a timeout, the mode will be switched to voice for the dtmf driver).
This new mode is activated by entering an "Additional Build Option" in the Software settings of the CPU in the PG5 project:

The string to be entered is:
/D._MODEM._OPTION._DEFAULTDATA0

In this example the modem channel is Port 0 (DEFAULTDATA0). If an other channel is used the string has to be adapted. For Port 1 (DEFAULTDATA1)

Important: Since the PGU Mode is now forced, the modem will automaticaly make a PGU connection after 10sec. if the DTMF Mode is not forced. To force the DTMF mode enter *# while this 10sec. Otherwise no DTMF commandes are accepted.

 

If an incomplete SMS message text is received, perhaps the necessary delimiter character is wrongly choosed or not set at all.

 

As descripted within the online help for the Modem Library, every SMS message text must be enclosed by a delimiter character:

 

"The message must be marked by delimiters. A character set at beginning and at the end of the message, can be freely selected by the user except some characters reserved for the assembler ( $ @ and " )."

If no delimiter is used at all, a text defined like "Attention! Attic temperature too high!" will be truncated at the second 'A' and the first 'A' is suppressed. So only "ttention! " is transmitted by the Send SMS FBox. The message with ampersands ('&') used as delimiters - "&Attention! Attic temperature too high!&" - will be transmitted completely.

The delimiter character should be choosed carefully, since it must not appear in the message text itself. Otherwise the message will be truncated at this position.

 

In the adust window of the FBox "Modem Driver 14" the status of the modem is shown if PG5 is online with the PCD. The modem status is directly shown as string for better readability. This FAQ contains the according values of the register in the PCD.

 

When visualizing this status on a SCADA system such as Visi.Plus, the translation form the read value to the according string must be done. The table below shows the possible values and their meanings (strings):

Value	String	Value	String
0	Standby	34	Blacklisted
1	Dialing	40	Ring
2	Connect	80	ICC Voice
3	HangUp	81	ICC DATA
4	Error	82	DTMF
5	Lost	90	Init
7	Executed	91	Init MSN
10	Go in AA	92	Load PIN
11	Incoming	94	Life check
12	Assigning	95	No Modem
13	PGU Used	97	HW-Reset
30	Busy	99	Fatal Error
32	No Dialtone	190	Abort
33	No Carrier

SMS can't be sent, the Call SMS Fbox gives an error: End No OK and also Last end Status = Error Code, Last error Code = 96.

 

This error comes when the server number has no land prefix. For Switzerland it has to be +41 79 4999 000 and not only 079 4999 000!

 

 

The FBoxes of the Modem- or Heavac-library (HVC, CVC or HLK FBoxes) must be placed in a cyclically called program block (but not in an XOB or SB!). The reason for this restriction is the initialisation procedure and the internal code structure of the libraries.

 

Since the initialisation of the adjust parameters of the FBoxes is done in the first program cycle, the concerned FBox must be processed while this program cycle.

A further point to be considered it the fact that some of the FBoxes do need several program cycles until their task is processed (e.g. FBoxes for reading analogue input values do only process one channel per program cycle).

As result of those facts it is absolutely necessary that the FBoxes of the HVC and Modem library are processed cyclically in an COB. Also a permanently called FB or PB is possible.
It is not allowed to place FBoxes of the HVC or Modem library in a XOB or in an SB! If they are placed in a XOB the initialisation isn't guaranteed; if they are placed in a SB the code of the FBoxes don't work correctly.

 

During the year 2003 SBC has delivered PCD2.T813Z42 modems. This is also an analogue modem like the PCD2.T813. The differrence is that the PCD2.T813Z42 in fact is a 56k modem while the PCD2.T813 is a 33.6k modem.

 

In the hardware settings only the type PCD8.T813 is available. This selection also fits when using the PCD2.T813Z42.

 

For using the modems with the modem FBox library both types can be configured in the "Modem 14" FBox.
The main difference between the AT commands of the two types is the handling of the DTMF commands. Therfore it is important to select the correct type in the "Modem 14" FBox when using the DTMF driver FBox. 
In case the modem only is used for going online and DTMF isn't used, it doesn't make a difference which  modem is selected in the "Modem 14" FBox.

 

By using the filed "confirmation option" you can define the behaviour of the PCD for received SMS.

 

There is the possibility that the PCD does send back a confirmation SMS for each received SMS. On this confirmation SMS you will see if the received DTMF instruction was performed correctly or not.

How to activate?
To activate the confirmation SMS you have to choice the filed "confirmation option" on the FBox "Poll SMS".

• If you select the option "Replay" then the confirmation SMS will be send back to the originator of the SMS.
• If you select the option "Destination" then the confirmation SMS will be send to the to the defined destination number.

Remark
Don't forget to set the FBox input "EnR" (Enable Reply) to 1 to enable this option.

 

The GSM standard does not support the receiption of DTMF tones by a GSM modem. This means that it isn't possible to send DTMF tones to a PCD which is equipped with a GSM modem.

 

Can a GSM modem (terminal) receive DTMF tones?
It's not possible to receive DTMF tones with a GSM modem (mounted on a PCD). This is due to the fact that the GSM standard doesn't support the reception of DTMF tones on a GSM modem.

 

Can I still have a similar functionality when I use a GSM terminal?
If you want to have the DTMF funcionaltiy (set binary/numeric values on the PCD or know the status of binary/numeric values of the PCD) on a PCD equipped with GSM modem then you can take advantage of the SMS service:
You can send a SMS message containing DTMF commands to the PCD (in the same way as you would use the phone keys for the DTMF). The PCD then can respond with a SMS to e.g. the originator of the command (for the acknowledgement of the command).

How can I realize that?
On the PCD you have use the FBox "PollSMS" to receive the SMS and the FBox "DTMF Driver" and "DTMF user xy" to handle the text on the received SMS. For further information please refer to the example available in the "Getting started" area of the support site www.sbc-support.ch and to the online help of the relevant FBoxes.

 

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

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

Edit Station, Channel List, Header

 

 

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

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

 

Wiring and Network termination should be as follows:

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

§ix100234§

<dir><dir>

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

ERNI Elektrotechnik AG, Brüttisellen, Switzerland:

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

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

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

</dir></dir> 

§ix100228§
ERNI ERbic connector

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

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

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

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

 

The first document describes the configuration between UNIGYR PRU and PCD2

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

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

 

 

 

 

   for more Help or application support you can connect:

   A&P Kieffer Omnitec Sàrl

   59, avenue Pasteur / BP 317

   L-2013 Luxembourg

   Tel.:  (+352) 474848-258

   Mail: martin.theis@kiffer-omnitec.lu

 

 

 

 

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

 

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

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

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

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

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

Profibus and Profi-S-I/O 

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

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

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

 

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

 

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


Signification of each bit (from right to left):

 

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

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

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

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

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

Remarks

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

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

 

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

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

 

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

 

The significations of the registers are the following:

Output registers: 

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

Description of the output registers:

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

Input registers:

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

Description of the input registers:

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

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

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

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

Table module status:

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

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

Status Input:  

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

Table input status:

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

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

Status Output:      

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

Table output status:

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

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

RUN = Yellow

ERROR = Red

 

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



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

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

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

 

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

 

Important points when commissioning the 6ES7

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

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

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

 

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

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

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

 

The configuration of the two devices has to match.

 

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

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

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

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

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

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

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

 

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

 

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

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

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

FW versions < 1.24d could have this problem. 

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

 

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

 

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

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

Solution
Please update the firmware of your

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

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

 

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

 

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

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

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

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

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

 

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

 

    

 

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

Rebuild and download also all programs.

 

 

 

 

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

 

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

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

 

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

 

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

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

Solution

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

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

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

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

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

 

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

 

 

 

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

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

 

Wiring and Network termination should be as follows:

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

§ix100234§

<dir><dir>

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

ERNI Elektrotechnik AG, Brüttisellen, Switzerland:

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

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

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

</dir></dir> 

§ix100228§
ERNI ERbic connector

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

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

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

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

 

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

 

The PCD2.M480 does support the following baudrates:

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

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

 

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

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

Solution

• Either update to the latest official FW for the PCD2

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

 

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

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

• a protocol analyzer specialized for Profibus based networks

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

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

 

 

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

doesen’t refresh automatically the diagnostic flags and registers.

 

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

 

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

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

 

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

 

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

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

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

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

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

Yes, it's possible.

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

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

 

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

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

 

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

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

 

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

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

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

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

 

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

 

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

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

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

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

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

Profibus and Profi-S-I/O 

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

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

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

 

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

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

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

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

We regret any inconvenience caused.

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

Update on 08.04.2020:

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

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

 

 

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

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

Introduction

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

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

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

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

---

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

---

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

Fupla:

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

  
  

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

  
  

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

  
  

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

 

Web-Editor8:

• Generation of HTML 5 compatible web pages

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

 

Improvements:

Device Configurator:

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

 

FBox libraries

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

  
  

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

  
  

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

  
  

DDC Suite

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

And other improvements and bug fixes

---

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

Windows Start menu

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

Device configurator:

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

Fupla:

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

Web templates and Web Editor 8:

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

Wiring Check Tool:

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

---

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

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

And other improvements and bug fixes

---

New features of PG5 2.1.310

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

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

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

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

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

And other corrections.

---

New features of PG5 2.1.300

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

And some other improvements and bug fixes

---

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

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

And some other improvements and bug fixes

---

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

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

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

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

---

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

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

 

---

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

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

 

---

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

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

---

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

• Support of the PCD1.M2160

---

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

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

---

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

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

 

---

New features of PG5 2.0.110 (first official release)

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

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

The new features in detail

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

 

---

Restrictions of PG5 2.0 and PG5 2.1

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

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

Even if this is not tested and guaranteed anymore many customers managed to install PG5 1.4 on their Windows 10 PC’s but there is a problem with licensing.

Symptoms

The installation path has to be adapted according the following document:

https://www.sbc-support.com/uploads/tx_srcproducts/Installation_Guide_PG5_1.4.300_on_Win7(64Bit)_V3.pdf

Many customers have problems to register the user.key with the function Help -> Register Software

The following message might be returned:

“Failed to update registry (ID1)”

Reason

The function is not executed due to missing administration rights.

Solution

At least for doing the operation of registering the user.key, PG5 1.4 should by started with right mouse click -> run as administrator.
After this operation, you can start PG5 the usual way.

If you install PG5 1.4 on a Windows 8 PC, then the PGU Port is not anymore visible in the online settings of PG5.

 

This is a problem in relation with the access rights of Windows8.

Solution:
PG5 1.4 has to be launched as administrator.
To start PG5 1.4 as administrator:
- Create a new short cut to the application 'PG5 1.4 project manager 'and 'run it as administrator'
or
- Browse to the installation folder of PG5 1.4 and there choose the file 'Spm.exe' and 'run it as administrator'

After this the PGU port is visible again in the online settings.

 

This error message can occur for example when you move in the symbol editor of Fupla the symbol folder of one DDC Suite FBox to another folder.

 

This problem is because the Antivirus Software McAfee blocks the access to these files. To solve the problem you have to deactivate these three services in the system panel under Maintenance->Services.

 

Sometimes Network administrators ask for the MAC address of PCD devices with Ethernet connections for setting up their network devices.

There is a sticker at the backside of the PCD that indicates the MAC address but if you aren't on site this isn't helpful.

 

With older version of PG5 1.4 and with PG5 2.0.220 and newer it is possible to check the address in the Online Configurator with the button information. This works for PCD1.M2120, PCD2.M5540 and all PCD3.Mxxxx with Ethernet connection. In PG5 1.4.301.15 the field MAC address remains empty.

There is another way to get the MAC address of a PCD with Ethernet connection.
Open the Online Debugger and enter D for Display and S for CPU-Status. This works for PCD1.M2120, PCD2.M5540 and all PCD3.Mxxxx with Ethernet connection




Remark:

There is a more general way to find the MAC address of any intelligent network device with the help of the ARP protocol.
It's also the only possible way to to find the MAC address of "not NT PCD's" (PCD1.M1, PCD2.M1, PCD4 and PCD6) devices that are equiped with a PCD7.F655 Ethernet module.
With Microsoft Windows NT 4.0 or newer you can open a cmd-Window and execute the 2 following commands:
ping ip-address_of_device
-> There must be a relpy from the device
arp -g ip-address_of_device
-> the MAC address of the device will be displayed

 

This error occurs only on PCs equipped with Win7 64 bit and PG5 1.4 where the hardwaer configuration is done with the help of the Device Configurator.

 

 

Reason
On such PCs it isn't possible to download the hardware configuration directly from the device configurator since each time the error message "downloader not found (-1)" is displayed.

Solution
To load the HW configuration on concerned PCs please execute the following steps:

• Define your configuration as needed in the Device Configurator
• Save the configuration and close the Device Configurator
• In the PG5 1.4 Project Manager select the menu "Online" --> "Hardware Settings" --> "Download" and click to the download button on the opening window.

It could happen sometimes that you can no more Build your project in your project done with the PG5 1.4.300.

 

Symptom:




Reported message:
SAIA_ASSERT failed at line 1843 in D:\work\source\PG5_1_4\Sfup32\Sfupcomp.cpp: Value==0 || Value == 1


Reason: 
In fupla editor some connectors can look like beeing empty but when you click on it/them it obviously contains a invisible "SPACE" char.


Solution:
Delete all these unwished "SPACE" chars and make a REBUILD ALL FILES in PG5

 

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

 

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

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

PG5 1.4: (Windows XP) 

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

PG5 2.0: (Windows XP)

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

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

 

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

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

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

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

 

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.

 

This error is displayed on the project manger of PG5 after compilation if the user does define a text with the text address 0 in the application program.

To solve the problem, change the address of the text 0 to a different address >0.

 

 

While older patches for PG5 1.4 required post-installation steps (lauching an executable after the installer for the patch has finished) this is no longer necessary for patch 10 and later. In order to install patch 11 for PG5 1.4.300, just launch it.

 

FAQ Update
For installing patch 10 it is sufficient to launch the patch 10; no additional steps are required!

Remarks

• This FAQ previously has been called "How to install the "Patch 9" for PG5 1.4.300?" and has been updated September 21 2009 due to the availability of patch 10 which does no longer require to execute post-instllation steps.
• This FAQ previously has been called "How to install the "Patch 8" for PG5 1.4.300?" and has been updated August 11 2009 due to the availability of the patch 9. For installing patch 8, a *.bat file had to be called instead of launching *.exe files.
  

Due to an error in the "Online debugger" from PG5 version 1.4 texts with a size of 16 characters are not displayed on the screen.

 

Symptom
Due to an error in the "Online debugger" from PG5 version 1.4 texts with a size of 16 characters are not displayed on the screen. (Instruction "display text xxxx".)
 
Solution
The error is fixed on the version 1.4.301.3 of the debugger. This version is supplied together with the patch 8 of PG5 version 1.4.300

 

This is usually the case if you are not connected in full protocol.

 

Problem
It is possible to go online in Fupla and the FBoxes indicate there status, but the "RUN" and "STOP" buttons are inactive.


Reason
This is usually the case if your connection is not a full protocol conection. Per example you are online over TCP/IP and TCP/IP is not configured as PGU line in the hardware settings.


Solution
Change your online connection to PGU in the hardware settings and make a download of the hardware settings. Afterwards the problem should be solved.

 

To access a RS 485 network from a PC / Notebook a converter is needed.

 

Problem
Since most notebooks do not have a serial port the PCD7.T120 (RS232-RS485 converter) cannot be used anymore. It is not possible to have a USB-RS 232 converter and afterwards the PCD7.T120 this will not work.

Solution
We successfully tested the following USB - RS 485 converter:

• Moxa UPort 1130. It works well with PG5 1.4 and PG5 2.0 on Windows XP and Windows Vista. 
• ICP DAS I-7561. It works fine with PG5 1.4 and PG5 2.0 on Windows XP SP2 or higher.
   

Important
Please note that the converter from ICP DAS only works for USB - RS 485. The USB - RS 232 option does not work properly.

 

It is possible storing the PG5 project directly onto the PCD in case there is a flash file system available (e.g. on the PCD3.R600). This strategy offers the advantage that the last version of the project can always be stored directly on site.

 

How to backup the PG5 Project (or the CPU of the project) on the PCD?
PG5 1.4.300 offers a feature which creates a beckup, connects to the PCD using the FTP protocol (given an Ethernet connection is existing) and stores the project on the file system of the PCD.

• In the PG5 Project Manager menu "Online" --> "Flash Memory" select the function "Backup File to Flash..."
   
• Select the CPU you want to backup (by default only a CPU but not the whole Project is pre-selected for saving some space on the file system). PG5 will then create a backup file (*.zip)
  
• In the automatically opened Window "Backup File to Flash", verify the IP address of the PCD. The default user is as always "root" and the default password is "rootpasswd"
  
• If required, browse to the folder on the PCD file system where you want to store your PG5 project backup file
  
• After selecting the target folder, click "OK" and wait until the file transfer has completed
  
• Verify whether the transfer finished without errors.
  

Remark
This feature is not the same as the "Backup user program to flash" which does store the content of the SRAM (user program, DBs etc.) of the PCD to its onboard flash. A "Backup user program to flash" only contains the compiled PCD code but not the source files (Fupla etc.). The "Backup user program to flash" can not be seen in the file system. 

 

The configuration of the two devices has to match.

 

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

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

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

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

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

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

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

 

If a new FBox library is installed in the default PG5 path, they won't be available in a DDC Suite project, because in this case, the FBox libraries are part of the project itself.

 

Problem
A new FBox library or a bugfix library was installed to the default PG5 path. These FBoxes are still not available in a DDC suite project.

Reason
The reason for this behaviour is, that in a DDC Suite Project, all FBoxes are stored local in the project. Under Settings/Software/Directories the option "Use Library override directories" is checked.

Solution
To make the FBoxes available in the DDC suite project, they have to be installed once more into the DDC suite project. In the project directory there is a folder FBoxes available. New FBoxes have to be copied/installed into this folder to make them available for the project.

 

This error appears if the first symbol of an array has a "first time data initialisation".

 

Problem
An array is defined in the symbol table:

Group/Symbol	Type	address/value
Symbol0	Register	[3]
Symbol1	Register	Symbol0+1
Symbol2	Register	Symbol0+2

If the first symbol of the array has a "first time data initialisation" the following error appears:
Error 212: Untitled1.sy5: Line 4: Missing initialisers

Group/Symbol	Type	address/value
Symbol0	Register	[3] :=0
Symbol1	Register	Symbol0+1 :=1
Symbol2	Register	Symbol0+2 :=2

Solution
At the moment the only solution is, to define the whole array in the first symbol or to realize the first time data initialisation elsewhere, per example in the XOB 16.

Group/Symbol	Type	address/value
Symbol0	Register	[3] :=0,1,2
Symbol1	Register	Symbol0+1
Symbol2	Register	Symbol0+2

In future versions of PG5 a better solution is planed.

 

Due to some problems of timing with the processor Dual Core from AMD the scommdll don't work properly. Some errors messages occur during the download and the download fails.

 

To solve this problem, there is a soft "AMD Dual-Core Optimizer" available under this link:
support.amd.com/fr/Pages/dynamicDetails.aspx

There is also a soft from Microsoft that increases the performance of a PC with multiple processors using Windows XP SP2. It is available under this link: support.microsoft.com/kb/896256/en-us

 

If the currently installed license key is to be replaced (e.g. for using a demo version of an FBox library), a backup of the installed user.key file is very handy.

 

Introduction
While installing a new license key for PG5 (by using the function "Register software" in the "Help" menu of PG5 Project Manager), the previous version of the license is overwritten. In case a license shall onyl be registered temporarily, it makes sense backing up the original license which shall be re-registered later on.

Procedure for backing-up the currently installed license

• Browse to the installation path of your PG5 (by default this is c:\Program Files\SAIA-Burgess\PG5_1_4\)
• Locate the file "user.key"
• Copy this file to some temporary direction (e.g. c:\temp).
• Register your new license (from PG5 Project Manager menu "Help" --> "Register Software")
• If you need to re-register your previous license, again register your PG5, but this time select the "user.key" you have backed-up in the temporary folder (e.g. c:\temp).

Hint
In case you often need to change the license of PG5, you can also give your different key files some meaningful names (e.g. "user_MyCompany.key", "user_LibraryDemo.key" etc.) and store them directly in the PG5 installation directory.
Every time you need to register one of these licenses, you can then just select the according file when browsing for a new key file.

 

When updating a PG5 project to PG5 1.4, around 50 more registers and flags are used. In very rare cases, this can lead to a "Dynamic space overflow" (if less than 50 flags or registers have been available in the project from PG5 1.3).

 

Symptom
After updating a PG5 project containing Fupla from e.g. PG5 1.3 to PG5 1.4, about 50 registers and flags are used in addition. This can lead to a "Dynamic space overflow" error as shown below:

Linking: _CPU1.obj + cob0.obj + _Global.obj + _TCPIPDBX.obj
To: CPU1.pcd CPU1.map
Fatal Error 368: Dynamic space overflow for type: R

Reason
In PG5 1.4, the "Synchronous Data View" has been implemented first time. This online mode avoids the situation that wrong values of the connector lines between FBoxes are temporarily shown when probes are set. Due to the implementation of the "Synchronous Data View", around 50 more registers and flags are used for organizing the correct visualisation of Fupla pages in the online mode.

Solution
As the "Synchronous Data View" can not be disabled (because at build time it is not defined whether the user will use the Synchronous Data View), the additional registers are to be freed or made available in the PG5 project. The easyest ways to do so is:

• Executing a "Clean files" which will release addresses that have been used once but are no longer needed (e.g. because symbols have been deleted). The "Clean files..." can be found in the PG5 Project Manager menu "CPU":
  
• Increasing the "Dynamic Space" for the relevant medias in the Software Settings of the CPU.
• Using statically addressed registers in the range from 4095 to 16838 if a Saia PCD® COSinus system such as the PCD3, PCD2.M5xx0 or a PCD2.M480).
• If several Fupla files with a "Heavac Init" FBox are used, some of its common medias can be shared. Therefore, select in the section "Valitity scope" the option "Global" (for all, "Sampling", "Reset" and "General alarm") in the first of your Fupla files, and in all other Fupla files select "External" in the parameters mentioned above.
• Reducing the used register by optimizing the program if the above possibilities do not help or can not be applied.

The project could be compiled in PG5 1.4.200 without any error. In PG5 1.4.300 an error appears and it is not possible to compile it anymore.

 

Problem
After a update from PG5 1.4.200 to 1.4.300 the program cannot be compiled anymore. The error 41: Multi defined symbol appears.

Reason
This can happen because PG5 1.4.300 is a bit more restrictive than PG5 1.4.200. If the addressing of symbols has been realised as explained below this error will appear on build:

Symbol       Address
Register1    Register2
Register2    Reg3+3

Solution
It will work again if the definition of Register2 is moved up.

Symbol       Address
Register2    Reg3+3
Register1    Register2

If you need an urgent fix ask the support team for a bugfix. The next patch or the next version of PG5 will contain this correction.

 

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

 

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

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

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


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

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

 

The download seems to start but blocks imediatly. The task has to be killed by the task manager.

 

Problem
It was possible since PG3 downloading just one block per example COB 0 with the debugger (File Load filename.pcd COB 0). This was often used for IL projects, as the possibility to download just the changed blocks was not available. In PG5 <=1.4.300 this function did not work anymore.

Solution
This problem is fixed in Patch 5 for PG5 1.4.300. You can either install this patch or use the download changed blocks option instead of the debugger as workaround.

 

With PG5 1.4.300 this error appears on some PC's.

 

Problem
After installing PG5 1.4.300 the Error message: "Error 160: Replaced macro _ENERH104S is not part of a family definition" appears.

Solution
Install the SfupBase_SP25300 again. It can be found on your installation CD (CDImage\Fbox libs\C\)

 

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.

 

 

 

With PG5 1.4.300 the backup routine in PG5 has changed

 

New:
The new backup routine is not creating a backup of the project by default, but a backup only of the selected CPU. To backup the project as it was before you have to change manually to project.


Reason:
The reason for this change is that it is now possible to backup the CPU / Project to your flash card per example to a PCD7.R550. Since on these cards the space is limited to 4MBytes (or 3MBytes) it would in most cases fail to backup the whole project to the card.

Important:
Note that you have to activate the backup of S-Net device files and plugins manually. It is never activated by default.
When creating a backup to the flashcard it is better to choose: "All files except listings and docs" than "All files" to save place on the flash card.

 

It could happen that an error occures when installing the Patch 1 for PG5 1.4.300

 

Problem
When installing the Patch 1 for PG5 1.4.300 the following error occurs:
"Copy Operation Failed on directory : C:\Program Files\SAIA-Burgess\ PG5 1_4\: Error" 


Reason
One or more of the files to be copied is/are write protected because PG5 is open or the S-Driver is running or for some other reasons.

Solution
Extract the Patch with WinZip (right-mouseklick on the file and choose "Extract to...") and copy the files manualy to C:/Program Files/SAIA-Burgess/PG5 1_4

 

 

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

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

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

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

PG5 does not change the TAPI settings of Windows.

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



 

PG5 does apply the following rules:

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

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

 

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

 

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


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

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

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

 

Is it possible to use the PGU port for programming and communication?

 

Problem
Generally the PGU port can be used for programming and communication (per example with a display). If the PGU cable is connected, the PCD is automatically switching to programming mode. Otherwise if the cable is disconnected, the communication does not start again. The PCD has to be switched off.

Solution
The PCD should switch back to the communication mode as soon as the PGU cable is unplugged. It should not be necessary to power off/on the PCD. This can be realized with a short program. The command SICL is checking if the DSR signal PIN 6 is high:
SICL   0                   ; Serial port number=0
         1                   ; DSR(data set ready) signal=1
In a graftec program per example the status of port 0 can be checked and as soon as the PG5 is offline the port can be reasigned.

Example project is attached to this FAQ

 

Updating the program/configuration of a PCD does not necessarily require the whole PG5 installation. By the use of the "S-Online Tools" and the functionality "Create Self-downloading file", a PCD can be updated without having a full PG5 installation on the PC.

 

Introduction
It is possible just installing the "S-Online Tools" which provide the necessary driver and interface to download the configuration and the user program files to a PCD. PG5 itself supports the functionality "Create Self-Downloading File" which creates one file containing configuration, program files etc. that can be to someone having installed the "S-Online Tools" (e.g. an end customer).

Usage
Given an end customer needs to update the user program of his CPU (and this customer shall not get the source program files (Fupla etc.) of the software his PCD is running). The easyest way to provide the configuration and the program files (compiled) to such a customer is executing the following steps:

• From PG5 Project Manager menu "CPU", select the functionality "Create Self-Downloading File". Select the parts of the project you want to change (HW settings, user program, ) and maybe other useful tasks (e.g. Set PCD Clock from PC, BAckup User Program to Flash etc.).
  A file with the extentsion "*.sd5" is generated.
• Send this ".sd5" file to your customer
• Ask your customer to install the "S-Online Tools" which can be found on the PG5 Controls Suite CD in the folder "S-Online Tools" or from the support site (section "Product Info"-->"Software"-->"PG5").
  No license is required for installing or running run the "S-Online Tools".
• Ask your customer to launch the *.sd5 file (of course he also needs to connect the PCD to the PC using a suitable connection, e.g. USB or PGU cable PCD8.K111).

Remark
The S-Online Tools do also support command line options. So you can also write an own script for using the according tools on the end-customer's PC.

Important note
The installer of the "S-Online Tools" that has been available on the support page between 07.02.2008 and 13.02.2008 did not install all necessary files. In case you have downloaded the "S-Online Tools" in this period, please re-download and re-install them.

 

In case that two IP addresses are assigned to the same Ethernet card (Ethernet port) on a PC, it is possible that the communication does only work on one of the two IP addresses. This problem is caused by the operating system (Windows XP) and is due to insufficient buffers.

 

Symptom
Only one Ether-S-Bus communication is working if there are two addresses assigned to the same Ethernet interface on the PC (running Windows XP or W2k). A tracewin log indicates the error message:
Error Message 10055 (WSAENOBUFS)

Reason (according to microsoft support)
An operation on a socket could not be performed because the system lacked sufficient buffer space or because a queue was full (as the SBC driver is concerned because it is using TCP port 7000 to communicate with its dll). Please refer to the microsoft support page (link below) for furhter information.

Solution
Please refer to the link below (pointing to the microsoft support site, as this is a problem of Windows and not from PG5).

 

After a crash of installshield, we can sometimes no more install or uninstall PG5 version.

When this happens, it is a big problem. It can only be solved by deleting the following windows registery keys:

 

 

    

After having installed PG5 1.4.200 it is possible that the build of a project (created with a former version of PG5) fails due to an object file error or an error indicating incompatible data types.

 

Problem
PG5 1.4.200 is not able to finish a build due to an error related to a "TFRtype". Below there are two possible messages:

In order to simplify the interpretation of firmware versions and to avoid confusion regarding implemented features and bug fixes in different firmware versions, a new firmware version format for Saia PCD® COSinus based systems will be introduced.

 

Arguments for the new format
The new firmware version naming allows a clear and easy comparison between the different versions and their implemented features (PCD type specific) and bug fixes.
Questions like "Why is the Alarming functionality of the PCD3 Web Server implemented in firmware version $31 but not in version 031? - They both do have the same number..." should be past (however, if you're interested in the answer, please refer to FAQ100176)

Format description
The new firmware version name does consist of a major version, a branch version and a minor version separated by a dot (.).
Note that the prefix characters “0”, “$” or “#” are no longer used in this notation.

Concerned systems
The new firmware version format is applied to the systems based on Saia PCD® COSinus firmware (Classic and xx7). These are

 

• PCD1.M2xxx
• PCD2.M48x
• PCD2.M5xxx
• PCD3.Mxxxx
• PCD7.D4xx (MB Panels)

While the firmware names for the MB Panels and PCD1.M2xxx do have this format from beginning, it was introduced on the PCD3 and PCD2.M480 systems with the firmware version after 03B.

Version flow example
Below an example for a version flow. If e.g. a bug is corrected in the version 1.06.01, also version 1.07.02 and all following 1.06.xx versions do/will have this correction implemented.


Version types

• Released beta- or maintenance versions (equivalent to the current “Bxx” or “#xx” versions).
• Released Production versions (equivalent to the current “0xx” versions): These versions are introduced in the production.
• New function versions (equivalent to the current “$xx” versions).

Compatibility with PG5
The new firmware names are fully supported by PG5 V 1.4.200:

Previous versions of PG5 will only show the first three digits of the firmware version (e.g. “106” instead of “1.06.08”). The full firmware version can always be read by displaying byte F0F0 in the “Online Debugger” (type DYF0F0 ):

Yes, PG5 1.4 is compatible with Microsoft Windows Vista , Windows Server 2008, Windows 7 and Windows 8 (with the exception that the BACnet Configurator is only supporting the 32bit versions of the above mentioned Operating Systems). But there are some special points to consider for the installation of PG5 1.4 as Windows Vista / Server 2008 / 7 / 8 is more restrictive (compared to e.g. Windows XP) regarding the write access during the installation.

 

Installation procedure
For a detailled report regarding the found issues during the intallation of PG5 1.4 under Windows Vista, Windows 7 and Windows 8 and the procedure to correctly install PG5, please refer to the PG5 section on the support site.
You can find the link to the PG5 section below.

Remark regarding 64-bit version of Vista, Windows 7 and Windows 8


The PG5 1.4.300 was developed before Windows 7 or Vista have been available. In order to use PG5 1.4 on these operating systems, the USB driver needs to be updated (explained in detail in the attached document).

• The BACnet Configurator from PG5 1.4 is not compatible to the 64bit version of Windows7

FAQ update (March 2012)

• The BACnet Configurator from PG5 1.4 is not compatible to the 64bit version of Windows7

FAQ update (January 2011)

• A step by step installation guide can now be found attached to this FAQ (updated January 2011). 
• A new USB driver compatible with the 64 bit version of Vista / Windows 7 has been developed. This new USB driver can be downloaded from the support site (from the PG5 1.4 Suite section).
• Internal tests have shown that for installing PG5 1.4 300 on a Windows Server 2008 the same operations have to be followed as for an installation on Windows Vista. 

While beeing online to a PCD with PG5 (with USB) and the USB cable is disconnected from the PCD, it may happen that the SBus driver running on the PC crashes. On some PC's also blue screens related to this problem were reported!

 

Symptom
The SCommDll (S-Bus driver on the PC) crashes if the USB cable that connects a PCD is unplugged while beeing online. The crash of the SCommDll can even lead to a blue screen on the PC.

Reason
This problem is caused by a bug in the SBC communication driver.

Solution
Install the attached patch by starting the attached installerfile (patch for PG5 1.4 130) which will update the SCommDll! This patch is solely intended for PG5 1.4.130 installations. In case you experience the above described problem with PG5 1.4.110 or 120, you need to update to PG5 1.4 130 before applying the patch!

Note
For more infos, please read the setup dialog readme after the installation, which is located in PG5 1.4 directory

 

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

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

 

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

 

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

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

 

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

• Uninstall PG 5 1.4 by using the SetupPG5.exe and choose the option "remove". After having unistalled PG5, reinstall PG5 1.4.130 using the SetupPG5.exe.
• Or, in case you don't want re-installing PG5, you can add the PG5 directories (found in the PG5 menu "Tools"-->"Options..", tab "Directories") as shown below:
  

 

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"

 

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)

 

Due to a bug the PCD diagnostic file cannot be recorded automatically with PG5 1.4 over a modem connection. The attempt to record a file fails due to a timeout and the Online Debugger remains open after the attempt.

This FAQ shows how to record the diagnostic file by calling the appropriate batch file manually.

 

Symptom
The function "Create diagnostic file..." of the PG5 1.4 Online Configurator fails if the PCD is connected over a modem line. The online debugger is opened and prompts for going online but afterwards nothing happens.

 

Reason
There is a bug in the function call that avoids the correct call of the Online Debugger batch file that reads the diagnostic data from the PCD and stores it into a file on the PC.

Solution
The mentioned Online Debugger batch can also be called directly from the Online Debugger. This way the online debugger will create a file named Maillon.txt. This file is stored into the same directory as the batches are stored (by default in C:\Program Files\SAIA-Burgess\PG5 1_4\Batches\).
Procedure for reading the PCD diagnostic file by calling the batch manually:

• Open PG5 and adjust the online parameters for connecting the PCD (over modem)

• Open the Online Debugger ("Online Debug" from the PG5 menu "Tools" or F11)

• In the Online Debugger, type G <Enter> (for Go Online, only if not already online)

• Once the Online Debugger is online, type B L <Enter> (for Batch Load)

• Browse to the PG5 installation directory into the folder Batches (C:\Program Files\SAIA-Burgess\PG5 1_4\Batches\) and select the appropriate batch file (listed below), click "OK"

• In the Online Debugger, type B R <loaded batch name> <Enter> (for Batch Run). For the "loaded batch name" the extension is not required (--> e.g. SRec_D2Mxxx and not SRec_D2Mxxx.dba)

• Wait until the batch has finished and close the connection. The recorded batch file is:
  C:\Program Files\SAIA-Burgess\PG5 1_4\Batches\Maillon.txt

Batch names
There is a dedicated batch file (*.dba) for each family of PCD or PCS. All the batch files for recording diagnostic information do begin with SRec_, followed by the PCD type (e.g. D2 for PCD2 or DxM170 for PCD2.M170 and PCD4.M170).

Warning
Don't run a batch created for another CPU type than really present! This can lead to unwanted results (or even a CPU crash)!

 

The error above appears when opening the project created in PG5 1.3 with PG5 1.4

 

Problem
The error message "Error 4501:Name exists" appears when opening a project created in PG5 1.3 with PG5 1.4. If the symbols are removed the error message disappears

Reason
There is a symbol (p.ex PG) with a name which begins with a space. Spaces are not allowed and PG5 1.4 reacts more sensitive in this case.

Solution
Remove the space from the name and execute a "Clean files"

 

This error message appears when creating a Profibus DP Network and adding a PCD3 Master

 

Problem
When inserting a PCD3 Master in the Profibus-DP Network the error message above is displayed.

Reason
The used PCD3 is probably a PCD3.M5xxx or PCD3.M3xxx. These CPU's can only be Profi S-IO Master and not Profibus-DP Master. Only the PCD3.M6540 can be a DP Master.

Solution
If a PCD3.M5xxx or PCD3.M3xxx has to be implemented in a Profibus-DP Network, the Profi S-IO Master has to be inserted and not the PCD3 Master.

 

See the example below.

 

Is this a bug ?

The error message "Error 1042: File open error..." appears when trying to import a project from PG5 1.3 to PG5 1.4.110.

 

Problem
When importing a project created in PG5 1.3 a similar error message as shown below appears.
S-FUP: Error 1042 : File open error : 'C:\PlsProg\Pg5 1_4\PS3_82_1\PS3_82_1\hoved.fup' file version : 514 created in:  < $1.4.022

 

Reason
This is a bug in PG5 1.4.110 fupla

Solution
Attached to this FAQ you can find a new Sfup.exe. You can insert this file into your PG5 1.4.110 root folder and replace the old one. This will fix the problem.

 

 

Often the memory definition is not correct.

 

Problem
The error message PCD memory write error appears when trying to download

 

Reason
The definition of the memory is propably not correct.
If a PCD3.M3xxx with Hardware version D is used a firmware problem (V023) is probably causing this error.

Solution
In most cases the problem can be solved by:
- Downloading the "Hardware Settings" with checking "Memory allocation..." (unchecked by default) and "S-Bus..."
- Adjust the "Software Settings" by pushing the "Set default" button
- If a PCD3.M3xxx with Hardware Version D and FW 023 is in use, a firmware update is probably necessary.

 

If the FBox "HDLog Init" of the "Historic Data Logging" family is placed and the DB "HD" has a size declaration the error 146 (Multi-defined DB) is shown on build of the PG5 project.

 

Problem
The FBox "HDLog Init" is placed in a fupla file and the DB "HD" (entered on the face of the FBox) has a size declaration. The following error is shown on build:
Error 146: Untitled1.fbd: Line 153: Multi-defined DB, in Block: BL 0, Page: 2, FBox: Initialize

Reason
The DB HD must be declared without a definition in the SymbolEditor !
§ix100372§

Solution
If the definition is disabled the build will be successful.

 

This is a bug in the HEAVAC library.

 

Symptom
Each time when the PCD is restarted the clock of the PCD will be incremented 1 hour. This problem does only occur in the lasth week of the month March. 

 

Reason
This is a bug in the HEAVAC library and the problem appeard after the winter-summertime changing when the "Automatic change" is activated in the HEAVAC Init F-Box.

Solution
This problem is fixed in the FBox "Init 7" of the heavac library. In case the PCD is equipped with an older version of this FBox (e.g. Init 5), this FBox is to be replaced. The "Init 7" FBox that fixes the problem is distributed together with PG5 1.4.110 and later.

 

An error message appears after build, but by clicking on the message PG5 doesn't jump to the page where the problem comes from.

 

Just set the cursor on the error message and push F1. A page which gives information about the error will open.

 

If under Settings/Software/Advanced the option: no "Software Settings" file is activated this error can appear.

 

Problem
A disassembled file without "Software Settings" file generates the following message on build:
Fatal Error 377: No $AUTO declaration for type: R

Reason
In an other file a global symbol with dynamic addressing is present. Even if the file is not linked the global symbol will cause this error.

Solution
Delete the dynamic addressed symbol or work with "Software Settings" file.

 

There are a few known cases where the USB Port didn't work anymore after installing PG5 1.4.100. The error message "Port Not Open" is displayed!

 

Problem
After installing PG5 1.4.1xx, the USB port isn't working with PG5 1.4 nor with PG5 1.3 (where it worked before). Unistalling PG5 1.4 doesn't solve the problem.

 

Solution
In this case it is necessary to uninstall the USB-Driver completly. On your PC browse to Start menu -->  Settings --> Control Panel --> System --> Hardware -->  Device manager and chose  DriverX USB / Saia driver / Uninstall.
Reinstall the USB-Driver which is attached to this FAQ before plugging in the PCD again.

 

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

 

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

 

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

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

 

This functionality is only available on the PCD7.F655 with firmware version 041 or newer. Further on this functionality does only allow the PCD to receive a dynamic IP address but it does not help other devices to access this PCD.

 

What for can the DHCP client functionality of the PCD be used?
The DHCP client functionality does only make sense in case the PCD does only need to send or request data but nobody needs to access it over Ethernet.

 

What for can the DHCP client functionality of the PCD not be used?
For any situation where any device needs to access the PCD autonomously. Once the PCD has received a new IP address, no other device (except of the DHCP server) knows about this IP address and therefore the PCD is not easily accessible by other devices (such as PCs running a Web Browser or other PCDs on the network). 

Reason
As soon as some device needs to access the PCD, this device needs to know the IP address of the PCD. As result, an additional mechanism needs to be implemented that collects and provides the IP addresses of the PCD stations to any other device that looks for the relevant PCD.
At the moment there is no such mechanism available. The services and protocols used by PCs (like NetBIOS, WINS, DNS) for this task are not (yet) supported on the PCD.

 

The reason for the warning is not clear. If a doubleclick on the warning is done it jumps on the first fupla page without indicating where the problem comes from

 

Problem
On build a warning as below appears:

Warning 11: Regelung.fbd: Line 10: Fupla block symbol not defined, in ';; Block:': Fupla file needs re-compile

Reason
PG5 1.3.120 checks if all COB's have a name. If COB 0 per example has no symbol name, this warning will appear.

Solution
This warning will no more appear in newer PG5 versions. You can either give a name to COB 0 or ignore the message since it won't generate any problems in your project.

 

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

 

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

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

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

 

The message: "The program contains features which will not run on this PCD..." appears when trying to download after a successful build.

 

Problem
After a successful build the following error message appears on download.
§ix100316§

Reason
If the program contains functions which are not supported this error appars on download. Often the problem is related to F-Boxes which work only on the PCS1 and a PCD2 is choosen as PCD-type. Maybe the program was once created for a PCS1 and the user forgot to remove these special F-Boxes like "Clock on Supercap"; "CPU LED" etc.

Solution
Remove the F-Boxes or functions which will not work on this PCD type.

 

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.

If View is on "Value" instead of "Symbol" some symbols will be created twice

 

Problem
If View is on "Value" instead of "Symbol" some symbols are created twice by error. The cross referece doesn't get any helpful information

Reason
This is a malfunction of PG 5. It didn't cause any critical problem

Solution
The problem will be fixed in PG5 1.4. When choosing Symbol the symbols will no more be created twice. If you need an urgent fix, ask the support team to send you a bugfix version.

 

If an EPROM of a programm with IP-address is made with PG5 1.3.120 the IP-adresse will not be stored in the EPROM (Hex-File)

 

Problem
A hex file of a programm is created. The hardware settings with IP-address should also be stored in the EPROM. The hex file can be created successfully, otherwise when putting the EPROM on a PCD, the IP-adress is missing

Reason
This is a bug of the current version of PG5 1.3.120

Solution
The problem will be corrected in PG5 1.4. If you need an urgent fix ask the support team to send you the bugfix version PG5 $1.3.127

 

Unfortunately clicking on the error messages doesn't open the page where the problem is.

 

Problem
When building a project with RIO configuration the following error message appears:

Unresolved Externals:
_SFUPCOMM.Channel1._MEDIA in module 1_slave.obj
f_riodiag in module 1_slave.obj
txt_rio in module 1_slave.obj
_SFUPCOMM.Channel1._RCOMMON in module 1_slave.obj
r_riodiag in module 1_slave.obj
_SFUPCOMM.Channel1._ADDR in module 1_slave.obj
r_riodst in module 1_slave.obj
_SFUPCOMM.Channel1._STATION in module 1_slave.obj

Reason
The reason is, that the RIO File is not correctly configured. The corresponding CPU is maybe not selected. If the project was created in PG5 1.4 and afterwards imported in PG5 2.0 the path is not adapted and therefore this error message often appears after the conversion to PG5 2.0

Solution
Open the RIO configurator and click on the master. Choose the associated CPU file (Existing CPU)

Make a rebuild. The error messages will disappear.

 

- rebuilt all

- Assembly complete. Errors: 0 Warnings: 0

- Linkage complete. 0 errors 0 warnings

 

This can be caused a block (COB, PB etc) is defined more than

once in the program. Use Project Manager's 'Data List' view, sort

by block type and address, and see if any block has been defined more than once. This should give a 'multi-defined block' error when the program is built, but in some cases no error is given

and S-Asm creates a PCD file with the same block in it twice. The firmware does not give an error either, it always uses the

last block in the file.

 

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

 

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

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

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

• Fupla

• Graftec

• SEdit

• WebConnect

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

 

The output stays low if it is not a valid value.

 

Problem
The output of a logic operation stays low, even if the condition is true
or
The output to a counter/timer stays 0 even if a value should be transmitted

Reason
If the output accesses a physical address p.ex. O 48, and there is no Digital Output card plugged in this slot, the output value in the program will always stay low.
If the output value for a Timer or Counter is negative p.ex. -1 which is an invalid value for a Timer or Counter the content of the timer or Counter will always stay 0

Solution
Plug a card or map the output to flag instead of a physical address
Write a valid value to the Timer/Counter

 

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

PG5 Version

Win '95

Win '98

Win ME

Win NT

Win 2k

Win XP

Vista

Server 2008

Windows 7

Windows 8

Windows 8.1

Windows 10

Windows 11

1.0.xxx

B or higher

Second Edition

Yes

SP5 or higher

Prof. SP4

No

No

No

No

No

No

No

No

1.1.xxx

B or higher

Second Edition

Yes

SP5 or higher

Prof. SP4

No

No

No

No

No

No

No

No

1.2.xxx

B or higher

Second Edition

Yes

SP5 or higher

Prof. SP4

Yes

No

No

No

No

No

No

No

1.3.xxx

B or higher

Second Edition

Yes

SP5 or higher

Prof. SP4

Yes

No

No

No

No

No

No

No

1.4.300

No

No

No

No

Prof. SP4

Yes

Yes*

Yes*

Yes*, ***

Yes*, ***

No

No

No

2.0.150

No

No

No

No

No

Yes (SP2,SP3)

Yes **

Yes **

Yes **

Yes **

Yes **

No

No

2.1.xxx

No

No

No

No

No

Yes (SP2,SP3)

No

No

Yes **

Yes **

Yes **

No

No

2.1.430

No

No

No

No

No

No

No

No

Yes **

Yes **

Yes **

No

No

2.2.100

No

No

No

No

No

No

No

No

Yes (SP1)

Yes

Yes

No

No

2.3.1xx

No

No

No

No

No

No

No

No

Yes (SP1)

No

No

Yes

No

2.3.195

No

No

No

No

No

No

No

No

Yes (SP1)

No

No

Yes

Yes

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

On launch of Saia PG5®, the license for running Saia PG5® is checked. In case the license file (named user.key) is not properly registered a "software protecion violation" is encountered. As result, you won't be able to open any file of your project with the Saia PG5® utilities.

 

Symptom
When opening Saia PG5®, the following message is shown:

Reason
The user license is not properly installed or missing. Note that the license must be installed with the "Register Software..." function of PG5.
It is not allowed to copy the license file into the installation path of PG5 by hand!

Solution
Please optain a valid license from your local Saia Burgess Controls representative.
For registering your license, use the functionality "Register Software..." from the menu "Help" of the PG5 Project Manager.

 

When trying to create a Hex-File the message: "Failed to initialize the hex file generator" appears

 

Symptom
§ix100238§

 

 

Reason
The problem is caused by one of the first (never officialized) versions of PG5 1.3. If this version of PG5 1.3 was installed on the same PC like PG5 1.2 the hex-file-generator-path for PG5 1.2 was overwritten in the registry. Even a deinstallation of PG5 1.3 won't help.

Solution
The Hex-File-Generator has to be uninstalled and reinstalled with the following procedure:

Open the DOS command prompt and type the commands below:
------------------------------------------------------------------------------------------------------------
C:\Program Files\SAIA-Burgess\PG5 1_3>regsvr32 -u SpromSvr.dll
C:\Program Files\SAIA-Burgess\PG5 1_3>cd..
C:\Program Files\SAIA-Burgess>cd PG5 1_2
C:\Program Files\SAIA-Burgess\PG5 1_2>regsvr32 -u SpromSvr.dll
C:\Program Files\SAIA-Burgess\PG5 1_2>regsvr32 SpromSvr.dll
C:\Program Files\SAIA-Burgess\PG5 1_2>cd..
C:\Program Files\SAIA-Burgess>cd PG5 1_3
C:\Program Files\SAIA-Burgess\PG5 1_3>regsvr32 SpromSvr.dll
------------------------------------------------------------------------------------------------------------

Afterwards it will be possible to create hex-files with PG5 1.2, too.

 

If an other tool is using a different SCommCom.dll (Webconnect, Visi+, OPC...) than PG5, an error message will appear when opening PG5

 

 

Symptom
The following message window will appear:

 

Reason
There are several tools using the SBC Communication Driver (SCommDrv.exe, SCommdll.dll). If they are not using the same version of the SComm.dll, it is not possible to run them at the same time.

Tools using Scomm.dll:

• Webconnect
• Visi+
• Merz OPC
• Various SCADA systems
• All tools from the PG5 controls suite

After execution CSF the error flag is set.

 

If a channel >31 is used the new PCD3's and also PCD2's with new firmware won't work. The reason is, that the number of channels is now limited on 32 channels 0-31. It was once 128 channels. Because of that programms can work on a PCD2 and didn't work on a PCD3.

Unfortunately the programming examples in the manual 26-776 D/F/E 3 are also made with a channel >31 (50/60).

 

If a PCD is connected to the PC via USB cable, the new firmware PCD3 V010 and PCD2.M480 V020 do send a unique ID in their StringVendorRequest (iSerialNumber).

This has to be done this way because it's the only way to distinguish between several devices with the same VID/PID (VendorID/ProductID) in a USB bus system.

 

By default Window finds a new hardware for every new SerialNum. Therefore the user is prompted to re-install the USB driver every time a new PCD is connected to the PC. For sure that's not nice and we have modified the driver in a way that Windows won't ask for a reinstallation of the driver every time a new PCD is connected.
PG5 versions up to 1.3.120 will install the old version of the USB driver. For this versions it is recommended to uninstall the existing USB driver and afterwards installing the one attached to this FAQ. To do so, please follow the instructions below:

Procedure for updating the USB driver

• Close your PG5 and Web Connect applications but keep the PCD connected to the usb port of the PC

• Uninstall the actual USB driver from the Windows Device Manager.

  • Select the Window menu: Start, Settings, Control Panel, System
    §ix100214§

  • Select the Hardware dialog sheet and the button: Device Manager

  • Select the USB driver present under: DriverX USB (xxx)

  • To uninstall the driver, select the context menu: Uninstall
    §ix100215§

  • Unplug the PCD from the USB port of the PC

• Install the new driver

  • Store the new driver files attached to this FAQ into a temporary directory
    (files: SaiaDevice.inf, drvxusb-sys, Dxusb10.dll)

  • Plug your PC to the PCD and wait for the "Found New Hardware Wizard"

  • Select the radio button "Install from a list or specific location"

  • On the following window, select the radio button "Don't search. I will choose the driver location"

  • Browse to the directory with the new files listed above

  • In case the installer has found several files, select the correct source files from your temporary directory

After this procedure Windows won't prompt the user for re-installing a USB driver for every PCD as long as always the same USB port (PC side) is used. However, Windows appears to recognise a new device for every USB port on the PC/USB hub (also if exactly this device has been installed on the same USB hub but attached to another port.)

 

In order to figure out wheter the PCD contains the same user program version as present on the PC, PG5 relays on the "unique program identifiers". This FAQ contains a description of the used identifiers.

• open the data block view of the PCD, and open the filter window from the context menu.
• enter as symbol name the __PCD_UID__ and select "Internal symbols" in the Section "scope"
  
• Disassemble your *.pcd file and look for the DB definition (usually DB 3500)
• Go online with the Online Debugger and check whether your DB content is identical to the one in your PG5 project

The __PCD_UID__ consists of a number defined at the time the device in the PG5 project is created (based on the PC MAC address and the milli-second counter of the PC). This "original part" of the UID is combined with the modification dates of the files belonging to this CPU in order to generate the UID.

If the PG5 (or the S-Bus driver SCommDdll) is already running and one doubleclicks a PG5 program file (such as *.src or *.fup), it is possible that the file is not opened but a window named SCommCom with the message "Try to load another SCommCom.dll..." is shown.

 

Symptom
When doubleclicking a PG5 program file the following window appears:
§ix100185§

 

Reason
The reason for this behaviour is that Windows tries to launch the editor (e.g. SEDIT32.exe for editing IL files) that belongs to a different PG5 version. Windows "remembers" the editor of the PG5 that was installed first. So if you updated from PG5 1.2 to PG5 1.3 you'll most likely be faced with the problem mentioned.

Solution
The default application for opening a file of a specific type can be defined as following:

1. Open the Windows Explorer

2. In the menu "Tools" select "Folder options..."

3. In the window "Folder Options" select the tab "File types"

4. Choose the PG5 program file extension you want to open by doubleclicking (SRC, FUP, SFC...)

5. In the field "Details for <filetype> extension" click the button "Change..."

6. In the window "Open With" click the button "Other..."

7. Browse to the actual PG5 installation directory (default is C:\Program Files\SAIA-Burgess\PG5 1.x) and select the required application (by clicking "Open")

8. Close the opened windows (press "OK" or "Close")

Below a small list that indicates the editors needed for editing the program files:

Extension	File type	Editor
SRC	Instruction List file	sedit32.exe
FUP	Fupla file	sfup32.exe
SFC	Graftec file	sgraf32.exe
5PJ, 5PC	PG5 Project file and CPU file	spm.exe

 

 

 

Important Note
It is recommended opening the program files that belong to a project directly from the Project Tree of the PG5 Project Manager. This way the link between the ressources an the program files etc. is guaranteed.
If the files are opened from the Windows explorer, you can not be sure that after a change of a ressource this change applies also to the symbol in the Symbol Editor!

 

While booting, the PCD reads the header of the user memory mounted on the PCD. In case the the memory doesn't contain a proper header, the message "Header not initialized" is shown when trying connecting the PCD.

 

It is possible that the same problem can occur if a Flash or RAM is mounted but the jumpers for defining the user memory (type and/or size) are not set correctly.

 

Few of the PG5 FBox libraries are PG4 compatible.

• Read system information

• System self test

• Install and execute XOB's

• Measure and survey cycle time

On some PC's an error occures while uninstalling PG5. The error message is the following:

"Error 1905.Module C:\Program Files\SAIA-Burgess\PG5 1_3\SpromSvr.dll failed to unregister. HRESULT . Contact your support personnel."

 

This PG5 Error is to be ignored and will not cause any further problems or malbehavior of the system.

The message is provoked by the MSI (Microsoft Installer) and is caused by a missing entry in the registry for the SpromSvr.dll. Because this entry doesn't exist, it isn't possible to delete it.

Since the entry isn't existent no further actions have to be performed. The message may be accepted by clicking "OK". The uninstallation will continue and no further problems are to be expected.

 

It may occur that the message "Not enough space for extended header" appears while downloading the hardware settings of a PCD. In this case in the PCD history a message like "CONFIG TOO LONG" or "BAD MODEM STRING" (displayed by older FW versions) will be listed.

 

The messages mentioned above are provoked by the fact that there is no more space left in the header of the user memory.

Since the default setting of PG5 1.3 for downloading the hardware settings is only "S-Bus, Serial, Modem, TCP/IP, Gateway" but not the "Memory Allocation", by default the changed settings are appended to the existing header. Because there is only limited space available in the header, at one point there won't be anymore space left causing the message mentioned.

The problem is to be solved by downloading the memory allocation (this will delete the existing entries in the header). Therefore the checkbox "Memory allocation" has to be checked in the window appearing before the download of the settings.
Note that on a new memory allocation the content of the whole memory will be reset; the user program has to be downloaded again).

 

There is an Error Led on nearly every PCD system that can indicate a problem on the system. Read this FAQ to learn more about the different reasons for a lit Error LED and how to find the problem causing the lit error LED.

 

What causes the Error LED to get lit?
There are different reasons for a lit error LED. The most common reasons are listed below:

• A problem while assigning a communication port (e.g. missing communication module or wrong parameters)
• A problem while sending an S-Bus telegram (e.g. missing port assignation or invalid data array or media)
• Invalid mathematical operation (e.g. division by zero or value overflow after a multiplication)
• Index register overflow

How to find the problem in the code/configuration?
One fast way to find the problem is reading the history entries of the PCD. This may be done by using either the Online Configurator or the Online Debugger (type "Display History"). In the History some of the problems are listed explicitely (e.g. IPM not present) for further information regarding the History entries, please refer to the PG5 Help. The chapter "Messages" contains "Halt and History messages".
If only an "Error Flag" is mentioned the next task is to find the program part where the Error status-flag is set. This is to be done by using the Online Debugger:

• Go online with your Fupla- or IL program.
• Open the Online Debugger and type "Restart Cold All CPUs".
• Still in the Online Debugger, type "Run Until Status-flag Error". As soon the Staus-flag "Error" is set, the PCD will be stopped. Therefore the Fupla Editor will jump to the page which actually is processed (only this page is part of the current Fupla file! If the Error isn't caused by this Fupla file, it will jump to any other page which doesn't cause the problem. Have a look at this page and the FBox with the "stop"-box on it and decide whether the problem could have been caused by this FBox!
  If there isn't any FBox that could cause any problems mentioned above, repeat the procedure while beeing online with the next Fupla file of the CPU).
• If you can't find the problem directly in a Fupla file, switch to the Online Debugger again. After having stopped, a line similar to the line written below will be shown:
  *001234  STH       I/O       48                                  A1   Z0     N0     P1    E1     IX      COB2
  This first number of this line indicates on which line of the code the problem happened: the last instruction BEFORE the line shown caused the problem (the error LED is lit after the problem).
• Type "Display Program <line indicated -10> Count 15". Now you can see the instruction that caused the problem: Refer to the IL instruction Set (Online Help of IL Editor SEDIT) in order to figure out what this instruction exactly does.

If a SASI instruction causes the problem, check out the following possible reasons:

• The port is already assigned (have a look at the HW configuration and search for further SASI instructions by typing "Locate Instruction SASI" in the Online Debugger!).
  Hint: Also have an eye on the SASI FBoxes you used as well as on the HMI Settings tab.
• The port doesn't exist
• The SASI text isn't valid
• S-Bus support isn't enabled in the Hardware Settings but an S-Bus assignation was executed. This won't work because in this case the PCD doesn't have an S-Bus address (which is required for S-Bus communication).

If it seems as a mathematical operation caused the error, use the online debugger to run shortly before the problem-causing part of the code by typing "Run Until Instruction-Pointer Equals <instruction line shortly before problem-line>" (note that the instruction line must contain an instruction!). Once reached this line, type "sTep". In the Step-mode, you will see the contents of the PCD medias [brackets].

Remark:
The Error LED is lit in case the Status Flag E (Error status flag is set high) and no XOB 13 is programmed. In case the XOB 13 is programmed, the Error Led won't get lit but this XOB is processed immediately.

 

The tool tracewin.exe is a small executable that records the communication between Saia PG5® and the S-Bus communicaiton driver. It is very useful in order to analyze the communication between Saia PG5® and the PCD's.

Since it logs the information of the SCommDll, it may also be used for recording S-Bus traffic of the SBC OPC server or any other software using the SBC S-Bus driver.

 

Opening Tracewin
The tool Tracewin is installed in the installation folder of Saia PG5® (default location: C:\Program Files\SAIA-Burgess\PG5 1_3\Tracewin.exe). It is to be called by double clicking it.

As soon it is called, the follwing window will be opened:

Configuring Tracewin
In order to record only the data needed, the "SComm Trace Options..." of the menu "File" can be adjusted.
E.g. the checkbox "Lock, Event, Critical" is only used in rare situations (but doubles the size of captured data if checked) and therefore narmally may stay unchecked. Below an example of the "SComm Trace Options" that suits in most cases:

In case no communication can be established, it can be helpful enabling all checkboxes in order to receive as many information as possible. As the file will be pretty small anyways, the additional lines won't bother much. 

Storing recorded data
The buffer finally may be stored with "Save as..." and then be viewed by any other text editor.
(The recorded data is very useful for the SBC support team in case you encounter a communicaton related problem.)

 

PG5 features special batch files that automatically record system and application specific information. The files generated by these batches do help the support team to analyze the problem the PCD is concerned of.

 

How to call the batch files for V1.2 and V1.3 ?
The batches are to be called directly from the Windows start menu (in standard installation under Programs/SAIA-Burgess/PG5/Record PCD Data). 
The file to be selected is depending on the controller type you want to read the data from. To read the system information of a PCD2.M170 you would choose the batch file "PCDxM170"; for a PCD3.M5540 the batch "PCD3Mxxxx".

 

How to call the batch files for V1.4 and higher ?
1. Start PG5 V1.4 or higher.
2. Choose "Tools" > "Online configurator" in windowmenu.
3  Choose "Tools" > "Create Diagnostic File .." in windowmenu.
4. Read the Text (savedirectory!) and press <OK>

 

What does the batch file do?
The batches will call the Online Debugger which will automatically connect to the PCD. (The online settings used to connect the PCD last time will be used. Please make sure these settings still apply. Please also note that the Online Debugger musn't already be in use because in this case the batch wouldn't be able to call it again.)

During recording you'll see the follwing information running over the screen:

• PCD type and system status

• Communication settings of the PCD

• History entries of the PCD

• Part of the user program

• Stack of the PCD (mainly hex code)

Where is the recorded data stored?
The recorded information will be appended to the file chaine.txt; to be found under C:\Program Files\SAIA-Burgess\PG5 1_3\Batches\.

 

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

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

 

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

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

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

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

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

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

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

Setup of the SCommDrv.exe On the client PC :

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

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

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

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

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

 

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

 

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

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

 

Standard properties:

 

§ix100423§

 

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

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

 

It is not possible to open the SCONF.exe (part of the standalone up-/downloader). An errormessage of a missing dll MFC42.DLL appears.

 

Normally the MFC42.DLL is installed automaticaly with Microsoft products. It is possible that a harddisk-cleaning program erases this dll.

If this is the case you have to re enter this dll in the directory Windows\System32.

Following attachment contains this dll.

 

At the first launch of PG5 or at the first attempt to connect a PCD the error message "Cannot find SCommDrv IP-Adress/port entry in Registry" is shown in case the TCP/IP protocol isn't enabled or if the user isn't a "Power User" or an "Administrator" of the concerned PC.

 

The reason for the requirement of TCP/IP is that the SCommDrv (SBC Communication Driver) communicates with the SCommDll via TCP/IP. This allows multiple applications to use the SCommDrv simultaneously and therefore establish a connection to a PCD at the same time.

 

The User needs to be a power user or an administrator because PG5 writes settings such as channel definitions into the PCs registry (which only can be edited by power users and administrators).

 

It might happen that a "Download Program Warning" is shown on program download. the message is the following:

The user program writes into the Text/DB segment. This will fail because the destination PCD contains Flash EPROM which is read-only.

 

§ix100157§

This message is shown if PG5 has allocated Texts and DBs which are to be modified during runtime of the Program in the Flash or EPROM memory. This won't work!

This allocation is done according the "Software Settings". In order to correct this problem it is recommended to use the "Set Defaults" button in the "Registers/Text/DB's" tab of the "Software Settings" window.

 

It may occur that the SCommDrv (Communication Driver of PG5 for connecting PCD's) can't connect a PCD. The error messages sometimes aren't very clear and vary form the message "SCommDrv error, Socket not installed or wrong IP number" to a simpler version "Driver not available".

 

This problem may be caused by the fact that the SCommDrv can't connect the localhost (127.0.0.1) on port 7000.

Reason Nr. 1: Firewall or antivirus SW blocks IP port
In case a firewall or a antivirus SW is installed on the concerned PC, the problem could be caused by this software. Please refer to FAQ 100323 (link attached below) for further information regarding this topic. 

Reason Nr. 2: Port 7000 used by another application
Another possibility is that the port 7000 is blocked by another application. In this case it is sufficient to configure another port in the Setup Window of the "SBC Communication Driver". To do so, click with the right mouse button on the "SBC Communication Driver"-Icon (, lower right side of the screen) and select "Open" in the context menu.
On tab "Setup" of this window the port number can be edited.
To figure out, which ports actually are used, the command NETSTAT can be typed in the Window's "Command Promt". This will list the actually open connections on your localhost.

Reason Nr. 3: Wrong server IP Address
In the setup of the SCommDrv the IP address of the machine where the SCommDll is running is specified. If on the machine specified there no SCommDll is running, messages as shown above are the result. For further information regarding this topic, refer to FAQ 100248 (link attached below).

Reason Nr. 4: TCP/IP not installed
One possible cause is that there is no Socket installed. Make sure you have enabled the "Internet Protocol (TCP/IP)" on your PC, even if you don't need it for any other application and also if you don't even have a network card built in. Please refer to the Windows Help for further instructions regarding the activation of the "Internet Protocol"

 

Some history entries introduced in new firmware versions can't be found in the Online Debugger Help nor in the online help of the Online Configurator.

 

Below you can find recently introduced History entries that can't be found in the Help files of PG5 versions older than PG5 1.3:

History Entry	Meaning	Remark
MEM-EXT. ERROR	Extension memory corrupted	Replaces "BAD TXT/DB TABLE"
CONFIG TOO LONG	HW setting to long to be put in EEPROM	Replaces "BAD MODEM STRING"
WATCHDOG FAIL	Restart due to SW Watchdog was executed
IPM NOT PRESENT	There is an IP configuration but no IP module
IPM DONT RESTART	PCD has restarted but the IP module does not respond
IPM HAS OLD FW	The IP module FW is not compatible with the PCD FW
IP FAIL SASITEXT	There is an error in the SASI text
IP FAIL SASI DBX	There is an error in the node list configuration DBX
IP FAIL NO IPM	An IP function has been carried out, but the PCD has no IP configuration
IP FAIL TOUT	Incorrect timeout value in Ether-S-Bus master SASI text
IP FAIL PORT Nbr	Incorrect port number in Ether-S-Bus master SASI text
Included text >3	Text nesting depth overflow
SBUS PGU Error	The SBUS PGU Port defined in the HW Settings isn't physically present

Error Messages concerning PCD1.M2, PCD2.M480, PCD2.M5xx0 and PCD3.Mxxx0 systems (SBC-NT)

History Entry	Meaning	.
Media corruption	This message indicates that the onboard RAM has been corrupted (becaused of a discharged superCap, bad Battery or similar). If this message is shown, all medias (R, C, F) are reset to 0, the clock is reset and the program is restored from the onboard flash (if possible). This entry has been replaced in firmware version 1.10.04 by "Memory Lost nn"
Memory Lost nn	Replacement message for "Media Corruption", but with more detailed informaton why the user program was restored and the media reset (since FW version 1.10.04):  01: Bad or missing battery 02: Supercap voltage too low 03: Corrupted memory pattern/signature 04: RAM memory cleared by user (push button) 05: RAM and flash memory cleared by push button 06: Corrupted program header
Not RUN on xx7HW	The HW is a xx/ type; the FW doesn't run the program on this HW
SYS. TYPE ERROR	The HW system type isn't correct
Reg>4095 not sup	The FW doesn't support more than 4095 registers
SF NOT LOADED	System function (CSF) isn't present
CSF INV PAR NBR	Invalide CSF parameter number
DOUBLE TIME BASE	Timebase defined more than once
XOB Nbr to big	XOB (Exception Organisation Block) number is too big
COB Nbr to big	COB (Cyclic Organisation Block) number is too big
FB Nbr to big	FB (Function Block) number is too big
PB Nbr to big	PB (Program Block) number is too big
IST Nbr to big	IST (Initial STep) number is too big
ST Nbr to big	ST (STep) number is too big
TR Nbr to big	TR (TRansition) number too big
SB Nbr to big	SB (Sequential Block) number too big
FABINFO CRC FAIL	Invalid CRC in the fabrication information. Please contact SBC
SYSWDOG START	Restart due to SW Watchdog executed
NO COB	No COB loaded
EXTHDR EEPR FAIL	Error in the EEPROM extended header
IP SB GWY FAIL	TCP/IP SBus gateway can't be initialised
IP Ch xxx no mem	No memory to open the channel on the TCP/IP Open data mode
MODEM: UART fail	UART doesn't accept the configuration
MODEM: Reset fail	Error on the modem reset command
MODEM: No modem	No modem or defective modem equipped on the port
MODEM: Init fail	Error on modem initialisation
MODEM: ERROR???	Unknown modem error
DIFF CFG Ch x	Different configuration on Profi-S-Net port x. Verify the configuration of the port
PS FAIL SASI DBX	Error in the node list configuration DBX
PS FAIL TOUT	Incorrect timeout value in Profi-S-Bus master SASI text
PS FAIL SAP	Incorrect SAP number in Profi-S-Bus master SASI text
PS FAIL SASITEXT	Error in SASI text
PSM NOT PRESENT	Profi-S-Net (Profibus) configuration but no Profi-S-Net (Profibus) existent
PSBus GWY FAIL	Profi-S-Bus GWY can't be initialized
PSBus PGU FAIL	Profi-S-Bus PGU port can't be initialized
SWTO ERROR	System Watchdog Timeout Error, see FAQ 100908 and 101069
BUS ERROR	Internal memory access failed. Please contact your local support team, see FAQ 101069
TCPS ERROR	TCPIP-Stack crash. Please contact your local support team
KRNL ERROR	Internal task overload. Please contact your local support team, see 101069
BACnet incompatible FW	The BACnet firmware found on the PCDx.R56x module is not compatible with the PCD firmware. Please update the BACnet firmware (see FAQ: 101010) This message is only given with firmware version 1.10.16 and later.
Bnt FAIL TL00001	An error occurred in relation to the BACnet configuration. Please refer to FAQ 101436.
MANUAL HALT	Indication that the PCD has been halted by pushing the Run/Halt button (implemented in firmware 1.14.23 and later)
EXT DEVICE FAIL	This message can be generated by PCD systems with FW 1.10.xx; The message is wrong and should be "31 CALL LEVELS". It indicates a too big nesting level of FB/PBs (if XOB 10 is programmed, it is called in this case)
RESISTERS FAIL	The termination resistors of port 3 of a PCD3.M5340 can not be activated due to a firmware restriction, see FAQ 101722.
INVALID PERI DBX	Hardware configuration contains errors (e.g. peripheral addresses, modules not supported by the firmware)

 

After the installation of PG5 the "Standby mode" and/or "Hypernite Mode" isn't available any more on the PC/Laptop.

 

This problem is caused by the DriverX that was installed together with the PG5. The DriverX is used for IPC's (PC104) and isn't used on Workstations and laptops. Its purpose is the communication between an IPC and a PCD2.M2x0 over it's dual port RAM. Unfortunately this driver isn't compatible with the power management of Microsoft Windows systems makes the standby option disappearing.
The DriverX isn't installed automatically installed with PG5 1.3.

 

How to get the Stanby Mode back:
Since the DriverX isn't used on normal workstations and laptops it can be uninstalled or disabled in order to gain back the Standby/Hypernate mode. Therefore please follow the steps below: 

-	Open "System Properties" from the "Control Panel" of your Windows OS
-	Select the "Hardware" tab and click the "Device manager" button.
-	Check the option "View hidden devices" from the "device manager" menu "View"
-	Now a new device group (Non-Plug and play drivers) is listed; select the "DriverX" and either uninstall or disable it.
-	Reboot your machine.

In case the standby mode still isn't available it is very likey that another driver (non SBC related) is causing this problem. For further information we recommend referring to the Microsoft Support:
support.microsoft.com/support/kb/articles/q266/1/69.asp

 

 

The amount of formal parameters has been increased to 250

 

 

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