Haas NGC: Difference between revisions

From Knowledge Base
No edit summary
No edit summary
Line 49: Line 49:
# Starting from the Diagnostics/Gauges tab, press [[File:Haas DOWN.png]] and then [[File:Haas RIGHT.png]] on the arrow pad to select the Diagnostics/System tab.
# Starting from the Diagnostics/Gauges tab, press [[File:Haas DOWN.png]] and then [[File:Haas RIGHT.png]] on the arrow pad to select the Diagnostics/System tab.
# The version number is displayed in the "Versions" section as "Release".
# The version number is displayed in the "Versions" section as "Release".
==== Active tool reporting ====
Even when a Haas machine is configured to use MTConnect, the OnTakt proxy (version 2.7.8 and newer) will still use read the active tool using a Q Command, as the machine does not report this field via MTConnect.
'''Known issue:''' If a Haas machine does not have Q Commands enabled, the proxy will freeze and eventually stop reporting data from all machines. We are actively working on fixing this bug. In the meantime, it can be fixed by enabling Q Commands on the control using the steps in the "Q Commands" section below. If enabling Q Commands is not possible or desirable for a particular machine, this behavior can also be disabled for a single machine:
# In OnTakt, expand the machine card and click '''Edit'''.
# Hold the '''alt''' key while pressing '''c''' to open the '''Custom Properties''' tab.
# Click '''Add''' to create a new custom property.
# Enter <code>mtconnect.haas.skip_q</code> for the name.
# Enter <code>true</code> for the value.
# Click '''OK''' to save your changes.


=== Q Commands ===
=== Q Commands ===
Line 71: Line 59:


For more information, see [https://www.haascnc.com/service/troubleshooting-and-how-to/how-to/machine-data-collection---ngc.html#MDC---Ethernet-Q-Commands Haas's documentation].
For more information, see [https://www.haascnc.com/service/troubleshooting-and-how-to/how-to/machine-data-collection---ngc.html#MDC---Ethernet-Q-Commands Haas's documentation].
==== Active tool reporting ====
Haas NGC does not report the active tool number via MTConnect, so OnTakt can read it using Q Commands each time it reads data from a machine configured with MTConnect. This requires OnTakt proxy version 2.7.8 or newer.
To enable this behavior, first enable Q Commands on the control using the steps above, then enter the selected port into the machine settings in OnTakt. If a control using MTConnect does not have Q Commands enabled, leave the Q Commands port setting empty in OnTakt so it doesn't attempt to connect.
[[Category:OnTakt User Guide]]
[[Category:OnTakt User Guide]]

Revision as of 11:44, 31 May 2024

This page provides information about Haas's Next Generation Control.

Part counting

OnTakt reads M30 counter #1.

Video by Haas Automation, Inc.

Counting with M99

Haas setting 118.png

By default, Haas controls only count parts when a program calls M30, but they can be configured to also count parts when a program calls M99 using the following procedure:

  1. Press the SETTING button.
  2. Type 118 on the keypad and then press Haas F1.png to jump to setting #118, "M99 Bumps M30 Cntrs".
  3. Change the value to On to enable counting with M99 or Off to only count with M30. To change the value:
    1. Highlight the row.
    2. Press Haas RIGHT.png to open the dropdown.
    3. Use Haas UP.png or Haas DOWN.png to change the selection.
    4. Press Haas ENTER.png to apply it.

Manually setting the part counter

Requires parameter 22 (ENABLE MACRO) to be available on the control.

MDI input or part programs can manually adjust the part count by writing to macro variables #3901 (M30 counter #1) and #3902 (M30 counter #2). It is possible to set a specific value (#3901=42) or increment the value (#3901=#3901+1). This is useful for programs that do not call M30 or M99.

Counting with a macro variable

Instead of using the built-in part counters, OnTakt can also read a macro variable and interpret it as a part counter. This way, the part program can increment the part counter by incrementing a macro variable. For example, the statement #500=#500+1 increments macro variable number 500.

Machine data collection

Machines with Haas NGC support two MDC (machine data collection) protocols: MTConnect and Q Commands.

MTConnect is the preferred communication method because it provides the emergency stop state, alarms, and variables, while Q Commands do not. However, Q Commands use a lower-level protocol that is more likely to be available on older controls.

For more details on the differences, see OnTakt's supported machine features matrix.

MTConnect

MTConnect is always enabled at port 8082 on Haas NGCs.

For more information, see Haas's documentation.

Control software version

This control will not offer full MTConnect functionality.

Controls with software versions before 100.20.000.1200 will not report alarms or variables.

To check your control's software version:

  1. Press the DIAGNOSTIC button.
  2. Starting from the Diagnostics/Gauges tab, press Haas DOWN.png and then Haas RIGHT.png on the arrow pad to select the Diagnostics/System tab.
  3. The version number is displayed in the "Versions" section as "Release".

Q Commands

Haas setting 143.png

Before use, Q Commands must be enabled in the control settings by performing the following steps:

  1. Press the SETTING button.
  2. Type 143 on the keypad and then press Haas F1.png to jump to setting #143, "Machine Data Collect".
  3. Change the value to a valid port number (we suggest 5051) by typing it and then pressing Haas ENTER.png.

For more information, see Haas's documentation.

Active tool reporting

Haas NGC does not report the active tool number via MTConnect, so OnTakt can read it using Q Commands each time it reads data from a machine configured with MTConnect. This requires OnTakt proxy version 2.7.8 or newer.

To enable this behavior, first enable Q Commands on the control using the steps above, then enter the selected port into the machine settings in OnTakt. If a control using MTConnect does not have Q Commands enabled, leave the Q Commands port setting empty in OnTakt so it doesn't attempt to connect.