A consumer electronics manufacturer deploying 18 UR10e cobots across three assembly cells discovered that joint grease degradation — not programming errors or sensor faults — was responsible for 61% of their unplanned cobot downtime in year two. Their PM programme had been copied from the robot vendor's generic manual, with no adaptation for their actual cycle rates, payload, or environmental conditions. Set up your cobot PM schedule in OxMaint to get cycle-count-based maintenance that fits how your cobots actually run, or book a demo to see how manufacturing teams are managing cobot fleets with the same rigour they apply to any other critical production asset.
Smart Factory & Industry 4.0 / Cobot Maintenance
Cobots in Manufacturing: Maintenance & Uptime Guide
Collaborative robots fail differently from industrial robots — and most PM programmes do not reflect that. This guide covers joint maintenance, gripper service, safety system verification, and the cycle-count logic that keeps cobot fleets running at maximum uptime.
Where Cobot Downtime Actually Comes From
Joint grease degradation
34%
Gripper & end-effector wear
22%
Cable harness fatigue
17%
Force/torque sensor drift
14%
Controller & software faults
8%
Source: Industry field data — cobot fleet maintenance surveys, 2022–2024
Why Cobots Need a Different Maintenance Approach Than Industrial Robots
Cobots are not scaled-down industrial robots — they are fundamentally different machines with different failure modes, different maintenance intervals, and different safety-critical systems that require verification. Applying a standard industrial robot PM programme to a cobot fleet is one of the most common causes of premature joint failure and safety system degradation.
Factor
Industrial Robot
Collaborative Robot
Joint design
Servo + gearbox — sealed, high-torque
Integrated joint module with built-in torque sensing — more maintenance access points
Grease type & interval
Specialist grease, 10,000–20,000 hr intervals
Joint-specific grease, 6,000–12,000 hr or cycle-count based — varies by axis
Safety-critical systems
Safety fence — perimeter protection only
Force/torque sensing, speed & separation monitoring — all require periodic verification
Cable routing
External cable tray — low flex fatigue
Internal or dress-pack routing through full range of motion — higher fatigue rate
PM trigger
Time-based (monthly/quarterly)
Cycle-count based — a robot running 3 shifts degrades 3x faster than one on 1 shift
Calibration requirement
Annual calibration — positional accuracy
Calibration + safety function re-verification after any joint service or collision event
Cobot PM Schedule: Intervals by Task and System
The following schedule reflects best-practice intervals for UR, FANUC CRX, ABB GoFa, and KUKA LBR iisy cobot families under typical manufacturing conditions. Adjust intervals down by 20–30% for high-cycle or high-payload applications.
Daily / Per Shift
Visual inspection — cable dress and routing condition
Gripper jaw and finger wear check
End-effector fastener torque check (if removable tooling)
Controller status light and fault log review
Collision detection sensitivity test (manual push test)
Mounting base fastener visual check
Weekly / 500 Cycles
Joint cover fastener torque verification
Teach pendant cable and connector condition
Tool flange face cleanliness and seating
Vacuum cup or pneumatic gripper leak test
Safety boundary zone integrity check (floor markings, guarding)
Emergency stop function test — all buttons
Monthly / 5,000 Cycles
Force/torque sensor zero-point calibration check
Joint temperature log review for thermal anomalies
Cable harness flex points — inspect for micro-cracking
Axis backlash measurement — compare to baseline
I/O signal integrity test — all connected peripherals
Controller fan and air filter cleaning
Annual / 10,000 Cycles
Full joint grease replacement — per axis spec
Joint encoder calibration and zero-point reset
TCP (Tool Centre Point) recalibration
Safety function re-verification to ISO/TS 15066
Brake function test — each axis independently
Full positional accuracy benchmark vs commissioning data
Run Cobot PM on Cycle Counts, Not the Calendar
OxMaint triggers cobot maintenance work orders based on actual cycle data from your robot controllers — so a cobot running three shifts gets serviced three times as often as one running one shift. Set up your fleet in minutes.
Joint Maintenance Deep Dive: The Most Common Cause of Premature Cobot Failure
Joint grease degradation is responsible for the largest share of cobot downtime, and it is almost entirely preventable with cycle-count-triggered maintenance. Here is what drives grease life and what to do about it.
Grease life is not time-based — it is work-based
Grease degrades based on the number of joint oscillations, not hours on the clock. A cobot running 24/7 at high cycle rates will need grease replacement in 12–18 months. The same robot at low cycle rates may go 4–5 years. Interval-based PM schedules consistently under-service high-utilisation robots and over-service low-utilisation ones.
Axis 1 and Axis 6 fail first — and for different reasons
Axis 1 (base rotation) carries the full arm weight through every cycle — high grease consumption, first to show backlash. Axis 6 (wrist) moves fastest and experiences the most oscillation cycles per task — grease shear degradation is the primary failure mode. Both require shorter service intervals than middle joints.
Using the wrong grease causes more damage than no grease
Every cobot joint specifies a grease type — Mobilgrease XHP 222, Molykote, Nachi Temp-A-Lube, and others — that is matched to the bearing and seal materials in that joint. Cross-contaminating with the wrong grease causes seal swelling, bearing corrosion, and joint failure that voids manufacturer warranties.
Grease Interval by Joint and Utilisation
| Joint |
Low Utilisation
(<500 cycles/day) |
Medium Utilisation
(500–2,000/day) |
High Utilisation
(>2,000/day) |
| Axis 1 (Base) |
36 months |
18 months |
10 months |
| Axis 2 (Shoulder) |
48 months |
24 months |
14 months |
| Axis 3 (Elbow) |
48 months |
24 months |
14 months |
| Axis 4 (Wrist 1) |
36 months |
20 months |
12 months |
| Axis 5 (Wrist 2) |
30 months |
16 months |
10 months |
| Axis 6 (Tool Flange) |
24 months |
12 months |
7 months |
Intervals are indicative for 6-axis cobots at nominal payload. Verify against manufacturer specification for your model and application.
Safety System Verification: What Needs Checking and When
The safety functions that make a cobot safe to operate alongside humans are not self-certifying — they degrade over time and must be periodically verified against the original risk assessment and ISO/TS 15066 parameters. Failing to verify is not just a maintenance gap; it is a regulatory compliance gap.
Verify after every collision event
Force and Power Limiting
Verify that force and power limits match the approved risk assessment values. A collision event can shift sensor zero-points. Test using calibrated force gauge against each axis and speed setting defined in the safety configuration.
Verify after any joint service
Speed & Separation Monitoring
If your application uses speed and separation monitoring (SSM) — dynamically adjusting cobot speed based on operator proximity — verify that speed reduction triggers at the correct distances after any joint or controller work that could affect motion profiles.
Verify every 6 months
Joint Torque Sensing Accuracy
Apply known loads to the tool flange at defined joint positions and confirm torque sensor readings are within ±5% of expected values. Drift beyond this threshold requires recalibration before the robot returns to collaborative operation.
Verify every 6 months
Safety-Rated Monitored Stop
Test that the safety-rated monitored stop engages within specification when the operator enters the defined zone. Response time and stopping distance must be within the values used in the original CE/risk assessment documentation.
Verify annually
Full ISO/TS 15066 Re-verification
Complete re-verification of all safety functions against the risk assessment — particularly if the application, tooling, payload, or operating environment has changed since commissioning. Document results for CE compliance records.
Verify after any software update
Safety PLC and Firmware
Controller firmware updates can reset or alter safety parameter configurations. After any software update, run the complete safety function test suite before returning the cobot to collaborative operation — even if the vendor's release notes do not indicate safety changes.
Frequently Asked Questions
How does OxMaint track cobot cycle counts for PM triggering?
OxMaint connects to cobot controllers via OPC-UA, REST API, or direct PLC integration to read cumulative cycle counters in real time. PM work orders are automatically triggered when cycle count thresholds are reached — not on a fixed calendar schedule.
Book a demo to see the cycle-count PM workflow for your cobot brand.
Which cobot brands does OxMaint support for maintenance tracking?
OxMaint supports maintenance management for all major cobot platforms including Universal Robots (UR3, UR5, UR10, UR16, UR20), FANUC CRX series, ABB GoFa and YuMi, KUKA LBR iisy, and Techman Robot. For brands with OPC-UA or REST API interfaces, integration is typically straightforward.
Start a free trial and connect your first cobot in minutes.
Does cobot joint maintenance require the robot to be taken offline?
Grease replacement and encoder calibration require the robot to be de-energised and locked out — plan for 2–4 hours per robot for a full annual service. Daily and weekly checks can be completed during scheduled breaks without removing the robot from production. OxMaint schedules cobot downtime windows automatically against your production calendar.
What happens to safety certification after cobot joint maintenance?
Any maintenance that involves joint disassembly, force/torque sensor contact, or controller work requires a safety function re-verification before returning the cobot to collaborative operation. OxMaint generates a post-maintenance safety checklist automatically and requires sign-off before the work order is closed.
Book a demo to see the safety verification workflow.
How do we build a cobot maintenance programme if we have no baseline data?
Start with the manufacturer's recommended intervals and adjust based on your actual cycle rates and application conditions. OxMaint includes cobot PM templates for UR, FANUC, and ABB platforms that you can deploy immediately, then refine as you accumulate your own maintenance history and failure data.
Start a free trial to access the template library.
Manage Your Cobot Fleet Like the Critical Production Assets They Are
OxMaint gives cobot fleet managers cycle-count-based PM scheduling, safety verification checklists, joint service tracking, and real-time downtime visibility — all in one platform built for manufacturing maintenance teams.
