Introduction
MachineMetrics can connect with HEIDENHAIN iTNC 530 and TNC 640 controls to enable data collection. This section guides you through configuring the connector for efficient data collection. In many cases, when default settings suffice, no additional configuration is required. For information on connecting a HEIDENHAIN control to MachineMetrics, refer to How to Connect Heidenhain iTNC 530 and 640 Controls.
Several subtopics of this section require PLC addresses to be entered. For more on this topic, refer to Identifying PLC Memory Addresses on a Heidenhain Machine.
Topics covered in this section:
- Configuring Part Counting
- Configuring Alarms
- Configuring Emergency Stops
- Configuring Additional PLC-based Data Items
- Configuring Addresses to Calculate Cutting
Configuring Part Counting
To configure part counting, you'll need to identify the specific location in the PLC WORD table and determine the corresponding address. This process varies depending on the machine model; typically, it's location 20 for iTNC 530 and locations 10 or 19944 for iTNC 640. This address should then be entered into the part counting configuration section of the MachineMetrics connector. If the default settings meet your needs, no additional configuration is necessary. Non-default part counter addresses are often used with non-standard configurations, such as when pallet changers are in use.
Make sure the machine’s Parts Counter is in use (see the below figure) and that M-codes are correctly utilized for your machine type. For example, M53/54 on some Hermle machines can increment or clear the counter.
To configure part counting in the MachineMetrics application, select the machine, which should by now have been configured to use the Heidenhain Data Collection Method, and update the partcounting configuration section.
Use one of the keys: plcPartCountMemAddressTNC530, plcPartCountMemAddressTNC640, or plcPartCountMemAddressOTHERS, according to your machine type.
Example Part Counting Configuration:
{
"partcounting": {
"plcPartCountMemAddressTNC530": "60",
"plcPartCountMemAddressTNC640": "192",
"plcPartCountMemAddressOTHERS": "70"
}
}
Configuring Alarms
By default, all alarms are considered WARNINGS. However, they can be elevated to FAULTS by listing the code numbers of specific alarms to be considered FAULTS in the configuration section under alarmFaults. Follow these guidelines for alarm names:
-
Start with NC or, when a positive PLC number is know, PLC. Either is case-insensitive.
-
Negative numbers will be converted to positive valued PLC error codes internally, and PLC prepended.
-
Positive numbers without preceding letters will be assumed to be NC error codes, which will be prepended.
Example Alarm Configuration:
In the following example, alarms NC100, NC40, PLC40, and PLC98 will be considered FAULT instead of WARNING
{
"alarmFaults": {
"100": "",
"NC40": "",
"PLC40": "",
"-2130706334": ""
}
}
Note: Reporting of alarms is supported for the iTNC 530, but not for the TNC 640.
Configuring Emergency Stops
E-Stop alarms can be detected by matching parts of the description string against a configured list in the estopAlarms section. Any listed alarms will be considered FAULTS and treated as estops.
If a match is found, the estop will be TRIGGERED; otherwise, it remains ARMED.
Example E-Stop Configuration:
In the following example, alarms with description strings containing emergency stop or emerg. stop will be considered FAULTs instead of WARNINGS, and if either or both are found in any alarm description string, estop will be TRIGGERED. Values are case-insensitive. (These two are current default values.)
{
"estopAlarms": {
"emergency stop": "",
"Emerg. Stop": ""
}
}
Configuring Additional PLC-based Data Items
The Heidenhain connector may be configured to issue additional data items to the MachineMetrics platform based on data read from PLC addresses in the WORD and DWORD tables. To do so, specify the data item name, the table to be read from, and the address, in the plc section in the following format: <data_item_name> = <table_type>,<address>
where <table_type> is "W" or "D".
Do not duplicate data items already issued by the adapter, except as specified in these reference pages to overwrite default addressing.
Example PLC Data Items Configuration:
To read a data item named "afc_idle_load" from the DWORD table, address 4508:
{
"plc": {
"afc_idle_load": "D,4508"
}
}
Note that after adding a new data item, it may be necessary to update the mapping on the MachineMetrics platform in order to make the new data visible.
Configuring Addresses to Calculate Cutting
The Heidenhain connector provides the cutting (ON/OFF) data item by default for the iTNC 530, and can be configured to do so for the TNC 640. It is unlikely that for the iTNC 530 addresses need to be updated, but it is possible to do so.
iTNC 530:
The data used to calculate whether or not the machine is cutting are for the iTNC 530 spindle_speed, read by default from the DWORD table address 368, and feedrate, read by default from the DWORD table address 388. To overwrite these addresses, simply introduce the two metrics as appropriate into the plc configuration section.
TNC 640:
For the TNC 640, the data items used to determine cutting (ON/OFF) are rapid and feedrate. No defaults are used for these; instead configuration must be specified for both, in the plc configuration section. Once configured, cutting will automatically be issued.
Example Configuration to collect base data for cutting from a TNC 640:
{
"plc": {
"rapid": "D,4444",
"feedrate": "D,4448"
}
}
For assistance, email us at support@machinemetrics.com. Please include a detailed description of your issue for prompt support.
Comments
0 comments
Please sign in to leave a comment.