Product Map · Okuma Multus U-Series · OSP-P500
Fifteen products, four shared data hubs, and two loops that carry a correction back. Nothing here talks to another product directly — each one reads or writes a hub, which is why any single product still works on its own and the rest can arrive in any order.
Solid lines write. Dashed lines read. Orange is a correction travelling back.
Four hubs carry everything. The magazine map says what is loaded, the machine's share holds programs and results, the live machine feed carries machine state and temperatures, and the post carries the Fusion tolerance band into the NC program so the machine can judge its own measurement. The one deliberate exception to the hub rule is thermal: CTE Scaler, the post and the Inspection Reporter are versioned as a single system, because a program posted from a scaled model already carries shop-temperature nominals and the report must never correct them a second time.
Numbers match the price sheet, so the two documents line up.
What you see in Fusion is what runs on the machine. No hand editing, no patching two posts together.
One post for the whole U-series: turning, milling, automatic spindle selection and part transfer, simultaneous 5-axis on main and sub spindle, Renishaw probing cycles and Fusion Inspect Surface straight out of CAM.
.MIN · probe cycles · tolerance beaconsFusion toolpaths, tolerances, tool libraryWorking setups for turning, part transfer, bar pull, milling, insert NC function macros and manual pass-through, including the W-axis M-codes. Weeks of setup handed over on day one.
Fusion sample and test programsTurning and milling library with converted holder models and a T101–T9999 tool sheet, so machine simulation and collision checking run on real geometry instead of approximations.
the post, the TDF check, machine simulationBuilds a marked manufacturing copy of the model, scaled about the setup’s own work origin for the temperature the part is cut at, and regenerates the toolpaths. In a cold shop the copy is deliberately small and the part grows into nominal as it warms. The master model is never touched, so the CMM still measures against the truth.
scaled copy · scale stampthe post + Inspection Reporter, as one systemThe Multus virtual twin: the machine simulation Fusion does not have for Mill-Turn setups. It runs the posted program on a twin built from the machine’s own data on the OSP-P500, so a collision, an overtravel or a missing tool shows up at the desk, not on the machine. Live, it mirrors the real machine and logs its loads and coolant temperature against the toolpath that was cutting.
posted .MIN · Fusion part model · magazine map · live machine statefindings · recorded runs · data logFour products, one magazine map. The guess about what is loaded is where crashes come from, so the guess is removed.
Runs on the control and reads every pot straight from the control — comment, kind, type, size, offsets, wear, remaining life, diameter, length, nose radius, flute count. One click writes the map, and it refreshes whenever the magazine changes.
the tool data hubthe control · live magazineThe live magazine in any browser — a shop PC or a tablet on the machine. Read-only, nothing to install on the operator side, and it keeps serving the last good snapshot if a machine drops off the network. Flags tools with no gauge length.
the magazine maplive web view, no installPre-flight for the posted program: hover any G or M code for a plain-English explanation from the Okuma manuals, then cycle time, feed and RPM ceilings, per-axis travel bars, block and character-limit checks, stock weight, and a tool check against the live magazine. It opens itself after you post.
.MIN + the magazine mapovertravel · record length · missing toolsMoves the same check further upstream, into CAM. Reads the machine’s live Tool Definition File — gauge length, stickout, holder — and validates every tool with exact deltas before you post, so you build the job around the tools you actually have.
the tool data hub gauge · stickout · holderdiameter and gauge mismatches, per toolRecovery that does not depend on who is on shift, and the two hardware assemblies that protect the cycle.
One call takes a reset or crashed machine back to a known state with zero operator input — home Y and X, reset B, restage. Written with Gosiger applications engineering, and called by the post to get back to cutting.
from the posted programLive bar remnant tracking, part counts and cycle times over MTConnect, a bar stock calculator, and a production calendar with projected completion dates. Includes Machine Monitor.
MTConnectbar load · counts · projected finishMeasures every tool before use, down to .008 inch drills, catching breakage, pullout or wear before the next tool crashes into the mess. Custom covers keep chips and coolant out, and the positioning came out of the kinematic simulator for B-axis clearance.
G210 in the post · CAS integrationPneumatic ejection under M-code control, each stroke confirmed by a proximity switch so the program knows the position was actually reached. Replaceable end pushers, bolts on in minutes.
M230 push · M231 retractCatches the silent tool-changer hang, where a reset freezes the changer mid-swap with no alarm on the screen. Reads the changer state live and walks the operator through recovery. Read-only by design — advance and reverse stay on the machine panel where they belong.
the control · changer state, livePushes tool offsets from the Lyndex or Elbo presetter to the machine with an identity check before every write, preserves in-machine wear instead of overwriting blindly, and reads back to verify. The P500 tool table stays authoritative.
verified offsets · magazine mapThe tolerance band set on the feature in Fusion travels through the post into the program, so the machine judges its own measurement against the real print.
Every Renishaw and Fusion Inspect Surface result lands on the control screen and the shop dashboard the second it is measured. Green is in print. Red is out, immediately, while the part is still correctable, with an optional program stop. Yellow is a projection that says how many parts remain before a feature drifts out. It also writes the shop, enclosure and coolant temperatures into the control where a running program can read them.
live probe resultstemperatures to the controlWatches each machine for new probe and surface-inspection results and builds a color-coded report the moment the part comes off — nominal, measured, deviation, pass or warning or fail, tied to part number and count. Handles flatness, profile and circular fits, gives every point a second row corrected to 68 °F, and carries the machine’s last tune date in the header.
probe results on the machine shareone HTML report per partThe tool for the question nobody could answer without guessing.
Scans every program on the machine's program drive to map which VC variables the code actually uses, reads every live-registered variable off the control, and heatmaps both. Region map, program scanner, file-to-file diff, multi-machine scan, and it detects 200-variable against extended 1000-variable controls on its own.
machine programs + variable dumpswhich addresses are safe for a new macroThe whole integration, as data contracts rather than arrows.
| Product | Runs on | Writes | Reads |
|---|---|---|---|
| Advanced Post Processor | Fusion, at the desk | .MIN · probe cycles · tolerance beacons · tool gauge records | Fusion toolpaths · feature tolerances · tool library |
| Workflow Templates | Fusion, at the desk | Fusion setups and sample programs | — |
| Ready Tool Library | Fusion, at the desk | tool + holder geometry for simulation | — |
| CTE Scaler | Fusion add-in | scaled manufacturing copy · scale factor / material / temperature | part temperature · shared CTE table |
| ProveOut 360-VT Available | office PC or Mac, in a browser | findings · recorded runs · data log | posted .MIN · Fusion part model · the magazine map · live machine state |
| MagazineDumper | OSP-P500 control | the tool data hub | the control |
| Magazine Dashboard | PC, Mac or NAS | live web view | the magazine map |
| NC CodeLens V2 | Windows or Mac | pre-flight report | .MIN · the tool data hub |
| Fusion TDF Plug-in | Fusion add-in | in-CAM warnings | the tool data hub · Fusion tool list |
| M360 Recovery Macro | OSP-P500 control | machine back to a known state | call from the posted program |
| BK Mikro | on-machine hardware | break / pullout alarm | G210 trigger from the post |
| Workpiece Ejector | on-machine hardware | proximity confirmation | M230 / M231 from the post |
| MachinePulse 360 | OSP-P500 + dashboard | live pass / fail / projection · temperatures | live probe results · shop sensors |
| Inspection Reporter | Windows or Mac | HTML report per part, corrected to 68 °F | probe results on the machine share |
| VC Variable Manager | Windows or Mac | heatmap · region map · diff | machine programs · variable dumps |
| Production Monitor | network | production calendar · bar remnant | MTConnect |
Every licence is perpetual. Buy once, own it.
Items 01 through 08 are sold together because they are the shortest path to a machine that programs clean, knows its own tooling and proves its own parts. Everything else plugs into the same hubs afterwards, in any order.
01 post → 02 templates → 03 tool library → 04 CodeLens → 05 dumper → 06 dashboard → 07 TDF check → 08 reporterCurrent pricing, maintenance and the bundle discount are on the price sheet.
The thermal coefficients live in one place and are read by the post, the CTE Scaler and the Inspection Reporter. A test asserts all three offer the same materials in the same order, so the three cannot drift into disagreeing about a number.
Tool data, results and machine state move in one documented format across the suite, which is what lets a product be added years later and still read what the others already wrote.
A single 20-character key per product, entered once, valid on Windows and Mac. No accounts, no cloud, no telemetry — everything runs on your own network.
The machine, the programming desk and inspection have always been three islands, with the operator carrying facts between them in their head. Every product here is a bridge between two of those islands, so nobody has to remember.
The overtravel is caught at the desk. The wrong tool is caught in CAM. The out-of-tolerance feature is caught in the chuck. The recovery does not depend on who is on shift.
Because everything reads and writes shared hubs rather than each other, a shop can start with one product and add the rest in any order. The loop closes as the pieces arrive.