1. Start with the machine make, model and controller
First send the full machine make and model, plus the control system type and software version if you have it. If you run more than one machine, label each one clearly, because a milling centre in Pretoria may behave differently to a router in Durban even when the frame looks similar.
We use this information to match the post to the right syntax, canned cycles, axis layout and tool change behaviour. If the controller is older or running a modified format, say so upfront. That saves time during post tuning and helps us avoid false alarms when a line of code is normal for that control but not for another.
- Machine make and model
- Controller type and version
- Number of axes, including rotary or trunnion units
- Machine orientation, such as gantry, bed mill, lathe or plasma table
2. Confirm the processes you actually run
Tell us which type of work the machine does on a daily basis. A router cutting MDF for shop fitting in Johannesburg needs different settings to a turning centre making steel shafts, and a plasma shop near Vereeniging may need very different lead-ins, pierce delays and height control commands.
List the main materials and the usual job sizes. If you switch between aluminium, mild steel, acrylic or hardwood, mention that too. Material thickness, work envelope and spindle speed range all help us set sensible defaults for feeds, retracts and safety moves. If the machine is used for more than one process, it is worth splitting the details by job type, not just by machine.
- Routing, milling, turning or plasma
- Primary materials and thicknesses
- Typical part size and max table travel
- Any special operations such as engraving, tapping or nesting
3. Share the sample code and current post file
If you already have a working post, send the latest version together with at least one sample NC file. That gives us a clean view of what the machine is doing now, not just what the settings say on paper. If the current output has extra lines, missing commands or incorrect tool calls, we can trace where the problem starts.
It also helps if you include one simple job and one more complex job. A straight profile may look fine, while a 5-axis or nested sheet job exposes the real issue. Please add any notes about what is wrong, what is acceptable and what must never change. Even small details matter, such as whether the machine needs a pause before toolchange or if the operator prefers manual confirmation for the first part.
- Current post file, if available
- One or two sample NC files
- Notes on what must be corrected
- Any lines that your team wants to keep exactly as they are
4. Map the tooling, holders and offsets
Tool data is a big part of getting a post right. We need to know the tool names or numbers, holder types, stick-out limits and whether your shop uses length offsets, diameter compensation or both. On some machines, especially where operators swap cutters often, a missing offset rule can cause a costly error on the first job. Its better to spell it out early.
Send your tool list if you have one, even if it is not complete yet. If your team uses a shared library, note how tools are named, grouped and stored. Also mention any custom tool change positions, safe Z heights or probing routines that must be called before cutting. For shops in coastal areas like Cape Town or Durban, the tooling notes can also help us account for corrosion-prone holders or probe issues caused by humidity and dust build-up.
5. Include machine limits, safety rules and local conditions
We also need the hard limits of the machine and the way your workshop runs. Tell us the max spindle speed, feed limits, axis soft limits, clamp zones and any forbidden areas on the table. If there are doors, light curtains, interlocks or alarm conditions that must be handled in code, include that as well. It is much easier to build this in up front than to discover it after a trial run.
For South African shops, practical site details matter too. If load-shedding affects machine start-up, say how you handle power recovery and whether the controller keeps its state. If the workshop is in a municipal area with strict noise or dust control, or if the machine is installed near a spray booth, forklift route or compressed air line, let us know. These details shape the setup and help us keep the program safe for your floor crew.
- Soft limits and home positions
- Spindle, feed and acceleration limits
- Clamp locations and no-go zones
- Interlocks, alarms and restart rules
6. Prepare the right contacts and a clear sign-off path
One good post-check can still stall if nobody knows who must approve changes. Tell us who the operator, programmer and owner contact is for the job, and who will sign off the first test file. If the machine is in a busy workshop in Pretoria or the East Rand, it helps to name one person who can answer questions quickly on the day.
We usually work better when the customer sends one packed set of information rather than ten separate messages. A single folder with notes, screenshots, sample code and machine photos is ideal. Add the most recent manuals or screenshots of the control screen if you have them. Once we have that, we can move through post tuning, machine onboarding or first job support with fewer back-and-forth calls and less risk of the wrong setting slipping through.
7. Final checklist before you send the job through
Before you use the enquiry form, quickly check that the package is complete. If one item is missing, we can still help, but a complete set usually shortens the turnaround and avoids guesswork. For older machines, or systems that were modified on site over the years, this final check is especially useful.
- Machine make, model and controller
- Process type and main materials
- Sample NC file and current post
- Tool list, offsets and holder details
- Safety limits, home positions and no-go areas
- Contact person for approval and testing
When all of that is together, we can build or tune the post with confidence and get your shop cutting cleaner, sooner.
