Академический Документы
Профессиональный Документы
Культура Документы
_____________________________________________________________________________________
BROMMA CONQUIP AB 00 01 ENG
rev.
use and maintenance
Bromma spreaders
1 INTRODUCTION
5 SAFETY PRECAUTIONS
6 START-UP PROCEDURES
7 MAINTENANCE PROCEDURES
12 APPENDICES
_________________________________________________________________________________
.01
Bromma Group Manual
BROMMA
spreaders
Operation Manual
BROMMA spreader
Operating Movements
Electrical Equipment
Hydraulic Equipment
Filter
Corrosion protection
telescopic arms
Lifting lugs
TELESCOPIC SYSTEM
HYDRAULIC UNIT
MAIN ELECTRICAL CABINET
TWISTLOCK
Automatic flippers
Manual flippers
A specially designed slotted adapter fits fixed flippers to the end of beam
The spreader structure is designed according to DIN 15018 and to the
following loading group which represents a container handling crane.
HOISTING GROUP H2
LOADING GROUP B4
LIFTING CASES
a)
b)
Safety features
1.
2.
3.
4.
NOTE ! When carrying out maintenance on the twistlocks, the blockading pin clamps can
be fitted to each corner, to by pass the electric and mechanical blockading when running
the twistlock.
5.
6.
In-plant testing
STRUCTURAL
FUNCTIONAL
Bromma Group Manual
See Appendix
Bromma Group Manual
Warnings
The manual contains vital information for the safety of personnel and the
correct use of the spreader.
Bromma Group will not accept any liability for the use of the spreader for
any purposes outside what is described in the manual.
DO NOT exeed the Safe Working Load (SWL) of the spreader bar. The Safe
Working Load is shown on the nameplate that is permanently affixed to the
side frame of the spreader.
Safety precautions
2. The spreader must only be used for the purpose for which it is
designed.
6. Stay clear of all moving parts, such as guide arms (flippers), moving
beams, telescopic chains, etc. A safe distance is 5 meters.
12. Care must be taken when performing any maintenance inside the
spreader frame. It must be carried out under extreme caution and by
personnel familiar with risks related to spreader function and
movements. Serious injury by crushing can occur
13. Contact Bromma Conquip AB before doing any repair work on the
spreader apart from replacing normal wear parts.
14. DO NOT walk or stand beneath the spreader bar during operation.
15. DO NOT attempt to lift a container that is not level (+/- 5°).
19. DO NOT stand between a container and any construction that many
prevent your movement to safety. A definite hazard exists that could
cause serious injury or death by being crushed between the container
and an obstruction (such as a building or another container).
20. Mobile work platforms which are used in repair and service work on the
spreader must be equipped with safety rails and kick plates.
22. The tower must be moved back to the centre of the spreader before it
leaves the container. There must be a good clearance between the
Spreader and the container before slewing the crane boom.
23. When welding might be needed on the spreader with SCS2 assembled,
make sure that it is properly grounded or dismantle the plug connection
and earth cable.
the FLIPPER
ARMS move upwards to their starting position
essential
Bromma Group Manual
NOTE: Take care that flipper does not fall down and cause injury!
1
NOTE: Take care, incorrect rotation may result in serious damage!
2
TOWER FUNCTIONS AND TESTING
WARNING!
Use the tower only to level loads, or serious damage may occur!
Never use the hand crank on the motor with power connected, or serious
injury may occur!
3
red when locked green when
unlocked.
4
5
GUIDE ARMS (drg no 22606)
1.
2.
1002945
1002945 PWH 18.2.2005
- b / SC 23.1.2007
-
-
Item Quant Title Material / Article No. Dwg No. Art. No. Remarks
1 1 TWISTLOCK PIN 1000431 1000431
2 1 GUIDE BLOCK 1000430 1000430
3 1 SPHERICAL WASHER 41683 53968
4 1 TWISTLOCK ARM, ASSY. 43653 43653 TYPE 1
5 1 TWISTLOCK KEY 1000434 1000434
6 1 NUT 1000432 1000432 (M39x4-6H)
7 1 SCREW A4 1000600 M6S 8x75, Art. No. was 70165
8 2 SPACER RING 41731 54049
9 1 HYDRAULIC CYLINDER 74147 (CA 32/20-100/65)
10 1 BLOCKADING PIN 37704 37704 FZB
11 1 SPRING 70429 SF-TF 4.5x22x90 SS 1774-04
12 1 NUT LOCK-KING A4 77891 M12, Art. No was 75055
13 2 WASHER NORD-LOCK A4 701440 M12, Art. No. was 75295
14 2 LOCK PIN 74044 R.R 3.0
15 2 GREASE FITTING 71328 R 1/8"
16 6 SWITCH ATTACH. STD. 74970 (SENSOR D=30)
17 3 SCREW A4 1000596 M6S 8x50, Art. No. was 75226
18 1 SWITCH PAD h=10 1001482 1001482
19 4 SCREW A4 1000585 M6S 6x55, Art. No. was 75694
20 2 SCREW A4 1000587 M6S 6x65, Art. No. was 700686
21 1 BLOCKADING PIECE 43654 43654 FZB
22 4 NUT A4 76460 LOC-KING M8, Art. No. was 75090
23 6 WASHER A4 77798 BRB 8.4x16x1.6, Art. No. was 75328
24 3 BOLTING PLATE 48916 48916 FZB
25 6 WASHER NORD-LOCK A4 701433 M6, Art. No. was 75268
26 3 COVER PLATE DEP4 79850 FZB
27 1 SENSOR PLATE ASSY. LEFT 1002453 1002453 FZB
1002946
1002946 PWH 18.2.2005
- b / SC 23.1.2007
-
-
Item Quant Title Material / Article No. Dwg No. Art. No. Remarks
1 1 TWISTLOCK PIN 1000431 1000431
2 1 GUIDE BLOCK 1000430 1000430
3 1 SPHERICAL WASHER 41683 53968
4 1 TWISTLOCK ARM, ASSY. 43653 57059 TYPE 2
5 1 TWISTLOCK KEY 1000434 1000434
6 1 NUT 1000432 1000432 (M39x4-6H)
7 1 SCREW A4 1000600 M6S 8x75, Art. No. was 70165
8 2 SPACER RING 41731 54049
9 1 HYDRAULIC CYLINDER 74147 (CA 32/20-100/65)
10 1 BLOCKADING PIN 37704 37704 FZB
11 1 SPRING 70429 SF-TF 4.5x22x90 SS 1774-04
12 1 NUT LOCK-KING A4 77891 M12, Art. No was 75055
13 2 WASHER NORD-LOCK A4 701440 M12, Art. No. was 75295
14 2 LOCK PIN 74044 R.R 3.0
15 2 GREASE FITTING 71328 R 1/8"
16 6 SWITCH ATTACH. STD. 74970 (SENSOR D=30)
17 3 SCREW A4 1000596 M6S 8x50, Art. No. was 75226
18 1 SWITCH PAD h=10 1001482 1001482
19 4 SCREW A4 1000585 M6S 6x55, Art. No. was 75694
20 2 SCREW A4 1000587 M6S 6x65, Art. No. was 700686
21 1 BLOCKADING PIECE 43654 43654 FZB
22 4 NUT A4 76460 LOC-KING M8, Art. No. was 75090
23 6 WASHER A4 77798 BRB 8.4x16x1.6, Art. No. was 75328
24 3 BOLTING PLATE 48916 48916 FZB
25 6 WASHER NORD-LOCK A4 701433 M6, Art. No. was 75268
26 3 COVER PLATE DEP4 79850 FZB
27 1 SENSOR PLATE ASSY. RIGHT 1002454 1002454 FZB
RUNNING-IN OF A NEW SPREADER
Nut
EVERY 100 WORKING HOURS
Twistlock pin
If the work requires that the electrical supply remains connected then staff on
or in the vicinity of the spreader must be informed that it could move.
Nut
Spherical
washer
Twistlock
pin
NOTE. See the twistlock drawing and/or the separate adjustment instructions
for the adjustment of the twistlock end stop switches after reassembly.
2
If the spreader is equipped with twistlock counter
3
If there is no hour counter or twistlockcounter
4
If the spreader is equipped with twistlock counter
5
If there is no hour counter or twistlock counter
6
Only for floating twistlocks
NOTE. Every time the pump is emptied, new oil must be added until it starts
to run out of the drain hose.
Adjusting
nut
50
Cotter pin
Chain lock
4.
10.
1.
2.
2.
3.
1.
2.
3.
4.
6.
1.
NOTE. When replacing the flipper arm motor ensure that the outlet plug is
correctly positioned.
2.
a)
b)
c)
d)
e)
Sensors:
a) Sensor
b)
Sensor
plate
a)
b)
c) Landing
switch
d) Landing pin
Guide
neck
Twistlock
MOUNTING housing
Twistlock
head
Adjusting Key
1. Remove the M6 screw from the top of the twistlock.
2. To lower the twistlock, loosen the twistlock nut
slightly. To raise the twistlock, tighten the nut.
The distance between the top of twistlock head and the Twistlock pin
bottom of guide block 1 -2 mm
3. Recheck the float of the twistlock.
Twistlock
8 of 10 BROMMA CONQUIP AB
head
07 02 ENG
rev. x
Removing the Twistlock Cylinder
Split pin
Spacer
ring
Removing Sensors
Signal
cable
Sensor connection
Installing Sensors
Tower Crank
motor
Torque
wrench
331Nm
331Nm
End beam
68Nm 6.5 Nm
40Nm
331Nm
40Nm
331Nm
Twistlock Twistlock
EH5 / EH170 EH5U / EH170U
100 Nm
95 Nm
91Nm
56Nm
103Nm
after 200
test cycles
Bromma Group Manual
GENERAL ASSEMBLY
-
EH5U
Bromma Group Manual
THIS DRAWING IS COPYRIGHT AND IS THE PROPERTY OF BROMMA CONQUIP AB. THE DESIGN AN OR CONSTRUCTIONS CONTAINED THEREIN MAY NOT BE
COPIED OR REPRODUCED WITHOUT THE WRITTEN CONSENT OF THE OWNER.
F/N Qty Name Rev Type Title Title2
THIS DRAWING IS COPYRIGHT AND IS THE PROPERTY OF BROMMA CONQUIP AB. THE DESIGN AN OR CONSTRUCTIONS CONTAINED THEREIN MAY NOT BE
COPIED OR REPRODUCED WITHOUT THE WRITTEN CONSENT OF THE OWNER.
A-A
B (2:1)
1018967
F/N Qty Name Title Title2
Cabinet X100
BGS Accessories
8.15 LED signal lamps
Application
Bromma telescopic spreaders can be equipped with LED
signal lamps to inform the crane driver and other personnel if
the sprader has landed, (white or yellow), is unlocked (green)
or has locked (red) on a container. For twinlift spreaders a
fourth lamp is used to indicate twinboxes down (blue). For
mobile harbour crane spreaders the fourth lamp indicates
- Low power consumption tower in mid position (yellow).
Available models
LED Colors voltage Art. No. Rec. cable
Green, red, yellow 24 VDC 1001399
Technical specifications
Model 24VDC 110/230VAC
Dimensions
Light
aspects A (mm) B (mm)
1 160 130
2 305 275
3 450 420
4 595 565
Spare parts
SP-POS PART NO. DESCRIPTION QTY REMARKS
Warnings
CAUTION: LED light units are sources of bright light. Do
not stare directly into the beam from close distances and
observe all the warnings and guidelines in the instruction
manual. Bromma LED indicator panels are classified as
Class 2M LED devices according to the standard
IEC60825-1:1993+A1:1997+A2:2001.
LED-PANEL MOUNT. DET.
-
STS 45
All ordering of Bromma spare parts must be done by the Bromma e-commerce
website. To order the requested spare parts some important information must be
available.
The serial no. of the spreader. See Data Sheet chapt. 3or the dataplate mounted on
main frame of the current spreader.
The requested Art no. and the quantity needed. See Spare part list.
Registered User
To be able to log in at the Bromma e-commerce site you must be a registered user.
To become a registered user you have to fill in the Application Form on the Bromma
website. After a few days you will receive an User ID and a password by e-mail.
When you are a regitered user fill in your User ID and password at the fields on the
Bromma e-commerce website (www.bromma.com) to log in. Then follow the
instructions on the screen.
Search Function
If you do not find the parts requested on the e-commerce site or if you have any other
problems finding valid part numbers you can use the search function on the website
or call your local Bromma dealer. The phone number is published on the website
at www.bromma.com
BROMMA CONQUIP
Bromma Group Manual
-
5 6 7 8 9
10 11 12 13 14 15
16 17 18 19 20 21 22
23 24 25 26 27 28
29 30 31 32 33
34 35 36 37
22 30 23 31 24 32 2 PE
1 1
:L1 :L1 :L2 :L2 :L3 :L3 :PE :PE 1 3 5 1 3 5
2A 2 2
2 4 6 2 4 6
1 3 5
2 4 6
1 3 5 1 3 5 1 3 5 1 3 5
/7.01 2 4 6
7 8 9 21 :1 :2 :3 :PE
/6.01 / -Phase L1
/6.01 / -Phase L2
/6.01 / -Phase L3
7 8 9 21 1 2 3 PE
:7 :8 :9 :PE
1 2 3 PE
U U
3 3
2 2
PE -BRAKE2 PE -BRAKE1
4 5 -WXP2
PE
BLUE
/5.01 / -Phase L3
BROWN
/5.01 / -Phase L2
/5.01 / -Phase L1
/10.03 2 4 6
14 12 24 22
1 3 5 1 3 5
/7.07 /7.07
11 21
2 4 6 2 4 6
L
1 2 3 22 4 5 6 20 PE
1 2 3 22 4 5 6 20 PE
1 2 3 PE 1 2 3 PE
U U
PE PE
Cabinet heater
25 1 3
13
/5.01 14
1 3
:N
10A 2 4
:N -N.VAC / /13.00
21 :L -L.VAC / /12.00
22
:L
PE
BN YL/GL BU
A1
A2 A2
A1
RD RD BK BK
-24VDC SCS² / /15.00
-24VDC / /9.00
-0VDC / /10.00
11
.01 12
:2 7 8
.01
:1
:3 :- :- :- :- :- :- :-
1 2 3 4 5 6 7 8 9 10
14
11
1 2 12
24
3 4 21
22
5 6
7 8
SIGN.
:7
blue -GND X13 / /25.09
:14
white -Can high X13 / /24.09
:
:
:21
brown -Can low X13 / /24.09
:28
/7.06 / -XP21:6
6
/7.06 / -XP21:7
7
/7.06 / -XP21:8
8
/7.06 / -XP21:9
9
/7.06 / -XP21:10
10
/7.04 / -XP21:1
1
/7.04 / -XP21:2
2
-0VDC / +X1/9.00
/7.05 / -XP21:3
3
/7.05 / -XP21:4
4
/7.05 / -XP21:5
5
COMMON GROUP 1 COMMON GROUP 2
O O O O O O O O
PIN NO: 21
PIN NO: 44
:44 :31 :41 :43 :42 :21 :3 :2 :11 :1
13 14 15 16 17 18 19
13 14 15 16 17 18 19
+X1/8.08 / -0VDC
1 2 3 4 5
1 2 3 4 5
1 1 1 1 1 1 1 1
2 2 2 2 2 2 2 2
O O O O O O O O
PIN NO: 21
PIN NO: 44
:8 :26 :16 :6 :7 :35 :4 :5 :25 :15
A1 A1 A1 A1 A1
A2 A2 A2 A2 A2
1 2 1 2 1 2 1 2 1 2
3 4 3 4 3 4 3 4 3 4
5 6 5 6 5 6 5 6 5 6
O O O O O O O O
PIN NO: 9
PIN NO: 50
:9 :10 :20 :30 :40 :50 :46 :47 :49 :48
O O O O O O O O
PIN NO: 43
PIN NO: 11
:11 :21 :31 :41 :42 :43 :24 :35 :44 :45
/7.08 / -L.VAC
7 8 35 20 21 34 36
7 8 35 20 21 34 36
19 18 13 9 10 12 11
O O O O O O O O
PIN NO: 1
PIN NO: 15
14 15 16 17
/11.09 / -24VDC
/13.08 / -N.VAC
:36 :49 :48 :47 :46 :8 :7 :10 :9 :40 :50 :30 :20
O O O O O O O O
PIN NO: 8
PIN NO: 36
PIN NO: 10
PIN NO: 40
PIN NO: 20
COMMON GROUP 11
2 3
white brown
/14.09 / -0VDC
WH
WH;BN
BN;GN
GN
RED
BLUE
BLACK
GREEN
6 16 26 36
:42 :43 :44 :45 :10 :9 :19 :29 :39 :49 :30 :40 :50 :20 :48 :6 :16 :26 :36
SD
SC
ID0
ID1
ID3
ID4
ID5
VCC
GND
GND
GND
GND
+24V
+24V
B-Can L
B-Can H
Can-GND
Can-open L
Can-open H
4 4 4 4 4 4
-Can high X2 / +X1/8.01
-Can low X2 / +X1/8.01
4 2 4 4
4 2 4 2 4 2 4 2 :1 :2
/17.00
O O O O O O O O
CAN_high
CAN_low
4 2 4 2 4 2 4 2 :3 :5
1 1 1 1 1 1 1 1
2 2 2 2 2 2 2 2
+X1/8.01 / -GND X2
+X1/8.00 / -+VBB X2
4 4 4 4 4 4
-Can high X3 / +X1/8.02
-Can low X3 / +X1/8.02
4 2 4 4
4 2 4 2 4 2 4 2 :1 :2
/19.00
O O O O O O O O
CAN_high
CAN_low
4 2 4 2 4 2 4 2 :3 :5
1 1 1 1 1 1 1 1
2 2 2 2 2 2 2 2
+X1/8.02 / -GND X3
+X1/8.01 / -+VBB X3
4 4 4 4 4 4 4 4
-Can high X8 / +X1/8.05
-Can low X8 / +X1/8.05
4 2 4 2 4 2 4 2
4 2 4 2 4 2 4 2 :1 :2
/21.00
O O O O O O O O
CAN_high
CAN_low
4 2 4 2 4 2 4 2 :3 :5
+X1/8.05 / -GND X8
+X1/8.04 / -+VBB X8
4 4
-Can high X10 / +X1/8.06
-Can low X10 / +X1/8.06
4 4
4 2 4 2 4 2 4 2 :1 :2
/23.00
O O O O O O O O
CAN_high
CAN_low
4 2 4 2 4 2 4 2 :3 :5
+X1/8.06 / -GND X10
+X1/8.05 / -+VBB X10
4 4 4 4 4 4 4
-Can high X13 / +X1/8.07
-Can low X13 / +X1/8.07
4 2 4 2 4 4 2
4 2 4 2 4 2 4 2 :1 :2
/25.00
O O O O O O O O
CAN_high
CAN_low
4 2 4 2 4 2 4 2 :3 :5
+X1/8.06 / -VBB X13
30x90x115mm
-K6
-QM6 -QM7 -K8 -QM8 -K2 -P2
-QM1
-F1 2A /5.09
/7.02 /7.01
/7.07
30x90x380mm
10A
-F2
-KA1
-K1
X2
8 9
XP21
XP22
XP23
CABINET
X100
1 4
X0 -BRAKE2 =A1+X1/5.04 79125 CURRENT RELAY SR15 SEW SEW SR15 8267626 BSR 150-500VAC M25
X0 -CABINET_X100 =A1+X1/6.04 1018972 CABINET X100 CANopen Bromma 1018972 1018972 Mobile Spreader 10 fuse
X0 -CABINET_X100 =A1+X1/6.04 700563 GLAND PLUG M16 MILTRONIC MILTRONIC SKINDICHT-BL-M16 12 12 31 M16
X0 -HINK_X0 =A1+X1/6.03 1002490 X1 cabinet EH5 ASSY BROMMA 1002490 Complete with SCS² for CAN open
X0 -HINK_X0 =A1+X1/6.03 1002607 CABLE AND ITEM MARKING FLEXIMARK MILTRONIC TOWER JIB
X0 -HINK_X0 =A1+X1/6.03 1002595 CABLE AND ITEM MARKING FLEXIMARK MILTRONIC END BEAM 3-FLIPPER
X0 -HINK_X0 =A1+X1/6.03 1002018 PROTECTION COVER HTS ABB ABB 5DLN296350-A 5DLN296350-A SIZE4
X0 -R2 =A1+X0/16.09 1002390 RESISTOR 120ohm 0,25W Elfa Elfa 60-103-83 60-103-83
X0 -R3 =A1+X0/18.09 1002390 RESISTOR 120ohm 0,25W Elfa Elfa 60-103-83 60-103-83
X0 -S1 =A1+X0/16.01 1002367 PROXIMITY SWITCH M30 F IFM IFM II5910 IIA3015BBPKG/US M30 SN:15 10-36VDC M12 3WIRE
X0 -S2 =A1+X0/16.03 1002367 PROXIMITY SWITCH M30 F IFM IFM II5910 IIA3015BBPKG/US M30 SN:15 10-36VDC M12 3WIRE
X0 -S3 =A1+X0/18.01 1002367 PROXIMITY SWITCH M30 F IFM IFM II5910 IIA3015BBPKG/US M30 SN:15 10-36VDC M12 3WIRE
X0 -S4 =A1+X0/18.03 1002367 PROXIMITY SWITCH M30 F IFM IFM II5910 IIA3015BBPKG/US M30 SN:15 10-36VDC M12 3WIRE
X0 -S5 =A1+X0/16.02 1002367 PROXIMITY SWITCH M30 F IFM IFM II5910 IIA3015BBPKG/US M30 SN:15 10-36VDC M12 3WIRE
X0 -S6 =A1+X0/16.04 1002367 PROXIMITY SWITCH M30 F IFM IFM II5910 IIA3015BBPKG/US M30 SN:15 10-36VDC M12 3WIRE
X0 -S7 =A1+X0/18.02 1002367 PROXIMITY SWITCH M30 F IFM IFM II5910 IIA3015BBPKG/US M30 SN:15 10-36VDC M12 3WIRE
X0 -S8 =A1+X0/18.04 1002367 PROXIMITY SWITCH M30 F IFM IFM II5910 IIA3015BBPKG/US M30 SN:15 10-36VDC M12 3WIRE
X0 -S9 =A1+X0/16.05 1002367 PROXIMITY SWITCH M30 F IFM IFM II5910 IIA3015BBPKG/US M30 SN:15 10-36VDC M12 3WIRE
X0 -S10 =A1+X0/16.07 1002367 PROXIMITY SWITCH M30 F IFM IFM II5910 IIA3015BBPKG/US M30 SN:15 10-36VDC M12 3WIRE
X0 -S11 =A1+X0/18.05 1002367 PROXIMITY SWITCH M30 F IFM IFM II5910 IIA3015BBPKG/US M30 SN:15 10-36VDC M12 3WIRE
X0 -S12 =A1+X0/18.07 1002367 PROXIMITY SWITCH M30 F IFM IFM II5910 IIA3015BBPKG/US M30 SN:15 10-36VDC M12 3WIRE
X0 -S13 =A1+X0/20.05 1002367 PROXIMITY SWITCH M30 F IFM IFM II5910 IIA3015BBPKG/US M30 SN:15 10-36VDC M12 3WIRE
X0 -S14 =A1+X0/20.07 1002367 PROXIMITY SWITCH M30 F IFM IFM II5910 IIA3015BBPKG/US M30 SN:15 10-36VDC M12 3WIRE
X0 -S16 =A1+X0/20.06 1002367 PROXIMITY SWITCH M30 F IFM IFM II5910 IIA3015BBPKG/US M30 SN:15 10-36VDC M12 3WIRE
X0 -S52 =A1+X0/20.03 1002367 PROXIMITY SWITCH M30 F IFM IFM II5910 IIA3015BBPKG/US M30 SN:15 10-36VDC M12 3WIRE
X0 -S53 =A1+X0/20.04 1002367 PROXIMITY SWITCH M30 F IFM IFM II5910 IIA3015BBPKG/US M30 SN:15 10-36VDC M12 3WIRE
X0 -S54 =A1+X0/20.01 1002367 PROXIMITY SWITCH M30 F IFM IFM II5910 IIA3015BBPKG/US M30 SN:15 10-36VDC M12 3WIRE
X0 -S55 =A1+X0/20.02 1002367 PROXIMITY SWITCH M30 F IFM IFM II5910 IIA3015BBPKG/US M30 SN:15 10-36VDC M12 3WIRE
X0 -S114 =A1+X0/20.08 1002367 PROXIMITY SWITCH M30 F IFM IFM II5910 IIA3015BBPKG/US M30 SN:15 10-36VDC M12 3WIRE
X0 -X2 =A1+X0/16.00 1001762 IFM MODULE CAN-OPEN IFM-Electronic IFM-Electronic CR9011 CR9011 8 in / 8 out
X0 -X3 =A1+X0/18.00 1001762 IFM MODULE CAN-OPEN IFM-Electronic IFM-Electronic CR9011 CR9011 8 in / 8 out
X0 -X8 =A1+X0/20.00 79282 GLAND PLUG MURR MILTRONIC AB ZVKM12 40 57 05 ASB BOX PLUGS M12
X0 -X8 =A1+X0/20.00 1001762 IFM MODULE CAN-OPEN IFM-Electronic IFM-Electronic CR9011 CR9011 8 in / 8 out
X0 -XP1 74410 INSERT 37P (M) ODU ODU GUNNAR PETTERSON AB 309 803 150 037 151 309 803 150 037 151 ODU 309 37 POL MALE
X0 -XP1 73523 PLUG ODU 309 ODU GUNNAR PETTERSON AB 309.020.000.554.000 309.020.000.554.000 ODU 309 BAJONETT BRONCE PG42
X0 -XP2 76576 SOCKET HNA TYPE 215 KARL DOSE KARL DOSE GmbH INSATS 162 MED HYLSA LÅNG 3121501
1 1
1 3 5 1 3 5
2A 2 2
2 4 6 2 4 6
1 3 5
2 4 6
1 3 5
/5.01 1 3 5 1 3 5 1 3 5 1 3 5
2 4 6
/7.04 2 4 6 /7.05 2 4 6 /7.01 2 4 6 /7.02 2 4 6
PE 20 21 22 7 8 9 :1 :2 :3
/4.00 / -Phase L1
/4.00 / -Phase L2
/4.00 / -Phase L3
This drawing is copyright, and is
the property of BROMMA CONQUIP AB.
The design an or constructions
contained therein, may not be copied
or reproduced, whitout the written :
consent of the owner.
:
SUBJECT OF CHANGE SIGN. DATE
:101 :103 :102 :104
/3.01 / -Phase L3
/3.01 / -Phase L2
/3.01 / -Phase L1
14 12 24 22
/5.07 /5.07
11 21
1 3 5
/7.03 2 4 6
1 3 5 1 3 5
N
2 4 6 2 4 6
1 2 3 4 5 6
13
/3.01 14
1 3
:N
10A 2 4
:N -N.VAC / /10.00
21 :L -L.VAC / /9.00
22
:L
PE
BN YL/GL BU
A1
A2 A2
A1
RD RD BK BK
-24VDC SCS² / /12.00
-24VDC / /6.00
-0VDC / /7.00
11
.01 12
:2 7 8
.01
:1
:3 :- :- :- :- :- :- :-
1 2 3 4 5 6 7 8 9 10
14
11
1 2 12
24
3 4 21
22
5 6
7 8
O O O O O O O O
PIN NO: 21
PIN NO: 44
:44 :31 :41 :43 :42 :21 :3 :2 :11 :1
13 14 15 16 17 18 19
O O O O O O O O
PIN NO: 21
PIN NO: 44
:8 :26 :16 :6 :7 :35 :4 :5 :25 :15
A1 A1 A1 A1 A1
A2 A2 A2 A2 A2
/5.08 / -0VDC
-0VDC / /8.00
1 2 1 2 1 2 1 2 1 2
3 4 3 4 3 4 3 4 3 4
5 6 5 6 5 6 5 6 5 6
O O O O O O O O
PIN NO: 9
PIN NO: 50
:9 :10 :20 :30 :40 :50 :46 :47 :49 :48
O O O O O O O O
PIN NO: 43
PIN NO: 11
:11 :21 :31 :41 :42 :43 :24 :35 :44 :45
/5.08 / -L.VAC
O O O O O O O O
PIN NO: 1
PIN NO: 15
/8.09 / -24VDC
/10.08 / -N.VAC
:36 :49 :48 :47 :46 :8 :7 :10 :9 :40 :50 :30 :20
O O O O O O O O
PIN NO: 8
PIN NO: 36
PIN NO: 10
PIN NO: 40
PIN NO: 20
COMMON GROUP 11
2 3
white brown
/11.09 / -0VDC
WH
WH;BN
BN;GN
GN
RED
BLUE
BLACK
GREEN
6 16 26 36
:42 :43 :44 :45 :10 :9 :19 :29 :39 :49 :30 :40 :50 :20 :48 :6 :16 :26 :36
SD
SC
ID0
ID1
ID3
ID4
ID5
VCC
GND
GND
GND
GND
+24V
+24V
B-Can L
B-Can H
Can-GND
Can-open L
Can-open H
30x90x115mm
-K6
-QM6 -QM7 -K8 -QM8 -K2 -P2
-QM1
-F1 2A /3.09
/5.02 /5.01
/5.07
30x90x380mm
10A
-F2
-KA1
-K1
X2
L
N
1-3
105-106
2-3
+
Blue
X1 X2
Contact No.1
Contact No.1
Guide Pin
Guide Pin
X1 -B1 =A1+X1/9.00 700086 SCS² PLUG K2 AD-CONTACT AD-CONTAKT AB DRC 26-50-S08 DRC 26-50-S08
X1 -B1 =A1+X1/9.00 700087 SCS² PLUG K3 AD-CONTACT AD-CONTAKT AB DRC 26-50-S09 DRC 26-50-S09
X1 -B1 =A1+X1/9.00 38905 IDENTIFICATION KEY FOR SCS² CC-SYSTEM CC-SYSTEM SEE DRAWING 38905
X1 -B1 =A1+X1/9.00 1002003 SCS² CONNECTOR COVER BMAL BMAL 1002003 Rubber boot for deutsch connectors
X1 -B1 80 =A1+X1/9.00 700079 SCS² SOCKET PIN AD-CONTACT AD-CONTAKT AB 0462-201-2031 AU 0462-201-2031 AU
X1 -B1 =A1+X1/9.00 700085 SCS² PLUG K1 AD-CONTACT AD-CONTAKT AB DRC 26-50-S07 DRC 26-50-S07
X1 -B1 =A1+X1/9.00 78601 INPUT MODULE DC OPTO22 ELECTRONA-SIEVERT AB G4IDC5 G4 IDC 5 24 VDC
X1 -B1 =A1+X1/9.00 700498 SCS I/O MARKING BROMMA BROMMA 700498 See document
X1 -B1 =A1+X1/9.00 39952 Attachment for SCS² in cabinet NPP/ Bromma 39952 39952 EH5-170-U
X1 -B1 =A1+X1/9.00 700020 SCS² SOFTWARE LICENS ENEA ENEA OSE SYSTEMS AB
X1 -B1 =A1+X1/9.00 1001750 OUTPUT MODULE 0-240VAC DELCON/AXIOM OEM-AUTOMATIC G4/SLO5TR G4/SLO5TR Sek:0-240VAC 3A
X1 -B1 80 =A1+X1/9.00 700080 SCS² DUMMY PIN AD-CONTACT AD-CONTAKT AB 0413-204-2005 0413-204-2005
X1 -B1 13 =A1+X1/9.00 78603 OUTPUT MODULE DC OPTO22 ELECTRONA-SIEVERT AB G40DC5 G4 ODC 5 24VDC 4A
X1 -EH1 =A1+X1/4.07 1001690 HEATER CABINET STEGO OEM AUTOMATIC HG140 14001.0-01 30W 110-250V AC/DC
X1 -F1 =A1+X1/3.09 1001828 MCB 1-POL 2A SIEMENS SIEMENS 5SY6 102-7 C-CHARACTER
X1 -F2 =A1+X1/5.02 1001829 MCB 2-POL 10A SIEMENS SIEMENS 5SY6 210-7 C-CHARACTER
X1 -G1 =A1+X1/5.02 1001859 POWER SUPPLY 90-255VAC/ 24VDC PrimePower OEM-Automatic 0036515 0036515 30A / 0-400HZ
X1 -K1 =A1+X1/5.01 1001826 CONTACTOR SIEMENS SIEMENS 3RT13 25-1BB40 3RT13 25-1BB40 24VDC 22kW 4-pol SIZE 0
X1 -K2 =A1+X1/7.01 1001827 PHASEREVERSER SIEMENS SIEMENS 3RA13 25-8XB30-1BB4 3RA13 25-8XB30-1BB4 24VDC 7,5kW 17A
X1 -K6 =A1+X1/7.03 1000763 CONTACTOR SIEMENS SIEMENS 3RT1025-1BB40 32 667 91 24VDC 7.5KW 17A
X1 -K8 =A1+X1/7.04 1001827 PHASEREVERSER SIEMENS SIEMENS 3RA13 25-8XB30-1BB4 3RA13 25-8XB30-1BB4 24VDC 7,5kW 17A
X1 -KA1 =A1+X1/5.07 78980 RELAY SOCKET 2-SWITCHING RELECO OEM-AUTOMATIC AB 40 165 54 S7M
X1 -KA1 =A1+X1/5.07 78986 AUXILIARY CONTACTOR RELECO OEM C7 A20 D24D C7 A20 D24D 24VDC 2-SWITCHING
X1 -KEY1 =A1+X1/12.03 38905 IDENTIFICATION KEY FOR SCS² CC-SYSTEM CC-SYSTEM SEE DRAWING 38905
X1 -P1 =A1+X1/3.09 70873 TIMECOUNTER 380 VAC BAUSER METRIC AB 632A.2 380VAC 24-0015-78
X1 -P2 =A1+X1/8.05 76140 PULSECOUNTER 190.07 24V DC BAUSER METRIC AB 632 A.2 24VDC 24-2032-25DC
X1 -Q1 =A1+X1/3.01 700869 LOCK HANDLE GREY 66X66mm BACO OEM 0174601 0174601
X1 -Q1 =A1+X1/3.01 700871 AUXILIARY BLOCK BACO OEM-AUTOMATIC AB 0172179 172179 NO+NC 400V 10A SIGNALCONTACT
X1 -Q1 =A1+X1/3.01 700868 MAIN CIRCUIT BREAKER BACO OEM 0172200 0172200 50A
X1 -QM1 =A1+X1/3.07 78993 THERMAL-MAGNETIC CIRCUIT BREAK SIEMENS SIEMENS 3RV10 21 - 4BA10 3RV1021-4BA10 7.5KW 14-20A
X1 -QM6 =A1+X1/4.01 79042 THERMAL-MAGNETIC CIRCUIT BREAK SIEMENS SIEMENS 3RV10 11-1GA10 3RV1011-1GA10 2.2kW 4.5-6.3 A
X1 -QM7 =A1+X1/4.03 79042 THERMAL-MAGNETIC CIRCUIT BREAK SIEMENS SIEMENS 3RV10 11-1GA10 3RV1011-1GA10 2.2kW 4.5-6.3 A
X1 -QM8 =A1+X1/3.04 79043 THERMAL-MAGNETIC CIRCUIT BREAK SIEMENS SIEMENS 3RV10 11-1HA10 3RV1011-1HA10 3,0kW 5,5-8A
X1 -SB1 =A1+X1/11.08 1019811 AUXILIARY BLOCK BACO OEM-AUTOMATIC AB 230 E10 230E 10 switch body with 1NO block
X1 -SB1 =A1+X1/11.08 1019832 SWITCH HEAD BACO OEM L21KA03 L21KA03 Only operating head 2 pos, 45º
X1 -SB1 =A1+X1/11.08 1019818 FRAME BACO OEM LWG3 (Suitable with LIB5 - 1019819)
X1 -SS1 =A1+X1/5.01 1019809 AUXILIARY BLOCK BACO OEM-AUTOMATIC AB 333E 02 333E 02 switch boddy with 2NC block
X1 -SS1 =A1+X1/5.01 1019818 FRAME BACO OEM LWG3 (Suitable with LIB5 - 1019819)
X1 -SS1 =A1+X1/5.01 1019810 PUSH BUTTON BLACK BACO OEM-AUTOMATIC AB L22 EC03 L22 EC03 FOR SPREADER STOP Ø29mm
X1 -SS1 =A1+X1/5.01 1019819 WHITE SIGNPLATE (+GRAVERING) BACO OEM-IDEALGRAVYR AB LIB5 GRAVERING ENL BILAGA (Suitable with LWG3 - 1019818)
X1 -XP21 700858 INSERT FEMALE 10POLE HTS TYCO ELECTRONICS HE.10.BU.C 2-1103637-3 CRIMP
X1 -XP21 700854 SURFACE MOUNTED HOUSING HTS TYCO ELECTRONICS HIP-K.10/24.AG 2-1102647-5 SCREW LOCK
X1 -XP21 10 700862 CRIMP CONTACT FEMALE HTS TYCO ELECTRONICS 4-1105101-1 2,5mm2 AWG14
X1 -XP21 1002018 PROTCTION COVER ABB ABB 5DLN296350-A 5DLN296350-A HTS SIZE4
X1 -XP22 1001921 SURFACE MOUNTED HOUSING HTS TYCO ELECTRONICS HIP.3/4.AG 1-1102603-5 SCREW LOCK
X1 -XP22 1001926 CRIMP CONTACT FEMALE HTS TYCO ELECTRONICS 1-1105051-1 0,14-0,37mm²
X1 -XP22 1001923 INSERT FEMALE 7+POLE HTS TYCO ELECTRONICS HN.D.7.Bu.C 2-1103103-3 CRIMP
X1 -XP22 1002520 PROTECTION COVER HTS ABB ABB 5DLN296350-C 5DLN296350-C SIZE1
X1 -XP23 700854 SURFACE MOUNTED HOUSING HTS TYCO ELECTRONICS HIP-K.10/24.AG 2-1102647-5 SCREW LOCK
X1 -XP23 1002018 PROTCTION COVER ABB ABB 5DLN296350-A 5DLN296350-A HTS SIZE4
X1 -XP23 700856 INSERT FEMALE 42POLE HTS TYCO ELECTRONICS HN.2D.42.BU.C 2-1103206-3 CRIMP
X1 -XP23 24 1001927 CRIMP CONTACT FEMALE HTS TYCO ELECTRONICS 4-1105051-1 1,5mm²
X1 :1 =A1+X1/5.02 79367 FUSE ATTACHMENT WAGO HELLERMANN TYTON AB 282-696 282-696 Blade fuse terminal
X1 :1 =A1+X1/5.02 79371 FUSE 30A LITTELFUSE ELFA AB 33-051-82 Blade fuse 30A
General ............................................................................................................................ 4
The X2 connector............................................................................................................ 5
Node ID....................................................................................................................... 5
Main Supply................................................................................................................ 6
CAN ............................................................................................................................ 6
The X1 and X3 connectors (I/O-connectors).................................................................. 7
I/O Groups .................................................................................................................. 7
Common junction........................................................................................................ 8
Internal jumper bars .................................................................................................... 8
Connecting a switch.................................................................................................... 9
Connecting a valve...................................................................................................... 9
I/O Modules .............................................................................................................. 10
General .......................................................................................................................... 15
Connecting the B1 node............................................................................................ 15
Connecting the A1 node............................................................................................ 16
The Anybus card (in this case for Profibus) ............................................................. 16
ABE............................................................................................................................... 18
General .......................................................................................................................... 20
BCAN - Status LEDs ................................................................................................ 21
Power connector........................................................................................................ 21
BCAN connector....................................................................................................... 21
Node address key switches ....................................................................................... 21
Serial port connector ................................................................................................. 21
2 REV 3
Teach......................................................................................................................... 23
General ...................................................................................................................... 24
Hardware................................................................................................................... 24
Software .................................................................................................................... 25
Activate the EE-prom ............................................................................................... 26
3 REV 3
Node Hardware
Below is a picture of a SCS2 node.
General
Here follows an example of how to build up a Can bus system with two nodes one with
one input and the other with one output.
4 REV 3
The X2 connector
The three connectors X1,X2&X3 have different connection keys to avoid the possibility
of connecting them in the wrong place. It is important to choose the correct one.This is
easy to check, on the connecting side of the connector just below the mounting screw
there is a number 7, 8 or 9.
connection
The X2 key
should be
marked “8”
Node ID
All nodes in a system must have a unique identity. This is read from the Id pins
9,19,29,39,49 on the X2 connector, where pins being connected to the ground pin (10)
correspond to and pins left unconnected are correspond to . A master
node (B1) has pins 10,9,19,29,49 connected together. (Commonly used as a spreader
Node)
A slave node on the crane A1 has pins 10,19,29,39,49 connected together.
Start with making “ID” jumpers.
5 REV 3
Main Supply
24Volt AC or DC powers the node internally. The signals are doubled in the connector
due to the current limit of single pins. DC voltage can be applied in either direction. The
potential is measured between the A section and the B section.
CAN
The CAN net connection is placed in the X2 connector.
All nodes in the system have to be connected equal (bus topology) to CAN High and
CAN Low to be able to establish communication.
Here is a schematic with the X2 connectors of two nodes, one A1 and one B1 with node id,
CAN bus and power supply connected.
+
24V Supply
-
Low
C AN Bus High
ID
9 10 19 29 30 40 42 43 44 45 49 10 19 29 30 39 40 42 43 44 45 49
Pin no.
CAN-bus
24V SUPPLY
6 REV 3
The X1 and X3 connectors (I/O-connectors)
Just like the X2 connector the X1 and X3 connectors are keyed to avoid connecting them
in the wrong place. The X1 can be identified by the number “7” on the front of the
connector, and the X3 connector by the number “9”.
connection
key
I/O Groups
There are 48 digital I/O on a node. Each I/O can be configured as either an input or an
output via the software. The I/O 1 to 44 are joined in groups of 4 resulting in 11 groups.
I/O 45 to 48 are single I/O’s. Each group has a “Common” junction. This makes it
possible to have different voltages in each group.
7 REV 3
Common junction
This point is to be connected to live or neutral depending on if the group is used for
inputs or outputs, Inputs need neutral and outputs need live as showed below. Inputs can
be viewed upon as relay coils and outputs as switching contacts.
L/24V D C
N / 0V D C
SCS SCS
9 10 11 12 9 10
S C S 11 12
8 26 16 6 7 8 26 16 6 7
In the picture is one I/O group used as inputs on the left, and on the right the same group
is used as outputs.
8 REV 3
Connecting a switch
Here is one example of how to use the internal jumpers while connecting the switch into A1.
One of the jumper groups is fed with live and supplies the switch, the other jumper group is
connected to neutral and supplies the I/O group.
L/24V Supply
N/0V Supply
6 7 8 12 13 1 4 16 17 18 19 22 23 24 26 27
11 12
10 9
Connecting a valve
Here is one example of how to use the internal jumpers while connecting the valve into B1.
One of the jumper groups is connected to Neutral and supplies the valves secondary side, the
other jumper group is connected to live and supplies the I/O group.
L/24V Supply
N/0V Supply
6 7 8 12 13 1 4 16 17 18 19 22 23 24 26 27
11 12 10 9
9 REV 3
I/O Modules
To be able to adapt the I/Os to the system voltage each I/O channel have a solid-state
interface relay (OPTO 22). This makes it possible to choose input or output and a voltage
range of 12-230 VAC/DC. Each module has a led indicating active state. On the output
modules there is a 3 Amp fuse. These modules are located inside the SCS² cover. The
cover has a lens for each channel, so the I/O status can be seen from the outside.
LED
FUSE
System properties
Menu tabs
10 REV 3
Pin configuration
Next menu tab is “pin configuration”, all present nodes are visible as tabs in this view. (1)
Make sure tab A1 is activated in the view. Give Port id# 9 the following name ”switch”.
(2) Comment field is optional. (3)
Activate tab B1 in the view (1) and do the same for Port id# 9 with following name
”VALVE”. (2)
The red color of the fields indicates that the ports are not yet connected or that any
of the letters are unaccepted. Space between words is not accepted instead use “_”.
A red field makes it impossible to compile the application.
Component view
Next menu tab is the “component view”
The component view is where components are deployed and connected. A palette
displaying all components is available in the view.
The palette can be made visible
by pressing “components” if it is
not already visible.
Available
component
pallet
11 REV 3
Select the OD timer (On Delay timer) component from the available component pallet
(1). It’s located in the Digital tab (2).
Place the component on Page 1 in the view with the left mouse button. Then press the
right button to get the arrow back.
Do the same thing on the right red dot and choose the output in this case “VALVE”
12 REV 3
Put the arrow on the component and right click, and select “properties”.
Put the delay time to two seconds (in mille seconds). The instance name is an internal
component address and should not be changed. When ready press “OK”.
Instance name
Delay time
13 REV 3
Load view
The last view is the “Load view”. From this view it is possible to download and up load
applications to and from a connected SCS² system. Press the “Download” button and a
dialogue box will appear, choose the desired “spr” file and press the “Open” button.
Download
Choose file
and press
open
Then the system distributes the file over the CAN-bus to the rest of the nodes (if
necessary).
When the download is ready
this dialogue box appears.
Current transfer
completed (%)
Total transfer
completed (%)
14 REV 3
General
Here follows an example of how to build up the same system as before with two nodes,
but the B1 node has one output and one input and on the A1 node is the input replaced
with an Anybus
interface
L/2 4VD C
N/ 0V DC
SC S² SC S²
1 2 3 4 9 10
SC S 11 12
44 31 41 43 42 8 26 16 6 7
15 REV 3
Connecting the A1 node
Connect power supply, can bus and an ID jumper as A1 in the X2 connector.
An “Anybus card” is also to be mounted and connected inside the hood where the digital
I/Os are located.
There is a D-sub connector on the card for connecting to outside net (1), and a selector
for termination resistance (2) and two selectors used for setting hard ware identification
of the unit in the outside net (3).
Item 3. HW address
1 2 3
*10 *1
The four LEDs are used for showing the state of the communication from the
Anybus-card and the outside net.
not used
(green) on-line on the Fieldbus
(red) off-line on the Fieldbus
(red) indicate faults on the Fieldbus side as follows:
Error in configuration: IN and/or OUT length set during initialization
of the module is not equal to the length set during configuration of the network.
Error in user parameter data: the length/contents of the user parameter
data set during initialization of the module is not equal to the length/contents set
during configuration of the network.
Error in initialisation of the Profibus communication ASIC.
16 REV 3
The Anybus card
is to be mounted
inside the hood on
the right upper
corner of the node
17 REV 3
ABE
Open the application used in the digital chapter. Get in to the ”pin configuration” view
and remove the switch from A1, add a new “switch” to B1 in Port id# 1
Then get in to the “component view” and set the cursor on the OD timers input connector
(on the left) and press Disconnect, the connection point turns red if a connection is
acquired for the component to function.
Connect the switch to the “split”, the “input bit” and the “split” to the “or” and the “or” to
the “OD timer”. Yore connection should now be as below.
18 REV 3
Right click on in/output bits and choose properties. In the properties menu it is possible to
configure following.
“ ” is a free text field. Use this field for notes about the Anybus port.
“ ” is the bit number of the chosen byte in Anybus interface. (0-7)
“ ” is the start byte in the Anybus interface. (0-63)
“ ” is where the any bus card is located (in this case A1)
The size of the data areas is decided of the highest byte in the application, in both
directions separately. The two sizes have to be equal on both sides of the Anybus card
(outside master/any bus) to be able to establish contact. If the outside areas is bigger than
in the application is it possible to put an empty byte to make the areas match.
19 REV 3
General
Compared to a conventional SCS² node the Anybus gateway does not have any digital or
analogue I/O’s, no internal battery backing up the event log (locally
The anybus gateway is used in cases where a physical I/O is not needed; one example is
when the SCS² system is connected as a slave unit (via a anybus card in the crane node)
on the crane PLC.
Status LEDs
20 REV 3
BCAN - Status LEDs
There are three green LEDs for Power, BCAN and Anybus indicating operating status
and one red LED indicating error status.
is lit when power is applied and system starts to execute.
is lit when the BCAN communication interface is operating normally and
flashing when the communication interface is not working as intended.
is flashing when the Anybus interface is not configured and lit when
configured and operating normally. (Between the node and the anybus card)
is unlit when system is running normally and lit when an error has occurred.
Power connector
The power connector is a Phoenix Contact 2-
pin header (MC1,5/2-G-3,81).
VCC 10 to 28 V DC 1
24Volt DC powers the node internally.
GND Ground 2
BCAN connector
The BCAN connector is a Phoenix Contact 3-
pin header (MC1,5/3-G-3,81). All nodes in
the system have to be connected equal (bus CAN H CAN high 1
topology) to CAN High and CAN Low to be CAN L CAN low 2
able to establish communication.
21 REV 3
Absolute encoder on the telescope
General
The absolute encoder should be connected to the RS485 port. (Channel A at X2/38 and
channel B at X2/37) In the ABE component pallet under the “analogue” tab, the RS485
port component is located. It is also possible to rescale the information from the sensor to
be able to work or monitor the actual measurements (in for instance mm), the tool for this
is the “scale” component. The “scale” component is also located under the “analogue”
tab.
Teach is used Add the RS485 port component
for storing from the analogue tab
positions
The scale component
makes it possible to
translate the sensor
value to the
mechanical distance
it is possible to choose
between some different standardised
protocols to suit the sensor used.
When using the protocol some more information is needed. (See sensor/manufacture
for data)
determines how the sensor value (bit pattern) shall be read when converting
to a decimal value (made internally in the component). Gray or Binary.
how many steps (bits) per revolution.
how many revolutions that are supported by the sensor.
22 REV 3
From bits to millimetres (scale)
Retract the spreader to the mechanical end stop, measure the distance between the single
twistlocks, note the value down, read the sensor value with the ABE online and make a
note of this. Expand the spreader to the mechanical end stop and repeat the same
procedure.
It is very important that the sensor doesn’t wraparound (when counting up, after
the highest value it starts at zero again), the retracted value should be low and the
expanded value should be larger.
Then verify the scale, put the spreader in some different positions measure and compare
with the scaled value.
Teach
To be able to store positions the APS component is equipped with a storing function
called “TEACH”. By giving the teach command and expand or retract command it is
possible to move the spreader in a lesser speed (defied by the parameter “PWM value for
teach” in APS properties) to the required length, for position “20ft”, hold the teach
command and give the go to position “20ft” command. The value is now stored in the
spreader memory (NV RAM). Repeat this procedure on all the required positions.
The connection point for teach
23 REV 3
General
In the external EE-prom it is possible to store information as spreader ID, twistlock
counters, running time etc. this makes it possible to replace the node(s) in the system
without loosing this information.
Hardware
The EE-prom is to be connected in to the node as following.
The EE-prom is located in a gland. The gland should be mounted solid near by the SCS²
node within the cable range.
24 REV 3
Software
A “spreader properties” component needs to be added in the application, that make the
system try to find the “EE-prom” at boot.
The “spreader properties” component (1) is located in the “misc…” tab (2) in the
“available component” menu.
4
3
2 1
The “spreader properties” contains twistlock counters and a time counter etc. To make
the counters work some info is needed, connect the available signals corresponding to the
connection points on the left of the component (3).
The information is possible to send out as analogue words true the bus to the outside net
(if present), the connection points for these values is located on the right of the
component (4).
25 REV 3
Activate the EE-prom
The EE-prom is activated after the “Serial number” value is set.
The BMS have to be connected to the node that the EE-prom is connected to.
Left click on the “Serial number” key in the BMS “spreader info” tab.
In the “current key” dialogue box down in the left corner there should now be seen “serial
number”.
Put the spreader serial number in the value bar and press the “set” button to store and
activate the EE-prom. It now displays the different values.
The information from the EE-prom is possible to upload with the BMS from the
“spreader info” tag. Connect the BMS to the system and press the “get all” button.
26 REV 3
User Manual
Version 1.0
Table of contents
1 INTRODUCTION .............................................................................................................5
2 INSTALLING ABE...........................................................................................................5
2.1 HW requirements .................................................................................................................................................... 5
2.3 Disclaimer................................................................................................................................................................. 5
2(92) © 2000
Document: Project: Project No
7 LOAD VIEW...................................................................................................................16
8 COMPONENTS .............................................................................................................17
8.1 Controllers.............................................................................................................................................................. 17
8.1.1 TLC4 – Twistlock Controller 4 ....................................................................................................................... 17
8.1.2 TLC8 – Twistlock Controller 8 ....................................................................................................................... 20
8.1.3 FAC – Flipper Arm Controller ........................................................................................................................ 24
8.1.4 DPS – Discrete Positioning System................................................................................................................. 26
8.1.5 Tower – Head block ........................................................................................................................................ 29
8.1.6 APS – Automatic Positioning System ............................................................................................................. 32
8.1.7 MPS – Memory position system...................................................................................................................... 36
8.1.8 Twin Telescope................................................................................................................................................ 40
8.1.9 TwinUpDown .................................................................................................................................................. 42
8.1.10 PID................................................................................................................................................................... 46
8.1.11 AutoTuner........................................................................................................................................................ 50
3(92) © 2000
Document: Project: Project No
8.8 Analogue................................................................................................................................................................. 78
8.8.1 RS485 port....................................................................................................................................................... 78
8.8.2 IN0 > IN1 ........................................................................................................................................................ 78
8.8.3 IN0 * IN1......................................................................................................................................................... 79
8.8.4 IN0 / IN1.......................................................................................................................................................... 79
8.8.5 IN0 – IN1......................................................................................................................................................... 79
8.8.6 IN0 + IN1 ........................................................................................................................................................ 80
8.8.7 Scale ................................................................................................................................................................ 80
8.8.8 AnalogueLatch ................................................................................................................................................ 81
8.8.9 Filter ................................................................................................................................................................ 81
8.8.10 AuxAnalogue................................................................................................................................................... 82
9 TUTORIAL.....................................................................................................................83
4(92) © 2000
Document: Project: Project No
1 Introduction
ABE – Application Builder Environment has been developed to create and manage spreader programs specifically for the
Bromma Conquip SCS2 system used on Spreaders. This tool gives the programmer/user the possibility of configuring and
programming the logic of the SCS2 via a graphical interface.
In principal ABE generates a binary file describing the interconnection between the graphical objects the user has tied
together. This file, when downloaded onto the target system, connects the precompiled objects within the target system
together according to the functionality described by the user. Hence all logical objects, components, reside within the
target system and the program file generated by ABE determines their interconnection.
The objects, from no on referred to as components, within ABE contain a varying amount of logic ranging from basic
Boolean instruction sets to Spreader specific blocks of functionality which can be altered in behaviour via parameter
settings. The components containing specified Spreader functions are developed to ensure that years of Spreader
experience is re-used and also contain the interlocking for generating fault and event messages to the onboard NVRAM
(log).
This programming tool is intended for use by staff with adequate knowledge of both the system and the functionality of
the Spreader/Crane in which it shall be used only. Any alterations or new programs causing failure in functionality due to
logical faults in the program are the responsibility of the person/company carrying out this work.
2 Installing ABE
2.1 HW requirements
The minimum requirements to run this application on your PC are:
an Intel compatible PC running Windows 95 / 98 / NT 4.0 / 2000.
at least one serial communication port available (COM1 or COM2).
at least 2Mb of free disk space.
2.2 Installation
Close any other applications running under windows.
Insert the CD into your station.
Run the file Setup.exe.
Follow the instructions on the screen.
2.3 Disclaimer
Copyright Bromma Conquip AB. All rights reserved.
Products and company names mentioned herein may be trademarks or trade names of their respective owners.
Bromma Conquip AB operates on a policy of continuous improvement. Therefore we reserve the right to make changes
and improvements to any of the products described in this manual without prior notice.
Bromma Conquip AB is not responsible for any loss of data, income or any consequential damage howsoever caused.
5(92) © 2000
Document: Project: Project No
3 User interface
ABE-application is divided into four main functions.
This chapter describes the four main functions of the program.
Remark:
Allowed characters when giving names to Item identifiers, Comments, Components and Tags are:
[a, b, c..., z], [A, B, C..., Z], [0, 1, 2,..., 9] and “_” (underscore). No other characters must be used.
3.4.1 File
Two types of files are available.
Type *.spr is a compiled file ready to download onto the SCS2.
Type *.spi is an intermediate file. Use Save or Save As... if you are not able to generate downloadable program file but
want to continue your work later on. The file extension will then be *.spi.
3.4.1.1 New
Creates a new program file for editing.
3.4.1.2 Open
Opens a program file for editing/viewing.
3.4.1.4 Save
Saves the current project. The file extension will be *.spi.
3.4.1.5 Compile
Generates and prompts you to save a downloadable program file used in the SCS2. The file extension will be *.spr.
3.4.1.6 Print
Prints the Component view.
3.4.1.7 Exit
Exits the application.
6(92) © 2000
Document: Project: Project No
3.4.2 Edit
3.4.2.1 Cut
Selected components will be cut and saved to the clipboard.
3.4.2.2 Copy
Selected components will be copied to the clipboard.
3.4.2.3 Paste
Content of clipboard will be pasted into selected page in the Component view. If connections match existing ports theses
will also be pasted into the page.
3.4.2.4 Find
Finds a text string in component comments, component identifiers or an actual component.
3.4.3 Settings
3.4.4 Tools
7(92) © 2000
Document: Project: Project No
3.4.5 Help
3.4.5.1 About
Short information about ABE such as version, current number of components etc.
8(92) © 2000
Document: Project: Project No
4 System view
4.1 General
The system view provides a way of enabling and disabling (connecting/disconnecting) nodes and setting system
properties such as version number, author, comments and date of modification. The nodes are named A1-A4 for the nodes
intended to be fitted to the crane and B1-B8 for the nodes intended to be fitted to the Spreader. Each node name
corresponds to a unique address key setting.
The system view allows the user to set up the node configuration by checking the desired nodes. A fixed set of
checkboxes are available that represent the used nodes in the system. The enabled nodes then have to be present in that
system. An exception is if the “EXISTS” function is used. This function can then replace a node on the bus with an input
on the master node.
The B1-node is selected by default, since every system has to contain exactly one Master node, B1. Four crane nodes and
seven spreader nodes are available for selection.
Checkboxes for enabling Twistlock redundancy as well as “Spreader stop” have to be checked here as well if these
functions are used.
4.2 Functionality
The system view enables the user to select a node configuration. By filling in the checkboxes you determine the lay-out
(topology) of the system. You also determine on which nodes (B1 & B2) you are to have the twistlock redundancy and
Spreader stop enabled. Each node configuration gives the respective node a unique ID represented by the address key.
You may also set system properties in this view. Some properties will be updated automatically when a project is saved.
The properties are:
4.2.1 Author
This is the author of the spreader program. Contains text of max 80 characters.
9(92) © 2000
Document: Project: Project No
4.2.8 Customer
This property is to contain the name of the customer who will use the Spreader program. Contains text of max 80
characters.
4.2.9 Comments
This is a text field intended for general comments regarding the Spreader program. Contains text of max 80 characters.
10(92) © 2000
Document: Project: Project No
5.1 General
The pin configuration view is presented as a tabular view of the system, where each tab represents a node. An I/O list
corresponding tags will be available for all enabled nodes in the system. The top tabs indicate which node is displayed.
A tag is composed of its Item identifier and its Comment. The used I/O not yet connected is marked red.
The Port id# field contains a port id, the numerical ID of the I/O number of the SCS2. The Connection field is either IN,
OUT or NC (Not connected) and if it’s a digital, analogue, PWM or Encoder signals. These fields cannot be edited.
Remark:
Allowed characters when giving names to Item identifiers, Comments, Components and Tags are:
[a, b, c..., z], [A, B, C..., Z], [0, 1, 2,..., 9] and “_” (underscore). No other characters must be used.
5.2 Functionality
This view allows you to change the tag for all port numbers on all nodes in the system. Within this view you give each
individual I/O its’ nick name, Item Identifier, to make the program more comprehensible, you also assign any comments
to the I/O. The connection type (IN/OUT) will be updated automatically as the Spreader program is altered in the
component view; i.e. the direction of the I/O point is decided when the I/O is connected. Note that ABE will only permit
I/O configuration that is supported by the current SCS2 HW, hence the digital I/O direction can only differ outside of
groups of four apart from the last four I/O points in the list (45-48) which can configured individually.
11(92) © 2000
Document: Project: Project No
12(92) © 2000
Document: Project: Project No
6 Component view
6.1 General
The component view is where components are deployed and connected. A palette displaying all components is available
in the view. To add a component, select the component from the Palette and place it on your work space with the mouse.
Remark:
Allowed characters when giving names to Item identifiers, Comments, Components and Tags are:
[a, b, c..., z], [A, B, C..., Z], [0, 1, 2,..., 9] and “_” (underscore). No other characters must be used.
Components may be dragged within a page to change the layout. Each page can be resized vertically.
13(92) © 2000
Document: Project: Project No
14(92) © 2000
Document: Project: Project No
Select COM1 or COM2 under selection depending on what serial port is connected to the SCS2.
Automatic update will be performed at an interval specified by Update interval, if Auto is checked
The online monitoring starts by telling the SCS2 to add all visible components and their connections. This takes more or
less time depending on the number of present components and connections in visible Page(s). A progress bar appears
above the buttons, when adding the components, to show you current status.
Stop online monitoring by pressing the Stop online monitoring button (same button as Start online monitoring button).
15(92) © 2000
Document: Project: Project No
7 Load view
7.1 General
The load view provides functionality to download and upload Spreader programs. The connection to the system is
selected in the connection box; the possible choices are, Com1 and Com2. Current status of the transfer is displayed in the
three progress bars.
7.2 Functionality
When the download button is pressed the user is prompted to point out the file to download to the system. It has to be a
compiled downloadable program file (*.spr-file). The current status of a download process from the PC to the system is
shown in the top progress bar. The distribution transfer between nodes is shown in the two progress bars at the bottom of
the page. The upload button allows the user to retrieve a program file from a connected system and save it to a file.
16(92) © 2000
Document: Project: Project No
8 Components
Terminology:
In this section the follow terms are used:
False = 0 = logical low level
True = 1 = logical high level
8.1 Controllers
States:
DISABLED:
When enable goes false or Spreader Stop is activated this state is reached.
All outputs are set false.
STARTUP:
This state is reached every time the system is starting up or when DISABLED state is left.
A decision is made if lock or unlock sequence should be initiated (i.e. a transition to those states).
LOCK_ALL:
Lock all Twistlocks.
UNLOCK_ALL:
Unlock all Twistlocks.
IDLE:
When a lock or unlock command has resulted in a complete sequence this state is reached. Lock/unlock outputs are not
changed from previous state.
17(92) © 2000
Document: Project: Project No
LOCK_ALL
[ SpreaderStop = 0, Enable = 1 ]
[ All unlocked ]
[ All unlocked ]
DISABLED
18(92) © 2000
Document: Project: Project No
8.1.1.4 Parameters
19(92) © 2000
Document: Project: Project No
“Unlock after landed” = when an unlock command is given after landed on all corners (and delay has elapsed if any)
“Lock after landed” = when a lock command is given after landed on all corners (and delay has elapsed if any)
States:
DISABLED:
When enable goes false or Spreader Stop is activated this state is reached.
20(92) © 2000
Document: Project: Project No
STARTUP:
This state is reached every time the system is starting up or when DISABLED state is left.
A decision is made if lock or unlock sequence should be initiated (i.e. a transition to those states).
LOCK_ALL:
Lock single and twin Twistlocks.
LOCK_SINGLE:
Lock single Twistlocks.
UNLOCK_ALL:
Unlock single and twin Twistlocks.
UNLOCK_SINGLE:
Unlock single Twistlocks.
IDLE:
When a lock or unlock command has resulted in a complete sequence this state is reached. Lock/unlock outputs are not
changed from previous state.
[ T wi n i s down ]
[ T wi n i s up ]
[ A l l l ocked ]
[ A l l l ocked ]
ena bl e = 1
[ A ll u nl ocked ]
DISA BL ED [ A l l u nl ocked ]
[ T wi n is do wn ]
T win is up
UNLOCK_ SINGLE
UNLOCK_ AL L
21(92) © 2000
Document: Project: Project No
22(92) © 2000
Document: Project: Project No
8.1.2.4 Parameters
This component generates the following messages stored in the fault and event log onboard the SCS2. The message log
can be turned on/off in the parameter settings view via the check box Enable logging.
23(92) © 2000
Document: Project: Project No
States:
DISABLED:
When enable goes false or Spreader Stop is activated this state is reached.
All outputs are set false.
STARTUP:
This state is reached every time the system is starting up or when DISABLED state is left.
A decision is made if lock or unlock sequence should be initiated (i.e. a transition to those states).
IDLE:
This state is reached emedeately after UP or DOWN states have been reached.
UP:
All Flippers are sent up.
DOWN:
All Flippers are sent down.
24(92) © 2000
Document: Project: Project No
[ UpCom m and ]
START_UP ID LE
[ DownCom m and ]
DISABLED DOWN
8.1.3.4 Parameters
25(92) © 2000
Document: Project: Project No
States:
DISABLED:
When enable goes false or Spreader Stop is activated this state is reached.
All outputs are set false.
STARTUP:
Unconditional transition is made to IDLE state.
IDLE:
Waiting for command input.
EXPAND:
Expanding to next stop. Next stop is either next closest stop or a stop decided according to which Return to position X
command is given. A transition is made to IDLE state when next stop is reached.
RETRACT:
26(92) © 2000
Document: Project: Project No
Retracting to next stop. Next stop is either next closest stop or a stop decided according to which Return to position X
command is given. A transition is made to IDLE state when next stop is reached.
CONSTANT REPEAT:
When stopped at a position a new constant command is required to go to another position. Depressed keys or similar must
be released before a new command will be excepted.
Example:
1. Expand command is given.
2. Next stop is reached.
3. The telescope stops.
4. Expand command is released.
5. New expand command is given.
6. The telescope continues.
DELAY:
A delay is made for a time defined by Stop delay time (parameter). This delay is only performed if Delay is set in
Operation mode (parameter) else ignored.
“currentCommand” = is always EXPAND or RETRACT. The command inputs Retract / Expand command or Return to
position X. These command inputs are internally converted to EXPAND or RETRACT depending on current position
and desired position.
[ desiredStop = currentStop,
Operation m ode = Cons tant repeat ]
RETRACT
[ desiredStop = currentStop,
Operation m ode = Delay ]
START_UP DISABLED
[ SpreaderStop = 0,
Enable = 1 ]
27(92) © 2000
Document: Project: Project No
8.1.4.4 Parameters
28(92) © 2000
Document: Project: Project No
States:
DISABLED:
When enable goes false or Spreader Stop is activated this state is reached.
All outputs are set false.
STARTUP:
Unconditional transition is made to IDLE state.
IDLE:
Waiting for command input.
FEED_LEFT:
29(92) © 2000
Document: Project: Project No
FEED_RIGHT:
Feeds the Tower to the right.
CENTER:
Centres the tower. The Tower is centred when both At left sensor and At right sensor is true.
DELAY:
A delay is performed for a time defined by Direction change time (parameter).
[ Feed right ]
[ Feed left ]
START_UP ID LE
[ SpreaderStop = 0, Enable = 1 ]
[ Center ]
[ Delay perform ed ]
DISABLED
CENTER DELAY
30(92) © 2000
Document: Project: Project No
8.1.5.4 Parameters
31(92) © 2000
Document: Project: Project No
States:
DISABLED:
When enable goes false or Spreader Stop is activated this state is reached.
All outputs are set false.
STARTUP:
Unconditional transition is made to IDLE state.
IDLE:
Waiting for command input.
Expand command or Go position command (depending on current position) makes a transition to EXPAND state.
Retract command or Go position command (depending on current position) makes a transition to RETRACT state.
EXPAND:
Expands telescope.
PWM expand output is set to maximum (High speed) if not in Low speed window or in Stop window.
PWM expand output is set to minimum (Low speed) if in Low speed window.
PWM expand output is set to zero if in Stop window.
Digital expand output is set to false if in Stop window else true.
RETRACT:
Retracts telescope.
PWM retract output is set to maximum (High speed) if not in Low speed window or in Stop window.
PWM retract output is set to minimum (Low speed) if in Low speed window.
PWM retract output is set to zero if in Stop window.
Digital retract output is set to false if in Stop window else true.
DELAY:
Performs a delay (Stop delay time) at each stop if Delay is selected in Operation mode (parameter)
Expand and retract outputs are set to false in this state.
32(92) © 2000
Document: Project: Project No
CONSTANT_REPEAT:
A new Expand or Retract command must be given to leave this state if Constant repeat is selected in Operation mode
(parameter).
Expand and retract outputs are set to false in this state.
[ desiredPosition >
currentPos ition ]
[ Delay perform ed ]
STARTUP ID LE
33(92) © 2000
Document: Project: Project No
34(92) © 2000
Document: Project: Project No
8.1.6.5 Parameters
35(92) © 2000
Document: Project: Project No
36(92) © 2000
Document: Project: Project No
the possibility of storing the current position in a volatile memory of the SCS2 and then returning to this position via a
command until the power is cycled or a new position is stored.
States:
DISABLED:
When enable goes false or Spreader Stop is activated this state is reached.
All outputs are set false.
STARTUP:
Unconditional transition is made to IDLE state.
IDLE:
Waiting for command input.
Expand command, Returned to logged position command (depending on current position) and Go to predefined position
(depending on current position) makes a transition to EXPAND state.
Retract command, Returned to logged position command (depending on current position) and Go to predefined position
(depending on current position) makes a transition to RETRACT state.
EXPAND:
Expands the Twin boxes until position is within range Stop window from desired stop.
RETRACT:
Retracts the Twin boxes until position is within range Stop window from desired stop.
RETRACT
[ desiredPosition = currentPosition ]
STARTUP ID LE
[ desiredPosition = currentPosition ]
[ SpreaderStop = 0, Enable = 1 ]
DISABLED
EXPAND
37(92) © 2000
Document: Project: Project No
38(92) © 2000
Document: Project: Project No
8.1.7.4 Parameters
39(92) © 2000
Document: Project: Project No
States:
DISABLED:
When enable goes false or Spreader Stop is activated this state is reached.
All outputs are set false.
STARTUP:
Unconditional transition is made to IDLE state.
IDLE:
Waiting for command input.
Expand command makes a transition to EXPAND state if In 45ft sensor is false.
Retract command makes a transition to RETRACT state if one not In zero left sensor is true and if not In zero right
sensor is false.
EXPAND:
Expands the Twin boxes as long as Expand command is given and In 45ft is false.
RETRACT:
Retracts the Twin boxes as long as Retract command is given and both In zero left and In zero right sensors are false.
[ Expand, !in45Pos ]
[ !Expand OR in45Pos ]
STARTUP ID LE
[ !Retract OR (inZeroPosLeft, in
[ !SpreaderStop, Enable ] ZeroPos Right) ]
DISABLED RETRACT
40(92) © 2000
Document: Project: Project No
8.1.8.4 Parameters
41(92) © 2000
Document: Project: Project No
8.1.9 TwinUpDown
The TwinUpDown component is designed to be used on the twin telescopic Spreaders. The component performs the twin
up and twin down sequences automatically upon the commands twin up and twin down. The sequence for twin down
consists of the twin units separating until the Left attach & right attach permits have been made. Thereafter the hooks
situated on the tension rod are lowered and finally the twin boxes are lowered. The sequence for twin up consists of the
hooks on the tension rod being raised followed by the twin boxes being raised. The twin consoles are now retracted until
the zero position switches are made, the retract output is active for a short off-delay after that to ensure that both units are
fully retracted. When a complete up sequence has been performed a pulse is given on the output “ Twin up ready pulse ”,
which in turn can be used for instance to run the Spreader back to the correct single 40ft position.
42(92) © 2000
Document: Project: Project No
TWIN_UP TWIN_DOWN
1 : [ !allTwinUp || !hookLeft 2 : [ !allTwinUp || !(hook [ twinDownRequestM ]
Disconnected || !hookRight LeftDisconnected &&
Disconnected ] RAISE_BOXES
hookR ightDis connected) ]
CONN ECT
[ !allTwinUp ] [ allTwinUp ]
2 : [ !(twinInZeroPosLeft
&& twinInZeroPosRight) ] IN CH_IN
3:
HOLD_DOWN
HOLD_UP
OFF_DELAY_INCH
1 : [ !(twinInZeroPosLeft && tw inIn
ZeroPos Right) || delayM.isTim eout() ]
Trans ition to IDLE state if Trans ition to IDLE state if
tw inDownCom m and tw inUpCom m and
H* H*
[ twinUpCom m and ]
ID LE
2 : [ anyTwinU p && !(hook
LeftConnected && hook 2 : [ twinUpRequestM ] 1 : [ !anyTw inUp && hook
RightConnected) ] LeftConnected && hook
RightConnected ]
3:
STARTUP
43(92) © 2000
Document: Project: Project No
44(92) © 2000
Document: Project: Project No
8.1.9.4 Parameters
45(92) © 2000
Document: Project: Project No
8.1.10 PID
8.1.10.1 Overview
The PID components are used to control fast processes, e.g. positioning, syncronisation and control of hydraulic cylinders
with special requirements.
Each PID component controls a single cylinder, but usually they ared used in pair and then 2 PID components are needed.
The PID component have the following features:
Position control
Velocity control
Syncronisation of two cylinders
Acceleration limitation
46(92) © 2000
Document: Project: Project No
8.1.10.6 Implementation
Each node are equipped with two PID components that can be used.
Each PID can control a single cylinder. All parameters for each cylinder are located in the corresponding PID. To identify
the two PIDs each component has a parameter called Regulator index which has to be set to 0 and 1 respectively.
When using sync mode both PID components cooperate and the sync parameters are taken from PID0.
For more detailed information about the implementation, it is reffered to a special document describing the PID
component and AutoTuner component.
47(92) © 2000
Document: Project: Project No
8.1.10.9 Parameters
48(92) © 2000
Document: Project: Project No
49(92) © 2000
Document: Project: Project No
8.1.11 AutoTuner
This component is intended as a help when setting up the PID component. It will automatically move the cylinder(s) and
measuring it’s characteristics when component is enabled. If one intentions are to synchronize two cylinders with PID
components, it’s possible to adapt the two cylinders with the use of this component. This is done by enabling the check
box Prepare for sync parameter.
50(92) © 2000
Document: Project: Project No
The AutoTuner will store it’s measured parameters in the onboard NVRAM. These parameters can then be uploaded and
monitored/transferred to the matching PID component. It is important that the Record name is identical to the PID that is
supposed to use the auto tuned parameters.
For more detailed information about the implementation, it is reffered to a special document describing the PID
component and AutoTuner component.
8.1.11.3 Parameters
51(92) © 2000
Document: Project: Project No
52(92) © 2000
Document: Project: Project No
8.2 AnyBus
8.2.1 Introduction
Apart from the parallel I/O of the nodes, each node can be equipped with an AnyBus card used for external buses. This
card is fitted into the node on the connector at the right side of the board when the cover is off. By using the Anybus the
crane can utilise the SCS 2 as an integrated slave on the PLC network or an Anybus card can be used as a Master bus for
an internal I/O bus on the Spreader. The principal behind the Anybus is that the interface card translates a number of
different bus protocols to a standardised format on the address and data bus of the node. To change between different
buses one can then simply change the type of interface card. For details regarding configuration of a specific bus, please
view the user manual for that specific card and the electrical documentation for your specific project.
The size of the data exchange area between the SCS2 and the Anybus card is configurable up to 64 bytes in and 64 bytes
out. The configuration is done via HMS standard files. This interface must be configured in the same way for both the
Master and the SCS2 slave for the bus to work correctly. For each project a document has to be sent to the customer
describing the used parts of the interface. When referring to in/out we view it from the SCS2 side, hence input for the
SCS2 is an output from the master in the crane.
OUT IN
Byte 0-63 Byte 0-63
Project Project
specific specific
outputs inputs
Output Segment
In the output segment it is possible to use a number of bytes for diagnostic information in the form codes. The diagnostics
are handled by the Anybus System component. The code sent will be equivalent with the code displayed in the onboard
display, hence there will be three levels of this code INFO, WARNING, ERROR. Apart from the code and the byte for
53(92) © 2000
Document: Project: Project No
indicating the type of code a counter will be incremented each time a code is sent. The counter is a 16bit value and
therefore will begin from 0 if the counter overflows. The value of this counter will be sent each time that a new diagnostic
message is transmitted. The start position of the diagnostic areas is configurable.
The remaining bytes for output will be assigned the interface with the crane and will vary on each project. The
assignments here are discrete outputs from the Spreader and current values (pressure etc.) from devices on the Spreader.
These assignments are documented in the electrical documentation of the project.
Input Segment
The entire range of the input area is configurable per project. The assignments here are discrete inputs to the Spreader and
set point values for the Spreader. These assignments shall be documented in the electrical documentation of the project.
8.2.2.2 Parameters
Parameter Unit Description
Node Node id The node identity of the node where
the Anybus interface is located.
Log active Option Indicates if the log should be
exported to the Anybus interface or
not.
54(92) © 2000
Document: Project: Project No
8.2.3.2 Parameters
8.2.4.2 Parameters
55(92) © 2000
Document: Project: Project No
8.2.5.2 Parameters
8.2.6.2 Parameters
56(92) © 2000
Document: Project: Project No
8.2.7.2 Parameters
8.2.8.2 Parameters
57(92) © 2000
Document: Project: Project No
8.3 CANopen
8.3.1 Introduction
CANopen is a field bus protocol based on CAN and provides a flexible and powerful open industrial communication
solution.
Apart from the parallel I/O of the nodes the SCS2 master node can control up to 15 CANopen slaves. The SCS2 master
node act’s as a CANopen master, this includes network management, SDO services and PDO handling.
The SCS2 master node processes the CANopen slave data i.e reads inputs and controls outputs.
All configuration of the CANopen functionality is made in the CANopen IO configuration view described in section
5.2.4. Note that the components described in the following section is not visible in the component palette.
8.3.2.2 Parameters
8.3.3.2 Parameters
58(92) © 2000
Document: Project: Project No
8.3.4.2 Parameters
8.3.5.2 Parameters
8.3.6.1 Parameters
59(92) © 2000
Document: Project: Project No
60(92) © 2000
Document: Project: Project No
8.4 Guards
8.4.1.2 Parameters
61(92) © 2000
Document: Project: Project No
8.4.3.3 Parameters
62(92) © 2000
Document: Project: Project No
8.4.4.2 Parameters
63(92) © 2000
Document: Project: Project No
8.5 Gates
This section contains the simple Boolean instruction set.
8.5.1 AND
This function block performs the function of the logical AND with the number of inputs specified in the parameter
settings.
Basic function
IN 0 IN n OUT
0 0 0
0 1 0
1 0 0
1 1 1
64(92) © 2000
Document: Project: Project No
8.5.1.3 Parameters
8.5.2 NAND
This function block performs the function of the logical NAND with the number of inputs specified in the parameter
settings.
Basic function
IN 0 IN n OUT
0 0 1
0 1 1
1 0 1
1 1 0
8.5.2.3 Parameters
8.5.3 NOR
This function block performs the function of the logical NOR with the number of inputs specified in the parameter
settings.
Basic function
IN 0 IN n OUT
0 0 1
0 1 0
1 0 0
1 1 0
65(92) © 2000
Document: Project: Project No
8.5.3.3 Parameters
8.5.4 OR
This function block performs the function of the logical OR with the number of inputs specified in the parameter settings.
Basic function
IN 0 IN n OUT
0 0 0
0 1 1
1 0 1
1 1 1
66(92) © 2000
Document: Project: Project No
8.5.4.3 Parameters
8.5.5 NOT
This function block performs the function of the logical NOT with the number of inputs specified in the parameter
settings.
Basic function
IN OUT
0 1
1 0
8.5.6 XOR
This function block performs the function of the logical XOR (exclusive or) with the number of inputs specified in the
parameter settings.
Basic function
IN 0 IN n OUT
0 0 0
0 1 1
1 0 1
1 1 0
67(92) © 2000
Document: Project: Project No
8.5.7 SR Latch
This function block performs the function of the logical SR latch with the number of inputs specified in the parameter
settings. The output will go high at a high signal on the Set input and will go low again at a high signal on the Reset input.
If both inputs are on simultaneously this latch will reset (output goes low).
8.5.8 RS Latch
This function block performs the function of the logical RS latch with the number of inputs specified in the parameter
settings. The output will go high at a high signal on the Set input and will go low again at a high signal on the Reset input.
If both inputs are on simultaneously this latch will set (output goes high).
68(92) © 2000
Document: Project: Project No
8.5.9.3 Parameters
8.6 Digital
69(92) © 2000
Document: Project: Project No
8.6.1.3 Parameters
8.6.2.3 Parameters
70(92) © 2000
Document: Project: Project No
8.6.3.3 Parameters
8.6.4 Split
The split component is used to generate two or more signals available for connection from one signal line. I.e. it can in
many cases replace the use of intermediate variables, since the signal value of the input and the outputs are always the
same.
8.6.4.3 Parameters
8.6.5 Pulse
The Pulse component is used to generate a pulse. The duration of the pulse is set by a parameter. The pulse can be trigged
on either positive or negative flank. The pulse is restarted if an new active flank is detected during the pulse.
An output indicating time left until pulse is unlit is also available.
71(92) © 2000
Document: Project: Project No
8.6.5.3 Parameters
8.7 Miscellaneous
8.7.1 Constant
The Constant component is used to store a Boolean or Analogue value as a constant variable to use within the logic. Note
that any other value than zero is considered as a logical one when using this component for digital purposes.
8.7.1.2 Parameters
72(92) © 2000
Document: Project: Project No
73(92) © 2000
Document: Project: Project No
74(92) © 2000
Document: Project: Project No
8.7.3.3 Parameters
8.7.4 Memory
The Memory component is used when one wishes to write or read an analogue value from or to the NVRAM.
75(92) © 2000
Document: Project: Project No
8.7.5.3 Parameters
76(92) © 2000
Document: Project: Project No
8.7.6.3 Parameters
77(92) © 2000
Document: Project: Project No
8.8 Analogue
The Analogue components are used to work with analogue values.
8.8.1.2 Parameters
78(92) © 2000
Document: Project: Project No
79(92) © 2000
Document: Project: Project No
8.8.6.3 Parameters
8.8.7 Scale
The Scale components scales a analogue value according to the formula,
OUT = ((scaledMax – scaledMin)/(INMax-INMin))*(IN - INMin) + scaledMin,
which performs a linear scaling with an offset according to OUT = k*IN + m.
8.8.7.3 Parameters
80(92) © 2000
Document: Project: Project No
8.8.8 AnalogueLatch
The Analogue latch is a component that stores a value internally when triggered by a digital input. The value stored in an
internal variable can be read at the output of the component. As long as the digital trigger input is active the input value is
directly transferred to the output value and as soon as the digital input goes low the output value remains constant at the
current value until a new digital command is given.
8.8.9 Filter
The Filter component is used to filter analogue signals from noise.
81(92) © 2000
Document: Project: Project No
8.8.9.3 Parameters
8.8.10 AuxAnalogue
This component implements two more analogue inputs.
8.8.10.2 Parameters
82(92) © 2000
Document: Project: Project No
9 Tutorial
This tutorial will guide you through the process of designing a Spreader program using ABE.
Steps covered in this tutorial.
Creating a new project
System view
Pin configuration
Component view
Load view
Fill in the Value fields in the parameter listing. Note that some of the fields are not editable.
83(92) © 2000
Document: Project: Project No
Make sure tab B2 is activated in the view and do the same for Port id# 1 to 4.
Note: The red colour of the fields indicates that the ports are not yet connected.
If available components pallet is not visible. Activate it by clicking at the Components button shown in picture below.
84(92) © 2000
Document: Project: Project No
Note: Connections with red colour indicate that they are not yet connected. Connections with white colour indicate that
they are optional to connect.
Double click on the component to open Properties for the FAC component. Change the property Number of Flippers to 2.
85(92) © 2000
Document: Project: Project No
The new appearance for the component should look like this:
By placing the pointer over the component or one of its connections a hint (tool tip) will appear. The hint tells you about
the properties for the component or its connection.
Click with your right mouse button over a connection on the component. A pop up menu will appear. Move the cursor as
shown in the picture below and click on your left mouse button over Flipper_Down.
86(92) © 2000
Document: Project: Project No
Continue with the remaining connections until you have all connections connected.
If you want to disconnect a connection you click over the connection with your right mouse button and choose disconnect
when it appears.
When your system is complete there should not be any red coloured connections in the Component view or Item
identifiers in the Pin configuration view.
Your Component view should look like Figure 12 when all your connections are made.
Now you are ready to generate downloadable Spreader program file. Select Compile from the File menu.
If the following message box appears your system is not configured properly. Look for red coloured connections or item
identifiers. If port is configured to be used but isn’t you must delete it.
Save the output file (when compiling the spreader program) with the name “tutorial.spr”.
When you have generated your downloadable program file it can be found at the location where it was saved. You must
not edit this file.
87(92) © 2000
Document: Project: Project No
1. Select COM1 or COM2 under selection depending on what serial port is connected to the SCS2.
Answer Yes to the second dialog to open the uploaded spreader program in the editor. (If you press No, you have to
manually open the uploaded spreader program.)
88(92) © 2000
Document: Project: Project No
1. Make sure you have the same spreader program in ABE and SCS2. If you are not sure about this, you can always
download your current spreader program or upload the spreader program from the SCS2 (see Step 5).
2. Select COM1 or COM2 under selection depending on what serial port is connected to the SCS2.
If Auto is checked, automatic update will be performed at an interval specified by Update interval.
The online monitoring starts by telling the SCS2 to add all visible components and their connections. This takes more or
less time depending on the number of present components and connections in visible Page(s). A progress bar appears
above the buttons, when adding the components, to show you current status.
Once the online monitoring is started, the design window is locked for editing. If you want to monitor another part of
your design (not visible at the moment); you have to stop the online monitoring and then scroll to that part and start the
monitoring again.
89(92) © 2000
Document: Project: Project No
10 CANopen tutorial
This tutorial will guide you through the process of configuring a Spreader program containing CANopen functionality.
The tutorial covers the following steps:
Add a CANopen slave
Add an input
Connecting input to Spreader logic
90(92) © 2000
Document: Project: Project No
The CANopen I/O configuration view now looks like the picture below.
91(92) © 2000
Document: Project: Project No
92(92) © 2000
User Manual
BMS - Light
Version 1.0
Table of contents
1 Introduction ................................................................................................................................................................... 3
2 Installing BMS – Light .................................................................................................................................................. 3
2.1 HW requirements................................................................................................................................................... 3
2.2 Installation ............................................................................................................................................................. 3
2.3 Disclaimer.............................................................................................................................................................. 3
3 User interface................................................................................................................................................................. 4
3.1 Menu (top toolbar) options: ................................................................................................................................... 4
3.2 Status bars in main window................................................................................................................................... 5
4 Download view.............................................................................................................................................................. 6
5 Get log view .................................................................................................................................................................. 7
5.1 Filtering constraints ............................................................................................................................................... 8
6 I/O status view............................................................................................................................................................... 9
7 Misc. view ................................................................................................................................................................... 10
Anybus view........................................................................................................................................................................ 11
8 Spreader info view....................................................................................................................................................... 12
9 CANopen IO view....................................................................................................................................................... 13
10 Upload view............................................................................................................................................................. 14
11 Advanced................................................................................................................................................................. 15
11.1 CAN Tester.......................................................................................................................................................... 15
11.2 Boot Loader ......................................................................................................................................................... 17
11.3 Asserts ................................................................................................................................................................. 18
11.4 POM Loader ........................................................................................................................................................ 19
11.5 Bluetooth ............................................................................................................................................................. 19
11.6 CANopen services ............................................................................................................................................... 20
2(20) © 2000
Document: Project: Project No
Introduction
The BMS is a software tool used for monitoring and handling the Bromma system SCS2. This manual assumes the user
has good knowledge of the SCS2 system as well as Windows environments.
HW requirements
An Intel compatible PC running Windows 95 / 98 / NT 4.0 / 2000.
At least one serial communication port available (COM1 or COM2).
At least 1Mb of free disk space.
Installation
Close any other applications running under Windows.
Insert the first disc into your disc station (if installing from disc)
Run the file BMSSetup.exe from the BMS folder on your provided disk.
Follow the instructions on the screen.
Disclaimer
Copyright Bromma Conquip AB. All rights reserved.
Products and company names mentioned herein may be trademarks or trade names of their respective owners.
Bromma Conquip AB operates on a policy of continuous improvement. Therefore we reserve the right to make changes
and improvements to any of the products described in this manual without prior notice.
Bromma Conquip AB is not responsible for any loss of data, income or any consequential damage howsoever caused.
3(20) © 2000
Document: Project: Project No
User interface
Activates selected tab [Download, Get log, I/O status, Misc., Anybus, Spreader info, Upload]
Modem connection
Connect to node: connects BMS to selected node [B1, B2,..., B8, A1, A2, A3, A4]. This connection is made over RS232
link through the CAN bus. Normally select Local node.
Advanced options: Intended for Bromma R&D personnel.
4(20) © 2000
Document: Project: Project No
Main window
5(20) © 2000
Document: Project: Project No
Download view
This tab is used to download the entire system program to the system. Note. It takes a considerable amount of time to
update the system program and therefore make sure that the system can be down for this amount of time.
1. Transfer status from BMS to the connected node [4]. PC downloading to the connected node.
2. Transfer status from connected node [4] to node [5]. Distribution of the program via the bus lines to the other nodes
on the bus.
3. Total transfer status. Status of complete system to be downloaded.
4. Connected node (to PC).
5. Receiving node when distributing between nodes.
6. Select file to download. Press here to select the file to be downloaded. When file is selected download process starts.
7. Cancels current transfer to connected node. The operation just cancels the feedback of transfer status if distribution
between nodes has started (i.e. the operation will not effect the transfer in this case).
6(20) © 2000
Document: Project: Project No
1. Gets next set of logged messages (max 128 messages each time its’ pressed)
2. Get all messages in log.
3. If checked, auto mode is on. Auto mode triggers the Next button [1] at an interval of X seconds defined by [4].
4. Interval for reading via auto mode in seconds.
5. Enable filtering. The filtered table is shown if checked. Filtering can be used to only view certain parts of the log.
6. Opens the Filtering constraint dialog. Select the type of filtering here.
7. Clears the log table on the PC. The log in the SCS2 remains unaffected.
8. Saves the entire log table in a comma separated text file. Can be opened in for instance in Wordpad, Excel etc.
9. Cancels current operation.
10. Load button. Loads and displays a saved log file.
7(20) © 2000
Document: Project: Project No
Filtering constraints
Select the type of filtering for the log view in this view.
Checked Categories, Nodes, Sub codes and Codes will appear in the filtered table.
Ex: APS_TEACH_COMMAND (of category Info) is checked but not Info under Category. The message will therefor not
appear in the filtered table.
1. Message categories
2. Nodes that have reported messages.
3. Message codes for entire table
Filtering constraints
8(20) © 2000
Document: Project: Project No
1 3
4
5
6 7
8
9(20) © 2000
Document: Project: Project No
Misc. view
This view is used to get and set general information of the SCS2.
1. Updates the Date and Time fields from the PC when pressed.
2. Set the time and date on SCS2 according to Date and Time fields.
3. Get current date and time from the SCS2. Displayed in Date and Time fields.
4. Get address key information from the node [5].
5. Destination of question.
6. Serial cable connection.
7. Cancels current operation.
8. Get version information. Software version and protocol version for Boot and System program. The Boot program
version is Boot SW version and the System program version is System SW version. Don’t care about the COM
versions.
9. Reboots the system.
Ex. Serial cable [6] is connected via COM1 to B1 and Destination [5] is set to Local node (or B1, which would be the
same). B1 is configured to have E-stop and Redundancy block activated. This will give us the answer:
Key: 5
E-Stop: YES
Redundancy: YES
Module name: B1
8
2
7
6 5
10(20) © 2000
Document: Project: Project No
Anybus view
The Anybus view shows the status of the I/O transferred over the fieldbus interface of the Anybus card.
1. Input data to SCS2 via Anybus interface. The index field shows which byte is being viewed and the value field the
value of that byte in binary format.
2. Output data from SCS2 via Anybus interface. The index field shows which byte is being viewed and the value field
the value of that byte in binary format.
3. Reads all Input data [1] and Output data [2] from Anybus interface.
4. Cancels current operation.
5. Set DeviceNet master in Run mode. This operation can only be done when using a DeviceNet master.
6. Set DeviceNet master in Idle mode. This operation can only be done when using a DeviceNet master.
7. Select node where to Read [3] data from.
3
4
Anybus view
11(20) © 2000
Document: Project: Project No
1. Shows the selected key in the Spreader info field [6]. This field can not be edited.
2. Shows the current value of corresponding Key [1].
3. Sets the Value [2] for selected Key [1].
4. Deletes the value for selected Key [1]. The Key [1] can not be deleted, just the value.
5. Updates the entire Spreader info [6] view on the PC.
6. Table of all Keys stored in external EEPROM.
7. Cancels current operation.
12(20) © 2000
Document: Project: Project No
CANopen IO view
The CANopen view shows the status of the I/O transferred over the CANopen interface.
From this view its also possible to select individual or groups of I/O and override it/them.
2
3
CANopen IO view
13(20) © 2000
Document: Project: Project No
Upload view
This view is for Bromma R&D personnel only. It is used to upload memory blocks from the SCS 2.
14(20) © 2000
Document: Project: Project No
Advanced
These six sub views are mainly intended for Bromma’s R&D personnel only.
CAN Tester
This view holds the functionally of the CAN Tester. To be able to use the CAN Tester the master node has to be keyed as
Test. See the SCS 2 manual for information.
15(20) © 2000
Document: Project: Project No
16(20) © 2000
Document: Project: Project No
Boot Loader
The Boot Loader view is used to download new boot program to connected node.
17(20) © 2000
Document: Project: Project No
Asserts
The asserts view holds the functionality of reading asserts from the SCS2 . It is used for detecting unexpected system
events.
Asserts view
18(20) © 2000
Document: Project: Project No
POM Loader
The POM Loader view is used for downloading new power monitoring programs to the SCS2 .
Bluetooth
From this dialog it’s possible to configure and manage Bluetooth settings.
Note that the configuration possibilities only works with Bromma Conquip’s own Serial port adapter.
19(20) © 2000
Document: Project: Project No
CANopen services
From this view it’s possible to perform read and write actions to CANopen slave nodes OD (Object Dictionary).
The read and write actions uses the SDO (Service Data Objects) concept of CANopen. For a more detailed description of
CANopen and it’s functionality it’s referred to more specific documentation.
20(20) © 2000
Rev 1.0 2004-12-08
Document: Project: Project No
2
Manual SCS
Prepared by: Date: Version: Page:
Andy Lewis 2004-12-08 13:51 11 2(55)
1 General
1.1 Overview
This document serves as a user manual and shall be used by the surveillance and maintenance operators of the Bromma
SCS2. Software as well as hardware routines and descriptions are covered in this document.
1.2 References
Location where to find the latest revision of this document: http://www.bromma.com/backyard/
2 Introduction
The core of the Bromma Smart Spreader is the Spreader Communications System (SCS2). In 1991 when Bromma decided
to develop a new and highly advanced communications system a close look at the available bus systems revealed a
number of shortcomings, such as temperature range, EMC (Electro Magnetic Compatibility) protection and mechanical
roughness.
Bromma therefore decided to design a bus system that met the demands made on an electronic system for a tough
Spreader application. We decided to develop a modular programmable controller, with a heavy-duty field bus interface
that complies with European and international standards for control equipment in this area. The SCS2 solution is a single
control product that can be used as I/O, as a PLC, and as distributed control for up to 528 I/O points. SCS2 nodes are
simple to install. You can connect up to 11 devices using just a single pair of wires. With its modular and scaleable
architecture, intuitive features and unparalleled ease of use, it will help save crane builders and end users time and money.
A bus system able to handle 528 I/O ports (programmable input or output).
Up to four analogue inputs with 12 bit resolution.
Four PWM outputs for proportional solenoids.
One general purpose RS485 channel OR SSI channel.
Communication with the help of a standard spreader cable — no screening, no twisted pair.
A system that withstands the repeated shocks and vibrations suffered by spreaders.
A system able to operate in tropical heat and arctic cold.
Choice of different field bus interfaces (ProfiBus, Interbus-S, Device Net….)
Optional duty cycle input
2.1 General
As a universal I/O, SCS2 gives you the freedom to connect to a wide variety of host controllers, including PLC's, DCS
and PC-based control systems by way of DeviceNet, Profibus-DP. SCS2 can be networked as a slave to Profibus-DP or
you can choose a DeviceNet master module for easy third-party integration. Designed by Bromma engineers for reliable
performance in the particularly challenging environment of container handling the system corporate four basic elements:
Crane Node A device directly interfacing with the crane’s control systems, computer and
monitoring screens, providing an optional serial bus interface for
programming or diagnostic communications, as well as an interface to the
spreader node.
Crane-Spreader Communications Link A two-wire conventional cable CAN communications between the crane
control system and the spreader.
Spreader Node A device that interfaces directly with the spreader’s sensors, supports discrete
signals, and acts as the Master node.
Sensors and Switches Conventional sensors, switches, and actuators on the spreader.
The system is divided into several hardware units called nodes. The nodes are located on the spreader and in the crane.
The nodes are connected to each other via a CAN network, see figure 1. The number of nodes required is based on the
1
For details regarding separate dedicated crane fieldbus gateway, see separate manual
Manual 4 2004 Bromma Conquip AB
File: SCS_1 Printed: 2004-12-08 13:51
Document: Project: Project No
2
Manual SCS
Prepared by: Date: Version: Page:
Andy Lewis 2004-12-08 13:51 11 5(55)
number of I/O needed. The nodes are all equals, both in software as well as in hardware. This reduces spare parts and
enables easy-to-change procedures.
The only difference is their identity, id. Depending on their location the nodes have different ids. They are numbered
from 0 to 11 where:
0 is the master called B1
1-7 are slave nodes located on the spreader called B2-B8
8-11 are slave nodes located in the crane called A1-A4.
Figure 1. The figure shows SCS2 connected to the spreader and the crane via I/O. The nodes are also connected internally
via a CAN network.
The SCS2 is built up of several nodes co-operating in the system. Each node has a specific role, either slave or master.
There must be only one master node in the system and the rest are slaves.
The master node makes all the calculations and decisions. The slave nodes act as remote I/O to the master, but can also
have distributed functions such as regulators.
3 Software
The SCS2 software consists of three types of programs; Boot Program, System Program and Spreader Program.
4 Hardware Overview
Below is a picture of a SCS2 node. The different parts are explained in the following chapter.
4.2 Display
The display shows three pages of information where each page has a maximum of 8 characters. Each page is shown for 1
second. The pages show the following:
Node ID and System program version. Format: <Node ID><Version>.
Elapsed time running since power on. Format: DDD HHMM where DDD is the number of days, HH the number of hours
and MM the number of minutes.
Message page. The message page shows numeric information only, which has to be translated into comprehensive plain
text manually. The meaning of this page is explained in the rest of this section.
There are also four red LED’s in the bottom of the display window indicating the supply voltage level. Four different
levels are indicated and the ideal voltage is when all LED’s are lit.
to run the system below the OK level though it still seems to work fine. Attached devices may
malfunction at lower voltages thus making the system unreliable. The green LED is the “power on” indicator.
There are three categories of information displayed on the event page: information, warning and error.
Warning W W60 Warning shows information about the system status that is of high
importance. The system keeps on running. Warning messages will
begin with a W.
Information
The display can show 8 characters. These are used in the following format:
LTTTSSSS
L = Level type
TTT = Message type
SSSS = Sub type
Example:
E102 => Error in initialising the hardware
W61 1 => Warning indicating that a twistlock is indicating locked and unlocked. The sub code indicates that it is corner 1.
I59 => Information that the system has started.
Level type
The level type can be one of the following: I = Information, W = Warning, E = Error
Message type
The message type represents the cause of the message. Examples of message types are System started, Wrong system
version and I/O error.
All these types are described in appendix A.
Sub type
The sub type is used to specify more detailed information about the message type. The sub types have different meanings
for all message types. For example does sub type 14 together with message type 47 mean I/O error on digital port 14
instead of just I/O error.
These sub types are described in appendix A.
Only the latest event is displayed at a time. When the display shows a warning and an event occurs which would show
information, the warning has higher priority and is thereby left on the display. The same relationship goes for error-
information and error-warning.
Priority in descending order:
Note that warnings are cleared from the display after at least 10 messages of informational type have passed and the
warning message is older than 15 minutes. Error messages are cleared by resetting the system.
Description
I/O-1 General purpose input or output / Unlocked_0 31
I/O-2 General purpose input or output / Unlocked_1 41
I/O-3 General purpose input or output / Unlocked_2 43
I/O-4 General purpose input or output / Unlocked_3 42
Common/Supply 1 Common junction for I/O-1 to I/O-4 44
To make linking of common supplies easier the X1 connector also has groups if pins linked together to be used basically
as jumper bars with the same potential. The following pins are linked together internally for the purpose of feeding
switches/valves with common potential.
To make linking of common supplies easier the connector also has groups if pins linked together to be used basically
as jumper bars with the same potential. The following pins are linked together internally for the purpose of feeding
switches/valves with common potential.
24Volt AC or DC power supply for the node. The signals are doubled in the connector due to the current limit of single
pins. DC voltage can be applied either way.
The two CAN nets are placed in the X2 connector. The first net use Bromma CAN (BCAN) voltage levels and the second
net use standard CAN voltage levels. The standard CAN net has to be terminated with external resistors.
All nodes must have a unique identity. This is read from the Id pins ID0 – ID4 where pins being connected to the ground
pin corresponds to ”zeroes” and pins left unconnected are considered ”ones”.
Configuration
Since all nodes are the same in reference to the software as well as hardware you have to configure them to carry different
roles. Setting the address key configures the role of the node. The address key has two other functions as well, enabling
Spreader stop and enabling redundancy block. These functions are described in chapters 4.10 and 4.8.
Key input Node Spreader Redundancy block and Pins to be linked together in Node number identifier
stop
name override of landing X2 connector when viewing Display and
pins Log
00000 Test 10,9,19,29,39,49
00001 A1 No No 10,19,29,39,49 8
00010 A2 No No 10,9,29,39,49 9
00011 A3 No No 10,29,39,49 10
00100 A4 No No 10,9,19,39,49 11
00101 B1 Yes Yes 10,19,39,49 0
00110 B1 Yes No 10,9,39,49 0
00111 B1 No Yes 10,39,49 0
01000 B1 No No 10,9,19,29,49 0
01001 B2 Yes Yes 10,19,29,49 1
01010 B2 Yes No 10,9,29,49 1
01011 B2 No Yes 10,29,49 1
01100 B2 No No 10,9,19,49 1
01101 B3 No No 10,19,49 2
01110 B4 No No 10,9,49 3
01111 B5 No No 10,49 4
10000 B6 No No 10,9,19,29,39 5
10001 B7 No No 10,19,29,39 6
10010 B8 No No 10,9,29,39 7
10011- Not
11110 Used
11111 Test None
Example
Here are three examples of how to set the address key:
A node with id B1 without redundancy block or emergency stop has the address key 01000.
A node with id B2 with both redundancy block and emergency stop has the address key 01001.
A node with id A2 (cannot have redundancy block or emergency stop enabled) has the address key 00010.
There are two analogue inputs on each node via the X2 connector (the other two are via the X4 connector). Each signal
has its own 10V-reference voltage output, ground reference and sensor signal that should be connected to the sensor
device.
Analogue in 2 X2/17
10Vref 2 X2/27
Signal ground 2 X2/7
There are four PWM outputs for driving external loads, for example proportional hydraulic valves. Each output has two
connections, one in and one out. The load should be connected between these, since it is a current loop.
An external EEPROM memory can be mounted on the spreader for spreader id and/or user defined purpose. The memory
is connected as below.
The RS 485 connection can be used for external sensors or user defined purpose. The SSI connection can be used with
external sensors with up to 25 bits data length. The hardware and the pins in connector X2 are shared between RS 485
and SSI. Therefore it is only possible to use one of these connections at a time.
To make linking of common supplies easier the X2 connector also has groups if pins linked together to be used basically
as jumper bars with the same potential. The following pins are linked together internally for the purpose of feeding
switches/valves with common potential.
Field bus operation is selected by connecting the field bus connector on the Anybus card with pin header CN103. The RS
232 serial port is selected by connecting CN100 and CN103. The two additional analogue inputs are selected by
connecting CN105 and CN103. Finally the duty cycle input is selected by connecting CN104 with CN103.
The AnyBus connector is used to interface any of the fieldbus types used apart from BCAN.
These two analogue inputs use the same ground and 10 V reference voltages as the two analogue inputs in connector X2.
The input range is either 0 to 10 V or 0 to 20 mA. The 0 to 20 mA range is selected for channel 1 by jumpering pin
number 1 and 2 in CN106 and for channel 2 by jumering pin number 4 and 5 in CN106. If no jumpers are added on
CN106 the voltage range, 0 to 10 V range is selected as default. In the 0 to 20 mA range a 500 Ohm resistor is used
internally and therefore the current being measured must be capable of driving 20 mA at 10 V to utilise the full 0 to 20
mA range.
The RS-232 connector, called BMS port, is located to the right of the node and is used only for this purpose.
C D
B
A E
The commands either from a remote node on the network or the local node itself.
The CPU and the system software as well as the application specific software (Spreader program).
The redundancy block of hardware static logic. The block has two functions, to make sure the twistlocks are energised
correctly at boot and to prevent the software from changing between lock and unlock when not landed during operation.
At boot the redundancy block checks the sensor status and determines if the twistlock valves are to be energised and in
what direction. After a correct landing and a transition between lock/unlock the redundancy block goes passive only
preventing the software to change between lock and unlock unless the Spreader is properly landed. In this state the
redundancy can be viewed as two relay contacts, where only one contact is closed at a time permitting the twistlock
outputs. The only way of overriding the logic of the redundancy block is to energise a specific I/O (landed override) on
that particular node.
The outputs to the lock/unlock valves
The sensor signals from landed, locked and unlocked.
To enable the redundancy the address key on B1 or B2 is used, this then automatically means you have to use input 48 as
Landed override to be able to override the hardware logic. The landed override signal sets the spreader in landed mode
and thereby temporarily disables the redundancy block.
The size of the data exchange area between the SCS2 and the Anybus card is configurable up to 64 bytes in and 64 bytes
out. The configuration is done via HMS standard files. This interface must be configured in the same way for both the
Master and the SCS 2 slave for the bus to work correctly. For each project a document has to be sent to the customer
describing the used parts of the interface. When referring to in/out we view it from the SCS2 side, hence input for the
SCS2 is an output from the master in the crane.
OUT IN
Byte 0-63 Byte 0-63
Project Project
specific specific
outputs inputs
Output Segment
In the output segment it possible to use a number of bytes for diagnostic information in the form codes. The code sent
will be equivalent with the code displayed in the onboard display; hence there will be three levels of this code INFO,
WARNING, ERROR. Apart from the code and the byte for indicating the type of code a counter will be incremented
each time a code is sent. The counter is a 16bit value and therefore will begin from 0 if the counter overflows. The value
of this counter will be sent each time that a new diagnostic message is transmitted.
The remaining bytes for output will be assigned the interface with the crane and will vary on each project. The
assignments here are discrete outputs from the Spreader and current values (pressure etc.) from devices on the Spreader.
These assignments shall be are documented in the electrical documentation of the project.
Input Segment
The entire range of the input area is configurable per project. The assignments here are discrete inputs to the Spreader and
set point values for the Spreader. These assignments shall be documented in the electrical documentation of the project.
This is performed by enabling Spreader stop using the address key on B1 or B2 and connecting the signal from the
spreader stop button to digital port 47 on the corresponding node (B1 or B2).
The spreader stop configuration must correspond to the spreader stop setting in the spreader program. This means that if
and only if the spreader stop on a node is enabled, digital port 47 must be connected to the Spreader Stop component in
the spreader program.
Node won’t start. No text appears in Measure the main supply. The voltage The green and all red LED’s in the
the display after power-on. should exceed 17V AC or DC. display should be lit.
BMS system can not communicate Probe TxD and RxD lines with Data lines should show square waves
with the node. oscilloscope while trying to between –10V to +10V relative to
communicate. GND pin.
The node can not communicate with Probe bus lines with oscilloscope.
the other nodes. CAN high should show square waves
pointing downwards and CAN low
should be showing square waves
pointing upwards.
Input signal fault Check if LED indicator on I/O module The LED should be lit when current
responds to sensor signal. flows through the module.
Check the Common connection for
correct supply.
Output signal fault Check if LED indicator on I/O module The LED should be lit when the circuit
responds to command. is closed.
Check the load for proper connection The load should be connected between
and grounding. the modules out pin and ground.
Check for broken fuse on the I/O
module.
Check the Common connection for The supply voltage depends on the
correct supply. type of load. 220V,110V,24V or other.
The node stops at start-up with Node Measure the voltage of all ID pins. 5V This can indicate that the node has
Id displayed. represent ones and 0V represents wrong id strapped telling the node to
zeroes. The measures should indicate participate in the system with wrong
the expected id. role.
Analogue input signal appears to be Check the reference voltage relative to There should be exactly 10V
faulty. the GND. difference between them.
Check if the node chassis is properly This is very important in an AC driven
grounded to the spreader. system.
5 Software tools
5.1 Overview
There are some related tools to the SCS 2, which support it in different ways. A brief description of these tools is given
below.
5.2 ABE
ABE (Application Builder Environment) is a tool for developing and configuring the spreader program, which controls
the logic of the spreader. ABE generates a load file. For more detailed see the separate manual.
5.3 BMS
BMS ultra light (Bromma Monitoring System ultra light) is a tool for monitoring events and reading status of I/O in the
SCS2. BMS can also be used to download new programs to the SCS2. For more detailed see the separate manual.
6 Miscellaneous
6.2 Dimensions
24 spare 16 .
25 spare 17 .
26 spare 18 .
27 spare 19 .
28 WARNING No data in program/system . System cannot start Contact Bromma
memory
29 spare 20 .
30 WARNING Checksum of memory corrupt .
31 ERROR HW fault on memory . System is brought into Contact Bromma
failsafe mode. if problem
persists
32 spare 21 .
33 spare 22 .
34 ERROR System init. Display. This error The error codes during the system boot phase that have caused the
code accumalates and displays system to go into failsafe mode
the errors ocurred during the
system boot, since no reporting
is done until the system has
started.
35 ERROR System failed in reading . System is brought into reload and
spreader program from memory failsafe mode. restart
36 ERROR No spreader program residing in . System is brought into download
memory failsafe mode. program
37 ERROR System failed to run spreader . System is brought into reload proram
program failsafe mode.
38 ERROR Spreader program object . System is brought into Check spreader
instances failed failsafe mode. program. If
problems persist
contact Bromma
39 ERROR Spreader program object . System is brought into Check spreader
instances failed failsafe mode. program. If
problems persist
contact Bromma
40 ERROR Spreader program object . System is brought into Check spreader
instances failed failsafe mode. program. If
problems persist
contact Bromma
41 ERROR Spreader program object . System is brought into Check spreader.
instances failed failsafe mode. If problems
persist contact
Bromma
42 ERROR Spreader program object . System is brought into Check spreader
instances failed failsafe mode. program. If
problems persist
contact Bromma
52 ERROR System initialising error when The node ID which has System is brought into restart
configuring nodes I/O generated the error failsafe mode.
53 ERROR Duplicate answers on I/O The node ID which has System is brought into restart
configuration from the same generated the error failsafe mode.
node when initialising system
54 spare 27
55 ERROR Duplicate answers on I/O The node ID which has System is brought into restart
configuration from the same generated the error failsafe mode.
node when initialising system
61 WARNING TWL - One twistlock indicating ID no. of the twistlock Message stored in log and check for
both locked and unlocked which generated the displayed on Spreader damaged sensors
warning and sensor
adjustment or
mechanical
reasons
62 WARNING TWL - timeout locking. Locked ID no. of the twistlock Message stored in log and check sensor,
signal has not been received which generated the displayed on Spreader valves and/or
after output to valve warning wiring or
mechanical
reasons
63 WARNING TWL - Locked sensor lost ID no. of the twistlock Message stored in log and check for
during operation. Sensor lost which generated the displayed on Spreader damaged sensors
without command/output when warning and sensor
twistlocks are all locked adjustment or
mechanical
reasons
64 WARNING TWL - timeout unlocking. ID no. of the twistlock Message stored in log and check sensor,
Unlocked signal has not been which generated the displayed on Spreader valves and/or
received after output to valve warning wiring or
mechanical
reasons
65 WARNING TWL - Unocked sensor lost ID no. of the twistlock Message stored in log and check for
during operation. Sensor lost which generated the displayed on Spreader damaged sensors
without command/output when warning and sensor
twistlocks are all unlocked adjustment or
mechanical
reasons
66 WARNING TWL - all landed sensors not ID no. of the twistlock Message stored in log and check for
received after first landed and which generated the displayed on Spreader damaged sensors
timeout. warning and sensor
adjustment or
mechanical
reasons
67 WARNING TWL - landed sensor not ID no. of the twistlock Message stored in log and check for
released when the other sensors which generated the displayed on Spreader damaged sensors
not active and a timer has timed warning and sensor
out adjustment or
mechanical
reasons
68 WARNING TELESCOPE - prox. type. No . Stops the telescope and check for
valid sensor found within displays/stores message damaged sensors
timeout limit after output has and sensor
been activated adjustment or
mechanical
reasons
69 WARNING TELESCOPE - prox. type. ID no. of the sensor Stops the telescope and check for
Wrong sensor in telescoping missing which displays/stores message damaged sensors
sequence reached generated the warning and sensor
adjustment or
mechanical
reasons
70 WARNING TELESCOPE - prox. type. The ID no. of the lost Message stored in log and displayed on
position sensor is lost without an sensor Spreader
output.
71 WARNING TELESCOPE - prox. type. Two ID no.s. of the sensors Message stored in log and check for
different position sensors displayed on Spreader damaged sensors
indicating simultaneously and sensor
adjustment or
mechanical
reasons
72 ERROR Duplicate answers from one The node ID which has System is brought into restart (check
node during boot verification generated the error failsafe mode. address keying)
73 ERROR Wrong boot version in a node The node ID which has System is brought into contact Bromma
generated the error failsafe mode.
74 ERROR No answer when master The node ID which has System is brought into restart
requesting boot version. generated the error failsafe mode.
75 spare 28
76 spare 29
77 spare 30
78 spare 31 .
79 spare 32 .
80 ERROR Wrong node answered request The node ID which has System is brought into restart
from master to check if pc was generated the error failsafe mode.
connected
81 ERROR No answer after master request The node ID which has System is brought into restart, check
to check PC port (RS232) generated the error failsafe mode. connections
82 ERROR Unable to download program . System is brought into retry
failsafe mode.
83 ERROR Unable to download program . System is brought into Check spreader
(checksum failure) failsafe mode. program. If
problems persist
contact Bromma
84 WARNING Onboard realtime clock time .
couldn't be read
85 WARNING Onboard realtime clock time .
couldn't be set
86 INFO minimum system CPU cycle time in ms Message stored in log and displayed on
time. Periodically reported every Spreader
half hour. The counter is reset
after reporting.
87 INFO maximum system CPU cycle time in ms Message stored in log and displayed on
time. Periodically reported every Spreader
half hour. The counter is reset
after reporting.
88 INFO average system CPU cycle time. time in ms Message stored in log and displayed on
Periodically reported every half Spreader
hour. The counter is reset after
reporting.
89 spare 33 .
90 INFO The number of control loops The number of the Message stored in log and displayed on
exceeding 100ms for th last half counter Spreader
hour. The counter is reset after
reporting
91 spare 34 .
92 spare 35 .
93 spare 36 .
94 ERROR No operative system in Node . Systems fails to start contact Bromma
95 ERROR Duplicate answer on The node ID which has System is brought into check adress key
determining Spreader stop set up generated the error failsafe mode.
96 ERROR No answer on Master request for . System is brought into check adress key
"Spreader stop" configuration failsafe mode.
97 INFO Spreader stop has been 0= activated Message stored in log and displayed on
activated/deactivated 1=deactivated Spreader
98 spare 37 .
99 spare 38 .
100 ERROR Spreader program fault . System is brought into
recompile and
failsafe mode. reload spreader
program
101 WARNING CAN message buffer is full The first message type Message stored in log and displayed on
in the buffer Spreader
106 spare 41 .
107 WARNING 10V reference voltage too low Actual voltage *10 Message stored in log and check supplies
displayed on Spreader
108 WARNING 12V internal supply too low Actual voltage *10 Message stored in log and check supplies
displayed on Spreader
109 ERROR Battery voltage too low Actual voltage *10 Message stored in log and check battery
displayed on Spreader
110 ERROR The System failed to lock th I/O . System is brought into restart
on a node during system init. failsafe mode.
111 spare 42
112 spare 43 .
113 spare 44 .
114 INFO System is shutting down .
115 INFO System shutdown has been .
completed
116 spare 45 .
117 spare 46 .
118 INFO Landed override has been .
activated
119 INFO Landed override has been .
deactivated
120 spare 47 .
121 spare 48 .
122 spare 49 .
123 spare 50 .
124 spare 51 .
125 spare 52 .
126 spare 53 .
127 spare 54 .
128 spare 55 .
129 ERROR Spreader program fault or load . System is brought into check and
file has been korrupted failsafe mode. recompile
spreader
program.
Reload. /contact
Bromma
130 ERROR Spreader program fault or load . System is brought into check and
file has been korrupted failsafe mode. recompile
spreader
program.
Reload. /contact
Bromma
131 ERROR Spreader program fault or load . System is brought into check and
file has been korrupted failsafe mode. recompile
spreader
program.
Reload. /contact
Bromma
132 spare 56 .
133 spare 57 .
134 spare 58 .
135 spare 59 .
136 ERROR Spreader program fault or load . System is brought into check and
file has been korrupted failsafe mode. recompile
spreader
program.
Reload. /contact
Bromma
137 spare 60 .
138 spare 61 .
139 spare 62 .
140 WARNING Unknown CAN message The ID type of the Message stored in log and displayed on
received message Spreader
141 INFO CAN messages missed. The count of the Message stored in log and displayed on
Cyclically reported. missed messages Spreader
142 ERROR Two nodes within the system The ID which is System is brought into check and
have the same ID/adress duplicate failsafe mode. correct the
adress key
143 WARNING 10V reference voltage is too Voltage * 10 Message stored in log and check supplies
high displayed on Spreader
144 WARNING 12V internal voltage is too high Voltage * 10 Message stored in log and check supplies
displayed on Spreader
145 WARNING Battery voltage is too high Voltage * 10 Message stored in log and check supplies
displayed on Spreader
146 WARNING User defined Warning. The . Message stored in log and Check specific
user/programmer defines what displayed on Spreader project.
this fault should indicate within
the application program.
147 WARNING User defined Warning. The . Message stored in log and Check specific
user/programmer defines what displayed on Spreader project.
this fault should indicate within
the application program.
148 WARNING User defined Warning. The . Message stored in log and Check specific
user/programmer defines what displayed on Spreader project.
this fault should indicate within
the application program.
149 WARNING User defined Warning. The . Message stored in log and Check specific
user/programmer defines what displayed on Spreader project.
this fault should indicate within
the application program.
150 WARNING User defined Warning. The . Message stored in log and Check specific
user/programmer defines what displayed on Spreader project.
this fault should indicate within
the application program.
151 WARNING User defined Warning. The . Message stored in log and Check specific
user/programmer defines what displayed on Spreader project.
this fault should indicate within
the application program.
152 WARNING User defined Warning. The . Message stored in log and Check specific
user/programmer defines what displayed on Spreader project.
this fault should indicate within
the application program.
153 WARNING User defined Warning. The . Message stored in log and Check specific
user/programmer defines what displayed on Spreader project.
this fault should indicate within
the application program.
154 WARNING User defined Warning. The . Message stored in log and Check specific
user/programmer defines what displayed on Spreader project.
this fault should indicate within
the spreader program.
155 WARNING User defined Warning. The . Message stored in log and Check specific
user/programmer defines what displayed on Spreader project.
this fault should indicate within
the spreader program.
156 spare 63 .
157 spare 64 .
158 spare 65 .
159 spare 66 .
160 spare 67 .
161 WARNING CAN error . Message stored in log and displayed on
Spreader
163 WARNING Power monitor P1 = sensor . Message stored in log and check supplies
supply voltage. Warning 1 = displayed on Spreader
Voltage < 21V
164 ERROR Power monitor P1 = sensor . System is taken down check supplies
supply voltage. ERROR = into idle mode. Ie if the
Voltage below permissive system voltage comes up
voltage of system. again it wakes otherwise
is prepared to shut down
165 WARNING Power monitor P2 = internal . Message stored in log and check supplies
supply voltage. Warning 1 = displayed on Spreader
Voltage < 21V
166 ERROR Power monitor P2 = internal . System is taken down check supplies
logic supply voltage. ERROR = into idle mode. Ie if the
Voltage below permissive system voltage comes up
voltage of system. again it wakes otherwise
is prepared to shut down
167 WARNING Power monitor P3 = PWM . Message stored in log and check supplies
supply voltage. Warning 1 = displayed on Spreader
Voltage < 21V
168 ERROR Power monitor P3 = PWM . System is taken down check supplies
supply voltage. ERROR = into idle mode. Ie if the
Voltage below permissive system voltage comes up
voltage of system. again it wakes otherwise
is prepared to shut down
169 WARNING System failed to read/write to a ID of port: Message stored in log and check supplies
I/O port Digital=0+port_no, displayed on Spreader
Analogue=100+port_n
o, PWM=200+port_no,
encoder=300+port_no.
170 spare 68 .
171 spare 69 .
172 spare 70 .
173 spare 71 .
174 ERROR No answer when on general . Message stored in log and displayed on
information request between Spreader
nodes.
175 INFO TWL - twistlock lock command . Message stored in log and displayed on
received Spreader
176 INFO TWL - twistlock unlock . Message stored in log and displayed on
command received Spreader
177 INFO TWL - twistlock has been . Message stored in log and displayed on
locked Spreader
178 INFO TWL - twistlock has been . Message stored in log and displayed on
unlocked Spreader
179 INFO TELESCOPE - prox. type. . Message stored in log and displayed on
Expand command received Spreader
180 INFO TELESCOPE - prox. type. . Message stored in log and displayed on
Retract command received Spreader
181 INFO TELESCOPE - prox. type. The ID of the position Message stored in log and displayed on
Command to go to a speceific requested Spreader
position has been received
182 INFO TELESCOPE - prox. type. The The ID of the position Message stored in log and displayed on
desired position has been requested Spreader
reached
183 WARNING TELESCOPE - automatic type. 0 = Desired position The telescopic motion is check sensor,
The telescope hasn't reached its' not reached within time stopped until a new pressure,mechan
position within time limit limit. command is given. ics. If necessary
1 = telescope has not Message stored in log and calibrate system.
moved more than 1 cm displayed on Spreader
during 3 seconds.
184 INFO TELESCOPE - automatic type. . Message stored in log and displayed on
expand command received Spreader
185 INFO TELESCOPE - automatic type. . Message stored in log and displayed on
Retract command received Spreader
186 INFO TELESCOPE - automatic type. The ID of the position Message stored in log and displayed on
Command to go to a specific requested Spreader
position received
187 INFO TELESCOPE - automatic type. The ID of the position Message stored in log and displayed on
The desired position reached requested Spreader
188 INFO The year has been set current value (year) Message stored in log and displayed on
Spreader
189 INFO The month has been set current value (month) Message stored in log and displayed on
Spreader
190 INFO The day/date has been set current value (date) Message stored in log and displayed on
Spreader
191 INFO The time of day (hour) has been current value (hour) Message stored in log and displayed on
set Spreader
192 WARNING Nocontact with the master for The ID of the node Message stored in log and check
10s which doesn't have displayed on Spreader connections
contact
195 INFO Download request active . Message stored in log and displayed on
(system boot functionality) Spreader
196 INFO Information request received . Message stored in log and displayed on
(system boot functionality) Spreader
197 INFO set time request received . Message stored in log and displayed on
(system boot functionality) Spreader
198 INFO Boot version request received. . Message stored in log and displayed on
(system boot functionality) Spreader
199 spare 72 .
200 INFO Download flag request received. . Message stored in log and displayed on
(system boot functionality) Spreader
201 spare 73 .
202 spare 74 .
203 spare 75 .
204 spare 76 .
205 INFO Check flash memory request . Message stored in log and displayed on
received. (system boot Spreader
functionality)
206 INFO Restart node request received. . Message stored in log and displayed on
(system boot functionality) Spreader
207 INFO System start init. (system boot . Message stored in log and displayed on
functionality) Spreader
208 INFO System look for downloadflag. . Message stored in log and displayed on
(system boot functionality) Spreader
209 INFO Send datablock request. (system . Message stored in log and displayed on
boot functionality) Spreader
210 INFO Received datablock. (system . Message stored in log and displayed on
boot functionality) Spreader
213 spare 77 .
214 spare 78 .
215 ERROR No answer when waiting for . System is brought into failsafe mode.
present nodes response
216 INFO Inforamtion on present nodes . Message stored in log and displayed on
has been received Spreader
230 ERROR Failed to set up spreader destination of error System is brought into Check spreader
program correctly failsafe mode. program. If
problems persist
contact Bromma
231 ERROR Spreader program download . System is brought into Check spreader
error failsafe mode. program. If
problems persist
contact Bromma
232 ERROR Spreader program download . System is brought into Check spreader
error failsafe mode. program. If
problems persist
contact Bromma
233 INFO Power monitor P1 = sensor . Message stored in log and displayed on
supply voltage. OK Spreader
234 INFO Power monitor P2 = internal . Message stored in log and displayed on
supply voltage. OK Spreader
235 INFO Power monitor P3 = PWM . Message stored in log and displayed on
supply voltage. OK Spreader
236 INFO Reboot (restart) request sent . Message stored in log and displayed on
from master to slaves. Happens Spreader
when slaves are powered on
before master at system start
237 INFO System has been taken down to . Message stored in log and displayed on
idle mode. Ie waiting to wake Spreader
up.
238 Spare 81 .
239 INFO System failed to cancel . Message stored in log and displayed on
shutdown process Spreader
240 INFO No answer when attempting to . Message stored in log and displayed on
cancel shutdown process Spreader
241 INFO System received timeout when . Message stored in log and displayed on
attempting to cancel shutdown Spreader
process
242 INFO System shutdown aborted . Message stored in log and displayed on
Spreader
243 spare 82 .
244 INFO TWL - The spreader has been . Message stored in log and displayed on
landed Spreader
245 INFO TWL - The Spreader has been . Message stored in log and displayed on
totally lifted (not landed) Spreader
246 INFO FLIPPER - flipper up command . Message stored in log and displayed on
received Spreader
247 INFO FLIPPER - flipper down . Message stored in log and displayed on
command received Spreader
248 WARNING Power monitor P1 = sensor . AI can start to flicker. Message stored in
supply voltage. Warning 2 = log and displayed on Spreader
Voltage < 17V
249 WARNING Power monitor P2 = internal . AI can start to flicker. Message stored in
supply voltage. Warning 2 = log and displayed on Spreader
Voltage <17V
250 WARNING Power monitor P3 = PWM . AI can start to flicker. Message stored in
supply voltage. Warning 2 = log and displayed on Spreader
Voltage < 17V
251 ERROR System failed to initialise fielbus . System is brought into failsafe mode.
interface
252 ERROR Duplicate answers when setting . System is brought into failsafe mode.
up fieldbus interface
253 ERROR No answer when configuring . System is brought into failsafe mode.
fieldbus interface
254 WARNING System failed in locking .
fieldbus interface
255 WARNING TWIN195 - twinboxes have ID of the twin box Message stored in log and check
failed to get to their upper failing displayed on Spreader solenoids/mecha
position within time limit nics/sensors
256 WARNING TWIN195 - left hook has failed . Message stored in log and check
to reach its' upper position displayed on Spreader solenoids/mecha
within time limit nics/sensors
257 WARNING TWIN195 - right hook has failed . Message stored in log and check
to reach its' upper position displayed on Spreader solenoids/mecha
within time limit nics/sensors
258 WARNING TWIN195 - twin boxes left . Twin down sequence check
timed out when expanding to stopped. Have to return solenoids/mecha
their attach position. Failed to Spreaer to twin up nics/sensors
reach switch within time limit position. Message stored
in log and displayed on
Spreader
259 WARNING TWIN195 - twin boxes right . Twin down sequence check
timed out when expanding to stopped. Have to return solenoids/mecha
their attach position. Failed to Spreaer to twin up nics/sensors
reach switch within time limit position. Message stored
in log and displayed on
Spreader
260 WARNING TWIN195 - left hook has failed . Message stored in log and check
to reach its' lower position displayed on Spreader solenoids/mecha
(connect) within time limit nics/sensors
261 WARNING TWIN195 - right hook has failed . Message stored in log and check
to reach its' lower position displayed on Spreader solenoids/mecha
(connect) within time limit nics/sensors
262 WARNING TWIN195 - twinboxes have ID of the twin box Message stored in log and check
failed to get to their lower failing displayed on Spreader solenoids/mecha
position within time limit nics/sensors
263 WARNING TWIN195 - twin up sensor lost ID of the twin box Message stored in log and check
unexpectedly. (not due to failing displayed on Spreader solenoids/mecha
output) nics/sensors
264 WARNING TWIN195 - twin up sensor ID of the twin box Message stored in log and check
received when twinboxes are failing displayed on Spreader solenoids/mecha
down nics/sensors
265 WARNING TWIN195 - left hook down . Message stored in log and check
sensor lost unexpectedly. displayed on Spreader solenoids/mecha
nics/sensors
266 WARNING TWIN195 - right hook down . Message stored in log and check
sensor lost unexpectedly. displayed on Spreader solenoids/mecha
nics/sensors
267 WARNING TWIN195 - left hook up sensor . Message stored in log and check
lost unexpectedly. displayed on Spreader solenoids/mecha
nics/sensors
268 WARNING TWIN195 - right hook up sensor . Message stored in log and check
lost unexpectedly. displayed on Spreader solenoids/mecha
nics/sensors
269 ERROR System failed to init. RS485 Node ID System is brought into restart / contact
failsafe mode. Bromma
270 ERROR Duplicate answers in system Node ID System is brought into restart / contact
when setting up RS485 failsafe mode. Bromma
271 ERROR System timed out when trying to . System is brought into restart / contact
configure RS485 failsafe mode. Bromma
272 INFO TELESCOPE - automatic type. . Message stored in log and displayed on
Teach in command received Spreader
280 spare 83 .
281 INFO TWINMPS - teaching a pre- The ID of the position Message stored in log and displayed on
defined position teached Spreader
282 INFO TWINMPS - command to go to The ID of the position Message stored in log and displayed on
a pre-defined position has been requested Spreader
received
284 INFO TWINMPS - A command to The ID of the position Message stored in log and displayed on
return to a log position has been requested Spreader
received
286 INFO TWIN195 - twin up command . Message stored in log and displayed on
has been received Spreader
287 INFO TWIN195 - twin down . Message stored in log and displayed on
command has been received Spreader
288 INFO TWIN195 - twin boxes have . Message stored in log and displayed on
reached their upper position Spreader
289 INFO TWIN195 - twin boxes have . Message stored in log and displayed on
reached their lower position Spreader
290 INFO TTDS - override request . Message stored in log and displayed on
received Spreader
291 INFO TTDS - override request ended . Message stored in log and displayed on
Spreader
292 WARNING Buffer full transferring serial . Message stored in log and displayed on
port info over CAN bus Spreader
293 WARNING No answer when transferring . Message stored in log and displayed on
serial port info over Can bus Spreader
295 spare 84 .
296 spare 85 .
297 spare 86 .
298 ERROR Failed reading spreader System is brought into Check spreader
program. failsafe mode. program. If
problems persist
contact Bromma
299 spare 87
300 spare 88
301 WARNING RS485 not functioning as Depending on type of Message stored in log and displayed on
intended sensor/device Spreader
302 WARNING AnyBus not functioning as Depending on type of Message stored in log and displayed on
intended sensor/device Spreader
306 INFO Spreader properties Number of containers Message stored in log and
353 INFO Present nodes shown in sub code bitwise OR for all included nodes. 12bit Value
357 INFO AnyBus Input data area size size of data area (bytes)
358 INFO AnyBus output data area size size of data area (bytes)
359 ERROR Hardware initialisation failed psu_mon.=1, temp_sens.=2, realtime_clock=3
(system prog.)
372 INFO The Spreader info has been set. The index of the field
which is set.
373 INFO The Spreader info has been set. The value of the field
which is set. The
logged value is in the
range 0-9999. This
range limit has nothing
374 INFO The time of day (minute) has Current value (minute) Message stored in log and displayed on
been set Spreader
378 WARNING Codeloading via anybus failed. node ID that failed to Message stored in log and displayed on
(start sequence) handle start sequence. Spreader
379 WARNING Codeloading via anybus failed. node ID that failed to Message stored in log and displayed on
(download sequence) download. Spreader
380 WARNING Codeloading via anybus failed. node ID that failed to Message stored in log and displayed on
(finish sequence) handle finish sequence. Spreader
381 WARNING Disabeling outputs failed. node ID that failed to Message stored in log and displayed on
disable outputs. Spreader
382 WARNING No answer when attempting to Message stored in log and displayed on
disable outputs. Spreader
383 WARNING Enabeling outputs faild. node ID that failed to Message stored in log and displayed on
enabeling outputs. Spreader
384 WARNING No answer when attempting to Message stored in log and displayed on
enabeling outputs. Spreader
385 INFO AutoTuner stored in NVRAM Regulator index. Message stored in log and displayed on
Spreader
386 INFO Tandem - Teaching a pre- The ID of the position Message stored in log and displayed on
defined position teached Spreader
387 INFO Tandem - A command to store a Message stored in log and displayed on
new value for a log position has Spreader
been received
388 INFO Tandem - command to go to a The ID of the position Message stored in log and displayed on
pre-defined position has been requested Spreader
received
389 INFO Tandem - A command to return The ID of the position Message stored in log and displayed on
to a log position has been requested Spreader
received
390 WARNING Tandem - Cylinder position has The ID of the cylinder Message stored in log and displayed on
changed more than allowed. Spreader
391 INFO Tandem – Both landside and Message stored in log and displayed on
waterside spreaders enabled Spreader
392 INFO Tandem – Landside spreader Message stored in log and displayed on
enabled Spreader
393 INFO Tandem – Waterside spreader Message stored in log and displayed on
enabled Spreader
395 INFO TandemPush – Inner position Message stored in log and displayed on
reached. Spreader
396 INFO TELESCOPE – Impact detected Message stored in log and displayed on
Spreader
398 WARNING TELESCOPE – Sensor value is Message stored in log and displayed on
out of range Spreader
399 INFO TELESCOPE – Bumped out of Message stored in log and displayed on
signal window Spreader
400 INFO TWL – TTDS active Message stored in log and displayed on
Spreader
401 WARNING TWL – Lock attempt with Message stored in log and displayed on
TTDS active Spreader
402 INFO Digital I/O configured on an Node id on where I/O Message stored in log and displayed on
AnybusGateway configured Spreader
403 INFO Analogue I/O configured on an Node id on where I/O Message stored in log and displayed on
AnybusGateway configured Spreader
404 INFO PWM configured on an Node id on where I/O Message stored in log and displayed on
AnybusGateway configured Spreader
405 INFO ASC – Antisway sytem active Message stored in log and displayed on
Spreader
406 INFO ASC – Antisway sytem ready Message stored in log and displayed on
Spreader
407 INFO ASC – Antisway sytem failed Message stored in log and displayed on
Spreaderi
408 spare 88
412 WARNING Auto Tuner – Finished but failed Parameter No. Some parameters could not be calculated.
to calculate some parameters Check sensors etc.
416 INFO CANopen – Node removed from Node number Message stored in log and displayed on
heartbeat list Spreader
417 INFO CANopen – New node added to Node number Message stored in log and displayed on
heart beat list Spreader. See more specific literature
regarding CANopen [DS 301, DS 401]
418 INFO CANopen – Boot message Node number Message stored in log and displayed on
received from node Spreader. See more specific literature
regarding CANopen [DS 301, DS 401]
419 INFO CANopen – Node stopped Node number Message stored in log and displayed on
Spreader. See more specific literature
regarding CANopen [DS 301, DS 401]
420 INFO CANopen – Node in operational Node number Message stored in log and displayed on
state Spreader. See more specific literature
regarding CANopen [DS 301, DS 401]
421 INFO CANopen – Node in Node number Message stored in log and displayed on
preoperational state Spreader. See more specific literature
regarding CANopen [DS 301, DS 401]
422 WARNING CANopen – Heartbeat failed on Node number Message stored in log and displayed on
node Spreader. See more specific literature
regarding CANopen [DS 301, DS 401]
423 ERROR CANopen – To many slaves in Message stored in log and displayed on
use Spreader. Check spreader program.
424 ERROR CANopen – Failed to configure Message stored in log and displayed on
SDO Spreader. Check spreader program.
425 WARNING CANopen – Failed to send SDO Node number Message stored in log and displayed on
Spreader. Check spreader program.
426 WARNING CANopen – Bus off occured Message stored in log and displayed on
Spreader.
427 ERROR CANopen – Failed to change the Message stored in log and displayed on
bitrate on CAN interface Spreader.
428 Spare 89
429 Spare 90
430 Spare 91
431 WARNING CANopen – Emergency object Contents of byte Message stored in log and displayed on
additional byte 1 Spreader. See more specific literature
regarding CANopen [DS 301, DS 401] and
slave user manual
432 WARNING CANopen – Emergency object Contents of byte Message stored in log and displayed on
additional byte 2 Spreader. See more specific literature
regarding CANopen [DS 301, DS 401] and
slave user manual
433 WARNING CANopen – Emergency object Contents of byte Message stored in log and displayed on
additional byte 3 Spreader. See more specific literature
regarding CANopen [DS 301, DS 401] and
slave user manual
434 WARNING CANopen – Emergency object Contents of byte Message stored in log and displayed on
additional byte 4 Spreader. See more specific literature
regarding CANopen [DS 301, DS 401] and
slave user manual
435 WARNING CANopen – Emergency object Contents of byte Message stored in log and displayed on
additional byte 5 Spreader. See more specific literature
regarding CANopen [DS 301, DS 401] and
slave user manual
436 INFO CANopen – Slave OK Node number Message stored in log and displayed on
Spreader. See more specific literature
regarding CANopen [DS 301, DS 401] and
slave user manual
437 WARNING CANopen – Generic error Node number Message stored in log and displayed on
Spreader. See more specific literature
regarding CANopen [DS 301, DS 401] and
slave user manual
438 WARNING CANopen – Current Node number Message stored in log and displayed on
Spreader. See more specific literature
regarding CANopen [DS 301, DS 401]
439 WARNING CANopen – Current, device Node number Message stored in log and displayed on
input side Spreader. See more specific literature
regarding CANopen [DS 301, DS 401]
440 WARNING CANopen – Current, inside Node number Message stored in log and displayed on
device Spreader. See more specific literature
regarding CANopen [DS 301, DS 401]
441 WARNING CANopen – Current, device Node number Message stored in log and displayed on
output side Spreader. See more specific literature
regarding CANopen [DS 301, DS 401]
442 WARNING CANopen - Voltage Node number Message stored in log and displayed on
Spreader. See more specific literature
regarding CANopen [DS 301, DS 401]
443 WARNING CANopen – Mains voltage Node number Message stored in log and displayed on
Spreader. See more specific literature
regarding CANopen [DS 301, DS 401]
444 WARNING CANopen - Voltage inside Node number Message stored in log and displayed on
Spreader. See more specific literature
regarding CANopen [DS 301, DS 401]
445 WARNING CANopen – Voltage output Node number Message stored in log and displayed on
Spreader. See more specific literature
regarding CANopen [DS 301, DS 401]
446 WARNING CANopen - Temperature Node number Message stored in log and displayed on
Spreader. See more specific literature
regarding CANopen [DS 301, DS 401]
447 WARNING CANopen – Temperature Node number Message stored in log and displayed on
ambient Spreader. See more specific literature
regarding CANopen [DS 301, DS 401]
448 WARNING CANopen – Temperature device Node number Message stored in log and displayed on
Spreader. See more specific literature
regarding CANopen [DS 301, DS 401]
449 WARNING CANopen – Hardware device Node number Message stored in log and displayed on
Spreader. See more specific literature
regarding CANopen [DS 301, DS 401]
450 WARNING CANopen – Software device Node number Message stored in log and displayed on
Spreader. See more specific literature
regarding CANopen [DS 301, DS 401]
451 WARNING CANopen – Software inside Node number Message stored in log and displayed on
Spreader. See more specific literature
regarding CANopen [DS 301, DS 401]
452 WARNING CANopen – software user Node number Message stored in log and displayed on
Spreader. See more specific literature
regarding CANopen [DS 301, DS 401]
453 WARNING CANopen – Data set Node number Message stored in log and displayed on
Spreader. See more specific literature
regarding CANopen [DS 301, DS 401]
454 WARNING CANopen – Additional module Node number Message stored in log and displayed on
Spreader. See more specific literature
regarding CANopen [DS 301, DS 401]
455 WARNING CANopen - Monitoring Node number Message stored in log and displayed on
Spreader. See more specific literature
regarding CANopen [DS 301, DS 401]
456 WARNING CANopen – CAN overrun Node number Message stored in log and displayed on
Spreader. See more specific literature
regarding CANopen [DS 301, DS 401]
457 WARNING CANopen – CAN error passive Node number Message stored in log and displayed on
Spreader. See more specific literature
regarding CANopen [DS 301, DS 401]
458 WARNING CANopen – Lifeguard or Node number Message stored in log and displayed on
heartbeat Spreader. See more specific literature
regarding CANopen [DS 301, DS 401]
459 WARNING CANopen – Recover from bus Node number Message stored in log and displayed on
off Spreader. See more specific literature
regarding CANopen [DS 301, DS 401]
460 WARNING CANopen - Transmit COB id Node number Message stored in log and displayed on
Spreader. See more specific literature
regarding CANopen [DS 301, DS 401]
461 WARNING CANopen – General Node number Message stored in log and displayed on
communication Spreader. See more specific literature
regarding CANopen [DS 301, DS 401]
462 WARNING CANopen – General protocol Node number Message stored in log and displayed on
Spreader. See more specific literature
regarding CANopen [DS 301, DS 401]
463 WARNING CANopen – PDO not processed Node number Message stored in log and displayed on
Spreader. See more specific literature
regarding CANopen [DS 301, DS 401]
464 WARNING CANopen – PDO length Node number Message stored in log and displayed on
exceeded Spreader. See more specific literature
regarding CANopen [DS 301, DS 401]
465 WARNING CANopen – External error Node number Message stored in log and displayed on
Spreader. See more specific literature
regarding CANopen [DS 301, DS 401]
466 WARNING CANopen – Additional Node number Message stored in log and displayed on
functions Spreader. See more specific literature
regarding CANopen [DS 301, DS 401]
467 WARNING CANopen – Device specific Node number Message stored in log and displayed on
Spreader. See more specific literature
regarding CANopen [DS 301, DS 401] and
slave user manual
468 WARNING CANopen – Node missing Node number Check CAN connections and spreader
program.
469 INFO CANopen – Node id changed Changed to node Message stored in log and displayed on
number Spreader.
470 WARNING CANopen – Node id chage Node number Message stored in log and displayed on
failed Spreader.
1 General ......................................................................................................................................................................... 3
1.1 OVERVIEW ............................................................................................................................................................... 3
1.2 DICTIONARY AND ABBREVIATIONS .......................................................................................................................... 3
1.3 DOCUMENT LAYOUT ................................................................................................................................................ 3
2 Introduction ................................................................................................................................................................. 4
2.1 GENERAL ................................................................................................................................................................. 4
2.2 THE NODES .............................................................................................................................................................. 5
3 Software........................................................................................................................................................................ 5
3.1 BOOT PROGRAM ...................................................................................................................................................... 5
3.2 SYSTEM PROGRAM ................................................................................................................................................... 5
3.3 SPREADER PROGRAM ............................................................................................................................................... 6
4 Hardware Overview .................................................................................................................................................... 6
4.1 BCAN - STATUS LEDS ........................................................................................................................................... 6
4.2 THE ANY BUS CARD ................................................................................................................................................. 6
4.3 POWER CONNECTOR ................................................................................................................................................. 6
4.4 BCAN CONNECTOR ................................................................................................................................................. 7
4.5 NODE ADDRESS KEY SWITCHES ................................................................................................................................ 7
4.6 SERIAL PORT CONNECTOR ........................................................................................................................................ 7
4.7 GROUND CONNECTION ............................................................................................................................................. 7
4.8 FIELD BUS CONNECTIONS. ....................................................................................................................................... 8
4.8.1 Mapping of I/O .............................................................................................................................................. 8
4.9 FAULT F INDING TABLE........................................................................................................................................... 10
5 Software tools............................................................................................................................................................. 10
5.1 OVERVIEW ............................................................................................................................................................. 10
5.2 ABE....................................................................................................................................................................... 10
5.3 BMS ...................................................................................................................................................................... 10
6 Miscellaneous ............................................................................................................................................................. 11
6.1 DATA SHEET........................................................................................................................................................... 11
6.2 DIMENSIONS .......................................................................................................................................................... 12
7 Appendix A (Error messages)................................................................................................................................... 13
1 General
1.1 Overview
This document serves as a user manual and shall be used by the those installing and using the Bromma SCS2 Anybus
Gateway. Software as well as hardware routines and descriptions are covered in this document.
2 Introduction
The core of the Bromma Smart Spreader is the Spreader Communications System (SCS2). In 1991 when Bromma decided
to develop a new and highly advanced communications system a close look at the available bus systems revealed a
number of shortcomings, such as temperature range, EMC (Electro Magnetic Compatibility) protection and mechanical
roughness.
Bromma therefore decided to design a bus system that met the demands made on an electronic system for a tough
Spreader application. We decided to develop a modular programmable controller, with a heavy-duty field bus interface
that complies with European and international standards for control equipment in this area. The SCS2 solution is a single
control product that can be used as I/O, as a PLC, and as distributed control for up to 528 I/O points. SCS2 nodes are
simple to install. You can connect up to 11 devices using just a single pair of wires. With its modular and scaleable
architecture, intuitive features and unparalleled ease of use, it will help save crane builders and end users time and money.
2.1 General
As a universal I/O, SCS2 gives you the freedom to connect to a wide variety of host controllers, including PLC's, DCS
and PC-based control systems by way of DeviceNet, Profibus-DP. SCS2 can be networked as a slave to Profibus-DP or
you can choose a DeviceNet master module for easy third-party integration. Designed by Bromma engineers for reliable
performance in the particularly challenging environment of container handling the system corporate four basic elements:
Crane Node A device directly interfacing with the crane’s control systems, computer and
monitoring screens, providing an optional serial bus interface for
programming or diagnostic communications, as well as an interface to the
spreader node.
Crane-Spreader Communications Link A two-wire conventional cable CAN communications between the crane
control system and the spreader.
Spreader Node A device that interfaces directly with the spreader’s sensorsand actuators.
One of the Spreader nodes normally acts as Master.
Sensors and Switches Conventional sensors, switches, and actuators on the spreader.
The system is divided into several hardware blocks called nodes. The nodes are located on the spreader and in the crane.
The nodes are connected to each other via a CAN network, see figure 1. The number of nodes required is based on the
number of I/O needed.
The only difference is their identity, id. Depending on their location the nodes have different ids. They are numbered
from 0 to 11 where:
Crane PLC
Crane field bus
Anybus Gateway A1
Spreader
Figure 1. The figure shows SCS2 connected to the spreader and the crane via I/O. The nodes are also connected internally
via a CAN network.
The SCS2 is built up of several nodes co-operating in the system. Each node has a specific role, either slave or master.
There must be only one master node in the system and the rest are slaves.
The master node makes all the calculations and decisions. The slave nodes act as remote I/O to the master.
3 Software
The SCS2 software consists of three types of programs; Boot Program, System Program and Spreader Program.
4 Hardware Overview
Figure2 is a SCS2 Anybus Gateway node equiped with a Profibus slave card. The different parts are explained in the
following chapter. This view shows a Profibus card, this can naturally be exchanged for any other available fieldbus.
AnyBus
(Profibus) card
Status LEDs
status LEDS
Figure 2. The SCS2 Anybus Gateway node equiped with a Profibus slave card.
The size of the data exchange area between the SCS2 and the Anybus card is configurable up to 64 bytes in and 64 bytes
out. The configuration is done via HMS standard files. This interface must be configured in the same way for both the
Master and the SCS 2 slave for the bus to work correctly. For each project a document has to be sent to the customer
describing the used parts of the interface. When referring to in/out we view it from the SCS2 side, hence input for the
SCS2 is an output from the master in the crane. Hence the crane PLC and the AnyBus card must have corresponding
addresses and the nymber of bytes configured for input/output data have to be the same on both sides of the
communication link i.e. the crane PLC and the SCS 2.
OUT IN
Byte 0-63 Byte 0-63
Project Project
specific specific
outputs inputs
Output Segment
In the output segment it possible to use a number of bytes for diagnostic information in the form codes. The code sent
will be equivalent with the code displayed in the onboard display, hence there will be three levels of this code INFO,
WARNING, ERROR. Apart from the code and the byte for indicating the type of code a counter will be incremented
each time a code is sent. The counter is a 16bit value and therefore will begin from 0 if the counter overflows. The value
of this counter will be sent each time that a new diagnostic message is transmitted.
The remaining bytes for output will be assigned the interface with the crane and will vary on each project. The
assignments here are discrete outputs from the Spreader and current values (pressure etc.) from devices on the Spreader.
These assignments shall be are documented in the electrical documentation of the project.
Input Segment
The entire range of the input area is configurable per project. The assignments here are discrete inputs to the Spreader and
set point values for the Spreader. These assignments shall be documented in the electrical documentation of the project.
Power Supply
The node won’t start. The power LED Measure the main supply. The voltage The power LED should be on.
is off. should exceed 10V DC and be less
than 30V DC.
RS-232
BMS system can not communicate Probe TxD and RxD lines with Data lines should show square waves
with the node. oscilloscope while trying to between –10V to +10V relative to
communicate. Ensure that connection GND pin.
cables aren’t damaged.
CAN
The node can not communicate with Probe bus lines with oscilloscope. Check that CAN high and CAN low
the other nodes. CAN high should show square waves are not mixed up.
pointing downwards and CAN low
should be showing square waves
pointing upwards.
Node ID
The unit stops at start-up. Check selected node ID. This can indicate that the node has
wrong id strapped telling the node to
participate in the system with wrong
role.
5 Software tools
5.1 Overview
There are some related tools to the SCS2, which support it in different ways. A brief description of these tools is given
below.
5.2 ABE
ABE (Application Builder Environment) is a tool for developing and configuring the spreader program, which controls
the logic of the spreader. ABE generates a load file. For more detailed see the separate manual.
5.3 BMS
BMS ultra light (Bromma Monitoring System ultra light) is a tool for monitoring events and reading status of I/O in the
SCS2. BMS can also be used to download new programs to the SCS2. For more detailed see the separate manual.
6 Miscellaneous
6.2 Dimensions
Figure 3. The SCS2 Anybus Gateway node equiped with a Profibus slave card. All dimensions are in mm.
HYDRAULIC PUMP MOTOR STOPPED