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

It’s possible, that after the installation of a PG5 library the warning ‚Missing dependency’ is shown in the library manager.

This message does appear if the new installed library does has a reference to a other library or to a special version of a library and this library or library version is not installed in PG5.

On the library manager the message is shown as:


On the message window of the PG5 project manager there will be a message which does indicate which library is missed and which version of the library is required.


The message could be like this:

Library Messages:
Warning 421: <$LibsDir>\App\Belimo.SAIALin: Library 'Belimo MP-Bus Library': Missing dependency: 'S-Fup Base Library;_SAIA_SFUPBASE;002007001,002007999;Saia-Burgess Controls AG'
Warning 421: <$LibsDir>\App\Heavac.saialin: Library 'Heavac library (HLK)': Missing dependency: 'S-Fup Base Library;_SAIA_SFUPBASE;002007001,002007999;Saia-Burgess Controls AG'

In this case it’s necessary to update the F-Box as shown in the message text.

The message text does indicate the needed F-Box Family and the version number.
In this case the F-Box library “S-Fus Base” has to be updated with a version between 2.7.001 and 2.7.999

The text SFUPBASE does indicate the F-Box library
The number after the library name does indicate the minimum required version of the library.
The number after the library name does indicate the maximum required version of the library.
The version indication is done in 3 digit format 002007001 -> 002.007.001 or 2.7.001

With the update of the BACnet Device Fbox from the Version 205002 to 205003, this Fbox creates a monitoring Object for BACnet, which needs symbols.

This symbols are not created automatically if the 'update Fbox' functionality of PG5 is used.

Symtom:
After an update of the BACnet Device Fbox, BACnet does't work anymore.
The error output of the BACnet Device Fbox is always high.
All Fboxes switch to a fallback mode without using BACnet.

Reason:
The reason is because of the missing symbols for the new monitoring object inside of the Fbox.
During the update of the Fbox, these symbols aren't created automatically.
Because of that, the control function of this Fbox does switch off BACnet because of the missing feedback.

Solution:
Add manually the symbols with a rightmouse click on the Fbox and click on "Add predefined symbols".
Click "ok" if a small window appears.

The library SfupBase V2.7.100  has been expanded.

From version  V2.7.100 we can use the PWM outputs of the following controllers:

The FBox that allow this is the FBox: PWM PCD1.M0xxx/M2xxx

This library is only available for PG5.2.0 To install it, please go to our support page: www.sbc-support.com/

With PG5 2.0.220 the EnOcean FBox library version 2.6.147 is delivered.

This FAQ lists the main modifications to this FBox library.

EnOcean library 2.6.147 (March 2012)

• New FBox "EOR 7x0 EVC":
  An FBox for the EnOcean gateway from Sensortec has been added
• FBox "Receive Any":
  The data outputs D0..D3 were labelled incorrectly (Data0 instead of Data3 etc.)

• New FBox:
  An FBox for the Thermokon SRC-Ethernet gateway has been added

Since 2011 Belimo has introduced in the market new type of valves (the VRP-M device),

they are not working with the old FBoxes MP VAV anymore therefore new FBoxes has been developed.

The FBox MP VAV20 where the 20 means second generation (2.0)

This FBox is included since the version $2.6.202 of the Belimo library for PG5 2.0

It's still possible to use the old type of valves, using the old FBox MP VAV and MP EPIV which is included in the same library but as general rule we recommed to use only the new VAV20 and EPIV20 FBoxes.

Remark:
The new MP VAV20 and MP EPIV20 FBoxes are only available for PG5 2.1 and PG5 2.0 but not for PG5 1.4

As general roule, it's possible to use the VAV20 and the EPIV20 FBoxes on all devices.

Remark about the VAV:
VAV wich are able to communicate with MP-Bus where introduced in 2000:
- The VRP-M device does require the VAV20 F-Box (to be able to use/set the Min/Max parameter)
- All other VAV devices can be used either with the VAV or the VAV20 F-Box
 
Remark about the EPIV device:
- All EPIV devices can be used with the EPIV or the EPIV20 F-Box.
 
How to know if the VAV does need the old or the new FBox?
The Belimo valve does have a serial number printed on a white label.
This number does consist on a 4 digit number with the format and is readable also in the master F-Box:
YYYWW-DDNNN-FFF-CCC
- If the code FFF is between 146 and 153 or the code is 158 or 160 then its necessary to use the MP VAV20 or MP EPIV20 FBoxes
- All other codes on the FFF field does indicate that the device does work either with the new or the old FBoxes.

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

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

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

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

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

