When updating the Micro Browser Firmware to version 10701, the contrast settings in the monochrome panels PCD7.D457BTCF and PCD7.D457BMCF have to be changed. You'll have to increase the contrast for several steps.

With the new Firmware version we had to change the contrast adjustment on the Hardware and Firmware side to avoid any whistle (noise) and waves appearances.

Please note: The tone and brightness of each MB-Panel display is an individual characteristic and can be slightly different from one display to the other. At some contrast settings or with some images, flickering or differences in the brightness levels may appear.

If you are using a Microbrowser panel with HW-Version <$C you have to download all teq- and gif-files to the PCD.

When using the commande function which allows for example the writing of the hardware clock from PLC to Terminal PCD7.D7-- over Ethernet connection the 2 first words are swapped.

The FKeys flags available in HMI Editor (in Tag Internals) don't work on the PCD7.D16_.

Because those flags have a double functionality, they don't work for those small displays. It is necessary to use a bigger display as PCD7.D231 or PCD7.D232 in order to have this FKeys functionality!

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

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!

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!

It is possible to convert all the variable from a S-Bus driver to Ether S-Bus driver if an existing project has to be used on another terminal type (e.g. PCD7.D786 convert to PCD7.D786ET)!

Hereby the procedure to convert your project from VT585W (PCD7.D786) rev 4 to VT585WB ETH  (PCD7.D786ET) in order to save the addresses of the project variable when you change the driver from SBC S-bus to SBC Ethernet S-bus:

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!

If you would like to insert special characters like "é", "ö", "@", etc. in field "Multilanguage label" just press "F12" and a character table will apear.