If on the Web-Editor8 a container variable is copied from the Web-Editor8 help file with copy paste in to the Web-editor8 painter, then it’s possible that not only the name of the variable is copied but also an invisible 'CR''LF' character.

In such a case, the container variable name does not correspond to the required name and the special action of this container variable is not performed.

Example with the container variable 'MB_InactivityCounter'
Copy form the Web-Editor8 file


Paste in the Web-Editor8 painter.


How to find out such variables?
Open the wvar file and check the ‘internal variables’ Tab.
The line of a variable which does have a at the end of the name is shown as a double size line.
Means that on the first line the name of the variable is shown and on the second line empty line is shown.



How to solve the problem?
On the wvar file do click with the right mouse key to the concerned variable and select rename.


On the next window put the cursor at the end of the variable name and press the Backspace button of your keyboard (the invisible will be deleted) and on the next step select all places where the variable should be replaced.


After the update the new and the old variable are shown in the wvar file and after clicking to the update button only the variable without is shown on the screen.

Symptom
If you build and download a project with PG5 2.1.100.100 or PG 5 2.1.100 to a PCS1, then there will be a strange behaviour of the program execution like:
- Overide FBoxes don’t seem to work correctly

- It’s possible that you have Index Register Overflow message in the PCD history

Reason
There is an bug in PG5 2.1.100.100 which lead to the situation that the PCD code can’t be executed correctly.

Solution
- Use PG5 2.1.200 or higher.
- If PG5 2.1.100.100 is used:
  Download and unzip the attached file and replace the two existing files
  (SaiaConf52.dll, Sasm52.dll) in the Installation folder of PG5 2.1.100.100 with these files. 

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

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

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

Remarks

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

The PCD7.D23x displays are equipped with a buzzer but the internal PCD7.D230 of the PCS1 has no buzzer!

With an activated software watchdog the processor monitors itself and restarts the PCD in the event of a malfunction or a loop.

Description (extract from the hardware manual)
The hardware watchdog provides maximum security. However, for non-critical applications, a software watchdog may be suffcient, whereby the processor monitors itself and the CPU is restarted in the event of a malfunction or a loop.
The core of the software watchdog is the instruction SYSWR K 1000. When this is first issued, the software watchdog function is activated. This instruction must then be issued at least every 200 ms, or the watchdog will trigger and restart the controller.

Usage

• Placing a "Watchdog"-FBox in a FUPLA-file is the easiest solution:
  
• Instead of using the FBox it is possible calling the Software Watchdog in IL (using the instruction SYSWR K 1000)
  

On the 8 pin RJ45 connector (on the left side of the PCS1) the pins 3, 4, 5 and 6 are used.

Signal description: 
Pin 3: TX+
Pin 4: RX+
Pin 5: RX-
Pin 6: TX- 

Numbering of pins of the connector cable (male connector):

In case a "non Saia PCD® COSinus" PCD or PCS1 system is connected with "Secure S-Bus Data mode" (e.g. over a serial cable or over modem) from time to time a telegram is not answered correctly.

Symptom
A PCD or a PCS connected with another system (e.g. PC or another PCD system) using the "Secure S-Bus Data mode" does not answer a telegram from time to time. This can e.g. be seen by a red LED on transmit or receive FBoxes (or in case a PC is used, by interpreting the tracewin files).
This phenomenon can be observed on PCD1.M1x5, PCD2.M150, PCD2/4.M170 and PCS1 systems (with firmware which are supporting the "Secure S-Bus Data mode"). Saia PCD® COSinus based systems (PCD2.M480, PCD2.M5xx0 and PCD3) are not concerned.

Reason
The reason for this behavior is that the PCD/PCS does not correcly answer telegrams where the sequence number in the secure S-Bus Data Mode header is 0xC5h. This is the case in every 255th telegram.
(The character "C5" should be replaced by "C5 01" but this is not done).

Solution
Please refer to the table below for firmware version which do correctly handle the "C5" and therefore the symptom described above is avoided.

