TRIO MP-245 Quick Reference

Transcription

1 TRIO MP245 Quick Reference Rev ( ) (FW v2.4) Manual Operation TRIO / MP 245 YAxis Movement Configuration XAxis Movement ZAxis Movement Table 2. Configuration Switches 6 10 (Ver. <2.4) Sw # Definition State Setting Position 6 Sens Test** Enabled Off Up (see Caution) Disabled On* Down* 7 10 Reserved Off* Up* **CAUTION: To avoid damage to the micromanipulat stage, DIP Switch 6 (Sens Test) must always be set to OFF (DOWN). HOME: defined home position. Press again to pause/resume. WORK: defined wk position. Press again to pause/resume. PULSE: Advances diagonal axis in 2.85 μm steps. Hold 3sec. to enter ANGLE SET mode (active f 10 sec.) use Knob D to change angle (0 90 degrees). RELATIVE: Toggles between Relative and Absolute position moves. Hold 3sec. to set the relative mode igin to the current absolute position. SPEED: Cycles through Speed 0 (nmal) through 3. Hold 3 sec. to enter LOCK mode. Setting Home/Wk Pos., Relative Mode Origin Pos., & Angle: To set position, hold down HOME, WORK, & RELATIVE buttons f 3 seconds until beep sounds. Likewise, set angle with LOCK. Screencol mode indications: Green = Absolute position; Blue = Relative position; Red = Movement in progress in quiet (LOCK) mode; knobs disabled. Movement Knobs Disabling and Quiet (LOCK) Mode: Movement knobs are disabled during movement to Home, Wk, external movement command, while in quiet (LOCK) Mode. DAxis Movement (Synthetic); select angle in degrees when in ANGLE SET mode. Table 1. Configuration Switches 1 5. Sw # Definition State Setting Position 1 XAxis Knob Rotation f Clockwise Off* Up* YAxis Knob Rotation f Clockwise Off* Up* 2 ZAxis Knob Rotation f Clockwise Off* Up* 3 DAxis Knob Rotation f Clockwise Off* Up* 4 Y Axis Lock Out f Enabled Off Up 5 Homing Disabled On* Down* * Nmal operation (facty default). Table 3. Config. Switches 6 10 (Ver. 2.4) Sw # Definition State Setting Position 6 Calibration Homing on None Off Up Power On Calibrate On Down* Speed Select SPEED Select PULSE Off* Up* 7 button mode Pulse On Down Electromechanical device 1.5μm Off* Up* 8 whole step size Reserved On Down 9 25mm Off* Up* Xaxis travel length *** 50mm On Down 10 25mm Off* Up* Yaxis travel length: *** 12.5mm On Down ***CAUTION: To avoid possible equipment damage, always be certain that Switch 9 and 10 settings crectly match the physical length of travel of the X & Y axes on the connected device. COPYRIGHT 2019 SUTTER INSTRUMENT COMPANY. ALL RIGHTS RESERVED. TRIO IS A TRADEMARK OF SUTTER INSTRUMENT COMPANY.

