How to Monitor an Aggregate Conveying System

Back to Blog

Bring the Belt Protection Devices Into View

Most aggregate conveyors already carry protection devices; the monitoring job is to make their state and their trips visible and trendable rather than just wired to stop the belt. Pull-cord emergency stops line the walkway so anyone can stop the belt, and monitoring which pull-cord tripped tells the crew where the problem is instead of sending them to walk the whole line; the device is explained in the conveyor pull-cord switch guide. Belt-drift switches detect a belt wandering off center before it grinds against the structure, and trending drift trips reveals a tracking problem developing over days, per the belt drift switch guide.

Two more devices protect against the failures that destroy belts and bury chutes. A belt-rip detector catches a longitudinal tear starting at a transfer point before it runs the length of the belt, as covered in the belt rip detector guide, and blocked-chute or plugged-chute detection stops the feed before material backs up and buries the transfer. Monitoring all of these together, with each trip tagged to a location, turns a line of independent switches into a system where a stop tells you what happened and where, not merely that the belt stopped.

Watch Idlers and Bearings for Heat and Failure

Idler rollers support the belt every few feet, and a seized idler is both a common failure and a genuine fire risk when a stalled roller heats against a moving belt full of combustible dust. Monitoring idler and pulley bearing temperature at the critical rollers catches a bearing heating up before it seizes or ignites, which is the whole point of the dedicated hardware described in the idler bearing temperature monitor guide. On long lines with many idlers, focus the instrumentation on the drive, tail, and bend pulleys and any known trouble spots rather than every roller.

Bearing temperature is a leading indicator, so trend it rather than only alarming on a threshold. A pulley bearing that runs a little warmer each week is telling you it is wearing out, and catching that trend schedules a bearing change on a planned outage instead of a belt fire on a night shift. The same condition-monitoring logic that applies to any rotating machine, covered in condition monitoring, applies here: the trend, not the single reading, is where the value is.

Trend the Drive and the Material Flow

The conveyor drive tells you how hard the belt is working. Monitor drive motor current or load and belt speed, because motor load tracks the material load on the belt and the mechanical resistance of the system, so a rising trend at constant feed points to a developing drag - a stiff bearing, misalignment, or material buildup - long before it trips. A drive that stalls or slips on start is a separate signature worth catching, and where the belt runs on a variable-frequency drive or a soft starter, that equipment's own faults are part of the monitored picture.

Material flow closes the loop. A belt scale or a simple material-present sensor tells you whether the belt is loaded, empty, or overloaded, which distinguishes a real process condition from an equipment fault: a drive current drop is fine if the belt has simply run out of feed, and alarming if the belt is loaded but the current fell because of slip. Tracking flow also protects downstream equipment from being fed when it is not ready and upstream from feeding into a stopped belt, which is the coordination that keeps a transfer chain from burying itself.

Verifying the System View and Common Mistakes

Prove the monitoring by testing the protection path and confirming the trends read true. Trip a pull-cord and a drift switch on a de-energized, locked-out belt per site procedure and confirm the event annunciates with the correct location, because a protection device whose trip does not reach the monitoring is worse than useless - it looks covered and is not. Walk the bearing-temperature points against a handheld reference so a monitored idler that reads cold when it is actually warm is caught before it matters.

The recurring mistakes: treating the protection switches as fire-and-forget wiring so nobody knows a drift switch has failed until a belt has already wandered; alarming on idler temperature thresholds without trending, so a slowly failing bearing looks fine until the day it seizes; ignoring material-flow context so every drive-current change looks like a fault; and scattering the devices across separate local panels so a stop is a mystery instead of a located, explained event. A monitoring platform such as Merobix that holds the protection trips, the bearing trends, the drive load, and the flow together is what makes the difference between a stopped belt and a diagnosable one.

Frequently Asked Questions