No

Saia-Burgess Controls devices and software are not affected from Domain Name System (DNS) vulnerabilities published with the report name NAME:WRECK

-

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

‘An error occurred during the connection to the sever’

A modification on the configuration file should fix the issue.

Error description:

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

Solution:

To solve the issue perform the following steps.

Close the PG5 update manager.

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

Search at the end of the file the string:

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

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

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

Save the file and restart the PG5 Update manager.

 

If the error persists then please check:

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

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

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

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

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

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

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

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

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

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

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

We regret any inconvenience caused.

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

Update on 08.04.2020:

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

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

 

 

Symptoms

If we try to send an SMS message with a GSM modem and the FBox SendSms. The CallSMS FBox is in Error with the Error code 535.

Reason

Probably a wrong SMS Service Center Number is configured.

It can be a typing Error or the SMS Service Center doesn't fit to the SIM card because it was exchanged with the card from another provider.

 

Solution

Use the correct number. The number for SMS Server must normally be divided in at least 2 parts. Tf number 1 / Tf number 2. Each part of the number can have 8 digits. Keep attention that if you do copy / paste from numbers that are available e.g. in the FBox-help that all numbers are correctly copied. Keep attention to use the protocol “GSM Text” in the protocol option of the Call SMS FBox.

 

 

 

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.

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:

 

 

It's not possible to display the content of a help file which was copied from a other PC.

 

How to display .chm content in Windows 7

Problem:

When you open a .chm file, you see only the the tree structure and the index but there is no content.

Reason:

In Windows 7 there is a protection for files which where copied from other computers.

Solution:

You have to copy the helpfile to a local harddrive.
Then you have to open file properties and click on the Unblock button.

After this, it's possible to see the content of the help file.

 

For security reasons it’s not possible to change (or adapt) the destination IP-Address on the download window of the 'Download over HTTP/FTP' downloader like it would be possible on other PG5 download tools.

This restriction leads to the behavior that the program is always loaded to the PCD where the IP address is defined in the device configurator.

 

But if a user does need to adapt the destination IP-address of the PCD on the download window of the 'Download over HTTP/FTP' downloader, then he have to start the PG5 tool 'SftpDnld.exe' from the following locations:

- Windows 7: C:\Program Files (x86)\SAIA-Burgess\PG5 V2.1.200\SftpDnld.exe
- Windows XP: C:\Program Files\SAIA-Burgess\PG5 V2.1.200\SftpDnld.exe

And then it's possible to change the IP-address.

 

If on the PCD the FW 1.20.nn is used and if on the device configurator a time zone is defined then it's possible that on the S-Web Trend Macro the time stamp of the trend values are displayed with a time stamp offset.

 

Symptom
The time stamp of the trend values on a S-Web trend does not have the same time as the PCD time (read e.g. with PG5).
The time stamp of the trend values are time shifted for several hours (depending of the selected time zone configured in the PG5 Device Configurator)
Also other macros could have this problem if the PCD instruction SYSRD 7090 is used in the PCD code to read out the PCD time.

Reason
The problem is because on the FW version 1.20.nn the instruction 'SYSRD 7090' (=> Read UNIX TIME) give back the number of seconds since 1.1.1970 00:00:00 as UTC time and not as local time.
On FW < 1.20.nn the instruction give back the time as local time.

Other reason
The default Container on the Web Editor project 'MB_tmz_en' is set to 1.
If you want that the timestamp of the trending corresponds to the time of the PCD this Container should be set to 0.

Solution
In the FW 1.22.nn and later the timestamp is again in local time and a new instruction is introduced 'SYSRD 7190' which gives back the value of seconds in UTC.
The FW 1.22.nn will coming out end of June 2013

 

In PG5 2.0.220, there's a constellation that leads to the fact that you are not able anymore to re-open the Device Configurator. We found this constellation on a very few Windows XP and Windows 7 computers installation. It's always related to the computer itself and not to a specific PG5 project.

 

Symptom:
It's not possible to re-open the Device Configurator a second time.
If for example the Device Configurator was open and closed and after this Fupla was open, and then the Device Configurator should be re-open again, then this will not work.
Closing PG5 2.0 and re-open it doesn't help. From the Windows File Browser, it's still possible to open the Device Configurator. But not from PG5 Project Manager. To re-open the Device Configurator it's necessary to restart the PC.

Reason:
The Device Configurator task 'SDevConf52.exe' is still running.

Solution/Workaround:
Until we'll have a Software patch that correct this bug, you'll have to kill the task 'SDevConf52.exe' in the Windows Task Manager before you can re-open the Device Configurator or you have to restart the PC.

 

On the patch 1 of the PG5 2.0.220 there is a error which does lead to the situation, that data’s which are defined by the user as ‘data transfer array’ where no more exchanged between the PCD3.T66x and the smart automation manager. This error occures during compilation of the project, but doesn't corrupt the original project.

