S-Bus remote I/O's, couplers

No, it’s only possible to connect an NTC10kOhm temperature sensor to the S or E2 terminal.

If a PT1000 temperature sensor is connected to the S terminal of a  PCD7.L60x room controller, then all the time the temperature value will be used/shown, which is defined as “temperature via SBus” in the “HVC Room” F-Box of the F-Box family ‘RoomController PCD7_L60x SV2_11/13’

Yes, the fan speed can be forced over the application program.

If the room controller is used as standalone:
With the help of the register 64 of the PCD7.L60x-1 it’s possible to force the fan speed of the PCD7-L60x-1
Example:
If the register has the value:
‘30’ then the maximum speed would be 3 and the minimum speed 0
‘22’ then the maximum speed would be 2 and the minimum speed 2 -> the fan speed is set to speed 2

With the help of the F-Box ‘L60x-1 Fan Room’ dedicated symbols are generated for the fan speed and it’s possible to write from the application program in to this registers and force the fan speed,


If the room controller is used as RIO:
The F-Box ‘L60x-1 Man RIO’ have already a input ‘Fan’ which can be written with a value between 0 and 3.

Yes it’s possible to use the Y1/Y2 triac output as 2 point outputs (always off / always on) instead as PWM outputs.

To use the outputs Y1/Y2 as 2 point outputs it’s necessary to define the configuration of the output Y1/Y2 “unused” in the configuration F-Box of the PCD7.L60x.


With the help of the F-Box ‘Analog Output’ from the F-Box family 'RoomControler PCD7_L60x' it’s then possible
to set the output Y1/Y2 of the PCD7.L60x to:

Attention:
Use only the value 0,0 or 100,0% to switch off or on the Y1/Y2 outputs.
Any other value between 0.0 and 100.0% does set the output in the PWM mode.

The PCD7.L640, L641, L642 and L644 room operation device does have a integrated temperature sensor.

The temperature sensor accuracy value depends on the measurement range.

The measurement is more accurate around 25°C, and less accurate when temperature is going far from 25°C.

For Fancoil applications, the fan output is always needed and the correct handling of this output is very important.

The cooling/heating valves shall not open if the fan is not switched on.

For applications with radiator/cooled ceiling combinations normally it’s not necessary to use a fan.

But the PCD7.L60x and PCD7.60x-1 keep the cooling or heating outputs to the value 0 if the fan is switched off.

Therefore for radiator/cooled ceiling combinations applications it’s necessary to switch on the fan output, also if there is no fan connected to the output to allow the room controller to handle correctly the cooling/heating outputs.
On the F-Box, the maximum fan speed shall not be set to the value "Off".
It's recommended to put the value "Speed 1" for minimum and maximum speed.
With these settings there is no unnecessary switching of the Fancoil outputs.


These settings have to be made in the following FBoxes for the PCD7.L60x in the L60x Conf FBox.
For the PCD7.L60x-1 in the L60x-1 Fan Conf FBox.

For the PCD7.L60x also in the FBoxes L60x Room the same settings have to be made.

For the PCD7.L60x-1 there is a special FBox for controlling the fan L60x-1 Fan Room.
Therefore if the fan isn't needed this box hasn't to be placed.

In the FBox 'HVC Configuration' (L60x-1 HVC Cfg) in the FBox family 'RoomControler PCD7_60x V2' it is possible to modify the set point correction from the default value 0.5°K (step) to another value for ex. 0.4°K.

So when pressing the buton on the PCD7.L644 once, and the actual setpoint is 21°C the diplays shows 20.5 instead of 20.6°C!

After a few seconds the new set value is indeed correctly displayed: 20.6°C!

This is only a visualisation probleme during the modifiation of the set point!

Reason:
Because over RJ9 protocol (used to communicate between the PCD7.L644 unit and the room controller PCD6.L60x-1) the actual set point correction can't be send (only the default set point step 0.5° is send).

Solution:
It's possible to not show the set point value on the display during the change of the setpoint
To do this it's necessary to change the 'LCD display symbols..' parameter to 87.

