HELLO CHINA

INDUSTRY CLUSTER · Equipment

Shanghai Minhang embodied-intelligence components

Shanghai Minhang embodied-intelligence components brings servo motors, six-axis force sensing and collision response into one area without turning them into one product. Component provenance, process interfaces and project status for integrated joints each retain the date of their original record.

Formation and regional foundations

Minhang embodied-intelligence components enter complete robots through joints, force sensing and control chips. Once interfaces are frozen, worst-case poses, sustained cycles and fault recovery still have to demonstrate machine behaviour.

Minhang’s embodied-intelligence chain spans joints, force sensing, control chips and machine validation. A signing or list entry does not show that a component has passed temperature-rise, interface and cycle-life tests.

Core geography: A component network in southern Minhang’s Intelligent Valley linking integrated joints, sensing and force control, controllers, robot validation and application integration

Torque, heat and control inside an integrated joint

How backlash data enters life validation

Nodes separate the interfaces of six-axis force sensing, embodied-intelligence chips and southern Intelligent Valley; positions are not actual sites in Shanghai Minhang embodied-intelligence components.

  • Joint integration — Integrated joints combine motor, drive, sensing and braking.
  • Backlash calibration — Reducer backlash is measured across load, heat and direction.
  • Thermal duty — Thermal control shapes torque retention during repeated cycles.
  • Embodied control core — Embodied chips join sensing, control cycles and safety response.
  • Life validation — Life tests record wear, drift, stoppage and recovery counts.

01 · Integrated joints face torque and heat first

Motor, reducer, encoder and brake constrain one another in a small package.

The Minhang plan names servo systems and integrated joints as core directions, while a municipal product list supplies a lightweight joint-module example. Neither provides a universal rating for every duty cycle. A joint rating must be read with duty cycle, reduction ratio and cooling. Handling, polishing and insertion sustain peaks for different periods, while horizontal mounting and a vertical cantilever impose different gravity moments on the same module. Different reduction ratios and arm lengths change allowable load and thermal balance, so one catalogue point cannot transfer across duties.

Peak torque lasting seconds does not replace continuous torque. Reducer backlash, bearing load and housing heat dissipation jointly limit repetitive motion. Repeated acceleration accumulates heat in motor, reducer and bearings, then changes lubrication, encoder drift and backlash. A short peak test can miss protective stops or positioning error that appears after tens of minutes of production. Maximum housing temperature during continuous motion is recorded separately.

A selection sheet should combine load spectrum, speed range, mounting direction, ambient temperature, permissible backlash and life cycles, then ask the supplier to state the test boundary. The supplier should provide continuous and peak torque curves, radial and axial limits, thermal conditions and backlash life, while the buyer supplies the real trajectory. A full worst-pose cycle then checks braking and power-off holding. Brake-release count also enters the life cycle.

  • A joint rating has meaning only with duty cycle, reduction ratio, mounting direction and arm length.
  • Short peak torque cannot reveal temperature rise, backlash drift or protective stops during sustained motion.
  • A full worst-pose cycle should verify brake holding, radial and axial load, and backlash life.

02 · Force control is not a sensor-specification contest

Sampling, filtering, control cycle and mechanical compliance shape collision behaviour.

Minhang actors such as Flexiv appear in force-controlled and compliant applications, while the demand list places sensing and control inside concrete problems. Each case remains tied to its stated workstation. Compliant assembly combines sensing, mechanics and control. If part tolerance, fixture stiffness or contact speed changes at another insertion station, force thresholds and recovery actions from the original case may no longer apply. A fixture change requires a new contact datum check.

A precise six-axis force sensor does not guarantee stable insertion. The system can oscillate or stop falsely when structural stiffness, communication delay or control gain do not fit. Beyond static accuracy, review sampling synchronisation, zero drift, overload recovery and mounting coupling. If the control cycle trails mechanical contact, smoothing can add delay and let the robot continue applying force after a jam. Zero calibration covers both cold and thermally stable states.

Validation should use real workpieces and record contact force, cycle time, false alarms and recovery, retaining the control version and sampling settings. One demonstration cannot replace multi-lot operation. Continuous trials should deliberately introduce misalignment, missing parts, loose fixtures and communication loss, observing safe stop and recovery. Every false stop and failure needs a timestamp, workpiece identity and software version for reproduction. The first part after recovery requires another measurement.

  • Force thresholds follow part tolerance, fixture stiffness and contact speed and need renewal after a fixture change.
  • Static sensor accuracy cannot compensate for communication delay, poor control gain or thermally shifted zero.
  • Continuous trials should inject misalignment, missing parts, loose fixtures and communication loss, then remeasure the recovered first part.

03 · Ti5, JAKA and Flexiv require different enquiry routes