In case an FBox library (or an IL program) uses a functionality which is not implemented in the PCD firmware, the PCD will not go in run but display the error message "SF not loaded" (e.g. in the PCD history or in the Online Configurator).

Symptom
After the download of a program a SBC-NT based PCD (e.g. PCD3) does not go in run but remains in halt. When going online with the Online Configurator a message "SF not loaded" is displayed.


Reason
The user program uses a functionality which is not implemented in the firmware (and therefore the PCD can not run the user program).

Solution
The solution is either updating the firmware, or avoiding the CSF which leads to the problem.
In case it is not know which CSF is responsible for the "SF not loaded", the SF library can be found based on the program line indicated by the Online Configurator (the program line is indicated with "Halt at xxx" in the Status; in the screenshot above the CSF is on program line 4). By using the Online Debugger, this CSF can be displayed by typing "DP4C10"):

   Display Program 4 Count 10 (Enter)
  

In this case, the CSF calls the SF library 26 (which is not implemented in the Firmware 1.10.51 which is used above).

How to know the functionality based on the library number?
Below you can find a list of the most commonly used System Function libraries (and in which FBox libarary they are used):

• SF library 0: S.SF.IP (e.g. Open Data Mode)
  Used by several IP communication drivers such as EIB/Net and for reading or writing the IP address of the PCD.
• SF library 2: System library
  Used by FBoxes for reading the Serial number
• SF library 4: S-Net library
  E.g. Used by FBoxes for Profi-S-Bus and Ether-S-Bus
• SF library 6: S.SF.DBLib (e.g. CopyTextBytes), previously the "ApplicationLib" for CopyText
  E.g. used by the Modem FBox library, HDLog to File library.
• SF library 7: File System library
  E.g. used by the FBoxes for the File System or "HDLog to File"
• SF library 9: IP Services (EMail, PPP, DNS, SNMP etc.)
  E.g. used by the EMail library and the WAA (Wide Area Automation) FBox library
• SF library 10: S-Web Alarming library
  E.g. used by the S-Web Alarming FBoxes and the DDC Suite
• SF library 13: Modbus library
  E.g. used by Modbus and the P-Bus FBox library
• SF library 19: LON over IP library
  used by LON over IP functions
• SF library 22: SPI framing protocol for PCD2/3.F2xx(x)
  e.g. used by the M-Bus library 2.6.100 and later
• SF library 23: Energy Manager library
• SF library 25: LON FT library
• SF library 27: ELine library for ELine modules
  Since PCD firmware version 1.24.xx

The single function codes (second line of the CSF call, "0" in the screenshot above) of the relevant libraries can be found in the definition files in folder
   c:\Documents and Settings\All Users\Saia-Burgess\PG5_20\Libs\SF\*.lib
