Solutions / Engineering guide
Wind Turbine Controller Supply: Prepare a Separate Enquiry
MARSTON can discuss wind turbine controllers as separate equipment supply. A useful enquiry identifies the turbine and existing devices, the functions being requested and the documentation or integration support needed, so the proposal can define a controller scope without implying a complete installed system.
Define what the controller enquiry includes.
A controller label does not establish its functions or compatibility. Requested algorithms, signals, permissions and operating duties need a response for the actual equipment proposed.
01 / Purchase purpose
State whether this is new supply, replacement or integration.
Describe why the controller is being requested and the turbine equipment it would serve.
Describe why the controller is being requested and the turbine equipment it would serve. Include manufacturer, model, available version references and known changes. For replacement, retain the installed controller identity and the responsible service assessment rather than assuming a reported symptom proves controller failure.
A separate controller enquiry can be considered without purchasing a complete turbine package. It does not establish an available controller catalogue, part number or fit for every other manufacturer’s machine. Provide the actual equipment information so the scope can be assessed.
02 / Function request
Turn broad labels into reviewable duties.
Prepare a function list naming the desired duty, command source, feedback and acceptance evidence.
Prepare a function list naming the desired duty, command source, feedback and acceptance evidence. Possible requests may concern turbine supervision, yaw or brake commands, state reporting or coordination with conversion equipment. These are topics to review, not a guaranteed feature list for every proposed controller.
If MPPT, unloading, remote access or another function is requested, record what outcome is needed and which device currently performs it. Keep turbine control distinct from charging or conversion functions until the actual architecture is established. Avoid treating the words wind controller as a complete functional specification.
03 / Interface pack
Provide the devices and signals the enquiry must cover.
Attach available generator data, controller or converter documents, mechanical actuation information and the existing connection records.
Attach available generator data, controller or converter documents, mechanical actuation information and the existing connection records. Identify auxiliary supplies and signals the connected equipment requires. Mark missing ranges, permissions and timing requirements explicitly rather than copying values from another installation.
Use the interface schedule to identify device and signal boundaries. A physical port alone does not establish supported communication or remote-control authority. The auxiliary-power guide helps identify the supply questions to include.
04 / Delivery items
Agree hardware, documents and integration boundaries.
Ask the proposal to identify the supplied controller, applicable equipment version, included interface documents and any configuration information agreed for delivery.
Ask the proposal to identify the supplied controller, applicable equipment version, included interface documents and any configuration information agreed for delivery. State whether related sensors, actuation equipment, conversion devices or local wiring are included or customer-supplied. Do not assume a controller price contains those items.
Where configuration work or integration support is requested, define its deliverables, responsible party and information dependencies. NASA’s configuration-management guidance provides general context for consistent equipment and document versions; it is not a MARSTON process certification.
05 / Quotation response
Keep confirmed scope distinct from pending functions.
Use a requirement-response matrix with accepted, conditional, clarification-needed or unavailable status.
Use a requirement-response matrix with accepted, conditional, clarification-needed or unavailable status. Record the applicable equipment version and evidence for each response. Attach commercial quantities, destination and requested schedule separately from technical capability statements.
Request actual availability, lead time, support and warranty terms in the proposal. No standing inventory, universal lead time or standard warranty is promised by this guide. Compare offers with the same included scope and unresolved dependencies rather than a controller price alone.
06 / Project handover
Define the records needed by the responsible integrator.
Agree the interface confirmation, required verification records and handover documents before the scope is treated as selected.
Agree the interface confirmation, required verification records and handover documents before the scope is treated as selected. The actual integration and test procedures belong to the responsible project teams. This page supplies no wiring, programming, protection-setting or forced-operation procedure.
Send the turbine identity, function matrix, existing-device documents and requested delivery scope through the equipment enquiry. MARSTON can respond on the controller supply under discussion; it makes no general third-party turbine compatibility or complete-system performance promise here.
Continue the review with Wind Power Converter Supply: Define the Purchase Boundary.
Continue the review with 10 kW vs 20 kW Wind Turbines: Electrical Package Review.
Continue the review with Wind Turbine Factory & Site Acceptance: Evidence Planning.
Further project guides: Wind Controller Protocols & Register Maps.
General background: NASA: Equipment and Document Configuration Identity. These references explain industry concepts; they are separate from the applicable MARSTON product and project documents.
Prepare the information for this review.
Use the checklist to organise the project information. Mark unavailable items and retain document references.
| Review item | Information to provide | Purpose |
|---|---|---|
| Purchase context | Turbine and installed controller identity, version and purpose | Define the separate enquiry. |
| Function matrix | Requested duty, command source, feedback and evidence | Make capability questions specific. |
| Interface pack | Device documents, electrical ranges, signals and auxiliary supply | Identify the connected equipment. |
| Delivery boundary | Hardware, documentation, configuration scope and customer items | Compare the included supply. |
| Response record | Confirmed functions, conditions, commercial terms and handover | Preserve the agreed proposal. |
Engineering questions.
Can wind controllers be discussed separately from a turbine?
Yes. MARSTON can discuss separate controller supply; define the turbine, required functions and actual delivery scope in the enquiry.
Is there a published universal controller specification here?
No. Ratings, functions, device identity and applicability need a configuration-specific supplier response.
Does every controller include MPPT or remote access?
Confirm each requested function for the proposed equipment. The label alone establishes neither implementation nor availability.
Can a controller be assumed compatible with another brand?
Provide that turbine and device documentation for review. No universal third-party compatibility is claimed.
Are sensors and actuators included automatically?
The proposal must identify included and customer-supplied items. Separate controller supply does not automatically include the whole control package.
What should I send to obtain a useful response?
Turbine and current-device identities, the function and interface matrices, available documents and the requested supply, support and delivery scope.
Technical enquiry
Bring your project information to the discussion.
MARSTON can discuss wind turbine controllers as separate equipment supply. Share the available information and the equipment scope you want reviewed in a technical quotation.