2 2 External Control Controlling the TRIO MP245 externally via computer is accomplished by sending commands over the USB interface between the computer and the USB connect on the rear panel of the TRIO MP245 controller/roe. The USB device driver f Windows is downloadable from Sutter Instrument s web site ( The TRIO MP245 requires USB CDM (Combined Driver Model) Version higher. The CDM device driver f the TRIO MP245 consists of two device drivers: 1) USB device driver, and 2) VCP (Virtual COM Pt) device driver. Install the USB device driver first, followed by the VCP device driver. The VCP device driver provides a serial RS232 I/O interface between a Windows application and the TRIO MP245. Although the VCP device driver is optional, its installation is recommended even if it is not going to be used. Once installed, the VCP can be enabled disabled. The CDM device driver package provides two I/O methodologies over which communications with the controller over USB can be conducted: 1) USB Direct (D2XX mode), 2) Serial RS232 asynchronous via the VCP device driver (VCP mode). The first method requires that the VCP device driver not be installed, if installed, that it be disabled. The second method requires that the VCP be installed and enabled. Virtual COM Pt (VCP) Serial Pt Settings: The following table lists the required RS232 serial settings f the COM pt (COM3, COM5, etc.) generated by the installation enabling of the VCP device driver. Table 4. USBVCP interface serial pt settings. Property Setting Data ( Baud ) Rate (bits per second (bps)) Data Bits 8 Stop Bits 1 Parity None Flow Control None The settings shown in the above table can be set in the device driver s properties (via the Device Manager if in Windows) and/ programmatically in your application. Protocol and Handshaking: Command sequences do not have terminats. All commands return an ASCII CR (Carriage Return; 13 decimal, 0D hexadecimal) to indicate that the task associated with the command has completed. When the controller completes the task associated with a command, it sends ASCII CR back to the host computer indicating that it is ready to receive a new command. If a command returns data, the last byte returned is the taskcompleted indicat. Command Sequence Fmatting: Each command sequence consists of at least one byte, the first of which is the command byte. Those commands that have parameters arguments require a sequence of bytes that follow the command byte. No delimiters are used between command sequence arguments, and command sequence terminats are not used. Although most command bytes can be expressed as ASCII displayable/printable characters, the rest of a command sequence must generally be expressed as a sequence of unsigned byte values (0 255 decimal; 00 FF hexadecimal, binary). Each byte in a command sequence being transmitted to the controller must contain an unsigned binary value. Attempting to code command sequences as strings is not advisable. Any command data being returned from the controller must also be received and initially treated as a sequence of unsigned byte values. Groups of contiguous bytes can later be combined to fm larger values, as appropriate (e.g., 2 bytes into 16bit wd, 4 bytes into a 32bit long double wd ). F the TRIO MP245, all axis position values (number of microsteps) are sted as unsigned long (32bit) values, and each is transmitted and received to and from the controller as four contiguous bytes. Axis Position Command Parameters: All axis positional infmation is exchanged between the controller and the host computer in terms of microsteps. Conversion between microsteps and microns (micrometers) is the responsibility of the software running on the host computer. The number of microsteps f any axis position must always be exchanged between the controller and the application running on an external computer as an unsigned 32bit value ( unsigned long f C/C++ U32 f LabVIEW). Unsigned means the value is always positive; negative values are not allowed. An unsigned long U32 consists of four contiguous bytes, with a byte/bitdering fmat of Little Endian ( Intel ) (most significant byte (MSB) in the first byte and least significant (LSB) in the last byte). If the platfm on which your application is running is Little Endian, then no byte der reversal of axis position values is necessary. Examples of platfms using Little Endian fmatting include any system using an Intel process (including Microsoft Windows and Apple Mac OS X). If the platfm on which your application is running is Big Endian (e.g., Motola PowerPC CPU), then these 32bit position values must have their bytes reversedered after receiving from, befe sending to, the controller. Examples of Big Endian platfms include many nonintelbased systems, Lab VIEW (regardless of operating system & CPU), and Java (programming language/environment). MATLAB adapts to the system on which it is run

3 ning, so Little Endian may need to be enfced if running on a Big Endian system. Microsteps and Microns (Micrometers): All codinates sent to and received from the controller are in microsteps. To convert between microsteps and microns (micrometers), use the following conversion facts (multipliers): Table 5. Microns/microsteps conversion. System/Device From/To Units Conversion Fact (multiplier) TRIO MP245 with TRIO MP245/M μsteps μm micromanipulat μm μsteps Table 7. TRIO MP245 external control commands. F accuracy in your application, these conversion facts should be typed as double precision ( double ); float is not recommended. If the result is in microsteps, it can be typed as a 32bit long integer; otherwise, it should be typed as floating point, preferably as double precision ( double ). Table 6. Ranges Device Axis Length Microns Microsteps TRIO MP245/M X, Y, & Z 25mm 0 25, ,667 With long X X 50mm 0 50, ,334 With sht Y Y 12.5mm 0 12, ,334 Command Reference: The following table lists all the externalcontrol commands f the TRIO MP Command Tx/ Delay/ Rx Ver. Total Bytes Byte Offset (Len.) Value Dec. Hex. Binary Altkeypad # Ctrlchar ASCII def./ char. Description Get Current Position and Angle ( c C ) HOME Position ( h ) WORK Position ( w ) Tx All c C Returns the current positions (μsteps) of X, Y, & Z axes and angle setting (degrees). Rx. All 14 Three 4byte (32bit) values (current positions in μsteps of X, Y, & Z), + 1 byte f angle, + 1 byte f completion indicat. See Ranges table f minimum and maximum values. 0 (4) X pos. in μsteps 4 (4) Y pos. in μsteps 8 (4) Z pos. in μsteps 12 Angle in degrees D ^M <CR> Completion indicat Tx All h Moves to the position saved f the controller s HOME button. Rx All D <CR> Completion indicat Tx All w Moves to the position saved f the controller s WORK button. Rx All D <CR> Completion indicat Specified Home Position ( H ) Tx All (4) H Move all 3 axes to specified position, moving Z befe X & Y together (see Ranges table) X μsteps 5 (4) Y μsteps 9 (4) Z μsteps Rx All D ^M <CR> Completion indicat Specified Wk Position ( W ) Tx All (4) W Move all 3 axes to specified position, moving X & Y together first, and then Z (see Ranges table) X μsteps 5 (4) Y μsteps 9 (4) Z μsteps Rx All D ^M <CR> Completion indicat

