rexroth indramotion mtx · rexroth indramotion mtx opc interface project planning manual...

Rexroth IndraControl VCP 20

IndustrialHydraulics

Electric Drivesand Controls

Linear Motion and Assembly Technologies Pneumatics

ServiceAutomation

MobileHydraulics

Rexroth IndraMotion MTXOPC Interface

R911310459Edition 01

Project Planning Manual

About this Documentation OPC Interface

DOK-MTX***-OPC*INT*V02-PR01-EN-P

Rexroth IndraMotion MTX

OPC Interface

Project Planning Manual


Document Number 120-2500-B313-01/EN

This documentation describes the OPC Interface.

Description ReleaseDate

Notes

120-2500-B313-01/EN 03.2005 First issue

2005 Bosch Rexroth AG

Copying this document, giving it to others and the use or communicationof the contents thereof without express authority, are forbidden. Offendersare liable for the payment of damages. All rights are reserved in the eventof the grant of a patent or the registration of a utility model or design(DIN 34-1).

The specified data is for product description purposes only and may notbe deemed to be guaranteed unless expressly confirmed in the contract.All rights are reserved with respect to the content of this documentationand the availability of the product.

Bosch Rexroth AGBgm.-Dr.-Nebel-Str. 2 • D-97816 Lohr a. Main

Telephone +49 (0)93 52/40-0 • Tx 68 94 21 • Fax +49 (0)93 52/40-48 85

http://www.boschrexroth.com/

Dept. BRC/ESM11 (JS)

Dept. BRC/ESM6 (DiHa)

This document has been printed on chlorine-free bleached paper.

Title

Type of Documentation

Document Typecode

Internal File Reference

Purpose of Documentation

Record of Revisions

Copyright

Validity

Published by

Note

OPC Interface Contents I


Contents

1 Communication through the OPC Server 1-1

1.1 General ......................................................................................................................................... 1-1

1.2 Test Client..................................................................................................................................... 1-2

1.3 Example for VB6........................................................................................................................... 1-6

2 System Items 2-1

2.1 Items for Control Diagnosis .......................................................................................................... 2-1

2.2 Language Switching ................................................................................................................... 2-12

2.3 Archives ...................................................................................................................................... 2-14

2.4 Time of the Day........................................................................................................................... 2-17

2.5 Time Zone................................................................................................................................... 2-18

2.6 Software Versions....................................................................................................................... 2-18

3 NC Items 3-1

3.1 General NC Items......................................................................................................................... 3-1

3.2 Status Information......................................................................................................................... 3-2

3.3 General XML Functions ................................................................................................................ 3-4

3.4 File-Based Tables......................................................................................................................... 3-6

3.5 Database-Based Tables ............................................................................................................... 3-9

3.6 Configuration Data...................................................................................................................... 3-15

3.7 System Data ............................................................................................................................... 3-18

Overview................................................................................................................................ 3-18

Read and Write Access to System Data ............................................................................... 3-20

List of System Data Items...................................................................................................... 3-20

SDI Events............................................................................................................................. 3-21

Load and Save....................................................................................................................... 3-22

3.8 Global Settings ........................................................................................................................... 3-23

3.9 Access to MACODA Parameter ................................................................................................. 3-24

3.10 Access to Permanent CPL-Variables ......................................................................................... 3-25

3.11 Delete Error ................................................................................................................................ 3-28

4 Channel-Specific Items 4-1

4.1 Status Information......................................................................................................................... 4-2

4.2 Active Programs and Tables......................................................................................................... 4-8

4.3 Axis Position Data......................................................................................................................... 4-9

4.4 Compensation and Offset Values............................................................................................... 4-16

4.5 Modal Functions ......................................................................................................................... 4-18

4.6 Technology Data......................................................................................................................... 4-20

II Contents OPC Interface


4.7 Other Process Data .................................................................................................................... 4-25

4.8 Mode of Operation, Program Selection, Reset, MDI etc. ........................................................... 4-28

4.9 Channel Settings ........................................................................................................................ 4-38

5 Error Handling 5-1

5.1 SAV Errors.................................................................................................................................... 5-2

5.2 MACODA Errors ........................................................................................................................... 5-3

5.3 TAD Errors.................................................................................................................................... 5-3

5.4 DBD Error ..................................................................................................................................... 5-4

5.5 CFG Errors ................................................................................................................................... 5-4

5.6 SD Errors ...................................................................................................................................... 5-5

5.7 XML Errors.................................................................................................................................... 5-6

5.8 TAR Errors.................................................................................................................................... 5-8

6 Index 6-1

7 Service & Support 7-1

7.1 Helpdesk....................................................................................................................................... 7-1

7.2 Service-Hotline ............................................................................................................................. 7-1

7.3 Internet.......................................................................................................................................... 7-1

7.4 Vor der Kontaktaufnahme... - Before contacting us... .................................................................. 7-1

7.5 Kundenbetreuungsstellen - Sales & Service Facilities ................................................................. 7-2

OPC Interface Communication through the OPC Server 1-1


1 Communication through the OPC Server

1.1 General

The GUI of the IndraMotion MTX communicates with the control kernelthrough the Scalable Communication Platform SCP. The communicationlayer can also be used by the OEM for its own interface functions orextensions. The SCP is accessed via the standardized interface OPC.

By using the OPC interface, the machine manufacturer can very easilyaccess control data. Here, it is not relevant for access whether the controlis comprised in the same hardware or linked by means of a networkconnection. The destination device is identified exclusively through itsname. As the OPC server will take full responsibility for administration ofthe communication relations, safe and interference-free operation isguaranteed.

As the OPC interface is widely spread in automation engineering, it iseasy to adjust the machine manufacturer's developments to the variouscontrol types.

The OPC server is a component of the IndraMotion MTX. You do notneed a licence to implement your own GUI extensions.

In this Chapter, the configuration of a communication relation andexchange of data between a user program and the control is described byway of example of a VisualBasic program.

The following Chapters document all available SPC items which can beused in the frame of OPC calls.

1-2 Communication through the OPC Server OPC Interface


1.2 Test Client

Together with the GUI, a so-called Test Client is installed. This programmakes it very easy to send data requests to the OPC server and todisplay the answers. Because of the standardization of the OPCcommunication, this function can also be taken over by any other freelyavailable OPC client.

The Test Client is named "OPCClient.exe" and must be started in thedirectory C:\Programs\Rexroth\IndraWorks.

To enable the OPC server to use the MTX items, additionally start theMTX interface.

OPC_Client_Start.JPG

Fig. 1-1: Test Client



Select "OPC.IwSCP.x" from "Server List" and activate the "Connect"button to make the connection.

OPC_Client_Connect.JPG

Fig. 1-2: Server allocation

Under "IOPCServer" a new group is generated with "AddGroup". Thegroup name is freely selectable.

OPC_Client_AddGroup.JPG

Fig. 1-3: Add a group



Under "IOPCItemMgt", generate a new item with "AddItem". Example:

!R8,IndraMotion_MTX_P60,NC.Chan.AxisPosWcs,1 {0,7}

OPC_Client_AddItem.JPG

Fig. 1-4: Add an item

"!R8" corresponds to the error result type of the item and is an optionalparameter.R8 = RealI4 = Integeretc.

"IndraMotion MTX P60" is the name of the MTX device stored inIndraWorks Engineering.

"NC.Chan.AxisPosWcs.1" is an SCP item.

"{0.7}" corresponds to the single data element of the result matrix of theitem response.



Under "IOPCSyncIO", the item is selected and read via "Read". The resultis indicated under "Value".

OPC_Client_Read.JPG

Fig. 1-5: Reading out an item



1.3 Example for VB6

In the example, three SCP items are read cyclically and displayed in thetext boxes. Via "Buttons", synchronous reading of the three items as wellas synchronous and asynchronous writing of one item is performed.

OPC_VB_Example.JPG

Fig. 1-6: Example VB

To allow for use of MTX-specific items, the logic device of the MTX mustbe started. This can either be done when the MTX interface is started, ordirectly in the program.

To enable start of the LDX in the project, "IwSCP x.x" must beincorporated under "References". "x.x" stands for the developmentversion.



OPC_IwSCP.JPG

Fig. 1-7: Incorporation of the IwSCP

The LDX is connected with the following routine. This takes place in the"Initialize" step and may take some time.

OPC_LoadLDX.JPG

Fig. 1-8: Load LDX

The "ScpConfig.ini" file conmprises the SCP specific settings which allowfor connection of the LDX. Copy the file into the path under"data.SetValue". Any adjustments, e.g. the device name (here"IndraMotion_MTX_P60") or the TCP/IP settings, must be made in thefile.



The OPC server must be incorporated via "References". Here, "OPCAutomation x.x" is activated. "x.x" stands for the development version.

OPC_Automation.JPG

Fig. 1-9: Incorporation of the OPC server

The required declarations for the OPC server are performed as follows:

OPC_Deklaration.JPG

Fig. 1-10: Declaration of the OPC server



In the "Connect" function, the connection to the OPC server is made orexited. A group is generated to which three SCP items are assigned. TheSCP items have the same structure as used for the OPC client describedabove.

The "Connect" function is called as follows:

• Connect: Call Me.HelloOPC1.Connect(True, "OPC.IwSCP.1")

• Exit: Call Me.HelloOPC1.Connect(False, "OPC.IwSCP.1")

Here, the OPC server described in connection with the OPC client is usedas well.

OPC_Connect.JPG

Fig. 1-11: "Connect" function

Once one of the three items changes, a callback function is called. Theevaluation of the items can be programmed here.

PLC items are addressed as follows:

After definition of a PLC access with "Plc.PVL", the PLC variable isdefined, e.g.:

• "iScreen" is used to define the global variable "iScreen".

• "PLCPRG.TestVar" is used to define the variable "TestVar in the"PLCPRG" program.



OPC_Callback.JPG

Fig. 1-12: Callback function

When the project is exited, the "Terminate" function is called up. Thegenerated group of the OPC server is completely deleted here.

OPC_Terminate.JPG

Fig. 1-13: "Terminate" function

Use the "Buttons" to start synchronous reading and writing, orasynchronous writing.

OPC_Buttons.JPG

Fig. 1-14: Definition of the buttons

With synchronous reading, cyclic reading is stopped, the items are readonce and then cyclic reading is started once more.



OPC_syncRead.JPG

Fig. 1-15: "Synchronous reading" function

With synchronous writing, cyclic reading is stopped, the item is writtenonce, and then cyclic reading is started once more.

OPC_syncWrite.JPG

Fig. 1-16: "Synchronous writing" function

With asynchronous writing, cyclic reading is not stopped, the item iswritten once parallel with cyclic reading.



OPC_asyncWrite.JPG

Fig. 1-17: "Asynchronous writing" function

The complete project can be opened through the link. As a precondition, aVB6 installation must be present.

OPC Interface System Items 2-1


2 System Items

2.1 Items for Control Diagnosis

There are different types of diagnosis items.

1. General commands. With these commands, simultaneous requestsof various types of diagnosis messages can be made, e.g. ProVitogether with MTX messages.

2. Specific commands for certain types of message. These messageshave been defined specifically for a certain type of message, e.g.special commands for the ProVi criteria analysis.

This Chapter describes the general commands.

Even if the general commands supply data for all types of diagnosis,different results are returned for each type.

Usually, there is always a solidly defined part which is identical with alltypes; after that, the type-specific data follows. From a result in the solidlydefined part, the type of diagnosis item in question is visible, and the kindof additional data to be expected.

Depending on the type of item, diagnosis items exist for a logic devicewith diagnosis (LD Diag) or for the logic devices for the logbook (LDLogbook).

Item name Brief description Logical device thatcan execute thiscommand

System.MessageStore Reading out of the current messages LD Diag

System.MessageStoreEx Reading out of the additional data of a message LD Diag

System.MessageStatus Query whether there are messages pending,changing, or newly received

LD Diag

System.ErrorStatus Query whether there are messages of 'Error'classification pending, changing, or newlyreceived

LD Diag

System.InfoStatus Query whether there are messages of 'Note'classification pending, changing, or newlyreceived

LD Diag

System.WarningStatus Query whether there are messages of 'Warning'classification pending, changing, or newlyreceived

LD Diag

System.StartupStatus Query whether there are messages of 'Startupstatus' classification pending, changing, ornewly received

LD Diag

System.SetupStatus Query whether there are messages of 'Setupstatus' classification pending, changing, ornewly received

LD Diag

System.MessageReset Resets the current messages LD Diag

System.LogbookStore Reads out the data of the logbook LD Logbook

System.LogbookStoreEx Reads out the additional data of a logbook entry LD Logbook

System.LogbookClear Cancels entries in the logbook LD Logbook

System.LogbookDevices Specifies the controls which are logged in thelogbook

LD Logbook

Brief description controldiagnosis items

2-2 System Items OPC Interface


Parameter of the Diagnosis ItemsHere, the valid value ranges of the individual parameter types for thecontrol diagnosis items are described.

There are different diagnosis types; they are defined in the IDL fileScpDiagnosisComponent by the enumerator SCPDiagnosisType.

• SCPDiagnosisType_MTX 0x01 MTX messages

• SCPDiagnosisType_ProVi 0x02 ProVi Messages

If all diagnosis types are required, the SCPDiagnosisType_All can beused. (This value corresponds to the string -1 in the item string, e.g.System.MessagStore,-1,2,3,0)

To combine different types, the types in question can be connected by anOR link.

Example: MTX and ProVi messages

SCPDiagnosisType_MTX | SCPDiagnosisType_ProVi

corresponds to 0x01 | 0x02 and equals 0x03.

Note: Even if the enumerator is defined as a hexadecimal value, adecimal value is expected as a filter.

There are different types of diagnosis classes; they are defined in the IDLfile ScpDiagnosisComponent by the enumerator SCPDiagnosisClass.

• SCPDiagnosisClass_Error 0x01 Error

• SCPDiagnosisClass_Info 0x02 Note

• SCPDiagnosisClass_Warning 0x04 Warning

• SCPDiagnosisClass_Startup 0x08 Start requirements

• SCPDiagnosisClass_Setup 0x10 Setup diagnosismessage

If all diagnosis classes are required, the SCPDiagnosisClass_All can beused. (This value corresponds to the string -1 in the item string, e.g.System.MessagStore,2,-1,3,0)

To combine different types, the classes in question can be connected byan OR link.

Example: Warning and setup diagnosis

SCPDiagnosisClass_Warning | SCPDiagnosisClass_Setup

corresponds to 0x04 | 0x10 and equals 0x14 as decimal value 20 in thestring.

Note: Even if the enumerator is defined as a hexadecimal value, adecimal value is expected as a filter.

This filter defines the requested module number.

The requested module number is specified, e.g.System.MessageStore,2,1,3,0 (module number 3 is requested).

If data is to be requested for several modules, the module numbers areconnected by a plus sign, e.g. System.MessageStore,2,1,2+3+5,0(module number 2, 3, and 5 are requested).

If the data for all modules are to be requested, or if no modules havebeen defined, the SCPErrorSource_All value can be used. It is defined inIDL File ScpDiagnosisComponent by means of the enumeratorSCPErrorSource. (This value corresponds to the string -1 in the itemstring, e.g. System.MessagStore,2,2,-1,0)

Filter diagnosis type

Rough filter classification

Source of error filter



System.MessageStore - Query of Current MessagesGeneral diagnosis item

System.MessageStore

This item is used to read out all current messages.

On generation of the item, specify which messages are to be returned.

This item is not designed to record each message; messages which areapplied only for a very short period of time are not signaled here. If youneed to record each message, use the items which also access thelogbook.

System.MessageStore,1,2,3,4 Read: yes; Write: no; Call: No

1 = Diagnosis type filter; several diagnosis types can be called upsimultaneously.

2 = Rough classification filter; several classifications can be called upsimultaneously.

3 = Error source filter; several error sources can be called upsimultaneously.

4 = Number of desired messages, 0 - all messages

For description of the parameters of the individual filters and theinstruction on how several call-ups can be made simultaneously, see"Parameter of the Diagnosis Items".

For each current message, a line is returned; i.e. if for example 3messages have been requested, the result will be only one line if there isonly one current message.

The result can also be 0 lines if there is no current message.

The number of columns of a line depends on the diagnosis type of themessage.

A line has always a minimum of 9 columns which are defined as follows.

Because every message can be unambiguously assigned to onediagnosis type, one rough classification and one error source, thereturned results are unambiguously as well, i.e. there is no more OR linkin the result.

Column Type Description

0 LONG Diagnosis type of this message, also describes the data from column 9

1 LONG Rough classification of this message

2 LONG Error source of this message

3 BSTR Error text with resolved wildcards

4 DOUBLE Time stamp of the message with date and time of the Variant Time type. Thetime is given in Coordinated Universal Time (UTC).

5 LONG Time index for sorting messages with the same time stamp according to thetime they occurred.When two messages have the same time index, the message whose timeindex is smaller has been received first. If both have the same index, they havebeen received at the same time, or the difference cannot be identified.

6 BOOL TRUE - Data for analysis of criteria availableFALSE - No data for analysis of criteria available

