Using webQAC

Open an archive

1. Open webQAC in a current desktop browser. Serving the tool over HTTP is recommended; opening the local HTML file directly is also supported for many workflows.
2. Drop a KRCDiag or Report ZIP onto the start surface, or click it to choose a file. With keyboard focus on the surface, press Enter or Space.
3. Wait for the import to finish. webQAC detects the archive type and opens the available diagnostic views.
4. Confirm the controller, robot, software release, and report context in Overview before investigating.

Keep the archive compressed: individual extracted files are not a replacement for the complete diagnostic ZIP. Some logfile and trace views parse their data only when first opened; wait for their loading indicator to finish.

The tool analyzes captured archive data, not a live controller. An absent value means the archive or parser did not supply it; it does not prove that a component or condition is absent.

A practical investigation

1. Confirm context: check Overview for the correct controller and software. For OS2, check the instance information.
2. Triage: open Analysis and review errors and warnings. Open related sections from a finding when an action is provided.
3. Check resources: inspect Hardware for temperatures, disk space, and component information.
4. Establish the sequence: open Log history, narrow the time interval, and compare relevant sources. Select a record to inspect the complete message.
5. Verify evidence: inspect the primary log, Files / KRL, and the dedicated bus, motion, brake, or trace views.
6. Collect results: use the available project, trace, JSON, or motion downloads. Preserve the original archive alongside your conclusions.

Automatic findings are investigation aids, not a safety assessment or approval to change a robot. Apply controller changes only through the appropriate authorized engineering procedure.

Overview

Start here to identify the controller, robot, installed software, and available hardware information. Depending on the archive, you will also see an HMI screenshot or OS2 instance information.

1. Check that the robot and controller match the system under investigation.
2. Record the software release and relevant installed options before checking compatibility.
3. Inspect storage summaries and follow up in Hardware when resources look constrained.

Drag a card by its arrow handle to change its position. Overview and Hardware retain their own card order in the current browser; this does not change archive data.

Hardware

Inspect the System, SmartPAD, Temperatures, and Controller cards for board identification, memory, storage, firmware, and reported sensor values.

1. Check component identification and versions against the installed hardware.
2. Review partition capacity and free space; disk values are displayed in MB.
3. Review temperatures and expand grouped Mainboard readings when available. Red readings and thermometer icons flag values outside the applicable limits.

Temperatures are captured readings, not continuous monitoring. Missing or invalid readings are not a healthy-state indication. Consult Analysis for related temperature findings.

Process list

Review the Windows processes captured in the diagnostic report and their working-set memory usage, displayed in MB.

Look for unusually large consumers and compare them with Analysis findings and the original KRCDiag.log. A single snapshot does not establish a memory leak or sustained load; compare multiple diagnostic captures when necessary.

Load data

Inspect configured tools, frames, load properties, and their recorded usage. Tool rows associate each tool index with its name and separate mass, center of mass, and inertia.

1. Find the tool index used by the relevant program.
2. Check the TCP/frame and load properties, paying attention to the displayed units.
3. Use the Usage entries to identify related modules, then inspect those modules in Files / KRL.
4. Use the available KUKA.Load action when a separate load assessment is needed.

Displayed values are shortened for readability; the JSON data model retains parsed precision. Configuration presence and recorded usage do not prove that a tool is physically installed or correctly calibrated.

Enable Display tools without load data to include tools whose load fields are empty.

KRCDiag / Report log

Open the first entry under Logfiles to read the archive's primary diagnostic report in the text viewer. Use it to verify the source behind a summary or locate report details that have no dedicated card.

The file tree is hidden for this dedicated view. Return to Files / KRL to browse the archive normally. Use the viewer's Find and text-size controls to inspect long reports.

Log history

Correlate supported timestamped logs in one chronological list. Sources can include System, Logbook, Cross, platform services, SmartHMI, Linux services, Flight Recorder, and supported Windows event logs.

1. Wait for the first history load to complete and check the summary for read errors.
2. Open the filter icon in the Source or Severity column header to choose multiple values. Select all and None affect only that column. A colored icon indicates an active filter; no selected values means no rows. On narrow screens, scroll the table horizontally to reach the headers.
3. Type directly in the Message column header to filter the displayed message text. Spaces mean AND: motor fault -reset requires both words but excludes messages containing reset. Quotes require complete words or phrases: "motor fault" -reset matches Motor fault! (also with extra spaces) but not motor faulty. Put - before a quoted phrase to exclude only that whole phrase. Matching ignores case; press Escape to clear the field. File paths and metadata are not included.
4. Open the filter icon in the Time column header to see the time slider. Use its activity marks to locate periods with records. Set an interval with the two handles or UTC From/To fields; drag the selection to move it. Clear time range removes only the time restriction.
5. Press Ctrl+F or Cmd+F to highlight matches among the rows left by the filters without hiding more rows. The Find bar shows the current/total count; use its arrows or Enter/Shift+Enter to move between matches. Closing the popup or pressing Escape clears only the highlighting search.
6. Select a row to read its full message, timestamp, and source file in the detail pane. Use ArrowUp/ArrowDown to inspect adjacent records. Changing filters keeps the selected row in view while it still matches; filtering it out clears the selection.
7. Choose Export filtered logs to download all records matching the current Source, Severity, Time, and Message filters as a timestamped filteredLogs.txt file. Each line contains Time, Severity, Module, and Message separated by semicolons and tabs; multiline messages are flattened. File locations and expanded details are omitted. Find highlighting does not limit the export. The button is unavailable when no records match.

