Skip to main content

Haas Troubleshooting

MTConnect Issues​

Problem: Cannot reach MTConnect on port 8082

Solutions:

  • Verify machine has Next Gen control
  • Check MTConnect is enabled in machine settings
  • Verify IP address is correct
  • Test from browser: http://[MACHINE-IP]:8082/current
  • Check firewall allows port 8082
  • Ensure machine and Edge are on same network or routable

Problem: MTConnect shows "UNAVAILABLE" for many data items

Solutions:

  • Machine may be powered off or in alarm state
  • Wait for machine to fully boot up
  • Clear any active alarms on machine
  • Cycle power on machine control

Problem: Part count not incrementing

Solutions:

  • Check Setting 57 (parts counter reset) on machine
  • Verify machine is actually counting parts on screen
  • Part counter may need to be configured in machine M-code program
  • See Haas manual for part counter setup

Problem: Double counting on M30

If you are seeing double part counts, check Assets → Machines → [machine] → Edit → Data Rules and ensure the part option is set to Haas M30-Counter. Using a different setting can cause the machine to count twice per cycle.

Validating part count health

Use the Connectivity Validation Guide to visually confirm part count behavior on the Timeline — including how to identify suspect counts from sporadic events and sub-second cycle times.

Haas Serial Issues​

Problem: No data from Haas Serial connection

Solutions:

  • Next Gen: Verify Setting 143 is set to 4001 (not ON/OFF)
  • Classic: Verify Setting 143 is ON
  • Check IP address and port 4001 are correct
  • Test connection with telnet: telnet [IP] 4001
  • Verify serial parameters match (38400, Even, 7, 1)
  • Classic only: Check Moxa converter is powered and connected

Problem: Moxa converter not responding (Classic controls)

Solutions:

  • Verify Moxa has power (LED should be lit)
  • Check Ethernet cable connection to Moxa
  • Use Moxa Device Search Utility to find Moxa IP
  • Reset Moxa to factory defaults (hold reset button 10 seconds)
  • Verify Moxa serial port settings match machine settings

Problem: Data comes through but looks garbled

Solutions:

  • Serial parameters mismatch - verify all settings match exactly
  • Check cable is not damaged
  • Verify baud rate is 38400 on both machine and Moxa/adapter
  • Ensure parity is EVEN (not NONE or ODD)
  • Verify data bits are 7 (not 8)

Problem: Macro variables show "UNAVAILABLE"

Solutions:

  • Check JSON configuration syntax is correct
  • Verify macro variable numbers are valid (see reference)
  • Some variables are read-only and may show UNAVAILABLE if condition not met
  • Test with common variables like #3027 (spindle RPM) to verify connection

Connection Conflicts​

Problem: Both MTConnect and Haas Serial show execution state but they conflict

Solution:

Problem: Duplicate data items from MTConnect and Serial

Solution:

  • Use transform adapter with deny-keys to block duplicates
  • Decide which source is authoritative for each data item
  • Keep MTConnect data for standard items, Serial only for macros