menu

This article is about the description of a fieldbus image which we deliver for special applications. The image delivers 8 control channels. The ToolScope is thus able to serve 8 NC channels out-of-the-box.

In this case, provide the ToolScope with the following input data in your PLC/PMC. All fields that are longer than one byte – other than those explicitly specified – are to be transferred in Motorola byte sequence.

Further input and output data for the device can be found in our interface description.













 

Profibus input of the TS

Meaning

Byte 1

Fixed "1"

Byte 2

Fixed "40"

Unsigned 16-bit from byte 4

Fixed "10000" in Intel notation

Unsigned 32-bit from byte 8

Torque of an axis (e.g. spindle) in 0.1 mNm in Intel notation

Unsigned 32-bit from byte 12

Torque of an axis (e.g. Z axis) in 0.1 mNm in Intel notation

(…)

(There are six more of the above fields, so that up to eight axis data items can be transferred)

Channel 1

 

Byte 108, bit 2

Activates "Rework" mode (ToolScope should consider currently monitored signals as abnormal and only monitor very roughly); Example: Override is not 100%

Byte 108, bit 3

Monitoring ON (manual trigger)

Byte 108, bit 5

Counts cuts (leads to: Counting of positive flanks of "Monitoring ON", so that every cut is given its own cut number and the cuts are therefore monitored separately)

Unsigned 32-bit from byte 116

Corresponds to "Processing number" signal in the GUI

Unsigned 16-bit from byte 118

Corresponds to "Program number" signal in the GUI (option "Service / Hardware / Data source Profibus CIFX (V2) / Read the uppermost 16 bits […] as program number" must be set)

In this case, only 16 bits are available for the Processing number.

Unsigned 32-bit from byte 112

Corresponds to "Tool number" signal in the GUI

Channel 2

(As for channels 3 to 8)

Byte 122, bit 2

Activates "Rework" mode (ToolScope should consider currently monitored signals as abnormal and only monitor very roughly); Example: Override is not 100%

Byte 122, bit 3

Monitoring ON (manual trigger)

Byte 122, bit 5

Counts cuts (leads to: Counting of positive flanks of "Monitoring ON", so that every cut is given its own cut number and the cuts are therefore monitored separately)

Unsigned 32-bit from byte 130

Corresponds to "Processing number" signal in the GUI

Unsigned 16-bit from byte 132

Corresponds to "Program number" signal in the GUI (the "Service / Hardware / Data source Profibus CIFX (V2) / Read the uppermost 16 bits […] as program number" option must be set)

 

In this case, only 16 bits are available for the Processing number.

Unsigned 32-bit from byte 126

Corresponds to "Tool number" signal in the GUI

Global data

(For all channels)

Unsigned 32-bit from byte 220

Program number

Unsigned 32-bit from byte 224

Corresponds to "ID Number" signal in the GUI (global)

Bit 0-2 of byte 228

Access level of the ToolScope as a number; 1: At least "Configuration"; 2: At least "Service"

For every channel to be transferred, the "Processing number", "Program number", "Tool number" and the global "ID" can be filled with any desired content. Only one thing is important: Based on this data, the monitoring must be able to distinguish one process from another. The same combinations of the four figures result in the ToolScope assigning cutting data to the same process in each case. These four figures must be set for the current channel to be monitored, before the "Monitoring ON" bit of the channel has a positive flank.

If you give this input data to the ToolScope, the device will largely work as desired. What is not covered, in particular, is the transfer of strings and the automatic activation of monitoring following transfer of G0 to G1/G2/G3, etc.    

The following output data of the ToolScope may be of interest to you:

Profibus output of the TS

Meaning

Channel 1

 

Byte 40

Channel 1 error code (see Section 12)

Unsigned 16-bit from byte 41

Override value from ToolScope; If no control is active, in most circumstances (including error statuses) this value is: "100"

Byte 42, bit 4

Configuration error (exact cause for setting the bit: The device's self diagnostics detected a status which does not normally correspond to proper operation; Caution: "Alarms are deactivated" is a proper operating status)

Byte 42, bit 3

The device is completely ready for monitoring (exact cause for setting the bit: There is no indication of improper operation and the alarms are switched on and the device is not in offline mode)

Channel 2

 

Unsigned 16-bit from byte 73

Override value from ToolScope; If no control is active, in most circumstances (including error statuses) this value is: "100"

Byte 44

Channel 1 error code (see Section 12)

Byte 46, bit 4

Configuration error (exact cause for setting the bit: The device's self diagnostics detected a status which does not normally correspond to proper operation; Caution: "Alarms are deactivated" is a proper operating status)

Byte 46, bit 3

The device is completely ready for monitoring (exact cause for setting the bit: There is no indication of improper operation and the alarms are switched on and the device is not in offline mode)

 

In the Profibus driver of the ToolScope, the checkmark next to "Do not send axis setting to the compile cycle; do not check for correct compile cycle image" must be set.

Remark from J. Brinkhaus, 2017/05/02: I doubt the last sentence; must be tested; TODO developers