7 BOOL TRUE - Information for additional diagnosis available (can be called up withSystem.MessageStoreEx

FALSE - No information for additional diagnosis available

Identifier

Description

Note

Item Syntax

Format of result




8 BSTR Unambiguous message ID.By means of this ID and the type of diagnosis, messages can beunambiguously differentiated even if several messages have the samemessage text. Is used as input parameter of additional diagnosis commands.

In dependence on the type of diagnosis (0. column), the followingcolumns differ from each other.

If SCPDiagnosisType_MTX is returned as type of diagnosis, the followingcolumns are defined as follows:


9 BSTR Error, message or notification number

10 LONG Fine classificationMessage class (device-specific, ~ 20 with BRIC)

11 BSTR Message class as text

12 LONG Channel, or identified as independent of a channel

13 BSTR Channel name (configuration date)

If SCPDiagnosisType_ProVi is returned as type of diagnosis, the followingcolumns are defined as follows:


9 LONG Message number

10 LONG Error category as number

11 LONG Message group as number

System.MessageStoreEx - Determine ExtendedDiagnosis Data

General diagnosis item

System.MessageStoreEx

The item supplies more data on a message which has been called up withSystem.MessageStore. The type of data depends on the type ofdiagnosis.

System.MessageStoreEx,1,2 Read: yes; Write: no; Call: No

1 = Type of diagnosis, value which has been returned in column 0 withSystem.MessageStore

2 = Unambiguous message ID, value which has been returned in column7 with System.MessageStore

See "Parameter of the Diagnosis Items" for description of the diagnosiserror.

The result has always one line.


In this case, there is no uniformly defined part of the result.

In dependence on the type of diagnosis (1. parameter of the item), thefollowing columns differ from each other.

Additional columns of an MTXmessage

Additional columns of a ProVimessage

Identifier

Description

Item Syntax

Format of result



If SCPDiagnosisType_MTX is returned as type of diagnosis, the columnsare defined as follows:


0 BSTR Cause text

1 BSTR Remedy text

If SCPDiagnosisType_ProVi is returned as type of diagnosis, the columnsare defined as follows:


0 BSTR Cause text from the message integrator

1 BSTR Remedy text from the message integrator

2 BSTR User notes from the message integrator

3 BSTR HTML link from the message integrator

4 LONG Type of POE in which the message is programmed.1 = Program, 2 = function block

5 BSTR Name of POE in which the message is programmed.

6 LONG Type of detail in which the message is programmed1 = implementation, 2 = action, 3 = transition

7 BSTR Name of the detail, empty for implementation

8 LONG Network number or line in which the message is programmed.

9 BSTR Variable which is used as assignment for the ProVi message

10 BSTR POE instances name

System.MessageStatus – Queries whether Messageshave changed


System.MessageStatus

This process is used to query whether certain messages are pending,whether they have changed, or whether new messages have beenreceived.


This item is not designed to record each message; messages which arepending only for a very short period of time are not signaled here. If youneed to record each message, use the items which also access thelogbook.

System.MessageStatus,1,2,3 Read: yes; Write: no; Call: No





The result always has 1 line with 3 columns.

Columns of an MTX message

Columns of a ProVi message

Identifier

Description

Note

Item Syntax

Format of result




0 BOOL TRUE - There are messages pendingFALSE - There are no messages pending

1 DOUBLE Time stamp of the message arrived last, with date and time of the Variant Timetype. The time is given in Coordinated Universal Time (UTC).

2 DOUBLE Time stamp of the message arrived last, with date and time of the Variant Timetype. The time is given in Coordinated Universal Time (UTC).

How can these results be interpreted?

• If messages are pending: Query of column 0.

• If the first message arrives or the last message goes back to normal:Cyclical logon of this item; when callback method is called up, querycolumn 0.

• If messages have changed: Cyclical logon of this item; when callbackmethod is called up, the messages have changed.

• If there are new messages: Marking of the arrival time stamp.Cyclical logon of this item; when the callback method has been calledup and the arrival time stamp has changed, new messages have beenreceived since the last query.

System.ErrorStatus - Query whether Errors HaveChanged


System.ErrorStatus

This process is used to query whether errors are pending, whether theyhave changed, or whether new errors have been signaled.

On generation of the item, specify which errors are to be returned.

This item is not designed to record each message; messages which areapplied only for a very short period of time are not signaled here. If youneed to record each message, use the items which also access thelogbook.

System.ErrorStatus,1,2 Read: yes; Write: no; Call: No




see "System.MessageStatus – Queries whether Messages havechanged".

Identifier

Description

Note

Item Syntax

Format of result



System.InfoStatus - Query whether Notifications HaveChanged


System.InfoStatus

see "System.ErrorStatus - Query whether Errors Have Changed".

The items differ in that this item does not relate to errors but tonotifications.

System.WarningStatus - Query whether Warnings HaveChanged


System.WarningStatus


The items differ in that this item does not relate to errors but to warnings.

System.StartupStatus - Query whether Startup StatusHas Changed


System.StartupStatus


The items differ in that this item does not relate to errors but to startupstatus.

System.ErrorStatus - Query whether Setup Status HasChanged


System.SetupStatus


The items differ in that this item does not relate to errors but to setupdiagnoses.

System.MessageReset - Resets the Currently PendingMessages


System.MessageReset

This item is used to reset currently pending messages.

The item does not have parameters of its own. In 'Write', specify whichmessages are to be reset.

System.MessageReset Read: no; Write: yes; Call: No

The call-up has only one line and 3 columns. It is used to define themessages which are to be reset.

The data can be transferred in the form of a string or a number. However,a link of several error sources can only be transferred in the form of astring.

Identifier

Description

Identifier

Description

Identifier

Description

Identifier

Description

Identifier

Description

Item Syntax

Format of the call-up




0 LONG (BSTR) Diagnosis type filter; several diagnosis types can be reset simultaneously.

1 LONG (BSTR) Rough classification filter; several classifications can be reset simultaneously.

2 LONG (BSTR) Error source filter; several error sources can be called up simultaneously.


System.LogbookStore - Reads out the Data of theLogbook


System.LogbookStore

The item is used to read out the messages from the logbook.


Each entry in the logbook is identified unambiguously by the diagnosistype and a MessageID.

If for example messages until time stamp X and then from time stamp Xare called up, both calls will yield messages with the exact time stamp X.However, the double messages can be identified through type ofdiagnosis and MessageID.

This applies analogously to messages which are back to normal. Theyare then returned once more with a more recent time stamp. Throughtype of diagnosis and MessageID, it is once more evident to whichincoming message they belong.

System.LogbookStore,1,2,3,4,5,6 Read: yes; Write: no; Call: No

1 = Control filter; -1: the messages of all configured controls of thislogbook are returned. If only the data of a certain control are required, itsGUID can be specified here.




5 = Time stamp from which the messages are to be returned; messagewith date and time of the Variant Time type. The time is given inCoordinated Universal Time (UTC).All messages whose time stamp is more recent or identical are supplied.If 0 is specified here, all messages are returned whose time stamp isolder than or identical with parameter 6. In this case, there is no top limit.

6 = Time stamp up to which the messages are to be returned; messagewith date and time of the Variant Time type. The time is given inCoordinated Universal Time (UTC).All messages whose time stamp is older or identical are supplied.If 0 is specified here, all messages are returned whose time stamp ismore recent than or identical with parameter 5. In this case, there is notop limit.


Identifier

Description

Note

Item Syntax



For each current message, a line is returned; i.e. if for example 3messages have been requested, the result will be only one line if there isonly one current message.

The result can also be 0 lines if there is no current message.


A line has always a minimum of 10 columns which are defined as follows.

Because every message can be unambiguously assigned to onediagnosis type, one rough classification and one error source, thereturned results are unambiguously as well, i.e. there is no more OR linkin the result.


0 BSTR Device name

1 BSTR Device GUID

2 LONG Diagnosis type of this message, also describes the data from column 10

3 LONG Rough classification of this message

4 LONG Error source of this message

5 BSTR Error text with resolved wildcards

6 DOUBLE Time stamp of the message with date and time of the Variant Time type. Thetime is given in Coordinated Universal Time (UTC).

7 BOOL TRUE - The message has arrivedFALSE - The message is back to normal

8 BOOL TRUE - Information for additional diagnosis available (can be called up withSystem.LogbookStoreEx

FALSE - No information for additional diagnosis available

9 BSTR Unambiguous message ID.By means of this ID and the type of diagnosis, messages can beunambiguously differentiated, for example to assign a back-to-normal messageto the arriving message. Is used as an input parameter for further diagnosiscommands.

In dependence on the type of diagnosis (2. column), the followingcolumns differ from each other.

If SCPDiagnosisType_MTX is returned as type of diagnosis, the followingcolumns are defined as follows:


10 BSTR Error, message or notification number

11 LONG Fine classificationMessage class (device-specific, ~ 20 with BRIC)

12 BSTR Message class as text

13 LONG Channel, or identified as independent of a channel

14 BSTR Channel name (configuration date)

If SCPDiagnosisType_ProVi is returned as type of diagnosis, the followingcolumns are defined as follows:


10 LONG Message number

11 LONG Error category as number

12 LONG Message group as number

Format of result

Additional columns of an MTXmessage

Additional columns of a ProVimessage



System.LogbookStoreEx - Reads out the Additional Dataof a Logbook Entry


System.LogbookStoreEx

The item supplies more data on a logbook entry which has been called upwith System.LogbookStore. The type of data depends on the type ofdiagnosis.

System.LogbookStoreEx,1,2 Read: yes; Write: no; Call: No

1 = Type of diagnosis, value which has been returned in column 0 withSystem.LogbookStore

2 = Unambiguous message ID, value which has been returned in column7 with System.LogbookStore

See "Parameter of the Diagnosis Items" for description of the diagnosiserror.

The result has always one line.


In this case, there is no uniformly defined part of the result.

In dependence on the type of diagnosis (1. parameter of the item), thefollowing columns differ from each other.

If SCPDiagnosisType_MTX is returned as type of diagnosis, the columnsare defined as follows:


0 BSTR Cause text

1 BSTR Remedy text

If SCPDiagnosisType_ProVi is returned as type of diagnosis, the columnsare defined as follows:


0 BSTR Cause text from the message integrator (presently still empty)

1 BSTR Remedy text from the message integrator (presently still empty)

2 BSTR User notes from the message integrator (presently still empty)

3 BSTR HTML link from the message integrator (presently still empty)

4 LONG Type of POE in which the message is programmed.1 = Program, 2 = function block

5 BSTR Name of POE in which the message is programmed.

6 LONG Type of detail in which the message is programmed1 = implementation, 2 = action, 3 = transition

7 BSTR Name of the detail, empty for implementation

8 LONG Network number or line in which the message is programmed.

9 BSTR Variable which is used as assignment for the ProVi message

10 BSTR POE instances name

Identifier

Description

Item Syntax

Format of result

Columns of an MTX message

Columns of a ProVi message



System.LogbookClear - Cancels Entries in the LogbookGeneral diagnosis item

System.LogbookClear

This item is used to cancel entries in the logbook

The item does not have parameters of its own. In 'Write', specify whichentries are to be cancelled.

When time ranges are specified, it is possible that the arrival entry of amessage is cancelled but its back-to-normal entry remains, or vice versa.

System.LogbookClear Read: no; Write: yes; Call: No

The call-up has only one line and 6 columns. It is used to define whichentries in the logbook are to be cancelled.

The data can be transferred in the form of a string or a number. However,a link of several error sources can only be transferred in the form of astring.


0 LONG (BSTR) Control filter; -1 all configured controls of this logbook; otherwise, GUID of thecontrol whose messages are to be cancelled.

1 LONG (BSTR) Diagnosis type filter; several diagnosis types can be cancelled simultaneously.

2 LONG (BSTR) Rough classification filter; several classifications can be cancelledsimultaneously.

3 LONG (BSTR) Error source filter; several error sources can be called up simultaneously.

4 LONG (BSTR) 5 = Time stamp from which the entries are to be cancelled; message with dateand time of the Variant Time type. The time is given in Coordinated UniversalTime (UTC).All entries whose time stamp is more recent or identical are cancelled.If 0 is specified here, all entries are cancelled whose time stamp is older thanor identical with parameter 4. In this case, there is no top limit.

Identifier

Description

Note

Item Syntax

Format of the call-up




5 DOUBLE(BSTR)

5 = Time stamp up to which the entries are to be cancelled; message with dateand time of the Variant Time type. The time is given in Coordinated UniversalTime (UTC).All entries whose time stamp is older or identical are cancelled.If 0 is specified here, all entries are cancelled whose time stamp is more recentthan or identical with parameter 3. In this case, there is no top limit.


System.LogbookDevices - Specifies the Controls whichare Logged in the Logbook


System.LogbookDevices

This items supplies the logic devices which log their messages in thelogbook.

System.LogbookDevices Read: yes; Write: no; Call: No

The result supplies one line for each logic device.

In each line, 2 columns are returned.


0 BSTR Name of the logic device

1 BSTR GUID of the logic device

2.2 Language Switching

The System.SupportedLanguages item supplies a list of supportedlanguages. Reading the item System.Language supplies the activelanguage; to switch the language, write the item.

Identifier System.SupportedLanguages List of supported languages

Description The System.SupportedLanguages item is used to specify the supported languages. Reading of theitem will supply the list of supported languages.

Item Syntax System.SupportedLanguages Read: yes; Write: no; Call: no

Parameter: none

Specification of the supported languages

Example SCP-Item System.SupportedLanguages

Access Read

Result Row/Col 0 1

0 049 (VT_BSTR) German (VT_BSTR)

1 044 (VT_BSTR) English (VT_BSTR)

2 031 (VT_BSTR) Dutch (VT_BSTR)

3 033 (VT_BSTR) French (VT_BSTR)

Identifier

Description

Item Syntax

Format of result



4 034 (VT_BSTR) Spanish (VT_BSTR)

5 039 (VT_BSTR) Italian (VT_BSTR)

Identifier System.Language Active language

Description Use the item System.Language to specify the currently set language or to switch languages.

Item syntax System.Language Read: yes; Write: yes; Call: no

Parameter : none

Specification of the active language

Example SCP item System. Language

Access Read

Result Row/Col 0 1


Language switching

Example SCP item System. Language

Access Write

WriteData Row/Col 0 1




2.3 Archives

Archives are used to save and restore data of the MTX kernel. Thearchive may either be situated in the file system of the control kernel (incl.NFS mounted file systems) or in the Windows file system.

Identifier System.Archive Archive Function

Description The System.Archive item is used to generate an archive with the data of the control, or to read anexisting archive.

Writing initiates the archiving process. The following information is required for writing the item:

• Mode (reading in the archive or generating the archive, and desired partial archives)

• Name of the archive

• Name of the Log file

The enumerator LDX_TarMode indicates whether the archive is being generated or whether anexisting archive is read in. Furthermore, this enumerator is used to specify the partial archives.

LDX_TAR_MODE_CREATE_C // generate new archive,LDX_TAR_MODE_EXTRACT_C // read in existing archive,LDX_TAR_MODE_ALL_C // complete,LDX_TAR_MODE_RAM_C // RAM file system,LDX_TAR_MODE_USRFEP_C // User FEPROM,LDX_TAR_MODE_MACODA_C // MACODA,LDX_TAR_MODE_TOOLTABLE_C // Tool tables,LDX_TAR_MODE_TOOLTAB1_C // 1. tool table (XML),LDX_TAR_MODE_TOOLTAB2_C // 2. tool table (XML),LDX_TAR_MODE_DATAMODULES_C // remanent data of the PLC,LDX_TAR_MODE_MARKERS_C // remanent data of the PLC,LDX_TAR_MODE_CPLVARS_C // permanent CPL variables,LDX_TAR_MODE_SYSTEMDATA_C // System data

Significant failures causing abortion of the function (e.g. not enough memory to read in the archive)are described in Section 5.8. In this case, Write will cause an error.

The writing process is finished only after archiving is completed. The errors logged during archivingcan be identified by reading the System.ArchiveLog item.

Item syntax System.Archive Read: no; Write: yes; Call: no

Parameter : none

Generation of a complete archive of the name /mnt/complete.tar

Example SCP item System.Archive

Access Write

WriteData Row/Col 0 1 2

0 /mnt/complete.tar /mnt/complete.tac LDX_TAR_MODE_CREATE_C |LDX_TAR_MODE_ALL_C

Reading in all data of the RAM file system from the /mnt/complete.tar archive

Example SCP item System.Archive

Access Write


0 /mnt/complete.tar /mnt/complete.tac LDX_TAR_MODE_EXTRACT_C |LDX_TAR_MODE_RAM_C



Identifier System.ArchiveLog Error evaluation after archiving

Description The System.ArchiveLog item is used to determine errors occurred while a new archive isgenerated or an existing archive is read in.

Reading the item supplies a list of the archived files or partial archives. Each list entry consists of aname, a respective error code and a plain text in English language explaining the error.

Any errors are coded by means of the enumerator LDX_TarLogError. It can have the followingvalues:

LDX_TAR_LOG_OK_C // no error occurred,LDX_TAR_LOG_NOT_YET_PROCESSED_C // file not yet processed,LDX_TAR_LOG_STAT_FAILED_C // stat failed,LDX_TAR_LOG_SKIPPED_C // file skipped (no error),LDX_TAR_LOG_PATH_NOT_OPENED_C // error on opening of directory,LDX_TAR_LOG_READING_C // error on reading the file,LDX_TAR_LOG_EACCESS_C // Access to file not possible,LDX_TAR_LOG_EEXIST_C // file exists,LDX_TAR_LOG_ENOENT_C // file does not exist,LDX_TAR_LOG_ENOMEM_C // no memory available,LDX_TAR_LOG_EROFS_C // read only file system,LDX_TAR_LOG_MODE_DIFF_C // different protection,LDX_TAR_LOG_SIZE_DIFF_C // different size,LDX_TAR_LOG_MTIME_DIFF_C // different date,LDX_TAR_LOG_OTHER_DIFF_C // other differences,LDX_TAR_LOG_FILE_DATA_DIFF_C // different file dates,LDX_TAR_LOG_TIME_MODE_C // protection/time not restored,LDX_TAR_LOG_MKDIR_FAILED_C // error on making of directory,LDX_TAR_LOG_ERR_UNKNOWN_C // unknown error (-> WERA),LDX_TAR_LOG_LOADING_MACODA_C // error on loading MACODA,LDX_TAR_LOG_LOADING_TABLE_C // error on loading of tables,LDX_TAR_LOG_CORRUPTED_C // file corrupted,LDX_TAR_LOG_WRITE_ENABLED_C // write protect cancelled,LDX_TAR_LOG_DATAMODULES_C // error on loading the PLC data,LDX_TAR_LOG_MARKERS_C // error on loading the PLC data,LDX_TAR_LOG_CPLVARS_C // error on loading the CPL variables,LDX_TAR_LOG_RAMFS_NOTFOUND_C // RAM file system not found in the archive,LDX_TAR_LOG_USRFEPFS_NOTFOUND_C // User FEPROM not found in the archive,LDX_TAR_LOG_MACODA_NOTFOUND_C // MACODA not found in the archive,LDX_TAR_LOG_TABLE_NOTFOUND_C // tables not found in the archive,LDX_TAR_LOG_DATAMODULES_NOTFOUND_C // remanent PLC data not found,LDX_TAR_LOG_MARKERS_NOTFOUND_C // remanent PLC data not found,LDX_TAR_LOG_CPLVARS_NOTFOUND_C // permanent CPL variables not found,LDX_TAR_LOG_SYSTEMDATA_NOTFOUND_C // system data not found,LDX_TAR_LOG_PLCSTATE_RUN_C // PLC is not in STOP status,LDX_TAR_LOG_SYSTEMDATA_C // error during transfer of system data

Item syntax System.ArchiveLog Read: yes; Write: no; Call: no

Parameter : none



Determination of the errors occurred during the last archiving

Example SCP item System.ArchiveLog

Access Read

Result Row/Col 0 1 2

0 / -- 0 o.k. LDX_TAR_LOG_OK_C

1 /usr/ -- 0 o.k. LDX_TAR_LOG_OK_C

2 /diag/ -- 0 o.k. LDX_TAR_LOG_OK_C

...

N-1 /database/K4 -- 0 o.k. LDX_TAR_LOG_OK_C

N /database/K5 -- 0 o.k. LDX_TAR_LOG_OK_C

Identifier System.ArchiveWin Archiving (in the Windows file system)

Description The System.ArchiveWin item is identical to System.Archive, except that archive as well as log fileare situated in the Windows file system.

See System.Archive for a description.

Item syntax System.ArchiveWin Read: no; Write: yes; Call: no

Parameter : none

Generation of a complete archive of the name c:\pnc\pncosa\all.tar

Example SCP item System.ArchiveWin

Access Write


0 c:\pnc\pncosa\all.tar

(VT_BSTR)

c:\pnc\pncosa\all.tac(VT_BSTR)

LDX_TAR_MODE_CREATE_C |LDX_TAR_MODE_ALL_C

(VT_I4)

Identifier System.ArchiveWinLog Error evaluation after archiving

Description The function of the System.ArchiveWinLog item is identical to that of the System.ArchiveLog item.It supplies the errors occurred during archiving to the Windows file system.

See System.ArchiveWin for a description.

Item syntax System.ArchiveWinLog Read: yes; Write: no; Call: no

Parameter : none



Determination of the errors occurred during the last archiving

Example SCP item System.ArchiveWinLog

Access Read


0 / -- 0 o.k. LDX_TAR_LOG_OK_C

1 /usr/ -- 0 o.k. LDX_TAR_LOG_OK_C

2 /diag/ -- 0 o.k. LDX_TAR_LOG_OK_C

...

N-1 /database/K4 -- 0 o.k. LDX_TAR_LOG_OK_C

N /database/K5 -- 0 o.k. LDX_TAR_LOG_OK_C

2.4 Time of the Day

The System.SystemTime SCP item supplies the current time of the day.This item can be written for synchronization of clocks.

Identifier System.SystemTime Time of the day (UTC)

Description The System.SystemTime item supplies the current time of the day. This item can be written to setthe clock.

Item syntax System.SystemTime Read: yes; Write: yes; Call: no

Parameter : none

Example SCP item System.SystemTime

Access Read

Result Row/Col 0

0 03.03.03 11:50:12 (VT_DATE)



2.5 Time Zone

The System.TimeZone SCP item supplies the settings for the time zone.The item can be written to set the time zone.

Identifier System.TimeZone Setting the time zone

Description The System.TimeZone item supplies the settings for the time zone. It can be read and written.

Item syntax System.TimeZone Read: yes; Write: yes; Call: no

Parameter : none

Example SCP item System.TimeZone

Access Write

Result Row/Col 0

0 "MEZ" (VT_BSTR) // Name of the time zone for standard time

1 -3600 (VT_I4) // Standard time at 60 min. east of Greenwich

2 "MESZ" (VT_BSTR) // Name of the time zone for daylight saving time

3 -7200 (VT_I4) // Daylight saving time at 120 min. east of Greenwich

4 0x00030500 (VT_INT4)// Start of daylight saving time on Sunday (00), in the 5. week (05) in March (03)

5 7200 (VT_I4) // Day of time change, starting at Midnight

6 0x000a0500 (VT_INT4)// End of daylight saving time on Sunday (00), in the 5. week (05) in October (0a)

7 10800 (VT_I4) // Day of time change, starting at Midnight

2.6 Software Versions

The Items System.MainReleases, System.SubsytemReleases andSystem.PcReleases supply information on software versions. Thisinformation is also supplied for software components in the control kerneland also for software components under Windows.

• Main releases

• Sub-system releases

• Windows software components: ncstyp3.dll, libctyp3.dll, tsvtyp3.dll,FIS, Logical Device MTX etc.

Note: Other information on software versions, e.g. software versionof the PLC user program, or software version of the SCPframework must be made available by the other devicecomponents or by the SCP framework.



Identifier System.MainReleases General software versions

Description The System.MainReleases item supplies version data on the general software version of the MTXkernel including a copyright message (version of the basis software and the extensions providedby the customer).

Item syntax System.MainReleases Read: yes; Write: no; Call: no

Parameter : none

Example SCP item System.MainReleases

Access Read

Result Row/Col 0 1

0 sys Release 100.0.3, 10-03-03 (VT_BSTR)

(C) Copyright Bosch Rexroth AG 1992 - 2003(VT_BSTR)

1 kns Release 100.0.3, 10-03-03 (VT_BSTR)


2 knb Release 100.0.3, 10-03-03 (VT_BSTR)


Identifier System.SubsystemReleases Version of the subsystems

Description The System.SubsystemReleases item supplies version data on software versions of thesubsystems in the MTX kernel. For each subsystem, the following data is supplied:

• name of the subsystem• version numbers (main release, release, sub-release, and patch release)• Time stamp (UTC)

Item syntax System.SubsystemReleases Read: yes; Write: no; Call: no

Parameter : none

Example SCP item System.SubsystemReleases

Access Read


0 cpn 100.1.2.0 10.03.03 23:49:12 (VT_DATE)

1 pxr 100.1.2.0 10.03.03 23:50:38 (VT_DATE)

2 ncb 100.1.2.0 10.03.03 23:50:58 (VT_DATE)

...

N mis 100.1.2.0 10.03.03 23:58:49 (VT_DATE)



Identifier System.PcReleases Version of the Windows components

Description This item supplies version data on the Windows software components providing thecommunication interface to the MTX kernel under Windows. This comprises the NCS interface(ncstyp3.dll), text administration (tsvtyp3.dll), the logical device MTX (SCPBricDevice.dll,SCPBricComponent.dll) and FIS (FisServer.dll). For each component, the following data issupplied:

• name of the subsystem• release string with main release, release, sub-release and patch release• Time stamp (UTC)

Item syntax System.PcReleases Read: yes; Write: no; Call: no

Parameter : none

Example SCP item System.PcReleases

Access Read


0 ncstyp3.dll(VT_BSTR)

100.0.3.0 (VT_BSTR) 10.03.03 23:51:12 (VT_DATE)

1 tsvtyp3.dll(VT_BSTR)

100.0.3.0 (VT_BSTR) 10.03.03 23:51:38 (VT_DATE)

2 libctyp3.dll(VT_BSTR)

100.0.3.0 (VT_BSTR) 10.03.03 23:51:58 (VT_DATE)

...

N Scpbriccomponent.dll (VT_BSTR)

100.0.3.0 (VT_BSTR) 10.03.03 23:52:49 (VT_DATE)

OPC Interface NC Items 3-1


3 NC Items

3.1 General NC Items

Identifier NC.ConnectionQuality Connection status

Description The NC.ConnectionQuality item supplies the current connection status (good/uncertain/bad). TheLDX_ConnectionQuality enumerator is available for evaluation of the supplied connection and canaccept the following values:

LDXConnectionQualityBad // no connection to the MTX kernel,LDXConnectionQualityUncertain // connection to the MTX kernel exists but

// no optimum communication,LDXConnectionQualityGood // connection to the MTX kernel exists

Item syntax NC.ConnectionState Read: yes; Write: no; Call: no

Parameter : none

Identifier NC.NofChannels No. of channels of the NC

Description The NC.NofChannels items is used to read the number of channels.

Item syntax NC.NofChannels Read: yes; Write: no; Call: no

Parameter : none

Example SCP item NC.NofChannels

Access Read

Result Row/Col 0

0 4 (VT_I4)

Identifier NC.SercosPhase Communication Mode

Description Item NC.SercosPhase is used to read and write the SERCOS phase. Writing the item caused aphase switching. The following data was transferred during writing:

• Target phase in which should be switched.

• Reset ZK1 Error

• Execute download of .scs files in phase 2.

• Execute download of .scs files in phase 3.

Item syntax NC.SercosPhase Read: yes; Write: yes; Call: no

Parameter : none

Switching in SERCOS phase 4 with resetting the ZK1 error and downloading the scs files.

Example SCP item NC.SercosPhase

Access Write

WriteData Row/Col 0 1 2 3

0 // Target phase4 (VT_I4)

// Reset ZK1TRUE (VT_BOOL)



3-2 NC Items OPC Interface


3.2 Status Information

Identifier NC.WaitingStates System waiting state

Description The NC.WaitingStates indicates the system waiting state. It is a compound signal over allchannels.

For waiting states, the LDX_McoWaitingState enumerator is available. This enumeration type canhave the following values:

LDX_McoDwellTime_C // dwell time,LDX_McoAuxiliaryFunction_C // Auxiliary function requiring acknowledgment,LDX_McoBlockTransferInhibit_C // Block transfer lock,LDX_McoChannelFeedrate0_C // Channel feedrate equals0,LDX_McoProgramStop_C // Program stop with M0/M1,LDX_McoFeedHold_C // Feed hold in the channel,LDX_McoFeedInhibit_C // Feed inhibit in the channel, or

// a channel axis,LDX_McoCustomerStop_C // Customer-specified

// block transfer lock,LDX_McoSynchronizedMovementStop_C // Synchronized movement

// stop between channels// (ASTOP, ...)

,LDX_McoWaitingForAxisTransfer_C // Waiting for axis during axis// transfer (G511)

,LDX_McoWaitingForPermanentVariable_C // Waiting for permanent variable// (WPV)

,LDX_McoWaitingForIFSignalActive_C // Waiting for interface signal at the// active moment in time (WAITA, ...)

,LDX_McoWaitingForIFSignalPreparation_C // Waiting for interface signal// (WAIT(IC...)) or for a defined// period of time// (WAIT(,TIME%)) in the// block preparation

,LDX_McoMotionCrontrolDataService_C // Motion Control data service// (MCODS(...))

Item syntax NC.WaitingStates Read: yes; Write: no; Call: no

Parameter : none

Example SCP item NC.WaitingStates

Access Read

Result Row/Col 0

0 LDX_McoFeedHold_C (VT_I4) // Feed hold

Identifier NC.DryRunMode Total block

Description The NC.DryRunMode item indicates the status of the total block.

Item syntax NC.DryRunMode Read: yes; Write: no; Call: no

Parameter : none



Example SCP item NC.DryRunMode

Access Read

Result Row/Col 0

0 TRUE (VT_BOOL)

Identifier NC.BitInterface Inputs and outputs of the bit interface

Description The NC.BitInterface item is used to access the inputs and outputs of the bit interface. In addition tothe current state of the inputs and outputs, a description in text form and the current signaldesignation is supplied. Parameters specify the type of interface (global interface, channelinterface, axis interface, spindle interface) as well as the desired instance (channel number, axisnumber, spindle number).

The number of supplied entries varies according to the interface range which has been called up.The first line of the read data supplies the number of outputs and inputs. The other lines comprisethe PLC outputs, followed by the PLC inputs.

The signal descriptions are supplied in dependence on the preset language.

To specify the interface range, use the LDX_AcblfType enumerator:

LDX_ACB_IFTYPE_CHAN_C // Channel interface,LDX_ACB_IFTYPE_AXIS_C // Axis interface,LDX_ACB_IFTYPE_SPINDLE_C // Spindle interface,LDX_ACB_IFTYPE_GENERAL_C // Global Interface

Item syntax NC.BitInterface,(1),(2) Read: yes; Write: no; Call: no

(1) = type Integer format, interface range,

refer to LDX_AcbIfType enumerator

(2) = index Integer format, needed for channel, axis, or spindleinterface

Calling the channel interface of channel 3

Example SCP item NC.BitInterface,0,3

Access Read


0 112 (VT_I4) // Number of PLCoutputs

112 (VT_I4) // Number of PLCinputs

1 Mode selection Bit0 (VT_BSTR) qCh_OpModeSel_00 (VT_BSTR) 1 (VT_I4)




: ..... (VT_BSTR) ..... (VT_BSTR) ... (VT_I4)

8 Operating mode specified by PLC(VT_BSTR)

qCh_OpModePLC (VT_BSTR) 0 (VT_I4)

9 Automatic restart (VT_BSTR) qCh_Restart (VT_BSTR) 1 (VT_I4)

10 NC-Start (VT_BSTR) qCh_NCStart (VT_BSTR) 0 (VT_I4)




112 (VT_BSTR) qCh_res_13_7 (VT_BSTR) 0 (VT_I4)

113 Active operation mode Bit0(VT_BSTR)

iCh_OpMode_00" (VT_BSTR) 1 (VT_I4)


iCh_OpMode_01 (VT_BSTR) 0 (VT_I4)






122 Test mode (VT_BSTR) iCh_DryRun (VT_BSTR) 1 (VT_I4)


224 (VT_BSTR) iCh_res_27_7 (VT_BSTR) 0 (VT_I4)

3.3 General XML Functions

Access to tables, system data and configuration data of the MTX is XML-based. A number of general functions are available:

• for determination of the schemata used in the kernel,

• for querying a list of root elements, and

• for determination of extensions and Top Level Schema in relation to aroot element.

Identifier NC.XmlSchemaList List of schemata

Description The NC.XmlSchemaList items supplies the list of all schemata used in the kernel. For each listentry, the full path, name and extension of the schema is supplied. Furthermore, the date (timestamp) of the last change (UTC!) is given.

It is possible to enter any number of list entries. It may vary between software versions.

Item syntax NC.XmlSchemaList Read: yes; Write: no; Call: no

Parameter : none

Identification of the schemata used in the kernel

Example SCP item NC.XmlSchemaList

Access Read

Result Row/Col 0 1

0 /feprom/schemas/basic_ty.xsd (VT_BSTR) 04.04.04 16:26:12 (VT_DATE)

1 /feprom/schemas/dct_sd.xsd (VT_BSTR) 04.04.04 17:26:12 (VT_DATE)

2 /feprom/schemas/dct_du.xsd (VT_BSTR) 04.04.04 18:26:12 (VT_DATE)

3 /feprom/schemas/pmt_sd.xsd (VT_BSTR) 04.04.04 19:26:12 (VT_DATE)

4 /usrfep/schemas/pmt_du.xsd (VT_BSTR) 04.04.04 20:26:12 (VT_DATE)

5 /feprom/schemas/zot_sd.xsd (VT_BSTR) 04.04.04 21:26:12 (VT_DATE)

...

N /feprom/schemas/tool_ty.xsd (VT_BSTR) 04.04.04 23:26:12 (VT_DATE)



Identifier NC.XmlRootElementList List of root elements

Description The NC.XmlRootElementList item supplies a list of all root elements in relation to the preset XMLdata class (e.g. file-based table, database-based table, configuration data etc.). The XML dataclass is preset as a parameter when the item is instantiated.

To specify the XML data class, use the LDX_XmlDataClass enumerator. The XML data class of aroot element is defined by means of the 'Class' attribute in the respective schema. The followingassignment between the value of the Class attribute and the XML data class applies:

LDX_XML_DATA_CLASS_UNKNOWN_C // otherwise,LDX_XML_DATA_CLASS_CFG_C // XML data class "CFG“,LDX_XML_DATA_CLASS_DBTAB_C // XML data class "DBTAB“,LDX_XML_DATA_CLASS_FILETAB_C // XML data class "FILETAB“

The number of supplied root elements varies, depending on the respective XML data type.Furthermore, it depends on the other boundary conditions, e.g. utilization of user-definable tables.

Item syntax NC.XmlRootElementList,(1) Read: yes; Write: no; Call: no

(1) = Data category -> Enumerator

Identification of the root elements for file-based tables

Example SCP item NC.XmlRootElementList,3 // 3 -> LDX_XML_DATA_CLASS_FILETAB_C

Access Read

Result Row/Col 0

0 /DCT (VT_BSTR) // Root element for D compensation tables

1 /PMT (VT_BSTR) // Root element for placement tables

2 /ZOT (VT_BSTR) // Root element for NPV tables

3 /MYT (VT_BSTR) // Root element of a user-defined table

Identifier NC.XmlRootElementInfo Information on a table type

Description The NC.XmlRootElementInfo item supplies additional information on the specified root element(table type), e.g. top level schema and extension.

The extension is relevant only for file-based tables; in other cases, no extension is supplied.

Item syntax NC.XmlRootElementInfo,(1) Read: yes; Write: no; Call: no

(1) = root element BSTR

Identification of the top level schema and the extension of NPV tables

Example SCP item NC.XmlRootElementInfo,/ZOT

Access Read

Result Row/Col 0

0 /feprom/zot_sd.xsd (VT_BSTR) // Top level schema for NPV tables

1 zot (VT_BSTR) // Extension for NPV tables



3.4 File-Based Tables

Identifier NC.XmlTable File-based table in XML format

Description The NC.XmlTable item is used to get read and write access to file-based tables. This comprises forexample zero offset tables, D compensation tables and placement tables. When creating the item,the table is specified which is to be accessed. Furthermore, the node in the table is identified bymeans of a second parameter.

On 'Read', the read data is supplied in the form of an XML string. The automation-compatibleBSTR type is used; however, the transmitted data is not in UTF8 format and are not converted toUNICODE.

On 'Write', the data is likewise transmitted in the form of an UTF8-coded XML string. On writing,the length of the XML string is limited to 4 kByte.

With NPV tables, it is furthermore possible to insert or delete columns.

To insert columns, specify when creating the item as a 2nd parameter the column where a newone should be inserted. The difference between inserting of columns and the usual function forwriting in tables is as follows: The written data contain data in XML format for the column to beinserted (1. line), as well as another line with the constants LDX_TAD_INSERT_AXIS_ZOT_C.

To delete a column, the column to be deleted is specified as 2nd parameter when the item is made.Subsequent write without data (in the 1st line) and of the constantsLDX_TAD_DELETE_AXIS_ZOT_C causes the column to be deleted.

The LDX_TadWriteMode enumerator can take the following values:

LDX_TAD_WRITE_CACHE // access via cache,LDX_TAD_INSERT_AXIS_ZOT_C // insert axis/column,LDX_TAD_INSERT_AXIS_ZOT_C // delete axis/column

See section 5.3 for a description of errors potentially occurring in connection with reading andwriting of tables.

Item syntax NC.XmlTable,(1),(2) Read: yes; Write: yes; Call: no

(1) = table name File name incl. Complete path

(2) = node in the table (optional) String in Xpath syntax

Reading the complete D compensation table / database/sample.dct

Example SCP item NC.XmlTable,/database/sample.dct

Access Read

Result Row/Col 0

0 <?xml version="1.0" encoding="UTF-8" ?>........</DCT>

Writing of a value of the D compensation table / database/sample.dct

Example SCP item NC.XmlTable,/database/sample.dct,/DCT/Corr[3]/Rough/L1

Access Write

WriteData Row/Col 0

0 <L1>2.5</L1>



Inserting a column into the NPV table / database/offsets.zot

Example SCP item NC.XmlTable, /database/offsets.zot,/ZOT/Offset/Ax[2]

Access Write

WriteData Row/Col 0

0 <Ax><Name>B</Name><Type>Lin</Type><Set><G54>5.1</G54>...</Ax>

1 LDX_TAD_INSERT_AXIS_ZOT_C

Deleting the 2nd column in the NPV table / database/offset.zot

Example SCP item NC.XmlTable, /database/offsets.zot,/ZOT/Offset/Ax[2]

Access Write

WriteData Row/Col 0

0 Empty // data is ignored

1 LDX_TAD_DELETE_AXIS_ZOT_C

Identifier NC.XmlTableEvent Event related to write access on tables

Description The NC.XmlTableEvent item is used to signal write access on the table opened in the editor. Whencreating the item, identify the table for which write access is to be signaled.

With 'Read', the data written last is supplied. Generally, the changed node is supplied in Xpathsyntax, the new data in form of an XML string (UTF8) together with a version number.

Sometimes, the changed node or the new data cannot be supplied; in this case, the complete tableor the node must be read once more.

It cannot be guaranteed that signaling will take place with all write processes. For this reason, it isnecessary to do a client-side check by means of a version number which is comprised in thedelivery. If the version numbers are consecutive, signaling will be continuous; otherwise, not allwrite accesses will be recorded, and the table must be read completely.

Errors occurring in context with this item are described in detail in Section 5.3.

Item syntax NC.XmlTableEvent,(1) Read: yes; Write: no; Call: no

(1) = table name File name incl. Complete path

Identification of write accesses to the D compensation table / database/sample.dct

Example SCP item NC.XmlTableEvent,/database/sample.dct

Access Read

Result Row/Col 0

0 213 (VT_UI4) //Version number

1 /DCT/Corr[3]/Rough/L1 (VT_BSTR) // changed node in Xpath syntax



Identifier NC.XmlTableCreate Creating tables

Description The NC.XmlTableCreate item is used to create a new table. It is created by writing the item.

See section 5.3 for a description of errors potentially occurring in connection with creating oftables.

Item syntax NC.XmlTableCreate Read: no; Write: yes; Call: no

Parameter : none

Creating the D compensation table sample.dct in the root directory by means of the template/mnt/template.dct

Example SCP item NC.XmlTableCreate

Access Write


0 /sample.dct(VT_BSTR)

/DCT (VT_BSTR) /mnt/template.dct(VT_EMPTY)

(VT_EMPTY)

Creating the axis offset table offsets1.aot in the root directory for channel 1

Example SCP item NC.XmlTableCreate

Access Write


0 /offsets1.aot(VT_BSTR)

/AOT (VT_BSTR) (VT_EMPTY) 1(VT_I4)



3.5 Database-Based Tables

Identifier NC.DbTableQuery Query for data records

Description The NC.DbTableQuery item is used to search for data records meeting a specified search criterion.The search criterion is indicated by means of parameters on initialization of the item; 2 differentformats are supported:

Specification of the search criterion in XML format:

• The root tag of the XML string is 'DBTCond'.• For the individual conditions, use the element denominators from the header of the data

record.• To specify the masks of the relevant bits in the bit masks, use the element denominators

BQ1Mask, BQ2Mask and BQ3Mask.

• The values for the bit arrays (e.g. BQ1) and the bit masks (e.g. BQ1Mask) are interpreted:- as a hexadecimal number if they start with '0x' or '0X'- as an octal number if they start with '0'- otherwise, as a decimal number.

• Boundary condition: Only the predefined tag names may be used.

• Example:<DBTCond><K1>1</K1><BQ2>1</BQ2><BQ2Mask>1</BQ2Mask></DBTCond>

Specification of the search preconditions in form of a list:

• The list contains individual preconditions all of which must be met.• The individual conditions are separated by ','.

• A normal individual condition has the following form:<Tag name><comparison operator><value> e.g.: SKQ=4711

• The following comparison operators are permissible:• "=" equal• ">" greater• ">=" greater/equal• "<" smaller• "<=" smaller/equal• "<>" unequal

• Restrictions for SKQ: Only "=" and "<>" are permissible as comparison operators.

• A bitmask individual condition has the following form:<Tag name>=<value>:<mask> e.g.: BQ1=0x307000:0xF0FF00<value> contains the value of the relevant bits<mask> contains the mask of the relevant bitsCaution: Only "=" is permissible as comparison operator!

• Values and masks are interpreted:- as a hexadecimal number if they start with '0x' or '0X'- as an octal number if they start with '0'- otherwise, as a decimal number.

• Within <value>, preceding or following spaces are not evaluated.

• If a string is to be specified in which these spaces are significant, the substring must beenclosed in inverted commas. (Example: SKQ=' ').

• To use an inverted comma in a substring enclosed in inverted commas, the character '\' mustprecede the inverted comma (example: SKQ='Achim\'s').

• Boundary condition: Only the predefined tag names may be used.

• Example:K1=1,IKQ2=3,BQ2=0x1:0x1

Subsequent reading of the item supplies a list of all data records meeting the search condition. Foreach data record, the complete header is supplied. See section 5.4 for a description of errorspotentially occurring in connection with searching of data records.

Item syntax NC.DbTableQuery,(1),...(N) Read: yes; Write: no; Call: no

(1) = root tag BSTR

(2) .. (N) VT_BSTR

XML string according to description Search condition in XML format



or Consequence of the individual condition in the form<Tag name><comparison operator><value>separated by comma.

Search condition in list form

Search condition in XML format:Searching all data records with(K1 == 1) &&(IKQ2 == 3) &&(((BQ2) & 0x00010000) == 0x00010000)

Example SCP item NC.DbTableQuery,/DBT1,<DBTCond><K1>1</K1><IKQ2>3</IKQ2><BQ2>0x10000</BQ2><BQ2Mask>0x10000</BQ2Mask></DBTCond>

Access Read

Result Row/Col 0

0 <DBT1>........</DBT1>

Note: The search condition is currently not available!

Search condition in list form:Searching all data records with(K1 == 1) &&(IKQ2 == 3) &&(((BQ2) & 0x00010000) == 0x00010000)

Example SCP item NC.DbTableQuery,/DBT1,K1=1,IKQ2=3,BQ2=1:1

Access Read

Result Row/Col 0

0 <DBT1>........</DBT1>

Identifier NC.DbTableDataRecLocked Data record of a DB table (with lock)

Description The NC.DbTableDataSetLocked item provides for read and write access to a data record. Wheninitiating the item, the desired data record is addressed (element path, sector, place). The readdata as well as the data to be written are transmitted in the form of XML strings.

By means of the element path in Xpath syntax, the table is unambiguously identified; besides, thisparameter can be used to address the data record as a whole, or only a substructure.

The addressed data record is locked by initial reading of the item. The initial write access releasesthe data record. On reduction of the item without preceding writing, the data record is releasedautomatically.

After write access, the data record can be re-locked by another read access.

See section 5.4 for a description of errors potentially occurring in connection with reading andwriting of data records.



Item syntax NC.DbTableDataRecLocked,(1),(2),(3) Read: yes; Write: yes; Call: no

(1) = element path BSTR(Xpath -> data record or substructure)

(2) = Key1 Integer format, e.g. sector

(3) = Key2 Integer format, e.g. place

Reading a locked data record with subsequent writing

Example SCP item NC.DbTableDataRecLocked,/DBT1,1,3

Access Read

Result Row/Col 0

0 XML-String (VT_BSTR, UTF8-encoded)

Writing -> results in automatic release

Access Write

Row/Col 0


Identifier NC.DbTableDataRec Data record of a DB table

Description The NC.DbTableDataRec item provides for read and write access to a data record. When initiatingthe item, the desired data record is addressed (element path, sector, place). The read data issupplied in the form of XML strings.

By means of the element path in Xpath syntax, the table is unambiguously identified; besides, thisparameter can be used to address the data record as a whole, or only a substructure.

See section 5.4 for a description of errors potentially occurring in connection with reading andwriting of data records.

Item syntax NC.DbTableDataRec,(1),(2),(3) Read: yes; Write: no; Call: no

(1) = element path BSTR(Xpath -> data record or substructure)

(2) = Key1 Integer format, e.g. sector

(3) = Key2 Integer format, e.g. place

Reading of a data record

Example SCP item NC.DbTableDataRec,/DBT1,1,1

Access Read

Result Row/Col 0




Identifier NC.DbTableEvent Event on changing of DB tables

Description The NC.DbTableEvent item is used to signal write access to a DB table, a substructure of thetable, or a data record of the table.

If only the first parameter is specified, write access to the table as a whole is signaled. When thesecond parameter is specified, for example monitoring of a sector is possible. If the third parameteris specified as well, only write access to a data record is monitored.

Read supplies the data record of the table (Key1 and Key2) changed last; this data record must beread anew after that.

It cannot be guaranteed that signaling will take place with all write processes. For this reason, it isnecessary to do a client-side check by means of a version number which is comprised in thedelivery. If the version numbers are consecutive, signaling will be continuous; otherwise, not allwrite accesses will be recorded, and the DB table must be read anew.


Item syntax NC.DbTableEvent,(1)[,(2),[(3)]] Read: yes; Write: no; Call: no

(1) = root tag BSTR

(2) = Key1 Optional, integer format, e.g. sector

(3) = Key2 Optional, integer format, e.g. place

Example SCP item NC.DbTableEvent,/DBT1,0

Access Read

Result Row/Col 0

0 213 (VT_UI4) //Version number

1 0 (VT_I2) // Key1

2 14 (VT_I2) // Key2

Identifier NC.DbTableSave Saving of data from a DB table

Description The NC.DbTableSave item is used to save data records of a DB table in an XML file. Optionally,the DB table as a whole, several data records (e.g. a complete sector of a tool table), or anindividual data record can be saved. If the XML file in question exists already, the data to be savedcan either be attached at the end, or the content of the file is deleted first.

No parameters are necessary to create the item. On subsequent writing, the files will be suppliedwith the following information.

Name of the XML file (incl. path and extension)

root tag (unambiguously identifies the DB table)

Attaching yes/no (attaching to an existing file, or overwrite)

Key1 (optional)

Key2 (optional)

It is possible to save specifically only the data records of one sector (Key1) or specifically one datarecord (Key1 and Key2). If neither Key1 nor Key2 are specified, the DB table is saved as a whole.




Item syntax NC.DbTableSave Read: no; Write: yes; Call: no

Parameter : none

Saving of a complete DB table in the XML file /database/dbt1.xmlwhile a potentially existing file is overwritten

Example SCP item NC.DbTableSave

Access Write


0 /database/dbt1.xml(VT_BSTR)

/DBT1 (VT_BSTR) 0 (VT_I4)

Attachment of the data records from sector2 to the existing XML file /mnt/tools.xml


Access Write


0 /mnt/tools.xml(VT_BSTR)

/DBT1 (VT_BSTR) 1 (VT_I4) 2 (VT_I4)

Attachment of a single data record to the existing XML file /mnt/tools.xml


Access Write

WriteData Row/Col 0 1 2 3 4

0 /mnt/tools.xml

(VT_BSTR)

/DBT1(VT_BSTR)

1 (VT_I4) 3 (VT_I4) 2 (VT_I4)



Identifier NC.DbTableLoad Reading in of data from a DB table

Description The NC.DbTableLoad item is used to read in data records of a DB table from an XML file. Theread-in data records must already be available in a DB table, i.e. no new data records are created.

Optionally, all data records from an XML file are read in, i.e. all data records in which the field Key1has a specified value (e.g. all data records of a sector of a tool table), or an individual data recordspecified by a value pair Key1, Key2.

No parameters are necessary to create the item. On subsequent writing, the files will be suppliedwith the following information.

Name of the file from which data is read in (incl. path and extension)

root tag (unambiguously identifies the DB table)

Key1 (optional)

Key2 (optional)

If neither Key1 nor Key2 is specified, all data records from the XML file are read in. Otherwise,several data records specified by Key1 are read in (e.g. only the data records of a sector), orexactly one data record defined by the specified value pair Key1 and Key2.

In the XML file, each data record should be present only once.


Item syntax NC.DbTableLoad Read: no; Write: yes; Call: no

Parameter : none

Reading in all data records from the XML file /database/dbt1.xml

Example SCP item NC.DbTableLoad

Access Write


0 /database/dbt1.xml (VT_BSTR) /DBT1 (VT_BSTR)

Reading in the data records of sector 3 from the XML file /mnt/tools.xml


Access Write


0 /mnt/tools.xml(VT_BSTR)

/DBT1 (VT_BSTR) 3 (VT_I4)



3.6 Configuration Data

Identifier NC.CfgData Access to the configuration data

Description NC.CfgData Item supports the read and write access to the configuration data. During instantiationof this item, a parameter is supplied which determined the accessible configuration data elements.This parameter is supplied in Xpath notation.

During reading, the item data was returned as XML string. The type BSTR is used for data transfer.This type is used as a "container", its contents are UTF8-data. No conversion to UNICODE isdone.

Write access is achieved in the same way. In this case the type BSTR is used equally but data hasto be provided in UTF8-format. Data size is limited to 4 kByte. In future an optional parameterMode may be specified in addition to the data to be written. Actually this parameter has to be set tozero if it is used.

Note: In future probably an additional parameter has to be suppliedat instantiation of the item (client ID returned at login).

Item syntax NC.CfgData,(1) Read: yes; Write: yes; Call: no

(1) = configuration data to access String in Xpath notation

Read configuration data element /NCO/Vel/Ch[2]/Fact/FactRotG70

Example SCP item NC.CfgDaten, /NCO/Vel/Ch[2]/Fact/FactRotG70

Access Read

Result Row/Col 0

0 <FactRotG70>1</FactRotG70>

Read configuration data elements /NCO/Vel/Ch[2]/Fact

Example SCP item NC.CfgDaten,/NCO/Vel/Ch[2]/Fact

Access Read

Result Row/Col 0

0 <Fact><FactG94>1</FactG94><FactG95>1</FactG95><FactRotG70>1</FactRotG70><FactRotG71>1</FactRotG71></Fact>

Set configuration data element /NCO/Vel/Ch[2]/Fact/FactRotG70 to 2

Example SCP item NC.CfgDaten, /NCO/Vel/Ch[2]/Fact/FactRotG70

Access Write

WriteData Row/Col 0

0 <FactRotG70>2</FactRotG70>

1 0 // Mode -> for future use



Identifier NC.CfgDataEvent Event on modification of configuration data

Description The Item NC.CfgDataEvent supports notification due to modification of configuration data. Oninstantiation of this item a parameter is supplied which specifies the configuration data element ora node within the configuration data tree for which notifications are requested. This parameter issupplied in Xpath notation.

If the configuration data element (or a subelement of the specified node) changes, the version isincremented. On Read the actual version is returned and a string in Xpath notation specifying theelement or subelement which has been modified. If the version changes, configuration data has tobe read using the item NC.CfgData.

Item syntax NC.CfgDataEvent,(1) Read: yes; Write: no; Call: no

(1) = configuration data element(s) String in Xpath notation

Request notification on modification of configuration data of axis or spindles (/AXSP)

Example SCP item NC.CfgDataEvent,/AXSP

Access Read

Result Row/Col 0

0 213 (VT_UI4) // actual version

1 /AXSP/Dr[2]/AxFun/Pos/TravLim/PosLim (VT_BSTR)

Identifier NC.CfgDataLoad Load configuration data from file

Description The item NC.CfgDataLoad supports reading of configuration data from an XML-file. Allconfiguration data entries within the file are stored to the configuration database.

No parameters are specified on creation of the item. An XML file is loaded by writing an item.. Thefollowing parameters are required:

• Name of XML-file to be read (path, name, and extension)

• Root-Tag

Item syntax NC. CfgDataLoad Read: no; Write: yes; Call: no

Parameter : None

Load configuration data from XML-file /mnt/axsp.xml

Example SCP item NC.CfgDataLoad

Access Write


0 /mnt/axsp.xml (VT_BSTR) /AXSP (VT_BSTR)



Identifier NC.CfgDataSave Save configuration data to file

Description The item NC.CfgDataLoad supports saving of configuration data to a XML-file. If the file exists it isoverwritten.

No parameters are specified on creation of the item. Saving of configuration data is achieved bywriting the item. The following parameters are required:

• Name of XML-file (path, name, and extension)

• Root-Tag

Item syntax NC. CfgDataLoad Read: no; Write: yes; Call: no

Parameter : None

Load configuration data from XML-file /mnt/axsp.xml

Example SCP item NC.CfgDataLoad

Access Write


0 /mnt/axsp.xml (VT_BSTR) /AXSP (VT_BSTR)



3.7 System Data

Overview

Overview_SDI.jpg

Fig. 3-1: Overview SDI

The term system data signifies a set of data items characterized asfollows:

• All system data items (SDIs) are managed by the system data server(SD server) within the MTX kernel.

• The SD server has remanent storage as well as volatile storage.

• SDIs located in the volatile storage are initialized at each startup ofMTX kernel, whereas SDIs located in the remanent storage hold theirvalues and are unaffected by a shutdown/startup sequence.

• The MTX kernel provides some "built in" SDIs, which need not to beconfigured.

• Additional SDIs may be defined by the machine tool builder or the enduser. The number of SDIs, their size and structure are freelyconfigurable within the range of available storage.

• Configuration files SDDefMTB.xml and SDDefUsr.xml are used fordefinition of SDIs. Built in SDIs are defined in SDDef.xml.

• Each entry in a configuration file specifies the following attributes of aSDI:

• name (up to 16 characters)

• number of data elements (e.g. one data element per channel)

• size (e.g. dimensions of arrays)

• structure



• storage class (remanent/volatile)

• SDIs are accessible from CPL, the PLC program and GUI.

• GUI access is based on XML. A string in Xpath notation is used toaddress a specific SDI, data exchange is based on XML streams.

• The SD server provides an event mechanism for SDIs, i.e. a clientmay request automatic notification upon modification of SDIs.

• A complete list of all SDIs is provided.

• SDIs may be saved to a XML file within the kernel file system orloaded from a file.

• In future access to SDIs is limited by access rights. For each SDIaccess rights may be specified, and read and write is controlled byaccess rights.

The SCP items documented in this paper support XML-based access tosystem data of MTX. The following functions are necessary to provideaccess to system data:

• Login/LogoutIn future access to configuration data will be protected. For this reasona login and logout at the MTX system data server is required. At loginthe actual user level is transferred and the configuration server returnsa corresponding client ID which is used for subsequent transactions.

• Read/Write accessRead and Write access to system data. Data is exchanged in XMLformat.

• List of system data itemsList of all system data items including attributes.

• EventsEvent notification due to modification of system data.

• Load/SaveLoad system data from a XML file or save system data in a XML file.

Note: In the actual software version 11.3.1 Login/Logout is not yetimplemented. The user has to be prepared for some slightmodifications of the SCP interface. Probably login/logout willbe achieved by an additional item and an additional parameterwill be required for some of the items implemented already.



Read and Write Access to System Data

Identifier NC.SystemData Access to System Data

Description The SCP item NC.SystemData supports Read and Write access to a specific system data item. Oninstantiation a parameter is supplied which specifies the system data item or one of its subelements. This parameter is supplied in Xpath notation. The two additional parameters Mode andUser ID are for future use.

On Read data is returned as an XML stream. The type BSTR is used for data transfer. This type isused as a "container", its contents are UTF8-data. No conversion to UNICODE is done.

Write access is achieved in like manner. In this case the type BSTR is used equally but data has tobe provided in UTF8-format. Data size is limited to 4 kByte. In future an optional parameter Modemay be specified in addition to the data to be written. Actually this parameter has to be set to zeroif it is used.

Item syntax NC.SystemData,(1) Read: yes; Write: yes; Call: no

(1) = system data item or sub element String in Xpath notation, string length limited to 99characters

(2) = Mode For future use

(3) = User ID returned at login For future use

Read system data element /BB[4]/K/UA[6]

Example SCP item NC.SystemData,/BB[4]/K/UA[6],0,0

Access Read

Result Row/Col 0

0 <UA>1</UA>

Set system data item /BB[4]/K/UA[6] to 2

Example SCP item NC.SystemData,/BB[4]/K/UA[6],0,0

Access Write

WriteData Row/Col 0

0 <UA>2</UA>

List of System Data ItemsThe list of SDIs is composed of all built in SDIs and additional SDIsdefined by the machine tool builder or the end user (-> configuration filesSDDefMTB.xml and SDDefUsr.xml).

To get a complete list of all SDIs the SCP item defined in the previoussection may be used. The list is returned in XML format and combines allpredefined SDIs as well as SDIs from the configuration mentioned above.The Tag <Comment> is omitted and the keyword "Channel" is replacedby the actual number of channels.

The type BSTR is used for data transfer. This type is used as a"container", its contents are UTF8-data. No conversion to UNICODE isdone.



Get complete list of all SDIs

Example SCP item NC.SystemData,/SDDef,0,0

Access Read

Result Row/Col 0

0 <?xml version="1.0" encoding="UTF-8"?>

<SDDef>

<Variable Dimension="Channel" Storage="permanent">

<Name>SearchRun</Name>

<Type>Var_t</Type>

</Variable>

<Variable Dimension="Channel" Storage="permanent">

<Name>SearchRun</Name>

<Type>SD_SearchRun_t</Type>

</Variable>

</SDDef>

SDI Events

Identifier NC.SystemDataEvent Event on modification of system data

Description The Item NC.SystemDataEvent is used to report modified system data. On instantiation aparameter is supplied which specifies the system data item or a sub element for which notificationsare requested. This parameter is supplied in Xpath notation.

If the system data item (or a sub element of the specified item) changes, the version isincremented. On Read the actual version is returned and a string in Xpath notation specifying thesystem data item or its sub element which has been modified. If the version changes, system datahas to be read using the item NC.SystemData.

To get notifications in case of write access to any system data item just use the XPath "/".

You may only use the root ("/") or a root element to specify the location to be "watched". Events onsub elements of a system data item are not supported.

Item syntax NC.SystemDataEvent,(1) Read: yes; Write: no; Call: no

(1) = system data item (or root) String in Xpath notation, string length is limited to99 characters

Request notification on modification of system data item /MySDI

Example SCP item NC.SystemDataEvent,/MySDI

Access Read

Result Row/Col 0

0 213 (VT_UI4) // actual version

1 /MySDI/SubComp/IntVal (VT_BSTR)



Load and Save

Identifier NC.SystemDataLoad Loading system data from file

Description The SCP item NC.SystemDataLoad supports reading of system data from an XML-file. All systemdata items within the file are loaded to the storage of the system data server.

No parameters are specified on creation of the item. Loading of an XML-file is achieved by writingthe item. The following parameters are required:

• Name of XML-file to be read (path, name, and extension)

• optional Xpath

• Mode

• User ID

Item syntax NC. SystemDataLoad Read: no; Write: yes; Call: no

Parameter : none

Load system data from XML-file /mnt/sdis.xml

Example SCP item NC.SystemDataLoad

Access Write


0 /mnt/sdis.xml(VT_BSTR) (VT_BSTR)

0(VT_I4)

0(VT_I4)

Identifier NC.SystemDataSave Save system data to file

Description The SCP item NC.SystemDataSave supports saving of system data to a XML-file. If the file exists itis overwritten.

No parameters are specified on creation of the item. Saving of system data is achieved by writingthe item. The following parameters are required:

• Name of XML-file (path, name, and extension)

• optional Xpath (to save only one SDI)

• Mode

• User ID

Item syntax NC. SystemDataSave Read: no; Write: yes; Call: no

Parameter : none

Save SDI "BigSDI" to XML-file /mnt/bigsdi.xml

Example SCP item NC.SystemDataSave

Access Write


0 /mnt/bigsdi.xml(VT_BSTR)

/BigSDI(VT_BSTR)

Xxx(VT_I4)

0(VT_I4)



Save complete system data to XML-file /mnt/allsdis.xml

Example SCP item NC.SystemDataSave

Access Write


0 /mnt/allsdis.xml(VT_BSTR) (VT_BSTR)

Yyy(VT_I4)

0(VT_I4)

3.8 Global Settings

Identifier NC.Cmd.DryRunMode Test mode setting

Description The NC.Cmd.DryRunMode item is used to set the test mode of channel, axis, spindle, or totalsystem. It is switched by writing the item. The written data comprises the desired test mode state,the instance (total system, channel, axis, or spindle) and a number (channel, axis, or spindlenumber).

The LDX_Acb_DryRunMode enumerator is used to specify test mode state. This enumeration typecan have the following values:

LDX_Acb_DryRunModeOff // Test mode off,LDX_Acb_DryRunModeOn // Test feedrate on,LDX_Acb_TestFeedrateOff // Test feedrate off,LDX_Acb_TestFeedrateOn // Test feedrate on,LDX_Acb_TestRapidTraverseOff // Test rapid traverse off,LDX_TestRapidTraverseOn // Test rapid traverse on

The LDX_Acb_DryRunItem enumerator is used to specify the instance for which a settingis made. This enumeration type can have the following values:

LDX_Acb_AllAxis // Total block of all axes for// Test mode

,LDX_Acb_ChannelAxis // all axes assigned to a channel,LDX_Acb_SingleAxis // any axis,LDX_Acb_AsyncAxis // all asynchronous axes,LDX_SingleSpindle // Spindle

Restriction: To date, only activation and deactivation of the total block (total system), and activationand deactivation of test feedrate and test rapid traverse (channel) are supported.

See section 5.1 for a description of errors potentially occurring in connection with switching.

Item syntax NC.Cmd.DryRunMode Read: yes; Write: yes; Call: no

Parameter : none

Activation of test mode

Example SCP item NC.Cmd.DryRunMode

Access Write

Row/Col 0 1 2

0 Test mode stateLDX_Acb_DryRunModeOn

(VT_I4)

InstanceLDX_Acb_AllAxis

(VT_I4)

Number(VT_EMPTY)



Activation of test mode


Access Write

Row/Col 0 1 2

0 Test mode stateLDX_Acb_DryRunModeOff

(VT_I4)

InstanceLDX_Acb_AllAxis

(VT_I4)

Number(VT_EMPTY)

Activation test feedrate in channel 2


Access Write

Row/Col 0 1 2

0 Test mode stateLDX_Acb_TestFeedrateOn

(VT_I4)

InstanceLDX_Acb_ChannelAxis

(VT_I4)

Number2

(VT_I4)

3.9 Access to MACODA Parameter

Identifier NC.MacodaParameter Access to MACODA

Description The NC.MacodaParameter item supplies the date of the required MACODA parameter of achannel or a spindle. The answer format varies depending on the type of parameter.

Note: Contrary to the channel parameter, Macoda access to spindleparameters is zero-based!

Item syntax NC.MacodaParameter,(1),(2) Read: yes; Write: no; Call: no

(1) = Parameter number Long format, valid parameter no.

(2) = Channel or spindle number (optional) Integer format, valid number

Reading out of data from the MACODA database in channel 1

Example SCP item NC.MacodaParameter,600500060,1

Access Read

Result Row/Col 0

0 G54.1 (VT_BSTR)

1 G54.2 (VT_BSTR)

2 G54.3 (VT_BSTR)

...

N ... // Number depending on MACODA



3.10 Access to Permanent CPL-Variables

Identifier NC.CplPermVariableList List of permanent CPL variables

Description The NC.CplPermVariableList item makes available all permanent, i.e. fixed (@1-@100) anddefinable CPL variables in a list. Each list entry comprises the name, the type, and thedimensioning of the respective variable.

Item syntax NC.CPLPermVariableList Read: yes; Write: no; Call: no

Parameter : none

Identification of the existing permanent CPL variables

Example SCP item NC.CplPermVariableList

Access Read

Result Row/Col 0 1 2 3

0 @1 (VT_BSTR) 1 (VT_I4) 1 (VT_I4) 1 (VT_I4)



...

99 @100(VT_BSTR)

1 (VT_I4) 1 (VT_I4) 1 (VT_I4)

100 @_X(VT_BSTR)

1 (VT_I4) 10 (VT_I4) 2 (VT_I4)

...

N ... // Number depending on definitions of whmperm.dat and anwperm.dat

Identifier NC.CplPermVariable Permanent CPL - Variables

Description The NC.Cpl.PermVariable item provides for read and write access to permanent CPL variables.With field variables, the optional indices can be used to access individual elements.

Indices are 1-based in CPL. Accordingly, the following applies for Index1 and Index2:

1 <= Index1 <= Dimension1 and1 <= Index2 <= Dimension2

Note: Reading is made possible by means of a cache which isupdated in an approx. 100ms/grid.

Item syntax NC.CplPermVariable (1),(2),(3) Read: yes; Write: yes; Call: no

(1) = name of the variable BSTR

(2) = index1 (optional) Integer format, valid index




Reading of the permanent CPL variables @ToolNo (type integer)

Example SCP item NC.CplPermVariable,@ToolNo

Access Write

Result Row/Col 0

0 4711 (VT_I4)

Writing of an element of the 2-dimensional permanent CPL variables @Darray (double type)

Example SCP item NC.CplPermVariable,@Darray,2,5

Access Write

WriteData Row/Col 0

0 2.75 (VT_R8)

Identifier NC.CplPermVariableWatch Watch permanent CPL variables

Description The NC.CplPermVariableWatch item is used to monitor access on permanent CPL variables.During instantiation of item, the name of the permanent CPL variable and the Watch mode isindicated.

The Watch mode is coded as follows:

0 : Monitoring internal read access

1 : Monitoring write access

It can be spedified via further optional parameters, which data supplies the item. By enteringindices, one or more elements (max. 100) from one field which are supplied in the answer can bespecified. If the optional parameters are missing, the complete data of CPL variables will besupplied.

Indices are 1-based in CPL. Accordingly, the following applies for Index1 and Index2:

1 <= Index1 <= Dimension1 and1 <= Index2 <= Dimension2

If the specific access is executed, the item supplies the current data of permanent CPL variablesincluding a version identification.

Item syntax NC.CplPermVariableWatch,(1),(2),(3),(4) Read: yes; Write: no; Call: no

(1) = name of the variable BSTR

(2) = Watch Mode Integer Format (currently 0 or 1)



Monitoing permanent CPL variables @ToolNmb (Typ Integer) according to modifications

Example SCP item NC.CplPermVariableWatch,@ToolNmb,1

Access Read

Result Row/Col 0

0 1 (VT_I4) // current value

1 245633 (VT_I4) // version identification



Monitoring 1-dimensional array @_R (Type Double, Dimension 100) to modifications

Example SCP item NC.CplPermVariableWatch,@_R,1

Access Read

Result Row/Col 0 1 ... 99

0 1.0 (VT_R8) 2.0 (VT_R8) ... 100.0 (VT_R8)


Monitoring 2-dimensional array @SampleArray (Type Double) to modifications

Example SCP item NC.CplPermVariableWatch,@SampleArray,1,2,9

Access Read

Result Row/Col 0

0 21.4 (VT_R8)




3.11 Delete Error

Identifier NC.Cmd.MessageStoreClr Delete error, warnings, notes

Description The NC.Cmd.MessageStoreClr item is used to delete errors, warnings and notes in the errordatabases of the NC.

Deletion is called up by writing the item. Via a delete mode, it is specified which messages are tobe deleted, and in which channel deletion is to be effected.

The enumerator LDX_WeaClrMode is available for delete mode. This enumeration type can havethe following values:

LDX_WEA_RESETCHAN1_C // Deletion for reset channel 1LDX_WEA_RESETCHAN2_C // Deletion for reset channel 2 …LDX_WEA_RESETCHAN16_C // Deletion for reset channel 16LDX_WEA_CLRWARNG_C // Delete warningsLDX_WEA_CLRRUNTIMEANCMT_C // Delete programmed notesLDX_WEA_ALLCHANRESET_C // Delete for system resetLDX_WEA_WARMSTART_C // Delete for warmstartLDX_WEA_WARMSTART_C // Delete for coldstart

The LDX_WeaClrChan enumerator is used to specify the channels in which data is deleted. Thisenumeration type can have the following values:

LDX_WEA_CHAN1_C // Deleting in channel 1LDX_WEA_CHAN2_C // Deleting in channel 2 ...LDX_WEA_CHAN13_C // Deleting in channel 13LDX_WEA_ALLCHAN_C // Global deletion in the system

Item syntax NC.Cmd.MessageStoreClr Read: no; Write: yes; Call: no

Parameter : none

Deletion of all warnings

Example SCP item NC.Cmd.MessageStoreClr

Access Write


0 LDX_WEA_CLRWARNG_C (VT_I4)

VT_EMPTY LDX_WEA_ALLCHAN_C

OPC Interface Channel-Specific Items 4-1


4 Channel-Specific Items

Identifier NC.Chan.ChanHidden Channel hidden

Description The NC.Chan.ChanHidden PLC item indicates whether the channel is hidden in the display. It isset through MACODA (600500010).

Item syntax NC.Chan.ChanHidden,(1) Read: yes; Write: no; Call: no

(1) = channel number Integer format, valid number

Example SCP item NC.Chan.ChanHidden,2

Access Read

Result Row/Col 0

0 TRUE (VT_BOOL)

4-2 Channel-Specific Items OPC Interface


4.1 Status Information

Identifier NC.Chan.ModeOfOperation NC mode

Description The NC.ModeOfOperation item supplies the operating mode of the channel. Use theLDX_SavOpModes enumerator to code the named operating modes. This enumeration type canhave the following values:

LDX_SAV_OP_MODE_EMPTY_C // No active operating mode,LDX_SAV_OP_MODE_JOGGING_C // Jog mode,LDX_SAV_OP_MODE_REFERENCE_C // Traverse to reference point,LDX_SAV_OP_MODE_SEARCHBLOCK_C // Program restart,LDX_SAV_OP_MODE_MDI_C // Manual entry,LDX _SAV_OP_MODE_AUTOMATIC_C // Automatic: Part programs

// can be processed in subsequent block mode,LDX _SAV_OP_MODE_SINGLE_BLOCK_C // Program block: With 'NC start'

// individual blocks located// in the parts program// are processed. Block preparation// only starts with 'NC start'.

,LDX _SAV_OP_MODE_SINGLE_STEP_C // Single step: With 'NC start'// a single block is// passed to the interpolator for// processing

,LDX _SAV_OP_MODE_TEACH_C // reserved,LDX _SAV_OP_MODE_SUSPEND_C // reserved,LDX _SAV_OP_MODE_SINGLE_ACT_BLOCK_C // Single block: With 'NC start'

// all blocks which have been// generated and fully prepared on// the basis of a single block in the// parts program are transmitted// passed to the interpolator for// processing.

,LDX _SAV_OP_MODE_RETURN_TO_PATH_C // Program restart: Axes// can be removed from the contour// manually and restarted// automatically or// manually.

,LDX _SAV_OP_MODE_DEBUG_STEP_C // CPL-Debugger: Single blocks// located in the parts// program are processed.

,LDX_SAV_OP_MODE_DEBUG_CONT_C // CPL-Debugger: All blocks// up to the next breakpoint// are processed.

,LDX_SAV_OP_MODE_JOGGING_COORDS_C // Manual setting:// Movement in tool coordinates

Item syntax NC.Chan.ModeOfOperation,(1) Read: yes; Write: no; Call:no


Example SCP item NC.Chan.ModeOfOperation,1

Access Read

Result Row/Col 0

0 LDX_SAV_OP_MODE_REFERENCE_C (VT_I4) // Traversing to reference point



Identifier NC.Chan.ChanState Channel status

Description The NC.Chan.ChanState item indicates the current channel state. The status diagram for thechannel state is shown in the following. On reading, the state of the channel and the state of blockprocessing and of the interpolator in the channel is supplied.

For coding the statuses, the LDX_ChanState, LDX_SavState and LDX_IpoState enumerators areused:

enum LDX_ChanState // channel state LDXChanInactive,LDXChanReady,LDXChanRunning,LDXChanStopped,LDXChanResetting,LDXChanCreating,LDXChanError

enum LDX_SavState // block processing stateLDX_SAV_OP_STATE_INACTIV_C // The state is 'inactive', a

// program can be// started.

,LDX_SAV_OP_STATE_READY_C // The state is 'ready' and the// program can be// started.

,LDX_SAV_OP_STATE_RUN_C // A program or an// NC block is processed.

,LDX_SAV_OP_STATE_WAIT_C // reserved,LDX_SAV_OP_STATE_HOLD_C // reserved,LDX_SAV_OP_STATE_ERROR_C // An error occurred which

// can only be remedied by// reset or program// deselection.

,LDX_SAV_OP_STATE_SUSPEND_C // reserved for internal purposes,LDX_SAV_OP_STATE_RESETTING_C // reset is executed.

// No jobs may be// accepted until// the state passes to 'inactive'.

,LDX_SAV_OP_STATE_CREATING_C // A program is selected and// prepared (e.g. linked).

,LDX_SAV_OP_STATE_CANCEL_DIST_PREP_C // 'Delete distance to go' has been// triggered, cleaning-up work// is being done.

,LDX_SAV_OP_STATE_CANCEL_DIST_RUN_C //,LDX_SAV_OP_STATE_READY_FOR_PROGSTART_C // The state is

// 'ready', the program is at// Start of Program and can// be started.

,LDX_SAV_OP_STATE_READY_FOR_NEXT_BLOCK_C // With the buffered// NC block selection, all blocks// are processed. Waiting for the// next input.

enum LDX_IpoState // interpolator state LDX_IPO_OP_STATE_RUN_C // The interpolator is running.,LDX_IPO_OP_STATE_SLOPEDOWN_C // The interpolator is brought to a stop

// via feed hold,LDX_IPO_OP_STATE_STOPPED_C // The interpolator has stopped

// the axes

Item syntax NC.Chan.ChanState,(1) Read: yes; Write: no; Call:no




Example SCP item NC.Chan.ChanState,1

Access Read


0 LDXChanReady(VT_I4)

LDX_SAV_OP_STATE_READY_FOR_PROGST

ART_C

LDX_IPO_OP_STATE_STOPPED_C

Zustandsdiagramm.jpg

Fig. 4-1: Status diagram during execution of part program

Note: MDI

• When manual data input blocks are specified, the statuspasses from inactive to ready.

• After activation of 'Start', the status passes from ready torunning.

• After completing the manual input blocks, the statuspasses from running to inactive or error (in case of error).

• There may be small differences between the specificationof a single MDI block and several blocks (state aftercompletion of the MDI blocks).

• The status diagram is supplied subsequently.



Identifier NC.Chan.DryRunMode Channel block

Description The NC.Chan.DryRunMode PLC item supplies the current state of the channel block. Currently, thekernel only supports a global total block effective through all channels; for this reason, the value ofthe NC.Chan.DryRunMode item corresponds to that of the NC.DryRunMode item.

Item syntax NC.Chan.DryRunMode,(1) Read: yes; Write: no; Call:no


Example SCP item NC.Chan.DryRunMode,2

Access Read

Result Row/Col 0

0 1 (VT_I4)

Identifier NC.Chan.SkipBlockMode Skip block

Description The NC.Chan.SkipBlockMode PLC item supplies the current state of "Skip block".

Item syntax NC.Chan.SkipBlockMode,(1) Read: yes; Write: no; Call:no


Example SCP item NC.Chan.SkipBlockMode,1

Access Read

Result Row/Col 0 1

0 0 (VT_I4) 0 (VT_I4)

Identifier NC.Chan.OptionalStop Optional stop

Description The NC.Chan.OptionalStop item supplies the current status of "Optional stop" as it is applied at theNC interface output and the NC interface input.

Item syntax NC.Chan.OptionalStop,(1) Read: yes; Write: no; Call:no


Example SCP item NC.Chan.OptionalStop,1

Access Read

Result Row/Col 0 1

0 0 (VT_I4) 0 (VT_I4)



Identifier NC.Chan.DryRunFeed Test Feed

Description The NC.Chan.DryRunFeed PLC item supplies the information whether test feed is active in therespective channel or not.

Item syntax NC.Chan.DryRunFeed,(1) Read: yes; Write: no; Call:no


Example SCP item NC.Chan.DryRunFeed,1

Access Read

Result Row/Col 0 1

0 0 (VT_I4) 0 (VT_I4)

Identifier NC.Chan.DryRunRapid Test rapid mode

Description The NC.Chan.DryRunFeed PLC item supplies the information whether test rapid mode is active inthe respective channel or not.

Item syntax NC.Chan.DryRunRapid,(1) Read: yes; Write: no; Call:no


Example SCP item NC.Chan.DryRunRapid,1

Access Read

Result Row/Col 0 1

0 0 (VT_I4) 0 (VT_I4)



Identifier NC.Chan.WaitingStates Channel waiting states

Description The NC.Chan.WaitingStates NC item supplies the active waiting states of a channel. Possiblewaiting states:

For waiting states, the LDX_McoWaitingState enumerator is available. This enumeration type canhave the following values:

LDX_McoDwellTime_C // dwell time,LDX_McoAuxiliaryFunction_C // Auxiliary function requiring acknowledgment,LDX_McoBlockTransferInhibit_C // Block transfer lock,LDX_McoChannelFeedrate0_C // Channel feedrate equals0,LDX_McoProgramStop_C // Program stop with M0/M1,LDX_McoFeedHold_C // Feed hold in the channel,LDX_McoFeedInhibit_C // Feed inhibit in the channel, or

// a channel axis,LDX_McoCustomerStop_C // Customer-specified

// block transfer lock,LDX_McoSynchronizedMovementStop_C // Synchronized movement

// stop between channels// (ASTOP, ...)

,LDX_McoWaitingForAxisTransfer_C // Waiting for axis during axis// transfer (G511)

,LDX_McoWaitingForPermanentVariable_C // Waiting for permanent variable// (WPV)

,LDX_McoWaitingForIFSignalActive_C // Waiting for interface signal at the// active moment in time (WAITA, ...)

,LDX_McoWaitingForIFSignalPreparation_C // Waiting for interface signal// (WAIT(IC...)) or for a defined// period of time// (WAIT(,TIME%)) in the// block preparation

,LDX_McoMotionCrontrolDataService_C // Motion Control data service// (MCODS(...))

Item syntax NC.Chan.WaitingStates,(1) Read: yes; Write: no; Call:no


Example SCP item NC.Chan.WaitingStates,1

Access Read

Result Row/Col 0

0 32 (VT_I4) // Feed hold



4.2 Active Programs and Tables

Identifier NC.Chan.ActMainProgram Active main program

Description The NC.Chan.ActMainProgram item supplies the name of the main program. The result comprisesthe file name and the full path of the main program.

Item syntax NC.Chan.ActMainProgram,(1) Read: yes; Write: no; Call: no


Identification of the active main program in channel 1

Example SCP item NC.Chan.ActMainProgram,1

Access Read

Result Row/Col 0

0 /usr/user/sekt.cnc (VT_BSTR)

Identifier NC.Chan.ActSubProgram Name of the subprogram

Description The NC.Chan.ActSubProgram item supplies the name of the current subprogram. The resultcomprises the file name and the full path of the subprogram.

Item syntax NC.Chan.ActSubProgram,(1) Read: yes; Write: no; Call: no


Identifier NC.Chan.ActNcBlock Current block number

Description The NC.Chan.ActNcBlock item supplies the designation of the current block. The result comprisesthe designation in the form of a string. If no block number is programmed, an empty string isreturned.

Item syntax NC.Chan.ActNcBlock,(1) Read: yes; Write: no; Call: no


Identifier NC.Chan.ActAxisOffsetTable Active axis offset table

Description The NC.Chan.ActAxisOffsetTable item supplies the name of the active axis offset table. The resultcomprises the file name and the full path of the table.

Item syntax NC.Chan.ActAxisOffsetTable,(1) Read: yes; Write: no; Call: no


Identification of the active axis offset table in channel 1

Example SCP item NC.Chan.ActAxisOffsetTable,1

Access Read

Result Row/Col 0

0 /database/achsoffsets.aot (VT_BSTR)



Identifier NC.Chan.ActDCorrectionTable Active D compensation number:

Description The NC.Chan.ActDCorrectionTable item supplies the name of the active D compensation table.The result comprises the file name and the full path of the table.

Item syntax NC.Chan.ActDCorrectionTable,(1) Read: yes; Write: no; Call: no


Identification of the active D compensation table in channel 1

Example SCP item NC.Chan.ActDCorrectionTable,1

Access Read

Result Row/Col 0

0 /database/sample.dct (VT_BSTR)

4.3 Axis Position Data

Beyond the actual position values, all axis position items comprise thefollowing additional information:

• Physical axis number or coordinates number

• Channel assignmentIf the axis is synchronous, a value >= 0 is supplied which specifies thechannel to which the axis is assigned. With asynchronous axes,spindles etc. a negative value is supplied. For coding the axisassignment, use the LDX_McoAxisAssignment enumerator. Thisenumeration type can have the following values:

LDX_McoIsAsynchron_C // Axis is asynchronuous,LDX_McoIsSpindle_C // It is a spindle,LDX_McoIsNotDefined_C // Axis is not defined,LDX_McoIsInactiveSpindle_C // Hidden spindle

• Logic axis or coordinates name

• The current logic axis name or coordinates name is supplied for eachaxis or coordinate. If no logic name is configured, the physical axisname will appear.

• Axis in position

• Reference point known

• Current unit

For each axis, the current unit of measurement is supplied in which theaxis is programmed (depending on G70/71). For the unit, theLDX_McoUnitOfMeasurement enumerator is available. This enumerationtype can have the following values:

LDX_McoUnitInch_C // Inch,LDX_McoUnitMetric_C // Metric,LDX_McoUnitDegree_C // Rotary axis,LDX_McoAuxiliaryFunction_C // Axis not available,LDX_McoUnitPlaceProgramming_C // Place programming for

// Hirth axes

• Diameter programming active



In the following example, the axis positions in the workpiece coordinatesystem are read through the NC.Chan.AxisPosWcs item. For each axis,the additional information is provided in the first 7 columns; the actualposition value follows in the 8th column:

Reading the axis positions in the workpiece coordinates system through theNC.Chan.AxisPosWcs item

Example SCPitem

NC.Chan.AxisPosWcs,1

Access

Read

Result 0 1 2 3 4 5 6 7Row/Col

Additional information

Axis#(VT_I4)

Channel(VT_I4)

Name(VT_BS

TR)

InPos(VT_I4)

InRef(VT_I4)

Unit(VT_I4)

Ø-Prg(VT_I4)

Position value(VT_R8)

0 1 1 X TRUE TRUE LDX_McoUnitMetric_C

FALSE 23.5678

1 2 1 Y TRUE TRUE LDX_McoUnitMetric_C

FALSE 13.5678

2 3 1 C TRUE TRUE LDX_McoUnitMetric_C

FALSE 3.5678

3 5 2 X2 FALSE TRUE LDX_McoUnitInch_C

FALSE 3.112

Identifier NC.Chan.AxisPosWcs Workpiece positions

Description The AxisPosWcs PLC item supplies the current axis positions in respect of the workpiececoordinates system of the axes. Beyond the actual position values, additional information issupplied per axis (see above).

Item syntax NC.Chan.AxisPosWcs,(1) Read: yes; Write: no; Call: no


Example SCP item NC.Chan.AxisPosWcs,2

Access Read

Result Row/Col 0 ... 6 7

Additional information Position

0 123,456 (VT_R8)

1 23.3456 (VT_R8)

2 23.6 (VT_R8)

3 23.6 (VT_R8)

4 0.423 (VT_R8)



Identifier NC.Chan.AxisPosMcs Machine position

Description The AxisPosMcs PLC item supplies the current axis positions in respect of the machinecoordinates system of the axes. Beyond the actual position values, additional information issupplied per axis (see above).

Item syntax NC.Chan.AxisPosMcs,(1) Read: yes; Write: no; Call: no


Identifier NC.Chan.AxisPosAcs Positions in the ACS

Description The AxisPosAcs SCP item supplies the current axis positions in respect of the axis coordinatessystem. Beyond the actual position values, additional information is supplied per axis (see above).

Item syntax NC.Chan.AxisPosAcs,(1) Read: yes; Write: no; Call: no


Identifier NC.Chan.AxisPosBcs Positions in the BCS

Description The AxisPosBcs SCP item supplies the current axis positions in respect of the basis coordinatessystem. Beyond the actual position values, additional information is supplied per axis (see above).

Item syntax NC.Chan.AxisPosBcs,(1) Read: yes; Write: no; Call: no


Identifier NC.Chan.AxisPosAcsDrv Axis positions in the ACS (drive)

Description The AxisPosAcsDrv SCP item supplies the current actual axis positions in respect of the axiscoordinates system. The positions are supplied directly from the drive data. Beyond the actualposition values, additional information is supplied per axis (see above).

Item syntax NC.Chan.AxisPosAcsDrv,(1) Read: yes; Write: no; Call: no


Identifier NC.Chan.AxisPosBcsDrv Axis positions in the BCS (drive)

Description The AxisPosBcsDrv SCP item supplies the current actual axis positions in respect of the basiscoordinates system. The positions are supplied directly from the drive data. Beyond the actualposition values, additional information is supplied per axis (see above).

Item syntax NC.Chan.AxisPosBcsDrv,(1) Read: yes; Write: no; Call: no


Identifier NC.Chan.AxisPosEndWcs Workpiece end position

Description The AxisPosEndWcs SCP item supplies the end positions in respect of the workpiece coordinatessystem. The positions comprise compensations which are active in relation to the programmed endvalue. Beyond the actual position values, additional information is supplied per axis (see above).

Item syntax NC.Chan.AxisPosEndWcs,(1) Read: yes; Write: no; Call: no




Identifier NC.Chan.AxisPosProg Program value

Description The AxisPosEndWcs SCP item supplies the programmed axis positions. Beyond the actualposition values, additional information is supplied per axis (see above).

Item syntax NC.Chan.AxisPosEndWcs,(1) Read: yes; Write: no; Call: no


Identifier NC.Chan.AxisPosDistWcs Distance to go in WCS

Description The AxisPosDistWcs SCP item supplies the distance to go in respect of the workpiece coordinatessystem. Beyond the actual position values, additional information is supplied per axis (see above).

Item syntax NC.Chan.AxisPosDistWcs,(1) Read: yes; Write: no; Call: no


Identifier NC.Chan.AxisPosDistAcs Distance to go in the ACS

Description The AxisPosDistAcs SCP item supplies the distance to go in respect of the axis coordinatessystem. Beyond the actual position values, additional information is supplied per axis (see above).

Item syntax NC.Chan.AxisPosDistAcs,(1) Read: yes; Write: no; Call: no


Identifier NC.Chan.AxisPosLag Lag

Description The AxisPosLag SCP item supplies the lag of the axes. Beyond the actual lag values, additionalinformation is supplied per axis (see above).

Item syntax NC.Chan.AxisPosLag,(1) Read: yes; Write: no; Call: no


Identifier NC.Chan.AxisPosDistMcs Machine distance to go

Description The AxisPosDistMcs SCP item supplies the distance to go in respect of the machine coordinatessystem. Beyond the actual position values, the information is supplied for each axis whetherdiameter programming is active; furthermore, the measuring unit of the axis and the number ofdecimal places for inch and metrical is specified.

Item syntax NC.Chan.AxisPosDistMcs,(1) Read: yes; Write: no; Call: no


Identifier NC.Chan.AxisPosDistBcs Basics distance to go

Description The AxisPosDisBcs SCP item supplies the distance to go in respect of the basis coordinatessystem. Beyond the actual position values, the information is supplied for each axis whetherdiameter programming is active; furthermore, the measuring unit of the axis and the number ofdecimal places for inch and metrical is specified.

Item syntax NC.Chan.AxisPosDistBcs,(1) Read: yes; Write: no; Call: no




Identifier NC.Chan.AxisNamesPhys Physical axes names

Description The "AxisNamesPhys" SCP item supplies the current physical axis names of the axes.

Item syntax NC.Chan.AxisNamesPhys,(1) Read: yes; Write: no; Call: no


Example SCP item NC.Chan.AxisNamesPhys,1

Access Read

Result Row/Col 0

0 X (VT_BSTR)

1 Y (VT_BSTR)

2 Z (VT_BSTR)

3 B (VT_BSTR)

Identifier NC.Chan.AxisNamesLog Logical axes names

Description The AxisNamesLog SCP item supplies the current logical axis names of the axes.

Item syntax NC.Chan.AxisNamesLog,(1) Read: yes; Write: no; Call: no


Identifier NC.Chan.AxisPosEndMcs Machine end position

Description The AxisPosEndMcs SCP item supplies the end positions in respect of the machine coordinatessystem. Beyond the actual position values, the information is supplied for each axis whetherdiameter programming is active; furthermore, the measuring unit of the axis and the number ofdecimal places for inch and metrical is specified.

Item syntax NC.Chan.AxisPosEndMcs,(1) Read: yes; Write: no; Call: no


Identifier NC.Chan.AxisPosEndBcs Basics end position

Description The AxisPosEndBcs SCP item supplies the end positions in respect of the basis coordinatessystem. Beyond the actual position values, the information is supplied for each axis whetherdiameter programming is active; furthermore, the measuring unit of the axis and the number ofdecimal places for inch and metrical is specified.

Item syntax NC.Chan.AxisPosEndBcs,(1) Read: yes; Write: no; Call: no


Identifier NC.Chan. AxisMeasUnit Measurement units

Description The Item AxisMeasUnit SCP item supplies the measuring units of the axes.

For the unit, the LDX_McoUnitOfMeasurement enumerator is available. This enumeration type canhave the following values:

LDX_McoUnitInch_C // Inch,LDX_McoUnitMetric_C // Metric,LDX_McoUnitDegree_C // Rotary axis,LDX_McoAuxiliaryFunction_C // Axis not available,LDX_McoUnitPlaceProgramming_C // Place programming for Hirth axes



Item syntax NC.Chan.AxisMeasUnit,(1) Read: yes; Write: no; Call: no


Example SCP item AxisMeasUnit,2

Access Read

Result Row/Col 0

0 LDX_McoUnitMetric_C (VT_I4)



3 LDX_McoUnitDegree_C (VT_I4)

Identifier NC.Chan.AxisInPos InPos state

Description The Item AxisInPos SCP item supplies the inpos state of the axes.

Value range:

0 - Axis position is not within the "InPos" window,

1 - Axis position is within the "InPos" window

Item syntax NC.Chan.AxisInPos,(1) Read: yes; Write: no; Call: no


Example SCP item AxisInPos,2

Access Read

Result Row/Col 0

0 1 (VT_I4)

1 1 (VT_I4)

2 1 (VT_I4)

3 1 (VT_I4)

Identifier NC.Chan.AxisReferenced Reference points known

Description The AxisReferenced SCP item supplies the information whether the reference points of the axesare known.

Value range:

0 - Reference point not known,1 - Reference point known

Item syntax NC.Chan.AxisReferenced,(1) Read: yes; Write: no; Call: no




Example SCP item NC.Chan.AxisReferenced,2

Access Read

Result Row/Col 0

0 1 (VT_I4)

1 1 (VT_I4)

2 1 (VT_I4)

3 1 (VT_I4)

Identifier NC.Chan.AxisAssignment Axis assignment

Description The NC.Chan.AxisAssignment SCP item supplies the information on the channels to which theaxes are assigned. If the axis is synchronous, a value >= 0 is returned which specifies the channelto which the axis is assigned. With asynchronous axes, spindles etc. a negative value is supplied.For coding the axis assignment, use the LDX_McoAxisAssignment enumerator. This enumerationtype can have the following values:

LDX_McoIsAsynchron_C // Axis is asynchronuous,LDX_McoIsSpindle_C // It is a spindle,LDX_McoIsNotDefined_C // Axis is not defined,LDX_McoIsInactiveSpindle_C // Hidden spindle

Item syntax NC.Chan.AxisAssignment,(1) Read: yes; Write: no; Call: no


Example SCP item NC.Chan. AxisAssignment,2

Access Read

Result Row/Col 0

0 1 (VT_I4)

1 1 (VT_I4)

2 1 (VT_I4)

3 LDX_MCoIsAsynchron_C (VT_I4)



4.4 Compensation and Offset Values

Identifier NC.Chan.ActZeroOffsetSummary Active zero offsets (total)

Description The NC.Chan.ActZeroOffsetSummary item supplies for all axes in the channel the total of activezero offset values of all NPV groups.

Beyond the actual offset values, the following additional data is supplied:

• Physical axis number or coordinates number• Channel assignment• Axis or coordinates names• Axis in position• Reference point known• Measuring unit• Diameter programming

Item syntax NC.Chan.ActZeroOffsetSummary,(1) Read: yes; Write: no; Call: no


Identification of the active zero offsets (summary) for channel 1

Example SCPitem

NC.Chan.ActZeroOffsetSummary,1

Access Read

Result Row/Col 0 1 2 3 4 5 6 7

Axis#(VT_I4)

Channel(VT_I4)

Name(VT_BSTR)

InPos(VT_BOOL)

InRef(VT_BOOL)

Unit(VT_I4)

Ø-Prg(VT_BOOL)

∑(VT_R8)

0 1 1 X TRUE TRUE LDX_McoUnitMetric_C

FALSE 23.5678

1 2 1 Y TRUE TRUE LDX_MCoUnitMetric_C

FALSE 13.5678

2 3 1 C TRUE TRUE LDX_MCoUnitMetric_C

FALSE 3.5678

Identifier NC.Chan.ActZeroOffsetValues Active zero offset values

Description The NC.Chan.ActZeroOffsetValues item supplies for all axes in the channel the active zero offsetvalues of all NPV groups. The values for the basis group and the values of the first to fourthadditive group are supplied separately.

As with the NC.Chan.ActZeroOffsetSummary item, the above additional information is suppliedbeyond the actual offset values.

Item syntax NC.Chan.ActZeroOffsetValues,(1) Read: yes; Write: no; Call: no




Identification of the active zero offsets for channel 1

Example SCPitem

NC.Chan.ActZeroOffsetValues,1

Access Read

Result Row/Col 0 ... 6 7 8 9 10 11

Axis#(VT_I4)

... Ø-Prg(VT_BOOL)

Bank 1(VT_R8)

Bank 2(VT_R8)

Bank 3(VT_R8)

Bank 4(VT_R8)

Bank 5(VT_R8)

0 1 ... FALSE 0.0 0.0 0.0 0.0 0.0

1 2 ... FALSE 0.04 0.5 0.44 0.0 0.0

2 3 ... FALSE 0.0 0.0 0.0 0.0 0.0

Identifier NC.Chan.ActDCorrectionValues Active D corrections

Description The NC.Chan.ActDCorrectionValues item supplies the active D compensation values, i.e. theactive values for length and radius compensation, as well as the tool edge position (orientation).

Item syntax NC.Chan.ActDCorrectionValues,(1) Read: yes; Write: no; Call: no


Identification of the active compensation values in channel 1

Example SCP item NC.Chan.ActDCorrectionValues,1

Access Read

Result Row/Col 1 2 3 4 5

L1 L2 L3 Rad Ori

0 2.65

(VT_ R8)

20.5

(VT_ R8)

0.109

(VT_ R8)

9.04

(VT_ R8)

0

(VT_ R8)

Identifier NC.Chan.ActDCorrectionNmb Active D-Correction Number

Description The NC.Chan.ActDCorrectionNmb item supplies the active D compensation number.

Item syntax NC.Chan.ActDCorrectionNmb,(1) Read: yes; Write: no; Call: no


Identification of the active D compensation number in channel 1

Example SCP item NC.Chan.ActDCorrectionNmb,1

Access Read

Result Row/Col 0

0 2 (VT_ I4)



Identifier NC.Chan.ActToolCorrectionValues Active tool compensations

Description The NC.Chan.ActToolCorrectionValues item supplies the active tool compensation values. Thevalues for length and radius compensation are supplied, as well as edge position, Euler angle(orientation in space) and edge number.

Item syntax NC.Chan.ActToolCorrectionValues,(1) Read: yes; Write: no; Call: no


Identification of the active tool compensations for channel 1

Example SCPitem

NC.Chan.ActToolCorrectionValues,1

Access Read

Result Row/Col 0 1 2 3 4 5 6 7 8

L1 L2 L3 Rad Ori Φ υ ψ Edge

0 2.65(VT_R8)

20.5(VT_R8)

0.109(VT_R8)

9.04(VT_R8)

0.0(VT_R8)

0.0(VT_R8)

0.0(VT_R8)

0.0(VT_R8)

4.0(VT_R8)

(each VT_R8)

4.5 Modal Functions

Identifier NC.Chan.ModalNcFunctions Modal NC functions

Description The NC.Chan.ModalNcFunctions supplies a list of the modal NC functions. Sequence and numberof the supplied modal functions can be configured in MACODA (6005 00040).

A list of the active NC functions is supplied. This list may have blank inputs (blank strings) if no NCfunction is active in a modal group.

Faulty inputs in the configuration (MACODA parameter has invalid value) cause inputs to bemarked as invalid. In this case, the list entry has the value "?".

Item syntax NC.Chan.ModalNcFunctions,(1) Read: yes; Write: no; Call: no


Reading out the modal NC functions in channel 1

Example SCP item NC.Chan.ModalNcFunctions,1

Access Read

Result Row/Col 0

0 G2 (VT_BSTR)

1 G9 (VT_BSTR)

2 G18 (VT_BSTR)




Identifier NC.Chan.ModalTransformationFunctions Modal NC functions for workpiece transformations

Description The NC.Chan.ModalTransformationFunctions item supplies a list of the modal NC functions forworkpiece transformations. Sequence and number of the supplied modal functions can beconfigured through MACODA (6005 00060).



Item syntax NC.Chan.ModalTransformationFunctions,(1)

Read: yes; Write: no; Call: no


Reading out the modal NC functions for workpiece transformations in channel 1

Example SCP item NC.Chan.ModalTransformationFunctions,1

Access Read

Result Row/Col 0

0 G154.0 (VT_BSTR)

1 G155.3 (VT_BSTR)

2 G156.3 (VT_BSTR)


Identifier NC.Chan.ModalAxisOffsetFunctions Modal NC functions for axis zero offset

Description The NC.Chan.ModalAxisOffsetFunctions item supplies a list of the modal NC functions for axiszero offset. Sequence and number of the supplied modal functions can be configured throughMACODA (6005 00070).



Item syntax NC.Chan.ModalAxisOffsetFunctions,(1) Read: yes; Write: no; Call: no


Reading out the modal NC functions for axis zero offsets in channel 1

Example SCP item NC.Chan.ModalAxisOffsetFunctions,1

Access Read

Result Row/Col 0

0 G54.0 (VT_BSTR)

1 G55.3 (VT_BSTR)

2 G56.2 (VT_BSTR)




Identifier NC.Chan.ModalAuxFunctions Modal auxiliary functions

Description The NC.Chan.ModalAuxFunctions item supplies a list of the modal auxiliary functions. Sequenceand number of the supplied modal functions can be configured through MACODA (6005 00050).

A list of the active auxiliary functions is supplied. This list may have blank strings if no auxiliaryfunction is active in a modal group.


Item syntax NC.Chan.ModalAuxFunctions,(1) Read: yes; Write: no; Call: no


Reading out the modal auxiliary functions in channel 1

Example SCP item NC.Chan.ModalAuxFunctions,1

Access Read

Result Row/Col 0

0 M10 (VT_BSTR)


Identifier NC.Chan.ModalFunction Reading out a modal group

Description The NC.Chan.ModalFunction item is used to read out a single modal group. When this item isinstantiated, the channel and the modal group to be read out is specified through parameters. Thegroup is specified by any modal function which may be effective in this group.

Item syntax NC.Chan.ModalFunction,(1) Read: yes; Write: no; Call: no


Identification of the information "Inch programming active" for channel 2

Example SCP item NC.Chan.ModalFunction,2,G70

Access Read

Result Row/Col 0

0 G71 (VT_BSTR)

4.6 Technology Data

Identifier NC.Chan.ActFeedOverride Feed override

Description The NC.Chan.ActFeedOverride item supplies the current value of the feed override. The resultincludes the override value in per cent.

In addition to the current value, the maximum value is supplied.

Item syntax NC.Chan.ActFeedOverride,(1) Read: yes; Write: no; Call: no




Reading the active feed override in channel 1

Example SCP item NC.Chan.ActFeedOverride,1

Access Read

Result Row/Col 0 1

0 85.0 (VT_R8) 120.0 (VT_R8) // maximum value

Identifier NC.Chan.ActSpindleOverride Spindle override

Description The NC.Chan.ActSpindleOverride item supplies the current value of the spindle override. Theresult includes the override value in per cent.

The spindles indicated in the channel are configured through MACODA parameter 6005 0030.Specifically for the channel, this parameter indicates which spindle is shown at which positionwithin the spindle display. A maximum of 8 spindles can be agreed. In the result, a value is shownfor each listed spindle.

Item syntax NC.Chan.ActSpindleOverride,(1) Read: yes; Write: no; Call: no


Reading the active spindle override in channel 1

Example SCP item NC.Chan.ActSpindleOverride,1

Access Read

Result Row/Col 0 1

0 110.0 (VT_R8) 150.0 (VT_R8) // maximum value

1 90 (VT_R8) 150.0 (VT_R8) // maximum value

Identifier NC.Chan.ActFeedrate Active feed value

Description The NC.Chan.ActFeedrate item supplies the current feed value.

Supplies 3 path feed values each in mm/min. With all 3 feed values, the override effective in eachcase if taken into consideration.

1. The command external interpolar velocity. It is assigned to the interpolator (programmedfeed).

2. The actual interpolator velocity. This corresponds to the current path velocity.

3. The command internal interpolar velocity. It may have changed vis-à-vis path feed 1 becauseof an application, e.g. a FeedAdapt function on the customer side. If feed is programmed inmm/U (G95), it supplies for example the path feed in mm/min.

Item syntax NC.Chan.ActFeedrate,(1) Read: yes; Write: no; Call: no




Reading the active feed in channel 1

Example SCP item NC.Chan.ActFeedrate,1

Access Read


0 85 (VT_R8) 85 (VT_R8) 85 (VT_R8)

0 11

1 (VT_I4) // Decimal places metr. 2 (VT_I4) // Decimal places inch

2 1 (VT_I4) // mm/min 1.000 (VT_R8) // 1mm/U

Identifier NC.Chan.ProgrammedFeedrate Programmed feed value

Description The NC.Chan.ProgrammedFeedrate item supplies the programmed feed value.

Item syntax NC.Chan.ProgrammedFeedrate,(1) Read: yes; Write: no; Call: no


Reading the programmed feed in channel 1

Example SCP item NC.Chan.ProgrammedFeedrate,1

Access Read

Result Row/Col 0

0 150 (VT_R8)

0 11

1 (VT_I4) // Decimal places metr. 2 (VT_I4) // Decimal places inch

2 1 (VT_I4) // mm/min 1.000 (VT_R8) // 1mm/U

Identifier NC.Chan.ActSpindleSpeed Active command spindle speed

Description The NC.Chan.ActSpindleSpeed item supplies the active command spindle speed(s). If 'G196' isactive, the surface speeds are supplied in m/min or feet/min.


Item syntax NC.Chan.ActSpindleSpeed,(1) Read: yes; Write: no; Call: no




Reading the active spindle speeds in channel 1

Example SCP item NC.Chan.ActSpindle,1

Access Read

Result Row/Col 0

0 2000 (VT_R8)

1 3500 (VT_R8)

Identifier NC.Chan.ActSpindleSpeedDrv Active actual spindle speed

Description The NC.Chan.ActSpindleSpeedDrv item supplies the active actual spindle speed(s).


Item syntax NC.Chan.ActSpindleSpeedDrv,(1) Read: yes; Write: no; Call: no


Reading the active spindle speeds in channel 1

Example SCP item NC.Chan.ActSpindleSpeedDrv,1

Access Read

Result Row/Col 0

0 2009.5 (VT_R8)

1 3497.7 (VT_R8)

Identifier NC.Chan.ProgrammedSpindleSpeed Programmed spindle speed

Description The NC.Chan.ProgrammedSpindleSpeed item supplies the programmed spindle speed(s).


Item syntax NC.Chan.ProgrammedSpindleSpeed,(1)

Read: yes; Write: no; Call: no


Reading the programmed spindle speeds in channel 1

Example SCP item NC.Chan.ProgrammedSpindleSpeed,1

Access Read

Result Row/Col 0

0 2000 (VT_R8)

1 3500 (VT_R8)



Identifier NC.Chan.ActSpindleGears Gear ranges of the spindles

Description The NC.Chan.ActSpindleGears item supplies the gear ranges of the spindles. To code the gearranges, use the LDX_McoSpindleGearRange enumerator which can assume the following values:

LDX_McoSpindleAutoGearRange_C // Automatic gear range selection,LDX_McoSpindleGearRange1_C // Gear range 1,LDX_McoSpindleGearRange2_C // Gear range 2,LDX_McoSpindleGearRange3_C // Gear range 3,LDX_McoSpindleGearRange4_C // Gear range 4,LDX_McoSpindleGearIdleMode_C // Gear range disengaged


Item syntax NC.Chan.ActSpindleGears,(1) Read: yes; Write: no; Call: no


Reading out the gear ranges for spindles in channel 1

Example SCP item NC.Chan.ActSpindleGears,1

Access Read

Result Row/Col 0

0 LDX_McoSpindleAutoGearRange_C (VT_I4)

1 LDX_McoSpindleGearRange2_C (VT_I4)

Identifier NC.Chan.ActSpindleMovements Movement functions of the spindles

Description The NC.Chan.ActSpindleMovement item supplies the movement functions of the spindles. To codethe gear ranges, use the LDX_McoSpindleGearRange enumerator which can assume the followingvalues:

LDX_McoSpindleNotDefined_C // Spindle not definedLDX_McoSpindleRight_C // Clockwise rotation without cooling agentLDX_McoSpindleRightCool_C // Clockwise rotation with cooling agentLDX_McoSpindleRightCool_C // Anticlockwise rotation without cooling agentLDX_McoSpindleRightCool_C // Anticlockwise rotation with cooling agentLDX_McoSpindleRightCool_C // Spindle stopLDX_McoSpindleOrientate_C // Orientate spindle


Item syntax NC.Chan.ActSpindleMovements,(1) Read: yes; Write: no; Call: no




Reading out the spindle movement functions in channel 1

Example SCP item NC.Chan.ActSpindleMovements,1

Access Read

Result Row/Col 0

0 LDX_McoSpindleRight_C (VT_I4) // clockwise rotation without cooling agent

1 LDX_McoSpindleStop_C (VT_I4) // Spindle stop

4.7 Other Process Data

Identifier NC.Chan.ProgramWindow Program section

Description The NC.Chan.ProgramWindow item supplies a section of the current main or subprogram. Thedesired window size of the program section can be parameterized, as well as the number of NCblocks before the active block. With read-protected subprograms and cycles, the calling programsupplies the section.

Beyond the program section (one BSTR per line), the answer data comprises the desired numberof preceding blocks, the actual number of preceding blocks, and a reference of the block preparedlast.

Note: Restriction: To date, the kernel does not yet supply theinformation which is the block prepared last. A correspondingfield provided in the answer data does not yet contain a validvalue.

Note: Restriction: To date, file protection is not evaluated yet!

Item syntax NC.Chan.ProgramWindow,(1),(2),(3) Read: yes; Write: no; Call: no


(2) = window size Integer format. Number of blocks in the result(maximum 40).

(3) = Number of preceding blocks Integer format. Number of blocks before the activeblock (maximum 10).



Example SCP item NC.Chan.ProgramWindow,3,40,10

Access Read

Result Row/Col 0

0 10 (VT_I4) 0 (VT_I4) 30 (VT_I4)

1 N010 X10 Y10 Z10 G0

2 N020 X20 Y20 Z20 G1 F2000

3 N030 X30 Y30 Z30

4 N040 X40 Y40 Z40

5 ...

Identifier NC.Chan.MessageWindow Programmed notes

Description The NC.Chan.MessageWindow SCP item supplies the current programmed notes. The kernelsupports channel-specific notes and non-channel-specific notes (-> MSG, GMSG); both types ofnotes are considered, as well as CPL outputs (-> MSG, GMSG

The window size, i.e. the number of supplied notes, can be specified; however, it is limited byreason of NC-internal resources (not more than 5 channel-specific notes and 5 non-channel-specific notes).

The result includes

• non-channel-specific notes -> (GMSG, ...

• channel-specific notes -> (MSG, ...

• CPL outputs -> PRINT#(0, ...

Note: Restriction: To date, the window size parameter has noeffect!

Item syntax NC.Chan.MessageWindow,(1),(2) Read: yes; Write: no; Call: no


(2) = window size Integer format. Number of notes in the result

Identifier NC.Chan.ActCallChain Subroutine nesting active

Description The NC.Chan.ActCallChain item supplies the current subroutine nesting. In each case, theprogram name including the path and the block number is supplied.

The subroutine nesting is supplied in relation to the active block; to date, subroutine nesting inrelation to the prepared block is not available.

Item syntax NC.Chan.ActCallChain,(1) Read: yes; Write: no; Call: no




Identification of the active subroutine nesting in channel 1

Example SCP item NC.Chan.ActCallChain,1

Access Read

Result Row/Col 0 1

0 /mnt/Testprogramm.cnc (VT_ BSTR) N235 (VT_ BSTR)

1 /mnt/UP-01.cnc (VT_ BSTR) N10 (VT_ BSTR)

2 /mnt/UP-2.cnc (VT_ BSTR) N23 (VT_ BSTR)

... ... (VT_ BSTR) ... (VT_ BSTR)

n ... (VT_ BSTR) ... (VT_ BSTR)

Identifier NC.Chan.UpCallFromNcBlock Identification of subroutine callups

Description The NC.Chan.UpCallFromNcBlock item is used to identify subroutine callups in a specified NCblock. On instantiation of the item, specify the path of the main program, the NC block, and thenumber of the channel in which the NC block is processed.

Subsequent reading of the item supplies the name of the subroutine including the path, if the blockcomprises a subroutine callup. If this is not the case, Read will supply a blank string.

Item syntax NC.Chan.UpCallFromNcBlock,(1),(2),(3) Read: yes; Write: no; Call: no


(2) = path of the main program BSTR (without slash at the end)

(3) = NC block BSTR

Identification of subroutine callups in an NC block

Example SCP item NC.Chan.UpCallFromNcBlock,1,/usr/user,"10 CALL /usrfep/subprogram.cnc"

Access Read

Result Row/Col 0

0 /usrfep/subprogram.cnc (VT_BSTR)



4.8 Mode of Operation, Program Selection, Reset, MDI etc.

Identifier NC.Chan.Cmd.ModeOfOperation Changing the NC mode of operation

Description The NC.Chan.Cmd.ModeOfOperation is used to change the mode of operation of the channel. Usethe LDX_SavOpModes enumerator to code the desired operating modes. This enumeration typecan have the following values:

LDX_SAV_OP_MODE_EMPTY_C // No active operating mode,LDX_SAV_OP_MODE_JOGGING_C // Jog mode,LDX_SAV_OP_MODE_REFERENCE_C // Traverse to reference point,LDX_SAV_OP_MODE_BLOCKSEARCH_C // Program restart,LDX_SAV_OP_MODE_MDI_C // Manual entry,LDX _SAV_OP_MODE_AUTOMATIC_C // Automatic: Part programs

// can be processed in subsequent block mode,LDX _SAV_OP_MODE_SINGLE_BLOCK_C // Program block: With 'NC start'

// individual blocks located// in the parts program// are processed. Block preparation// only starts with 'NC start'.

,LDX _SAV_OP_MODE_SINGLE_STEP_C // Single step: With 'NC start'// a single block is// passed to the interpolator for// processing

,LDX _SAV_OP_MODE_TEACH_C // reserved,LDX _SAV_OP_MODE_SUSPEND_C // reserved,LDX _SAV_OP_MODE_SINGLE_ACT_BLOCK_C // Single block: With 'NC start'

// all blocks which have been// generated and fully prepared on// the basis of a single block in the// parts program are transmitted// passed to the interpolator for// processing.

,LDX _SAV_OP_MODE_RETURN_TO_PATH_C // Program restart: Axes// can be removed from the contour// manually and restarted// automatically or// manually.

,LDX _SAV_OP_MODE_DEBUG_STEP_C // CPL-Debugger: Single blocks// located in the parts// program are processed.

,LDX_SAV_OP_MODE_DEBUG_CONT_C // CPL-Debugger: All blocks// up to the next breakpoint// are processed.

,LDX_SAV_OP_MODE_JOGGING_COORDS_C // Manual setting:// Movement in tool coordinates

See section 5.1 for a description of errors potentially occurring in connection with changing ofmodes of operation.

Item syntax NC.Chan.Cmd.ModeOfOperation,(1) Read: yes; Write: yes; Call:no


Selection of automatic mode in channel 1

Example SCP item NC.Chan.Cmd.ModeOfOperation,1

Access Write

Write-Data Row/Col 0

0 LDX _SAV_OP_MODE_AUTOMATIC_C (VT_I4) // Automatic mode



Identifier NC.Chan.Cmd.SelectProgram Program selection

Description The NC.Chan.Cmd.SelectProgram item is used to select a program in a specified channel. It isselected by writing the program name including the path. In addition to the program name of thedesired program, a start and an end block may be specified. Additional parameters are specifiedthrough flags. To this end, the LDX_SavFlags enumerator is available with the following values:

LDX_SAV_FLAG_LINK_BEFORE_READY_C // If this flag is set, a link run is performed// during selection. During this process,// and unless already available, a link table// is generated for this main program.// A link table is required if subroutine callups// or CPL elements exist in the// program.

,LDX_SAV_FLAG_RETURN_BY_READY_C // During selection, it is usually checked by means// of the mode of operation and the NC state whether// selection is permissible. Afterwards, the selection// is acknowledged. If this flag is set, acknowledgment will// take place only after selection is completed, i.e.// when the NC state is 'ready'.

,LDX_SAV_FLAG_DA_C // reserved,LDX_SAV_FLAG_REMOTE_C // reserved,LDX_SAV_FLAG_SUPERVISOR_C // reserved,LDX_SAV_FLAG_MDI_C // This flag must be set if axes are to be started

// in 'manual input' mode.,LDX_SAV_FLAG_PROCESSDELETE_C // If this flag is set, an active program

// or an active manual input is deselected// first.

,LDX_SAV_FLAG_AUTOSTART_C // In connection with LDX_SAV_FLAG_MDI_C:// The input block is started immediately. If the// specified channel is not active, the block// is started in this channel. Then, all NC blocks are// permitted. If the specified channel is active,// the block is treated like a switching function.// Restrictions:// -> LDX_SAV_FLAG_MACHINE_C

,LDX_SAV_FLAG_JOG_C // This flag must be set if axes are to be started// in 'jog mode' or// workpiece coordinates movements are to.// be performed in 'setup'// mode.

,LDX_SAV_FLAG_REFPT_C // This flag must be set if axes are to be started// in 'Traverse to reference point'// mode.

,LDX_SAV_FLAG_MACHINE_C // Switching function is effective in connection with// LDX_SAV_FLAG_MDI_C. The block is executed in parallel// to the specified channel. With switching// function, however, only auxiliary functions and// asynchronous axis movements are permissible.

,LDX_SAV_FLAG_PROCESSCHANGE_C // If this flag is set, a program which is already// active at the start of program is not aborted by// deselection but replaced by the newly// selected program, i.e. the modal states// are retained.// With manual input, the old string of characters// is replaced by the new one.

,LDX_SAV_FLAG_BUFFERED_INPUT_C // The buffered NC block selection is effective in connection// with LDX_SAV_FLAG_MDI_C. While// preceding blocks are still being processed,// blocks to follow can already be selected.

,LDX_SAV_FLAG_NO_CHAN_CHANGE_C // The specified channel is retained, and no implicit// to the autostart channel takes place

,LDX_SAV_FLAG_RSP_IMMEDIATELY_C // The job is acknowledged after processing and// not only when the block is active.

See section 5.1 for a description of errors potentially occurring in connection with programselection.

Item syntax NC.Chan.Cmd.SelectProgram,(1) Read: yes; Write: yes; Call: no




Selection of the program /mnt/mypartprogram in channel 2 without specification of start andend block; linking should be done before selection, and any selected program should bedeselected automatically.

Example SCP item NC.Chan.Cmd.SelectProgram,2

Access Write

Write-Data Row/Col 0 1 2 3

0 Program name

/mnt/mypartprogram

Startblock

""

End block

""

LDX_SAV_FLAG_LINK_BEFORE_READY_C |LDX_SAV_FLAG_PROCESSDELETE_C

Identifier NC.Chan.Cmd.MidProgramStartup NC restart

Description The NC.Chan.Cmd.MidProgramStartup item is used to parameterize program restart in thespecified channel. It is parameterized by writing the item.

On writing, the name of the main program is given. Furthermore, the program restart data (e.g.target block) is specified in the form of an XML string; additional parameters are specified by flags.To this end, the following values of the LDX_SavFlags enumerator are relevant:

LDX_SAV_FLAG_SET_INTERRUPTFCT_C // With this flag, asynchronous Ups can// be controlled. In StartBlock, the number// (1..8) is specified as string (e.g. "1"), in EndBlock// the job is specified.// Jobs for asynch. UP: log on "SETINT"// switch off "DISABLE"// re-activate "ENABLE"// delete "CLRINT"// start "START"

,LDX_SAV_FLAG_SET_SEARCHRUN_C // With this flag, settings for block// preprocessing can be made. The block// preprocessing data is specified as XML string. It// is enclosed by <SearchRun> and// </SearchRun>.

See section 5.1 for a description of errors potentially occurring in connection with blockpreprocessing.

Item syntax NC.Chan.Cmd.MidProgramStartup,(1) Read: yes; Write: yes; Call: no


Program restart dataAll program restart data are transmitted in a string enclosed in the XMLtags <SearchRun> and </SearchRun>.

Position of the target block in the parts programSyntax: <DestPos>[Position]</DestPos>Defines the position of the target block in a main or subprogram.Position is the offset of the first character of the target block to theprogram start.The first block has position 0.The position is deleted with• NC start for further processing after program restart• change of mode of operation• reset• new specification• deleting via blank tags <DestPos></DestPos>



Note: If program restart is repeatedly started by means of<StartCmd>, processing in a loop can be continued at anyposition.

Subroutine of the target positionSyntax: <DestFName>[parts program]</DestFName>Specifies the parts program in which the target position is located. If noparts program is specified, the target position is searched in the mainprogram.If the name of the parts program does not contain an absolute path, it issearched in the search path of the main program.The name is deleted with• NC start for further processing after program restart• change of mode of operation• reset• new specification• deleting via blank tags <DestFName></DestFName>

Start NC program restartSyntax: <StartCmd>[commands]</StartCmd>Starts program restart and controls various strategies for returning.The different commands are added and linked bit by bit,e.g.: Flags = LDX_PRsStartSearchRun_C | LDX_PRsAsupAfterRepos_C:• LDX_PRsStartSearchRun_C starts program restart at the start of

program, or for repeated start after a target block has been reached.In loops, the target block can be reached several times.Start is only effective• if the target position is set, and• the subroutine of the target position is set, or if the current

machining position is located in the main program and• program restart is the active operating mode.

• LDX_PRsUseNcCallChain_C uses the stored status structure to findthe target block.

• LDX_PRsActionBlkWhileRepos1_C activates the first action block. Itis executed after NC start for further processing, or - if applicable -after the first Asup.

• LDX_PRsActionBlkWhileRepos2_C activates the second actionblock. It is executed after the first action block.

• LDX_PRsActionBlkAfterRepos_C activates the third action block. It isexecuted after the end position of the target block has been reached.

• LDX_PRsAsupBeforeRepos_C activates the first Asup. It is startedfor further processing after the NC start.

• LDX_PRsAsupWhileRepos_C activates the second Asup. If is startedafter completion of the second action block, or - if none is activated -after the first Asup.

• LDX_PRsAsupAfterRepos_C activates the third Asup. It is startedafter the third action block, or - if it does not exist - after reaching theend position of the target block.

• LDX_PrsNcStartAfterWhileAsup_C requires NC start after the secondAsup.

• LDX_PRsNcStartAfterLastAsup_C requires NC start after the thirdAsup before machining can be continued.



The commands are deleted with• after completion of all action blocks and Asups• change of mode of operation• reset• deletion by means of <ResetCmd>...</ResetCmd>

Delete program restart commandsSyntax: <ResetCmd>[commands]</ResetCmd>Deletes the program restart commands. The commands to be deleted areset analog with <StartCmd>.

Store subroutine nestingSyntax: <StoreCallChain>1</StoreCallChain>Stores a status structure consisting of a call chain in a channel. It can beset for the next program restart after processing has been stopped.It is deleted with a new specification, or with< StoreCallChain ></ StoreCallChain >.

Logging on various action blocksSyntax: <ActionBlkWhile1>[NC block]</ActionBlkWhile1>Syntax: <ActionBlkWhile2>[NC block]</ActionBlkWhile2>Syntax: <ActionBlkAfter>[NC block]</ActionBlkAfter>Logs on action blocks. Two action blocks can be called during returning tothe contour, and one after.Parameter :• NC block

NC block with maximum length LDX_McoMaxNcBlockSize_C

It is deleted with a new specification, or with<ActionBlk...></ActionBlk...> gelöscht.

Logging on various AsupsSyntax: <AsupBefore>[path name] [selection flags]</AsupBefore>Syntax: <AsupWhile>[path name] [selection flags]</AsupWhile>Syntax: <AsupAfter>[path name] [selection flags]</AsupAfter>Logs on Asups. They can be called before, during, or after returning to thecontour.Parameter :• Path name of the Asup

If no path is specified, the system searches in the path of the mainprogram.

• Selection flagsSelection flags of the program selection LDX_SavProcessCreate. Thefollowing are significant:LDX_SAV_FLAG_LINK_BEFORE_READY_C for linking, andLDX_SAV_FLAG_AUTOSTART_C for automatic start of this Asup.

It is deleted with a new specification, or with<Asup...></Asup...>.



Example"/usrfep/sekt.cnc" is to be selected. Target is block N20. Program restartis to be started immediately in the Program restart mode. After NC startfor further processing, an action block is to be started, and after reachingthe target position the Asup "sektAsup.cpl" is to be started from /usrfep.

Beispiel.jpg

Fig. 4-2: Example

SVString =<SearchRun><DestPos>25</DestPos><DestFName>/usrfep/sekt.cnc</DestFName>// not required in this case// Start (1) with activation of action block 1 (2) andAsup 3 (64)(=67)<StartCmd>67</StartCmd>// Asup is to be selected with linking (1) andautostart (128).<AsupAfter>sektAsup.cpl 129</AsupAfter><ActionBlkWhile1>M99 S1000</ActionBlkWhile1></SearchRun>

Program restart with selected program '/mnt/sekt.cnc' in channel 1.

Example SCP item NC.Chan.Cmd.MidProgramStartup,1

Access Write

Write-Data Row/Col 0 1 2 3

0 Program name

""

(VT_BSTR)

Program restart data

SVString

(VT_BSTR)

Reserved

(VT_EMPTY)

Flags

LDX_SAV_FLAG_ SET_SEARCHRUN_C

(VT_I4)



Identifier NC.Chan.Cmd.SearchBlock Search block

Description The NC.Chan.Cmd.SearchBlock item positions on the specified NC block within the selected mainprogram. Search block is possible only within the main program. Optionally, an end block can bespecified in addition to the start block; program execution will then run up to this block.

The Search block function is initiated by writing the item. The start block and end block parameter(codes) are transmitted in the form of a string. Searching takes place according to the followingconvention:

Spaces (blanks, tabs, lf, etc.) at the start of an NC block are ignored.

If the code starts with a number and the code is not found, it is searched once more accord toN<code>, e.g. code "50" will find the NC block N50x100...

If the code ends in a number, no other numbers may follow in the found NC block; e.g. code"G1X10" will not find the NC block "G1x100".

If the code ends in a letter, a space must follow in the found NC block; e.g. code "50A" will find theNC block "50A = 1" but not "50A=1".

Furthermore, an NC block will be found if code and the start of the NC block are identical; code"G1" for example will find "G1F1000", code "100" will find "100 A=1", code "100" will find"N100G1", or code "N100" will find "N100G1".

When the codes are found, processing will start with the block of the start-code and will end withthe block with the end-code. If there is information missing, or if a code is not found, processing willstart at the start of program and ends at end of program. After the end of search, the NC state willchange to 'ready' (LDX_SAV_OP_STATE_READY_C).

Item syntax NC.Chan.Cmd.SearchBlock,(1) Read: yes; Write: yes; Call: no


Block search in channel 1, no end block is specified

Example SCP item NC.Chan.Cmd.SearchBlock,1

Access Write

Write-Data Row/Col 0 1

0 Start block

N545

(VT_BSTR)

End block

(VT_EMPTY)



Identifier NC.Chan.Cmd.Reset Channel reset

Description The NC.Chan.Cmd.Reset item is used to reset a channel. Reset is initiated by writing the item.Additional parameters are specified through flags. To this end, the LDX_SavRFlags enumerator isavailable with the following values:

LDX_SAV_RFLAG_NORESELECT_C// This flag must be set if in case of// reset, the implicit automatic// program reselection is to be// hidden.

See section 5.1 for a description of errors potentially occurring in connection with reset.

Item syntax NC.Chan.Cmd.Reset,(1) Read: yes; Write: yes; Call: no


Reset in channel 3

Example SCP item NC.Chan.Cmd.Reset,3

Access Write


0 0



Identifier NC.Chan.Cmd.MDI MDI

Description The NC.Chan.Cmd.MDI item provides for transfer of one or several manual input blocks to aspecified channel. Additional parameters are specified through flags. To this end, theLDX_SavFlags enumerator is available with the following values:

LDX_SAV_FLAG_LINK_BEFORE_READY_C // If this flag is set, a link run is performed// during selection. During this process,// and unless already available, a link table// is generated for this main program.// A link table is required if subroutine callups// or CPL elements exist in the// program.

,LDX_SAV_FLAG_RETURN_BY_READY_C // During selection, it is usually checked by means// of the mode of operation and the NC state whether// selection is permissible. Afterwards, the selection// is acknowledged. If this flag is set, acknowledgment will// take place only after selection is completed, i.e.// when the NC state is 'ready'.

,LDX_SAV_FLAG_DA_C // reserved,LDX_SAV_FLAG_REMOTE_C // reserved,LDX_SAV_FLAG_SUPERVISOR_C // reserved,LDX_SAV_FLAG_MDI_C // This flag must be set if axes are to be started

// in 'manual input' mode.,LDX_SAV_FLAG_PROCESSDELETE_C // If this flag is set, an active program

// or an active manual input is deselected// first.

,LDX_SAV_FLAG_AUTOSTART_C // In connection with LDX_SAV_FLAG_MDI_C:// The input block is started immediately. If the// specified channel is not active, the block// is started in this channel. Then, all NC blocks are// permitted. If the specified channel is active,// the block is treated like a switching function.// Restrictions:// -> LDX_SAV_FLAG_MACHINE_C

,LDX_SAV_FLAG_JOG_C // This flag must be set if axes are to be started// in 'jog mode' or// workpiece coordinates movements are to.// be performed in 'setup'// mode.

,LDX_SAV_FLAG_REFPT_C // This flag must be set if axes are to be started// in 'Traverse to reference point'// mode.

,LDX_SAV_FLAG_MACHINE_C // Switching function is effective in connection with// LDX_SAV_FLAG_MDI_C. The block is executed in parallel// to the specified channel. With switching// function, however, only auxiliary functions and// asynchronous axis movements are permissible.

,LDX_SAV_FLAG_PROCESSCHANGE_C // If this flag is set, a program which is already// active at the start of program is not aborted by// deselection but replaced by the newly// selected program, i.e. the modal states// are retained.// With manual input, the old string of characters// is replaced by the new one.

,LDX_SAV_FLAG_BUFFERED_INPUT_C // The buffered NC block selection is effective in connectionwith

// LDX_SAV_FLAG_MDI_C. While// preceding blocks are still being processed,// blocks to follow can already be selected.

,LDX_SAV_FLAG_NO_CHAN_CHANGE_C // The specified channel is retained, and no implicit// to the autostart channel takes place

,LDX_SAV_FLAG_RSP_IMMEDIATELY_C // The job is acknowledged after processing and// not only when the block is active.

The transferred NC blocks are converted from UNICODE to ANSI. Writing is only permissible afterthe end of the last manual input (successful or faulty). If errors occur, the write process isnegatively acknowledged.

See section 5.1 for a description of errors potentially occurring in connection with manual input.

Item syntax NC.Chan.Cmd.MDI,(1) Read: no; Write: yes; Call: no




The following restrictions apply for manual input data:

• If several blocks are transferred, processing is made "en bloc". Toprocess single blocks, each block must be transferred separately.

• CPL elements in the manual data are not permissible; however, asubroutine may be called in the manual input blocks.

• The kernel does not support "linking" before processing the manualinput blocks.

• The length of an NC block is limited to 511 characters.

• When several NC blocks are transferred, the total length is limited to 8kByte (equals 4 kByte in ANSI).

• Only LF ('\n') is permissible as end code.

MDI in channel 2

Example SCP item NC.Chan.Cmd.MDI,2

Access Write


0 LDX_SAV_FLAG_MDI_C (VT_I4)

1 N10 G1 F100 X35 (VT_BSTR)

2 N20 X45 Y37.5 (VT_BSTR)

Identifier NC.Chan.Cmd.ReturnToPath Return to path

Description The NC.Chan.Cmd.ReturnToPath item completes leaving the contour, i.e. logging of the leavingmovements is terminated. Further jog movements are no longer recorded.

Subsequent activation of NC restart causes return to path with the active return strategy.

Item syntax NC.Chan.Cmd.ReturnToPath,(1) Read: yes; Write: yes; Call: no


Initiation of return to the contour in channel 2.

Example SCP item NC.Chan.Cmd.ReturnToPath,2

Access Write




Identifier NC.Chan.ReturnToPathStrategy Return strategy

Description The NC.Chan.ReturnToPathStrategy item defines the return strategy. Reading of the item suppliesthe current return strategy, writing of the item changes the return strategy.

The return mode (manual, automatic, single block) is specified, as well as the return point (point ofinterruption, start of block, end of block).

The return mode is coded by means of the LDX_McoRetPathMode enumerator which can assumethe following values:

LDX_McoRetPathAutomatic_C // Automatic return to path,LDX_McoRetPathSingleBlock_C // Return to path with single block,LDX_McoRetPathManual_C // Manual returnThe LDX_McoRetPathPoint enumerator is provided for the return to path point; it can assume thefollowing values:

LDX_McoRetPathStartOfBlock_C // Return to point of start,LDX_McoRetPathEndOfBlock_C // Return to point of end,LDX_McoRetPathEndOfBlock_C // Return to point of interruption

Item syntax NC.Chan.ReturnToPathStrategy,(1) Read: yes; Write: yes; Call: no


Return strategy specified for channel 2:Automatic return to point of start

Example SCP item NC.Chan.ReturnToPathStrategy,2

Access Write

Write-Data Row/Col 0 1

0 LDX_MCoRetPathAutomatic_C LDX_MCoRetPathStartOfBlock_C

4.9 Channel Settings

Identifier NC.Chan.Cmd.SkipBlockMode Skip block

Description By means of the NC.Chan.Cmd.SkipBlockMode item, "Skip block" can be switched for thespecified channel.

Item syntax NC.Chan.Cmd.SkipBlockMode,(1) Read: yes; Write: yes; Call: no


Example SCP item NC.Chan.Cmd.SkipBlockMode,1

Access Write

Row/Col 0

0 TRUE (VT_BOOL)

Identifier NC.Chan.Cmd.OptionalStop Optional stop

Description By means of the NC.Chan.Cmd.OptionalStop item, "Optional stop" can be switched for thespecified channel.

Item syntax NC.Chan.Cmd.OptionalStop,(1) Read: yes; Write: yes; Call: no




Example SCP item NC.Chan.Cmd.OptionalStop,1

Access Write

Row/Col 0

0 TRUE (VT_BOOL)

OPC Interface Error Handling 5-1


5 Error HandlingTo provide the user with accurate information in case of error, StandardSCP Error Handling is supported, i.e. information on errors are madeavailable through the ISCPError interface. If an error occurs during theexecution of a called-up service, an SCP error code will be returned. If theSCP interface is used incorrectly (e.g. by faulty parameterization ongeneration of an item), standard error codes are returned.

If errors occur during execution of a called-up function (program selection,reading of a table etc.), the device-specific error codes SCPErrNACK3 toSCPErrNACK5 are returned.

Via the ISCPError interface, the Logical Device MTX supplies moredetailed information on the error in question:

• a brief description of the error in plain text,

• a detailed error code which allows for an exact analysis of the error,

• a detailed description of the error in plain text.

The following table gives an overview of the error information.

Error code ShortDescription DetailedNumber LongDescription

Standard error codes SCPErrFailed

...

SCPErrInvalidConfig

see SCP docu see SCP docu see SCP docu

NCS error SCPErrNACK3 Name of the NCSfunction

NCS error code Description of the NCSerror in plain text

Error of the NCSserver

SCPErrNACK4 Name of the NCSfunction

Error of the NCSserver

Description of the reportederror in plain text

Reserved SCPErrNACK5 Reserved Reserved Reserved

Error code SCPErrNACK3 signals that an NCS error has occurred. Thebrief description includes the name of the NCS function where the erroroccurred; the detailed error code and the detailed error description identifythe NCS error in more detail. In normal operation, these errors should notoccur.

Error code SCPErrNACK4 signals that during execution of an NCSfunction, the respective server signaled an error. Depending on thecalled-up function, this may be another server. Also in this case, a briefdescription of the error, the detailed error code from the server, as well asthe detailed error description are supplied. The server error codes areserver-specific, i.e. each server has its own error constants. This must betaken into consideration for the evaluation of the error code. For thisreason, the item documentation indicates which errors are relevant forthis item.

5-2 Error Handling OPC Interface


5.1 SAV Errors

The following table shows the error codes used by the SAV server; thesecodes may for example by signaled with change of operating mode,program selection, or reset.

LDX_SAV_SERVICEOK_C No error occurredLDX_SAV_ILLCHANNUMBER_C Addressed channel does not existLDX_SAV_CHANUSED_C Service cannot be provided as the channel is being used,

i.e. its current state does not allow for the action.LDX_SAV_CHANRESETTING_C Service cannot be provided yet as resetting the channel is

not completed.LDX_SAV_FILENAMETOOLONG_C Program name too long (not used to date)LDX_SAV_NOREFPKT_C The service requires approached reference pointsLDX_SAV_NOPROGRAM_C The selected program does not exist, or cannot be

executed.LDX_SAV_SERVICEINTERRUPTED_C With buffered NC block selection, writing in the buffer was

interrupted. A second instance had attempted to write to thebuffer at the same time.

LDX_SAV_ILLMODE_C Service cannot be executed because it is not permissible inthe current operating mode.

LDX_SAV_STATENOTREADY_C Channel cannot be started as the state of the channel is not'ready'.

LDX_SAV_NOTSELECTED_C Service cannot be executed as no program has beenselected.

LDX_SAV_EXECUTEFEEDHOLD_C Program cannot be deselected as this is not allows in thestate of the channel, e.g. state of Sav and Ipo is 'running'.

LDX_SAV_ILLREMLOC_C Not used to dateLDX_SAV_ILLSTATE_C Operating mode cannot be changed as the state of the

channel does not permit it.LDX_SAV_UNKNOWNLABEL_C The target of 'Search block' has not been found.LDX_SAV_STATENOTREADYFORPROGSTART_C 'Search block' not possible as, though the state of the

channel is 'ready', processing of the main program hasalready started (program is e.g. on M0).

LDX_SAV_NMBOFAXISEXCCEEDED_C In the specification of external NPVs, the number of axes istoo high.

LDX_SAV_NMBOFEXTZOFFSGRPSEXCCEEDED_C In the specification of external NPVs, the number of NPVgroups is too high.

LDX_SAV_UNKNOWNSYNTAX_C The specified syntax is not knownLDX_SAV_ILLTOOLCOMPINDEX_C Invalid index with specification of an ext. tool compensationLDX_SAV_NMBOFEXTTOOLCOMPSEXCCEEDED_C The number of compensations in the specification of an ext.

tool compensation is too high (possibly in connection withthe compensation index).

LDX_SAV_ILLTOOLCOMPTYPE_C Invalid format identification with specification of an ext. toolcompensation

LDX_SAV_ILLTOOLCOMPORIENTATION_C Invalid edge position with specification of an ext. toolcompensation

LDX_SAV_ILLTOOLCOMPGROUP_C Invalid compensation groupLDX_SAV_ILLAXISNUMBER_C Addressed axis not presentLDX_SAV_RUNTIMEERROR_C With an NC block selection with automatic start, a runtime

error was identified, e.g. a syntax error.LDX_SAV_BUFFER_OVERFLOW_C With a buffered NC block selection, a buffer has overflown.LDX_SAV_ILLCOORDFILTER_C The entry for the coordinate filter is not correct.LDX_SAV_VNCILLSTATE_C The entry for the VNC is not permissible because the VNC

state is not frozen.LDX_SAV_NOMEM_C No memory in the server. The requested data could not be

stored.LDX_SAV_ILLPARAM_C The NCS function has been given an invalid value;

therefore the server cannot supply the data.LDX_SAV_ILLREQUEST_C Internal errorLDX_SAV_ILLRESPONSE_C Internal error



LDX_SAV_FUNCTIONNOTIMPLEMENTED_C The addressed service is not available in this softwareversion.

LDX_SAV_EVDATAFAIL_C Internal error

5.2 MACODA Errors

The table below shows the error codes used by the MACODA server.They can occur when MACODA parameters are read.

LDX_MCA_OK_C No errorLDX_MCA_SQL_NOTFOUND_C Parameter not available in the current software version.LDX_MCA_INSUFFICIENT_MEMORY_C Insufficient memory for receipt of the called-up data.LDX_MCA_NO_GROUP_OR_AREA_VERSION_C No group or function area version exists for the specified

block code.

LDX_MCA_CHANNEL_SPECIFIC_PARAMETER_EXIST_CLDX_MCA_NO_CHANNEL_SPECIFIC_PARAMETER_CLDX_MCA_NO_CONCURRENT_EDIT_C

5.3 TAD Errors

The table below shows the error codes used by the table server. Theymay occur for example during read or write access to D compensationtables. The table server may also signal the XML error listed in Section5.7.

LDX_TAD_ERR_OK_C No error

LDX_TAD_ERR_INTERNAL_ERROR_C Internal error (see Wera error)LDX_TAD_ERR_SERVER_NOT_READY_C Server not ready (see Wera error)LDX_TAD_ERR_NAME2LONG_C Invalid length of a nameLDX_TAD_ERR_UNKNOWN_TABLETYPE_C Table type not recognized

LDX_TAD_ERR_TABLE_NOT_FOUND_C Table does not exist

LDX_TAD_ERR_TABLE_EXISTS_C Table does not exist

LDX_TAD_ERR_BAD_DATASIZE_C Data buffer too small

LDX_TAD_ERR_BAD_PATHSIZE_C Path buffer too small

LDX_TAD_ERR_BAD_SEGMENTPATHSIZE_C SegmentPath too small (internal)

LDX_TAD_ERR_SCHEMA_INIT_FAILED_C Error during initialization of the schema

LDX_TAD_ERR_BAD_NCS_MSG_C invalid NCS message (used only by .._X functions) (internal)

LDX_TAD_ERR_NO_MORE_MOD_EVENTS_C Maximum number of ModEvents reached. No moreModEvents can be generated.

LDX_TAD_ERR_UNKNOWN_MOD_EVENT_C Unknown EventId

LDX_TAD_ERR_MOD_EVENT_ALREADY_REQ_C ModEvent has already been requested

LDX_TAD_ERR_MOD_EVENT_DELETED_C Error code of an event request, after deletion of therespective ModEvent (no error)

LDX_TAD_ERR_CHAN_NUMB_TOO_BIG_C Number of channels too large

LDX_TAD_ERR_EXTENSION_C Erro in file extension

LDX_TAD_ERR_INSERT_AXIS_NOT_ALLOWED_C Insert axis only allowed for offset tables

LDX_TAD_ERR_DELETE_AXIS_NOT_ALLOWED_C Delete axis only allowed for offset tables

LDX_TAD_ERR_PATH_BLOCK_POS_INVALID_C Invalid Xpath for this function

LDX_TAD_ERR_MAX_NUMBER_AXES_REACHED_C Maximum number of axes reached

LDX_TAD_ERR_AXIS_POSITION_NOT_EXIST_C axis does not exist

LDX_TAD_ERR_INPUT_PARAMETER_C Invalid parameters

LDX_TAD_ERR_INVALID_SCHEMA_C Schema contains unexpected elements



LDX_TAD_ERR_NO_READ_ACCESS_FOR_FILE_C No read privileges for the file

LDX_TAD_ERR_NO_WRITE_ACCESS_FOR_FILE_C No write privileges for the file

LDX_TAD_ERR_TABLE_REC_TOO_BIG_C Table record is too large - it must be transferable with anNCS response

LDX_TAD_XML_ERR_NOT_IMPLEMENTED_C See section 5.7

...

5.4 DBD Error

The following table shows the error codes which may occur during accessto database tables. Here, the XML error listed in Section 5.7 may occur aswell.

LDX_DBD_ERR_OK_C No errorLDX_DBD_ERR_INTERNAL_ERROR_C Internal error (see Wera error)LDX_DBD_ERR_SERVER_NOT_READY_C Server not ready (see Wera error)LDX_DBD_ERR_NAME2LONG_C Invalid length of a nameLDX_DBD_ERR_UNKNOWN_TABLETYPE_C Table type not recognizedLDX_DBD_ERR_TABLE_NOT_FOUND_C Table does not existLDX_DBD_ERR_TABLE_EXISTS_C Table does not existLDX_DBD_ERR_BAD_DATASIZE_C Data buffer too smallLDX_DBD_ERR_BAD_PATHSIZE_C Path buffer too smallLDX_DBD_ERR_BAD_SEGMENTPATHSIZE_C SegmentPath too small (internal)LDX_DBD_ERR_SCHEMA_INIT_FAILED_C Error during initialization of the schemaLDX_DBD_ERR_BAD_NCS_MSG_C invalid NCS message (used only by .._X functions) (internal)LDX_DBD_ERR_NO_MORE_MOD_EVENTS_C Maximum number of ModEvents reached. No more

ModEvents can be generated.LDX_DBD_ERR_UNKNOWN_MOD_EVENT_C Unknown EventIdLDX_DBD_ERR_MOD_EVENT_ALREADY_REQ_C ModEvent has already been requestedLDX_DBD_ERR_MOD_EVENT_DELETED_C Error code of an event request, after deletion of the

respective ModEvent (no error)LDX_DBD_ERR_TABLE_REC_TOO_BIG_C Table record is too large - it must be transferable with an

NCS responseLDX_DBD_XML_ERR_NOT_IMPLEMENTED_C See section 5.7...

5.5 CFG Errors

The following table shows the error codes which may occur during accessto configuration data. Here, the XML error listed in Section 5.7 may occuras well.

LDX_CFG_ERR_OK_C No errorLDX_CFG_ERR_INTERNAL_ERROR_C Internal error (see Wera error)LDX_CFG_ERR_SERVER_NOT_READY_C Server not ready (see Wera error)LDX_CFG_ERR_NAME2LONG_C Invalid length of a nameLDX_CFG_ERR_BAD_DATASIZE_C Data buffer too smallLDX_CFG_ERR_BAD_PATHSIZE_C Path buffer too smallLDX_CFG_ERR_BAD_SEGMENTPATHSIZE_C SegmentPath too small (internal)LDX_CFG_ERR_SCHEMA_INIT_FAILED_C Error during initialization of the schemaLDX_CFG_ERR_BAD_NCS_MSG_C invalid NCS message (used only by .._X functions) (internal)LDX_CFG_ERR_NO_MORE_MOD_EVENTS_C Maximum number of ModEvents reached. No more

ModEvents can be generated.LDX_CFG_ERR_UNKNOWN_MOD_EVENT_C Unknown EventIdLDX_CFG_ERR_MOD_EVENT_ALREADY_REQ_C ModEvent has already been requestedLDX_CFG_ERR_MOD_EVENT_DELETED_C Error code of an event request, after deletion of the

respective ModEvent (no error)LDX_CFG_ERR_INVALID_MODE_C Invalid mode.LDX_CFG_ERR_INVALID_ROOT_ELEM_C Invalid root element

LDX_CFG_ERR_CORRUPT_DATA_GROUP_C Data group has not been correctly initialized

LDX_CFG_ERR_FILE_ACCESS_ERROR_C Error on access to a file



LDX_CFG_ERR_INVALID_USER_ID_C Invalid user code

LDX_CFG_ERR_NO_MCA_INFO_C Element does not contain MACODA information in theschema

LDX_CFG_ERR_INVALID_MCA_INFO_C Element contains invalid MACODA information in theschema

LDX_CFG_ERR_NO_CONVERSION_CLASS_DEFINED_C

For the configuration data element, no MACODA CFGillustration class is defined.

LDX_CFG_ERR_CONVERSION_CLASS_NOT_VALID_C

For the configuration data element, no valid MACODA CFGillustration class is defined.

LDX_CFG_ERR_NO_CONVERSION_FUNC_DEFINED_C

For the configuration data element, no MACODA CFGconversion class is defined.

LDX_CFG_ERR_CONVERSION_CLASS_1_NOT_ALLOWED_C

For the configuration data element, MACODA CFGconversion class 1 (no illustration) is not permissible.

LDX_CFG_ERR_MACODA_ID_NOT_IN_CONVERSION_TABLE_C

For the specified MACODA block number, there is not entryin the MACODA CFG conversion table.

LDX_CFG_ERR_OPEN_MACODA_BLOCK_FAILED_C

Opening of an MACODA block has failed.

LDX_CFG_ERR_XMLSTRING_EMPTY_C The transferred XML string is empty

LDX_CFG_ERR_NO_STARTTAG_IN_XMLSTRING_C The transferred XML string has no start TAG

LDX_CFG_ERR_NO_ENDTAG_IN_XMLSTRING_C The transferred XML string has no end TAG

LDX_CFG_ERR_READ_MACODA_PARA_FAILED_C Reading of an MACODA block has failed.

LDX_CFG_ERR_WRITE_MACODA_PARA_FAILED_C Writing of an MACODA block has failed.

LDX_CFG_ERR_CLOSE_MACODA_BLOCK_FAILED_C

Writing of an MACODA block has failed

LDX_CFG_ERR_XMLSTRING_BUFFER_TOO_SMALL_C

Insufficient buffer for the XML data

LDX_CFG_ERR_NO_CONVERSION_PATH_DEFINED_C

No conversion path is defined in the conversion table forconversion of a MACODA parameter into CFG data

LDX_CFG_ERR_INVALID_CONVERSION_PATH_C An incorrect conversion path is defined in the conversiontable for conversion of a MACODA parameter into CFG data

LDX_CFG_ERR_UNEXPECTED_XPATH_ELEMENT_C

The converted XPath or an XPath in the MACODA CFGconversion table contains an unexpected input

LDX_CFG_XML_ERR_NOT_IMPLEMENTED_C See section 5.7...

5.6 SD Errors

The following table shows the error codes which may occur during accessto system data. Here, the XML error listed in Section 5.7 may occur aswell.

LDX_SD_ERR_OK_C No errorLDX_SD_ERR_INTERNAL_ERROR_C Internal error (see Wera error)LDX_SD_ERR_SERVER_NOT_READY_C Server not ready (see Wera error)LDX_SD_ERR_NAME2LONG_C Invalid length of a nameLDX_SD_ERR_BAD_DATASIZE_C Data buffer too smallLDX_SD_ERR_BAD_PATHSIZE_C Path buffer too smallLDX_SD_ERR_BAD_SEGMENTPATHSIZE_C SegmentPath too small (internal)LDX_SD_ERR_SCHEMA_INIT_FAILED_C Error during initialization of the schemaLDX_SD_ERR_BAD_NCS_MSG_C invalid NCS message (used only by .._X functions) (internal)LDX_SD_ERR_NO_MORE_MOD_EVENTS_C Maximum number of ModEvents reached. No more

ModEvents can be generated.LDX_SD_ERR_UNKNOWN_MOD_EVENT_C Unknown EventIdLDX_SD_ERR_MOD_EVENT_ALREADY_REQ_C ModEvent has already been requestedLDX_SD_ERR_MOD_EVENT_DELETED_C Error code of an event request, after deletion of the

respective ModEvent (no error)LDX_SD_ERR_INVALID_MODE_C Invalid mode.LDX_SD_ERR_INVALID_ROOT_ELEM_C Invalid root elementLDX_SD_ERR_CORRUPT_DATA_GROUP_C Data group has not been correctly initializedLDX_SD_ERR_FILE_ACCESS_ERROR_C Error on access to a fileLDX_SD_ERR_INVALID_USER_ID_C Invalid user code



LDX_SD_XML_ERR_NOT_IMPLEMENTED_C See section 5.7...

5.7 XML Errors

The following table shows XML error codes which are used when file-based and database-based tables are accessed. For XML errors, anenumerator of their own is provided. Furthermore, the enumerators forfile-based tables and database-based tables contain the XML errors.

LDX_XML_ERR_OK_C No error

LDX_XML_ERR_NOT_IMPLEMENTED_C Function not implemented yet

LDX_XML_ERR_INTERNAL_ERROR_C Internal error (see Wera error)

LDX_XML_ERR_SCHEMA_PARSE_FAILED_C Error on parsing the schema file (see Wera error)

LDX_XML_ERR_UNKNOWN_LIBXML_ERROR_C Unknown error from the libxml

LDX_XML_ERR_FOPEN_FAILED_C Error while opening the file

LDX_XML_ERR_MAX_OCCURS_EXCEEDED_C Parser error: there are more elements than permittedaccording to maxOccurs

LDX_XML_ERR_BAD_ELEM_CONTENT_C Parser error: Contents of the element does not correspondto data type acc. to schema

LDX_XML_ERR_PATH_SYNTAX_ERROR_C Syntax error in the path string

LDX_XML_ERR_PATH_CONFLICT_C Segment path is not located within root path (internal)

LDX_XML_ERR_PATH_ELEM_POS_INVALID_C Element position not permitted according to schema (path)

LDX_XML_ERR_PATH_ELEM_CREATE_FAILED_C An element specified via path cannot be generated

LDX_XML_ERR_PATH_ELEM_DELETE_FAILED_C The element specified using Path cannot be deleted

LDX_XML_ERR_PATH_ELEM_NOT_EXISTING_C The element specified via path does not exist in the XMLfiles

LDX_XML_ERR_PATH_ELEM_NOT_DECLARED_C The element specified via path is not declared in the schema

LDX_XML_ERR_PATH_ELEM_MISMATCH_C The last element in path is not identical with the first elementin data

LDX_XML_ERR_ELEM_NOT_DECLARED_C The element of the XML file or XML string is not declared inthe schema

LDX_XML_ERR_INVALID_DATA_SIZE_C The data size does not fit the specified element

LDX_XML_ERR_INVALID_TYPE_ID_C The data type does not fit the specified element

LDX_XML_ERR_TOO_MUCH_DATA_REQUESTED_C Too much binary data have been requested

LDX_XML_LIBERR_INTERNAL_ERROR_CLDX_XML_LIBERR_NO_MEMORY_CLDX_XML_LIBERR_DOCUMENT_START_CLDX_XML_LIBERR_DOCUMENT_EMPTY_CLDX_XML_LIBERR_DOCUMENT_END_CLDX_XML_LIBERR_INVALID_HEX_CHARREF_CLDX_XML_LIBERR_INVALID_DEC_CHARREF_CLDX_XML_LIBERR_INVALID_CHARREF_CLDX_XML_LIBERR_INVALID_CHAR_CLDX_XML_LIBERR_CHARREF_AT_EOF_CLDX_XML_LIBERR_CHARREF_IN_PROLOG_CLDX_XML_LIBERR_CHARREF_IN_EPILOG_CLDX_XML_LIBERR_CHARREF_IN_DTD_CLDX_XML_LIBERR_ENTITYREF_AT_EOF_CLDX_XML_LIBERR_ENTITYREF_IN_PROLOG_CLDX_XML_LIBERR_ENTITYREF_IN_EPILOG_CLDX_XML_LIBERR_ENTITYREF_IN_DTD_CLDX_XML_LIBERR_PEREF_AT_EOF_CLDX_XML_LIBERR_PEREF_IN_PROLOG_CLDX_XML_LIBERR_PEREF_IN_EPILOG_CLDX_XML_LIBERR_PEREF_IN_INT_SUBSET_CLDX_XML_LIBERR_ENTITYREF_NO_NAME_CLDX_XML_LIBERR_ENTITYREF_SEMICOL_MISSING_C



LDX_XML_LIBERR_PEREF_NO_NAME_CLDX_XML_LIBERR_PEREF_SEMICOL_MISSING_CLDX_XML_LIBERR_UNDECLARED_ENTITY_CLDX_XML_LIBWAR_UNDECLARED_ENTITY_CLDX_XML_LIBERR_UNPARSED_ENTITY_CLDX_XML_LIBERR_ENTITY_IS_EXTERNAL_CLDX_XML_LIBERR_ENTITY_IS_PARAMETER_CLDX_XML_LIBERR_UNKNOWN_ENCODING_CLDX_XML_LIBERR_UNSUPPORTED_ENCODING_CLDX_XML_LIBERR_STRING_NOT_STARTED_CLDX_XML_LIBERR_STRING_NOT_CLOSED_CLDX_XML_LIBERR_NS_DECL_ERROR_CLDX_XML_LIBERR_ENTITY_NOT_STARTED_CLDX_XML_LIBERR_ENTITY_NOT_FINISHED_CLDX_XML_LIBERR_LT_IN_ATTRIBUTE_CLDX_XML_LIBERR_ATTRIBUTE_NOT_STARTED_CLDX_XML_LIBERR_ATTRIBUTE_NOT_FINISHED_CLDX_XML_LIBERR_ATTRIBUTE_WITHOUT_VALUE_CLDX_XML_LIBERR_ATTRIBUTE_REDEFINED_CLDX_XML_LIBERR_LITERAL_NOT_STARTED_CLDX_XML_LIBERR_LITERAL_NOT_FINISHED_CLDX_XML_LIBERR_COMMENT_NOT_FINISHED_CLDX_XML_LIBERR_PI_NOT_STARTED_CLDX_XML_LIBERR_PI_NOT_FINISHED_CLDX_XML_LIBERR_NOTATION_NOT_STARTED_CLDX_XML_LIBERR_NOTATION_NOT_FINISHED_CLDX_XML_LIBERR_ATTLIST_NOT_STARTED_CLDX_XML_LIBERR_ATTLIST_NOT_FINISHED_CLDX_XML_LIBERR_MIXED_NOT_STARTED_CLDX_XML_LIBERR_MIXED_NOT_FINISHED_CLDX_XML_LIBERR_ELEMCONTENT_NOT_STARTED_CLDX_XML_LIBERR_ELEMCONTENT_NOT_FINISHED_CLDX_XML_LIBERR_XMLDECL_NOT_STARTED_CLDX_XML_LIBERR_XMLDECL_NOT_FINISHED_CLDX_XML_LIBERR_CONDSEC_NOT_STARTED_CLDX_XML_LIBERR_CONDSEC_NOT_FINISHED_CLDX_XML_LIBERR_EXT_SUBSET_NOT_FINISHED_CLDX_XML_LIBERR_DOCTYPE_NOT_FINISHED_CLDX_XML_LIBERR_MISPLACED_CDATA_END_CLDX_XML_LIBERR_CDATA_NOT_FINISHED_CLDX_XML_LIBERR_RESERVED_XML_NAME_CLDX_XML_LIBERR_SPACE_REQUIRED_CLDX_XML_LIBERR_SEPARATOR_REQUIRED_CLDX_XML_LIBERR_NMTOKEN_REQUIRED_CLDX_XML_LIBERR_NAME_REQUIRED_CLDX_CFG_ERR_NO_STARTTAG_IN_XMLSTRING_CLDX_XML_LIBERR_URI_REQUIRED_CLDX_XML_LIBERR_PUBID_REQUIRED_CLDX_XML_LIBERR_LT_REQUIRED_CLDX_XML_LIBERR_GT_REQUIRED_CLDX_XML_LIBERR_LTSLASH_REQUIRED_CLDX_XML_LIBERR_EQUAL_REQUIRED_CLDX_XML_LIBERR_TAG_NAME_MISMATCH_CLDX_XML_LIBERR_TAG_NOT_FINISHED_CLDX_XML_LIBERR_STANDALONE_VALUE_CLDX_XML_LIBERR_ENCODING_NAME_CLDX_XML_LIBERR_HYPHEN_IN_COMMENT_CLDX_XML_LIBERR_INVALID_ENCODING_CLDX_XML_LIBERR_EXT_ENTITY_STANDALONE_CLDX_XML_LIBERR_CONDSEC_INVALID_CLDX_XML_LIBERR_VALUE_REQUIRED_CLDX_XML_LIBERR_NOT_WELL_BALANCED_CLDX_XML_LIBERR_EXTRA_CONTENT_C



LDX_XML_LIBERR_ENTITY_CHAR_ERROR_CLDX_XML_LIBERR_ENTITY_PE_INTERNAL_CLDX_XML_LIBERR_ENTITY_LOOP_CLDX_XML_LIBERR_ENTITY_BOUNDARY_CLDX_XML_LIBERR_INVALID_URI_CLDX_XML_LIBERR_URI_FRAGMENT_CLDX_XML_LIBWAR_CATALOG_PI_CLDX_XML_LIBERR_NO_DTD_C

5.8 TAR Errors

The following table shows the error codes which may occur duringarchiving. If one of the errors listed in the table occurs, archiving isstopped. In this case, the information in the log file will be invalid.

LDX_TAR_ERR_OK_C Archiving or reading in the archive has been completedsuccessfully, further information has been logged.

,LDX_TAR_ERR_NCS_C An NCS error has occurred,LDX_TAR_ERR_BAD_PARAMETERS_C Incorrect parameter,LDX_TAR_ERR_OPENING_ARCHIVE_C Error during opening the archive,LDX_TAR_ERR_WRITING_ARCHIVE_C Error during writing archives,LDX_TAR_ERR_READING_ARCHIVE_C Error during reading archives,LDX_TAR_ERR_CHDIR_C Error during change to the target directory,LDX_TAR_ERR_LOGFILE_C Error during generating or writing the log file,LDX_TAR_ERR_MACODA_C Error during editing the MACODA parameters,LDX_TAR_ERR_TABLES_C Error during editing the tables

,LDX_TAR_ERR_CPLVARS_C Error during editing of the permanent CPL-variables,LDX_TAR_ERR_DATAMODULES_C Error during processing of the remanent data,LDX_TAR_ERR_MARKERS_C Error during processing of the remanent data,LDX_TAR_ERR_FORMAT_C Incorrect archive format,LDX_TAR_ERR_USRFEP_C Error during programming the user FEPROM,LDX_TAR_ERR_ENOMEM_C Insufficient memory,LDX_TAR_ERR_ALREADY_ACTIVE_C Archives already running,LDX_TAR_ERR_NOLOGIN_C Incorrect login at the file server,LDX_TAR_ERR_PLCSTATE_RUN_C PLC is not in STOP state

During archiving, a log file is written which lists all saved or restored files,as well as any errors. The error codes listed in the log file are shown inthe following table:

LDX_TAR_LOG_OK_C File processed without error,LDX_TAR_LOG_NOT_YET_PROCESSED_C File not processed (yet)

,LDX_TAR_LOG_STAT_FAILED_C Error on calling up the stat function

,LDX_TAR_LOG_SKIPPED_C File or directory not processed (no error!)

,LDX_TAR_LOG_PATH_NOT_OPENED_C Directory could not be opened.

,LDX_TAR_LOG_READING_C Error during reading file.

,LDX_TAR_LOG_EACCESS_C Access to file not possible.

,LDX_TAR_LOG_EEXIST_C File already exists

,LDX_TAR_LOG_ENOENT_C File not found.

,LDX_TAR_LOG_ENOMEM_C No memory

,LDX_TAR_LOG_EROFS_C Read-only file system

,LDX_TAR_LOG_MODE_DIFF_C Different protections

,LDX_TAR_LOG_SIZE_DIFF_C Different size

,LDX_TAR_LOG_MTIME_DIFF_C Different date

,LDX_TAR_LOG_OTHER_DIFF_C Different file dates

,LDX_TAR_LOG_FILE_DATA_DIFF_C Other differences

,LDX_TAR_LOG_TIME_MODE_C Date/Protection not restored

,LDX_TAR_LOG_MKDIR_FAILED_C Error creating a directory

,LDX_TAR_LOG_ERR_UNKNOWN_C unknown error



,LDX_TAR_LOG_LOADING_MACODA_C Error during transfer of MACODA

,LDX_TAR_LOG_LOADING_TABLE_C Error during transfer of tool table

,LDX_TAR_LOG_CORRUPTED_C File corrupted

,LDX_TAR_LOG_WRITE_ENABLED_C Write protection changed

,LDX_TAR_LOG_DATAMODULES_C Error during transfer of remanent PLC data

,LDX_TAR_LOG_MARKERS_C Error during transfer of remanent PLC data

,LDX_TAR_LOG_CPLVARS_C Error during transfer of CPL-variables

,LDX_TAR_LOG_RAMFS_NOTFOUND_C RAM file system not found in the archive

,LDX_TAR_LOG_USRFEPFS_NOTFOUND_C usrfep file system not found in the archive

,LDX_TAR_LOG_MACODA_NOTFOUND_C MACODA data not found in the archive

,LDX_TAR_LOG_TABLE_NOTFOUND_C Tool table not in archives

,LDX_TAR_LOG_DATAMODULES_NOTFOUND_C Remanent PLC data not found in the archive

,LDX_TAR_LOG_MARKERS_NOTFOUND_C Remanent PLC data not found in the archive

,LDX_TAR_LOG_CPLVARS_NOTFOUND_C CPL variables not found in the archive

,LDX_TAR_LOG_SYSTEMDATA_NOTFOUND_C System data not in archives,LDX_TAR_LOG_PLCSTATE_RUN_C PLC is not in STOP state

,LDX_TAR_LOG_SYSTEMDATA_C Error during transfer of system data

OPC Interface Index 6-1


6 Index

SSystem.ErrorStatus 2-6System.InfoStatus 2-7System.LogbookClear 2-11System.LogbookDevices 2-12System.LogbookStore 2-8System.LogbookStoreEx 2-10System.MessageReset 2-7System.MessageStatus 2-5System.MessageStore 2-3System.MessageStoreEx 2-4System.SetupStatus 2-7System.StartupStatus 2-7System.WarningStatus 2-7

6-2 Index OPC Interface


OPC Interface Service & Support 7-1


7 Service & Support

7.1 Helpdesk

Unser Kundendienst-Helpdesk im Hauptwerk Lohram Main steht Ihnen mit Rat und Tat zur Seite.Sie erreichen uns

Our service helpdesk at our headquarters in Lohr amMain, Germany can assist you in all kinds of inquiries.Contact us

- telefonisch - by phone: +49 (0) 9352 40 50 60über Service Call Entry Center Mo-Fr 07:00-18:00- via Service Call Entry Center Mo-Fr 7:00 am - 6:00 pm

- per Fax - by fax: +49 (0) 9352 40 49 41

- per e-Mail - by e-mail: [email protected]

7.2 Service-Hotline

Außerhalb der Helpdesk-Zeiten ist der Servicedirekt ansprechbar unter

After helpdesk hours, contact our servicedepartment directly at

+49 (0) 171 333 88 26

oder - or +49 (0) 172 660 04 06

7.3 Internet

Unter www.boschrexroth.com finden Sieergänzende Hinweise zu Service, Reparatur undTraining sowie die aktuellen Adressen *) unsererauf den folgenden Seiten aufgeführten Vertriebs-und Servicebüros.

Verkaufsniederlassungen

Niederlassungen mit Kundendienst

Außerhalb Deutschlands nehmen Sie bitte zuerst Kontakt mitunserem für Sie nächstgelegenen Ansprechpartner auf.

*) Die Angaben in der vorliegenden Dokumentation könnenseit Drucklegung überholt sein.

At www.boschrexroth.com you may findadditional notes about service, repairs and trainingin the Internet, as well as the actual addresses *) ofour sales- and service facilities figuring on thefollowing pages.

sales agencies

offices providing service

Please contact our sales / service office in your area first.

*) Data in the present documentation may have becomeobsolete since printing.

