Reading the Record: Using Bosch Drive Fault History to Schedule Maintenance
Photo: Internet Archive Book Images, No restrictions, via Wikimedia Commons
The reset button is a powerful silencer. A drive trips, the fault is cleared, the line restarts and the event disappears into the shift log. Yet the drive has usually recorded more than the immediate cause. Timestamps, fault codes, operating hours, DC-bus values, temperatures and encoder status are captured in the diagnostic memory. Used properly, that record is a maintenance planning tool rather than a post-mortem.
The argument for exporting fault history is straightforward: the data already exists, and the cost of collecting it is small compared with the cost of an unplanned stop. The discipline lies in deciding what to trend and in converting the trends into scheduled work.
Export before you clear
Establish a routine for exporting the drive's event log before any fault memory is cleared. The export should include the fault code, the time and date, the operating hours or production count at the event, and the drive's captured values where available. For Bosch drives, the commissioning or engineering software will typically provide an event history and diagnostic buffer. Use it to save a record that can be compared with previous exports.
Keep a baseline export after commissioning and after any significant change to the machine, motor or parameter set. Confirm that the drive clock is synchronised with the site time source; otherwise the sequence of events across drives and control systems becomes difficult to reconstruct.
Metrics that earn a place on the calendar
Not every logged value deserves a trend. The following are useful because they connect electrical and mechanical behaviour to maintenance actions.
DC-bus ripple is a slow indicator with real diagnostic value. A rising ripple trend can point to capacitor ageing, supply asymmetry or excessive single-phase loading. It should be compared at similar load and operating conditions. A step change after a supply alteration is as important as a gradual drift.
Overtemperature events are a record of cooling performance. Count them per thousand operating hours and correlate them with ambient temperature, cabinet filter condition, heatsink contamination and fan operation. In UK plants, seasonal humidity and summer ambient peaks can expose a cooling path that is marginal for much of the year.
Encoder errors deserve attention when they cluster on one axis, appear after washdown or occur at particular positions. They may indicate cable damage, connector contamination, coupling slip or an encoder that is approaching failure. A single isolated error is a data point; a cluster is a maintenance trigger.
Stall and overload occurrences should be read alongside the machine cycle. Repeated stalls at the same point may point to mechanical binding, product change, incorrect acceleration or a brake that is not releasing cleanly. Undervoltage and overvoltage events can reflect supply quality, regeneration or drive deceleration settings, and they are worth reviewing with the site electrical engineer.
From Pareto to planned work
A fault log becomes a calendar when the events are ranked. Sort by fault code, by machine and by downtime. Identify the few codes that account for most interruptions, then set site-specific triggers. The thresholds should reflect the criticality of the machine, not a generic rule from another plant.
Useful examples of triggers include: two encoder errors on the same axis within a month leading to a cable and connector inspection; a rising count of overtemperature events across successive quarters leading to heatsink cleaning, fan replacement and filter review; repeated stalls at a known cycle position leading to a mechanical alignment check; and a sustained increase in DC-bus ripple leading to a capacitor assessment. These are investigation triggers, not automatic replacement instructions. The drive data points to where to look.
Record the action taken against the trigger and verify the effect in the next export. If the overtemperature count falls after the cooling path is cleaned, the trigger was useful. If it does not, the investigation continues.
A UK operating context
UK sites often combine older infrastructure with tight production schedules. Supply quality, harmonic distortion and seasonal moisture all leave traces in drive data. A drive that trips on overvoltage during deceleration may be revealing a braking or regeneration issue rather than a supply fault. A food plant that washdowns equipment may see encoder errors that follow the cleaning routine rather than the production load. The fault history allows these patterns to be separated from the noise of daily resets.
Make the review routine
A practical rhythm is monthly export, quarterly review and an annual reliability summary. The monthly export protects the data. The quarterly review turns it into work orders. The annual summary shows whether the maintenance calendar is reducing repeat trips or merely moving them around.
Store the exports with the machine records and keep them long enough to compare seasons and maintenance intervals. Restrict access to those who need it, and avoid overwriting old exports with new ones. The value lies in the series, not in a single snapshot.
A fault log is not simply a record of what went wrong. It is a forward plan written by the machine. The maintenance team that reads it regularly can schedule work before the next reset becomes another lost shift.
