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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Possible battery types instead of 4 507 4815 0:

Standard

• Type LS14250 from Saft

Alternatives

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

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

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

 The latest programming tool version is available under:

sbc-support.ch/download/pcd8_d81w_v5_22.zip

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

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

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

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

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

Procedure for the conversion of a PCD8.D81W project

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

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

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

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

5. Export variables into a CSV format file. 

6. Run Excel and open the CSV file.

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

8. Save and close the CSV file.

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

10. Adjust the addresses of the memory areas.

11. Compile the project.

12. Close the VTWIN project editor.

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

14. Save the project.

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

The FBox library is attached to this FAQ

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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


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

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

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

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

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

Procedure for recalibrating the touch screen

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

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


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

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

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

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

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

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

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

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

Remarks

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

Web Editor 5.07 Project with Microbrowser V1.5.07.074

URL Jump doesen't work!

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

    Contact PCD Support

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

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

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

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

Notebooks without RS232 COM-ports need a USB-Port and a USB to RS converter in order to connect a PCD over a serial line. Our experiences has shown that the driver software from some USB to RS-232 converters do not work in all cases (or not at all). This is why SBC tested various converters.

Please refer to the following list of converters which have been tested and found to be working fine with PG5 1.4, 2.0 and PCD8.D81W (for programming PCD7.D7xx displays, version V4.68 and later).

• Moxa UPort 1110 (RS232) and Moxa UPort 1130 (RS422/485)
  Works on Windows XP and Windows Vista for PG5 1.4 and PG5 2.0
  www.distrelec.ch
  
  
• BAFO BF-810   www.bafo.com
  works on Windows 98, 2000, XP
  
  
• ICP-DAS "I-7560"  www.redacom.ch
  
                               
• Converter USB2.0 to serial #61460 from www.delock.com
  tested on Windows XP, Vista and Windows7 (for Win7 the latest driver is required, see attachment)
  

Remark
Please note that a PCD8.K111 PGU programming cable is still required in order to connect in PGU mode to a PCD (the USB to serial converter does "create" an RS232 port on the PC but it does not cross the Rx/Tx lines which is necessary for RS232 connections).

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

§ix100165§

§ix100166§

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

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

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

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

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

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

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

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

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

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

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

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

Boot update procedure 

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

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

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

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

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

Solution
So there are 2 solutions possible:

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

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

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

Afterward a FW download may be needed.

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

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

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

We therefore recommend other solutions:

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

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

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

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

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

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

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

There are basically three sources of errors:

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

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

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

Edit Station, Channel List, Header

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

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

The first document describes the configuration between UNIGYR PRU and PCD2

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

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

   for more Help or application support you can connect:

   A&P Kieffer Omnitec Sàrl

   59, avenue Pasteur / BP 317

   L-2013 Luxembourg

   Tel.:  (+352) 474848-258

   Mail: martin.theis@kiffer-omnitec.lu

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

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

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

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

Profibus and Profi-S-I/O 

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

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

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


Signification of each bit (from right to left):

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

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

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

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

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

Remarks

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

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

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

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

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

The significations of the registers are the following:

Output registers: 

Description of the output registers:

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

Input registers:

Description of the input registers:

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

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

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

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

Table module status:

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

Table input status:

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

Table output status:

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

RUN = Yellow

ERROR = Red

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



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

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

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

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

Important points when commissioning the 6ES7

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

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

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

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

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

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

The configuration of the two devices has to match.

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

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

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

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

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

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

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

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

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

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

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

FW versions < 1.24d could have this problem. 

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

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

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

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

Solution
Please update the firmware of your

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

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

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

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

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

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

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

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

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

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

Rebuild and download also all programs.

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

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

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

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

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

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

Solution

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

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

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

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

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

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

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

The PCD2.M480 does support the following baudrates:

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

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

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

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

Solution

• Either update to the latest official FW for the PCD2

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

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

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

• a protocol analyzer specialized for Profibus based networks

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

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

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

doesen’t refresh automatically the diagnostic flags and registers.

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

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

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

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

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

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

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

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

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

Yes, it's possible.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Profibus and Profi-S-I/O 

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

In PG5 2.3.175, due to a bug in Web-Editor8 when compiling the Web-Editor8 project (as HTML5 or Hybrid solution), all horizontal and vertical lines of the Web-Editor project were ‘crooked‘ by 1 pixel and this information was stored in the Web-Editor project.

