{"id":3787,"date":"2026-10-20T19:00:00","date_gmt":"2026-10-20T11:00:00","guid":{"rendered":"https:\/\/sayoon-dc.com\/blog\/plc-resets-when-contactor-switches\/"},"modified":"2026-11-09T00:19:04","modified_gmt":"2026-11-08T16:19:04","slug":"plc-resets-when-contactor-switches","status":"publish","type":"post","link":"https:\/\/sayoon-dc.com\/ja\/blog\/plc-resets-when-contactor-switches\/","title":{"rendered":"\u30b3\u30f3\u30bf\u30af\u30bf\u30fc\u306e\u30b9\u30a4\u30c3\u30c1\u30f3\u30b0\u6642\u306bPLC\u304c\u30ea\u30bb\u30c3\u30c8\u3055\u308c\u308b\uff1a\u8a3a\u65ad\u30ef\u30fc\u30af\u30d5\u30ed\u30fc"},"content":{"rendered":"<p>If a PLC resets when a contactor switches, first determine whether the controller actually loses power, enters a fault state, restarts its program, or merely loses communications. Then correlate that event with controller-terminal voltage, contactor commands, and the machine&#8217;s power sequence. A shared-supply voltage dip, a switching transient, a grounding or routing problem, and a programmed reset can produce similar operator reports. Do not replace the PLC or add a suppression component solely because the two events occur together. Preserve the evidence and isolate the cause under an approved electrical test procedure.<\/p>\n<h2>Define what reset means in this machine<\/h2>\n<p>Ask the operator what changed: did the power indicator go out, did the run indicator change, did an error code appear, or did only the HMI reconnect? Those observations help separate a power interruption from a controller fault, network interruption or application state change. Record the exact display and diagnostic information before clearing it. A phrase such as the PLC rebooted is a starting observation, not a confirmed mechanism.<\/p>\n<p>Check uptime, restart counters and event logs where available. Compare the controller&#8217;s time stamps with the HMI, drive, power supply and safety controller records. Document any clock differences. If the evidence shows that only the screen connection dropped, investigate that path rather than treating it as proof that the processor lost supply. Keep the original report intact while refining the technical description.<\/p>\n<h2>Identify which contactor event matters<\/h2>\n<p>Distinguish coil energization, main-contact closure, main-load startup, coil de-energization and main-contact opening. These events may be separated in time and affect different parts of the machine. A controller disturbance after a close command can arise when the load starts, rather than from the coil itself. A disturbance at release may involve the coil suppression, the load circuit, or both.<\/p>\n<p>Record the command sequence and expected response. Include auxiliary feedback, drive enable and load-current events if relevant. Avoid repeated uncontrolled operation of a machine that restarts unexpectedly. The responsible person should establish a safe test state and decide whether the load can be isolated or represented in a permitted fixture. Do not bypass a safety interlock to make the fault easier to reproduce.<\/p>\n<figure><img decoding=\"async\" src=\"https:\/\/sayoon-dc.com\/wp-content\/uploads\/2026\/05\/szj100a-d_s1-2.webp\" alt=\"SAYOON DC contactor product view\" loading=\"lazy\"><\/figure>\n<h2>Examine shared control-power demand<\/h2>\n<p>A contactor coil and PLC may share a control-power output. If the combined demand exceeds what the source can deliver in that operating state, voltage at the controller may fall or the source may enter a protection mode. Even when the source is adequate, distribution losses can affect the controller branch. Compare the source-terminal and PLC-terminal behavior during the same event.<\/p>\n<p>Use the exact coil current profile, background load and allowed simultaneous operation to review the supply. Do not infer coil demand from the main-contact current rating. Likewise, a large wattage marking on the supply does not describe its transient response or installed derating. The shared-supply sizing guide handles the capacity calculation; this diagnostic article uses those results to test whether a power event explains a specific controller restart.<\/p>\n<h2>Measure at the controller terminals<\/h2>\n<p>A steady reading at the panel supply can miss a brief disturbance at the PLC. Place the approved voltage measurement at the controller power terminals and capture the relevant event. State the measurement reference, acquisition window and instrument settings. Compare the waveform with the controller&#8217;s own documented supply and interruption requirements, not a generic limit copied from another machine.<\/p>\n<p>If source voltage remains stable while controller-terminal voltage changes, examine the path between them. Review protective devices, connectors, distribution terminals, shared returns and conductor condition. If both move together, review source loading and input conditions. Make one controlled change at a time where practical. A successful run after several simultaneous modifications does not identify which change removed the original problem.<\/p>\n<h2>Separate conducted disturbance from electromagnetic pickup<\/h2>\n<p>A disturbance can reach a control system through its power or signal conductors, or through coupling associated with the installation. Start with the approved wiring and grounding instructions for the actual equipment. Inspect power and signal routing, enclosure connections, cable shields and the placement of switching conductors. An untidy panel photograph alone cannot prove the cause, but it can identify points requiring inspection.<\/p>\n<p>Keep the measurement arrangement from becoming a source of error. Long probe loops can pick up switching fields, and an unsuitable reference can introduce an unintended connection. Tektronix&#8217;s probe guidance explains these measurement limitations. Use a suitable differential or isolated method where the circuit requires it; never remove protective earth from a bench oscilloscope to obtain a convenient reference.<\/p>\n<h2>Review the coil suppression as an exact combination<\/h2>\n<p>Confirm whether suppression is internal, external, or absent, and identify the exact type and polarity requirements. A diode, TVS, varistor or other network can affect voltage and current during release differently. A driver may already include a protection function. Obtain the contactor and driver instructions before adding another component.<\/p>\n<p>An added suppressor can change release timing, driver stress or diagnostic behavior. Therefore a controller reset disappearing after a modification does not complete the design review. Verify that the approved stop sequence and contactor response still meet the system requirements. Do not prescribe a universal suppression value or replace a documented arrangement with an improvised one during service. Retain the original and modified configurations for review.<\/p>\n<h2>Check the switched load separately<\/h2>\n<p>The main contacts may energize a motor, converter, capacitive input or another circuit with its own startup behavior. That event can influence the installation independently of the coil branch. Record the load identity, source, start sequence and protective-device behavior. Review whether the observed disturbance occurs before, at, or after the load-current change.<\/p>\n<p>A controlled test that operates the coil with the main load isolated can help distinguish paths only when the test owner approves that configuration. Its result must be interpreted within that limitation. A fault absent under no-load conditions may still involve a sequence or installation interaction that needs further evidence. Do not use a successful coil-only test as approval for main-contact switching duty or the complete machine.<\/p>\n<h2>Check logic and communication explanations<\/h2>\n<p>Review application commands, watchdog and fault history, startup routines, interlocks and external reset inputs. A contactor state change may trigger software that intentionally moves the controller to another state. An HMI message can also describe a process restart without a processor power cycle. Ask for the program revision and preserve diagnostics before making changes.<\/p>\n<p>For communications, identify whether the event affects one network link, one device or the entire controller. Review the network device&#8217;s power source and logs. A switch or gateway supplied from the same disturbed branch can drop the HMI while the PLC continues running. Keep the process-state and communications evidence together so the report does not combine two separate faults into one explanation.<\/p>\n<h2>Use a cause-and-evidence table<\/h2>\n<p>This qualitative table helps choose the next controlled check. It does not assign universal voltage limits, prove electromagnetic compatibility, or authorize an energized fault test. Apply the exact equipment instructions and the responsible engineer&#8217;s procedure.<\/p>\n<div class=\"sy-table-wrap\">\n<table>\n<thead>\n<tr>\n<th>Review item<\/th>\n<th>Evidence<\/th>\n<th>Decision<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>Actual controller power restart<\/td>\n<td>Uptime, restart log and terminal-voltage capture<\/td>\n<td>Review source and distribution event<\/td>\n<\/tr>\n<tr>\n<td>HMI-only connection loss<\/td>\n<td>PLC uptime and network-device logs<\/td>\n<td>Investigate communication and device supply<\/td>\n<\/tr>\n<tr>\n<td>Fault at load startup<\/td>\n<td>Command, main-load current and supply traces<\/td>\n<td>Separate load event from coil event<\/td>\n<\/tr>\n<tr>\n<td>Fault at coil release<\/td>\n<td>Exact suppression, driver and waveform<\/td>\n<td>Review approved switching combination<\/td>\n<\/tr>\n<tr>\n<td>Normal supply but changed state<\/td>\n<td>Program revision, external reset and fault history<\/td>\n<td>Review application and diagnostic logic<\/td>\n<\/tr>\n<tr>\n<td>Apparent spike changes with probing<\/td>\n<td>Reference map and repeatable setup<\/td>\n<td>Resolve measurement artifact first<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<h2>Design the verification before changing the panel<\/h2>\n<p>State the suspected cause, the predicted observation, and the measurement that could contradict it. For example, a shared-source hypothesis predicts a relevant voltage event at the controller during the allowed load combination. If a suitable capture shows no such event, continue investigating instead of declaring the source faulty because it is small.<\/p>\n<p>Keep environmental and operating conditions repeatable. Record other loads, enclosure condition, supply input, temperature and machine mode. Some intermittent issues appear only during warm restart or a particular sequence. Retain unsuccessful reproduction attempts as part of the evidence, with their actual conditions. They establish the limits of the investigation and prevent a later reader from mistaking absence of reproduction for proof of repair.<\/p>\n<h2>Verify the repair and the original safety behavior<\/h2>\n<p>After an approved correction, repeat the conditions that reproduced the problem and the relevant normal and abnormal sequences. Confirm that the controller remains in its required state and that the contactor still performs the intended stop, release and restart behavior. Preserve raw traces and diagnostics from before and after the change using compatible methods.<\/p>\n<p>If wiring, source, driver, suppression or software changed, update the controlled record and identify any further verification it triggers. A larger supply may require protection review; a suppressor may affect release; a route change may alter installation evidence. Report the actual scope checked. Do not claim complete EMC compliance or a certified safety performance from a troubleshooting exercise that did not evaluate those requirements.<\/p>\n<figure><img decoding=\"async\" src=\"https:\/\/sayoon-dc.com\/wp-content\/uploads\/2026\/05\/szj100a-d_s1-2.webp\" alt=\"SAYOON DC contactor product view\" loading=\"lazy\"><\/figure>\n<h2>Product reference and supplier handover<\/h2>\n<p>The SZJ100A-D normally open DC contactor is the real Sayoon construction reference illustrated in this article. Its unpowered images do not identify the cause of a PLC reset, specify suppression, or approve a coil option for the machine. Request the exact drawing, coil and driver information for the proposed ordering code.<\/p>\n<p>Send a concise event timeline, actual controller diagnostics, relevant voltage and current captures, circuit revision and installed component identities. State whether the problem follows coil pickup, release or main-load switching. Include the changes already tried and their results. This evidence allows a supplier to answer a focused question instead of guessing from a general report that the panel occasionally restarts.<\/p>\n<h2>Educational video<\/h2>\n<p>The Electrician U contactor introduction explains the coil and main-contact circuits. It supports the distinction between control events and load events. It does not diagnose your PLC, specify a suppressor, or replace the written test and isolation procedure.<\/p>\n<div style=\"position:relative;aspect-ratio:16\/9\"><iframe src=\"https:\/\/www.youtube-nocookie.com\/embed\/F2yL2Cs2nHc\" title=\"What is a Contactor and How Does it Work? \u2014 Electrician U\" loading=\"lazy\" allowfullscreen style=\"width:100%;height:100%;border:0\"><\/iframe><\/div>\n<p><a rel=\"noopener nofollow\" href=\"https:\/\/www.youtube.com\/watch?v=F2yL2Cs2nHc\" target=\"_blank\">Watch the Electrician U educational introduction.<\/a><\/p>\n<h2>Frequently asked questions<\/h2>\n<h3>Does a reset during contactor switching prove the coil is faulty?<\/h3>\n<p>No. Establish whether the controller lost power, entered a fault, changed program state, or lost communications, then correlate the evidence.<\/p>\n<h3>Can I diagnose the problem from a steady supply reading?<\/h3>\n<p>Not reliably. Capture the relevant event at the controller terminals with a suitable instrument and compare the correct equipment requirements.<\/p>\n<h3>Should I add a diode immediately?<\/h3>\n<p>No. Identify the existing suppression, driver and polarity requirements, and review any effect on release and system behavior before changing the circuit.<\/p>\n<h3>Does disappearance of the symptom prove complete EMC compliance?<\/h3>\n<p>No. It verifies only the tested behavior and conditions. Compliance and safety validation require their own defined evidence.<\/p>\n<h2>Product and related engineering references<\/h2>\n<p>Request the current documentation for the <a href=\"https:\/\/sayoon-dc.com\/product\/szj100a-d-normally-open-dc-contactor\/\">SZJ100A-D Sayoon product reference<\/a>. Use the <a href=\"https:\/\/sayoon-dc.com\/blog\/dc-contactor-selection-guide-key-factors-for-reliable-motor-control\/\">DC contactor selection guide<\/a> for the full application. Related reviews: <a href=\"https:\/\/sayoon-dc.com\/blog\/drive-dc-contactor-coil-from-plc\/\">PLC coil-driver interface<\/a>, <a href=\"https:\/\/sayoon-dc.com\/blog\/contactor-coil-surge-suppression\/\">coil surge suppression<\/a>, <a href=\"https:\/\/sayoon-dc.com\/blog\/dc-contactor-coil-power-supply-sizing\/\">shared coil power-supply sizing<\/a>.<\/p>\n<h2>Technical sources and scope<\/h2>\n<ul>\n<li><a rel=\"noopener nofollow\" href=\"https:\/\/www.ti.com\/document-viewer\/lit\/html\/snvaa45\" target=\"_blank\">Texas Instruments inductive-load switching application brief<\/a>: apply the stated scope and exact equipment instructions; this does not certify the illustrated product.<\/li>\n<li><a rel=\"noopener nofollow\" href=\"https:\/\/www.tek.com\/en\/documents\/whitepaper\/abcs-probes-primer\" target=\"_blank\">Tektronix probe and noise guidance<\/a>: apply the stated scope and exact equipment instructions; this does not certify the illustrated product.<\/li>\n<li><a rel=\"noopener nofollow\" href=\"https:\/\/www.ecfr.gov\/current\/title-29\/subtitle-B\/chapter-XVII\/part-1910\/subpart-S\/section-1910.333\" target=\"_blank\">29 CFR 1910.333 electrical work practices<\/a>: use the applicable jurisdiction and approved isolation procedure.<\/li>\n<\/ul>\n<p><script type=\"application\/ld+json\">{\"@context\": \"https:\/\/schema.org\", \"@type\": \"FAQPage\", \"mainEntity\": [{\"@type\": \"Question\", \"name\": \"Does a reset during contactor switching prove the coil is faulty?\", \"acceptedAnswer\": {\"@type\": \"Answer\", \"text\": \"No. Establish whether the controller lost power, entered a fault, changed program state, or lost communications, then correlate the evidence.\"}}, {\"@type\": \"Question\", \"name\": \"Can I diagnose the problem from a steady supply reading?\", \"acceptedAnswer\": {\"@type\": \"Answer\", \"text\": \"Not reliably. Capture the relevant event at the controller terminals with a suitable instrument and compare the correct equipment requirements.\"}}, {\"@type\": \"Question\", \"name\": \"Should I add a diode immediately?\", \"acceptedAnswer\": {\"@type\": \"Answer\", \"text\": \"No. Identify the existing suppression, driver and polarity requirements, and review any effect on release and system behavior before changing the circuit.\"}}, {\"@type\": \"Question\", \"name\": \"Does disappearance of the symptom prove complete EMC compliance?\", \"acceptedAnswer\": {\"@type\": \"Answer\", \"text\": \"No. It verifies only the tested behavior and conditions. Compliance and safety validation require their own defined evidence.\"}}]}<\/script><\/p>\n<style>.sy-table-wrap{max-width:100%;overflow-x:auto}.sy-table-wrap table{min-width:650px;border-collapse:collapse;width:100%}.sy-table-wrap td,.sy-table-wrap th{padding:12px;border:1px solid #d5dce4;text-align:left;vertical-align:top}figure{margin:24px 0}figure img{max-width:100%;height:auto}iframe{max-width:100%}<\/style>\n","protected":false},"excerpt":{"rendered":"<p>\u30b3\u30f3\u30dd\u30fc\u30cd\u30f3\u30c8\u306e\u4ea4\u63db\u524d\u306b\u3001\u30b3\u30f3\u30bf\u30af\u30bf\u30fc\u52d5\u4f5c\u4e2d\u306ePLC\u30ea\u30bb\u30c3\u30c8\u3092\u3001\u96fb\u6e90\u4f4e\u4e0b\u3001\u30b9\u30a4\u30c3\u30c1\u30f3\u30b0\u30a4\u30d9\u30f3\u30c8\u3001\u901a\u4fe1\u969c\u5bb3\u3001\u304a\u3088\u3073\u30d7\u30ed\u30b0\u30e9\u30e0\u30a8\u30e9\u30fc\u3092\u5206\u96e2\u3057\u3066\u8a3a\u65ad\u3057\u307e\u3059\u3002.<\/p>","protected":false},"author":4,"featured_media":4450,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_gspb_post_css":"","footnotes":""},"categories":[1],"tags":[61],"class_list":["post-3787","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-blog","tag-dc-contactor-engineering"],"blocksy_meta":{"styles_descriptor":{"styles":{"desktop":"","tablet":"","mobile":""},"google_fonts":[],"version":7}},"_links":{"self":[{"href":"https:\/\/sayoon-dc.com\/ja\/wp-json\/wp\/v2\/posts\/3787","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/sayoon-dc.com\/ja\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/sayoon-dc.com\/ja\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/sayoon-dc.com\/ja\/wp-json\/wp\/v2\/users\/4"}],"replies":[{"embeddable":true,"href":"https:\/\/sayoon-dc.com\/ja\/wp-json\/wp\/v2\/comments?post=3787"}],"version-history":[{"count":5,"href":"https:\/\/sayoon-dc.com\/ja\/wp-json\/wp\/v2\/posts\/3787\/revisions"}],"predecessor-version":[{"id":5117,"href":"https:\/\/sayoon-dc.com\/ja\/wp-json\/wp\/v2\/posts\/3787\/revisions\/5117"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/sayoon-dc.com\/ja\/wp-json\/wp\/v2\/media\/4450"}],"wp:attachment":[{"href":"https:\/\/sayoon-dc.com\/ja\/wp-json\/wp\/v2\/media?parent=3787"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/sayoon-dc.com\/ja\/wp-json\/wp\/v2\/categories?post=3787"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/sayoon-dc.com\/ja\/wp-json\/wp\/v2\/tags?post=3787"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}