Local FAQ CH
What information is needed by the support team in order to provide efficient support? (FAQ #101521)
In some cases the support team is asking you to provide more detailed information regarding a problem you report. This FAQ contains a list of relevant points which are most likely needed in order to professionally answer your support request.
Why this list?
This list has been compiled as we have recognized that we are often asking for more information if a support case is sent to us. By doing so, the solution of the support case often is delayed. Therefore we compiled this list; if a support case is fed in to us according to this list the support case will be more efficient.
As the kind of information is depending on the problem itself, you will find a general part (which is always used) and then specific parts.
The information you send us is used only to solve your support request; we will not provide any information (or drawings, projects) to persons who are not involved in solving your support request.
To the general information the following points are relevant:
- Your contact information
- The concerned product
- A detailed description of the problem
- In case the problem has already been reported, the person you had contact with
Software or PG5 project related information
In case the problem you are faced with is related to software or is e.g. a PG5 project which can not be built, please include the following information. In many cases a screenshot is very useful.
- Which software version you are using
Can usually be found under the menu "Help" --> "About"
- Is the problem you have
- project specific (the problem does not occur on all projects)
- installation specific (it works on other PCs)
- Can the problem be reproduced or is it random?
- Since when does the problem occur?
- In case of an error message or a uncommon behaviour of the interface:
Please include a screenshot of the error message (please send the screenshot by mail as attachment and not embedded in the EMail, as we are working with Lotus Notes, some mails with embedded pictures from Microsoft tools are not displayed correctly).
- In case of a PG5 project-specific support case:
Please send us a backup of your project (in PG5: Menu "Project" --> "Backup"). Please note that one single file from a project (e.g. only a Fupla file) can not be used in many cases but a PG5 project backup often contains all information needed.
In case your PG5 project exceeds 20 MBytes, you could e.g. use the file exchange area:
PCD firmware related information
In case an influence of the firmware could be the reason for the support case, please provide the following information.
- PCD diagnostic file
Can be made from the "PG5 Online Configurator" menu "Tools" --> "Create Diagnostic File"
This file will contain firmware version, hardware version, indications to the last errors of the PCD together with status information of the PCD which can be valuable for our development team.
- Can the problem be reproduced? If yes, how?
- How many times did you face the problem?
- What is the environment of the PCD; where is it installed and what tasks does it execute?
- In case the error is PG5 project specific, please include a PG5 project backup.
Communication specific problem
In case you are facing a problem related to communication with the PCD, please include the following information
- Which communication is involved?
- The topology of the project (e.g. a drawing; note that even a scanned hand-drawing is far better than no drawing)
- Since when does the problem occur (e.g. from beginning, since a modification of the project has been made etc.)
- How often does the error occur?
- What is the environment of the PCD; where is it installed and what tasks does it execute?
- PCD diagnostic file (see above)
- If possible, please include a capture of the network traffic (if it is IP traffic, please use Wireshark, see FAQ 100569)
- In case the communication problem concerns a connection between the SComm driver (e.g. PG5) and a PCD, please include a tracewin capture of the communication (see FAQ 100268)
Hardware related information
In case you are facing a hardware related problem, please let us know:
- Which hardware type is concerned
- What is the production date (if available)
- If there is a sticker with the product type and e.g. a 4-digit number (such as 1042),
please include the content of this sticker;
- If the "PO number (7-digit number on same sticker) is available, please include
this number as well.
- How many systems are concerned (out of how many received)?
- In case the error is visible and a photo exists, please include this photo.
What do I have to do to be able to send E-Mails to the bluewin.ch SMTP Server ? (FAQ #101020)
If you want to use the bluewin.ch SMTP Server for relaying purposes (send an E-Mail from the PCD to the bluewin.ch SMTP Server and the SMTP Server will send the E-Mail to the destination E-Mail account) the following has to be considered
- The use of the bluewin.ch SMTP Server is only possible if you have a bluewin.ch account (bluewin ADSL router with a bluewin.ch account)
- The SMTP Server of bluewin.ch does need a authentification
- In PG5 use the F-Box “AMail Init”
- In the F-Box “AMail Init”
- In the F-Box do set the SMTP Server port to 25 or 587
- In the text “SMTP” set the TCP/IP Address of the bluewin.ch SMTP Server to 22.214.171.124 (old TCP/IP address was 126.96.36.199, the DNS-name is smtpauth.bluewin.ch)
- In the “Name” text, write your bluewin e-mail address without "@bluewin.ch"
(exp. my_name for the e-mail account email@example.com).
The e-mail address @bluemail.ch does not work.
- In the “Pwd” text, write the password of your e-mail account
- In the “Sender” text to write a “correct” E-Mail address,
“correct” means where the domain name does exist.
- In the “To1..To5” text, write the destination E-Mail account
Use the Send Mail F-Box to send the E-Mails.
Which abonnoment is recommended for the SIM cards used for PCD applications in the GSM modem (just for Switzerland)? (FAQ #100492)
To go online over PG5, a data channel is needed. For sending SMS a usual Voice SIM card can be used as well.
The provider Swisscom offers different abonnoments. If you like to go online with PG5, you will need to choose the right abonnoment.
Probably the best solution is to use an abonnoment called: "Data Basic" this abonnoment offers a Data channel for online connections and it is possible to send SMS. Since the Voice service is never needed for PCD applications (SMS and going online), there is no need to buy another abonnoment.
If you already have a Voice abonnoment and you like to use it for test purposes in a GSM modem you can send SMS but it is not possible to go online with PG5. To use this functionality you have to add an additional Data Call number to your voice abonnoment. Please note that in this case you will have two different phone numbers on your SIM card. One for the Voice Service and another one for the Data Service.
Important: According to our tests the Prepaid Easy-Cards do not work for modem connections, going online with PG5. Since they do not support CSD (Circuit Switched Data). It is possible to send SMS with these Prepaid Easy Cards but going online with PG5 is not possible. There is one single exeption: If you have a GSM modem on both sides (PC and PCD) then it would be possible to make a Data call (going online with PG5), since they are connection with V110 protocoll. In this case there is one thing to keep in mind: You have to launch at least one call per year, otherwise the functionality will be disabled by the provider.
Local FAQ Deutschland / Français
Local FAQ Deutschland / Deutsch
Welche Informationen benötigt das Support-Team um erfolgreich Support zu geben? (FAQ #101526)
In einigen Fällen fragt Sie das Support-Team nach mehr und detailierteren Informationen die das berichtete Problem betreffen. Dieser FAQ enthält eine Auflistung aller wichtigen Punkte die voraussichtlich benötigt werden um Ihre Support-Anfrage erfolgreich zu beantworten.
Warum diese Liste?
Diese Liste wurde zusammengestellt nachdem wir erkannt haben, dass häufig zusätzliche Informationen nach Erhalt der Support- Anfrage notwendig werden.
Durch das Nachfragen wird die Lösung des Problems häufig verzögert. Deshalb wurde diese Liste generiert; wird uns ein Support- Fall mit den Informationen die in dieser Liste aufgeführt sind übergeben, können wir diesen effizienter bearbeiten.
Die Art der Informationen gliedert sich in einen allgemeinen Teil (der immer benötigt wird) und problemspezifische Teile.
Die Informationen die Sie uns zur Verfügung stellen werden nur zur Lösung Ihres Problems genutzt; keine dieser Informationen (egal ob Zeichnung oder Projekte) wird anderen Personen zugänglich gemacht, außer denen die mit der Lösung des Problems befasst sind.
- Ihre Kontaktinformationen (Name, Firma, Mobiltelefon/Festnetznummer, Email- Adresse)
- Das betroffene Produkt
- Eine genaue Beschreibung des Problems
- Falls das Problem schon einmal berichtet wurde, mit wem Sie gesprochen haben
Software Informationen oder PG5 spezifische Informationen
Falls das Problem mit dem Sie konfrontiert sind mit Software zusammen hängt, z.B. ein PG5 Projekt läßt sich nicht builden, dann geben Sie uns folgende Informationen. In vielen Fällen ist ein Screenshot sehr hilfreich.
- Welche Software Version benutzen Sie?
Die Version finden Sie im Projektmanager unter dem Menue „Help“ --> „About“
- Ist das Problem das Sie haben
- Projekt bezogen (das Problem tritt nicht in allen Projekten auf)
- Installations bezogen (auf anderen PC’s funktioniert es)
- Kann das Projekt reproduziert werden oder ist es zufällig?
- Seit wann tritt das Problem auf?
- Im Fall einer Fehlermeldung oder eines ungewöhnlichen Verhaltens der Schnittstelle:
Erzeugen Sie bitte einen Screenshot (im *.jpg Format) der Fehlermeldung (bitte senden Sie den Screenshot als Anhang der Email und nicht eingebettet, da wir mit Lotus Notes arbeiten werden Mails mit eingebetteten Bildern, die aus Microsoft- Produkten versand werden, nicht korrekt dargestellt).
- Handel es sich um eine PG5 Projekt spezifischen Support- Fall:
Senden Sie uns bitte ein Backup Ihres Projektes (im PG5 Projektmanager unter
dem Menu „Project“ --> „Backup“). Bitte beachten Sie das eine einzelne Datei (z.B. nur die Datei mit der Endung .fup) in vielen Fällen nich verwendet werden kann, aber das PG5 Projektbackup enthält meistens alle benötigten Informationen.
Ist das Projektbackup größer als 5 MByte benutzen Sie bitte unseren FTP- Server zum Datenaustausch:
Informationen finden Sie unter www.sbc-support.com/de/services/austauschbereich/
PCD Firmware bezogene Informationen
In Fällen eines Einflusses der Firmware auf das Problem stellen Sie bitte folgende Informationen bereit:
- PCD Diagnostic File
Dieser kann mit dem „PG5 Online Configurator“ im Menue „Tools“ --> „Create Diagnostic File“ erzeugt werden.
Diese Datei enthält die Firmware- Version, Hardware- Version, zeigt die letzten Fehler aus der History zusammen mit Statusinformationen der PCD, welche nützlich für das Entwicklerteam sein können.
- Kann das Problem reproduziert werden? Wen ja, wie?
- Wie oft haben Sie das Problem beobachtet?
- In was für einer Umgebung befindet sich die PCD; wo ist sie installiert, welche Aufgaben führt sie aus?
- Sollte der Fehler PG5 Projekt spezifisch sein, geben Sie uns bitte ein Projektbackup. (Siehe oben)
Wenn Sie Probleme die mit der Kommunikation der PCD verbunden sind beobachten, geben Sie uns bitte nachfolgende Informationen:
- Welche Kommunikation ist betroffen?
- Die Topologie des Projektes (z.B. eine Zeichnung; bitte bedenken Sie das eine gescannte Handzeichnung immer besser ist als gar keine Zeichnung)
- Seit wann besteht das Problem (z.B. seit Anfang an, seit eine Änderung des Projektes durchgeführt wurde, etc.)
- Wie oft tritt das Problem auf?
- In was für einer Umgebung befindet sich die PCD; wo ist sie installiert, welche Aufgaben führt sie aus?
- PCD Diagnostic File (siehe oben)
- Wenn möglich geben Sie uns bitte einen Mitschnitt des Netzwerks (wenn es IP- Kommunikation ist, benutzen Sie bitte Wireshark, Informationen dazu unter FAQ #100569)
- Falls die Kommunikation mit dem S-Bus Treiber SComm in Zusammenhang steht (z.B. PG5 zu PCD), fügen Sie bitte eine Tracewin Aufzeichnung bei (siehe FAQ #100268)
Hardware bezogene Informationen
Wenn das beobachtete Problem mit der Hardware zusammenhängt, lassen Sie uns bitte folgendes wissen:
- Welche Hardware ist betroffen?
- Das Produktionsdatum (wenn verfügbar)
- Wenn ein Aufkleber mit der Typenbezeichnung vorhanden ist und z.B. eine 4-stellige
Nummer (wie z.B. 1042) darauf ist, fügen Sie diese Informationen bitte mit bei.
- Falls die "PA Nummer (7-stellige Nummer auf den selben Aufkleber) verfügbar ist, bitte
diese Nummer auch beifügen.
- Wie viele Systeme sind betroffen (von wievielen die Sie geliefert bekommen haben)?
- Im Falle eines sichtbaren Fehlers den Sie auf einem Bild dokumentiert haben, bitte schicken Sie uns das Bild.
The special FBox library PCD7_D7 is now available for PG5 2.0. (FAQ #101356)
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
Support für Schweizer Kunden (FAQ #100142)
Per Telefon: 026 672 71 11, Support verlangen
per e-Mail: firstname.lastname@example.org
Why is there a Malware Warning for the Support Site displayed? (solved) (FAQ #101763)
At the moment allways when you want to enter the Support Site with Chrome or Firefox, a Malware Warning is displayed from google. This is because there was a file on the server which refered to a malware server.
At the moment allways when you want to enter the support site a Malware warning is displayed from google, this is because there was a file on the server which refered to a malware server. This is no longer the case and we informed google to scan the server again.
Concerned Products: This warning only occurs when using Firefox or Chrome.
As there is no danger or malware on the support site you can either ignore this warning, use a not concerned browser or access the support site via: www.sbc-support.com
Problem has been solved! No warning should be displayed anymore when accessing the support site dirtectly, otherwise the database is not up to date.
Can I automatically be informed if the support site is updated? (FAQ #101695)
In case you are interested in updates of the support site (www.sbc-support.ch or alternatively www.sbc-support.com) you can subscribe to the RSS feed which is available for this site.
What for can the RSS feed be used?
The RSS feed from the support site can be used in order to have an overview over the latest updates without having the need to manually connect to the site to read the "What's new" section. The content of the feed can be read using various tools such as the built-in RSS feed reader from the Internet Exploer (IE8 or later), Firefox or specific tools such as gReader for smartphones or the free software "RSS Bandit".
How to subscibe?
The subscription process is depending on the RSS reader. Below some hints for the most commonly used readers:
- Firefox (version 3.6 and later)
Type in the URL of the support site (e.g. www.sbc-support.com) and click on the small icon for RSS feeds:
In the appearing window, click the button "Subscribe now"
- Firefox (version 3.6 and later)
Why do the links from the FAQ Newsletter not work correctly? (FAQ #101594)
At the moment the FAQ Newsletter contains wrong links when opening a mail with Lotus Notes. We are currently investigating this issue and expect it working correctly for the next newsletter.
In order to use a link, the "D3" in the link must be deleted:
How to dump the memory of a PCD (with Saia PCD® COSinus firmware)? (FAQ #100833)
The information provided in the history or the "Diagnostic file" of the PCD does not always give enough information for the firmware developpers to find the reason for e.g. a crash of a PCD. If more information is required in order to trace back a crash, a dump of the whole memory (SRAM, DRAM and FLASH) of a PCD can be done. This FAQ does apply to PCD1.M2, PCD2.M480, PCD2.M5xxx, PCD3 (including PCD3.Mxx60) and PCD7.D4xxxT5F (Programable MB-panels).
For dumping the memory of one of the following systems a dedicated small executable is available as standalone tool or since PG5 2.1.210 there is a DumpTool.exe in the PG5 directory.
- PCD3.Mxx60 (fast CPU)
- PCD7.D4xxxT5F (programmable MB-panels)
Usage of the old stand alone tool SaiaDump.exe:
This tool is called by a batch file which will call an executable (SaiaDump.exe) with hardware specific parameters. The executable will establish an USB connection to the PCD and will read out the memory content. This content will be stored in 4 files and all these files will automatically be stored in a *.zip archive.
Usage of the new stand alone tool DumpTool.exe (included in the PG5 directory since PG5 2.1.210):
This tool does open a small window which allow to define the device type and the destination folder where the dump files will be stored. The device field does show the PCD which is connected over USB. The program will establish an USB connection to the PCD and will read out the memory content. This content will be stored in 4 files and all these files will automatically be stored in a *.zip archive.
In order to obtain all necessary information it is important that the dump is made while the CPU's memory still contains the last information. Since this information is lost (overwritten) when the PCD re-boots, it must be achieved that the PCD does not reboot in case of a crash (e.g. Bus Error or Kernel Error). Therefore a specific SYSWR has been implemented. This command is to be executed on the PCD e.g. in XOB 16 before a crash occurs (on every boot, because it is reset on each power off).
Software installation (only for old stand alone tool SaiaDump.exe)
- Download the archive "SaiaDump_V1_3_006.zip" from this FAQ
- Unpack the *.zip archive on your PC or Laptop
- In the extracted folder "SaiaDump" you'll find several batch files (e.g. RUN_DUMP_PCD1M2xx0.bat). By double-clicking the file fitting your hardware, a dump is started (make sure that PCD is connected with a USB cable and no PG5 is running)
Use the following versions in dependance of your hardware:
- RUN_DUMP_PCD1M2xx0.bat for PCD1.M2xx0
- RUN_DUMP_PCD3Mxxx0.bat for PCD2.M5xx0 and PCD3 systems
- RUN_DUMP_PCD3Mxx6x.bat for PCD3.Mxx60 (fast CPU) systems
After a successful dump a new *.zip archive with the name "PCDDump_date" will be stored in the same directory. Please send this archive (it should contain four files with the extension *.blk or *.bin and a log file) to the support.
Preparing the PCD
In order to cause the PCD not to reboot in case of a crash, add the follwoing lines to the code of your CPU (and remove the watchdogs, if present). Altermantively, you can also add and link the file "DontRestartAfterCrash.src" which is contained in the folder "PCD_Preparation" off the "SaiaDump_exe.zip" to the concerned CPU in your PG5 project.
$INIT ; Add the following lines to the XOB 16
SYSWR K 9999 ; Instruction to cause the PCD not to
K 1 ; reboot after a crash
This instruction has been implemented first in PCD3 firmware version 03A. Therefore please also make sure that FW version 03A or higher is installed on the system.
The SBC Dump tool can only dump the memory of a PCD that has boot loader version 035 (created in April 2006) or higher installed. In case your PCD has a too old boot loader or if you are in doubt of the boot loader version of your PCD, please refer to FAQ 100680 in order to learn more about how to find out the boot loader version and how to update the boot loader version.
Dumping the PCD memory
After the next crash, the PCD will not re-boot anymore and will blink with all tree LEDs simultaneously instead. Please note that the SYSWR K 9999 (see above) must have been introduced before the crash and the LEDs must blink in this state! In this (and only in this) situation it is possible dumping the memory of the PCD:
Possibility 1 with the use of the old stand alone tool SaiaDump.exe:
Launch the SaiaDump.exe for retrieving valuable debug information (it is also possible dumping the PCD if the PCD is in boot loader state or run for test purposes, but no valuable debug information can be retrieved from these files).
For launching the SBC Dump is should be enough to double-click the file RUN_DUMP_PCDx.bat.
Possibility 2 with the use of the new stand alone tool DumpTool.exe:
Launch the DumpTool.exe from the PG5 installation directory.
The PCD information is shown in the ‘Device’ field, as soon as the tool does detect a PCD which is connected over USB to the PC.
In the ‘Template’ filed it’s possible to define the device type; Type Automatic should be fine.
Do define in the ‘Target folder’ field the folder where the zip file should be stored.
Click on the ‘Start Dump’ button to perform the memory dump.
Additional information for PCD3.Mxxx7
The same tool can also be used for dumping the memory of a PCD3.Mxxx7. But note that the usage of the SYSWR listed above is not to be used.
- August 2015
- Since PG5 2.1.210 there is a dumptool.exe available in the PG5 installation directory
which can be used instead of the SaiaDump.exe
- March 2013 (version 1.3.006)
- Support also the PCD7.D4xxxT5F (programmable MB-panels)
- July 2011 (version 1.3.005)
- created batch files for easy launch or the SBC Dump executable
- added log file creation during dump process
- November 2010 (version 1.2)
- supports new hardware: PCD1.M2 and PCD3.Mxx60 (fast CPU)
- supports the new USB driver (for 64Bit OS)
- removed the firmware files from the package in order to make it smaller
- June 2010 (version 1.1)
- increased SRAM memory Dump (2 MByte) for recent PCD systems (PCD3, PCD2.M5).
- update of firmware delivered in the package to 1.10.51.
- Mai 2009
Version 1.0 of the SBC Dump: This version does also dump the internal SRAM of the PCD.
PCMCIA card with 2 serial COM Ports (RS-232) suitable for S-Bus (FAQ #100764)
Serial S-Bus is still very often in use for it's low costs combined with good communication performance. Unfortunately, nowadays it's quite difficult to buy a notebook PC which still has at least one serial COM port!
USB to RS-232 adapters may be a solution, but there is no guaranty that a specific adapter will work with SBC S-Bus properly.
The EXSYS PCMCIA card EX-1352 with 2 serial RS-232 ports has been sucessfully tested at our technical support department. We can recommend this card for use with SBC S-Bus and Saia PG5®. Also available from EXSYS, but not tested, are cards with 1 or 4 RS-232 ports plus a card with 2 surge protected RS-232 ports.
Detailed information about this EXSYS cards can be found at the EXSYS homepage:
EXSYS Vertriebs GmbH
Tel.:+49 (0)6171 975656
Fax:+49 (0)6171 975697
New version of the lable creator (FAQ #100637)
There is a new version of the lable creator available. We recommend to use the newest version, since in the old one were a few problems and some lables where not correctly created.
The link attached to this FAQ leads to the latest version of the label creator. It has to be V01.01.05 or newer.
Can a PCD be started at negative temperatures? (FAQ #100483)
In the manual a minimal operation temperature for PCDs of 0 degree Celsius is specified. Given the user takes into account of a lowered MTBF (Mean Time Between Failure), it is also possible starting a PCD at lower temperatures.
Does a PCD work at -25°C?
Internal tests permit a practical guarantee of operation to be given. As mentioned in FAQ 100480, internal type acceptance tests in research have demonstrated perfect operation throughout the temperature range of -25..+100°C.
Why is a minimal temperature of 0°C specified?
The reason for this specification the fact that the manufacturers of the single components usually do specify this temperature for their products. The component specific time- and electrical parameters are guaranteed to be valid for the temperature range in their specification.
We have learned that these components do fulfill their function also in an extended temperature range if the electronical design concept is appropriate.
Our prototype and type acceptance tests of our systems at less than -25°C do show the correct functionality of our products. But we cannot give an definitive guarantee because the temperature range of the components is already specified by the according manufaturers.
A PCD that is continuausly started at negative temperature can have a reduced length of operation between two breakdowns.
The user must also consider that every kind of dewing or ice building on the controller must be avoided scrupulously.
Does dewing harm PCD controllers? (FAQ #100482)
In case the PCD is colder than the environment and the relative air humidity is high enough, it is possible that wather condensates on the PCD. This situation as well as the building of ice on the PCD is to be avoided scrupulously.
As dewing will cause corrosion and attacks the components of the controller, it must be considered that no condensation must take place also if the controller is not running (e.g. on stock before mounting them or while the machine is not running but stored).
How to avoid dewing?
If the PCD is used in a place where dewing cannot be avoided, the dewing must be prevented by e.g. permanently heating the device or placing the PCD into a airtight cabinet (where no humid air causing dewing can enter).
Extended temperature range for PCD operation (FAQ #100480)
The specified operation temperature range of Saia PCD® systems is 0..40 degree Celsius or 0..55 degree Celsius. Given the user takes account of the consequences a PCD can be used in extended temperature ranges.
Specified temperature range
The specified operation temperature range of Saia PCD® systems stated in the user manuals is 0°..40°C or 0°..55°C depending on the position in which the device is mounted.
Extended temperature range
Saia-Burgess Controls AG gives its agreement to operation across the extended range of -20°..+75°C on condition that the user takes account of the influences and responsatilities described below.
In fact, internal tests permit a practical guarantee of operation to be given:
During manufacture a systematic Run-In is used (with function monitoring) at 85°C for 48 hours.
Type acceptance tests in research on extreme termperatures have demonstrated perfect operation throughout the range -25°..100°C.
Influences and user responsabilities:
It is known that the failure rate for an electronic device depends on the service termperature. A rule of thumb states that a 10°C rise in the service temperature accelerates failure mechanisms by a factor of 2.
If the temperature is raised temporarily (peaks of 65°C) for a few hours, days or even weeks in summer, the influence on breakdown rate remains negligible. However, if these are permanent conditions the user must accept that more frequent failures may be possible.
It is also advisable to follow the recommendations below:
maintain the lowest possible ambient temperature,
mount the device in the best position to promote natural ventilation.
avoid placing it in a location where heat accumulates or exposing it to heat sources (sun) directly on the device or on the cabinet.
For the negative temperature range, the case is different: the phenomena of condensation and ice formation must be scrupulously avoided. The influence on the length of service life then becomes negligible.
More information about PCD system problems/crashes (FAQ #100458)
In order to get support in case of system crashes, it is absolutely necessary providing very specivic information to the development department.
In the path „Program Files Saia Burgess/ PG5 1_3/ Batches“
can be started the CPU according a batch files, which select and into the
file chaine.txt write the memory of the appropriate CPU.
Are there *.dxf files or other pre-defined CAD drawings of PCD systems available? (FAQ #100444)
There are only *.dxf files and EPLAN Macros available for the PCD3 products. There have been requests for such files for other PCD systems, but due to very different requests regarding information contained by these files we couldn't define a general standard for the creation of these files.
Why aren't*.dxf files for all PCDs availabe?
While trying to define a standard requirement what these files should contain, it turned out that there are very different needs. Some customers would like to have some kind of a view of the system (for placing into a drawing of the control cabinet), other customes mainly need a detailed description of the terminals present in their drawings. Again other customers need such files for placing into the machanical drawings, providing mainly dimensions.
There are also completely different target softwares around, some designed for the creation of electric diagrams, mechanical drawings, 3-d modelling or just for the creation of a veiw of the control cabinet.
Will there be *.dxf files of PCD systems?
In general we are interested to offer this service to our customers. But therefore we need more information about the requests in order to define which layout we shall use.
In case you have a specific idea how such a library should look like and for which software it should fit best, please let us know! Send us your suggestion to email@example.com (Subject: DXF suggestion).
S-Bus communication with Exor terminal doesn't work! (FAQ #100307)
In the Exor programming tool the S-Bus driver parameter displays what looks like Data mode parameters (Parity:no, Data bit: 8, Stop bit: 1) but in reality Parity mode is needed!
To assignate the serial port of the PCD use Sasi slave FBox with the same default Parameter that the Exor configuration S-Bus driver are:
The S-Bus station number has to be identical in PCD HW setting as in the Exor S-Bus driver configurator.
Be also aware that the PCD wiring designation might be different that the one from foreign component:SBCForeign componentRXD-RX/RX/D+RXTXD-TX/TX/D+TX
What EPROM burner is recommended to create firmware chips for PCD's? (FAQ #100256)
We have made good experiences with the GALEP 4, for PCD1 FW together with the adaptor 210841. The local dealer for Switzerland is www.redacom.ch.
Order numbers for empty firmware chips:
PCD1.M1x0: 1x ASN 4 502 7178 (OTP27C4002), one time programmable
PCD1.M137: 1x ASN 4 502 7178 (OTP27C4002), one time programmable
PCD2.M110/M120: 2x ASN 4 502 7126 0 (27C1001-10, EPROM)
PCD2.M127: can be downloaded, refer to the product page on www.sbc-support.ch
PCD2.M150: 2x ASN 4 502 7341 0 (49F040 ,Flash-EPROM)
PCD2.M157: can be downloaded, refer to the product page on www.sbc-support.ch
PCD2.M170: chip soldered on the main board, the FW can be downloaded with PG5 *
PCD2.M177: can be downloaded, refer to the product page on www.sbc-support.ch
PCD2.M480: chip soldered on the main board, the FW can be downloaded with PG5 *
PCD2.M487: can be downloaded, refer to the product page on www.sbc-support.ch
PCD3.Mxxxx: chip soldered on the main board, the FW can be downloaded with PG5 *
* Procedure to downlaod a firmware:
1) get the appropriate file from product page on the supportsite www.sbc-support.ch
2) open PG5 and go to the online-configurator; go offline
3) open the menu tools, download firmware
4) browse for the firmware file and start the download
5) load the HW configuration and the user program