Configuring SINUMERIK 810D for DIN/ISO Programming

After selecting the correct program type, write a native DIN/ISO program without changing the entire operator interface. A DIN/ISO program does not require ShopMill stock or retract-plane definitions to execute; those definitions mainly support ShopMill sequencing and graphical simulation. Use the CNC ISO interface only when the machine-specific configuration leaves the normal G-code editor locked, and treat an Explorer-like display or trapped simulation screen as an HMI configuration problem rather than a machining-language requirement.

Symptom interpretation

Three symptoms must be separated because they have different causes:

The term program type here means the syntax and interpreter context assigned when a file is created. The term HMI mode means the operator-interface environment used to create, manage, and simulate that file. Selecting DIN/ISO as the program type and switching to the separate CNC ISO HMI are therefore not equivalent actions.

Program interpreter and HMI separation

The numerical control executes a program according to its interpreter context. ShopMill adds a structured work-step layer around machining operations, including header data and graphical input forms. DIN/ISO exposes the block-oriented program more directly. The HMI supplies the editor and simulation screens, but it is not the interpreter itself.

This separation explains why a program may be executable even when its editor looks old, lacks conversational softkeys, or provides no stock form. It also explains why changing the complete HMI can reveal a different editor without changing the fundamental DIN/ISO language. A poorly configured alternate HMI may display file-management screens, omit expected navigation, or provide an awkward simulation workflow while the CNC interpreter remains functional.

Software generation matters. A physical control and a newer SinuTrain installation can expose different editors, cycles, contour tools, and softkey layouts. Use SinuTrain to learn syntax and toolpath logic, but verify editor functions, supported commands, and simulation behavior at the machine. A successful selection in a newer training environment does not prove that the same menu path exists on an older installation.

Programming-route selection

Choose one primary programming model for each operation. Mixing models without an explicit interface creates hidden modal-state dependencies and parser conflicts. A ShopMill file opened through a DIN/ISO-oriented screen is not automatically converted into a clean block program, and a DIN/ISO file does not gain ShopMill semantics merely because it is displayed from the ShopMill program manager.

For production work requiring direct access to inactive program sections, native DIN/ISO or independently stored subprograms can be more practical. Structured ShopMill sections may not be editable after execution has started, especially when the section lies within the active program structure or read-ahead region. Editing an active production program remains a controlled machine procedure, not a workaround for selecting the wrong program type.

Native DIN/ISO creation procedure

1. Stop at a safe machine state. Create and edit the first test without an active automatic cycle. HMI switching is an operator-interface action, not a recovery method during motion.
2. Open the normal program manager. Start from the interface used for ordinary file management rather than pressing CNC ISO immediately.
3. Create a new G-code or DIN/ISO program. The label varies with the installed software. Confirm the selected program type before entering machining blocks.
4. Test the editor. Select the text area and use the alphanumeric keyboard. If the editor is available, remain in this HMI; a complete interface switch adds no programming capability by itself.
5. Classify a locked editor correctly. If character entry remains disabled, confirm that the file is not read-only, protected, active, or opened through a view-only route. Then record the control software identity shown by the machine and compare the enabled editor options with its machine documentation. The installation described here required the separate DIN/ISO HMI to obtain an editable program.
6. Use CNC ISO only if required. Expect the entire interface to change. Open the program manager within that environment and create or open the native DIN/ISO file there.
7. Enter all motion prerequisites explicitly. A native program has no ShopMill header to supply approach or retract behavior. Establish the intended tool, spindle, feed, coordinate, compensation, and safe-position states before the cutting blocks.
8. Save and reopen the file. Confirm that it returns to the same program type and remains editable before adding a full production sequence.

For a tool change, the installation referenced the form Txx M6. Replace xx only with a tool identifier valid for that machine. Do not copy a tool-call convention from a simulator or another control without checking the machine's tool-management configuration.

Stock model and simulation mechanism

A stock model is not a prerequisite for CNC execution. The control can execute programmed motion without knowing a graphical blank size or fixture shape. ShopMill asks for such data because its work-step environment uses it for visualization, machining context, and generated motion. DIN/ISO separates execution geometry from optional simulation geometry.

Some software versions accept the command WORKSPACE to describe the workpiece region for simulation. The exact syntax is version-dependent and is not defined here. Read the programming manual for the software installed on the machine before using it. When the command is unavailable or omitted, simulation may show only toolpaths rather than material removal.

A second route is to place the simulation settings in a ShopMill program and call a separately written ProgramGuide or DIN/ISO program from it. This preserves the ShopMill simulation context while keeping the machining logic in a block program. Before adopting that structure, verify the coordinate system, active tool, compensation state, and return behavior at the call boundary.

Simulation is a diagnostic aid, not authorization to run. It may detect gross path and stock errors, but it cannot prove the physical fixture, actual tool assembly, work offset, or machine-specific auxiliary behavior. If the alternate HMI provides no reliable way back from simulation, stop using that path until its documented return function has been identified and tested with the machine stationary.

Hybrid ShopMill and G-code entry