(e.g. SFModbusLib_en.lib for the functions of the Modbus library.

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

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

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

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

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

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

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

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

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

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

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

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

The FBox library 'Modbus 1' from Engiby is obsolete and is replaced by 'Modbus 2.'

Therefore, only Modbus 2 licences can be ordered for PG5 2.0, PG5 2.1 or PG5 2.2.

For information regarding the differences between the 'Modbus 1' and the 'Modbus 2' library please refer to the this comparison page from Engiby (see link below).

Do I need to adapt my Fupla program in case it contains "Modbus 1" FBoxes?
No, to be able to keep old projects unchaged, a 'Modbus 1' library, version 1.85 (compatible to V 1.4, V2.0,  V2.1 and V2.2) is available from Engiby and use the same license key as "Modbus 2".
In other words, once Modbus 2 is installed, Modbus 1.82/1.83/1.84/1.85 can also be used without a new key.

• 'Modbus 1' library, version 1.82 is usable only on PG5 2.0
• 'Modbus 1' library, version 1.83 is usable on PG5 2.0 and PG5 2.1 (except PG5 2.1.300 and later)
• 'Modbus 1' library, version 1.84 is usable on PG5 2.1 and PG5 2.1 including PG5 2.1.300 and later
• 'Modbus 1' library, version 1.85 is usable on PG5 1.4, PG5 2.0, PG5 2.1 and PG5 2.2

Download
The 'Modbus 1' library version 1.84 can be downloaded from the Engiby homepage using the following link:

• Download Modbus1 (1.85)

As described in FAQ 101479 the version 2.6.xxx of the Engiby libraries is required for PG5 2.0.150 (PG5 2.0 SP1). This FAQ contains the link to download the libraries (in order to have a fast solution for concerned customer SBC exceptionally does have the possibility to provide these libraries).

Remarks

• Please note that the M-Bus library 2.6.014 available from this FAQ is not the latest version.
  In order to obtain the last version 2.6.1xx please contact Engiby directly (SBC is not allowed to distribute the last version which contains new features for free).
• Please do install the "M-Bus SBC version" OR the "M-Bus Engiby version" but not both in parallel; this could lead to inconsistent file combinations.

The FBox libraries from Engiby for PG5 2.0.110 can not be used in PG5 2.0.150 because of internal changes of PG5 2.0.150 which lead to the fact that the library installer is not able to register the FBox libraries.

Symptom
The FBox libraries from Engiby (e.g. the "Modbus 2" or "M-Bus" drivers) as well as the Add-on tools provided from Engiby for PG5 2.0.110 can not be installed on PG5 2.0.150.

Reason
Due to modifications between PG5 2.0.110 and PG5 2.0.150 the installer for the FBox libraries from Engiby (and probably also other third-party FBoxes) is no longer able to register the license properly.

Solution

• FBox libraries from Engiby
  The concerned libraries and Add-on tools are being updated in order to be compatible with PG5 2.0.150. FBox libraries from Engiby which are compatible with PG5 2.0.150 do have version 2.6.000 or later.
  For version 2.6.000 of the Modbus2 or the M-Bus library please contact Engiby or your local sales office. For other libraries or Add-on tools please contact Engiby for the latest FBox library version which is compatible with PG5 2.0.
• Add-on tools from Engiby
  Add-On tool that are not yet adapted to PG5 SP 2.0.150 will install a 5at file in a wrong folder. By moving the file manually you can solve the problem.
  The old folder used by PG5 2.0.110:  "c:\Documents and Settings\All Users\Application Data\Saia Burgess\"
  The new folder used by PG5 2.0.150 and later is "c:\Documents and Settings\All Users\Saia Burgess\LocalDir"
  Folder names can varry depending on Windows version and language. Folders may also be invisible or need administrator right.
  Procedure for installation of Add-on tools for PG5 2.0.110 in PG5 2.0.150:
  - Install the new PG5 SP2.0.150 according to the SBC's instructions
  - Installed the Add-On tool with the delivered Setup.
  - Find the *.5at file in the old folder
  - Move the file manually in the new folder
  - Restart PG5 SP 2.0.150
  The Add-On Tool should now be added in PG5.

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

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

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

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

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

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

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

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

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

Examples

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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


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

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

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

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

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

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

PG5 2.0 features a library import feature which allows importing FBox libraries from PG5 1.4. This feature can be used for user-written libraries which are not protected and do not require a specific license but it is not recommended for more advanced FBox libraries such as the ones from Engiby.

For ensuring a proper functionality of the FBox library Engiby tests the FBox library for each new version of PG5 and adapts the library in order to guarantee the compatibility with the new PG5 version. In order to take advantage from these tests and adaptions it is not recommended to import the FBox libraries but to use the updated version of the library provided by the author (e.g. Engiby).

How to update an Enbigy FBox library?
For optaining the FBox library version please contact Engiby (an overview of the available, updated FBox library can be found on the Engiby homepage as well, see link below).

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Remarks

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

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

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

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

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

There is no need to use a Tridonic interface.

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

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

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

Additionaly an USB interface is necessary.

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

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

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

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

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

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

Updates

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

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

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

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

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

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

The option has to be a constant.

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

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

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

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

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

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


Remarks

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

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

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

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

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

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

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

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

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

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

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

Because new instructions have been defined, user programs with Heavac Dialog FBoxes can in some cases no longer be built.

Symptom
Wenn building a fupla file using HeaDlg library a similar error message is display:
Error 1034: SASI_Dialog.fbd: Line 88: Missing operand, in Block: COB 0, Page: 1, FBox: SAS (Macro: __dlgcupdn, Line 45)
With PG5 1.4.300 the probleme isn't present!

Reason

The probleme is caused by the Macro "dlgcupdn" in head0.lib which used a reserved word "LT". When this macro was created (over 15 years ago) the word "LT" was not reserved. Now in PG5.2.0 the word "LT" can't be used any more which is the reason why the message "missing operand" appears.

Solution
Please copy the attached corrected file to the folder

C:\Documents and Settings\All Users\Saia-Burgess\PG5_20\Libs\App

Remark
This correction will be part of PG5 2.1.