On the PG5 HVC library, per default the values does have a dec.1 notation means that the 'raw' value 1234 does have a signification of 123,4.

But the 'Man AO' FBox (L60x-1 Man AO) from the FBox family 'RoomControler PCD7_60x V2' does need to have a decimal value without decimal point. (for an output value of 8.3 V the decimal value 83 have to be set)

This FBox allows the manual control of the Y3,Y4 or PWMs outputs (as long as there are not configured or used with HVC-Room FBox PCD7.L60x-1).

If connected to the output of a HVC FBox, when the input value of the 'Man AO' FBox reaches 10.0 the output (configured for example as Y3 in 0-10 V) provides 10.0 Volt

Reason:

Per default the values does have a dec.1 notation means that the 'raw' value 1234 does have a signification of 123,4.

But the 'Man AO' FBox provides an output for Y3: 0-10 Volts depending of the input signal 0-100 (not 0-100.0)
So the 'MAN AO' FBox output reach already 100% with 10.0 (100) input value

Solution:

Add a division /10 when connected to a FBox providing 0-100.0

L60x Config, L60x Room FBoxes indicates that everything is ok:

The FBox LED is green, but there is no actualisation of the values in the roomcontrollers.

It's not possible to modify any parameter of the L60x controler; setpoint, Occ mode, etc.. as the communication is frozen!

Reason:

Auto Configuration: when the configuration is loaded into a L60x the Register R 126 (ConfigTimeStamp) is writen with a time stamp.
Also in the PCDX.Mxxx master station this time stamp is memorised.
In case a PCD7.L6xx is exchanged on the network, the master station will noticed it and send the configuration automaticaly.

Problem:
The change-over signal can be connected to the input of a PCD7.L6xx/PCD7.L79xN or it can be transmitted through s-bus.
When the PCD7.L6xx/PCD7.L79xN does work as Master/Slave the change-over signal has to be transferred to the Slave. But if we choose the application "2-pipe,CO" the change-over is not transferred to the Slave and his cooling output is not working.

Solution:
For PCD7.L6xx: Install the FBox library V2.6.446 or newer.
For PCD7.L79xN: Install the FBox library V2.6.132 or newer.
With this library it is possible to use a Fbox "Load when enable" to write the change-over from the Master to the Slave when working as Maste/Slave.

Problem:
Das Change-over Signal kann über den Eingang vom PCD7.L6xx oder über den SBus angesteuert werden und muss daher im Master/Slave Betrieben über das PG5 Programm auf den Slave übertragen werden. Wenn die PCD7.L60x als Master/Slave Betrieben werden und die Applikation "2-Rohr Change-over" eingestellt wird, kann beim Slave der Change-over nicht auf Kühlen geschalten werden.

With the use of the PCD7.L645W/B, the maximum power consumption on the RJ9 jack had to be increased. That's the reason why you have to respect new minimum hardware versions of PCD7.L60x and L61x when using them together with the PCD7.L645W/B unit.

Please refer to the following compatibility table and respect the hardware versions and production dates.

Up to FW Version SV2.01 of the PCD7.L60x room controller, only the groups 3 and 4 of "light on/off" or "shades up/down" can be controlled on the PCD7.L645W/B. The groups 1 and 2 can only be controlled from FW SV2.11 of the PCD7.L60x.of the PCD7.L60x.

Solution:
From FW SV2.11 of the PCD7.L60x room controller, all the four groups can be used.
Up to FW SV2.01 of the PCD7.L60x room controller, the light- or shade-outputs have to be configured in the groups 3 and 4. Therewith,  all outputs can be controlled over 2 independent groups.

This restriction only applies in combination with use of the PCD7.L60x S-Bus room controllers (not LON)

With the FBox "L60x Config" the same configuration has been downloaded to all the PCD7.L60x modules but not all have the same operating mode!

Problem
After the powerdown the controller can be driven autonomous and the occupancy can't be controlled over the room operation unit.

