Direct Answer

An old machine in the workshop needs data acquisition and remote control — should you install a CX industrial wristband or a CC cloud PLC? In one sentence: the CX industrial wristband is "putting a smartwatch on the equipment" — 8 DI plus 8 AI for acquisition with limited control, leaving the existing electrical cabinet untouched, suiting fast onboarding of legacy equipment in collect-only scenarios; the CC cloud PLC is "swapping in a cloud brain" — an 8 DI plus 8 DO host with DIO/AIO/temperature expansion modules, running 300+ Mistudio instructions, suiting line retrofits that need new control logic, remote start-stop and motion control. The rule: acquire data without changing logic, choose CX; add new control logic, choose CC.

A scenario: One workshop has an old injection-molding machine with a closed PLC interface, and the team does not want to touch the cabinet — install the CX wristband: 8 DI channels collect running signals and 8 AI channels collect temperature and current, data to the platform, original control untouched. Another old punch press needs "remote emergency stop plus automatic loading/unloading" logic — go with the CC cloud PLC: host plus expansion modules, ladder logic written in Mistudio, new logic deployed from the cloud. The same legacy retrofit — choose CX to "watch", choose CC to "control".

1. Acquisition and Control Capability Comparison

I/O points — CX offers 8 DI plus 8 AI; CC offers an 8 DI plus 8 DO host, expandable with DIO/AIO/temperature modules; Control capability — CX has only limited control; CC runs 300+ Mistudio instructions and motion control; Retrofit invasiveness — CX leaves the existing cabinet untouched; CC joins the control loop and requires new logic; Development threshold — CX needs no development, configure and go; CC needs ladder programming (accessible to electrical engineers); Positioning — CX is "sense plus light control"; CC is "logic plus control" — one wears a wristband, the other swaps in a brain.

In one sentence: CX versus CC is 8 DI plus 8 AI light acquisition versus an 8 DI plus 8 DO expandable host — collect-only selects CX, new logic selects CC — one is a wristband, one is a brain.

A comparison example: Two old machines in one workshop: A only needs temperature and current on the platform (CX, configure and go); B needs "auto-stop on over-temperature" logic (CC, ladder logic in Mistudio). Both add acquisition — but "whether to change control logic" is the divide — changing logic requires CC.

2. The CX Industrial Wristband: A Smartwatch for Equipment

CX's role — sense first: 8 DI collects discrete signals, 8 AI collects analog quantities; CX's form — parallel access: the existing cabinet is untouched; it "wears" on the equipment like a wristband; CX's scenarios — collect only, no control: running status, temperature and current of old equipment go to the platform; CX's advantage — fast retrofit: no development, configure and go, minimal downtime; CX's boundary — cannot run new logic: acquisition plus limited control only; it does not replace a PLC.

In one sentence: the CX industrial wristband is 8 DI plus 8 AI sensing, parallel access and no development — suiting legacy equipment "collect only" — fast retrofit is its core value.

A CX example: One factory has 30 old motors: a CX wristband per motor, 8 DI for start-stop status and 8 AI for current and temperature — data to the platform, cabinets untouched — 30 units onboarded in one weekend. CX's value is rapid digitization of legacy equipment — no cabinet removal, no rewiring, no development — a "data wristband" for existing assets.

3. CX's Typical Scenarios: Collect-Only and Parallel Access

Scenario one, collect only — the equipment only needs data, not control: running status, temperature and current on the platform suffice; Scenario two, parallel access for old equipment — the PLC interface is closed or too old: CX collects in parallel without affecting the original control; Scenario three, quick survey — data survey before a retrofit: install CX to collect for a while, then decide whether to make big changes; Scenario four, non-standard equipment — no standard communication interface: CX's DI/AI connect directly to sensor signals; The common thread — as long as it is "watch, not control": CX is the least invasive way in.

In one sentence: CX's typical scenarios are collect-only, parallel access for old equipment, quick survey and non-standard access — the common thread is "watch" — data without logic.

A scenario example: One food workshop: an old packaging machine with a closed interface — a CX wristband collects running status and temperature in parallel — the original PLC untouched, data on the platform — failure statistics now have a basis. Parallel access to old equipment is CX's most common scenario — the original system stays, the data still comes.

4. The CC Cloud PLC: Swapping in a Cloud Brain

CC's role — logic control: an 8 DI plus 8 DO host, expandable with modules; CC's form — joins the control loop: replaces or bypasses the original logic, new logic deployed from the cloud; CC's scenarios — new logic, remote start-stop, motion control, auto-stop on over-temperature; CC's advantage — programmable: 300+ Mistudio instructions, ladder development by electrical engineers; CC's boundary — a larger retrofit than CX: wiring, logic writing and commissioning — count the investment before choosing.

In one sentence: the CC cloud PLC is an expandable 8 DI plus 8 DO host, Mistudio programming and cloud control — suiting lines that need new logic — the retrofit is larger than CX, and so is the value.

A CC example: One stamping line adds "safety light curtain plus remote start-stop" logic: the CC host takes the light-curtain signal, interlock logic written in Mistudio, deployed from the cloud — remote start-stop and abnormal shutdown both realized. CC's value is giving old equipment a new brain — not replacing the machine but the control logic — the main force of line-level intelligent retrofits.

5. CC Expansion Modules: DM160/AI080/PT040

DIO expansion module — digital expansion: add DIO modules when DI/DO points run short; AI expansion module — analog expansion: modules such as AI080 add more analog channels; Temperature expansion module — PT040: connects PT100/PT1000 resistance thermometers directly; Combining expansions — configure by site points: DI/DO/AI/temperature stack on demand; The point of expansion — host plus expansion equals on-demand growth: host only for small projects, modules for large ones.