The configured I/O’s of the PCD3.T66x are exchanged without problems between the devices.

 

The patch 2 for PG5 2.0.220 will fix this error and will be available soon.

 

 

 

In case any of the dockable FBox Builder windows (e.g. Message Window) is not visible anymore, although its visibility state is switched to on, deleting the file FBE.saiaopt will solve the problem.

 

Sympton:
One or more dockable windows of the FBox Builder are not visible anymore, although they are activated in the View menu or via toolbar.

Possible reason:
Its not completely clear when and why this happens, but it has most likely someting to do with a crash of the FBox Builder during the work within a multi-screen enviroment.

Solution:
While its possible to edit the file FBE.saiaopt with a plain-text editor (such as Notepad), it may be difficult to find out the proper line(s) to edit. Thats why it is recommended simply to delete the whole file. Please note that the FBox Builder must not be running when FBE.saiaopt is edited or deleted! Be also aware that all individual settings (e.g. User Prefix, Project Directory, configured tools, etc.) are lost when FBE.saiaopt is deleted.

 

With the version 2.0.237 of the FBox Builder and PG5 2.0.220 Fupla Editor, it is not possible to Import a Fupla page (fxp-file) in the FBox Builder. The following error message is shown in the FBox Builder: Import failed.

 

 

 

This error has been fixed in FBox Builder 2.0.239 and the corrected version is available within Patch 1 for PG5 2.0.220. FBox Builder 2.0.239 (or newer) will also be included in PG5 versions > 2.0.220.

 

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

 

Upgrade from PG5 2.0.210 to PG5 2.0.220 does not let go online with a Project done with a previous version: Message "The program needs to be rebuilt and download" is displayed.

The same happens with the upgrade from PG5 2.0.150 to PG5 2.0.210.

This problem is coming from the background build.

 

Symptom
After the upgrade from PG5 2.0.210 to PG5 2.0.220 or from PG5 2.0.150 to PG5 2.0.210, PG5 does not let go online with a Project done with a previous version.

Direct after opening the old project, it is possible to go online with SPM without problem.
But if you open an editor, for example Fupla, the message "The program needs to be rebuilt and download" will be displayed.

Reason

This  problem is coming from the "background build": Before opening the Editor, if the backgound build is enabled, a check is done in order to detect if a new build is required. When opening a project done with an older version, a build will be required. A build is required because the version has changed, some new libraries can be updated. The result of the build will probably not generate the same code as with the earlier version, because of updated libraries, because of change in the code generation (Fupla code generator, compiler, linker...).
When the background build is done, the editor will detect the difference between the code generated and the code present into the PCD and will ask for a download in order to update the PCD program.

Workaround
The solution is to disable the "background build" (under menu "Tools" --> "Options"). In changing this parameter, when opening project done with older version, no build will be done and it is possible to go online with the editors.

Solution

This problem will be  solved in the next version of PG5.

 

When importing the symbols of a PG5 2.0 project into the OPC configuration the floating point registers are not correctly detected (if PG5 2.0.210 or earlier is used).

 

Symptom
When importing the symbols of a PG5 2.0 project into the OPC configuration the floating point registers are not correctly detected (if PG5 2.0.210 or earlier is used). Instead of floats they are configured as integers.

Reason
The symbol files generated by PG5 2.0.210 (and earlier) are missing the indication to be a floating point register (a {F} in the comment of the symbol). As this indication is missing, the OPC Server can not figure out it is a floating point value.

Solution
PG5 2.0.220 adds the indications again to the symbol files. If only an older version of PG5 2.0 can be used the following work-around could be applied: 

• the configuration can be corrected manually by modifying the "Type" to "Float":
  

Depending on the standard language configured on the PC some FBoxes are missing in the FBox selector when using PG5 2.0.210.

 

Symptom
When using PG5 2.0.210 it is possible that one or a part of the FBox are missing (no longer visible in the FBox selector). It is possible that the FBoxes were available in a previous version of PG5 2.0.

Reason
This problem is related to the language setting of the computer. It occurs when using a language who is not a "standard" language of the FBox. The "standard" languages are EN, FR, DE, IT.

Solution
As workaround you have to set a "standard" language on your computer. You can find this setting in the Control Panel under the menu Regional and Language.

Remark
This problem will be solved in the next version of PG5 2.0.

 

When trying to copy a smart Ethernet RIO station from the menu "Edit" --> "Copy RIO" in the Saia PG5® RIO Network Configurator the following error message appears if the RIO contains a Web Editor project!

 

Solution
Please use Saia PG5®2.0.210 which corrects will no longer be concerned of this problem.

 

On download of a big program with PG5 2.0.200 to a PCD1.M2xx0 or PCD3.Mxx60 the error message "Command not accepted: NAK response" can be returned by the downloader.

 

