DOCUMENTATION

RichAuto Manuals, Wiring Diagrams and Firmware

Reference documents for the A1X, B1X and B5X controller ranges. Every file below belongs to a specific controller and board revision, so confirm the label on the unit before using a wiring reference or loading a firmware package.

Documents by Model

A "Download" link opens a file that is available directly. "Request matching file" means the document is supplied after the controller label, board revision and current version are checked, because a near match is more dangerous than no document.

ModelSeriesManualWiringFirmware
A11A1XA11 manualDownloadA11 wiring setRequest matching fileA11 upgrade packageRequest matching file
A12A1XA1X range manualDownloadA12 wiring referenceDownloadA12 packageRequest matching file
A15A1XA1X range manualDownloadA15 wiring setRequest matching fileA15 packageRequest matching file
A18A1XA18 manualDownloadA18 wiring setRequest matching fileA18 packageRequest matching file
B11B1XB11 operating manualRequest via CINKRB11 wiring referenceDownloadB11 packageRequest matching file
B15B1XB15 operating manualRequest via CINKRB15 wiring referenceDownloadB15 packageRequest matching file
B18B1XB18 operating manualRequest via CINKRB18 wiring referenceDownloadB18 packageRequest matching file
B51B5XB5X system manualDownloadB51 board wiringRequest via CINKRB51 packageRequest matching file
B57B5XB5X system manualDownloadB57 step and servo wiringRequest via CINKRB57 packageRequest matching file
B58B5XB5X system manualDownloadB58 step and servo wiringRequest via CINKRB58 packageRequest matching file

Files marked for request are matched to the controller and interface board before they are sent. For a replacement order, include photographs of the controller label, the board marking and the machine terminals.

Match a Document to Your Controller

  1. Read the controller label. Record the designation and any revision or batch marking, including the suffix shown on the unit.
  2. Read the interface board. The board marking decides which wiring reference applies, even when the controller designation is unchanged.
  3. Note the current version. For a firmware package, the installed version determines the update path and the way back.
  4. Keep the record with the machine. Store the label photographs, version and parameter backup together so the next service visit starts from evidence.

Two units sold under the same model name can carry different boards. That is why the documents here are indexed by model, then matched by board. If the label and the supplied document disagree, stop and request the matching set rather than applying a near match.

Reading the Access Labels

Three labels appear in the table, and they describe how a document is released rather than how useful it is. A file marked for request is not withheld to create friction; it is released after the controller and board are identified, because a document that describes a different board is worse than no document at all.

  • Download. A published file for the model. Open it, then confirm the revision note on the first pages before applying a value to an installed machine.
  • Request matching file. The document exists in more than one revision. Send the label and board marking so the correct one can be selected.
  • Request via CINKR. The document is prepared for the supplied configuration. This is common for wiring sets where the terminal arrangement follows the board variant.

Where a published file and the installed hardware disagree, treat the hardware as the reference and request the matching document. A reference edition can describe an earlier arrangement while remaining correct for the machine it was written for.

Version and revision notes

Each controller carries two identifiers that matter here: the model designation on the label and the board revision inside the cabinet. The model decides which document family applies; the board decides which revision within that family. Recording both at the same time prevents the most common documentation error, which is applying a correct document to the wrong revision.

Keep the record with the machine. A photograph of the label, a photograph of the board and the current version answer the first three questions of any support conversation, and they cost a minute at the machine.

What Each Document Covers

Manuals

Operating sequence, parameter groups, file handling and reference specifications for a controller range. A range manual covers several models and points out where they differ.

How the document set is organised

Wiring references

Interface-board terminals, power rails, input and output groups, and the connector set between handle and board. The revision on the board decides which reference applies.

Wiring checks before power-up

Firmware

Packages that change controller behaviour, matched to the range and board. Record the current version and the parameter set before loading anything.

Firmware version checks

Common Document Questions

Can I use a document for a previous revision?

Only where the revision note confirms it covers the installed board. A document for an earlier board can be correct for that board and misleading for the current one, so compare the marking before applying a value.

Why is the firmware not a public download?

Packages are matched to the controller range, board revision and current version. A package for a different revision can leave the controller unable to start, so the version is confirmed before release.

Does the manual include the wiring set?

A range manual covers functions and parameters; the terminal arrangement follows the interface board. Where the two differ, the board marking decides which wiring reference applies.

What if my model is not in the table?

Send the controller label and board marking. A model that is not listed may share a document with a related model, or may need a document prepared for the supplied configuration.

Common Document Questions

Can I use a document for a previous revision?

Only where the revision note confirms it covers the installed board. A document for an earlier board can be correct for that board and misleading for the current one, so compare the marking before applying a value.

Why is the firmware not a public download?

Packages are matched to the controller range, board revision and current version. A package for a different revision can leave the controller unable to start, so the version is confirmed before release.

Does the manual include the wiring set?

A range manual covers functions and parameters; the terminal arrangement follows the interface board. Where the two differ, the board marking decides which wiring reference applies.

What if my model is not in the table?

Send the controller label and board marking. A model that is not listed may share a document with a related model, or may need a document prepared for the supplied configuration.

Request a Document That Is Not Listed

Some documents are only released against a confirmed controller and board combination, and some models are supplied with a document set that is not published here. Send the four records below and CINKR will confirm what applies to your unit.

  • Controller label photograph, including the suffix and any revision marking.
  • Interface-board marking and a photograph of the terminal arrangement.
  • Current firmware version and any package name already on file.
  • Machine application, axis configuration and the reason for the request.

Send a document request

To attach a model reference, open the product page and use the enquiry form there instead. If the machine is down, start with the controller not working guide so the symptom is recorded before parts are ordered.