Haas NGC: Difference between revisions

From Knowledge Base
No edit summary
No edit summary
Line 45: Line 45:
'''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:
'''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.
# In OnTakt, expand the machine card and click '''Edit'''.
# Hold the '''alt''' key while pressing '''c''' to open the Custom Properties tab.
# Hold the '''alt''' key while pressing '''c''' to open the '''Custom Properties''' tab.
# Click Add to create a new custom property.
# Click '''Add''' to create a new custom property.
# Enter <code>mtconnect.haas.skip_q</code> for the name.
# Enter <code>mtconnect.haas.skip_q</code> for the name.
# Enter <code>true</code> for the value.
# Enter <code>true</code> for the value.
# Click OK to save your changes.
# Click '''OK''' to save your changes.


=== Q Commands ===
=== Q Commands ===

Revision as of 16:51, 22 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

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. Go to the SETTING page.
  2. Enter 118 on the number pad and press the down arrow 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.

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 enabled by default on Haas NGC.

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

When connecting to the MTConnect agent on Haas NGC, use port 8082.

For more information, see Haas's documentation.

Active tool reporting

Even when a Haas machine is configured to use MiConnect, OnTakt proxy version 2.7.8 and newer will still use a single Q Command to read the active tool, 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:

  1. In OnTakt, expand the machine card and click Edit.
  2. Hold the alt key while pressing c to open the Custom Properties tab.
  3. Click Add to create a new custom property.
  4. Enter mtconnect.haas.skip_q for the name.
  5. Enter true for the value.
  6. Click OK to save your changes.

Q Commands

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

  1. Go to the SETTING page.
  2. Switch to the Settings tab.
  3. Change setting 143 (Machine Data Collect) to 5051. This sets the port that the Q Commands server listens on.

For more information, see Haas's documentation.