The controller questions to settle before buying a motorized stage

A motorized stage can be a suitable mechanical candidate while its automation package remains unspecified. Before placing an order, turn the word “controller” into a short list of deliverables, interfaces and responsible parties. The useful outcome is a questionnaire that a purchasing team can compare line by line, rather than a promise that two boxes will work together.

Start with an itemized supply boundary

Record the proposed stage and motor identifiers, then give the drive or amplifier, motion controller, power supply, cable set and host software their own rows. For each row, ask whether it is included, optional, provided by the integrator or unresolved. Include configuration and commissioning services separately from hardware. A cable shown in a photograph is not purchasing evidence.

Our product pages identify controller and cable supply as matters for quotation confirmation. Use the stage selector to establish the mechanical shortlist, then attach the specific product page to the questionnaire. Do not interpret a listed motor or sensor as confirmation of a complete automation system.

Ask who owns the final bill of materials. If a distributor selects the drive and an integrator selects the controller, someone must still verify the interface between them. Put that responsibility in the quotation instead of leaving it as a shared assumption.

Ask for evidence at each interface

Request the current motor electrical documentation, connector drawing, cable assignment and controller compatibility statement for the exact revisions offered. Identify which party will confirm supply requirements and protective provisions. Never derive a pinout from the connector’s appearance or reuse a cable simply because it fits.

Next specify the host environment: operating system or PLC family, available communications hardware, application language if relevant, and ownership of the machine program. Ask for supported versions, installation requirements and a sample communication exchange that can be reviewed without moving machinery. Availability of a software download does not establish its suitability for the intended host.

The Zaber protocol manual limits command support by product and firmware. That is a useful documentation example, not evidence of compatibility with this catalogue. Request equally specific evidence from the proposed controller provider.

Procurement questionnaire checklist

Use this original purchasing worksheet to compare the same deliverable boundary. The owner column proposes who should close each question; the parties must agree the actual responsibility. It does not assert compatibility or an included supply scope.

Purchase item	Evidence to attach to the quotation	Proposed owner to agree
Stage, motor and drive	Exact identifiers, revisions and configuration-specific electrical documentation	Hardware supplier with integrator review
Controller and host	Controller revision, firmware, supported host environment and interface documentation	Controller provider and software integrator
Cables and power	Cable schedule, connector assignments, power requirements and explicit included/optional items	Supplier responsible for the connection package
Reference, limits and faults	Documented reference establishment, travel-limit behavior, status reporting and restart requirements	Controls integrator with supplier confirmation
Camera or measuring instrument	Trigger direction, readiness/completion signals, timeout ownership and example event record	Instrument owner and controls integrator
Delivery and service	Configuration backup, required licences, acceptance record and support exclusions	Buyer and delivery lead

For each row, record the document identifier, revision, included/optional/customer-supplied status and unresolved decision. An absent cable schedule or unsupported host version remains an open item; a lower price does not close it.

Hypothetical quotation review

Imagine an inspection fixture needs two independent translation axes and a camera. Quote A includes stage assemblies and motors. Quote B includes those items plus a controller, but its cable scope is unclear. Neither offer documents camera triggering. The buyer should not call B a complete inspection system simply because its total is higher.

Instead, create three unresolved actions: obtain the cable schedule, establish host communication support, and define camera synchronization responsibility. Ask each bidder to price the same deliverable boundary. The example contains no recommended controller, operating settings or validated machine architecture; it illustrates how to make two offers comparable.

Separate acknowledgement from process completion

A useful conceptual hand-off is: connection checked, reference established as required, move requested, controller motion status checked, application readiness confirmed, instrument acquisition completed, and result recorded. Agree which component reports each transition before deciding how the process advances.

The Zaber protocol manual illustrates why a reply alone is insufficient: its examples return an accepted command while the device reports BUSY. This describes that protocol, not a catalogue controller. Obtain the equivalent state definitions for the proposed package, and keep workpiece settling or measurement validity separate from a controller’s motion-complete indication.

Condition to discuss	Question to resolve before acceptance	Evidence to retain
Command acknowledged	Has motion finished, or only been accepted?	Timestamped command/reply and motion-state record
Instrument not ready	Who waits, times out and records the incomplete cycle?	Agreed event sequence and incomplete-result policy
Communication interrupted	Which result is unknown, and what revalidation is required before resuming?	Connection-loss record and agreed recovery test
Configuration restored	Are the axis identity, units and reference state the intended ones?	Versioned backup and witnessed restoration record

These are review questions, not executable machine logic or instructions to bypass protective functions. The responsible integrator must define and test the actual sequence.

Close the order with observable acceptance

Define what the buyer must witness: correct axis identification, configuration recovery, documented fault reporting and the agreed process sequence under the intended fixture load. Describe the measurement evidence separately from successful command transmission. An application window reporting completion does not prove that the workpiece reached its required location.

Agree how deviations will be recorded and who decides whether they affect acceptance. Keep genuine technical review pending until the electrical documentation, software evidence and representative test results are available. The questionnaire should reduce ambiguity before purchase, rather than attempt to replace commissioning or a machine risk assessment.