Yunni AI · Real cases, redacted

A real, peer-industry case with numbers beats a hundred-page brochure

We only publish work we have actually done. Every client identity is redacted; every figure is an indicative range from similar equipment — not a promise of results.

The case standard

If one of these four elements is missing, we do not publish the case.

In which industryThe specific segment and machine type
In which equipmentThe equipment name, control-system makeup and unit count
The original riskNo backup / encrypted program / vendor gone / spare parts discontinued
The deliverablesThe result: what risk was eliminated or reduced

The first case · steel-pipe end-processing machine

The equipment family we understood first and most thoroughly

The equipment

Type: steel-pipe end-processing machine (end-cutting / end-punching). Dual-station layout with end-head trolley, feed trolley, wire brush, rotary rollers, hydraulic station, pulse dust collector, pinch rollers, tool holder, pipe pusher, brake and other mechanisms.

In detail: the machine is built around a Siemens S7-1200 CPU 1214C with SM1223 and SM1221 digital expansion modules; multiple SINAMICS G120C variable-frequency drives; 2 servo axes; PROFINET communication to the host; 2 end-punching operator stations. About 54 digital inputs.

EPLAN schematics: 34 A3 pages, GB-standard label structure, covering electrical diagrams, component selection, network topology and operator-station panels.

The original risk

The equipment was designed and built by a small out-of-town machine builder with limited service reach. Once that builder pivots or stops supporting the line, the machine loses its software layer — programs cannot be read, faults cannot be diagnosed, functions cannot be modified. The machine will remain in service for years, so the risk grows over time.

The work

Reviewed every drawing and compiled a control-system “brain” inventory (CPU, expansion, drives, servos, motors, sensors, analogue modules, network, operator stations, protection elements and estimated point counts); mapped the 10-step dual-branch process flow (end-cutting/grinding line A, end-punching/cutting line B, sharing automatic-stop and homing states); built a program-logic draft as the foundation for later reading, custody and retrofit.

The principle

The mechanical, hydraulic and pneumatic hardware can be bought, repaired or even replicated in China. The software layer is what most factories cannot recover once it is lost. Our role is to be the software steward for this machine.

Inventoried control systemS7-1200 · 2 expansion modules · 3 G120C drives · 2 servo axes
Archived program & tag table12 program blocks · annotated tag table ~300 points
Process logic mapped10-step dual-branch flow (line A cutting/grinding · line B punching/cutting)
Drawings interpreted34 A3 EPLAN pages turned into a searchable logic draft

Figures above are indicative, redacted quantities for this equipment family, not a single client’s measured values.

Note about cases: We only talk about real work; every client identity is redacted. The case above is the starting point we have fully understood and turned into a methodology. More cases will be added after written client authorization and redaction confirmation. If you need delivery records or sample deliverables for similar equipment, contact us by phone and we will tell you exactly what we can provide.

Three case scenarios · indicative results (redacted)

Equipment configurations are typical for the machine family; figures are indicative ranges showing the range of expected outcomes

Case 2 · food filling & packaging line (multi-axis servo + weighing)

Equipment & process: automatic filling, capping, labelling and boxing line; Omron CJ2M main controller, 2 Weinview touch panels, 4-axis servo linkage, weighing-module analogue feedback.

Original risk: integrated years ago by a small out-of-town integrator that has since discontinued service; 2 program blocks were read-protected and unreadable; the plant had no program or drawing backup; a previous fault caused several hours of downtime.

What we did: read and verified the readable program on-site; documented the 2 protected blocks with notes on their limitations and alternative handling; built a program-and-drawing asset register; set up an off-site dual backup and performed a restore drill; produced fault-location flowcharts for critical stations.

Indicative results (redacted): unplanned downtime dropped from ~4 events per month to under 1; average fault-location time compressed from ~2 hours to under 30 minutes; program backup completeness rose from ~40% to 100%; one full restore drill performed, 100% success.

Case 3 · automotive parts processing & assembly line (imported controller discontinued)

Equipment & process: machining + assembly line; 4 imported PLC main controllers that have been discontinued by their vendor for more than five years, with servo drives and safety-interlock circuits.

Original risk: spare parts only available on the secondary market, at high prices and with uncertain lead times; the vendor no longer supplies software or firmware support; a main-controller failure would stop the whole line with no replacement path.

What we did: mapped existing process cycle and safety-interlock logic; reverse-engineered the control logic; ported the logic to a controller family that is still in production, preserving original cycle time and safety functions (every safety-circuit change confirmed in writing); staged switchover with a rollback path retained.

Indicative results (redacted): 4 controllers and 6 program blocks migrated; 2 weeks of continuous trial run, zero unplanned downtime; key spare-part lead time reduced from ~8 weeks to under 1 week; investment payback estimated at ~14 months based on avoided downtime loss and spare-part premium.

Case 4 · non-standard special-purpose machines (program rescue + annual support)

Equipment & process: 3 non-standard special machines, Siemens S7-300 and Mitsubishi FX3U mixed, with analogue and temperature-control loops, line cycle ~20 pieces per minute.

Original risk: programs existed only on one engineer’s personal PC, with no version history; a hard-drive failure once lost a program version and the team had to rebuild from memory, taking several days.

What we did: read and archived all 3 controller programs, established version numbering and change logs; enrolled in the annual support package with quarterly integrity checks and backup refresh; wrote an operating manual covering key parameters and alarm meanings for hand-over.

Indicative results (redacted): 3 program versions archived, ~480 points, ~90 alarm entries; remote response within 2 hours; quarterly integrity checks 4 times per year, all identified defects were addressed during planned downtime windows; version-loss rebuilds reduced to zero.

Figure note: the result numbers in the three scenarios above are indicative, redacted quantities showing the typical range of expected outcomes on similar equipment. They are not measured values from any single client project and do not constitute a performance guarantee. Real delivery records and sample deliverables are provided only after written client authorization and redaction confirmation.

The library keeps growing

Because every machine we finish adds material to the program asset library

Re-usable within the same industry

De-duplicated control-logic templates for similar equipment can be re-used, so the second and third machines of the same family are delivered faster and with higher quality.

A thicker fault library

Every fault diagnosis and fix is recorded, building our own diagnostic handbook — that is why we can quote the response speeds we do.

Not sure if we can help? Start with a free remote check

Tell us the controller model, brand and whether the program is encrypted. We will give a “yes / no / roughly how much” verdict before any on-site visit.

Mr. Deng · General Manager · Changsha-based; Hunan Province and nationwide on-site service available

微信二维码(扫码添加 13369210212)扫码加微信13369210212 · 发照片或图纸,当天给答复