Solution
It is neccessary to activate the "Presence button" on the operating Device or in the fupla program to change the state of the input "Occ" of the L60x Room Fbox from 0 ->1 ->0 again!

Remark:
A new functionnality is planned for the PCD7.L60x which will allow to select a user defined Operating Mode (OccMode) on power up, like it is already the case for the PCD7.L79x(N)!
 

This FAQ explains how to configure the dew point functionality of the room controllers PCD7.L60x and PCD7.L79x.

If the dew point has to be detected in cooling mode of the room controller this should be done by connecting the dew point sensor to the input E2 (and select in the config FBox its functionality as dew point):

 

If the dew point has to be set over the S-Bus or in the "Room" FBox, then it has to be used in minimum the FW version SV1.15 (for the PCD7.L60x) and SV1.16 for the PCD7.L79x.


Remark
In case the logic of the dew point sensor is to be inverted, this can be realized by writing the register 114 to 1 (minimal firmware supporting this inversion is 1.15 for the L60x and 1.16 for the L79x).

This FAQ explains how the wireless remote control PCD7.L662 can be linked to the wireless receiver with multi-sensor PCD7.L666.

Introduction
In order to use a wireless receiver with multi-sensor (PCD7.L666) to control the room controller by the wireless remote control PCD7.L662 the configuration tool PCD7.L662-CT is required to link them together.

Configuration procedure

On the remote control PCD7.L662:

• press 'FAN'+'TEMPERATURE'+'UNOCCUPIED'+'OCCUPIED' simultaneously
  --> the remote is now waiting for linking.

On the PCD7.L662-CT:

• direct it to the multisensor (infrared signal will be sent at next step)
• simultaneously press 'FAN'+'TEMPERATURE'+'UNOCCUPIED'+'OCCUPIED'
• simultaneously press '+' and '-'

On the remote control PCD7.L662:        

•  A 4 digit ID must appear, corresponding to the multisensor ID.

If this is the case, the products are linked. Test it with any function to check correct operation.

If the controller is used without an S-Bus connection and there is a power supply interrupt, the occupancy mode (OccMode) of the controller is initialized with the value 1 (unoccupied) after restart.

What to do if I need another mode after restart?

• If the controller is supposed to run in Stand-By mode (OccMode 2), a little workaround is needed:
  In the adjust window of the Config-FBox the parameter “Dead band reduced mode” and the “Dead band standby mode” need to contain the same values. (Or it can be written directly in the register 4)
  
  
  
  (And the “Coasting Comfort Mode x10min” has to be left on the initial value 0 => register 0)
  
  
   
• If the controller is supposed to run in Comfort Mode (OccMode 0), a little workaround is needed:
  In the adjust window of the Config-FBox the parameter “Dead band reduced mode” and the “Dead band comfort mode” need to contain the same values. (Or it can be written directly in the register 4)
  
  

The FBox libraries required can be downloaded from the support website, the version of the libraries must be:

• For PG5 1.4:
  PCD7.L60x RoomController FBox library version 2.5.166 or later
• For PG5 2.0:
  PCD7.L60x RoomController FBox library version 2.6.166 or later
  
  

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

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

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

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

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

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

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

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

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

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

Yes, starting with firmware version 3.1 this feature is possible.

How to define the duration of the time the RIO modules are rotating back the lamellas?
The time the lamellas are rotated after the the end position has been reached can be defined with the register 17 of the modules PCD7.L120 and PCD1.L121 (with firmware 3.1):


Remark
The first modules equipped with firmware 3.1 have been delivered in May 2010.

Up to now the Ni1000 L&S is not present in the Device Configurator of PG5 2.0 (e.g. in PG5 2.0.150). In order to connect such temperature sensors, the read temperature needs to be converted.

Symptom
It is not possible to configure the Device Configurator to read an analogue value according to the specification for a Ni1000 L&S.
Similarly, it is not possible to configure a PCD7.L310 to interpret a temperature sensor with the specification of a Ni1000 L&S.

Reason

