SGDB-20VD - Yaskawa SGDB-20VD Sigma servo drive

Evidence-backed servo drive role for SGDB-20VD, with explicit installation boundaries.

Documented function

Rebuilt from individual evidence

System position

Unknown: Evidence boundary

Yaskawa's EMC document explicitly lists SGDB-20VD as an SGDB-VD SERVOPACK in the three-phase 200 V class.

Yaskawa assigns SGDB-20VD the FN351-25/33 noise filter in the documented EMC installation table.

The SGDB manual documents R, S, and T power input, U, V, and W motor terminals, and encoder and controller connections for the SERVOPACK.

The drive sits between the upstream controller and the matched servo motor in the documented axis.

The drive converts controller references into controlled electrical output for the matched servo motor.

Unknown: The exact motor capacity, installed parameter set, controller mode, and machine load are not established by the captured sources.

Exact reference
SGDB-20VD
Category
Drives / VFD
Evidence checked
2026-09-12

System role

This section explains what the product does and where it acts in the surrounding system.

Function
Drives a matched Sigma servomotor from the SGDB controller interface.
System position
Sits between the three-phase power and host controller on one side and the matched servomotor on the other.
Upstream / inputs
Receives controller references and encoder feedback through the documented SGDB connections.
Downstream / outputs
Supplies controlled three-phase motor power through the U, V, and W terminals.
Limitations
Unknown: The exact motor capacity, installed parameter set, controller mode, and machine load are not established by the captured sources.

Evidence ledger

Facts, inferences, and unknowns are kept separate.

Facts

  • Yaskawa's EMC document explicitly lists SGDB-20VD as an SGDB-VD SERVOPACK in the three-phase 200 V class.

    Confidence: high

  • Yaskawa assigns SGDB-20VD the FN351-25/33 noise filter in the documented EMC installation table.

    Confidence: high

  • The SGDB manual documents R, S, and T power input, U, V, and W motor terminals, and encoder and controller connections for the SERVOPACK.

    Confidence: high

Inferences

  • The drive sits between the upstream controller and the matched servo motor in the documented axis.

    Confidence: medium

    Rationale: The documented product type, interfaces, and motor or controller relationships support this system position.

  • The drive converts controller references into controlled electrical output for the matched servo motor.

    Confidence: medium

    Rationale: The documented control interfaces and motor or feedback connections support this signal and power path.

Unknowns

  • Unknown: The exact motor capacity, installed parameter set, controller mode, and machine load are not established by the captured sources.

    Confidence: low

    Missing evidence: The exact motor capacity, installed parameter set, controller mode, and machine load are not established by the captured sources.

System position diagram

Diagram showing SGDB-20VD between a motion controller and a matched servo motor.

Reading limit: system position only, not a wiring or safety drawing.

System position of SGDB-20VD from the captured evidence.

Enlarged system diagram

Diagram showing SGDB-20VD between a motion controller and a matched servo motor.

System position of SGDB-20VD from the captured evidence.

View Mermaid source
flowchart LR
  controller[Motion controller] --> unit[SGDB-20VD]
  unit --> motor[Matched servo motor]
View diagram labels
Nodes
Motion controller; SGDB-20VD; Matched servo motor
Edges
Upstream control reaches the product; The product provides the documented downstream function

Next action

Decision: The captured evidence supports the documented servo drive role for SGDB-20VD; verify the installed system before replacement.

Next action: Match the exact reference, compatible controller or amplifier, feedback arrangement, and site conditions against the cited documents before sourcing.

Request help with this reference

Request help with this reference

Provide the exact reference, machine context, and observed symptom so the next review can stay evidence-based.

Submission is unavailable until durable storage is verified.

Recovery request details
Add context only if useful
Optional updates
Recipient and data disclosure

Recipient and data disclosure

Named recipient: Ardkor human-qualification queue (internal local preview). No partner delivery is enabled here.

Data retained for this review: reference, selected route, location, technical context, contact details, consent state, and any accepted private attachment.

Response expectation: none is promised. If external routing is enabled later, the partner name, disclosed fields, and response expectation must be shown and accepted again.

Withdrawal and deletion: use the private request controls from the receipt to withdraw further processing or request access/deletion. The request remains recorded until the relevant Ardkor systems and any recipient confirm completion.

Read the privacy information before sending. For corrections, access, or deletion help, use the contact page or email reference@ardkor.org; mailbox delivery and attendance have not been verified.

This routing state is separate from watch, marketing, payment, and analytics choices. If no capable service match is found, the request remains a human-qualification lead and is never presented as provider acceptance. Ardkor is not an emergency or safety service and submission does not guarantee availability, price, repair, sourcing, or response.