SINUMERIK 840D sl
The SINUMERIK 840D sl can communicate with Reniway Edge through the SINUMERIK connector. This guide walks through the CNC-side checks first, then the Reniway Edge connector setup and a small set of starter properties.
This page focuses on SINUMERIK 840D sl solution line controls. It also explains the most important difference between NCK addressing and PLC addressing, because both are available on many machines but they are not configured or named the same way.
What you need
| Necessities | Description |
|---|---|
| Reniway Edge | The edge device or server that will connect to the CNC. |
| Network connection | Ethernet connection between Reniway Edge and the SINUMERIK control. |
| Machine IP address | Static or reserved IP address of the SINUMERIK control, NCU, or HMI network interface used for machine data access. |
| Machine type | For this example, use s840d. |
| Device type | For SINUMERIK 840D sl, use SolutionLine. |
| Variable list | The SINUMERIK NCK and/or PLC addresses you want to read from the control. |
| Access rights | Permission from the machine owner or machine builder to access the required CNC variables. |
| Machine documentation | OEM documentation for channel, axis, PLC DB, alarm, counter, and tool-management addresses. |
Preparing the CNC
Start from the main screen of the SINUMERIK Operate interface. The exact menus can differ depending on the machine builder, but the goal is always the same: identify the control, confirm the network address, and make sure Reniway Edge can reach it.
Identify the control
Open the version or diagnostics screen on the SINUMERIK HMI and confirm the control generation.
For this example, the connector settings assume:
| Setting | Value |
|---|---|
| Machine Type | s840d |
| Device Type | SolutionLine |
Use PowerLine only for older SINUMERIK 840D powerline controls.
Configure the network
Open the network settings on the SINUMERIK HMI and write down the IP address that Reniway Edge must use.
For 840D sl solution line, the NC is commonly reached through one of these NCU interfaces:
| Interface | Typical purpose | Typical address behavior |
|---|---|---|
X130 | Company network. | Often DHCP client or site-assigned static address. |
X120 | Plant network. | Common default/static NCU address 192.168.214.1. |
X127 | Service interface for PG/PC. | Common service address 192.168.215.1. |
X136 | PROFIBUS DP/MPI socket when using a NetLink adapter. | Uses the NetLink adapter IP address. |
A static IP address or DHCP reservation is recommended so the connector keeps pointing to the same machine. Make sure the subnet mask and gateway match the machine network.
Verify network reachability
From the Reniway Edge network, verify that the SINUMERIK IP address is reachable.
The simplest check is a ping from the edge device or from a PC on the same network:
ping [machine-ip]
If the machine does not respond, check the physical network connection, VLAN, subnet, routing, and firewall rules. Some machine networks block ping, so use the site's normal network test procedure if ICMP is disabled.
Confirm NC/PLC variables on the HMI
On many SINUMERIK HMIs, NC and PLC variables can be displayed before adding them to Reniway Edge. Use the HMI variable screen to confirm the final spelling, index, and live value.
Typical menu path:
F10 > Diagnostics > NC/PLC variables > Insert variable
Use this screen for two tasks:
- Search for standard NC/NCK variables by path or name.
- Search for PLC symbols or operands and confirm the absolute operand shown by the HMI.
Reniway Edge connection
Open Reniway Edge and add a new SINUMERIK connector.
Fill in the connection settings:
| Setting | Value |
|---|---|
| Name | A clear name, for example SINUMERIK 840D sl. |
| Host | The IP address of the SINUMERIK control. |
| Machine Type | s840d. |
| Device Type | SolutionLine. |
Save the connector and start the connection. If the connector status becomes connected, continue by adding a small number of test properties.
Adding properties
SINUMERIK properties are configured by address. Start with a few read-only input properties and a moderate polling interval, for example 1000 ms.
When adding a property, fill in:
| Property field | Value |
|---|---|
| Name | A clear display name in Reniway Edge. |
| Address | The SINUMERIK NCK or PLC variable address. |
| Direction | Input. |
| Polling Interval | Start with 1000 ms. |
| Type | Resolved automatically by Reniway Edge. |
Addressing overview
A SINUMERIK control contains both an NC/NCK side and a PLC side:
| Area | What it usually contains | Typical address style | Typical use in Reniway Edge |
|---|---|---|---|
| NCK / NC | CNC state, channels, axes, spindles, program state, R parameters, tool data, GUD variables. | Path-based SINUMERIK variable names such as /Channel/State/progStatus[u1]. | Machine state, program state, axis positions, feedrates, spindle override, active program, active tool. |
| PLC | Machine-builder logic, interlocks, M-code handling, signals, lamps, buttons, counters, OEM statuses, custom DB values. | PLC operand or symbolic address, depending on what the connector supports and what the machine exposes. | Machine-specific signals such as cycle start, door status, chuck clamp, part counter, custom production state. |
Use NCK variables first for standard CNC data. Use PLC variables when the value is created by the machine builder or when the NCK variable list does not contain the required signal.
Important: PLC addresses are highly OEM-specific. Never assume that a PLC DB, bit, marker, or symbolic name from one machine is valid on another machine.
NCK addressing
NCK addresses use path-like SINUMERIK variable names. They usually start with / and are separated with / between the variable groups.
General format:
/Area/Block/Variable[indexes]
Example:
/Channel/State/progStatus[u1]
The address can contain an optional index list in square brackets. The most common index positions are:
| Index | Meaning | Example |
|---|---|---|
u or U | Unit, commonly used as channel index. The default is u1. | /Channel/State/progStatus[u1] |
| Column | Often used for an axis, spindle, line, or list index depending on the variable. The default is 1. | /Channel/MachineAxis/name[u1, 2] |
| Row | Optional third index for variables that require a row. The default is 1. | Depends on the variable definition. |
Indexing starts at 1. This is important for R parameters: R0 is addressed with row/index 1, R1 with row/index 2, and so on.
Examples:
| Value wanted | Address |
|---|---|
| R0 in channel 1 | /Channel/Parameter/R[1] or /Channel/Parameter/R when defaults are accepted. |
| R1 in channel 1 | /Channel/Parameter/R[2] |
| R0 in channel 2 | /Channel/Parameter/R[u2] |
| R10 in channel 2 | /Channel/Parameter/R[u2, 11] |
Common NCK areas
| Area | Typical contents |
|---|---|
/Nck | NC-wide state and configuration, such as NCK sign of life, NCK time, alarms, and access level. |
/Bag | Operating-mode-group data, such as active operating mode. |
/Channel | Channel-specific data, such as program status, program pointer, R parameters, feed override, and channel axis names. |
/Channel/MachineAxis | Channel-related machine axis values, such as axis names, feedrate, and positions. |
/Channel/Spindle | Channel spindle values, such as spindle override. |
/Tool | Tool-related data when available on the machine. |
/Nck/GD... | Global user data (GUD) areas, when configured and accessible. |
Starter NCK property examples
The addresses below are useful first checks on many SINUMERIK 840D sl controls. Always verify the final address list against the machine builder documentation, because OEM configuration can change what is available.
| Name | Address | Notes |
|---|---|---|
| NCK sign of life | /Nck/State/nckAliveAndWell | Basic check that the NCK is alive. |
| NCK time | /Nck/State/sysTimeBCD | NCK system time. |
| Operating mode | /Bag/State/opMode[u1] | Operating mode for operating-mode group 1. Common values include JOG, MDI, and AUTO depending on variable definition. |
| Channel status | /Channel/State/chanStatus[u1] | Status of channel 1. |
| Program status | /Channel/State/progStatus[u1] | Program state for channel 1. |
| Feed override | /Channel/State/feedRateIpoOvr[u1] | Feed override for channel 1. |
| Spindle override | /Channel/Spindle/speedOvr[u1, 1] | Spindle override for spindle index 1 in channel 1. |
| Active program name | /Channel/ProgramPointer/progName[u1, 1] | Active program or subprogram name. |
| Active tool number | /Channel/State/actTNumber[u1] | Active tool number. |
| Active tool identifier | /Channel/State/actToolIdent[u1] | Active tool name or identifier. |
| Axis 1 name | /Channel/MachineAxis/name[u1, 1] | Axis name for axis line index 1 in channel 1. |
| Axis 1 feedrate | /Channel/MachineAxis/actFeedRate[u1, 1] | Actual feedrate for axis index 1 in channel 1. |
| Axis 1 position | /Channel/MachineAxis/actToolBasePos[u1, 1] | Tool base position for axis index 1 in channel 1. |
| Number of pending alarms | /Nck/State/numAlarms | Number of pending general alarms. |
| Access level | /Nck/Configuration/accessLevel | Current access level. |
| R parameter R0, channel 1 | /Channel/Parameter/R[1] | R0 is index 1. |
| R parameter R1, channel 1 | /Channel/Parameter/R[2] | R1 is index 2. |
For machines with multiple channels or axes, adjust the indices. In u1, the 1 refers to the channel or unit index. In addresses such as [u1, 1], the second value is the axis, spindle, line, or column index defined for that variable.
NCK addressing rules and tips
- Keep the leading
/in the address. - Use the exact capitalization from the SINUMERIK variable documentation or the HMI variable list.
- Do not add a device name unless the connector documentation specifically requires it. Some OPC UA tools show a full NodeID such as
/DeviceName/Channel/...; Reniway Edge properties normally use the SINUMERIK variable path itself. - Start with
u1and axis/spindle index1, then change one index at a time. - For multi-channel machines, validate each channel separately, for example
u1,u2, andu3. - For multi-axis machines, read the axis name first, for example
/Channel/MachineAxis/name[u1, 1], before assuming that index1is X, Z, or another physical axis. - For array-like variables, keep polling narrow. Avoid reading large arrays at a high rate unless the use case requires it.
PLC addressing
PLC addresses refer to the PLC part of the SINUMERIK. The PLC is separate from the NCK even though both are part of the same machine control. PLC variables are often machine-builder-specific and can expose values that do not exist as standard NCK variables.
Typical PLC data includes:
- Machine-ready and cycle-start logic.
- Door, clamp, chuck, tailstock, coolant, robot, loader, or hydraulic states.
- M-code and H-code signals.
- Part counters and shift counters implemented by the OEM.
- Machine-specific alarms and diagnostic bits.
- Custom production state words.
PLC connection details for 840D sl
For SINUMERIK 840D sl solution line, PLC access commonly uses rack/slot 0/2.
| Interface | Typical PLC IP address | Typical PLC rack/slot |
|---|---|---|
X130 | DHCP client or company-network address | 0/2 |
X120 | 192.168.214.1 | 0/2 |
X127 | 192.168.215.1 | 0/2 |
X102 through NetLink | NetLink adapter IP | 0/2 |
When using a NetLink adapter for the PLC side, machine and adapter settings may require additional configuration such as the PLC bus address and network-parameter detection behavior. Use the machine builder or adapter documentation for the final values.
PLC address formats
The exact PLC syntax depends on how the connector exposes PLC variables and whether symbols are available. Common forms include symbolic names and absolute operands.
| PLC address type | Example style | Notes |
|---|---|---|
| Symbolic variable | BAG.AUTO or OEM-specific symbol | Easier to read, but only available when symbols are exposed. |
| Data block bit | DB10.DBX0.0 | Boolean bit in a data block. Exact DB and bit are OEM-specific. |
| Data block byte | DB10.DBB2 | Byte value in a data block. |
| Data block word | DB10.DBW4 | 16-bit word. Confirm byte order and signedness. |
| Data block double word | DB10.DBD8 | 32-bit value. Confirm data type. |
| Marker bit | M10.0 | Marker memory bit. OEM-specific. |
| Input bit | I0.0 or E0.0 | Physical or logical input, depending on notation. |
| Output bit | Q0.0 or A0.0 | Physical or logical output, depending on notation. |
Use the HMI variable screen to confirm the exact absolute operand. On SINUMERIK, the HMI can show the absolute operand under the variable selection field, which is useful when an OEM symbol is known but the connector needs an operand.
PLC property examples
The table below shows the style of PLC properties. Treat the addresses as examples only. Replace them with the actual machine-builder addresses.
| Name | Example address | Type | Notes |
|---|---|---|---|
| Machine automatic mode | BAG.AUTO | Bool or status | Symbolic example. Confirm symbol availability. |
| Cycle active | DB10.DBX0.0 | Bool | OEM-specific PLC bit. |
| Door closed | DB10.DBX0.1 | Bool | OEM-specific safety or status bit. Do not use for safety decisions in Reniway Edge. |
| Part counter | DB20.DBD0 | DInt or UInt32 | OEM-specific counter. Confirm reset behavior. |
| Machine state word | DB30.DBW2 | UInt16 | Decode bits according to OEM documentation. |
| Alarm group word | DB40.DBW0 | UInt16 | OEM-specific grouped status word. |
PLC addressing rules and tips
- Ask the machine builder for the PLC symbol list or a tag export when possible.
- Prefer named symbols when they are stable and exposed by the control.
- Use absolute operands when symbols are unavailable or ambiguous.
- Confirm data type, length, signedness, and scaling for every non-boolean value.
- Avoid writing PLC values unless the machine builder explicitly approves the address and behavior.
- Do not use Reniway Edge PLC reads as a safety system. Safety-related decisions must remain in the certified machine safety architecture.
- Some PLC values are latched, debounced, or updated only in a specific machine mode. Validate them while the machine is running through the relevant sequence.
Choosing between NCK and PLC addresses
| Use case | Prefer | Reason |
|---|---|---|
| Program state, channel state, active program | NCK | Standard CNC data is normally available directly from NCK variables. |
| Axis position, axis name, feedrate, spindle override | NCK | NCK owns motion and channel data. |
| R parameters and GUD variables | NCK | These are NC data areas. |
| Door, clamp, chuck, robot, loader, coolant | PLC | These are usually implemented in the machine PLC by the OEM. |
| Part counters | Depends | Use NCK if a standard NC counter exists and matches the requirement; otherwise use OEM PLC counters. |
| Custom production states | PLC | Usually created by the machine builder. |
| Tool data | Depends | Standard active-tool data can be NCK; detailed tool-management data may be OEM-specific. |
Validate the values
After adding the properties, verify that values update in Reniway Edge:
- Channel and program status change when the machine changes mode or starts/stops a program.
- Axis position changes when the machine moves.
- Active tool values change after a tool change.
- PLC bits change when the corresponding machine signal changes.
- PLC words and counters decode correctly according to the machine documentation.
- Errored properties are checked for address spelling, index, connection type, and machine availability.
Event properties
The SINUMERIK connector also supports event-oriented property creation for supported SINUMERIK events.
For a first commissioning run, start with polled address properties. After the base connection is stable, add event properties for event-driven use cases such as alarms or program events.
Troubleshooting
| Symptom | Possible cause | Solution |
|---|---|---|
| Reniway Edge cannot connect | Wrong host or blocked network route | Verify the SINUMERIK IP address, subnet, VLAN, and firewall rules. |
| Connector does not connect on an older machine | Wrong device type | Use PowerLine for older SINUMERIK 840D powerline controls. Use SolutionLine for 840D sl. |
| NCK property type cannot be resolved | Invalid or unavailable address | Check the address spelling, index, and whether the variable exists on this machine. |
| NCK property connects but value does not change | Wrong channel, axis, spindle, or row index | Verify the channel number and axis/spindle line index on the SINUMERIK control. |
| Axis values look swapped | Axis line index does not match the assumed physical axis | Read /Channel/MachineAxis/name[u1, n] for each index before mapping values. |
| R parameter value is off by one | R parameter index starts at 1 | Use R[1] for R0, R[2] for R1, and R[u2, 11] for R10 in channel 2. |
| PLC property cannot be read | Wrong PLC connection, rack/slot, or unsupported address format | Confirm PLC access settings and use the HMI NC/PLC variable screen to verify the operand. |
| PLC value is present but wrong type | Wrong byte, word, double-word, signedness, or scaling | Confirm the exact PLC data type with the machine builder. |
| Symbolic PLC address is not found | PLC symbols are not exposed or symbol name differs | Use the absolute operand shown by the HMI or request a PLC symbol export. |
| Many properties become slow or errored | Polling interval is too aggressive | Increase the polling interval or reduce the number of high-frequency properties. |
| Tool or production counters are missing | OEM-specific implementation | Ask the machine builder for the correct SINUMERIK, PLC, or tool-management variables. |
References
SINUMERIK address availability depends on the control version and OEM configuration. Siemens documents NC variable areas and variable lists in SINUMERIK list manuals. Machine-specific PLC addresses must come from the machine builder, PLC project, symbol list, or confirmed HMI NC/PLC variable screen.
Use the machine builder documentation as the final source for production tags.
Result
The SINUMERIK 840D sl is now connected to Reniway Edge and can be used as a live machine data source through polled SINUMERIK NCK variable addresses, PLC addresses, and supported event subscriptions.