LAST UPDATED: 02/25/2020

How to Read an Error Report - NGC

Error Reports

NOTE: This is procedure should only be performed by a Haas certified service technician.

Haas machines with the Next Generation Control (NGC) can create an error report that saves the state of the machinefor analysis. The error report is a ZIP file that includes a screenshot, the active program, and other information fordiagnostics and system debugging. Train your customers to create this file immediately after a crash, a control freeze,an alarm, or when an apparent software bug appears.

Be sure to always generate the error report with the alarm active.

If the control freezes, and does not respond to input:

1. Take a digital photograph of the control screen.2. Cycle power.3. Immediately generate an error report.

Use these steps to generate an error report:

1. Put a USB memory device into the USB port. The USB memory device is not required to generate an errorreport; without it, the control saves the error report in User Data, and you can retrieve it over Net Share orwith a USB memory device.

2. Press [SHIFT].3. Press [F3].

Send the ZIP file and digital photo to [EMAIL PROTECTED] for analysis.

How to Read an Error Report - NGC

Page 1 of 7 pages

Unpack the Error Report

You need to unpack the error report using a"unpack2.bat" utility program to be able to viewall the files in the error report.

Important: Make sure Java is installed on thePC. Open Control Panel>Programs andFeatures> make sure Java Update or Java X isinstalled.

1. Download the file NGC- UNPACK TOOLand unzip files

2. Save the machine Errorxxxx.zip file intothe NGC unpack folder.

• Run the unpack2.bat program.• Enter the name of the Errorxxx.zip file

without the .zip file extension.

Note: You can also drag and drop theErrorxxx.zip file into the black screen.

• Press [Enter]. This will unzip and extractthe hidden files from the error reportand generate a folder with the samename as the Errorxxxx.zip file.

How to Read an Error Report - NGC

Page 2 of 7 pages

The Error Report and Its FilesOnce the Error Report is unpacked it will contain the following files shown in the table.

Note: The table below shows the contents of an error report for software version 100.19.000.1102. Older softwareversions contain some different files.

File Contents

BBU folder This folder contains Haas Automation, Inc. internal software information.

CONFIGURATIONfolder This folder contains the machine configuration files.

HaasData/PatchData.txt

This file will show you which Patch files are applied. See the Patch Files section for moreinformation.

OS_Logs folder This folder contains Haas Automation, Inc. internal software information.

ThreadInformationfolder This folder contains Haas Automation, Inc. internal software information.

ParameterList.txt orParameterList.xml

This files shows the parameters that the machine is currently using. This includes any patches thathave been applied. See View Parameters section for more information.

AlarmHistory.txt The alarm history of the machine. The alarm history includes the serial number and softwareversion of the machine.

ATM.xml All of the tool data from the Advanced Tool Management table.

Diagnostics.txt Diagnostic data at time of report.

IOStates.txt The I/O PCB input, output, and analag states.

KeyHistory.txt The key history of the machine. The key history includes the serial number and software version ofthe machine.

LSC.xml All of the data from the Lead Screw Compensation table.

Macro.xml All of the data from the Macro Variable table.

ModelRunTimes.txt Haas Automation, Inc. internal software information.

Oxxxxx.nc The active program in the control.

Offsets.xml Tool offsets and work offsets.

screenshot.png A screenshot of the control when the error report was taken.

How to Read an Error Report - NGC

Page 3 of 7 pages

Error Report Screenshot

View Parameters

The screenshot of the error report containsuseful information if it is taken at the correcttime.

• Always generate the error report withthe alarm active.

• The screenshot is an example of acorrectly generated error report.

• You can see the active alarm, theprogram that was running, and the lineof the program where the alarmocurred.

The ParameterList.xml or ParameterList.txt (inthe error report) contains useful information. Ittells you exactly what parameter values themachine is using after all patches, etc. have beenapplied.

Note: As of 100.19.000.1100 software version,the file format of the ParameterList has beenchanged to .xml so it can easily be imported to anExcel spreadsheet.

To view this file Unpack the error report.

For ParameterList.xml file:

Use Excel to open the ParameterList.xml filelocated in the main directory folder in theunzipped error report.

Open as an XML table and click OK on the nextbox. You can scroll or search through theparameter list.

For ParameterList.txt file:

Use a text editor program to open theParameterList.txt file located in the maindirectory folder in the unzipped error report.

How to Read an Error Report - NGC

Page 4 of 7 pages

View Combined Alarm & Key History

How to Read an Error Report - NGC

Page 5 of 7 pages

1. Run the Alarm_Key_History_Merger.exefile.

2. Browse to find the .zip error report inthe NGC Unpack folder.

3. Browse to save the file in the NGCUnpack folder.

4. Select Mill or Lathe.5. Click "Create Excel". This will create an

excel file with the keystroke history andalarm history merged.Note: This will help to know whatkeys were pressed when the alarmswere generated.

How to Read an Error Report - NGC

Page 6 of 7 pages

Patch FilesThe examples below will show you how to determine which patches are applied.

To load and unload a patch refer to the: PATCH FILE LOAD / UNINSTALL - NGC.

Starting in software version 100.19.000.1100 information on the patches tab has been expanded to includea patch description. Also a second table has been added to improve the ability to preview the contents ofa patch.

Machines with software version100.19.000.1100 and higher.

Unpack the error report [1].

Open the HaasData folder [2].

Open the PatchData.txt with a text editorprogram.

This file will show you which patches havebeen applied [3].

Machines with software version100.19.000.1102 and lower.

Unpack the error report.

Open the CONFIGURATION folder [1]. Lookfor Patch_XXX.xml files [2]. If there are nonelisted then there is no patch files loaded.

Note: To view the contents of the patchfile, you can open the Patch file using a texteditor program [3].

Open the AlarmHistory.txt with a texteditor program [4]. Look at the last 903CNC MACHINE POWERED UP notification.See which files patch files have been applied[5].

This file will show you which patches havebeen applied [3].

How to Read an Error Report - NGC

Page 7 of 7 pages