Drag a column-header edge to resize its column. Inside the Source filter, Message language appears beneath Logbook; it changes supported KUKA message translations and is remembered in this browser. Missing translations retain raw keys; changing language does not translate arbitrary log text.

Cross entries show decoded operations where recognized; their details preserve raw records. Windows-event details retain payload and metadata even when a KUKA message is translated.

KSS Systemlog dates can be inferred from filenames; controller clock offsets and time zones are not corrected. Treat cross-source timing as evidence to verify, not guaranteed synchronization. OS2 history uses the selected report snapshot and matching Flight Recorder service logs, not every snapshot in the ZIP.

EtherCAT

Review discovered bus devices, firmware information, and EtherCAT diagnostic errors. Open the view and wait for its first diagnostic load.

Identify the affected device or slave, inspect the error details, and correlate the incident with Log history. Firmware summaries describe captured versions; verify release-specific compatibility before recommending an update.

Poslogs

Inspect recorded positions through metadata, plotted signals, and the 3D motion view.

1. Select a recording from the Poslogs list.
2. Check its metadata and chart before interpreting the motion.
3. Use Play and the frame slider to inspect the sequence. The ghost and manual-axis controls support visual comparison; manual changes affect the visualization, not the archive or robot.
4. For a motion export, select Video or GIF and choose Export motion. Video format depends on browser encoder support.

Use the available KRL export when needed for further inspection. A reconstructed visualization or exported program is not a validated robot execution path; verify kinematics, frames, and configuration independently.

Accutest

Inspect the recorded battery-test voltage and temperature curves. Compare the available history for changes over time and check the underlying diagnostic context before concluding that a battery needs replacement.

This view displays historical tests; opening it does not initiate a battery test on the controller.

Read the chart units carefully: voltage is shown in volts and this test's temperature series is shown in kelvin.

Braketest

Inspect captured brake-test results. Switch between basic and expert views to move from the result summary to more detailed source information.

Check the test context and affected axes, and use the source text to verify unexpected results. Viewing a report does not perform a brake test or certify brake safety.

Project info

Review the available WorkVisual/project information and KRL checks. Use the project download when the ZIP contains an exportable project.

Compare the project information with the controller software and options in Overview. A project extracted from a diagnostic archive is evidence of the captured configuration, not confirmation that a local engineering project is current.

Trace

Inspect available trace recordings and supported modules, including KrcIpo and NextGenDrive data.

1. Select a recording, then choose an available module such as KrcIpo or NextGenDrive.
2. Choose the available signals in the channel selector and inspect the plot.
3. When enabled, choose Run Analyzer to evaluate the supported torque check and inspect the on-screen results.
4. Use Trace Download to save the captured trace files from the archive for further inspection; it does not export the on-screen analyzer results.

The example below shows an archive without a supported trace recording: the recording and module selectors cannot be used, and there is no plot to inspect. With a supported recording, selecting it makes its available modules and signals accessible. If your view looks like the example, check whether the archive contains a supported recording before trying the analyzer. Trace plots show captured signals, not live measurements.

The automatic torque check uses static limits and does not replace a complete load analysis or the motor characteristic.

Files / KRL

Browse the archive file system or the focused KRL tree and select a readable file to preview it. Supported KRL, XML, JSON, and INI content receives syntax highlighting.

1. Expand the appropriate directory and select the source or configuration file.
2. Use the viewer's Find control to locate relevant text.
3. Use the plus/minus controls to adjust that viewer's text size independently.

Use this view to verify configuration references and program usage found elsewhere. The preview is read-only; it does not modify the archive or controller. Binary and unsupported files may not have a useful text preview.

Analysis

Review automatic diagnostic findings and recommended follow-up actions. The navigation badge summarizes findings from the registered checks.

Analysis checks Windows System events for unclean restarts without loading the full Log history. Kernel-Power event 41 does not identify the cause. Its possible mitigations are listed separately, including checking batteries and network connections; KSS 8.7 also suggests considering the system board. Review the event record in Log history.

1. Open Analysis after the initial import and review the highest-severity findings first.
2. Use the available filters to narrow the findings, then expand an item to inspect its evidence and recommendation.
3. Follow actions such as Open load data or Open process list to inspect the related configuration.
4. Open relevant deferred diagnostic views and return to Analysis: additional parsed evidence can update the findings.

No findings does not mean that the robot is fault-free. Analysis checks selected conditions in the data it can parse; incomplete captures, unsupported formats, and conditions outside those checks require independent investigation.

Search files and results

1. Enter a query in the sidebar's Search files control.
2. Choose KRL, Logfiles, or All as the search scope, then run the search.
3. Wait for scanning to finish and open Search results.
4. Select a matching file to inspect its full preview and highlighted matches.

Use archive-wide search when you know a variable, configuration key, or message fragment but not its file. All includes readable archive content; binary files are skipped. This search is separate from Log history's row highlighting and does not inherit its source, severity, message, or time filters.

Downloads and general controls

Downloads depend on the files actually present and recognized in the archive. Store exported evidence with its original archive and protect it as controller/customer data.

Troubleshooting and limits

Data handling

Archive parsing runs in the browser. Some features may contact external services, such as firmware information or KUKA.Load; do not assume that every workflow is network-free. Review your organization's rules before sharing archives, screenshots, or exports.