Joint modules, collaborative robots and adaptive robots are not one item.

Ti5 publicly sits near joint modules, JAKA supplies a collaborative-robot node, and Flexiv material emphasises force control and adaptive applications. Their roles may complement but cannot prove one another. Ti5 modules answer a component question, JAKA cobots a complete-machine question, and Flexiv adaptive applications also include process integration. They can share one line while retaining different contract boundaries, warranty objects and site responsibilities.

A robot-joint purchase focuses on torque, backlash, life, and mechanical, electrical, and software interfaces; a complete robot adds controller, safety circuit, teaching, and service. When the project also requires adaptive processing, customer trajectory, force-control, and quality data enter integration and expand responsibility. The three purchase scopes cannot share one simple parameter sheet, and intellectual-property, data-use, and site-commissioning boundaries need agreement before quotation.

Each company should receive a role-specific requirement, followed by a system comparison using common workpieces, cycle and downtime criteria. Each requirement should define its own deliverable before system testing uses common workpieces. If cycle time fails, the review must separate joint thermal limits, robot path planning and process parameters rather than blame the last integrator on site. The system comparison retains configuration lists from all three parties.

  • Ti5 joint modules, JAKA robots and Flexiv adaptive solutions create three contract and warranty objects.
  • A joint exposes interfaces, a robot adds safety and service, and an adaptive solution adds process-data rights.
  • Cycle-time diagnosis assigns joint thermal protection, trajectory generation and process tuning to their responsible parties.

04 · Different roles behind more than 200 firms

Scale needs its date, firm scope and component boundary.

The Minhang plan published in February 2026 reports more than 200 related firms and a then-current scale above RMB 10 billion, while placing RMB 25 billion separately as a 2030 target. The count may include robots, reducers, sensors, software, research platforms and application integrators. Industry scale also changes with its statistical boundary, so the figures describe ecosystem size rather than supply of one component category.

Robot makers, core components, software and integration services may all enter the related-firm count. The number does not state how many suppliers offer purchasable joints or sensors. Purchasable suppliers are constrained by production status, specification range, quality systems and lead time. Some remain in research or pilot work and others sell only complete solutions; counting them all as joint makers overstates competition. Prototype counts do not establish production capacity.

A supplier longlist should assign joint, sensing, control, robot or integration roles, then check address and product pages. A robot application must not be turned into evidence that a component is sold separately. The longlist can mark products as sold separately, supplied with a robot or available only through integration, and record sample and production sites. Core-component screening then checks continuity, change notice and substitute-material control.

  • More than 200 firms include robots, components, software, platforms and integration, not a count of joint suppliers.
  • Purchasable supply also depends on production status, specification range, quality systems and lead time; prototypes are not capacity.
  • Screening also records prototype and production sites, change notification and substitute-material control rather than only a product name.

05 · Embodied chips must resolve into interfaces and power

Compute labels matter only inside the control chain and thermal design.

The district plan lists embodied-intelligence chips as a component direction, and the municipal interpretation discusses training grounds and data. The policy does not say that a particular chip is frozen for volume robots in Minhang. An embodied-intelligence chip may handle sensor preprocessing, motion control or model inference, with different real-time and safety demands. The industry direction does not define package, interfaces, toolchain or production status and cannot replace robot validation.

Robot control combines perception, trajectory, safety and communications. Memory, interfaces and the software stack also affect compute utilisation. Peak compute comparisons outside a robot power budget are misleading. Peak compute may be limited by memory bandwidth, data movement or thermal throttling, causing missed control cycles. A robot also reserves deterministic resources for safety, so model throughput must be assessed with worst-case latency, power and cooling.

Technical engagement begins with sensor count, buses, control cycle, model size, power ceiling and safety partition, followed by board-level and robot stress tests. Board testing first covers supply variation, saturated interfaces, temperature and prolonged inference. The same software then enters the robot to measure jitter and recovery. A model or sensor-count change requires rerunning stress tests with version differences retained. Fault injection covers interface loss and thermal throttling.

  • An embodied chip may preprocess sensing, control motion or run inference, each with different real-time and safety demands.
  • Peak compute can still miss control cycles when memory bandwidth, data movement or thermal throttling intervene.
  • Board stress and robot jitter or recovery tests should share one software version and repeat after model or sensor changes.

06 · How robot and component makers should talk

Interfaces, responsibility and failure reproduction are more concrete than ecosystem language.

The spatial paper places robot or system actors such as JAKA and Flexiv beside the component cluster, indicating local integration settings without proving fixed procurement. Geographic concentration shortens integration distance but does not create procurement. A robot maker may develop joints or controllers internally or choose different suppliers by model; proximity indicates convenience, not a fixed supply arrangement.