The bug was fixed in PG5 2.3.192 but unfortunately Web-Editor projects compiled in PG5 2.3.175 as HTML5 or Hybrid solutions, have to be reworked manually in PG5 2.3.192 (or newer).

The information about the issue and how to solve the issue is described on the attached document on the chapter ‘Web-Editor8; Horizontal and vertical lines are displayed with an offset’

For connecting a PCD to the internet a router is required. In case this router "knows" a DynDNS service, it is possible to find this this router by name.

The attached document contains an example of a step by step procudure for configuring dynamic DNS on a router (which "knows" DynDNS).

Remarks

• Note that the choice of the router or the DynDNS service from this document is sheer coincicence and does not mean that only this router works with PCD systems.
• Saia-Burgess Controls AG can not give support for the router configuration or the DynDNS setup. For support request regarding the router functionality or DynDNS please contact the according provider. 

The use of DNS (Domain Name Service) is very convenient for remembering the address of a host (e.g. a PCD3 connected to the internet with a DSL router). However, in some cases it is necessary to know the IP address of this host rather than the domain name.

How to translate the URL of a host to its IP address?
This task can be done by the tool "nslookup" which is installed on every Windows system:

• Open the DOS console (from the "Windows Start menu" select "Run..." and type in "cmd") 
• Type in the the instruction
  nslookup myname.dyndns.com.
  
  (don't forget the point after the URL)

As response you will receive the IP address of the requested name. In the screenshot above the IP address of the host "durrer.dyndns.tv" is 83.222.146.209.

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

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

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

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

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

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

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

The settings of the ADSL router which we do use in Murten are shown on the attached document.

Depending on your configuration and your needs you have to adapt the settings of the ADSL router.

The instruction nslookup allows to find out the TCP/IP address of a public e-mail server.

To know the e-mail address of a public e-mail server enter the following string on the command window of windows.

nslookup

After this you have to enter the smtp address of the e-mail server.
(On the example below it's the address smtp.green.ch)

The TCP/IP address of the e-mail server is shown on the next line below the name of the smtp server.
(On the example below it's the address 81.221.250.52)

§ix100292§

For our Webserver Demo installation we have worked with different ADSL Routers, none of which was perfect.

Our Webserver Demo installation is connected to the Internet via an ADSL Link on an ISDN line, which is provided by www.green.ch. This provider offers fixed IP addresses for a good price and can be recommended vividly to all Swiss Customers.

Criterias to choose an ADSL Router

• you need to know whether an analogue or ISDN version is required (depends on the telephone line)
• it must support "nailed up connections", which means that if the internet connection is not closed periodically and if for some reason the connection gets lost anyway, the Router re-establishes the connection
• it should contain a firewall
• it should support address translation, so you can route telegrams to port 80 to the PC with WebConnect and telegrams to port 5050 to a PCD directly. Other ports should be blocked inwards
• an integrated switch is quite useful

Zyxel Prestige 650 ME-I

• does not support nailed up connections, so you need to run a software on the frontend PC which simulates Web traffic (for instance come.to/StayAlive ), to make sure the installations stays available from outside. Without such a tool the Router closes the Internet connection after a while and you cannot access the frontend PC or PCD anymore until you create Web traffic on the PC
• user friendly configuration tool

Zyxel Prestige 650 H-I

• nice product with rich features, 4 Port Switch, supports nailed up connections. Didn't work in our installation, Web traffic was only possible from the LAN to the WAN, but not vice versa, independent of the firewall configuration
• user friendly configuration tool 

Devolo Microlink ADSL Modem Router

• nice product with rich features, 4 Port Switch, supports nailed up connections. Blocks periodically in our installation, a power down / power up is necessary to re-establish the Internet connection. Since we cut the supply of the unit for a moment at noon, the product works fine...
• very bad documentation, configuration tool is not user friendly, not suitable for people that configure an ADSL Router for the first time

General Remarks

• we bought standard low price Routers, which are designed to let a workgroup share an Internet connection. With the Webserver we use the product the other way around, which can cause problems with some products
• do not expect to get useful support from the suppliers of ADSL Routers in this class. If the product does not work in your installation, it is worth returning it and try another model from the same or from another manufacturer
• using an output of the PCD to cut the supply of the Router periodically has proved to be a good idea. The cheap routers are usually used in an environment where somebody can interact easily in case of problems (private use at home), for Webserver applications in the field this is not always that easy