Loom & knit controllers
Picanol, Toyota, Tsudakoma, Karl Mayer and Mayer & Cie controllers over OPC UA and vendor PLC tags.
Integrations
It reads your mill. It does not replace it.
Yarneon sits beside the controllers, recipe systems, spectrophotometers, cameras, meters and MES you already own. Connectors read first, write only inside an agreed envelope, and every write is logged.
Integrations
Eight connector families
The machines, instruments and systems a textile mill already runs, grouped by the stage they serve.
Spinning frames
Rieter, Trützschler, Saurer and Murata frames, draft, twist, speed and end-break telemetry.
Dyeing & finishing
Thies, Fongs, Brazzoli jets and Monforts/Brückner stenters via PLC, recipe systems and dosing units.
Colour & lab
Datacolor and X-Rite spectrophotometers, colour libraries, Pantone TCX standards and lab-dip workflows.
Inspection hardware
Line-scan RGB and NIR cameras, Uster and Elbit inspection frames, existing light boxes.
MES / ERP
SAP, Datatex, TIM, Coats Digital and homegrown mill MES over REST, files and database CDC.
Utilities & sustainability
Water, steam and electricity meters; ZDHC Gateway, Higg FEM and OEKO-TEX reporting.
Robotics
Vision-guided manipulators and AMRs on NVIDIA Isaac and Jetson for doffing, beams and roll transport.
Vendor names are listed for compatibility reference only and do not imply endorsement or partnership.
Compatibility
Systems and what we do with them
Reading is the default for every system. Writing is limited to the setpoints a process owner has authorised, inside an envelope, with a revert path.
| System family | How we connect | What we read | What we may write |
|---|---|---|---|
| Loom and knit controllers | OPC UA, vendor PLC tags | Tension curves, pick and course density, stop causes, efficiency, beam state | Let-off, take-up, speed and tension setpoints, inside the envelope |
| Spinning frames | Vendor PLC tags, evenness-tester exports | Draft, twist, speed, end-break and evenness telemetry | Draft ratio, spindle speed, twist multiplier, doffing schedule |
| Dyeing and finishing machines | PLC, recipe systems, dosing units | Exhaust curve, temperature ramp, pH, conductivity, liquor ratio, stenter profile | Dosing schedule, ramp and hold, pad-bath concentration, overfeed, line speed |
| Colour and lab | Spectrophotometer SDKs and exports, colour libraries | Bath and roll spectral reads, buyer standards, lab dips | Nothing. Colour instruments are read only |
| Inspection hardware | Camera SDKs, existing inspection-frame outputs | Line-scan and NIR frames, existing defect events | Stop requests to the machine, through its own controller |
| MES and ERP | REST, file drops, database change capture | Lots, work orders, specs, buyer standards, shift context | Run events, approvals, holds, releases and conformance packets |
| Utilities | Water, steam and electricity meters; reporting gateways | Consumption per lot and per machine | Reports to ZDHC, Higg FEM and OEKO-TEX workflows |
| Robotics | NVIDIA Isaac and Jetson, safety PLCs | Robot state, cell cameras, safety zones | Doffing, roll and beam moves, behind safety interlocks |
Vendor names on this page are listed for compatibility reference only and do not imply endorsement or partnership. Connectors are built design partner by design partner; long-tail integrations are out of scope for the first release.
Connection
How a mill gets connected
Connectors go in before any model runs, and the mill sees what is being read before anything is written.
-
Phase 1
Network segmentation
The edge appliance sits in the OT network with a minimal, documented path to the control plane. No inbound ports on the mill network.
-
Phase 2
Tag mapping
Every tag Yarneon may read or write is listed and reviewed with the automation engineer. The write list is short and signed.
-
Phase 3
History backfill
Lot outcomes, shade records and defect history are backfilled so models train and baselines come from your data.
-
Phase 4
Validation in shadow
Readings and recommendations run in shadow until the mill agrees they match what the crew sees on the machine.
Boundaries
What Yarneon deliberately does not do
Out of scope by design
Yarneon is a control layer, not a replacement for the systems that run the mill today. The boundaries below are deliberate and are written into the connector scope.
- Not an MES or ERP: lots, orders and inventory stay where they are
- Not a PLC replacement: every write goes through the machine’s own controller
- No unbounded writes: a model output cannot reach a setpoint outside its envelope
- No colour instrument control: spectrophotometers are read only
- No cross-tenant data: one mill’s recipes and rolls never train another’s models
Write policy
Short list, signed
The list of writable tags is agreed with the process owner, versioned, and reviewable in the audit log.
Revert
One button
At the machine panel.
Offline
Keeps running
Local loop, buffered record.
Tool-call stream
Integration calls, in the open
Every connector call and result in the scenario run is text in the log: the MES lookup, the twin, the spectrophotometer, the PLC dose and the release.
04:02:11
result: mes.get_lot("DL-4471") → 14 rolls · 3,180 kg · poplin 40s
SUCCEEDED
04:02:12
call: twin.simulate(recipe_candidates=3, machine="jet-07")
RUNNING
04:02:58
result: twin.simulate → best ΔE 0.52 · cycle 118 min · water 46 L/kg
SUCCEEDED
04:03:01
call: colour.predict_recipe(substrate="cotton", standard="19-4028 TCX")
RUNNING
04:03:03
result: colour.predict_recipe → Navy RGB 2.14% · Blue BRF 0.61% · Black B 0.08%
SUCCEEDED
04:03:04
call: policy.check(action="dose", deviation=7.2%) → requires human approval
APPROVAL
04:18:22
result: human.approve(user="colourist-on-shift", decision="approve", note="ok, hold ramp")
SUCCEEDED
04:18:24
call: plc.dose(machine="jet-07", schedule="ramp-B")
RUNNING
05:41:07
result: spectro.read(bath) → exhaustion 96.4% · bath ΔE 0.41
SUCCEEDED
06:22:40
result: vision.scan(roll=09) → WEFT_STREAK 412–445 m · severity 3
FAILED
06:22:41
call: cuopt.replan(cut_plan, constraint="ship_thu_0600")
RUNNING
06:22:43
result: cuopt.replan → 33 m to seconds · ship date held
SUCCEEDED
06:25:02
result: quality.release(lot="DL-4471") → 13 Grade A · 1 Grade B · packet signed
SUCCEEDED
Guardrail in action
policy.check → requires human approval
At 04:03:04 the proposed recipe deviated 7.2% from the standing card, above the 5% autonomy ceiling for dye dosing at this mill. The agent stopped and asked. Fifteen minutes later a colourist approved it, and that approval is attributed, timestamped and reversible.
Failure handled honestly
vision.scan → WEFT_STREAK, roll 09
A 33 m weft streak is a real defect, and the run shows it as failed rather than smoothing it over. The mechanical root cause, a stenter pin-chain slip, was correlated automatically and raised as a work order.
Agent graph
One run, ten steps, one human decision
This is the shape of a dye lot on Yarneon, shown as an illustrative scenario rather than a customer run. Ingest and simulation fan out, converge on a colourist approval gate, then dosing, verification, finishing, inspection and release. The accent traces the active path; every node opens in the inspector.
Scroll the graph sideways · or open the text equivalent below
SUCCEEDED APPROVAL FAILED RUNNING
Text equivalent, workflow steps, dependencies and status
| Step | Stage | Depends on | Status | Duration |
|---|---|---|---|---|
| ingest | conformance | none | SUCCEEDED | 0.8s |
| twin | simulate | ingest | SUCCEEDED | 46s |
| recipe | dye + colour | ingest | SUCCEEDED | 2.4s |
| approve | human gate | twin, recipe | APPROVAL | 4m 12s |
| dose | bath control | approve | SUCCEEDED | 118m |
| shade | verify ΔE | dose | SUCCEEDED | 9.1s |
| finish | stenter | dose | SUCCEEDED | 64m |
| inspect | vision | shade, finish | FAILED | 38m |
| rework | replan | inspect | SUCCEEDED | 1.6s |
| grade | release | rework | SUCCEEDED | 3.0s |
- Parallel branches2twin simulation and recipe prediction run together
- Human gates1colourist approval, 15 minutes, attributed
- Failures recovered1weft streak on roll 09, replanned in-run
Accelerated computing
Physical AI needs real compute, at the machine
Line-speed vision, spectral colour science and a fabric-line twin are GPU-essential workloads. Yarneon runs them at the mill edge and trains them centrally.
| Component | Role in the mill |
|---|---|
| Isaac + Jetson | Robotic roll, beam and doffing handling, plus mill-edge inference on inspection and control cells. |
| Metropolis / DeepStream + TensorRT | Line-speed fabric-defect vision pipelines targeting sub-100 ms per-frame decisions. ASPIRATIONAL |
| Holoscan | Sensor fusion across cameras, spectrophotometers, probes, PLC events and meters into one explainable state stream. |
| Omniverse + Replicator / Cosmos | The as-produced fabric twin, and synthetic generation of rare defect, barré and shade-variation cases. |
| cuOpt | Dye-lot sequencing, rework queues, machine assignment and water/energy allocation under hard constraints. |
| Triton + NIM + NeMo | Multi-model serving at the mill edge, plus grounded textile-process and colour reasoning with citations. |
| NVIDIA AI Enterprise | Private and on-prem deployment for groups protecting dye recipes and construction IP. |
Items marked ASPIRATIONAL describe target architecture ahead of full production validation.
Guardrails
An agent earns the right to touch a machine
Nothing here is a global "AI on" switch. Autonomy is granted per setpoint, bounded by policy, reversible by any operator and logged permanently.
- Graduated autonomy
- Every workflow moves observe → assist → bounded auto-control. Autonomy ceilings are per-setpoint policy, not a global switch.
- Human-in-the-loop gates
- Approval gates fire on deviation thresholds, new substrates, or any action outside the authorised envelope. Approvals are attributed and time-stamped.
- Reversibility
- Every control action ships with a revert path and a last-known-good setpoint. Operators can take manual control at any moment, from the HMI or the panel.
- Immutable audit log
- Assurance-grade, append-only record of every observation, decision, tool call, approval and actuation, exportable for buyer and regulatory audit.
- Tenant isolation
- Recipes, construction libraries and roll data are isolated per tenant. No cross-tenant training. Permission-aware retrieval with enforced citations.
- Sandboxed tools
- Agents call machines through a typed, scoped tool layer with rate and range limits. There is no path from a model output to an unbounded PLC write.
Enterprise
Built for groups, not just for one dyehouse
Multi-site rollout, group benchmarking, governance that a CIO recognises, and deployment options for producers who will never put a dye recipe in someone else’s cloud.
Governance a textile group can actually sign
Approval policies, spend limits, autonomy ceilings and audit exports are configured per site and enforced centrally. Group leadership sees which mill holds shade best on which family, and the mills see why.
- SSO (SAML/OIDC), SCIM provisioning and RBAC down to the setpoint
- Per-site data residency, private VPC or fully on-prem deployment
- Group benchmarking across right-first-time, seconds, water and energy
- Signed SLAs, named mill engineers and quarterly outcome reviews
- Outcome-based commercial components on yield, re-dyes and utilities
Group view
One group, one standard
Right-first-time shade by site and shade family, normalised for substrate mix, so a fair comparison is possible for the first time.
Rollout
Shadow first
Wedge line in shadow, then assist, then control.
Autonomy
Per setpoint
Granted one at a time.
Questions
Integration questions
The control loop lives at the mill edge. Inference, guardrails and the audit log run locally on the edge appliance, so a lost uplink degrades reporting and retraining, not machine control. Buffered telemetry syncs when the link returns.
Design partners start with one wedge line in shadow mode: connectors and telemetry first, then models scored against what the mill actually produced, then assist mode where the agent proposes and an engineer approves. Whole-mill rollout follows once the wedge holds its numbers. Durations depend on how instrumented the mill already is, so we quote them after the assessment, not before.
To predict recipes well, yes, and that IP never leaves your tenant. Retrieval is multi-tenant isolated, models fine-tuned on your data are yours, and on-prem deployment is available for groups that will not put recipes in any cloud.
A Jetson-class edge device per inspection or control cell, one GPU server per mill for multi-model serving, line-scan cameras where in-line inspection is in scope, and a spectrophotometer feed for colour work. We survey the existing fleet first, most mills already have more sensing than they use.
Vendor inspection tells you a defect happened on one machine. Yarneon closes the loop across the mill: it links the defect to the yarn lot, the loom, the dye bath and the stenter, replans the cut and the schedule, and carries the evidence into the buyer packet.
Check your stack
Send your machine list, your MES and your instruments. We will tell you what connects today, what needs a connector built, and what stays out of scope.