Symptom
When downloading a big program with PG5 2.0.200 to a PCD1.M2xx0 or PCD3.Mxx60 and in the option "Halt the PCD" before download is activated, the error message "Command not accepted: NAK response" can appear and the download is aborted.
§Ix101355§

Reason
The problem in this case is that the commanded restart of the PCD does take longer than PG5 expects. The restart is commanded in order to bring the PCD into a defined state during the download.

Solution
Please update your PG5 to version 2.0.210 or later.

Remarks

• In case it is not possible to use version 2.0.210, the following workaround could be applied:
  Activate "Stay in run" before download in the Download Program to solve this problem.
  §Ix101356§
  It isn't possible to select the option "Delete Backups from all Flash Cards" if the PCD is not halted (and the download is not possible if the PCD is halted before download due to the above described problem.
  In order to work around this trouble, just select "Backup to Onboard Flash" and "Backup to Flash Card" (if you have plugged a module e.g. in M1 slot). This way the backups will be deleted automatically before the new backup is created.
  
  
  
  

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

 

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



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

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

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

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

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

 

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

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

 

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

 

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


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

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

 

When updating the PCD firmware from 1.14.xx (or earlier) to firmware 1.16.27 the user program, its backup as well as the PCD configuration is lost.

 

Symtom
When updating the PCD firmware from 1.14.xx (or earlier) to firmware 1.16.27 the user program as well as the PCD configuration is lost.

Reason
The reason for this loss of the user program and the user program backup is that the onboard flash is reformatted. This task is executed right after the firmware update and is required for the generation of an internal (hidden) file system where the new user program backups can be stored.

Solution
In order to avoid data loss of the installation please execute the following steps for updating the firmware:

• For security reasons always update the firmware by an USB connection (and not over the network)
• Before updating the firmware, execute an "Upload all..." of the PCD (from the Online Configurator menu "Online"):
  
• Download the firmware 1.16.27 or more recent. Note that after the download the Error LED is lit and the Run Led blinks for some seconds; during this time the onboard flash is reformatted
• Download your *.im5 file you created with "Upload All..." 

Additional information

• Thanks to this reformatting the new "user program backup to file system" can be executed.
  This backup also includes the media content (R, F, T, C) and the configuration of the IP Enhancements (DHCP, SNTP) and the configuration of the FTP and HTTP server of the PCD. See FAQ 101622
• Additionally, the "Extension Memory Backup size" is now always 256 kByte, independent of the hardware. The available memory for the user program is not reduced by configuring the "Extension Memory Backup size". See FAQ 101623
• The S-Bus and IP configuration remain valid even if the user program is lost
• PG5 2.0.150 with patch 3 or later shows now a warning if the user program and/or the user program backup is lost before the firmware download starts
  

On a PCD1.M2 if you define 2 PCD2.W525 with the media mapping activated there will be an error after the download of the program and the PCD1.M2 will stay in halt.

 

With PG5 2.0.150 this is not possible to program 2 PCD2.W525 with the media mapping activated on a PCD1.M2. Even if you are using the Patch 4 it will not work.

After the download of the program you will get the following error:


This problem is solved with PG5 $2.0.182 or more recent.
We suggest to use PG5 2.0 Service Pack 2.

 

While using an SSD disk could improve the performance of PG5 2.0 (see remark below), we are in parallel working on increasing the performance of PG5 2.0 in general.

 

Remark concerning the usage of SSD disks
Our experience in the support team showed that exchanging the disk drive from the PC by an SSD drive does significantly improve the performance of PG5 2.0 (After replacing the HD by an SSD, opening files with PG5 2.0 is around 3 times faster). 
Unfortunately we also experienced several (3 out of 20 within 6 months) failures of SSDs. In case you intend to exchange your HDD by an SSD, it is strongly recommended to work on a backup strategy to avoid data loss in case of an SSD failure.

 

In PG5 2.0.150 sometimes the following error message appears on execution of "Copy user program to flash": "Failed to copy to/from flash. Check Flash Memory or card is fitted".

 

Symptom
When checking the memory map of the PCD in the "Online Debugger" after downloading a program the total size of the "User Program" (Code Size + Text Size + Extension size) differs from 1024 K bytes (1022 K bytes in the screenshot 2), this will lead to the following error message (and the backup of the program is not done):

Even the firmware filename suggests hardware rev. 'D' is needed this firmware is suitable for revisions 'A' and later.

 

With PG5 2.0 the current production firmwares gets also installed on the computer. They are located in the directory
"c:\Program Files\SAIA-Burgess\PG5_20\FW\Classic\" or similar.



The filename for the PCD2.M5_ contains a wrong minimum hardware revision description and is named "PCD2M5xx0_1.14.23(HW min D).blk" by mistake.
So in contrast to the filename the firmware 1.14.23 is applicaple to PCD2.M5xx0 with hardware revision 'A' and later.
The filename will be corrected with the next service pack for PG5 2.0.

 