• Device Configurator
  The device configurator does not provide the sensor type Ni1000 L&S because the according conversion table is not present in the firmware of the PCD to be configured. 
• PCD7.L310
  The PCD7.L310 does calculate the temperature directly from the measured resistance of a Ni 1000 DIN 43760 sensor which is to be connected to its inputs.

Solution
In case a Ni1000 Tk 5000 (or Ni 1000 L&S) is to be connected to a analogue module (which supports Ni1000 sensors) and this module is configured with the Device Configurator, the temperature which is read needs to be scaled. The following settings have to be used:

§ix101504§

The correction factor from the value received from the DC / PCD7.L310 to the temperature if a Ni 1000 Tk 5000 sensor is connected is 1.234 (1.23430072 to be very precise).

The correction can easily be calculated by using the conversion FBox from the HVC general FBox library:


Remark
A modification of the Device Configurator and the firmware versions in order to support the Ni1000 L&S sensors is in preparation. This FAQ will be updated as soon as the direct configuration of these sensors is possible.

On the room controller PCD7.L60x the firmware version is printed on a label on the device and on the package. The firmware is indicated behind the "SV".

When has which version been delivered?

• starting in April 2007 hardware version V1.1 and firmware (software) versions SV1.05 and SV1.07 has been deliverd
• in May 2009 the hardware has changed to V1.2 equipped with firmware 1.08
• in September 2009 the firmware has been changed to version 1.11

Remark
Please note that firmware version 1.11 required the new FBox library version 2.1.007 (for PG5 1.4.300).

If the "Electric Heat" output K 1/2 of the PCD7.L60x room controllers is written to 100% in RIO mode, it is still switched off after around 15 minutes for 2 minutes.

Symptom
If the "Electric Heat" output K 1/2 of the PCD7.L60x room controllers is written to 100% in RIO mode, it is still switched off after around 15 minutes for 2 minutes. The firmware version (called SV on the label sticker) of the room controller is 1.08 and older.

Reason
This feature (switching off the output after 15 minutes for 2 minutes) has been implemented as "security mechanism" for the case that a battery is connected to the K 1/2 output.
As the experience has shown that this feature is not required, it has been removed in firmware version 1.11 and later.

Solution
In case the described behavior does negatively influence your installation, please replace the concerned controller by one with firmware version 1.11 or newer.

Remarks

• Please note that for working with room controllers PCD7.L60x with firmware 1.11 the FBox library 2.1.007 (for PG5 1.4.300) is required.
• Room controllers PCD7.L60x with firmware version 1.11 are delivered starting in September 2009.

Due to a restriction of the firmware before SV 1.08 of the PCD7.L60x room controllers, the Fan Speed output of the devices in RIO mode are not working correctly. This phenomenon can also occur if a too old FBox library is used.

Symptom
The value written to the "Fan" input of the FBox is not written to the hardware output of the room controller. The other outputs may work correctly though.

Solution

• The FBox library "Room Controller PCD7.L60x" is too old. Please update to the newest library found on our support site in section "Room Controller" -> "PCD7" -> "Lxxx" -> "L6xx".
  
• If the room controller hardware has firmware older than SV 1.08 the workaround mentioned on the support site (section "Room Controller" -> "PCD7" -> "Lxxx" -> "L6xx") can be applied. This workaround bases on the trick that both (upper and lower) limits of the fan speed are written to the desired fan speed (and therefore forcing the actual fan speed to the correct value). This workaround is not necessary for firmware SV 1.08 and later of the PCD7.L60x!
  The firmware 1.08 has first been delivered in April 2009.

Remark
Please note that the firmware of the room controllers PCD7.L60x can not be updated.

Thanks to the analysis of returned modules we have found that several PCD7.L79x devices were damaged due to inconsistent polarity of the connected AC power supply. This can be the case if no attention is paid to the terminal indications "24V" and "GND".

Symptom
A damaged communication port.