Note that connecting an external terminal is possible even if the PCS1 has already an internal terminal

Possibilities
It is possible to use the ports 0, 1 , 2 and 3.
The internal terminal is using the port 2. So in case if there is an internal terminal the port 2 is not available.

Port 2
For the connection to port 2 we recommend using the cable PCD7.K423 (with Handshake). The wiring is:

When trying to write a text (with address higher than 4000) using the S-Web Server, the PCD system stopps working and in the PCD history a "68k add Error" is indicated.

Symptom
When trying to write a text (with address higher than 4000) using the S-Web Server, the PCD system stopps working and in the PCD history a "68k add Error" is indicated.
The following PCD systems are concerned:

• PCD1.M1x5 with firmware version higher than 0B0
• PCD2.M150 with firmware version higher than 0E0
• PCD2/4.M170 with firmware version higher than 030
• PCS1.Cxx0 with firmware version higher than 0C0 

Reason
This behaviour is not intended. Due to a problem in the firmware the write access fails.

Solution
This problem is solved in firmware version 0E6 (the version indication 0E6 is the same for all systems) which can be downloaded from the support site (www.sbc-support.ch).

In some (very rare cases) the clock of a PCS can not been written, and the shown time always is the 1.01.1990. After switching the PCS off and on again, the problem disappears.

Symtom
The RTC (real time clock) of the PCS does no longer work and shows the date 1.01.1990. Attempts to write the clock using e.g. the PG5 Online Configurator fail with a NAK response. However, after restarting or switching the power off and on again, the problem disappears. This phenomenon has only been observed with firmware version 0C0, 0C1 and 0E3.

Reason
This phenomenon has been observed on very few sites, and it is very likely that it occurred after a very short power outage, which lead to the fact that the firmware of the PCS could no longer access the internal RTC of the PCS.