Up to firmware version 1.14.23 the maximal amount of COBs (Cyclic Organization Blocks) has been 16. In firmware 1.14.23 the amoung of COBs has been increased to 32. Thus on PCD2.M5 and PCD3 and newer systems up to 32 COBs can be used (COB to 31).

 

Remark
Please note that PG5 2.0 Service Pack 1 (PG5 2.0.150) is required in order to program the COBs 16 and higher.

 

The windows Symbol Editor, FBox Selector, Page Navigator etc. are missing; how to get them back?

 

Problem
Somehow the property windows and the Symbol Editor, FBox Selector, Page Navigator etc. are no longer visible (or lost). If they are switched off and on under view, it doesn't change anything.
Restarting PG5 or the Device Configurator and also uninstalling and re-installing does not help to get the disappeared windows back.

Solution
If the windows got lost this way, it is possible to restore the default settings:

• Close PG5 2.0
• Make sure the hidden files are displayed on your PC (refer to the link below in case you don't know how to configure this)
• Browse to the following path:
  - For Windows XP:
    C:\Documents and Settings\username\Local Settings\Application Data\Saia-Burgess\PG5_20\
  - For Windows Vista, Windows 7:
    C:\Users\username\AppData\Local\Saia-Burgess\PG5_20\
• Arrange the files by name
• Delete or cut all files starting with SFup (about 7 files)
• Restart PG5 2.0
• The original settings are restored

Remark: On Windows 7 and Windows Vista, the folder "AppData" is a hidden folder. Please adjust the settings on your computer
as following:
Control Panel -> Appearance and Personalization -> Folder Options -> View -> check "Show hidden files, folders or drives -> Apply
This way round, the folder "AppData" will appear half-transparent and you'll be able to restore the default settings as described in this FAQ.

 

With firmware version 1.14.23 of the PCD3.Mxxx0 and the PCD2.M5xx0 the amount of available flags has been increased from 8191 to 14335.

 

Extension of amount of available flags on a PCD
With firmware version 1.14.23 the amount of available flags has been increased from 8191 to 14335. In order to use these flags, the firmware needs to be updated to version 1.14.19 or higher and PG5 2.0.150 (SP1 for PG5 2.0) is to be used.
In the "Build Options" from PG5 2.0 SP1 the range of dynamically used flags can be increased to 14335:


Supported hardware
The following hardware systems support the flag extension:

• PCD1.M2xx0
• PCD2.M5xx0
• PCD3 (see remark below)
• PCD3 Power CPUs (PCD3.Mxx60)

Remarks

• Please note that while the instruction list command set of the PCD fully supports the new range of 14335 flags, it is not possible to use them in "interpreted texts" (where "$Rnnnn" will be replaced by the value of the register with address "nnnn") because the syntaxt for the interpreted texs only supports 4 digits.
  This can lead to problems in case the dynamically addressed flags are used for the "HDLog to File" FBoxes for binary values. If this is the case it is recommended to configure the media allocation for dynamically addressed flags to a maximum of 9999.
• PCD3 systems with hardware older than "D" (and PCD3.M3020 and PCD3.M3120 with hardware older than E48) can not be updated to firmware version 1.14.xx because these platforms are not equipped with enough memory to hold the firmware 1.14.xx.
• When updating the firmware of the PCD from a version 1.10.xx to 1.14.xx the content of the memory is lost (user program, hardware configuration, register, flags etc.). Please "upload all" before updating the firmware (for that you can "download all" after updating the firmware. Note that you'll need the USB port after the update (as your S-Bus address might be gone). The reason for this loss of memory is that the memory structure has been changed in order to allow more flags.

PG5 2.0 shows an error that the DevTable.dat is missing. DP files cannot be created or opened anymore

 

Problem
It is not possible to open .DP files. PG5 2.0 is showing an error DevTable.dat missing.

Solution
Check under C:\Documents and Settings\All Users\Saia-Burgess\PG5_20\S-Net Files\
if the DevTable.dat is available. Most probably the file was renamed to DevTable.old. Just change the name back to DevTable.dat and it should work again.

 

In PG5 1.4 comments with more than 80 characters where possible, but PG5 2.0.110 does not accept these comments any more.

 

Problem
A project was imported from PG5 1.4 into PG5 2.0. When saving the global.sy5 file the following error message appears:
symbol table contains error
do you want to continue anyway?

Reason
This problem can be related to a symbol comment which contains more than 80 characters. In PG5 1.4 it was possible to define comments with more than 80 characters. PG5 2.0.110 is only accepting comments with up to 80 characters.

Solution
This problem is eliminated in the Service Pack 1 for of PG5 2.0 (PG5 2.0.150).
In case it is not possible updating PG5 2.0 the only solution to avoid this error message is to reduce your symbol comments to 80 characters or less.

 

With PG5 2.0 patch 3 an FBox library was not shown in the Library Manager after it has been installed (but the FBox installer claimed that the installation was successful).

 

Symptom
At the end of the installation of an FBox library for PG5 2.0 (with e.g. patch 3) the FBox installer claims that the FBox library is installed correctly but still the library in not shown in the Library Manager. Thus this library can not be used.

Reason
The reason for this phenomenon is that not all FBox files have been installed to the target installation directory (the file *.saialin is missing).

Solution
Please install patch 4 or later which corrects this issue. Patch 4 can be found on the PG5 2.0 section of the support site (see link below).

 

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
   
   

This FAQ contains an overview over the shortcuts of PG5 2.0 compared to the ones from PG5 1.4.

 

Common shortcuts
 

Commands	PG5 1.4	PG5 2.0
Open	Ctrl + O	Ctrl + O
New	Ctrl + N	Ctrl + N
Save	Ctrl + S	Ctrl + S
Print	Ctrl + P	Ctrl + P
Copy	Ctrl + C, Ctrl + Ins	Ctrl + C, Ctrl + Ins
Paste	Ctrl + V, Shift + Ins	Ctrl + V, Shift + Ins
Cut	Ctrl + X	Ctrl + X
Delete	Del	Del
Undo	Ctrl + Z	Ctrl + Z
Redo	Ctrl + Y	Ctrl + Y
Build Changed Files	F2	F2
Project Manager	Alt + F2	Alt + F2
Go Online	F9	F9
Run	F10	F10
Stop	F12	F12
Step by Step	F11	F11
Restart	F8	F8
Cross Reference	Ctrl + R	Ctrl + R

Symbol Editor shourtcuts
 

Commands	PG5 1.4	PG5 2.0
New Symbol	Ins	Ins (option)
New Group	Ctrl + G	Ctrl + G
Find	Ctrl + F	Ctrl + H
Filter	Ctrl + T	- (Symbol Nagivator)
Move Up	Ctrl + Up	- (toolbar)
Move Down	Ctrl + Down	- (toolbar)
Create Reference	Ctrl+B (status)	Ctrl+E (action)
Open Group	Ctrl+Space	Ctrl+Space
Select All	Ctrl+A	Ctrl+A
Add to Watch Window		Ctrl+W
Select Line		Shift+Space
Go Editing	Enter	Shift+F2
Move Down	Down- (toolbar)	Down,Enter
Address Selected symbols	Ctrl+Alt+F9	Ctrl+Alt+F9
Align Resource	-	Ctrl + U
Call Dialog (Text/DB, Tags)		Ctrl + Space

Fupla shortcuts
 

Commands	PG5 1.4	PG5 2.0
Synchron Data View	Ctrl + F9	Ctrl + F9
Select All	-	Ctrl + A
Symbol Editor	F5	F5
Page Navigator	Ctrl + I, Ctrl + Alt + 1 Ctrl + 1	Ctrl + I, Alt + F9 Ctrl+1
FBox Selector	Ctrl + Alt + 2, Ctrl + 2	Alt + F6, Ctrl + 2
Reference Window	Ctrl + Alt + 3, Ctrl + 3	Alt + F7, Ctrl + 3
Adjust Window		Alt + F3
Error Window		Alt + F8
Property Window		F4
Zoom Normal		Num /
Zoom In		Num +
Zoom Out		Num -
Zoom to Fit		Num *
Draw Lines	Ctrl + D	Ctrl + D
Bus Connect	Ctrl + B	Ctrl + B
First Page	Home	Ctrl + Home, Home
Last Page	End	Ctrl + End, End
Previous Page	PageUp	Ctrl + PageUp PageUp
Next Page	PageDown	Ctrl+PageDown PageDown
Jump to next window	Alt + F5	Alt + F5

Graftec shortcuts
 

Commands	PG5 1.4	PG5 2.0
Find	Ctrl + F	Ctrl + F
Edit Code	Enter	Ctrl + Enter, Enter
Element Properties	Alt + Enter	Alt + Enter
Symbol Editor	F5	F5
Block (PAge) Navigator	Ctrl + Alt + 1, Ctrl + 1	Ctrl + I, Alt + F9, Ctrl + 1
Sequence Navigator	Ctrl + Alt + 2, Ctrl + 2	Alt + F7, Ctrl + 2
Templates	-	Alt + F6
Error Window		Alt + F8
Property Window		F4
Find List		Alf + F3
Zoom Normal		Num /
Zoom In	Num +	Num +
Zoom Out	Num -	Num -
Zoom to Fit	Num *	Num *
Online Step In	-	F7
Select Mode	Esc	Ctrl + Shift + E, E
Mixed (Smart) Mode	M	Ctrl + Shift + M, M
Istep Mode	I	Ctrl + Shift + I, I
Step Mode	S	Ctrl + Shift + S, S
Transition Mode	T	Ctrl + Shift + T, T
Page Mode	P	Ctrl + Shift + P, P
Link Mode	L	Ctrl + Shift + L , L
Block Set Name	Alt + N	Alt + N
Block Renumber	Alt + R	Alt + R
Go to Main	Ctrl + Home	Ctrl + Home
Calling	Ctrl + PageUp	Ctrl + PageUp
SubPage	Ctrl + PageDown	Ctrl + PageDown

 

Currently the latest version of PG5 2.0 is the version 2.0.220.

 

The main modifications, new features and corrections of the individual versions can be found in the following feature list.

---

Service Pack 2: PG5 2.0.2xx

• Version 2.0.220 (PG5 2.0.220, April 12) 
  - added FBoxes for the new PCD7.L79xN
  - added FBoxes for EnOcean devices from Sensortec, see FAQ 101765
  - increased stability of Fupla, Symbol Editor and Graftec
  - improved "Upload all /download all" to support PCD1.M2
  - correction of Device Configuratior for encoder inputs of PCD3 Compact
  - the EIB/IP driver now allows modifying the IP address of the gateway in runtime
  - the stations in the TCP/IP Settings table are now enabled by default
  S-WebEditor 5.15.0221
  Together with PG5 the S-Web Editor has been updated to version 5.15.0221.
  This version includes the following updates (among others).
  - the loading messages during applet initialization can now be configured
  - under certain circumstances a Micro Browser could stop working if specific macros
    were present on the page, see FAQ 101724 
  
• Version 2.0.210 (PG5 2.0.210, October 11) 
  - T665|T666 diagnostic flags are correctly mapped (‘RIO.ManagerNotPresent’), FAQ 101652
  - Correction concerning the renaming of RIO devices (symbol update)
  - Correction in Fupla concerning the importation of templates, FAQ 101647
  - Improvements and corrections concerning for the support of Cyrillic characters in Fupla
  - Several corrections in order to improve the stability of Fupla
  - Correction of the IL Editor in order to open the *.inc files
  - Support for the PCD1.M2160
  - Corrections concerning the time zone in the Device Configuration, FAQ 101685
  - Improvement of the IP settings upload in the Device Configurator
  - WAC outputs are now working properly, FAQ 101659
  - The library 'Room L79x V2.6.121' and 'EnOcean SP2.6.130' are now installed
  - Corrections have been done in the help of several FBox libraries (images were missing)
  - Better handling for the downloading of large Web Editor projects into PCD1.M2
    and PCD3.Mxx60 devices (no NAK response), FAQ 101656
  - Improvement and corrections regarding the online alarming macro of the S-Web Editor, FAQ 101654
  - the "Select" button in the "Macro Find/Replace" dialog (FAQ 101643) is now present
  - Loop object and the count of input references are now correctly handled in the BACnet Compiler
  - DDC Add-on generates error message in case of duplicated web alarming texts, FAQ 101650
  - Improvements and corrections concerning for the support of Cyrillic characters in the FBox Builder. 
  
• First release of SP2 (PG5 2.0.200, July 11) 
  - Support of the Smart Ethernet RIO PCD3.T665|T666
  - Support for PCD3.Mxx60 (PCD3 Power CPU)
  - 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.

---

Service Pack 1: PG5 2.0.150

• Patch 5 for PG5 SP1 (PG5 2.0.150.500, June 11) 
  - The project import from PG5 1.4 projects modified the original project when 
    using patch 4(a), see FAQ 101628
  - In some situations the memory allocation on download of a project was incorrectly calculated 
  
• Patch 4a for PG5 SP1 (PG5 2.0.150.400, June 11)
  - Patch4a displays "SP2.0.150.400" in the SPM title bar (patch 4 shows "SP2.0.150.300") 
  
• Patch 4 for PG5 SP1 (PG5 2.0.150.300, June 11)
  - RAM DBs and Texts are correctly re-initialized after a program download to a PCD1.M2xx0 (FAQ 101541)
  
• Patch 3 for PG5 SP1 (PG5 2.0.150.300, May 11)
  - Firmware downloader now warns if the FW update leads to program loss
  - Upload all works now correct even if no BACnet project is stored on the R56x module
  - BACnet Configurator correctly exports client objects to CSV files
  - Conversion of double values in BACnet Configurator do no longer fail on french PCs
  - Default character set in BACnet Configurator is now ANSI
  - BACnet Configurator now creates a backup when saving the configuration  
  
• Patch 2 for PG5 SP1 (PG5 2.0.150.200, April 11) 
  - Correction for the usage of the PCD1.M2xx0 (FAQ 101541)
  - The result of the command "Read FBox Adjust Parameters" is now shown
  - Avoids the destruction of a project with very many symbols
  - Improved performance during build
  - The message "Program needs to be rebuilt" was displayed after opening the
     "Download Configuration" dialog box
  - The "Extension Memory Backup Size" was lost if the PCD memory is re-allocated
  - Update BACnet configurator for future BACnet firmware 1.16.xx (supporting BACnet 2008 Standard) 
  - The memory allocation was not always correctly calculated on download of the project, leading to the
    fact that a backup user program to flash failed in some cases  
  
• Patch 1a for PG5 SP1 (PG5 2.0.150.100, December 10) 
  - Corrects an issue that the patch could not be installed on Windows7 systems
    Otherwise the patch is identical to the patch 1. 
  
• Patch 1 for PG5 SP1 (November 10) 
  - Program download was not possible if flag > 8191 had first time initialization (FAQ 101497)
  - HMI Editor: Texts and constants could not longer be used
  - Fupla Editor: Layout problems when printing are corrected
  - BACnet configurator now supports 64 bit OS
  
• Release of SP1 (July 10)
  - S-Web and FTP Server and IP Enhancements can be configured in the
    Device Configurator, see FAQ 101464.
  - Increased amount of available flags on a PCD3 or a PCD2.M5 to 14335
    (instead of 8191), see FAQ 101447.
  - Support of new hardware (PCD1.M2120, PCD3.Mxx60)
  - Support of Windows Server 2008
  - Various improvements of stability 

---

First release: PG5 2.0.110

• Patch 5 (January 10)
  - TEQU statement was lost in-between $INIT and $ENDINIT statement
  - Various improvements of Fupla stability
  
• Patch 4 (December 09)
  - FBox libraries were not correctly installed with patch 3 
  
• Patch 3 (December 09)
  - Various improvements of stability
  - Old Adjust window can be used directly
  - Floating point values were not accepted in labels
  - FBox priority was not shown if FBox had a Name or Reference
  
• Patch 2 (October 09)
  - HMI Editor did not support external symbols 
  
• Patch 1 (September 09)
  - BACnet Compiler was not able to load public symbols
  

---

Where to get a detailed list of the modifications

For a complete list of the modifications, please refer to the "Help" button of the installer which displays a list of the modifications.

 

Due to the fact that the software "AVG Antivirus" is considering PG5 2.0 as virus, PG5 2.0 will not work properly on a PC with Windows 7 installed which is also running AVG anti virus software.

 

Symptom
After copy/pasting or importing a page in e.g. Fupla from PG5 2.0, this page will be corrupted (if the AVG Antivirus is running on this machine). This will lead to a failed build later on.

Reason
The sofware AVG Antivirus apparently is considering PG5 2.0 as a virus.

Solution
Currently the only solution for this problem is stopping the AVG Antivirus (or uninstalling it). This FAQ will be updated once another solution is available.

Remark
This behaviour could only be observed on Windows 7 together with AVG Antivirus.

 

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.

 

The BACnet Configurator distributed with PG5 2.0.110 contains references to dll libraries at a wrong place, which leads to error messages like "Cannot find SymDlg52.dll". Installing the patch below cures the probem. Attention: PG5 version 2.0.110 only.

 

Symptom
The BACnet Configurator distributed with PG5 2.0.110 contains references to dll libraries at a wrong place, which leads to the error message "Cannot find SymDlg52.dll".

Solution
Please install the patch 1 for PG5 2.0.110 which is available on the support site in the menu "Product Information" --> "Software" --> "PG5 2.0"

Remark
The mentioned patch applies to PG5 version  2.0.110 only.

 

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)

---

Improvements on SP 1 for PG5 2.3 (PG5 2.3.162)

The following short list gives an overview of the 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:

Graftec:

On PG5 2.3.162, the Graftec Editor supports now the complete range of functions and it's possible to use Fupla pages on Steps/Transitions.

The Symbol Editor has been removed from the Graftec editor. The Fupla or IL editor now has exclusive access to the symbols. 
Graftec editor is for editing the Graftec state machine, not the program itself, so it does not need the program's symbols.
To edit symbols, open a Step or Transition in Fupla or IL.
When symbols are modified, changes are only made to the symbols in other Steps and Transitions when the editor's files are saved. 

Saving one ST/TR file will now save ALL the modified ST/TR files which are open for that Graftec module.

Project Generator:

The Project Generator Wizard is now available.

HTML5 Web-Pages on iOS:

Low performance on iOS devices:
Displaying HTML5 web-pages on iOS devices causes performance issues. 
It took a long time to load a new page if you click on a button that has a view jump. 

---

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)

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.

 