Reason
If GND and 24V are mixed on several units connected to the same S-Bus network, one or more serial communication interfaces of the module(s) are destroyed. Please make sure that all PCD7.L60x are connected the same way to the AC power supply as shown below:

Starting from resource pack 1.01 the PCD7.L611 LON controllers can be configured to use the 0..10V output as cooling signal. The nciCfgIrc.ValveType has to be set to 2 to choose the option.

All possible values of  nciCfgIrc.ValveType:
0 = thermal 230V
1 = 3 point
2 = 0..10V

The PCD7.L600, L601 and L603 room controls units delivered since April 2009 are equipped with a different connection terminal in comparison with the units which are delivered before April 2009.

The new units have the version 1.2 SV 1.08.

The connecting terminal on the output side (below) has changed.

First version: V1.1/ to SV1.05 and SV 1.07 delivered from 04/2007 until approximatly week 15, 2009:

New version: V1.2 from SV 1.08 delivered from week 15, 2009



Detailed description for PCD7.L600:
Version 1.1:

Version 1.2:

Detailed description for PCD7.L601:
Version 1.1:

Detailed description for PCD7.L602:
Version 1.1:

Detailed description for PCD7.L603:
Version 1.1 and version 1.2

Thanks to the analysis of returned modules we have found that several PCD7.L602 and PCD7.L603 room controllers were damaged due to inconsistent polarity of the connected AC power supply. This can be the case if no attention is paid to the terminal indications "24V" and "GND".

Reason
If GND and 24V are mixed on several units connected to the same S-Bus network, one or more serial communication interfaces of the module(s) are destroyed. Please make sure that all PCD7.L60x are connected the same way to the AC power supply as shown below:

Belimo does offer new 6-way valves which can be controlled with a 0..10 V input (0..3V: heating; 3..7V: dead range; 7..10V: cooling). These valves can be driven by a PCD7.L6xx room controller.

Introduction
Belimo does offer new 6-way valves which can be controlled with a 0..10 V input (0..3V: heating; 3..7V: dead range; 7..10V: cooling).

Can such a valve be driven by a PCD7.L6xx?
Yes, since the PCD7.L6xx with firmware SV1.12 (January 2010).

You have to select the following option in the Fbox Config:

The FBoxes for the room controllers need quite a lot ressources. Therefore it is depending on the project, how many room controller FBoxes can be introduced in a project.

Based on our experiences we stronly recommend not to connect/program more than 45 Room controllers per PCD.

Required ressources:

In the description of the Occmode there is an error.

Wrong description:
In the help of the PCD7_L60x FBox the description of the occupancy mode is:
0=Reduced 1=Comfort

Correct description:
The correct description is:
0=Comfort 1=Reduced

It is inverse than mentioned in the FBox help.

In case connectors for the PCD7.L62x modules are required, please refer to "Good to know" on the room controller section on the support page (link below).

Normally the internal symbols of the FBoxes for the PCD7.L60x should be inserted in the global symbol list as soon as the FBox is placed in the project. If this does not happen you, have to change your settings in PG5.

Problem
The internal symbols of the PCD7.L60x FBox are missing. Normally they should be created automatically when the FBox is placed in a Fupla File

Reason and Solution
If this does not happen, you have to change the following settings: Select in Fupla: View/Options/Symbols and check the option: "Delete the internal Symbols when the FBox removed". Now the F-Box symbols will be added to the global symbol table immediately if a new PCD7.L60x F-Box is inserted in the Fupla page.

The reason for this behaviour of a PCD7.L6xx is often related to the window contact which is not closed.

Problem
Even if the temperature is lower than the limit temperature, the heating output is not set. The FBox shows the status "frost protection".

Reason
The window contact is per default configured as: Normal state window contact=closed. In this case the PCD7.L60x checks the window contact. If nothing is connected to this conntact it won't start heating until it reachs the frost protection point.

Solution
If the contact is not used for a real window contact you must either have a bridge between the contact 7 and 8 to simulate the window contact as closed or you have to define the window contact in the "Config" F-Box as: Normal state window contact=open.

