{"id":2773,"date":"2026-08-11T11:00:00","date_gmt":"2026-08-11T03:00:00","guid":{"rendered":"https:\/\/sayoon-dc.com\/blog\/dc-contactor-chattering-diagnostic-record\/"},"modified":"2026-08-11T11:00:00","modified_gmt":"2026-08-11T03:00:00","slug":"dc-contactor-chattering-diagnostic-record","status":"publish","type":"post","link":"https:\/\/sayoon-dc.com\/fr\/blog\/dc-contactor-chattering-diagnostic-record\/","title":{"rendered":"Qu'enregistrer lorsqu'un contacteur \u00e0 courant continu vibre"},"content":{"rendered":"<div class=\"b2b-article\">\n<p style=\"margin:0 0 16px;line-height:1.7\"><strong>DC contactor chattering<\/strong> should be treated as an event to document before it is treated as a cause to name. A useful record preserves the approved inspection condition, the command state, the drawing context, the repeated movement observed, and the installed device marking.<\/p>\n<p style=\"margin:0 0 16px;line-height:1.7\">That approach gives a service or engineering reviewer something concrete to evaluate. It also prevents an unstable sound or movement from being converted too quickly into a generic coil or replacement conclusion.<\/p>\n<figure class=\"wp-block-image\" style=\"clear:both;display:block;float:none;\"><img decoding=\"async\" src=\"https:\/\/sayoon-dc.com\/wp-content\/uploads\/2026\/08\/dc-contactor-chattering-diagnostic-record-hero.webp\" alt=\"Contacteur DC SAYOON illustr\u00e9 pour un enregistrement de diagnostic de b\u00e9gaiement de contacteur\" style=\"float:none;display:block;max-width:640px;height:auto;\" \/><\/figure>\n<nav class=\"b2b-toc\" style=\"background:#f5f8fa;padding:16px 20px;border-radius:8px;margin:0 0 24px\">\n<h2 id=\"contents\" style=\"margin:42px 0 14px;scroll-margin-top:96px\">Contenu<\/h2>\n<ul style=\"margin:0 0 18px 1.2em;line-height:1.7\">\n<li style=\"margin:0 0 8px\"><a href=\"#part-1-what-should-be-controlled-before-a-chattering-event-is-inspected\">Part 1. What should be controlled before a chattering event is inspected?<\/a><\/li>\n<li style=\"margin:0 0 8px\"><a href=\"#part-2-what-makes-a-chattering-observation-useful\">Part 2. What makes a chattering observation useful?<\/a><\/li>\n<li style=\"margin:0 0 8px\"><a href=\"#part-3-which-command-path-details-belong-in-the-record\">Part 3. Which command-path details belong in the record?<\/a><\/li>\n<li style=\"margin:0 0 8px\"><a href=\"#part-4-how-should-the-repeated-movement-be-described\">Part 4. How should the repeated movement be described?<\/a><\/li>\n<li style=\"margin:0 0 8px\"><a href=\"#part-5-which-surrounding-conditions-should-not-be-assumed\">Part 5. Which surrounding conditions should not be assumed?<\/a><\/li>\n<li style=\"margin:0 0 8px\"><a href=\"#part-6-when-is-chattering-not-a-replacement-decision\">Part 6. When is chattering not a replacement decision?<\/a><\/li>\n<li style=\"margin:0 0 8px\"><a href=\"#part-7-how-should-a-team-send-the-event-record-for-review\">Part 7. How should a team send the event record for review?<\/a><\/li>\n<\/ul>\n<\/nav>\n<h2 style=\"margin:42px 0 14px;scroll-margin-top:96px\" id=\"part-1-what-should-be-controlled-before-a-chattering-event-is-inspected\">Part 1. What should be controlled before a chattering event is inspected?<\/h2>\n<p style=\"margin:0 0 16px;line-height:1.7\">Begin with the site\u2019s approved isolation and safe-condition verification process. A chattering sound or repeated movement does not indicate that the control supply, main path, stored energy, or auxiliary feeds are safe to inspect. The OSHA energy-control and electrical-work sources explain the cited safety principle, while the responsible site defines authorization and competent-person requirements. (<a href=\"https:\/\/www.osha.gov\/laws-regs\/regulations\/standardnumber\/1910\/1910.147\" rel=\"nofollow noopener\" target=\"_blank\">contr\u00f4le de l'\u00e9nergie de l'OSHA<\/a>, <a href=\"https:\/\/www.osha.gov\/laws-regs\/regulations\/standardnumber\/1910\/1910.333\" rel=\"nofollow noopener\" target=\"_blank\">Pratiques de travail \u00e9lectrique de l'OSHA<\/a>)<\/p>\n<p style=\"margin:0 0 16px;line-height:1.7\">Establish the observation boundary first. Note where the symptom was noticed, which drawing revision is available, and whether the record comes from a permitted observation, an event log, or an approved diagnostic step.<\/p>\n<blockquote>\n<p style=\"margin:0 0 16px;line-height:1.7\"><strong>Important :<\/strong> Do not force the contactor mechanism or repeat commands merely to make the symptom disappear. Use the site\u2019s approved isolation and verification process before inspection. Source: OSHA safety references listed below.<\/p>\n<\/blockquote>\n<h2 style=\"margin:42px 0 14px;scroll-margin-top:96px\" id=\"part-2-what-makes-a-chattering-observation-useful\">Part 2. What makes a chattering observation useful?<\/h2>\n<p style=\"margin:0 0 16px;line-height:1.7\">Useful observations answer what happened and when. Write down the beginning and end of the reported event, the system state that preceded it, and the indication or movement seen by the team. Keep the language descriptive: \u201crepeated movement during the recorded command condition\u201d is more useful than an unsupported diagnosis.<\/p>\n<table style=\"width:100%;border-collapse:collapse\">\n<thead>\n<tr>\n<th style=\"border:1px solid #d9e1e8;padding:9px 12px;background:#f5f8fa;text-align:left\">Event record element<\/th>\n<th style=\"border:1px solid #d9e1e8;padding:9px 12px;background:#f5f8fa;text-align:left\">Capture<\/th>\n<th style=\"border:1px solid #d9e1e8;padding:9px 12px;background:#f5f8fa;text-align:left\">Valeur d'examen<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td style=\"border:1px solid #d9e1e8;padding:9px 12px\">Reported symptom<\/td>\n<td style=\"border:1px solid #d9e1e8;padding:9px 12px\">What was heard or seen and where it was observed<\/td>\n<td style=\"border:1px solid #d9e1e8;padding:9px 12px\">Preserves the starting condition.<\/td>\n<\/tr>\n<tr>\n<td style=\"border:1px solid #d9e1e8;padding:9px 12px\">Sequence context<\/td>\n<td style=\"border:1px solid #d9e1e8;padding:9px 12px\">The command or system event immediately before it<\/td>\n<td style=\"border:1px solid #d9e1e8;padding:9px 12px\">Links the symptom to a specific operating moment.<\/td>\n<\/tr>\n<tr>\n<td style=\"border:1px solid #d9e1e8;padding:9px 12px\">Source d'observation<\/td>\n<td style=\"border:1px solid #d9e1e8;padding:9px 12px\">Approved inspection note, system event record, or labelled photo<\/td>\n<td style=\"border:1px solid #d9e1e8;padding:9px 12px\">Shows how the information was obtained.<\/td>\n<\/tr>\n<tr>\n<td style=\"border:1px solid #d9e1e8;padding:9px 12px\">Time order<\/td>\n<td style=\"border:1px solid #d9e1e8;padding:9px 12px\">What changed before and after the event<\/td>\n<td style=\"border:1px solid #d9e1e8;padding:9px 12px\">Helps separate an event sequence from a later assumption.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p style=\"margin:0 0 16px;line-height:1.7\">Do not combine several changes into one vague service note. The record should let a reviewer see whether the device was being commanded, whether the expected sequence was present, and what was actually observed.<\/p>\n<h2 style=\"margin:42px 0 14px;scroll-margin-top:96px\" id=\"part-3-which-command-path-details-belong-in-the-record\">Part 3. Which command-path details belong in the record?<\/h2>\n<p style=\"margin:0 0 16px;line-height:1.7\">Use the actual circuit drawing to identify the intended command path. Record the terminal labels used in the installation, the command state expected at the event, the relevant interlock or control logic, and the installed marking. This is not a request to infer a generic coil value from an image; it is a way to link the observation to the correct documentation.<\/p>\n<p style=\"margin:0 0 16px;line-height:1.7\">Readers who need to clarify the terminal language can use the related <a href=\"https:\/\/sayoon-dc.com\/fr\/blog\/contactor-a1-a2-wiring-dc-coil-terminals-panel-builders\/\">A1 and A2 coil-terminal guide<\/a>. It supports terminology and should not replace the installed drawing or label.<\/p>\n<p style=\"margin:0 0 16px;line-height:1.7\">For a no-movement symptom rather than repeated movement, see the related <a href=\"https:\/\/sayoon-dc.com\/fr\/blog\/dc-contactor-coil-not-pulling-in-diagnosis\/\">no-pull-in diagnostic guide<\/a>. The two topics use different event records and should not be merged into one replacement conclusion.<\/p>\n<h2 style=\"margin:42px 0 14px;scroll-margin-top:96px\" id=\"part-4-how-should-the-repeated-movement-be-described\">Part 4. How should the repeated movement be described?<\/h2>\n<p style=\"margin:0 0 16px;line-height:1.7\">Describe the observed movement along with the condition under which it occurred. Record whether the movement was reported during a command event, whether it agreed with the drawing-defined expectation, and whether an approved indication changed with it. Do not convert the movement into an exact mechanical, electrical, or coil conclusion without the relevant evidence.<\/p>\n<figure class=\"wp-block-image\" style=\"clear:both;display:block;float:none;\"><img decoding=\"async\" src=\"https:\/\/sayoon-dc.com\/wp-content\/uploads\/2026\/08\/dc-contactor-chattering-diagnostic-record-explainer.webp\" alt=\"SAYOON DC contactor view for a control-event observation record\" style=\"float:none;display:block;max-width:640px;height:auto;\" \/><\/figure>\n<table style=\"width:100%;border-collapse:collapse\">\n<thead>\n<tr>\n<th style=\"border:1px solid #d9e1e8;padding:9px 12px;background:#f5f8fa;text-align:left\">Observation wording<\/th>\n<th style=\"border:1px solid #d9e1e8;padding:9px 12px;background:#f5f8fa;text-align:left\">Include with it<\/th>\n<th style=\"border:1px solid #d9e1e8;padding:9px 12px;background:#f5f8fa;text-align:left\">Ne concluez pas<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td style=\"border:1px solid #d9e1e8;padding:9px 12px\">Repeated movement was observed<\/td>\n<td style=\"border:1px solid #d9e1e8;padding:9px 12px\">Command state and drawing reference<\/td>\n<td style=\"border:1px solid #d9e1e8;padding:9px 12px\">A specific coil or mechanism cause.<\/td>\n<\/tr>\n<tr>\n<td style=\"border:1px solid #d9e1e8;padding:9px 12px\">Indication changed during the event<\/td>\n<td style=\"border:1px solid #d9e1e8;padding:9px 12px\">Terminal or logic function represented<\/td>\n<td style=\"border:1px solid #d9e1e8;padding:9px 12px\">That all main contacts followed the indication.<\/td>\n<\/tr>\n<tr>\n<td style=\"border:1px solid #d9e1e8;padding:9px 12px\">Symptom ended after a system change<\/td>\n<td style=\"border:1px solid #d9e1e8;padding:9px 12px\">What change was recorded and when<\/td>\n<td style=\"border:1px solid #d9e1e8;padding:9px 12px\">That the change proved the root cause.<\/td>\n<\/tr>\n<tr>\n<td style=\"border:1px solid #d9e1e8;padding:9px 12px\">Event reappeared<\/td>\n<td style=\"border:1px solid #d9e1e8;padding:9px 12px\">New event record and operating context<\/td>\n<td style=\"border:1px solid #d9e1e8;padding:9px 12px\">That repeated cycling is a corrective action.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<h2 style=\"margin:42px 0 14px;scroll-margin-top:96px\" id=\"part-5-which-surrounding-conditions-should-not-be-assumed\">Part 5. Which surrounding conditions should not be assumed?<\/h2>\n<p style=\"margin:0 0 16px;line-height:1.7\">Do not assume that an auxiliary indication proves the main-contact state, that a similar sound means the same cause in every circuit, or that the installed terminal count establishes the replacement. The command path, contact function, connected application, and drawing-defined sequence each add information that a sound or movement alone cannot provide.<\/p>\n<p style=\"margin:0 0 16px;line-height:1.7\">Practitioner discussions about contactor testing show why an observed state and a release decision should remain separate. (<a href=\"https:\/\/www.eevblog.com\/forum\/projects\/welded-contactor-test\/\" rel=\"nofollow noopener\" target=\"_blank\">EEVblog discussion of contactor state evidence<\/a>) Keep the record at the level of evidence actually captured.<\/p>\n<h2 style=\"margin:42px 0 14px;scroll-margin-top:96px\" id=\"part-6-when-is-chattering-not-a-replacement-decision\">Part 6. When is chattering not a replacement decision?<\/h2>\n<p style=\"margin:0 0 16px;line-height:1.7\">Chattering is not a replacement decision when the record lacks the installed marking, command state, drawing context, or required contact function. It is also not enough to select from an image, enclosure shape, or a remembered coil detail.<\/p>\n<p style=\"margin:0 0 16px;line-height:1.7\">Use the symptom to start a review, not to bypass it. A compatible replacement discussion needs the application information and exact product documentation that connect the device to its intended role.<\/p>\n<p style=\"margin:0 0 16px;line-height:1.7\">For the broader method boundary, review the related <a href=\"https:\/\/sayoon-dc.com\/fr\/blog\/how-to-test-a-dc-contactor-safely\/\">safe DC contactor test sequence<\/a>. It does not authorize work outside the site\u2019s approved procedure or supply a model-specific acceptance value.<\/p>\n<h2 style=\"margin:42px 0 14px;scroll-margin-top:96px\" id=\"part-7-how-should-a-team-send-the-event-record-for-review\">Part 7. How should a team send the event record for review?<\/h2>\n<p style=\"margin:0 0 16px;line-height:1.7\">When the event record is ready, SAYOON\u2019s <a href=\"https:\/\/sayoon-dc.com\/fr\/produits\/\">Gamme de produits de contacteurs CC<\/a> can provide product-family context, including the <a href=\"https:\/\/sayoon-dc.com\/fr\/contacteur-cc-de-la-serie-czw\/\">Gamme de contacteurs CC CZW<\/a> et <a href=\"https:\/\/sayoon-dc.com\/fr\/contacteur-cc-de-la-serie-szj\/\">Ligne de contacteurs CC SZJ<\/a>. These links help start a review conversation; they do not identify a model for the installed circuit.<\/p>\n<figure class=\"wp-block-image\" style=\"clear:both;display:block;float:none;\"><img decoding=\"async\" src=\"https:\/\/sayoon-dc.com\/wp-content\/uploads\/2026\/08\/dc-contactor-chattering-diagnostic-record-product.webp\" alt=\"SAYOON DC contactor product view for diagnostic review\" style=\"float:none;display:block;max-width:640px;height:auto;\" \/><\/figure>\n<table style=\"width:100%;border-collapse:collapse\">\n<thead>\n<tr>\n<th style=\"border:1px solid #d9e1e8;padding:9px 12px;background:#f5f8fa;text-align:left\">Demande de devis \/ L'acheteur doit fournir<\/th>\n<th style=\"border:1px solid #d9e1e8;padding:9px 12px;background:#f5f8fa;text-align:left\">Pourquoi c'est important<\/th>\n<th style=\"border:1px solid #d9e1e8;padding:9px 12px;background:#f5f8fa;text-align:left\">\u00c9vitez ce raccourci<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td style=\"border:1px solid #d9e1e8;padding:9px 12px\">Event timeline with the reported chattering condition<\/td>\n<td style=\"border:1px solid #d9e1e8;padding:9px 12px\">Gives the reviewer an operating sequence<\/td>\n<td style=\"border:1px solid #d9e1e8;padding:9px 12px\">Sending only \u201cit chatters.\u201d<\/td>\n<\/tr>\n<tr>\n<td style=\"border:1px solid #d9e1e8;padding:9px 12px\">Drawing reference and command-path note<\/td>\n<td style=\"border:1px solid #d9e1e8;padding:9px 12px\">Connects the event to its intended control function<\/td>\n<td style=\"border:1px solid #d9e1e8;padding:9px 12px\">Treating a terminal photo as complete circuit evidence.<\/td>\n<\/tr>\n<tr>\n<td style=\"border:1px solid #d9e1e8;padding:9px 12px\">Installed marking and labelled terminal views<\/td>\n<td style=\"border:1px solid #d9e1e8;padding:9px 12px\">Links the request to the device under review<\/td>\n<td style=\"border:1px solid #d9e1e8;padding:9px 12px\">Choosing by enclosure appearance.<\/td>\n<\/tr>\n<tr>\n<td style=\"border:1px solid #d9e1e8;padding:9px 12px\">Required contact function and application description<\/td>\n<td style=\"border:1px solid #d9e1e8;padding:9px 12px\">Frames the selection question<\/td>\n<td style=\"border:1px solid #d9e1e8;padding:9px 12px\">Reusing a remembered coil detail from another device.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p style=\"margin:0 0 16px;line-height:1.7\">The fit boundary is explicit: the event record supports review but does not select a replacement. When the information is ready, <a href=\"https:\/\/sayoon-dc.com\/fr\/contactez-nous\/\">send the chattering-event record for review<\/a> with the relevant application context.<\/p>\n<h2 style=\"margin:42px 0 14px;scroll-margin-top:96px\" id=\"faq\">FAQ<\/h2>\n<h3 style=\"margin:28px 0 12px\">Does chattering prove a coil fault?<\/h3>\n<p style=\"margin:0 0 16px;line-height:1.7\">No. It is an observation that should be recorded with the command path, drawing context, and installed marking before a cause is assigned.<\/p>\n<h3 style=\"margin:28px 0 12px\">Should the device be repeatedly commanded?<\/h3>\n<p style=\"margin:0 0 16px;line-height:1.7\">Do not repeat commands to try to clear the symptom. Follow the approved safety process, preserve the event record, and use the responsible review process for the next action.<\/p>\n<h3 style=\"margin:28px 0 12px\">Why is the drawing required?<\/h3>\n<p style=\"margin:0 0 16px;line-height:1.7\">The drawing identifies the intended command path and expected sequence. It helps a reviewer understand what the observed movement was being compared with.<\/p>\n<h3 style=\"margin:28px 0 12px\">Can a meter reading identify a cause?<\/h3>\n<p style=\"margin:0 0 16px;line-height:1.7\">No. A reading may be one observation, but it does not replace the command context, installed marking, drawing, and exact product documentation.<\/p>\n<h3 style=\"margin:28px 0 12px\">Does a product page select the replacement?<\/h3>\n<p style=\"margin:0 0 16px;line-height:1.7\">No. A product page is a discovery destination. Final selection requires a documented application review.<\/p>\n<h3 style=\"margin:28px 0 12px\">Que doit-on inclure avec la demande de prix ?<\/h3>\n<p style=\"margin:0 0 16px;line-height:1.7\">Include with the RFQ the event timeline, drawing reference, command-path note, installed marking, labelled terminal views, required contact function, and application description.<\/p>\n<h2 style=\"margin:42px 0 14px;scroll-margin-top:96px\" id=\"references\">R\u00e9f\u00e9rences<\/h2>\n<ul style=\"margin:0 0 18px 1.2em;line-height:1.7\">\n<li style=\"margin:0 0 8px\"><a href=\"https:\/\/www.osha.gov\/laws-regs\/regulations\/standardnumber\/1910\/1910.147\" rel=\"nofollow noopener\" target=\"_blank\">OSHA resource on hazardous-energy control<\/a> is cited for the isolation boundary in this event-record discussion.<\/li>\n<li style=\"margin:0 0 8px\"><a href=\"https:\/\/www.osha.gov\/laws-regs\/regulations\/standardnumber\/1910\/1910.333\" rel=\"nofollow noopener\" target=\"_blank\">OSHA page on electrical work practices<\/a> is cited for the inspection safety boundary in this event-record discussion.<\/li>\n<li style=\"margin:0 0 8px\"><a href=\"https:\/\/www.eevblog.com\/forum\/projects\/welded-contactor-test\/\" rel=\"nofollow noopener\" target=\"_blank\">EEVblog discussion of contactor state evidence<\/a> supplies practitioner question language only.<\/li>\n<\/ul>\n<\/div>","protected":false},"excerpt":{"rendered":"<p>DC contactor chattering should be treated as an event to document before it is treated as a cause to name. A useful record preserves the approved inspection condition, the command state, the drawing context, the repeated movement observed, and the installed device marking. That approach gives a service or engineering reviewer something concrete to evaluate. [&hellip;]<\/p>\n","protected":false},"author":3,"featured_media":2767,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_gspb_post_css":"","footnotes":""},"categories":[1],"tags":[],"class_list":["post-2773","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-blog"],"blocksy_meta":{"styles_descriptor":{"styles":{"desktop":"","tablet":"","mobile":""},"google_fonts":[],"version":7}},"_links":{"self":[{"href":"https:\/\/sayoon-dc.com\/fr\/wp-json\/wp\/v2\/posts\/2773","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/sayoon-dc.com\/fr\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/sayoon-dc.com\/fr\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/sayoon-dc.com\/fr\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/sayoon-dc.com\/fr\/wp-json\/wp\/v2\/comments?post=2773"}],"version-history":[{"count":0,"href":"https:\/\/sayoon-dc.com\/fr\/wp-json\/wp\/v2\/posts\/2773\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/sayoon-dc.com\/fr\/wp-json\/wp\/v2\/media\/2767"}],"wp:attachment":[{"href":"https:\/\/sayoon-dc.com\/fr\/wp-json\/wp\/v2\/media?parent=2773"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/sayoon-dc.com\/fr\/wp-json\/wp\/v2\/categories?post=2773"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/sayoon-dc.com\/fr\/wp-json\/wp\/v2\/tags?post=2773"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}