There is no useful one-line list of “the types of DC contactors” for every OEM project. A type label helps only when it is tied to the circuit job. Start with four independent lenses, then use the drawing and product documentation to check the available route.
This first-party CZW1600A photo provides product context only; it does not state a rating, system role or model fit for a project.
Use four independent lenses
| Lens | What to record | Why it matters |
|---|---|---|
| Voltage domain | The documented DC system context | It directs the family conversation without assuming a rating. |
| Contact behaviour | Required state and any specified arrangement | It connects a label to the governing drawing. |
| Holding method | Whether a holding-method question is part of the requirement | It is an operating-method question, not an automatic upgrade. |
| Circuit role | Main path, auxiliary path or another documented function | It prevents an application label from replacing circuit evidence. |
Turn a type label into a requirement
- State the circuit role and the action the device must perform.
- Identify the voltage-domain and contact-behaviour information in the drawing.
- Record any holding-method requirement separately.
- Attach the drawing revision, existing label and project conditions to the enquiry.
A product perspective can prompt a documentation check; it does not replace the schematic or identify a project’s required terminals.
If the question is specifically about a default contact state, use the NO and NC contactor configuration guide. The broader SAYOON Products page is useful only after the requirement is clear enough to choose a category.
Continue after the requirement is clear
For a low-voltage DC family route, review the SAYOON CZW Series DC Contactor page. The page supports product-document research after the circuit requirement is recorded; it does not promise that every CZW model fits the reader’s voltage domain, contact behaviour, holding-method or circuit role.
First-party CZW1600A media supports the product-document route only and makes no compatibility or performance claim.