On the back side of the module you find a stamp which such a code, for example: 51R 2.2. The meaning is 51st week of 2003 firmeware version 2.2. See below the year code:

Reading Input 5 to 8 of the PCD7.L100/L200 leads to a NAK response.

Problem
The status of the manual switch from channel 1 to 4 is stored in addresse 5 to 8 of the PCD7.L100/L200. When trying to read this addresses as input from the debugger or OPC server a NAK response is returned from the PCD instead of the status.
Reason
These status can only be read as Output.
Solution
Instead of Display Input you have to use the Display Output command and it will work

The first PCD7.L60x module series keeps the presence for 1 hour once the button "Presence" is pressed. It can't be desactivated manualy as it is done automatcaly after 1 hour!

This is the default parameter: R 0 = 6 (6 x 10 minutes).

Solution
In order to modify this default parameter connect over a S-Bus connection to the PCD7.L60x and modify the register 0 with the value 0 (instead of 6)! So one press on the presence button activates the presence and a 2nd press desactivate it!

Remark
The new PCD7.L60x have now as default the value 0 (since about begining 2008)!

When values are read from a PCD7.L1xx or a PCD7.L3xx module, the preparation of the S-Bus response telegram needs about 10 ms. This time is longer than the same task does take on a PCDx.Mxxx CPU. The time used for writing a value to a PCD7.Lxxx module is about equal to the time that is used by a PCDx.Mxxx CPU (because only an acknowledgement needs to be replied).

Symptom
The communication cycle time for reading e.g. 4 bits from some PCD7.Lxxx modules is higher than the communication cycle time for reading the same amount of data (with the same number of telegrams) from PCDx.Mxxx CPUs.

Reason
This phenomenon is caused by the fact that a PCD7.Lxxx (e.g. a PCD7.L100) has a slower processor than a PCDx.Mxxx CPU. The preparation of an S-Bus telegram does therefore take longer (about 10 ms per response).

Remark
This rule does only apply when reading from a PCD7.L1xx or a PCD7.L3xx module. The treatment of requests for writing values (outputs) to the module is much faster (because only a "simple" acknowledgement needs to be responded). 

The library of the "RAG Einzelraumregelung" (for the obsolete product PCD7.L71x) is not distributed with recent PG5 versions. In case a project is to be updated and this FBoxes are still needed, please download it from this FAQ.

Symptom
After importing an old PG5 project containing the FBoxes for the obsolete PCD7.L71x room controllers, not all FBoxes are found. During the build, PG5 prints the following error messages:
Compiling: D:\Projects\PG5_1_4_Projects\CustomerCPUs\MyProject\MyFupla.fup
S-FUP: Error 65: MyFupla.fup: Page 1(47,28-1): FBox not in library.
After double-clicking the error messages, Fupla opens and e.g. an FBox "PCD7L712" or "EZRCOM2" like in the screenshot below is shown:


Reason
As the products PCD7.L71x are obsolete, the according FBoxes are not installed by default (in order to avoid confusion with the current, similar products).

Solution
Download the library from this FAQ and launch the self-executable "Ragezr.exe". It will extract the library files directly into the same folder as the "Ragezr.exe" is stored. Cut these files and paste them in the folder "c:\Program Files\SAIA-Burgess\PG5 1_4\Libs\Usr\" (for PG5 1.4).
Once this is done, you'll be able to compile the project.

Additional information
The library contained in "Ragezr.exe" contains the following Fupla Macros: _EZRCOM2, _RAGEZR, _RAG12, _RAG11, _RAG10.

In case the PCD7.L120 is not configured as RIO it is not possible writing the outputs.

Symptom
The inputs of the PCD7.L120 can be read by the PCD but the outputs can't be activated by the PCD.
 
Reason
In order to use the PCD7.L120 as RIO modul it is necessary to activate this function through the parameter register 12 as mentioned in the leaflet: by default the register 12 contains 1 (application) it has to be changed to 0 (RIO).

