Note

General stage communication concepts are described on the corresponding page

Thorlabs APT/Kinesis devices

Thorlabs has a variety of APT/Kinesis devices for various motion-related functionality (mostly motor controllers and piezo drivers), which share the same API. The library uses an older and more low-level APT protocol to communicate with these devices. So far it has been only implemented for motor controllers and some specialized devices and tested with KDC101 and K10CR1 motor controllers, KIM101 piezo motor controller, and TPA101 quadrature sensor controller.

The main device classes are pylablib.devices.Thorlabs.BasicKinesisDevice for a generic Kinesis/APT devices pylablib.devices.Thorlabs.KinesisMotor aimed at motor controllers such as K10CR1 or KDC101, and pylablib.devices.Thorlabs.KinesisPiezoMotor for piezo drivers such as KIM and TIM.

Software requirements

The connection is done using Thorlabs APT protocol, so it needs the corresponding APT drivers. Pylablib communicates directly with the FTDI USB-to-RS232 using pyft232 chip inside the controller, so it bypasses most of the Thorlabs software. This means that it does not need any Thorlabs-supplied DLLs, but it also means that it can not work with the simulated devices, since these are simulated on a level above the direct serial communication.

In some cases pyft232 library can not find the required ftd2xx.dll library, which leads to an error. There are several ways to get around this. First, you can install the FTDI drivers from the manufacturer’s website. Setup executable for Windows automatically places the necessary DLL into the System32 folder, where pyft232 can discover them. Alternatively, you can copy the DLLs there yourself from the Thorlabs APT installation. Their default location is Program Files\Thorlabs\APT\Drivers\APT\USB Driver\amd64 for 64-bit version or Program Files\Thorlabs\APT\Drivers\APT\USB Driver\i386 for 32-bit version. Note that in the first case the file is called ftd2xx64.dll, and you will need to rename it to ftd2xx.dll when copying to the System32 folder.

Connection

The devices are identified by their address, which correspond to their serial numbers. To get the list of all the connected devices, you can use Thorlabs.list_kinesis_devices:

>> from pylablib.devices import Thorlabs
>> Thorlabs.list_kinesis_devices()
[('27500001', 'Kinesis K-Cube  DC Driver')]
>> stage = Thorlabs.KinesisMotor("27500001")
>> stage.close()

Operation

Standard motors

This controller has several features and differences compared to most other stages and sliders:

  • There are several different ways to specify the stage calibration, which are controlled by the scale parameter supplied upon the connection. By default (scale = "step"), it accepts and returns position in motor steps, velocity in steps/s and acceleration in steps/s^2 (scaling coefficients for the latter two are determined from the controller model). If scale = "stage", the class attempts to autodetect the stage and use meters or degrees instead of steps; in addition you can supply the stage name (e.g., "MTS25-Z8") as a scale instead of relying on the autodetection. If there is no calibration for the stage that you have, you can instead supply a single scaling factor, which specifies the number of steps per physical unit (e.g., for "MTS25-Z8" stage and mm units, one would supply scale = 34304). The stage scaling can be obtained from the APT manual. Finally, one can supply a 3-tuple of scales for position, velocity and acceleration (all relative to the internal units). The details are given in the APT manual. To ensure that the units have been applied and/or autodetected correctly, you can use KinesisMotor.get_scale(), KinesisMotor.get_scale_units() and KinesisMotor.get_stage() methods.
  • By default, the controllers are treated as single-axis. If several axes are supported, they can be specified using channel argument.
  • The motor power-up parameters for homing, jogging, limit switches, etc., can be different from the parameters showing up in the APT/Kinesis controller. This can lead to problems if, e.g., homing speed is too low, so the motor appears stationary while homing. You should make sure to check those parameters using KinesisMotor.get_velocity_parameters(), KinesisMotor.get_jog_parameters(), KinesisMotor.get_homing_parameters(), KinesisMotor.get_gen_move_parameters(), and KinesisMotor.get_limit_switch_parameters().

Piezo motors

This controller has several features and differences compared to most other stages and sliders:

  • The controllers are treated as multi-axis. However, to be compatible with other Kinesis motor, the channel argument is not required, and it defaults to the currently selected “default” channel (1 in the beginning). To control different channels, you can either supply channel argument explicitly, or specify a different default channel using KinesisPiezoMotor.set_default_channel() or KinesisPiezoMotor.using_channel().
  • The motor power-up parameters for jogging and drive can be different from the parameters showing up in the APT/Kinesis controller. This can lead to problems if, e.g., speed is too low. You should make sure to check those parameters using KinesisPiezoMotor.get_drive_parameters() and KinesisPiezoMotor.get_jog_parameters().
  • Even open-loop controllers support absolute positioning, which is achieved simply by counting steps in both directions. However, unlike stepper motors or encoders, these steps can be different depending on the direction, position, instantaneous load, speed, etc. Hence, the absolute positions quickly become unreliable. It is, therefore, recommended to generally use relative positioning using KinesisPiezoMotor.move_by() method.

Quadrature detector

These are fairly different from the other discussed devices, since they are more related to sensors than to motors. This controller takes signal from a quadrature photodetector and implements a PI control loop to feed back to some control device (e.g., a piezo driver or a galvo mirror). Hence, all of its methods are fairly distinct from the usual motors. Nevertheless, it is described here, since it still belongs to the APT/Kinesis family of devices and shares their detection and connection approach. The device is implemented in the pylablib.devices.Thorlabs.KinesisQuadDetector class.

The operation is fairly straightforward: it implements control of PID parameters, output parameters (such as limits), operation mode (open/close loop), allows for reading current state and setting outputs in the open-loop mode.