{"id":5546,"date":"2026-11-12T06:09:15","date_gmt":"2026-11-11T22:09:15","guid":{"rendered":"https:\/\/www.corvelanmag.com\/?p=5546"},"modified":"2026-10-30T13:04:05","modified_gmt":"2026-10-30T05:04:05","slug":"metal-detector-alarm-but-conveyor-not-stopping","status":"publish","type":"post","link":"https:\/\/www.corvelanmag.com\/es\/metal-detector-alarm-but-conveyor-not-stopping\/","title":{"rendered":"El detector de metales se activ\u00f3, pero el transportador no se detuvo: qu\u00e9 comprobar"},"content":{"rendered":"\n<style>\n.cv-alarm-article {color:#25282c;font-family:inherit;font-size:17px;line-height:1.75;overflow-wrap:break-word;}\n.cv-alarm-article .cv-section,.cv-alarm-article .cv-intro,.cv-alarm-article .cv-toc {box-sizing:border-box;margin:0 0 24px;padding:22px;border:1px solid #d8dce0;border-radius:16px;}\n.cv-alarm-article .cv-intro,.cv-alarm-article .cv-toc {background:#f5f6f7;}\n.cv-alarm-article .cv-section {background:#fff;border-top:4px solid #55595e;box-shadow:0 2px 8px rgba(0,0,0,.035);scroll-margin-top:110px;}\n.cv-alarm-article h2 {font-family:inherit;font-size:30px;line-height:1.3;color:#202428;margin:0 0 18px;font-weight:700;}\n.cv-alarm-article h3 {font-family:inherit;font-size:24px;line-height:1.3;color:#202428;margin:28px 0 14px;font-weight:700;}\n.cv-alarm-article p {margin:0 0 16px;}\n.cv-alarm-article p:last-child {margin-bottom:0;}\n.cv-alarm-article ul,.cv-alarm-article ol {margin:12px 0 20px;padding-left:24px;}\n.cv-alarm-article li {margin:8px 0;}\n.cv-alarm-article a {color:#30353b;text-decoration:underline;text-underline-offset:3px;overflow-wrap:anywhere;}\n.cv-alarm-article a:focus-visible,.cv-alarm-article summary:focus-visible,.cv-alarm-article .cv-table-scroll:focus-visible {outline:3px solid #30353b;outline-offset:4px;}\n.cv-alarm-article strong {font-weight:700;}\n.cv-alarm-article .cv-toc summary {cursor:pointer;font-weight:700;color:#202428;}\n.cv-alarm-article .cv-toc summary::after {content:' +';}\n.cv-alarm-article .cv-toc details[open] summary::after {content:' \u2212';}\n.cv-alarm-article .cv-toc ul {margin-bottom:0;}\n.cv-alarm-article .cv-media {display:block;float:none;clear:both;margin:20px 0;}\n.cv-alarm-article .cv-media img {display:block;float:none;max-width:100%;height:auto;margin-inline:auto;border-radius:8px;}\n.cv-alarm-article .cv-table-scroll {overflow-x:auto;margin:20px 0;}\n.cv-alarm-article table {border-collapse:collapse;width:100%;min-width:600px;font-size:inherit;line-height:1.6;}\n.cv-alarm-article th,.cv-alarm-article td {border:1px solid #d8dce0;padding:12px;vertical-align:top;text-align:left;}\n.cv-alarm-article th {background:#f0f1f2;color:#202428;font-weight:700;}\n.cv-alarm-article tbody tr:nth-child(even) {background:#fafafa;}\n.cv-alarm-article .cv-button {display:inline-block;box-sizing:border-box;background:#30353b;color:#fff;padding:12px 18px;border-radius:8px;text-decoration:none;line-height:1.5;font-weight:700;}\n.cv-alarm-article #faq h3 {padding-top:20px;border-top:1px solid #d8dce0;}\n@media (max-width:767px) {\n .cv-alarm-article {font-size:16px;}\n .cv-alarm-article .cv-section,.cv-alarm-article .cv-intro,.cv-alarm-article .cv-toc {padding:18px;margin-bottom:18px;border-radius:12px;}\n .cv-alarm-article .cv-section {border-top-width:3px;}\n .cv-alarm-article h2 {font-size:24px;}\n .cv-alarm-article h3 {font-size:20px;}\n .cv-alarm-article th,.cv-alarm-article td {padding:10px;}\n}\n<\/style>\n<article class=\"cv-alarm-article\" lang=\"en\"><div class=\"cv-intro\"><p><strong>If your metal detector alarms but the conveyor is not stopping, first check whether the detection event produces a stop command.<\/strong> Then follow that command through the detector output, the conveyor controls, and the drive. A working alarm light does not prove that the belt-stop circuit has operated.<\/p>\n<p>Separate two symptoms before changing anything: a belt that keeps running at normal speed, and a belt that receives a stop command but travels too far before it stops. They need different checks. Increasing detector sensitivity will not repair a missing control signal or shorten mechanical stopping travel.<\/p>\n<\/div><nav aria-label=\"Article contents\" class=\"cv-toc\"><details open=\"\"><summary>On this page<\/summary><ul><li><a href=\"#first-check\">What should you check first when the detector alarms but the belt keeps moving?<\/a><\/li><li><a href=\"#detector-output\">Why can the detector alarm without switching its stop output?<\/a><\/li><li><a href=\"#plc-stop-logic\">What if the detector output changes but the PLC does not stop the conveyor?<\/a><\/li><li><a href=\"#drive-response\">What if the stop command is present but the belt keeps traveling?<\/a><\/li><li><a href=\"#stopping-distance\">How do you check whether the conveyor stops before the metal reaches the machine?<\/a><\/li><li><a href=\"#repair-test\">How do you prove the repair works before returning to production?<\/a><\/li><li><a href=\"#next-steps\">Fix the failed link before replacing the detector<\/a><\/li><li><a href=\"#faq\">Frequently asked questions<\/a><\/li><\/ul><\/details><\/nav><section class=\"cv-section\" id=\"first-check\"><h2>What should you check first when the detector alarms but the belt keeps moving?<\/h2>\n<div class=\"cv-media\"><img loading=\"lazy\" src=\"https:\/\/www.corvelanmag.com\/wp-content\/uploads\/2026\/09\/coverlan-gjt-f-metal-detector-conveyor-hero.webp\" alt=\"Rectangular detector frame beside a control cabinet on an inclined conveyor\" width=\"1200\" height=\"900\" loading=\"lazy\" decoding=\"async\" style=\"display:block;max-width:100%;height:auto;object-fit:contain;\"><\/div>\n<p><strong>Start with the required line action, then find the first point where the detection event fails to produce the expected response.<\/strong> Some systems are set up to alarm or reject while the belt continues. If the agreed action is to stop the belt, trace the stop signal rather than assuming the detector is faulty.<\/p>\n<p>Use the electrical drawing and the line&#8217;s operating description to identify the intended response. Check whether the problem occurs in automatic mode, local control, maintenance mode, or every mode. Note whether it began after a controller change, maintenance work, or a settings restore.<\/p>\n<div aria-label=\"Conveyor stop symptoms and checks\" class=\"cv-table-scroll\" role=\"region\" tabindex=\"0\"><table>\n<thead>\n<tr>\n<th scope=\"col\">What you observe<\/th>\n<th scope=\"col\">What it suggests<\/th>\n<th scope=\"col\">Where to go next<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>The alarm appears and belt speed does not change<\/td>\n<td>The stop command may be missing, blocked, or ignored<\/td>\n<td>Follow the detector output and conveyor control signals<\/td>\n<\/tr>\n<tr>\n<td>The belt slows, but the metal reaches the transfer or machine<\/td>\n<td>Stopping travel or material movement may exceed the available distance<\/td>\n<td>Measure delay and loaded stopping travel<\/td>\n<\/tr>\n<tr>\n<td>The belt stops briefly, then starts again<\/td>\n<td>The event may not stay latched, or another run request may restart it<\/td>\n<td>Review event retention, reset, and start logic<\/td>\n<\/tr>\n<tr>\n<td>The response works in one operating mode only<\/td>\n<td>The control path changes with the selected mode<\/td>\n<td>Compare the mode logic and drive command source<\/td>\n<\/tr>\n<\/tbody>\n<\/table><\/div>\n<p>For the same controlled test event, record these six observations in order:<\/p>\n<ol>\n<li>The detector registers the event.<\/li>\n<li>The assigned detector output changes state.<\/li>\n<li>The receiving relay or programmable logic controller (PLC) input responds, if fitted.<\/li>\n<li>The conveyor control issues its stop command or removes run permission.<\/li>\n<li>The motor starter or variable-frequency drive (VFD) responds.<\/li>\n<li>The belt and affected material stop before the protected point.<\/li>\n<\/ol>\n<p><strong>The first missing response tells you which section to investigate.<\/strong> For example, a PLC input that changes while the run command stays active directs attention to the program and operating mode. It does not establish a detector-head fault.<\/p>\n<h3>Make the line safe before tracing the fault<\/h3>\n<p><strong>Stop normal feeding and control the affected material while the required stop function is unavailable.<\/strong> Keep people clear of the belt and downstream equipment. If immediate danger exists, use the site&#8217;s emergency stopping procedure.<\/p>\n<p>Operators can record external displays, timestamps, and selected modes from a safe position. Electrical measurements, cabinet access, and control changes belong to qualified electrical or controls personnel using the approved work procedure. Before touching wiring, opening guarded areas, or retrieving metal, isolate all relevant energy sources and verify isolation, including stored energy and possible upstream feed.<\/p>\n<p>A stop button or detector reset is not an energy-isolation device. <a href=\"https:\/\/www.osha.gov\/laws-regs\/regulations\/standardnumber\/1910\/1910.147\" rel=\"nofollow noopener\" target=\"_blank\">OSHA&#8217;s hazardous-energy rule<\/a> makes that distinction explicitly for covered US work. Do not bridge detector contacts, force PLC inputs, or bypass a safety circuit to keep production running.<\/p>\n<\/section><section class=\"cv-section\" id=\"detector-output\"><h2>Why can the detector alarm without switching its stop output?<\/h2>\n<p><strong>The display and the stop output can have different functions or settings.<\/strong> First identify the event being displayed. Then check whether the output assigned to conveyor stopping is enabled and actually changes state.<\/p>\n<h3>Is the displayed event actually a metal detection?<\/h3>\n<p><strong>Read the event text and fault status together; a lit indicator may represent a fault or test state rather than a normal metal event.<\/strong> Keep the exact message or code before resetting it.<\/p>\n<p>The <a href=\"https:\/\/www.eriez.com\/Documents\/Literature\/IOMs\/Metal-Detection\/MM-247-Eriez-MA3500-QM2-Metal-Detector-IOM.pdf\" rel=\"nofollow noopener\" target=\"_blank\">Eriez Metalarm Series 3500 QM2 manual<\/a>, MM-247C, explains that a coil fault also illuminates its Detect light. The same manual describes a Relay switch with OFF, ON, and LATCH positions. In OFF, the detection indicators can operate without the output relay operating; LATCH retains the response until reset. These are useful examples of why a lamp and a relay must be checked separately. The switch names and behavior apply to that controller.<\/p>\n<p>For another detector, use its event list and output settings. Identify any output-disable, test, inhibit, or product-specific setting that affects the required action. Record the approved setting before changing it, so an unrelated setting is not lost during troubleshooting.<\/p>\n<h3>Is the correct output enabled and able to change state?<\/h3>\n<p><strong>Have the technician verify the assigned output at the actual interface, then compare it with the electrical drawing.<\/strong> A relay click or output LED alone does not establish that the receiving circuit sees the required contact change.<\/p>\n<p>For a relay output, the drawing should identify common (COM), normally open (NO), and normally closed (NC) contacts, where provided. <a href=\"https:\/\/www.ia.omron.com\/support\/guide\/36\/explanation_of_terms.html\" rel=\"nofollow noopener\" target=\"_blank\">NO and NC<\/a> describe the relay&#8217;s unactuated condition. They do not, by themselves, tell you which circuit state means \u201chealthy,\u201d \u201cmetal detected,\u201d or \u201cstop.\u201d A relay may be energized during normal running and drop out on an event.<\/p>\n<p>Build a small state record from the supplied drawing: expected output state during normal running, detection, detector fault, and loss of detector power. Compare the observed states with those expectations. This reveals wrong contact selection or inverted logic more reliably than swapping NO and NC connections by trial.<\/p>\n<p>A <a href=\"https:\/\/www.se.com\/uk\/en\/faqs\/FA236344\/\" rel=\"nofollow noopener\" target=\"_blank\">dry contact<\/a> switches a separate circuit; it does not supply that circuit&#8217;s operating voltage. If the contact changes correctly but the receiving device does not respond, investigate its control supply, wiring, common connection, and interface type next. A transistor output needs its own matching input and wiring arrangement instead.<\/p>\n<p>If the output should change but does not, investigate its configuration and output hardware. If an interface relay is fitted, check its coil and contacts as separate points. Use the supplied ratings and load details when deciding whether an interface relay is needed; do not connect a conveyor motor directly to a detector signal output.<\/p>\n<\/section><section class=\"cv-section\" id=\"plc-stop-logic\"><h2>What if the detector output changes but the PLC does not stop the conveyor?<\/h2>\n<p><strong>Check whether the event reaches the correct PLC input, then whether the program uses it to stop the conveyor in the selected mode.<\/strong> An alarm shown on the operator screen may be connected to a different tag from the one used in the motor control logic.<\/p>\n<h3>Does the event reach the correct PLC input?<\/h3>\n<p><strong>If the detector output changes but the corresponding PLC input does not, focus on the interface between them.<\/strong> Match the drawing&#8217;s wire number and input channel to the installed hardware before changing the program.<\/p>\n<p>The technician should compare the output type, input type, required control voltage, common connection, and any intermediate relay. A correct contact change at the detector does not rule out a broken conductor, missing control supply, or incorrect input wiring farther along the circuit.<\/p>\n<p>If the event is intermittent, record its duration as well as its state. A short pulse can disappear before a PLC samples it, or be removed by an input filter. A slowly refreshed operator screen can also miss a brief change that the controller did receive. Use a suitable PLC trace or properly rated test equipment under the electrical work procedure, rather than relying on a person watching the screen.<\/p>\n<p><a href=\"https:\/\/docs.tia.siemens.cloud\/r\/simatic_s7_1200_manual_collection_eses_20\/device-configuration\/configuring-the-operation-of-the-cpu\/pulse-catch\" rel=\"nofollow noopener\" target=\"_blank\">Siemens&#8217; S7-1200 pulse-catch documentation<\/a> explains this distinction. Pulse catch can retain short events for the next input update, but it operates after the input filter. It cannot recover an event that the filter has already removed.<\/p>\n<p>Compare the measured output pulse with the installed input&#8217;s filter, update, and program timing. Where a pulse is too short, the controls engineer can assess a supported retained output, pulse extension, or suitable input-capture method. <strong>There is no universal pulse duration or filter setting for every detector and PLC.<\/strong> A change must preserve the required response time and avoid accepting electrical noise as a valid event.<\/p>\n<h3>Does the PLC use that input to remove the run command?<\/h3>\n<p><strong>If the input is received but the conveyor run command stays active, investigate the stop logic and its conditions.<\/strong> Start at the received input and follow it to the motor command during the same event.<\/p>\n<p>Look for the specific condition that blocks the response: a maintenance bypass, alarm-only selection, wrong equipment tag, disabled interlock, local\/remote selection, or a reset that clears the event too early. Compare automatic and manual modes if the symptom changes between them. A mode-dependent failure is a reason to examine those different paths, rather than replace an output that already works.<\/p>\n<p>Also compare the PLC command with the drive&#8217;s active command source. A VFD running from its local keypad may not be using the PLC run request that the program just removed. Conversely, the PLC may send a stop while a separate maintained run request causes motion to resume after the event clears.<\/p>\n<p>Keep a time-aligned record of input received, stop request, drive response, and any new start request. If the input and stop logic are correct but the physical output or drive command is wrong, continue downstream to that interface. Repair the first demonstrated mismatch, then repeat the complete event. Do not use forced PLC states as a substitute for proving the real detector path.<\/p>\n<\/section><section class=\"cv-section\" id=\"drive-response\"><h2>What if the stop command is present but the belt keeps traveling?<\/h2>\n<p><strong>Find out whether the drive has accepted the command and whether the belt is slowing, coasting, or still being driven.<\/strong> A stop request in the PLC and a stopped conveyor are two different observations.<\/p>\n<p>For a VFD-controlled conveyor, compare the active control source, stop status, output frequency, and available speed feedback during the event. For a starter-controlled motor, the technician should verify the starter&#8217;s actual response and feedback. If the stop command changes but the starter remains closed, investigate its control path and hardware; do not infer contact position from a PLC screen alone.<\/p>\n<p><a href=\"https:\/\/literature.rockwellautomation.com\/idc\/groups\/literature\/documents\/rm\/pflex-rm002_-en-e.pdf\" rel=\"nofollow noopener\" target=\"_blank\">Rockwell&#8217;s PowerFlex 700S reference manual<\/a>, in its Start\/Stop Modes section, distinguishes coast and ramp stopping. A coast stop removes drive control and lets the load lose its stored motion. A ramp stop reduces the commanded motor speed while the drive retains control. This explains why a correctly received command can still be followed by substantial conveyor travel.<\/p>\n<p>If the drive accepts the stop but stopping is too slow, investigate the configured stop mode, deceleration behavior, load, and braking arrangement. Record any drive fault during deceleration. Shortening the programmed ramp without checking the drive and braking capacity can create a new fault without delivering the intended stop.<\/p>\n<p><strong>Measure the belt and material movement, not just a \u201cStopped\u201d message.<\/strong> An inclined conveyor, a loaded belt, or material sliding in a chute may continue moving differently from the motor&#8217;s reported speed. Where motion persists after the motor stops, investigate that mechanical or material movement before changing detector settings.<\/p>\n<p>A long stopping distance may need an earlier detection position, an engineered change to the drive or braking system, or a different removal arrangement. Choose the change from the measured cause. Keep the line&#8217;s personnel-safety functions separate from an ordinary metal-detection process signal.<\/p>\n<\/section><section class=\"cv-section\" id=\"stopping-distance\"><h2>How do you check whether the conveyor stops before the metal reaches the machine?<\/h2>\n<p><strong>Compare travel from the detection event to complete stopping with the actual distance to the protected point.<\/strong> Include control delay and movement after the stop command, then allow for material movement and variation found during testing.<\/p>\n<p>First mark the relevant locations on the conveyor drawing: the point where the target produces the detection event, and the transfer or machine entry it must not reach. Use distance along the material path, rather than a straight-line distance across the floor. Arrange controlled commissioning tests with downstream recovery, so a test target cannot enter an operating crusher or mill.<\/p>\n<p>You need three inputs:<\/p>\n<ul>\n<li><strong>Belt speed, v, in meters per second:<\/strong> measure the actual speed or use a verified belt-speed signal. A VFD frequency display alone is not a belt-speed measurement.<\/li>\n<li><strong>Control delay, t, in seconds:<\/strong> time from the detection event to the defined stop command reaching the drive or starter. Include configured delays and the intervening controls.<\/li>\n<li><strong>Travel after that command, d, in meters:<\/strong> measure actual belt travel to standstill under the relevant load and operating condition.<\/li>\n<\/ul>\n<p>If speed remains approximately steady during the control delay:<\/p>\n<p><strong>Travel from detection to standstill = v \u00d7 t + d.<\/strong><\/p>\n<p>For example, suppose a loaded conveyor runs at <strong>1.2 m\/s<\/strong>. Its control delay is <strong>0.25 s<\/strong>, and it travels <strong>2.1 m<\/strong> after the stop command. The total is:<\/p>\n<p><strong>1.2 \u00d7 0.25 + 2.1 = 2.4 m.<\/strong><\/p>\n<p>If only <strong>2.2 m<\/strong> separates the detection point from the protected transfer, this example fails to retain the target upstream. Investigate an earlier detection position or an improved stopping arrangement before accepting the line response.<\/p>\n<p>If the delay increases to <strong>0.65 s<\/strong> while speed and after-command travel remain the same, total travel becomes <strong>2.88 m<\/strong>. The extra <strong>0.48 m<\/strong> comes from control delay, which points the investigation toward timing. If the delay is already small but after-command travel dominates, changing an alarm timer will offer little improvement.<\/p>\n<p>These are assumed inputs to show the method. For your line, repeat measurements at the relevant speeds and loads, including the condition that produces the longest travel. Faster running also requires a fresh stopping measurement; do not assume that after-command travel stays constant when speed changes.<\/p>\n<p><strong>If you measure the complete event-to-standstill travel directly, do not add the control delay again.<\/strong> Where speed varies during the delay, direct travel measurement is preferable to multiplying by one nominal speed. Include any target sliding, rolling, or continued chute movement when deciding whether the metal remains clear of the protected point. Set the final allowance from the line&#8217;s measured variation and protection requirements.<\/p>\n<\/section><section class=\"cv-section\" id=\"repair-test\"><h2>How do you prove the repair works before returning to production?<\/h2>\n<p><strong>Repeat a controlled detection event through the complete line and prove both the stop response and the target&#8217;s final location.<\/strong> A relay that switches on a workbench, or a detector that finds metal on an empty belt, does not finish this check.<\/p>\n<p>Use the agreed commissioning procedure, with a recoverable target and downstream containment. Keep people outside the hazard area while the line moves. Account for each target after the test so the exercise does not introduce loose metal into production.<\/p>\n<ol>\n<li><strong>Define the target and condition.<\/strong> Record metal type, dimensions, position in the load, belt speed, material depth, operating mode, and the required line action. Use a target representative of the hazard the detector was selected to find.<\/li>\n<li><strong>Record the complete event.<\/strong> Capture the detector indication, physical output, receiving input, stop request, drive or starter response, and belt standstill. A common timebase or a coordinated recording helps distinguish a lost signal from a late response.<\/li>\n<li><strong>Prove where the target ends up.<\/strong> Verify that the affected material remains upstream of the protected point, or that the specified reject arrangement captures it. Retrieve the target only after the required isolation.<\/li>\n<li><strong>Exercise the relevant variations.<\/strong> Include the operating modes, loads, speeds, and successive events that occur on this line. For successive targets, verify that the stop or reject response still controls the affected material throughout recovery and reset.<\/li>\n<li><strong>Check fault and restart behavior.<\/strong> Through the approved commissioning method, demonstrate the specified response to detector fault or power loss. Verify what happens when the event clears, the detector is reset, and a new start is requested. Include upstream feeding and downstream equipment in the sequence where needed.<\/li>\n<\/ol>\n<p>A successful result ties the recorded event to an effective stop or removal action, target recovery, and the specified restart sequence. If a signal disappears between two observation points, return to that interface. If every signal works but the target passes the protected point, return to the stopping-distance or reject-timing problem.<\/p>\n<h3>What if the alarm itself is false or unstable?<\/h3>\n<p><strong>Investigate the unwanted detections and the missing stop response as separate problems.<\/strong> Do not disable a required stop merely because alarms are inconvenient.<\/p>\n<p>The <a href=\"https:\/\/adsdetection.com\/wp-content\/uploads\/2024\/01\/Metal-Detector-Troubleshooting-Guide.pdf\" rel=\"nofollow noopener\" target=\"_blank\">Advanced Detection Systems troubleshooting guide<\/a> uses a useful sequence: compare the detector with the conveyor stopped, with the empty belt moving, and with product moving. Under controlled conditions, those comparisons can help separate electrical interference, belt or nearby-metal effects, and changes caused by the material.<\/p>\n<p>Record whether events follow a belt splice, another machine cycle, vibration, or a material change. Address the demonstrated source, then repeat the required target test and the complete line response. Reducing sensitivity until alarms disappear can also remove the ability to find the target that matters.<\/p>\n<\/section><section class=\"cv-section\" id=\"next-steps\"><h2>Fix the failed link before replacing the detector<\/h2>\n<p><strong>When a metal detector alarms but the conveyor does not stop, repair the first demonstrated failure between detection and controlled material handling.<\/strong> Keep the existing detector if it finds the required target and its output works. A wiring or program correction may be the needed change. If the controls respond correctly but the target travels too far, improve the layout or stopping arrangement instead.<\/p>\n<p>For a new or modified bulk conveyor, our <a href=\"https:\/\/www.corvelanmag.com\/product-category\/conveyor-metal-detector\/\">conveyor metal detector range<\/a> helps you compare installation arrangements. The <a href=\"https:\/\/www.corvelanmag.com\/products\/ljt-a-conveyor-metal-detector\/\">LJT-A conveyor metal detector<\/a> is a frame-style option for bulk-material belts. Its detection function and your conveyor&#8217;s required response need to be matched as part of the project; use the supplied control details for the installed unit.<\/p>\n<p>To discuss a Corvelan application, send the detector and controller nameplates, a short account of the event, the selected operating mode, and which of the six response points worked. Include belt speed, material depth, available stopping distance, and the required action. Electrical drawings, an input\/output list, and timestamped observations help identify the interface that needs attention.<\/p>\n<p>Use our contact form for the initial description. Send photos or drawings by email to sales@corvelanmag.com; the form itself is for your message and contact details.<\/p>\n<p><a class=\"cv-button\" href=\"https:\/\/www.corvelanmag.com\/contact-us\/\">Discuss Your Conveyor Detection and Stop Requirements<\/a><\/p>\n<\/section><section class=\"cv-section\" id=\"faq\"><h2>Frequently asked questions<\/h2>\n<h3>Why does the emergency stop work while the metal detector does not?<\/h3>\n<p><strong>The two events can use different control paths, so a working emergency stop does not prove that the detector&#8217;s stop signal is connected or used correctly.<\/strong> Trace the actual detection event through its assigned input and conveyor logic. Do not move an ordinary detector output into a safety circuit as a troubleshooting shortcut; any safety-related change needs the appropriate system design and validation.<\/p>\n<h3>Should resetting the metal detector restart the conveyor?<\/h3>\n<p><strong>For stop-and-retrieve operation, keep detector reset separate from the deliberate restart sequence after the metal is removed and the line is clear.<\/strong> Check for a maintained run request that becomes active again when the detector resets. Resetting an alarm must not be treated as evidence that retrieval is complete or that people have left the hazard area.<\/p>\n<h3>What should you check after replacing the controller or restoring settings?<\/h3>\n<p><strong>Compare the installed controller&#8217;s output assignment, active state, retained-event behavior, and interface settings with the approved configuration.<\/strong> Also compare the PLC input and stop logic if they changed. A restored sensitivity setting does not prove that output settings were restored. Repeat an actual detector event through to the belt response instead of accepting a settings screen alone.<\/p>\n<h3>Does passing a test piece by hand prove the stop circuit works?<\/h3>\n<p><strong>No. It may demonstrate a detection response, but it does not reproduce the moving belt&#8217;s timing, loaded stopping travel, or target recovery.<\/strong> Use the controlled complete-line test described above. Keep trial targets contained and accounted for; do not use a loose object that can reach downstream machinery.<\/p>\n<h3>What if the belt stops but the feeder above it keeps running?<\/h3>\n<p><strong>The conveyor stop may work while the wider feed sequence is incomplete.<\/strong> Continued feeding can pile material onto a stopped belt, bury the target, or cause a spill. Review the feeder and conveyor sequence together, including material already falling through a chute. Have the controls team implement the required coordinated response, then test stopping and restart with that remaining material included.<\/p><\/section><\/article>\n<script type=\"application\/ld+json\">\n{\n  \"@context\": \"https:\/\/schema.org\",\n  \"@type\": \"FAQPage\",\n  \"mainEntity\": [\n    {\n      \"@type\": \"Question\",\n      \"name\": \"Why does the emergency stop work while the metal detector does not?\",\n      \"acceptedAnswer\": {\n        \"@type\": \"Answer\",\n        \"text\": \"The two events can use different control paths, so a working emergency stop does not prove that the detector's stop signal is connected or used correctly. Trace the actual detection event through its assigned input and conveyor logic. Do not move an ordinary detector output into a safety circuit as a troubleshooting shortcut; any safety-related change needs the appropriate system design and validation.\"\n      }\n    },\n    {\n      \"@type\": \"Question\",\n      \"name\": \"Should resetting the metal detector restart the conveyor?\",\n      \"acceptedAnswer\": {\n        \"@type\": \"Answer\",\n        \"text\": \"For stop-and-retrieve operation, keep detector reset separate from the deliberate restart sequence after the metal is removed and the line is clear. Check for a maintained run request that becomes active again when the detector resets. Resetting an alarm must not be treated as evidence that retrieval is complete or that people have left the hazard area.\"\n      }\n    },\n    {\n      \"@type\": \"Question\",\n      \"name\": \"What should you check after replacing the controller or restoring settings?\",\n      \"acceptedAnswer\": {\n        \"@type\": \"Answer\",\n        \"text\": \"Compare the installed controller's output assignment, active state, retained-event behavior, and interface settings with the approved configuration. Also compare the PLC input and stop logic if they changed. A restored sensitivity setting does not prove that output settings were restored. Repeat an actual detector event through to the belt response instead of accepting a settings screen alone.\"\n      }\n    },\n    {\n      \"@type\": \"Question\",\n      \"name\": \"Does passing a test piece by hand prove the stop circuit works?\",\n      \"acceptedAnswer\": {\n        \"@type\": \"Answer\",\n        \"text\": \"No. It may demonstrate a detection response, but it does not reproduce the moving belt's timing, loaded stopping travel, or target recovery. Use the controlled complete-line test described above. Keep trial targets contained and accounted for; do not use a loose object that can reach downstream machinery.\"\n      }\n    },\n    {\n      \"@type\": \"Question\",\n      \"name\": \"What if the belt stops but the feeder above it keeps running?\",\n      \"acceptedAnswer\": {\n        \"@type\": \"Answer\",\n        \"text\": \"The conveyor stop may work while the wider feed sequence is incomplete. Continued feeding can pile material onto a stopped belt, bury the target, or cause a spill. Review the feeder and conveyor sequence together, including material already falling through a chute. Have the controls team implement the required coordinated response, then test stopping and restart with that remaining material included.\"\n      }\n    }\n  ]\n}\n<\/script>\n","protected":false},"excerpt":{"rendered":"<p>If your metal detector alarms but the conveyor is not stopping, first check whether the detection event produces a stop command. Then follow that command through the detector output, the conveyor controls, and the drive. A working alarm light does not prove that the belt-stop circuit has operated. Separate two symptoms before changing anything: a [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":4213,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[1],"tags":[],"class_list":["post-5546","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-blog"],"acf":[],"_links":{"self":[{"href":"https:\/\/www.corvelanmag.com\/es\/wp-json\/wp\/v2\/posts\/5546","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.corvelanmag.com\/es\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.corvelanmag.com\/es\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.corvelanmag.com\/es\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.corvelanmag.com\/es\/wp-json\/wp\/v2\/comments?post=5546"}],"version-history":[{"count":1,"href":"https:\/\/www.corvelanmag.com\/es\/wp-json\/wp\/v2\/posts\/5546\/revisions"}],"predecessor-version":[{"id":5612,"href":"https:\/\/www.corvelanmag.com\/es\/wp-json\/wp\/v2\/posts\/5546\/revisions\/5612"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.corvelanmag.com\/es\/wp-json\/wp\/v2\/media\/4213"}],"wp:attachment":[{"href":"https:\/\/www.corvelanmag.com\/es\/wp-json\/wp\/v2\/media?parent=5546"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.corvelanmag.com\/es\/wp-json\/wp\/v2\/categories?post=5546"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.corvelanmag.com\/es\/wp-json\/wp\/v2\/tags?post=5546"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}