DCS-CU Control unit
DCS-CU Control unit
HISTORY
Issue Date Details Of Change
1.0 20/10/2009 First Emission
1.1 28/07/2010 General revision, added DCS.ST & DCS.AUX
1.2 27/09/2010 Revision
2.0 System diagnostic,
Fw specific for motor type M
0/02/2011
Interworking softouch Vs touchscreen,
Fw specific for DCS.ST01 (single unit softouch controller).
All rights reserved to Speich Srl. Disclosure, reproduction or whatsoever use of this
Date Issue2.0
document and of any data herein contained without the prior written authorisation of
Feb 2011
Speich Srl is forbidden. Violations will be persecuted.
DRAFT 3 ( 15 )
CONTENTS
1.1. DCS System components ............................................................................. 4
2. DCS SYSTEM BASIS .................................................................................. 6
2.1. Wiper/group assignment scheme .................................................................. 6
3. DCS SYSTEM GENERAL WIRING SCHEME .............................................. 8
3.1. CAN bus Communication network ................................................................. 8
3.1.1. CAN Bus network cable .......................................................................................................................... 9
3.2. Motor Power Feeding .................................................................................... 9
3.2.1. Electric Motor power cable ................................................................................................................... 11
4. DCS.CU Controller Unit ........................................................................... 11
4.1. Controller Unit installation procedure .......................................................... 11
4.1.1. DCS Controller address setting ............................................................................................................ 12
4.1.2. CAN Bus termination setting ................................................................................................................. 13
4.1.3. Can Bus connection.............................................................................................................................. 13
4.1.4. Stroke End switch connection ............................................................................................................... 14
4.1.5. Wiper parking position selection ........................................................................................................... 14
4.1.6. Power supply connection ...................................................................................................................... 15
4.2. CAN Bus network diagnostic ....................................................................... 15
All rights reserved to Speich Srl. Disclosure, reproduction or whatsoever use of this
Date Issue2.0
document and of any data herein contained without the prior written authorisation of
Feb 2011
Speich Srl is forbidden. Violations will be persecuted.
DRAFT 4 ( 15 )
All rights reserved to Speich Srl. Disclosure, reproduction or whatsoever use of this
Date Issue2.0
document and of any data herein contained without the prior written authorisation of
Feb 2011
Speich Srl is forbidden. Violations will be persecuted.
DRAFT 5 ( 15 )
All rights reserved to Speich Srl. Disclosure, reproduction or whatsoever use of this
Date Issue2.0
document and of any data herein contained without the prior written authorisation of
Feb 2011
Speich Srl is forbidden. Violations will be persecuted.
DRAFT 6 ( 15 )
All motors belonging to one group receive the same command from the user interface (Softouch control panel, Touch-
screen control panel or on-board integrate system), thus they run all in the same modality (intermitting, low speed, high
speed).
Whenever it is requested the possibility to control one motor individually, a relevant group shall be created that include
just that motor and no other ones. For example, if a system consists of five wipers to be managed independently, it is
necessary to define it as composed of five groups, each of them consisting of one wiper.
According to the above, in the next of the document “wiper” or “group of wiper” have got the same meaning and for con-
venience they can be named “wiper/group ”
The auxiliary devices are managed in a similar way. Standard configuration foresees that to each group are assigned
their own auxiliary units, thus making it possible to activate the auxiliary devices singularly and for each group independ-
ently from other groups. For example, the FRONT group auxiliary unit the electrovalve of water/air front line and the
heater of all windows that belongs to FRONT group, the PORT group auxiliary unit drive the auxiliaries of PORT installa-
tion and so on.
Note:
It is also possible to configure the one DCS.AUX unit or DCS.EXT.AUX unit in order to be shared among all groups. In
this case, indeed the number of the grups which are present, the auxiliary devices are one for all the installation ( for
example, one water electrovalve for all windows).
Therefore, care shall be taken when DCS Softouch panel or DCS.TS touchscreen panels are present. For these sys-
tems, in fact, the correspondence between wiper groups and activation keys is fixed, i.e. a one to one correspondence
exists between the group identifier Gid and the wiper/group keys that are present on the panel.
To facilitate end user comprehension, care should be taken to match as much as possible the assignment of a wiper to a
group (by the Gid) with the deck layout that is schematized on the panel. On DCS Softouch and DCS.TS touchscreen
control panel the wiper/group assignment is done according to the scheme reported in Figure 1 and in Figure 2.
All rights reserved to Speich Srl. Disclosure, reproduction or whatsoever use of this
Date Issue2.0
document and of any data herein contained without the prior written authorisation of
Feb 2011
Speich Srl is forbidden. Violations will be persecuted.
DRAFT 7 ( 15 )
The composition of each group can be flexible chosen, therefore it must be considered the following limits:
Example
All rights reserved to Speich Srl. Disclosure, reproduction or whatsoever use of this
Date Issue2.0
document and of any data herein contained without the prior written authorisation of
Feb 2011
Speich Srl is forbidden. Violations will be persecuted.
DRAFT 8 ( 15 )
The wiring scheme essentially foresees two cable connections, which are:
- CAN bus communication network.
- Motor power line, 110/220V
The position of the different elements along the line is not fixed, as well as the positioning of the DCS Auxiliary unit
(DCS.AUX). This possibility allows the maximum flexibility in arranging cable ducts and reduces the length of the cable to
lay down.
Important Note:
The system does not support other network topology rather than a bus line. For this reason, all
connection must be done only using the CANBus RJ45 adapter (See Figure 4).
All rights reserved to Speich Srl. Disclosure, reproduction or whatsoever use of this
Date Issue2.0
document and of any data herein contained without the prior written authorisation of
Feb 2011
Speich Srl is forbidden. Violations will be persecuted.
DRAFT 9 ( 15 )
Any cable matching with the above Cat5e specifications can be used. Therefore, it is convenient the use of pre-wired
FTP patchcords for connection of motors to CANbus line (Speich can provide pre-defined cabling kit on request).
Following table reports the colour marking of the Cat5e cable according to TIA/EIA-568 A&B specification.
Important Note:
Once a wiring scheme has been adopted, the same shall be used for wiring RJ45 connectors at
DCS.AUX units and at DCS.ST control panel.
Alternatively, to reduce the number and length of the cable to lie down, a power bus can be deployed that runs over all
bridge and where power feeding of each motor is derived. This option allows also adopting smaller section cables to
connect the motor (see Par 3.2.1). In this case, the DCS.JB equipment can be adopted to locally distribute the power
from the bus to each single motor (see Figure 6).
All rights reserved to Speich Srl. Disclosure, reproduction or whatsoever use of this
Date Issue2.0
document and of any data herein contained without the prior written authorisation of
Feb 2011
Speich Srl is forbidden. Violations will be persecuted.
DRAFT 10 ( 15 )
The Controller Unit performs protection of the electric motor against overcurrent and overload. For this reason use of
magnetotermic breaker switch or fuse per single motor is not strictly required. Therefore one magnetotermic breaker
switch of the appropriate load is required to be installed on the main power line to protect it and to facilitate maintenance
operation.
Important note:
Due to the absorption characteristics of the system, use ONLY D Type (Retarded curve) mag-
netotermic breaker switch on the motor feeding power line
All rights reserved to Speich Srl. Disclosure, reproduction or whatsoever use of this
Date Issue2.0
document and of any data herein contained without the prior written authorisation of
Feb 2011
Speich Srl is forbidden. Violations will be persecuted.
DRAFT 11 ( 15 )
Please consider that the connector terminal block accept cables with the following characteristics:
Conductor cross section stranded, with ferrule without plastic sleeve (min–
0.25 mm² - 1.5 mm²
max):
Conductor cross section stranded, with ferrule with plastic sleeve (min–max): 0.25 mm² - 1.5 mm²
During cable installation, care shall be paid to fix it is such a way that the cable does not gener-
ate excessive forces or torsion on the connector and its housing
Cable fixing system shall be used to reduce the weight of the cable on the connector
Risk of electric shock. Never remove unit cover and access Controller Unit before disconnecting
the power line by removing the power supply connector
All rights reserved to Speich Srl. Disclosure, reproduction or whatsoever use of this
Date Issue2.0
document and of any data herein contained without the prior written authorisation of
Feb 2011
Speich Srl is forbidden. Violations will be persecuted.
DRAFT 12 ( 15 )
Always connect CANBus lines connector BEFORE connecting the Power line.
Each DCS Controller Unit is equipped with a slide dip switch that allows
to correctly set the unique identifier by defining the motor number Mid
and Group number Gid.
To assign the Mid and Gid identifier to the unit, remove the unit cover to
access the dip switch inside. The dip switch provides eight contacts
numbered 1 to 8, which can be either ON or OFF. The dip switch con-
tacts are assigned as follows:
Motor unit (Mid): switch contact 1, 2, 3
Group number (Gid): switch contact 4, 5, 6, 7
By changing the position of the contact of the dip switch, a unique identi-
fier can be assigned to the DCS Controller unit.
The correspondence between motor and group number and contact
position is reported in Figure 7
Example:
Motor 1 of Group 0 Mid = 1, Gid = 0
dip switch contacts (1 to 7) are: 0.0.0.0.0.0.0
Motor 2 of Group 0 Mid = 2, Gid = 0
dip switch contacts (1 to 7) are: 1.0.0.0.0.0.0
Motor 1 of Group 1 Mid = 1, Gid = 1
dip switch contacts (1 to 7) are: 0.0.0.1.0.0.0
Motor 2 of Group 1 Mid = 2, Gid = 1
dip switch contacts (1 to 7) are: 1.0.0.1.0.0.0
Motor 6 of Group 7 Mid = 6, Gid = 7
dip switch contacts (1 to 7) are: 1.0.1.1.1.1.0
All rights reserved to Speich Srl. Disclosure, reproduction or whatsoever use of this
Date Issue2.0
document and of any data herein contained without the prior written authorisation of
Feb 2011
Speich Srl is forbidden. Violations will be persecuted.
DRAFT 13 ( 15 )
NOTE:
When a DCS Softouch panel is used, care should be taken in assigning the Gid to the different motors. Please refer to
Paragraph Errore. L'origine riferimento non è stata trovata. for more details
Pay attention that the RJ45 wiring scheme is consistent with the one adopted for the connection
of the motor over the CANBus line (TIA 568A or TIA 568B). The RJ45 connector shall be pre-
pared according to the following wiring scheme:
All rights reserved to Speich Srl. Disclosure, reproduction or whatsoever use of this
Date Issue2.0
document and of any data herein contained without the prior written authorisation of
Feb 2011
Speich Srl is forbidden. Violations will be persecuted.
DRAFT 14 ( 15 )
Once the RJ45 plug has been inserted in the adapter, secure to the FTP cable to a cable race-
way, the structure or the power supply cable. Act in order the cable do not weigth on the con-
nector and it is not subject to vibrations.
When adopted with motors of Series M and S, the DCS Controller Unit allows setting the parking position of the wiper
(Right or Left) without any change on the mechanical part of the motor. To set up the parking position, access the DCS
Controller unit inside its box, and act on the contact number 8 of the dip-switch.
All rights reserved to Speich Srl. Disclosure, reproduction or whatsoever use of this
Date Issue2.0
document and of any data herein contained without the prior written authorisation of
Feb 2011
Speich Srl is forbidden. Violations will be persecuted.
DRAFT 15 ( 15 )
Figure 10: dip switch contact position for selection of self-parking side
The CAN bus communication led that is present on the board blinks every time the Controller Unit receives a message
over the network.
This led can be used for a first level network diagnostic. In particular, after few seconds it has been powered, the Control-
ler unit should receive from other Controller units a number of control messages.
Always “On”
for max System powered, controller starting up. Correct functioning.
10secs
MOTOR NOT RUNNING
4sec Correct functioning. Controller receives and transmits over CANbus line.
CANBus error
10ms with
The controller is not communicating over the CANBus line. Please check:
double blink
Correct CANBus connector installation;
every 1sec
Correct setting of CANbus line termination (Par 4.1.2 )
All rights reserved to Speich Srl. Disclosure, reproduction or whatsoever use of this
Date Issue2.0
document and of any data herein contained without the prior written authorisation of
Feb 2011
Speich Srl is forbidden. Violations will be persecuted.