Three tools in the material at once. One program that has to keep them apart.
The Tornos Swiss XT 32/9 is a compact 32 mm Swiss-type lathe with three independent tool systems. In its 9-axis version it has three Z axes, and it can work with three tools in the material at the same time. It also accepts bars up to 38 mm in non-guide-bush mode, and an optional plug-and-play B axis adds further tool positions for main operations.
On a machine like this, the difficulty is not making one tool cut well. It is making three independent tool systems, a main spindle and a counter spindle behave as one machine.
What the Swiss XT 32/9 gives the programmer to coordinate
The features that shape the NC program are:
- Three independent tool systems working in parallel
- Nine axes with three Z axes, allowing complex operations on the main side and the counter side at once
- A double gang tool configuration for dividing work across tool systems
- Dedicated tools for counter-operations, so back working can run while the main side is still cutting
- An optional B axis that adds tools to main operations
- Quick conversion between guide bush and non-guide bush operation
- Three tools in the cut at the same time, the main source of the machine’s productivity
Each feature is an opportunity to shorten the cycle. Each is also a dependency that the program must express correctly.
Valid code that runs wrong
On a machine with three tool systems the typical failure is not a syntax error. The NC program loads, the control accepts it, and the result is still wrong:
- a waiting point is missing or misplaced, so one channel runs ahead of the others
- the counter spindle closes on the part before the cut-off is complete
- two tool systems reach the same zone at the same moment
- three tools are in the material together, but one of them starts before its neighbours are in position
- the part transfer works, but only after waits that a better sequence would have avoided
- a hand edit made at the machine never returns to the CAM model, so the next revision reintroduces the original problem
None of these produce an alarm at load time. They show up as a crash, a scrapped bar, or a cycle time nobody can explain.
Why the usual workflow misses it
A conventional workflow for a machine like the Swiss XT looks like this:
CAM > individual operations > postprocessor > manual synchronization > manual edits > prove-out on the machine
Three weaknesses stand out.
The postprocessor is not a programming layer. It converts operations into NC code. It does not decide how work should be divided among three tool systems, where the channels should wait for each other, or how the part should be handed to the counter spindle.
Manual refinement becomes part of the process. Synchronization and handover logic are added by hand after posting. That work is repeated for every part and depends on the individual programmer.
Simulation usually runs before the postprocessor. CAM simulation shows what the CAM system intended to produce. It does not see waiting codes, macros, offsets or hand edits added afterwards. Toolpath simulation tells you what the CAM system intended to produce. G-code simulation tells you what the CNC machine has actually been instructed to do.
The machine has its own tools. The gap is upstream and downstream.
Tornos provides its own programming software for the Swiss XT, TISIS, which includes an integrated Gantt chart to help synchronize the machine’s channels. This is a useful way to work on the machine itself.
Many shops, however, start from a CAM system and want to stay there. Their questions are different:
- How do we get from the operations in our CAM to a synchronized multi-channel program without rebuilding the sequence by hand for every part?
- How do we verify the final NC program, offline, on a digital twin, before it occupies the machine?
That is the gap Eureka NC Coder and Eureka G-Code address, on the CAM side and before machine time is spent.
Where Eureka NC Coder fits
Eureka NC Coder is the layer between your existing CAM and the final NC program for the Swiss XT 32/9. It is not a replacement for CAM, and it does not require you to change CAM platform.
The division of work is straightforward:
- CAM creates the machining operations, in the system your team already uses.
- NC Coder assigns operations to the machine’s channels, manages synchronization, axis superimposition and part transfer, and applies the machine-specific postprocessing logic for the Tornos.
The result is a multi-channel NC program in which waiting points, handovers and channel assignments are generated in a controlled way rather than typed in afterwards. Because NC Coder works from the operations rather than from a single postprocessor, it applies to the CAM systems already used for Swiss-type work, including Fusion 360, Mastercam, Siemens NX, PTC Creo and hyperMILL.
Where Eureka G-Code fits
NC Coder produces the program. Eureka G-Code
verifies the program the machine will actually run.
Eureka G-Code simulates the final, post-processed NC program on a digital twin of the Swiss XT 32/9 and its control. It interprets the real program, the machine kinematics, the controller logic, macros and variables, work and tool offsets and machine limits, and runs all channels in their real relative timing. That is what exposes the problems that only exist when the channels interact:
- collisions and near-misses between the three tool systems, their tools and the spindles
- a counter spindle closing on the part at the wrong moment
- axis limit violations
- three tools in the cut with one of them starting too early
- material removal errors, checked by comparing the simulated part with the design model
Three tools in the cut: fast when it works, expensive when it does not
Working with three tools in the material at once removes the safety margin that a sequential program enjoys. When several channels are cutting together, a small timing error is no longer a wasted second. It is two tools competing for the same space, or a tool cutting before its support is in place.
Verifying the complete multi-channel sequence on the digital twin, before it runs on the machine, is what allows overlapping strategies to be used with confidence.
It is also about cycle time
Once the whole sequence is visible, the question changes from “Will the program work?” to “Is this the best way to run the machine?” On a three-system machine you can see:
- channels sitting idle while another finishes
- waiting points that could be moved earlier
- operations that could be overlapped instead of run in sequence
- a part-transfer sequence that spends more time synchronizing than cutting
For small parts made in volume, seconds recovered per cycle add up. They can only be found when the full multi-channel sequence can be seen and measured before it runs.
The Swiss XT 32/9 workflow, end to end
CAM (Fusion 360, Mastercam, NX, Creo, hyperMILL)
Machining operations
↓
Eureka NC Coder
Channel assignment
Synchronization
Axis superimposition
Part transfer
Tornos machine logic
Postprocessing
↓
Final multi-channel NC program
↓
Eureka G-Code
Eureka G-Code
Digital twin of the Swiss XT 32/9 and its control
Collision detection
Limits
Material removal
Complete multi-channel sequence
↓
Tornos Swiss XT 32/9
The program that is generated is the program that is simulated, and the program that is sent to the machine.
> Running a Tornos Swiss XT or another multi-channel Swiss-type machine? Request a demonstration on a digital twin of your own machine and controller, and see how Eureka NC Coder and Eureka G-Code connect your CAM, synchronization, postprocessing and G-code simulation in one workflow.
FAQ
Can I program a Tornos Swiss XT 32/9 from my existing CAM system?
Yes. Eureka NC Coder sits between the CAM system and the final NC program, so you keep the CAM you already use. It takes the machining operations, assigns them to the machine’s channels, manages synchronization, superimposition and part transfer, and produces the machine-specific multi-channel NC program.
Why is the Swiss XT 32/9 harder to program than a conventional lathe?
It has three independent tool systems, three Z axes and a counter spindle, and it can cut with three tools in the material at once. The difficulty is not any single toolpath but coordinating channels: waiting points, part handover and clearance between tool systems.
Is a postprocessor enough for multi-channel Swiss-type programming?
A postprocessor converts operations into NC code, but it does not normally distribute operations across channels or design the synchronization between them. That work is often done by hand after posting, which is where errors and lost cycle time come from. NC Coder is designed to handle that step.
How does this relate to Tornos TISIS?
TISIS is Tornos software for programming and managing the machine, including a Gantt chart for channel synchronization. Eureka NC Coder addresses the workflow that starts in CAM, generating the synchronized multi-channel program offline, and Eureka G-Code verifies the final NC program on a digital twin before it runs on the machine.
What does Eureka G-Code check on the Swiss XT 32/9?
It simulates the real post-processed NC program on a digital twin of the machine and its control: kinematics, controller logic, macros and variables, work and tool offsets, machine limits, collisions between tool systems, tools and spindles, timing across all channels, and material removal.
Why simulate the NC program instead of the CAM toolpaths?
CAM simulation runs before the postprocessor and before any manual edits. It shows what the CAM system intended. Simulating the final NC program shows what the machine has actually been told to do, including synchronization codes and hand modifications.
Can simulation help when three tools cut at the same time?
Yes. Overlapping cuts depend on precise timing between channels. Running all channels together on the digital twin shows whether each tool is in position when its cut starts, and whether tools and tool systems clear each other throughout.
Do I need to change my CAM system to use NC Coder?
No. NC Coder works with the CAM systems already used for Swiss-type work, including Fusion 360, Mastercam, Siemens NX, PTC Creo and hyperMILL.
Next step
Eureka G-Code — request a demonstration on a digital twin of your own machine and controller.
Verify the real ISO program — on a digital twin of your sliding-headstock machine, before the first bar.