26.03.2013 Views

Wire Rope Hoists _ Operating and Maintenance ... - STAHL-POLSKA

Wire Rope Hoists _ Operating and Maintenance ... - STAHL-POLSKA

Wire Rope Hoists _ Operating and Maintenance ... - STAHL-POLSKA

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

3 Installation<br />

3.1 Stationary wire rope hoist<br />

M T (<strong>Rope</strong> drum torque)<br />

SH 3: M T = 0.5 x F x 126 mm<br />

SH 4: M T = 0.5 x F x 167 mm<br />

SH 5: M T = 0.5 x F x 219 mm<br />

SH 6 : M T = 0.5 x F x 356 mm<br />

8<br />

St<strong>and</strong>ard reevings<br />

Possible fixing positions <strong>and</strong> rope lead-off<br />

Feet "at bottom," <strong>and</strong> "at top" are possible for designs with bottom hook block (rope<br />

lead-off vertically downwards).<br />

The SH wire rope hoist with 1/1 <strong>and</strong> 2/2 rope lead-off can be installed in various positions.<br />

The fleet angles possible can be seen from the sketches on pages 9 <strong>and</strong> 10.<br />

If possible, install the hoist in the preferred installation position ***, see page 9.<br />

Use the fixing elements specified, see sketches <strong>and</strong> tables.<br />

Take care that no distortion arises from unevenness, etc.<br />

(see sketch, max. 0.5°, max. 2mm)<br />

The customer's substructure must take up the torque M T from the rope drum. It<br />

must therefore be torsion resistant.<br />

If the rope lead-off is not vertical, the shearing forces arising must be taken up by a<br />

support bar.<br />

For tightening torques, see page 63<br />

1/1 2/1 4/1 2/2-1 4/2-1<br />

8/2-1<br />

3.1.1 Feet at bottom<br />

SH 3 SH 4 SH 5 SH6 / SHR6 SH 6<br />

2/1, 4/1, 4/2-1 1/1<br />

3.1.2 Feet at top<br />

SH3 SH4 SH5 SH6 1/1<br />

*1 Tractive force at rope drum<br />

*2 Lock washer (Schnorr)<br />

10.08<br />

BASH_02_1.FM

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!