7.4 Vor der Kontaktaufnahme... - Before contacting us...

Wir können Ihnen schnell und effizient helfen wennSie folgende Informationen bereithalten:

1. detaillierte Beschreibung der Störung und derUmstände.

2. Angaben auf dem Typenschild der betreffendenProdukte, insbesondere Typenschlüssel undSeriennummern.

3. Tel.-/Faxnummern und e-Mail-Adresse, unterdenen Sie für Rückfragen zu erreichen sind.

For quick and efficient help, please have thefollowing information ready:

1. Detailed description of the failure andcircumstances.

2. Information on the type plate of the affectedproducts, especially type codes and serialnumbers.

3. Your phone/fax numbers and e-mail address,so we can contact you in case of questions.

7-2 Service & Support OPC Interface


7.5 Kundenbetreuungsstellen - Sales & Service Facilities

Deutschland - Germany vom Ausland: (0) nach Landeskennziffer weglassen!from abroad: don’t dial (0) after country code!

Vertriebsgebiet Mitte Germany Centre

Rexroth Indramat GmbHBgm.-Dr.-Nebel-Str. 2 / Postf. 135797816 Lohr am Main / 97803 Lohr

Kompetenz-Zentrum Europa

Tel.: +49 (0)9352 40-0Fax: +49 (0)9352 40-4885

