aerotech.com

EPICS & TANGO SPECIFICATIONS

Feature

EPICS

TANGO

Home Page

Epics Controls

Tango Controls

Development Partners

Argonne National Labs

Observatory Sciences

Observatory Sciences

GitHub Repository

https://github.com/epics-motor/

motorAutomation1

TBD

Open Source

Yes

Yes

Step-Scan Control

Yes

Yes

On-the-Fly Scanning Control

Yes (PSO)

Yes (PSO)

Backup & Restore Controller Data (MCD files)

Yes

Yes

Run Any Command via the Interface

Yes

Yes

Command, Control & Synchonize Axes

Yes

Yes

BUILT FOR SMALLER BEAM SIZES

The superior performance of Automation1 drive hardware, coupled with PSO control, makes Automation1 the natural choice

for beamline applications. Automation1 drives also contain large memory arrays and the capability to store—in real-time—the

feedback positions at each PSO firing event. This data is later downloaded and synchronized with experimental data. This

approach enables continuous scanning, optimizing experimental time and beamline profitability.

ETHERCAT + HYPERWIRE SUPPORT

Automation1 supports EtherCAT at the controller level, enabling the controller to be networked into larger controller architectures

—like the ones required to control light sources or telescopes. Motion control is still managed over the innovative HyperWire

motion bus, which operates at 100kHz, has 2 Gbps throughput and can manage up to 32* axes of servo control trajectories at 20

kHz. HyperWire also contains patented jitter reduction technology enabling <1 nanosecond of jitter for 16 axes of control, giving

you the best multi-axis synchronization in motion control.

BUILT-IN CLIENT:SERVER MODEL

Automation1 has a client:server model built into the controller. The controller is available to be deployed to a Linux-based servo

motor drive (which can network up to 12 axes of motion together) or to a Windows-based PC (which can network up to 32 axes of

motion). Each controller can be accessed remotely by any of the available Automation1 APIs.

*Note: EtherCAT connectivity is only available for drive-based controllers. Drive-based controllers can control a maximum of 12 axes. To control up to 32

axes you must use a PC-based controller. See Automation1-iSMC for more information.