QQ: 859818709

RayTools xNCI CNC Integration Software Module, Third-Party Servo, IO and Sensor Adaptation

RayTools xNCI CNC Integration Software Module, Third-Party Servo, IO and Sensor Adaptation

Price on request
Category:

Description

Product Overview

xNCI is the integration layer of the RayTools xEOS software ecosystem. Its scope is narrow and deliberate: take hardware that did not ship with xEOS – third-party servo drives, IO blocks, sensors and peripheral devices – and make it behave as though it were native to the platform. An integrator describes a device once through one uniform interface, and from that point the machine control sees an axis, a signal or a measurement instead of a vendor-specific protocol. The module is written for system integrators and machine builders. It is not an operator tool, and in normal production it does not appear on the screen at all.

The commercial reason the module exists is schedule. On a non-standard laser machine the mechanical build is usually the predictable part; what stretches is electrical and control integration, where every drive vendor brings its own commissioning tool, its own parameter set and its own way of reporting a fault. xNCI collapses that into one model with one commissioning path, so a device that is new to the project no longer means a new development task. Axis control and IO management sit in the same environment, which lets a servo axis, a limit switch and an analogue sensor be proven together on the bench – the point in a build where a fault is still cheap to correct.

What xNCI does not do matters as much as what it does. It does not replace the machine control system, and it does not design the process: choosing a nest, a lead-in or a parameter set is the work of xStudio in the same ecosystem. xNCI widens the set of hardware that an xEOS-controlled machine can be built from, and stops there. Licensing is by module and by version, and the module is normally quoted together with the control system it will run on. The table below covers deployment, integration scope, functional modules and licence terms; the device list for a specific project is confirmed against your own hardware bill of materials rather than assumed from the table.

Key Features

  • One integration interface: third-party devices join the platform through a single documented interface, so the control model does not change when the drive brand does
  • Axis control: multiple axes are configured, referenced and monitored from one place, with per-axis parameters held in the project rather than buried in a drive vendor tool
  • IO management: digital and analogue signals are mapped by table, so adding a sensor or a solenoid is a configuration step instead of a code change
  • Commissioning before assembly: each device can be proven against the module on the bench, which moves faults earlier in the build and out of the final week
  • Diagnostics in one view: drive status, IO state and device faults are reported together, which shortens the search when a machine stops for a reason the operator cannot see
  • Documented for integrators: interface documentation, a configuration workflow and SDK access, so the work is repeatable across projects instead of living with one engineer
  • Shorter non-standard development: because adaptation is configuration, the schedule of a bespoke machine is driven by mechanical build rather than by control development

Technical Specifications

Brand Empower / RayTools
Model xNCI
Product type CNC integration software module
Ecosystem xEOS platform
Deployment Installed on the machine control PC or on an industrial PC in the same control network segment
Terminal support Engineering workstation for configuration and commissioning; runtime on the machine control terminal
Integration target Third-party servo drives, digital and analogue IO modules, industrial sensors and peripheral devices
Functional modules Hardware adaptation, axis control, IO management, device diagnostics
Interface model One uniform integration interface inside xEOS, with SDK and documentation for integrators
Device classes Mainstream servo drives, IO blocks and common industrial sensors; the exact list is confirmed per project
Configuration method Parameter and mapping tables plus a commissioning toolset; no source code required for standard devices
Licence model By module and by version, per machine; can be bundled with a control system
Hardware specification Not applicable – software product, licensed separately from the machine it runs on

Applications

xNCI is used wherever a laser machine has to be assembled from hardware that the platform did not supply. Typical projects share one trait: the mechanical design is settled before the electrical design, and the electrical design is where the uncertainty sits.

  • Non-standard laser machines whose servo platform is chosen by the customer rather than by the machine builder
  • Retrofits that must keep an existing drive family while the control layer is modernised
  • OEM builders who ship the same machine to several customers with different preferred drive vendors, and want one control model instead of one per customer
  • Production lines that add sensing after the machine has been specified – gap measurement, seam position, temperature – without reopening the control software
  • Integration houses that build a reusable hardware library and want the next machine to start from it

A project normally begins with the hardware bill of materials: drive models, IO block types, sensor interfaces and the communication each device speaks. That list is checked against the current adaptation set, the gaps are quoted, and only then is a commissioning plan written. Sending the list early is the difference between a quotation and a guess.