S E R V I C E A U T O M A T I O N

C A L L E N T R Y C E N T E RH e l p d e s kMO – FR

von 07:00 - 18:00 Uhrfrom 7 am – 6 pm

Tel. +49 (0) 9352 40 50 60Fax +49 (0) 9352 40 49 41

[email protected]


H OTLIN E 24 / 7 / 365

außerhalb der Helpdesk-Zeitout of helpdesk hours

Tel.: +49 (0)172 660 04 06o d e r / o r

Tel.: +49 (0)171 333 88 26


ERSATZTEILE / SPARESverlängerte Ansprechzeit- extended office time -

♦ nur an Werktagen- only on working days -

♦ von 07:00 - 18:00 Uhr- from 7 am - 6 pm -

Tel. +49 (0) 9352 40 42 22

Vertriebsgebiet Süd Germany South

Bosch Rexroth AGLandshuter Allee 8-1080637 München

Tel.: +49 (0)89 127 14-0Fax: +49 (0)89 127 14-490

Vertriebsgebiet West Germany West

Bosch Rexroth AGRegionalzentrum WestBorsigstrasse 1540880 Ratingen

Tel.: +49 (0)2102 409-0Fax: +49 (0)2102 409-406

+49 (0)2102 409-430

Gebiet Südwest Germany South-West