Solution
Connect to the L120 S-Bus station with the debugger after having configured the port of the PCD master as S-Bus gateway port in the hardware settings.
Once you are online with the PCD in the Online Debugger, type:

• Connect Sbus-station <station nr> <enter>
• Write Register 12 0 <enter>
  

The Sasi and the Send F-Box to the PCD7.L400 FW Version 3.0 is getting red from time to time.

Problem
One "Send" F-Box is sending 4 registers to the PCD7.L400. This Send F-Box and the Sasi F-Box indicates a communication error from time to time and the communication cycle time is getting high.

Reason
Do to a short timeout, this problem can appear when reading registers with a baudrate <=9600.

Solution
This timeout can be adjusted by writing register 8 to a value of 4 for 9600 baud (6 for 4800 baud).

This RIO modules need some time to synchronize the baudrate and establish communication.

Problem
The communication between a Master Station and a RIO modules doesn't work. There is an "S-Bus Station" FBox used in the project and on the whole S-Bus only RIO modules are placed (no other S-Bus slave station like e.g. a PCD3).

Reason
The "S-Bus Station" FBox tries only once to connect the slave. If the connection was not successful it waits 10 seconds (default) and after a second try it waits 60 seconds (default). Since the RIO modules need some time to synchronize the communication will never work. If there is no S-Bus slave station that does not need to synchronize, the RIOs don't have enough traffic to synchronize their UART.

Solution
Change the communication speed to the default value: 9600 bits/s
or
Remove the S-Bus Station FBox from the project until the module(s) are synchronized. If they are once synchronized the S-Bus Station FBox can be added again. As long as the communication works properly on the same baudrate the modules won't start autobauding anymore. If this isn't possible; check that Output 255 (auto baudrate) is activated = 1 using the "Online Debugger" over Gateway and type: Display Output 255. If = 0 type: Write Output 255 1
or
Deactivate the autobauding and set the RIOs to a fixed baudrate. Autobauding can be switched of by writing Output 255 to 0. Connect to the RIO over a Gateway using the "Online Debugger" and type: broadcAst Write Output 255 0.
More detail in FAQ below 100430.

You are able to read Baud rate, Module address, Status regsiter, Bus timer... on the PCD7.L1xx - L4xx.

Diagnostic Registers
To access the information directly you have to configure a "master gateway port" on the PCD. Now you are able to connect the modules using the Online Debugger (Connect / S-Bus Station). With Display Register xx you are able to read the following informations:

The information can also be read an used in the programm.

Attention
Older Versions of the PCD7.Lxxx had always the staus register on regsiter 7 and 10. So if you exchange an old modul and you where observing register 10 as status register you have to change register 10 to register 7.

Status regsiter information
The most important information are stored in Bit 0 to 5 and 8 to 10 of the status register. Bit 12 to 15 are containing the status information of the swich (Automatic=0/Manual=1) when the modul is supporting it (Switch 1-4 on Bit 12-15: L100/L101/L110/L200/L201) (Switch 1-2 on Bit 12 and 13: L120/L121). All other Bits are reserved for factory tests

The messured temperatures are frosen about 50°C. If the roomtemperature is frosen at 50°C the controler are cooling at maximum.

If an external peak on any contact reaches the L72x about an level of less than -10V the internal AD converter will be out of order.

This can happen if the scheeld is contacted to any clamp of the controler. It is vorbidden to contact the scheeld to the controler L72x.  If an external peak hits the controler the new FW V23 restart the AD converter and the L72x works again.

In this case an minimum FW Version V23 is nessesare. To update the FW of PCD7.L72x please contact your local SBC Support.

The communication with the master station doesn't work and the green LED blink!

Check the power supply! All the hardware serie up to and including V 12 are very sensible regarding the power supply level. If we have less than 24 VCA (-10%) this phenomenon occurs, it might also happens if it is within the - 10% tolerance ( for example 22 VCA). Make sure you have really 24 Volts!

The harware serie V 12 SR have a correction which solve that over sensibility problem. The new serie from v 22 are OK.