A joint failure can arise from the motor, reducer, encoder, control parameters or mechanical installation. Unclear interface responsibility sends the problem between parties. Failure attribution starts by freezing mechanical installation, harness, firmware and control parameters. Without a shared interface baseline, the component maker may blame assembly and the robot maker the joint, extending recovery through repeated disputes.

The prototype phase should establish a signal dictionary, mechanical datums, log format and failure-reproduction procedure, with one party assigned to retain raw data. The signal dictionary needs units, ranges, refresh rates and fault codes; logs also record clock synchronisation and configuration checksums. Reproduction starts from the original motion, load and environment so all parties can recreate a fault rather than exchange screenshots. Raw logs must not be reduced to selected alarm excerpts.

  • Geographic concentration shortens integration distance but does not prove fixed procurement between robot and component makers.
  • Joint failure attribution first freezes installation, harness, firmware and control settings or responsibility will drift between parties.
  • Signal definitions, clock synchronisation, configuration checksums and raw logs should reproduce a fault under the same load.

07 · Signed projects still pass through pilots

Investment, planned capacity and construction period are not current delivery evidence.

A WAIC 2025 page records the signed scope of Minhang projects including Ti5, and a spatial paper proposes park arrangements. Signing and promotion are later actions. A signing records intent or a project start, while a park arrangement prepares space; neither creates conforming output. Facility preparation, line installation and staff training follow separate schedules, and any one can change the production date.

Moving a robot component from prototype to stable volume requires tooling, life tests, supply substitutions and robot integration. A project value does not establish completion of those steps. Scaling from prototype to volume requires consistent tooling, substitute-part control, efficient calibration and repair processes. A life test covers one version; later material or firmware changes can reopen risk, and investment value does not replace this work.

Signing, site preparation, equipment arrival, trials and customer validation each use their own date. A stage without a later progress record remains pending confirmation. Each milestone needs an observable result: equipment arrival an installation list, trials a lot and inspection, and customer validation defined duty and conclusions. Unreached steps remain pending so a later update moves them accurately. A critical-part substitution requires repeating boundary duty.

  • Signing and park arrangements are starting points; delays in facilities, equipment or training move the trial date.
  • Moving from prototype to volume requires consistent tooling, substitute-part control, calibration efficiency and repair processes.
  • Every milestone needs an observable result, and a critical component or firmware change reopens its boundary tests.

08 · Applications need stable-cycle acceptance

Compliant assembly, handling and inspection have different failure modes.

Training infrastructure can collect motion data and check stability, while a company case shows how one robot ran with a particular workpiece and cycle; neither proves replication across factories. Fixtures, worker paths, safeguarding, and the site network all change when a solution moves to another line. The new plant repeats risk assessment, tooling adaptation, and sustained operation because success in a demonstration environment is not production release.

Handling focuses on gripping and cycle, insertion on contact force and jamming, and vision inspection on misses and false calls. One successful demonstration cannot cover all three. Handling tracks dropped parts, collisions and empty picks; insertion counts jams and part damage; vision inspection calculates misses by defect type. Their downtime consequences also differ, so one success rate averages away the important distinctions. Each failure class needs its own denominator and downtime record.

Acceptance uses representative workpieces, continuous run time, recovery counts and changeover time, while retaining failed samples for diagnosis. Acceptance should include shift changes, replenishment, changeovers and restart after planned stops, not one ideal run. Paired failed and normal samples let suppliers investigate sensing, control and mechanical causes and close corrective action. Corrective items are retested in the next continuous run.

  • A training ground or individual case does not establish safety, fixture or network fitness at another factory.
  • Handling, insertion and vision inspection separately count drops, jams and misses rather than one averaged success rate.
  • Acceptance should span shift changes, replenishment, changeovers and restart, using failed samples to test the next correction.

Sources and reading notes

An integrated joint should be checked for torque, backlash and temperature rise under a defined load spectrum, mounting direction, ambient temperature and cycle count. A prototype signing does not establish continuous-duty performance.

  • Shanghai Minhang embodied-intelligence components — Related firms at plan publication: 200+.
  • Shanghai Minhang embodied-intelligence components — Industry scale stated at publication: more than RMB 10 billion.
  • Shanghai Minhang embodied-intelligence components — 2030 target scale: RMB 25 billion.
  • Shanghai Minhang embodied-intelligence components — Core component directions: 4 categories.

Related companies

These companies have a locally relevant industry role supported by public information. Order is not a ranking, inclusion does not imply authorization, partnership or endorsement, and Hello China does not participate in or guarantee transactions.

A company may request a free correction or removal through the formal channel if its record is inaccurate or it does not wish to be shown. Do not send business licences, authorization letters or other sensitive files through insecure channels.

Sources

Use the original publishers to check dates, scope and definitions; public material is not a transaction guarantee.