For a small number of G-code lines inside ShopMill, use the yellow Input key and enter the blocks through the alphanumeric keyboard. The resulting line spacing may retain the work-step-plan presentation. This method does not turn the ShopMill file into an unrestricted DIN/ISO program.

The main architectural limit is variable handling. Within a ShopMill program header, unrestricted variable definitions are not available through the reported workflow; use R-parameters where that control and program design permit them. If the operation depends on broader DIN/ISO program structure, place it in a native program or subprogram rather than building a large hybrid section.

Parser acceptance must be tested statement by statement. In the described installation, ShopMill rejected G41 and G42, and the resulting motion followed the cutter-center path. That is a dimensional hazard: a displayed line of code is not proof that cutter compensation became active. Read the program messages, inspect the active compensation state, and compare the simulated or dry-run path with the required offset side.

Do not open a structured ShopMill file in the DIN/ISO HMI and expect a useful conversion. The two formats carry different structural information. Move logic deliberately: preserve the machining intent, then rebuild the required initial states and paths in the destination programming model.

Contours, cycles, and coordinate strategy

An older DIN/ISO editor may not provide the contour calculator or cycle set visible in newer training software. Missing forms do not prevent contour programming; they transfer responsibility for geometry and path construction to the programmer. Choose among Cartesian blocks, polar programming, supported cycles, or explicit cycle-free motion according to the geometry and installed command set.

Polar-coordinate programming can simplify bolt-circle and connected circular geometry that would otherwise require repeated Cartesian calculations. For circular interpolation written with G2 or G3, the cited workflow uses I and J to describe arc geometry. Confirm the control's definitions and the active plane in its programming manual before releasing the path; arc-center conventions must match the interpreter.

A missing boss-milling or residual-material cycle is not a reason to force ShopMill syntax into DIN/ISO. Build the boss with supported contour or path-milling functions, or program the toolpath explicitly. One installation used an additional 10 mm in both X and Y so a path-milling strategy could travel from outside toward the contour. That value was job-specific, not a reusable clearance. Calculate entry distance from stock boundary, cutter radius, compensation method, fixture envelope, and required approach geometry for each part.

Repeated simulation while constructing a contour is useful, but every revision also needs a syntax check and a controlled motion test. Geometry that looks plausible may still begin from the wrong modal state or apply an arc or compensation direction differently from the programmer's intent.

Tool, speed, feed, and motion responsibility

ShopMill commonly requests cutting data through conversational fields such as Vc and Fz. In the DIN/ISO workflow described here, spindle speed and feed are entered directly as rotational speed and either millimetres per minute or millimetres per revolution. The program must match the active feed interpretation; a numerically valid feed value in the wrong mode can produce a severe process error.

Use the tooling record and process plan to derive the direct values. Confirm the cutter diameter associated with any surface-speed conversion and the flute count associated with any per-tooth conversion. Do not transfer a Vc or Fz number into a direct-speed or direct-feed field without performing the required calculation and checking units.

DIN/ISO also requires explicit control of retract motion. The absence of a ShopMill retract-plane form does not remove the physical requirement for clearance. Program each transition around the actual stock, fixture, tool length, and machine travel. Treat every call to a subprogram as a state boundary: document what the caller establishes and what the callee may change.

Verification checks

1. Check 1: program classification. Reopen the new file from the program manager. Expect it to retain the DIN/ISO or G-code type rather than appear as a ShopMill work-step program.
2. Check 2: editor state. Enter and delete a harmless comment or non-motion test line. Expect ordinary alphanumeric editing without a full HMI change. If the text area stays locked, expect the separate configured DIN/ISO editor to be required.
3. Check 3: syntax acceptance. Run the control's program check with motion inhibited according to the machine procedure. Expect no parser message at each inserted block. A line visible on screen but rejected by ShopMill is not active logic.
4. Check 4: stock-independent execution path. Load the native program without a ShopMill stock definition. Expect the program check to proceed; graphical material removal may be absent.
5. Check 5: tool and cutting data. Compare the selected tool, direct spindle-speed value, direct feed value, and feed interpretation with the setup sheet. Expect exact agreement in identifier and units.
6. Check 6: explicit clearance. Single-block the approach and retract sequence above the work. Expect every rapid and feed move to remain clear of stock and fixturing without relying on an unseen ShopMill retract plane.
7. Check 7: contour geometry. Inspect line and arc endpoints, including any G2/G3 blocks using I and J. Expect continuity at every junction and the intended arc direction.
8. Check 8: cutter compensation. When G41 or G42 is used, observe the accepted compensation state and the displaced path during simulation or a controlled dry run. Expect the path to follow the required side of the contour, not the programmed cutter-center line.
9. Check 9: subprogram interface. For a ShopMill wrapper calling DIN/ISO, inspect the state before the call and after return. Expect the intended coordinate system, tool, feed interpretation, compensation state, and safe position at both boundaries.
10. Check 10: simulation navigation. Enter and exit simulation while the machine is stationary. Expect a documented return to the program manager without restarting or changing HMI environments.

Recurring configuration and programming pitfalls

Frequently asked questions