After the correct runtime entitlements are confirmed and applied, the Berghof PLC can load the intended CODESYS SoftMotion CNC application without relying on an assumed license bundle. The purchasing decision must come from the PLC’s installed runtime, the application components actually used, and Berghof’s licensing rules—not from the controller being described as SoftMotion-capable.
What is installed on the controller now?
Start at the controller. The installation described has a license for Modbus only. That fact establishes the current entitlement but says nothing about whether motion components are included elsewhere in the Berghof runtime package.
Separate capability, installed software, and licensing. A controller can support a technology while lacking the entitlement required to execute an application that uses it. Likewise, an engineering package may allow configuration or compilation even when the target runtime cannot run the downloaded project.
| Item | Known state | Commissioning implication |
|---|---|---|
| Controller | Berghof PLC | Use the exact controller and runtime identification when requesting a license quotation. |
| Motion capability | Described as SoftMotion-capable | Capability alone does not identify the supplied entitlement. |
| Existing entitlement | Modbus license only | Treat additional motion licensing as unresolved until the installed license inventory and Berghof package are checked. |
| Requested function | SoftMotion CNC | Build the license list from the CNC application and its runtime dependencies. |
Read the controller’s license inventory and record the exact runtime identification. The check passes when the installed entitlements and target identity are documented rather than inferred from the hardware description.
Which application components will the project use?
Follow the execution path from the application to the runtime. The proposed purchase includes SoftMotion SL and SoftMotion CNC_Robotics SL; the unresolved item is SoftMotion Light SL. Similar names do not establish a prerequisite relationship. A lighter product tier may be an alternative package, a subset, or a separately licensed runtime component. Only the applicable product dependency information and the target manufacturer’s licensing arrangement decide the case.
Inventory the project by function. Record whether it uses CNC path processing, robotics functions, ordinary coordinated motion, or only a limited motion feature set. Then map each used component to the license requirement shown for the exact runtime package.
| Candidate entitlement | Reason it appears in the decision | Status for this installation |
|---|---|---|
SoftMotion SL |
Included in the proposed purchase | Requirement must be confirmed for the Berghof runtime. |
SoftMotion CNC_Robotics SL |
Matches the requested CNC use | Requirement and dependencies must be confirmed. |
SoftMotion Light SL |
Possible additional or alternative entitlement | Do not add or omit it based only on its name. |
| Modbus license | Already supplied on the PLC | Does not resolve the motion-license question. |
The check passes when every motion component instantiated by the project has a corresponding confirmed entitlement or is explicitly documented as included.
Who supplies the runtime license?
The next hop is the license supplier. For a manufacturer-supplied PLC runtime, licensing may be integrated into the controller offering rather than purchased as a generic add-on independently of the hardware. Berghof is therefore the first authority for this target. Ask whether it supplies the required SoftMotion entitlement with the PLC, as an option tied to the controller, or through another defined purchasing route.
A store contact request that has not yet received a response does not answer the technical dependency question. It also does not establish that a store license is compatible with the Berghof runtime. Before ordering, obtain a written mapping between the exact target and the required products.
| Question for Berghof | Why it matters |
|---|---|
| Which SoftMotion licenses are supplied with this exact PLC and runtime? | Prevents buying an entitlement already included by the manufacturer. |
Does CNC use require both SoftMotion SL and SoftMotion CNC_Robotics SL? |
Confirms the base-to-option dependency. |
Is SoftMotion Light SL required, optional, or an alternative? |
Resolves the specific bill-of-materials uncertainty. |
| Who issues the license for this target? | Prevents purchasing through an incompatible channel. |
| What target identifier must be supplied? | Binds the quotation and entitlement to the correct controller or runtime. |
The check passes when Berghof identifies both the required license set and the authorized purchasing path for the exact target.
How do I build the purchase list?
Build the commercial list only after the runtime and application paths meet. Use the following sequence:
- Record the Berghof PLC identification, installed CODESYS runtime identification, and current license inventory.
- List the CODESYS motion components referenced by the final application, including CNC or robotics functionality actually used.
- Send that information to Berghof and request the required entitlement list for the exact target.
- Ask for an explicit answer on whether
SoftMotion Light SLis a prerequisite, an alternative, or unnecessary when purchasingSoftMotion SLandSoftMotion CNC_Robotics SL. - Compare the response against the quotation or store cart. Product names, quantities, target binding, and delivery method must match.
- Purchase only through the channel identified for that Berghof runtime.
Do not substitute a successful engineering-station installation for target compatibility. The runtime executes the motion application, so the runtime entitlement is the controlling item. The check passes when the quotation reproduces the confirmed dependency list without unexplained additions or omissions.
How do I apply and check the entitlement?
Apply the entitlement using the activation method specified for the Berghof target. Preserve the license record and the target identity used during activation. If activation involves more than one device or software layer, follow each hop: engineering workstation, license mechanism, controller runtime, then application component.
After activation, reopen the target’s license inventory and confirm that the purchased product names appear for the intended controller. A license present only on the engineering workstation does not prove that the PLC runtime can consume it.
| Check point | Expected result | Failure direction |
|---|---|---|
| Target identity | Matches the identity used for purchase or activation | Correct the target binding before troubleshooting the application. |
| Runtime inventory | Shows the required SoftMotion entitlements | Review delivery, activation, or manufacturer packaging. |
| Project dependencies | Match the licensed components | Remove unused components or obtain the missing entitlement. |
| Application load | Completes without a motion-license rejection | Capture the exact diagnostic text and identify which component requested the entitlement. |
The check passes when the entitlement is visible at the controller runtime and corresponds to every motion component in the project.
How do I verify the CNC application end to end?
Commission from the lowest layer upward. First verify the controller and motion hardware are operational through the manufacturer’s normal diagnostics. Then verify that the runtime accepts the application. Finally exercise the CNC functions used by the project and watch the runtime diagnostic log during application startup and execution.
- Connect to the intended Berghof target and confirm its identity.
- Read the target license inventory and verify the confirmed SoftMotion products are present.
- Download the final project containing the same CNC and motion components used to determine the license list.
- Start the application and check the runtime diagnostics for missing-license or component-loading messages.
- Execute a controlled CNC test that traverses the application path from CNC command generation through the motion runtime to the configured axes.
If the application fails, follow the request. Identify the component named by the diagnostic, determine where its entitlement is expected, and compare that requirement with the runtime inventory. The final check passes when the production-equivalent project starts, the CNC function executes, and the controller records no license-related diagnostic.
FAQ
How do I know whether SoftMotion Light SL is required?
Ask Berghof to classify SoftMotion Light SL as a prerequisite, alternative, or unnecessary for the exact PLC runtime and project. The product name alone does not define its dependency on SoftMotion SL or SoftMotion CNC_Robotics SL.
How do I check which licenses are already on the Berghof PLC?
Open the target runtime’s license inventory and record every installed entitlement together with the controller and runtime identity. The installation described currently reports only a Modbus license.
How do I choose between buying from CODESYS or Berghof?
Confirm the authorized licensing route with Berghof before purchasing. Manufacturer-supplied runtimes may use licenses packaged or issued specifically for the controller.
How do I prevent buying duplicate SoftMotion licenses?
Compare the PLC’s installed inventory, Berghof’s supplied options, and the final project dependency list. Add an item to the quotation only when it is required by the project and not already included for the target.
How do I prove the SoftMotion CNC license works?
Verify the entitlement in the PLC runtime, download the final CNC project, start it, and execute a controlled CNC test. Accept the result only when the CNC path runs and the controller diagnostic log contains no license-related message.