Sutter Instrument TRIO MPC-165 Series, Руководство по эксплуатации

Страница: 51 / 60

TRIO MPC-165 SERIES MICROMANIPULATOR SYSTEM OPERATION MANUAL – REV. 2.67K2 (20201130) (FW V2.62)
49
the platform on which your application is running is
Little Endian, then no byte order reversal of axis
position values is necessary. Examples of platforms
using Little Endian formatting include any system
using an Intel/AMD processor (including Microsoft
Windows and Apple Mac OS X).
If the platform on which your application is running
is Big Endian (e.g., Motorola PowerPC CPU), then
these 32-bit position values must have their bytes
reverse-ordered after receiving from, or before
sending to, the controller. Examples of Big-Endian
platforms include many non-Intel-based systems,
LabVIEW (regardless of operating system & CPU),
and Java (programming language/environment).
MATLAB and Python (script programming
language) are examples of environments that adapt
to the system on which each is running, so Little-
Endian enforcement may be needed if running on a
Big-Endian system. Some processors (e.g., ARM) can
be configured for specific endianess.
Microsteps and Microns (Micrometers): All
coordinates sent to and received from the controller
are in microsteps. To convert between microsteps
and microns (micrometers), use the following
conversion factors (multipliers):
Table
D-3
. Microns/microsteps conversion.
TRIO MPC-100 Controller
with Device
From/To
Units
Conversion Factor
(multiplier)
MP-865/M* micromanipulator
µsteps

µm 0.09375
µm

µsteps 10.66666666667
MP-285/M**
micromanipulator
µsteps

µm 0.125
µm

µsteps 8
* The same applies also to the MP-845[S]/M and MP-245/M
(discontinued) with DB25 to DB26HD adapter.
** The same applies also to the 3DMS or MT-78 stage, MOM or
SOM objective mover, and MP-265/M micromanipulator
(discontinued).
For accuracy in your application, type these
conversion factors as “double” (avoid using the
“float” type as it lacks precision with large values).
When converting to microsteps, type the result as a
32-bit “unsigned long” (C/C++), “uint32”
(MATLAB), or “U32” (LabVIEW) integer (positive
only) value. When converting to microns, type the
result as a “double” (C/C++, MATLAB) or “DBL”
(LabVIEW) 64-bit double-precision floating-point
value.
Table D-4. Ranges and bounds.
Device Axis Len.
(mm)
Origin Microns
(Micromet
ers (µm))
Microsteps
(µsteps)
MP-865/M
micromanipulator
X 50 BOT 0 – 50,000 0 – 533,333
Y 12.5 BOT 0 – 12,500 0 – 133,333
Z 25 BOT 0 – 25,000 0 – 266,667
MP-845[S]/M *
micromanipulator X, Y,
Z
25 BOT 0 – 25,000 0 – 266,667
MP-285/M**
micromanipulator X, Y,
Z
25 BOT 0 – 25,000 0 – 200,000
* The same applies also to the MP-245/M micromanipulator
(discontinued) with DB25 to DB26HD adapter.
** The same applies also to the 3DMS & MT-78 stages, and MOM
& SOM objective movers, and MP-265/M micromanipulator
(discontinued) with 12.5mm for Y axis,
NOTE: Origin is a physical position of travel that defines the
center of the absolute position coordinate system (i.e., absolute
position 0).
Physical Positions: BOT (Beginning Of Travel), COT (Center Of
Travel), & EOT (End Of Travel).
In the TRIO MPC-100, the Origin is fixed at BOT.
NOTE: Travel length of each axis is automatically determined by
end-of-travel sensor.
Travel Speed: The following table shows the travel
speeds for supported devices using orthogonal move
commands.
Table
D-5
.
Travel speeds.
Device
mm/sec or µm/ms
Single
Axis
Dual Axis
(x 1.4)
MP-865/M * micromanipulator 3 4.2
MP-285/M ** micromanipulator 5 7
* The same applies also to the MP-845[S]/M & MP-245/M
(discontinued) micromanipulators.
** The same applies also to the 3DMS & MPC-78 stages, and
SOM & MOM objective movers, MP-265/M micromanipulator
(discontinued).
Command Reference: The following table lists all
the external-control commands for the TRIO MPC-
100.