Bosch Rexroth AGService-Regionalzentrum Süd-WestSiemensstr. 170736 Fellbach

Tel.: +49 (0)711 51046–0Fax: +49 (0)711 51046–248

Vertriebsgebiet Nord Germany North

Bosch Rexroth AGWalsroder Str. 9330853 Langenhagen

Tel.: +49 (0) 511 72 66 57-0Service: +49 (0) 511 72 66 57-256Fax: +49 (0) 511 72 66 57-93Service: +49 (0) 511 72 66 57-783

Vertriebsgebiet Mitte Germany Centre

Bosch Rexroth AGRegionalzentrum MitteWaldecker Straße 1364546 Mörfelden-Walldorf

Tel.: +49 (0) 61 05 702-3Fax: +49 (0) 61 05 702-444

Vertriebsgebiet Ost Germany East

Bosch Rexroth AGBeckerstraße 3109120 Chemnitz

Tel.: +49 (0)371 35 55-0Fax: +49 (0)371 35 55-333

Vertriebsgebiet Ost Germany East

Bosch Rexroth AGRegionalzentrum OstWalter-Köhn-Str. 4d04356 Leipzig

Tel.: +49 (0)341 25 61-0Fax: +49 (0)341 25 61-111



Europa (West) - Europe (West)

vom Ausland: (0) nach Landeskennziffer weglassen, Italien: 0 nach Landeskennziffer mitwählenfrom abroad: don’t dial (0) after country code, Italy: dial 0 after country code

Austria - Österreich

Bosch Rexroth GmbHElectric Drives & ControlsStachegasse 131120 Wien

Tel.: +43 (0) 1 985 25 40Fax: +43 (0) 1 985 25 40-93

Austria – Österreich

Bosch Rexroth GmbHElectric Drives & ControlsIndustriepark 184061 Pasching

Tel.: +43 (0)7221 605-0Fax: +43 (0)7221 605-21

Belgium - Belgien

Bosch Rexroth NV/SAHenri Genessestraat 11070 Bruxelles

Tel: +32 (0) 2 451 26 08Fax: +32 (0) 2 451 27 90 [email protected] [email protected]

Denmark - Dänemark

BEC A/SZinkvej 68900 Randers

Tel.: +45 87 11 90 60Fax: +45 87 11 90 61

Great Britain – Großbritannien

Bosch Rexroth Ltd.Electric Drives & ControlsBroadway Lane, South CerneyCirencester, Glos GL7 5UH

Tel.: +44 (0)1285 863000Fax: +44 (0)1285 863030 [email protected] [email protected]

Finland - Finnland

Bosch Rexroth OyElectric Drives & ControlsAnsatie 6017 40 Vantaa

Tel.: +358 (0)9 84 91-11Fax: +358 (0)9 84 91-13 60

France - Frankreich

Bosch Rexroth SASElectric Drives & ControlsAvenue de la Trentaine(BP. 74)77503 Chelles Cedex

Tel.: +33 (0)164 72-63 22Fax: +33 (0)164 72-63 20Hotline: +33 (0)608 33 43 28

France - Frankreich

Bosch Rexroth SASElectric Drives & ControlsZI de Thibaud, 20 bd. Thibaud(BP. 1751)31084 Toulouse

Tel.: +33 (0)5 61 43 61 87Fax: +33 (0)5 61 43 94 12

France – Frankreich

Bosch Rexroth SASElectric Drives & Controls91, Bd. Irène Joliot-Curie69634 Vénissieux – Cedex

Tel.: +33 (0)4 78 78 53 65Fax: +33 (0)4 78 78 53 62

Italy - Italien

Bosch Rexroth S.p.A.Via G. Di Vittorio, 120063 Cernusco S/N.MI

Hotline: +39 02 92 365 563Tel.: +39 02 92 365 1Service: +39 02 92 365 300Fax: +39 02 92 365 500Service: +39 02 92 365 516

Italy - Italien

Bosch Rexroth S.p.A.Via Paolo Veronesi, 25010148 Torino

Tel.: +39 011 224 88 11Fax: +39 011 224 88 30

Italy - Italien

Bosch Rexroth S.p.A.Via Mascia, 180053 Castellamare di Stabia NA

Tel.: +39 081 8 71 57 00Fax: +39 081 8 71 68 85

Italy - Italien

Bosch Rexroth S.p.A.Via del Progresso, 16 (Zona Ind.)35020 Padova

Tel.: +39 049 8 70 13 70Fax: +39 049 8 70 13 77

Italy - Italien

Bosch Rexroth S.p.A.Via Isonzo, 6140033 Casalecchio di Reno (Bo)

Tel.: +39 051 29 86 430Fax: +39 051 29 86 490

Netherlands - Niederlande/Holland

Bosch Rexroth Services B.V.Technical ServicesKruisbroeksestraat 1(P.O. Box 32)5281 RV Boxtel

Tel.: +31 (0) 411 65 19 51Fax: +31 (0) 411 67 78 14Hotline: +31 (0) 411 65 19 [email protected]

Netherlands – Niederlande/Holland

Bosch Rexroth B.V.Kruisbroeksestraat 1(P.O. Box 32)5281 RV Boxtel

Tel.: +31 (0) 411 65 16 40Fax: +31 (0) 411 65 14 83 www.boschrexroth.nl

Norway - Norwegen

Bosch Rexroth ASElectric Drives & ControlsBerghagan 1 or: Box 30071405 Ski-Langhus 1402 Ski

Tel.: +47 64 86 41 00

Fax: +47 64 86 90 62

Hotline: +47 64 86 94 82 [email protected]

Spain – Spanien

Goimendi AutomationParque Empresarial ZuatzuC/ Francisco Grandmontagne no.220018 San Sebastian

Tel.: +34 9 43 31 84 21- service: +34 9 43 31 84 56Fax: +34 9 43 31 84 27- service: +34 9 43 31 84 60 [email protected]

Spain - Spanien

Bosch Rexroth S.A.Electric Drives & ControlsCentro Industrial SantigaObradors s/n08130 Santa Perpetua de MogodaBarcelona

Tel.: +34 9 37 47 94 00Fax: +34 9 37 47 94 01

Spain - Spanien

Bosch Rexroth S.A.Electric Drives & Controlsc/ Almazara, 928760 Tres Cantos (Madrid)

Tel.: +34 91 806 24 79Fax: +34 91 806 24 72 [email protected]

Sweden - Schweden

Bosch Rexroth ABElectric Drives & Controls- Varuvägen 7(Service: Konsumentvägen 4, Älfsjö)125 81 Stockholm

Tel.: +46 (0) 8 727 92 00Fax: +46 (0) 8 647 32 77

Sweden - Schweden

Bosch Rexroth ABElectric Drives & ControlsEkvändan 7254 67 Helsingborg

Tel.: +46 (0) 4 238 88 -50Fax: +46 (0) 4 238 88 -74

Switzerland East - Schweiz Ost

Bosch Rexroth Schweiz AGElectric Drives & ControlsHemrietstrasse 28863 ButtikonTel. +41 (0) 55 46 46 111Fax +41 (0) 55 46 46 222

Switzerland West - Schweiz West

Bosch Rexroth Suisse SAAv. Général Guisan 261800 Vevey 1

Tel.: +41 (0)21 632 84 20Fax: +41 (0)21 632 84 21



Europa (Ost) - Europe (East)

vom Ausland: (0) nach Landeskennziffer weglassen from abroad: don’t dial (0) after country code

Czech Republic - Tschechien

Bosch -Rexroth, spol.s.r.o.Hviezdoslavova 5627 00 Brno

Tel.: +420 (0)5 48 126 358Fax: +420 (0)5 48 126 112

Czech Republic - Tschechien

DEL a.s.Strojírenská 38591 01 Zdar nad SázavouTel.: +420 566 64 3144Fax: +420 566 62 1657

Hungary - Ungarn

Bosch Rexroth Kft.Angol utca 341149 Budapest

Tel.: +36 (1) 422 3200Fax: +36 (1) 422 3201

Poland – Polen

Bosch Rexroth Sp.zo.o.ul. Staszica 105-800 Pruszków

Tel.: +48 (0) 22 738 18 00– service: +48 (0) 22 738 18 46Fax: +48 (0) 22 758 87 35– service: +48 (0) 22 738 18 42

Poland – Polen

Bosch Rexroth Sp.zo.o.Biuro Poznanul. Dabrowskiego 81/8560-529 Poznan

Tel.: +48 061 847 64 62 /-63Fax: +48 061 847 64 02

Romania - Rumänien

East Electric S.R.L.Bdul Basarabia no.250, sector 373429 Bucuresti

Tel./Fax:: +40 (0)21 255 35 07+40 (0)21 255 77 13

Fax: +40 (0)21 725 61 21 [email protected]

Romania - Rumänien

Bosch Rexroth Sp.zo.o.Str. Drobety nr. 4-10, app. 1470258 Bucuresti, Sector 2

Tel.: +40 (0)1 210 48 25+40 (0)1 210 29 50

Fax: +40 (0)1 210 29 52

Russia - Russland

Bosch Rexroth OOOWjatskaja ul. 27/15127015 Moskau

Tel.: +7-095-785 74 78+7-095 785 74 79

Fax: +7 095 785 74 77 [email protected]

Russia Belarus - Weissrussland

ELMIS10, Internationalnaya246640 Gomel, Belarus

Tel.: +375/ 232 53 42 70+375/ 232 53 21 69

Fax: +375/ 232 53 37 69 [email protected]

Turkey - Türkei

Bosch Rexroth OtomasyonSan & Tic. A..S.Fevzi Cakmak Cad No. 334630 Sefaköy Istanbul

Tel.: +90 212 413 34 00Fax: +90 212 413 34 17 www.boschrexroth.com.tr

Turkey - Türkei

Servo Kontrol Ltd. Sti.Perpa Ticaret Merkezi B BlokKat: 11 No: 160980270 Okmeydani-Istanbul

Tel: +90 212 320 30 80Fax: +90 212 320 30 81 [email protected] www.servokontrol.com

Slowenia - Slowenien

DOMELOtoki 2164 228 Zelezniki

Tel.: +386 5 5117 152Fax: +386 5 5117 225 [email protected]



Africa, Asia, Australia - incl. Pacific Rim

Australia - Australien

AIMS - Australian IndustrialMachinery Services Pty. Ltd.28 Westside DriveLaverton North Vic 3026Melbourne

Tel.: +61 3 93 14 3321Fax: +61 3 93 14 3329Hotlines: +61 3 93 14 3321

+61 4 19 369 195 [email protected]

Australia - Australien

Bosch Rexroth Pty. Ltd.No. 7, Endeavour WayBraeside Victoria, 31 95Melbourne

Tel.: +61 3 95 80 39 33Fax: +61 3 95 80 17 33 [email protected]

China

Shanghai Bosch RexrothHydraulics & Automation Ltd.Waigaoqiao, Free Trade ZoneNo.122, Fu Te Dong Yi RoadShanghai 200131 - P.R.China

Tel.: +86 21 58 66 30 30Fax: +86 21 58 66 55 [email protected][email protected]

China

Shanghai Bosch RexrothHydraulics & Automation Ltd.4/f, Marine TowerNo.1, Pudong AvenueShanghai 200120 - P.R.China

Tel: +86 21 68 86 15 88Fax: +86 21 58 40 65 77

China

Bosch Rexroth China Ltd.15/F China World Trade Center1, Jianguomenwai AvenueBeijing 100004, P.R.China

Tel.: +86 10 65 05 03 80Fax: +86 10 65 05 03 79

China

Bosch Rexroth China Ltd.Guangzhou Repres. OfficeRoom 1014-1016, Metro Plaza,Tian He District, 183 Tian He Bei RdGuangzhou 510075, P.R.China

Tel.: +86 20 8755-0030+86 20 8755-0011

Fax: +86 20 8755-2387

China

Bosch Rexroth (China) Ltd.A-5F., 123 Lian Shan StreetSha He Kou DistrictDalian 116 023, P.R.China

Tel.: +86 411 46 78 930Fax: +86 411 46 78 932

China

Melchers GmbHBRC-SE, Tightening & Press-fit13 Floor Est Ocean CentreNo.588 Yanan Rd. East65 Yanan Rd. WestShanghai 200001

Tel.: +86 21 6352 8848Fax: +86 21 6351 3138

Hongkong

Bosch Rexroth (China) Ltd.6th Floor,Yeung Yiu Chung No.6 Ind Bldg.19 Cheung Shun StreetCheung Sha Wan,Kowloon, Hongkong

Tel.: +852 22 62 51 00Fax: +852 27 41 33 44

[email protected]

India - Indien

Bosch Rexroth (India) Ltd.Electric Drives & ControlsPlot. No.96, Phase IIIPeenya Industrial AreaBangalore – 560058

Tel.: +91 80 51 17 0-211...-218Fax: +91 80 83 94 345

+91 80 83 97 374

[email protected]

India - Indien

Bosch Rexroth (India) Ltd.Electric Drives & ControlsAdvance House, II FloorArk Industrial CompoundNarol Naka, Makwana RoadAndheri (East), Mumbai - 400 059

Tel.: +91 22 28 56 32 90+91 22 28 56 33 18

Fax: +91 22 28 56 32 93

[email protected]

India - Indien

Bosch Rexroth (India) Ltd.S-10, Green Park ExtensionNew Delhi – 110016

Tel.: +91 11 26 56 65 25+91 11 26 56 65 27

Fax: +91 11 26 56 68 87

[email protected]

Indonesia - Indonesien

PT. Bosch RexrothBuilding # 202, CilandakCommercial EstateJl. Cilandak KKO, Jakarta 12560

Tel.: +62 21 7891169 (5 lines)Fax: +62 21 7891170 - [email protected]

Japan

Bosch Rexroth Automation Corp.Service Center JapanYutakagaoka 1810, Meito-ku,NAGOYA 465-0035, Japan

Tel.: +81 52 777 88 41+81 52 777 88 53+81 52 777 88 79

Fax: +81 52 777 89 01

Japan

Bosch Rexroth Automation Corp.Electric Drives & Controls2F, I.R. BuildingNakamachidai 4-26-44, Tsuzuki-kuYOKOHAMA 224-0041, Japan

Tel.: +81 45 942 72 10Fax: +81 45 942 03 41

Korea

Bosch Rexroth-Korea Ltd.Electric Drives and ControlsBongwoo Bldg. 7FL, 31-7, 1GaJangchoong-dong, Jung-guSeoul, 100-391

Tel.: +82 234 061 813Fax: +82 222 641 295

Korea

Bosch Rexroth-Korea Ltd.1515-14 Dadae-Dong, Saha-guElectric Drives & ControlsPusan Metropolitan City, 604-050

Tel.: +82 51 26 00 741Fax: +82 51 26 00 747 [email protected]

Malaysia

Bosch Rexroth Sdn.Bhd.11, Jalan U8/82, Seksyen U840150 Shah AlamSelangor, Malaysia

Tel.: +60 3 78 44 80 00Fax: +60 3 78 45 48 00 [email protected] [email protected]

Singapore - Singapur

Bosch Rexroth Pte Ltd15D Tuas RoadSingapore 638520

Tel.: +65 68 61 87 33Fax: +65 68 61 18 25 sanjay.nemade

@boschrexroth.com.sg

South Africa - Südafrika

TECTRA Automation (Pty) Ltd.71 Watt Street, MeadowdaleEdenvale 1609

Tel.: +27 11 971 94 00Fax: +27 11 971 94 40Hotline: +27 82 903 29 23 [email protected]

Taiwan

Bosch Rexroth Co., Ltd.Taichung Industrial AreaNo.19, 38 RoadTaichung, Taiwan 407, R.O.C.

Tel : +886 - 4 -235 08 383Fax: +886 - 4 -235 08 586 [email protected] [email protected]

Taiwan

Bosch Rexroth Co., Ltd.Tainan BranchNo. 17, Alley 24, Lane 737Chung Cheng N.Rd. YungkangTainan Hsien, Taiwan, R.O.C.

Tel : +886 - 6 –253 6565Fax: +886 - 6 –253 4754 [email protected]

Thailand

NC Advance Technology Co. Ltd.59/76 Moo 9Ramintra road 34Tharang, Bangkhen,Bangkok 10230

Tel.: +66 2 943 70 62 +66 2 943 71 21Fax: +66 2 509 23 62Hotline +66 1 984 61 52 [email protected]



Nordamerika - North AmericaUSAHeadquarters - Hauptniederlassung

Bosch Rexroth CorporationElectric Drives & Controls5150 Prairie Stone ParkwayHoffman Estates, IL 60192-3707

Tel.: +1 847 645-3600Fax: +1 847 [email protected] [email protected]

USA Central Region - Mitte

Bosch Rexroth CorporationElectric Drives & Controls1701 Harmon RoadAuburn Hills, MI 48326

Tel.: +1 248 393-3330Fax: +1 248 393-2906

USA Southeast Region - Südost

Bosch Rexroth CorporationElectric Drives & Controls2810 Premiere Parkway, Suite 500Duluth, GA 30097

Tel.: +1 678 957-4050Fax: +1 678 417-6637

USA SERVICE-HOTLINE

- 7 days x 24hrs -

+1-800-REXROTH+1 800 739-7684

USA Northeast Region – Nordost

Bosch Rexroth CorporationElectric Drives & Controls99 Rainbow RoadEast Granby, CT 06026

Tel.: +1 860 844-8377Fax: +1 860 844-8595

USA West Region – West

Bosch Rexroth CorporationElectric Drives & Controls7901 Stoneridge Drive, Suite 220Pleasanton, CA 94588

Tel.: +1 925 227-1084Fax: +1 925 227-1081

Canada East - Kanada Ost

Bosch Rexroth Canada CorporationBurlington Division3426 Mainway DriveBurlington, OntarioCanada L7M 1A8

Tel.: +1 905 335 5511Fax: +1 905 335 4184

[email protected]

Canada West - Kanada West

Bosch Rexroth Canada Corporation5345 Goring St.Burnaby, British ColumbiaCanada V7J 1R1

Tel. +1 604 205 5777Fax +1 604 205 6944

[email protected]

Mexico

Bosch Rexroth Mexico S.A. de C.V.Calle Neptuno 72Unidad Ind. Vallejo07700 Mexico, D.F.

Tel.: +52 55 57 54 17 11Fax: +52 55 57 54 50 [email protected]

Mexico

Bosch Rexroth S.A. de C.V.Calle Argentina No 3913Fracc. las Torres64930 Monterrey, N.L.

Tel.: +52 81 83 65 22 53+52 81 83 65 89 11+52 81 83 49 80 91

Fax: +52 81 83 65 52 80

Südamerika - South AmericaArgentina - Argentinien

Bosch Rexroth S.A.I.C."The Drive & Control Company"Rosario 2302B1606DLD CarapachayProvincia de Buenos Aires

Tel.: +54 11 4756 01 40+54 11 4756 02 40+54 11 4756 03 40+54 11 4756 04 40

Fax: +54 11 4756 01 36+54 11 4721 91 53

[email protected]

Argentina - Argentinien

NAKASEServicio Tecnico CNCCalle 49, No. 5764/66B1653AOX Villa BalesterProvincia de Buenos Aires

Tel.: +54 11 4768 36 43Fax: +54 11 4768 24 13Hotline: +54 11 155 307 6781 [email protected] [email protected] [email protected] (Service)

Brazil - Brasilien

Bosch Rexroth Ltda.Av. Tégula, 888Ponte Alta, Atibaia SPCEP 12942-440

Tel.: +55 11 4414 56 92+55 11 4414 56 84

Fax sales: +55 11 4414 57 07Fax serv.: +55 11 4414 56 86 [email protected]

Brazil - Brasilien

Bosch Rexroth Ltda.R. Dr.Humberto Pinheiro Vieira, 100Distrito Industrial [Caixa Postal 1273]89220-390 Joinville - SC

Tel./Fax: +55 47 473 58 33Mobil: +55 47 9974 6645 [email protected]

Columbia - Kolumbien

Reflutec de Colombia Ltda.Calle 37 No. 22-31Santafé de Bogotá, D.C.Colombia

Tel.: +57 1 368 82 67+57 1 368 02 59

Fax: +57 1 268 97 [email protected]

OPC Interface


Notes

Bosch Rexroth AGElectric Drives and ControlsP.O. Box 13 5797803 Lohr, GermanyBgm.-Dr.-Nebel-Str. 297816 Lohr, GermanyPhone +49 (0)93 52-40-50 60Fax +49 (0)93 52-40-49 [email protected]

Printed in GermanyDOK-MTX***-OPC*INT*V02-PR01-EN-PR911310459

rexroth indramotion mtx · rexroth indramotion mtx opc interface project planning manual...

Documents