The RIO modul PCD7.L100 / L 200 doesn't respond. It is frozen , all the LED are switch off and it doesn't communicate anymore! After a powerup the RIO communicates again properly. This phenomenon occurs in an enironment with electronmagnetic noises. The very new PCD7.Lx00 have a filter which cures that problem. If it isn't possible to reduce the noises, try to change the PCD7.Lx00 module, the new one should be at least of the version S 18 (stamp on the modul).

Every RAIL and SAFE modules fulfil the standard DIN EN 61000-6-2 (interface resistance).

That means that the communication "bus line" is proved for an interference resistance +/- 1kV

capacitive load . Modules with firmware <2.1 had a tolerance in the inerference resistance up to

+/- 4kV.

Modules with the firmware 2.1 and 2.2 will actually interrupt the working condition if the EMC influence

in the communication bus line is higher than 3 kV.

All RAIL modules with firmware 2.1 and 2.2 can have a communication conflict. They have been de-livered approximately from June 2002 till now. The RAIL modules can stop their running mode and freeze itself in stop condition. The stopped mod-ule can only be reconditioned to running mode by a manual replacement of the power supply! The stopped working condition appears due to a new integrated processor that has a lower EMC (electro magnetic compatibility) tolerance than in module series with firmware lower 2.1. Modules with integrated new processor:

PCD7.L100 , PCD7.L110

PCD7.L121 (SAFE module with new functionalities)

PCD7.L200 

PCD7.L300, PCD7.L310

PCD7.L400

EMC compatibility

 Every RAIL and SAFE modules fulfil the standard DIN EN 61000-6-2 (interference resistance)! That means that the communication bus line is proved for an interference resistance +/- 1kV (capaci-tive load). Modules with firmware <2.1 with the former processor and less features had a tolerance in the inter-ference resistance up to approximately +/- 4kV (remember: the proved and official resistance is +/- 1kV). Modules with firmware 2.1 and 2.2 will actually interrupt the working condition if the EMC influence in the communication bus line is higher than 3 kV.

 Short term solution

 If there are some modules which indicate the described failure, the following improvements are possi-ble: 1. The bus line should be installed as described in the RS485 manual (26/740) to be sure that the bus line is free of any electromagnetic compatibility (EMC) influence. 2. With adding two external “Varistors” (Type: SIOV S07 K60) in the busline according to the drawing below at every single module, it is possible to increase the EMC interference resistance to +/ - 4.5kV.

 Varistor type: Disc-Varistor SIOV S07 K60

Possible Distributor: EPCOS AG (international) Homepage: www.epcos.com

Ordering code: B72207-S600-K101

Varistors are usually available in every electronic components store!

Important note:

With use of external Varistors is it possible that some S-Bus telegrams go lost. The higher the baudrate and the more bus members are involved, the higher the probability to loose telegrams.

Therefore we do not recommend to use a communication baudrate of 38’400 baud if the project has long distances, more than 50 S-Bus members and if external varistors are added!

Long term solution

The supplier BTR is about to improve the EMC interference resistance up to +/- 4.5kV of the module types mentioned above. This requires a modification of the module manufacturing process. The new modules will have an integrated interference resistance of around +/- 4.5kV without any restrictions.

The communication is interrupted for a while (red LED on) and works again by itself (green LEd on) after a few secondes or minutes! Some telegrams are lost.

The new modules are slower than the previous ones. It may be necessary to modify the bus timer.
Therefore follow this procedure:
Configure the master station as Gateway and connect to the RIO slave station with the Online Debugger by typing 
"cOnnect Sbus station xx"
Type: Display Register 8 (10 is displayed = 100 ms)
Type: Write Register 8 2 (20 ms)

If the commnucation isn't yet completly improved, it is needed to change also the parameter Bautrate. In fact the following command disables the "auto baud" functionality. The result is an approved communication because the modules won't try to detect the baudrate after corrupted telegrams.
Type: broadcAst Write Output 255 0 (-->automatic baudrate inactive)