You want to change the file name of the attachment. Because you log every day trends and save them daily in a new .csv file. The actually date is coded in the file name. Now you want to send an email every day with the actually file. See the PG5 example below.

Note:

In the attached example the data’s will be stored daily. If you store the data’s weekly or monthly you have to adapt the program especially the file name in the log file inside of the SendMail FBox.

Additionally in the example is the function implemented that you can give directly the SMTP server name and the IP Address is not needed. The advantage is if your provider change the IP address you do not need to adapt the program see FAQ 101850 for more information about this topic.

It is possible to send SMS by sending Emails to a provider that will transfer them to SMS messages. This requires an Internet connection (DSL, or GPRS / UMTS)

In Switzerland we have tested the 2 following solutions:

1) Bluewin

Requirements:
- ADSL connection from Swisscom / Bluewin
- You have to set up a Bluewin Email account to be able to send an mails (included with ADSL connection)
If you have an ADSL connection from Bluewin and at least a DSL Mini Abo, the "Service Package Classic" is included.

30 SMS/month are free of charge and each additional one costs 0.10 Fr. (This was valid Nov. 2013. For more information you have to contact swisscom)

www.swisscom.ch/res/internet/email/email-angebote/index.htm

Use the following syntax / procedure:

1. You have to use the FBoxes Adv. Text Mail Initialization and Adv. Text Mail Send.
Additional information how to send Emails with Bluewin can be obtained in FAQ # 101020

2. In the "to" field enter the phone number and then @sms.bluewin.ch (example: 0791234567@sms.bluewin.ch)

3. The SMS Text can be entered in either "subject" and/or in the Email Text field

2) Ecall

Requirements:

- works independently from Internet-Provider
- Configuration an email account by any Provider. The Provider must offer the possibility to send emails without SSL-encoding. (for this reason for example Gmail from Google is not appropriate)

More details in this link:
www.ecall.ch

This error message code of the "E-Mail Init" FBox (when trying to send a mail) indicates that the authenthification on the SMTP server failed.

The most common reason therefore is that the password or the user name is not correct.

Symptom
It is not possible to send EMails and the FBox "EMail Init" indicates the error code -29.

Possible reasons
The most common reason therefore is that the password or the user name is not correct. However, it is possible that one of the following reasons are responsible for the failed authentication:

• The user name or the password is too long.
  In earlier PCD Firmware versions, the size for the user name and the password string was fix limited to a maximum of 24 characters. This limit was enlarged to 128 characters in firmware 1.16.18 and newer.
  Following systems are concerned:
  - PCD1.M2xx0
  - PCD2.M5xx0
  - PCD3.Mxxx0
  Solution
  Please update the fimrware to the version to version 1.16.27 available on the support site.