In one sentence: CC expansion modules are DIO (digital), AI (analog) and PT040 (temperature) — the host plus modules stacks on demand — add modules when points run short instead of replacing the host.

An expansion example: One kiln retrofit: 8 DI on the host was not enough — a DIO module expanded to 16 DI and a PT040 connected 4 thermocouples — one CC covers all measurement and control points. Expansion modules let CC grow from a "small PLC" into a "controller that can grow" — fit modules to the site points, and one unit handles it all.

6. Mistudio Ladder Logic: The Programming Threshold for Electrical Engineers

What Mistudio is — the programming environment bundled with CC: ladder and instruction-list development; The ladder threshold — accessible to electrical engineers: a graphical expression of relay-circuit logic; 300+ instructions — timers, counters, comparisons, math and communication instructions are complete; The meaning of cloud deployment — programs need no on-site edits: change logic in Mistudio, deploy remotely from the cloud; The development investment — writing logic plus commissioning: one more step than CX configuration, in exchange for programmability.

In one sentence: Mistudio is ladder programming, 300+ instructions and cloud deployment — electrical engineers think in relay logic and can start — one step beyond configuration, in exchange for programmability.

A Mistudio example: One electrician wrote a "star-delta start plus overload stop" ladder using relay logic: dragging instructions in Mistudio, compiling and downloading — the logic runs, managed from the cloud — done without a dedicated PLC engineer. Mistudio's threshold is designed for electrical engineers — no C language required, relay logic required — know how to read a circuit diagram and you can write ladder logic.

7. Selection Judgment: Four Questions to Decide CX or CC

Question one, new logic or not — collect only selects CX; adding control logic selects CC; Question two, cabinet changes or not — untouched cabinet selects CX; joining the control loop selects CC; Question three, are points enough — 8 DI plus 8 AI sufficient selects CX; insufficient selects CC with expansion; Question four, development resources — no development selects CX; an electrical engineer writing ladder selects CC; The conclusion — all four questions concern "control": want control, CC; watch only, CX.

In one sentence: the four selection questions are new logic, cabinet changes, point sufficiency and development resources — want control, choose CC; watch only, choose CX — the divide is always "control".

A judgment example: One workshop surveyed first: CX collected data for two weeks and found "circulation pumps idling at night waste energy" — adding "automatic night shutdown" logic called for an upgraded plan with CC — first CX to see the data, then CC to control — two steps. Selection is not a one-time decision — CX to see data first, CC to add control later — data-driven decisions are more accurate.

8. Common Pitfalls: Four Traps in Legacy-Equipment Retrofits

Trap 1 — buying CC for collection only — paid PLC money and effort for data alone: CX configure-and-go is cheaper; Trap 2 — buying CX when control is needed — CX has only limited control: new logic is impossible, rework to CC; Trap 3 — ordering before counting points — 8 AI insufficient: CC with expansion modules or multiple CX units in parallel; Trap 4 — ignoring the development investment — CC assumed to be programming-free: ladder writing and commissioning take time — reserve the schedule.

In one sentence: the four traps are collect-buys-CC, control-buys-CX, points uncounted and development ignored — the first two go wrong on direction, the last two on investment.

A trap example: One project bought a CC cloud PLC just to "view temperature remotely": two weeks spent writing ladder logic, when CX configuration would have taken ten minutes — remote data viewing uses CX, remote control uses CC. Legacy retrofit asks "control or not" first — do not buy a PLC without control needs — with the direction right, the investment is not wasted.

9. Back to YESLON: How the CX/CC Lands

CX-08R06AI08-C1/C2/C3 — the industrial wristband series: 8 DI plus 8 AI sensing, fast onboarding of legacy equipment; CC100/CC101 — the cloud PLC series: an 8 DI plus 8 DO host, expandable and able to grow; Mistudio — the bundled programming environment: ladder development plus cloud deployment, accessible to electrical engineers; The division of labor — CX handles sensing and light control; CC handles logic and control — divided by retrofit goal; The landing order — ask "watch or control" first: watch chooses CX, control chooses CC — then count points, then configure expansion.

In one sentence: CX/CC lands as CX wristband for sensing, CC cloud PLC for control and Mistudio for programming — ask "watch or control" first, and configure right once the direction is set.

A landing example: One group's line retrofit: 30 legacy devices with CX for data (cabinet untouched, no development); 3 lines with new logic on CC plus expansion (ladder logic, cloud deployment) — watch and control each in place, the retrofit lands in two batches. CX and CC are not competitors — they divide the work — digitize with the wristband, intelligentize with the brain — choose the right product for the goal and legacy retrofits never rework.

Scope and Limitations

  • The conclusions in this article are intended for LV distribution and electrical-safety sites. Criteria are compiled from public codes and FEXLINK product documentation, and product parameters follow the latest selection handbook and product knowledge base.
  • Quantitative criteria (protection zone, discharge and residual voltage, earth resistance, thresholds and grading) hold under the preconditions stated in this article. Where the site voltage level, earthing arrangement, environmental category or load profile differs, the figures must be recalculated. Specific configurations involving CX-08R06AI08-C1/C2/C3、CC100/CC101、Mistudio should be verified against actual circuit parameters.
  • Specific product models and parameters are subject to the latest selection handbook and product knowledge base; this article does not constitute selection or procurement advice.
  • Standard numbers cited here refer to the currently effective editions; when a standard is revised, the related quantitative conclusions must be re-checked.
  • Deployment and implementation for specific projects must be carried out by qualified engineers based on site survey and design drawings.

Frequently Asked Questions

CX Industrial Wristband vs CC Cloud PLC

An old machine in the workshop needs data acquisition and remote control — should you install a CX industrial wristband or a CC cloud PLC