Solution
This behavior does no longer occur with firmware version 0E6 (and is does not occur with firmware versions older than 0C0 or newer than #E4, neither).
In case you are concerned by this problem, please update the firmware of your PCS system to version 0F0 or later which can be downlaoded from the support site (www.sbc-support.ch).

Depending on the resistive temperature detector type and the analogue input module, various combinations are possible which are not all listed in the FBox or the manuals.

In general an analogue input module designed for measuring the resistance of an NI1000 or PT1000 sensor can also measure the resistance of e.g. an NI1000 Landis & Staefa (L&S) or an NTC10 sensors (and many more). However, the FBox does not necessarily feature the option for configuring the relevant sensor type. In this case, the digital value of the input module can be read in the mode "1:1" and based on this value, the temperature can be calculated (or more precisely: interpolated) by using the FBox "Conversion 20 point" from the FBox Family "HVC General".
The according values which are to be filled in the "Conversion 20 point" FBox can be obtained from Saia-Burgess Controls AG.

Which combinations are possible?
In general it is important that the resistance range for which the analogue input module is designed for does fit the resistance range of the sensor for the temperature range to be measured. It is even possible to apply e.g. a parallel resistance in order to shift the resistance measured to a range which can be measured by the analogue input module. Below you can find some often used combinations of analogue input modules and special tempearture sensors:

• NTC10k sensor with PCD2/3.W340 together
• NTC10kPre sensor with PCD2.W220Z02 or PCD3.W220Z03
• NTC20k Honeywell with PCD2.W220Z02 or PCD3.W220Z03 
• Ni1000 L&S with large temperature range on PCD2/3.W220 or PCD2/3.W340
• Ni1000 Tk 5000 with PCD2/3.W360
• Ni200 DIN 43760 with PCD2/3.W350
• Potentiometer 1kOhm on PCD2/3.W220
• Potentiometer 2kOhm on PCD2/3.W340
• Staefa T1 with PCD2/3.W220
• QAC 31 with PCD2/3.W220
• KTY10-6 on PCD2/3.W220 or PCD2/3.W340 (temperature range -45..50°C)

Where from do I get the values for the conversion?
Please send a mail which contains the specific type of your sensor (if possible, provide the resistance table of the sensor) and the definition of the temperature range you need to measure to support@saia-pcd.com.

This is a bug in PG5 1.4 200 assembler.

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

Connector block X3, Pin 4 can used as power supply 5 Volt.

Note that the maximum load is 150mA.

Once entered in the strucure, the root menu appears again after a few seconds. So it isn't possible to stay in the structure/object because it comes back automaticaly in the root menu after 5-10 seconds!

This problem is present with PCS1 and Displays PCD7.D23x older Hardware version and newer Version of the HMI editor (1.4 100 to 200) using the default parameters RS 232 / 9600 Bauts / RTS/CTS.

Solution:

Used the latest HMI Library 1.4 213 or newer where the correction is implemented!

Attention:
If the PCS1 has an old FW version it might also needed to update it to the actual FW version (0C1 or newer). If the PCS1 is older than january 2004 see FAQ 100384!

With firmware 0C0 a short power down can lead to the loss of the production information. In detail this is the product identification, the serial number as well as the production date.

Symptom
The production information is lost after a short power down if the firmware version 0C0 is installed on the PCS system. Once this information is lost only question marks are shown in the PG5 "Online Configurator" instead of the values expected.

Reason
This situation is caused by a corruption of the internal EEPROM. Such a corruption can be caused by the firmware 0C0 if the PCS is switched off and very shortly after this power down switched on again.

Solution
The content of the EEPROM can only be restored by the repair service of Saia-Burgess Controls AG. Please contact your local Sales Office in order to organize a repair of the concerned system.

Important recommandation
In case you do have PCS systems equipped with firmware version 0C0 (having been distributed between May and June 2007), it is strongly recommended updating the system with firmware version 0C1 (or later) in order to avoid a loss of the production information. The lates version of the firmware can be found in the PCS1 section of the support site www.sbc-support.ch.

Even the Fbox Clock Super Cap is used in the user programme when the PCS1 is powerup it has lost the initial time!

Some PCS1 produce before 2007 might have a hardware problem concerning the hardware clock managment.

Turn around:

Instead to put to 1 the Enable input of the Clock/Scap Fbox, put the Enable to 0 in the user programme and download it to the PCS1.

Solution:

The PCS1 has to be repared to solve that problem correctly. If the turn around didn't help it has to be send anyway to repair!

The PCD1.M110, PCS1 and PCD3 are equipped with a supercap. This supercap needs a certain time until it is fully charged.

PCD1.M110/120
It takes about 30min. until the supercap is fully charged (5T). To keep the RAM content at least 2V are needed. The supercap contains 2V after about 5min. After this time the PCD1 will keep the data in RAM for a short time. The  buffer time (30 days for PCD1.M110 and 7 days for PCD1.M120) can only be guaranteed if the supercap is fully charged, that means after at least 30 minutes runtime.

PCS1
It takes about 45min. until the supercap is fully charged (5T). To keep the RAM content at least 2V are needed. The supercap contains 2V after about 6min. After this time the PCS1 will keep the data in RAM for a short time. The full buffer time (5..15 days) can only be guaranteed if the supercap is fully charged, that means after at least 45 minutes runtime.

PCD3
It takes about 6min. until the supercap is fully charged (5T). To keep the RAM content at least 2V are needed. The supercap contains 2V after about 1.5min. After this time the PCD3 will keep the data in RAM for a short time. The full buffer time can only be guaranteed if the supercap is fully charged, that means after at least 6 minutes runtime.

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

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

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

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

Restrictions

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

Since November 05 all PCS1 with analog and ISDN modem are deliverd with T814 and T851 modem. The PCS1 needs to have modification 4 in order to use those new modems.

    In case of older PCS1 (< modif. 4) which need to be equipped now with a modem,
or which are already equipped with an older modem (T813 or T850) and need to be repaired,  
they must  be send to Murten for modification.

Only PCS1 modification 4 can receive new modem T814 / T851!

PCS1 with hardware version E (or newer) with firmware 0A0 (or newer) have 50 non-volatile E² registers. Older PCS1 systems have only 5 E² registers.

PCS1 systems older than hardware version E are equiped with 240 KB flash memory, 128 KB RAM (extension memory) and only 5 non-volatile EEPROM registers.

Starting with hardware version E and firmware 0A0 (or newer), PCS1 systems are equiped with 1008 KB flash and 896 KB RAM. The amount of EEPROM registers has also been increased to 50.

HINT: Non-volatile register can be used to store important data that is not to be lost even in the case of an empty buffer capacitor. Reading and writing these EEPROM registers from the user program can either be done with IL commands (see SYSRD, SYSWR) or with FUPLA FBoxes (see Special Functions).

WARNING: A maximum of 100,000 user writes are permitted to the EEPROM, so do not execute this instruction frequently in your user program. The SYSWR instruction takes 20 ms to execute, so it must not be used in XOB 0.

The modem doesn't send any SMS and Modem 14 Fbox indicates: NO Modem

In order to be on line on a PCS1 with a modem, it is necessary to assigne another port (for example Port 1 + RS 232) as S-Bus PGU port.

With the following parameters in modem 14 FBox:

Handshake: PGU switched
Default Standby Mode: OFF

It might happens that the SASI instruction on port 0 isn't executed! So the modem 14 FBox give the modem status NO Modem.

It is necessary to update the Modem Librairy to version 2.4 124 or use PG5 1.4 !

The PCS1.C6xxx has less inputs than the PCS1.C8xxx

§ix100249§

Version 0B0 for PCS1 is not to be used, as at each shutdown an area of registers are overwritten by the firmware.

The latest firmware versions for PCS1 require a boot version of 090 or more recent to be downloaded. PCS1 with hardware version E (original FW version 0A1, produced after April 2004) are already equiped with an appropriate boot version, earlier PCS1 can be updated using the attached tool.

How to update the boot and firmware:

1. connect to the PCS1 using a PCD8.K111 programming cable
2. run the attached .exe file using PG5 1.3. This tool has been introduced to make the update more safe, as the right files with the right options are downloaded
   If you have PG5 1.4 insteed jump to point 8!
3. go to the file, settings menu and check that the connection is in PGU mode
4. press the start button (the boot and the firmware are updated, wait for the download to be finished)
5. if the download fails at the end, it could be that the unit is affected by a problem encountered with units produced between week 48 in 2003 and week 12 in 2004, where a firmware update cannot be done by the user and the units have to be returned to the factory for a firmware update. If the production date of the unit is not in the mentioned range, try to run the update a second time
6. quit the tool with the exit button
7. as the tool downloads the firmware version 0B0, you may wish to download a more recent version, use the online-configurator of PG5 to do this in the usual manner
   
8. Only if the exe file can't be used!
   Use the attached description FW_Boot_dwld.doc with the Boot and FW in attached zipp file. Note: if the download failed refer to point 5 above!

If you try to connect to the the WEB Server of a PCD2.M170, PCD2.M150 (pilot FW) or a PCS1 and no WEB Server project has been downloaded, the following error is displayed: "Error 4 -Invalid page indentifier in the PCD answer".

On the "older" system it is necessary to download a Web Server project (even if it is empty) into the PCD in order to be able to access to the default SBC WEB Pages!

On the Saia PCD® COSinus systems (PCD3, PCD2.M5 and PCD2.M480) this problem doesn't occur!

The Poll SMS Fbox shows the mobil phone number but display No message. The message from the mobil phone isn't received or can't be executed properly. Some time it is executed once it has been send a second time but it takes a lot of time....

This problem is caused when too many message are contained on the SIM card used in the  GSM Modem. The Poll SMS Fbox get confused when the SIM card contains  too many texts. The last received message is deleted once it has been executed but the messages already present on the SIM card can not be deleted!

Solution: Put back the SIM card on a mobil phone and delete all messages!

Please note that due to the evolution of our mobile phone, it is not possible to delete sms  with a smart phone. You will have to use an older phone. By older phone is supposed to be a phone that still store sms on the sim card.

Example Nokia 6210

In the case you do not have an old phone at your disposal, it is still possible to delete them by using commands on a serial line connected to the modem.

You will need the following: 

1 PC with a RS-232 line

1 serial cable 1:1

1 terminal software. If you do not have one, we suggest you to use the puTTY

the.earth.li/~sgtatham/putty/latest/x86/putty-0.66-installer.exe

The command

AT+CMGL="ALL"

shows the messages on the SIM.for example:

+CMGL: 1,"REC UNREAD","+31628870634",,"11/01/09,10:26:26+04"

This is text message 1

+CMGL: 2,"REC UNREAD","+31628870634",,"11/01/09,10:26:49+04"

This is text message 2

Then, you will have to execute the following command in order to delete messages

AT+CMGD=1

OK

AT+CMGD=2
OK

************************

Note: There is a GSM modem programming example on our web site for PCD3.M with sending SMS and DTMF fonction using Poll SMS Fbox. (see under Getting Started)!

https://www.sbc-support.com/en/services/archive/getting-started/programm-examples/pg5-20/communication/

The internal display of the PCS1.C8xx is conneted on port (channel) 2. This channel is to be selected in the HMI Editor's settings tab.

SMS can't be sent, the Call SMS Fbox gives an error: End No OK and also Last end Status = Error Code, Last error Code = 96.

This error comes when the server number has no land prefix. For Switzerland it has to be +41 79 4999 000 and not only 079 4999 000!

Originally it wasn't foreseen to connect an external modem to the port 0 of the PCS1. However, in special cases it might be useful having the possibility of sending SMS messages with an external modem.

Since the port 0 of the PCS is used as PGU port and as internal modem port, some special settings are to be made in order to use the D-Sub connector for dealing with a modem.

• Switching the port 0 statically to the D-Sub connector (see FAQ 100128)

• In the Modem 14 FBox, the parameter for the handshaking is to be set to "PGU Reduced"

• In the Modem 14 FBox the standby mode is to be set to "Off" (because no online connection is possible, see below)

• The DSR signal of the modem must not be connected to the D-Sub connector

• Required FW is 0A1 or higher

Important note
Due to the fact that the DSR signal (pin 6 of the D-Sub connector) is used as indicator for a PGU connection, this signal can't be used for the communication between the PCS and the external modem. This implies that no online connection may be established with the external modem (an online connection requires full RS232 handshaking, including DSR and DCD (not present on the D-Sub). If an online connection is required, an internal modem is to be used!

The PCS1 with GSM option and the Q.G736-AS2 are delivered without antenna for the GSM terminal. The antenna is not delivered because the selection of the antenna type it is very much depending on the application/site where it is used.

Whom to consult?
We recommend consulting a specialist for antennas in order to choose the best antanna for your application.
Since most antenna providers do not have branches in the same countries as Saia-Burgess Controls AG, it is not possible to refer to the same antenna distributor worldwide.
Attached below there is a link for swiss customers. If you can't find an appropriate distributor for your country, please contact your local Saia-Burgess Controls AG representative.

What about the antenna PCD7.K830?
You can also find an antenna for the GSM modem in the SBC price list. This is a "table-antenna" with a magnetic foot ideal for tests in the office bot not necessarily suitable for the use in an application.

Technical data of this antenna

Symptom
An application running on a PCS with hardware version older than D is running fine but in some cases the PCS1 goes to Halt and indicates e.g. a "68k Error" or "Invalid OPC" errors. The error messages are not always the same.
After restarting the PCS (e.g. with a power down / power up) the PCS1 is running fine again.

Possible reason
Some of the digital outputs of the PCS1 are relay outputs. On some applications the PCS1 experiences errors such as "68k Errors" or "Invalid OPC" because inductive charges (other relays for instance) were switched with the mentioned relay outputs. 
With HW version D additional improvements were introduced to make the PCS1 less sensitive against such perturbations, but even the early CPU's (e.g. hardware version A) that left the company were conform to the EMC statements.

Solution
The corrective action is to add RC or other filters on the inductive charges, to reduce the high voltage peaks that occur if the supply of an inductive charge is cut. The best place to place the filters is directly on the source, many relay manufacturers offer optional RC cirquits that can easily be mounted.

Basically on PCD systems introduced before 2003 there are some restrictions to be considered about the maximum baud rate of serial communications.

Depending on firmware and hardware not all serial ports can be used at their theoretical maximum baud rate at the same time.

Systems introduced before 2003:

• All PCD1, PCD2 (except PCD2.M480), PCD4 and PCD6 as well as PCS1 classic contollers do have a baud rate limitation of 38.4 kB/s on each serial port.
  For older firmware (FW) versions there is a further restriction since there is one UART responsible for two serial ports and this UART cannot handle baud rates of 38.4 kB/s on both ports at the same time. The port allocation of the UARTs is the following: first UART: port 0 and 1; second UART: port 2 and 3 etc.
  This means that it isn't possible to set the concerned ports to
  - 38.4 kB/s each
  - one to 38.4 kB/s and one to 19.2 kB/s
  - but it is possible to set one port to 38.4 kB/s and one port to 9600 B/s.
  
• Due to more efficent port handling recent FW versions do have the following restriction (independent of production date of HW):
  Amount of ports available divided by 2 equal amount of ports that can communicate at 38.4 kB/s. All the residuary ports do have a maximal baud rate of 19.2 kB/s.
  In addition an UART of an PCD7.F5xx isn't able to handle 19.2 kB/s on one and 38.4 kB/s on the other port. But it is possible to assign both ports to 38.4 kB/s.

Systems introduced since 2003 (PCD2.M480 and PCD3.xxxx):

Due to faster hardware there are much higher baud rates possible on the serial ports (up to 115 kB/s)!
There is only one restriction regarding UART sharing left:
On a PCD7.F5xx it is not possible to communicate on one port at 19.2 kB/s and one the second port at 34.8 kB/s at the same time (but two times 38.4 kB/s is possible!).
This means that all ports may communicate at the maximum baud rate (which is specified in the technical information (TI) or in the manual) at the same time.

FW versions that support the new port handling mentioned above:
For the following and newer FW version the following rule is valid:
Amount of ports available divided by 2 equal amount of ports that can communicate at 38.4 kB/s.
All the residuary ports do have a maximal baud rate of 19.2 kB/s.

Communication interfaces containing a co-processor aren't restarted after a restart caused by the software watchdog with the option "Execute XOB0". In fact only a restart cold will be executed but without resetting the communication modules.

This behaviour is a bug and will be corrected in the next FW version for the corresponding CPU. As soon as the new FW is built it will be available on the support homepage.

In the meantime it is recommended not to use the option "Execute XOB0" for the software watchdog. In this case the communication modules will be reset normally on software watchdog execution.

There is a "power down reset" that can be activated in the Modem 14 Driver FBox. This hardware reset will the modem power down and up again.

For PCD2.T813, PCD2.T813Z42, PCD2.T850 and internal analogue and ISDN modems only (GSM Modems do not support the hardware reset):

In order to reset an internal modem the hardware reset output of the "Modem 14" FBox can be used.

In the adjust window for the parameter "Hardware reset option" choose "always". Additionally the Hardware Reset Output "HwR" of the FBox has to be connected to the corresponding output address written in the right side of the Fupla window (output address field).

The hardware reset output of PCD controllers is (base address of the PCD2.T8xx) +3, in the PCS1 the hardware reset is available on O 99.

Examples:

PCD2.M170 module base address = 16 hardware reset = O 19
PCD2.M120/150 module base address = 64 hardware reset = O 67
PCS1 hardware reset = O 99

In firmware version 0A1 a new functionality has been introduced that allows to use the port 0 (D sub 9 poles) a PCS1 as free port (eg. Serial-S-Bus, MC etc.). This allows the user configuring the PCS1 e.g. as gateway, using port 0 as gateway slave port.

On the PCS1 the port 0 is used for the Modem (S-Bus PGU port) and the PGU port (D Sub 9 poles). Until FW version 0A1 the PGU port could only be used in PGU mode, but not in S-Bus PGU mode. This has been improved in firmware verion 01A. Beginning with this firmware version, the D-Sub can also be used as "free serial port".

Usage in Fupla
An FBox is available for switching the Port 0 of the PCS to a "free serial port". The FBox can be found in the "Standard" FBox Tab in the family "Special" and is called  "PGU Switch(PCS1)". If the setting is "default", it is switched to the modem. If the setting is "RS232 only", the port can be used as serial port.


Usage in IL
For configuring the port 0 as "free serial port", an SYSWR instruction is to be used:  

The user program can call the mentioned instructions at any time to switch between the modem and the D-Sub port. This means that in some cases communication is lost when calling the instruction, for instance while being online with S-Bus on the D-Sub port and switching to the modem.

Configuring the port using the Online Debugger
Alternativey, the port may also be switched directly in the Online Debugger. Therefore the PCS must be stopped. Then enter (only the bold letters are to be edited):
Instruction SYSWR K 9002, K 0 for switching port 0 to the internal modem
Instruction SYSWR K 9002, K 1 for switching port 0 to the D-Sub

Important note

• Note that once the port is swiched, it will stay in this state also after a reboot. The information is stored in RAM so the state will be swiched to default when the supercap is discharged.

• The signal DSR (pin 6) of the D-Sub is used for the recognition of the PGU cable (indicating that the PG5 is connected). As soon as the DSR signal is detected as high, the port 0 will be assigned as PGU port and the previous configuration will be disabled!

• Due to the fact that the DSR signal is used for PGU line detection, no external modem can be attached to the D-SUB of the PCS.
  
  

If the program-download over modem is interrupted the program and also the hardware settings are lost. It is not possible to go online over modem again. The hardware settings has to be downloaded in PGU-mode.

Due to not fully compatible firmware chips it isn't possible for the user to download a new FW to the PCD produced between week 48/2003 and 12/2004.

The concerned PCS's FW only can be updated in Murten.

Once the FW is updated to Version 0A1 the problem won't persist any more. The version 0A1 and all later versions do support the firmware chips that were introduced in week 48 of 2003.

What does the output format "1:1" in the FBoxes for temperature sensors (PT1000/NI1000) mean?

The temperature inputs of most of our modules do measure resistance in the range of about 500 Ω to 2.5 kΩ.  If the output format "1:1" is selected, this range is represented in the resolution of the module. Therfore you'll get a signal from 0 to 255 when using a module with 8 bits resolution. The maximum value of a 10 bit resolution module is 1023 and of a 12 bit resolution module it is 4095. 

Attention has to be payed when using an analogue FBox of the HVC library. There the output always will be scaled in the range of 0..4095, also if the module has a smaller resoultion.

www.compact-easy.de

This webpage is no longer active. Due to a lack of demand this product is no longer active and can't be bought anymore.

After the installation of a new version it can happen that the Easy Suite opens with an error message (...found old project...), and you can only click OK. If this happens to you do the following:

• open the windows explorer
• go to the promos13\proj\pcs1easysuite folder and delete any files in this folder
• open the Easy Suite again, it should work as expected again

Due to not fully compatible firmware chips it isn't possible for the user to download a new FW to the PCD produced between week 48/2003 and 12/2004.

The concerned PCS's FW only can be updated in Murten.

Once the FW is updated to Version 0A1 the problem won't persist any more. The version 0A1 and all later versions do support the firmware chips that were introduced in week 48 of 2003.

The mentioned PCS1 have a wrong serial number in the memory, this is causing problems when trying to use them for Compact Easy.

Indicate the serial number printed on the PCS1 to your SBC representative. He will contact Murten and ask for a key for Compact Easy. Only the mentioned production dates are affected by the problem and if you don't use the mentioned PCS1 for Compact Easy, there is no problem.