sinumerik fm-nc installation and start-up guide 07-00

SINUMERIK FM-NC

Installation and Start-Up Guide 07.2000 Edition

Manufacturer/Service Documentation

Valid for:

Control Software VersionSINUMERIK FM–NC 3

07.2000 Edition

SINUMERIK FM–NC

Installation and Start-up Guide


Preface, Contents

General Preparations 1

Design 2

Settings, MPI Nodes 3

EMC and ESD Measures 4

Power On and Power-Up 5

Parameterization of the FM–NC 6

PLC 7

Alarm and Message Texts 8

Axis and Spindle Dry Run 9

Drive Optimization 10

Data Saving 11

Software/Hardware Replacement 12

Miscellaneous 13

Abbreviations A

References B

General Index

SINUMERIK documentation

Printing history

Brief details of this edition and previous editions are listed below.

The status of each edition is shown by the code in the ”Remarks” column.

Status code in the ”Remarks” column:

A New documentation.. . . . . B Unrevised reprint with new Order No.. . . . . C Revised edition with new status. . . . . .

If factual changes have been made on the page since the last edition, this is indicated by a new edition coding in the header on that page.

Edition Order No. Remarks07.94 6FC5 297-0AB00-0BP0 A06.95 6FC5 297-2AB00-0BP0 C04.96 6FC5 297-3AB00-0BP0 C07.2000 6FC5 297-3AB00-0BP1 C

This manual is included in the documentation available on CD-ROM (DOCONCD)Edition Order No. Remarks09.01 6FC5 298-6CA00-0BG1 C

TrademarksSIMATIC�, SIMATIC HMI�, SIMATIC NET�, SIROTEC�, SINUMERIK� und SIMODRIVE� are trademarks ofSiemens. Other product names used in this documentation may be trademarks which, if used by thirdparties, could infringe the rights of their owners.

Further information is available on the Internet under:http://www.ad.siemens.de/sinumerik

This publication was produced with Interleaf V 7

The reproduction, transmission or use of this document or itscontents is not permitted without express written authority. Offenderswill be liable for damages. All rights, including those created by patentgrant or registration of a utility model or design, are reserved.

Siemens AG 1994 – 2000. All rights reserved.

Other functions not described in this documentation might beexecutable in the control. However, no claim can be made regardingthe availability of these functions when the equipment is first suppliedor for service cases.

We have checked that the contents of this document correspond tothe hardware and software described. Nonetheless, differences mightexist and therefore we cannot guarantee that they are completelyidentical. The information contained in this document is, however,reviewed regularly and any necessary changes will be included in thenext edition. We welcome suggestions for improvement.

Subject to changes without prior notice.

Siemens-AktiengesellschaftOrder No. 6FC5 297-3AB00-0BP1Printed in the Federal Republic of Germany

v Siemens AG 2000 All Rights ReservedSINUMERIK FM-NC Installation and Start–Up Guide (IAF) – 07.2000 Edition

Preface

The SINUMERIK documentation is organized in 3 parts:

� General Documentation

� User Documentation

� Manufacturer/Service Documentation

The Installation and Start-Up Guide provides the information required forstart-up and servicing.

This publication describes the structure of the control system and the interfacesof the various components. Also, the procedure for starting up the system isdescribed and all data, signals, PLC blocks and alarms relevant to the start–upare listed.

Information on the individual functions, the assignments of the functions and theperformance data for the various components can be found in more specificdocumentation (manuals, description of functions, etc.).

Separate descriptions are available for user-oriented activities such as writingpart programs and operating the control.

There are also separate descriptions for work to be performed by the machinemanufacturer such as configuring, design, programming of the PLC.

Note

This guide contains a description of standard start-up and initial start-up (up toand including axis or spindle). The start-up of other functions can be found inthe appropriate function description.

To help the reader, this Guide offers not only a list of contents but also the follo-wing appendices:

1. List of Abbreviations

2. List of References

3. Index

Notes for thereader

Objective

Standard scope

Search aids

07.2000

vi Siemens AG 2000 All Rights Reserved

SINUMERIK FM-NC Installation and Start–Up Guide (IAF) – 07.2000 Edition

!Important

This Installation and Start-Up Guide is valid forSINUMERIK FM–NC, Software Version 3, with MMC 100/100.2/102 or MMC 103

The SINUMERIK FM–NC alarms are listed and described in the

References: /DA/, Diagnostics Guide

Further help for start-up and in tracing errors is given in the

References: /FB/, D1, “Diagnostics Tools”

The Installation and Start-up Guide includes:

� Description of the overall design and the interfaces of the variouscomponents in order to provide an overview of how the individual compo-nents interact.

� The procedure for standard start-up, initial start-up and start-up of a stan-dard machine and also data saving.

The Installation and Start-Up Guide includes information for:

� the person starting up the installation after it has been configured anderected,

� the service engineer for checking and interpreting the status displays andalarms.

The following notes have a special significance and are used in thedocumentation:

Note

This symbol appears in the documentation whenever background informationis provided.

!Important

This symbol appears in the documentation whenever attention has to be paidto something of particular importance.

Contents

Target groups

Notes

Preface

07.2000

vii Siemens AG 2000 All Rights ReservedSINUMERIK FM-NC Installation and Start–Up Guide (IAF) – 07.2000 Edition

The following warning notes with different level of severity are used in this publi-cation:

!Danger

This symbol appears whenever death, severe bodily injury or substantialmaterial damage will occur if the appropriate precautions are not taken.

!Caution

This symbol appears whenever minor bodily injury or material damage canoccur if the appropriate precautions are not taken.

!Warning

This symbol appears whenever death, severe bodily injury or substantialmaterial damage can occur if the appropriate precautions are not taken.

Technical notes

IBM is registered trademark of International Business Corporation.MS–DOS and WINDOWS� is a registered trademark of MicrosoftCorporation.

The following notation and abbreviations apply in this documentation:

� PLC interface signals –> IS “Signal name” (Signal data)Examples:

– IS “MMC–CPU1 Ready” (DB10, DBX108.2) i.e. the signal is stored indata block 10, data byte 108, bit 2.

– IS “Feed/spindle override” (DB31–34, DBB0) i.e. the signals are locatedfor specific axes/-spindles in datablocks 31 to 34, datablock byte 0.

� Machine data –> MD: MD_NAME (designation)

� Setting data –> SD: SD_NAME (designation)

� The symbol “�” means “corresponds to”.

After altering data (e.g. machine data) attention must also be paid to the ques-tion as to when the alterations will become effective (e.g. after Power ON orIMMEDIATE).

Warning notes

Trademarks

Notation

Effectiveness ofalterations

Preface

07.2000

viii Siemens AG 2000 All Rights Reserved


If it is necessary to perform measuring or testing work on the active device, thestipulations and instructions for complying with the accident preventionspecifications VBG 4.0 must be observed, in particular § 8 “Permissibledeviations when working on active parts”. Other, similar specifications willcertainly apply in countries outside of Germany. Suitable electrical tools must beused.

!Warning

� Repair on equipment supplied by our company may only be carried out bySIEMENS Service or repair stations authorized by SIEMENS. Any defec-tive parts or components are only to be replaced by parts contained in therelevant spare parts list.

� Disconnect the power supply before opening the equipment.

� Emergency Stop facilities according to EN 60204 IEC 204 (VDE 0113 Part1) must remain operative in all operating modes of the automation equip-ment. Any disengaging of the Emergency Stop facility must not lead to un-controlled or undefined restart.

� Wherever faults occurring in the automation equipment can lead tosubstantial material damage or even grievious bodily injury, i.e. arepotentially dangerous faults, additional external precautions must be takenor facilities must be provided ensuring or enforcing safe operation evenwhen a fault occurs (e.g. independent limit switches, mechanical interlocksetc.).

!Caution

� Connecting and signal lines must be installed so as to safely preventinductive and capacitive interferences from affecting automation functions.

Further notes

Preface

07.2000

ix Siemens AG 2000 All Rights ReservedSINUMERIK FM-NC Installation and Start–Up Guide (IAF) – 07.2000 Edition

Electrostatically Sensitive Devices

!Important

Handling of electrostatically sensitive devices (ESD)

� When handling electrostatically sensitive components make sure theoperator, workplace and packing material are properly earthed.

� Generally, electrostatically sensitive components must not be touched unless work has to be carried out on them. Always handle printed circuitboards without touching pins or printed conductors.

� Touch components of the equipment only if

– you are permanently earthed by means of an antistatic chain

– you are wearing ESD boots or ESD boots with earthing strips inconjunction with an ESD flooring.

� Modules may be set down only on electrically conducting surfaces (tablewith ESD top, conductive ESD foam plastic, ESD packing bags, ESD trans-port containers).

� Keep modules away from visual display units, monitors, or TV sets (mini-mum distance from screen > 10 cm).

� Modules must not be allowed to come into contact with electricallyinsulating materials such as plastic film, insulating table tops or clothingmade of synthetic fibers.

� Measurements on modules are allowed only if

– the measuring instrument is properly earthed (e.g. equipment groundingconductor) or

– before measuring with a potential-free instrument, the probe is brieflydischarged (e.g. touch the bare, earthed metal control housing).

The SINUMERIK FM-NC may be used only for the applications provided for inthe Installation and Start-Up Guide and only in conjunction with non-Siemensequipment and components recommended or authorized by Siemens.

Should you encounter problems or have questions on reading the Installationand Start-Up Guide, please contact the Siemens office specified on the replysheet provided at the end of this manual.

If you have any queries, please contact:

� SINUMERIK Hotline for FM-NC and FM354:Tel.: +49 180 525 8008Fax.: +49 180 525 8009Fax.: +49 911 895 7002 or

� SIMATIC Hotline for PLC-CPU and AS300 modules:Tel.: +49 911 895 7000.

�

ESD notes

Use for intendedpurpose only

Contact addresses

Hotline

Preface

07.2000

x Siemens AG 2000 All Rights Reserved


Preface

xi Siemens AG 2000 All Rights ReservedSINUMERIK FM-NC Installation and Start–Up Guide (IAF) – 07.2000 Edition

Contents

1 General Preparations 1-15. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.1 General requirements 1-16. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.2 Requirements for start-up 1-18. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2 Design 2-23. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.1 Integration of FM-NC module (NCU 570.2) in the S7-300 PLC 2-24. . . . .

2.2 Overviews of connections 2-26. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.2.1 Overview of connections for FM-NC (NCU 570.2) 2-26. . . . . . . . . . . . . . . . 2.2.2 Overview of connections for FM 354 2-32. . . . . . . . . . . . . . . . . . . . . . . . . . .

2.3 Power supply 2-36. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.3.1 Power supply requirements of entire S7-300 system 2-36. . . . . . . . . . . . . . 2.3.2 FM-NC power supply 2-36. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.3.3 FM 354 power supply 2-37. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.3.4 Module power supply options 2-37. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.3.5 Back-up battery service 2-38. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.4 Interfaces of operator panel with MMC 2-40. . . . . . . . . . . . . . . . . . . . . . . . .

2.5 Machine control panel interfaces 2-46. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.5.1 Interfaces of the standard machine control panel 2-46. . . . . . . . . . . . . . . . . 2.5.2 Interfaces of machine control panel 2-48. . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.5.3 2nd machine control panel 2-49. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.6 Interface for customer operator panel 2-50. . . . . . . . . . . . . . . . . . . . . . . . . . .

2.7 Hand-held unit (HHU) 2-51. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.8 COROS OP 27 operator interface 2-52. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3 Settings, MPI Nodes 3-53. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.1 MPI networking rules 3-54. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.2 Standard configuration 3-55. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.3 Nonstandard configuration 3-58. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.4 Example of an MCP and HHU configuration on MPI bus with STEP7 V5x 3-60. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.5 Example of distribution of MPI addresses 3-66. . . . . . . . . . . . . . . . . . . . . . .

4 EMC and ESD Measures 4-69. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4.1 Measures to suppress interference 4-70. . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4.2 Measures to protect ESD-sensitive components 4-71. . . . . . . . . . . . . . . . .

07.2000

xii Siemens AG 2000 All Rights Reserved


5 Power On and Power-Up 5-73. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

5.1 Start-up sequence 5-74. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

5.2 Power on 5-74. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

5.3 Booting of system software 5-75. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.3.1 Booting of entire system 5-76. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.3.2 Booting of FM-NC (NCU 570.2) 5-78. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.3.3 Booting of PLC-CPU 5-79. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.3.4 MMC102/103 BIOS setup 5-80. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.3.5 Booting of MMC 100/102 5-81. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.3.6 Booting of machine control panel (MCP) 5-81. . . . . . . . . . . . . . . . . . . . . . . .

6 Parameterization of the FM-NC 6-83. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

6.1 Machine and setting data 6-84. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

6.2 Handling machine and setting data 6-85. . . . . . . . . . . . . . . . . . . . . . . . . . . . .

6.3 Protection level strategy 6-87. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

6.4 Operator control functions for start-up 6-89. . . . . . . . . . . . . . . . . . . . . . . . . .

6.5 Initialization of system 6-91. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

6.6 SINUMERIK FM–NC configuration/system data 6-92. . . . . . . . . . . . . . . . . . 6.6.1 General configuration 6-92. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

6.7 Memory configuration 6-96. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

6.8 Sequence of operations for initial start-up 6-100. . . . . . . . . . . . . . . . . . . . . . .

6.9 Sequence of operations for starting up a series machine 6-104. . . . . . . . . .

6.10 Axes and spindles 6-105. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.10.1 Axis configuration 6-105. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.10.2 Axis data 6-109. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.10.3 Encoder matching (axis) 6-111. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.10.4 Setpoint routing (axis) 6-120. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.10.5 Velocity/speed matching 6-121. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.10.6 Monitoring functions (axis) 6-129. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.10.7 Reference point approach 6-135. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.10.8 Reference point approach for stepper motors 6-138. . . . . . . . . . . . . . . . . . . . 6.10.9 Extension to 5th axis 6-139. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.10.10 Basic settings for operator panel 6-140. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.10.11 Configuration and machine data of local P bus of FM-NC 6-141. . . . . . . . . . 6.10.12 Spindle data 6-143. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.10.13 Spindle configuration 6-145. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.10.14 Encoder matching (spindles) 6-145. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.10.15 Speeds and setpoint adjustment (spindles) 6-147. . . . . . . . . . . . . . . . . . . . . . 6.10.16 Spindle positioning 6-149. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.10.17 Spindle synchronization 6-150. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.10.18 Monitoring functions (spindles) 6-151. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

6.11 Start-up of functions 6-153. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Contents

07.2000

xiii Siemens AG 2000 All Rights ReservedSINUMERIK FM-NC Installation and Start–Up Guide (IAF) – 07.2000 Edition

7 PLC 7-155. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

7.1 PLC applications 7-156. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

7.2 Mode switch on CPU 7-160. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

7.3 CPU: Status and error displays 7-162. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

7.4 CPU: MPI Multi-point interface 7-163. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

7.5 CPU operating status for FM-NC start-up 7-163. . . . . . . . . . . . . . . . . . . . . . .

7.6 Overview of organization blocks, function blocks, DBs 7-165. . . . . . . . . . . .

7.7 Interface signals 7-165. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

8 Alarm and Message Texts 8-167. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

8.1 Alarm text files for MMC100/100.2 8-168. . . . . . . . . . . . . . . . . . . . . . . . . . . . .

8.2 Alarm text files for MMC 102/103 8-170. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

8.3 Syntax for alarm text files of cycles and PLC alarms 8-173. . . . . . . . . . . . . .

9 Axis and Spindle Dry Run 9-177. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

9.1 Preconditions 9-178. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

9.2 Testing the axis 9-179. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

9.3 Testing the spindle 9-180. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

10 Drive Optimization 10-183. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

10.1 General principles of optimization 10-184. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

10.2 Aim of optimization procedure 10-184. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

10.3 Checking the speed control loop 10-185. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

11 Data Saving 11-187. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

11.1 General 11-188. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

11.2 Data saving via MMC 100/100.2 11-189. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

11.3 Data saving via MMC 102/103 11-193. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

11.4 Saving data on a PCMCIA memory card 11-194. . . . . . . . . . . . . . . . . . . . . . . .

11.5 Data saving from MMC 102/103 11-195. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.5.1 Data saving from MMC 102 11-195. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.5.2 Data saving from MMC 103 11-196. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

11.6 Line checksums and MD numbers in MD files 11-199. . . . . . . . . . . . . . . . . . . 11.6.1 Line checksums 11-199. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.6.2 Machine data numbers 11-200. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.6.3 Abortion of MD import 11-200. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

11.7 Notes on loading and saving machine data 11-202. . . . . . . . . . . . . . . . . . . . . .

11.8 Machine/setting data 11-204. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Contents

07.2000

xiv Siemens AG 2000 All Rights Reserved


12 Software/Hardware Replacement 12-205. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

12.1 Upgrading FM-NC software (firmware update) 12-206. . . . . . . . . . . . . . . . . . . 12.1.1 Procedure for updating firmware on FM-NC 12-206. . . . . . . . . . . . . . . . . . . . . 12.1.2 Procedure for updating firmware on FM354 12-207. . . . . . . . . . . . . . . . . . . . .

12.2 Upgrading MMC 100/100.2 software 12-208. . . . . . . . . . . . . . . . . . . . . . . . . . . 12.2.1 Installation of MMC 100/100.2 system diskette(s) 12-210. . . . . . . . . . . . . . . . 12.2.2 Installation of MMC100/100.2 application diskette 12-216. . . . . . . . . . . . . . . . 12.2.3 Installation of MMC 100.2 software via PCMCIA 12-221. . . . . . . . . . . . . . . . .

12.3 Upgrading MMC 102/103 software 12-225. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12.3.1 Installation via MMC 102/103 floppy drive 12-225. . . . . . . . . . . . . . . . . . . . . . . 12.3.2 Installation via PC/PG to MMC102/103 12-226. . . . . . . . . . . . . . . . . . . . . . . . .

12.4 Hardware replacement 12-230. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12.4.1 Special notes for CPU318 12-230. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12.4.2 CPU hardware replacement 12-233. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12.4.3 FM-NC hardware replacement 12-233. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

12.5 Battery replacement 12-234. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

13 Miscellaneous 13-235. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

13.1 “Tool Box” software package 13-236. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13.1.1 Contents of tool box 13-236. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13.1.2 Application of tool box 13-237. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

13.2 Assessing machine data via part program 13-238. . . . . . . . . . . . . . . . . . . . . . .

13.3 O & M for FM-NC with OP 27 13-239. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

A Abbreviations A-243. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

B References B-249. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

C General Index Index-261. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Contents

1

1-15 Siemens AG 2000 All Rights ReservedSINUMERIK FM-NC Installation and Start–Up Guide (IAF) – 07.2000 Edition

General Preparations

1.1 General requirements 1-16. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.2 Requirements for start-up 1-18. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1

1

07.2000

1-16 Siemens AG 2000 All Rights Reserved


1.1 General requirements

This Installation and Start-Up Guide describes the procedure for starting up thebasic control functions. Please refer to Descriptions of Functions/Manuals (see“Documentation requirements”) for further reference material relating to specialNCK, MMC, PLC or drive functions.

The following software is required to start up the SINUMERIK FM-NC:

1. PCIN for transmission of data between PC/PG and MMCOrder No. 6FX2 060–4AA00–2XB0 (German, English, French). Order from: WK Fürth

2. SIMATIC STEP7

3. Tool Box for SINUMERIK FM-NCOrder No. 6FC5 252–0AX20–0AB0Supplied on 3.5” diskettes with:

– Basic PLC program

– Sample machine data sets

– NC variable selector

– OP27 sample configuration

4. Software for generating user applications and transferring them to MMC:

– MMC 100: System diskette and applications diskette

– MMC 100.2: 2 system diskettes and 1 application diskette.

The following equipment and accessories are required to start up theSINUMERIK FM-NC:

1. PC/PG with MPI interface (e.g. PG 740)

2. MPI cable

3. V24 cable with 9-pin connector (socket)

Introduction

Softwarerequirements

Equipment andaccessoryrequirements


1

07.2000


The following documentation is required to start up the SINUMERIK FM-NC:

1. Configuring, Manuals NCU 570 and FM 354 /PHF/Order No.: 6FC5 297-3AC00-0BP0

2. Operator Components Manual /BH/Order No.: 6FC5 297-6AA50-0BP0

3. Description of Functions, Basic Machine (Part 1) /FB1/Order No.: 6FC5 297-6AC20-0BP0

4. Installation and start-up documentation and equipment for starting up analogor stepper drives (according to manufacturer’s specifications).

5. Lists /LIS/Order No.: 6FC5 297-6AB70-0BP0

6. Description PCIN /PI/ (supplied with software)

Documentationrequirements


1

07.2000



1.2 Requirements for start-up

Before an installation with SINUMERIK FM–NC can be started up, it is essentialthat all mechanical and electrical equipment has been fully installed. The axisand spindle drives have already been started up (speed control loop) accordingto the relevant manufacturer specifications.

The S7–300 system has been configured and started up.

Customer personnel must be available to provide assistance with configuringtasks and machine operation.

The component variants and their design are described in

References: /PHF/, “SINUMERIK FM-NC” manual

/S7H/, “SIMATIC S7-300” manual

/BH/, “Operator Components” manual

Note

The information contained in this Guide regarding

� connection and ambient conditions,

� cable installation and lengths, cable shielding,

� electromagnetic compatibility (EMC),

� earthing system, insulation, class of protection and degree of protection,

� back-up batteries, etc.

must be taken into account when the installation with the SINUMERIK FM–NCis set up and must be tested prior to start-up.

The following jumper connections must be made on the components and testedprior to start-up.

References: /PHF/, “SINUMERIK FM-NC” manual

/S7H/, “SIMATIC S7-300” manual

Note

Please refer to the Description of the PLC S7–300 for jumper connections onthe PLC I/O devices.

All wiring and cabling must be installed. In order to identify obvious wiring andtermination faults, the installation must be inspected visually.

Requirements forcommencingstart-up

Installation designwith SINUMERIKFM–NC

Jumper connections

Visual inspection/wiring and cabling


1

07.2000


Particular attention is to be paid to the following:

� Cable installationTo avoid electrical interference, power and signal cables must not be laid inthe same cable duct. A check must be made to ensure that all cables areproperly installed/routed and correctly connected to the actual value sensors(measuring system) and to the drives (setpoint).

Any cables assembled by the customer must be checked for adequate qual-ity/workmanship, particularly the shield cabling.

� Earthing system checkTo ensure fault-free operation of the system, it is essential that any externalinterference is diverted effectively. The earthing system must comply withthe specifications laid down in the SINUMERIK FM–NC Planning Guide. Inthis respect, it is particularly important that:

– the earthing system complies with requirements stated in DIN VDE 0160,

– a common earthing system is provided for the NC, drive and machine,

– the earth connections are taken in a start connection to a central earth-ing point

– equipotential bonding is provided between the individual components

– a PE connection is provided and

– relays and motors are equipped with interference suppression elements.

� Power supply checkA check must be made to ensure that the power supply cable connectionsfor all S7–300 system function modules and the power supply tolerancerange are correct.

In order to start up the system, the basic data (velocities, timers, names, etc.)and information which were produced in the course of design and configurationof the installation must be made available. These data cover all areas of thecontrol system.

The data required to start up basic functions are listed below.

Table 1-1 Basic data for start-up

MD No. Machine data name Unit

General data

10000 Machine axis name [axis no.]: 0...3 –

Channel data

20050 Assignment between geometry and channel axes –

20060 Geometry axis name in channel –

20070 Machine axis number valid in channel –

20080 Channel axis name in channel –

Axis data

30110 Setpoint assignment: Drive number –

30130 Output type of setpoint –

30200 Number of encoders –

30220 Actual value assignment: Drive number –

30230 Input on drive module –

Machine data


1

07.2000



Table 1-1 Basic data for start-up, continued

MD No. UnitMachine data name

30240 Type of actual value sensing –

30300 Rotary axis –

30310 Modulo conversion for rotary axis –

30320 Modulo 360 degrees display for rotary axes and spindle –

31000 Direct measuring system (linear scale) [encoder no.]: 0,1 –

31010 Division period for linear scales [encoder no]: 0,1 mm, degrees

31020 Encoder marks per revolution [encoder no]: 0,1 –

31030 Leadscrew pitch mm/rev

31040 Encoder is directly mounted on machine [encoder no.]: 0,1 –

31050 Denominator load gearing –

31060 Numerator load gearing –

31070 Denominator measurement gearing [encoder no.]: 0,1 –

31080 Numerator measurement gearing [encoder no.]: 0,1 –

31350 Stepping frequency at maximum speed (only relevant for stepper motors) Hz

31400 Steps per stepper motor revolution (only relevant for stepper motors) –

32000 Maximum axis velocity mm/min, rev/min

32010 Conventional rapid traverse mm/min, rev/min

32020 Conventional axis velocity mm/min, rev/min

32200 Servo gain factor 1/s

32250 Rated output voltage %

32260 Rated motor speed rev/min

32300 Axis acceleration mm/s2, rev/s2

34000 Axis with reference point cam –

34010 Approach reference point in minus direction –

34020 Reference point approach speed mm/min, rev/min

34030 Maximum path to reference cam mm, degrees

34040 Creep speed [encoder no.]: 0,1 mm/min, rev/min

34050 Direction reversal to reference cam –

34060 Maximum path to reference mark. Maximum distance from 2 reference marks in the case of distance-coded measuringsystems. [encoder no.]: 0,1

mm , degrees

34070 Reference point approach speed mm/min, rev/min

34080 Reference point distance/target point [encoder no.]: 0,1 mm, degrees

34100 Reference point value [cam no.]: 0...3 mm, degrees

34200 Position measuring system type –

34300 Reference mark distance [encoder no.]: 0,1 mm, degrees

34310 Differential distance between two reference marks with distance-coded scales [encoder no.]: 0,1

mm, degrees

34320 Length measuring system is inverted [encoder no.]: 0,1 –

36000 Exact stop limit coarse mm, degrees

36010 Exact stop limit fine mm, degrees

36030 Standstill tolerance mm, degrees


1

07.2000


Table 1-1 Basic data for start-up, continued

MD No. UnitMachine data name

36050 Clamping tolerance mm, degrees

36100 1st software limit switch minus mm, degrees

36110 1st software limit switch plus mm, degrees

36200 Threshold value for speed monitoring mm/min, rev/min

36300 Encoder limit frequency [encoder no.]: 0,1 Hz

36400 Tolerance band for contour monitoring mm, degrees

Spindle data

35000 Assignment between spindle and machine axis –

35010 Gear step change possible –

35040 Independent spindle reset –

35100 Maximum spindle speed rev/min

35110 Maximum speed for gear step change rev/min

35120 Minimum speed for gear step change rev/min

35130 Maximum gear step speed rev/min

35140 Minimum gear step speed rev/min

35150 Spindle speed tolerance Factor

35200 Acceleration in speed control mode rev/s2

35210 Acceleration in position control mode rev/s2

35300 Creep speed rev/min

35400 Oscillating speed rev/min

35410 Acceleration in oscillation mode rev/s2

�


1

07.2000



2


Design

2.1 Integration of FM-NC module (NCU 570.2) in the S7-300 PLC 2-24. . . . .

2.2 Overviews of connections 2-26. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.2.1 Overview of connections for FM-NC (NCU 570.2) 2-26. . . . . . . . . . . . . . . . 2.2.2 Overview of connections for FM 354 2-32. . . . . . . . . . . . . . . . . . . . . . . . . . .

2.3 Power supply 2-36. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.3.1 Power supply requirements of entire S7-300 system 2-36. . . . . . . . . . . . . . 2.3.2 FM-NC power supply 2-36. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.3.3 FM 354 power supply 2-37. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.3.4 Module power supply options 2-37. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.3.5 Back-up battery service 2-38. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.4 Interfaces of operator panel with MMC 2-40. . . . . . . . . . . . . . . . . . . . . . . . .

2.5 Machine control panel interfaces 2-46. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.5.1 Interfaces of the standard machine control panel 2-46. . . . . . . . . . . . . . . . . 2.5.2 Interfaces of machine control panel 2-48. . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.5.3 2nd machine control panel 2-49. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.6 Interface for customer operator panel 2-50. . . . . . . . . . . . . . . . . . . . . . . . . . .

2.7 Hand-held unit (HHU) 2-51. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.8 COROS OP 27 operator interface 2-52. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2

2

07.2000



2.1 Integration of FM-NC module (NCU 570.2) in the S7-300PLC

The SINUMERIK FM-NC comprises a SIMATIC S7-300 programmable logiccontrol and an FM-NC function module (NCU 570.2) as an I/O module. In thissystem, the S7-300 CPU performs the functions of a PLC-CPU while the NCfunctionality is provided by the FM-NC function module (NCU 570.2). A functionmodule can operate a maximum of four position-controlled axes/spindles. Thesystem can be extended to include a fifth axis/spindle through connection of anFM 354 module to the local P bus of the FM-NC.A maximum of two spindles can be implemented with one FM-NC.

dig./anal.

FM-NC(NCU 570.2)

Encoder

Servo and/orstepper drive

SIMATIC S7-300 CPU

C bus

P bus

to next rack

PS 24 V2/5/10 A

dig./anal.

24 V

PC/PG with STEP7Operator panel with MMC

IM SM SM

Machine control panel (MCP)/interface to customer op. panel/narrow machine control panel

FM 354 SM

Encoder

Drive�10 V Servo drive

local P bus

PS – Power supplyIM – Interface moduleSM – Signal module (I/O module)FM 354 – Function module as axis expansionCPU – PLC (Programmable Logic Control) of FM-NCMPI – Multi Point Interface (multipoint serial interface)

Start-up devicee.g. PG740

MPI

V24

Hand–held unit

HHU OP 27

Operatorpanel

Fig. 2-1 Integration of FM-NC into the S7-300 system

Overview

2.1 Integration of FM-NC module (NCU 570.2) in the S7-300 PLC

2

07.2000


The NCU 570.2 constitutes the NC area.

The NCU 570.2 communicates

� with the SIMATIC S7-300 CPU via the serial P (peripherals) and C (commu-nications) buses,

� with the FM 354 (as axis extension) or with digital input/output modules viathe serial local P bus,

� with up to four servo drives via a �10 V interface and/or with up to four step-per drives via pulse interfaces,

� with incremental or absolute measuring systems via four measuring circuitinterfaces and

� with operator panels (OP), programming devices (PG) and machine controlpanels (MCP), etc. of various rating classes via the multi-point serial inter-face (MPI).

The following can be connected via a 20-pin front connector with single-wireterminals:

� 2 probes

� 4 sensing elements, e.g. proximity sensors

� 2 handwheels.

The NC area can be extended if required by installing an FM 354 which is con-trolled by the NCU 570.2 via a local bus. Furthermore, additional NC-specificinputs and outputs can be implemented through the installation of additionalsignal modules (without exceeding the maximum configuration per tier) whichare driven via the local P bus.

The FM 354 communicates as an axis extension module

� with the NCU 570.2 via a serial local P bus,

� with the SIMATIC S7-300 CPU during “power-up” via the serial local P bus,

� with a servo drive via a �10 V interface and

� with an incremental or absolute measuring system via a measuring circuitinterface.

The following can be connected via a 20-pin front connector with single-wireterminals:

� 4 digital inputs

� 4 digital outputs

Since the FM-NC is an integral component of the S7-300 installation, with thePLC-CPU acting as the “master”, the entire S7-300 system must be started upfirst.

To start up the entire S7-300 system, please refer to the following documenta-tion:

References: /S7H/, “SIMATIC S7-300” manual

/PHF/, “SINUMERIK FM-NC” manual

/BH/, “Operator Components” manual

NCU 570.2

FM 354

Start-up

2.1 Integration of FM-NC module (NCU 570.2) in the S7-300 PLC

2

07.2000



2.2 Overviews of connections

2.2.1 Overview of connections for FM-NC (NCU 570.2)

Fig. 2-2 shows the interfaces of the FM-NC (NCU 570.2) to the S7-300 systemand to the NC machine.

Label plate

Front viewwithout front covers

Measuring system interfaces X3...X6

Front cover(hinged)

Error and status displays

Drive interface X2

Bus connectorSIMATIC interface(local P bus)

SFBAFDC5VDIAG

ML+M

Compartmentfor backup battery

Power supply connec-tionX10

DIN rail

I/O interface X1

123456789

1

1

111111112

0

0

123456789

L+

Front connector

X2 X3 X4

X5 X6

Bus connector (hidden)SIMATIC interface(P bus and C bus)

Start-up switch Slot for memory module (PCMCIA)

Start-upswitch

Slot for memorymodule(PCMCIA)

Fig. 2-2 Layout of interfaces and front elements

Interfaces andfront panel ele-ments


2

07.2000


� SIMATIC interface

– Rear-panel connectors (on left in Fig. 2-2) for connecting the NCU 570.2to other control components via the S7-300 backplane bus (P and Cbuses)

– Rear-panel connectors (on right in Fig. 2-2) for connecting NCU 570.2 to S7-300 modules to extend NCU 570.2 functionality (local P bus)

� Drive interface

50-pin D-sub connector (X2) for connecting the power sections for a maxi-mum of four drives (analog drives and/or stepper drives)

� Measuring system interfaces

D-sub sockets (X3...X6) to which up to a maximum of four position encoderscan be connected via 15-pin connectors.

� I/O interface

20-pin front connector (X1) for connecting the handwheels, high-speed in-puts and probes and for wiring up the NC-READY relay.

� Power supply connection

4-pin screw-type terminal block (X10) for connecting the 24 V load powersupply.

� Memory module interface

68-pin memory module interface for PCMCIA (JEIDA memory card)

Start-up switch (rotary switch)

for connection of a lithium battery, pre-assembled with connector

The start-up switch is provided to assist start-up. It can be actuated by means ofa screwdriver.

4 LEDs for error and status displays

� SF (red) Group error

This LED indicates an error status of the NCU 570.2. In order to eliminatethe error, it may be necessary to start up or install the system again, to up-date the firmware or to replace a hardware component.

� DIAG (yellow) Diagnosis

This LED indicates various diagnostic statuses. If you are not using an oper-ator panel (OP) or a programmer (PG) to indicate error statuses, the flashingof this LED will help you to localize the causes of errors.

� BAF (red) Battery fault

Flashing of this LED indicates that the battery needs to be changed.

When it lights up continuously, the data contents of the buffered memorymay no longer be stored. A restart is required after replacement of the bat-tery.

Interfaces

Operator controls

Battery compartment

Displays


2

07.2000



� DC 5V (green) Logics supply connected

This LED indicates that the hardware is ready to operate.

If it does not light up, check the following:

– Is mains power supply OK?

– Is load power supply defective?

– Is module incorrectly connected?

– Is control incorrectly configured (sum of rated and starting currents toohigh)? or

– Is module defective?

� LED display when FM-NC (NCU 570.2) is in “Normal state”

– LED SF: OFF

– LED BAF OFF

– LED DC 5V ON

– LED DIAG Rapid, regular flashing = NC sign of life (3 Hz)

Table 2-1 provides you with an overview of the LED error indications on theNCU 570.2 module.

In the table, the following mean:

1 = ON0 = OFFn/1 = Periodic flashing for indefinite timex = Not significant for fault/error described

Table 2-1 Summary of LED error displays

SF BAF DC5V DIAG Meaning Remark

Hardware/Power supply:

1 X 1 X HW fault1) Replace FM-NC (NCU 570.2)

1 X 0 X 5 V failure Replace FM-NC (NCU 570.2)/remove external connections

0 X 0 X 24 V failure Check 24 V incoming supply/remove external connections/replace FM-NC (NCU 570.2)

1) LED combination even when PLC-CPU is switched off or not connected (no 5 V power supply on P bus).

Battery monitoring:

X 1 X X Battery failure Scan: During power-upRemedy: Replace battery(System must be started up again)

X 1/1 X X Battery warning, voltage belowlimit

Scan: CyclicRemedy: Replace battery a.s.a.p.

Power-up and SW monitoring: (With this error/fault group, we recommend that you run the FM-NC (NCU 570.2) upagain with a SW update. If this does not eliminate the error/fault, then the FM-NC (NCU 570.2) must be replaced).

1 1 1 1 RAM error in COM(power-up aborted)

1 x x 1/1 COM power-up error, parameter-ization by S7-300 missing.

0 X X 0 Power-up Status display


2

07.2000


Table 2-1 Summary of LED error displays, continued

SF RemarkMeaningDIAGDC5VBAF

0 X X 1 PLC STOP PLC RUN and POWER OFF/ON

0 X X 2/1 COM watchdog

0 X X 3/1 NCK watchdog

0 X X 4/1 Internal NCK SW error:NRK timer/memory/link

0 X X 5/1 Internal NCK SW error:Processor FAULTs

Please contact theSIEMENS AG

0 X X 6/1 Internal NCK SW error:Plane run

SIEMENS AGHotline (Tel.: +49 9313 / 98 – 3836)

0 X X 7/1 Internal NCK SW error:Stack overflow, MM error

0 X X 8/1 COM-NCK power-up error

0 X X 9/1 NCK-PLC power-up error

1 x x 10/1to

17/1

Access error on local P bus HW or SW error/fault on a moduleconnected to local P bus of FM-NC

1 1/1 x 1/1 RAM error After POWER ON or RESET

Measuring system monitoring:

1 X X 2/1 Encoder supply failure Check measuring system and connection

Start-up and checksum check, update:

1 X X 1 No start-up synchronization Update request after 30 s

1/1 X X X Update request

1/1 X X 2/1 COM checksum error Update COM

1/1 X X 3/1 NCK checksum error Update NCK

After initiation of update:

1/1 x x x Update request

1/1 x x 2/1 Checksum error during COM up-date

1/1 x x 3/1 Checksum error during NRK/NCKupdate

1/1 x x 4/1 Group error during NRK/NCK de-compression

0 X X 1 Flash deletion in progress Status display

0 X X 4/1 Flash programming in progress Status display

0 X X 5/1 Update complete, o.k. Status display, power OFF/ON


2

07.2000



Table 2-2 provides you with a list of the connector pin assignments for thepower supply and connectors X1 to X6

Table 2-2 PIN assignment of front connectors on FM-NC (NCU 570.2)

PIN MD 30120CTRLOUT_NR

Designation

Terminal block for 24 V load power supply

1/3 L+ (DC 24 V)

2/4 M (frame)

X1: Handwheel and I/O connection, 20-pin front connector

X1 1/2 5 Handwheel 1, track A (A1, A1_N)

3/4 Handwheel 1, track B (B1, B1_N)

7/8 6 Handwheel 2, track A (A2, A2_N)

9/10 Handwheel 2, track B (B2, B2_N)

5 – Handwheel voltages: P5_EXT

6 – M5_EXT

11/12 – NCRDY.1/.2 (ready to operate)(NC READY contact)

X1 13 – Digit. input 1 (I0/BERO1)

14 – Digit. input 2 (I1/BERO2)



17 – Digit. input 5 (I4/MEPU1)

For connection of probes please refer to:

References: /FB/, M4, “Measuring Cycles”

18 – Digit. input 6 (I5/MEPU2)

For connection of probes please refer to:

References: /FB/, M4, “Measuring Cycles”

19 – Not assigned

20 – M (reference potential for inputs)

X3 to X6 (axes 1 to 4): 15-pin D-sub socket connector, measuring system interface

X3 4/6 1 (X3) Measuring system power supply: P5EXTtoX6 5

2 (X4)3 (X5) Measuring system power supply:P24EXT

7/94 (X6)

MEXT

2/3 Absolute encoder: Shift clock cycle (CLS,CLS_N)

10/11 Incremental encoder: Zero mark (N, N_N)

15/14 Track A/SSI data (A/DATA, A/DATA_N)

13/12 Track B (B, B_N)

Connector pin assignments


2

07.2000


Table 2-2 PIN assignment of front connectors on FM-NC (NCU 570.2), continued

DesignationMD 30120CTRLOUT_NR

PIN

X2: 50-pin D-sub plug connector, drive interface

X2 1/34 1 Analog setpoint (SW1, BS1)

2/35 2 Analog setpoint (BS2, SW2)

3/36 3 Analog setpoint (SW3, BS3)

4/37 4 Analog setpoint (BS4, SW4)

5/38 1 Clock pulse 1 (PULS1, PULS1_N)

6/39 Directional pulse 1 (DIR1, DIR1_N)

18/19 Enable signal 1 (ENABLE1, ENABLE1_N)










14/47 1 Servo enable 1 (RF1.1, RF1.2)





2

07.2000



2.2.2 Overview of connections for FM 354

Fig. 2-3 shows the interfaces of the FM-354 to the S7-300 system and to theNC machine.

Label plate

Front viewwithout front covers

Measuring system interface X3

Front cover(hinged)

Status and error displays

Drive interface X2

Bus connectorSIMATIC interface(local P bus)

SF

DC5VDIAG

DIN rail

I/O interface X1

123456789

1

1

111111112

0

0

123456789

Front connectorENCODER X3

ANAL.OUT X2

I0I1I2I3

RM

Q0Q1Q2Q3

Display for digital inputs and outputs

Label on module:FM 354F.SERVO MOTOR

Bus connector (hidden)SIMATIC interface(local P bus)

Fig. 2-3 Layout of interfaces and front elements

Interfaces andfront panel ele-ments


2

07.2000


� SIMATIC interface

Rear-panel connectors for connecting the FM 354 to the FM-NC (NCU570.2) via the local P bus or to the SIMATIC S7-300 CPU during systempower-up.

� Drive interface

9-pin D-sub connector (X2) for connecting the drive unit (analog drive orstepper motor)

� Measuring system interfaces

15-pin D-sub socket (X3) to which one position encoder can be connected.

� I/O interface

20-pin front connector (X1) for connecting the digital inputs/outputs are wir-ing up the power supply

12 LEDs for error and status displays

� SF (red) Group error

This LED indicates an error status of the FM 354. In order to eliminate theerror, it may be necessary to start up or install the system again, to updatethe firmware or to replace a hardware component.

� DIAG (yellow) Diagnosis

This LED indicates various diagnostic statuses. If you are not using an oper-ator panel (OP) or a programming device (PG) to indicate error statuses, theflashing of this LED will help you to localize the causes of errors.

� DC 5V (green) Logics supply connected

This LED indicates that the hardware is ready to operate.

If it does not light up, check the following:

– Is mains power supply OK?

– Is load power supply defective?

– Is module incorrectly connected?

– Is control incorrectly configured (sum of rated and starting currents toohigh)? or

– Is module defective?

� I0...I3 (yellow) Digital inputs

These LEDs display the enabled input.

� Q0...Q3 (yellow) Digital outputs

These LEDs display the enabled output.

� RM (yellow) Drive unit ready (not used for FM-NC)

This LED indicates that the drive unit is ready.

Interfaces

Displays


2

07.2000



� LED display when FM 354 connected to local P bus of FM-NC is in “Normalstate”

– LED SF: OFF

– LED DC 5V ON

– LED DIAG Flashes only in the case of axes with measuring system, at a rate dependent on the set basic clock cycle time of FM-NC (MD_ENC_TYPE=2 or 5MN 10050 SYSCLOCK_CYCLE_TIME = 0.006 illuminated for 3 s, dark for 3 s)

– LED DIAG ON only in the case of an axis without measuring system(MD_ENC_TYPE=0; e.g. spindle without measuring system or simulation axis)

Table 2-3 provides you with an overview of the LED error indications on the FM354 module.

In the table, the following mean:

1 = ON0 = OFFn/1 = Periodic flashing for indefinite timex = Not significant for fault/error describedB = Flashing

Table 2-3 Summary of LED error displays

SF DC5V DIAG Meaning Remark

1 x x HW fault or SW error FM 354 SW update or replace FM 354 module

0 1 0 FM 354 power-up not detected bySIMATIC S7-300 CPU

Check SDB 100 in PLC program

1 1 0 RESET Module in RESET state

0 1 1 FM 354 power-up detected by SI-MATIC S7-300 CPU, but 354module not parameterized as 5thaxis by FM-NC or axis withoutmeasuring system

Axis parameterized without measuring systemorFM 354 or FM-NC (NCU 570.2) defective

0 1 B Normal state; FM 354 as 5th axisof FM-NC with measuring system

No error/fault


2

07.2000


Table 2-4 provides you with a list of the connector pin assignments for connec-tors X1 to X3.

Table 2-4 PIN assignment of front connectors on FM 354

PIN Designation

X1: Handwheel and I/O connection, 20-pin front connector

X1 3 Digit. input 1 (DE1)

4 Digit. input 2 (DE2)

5 Digit. input 3 (DE3) / Probe 2

6 Digit. input 4 (DE4) / Probe 1

9 Positive input of controller message (RM_P) (not with FM–NC)

10 Negative input of controller message (RM_N) (not with FM–NC)

11 Digit. output 1 (DA1)




19 Load power supply: 24 V

20 M

X3: 15-pin D-sub socket connector, measuring system interface

X3 4/6 Measuring system power supply: P5EXT

5 Measuring system power supply: P24EXT

7/9 MEXT

2/3 Absolute encoder: Shift clock cycle (CLS, CLS_N)

10/11 Incremental encoder: Zero mark (N, N_N)

15/14 Track A/SSI data (A/DATA, A/DATA_N)

13/12 Track B (B, B_N)

X2: 9-pin D-sub plug connector, drive interface

X2 1/6 Analog setpoint (SW, BS)

9/5 Controller enable 1 (RF1.1, RF1.2)

Connector pin as-signments


2

07.2000



2.3 Power supply

2.3.1 Power supply requirements of entire S7-300 system

The S7-300-CPU can buffer mains supply interruptions lasting up to 5 ms (guaranteed minimum period).

After a power failure, a back-up period of at least 50 ms is still available in theNCU 570.2.

Note

In order to bridge power supply interruptions of > 5 ms, the FM-NC, FM 354and PLC-CPU (or the entire S7-300 under ideal conditions) should be operatedon a common 24 V power supply which guarantees the power supply back-uptime required by the customer.

PS 307 power supply modules (2 A, 5 A and 10 A) should preferably be used,depending on power requirements. These modules are capable of bufferingsupply failures of 20 ms.

If the customer prefers to use a separate power supply for the FM-NC, FM 354and PLC CPU 314 as an alternative to the above solution, then he must ensurethat all modules are powered up/down simultaneously when “POWER OFF/ON”is selected. The FM-NC cannot be powered up via “POWER OFF/ON” sepa-rately from the PLC CPU 314.

2.3.2 FM-NC power supply

4-way screw-type terminal blockTerminals 1 and 3: L+ +24 V load power supply

Terminals 2 and 4: M 0 V load power supply (frame)

Approx. 1 A load current.

FM-NC cannot operate when the polarity is reversed. LED “DC5V” is off.

LED “DC5V” lights up when the poles have been properly connected.

!Important

Equipotential bonding must be provided if the S7-300-CPU and FM-NC aresupplied by different load power supplies.

Mainsbuffering

POWER OFF/ON

Power supplyconnection

Power requirement

Polarity reversalprotection

2.3 Power supply

2

07.2000


2.3.3 FM 354 power supply

20-pin front connector X1

Terminal 19: L+ +24 V power supply

Terminal 20: M 0 V power supply (frame)

Approx. 350 mA load current (with encoder supply).

FM 354 cannot operate when polarity is reversed. LED “DC 5V” is off.

LED “DC 5V” lights up when the poles have been properly connected.

!Important

Equipotential bonding must be provided if the S7-300-CPU and FM 354 aresupplied by different power supplies.

2.3.4 Module power supply options

L1

L2L3NPE

L+N

NCU 570.2CPUPS 307

PEM

MM

L+L

M

AC

DC

L+

L–

L+M

CPU

PEM

M

L+

NCU 570.2

L+M

FM 354

M

L+M

FM 354

Low-voltage distribution e.g. TNS system (3 x 400 V)

Rail

Rail

Earthingbarin cabinet

Earthing barin cabinet

Fig. 2-4 Module power supply options

Power supply con-nection

Power requirement

Polarity reversalprotection

2.3 Power supply

2

07.2000



2.3.5 Back-up battery service

The FM-NC has a back-up battery which acts as the power supply for the buffered RAM.

It must be ensured that the battery is properly connected (notch on battery con-nector must face towards right or lug towards left and positive pole downwards,connector is inserted in battery compartment).

SFBAFDC 5VDIAG

ML+M

L+

Compartment for back-up battery

X2 X3 X4

X5 X6

Fig. 2-5 Insertion of back-up battery

A battery fault is detected in the case of incorrect connection.

!Important

An incorrectly inserted battery may discharge and have to be replaced.

The battery voltage is monitored in two phases:

1st phase: “Battery warning”

The battery must be replaced if LED “BAF” starts to flash. Buffered data will re-main safe for several weeks depending on how often the control is switched on.The battery must be replaced as quickly as possible after output of a batterywarning. The system need not be started up again.

Error message: 2100 “NCK battery warning threshold reached”

!Important

The battery must be replaced when the control system is switched on (other-wise data will be lost).

Battery connection

Battery voltagemonitoring

2.3 Power supply

2

07.2000


2nd phase: “Battery fault”

The “BAF” LED lights up steadily when the battery voltage has dropped belowthe minimum value required to buffer the RAM.

During control power-up, the system automatically branches to the start-upmode with default values and the error message “Standard machine dataloaded” is set. A new battery must be inserted before buffered data are reloadedor entered again.

If buffered data have been lost, please proceed as described in Section 11 or 3.

� Battery type: Li battery set with connecting lead,size 1/2 AA, capacity approx. 850 mAh,voltage min. 3.6 V

� Service life: Minimum 2 years, typically 4 to 6 years dependingon control system service period.

Error message: 2102 “NCK battery alarm”

2.3 Power supply

2

07.2000



2.4 Interfaces of operator panel with MMC

Fig. 2-6 shows a view of the rear of the operator panel with its individual compo-nents.

For a detailed description and diagrams of these components, please refer to

References: /BH/, “Operator Components” manual

MMC

ISA adapter3)

Pow

er s

uppl

y

S1

X10

X6 X5 X4X3

1) 2)

Chassis

1) Housing edge MMC 100/100.22) Housing edge MMC 102/1033) not with MMC 1004) not with MMC100.2

S2

Power supply

24 V0 V PE

Equipotential bonding conductor

4)

Fig. 2-6 Operator panel with individual components

Operator panelwith individualcomponents


2

07.2000


The interfaces and operating elements of the MMC 100 are shown in Fig. 2-7.

MMC 100

S1

X10

X6 X5 X4X3

S2

External keyboard interface (keyboardmust be set to “XT keyboard”

RS 232 serial interface

Operator panel interface(MPI)

VGA interface

RESET buttonNMI button

NC keyboard interface

LCD interface

Power supply interface

Fig. 2-7 Interfaces and operating elements of MMC 100

For a detailed description and diagrams of the interfaces (e.g. pin assignment),please refer to


� RESET button S1

� NMI button S2

Interfaces and op-erating elementsof MMC 100

Interfaces on MMC100

Operating elements


2

07.2000



The interfaces and operating elements of the MMC 100.2 are shown in Fig. 2-8 .

NC keyboard interface X142

LCD interface X141

Power supply interface X3

MPIoperator panel interface

Reset buttonMF2external keyboard interface

COM1serial interface RS232

VGA monitorinterface

Memory module interface for PCMCIAX201

DIP switch S3

X201

S31 8

COM2serial interface RS232(in preparation)

Cover for memory module interface X201

Fig. 2-8 Interfaces and operating elements of MMC 100.2



� RESET button S1

� DIP switch S3

Interfaces and op-erating elementsof MMC 100.2

Interfaces on MMC 100.2

Operatingelements onMMC100.2


2

07.2000


I The interfaces and operating elements of the MMC 102/103 are shown in Fig. 2-9.

PCMCIA option interface for MMC103

X11

X3

X4X5X6X7

X8S1

S2

X10X9

X153

X152

D12

X151

SIE

ME

NS

X142

X141

X12

2X

121

Hard disk

Battery 7-segment display

ISA interface

NC keyboard interface

LCD interface

Button S1

Button S2

Mass storage in-terface IDE

Floppy disk drive interface External keyboard/

mouse portParallel printer port (LPT1)

Serial interfacesRS232


Operator panel interface (MPI)

VGA interface

CO

M2

CO

M1

LPT

1

MP

I

VG

A

Fig. 2-9 Interfaces and operating elements of MMC 102/103



The buttons S1 and S2 have the following functions:

� MMC102:RESET button S1NMI button S2

� MMC103:NMI button S1RESET button S2

Interfaces and op–erating elementsof MMC 102/103

Interfaces on MMC 102/103

Operatingelements on MMC 102/103


2

07.2000



The ISA adapter interfaces are shown in Fig. 2-10. The ISA adapter is an exten-sion for the CPUs MMC 102.

ISA slot interface

X151

X152

X153

X22

0

X22

1

ISA interface

Fig. 2-10 ISA adapter interfaces



Interfaces on ISAadapter

ISA adapterinterfaces


2

07.2000


The PCI adapter interfaces are shown in Fig. 2-11. The PCI adapter is an exten-sion for the CPUs MMC 103.

Card interface

PCI slot interface

X151

X153

X3

X22

0

X4

X22

1

PCIinterface

8/16–bit card interface

X123

X121

X122

Fig. 2-11 PCI adapter interfaces



Interfaces on PCI adapter

PCI adapter interfaces


2

07.2000



2.5 Machine control panel interfaces

2.5.1 Interfaces of the standard machine control panel

The following interfaces, switches and display elements are present on the rearof the standard machine control panel (MCP):

Operator panel interface

Power supplyinterface

Switch S3

X10

X20

S3 3 1

4 2

Emergencystop button

ON

”

1 2 3 4

LEDs 1...4Equipotential bonding conductor terminal

1 2 3

SHIELD M24 P24

Fig. 2-12 Rear view of machine control panel, M and T versions



The baud rate, transmission cycle time, bus address and hardware can be setvia switch S3. The standard switch settings are as follows:

Table 2-5 Standard settings of switch S3

1 2 3 4 5 6 7 8 Meaning

6FC5 203 0AD10-0AA0 off off on off on on off off Baud rate: 187.5 kbaudTransmission cycle time: 100 msBus address: 6

Interfaces and op-erating elementsof standard MCP

Interfaces

Switch S3


2

07.2000


Other settings for the machine control panel are shown in the following table.These table data apply to MCPs and to the customer operator panel interface(Section 2.6).

Table 2-6 Possible settings for S3

1 2 3 4 5 6 7 8 Meaning:

onoff

Baud rate: 1.5 MbaudBaud rate: 187.5 kbaud

ononoffoff

onoffonoff

400 ms transmission cycle time200 ms transmission cycle time100 ms transmission cycle time50 ms transmission cycle time

ononononononononoffoffoffoffoffoffoffoff

ononononoffoffoffoffononononoffoffoffoff

ononoffoffononoffoffononoffoffononoffoff

onoffonoffonoffonoffonoffonoffonoffonoff

Bus address: 15Bus address: 14Bus address: 13Bus address: 12Bus address: 11Bus address: 10Bus address: 9Bus address: 8Bus address: 7Bus address: 6Bus address: 5Bus address: 4Bus address: 3Bus address: 2Bus address: 1Bus address: 0

off Series HW (MCP)

on Interface for customeroperator panel


The LEDs have the following meaning:

Table 2-7 LEDs 1...4 on machine control panel

Designation Meaning

LEDs 1 and 2 Reserved

LED 3 POWER: Lights up when voltage (24V) is present

LED 4 SEND: Changes state after data have been sent

LEDs 1...4


2

07.2000



2.5.2 Interfaces of machine control panel OP032S

The following interfaces, switches and display elements are present on the rearof the machine control panel OP032S:

X20

X10

Operator panel interface (MPI)

DIP switch(8-way), assignments


Displays: LED 1, 2: not usedLED 3: POWER (24 V supply)LED 4: SEND, changes state on protocol transmission

ON �

1 2 3 4

Equipotentialbonding con-ductor terminal

S3

LED:

Inputs

Outputs

8 1

Connector1x6-pin

Pin 4 1 4 1 Pin 4 1 4 1

X36X35

X10

P24 M24 Shield

Fig. 2-13 Rear view of machine control panel OP032S



The baud rate, transmission cycle time, bus address and hardware can be setvia switch S3. The standard switch settings are as follows:

Table 2-8 Standard settings of S3 for MSTT OP32S

1 2 3 4 5 6 7 8 Meaning:

on off on off on on off off Baud rate: 1.5 MBaudTransmission cycle time: 100 msBus address: 6

Note

For use with the FM-NC, a baud rate of 187.5kBaud is to be set at the MCP OP032S (see Possible settings in Table 2-9). Switch S3.1 is to be set to the position ”OFF”.

Interfaces and op-erating elementsof MCP OP032S

Interfaces

Switch S3


2

07.2000


Other settings for the machine control panel are shown in the following table.These table data apply to MCP OP032S.

Table 2-9 Possible settings for S3 for MCP OP032S

1 2 3 4 5 6 7 8 Meaning:

onoff

Baud rate: 1.5 MBaudBaud rate: 187.5 kBaud

onoffoff

offonoff

200ms transmission cycle time / 2400 ms receipt monitoring100ms transmission cycle time / 1200 ms receipt monitoring50 ms transmission cycle time / 600 ms receipt monitoring






onoff

Interface MPI customer operator panelSeries HW

2.5.3 2nd machine control panel

Two machine control panels can be operated with the SINUMERIK FM-NC. The2nd MCP must be parameterized in the basic program parameters of FB1 inOB100.


2

07.2000



2.6 Interface for customer operator panel

A customer operator panel can be connected via this interface. 64 digital inputsand 64 digital outputs with C-MOS level (5V) are provided on the module for thispurpose.

The interface to the customer operator panel has the following interfaces,switches and display elements:

ON

X231

LEDs

S3

X20

X10

X221X211

H3H1H4H2�


123

SHIELDM24P24

Switch S3 LED 1...4

Operator panel interface

Equipotential bonding conductor terminal

Fig. 2-14 Front view of interface for customer operator panel



The baud rate, transmission cycle time, bus address and hardware can be seton switch S3. The default switch settings are as follows:

Table 2-10 Default settings of switch S3

1 2 3 4 5 6 7 8 Meaning:

off off on off on on off on Baud rate: 187.5 kBaudTransmission cycle time: 100 msBus address: 6

Interface

Interfaces,switches and dis-play elements

Interfaces

Switch S3

2.6 Interface for customer operator panel

2

07.2000


2.7 Hand-held unit (HHU)

The hand-held unit is connected to the MPI line via a distributor. The distributoris designed for mounting in a control cubicle or separate housing.

1

2

3

4

1

2

3

4

ON OFF

S1

S2

ON OFF

S1

S2

Reserved

187.5 kBaud

Bus ad-dress 15

IDLEtime100 ms

Default settings

Fig. 2-15 Position of DIP switches in HHU (default setting)

The default setting (delivery state) of the DIP switches should be used when theHHU is operated on the MPI interface.

Table 2-11 S1 and S2 settings in HHU

S11

S12

S13

S14

S21

S22

S23

S24

Meaning:

off on off off on on on on Delivery state

off Baud rate: 187.5 kbaud







Overview

DIP switch settingfor MPI

2.7 Hand-held unit (HHU)

2

07.2000



2.8 COROS OP 27 operator interface

To operate and monitor (O & M) the FM-NC, it is possible to connect an operatorinterface (OP 27) to the CPU via the MPI interface.

The FM-NC communicates with the OP 27 via the backplane bus.

The interfaces on the OP 27 are shown in the following diagram.

IF1 A IF2 IF1 B

Power supply

optional

V24/TTY

Printer PC/PG

CPU FM-NCNCU 570.2

OP 27

MPI

Equipotential bonding conductorconnection

MemoryExtension

P24 M24 Relay contacts24 V DC; 0.3 A

Fig. 2-16 Interfaces of OP 27

Standard cables are available to make the connections shown.

The supply voltage is connected via the four-pin terminal block supplied asfollows:

1. Connect leads to terminals (conductor cross-section: 0.5...2.5 mm2)

2. Insert terminal block in lower plug connector on OP 27

The ground terminal must be connected to the cubicle ground.

References: /ST7/, SIMATIC S7, Catalog ST 70

�

Overview

Connecting cable

Terminal block

Ground terminal

References forCOROS operatorinterfaces

2.8 COROS OP 27 operator interface

3


Settings, MPI Nodes

3.1 MPI networking rules 3-54. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.2 Standard configuration 3-55. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.3 Nonstandard configuration 3-58. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.4 Example of an MCP and HHU configuration on MPI bus with STEP7 V5x 3-60. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.5 Example of distribution of MPI addresses 3-66. . . . . . . . . . . . . . . . . . . . . . .

3

3

07.2000



3.1 MPI networking rules

The following basic rules must be observed with respect to networkinstallations:

1. The bus line must be terminated at both ends. To do so, switch in theterminating resistor in the MPI connector in the first and last nodes. Switchout all other terminating resistors.

Note

Only two terminating resistors may be activated in the same line at a time.

2. At least one termination must be supplied with a 5V voltage. For this pur-pose, the MPI connector with active terminating resistor must be connectedto a device that is connected to the power supply.

Note

Connecting the MPI connector to the PLC (CPU) is ideal for this purpose.

3. Spur lines (feeder cable from bus segment to node) should be as short aspossible.

Note

Unused spurs should be removed wherever possible.

ËËËËËËËËËËËË

MCP

ËËËËËËËËËËËËËËË

MMC 100/102ËËËËËËËËËËËËËËË

PG

Terminating resistoractivated in connector

ON


ËËËËËËËËËËËËËËËË

MPI

PLC-CPU

FM-NCNCU 570.2

ON

ON

Fig. 3-1 Network installation with terminating resistors

Basic rules

Example

3.1 MPI networking rules

3

07.2000


3.2 Standard configuration

PLC–CPU mit SINUMERIK FM-NC, MMC and a machine control panel (MCP)or interface to customer operator panel on MPI bus.

The following hardware components are required for the minimum configuration

� AS300 PLC-CPU (315, 316, 614, .., 318)

� SINUMERIK FM-NC NCU 570.2 with firmware version from V 03.xx

� MMC

� MCP or interface to customer operator panel.

STEP7

MPI bus nodes operate at 187.5 kbaud.

Every node on the MPI bus must have a bus address (0...31).

Fig. 3-2 shows the default settings for the MPI bus addresses.

ËËËËËËËËËËËËËËËËËËËËËËËË

MCP/interface tocustomer operatorpanel


Operator panel with MMC

ËËËËËËËËË


PLC-CPU

FM-NCNCU 570.2

ËËËËËËËËËËËËËËËËËËËË

Programmingdevice with S7

1

MPI 187.5 kbaud

6 0

2 3

MPI bus addresses

Fig. 3-2 Standard application for SINUMERIK FM-NC

Standardapplication

Hardware requirements

Software

Baud rate

Bus addresses


3

07.2000



The addresses of the bus nodes can be set as follows:

� MMC 100/100.2

Default address: 1

Setting in configuration file “NETNAMES.INI” using application software

References: /FB/, B3, “Several Operator Panels and NCUs”

� MMC 102/103

Default address: 1

Setting in operating area ”Start–up/MMC/Operator panel”

� Programming device

Default address: 0

Setting in STEP7 via menu “Extras / PG/PC interface”

� PLC-CPU

Default address: 2

Setting in STEP7 hardware configuration under menu item “Edit/Objectproperties/General/Properties/MPI”

After changing the MPI address, it is necessary to load the configuration intothe target module via menu item ”Target system/Load into module”. It isonly possible to change the MPI address if the PLC-CPU is in ”STOP”.

References: /S7H/, S7 Manual or/S7HT/, “Start-up MPI Bus Nodes” manual

� FM-NC (NCU 570.2)

Default address: 3

Setting: The PLC-CPU ascertains the MPI bus address of the FM-NCfor its rack configuration while the S7-300 system is being booted. This slot-dependent MPI address is then transferred to the C-bus modules. Based onits own MPI address, the PLC-CPU increments by one the MPI address foreach C-bus module

Example:

ËËËËËËËËË


PLC-CPU

FM-NCNCU 570.2

ËËËËËËËËË

SM ËËËËËË

SMËËËËËËËËË

FM

2 3 4

MPI

Fig. 3-3 MPI addresses for C-bus modules

Setting of busaddresses


3

07.2000


!Important

It must be ensured that the addresses of other MPI nodes (e.g. MCP = 6) arenot overlapped when the addresses are consecutively numbered in this way.

� Standard MCP / MCP OP032S / Interface to customer operator panel

Default address: 6

Setting via DIP switch S3

Table 3-1 Settings on DIP switch S3 for standard application

1 2 3 4 5 6 7 8 Meaning:

off off on off on on off off Standard MCP / MCP OP032S:Baud rate: 187.5 kbaudTransmission cycle time: 100 msBus address: 6

off off on off on on off on Interface to customer operatorpanelBaud rate: 187.5 kbaudTransmission cycle time: 100 msBus address: 6

The following bytes in the PLC-CPU are assigned for the MCP or interface tocustomer operator panel (applies when SDB210 of the basic program Library isused):

� Input bytes 118...125

� Output bytes 120...127

� Status bytes for error detection, output double word 108 (evaluated by basicprogram)

These parameters on FB1 in OB100 (basic program) for the MCP are alreadyset.

Note

The input and output bytes given above are addresses in the range of the 4thrack. If this address range in the 4th rack is being used, different input, outputand status ranges must be assigned in the PLC-CPU and a new SDB210 mustbe generated (see Section 3.3).

If communication does not commence after a PLC reset (all display LEDs of theMCP flashing), the following points should be checked:

� Cable and connector wiring

� DIP switch S3 (default setting)

� SDB210 from basic program diskette not loaded

Assignedinputs/outputs inPLC-CPU

CommunicationPLC–MCP doesnot start


3

07.2000



3.3 Nonstandard configuration

To name an example, the connection of additional MPI bus nodes would consti-tute a nonstandard configuration. The following are nonstandard features:

� Connection of a hand-held unit (HHU)


� Connection of a second MCP

� Connection of further PLCs

Nonstandard settings with regard to the HHU, MCP and PLC are specified inthe global data configuration (see Section 3.4 ).

� Connection of an OP 27 operator panel

(Configuration via ProTool.)

References: /ST7/, Catalog ST 70

� Connection of further FM-NCs

(Configuration via the PLC basic program on FB1 in OB100.)

� Connection of positioning modules FM 353/FM 354 (not on local P bus of the FM-NC)

(Configuration via the start–up tool.)

References: /S7S/, /S7L/, ”SIMATIC S7-300” manuals

You must adjust the communications parameters and possibly the switch set-tings (addresses) of the bus nodes.

To be able to enter a new configuration it is necessary to define global data inSTEP7. Select the object MPI network in the STEP7 project and then selectDefine global data in the menu Extras. The following procedure assumes thatthe user is acquainted with the handling of this tool.

1. Set up a new project in STEP7. A separate station is to be set up for each ofthe components (PLC, HHU, ...) which are linked together via MPI.

2. Link the MPI nodes, i.e. interconnect CPU programs with MPI address(hardware configuration).

3. Define global data and enter the desired configuration

4. Compile this configuration. A new SDB210 (system data block) will be crea-ted for each CPU program. The SDB210 for the component MCP/HHU ismeaningless, because the settings of the basic data parameters are madewith DIP switches or via the keyboard.

5. Set the cyclical transmit pattern. Once the configuration has been compiledsuccessfully for the first time, the “Conversion factor” (SR) and “Status”(GDS) can be activated and then input.

6. Compile your configuration again.

7. Transfer the SDB210 (from the CPU program of the PLC) to the PLC.

Overview

Procedure


3

07.2000


Note

The SDBs are not displayed in the STEP7 project manager by default. Theyare listed by double-clicking on the object System data.

8. Make the device-specific settings for all nodes: You now need to set the GDidentifiers from the table of global data definitions for the components(HHU,..).

9. You must set the input, output and status parameters for call FB1, DB7 inOB 100 in the basic PLC program for all operator control components (MCP,HHU).


3

07.2000



3.4 Example of an MCP and HHU configuration on MPI buswith STEP7 V5x

PG/PC with STEP7 V5.x, PLC-CPU, FM-NC, MCP, HHU,(MMC)

MCP


Operator panel with MMC

ËËËËËËËËË


PLC-CPU

FM-NCNCU 570.2

1

MPI bus 187.5 kBaud

14

2 3


ËËËËËËËËËË

Distri-butor

HHU Inputs: Flag byte (MB) 20...25Outputs: Flag byte (MB) 0...19Status: Flag double word (MD) 26

15

Inputs: Input byte (EB) 118...125Outputs: Output byte (AB) 120...127Status: Output double–word (AD) 108

ËËËËËËËËËËËËËËËËËË

PG with S7

0

Fig. 3-4 Example of an MCP and HHU configuration on an MPI bus

Set up new project with the name Example. 3 stations must then be set up for the Example project.

� PLC–CPU

� MCP

� HHU

The 3 stations are assigned as follows:

� PLC-CPU e.g. for the CPU315

� MCP for the machine control panel

� HHU for the hand–held unit.

Requirements

Call STEP 7

Assignment of stations

3.4 Example of an MCP and HHU configuration on MPI bus

3

07.2000


Networking must be activated for each CPU station in the hardware configura-tion. The CPU stations of the MCP/HHU do not have their own CPU. Any CPUcan be selected (e.g. CPU315). To aid identification, the selected CPU for theMCP is given the name “MCP-CPU” and that for the HHU the name “HHU-CPU”. CPU315 is selected for the PLC–CPU. The individual CPUs are linkedon a network with the following MPI addresses:

� PLC-CPU with MPI address 2,

� MCP-CPU with MPI address 14 and

� HHU-CPU with MPIaddress 15.

Networking procedure for each CPU station:

1. Select the CPU in the hardware configuration and then the menu function Edit/Object properties/General/Properties

2. Set the MPI address

3. Select MPI(1) 187.5 kbit/s

4. Confirm “Properties - MPI interface” with OK

5. Confirm “Properties CPU 315” with OK

6. Use the menu command Save and compile station to save the configuration

Select the object MPI network in the STEP7 project and then the menu function Extras/Define global data.

The table ”GD; Define global data – [MPI(1) (global data) –– Example]” isdisplayed.

You must now call the CPU stations in this table.

1. Click with the mouse in the field next to GD identifiers (the column is high-lighted).

2. Select CPU in the Edit menu.

3. A window ”Select CPU” is displayed. Click on the project Example. Thethree CPU stations PLC-CPU, MCP and HHU are displayed.

4. Select PLC-CPU/CPU315

5. The table now contains the entry PLC-CPU/CPU315

6. Click on the empty field alongside and repeat steps 2. to 5. for the stationsMCP and HHU, in this order.

7. You will then have a table with the three stations.

GD; Define global data – [MPI(1) (global data) –– Example]

GD identifiers PLC-CPU/CPU315

MCP/MCP-CPU

HHU/HHU-CPU

GD

GD

GD

Networking

Define global data

Table ofglobal data


3

07.2000



You can now make the entries for the MCP and HHU in the global data table .

1. Start in column PLC–CPU/CPU315 by selecting the first field.

2. Enter data area for reception or transmission from Fig. 3-4

For MCP/MCP–CPUAB120:8 is the entry for the receive area andEB118:8 is the entry for the transmit area.AB 8 bytes are received starting at AB120 andEB 8 bytes are transmitted starting at EB118.)

For HHU/HHU–CPUMD0:20 is the entry for the receive area andMD20:6 is the entry for the transmit area.(MD0:20 20 bytes are received starting at MD0 andMD20:6 6 bytes are transmitted starting at MD20.)

3. Declare the transmit and receive areas to be such, i.e. activate the appropri-ate field in the table. Then select Transmitter in the Edit menu. The transmitarea is then marked with “»” and highlighted.

4. The table with all its entries then looks like this:



MCP/MCP-CPU

HHU/HHU-CPU

GD >AB120:8 AB120:8

GD EB118:8 >EB118:8

GD >MB0:20 MB0:20

GD MB20:6 >MB20:6

Note

The order in which inputs are made (transmit, receive) affects the way in whichGD identifiers are assigned and should be noted carefully as shown by theabove example.

You now need to select Compile in the menu GD table.

The GD identifiers are generated during compilation. They are displayed intable as the result of compilation.



MCP/MCP-CPU

HHU/HHU-CPU

GD 1.1.1 >AB120:8 AB120:8

GD 1.2.1 EB118:8 >EB118:8

GD 2.1.1 >MB0:20 MB0:20

GD 2.2.1 MB20:6 >MB20:6

Enter areas fortransmitting andreceiving

Compilation


3

07.2000


Click on menu View/Reducing factors. The table below appears with the SRparameters.



MCP/MCP-CPU

HHU/HHU-CPU

SR 1.1 8 8

GD 1.1.1 >AB120:8 AB120:8

SR 1.2 8 8

GD 1.2.1 EB118:8 >EB118:8

SR 2.1 8 8

GD 2.1.1 >MB0:20 MB0:20

SR 2.2 8 8

GD 2.2.1 MB20:6 >MB20:6

The transmission rate for the MCP and HHU must be set.

The default setting is one transmission every 8 PLC cycles.

You must specify a value of 1, 2, 4 or 8. Only 4 and 8 are allowed for transmis-sion.

Example of a global data table with altered SR parameters:

Value 1 can be set for the receiver.



MCP/MCP-CPU

HHU/HHU-CPU

SR 1.1 4 1

GD 1.1.1 >AB120:8 AB120:8

SR 1.2 1 4

GD 1.2.1 EB118:8 >EB118:8

SR 2.1 4 1

GD 2.1.1 >MB0:20 MB0:20

SR 2.2 1 4

GD 2.2.1 MB20:6 >MB20:6

When you have changed the SR parameters, you must compile your configura-tion again (command Compile in menu GD table).

Setting scan rate

Altering SRparameters


3

07.2000



Click on menu View/GD status. The following table appears



MCP/MCP-CPU

HHU/HHU-CPU

GST

GDS 1.1

SR 1.1 4 1

GD 1.1.1 >AB120:8 AB120:8

GDS 1.2

SR 1.2 1 4

GD 1.2.1 EB118:8 >EB118:8

GDS 2.1

SR 2.1 4 1

GD 2.1.1 >MB0:20 MB0:20

GDS 2.2

SR 2.2 1 4

GD 2.2.1 MB20:6 >MB20:6

You now need to specify the status double words for GDS1.2 and GDS2.2 (re-ceive data).

Extract from the global data table:



MCP/MCP-CPU

HHU/HHU-CPU

GDS 1.2 AD108

GDS 2.2 MD26

Once you have entered the status, you must compile your configuration again.

SDB210 is created in the course of compilation. Transfer the SDB210 for theCPU program CPU315 to the PLC-CPU (PLC must be in the STOP state).

Procedure in STEP7:

1. Click on menu Target system/Load

2. In the download window, select PLC-CPU/CPU315 and confirm with OK.

3. Put PLC into RUN mode (restart)

MPI address 14 on the MCP must be set according to GD parameters1.1.1–1.2.1. The default MPI address 15 can be left unchanged on the HHU.The default settings for GP parameters 2.1.1...2.2.1 remain valid.

The hardware switch settings are described in:

Section 2.5 for MCP andSection 2.7 for HHU

Activate status

Transfer SDB210

Set MCP and HHU


3

07.2000


Before the HHU can exchange data with the PLC-CPU via the MPI interface,the GD parameters created must also be set in the HHU.

To set these parameters, proceed as follows:

HHU display Value Operator action

1. – Press the left-hand and right-hand keys in the 1stline together while the HHU is being booted.

2. REC-GD-No: 2 2 Use keys + and – to select the value and transferwith the AUTO key (2nd key from left in 1st line)

3. REC-GBZ-No: 1 1 Select and transfer

4. REC-OBJ-No: 1 1 Select and transfer

5. SEND-GD-No: 2 2 Select and transfer

6. SEND-GBZ-No: 2 2 Select and transfer

7. SEND-OBJ-No: 1 1 Select and transfer

When the last value is transferred, the HHU joins the “Waiting for PLC” queue.

Bit 7 in byte 0 of the output signal must be set to “1” (in the example M0.7: =TRUE) for data to be exchanged with the HHU.

Note:

The directional terms SEND and REC are applied as viewed by the HHU, i.e.SEND: HHU transmits data to the PLC-CPU.

The MPI address can be changed by switch S2 on the HHU (see Section 2.7),while the baud rate is changed with switch S1.

The switch settings corresponding to different MPI bus addresses for the HHUare shown in Table 2-11 in Section 2.7.

The delivery state is S1.3=OFF and S2.1...S2.4=ON (187.5 kBaud, MPI address 15)

The following parameter settings must be made on the FB1 for operator compo-nents MCP and HHU.

MCPNum := 1 (one MCP)MCP1In:= P#E118.0 (input signals MCP)MCP1Out:= P#A120.0 (output signals MCP)MCP1StatRec:= P#A108.0 (status double word)HHU:= 1 (HHU on MPI bus)HHUIn:= P#M20.0 (input signals BHG)HHUOut:= P#M0.0 (output signals BHG)HHUStatRec:= P#M26.0 (status double word)

References: /FB/, P3, “Basic PLC Program”

Two machine control panels can be operated with the SINUMERIK FM-NC.

The settings and configuration via SDB210 are the same as for the project “Example” for the 1st machine control panel and HHU.

The parameters assigned automatically via the communication configurationmust be set on the machine control panels.

The basic program parameters on FB1 in OB100 must be updated to effectmonitoring of both machine control panels.

Parameterizationof HHU

MPI addresssetting (HHU)

Example:Parameterizationof FB1 in basicPLC program

2nd machinecontrol panel


3

07.2000



3.5 Example of distribution of MPI addresses

The following diagram shows you an example of how MPI addresses aredistributed.


MCP


Address: MPI 1

ËËËËËËËËË


PLC-CPU

1st FM-NCNCU 570.2


Address: MPI 10

Address: MPI 6

Address:MPI 8PLC 320

Addr.:MPI 7

Operator panel with MMC OP 27


2nd FM-NCNCU 570.2


ËËËËËËËËË


PLC-CPU

3rd FM-NC NCU 570.2


Addr.:MPI 2

Fig. 3-5 Example of how MPI addresses are distributed

A description of how to set the addresses for the MMC and MCP modules canbe found in Section 3.2.

Overview


3

07.2000


A sample configuration for the OP 27 is included in the Toolbox for theSINUMERIK FM-NC (File “OP27_NCx.PDB”).

The MPI address for the OP 27 is determined when the module is configuredwith “ProTool”.

Call the following menu in this configuring tool:

“Edit / Properties / Parameters”

The following subdisplay appears:

“SIMATIC S7 - 300/400”

In this screen, you can set the following OP and network parameters:

� Address [ ] 10 is set here in the sample configuration

� Interface [ ] IF1 B is entered here in the sample configuration

� Baud rate [ ] 187.5 is entered here in the sample configuration

It is also necessary to set the MPI address of the module from/to which the OP27 is to read/write variables in display “SIMATIC S7 - 300/400”. This address isset to 3 in the sample configuration. In the example above, the OP 27 can readand write variables from the 3rd FM-NC.

The MPI addresses of the PLC-CPUs must be distributed such that addressesdo not overlap on the MPI bus (Note: PLC increments addresses for MPI (Cbus) nodes).

Since the default address for the PLC-CPU is “2”, PLC-CPUs will need to bestarted up individually if several are connected to the bus, i.e.

1. The PLC-CPU which is to be assigned the MPI address “7” must be linkedto the MPI bus first.

2. The address for this PLC-CPU must then be changed from “2” to “7” (seeSection 3.2).

3. The 2nd PLC-CPU is then connected to the MPI bus. Its MPI address re-mains unchanged as “2”.

Useful data telegrams are exchanged cyclically between the nodes within theGD circuits. The GD circuits are set up in the PLC via parameter block SDB210(transmit cycle, data areas, source and target addresses).

Although the following MPI nodes have an MPI address, they are addressedadditionally by the PLC-CPU via the so-called GD circuit number.

� MCP

� HHU

� Interface to customer operator panel

Note

The PLC-CPU in the SINUMERIK FM-NC is capable of addressing up to 4 de-vices via GD circuit numbers (MCP, HHU, interface to customer operator paneland, for example, 2nd MCP).

�

MPI address of OP 27

2 PLCs on the MPIbus

GD circuits,SDB210


3

07.2000




4


EMC and ESD Measures

4.1 Measures to suppress interference 4-70. . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4.2 Measures to protect ESD-sensitive components 4-71. . . . . . . . . . . . . . . . .

4

4

07.2000



4.1 Measures to suppress interference

To ensure safe, interference-free operation of the installation, it is essential touse the cables specified in the individual diagrams.

Both ends of the shield must always be connected conductively to theequipment enclosures.

Exception:

If external equipment (such as printers, programming devices, etc.) isconnected, standard shielded cables connected at one end may also be used.

These external devices may not be connected to the control during normal op-eration. However, if the system cannot be operated without them, then the cableshields must be connected at both ends. Furthermore, the external device mustbe connected to the control via an equipotential bonding lead.

To ensure that the entire installation (control, power section, machine) has thegreatest possible immunity to interference, the following EMC measures mustbe taken:

� Signal leads and load leads must be routed at the greatest possible distancefrom one another.

� The cables supplied by SIEMENS must be used as signal cables from andto the NC or PLC.

� Signal leads must not be routed close to strong external magnetic fields(e.g. motors and transformers).

� Pulse-carrying HC/HV leads must always be laid completely separately fromall other leads/cables.

� If signal leads cannot be laid at a sufficient distance from other leads, thenthey must be installed in shielded cable ducts (metal).

� The distance (noise field) between the following leads should be as small aspossible:

– Signal lead and signal lead

– Signal lead and associated equipotential bonding lead

– Equipotential bonding lead and PE conductor (routed together)

!Important

For further information about interference suppression measures and connec-tion of shielded cables, please refer to

References: /EMC/, EMC Guidelines

Shielded signalleads

Precautionarymeasures

4.1 Measures to suppress interference

4

07.2000


4.2 Measures to protect ESD-sensitive components

!Important

Handling of modules at risk from ESD:

� When electrostatic components are handled, it must be ensured thatpersonnel, workstation and packaging are properly earthed.

� As a general principle, electronic modules should only be touched if thisabsolutely unavoidable (owing to repair work, etc.). When you are handlingPCBs, therefore, make sure that you never touch any submodule pins orconducting paths.

� You may only touch components if

– you are constantly connected to earth by means of an anti-static chainyou are wearing anti-static shoes or anti-static shoes with earthing stripin conjunction with an anti-static floor surface.

– Modules must always be placed on a conductive surface (table withanti-static covering, electrically conductive foam rubber, anti-static pack-aging materials, anti-static transport container).

� Modules must always be placed on a conductive surface (table with anti-static covering, electrically conductive foam rubber, anti-static packagingmaterials, anti-static transport container).

� Modules must not placed near VDUs, monitors or television sets (not closerthan 10 cm from screen).

� Modules must not be allowed to come into contact with electricallyinsulating materials such as plastic foil, insulating table tops or clothingmade of synthetic fibres.

� Measurements may only be taken on modules if

– the measuring instrument is earthed (e.g. via PE conductor) or

– the measuring head on a potential-free instrument is discharged briefly(e.g. by being brought into contact with bare metal part of controlhousing) before the measurement is taken.

�

4.2 Measures to protect ESD-sensitive components

4

07.2000



5


Power On and Power-Up

5.1 Start-up sequence 5-74. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

5.2 Power on 5-74. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

5.3 Booting of system software 5-75. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.3.1 Booting of entire system 5-76. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.3.2 Booting of FM-NC (NCU 570.2) 5-78. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.3.3 Booting of PLC-CPU 5-79. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.3.4 MMC102/103 BIOS setup 5-80. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.3.5 Booting of MMC 5-81. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.3.6 Booting of machine control panel (MCP) 5-81. . . . . . . . . . . . . . . . . . . . . . . .

5

5

07.2000



5.1 Start-up sequence

All mechanical and electrical installation work must be complete. Before thesystem is started up, it is important to ensure that the control and its compo-nents power up correctly. It is also essential that the equipment is installed inaccordance with the EMC guidelines given in the previous section.

The start-up procedure is detailed below. The order in which the individual stepsare taken is not mandatory, but recommended:

1. Check that PLC Start-up has been completed successfully

2. Check the connection of the NC back-up battery (Section 2.3.5)

3. Check that SINUMERIK FM-NC powers up correctly

4. Transfer PLC user program and alarm texts

5. Set axis configuration

6. Set axis-specific machine data

– Setpoint matching

– Encoder matching

– Velocities

– Monitoring functions

– Spindle data, rotary axis

7. Perform axis and spindle test runs

8. Optimize drives

9. Save data

5.2 Power on

The installation should be inspected visually for any obvious faults or defects.Make sure that the mechanical installation of components is correct and thatelectrical connections are firmly in place. Make sure that all electrical connec-tions have been made correctly before switching on the power supply. Checkthe supply voltages 230 V AC and 24 V DC as well as the shields and earthingconnections.

Before commencing with start-up, check that the address and switch settings onthe MCP, HHU and PLC I/O devices are correct for your application. Reset themif required.


The components MCP, HHU and MMC can be switched on in any desired se-quence if they are physically installed.

Switch on the power supply on all components and on the mains supplymodule. However, the LEDs on the mains supply module may not indicate anyerrors/faults in the power supply.

Start-up sequence

Visual inspection

Address/switchsettings

Power onsequence

Power on

5.1 Start-up sequence

5

07.2000


5.3 Booting of system software

The system software is already loaded in the delivery state.The control is booted after the power supply is connected.

The following operator control and display elements are relevant for booting theSINUMERIK FM-NC (NCU 570.2):

� Error and status LEDs

� Start-up switch on FM-NC (NCU 570.2)

� Start-up switch on PLC-CPU

RUN_PRUN

STOPMRES

SF

BAF

DC5V

DIAG

SF

BAF

DC5VFRCERUN

STOP

PLC-CPU FM-NC (NCU 570.2)

Start-up switch

Error and status LEDs Memory module interface(JEIDA)

1 23

0

45

610

1514

1312

119 8 7Memory module

interface (S7 memory card with user program)

Fig. 5-1 Operator control and display elements for booting

Overview

Operator controland displayelements relevantto booting


5

07.2000



5.3.1 Booting of entire system

Since the PLC views the FM–NC as being an FM module, it boots it in thecourse of the S7–300 system boot.

When the PLC is booted, it detects the configuration level (rack configuration)by means of the “ID run” via the P-bus and then transfers the slot-dependentC-bus parameters (C-bus initialization via P-bus).

The communication bus (K bus) (MPI) then runs up on the communicationsmodule (COM). Data can now be exchanged according to the S7 protocol viathe K bus (MPI). The remaining configuration data (system data blocks) areloaded via the K bus (MPI) from the PLC, operator panel (OP) or programmer(PG) to the COM module of the FM–NC.

The configuration of the local P bus is also detected in the course of theS7–300–CPU system boot and transferred to the FM–NC (including the moduleaddress of the FM 354).

This process can only take place if the local P bus is configured in the SDB100.

The FM–NC configuration address is entered in parameternc_laddr: = of the basic program =B 100, Call FB1, DB7. The address is derived from theFM–NC slot. The slots are assigned from left to right as follows:

1 Power supply2 PLC–CPU3 Interface module4–11 Signal modules, FM–NC, FM 354

Table 5-1 FM–NC configuration address

Slot number FM–NC/FM 354 address

4 256

5 272

6 288

7 304

8 320

9 336

10 352

11 368

Example:

If the FM–NC is inserted in slot 10, then the parameters setting nc_laddr: =352must be written for FB1.

References: /S7H/, Manual

Overview

Basic bootingprocess

Booting of FM 354as 5th axis

I/O address of FM–NC and FM 354


5

07.2000


Note

The module addresses are displayed in the hardware configuration in the STEP7 project.

MPI

PLC–CPU

NCK

S7-300

FM–NC

MCP PG

(OP)

K bus

P bus

COM

FM 354

Operator panel withMMC 100/102

Local P bus

Fig. 5-2 Components involved in FM–NC booting process

Components involved in booting


5

07.2000



5.3.2 Booting of FM-NC (NCU 570.2)

After POWER ON, the packed NCK system software is fetched from the internalmemory (FLASH), unpacked, stored on the dynamic RAM and then processed.

There is a start-up switch on the NCU 570.2 (see Fig. 5-1). It is used in thestart-up process and can be operated by means of a screwdriver.

The following switch settings are relevant.

Table 5-2 Settings with the start-up switch of the FM-NC

Position Meaning

0 Normal booting from the internal memory (FLASH)

1 Booting from the internal memory and loading of default values

3 Switch to restoring of software and user data (see Section 11.4)

6 Updating of firmware and user data (see Section 12.1.1)

Booting of the software from the internal memory (start-up switch = 0/1) takesapproximately 1 minute and 30 seconds.

The booting status is displayed as follows:

� PLC-CPU: 5 V DC (green) � ONRUN (green) � flashesSTOP (yellow) � ONOther LEDs � OFF

Booting complete: 5 V DC (green) � ONRUN (green) � ONOther LEDs � OFF

� FM-NC (NCU 570.2): 5 V DC (green) � ONOther LEDs � OFF

Booting complete: 5 V DC (green) � ONDIAG (yellow) � flashes

(sign of life approx. 8 Hz)

� Local axis with measuring system (if present)Booting complete: 5 V DC (green) � ON

DIAG (yellow) � flashes (approx. 4 sec ON / 4 sec OFF)

� Local axis without measuring system (if present)Booting complete: 5 V DC (green) � ON

DIAG (yellow) � ON

Overview

Start-up switch

Booting times

Status displays(LEDs) duringbooting


5

07.2000


5.3.3 Booting of PLC-CPU

A GENERAL RESET erases the contents of the program memory in the PLC-CPU. The contents of the diagnostics buffer in the PLC-CPU are not erased.

There are two methods to effect a general reset:

1. Via STEP7 on the programming device

2. Via the PLC start-up switch on the CPU module

Table 5-3 Settings with the PLC start-up switch

Position Meaning

0 PLC RUN PROGRAMMING: RUN state. It is possible to intervene in thePLC program without activating a password.

1 PLC RUN: RUN state. The program can only be accessed for reading via theprogrammer. After activation of the password, it is possible to intervene in (i.e.change) the PLC program.

2 PLC STOP: STOP state.

3 MRES: A module reset (general reset function) can be executed with theswitch in this setting.

The following operation initiates a PLC RESTART:

Turn PLC start-up switch from STOP position to RUN position.

The following operations with the PLC start-up switch initiate a GENERALRESET of the PLC-CPU:

1. Turn operating mode switch to “STOP” position (set STOP operating state)

� LED STOP lights up.

2. Turn operating mode switch to “MRES” position and keep it there until STOPLED lights up again (request general reset)

� LED STOP goes out and lights up again.

3. Within 3 seconds, turn operating mode switch to settings STOP-MRES-STOP

� LED STOP flashes first at frequency of approx. 2 Hz and then lights up again

� LED FORCE lights up

If the switch is not kept in the MRES position for 3 seconds, then no generalreset is requested. The STOP LED also remains off if the switch does notchange positions STOP-MRES-STOP within 3 seconds.

PLC general reset

Operator inputs forPLC restart

Operator inputs forPLC general reset


5

07.2000



4. After LEDs STOP and FORCE are alight again, turn operating mode switchto the RUN position

� LEDs STOP and FORCE go out and LED RUN (green) lights up

� The PLC program memory is now erased, PLC is operating in cyclicmode

A GENERAL RESET erases the contents of the program memory in the PLC-CPU.

The contents of the diagnostics buffer in the PLC-CPU are not erased.

Note

If a GENERAL RESET is initiated (according to procedure described above)when the back-up battery is not installed, then the entire SRAM of the PLC iserased, i.e. the diagnostics buffer contents are also erased. These data canthen no longer be accessed.

If the switch is not kept in position “3” (MRES position) for 3 seconds, then nogeneral reset is requested. The STOP LED also remains off if the switch doesnot change positions STOP-MRES-STOP within 3 seconds.


The LEDs of the PLC-CPU are in the following state while the PLC-CPU isbeing booted:

� 5 V DC (green) � ON

� RUN (green) � flashes

� STOP (yellow) � ON

5.3.4 MMC102/103 BIOS setup

The defaults in the BIOS of the MMC102 can be displayed directly on thescreen during booting through selection of the key combination

� CTRL + ALT + ESC on a connected PC keyboard

� CTRL + ALT + Alarm acknowledge on a Qwerty keyboard.

The plug-and-play-capable Standard BIOS with Power Management with ELITE BIOS is called when booting the MMC103 by pressing the key

� DEL on a connected PC or Qwerty keyboard.

Note

The BIOS setup settings are described in

References: /BH/, Operator Components” manual

PLC statusdisplays duringbooting

MMC102/103

MMC103


5

07.2000


5.3.5 Booting of MMC

After the power supply has been switched on, the MMC is booted automatically.The system software is installed in the factory and is ready to run. The basicdisplay appears on the screen if the MMC has been booted successfully.

MMC100 / 100.2

If the MMC100 cannot establish a connection to the NC, then the message “waitfor NCU connection: “x” seconds” (“x” 0 1 to 60 seconds). If a connection hasstill not been established after this time, then rebooting takes place soon after.

Check the following:

� Is the FM-NC (NCU module) ready to operate (LED “DIAG” flashes at 3 Hz)?

� Is the MPI cable inserted, is cable attached properly to connector?

MMC 102 / 103

If the MMC102/103 is not booted, i.e. the screen remains dark, check the 24 VDC power supply. If the power supply is present at the power unit on theMMC102/103 and the seven-segment display on the rear panel does not lightup, then the MMC102/103 module is defective.

If the MMC102/103 is booted, but cannot establish a connection to the NC, thenthe message “Communications to NC failed” is output.

In this case, please check the following:

� Is the FM-NC (NCU module) ready to operate (LED DIAG” flashes at 3 Hz)

� Is the MPI cable inserted, is cable attached properly to connector?

� Is the baud rate in menu Start-up/MMC/operator panel set correctly? Itmust be set to 1.5 mbaud (password for protection level 2 required).

5.3.6 Booting of machine control panel (MCP)

The flashing LEDs on the MCP indicate that the panel is booting. When bootingis completed, the LEDs continue to flash until the MCP receives control tele-grams from the PLC.

�

MMCbooting

Problems duringbooting

MCP booting


5

07.2000




6


Parameterization of the FM-NC

6.1 Machine and setting data 6-84. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

6.2 Handling machine and setting data 6-85. . . . . . . . . . . . . . . . . . . . . . . . . . . . .

6.3 Protection level strategy 6-87. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

6.4 Operator control functions for start-up 6-89. . . . . . . . . . . . . . . . . . . . . . . . . .

6.5 Initialization of system 6-91. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

6.6 SINUMERIK FM–NC configuration/system data 6-92. . . . . . . . . . . . . . . . . . 6.6.1 General configuration 6-92. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

6.7 Memory configuration 6-96. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

6.8 Sequence of operations for initial start-up 6-100. . . . . . . . . . . . . . . . . . . . . . .

6.9 Sequence of operations for starting up a series machine 6-104. . . . . . . . . .

6.10 Axes and spindles 6-105. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.10.1 Axis configuration 6-105. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.10.2 Axis data 6-109. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.10.3 Encoder matching (axis) 6-111. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.10.4 Setpoint routing (axis) 6-120. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.10.5 Velocity/speed matching 6-121. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.10.6 Monitoring functions (axis) 6-129. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.10.7 Reference point approach 6-135. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.10.8 Reference point approach for stepper motors 6-138. . . . . . . . . . . . . . . . . . . . 6.10.9 Extension to 5th axis 6-139. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.10.10 Basic settings for operator panel 6-140. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.10.11 Configuration and machine data of local P bus of FM-NC 6-141. . . . . . . . . . 6.10.12 Spindle data 6-143. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.10.13 Spindle configuration 6-145. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.10.14 Encoder matching (spindles) 6-145. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.10.15 Speeds and setpoint adjustment (spindles) 6-147. . . . . . . . . . . . . . . . . . . . . . 6.10.16 Spindle positioning 6-149. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.10.17 Spindle synchronization 6-150. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.10.18 Monitoring functions (spindles) 6-151. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

6.11 Start-up of functions 6-153. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

6

6

07.2000



6.1 Machine and setting data

Machine and setting data are used to adjust the control so that it matches themachine.

The machine and setting data are divided into the following areas:

Table 6-1 Overview of machine and setting data

Area Designation

Machine data

From 1000 to 1799 Machine data for drives

From 9000 to 9999 Machine data for operator panel

From 10000 to 18999 General machine data

From 19000 to 19999 Reserved

From 20000 to 28999 Channel-specific machine data


From 30000 to 38999 Axis-specific machine data


Setting data

From 41000 to 41999 General setting data

From 42000 to 42999 Channel-specific setting data

From 43000 to 43999 Axis-specific setting data

The machine and setting data are listed in:

References: /LIS/, Lists

Option data are used to enable options. They are included in the scope of deliv-ery of the relevant option.

Appropriate displays are provided for the input of machine data. To selectdisplays:

When the Area switchover key is selected on the MMC, a menu bar with theareas “Machine”, “Parameters”, “Program”, “Services”, “Diagnosis” and“Start-up” is displayed. Select Start-up and then Machine data.

Note

Machine data can be input only if the password for protection level 2“EVENING” has been set.

Parameterization

Overview ofmachine andsetting data

Option data

Input of machinedata

6.1 Machine and setting data

6

07.2000


6.2 Handling machine and setting data

MD and SD are addressed by number or by name (identifier). The number andname are displayed on the MMC. The following must also be noted:

� Active

� Protection level

� Unit

� Default value

� Value range

The levels at which a data becomes active are listed below in order of priority. Achange to the data takes effect after:

� POWER ON (po) Switch FM-NC power supply OFF/ON

� NEW_CONF (cf)

– Set MD active on MMC

– RESET key on operating unit

– Changes at block ends in program mode

� RESET M2/M30 at program end

� RESET (re) RESET key on operating unit

� IMMEDIATE (so) after entry of value

Protection level 4 or higher (keyswitch position 3) must be activated to displaymachine data.

The appropriate protection level must generally be enabled by means of pass-word “EVENING” to start up the system.

The unit refers to the default setting for the machine data SCALING_FACTOR_USER_DEF_MASK andSCALING_FACTOR_USER_DEF andSCALING_SYSTEM IS METRIC = 1.

Depending on the MD SCALING_SYSTEM_IS_METRIC, the physical units dif-fer as follows:

MD 10240 = 1 MD 10240 = 0

mm inch

mm/min inch/min

m/s2 inch/s2

m/s3 inch/s3

mm/rev inch/rev

“–” is entered in the field if the MD is not based on any physical unit.

Number and identi-fier

Active

Protection level

Unit


6

07.2000



This is the value to which the machine data is preset.

Some machine data are provided with different default values depending on theNCU used.

Note

When data is entered via the MMC, the input value is limited to 10 places plusdecimal point and sign.

Specification of the input limits. If no value range is specified, the data type de-termines the input limits and “∗∗∗ ” is entered in the field.

BOOLEAN Machine data bit (1 or 0)BYTE Integer values (from –128 to 127)DOUBLE Real and integer values

(from � 4.19*10–307 to � 1.67*10308)DWORD Integer values (from –2.147*109 to 2.147*109 )STRING Character string (maximum 16 characters) consisting

of capital letters with digits and underliningUNSIGNED WORD Integer values (from 0 to 65536)SIGNED WORD Integer values (from –32768 to 32767)UNSIGNED DWORD Integer values (from 0 to 4294967300)SIGNED DWORD Integer values (from –2147483650 to 2147483649)WORD Hex values (from 0000 to FFFF)DWORD Hex values (from 00000000 to FFFFFFFF)FLOAT DWORD Real values (from �8.43∗ 10–37 to �3.37∗ 1038)

The default setting of the MDs is not specific to any technology. As an aid forthe initial start-up of machines, three example MD files are supplied on the 1sttool box diskette with the FM–NC. The purpose of these files is to support initialstart-up with respect to the MD settings for specific technologies.

� md_fr_a.tea Example of MD setting for 4-axis milling machine with local P bus (FM 354)

� md_dr_a.tea Example of MD setting for lathe with analog drive

� md_dr_s.tea Example of MD setting for lathe with stepper motor drive

Please refer to the supplied readme file: readme.txt for further details.

Default value

Value range(minimum andmaximum value)

Data type

Example of MD file


6

07.2000


6.3 Protection level strategy

Protection levels for enabling data areas are implemented in the SINUMERIKFM-NC. There are protection levels 0 to 7; is the highest and 7 is the lowest.

Protection levels

� 0 to 3 are disabled by means of a password and

� 4 to 7 by means of keyswitch positions.

The operator only has access to information protected by one particular leveland the levels below it. The machine data are assigned various protection lev-els as standard.

Protection level 4 (keyswitch position 3) and higher is required to displaymachine data.

The appropriate protection level must generally be disabled with password“EVENING” for start-up procedures.

Note

For information about changing protection levels, refer to

References: /BA/ Operator’s Guide/FB/ A2, “Various Interface Signals”

Table 6-2 Protection level strategy

Protection level Locked by Area

0 Password Siemens

1 Password: SUNRISE (default) Machine manufacturer

2 Password: EVENING (default) Service engineer

3 Password: CUSTOMER (default) User

4 Keyswitch position 3 Programmer, machine setter

5 Keyswitch position 2 Qualified operator

6 Keyswitch position 1 Trained operator

7 Keyswitch position 0 Semi-skilled operator

Protection levels 0 to 3 require the input of a password. The password for level0 provides access to all data areas. The passwords can be changed afteractivation (not recommended). If, for example, the passwords have beenforgotten, then the system must be re-initialized (NCK general reset). This setsall passwords back to the standard of this software version.

The password remains valid until it is reset with softkey Delete password. APOWER ON does not reset the password.

Protection levels

Protection levels 0 – 3


6

07.2000



Protection levels 4 to 7 require a particular keyswitch setting on the machinecontrol panel. Three keys of different colours are provided for this purpose.Each of these keys is capable of providing access to particular data areas. Theassociated interface signals are located in DB10, DBX56.

Table 6-3 Meaning of keyswitch positions

Key colour Switch position Protection level

All 0 = Remove key position 7

Black 0 and 1 6–7

Green 0 to 2 5–7

Red 0 to 3 4–7

The user has the option of changing the protection level priority. Only protectionlevels of a lower priority may be assigned to machine data. Levels of a lower orhigher priority may be assigned to setting data.

Example:

%_N_SGUD_DEF File for global variables;$PATH=/_N_DEF_DIRREDEF $MA_CTRLOUT_SEGMENT_NR APR 2 APW 2

(APR ... read authorization)REDEF $MA_ENC_SEGMENT_NR APR 2 APW 2

(APW ... write authorization)REDEF $SN_JOG_CONT_MODE_LEVELTRIGGRD APR 2 APW 2M30

The file becomes active when the next _N_INITIAL_INI is read in.

Different protection levels are specified for writing (changing) or reading (partprogram or PLC).

Example:

MD 10000 is protected by levels 2 / 7, i.e. protection level 2 (password) must bedisabled to write it and protection level 7 to read it.

Keyswitch position 3 or higher is required to reach the machine data area.

References: /BA/, Operator’s Guide/FB/, A2, “Various Interface Signals”

Protection levels 4 – 7

Redefinition ofprotection levels


6

Start–up

Machinedata

07.2000


6.4 Operator control functions for start-up

The operator control functions are divided into the areas Program, Machine,Services, Parameters, Diagnosis and Startup.

The Diagnosis and Startup areas are the most important with respect tostart-up.

After pressing the area switchover key, you can reach the area menu bar fromany operator control area.

The area and basic display are selected with the Start–up softkey. From thisbasic display menus can be selected for:

� Machine data

� User views (only MMCs 102/103)

� NC

� PLC

� Drives / servo (only MMCs 102/103)

� MMC

� Tool management

The following menu is selected with the Machine data softkey in the areaStart–up:

OK

Fig. 6-1 Basic display for machine data

Overview


6

Start-up

07.2000



The Start-up softkey can be used to select menus for:

� Alarms

� Messages

� Alarm log (only MMC103)

� Service display

� PLC start–up

References: /BA/, Operator’s Guide

The software versions of the control system can be called by selecting Servicedisplays/Version in the operator control area Diagnosis.

The following start-up functions can be called with softkey NC in the Start-upmenu.

� Normal booting

... initiates a “RESET” in the FM–NC.

� Booting with default values (start-up mode)

... initiates a “RESET” in the FM–NC followed by a booting operation with thedefault values.

!Important

User data are deleted or overwritten. See Section 11.7, heading “Handling ofmachine data”.

� Start software update

... initiates the update request (see Section 12.1) in the FM–NC.

The start-up switch on the FM-NC determines the method by which the FM-NCis booted. The following switch settings are relevant for the start-up process:

� 0 – Normal booting from internal memory (FLASH)

� 1 – Booting from internal memory and start-up with default values

� 3 – Switch to restoring of complete software of the NCU570.2

� 6 – Start-up from PCMCIA and switch to “update mode” of the completeFM-NC software.

The MMC provides a service menu to support axis start-up:

Diagnosis/Service display/Service axes

This menu displays axis parameters (following error, etc.) which support axisstart-up.

SW version

Start-up switch(SW) on MMC

Start-up switch(HW) on FM-NC

Axes servicedisplay


6

07.2000


6.5 Initialization of system

The initialization process establishes a basic state. The buffered storage areasare initialized and default values stored in the system assigned to the data. Thecontrol cannot power up correctly unless this basic state is established. An ini-tialization operation must be carried out

� when the system is switched on for the first time,

� in the case of a hardware defect and

� after data have been lost.

The FM–NC can detect whether the stored RAM contains valid data. If it doesnot, the system is automatically initialized with default values.

This initialization process can also be initiated through appropriate inputs via theMMC with subsequent NCK reset:Start-up/NC/Start-up switch.

After an initialization process, the FM–NC can power up without any error mes-sages and the system is now ready for initial or series start-up.

To initialize the system, the operations listed below must be performed in theorder specified:

1. Switch on FM–NCWhen the FM–NC is booted for the first time (after initial insertion of battery),the contents of the SRAM are deleted and the machine data set to defaultvalues.

2. Execute PLC overall reset.A PLC overall reset can be implemented in 2 different ways:

– Via the programmer with STEP7

– Via the PLC start-up switch on the front panel of the PLC–CPU.

3. Load the PLC basic program with the programmer. Transfer the basic program to the PLC–CPU.

4. Switch control (CPU 314 with FM-NC) off/onThe control powers up with default data and PLC basic program.

The MMC area (operator panel area) need not be initialized. The system soft-ware is loaded ready to run at the factory.

Loading of manufacturer data and of languages other than the standard for theMMC 100 is described in Section 8.

General

FM–NCinitialization

MMC 100initialization

6.5 Initialization of system

6

07.2000



6.6 SINUMERIK FM–NC configuration/system data

6.6.1 General configuration

The control operates according to time cycles which are defined via machinedata. The basic system clock cycle is defined in seconds; the other time cyclesare calculated through multiplication with the basic system clock cycle.

Table 6-4 Control time cycles

Machine data Name Example

10050: SYSCLOCK_CYCLE_TIME Basic system clock cycle MD 10050 = 0.006 s ––> 6 ms

10060: POSCTRL_SYSCLOCK_TIME_RATIO Factor for position controlclock cycle (LT)

MD 10060 = 1 ––> 1 � 6 ms = 6 ms

10070: IPO_SYSCLOCK_TIME_RATIO Factor for interpolatorclock cycle

MD 10070 = 3 ––> 3 � 6 ms = 18 ms

Note

Only in exceptional cases may the values entered deviate slightly from thisbasic setting (in default values).

The values must be adjusted such that the control operates reliably with the setfunctionality.

The recommended optimization procedure is described below:

� Define the desired number of axes with time cycles set to default values.

� Adjust time cycles as desired and start a program in the AUTOMATIC mode.

If no alarms occur which indicate timing problems on the position control or in-terpolator levels, then the settings can be transferred. If the set time cycles aretoo short, then the alarm “4240 MD standard values for IPO and positional cycleloaded” is displayed and the appropriate default (standard) values are loaded.

The control uses the following physical quantities for internal calculation pur-poses regardless of the selected basic system (metric or inch):

Linear position 1 mmAngular position 1 degreeLinear velocity 1 mm/sAngular velocity 1 degree/sLinear acceleration 1 mm/s2

Angular acceleration 1 degree/s2

Linear jerk 1 mm/s3

Angular jerk 1 degree/s3

Time 1 sServo gain factor 1/sRotational feedrate 1 mm/degreeLinear position (compensation value) 1 mmAngular position (compensation value) 1 degree

Control time cycles

Optimization oftime cycles

Internal physicalquantities


6

07.2000


A control system is switched over from the metric to inch system by means ofMD 10240: SCALING_SYSTEM_IS_METRIC (basic system metric, active afterPOWER ON). The additional conversion factor is specified in MD 10250: SCAL-ING_VALUE_INCH (conversion factor for switchover to INCH system, factor =25.4). The existing data are converted to inches after power ON and displayed.After switchover data must be entered in inches.

The basic programming setting (G70, G71) is switched over on a channel-spe-cific basis in MD 20150: GCODE_RESET_VALUES [12].

The standard units for the machine data physical quantities are as follows:

Physical quantity Metric InchLinear position 1 mm 1 inchAngular position 1 degree 1 degreeLinear velocity 1 mm/min 1 inch/minAngular velocity 1 rev/min 1 rev/minLinear acceleration 1 mm/s2 1 inch/s2

Angular acceleration 1 rev/s2 1 rev/s2

Linear jerk 1 mm/s3 1 inch/s3

Angular jerk 1 rev/s3 1 rev/s3

Time 1 s 1 sServo gain factor 1/s 1/sRotational feedrate 1 mm/rev 1 inch/revLinear position (compensation value) 1 mm 1 inchAngular position (compensation value) 1 degree 1 degree

The physical quantities for the input/output of machine and setting data (V24,MMC 100) can be defined systemwide viaMD 10220: SCALING_USER_DEF_MARK (activation of scaling factors) andMD 10230: SCALING_FACTORS_USER_DEF (physical quantities scaling fac-tors).

If the appropriate activation bit is not set in MD 10220 (activation of scaling fac-tors), then scaling is implemented internally with the conversion factors listedbelow (default setting, exception servo gain factor).

If all bits are set in MD 10220 and if the default settings are to remain valid, thenthe following scaling factors must be entered in MD 10230.

Table 6-5 Physical quantities for inputs/outputs

Index No. Physical quantity Input/output Internal unit Scaling factor

0 Linear position 1 mm 1 mm 1

1 Angular position 1 degree 1 degree 1

2 Linear velocity 1 mm/min 1 mm/s 0.016666667

3 Angular velocity 1 rev/min 1 degree/s 6

4 Linear acceleration 1 m/s2 1 mm/s2 1000

5 Angular acceleration 1 rev/s2 1 degree/s2 360

6 Linear jerk 1 m/s3 1 mm/s3 1000

7 Angular jerk 1 rev/s3 1 degree/s3 360

8 Time 1 s 1 s 1

Switchover frommetric to inch system

Physical quantitiesfor inputs/outputs


6

07.2000



Table 6-5 Physical quantities for inputs/outputs

Index No. Scaling factorInternal unitInput/outputPhysical quantity

9 Servo gain factor 1m/min � mm 1/s 16.66666667

10 Rotational feedrate 1 mm/rev 1 mm/degree 1/360

11 Linear position (compensation value) 1 mm 1 mm 1

12 Angular position (compensation value) 1 degree 1 degree 1

If the activation bit is set and the default settings retained, then the factors spe-cified above correspond to those in MD 10230 (scaling factors for physicalquantities).

Input values for machine data

Internal physical quantity

MD 10230Scaling factor

MD 10220Scaling factoractivated?

Internal scaling

no

yes

Fig. 6-2 Changing physical quantities

Example:

The user wishes to enter the linear velocity in m/min. The internal physicalquantity is mm/s.

min � 1 m � 60 s = 1000/60 [mm/s] = 16.666667

1 m �1000 mm �1 min[m/min] =

The machine data must be entered as follows:

MD 10220: SCALING_USER_DEF_MASK = H4(activation of new factor) and

MD 10230: SCALING_FACTORS_USER_DEF [2] = 16.6666667(scaling factor for linear velocity in m/min)

The machine data are automatically converted to these physical quantities afterinput of the new scale and power ON. The new values are displayed on theMMC and can then be saved.

The unit of the physical quantities for programming in the part program is speci-fied in the Programming Guide.


6

07.2000


The internal control calculation resolutions are entered inMD 10200: INT_INCR_PER_MM (calculation resolution for linear positions) andMD 10210: INT_INCR_PER_DEG (calculation resolution for angular positions).

The default value for this machine data is “1000”. The control thus calculates asstandard in 1/1000 mm or 1/1000 degrees. If greater accuracy is required, onlythese two machine data need to be changed. It is useful to enter machine datain powers of 10 (100, 1000, 10000). Rounding (and thus also falsification) of theinternal values is implemented only for finer units. However, it is essential thatthe measuring system is adapted to this degree of accuracy. The internal cal-culation resolution also determines the accuracy with which positions and se-lected offset functions are calculated. Changes to the MD have no influence onthe velocities and cycle times which can be attained.

The number of decimal places for position values on the operator panel screenmust be set in MD 9004: DISPLAY_RESOLUTION (input resolution).

Exception:

On MMCs 100/100.2/102, the spindle speed is always displayed with three decimal places regardless of the setting in MD 9004. On MMC103 the displayresolution is determined by MD9010: SPIND_DISPLAY_RESOLUTION.

Machine data for velocities and positions are not or only slightly limited by theinput limits in the machine data. The input value limitation depends on what val-ues can be displayed and input on the operator panel.

This limit is reached at 10 digit positions plus decimal point plus sign.

Internal calculationresolutions

Input and displaylimit values


6

07.2000



6.7 Memory configuration

The NCU 570.2 has the following hardware configuration:

� DRAM � 4 MB

� FLASH � 4 MB

� Buffered SRAM � 0.5 MB

� PCMCIA � 4 MB

The memory areas for user data in the NC are preset to suit most user require-ments during an NCK general reset. The following areas can be adjusted toachieve optimum utilization of the available user memory:

� Tool offsets

� User variables

� R parameters

� Compensations (e.g.: LEC)

� Protection zones

� Frames

The memory must be sectionalized before commencement of the actual start-upprocess because all buffered user data (e.g. part programs, drive data are lostwhen the memory is re-allocated.

Machine data, setting data and options are not erased.

The areas for user data (general, channel-specific and axis-specific) are set todefault values during control initialization, thus ensuring that the control powersup reliably. The machine manufacturer has the possibility of entering data whichchange the memory partitioning (SRAM) within individual subareas (e.g. tooloffsets, user variables, R parameters, macros). This applies to

MD 10010: ASSIGN_CHAN_TO_MODE_GROUP (cannot be altered withFM_NC) and all machine data within the range ofMD 18000 to 18999 (general MDs),MD 28000 to 28999 (channel-specific MDs) andMD 38000 to 38999 (axis-specific MDs).

The memory (SRAM) should be structured during system initialization if possiblesince all buffered user data (e.g. part programs, drive boot files) are lost whenthe memory is re-partitioned! Options as well as machine and setting data areretained.

These machine data become active after power ON. If the machine data for thememory configuration (SRAM, DRAM) are set such that the memory cannot bestructured meaningfully (e.g. insufficient memory capacity), the standard config-uration is applied and an alarm displayed.

Hardwareconfiguration

Memory areas

Changing memoryareas


6

07.2000


Note

The user should first check whether sufficient memory is available (MD 18050)before data areas are enlarged (e.g. local user variables or function parame-ters). If more dynamic memory is required than is actually available, then theSRAM will also be erased during the next booting process without prior warn-ing and all MD set to their default values.

References: /DA/, Diagnostics Guide/FB/, S7, “Memory Configuration”

!Danger

If the memory is not partitioned immediately during system initialization, all con-trol data will be lost! Before machine data changes are made, all NC and drivedata must be backed up (see Section 11). To back up NC data, please proceedas follows:

� Change machine data (including MDs for memory partitioning)� Back up data� Initiate NCK power-up� Load data back to the control� Initiate NCK power-up


6

07.2000



The following machine data cause a re-configuration of the control SRAM inindividual cases when their contents are changed. When a change is made, thealarm “4400 MD alteration will cause reorganization of buffer (data loss!)” is gen-erated. When this alarm is output, all data must be backed up because all buff-ered user data will be erased during the next power-up.

MD 10010: ASSIGN_CHAN_TO_MODE_GROUP[n] MD 18080: MM_TOL_MANAGEMENT_MASK (tool management memory)MD 18082: MM_NUM_TOOL (number of tools)MD 18084: MM_NUM_MAGAZINE (number of magazines)MD 18086: MM_NUM_MAGAZINE_LOCATION (number of magazine locations)MD 18090: MM_NUM_CC_MAGAZINE_PARAM (number of magazine data)MD 18092: MM_NUM_CC_MAGLOC_PARAM (number of magazine locationdata)MD 18094: MM_NUM_CC_TDA_PARAM (number of tool-specific data)MD 18096: MM_NUM_CC_TOA_PARAM (number of TOA data)MD 18098: MM_NUM_CC_MON_PARAM (number of monitoring data)MD 18100: MM_NUM_CUTTING_EDGES_IN_TOA (tool offsets per TOA mod-ule)MD 18110: MM_NUM_TOA_MODULES (number of TOA modules)MD 18118: MM_NUM_GUD_MODULES (number of GUD files)MD 18120: MM_NUM_GUD_NAMES_NCK (number of global user variables)MD 18130: MM_NUM_GUD_NAMES_CHAN (number of channel-specific uservariables)MD 18140: MM_NUM_GUD_NAMES_AXIS (number of axis-specific user vari-ables)MD 18150: MM_GUD_VALUES_MEM (memory location for user variables)MD 18160: MM_NUM_USER_MACROS (number of MACROS)MD 18190: MM_NUM_PROTECT_AREA_NCKC (number of protection zones)MD 18230: MM_USER_MEM_BUFFERED (user memory in SRAM)MD 18270: MM_NUM_SUBDIR_PER_DIR (number of subdirectories)MD 18280: MM_NUM_FILES_PER_DIR (number of files)MD 18290: MM_FILE_HASH_TABLE_SIZE (hash table size for files of a direc-tory)MD 18300: MM_DIR_HASH_TABLE_SIZE (hash table size for subdirectories)MD 18310: MM_NUM_DIR_IN_FILESYSTEM (number of directories in passivefile system)

MD 18320: MM_NUM_FILES_IN_FILESYSTEM (number of files in passive filesystem)MD 18330: MM_CHAR_LENGTH_OF_BLOCK (max. length of an NC block)MD 18340: MM_NUM_CEC_NAMES (number of LEC system variables)MD 18342: MM_CEC_MAX_POINTS[n] (max. number of intermediate points)MD 18350: MM_USER_FILE_MEM_MINIMUM (minimum user memory inSRAM)MD 28050: MM_NUM_R_PARAM (number of channel-specific R parameters)MD 28080: MM_NUM_USER_FRAMES (number of settable frames)MD 28085: MM_LINK_TOA_UNIT (assignment of a TO unit to a channel)MD 28200: MM_NUM_PROTECT_AREA_CHAN (number of files for protectionzones)MD 38000: MM_ENC_COMP_MAX_POINTS [n] (number of interpolation pointswith interpol. compensation)MD 38010: MM_QEC_MAX_POINTS (number of values for QEC)(not relevant for FM-NC)

Erasure of SRAMthrough MDchange


6

07.2000


Exception:

A change to MD 18350: MM_USER_FILE_MEM_MINIMUM results in re-config-uration only in cases where the unassigned SRAM for the passive file system islower than defined in MD 18350.

MD 18060: INFO_FREE_MEM_STATIC (display data of unassigned staticmemory).

This data cannot be written! The data contents specify how much SRAM isavailable for the passive file system at the instant of power-up. After a systeminitialization process, the maximum available memory in the file system must beread. If changes are made to machine data which influence the buffer require-ment (e.g. global user variables, number of points for LEC), then the amount ofmemory available for the passive file system also changes. The minimum sizeof the passive file system is defined inMD 18350: MM_USER_FILE_MEM_MINIMUM and is calculated on the basis ofMD 18230: MM_USER_MEM_BUFFERED minus all other buffered user data.

MD 18050: INFO_FREE_MEM_DYNAMIC (display data of unassigned dynamicmemory)

This data cannot be written! The data contents specify how much DRAM is cur-rently available for the enlargement of unbuffered user data areas by means ofmachine data.

Displaying unas-signed SRAM andDRAM


6

07.2000



6.8 Sequence of operations for initial start-up

When the system is started up for the first time, it is advisable to work throughthe following points in succession. To assist the user, the most important ma-chine data of the individual subareas are listed below. If further information isrequired, the user can refer to Chapters in this Guide specified in brackets. Adetailed description of the machine data and interface signals is given in thefunction descriptions referred to in the lists.

� Control system design

� Connection of components

� Cabling, jumpering, voltages

� Machine data

� Switch on control (CPU and FM–NC)

� NCK automatically loads default values

� PLC overall reset (with SK in Overall reset mode menu)

� Load PLC basic program via programmer

� Set options

� Define memory areas for user data which deviate from default settings (seeSection 6.7)

MD 10010: ASSIGN_CHAN_TO_MODE_GROUP[n] (cannot be changedfor FM-NC)MD 18000 to MD 18999MD 28000 to MD 28999MD 38000 to MD 38999

� Switch control off/on

Load the PLC user program using the programmer and incorporate into the PLCbasic program.

References: /S7H/, Manual/FB/, P3; “Basic PLC Program”

The followingsequence applies for the MMCs 100/100.2

� Switch off MMC

� Switch on MMC100 while actuating key “6” on the operator panel or switchon MMC100.2 and actuate key “6” on the operator panel as soon as theserial number appears on the display

� Load manufacturer data to MMC (Section 11.7)

Cycle alarm texts, error and operational message texts

� Switch MMC off/on

Overview

Check essentialpreconditions

Initialize system(Section 6.5)

Load PLC userprogram

Enter user data foroperator panel


6

07.2000


� Enter basic settings for operator panel (Section 6.10.10)MD 9000: LCD_CONTRAST (only MMC100/100.2 with mono display)MD 9001: DISPLAY_TYPE (for MMCs 100/100.2)MD 9002: DISPLAY_MODE (for MMCs 100/100.2)MD 9003: FIRST_LANGUAGE (for MMCs 100/100.2)MD 9004: DISPLAY_RESOLUTIONMD 9006: DISPLAY_BLACK_TIME (for MMCs 100/100.2)

� NCK machine data

– Control system time cycles (Section 6.6.1)MD 10050: SYSCLOCK_CYCLE_TIMEMD 10060: POSCTRL_SYSCLOCK_TIME_RATIOMD 10070: IPO_SYSCLOCK_TIME_RATIO

– Control system calculation resolutions (Section 6.6.1)MD 10200: INT_INCR_PER_MMMD 10210: INT_INCR_PER_DEG

– Scaling machine data (Sections 6.6.1 and 6.2)MD 10220: SCALING_USER_DEF_MASK [n]MD 10230: SCALING_FACTORS_USER_DEF [n]MD 10240: SCALING_SYSTEM_IS_METRICMD 10250: SCALING_VALUE_INCHMD 30300: IS_ROT_AX

– Axis assignments (Section 6.10.1)MD 20050: AXCONF_GEOAX_ASSIGN_TAB [n]MD 20060: AXCONF_GEOAX_NAME_TAB [n]MD 20070: AXCONF_MACHAX_USED [n]MD 20080: AXCONF_CHANAX_NAME_TAB [n]

� Initiate NCK power-up

� Axis and spindle: Enter machine data for

– Assignment of actual values and setpoints (Sections 6.10.2 and 6.10.15)MD 30110: CTRLOUT_MODULE_NR [n]MD 30130: CTRLOUT_TYPE [n]MD 30220: ENC_MODULE_NR [n]MD 30230: ENC_INPUT_NR [n]MD 30240: ENC_TYPE [n]MD 30310: ROT_IS_MODULOMD 30320: DISPLAY_IS_MODULO

– Encoder matching (Sections 6.10.3 and 6.10.14)MD 31000: ENC_IS_LINEAR [n]MD 31010: ENC_GRID_POINT_DIST [n]MD 31020: ENC_RESOL [n]MD 31030: LEADSCREW_PITCHMD 31040: ENC_IS_DIRECT [n]MD 31050: DRIVE_AX_RATIO_DENOM [n]MD 31060: DRIVE_AX_RATIO_NUMERA [n]MD 31070: DRIVE_ENC_RATIO_DENOM [n]MD 31080: DRIVE_ENC_RATIO_NUMERA [n]

Enter control configuration

Start up axis andspindle


6

07.2000



Start up axis and spindle (continued)

� Axis-specific: Enter machine data for

– SSI encoderMD 14000: ENC_SSI_BAUD_RATEMD 34400: ENC_SSI_STATUSMD 34410: ENC_SSI_MESSAGE_LENGTHMD 34420: ENC_SSI_MESSAGE_FORMAT

– Axis velocities (Section 6.10.5)MD 32000: MAX_AX_VELOMD 32010: JOG_VELO_RAPIDMD 32020: JOG_VELOMD 34020: REFP_VELO_SEARCH_CAMMD 34040: REFP_VELO_SEARCH_MARKER [n]MD 34070: REFP_VELO_POSMD 36200: AX_VELO_LIMIT [n]

– Axis control (Section 6.10.5)MD 32200: POSCTRL_GAINMD 32300: MAX_AX_ACCEL

– Axis monitoring functions (Section 6.10.6)MD 36000: STOP_LIMIT_COARSEMD 36010: STOP_LIMIT_FINEMD 36030: STANDSTILL_POS_TOLMD 36040: STANDSTILL_DELAY_TIMEMD 36060: STANDSTILL_VELO_TOLMD 36100: POS_LIMIT_MINUSMD 36110: POS_LIMIT_PLUSMD 36300: ENC_FREQ_LIMIT[n]MD 36400: CONTOUR_TOL

– Axis reference point approach (Section 6.10.7)MD 34000: REFP_CAM_IS_ACTIVMD 34010: REFP_CAM_DIR_IS_MINUSMD 34030: REFP_MAX_CAM_DISTMD 34050: REFP_SEARCH_MARKER_REVERSE [n]MD 34060: REFP_MAX_MARKER_DIST [n]MD 34080: REFP_MOVE_DIST [n]MD 34090: REFP_MOVE_DIST_CORR [n]MD 34100: REFP_SET_POS [n]MD 34110: REFP_CYCLE_NRMD 34200: ENC_REFP_MODE [n]MD 34300: ENC_REFP_MARKER_DIST [n]MD 34310: ENC_MARKER_INC [n]MD 34320: ENC_INVERS [n]MD 34330: REFP_STOP_AT_ABS_MARKER [n]


6

07.2000


Start up axis and spindle (continued)

� Spindle-specific: Enter machine data for

– Spindle definition (Section 6.10.12)MD 30300: IS_ROT_AXMD 30320: DISPLAY_IS_MODULOMD 35000: SPIND_ASSIGN_TO_MACHAXMD 35010: GEAR_STEP_CHANGE_ENABLEMD 35040: SPIND_ACTIVE_AFTER_RESETMD 35500: SPIND_ON_SPEED_AT_IPO_START

– Speeds (Section 6.10.15)MD 35100: SPIND_VELO_LIMITMD 35110: GEAR_STEP_MAX_VELO [n]MD 35120: GEAR_STEP_MIN_VELO [n]MD 35200: GEAR_STEP_SPEEDCTRL_ACCEL [n]MD 35220: ACCEL_REDUCTION_SPEED_POINTMD 35230: ACCEL_REDUCTION_FACTOR

– Spindle positioning (Section 6.10.16)MD 35210: GEAR_STEP_POSCTRL_ACCEL [n]MD 35300: SPIND_POSCTRL_VELOMD 35350: SPIND_POSITIONING_DIRMD 36000: STOP_LIMIT_COARSEMD 36010: STOP_LIMIT_FINEMD 32200: POSCTRL_GAINMD 36400: CONTOUR_TOL

– Spindle synchronization (Section 6.10.17)MD 34090: REFP_MOVE_DIST_CORR [n]MD 34100: REFP_SET_POS [n]MD 34200: ENC_REFP_MODE [n]

– Spindle monitoring functions (Section 6.10.18)MD 36060: STANDSTILL_VELO_TOLMD 35130: GEAR_STEP_MAX_VELO_LIMIT [n]MD 35140: GEAR_STEP_MIN_VELO_LIMIT [n]MD 35150: SPIND_DES_VELO_TOL

� Initiate NCK power-up

Check

� Safety signals (e.g. EMERGENCY STOP, HW limit switch)

� Traversing path, velocity, speed and direction of rotation (Sections 9.2 and9.3)

� Optimize axes and spindles

� Check machine functions

See Section 11

Test axis andspindle

Backup data


6

07.2000



6.9 Sequence of operations for starting up a series machine

See also Section 11.2 “Series start-up via V24”.

� Control system design

� Connection of components

� Cabling, jumpering, voltages

� Machine data

� Switch on control (CPU and FM-NC)

� NCK automatically loads default values

� PLC overall reset (with SK in Overall reset mode menu)

� Load PLC basic program via programmer

� Switch control off and on again

Load the PLC user program using the programmer and incorporate into the PLCbasic program.


The user data are entered as follows for the MMCs 100/100.2:� Switch off MMC

� Switch on MMC100 while actuating key “6” on the operator panel or switchon MMC100.2 and actuate key “6” on the operator panel as soon as theserial number appears on the display

� Load manufacturer data to MMC (Section 11.7)

Cycle alarm texts, error and operational message texts

� Switch MMC off and on again

See Section 11

Check

� Safety signals (e.g. EMERGENCY STOP, HW limit switch)

� Traversing path, velocity, speed and direction of rotation (Sections 9.2 and9.3)

� Optimization of axis and spindle (start-up software for drive)

� Check machine functions

See Section 11

Note

Check essentialpreconditions

Initialize system(Section 6.5)

Load PLC user program

Enter user data foroperator panelwith MMC100/100.2

Read in the datafor this machine

Test axis andspindle

Back up data

6.9 Sequence of operations for starting up a series machine

6

07.2000


6.10 Axes and spindles

6.10.1 Axis configuration

The SINUMERIK FM-NC is supplied as standard with the followingconfiguration:

NCU 570.2: 1 channel and 4 axes

These are all the axes on the machine. They are defined as geometry axes oradditional axes.

These are used to program the workpiece geometry. The geometry axes form arectangular coordinate system (2D or 3D). Tool offsets are only included incalculations for geometry axes.

In contrast to geometry axes, there is no geometric relationship betweenadditional axes such as

� rotary axes

� revolver axes

� positioned-controlled spindle

The axis configuration is defined on 3 levels:

1. Machine level

2. Channel level

3. Program level

Machine level

MD 10000 AXCONF_MACHAX_NAME_TABAn axis name is defined for each machine axis in MD 10000 AXCONF_MACHAX_NAME_TAB.

Example:

Turning machine Milling machinewith X, Z, C axis/spindle 4 axes + spindle/C axis

X1

0 1

Z1 C1

3 42

X1

0 1

Y1 Z1

3 42

A1 C1MD 10000

Index

Example for milling machine: MD 10000

AXCONF_MACHAX_NAME_TAB[0] = X1AXCONF_MACHAX_NAME_TAB[1] = Y1AXCONF_MACHAX_NAME_TAB[2] = Z1AXCONF_MACHAX_NAME_TAB[3] = A1AXCONF_MACHAX_NAME_TAB[4] = C1

Overview

Machine axes

Geometry axes

Additional axes

Axis configuration


6

07.2000



Channel level

� MD 20070 AXCONF_MACHAX_USED[0...4]

The machine axes are assigned to a geometry channel by means of thechannel-specific MD.

Turning machine Milling machine

1 2 3 4 51 2 3 0 0

� MD 20080 AXCONF_CHANAX_NAME_TAB[0...4]

This MD defines the names of the axes in the channel. Enter the names ofthe geometry and additional axes here.

A CCX Y ZX Y

Program level

� MD 20060 AXCONF_GEOAX_NAME_TAB[0...4]

This MD specifies the names to be used in the part programs for thegeometry axes (workpiece axes not specific to machine).

X Y ZX ZY1)

1) The 2nd geometry axis coordinate must also be assigned a name (e.g. “Y”) for a transformation, e.g. TRANSMIT.

� MD20050 AXCONF_GEOAX_ASSIGN_TAB[0...4]

Defines the assignment between the geometry axes and the channel axes(MD20070) without transformation.

(For assignment with an active transformation, please refer to: References: /FB/, K2 “Coordinate Systems, Axis Types, Axis Configuration,...”)

Note the relationship with the inclusion of tool offsets in the calculation (G17,G18, G19).

1 2 31 0 2


6

07.2000


The axis designators AX1 to AX4 always apply in the system. In addition, aname can be entered in MD 10000: AXCONF_MACHAX_NAME_TAB for everymachine axis. However, this name is significant only for the following functions:

� Loading, saving and display of machine data

� Machine-axis-specific reference point approach (G74)

� Measurements

� Fixed-point approach (G75)

� Display in “AX–MD” menu and with axis alarms

� Display in machine-related actual value system

� Handwheel function

� Traversal from PLC

Machine axes can be assigned by means of MD 20070: AXCONF_MA-CHAX_USED to an active channel which in turn is assigned to a mode group bymeans of MD 10010: ASSIGN_CHAN_TO_MODE_GROUP. These axes canalso be activated in MD 20070. A distinction is made between additional axesand geometry axes (GEOaxis) in the channel. Geometry axes are imaged onmachine axes via a transformation. If no transformation is selected, then theGEOaxes are imaged as standard 1:1 on the appropriate machine axes. Addi-tional axes are machine axes which can be programmed in addition to theGEOaxes (e.g. rotary axes). A machine axis which is not defined in the channelcannot be addressed in this channel.

Machine axis no. for channel1 2 3 4 5

X Y Z A BAxis name in channel

X Y ZGEOaxis

Assignment of GEOaxes

A B Additional axes

MD 20070: AXCONF_MACHAX_USEDMachine axes used in channel

MD 20080: AXCONF_CHANAX_NAME_TABAn axis name must be assigned to every machineaxis defined in the channel.

MD 20050: AXCONF_GEOAX_ASSIGN_TABAssignment between GEOaxis and machine axis.AXCONF_GEOAX_ASSIGN_TAB [0] = 1AXCONF_GEOAX_ASSIGN_TAB [1] = 2AXCONF_GEOAX_ASSIGN_TAB [2] = 3X to X, Y to Y, Z to Z

MD 20060: AXCONF_GEO_AX_NAME_TABName of GEOaxes

Fig. 6-3 Axis configuration in channel (default settings)

Note

There must be no gaps in the list of machine axes to be traversed (MD:20070_AXCONF_MACHAX_USED).

The relevant machine axis is activated through entry in this list, i.e. a machineaxis which is not entered in any channel in $MC_AXCONF_MACHAX_USED isnot included in the calculation and therefore not affected by the closed-loopcontrol function.

Axis assignmentsin system

Axis assignmentwith respect to achannel


6

07.2000



The control must be informed of the interface via which setpoints and actualvalues are to be exchanged with the drive. In the FM–NC control system, onlyone actual value input can be defined for each axis so that the maximum pos-sible setting for MD 30200: NUM_ENCS is “1”. The actual value which is activefor the position control is selected via the PLC user interface.

The following parameters must be specified for the FM–NC:

Drive segment

With the FM–NC, a value of “0” (default setting) must be entered in the MD forthose axes which are supplied directly with setpoints and actual values by theFM–NC. A value of “2” must be entered in the MD for the 5th axis which re-ceives its setpoints and actual values from the FM–NC via the local P bus.

MD 30100: CTRLOUT_SEGMENT_NR (setpoint)MD 30210: ENC_SEGMENT_NR (actual value)

Drive module

The module number entered corresponds to the number of the module whichdrives the motor. “1” must be entered for an FM–NC control.

MD 30110: CTRLOUT_MODULE_NR (setpoint)MD 30220 ENC_MODULE_NR (actual value)

Interface

The number of the actual value input or of the setpoint interface (“1” to “4” forFM–NC or FM 354 “1”) of the drive module is defined in this parameter.

MD 30120: CTRLOUT_NR (setpoint)MD 30230: ENC_INPUT_NR (actual value)

!Important

In order to guarantee that the control powers up reliably, all activated axes aredeclared as simulation axes (without hardware) during initialization.

MD30130: CTRLOUT_TYPE = 0 (simulation)MD30240: ENC_TYPE = 0 (simulation)

When the axes are traversed, the control loop is simulated and no alarms areoutput. For the purpose of axis or spindle start-up, MD 30130 must be set to “1”or MD 30240 to “2”, or to the value corresponding to the hardware identifier.

The user can select in MD 30350: SIMU_AX_VDI_OUTPUT whether the inter-face signals of a simulation axis are output at the PLC interface (e.g. duringprogram test, start-up).

Assignment of actual values andsetpoints


6

07.2000


Closed-loopcontrol

Manipulated-variable branch

Manipulated-variable branch

Act.-value process.

30200 NUM_ENCS

Manipulated-variablerouting

M

M

Actual-valuerouting

G

G

30200 NUM_ENCS

30240 ENC_TYPE = 0 (simulation)

Present only on test set-upsor real installations

Act.-value process.

Fig. 6-4 Block diagram showing setpoint and actual-value routing

6.10.2 Axis data

4 linear axes are active by default with the SINUMERIK FM-NC. The assign-ment for rotary axis and spindle must be made during start–up.

MD 30300: IS_ROT_AX must be set for a rotary axis. This setting causes“Rotary axis” to be selected internally and the control to be switched over frommm to degrees. In addition, there is the rotary axis display referred to 360 de-grees, MD 30320: DISPLAY_IS_MODULO (modulo 360 degrees display forrotary axes) and the modulo programming MD 30310: ROT_IS_MODULO(modulo conversion for rotary axis and spindle).

These MD are activated after POWER ON. When MD 30300 is set followed bypower ON, the active axis machine data (e.g. for velocity, acceleration, jerk) areconverted automatically to the new physical unit.

Example:

Velocity = 10000 mm/min and linear axis is set. After the conversion to rotary axis, the value 27.77777778 is entered in this MDwith a unit of rev/min.

Indexing axis

The user must specify in MD 30500: INDEX_AX_ASSIGN_POS–TAB (indexingaxis assignment) which global list (general machine data 10900:INDEX_AX_LENGTH_POS_TAB1 or MD 10910: INDEX_AX_POS_TAB1 for list1 and MD 10920 or MD 10930 for list 2) with indexing positions is to be used.

Concurrent positioning axis

The axis can be defined as a “Concurrent positioning axis” in MD 30450:IS_CONCURRENT_POS_AX.

Example of actualvalue and setpointassignments

Overview

Distinction be-tween linear axisand rotary axis

Axis types


6

07.2000



In the case of machine data which are stored as a field, the first value is alwaysassigned to the first parameter, e.g. 1st reference point value, 1st encoder num-ber. This is not the case for the following machine data for which the assignmentis made by means of a special function. In the case of machine data with thefield parameter “Control parameter set no.”, the first field is used for normal axisoperation.

If the axis interpolates with a spindle, e.g. with G331 (tapping without compen-sating chuck), the selected gear stage determines the appropriate field (1st gearstage –––> field index 1). This applies to all machine axes which can be tra-versed by means of geometry axes (see Section 6.1).

MD 31050: DRIVE_AX_RATIO_DENOM (denominator load gearing)MD 31060: DRIVE_AX_RATIO_NUMERA (numerator load gearing)MD 32200: POSCTRL_GAIN (servo gain factor)MD 32800: EQUIV_CURRCTRL_TIME (substitute time constant, current controlloop for feedforward control)MD 32810: EQUIV_SPEEDCTRL_TIME (substitute time constant, speed con-trol loop for feedforward control)MD 32910: DYN_MATCH_TIME (dynamic response matching time constant)MD 36200: AX_VELO_LIMIT (threshold value for speed monitoring)

Example:

MD 32200: POSCTRL_GAIN [0,AX1] = 1 (servo gain factor for normal axisoperation)MD 32200: POSCTRL_GAIN [1,AX1] = 1 (servo gain factor for G331 and activespindle gear stage 1)MD 32200: POSCTRL_GAIN [3,AX1] = 1 (servo gain factor for G331 and activespindle gear stage 3)

Exception regard-ing machine dataparameterization


6

07.2000


6.10.3 Encoder matching (axis)

NC–CPU 30220 ENC_MODULE_NR

1 1

FM–NC

30210 ENC_SEGMENT_NR(FM–NC = 0)(Local P bus = 2)

FM 354 (optional)

3210

11 2

3 4

30230 ENC_INPUT_NR30240 ENC_TYPE: = 0 Simulation

= 1 Raw signal encoder (not FM–NC)= 2 Square-wave encoder= 3 Stepper motor= 4 EnDat absolute encoder (for SINUMERIK 840D only)= 5 SSI encoder

MD for measuring-circuit routing:30210 ENC_SEGMENT_NR = 0 or 2 for FM–NC local bus)30220 ENC_MODULE_NR = 130230 ENC_INPUT_NR = 1...4 (FM–NC = 1...4, FM = 1, handwheels = 5,6)30240 ENC_TYPE = 0, 2, 3 and 5 (for FM-NC)

0, 2, and 5 (for FM 354)Example:5th axis (FM 354)ENC_SEGMENT_NR = 2ENC_MODULE_NR = 1ENC_INPUT_NR = 1ENC_TYPE = 2

(Local P bus)

Fig. 6-5 Measuring circuit assignment (FM–NC)

The control requires scaled encoder signals for a closed position control loop. Inorder to match the encoder, the encoder type and prevailing mechanical condi-tions must be known and entered in the machine data (other values are not re-quired). The control then calculates the resolution referred to the internal cal-culation resolutions(MD: INT_INCR_PER_MM; MD INT_INCR_PER_DEG) automatically.

The following machine data must be set when the data are input:

IS_ROT_AX Distinction between rotary and linear axisENC_IS_LINEAR Linear scale or rotary encoderENC_IS_DIRECT Encoder directly mounted on machine or motor

Please refer to the function descriptions for detailed information.

References: /FB/, G2, “Velocities, Actual Value Systems, Cycle Times”R2, “Rotary Axes”

Overview


6

07.2000



The following table lists all the data which must be entered for the sake of en-coder matching.

Table 6-6 Machine data for matching rotary encoders

Machine data Linear axis Rotary axis

Encoder onmotor

Encoder onmachine

Encoder onmotor

Encoder onmachine

30300: IS_ROT_AX 0 0 1 1

31000: ENC_IS_LINEAR 0 0 0 0

31040: ENC_IS_DIRECT 0 1 0 1

31020: ENC_RESOL Marks/rev Marks/rev Marks/rev Marks/rev

31030: LEADSCREW_PITCH mm/rev mm/rev – –

31080: DRIVE_ENC_RATIO_NUMERA Motor rev Load rev Motor rev Load rev

31070: DRIVE_ENC_RATIO_DENOM Encoder rev Encoder rev Encoder rev Encoder rev

31060: DRIVE_AX_RATIO_NUMERA Motor rev See note Motor rev See note

31050: DRIVE_AX_RATIO_DENOM Load rev See note Load rev See note

Note

These MD are not required to match the encoder (path evaluation), but theymust be entered correctly for the sake of setpoint calculation otherwise the de-sired servo gain factor will not be obtained.

The load revolutions are entered in MD 31050: DRIVE_AX_RATIO_DENOMand the motor revolutions in MD 31060: DRIVE_AX_RATIO_NUMERA.

1st example of encoder matching

Linear axis X1 with rotary encoder (2500 pulses) on motor, internal multiplier 4(standard, INTV), motor/leadscrew gearing 5/1, leadscrew pitch 10 mm, 1000increments per mm

MD 30300: IS_ROT_AX [X1] = 0MD 31000: ENC_IS_LINEAR [0,X1] = 0MD 31040: ENC_IS_DIRECT [0,X1] = 0MD 31020: ENC_RESOL [0,X1] = 2500MD 31030: LEADSCREW_PITCH [X1] = 10MD 31080: DRIVE_ENC_RATIO_NUMERA [0,X1] = 1MD 31070: DRIVE_ENC_RATIO_DENOM [0,X1] = 1MD 31060: DRIVE_AX_RATIO_NUMERA [0,X1] = 5MD 31050: DRIVE_AX_RATIO_DENOM [0,X1] = 1MD 10200: INT_INCR_PER_MM = 1000

MD31020 � INTV � MD31070 � MD31060

1 � MD31080 � MD31050 � MD31030 � MD10200Internal resolution =

2500 � 4 � 1 � 5

1 � 1 � 1 � 10 mm � 1000/mmInternal resolution = = 0.2

Result:

1 encoder increment corresponds to approximately 0.2 increments of theinternal unit.

Matching rotaryencoders


6

07.2000


2nd example of encoder matching

Rotary axis C with rotary encoder (1024 pulses) on motor, internal multiplier 4(standard, INTV), motor/leadscrew gearing 5/1, 1000 increments per degree

MD30300: IS_ROT_AX [C] = 1MD31000: ENC_IS_LINEAR [0,C] = 0MD31040: ENC_IS_DIRECT [0,C] = 0MD31020: ENC_RESOL [0,C] = 1024MD31080: DRIVE_ENC_RATIO_NUMERA [0,C] = 1MD31070: DRIVE_ENC_RATIO_DENOM [0,C] = 1MD31060: DRIVE_AX_RATIO_NUMERA [0,C] = 5MD31050: DRIVE_AX_RATIO_DENOM [0,C] = 1MD10210: INT_INCR_PER_DEG = 1000

MD31020 � INTV � MD31070 � MD31060

360 � MD31080 � MD31050 � MD10210Internal resolution =

1024 � 4 � 1 � 5

360 � 1 � 1 � 1000/degreeInternal resolution = = 17.5781

Result:

1 encoder increment corresponds to approximately 17.5781 increments of theinternal unit.

Alongside incremental encoders the FM–NC can also be used with SSI encoders with the telegram types

� 13-bit (only single-turn encoder),

� 21-bit (max.12-bit resolution/revolution) and

� 25-bit (max. 13-bit resolution/revolution).

Connection is similarly at the measuring system interfaces X3...X6.The pin assignment is to be taken from

References: /PHF/, ”Planning, NCU570 and FM354 Manuals”

The encoder type is to be set with MD30240_ENC_TYPE=5 (SSI encoder).

The following machine data are used to match the SSI encoder to the FM–NC:

� MD14000: ENC_SSI_BAUD_RATEBaud rate setting for SSI encoder,

Value: 0,1 250 kHz (default value)Value: 2 400 kHzValue: 3 500 kHzValue: 4 1 MHz

SSI encoder matching


6

07.2000



SSI encoder matching, continued

� MD34220: ENC_ABS_TURNS_MODULO(valid from product version 3.07.11)The absolute position of an axis is reduced to the range entered here whenthe absolute encoder is switched on. The value should correspond to thetravel range (in turns) of the absolute encoder actually in use.Default setting: 1 (corresponds to single–turn)Min. input value: 1, max. input value: 4096

� MD34400: ENC_SSI_STATUSSynchronization for SSI encoder, default value=0

Bit 0 (value code) Value=0 –> Gray codeValue=1 –> binary code

Bit 1 (parity test) Value=0 –> noValue=1 –> yes

Bit 2 (parity) Value=0 –> uneven parityValue=1 –> even parity

Bit 3 (measurement) Value=0 –> measurement not plannedValue=1 –> activate for measurement

Bit 4 (probe selection) Value=0 –> probe 1 at connector X1.17Value=1 –> probe 2 at connector X1.18

� MD34410: ENC_SSI_MESSAGE_LENGTHTelegram length for SSI encoder,

Value: 0 25 bits for multi-turn encoder (default value)Value: 1 13 bits for single-turn encoderValue: 2 21 bits for multi-turn encoderValue: 3 25 bits for multi-turn encoder

� MD34420: ENC_SSI_MESSAGE_FORMATFormat of SSI telegram.For SSI encoders the number of increments per revolution of the encoder ishere used to set the telegram format within the telegram length.

Value: 0 right-justifiedValue: 1 8192 increments per revolution in fir-tree formatValue: 2 4096 increments per revolution in fir-tree formatValue: 3 2048 increments per revolution in fir-tree formatValue: 4 1024 increments per revolution in fir-tree formatValue: 5 512 increments per revolution in fir-tree formatValue: 6 256 increments per revolution in fir-tree formatValue: 7 128 increments per revolution in fir-tree formatValue: 8 64 increments per revolution in fir-tree formatValue: 9 32 increments per revolution in fir-tree formatValue: 10 16 increments per revolution in fir-tree formatValue: 11 8 increments per revolution in fir-tree formatValue: 12 4 increments per revolution in fir-tree formatValue: 13 2 increments per revolution in fir-tree format

The following machine data are also affected:

� MD34320: ENC_INVERS (length measuring system is inverse)

� MD34200: ENC_REFP_MODE = 0 (referencing mode, 0=no RP travel)

� MD31020: ENC_RESOL (number of increments to base 2)

� MD30240: ENC_TYPE = 5 (type of actual value encoder)

� MD34090: REFP_MOVE_DIST_CORR (reference point offset)


6

07.2000


The following table lists all the data which need to be entered in order to matchthe encoder.

Table 6-7 Machine data for encoder matching with linear measuring systems

Machine data Linear axis

MD 30300: IS_ROT_AX 0

MD 31000: ENC_IS_LINEAR 1

MD 31010: ENC_GRID_POINT_DIST Division

MD 34320: ENC_INVERS Inverted

Example:

Linear axis with a glass scale which has a division period of 0.020 mm. Internalmultiplier 4 (standard, INTV). Internal calculation resolution = 1000 incrementsper mm.

internal multiplier (INTV)

MD31010 � 11) � MD10200Internal resolution =

4

0.02 mm � 1000/mmInternal resolution = = 5

Result:

A division period corresponds to approximately 5 increments of the internal unit.

M

ENC_SEGMENT_NR[0, Y] = 2 CTRLOUT_SEGMENT_NR[Y] = 2ENC_MODULE_NR[0, Y] = 1 CTRLOUT_MODULE_NR[Y] = 1ENC_INPUT_NR[0, Y] = 1 CTRLOUT_NR [Y] = 1

G

NC-CPU

1 1

3210

11 2

3 4 1

FM-NC FM 354

Table YLeadscrew

(Y is 2nd machine axis)

Fig. 6-6 Example of a measuring-circuit and setpoint assignment with an FM 354 as anadditional axis on FM-NC

1) Position control cycle factor (MD 10060) is preset to a value of “1” in the FM–NC.

Encoder matchingwith linear measur-ing systems


6

07.2000



DRIVE_AX_RATIO_NUMERA=

DRIVE_AX_RATIO_DENOMNumber of motor revolutionsNumber of load (spindle) revolutions

MController

Wire word

36710 DRIFT_LIMIT (%)

CTRLOUT_LIMIT (%)

Spindle

31030 LEADSCREW_PITCH

with linear axes only

AX_MOTION_DIR = �1

RATED_OUTVAL (%)

RATED_VELO (degrees/s)

Fig. 6-7 Actual value encoder on spindle

� Linear axis IS_ROT_AX = 0

Linear scale

TableSpindle

Load gearing

31000 ENC_IS_LINEAR = 131010 ENC_GRID_POINT_DIST34320 ENC_INVERS

M

Fig. 6-8 Linear scale

ENC_IS_DIRECT = 0ENC_IS_LINEAR = 0

ENC_RESOL

DRIVE_ENC_RATIO_NUMERA

DRIVE_ENC_RATIO_DENOM

Number of spindle revolutions

Number of encoder revolutions=

Measurement gearing:

LEADSCREW_PITCH = main spindle pitch

int resolution =1

ENC_RESOL .multiplication.


DRIVE_ENC_RATIO_DRIVE

Encoderincrement/revolutions

Number of encodermarkings, calculatedallowing for externalmultiplier if applicable

LEADSCREW_PITCH

INT_INKR_PER_MM

M G

.

.

Fig. 6-9 Rotary encoder on machine

Actual valueencoder onspindle

Actual value processing


6

07.2000


ENC_IS_DIRECT = 0

ENC_RESOLDRIVE_AX_RATIO_NUMERA

=DRIVE_AX_RATIO_DENOM

Number of motorsNumber of spindle revolutions

Table

LEADSCREW_PITCH


DRIVE_ENC_RATIO_DENOM=

Number of motor revolutionsNumber of encoder revolutions

Internal resolution =1

ENC_RESOL . multiplication



DRIVE_AX_RATIO_DENOM

DRIVE_AX_RATIO_NUMERALEADSCREW_PITCH

.

. . INT_LNCR_PER_MM.

G M

ENC_IS_LINEAR = 0

Fig. 6-10 Rotary encoder on motor

� Rotary axis IS_ROT_AX = 1

ENC_IS_DIRECT = 1

ENC_IS_LINEAR = 0



Number of load (spindle) revolutions

Number of encoder revolutions

Internal resolution =360°

ENC_RESOL . multiplication DRIVE_ENC_RATIO_DENOM. INT_INCR_PER_DEG.

M L GENC_RESOL


Fig. 6-11 Rotary encoder on machine

.

ENC_IS_DIRECT = 0



Number of motor revolutions

Number of load revolutions

LEADSCREW_PITCH




Number of encoder revolutions

Intern. resolution =ENC_RESOL . multiplication




DRIVE_AX_RATIO_NUMERA

.

. INT_INCR_PER_DEG.

G M

ENC_IS_LINEAR = 0

L

360°

Fig. 6-12 Rotary encoder on motor


6

07.2000



� Stepper motor without encoder

.

31400 STEP_RESOL

31060 DRIVE_AX_RATIO_NUMERA=

31050 DRIVE_AX_RATIO_DENOM

31030 LEADSCREW_PITCH

DRIVE_ENC_RATIO_NUMERADRIVE_ENC_RATIO_DENOM

=

STEP_RESOL


DRIVE_AX_RATIO_NUMERAINT_INCR_PER_DEG.

G SM

31000 ENC_IS_LINEAR = 0

L

360°

FM-NC

MD 30240 ENC_TYPE = 3MD 30130 CTRLOUT_TYPE = 2

Number of motor revolutionsNumber of load revolutions

Number of motor revolutionsNumber of encoder revolutions

Internal resolution =

The “encoder” in stepping motor controls is simulated in the FM–NC. The value “Pulse per step revolu-tion” must be entered in MD 31020 ENC_RESOL.

Fig. 6-13 Stepping motor without encoder

Although encoderless stepper motors have no external encoder, the follow-ing encoder machine data must be observed (due to internal pulse feed-back):

– MD30130_NUM_ENCS = 1

– MD31020__ENC_RESOL = 31400_STEP_RESOL = steps per steppermotor revolution

Note

For further information about motor rotation monitoring, please refer to

References: /FB/, S6 “Stepping Motors”


6

07.2000


� Stepper motors with encoder

Stepper motor drives with encoder must be treated like normal drives ex-cept for MD settings

MD30240 ENC_TYPE � 3,

MD30130 CTRLOUT_TYPE = 2,

MD31020 ENC_ RESOL = pulses per encoder revolution

MD31400 STEP_RESOL = steps per stepper motor revolution and

MD30130 NUM_ENCS = 1

.

ENC_IS_DIRECT = 0





LEADSCREW_PITCH





Int. resolution =ENC_RESOL . Multiplication




DRIVE_AX_RATIO_NUMERA

.

. INT_INCR_PER_DEG.

G SM

ENC_IS_LINEAR = 0

L

360°

MD 30240 ENC_TYPE � 3MD 30130 CTRLOUT_TYPE = 2STEP_RESOL

Fig. 6-14 Rotary encoder on stepper motor


6

07.2000



6.10.4 Setpoint routing (axis)

NC–CPU 30110 CTRLOUT_MODULE_NR

1 1

FM–NC

30100 CTRLOUT_SEGMENT_NR(FM–NC = 0)(FM 354 = 2)

FM 354 (optional)

3210

1

30120 CTRLOUT_NR (for FM–NC = 1...4, for FM 354 = 1)

30130 CTRLOUT_TYPE: = 0 Simulation= 1 Standard= 2 Stepper motor= 3 Unassigned

MD for setpoint routing:

CTRLOUT_SEGMENT_NR = 0 (FM–NC) and 2 (FM 354)CTRLOUT_MODULE_NR = 1CTRLOUT_NR = 1...4 (FM–NC = 1...4, FM = 1)CTRLOUT_TYPE = 0...3

Output PINanalog Increm.

1

2

3

4

1 5/6

35 40/41

37 44/45

3 9/10

X2

1 2

3 4 1

(local P bus)

Fig. 6-15 Measured variable (setpoint) assignment (FM–NC)

Axes which are activated but not connected to a drive system must be assigneda value of 0 (simulation) in MD 30130: CTRLOUT_TYPE.

Note

MD 30120: CTRLOUT_NR simultaneously routes the “Controller enable” sig-nals (X2 pin 14/47, pin 15/48, etc.). Controller output X2, pin 16/49, is thereforeassigned, for example, to setpoint out 3 (X2 pin 3/36, MD 30120:CTRLOUT_NR = 3).

The setpoint routing function for stepper motors without measuring system (MD30130. CTRLOUT_ TYPE = 2) also routes the appropriate actual value feed-back. For example, if the 3rd setpoint output is generated (MD 30120:CTRLOUT_NR = 3) for the 2nd channel axis, then the stepping pulses are alsofed back to the 3rd actual value input. Actual value connector 3 may not there-fore have a measuring system assigned to it.

The steps per stepper motor revolution must be entered in MD31400STEP_RESOL (corresponds to MD31020 ENC_RESOL for SM with encoder).

Setpointadaptation foraxes without drive

Setpoint for stepper motor


6

07.2000


6.10.5 Velocity/speed matching

The following machine data must be defined:

MD 32000: MAX_AX_VELO (maximum axis velocity)MD 32010: JOG_VELO_RAPID (conventional rapid traverse)MD 32020: JOG_VELO (conventional axis velocity)MD 34020: REFP_VELO_SEARCH_CAM (reference point approach speed)MD 34040: REFP_VELO_SEARCH_MARKER [n] (creep speed)MD 34070: REFP_VELO_POS (reference point approach speed)

These velocity/speed values, which can be set via machine data, are used tomatch the drive to the machine. Their purpose is to preclude the risk of damageresulting from incorrectly adapted axis velocity settings.

Note

When new velocity/speed values are entered, the velocity/speed monitor (MD36200: AX_VELO_LIMIT) must be adapted accordingly.

These velocity/speed values must be transferred to the drive after scaling forthe drive control. The setpoint output is scaled internally in the NC.

In order to ensure correct setpoint scaling, it is essential to enter the correct loadgearbox data!MD 31060: DRIVE_AX_RATIO_NUMERAMD 31050: DRIVE_AX_RATIO_DENOM

The following data are also relevant in terms of velocity/speed adaptation:MD 32250: RATED_OUTVAL (speed setpoint scaling)MD 32260: RATED_VELO (motor speed scaling)

References: /FB/, G2 “Velocities, Setpoint/Actual Value Systems, Closed-Loop Control”

Optimum start/stop characteristics at low velocities, i.e. in the vicinity of the start/stop frequency of the stepper motor, can be obtained by means of the accelera-tion characteristic with break-point. In this case, a steeper characteristic is setfor the lower velocity range of the stepper motor than for the upper range.

References: /FB/, S6, “Stepper Motors”

Machine data

Accelerationcharacteristic withbreak-point


6

07.2000



Activation

The acceleration characteristic with break-point is activated by means ofmachine data or NC language commands.

MA_ACCEL_TYPE_DRIVE = 1

This characteristic is the basic setting for each axis. It is not permissible toviolate any of the parameters specified for the acceleration characteristic in anymotion situation.

Effect:

1. The acceleration characteristic with break-point is always active for motionsby single axes (positioning, oscillation, JOG, ...).

It is not permissible to switch over to BRISKA (constant acceleration overentire velocity range) or SOFTA (constant jerk).

2. If at least one axis with setting MA_ACCEL_TYPE_DRIVE = 1 is involved inthe path motion and there is no DRIVE active, the dynamic limit values arereduced (equivalent path characteristic).

DRIVE NC language commands

The acceleration characteristic with break-point is activated for the path motionby means of language command “DRIVE” or with machine data

MC_GCODE_RESET_VALUE[20] = 3.

Setting 3 of MD “MC_GCODE_RESET_VALUE[20]” means that the accelera-tion characteristic with break-point is active after POWER ON.

MA_ACCEL_TYPE_DRIVE is not relevant in this case.

The machine data

MA_ACCEL_REDUCTION_SPEED_POINTMA_ACCEL_REDUCTION_FACTORMA_ACCEL_REDUCTION_TYPE

of the axes involved in the motion determine (together with the geometry) thepath characteristic.

Transformation:

When a kinematic transformation is active, the axis cannot be traversed withDRIVE acceleration characteristics. The BRISK command is selected internally.If MA_ACCEL_TYPE_DRIVE is set for at least one of the path axes involved,the equivalent characteristic for the path is activated.

DRIVEA(AXIS) NC language commands

Activation of acceleration characteristic with break-point for single-axis motions(positioning axes).


6

07.2000


Examples of how to activate characteristic:

Machine data:

DRIVE as power ON setting

MC_GCODE_RESET_VALUE[20] = 3

Parameters of axis characteristic:

X axis MA_ACCEL_REDUCTION_SPEED_POINT[X] = 0.4MA_ACCEL_REDUCTION_FACTOR[X] = 0.85MA_ACCEL_REDUCTION_TYPE[X] = 2MA_ACCEL_TYPE_DRIVE[X] = 1

Y axis MA_ACCEL_REDUCTION_SPEED_POINT[Y] = 0.0MA_ACCEL_REDUCTION_FACTOR[Y] = 0.6MA_ACCEL_REDUCTION_TYPE[Y] = 1MA_ACCEL_TYPE_DRIVE[Y] = 1

Z axis MA_ACCEL_REDUCTION_SPEED_POINT[Z] = 0.6MA_ACCEL_REDUCTION_FACTOR[Z] = 0.4MA_ACCEL_REDUCTION_TYPE[Z] = 0MA_ACCEL_TYPE_DRIVE[Z] = 0

NC program:

N10 G1 X100 Y50 Z50 F700 Path motion (X, Y, Z) with DRIVEN15 Z20 Path motion (Z) with DRIVEN20 BRISK Switchover to BRISKN25 G1 X120 Y70 Path motion (Y, Z) with equivalent

characteristicN30 Z100 Path motion (Z) with BRISKN35 POS[X] = 200 FA[X] = 500 Positioning motion (X) with DRIVEAN40 BRISKA(Z) Activate BRISKA for ZN40 POS[Z] = 50 FA[Z] = 200 Positioning motion (Z) with BRISKAN45 DRIVEA(Z) Activate DRIVEA for ZN50 POS[Z] = 100 Positioning motion (Z) with DRIVEN55 BRISKA(X) Causes error message...


6

07.2000



The closed-loop control loop for an axis consists of the drive speed control loopand a higher-level position control loop in the NC.

With the FM–NC control system, the speed control loop is located in the driveunit; only the position control loop is situated in the FM–NC itself.

Setpointprocessing

SetpointsController

Braking ramp

CTRLOUT_LIMITLogic

FOLLOW_TIME, HOLD_TIME

Controller trigger

DRIFT_LIMIT

AX_EMERGENCY_STOP_TIME

Control loopmodel

–

–CONTOUR_TOL

Following error

AX_VELO_LIMIT

STSTILL_VELO_TOL

ENC_CHANGE_TOL

ENC_CHOICE

STOP_LIMIT_COARSESTOP_LIMIT_FINEPOSITIONING_TIMESTSTILL_DELAY_TIMESTSTILL_POS_TOLCLAMP_POS_TOL

ENC_FREQ_LIMIT

–

Monitoring

Manip. var.processing

Actual valueprocessing

Actual valueprocessing

Fig. 6-16 Overview of position controller machine data

FIPO Jerk limitation Dynamic re-sponse adaptation

FIPO_TYPE AX_JERK_ENABLEAX_JERK_TIME

DYN_MATCH_ENABLEDYN_MATCH_TIME

Feedforward control ControllerManipulated-varia-ble processing

AX_COMP_ENABLEAX_MOTION_DIR = +1

ENC_FEEDBACK_POL = ”1ENC_COMP_ENABLE (SSFK)BACKLASH

POSCTRL_GAINPOSCTRL_SIMU_ENABEL

Actual-valueprocessing

NUM_ENCS

Fig. 6-17 FM–NC control parameters

Control data


6

07.2000


Position

controller

Speed

controller

isetnset

Current

controller

nset iset

Motor Encoder

Position actual

value

In FM–NC In motorized rheostat

Position setpoint from interpolator

Fig. 6-18 Control loops

If the axis does not traverse in the desired direction, then the direction can beadjusted in MD 32100: AX_MOTION_DIR (traversing direction). The direction isreversed when a value of “1” is entered. The control direction of the positioncontroller is taken into account internally. If the control direction of the positionmeasuring system is incorrect, then it can be reversed in MD 32110:ENC_FEEDBACK_POL (actual value sign).

In order to obtain a high degree of contour accuracy with interpolated axes, it isnecessary to set a high servo gain (KV) factor for the position controller. How-ever, an excessively high KV factor causes overshoots, instability and imper-missibly high loading of the machine. The maximum permissible KV factor de-pends on the design and dynamic response of the drive and on the mechanicalquality of the machine.

Definition of KV factor:

Following error [mm]

Velocity [m/min]KV =

The SG factor is entered in MD 32200 POSCTRL_GAIN according to the follow-ing conversion formula:

1 m 60 s

1000 mm 1 minSG [s–1] =

[m/min]

[mm]KV � = = KV � 16.667 s–1

m

min mm�

To achieve an KV factor of 1, MD 32200: POSCTRL_GAIN must be set to “1”.Allowance is made for the factor 16.667 byMD 10220: SCALING_USER_DEF_MASK and MD 10230: SCALING_FACTORS_USER_DEF.

For continuous path control, all axes included in the interpolation must have thesame dynamic response. They must all have the same following error at a givenvelocity, in other words, the axes must all have the same servo gain factor.

Note

Axes which interpolate with one another must have the same following error ata given velocity. This can be achieved by setting the same KV factor or throughdynamic response matching viaMD 32900: DYN_MATCH_ENABLE andMD 32910: DYN_MATCH_TIME.

References: /FB/, G2, “Velocities, Actual Value Systems, Closed-Loop Control”

Traversingdirection

Servo gain


6

07.2000



In order to obtain a satisfactory acceleration curve for axes with a stepper mo-tor, it is necessary to match the KV factor to the internal control loop feedback(stepper motor pulses are fed back internally as an actual value). The servoclock cycle must be set to 6 ms for this purpose.MD 10050: SYSCLOCK_CYCLE_TIME = 0,006MD 10060: POSCTRL_SYSCLOCK_TIME_RATIO = 1.The KV factor must be set to between “2” and “3” in MD 32200:POSCTRL_GAIN.

The automatic drift compensation (MD 36700_DRIFT_ENABLE = 1) must beupdated for stepper motor axes.

If an factor is already known for the machine in question, this can be set andchecked. If the maximum KV factor is not known, then it must be worked out onthe basis of the least dynamic axis within the interpolation group. To check thefactor, the axis acceleration must be reduced via MD 32300: MAX_AX_ACCELin order to ensure that the drive does not reach its current limit during accelera-tion and braking.

In the case of rotary axes and spindles, the KV factor must also be checked athigh speeds (e.g. for spindle positioning, tapping).

The approach behaviour at various speeds can be checked by means of astorage oscilloscope. The speed setpoint is recorded for this purpose.

nset[V]

t [ms]

nset[V]

t [ms]

“Poor”

Badly selected Kv factor

“Good”

Well selected Kv factor

Fig. 6-19 Speed setpoint characteristic

No overshoots may occur while the drive is approaching the static statuses; thisapplies to all speed ranges.

Causes of overshoots in position control loop

� Acceleration too high (current limit is reached)

� Error in speed controller (re-optimization necessary)

� Rise time of speed controller too high

� Mechanical backlash

� Load fluctuations

� Mechanical components canted

For reasons of safety, the KV factor should be set slightly lower than the maxi-mum permissible value. A static check of the factor can be executed by select-ing the Service display menu in the “Service axis” display. The actual KV factormust correspond precisely to the set value since monitoring functions, which arebased on the factor, will otherwise respond (e.g. contour monitoring).

Stepper motorcontrol loop

Checking the loop gain


6

07.2000


The axes are accelerated and braked at a value no higher than the accelerationvalue entered in MD 32300: MAX_AX_ACCEL. The maximum acceleration canbe influenced additionally via MD 32310: MAX_ACCEL_OVL_FACTOR which isan overload factor for velocity step changes. Ideally, this MD should be set to avalue between 1.2, ... 1.3. The set acceleration should allow the axes to be ac-celerated and positioned rapidly and accurately while ensuring that the machineis not unduly loaded. The acceleration default settings are in the 0.5 m/s2 to 2m/s2 range.

The acceleration data entered can be either empirical values or the maximumpermissible acceleration values which the user must calculate. The data mustalways be checked after entry by means of an oscilloscope.

Checking and calculating acceleration values:

Setting: MD 32300: MAX_AX_ACCE

Identification: Overshoot-free acceleration and approach with rapid traverse velocity under maximum load (heavy workpiece).

Measur. points: DAC outputs on X2 of FM–NC

After the acceleration has been entered, the axis is traversed rapidly; the actualcurrent value and the analog voltage at output X2 of the FM–NC in the drivespeed control loop are recorded. This recording shows whether the drivereaches the current limit. While traversing rapidly, the drive may reach the cur-rent limit briefly. However, the current must be well below the current limit beforethe rapid traverse velocity or the final position is reached. Slight load changesduring machining must not cause the current limit to be reached. Excessivecurrent during machining causes falsification of the contour. It is therefore advis-able in this case as well to enter a slightly lower acceleration value in the MDthan the maximum permissible value. Axes can be assigned different accelera-tion values even if they do interpolate with one another.

nset

nact

iset –

iset +

Example of well selectedacceleration value

The current limit is reached in this example (evidentfrom the fact that the actual current value stays at themaximum over a period of time). A lower accelerationvalue must be selected in this case.

Fig. 6-20 Correlation between acceleration and actual current value

Acceleration

Checking and cal-culating accelera-tion values


6

07.2000



AX_JERK_ENABLEAX_JERK_TIME

FIPO_TYPE DYN_MATCH_ENABLEDYN_MATCH_TIME

POSCTRL_GAIN

FRICT_COMP_ENABLEAX_MOTION_DIR

FFW_MODE

VELO_FFW_WEIGHTAX_INERTIAEQUIV_SPEEDCTRL_TIMEEQUIV_CURRCTRL_TIME

ENC_FEEDBACK_POLENC_COMP_ENABLEBACKLASH

FFW_ACTIVATION_MODE

Jerklimitation

Fine inter-polation

Dynamicresponsematching

Closed-loopcontrol

Feedfor-ward control

Speedsetpointprocessing

IS position meas. system 1/2

Actualvalueprocessing

Fig. 6-21 Additional parameters for position control

When dynamic matching is implemented for one geometry axis, then thedynamic response matching function must be activated (MD 32900 = 1) for allfurther axes to ensure that the dynamic response of all axes is identical.

Dynamic matching


6

07.2000


6.10.6 Monitoring functions (axis)

References: /FB/, A3, “Axis Monitoring, Protection Zones”

When an axis is being positioned, a monitoring function checks whether itreaches the position window (exact stop). It also checks whether an axis forwhich no traversing command has been issued remains within a certain toler-ance window (zero speed control, clamping tolerance).

MD 36000: STOP_LIMIT_COARSE (coarse exact stop)

� INTSIG “Position reached with coarse exact stop” (DB31–48, DBX60.6)

MD 36010: STOP_LIMIT_FINE (fine exact stop)

� INTSIG “Position reached with fine exact stop” (DB31–48, DBX60.7)

MD 36020: POSITIONING_TIME (coarse exact stop delay)

� This MD represents the delay after which the actual value must havereached the “Fine exact stop” tolerance window when the setpoint positionat the block end is reached.

� If the value does not reach the fine exact stop window within this time, thealarm “25080 axis [name] positioning monitoring” is generated.

� The control switches to follow-up mode.

MD 36030: STANDSTILL_POS_TOL (zero speed tolerance)

� The machine data specifies the position tolerance which a stationary axismay not leave.

� If the axis leaves the tolerance window, the alarm “25040 axis [name] zerospeed monitoring” is output. The control switches to follow-up mode.

MD 36040: STANDSTILL_DELAY_TIME (zero-speed monitoring delay time)

� This MD represents the delay after which the actual value must havereached the “Zero-speed tolerance” window when the setpoint position atthe block end is reached.

� If the value does not reach the position tolerance within this time, the alarm“25040 axis [name] zero speed monitoring” is generated. The controlswitches to follow-up mode.

MD 36050: CLAMP_POS_TOL (clamping tolerance)

� Position tolerance while the “Clamping in progress” signal is present at thePLC interface. If the tolerance is exceeded, the alarm “26000 axis [name]clamping monitoring” is generated.

� INT SIG “Clamping in progress” (DB31–34 DBX2.3).

MD 36060: STANDSTILL_VELO_TOL (threshold for “Axis stationary” signal)

� Position tolerance while the “Axis stationary” signal is present at the PLCinterface.

� INTSIG “Axis/spindle stationary” (DB31– to 34, DBX61.4)

Positioning monitor


6

07.2000



STANDSTILL_DELAY_TIME

Interface signal “Clamping in progress”

CLAMP_POS_TOL

STANDSTILL_POS_TOL

STOP_LIMIT_COARSE

STOP_LIMIT_FINE

“Exact stop fine” signal

“Exact stop coarse” signal

POSITIONING_TIME

Actual value

Setpoint

v or s

t

Fig. 6-22 Positioning, zero-speed and clamping monitoring

It is possible to implement a monitor for each axis via the hardware interface. Asignal is provided for each traversing range limit; this signal is transmitted to theFM–NC as soon as the appropriate limit has been reached. The alarm “Hard-ware limit switch” is then output. The relevant axis or the axes included in theinterpolation group are then shut down. The braking method applied can be setvia MD 36600: BRAKE_MODE_CHOICE (braking mode for hardware limitswitch).

!Important

If the relevant axis is operated by a stepping motor, then MD 36600:BRAKE_MODE_CHOICE must be set to 0 (braking characteristic).

Machine data, interface signals and alarms

MD 36600: BRAKE_MODE_CHOICE = 1 (rapid braking with setpoint “0”)MD 36600: BRAKE_MODE_CHOICE = 0 (braking according to characteristic)INTSIG “Hardware limit switch minus” (DB31–34, DBX12.0)INTSIG “Hardware limit switch plus” (DB31–34, DBX12.1)Alarm “21614 channel [name1] axis [name2] hardware limit switch [+/–]”The axis must be traversed in the opposite direction away from the switch inJOG mode.

Position monitor-ing by means ofhardware limitswitches


6

07.2000


2 software limit switch values can be specified in the machine data for eachaxis. The active software limit switch is selected via the PLC. The axis does nottraverse beyond the software limit switch. The monitoring function is activatedafter reference point approach and is deactivated after PRESET.

Machine data, interface signals and alarms:

MD 36100: POS_LIMIT_MINUS (1st software limit switch minus)MD 36110: POS_LIMIT_PLUS (1st software limit switch plus)MD 36120: POS_LIMIT_MINUS2 (2nd software limit switch minus)MD 36130: POS_LIMIT_PLUS2 (2nd software limit switch plus)INTSIG “2nd software limit switch minus” (DB31–34, DBX12.2)INTSIG “2nd software limit switch plus” (DB31–34, DBX12.3)Alarm “10614 channel [name1] block [no.] axis [name2] has reached softwarelimit switch +/–”Alarm “10616 channel [name1] axis [name2] stationary at software limit switch+/– (JOG)”Alarm “10701 channel [name1] block [no.] axis [name2] programmed end pointis behind software limit switch +/–”

In addition to software limit switches, a working area limitation can be specifiedfor geometry axes. The limitation can be entered via setting data or specified bymeans of G25/G26 from the program. It is activated via setting data or from theprogram. The monitoring function is active after reference point approach.

Setting data and alarms:

SD 43400: WORKAREA_PLUS_ENABLE (working area limitation active in pos.direction)

SD 43410: WORKAREA_MINUS_ENABLE (working area limitation active inneg. direction)

SD 43420: WORKAREA_LIMIT_PLUS (working area limitation plus)

SD 43430: WORKAREA_LIMIT_PLUS (working area limitation minus)Alarm “10618 channel [name1] block [no.] axis [name2] has reached workingarea limitation +/–”Alarm “10620 channel [name1] axis [name2] stationary at working area limita-tion +/– (JOG)”Alarm “10719 channel [name1] block [no.] axis [name2] working area limitation+/–”

2nd SW limit switch(can be activated

via PLC)

1st SW limitswitch

HW limitswitch

Mechanicaltraversing

limit

EMERGENCYSTOP

Workingarealimitation(for GEOaxes only)

Fig. 6-23 Overview of end limitations

Position monitor-ing by means ofsoftware limitswitches

Position monitor-ing by means ofworking area li-mitation


6

07.2000



The velocity is limited internally in the FM–NC. The setpoint is limited on a per-centage basis in MD 36210: CTRLOUT_LIMIT. An alarm is generated if the set-point is exceeded for the time period set in MD 36220: CTRLOUT_LIMIT_TIME.The axes are braked down to zero speed along a braking ramp when the posi-tion control loop is open (MD 36610: AX_EMERGENCY_STOP_TIME). ThisMD must contain the time within which the axis can brake to zero from maxi-mum velocity.

MD 36210: CTRLOUT_LIMIT (maximum speed setpoint)MD 36220: CTRLOUT_LIMIT_TIME (monitoring time for maximum speed set-point)MD 36610: AX_EMERGENCY_STOP_TIME (braking ramp time in event offaults)Alarm “25060 axis [name] speed setpoint limitation”

This monitoring function is provided to ensure that axes whose velocity is lim-ited in theory owing to the prevailing mechanical conditions (e.g. pulse encoder)traverse correctly. The actual velocity monitoring function is always active pro-vided, however, that the selected encoder is operating below its limit frequency.Alarm 25030 is output when the threshold value is exceeded.

MD 36200: AX_VELO_LIMIT (threshold value for velocity monitoring)MD 36610: AX_EMERGENCY–STOP_TIME (braking ramp time in the event offaults)Alarm “25030 axis [name] actual velocity alarm limit”

This monitoring function is provided to ensure that the part program is pro-cessed within a tolerance band, MD: CONTOUR_TOL. The function is based onthe continuous comparison between the measured following error and the fol-lowing error predicted on the basis of the NC position setpoint. Contour monitor-ing is always active in position-controlled operation. If the tolerance band is vio-lated, then the alarm “Contour monitoring” is generated and the axes are brakedalong a set braking ramp.

� MD 36400: CONTOUR_TOL (contour monitoring tolerance band)

� MD 36610: AX_EMERGENCY_STOP_TIME (braking ramp time in theevent of faults)

� Alarm “25050 axis [name] contour monitoring”.

Velocity limitation

Velocity monitoring

Contourmonitoring


6

07.2000


Encoder limit frequency and zero mark

� Encoder limit frequency monitoring

The frequency entered in MD: ENC_FREQ_LIMIT is monitored. If this isexceeded, the alarm “Encoder frequency exceeded” is output and the axesbraked to zero speed.

IS “Referenced/synchronized” is reset (DB31–35, DBX60.4, DBX60.5)

Example:

Encoder with 2048 pulses mounted directly on motor,limit frequency 200 kHz, nmax = (flimit/pulses) � 60 sec = 5900 rpm

Result:

It must be ensured that this speed is not reached at maximum axis velocity(MAX_AX_VELO).MD 36300: ENC_FREQ_LIMIT (encoder limit frequencyINTSIG “Encoder limit frequency exceeded 1” (DB31–34, DBX60.2)INTSIG “Encoder limit frequency exceeded 2” (DB31–34, DBX60.3)Alarm “21610 axis [name] encoder frequency exceeded”

� Zero mark monitoring

The zero mark monitoring is activated in MD: ENC_ZERO_MONITORING. Ifmore pulses are lost than specified in the MD, then the alarm “Zero markmonitoring” is generated and the axes are braked down to zero speed.MD 36310: ENC_ZERO_MONITORING (zero mark monitoring)MD 36610: AX_EMERGENCY_STOP_TIME (braking ramp time in event offaults)Alarm “25020 axis [name] zero mark monitoring”

Setpointprocessing

Setpoints

Interpolator

DAW ”10 VPositioncontroller

AX_EMERGENCY_STOP_TIME

CTRLOUT_LIMITControlloop model

CONTOUR_TOL

STSTILL_VELO_TOL

AX_VELO_LIMIT

Actual value proc.

ENC_FREQ_LIMITENC_ZERO_MONITORINGFollowing error

STOP_LIMIT_COURSESTOP_LIMIT_FINEPOSITIONING_TIMESANDSTILL_DELAY_TIMESANDSTILL_POS_TOLCLAMP_POS_TOL

Brakingramp Drive

Act. val. enc.

Fig. 6-24 Monitoring functions in SINUMERIK FM–NC

Encodermonitoring


6

07.2000



Note

The time setting in MD 36620: SERVO_DISABLE_TIME (controller enableshutdown delay) must always be higher than the time set in MD 36610:AX_EMERGENCY_STOP_TIME (braking ramp time in event of faults). If this isnot the case, the braking ramp in MD 36610 cannot take effect.

The analog system (� 10 V) of the FM–NC is equipped with an automatic driftcompensation function so that it can be compensated if required. The auto-matic drift compensation function must always be activated for axes with astepper motor drive.

The following three machine data are important for this function:

� MD 36700: DRIFT_ENABLE (automatic drift compensation)

� MD 36710: DRIFT_LIMIT (drift limit value)

� MD 36720: DRIFT_VALUE (basic drift value)

!Important

The use of direct measuring systems and activation of the “Automatic drift com-pensation” function (MD 36700 DRIFT_ENABLE = 1) causes the axis con-cerned to oscillate as a result of mechanical backlash.

The oscillation amplitude is dependent on the magnitude of the backlash, thetotal servo gain and on the concrete dynamic conditions (e.g. mass, vertical orhorizontal axis).

The BERO for rotation monitoring is connected in the same way as for referenc-ing with BERO.

The BERO can be connected in parallel for referencing purposes or can beused as the rotation monitor. However, the rotation monitoring function mustthen be deactivated during referencing and it must be ensured that the refer-ence BERO does not output any switching pulse edges when the monitoringfunction is active.

A modulo counter (modulo 1 revolution) counts the actual value increments.The modulo counter value is stored as a machine data.

MD: 31100 BERO_CYCLE Repeat cycle of BERO edge in actualvalue increments

The rotation monitor can be activated or deactivated via INTSIG “Rotation moni-toring ON/OFF” DB31–34 DBX24.0.

When the BERO has been actuated for the first time, it is “zeroed”, i.e. the mo-dulo counter contents are noted as the “BERO zeroing value”.

The BERO edge (1 = positive edge) can be selected in MD: 31120BERO_EDGE.

Automatic driftcompensation

Stepper motorrotation monitor-ing with BERO

Modulo counter

Activation (zeroing)


6

07.2000


Every time the BERO is actuated again, a check is made to establish whetherthe value of the modulo counter contents is close to the stored “BERO zeroingvalue”.

In this case, a BERO tolerance can be included in the calculation by means ofMD: 31110 BERO_EDGE_TOL. If the comparison has a negative result, theINTSIG “Rotation monitoring error” is output to the PLC (DB31–34 DBX96.0).The monitoring is automatically deactivated at the same time and a new refer-ence point approach is then required.

6.10.7 Reference point approach

After the control has been switched on, it must be synchronized (referenced)with the position measuring system of every machine axis. Referencing must becarried out for axes with incremental measuring systems and with distance-coded reference marks.

Axes with an SSI encoder do not need to be referenced.

References: /FB/, R1, “Reference Point Approach”

Reference cam calibration

If the position measuring system has several zero marks which repeat at cyclicintervals (e.g. incremental rotary indirect position measuring system mounted onmotor), the reference cam must be calibrated exactly. If the reference cam is notcalibrated precisely, an incorrect zero mark may be evaluated. In this case,alarm 20002 “Zero mark missing” may be output, resulting inevitably in a mea-sured value offset.

The reference cam is signalled by the PLC to the NCK by means of IS “Refer-ence point approach delay”. The following factors influence how the referencecam is detected by the the control (NCK) in terms of time:

� Switching accuracy of reference cam switch

� Time delay of reference cam switch (NC switch)

� Time delay at PLC input

� PLC cycle time

� Cyclical time for updating NCK–PLC interface

� Interpolation cycle

� Position control cycle

The best solution in practice has been to adjust the edge of the reference camrequired for synchronization in the centre between two zero marks.

!Warning

An incorrect zero mark may be evaluated if the reference cam is not calibratedexactly. This causes the control to detect the machine zero point incorrectlyand to move the axes to incorrect positions. Software limit switches, protectionzones and working area limitations are all referred to incorrect positions andcannot therefore afford any protection for the machine. The difference corre-sponds in each case to � one revolution of the encoder.

Comparison

Overview


6

07.2000



General machine data and interface signals

MD 34000: REFP_CAM_IS_ACTIVE (axis with reference cam)MD 34110: REFP_CYCLE_NR (axis sequence with channel-specific referencepoint approach)INTSIG “Activate referencing” (DB21, DBX1.0)INTSIG “Referencing active” (DB21, DBX33.0)

There are three phases of reference point approach with incremental measuringsystems:

Phase 1: Approach reference cam

Phase 2: Synchronize with zero mark

Phase 3: Approach reference point

� Machine data and interface signals for phase 1

MD 11300: JOG_INC_MODE_LEVELTRIGGRD (INC/REF in JOG mode)

MD 34010: REFP_CAM_DIR_IS_MINUS (approach reference point in minus direction)

MD 34020: REFP_VELO_SEARCH_CAM (reference point approach velocity)

MD 34030: REFP_MAX_CAM_DIST (maximum path to reference cam)

INTSIG “Traversing keys plus/minus” (DB31–34, DBX8.6/DBX8.7)

INTSIG “Reference point approach delay” (DB31–34, DBX12.7)

� Machine data for phase 2

MD .34040: REFP_VELO_SEARCH_MARKER (creep speed)

MD 34050: REFP_SEARCH_MARKER_REVERSE (direction reversal to reference cam)

MD 34060: REFP_MAX_MARKER_DIST (maximum path to reference mark)


MD 34070: REFP_VELO_POS (reference point approach speed)

MD 34080: REFP_MOVE_DIST (reference point distance/target point)

MD 34090: REFP_MOVE_DIST_CORR (reference point offset/absolute

MD 34100: REFP_SET_POS (reference point value)

INTSIG “Reference point value 1...4” (DB31–34, DBX2.4, 2.5, 2.6, 2.7)

INTSIG “Referenced/synchronized 1, 2” (DB31–34, DBX60.4, DBX60.5)

Reference pointapproach with in-cremental measur-ing systems


6

07.2000


There are two phases of referencing for axes with distance-coded referencemarks:

Phase 1: Synchronize by travelling over 2 reference marks (2 measuring intervals)

Phase 2: Traverse to target point

General machine data

MD 34310: ENC_MARKER_INC (differential distance between two reference marks)

MD 34320: ENC_INVERS (measuring system inverted)


MD 11300: JOG_INC_MODE_LEVELTRIGGRD (INC and REF in jog mode)

MD 34010: REFP_CAM_DIR_IS_MINUS (approach reference point in minus direction)

MD 34040: REFP_VELO_SEARCH_MARKER (creep speed)

MD 34060; REFP_MAX_MARKER_DIST (maximum path to reference mark)

MD 34300: ENC_REFP_MARKER_DIST (reference mark distance)

INTSIG “Traversing keys plus/minus” (DB31–34, DBX8.6/DBX8.7)



MD 34070: REFP_VELO_POS (reference point approach speed)

MD 34080: REFP_MOVE_DIST (reference point distance/target point)

MD 34090; REFP_MOVE_DIST_CORR (reference point offset/absolute offset)

MD 34330: REFP_STOP_AT_ABS_MARKER (without target point)


Reference pointapproach with dis-tance-coded refer-ence marks


6

07.2000



6.10.8 Reference point approach for stepper motors

The basic sequence of referencing steps and the possible machine data set-tings are no different to those for referencing with an incremental encoder (cf./FB/, R1 “Reference point approach”). A BERO encoder which is mounted, forexample, on the motor shaft or spindle, takes the place of the incremental en-coder zero pulse. Synchronization takes place with the rising edge of the BERO(single-edge evaluation) or with the BERO centre (two-edge evaluation.

Note: MD 34200: ENC_REFP_MODE

� Phase 1: Travel to reference point cam (mech. cam or BERO, cf. /FB/, R1,“Reference Point Approach”),

� Phase 2: Synchronization with reference point BERO (zero pulse simulator),basic sequence as described in /FB/, R1, “Reference Point Approach”, Sec-tion “Reference Point BERO replaces zero mark”,

� Phase 3: Travel to reference point (cf. /FB/, R1, “Reference Point Ap-proach”).

A digital input is required for the transfer of switching edges to the control. TheFM–NC provides four digital inputs at inputs X13 to X16 on connector X1 (con-nector for handwheel and I/O device connection) for this purpose. There is afixed assignment between the four rapid digital inputs and the measuring cir-cuits.

When the selected BERO edge appears, the appropriate actual value register islatched. Referencing can therefore take place at very high velocities, the maxi-mum upper limit corresponding to half the maximum actual value counter perSERVO clock cycle. It must be noted that only one latch is provided per axis.

The positive edge of the BERO is interpreted as a zero pulse. The selection is made via MD 34200 ENC_REF_MODE = 2.

The positive edge and the negative edge of the reference point BERO are over-travelled in succession and the relevant actual values register. The averagevalue is the synchronization point at which phase 2 ends and phase 3 begins.

The selection is made in MD 34200 ENC_REF_MODE = 4.

The two-edge evaluation function allows any drift to be compensated. In thiscase, the maximum permissible velocity is additionally limited by the fact thatthe time between the two edges including any switching delay of the BEROmust be longer than 1 SERVO clock cycle.

Overview

Ablauf

Synchronizationwith BERO refer-ence point

BERO edge

Single-edge evaluation

Two-edge evaluation


6

07.2000


6.10.9 Extension to 5th axis

The SINUMERIK FM-NC is supplied as standard with the following configura-tion:

1 channel, 4 axes

It is not possible to extend the channels.

If you wish to increase the number of axes to 5, then you must connect an FM354 to the local P bus of the FM-NC.

References: /FB/, L1, “Local P Bus”

By connecting an FM 354 (FM servo) to the local P bus of the FM-NC, it is pos-sible to increase the number of machine axes controlled by the FM-NC fromfour to five. All the parameter settings and all the calculations for the 5th axis areperformed in the FM-NC.

The FM 354 acts as an actual value input and a setpoint output.

When the FM 354 (FM servo) is correctly configured as the 5th axis of theFM-NC, the yellow LED “DIAG” flashes in accordance with the selected basicclock cycle time.

Example:

If machine data MN10050 SYSCLOCK_CYCLE_TIME is parameterized as0.006, then the “DIAG” LED flashes in a 6-second cycle (3 s bright and 3 sdark).

The 5th axis (FM 354) need not be the 5th channel axis of the FM-NC. The 5thaxis is parameterized in exactly the same way as the other four axes.

The setpoint output of the FM 354 (on the local P bus) is assigned to an axiswith axis machine data MA30100 CTRLOUT_SEGMENT_NR[n] = 2 (identifierof local P bus).

The actual value input (measuring system) is assigned to the appropriate axiswith axis machine data MA30210 ENC_SEGMENT_NR[n] = 2 (identifier of localP bus).

!Important

It is not permissible to mix the axes of a setpoint output of the FM-NC and theactual value input of the 5th axis (FM 354), i.e. the setpoint output and the ac-tual value input of the 5th axis may only be operated on the same channel axis.

Overview

Extension to 5axes


6

07.2000



6.10.10 Basic settings for operator panel

MD 9000: LCD_CONTRAST (contrast)The contrast setting can be entered directly into the machine data on MMCs100/100.2 with monochrome display or else made in the operator control area“Start–up” via the softkeys “LCD brighter” and “LCD darker”.

MD 9001: DISPLAY_TYP (monitor type)The monitor type (LCD monochrome, LCD colour, CRT colour) is entered in thisMD.

MD 9003: DISPLAY_LANGUAGE (foreground language)

The MMC user interface is supplied as standard with two languages (English,German); English is the default setting. The language can be switched over inthe operator control area “Start–up” via the softkey “Change language”.

MD 9004: DISPLAY_RESOLUTION (display resolution)

The display resolution for position values on the screen is set in this MD. Themaximum screen display capacity is 10 digits plus decimal point and sign (e.g. 4places after decimal point, max. display =+/–999999.9999).

Exception:

On MMCs 100/100.2 the spindle speed is always displayed with three decimalpoints regardless of the setting of MD 9004.

On MMCs 102/103 the display resolution for the spindle speed is set via

MD 9010: SPIND_DISPLAY_RESOLUTION (spindle speed display resolution)

MD 9006: The time which elapses before the screen is darkened (assumingthat no key is actuated on the operator panel in the meantime) is entered in thisMD (for MMCs 100/100.2).

The protection levels for user data are set in machine data 9200 to 9299.

The settings of the MMC V24 interface are stored for back-up purposes in ma-chine data 9300 and above. The setting for 3 different devices is made in theServices menu via an input display.

Screen

Language

Display resolution

Screen darkening

User data protec-tion levels

V24 interfaces


6

07.2000


6.10.11 Configuration and machine data of local P bus of FM-NC

References: /FB/, L1, “FM–NC Local Bus”

The purpose of the FM–NC local P bus is to extend the functionality of theFM–NC. An FM 354 (FM servo) and digital input and output modules (SMs) canbe connected to this bus. These modules increase the number of FM–NC axesfrom four to five and provide the FM–NC with digital inputs and outputs.

No more than one FM 354 (FM servo) may be connected to the local P bus as a5th axis.

The hardware for a maximum for 20 digital inputs and 20 digital outputs (nos. 9to 28) may be connected to the local P bus. Nos. 1 to 8 are always simulationinputs/outputs.

Example:

Nos. 1 to 8 No hardware (simulation inputs)Nos. 9 to 24 2 signal modules with 8 digital inputs eachNos. 25 to 32 FM 354 with 4 digital hardware inputs (nos. 25 ... 28) and 4

simulation inputs (nos. 29...32)

The following machine data are used to assigned the input/output modules tothe FM–NC:

� MN10362 HW_ASSIGN_ANA_FASTIN[0...3]

� MN10364 HW_ASSIGN_ANA_FMSTOUT[0...3]

� MN10366 HW_ASSIGN_DIG_FASTIN[0...3]

� MN10368 HW_ASSIGN_DIG_FMSTOUT[0...3]

The following applies to these MDs:MD: 02 0x 01 0x

Byte no.

Submodule no.

Slot in local P bus

Local P bus

Example: The local P bus of the FM–NC is configured as follows:

FM–NCNCU 570

FM 354 (FM servo)

16 dig.outputs

16 dig.inputs

. . .

Slot in local P bus 1 3I9...16Q9...16

Q17...24 Q25...28I17...24I25...28

2

Overview

FM 354 as 5th axis

Inputs/outputs

Machine data forinputs/outputs


6

07.2000



The machine data settings are therefore as follows:

MN10366...IN[0] = 02 02 01 01 I 9...16MN10366...IN[1] = 02 02 01 02 I17...24MN10366...IN[2] = 02 03 01 01 I25...28MN10366...IN[3] = 02 00 01 00 not assigned

MN10368...OUT[0] = 02 01 01 01 Q 9...16MN10368...OUT[1] = 02 01 01 02 Q17...24MN10368...OUT[2] = 02 03 01 01 Q25...28MN10368...OUT[3] = 02 00 01 00 not assigned

!Important

The FM 354 (FM servo) has four digital inputs/outputs which can be addressedvia front connector X1. The remaining digital inputs/outputs of the byte (29...32)can be addressed as simulation inputs/outputs.

The input and output bytes are activated with the machine data

� MN10300 FASTIO_ANA_NUM_INPUTS

� MN10310 FASTIO_ANA_NUM_OUTPUTS

� MN10350 FASTIO_DIG_NUM_INPUTS

� MN10360 FASTIO_DIG_NUM_OUTPUTS

Possible setting value Meaning

1 1...8 NCK I/O without hardware (simulation)

2 9...16 ext. I/O of FM–NC (local P bus)



The PLC (CPU) reads the configuration of the local P bus in exactly the sameway as the configuration of the P bus during booting of the FM-NC.

The rack configuration is displayed in the online view of the STEP7 hardwareconfiguration. The local bus is parameterized in the offline view of the hardwareconfiguration as follows:

� Select the module NCU-570

� Select Object properties/Basic parameters in the menu Edit

� Activate Process alarm generation and Local bus segment with Yes

� Confirm configuration with OK and transfer to the control with the menucommand Target system/Load to module

(SDB100 is generated and transferred to the PLC). The local P bus is then acti-vated.

Setting the usabledig. inputs/outputs

Configuration


6

07.2000


6.10.12 Spindle data

In the SINUMERIK FM–NC control system, the spindle is a sub-function of theentire axial functionality. The machine data for the spindle are therefore locatedamong the axis machine data (from MD 35000 onwards). For this reason, datamust be entered for a spindle which are described in the chapters relating toaxis start-up. The following description contains merely a cross-reference tothese MD.

Note

The standard machine data do not include any spindle setting. An appropriatestart-up operation must be performed in order to define a spindle (seeSection 6.2 “Example MD file”).

References: /FB/, S1, “Spindles”

The following machine data are required to define a spindle:MD30300: IS_ROT_AX (rotary axis)MD 30320: DISPLAY_IS_MODULO (display referred to 360 degrees)MD 35000: SPIND_ASSIGN_TO_MACHAX (assignment between spindle andmachine axis)Entry of spindle number under which the spindle is to be addressed.

The following spindle operating modes are provided:

� Open-loop control mode (M3, M4, M5)

� Oscillation mode (support for gear changing operations)

� Positioning mode (SPOS, SPOSA)

� Synchronous mode

� Rigid tapping

In spindle mode, the feedforward control switches on as standard (FFW mode= 1). Exception: In the case of rigid tapping, the feedforward control acts onlywhen activated explicitly (e.g. by means of the programming commandFFWON).

The set of parameters is selected that corresponds to the current gear stage.

Example: 2nd gear stage � Parameter set [2]

It is possible to switch directly from spindle mode into axis mode provided thatthe same drive is used for both modes. The machine data for one axis must beapplied in axis operation. In axis mode, the first parameter set (index [0]) is se-lected irrespective of the current gear stage.

After the spindle has been positioned, the rotary axis can be programmed di-rectly with the axis name.

INTSIG “Axis/spindle” (DB31–35, DBX60.0)

Overview

Spindle definition

Spindle operatingmodes

Axis mode


6

07.2000



MD 20090 SPIND_DEF_MASTER_SPIND (master spindle reset position inchannel)

MD 35020: SPIND_DEFAULT_STATUS (spindle initial setting)This MD allows a spindle initial setting to be defined. The following are possible:

� Speed control without/with position control

� Positioning mode

� Axis mode

The time at which the spindle initial setting acts is defined by means of MD35030 SPIND_DEFAULT_ACTIVATION.The following are possible:

� POWER ON

� POWER ON and program start

� POWER ON, program start and reset

MD 35040 SPIND_ACTIVE_AFTER_RESET (independent spindle reset)This MD determines whether the spindle must be stopped by a RESET or aprogram end. If the MD has been set, a termination of the spindle functionsmust be initiated explicitly via a program command or the INTSIG “Spindle re-set” (DB31–48, DBX2.2).

MD 35010 GEAR_STEP_CHANGE_ENABLE (gear stage changeover possible.Spindle has several gear stages).If this machine data is not set, the system assumes that the spindle has no gearstages. A gear stage changeover is therefore impossible.

In the case of machine data which are stored as a field, the first value is alwaysassigned to the first parameter, e.g. 1st reference point value, 1st encoder num-ber.This is not the case for the following machine data with the field parameter“Gear stage no.” and “Control parameter set no.”. With these data, the selectedgear stage determines the appropriate field index. The field with the index “0”is not used for the spindle machine data. See Section 6.10.2.

MD 35110: GEAR_STEP_MAX_VELO (nmax for gear stage changeover)MD 35120: GEAR_STEP_MIN_VELO (nmin for gear stage changeover)MD 35130: GEAR_STEP_MAX_VELO_LIMIT (nmax for gear stage)MD 35140: GEAR_STEP_MIN_VELO_LIMIT (nmin for gear stage)MD 35200: GEAR_STEP_SPEEDCTRL_ACCEL (acceleration in speed controlmode)MD 35210: GEAR_STEP_POSCTRL_ACCEL (acceleration in position controlmode)MD 31050: DRIVE_AX_RATIO_DENOM (denominator load gearing)MD 31060: DRIVE_AX_RATIO_NUMERA (numerator load gearing)MD 32200: POSCTRL_GAIN (loop gain factor)MD 36200: AX_VELO_LIMIT (threshold value for speed monitoring)

Example

MD 35110: GEAR_STEP_MAX_VELO [0,AX1] = 500 (not used for spindle)MD 35110: GEAR_STEP_MAX_VELO [1,AX1] = 500 (nmax for gear stagechange, gear stage 1)MD 35110: GEAR_STEP_MAX_VELO [2,AX1] = 1000 (nmax for gear stagechange, gear stage 2)

General machinedata definitions

Exception regard-ing machine dataparameterization


6

07.2000


6.10.13 Spindle configuration

Setpoints:

MD 30100 CTRLOUT_SEGMENT_NR MD 30110 CTRLOUT_MODULE_NR MD 30120 CTRLOUT_NR MD 30130 CTROUT_TYPE

Actual values:

MD 30210 ENC_SEGMENT_NRMD 30220 ENC_MODULE_NR MD 30230 ENC_INPUT_NR MD 30240 ENC_TYPE

Note

Further information about the spindle configuration can be found inSection 6.10.1 .

6.10.14 Encoder matching (spindles)

For the purpose of matching the spindle encoder, the same machine data applyas for the axis. MD: IS_ROT_AX must always be set for the spindle so that theencoder is always matched in relation to one revolution. In order to obtain adisplay which is always referred to 360 degrees,MD: DISPLAY_IS_MODULO must be set.

Table 6-8 Machine data for encoder matching

Machine data Rotary axis

Encoder onmotor

Encoder onspindle

30300: IS_ROT_AX 1 1

31000: ENC_IS_LINEAR 0 0

31040: ENC_IS_DIRECT 0 1

31020: ENC_RESOL Marks/rev Marks/rev

31080: DRIVE_ENC_RATIO_NUMERA Motor rev Load rev

31070: DRIVE_ENC_RATIO_DENOM Encoder rev Encoder rev

31060: DRIVE_AX_RATIO_NUMERA Motor rev See note

31050: DRIVE_AX_RATIO_DENOM Load rev See note

Machine data forsetpoints and actual values

Machine data forencoder matching


6

07.2000



Note

These MD are not required to match the encoder, but they must be enteredcorrectly for the sake of setpoint calculation. Load revolutions are entered inMD 31050: DRIVE_AX_RATIO_DENOM and motor revolutions in MD 31060: DRIVE_AX_RATIO_NUMERA.

1st example of encoder matching:

Spindle with raw signal encoder (500 pulses) mounted directly on the spindle.Internal multiple = 4. Internal calculation resolution = 1000 increments per de-gree.

MD31020 � 4

360 degreesInternal resolution =

MD31070

MD31080� � 1000

500 � 4 � 1

360 � 1 � 1000Internal resolution = = 180

The encoder increment corresponds to 180 internal increments. An encoderincrement corresponds to 0.18 degrees (highest possible positioning resolu-tion).

2nd example of encoder matching:

Spindle with rotary encoder on motor (2048 pulses), internal multiple = 4, 2 gearstages:Gear stage 1: Motor/spindle = 2.5/1Gear stage 2: Motor/spindle = 1/1

Gear stage 1

MD31020 � 4

360 degrees

MD31070

MD31080� � 1000 Incr/degr.�

MD31060

MD31050Internalresolution

=

4 � 2048 puls.

360 degrees 1� 1000 puls./deg.

1

1

2.5= 17.5781Internal

resolution= � �

One encoder increment corresponds to 17.5781 internal increments. An en-coder increment corresponds to 0.0175781 degrees (highest possible position-ing resolution).

Gear stage 2

MD31020 � 4

360 degrees

MD31070

MD31080� 1000 Incr/deg.�

MD31060

MD31050Internalresolution

= �

4 � 2048 puls

360 degrees 11000 puls./degr.

1

1

1= 43.945Internal

resolution= � � �

One encoder increment corresponds to 43.945 internal increments. One en-coder increment corresponds to 0.043845 degrees (highest possible positioningresolution).


6

07.2000


6.10.15 Speeds and setpoint adjustment (spindles)

With the SINUMERIK FM–NC control, the spindle speed output is implementedin the FM–NC. The control contains the data for 5 gear stages.

These stages are defined by a minimum and maximum speed for the stage it-self and by a minimum and maximum speed for the automatic gear stagechangeover.

A new gear stage is output only if the newly programmed speed setpoint cannotbe traversed in the present gear stage.

The setpoint output ramp is defined by the input of an acceleration value forcontrol operation; it is possible to specify a reduced acceleration rate in order totake account of the torque limitation in the field weakening range.

For the sake of simplification, the oscillation times for gear stage changeoverscan be specified directly in the FM–NC; the oscillation function must otherwisebe implemented in the PLC. The oscillation function is initiated via the PLC.

The spindle speeds for conventional operation are entered in axis machine dataMD 32010: JOG_VELO_RAPID (conventional rapid traverse) and MD 32020:JOG_VELO (conventional axis velocity). The direction of rotation is specified viathe appropriate directional keys for the spindle on the MCP.

The rotational direction with respect to a spindle corresponds to the traversingdirection with respect to an axis (see Section 6.10.5).

These speed data must be transferred in scaled form to the drive for the drivecontrol. The values are scaled in the NC on the basis of the gear stage speeddefinitions. The maximum speed setpoint is specified at the maximum gearstage speed. The spindle attains the desired speed via the mechanical gearstage.

Machine data and interface signals:

MD35110: GEAR_STEP_MAX_VELO (maximum speed for gear stage changeover)

MD35120: GEAR_STEP_MIN_VELO (minimum speed for gear stage changeover)

MD35130: GEAR_STEP_MAX_VELO_LIMIT (gear stage maximum speed)

MD35140: GEAR_STEP_MIN_VELO_LIMIT (gear stage minimum speed)

MD35200: GEAR_STEP_SPEEDCTRL_ACCEL (acceleration in speed control mode)

MD35220: ACCEL_REDUCTION_SPEED_POINT (speed for reduced acceleration)

MD35230: ACCEL_REDUCTION_FACTOR (reduced acceleration)

Speeds

Speeds for con-ventional opera-tion

Direction of rota-tion

Setpointadaptation


6

07.2000



MD 35400: SPIND_OSCILL_DES_VELO (oscillation speed)MD 35410: SPIND_OSCILL_ACCEL (acceleration in oscillation mode)MD 35430: SPIND_OSCILL_START_DIR (start direction in oscillation mode)MD 35440: SPIND_OSCILL_TIME_CW (oscillation time for direction M3)MD 35450: SPIND_OSCILL_TIME_CCW (oscillation time for direction M4)

MD 31060: DRIVE_AX_RATIO_NUMERA (numerator load gearing)MD 31050: DRIVE_AX_RATIO_DENOM (denominator load gearing)

MD 32010: JOG_VELO_RAPID (conventional rapid traverse)MD 32020: JOG_VELO (conventional axis velocity)

INTSIG “Change over gear” DB31 to DB34, DBX82.3INTSIG “Setpoint gear stage” DB31–34, DBX82.0 to DBX82.2INTSIG “No speed monitoring for gear changeover” DB31 to 34, DBX16.3INTSIG “Gear stage changed over” DB31 to DB34, DBX16.3INTSIG “Setpoint gear stage” DB31 to DB34, DBX16.0 to DBX16.2INTSIG “Oscillation speed” DB31 to DB34, DBX18.5INTSIG “Oscillation via PLC” DB31 to DB34, DBX18.4INTSIG “Oscillation mode” DB31 to DB34, DBX84.6INTSIG “Control mode” DB31 to DB34, DBX84.7INTSIG “Traverse keys minus” DB31 to DB34, DBX4.6INTSIG “Traverse keys plus” (DB31 to DB34, DBX4.7

Speed

Max. spindle speed

ÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉ

Max. speed of gear stage 2Max. speed for gear stage 2 changeover

Max. speed of gear stage 1Max. speed for gear stage 1 changeover

Min. speed for gear stage 2 changeover

Min. speed for gear stage 2

Min. speed for gear stage 1 changeverMin. speed for gear stage 1

Min. spindle speed

(rev/min

ÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉ

Gea

rst

age

2

Gea

rst

age

1

0

Fig. 6-25 Example of speed ranges with automatic gear stage selection (M40)


6

07.2000


6.10.16 Spindle positioning

The control provides an “oriented spindle stop” function with which the spindlecan be moved into a certain position and held there (e.g. for tool changing pur-poses). Several programming commands are available for this function whichdefine the approach and program processing.

References: /PA/, Programming Guide

� To absolute position (0 – 360 degrees)

� Incremental position (+/– 999999.99 degrees)

� Block change when position reached

� Block change on block end criterion

The control brakes the spindle down to creep speed at the acceleration rate forspeed operation. If the creep speed has been reached (INT “Spindle in setpointrange”), the control branches into position control mode and the accelerationrate for position control mode and the SG factor become active.

The interface signal “Exact stop fine” is output to indicate that the programmedposition has been reached (block change when position reached). The accel-eration rate for position control mode must be set such that the current limit isnot reached.

The acceleration rate must be entered separately for each gear stage. If thespindle is positioned from zero speed, it is accelerated up to a maximum speedcorresponding to creep speed; the direction is defined via machine data. Thecontour monitoring function is activated as soon as the control mode switches toposition control.

MD 35300: SPIND_POSCTRL_VELO (creep speed)MD 35350: SPIND_POSITIONING_DIR (direction of rotation on positioning from zero speed)MD 35210: GEAR_STEP_POSCTRL_ACCEL (acceleration in position control mode)MD 36000: STOP_LIMIT_COARSE (exact stop coarse)MD 36010: STOP_LIMIT_FINE (exact stop fine)MD 32200: POSCTRL_GAIN (SG factor)MD 36400: CONTOUR_TOL (contour monitoring)INTSIG “Position reached with exact stop fine/coarse” (DB31 to DB34, DBX60.6/60.7)INTSIG “Positioning mode” (DB31 to DB34, DBX84.5)

Overview

Functionality

Machine data andinterface signals


6

07.2000



6.10.17 Spindle synchronization

The spindle must synchronize its position with the measuring system. Thespindle position is always synchronized with the zero mark of the encoder orwith a Bero signal connected to the FM–NC drive module.

MD 34200 ENC_REFP_MODE is used to specify through which signal synchro-nization is effected (zero mark via BERO).

� After switch-on of the control if the spindle is moved with a programmingcommand.

� The PLC signal “Re-synchronize spindle 1/2” always cancels the “Refer-enced/synchronized 1/2” signal; the spindle is re-synchronized with the nextreference signal.

� After every gear stage changeover (MD 31040: ENC_IS_DIRECT=0)

� The spindle goes out of synchronism if a speed above the encoder limit fre-quency is programmed. When the speed drops to below the encoder limitfrequency, the spindle is re-synchronized. If the synchronized state hasbeen lost, it is impossible to implemented functions such as rotational fee-drate, constant cutting velocity, tapping with and without compensatingchuck, positioning and axis modes.

To synchronize the spindle, it must always be rotated via a programming com-mand (e.g. M3, M4, SPOS). It is not sufficient to enter a spindle speed via thedirectional keys of the appropriate axis on the machine control panel.

MD34100: REFP_SET_POS (reference point value, zero mark position)The position of the reference signal during synchronization is entered in thisMD.

MD34090: REFP_MOVE_DIST_CORR (reference point offset, zero mark offset)The zero mark offset resulting from the synchronization process is entered here.

MD34200: ENC_REFP_MODE (position measuring system type)INTSIG “Re-synchronize spindle 1,2” (DB31 to DB34, DBX16.4 or 16.5)INTSIG “Referenced/synchronized 1,2” (DB31 DB34, DBX60.4 or 60.5)

Overview

When issynchronizationnecessary?

Machine data andinterface signals


6

07.2000


6.10.18 Monitoring functions (spindles)

If the velocity/speed drops below the value entered in MD 36060: STAND-STILL_VELO_TOL, then the interface signal “Axis/spindle stationary” is output.

The path feed is then enabled if MD 35500:SPIND_ON_SPEED_AT_IPO_START is set.

If the spindle reaches the tolerance range specified in MD 35150: SPIND_DES_VELO_TOL, then the signal “Spindle in setpoint range” is output. The pathfeed is then enabled if MD 35500: SPIND_ON_SPEED_AT_IPO_ START is set.

The maximum spindle speed is entered in MD SPIND_MAX_VELO_LIMIT andthe minimum in MD SPIND_MIN_VELO_LIMIT. The NCK limits the speeds tothe set values. However, if the actual speed exceeds the set value by the speedtolerance (drive error), then the interface signal “Speed limit exceeded” is outputand alarm 22050 “Channel [name] block [number] spindle [number] maximumspeed reached” is output.

The spindle speed is also monitored via MD AX_VELO_LIMIT; an alarm is gen-erated when the speed threshold is exceeded.

The maximum spindle speed is entered in MD 35100: SPIND_VELO_ LIMIT.The NCK limits the speed to this value. If, however, the speed is exceeded bythe speed tolerance in spite of the NCK limitation (drive error), then the INTSIG“Speed limit exceeded” is output together with the alarm “22100 channel [name]block [number] spindle [number] maximum chuck speed exceeded”.

The spindle speed is also monitored by MD 36200; AX_VELO_LIMIT; an alarmis generated if the set value is exceeded. In position-controlled mode (e.g.SPCON), the maximum speed (control reserve) specified via MD or setting datais limited to 90% internally in the control.

The maximum gear stage speed is entered inMD 35130; GEAR_STEP_MAX_VELO_LIMIT and the minimum speed inMD 35140: GEAR_STEP_MIN_VELO_LIMIT. The speed cannot leave thisrange when the appropriate gear stage is engaged.

Function G25 S... permits a minimum spindle speed to be programmed andfunction G26 S... a maximum spindle speed limitation. The limitation is active inall operating modes.

Function LIMS=... allows a spindle speed limit for G96 (constant cutting velocity)to be specified. This limitation is operative only when G96 is active.

Axis/spindle stationary

Spindle in setpointarea

Minimum and max-imum spindlespeeds

Maximum spindlespeed

Minimum and max-imum gear stagespeeds

Programmablespindle speed limitations


6

07.2000



The maximum encoder limit frequency (MD 36300: ENC_FREQ_LIMIT) is moni-tored. If this limit is exceeded, the synchronization is lost and the spindle func-tionality reduced (thread, G95, G96). The position measuring systems which areout of synchronism are automatically re-synchronized as soon as the speeddrops below the encoder limit frequency again. The encoder limit frequencyvalue must be such that the mechanical encoder speed limit is not exceeded orelse the synchronization from high speeds will be incorrect.

Speedn

MD36300 ENC_FREQ_LIMIT

MD35110 GEAR_STEP_MAX_VELO

MD35130 GEAR_STEP_MAX_VELO_LIMIT

Programmable spindle speed limitation G26



MD35140 GEAR_STEP_MIN_VELO_LIMIT

MD35120 GEAR_STEP_MIN_VELO

MD36060 STANDSTILL_VELO_TOL

INTSIG “Axis/spindle stationary” (DB31–34, DBX61.4)Spindle speed rangeSpeed range of active gear stageSpeed range limited by G25 and G26Speed range for constant cutting velocity through G92INTSIG “Referenced/synchronized” (DB31–34, DBX60.4/60.5)

MD36200 AX_VELO_LIMITMD35100 SPIND_VELO_LIMIT

Actual speed monitoringMaximum spindle speed

Fig. 6-26 Spindle monitoring ranges

Maximum encoderlimit frequency


6

07.2000


6.11 Start-up of functions

In this case, “Functions” refers to the NC functions of the FM–NC (e.g. H1 hand-wheel, E1 electronic gearing, etc.), each of which represents an independentfunction complex while forming part of the total functionality of a CNC.

References: /FB/, Description of Functions

These are functions that are always contained in the FM–NC and are includedin the basic description of functions.

These are functions which cannot be described as basic functions (e.g. S3 syn-chronization spindle, T2 table interpolator). They must be ordered specially bythe customer (options). These, together with the basic functions, represent thetotal functionality of the FM–NC.

A function description is provided for all functions. These descriptions containdetailed information about the functions and how to deal with them, a data de-scription (MD, SD variable) and a signal description.


The functions must be adapted to the machine controlled by the FM–NC and tothe specific requirements of the customer, i.e. they must be started up.

A description of how the functions are adapted and started up is given in


�

What are functions?

Basic functions

Extended functions

Description offunctions

Starting up a function

6.11 Start-up of functions

6

07.2000



7


PLC

7.1 PLC applications 7-156. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

7.2 Mode switch on CPU 7-160. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

7.3 CPU: Status and error displays 7-162. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

7.4 CPU: MPI Multi-point interface 7-163. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

7.5 CPU operating status for FM-NC start-up 7-163. . . . . . . . . . . . . . . . . . . . . . .

7.6 Overview of organization blocks, function blocks, DBs 7-165. . . . . . . . . . . .

7.7 Interface signals 7-165. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

7

7

07.2000



7.1 PLC applications

References: /FB/, P3, “PLC Basic Program”


The SIMATIC S7–300 CPU is used as an interface control.

Data are exchanged between the NC and PLC via the P-bus and C-bus.

DB

PLCuserprogram

Userinterface

PLC

P bus

K busOperator panelMCP

CPU

MPI

COM NCK

FM–NC

Bus driver

Basicprogram

PLC system SW

Fig. 7-1 NC–PLC link

The program is modular, i.e. it is structured according to NCK functions. Further-more, a distinction is made between the various routine levels specified by theoperating system.

These are as follows:

� Starting and synchronization

� Cyclic operation

� Process alarm processing

The relevant section of the basic program must be called by the user in OBs 1,40 and 100.

The basic PLC program is part of the FM-NC Tool Box.

Observe the special notes given in Section 12.4.1 when using a CPU 318

Interface betweenNC and PLC

General

Tool Box

Special notes con-cerning CPU 318


7

07.2000


The following diagram provides an overview of how the basic PLC program isstructured:

Process alarm

Cyclicprocessing

Start-up

GP_PRAL

GP–OB1 NCKMode groupChannelAxisSpindle

Aux./G function dis-tributor

TD(for 840D)

Complete restart

Userprogram

Userprogram

Userprogram

OB40

OB1

OB100

G groupdistributor

M decoder

M, S, Fdistributor

FB1

FC14

FC3

MCP

FC6

Conc. axes,ASUP, etc.

FC(15/16/9)

Error and operationalmessages

FC10

MCPMCP_IFMMCP_IFT

FC19/25

TDTM_TransTM_Dir

FC8/22

FC2

Fig. 7-2 Structure of PLC basic program

Structure


7

07.2000



The CPU always powers up in the COMPLETE RESTART mode, i.e. the PLCoperating system runs through OB100 after initialization and then begins cyclicoperation at the start of OB1. No re-entry is made at the interruption point (e.g.in the case of power failure).

In terms of time, the basic program is executed before the PLC user program isprocessed. The NC/PLC interface is completely processed in cyclic operation.The present G functions are transmitted to the PLC on the process alarm level ifthe function is activated.

A cyclical monitoring function is activated between the PLC and NCK after ter-mination of power-up and the first OB1 cycle. In the event of PLC failure, thealarm “2000 sign of life monitoring PLC”.

There are both retentive and non-retentive areas for flags, timers and counters.Both areas are contiguous and are separated by a parameterizable limit, thearea with the high-order area addresses being defined as the non-retentivearea. PLC data blocks are always retentive.

If the retentive area is not buffered, then start-up is inhibited. The followingpoints are processed during restart.

� Erase Ustack, Bstack and non-retentive flags, timers and counters

� Erase process image of outputs (PIO)

� Discard process and diagnostic alarms

� Update system status list

� Evaluate parameterization objects of modules (as of SD100) or output de-fault parameters to all modules in single-processor operation

� Process restart OB (OB100)

� Read in process image of inputs (PII)

� Cancel command output inhibit

Start-up, cyclic operation andsign-of-life monitoring

COMPLETERESTART start-upmode


7

07.2000


The basic routine organizes the exchange of signals and data between the PLCuser program and the internal NCK interface.

User interfaceOB1

Signals to NC

OB40

HIFU-distributor M decoderM,S,T,Frouting

BP cyclic section

Messageacquisition

VDIsignal transfer

VDIsignal transfer

BP interrupt-driven sec-tion

G groupdecoder

Transfer, acknowledgem.rapid HIFU

MCPsignals

Signalsfrom MMC

Signalsfrom NC

Alarms &messages

SFC

Diagnosticbuffer

MMC2)

TransferMCP signals

HIFI buffer

NC → PLCsignals

MSD signals

Status signals

Auxiliary functs.

G functions

Alarm status

from NC

PLC → NCsignals

to NC

Control signals

ASUPinterface

Concurrentpositioning axis

MCP signals

MMC1)

1) Entry by variable service

2) Transfer by message services

Fig. 7-3 Data flow between NC/PLC

Functions of PLCbasic routine


7

07.2000



7.2 Mode switch on CPU

Since the FM–NC is a module of the automation system 300, the PLC (CPU)functions as the system “master”. This means that the system CPU, i.e. thePLC–CPU, must be successfully started up before any start-up measures forthe FM–NC can be undertaken.


/S7H/, Manual

Fig. 3-4 shows the CPU elements which are relevant for starting up the FM–NC:

� Mode switch,

� Status and error display

� Multi-point interface MPI

1

5

6

9

SFBAFDC 5 VCFORCERUNSTOP

ML+M

RUN–PRUNSTOPMRES

Memorycard slot

Multi-port interface MPI

Status and Errordisplay

Mode switch

Back-up batterycompartment

Jumper (removable)

Connection forpower supplyand functionearth

Fig. 7-4 Elements of a PLC–CPU

The positions of the elements of the PLC–CPU may deviate slightly from thelayout shown in Fig. 7-4 (e.g. in case of CPU 318).

Overview


7

07.2000


The order in which the mode switch settings are described corresponds to theorder in which they are arranged on the CPU. The explanatory information re-fers to an “unprotected” CPU. (Please refer to the STEP7 description for an ex-planation of the various protection levels of the CPU).

Table 7-1 Mode switch on CPU

Mode switchsetting

Meaning Explanation

RUN–P “RUN program” operating status

The CPU is processing the user program.The key cannot be removed in this position.Programs can be

� read out of the load memory by means of the PG (CPU � PG)

� transferred to the load memory of the CPU (PG� CPU).

RUN “RUN” operating status

The CPU is processing the user program.The keyswitch can be removed in this posi-tion to prevent unauthorized persons fromchanging the operating mode.Programs in the load memory of the CPUcan be read out by means of the PC(CPU � PG).The program in the load memory cannotbe changed in the “RUN” mode!(� STEP7 description).

STOP “STOP” operating status

The CPU is not processing a user program. The key can be removed in this position toprevent unauthorized persons from chang-ing the operating mode.Programs can be

� read out of the load memory by means of the PG (CPU � PG)

� transferred to the load memory of the CPU (PG� CPU).

MRES Memory reset Keyswitch position to reset the memory ofthe CPU. A special sequence of operations must befollowed to reset the memory via the key-switch (see CPU Manual, Chapter 8.3 ofSIMATIC S7–300).See Sections 7.5 and 5.3.3


Mode switchsettings


7

07.2000



7.3 CPU: Status and error displays

The status and error displays are explained in the order in which they are arran-ged on the CPU.

Table 7-2 Status and errors displays of CPU

Display Meaning Explanation

SF (red) Group error Lights up in the case of

� hardware faults

� firmware errors

� programming errors

� computational errors

� timing errors

� defective memory card

� battery failure or no back-up with mains ON

� I/O faults.Use PG to determine exact fault/error (readout diagnostics back-up).

BAF (red) Battery fault Lights up if battery is defective or missing.Flashes if battery needs to be replaced.

DC5V (green) 5 V DC supply forCPU and S7–300 bus

Lights up if internal DC 5 V supply is O.K.

FORCE (yellow) Reserved The FORCE functions assigns a definedvalue to a variable. The variable is write-protected and cannot be altered from anylocation. The write-protective remains effec-tive until it is cancelled again by the UN-FORCE function. If the FORCE LED is off,then no FORCE job is present.

RUN (green) “RUN” operating state

Lights up when the CPU is processing theuser program.Flashes (2 Hz) during CPU start-up (STOPdisplay also lights up during start-up; out-puts are enabled once STOP display hasgone out).Flashes (0.5 Hz) when the “breakpoint” testfunction is active (STOP display also lightsup).

STOP (yellow) “STOP” operating state

Lights up when

� CPU is not processing a user program,

� “breakpoint” test function is active(RUN display also flashes).

Flashes at 3 s intervals if CPU requestsmemory reset.

Meaning of statusand error displays

7.3 CPU: Status and error displays

7

07.2000


7.4 CPU: MPI Multi-point interface

The interface on the PLC–CPU which allows connection of equipment such asPGs is designated the “multi-point interface” because several items of equip-ment (i.e. at various points in configuration) can access the CPU via this inter-face.

In other words, the PLC–CPU with an MPI multi-point interface is has a network-ing capability without any additional modules!

The FM–NC is also connected via this interface(e. g. PG –– MPI –– PLC CPU –– C-bus –– FM–NC).

The following items of equipment can be connected to the MPI multi-point inter-face:

� Programming devices (PG/PC), each with MPI interface

� OPs (e.g. OP 27)

� MMC

� MCPs

� other S7–300 controllers.

Use only Siemens bus connectors or PG cables to connect equipment to theMPI multi-point interface.

References: /BU/, Ordering Information

7.5 CPU operating status for FM-NC start-up

The PLC–CPU must be operating in the “cyclic” mode. The VDI interface (PLC/NC) interface is active (OB1 processing) in “cyclic operation”.

The mode switch must be set to “RUN” and only the green LEDs “DC5V” and“RUN” are alight on the status and error display.

Definition: Multi-point interface MPI

Other equipment

Connectors

Cyclic operation

7.4 CPU: MPI Multi-point interface

7

07.2000



By setting the mode switch to the appropriate position, the COMPLETE RE-START and MEMORY RESET functions can be executed as described below:

� COMPLETE RESTART

Turn mode switch from STOP position to RUN position.

� MEMORY RESET

– Turn mode switch to “STOP” position (select STOP operating state)

� LED STOP lights up

– Turn mode switch to “MRES” position and hold it there until STOP LEDlights up again (request memory reset)

� LED STOP goes out and lights up again.

– Turn mode switch to positions STOP–MRES–STOP within 3 seconds

� LED STOP first flashes at approx. 2 Hz and then lights up again

� LED FORCE lights up

No memory reset is requested if the switch is held in the MRES positionfor less than 3 seconds. The STOP LED also remains off if the switchposition is not changed from STOP–MRES–STOP within 3 seconds.

– Once LEDs STOP and FORCE are alight, turn mode switch to RUNposition

� LED STOP and LED FORCE go out and LED RUN (green) lights up

� PLC memory is now reset and PLC is operating in cyclic mode

The program memory of the PLC is erased by the MEMORY RESET function.System data blocks and the PLC diagnostic back-up are not erased.

Note

If the MEMORY RESET function is initiated (using procedure described above)when the back-up battery is not installed, then the entire SRAM of the PLC iserased, i.e. the system data blocks and diagnostic back-up are also erased.These data can no longer be accessed. The system data blocks must be trans-ferred to the memory again.

No memory reset is requested if the switch is held in position 3 (MRES) for lessthan 3 seconds. The STOP LED also remains off if the switch position is notchanged from STOP–MRES–STOP within 3 seconds.


COMPLETERESTART andMEMORY RESETvia mode switch

7.5 CPU operating status for FM–NC start-up

7

07.2000


7.6 Overview of organization blocks, function blocks, DBs

References: /FB/, P3, “Basic PLC Program”

7.7 Interface signals

The interface signals are listed in

References: /LIS/, Lists

�


7

07.2000




8


Alarm and Message Texts

8.1 Alarm text files for MMC100/100.2 8-168. . . . . . . . . . . . . . . . . . . . . . . . . . . . .

8.2 Alarm text files for MMC 102/103 8-170. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

8.3 Syntax for alarm text files of cycles and PLC alarms 8-173. . . . . . . . . . . . . .

8

8

07.2000



8.1 Alarm text files for MMC100/100.2

The installation routine stored on the MMC100/100.2 application diskette (seeSection 12.2.2) transfers

� configuration settings,

� texts,

� the configured interface and

� the user software

from the update directory on your PC/PG to the MMC100/100.2 hardware.

This section describes the ways in which the alarm text files can be adaptedbeforehand.

� PC/PG with DOS 6.x or higher

� V.24 cable between the COM interface of the MMC100/100.2 (X6) and theCOM1 or COM2 interface of your PC/PG

� At least 3 MB free space on hard disk

� The following description is based on the assumption that you have alreadytransferred the software from the supplied application diskette for MMC100(no. 2) or MMC100.2 (no. 3) to the hard disk of your PC/PG as described inSection 12.2.2.

MMC100/100.2 can be assigned two languages in online mode. These are re-ferred to as the foreground and background languages. It is possible to ex-change the foreground and background languages of the MMC system usingthe application diskette as described in Section 12.2.2.

During installation, it is possible to select any combination of two of thelanguages on the application diskette as the foreground and backgroundlanguages.

The languages German and English are to be found on the application diskette.Other languages are available on language diskettes and must be saved intothe same directory as the application diskette. The language selection menu isexpanded to reflect the available languages.

The texts with the Siemens standard entries are stored on your PC/PG. Theyare to be found under the drive (<drive>) and directory (<path>) you selected, inthe following subdirectory:

’<drive>:\<path>\PROJ\TEXT\<LANGUAGE DIRECTORY>’.

Example:

If you select drive “C” and confirm the default directory path, the German alarmand message texts are to be found in directory

’C:\MMC100PJ.APP\PROJ\TEXT\D’.

Description

Preconditions

More than onelanguage

Alarm texts/message texts


8

07.2000


The letters used for <LANGUAGE DIRECTORY> have the following meanings:

Standard languages for MMC100/100.2:

D GermanG English

Further languages for MMC100/100.2 (available on language diskettes):

F FrenchI ItalianE SpanishF FinnishU HungarianKO KoreanN DutchP PortuguesePL PolishS SwedishX RussianZ CzechC Chinese (simplified)TW Chinese (standard)

The text file names start with ’A’ and end in the extension ’.TXT’:ALC.TXT Compile cycle alarm textsALM.TXT MMC alarm textsALMC.TXT Measuring cycle textsALN.TXT NCK alarm/message textsALNX.TXT NCK extended alarm textsALP.TXT PLC alarm/message textsALPU.TXT User PLC alarm/message textsALSC.TXT Standard cycle textsALUC.TXT User cycle alarm/message textsALZ.TXT Cycle alarm textsASY.TXT System error texts

The DOS editor EDIT must be used to edit the files.

User-specific alarm and message texts can be inserted into the text files ALPU.TXT and ALUC.TXT. The standard texts contained in the text files arehereby overwritten by user-specific texts. An ASCII editor, e.g. DOS editor,must be used for this purpose. New entries can be added to alarm text files.

Please refer to Section 8.3 for the applicable syntax rules.

The number and order of the alarm/message texts must be identical for the se-lected languages.

After the text contents have been modified, the text files must be converted andtransferred to the MMC (Section 12.2.2).

Language directory

Files

Editor

Conversion andtransmission


8

07.2000



8.2 Alarm text files for MMC 102/103

Files containing error texts are stored on the hard disk in the directoryC:\DH\MB.DIR\ . The error text files intended for use are activated in the fileMBDDE.INI.

To ensure that your personal settings are maintained after a future softwareupdate, you must store the user-specific configurations in directory C:\USER.

If there is no file MBDDE.INI in the directory C:\USER on the MMC102/103, itmust be copied from the directory C:\MMC2 as described below:

1. Switch to the DOS Shell via the operator control area

Start–up / MMC / DOS Shell

2. When the DOS prompt ”C:\MMC2>” appears, enter the following command:

C:\MMC2>COPY MBDDE.INI C:\USER and confirm with RETURN.

3. Enter EXIT and confirm once more with RETURN to return to the MMC inter-face.

The following block in the file MBDDE.INI integrates the alarm text files:

...[Textfiles]MMC=c:\dh\mb.dir\alm_NCK=c:\dh\mb.dir\aln_PLC=c:\dh\mb.dir\plc_ZYK=c:\dh\mb.dir\alc_CZYK=c:\dh\mb.dir\alz_UserMMC=UserNCK=UserPLC=c:\dh\mb.dir\myplc_UserZyk=UserCZyk=...

The standard alarm texts in ASCII format are stored in the following files in di-rectory C:\dh\mb.dir on the hard disk of the MMC102/103:

MMC ALM_xx.COMNCK ALN_xx.COM, ALNX_xx.COMPLC ALP_xx.COMCycles ALC_xx.COM, ALZ_xx.COM,

ALSC_xx.COM, ALMC_xx.COM

In these file names, “xx” stands for the code of the appropriate language. Thestandard files should not be changed by the user to store his own error texts.If these files are replaced by new ones when other software is loaded on theMMC102/103, then the added or modified user-specific alarms will be lost. Theuser should store his own alarm texts in user files.

Storage of textfiles

Configuration inMBDDE.INI

Standard files


8

07.2000


The user can replace the error texts stored in the standard files by his own textsor add new ones to them. To do so, he must load additional text files to directoryC:\DH\MB.DIR via the “Services” operating area. The directory and the names of the text files are set as parameters in the fileC:\USER\MBDDE.INI by means of an editor provided in the area Start–up /MMC. The editor is used to edit the file MBDDE.INI in the directory C:\USER.

Example:

Configuration of two additional user files (texts for PLC alarms, altered alarmtexts NCK) in file MBDDE.INI:

...User NCK = C:\DH\MB.DIR\MYNCK_User PLC = C:\DH\MB.DIR\MYPLC_...

The texts from the user files overwrite standard texts with the same alarmnumber. Alarm numbers which do not already exist in the standard texts areadded.

Note

The alarm/message texts of the selected languages must be defined for thesame numbers.

An ASCII editor must be used for editing (e.g. the DOS editor EDIT).

A language is assigned to the user alarm texts for the MMC102/103 by meansof the text file name. The appropriate code and the extension .COM are addedto the user file name entered in MBDDE.INI. The codes are assigned to thedifferent languages as follows:

Standard languages of the MMC102/103:

gr Germanuk English

Further languages for the MMC102/103 (available on language diskettes):

fr Frenchit Italiansp Spanishko Koreannl Dutchpl Polishpo Portuguesesw Swedishcz Czechhu Hungarian

Example:

myplc_gr.com File for German user PLC alarm textsmynck_uk.com File for English user NCK alarm texts

User files

Editor

Alarm textlanguages


8

07.2000



Note

The maximum length of an alarm text is 110 characters for a 2-line display.

Changes to alarm and message texts do not take effect until the MMC haspowered up again.

The languages English and German are implemented in the standard software.Further languages are available on language diskettes and can be installedseparately.

When you generate text files, make sure that the date and time of day on yourPC are set correctly or else your texts may not be displayed!

File with German user texts, PLC: C:\DH\MB.DIR\MYPLC_GR.COM:

700000 0 0 ”DB2.DBX180.0 gesetzt”700001 0 0 ”Schmierdruck fehlt”

A second text file with the language code for the selected background language(e.g. English) must contain texts for the same alarm numbers, e.g.:C:\DH\MB.DIR\MYPLC_UK.COM:

700000 0 0 ”DB2.DBX180.0 set”700001 0 0 ”missing lubricator pressure”

The parameter to be set in the file C:\USER\MBDDE.INI for this example is:

...User PLC = C:\DH\MB.DIR\MYPLC_...

Example for a useralarm text file


8

07.2000


8.3 Syntax for alarm text files of cycles and PLC alarms

The following alarm numbers are available for the cycle and PLC alarms:

Table 8-1 Alarm numbers for cycle and PLC alarms

No. range Designation Effect Eraseby

60000 – 60999 Cycle alarms Display, NC start disable Reset

61000 – 61999(Siemens)

Display, NC start disable,no motion

Reset

62000 – 62999 Display Cancel

63000 – 64999 Reserved

65000 – 65999 Cycle alarms Display, NC start disable Reset

66000 – 66999(user)

Display, NC start disable,no motion

Reset

67000 – 67999 Display Cancel

68000 – 69000 Reserved

510000 – 511315 PLC alarms for channel

600100 – 600815 PLC alarms for axis andspindle

700000 – 700063700100 – 700163�

702400 – 702463

PLC alarms for userUser area 0User area 1�

User area 24

PLC alarms are acknowledged by means of a key defined according to cus-tomer specification. In this case, a distinction is made only between alarms andmessages. Messages do not need to be acknowledged. There are no prioritiesbetween the groups, merely a chronological sequence. The difference betweenerror and operational messages is determined when the message is output viathe PLC.

Alarm numbers

Reset keys


8

07.2000



The text file for cycle and compile cycle alarms is structured as follows:

Table 8-2 Structure of text file for cycle alarm texts (example)

Alarm number Display Help ID Text or alarm number

60100 1 20 “No D number % 1 programmed”

60101 1 20 60100

... ... ... ...

65202 0 18 “Axis %2 in channel %1 ”

// Alarm text file for cycles in German

Alarm number: Alarm number

Display:

The alarm display mode is determined here:0: Display in the alarm line1: Display in a dialog box

Help ID: MMC 102/103

Text or alarm number:

The associated text is specified with the position parameters in inverted com-mas. The text must not otherwise contain any inverted commas. An existing textcan be used by means of a reference to the appropriate alarm text. The alarmtext file can include comment lines which must start with “//”. The alarm text maybe a total of 110 characters in length for a 2-line display. If the text is too long, itis cut off and marked with the “*” symbol.

Parameter “%1”: Channel numberParameter “%2”: Axis name

Format of text filefor cycle alarmtexts


8

07.2000


The ASCII file for PLC alarm texts has the following format:

Table 8-3 Structure of text file for PLC alarm texts (example)

Alarmno.

Display Help ID Text Text on MMC

510000 1 5 “Channel %K VSP disab.” Channel 1 VSP disab.

600124 1 78 “Feed disable axis %A” Feed disable axis 1

600224 1 78 600124 Feed disable axis 2

600324 1 78 600224 Feed disable axis 3

// Alarm text file for PLC alarms

Alarm number:

The alarm number consists of the event number (2 digits), signal group (2 digits)and the signal number (2 digits). These parameters are parts of a diagnosticelement of the CPU.


Event number Signal group Signal number

5x (for channels) 0–3 (disable)11–16 (GEO axes)21–28 (additional axes)

0–99

60 (for axis and spindle) 1–18 (axis no.) 0–99

70 (for user) 0–9 (user no.) 0–99

Display:

The alarm display mode is determined here:0: Display in the alarm line1: Display in a dialog box

Help ID: Index for HELP files, default setting “0”

Text or alarm number:

The associated text is specified with the position parameters in inverted com-mas. The text must not otherwise contain any inverted commas. An existing textcan be used by means of a reference to the appropriate alarm text. The alarmtext file can include comment lines which must start with “//”. The alarm text maybe a total of 110 characters in length for a 2-line display. If the text is too long, itis cut off and marked with the “*” symbol.

Parameter “%K”: Channel number (2nd digit of alarm number)Parameter “%A”: The parameter is replaced by the signal group number

(e.g. axis no., user area no., sequence cascade no.).Parameter “%N”: Signal number Parameter “%Z”: Status number

�

Format of text filefor PLC alarm texts


8

07.2000




9


Axis and Spindle Dry Run

9.1 Preconditions 9-178. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

9.2 Testing the axis 9-179. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

9.3 Testing the spindle 9-180. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

9

9

07.2000



9.1 Preconditions

To allow an axis to be traversed from the control system, it is necessary tosupply enabling terminals on the drive and to set enabling bits on the interface.

Enabling signals on drive

The FM-NC supplies the drive system with enabling commands via the driveinterface (X2). In addition to analog setpoints or clocking and direction pulses,the “Controller enable” or “Enable signal” (for stepper motor) are output on thisinterface (see Section 2.2 “Overview of Connections”).

Enabling via PLC interface

The following signals must be made available at the PLC interface for axis orspindle:

IS “Controller enable” (DB31 – 48, DBX2.1)IS “Pulse enable” (DB31 – 48, DBX21.7)IS “Position measuring system 1” (DB31 – 48, DBX1.5)

The following signals on the interface must not be set or else the axis/spindlemotion will be disabled:

IS “Feed/spindle override switch” (DB31 – 48, DBX0) not at 0% IS “Axis/spindle disable” (DB31 – 48, DBX1.3)IS “Distance to go/spindle reset” (DB31 – 48, DBX2.2)IS “Feed stop/spindle stop” (DB31 – 48, DBX4.3)IS “Traverse key disable” (DB31 – 48, DBX4.4)IS “Ramp-function generator disable”(DB31 – 48, DBX20.1)

References: /FB/, A2, “Various Interface Signals”

Setting of hardware limit switches and interface signal check:

� Hardware limit switch PLUSD B31 – 48.DBX12.1

� Hardware limit switch MINUSD B31 – 48.DBX12.0

Axis enabling

Limit switches

9.1 Preconditions

9

07.2000


9.2 Testing the axis

Disable axis (in HW and via PLC)

Specified path 10 mm

Enter machine data for NC

Select JOG mode and enable axis

Axis moving?

Check NC controller enabling signals at connector X2

Check interface signals (DB 31 – 34)DBX 0 Feed override switchDBX 1.7 Override activeDBX 1.4 Follow-up modeDBX 1.5 Position measuring system 1DBX 1.6 Position measuring system 2DBX 1.3 Axis disableDBX 2.2 Delete distance to goDBX 2.1 Controller enableDBX 8.7/8.6 Traversing keysDBX 8.3 Feed stop

Check machine dataMD 32000–32050 VelocitiesMD 36000–36620 Monitoring functionsMD 32110 Actual value sign

Axis check in Service Display menu

Check MD32100 FIX_MOTION_DIR

yes

no

Start up speed controller acc. to drivemanufacturer’s specifications

jaCheck MD31000 – MD31080 (encoder matching)

yes

noTravel direction OK?

Path evaluation OK? no

Interpret alarm and check machine datafor velocity adaptation

yes

Traverse with feedrate

Following error OK? CheckMD 32200 (KV factor)MD 32910 (dynamic response matching)MD 31050/31060 (load gearing)MD 32610 (feedforward control)MD for velocity adaptation

no

Rapid traverse

yes

no

Alarm?

End

Note

If further optimization measures are required, please refer to Section 10.

9.2 Testing the axis

9

07.2000



9.3 Testing the spindle

Check NC controller enabling signals (connector X2)

Check interface signals (DB 31 – 34)DBX0 Spindle overrideDBX1.7 Override activeDBX1.5/DBX1.6 Position measuring system 1/2DBX1.3 Axis/spindle disableDBX2.1 Controller enableDBX16.7 Delete S valueDBX3.6 Velocity/spindle speed limita-

tion and MD 35160DBX4.3 Feed stop/spindle stopDBX20.1 HLGSSDBX2.2 Spindle reset when MD 35050=1DBX21.7 Pulse enable

Check machine and setting dataMD 35100–35150 Spindle speed limitationMD 36200 AX_VELO_LIMITSD 60200JOG_SPIND_SET_VELOSD 60210SPIND_MAX_VELO_G26SD 60220SPIND_MIN_VELO_G25

Disable spindle (in HW andvia PLC)

Enter machine data for NCand setting data

Enable spindle(controller enable NC)

Change MD32100 AX_MOTION_DIR

Enter speed

Specified speed 100 rev/min

Check MD31000 – 31080 (encoder matching)

yes

noSpindle rotating?

yes

noRotation direction OK?

yes

yes

noActual speed OK?

noIS ”Spindle in setpoint range”

(DB31 – 34, DBX83.5)?

Check machine data and interface signalsMD 35110–35140 Speeds for gear stagesMD 35150 Spindle speed toleranceIS “Actual gear stage” (DB31–34, DBX16)IS “Select drive parameter set” (DB31–34, DBX21)IS “Setpoint gear stage” (DB31–34, DBX82)IS “Active drive parameter set (DB31–34, DBX93)

no

Change overgear stage

All gear stages tested?

yes

yes

Position spindle?

no

End

1yes


9

07.2000


Check machine dataMD 36000 Exact stop coarseMD 36010 Exact stop fineMD 32200 SG factorMD 35210 Acceleration in position control rangeMD 35300 Creep speedMD 35300 Encoder limit frequencyCheck encoder matchingCheck spindle synchronization

1

no

noAll gear stages

tested?

yes

yes

(Spindle positioning)

End

Position reached from highspeed and zero speed?

Change overgear stage

Note

If any further optimization measures are required, please following the instruc-tions in the relevant drive manufacturer documentation.

�


9

07.2000




10


Drive Optimization

10.1 General principles of optimization 10-184. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

10.2 Aim of optimization procedure 10-184. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

10.3 Checking the speed control loop 10-185. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

10

10

07.2000



10.1 General principles of optimization

These optimization instructions should be viewed as a recommendation. Theuser may find that he needs to modify the recommended procedure in order toallow for the marginal conditions of the application in question. These instruc-tions apply only to axes which are operated under position control (linear androtary feed axes, spindles operating temporarily under position control, robotaxes). In order to meet the generally high machining quality requirements, it isparticularly important to carefully optimize those axes which are directly involvedin workpiece machining.

In order to optimize the required axes, it is necessary to record the machineperformance in SYSTEM OPERATION. It is advisable to execute the requiredaxis motions in fixed or optional incremental dimensions using the axis directionkeys or by means of the NC program applying appropriate feedrates and tra-verse paths.

10.2 Aim of optimization procedure

The aim of the optimization procedure is to achieve overshoot-free positioningwith minimum ramp-up and braking times and to ensure that the axis motion isfree of vibration, particularly when the position control loop is in the steady state(both in rapid traverse mode and at low traversing velocities if applicable).

To achieve higher machining accuracy, those axes whose motion is directlyconnected with workpiece machining, can be mutually coordinated in terms ofresponse as described below after individual optimization:

� Enter lowest Kv factor value (32200 POSCTRL_GAIN) for all axes,

� Set the same dynamic response for all axes viaMD 32900: DYN_MATCH_ENABLEMD 32910: DYN_MATCH_TIME

References: /FB/, G2 “Velocities, Setpoint/Actual Value Systems, Closed-Loop Control”

Overview

Procedure

10.1 General principles of optimization

10

07.2000


10.3 Checking the speed control loop

The speed control loop must be started up under strictest observation of thedrive manufacturer’s specifications.

Once the speed control loop has been started up and you are ready to com-mence optimization, please check that

� all required machine data been entered,

� the drive does not move with a setpoint voltage of 0.000 V,

� the drive reaches the set rapid traverse velocity with a setpoint voltage of9.000 V (32010 JOG_VELO_RAPID),

� you know the transient reaction time constant and

� the axis moves smoothly at very low velocity setpoints.

The speed control loop response basically determines the quality of positioncontrol which can be achieved. It is therefore important to eliminate any obviousdeficiencies in the speed loop before proceding with further optimization mea-sures.

!Warning

Subsequent changes to the rapid traverse value or the 9 V assignment of thedrive actuator will alter the physical positional loop gain!

Satisfactory position loop optimization is generally achieved with the usual ve-locity control loop setting for a one-off, approximately 5 to 10 % overshoot with asetpoint step change from zero to rapid traverse and back. This response qual-ity should also be obtained with very small setpoint step changes (100 mV andsmaller in some cases).

�

Requirement

Optimization

Speed control loop

10.3 Checking the speed control loop

10

07.2000



11


Data Saving

11.1 General 11-188. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

11.2 Data saving via MMC 100/100.2 11-189. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

11.3 Data saving via MMC 102/103 11-193. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

11.4 Saving data on a PCMCIA memory card 11-194. . . . . . . . . . . . . . . . . . . . . . . .

11.5 Data saving from MMC 102/103 11-195. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.5.1 Data saving from MMC 102 11-195. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.5.2 Data saving from MMC 103 11-196. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

11.6 Line checksums and MD numbers in MD files 11-199. . . . . . . . . . . . . . . . . . . 11.6.1 Line checksums 11-199. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.6.2 Machine data numbers 11-200. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.6.3 Abortion of MD import 11-200. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

11.7 Notes on loading and saving machine data 11-202. . . . . . . . . . . . . . . . . . . . . .

11.8 Machine/setting data 11-204. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

11

11

07.2000



11.1 General

You should save your data

� after start-up,

� after changing machine-specific settings,

� during servicing (e.g. after replacing hardware, upgrading software) so thatyou can put the system back into operation as soon as possible and

� during start-up before altering the memory configuration to make sure thatno data are lost during start-up.

There are three types of data to be saved on the SINUMERIK FM-NC, i.e.

1. Saving data for FM-NC

2. Saving data for PLC-CPU (with STEP7)

3. Saving data for MMC when MMC 102/103 is installed

There are basically two methods of saving data, each of which has a specificpurpose.

1. Series start-up

Provision is made for the generation of so-called series start-up files. Theseallow a specific configuration to be transferred complete to other controlswith the same SW version that are, for example, operating on the samemachine type. This type of file cannot be modified externally using an ASCIIeditor. Series start-up files contain all relevant settings (except forcompensation data). They must be created for NCK and also for the MMC ifan MMC 102/103 is installed.

On the FM–NC, you can also store data (memory dump) on a PCMCIA me-mory card. The saved data can be retrieved in the same FM–NC (e.g. if datais lost) or into other FM–NCs.

2. Area-specific archiving

To ensure that archived data can be transferred to controls on which futureSW versions are installed or to other FM-NC controls, it is advisable to ar-chive data on an area-specific basis, i.e. each data area is stored in a sepa-rate file which can be edited later with an ASCII editor.

Data are read out or read back in again in several steps. Only in this waycan compensation data be saved.

MMC data are not divided up.

You will require the following accessories in order to save data:

� PC/PG with DOS 6.x or higher (e.g. PG 740)

� PCIN data transfer program for PC/PG

� V24 cable

References: /Z/, Catalog NC Z (Accessories)

When to save data

NCK/PLC/MMC

Series start-up/area-specificarchiving

Required accessories

11.1 General

11

07.2000


11.2 Data saving via MMC 100/100.2

These texts are parts of the operator panel system software. They must bereloaded after hardware component replacement or software upgrading. Themessages must be available in the correct format for this purpose (seeSection 12.2, Upgrading MMC 100/100.2 software). The texts cannot be readback.

(Data saving)

1. Connect programming device/PC to interface X6 on the MMC.

2. Select Services operating area on the MMC.

3. Select V24 PG/PC interface (vertical softkey)

4. Select Settings and check or enter the parameter settings of the V.24 inter-face. Default setting.

Device type: RTS/CTS

Baud rate: 9600 baud

Parity: None

Data bits: 8

Stop bits: 1

Character for XON: 11H(ex)

Character for XOFF: 13H(ex)

Format:

– Tape format, deselected for series start-up or for saving areas of drivedata

– Select tape format for saving areas of all other data.

Continue with Series start-up or Area-specific archiving.

Note

The PLC-CPU must always be started up before series start-up of the FM-NC.

(Data saving)

5. MMC interface configuration (see above, tape format deselected)

6. Start PCIN data transfer program (Data In) on PC/programming device.

7. Select Start-up data on MMC (MMC Services operating area, data outputData Out); NCK (FM-NC) and PLC (do not use for FM-NC) areas are dis-played after selection of the Input key.

8. First select NCK and start the read-out process (Start softkey).

Texts for errormessages,operationalmessages andcycle alarms

Sequence of operations

Series start-up


11

07.2000



5. MMC interface configuration (see above, select tape format).

6. Start PCIN data transfer program (Data In) on PC/programming device,specify file name for the archive.

7. Select data area to be output on MMC (MMC Services operating area, dataoutput Data Out).

8. Select the heading Data and then select the following areas in the ordergiven from the list that is then displayed:

– All

– Machine data

– Setting data

– Option data

– Global user data

– Tool and magazine data

– Protection zones

– R parameters

– Zero offsets

– Sag/angle compensation

– Quadrant error compensation

– Display machine data

– LEC/measuring system error compensation

When the areas are output, the internal area identifier used in each caseappears on the top line of the display.

9. Start the read-out process (Start softkey) and acknowledge any related in-put requests on the operator panel.

Recommendation

MD 11210 UPLOAD_MD_CHANGES_ONLY should be set to “1”. With thissetting, the transferred files contain only those data which deviate from thedefault. This is of advantage with respect to future SW upgrades.

Area-specificarchiving


11

07.2000


The NCK data are output in the following sequence and notation:

Table 11-1 NCK data

Designation in the archive file Meaning

_N_NC_OPT Options

_N_CFG_GLOBAL_INI Global memory and channel configuration

_N_CFG_SCALING_INI Scaling

@@_N_IBN_SS NCK Reset

_N_CFG_CHAN_INI Channel-specific memory configuration


/_N_DEF_DIR Macros (SMAC/MMAC/UMAC)

_N_INITIAL_INI (MD, R parameters, etc.)


/_N_BD_DIR Display machine data

/_N_MPF_DIR Global main programs

/_N_SPF_DIR Global subprograms

/_N_CUS_DIR User cycles

/_N_CST_DIR Standard cycles

/_N_WKS_DIR All workpieces with all files

Note

STEP7 must be used to save PLC_CPU area data.

References: /S7HT/ Manual

1. Set the protection level to Manufacturer (password SUNRISE).

2. Connect the programming device/PC to interface X6 on the MMC.

3. Select the Services operating area on the MMC. Continue with steps listedunder Reading in series start-up or Reading in area-specific archivedata.

4. Select the MMC interface configuration V24 PG/PC as above (tape formatdeselected).

5. Start the PCIN data transmission program on the programming device/PC.Select the NCK series start-up file to be read into control for transmissionunder Data Out . Select Data In in the Services area on the MMC and start data import byselecting the Start softkey. Acknowledge any input requests displayed on the MMC.

6. After another NCK reset, the control powers up with the imported data sets.

Sequence of NCKdata for seriesstart-up

Loading archivingdata

Reading in seriesstart-up files


11

07.2000



4. Select the MMC interface configuration V24 PG/PC as above and set tapeformat.

– Start the PCIN data transfer program on the programming device/PC.Select the archive file to be read into control for transmission under DataOut.

– Select Data In in the Services area on the MMC. Start data import byselecting the Start softkey. The file is automatically detected and loadedaccordingly.

5. Read in option data, initiate NCK reset.

6. Load the machine data file and actuate NCK reset. If you then receive mes-sages about a reconfiguration of the memory or restandardization of ma-chine data, then you must read in the machine data file again and reset thecontrol. Generally speaking, this process must be carried out two to threetimes.

7. If global user data must be activated, then the so-called N_INITIAL_INI file(Table 11-2) must be read out through selection of the setting All data as forarea-specific archiving.

8. Read in archive file for global user data.

9. Read the saved N_INITIAL_INI file back in to activate the global user data.

10. Then load the other areas.

Note

Check/correct the interface settings after display of a message regardingmemory reconfiguration.

If data transmission is aborted with an error message, check the following:

� Is the password at the correct protection level?

� Are the interface parameters (V24 PG/PC) correct?

� Has MD 32700, ENC_COMP_ENABLE been set to 0 before importing LECdata?

� Has MD11220 INI_FILE_MODE been set to 1 or 2?

Reading in area-specific archivedata

Transmission error


11

07.2000


Table 11-2 Data in _N_INITIAL_INI file

File _N_INITIAL_INI Data not contained in file _N_INITIAL_INI

� Option data

� Machine data

� Setting data

� Tool offsets

� Zero offsets

� Global user data

� Local user data

� R parameters

� Compensation data– Leadscrew error compensation– Quadrant error compensation– Sag compensation

� Display machine data

� Workpieces

� Global part programs

� Global subroutines

� User cycles

� Standard cycles

� Definitions and macros

11.3 Data saving via MMC 102/103

To archive or read in data, proceed in exactly the same way described inSection 11.2:

� Series start-up with selection possibility for areas

– NCK (complete)

– MMC (with option of saving only partial areas of the MMC data)

� Area-specific archiving Saving or re-importing individual data areas (Data In, Data Out and DataSelection softkeys)

You can divert data saving to archive files to the MMC102 hard disk.

When a diskette drive is connected to the MMC, it is possible to save or re-import data using diskettes.

Data are saved via the Services operating area.

References: /BA/, Operator’s Guide

Via V.24

Via MMC hard disk

Via diskette

11.3 Data saving via MMC 102/103

11

07.2000



11.4 Saving data on a PCMCIA memory card

The PCMCIA (JEIDA) memory card is a functional component of the SINUMERIK FM-NC and can be purchased together with the control or at alater date.

For data to be saved to a PCMCIA memory card, you need an FM-NC with sys-tem software 3.7 or higher and an 8 MB PCMCIA memory card.

1. Control in RESET state following normal power–up (start–up switch in position 0, program or motion not active)

2. Insert the PCMCIA memory card into the FM-NC

3. Set start-up switch on FM-NC to position 3

4. The LED “DIAG” flashes twice cyclically while the complete data of theFM-NC are being saved to the PCMCIA card

Note:

If an error occurs during data saving (memory dump) to the PCMCIA card,the LED “DIAG” flashes once cyclically.

5. Data saving is complete as soon as LED “DIAG” flashes three times cycli-cally. You can then turn the control off.

6. Remove the PCMCIA card from the FM-NC and turn the start–up switchback to position 0.

7. Turn FM-NC on. The FM-NC powers up in the normal operating state.

The saved data can be used for the following functions:

� For series start-up of an FM-NC

� For replacement of hardware on the FM-NC requiring the transfer of the soft-ware version and data from the defective FM-NC to a new FM-NC.

1. Insert PCMCIA memory card into control after control “OFF”

2. Start-up switch to position 6

3. Control “ON” system software and data are transferred from the PCMCIAmemory card to the control (see also Section 12.1 “Firmware update”)

LED “DIAG” flashes 4 times cyclically during data transfer

4. As soon LED “DIAG” flashes 5 times cyclically, data transfer is complete.You can now turn the control “OFF”

5. Remove PCMCIA memory card from the FM-NC

6. Start-up switch in position “0”

7. Turn the control “ON”. The control is booted with the system software andthe saved data from the PCMCIA memory card.

Overview

Data savingsequence

Use of data savedon PCMCIA

Importing saveddata from PCMCIA

11.4 Saving data on a PCMCIA memory card

11

07.2000


11.5 Data saving from MMC 102/103

With MMC102/103 it is possible to make backups on a connected VALITEKstreamer. These backups can be restored to the MMC102/103 at any time in thefuture. With MMC103 it is possible to create a backup on a hard disk (from version4.04).

11.5.1 Data saving from MMC 102

Proceed as follows to save data from MMC 102:

1. Hold key “6” pressed when switching on the MMC until the following mainmenu appears on the display.

Main menu

1. Install / Update MMC System

2. Install / Update Standard Software

3. DOS Shell

4. Start Windows (Service Mode)

5. MMC System Check

6. Reboot System (Warmboot)

7. Backup/Restore with VALITEK Streamer

8. Start PC Link

9. End (Load MMC)

2. Select ”7” (Backup/Restore with VALITEK Streamer) and you will be presented the following menu:

PLEASE SELECT :

1. Select VALITEK Streamer Type

2. Test Connection to Streamer

3. Backup System

4. Backup Userdata

5. Restore from Tape

6. Uninstall MMC102 (Delete Files)

7. Return to Main Menu

3. Select the streamer type you are using in submenu 1. You can test the con-nection to the streamer via submenu 2.

4. Select submenu 3 to copy the system data from the MMC102 to the streamer.Select submenu 4 to copy the user data from the MMC102 to the streamer.

Overview

Sequence for data saving fromMMC102 (backup)


11

07.2000



Proceed as follows to restore the data from the connected streamer to theMMC102:

1. Hold key “6” pressed when switching on the MMC until the following mainmenu appears on the display.

2. Select ”7” (Backup/Restore with VALITEK Streamer) and you will be presen-ted the following menu:

PLEASE SELECT :

1. Select VALITEK Streamer Type

2. Test Connection to Streamer

3. Backup System

4. Backup Userdata

5. Restore from Tape

6. Uninstall MMC102 (Delete Files)

7. Return to Main Menu

3. Select ”5” (Restore from Tape) to restore the data from the streamer to theMMC102.

11.5.2 Data saving from MMC 103

Proceed as follows to save data from MMC 103:

1. When the MMC powers up (after switching on the operator panel) press thekey 6 on the operator panel keyboard briefly while the message StartingMS DOS or Starting MS Windows 9x is displayed.

PLEASE SELECT:

1 Install/Update MMC System2 MMC Configuration Tool3 DOS Shell4 Start Windows (Service Mode)5 MMC System Check6 Reboot System (Warmboot)7 Backup/Restore8 Start PC-Link9 End (Load MMC)

Your Choice [1,2,3,4,5,6,7,8,9] ?

Fig. 11-1 Main menu MMC103

2. Select ”7” (Backup/Restore) to display the menu for data saving and datarestoring.

The system prompts you to enter a password with:

passwd:

Sequence to restore the data toMMC102

Sequence fordata saving fromMMC 103 (backup)


11

07.2000


3. Enter one of the passwords for levels 0 – 2.

– System

– Manufacturer

– Service

The following menu is displayed:

PLEASE SELECT:

1 Harddisk Backup / Restore with GHOST2 Backup / Restore with Valitek3 Uninstall MMC102 (Delete Files)4 Return to Main Menu

Your Choice [1,2,3,4] ?

Fig. 11-2 Backup/Restore menu MMC103

4. Select ”2” (Backup/Restore with Valitek) to save data on a Valitek streamer.

Select “1” in the submenu (Select Valitek Streamer Type) to set theValitek streamer you are using.

Select “3” (Backup System with Valitek Streamer) to save the systemdata.

Select “4” (Backup Userdata with Valitek Streamer) to save the userdata.

or (from version 4.04)

Select ”1” (Harddisk Backup/Restore with GHOST) to save data to a harddisk.

Select “1” in the submenu (Configure GHOST Parameter) to paramete-rize the connection and set the backup file.

Select “2” (Harddisk Backup to ...) to start data saving. Follow the in-structions displayed on the MMC103.

Proceed as follows to restore the data to the MMC103:

1. When the MMC powers up (after switching on the operator panel) press thekey 6 on the operator panel keyboard briefly while the message StartingMS DOS or Starting MS Windows 9x is displayed.

Sequence to restore the data toMMC103


11

07.2000



PLEASE SELECT:

1 Install/Update MMC System2 MMC Configuration Tool3 DOS Shell4 Start Windows (Service Mode)5 MMC System Check6 Reboot System (Warmboot)7 Backup/Restore8 Start PC-Link9 End (Load MMC)

Your Choice [1,2,3,4,5,6,7,8,9] ?

Fig. 11-3 Main menu MMC103

2. Select ”7” (Backup/Restore) to display the menu for data saving and datarestoring.

The system prompts you to enter a password with:

passwd:


– System

– Manufacturer

– Service


PLEASE SELECT:

1 Harddisk Backup / Restore with GHOST2 Backup / Restore with Valitek3 Uninstall MMC102 (Delete Files)4 Return to Main Menu

Your Choice [1,2,3,4] ?

Fig. 11-4 Backup/Restore menu MMC103

Select “1” in the submenu (Select Valitek Streamer Type) to set theValitek streamer you are using.

Select ”5” (Restore from Valitek Tape) to restore the data from thestreamer to the MMC103.

or (from version 4.04)

4. Select ”1” (Harddisk Backup/Restore with GHOST) to restore the data froma hard disk.

Select “1” in the submenu (Configure GHOST Parameter) to paramete-rize the connection and to set the path to the backup file.

Select ”3” (Harddisk Restore from ...) to restore the data to the MMC103 from the set hard–disk path.


11

07.2000


11.6 Line checksums and MD numbers in MD files

A check facility has been created through the introduction of line checksums toback-up files for machine data (INI and TEA files). By saving the filesthemselves, it is possible to dispense with the “Manufacturer” write authorizationwhen these backed-up files are read in again.

The purpose of introducing machine data numbers (MD numbers) in theback-up files is to facilitate the communication of machine data values forservicing purposes and automatic processing of MD back-up files in somecases.

The following two subsections describe line checksums and machine datanumbers in detail.

11.6.1 Line checksums

� A line checksum is generated only for lines with machine data assignments.

� Machine data numbers generated at the same time on request (MD 11230bit 1 = 1) are included in the line checksum.

� The line checksum is positioned immediately after the machine dataassignment preceded by a blank space and apostrophe.

� The checksum consists of 4 HEXA characters.

� The line checksum is only ever generated by the control on creation of anMD back-up file and not by external editors on PC or programming device.

� The generation of line checksums is preset (MD11230 Bit 0 = 1), but can bedeselected (MD11230 Bit 0 = 0) in individual cases.

� “;<Comment>” can be added later to lines with checksums without affectingthe sum check.

Example of a line with checksum:

$MC_AXCONF_MACHAX_USED[0]=1 ’2F34

No write authorization is required to read in machine data files with valid linechecksums.

To load

� machine data without line checksum,

� modified MD values with deleted line checksum and

� MD files from SW version 1 or 2,

it is necessary to have the “Manufacturer” write authorization.

When loading machine data files, the user can select how the system shouldrespond to errors in the machine data file. See 11.6.3 Abortion of MD import.

If the file contains incorrect values, then the current values are neveroverwritten.

Overview

Properties of linechecksums

Evaluation of linechecksums


11

07.2000



11.6.2 Machine data numbers

� Machine data numbers are positioned as block numbers (e.g. N20070) infront of an MD assignment line.

� There is a blank between the machine data number and MD assignment.

� The MD number refers to the machine data in total. Any existing field valuesare not represented in the MD number.

� It is possible to select/deselect the generation of MD numbers in front of MDassignment lines in INI and TEA files.

– MD 11230 bit 1 = 1 Generate MD number

– MD 11230 bit 1 = 0 Do not generate MD number.

When machine data files are read back in, the control evaluates the MDnumbers as follows:

If errors are found in MD files during import, then the MD number is displayed asa block number with the appropriate alarm.

11.6.3 Abortion of MD import

If, during the import of machine data files (INI files) to controls, files are read in

� which contain errors

� which do not match the checksum,

then alarms are generated and the import process aborted in some cases. It ispossible to select the following control reactions to errors by setting machinedata MD 11220 appropriately:

MD 11220 value Reaction to errors

0 Output of an alarm, abortion on detection of 1st error (as inSW versions 1 and 2).

1 Output of an alarm, continuation of file import, output ofnumber of errors at file end by means of alarm

2 Import process continues to end of file even if errors aredetected. Output of number of errors at file end by meansof alarm.

In all cases where at least one error is detected in the MD file, the name of theaffected file is output by means of alarm 15180.

Archive files

Evaluation of MDnumbers

Control reactions


11

07.2000


Other reactions:

� MD containing errors do not overwrite current MD.

� The current MD are not overwritten when an attempt is made to load MDwith no line checksums without adequate write authorization.

� CHANDATA instructions for non-existent channels (MD for multiple channelconfiguration are not set) cause import process to be aborted.

� Invalid file end causes import process to be aborted.

MD 11220 INI_FILE_MODE must be reset explicitly. An earlier setting is notaccepted in the course of series start-up.

� Import machine data and output alarms generated on import.

� % character here stands for file name or number of errors.

� MD 11220 = 1, i.e. output of an alarm for every error, continuation ofprocessing, output of number of errors at end of file by means of an alarm.

MD file Alarms

CHANDATA(1)

$MC_AXCONF_GEOX_NAME_TAB[0]=“X”

$MC_AXCONF_GEOX_NAME_TAB[1]=“Y”

15180 Program % cannot be processedas INI file

$MC_AXCONF_GEOX_NAME_TAB[99]=“A” 17020 Illegal array index 1

$MC_MM_REORG_LOG_FILE_MEM=1000 17090 Value greater than upper limit

$MC_AXCONF_GEOX_NAME_TAB=“X” 12400 Element does not exist

$MC_MM_REORG_LOG_FILE_MEM[1]=100 12400 Element does not exist

$MN_UNKNOWN_MD=1 12550 Name % not defined

M17

15185 % Error detected in INI file

MD 11220

Example


11

07.2000



11.7 Notes on loading and saving machine data

Machine data also include data which define how machine data are scaled withrespect to their physical unit (e.g. velocities).

These “scaling” data are as follows:

� MD 10220: SCALING_USER_DEF_MASK (activation of scaling factors)

� MD 10230: SCALING_FACTORS_USER_DEF (scaling factors of physical quantities)

� MD 10240: SCALING_SYSTEM_IS_METRIC (basic system metric)

� MD 10250: SCALING_VALUE_INCH (conversion factor for switchover to INCH system)

� MD 30300: IS_ROT_AX (rotary axis)

When machine data are loaded (via MMC, V.24 interface, program), they arescaled according to the physical unit which is currently valid. If this data set con-tains a new scale (e.g. rotary axis declaration), those machine data which aredependent upon scaling data are converted to the new scale after the next“Power ON”. The MD do not then contain the expected values (e.g. rotary axistraverses at very low F values).

Example:

The control has been started up with default values. The 4th axis is defined as arotary axis in the MD file to be loaded and contains the following machine data:

$MA_IS_ROT_AX[A1] = 1 (rotary axis)$MA_MAX_AX_VELO [A1] = 1000 [rev/min] (maximum axis velocity)

When the MD set is loaded the velocity is interpreted with respect to a linearaxis (default setting $MA_IS_ROT_AX[A1]=0) and normalized according to thelinear velocity. During the next Power ON process, the control detects that thisaxis is defined as a rotary axis and normalizes the velocity with reference torev/min. The value in the machine data is then no longer “1000”, but“2.77777778” (1000/360). If the MD file is loaded again, the axis is already de-fined as a rotary axis and the velocity is interpreted as the rotary axis velocity.The MD then contains the value “1000” that is interpreted in rev/min by the con-trol system.

Suggestions for step-by-step loading of machine data

1. Change the machine data concerned manually via the MMC (MD 10220,10230, 10240, 12050, 30300) and then initiate an NCK power-up. Import theMD set via the V.24 interface and then initiate another NCK power-up.

2. Generate an MD set with the scaling machine data (MD 10220, 10230,10240, 10250, 30300). Load this MD set and initiate an NCK power-up.Read in the complete MD set and then initiate another NCK power-up.

3. As an alternative to the methods above, an MD set can also be loaded twice(via V.24 interface) with an NCK power-up operation after each loading.

Loading of scalingmachine data


11

07.2000


Note

If a scaling MD is altered, then the control outputs alarm “4070 Scaling datachanged”.

When machine and setting data are saved, MD 11210:UPLOAD_MD_CHANGES_ONLY can be set to define whether all data or onlythose data which deviate from the defaults are to be output via the V.24interface.

UPLOAD_MD_CHANGES_ONLY = 1 Output only those data which deviate from the defaults.

UPLOAD_MD_CHANGES_ONLY = 0 Output all data.

If a value has been changed in a data which is stored as an array, then thecomplete MD array is always output (e.g. MD 10000:AXCONF_MACHAX_NAME_TAB).

Note

If may be useful to perform a data saving operation in which only alteredmachine data are saved prior to upgrading software in cases where thedefaults in the new software are not the same as those in the earlier version.This applies particularly to machine data which are assigned SIEMENSprotection level 0.

Standard machine data can be loaded in a number of different ways.

Note

With methods 1 and 2, the entire SRAM on the NCU module is re-initialized. Alluser data are also erased. Save your user data first, if necessary.

� Method 1 � Start–up switch of MMC user interface (SW switch)

Select Start-up/NC/Start-up switch. The menu Start-up FM–NC is dis-played. Use softkey Start–up mode to select Power–up with defaultvalues (start-up). Start the power–up with standard machine data byselecting softkey OK. After the FM–NC has powered up again, themessage “4060 Standard MD have been loaded” is displayed.

Any password setting is deleted.

� Method 2 � Start-up switch on FM-NC (HW switch)

Switch position 1 and subsequent NCK RESET or POWER ON startsFM-NC power–up with standard machine data.

Any password setting is deleted.

Saving alteredvalues

Loading of standard data


11

07.2000



� Method 3 � MD 11200: INIT_MD

(Load standard MD on “next” power-up)

Certain input values in MD: INIT_MD allow various data areas to be loadedwith default values on the next NCK power-up. The machine data is dis-played in HEX format. After MD:INIT_MD has been set, POWER ON or NCKRESET must be initiated.

After the FM–NC has powered up again, the message “4060 Standard MDhave been loaded” is displayed and MD 11200 INIT_MD is set to the value“0”.

Any password setting remains valid.

Meaning of input values of MD11200

Value “0”

On the next power-up, no MD are overwritten with the default settings. (Thestored machine data remain valid.)

Value “1” (bit 0 set)

All MDs which are not memory-configuring data will be overwritten with defaultvalues during the next power-up operation.

Value “2” (bit 1 set)

All memory-configuring MDs will be overwritten with default values during thenext power-up operation.

Memory-configuring MDs are:

� MD 10010: ASSIGN_CHAN_TO_MODE_GROUP

� All machine data starting with “MM_” or following MDs

– MD 18000 – 18999 (general MDs)

– MD 28000 – 28999 (channel-specific MDs)

– MD 38000 – 38999 (axis-specific MDs)

Value “3” (bits 0 and 1 set)

All MDs will be overwritten with default values during the next power-up operation.

Value “4” (not for FM–NC)

11.8 Machine/setting data

The machine/setting data are listed in References: /LIS/ Lists

�


12


Software/Hardware Replacement

12.1 Upgrading FM-NC software (firmware update) 12-206. . . . . . . . . . . . . . . . . . . 12.1.1 Procedure for updating firmware on FM-NC 12-206. . . . . . . . . . . . . . . . . . . . . 12.1.2 Procedure for updating firmware on FM354 12-207. . . . . . . . . . . . . . . . . . . . .

12.2 Upgrading MMC 100/100.2 software 12-208. . . . . . . . . . . . . . . . . . . . . . . . . . . 12.2.1 Installation of MMC 100/100.2 system diskette(s) 12-210. . . . . . . . . . . . . . . . 12.2.2 Installation of MMC100/100.2 application diskette 12-216. . . . . . . . . . . . . . . . 12.2.3 Installation of MMC 100.2 software via PCMCIA 12-221. . . . . . . . . . . . . . . . .

12.3 Upgrading MMC 102/103 software 12-225. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12.3.1 Installation via MMC 102/103 floppy drive 12-225. . . . . . . . . . . . . . . . . . . . . . . 12.3.2 Installation via PC/PG to MMC102/103 12-226. . . . . . . . . . . . . . . . . . . . . . . . .

12.4 Hardware replacement 12-230. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12.4.1 Special notes for CPU318 12-230. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12.4.2 CPU hardware replacement 12-233. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12.4.3 FM-NC hardware replacement 12-233. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

12.5 Battery replacement 12-234. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

12

12

07.2000



12.1 Upgrading FM-NC software (firmware update)

The following are required to replace the FM-NC and FM 354 system software:

� for FM-NC:A memory card (PCMCIA) with the new software version

� for FM354:a diskette with the system software, including the file README.TXT, aPC/PG with MPI interface, with WINDOWS95 and STEP7 from version 3.1

A change of system SW in the FM-NC and FM 354 may by required for the fol-lowing reasons:

� A new, different system SW (new SW version) may be required.

� After replacement of an FM hardware component, it may be necessary toload the currently valid system SW into the new hardware (to maintain theSW version of the FM component). This point applies only if the new hard-ware has been ordered with the wrong system SW.

12.1.1 Procedure for updating firmware on FM-NC

When the software is updated from the PCMCIA memory card, the system SWof the FM-NC (NCK and COM) is automatically loaded. The system SW soft-ware on an FM 354 remains unaffected (i.e. it is not updated from the PCMCIAcard).

Note

Before updating the firmware, it is essential to create a back-up of all data andall SW programs which are not part of the system SW (see Section 11).

Proceed as follows:

1. Switch the control “OFF”

2. Turn start-up switch on the FM-NC to position 6

3. Switch the control “ON”. The control switches into update state. The LED“DIAG” on the FM-NC flashes cyclically four times in this state.

4. The control then switches into the state update complete. The LED “DIAG”signals this state by flashing cyclically five times.You can switch the control “OFF” as soon as the firmware update is com-plete.

Note:

In configurations that include more than one FM-NC, the control must not beswitched off after updating of the firmware until the all the other FM-NCshave also completed the updating of their firmware.

Requirements

Changing system SW

FM-NC firmwareupdate

Procedure for up-date from PCMCIA


12

07.2000


5. Turn the start-up switch on the FM-NC to position 0 and switch the control“ON”.The FM-NC is booted with default values after a firmware update.

6. Where appropriate, any saved data and programs can now be restored tothe FM-NC.

12.1.2 Procedure for updating firmware on FM354

Read the file README.TXT on the update diskette before starting the firmwareupdate. Proceed as follows to perform the update:

1. If SDB>=1000 are present in the control, perform a general reset without amemory card inserted.

2. Switch the CPU into the state ”STOP” and connect the PG/PC via the freeMPI interface.

3. Set the MPI time-out on your PC/PG to 100s. Note down the previously settime-out so that it can be restored later.The setting is made, for example, via: ”Control panels” / ”Set PG/PC inter-face” / ”MPI interface” / ”Properties” / ”Time Out”

4. Start the update by entering A:\FMUPDATE.EXE under ”START” / ”Run”.You can modify the update language before activating ”Start data processing”.

5. In the following dialog, enter the ”MPI address of FM354” (<=14) and se-lect ”Switch FM into update state”. The FM signals its update readinessthrough cyclic flashing of the red LED ”SF”.

6. Set the value 14 under ”MPI address of FM354”. (Refer also to the file README.TXT on the update diskette)

7. Start the update process by clicking on ”Start data transfer to FM”. Theprogress of the update is indivated as follows:

– Deletion: LED ”DIAG” lights

– Programming: LED ”DIAG” flashes 4 times cyclically

– Update completed: LED ”DIAG” flashes 5 times cyclically

An automatic RESET is effected on the FM354 once the update process iscompleted.

8. Repeat steps 5. to 7. if the firmware update is to be performed for furtherFM354s in the system. If there are no further axis expansion modules requi-ring firmware to be loaded, you can close the dialog box on the PG/PC.

9. Where appropriate, you must perform another general reset of the CPU witha memory card inserted. Switch the CPU and FM354 off and back on againto enable them to boot together.

10. Restore the original MPI time-out on the PC/PG (see Step 3.).

FM354firmware update


12

07.2000



12.2 Upgrading MMC 100/100.2 software

The MMC 100/100.2 software is supplied on two or three 3.5” diskettes. Theircontents are as follows:

1. System diskette (MMC100) or two system diskettes (MMC100.2)

– Boot software

– System software

– User software

2. Application diskette

– Alarm text files in 2 standard languages

– Configuration files for MMC 100/100.2 MD

– Configuration file for several operator panels

By loading the system diskette(s), you will obtain a functional standard MMCsystem for the foreground language English and the background language Ger-man. The alarm text and message files contain only Siemens texts.

After loading the application diskette, you are able to

� adapt and extend alarm text files

� select one or two other languages to those previously available after loadingdiskette 1/2 (there are no more than 2 languages on the MMC 100/100.2 atany time; other languages besides the standard languages are available onlanguage diskettes).

� make special MMC MD settings

� adapt configuration parameters for several operator panels

� transfer user-defined screenforms for PLC status to the MMC.

Details of how to use the two diskettes are given below. Rules about adaptingfiles before transferring them to the MMC100/100.2 can be found in Section11.2 “Data saving via MMC 100/100.2”.

How is softwaresupplied?

System diskette(s)

Application diskette


12

07.2000


The system software on the MMC 100/100.2 is divided into the following areas:

� Boot software

� System software

� User software

The MMC software is stored on FEPROMs. The boot software area containssoftware components which are required for system software booting as well asthe software which permits the system software to be loaded in the case of anew software version. All files required for MMC operation are contained in thesystem software. Languages other than English and German can be retro-installed. The user software area contains all system texts, message texts forthe PLC-CPU and cycle alarm texts.

Note

The boot software area also contains software components which are requiredfor a software exchange. If these components are missing or incapable of run-ning (e.g. after power failure during upgrading), then a new software versioncan be installed only at the appropriate Siemens works.

In order to upgrade the system software (software version) of the MMC, a boot-strap status must be established in the MMC. A PC/PG from which the new sys-tem software can be loaded is also required. Directories occupying approxi-mately 3 MB are set up on the PC/PG hard disk. The data which are selectedfor transfer during installation are stored in these directories.

System softwareareas


12

07.2000



12.2.1 Installation of MMC 100/100.2 system diskette(s)

See also SYS_READ.TXT on the system diskette.

� PC/PG with MS-DOS 6.x or later

� MMC and PC/PG are connected via a V.24 (zero modem) cable.

� The compression software ARJ.EXE must be available.

� At least 3 MB free space is available on the hard disk of the PC/PG.

The software and associated files supplied on diskette are prepared for use onthe MMC 100/100.2 by means of file SYS_INST.EXE (runs under DOS) and thePC/programming device. They are then transferred to the MMC.

The user can select the areas to be loaded.

The software installation procedure is menu-assisted. The following sequenceof operations is recommended for installation:

1. Save control-specific data via the MMC V24 interface.

2. Switch off MMC.

3. Connect the defined serial interface of the PC with the MMC interface (MMCinterface: X6).

4. On the MMC100, press key “6”, switch on the operator panel and holddown key “6” until a display with “PCIN” appears on the display.On the MMC100.2, press key “6” during booting as soon as the serial num-ber is displayed. If a PCMCIA memory card is inserted in the MMC100.2during booting, a menu box appears in which you select 1 Update withPC–IN (COM1:). The MMC is now ready to receive data via the V24 inter-face.

PCIN VERSION MMCIN 1.1 (c) SIEMENS AG 1994 COM1: 19200 , NONE,8,1 XON/XOFF

V24 INI DATA_IN DATA_OUT EXIT

PCINLight

VERSION MMCIN System Upload 1.1Copyright (c) SIEMENS AG 1994

Fig. 12-1 Display on MMC 100 when bootstrapping state is reached

Note

Preconditions

Functions ofSYS_INST.EXE

Installation procedure


12

07.2000


5. Go into DOS command mode (Windows not active) on your PC/PG.

Insert the system diskette (on MMC100.2 system diskette 1) into thePC/PG disk drive and switch over to disk drive (e.g. with A: Return).

Call program “SYS_INST.EXE” on the diskette.

(A:\SYS_INST.EXE and start by pressing Return)

The following menu appears:

System installation MMC100(.2)

< 1 > = Install system disk on hard disk

< 2 > = Install system disk on hard disk & on MMC-hardware

< 3 > = Select optional files to install

< ESC > = Quit program!

Please make your choice < F1 > – Help

Fig. 12-2 PC screen after SYS_INST.EXE has been called

1 Install the system diskette on the hard disk of your PC/PGby selecting 1.

2 Install the system diskette on the hard disk of your PC/PG and on the hardware of the MMC 100 by selecting 2.

3 Choose the files to be installed on the MMC 100 by selecting 3.

ESC Abort the installation process and end the program by pressing ESC.

6. Now select 3.


Select files to install

< 1 > = VGABIO28.EXE NO

< 2 > = SYSBIO31.EXE NO

< 3 > = ROMDOS30.BIN NO

< 4 > = MMCIN_27.EXE NO

< ESC > = Return to main menu!

Fig. 12-3 Files to be selected for MMC 100


12

07.2000




Select files for installation

< 1 > = ROMDOS_2.BIN NO

< ESC > = Return to main menu!

Fig. 12-4 Files to be selected for MMC 100.2

Mark all the files by selecting the corresponding numbers to switch between“NO” (deselected) and “YES” (selected).

7. Return to the main menu by pressing ESC (see Fig. 12-2)

8. Now select 2.

Copyright (c) Siemens AG 1996,1997, all rights reserved Installation kit version 04.04

Install system disk on hard disk

Select drive for installation

Drive :

ESC F1 RETURN

Fig. 12-5 Selection of drive

9. Select the drive on which you wish to install the system diskette contents.Continue by pressing Return.


12

07.2000




Select path for installation

Path :C:\MMC100PJ.SYS

ESC F1 RETURN

Fig. 12-6 Selection of path

10. Select the path to which you wish to unpack the files. The files are copied to the specified drive and unpacked. Any hard disk or network drive with write authorization can be selected. The following path is set up as standard, whereby <drive> stands for theselected drive (e.g. C:\):

<drive>:\MMC100PJ.SYS

Note:

The directory must not already exist and/or contain files. You may alter thepath specified by the system.

The installation data are installed under the drive and path you enter.

Continue by pressing Return.

Transfer software to hardware MMC100

Selected COM port : COM1


< 1 > = Install software via serial line

< 2 > = select COM port


Fig. 12-7 Selection of interface on MMC100


12

07.2000



Transfer software to hardware MMC100.2




< 2 > = Create Flash Memory Card image

< 3 > = Select COM port


Fig. 12-8 Selection of interface on MMC100.2

11. Select 2 (MMC100) or 3 (MMC100.2) to specify the serial interface of thePC/PG through which MMC and PC/PG are linked.

12. Press ESC to quit this submenu.

13. Select 1 to install the software on the MMC.The communications software PCIN transfers to software to the MMC.

Note

If on the MMC100 the VGA-BIOS is upgraded together with other booting soft-ware parts, then the software is transferred to the MMC100 in 2 steps.

The following steps are only relevant for the MMC100.

Step 1 involves the transferring of the VGA-BIOS. A reboot is then effected automatically on the MMC100 and you receive the following message on thePC/PG:

ANNOUNCEMENT

Transfer of VGA-BIOS succesfully completedPlease reboot your MMC100 and press 6 on MMC100 to restart PCIN!Press RETURN on PC/PG if MMC100-PCIN is ready for receiving data!

RETURN

Fig. 12-9 Data transfer to MMC100 - Step 2

14. Hold the key “6” pressed while the MMC is booting until a screen with PCINappears on the display. If the MMC user interface is displayed, trigger thebooting of the MMC100 again and hold the key 6 on the MMC100 presseduntil a screen with PCIN appears on the display.

15. Continue with the data transfer at the PC/PG by pressing RETURN.Step 2 transfers the remaining selected software areas. When the transfer iscomplete, the MMC100 reboots.


12

07.2000


If data transmission cannot be started from the PC, then an error message isoutput.

– Are cables connected correctly?

– Is correct interface selected?

– Is there a hardware defect?

16. The upgrading of the software is not completed. The saved operator paneldata can now be loaded again if necessary.

Note

When the software on other MMC 100/100.2 devices is updated, the updatecan be started from the drive of your PC/PG with “SYS_INST.EXE”. You will findSYS_INST.EXE in the path specified under point 10 under directory INSTUTIL.


12

07.2000



12.2.2 Installation of MMC100/100.2 application diskette

See also APP_READ.TXT on application diskette.

� PC/PG with MS-DOS 6.x or later.

� PC/PG and MMC are connected with a V.24 (zero modem) cable.

� The boot and system software for MMC100/100.2 must already have beenloaded (see Sections 12.2.1 and 12.2.3).

� The compression software ARJ.EXE must be available.

� At least 3 MB of free space is needed on the PC/PG hard disk.

The software and associated files supplied on diskette are prepared for use onthe MMC100/100.2 using file APP_INST.EXE (runs under DOS) and a PC/PG.They are then transferred to the MMC.

The user can make specific adjustments if necessary:

� Selection of languages to be loaded

� Modification of alarm texts, message texts, etc. to special requirements

� Adjustment of operator panel parameters

� Adjustment of configuration parameters for several operator panels andNCUs.

� User-defined screenforms for PLC status display on MMC100/100.2

If only the user software with the two standard languages German and Englishis to be loaded without any other modifications, then proceed as follows:

Perform the steps in the order in which they are listed below. Some messagetexts and submenus have been simplified.

1. Save the control-specific data via the V.24 interface of the MMC.

2. The MMC is disconnected from the power supply.

3. Connect the defined serial interface of the PC/PG to the interface of theMMC (X6).

4. On the MMC100, press key “6”, switch on the operator panel and holddown key “6” until a display with “PCIN” appears on the display.On the MMC100.2, press key “6” during booting as soon as the serial num-ber is displayed. If a PCMCIA memory card is inserted in the MMC100.2during booting, a menu box appears in which you select 1 Update withPC–IN (COM1:). The MMC is now ready to receive data via the V24 interface.

Note

Preconditions

Functions ofAPP_INST.EXE

Installationwithoutmodifications


12

07.2000


PCIN VERSION MMCIN 1.1 (c) SIEMENS AG 1994 COM1: 19200 , NONE,8,1 XON/XOFF

V24 INI DATA_IN DATA_OUT EXIT

PCINLight

VERSION MMCIN System Upload 1.1Copyright (c) SIEMENS AG 1994

Fig. 12-10 Display on MMC when bootstrapping state is reached

5. Go into DOS command mode (Windows not active) on your PC/program-ming device.

Insert the application diskette into the PC disk drive and switch over tothis drive (e.g. with A: Return).

Call program “APP_INST.EXE” on the diskette(e.g. APP_INST.EXE Return)

The following menu appears:


Install applikation disk on hard disk

Select drive for installation

Drive :

ESC F1 RETURN

Fig. 12-11 PC screen after APP_INST.EXE has been called, selection of drive

6. Select the drive on which you wish to install the application diskettecontents. Continue by pressing Return.


12

07.2000





Select path for installation

Path :C:\MMC100PJ.SYS

ESC F1 RETURN

Fig. 12-12 Selection of path

7. Select the path to which you wish to unpack the files. The files are copied to the specified drive and unpacked. Any hard disk or network drive with write authorization can be selected. The following path is set up as standard:

<drive>:\MMC100PJ.APP

<drive> here stands for the selected drive (e.g. C:)

Note:

The data are installed under the drive and path you enter. If files alreadyexist under the specified path, you are asked whether these files are to bedeleted. It is also possible to specify a different destination directory.

Continue by pressing RETURN.

Install application on hardware MMC100(.2)

First language : English Second language : German


< 1 > = Install all modules on hardware

< 2 > = Modify configuration

< ESC > = Esc to quit!

Fig. 12-13 Setting the configuration

1 Start installing data by selecting 1.

2 Choose your applications (see Installation with modifications) by selecting 2.

ESC Abort the installation and end the program by pressing ESC.


12

07.2000


8. Now select 1. The files to be installed are displayed.

Transfer software to hardware MMC100






Fig. 12-14 Selection of interface with MMC100

Transfer software to hardware MMC100.2




< 2 > = Create Flash Memory Card image



Fig. 12-15 Selection of interface with MMC100.2

9. Select 2 (MMC100) or 3 (MMC100.2) to select the serial interface of the PC/PG through which the MMC and PC/PG are linked. Press ESC to return tothe above screen.

10. Now select 1. The installation process is started.

If data transmission cannot be started from the PC, then an error message isoutput.

– Are cables connected correctly?

– Is correct interface selected?

– Is there a hardware defect?

11. As soon as the PC has signalled that all data have been loaded, the MMC isrebooted. The software is now upgraded and the control system should befully operational again.

12. The saved operator panel data can now be loaded again if necessary.


12

07.2000



Proceed as in the case of an installation without modifications up to point 7.

8. Now select point 2 as shown in Fig. 12-13.

Changing applications:

Install application on hardware MMC100

First language : English Second language : German


< 1 > = Change first language< 2 > = Change second language< 3 > = Edit ASCII files < 4 > = Edit text files for first language< 5 > = Edit text files for second language< ESC > = Return to previous menu!

Fig. 12-16 Setting the configuration

1 Select 1 to change the setting for the first language.

2 Select 2 to change the setting for the second language.

3 Select 3 to make the modifications you require (see APP_READ_TXT).

4 Select 4 to edit the language files for the set first language

5 Select 5 to edit the language files for the set second language.

ESC Select ESC to quit the submenu (see Fig. 12-13)

Next step: See Installation without modifications, points 10. to 12.

Installation withmodifications


12

07.2000


12.2.3 Installation of MMC 100.2 software via PCMCIA

� PC/PG with MS-DOS 6.x or later and WINDOWS

� Flash burner

� 4 MB flash memory card (PCMCIA)

� Software SINUCOPY V01.03.05 or later

� Two system diskettes and one application diskette for MMC100.2

When installing MMC100.2 software via PCMCIA, proceed at first as describedin Section 12.2.1 under ”Installation procedure”, steps 1. to 10. If you wish to load the standard configuration without specific modifications,proceed as described under ”Installation via PCMCIA without modifications”.If you wish to make individual changes, proceed as described under ”Installa-tion mit PCMCIA with modifications” .

If you wish to load the standard configuration without specific modifications,proceed as follows:

13. In the screen shown in Fig. 12-8, select 2 (Create Flash Memory Cardimage).

Copyright (c) Siemens AG 1996,1997, all rights reserved

Installation kit version 04.04

Please wait!

Select drive for copying the Flash Memory Card image

Drive :

ESC F1 RETURN

Fig. 12-17 Selection of drive for flash memory card image

14. Select the drive to which the flash memory card image (file MMC100_2.ABB) is to be copied. Continue by pressing Return

Preconditions

Installation viaPCMCIA forMMC100.2

Installation viaPCMCIA withoutmodifications


12

07.2000





Please wait!

Select path for copying the Flash Memory Card image

Path :C:\

ESC F1 RETURN

Fig. 12-18 Selection of path for flash memory card image

15. Select the path under which the image file is to be saved. The fileMMC100_2.ABB will be copied to the specified path. The default setting isthe root directory of the selected drive (e.g. C:\). Continue by pressing ReturnA message is displayed to confirm that the image file has been created suc-cessfully and to indicate the path under which MMC100_2.ABB has beensaved. Continue by pressing Return

16. End the program SYS_INST.EXE by pressing ESC.

17. Start the software SINUCOPY and write the flash memory card imageMMC100_2.ABB to the PCMCIA.

18. Continue with the steps described under “Procedure for software update viaPCMCIA” later in this Section.

If you wish to load the standard configuration with individual modifications, proceed as follows:

1. End the program in the screen shown in Fig. 12-8 by pressing ESC.

2. Perform the following steps as described in Section 12.2.2:

– Steps 5. to 7. under ”Installation without modifications” and

– Step 8. under ”Installation with modifications“.

3. In the screen shown in Fig. 12-15, select 2 (”Create Flash Memory Card image”).

4. The system data which are already stored on the hard disk are required tocreate the memory card image. In the following screens you must specifythe drive and path under which the system files have been stored. If you used the default settings for the intermediate saving, the entries will be”C” for the drive and ”MMC100.SYS” for the path.

Installation viaPCMCIA withmodifications


12

07.2000




A running system needs systemdisk-data! Therefore:

Please enter drive for copying the Flash Memory Card image

Drive :

ESC F1 RETURN

Fig. 12-19 Specifying the drive for system files

Enter the drive on which the MMC100.2 system files are to be found andconfirm your entry by pressing RETURN.



A running system needs systemdisk-data! Therefore:

Please enter Pfad for copying the Flash Memory Card image

Drive :C:\

ESC F1 RETURN

Fig. 12-20 Specifying the path for system files

5. Enter the path under which the system files have been stored and confirmyour entry by pressing RETURN.



Please wait!

Select drive for copying the Flash Memory Card image

Drive :

ESC F1 RETURN

Fig. 12-21 Selecting the drive for the flash memory card image

6. Select the drive on which the flash memory card image (fileMMC100_2.ABB) is to be saved and confirm your entry with RETURN.


12

07.2000





Please wait!

Select path for copying the Flash Memory Card image

Path :

ESC F1 RETURN

Fig. 12-22 Selecting the path for the flash memory card image

7. The next screen requests that you enter the path for the image file. The fileMMC100_2.ABB will be copied to the specified path. The default setting isthe root directory of the selected drive (e.g. C:\). Continue by pressing RETURN.

8. A message is displayed to confirm that the image file has been created suc-cessfully and to indicate the path under which MMC100_2.ABB has beensaved. Confirm by pressing RETURN.

9. End the program APP_INST.EXE by pressing ESC.

10. Start the software SINUCOPY and write the flash memory card imageMMC100_2.ABB to the PCMCIA.

11. Continue with the steps described under “Procedure for software update viaPCMCIA” later in this Section.

The PCMCIA memory card containing the memory image ”MMC100_2.ABB”can be used to transfer the software to any number of MMCs. To do so, proceedas follows:

1. Insert the PCMCIA with the flash memory card image into the memory cardslot of the MMC100.2.

2. Reboot the MMC100.2 and press the key ”6” on the operator panel as soonas the serial number appears on the display. If a memory card is inserted atthis point, a menu box is displayed.

3. Select ”Update from PC-Card” by pressing the key ”0” on the operatorpanel.The update process takes approximately 1 minute. When the updating iscomplete, you will be prompted to”Remove PC-Card”

4. Remove the memory card from the MMC100.2.The MMC100.2 is rebooted automatically.The installation of the system software is now complete.

The same PCMCIA memory card can be used to transfer the system softwareto further MMC100.2 modules. In this case repeat steps 1. to 4. as often as ne-cessary.

Procedure for software updatevia PCMCIA


12

07.2000


12.3 Upgrading MMC 102/103 software

12.3.1 Installation via MMC 102/103 floppy drive

During MMC booting (after control has been switched on), while the messageStarting MS DOS or Starting MS Windows 9x is displayed:

1. Press key 6 on the operator panel keyboard just once and briefly.


PLEASE SELECT:

1 Install/Update MMC System2 Install/Update Standard Software3 DOS Shell4 Start Windows (Service Mode)5 MMC System Check6 Reboot System (Warmboot)7 Backup/Restore with VALITEK Streamer8 Start PC-Link9 End (Load MMC)

Your Choice [1,2,3,4,5,6,7,8,9] ?

Fig. 12-23 Main menu MMC102(/103)

2. Press key 1.

The system requests you to enter a password with:

passwd:


– System

– Manufacturer

– Service


PLEASE SELECT MEDIUM:

1 Install from Floppy Disk2 Install via Serial/Parallel Line3 Install from VALITEK Streamer4 Return to Main Menu5 Reboot

Your Choice [1,2,3,4,5] ?

Fig. 12-24 Submenu1 MMC102(/103)

4. Press key 1.

Operator action


12

07.2000



The system requests you to insert the first diskette with the message:

Please insert Installation Floppy #1(Hit ”n” to ABORT Installation)

Continue[y]

5. Insert the diskette and press Y if you want to continue with the installation.

– Installation is menu-assisted.

– The data are initially put into a clipboard.

– After successful transfer to the clipboard, the SETUP menu is offered.

– When you confirm CONTINUE, the data are transferred to the destina-tion directory.

– A booting of the MMC is then initiated.

12.3.2 Installation via PC/PG to MMC102/103

1. Establish a parallel or serial (V24) connection between PC/PG and MMC.

2. Insert installation diskette 1 in PC/PG.

3. Switch over to the disk drive (e.g. A: RETURN)

4. Start the installation program DOSSETUP at the command line

The installation start screen is displayed on the PC/PG. This screen in-cludes a warning that any user data will be overwritten by the installation. Atthe same time it offers two methods to proceed with installation:

You have two Choices:

1. Install directly from Floppy to MMC 10x (Single Installation)(Only some batchfiles will be copied to the selected Diskdrive)

2. Install once to local Harddisk and then multiple to MMC 10x(You will need about xx MB free space on your harddisk!)

Continue with installation (y/n)? [y] _

Fig. 12-25 Start screen of installation program (excerpt)

You can later choose one of two installation methods:

1. Load directly from floppy of PC/PG to MMC102/103

2. Load once to hard disk of PC/PG and transfer later to one orseveral MMC102/103 modules

Operator actionson PC/PG


12

07.2000


Once you have saved the user data of the control system if requested to do soby a message text, you can continue with “Y”.

5. The system now displays the default settings for

– the disk drive on the PC/PG

– method 1 or 2 and

– the directory.

Please check the installation parameters:

Installation from drive : A:Copy files to disk : NCopy (batch) files to directory : C:\MMC102

Would you like to change anything (y/n)? [n].

Fig. 12-26 Installation parameters

Note

Copy files to disk: N means direct loading from FD of PC/PG to MMC102 (method 1, single installation)

Copy files to disk: Y means load data once to hard disk of PC/PG (method 2, multiple installation)

The type of connection between PC/PG and MMC is recognized automaticallyby the communications software and does not need to be set.

If you select y to be able to enter changes, these changes will be requestedone by one. You are then returned to the screen shown in Fig. 12-26. If thedefault settings are correct for your system, or if you have made all thechanges you require, press n.

6. Switch PC/PG to “Server” mode (press “Y” key).

End PC/PG server mode by pressing Alt + F4 once all data have beentransferred.


12

07.2000



During MMC booting (after control has been switched on), while the messageStarting MS DOS or Starting MS Windows 9x is displayed:

1. Press key 6 on the operator panel keyboard once and briefly.


PLEASE SELECT:

1 Install/Update MMC System2 Install/Update Standard Software3 DOS Shell4 Start Windows (Service Mode)5 MMC System Check6 Reboot System (Warmboot)7 Backup/Restore with VALITEK Streamer8 Start PC-Link9 End (Load MMC)

Your Choice [1,2,3,4,5,6,7,8,9] ?

Fig. 12-27 Main menu MMC102(/103)

2. Press key 1

The system request you to enter a password with:

passwd:


– System

– Manufacturer

– Service


PLEASE SELECT MEDIUM:

1 Install from Floppy Disk2 Install via Serial/Parallel Line3 Install from VALITEK Streamer4 Return to Main Menu5 Reboot

Your Choice [1,2,3,4,5] ?

Fig. 12-28 Submenu 1 MMC102(/103)

4. Press key 2 (Install via Serial/Parallel Line)

– The installation is menu-assisted.

– The data are initially put into a clipboard.

– After successful transfer to the clipboard, the SETUP menu is offered.

– When you confirm CONTINUE, the data are transferred to the destina-tion directory.

– A booting of the MMC is then initiated.

Operator actionson MMC 102


12

07.2000


If you have chosen method 2 as described above and have copied files fromthe floppy disk to the hard disk of the PC/PG, proceed as follows to transferthem on to the MMC102/103:

1. Establish a parallel or serial connection between PC/PG and MMC.

2. Change to the directory which you specified under “Copy (batch) files todirectory:...” in the screen shown in Fig. 12-26 (e.g. C:\MMC102)

3. Call:

C:\MMC102\INSTALL2.BAT

4. Take the action described above under “Operator action on MMC102”.

Transfer of SWfrom PC/PG harddisk to MMC


12

07.2000



12.4 Hardware replacement

You can replace all components that are ordered via an MLFB (order number).

All data must be saved before any component is removed (see Section 11).

12.4.1 Special notes for CPU318

When replacing or using a CPU318 for the first time, attention must be given tothe changes described below.

� SIMATIC STEP7 from V5.x is required to be able to use CPU318.

Global data are exchanged between the CPU and MCP with the system datablock SDB210. The previously supplied SDB210 (Toolbox up to V03/06) is notsupported by the CPU318. The standard MPI address 6 cannot be used for theMCP in conjunction with the CPU318.

� CPU318 is able to use SDB210 from the project GDCOPU318 on the Toolbox diskette 1 from V03/07 (see also file PLCFMNCD.TXT on Toolboxdiskette 1).To be able to use this SDB210 the MPI address 14 must be set as follows atthe DIP switch of the MCP:

Table 12-1 Setting of switch S3 on the MCP

1 2 3 4 5 6 7 8 Meaning:

on off on on on on off off Baud rate: 187.5 kBaudTransmission cycle time: 100 msBus address: 14

� With the global data communication in STEP7 it is possible to create a user–specific SDB210 independently of the above-mentioned SDB210. In thiscase you can define individually selected transmit, receive and status datatogether with a free MPI address, except address 6. (see Section 3.3: ”Nonstandard configuration”)

Overview

Special require-ment of CPU318

Global data forMCP and CPU318


12

07.2000


When using a CPU318, the connection between MMC and FM-NC is via theCPU318. The FM-NC is addressed by the CPU by means of a rack-slot ad-dress. This address must be specified in the configuration file NETNAMES.INIof the MMC.

The rack-slot addresses are defined as follows:

Table 12-2 Rack-slot addresses

Rack slot addresses:

Slot 4 Slot 5 Slot 6 Slot 7 Slot 8 Slot 9 Slot 10 Slot 11

Rack 0 4 5 6 7 8 9 10 11

Rack 1 36 37 38 39 40 41 42 43

Rack 2 68 69 70 71 72 73 74 75

Rack 3 100 101 102 103 104 105 106 107

The valid rack-slot address is derived from the subrack and slot at which theFM-NC is installed. This address can be taken from Table 12-2 and must beentered into the configuration file NETNAMES.INI.

The procedure for modification of the configuration file NETNAMES.INI is de-pendent on the MMC hardware you are using.

� MMC100/100.2

The configuration is modified using the application diskette on the PC/PG and subsequently transferred to the MMC100/100.2.

Proceed as described in Section 12.2.2 under ”Installation with modifications”.

– In the submenu ”Modify configuration” (Fig. 12-16) select for example<3> ”Edit ASCIIfiles”.

– In the next menu select <1> ”Edit MPI configuration data”. The configuration file NETNAMES.INI is opened with the DOS editorEDIT.

– Modify the block [param NCU_1] in accordance with your requirementsand save your modifications with the menu command ”File/Save”. Anexample for the configuration of the file NETNAMES.INI for use of anFM-NC with CPU318 is enclosed below as orientation.

– Quit the editor (menu ”File/Quit”). When you have made all the neces-sary modifications, transfer the application to the MMC100/100.2 as des-cribed in Section 12.2.2.

Connecting FM-NCand MMC viaCPU318

Modification ofNETNAMES.INI


12

07.2000



� MMC102/103

The configuration is modified by means of a DOS editor at the MMC.

– Select the operator area ”Start–up/MMC/DOS Shell”.

– Copy the configuration file into the user directory by entering the following command line at the DOS prompt ”C:\MMC2>”:C:\MMC2>COPY NETNAMES.INI C:\USER.

– Then select EXIT to return to the MMC user interface.

Note

The user-specific settings in the file NETNAMES.INI should be made under theUSER path. The configuration files under the USER path take priority over thestandard configuration files. The configuration file with the same name underthe path MMC2 remains unaltered.

– Select the operator area and command ”Start–up/MMC/Editor”.

– Then select the path C:\USER, find the configuration file NETNAMES.INIand open the file for editing.

– Modify the block ”[param NCU_1]” in accordance with your require-ments. An example for the configuration of the file NETNAMES.INI foruse of an FM-NC with CPU318 is enclosed below as orientation.

– Quit the editor by selecting the softkey ”Close Editor”.

– The modified parameters do not become effective until the next time theMMC102/103 is booted. Initiate rebooting of the MMC.

Example:

An FM-NC is installed at the eighth slot (Slot 8) on the first subrack (Rack 0).

The rack-slot address 8 is to be taken from Table 12-2 and specified as a para-meter in the block [param NCU_1] of the file NETNAMES.INI:

::[param NCU_1]nck_adress =2, rack_slot =8plc_adress =2name =NCU_1::


12

07.2000


12.4.2 CPU hardware replacement

Data saving for the CPU is done with SIMATIC STEP7. If the CPU hardware is replaced, the basic program and the user program mustbe loaded into the new CPU hardware.

12.4.3 FM-NC hardware replacement

The FM-NC (NCU 570) can only be replaced as a complete unit. The data saved beforehand can be loaded into the new FM-NC.

� The procedure for data saving via the MMC is described in Sections 11.2and 11.3.

� The data of the FM-NC to be replaced can also be saved without externaldevices (PG/PC) by saving to a PCMCIA memory card. The saved data canthen simply be reloaded after replacement of the FM-NC hardware (seeSection 11.4 ”Saving data on a PCMCIA memory card”).

References: /PHF/, Manual “Configuring, Manual NCU 570 and FM 354”

/BH/, Manual “Operator Components”

Transferring data to new CPU hardware

Transferring data to new FM-NC hardware


12

07.2000



12.5 Battery replacement

!CautionYou should never attempt to revitalize dead batteries through heat or any othertreatment. The batteries must not be charged as this could cause them to leakor explode.

Failure to observe this warning could lead to physical injury or propertydamage.

There are SRAMs and timers backed up by batteries in the PLC-CPU, FM-NC andMMC 102. Data are saved to these in the event of power failure. The back-up volt-age is monitored by the control and a monitoring signal output. Once the monitoringfunction has responded, the battery must be replaced within 6 weeks.

References: /S/H/, Manual “Design of an S7-300”

/BH/, Manual “Operator Components”

When does the battery need to be replaced?

The battery must be replaced when an error message indicating a battery prob-lem is output. In addition, the LED “BAF” indicates the status of the battery volt-age and the buffered memory.

The battery does not require any maintenance for at least two years. It may notneed to be replaced for five or more years depending on its condition.

However, since the battery becomes less and less effective with increasing age,we would recommend that it is replaced after five years at the latest.

� LED “BAF” flashes

The buffered data are still safe, but the battery is beginning to lose itscharge. It must be replaced.

� LED “BAF” lights up steadily

The buffered data are lost and the control must be started up again afterreplacement of the battery. This state is forced by the FM-NC.

!Important

The load current supply must always be connected while a battery is replacedor else the buffered data (if any is still present) will be lost.

Proceed as follows to replace the battery

1. Lift up the left-hand front door.

2. Remove the dead battery, pulling the battery connector out of the socket inthe battery compartment.

3. Insert the battery connector into the socket in the battery compartment. Thenotch on the connector must point towards the right, or alternatively the lugmust point towards the left and positive pole downwards).

4. Insert the battery in the battery compartment, close the front door.

Battery type

Only preassembled batteries with plug-in connector may be used.

Order No.: 6ES7–971–1AA00–0AA0

�

Replacement ofbattery on FM-NC

12.5 Battery replacement

13


Miscellaneous

13.1 “Tool Box” software package 13-236. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13.1.1 Contents of tool box 13-236. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13.1.2 Application of tool box 13-237. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

13.2 Assessing machine data via part program 13-238. . . . . . . . . . . . . . . . . . . . . . .

13.3 O & M for FM-NC with OP 27 13-239. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

13

13

07.2000



13.1 “Tool Box” software package

13.1.1 Contents of tool box

Supplied on two 3.5” diskettes with

1st diskette:

– Basic PLC program for FM-NC

– Standard machine data sets for FM-NC

– Sample project file OP 27

– Info file SIEMENSD.TXT

2nd diskette:

NC variable selector

The following programs are required to be able to use the Tool Box softwarepackage� PCIN software program

� SIMATIC STEP7 for creation of the PLC user program and for integration ofthe PLC basic program

� COROS ProTool, V1.31 or higher for configuration of the Operator PanelOP27

The following components are required for the connections to a control system

� PC/programmer with MPI interface, e.g. PG740

� Cable for the connection between PG/PC and MMC (V24)

� Cable for the connection between PG/PC aqnd PLC (MPI)

References: /Z/, Catalog NC Z

Contents

Softwarerequirements

Hardware requirements


13

07.2000


13.1.2 Application of tool box

The default settings for the MD are not specific to any particular technology. Toprovide assistance in starting up machines for the first time, three example MDfiles are supplied on the 1st tool box diskette with the FM-NC. The purpose ofthese files is to assist the user in setting the machine data for specific technolo-gies when starting up machines for the first time.

� md_fr_a.tea Example of MD setting for 4-axis milling machine with localP bus (FM 354)

� md_dr_a.tea Example of MD setting for turning machine with analogdrive

� md_dr_s.tea Example of MD setting for turning machine with steppermotor drive

Please refer to the “readme” file: readme.txt supplied with the tool box for fur-ther information.

See SIMATIC STEP7, User Manual

References: /FB/, P3 “Basic PLC Program”

You need the NC variable selector to be able to read and write the NCK vari-ables from the PLC-CPU or from the OP 27.

References: /FB/, P3 “Basic PLC Program”

/LIS/, Lists, Section “Variables”

Standard MD sets

Basic PLCprogram

NC variableselector


13

07.2000



13.2 Assessing machine data via part program

The machine data designation is displayed on the MMC. The internaldesignation of the data requires further identifiers which must be specified whena machine data is altered via programming measures or imported via the serialinterface.

$MM_ Operator panel data$MN_/$SN_ General machine data/setting data$MC_/$SC_ Channel-specific machine data/setting data$MA_/$SA_ Axis-specific machine data/setting data$MD_ Drive machine dataPlease note: $ System variable

M Machine dataS Setting dataM, N, C, A Subarea (second letter)

Axis data are addressed via the axis name. The internal axis designation (AX1,AX2 ... AX5) or the name specified in MD 10000: AXCONF_NAME_TAB can beused as the axis name.

E.g.: $MA_JOG_VELO[Y1] = 2000The JOG velocity of axis Y1 is 2000 mm/min.

The contents of a machine data must be inserted in apostrophes (e.g. ’X1’ or’H41’) if they are a STRING (e.g. X1) or a hexadecimal value (e.g. H41).

E.g.: $MN_SCALING_USER_DEF_MASK = ‘H200’Activation of the scaling factor position control loop gain in 1/s.

In order to address various contents of a machine data, entries in square paren-theses are required.E.g.: MD FIX_POINT_POS [0,X1] = 500.000

Axis X1 is 500The 1st fixed-point positionof (0 = 1st, 1 = 2nd, 2 = 3rd etc.)

Examples:

$MN_AUXFU_GROUP_SPEC[2] = ‘H41‘Output instant of auxiliary functions of 3rd auxiliary function group.

$MN_AXCONF_MACHAX_NAME_TAB[0] = ‘X1‘Name of 1st machine axis is X1.

$MA_REF_SET_POS[0,AX1] = 100.000001st reference point value of axis X1 is 100 mm.

Assignment of channel-specific machine data:CHANDATA(1) Assignment channel 1$MC_CHAN_NAME=‘CHAN1‘ Channel name for channel 1$MC__AXCONF_GEOAX_NAME_TAB[1]=‘Y‘ Name of 2nd geometry axis

in channel 1 is Y...R10 = 33.75 R10 of channel 1

Data identifiers

Data areas

13.2 Assessing machine data via part program

13

07.2000


13.3 O & M for FM-NC with OP 27

A data server function is integrated in the FM-NC to allow the connection of de-vices (e.g. OP 27) that operate with the S7 protocol. Owing to differences in theaddress structure of variables and data formats used in the BTSS or S7 proto-cols, there are restrictions regarding the number of addressable variables andthe useful value range. The OPs use only the variable services (read/write vari-ables). The Domain and PI services of the BTSS protocol are thus omitted. FileOP27_NCx.PDB on the 1st diskette in the tool box contains a sample configu-ration for an OP 27 with respect to FM-NC variables.

In addition to FM-NC variables, you can also configure the variables of otherMPI nodes in OP 27 displays.

Note

This Section deals only with special features that are relevant with respect tooperation and monitoring (O & I) of the FM-NC using the OP 27. It is assumedthat the reader is already familiar with the ProTool configuring tool, the hard-ware connections and the documentation regarding the basic functions of theOP 27.

References: /ST7/, Catalog ST70

References for OP 27 operation

� COROS ProTool, User Manual

� COROS OP 25, OP 27, OP 35, OP45 Operator Panel, Product Manual

� COROS ProTool Application Example, Installation and Start-Up Guide

The sample configuration can be found in file OP27_NCx.PDB on the 1st dis-kette in the SW tool box.

The file can be opened in configuring tool COROS ProTool.

ProTool allows you to view, modify and extend this sample configuration. Youcan generate the modified/unmodified sample project in ProTool and then trans-fer it to the OP 27.

In this sample, all variables are configured with respect to an FM-NC (control_1)with MPI address 3. In the sample, the OP 27 has MPI address 10 (see Section3.5).

Display ks_25_1 in the sample shows the configuring data for the following vari-ables in an FM-NC system:

� Channel status (variable name: chanStatus)

� Active mode (variable name: opMode)

� Axis names of 1st to 4th axes (variable name: name, name1, ...)

� Axis actual values of 1st to 4th axes (variable name: actProPos, ...)

� Dimensional unit of 1st to 4th axes (variable name: extUnit, extUnit1, ...)

� etc.

Overview

Configuring an OP 27 for FM-NCvariables


13

07.2000



For a full list of FM-NC variables, please refer to

References: /LIS/, Lists, Section “Variables”

This document can only be used as an overview of the variables. The followingvariables are not supported by the FM-NC data server:

� Compile cycle Block CC

� Interpolative compensation Block type IK

� Status data Interrupt_Status Block type SINT

� Machine data Block type M

� Setting data ov areas V and H of Block type S

Variables that are not set up until the program is running (e.g. address in ACCfile) or that have an address that may change during program execution (e.g.GUD) cannot be addressed directly.

There are two methods by which you can determine the necessary configuringdata of FM-NC variables:

Method 1

You can acquire the configuring parameters of the variables by using the “Vari-able selector NC-VAR selector” tool. You will find it on the 2nd diskette of theSW tool box (self-extracting file: *.EXE).

To determine the configuring parameters of variables using the NC-VARselector, please proceed as follows:

1. Using an editor, set the key Konv = ProTool in the profile file NC_VAR.INI(stored in user directory of NC-VAR selector).

e.g.: �

; Specify conversion (Konv) either with S7 or ProTool; Konv = S7 Konv = ProTool�

If variables must be selected for the S7 interface (e.g. for PLC-CPU), thenKonv = S7 must be set.

2. Start the NC VAR selector (double-click on icon)

3. New project or Open existing project

You can either create a new project or open and modify a project that al-ready exists.

4. Select total list

Select the total list of variables for the FM-NC (NCU 570) with the appropri-ate software version for NCU570:

e.g.: ...\nc_var\data\swx_xx.570

Select this file by a double-click.

The file: nc_var.mdb is displayed.

Select this as well by a double-click.

The full list of variables is displayed.

Variable selection


13

07.2000


5. You can select the appropriate variables from this list. The variable name istransferred to the project list when it is double-clicked. The transfer is initi-ated via the intermediate display Input line, column and area number inwhich you can also specify supplementary information about the variable(e.g. axis number, number of R parameter, field number, etc.).

6. Once you have transferred all the variables to be configured to the projectlist or have modified or extended and existing list, you can store it.

If you have called a new project, then it must be saved under path extension*.s7d.

e.g.: ...\opvar_v1.s7d\op27_v1.var

7. Go into menu Code and call the Generate function. This function generatesboth the *.var file and the *.p25 ASCII file (e.g. op27_v1.P25). A typical ex-ample of how this ASCII file may appear on the screen is given below:

//Ran Type Variable Format Li Ci DBNr DBOffset Remark

//// File : C:\VARSTEST.S7A\VARSTEST.S7P\VARSTEST.S7D\OP27_V1.P25

// Source File : C:\VARSTEST.S7A\VARSTEST.S7P\VARSTEST.S7D\OP27_V1.VAR// Generation Date : xx-xxxx-xx Time: xx : xx//

//

A[1] SE TEMP_COMP_SLOPE A1_SE_TEMP_C REAL 1 43910 24854 1934A[2] SE WORKAREA_MINUS_ENABLE A3_SE_WA_MIN BYTE 1 43410 25366 1434// END TABLE

8. Close NC-VAR selector.

9. Using an ASCII editor, you can view and printout the *.p25 file.

The *.p25 file contains all the configuring parameters of the selected variablessuch as format, DB no., and DB offset that may be needed for configuration withProTool.

Method 2

The docu file read_op.doc can be found on the 1st diskette in the SW tool box.

This file contains the following:

� Instructions on how to determine the DB no. and DB offset for a variable tobe configured.

� Notes on data formats and supplementary conditions

� A description of how specific workpiece programs can be selected via theOP 27

� A list of configurable variables (Appendix A1)

�


13

07.2000




A

A-243 Siemens AG 2000 All Rights ReservedSINUMERIK FM-NC Installation and Start–Up Guide (IAF) – 07.2000 Edition

Abbreviations

Automation System

American Standard Code for Information Interchange

Asynchronous Subroutine

Advanced Technology

BCD Binary Coded Decimals

BP Basic Program

C1 Channel 1

C BUS Communications Bus

COM Communication

CPU Central Processing Unit

CRC Cutter Radius Compensation

CTS Clear To Send (serial data interfaces)

DAC Digital–to–Analog Converter

DB Data Block

DBB Data Block Byte

DBX Data Block Bit

DCE Data Communications Equipment

DP Distributed Peripherals

DPR Dual–Port RAM

DRAM Dynamic storage (RAM)

DRF Differential Resolver Function

AS

ASCII

ASSR

AT

A

A

07.2000

A-244 Siemens AG 2000 All Rights Reserved


DRY Dry Run

DSR Data Send Ready (serial data interfaces)

DTE Data Terminal Equipment

DW Data Word

EPROM Erasable Programmable Read Only Memory

ESM Electrostatic–Sensitive Modules

ETC ETC key > Extension of softkey selection in the same menu

FC Function Call (function block in PLC)

FDD Feed Drive

FEPROM Flash–EPROM

FIFO First In First Out: Memory which operates without address specification from which data are read in the same order as they were stored.

FIPO Fine Interpolator

FM Function Module

GEO Geometry

GND Signal ground

GR Gear Ratio

GUD Global User Data

HEX Abbreviation for hexadecimal digit

HW limit switch Hardware limit switch

IM Interface Module (SIMATIC S7–300)

IMR Interface Module Receive

IMS Interface Module Send

INC Increment

INI Initializing Data

INTM Internal Multiplication

A. Abbreviations

A

07.2000


INTSIG Interface Signal

ISO code Special tape code, no. of holes per character is always even

JOG Jogging

LEC Leadscrew Error Compensation

LED Light Emitting Diode

MCP Machine Control Panel

MD Machine Data

MDA Manual Data Automatic

MG Mode Group

MMC Man Machine Communication: SINUMERIK operator interface

MPF Main Program File: NC part program

MPI Multi–Port–Interface

MSD Main Spindle Drive

NC Numerical Control

NCK Numerical Control Kernel (with block conditioning, traversing range, etc.)

NCU Numerical Control Unit

NMI Non–maskable Interrupt

OB Organization Block in PLC

OM Operating Mode

OP Operator Panel

OPINT Operator Panel Interface

P BUS Peripherals Bus

PCMCIA Personal Computer Memory Card International Association

PII Process Input Image

PIO Process Output Image

PG Programming device

A. Abbreviations

A

07.2000



PLC Programmable Logic Controller

PMS1 Position Measuring System 1

PMS2 Position Measuring System 2

PRT Program Test

QEC Quadrant Error Compensation

RAM Random Access Memory

RDY Ready

ROV Rapid Override

RPA R–Parameter Active

RTS Request To Send (serial data interfaces)

SBL Single Block

SD Setting Data

SEA Setting Data Active

SG Servo Gain factor

SK Softkey

SKP Skip

SM SIMATIC S7–300 signal module, e.g. input/output modules

SPF Sub Program File

SRAM Static storage (RAM)

SSI Synchronous Serial Interface

SW Software

SW limit switch Software limit switch

TC Tool Change

TEA Testing Data Active

TL Tool

TLRO Tool Radius Offset

A. Abbreviations

A

07.2000


TO Tool Offset

TOA Tool Offset Active

VDI Virtual Device Interface

V24 Serial interface (equivalent to RS232C)

ZO Zero Offset

ZOA Zero Offset Active

�

A. Abbreviations

A

07.2000



A. Abbreviations

B-249 Siemens AG 2000 All Rights ReservedSINUMERIK FM-NC Installation and Start–Up Guide (IAF) – 07.2000 Edition

References

General Documentation

SINUMERIK 840D/840Di/810D/802S, C, DOrdering Information Catalog NC 60Order No.: E86060-K4460-A101-A8-7600

SIMATICSIMATIC S7 Programmable Logic ControllersCatalog ST 70Order No.: E86 060-K4670-A111-A3

SINUMERIK, SIROTEC, SIMODRIVEAccessories and Equipment for Special-Purpose MachinesCatalog NC ZOrder No.: E86060-K4490-A001-A7-7600

Electronic Documentation

The SINUMERIK System (09.01 Edition)DOC ON CD (includes all SINUMERIK 840D/840Di/810D/FM-NC and SIMODRIVE publications)Order No.: 6FC5 298-6CA00-0BG1

/BU/

/ST7/

/Z/

/CD6/

B

07.2000

B-250 Siemens AG 2000 All Rights Reserved


User Documentation

SINUMERIK 840D/810D/FM-NCAutoTurn Graphic Programming System (07.99 Edition)Part 2: SetupOrder No.: 6FC5 298-4AA50-0BP2

SINUMERIK 840D/810D/ FM-NCShort Guide AutoTurn Operation (07.99 Edition)Order No.: 6FC5 298-4AA30-0BP2

SINUMERIK 840D/810D/FM-NCAutoTurn Graphic Programming System (07.99 Edition)Part 1: ProgrammingOrder No.: 6FC5 298-4AA40-0BP2

SINUMERIK 840D/840Di/810D/FM-NCOperator’s Guide (10.00 Edition)Order No.: 6FC5 298-6AA00-0BP0

– Operator’s Guide MMC

– Operator’s Guide HMI Advanced

SINUMERIK 840D/810D/ FM-NCOperator’s Guide Unit Operator Panel (04.96 Edition)Order No.: 6FC5 298-3AA60-0BP1

SINUMERIK 840D/840Di/810DOperator’s Guide HT 6 (HPU new) (06.00 Edition)Order No.: 6FC5 298-0AD60-0BP0

SINUMERIK 840D/840Di/810D/FM-NCShort Guide Operation (10.00 Edition)Order No.: 6FC5 298-6AA10-0BP0

SINUMERIK 840D/810DOperator’s Guide ManualTurn (02.00 Edition)Order No.: 6FC5 298-5AD00-0BP0

SINUMERIK 840D/810DShort Guide ManualTurn (11.98 Edition)Order No.: 6FC5 298-2AD40-0BP0

/AUE/

/AUK/

/AUP/

/BA/

/BAE/

/BAH/

/BAK/

/BAM/

/KAM/

B References

07.2000


SINUMERIK 840D/810DOperator’s Guide ShopMill (08.00 Edition)Order No.: 6FC5 298-5AD10-0BP1

SINUMERIK 840D/810DShort Guide ShopMill (01.98 Edition)Order No.: 6FC5 298-2AD30-0BP0

SINUMERIK 840D/840Di/810DOperator’s Guide Handheld Programming Unit (04.00 Edition)Order No.: 6FC5 298-5AD20-0BP1

SINUMERIK 840D/840Di/810D/FM-NCUser’s Guide Measuring Cycles (06.00 Edition)Order No.: 6FC5 298-5AA70-0BP2

SINUMERIK 840D/840Di/810D/FM-NCDiagnostics Guide (10.00 Edition)Order No.: 6FC5 298-6AA20-0BP0

SINUMERIK 840D/840Di/810D/FM-NCProgramming Guide Fundamentals (10.00 Edition)Order No.: 6FC5 298-6AB00-0BP0

SINUMERIK 840D/840Di/810D/FM-NCProgramming Guide Advanced (10.00 Edition)Order No.: 6FC5 298-6AB10-0BP0

SINUMERIK 840D/840Di/810D/FM-NCShort Guide Programming (10.00 Edition)Order No.: 6FC5 298-6AB30-0BP0

SINUMERIK 840D/840Di/810D/FM-NCProgramming Guide Cycles (10.00 Edition)Order No.: 6FC5 298-6AB40-0BP0

PCIN 4.4Software for Data Transfer to/from MMC ModuleOrder No.: 6FX2 060 4AA00-4XB0 (German, English, French)Order from: WK Fürth

SINUMERIK 840DiSystem Overview (01.00 Edition)Order No.: 6FC5 298-5AE40-0BP0

/BAS/

/KAS/

/BAP/

/BNM/

/DA/

/PG/

/PGA/

/PGK/

/PGZ/

/PI /

/SYI/

B References

07.2000




SINUMERIK 840D/840Di/810D/FM-NCSIMODRIVE 611DLists (10.00 Edition)Order No.: 6FC5 297-6AB70-0BP0

SINUMERIK 840D/840Di/810D/FM-NCOperator Components Manual (HW) (10.00 Edition)Order No.: 6FC5 297-6AA50-0BP0

SIMODRIVE SensorAbsolute Encoder with PROFIBUS-DPUser Guide (HW) (02.99 Edition)Order No.: 6SN1197-0AB10-0YP1

SINUMERIK, SIROTEC, SIMODRIVEEMC Installation GuidePlanning Guide (HW) (06.99 Edition)Order No.: 6FC5 297-0AD30-0BP1

SINUMERIK 810DConfiguring Manual (HW) (10.00 Edition)Order No.: 6FC5 297-4AD10-0BP0

SINUMERIK 840DNCU 561.2–573.2 Configuring Manual (HW) (10.00 Edition)Order No.: 6FC5 297-6AC10-0BP0

SINUMERIK FM-NCNCU 570 Configuring Manual (HW) (04.96 Edition)Order No.: 6FC5 297-3AC00-0BP0

SIMODRIVE SensorMeasuring System for Main Spindle DrivesConfiguring/Installation Guide, SIMAG-H (HW) (05.99 Edition)Order No.: 6SN1197-0AB30-0BP0

a) Lists

/LIS/

b) Hardware

/BH/

/BHA/

/EMV/

/PHC/

/PHD/

/PHF/

/PMH/

B References

07.2000


SINUMERIK 840D/840Di/810D/FM-NCDescription of Functions, Basic Machine (Part 1) – (10.00 Edition) –(the various sections are listed below)Order No.: 6FC5 297-6AC20-0BP0

A2 Various Interface SignalsA3 Axis Monitoring, Protection ZonesB1 Continuous Path Mode, Exact Stop and Look AheadB2 AccelerationD1 Diagnostic ToolsD2 Interactive ProgrammingF1 Travel to Fixed StopG2 Velocities, Setpoint/Actual-Value Systems, Closed-Loop

ControlH2 Output of Auxiliary Functions to PLCK1 Mode Group, Channel, Program Operation ModeK2 Axes, Coordinate Systems, Frames,

Actual-Value System for Workpiece, External Zero OffsetK4 CommunicationN2 EMERGENCY STOPP1 Transverse AxesP3 Basic PLC ProgramR1 Reference Point ApproachS1 Spindles V1 FeedsW1 Tool Compensation

SINUMERIK 840D/840Di/810D(CCU2)/FM-NCDescription of Functions, Extended Functions (Part 2) –(10.00 Edition)–including FM-NC: Turning, Stepper Motor(the various sections are listed below)Order No.: 6FC5 297-6AC30-0BP0

A4 Digital and Analog NCK I/OsB3 Several Operator Panels and NCUsB4 Operation via PG/PCF3 Remote DiagnosticsH1 Jog with/without HandwheelK3 CompensationsK5 Mode Groups, Channels, Axis ReplacementL1 FM-NC Local BusM1 Kinematic TransformationM5 MeasurementN3 Software Cams, Position Switching SignalsN4 Punching and NibblingP2 Positioning AxesP5 OscillationR2 Rotary AxesS3 Synchronous SpindlesS5 Synchronized Actions (up to and including SW 3)S6 Stepper Motor ControlS7 Memory ConfigurationT1 Indexing AxesW3 Tool ChangeW4 Grinding

c) Software

/FB1/

/FB2/

B References

07.2000



SINUMERIK 840D/840Di/810D(CCU2)/FM-NCDescription of Functions, Special Functions (Part 3) – (10.00 Edition) –(the various sections are listed below)Order No.: 6FC5 297-6AC80-0BP0

F2 3-Axis to 5-Axis TransformationG1 Gantry AxesG3 Cycle TimesK6 Contour Tunnel MonitoringM3 Coupled Motion and Leading Value CouplingS8 Constant Workpiece Speed for Centerless GrindingT3 Tangential ControlV2 PreprocessingW5 3D Tool Radius CompensationTE1 Distance ControlTE2 Analog AxisTE3 Master-Slave for DrivesTE4 Transformation Package for HandlingTE5 Setpoint ExchangeTE6 MCS Coupling

SIMODRIVE 611D/SINUMERIK 840D/810DDescription of Functions, Drive Functions (10.00 Edition)(the various sections are listed below)Order No.: 6SN1 197-0AA80-0BP6

DB1 Operational Messages/Alarm ReactionsDD1 Diagnostic FunctionsDD2 Speed Control LoopDE1 Extended Drive FunctionsDF1 Enable CommandsDG1 Encoder ParameterizationDM1 Calculation of Motor/Power Section Parameters and

Controller DataDS1 Current Loop ControlDÜ1 Monitors/Limitations

SINUMERIK 840D/SIMODRIVE 611 digitalDescription of Functions ANA Module (02.00 Edition)Order No.: 6SN1 197-0AB80-0BP0

SINUMERIK 840DDescription of Functions Digitizing (07.99 Edition)Order No.: 6FC5 297-4AC50-0BP0

DI1 Start-UpDI2 Scanning with Tactile Sensors (scancad scan)DI3 Scanning with Lasers (scancad laser)DI4 Milling Program Generation (scancad mill)

/FB3/

/FBA/

/FBAN/

/FBD/

B References

07.2000


CAM Integration DNC NT-2000Description of Functions System for NC Data Management and Data Distribution (05.00 Edition)Order No.: 6FC5 297-6AE50-0BP0

SINUMERIK 840D/840Di/810DDescription of Functions ISO Dialects for SINUMERIK (10.00 Edition)Order No.: 6FC5 297-6AE10-0BP0

SINUMERIK 840D/SIMODRIVE 611 digitalDescription of Functions HLA Module (08.99 Edition)Order No.: 6SN1 197-0AB60-0BP1

SINUMERIK 840D/810DDescription of Functions ManualTurn (02.00 Edition)Order No.: 6FC5 297-5AD50-0BP0

SINUMERIK 840D/810D/FM-NCDescription of Functions Configuring of Operator Interface OP 030 (03.96 Edition)(the various sections are listed below)Order No.: 6FC5 297-3AC40-0BP0

BA Operator’s GuideEU Development Environment (Configuring Package)PS Online only: Configuring Syntax (Configuring Package)PSE Introduction to Configuring of Operator InterfaceIK Screen Kit: Software Update and Configuration

SINUMERIK 840DDescription of Functions C-PLC Programming (03.96 Edition)Order No.: 6FC5 297-3AB60-0BP0

SINUMERIK 840D/810DDescription of Functions SINCOM Computer Link (02.00 Edition)Order No.: 6FC5 297-5AD60-0BP0

NFL Host Computer InterfaceNPL PLC/NCK Interface

SINUMERIK 840D / SIMODRIVEDescription of Functions SINUMERIK Safety Integrated (05.00 Edition)Order No.: 6FC5 297-5AB80-0BP1

/FBDN/

/FBFA/

/FBHLA/

/FBMA/

/FBO/

/FBP/

/FBR/

/FBSI/

B References

07.2000



SINUMERIK 840D/810DDescription of Functions ShopMill (08.00 Edition)Order No.: 6FC5 297-5AD80-0BP1

SIMATIC (11.98 Edition)FM STEPDRIVE/SIMOSTEPDescription of FunctionsOrder No.: 6SN1 197-0AA70-0YP3

SINUMERIK 840D/840Di/810D(CCU2)Description of Functions Synchronized Actions (10.00 Edition)for Wood, Glass, Ceramics, PressesOrder No.: 6FC5 297-6AD40-0BP0

SINUMERIK 840D/810DDescription of Functions Tool Information SINTDI with Online Help (04.99 Edition)Order No.: 6FC5 297-5AE00-0BP0

SIMODRIVE 611 universalDescription of Functions (05.00 Edition)Closed-Loop Control Component for Speed Control and PositioningOrder No.: 6SN1 197-0AB20-0BP3

SINUMERIK 840D/840Di/810DDescription of Functions Tool Management (07.00 Edition)Order No.: 6FC5 297-5AC60-0BP2

SINUMERIK 840DiManual (06.00 Edition)Order No.: 6FC5 297-5AE60-0BP0

SINUMERIK 840D/810D/FM-NCScreen Kit MMC 100/Unit Operator Panel (06.96 Edition)Description of Functions: Software Update and ConfigurationOrder No.: 6FC5 297-3EA10-0BP1

SIMODRIVE 611 universalShort Description (05.00 Edition)Closed-Loop Control Component for Speed ControlOrder No.: 6SN1 197-0AB40-0BP3

/FBSP/

/FBST/

/FBSY/

/FBTD/

/FBU/

/FBW/

/HBI/

/IK/

/KBU/

B References

07.2000


SIMODRIVEPlanning Guide Linear Motors (05.00 Edition)(on request)ALL General Information about Linear Motors1FN1 1FN1 Three-Phase AC Linear Motor1FN3 1FN3 Three-Phase AC Linear MotorCON ConnectionsOrder No.: 6SN1 197-0AB70-0BP1

SIMODRIVEPlanning Guide MotorsThree-Phase AC Motors for Feed and Main Spindle Drives (09.00 Edition)Order No.: 6SN1 197-0AA20-0BP4

SIMODRIVEPlanning Guide 1FE1 Synchronous Built-In MotorsThree-Phase AC Motors for Main Spindle Drives (03.00 Edition)Order No.: (on request)

SIMODRIVE 611-A/611-D Planning Guide Inverters (08.98 Edition)Transistor PWM Inverters forAC Feed Drives and AC Main Spindle DrivesOrder No.: 6SN1 197-0AA00-0BP4

SIMODRIVE POSMO A (02.00 Edition)Distributed Positioning Motor on PROFIBUS DP, User ManualOrder No.: 6SN2197-0AA00-0BP1

SIMODRIVE POSMO A (12.98 Edition)Installation Instructions (enclosed with POSMO A)Order No.: 462 008 0815 00

SIMODRIVE POSMO SI/CD/CA (09.00 Edition)Distributed Servo Drive Technology, User ManualOrder No.: 6SN2197-0AA20-0BP0

SIMATIC S7-300 (10.98 Edition)– Manual: Assembly, CPU Data (HW)– Reference Manual: Module DataOrder No.: 6ES7 398-8AA03-8AA0

SIMATIC S7-300 (03.97 Edition)Manual: STEP 7, Basic Information, V. 3.1Order No.: 6ES7 810-4CA02-8AA0

/PJLM/

/PJM/

/PJMS/

/PJU/

/POS1/

/POS2/

/POS3/

/S7H/

/S7HT/

B References

07.2000



SIMATIC S7-300 (03.97 Edition)Manual: STEP 7, Reference Manuals, V. 3.1Order No.: 6ES7 810-4CA02-8AR0

SIMATIC S7-300 (04.97 Edition)FM 353 Step Drive Positioning Module Order in conjunction with Configuring Package

SIMATIC S7-300 (04.97 Edition)FM 354 Servo Drive Positioning Module Order in conjunction with Configuring Package

SIMATIC S7-300 (10.99 Edition)FM 357 Multi-Axis Module for Servo and Stepper DrivesOrder in conjunction with Configuring Package

SIMODRIVE 611 (01.98 Edition)Manual Single-Axis Positioning for MCU 172AOrder No.: 6SN 1197-4MA00-0BP0

SIMODRIVE 611-A/611-D,SimoPro 3.1Program for Configuring Machine-Tool DrivesOrder No.: 6SC6 111-6PC00-0AA�Order from: WK Fürth

SIMODRIVE 611AInstallation and Start-Up Guide (09.00 Edition)Order No.: 6SN 1197-0AA60-0BP5

SINUMERIK 810DInstallation and Start-Up Guide (10.00 Edition)(incl. description of SIMODRIVE 611D start-up software)Order No.: 6FC5 297-4AD20-0BP0

SINUMERIK 840D/SIMODRIVE 611DInstallation and Start-Up Guide (10.00 Edition)(incl. description of SIMODRIVE 611D start-up software)Order No.: 6FC5 297-6AB10-0BP0

SINUMERIK FM-NCInstallation and Start-Up Guide (04.96 Edition)Order No.: 6FC5 297-3AB00-0BP0

/S7HR/

/S7S/

/S7L/

/S7M/

/SHM/

/SP/

d) Installation and start-up

/IAA/

/IAC/

/IAD/

/IAF/

B References

07.2000


SINUMERIK 840D/840Di/810DMMC/HMI Installation and Start-Up Guide (10.00 Edition)Order No.: 6FC5 297-6AE20-0BP0

IM1 Start-Up Functions for the MMC 100.2IM3 Start-Up Functions for the MMC 103IM4 Start-Up Functions for the HMI Advanced (PCU 50)HE1 Online HelpBE1 Supplement Operator Interface

/IAM/

B References

07.2000



B References

Index-261 Siemens AG 2000 All Rights ReservedSINUMERIK FM-NC Installation and Start–Up Guide (IAF) – 07.2000 Edition

Index

AAbortion of MD import, 11-200Acceleration characteristics with breakpoint,

6-121Accleration characteristic with breakpoint, activa-

tion, 6-122Address/switch settings, 5-74Alarm text files for MMC, alarm numbers, 8-173Alarm text files for MMC 100/100.2, files, 8-169Alarm text files for MMC 102/103, 8-170

configuration in mbdde.ini, 8-170example, 8-172

Alarm text files for MMC100/100.2, 8-168Alarm text languages, 8-171Alarm texts for MMC 102/103, editor, 8-171Alarm texts/message texts, 8-168APP_INST.EXE, 12-216Applications of tool box, 13-237Area-specific archive data, 11-192Area-specific archiving, 11-190Assessing machine data via part program, 13-238

data identifiers, 13-238Axes and spindles, 6-105

testing, 9-179, 9-180Axis and spindle dry run, 9-177

preconditions, 9-178Axis configuration, 6-105

extension to 5th axis, 6-139Axis data, 6-109Axis enabling, 9-178Axis extension, 6-139Axis start-up

encoder matching, 6-111monitoring, 6-129reference point approach, 6-135setpoint routing, 6-120testing the axis, 9-179velocity/speed matching, 6-121

Axis start-up data, control data, 6-124

BBasic PLC program, 13-237

Basic settings for operator paneldisplay resolution, 6-140language, 6-140protection levels, 6-140screen, 6-140V24 interfaces, 6-140

Battery connection, 2-38Battery replacement, 12-234Battery voltage monitoring, 2-38BIOS-setup, MMC102, 5-80Booting

booting of FM-NC (NCU 570.2), 5-78booting of machine control panel, 5-81booting of MMC, 5-81booting of PLC-CPU, 5-79components involved in booting, 5-77operator control and display elements, 5-75

Booting of entire system, 5-76Booting of system software, 5-75Bus addresses, 3-55

CChecking the loop gain, 6-126Components involved in booting, 5-77Configuration

basic settings for operator panel, 6-140changing memory areas, 6-96general, 6-92internal calculation resolutions, 6-95switchover from metric to inch system, 6-93

Configuration and machine data of local P bus ofFM-NC, 6-141FM 354 as 5th axis, 6-141inputs/outputs, 6-141

Connector pin assignmentFM 354, 2-35FM-NC, 2-30

Control data, 6-124COROS OP 27 operator interface, 2-52CPU, MPI multi-point interface, 7-163CPU operating status for FM-NC start-up, 7-163

cyclic operation, 7-163reset, 7-164restart, 7-164

07.2000

Index-262 Siemens AG 2000 All Rights Reserved


CPU314positions of mode switch, 7-160status and error displays, 7-162

CPU318, 12-230MMC configuration, 12-231rack-slot addresses, 12-231settings of switch S3 on MCP, 12-230STEP7, 12-230

Cycle alarms, 11-189

DData identifiers, 13-238Data saving, 11-187

series start-up, 11-189Data saving via MMC100/100.2, 11-189Data saving via MMC102/103, 11-193Data type, 6-86Displaying unassigned SRAM and DRAM, 6-99Documentation, 1-17Drive optimization

aim, 10-184checking the speed control loop, 10-185overview, 10-184procedure, 10-184

EEditor, 8-169, 8-171EMC and ESD measures, 4-69Encoder matching

actual value encoder on spindle, 6-116actual value processing, 6-116linear measuring systems, 6-115SSI-encoder, 6-113

Encoder matching (axis), 6-111Encoder matching (spindles), 6-145Equipment and accessories, 1-16Erasure of SRAM through MD change, 6-98Evaluation of line checksums, 11-199

FFM 254 interfaces, drive interface, 2-33FM 354, as 5th axis, 6-139FM 354 interfaces

I/O interface, 2-33measuring system interfaces, 2-33SIMATIC interface, 2-33

GGeneral preparations, 1-15

HHand-held unit (HHU), 2-51

default setting for FM-NC, 2-51Handling machine and setting data, 6-85Hardware replacement, 12-230

hardware replacement CPU, 12-233hardware replacement FM-NC, 12-233

Hardware requirements, 3-55

IInitial start-up, 6-100

initialize system, 6-100user data for operator panel, 6-100

Initialization of system, 6-91FM-NC, 6-91MMC100, 6-91

Input of machine data, 6-84Installation of MMC100/100.2 application diskette,

12-216Installation via PC/PG to MMC102/103, 12-226Integration of FM-NC module in the S7-300 PLC,

2-24Interface for customer operator panel, 2-50

default settings of switch S3, 2-50Interfaces

machine control panel, 2-46operating elements of MMC 100, 2-41operating elements of MMC 100.2, 2-42operating elements of MMC 102/103, 2-44operator panel with MMC, 2-40operator panel with MMC 102/103, 2-43operator panel with PCI adapter, 2-45

Interfaces NCU 570, memory module interface,2-27

LLine checksums, 11-199Line checksums and MD numbers in MD files,

11-199Loading archiving data, 11-191Loading of scaling machine data, 11-202Local P bus, 2-24, 6-141

MMachine and setting data, 6-84, 6-85

data areas, 13-238default value, 6-86unit, 6-85value range, 6-86

C General Index

07.2000

Index-263 Siemens AG 2000 All Rights ReservedSINUMERIK FM-NC Installation and Start–Up Guide (IAF) – 07.2000 Edition

Machine control panel, settings for CPU318,12-230

Machine control panel OP032Sdefault settings of switch S3, 2-48possible settings S3, 2-49

Machine data numbers, 11-200Measures to protect ESD-sensitive components,

4-71Measures to suppress interference, 4-70Memory areas, 6-96Memory configuration, 6-96

hardware configuration, 6-96MMC 100.2, 2-42MMC 102/103, 2-43Modulo counter, 6-134Monitoring functions axis, 6-129

automatic drift compensation, 6-134by means of hardware limit switches, 6-130contour monitoring, 6-132encoder monitoring, 6-133modulo counter, 6-134stepper motor rotation monitoring with BERO,

6-134velocity limitation, 6-132velocity monitoring, 6-132

Monitoring functions spindles, 6-151More than one language, 8-168MPI networking rules, 3-54

NNC variable selector, 13-237NCU 570 interfaces

drive interface, 2-27I/O interface, 2-27measuring system interfaces, 2-27power supply connection, 2-27SIMATIC interface, 2-27

OO & M for FM-NC with OP 27, 13-239

configuring, 13-239Operational messages, 11-189Operator control functions for start-up, 6-89Operator controls, 2-27, 5-75

start-up switch, 2-27start-up switch on FM-NC, 5-75start-up switch on PLC-CPU, 5-75

Operator inputs for PLC general reset, 5-79Overview of connections

for FM 354, 2-32for FM-NC, 2-26

Overview of machine and setting data, 6-84Overview of organization blocks, OBs, FBs, DBs,

7-165

PPCI adapter, 2-45PLC general reset, 5-79PLC restart, 5-79PLC start-up, 7-155

COMPLETE RESTART start-up mode, 7-158PLC applications, 7-156structure, 7-157tool box, 7-156

PLC-CPU display elements, 5-75Power On, 5-74Power On and Power-Up, 5-73Power On sequence, 5-74Power supply, FM-NC, 2-36, 2-37Prerequisite for start-up, basic machine data, 1-19Problems during booting, 5-81

MMC 100/100.2, 5-81MMC 102/103, 5-81

Properties of line checksums, 11-199Protection level strategy, 6-87Protection levels 0–3, 6-87Protection levels 4–7, 6-88

RRack-slot addresses, 12-231Reading in area-specific archive data, 11-192Reading in series start-up files, 11-191Reference cam calibration, 6-135Reference point approach, 6-135

with distance-coded reference marks, 6-137with incremental mreasuring systems, 6-136

Reference point approach for stepper motors,6-138synchronization with BERO reference point,

6-138Requirements to be fulfilled prior to start-up

documentation requirements, 1-17equipment and accessory requirements, 1-16machine data, 1-19software requirements, 1-16start-up, 1-18visual inspection/wiring, 1-18

Requirements to be fulfilled prior to start–up, jum-per connections, 1-18

SSaving altered values, 11-203Series start-up/area-specific archiving, 11-188Servo gain, 6-125Setpoint routing axis, 6-120Settings, MPI-bus, example of a configuration,

3-60Settings, MPI nodes, 3-53

C General Index

07.2000

Index-264 Siemens AG 2000 All Rights Reserved


Shielded signal leads, 4-70Software upgrading MMC 100.2

installation via PCMCIA, 12-221installation via PCMCIA with modifications,

12-222installation via PCMCIA without modifications,

12-221Software/hardware replacement, 12-205Speeds and setpoint adjustment spindles, 6-147Spindle data, 6-143

axis mode, 6-143general machine data definitions, 6-144speeds and setpoint adjustment spindles,

6-147spindle operating modes, 6-143spindle synchronization, 6-150

Spindle start-upspindle definition, 6-143spindle positioning, 6-149testing the spindle, 9-180

Standard application, 3-55Standard files, 8-170Standard MD sets, 13-237Start-up of functions, 6-153Start-up sequence, 5-74Start-up switch, 2-27, 5-75

FM-NC, 2-27, 5-75PLC-CPU, 5-75

Starting up a series machine, user data for opera-tor panel, 6-104

STEP7, 3-55Stepper motor control loop, 6-126Stepper motor rotation monitoring with BERO,

6-134Storage of text files, 8-170Syntax for alarm text files, 8-173Syntax for alarm texts, PLC alarm texts, 8-175

TText for error messages, operational messages

and cycle alarms, 11-189Tool box, 13-236Tool box software package, 13-236

application, 13-237basic PLC program, 13-237contents, 13-236hardware requirements, 13-236NC variable selector, 13-237software requirements, 13-236standard MD sets, 13-237

Transfer of SW from PC/PG disk to MMC, 12-229Traversing direction, 6-125

UUpgrading FM-NC software, 12-206Upgrading MMC 100/100.2 software, installation

with modifications, 12-220Upgrading MMC 100/100.2 software

as supplied, 12-208installation of MMC 100/100.2 system dis-

kette, 12-210installation procedure, 12-210installation software, 12-208

Upgrading MMC 102/103 software, 12-225installation via MMC floppy drive, 12-225

User files, 8-171

VVelocity/speed matching axis, 6-121

acceleration characteristic with breakpoint,6-121

Visual inspection, 5-74

C General Index

Siemens AG 1994 All Rights Reserved 6FC5 297–�AB00

From

Name

Company/Dept.

Address

/

Suggestions

Corrections

For Publication/Manual

SINUMERIK FM–NC


Installation and Start–up Guide

Order No.: 6FC5 297-3AB00-0BP1Edition: 07.2000

Should you come accross any printingerrors when reading this publication,please notify us on this sheet.Suggestions for improvement are alsowelcome.

SIEMENS AG

Telefax: /

Telephone:

A&D MC ISPostfach 3180

D-91050 Erlangen

(Tel. +49 - 180 / 525 - 8008 / 5009 [Hotline]Fax +49 - 9131 / 98 - 2176E-mail: [email protected])

Suggestions and/or corrections

SINUMERIK

840D/810D/FM-NC

SINUMERIK

Overview of SINUMERIK 840D/840Di/810D/FM-NC Documentation

Brochure Catalog Ordering Info NC 60 *)

Description of Functions Drive Functions *)

Description of Functions– Basic Machine *) – Extended Functions– Special Functions

SINUMERIK

611D840D/810D

SINUMERIK

840D/840Di/810D/FM-NC

840D/840Di/810D/FM-NC/611

Accessories

CatalogAccessories NC-Z

SINUMERIKSIROTECSIMODRIVE

840D/840Di/810DFM-NC611D

Lists *)Installation &Start-up Guide *)– FM-NC– 810D– 840D/611D– MMC/HMI

SINUMERIK

840D

Description ofFunctionsDigitizing

SINUMERIK

SINUMERIK

840D/810D/FM-NC

Configuring KitMMC 100/101– Configuring

Syntax – Development Kit

SINUMERIK

840D/810D/FM-NC

Screen KitMMC 100/101SW Update andConfiguration

SINUMERIK

840D/840Di/810D/FM-NC

SINUMERIK

840D/840Di/810D

Operator Components(HW) *)

840D/840Di/810D/FM-NC

Description ofFunctionsSINUMERIKSafety Integrated

SINUMERIKSIMODRIVE

SINUMERIK

840D/840Di/810D/FM-NC, 611,Motors

SIMODRIVE

DOC ON CD *)The SINUMERIK System

General Documentation

Electronic Documentation



SINUMERIK

840D/810D/FM-NC

SINUMERIK

840D/810D

User Documentation

DiagnosticsGuide *)

Operator’s Guide– HT 6 (+ 840Di)– HPU– Unit Operator

Panel

AutoTurn– Short Guide– Programming (1)– Setup (2)

SINUMERIK

840D/840Di/810D/FM-NC

Program. Guide– Short Guide– Fundamentals *)– Advanced *)– Cycles– Measuring Cycles

Description ofFunctions– ManualTurn– ShopMill

Description ofFunctionsSynchronized Actions

840D/810D

SINUMERIK

Operator’s Guide– ManualTurn– Short Guide ManualTurn– ShopMill– Short Guide ShopMill

840D/810D


SINUMERIK

840D/810D

Descr. of Functions– Computer Link– Tool Data

Information System

*) These documents are a minimum requirement for the control

Operator’s Guide– Short Guide– Operator’s Guide *)

SINUMERIK

840D/840Di/810D/FM-NC

Configuring (HW) *)– FM-NC– 810D– 840D

SINUMERIK

SINUMERIK

840D/840Di/810D

SINUMERIK

840D/810D/FM-NC

Description ofFunctionsOperator InterfaceOP 030

Description ofFunctionsTool Management

SINUMERIKSIMODRIVE

SINUMERIKSIMODRIVE

SINUMERIKSIMODRIVE

SINUMERIKSIMODRIVE

SINUMERIKSIMODRIVE

840D611D

840D611D

Description ofFunctionsLinear Motor

SINUMERIKSIMODRIVESIROTEC

EMC Guidelines

Description ofFunctions– Hydraulics

Module– Analog Module

User Documentation

SINUMERIK

System Overview

840Di


SINUMERIK

Descr. of FunctionsISO Dialects for SINUMERIK

840D/840Di/810D

SINUMERIK

Descr. of FunctionsCAM IntegrationDNC NT-2000

SINUMERIK

Manual(HW + Installationand Start-up)

840Di

sinumerik fm-nc installation and start-up guide 07-00

Documents

new documentation

documentation available

new edition coding

thenext edition

new order

new status

c revised edition

control system