• The user name (often an email address) contains one of the following expressions:
  - @d, @h, @l
  - $d, dH, dRxxxx
  Solution
  If this is the case (and e.g. the "$D" will be replaced with the current date by the firmware, please add a second "@" or "$" (--> @@d) in order to avoid the interpretation of the text during the transmission.
  
  

There are some characters like D, H, R, C and L that can be wrong interpreted if this characters are the first one behind the @.

Problem
The characters mentioned above can be used to implement a PCD value like register or countersin a text. For example $D implements the date, $R1000 the value of register 1000 etc. In an email address the @ is in some cases interpreted like the $. Therefore it can lead to problems if one of this characters follows the @. Per example: email@dinfo.com
In this case the date is introduced to the email address : email130309info.com. For that reason the email will never arrive at his destination due to this wrong interpretation.

Solution
At the moment the only workaround for this problem is to implement a second @ : email@@dinfo.com
With this additional @ the interpretaition will be correctly.

Depending of the applications different ports are used on the PCDs:

The PCD3 systems equipped with an Ethernet port and the PCD2.M5540 are able to send emails. But sending e-Mails is not only depending on the CPU itself.

The PCD3 systems equipped with an Ethernet port and the PCD2.M554x support SMTP (Simple Mail Transfer Protocol). Sending emails does not only depend on this feature but as well on the ISP (Internet Service Provider), the firewalls and router configurations between PCD and ISP.

The attached checklist with the criterias to verify with your provider and / or your IT support shall help to check whether sending E-Mail is possible.

If you want to use the bluewin.ch SMTP Server for relaying purposes (send an E-Mail from the PCD to the bluewin.ch SMTP Server and the SMTP Server will send the E-Mail to the destination E-Mail account) the following has to be considered

• The use of the bluewin.ch SMTP Server is only possible if you have a bluewin.ch account (bluewin ADSL router with a bluewin.ch account)
• The SMTP Server of bluewin.ch does need a authentification
• In PG5 use the F-Box “AMail Init”
•  In the F-Box “AMail Init”
•  In the F-Box do set the SMTP Server port to 25 or 587
•  In the text “SMTP” set the TCP/IP Address of the bluewin.ch SMTP Server to 195.186.227.53 (old TCP/IP address was 195.186.19.55, the DNS-name is smtpauth.bluewin.ch)
• In the “Name” text, write your bluewin e-mail address without "@bluewin.ch"
  (exp. my_name for the e-mail account my_name@bluewin.ch).
  The e-mail address @bluemail.ch does not work.
• In the “Pwd” text, write the password of your e-mail account
• In the “Sender” text to write a “correct” E-Mail address,
  “correct” means where the domain name does exist.
• In the “To1..To5” text, write the destination E-Mail account 

Use the Send Mail F-Box to send the E-Mails.

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

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

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

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

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

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

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

Yes, there are limits both for the E-Mail itself and also for the attachment.

General information
for all EMail messges sent by a PCD, the following limitations of the EMail elements apply. Additionally, the maximum size of a message is limited depending on the system from which the message is sent (PCD7.F655 or PCD3/PCD2.M5). Please refer to the table below for the maximum size of the EMail elements:

PCD7.F655
The maximum text size of the whole message is 780 characters for EMails sent by the PCD7.F655. This amount is calculated as:
 sender address + recipients addresses + subject + body text (content)
If the message is HTML-formatted, all characters from the embedded HTML-Tags are part of the sended body text! Attachments are not supported on a system equipped with a PCD7.F65x.

PCD3.Mxxxx and PCD2.M5xxx
The maximum text size of the whole message is 3072 characters. This amount is calculated as:
 sender address + recipients addresses + subject + body text (content)
If the message is HTML-formatted, all characters from the embedded HTML-Tags are part of the sended body text! Only one single file attachment per E-Mail is allowed. The attached file must not be bigger than 1 MB.

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

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

In general, a HALT reason "CSF INV PAR" always indicates a problem with a system function parameter. When using the E-Mail functions the reason is often an empty TEXT string declared with default size.

Right after downloading a program with an empty TEXT declared with default size, the PCD does not go in RUN, but goes in HALT. In this case PG5 displays the following dialog:



In order to solve the problem, the empty TEXTs must be declared with a fixed size of 1 characters, as in this example:



Remark: This modification must not be applied to the text who is in the field "File". This text must stay declared with default.

The DDC-Suite F-Box "Init ABS" allows to define a antiblock protection for pumps and valves.

If the criterias to switch on the antiblock protection is true, the antiblock protection is switched

on for one minute.

It is not possible to change this "switch on" time.

With the DDC Suite version 2.6.172 (or 2.5.172 for PG5 1.4) the FBox "System hot water 2.0" (in German: "Anlage WWB 2.0") did not switch off even after the "temperature limit during disinfection" has been reached.

Symptom
With the DDC Suite version 2.6.172 (or 2.5.172 for PG5 1.4) the FBox "System hot water 2.0" from the Family "DDC Systems and clocks" did not switch off the output "recommended state" even after the "temperature limit during disinfection" has been reached.

Reason
Older versions of the DDC Suite did apply the "maximum operation time of the disinfection (legionella) prevention" in every case.

Solution
The following FBox library versions do switch the output off immediately after the temperature limit during disinfection has been reached:

• PG5 1.4: 2.5.172
• PG5 2.0: 2.6.172
  

In case a controller of the DDC Suite has a setpoint which is far below (or higher, depending on the usage of the controller) the current actual value and the set point is modified, the output value is increasing (or decreasing).

Symptom
The output value of a controller of the DDC Suite is "jumping" if the setpoint is changed. This kind of output value jumps can be observed even if the actual value is still higher than the setpoint (e.g. if the room temperatur is 20°C and the setpoint is changed from 24.0°C to 22.0°C).


Reason
This behaviour is a standard behaviour of the PI controller used by the DDC Suite by default (the output value is the sum of the proportional part and the integral part which is responsible to eliminate a persistent controller deviation which can be caused by the pure P-controller). In case the setpoint is changed, the proportional part is changing immediately while the integral part will be reduced over time (resulting in the same valve postion of 0%). This behaviour is identical to the one applied by the PI controllers from the Heavac FBox library.

Solution PG5 2.0
In case this behaviour is not wished (in order to keep the valve closed on changes of the setpoint if the actual value is still smaller than the setpoint) the controller algorithm used by the DDC Suite can be changed:
You have to create a Global Symbol File ".sy5" and create a Constant "K" public symbol with the path "DDC_Suite.Controller.PID_Mode" inside this File.
§Ix101461§
During the next build, the message window from PG5 will indicate that the "Modified PID algorithm" is used (for all the FBoxes in this Fupla). This algorithm will disable the I-portion of the output in case the actual value is higher than the setpoint.
§Ix101462§

Solution PG5 1.4
In PG5 1.4, add a K-constant with the name "DDC_Suite.Controller.PID_Mode" to your public symbols:

During the next build, the message window from PG5 will indicate that the "Modified PID algorithm" is used (for all the FBoxes in this Fupla). This algorithm will disable the I-portion of the output in case the actual value is higher than the setpoint.

The "modified PID algorithm" will no longer lead to jumps of the controller output as long as the valve is closed:


By default (if the above mentioned symbol does not exist), the standard PID algorithm will be used and the message in the message window is "Standard PID algorithm enabled"

Remarks

• The "Modified PID algorithm" is implemented in the DDC Suite library version
  - 2.5.150 and later (for PG5 1.4.300)
  - 2.6.150 and later (for PG5 2.0) 
• In DDC Suite V3 this option will be integrated to the Init FBox of the DDC Suite.
• When working with the Heavac FBox library, the P-PI controller can be used in order to avoid the output jumps of PI controllers (the P-PI controller is only adding the I-portion in case the setpoint is near the actual value).

When using the FBox "Motor 2-speed 2.0" (or the "Motor 3-speed 2.0"from the FBox family "DDC Controls" with the option BACnet activated, it can happen that the motor does not change to speed 2 (but shortly is switched off before re-using speed 1).

Symptom
When using the FBox "Motor 2-speed 2.0" from the FBox family "DDC Controls" with the option BACnet activated, it can happen that the motor does not change to speed 2 (but shortly is switched off before re-using speed 1).

Reason
In case the option BACnet has been selected, the feature from "HMI Super" has not been deactivated.

Solution
The versions listed below correct this wrong behaviour. Please update your library and then rebuild and download the program again.

• PG5 1.4.300: DDC Suite library version 2.5.150 
• PG5 2.0.110: DDC Suite library version 2.6.150

The FBox "Initialisation 2.0" from the DDC Suite FBox library has a "WD" input. When activated, this will close the onboard watchdog relay of the PCD (and open it if an error on the PCD occurs or if the user program takes more than 250 ms to be executed).

WatchDog description
If the input WD (see below in the screenshot) is activated, the onboard WatchDog relay stays switched on (closed) until an internal error is detected. The WD relay is turned off and stays deactivated until the error has been reset via FBox parameter "diagnostic history" and if no error occurs immediately again.
An error detected once will stay active after power down/up. This means that the WD relay stays open until a "reset" will be done.

Usage
This mechanism can e.g. be used for switching on an alarm signal (horn, lamp) or to indicate to another PCD to take over some functionality in case of error (a kind of redundancy).

Remarks

• If the WatchDog relay should only be opened in case the CPU cycle time exceeds 250 ms (as it has been the common when not working with the DDC Suite), the FBox "Hardware WatchDog" from the standard FBox family "Special functions" has to be used.
  In that case the "WD" input of DDC Suite FBox "Init" will be overwritten by the feature of this FBox.
• The description of this mechanism has not been present in the help of the DDC Suite until version 2.5.101 (for PG5 1.4) and 2.6.101 (for PG5 2.0).

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

Step-by-step example Web Editor 5

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

Step-by-step example Web Editor 8

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

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

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

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

Some DDC Suite FBoxes provide the possibility to generate BACnet objects automatically. This FAQ lists solutions if the suggested objects are not convenient.

Problem
The suggested BACnet objects which are available in the FBox do not cover the requirements. E.g. only the operation hours (CntH in the FBox below) shall be mapped to BACnet. 


Solution
There are several possibilities available to solve this problem:

• Selecting "BACnet = No" in the FBox and then configuring the operation hours manually in the BACnet configurator (and merging the DDC BACnet configuration with the manually generated BACnet configuration).
• Selecting "BACnet = No" in the FBox and using the FBox "Integer 2.0" from the FBox family "DDC Analogue values" for mapping the value to BACnet (in this case the according data point's unit and scaling is to be configured correctly in the BACnet configurator)
• Advanced version: Selecting "BACnet = Yes" in the FBox and adapting the generated generated BACnet objects. The objects can be adapted according to the chapter "BACnet advanced" in the "DDC Suite Guideline" (note that this will modify the BACnet objects creatd by all identical FBoxes used in this CPU; e.g. by all FBox "Pump 2.0" used in the CPU) 

If BACnet is enabled in a DDC Suite project a BACnet flash module must be installed because the I/O are treated differently by the DDC Suite FBoxes.

Symptom
The outputs of controlled with DDC Suite FBoxes are not working. In the DDC FBoxes, BACnet is enabled, but no BACnet flash module (PCD7.R65x or PCD3.R56x) is plugged.


Reason
If BACnet is enabled, code generated by the DDC suite is adapted to the BACnet feature (outputs can e.g. be written with priorities with a BACnet Operator Station BOW). If the BACnet task is not running (e.g. because no BACnet module is plugged or because the BACnet firmware stored on the PCDx.R65x is not compatible with the PCD firmware) the program will not work correctly.

Solution
Only enable BACnet in the DDC Suite if there is an according module plugged to the PCD.

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.

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

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

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

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

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

Every time when you send an email you make a query to get the IP-Address with the FBox Querry IP Name.
After that the received IP-Address is written in to the WebCMail FBox.
This workaround inhibit that the emails are transmitted also when the SMTP Server change the IP-Address.
Project example is in the attachment the following Image shows a PrintScreen of the Fupla. (PG5 2.1.200)

This error message code of the "E-Mail Init" FBox (when trying to send a mail) indicates that the authenthification on the SMTP server failed.

The most common reason therefore is that the password or the user name is not correct.

Symptom
It is not possible to send EMails and the FBox "EMail Init" indicates the error code -29.

Possible reasons
The most common reason therefore is that the password or the user name is not correct. However, it is possible that one of the following reasons are responsible for the failed authentication:

• The user name or the password is too long.
  In earlier PCD Firmware versions, the size for the user name and the password string was fix limited to a maximum of 24 characters. This limit was enlarged to 128 characters in firmware 1.16.18 and newer.
  Following systems are concerned:
  - PCD1.M2xx0
  - PCD2.M5xx0
  - PCD3.Mxxx0
  Solution
  Please update the fimrware to the version to version 1.16.27 available on the support site.
• The user name (often an email address) contains one of the following expressions:
  - @d, @h, @l
  - $d, dH, dRxxxx
  Solution
  If this is the case (and e.g. the "$D" will be replaced with the current date by the firmware, please add a second "@" or "$" (--> @@d) in order to avoid the interpretation of the text during the transmission.
  
  

Yes, there are limits both for the E-Mail itself and also for the attachment.

General information
for all EMail messges sent by a PCD, the following limitations of the EMail elements apply. Additionally, the maximum size of a message is limited depending on the system from which the message is sent (PCD7.F655 or PCD3/PCD2.M5). Please refer to the table below for the maximum size of the EMail elements:

PCD7.F655
The maximum text size of the whole message is 780 characters for EMails sent by the PCD7.F655. This amount is calculated as:
 sender address + recipients addresses + subject + body text (content)
If the message is HTML-formatted, all characters from the embedded HTML-Tags are part of the sended body text! Attachments are not supported on a system equipped with a PCD7.F65x.

PCD3.Mxxxx and PCD2.M5xxx
The maximum text size of the whole message is 3072 characters. This amount is calculated as:
 sender address + recipients addresses + subject + body text (content)
If the message is HTML-formatted, all characters from the embedded HTML-Tags are part of the sended body text! Only one single file attachment per E-Mail is allowed. The attached file must not be bigger than 1 MB.

The E-Mail FBoxes and System Functions allow both the sending of plain text e-mail messages, as well as HTML-formated E-Mail messages. However, a special syntax is required for inserted HTML tags.

To send E-Mails with HTML-formated text it is necessary to use the FBox "Adv. Text Mail Send". Within the FBox adjust dialog the parameter "Mail format" must be set to "HTML".

HTML tags have to be inserted with a special syntax. E.g. to format some words bold or red the following syntax has to be used:

"Some words are <<>b<>>bold<<>/b<>> or <<>span style='color: red;'<>>red<<>/span<>>, others are just black!<<>br /<>>This is a new line."

Any HTML-capable E-Mail client will show the above example code as follows:

Some words are bold or red, others are just black!
This is a new line.

Common HTML editors (like Dreamweaver, NVU, KompoZer etc.) can be used to build the HTML-formated text. However, in this case it is absolutely necessary to edit the HTML code by adding the additional bracket <> pairs manually, since the SBC-specific notation with <<> and <>> is not generated by these programs directly!

It is recommended to use only simple HTML tags within E-Mails, since many E-Mail clients only support a small subset of HTML formating codes. Also, it is always good practice to check HTML-formated E-Mails with a few different clients (e.g. Thunderbird, Outlook etc.) to ensure the proper displaying of the message before it is used for a real-world application!

More about HTML

General information about the Hypertext Markup Language (HTML) can be found at Wikipedia in English (en.wikipedia.org/wiki/HTML) and German (de.wikipedia.org/wiki/HTML). German users should also have a look at the comprehensive SelfHTML website at de.selfhtml.org.

When using the EIB/KNX driver FBox "EIB driver FT1.2" with PG5 2.0.200 (and the EIB FBox library SP2.6.210) the build of the project fails due to a fatal error.

Symptom
When using the EIB/KNX driver FBox "EIB driver FT1.2" with PG5 2.0.200 (and the EIB FBox library SP2.6.210) the build of the project fails due to a fatal error. The according error messages are :

Assembling: C:\Documents and Settings\All Users\Saia-Burgess\PG5_20\Libs\App\EibDrvG5.srx
Assembling: eibdrvf5.srl
Fatal Error 1304: eibdrvf5.srl: Can't open file
Assembly complete. Errors: 1 Warnings: 0
Linking: _Device1.obj + Fupla.obj + InitODM.obj + EibDrvG5.obj + eibdrvf5.obj
Error 2006: Obj\eibdrvf5.obj: Can't open file
Lib files: sfuplib3.obl
To: Device1.pcd Device1.map
Error 2021: Fupla.obj: Unresolved external symbol: _eib_group.CH_1._FB.RECEPT12

Reason
The reason for this problem is a missing file in the EIB FBox libraray version SP2.6.210.

Solution
Please update your EIB / KNX driver FBox library to version $2.6.212 or later (available on the support site) or later.

Remark
This problem is solved with PG5 2.0.220 (which installs the EIB library 2.0.220).

Yes, this is possible starting from the EIB FBox library version $2.5.302.

If the version 2.7.320 of the ‘File System Library’ is used, and the F-Box 'LogToFile' does log information's in to a *.csv file, then it could be that not all information’s are stored in the *.csv file.

Description:

If for example the information should be stored each second in the *.csv file with the help of the F-Box 'LogToFile', then it could happen that sometime the information is stored only after 6 or 10 seconds, means that not all information’s are stored in the csv file.

This error doesn’t happen in the past and was introduced with the ‘File System Library’ version 2.7.320.

Correction:

To fix the problem use the ‘File System Library’ version $2.7.325 or later.

After a file has been downloaded from the PC using FTP to the file system of the PCD (and the file has not been present before) the case can occur that the PCD can no longer write into this file (or read from this file).

This situation can be caused by the fact that the file has been created (downloaded) by the FTP user "root".

Symptom
After a file has been downloaded over FTP to the PCD (with the default user "root") this file can no longer be accessed by the user program with e.g. the rights of the "Web Group".
If the PCD user program tries to access such a file (which was copied before from the PC to the PCD) by the FBox "HDLog File" and on the FBox "Memory" the parameter "Group ID" is set to "Web", then the FBox will not allow the access to the file because the group ID of the file is not the same as the group ID specified on the FBox.
This means that the LED of the FBox do switch to red and the error output of the FBox is set to high.

Reason
If the FTP user "root" (default) does access the file system, then all files which are created (moved/copied/generated) do have the group ID set to 0. This behaviour has been introduced in the first firmware versions supporting the FTP Server and have been left this way in order to keep the compatibility. 

Solution
To avoid this problem it's necessary to create on the PCD a new FTP user which belongs to the same group ID as defined on the FBox "Memory".

For PG5 2.0 or later:
Defintion of a new FTP user on the device configurator with the follwoing configuration:
# User = sbc_pcd
# password = web_access
# Belong to Web Group.
# Have access to files / directories belonging to all groups except PLC Group
# By default read/write access


For PG5 1.4:
(File FTPCONFIG.TXT which does contain the FTP user and which have to be copied to the folder "config").

Example for the definition of an FTP user with belongs to the group ID "Web" (note that the line "UserName..." must not contain any space characters):

# User = sbc_pcd
# password = web_access
# Belong to Web Group.
# Have access to files / directories belonging to all groups except PLC Group
# By default read/write access
UserName=sbc_pcd,web_access,0x08,0xFE

Remarks

• For security reasons it is recommended not to leave the default user "root" active (because if this is the case, everyone who read the FTP manual can access the file system).
• To figure out the group ID of a file on the PCD file system you have to use the "SBC SD File System Explorer":
  

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

The following text definition option has to be used:


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

For the FBox "Log to File Advanced" or "Log to File" the text 0 must not be used.

Symptom
If it isn't possible to write to a file on the file system of the PCD and the LED on the FBox is red when trying.

Possible reason
It is possible that you have used the text with the address 0 in the application program of the PCD. Due to a restriction of the FBox library it isn't allowed to use the text with the address 0.

Solution
To solve the problem, please change the address of the text 0 to an different address >0.

One write access executed with the new version of the FBoxes can write up to 3072 characters (the FBox executes several write commands for 255 bytes each, which is the biggest junk of data which can be written to the file system with one internal command). This new FBox library is available for PG5 1.4 and for PG5 2.0 (2.0.210)

With the help of the FBox "Log to file" or "Log to file advanced" it's possible to store data to the filesystem of the PCD.
These FBoxes permit the user that information is written according to his needs (formatting) into the file.
Older FBoxes have the limitation that only 255 characters could be written at once in to the file.
With newer FBoxes we have increased the limit of the "Head" value and the "Val" value of the FBox "Log to File Advanced" from 255 characters to 3072 characters.

Version dependencies
Minimum requirement for the file system library to support the writing of 3072 characters:

• For PG5 1.4: $2.5.309
• For PG5 2.0: 2.6.200 (delivered with PG5 2.0.210) 

Remarks

• Minimal firmware version to use this new library is 1.10.16.
• The length of 3072 bytes concerns the effectively written data; in case template texts using e.g. $Rnnnn are used, the amount of written bytes count.
• When working with the System Funtions (CSF), the maximum amount is 255 characters.
   

Example
The text "Register 0 contains: $R0000" is written to a file:

• if register 0 has value 1234:           25 characters (bytes) are written
  (Written content: "Register 0 contains: 1234")
• if register 0 has value 1234567890: 31 characters are written.
  (Written content: "Register 0 contains: 1234567890")

If the file- or directory- names are not correct, this will lead to errors.

Directories
A directorie name needs always a slash in front of the name in the text definition:
"/Mydir"

Files
For file names the slash is not allowed:
"Myfile"

General
Note that the maximal length of filenames (including the extension etc.) is 23 characters.
"thisisthemaximum123.txt"

The maximal filename length on the filesystem is 64 characters.
M2_Flash:/Directory/File.txt

Be careful when implementing time and date to the filename with the syntax $D and $H. $D per example will use 9 characters. If the file has an extension as well, per example .csv, already 13 characters are used, means the filename itself cannot be longer than 10 characters.

Special characters like ä, ö, ü are not allowed on the filesystem.

Remark
Please note that "special characters" such as "ü", "¢", "ç" are not supported on the PCD file system. Additionally, the maximal file name lenght is 23 characters.

If a file- or directory- name is defined with a fixed length, it can lead to problems

Problem
The FBox indicates an error and the file or directory is not created on the filesystem

Reason
The file- or directory- name has to be defined with a default text size. If the text is defined as fixed and there are less characters than defined it is filled up with spaces. Since spaces are not allowed on the filesystem, this will lead to an error.

It is possible to change the configuration of the FTP server by placing a file FTPConfig.txt on the CPU.

With such a configuration file it is possible to modify the following parameter:

Attached to this FAQ an example of a configuration file with two new users is available.

This configuration file has to be placed in one of the following locations:

■ INTFLASH:/Config (integral on-board Flash)

■ WEB:/WEBPAGES (User program)

■ M1_FLASH:/Config (Flash device in M1 slot)

■ M2_FLASH:/Config (Flash device in M2 slot)

■ SL0FLASH:/Config (Flash device in I/O slot #0)

■ SL1FLASH:/Config (Flash device in I/O slot #1)

■ SL2FLASH:/Config (Flash device in I/O slot #2)

■ SL3FLASH:/Config (Flash device in I/O slot #3)

When the winter / summer time changed has been configured in Heavac Init Fbox and/or in the Device configurator of PG5 with SNTP time zone, also depending of the IP connection it can happen that the summer/winter time change doesn't work or is performed with 2 hours (instead of 1 hour)!

In order to avoid these problems the Heavac Lib has been modified.
It solves the problem of double summer-winter time changes if the summer/winter time change is defined in the ‘Heavac Init' FBox as also a timezone is defined in the Device Configurator.

Details:
On NT-Systems, since FW version 1.14.00 it's possible to configure a time zone in the device configurator of PG5 which does include the summer-wintertime change.
To avoid the clock time to skip 2 hours instead of 1 you should not activate the summer-wintertime change in the ‘Heavac Init' FBox if you have defined a time zone in the Device Configurator of PG5.
Otherwise both, the ‘Heavac Init' FBox and the device configurator settings does change the time for 1 hour which lead to the situation that the time new time is 1 hour to early/ to late.

The Summer/Winter indication returned by the FBox ‘Clock-Read' will not be updated in this case.

Since Heavac library version $2.7.150 and PCD FW version 1.20.00 the configuration of the time zone is automatically checked from the PCD in runtime and the summer-winter time change option in the ‘Heavac Init' Fbox is automatically de-activated if a time-zone has been defined in the Device Configurator. The Summer/Winter indication returned by the ‘Clock-Read' FBox will be updated according to the state handled by the FW.
Conclusion:
If you have a firmware in range 1.14.xx or 1.16.xx you should update to the FW version 1.20.xx (or newer) to have a full and correct functionality of the clock FBoxes in Heavac and the Hevac library 2.7.150 or newer have to be used.

Note also that the text in the adjust window of all ‘Heavac Init' FBoxes have been changed from ‘Disabled' to ‘Device Configurator' and a remark has been added.

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
  

When using the PCD1.M2xx0 the option "Automatic Reset" of the Heavac FBox library is not working.

RAM DBs/Texts once defined are not changed when downloading the program with PG5.

Symptom
The FBoxes from the Heavac library (as well as the ones from the DDC Suite) are not reset after a download of the program to the PCD. This is not even the case if the option "Automatic Reset" is enabled.
A possible consequence may be that the times configured in a clock FBox are never set correctly (unless you execute a manual reset of the Heavac Init FBox).

Also it is possible that baud rates don't change after downloading a program (with a new baud rate) because the SASI texts are not updated after download with PG5. The same error can also cause that a changed recipient in an email FBox is not updated and the FBox shows asterisks as output.

Reason
The reason for this phenomenon is that PG5 2.0.150 with patch 1 applied does not initialize the RAM DBs (on which the functionality of the "Automatic Reset" is based).
The problem appears also when having PG5 2.0.150 with Patch 3 installed, that texts once defined do not change.

Solution
In order to solve this issue please install the patch 4 for PG5 2.0.150 by executing the following steps:

• Install PG5 2.0.150
• Install patch 4 for PG5 2.0.150
• Re-download your project; from now on the "Automatic Reset" from the Heavac library (which is also applied to the DDC Suite FBoxes) is working correctly.

Remark
Plase note that this FAQ has been updated; At the time the FAQ has been released patch 2 was mentioned, but in fact patch 4 is required.

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

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

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

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\

Error code 2144 appears when trying to send a SMS in case the format of the phone number of the service center is not entered correctly.

Symptom
The Error code 2144 is indicated by the "Call SMS" FBox when  trying to  send  an SMS.

Reason
This error can be generated in case the SMS server number is written in the format "0041794999000" but it should be written as "+41794999000":


Solution
Please avoid the leading zeros and use the plus-sign instead.

In some PCD3 WAC projects where the PPP- and GPRS-diagnostic FBoxes of the Wide Area Automation library (WAA library) are used the following problem was observed:

After program download and setting the PCD to run, the FBoxes are active without any error but the output values of the FBox "GPRS diagnose" is 0 even if the modem is initialized.

Symptom
In some projects where the PPP- and GPRS-diagnostic FBoxes of the Wide Area Automation library (WAA library) are used the following problem was observed:
After program download and setting the PCD to run, the FBoxes are active without any error but the output values of the FBox "GPRS diagnose" is 0 even if the modem is initialized:


Reason
The reason for this situation is that the FBox from the library version 2.6.150 has expected a "Clean All Elements" in order to correctly initialize.

Solution
Please update your WAA FBox library to version 2.6.151 or later and re-build / download your project. This FBox library version can be found on the support site.
In case it is not possible updating the FBox library, please execute a "Clean All Elements" before running the PCD (e.g. with the Online Debugger).

Remark
This FBox library version will be part of patch 2 for PG5 2.0.150.

With PG5 2.0.110 Patch 2 it is not possible using special chars like + for the phone number

Problem
If a number (per example for the SMS service center) is entered with the country code (+41). The + is not accepted anymore. The error message Error 93: Invalid value is displayed. This can lead to problems when importing a project from PG5 1.4.

Solution
We will correct this in future versions. As a workaround the + can be replaces by a !

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.

If the modem is connected to the PGU port the handshake needs to be "FULL" in PG5 2.0. In PG5 1.4 it worked fine if the handshake was "Default".

Problem
When importing a Modem project from PG5 1.4 to PG5 2.0 it can happen that the modem on the PGU port does not work anymore. Or if you are creating a new project with default settings it won't work as before.

Reason
In PG5 2.0 it is necessary to set the handshake in the Modem Driver FBox to "Full". In PG5 1.4 it worked with the "Default" settings.

Solution
If the modem is connected on the PGU port, set the handshake to "Full" in PG5 2.0.

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.

The Poll SMS Fbox shows the mobil phone number but display No message. The message from the mobil phone isn't received or can't be executed properly. Some time it is executed once it has been send a second time but it takes a lot of time....

This problem is caused when too many message are contained on the SIM card used in the  GSM Modem. The Poll SMS Fbox get confused when the SIM card contains  too many texts. The last received message is deleted once it has been executed but the messages already present on the SIM card can not be deleted!

Solution: Put back the SIM card on a mobil phone and delete all messages!

Please note that due to the evolution of our mobile phone, it is not possible to delete sms  with a smart phone. You will have to use an older phone. By older phone is supposed to be a phone that still store sms on the sim card.

Example Nokia 6210

In the case you do not have an old phone at your disposal, it is still possible to delete them by using commands on a serial line connected to the modem.

You will need the following: 

1 PC with a RS-232 line

1 serial cable 1:1

1 terminal software. If you do not have one, we suggest you to use the puTTY

the.earth.li/~sgtatham/putty/latest/x86/putty-0.66-installer.exe

The command

AT+CMGL="ALL"

shows the messages on the SIM.for example:

+CMGL: 1,"REC UNREAD","+31628870634",,"11/01/09,10:26:26+04"

This is text message 1

+CMGL: 2,"REC UNREAD","+31628870634",,"11/01/09,10:26:49+04"

This is text message 2

Then, you will have to execute the following command in order to delete messages

AT+CMGD=1

OK

AT+CMGD=2
OK

************************

Note: There is a GSM modem programming example on our web site for PCD3.M with sending SMS and DTMF fonction using Poll SMS Fbox. (see under Getting Started)!

https://www.sbc-support.com/en/services/archive/getting-started/programm-examples/pg5-20/communication/

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.

Because the energy meters have a slower S-Bus interface the "SASI S-Bus Master" FBox gets red when communicating with energy meters. This red LED can be ignored (or the FBox SEnergyInit can be used; this FBox does not get red on every retry but only if the Energy Meter does not answer at all).

Why  does the "normal" SASI S-Bus Master" FBox get red?
It is possible that an S-Energy Meter does not answer one Serial-S-Bus request from time to time (the retry of this request will be answered in every case). The "normal" SASI Master FBox does indicate such a retry with a red LED (which can be ignored).

What can I do against the red LED?
There are special FBoxes for the S-Energy meters with Serial-S-Bus. These FBoxes for the energy meter will remain green as long as the communication is working correctly (taking into account that a retry can happen from time to time). The performance of the S-Bus is only slightly decreased due to the retry time.



The minimal FBox library version which contains the "SEnergyInit" FBox

• PG5 2.0: 2.6.171 (file "Energy Meter S-Bus_V2_6_171_ml.exe") or newer
• PG5 1.4: 2.5.171 (file "Energy Meter S-Bus_V2_5_171_ml.saiazip") or newer

Please find the adequate FBoxes for PG5 1.4 and 2.0 to read the values of energy meters supporting S-Bus on our support site in section 'energy meters':
sbc-support.ch/Axx/Axx3_SBus.htm.  

Remark
Please note that the SEnergyInit FBox can only be used together with the AWD FBoxes (but not with "common" Send and Receive FBoxes for S-Bus).

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

Detail information:

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

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

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

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

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

Error description:

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

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

Solution:

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

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

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

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

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

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

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

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

Introduction

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

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

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

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

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

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

Fupla:

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

  
  

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

  
  

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

  
  

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

Web-Editor8:

• Generation of HTML 5 compatible web pages

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

Improvements:

Device Configurator:

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

FBox libraries

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

  
  

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

  
  

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

  
  

DDC Suite

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

And other improvements and bug fixes

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

Windows Start menu

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

Device configurator:

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

Fupla:

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

Web templates and Web Editor 8:

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

Wiring Check Tool:

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

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

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

And other improvements and bug fixes

New features of PG5 2.1.310

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

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

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

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

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

And other corrections.

New features of PG5 2.1.300

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

And some other improvements and bug fixes

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

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

And some other improvements and bug fixes

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

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

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

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

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

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

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

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

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

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

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

• Support of the PCD1.M2160

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

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

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

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

New features of PG5 2.0.110 (first official release)

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

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

The new features in detail

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

Restrictions of PG5 2.0 and PG5 2.1

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

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

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

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

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

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

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

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

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

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

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

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

If the PCD does have a FW 1.20.xx or higher and no time zone is defined in the PG5 device configurator, then the ‘Hevac Initx’ F-Box with version < 2.7.530 does not change the clock of the PCD if the winter/summer or summer/winter time change should be executed.
This problem occurs with all 'Heavac Init' F-Boxes (Hevac 4 to Heavac 8)

Correction:
The correction is done in the Heavac Library 2.7.530 and consist in:
The summer/winter time change is executed
The summer/winter time status in the F-Box is updated correctly   
The parameter ‘Automatic Change’ in the F-Box is forced to ‘Device Configurator’

To fix the problem, do load the F-box library 2.7.530 or later from the update manager, update the F-Box if it’s required and compile the PG5 project and download the project to the PCD