Software That Speaks Your Machine's Language

Renishaw WCS Setup Data

Every probing point reported with actual values, deviations, and pass/fail status — Z-front, X-wall, Y-surface, and more. Color-coded OK, warning, and caution at a glance.

Probing Simulation in Fusion 360

See the Renishaw probing cycle simulated in Fusion 360 before posting the G-code to your Multus — verify every touch point before it hits the machine.

Cutter Compensation & In-Process Probing

Probe to align the part and update work offsets, rough turn the OD, measure it, adjust cutter wear offset, recut to final dimension and verify — then the same closed-loop process for milling with cutter comp. All simulated in Fusion before posting G-code.

Fusion Inspect Surface — Visual Results on the 3D Model

Import your probing results back into Fusion via the inspection post and see surface deviations projected directly onto the solid model. Instantly visualize where your part is in or out of tolerance — no separate software needed.

Probe Sub Renishaw & Surface Inspect — Multi-Angle Measurement

Renishaw probing and Fusion Inspect Surface measuring at different B-axis angles — verifying features from multiple orientations and renaming the output file with the correct part number.

Smart Code View & Program Analysis

The full NC CodeLens interface — syntax-highlighted code on the left with hover tooltips explaining every G and M code, and a complete analysis panel on the right showing file info, stock material and part weight, program analysis, max spindle RPMs, tools used, and estimated cycle time.

Post Properties — Every Setting, Decoded

The Post Properties tab reads every setting baked into the posted program and lays it out by group — SET360 offset calc, configuration, formats, home positions, multi-axis, probing. Modified values are flagged against their defaults, so you can see exactly how a program was posted at a glance.

Tool Check — Every Tool, Cross-Referenced to Your Magazine

Load your program and TDF folder and NC CodeLens checks every required tool against the live magazine map from MagazineDumper — how many are loaded and ready, missing, or still sitting in the cabinet. It flags any tool that isn't in a pot or in the TDF export, and can post the whole tool list straight to a Tool Sync 360 server.

Gauge Tolerance, Tool by Tool

The detail view lists every tool with its holder, diameter, nose radius, flutes, life, pot, and per-position wear — and flags any tool gauged too short or too long against your tolerance with a red Gauge SHORT / LONG pill, so a mis-set tool never makes it to the cut.

NC CodeLens Demo

Watch NC CodeLens in action — hover explanations, real-time program analysis, stock weight calculation, and Autodesk Fusion integration all working together.

Runs Right on the OSP-P500 Control

One click writes every magazine tool — comments, kinds, sizes, offsets, wear and life — to magazine_map.json and full TDF files, right on the machine control. Auto-refresh watches for magazine load/unload and keeps the map current, ready for NC CodeLens to read.

The Live Magazine Dashboard

Every pot laid out with its tool, description, type, gauge length, diameter, nose radius, flutes, holder, life, and location. It flags tools with no gauge length that would silently skip a gauge check, and when a machine goes offline it keeps serving the last saved copy and refreshes automatically the moment it comes back.

One Small App, Served to the Whole Shop

The desktop app points at your magazine map and serves the dashboard on a single address — open it from any computer or iPad on the shop network. Keep-a-local-copy lets it run offline from the last snapshot, and it hands NC CodeLens and Fusion a folder to read straight from.

Multi-Machine Launcher

Start the reporter for the machine you want — Multus 1 or Multus 2 — from one simple launcher. It then watches that machine for new inspection data and builds a report the moment results land.

Every Feature, Reported and Color-Coded

Renishaw probing and surface-inspection results land on a single report — actual value, nominal, and deviation for every feature, color-coded pass / warning / fail, and tied to part number and counting sequence. Output is a self-contained HTML report you can open in any browser.

View sample report: OP2-P28 →   View sample report: ADM-P37 →

This Is the Report It Produces

Here's the top of a real report: a summary of total points, in- and out-of-tolerance counts, and worst deviation, then every feature with nominal, measured, deviation, and a color-coded pass / warning / fail status — each tied to part number and counting sequence. Open the full interactive samples: OP2-P28 →  ADM-P37 →