Yes, PG5 2.0 and PG5 2.1 are fully compatible with the 32 and 64-bit version of Windows Vista, Windows 7 ("Windows 7 professional" and "Windows 7 home premimum edition") and Windows 8.

PG5 1.4 is compatible with Windows 7 and Windows 8, but with some points to consider during the installation and operation (please refer to FAQ 100710).

 

Compatibilty with Windows Vista
Since Windows 7 and Windows 8 (like Windows Vista) does have more restrictive rules than e.g. Windows XP some adaptions in the default paths of PG5 2.0 have been applied (compared to PG5 1.x):

---

Paths used for Windows XP:

• Project directory
  Windows 7/8 does not expect users to write into a root folder in "C:\" like PG5 1.x did. therefore the new default folder is:
  for PG5 2.0: C:\Documents and Settings\All Users\Saia-Burgess\PG5_20\Projects
  for PG5 2.1: C:\Documents and Settings\All Users\Saia-Burgess\PG5_21\Projects
• Library directory
  Windows 7/8 does not expect users to write into the "Program Files" folder (which is done when installing a new FBox library by the user). Therefore the new default folder for libraries is:
  for PG5 2.0: C:\Documents and Settings\All Users\Saia-Burgess\PG5_20\Libs
  for PG5 2.1: C:\Documents and Settings\All Users\Saia-Burgess\PG5_21\Libs