Selection Guide

  • Scope the device list before the licence: send drive models, IO block types and sensor interfaces, and the configuration is confirmed against them rather than assumed
  • Decide the split between xNCI and xStudio at the start. xNCI handles what the machine is made of; xStudio handles what the machine does. Mixing the two in one requirement list is the usual reason a quote comes back late
  • If the machine already runs an xEOS control system, confirm the current control version first, because module versions follow the control version and not the other way round
  • The licence is per machine, per module and per version. A second machine on the same site is a second licence, and moving to a new major version is a separate decision from adding a device
  • For a multi-vendor line, keep one configuration file per machine type and reuse it. Rebuilding the same mapping for every unit is where inconsistency between identical machines comes from
  • Allow commissioning time per device rather than per machine. Ten devices proven individually take less total time than ten devices discovered together at the end

Series Comparison

xNCI belongs to the xEOS software suite, whose modules divide the plant by the question each one answers. The boundaries are deliberate, and each module is a separate licence.

Module Layer Question it answers Main user
xNCI Hardware integration What is this machine built from, and how does the control reach it System integrator, machine builder
xStudio Process programming What is being cut, in what order, with which parameters Process engineer
xERP Order and work order What has to be made, by whom, and how far along is it Production planning
xMES Shop floor execution What actually happened at the machine, and can it be evidenced Workshop supervisor, quality
xSmart AI agent Assistance How do I operate, diagnose or document this Operator, service

xNCI can be licensed and used on its own. It becomes more useful when xStudio is also present, because a machine that is easy to build is also a machine that can be given a proper process file. The reverse is not true: xStudio does not make a third-party drive visible to the control, and no amount of process design compensates for hardware the platform cannot address.

Usage Precautions

  • Version alignment: the module version must match the control system version. Confirm the compatibility matrix before upgrading either side, and never upgrade the control and the module in the same maintenance window
  • Back up the configuration before any change: axis parameters and IO mapping are project data, not part of the installer, and they are not restored by reinstalling the module
  • Network and addressing: use fixed addressing on the machine network, kept separate from the office LAN. Changing an address after commissioning invalidates the mapping that was proven on the bench
  • Licence binding: licence files are tied to the machine. Replacing the control PC or the network adapter can require a re-issue, so plan the hardware change before the licence expires, not after
  • Upgrade path: run a new module version on one machine through a full production cycle before rolling it out to a line, and keep the previous installer until that cycle has finished
  • Who should configure: the module assumes an integrator or a trained technician. An unintended axis parameter change can move a machine outside its safe working envelope. Safety functions such as interlocks and emergency stops belong to the safety circuit and are not configured here

FAQ

Which hardware can be connected?
Mainstream servo drives, digital and analogue IO blocks and common industrial sensors. Send the device list and it is checked against the current adaptation set; anything outside it is quoted as an adaptation task rather than assumed to work.

Do we need programming skills to use it?
No for standard devices: mapping is table-driven and a technician can complete it. SDK access exists for integrators who want to script behaviour beyond the standard mapping, and that part does assume software experience.

How is this different from xStudio?
xStudio designs the process, from drawing to machining task. xNCI makes hardware visible to the platform. They are separate licences, they can be bought independently, and neither substitutes for the other.

Does it work on a non-RayTools control system?
xNCI is an xEOS module and runs inside that platform. On a third-party control it is not a drop-in component; the integration is assessed per machine, and in most cases the honest answer is that the control layer has to change first.

What happens when we add a second machine?
A second licence. The configuration file can be copied from the first machine, which is the practical benefit of doing the work once, but the licence itself is machine-bound.

About the Brand

RayTools, trading as Empower, builds laser cutting heads, welding systems and the xEOS software suite that connects them. xEOS is organised by plant function rather than by product family: hardware integration, process programming, order management, shop floor execution and AI assistance are separate modules with separate licences. This page covers xNCI only. The other xEOS modules have their own pages, and buying one does not entitle you to another.

Disclaimer

Specifications on this page are compiled from the manufacturer’s published material and from existing documentation, and are provided as a selection reference. The delivered product is defined by the physical unit, the factory test report and the current manufacturer specification; software behaviour also depends on the control system version it is installed on. Configurations may change between batches, so confirm the details with us before ordering. Reproduction of this page without written permission is not permitted.

Selection enquiries: Changsha Soar Laser Equipment Co., Ltd., hotline +86 159 2722 0467, www.soar-laser.cn, email 859818709@qq.com.

Reviews

There are no reviews yet.

Be the first to review “RayTools xNCI CNC Integration Software Module, Third-Party Servo, IO and Sensor Adaptation”

Your email address will not be published. Required fields are marked *

中文EN