On the Control, While the Part Runs

This is the whole OSP-P500 screen during a real job — the machine's own control, not a PC beside it. SP1-SP2-SET360, part 47, 19 features measured, 19 pass, 0 fail, main and sub spindle both covered. Nothing left the machine to produce this: MachinePulse 360 reads each probe result out of the control as it is written and puts it straight on the operator's screen, right next to the running program. The one row judged against the assumed band is called out by name rather than being quietly mixed in with the real tolerances.

Every Feature, As It Is Measured

A real run: 52 features on part 37, each row landing as the probe touches off. Feature name, the Fusion operation it came from, measured value, deviation, the tolerance band and a pass / fail call — live, while the part is still in the machine. Surface-inspection points carry the tolerance straight from Fusion; Renishaw cycle results are shown against a stated default band and labelled as such, so an assumed number never reads like a real one.

Trends Across a Real Production Run

A live job, not a demo: SPT-TJS-8 short jaws, 30 parts, P6 through P35, one card per inspected feature. Each chart plots that feature's measured deviation part by part inside its own band — note they differ (+0.0010/-0.0020, ±0.0040, ±0.0020), because each one is the tolerance set on that feature in Fusion, not a blanket number. Eight features report no trend detected; two are quietly drifting, at +0.000017″ and -0.000011″ per part. That is the whole point — the drift is called out while it is still four zeros deep, not when it reaches the print.

And Where They're Headed

The same run read as a report. Every card says how much of its tolerance the worst part actually used — 7%, 15%, 24%, 59% — so a feature quietly eating its band stands out long before anything fails. Where a feature is genuinely drifting, the fit is projected forward as the dashed yellow line past the last measured part, with the drift called out (+0.000010″/part here). Where the scatter doesn't support a trend it says no trend detected instead of drawing a line through noise.

Open One Up

Click a feature and it shows its work. This one is drifting +0.000010″ per part, and rather than just saying so it commits to a number: “from P46: next -0.001059″ (±0.000073), then -0.001050″ (±0.000078)” — the prediction and the uncertainty on it, so you can judge for yourself whether it is worth touching an offset. Underneath sits the audit trail: every part measured, when it ran, what it deviated, whether it passed.

Watch the Count Climb — Recorded Off a Running Job

Part 47, from the first touch. The counter climbs 1, 3, 5, 7, 9 and a row lands each time the probe touches off — live, with the part still in the chuck. Every row carries the Fusion operation it came from and its own band: ±0.0020 on the Z surfaces, ±0.0040 on the XY outside surfaces, -0.0020/+0.0010 on the inside distance. At the end it flips to the Trend tab, where the part has already joined the run history. Nothing was exported and nothing waited for M30. (Sped up 3× — the real part takes about a minute of probing.)

Live Numbers → Trend → Signed Report, In One Take

The part is done, and this is everything that came out of it, unedited. Start on the live results — 9 measured, 9 pass. Switch to Trend and every one of those features is already plotted against the run. Open the one that is drifting and it shows the fit, the forecast for the next two parts and the part-by-part table behind it. Then the finished inspection report: 9 total points, 9 in tolerance, 0 out, worst deviation -0.00110″, each feature with its profile zone and pass status. One probe cycle feeds all three — the operator's screen, the trend history and the document you send with the parts.

The Live VC Heatmap

Every VC address (VC[0]–VC[199]+) color-coded by value and category. Hover any cell for its live value, zone — Renishaw, calibration, inspection — read/write status, and the exact code lines that reference it. Summary bar tallies zeros, non-zeros, sentinels, calibration, and free addresses at a glance.

Compare Two Dumps

Diff two VCDUMP files or machine states side by side — every address whose value differs, with the delta and its zone — so you can see exactly what changed between machines or over time.

Alarm State — Guided Recovery

When the changer stops, the banner turns orange and the recovery panel spells out the situation: spindle tool, staged tool, swap status, and the exact interlock checklist to verify before any ADVANCE or REVERSE on the machine panel.