• Local directory
  The license file (USER.KEY) and the '.5at' files used to register the add-on tools are in the following directory:
  PG5 2.0.110:                C:\Documents and Settings\All Users\Application Data\Saia-Burgess\PG5_20
  PG5 2.0.150 and later:   C:\Documents and Settings\All Users\Saia-Burgess\PG5_20\LocalDir
  PG5 2.1:                       C:\Documents and Settings\All Users\Saia-Burgess\PG5_21\LocalDir
• User specific settings
  The specific user settings for the different editors and S-Comm driver are no longer saved in the Windows registry but in the directory defined specially for this kind of data:
  for PG5 2.0: C:\Documents and Settings\"user name"\Local Settings\Application Data\Saia-Burgess\PG5_20
  for PG5 2.1: C:\Documents and Settings\"user name"\Local Settings\Application Data\Saia-Burgess\PG5_21
• Application directory
  The PG5 default installation path is in the same location as with PG5 1.x:
  for PG5 2.0: C:\Program Files\SAIA-Burgess\PG5_20
  for PG5 2.1: C:\Program Files\SAIA-Burgess\PG5_21
• Templates directory
  for PG5 2.0: C:\Documents and Settings\All Users\Saia-Burgess\PG5_20\Templates
  for PG5 2.1: C:\Documents and Settings\All Users\Saia-Burgess\PG5_21\Templates

---

Paths used for Windows Vista / Windows 7 / Windows 8:

• Project directory
  Windows 7/8 does not expect users to write into a root folder in C:\ like PG5 1.x did. therefore the new default folder is:
  for PG5 2.0: C:\Users\Public\Saia-Burgess\PG5_20\Projects
  for PG5 2.1: C:\Users\Public\Saia-Burgess\PG5_21\Projects
• Library directory
  Windows 7/8 does not expect users to write into the "Program Files" folder (which is done when installing a new FBox library by the user). Therefore the new default folder for libraries is:
  for PG5 2.0: C:\Users\Public\Saia-Burgess\PG5_20\Libs
  for PG5 2.1: C:\Users\Public\Saia-Burgess\PG5_21\Libs
• Local directory
  The license file (USER.KEY) and the '.5at' files used to register the add-on tools are in the following directory:
  for PG5 2.0.110:               C:\Users\Public\Application Data\Saia-Burgess\PG5_20
  for PG5 2.0.150 and later:  C:\Users\Public\Saia-Burgess\PG5_20\LocalDir
  for PG5 2.1:                     C:\Users\Public\Saia-Burgess\PG5_21\LocalDir
• User specific settings
  The specific user settings for the different editors and S-Comm driver are no longer saved in the Windows registry but in the directory defined specially for this kind of data:
  for PG5 2.0: C:\Users\"user name"\Local\AppData\Saia-Burgess\PG5_20
  for PG5 2.1: C:\Users\"user name"\Local\AppData\Saia-Burgess\PG5_21
• Application directory
  The PG5 default installation path is in the same location as with PG5 1.x:
  for PG5 2.0: C:\Program Files\SAIA-Burgess\PG5_20
  for PG5 2.0: C:\Program Files\SAIA-Burgess\PG5 V2.1.nnn
• Templates directory
  for PG5 2.0: C:\Users\Public\Saia-Burgess\PG5_20\Templates
  for PG5 2.1: C:\Users\Public\Saia-Burgess\PG5_21\Templates

---

PG5 2.0 and 2.1 does no longer write into the Windows registry during normal operation.
Therefore it is possible running PG5 2.0/2.1 as "common" user (for PG5 1.x you had to be "power user" or "administrator").

Remark regarding 64-bit version of Vista and Windows 7
In case you need to install PG5 2.0/2.1 on a PC running a 64-bit version of Windows Vista, Windows7 or Windows Server 2008, please refer to FAQ 101463 (see link below).

 

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

 

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.

 

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

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.

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.

 

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)