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

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

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

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

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

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

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

Example
Definition of the initial values:

Actual online values:

Upload function:

DB with new initial values:

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

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

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

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

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

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

PG5 does not change the TAPI settings of Windows.

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



 

PG5 does apply the following rules:

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

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

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

The product range PCD7.D7xx will be discontinued in 2011/2012 (we expect to be able to deliver the actual range until end of 2012); the repair service is guaranteed until end of 2015.

Together with the product range PCD7.D7xx (also known under the name "VT also the following products (cables and the programming software for the "ESA Panels") are discontinued:

• PCD8.D81W (VTWIN) 
• Q-CVPLC04202
• Q-CVPLC01402
• Q-CVCOM11102
• Q-CVCOM25F8M
• Q.CVCOM25F9M
• Q.CVAD25M9M

Remark
The products of the PCD7.D7xx range do have an equivalent product code in the form of VTxxx:       
      PCD7.D790................VT50   (0500 00000)
      PCD7.D795................VT60   (0600 00000)

      PCD7.D700................VT150W (150W 00000)
      PCD7.D706................VT150W (150W 000DP)

      PCD7.D710................VT170W  (170W A0000)

      PCD7.D720................VT190W  (190W A0000)
      PCD7.D725................VT190W  (190W AP000)
 
      PCD7.D730................VT300W  (300W A0000)
      PCD7.D735................VT300W  (300W AP000)

      PCD7.D740................VT310W  (310W A0000)
      PCD7.D745................VT310W  (310W AP000)

      PCD7.D750................VT320W  (320W A0000)
      PCD7.D755................VT320W  (320W AP000)

      PCD7.D760................VT555W  (555W A0000)
      PCD7.D761................VT155W  (155W 00000)
      PCD7.D761ET..............VT155W  (155W 000ET)
      PCD7.D763................VT525W  (525W 00000)
      PCD7.D763ET..............VT525W  (525W 000ET)
      PCD7.D765................VT555W  (555W AP000)
      PCD7.D766................VT555W  (555W AP0DP)

      PCD7.D770................VT565W  (565W A0000)
      PCD7.D771................VT505W  (505W 00000)
      PCD7.D771ET..............VT505W  (505W 000ET)
      PCD7.D772................VT505W  (505W 000DP)
      PCD7.D775................VT565W  (565W AP000)
      PCD7.D776................VT575W  (575W APS00)
      PCD7.D776ET..............VT575W  (575W 0PSET)

      PCD7.D785................VT585W  (585W APS00)
      PCD7.D786................VT585WB (585W BPT00)
      PCD7.D786ET..............VT585WB (585W BPTET)
      PCD7.D787................VT595W  (595W APT00)
      PCD7.D787ET..............VT595W  (595W 0PTET)

      PCD7.D788................VT585W  (585W APT00)

      PCD7.F779................VTPROFI/DP (VTPROFI/DP)

The article 450748150 is no longer available from Saia-Burgess Controls AG as the according displays have been phased-out. However, this article can be bought from other providers (it is a Lithium battery 3.6V 1/2 AA).

Possible battery types instead of 4 507 4815 0:

Standard

• Type LS14250 from Saft

Alternatives

• ER 1/2AA S from Varta 
• ER3 STC from Maxell 

Since the production 16/07/2010 the displays PCD7.D761, PCD7.D763, PCD7.D771 have a new boot version it is required to use as well the new FW version contained in the latest PCD8.D81W Version 5.22 programming tool.

This new boot and FW correct problem of frozen screen as describt in FAQ 101196!

 The latest programming tool version is available under:

sbc-support.ch/download/pcd8_d81w_v5_22.zip

Remarks
If we download a project / firmware with the latest PCD8.D81W V 5.22 to a panel containing the older boot (display older than 16/07/2010) it will request the calibration at each start up.

So it is necessary to update the boot first as descript in FAQ 101196 (link below)!

The programming tool PCD8.D81W (VTWIN) is not supported on the Microsoft Windows7 operating system.

The software PCD8.D81W has been written at a time Windows7 did not exist and therefore it is not compatible with Windows 7 or Vista. At the moment there are no plans for changing the software in order to be supported on Windows 7 or Windows Vista.
However it is possible to install PCD8.D81W V5.22 (VTWIN 5.22) on Win7 PCs and work with it but you might be faced to some restrictions!
Known restriction:
The german characters "ä", "ö", "ü" aren't display in the editor and on the screen!
Workaround install another font for example Arial instead of ESA font (see attached document)!
Remark
Please note that the software Polymath from ESA is not compatible with the PCD7.D7xx displays from SBC. The only solution in order to program these displays without any restriction is not to use Windows7 or Windows Vista.

Yes, bu the resources have to transfer from the S-Bus driver to the Ether-S-Bus driver. See the description below

Procedure for the conversion of a PCD8.D81W project

1. Open the project and move the SBC S-Bus driver from ASP to MSP.

2. Convert the panel from Vxxx rev 4 to VTxxx ETH.

3. Drag and drop the driver "SBC Ethernet S-Bus" to the Ethernet port.

4. Open the project editor (double click on the VT icon).

5. Export variables into a CSV format file. 

6. Run Excel and open the CSV file.

7. Change the name of the source device into SBC:Ether-S-Bus_a (default name in VTWIN project).

8. Save and close the CSV file.

9. Import the CSV file in your project
   The  source device of the variables should now have changed.

10. Adjust the addresses of the memory areas.

11. Compile the project.

12. Close the VTWIN project editor.

13. Delete the driver "SBC S-Bus" from the MSP port.

14. Save the project.

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

The FBox library is attached to this FAQ

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

The display has a frozen screen (can be black if in standby mode) and can't be operated.

After a powerup the project's start page is displayed but it might be that the touch screen doesn't respond, because the calibration has been lost.

Solution
The booter and the firmware need to be updated.
If it isn't possible to force the display in transfer mode (download mode) it is necessary first to recalibrate the screen following the description. See FAQ 100868 (see link below).
All displays produced since 16/07/2010 have the new booter.

Procedure to update booter and firmware
If you use PCD8.D81W software version 5.22 skip to point 4 directly or point 5 if the display has already a new booter:

1.  Download the files attached to this FAQ and unzip the archives.
2. Copy the bootloader files 'BT525MTF.FIL' into the following folder:
   'C:\Program Files\SAIA\PCD8.D81W_51x\\boot\'
3. Copy the firmware files "VT525W.BIN" into the following folder:
   'C:\Program Files\SAIA\PCD8.D81W_51x\\firmware\'
4. The boot has to be sent via the bootloader download utility. In PCD8.D81W (programming tool; select the menu TOOLS / BOOT UPDATE-AUTOMATIC), enter the password 371013 and follow the instructions.
5. Open the project, compile it again and download it to the panel and active the download option 'Update operating unit firmware'. Remark: during the download the Boot version is desplayed: version 3.9
6. When the download has finished, after a powerup of the panel, please verify that the new firmware version is
   - 1.13 for PCD7.D763

Remark
Please note that the PCD8.D81W version 5.22 (VTWIN 5.22) CONTAINS this new booter and FW version!
It can be downloaded with this link:
sbc-support.ch/download/pcd8_d81w_v5_22.zip
It is mendatory to use this new FW only on panel having this new booter!

The 7.5" STN VGA displays PCD7.D776 and PCD7.D776ET have been discontinued and phased-out in November 2009.

As the manufacturer of the displays PCD7.D776(ET) has discontinued these types, SBC has phased out these products by November 2009.
As replacement product the MB Panel PCD7.D410VTCF is recommended.

Repair service
The repair service for the above mentioned displays will be maintained until 31.12.2013.

Remark
The ESA reference for the concerned displays is VT 575W APS00SA and VT575W OPSETSA.

When a PCD7.D7xx display visualizes the resources from several PCD stations (more than 3) over Ether S-Bus, some stations don't respond or respond with the ressources from other stations!

Symptom
When a PCD7.D7xx display visualizes the resources from several PCD stations (more than 3) over Ether S-Bus, some stations don't respond or respond with the ressources from other stations!
The PCD7.D7xx has been programmed with PCD8.D81W version 5.12 or 5.18.

Reason
This pheonomenon is caused by a wrong handling of MAC addresses in the Ether-S-Bus driver from the panel, the MAC addresses of the IP stations are not correctly updated.

Solution
By updating the driver of the concerned panel, the described behaviour can easily be corrected. Therefore please:

• download the attached version of the Ether-S-Bus driver (tcp_sbus.BIN)
• unzip it and copy it to:
  C:\Program Files\SAIA\PCD8.D81W_518\firmware\
• Compile the project and download it to the panel

It is possible that gaps in trend from logs are visible in the browser if the "load info & data" of the macro "Trend" is executed after a longer time interval than the data memory size available in the PCD allows to store!

Symptom
It is possible that "holes" in "HDLog to DB" trends are visible in the browser if the "load info & data" of the macro "Trend" is executed after a longer time interval than the data memory size available in the PCD allows to store!


Reason
The trend data's loaded from the PCD are stored temporarily on the memory of the Web browser.
The gaps can occur if the displayed time range on the browser is bigger than the data logging ringbuffer on the PCD.

Example
The log date size is 100 KByte data with a frequency of 1 log per seconds.
As 1 KB is 1024 bytes, there are 102400 bytes (100 x 1024 bytes) available for the trend.
1 log entry including time stamp (date/hour/value) takes 8 bytes.
As result, the available DBs on the PCD are filled up after 12800 seconds (102400 bytes / 8 bytes) which corresponds to 3h and 33 minutes. 

If the "load info & data" is executed at at 8.00 PM and again at 12.00 PM, a gap of 26.66 minutes will be displayed between the two ranges of logs.
At 8.00 PM the data's from 4.26.66 PM to 8.00 PM are loaded from the PCD, stored in the temporary memory of the browser and displayed on the browser.
At 12.00 PM, the data's from 8.26.66 PM to 12.00 PM are loaded from the PCD, added to the data's loaded before at 8.00 PM and stored in the temporary memory of the browser.
All data's (from 08.00 PM and 12.00 PM) are then displayed on the browser.
No recorded data is available between 8 and 8.26.66 PM because the data recorded in this period has been overwritten by the ringbuffer on the PCD.

Note
If the browser is restarted or if a "clear Log" is exectuted then the gap disappaers because the temporary memory of the browser is cleared and trend shows only the last data's (3h33.33) uploaded from the PCD!

It might happend that the touch area of a PCD7.D7xx panel doesn't respond anymore: In this case most likely the calibration has been lost and the touch area has to be recalibrated. In many cases the loss of the calibration can be avoided by a boot and firmware update (see related link below)!

Procedure for recalibrating the touch screen

• Switch off the panel
• Open the back cover (4 screws)
• Locate the single jumper J1 or J5 also indicated with C
• Move the jumper on the position C
• Swicth the power on
• Calibrate the screen with a fine pointer (on the cross 3 times)
• Swich the power off
• Move the jumper to the inital position
• Close the cover
• Switch the panel on

More details about the calibration with drawings for each panel type are available in hardware manual 405_1200_037 which is availbale on the PCD support page:
www.sbc-support.ch/pcd7/dxxx/d7xx/pcd7d7xx.htm


Important
Always use the latest PCD8.D81W version: the actual version is 5.22. In this version some boot / firmware versions have to be updated, see related link to the FAQs 100823 and 100716!

The display has a frozen screen (can be black if in standby mode) and can't be operated. After a powerup the project's start page is displayed but the touch screen doesn't respond, because the calibration has been lost!

Solution
The firmware (PCD7.D761) needs to be updated! The firmware update is done when downloading the project to the panel when the option "Update operating unit firmware" is activated.
If the display can't be forced in transfer mode (download mode) it might be necessary first to recalibrate it as explain in FAQ 100868 (see link below).
Use the latest PCD8.D81W 5.18 version which contains the newest FW!
If you haven't le possibility to use this version and you have the version 5.12 you can also add the new Fw in attachment. So, please execute the following steps:

• Download the files attached to this FAQ and unzip the archives.
• Copy the firmware files "VT155W.BIN" into the following folder:
  "C:\Program Files\SAIA\PCD8.D81W_512\\firmware\"
• Open the VTWIN project, compile it again and download it to the panel and active the download option "Update operating unit firmware".
• When the download has finished, after a powerup of the panel, please verify that the new firmware version is: 1.13.

New: Use the actual programming tool version PCD8.D81W V 5.18 which contains already the new firmware version. So no need to copy the fw files in attachment!

If alarms are activated on a PCD7.D776, it might happened that the screen loses its contrast over the operating time (it become darker and it is very difficult to see properly)!

• Update the boot loader by using PCD8.D81W; function "TOOL" --> "BOOT UPDATE" à automatic, use the code 371013.
• Open the project, compile again and then re-download the project.

Procedure for resolving the problem on a PCD7.D776 Rev. 2
In this case the device needs to be returned to your local Saia-Burgess Controls AG sales office for applying a hardware modification.

Remarks

Only in the programming tool version V 5.18 and newer, the new firmware and boot versions for the PCD7.D776 are included!

Web Editor 5.07 Project with Microbrowser V1.5.07.074

URL Jump doesen't work!

    Web projects built with WebEditor 5.07 need the Microbrowser Version V 1.5.076b7.

    Contact PCD Support

A VT Win project which had a size of a few MBytes becomes after storing more then ten time bigger (100-200MBytes).

Problem
The size of the project increase after storing to a really hughe size.

Reason
If unicode fonts are used which are not present in the PC the project can become so big because each character has to be stored as bitmap.

Solution
Check the fonts you are using and change to a font which is installed on the PC.

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

It is possible setting the clock of the terminals by passing a command from the PCD to the command area of the terminal.

There is an FBox library that was built for this task and eases the handling of the command area and the exchange of the data to be transferred.

Functional description
In general the clock of the intelligent terminals PCD7.D7xx can be set by writing the according command into the command area. The command area is an array of registers that are periodically read (and end interpreted) by the terminal (masters of the communication).
The attached FBox library is designed to interface with the command area of the intelligent terminals of the series PCD7.D7xx.
Please refer to the help for detailed instructions and examples.

Supported functions of the attached library
The attached library does not only allow setting the clock of the PCD7.D7xx but does also allow writing all other supported commands to the terminal. Depending on the type of the terminal this is e.g. deleting the alarm buffer, forced jump to a specific page/sequence, reading the status area etc. Please refer to the ESA manual for a list of the functions supported by your terminal.

Installation
For installing this library, copy the files of the attached archive into the folder "Libs\Usr" in your PG5 installation directory (default C:\Program Files\SAIA-Burgess\PG5 1_3\Libs\Usr\) and reopen Fupla.

Note
Please note that the FBox library can only work if the command area on the intelligent terminal is defined and the addresses of the command area is set correctyl on the terminal as well as in the FBoxes.

On a Profi S-Bus network when PCD7.D76_ terminals are connected to PCD3.Mxxx or PCD2.M480 PLC's over Profi S-Bus, the terminal loses the communication after some time and get even frozen. This problem is corrected in the new boot, FW and driver. The PCD8.D81 V 5.09 is needed , the attached files have to be copied in it (see procedure below).

It is also necessary to update the PCD3.Mxxx and PCD2.M480 FW with the version PCD3.Mxxx_023.blk / PCD2.M480_$27 or newer! Ask the PCD technical support or your representation for it!

Attached you can find the new boots, firmwares and driver that resolve the problem with the Profi-S-Bus network.
The booter file " BT155MTF" and BT525MTF have to be copied in the following folder
C:\Program Files\SAIA\PCD8.D81W 5.09\Boot

NEWS: In the latest version PCD8.D81W V 5.12 contains all thoses updated FWs, drivers and boots! Ask the technical support or your representation for it!

Since the version V5.07, it is possible to import the global symbols from a Saia PG5® project. Because the online help doesn't explain the import procedure correctly, you can find a corrected version attached to this FAQ!

If you need an update of your VTWIN version to this beta version, please contact your local Saia-Burgess Controls AG representative.
The beta version 5.09 is now available!

Newer intelligent terminals PCD7.D7xx do support Profi-S-Bus communication. This FAQ contains a document that describes the wiring for this communication.

In general the Profi-S-Bus communication is handled over the MSP port of the terminal. The attached document contains information regarding cable specifications, wiring information and possible lengths for the communication between a PCD and a VT.

Additial notes
No bridges on the 25 pin D-Sup (MSP port) are required.
Minimal version of the programming tool (PCD8.D81W or VTWIN) is 4.82. 

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

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

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

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

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

Probably through the download the FW wasn't installed properly. The terminal is blocked and stays in a loop, rebooting constantly.

Solution: After the 1st check page, when the screen displays "Wait for boot forced", press the screen in diagonal in order to put it in transfer page. Download than the programme and the firmware again!

After this operation the terminal should be return to work properly.

In order to connect PCDs and PCD7.D7xxET terminals on a remote TCP/IP network the use of an ISDN router possible. Internal tests have proven that this is no problem.

In order to get an overview of possible problems that might occur while setting up and working wiht a remote IP network connected via two ISDN routers or an ISDN TA (terminal adaper) and an ISDN router the following  constellations were set up:

§ix100165§

§ix100166§

In this test we used two AR140 ISDN routers (model number: AT-AR140S-513) of the manufacturer Allied Telesyn. This routers do have an integraded 4-port hub and a firewall (that wasn't tested in our test).

We didn't encounter problems for this constellation and found the following test results:

• It is possible to download projects of the PCD8.D81W (VTWIN) to PCD7.D7xx equipped with an Ethernet interface without someone on site

• The connection is established automatically in case of the use of two ISDN routers

• It is possible to download PG5 projects to PCDs (Ether-S-Bus stations) having an Ethernet interface

• A connection can also be established by first activating a dial-up connection and then adding a route (while the tests the added route over a Dial-up connection was removed at disconnecting)

• The networks can be defined by the user (no DHCP is required) on either network constellation

• Proxy servers and already existing network functions aren’t affected if properly configured (exception is the setup procedure of the ISDN routers due to the need of DHCP and set proxy addresses onto the routers!)

• All cables in the installation aren’t crossed (since the internal hub of the routers do feature an uplink which has to be set to “Hub” in case the connection PC-Router is going over an hub (hub-hub connection which would require a crossed cable if no uplink port were available))

For further information please refer to the test report (attached to this FAQ, file "ISDN-Router.pdf").

If the screen has not been touched for a long time, the screen of the display stays blocked. Only a powerup does reactive it!

In order to avoid this situation, it is necessary updating the boot with the programming tool PCD8.D81W.

Boot update procedure 

• For PCD8.D81w (VTWIN) version 4.81 (but older than V5.12), please copy the attached firmware files into the directory Firmware of the PCD8.D81W! Since version of PCD8.D81W  V 5.12  these new FWs are already included!
• In the PCD8.D81W software, choose the function "Tools" --> "Boot update" --> "Automatic"
• Enter the following code for the update
  371013
• Put the terminal im transfer mode
• Leave all settings with default values: Baudrate 9600...
• For more details see in the software manual under Boot Update.
• After the update of the boot, the programme and the firmware have to be re-downloaded to the terminal!

Remarks
If the displays PCD7.D785 / D788 are produced from june 2005 only the Firmware update is necessary (no boot update is needed)!
NEW: The new FW for PCD7.D785 / D788 is for all terminals (Rev. 4 or newer and Rev. 3 or older)

The "PCD driver" of the PCD7.D7xx terminals is not supported by all PCD systems.

Symptom
When the communication driver "PCD driver" is used in a PCD8.D81w project, the communication works on the PGU Port (port 0) of a PCD2.M110 (or a PCD2.M120) but not on the following systems: PCS1, PCD2.M150/M170/M480/M5xx0 or on a PCD3.

Reason
The PGU mode of recent PCD systems is no longer based on the P800 communication protocol (which uses the obsolete communication protocol "Mode D"). The recent PCD2 and the PCD3 use S-Bus on Port 0, and the PCD driver on the terminal uses P800 protocol. Because the PCD7.D7xx terminals use the P800 protocol if the "PCD driver" is selected, the communication does not work on systems developed after the PCD2.M110/M120.

Solution
So there are 2 solutions possible:

• Use the S-Bus driver on the terminal (recommended): In this case the project has to be adapted accordingly and an S-Bus connection cable is to be used (according to our Workshop Documents).
• Only for PCD2.M150 and PCD2.M170: Modify your communication cable (Pin 6 should not be used, Pin 6 of PGU port =0). In the PCD program you need to add a "SASI Slave Mode D" with the parameters: RS 232, 9600, Parity, 7-E-1.
  This solution can only be applied on PCD2.M150 and M170 systems, but not on other systems (because the Mode D is no longer supported).
  See attached document for wiring information in this case.

The PCD7.D7__ET offer the possibility to download the programme over Ethernet, the display switch automatic to download mode. This functionality exist already on the display produce after may 24th 2004. For the display produce before that date a Boot update has to be done first.

Use the menu "Tools" / Boot update / automatic of the PCD8.D81W V4.73 software, use the numerical code: 371013 and follow the instruction. Attention: keep the default setting baurate of 9600 Bauts for the download.

Afterward a FW download may be needed.

Some of the PCD7.D7xx terminals are available with a Profibus DP option, but this solution is obsolete and we recommend other solutions

The Profibus DP option has the disadvantage that the terminal is a slave and the PCD must organize the data transfer. This means

• that an FB per terminal is running in the PCD, which that is creating a significant CPU charge
• that the reaction time after user interactions on the terminal gets slow

We therefore recommend other solutions:

• Profi-S-Bus is to solution to be used together with new Classic products like the PCD2.M480 and PCD3.Mxxxx, it allows to have several terminals and PCD's on the same bus and the terminals are active participants
• MPI is the alternative for xx7 PCD's
• Ether-S-Bus or Serial-S-Bus connections are very often an alternative as well
• an ESANET network is sometimes interesting, but requires an independent network among the terminals. One terminal acts as Server for the others (Clients). The Server terminal must have two serial ports, one of which connected to the PCD via S-Bus, the other connected to ESANET

The Touch Screen Terminal loose the calibration from time to time.

If you remark this problem on your terminal, it will be nessesary to update the bootloader. This is possible with the version of PCD8.D81W VTWIN 4.73 (or newer).

Bootloader Download:
Choose in VTWin: Tools/Boot update/Automatic
All settings should have default values. Baudrate 9600...
Code for download: 371013
After this bootloader update you have to calibrate your terminal like describen in the manual and download the FW (see FAQ 100195)

A PCD7.D7xx Terminal can access several PCD's in an S-Bus network, it is as well possible to have one gateway station in the network and access PCD's that are located in a subnet. The response timeout has to be adapted accordingly.

If the PCD7.D7xx Terminal has to access S-Bus participants that are behind a gateway station, they are defined in the PCD8.D81W software as if they were in the same network. As passing a gateway station adds delay to the communication, the timout value (default 500 ms) has to be significantly increased (in the terminal) according to chapter 6.6 of the S-Bus manual. With PCD8.D81W versions until 4.66 the timeout can only be defined for the whole network, later versions allow to define the timout per station. The timout settings of the gateway and slave stations stay usually untouched.

There are a couple of common causes in case of a lack of communication. Please take care of the points mentioned below.

There are basically three sources of errors:

• the wiring: check the attached workshop document for details, remember that in most of the cases 3 bridges are necessary on the MSP. Without these bridges there is no communication
• the kind of protocol selected: always use S-Bus, don't forget to check whether the S-Bus Station address configured in the PCD8.D81W Software does match with the S-Bus address of the PCD(s)
• serial port settings: the PCD7.D7xx Terminals use S-Bus Parity Mode and are always master, per default at 9600 baud. Make sure the serial port of the PCD is configured or assigned in S-Bus Parity Slave Mode in the right baudrate

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

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

Edit Station, Channel List, Header

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

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

The first document describes the configuration between UNIGYR PRU and PCD2

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

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

   for more Help or application support you can connect:

   A&P Kieffer Omnitec Sàrl

   59, avenue Pasteur / BP 317

   L-2013 Luxembourg

   Tel.:  (+352) 474848-258

   Mail: martin.theis@kiffer-omnitec.lu

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

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

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

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

Profibus and Profi-S-I/O 

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

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

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


Signification of each bit (from right to left):

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

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

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

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

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

Remarks

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

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

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

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

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

The significations of the registers are the following:

Output registers: 

Description of the output registers:

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

Input registers:

Description of the input registers:

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

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

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

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

Table module status:

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

Table input status:

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

Table output status:

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

RUN = Yellow

ERROR = Red

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



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

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

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

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

Important points when commissioning the 6ES7

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

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

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

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

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

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

The configuration of the two devices has to match.

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

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

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

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

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

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

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

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

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

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

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

FW versions < 1.24d could have this problem. 

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

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

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

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

Solution
Please update the firmware of your

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

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

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

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

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

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

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

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

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

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

Rebuild and download also all programs.

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

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

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

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

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

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

Solution

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

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

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

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

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

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

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

The PCD2.M480 does support the following baudrates:

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

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

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

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

Solution

• Either update to the latest official FW for the PCD2

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

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

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

• a protocol analyzer specialized for Profibus based networks

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

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

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

doesen’t refresh automatically the diagnostic flags and registers.

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

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

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

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

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

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

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

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

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

Yes, it's possible.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Profibus and Profi-S-I/O 

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

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

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

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

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

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

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

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

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


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

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

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

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

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

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

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

Solutions

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

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

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

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

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

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

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

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

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

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

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

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

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

With the following relations:

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

and

a=exp(y*ln(x))


The following example is the operation 3^4.

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

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

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

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

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

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

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

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

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

 

Remarks

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

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

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

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

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

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

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

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

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

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

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

Solution

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

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

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

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

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

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

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


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

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

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

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


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

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

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

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

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

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

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

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

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

 Solution:

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

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

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

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

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

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

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

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

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

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

Install the corrected Alarming library 103001in attachment!

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

PG5 1.4.120 does contain a correction that avoids this problem.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Offset = Ymax - Range               

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

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

Offset = 500 - 625 = - 125              

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

S-Bus in Fupla

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

Conclusions

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

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

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

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

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

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

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

 §ix100290§

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

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

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

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

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

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

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

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

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

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

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

spare registers

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

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

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

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

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

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

• Save the file and re-open the Fupla Editor

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

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

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

Symptom

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

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

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

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

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

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

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

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

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

In this way each symbol can be access individualy.

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

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

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

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

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

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

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

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

• The programs get less modular

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

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

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

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

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

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

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

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

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

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

Diagram showing the difference between MC4 and MC5

§ix100137§

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

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

§ix100138§

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

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

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

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

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

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

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

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

Symptom

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


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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Project Manager:

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

Fupla Editor:

Symbol Editor Window:

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

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

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

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

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

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

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

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

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

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

As workaround you either could 

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

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

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

Assembling: praca.sfc

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

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

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

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

Procedure

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

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

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

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

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

Example
Example of the listing file for the Slave 3:

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

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

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

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

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

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

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

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

FW versions < 1.24d could have this problem. 

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

multi defined blocks
DBX2 in modul xxx.dp

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

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

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

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

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

Solution

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

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

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

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

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

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

Solution

• Either update to the latest official FW for the PCD2

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

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

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

§ix100177§ §ix100178§

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Remarks

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

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

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

Solution
Change to: "Buffer mark End":

It is advised to use the default setting whenever possible.

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

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

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


To modify the resolution of your screen make the following:

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

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

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

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

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

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

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

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

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



The correction is now available in SP PG5 1.4.300!

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

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

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

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

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

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

Problem
The error 31 appears on build:

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

Reason 

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

Solution

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

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

Install HMI Library $1.4.213 and HMI Editor $1.4.215.

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

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

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

 Solution:

Update the HMI Library with the $ version 14211 in attachement

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

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

www.engiby.ch 

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

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

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

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

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

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

Reason

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

Solution

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Reason
The problem is probably related to wrong Software Settings.

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

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

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

§ix100294§

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

This problem occurs with all FW version up to:

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

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

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

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

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

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

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

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

The functions:

- close buffer when empty

- move cursor down by screen

are not working correctly

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

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

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

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

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

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

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

Error messages like:

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

or

2. Unresolved Externals:

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Globals Symbols without name were not imported from HMI Editor.

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

These symbols will not be imported:
§ix100063§ 

These symbols will be imported:
§ix100064§

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

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

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

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

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

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

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

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

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

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

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

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

Explanation
The square brackets are used for the following cases:

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

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

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


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

Remarks

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

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

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

Solution

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

Remarks

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

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

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

Reason
This is a bug in PG5 SP1.4.130.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

• The programs get less modular

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

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

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

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

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

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

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

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

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

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

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

This problem is solved in PG5 1.3.

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

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

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

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

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

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

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

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

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

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

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

As workaround you either could 

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

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

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

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

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

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

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

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

Possible solution 

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

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

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


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

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

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

This is a bug in PG5 1.4 200 assembler.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Solution

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Restrictions

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

test SBUS station / CPU

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

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

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

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

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

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

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

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

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

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

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

Example such an error message:

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

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

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

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

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

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

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

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

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

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

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

Project Manager:

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

Fupla Editor:

Symbol Editor Window:

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

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

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

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

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

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

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

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

www.distrelec.ch

www.distrelec.ch

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

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

Cure:

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

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

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

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

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

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

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

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

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

Problem:

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

Solution:

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

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

Reason:

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

Solution:

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

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

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

Remark:

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

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

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

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

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

Your Webproject look like this:

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

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

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

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

Here is the description how to proceed.

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

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

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

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

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

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


Paste in the Web-Editor8 painter.


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



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


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


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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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


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

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


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

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

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



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

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



For Webeditor8 you must set up the following options:



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

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

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

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

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

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

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

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

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

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


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

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

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

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


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

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

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

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

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

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

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


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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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


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

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

"No license found on this computer, will run in DEMO mode." after the installation of PG5.2.0

Symptom
The following error appears when attempting to open the Web Builder from PG5 2.0 (on a Windows XP PC, 32bit):

“No license found on this computer, will run in DEMO mode. Limit is 2 HTML pages on the project”

Reason
The cause of this problem is that the library "SCRRUN.DLL" was not registered in Windows for some reason.

Solution
The SCRRUN.DLL can be registered by using the command "REGSVR32" from Microsoft Windows. "REGSVR32" (Microsoft© Register Server) is a command-line utility present in the Windows operating systems for registering and unregistering DLLs and ActiveX controls in the Windows Registry. The missing scrrun.dll is a Microsoft Script Runtime DLL Library.

Procedure for registering SCRRUN.DLL

• Open a Command Prompt (Start Menu --> Run --> COMMAND) and press ENTER
• Change directory to the WINDOWSSYSTEM: For XP systems, this is normally the folder:
  C:/WINDOWS/SYSTEM32
• Type the following command:
  REGSVR32 SCRRUN.DLL and then press ENTER
• You should see a successful confirmation message. If not, make sure you typed the command correctly (and that the command is executed in the correct directory).

If you open the standard status page on a PCD there are some additional parameters shown which aren't obvious.

You can display the status page of a PCD with the URL
(address of PCD)/status.htm



Please find the necessary informations in the following text.

Speed:
Time assigned to the Web Server task in milliseconds.
Range: 1..15
Default: 5
Requirements: PCD3Mxxxx, PCD2M5xxx, Firmware > 1.10.00

Priority:
Priority of the TCP Web communiction driver in the Web Server.
Range: 1..12 (1 means highest, 12 lowest priority)
Default: 10 (standard port) and 5 (command port)
Requirements: PCD3Mxxxx, PCD2M5xxx, Firmware > 1.10.00

The memory requirement of a "HDLog to File" FBox (log in csv format) is calculated as follows:

Possible records = 50% of memory capacity (in bytes) / required characters per record (in bytes). Further on the maximum amount of files per file system is to be considered (around 850 files per SD card).

Memory available on a 1 GByte SD card
1 GB SD Card (PCD3.R600 with PCD7.R-SD1024) has 1’073’741’824 bytes
Note: It is not recommended to fill the SD card completely; in general we recommend only using 50% of the available memory in case data is written (and deleted) regularly.
Further on the maxumum amount of files per SBC file system is 900 in total, and every directory counts as 20 files (because the folder "WEBPAGES" and "CONFIG" always exists, the maximum amount of files which can be created on a SD card is around 850 (860 to be precise).

Memory requirement of log files
The memory requirement of files created by the "HDLog to File" FBox (log in csv format) is calculated as follows:
Possible records = 50% of memory capacity (in bytes) / required characters per record (in bytes)

Examples

• Writing 30 values to an SD card
  In case 30 values are to be recorded:
  Each value has an average number of six characters (exp. 123,4).
  Each HD Log File FBox requires 30 characters for the date and timestamp.
  So 30 record sets, subdivided into 3 FBoxes requires about 270 bytes per record (rounded about 300 bytes per record, including date and time stamps).
  1 GB SD Card (PCD3.R600 with PCD7.R-SD1024) = 1’073’741’824 bytes
  This results in about 3,500,000 entries. Due to the fact that you should not fill the SD card over 50% there remain effective 1'700'000 entries.
  At a recording interval of 5 minutes the SD card has space for about 16 years, given one file per month is generated (--> 16 years * 12 files/year * 3 FBoxes = 576 files)
  
  

  Remark regarding this example
  In case one file is generated per week, after around 5.5 years it won't be possible creating more files because of the maxumum number of files per file system has been reached (5.5 years * 52 files/year * 3 FBoxes = 858).

  
  
• Writing 3 values to a PCD7.R550 memory card
  In case 3 values are to be recorded:
  Each value has an average number of six characters (exp. 123,4).
  Each HD Log File FBox requires 30 characters for the date and timestamp.
  So 3 record sets can be recorded with one FBox and requires 48 bytes per record (rounded about 50 bytes per record, including date and time stamps).
  1 PCD7.R550 module = 4'000'000 bytes
  This results in about 80'000 entries. Due to the fact that you should not fill the SD card over 50% there remain effective 40'000 entries.
  At a recording interval of 1 minute the memory module has space for about 1 month (28 days) 

The first generation of PCDs with integrated S-Web server did not support http-direct (e.g. the PCD1.M125, PCD1.M135, PCD2.M150, PCD2.M170, PCD2.M480) . Therefore the access of the S-Web Server must be realized using the free software "S-WebConnect" which is to be installed on a PC (accessing the PCD using e.g. Ether-S-Bus). Alternatively, an MB Panel can also access the S-Web Server (e.g. using Ether-S-Bus).

However, it is important to know that only one S-Bus client can access the S-Web Server over Ether-S-Bus at the same time!

Problem
By desing the S-Web Server of a PCD can only be accessed by one S-Bus connection per physical port (Serial-S-Bus, Profi-S-Bus, Ether-S-Bus). As result it is possible to access the S-Web Server over Serial-S-Bus and in parallel over Ether-S-Bus, but it is only possible to have one Ether-S-Bus Master which connects the S-Web Server.

That means it is not possible to access the S-Web Server of a PCD at the same time with the S-WebConnect (Ether-S-Bus) and the MB panel (Ether-S-Bus) because in this case the S-Web Server is accessed 2 times trough the same physical port (Ethernet Port).

Work around 
Here you can use the Web Connect as frontentd. The S-WebConnect will serialize the web requests and therefore avoid two parallel connections.

• The WebConnect creates only 1 connection to the Eternet Port of the PCD (Ether-S-Bus to a PCD1.M135 for example)
  --> there is no problem, because only one connection was created
• With the MB panel, instead to accessing the WebServer of the PCD directly (with the Ether-S-Bus protocol), the MP panel can be accessed indirectly via the S-WebConnect.

Example
For this example the following configuration is to be done in the MB panel configuration:

• HTTP direct
• Remost host IP of the PC (where the WebConnect is installed)
• as html file to open, you have to write: WebConnect_Connection_Profil/File_Name.html (htm)

For more information please refer to the manual for the "Web Server Classic" (26/790).

In case the dynamic space of registers is defined below 1000 or above 9999 the FBox HD Log to file cannot create the Logfiles correctly

Problem
If the dynamic space of registers is defined <1000 or >=10 000 the FBox HD Log to File is not able to create the Logfile correctly. The FBox is using interpreted text with $R commands. Due to a problem in the FBox this won't work for registers below 1000 since they only have 3 digits $Rxxx and the interpreted text needs 4 digits. Also in case the dynamic space is defined above 9999 the interpreted text won't work correctly, because the last digit is cut off by the firmware.

Solution
At the moment the dynamic space has to be defined >=1000 and <10 000 otherwise the FBox HD Log to File will not work correctly. The FBox library will be corrected for a dynamic space below 1000. To define the dynamic space above 10 000 a correction in the firmware will be necessary. As soon as a correction is available, this FAQ will be updated.

In some situations it is possible that the FBox "HDLog to File" is writing the same values several times (even if no change of value has been detected) to the *.csv file.

Symptom
When viewing the file creatd by the "HDLog to File" FBox it can be observed that in some cases several lines have been created (despite of the fact that the values did not change or the cyclic writing has not been due).

Reason
In case a "Write to file" command has been executed (and thus the buffer has been written to the file) and no new values have been written to the buffer, browsing the trends on the S-Web project could lead to re-writing the same (last) value to the file.

Solution
The FBox library version listed below do avoid the re-writing of an already written entry to the *.csv file.

• PG5 1.4.300: HDLog to file FBox library version 2.1.040
• PG5 2.0.110: HDLog to file FBox library version 2.6.150

There are different formats of GIF-files which need to be considered as not all formats/features are supported by SBC S-Web products.

In general there is a differentation between the GIF-file formats "87a" and "89a". The version "89a" includes all features from the version 87a but adds new features such as the possibility to provide animated graphics.
On all SBC products the format "87a" is fully supported while some features from the format "89a" are not supported on all devices (e.g. PCD7.D4xx).

Supported features on a MB Panel PCD7.D4xx

• Transparent GIF, if within the GIF less than 256 separate colours are used.
• GIF interlaced and non-interlaced – The GIF is drawn however in one go after full reception.

Restrictions related to *.gif files on the MB Panel

• Due to hardware relations, the QVGA Panel will not be able to display transparent GIFs
  
• Only the VGA Panel supports transparent GIFs in which case on the transparent pixel either the background or the inner colour setting is shown if this is configured. This inner colour drawing is also drawn on the full painter area and shown on the transparent pixel in the GIF image part that is below the outline under a dotted/dashed outline.
• A 3D border is not used.
• No split canvas / background and image frame handling (single full frame). For the canvas size the frame size is taken.
• No multi frame / image GIF file support (no animated / sequenced GIF). 
  For sequenced GIF file the first frame is taken. This may only partly display the wanted image.
  Note: The animated GIF macro from the S-Web Editor bases on a sequenced display of GIF files. The single gif files are not animated.
• No full colour support of the used 24 bit colours out of the given colour table.
  - On the VGA 16 Bit in a RGB 5-6-5 bit scheme is used, on the QVGA 8 Bit in a 3-3-2 Bit scheme is used.
  - For the colour rounding a grey scale nearest value is taken.
  - On the VGA the GIF uncompressing and this rounding can be checked using the screen dump feature
    that dumps the used RGB16, 5-6-5 code pixel code in an uploadable  uncompressed BMP16 file.
• No GIF meta information support, no GIF coded text support.

When using a GIF-files in format "89a" (incl. animation) the following phenomenons can be observed:

• everything works fine in the Applet 5.14.27 displayed on a PC

• display works, but no animation is done on a VGA MB Panel PCD7.D4xxV with firmware 1.12.11 and newer
  

• display doesn't work at all and only a rectangle with a red cross is displayed on a VGA MB Panel PCD7.D4xxV with firmware 1.12.11 and newer

Here are some possibilities how to generate or convert any type of picture into GIF format "87a"

• "GIMP": use the free graphical editor "GIMP" and save any picture as *.gif. If necessary select "fit picture" to not save an animated GIF when you're prompted. Just to be sure to generate a GIF file of format "87a".
  Get the most actual version of "GIMP" from the download website www.gimp.org/downloads/
  
• "Imagemagick": use the portable version of the conversion tool "Imagemagick" and run a batch-file to convert a whole directory of GIF-files into "87a" formatted GIF files.
  Download the portable version from www.imagemagick.org/script/binary-releases.php
  Copy the attached batch-file and the expanded zip file of "Imagemagick" into one directory. Also copy all *.gif files to be converted into the same directory.
  Start the batch file with a doubleclick. The converted GIF-files will be stored in a new directory named "gif87".
  

As soon as a curve is added to the HDLog to file macro it is not possible to compile the project anymore.

Problem
In Fupla the FBox HDLogFile was placed. In WebEditor the file is added under Project configuration and the according macro is added to a teq file. As soon as you add one trend-curve to the macro it is not possible anymore to compile the project. An errormessage similar to the message below appears:

Error 2009: WEB_PG.obj: Unresolved external symbol: __stc_id_0000C_var_00___SG_COB_Daten
Reason
This problem happens, if in Fupla the option "Use predefined symbols" is not activated. Since the HDLog FBox has internal symbols it is necessary to activate this option, to have the proper functionality.

Solution
Activate the option in Fupla under View/Options. In PG5 2.0 you have to activate the options:
Use predefined symbols: Yes
Delet internal: Yes
In PG5 1.4 you have to activate the options:
Use predefined Symbols
Delete internal symbols when the FBox removed

Then in the fupla you have to:
-right clic on the Fbox "HDLog" and choose "Add Predefined Symbols..."
-save the file

Then in the Web Editor you have to:
-remove the macro "HDLog"
-delete and select one more time the file *.HDF in the menu Project ->Configuration
-add the macro "HDLog" ,choose "Keep For All"

The alarm texts generated by DDC Suite are quit long and are in some cases not complete displayed with the default alarming macro. There's a description in FAQ #100711 how to modify the columns width. This FAQ contains an example which applies well to the screen dimensions of a VGA MB Panel PCD7.D4xxV.

Step-by-step example Web Editor 5

• In the Web-Editor 5 open the page with the alarming macro
• Double click the alarming macro, so that the window "GROUP" opens
• Select the tab "Cross Ref". In the cross reference list select entry "STRING "#sp;…."".
  The start position of the individual columns are defined in this string in the order: 
  StateColour, ID, Alarm text, Time on, Time off, ACK/NAK, Counter.
• Replace the default string by this string: "#sp;120,0,5,71,120,90,95\n" and don't forget to click 'update' to validate the changes.

Step-by-step example Web Editor 8

• In the Web-Editor 8 open the page with the alarming macro
• Rightmouse click in the alarming macro, choose "Cross Reference"
• Choose in the upper part for the "Filter by type" ALL
  
• Select in the Cross Ref Table the column with the Type "STRING "#sp;…."".
  The start position of the individual columns are defined in this string in the order: 
  StateColour, ID, Alarm text, Time on, Time off, ACK/NAK, Counter.
• Replace the default string by this string: "#sp;120,0,5,71,120,90,95\n"
  §Ix101640§
  

• The numbers entered stand for the percentage of the total width of the alarm list where the according column starts. So the "ID" column starts at 0% of the whole width of the alarm list, and the "Alarm text" starts at 6% of the whole width fo the list etc.
  The value 120 will disable the according column (in this example the "StateColour" and the "TimeOff").

As result, the alarm list will be drawn like the below attached screenshot:
§Ix101641§

Remark
Please note that the S-Web Editor 5.14.27 or later is required for this configuration (otherwise the "\n" will not work)

You can extend the HDLog FBox to log a maximum of 10 trend variables. If you want to log more than 10 trends, you'll have to place several HDLog FBoxes.

The HDLog FBox you place has to get a unique reference name. Because the CSV-file, that contains the maximum of 10 trend variables, is combined to this unique name. If you want to log more than 10 trends, you'll have to place an additional HDLog FBox with another unique name referenced. Because these additional 10 trends are logged into a second CSV-file combined to the second unique name. This means, that in one single CSV-file you can log a maximum of 10 trends.

There are some very useful recommandations / restrictions that should be respected when engineering an S-Web Editor project for VGA MicroBrowser Touch-Panels PCD7.D4xxV.

• The maximum size of a GIF-picture is 256 kB
• The maximum dimensions of a GIF-picture is 638 x 478 pixels
• It's recommended to use text fields that are around 20% larger than the text that is displayed in the S-Web Editor. For more details, please refer to the user's guide of the MB Panels on the support site.
• The maximum size of a displayed offline trend is 1024 kB
• A maximum of 512 painter objects can be displayed on one TEQ-view. Please note that also a simple line counts as an object. As reference: the "offline-trend" macro uses 40 objects
• According our experience, there can be displayed up to 320 registers or 500 flags on one single TEQ with reasonable speed
• One line in a TCR-file must not exceed 128 characters. This affects the choice of the size of a variable
• In a CSV-file, one line must not exceed 128 characters when programming in ASCII code, and 64 characters when programming in Unicode/UTF-16

When you use HTML tags in csv-file with the S-Web Editor 5.14.27, unused tags in *.csv files are detected (and the S-Web Editor asks whether to delete these lines in order to increase the performance of the panel in runtime).

In normal use you don't even remark this feature, because it's done in background when you delete a macro, for example.

Remark when using indexing
However, if you add on your own some HTML tags (i.e. when indexing variables with an expression like e.g. ...@Index_PPO@), the S-Web Editor detects that there are HTML tags that don't belong to any macro. It therefore asks you whether you want to remove these tags with the message:
'WARNING found HTML tags in csv files that are no more used in actual project. Do you want editor to delete those HTML tags?'
--> If you work with the above mentionned indexed variables, remember to click 'No'!

Remark
In the next service pack of the S-Web Editor (Version 5.14.30) this warning will have an option to hide.
This version is available in Service Pack 1 for PG5 2.0 (PG5 2.0.150). For PG5 1.4 the S-Web Editor version 5.14.30 can be downloaded from the support site.

The new WebServer 2 implemented in the PCD3 and PCD2.M5xxx supports caching and therefore the loading of the Java Applet can be avoided when reloading web pages. From firmware version 1.10.16 on you can profit of the caching possibility of the Java Virtual Machine.

How to activate caching?
To activate caching on the Java Virtual Machine you select on your local computer 'Start -> Settings -> Control Panel -> Java'. In the tab 'General', click on 'Settings' and under 'Temporary Internet Files' check the box for 'remain temporary internet files on the computer'.

Remark
Please note that in case an older firmware than 1.10.16 is loaded on the PCD, it might be that values of the web project are not refreshed correctly (see FAQ 100708).

When building a project with HDLog FBoxes the build fails with the message "Down.wsc Line xxxx Symbol not defined_stc_id_0016_var_00" or similar can be caused by an incorrect setting in the Fupla options.

Symptom
After having used the FBoxes from the family "Historical Data Logging" in a Fupla program for the use with a Macro for HD Log from file in the Web Editor the build fails. The error message indicates that symbols are not defined.

Reason
The HD Log FBoxes is creating automtically internal symbols for the use in the Webeditor macros. These symbols should be created automatically when adding the FBox to a project. If this is not the case the symbols are missing on build time and therefore lead to the error mentioned above.

Solution
you have to activate some options in the Fupla: Under View/Options:

• Use predefined Symbols
  If this is unchecked the FBox symbols are not created when adding the FBox. Make sure this optoin is checked!
• Delete the internal symbols when the FBox removed
  If this is unchecked the internal symbols stay in the symbol list, even if the FBox is removed from the project. It is recommended to have this option checked, too.
  

Remark
If the FBox is already part of the project you can add the internal symbols to the symbol list with right click on the FBox and choosing "Add predefined symbols".

When trying to compile an S-Web Editor project on a PC running a Chinese Windows the error message "DBX initialization data too big" is displayed and the build fails.

Symptom
When trying to compile an S-Web Editor project on a PC running a Chinese Windows the error message "DBX initialization data too big" is displayed and the build fails.

Reason
Due to a restriction of older versions of the S-Web builder it wasn't possible to compile a PG5 project containing an S-Web Builder project on a PC running a Chinese version of Microsoft Windows.

Solution
Since the version 2.0.100 of the S-Web builder it is possible to compile PG5 projects which contains a Web-Builder file on a PC with Chinese Windows.

Remark
Please note that the version Web Builder version 2.0.100 does not support "non ASCII characters" like for example Chinese characters on the *.htm/html or *.tcr files.
This means that it isn't allowed to define:

• a PPO name in the S-Web Editor which does contain a "non ASCII character" or
• a "PDP,,"-syntax wich contains a "non ASCII character" within an htm/html file

Where can I get the S-Web Builder version 2.0.100?
Please contact your local Saia-Burgess Controls AG representative.

Webpage doesn't get displayed at all when selecting an incorrect "base ppo name" in the trend macro.

Problem:
When trying to open the webproject the java applet is not loaded and the error message in the Java console is:
java.lang.ClassNotFoundException: IMasterSaia5_xx_yy.class.

Possible Reasons:
Wrong "Base PPO Name" selected.

Solution:
You have to enter the symbol name of the "Data DB" output of the "HD Init" F-Box.

In order to prevent that someone do copy the web pages which are stored on the file system (memory module) of the PCD, it’s possible to convert the content of the web-pages in a DB of the PCD with the use of the web-builder tool.

For S-Web editor project’s we do recommend to convert the *.teq files in the web-builder.

Using an indirect connection of the web-connect software on the CE web-panel (PCD7.D5xxx) it’s possible that a remote PC is able to load the web-pages stored on the PCD/PCS.

Requirement
On application the PCD/PCS is connected over serial line to a CE web-panel and the end user wants to display the web-pages stored on the PCD/PCS on the CE web-panel and on a remote PC.

Solution
With the help of the web-connect SW on the CE web-panel it's possible that the any PC on the TCP/IP network is able to establish an indirect TCP/IP connection to the web application stored on the PCD/PCS and to display the web application on the browser of the remote PC.

Open the web-browser on the remote PC and type the IP address of the CE web-panel, the connection name defined on the web-connect software and the name of the startpage in the navigation bar of the browser.
Example: 172.16.1.64/pcs/start.htm

172.16.1.64=IP address of the panel
pcs=web-conncect connection name
start.htm=name of the start page

Remarks
Instead of a CE web-panel there can as well be an ordinary PC, connected over the web-connect software to the PCD / PCS. The procedure is the same.
It is not possible to use a Microbrowser QVGA panel for this kind of connection.
The Microbrowser VGA panel doesn't support this functionality at the moment; but it's planned for the future.

When using text PPOs they have to be defined as STRING in the PPO list. Otherwise this can cause strange errors.