4 4 Command Tx/ Delay/ Rx Ver. Total Bytes Byte Offset (Len.) Value Dec. Hex. Binary Ctrlchar Altkeypad # ASCII def./ char. Description Move in Straight Line to Specified Position at Specified Speed ( S ) Tx All S Move all three axes in a straight line to specified position (see Ranges table) F ^O ^@ 2 (4) X μsteps 6 (4) Y μsteps 10(4) Z μsteps Speed (15 0 (fastest through slowest)) Rx All D ^M <CR> Completion indicat Interrupt StraightLine Move (^C) Tx All ^C <ETX> Interrupts a move in progress (only f moves initiated by the Straightline move ( S ) command) Rx All D <CR> Completion indicat specified X axis Tx All x Move X axis to specified position (see Ranges table) 90 5A X Position ( x X ) 1 (4) X μsteps Rx All D <CR> Completion indicat specified Y axis Tx All y Move Y axis to specified position (see Ranges table) 91 5B Y Position ( y Y ) 1 (4) Y μsteps Rx All D <CR> Completion indicat specified Z axis Tx All A z Move Zaxis to specified position (see Ranges table) 92 5C Z Position ( z Z ) 1 (4) Z μsteps Rx All D <CR> Completion indicat Enter Angle ( A ) Tx All A Sets the angle value, in degrees, to match the angle position of the rotary dovetail A <NUL> Angle in degrees between 0 and 90. z Rx All D <CR> Completion indicat NOTES: 1. All positions sent to and received from the controller are in microsteps. See Microns/microsteps conversion f conversion between microns (micrometers (μm)) and microsteps (μsteps). 2. See Ranges f exact minimum and maximum values f each axis of each compatible device that can be connected. 3. A sht delay (usually around 2 ms) is recommended between commands (after the reception of one command and the sending of the next command). 4. All positions sent and received to and from the controller are in microsteps and consist of 32bit positive integer values (four contiguous bytes). F C/C++, these are typed as unsigned long ; U32 f LabVIEW. Although a signed type might be desirable f computation and compatibility purposes, the application must ensure that only unsigned longs U32 values are sent to, and received from, the controller (i.e., no negative values). 5. All 32bit position values transmitted to, and received from, the controller must be bit/bytedered in Little Endian fmat. This means that the least significant bit/byte is last (last to send and last to receive). Byteder reversal may be required on some platfms. Microsoft Windows, Intelbased Apple Macintosh systems running Mac OS X, and some Intel/AMD process based Linux distributions handle byte stage in LittleEndian byte der so byte redering is not necessary befe converting to/from 32bit long values. Lab VIEW always handles byte strings in Big Endian byte der irrespective of operating system and CPU, requiring that the four bytes containing a microsteps value be reversedered befe/after conversion to/from a multibyte type value (I32, U32, etc.). MATLAB automatically adjusts the endianess of multibyte stage entities to that of the system on which it

5 5 is running, so explicit byte redering is generally unnecessary unless the underlying platfm is Big Endian. If your development platfm does not have builtin Little/Big Endian conversion functions, bit redering can be accomplished by first swapping positions of the two bytes in each 16bit half of the 32bit value, and then swap positions of the two halves. This method efficiently and quickly changes the bit dering of any multibyte value between the two Endian fmats (if Big Endian, it becomes Little Endian, and if Little Endian, it becomes then Big Endian). 6. Move commands might have sht to long distances of travel. If not polling f return data, an appropriate delay should be inserted between the sending of the command sequence and reception of return data so that the next command is sent only after the move is complete. This delay can be autocalculated by determining the distance of travel (difference between current and target positions) and rate of travel. This delay is not needed if polling f return data. In either case, however, an appropriate timeout must be set f the reception of data so that the I/O does not time out befe the move is made and/ the delay expires. 7. Actual speed f the StraightLine Move S command can be determined with the following fmula: (5000 / 16) * (sp +1), where 5000 is the maximum speed in microns/second and sp is the speed level 0 (slowest) through 15 (fastest). F mm/second microns/millisecond, multiply result by NOTES:

6 6 NOTES: