Delta Tau Geo Brick Drive Reference Manual 773825
Delta Tau Geo Brick Drive Reference Manual 773825
^2 Turbo PMAC/PMAC2
^4 3Ax-01.937-xSxx
DELTA TAU
Data Systems, Inc.
NEW IDEAS IN MOTION …
Copyright Information
© 2014 Delta Tau Data Systems, Inc. All rights reserved.
This document is furnished for the customers of Delta Tau Data Systems, Inc. Other uses
are unauthorized without written permission of Delta Tau Data Systems, Inc.
Information contained in this manual may be updated from time-to-time due to product
improvements, etc., and may not conform in every respect to former issues.
To report errors or inconsistencies, call or email:
Delta Tau Data Systems, Inc. Technical Support
Phone: (818) 717-5656
Fax: (818) 998-7807
Email: support@deltatau.com
Website: http://www.deltatau.com
Operating Conditions
All Delta Tau Data Systems, Inc. motion controller products, accessories, and amplifiers
contain static sensitive components that can be damaged by incorrect handling. When
installing or handling Delta Tau Data Systems, Inc. products, avoid contact with highly
insulated materials. Only qualified personnel should be allowed to handle this
equipment.
REVISION HISTORY
REV. DESCRIPTION DATE CHG APPVD
1 REVISION TO Ixx97 ERROR DESCRIPTION 08/29/06 CP P. SHANTZ
2 REVISION TO IXX83 VARIABLES, P. 188 10/10/06 CP S. SATTARI
3 REV. IXX25 & IXX42 PMAC2 VARIABLES, P. 149 & 159 04/25/07 CP S. SATTARI
B.
4 LOOKAHEAD WARNING TO ISX21(P.220) & \ (P.308) 05/30/07 CP
PEDERSEN
5 REV. TO IXX02 PULSE FREQ. SETTINGS, P. 127 10/19/07 CP C. WILSON
C. WILSON
6 REV. TO IXX24 BIT 16 SETTINGS, P. 145 12/04/07 CP M.
ESPOSITO
7 CORRECTION TO ISX99 DEFAULT SETTING, P. 227 01/04/08 CP M.ESPOSITO
CORRECTED COORDINATE SYSTEM STATUS BITS FOR
8 “CONTINUOUS MOTION REQUEST” 11/25/08 CP R.NADDAF
M-VARIABLE DEFS., PP. 619-627, 685-692, 751-758
9 INCORPORATED V1.941-45 FIRMWARE UPDATES 12/08/09 CP C. WILSON
10 CORRECTED ERRORS P. 97 AND P. 592 01/05/10 CP S. MILICI
INCORPORATED V1.946-47 FIRMWARE UPDATES
11 ADDED TO I43 DESCRIPTION 12/19/12 CW C. WILSON
FIXED TYPOGRAPHICAL ERRORS
FIXED VARIOUS TYPOGRAPHICAL ERRORS
12 02/24/14 DCDP C. WILSON
MISC. FORMATTING
Turbo PMAC/PMAC2 Software Reference
Table of Contents
INTRODUCTION ................................................................................................................... 21
What is Turbo PMAC? .............................................................................................................. 21
What is New about Turbo PMAC? ............................................................................................ 21
How do I Convert a PMAC Application? .................................................................................. 22
How do I use this Manual? ........................................................................................................ 22
Table of Contents v
Turbo PMAC/PMAC2 Software Reference
Table of Contents vi
Turbo PMAC/PMAC2 Software Reference
Table of Contents ix
Turbo PMAC/PMAC2 Software Reference
Isx85 Coordinate System ‘x’ Corner Dwell Break Point ...................................................................... 186
Isx86 Coordinate System x Alternate Feedrate .................................................................................... 187
Isx87 Coordinate System x Default Program Acceleration Time .......................................................... 188
Isx88 Coordinate System x Default Program S-Curve Time ................................................................. 188
Isx89 Coordinate System x Default Program Feedrate/Move Time ...................................................... 189
Isx90 Coordinate System x Feedrate Time Units.................................................................................. 189
Isx91 Coordinate System x Default Working Program Number ............................................................ 189
Isx92 Coordinate System ‘x’ Move Blend Disable................................................................................ 190
Isx93 Coordinate System x Time Base Control Address ....................................................................... 190
Isx94 Coordinate System x Time Base Slew Rate ................................................................................. 191
Isx95 Coordinate System x Feed Hold Slew Rate ................................................................................. 191
Isx96 Coordinate System x Circle Error Limit ..................................................................................... 191
Isx97 Coordinate System x Minimum Arc Length................................................................................. 192
Isx98 Coordinate System x Maximum Feedrate ................................................................................... 193
Isx99 Coordinate System x Cutter-Comp Outside Corner Break Point ................................................. 193
Turbo PMAC2 MACRO IC I-Variables .................................................................................. 194
I6800/I6850/I6900/I6950 MACRO IC MaxPhase/PWM Frequency Control .......................................... 194
I6801/I6851/I6901/I6951 MACRO IC Phase Clock Frequency Control ................................................. 196
I6802/I6852/I6902/I6952 MACRO IC Servo Clock Frequency Control .................................................. 196
I6803/I6853/I6903/I6953 MACRO IC Hardware Clock Control ............................................................ 198
I6804/I6854/I6904/I6954 MACRO IC PWM Deadtime / PFM Pulse Width Control ............................... 200
I6805/I6855/I6905/I6955 MACRO IC DAC Strobe Word ...................................................................... 200
I6806/I6856/I6906/I6956 MACRO IC ADC Strobe Word ...................................................................... 201
I6807/I6857/I6907/I6957 MACRO IC Clock Direction Control ............................................................. 201
Channel-Specific MACRO IC I-variables............................................................................ 202
I68n0/I69n0 MACRO IC Channel n* Encoder/Timer Decode Control ................................................... 203
I68n1/I69n1 MACRO IC Channel n* Position Compare Channel Select ................................................ 204
I68n2/I69n2 MACRO IC Encoder n* Capture Control .......................................................................... 204
I68n3/I69n3 MACRO IC Channel n* Capture Flag Select Control ........................................................ 205
I68n4/I69n4 MACRO IC Channel n* Encoder Gated Index Select ......................................................... 206
I68n5/I69n5 MACRO IC Channel n* Encoder Index Gate State/Demux Control .................................... 207
I68n6/I69n6 MACRO IC Channel n* Output Mode Select ..................................................................... 208
I68n7/I69n7 MACRO IC Channel n* Output Invert Control .................................................................. 208
I68n8/I69n8 MACRO IC Channel n* PFM Direction Signal Invert Control........................................... 209
I68n9/I69n9 Reserved for Future Use ................................................................................................... 209
MACRO IC Ring Setup I-variables ..................................................................................... 210
I6840/I6890/I6940/I6990 MACRO IC Ring Configuration/Status .......................................................... 210
I6841/I6891/I6941/I6991 MACRO IC Node Activate Control ................................................................ 211
Servo IC I-Variables ............................................................................................................... 212
PMAC2-Style Multi-Channel Servo IC I-Variables ............................................................. 213
I7m00 Servo IC m MaxPhase/PWM Frequency Control ....................................................................... 213
I7m01 Servo IC m Phase Clock Frequency Control ............................................................................. 215
I7m02 Servo IC m Servo Clock Frequency Control .............................................................................. 215
I7m03 Servo IC m Hardware Clock Control ........................................................................................ 217
I7m04 Servo IC m PWM Deadtime / PFM Pulse Width Control ........................................................... 218
I7m05 Servo IC m DAC Strobe Word................................................................................................... 219
I7m06 Servo IC m ADC Strobe Word................................................................................................... 219
I7m07 Servo IC m Phase/Servo Clock Direction .................................................................................. 220
PMAC2-Style Channel-Specific Servo IC I-Variables ......................................................... 221
I7mn0 Servo IC m Channel n Encoder/Timer Decode Control.............................................................. 221
Table of Contents x
Turbo PMAC/PMAC2 Software Reference
Table of Contents xi
Turbo PMAC/PMAC2 Software Reference
$$$.......................................................................................................................................................... 273
$$$*** .................................................................................................................................................... 273
$$*.......................................................................................................................................................... 274
$*............................................................................................................................................................ 274
% ............................................................................................................................................................ 275
%{constant} ............................................................................................................................................ 276
& ............................................................................................................................................................ 276
&{constant}............................................................................................................................................. 277
\ .............................................................................................................................................................. 278
< ............................................................................................................................................................. 278
> ............................................................................................................................................................. 279
/ .............................................................................................................................................................. 279
? ............................................................................................................................................................. 280
??............................................................................................................................................................ 284
???.......................................................................................................................................................... 289
A ............................................................................................................................................................. 291
ABR[{constant}]...................................................................................................................................... 292
ABS ......................................................................................................................................................... 293
{axis}={constant} .................................................................................................................................... 294
B{constant} ............................................................................................................................................. 295
CHECKSUM ........................................................................................................................................... 295
CID ......................................................................................................................................................... 296
CLEAR .................................................................................................................................................... 296
CLEAR ALL ............................................................................................................................................ 297
CLEAR ALL PLCS................................................................................................................................... 297
CLOSE .................................................................................................................................................... 297
CLOSE ALL ............................................................................................................................................ 298
CLRF ...................................................................................................................................................... 299
{constant}................................................................................................................................................ 299
CPU ........................................................................................................................................................ 300
DATE ...................................................................................................................................................... 300
DEFINE BLCOMP .................................................................................................................................. 300
DEFINE CCBUF..................................................................................................................................... 301
DEFINE COMP (one-dimensional).......................................................................................................... 302
DEFINE COMP (two-dimensional).......................................................................................................... 303
DEFINE GATHER .................................................................................................................................. 307
DEFINE LOOKAHEAD .......................................................................................................................... 307
DEFINE ROTARY ................................................................................................................................... 309
DEFINE TBUF ....................................................................................................................................... 310
DEFINE TCOMP .................................................................................................................................... 310
DEFINE UBUFFER [modified description]......................................................................................... 311
DELETE ALL .......................................................................................................................................... 312
DELETE ALL TEMPS ............................................................................................................................. 313
DELETE BLCOMP ................................................................................................................................. 313
DELETE CCUBUF ................................................................................................................................. 314
DELETE COMP ...................................................................................................................................... 314
DELETE LOOKAHEAD .......................................................................................................................... 314
DELETE GATHER .................................................................................................................................. 315
DELETE PLCC ....................................................................................................................................... 316
DELETE ROTARY................................................................................................................................... 316
DELETE TBUF ....................................................................................................................................... 317
P{data}={expression}.............................................................................................................................. 383
PASSWORD={string}.............................................................................................................................. 384
PAUSE PLC ............................................................................................................................................ 385
PC........................................................................................................................................................... 386
PE ........................................................................................................................................................... 387
PMATCH ................................................................................................................................................ 387
PR ........................................................................................................................................................... 388
Q............................................................................................................................................................. 388
Q{constant} ............................................................................................................................................. 389
Q{data}={expression} ............................................................................................................................. 389
R ............................................................................................................................................................. 391
R[H]{address}......................................................................................................................................... 391
RESUME PLC ......................................................................................................................................... 392
S ............................................................................................................................................................. 393
SAVE....................................................................................................................................................... 394
SETPHASE ............................................................................................................................................. 395
SID ......................................................................................................................................................... 395
SIZE ........................................................................................................................................................ 396
STN ......................................................................................................................................................... 396
STN={constant} ...................................................................................................................................... 397
TIME....................................................................................................................................................... 397
TIME={time} .......................................................................................................................................... 397
TODAY ................................................................................................................................................... 398
TODAY={date} ....................................................................................................................................... 399
TYPE....................................................................................................................................................... 399
UNDEFINE............................................................................................................................................. 400
UNDEFINE ALL ..................................................................................................................................... 400
UNLOCK{constant} ................................................................................................................................ 401
UPDATE ................................................................................................................................................. 401
V ............................................................................................................................................................. 401
VERSION ................................................................................................................................................ 402
VID ......................................................................................................................................................... 402
W{address} ............................................................................................................................................. 403
Z ............................................................................................................................................................. 403
Table of Contents xv
Turbo PMAC/PMAC2 Software Reference
- .............................................................................................................................................................. 486
* ............................................................................................................................................................. 486
/ .............................................................................................................................................................. 486
% ............................................................................................................................................................ 487
& ............................................................................................................................................................ 488
| .............................................................................................................................................................. 488
^ .............................................................................................................................................................. 489
Mathematical Functions .......................................................................................................... 489
ABS ......................................................................................................................................................... 489
ACOS ...................................................................................................................................................... 489
ASIN ....................................................................................................................................................... 490
ATAN ...................................................................................................................................................... 490
ATAN2 .................................................................................................................................................... 491
COS ........................................................................................................................................................ 492
EXP ........................................................................................................................................................ 492
INT ......................................................................................................................................................... 492
LN ........................................................................................................................................................... 493
SIN.......................................................................................................................................................... 493
SQRT ...................................................................................................................................................... 494
TAN ........................................................................................................................................................ 494
Table of Contents xx
Turbo PMAC/PMAC2 Software Reference
INTRODUCTION
What is Turbo PMAC?
The Turbo PMAC is the newest addition to the renowned PMAC family of motion controllers. The
Turbo refers to a new high-performance CPU section that can be used with existing PMAC or PMAC2
interface circuitry to turbo-charge the application.
The Turbo PMAC is currently available in six versions:
Turbo PMAC PC: PMAC servo interface circuitry, PC (ISA) bus interface
Turbo PMAC VME PMAC servo interface circuitry, VME bus interface
Turbo PMAC2 PC PMAC2 servo interface circuitry, PC (ISA) bus interface
Turbo PMAC2 VME PMAC2 servo interface circuitry, VME bus interface
Turbo PMAC2 PC Ultralite MACRO servo interface circuitry, PC(ISA) bus interface
Turbo PMAC2 3U (UMAC Turbo and 3U Turbo Stack)
PMAC2 servo interface circuitry, PC/104 bus interface
Each of these versions has its own Hardware Reference manual.
More versions will be available in the near future.
What is New about Turbo PMAC?
The Turbo PMAC uses the increased speed and memory of the newest generation of digital signal
processing (DSP) ICs to enhance the capabilities of the PMAC family. The Turbo PMAC has the
software capability to control 32 axes in 16 independent coordinate systems, up from eight axes in eight
coordinate systems for the standard PMAC.
Many users will find the Turbo PMAC a very powerful and cost-effective solution when controlling large
numbers of axes. Remember that a PMAC board itself has at most eight servo interface channels; the
actual control of more than eight physical axes will require the use of either Acc-24 family axis expansion
boards, or remote interface circuitry on the MACRO ring.
The extra software axis capability can be useful for virtual axes which do not require (full) physical
hardware interface circuitry. Virtual axes have many important uses, including:
Phantom coordinate systems in tool tip coordinates for inverse kinematics
Virtual masters to replace mechanical line-shaft masters
Redundant axes for error checking and recovery purposes
Cascaded servo loops for hybrid control techniques (e.g. force and position)
Many other users will find the Turbo PMAC valuable even if less than eight axes are used, just because of
the additional computational speed. The DSP of the base version of the Turbo PMAC runs at 80 MHz,
but because operations on internal registers (about half of all operations) run in one clock cycle instead of
the two clock cycles required for the standard PMAC, performance is equivalent to that of a 120 MHz
standard PMAC.
The additional memory addressing capability of the Turbo PMAC permits the use of more axes and
coordinate systems, and more features for it. It also supports more variables, and (optionally) much larger
user buffer spaces.
Introduction 21
Turbo PMAC/PMAC2 Software Reference
With the additional speed and memory, new features are possible on the Turbo PMAC. The most
important of these are:
Multi-block lookahead for acceleration control
Built-in inverse-kinematic and forward-kinematic capability
Three-dimensional cutter-radius compensation
Altered destination of moves on the fly
Simultaneous communications over multiple ports
Individual custom commutation sine tables for each motor
Individual selection by motor of PID or extended servo algorithm
Significantly enlarged synchronous M-variable buffer
2 dedicated user servo-rate timers per coordinate system
Trajectory reversal capability
Introduction 22
Turbo PMAC/PMAC2 Software Reference
Definitions
constant -- numerically specified non-changing value
variable -- entity that holds a changeable value
I-variable -- variable of fixed meaning for card setup and personality (1 of 8192)
P-variable -- global variable for programming use (1 of 8192)
Q-variable -- local variable (in coordinate system) for programming use (1 of 8192)
M-variable -- variable assigned to memory location for user use (1 of 8192)
pre-defined variable -- mnemonic that has fixed meaning in card
function -- SIN, COS,TAN,ASIN,ACOS,ATAN,ATAN2,LN,EXP,SQRT,ABS,INT
operator -- for arithmetic or bit-by-bit logical combination of two values: +, -, *, /, % (mod), &
(and), | (or), ^ (xor)
expression -- grouping of constants, variables, functions, and operators
data -- constant without parentheses, or expression with parentheses
comparator -- evaluates relationship between two values: =, !=, >, !>, <, !<, ~, !~
condition -- evaluates as true or false based on comparators
simple condition -- {expression} {comparator} {expression}
compound condition -- logical combination of simple conditions
motor -- element of control for hardware setup; specified by number
coordinate system -- collections of motors working synchronously
axis -- element of a coordinate system; specified by letter chosen from X, Y, Z, A, B, C, U, V, W
buffer -- space in user memory for program or list; contains up to 256 motion programs and 32 PLC
blocks
On-Line Commands
(Executed immediately upon receipt by PMAC)
On-line Global Commands
Addressing Mode Commands
@n – Address card n (n is hex digit 0 to f); serial host only
@ – Report currently addressed card to host; serial host only
#n – Make motor n currently addressed motor
# – Report currently addressed motor number to host
##n – Select motor group of 8 for multi-motor responses
## - Report selected motor group of 8
&n – Make coordinate system n the currently addressed coordinate system
& – Report currently addressed coordinate system to host
Communications Control-Characters
<CTRL-H> – Erase last character from host (backspace)
<CTRL-I> – Repeat last command from host (tab)
<CTRL-M> – End of command line (carriage return)
<CTRL-N> – Report checksum of current command line
<CTRL-T> – End MACRO ASCII pass through mode
<CTRL-X> – Abort current PMAC command and response strings
Jogging Commands
J+ – Jog motor indefinitely in positive direction
J- – Jog motor indefinitely in negative direction
J/ – Stop jogging motor; also restore to position control
J= – Jog motor to last pre-jog or pre-handwheel position
J={constant} – Jog motor to specified position
J=* – variable jog-to-position
J:{constant} – Jog motor specified distance from current commanded position
J:* – Variable incremental jog from current commanded position
J^{constant} – Jog motor specified distance from current actual position
J^* – Variable incremental jog from current actual position
{jog command}^{constant} – Jog until trigger, final value specifies distance from trigger position
to stop
Motor Reporting Commands
P – Report position of motor
V – Report velocity of motor
F – Report following error of motor
? – Report status words for motor in hex ASCII form
LIST BLCOMP – Report contents of backlash compensation table for motor
LIST BLCOMP DEF – Report definition of backlash compensation table for motor
LIST COMP – Report contents of position compensation table for motor
LIST COMP DEF – Report definition of position compensation table for motor
Miscellaneous Commands
COMMAND"{command}" – Issue text command, no response
COMMAND^{letter} – Issue control character command, no response
COMMANDS"{command}" – Issue text command, respond to main serial port
COMMANDS^{letter} – Issue control character command, respond to main serial port
COMMANDP"{command}" – Issue text command, respond to parallel bus port
COMMANDP^{letter} – Issue control character command, respond to parallel bus port
COMMANDR"{command}" – Issue text command, respond to DPRAM ASCII port
COMMANDR^{letter} – Issue control character command, respond to DPRAM ASCII port
COMMANDA"{command}" – Issue text command, respond to auxiliary serial port
COMMANDA^{letter} – Issue control character command, respond to auxiliary serial port
SENDS"{message}" – Transmit message over main serial interface
Command Issuance
ADDRESS#n&n – Modally address specified motor and/or coordinate system
ADDRESS#Pn – Modally address motor specified in P-variable
ADDRESS&Pn – Modally address coordinate system specified in P-variable
COMMAND"{command}" – Issue text command, no response
COMMAND^{letter} – Issue control character command, no response
COMMANDS"{command}" – Issue text command, respond to main serial port
COMMANDS^{letter} – Issue control character command, respond to main serial port
COMMANDP"{command}" – Issue text command, respond to parallel bus port
COMMANDP^{letter} – Issue control character command, respond to parallel bus port
COMMANDR"{command}" – Issue text command, respond to DPRAM ASCII port
COMMANDR^{letter} – Issue control character command, respond to DPRAM ASCII port
With I3=2:
#1J+<CR> ........ ; Valid command not requiring data response
<ACK>....... ; Acknowledging character
UUU<CR> .......... ; Invalid command
<BELL>............. ; PMAC reports error
P1..3<CR> ...... ; Valid command requiring data response
25<CR>50<CR>75<CR><ACK>
; PMAC responds with requested data
With I3=3:
#1J+<CR> ........ ; Valid command not requiring data response
<ACK> ............... ; Acknowledging character
UUU<CR> .......... ; Invalid command
<BELL>............. ; PMAC reports error
P1..3<CR> ...... ; Valid command requiring data response
<LF>25<CR><LF>50<CR><LF>75<CR><ACK>
.......................... ; PMAC responds with requested data
Turbo-PMAC-to-Host Checksum: Turbo PMAC will compute the checksum of any communications
line it sends to the host. This checksum includes control characters sent with the line, including the final
<carriage-return>. The checksum is sent immediately following this <carriage-return>.
On a multiple-line response, one checksum is sent for each line. Note that this checksum is sent before
the checksum of the command line that caused the response.
For more details on checksum, refer to the Writing a Host Communications Program section of the
manual.
Serial character errors: If Turbo PMAC detects a serial character error, it will set a flag so that the
entire command line will be rejected as having a syntax error after the <CR> is sent. With I4=0 or 1, it
will also send a <BELL> character to the host immediately on detecting the character error. Note that this
mode will catch a character error on the <CR> as well, whereas in the I4=2 or 3 mode, the host would
have to catch an error on the <CR> character by the fact that Turbo PMAC would not respond (because it
never saw a <CR>).
I5 PLC Program Control
Range: 0 to 3
Units: None
Default: 1
I5 controls which PLC programs may be enabled. There are two types of PLC programs: the foreground
programs (PLC 0 and PLCC 0), which operate at the end of servo interrupt calculations, with a repetition
rate determined by I8 (PLC 0 and PLCC 0 should be used only for time-critical tasks and should be
short); and the background programs (PLC 1 to PLC 31, PLCC 1 to PLCC 31) which cycle repeatedly in
background as time allows. I5 controls these as follows:
Setting Meaning
0 Foreground PLCs off; background PLCs off
1 Foreground PLCs on; background PLCs off
2 Foreground PLCs off; background PLCs on
3 Foreground PLCs on; background PLCs on
Note that an individual PLC program still needs to be enabled to run -- a proper value of I5 merely
permits it to be run. Any PLC program that exists at power-up or reset is enabled automatically (even if
the saved value of I5 does not permit it to run immediately); also, the ENABLE PLC n or ENABLE
PLCC n command enables the specified programs. A PLC program is disabled either by the DISABLE
PLC n or DISABLE PLCC n command, or by the OPEN PLC n command. A CLOSE command
does not re-enable the PLC program automatically – it must be done explicitly.
I6 Error Reporting Mode
Range: 0 to 3
Units: None
Default: 1
I6 controls how Turbo PMAC reports errors in command lines. When I6 is set to 0 or 2, PMAC reports
any error only with a <BELL> character. When I6 is 0, the <BELL> character is given for invalid
commands issued both from the host and from Turbo PMAC programs (using CMD”{command}”).
When I6 is 2, the <BELL> character is given only for invalid commands from the host; there is no response
to invalid commands issued from Turbo PMAC programs. (In no mode is there a response to valid
commands issued from PMAC programs.)
When I6 is set to 1 or 3, an error number message can be reported along with the <BELL> character. The
message comes in the form of ERRnnn<CR>, where nnn represents the three-digit error number. If I3 is
set to 1 or 3, there is a <LF> character in front of the message.
When I6 is set to 1, the form of the error message is <BELL>{error message}. This setting is the
best for interfacing with host-computer driver routines. When I6 is set to 3, the form of the error message
is <BELL><CR>{error message}. This setting is appropriate for use with the PMAC Executive
Program in terminal mode.
Currently, the following error messages can be reported:
Error Problem Solution
ERR001 Command not allowed during program execution (should halt program execution before issuing
command)
ERR002 Password error (should enter the proper password)
ERR003 Data error or unrecognized command (should correct syntax of command)
ERR004 Illegal character: bad value (>127 ASCII) or serial (should correct the character and or check for
parity/framing error noise on the serial cable)
ERR005 Command not allowed unless buffer is open (should open a buffer first)
ERR006 No room in buffer for command (should allow more room for buffer --
DELETE or CLEAR other buffers)
ERR007 Buffer already in use (should CLOSE currently open buffer first)
ERR008 MACRO auxiliary communications error (should check MACRO ring hardware and
software setup)
ERR009 Program structural error (e.g. ENDIF without IF) (should correct structure of program)
ERR010 Both overtravel limits set for a motor in the C. S. (should correct or disable limits)
ERR011 Previous move not completed (should Abort it or allow it to complete)
ERR012 A motor in the coordinate system is open-loop (should close the loop on the motor)
ERR013 A motor in the coordinate system is not activated (should set Ix00 to 1 or remove motor from
C.S.)
ERR014 No motors in the coordinate system (should define at least one motor in C.S.)
ERR015 Not pointing to valid program buffer (should use B command first, or clear out
scrambled buffers)
ERR016 Running improperly structured program (e.g. (should correct structure of program)
missing ENDWHILE)
ERR017 Trying to resume after H or Q with motors out of (should use J= to return motor[s] to stopped
stopped position position)
ERR018 Attempt to perform phase reference during move, (should finish move before phase reference,
move during phase reference., or enabling with finish phase reference before move, or fix
phase clock error. phase clock source problem)
ERR019 Illegal position-change command while moves (should pass through section of Program
stored in CCBUFFER requiring storage of moves in CCBUFFER, or
abort)
The hardware Phase clock period (frequency) is controlled by jumpers E98 and E29-E33 on a Turbo
PMAC, variables I7000 and I7001 on a Turbo PMAC2 that is not Ultralite, or variables I6800 and I6801
on a Turbo PMAC2 Ultralite.
Most Turbo PMAC users will leave I7 at the default value of 0, so that phase update algorithms are
executed every phase clock cycle. There are two reasons to extend the phase update cycle by setting I7
greater than 0.
First, if the Turbo PMAC is doing direct PWM control of motors over the MACRO ring, it is advisable to
set I7 to 1 so that the MACRO ring, which operates on the hardware phase clock, cycles twice per
software phase cycle. This will eliminate one phase cycle delay in the closing of the current loops, which
permits higher gains and higher performance. For example, the hardware phase clock could be set to 18
kHz, but with I7=1, the current loop would be closed at a reasonable 9 kHz.
Second, if many multiplexed A/D converters from the on-board Option 12, or Acc-36 boards, are used for
servo feedback, I7 can be set greater than zero to ensure that each A/D converter is processed once per
servo cycle. One pair of multiplexed ADCs is processed each hardware phase clock cycle.
For example, if 8 pairs of multiplexed ADCs needed to be processed each 440 sec (2.25 kHz) servo
cycle, and the software phase update were desired to be at 220 sec (4.5 kHz), the phase clock update
would be set to 18 kHz (18/8 = 2.25) to get through all 8 ADC pairs each servo cycle, I7 would be set to 3
(18/[3+1] = 4.5) to get the software phase update at 4.5 kHz, and the servo cycle clock divider would be
set to divide-by-8 (E3-E6 on Turbo PMAC, I7002=7 on non-Ultralite Turbo PMAC2, I6802=7 on Turbo
PMAC2 Ultralite).
There must be an integer number of software phase updates in a Servo clock period. For example if the
Servo clock frequency is ¼ the Phase clock frequency (I7002 or I6802 = 3), the legitimate values of I7 are
0, which provides 4 software phase updates per servo clock period; 1, which provides 2 updates per
period; and 3, which provides 1 update per period. Note that this rule means that the software phase
update period must never be longer than the servo clock period.
I8 Real-Time Interrupt Period
Range: 0 to 255
Units: Servo Clock Cycles
Default: 2
I8 controls how often certain time-critical tasks, such as PLC 0, PLCC 0, and checking for motion
program move planning, are performed. These tasks are performed every (I8+1) servo cycles, at a
priority level called the “real-time interrupt” (RTI). A value of 2 means that these tasks are performed
after every third servo interrupt, 3 means every fourth interrupt, and so on. The vast majority of users can
leave this at the default value. In some advanced applications that push PMAC's speed capabilities,
tradeoffs between performance of these tasks and the calculation time they take may have to be evaluated
in setting this parameter.
Turbo PMAC cannot compute more than one programmed move block, or more than one internal move
segment if the coordinate system is in segmentation mode (Isx13 > 0), per real-time interrupt. If very
high programmed move block rates (small move times), or very high segmentation rates (small
segmentation times) are desired, it is best to make I8 as small as possible (preferably 0). This will ensure
that the calculations are done every move or segment, and that they are started as early as possible in the
move or segment to maximize the likelihood of completing the calculations in time.
If move or segment calculations are not completed in time, Turbo PMAC will abort the program
automatically with a run-time error.
Note:
A large PLC 0 with a small value of I8 can cause severe problems, because Turbo
PMAC will attempt to execute the PLC program every I8 cycle. This can starve
background tasks, including communications, background PLCs, and even
updating of the watchdog timer, for time, leading to erratic performance or
possibly even shutdown.
In multiple-card Turbo PMAC applications where it is very important that motion programs on the two
cards start as closely together as possible, I8 should be set to 0. In this case, no PLC 0 should be running
when the cards are awaiting a Run command. At other times, I8 may be set greater than 0 and PLC 0 re-
enabled.
I9 Full/Abbreviated Listing Control
Range: 0 to 3
Units: None
Default: 2
I9 controls how Turbo PMAC reports program listings and variable values. I9 is a 2-bit value. Bit 0
whether short-form or long-form reporting is used; bit 1 controls whether address I-variable values are
reported in decimal or hexadecimal form. The following table summarizes:
Setting Meaning
0 Short form, decimal address I-variable return
1 Long form, decimal address I-variable return
2 Short form, hex address I-variable return
3 Long form, hex address I-variable return
When this parameter is 0 or 2 (bit 0 = 0), programs are sent back in abbreviated form for maximum
compactness, and when I-variable values or M-variable definitions are requested, only the values or
definitions are returned, not the full statements. When this parameter is 1 or 3 (bit 0 = 1), programs are
sent back in full form for maximum readability. Also, I-variable values and M-variable definitions are
returned as full command statements, which is useful for archiving and later downloading.
When this parameter is 0 or 1 (bit 1 = 0), I-variable values that specify PMAC addresses are returned in
decimal form. When it is 2 or 3 (bit 1 = 1), these values are returned in hexadecimal form (with the '$'
prefix). Any I-variable values cdan be sent to PMAC either in hex or decimal, regardless of the I9 setting.
This does not affect how I-variable assignment statements inside Turbo PMAC motion and PLC
programs are reported when the program is listed.
I10 Servo Interrupt Time
Range: 0 to 8,388,607
Units: 1 / 8,388,608 msec
Default: 3,713,707 [Turbo PMAC: 442.71 sec]
3,713,991 [Turbo PMAC2: 442.74 sec]
This parameter tells Turbo PMAC how much time there is between servo interrupts (which is controlled
by hardware circuitry), so that the interpolation software knows how much time to increment each servo
interrupt.
The fundamental equation for I10 is:
8 ,388 ,608
I 10 8 ,388 ,608 * ServoTime( m sec)
ServoFrequency ( kHz )
On Turbo PMAC, the servo interrupt time is determined by the settings of hardware jumpers E98, E29-
E33, and E3-E6. The proper value of I10 can be determined from the settings of these jumpers by the
formula:
I 10 232,107 * E 98 JumperFact or * PhaseJumperFactor * ServoJumperFactor
where the factors can be taken from the following:
E98 Setting 1-2 2-3
E98JumperFactor 1 2
ServoJumperFactor 1 E 3 ( 2 * E 4 ) ( 4 * E 5 ) ( 8 * E6 )
in which En = 0 if the jumper is ON, and En = 1 if the jumper is OFF.
On Turbo PMAC2, the servo interrupt time is determined on PMAC2 Ultralite boards by MACRO IC 0 I-
variables I6800, I6801, and I6802; on non-Ultralite boards by Servo IC 0 I-variables I7000, I7001, and
I7002; on UMAC Turbo systems by Servo IC m I-variables I7m00, I7m01, and I7m02, or MACRO IC 0
I-variables I6800, I6801, or I6802. The proper setting of I10 can be determined from Servo IC variables
by the formula:
I 10
640
2* I7 m00 3I7 m01 1I7 m02 1
9
The proper setting of I10 can be determined from MACRO IC 0 variables by the formula:
I 10
640
2* I 6800 3I 6801 1I 6802 1
9
When changing I10, a %100 command must be issued, or the value saved and the controller reset, before
the new value of I10 will take effect.
I10 is used to provide the delta-time value in the position update calculations, scaled such that 2 23 –
8,388,608 – means one millisecond. Delta-time in these equations is I10*(%value/100). The % (feedrate
override) value can be controlled in any of several ways: with the on-line ‘%’ command, with a direct
write to the command ‘%’ register, with an analog voltage input, or with a digital input frequency. The
default % value is 100, and many applications can always leave it at 100.
I11 Programmed Move Calculation Time
Range: 0 to 8,388,607
Units: msec
Default: 0
I11 controls the delay from when the run signal is taken (or the move sent if executing immediately) and
when the first programmed move starts. If several Turbo PMACs need to be run synchronously, I11
should be set the same on all of the cards. If I11 is set to zero, the first programmed move starts as soon
as the calculation is complete.
This calculation time delay is also used after any break in the continuous motion of a motion program: a
DWELL, a PSET, a WAIT, or each move if Ix92=1 (a DELAY is technically a zero-distance move, and so
does not constitute a break).
The actual delay time varies with the time base (e.g. at a value of 50, the actual delay time will be twice
the number defined here), which keeps it as a fixed distance of the master in an external time base
application. If it is desired to have the slave coordinate system start up immediately with the master, I11
should be set to zero, and the program commanded to run before the master starts to move.
Note:
If I11 is greater than zero, defining a definite time for calculations, and Turbo
PMAC cannot complete the calculations for the first move of a sequence by the
end of the I11 time, Turbo PMAC will terminate the running of the program with a
run-time error.
I19 contains the number of the servo/phase clock-direction I-variable whose value is set by default to 0,
indicating that the matching Servo IC or MACRO IC is the source of the servo and phase clock signals
for the Turbo PMAC2 system. This I-variable for all other Servo ICs and MACRO ICs in the system is
set to 3, indicating that these ICs will use servo and phase clock signals from a source external to them.
The clock-direction I-variables for MACRO ICs 0, 1, 2, and 3 are I6807, I6857, I6907, and I6957,
respectively. The clock direction I-variables for Servo ICs m and m* (m = 0 to 9) are I7m07 and I7m57,
respectively.
Note:
Only in 3U-format Turbo PMAC2 systems (UMAC Turbo and 3U Turbo Stack)
can the clock signals come from ICs on accessory boards. In other Turbo PMAC2
systems, the clock signals must come from an IC on the base PMAC board, or be
brought in through the serial port.
During system re-initialization (reset with E3 jumper ON, or $$$*** command), then Turbo PMAC2 first
determines the “default” value of I19 by searching for the presence of all possible Servo and MACRO ICs,
and assigning the clock source to the first IC it finds in the following list:
1. Servo IC 0 (On-board or 3U Stack) (I19=7007)
2. MACRO IC 0 (On-board or Acc-5E) (I19=6807)
3. Servo IC 1 (On-board or 3U Stack) (I19=7107)
4. Servo IC 2 (Acc-24E2, 51E) (I19=7207)
…
11. Servo IC 9 (Acc-24E2, 51E) (I19=7907)
12. Servo IC 2* (Acc-24E2, 51E) (I19=7257)
…
19. Servo IC 9* (Acc-24E2, 51E) (I19=7957)
20. MACRO IC 1 (On-board or Acc-5E) (I19=6857)
21. MACRO IC 2 (On-board or Acc-5E) (I19=6907)
21. MACRO IC 3 (On-board or Acc-5E) (I19=6957)
(MACRO ICs must be DSPGATE2 ICs to be used as a clock source.)
If the E1 external-clock-source jumper is ON during re-initialization, I19 is set to 0, indicating that no
Servo IC or MACRO IC will be the source of the system clocks.
If one of the clock-direction I-variables is commanded to be set to its default value (e.g. I7007=*),
Turbo PMAC2 looks to I19 to decide whether this variable will be set to 0 or not.
In 3U-format Turbo PMAC2 systems, I19 also operates at the system’s power-up/reset. At this time, the
saved value of I19 determines which single one of the Servo-IC or MACRO-IC clock-direction I-
variables is set to 0 at reset to provide the system with that ICs servo and phase clock signals.
The clock-direction I-variables for all of the other Servo ICs and MACRO ICs are set to 3 at reset to tell
them to input the servo and phase clock signals, regardless of the saved values for these I-variables. (On
other Turbo PMAC2 boards, the saved values of the clock-direction I-variables are used.) If the Servo IC
or MACRO IC thus selected is not present, the watchdog timer will trip immediately.
In 3U-format Turbo PMAC2 systems, if the saved value of I19 is 0, the clock-direction I-variables for all
Servo ICs (I7m07) and MACRO ICs (I6807 etc.) is not automatically set on power-up/reset based on the
setting of I19. The saved values of these variables are used instead. If all of these values are 3, an external
clock signal can be used. To do this, jumper(s) E1 must be ON to admit externally generated servo and
phase clocks on the serial port.
On Turbo PMAC boards, the Servo and Phase clock signals are generated in the same discrete logic (or
come in from an external source), so I19 is not needed to control which ASIC provides the clock signals.
For a Turbo PMAC2 that is not Ultralite or UMAC, the only valid MACRO IC base address is $78400.
For a Turbo PMAC2 Ultralite, the valid base addresses are $78400, $79400, $7A400, and $7B400. For a
UMAC Turbo system, the valid base addresses can be expressed as $7xy00, where x can be 8, 9, A, or B,
and ‘y’ can be ‘4’, ‘5’, ‘6’, or ‘7’.
If the configuration of the MACRO ICs in a modular Turbo PMAC system, such as a UMAC Turbo rack,
is changed, the values of I20 – I23 will need to be changed.
See Also:
I-Variables I20, I21, I23, I24, I4902 – I4903, I4926 – I4941, I6800 – I6999.
I23 MACRO IC 3 Base Address (Turbo PMAC2 only)
Range: $0, $078400 - $07B700
Units: Turbo PMAC Addresses
Default: Auto-detected
I23 sets the base address of the fourth MACRO IC (called MACRO IC 3) in the Turbo PMAC2 system,
normally the one with the fourth-lowest base address. On re-initialization – either on resetting with the
E3 re-initialization jumper ON or on issuing the $$$*** command, Turbo PMAC2 will auto-detect
which MACRO ICs are present, and set I23 to the base address of the MACRO IC with the fourth-lowest
base address. Turbo PMAC2 will also do this when commanded to set I23 to its default value (I23=*).
If less than four MACRO ICs are found, I23 will be set to 0 instead.
I-variables I6950 – I6999 reference registers in MACRO IC 3, whose addresses are relative to the address
contained in I23. These addresses are established at power-up/reset. If the value of I23 is incorrect at
power-up/reset, these I-variables will not work. It is possible to set the value of I23 directly, saving the
value and resetting the card, but users are strongly encouraged just to let Turbo PMAC2 set I23 itself by
re-initialization or default setting, and to treat I23 as a status variable. If I23 is set to 0, these variables
will always return a value of 0.
A Turbo PMAC2 will look to find MACRO nodes 48 – 63 in MACRO IC 3, referenced to the address
contained in I23. These addresses are established at power-up/reset. If the value of I23 is incorrect at
power-up/reset, these MACRO nodes will not be accessed.
UMAC versions of the Turbo PMAC2 have the addressing capability for up to 16 MACRO ICs, but only
the 4 MACRO ICs referenced by I20 – I23 can have I-variable support. Master-to-master MACRO
communications can only be done on MACRO IC 3, referenced by I23, when I84=3.
For a Turbo PMAC2 that is not Ultralite or UMAC, the only valid MACRO IC base address is $78400.
For a Turbo PMAC2 Ultralite, the valid base addresses are $78400, $79400, $7A400, and $7B400. For a
UMAC Turbo system, the valid base addresses can be expressed as $7xy00, where x can be 8, 9, A, or B,
and ‘y’ can be ‘4’, ‘5’, ‘6’, or ‘7’.
If the configuration of the MACRO ICs in a modular Turbo PMAC system, such as a UMAC Turbo rack,
is changed, the values of I20 – I23 will need to be changed.
See Also:
I-Variables I20, I21, I22, I24, I4902 – I4903, I4926 – I4941, I6800 – I6999.
I24 Main DPRAM Base Address
Range: $0, $060000 - $077000
Units: Turbo PMAC Addresses
Default: Auto-detected
I24 sets the base address of the dual-ported RAM IC in the Turbo PMAC system that is used for the
automatic DPRAM communications functions.
Default: 0
I27 controls how the Turbo PMAC interprets incoming data on a TWS-format M-variable read from an
ACC-34 or similar serial-interface I/O board. If I27 is set to the default value of 0, PMAC expects the
serial input data on the DAT0 signal line. If I27 is set to 1, PMAC expects the serial input data on the
DAT7 signal line.
The DAT7 line is separated more from the output clock line on the same cable; the use of DAT7 by
setting I27 to 1 and making the appropriate jumper setting on the I/O board makes it possible to use a
longer cable without too much coupling interference between signals.
On the ACC-34AA, jumper E23 must be connect pins 1 and 2 to support the default setting of I27 = 0; it
must connect pins 2 and 3 to support the setting of I27 = 1. On the ACC-76 and ACC-77 “P-Brain”
boards, jumper E1 should be ON to support the default setting of I27 = 0; jumper E8 should be ON to
support the setting of I27 = 1. Older boards of this class do not support settings of I27 = 1.
I28 Display Port Disable
Range: 0–1
Units: none
Default: 0
I28 permits the user to disable the automatic update of 80-character displays on the the JDISP port. If I28
is set to the default value of 0, the Turbo PMAC will write an ASCII character value to the 8 data lines
(DISP0 – DISP7) of the JDISP port every real-time interrupt, and index a pointer to the next character in
Turbo PMAC’s 80-character buffer in RAM.
If I28 is set to 1, this automatic functionality is disabled, permitting general-purpose use of the 8 I/O lines
on the port. On many hardware versions of the Turbo PMAC, the buffer IC for this port can only support
outputs, but on some it is possible to reverse the direction of these lines to input as well.
I28 is only used at power-on/reset, so to make a change in the functionality of the display port, it is
necessary to change the value of I28, store the value in non-volatile flash memory with the SAVE
command, and reset the Turbo PMAC.
I29 Multiplexer Port Alternate Address
Range: $0, $078400 - $07B7FF
Units: Turbo PMAC addresses
Default: 0
I29 permits the user to select an alternate address for the automatic functions of the “JTHW” multiplexer
port, such as TWS, TWR, and TWD-format M-variables. If I29 is set to the default value of 0, the Turbo
PMAC will use the standard multiplexer-port register at address Y:$078402 for these functions.
If I29 is set to a non-zero value, Turbo PMAC will use the Y-register at the address specified by the value
for these functions. There are several possible uses for this functionality.
In the Turbo PMAC2-Eth Ultralite and Turbo PMAC2-RTEX controllers, the multiplexer port uses the Y-
register at $078400, so I29 should be set to this value to use the automatic functions on this port.
If an ACC-2P is installed on a Turbo PMAC2A-Eth Lite (“Clipper”) board, and it is desired to use the
automatic functions on the multiplexer port of the ACC-2P instead of that of the Clipper itself, I29 should
be set to $078502.
If multiple ACC-5E boards are installed in a UMAC Turbo system, and it is desired to use the automatic
functions on the multiplexer port of one of the secondary boards not at the standard base address, I29
should be set to a value 2 greater than the base address of that board (e.g. $078502, $078602, or
$078702).
I29 is only used at power-on/reset, so to make a change in the functionality of the display port, it is
necessary to change the value of I29, store the value in non-volatile flash memory with the SAVE
command, and reset the Turbo PMAC.
I30 Compensation Table Wrap Enable
Range: 0-1
Units: none
Default: 0
I30 controls whether the compensation tables entered into Turbo PMAC will automatically wrap or not.
This affects position (leadscrew), backlash, and torque compensation tables. If I30 is set to 0, when a
table is downloaded to PMAC, the compensation correction at motor position 0 is always set to 0. In this
case, if smooth rollover of the table is desired, the last entry of the table must explicitly be set to 0.
If I30 is set to 1, the last entry of the table also becomes the correction at motor position 0, automatically
yielding a smooth rollover of the table, and permitting non-zero corrections at the rollover point.
I30 affects table values only as they are being downloaded to Turbo PMAC; it does not affect the values
of tables already in Turbo PMAC’s memory.
I35 Brick LV & Controller E-Stop Enable
Range: 0 .. 1
Units: none
Default: 0
I35 permits the user to enable a fail-safe “E-stop” input on the Geo Brick LV controller/amplifier and on
the Brick Controller. If I35 is set to 1, system wiring must be drawing sufficient current through the E-
stop input (in the “ABORT+” pin and out the “ABORT-” pin) on the front panel to close the normally-
open E-stop relay, permitting motion. This is typically done by applying 24VDC across the circuit.
When sufficient current is passing through the relay to close the contactor, bit 5 of Y:$070801 will be
read as 1 by the processor. In this case, normal operation of all motors in the system is permitted.
When there is not sufficient current through the relay, the contactor opens, and bit 5 of Y:$070801 will be
read as 0 by the processor. When this occurs, the processor executes an “abort all” command, the
equivalent of receiving a <CTRL-A> command with I36 = 1. This will bring any enabled motor to a
closed-loop zero-velocity state, but will not enable any disabled motor. No motion can be commanded of
any motor as long as the relay contactor is closed and the bit value is 1. Note that the setting of I36 affects
the action of received <CTRL-A> commands, but it does not affect the action of this E-stop input.
This is a software-controlled stop function, and may not qualify as an emergency-stop circuit in
jurisdictions that require a “software-free” and/or “silicon-free” circuit. In those applications, the bus
supply power should be disconnected from the drives for an emergency stop.
In other Turbo PMAC hardware implementations, I35 should be set to 0, because there is no physical
input at this address, and the value of the bit read by the processor is indeterminate.
Note: This E-stop function is automatically enabled on the higher-voltage Geo Brick controller/amplifier,
which uses its own firmware variant. The Geo Brick does not use I35.
The following table shows the action of each of these commands with I36 = 1:
Command Starting State: Starting State: Starting State:
Disabled Open-Loop Enabled Closed-Loop Enabled
A (no action) Close loop at present Decelerate to stop using
position Ixx15
<CTRL-A> (no action) Close loop at present Decelerate to stop using
position Ixx15
E Enable, close loop at Close loop at present (no action)
present position position
<CTRL-E> Enable, close loop at Close loop at present (no action)
present position position
If I38 is set to the default value of 0, the jump to the subprogram causes suspension of program
calculation until the start of execution of a new move.
I39 UBUS Accessory ID Variable Display Control
Range: 0–5
Units: none
Default: 0
I39 controls which portions of the identification variables I4909 – I4999, which provide information
about accessory boards on UMAC’s “UBUS” backplane expansion port, are reported. These variables are
36-bit variables in total, with 4 parts:
1. Vendor ID (Bits 0 – 7)
2. Options Installed (Bits 8 – 17)
3. Revision Number (Bits 18 – 21)
4. Card ID [Part #] (Bits 22 – 35)
The following list shows the possible values of I39, and which parts of these ID variables are reported for
each value:
I39 = 0: Vendor ID, Options Installed, Revision Number, Card ID (36 bits)
I39 = 1: Vendor ID only (8 bits)
I39 = 2: Options Installed only (10 bits)
I39 = 3: Revision number only (4 bits)
I39 = 4: Card ID only (14 bits)
I39 = 5: Base Address of Card (19 bits)
Note:
The base address of the card reported with I39 = 5 is not part of the card
identification variable, but it is still very useful in determining the configuration of
the system.
The value of I39 is not saved, and I39 is set to 0 automatically on power-up/reset.
Example:
I39=1 ; Report Vendor ID only
I4910 ; Query first axis card vendor ID
1 ; (Delta Tau is Vendor ID #1)
I39=2 ; Report Options Installed only
I4910 ; Query first axis card options installed
3 ; First 2 options installed (bits 0 and 1 set)
I39=3 ; Report revision number only
I4910 ; Query first axis card revision number
2 ; Revision 2 (-102 board)
I39=4 ; Report Card ID (part number) only
I4910 ; Query first axis card part number
3397 ; Card ID 3397 (Delta Tau part # 603397: Acc-24E2)
I39=5 ; Report base address only
I4910 ; Query first axis card base address
$78200 ; Base address $78200
I39=0 ; Report all of ID variable
I4910 ; Query first axis card full ID variable
14248575745 ; Full ID variable for card
See Also:
I-Variables I4909 – I4999
This ability to disable the automatic command parser permits the auxiliary port to be interfaced to other
devices such as vision systems, which send out data on their serial ports, and not have the Turbo PMAC
try to interpret this data as commands. The user can then interpret the input string in application software
using M-variable pointers, typically with indirect addressing techniques.
Serial Port Command Queue Command Pointer Response Queue Response Response
Pointer Transmit Flag
Auxiliary X:$001C00 … X:$000034 Y:$001C00 … Y:$000034 Y:$30,11
$001CFF $001CFF
Main X:$003600 … X:$FFFFE6 Y:$003600 … X:$FFFFE1 X:$FFFFE0,23
$0036FF $0036FF
Only the low byte (bits 0 – 7) of each word in the command and response queues is used. The command
pointer contains the location of the next character to be input to the Turbo PMAC. The response pointer
does not need to be used if responses are issued using the SENDA or SENDS commands; only if responses
are “manually” placed in the response queue. If assembling responses manually on the main serial port,
the response must start at Y:$003600, the number of bytes to output must be placed in X:$FFFFE1, and
bit 23 of X:$FFFFE0 must be set to 1 to enable the output . On the auxiliary serial port, the response must
start at Y:$001C00, and bit 23 of the last character to be sent has to be set to 1. Setting bit 11 of Y:$30 to
1 initiates the transmission of data.
I44 PMAC Ladder Program Enable {Special Firmware Only}
Range: 0-1
Units: none
Default: 0
I44 controls whether the “PMAC Ladder” graphical PLC programs that can be used with optional
firmware are running or not. If I44 is set to 1, any PMAC ladder programs that have been downloaded
into Turbo PMAC program memory are active. If I44 is set to 0, these programs will not execute, even if
they are present.
If the firmware does not support these PMAC Ladder PLC programs, I44 cannot be changed from 0.
I45 Foreground Binary Rotary Buffer Transfer Enable
Range: 0-1
Units: none
Default: 0
I45 controls whether the transfer of binary rotary buffer commands from dual-ported RAM to internal
memory is done as a background task or as a foreground task. If I45 is set to the default value of 0 when
the OPEN BIN ROT command is given, Turbo PMAC checks the DPRAM binary rotary buffer once per
background cycle (if the binary buffer is open) and copies commands received in the last cycle to the
buffer in internal memory. If I45 is set to 1 when the OPEN BIN ROT command is given, Turbo PMAC
checks the DPRAM buffer every real-time interrupt (every I8+1 servo cycles) instead.
Setting I45 to 1 permits a quicker and more predictable reaction to the receipt of binary rotary buffer
commands from the host computer.
I46 P & Q-Variable Storage Location
Range: 0 to 3
Units: None
Default: 0
I46 controls the memory locations that Turbo PMAC uses to store the P and Q-Variables. For each type
of variable, there is a choice between the main flash-backed memory and the optional supplemental
battery-backed memory. Option 16 must be purchased in order to be able to select the battery-backed
memory storage.
I46 can take four values: 0, 1, 2, and 3. The meaning of each is:
Reporting this data as a high-priority foreground task permits a reliable high-frequency transfer of motor
data to the host, but it can have a significant impact on the capabilities of lower priority tasks, such as
motion program trajectory calculations, and PLCs.
When I48=0, the DPRAM motor data reporting function in foreground is disabled.
If I57 is set to 1 to enable DPRAM reporting of the motor registers as a background task, Turbo PMAC
automatically sets I48 to 0 to disable the foreground reporting.
Refer to the description of DPRAM functions for more information.
I49 DPRAM Background Data Reporting Enable
Range: 0 to 1
Units: None
Default: 0
I49 enables or disables the dual-ported RAM (DPRAM) background data reporting function. When
I49=1, PMAC copies key data from coordinate-system and global data registers to fixed registers in the
DPRAM approximately every I50 servo cycles (or on demand if I50=0) for easy access by the host
computer. The data for coordinate systems up to the number specified by a designated register in
DPRAM are reported.
When I49=0, the DPRAM background data reporting function is disabled.
Refer to the description of DPRAM functions for more information.
I50 DPRAM Background Data Reporting Period
Range: 0 to 255
Units: Servo Cycles
Default: 0
I50 specifies the minimum period, in servo cycles, that Turbo PMAC will copy data from coordinate-
system and global data registers into fixed registers in DPRAM for easy access by the host computer, if
this function has been enabled by setting I49 to 1. In addition, if I57 is set to 1, I50 specifies the
minimum period that Turbo PMAC will copy motor data registers into DPRAM. If I49 and/or I57, and
I50 are greater than 0, then each background cycle, Turbo PMAC will check to see if at least I50 servo
cycles have elapsed since the last reporting; if this is so, it will copy the current data into DPRAM. The
data for coordinate systems up to the number specified by a designate register in DPRAM are reported.
If I50 is set to 0, the reporting is on demand. In this mode, Turbo PMAC will check every background
cycle to see if the host computer has set the request bit in DPRAM, signaling that it has read the previous
cycle’s data. Turbo PMAC will copy the latest data into DPRAM only if this bit is set, and it will clear
the bit.
I51 Compensation Table Enable
Range: 0 to 1
Units: None
Default: 0 (disabled)
I51 the enabling and disabling of all of the compensation tables for all motors on Turbo PMAC:
leadscrew compensation tables, backlash compensation tables, and torque compensation tables. When
I51 is 0, all tables are disabled and there is no correction performed. When I51 is 1, all tables are enabled
and corrections are performed as specified in the tables.
The constant backlash as controlled by Ixx85 and Ixx86 is not affected by the setting of I51.
I52 CPU Frequency Control
Range: 0 to 31
If the host computer baud rate cannot be made to match the Turbo PMAC’s baud rate, the Turbo PMAC’s
baud rate must be changed through another communications port.
I54 Serial Port Baud Rate Control
Range: 0 to 15
Units: None
Default: 12 (38400 baud)
I54 controls the baud rate for communications on the main serial port. Turbo PMAC uses I54 only at
power-up/reset to set up the frequency of the clocking circuit for the serial port. To change the baud rate,
it is necessary to change the value of I54, store this value to non-volatile flash memory with the SAVE
command, and reset the card. At this time, Turbo PMAC will establish the new baud rate.
The possible settings of I54 and the baud rates they define are:
I54 Baud Rate I54 Baud Rate
0 600 8 9600
1 900 9 14,400
2 1200 10 19,200
3 1800 11 28,800
4 2400 12 38,400
5 3600 13 57,600
6 4800 14 76,800
7 7200 15 115,200
Baud rates set by odd values of I54 are not exact unless the CPU is running at an exact multiple of 30
MHz (I52 = 2, 5, 8, 11, 14, 17, 20, 23). For most of these baud rates, the errors are small enough not to
matter. However, for 115,200 baud, the CPU must be running at an exact multiple of 30 MHz to establish
serial communications.
If the host computer baud rate cannot be made to match the Turbo PMAC’s baud rate, either the Turbo
PMAC's baud rate must be changed through the bus communications port, or the Turbo PMAC must be
re-initialized by resetting or powering up with the E51 jumper ON for Turbo PMAC, or the E3 jumper
ON for Turbo PMAC2. This forces the Turbo PMAC to the default baud rate of 38,400.
I55 DPRAM Background Variable Buffers Enable
Range: 0 to 1
Units: None
Default: 0 (disabled)
I55 enables or disables the dual-ported RAM (DPRAM) background variable read and write buffer
function. When I55 is 0, this function is disabled. When I55 is 1, this function is enabled. When
enabled, the user can specify up to 128 Turbo PMAC registers to be copied into DPRAM each
background cycle to be read by the host (background variable read) and up to 128 Turbo PMAC registers
to be copied each background cycle from values written into the DPRAM by the host (background
variable write).
I56 DPRAM ASCII Communications Interrupt Enable
Range: 0 to 1
Units: None
Default: 0 (disabled)
This parameter controls the interrupt feature for the dual-ported RAM (DPRAM) ASCII communications
function enabled by I58=1. When I56=1, PMAC will generate an interrupt to the host computer each
time it loads a line into the DPRAM ASCII buffer for the host to read. When I56=0, it will not generate
this interrupt.
For the Turbo PMAC PC, the interrupt line used is the EQU4 interrupt. For this to reach the host, jumper
E55 must be ON, and jumpers, E54, E56, and E57 must be OFF. When using this feature, do not use the
EQU4 line for any other purpose, including position compare.
For the Turbo PMAC2 PC the interrupt line used is the EQU1 interrupt. When using this feature, do not
use the EQU1 line for any other purpose, including position compare.
For the VME-bus versions of Turbo PMAC (Turbo PMAC VME, Turbo PMAC2 VME and Turbo
PMAC2 VME Ultralite), the interrupt line used is the normal communications interrupt (the only interrupt
available). This line -- IRQn on the VME bus, is determined by the VME setup variable I95. The
interrupt vector provided to the host is one greater than the value in VME setup variable I96. For
example, if I96 is set to the default value of $A1, this interrupt will provide an interrupt vector of $A2.
For the Turbo PMAC2 PC Ultralite, this feature is not presently supported with the standard hardware.
I57 DPRAM Motor Data Background Reporting Enable
Range: 0 to 1
Units: None
Default: 0
I57 enables or disables the dual-ported RAM (DPRAM) motor data reporting as a background function.
When I57=1, Turbo PMAC copies key data from internal motor system and global data registers to fixed
registers in the DPRAM as a background task approximately every I50 servo cycles (or on demand if
I50=0) for easy access by the host computer. The data is reported for those motors specified by a mask
word in DPRAM at Turbo PMAC address $06001C.
If I57 is set to 1, then Turbo PMAC automatically sets I48 to 0, disabling the foreground reporting of the
same data.
When I57=0, the DPRAM background motor data reporting function is disabled. In this setting, I48 can
be set to 1 to enable foreground reporting of the motor data.
For most purposes, background reporting of the motor data will provide the data at a high enough rate,
and it will not degrade the performance of motion programs. Only if the data is required at a guaranteed
high frequency should the foreground reporting be used.
Refer to the description of DPRAM functions for more information.
I58 DPRAM ASCII Communications Enable
Range: 0 to 1
Units: None
Default: 0 (disabled) if no DPRAM present
1 (enabled) if DPRAM present
I58 enables or disables the dual-ported RAM (DPRAM) ASCII communications function. When I58=1,
this function is enabled and the host computer can send ASCII command lines to the Turbo PMAC
through the DPRAM and receive ASCII responses from Turbo PMAC through the DPRAM. When
I58=0, this function is disabled.
At power-up/reset, if Turbo PMAC finds a DPRAM IC present in the system, I58 is automatically set to
1, immediately enabling this communications. If no DPRAM IC is found in the system at this time, I58 is
automatically set to 0.
I3 does not affect the handshaking characters used in DPRAM ASCII communications.
If I56 is also equal to 1, PMAC will provide an interrupt to the host computer when it provides a response
string.
I65 is a variable that has no automatic function in Turbo PMAC. Because its factory default value is 0,
setting it to a non-zero value as part of the downloaded configuration file provides an easy way of later
verifying that the configuration has been loaded in a particular card.
Since this variable has no automatic function, how this variable is utilized (if it is utilized at all) is
completely up to the user. The same value may be downloaded to every controller, just for later
verification of the presence of the download. Alternately, it may be used to identify different optional
configurations, or as an electronic serial number.
I67 Modbus TCP Buffer Start Address
Range: $0 – $03FFFF
Units: Turbo PMAC addresses
Default: 0
I67 enables the Modbus TCP interface in Turbo PMAC software and reports the starting address of the
256-word Modbus buffer in Turbo PMAC memory. To enable the Modbus TCP interface on the Turbo
PMAC’s Ethernet port, the following conditions must apply:
1. The Ethernet physical interface must be present
2. The Modbus TCP firmware for the Ethernet processor must be installed
3. V1.941 or newer Turbo PMAC firmware must be installed
4. A user buffer of 256 or more words must have been defined with the DEFINE UBUFFER
command
5. I67 must be set to a value greater than 0.
The user can set I67 to any value greater than 0 to enable the Modbus TCP buffer. When this is done,
PMAC will automatically set I67 to the address of the start of the 256-word Modbus buffer. In the
standard Turbo PMAC CPU/memory configuration (Option 5C0), this address will be $010700, so the
buffer will occupy the addresses $010700 - $0107FF.
A SAVE command must be issued with I67 at a non-zero value in order for the Modbus TCP buffer to be
active after subsequent power-up or reset operations.
I68 Highest Sync. M-Var. Max. Sync M-Var. Max. Sync M-Var.
Value Numbered Stack per C.S. Assignments per Assignments per
Coordinate move, no cutter comp move, cutter comp on
System Activated
0 C.S. 1 256 words 63 42
1 C.S. 2 128 words 31 20
2-3 C.S. 3 - 4 64 words 15 10
4-7 C.S. 5 - 8 32 words 7 4
8 - 15 C.S. 9 - 16 16 words 3 2
The default I68 value of 15 (all coordinate systems activated) will always work, even if fewer coordinate
systems are actually being used. Lowering I68 from this default if fewer coordinate systems will be used
brings two advantages. First, there is a slight improvement in computational efficiency because de-
activated coordinate systems do not have to be checked periodically.
Second, each remaining active coordinate system has a bigger piece of the synchronous M-variable
assignment stack, so more synchronous M-variable assignments can be executed per move. Each
synchronous M-variable assignment requires two words of the stack; one additional word is required per
move. The above table lists how many synchronous M-variables assignments can be performed per move
in each active coordinate system.
If the special lookahead function is enabled, synchronous M-variable assignments made during lookahead
are stored in the area reserved in the lookahead buffer, and the number of assignments that can be
buffered is limited by the space reserved with the DEFINE LOOKAHEAD command.
I68 is actually used at power-on/reset only, so to make a change in the number of activated coordinate
systems, change the value of I68, store this new value to non-volatile flash memory with the SAVE
command, and reset the card with the $$$ command.
I69 Modbus TCP Software Control Panel Start Address
Range: $0 – $03FFFF
Units: Turbo PMAC addresses
Default: 0
I69 enables and specifies the address of the start of the Modbus TCP software control panel in Turbo
PMAC. I69 permits a software control panel to be commanded over the Modbus TCP link, typically from
a PLC, using part of the user buffer created with the DEFINE UBUFFER command and reserved for
Modbus TCP use with I67. If I69 is set to a value greater than 0, this software control panel is enabled.
Typically, I69 is set to a value 112 ($70) greater than the value of I67, so this control panel starts at an
address 112 higher than the beginning of the entire Modbus TCP buffer in an unused configuration
portion of the buffer. For example, if the beginning of the Modbus buffer were at $010700, I69 could be
set to $010770.
The software control panel occupies 16 long words of Turbo PMAC memory. The structure functions of
the Modbus panel are equivalent to those for the DPRAM software control panel, which are documented
in the Memory and I/O Map chapter of the Software Reference Manual at their default addresses of
$060000 - $06000F.
The operation of the Modbus control panel is independent of that for the DPRAM control panel (which is
controlled by I2). One, neither, or both of these control panels may be active at one time.
MACRO Ring Configuration I-Variables
I70 MACRO IC 0 Node Auxiliary Register Enable
Range: 0 .. $FFFF (0 .. 65,535)
Units: none
Default: 0
I70 controls which nodes of MACRO IC 0 for which Turbo PMAC performs automatic copying into and
out of the auxiliary registers. Enabling this function for a node is required to use the auxiliary register as
the flag register for a motor.
I70 is a 16-bit variable. Bits 0 to 15 control the enabling of this copying function for MACRO nodes 0 to
15, respectively. A bit value of 1 means the copying function is enabled; a bit value of 0 means the
copying function is disabled.
If the copying function is enabled for Node n (where n = 0 to F hex or 0 to 15 decimal), during each
background “housekeeping” software cycle, PMAC copies the contents of Y:$000344n to the Node n
auxiliary write register, and copies the contents of the Node n auxiliary read register into X:$00344n.
The copying function enabled by I70 permits the use of the auxiliary registers for command and status
flags plus Type 0 auxiliary read and write functions in PLC programs and on-line commands.
For each node whose auxiliary functions are enabled by I70, I71 must correctly specify for the node
whether the Type 0 or Type 1 MACRO protocol is used.
If a value of I78 greater than 0 has been saved into PMAC’s non-volatile memory to enable Type 1
MACRO master/slave auxiliary communications with Node 15, then at subsequent power-up/resets, bit
15 of I70 is automatically forced to 0 by PMAC firmware, regardless of the value saved for I70. This
reserves Node 15 for the Type 1 master/slave auxiliary communications alone.
If a value of I79 greater than 0 has been saved into PMAC’s non-volatile memory to enable Type 1
MACRO master/master auxiliary communications with Node 14, then at subsequent power-up/resets, bit
14 of I70 is automatically forced to 0 by PMAC firmware, regardless of the value saved for I70. This
reserves Node 14 for the Type 1 master/master auxiliary communications alone.
I71 MACRO IC 0 Node Protocol Type Control
Range: 0 .. $FFFF (0 .. 65,535)
Units: none
Default: 0
I71 controls for each node (0 - 15) on MACRO IC 0 whether the matching slave node is expected to be
another Turbo PMAC or a slave-only “MACRO Station” for purposes of the protocol of exchanging non-
cyclic information. I71 is a 16-bit value; each bit 0 – 15 controls the protocol type for the MACRO node
of the same number. A value of 0 in the bit selects the “Turbo PMAC” protocol for the matching
MACRO node (using MX commands); a value of 1 in the bit selects the Type 1 protocol for the node
(using MS commands). The selection of the proper protocol is essential for the correct operation of
homing-search moves and other “move-until-trigger” functions, which require an MS or MX command to
obtain the trigger-captured position across the ring.
“MACRO Stations” include UMAC MACRO racks with 8 or 16-axis CPUs, Geo MACRO drives,
MACRO Peripheral modules, and 3rd-party MACRO devices. To use a Turbo PMAC as a slave on a
MACRO ring, V1.945 or newer firmware is required.
Prior to V1.945 firmware, a value of 0 in a bit selected the now-obsolete “Type 0” slave-only protocol for
the matching node.
I72 MACRO IC 1 Node Auxiliary Register Enable
Range: 0 .. $FFFF (0 .. 65,535)
Units: none
Default: 0
I72 controls which nodes of MACRO IC 1 for which Turbo PMAC performs automatic copying into and
out of the auxiliary registers. Enabling this function for a node is required to use the auxiliary register as
the flag register for a motor.
Note:
MACRO IC 1 can be present only on Turbo PMAC2 Ultralite boards with Option
1U1 ordered, or on a 3U Turbo PMAC2 with some configurations of its Acc-5E.
I72 is a 16-bit variable. Bits 0 to 15 control the enabling of this copying function for MACRO nodes 0 to
15, respectively. A bit value of 1 means the copying function is enabled; a bit value of 0 means the
copying function is disabled.
If the copying function is enabled for Node n (where n = 0 to F hex or 0 to 15 decimal), during each
background “housekeeping” software cycle, PMAC copies the contents of Y:$000345n to the Node n
auxiliary write register, and copies the contents of the Node n auxiliary read register into X:$00345n.
The copying function enabled by I72 permits the use of the auxiliary registers for command and status
flags plus Type 0 auxiliary read and write functions in PLC programs and on-line commands.
For each node whose auxiliary functions are enabled by I72, I73 must correctly specify for the node
whether the Type 0 or Type 1 MACRO protocol is used.
If a value of I78 greater than 0 has been saved into PMAC’s non-volatile memory to enable Type 1
MACRO auxiliary communications with Node 15, then at subsequent power-up/resets, bit 15 of I72 is
automatically forced to 0 by PMAC firmware, regardless of the value saved for I72. This reserves Node
15 for the Type 1 auxiliary communications alone.
I74 controls which nodes of MACRO IC 2 for which Turbo PMAC performs automatic copying into and
out of the auxiliary registers. Enabling this function for a node is required to use the auxiliary register as
the flag register for a motor.
Note:
MACRO IC 2 can only be present on Turbo PMAC2 Ultralite boards with Option
1U2 ordered, or on a 3U Turbo PMAC2 with some configurations of its Acc-5E.
I74 is a 16-bit variable. Bits 0 to 15 control the enabling of this copying function for MACRO nodes 0 to
15, respectively. A bit value of 1 means the copying function is enabled; a bit value of 0 means the
copying function is disabled.
If the copying function is enabled for Node n (where n = 0 to F hex or 0 to 15 decimal), during each
background “housekeeping” software cycle, PMAC copies the contents of Y:$000346n to the Node n
auxiliary write register, and copies the contents of the Node n auxiliary read register into X:$00346n.
The copying function enabled by I74 permits the use of the auxiliary registers for command and status
flags plus Type 0 auxiliary read and write functions in PLC programs and on-line commands.
For each node whose auxiliary functions are enabled by I74, I75 must correctly specify for the node
whether the Type 0 or Type 1 MACRO protocol is used.
If a value of I78 greater than 0 has been saved into PMAC’s non-volatile memory to enable Type 1
MACRO auxiliary communications with Node 15, then at subsequent power-up/resets, bit 15 of I74 is
automatically forced to 0 by PMAC firmware, regardless of the value saved for I74. This reserves Node
15 for the Type 1 auxiliary communications alone.
I75 MACRO IC 2 Node Protocol Type Control
Range: 0 .. $FFFF (0 .. 65,535)
Units: none
Default: 0
I75 controls for each node (0 - 15) on MACRO IC 2 whether the matching slave node is expected to be
another Turbo PMAC or a slave-only “MACRO Station” for purposes of the protocol of exchanging non-
cyclic information. I75 is a 16-bit value; each bit 0 – 15 controls the protocol type for the MACRO node
of the same number. A value of 0 in the bit selects the “Turbo PMAC” protocol for the matching
MACRO node (using MX commands); a value of 1 in the bit selects the Type 1 protocol for the node
(using MS commands). The selection of the proper protocol is essential for the correct operation of
homing-search moves and other “move-until-trigger” functions, which require an MS or MX command to
obtain the trigger-captured position across the ring.
“MACRO Stations” include UMAC MACRO racks with 8 or 16-axis CPUs, Geo MACRO drives,
MACRO Peripheral modules, and 3rd-party MACRO devices. To use a Turbo PMAC as a slave on a
MACRO ring, V1.945 or newer firmware is required.
Prior to V1.945 firmware, a value of 0 in a bit selected the now-obsolete “Type 0” slave-only protocol for
the matching node.
I76 MACRO IC 3 Node Auxiliary Register Enable
Range: 0 .. $FFFF (0 .. 65,535)
Units: none
Default: 0
I76 controls which nodes of MACRO IC 3 for which Turbo PMAC performs automatic copying into and
out of the auxiliary registers. Enabling this function for a node is required to use the auxiliary register as
the flag register for a motor.
Note:
MACRO IC 3 can only be present on Turbo PMAC2 Ultralite boards with Option
1U3 ordered, or on a 3U Turbo PMAC2 with some configurations of its Acc-5E.
I76 is a 16-bit variable. Bits 0 to 15 control the enabling of this copying function for MACRO nodes 0 to
15, respectively. A bit value of 1 means the copying function is enabled; a bit value of 0 means the
copying function is disabled.
If the copying function is enabled for Node n (where n = 0 to F hex or 0 to 15 decimal), during each
background housekeeping software cycle, PMAC copies the contents of Y:$000347n to the Node n
auxiliary write register, and copies the contents of the Node n auxiliary read register into X:$00347n.
The copying function enabled by I76 permits the use of the auxiliary registers for command and status
flags plus Type 0 auxiliary read and write functions in PLC programs and on-line commands.
For each node whose auxiliary functions are enabled by I76, I77 must correctly specify for the node
whether the Type 0 or Type 1 MACRO protocol is used.
If a value of I78 greater than 0 has been saved into PMAC’s non-volatile memory to enable Type 1
MACRO auxiliary communications with Node 15, then at subsequent power-up/resets, bit 15 of I76 is
automatically forced to 0 by PMAC firmware, regardless of the value saved for I76. This reserves Node
15 for the Type 1 auxiliary communications alone.
I77 MACRO IC 3 Node Protocol Type Control
Range: 0 .. $FFFF (0 .. 65,535)
Units: none
Default: 0
I77 controls for each node (0 - 15) on MACRO IC 3 whether the matching slave node is expected to be
another Turbo PMAC or a slave-only “MACRO Station” for purposes of the protocol of exchanging non-
cyclic information. I77 is a 16-bit value; each bit 0 – 15 controls the protocol type for the MACRO node
of the same number. A value of 0 in the bit selects the “Turbo PMAC” protocol for the matching
MACRO node (using MX commands); a value of 1 in the bit selects the Type 1 protocol for the node
(using MS commands). The selection of the proper protocol is essential for the correct operation of
homing-search moves and other “move-until-trigger” functions, which require an MS or MX command to
obtain the trigger-captured position across the ring.
“MACRO Stations” include UMAC MACRO racks with 8 or 16-axis CPUs, Geo MACRO drives,
MACRO Peripheral modules, and 3rd-party MACRO devices. To use a Turbo PMAC as a slave on a
MACRO ring, V1.945 or newer firmware is required.
Prior to V1.945 firmware, a value of 0 in a bit selected the now-obsolete “Type 0” slave-only protocol for
the matching node.
I78 MACRO Type 1 Master/Slave Communications Timeout
Range: 0 .. 255
Units: Servo Cycles
Default: 0
I78 permits the enabling of MACRO Type 1 master-slave auxiliary communications using Node 15,
which are executed with the MS, MSR, and MSW commands. If I78 is set to 0, these communications are
disabled. If I78 is set to a value greater than 0, these communications are enabled, and the value of I78
sets the “timeout” value for the auxiliary response, in Turbo PMAC servo cycles.
If Turbo PMAC has not received a response to the MACRO auxiliary communications command within
I78 servo cycles, it will stop waiting and register a “MACRO Auxiliary Communications Error”, setting
Bit 5 of global status register X:$000006. A value of 32 for I78 is suggested.
Bit 15 of I70, I72, I74, and I76 must be set to 0 to disable Node 15’s Type 0 (node-specific) auxiliary
communications for each MACRO IC if I78 is greater than 0. If a value of I78 greater than 0 has been
saved into PMAC’s non-volatile memory, then at subsequent power-up/resets, bit 15 of I70, I72, I74, and
I76 are automatically forced to 0 by PMAC firmware, regardless of the value saved for I70.
This function is controlled by I1003 on non-Turbo PMACs.
I79 MACRO Type 1 Master/Master Communications Timeout
Range: 0 .. 255
Units: Servo Cycles
Default: 0
I79 permits the enabling of MACRO Type 1 master-to-master auxiliary communications using Node 14,
which are executed with the MM, MMR, and MMW commands. If I79 is set to 0, these communications are
disabled. If I79 is set to a value greater than 0, these communications are enabled, and the value of I79
sets the timeout value for the auxiliary response, in Turbo PMAC servo cycles.
If Turbo PMAC has not received a response to the MACRO auxiliary communications command within
I79 servo cycles, it will stop waiting and register a MACRO Auxiliary Communications Error, setting Bit
5 of global status register X:$000006. A value of 32 for I79 is suggested.
Bit 14 of I70 must be set to 0 to disable Node 14’s Type 0 (node-specific) auxiliary communications if
I79 is greater than 0. If a value of I79 greater than 0 has been saved into PMAC’s non-volatile memory,
then at subsequent power-up/resets, bit 14 of I70 is automatically forced to 0 by PMAC firmware,
regardless of the value saved for I70.
Certain master-to-master communications registers are only set up at the Turbo PMAC power-up/reset, so
before master-to-master communications can be performed, a non-zero value of I79 must be stored in
flash memory with the SAVE command, and the board must be reset.
I80 MACRO Ring Check Period
Range: 0 .. 255
Units: servo cycles
Default: 0
I80 determines the period for Turbo PMAC to evaluate whether there has been a MACRO ring failure. If I80
is greater than 0, Turbo PMAC must receive the sync node packet (as specified by I6841) at least I82 times
within I80 servo cycles. It also must detect less than I81 ring errors (byte violation error, packet parity error,
packet overflow error, or packet underflow error) in this same period, and find no errors for at least one of its
checks during the period. If either of these conditions is not met, Turbo PMAC will assume it is a ring fault,
and will disable all motors.
If I80 is 0, Turbo PMAC does not perform these checks, even if MACRO is active.
A ring check period of about 20 milliseconds is recommended in a typical MACRO application. I80 can
be set as function of the desired period according to the formula:
I80 = Desired ring check period (msec) * Servo update frequency (kHz)
If I80 is greater than 0, activating this check function, bits 16 to 19 of I6841 (Sync Packet Number) must
specify the number of a packet that is regularly being received by this card. Otherwise, Turbo PMAC will
immediately detect a ring fault. Typically, Packet 15 ($F) is used as the sync packet, and it is always sent
because bit 15 of I6841 is set to 1 to activate the node to send the packet around the ring every cycle.
When a ring fault is detected, Turbo PMAC sets bit 4 of global status word X:$000006 to 1. It disables
all motors using the MACRO ring, and attempts to notify all of its MACRO slave stations that a ring fault
has occurred.
Turbo PMAC performs this check each real-time interrupt (every I8+1 servo cycles), so it will perform
I80 / (I8 + 1) checks during the check period. This value must be greater than I82, or ring failures will be
detected because not enough checks were done to detect the required number of sync packets received.
This function is controlled by I1001 on non-Turbo PMACs.
I81 MACRO Maximum Ring Error Count
Range: 0 .. 255
Units: Detected ring errors
Default: 2
I81 sets the maximum number of MACRO ring communications errors that can be detected in one ring
check period before a MACRO communications fault is declared. The ring check period is set at I80
servo cycles; if I80 is 0, this checking is not performed.
There are four types of ring communications errors that can be detected: byte violation errors, packet
parity errors, packet overflow errors, and packet underflow errors. If any one of these is detected during a
check, this counts as a ring error towards the I81 counts.
Turbo PMAC performs the check every real-time interrupt (every I8+1 servo cycles), so it will perform
I80 / (I8 + 1) checks during the check period. If I81 or more ring errors are detected during this period, a
ring fault is declared, and the ring is shut down. Regardless of the setting of I81, if a ring error is detected
on every check during the period, a ring fault is declared.
This function is controlled by I1004 on non-Turbo PMACs.
I82 MACRO Minimum Sync Packet Count
Range: 0 .. 255
Units: Detected sync packets
Default: 2
I82 sets the minimum number of MACRO sync packets that must be received in one ring check period for
Turbo PMAC to conclude that the ring is operating properly. The ring check period is set at I80 servo
cycles; if I80 is 0, this checking is not performed.
The number of the sync packet is determined by bits 16 – 19 of I6841. Usually Packet 15 is used as the
sync packet, and its transmission around the ring is enabled by setting bit 15 of I6841 to 1, activating
Node 15. If the sync packet is defined as a packet that is not regularly transmitted around the ring, this
check will shut down the ring immediately.
If fewer than I82 sync packets are detected during any ring check period of I80 servo cycles, Turbo
PMAC will shut down operation of the ring, declaring a ring fault. Turbo PMAC performs the check
during the real-time interrupt (every I8+1 servo cycles), so it will perform I80 / (I8 + 1) checks during the
check period. If I82 is set to a value greater than I80 / (I8 +1), Turbo PMAC will find a ring fault
immediately.
This function is controlled by I1005 on non-Turbo PMACs.
I83 MACRO Parallel Ring Enable Mask
Range: 0 – 15
Units: none
Default: 0
I83 specifies which MACRO ICs on Turbo PMAC2 control their own independent rings so independent
checking of ring communications using variables I80 to I82 is done using registers in that MACRO IC.
I83 is a 4-bit value. Bit n of I83 corresponds to MACRO IC n. If bit n is set to 1, ring checking is
performed using registers in MACRO IC n. If bit n is set to 0, no ring checking is performed using
registers in MACRO IC n. (However, if all bits are 0, checking can still be done on MACRO IC 0; see
below.)
I80 must be set greater than 0 to specify a ring-check period and activate any ring checking. If I80 is set
greater than 0, ring checking is done automatically on MACRO IC 0, so bit 0 if I83 is not used. However,
if multiple rings are used, it is recommended that Bit 0 be set to 1 for clarity’s sake.
Presently, only the UMAC configuration of the Turbo PMAC2 supports multiple rings (through multiple
Acc-5E boards). All other versions of Turbo PMAC2 can only support a single ring and do ring checking
on MACRO IC 0. For these boards, I83 can be left at the default value of 0.
If multiple MACRO ICs share a common ring, the lowest-numbered MACRO IC on the ring should be
used for ring checking. For example, if MACRO ICs 0 and 1 share one ring, and MACRO ICs 2 and 3
share another, bits 0 and 2 of I83 should be set to 1, yielding a value of 5.
I-variables I20 – I23 specify the base addresses of MACRO ICs 0 – 3, respectively. These must be set
correctly in order for the ring-checking function on these ICs to work properly.
The following table shows which MACRO rings are enabled by the I83 bits.
I83 Bit #, Bit Value I-Variable for
MACRO IC # IC Address
0 1 I20
1 2 I21
2 4 I22
3 8 I23
See Also:
I-Variables I20 – I23, I80 – I82
I84 MACRO IC # for Master Communications
Range: 0–3
Units: MACRO IC #
Default: 0
I84 specifies which MACRO IC on the Turbo PMAC2 is used for “MACRO Master” communications
with the MACROMSTASCII, MACROSTASCII, MACROMSTREAD, and MACROMSTWRITE commands.
I84 can take a value from 0 to 3. The value of I84 specifies that the MACRO IC of that number will be
used. Variables I20 – I23 specify the base addresses of MACRO ICs 0 – 3, respectively.
Note:
The UMAC Turbo firmware will support up to four parallel MACRO Rings and, if
desired up to sixteen by changing I20 – I23 before initiating communication over
the MACRO Ring. Each parallel MACRO Ring will be a Ring Controller with the
MACRO IC tied to I20 being the source of the Phase and Servo clock.
See Also:
I-variables I20 – I23
Commands MACROMASTASCII, MACROSTASCII, MACROMSTREAD, MACROMSTWRITE
I85 MACRO Ring Order Number
Range: 0 – 254
Units: none
Default: 0
I85 is used to store the order of the Turbo PMAC2 in the MACRO ring. The first device (Turbo PMAC2,
MACRO Station, or other device) “downstream” in the ring from the ring controller is 1, the next is 2,
and so on. If I85 is 0, the Turbo PMAC2 has not been assigned an order in the ring yet.
If I85 has a value from 1 to 254, the Turbo PMAC2 will respond when the {constant} in the
MACROSTASCII{constant} command matches the value of I85. The first device in the ring with I85
= 0 will respond to the MACROSTASCII255 command.
Note:
For the ring controller, I85 should remain at 0, even though it has no effect on the
ordered ring communications.
The STN command will return the value of I85.
See Also:
Commands MACROSTASCII, STN
VME/DPRAM Setup I-Variables
I90 VME Address Modifier
Range: $00 - $FF
Units: None
Default: $39
I90 controls which address modifier value Turbo PMAC will respond to when sent by the VME bus host.
I90 takes one of three valid values in normal use, depending on the address bus width used:
I90 = $29: 16-bit addressing
I90 = $39: 24-bit addressing
I90 = $09: 32-bit addressing
I90 is actually used at power-on/reset only, so to set or change the VME address modifier, change the
value of I90, store this new value to non-volatile flash memory with the SAVE command, and reset the
card with the $$$ command. The active register into which the value of I90 is copied at power-on/reset
is X:$070006 bits 0 – 7. It is permissible to write to this register directly (suggested M-variable M90) to
change the active setup without a SAVE and reset.
I91 VME Address Modifier Don’t Care Bits
Range: $00 - $FF
Units: None
Default: $04
I91 controls which bits of the I90 VME address modifier are “don’t care” bits. I91 is set to $04 in all
normal use, which permits both “non-privileged” and “supervisory” data access by the VME host.
I91 is actually used at power-on/reset only, so to set or change the VME address modifier don’t care bits,
change the value of I91, store this new value to non-volatile flash memory with the SAVE command, and
reset the card with the $$$ command. The active register into which the value of I91 is copied at power-
on/reset is X:$070007 bits 0 – 7. It is permissible to write to this register directly (suggested M-variable
M91) to change the active setup without a SAVE and reset.
I92 VME Base Address Bits A31-A24
Range: $00 - $FF
Units: None
Default: $FF
I92 controls bits A31 through A24 of the VME bus base address of Turbo PMAC, both for the mailbox
registers, and the dual-ported RAM. It is only used if 32-bit addressing has been selected with I90 and
I99.
I92 is actually used at power-on/reset only, so to set or change bits 16-23 of the VME bus base address,
change the value of I92, store this new value to non-volatile flash memory with the SAVE command, and
reset the card with the $$$ command. The active register into which the value of I92 is copied at power-
on/reset is X:$070008 bits 0 – 7. It is permissible to write to this register directly (suggested M-variable
M92) to change the active setup without a SAVE and reset.
I93 VME Mailbox Base Address Bits A23-A16 ISA DPRAM Base Address Bits A23-
A16
Range: $00 - $FF
Units: None
Default: $7F (VME); $0D (ISA)
On VME bus systems, I93 controls bits A23 through A16 of the VME bus base address of the mailbox
registers for Turbo PMAC. Bit 7 of I93 corresponds to A23 of the base address, and bit 0 of I93
corresponds to A16. I93 is only used on VME systems if 24-bit or 32-bit addressing has been selected
with I90 and I99.
On ISA bus systems (PC, PC Ultralite, 3U Turbo with PC/104), I93 controls bits A23 through A16 of the
ISA bus base address of the DPRAM. Bit 7 of I93 corresponds to A23 of the base address, and bit 0 of
I93 corresponds to A16. A23 through A20 are only used on ISA bus systems if bit 2 of I94 is set to 1,
enabling 24-bit addressing.
Note:
When DPRAM is used on the PCI bus, Universal Serial Bus (USB), or Ethernet,
the host address is set by a “plug-and-play” process, and I93 is not used.
I93 is actually used at power-on/reset only, so to set or change the base address, change the value of I93,
store this new value to non-volatile flash memory with the SAVE command, and reset the card with the
$$$ command. The active register into which the value of I93 is copied at power-on/reset is X:$070009
bits 0 – 7. It is permissible to write to this register directly (suggested M-variable M93) to change the
active setup without a SAVE and reset.
I94 VME Mailbox Base Address Bits A15-A08 ISA DPRAM Base Address Bits A15-
A14 & Control
Range: $00 - $FF
Units: None
Default: $A0 (VME); $45 (ISA)
On VME bus systems, I94 controls bits A15 through A08 of the VME bus base address of the mailbox
registers of Turbo PMAC. Bit 7 of I93 corresponds to A23 of the base address, and bit 0 of I93
corresponds to A16. I94 is used whether 16-bit, 24-bit, or 32-bit addressing has been selected with I90
and I99.
On ISA bus systems (PC, PC Ultralite, 3U Turbo with PC/104), I94 controls the enable state and
addressing mode of the DPRAM. If the DPRAM is to appear as a 16k block of memory on the ISA bus,
it also sets bits A15 and A14 of the ISA bus base address.
The first hex digit of I94 contains bits 4 – 7. When the DPRAM is addressed as a 16k x 8 block of
memory on the ISA bus, bit 7 of I94 corresponds to A15, and bit 6 of I94 corresponds to A14. Bits 5 and
4 must be set to 0. When the extended 32k x 8 DPRAM is addressed as a 64k x 8 block of memory on
the ISA bus, bits 7 through 4 of I94 must all be set to 0.
The second hex digit of I94 contains bits 0 – 3. These are individual control bits. Bits 0 and 2 control the
addressing mode and block size. Bits 1 and 3 control the bank selection if the large DPRAM is addressed
as a small block of memory. Usually, these should be set to 0 in the I-variable. The commonly used
settings of the second hex digit of I94 are:
0: DPRAM not enabled
1: 20-bit addressing (below 1M), 16k x 8 address block
4: 24-bit addressing (above or below 1M), 64k x 8 address block
5: 24-bit addressing (above or below 1M), 16k x 8 address block
Note:
When DPRAM is used on the PCI bus, Universal Serial Bus (USB), or Ethernet,
the host address is set by a “plug-and-play” process, and I94 is not used.
Actually I94 is used at power-on/reset only, so to set or change, and keep, these settings, change the value
of I94, store this new value to non-volatile flash memory with the SAVE command, and reset the card
with the $$$ command. The active register into which the value of I94 is copied at power-on/reset is
X:$07000A bits 0 – 7. It is permissible to write to this register directly (suggested M-variable M94) to
change the active setup without a SAVE and reset.
If the large (32k x 16) DPRAM is addressed through a small (16k x 8) address block, it is necessary to
change the bank select bits (bits 1 and 3) of the active register to access all of the DPRAM from the PC.
This is best done through the active control register at X:$07000A using suggested M-variable M94. The
bit settings are:
Bit 1 = 0, Bit 3 = 0: Bank 0 (PMAC addresses $060000 - $060FFF)
Bit 1 = 1, Bit 3 = 0: Bank 1 (PMAC addresses $061000 - $061FFF)
Bit 1 = 0, Bit 3 = 1: Bank 2 (PMAC addresses $062000 - $062FFF)
Bit 1 = 1, Bit 3 = 1: Bank 3 (PMAC addresses $063000 - $063FFF)
put a line of text in the DPRAM ASCII response buffer and is ready for the host computer to read this, the
interrupt vector value will be equal to (I96+1).
If there are multiple Turbo PMAC boards asserting the same interrupt level in the VME bus as set by I95,
they each must assert a unique, non-overlapping set of interrupt vectors.
I96 is actually used at power-on/reset only, so to set or change the VME interrupt vector, change the value
of I96, store this new value to non-volatile flash memory with the SAVE command, and reset the card
with the $$$ command. The active register into which the value of I96 is copied at power-on/reset is
X:$07000C bits 0 – 7. It is permissible to write to this register directly (suggested M-variable M96) to
change the active setup without a SAVE and reset.
I97 VME DPRAM Base Address Bits A23-A20
Range: $00 - $FF
Units: None
Default: $00
I97 controls bits A23 through A20 of the VME bus base address of the dual-ported RAM of Turbo
PMAC. Bit 3 of I93 corresponds to A20 of the base address, and bit 0 of I93 corresponds to A16. I97 is
only used if 24-bit or 32-bit addressing has been selected with I90 and I99.
Bits A19 through A14 of the DPRAM VME base address must be set by the host computer after every
power-on/reset by writing a byte over the bus to the “page select” register in the Turbo PMAC’s VME
mailbox IC at the mailbox base address + $0121. This must be done even with the single-page 8k x 16
standard DPRAM option. With the extended DPRAM option, the host computer must write to the page
select register every time a new page is accessed.
Actually I97 is used at power-on/reset only, so to set or change bits 8 to 15 of the VME bus DPRAM base
address, change the value of I97, store this new value to non-volatile flash memory with the SAVE
command, and reset the card with the $$$ command. The active register into which the value of I97 is
copied at power-on/reset is X:$07000D bits 0 – 7. It is permissible to write to this register directly
(suggested M-variable M97) to change the active setup without a SAVE and reset.
I98 VME DPRAM Enable
Range: $00 - $FF
Units: None
Default: $60
I98 controls whether VME access to the DPRAM IC on the Turbo PMAC is enabled or not. It should be
set to $60 if DPRAM is not present to disable access; it should be set to $E0 if DPRAM is present to
enable access.
Actually I98 is used at power-on/reset only, so to set or change the DPRAM enabling, change the value of
I98, store this new value to non-volatile flash memory with the SAVE command, and reset the card with
the $$$ command. The active register into which the value of I98 is copied at power-on/reset is
X:$07000E bits 0 – 7. It is permissible to write to this register directly (suggested M-variable M98) to
change the active setup without a SAVE and reset.
I99 VME Address Width Control
Range: $00 - $FF
Units: None
Default: $10
I99 controls the VME bus address width, with or without DPRAM. It should take one of six values in
normal use:
commands. If Ixx82 is set greater than zero, then the Turbo PMAC performs current-loop calculations as
well as commutation, and it outputs three phase-voltage commands.
Summarizing the values of Ixx01, and their effect:
Ixx01 = 0: No Turbo PMAC commutation, command output to Y-register
Ixx01 = 1: Turbo PMAC commutation, commutation feedback from X-register
(used for commutating with PMAC encoder register feedback)
Ixx01 = 2: No Turbo PMAC commutation, command output to X-register
Ixx01 = 3: Turbo PMAC commutation, commutation feedback from Y-register
(used for commutating with feedback from MACRO ring)
Ixx02 Motor xx Command Output Address
Range: $000000 - $FFFFFF
Units: Turbo PMAC Addresses
Turbo PMAC Ixx02 Defaults
Ixx02 Value Register Ixx02 Value Register
I102 $078003 PMAC DAC1 I1702 $079203 Second Acc-24P/V DAC1
I202 $078002 PMAC DAC2 I1802 $079202 Second Acc-24P/V DAC2
I302 $07800B PMAC DAC3 I1902 $07920B Second Acc-24P/V DAC3
I402 $07800A PMAC DAC4 I2002 $07920A Second Acc-24P/V DAC4
I502 $078103 PMAC DAC5 I2102 $079303 Second Acc-24P/V DAC5
I602 $078102 PMAC DAC6 I2202 $079302 Second Acc-24P/V DAC6
I702 $07810B PMAC DAC7 I2302 $07930B Second Acc-24P/V DAC7
I802 $07810A PMAC DAC8 I2402 $07930A Second Acc-24P/V DAC8
I902 $078203 First Acc-24P/V DAC1 I2502 $07A203 Third Acc-24P/V DAC1
I1002 $078202 First Acc-24P/V DAC2 I2602 $07A202 Third Acc-24P/V DAC2
I1102 $07820B First Acc-24P/V DAC3 I2702 $07A20B Third Acc-24P/V DAC3
I1202 $07820A First Acc-24P/V DAC4 I2802 $07A20A Third Acc-24P/V DAC4
I1302 $078303 First Acc-24P/V DAC5 I2902 $07A303 Third Acc-24P/V DAC5
I1402 $078302 First Acc-24P/V DAC6 I3002 $07A302 Third Acc-24P/V DAC6
I1502 $07830B First Acc-24P/V DAC7 I3102 $07A30B Third Acc-24P/V DAC7
I1602 $07830A First Acc-24P/V DAC8 I3202 $07A30A Third Acc-24P/V DAC8
Turbo PMAC2 Ixx02 Defaults
Ixx02 Value Register Ixx02 Value Register
I102 $078002 PMAC2 DAC/PWM1A I1702 $079202 Second Acc-24P/V2 DAC/PWM1A
I202 $07800A PMAC2 DAC/PWM2A I1802 $07920A Second Acc-24P/V2 DAC/PWM2A
I302 $078012 PMAC2 DAC/PWM3A I1902 $079212 Second Acc-24P/V2 DAC/PWM3A
I402 $07801A PMAC2 DAC/PWM4A I2002 $07921A Second Acc-24P/V2 DAC/PWM4A
I502 $078102 PMAC2 DAC/PWM5A I2102 $079302 Second Acc-24P/V2 DAC/PWM5A
I602 $07810A PMAC2 DAC/PWM6A I2202 $07930A Second Acc-24P/V2 DAC/PWM6A
I702 $078112 PMAC2 DAC/PWM7A I2302 $079312 Second Acc-24P/V2 DAC/PWM7A
I802 $07811A PMAC2 DAC/PWM8A I2402 $07931A Second Acc-24P/V2 DAC/PWM8A
I902 $078202 First Acc-24P/V2 DAC/PWM1A I2502 $07A202 Third Acc-24P/V2 DAC/PWM1A
I1002 $07820A First Acc-24P/V2 DAC/PWM2A I2602 $07A20A Third Acc-24P/V2 DAC/PWM2A
I1102 $078212 First Acc-24P/V2 DAC/PWM3A I2702 $07A212 Third Acc-24P/V2 DAC/PWM3A
I1202 $07821A First Acc-24P/V2 DAC/PWM4A I2802 $07A21A Third Acc-24P/V2 DAC/PWM4A
I1302 $078302 First Acc-24P/V2 DAC/PWM5A I2902 $07A302 Third Acc-24P/V2 DAC/PWM5A
I1402 $07830A First Acc-24P/V2 DAC/PWM6A I3002 $07A30A Third Acc-24P/V2 DAC/PWM6A
I1502 $078312 First Acc-24P/V2 DAC/PWM7A I3102 $07A312 Third Acc-24P/V2 DAC/PWM7A
I1602 $07831A First Acc-24P/V2 DAC/PWM8A I3202 $07A31A Third Acc-24P/V2 DAC/PWM8A
Turbo PMAC2 Ultralite Ixx02 Defaults
Ixx02 Value Register Ixx02 Value Register
I102 $078420 MACRO IC 0 Node 0 Reg. 0 I1702 $07A420 MACRO IC 2 Node 0 Reg. 0
I202 $078424 MACRO IC 0 Node 1 Reg. 0 I1802 $07A424 MACRO IC 2 Node 1 Reg. 0
I302 $078428 MACRO IC 0 Node 4 Reg. 0 I1902 $07A428 MACRO IC 2 Node 4 Reg. 0
I402 $07842C MACRO IC 0 Node 5 Reg. 0 I2002 $07A42C MACRO IC 2 Node 5 Reg. 0
I502 $078430 MACRO IC 0 Node 8 Reg. 0 I2102 $07A430 MACRO IC 2 Node 8 Reg. 0
I602 $078434 MACRO IC 0 Node 9 Reg. 0 I2202 $07A434 MACRO IC 2 Node 9 Reg. 0
I702 $078438 MACRO IC 0 Node 12 Reg. 0 I2302 $07A438 MACRO IC 2 Node 12 Reg. 0
I802 $07843C MACRO IC 0 Node 13 Reg. 0 I2402 $07A43C MACRO IC 2 Node 13 Reg. 0
The default values listed above are usually suitable for commanding analog output pairs when the Turbo
PMAC is commutating the motor, but not closing the current loop.
Commutation and Current Loop: If Turbo PMAC is commutating Motor xx (Ixx01=1 or 3) and
closing its current loop (Ixx82>0), three command output values are calculated, which are written to the
Y-register at the address specified in Ixx02, plus the Y-registers at the next two higher addresses.
The default values listed above are usually suitable for commanding three-phase PWM sets when the
Turbo PMAC is commutating the motor, and closing the current loop.
Pulse Frequency Output: One common application type for which the default value of Ixx02 cannot be
used is the direct pulse-and-direction output for stepper motor drives (Turbo PMAC2 only). This mode
uses the ‘C’ output register alone for each channel, and I7mn6 for Servo IC m Channel n must be set to 2
or 3 to get pulse frequency output. In this case, the following values should be used:
Turbo PMAC2 Ixx02 Pulse Frequency Output Settings
Servo Chan. 1 Chan. 2 Chan. 3 Chan. 4 Notes
IC #
0 $078004 $07800C $078014 $07801C First IC on board PMAC2, 3U stack
1 $078104 $07810C $078114 $07811C Second IC on board PMAC2, 3U stack
2 $078204 $07820C $078214 $07821C First Acc-24E2x, first IC on first Acc-24P/V2
3 $078304 $07830C $078314 $07831C Second Acc-24E2x, second IC on first Acc-24P/V2
4 $079204 $07920C $079214 $07921C Third Acc-24E2x, first IC on second Acc-24P/V2
5 $079304 $07930C $079314 $07931C Fourth Acc-24E2x, second IC on second Acc-24P/V2
6 $07A204 $07A20C $07A214 $07A21C Fifth Acc-24E2x, first IC on third Acc-24P/V2
7 $07A304 $07A30C $07A314 $07A31C Sixth Acc-24E2x, second IC on third Acc-24P/V2
8 $07B204 $07B20C $07B214 $07B21C Seventh Acc-24E2x, first IC on fourth Acc-24P/V2
9 $07B304 $07B30C $07B314 $07B31C Eighth Acc-24E2x, second IC on fourth Acc-24P/V2
MACRO Type 1 Command Outputs: To write command outputs to MACRO registers for Type 1
MACRO devices such as the Delta Tau MACRO Station, the values of Ixx02 shown above as defaults for
the Turbo PMAC2 Ultralite can be used.
MACRO Type 0 Command Outputs: To write single velocity or torque command outputs to MACRO
registers for Type 0 MACRO drives such as the Performance Controls FLX Drive and the Kollmorgen
FAST Drive, the values of Ixx02 in the following table should be used. Each value can select two
registers (e.g. for Node 0 and Node 2). To select the lower-numbered node’s register, which is a Y-
register in Turbo PMAC, Ixx01 should be set to 0; to select the higher-numbered node’s register, which is
a Y-register, Ixx01 should be set to 2.
Ixx02 for Type 0 MACRO Commands
Ixx02 Value Register Ixx02 Value Register
I102 $078423 MACRO IC 0 Node 0/2 Reg. 3 I1702 $07A423 MACRO IC 2 Node 0/2 Reg. 3
I202 $078427 MACRO IC 0 Node 1/3 Reg. 3 I1802 $07A427 MACRO IC 2 Node 1/3 Reg. 3
I302 $07842B MACRO IC 0 Node 4/6 Reg. 3 I1902 $07A42B MACRO IC 2 Node 4/6 Reg. 3
I402 $07842F MACRO IC 0 Node 5/7 Reg. 3 I2002 $07A42F MACRO IC 2 Node 5/7 Reg. 3
I502 $078433 MACRO IC 0 Node 8/10 Reg. 3 I2102 $07A433 MACRO IC 2 Node 8/10 Reg. 3
I602 $078437 MACRO IC 0 Node 9/11 Reg. 3 I2202 $07A437 MACRO IC 2 Node 9/11 Reg. 3
I702 $07843B MACRO IC 0 Node 12/14 Reg. 3 I2302 $07A43B MACRO IC 2 Node 12/14 Reg. 3
I802 $07843F MACRO IC 0 Node 13/15 Reg. 3 I2402 $07A43F MACRO IC 2 Node 13/15 Reg. 3
I902 $079423 MACRO IC 1 Node 0/2 Reg. 3 I2502 $07B423 MACRO IC 3 Node 0/2 Reg. 3
I1002 $079427 MACRO IC 1 Node 1/3 Reg. 3 I2602 $07B427 MACRO IC 3 Node 1/3 Reg. 3
I1102 $07942B MACRO IC 1 Node 4/6 Reg. 3 I2702 $07B42B MACRO IC 3 Node 4/6 Reg. 3
I1202 $07942F MACRO IC 1 Node 5/7 Reg. 3 I2802 $07B42F MACRO IC 3 Node 5/7 Reg. 3
I1302 $079433 MACRO IC 1 Node 8/10 Reg. 3 I2902 $07B433 MACRO IC 3 Node 8/10 Reg. 3
I1402 $079437 MACRO IC 1 Node 9/11 Reg. 3 I3002 $07B437 MACRO IC 3 Node 9/11 Reg. 3
I1502 $07943B MACRO IC 1 Node 12/14 Reg. 3 I3102 $07B43B MACRO IC 3 Node 12/14 Reg. 3
I1602 $07943F MACRO IC 1 Node 13/15 Reg. 3 I3202 $07B43F MACRO IC 3 Node 13/15 Reg. 3
Note:
To use Turbo PMAC’s hardware position-capture feature for homing search moves
or other types of automatic move-until-trigger (Ixx97=0), the encoder channel
number addressed by Ixx03 through the Encoder Conversion Table must match the
channel number of the flags addressed by Ixx25.
bits of fractional data). The result registers in the Encoder Conversion Table are located at addresses
X:$003501 to X:$0035C0, corresponding to table setup I-variables I8000 to I8191, respectively.
For a control-loop with only a single feedback device – the usual case – Ixx03 and Ixx04 will have the
same value, so the same register is used for both position and velocity loops. For a control loop with dual
feedback, motor and load, use Ixx03 to point to the encoder on the load for the position loop, and Ixx04 to
point to the encoder on the motor for the velocity loop. If the velocity loop uses feedback with different
resolution from the position loop, the Ixx09 velocity-loop scale factor should be different from the Ixx08
position-loop scale factor.
Ixx05 Motor xx Master Position Address
Range: $000000 - $FFFFFF
Units: Turbo PMAC ‘X’ Addresses
Default: $0035C0 (end of conversion table)
WARNING:
Never use the same register for master position and feedback position for the same
motor. A dangerous runaway condition may result.
Ixx05 specifies the address of the register for master position information of Motor xx for the position
following, or electronic gearing, function. Typically, this is a register in the encoder conversion table
(addresses $003501 to $0035C0), where processed input position data resides.
The position following function is only enabled if Ixx06 is set to 1 or 3.
Ixx06 Motor xx Position Following Enable and Mode
Range: 0-3
Units: none
Default: 0
Ixx06 controls the position following function for Motor xx. It determines whether following is enabled
or disabled, and whether the following function is in normal mode or offset (superimpose) mode.
Normal Mode: In normal following mode, motor position changes due to following are reported when
the motor position is queried, and subsequent programmed moves for the motor cancel out the position
changes due to the following function.
Offset Mode: In offset following mode, motor position changes due to following are not reported when
the motor position is queried (the position reference is effectively offset for the motor), and subsequent
programmed moves are added on top of the position changes due to the following function. This permits
the superimposition of programmed and following moves in offset mode.
Ixx06 is a two-bit value. Bit 0 controls the enabling of the following function (0 = disabled, 1 = enabled).
Bit 1 controls the following mode (0 = normal mode, 1 = offset mode). This yields four possible values
for Ixx06:
Ixx06 = 0: Following disabled, normal mode
Ixx06 = 1: Following enabled, normal mode
Ixx06 = 2: Following disabled, offset mode
Ixx06 = 3: Following enabled, offset mode
Note:
The following mode can be important even when following is disabled, because it
affects how subsequent programmed moves are calculated. If the following mode
is ever changed, a PMATCH position-matching command must be executed before
the next programmed move is calculated. Otherwise, that move will use the wrong
value for its starting position, and a potentially dangerous jump will occur.
(PMATCH is automatically executed on an R (run) or S (step) command.)
Ixx07 Motor xx Master (Handwheel) Scale Factor
Range: -8,388,608 - 8,388,607
Units: none
Default: 96
Ixx07 controls with what scaling the master (handwheel) register gets multiplied when extended into the
full-length register. In combination with Ixx08, it controls the following ratio of Motor xx for position
following (electronic gearing) according to the equation:
Ixx07
MotorPosition MasterPosition
Ixx08
For this position-following function, Ixx07 and Ixx08 can be thought of as the number of teeth on
meshing gears in a mechanical coupling.
Ixx07 may be changed on the fly to permit real-time changing of the following ratio, but Ixx08 may not.
Ixx08 should therefore be set to a large enough value to get the required fineness of ratio changes.
Ixx08 Motor xx Position Scale Factor
Range: 0 - 8,388,607
Units: none
Default: 96
Ixx08 specifies the multiplication scale factor for the internal position registers for Motor xx. Source
position registers are multiplied by Ixx08 as the get extended into the full-length motor position registers.
For most purposes, this is transparent to the user and Ixx08 does not need to be changed from the default.
There are two reasons that the user might want to change this from the default value. First, because it is
involved in the gear ratio of the position following function -- the ratio is Ixx07/Ixx08 – the value of
Ixx08 might be changed (usually raised) to get a more precise ratio.
The second reason to change this parameter (usually lowering it) is to prevent internal saturation at very
high gains or count rates (velocity). PMAC's filter will saturate when the velocity in counts/sec
multiplied by Ixx08 exceeds 768M (805,306,368), or 256M (268,435,456) in PVT mode. This only
happens in very rare applications -- the count rate must exceed 8.3 million counts per second (2.8 million
in PVT mode) before the default value of Ixx08 gives a problem.
Note:
When changing this parameter, make sure the motor is killed (disabled).
Otherwise, a sudden jump will occur, because the internal position registers will
have changed. This means that this parameter should not be changed in the middle
of an application. If a real-time change in the position-following gear ratio is
desired, Ixx07 should be changed.
In most practical cases, Ixx08 should not be set above 1000 because higher values can make the servo
filter saturate too easily. If Ixx08 is changed, Ixx30 should be changed inversely to keep the same servo
performance (e.g. if Ixx08 is doubled, Ixx30 should be halved).
Ixx09 Motor xx Velocity-Loop Scale Factor
Range: 0 - 8,388,607
Units: none
Default: 96
Ixx09 specifies the multiplication scale factor for the internal actual velocity registers for Motor xx.
Source position registers for the velocity loop are multiplied by Ixx09 before they are compared and used
in the velocity loop. For most purposes, this is transparent to the user and Ixx09 does not need to be
changed from the default.
This parameter should not be changed in the middle of an application, because it scales many internal
values. If the same sensor is used to close both the position and velocity loops (Ixx03=Ixx04), Ixx09
should be set equal to Ixx08.
If different sensors are used, Ixx09 should be set such that the ratio of Ixx09 to Ixx08 is inversely
proportional to the ratio of the velocity sensor resolution (at the load) to the position sensor resolution. If
the value computed this way for Ixx09 does not come to an integer, use the nearest integer value.
Example:
If a 5000 line/inch (20,000 cts/in) linear encoder is used for position feedback, and a 500 line/rev (2000
cts/rev) rotary encoder is used for velocity loop feedback, and there is a 5-pitch screw, the effective
resolution of the velocity encoder is 10,000 cts/in (2000*5), half of the position sensor resolution, so
Ixx09 should be set to twice Ixx08.
Ixx10 Motor xx Power-On Servo Position Address
Range: $000000 - $FFFFFF
Units: Turbo PMAC or Multiplexer Port Addresses
Default: $0
Ixx10 controls whether Turbo PMAC reads an absolute position sensor for Motor xx on power-up/reset
and/or with the $* or $$* commands. If an absolute position read is to be done, Ixx10 specifies what
register is read for that absolute position data. Ixx95 specifies how the data in this register is interpreted.
If Ixx10 is set to 0, no absolute power-on/reset position read is performed. The power-on/reset position is
considered to be zero, even if an absolute sensor reporting a non-zero value is used. Ixx10 should be set
to 0 when an incremental position sensor is used; a homing search move is typically then executed to
establish a position reference.
If Ixx10 is set to a non-zero value, an absolute position read is performed for Motor xx at power-on/reset,
from the register whose location is specified in Ixx10 (unless Bit 2 of Ixx80 is set to 1). This is either the
address of a Turbo PMAC register, the multiplexed data address on the Multiplexer Port, or the number of
the MACRO node on the Turbo PMAC, depending on the setting of Ixx95. The motor’s position is set to
the value read from the sensor location the Ixx26 home offset value.
Ixx10 is used only on power-on/reset, when the $* command is issued for the motor, or when the $$*
command is issued for the coordinate system containing the motor. To get a new value of Ixx10 to take
effect, either the $* or $$* command must be issued, or the value must be stored to non-volatile flash
memory with the SAVE command, and the board must be reset.
Note:
Variable Ixx81 (with Ixx91) performs the same power-on position read function
for the phasing (commutation) algorithm.
R/D Converter Read: If Ixx95 is set to a value from $000000 to $070000, or from $800000 to $870000,
the address specified in Ixx10 is a Multiplexer Port address. Turbo PMAC will read the absolute position
from an Acc-8D Opt 7 Resolver-to-Digital Converter board at that port address, as set by DIP switches on
the board. Ixx95 specifies which R/D converter at that address is read, and whether it is treated as a
signed or unsigned value.
If Ixx99 is greater than 0, the next R/D converter at that port address is also read as a second geared-down
resolver, with Ixx99 setting the gear ratio. If Ixx98 is also greater than 0, the next R/D converter past that
one at the same port address is read as a third geared-down resolver, with Ixx98 setting the gear ratio.
In this mode, bits 1 through 7 of Ixx10 match the settings of DIP-switches SW1-2 through SW1-8,
respectively, on the Acc-8D Opt 7 R/D Converter board. A Closed (ON) switch represents a 0 value; an
Open (OFF) switch represents a 1 value. Bit 0 and bits 9 through 23 of Ixx10 are always set to 0 in this
mode; bit 8 is only set to 1 if all other bits are 0.
The following table shows the common Multiplexer Port addresses that can be used. Note that address 0
uses an Ixx10 value of $000100, because Ixx10=0 disables the absolute position read function.
Ixx10 for Acc-8D Option 7 Resolver/Digital Converter
(Ixx95=$000000 - $070000, $800000 - $870000) Addresses are Multiplexer Port Addresses
Board Ixx10 Board Ixx10 Board Ixx10 Board Ixx10
Mux. Mux. Mux. Mux.
Addr. Addr. Addr. Addr.
0 $000100 64 $000040 128 $000080 192 $0000C0
8 $000008 72 $000048 136 $000088 200 $0000C8
16 $000010 80 $000050 144 $000090 208 $0000D0
24 $000018 88 $000058 152 $000098 216 $0000D8
32 $000020 96 $000060 160 $0000A0 224 $0000E0
40 $000028 104 $000068 168 $0000A8 232 $0000E8
48 $000030 112 $000070 176 $0000B0 240 $0000F0
56 $000038 120 $000078 184 $0000B8 248 $0000F8
Parallel Word Read: If Ixx95 is set to a value from $080000 to $300000, from $480000 to $700000,
from $880000 to $B00000, or from $C80000 to $F00000, the address specified in Ixx10 is a Turbo
PMAC memory-I/O address, and Turbo PMAC will read the parallel word at that address. The least
significant bit (count) is expected at bit 0 of the address. The bit width (8 to 48 bits), the format (signed
or unsigned), and the register type (X or Y) are determined by Ixx95.
The common sources for this type of read are Acc-14 parallel I/O expansion boards, and the MLDT timer
registers. The following tables show the settings of Ixx10 for these devices.
Ixx10 Values for Acc-14D/V Registers
(Ixx95=$080000 to $300000 [unsigned], $880000 to $B00000 [signed])
Register Acc-14 Ixx10 Register Acc-14 Ixx10
Select Select
Jumper Jumper
First Acc-14D/V Port A E12 $078A00 Fourth Acc-14D/V Port A E15 $078D00
First Acc-14D/V Port B E12 $078A01 Fourth Acc-14D/V Port B E15 $078D01
Second Acc-14D/V Port A E13 $078B00 Fifth Acc-14D/V Port A E16 $078E00
Second Acc-14D/V Port B E13 $078B01 Fifth Acc-14D/V Port B E16 $078E01
Third Acc-14D/V Port A E14 $078C00 Sixth Acc-14D/V Port A E17 $078F00
Third Acc-14D/V Port B E14 $078C01 Sixth Acc-14D/V Port B E17 $078F01
Ixx10 for PMAC2-Style MLDT Timer Registers (Ixx95=$180000)
Servo Chan. 1 Chan. 2 Chan. 3 Chan. 4 Notes
IC #
0 $078000 $078008 $078010 $078018 First IC on board PMAC2, 3U stack
1 $078100 $078108 $078010 $078018 Second IC on board PMAC2, 3U stack
2 $078200 $078208 $078210 $078218 First Acc-24E2x, first IC on first Acc-24P/V2
3 $078300 $078308 $078310 $078318 Second Acc-24E2x, second IC on first Acc-24P/V2
4 $079200 $079208 $079210 $079218 Third Acc-24E2x, first IC on second Acc-24P/V2
5 $079300 $079308 $079310 $079318 Fourth Acc-24E2x, second IC on second Acc-24P/V2
6 $07A200 $07A208 $07A210 $07A218 Fifth Acc-24E2x, first IC on third Acc-24P/V2
7 $07A300 $07A308 $07A310 $07A318 Sixth Acc-24E2x, second IC on third Acc-24P/V2
8 $07B200 $07B208 $07B210 $07B218 Seventh Acc-24E2x, first IC on fourth Acc-24P/V2
9 $07B300 $07B308 $07B310 $07B318 Eighth Acc-24E2x, second IC on fourth Acc-24P/V2
It can also be used for registers in the 3U-format Acc-3E1 (for 3U Turbo Stack systems) and Acc-14E
(for UMAC Turbo systems) boards. In this case, the last hex digit of Ixx95 must be set to a non-zero
value to specify the byte-wide bus of these boards. The following tables show Ixx10 values for these
boards.
Ixx10 Values for Acc-3E1 Registers in 3U Turbo Stack Systems
(Ixx95=$08000x to $30000x [unsigned], $88000x to $B0000x [signed])
Acc-3E1 Address Jumper E1 E2 E3 E4
Ixx10 Value $07880x $07890x $078A0x $078B0x
Ixx10 Values for Acc-14E Registers in UMAC Turbo Systems
(Ixx95=$08000x to $30000x [unsigned], $88000x to $B0000x [signed])
DIP-Switch SW1-1 ON (0) SW1-1 OFF (1) SW1-1 ON (0) SW1-1 OFF (1)
Setting SW1-2 ON (0) SW1-2 ON (0) SW1-2 OFF (1) SW1-2 OFF (1)
SW1-3 ON (0) $078C0x $078D0x $078E0x $078F0x
SW1-4 ON (0)
SW1-3 OFF (1) $079C0x $079D0x $079E0x $079F0x
SW1-4 ON (0)
SW1-3 ON (0) $07AC0x $07AD0x $07AE0x $07AF0x
SW1-4 OFF (1)
SW1-3 OFF (1) $07BC0x $07BD0x $07BE0x $07BF0x
SW1-4 OFF (1)
SW1-5 & 6 must be ON (0). ON means CLOSED; OFF means OPEN.
The final digit, represented by an x in both of these tables, can take a value of 0 to 5, depending on which
I/O point on the board is used for the least significant bit (LSB):
Ixx10 Last Hex Pin Used for LSB Pin Used for LSB Pin Used for LSB
Digit x
x=0 I/O00-07 I/O48-55 I/O96-103
x=1 I/O08-15 I/O56-63 I/O104-111
x=2 I/O16-23 I/O64-71 I/O112-119
x=3 I/O24-31 I/O72-79 I/O120-127
x=4 I/O32-39 I/O80-87 I/O128-135
x=5 I/O40-47 I/O88-95 I/O136-143
Acc-28 A/D Converter Read: If Ixx95 is set to $310000 or $B10000, the address specified by Ixx10 is a
Turbo PMAC ‘Y’ memory-I/O address, and Turbo PMAC will read the data in the high 16 bits of that
address as the absolute position (the LSB – one count – is in bit 8). This format is intended for the Acc-
28A and Acc-28B A/D converters.
The following table shows the settings of Ixx10 for these registers.
Ixx10 Values for PMAC-Style ADC Registers
(Ixx95=$B10000 for Acc-28A, Ixx95=$310000 for Acc-28B)
Register PMAC First Second Third Fourth
Acc-24P/V Acc-24P/V Acc-24P/V Acc-24P/V
ADC1 $078006 $078206 $079206 $07A206 $07B206
ADC2 $078007 $078207 $079207 $07A207 $07B207
ADC3 $07800E $07820E $07920E $07A20E $07B20E
ADC4 $07800F $07820F $07920F $07A20F $07B20F
ADC5 $078106 $078306 $079306 $07A306 $07B306
ADC6 $078107 $078307 $079307 $07A307 $07B307
ADC7 $07810E $07830E $07930E $07A30E $07B30E
ADC8 $07810F $07830F $07930F $07A30F $07B30F
In this mode, bits 3 through 7 of Ixx10 match the settings of DIP switches SW1-1 through SW1-5,
respectively, of the Acc-8D Option 9 Yaskawa converter board.
A Closed switch represents a bit value of 0; an OPEN switch represents a bit value of 1. Bits 0 through 2,
and bits 8 though 23, of Ixx10 are always set to 0 in this mode.
The following table shows the Multiplexer Port addresses that can be used and the matching values of
Ixx10. Note that address 0 uses an Ixx10 value of $000100, because Ixx10=0 disables the absolute
position read function.
Ixx10 for Acc-8D Option 9 Yaskawa Absolute Encoder (Ixx95=$710000, $F10000)
Addresses are Multiplexer Port Addresses
Board Ixx10 for Ixx10 for Ixx10 for Ixx10 for Board Ixx10 for Ixx10 for Ixx10 for Ixx10 for
Mux. Enc. 1 Enc. 2 Enc. 3 Enc. 4 Mux. Enc. 1 Enc. 2 Enc. 3 Enc. 4
Addr. Addr.
0 $000100 $000002 $000004 $000006 128 $000080 $000082 $000084 $000086
8 $000008 $00000A $00000C $00000E 136 $000088 $00008A $00008C $00008E
16 $000010 $000012 $000014 $000016 144 $000090 $000092 $000094 $000096
24 $000018 $00001A $00001C $00001E 152 $000098 $00009A $00009C $00009E
32 $000020 $000022 $000024 $000026 160 $0000A0 $0000A2 $0000A4 $0000A6
40 $000028 $00002A $00002C $00002E 168 $0000A8 $0000AA $0000AC $0000AE
48 $000030 $000032 $000034 $000036 176 $0000B0 $0000B2 $0000B4 $0000B6
56 $000038 $00003A $00003C $00003E 184 $0000B8 $0000BA $0000BC $0000BE
64 $000040 $000042 $000044 $000046 192 $0000C0 $0000C2 $0000C4 $0000C6
72 $000048 $00004A $00004C $00004E 200 $0000C8 $0000CA $0000CC $0000CE
80 $000050 $000052 $000054 $000056 208 $0000D0 $0000D2 $0000D4 $0000D6
88 $000058 $00005A $00005C $00005E 216 $0000D8 $0000DA $0000DC $0000DE
96 $000060 $000062 $000064 $000066 224 $0000E0 $0000E2 $0000E4 $0000E6
104 $000068 $00006A $00006C $00006E 232 $0000E8 $0000EA $0000EC $0000EE
112 $000070 $000072 $000074 $000076 240 $0000F0 $0000F2 $0000F4 $0000F6
120 $000078 $00007A $00007C $00007E 248 $0000F8 $0000FA $0000FC $0000FE
MACRO Absolute Position Read: If Ixx95 contains a value from $720000 to $740000, or from
$F20000 to $F40000, the value specified in Ixx10 is a MACRO node number, and Turbo PMAC will
obtain the absolute power-on position through the MACRO ring. Ixx95 specifies what type of position
data is used, and whether it is treated as a signed or unsigned value.
The MACRO node number is specified in the last two hex digits of Ixx10. The second-to-last digit
specifies the MACRO IC number 0 to 3 (1, 2, and 3 exist only on Ultralite versions of the Turbo PMAC2,
or a UMAC Turbo with Acc-5E). Note that the MACRO IC number on the Turbo PMAC does not
necessarily match the ring master number for that IC, although it often will. The last digit specifies the
MACRO node number 0 to 15 (0 to F hex) in that IC. This function is only supported in nodes 0, 1, 4, 5,
8, 9, 12 (C), and 13 (D).
The following table shows the required values of Ixx10 for all of the MACRO nodes that can be used.
Note that MACRO IC 0 Node 0 uses an Ixx10 value of $000100, because Ixx10=0 disables the absolute
position read function.
Setting this parameter to zero disables the warning following error limit function. If this parameter is set
greater than the Ixx11 fatal following error limit, the warning status bit will never go true, because the
fatal limit will disable the motor first.
If bit 1 of Ixx97 is set to 1, the motor can be triggered for homing search moves, jog-until-trigger moves,
and motion program move-until-trigger moves when the following error exceeds Ixx12. This is known as
torque-mode triggering, because the trigger will occur at a torque level corresponding to the Ixx12 limit.
Bit 0 of Ixx97 should also be set to 1 to enable software position capture, making the value of Ixx97 equal
to 3 in this mode.
At any given time, one coordinate system's status bit can be output to several places; which system
depends on what coordinate system is hardware-selected on the panel input port if I2=0, or what
coordinate system is software-addressed from the host (&n) if I2=1.
The outputs that work in this way are F1LD/ (pin 23 on connector J2 on Turbo PMAC only), F1ER (line
IR3 into the programmable interrupt controller (PIC) on Turbo PMAC PC) and, if E28 connects pins 1
and 2, FEFCO/ (on the JMACH1 connector on Turbo PMAC only).
Note:
The units of Ixx12 are 1/16 of a count. Therefore, this parameter must hold a value
16 times larger than the number of counts at which the limit will occur. For
example, if the limit is to be 1000 counts, Ixx12 should be set to 16,000.
If this target position is calculated within the special lookahead buffer, when this position is greater in an
absolute sense (not magnitude) than [Ixx13-Ixx41], Turbo PMAC modifies this position to [Ixx13-Ixx41].
Depending on the setting of bit 14 of Ixx24, it either brings the program to a controlled stop at this point
(bit 14=0) or continues the program with the motor position saturated to this value (bit 14=1).
If stopped at the limit in lookahead, reversal along the path is possible. Commands for forward execution
into the limit will execute one segment at a time in a point-to-point fashion. If the software limit is
extended, normal program execution may be resumed. Because program execution is technically only
suspended when stopped at the limit in this mode, an Abort command must be issued before another
program can be run.
Lookahead is active for LINEAR and CIRCLE mode moves, provided that the lookahead buffer is
defined, and with Isx13 and Isx20 set to values greater than 0.
If Ixx13 is set to 0, there is no positive software limit (if 0 should be the limit, use 1). This limit is
automatically de-activated during homing-search moves, until the home trigger is found. It is active
during the post-trigger move.
Ixx13 is referenced to the most recent power-up zero position or homing-move zero position. The
physical position at which this limit occurs is not affected by axis-offset commands (e.g. PSET,
{axis}=), although these commands will change the reported position value at which the limit occurs.
Note:
It is possible to set this parameter outside the range +235 (+64 billion) if a couple of
special things are done. First, the Ixx08 scale factor for the motor must be reduced
to give the motor the range to use this position (motor range is +242/Ixx08).
Second, the variable value must be calculated inside Turbo PMAC, because the
command parser cannot accept constants outside the range +2 35 (e.g. to set I113 to
100 billion, use I113=1000000000*100).
of programmed move, or end of intermediate segment – to the limit. If this target position is not
calculated within the special lookahead buffer, when this position is less in an absolute sense (not
magnitude) than Ixx14, Turbo PMAC automatically issues an Abort command, which causes this motor
to start decelerating to a stop at the rate set by Ixx15. If other motors are in coordinated motion, they are
also brought to a stop at their own Ixx15 rate.
If this target position is calculated within the special lookahead buffer, when this position is less in an
absolute sense (not magnitude) than [Ixx14+Ixx41], Turbo PMAC modifies this position to
[Ixx14+Ixx41]. Depending on the setting of bit 14 of Ixx24, it either brings the program to a controlled
stop at this point (bit 14=0) or continues the program with the motor position saturated to this value (bit
14=1). If stopped at the limit in lookahead, reversal along the path is possible. Commands for forward
execution will execute one segment at a time in a point-to-point fashion.
Lookahead is active for LINEAR and CIRCLE mode moves, provided that the lookahead buffer is
defined, and with Isx13 and Isx20 set to values greater than 0.
If Ixx14 is set to 0, there is no positive software limit (if 0 should be a limit, use 1). This limit is
automatically de-activated during homing-search moves, until the home trigger is found. It is active
during the post-trigger move.
Ixx14 is referenced to the most recent power-up zero position or homing-move zero position. The
physical position at which this limit occurs is not affected by axis-offset commands (e.g. PSET,
{axis}=), although these commands will change the reported position value at which the limit occurs.
Note:
It is possible to set this parameter outside the range +235 (+64 billion) if a couple of
special things are done. First, the Ixx08 scale factor for the motor must be reduced
to give the motor the range to use this position (motor range is +242/Ixx08).
Second, the variable value must be calculated inside Turbo PMAC, because the
command parser cannot accept constants outside the range +2 35 (e.g. to set I114 to
-100 billion, use I114=-1000000000*100).
programmed moves, the Ixx17 limit in this mode cannot guarantee that the limits will be observed.
Special lookahead is required for this capability.
In this mode, the Ixx17 acceleration limit can lower the speed of short programmed moves, even if they
are intended to be blended together at high speed. The algorithm limits the speed of each move so that it
can decelerate to a stop within that move. Without special lookahead, it cannot assume that it will blend
at full speed into another move.
2. Segmented LINEAR and CIRCLE mode moves with lookahead: If the Isx13 segmentation time
parameter for the coordinate system containing Motor xx is set greater than 0, put the coordinate system
in segmentation mode and the special multi-block lookahead function is active (lookahead buffer defined
and Isx20 greater than 0). Then Ixx17 serves as the maximum acceleration for Motor xx in all segments
of LINEAR and CIRCLE mode moves in the coordinate system. If a segment of one of these
programmed moves requests a higher acceleration magnitude of this motor, the segment time for all
motors in the coordinate system is extended so that the motor will not exceed this parameter, yet full
coordination is maintained. Furthermore, the Turbo PMAC will work back through already calculated,
but not yet executed, segments, to make sure the change in this segment does not cause violations in any
of those segments.
Note:
Ixx17 is not used for segmented LINEAR and CIRCLE mode moves when the
special lookahead buffer is not active.
The Ixx17 acceleration limit calculations assume that the coordinate system is operating at the %100
override value (real-time). The true acceleration will vary proportionately with the square of the override
value.
The use of the Ixx17 limit permits the setting of very small TA and/or TS values (Ixx87 and Ixx88 by
default). Do not set both of these values to 0, or a division-by-zero calculation error could occur. It is
advised that the TA time is set no smaller the minimum programmed move block time that should occur.
Example:
Given axis definitions of #1->10000X, #2->10000Y, Isx13=0 and Ixx17 for each motor of 0.25, and
the following motion program segment:
INC F10 TA200 TS0
X20
Y20
The rate of acceleration from the program at the corner for motor #2 (X) is ((0-10)units/sec * 10000
cts/unit * sec/1000msec) / 200 msec = -0.5 cts/msec2. The acceleration of motor #2 (Y) is +0.5 cts/msec2.
Since this is twice the limit, the acceleration will be slowed so that it takes 400 msec.
With the same setup parameters and the following program segment:
INC F10 TA200 TS0
X20 Y20
X-20 Y20
The rate of acceleration from the program at the corner for motor #1 (X) is ((-7.07-7.07)units/sec * 10000
cts/unit * sec/1000msec) / 200 msec = -0.707 cts/msec2. The acceleration of motor #2 (Y) is 0.0. Since
motor #1 exceeds its limit, the acceleration time will be lengthened to 200 * 0.707/0.25 = 707 msec.
Note:
In the second case, the acceleration time is made longer (the corner is made larger)
for what is an identically shaped corner (90o). In a contouring XY application, this
parameter should not be relied upon to produce consistently sized corners without
the special lookahead algorithm.
Bit 0: Flag Register Type Bit: If bit 0 is set to zero, the Turbo PMAC expects the flag registers to be in
the format of a PMAC-style Servo IC. Bit 0 should be set to 0 for any flags on-board a Turbo PMAC, an
Acc-24P, or an ACC24V.
If bit 0 is set to one, the Turbo PMAC expects the flag registers to be in the format of a PMAC2-style
Servo IC. Bit 0 should be set to 1 for any flag register on-board a Turbo PMAC2, an Acc-24P2, an Acc-
24V2, an Acc-24E2, or coming from a MACRO Station.
If multiple flag registers are specified by non-zero settings of Ixx42 and/or Ixx43, all registers must be of
the same format.
Bit 8: Kill on Hardware Limit Bit: If bit 8 is set to 0, the Turbo PMAC will always “abort” the motor
(controlled deceleration to closed-loop, zero-velocity, enabled state) on hitting a hardware overtravel limit
switch. If bit 8 is set to 1, the Turbo PMAC will instead “kill” the motor (immediate open-loop, zero-
output, disabled state) on hitting a hardware limit if (a) the software overtravel limit capability in that
direction is enabled (Ixx13 or Ixx14 != 0), and (b) the software overtravel limit in that direction has not
already been exceeded. Other motors are killed or aborted as determined by bits 21 and 22 of Ixx24, just
as for an amplifier fault or fatal following-error trip. If either of these conditions is not true with bit 8 set
to 1, the motor will still be aborted on hitting a hardware limit function.
The “kill on hardware limit” function permits the software limits (set inside the hardware limits) to be
used to catch controlled moves past the limits in a manner that is easily recoverable, and the hardware
limits to catch uncontrolled moves past the limits due to feedback problems.
Bit 10: Third-Harmonic Injection Control Bit: If bit 10 is set to zero when the motor is controlled in
direct-PWM mode, a third-harmonic component is added to the commutation output waveforms. For
three-phase motors, this increases the operating range of the motors. If bit is set to one when the motor is
controlled in direct-PWM mode, no third-harmonic component is added. This is appropriate for the
control of two-phase motors, such as most stepper motors, for which the addition of a third-harmonic
component would add significant torque ripple without increasing operating range.
Bit 11: Capture with High-Resolution Feedback Bit: If bit 11 is set to zero when hardware position
capture is used in a triggered move such as a homing-search move, the captured data (whether whole-
count only or including sub-count data) is processed to match servo feedback of normal resolution (five
bits of fractional count data per hardware whole count). This setting is appropriate for digital quadrature
feedback or for low-resolution interpolation of a sinusoidal encoder.
If bit 11 (value $800, or 2,048) is set to one when hardware position capture is used in a triggered move,
the captured data (whether whole-count only or including sub-count data) is processed to match servo
feedback of high resolution (10 bits of fractional count data per hardware whole count). This setting is
appropriate for high-resolution interpolation of a sinusoidal encoder through an Acc-51x interpolator.
Bit 12: Sub-Count Capture Enable Bit: If bit 12 is set to zero when hardware position capture is used
in a triggered move such as a homing-search move, only the whole-count captured position register is
used to establish the trigger position. This setting must be used with PMAC-style Servo ICs, and with
PMAC2-style Servo ICs older than Revision D (Revision D ICs started shipping in early 2002).
If bit 12 (value $1000, or 4,096) is set to one when hardware position capture is used in a triggered move,
both the whole-count captured position register and the estimated sub-count position register are used to
establish the trigger position. A PMAC2-style Servo IC of Revision “D” or newer must be used for this
mode, and I7mn9 for the channel used must be set to 1 to enable the hardware sub-count estimation. This
setting is typically used for registration or probing triggered moves with interpolated sinusoidal encoder
feedback. (Even with interpolated sinusoidal encoder feedback, homing search moves will probably be
done without sub-count captured data, to force a home position referenced to one of the four zero-
crossing positions of the sine/cosine signals.)
Bit 13 Error Saturation Control Bit: If bit 13 is set to zero, when the motor’s following error exceeds
the Ixx67 position-error limit, the error is simply truncated by the limit parameter.
If bit 13 (value $2000, or 8,192) is set to 1, when the motor’s following error exceeds the Ixx67 position-
error limit, the excess is put in the “master position” register for the motor, so it is eventually recoverable.
Bit 14: Continue on Desired Position Limit Bit: If bit 14 is set to zero when desired position limits are
enabled (bit 15=1), and desired position within the lookahead buffer exceeds a position limit, Turbo
PMAC will stop execution of the program at the point where the motor reaches the limit.
If bit 14 (value $4000, or 16,384) is set to one when desired position limits are enabled (bit 15=1) (e.g.
I224=$C000) and desired position within the lookahead buffer exceeds a position limit, Turbo PMAC
will continue execution of the program past the point where the motor reaches the limit, but will not let
the desired motor position exceed the limit.
Bit 15: Desired Position Limit Enable Bit: If bit 15 is set to zero, Turbo PMAC does not check to see
whether the desired position for this motor exceeds software overtravel limits.
If bit 15 (value $8000, or 32,768) is set to one (e.g. I324=$8001), Turbo PMAC will check desired
position values for this motor against the software overtravel limits as set by Ixx13, Ixx14, and Ixx41.
If inside the special lookahead buffer, Turbo PMAC will either come to a controlled stop along the path at
the point where the desired position reaches the limit, or continue the program with desired position
saturated at the limit, depending on the setting of bit 14. If not inside the special lookahead buffer, Turbo
PMAC will issue an Abort command when it sees that the desired position has exceeded a position limit.
Bit 16: Amplifier Enable Use Bit: With bit 16 equal to zero – the normal case – the AENAn output is
used as an amplifier-enable line: off when the motor is “killed”, on when it is enabled.
If bit 16 (value $10000, or 65,536) is set to one (e.g. I1924=$10001), this output is not used as an
amplifier-enable line. On PMAC-style channels, it could then be used as a direction output for magnitude
and direction command format if Ixx96 is set to 1. In addition, by assigning an M-variable to the AENAn
output bit, general-purpose use of this output is possible on either Turbo PMAC or PMAC2 if this bit is
set.
Bit 17: Overtravel Limit Use Bit: With bit 17 equal to zero – the normal case – the two hardware
overtravel limit inputs must read 0 (drawing current) to permit commanded motion in the appropriate
direction. If there are not actual (normally closed or normally conducting) limit switches, the inputs must
be hardwired to ground.
If bit 17 (value $20000, or 131,072) is set to one (e.g. I1924=$20000), Motor xx does not use these inputs
as overtravel limits. This can be done temporarily, as when using a limit as a homing flag. If the
hardware overtravel limit function is not used at all, these inputs can be used as general-purpose inputs by
assigning M-variables to them.
Bits 18 and 19: MACRO Node Use Bits: Bits 18 (value $40000, or 262,144) and 19 (value ($80000, or
524,288) of Ixx24 specify what flag information is connected directly to Turbo PMAC hardware
channels, and what information comes through the MACRO ring into a MACRO auxiliary register. The
following table shows the possible settings of these two bits and what they specify:
Bit 19 Bit 18 Capture Flags Amp Flags Limit Flags
0 0 Direct Direct (don’t care)
0 1 Thru MACRO Thru MACRO (don’t care)
1 0 Direct Thru MACRO (don’t care)
1 1 Thru MACRO Direct (don’t care)
If the amplifier flags are connected through the MACRO ring, bit 23 of Ixx24 must be set to 1 to
designate a high-true amplifier fault, which is the MACRO standard. When using a MACRO auxiliary
register for the flags, Ixx25, Ixx42, or Ixx43 should contain the address of a holding register in RAM, not
the actual MACRO register. Refer to the descriptions of those variables for a list of the holding register
addresses. Turbo PMAC firmware automatically copies between the holding registers and the MACRO
registers as enabled by I70, I72, I74 and I76, for MACRO ICs 0, 1, 2, and 3, respectively. I71, I73, I75,
and I77 must be set properly to determine whether the Type 0 or Type 1 MACRO protocol is being used
on the particular node (all Delta Tau products use Type 1).
Bit 20: Amplifier Fault Use Bit: If bit 20 of Ixx24 is 0, the amplifier-fault input function through the
FAULTn input is enabled. If bit 20 (value $100000, or 1,048,576) is 1 (e.g. I1924=$100000), this
function is disabled. General-purpose use of this input is then possible by assigning an M-variable to the
input.
Bits 21 & 22: Action-on-Fault Bits: Bits 21 (value $200000, or 2,097,152) and 22 (value $400000, or
4,194,304) of Ixx24 control what action is taken on an amplifier fault for the motor, or on exceeding the
fatal following error limit (as set by Ixx11) for the motor:
Bit 22 Bit 21 Function
Bit 22=0 Bit 21=0: Kill all PMAC motors
Bit 22=0 Bit 21=1: Kill all motors in same coordinate system
Bit 22=1 Bit 21=0: Kill only this motor
Bit 22=1 Bit 21=1: (Reserved for future use)
Regardless of the setting of these bits, a program running in the coordinate system of the offending motor
will be halted on an amplifier fault or the exceeding of a fatal following error.
Bit 23: Amplifier-Fault Polarity Bit: Bit 23 (value $800000, or 8,388,608) of Ixx24 controls the
polarity of the amplifier-fault input. A zero in this bit specifies that a zero read in the fault bit means a
fault; a one in this bit specifies that a one read in the fault bit means a fault. The actual state of the input
circuitry for a fault depends on the actual interface circuitry used. If a Delta Tau-provided optically
isolated fault interface is used, when the fault driver from the amplifier is drawing current through the
isolator, either sinking or sourcing, the fault bit will read as zero; when it is not drawing current through
the isolator, the fault bit will read as one.
In both the standard direct-PWM interface and the standard MACRO interface, bit 23 should be set to
one, to specify that a one in the fault bit means a fault. (The actual polarity of the signal into the remote
MACRO Station is programmable at the station).
Bit 23 is only used if bit 20 of Ixx24 is set to 0, telling Turbo PMAC to use the amplifier fault input.
Ixx25 Motor xx Flag Address
Range: $000000 - $FFFFFF
Units: Turbo PMAC Addresses
Default:
Turbo PMAC Ixx25 Defaults
Ixx25 Value Register Ixx25 Value Register
nd
I125 $078000 PMAC Flag Set 1 I1725 $079200 2 Acc-24P/V Flag Set 1
I225 $078004 PMAC Flag Set 2 I1825 $079204 2nd Acc-24P/V Flag Set 2
I325 $078008 PMAC Flag Set 3 I1925 $079208 2nd Acc-24P/V Flag Set 3
I425 $07800C PMAC Flag Set 4 I2025 $07920C 2nd Acc-24P/V Flag Set 4
I525 $078100 PMAC Flag Set 5 I2125 $079300 2nd Acc-24P/V Flag Set 5
I625 $078104 PMAC Flag Set 6 I2225 $079304 2nd Acc-24P/V Flag Set 6
I725 $078108 PMAC Flag Set 7 I2325 $079308 2nd Acc-24P/V Flag Set 7
I825 $07810C PMAC Flag Set 8 I2425 $07930C 2nd Acc-24P/V Flag Set 8
I925 $078200 First Acc-24P/V Flag Set 1 I2525 $07A200 3rd Acc-24P/V Flag Set 1
I1025 $078204 First Acc-24P/V Flag Set 2 I2625 $07A204 3rd Acc-24P/V Flag Set 2
I1125 $078208 First Acc-24P/V Flag Set 3 I2725 $07A208 3rd Acc-24P/V Flag Set 3
I1225 $07820C First Acc-24P/V Flag Set 4 I2825 $07A20C 3rd Acc-24P/V Flag Set 4
I1325 $078300 First Acc-24P/V Flag Set 5 I2925 $07A300 3rd Acc-24P/V Flag Set 5
I1425 $078304 First Acc-24P/V Flag Set 6 I3025 $07A304 3rd Acc-24P/V Flag Set 6
I1525 $078308 First Acc-24P/V Flag Set 7 I3125 $07A308 3rd Acc-24P/V Flag Set 7
I1625 $07830C First Acc-24P/V Flag Set 8 I3225 $07A30C 3rd Acc-24P/V Flag Set 8
Ixx25 tells Turbo PMAC what registers it will access for its position-capture flags, and possibly its
overtravel-limit input flags and amplifier enable/fault flags, for Motor xx. If Ixx42 is set to 0, Ixx25
specifies the address of the amplifier flags; if Ixx42 is set to a non-zero value, Ixx42 specifies the address
of the amplifier flags. If Ixx43 is set to 0, Ixx25 specifies the address of the overtravel limit flags; if
Ixx43 if set to a non-zero value, Ixx43 specifies the address of the overtravel limit flags. Variable Ixx24
tells which of the flags from the specified registers are to be used, and how they are to be used.
The addresses for the standard flag registers are given in the default table, above. The following tables
show settings by register if changing from the default.
Ixx25 Addresses for PMAC-Style Servo ICs
Servo Chan. 1 Chan. 2 Chan. 3 Chan. 4 Notes
IC #
0 $078000 $078004 $078008 $07800C First IC on board PMAC
1 $078100 $078104 $078108 $07810C Second IC on board PMAC
2 $078200 $078204 $078208 $07820C First IC on first Acc-24P/V
3 $078300 $078304 $078308 $07830C Second IC on first Acc-24P/V
4 $079200 $079204 $079208 $07920C First IC on second Acc-24P/V
5 $079300 $079304 $079308 $07930C Second IC on second Acc-24P/V
6 $07A200 $07A204 $07A208 $07A20C First IC on third Acc-24P/V
7 $07A300 $07A304 $07A308 $07A30C Second IC on third Acc-24P/V
8 $07B200 $07B204 $07B208 $07B20C First IC on 4th Acc-24P/V
9 $07B300 $07B304 $07B308 $07B30C Second IC on 4th Acc-24P/V
Bit 0 of Ixx24 must be set to 0 to use PMAC-style Servo ICs.
Ixx25 Addresses for PMAC2-Style Servo ICs
Servo Chan. 1 Chan. 2 Chan. 3 Chan. 4 Notes
IC #
0 $078000 $078008 $078010 $078018 First IC on board PMAC2, 3U stack
1 $078100 $078108 $078110 $078118 Second IC on board PMAC2, 3U stack
2 $078200 $078208 $078210 $078218 First Acc-24E2x, first IC on first Acc-24P/V2
3 $078300 $078308 $078310 $078318 Second Acc-24E2x, second IC on first Acc-24P/V2
4 $079200 $079208 $079210 $079218 Third Acc-24E2x, first IC on second Acc-24P/V2
5 $079300 $079308 $079310 $079318 Fourth Acc-24E2x, second IC on second Acc-24P/V2
6 $07A200 $07A208 $07A210 $07A218 Fifth Acc-24E2x, first IC on third Acc-24P/V2
7 $07A300 $07A308 $07A310 $07A318 Sixth Acc-24E2x, second IC on third Acc-24P/V2
8 $07B200 $07B208 $07B210 $07B218 Seventh Acc-24E2x, first IC on fourth Acc-24P/V2
9 $07B300 $07B308 $07B310 $07B318 Eighth Acc-24E2x, second IC on fourth Acc-24P/V2
Bit 0 of Ixx24 must be set to 1 to use PMAC2-style Servo ICs.
Ixx25 Addresses for MACRO Flag Holding Registers
IC MACRO MACRO MACRO MACRO Notes
Node # IC 1 IC 2 IC 3 IC 4
0 $003440 $003450 $003460 $003470 MACRO Flag Register Sets 0, 16, 32, 48
1 $003441 $003451 $003461 $003471 MACRO Flag Register Sets 1, 17, 33, 49
4 $003444 $003454 $003464 $003474 MACRO Flag Register Sets 4, 20, 36, 52
5 $003445 $003455 $003465 $003475 MACRO Flag Register Sets 5, 21, 37, 53
8 $003448 $003458 $003468 $003478 MACRO Flag Register Sets 8, 24, 40, 56
9 $003449 $003459 $003469 $003479 MACRO Flag Register Sets 9, 25, 41, 57
12 $00344C $00345C $00346C $00347C MACRO Flag Register Sets 12, 28, 44, 60
13 $00344D $00345D $00346D $00347D MACRO Flag Register Sets 13, 29, 45, 61
Bit 0 of Ixx24 must be set to 1 to use MACRO flag holding registers
Bits 18 and 19 of Ixx24 specify what flag information comes directly into Turbo PMAC and what comes
through the MACRO ring. The following table explains the possible settings:
Note:
The units of this parameter are 1/16 of a count, so the value should be 16 times the
number of counts between the trigger position and the home zero position.
Example:
To change the motor zero position to 500 counts in the negative direction from the home trigger position,
set Ixx26 to -500 * 16 = -8000.
Ixx27 Motor xx Position Rollover Range
Range: -235 - +235
Units: counts
Default: 0
Ixx27 permits either of two position rollover modes on a Turbo PMAC rotary axis assigned to Motor xx
by telling Turbo PMAC how many encoder counts are in one revolution of the rotary axis. This lets
Turbo PMAC handle rollover properly. If Ixx27 is set to the default value of 0, no rollover mode is
active, and the axis is treated as a linear axis.
If Ixx27 is greater than zero, and Motor xx is assigned to a rotary axis (A, B, or C), the standard rollover
mode is active. With standard rollover active, for a programmed axis move in absolute (ABS) mode, the
motor will take the shortest path around the circular range defined by Ixx27 to get to the destination point.
No absolute-mode move will be longer than half of a revolution (Ixx27/2) with standard rollover.
If Ixx27 is set to a negative number, an alternate rollover mode for the rotary axis assigned to the motor is
activated that uses the sign of the commanded destination in absolute mode to specify the direction of
motion to that destination. In this mode, all moves are less than one revolution (with the size of the
revolution specified by the magnitude of Ixx27), but can be greater than one-half revolution. This mode
also does not affect the action of incremental-mode moves.
The sign of the commanded absolute destination in this mode is also part of the destination value.
Therefore, a command of A-90 in this mode is a command to go to -90 degrees (= +270 degrees) in the
negative direction. For commands to move in the positive direction, the + sign is not required, but it is
permitted (e.g. to command a move to 90 degrees in the positive direction, either A90 or A+90 can be
used).
PMAC cannot store the difference between a +0 and a –0 destination command, so a command with a
tiny non-zero magnitude for the end position must be used (e.g. A+0.0000001 and A-0.0000001).
This increment can be small enough not to have any effect on the final destination.
If the distance of the move commanded in alternate rollover mode is less than the size of the in-position
band defined for the motor with Ixx28, no move will be executed. This means that the minimum distance
for a move in this mode is Ixx28, and the maximum distance is 360 degrees minus Ixx28.
If using commands from a similar mode in which only the magnitude, and not the sign, of the value
specifies the destination position, then the destination values for negative-direction moves must be
modified so that the magnitude is 360 degrees minus the magnitude in the other mode. For example, if
the command were C-120, specifying a move to (+)120 degrees in the negative direction, the command
would have to be modified for PMAC to C-240, which specifies a move to -240 degrees (= +120 degrees)
in the negative direction. Commands for positive-direction moves do not have to be modified.
Axis moves in incremental (INC) mode are not affected by either rollover mode. Rollover should not be
attempted for axes other than A, B, or C. Jog moves are not affected by rollover. Reported motor
position is not affected by rollover. (To obtain motor position information rolled over to within one
motor revolution, use the modulo (remainder) operator, either in PMAC or in the host computer: e.g.
P4=(M462/(I408*32))%I427).
Note:
It is possible to set this parameter outside the range -235 to +235 (+64 billion) if a
couple of special things are done. First, the Ixx08 scale factor for the motor must
be reduced to give the motor the range to use this position (motor range is
+242/Ixx08). Second, the variable value must be calculated inside Turbo PMAC,
because the command parser cannot accept constants outside the range +235 (e.g. to
set I127 to 100 billion, use I127=1000000000*100).
Example:
Motor #4 drives a rotary table with 36,000 counts per revolution. It is defined to the A-axis with #4-
>100A (A is in units of degrees). I427 is set to 36000. With motor #4 at zero counts (A-axis at zero
degrees), an A270 move in a program is executed in Absolute mode. Instead of moving the motor from 0
to 27,000 counts, which it would have done with I427=0, PMAC moves the motor from 0 to -9,000
counts, or -90 degrees, which is equivalent to +270 degrees on the rotary table.
Ixx28 Motor xx In-Position Band
Range: 0 - 8,388,607
Units: 1/16 count
Default: 160 (10 counts)
Ixx28 specifies the magnitude of the maximum following error at which Motor xx will be considered “in
position” when not performing a move.
Several things happen when the motor is “in-position”. First, a status bit in the motor status word (bit 0
of Y:$0000C0 for Motor 1) is set. Second, if all other motors in the same coordinate system are also “in-
position”, a status bit in the coordinate system status word (bit 17 of Y:$00203F for C.S. 1) is set.
Third, for the hardware-selected (FPD0/-FPD3/) coordinate system – if I2=0 (Turbo PMAC only) – or for
the software addressed (&n) coordinate system – if I2=1 – outputs to the control panel port (Turbo PMAC
only) and to the interrupt controller are set.
Technically, five conditions must be met for a motor to be considered “in-position”:
1. The motor must be in closed-loop control;
2. The desired velocity must be zero;
3. The magnitude of the following error must be less than this parameter;
4. The move timer must not be active;
5. The above four conditions must all be true for (Ixx88+1) consecutive scans.
The over timer is active (the motor running a program/definite-time move status bit is 1) during any
programmed or non-programmed move, including DWELLs and DELAYs in a program – to have this bit
come true during a program, do an indefinite wait between some moves by keeping the program trapped
in a WHILE loop that has no moves or DWELLs.
To have a status bit indicating whether the magnitude of the following error is above or below a threshold
(condition 3 only), use the warning following error status bit with Ixx12 as the threshold.
If global variable I13 is set to 1, Turbo PMAC also performs an in-position check every servo cycle as
part of the foreground tasks. In this check, it only evaluates the first four conditions listed above. This
task controls a separate motor status bit: foreground in-position (bit 13 of Y:$0000C0 for Motor 1). This
function can be used when the background in-position check is not fast enough.
Note:
The units of this parameter are 1/16 of a count, so the value should be 16 times the
number of counts in the in-position band.
Example:
The following motion program segment shows how the in-position function could be used in a program to
set an output after coming in-position at a programmed point. M140 represents Motor 1’s in-position
status bit (see suggested M-variable definitions).
X10 ; Commanded move
DWELL0 ; Stop lookahead in motion programs
WHILE (M140=0) WAIT ; Loop while not in position
M1=1 ; Set output
Ixx29 Motor xx Output/First Phase Offset
Range: -32,768 - 32,767
Units: 16-bit DAC/ADC bit equivalent
Default: 0
Ixx29 serves as an output or feedback offset for Motor xx; its exact use depends on the mode of operation
as described below. In any of the modes, it effectively serves as the digital equivalent of an offset pot.
Mode 1: When Turbo PMAC is not commutating Motor xx (Ixx01 Bit 0 = 0), Ixx29 serves as the offset
for the single command output value, usually a DAC command. Ixx29 is added to the output command
value before it is written to the command output register.
Mode 2: When Turbo PMAC (PMAC-style Servo ICs only) is not commutating Motor xx (Ixx01 Bit 0 =
0) but is in sign-and-magnitude output mode (Ixx96 = 1), Ixx29 is the offset of the command output value
before the absolute value is taken (Ixx79 is the offset after the absolute value is taken). Ixx29 is typically
left at zero in this mode, because it cannot compensate for real circuitry offsets.
Mode 3: When Turbo PMAC is commutating Motor xx (Ixx01 Bit 0 = 1) but not closing the current loop
(Ixx82 = 0), Ixx29 serves as the offset for the first of two phase command output values (Phase A), for the
address specified by Ixx02; Ixx79 serves the same purpose for the second phase (Phase B). Ixx29 is
added to the output command value before it is written to the command output register.
When commutating from a PMAC-style Servo IC, Phase A is output on the higher-numbered of the two
DACs (e.g. DAC2); Phase B on the lower-numbered (e.g. DAC1). When commutating from a PMAC2-
style Servo IC, Phase A is output on the A-channel DAC (e.g. DAC1A), Phase B on the B-channel DAC
(e.g. DAC1B).
As an output command offset, Ixx29 is always in units of a 16-bit register, even if the actual output device
is of a different resolution. For example, if a value of 60 had to be written into an 18-bit DAC to create a
true zero command, this would be equivalent to a value of 60/4=15 in a 16-bit DAC, so Ixx29 would be
set to 15 to cancel the offset.
Mode 4: When Turbo PMAC is commutating (Ixx01 Bit 0 = 1) and closing the current loop for Motor xx
(Ixx82 > 0), Ixx29 serves as an offset that is added to the phase current reading from the ADC for the first
phase (Phase A), at the address specified by Ixx82 minus 1. Ixx79 performs the same function for the
second phase. The sum of the ADC reading and Ixx29 is used in the digital current loop algorithms.
As an input feedback offset, Ixx29 is always in units of a 16-bit ADC, even if the actual ADC is of a
different resolution. For example, if a 12-bit ADC reported a value of -5 when no current was flowing in
the phase, this would be equivalent to a value of -5*16=-80 in a 16-bit ADC, so Ixx29 would be set to 80
to compensate for this offset.
On a typical system with a current-loop amplifier and PMAC's default servo update time (~440 sec), an
Ixx31 value of 2000 to 3000 will provide a critically damped step response.
If the servo update time is changed, Ixx31 must be changed proportionately in the opposite direction to
keep the same damping effect. For instance, if the servo update time is cut in half, from 440 sec to 220
sec, Ixx31 must be doubled to keep the same effect.
This parameter is usually set initially using the Tuning utility in the PMAC Executive Program. It may be
changed on the fly at any time to create types of adaptive control.
Ixx31 is not used if Iyy00/50 for the motor has been set to 1 to enable the Extended Servo Algorithm
(ESA) for the motor.
Ixx32 Motor xx PID Velocity Feedforward Gain
Range: -8,388,608 - 8,388,607
Units: (Ixx30*Ixx08)/226 16-bit output bits / (counts/servo update)
Default: 1280
Ixx32 adds an amount to the control output proportional to the desired velocity of Motor xx. It is
intended to reduce tracking error due to the damping introduced by Ixx31, analog tachometer feedback, or
physical damping effects.
If the motor is driving a current-loop (torque) amplifier, Ixx32 will usually be equal to (or slightly greater
than) Ixx31 to minimize tracking error. If the motor is driving a velocity-loop amplifier, Ixx32 will
typically be substantially greater than Ixx31 to minimize tracking error.
If the servo update time is changed, Ixx32 must be changed proportionately in the opposite direction to
keep the same effect. For instance, if the servo update time is cut in half, from 440 sec to 220 sec,
Ixx32 must be doubled to keep the same effect.
This parameter is usually set initially using the Tuning utility in the PMAC Executive Program. It may be
changed on the fly at any time to create types of adaptive control.
Ixx32 is not used if Iyy00/50 for the motor has been set to 1 to enable the Extended Servo Algorithm
(ESA) for the motor.
Ixx33 Motor xx PID Integral Gain
Range: 0 - 8,388,607
Units: (Ixx30*Ixx08)/242 16-bit output bits / (counts*servo update)
Default: 1280
Ixx33 adds an amount to the control output proportional to the time integral of the position error for
Motor xx. The magnitude of this integrated error is limited by Ixx63. With Ixx63 at a value of zero, the
contribution of the integrator to the output is zero, regardless of the value of Ixx33.
No further errors are added to the integrator if the output saturates (if output equals Ixx69), and, if
Ixx34=1, when a move is being commanded (when desired velocity is not zero). In both of these cases,
the contribution of the integrator to the output remains constant.
If the servo update time is changed, Ixx33 must be changed proportionately in the same direction to keep
the same effect. For instance, if the servo update time is cut in half, from 440 sec to 220 sec, Ixx33
must be cut in half to keep the same effect.
This parameter is usually set initially using the Tuning utility in the PMAC Executive Program. It may be
changed on the fly at any time to create types of adaptive control.
Ixx33 is not used if Iyy00/50 for the motor has been set to 1 to enable the Extended Servo Algorithm
(ESA) for the motor.
Ixx36 is not used if Iyy00/50 for the motor has been set to 1 to enable the Extended Servo Algorithm
(ESA) for the motor.
Ixx37 Motor xx PID Notch Filter Coefficient N2
Range: -2.0 - 2.0
Units: none (unit-less z-transform coefficient)
Default: 0.0
Ixx37 is part of the notch filter for Motor xx. See Ixx36 and the Servo Loop Features section of the
manual for details.
Usually, this parameter is set initially using the Tuning utility in the PMAC Executive Program. It may
be changed on the fly at any time to create types of adaptive control.
Ixx37 is not used if Iyy00/50 for the motor has been set to 1 to enable the Extended Servo Algorithm
(ESA) for the motor.
Ixx38 Motor xx PID Notch Filter Coefficient D1
Range: -2.0 - 2.0
Units: none (unit-less z-transform coefficient)
Default: 0.0
Ixx38 is part of the “notch filter” for Motor xx. See Ixx36 and the Servo Loop Features section of the
manual for details.
Usually, this parameter is set initially using the Tuning utility in the PMAC Executive Program. It may
be changed on the fly at any time to create types of adaptive control.
Ixx38 is not used if Iyy00/50 for the motor has been set to 1 to enable the Extended Servo Algorithm
(ESA) for the motor.
Ixx39 Motor xx PID Notch Filter Coefficient D2
Range: -2.0 - 2.0
Units: none (unit-less z-transform coefficient)
Default: 0.0
Ixx39 is part of the notch filter for Motor xx. See Ixx36 and the Servo Loop Features section of the
manual for details.
Usually, this parameter is set initially using the Tuning utility in the PMAC Executive Program. It may
be changed on the fly at any time to create types of adaptive control.
Ixx39 is not used if Iyy00/50 for the motor has been set to 1 to enable the Extended Servo Algorithm
(ESA) for the motor.
Ixx40 Motor xx Net Desired Position Filter Gain
Range: 0.0 – 0.999999
Units: none
Default: 0.0
Ixx40 permits the introduction of a first-order low-pass filter on the net desired position for Motor xx.
This can be useful to smooth motion that comes from a “rough” source, such as master following from a
noisy sensor, or quantization error in very closely spaced programmed points that are commonly found in
lookahead applications.
If Ixx40 is set to its default value of 0.0, this filter function is disabled. If Ixx40 is set to any value greater
than 0.0, the filter is enabled.
Ixx40 can be expressed in terms of the filter time constant by the following equation:
where Tf is the filter time constant, and Ts is the servo update time.
Tf
Ixx 40
Ts T f
The filter time constant can be expressed in terms of Ixx40 by the following equation:
Ixx40 * Ts
Tf
1 Ixx40
Filter time constants can range from a fraction of a servo cycle (when Ixx40 ~ 0) to infinite (when Ixx40
~ 1). As with any low-pass filter, there is a fundamental trade-off between smoothness and delay.
Generally, when the filter is used, filter time constants of a few milliseconds are set. In an application
where multiple motors are executing a path, the same time constant should be used for all of the motors.
Example:
To set a filter time constant of 2 msec on a system with the default servo update time of 442 sec, Ixx40
can be computed as:
2
Ixx40 0.819
0.442 2
If amplifier flags are specified separately using Ixx42, they must use the same type of ICs as does Ixx25,
those specified by bit 0 of Ixx24.
Bits 18 and 19 of Ixx24 specify whether the amplifier flags and the capture flags are connected directly to
Turbo PMAC circuitry, or interface to it through the MACRO ring as shown in the following table:
Bit 19 Bit 18 Capture Flags Amp Flags
0 0 Direct Direct
0 1 Thru MACRO Thru MACRO
1 0 Direct Thru MACRO
1 1 Thru MACRO Direct
The following tables show the standard addresses that can be used for Ixx42.
Ixx42 Addresses for PMAC-Style Servo ICs
Servo IC # Chan. 1 Chan. 2 Chan. 3 Chan. 4 Notes
0 $078000 $078004 $078008 $07800C First IC on board PMAC
1 $078100 $078104 $078108 $07810C Second IC on board PMAC
2 $078200 $078204 $078208 $07820C First IC on first Acc-24P/V
3 $078300 $078304 $078308 $07830C Second IC on first Acc-24P/V
4 $079200 $079204 $079208 $07920C First IC on second Acc-24P/V
5 $079300 $079304 $079308 $07930C Second IC on second Acc-24P/V
6 $07A200 $07A204 $07A208 $07A20C First IC on third Acc-24P/V
7 $07A300 $07A304 $07A308 $07A30C Second IC on third Acc-24P/V
8 $07B200 $07B204 $07B208 $07B20C First IC on fourth Acc-24P/V
9 $07B300 $07B304 $07B308 $07B30C Second IC on fourth Acc-24P/V
Bit 0 of Ixx24 must be set to 0 to use PMAC-style Servo ICs.
Ixx42 Addresses for PMAC2-Style Servo ICs
Servo IC # Chan. 1 Chan. 2 Chan. 3 Chan. 4 Notes
0 $078000 $078008 $078010 $078018 First IC on board PMAC2, 3U stack
1 $078100 $078108 $078110 $078118 Second IC on board PMAC2, 3U stack
2 $078200 $078208 $078210 $078218 First Acc-24E2x, first IC on first Acc-24P/V2
3 $078300 $078308 $078310 $078318 Second Acc-24E2x, second IC on first Acc-24P/V2
4 $079200 $079208 $079210 $079218 Third Acc-24E2x, first IC on second Acc-24P/V2
5 $079300 $079308 $079310 $079318 Fourth Acc-24E2x, second IC on second Acc-24P/V2
6 $07A200 $07A208 $07A210 $07A218 Fifth Acc-24E2x, first IC on third Acc-24P/V2
7 $07A300 $07A308 $07A310 $07A318 Sixth Acc-24E2x, second IC on third Acc-24P/V2
8 $07B200 $07B208 $07B210 $07B218 Seventh Acc-24E2x, first IC on fourth Acc-24P/V2
9 $07B300 $07B308 $07B310 $07B318 Eighth Acc-24E2x, second IC on fourth Acc-24P/V2
Bit 0 of Ixx24 must be set to 1 to use PMAC2-style Servo ICs.
Ixx42 Addresses for MACRO Flag Holding Registers
IC Node MACRO MACRO MACRO MACRO Notes
# IC 1 IC 2 IC 3 IC 4
0 $003440 $003450 $003460 $003470 MACRO Flag Register Sets 0, 16, 32, 48
1 $003441 $003451 $003461 $003471 MACRO Flag Register Sets 1, 17, 33, 49
4 $003444 $003454 $003464 $003474 MACRO Flag Register Sets 4, 20, 36, 52
5 $003445 $003455 $003465 $003475 MACRO Flag Register Sets 5, 21, 37, 53
8 $003448 $003458 $003468 $003478 MACRO Flag Register Sets 8, 24, 40, 56
9 $003449 $003459 $003469 $003479 MACRO Flag Register Sets 9, 25, 41, 57
12 $00344C $00345C $00346C $00347C MACRO Flag Register Sets 12, 28, 44, 60
13 $00344D $00345D $00346D $00347D MACRO Flag Register Sets 13, 29, 45, 61
Bit 0 of Ixx24 must be set to 1 to use MACRO flag holding registers.
With MACRO ICs in the standard addresses, the following table shows the appropriate settings for Ixx44
for accepting commanded position.
Ixx44 MACRO IC and Node Ixx44 MACRO IC and Node
$278420 MACRO IC 0 Node 0 $27A420 MACRO IC 2 Node 0
$278424 MACRO IC 0 Node 1 $27A424 MACRO IC 2 Node 1
$278428 MACRO IC 0 Node 4 $27A428 MACRO IC 2 Node 4
$27842C MACRO IC 0 Node 5 $27A42C MACRO IC 2 Node 5
$278430 MACRO IC 0 Node 8 $27A430 MACRO IC 2 Node 8
$278434 MACRO IC 0 Node 9 $27A434 MACRO IC 2 Node 9
$278438 MACRO IC 0 Node 12 $27A438 MACRO IC 2 Node 12
$27843C MACRO IC 0 Node 13 $27A43C MACRO IC 2 Node 13
$279420 MACRO IC 1 Node 0 $27B420 MACRO IC 3 Node 0
$279424 MACRO IC 1 Node 1 $27B424 MACRO IC 3 Node 1
$279428 MACRO IC 1 Node 4 $27B428 MACRO IC 3 Node 4
$27942C MACRO IC 1 Node 5 $27B42C MACRO IC 3 Node 5
$279430 MACRO IC 1 Node 8 $27B430 MACRO IC 3 Node 8
$279434 MACRO IC 1 Node 9 $27B434 MACRO IC 3 Node 9
$279438 MACRO IC 1 Node 12 $27B438 MACRO IC 3 Node 12
$27943C MACRO IC 1 Node 13 $27B43C MACRO IC 3 Node 13
actual or commanded current level from Turbo PMAC is above the magnitude of Ixx57 for a significant
period of time, as set by Ixx58, Turbo PMAC will trip this motor on an integrated-current amplifier fault
condition.
The integrated current limit can either be an I2T (“I-squared-T”) limit, or an |I|T (I-T) limit. If Ixx57 is set
to a positive value, Turbo PMAC performs I2T limiting, squaring the value of current before integrating
and comparing to Ixx58. If Ixx57 is set to a negative value, Turbo PMAC performs |I|T limiting, just
taking the absolute value of the current before integrating and comparing to Ixx58.
I2T limiting is best used if the system device with the shortest thermal time constant is resistive (and so
has I2R heating), as in motor windings and MOSFET drivers. |I|T limiting is best used if the system
device with the shortest thermal time constant has a fixed voltage drop (and so has IV heating), as in
IGBT drivers.
Ixx57 is in units of a 16-bit DAC or ADC (maximum possible value of 32,767), even if the actual output
or input device has a different resolution. Typically, Ixx57 will be set to between 1/3 and 1/2 of the Ixx69
(instantaneous) output limit. Consult the amplifier and motor documentation for their specifications on
instantaneous and continuous current limits.
Technically, Ixx57 is the continuous limit of the vector sum of the quadrature and direct currents. The
quadrature (torque-producing) current is the output of the position/velocity-loop servo. The direct
(magnetization) current is set by Ixx77.
In sine-wave output mode (Ixx01 bit 0 = 1, Ixx82 = 0), typically, amplifier gains are given in amperes of
phase current per volt of PMAC output, but motor and typically amplifier limits are given in RMS
amperage values. In this case, it is important to realize that peak phase current values are 2 (1.414)
times greater than the RMS values.
In direct-PWM mode (Ixx01 bit 0 = 1, Ixx82 > 0) of 3-phase motors (Ixx72 = 683 or 1365), the
corresponding top values of the sinusoidal phase-current ADC readings will be 1/cos(30o), or 1.15, times
greater than the vector sum of quadrature and direct current. Therefore, once the top values have been
established in the A/D converters the phase currents on a continuous basis, this value should be multiplied
by cos(30o), or 0.866, to get the value for Ixx57. Remember that if current limits are given as RMS
values, multiply these by 2 (1.414) to get peak phase current values.
Examples:
1. Turbo PMAC Motor 1 is driving a torque-mode DC brush-motor amplifier that has a gain of 3
amps/volt with a single analog output voltage. The amplifier has a continuous current rating of 10
amps; the motor has a continuous current rating of 12 amps.
PMAC’s maximum output of 32,768, or 10 volts, corresponds to 30 amps.
The amplifier has the lower continuous current rating, so we use its limit of 10 amps.
I157 is set to 32,768 * 10 / 30 = 10,589.
2. Motor 3 is driving a self-commutating brushless-motor amplifier in current (torque) mode with a
single analog output. The amplifier has a gain of 5 amps (RMS)/volt and an continuous current limit
of 20 amps (RMS). The motor has a continuous current limit of 25 amps (RMS).
PMAC’s maximum output of 32,768, or 10V, corresponds to 50 amps (RMS).
The amplifier has the lower continuous current rating, so we use its limit of 20 amps (RMS).
I357 is set to 32,768 * 20/50 = 13,107.
3. Turbo PMAC Motor 4 is driving a sine-wave mode amplifier that has a gain for each phase input of 5
amps/volt. The amplifier has a continuous rating of 20 amps (RMS); the motor has a continuous
rating of 22 amps (RMS).
PMAC’s maximum output of 32,768, or 10 volts, corresponds to 50 amps peak in a phase.
The amplifier has the lower continuous current rating, so we use its limit of 20 amps (RMS).
20 amps (RMS) corresponds to peak phase currents of 20*1.414 = 28.28 amps.
I457 is set to 32,768 * 28.28 / 50 = 18,534.
4. Turbo PMAC Motor 6 is driving a direct-PWM power block amplifier for an AC motor. The A/D
converters in the amplifier are scaled so that a maximum reading corresponds to 50 amps of current in
the phase. The amplifier has a continuous current rating of 20 amps (RMS), and the motor has a
continuous rating of 15 amps (RMS).
PMAC’s maximum ADC phase reading of 32,768 corresponds to 50 amps.
The motor has the lower continuous current rating, so we use its limit of 15 amps (RMS).
15 amps (RMS) corresponds to peak phase currents of 15*1.414 = 21.21 amps.
21.21 amps corresponds to an ADC reading of 32,768 * 21.21/50 = 13,900.
I657 should be set to 13,900 * 0.866 = 12,037.
See Also:
Integrated Current Protection (Making an Application Safe)
I-Variables Ixx58, Ixx69
Ixx58 Motor xx Integrated Current Limit
Range: 0 - 8,388,607
Units: 230 (DAC bits)2 servo cycles
{Bits of a 16-bit DAC/ADC}
Default: 0
Ixx58 sets the maximum integrated current limit for Turbo PMAC’s I 2T or |I|T integrated current limiting
function. If Ixx58 is 0, the I 2T limiting function is disabled. If Ixx58 is greater than 0, Turbo PMAC will
compare the time-integrated difference between the commanded or actual current and the Ixx57
continuous current limit to Ixx58. If Ixx57 is greater than 0, Turbo PMAC uses the squares of these
current values for I2T limiting; if Ixx57 is less than 0, Turbo PMAC uses the absolute value of these
current values for |I|T limiting. If the integrated value exceeds the limit set by Ixx58, then Turbo PMAC
faults the motor just as it would for receiving an amplifier fault signal, setting both the amplifier-fault and
the integrated-current-fault motor status bits.
Typically, the Ixx58 limit is set by taking the relationship between the instantaneous current limit (Ixx69
on Turbo PMAC, in units of a 16-bit DAC), the magnetization current (commanded by Ixx77; typically 0
except for vector control of induction motors) and the continuous current limit (|Ixx57| on Turbo PMAC,
in units of a 16-bit DAC) and multiplying by the time permitted at the instantaneous limit.
When using I2T limiting (Ixx57 > 0), the formula is:
Ixx69 2 Ixx77 2 Ixx 57 2
Ixx58 ServoUpdateRate ( Hz ) PermittedT ime(sec)
32768 2
When using |I|T limiting (Ixx57 < 0), the formula is:
2 2
Ixx69 Ixx77 Ixx 57
Ixx 58 ServoUpdateRate ( Hz ) PermittedT ime(sec)
32768
Refer to the Making the Application Safe section in the User manual for a more detailed explanation of
I2T and |I|T protection.
Example:
For I2T limiting, with the instantaneous current limit Ixx69 at 32,767, the magnetization current Ixx77 at
0, the continuous current limit Ixx57 at 10,589 (1/3 of max), the time permitted with maximum current at
1 minute, and the servo update rate at the default of 2.25 kHz, Ixx58 would be set as
2 2 2
Ixx 58 ( 1.0 0.0 0.33 ) 2250 60 120000
For |I|T limiting, with the instantaneous current limit Ixx69 at 24,576, the magnetization current Ixx77 at
0, the continuous current limit at 8192 (Ixx57 = -8192), the time permitted with maximum current at 3
seconds, and the servo update rate at 4 kHz, Ixx58 would be set as:
2 2
Ixx 58 ( 0.75 0.0 0.25 ) 4000 3 6000
expecting a steady-state position error. (In contrast, setting Ixx33 to 0 prevents further inputs to the
integrator, but maintains the output.)
The Ixx63 integration limit can also be used to create a fault condition for the motor. If Ixx63 is set to a
negative number, then PMAC will also check as part of its following error safety check whether the
magnitude of integrated following error has saturated at the magnitude of Ixx63. With Ixx63 negative, if
the integrator has saturated, PMAC will trip (kill) the motor with a following error fault. Both the normal
fatal following error motor status bit and the integrated following error status bit are set when this fault
occurs. If Ixx63 is 0 or positive, the motor cannot trip on integrated following error fault.
To set Ixx63 to a value such that the integrator saturates at the same point that its contribution to the
command output causes saturation at the Ixx69 level, use the following formula:
Ixx69 2 23
Ixx63
Ixx08 Ixx30
To cause trips, the magnitude of Ixx63 must be set to less than this value due to other potential
contributions to the output. Remember that the integrator stops increasing when the output saturates at
Ixx69.
Ixx63 is not used if the Extended Servo Algorithm for Motor xx is being executed (Iyy00=1).
Ixx64 Motor xx Deadband Gain Factor
Range: -32,768 - 32,767
Units: none
Default: 0 (no gain adjustment)
Ixx64 is part of the PMAC feature known as deadband compensation, which can be used to create or
cancel deadband. It controls the effective gain within the deadband zone (see Ixx65). When the
magnitude of the following error is less than the value of Ixx65, the proportional gain (Ixx30) is
multiplied by (Ixx64+16)/16. At a value of -16, Ixx64 provides true deadband.
Values between -16 and 0 yield reduced gain within the deadband. Ixx64 = 0 disables any deadband
effect.
Values of Ixx64 greater than 0 yield increased gain within the deadband; a value of 16 provides double
gain in the deadband. A small band of increased gain can be used to reduce errors while holding position,
without as much of a threat to make the system unstable. It is also useful in compensating for physical
deadband in the system.
Note:
Values of Ixx64 less than -16 will cause negative gain inside the deadband, making
it impossible for the system to settle inside the band. These settings have no
known useful function.
Outside the deadband, gain asymptotically approaches Ixx30 as the following error increases.
Ixx64 is not used if the Extended Servo Algorithm for Motor xx is being executed (Iyy00/50=1).
Ixx65 Motor xx Deadband Size
Range: -32,768 - 32,767
Units: 1/16 count
Default: 0
Ixx65 defines the size of the position error band, measured from zero error, within which there will be
changed or no control effort, for the PMAC feature known as deadband compensation. Ixx64 controls the
effective gain relative to Ix30 within the deadband.
Note:
The units of this parameter are 1/16 of a count, so the value should be 16 times the
number of counts in the deadband. For example, if modified gain is desired in the
range of +/-5 counts of following error, Ixx65 should be set to 80.
Ixx65 is not used if the Extended Servo Algorithm for Motor xx is being executed (Iyy00/50=1).
Ixx66 Motor xx PWM Scale Factor
Range: 0 - 32,767
Units: PWM_CLK cycles
Default: 6527
Ixx66 multiplies the output of the digital current loops for Motor x (which are values between -1.0 and
1.0) before they are written to the PWM output registers. As such, it determines the maximum value that
can be written to the PWM output register. Ixx66 is only used if Ixx82>0 to activate digital current loop
execution.
The PWM output value for each phase is compared digitally to the PWM up-down counter, which
increments or decrements once per PWM_CLK cycle to determine whether the outputs are on or off. The
limits of the up-down counter are set by the PWM maximum count variable, I7m00 for Servo IC m on
PMAC, and MI900, MI906, or MI992 on the MACRO Station.
With many power-block amplifiers, Ixx66 is set to about 10% above the PWM maximum count value.
This permits a full-on command of the phase for a substantial fraction of the commutation cycle,
providing maximum possible utilization of the power devices at maximum command. If Ixx66 is set to a
smaller value than PWM maximum count, it serves as a voltage limit for the motor (Vmax = VDC *
Ixx66 / PWM_Max_Count). Some amplifiers require that the PWM command never turn fully on or off;
in these amplifiers Ixx66 is usually set to about 95% of the PWM maximum count value. Note that Ixx69
serves as the current limit.
Digital current loop closure on the Turbo PMAC requires a set of three consecutive command output
registers. Generally, this requires writing to either a PMAC2-style Servo IC or a MACRO IC.
Ixx67 Motor xx Position Error Limit
Range: 0 – 8,388,607
Units: 1/16 count
Default: 4,194,304 (= 262,144 counts)
Ixx67 defines the biggest position error that will be allowed into the servo filter. This is intended to keep
extreme conditions from upsetting the stability of the filter. However, if it is set too low, it can limit the
response of the system to legitimate commands (this situation can particularly be noticed on very fine
resolution systems).
If pure velocity control is desired for the motor, Ixx67 can be set to 0, effectively disabling the position
loop.
This parameter is not to be confused with Ixx11 or Ixx12, the following error limit parameters. Those
parameters take action outside the servo loop based on the real (before limiting) following error.
Note:
The units of this parameter are 1/16 of a count, so the value should be 16 times the
number of counts in the limit.
Ixx67 is not used if the Extended Servo Algorithm for Motor xx is being executed (Iyy00=1).
Use when Commutating: When Turbo PMAC is commutating Motor xx, Ixx69 corresponds to peak
values of the sinusoidal phase currents. Motor and amplifier current limits are usually given as RMS
values. Peak phase values are 2, or 1.414, times greater than RMS values. For instance if an amplifier
has a 10 amp (RMS) instantaneous current limit, the instantaneous limit for the peak of the phase currents
is 14.14 amps.
Use with Magnetization Current: When commutating (Ixx01 bit 0 = 1), Ixx69 is technically the limit
of only the quadrature, or torque-producing, current. Ixx77 sets the magnitude of the direct, or
magnetization current, and the total current limit is the vector sum of these two variables. If the Ixx77
magnetization current for the motor is set to a value other than 0, Ixx69 should be set such that:
Ixx69 2 Ixx77 2 I max 32,767
Use in Direct-PWM Mode: When commutating (Ixx01 bit 0 = 1) and closing the current loop (Ixx82 >
0) of a 3-phase motor (Ixx72 = 683 or 1365), it is important to understand the relationship between the
quadrature current limited by Ixx69 and the phase currents measured by the A/D converters. This
difference is due to the nature of the conversion between direct and quadrature current components, which
are 90o apart, and the phase currents, which are 120o apart. This difference introduces a factor of cos(30 o)
into the calculations.
For a given level of DC quadrature current with zero direct (magnetization) current, the peak value of AC
sinusoidal current measured in the phases will be 1/cos(30 o), or 1.15 times, greater. When quadrature
current is commanded at its limit of Ixx69, the peak phase currents can be 15% higher that this value. For
instance, with Ixx69 at 10,000, and Ixx77 at 0, the A/D converters can provide readings (normalized to
16-bit resolution) up to 11,547.
With non-zero direct current, the peak value of AC sinusoidal current measured in the phases will be 1.15
times greater than the vector sum of the direct and quadrature currents. Therefore, in order not to saturate
the current in the phases, Ixx69 should be set such that:
2 2 o
Ixx69 Ixx77 I max cos 30 32 ,767 * 0.866 28 ,377
Examples:
1. Motor 1 is driving a velocity-mode amplifier with differential analog inputs that are limited to +/-10V
between the inputs. This means that the PMAC outputs should each be limited to +/-5V with respect to
the AGND reference. I169 should therefore be limited to 32,768/2 = 16,384.
2. Motor 3 is driving a DC brush motor amplifier in current (torque) mode with an analog output. The
amplifier has a gain of 2 amps/volt and an instantaneous current limit of 20 amps. The motor has an
instantaneous current limit of 15 amps.
PMAC’s maximum output of 32,768, or 10 volts, corresponds to 20 amps.
The motor has the lower instantaneous current rating, so we use its limit of 15 amps.
I369 is set to 32,768 * 15/20 = 24,576.
3. Motor 5 is driving a self-commutating brushless-motor amplifier in current (torque) mode with a
single analog output. The amplifier has a gain of 5 amps(RMS)/volt and an instantaneous current
limit of 50 amps (RMS). The motor has an instantaneous current limit of 60 amps (RMS).
PMAC’s maximum output of 32,768, or 10 volts, corresponds to 50 amps (RMS).
The amplifier has the lower instantaneous current rating, so we use its limit of 50 amps (RMS).
I569 is set to 32,768 * 50/50 = 32,767 (note that the maximum permitted value is 32,767).
4. Motor 7 is driving a sine-wave amplifier for a brushless servo motor with two analog outputs. The
Ixx77 magnetization current limit is set to 0. The amplifier has a gain on each phase of 4 amps/volt.
The amplifier has an instantaneous current limit of 25 amps (RMS). The motor has an instantaneous
current limit of 30 amps (RMS).
PMAC’s maximum output of 32,768, or 10 volts, corresponds to 40 amps peak in the phase.
The amplifier has the lower instantaneous current rating, so we use its limit of 25 amps (RMS).
25 amps (RMS) corresponds to peak phase currents of 25*1.414 = 35.35 amps.
I769 is set to 32,768 * 35.35/40 = 28,958.
5. Motor 9 is driving a direct-PWM power-block amplifier and an AC induction motor. The Ixx77
magnetization current parameter is set to 3000. The A/D converters in the amplifier are scaled so that
a maximum reading corresponds to 100 amps of current in the phase. The amplifier has an
instantaneous current limit of 60 amps (RMS), and the motor has an instantaneous current limit of 75
amps (RMS).
PMAC’s maximum ADC phase reading of 32,768 corresponds to 100 amps in the phase.
The amplifier has the lower instantaneous current rating, so we use its limit of 60 amps (RMS).
60 amps (RMS) corresponds to peak phase currents of 60*1.414 = 84.84 amps.
84.84 amps corresponds to an ADC reading of 32,768 * 84.84/100 = 27,800.
The vector sum of Ixx69 and Ixx77 should equal 27,800 * 0.866 = 24,075.
I969 should be set to sqrt(24,0752-3,0002) = 23,887.
Motor Commutation Setup I-Variables
Ixx70 Motor xx Number of Commutation Cycles (N)
Range: 0 – 255
Units: Commutation Cycles
Default: 1
For a PMAC-commutated motor (Ixx01=1), Ixx70 is used in combination with Ixx71 to define the size of
the commutation cycle, as Ixx71/Ixx70 counts. Usually, Ixx70 is set to one, and Ixx71 represents the
number of counts in a single commutation cycle. However, many people will use Ixx70 to represent the
number of commutation cycles (pole pairs) per mechanical revolution, and Ixx71 to represent the counts
per mechanical revolution. Ixx70 needs to be set greater than one if the number of counts in a single
cycle is not an integer.
A commutation cycle, or electrical cycle, consists of two poles (one pole pair) of a multiphase motor.
Setting Ixx70 to 0 effectively defeats the creation of the AC commutation cycle. This setting can be
useful when doing direct PWM control of DC brush motors which requires the use of the Turbo PMAC
commutation algorithms, but cannot use an AC output.
Example:
A 6-pole brushless motor has three commutation cycles per mechanical revolution. If a feedback device
with 4096 counts per mechanical revolution (a number not divisible by three) is used, Ixx70 should be set
to 3, and Ixx71 to 4096.
See Also:
I-variables Ixx01, Ixx71-Ixx83
Setting Up PMAC Commutation
Ixx71 Motor xx Counts per N Commutation Cycles
Range: 0 – 16,777,215
Units: counts
Default: 1000
For a Turbo PMAC-commutated motor, this parameter defines the size of a commutation cycle in
conjunction with Ixx70 (counts/cycle = Ixx71/Ixx70). The meaning of a count used in this parameter is
defined by the encoder-decode variable I7mn0 for the commutation feedback device. If a times-4 decode
is used, a count is one-fourth of an encoder line.
When the commutation position feedback is received over the MACRO ring, the units of the feedback are
typically 1/32 of a count, so Ixx71 should be in units of 1/32 count in this case.
A commutation cycle, or electrical cycle, consists of two poles (one pole pair) of a multiphase motor.
Note:
In firmware revisions V1.938 and older, the maximum value of Ixx71 was
8,388,607.
Examples:
1. A four-pole brushless motor with a 1000-line-per-revolution encoder and “times-4” decode has 2
commutation cycles per revolution and 4000 counts per revolution. Therefore, either Ixx70=2 and
Ixx71=4000 could be used, or Ixx70=1 and Ixx71=2000.
2. A linear motor has a 60.96-mm (2.4-inch) electrical cycle. An encoder with a 40 micron pitch is
wired directly into PMAC and “times-4” decode is used. Ixx70 can be set to 1 and Ixx71 can be
calculated as:
mm line counts counts
Ixx71 60.96 * *4 6096
cycle 0.04 mm line cycle
3. An 8-pole brushless motor has an 8192-line encoder that is wired into a Compact MACRO Station
with “times-4” decode. The position data is sent back to PMAC in the MACRO “Type 1” protocol,
with units of 1/32 count. If Ixx70 is set to 4 (for 4 electrical cycles per revolution), Ixx71 can be
calculated as:
lines rev counts ( 1 / 32count ) ( 1 / 32count )
Ixx71 8192 * *4 * 32 262 ,144
rev 4 cycles line count line
See Also:
I-variables Ixx01, Ixx70, Ixx72-Ixx83
Setting Up Turbo PMAC Commutation
Ixx72 Motor xx Commutation Phase Angle
Range: 0 – 2047
Units: 360/2048 elec. deg. (1/2048 commutation cycle)
Default: 1365 (= -120oe or 240oe)
For a Turbo PMAC-commutated motor, Ixx72 sets the angular distance between the phases of a
multiphase motor. The units of Ixx72 are 1/2048 of an electrical cycle. The usual values to be used are:
3-phase: 683 or 1365 (+/- 120oe)
2- or 4-phase: 512 or 1536 (+/- 90oe)
For a given number of phases, the proper choice of the two possible values is determined by the polarity
match between the output commands and the feedback, as detailed below. Typically, the choice is made
automatically by the Turbo Setup expert-system program on the PC.
Ixx72 is used slightly differently depending on whether Turbo PMAC is performing current-loop
calculations as well as commutation. Both cases are explained below:
1. Turbo PMAC performing commutation, but not current loop: When Turbo PMAC is not
performing digital current loop closure for Motor xx (Ixx82=0), the output direction sense determined
by this parameter and the motor and amplifier phase wiring must match the feedback direction sense
as determined by the encoder-decode variable I7mn0 and the encoder wiring. If the direction senses
do not match, proper commutation and servo control will be impossible; the motor will lock into a
given position.
For these systems, changing between the two values for a given number of phases has the same effect
as exchanging motor leads, which changes the motor's direction of rotation for a given sign of a
PMAC2 torque command.
Refer to the section Setting up Turbo PMAC Commutation for tests to determine the proper Ixx72
setting. For systems without Turbo PMAC digital current loop closure, once this
commutation/feedback polarity has been properly matched, the servo/feedback polarity will
automatically be properly matched.
2. Turbo PMAC performing commutation and current loop: When Turbo PMAC (PMAC2-style
interface only) is performing digital current loop closure for Motor xx (Ixx82 > 0), the output
direction sense determined by this parameter must match the polarity of the phase current sensors and
the analog-to-digital conversion (ADC) circuitry that brings this data into Turbo PMAC. It is
independent of motor or amplifier phase wiring, encoder wiring, and Turbo PMAC encoder-decode
direction sense.
WARNING:
Do not attempt to close the digital current loops on Turbo PMAC (O commands or
closing the position loop) until sure of the proper sense of the Ixx72 setting. An
Ixx72 setting of the wrong sense will cause positive feedback in the current loop,
leading to saturation of the PMAC outputs and possible damage to the motor and
or amplifier.
For systems with a Turbo PMAC digital current loop, if the phase-current ADC registers report a positive
value for current flowing into the phase (i.e. the PWM voltage command value and the current feedback
value have the same sign), Ixx72 must be set to a value greater than 1024 (usually 1365 for a 3-phase
motor or 1536 for a 2- or 4-phase motor).
If the phase-current ADC registers report a positive value for current flowing out of the phase (i.e. the
PWM voltage command value and the current feedback value have opposite signs), Ixx72 must be set to a
value less than 1024 (usually 683 for a 3-phase motor, or 512 for a 2- or 4-phase motor).
For systems with Turbo PMAC digital current loop closure, the commutation/feedback polarity match is
independent of the servo/feedback polarity. Once Ixx72 has been set for proper commutation/feedback
polarity, the proper position-loop servo/feedback polarity must still be established.
Ixx73 Motor xx Phase Finding Output Value
Range: -32,768 – 32,767
Units: bits of 16-bit DAC
Default: 0
WARNING:
An unreliable phasing search method can lead to a runaway condition. Test the
phasing search method carefully to make sure it works properly under all
conceivable conditions. Make sure the Ix11 fatal following error limit is active
and as tight as possible so the motor will be killed quickly in the event of a serious
phasing search error.
Ixx73 defines the magnitude of the open-loop output to be used if a power-on phasing search is done for a
Turbo PMAC-commutated motor (Ixx01 bit 0 = 1). A phasing search is required for a synchronous motor
(Ixx78=0) such as a permanent-magnet brushless motor with no absolute position sensor (Ixx81=0). The
phasing search is done automatically as part of the power-on phasing search if Ixx80 is 1 or 3; if Ixx80 is
0 or 2, the on-line $ or $$ command must be used must be used to initiate the phasing search.
Ixx73 is in units of a 16-bit DAC, so that 32,767 represents full current command to the phases, even if a
different output device and/or different resolution is used.
If Ixx80 is 0 or 1, the “two-guess” phasing search is used, and Ixx73 controls the “vector” magnitude of
the open-loop output that is distributed among the phases according to the guessed phasing angle.
If Ixx80 is 2 or 3, the “stepper-motor” phasing search is used, and Ixx73 controls the magnitude of current
forced into individual phases to lock the motor to a position like a stepper motor. In this method, if the
Turbo PMAC is not performing current loop closure for the motor (Ixx82=0) and Ixx72 > 1024, then
Ixx73 should be set to a negative number of the desired magnitude. In all other cases it should be set to a
positive number. If the sign of Ixx73 is wrong for a setup, the motor will run away when the loop is
closed.
A negative value of Ixx73 must be used for sinewave-output commutation (Ixx82 = 0) with Ixx72 > 1024
and the stepper-motor phase search method (Ixx80 bit 0 = 1).
Typically, values of magnitude 2000 to 6000 are used for Ixx73 in either method.
See Also:
Power-Up Phasing Search (Setting Up PMAC Commutation)
I-Variables Ixx01, Ixx74, Ixx78, Ixx80, Ixx81
Ixx74 Motor xx Phase Finding Time
Range: 0 – 255
Units: Servo Interrupt Cycles (for Ixx80 = 0 or 1)
or
Servo Interrupt Cycles * 256 (for Ixx80 = 2 or 3)
Default: 0
WARNING
An unreliable phasing search method can lead to a runaway condition. Test the
phasing search method carefully to make sure it works properly under all
conceivable conditions. Make sure the Ixx11 fatal following error limit is active
and as tight as possible so the motor will be killed quickly in the event of a serious
phasing search error.
Ixx74 defines the time that an open-loop output is to be used if a power-on phasing search is done for a
PMAC-commutated motor (Ixx01 bit 0 = 1). A phasing search is required for a synchronous motor
(Ixx78=0) such as a permanent-magnet brushless motor with no absolute position sensor (Ixx81=0). The
phasing search is done automatically as part of the power-on phasing search if bit 0 of Ixx80 is 1; if bit 0
of Ixx80 is 0, the on-line $ or $$ command must be used must be used to initiate the phasing search.
If Ixx74 is set to 0, no phasing search move will be done, even if one is requested and required. In this
case, the “phase reference error” motor status bit will stay set, preventing the servo loop from closing.
If bit 1 of Ixx80 is 0 (Ixx80 = 0 or 1), the two-guess phasing search is used; Ixx74 has units of servo
cycles and controls the time for the open-loop command at each “guess” of the phase angle. Typical
values are three to ten servo cycles; a value of 5 is a good starting point.
If bit 1 of Ixx80 is 1 (Ixx80 = 2 or 3), the stepper-motor phasing search is used; Ixx74 has units of (servo
cycles*256) and controls the time current is forced into each phase and Turbo PMAC waits for the motor
to settle into the step position. With the default servo cycle rate of 2.25 kHz, each unit of Ixx74
represents about 0.1 seconds in this mode; typical values are 10 to 20.
See Also:
Power-Up Phasing Search (Setting Up PMAC Commutation)
I-Variables Ixx01, Ixx73, Ixx78, Ixx80, Ixx81
Ixx75 Motor xx Phase Position Offset
Range: 0 – Ixx71 (up to 16,777,215)
Units: Counts * Ixx70
Default: 0
Ixx75 tells Turbo PMAC the distance between the zero position of an absolute sensor used for power-on
phase position (specified by Ixx81 and Ixx91) and the zero position of Turbo PMAC's commutation
cycle.
It is used to reference the phasing algorithm for a PMAC-commutated motor with an absolute sensor
(Ixx81 > 0). If Ixx80 bit 0 is 1 (Ixx80 = 1 or 3), this is done automatically during the power-up/reset
cycle. It will also be done in response to a $ on-line command to the motor, or a $$ on-line command to
the coordinate system containing the motor.
Ixx75 is also used by the SETPHASE command (on-line, motion-program, or PLC-program). When the
SETPHASE command is given, the value of Ixx75 is immediately copied directly into the motor’s phase
position register. Typically, this operation is used to correct the phasing, usually at the encoder index
pulse, after an initial rough phasing (e.g. from Hall commutation sensors).
The proper value for this parameter can be found with a simple procedure that should be done with an
unloaded motor, after satisfactory operation has been achieved using a power-on phasing search.
Define an M-variable to the absolute sensor if using one.
Define an M-variable to the internal phase position register. Mxx71 is the suggested M-variable.
Give the motor an O0 command.
Put a bias (a magnitude of 2000 is usually good) on the A phase (higher-numbered DAC of a pair for
Turbo PMAC) by setting Ixx29; use a positive bias if Ixx82>0 for digital current loop closure or if
Ixx82=0 and Ixx72>1024 (e.g. 1365 or 1536); use a negative bias if Ixx82=0 and Ixx72<1024 (e.g.
683 or 512).
Also, put a bias in the opposite direction of the same magnitude on the B phase by setting Ixx79. The
motor should lock in on a position like a stepper motor.
Now remove the A-phase bias by setting Ixx29 back to zero, or at least to the value found to force
zero current in the phase, and the motor should lock in on another position. This position is the zero
position of the phasing cycle.
If there is an absolute sensor, after sure that the motor has settled, read the position of the absolute
sensor by querying its M-variable value. Then:
Take the negative of this value, multiply it by Ixx70, and put the resulting value in Ixx75.
Now, with Ixx79 returned to zero or the proper bias, and Ixx81 pointing to the absolute sensor, give
the motor a $ command. The motor should be properly phased.
If doing this to use the SETPHASE command at a known position such as the index, set the internal
phase position register to 0 with Mxx71. Then:
Return Ixx79 to zero or the proper bias, and close the loop with a J/ command.
Now move to the reference position (e.g. do a homing search move with the index pulse as the
trigger) and make sure it is settled there with minimal following error (some integral gain should be
used).
Read the value of Mxx71 at this point and set Ixx75 to this value.
Remember to save these variable values before doing a full reset on the card.
See Also
I-variables Ixx01, Ixx70 – Ixx74, Ixx76 – Ixx83
Setting Up Turbo PMAC Commutation
Turbo PMAC computes the slip frequency each phase update by multiplying the torque command from
the position/velocity-loop servo (or O-command magnitude) by Ixx78 and dividing by the magnetization
current value controlled by Ixx77.
Ixx78 is typically set through use of the Turbo Setup expert-system program running on PCs. This
program excites the motor and analyzes its response to derive an optimum Ixx78 value.
Ixx78 can also be set experimentally by giving the motor an O-command and watching the velocity
response, probably with the data-gathering feature. As the velocity saturates because the back EMF
reaches the supply voltage, the velocity should fall back about 5% to reach a steady-state value. If it falls
back more than this, the slip time constant is too high; if it falls back less than this, or not at all, the slip
time constant is too low.
0.00015 is a typical value of Ixx78 for a standard induction motor at a phase update rate of about 9 kHz.
Ixx78 is only active if Ixx01 is set to 1 to specify Turbo PMAC commutation of Motor xx. It should be
set to 0 for AC synchronous motors such as permanent-magnet brushless motors and switched (variable)
reluctance motors.
Ixx79 Motor xx Second Phase Offset
Range: -32,768 – 32,767
Units: 16-bit DAC/ADC bit equivalent
Default: 0
Ixx79 serves as an output or feedback offset for Motor xx; its exact use depends on the mode of operation
as described below:
Mode 1: When Turbo PMAC is not commutating Motor xx (Ixx01 bit 0 = 0), Ixx79 is not used. Ixx29 is
the offset for this mode.
Mode 2: When Turbo PMAC is not commutating Motor xx (Ixx01 bit 0 = 0) but is in sign-and-
magnitude output mode (Ixx96 = 1 – PMAC-style outputs only), Ixx79 is the offset of the command
output value after the absolute value is taken (Ixx29 is the offset before the absolute value is taken).
Typically, Ixx79 is used in this mode to compensate for analog offsets in interface circuitry, either in
DACs or in voltage-to-frequency converters.
Mode 3: When Turbo PMAC is commutating Motor xx (Ixx01 bit 0 = 1) but not closing the current loop
(Ixx82 = 0), Ixx79 serves as the offset for the second of two phase command output values (Phase B), for
the address specified by Ixx02 plus 1; Ixx29 serves the same purpose for the first phase. Ixx79 is added
to the output command value before it is written to the command output register.
When commutating from a PMAC-style Servo IC, Phase A is output on the higher-numbered of the two
DACs (e.g. DAC2) and Phase B on the lower-numbered (e.g. DAC1). When commutating from a
PMAC2-style Servo IC, Phase A is output on the A-channel DAC (e.g. DAC1A), Phase B on the B-
channel DAC (e.g. DAC1B).
As an output command offset, Ixx79 is always in units of a 16-bit register, even if the actual output device
is of a different resolution. For example, if a value of 60 had to be written into an 18-bit DAC to create a
true zero command, this would be equivalent to a value of 60/4=15 in a 16-bit DAC, so Ixx79 would be
set to 15 to cancel the offset.
Mode 4: When Turbo PMAC is commutating (Ixx01 bit 0 = 1) and closing the current loop for Motor xx
(Ixx82 > 0), Ixx79 serves as an offset that is added to the phase current reading from the ADC for the
second phase (Phase B), at the address specified by Ixx82. Ixx29 performs the same function for the first
phase. The sum of the ADC reading and Ixx79 is used in the digital current loop algorithms.
As an input feedback offset, Ixx79 is always in units of a 16-bit ADC, even if the actual ADC is of a
different resolution. For example, if a 12-bit ADC reported a value of -5 when no current was flowing in
the phase, this would be equivalent to a value of -5*16=-80 in a 16-bit ADC, so Ixx79 would be set to 80
to compensate for this offset.
WARNING:
An unreliable phasing search method can lead to a runaway condition. Test the
phasing search method carefully to make sure it works properly under all
conceivable conditions. Make sure the Ixx11 fatal following error limit is active
and as tight as possible so the motor will be killed quickly in the event of a serious
phasing search error.
Phasing search move method: The two-guess phasing search is very quick and requires little
movement, but can be adversely affected if there are significant external loads such as friction and
gravity. The stepper-motor phasing search takes more time and causes more movement, but it is more
reliable in the presence of significant external loads.
Absolute motor position read: If Ixx10 is set to 0, the position reference for a motor comes from a
homing search move. If Ixx10 is greater than 0, the position reference comes from reading an absolute
position sensor at the address specified by Ixx10 and with the format specified by Ixx95. In this case,
Ixx80 bit 2 specifies whether this read is done automatically at power-up/reset.
If the absolute position read is not done automatically at power-up/reset, the motor position will be set to
0 at this time. This does not prevent full operation of the motor. The $* or $$* command must be used
later to read the sensor and establish absolute position. Even if the absolute position is read automatically
at power-up/reset, it may be read again later with the $* or $$* command.
See Also:
Power-Up Phasing Search (Setting Up PMAC Commutation)
On-line commands $, $$, $* $$*, $$$
I-Variables Ixx01, Ixx73, Ixx74, Ixx78, Ixx81
Ixx81 Motor xx Power-On Phase Position Address
Range: $000000 - $FFFFFF
Units: Turbo PMAC or multiplexer-port addresses
Default: 0
WARNING:
An unreliable phasing reference method can lead to a runaway condition. Test the
phasing reference method carefully to make sure it works properly under all
conceivable conditions. Make sure the Ixx11 fatal following error limit is active
and as tight as possible so the motor will be killed quickly in the event of a serious
phasing search error.
Ixx81 tells Turbo PMAC what address to read for absolute power-on phase-position information for
Motor xx, if such information is present. This can be a different address from that of the ongoing phase
position information, which is specified by Ixx83, but it must have the same resolution and direction
sense. Ixx81 is set to zero if no special power-on phase position reading is desired, as is the case for an
incremental encoder.
If Ixx81 is set to zero, a power-on phasing search routine is required for synchronous fixed-field brushless
motors (permanent magnet, and switched reluctance); those that have a slip gain (Ixx78) of zero. Turbo
PMAC’s automatic phasing search routines based on Ixx73 and Ixx74 can be used, or a custom power-on
PLC routine can be written.
Note:
Ixx81 is used for PMAC’s commutation algorithms alone, to locate position within
one electrical cycle of the motor. It is not used for any servo loop position
information, even for power-up. Ixx10 and Ixx95 are used for that purpose.
Ixx91 tells how the data at the address specified by Ixx81 is to be interpreted. It also determines whether
the location specified by Ixx81 is a multiplexer (thumbwheel) port address, an address in Turbo PMAC’s
own memory and I/O space, or a MACRO node number.
Note:
It is easier to specify this parameter in hexadecimal form ($ prefix). If I9 is set to 2
or 3, the value of this variable will be reported back to the host in hexadecimal
form.
R/D Converter Read: If Ixx91 contains a value from $000000 to $070000, Ixx81 contains the
multiplexer port address of an Acc-8D Option 7 R/D-converter board. The value of Ixx81 matches the
base address of the board (0 to 248 decimal, $0 to $F8 hex) on the port as set by its DIP switches. If the
base address is 0, Ixx81 should be set to $100, because a value of 0 in Ixx81 disables the absolute read.
The following table lists the possible values of Ixx81 in this mode.
Ixx81 for Acc-8D Option 7 Resolver/Digital Converter
(Ixx91=$000000 - $070000)
Addresses are Multiplexer Port Addresses
Board Ixx81 Board Ixx81 Board Ixx81 Board Ixx81
Mux. Mux. Mux. Mux.
Addr. Addr. Addr. Addr.
0 $000100 64 $000040 128 $000080 192 $0000C0
8 $000008 72 $000048 136 $000088 200 $0000C8
16 $000010 80 $000050 144 $000090 208 $0000D0
24 $000018 88 $000058 152 $000098 216 $0000D8
32 $000020 96 $000060 160 $0000A0 224 $0000E0
40 $000028 104 $000068 168 $0000A8 232 $0000E8
48 $000030 112 $000070 176 $0000B0 240 $0000F0
56 $000038 120 $000078 184 $0000B8 248 $0000F8
Parallel Data Read: If Ixx91 contains a value from $080000 to $180000 or from $480000 to $580000,
Ixx81 specifies the address of a Turbo PMAC memory or I/O register where it will read the power-on
phase position. Bits 16 to 21 of Ixx91, which can take a value of $08 to $18 (8 to 24) in this mode,
specify the number of bits, starting at bit 0, of the register to be read for the absolute position.
Bit 22 of Ixx91 controls whether the address specified in Ixx81 is an X-register or a Y-register. If bit 22
of Ixx91 is set to 0, it is a Y-register. If bit 22 of Ixx91 is set to 1, it is an X-register.
There are four common sources of parallel data for absolute power-on phase position read. The first
source is an Acc-14D/V parallel I/O board. Acc-14D/V boards map into Y-registers, so bit 22 of Ixx91 is
set to 0. The settings of Ixx81 for each port of each possible Acc-14DV board are shown in the following
table:
If the flag register is in a PMAC-style Servo IC, the flags used are HMFLn, +LIMn, and -LIMn. Usually,
the flag register is for the “spare” (even-numbered) set of flags corresponding to the second DAC output
used for the commutation. The following table shows the values of Ixx81 used here.
Turbo PMAC Ixx81 Typical Hall Phasing Settings
(Ixx91=$800000 - $FF0000)
Hall Flag PMAC First Second Third Fourth
Channel # Acc-24P/V Acc-24P/V Acc-24P/V Acc-24P/V
Channel 2 $078004 $078204 $079204 $07A204 $07B204
Channel 4 $07800C $07820C $07920C $07A20C $07B20C
Channel 6 $078104 $078304 $079304 $07A304 $07B304
Channel 8 $07810C $07830C $07930C $07A30C $07B30C
If the flag register is in a PMAC2-style Servo IC, the flags used are CHUn, CHVn, and CHWn. Usually
the flag register is the same register as used for the main flags as specified by Ixx25.
The following table shows the values of Ixx81 used here.
Turbo PMAC2 Ixx81 Typical Hall Phasing Settings
(Ix91=$800000 - $FF0000)
Servo Chan. 1 Chan. 2 Chan. 3 Chan. 4 Notes
IC #
0 $078000 $078008 $078010 $078018 First IC on board PMAC2, 3U stack
1 $078100 $078108 $078010 $078018 Second IC on board PMAC2, 3U stack
2 $078200 $078208 $078210 $078218 First Acc-24E2x, first IC on first Acc-24P/V2
3 $078300 $078308 $078310 $078318 Second Acc-24E2x, second IC on first Acc-24P/V2
4 $079200 $079208 $079210 $079218 Third Acc-24E2x, first IC on second Acc-24P/V2
5 $079300 $079308 $079310 $079318 Fourth Acc-24E2x, second IC on second Acc-24P/V2
6 $07A200 $07A208 $07A210 $07A218 Fifth Acc-24E2x, first IC on third Acc-24P/V2
7 $07A300 $07A308 $07A310 $07A318 Sixth Acc-24E2x, second IC on third Acc-24P/V2
8 $07B200 $07B208 $07B210 $07B218 Seventh Acc-24E2x, first IC on fourth Acc-24P/V2
9 $07B300 $07B308 $07B310 $07B318 Eighth Acc-24E2x, second IC on fourth Acc-24P/V2
If the flag register is obtained through the MACRO ring, Ixx81 will contain the address of a MACRO
auxiliary image register in RAM. The following table shows the typical values of Ixx81 used here.
When the digital current loop is used for drives connected directly to the Turbo PMAC2, the typical
values for Ixx82 are:
Turbo PMAC2 Ixx82 Typical Settings
Ixx82 Value Register Ixx82 Value Register
I182 $078006 PMAC2 ADC1B I1782 $079206 Second Acc-24x2 ADC1B
I282 $07800E PMAC2 ADC2B I1882 $07920E Second Acc-24x2 ADC2B
I382 $078016 PMAC2 ADC3B I1982 $079216 Second Acc-24x2 ADC3B
I482 $07801E PMAC2 ADC4B I2082 $07921E Second Acc-24x2 ADC4B
I582 $078106 PMAC2 ADC5B I2182 $079306 Second Acc-24x2 ADC5B
I682 $07810E PMAC2 ADC6B I2282 $07930E Second Acc-24x2 ADC6B
I782 $078116 PMAC2 ADC7B I2382 $079316 Second Acc-24x2 ADC7B
I882 $07811E PMAC2 ADC8B I2482 $07931E Second Acc-24x2 ADC8B
I982 $078206 First Acc-24x2 ADC1B I2582 $07A206 Third Acc-24x2 ADC1B
I1082 $07820E First Acc-24x2 ADC2B I2682 $07A20E Third Acc-24x2 ADC2B
I1182 $078216 First Acc-24x2 ADC3B I2782 $07A216 Third Acc-24x2 ADC3B
I1282 $07821E First Acc-24x2 ADC4B I2882 $07A21E Third Acc-24x2 ADC4B
I1382 $078306 First Acc-24x2 ADC5B I2982 $07A306 Third Acc-24x2 ADC5B
I1482 $07830E First Acc-24x2 ADC6B I3082 $07A30E Third Acc-24x2 ADC6B
I1582 $078316 First Acc-24x2 ADC7B I3182 $07A316 Third Acc-24x2 ADC7B
I1682 $07831E First Acc-24x2 ADC8B I3282 $07A31E Third Acc-24x2 ADC8B
When the digital current loop is used for drives connected to the Turbo PMAC2 Ultralite through a
MACRO station, the typical values for Ixx82 are:
Turbo PMAC2 Ultralite Ixx82 Typical Settings
Ixx82 Value Register Ixx82 Value Register
I182 $078422 MACRO IC 0 Node 0 Reg. 2 I1782 $07A422 MACRO IC 2 Node 0 Reg. 2
I282 $078426 MACRO IC 0 Node 1 Reg. 2 I1882 $07A426 MACRO IC 2 Node 1 Reg. 2
I382 $07842A MACRO IC 0 Node 4 Reg. 2 I1982 $07A42A MACRO IC 2 Node 4 Reg. 2
I482 $07842E MACRO IC 0 Node 5 Reg. 2 I2082 $07A42E MACRO IC 2 Node 5 Reg. 2
I582 $078432 MACRO IC 0 Node 8 Reg. 2 I2182 $07A432 MACRO IC 2 Node 8 Reg. 2
I682 $078436 MACRO IC 0 Node 9 Reg. 2 I2282 $07A436 MACRO IC 2 Node 9 Reg. 2
I782 $07843A MACRO IC 0 Node 12 Reg. 2 I2382 $07A43A MACRO IC 2 Node 12 Reg. 2
I882 $07843E MACRO IC 0 Node 13 Reg. 2 I2482 $07A43E MACRO IC 2 Node 13 Reg. 2
I982 $079422 MACRO IC 1 Node 0 Reg. 2 I2582 $07B422 MACRO IC 3 Node 0 Reg. 2
I1082 $079426 MACRO IC 1 Node 1 Reg. 2 I2682 $07B426 MACRO IC 3 Node 1 Reg. 2
I1182 $07942A MACRO IC 1 Node 4 Reg. 2 I2782 $07B42A MACRO IC 3 Node 4 Reg. 2
I1282 $07942E MACRO IC 1 Node 5 Reg. 2 I2882 $07B42E MACRO IC 3 Node 5 Reg. 2
I1382 $079432 MACRO IC 1 Node 8 Reg. 2 I2982 $07B432 MACRO IC 3 Node 8 Reg. 2
I1482 $079436 MACRO IC 1 Node 9 Reg. 2 I3082 $07B436 MACRO IC 3 Node 9 Reg. 2
I1582 $07943A MACRO IC 1 Node 12 Reg. 2 I3182 $07B43A MACRO IC 3 Node 12 Reg. 2
I1682 $07943E MACRO IC 1 Node 13 Reg. 2 I3282 $07B43E MACRO IC 3 Node 13 Reg. 2
Some amplifiers will transmit status and fault information on the end of the serial data stream for the
ADC, and it is important to mask out these values from the current loop equations.
Examples:
For a 10-bit ADC: Ixx84=$FFC000
For a 12-bit ADC: Ixx84=$FFF000
For a 16-bit ADC: Ixx84=$FFFF00
Further Motor I-Variables
Ixx85 Motor xx Backlash Take-up Rate
Range: 0 - 8,388,607
Units: 1/16 count / background cycle
Default: 0
Ixx85 determines how fast backlash is taken up on direction reversal. The size of the backlash is
determined by Ixx86, and possibly by the backlash compensation table for the motor. Turbo PMAC will
take up the backlash at the Ixx85 rate whenever the commanded or Master Handwheel position for the
motor reverses by more than the amount set by Ixx87 the backlash hysteresis parameter. If Ixx85 is zero,
backlash is effectively disabled. Usually, Ixx85 is set interactively and experimentally to as high a value
as possible without creating dynamic problems.
Ixx86 Motor xx Backlash Size
Range: 0 - 8,388,607
Units: 1/16 count
Default: 0
Ixx86 allows PMAC to compensate for backlash in the motor's coupling by adding or subtracting
(depending on the new direction) the amount specified in the parameter to the commanded position on
direction reversals (this offset will not appear when position is queried or displayed). A value of zero
means no backlash. The rate at which this backlash is added or subtracted (taken up) is determined by
Ixx85.
Variable Ixx87, Backlash Hysteresis, determines the amount of reversal in desired position that is
required before backlash will start to be introduced or removed.
If backlash tables are used, Ixx86 represents the backlash at motor zero position; values in the table
should represent the difference between the backlash at a given position and Ixx86.
Note:
The units of this parameter are 1/16 of a count so the value should be 16 times the
number of counts of backlash compensation desired.
Example:
If there is a backlash on reversal of motor direction of 7.5 encoder counts, set Ixx86 to 7.5 * 16 = 120.
Ixx87 Motor xx Backlash Hysteresis
Range: 0 - 8,388,607
Units: 1/16 count
Default: 64 (= 4 counts)
Ixx87 controls the size of the direction reversal in motor commanded position that must occur on Motor
xx before Turbo PMAC starts to add the programmed backlash (Ixx86) in the direction of motion. The
purpose of this variable is to allow the customer to ensure that a very small direction reversal (e.g. from
the dithering of a master encoder) does not cause the backlash to kick in. Ixx87 thus provides a hysteresis
in the backlash function.
The units of Ixx87 are 1/16 of a count. Therefore, this parameter must hold a value 16 times larger than
the number of counts reversal at which backlash is introduced. For example, if backlash is to be
introduced after five counts of reversal, Ixx87 should be set to 80.
Example:
With a system in which one count of the master encoder creates 10 counts of movement in the slave
motor, it is desired that a single count reversal of the master not trigger backlash reversal. Therefore, the
backlash hysteresis is set to 15 counts, and Ixx87 is set to 15*16=240.
Ixx88 Motor xx In-Position Number of Scans
Range: 0 - 255
Units: Background computation cycles (minus one)
Default: 0
Ixx88 permits the user to define the number of consecutive scans that Turbo PMAC Motor xx must
satisfy all in-position conditions before the motor in-position status bit is set true. This permits the user to
ensure that the motor is truly settled in the end position before executing the next operation, on or off
Turbo PMAC. The number of consecutive scans required is equal to Ixx88 + 1.
Turbo PMAC scans for the in-position condition of each active motor during the housekeeping part of
every background cycle, which occurs between each scan of each enabled background PLC (PLC 1-31).
All motors in a coordinate system must have true in-position bits for the coordinate-system in-position bit
to be set true.
In non-Turbo PMACs, this function is controlled by global I-variable I7.
Ixx90 Motor xx Rapid Mode Speed Select
Range: 0-1
Units: None
Default: 1
Ixx90 determines which variable is used for the speed of a RAPID mode move. When Ixx90 is set to 0,
the jog speed parameter Ixx22 is used. When Ixx90 is set to the default of 1, the maximum program
speed parameter Ixx16 is used. Regardless of the setting of Ixx90, the jog acceleration parameters Ixx19 -
Ixx21 control the acceleration and deceleration of a RAPID mode move.
In non-Turbo PMACs, this function is controlled by global I-variable I50.
Ixx91 Motor xx Power-On Phase Position Format
Range: $000000 - $FFFFFF
Units: None
Default: 0
Ixx91 specifies how the power-on phase-position data, if any, for Motor xx is interpreted. Ixx81 specifies
the address of the register containing this position data; Ixx91 controls how that data is read. This permits
the use of a wide variety of absolute position sensors with the Turbo PMAC.
Ixx91 is used only on power-on/reset or on the $ or $$ on-line reset commands. To get a new value of
Ixx91 to take effect, the $ or $$ command must be issued, or the value of Ixx91 must be stored to non-
volatile flash memory with the SAVE command, and the board must be reset.
Ixx91 is a 24-bit value; currently only bits 16-23, which comprise the first two of six hex digits, are used.
Ixx91 is only used if Ixx81 is set to a non-zero value.
The possible values of Ixx91 and the position sources they specify are summarized in the following table:
Ixx91 Value Range Absolute Position Source Ixx81 Address Type
$000000 - $070000 Acc-8D Opt 7 R/D Converter Multiplexer Port
$080000 - $180000 Parallel Data Y-Register Turbo PMAC Memory-I/O
$480000 - $580000 Parallel Data X-Register Turbo PMAC Memory-I/O
$730000 MACRO Station R/D Converter MACRO Node Number
$740000 MACRO Station Parallel Read MACRO Node Number
$800000 - $FF0000 Hall Sensor Read Turbo PMAC Memory-I/O
R/D Converter: If Ixx91 contains a value from $000000 to $070000, Motor xx will expect its absolute
power-on phase position from an Acc-8D Option 7 R/D converter board. Ixx81 should contain the
address of the board on the multiplexer port, as set by the DIP switches on the board.
The second hex digit of Ixx91, which can take a value from 0 to 7 in this mode, specifies the number of
the individual R/D converter at that multiplexer port address. This is a function of the DIP switch setting
on the board and the location of the converter on the board, as specified in the following table:
Ixx91 Value Acc-8D Opt. 7 # of R/D Converter
SW1-1 Setting on Acc-8D Opt. 7
$000000 CLOSED (0) 1
$010000 CLOSED (0) 2
$020000 CLOSED (0) 3
$030000 CLOSED (0) 4
$040000 OPEN (1) 1
$050000 OPEN (1) 2
$060000 OPEN (1) 3
$070000 OPEN (1) 4
Parallel Data Read: If Ixx91 contains a value from $08000n to $18000n, or from $48000n to $58000n,
Motor xx will do a parallel data read of the Turbo PMAC memory or I/O register at the address specified
by Ixx81.
In this mode, bits 16 to 21 specify the number of bits to be read. If the last hex digit of Ixx91 is 0,
consecutive bits will be read from the address specified by Ixx81, with the least significant bit read from
bit 0. This format is used for registers and I/O devices with 24-bit interfaces.
If the last hex digit of Ixx91 is 4, 5, or 6, data will be read in byte-wide pieces, with the least significant
byte at the address specified in Ixx81, the next byte at one address higher, and the next byte (if used) at
one more address higher. This format is intended for getting parallel data from the Acc-3E 3U-format
stack I/O board or the Acc-14E 3U-format pack (UMAC) I/O board, which have byte-wide interfaces.
For this format, the last hex digit of Ixx91 determines which byte of the 24-bit word is used, according to
the following table:
Ixx91 Last Digit Byte Bits
4 Low 0–7
5 Middle 8 – 15
6 High 16 – 23
In this mode, bit 22 of Ixx91 specifies whether a Y-register is to be read, or an X-register. A value of 0 in
this bit, yielding Ixx91 values from $080000 to $180000, specifies a Y-register; a value of 1, yielding
Ixx91 values from $480000 to $580000, specifies an X-register.
For the Acc-8D Option 9 Yaskawa Absolute Encoder Converter, Turbo PMAC’s 24-bit encoder phase
position register, an X-register, is read, so Ixx91 is set to $580000 ($180000 + $400000).
For the Acc-49 Sanyo Absolute Encoder Converter, the encoder provides a 13-bit value within one motor
revolution, and the data is read from a Y-register, so Ixx91 is set to $0D0000.
Example: If Ixx81=$078D01 and Ixx91=$140000, Turbo PMAC would read 20 bits (bits 0 – 19) from
Y:$078D01.
Example: If Ixx81=$078C00 and Ixx91=$100004, Turbo PMAC would read 16 bits, with the low eight
bits from the low byte of Y:$078C00, and the high eight bits from the low byte of Y:$078C01.
Example: If Ixx81=$079E03 and Ixx91=$120005, Turbo PMAC would read 18 bits, with the low eight
bits from the middle byte of Y:$079E03, and the next eight bits from the middle byte of Y:$079E04, and
the high 2 bits from the first 2 bits of the middle byte of Y:$079E05.
MACRO R/D Read: If Ixx91 contains a value of $730000, Motor xx will read the absolute phase
position from an Acc-8D Option 7 Resolver-to-Digital Converter through a MACRO Station or
compatible device.
In this mode, Ixx81 specifies the MACRO node number. MACRO Station setup variable MI11x for the
matching node must be set to read the R/D converter.
MACRO Parallel Read: If Ixx91 contains a value of $740000, Motor xx will read the absolute phase
position from a parallel data source through a MACRO Station or compatible device.
In this mode, Ixx81 specifies the MACRO node number. MACRO Station setup variable MI11x for the
matching node must be set to read the parallel data source.
Hall Sensor Read: If Ixx91 contains a value from $800000 to $FF0000 (bit 23 set to 1), Motor xx will
read bits 20 through 22 of the Turbo PMAC memory or I/O register at the address specified by Ixx81. It
will expect these three bits to be encoded as the U, V, and W hall-effect commutation signals with 120oe
spacing for the absolute power-on phase position. In this mode, the address specified in Ixx81 is usually
that of a flag register.
Note:
Hall-style commutation sensors give only an approximate phase position, with a
+/-30oe error. Generally, it is necessary to correct the phase position value at a
known position such as the encoder’s index pulse, either using the SETPHASE
command or by writing directly into the phase position register (suggested M-
variable Mxx71).
If the flag register is in a PMAC-style Servo IC, the flag inputs for bits 20, 21, and 22, representing W, V,
and U, are +LIMn, -LIMn, and HMFLn, respectively. In a typical application, Ixx81 specifies that these
inputs be used from the “spare” flag register matching the second DAC channel used for commutation.
If the flag register is in a PMAC2-style Servo IC, the input flags for bits 20, 21, and 22, representing W,
V, and U, are CHWn, CHVn, and CHUn, respectively. In a typical application, these inputs are used
from the same flag register addressed by Ixx25 for the main flags.
In this mode, bit 22 of Ixx91 allows for reversal of the sense of the hall-effect sensors. If W (bit 20 of the
register; HMFLn or CHWn) leads V (bit 21; -LIMn or CHVn), and V leads U (bit 22; +LIMn or CHUn)
as the commutation cycle counts up, then bit 22 of Ixx91 should be set to 0. If U leads V and V leads W
as the commutation cycle counts up, then bit 22 of Ixx91 should be set to 1.
In this mode, bits 16 to 21 of Ixx91 together form an offset value from 0 to 63 representing the difference
between PMAC’s commutation cycle zero and the hall-effect sensor zero position, which is defined as the
transition of the V signal when U is low. This offset has units of 1/64 of a commutation cycle, or 5.625 oe.
Typically, one of the transitions will be at PMAC’s commutation zero point, so the desired offset values
will be 0o, 60o, 120o, 180o, 240o, and 300o, approximated by values of 0, 11($0B), 21($15), 32($20),
43($2B), and 53($35).
This operation can handle hall-effect sensors separated by 120oe. The following table gives the Ixx91
settings for bits 16 to 23 for all of the common cases of hall-effect settings as they relate to the PMAC
commutation cycle.
The possible values of Ixx95 and the absolute position feedback devices they reference are summarized in
the following table:
Ixx95 Value Range Absolute Position Source Ixx10 Address Type Format
$000000 - $070000 Acc-8D Opt 7 R/D Converter Multiplexer Port Unsigned
$080000 - $300000 Parallel Data Y-Register Turbo PMAC Memory-I/O Unsigned
$310000 Acc-28 A/D Converter Turbo PMAC Memory-I/O Unsigned
$320000 Acc-49 Sanyo Abs. Encoder Turbo PMAC Memory-I/O Unsigned
$480000 - $700000 Parallel Data X-Register Turbo PMAC Memory-I/O Unsigned
$710000 Acc-8D Opt 9 Yaskawa Abs. Enc. Multiplexer Port Unsigned
$720000 MACRO Station Yaskawa Abs. Enc. MACRO Node Number Unsigned
$730000 MACRO Station R/D Converter MACRO Node Number Unsigned
$740000 MACRO Station Parallel Read MACRO Node Number Unsigned
$800000 - $870000 Acc-8D Opt 7 R/D Converter Multiplexer Port Signed
$880000 - $B00000 Parallel Data Y-Register Turbo PMAC Memory-I/O Signed
$B10000 Acc-28 A/D Converter Turbo PMAC Memory-I/O Signed
$B20000 Acc-49 Sanyo Abs. Encoder Turbo PMAC Memory-I/O Signed
$C80000 - $F00000 Parallel Data X-Register Turbo PMAC Memory-I/O Signed
$F10000 Acc-8D Opt 9 Yaskawa Abs. Enc. Multiplexer Port Signed
$F20000 MACRO Station Yaskawa Abs. Enc. MACRO Node Number Signed
$F30000 MACRO Station R/D Converter MACRO Node Number Signed
$F40000 MACRO Station Parallel Read MACRO Node Number Signed
The following section provides details for each type of position feedback.
R/D Converter: If Ixx95 contains a value from $000000 to $070000, or from $800000 to $870000,
Motor xx will expect its absolute power-on position from an Acc-8D Option 7 R/D converter board.
Ixx10 should contain the address of the board on the multiplexer port, as set by the DIP switches on the
board.
The first hex digit of Ixx95, which can take a value of 0 or 8 in this mode, specifies whether the position
is interpreted as an unsigned value (first digit = 0) or as a signed value (first digit = 8).
The second hex digit of Ixx95, which can take a value from 0 to 7 in this mode, specifies the number of
the individual R/D converter at that multiplexer port address.
The following table shows the Ixx95 values for this mode and the R/D converter each specifies at the
Ixx10 address:
Ixx95 Value for Ixx95 Value for Acc-8D Opt. 7 # of R/D Converter
Unsigned Position Signed Position SW1-1 Setting on Acc-8D Opt. 7
$000000 $800000 CLOSED (0) 1
$010000 $810000 CLOSED (0) 2
$020000 $820000 CLOSED (0) 3
$030000 $830000 CLOSED (0) 4
$040000 $840000 OPEN (1) 1
$050000 $850000 OPEN (1) 2
$060000 $860000 OPEN (1) 3
$070000 $870000 OPEN (1) 4
If Ixx99 is set greater than 0, the next higher numbered R/D converter at the same multiplexer port
address is also read and treated as a geared-down resolver, with Ixx99 specifying the gear ratio. Ixx98 is
also set greater than 0, the following R/D converter at the same multiplexer port address is read and
treated as a third resolver geared down from the second, with Ixx98 specifying that gear ratio.
Parallel Data Read: If Ixx95 contains a value from $080000 to $300000, from $480000 to $700000,
from $880000 to $B00000, or from $C80000 to $F00000, Motor xx will do a parallel data read of the
Turbo PMAC memory or I/O register at the address specified by Ixx10. It expects to find the least
significant bit of the feedback in Bit 0 of this register.
In this mode, bits 16 to 21 specify the number of bits to be read. If the last hex digit of Ixx95 is 0,
consecutive bits will be read from the address specified by Ixx81, with the least significant bit read from
bit 0. If the number of bits is greater than 24, the high bits are read from the register at the next higher-
numbered address. This format is used for registers and I/O devices with 24-bit interfaces.
If the last hex digit of Ixx95 is 4, 5, or 6, data will be read in byte-wide pieces, with the least significant
byte at the address specified in Ixx81, the next byte at one address higher, and so on, up to a possible 6
consecutive addresses. This format is intended for getting parallel data from the Acc-3E 3U-format stack
I/O board or the Acc-14E 3U-format pack (UMAC) I/O board, which have byte-wide interfaces. For this
format, the last hex digit of Ixx95 determines which byte of the 24-bit word is used, according to the
following table:
Ixx95 Last Digit Byte Bits
4 Low 0–7
5 Middle 8 – 15
6 High 16 – 23
In this mode, bits 16 to 21 of Ixx95 specify the number of bits to be read, starting with bit 0 at the
specified address. In this mode, they can take a value from $08 to $30 (8 to 48). If the number of bits is
greater than 24, the high bits are read from the register at the next higher-numbered address.
In this mode, bit 22 of Ixx95 specifies whether a Y-register is to be read, or an X-register. A value of 0 in
this bit specifies a Y-register; a value of 1 specifies an X-register. Almost all common sources of
absolute position information are located in Y-registers, so this digit is usually 0.
In this mode, bit 23 of Ixx95 specifies whether the position is interpreted as an unsigned or a signed
value. If the bit is set to 0, it is interpreted as an unsigned value, if the bit is 1, it is interpreted as a signed
value.
Combining these components, Ixx95 values in this mode can be summarized as:
$08000n - $30000n: Parallel Y-register read, unsigned value, 8 to 48 bits
$48000n - $70000n: Parallel X-register read, unsigned value, 8 to 48 bits
$88000n - $B0000n: Parallel Y-register read, signed value, 8 to 48 bits
$C8000n - $F0000n: Parallel X-register read, signed value, 8 to 48 bits
Example: If Ixx10=$078D00 and Ixx95=$200000, Turbo PMAC would read 32 bits, the low 24 bits
from Y:$078D00, and the high eight bits from the low eight bits of Y:$078D01.
Example: If Ixx10=$078C00 and Ixx95=$100004, Turbo PMAC would read 16 bits, with the low 8 bits
from the low byte of Y:$078C00, and the high eight bits from the low byte of Y:$078C01.
Example: If Ixx10=$079E03 and Ixx95=$120005, Turbo PMAC would read 18 bits, with the low eight
bits from the middle byte of Y:$079E03, and the next 8 bits from the middle byte of Y:$079E04, and the
high two bits from the first 2 bits of the middle byte of Y:$079E05.
Example: If Ixx10=$078000 and Ixx95=$540000, Turbo PMAC would read 20 bits from X:$078000
(timer register for Channel 1). This type of setting is used for MLDT feedback.
Acc-28 A/D Converter Read: If Ixx95 is set to $310000 or $B10000, Motor xx will expect its power-on
position in the upper 16 bits of the Turbo PMAC Y-memory or I/O register specified by Ixx10. This
format is intended for Acc-28 A/D converters.
Bit 23 of Ixx95 specifies whether the position is interpreted as an unsigned or a signed value. If the bit is
set to 0, it is interpreted as an unsigned value, if the bit is 1, it is interpreted as a signed value. Because
Acc-28A produces signed values, Ixx95 should be set to $B10000 when using Acc-28A. Acc-28B
produces unsigned values, so Ixx95 should be set to $310000 when using Acc-28B.
Sanyo Absolute Encoder Read: If Ixx95 is set to $320000 or $B20000, Motor xx will expect its power-
on position from the Acc-49 Sanyo Absolute Encoder converter board at the Turbo PMAC address
specified by Ixx10.
The first hex digit of Ixx95, which can take a value of 3 or B in this mode, specifies whether the position
is interpreted as an unsigned value (first digit = 0) or as a signed value (first digit = 8). Set Ixx95 to
$320000 for unsigned, or to $B20000 for signed.
Yaskawa Absolute Encoder Read: If Ixx95 is set to $710000 or $F10000, Motor xx will expect its
power-on position from the Yaskawa Absolute Encoder converter board at the multiplexer port address
specified by Ixx10.
The first hex digit of Ixx95, which can take a value of 7 or F in this mode, specifies whether the position
is interpreted as an unsigned value (first digit = 0) or as a signed value (first digit = 8). Set Ixx95 to
$710000 for unsigned, or to $F10000 for signed.
In this mode, Ixx99 specifies the number of bits per revolution for a single turn of the Yaskawa absolute
encoder. It must be set greater than 0 to use the multi-turn absolute capability of this encoder.
MACRO Station Yaskawa Absolute Encoder Read: If Ixx95 is set to $720000 or $F20000, Motor xx
will expect its power-on position from a Yaskawa Absolute Encoder through a MACRO Station. In this
mode, Ixx10 specifies the MACRO node number at which the position value will be read by Turbo
PMAC itself. Set-up variable MI11x for the MACRO Station tells the Station how to read the Yaskawa
Encoder converter connected to its own multiplexer port or serial port.
The first hex digit of Ixx95, which can take a value of 7 or F in this mode, specifies whether the position
is interpreted as an unsigned value (first digit = 0) or as a signed value (first digit = 8). Set Ixx95 to
$720000 for unsigned, or to $F20000 for signed.
In this mode, Ixx99 specifies the number of bits per revolution for a single turn of the Yaskawa absolute
encoder. It must be set greater than 0 to use the multi-turn absolute capability of this encoder.
MACRO Station R/D Converter Read: If Ixx95 is set to $730000 or $F30000, Motor xx will expect its
power-on position from an R/D converter through a MACRO Station or compatible device. In this mode,
Ixx10 specifies the MACRO node number at which Turbo PMAC will read the position value itself. Set-
up variable MI11x for the matching node on the MACRO Station tells the Station how to read the R/D
converter connected to its own multiplexer port.
The first hex digit of Ixx95, which can take a value of 7 or F in this mode, specifies whether the position
is interpreted as an unsigned value (first digit = 0) or as a signed value (first digit = 8). Set Ixx95 to
$730000 for unsigned, or to $F30000 for signed.
If Ixx99 is set greater than 0, the next higher numbered R/D converter at the same multiplexer port
address is also read and treated as a geared-down resolver, with Ixx99 specifying the gear ratio. Ixx98 is
also set greater than 0, the following R/D converter at the same multiplexer port address is read and
treated as a third resolver geared down from the second, with Ixx98 specifying that gear ratio.
MACRO Station Parallel Data Read: If Ixx95 is set to $740000 or $F40000, Motor xx will expect its
power-on position from a parallel data source through a MACRO Station or compatible device. In this
mode, Ixx10 specifies the MACRO node number at which Turbo PMAC will read the position value
itself. Set-up variable MI11x for the matching node on the MACRO Station tells the Station how to read
the parallel data source connected to it.
The first hex digit of Ixx95, which can take a value of 7 or F in this mode, specifies whether the position
is interpreted as an unsigned value (first digit = 0) or as a signed value (first digit = 8). Set Ixx95 to
$740000 for unsigned, or to $F40000 for signed.
This parameter is used only during Turbo PMAC’s power-up/reset cycle to establish absolute power-on
servo position. Therefore, the parameter must be set, the value stored in non-volatile flash memory with
the SAVE command, and the card reset before it takes effect.
If there is no geared third resolver on Motor xx, or if absolute power-on position is not desired, Ixx98
should be set to zero. If either Ixx10 (for the primary resolver) or Ixx99 (for the secondary resolver) is set
to zero, Ixx98 is not used.
The third resolver must be connected to the next higher numbered R/D converter at the same multiplexer
address than the second resolver, which must be connected to the next higher numbered converter at the
same multiplexer address than the primary resolver. There can be up to eight R/D converters on two Acc-
8D Option 7 boards at one multiplexer address.
In non-Turbo PMACs, this function is controlled by I-variable I8x.
Example:
Motor 3 has a triple resolver, with each resolver geared down by a ratio of 16:1 from the resolver before
it. The fine resolver is connected to R/D converter 4 at multiplexer address 0 (the first R/D converter on
the second Acc-8D Option 7 at address 0). The medium resolver is connected to R/D converter 5 at this
address, and the coarse resolver is connected to R/D converter 6. The following I-variable values should
be used:
I310=$000100 .. ; The $000100 specifies multiplexer address 0
I395=$040000 .. ; the 4 in the high eight bits of Ixx95
......................... ; specifies R/D converter 4 at this address.
I399=16............ ; Specifies 16:1 ratio between medium and fine
I398=16............ ; Specifies 16:1 ratio between coarse and medium
Ixx99 Motor xx Second-Resolver Gear Ratio
Range: 0 - 4095
Units: Primary resolver turns per second-resolver turn
Default: 0
Ixx99 tells PMAC the gear ratio between the first (fine, or primary) and second (coarse or medium)
resolvers for a double- or triple-resolver setup for Motor xx. It is expressed as the number of turns
(electrical cycles) the first resolver makes in one full turn (electrical cycle) of the second resolver.
This parameter is used only during Turbo PMAC's power-up/reset cycle to establish absolute power-on
servo position. Therefore, the parameter must be set, the value stored in non-volatile flash memory with
the SAVE command, and the card reset before it takes effect.
If there is no geared second resolver on Motor xx, or if absolute power-on position is not desired, Ixx99
should be set to zero. If Ixx10 (for the primary resolver) is set to zero, Ixx99 is not used. In a triple-
resolver system, Ixx99 must be set greater than zero in order for Ixx88 (third-resolver gear ratio) to be
used.
The second resolver must be connected to the next higher numbered R/D converter at the same
multiplexer address than the first resolver. If there is a third resolver, it must be connected to the next
higher numbered converter at the same multiplexer address than the second resolver. There can be up to
eight R/D converters on two Acc-8D Option 7 boards at one multiplexer address.
If Ixx10 is set up for an Acc-8D Option 9 Yaskawa encoder converter, Ixx99 represents the counts per
revolution (including x2 or x4 quadrature decode, if used) of the encoder; effectively it is the “gear ratio”
between the encoder and the revolution counter.
In non-Turbo PMACs, this function is controlled by I-variable I9x.
Example:
Motor 1 has a double resolver with the fine resolver connected to the R/D converter at location 2 on an
Acc-8D Option 7 board set to multiplexer address 4, and the coarse resolver, geared down at a 36:1 ratio
from the fine resolver, connected to the R/D converter at location 3 on the same board. The following I-
variable settings should be used:
I110=$000004 .. ; Value of $0004 specifies multiplexer address 4
I118=$020000 .. ; $02 in high 8 bits of I118
......................... ; specifies R/D at location 2 of this address
I199=36............ ; Specify 36 turns of fine resolver per turn of
......................... ; coarse resolver; R/D must be at location 3
......................... ; of multiplexer address 4
I198=0 ............. ; No third resolver
Supplemental Motor Setup I-Variables
Iyy00 – Iyy49/Iyy50 – Iyy99 Supplemental Motor I-Variables
yy = 33 – 48
Motor Number xx = 2 * (yy - 32) - 1 for Iyy00 – Iyy49 (odd-numbered motors)
Motor Number xx = 2 * (yy - 32) for Iyy50 – Iyy99 (even-numbered motors)
Motor Supplemental Motor Supplemental Motor Supplemental Motor Supplemental
# I-Variables # I-Variables # I-Variables # I-Variables
1 I3300 - I3349 9 I3700 - I3749 17 I4100 - I4149 25 I4500 - I4549
2 I3350 - I3399 10 I3750 - I3799 18 I4150 - I4199 26 I4550 - I4599
3 I3400 - I3449 11 I3800 - I3849 19 I4200 - I4249 27 I4600 - I4649
4 I3450 - I3499 12 I3850 - I3899 20 I4250 - I4299 28 I4650 - I4699
5 I3500 - I3549 13 I3900 - I3949 21 I4300 - I4349 29 I4700 - I4749
6 I3550 - I3599 14 I3950 - I3999 22 I4350 - I4399 30 I4750 - I4799
7 I3600 - I3649 15 I4000 - I4049 23 I4400 - I4449 31 I4800 - I4849
8 I3650 - I3699 16 I4050 - I4099 24 I4450 - I4499 32 I4850 - I4899
Note:
These I-variables are disabled if Iyy00/50 for the motor is set to 0. No value can
be written to them, and if queried, they will report a value of 0.
The following servo control I-variables are used regardless of the setting of Iyy00/50:
Ixx59, Ixx60, Ixx68, Ixx69
Iyy10 – Iyy39/Iyy60 – Iyy89 Motor xx Extended Servo Algorithm Gains
Iyy10 through Iyy39 (for odd-numbered motors), and Iyy60 through Iyy89 (for even-numbered motors)
are the gains for the Extended Servo Algorithm (ESA). The following table lists the function of each
variable; refer to the User Manual for a detailed description and diagram of the algorithm structure.
I-Var. for I-Var. for Gain Range I-Var. for I-Var. for Gain Range
Odd- Even- Name Odd- Even- Name
Numbered Numbered Numbered Numbered
Motors Motors Motors Motors
Iyy10 Iyy60 s0 -1.0Var+1.0 Iyy25 Iyy75 TS -223Var223
Iyy11 Iyy61 s1 -1.0Var+1.0 Iyy26 Iyy76 L1 -1.0Var+1.0
Iyy12 Iyy62 f0 -1.0Var+1.0 Iyy27 Iyy77 L2 -1.0Var+1.0
Iyy13 Iyy63 f1 -1.0Var+1.0 Iyy28 Iyy78 L3 -1.0Var+1.0
Iyy14 Iyy64 h0 -1.0Var+1.0 Iyy29 Iyy79 k0 -1.0Var+1.0
Iyy15 Iyy65 h1 -1.0Var+1.0 Iyy30 Iyy80 k1 -1.0Var+1.0
Iyy16 Iyy66 r1 -1.0Var+1.0 Iyy31 Iyy81 k2 -1.0Var+1.0
Iyy17 Iyy67 r2 -1.0Var+1.0 Iyy32 Iyy82 k3 -1.0Var+1.0
Iyy18 Iyy68 r3 -1.0Var+1.0 Iyy33 Iyy83 KS -223Var223
Iyy19 Iyy69 r4 -1.0Var+1.0 Iyy34 Iyy84 d1 -1.0Var+1.0
Iyy20 Iyy70 t0 -1.0Var+1.0 Iyy35 Iyy85 d2 -1.0Var+1.0
Iyy21 Iyy71 t1 -1.0Var+1.0 Iyy36 Iyy86 g0 -1.0Var+1.0
Iyy22 Iyy72 t2 -1.0Var+1.0 Iyy37 Iyy87 g1 -1.0Var+1.0
Iyy23 Iyy73 t3 -1.0Var+1.0 Iyy38 Iyy88 g2 -1.0Var+1.0
Iyy24 Iyy74 t4 -1.0Var+1.0 Iyy39 Iyy89 GS -223Var223
Usually, the ESA gains that these I-variables represent are set using the Auto-tuning function of the Servo
Evaluation Package (SEP).
Note:
These I-variables are disabled if Iyy00/50 for the motor is set to 0. No value can
be written to them, and if queried, they will report a value of 0.
Note:
In firmware versions older than 1.936, bits 20 through 23 of I4900 reported the
presence of the four possible MACRO ICs. With versions 1.936 and newer, there
is support for more than four MACRO ICs, and their presence is reported in I4902.
I4901 is a 20-bit value with each individual bit representing each possible Servo that could be present in
the system. The table shown in the I4900 description, above, lists which IC is represented by each bit.
A bit of I4901 is set to 0 if a Type 0 PMAC-style DSPGATE Servo IC is found at the appropriate address
slot, or if no Servo IC is found there. The bit is set to 1 if a Type 1 PMAC2-style DSPGATE1 Servo IC
is found there.
I4902 MACRO ICs Present
Range: $000000 – $0FFFF
Units: none (individual bits)
Default: --
I4902 is a read-only status I-variable that reports which MACRO ICs are present in a Turbo PMAC
system. It is provided for user setup and diagnostic purposes only. On power-up/reset, Turbo PMAC
queries for the presence of each possible MACRO IC automatically and reports what it has found in
I4902.
I4902 is a 16-bit value with each individual bit representing each possible MACRO IC that could be
present in the system. (Only a UMAC system can have more than four MACRO ICs present.) The bit is
set to 0 if the IC is not present; it is set to 1 if the IC is present.
The following table shows the MACRO IC each bit of I4902 represents:
I4902 Bit Base Ident I4902 Bit Base Ident
Bit # Value Address I-var Bit # Value Address I-var
0 $1 $078400 I4926 8 $100 $078600 I4934
1 $2 $079400 I4927 9 $200 $079600 I4935
2 $4 $07A400 I4928 10 $400 $07A600 I4936
3 $8 $07B400 I4929 11 $800 $07B600 I4937
4 $10 $078500 I4930 12 $1000 $078700 I4938
5 $20 $079500 I4931 13 $2000 $079700 I4939
6 $40 $07A500 I4932 14 $4000 $07A700 I4940
7 $80 $07B500 I4933 15 $8000 $07B700 I4941
Which of these ICs is assigned as MACRO IC 0, 1, 2, and 3 for firmware support issues is dependent on
the settings of I20, I21, I22, and I23, respectively.
Note:
In firmware versions older than 1.936, bits 20 through 23 of I4900 reported the
presence of the four possible MACRO ICs. With versions 1.936 and newer, there
is support for more than four MACRO ICs, and their presence is reported in I4902.
In addition, I4904 contains the status of the eight locking bits that an application can use with the LOCK
and UNLOCK commands to make sure that tasks of different priorities do not overwrite each other. The
following table shows how the eight locking bits are stored. Each bit is a 0 if unlocked; it is a 1 if locked.
I4904 Bit # Bit Value Locking Bit #
4 $10 0
5 $20 1
6 $40 2
7 $80 3
8 $100 4
9 $200 5
10 $400 6
11 $800 7
The following table shows what each part of I4909 returns and what each part means.
I4909 Bit #s Bit Values Meaning
0 – 7 (I39=0) $FF (I39=0) =1: Vendor is Delta Tau
0 – 7 (I39=1) $FF (I39=1)
8 (I39=0) $100 (I39=0) =0: Standard (128k x 24) user data memory (Opt 5x0,2)
0 (I39=2) $1 (I39=2) =1: Extended (512k x 24) user data memory (Opt 5x1,3)
9 (I39=0) $200 (I39=0) =0: Standard (128k x 24) program memory (Opt 5x0,1)
1 (I39=2) $2 (I39=2) =1: Extended (512k x 24) program memory (Opt 5x2,3)
10,11 (I39=0) $C00 (I39=0) =0: No dual-ported RAM
2,3 (I39=2) $C (I39=2) =1: 8k x 16 dual-ported RAM (Opt 2x)
=3: 32k x 16 dual-ported RAM (Opt 2x)
12,13 (I39=0) $3000 (I39=0) =0: No battery-backed RAM
4,5 (I39=2) $30 (I39=2) =1: 32k x 24 battery-backed RAM (Opt 16A)
=3: 128k x 24 battery-backed RAM (Opt 16B)
14,15,16 (I39=0) $1C000 (I39=0) =0: Unknown flash IC (cannot save)
6,7,8 (I39=2) $1C0 (I39=2) =1: Intel 28F004S3 512k x 8 flash IC
=2: Intel 28F008S3 1M x 8 flash IC (Opt 5x0)
=3: Intel 28F016S3 2M x 8 flash IC (Opt 5x1,2)
=4: Intel 28F160S3 2M x 8 flash IC (Opt 5x1,2)
=5: Intel 28F320S3 4M x 8 flash IC (Opt 5x3)
=6: Intel 28F320J5 4M x 8 flash IC (Opt 5x3)
=7: Intel 28F640J5 8M x 8 flash IC
17 (I39=0) $20000 (I39=0) =0: Aux. RS232 not present or not active
9 (I39=2) $200 (I39=2) =1: Aux. RS232 present (Opt 9T) and active (I53>0)
18 – 21 (I39=0) $3C0000 (I39=0) =0: DSP56303 CPU
0 – 3 (I39=3) $F (I39=3) =1: DSP56309 CPU
>1: (Reserved)
22 – 35 (I39=0) $FFFC00000 (I39=0) (Last 4 digits of card part number)
0 – 13 (I39=4) $3FFF (I39=4)
I4910 to I4925 have multiple fields of information, which can be reported individually or in groups,
depending on the setting of I39. The following table shows what each field reports.
Information Reported when: Bits when I39=0 Bits when I39>0
Vendor ID I39 = 0 or 1 0–7 0–7
Options I39 = 0 or 2 8 – 17 0–9
Revision # I39 = 0 or 3 18 – 21 0–3
Card ID I39 = 0 or 4 22 – 35 0 – 13
Base Address I39 = 5 -- 0 - 18
The Vendor ID field is an 8-bit value that reports the manufacturer of the board. Delta Tau boards
report a value of 1 in this field.
Typically, the Options field is a 10-bit field that is used as a set of individual bits to report which
options are present on the board. The meaning of each bit is board-dependent.
The Revision Number field is a 4-bit value that represents the design revision (0 to 15) of the board.
For Delta Tau boards, this value matches the x in the –10x part number suffix for the board.
The Card ID field is a 14-bit value that represents the part number of the board. For Delta Tau
boards, this value matches the xxxx in the 60xxxx (decimal) main part number for the board.
The Base Address field is a 19-bit value that represents the starting address of the board in the Turbo
PMAC’s address space.
The Base Address field is a 19-bit value that represents the starting address of the board in the Turbo
PMAC’s address space.
I4942 – I4949 DPRAM IC Card Identification
Range: $000000000 – $FFFFFFFFF
Units: none (individual bits)
Default: --
I4942 – I4949 are read-only status I-variables that report configuration information for UMAC accessory
boards that contain DPRAM ICs, such as the Acc-54E. The following table shows which variable
corresponds to which card:
Ident I-var I4904 Board DIP Switch Board Base Board Ident.
Bit # 4,3,2,1 Setting1 Address Info Address2
I4942 16 0000 (0) or 0001 (1) $06C000 $078F20
I4943 17 0010 (2) or 0011 (3) $074000 $078F24
I4944 18 0100 (4) or 0101 (5) $06D000 $079F20
I4945 19 0110 (6) or 0011 (7) $075000 $079F24
I4946 20 1000 (8) or 1001 (9) $06E000 $07AF20
I4947 21 1010 (10) or 1011 (11) $076000 $07AF24
I4948 22 1100 (12) or 1101 (13) $06F000 $07BF20
I4949 23 1110 (14) or 1011 (15) $077000 $07BF24
Notes:
1. Board DIP-switches SW1-1 to SW1-4 are currently used to set the addresses of the boards on the
UBUS backplane. A 0 is ON (Closed); a 1 is OFF (Open). The E1 jumper on the back of the Acc-
Ux UBUS backplane board must be ON to use the DIP-switch addressing. SW1-5 and SW1-6 must
be ON (Closed).
2. For diagnostic purposes only. The four Y registers starting at this address contain the information
used to assemble this I-variable.
I4942 to I4949 have multiple fields of information, which can be reported individually or in groups,
depending on the setting of I39. The following table shows what each field reports.
Information Reported when: Bits when Bits when
I39=0 I39>0
Vendor ID I39 = 0 or 1 0–7 0–7
Options I39 = 0 or 2 8 – 17 0–9
Revision # I39 = 0 or 3 18 – 21 0–3
Card ID I39 = 0 or 4 22 – 35 0 – 13
Base Address I39 = 5 -- 0 - 18
The Vendor ID field is an 8-bit value that reports the manufacturer of the board. Delta Tau boards
report a value of 1 in this field.
The Options field is a 10-bit field that is typically used as a set of individual bits to report which
options are present on the board. The meaning of each bit is board-dependent.
The Revision Number field is a 4-bit value that represents the design revision (0 to 15) of the board.
For Delta Tau boards, this value matches the x in the –10x part number suffix for the board.
The Card ID field is a 14-bit value that represents the part number of the board. For Delta Tau
boards, this value matches the xxxx in the 60xxxx (decimal) main part number for the board.
The Base Address field is a 19-bit value that represents the starting address of the board in the Turbo
PMAC’s address space.
The Card ID field is a 14-bit value that represents the part number of the board. For Delta Tau
boards, this value matches the xxxx in the 60xxxx (decimal) main part number for the board.
The Base Address field is a 19-bit value that represents the starting address of the board in the Turbo
PMAC’s address space.
Data Gathering I-Variables
I5000 Data Gathering Buffer Location and Mode
Range: 0-3
Units: none
Default: 0
I5000 controls where the data gathering buffer will be located when it is defined, and whether it will wrap
around when it is filled. It can take the following values:
0: Locate buffer in regular RAM. Do not permit wrap-around (stop gathering when end of buffer is
reached). This setting must be used for Turbo PMAC Executive program data gathering and tuning
routines.
1: Locate buffer in regular RAM. Permit wrap-around upon reaching end of buffer.
Note:
Wrap-around feature is not supported by Turbo PMAC Executive program data
gathering and tuning routines.
2: Locate buffer in dual-ported RAM (Turbo PMAC Option 2 required). Do not permit wrap-around.
3: Locate buffer in dual-ported RAM (Turbo PMAC Option 2 required). Permit wrap-around upon
reaching end of buffer (usual mode for dual-ported RAM).
Note:
Normally, this parameter is set automatically by the PMAC Executive Program’s
gathering and tuning routines.
Note:
Normally, this parameter is set automatically by the PMAC Executive Program’s
gathering and tuning routines.
The following table shows the relationship between bits of I5051 and the data gathering source address I-
variables:
Bit # Value I-Variable Enabled Bit # Value I-Variable Enabled
0 $1 I5025 12 $1000 I5037
1 $2 I5026 13 $2000 I5038
2 $4 I5027 14 $4000 I5039
3 $8 I5028 15 $8000 I5040
4 $10 I5029 16 $10000 I5041
5 $20 I5030 17 $20000 I5042
6 $40 I5031 18 $40000 I5043
7 $80 I5032 19 $80000 I5044
8 $100 I5033 20 $100000 I5045
9 $200 I5034 21 $200000 I5046
10 $400 I5035 22 $400000 I5047
11 $800 I5036 23 $800000 I5048
Note:
Normally, this parameter is set automatically by the PMAC Executive Program’s
gathering and tuning routines.
Each variable I5061 – I5076 is matched with the I-variable numbered 20 higher (e.g. I5081 for I5061) to
specify which channel of the muxed A/D-converter is to be used, and how that channel is to be read. Up
to 8 of these I-variable pairs must be used to read all 8 channels of a muxed A/D converter – the eight
variables in the I5061 – I5076 range will all contain the same address.
The results of the A/D tables are placed in registers at addresses Y:$003400 to Y:$00341F, using bits 12
to 23 of these registers. The value of the A/D converter found in the low 12 bits of the source register is
placed in the register with the even-numbered address; the value of the A/D converter found in the high
12 bits of the source register is placed in the register with the odd-numbered address. The following table
shows the matching between the A/D pointer I-variables and the addresses of the result registers.
I-Variable Result Address Result Address I-Variable Result Address Result Address
for Low ADC for High ADC for Low ADC for High ADC
I5061 Y:$003400 Y:$003401 I5069 Y:$003410 Y:$003411
I5062 Y:$003402 Y:$003403 I5070 Y:$003412 Y:$003413
I5063 Y:$003404 Y:$003405 I5071 Y:$003414 Y:$003415
I5064 Y:$003406 Y:$003407 I5072 Y:$003416 Y:$003417
I5065 Y:$003408 Y:$003409 I5073 Y:$003418 Y:$003419
I5066 Y:$00340A Y:$00340B I5074 Y:$00341A Y:$00341B
I5067 Y:$00340C Y:$00340D I5075 Y:$00341C Y:$00341D
I5068 Y:$00340E Y:$00340F I5076 Y:$00341E Y:$00341F
I5061 – I5076 are used at power-on/reset only, so to make a change in the A/D de-multiplexing sources,
change the values of I5061 – I5076, store these new values to non-volatile flash memory with the SAVE
command, and reset the card with the $$$ command.
I5080 A/D Ring Convert Enable
Range: 0-1
Units: none
Default: 1
I5080 controls whether the A/D-converter demultiplexing algorithm specified by I5060 – I5076 and
I5081 – I5096 is enabled or not. If I5080 is set to 1, the algorithm is enabled; if I5080 is set to 0, the
algorithm is disabled.
If the saved value of I5060 is greater than 0, specifying that some demultiplexing is to be done, then
I5080 is automatically set to 1 on power-up/reset, so the algorithms are automatically running. By
subsequently setting I5080 to 0, the user can suspend the execution of these algorithms, to be resumed by
setting I5080 back to 1. If the saved value of I5060 is 0, then I5080 is automatically set to 0 on power-
up/reset.
I5081-I5096 A/D Ring Convert Codes
Range: $000000 - $00F00F
Units: None
Default: $000000
I5081 through I5096 contain the convert codes written to the multiplexed A/D converters that are read in
the A/D ring table, as enabled by I5060. The convert codes control which of the multiplexed ADCs at the
address is to be read, and the range of the analog input for that ADC. The ADCs can be on-board the
Turbo PMAC with Option 12 and 12A, or off-board with an Acc-36P/V. The Turbo PMAC address of
the ADC to be read is set by the I-variable number 20 less (e.g. I5061 determines the address of the ADC
whose convert code is set by I5081). The number of ADC converters in the ring is determined by I5060.
I5081-I5096 are 24-bit values, represented by 6 hexadecimal digits. Legitimate values are of the format
$00m00n, where m and n can take any hex value from 0 through F.
For the on-board Option 12 & 12A ADCs on a Turbo PMAC2, the m value determines which of the
inputs ANAI08 to ANAI15 that come with Option 12A is to be read, and how it is to be converted,
according to the following formulas:
m ANAI #8 ; 0 to +5V unipolar input
m ANAI # ; -2.5V to +2.5V bipolar input
For the on-board Option 12 & 12A ADCs on a Turbo PMAC2, the n value determines which of the inputs
ANAI00 to ANAI07 that come with Option 12A is to be read, and how it is to be converted, according to
the following formulas:
n ANAI # ; 0V to +5V unipolar input
n ANAI #8 ; -2.5V to +2.5V bipolar input
For example, to read ANAI02 from Option 12 and ANAI10 from Option 12A, both as +/-2.5V inputs,
into the first slot in the ring, m would be set to A (10) and n would be set to A (10), so I5081 would be set
to $00A00A.
For the off-board Acc-36P/V ADCs, the m value is always 0, and the n value determines which pair of
ADCs is to be read, and how they are to be converted, according to the following formulas:
n ADC#1, ADC# 9 ; 0 to +10V (between + and -) unipolar inputs
n ADC#7 , ADC#1 ; -5V to +5V (between + and -) bipolar inputs
For example, to read ADC3 and ADC11 of an Acc-36 as 0-10V inputs into the second slot in the ring, n
would be set to 2, so I5082 would be set to $000002.
I5081 – I5096 are actually used at power-on/reset only, so to make a change in the A/D de-multiplexing
codes, change the values of I5081 – I5096, store these new values to non-volatile flash memory with the
SAVE command, and reset the card with the $$$ command.
Coordinate System I-Variables
I-Variables in the I5100s through the I6600s control the setup of the 16 possible coordinate systems on a
Turbo PMAC, Coordinate System 1 through Coordinate System 16. Each group of 100 I-variables is
reserved for a specific coordinate system: the I5100s for C.S. 1, the I5200s for C.S. 2, and so on, to the
I6600s for C.S. 16. The following table lists the I-variables used for each coordinate system:
C.S. # I-Variables C.S. # I-Variables C.S. # I-Variables C.S. # I-Variables
1 I5100-5199 5 I5500-5599 9 I5900-5999 13 I6300-6399
2 I5200-5299 6 I5600-5699 10 I6000-6099 14 I6400-6499
3 I5300-5399 7 I5700-5799 11 I6100-6199 15 I6500-6599
4 I5400-5499 8 I5800-5899 12 I6200-6299 16 I6600-6699
In the generic description of these I-variables, the thousands digit is represented by the letter s, and the
hundreds digit by the letter x; for example, Isx11. s and x can take the following values:
s is equal to 5 for Coordinate Systems 1 – 9;
s is equal to 6 for Coordinate Systems 10 – 16;
x is equal to the coordinate system number for Coordinate Systems 1 – 9;
x is equal to the (coordinate system number minus 10) for Coordinate Systems 10 – 16.
The descriptions of the variables refer to “Coordinate System x generically, even though the coordinate
system number is equal to (x + 10) for Coordinate Systems 10 – 16.
To calculate the value of Isx15 required for a given override value, the following equation can be used:
Isx15 = [Override(%) / 100%] – 1.0
The effect of override control with Isx15 is similar to that of override control with Turbo PMAC’s time-
base control (%) feature, but there are several important differences.
First, because the segmentation override control occurs before the lookahead buffer, the acceleration
control of the lookahead buffer is independent of the segmentation override value. If the programmed
acceleration times are kept small, acceleration rates are essentially unaffected by the segmentation
override value. By contrast, the time-base control occurs after the lookahead acceleration control, so
override control with the time-base feature will always affect acceleration as well as velocity.
Second, because the trajectories calculated with the segmentation override are (typically) passed through
the lookahead buffer, changes in the segmentation override value are delayed in execution by the length
of the lookahead buffer. Changes in override through time-base control are instantaneous.
Third, time-base control can be used to provide complete synchronization to a master encoder, but
segmentation override cannot.
The user may write to Isx15 at any time, and it will immediately affect segmentation calculations. As
noted above, the effect on actual motion is delayed by the length of the lookahead buffer. The rate of
change in the active override value is limited by the Isx16 override slew rate parameter. Global variable
I12 should be set to 1 to enable “time splining” in lookahead for smooth transitions, and whatever
algorithm is setting Isx15 should ensure that no instantaneous change in resulting velocity of greater than
2-to-1 magnitude results.
If the user attempts to write a value greater than 0.9999999 to Isx15, it will saturate at 0.9999999. If the
user attempts to write a value less than -1.0 to Isx15, it will saturate at -1.0.
The value of Isx15 at power-up/reset is always 0.0, representing 100% override. The user cannot save the
present value of Isx15 to non-volatile flash memory.
Isx16 Coordinate System ‘x’ Segmentation Override Slew
Range: 0 – 0.9999999
Units: Change in Isx15 per segment
Default: 0.0
Isx16 controls the rate of change of the segmentation override value commanded by Isx15 for Coordinate
System ‘x’. When the user changes the Isx15 command value, Turbo PMAC will change the actual
override value by the magnitude of Isx16 each motion segment until the new value of Isx15 is reached.
When used with the special lookahead buffer active, the user should set Isx15 so that there cannot be an
instantaneous change in segment velocity of greater than 2-to-1 magnitude (of non-zero velocities)
between adjacent segments, before lookahead. This will permit the “time-spline” algorithm in lookahead
enabled with I12 = 1 to generate smooth acceleration trajectories.
If Isx16 is set to 0.0 when Isx15 is changed, there is no slew rate control in the segmentation override, and
override will immediately change to the new value of Isx15 in the next segment calculated.
Example:
For a change in override of 100% (e.g. Isx15 changing from 0.0 to -1.0) in 1.0 seconds with a 5
millisecond segmentation time (Isx13 = 5), we would want the effective value of the override parameter
to change by 0.005 each segment, so Isx16 should be set to 0.005.
Note:
The use of DWELL, WHILE({condition})WAIT, and a violation of the double-
jump-back rule momentarily switches PMAC out of lookahead mode. Therefore,
these constructs should not be used in programs and sub-programs when Isx21 will
be used to control their lookahead state.
Note:
In preliminary versions of the Turbo PMAC firmware, Isx21 served a different
function. That variable value is now a constant value (3) set by the firmware.
is used to compute the starting axis positions on an R (run), S (step), or PMATCH command. The inverse-
kinematic program is used to convert programmed axis positions to motor positions each programmed
move or move segment for each motor defined as an inverse-kinematic axis (#xx->I). Motors in the
coordinate system not defined as inverse-kinematic axes still use axis-definition equations to convert
programmed axis positions to motor positions.
Isx53 Coordinate System x Step Mode Control
Range: 0-1
Units: none
Default: 0
Isx53 controls the action of a Step s command in Coordinate System x. At the default Isx53 value of 0, a
Step command causes program execution through the next move, DELAY, or DWELL command in the
motion program, even if this takes multiple program lines.
When Isx53 is set to 1, a Step command causes execution of only a single program line, even if there is
no move, DELAY, or DWELL command on that line. If there is more than one DWELL or DELAY
command, a single Step command will only execute one of the DWELL or DELAY commands.
Regardless of the setting of Isx53, if program execution on a Step command encounters a BLOCKSTART
statement in the program, execution will continue until a BLOCKSTOP statement is encountered.
On non-Turbo PMACs, this function is controlled by global I-variable I53.
Isx78 Coordinate System ‘x’ Maximum Circle Acceleration
Range: Non-negative floating-point
Units: (user position units) / (Isx90 feedrate time units) 2
Default: 0 (disabled)
Isx78, if set to a positive value, specifies the maximum centripetal acceleration that Turbo PMAC will
permit for a feedrate-specified (F) CIRCLE-mode move in Coordinate System ‘x’. If the move as
programmed would yield a higher centripetal acceleration, Turbo PMAC will automatically lower the
programmed speed for the move so that the Isx78 limit is not exceeded. The centripetal acceleration is
expressed as:
V2
A
R
This limitation is done at the initial move calculation time, so it is not required to use the special
lookahead buffer in conjunction with Isx78. It still may be desirable to use the special lookahead buffer,
especially to manage the tangential acceleration into and out of a reduced-speed arc move.
The most important difference between limiting centripetal acceleration with Isx78 and limiting it with
the individual motor Ixx17 acceleration limits has to do with the exact path generated. Turbo PMAC’s
circular interpolation algorithms introduce a radial error term that can be described by:
V 2T 2
E
6R
where V is the speed along the arc determined by the motion program (possibly limited by Isx78), T is the
Isx13 segmentation time, and R is the radius of the arc. If Isx78 is used to limit the speed of the arc, this
error will be reduced. However, if the special lookahead is used to limit the speed, the error will be as
large as if the arc move were run at full speed.
Isx78 is expressed in the user length units for the linear axes (usually millimeters or inches) divided by
the square of the user “feedrate time units” set by Isx90 for the coordinate system (usually seconds or
minutes).
Example 1:
You want to limit the centripetal acceleration to 1.0g with Isx78. Your length units are millimeters, and
your time units are seconds. Isx78 can be calculated as follows:
m
9.8
Isx78 1.0 g * s 2 * 1000 mm 9800 mm
2
g m s
Example 2:
You want to limit your circular interpolation calculation errors to 0.001 inches. Your length units are
inches, your time units are minutes, and your Isx13 segmentation time is 10 milliseconds. Isx78 can be
calculated as follows:
V 2 6 E 6 * 0.001in 60 2 s 2 in
Isx 78 2 * 216000 2
min
2 2 2
R T 0.01 s min
Example 3:
Your system is capable of 10 m/s2 acceleration (about 1g). Your length units are millimeters, your time
units are minutes, and your Isx13 segmentation time is 2 milliseconds. Isx78 can be calculated as
follows:
m 1000 mm 3600 s 2 mm
Isx 78 10 * * 36,000,000 2
min
2 2
s m min
At this setting, your maximum circular interpolation calculation errors can be computed as:
V 2T 2 T 2 36,000,000 mm min 2
E Isx78 * * 0.002 2 2
s * 0.0067 mm
6R 6 6 min 2 60 2 s 2
If Isx79 is set to 1, all motors involved in the multi-axis move will be commanded to move at their
specified speed. This means that motors with lower distance/speed ratios will finish sooner than those
with higher ratios, and the path in a Cartesian system will not be linear in the general case.
In both cases, each motor involved in the multi-axis move will use its own acceleration parameters Ixx19
– Ixx21 to calculate its acceleration and deceleration profile.
Isx81 Coordinate System ‘x’ Blend Disable In-Position Time-Out
Range: 0 .. 8,388,607
Units: real-time interrupt periods
Default: 0 (disabled)
Isx81, if set to a positive value, specifies that when blending is disabled between programmed moves,
Turbo PMAC will determine that all axes in the coordinate system will be “in-position” before starting
execution of the next move in the motion program. In this case, the value of Isx81 specifies the “time-
out” value for the in-position check, expressed in real-time interrupt periods (I8+1 servo cycles). If all
axes in the coordinate system are not in-position within this time from the end of the incoming
commanded move, the program will be stopped with a run-time error.
If Isx81 is set to 0, Turbo PMAC merely brings the commanded trajectory to a momentary stop before
starting the next move in the cases where blending is disabled; it does not verify that any of the actual
positions have reached this point. (This setting is fully compatible with firmware versions from before
Isx81 was implemented.)
The in-position check as specified by Isx81 is performed after programmed moves that are never blended
(RAPID-mode moves, programmed homing-search moves), or after moves that can be blended, but for
which blending has been disabled by the clearing of the coordinate system “continuous motion request”
status/control bit (directly or from Isx92), or because the corner is sharper than the angle specified by
Isx83.
The in-position check enabled by Isx81 is the “background” check function that uses the Ixx28 in-
position band for each motor, and the Ixx88 number of scans for each motor. When all axes in the
coordinate system have been verified to be “in position”, the coordinate-system “in-position” status bit is
set. After the in-position check, a dwell of the time specified by Isx82 is inserted before execution of the
next programmed move is started.
Isx82 Coordinate System ‘x’ Blend Disable Dwell Time
Range: 0 .. 8,388,607
Units: real-time interrupt periods
Default: 0
Isx82 specifies the dwell time that is automatically inserted between programmed moves when blending
is disabled. This dwell time is inserted after programmed moves that are never blended (RAPID-mode
moves, programmed homing-search moves), or after moves that can be blended, but for which blending
has been disabled by the clearing of the coordinate system “continuous motion request” status/control bit
(directly or from Isx92), or because the corner is sharper than the angles specified by Isx83 and Isx85. (If
the angle is sharper than that specified by Isx83 but not sharper than that specified by Isx85, blending will
be disabled at the corner, but no dwell will be added.) The units of this dwell are in real-time interrupt
periods (I8+1 servo cycles), not milliseconds as in a directly programmed dwell.
If Isx81 is 0, this dwell time is inserted immediately after the end of commanded execution of the
previous move. If Isx81 is greater than 0, this dwell time is inserted after all axes in the coordinate
system have been verified to be “in position”.
During this automatically inserted dwell time (if greater than 0), a coordinate-system “dwell-in-progress”
status bit (Y:$002x40 bit 5, distinct from the motor “dwell-in-progress” status bits from a directly
programmed dwell) will be set.
Example:
If it is desired that motion in Coordinate System 1 be stopped if the change in directed angle is greater
than 30o (included angle less than 150o), then I5183 should be set to 0.866, because cos
= cos 30o = 0.866.
Isx84 Coordinate System ‘x’ Outside Corner Stop Point Control
Range: 0 .. 1
Units: none
Default: 0
Isx84 controls where the programmed movement stops when blending is disabled due to a corner sharper
than the Isx83 threshold on an outside corner in 2D cutter-radius compensation with an added arc at the
corner. If Isx84 is 0, the programmed movement will stop at the end of the added arc; if Isx84 is 1, the
programmed movement will stop at the beginning of the added arc.
If blending is disabled due to single-step operation (S), program termination (Q or /), or continuous-
motion-request bit cleared (usually from Isx92=1), programmed movement will always stop at the end of
the added arc, regardless of the setting of Isx92=1.
Isx85 Coordinate System ‘x’ Corner Dwell Break Point
Range: -1.0 .. 0.9999 (floating-point)
Units: cosine
Default: 0.0 (disabled)
Isx85, if set to a non-zero value, controls the threshold in Coordinate System ‘x’ between corner angles
for which LINEAR and CIRCLE-mode moves are made without an automatically intervening dwell, and
those for which a dwell of Isx82 real-time-interrupt periods is automatically added. Isx85 is only used if
the “continuous motion request” (CMR) coordinate-system status/control bit is set to 1 permit blending.
(This can be set by Isx92=0 at the beginning of a motion program, or can be set directly afterwards.) If
the CMR bit is 0 (usually from Isx92=1), no blending occurs between any moves, and Isx85 is not used.
The corner angle is only evaluated against Isx85 if the blending at the corner has been disabled due to the
action of Isx83. This means that Isx85 must be set to a value less than Isx83 if it is to have any effect.
If Isx85 is set to 0.0, no dwell is ever automatically added. (If a threshold corner angle of 90 o is desired –
for which the Isx85 would be 0.0 – Isx85 should be set to a value that is not exactly 0.0, for example to
0.00001).
Isx85 is expressed as the cosine of the change in directed angle between the incoming and outgoing
moves. (The change in directed angle is equal to 180o minus the included angle of the corner.) As such,
it can take a value between -1.0 and +1.0. If the two moves have the same directed angle at the move
boundary (i.e. they are moving in the same direction), the change in directed angle is 0, and the cosine is
1.0. As the change in directed angle increases, the corner gets sharper, and the cosine of the change in
directed angle decreases. For a total reversal, the change in directed angle is 180 o, and the cosine is -1.0.
The change in directed angle is evaluated in the plane defined by the NORMAL command (default is the
XY-plane); if the corner also involves axis movement perpendicular to this plane, it is the projection of
movement into this plane that matters.
If the cosine of the change in directed angle at a corner is less than Isx85 (a large change in directed
angle; a sharp corner), Turbo PMAC will automatically add a dwell of Isx82 real-time-interrupt periods
before the outgoing move is started. From the time the incoming commanded move begins, through any
in-position settling and added dwell, until the commanded outgoing move starts, the coordinate-system
status bit “sharp corner stop” (Y:$002x40 bit 6) will be set.
If the cosine of the change in directed angle at a corner is greater than Isx85 (a small change in directed
angle; a gradual corner), Turbo PMAC will not automatically add a dwell.
The operation of Isx85 is independent of the operation of the similar function of Isx99, which controls for
outside corners in 2D cutter-radius compensation whether an arc move will be added based on the change
in directed angle. Isx85 works regardless of whether cutter-radius compensation is active or not, or
whether the corner is an inside or outside corner when cutter-radius compensation is active. If this is an
outside-compensated corner with an added arc, the corner angle is based on the moves without the added
arc (i.e. the uncompensated moves).
Example
If it is desired that motion in Coordinate System 1 be stopped if the change in directed angle is greater
than 45o (included angle less than 135 o), then I5185 should be set to 0.707, because cos
= cos 45o = 0.707.
Isx86 Coordinate System x Alternate Feedrate
Range: non-negative floating point
Units: (user position units) / (Isx90 feedrate time units)
Default: 0.0
Isx86 can control the speed of motion for a feedrate-specified move when the motion of non-feedrate axes
is predominant. It is only used if the coordinate system is in segmentation mode (i.e. Isx13 > 0).
Feedrate, or vector-feedrate axes are those specified by the FRAX command; X, Y, and Z are the feedrate
axes by default.
If Isx86 is greater than 0, PMAC compares the move time for the vector feedrate axes, computed as the
vector distance of the feedrate axes divided by the specified feedrate (the F value in the program or Ix89),
to the move time for the non-feedrate axes, computed as the longest distance for these axes divided by
Isx86. It then uses the longer of these two times as the move time for all axes, feedrate and non-feedrate.
If Isx86 is 0, and PMAC sees a feedrate-specified move in which the vector distance is zero (i.e. no
motion of the vector feedrate axes), PMAC computes the move time as the longest distance of the non-
feedrate axes on the line divided by the program feedrate.
Isx86 has two main uses. First, it automatically controls the motion of non-feedrate axes when they are
commanded alone on a line in feedrate mode. Typically, these are rotary axes in a combined linear/rotary
system where only the linear axes are vector feedrate axes.
Second, it permits a fast dry-run mode in which the programmed feedrates are ignored. If no axes in the
coordinate system are vector feedrate axes (implemented with the NOFRAX command), then Isx86 will be
used for all moves, regardless of the F values in the program.
Example:
I5113=10 ; 10 ms segmentation period
I5190=1000 ; Speeds are specified as per-second
I5186=5 ; Alternate feedrate of 5 user units per second
INC ; Moves specified by distance
X20 F10 C1 ; Move time = 20 units / 10 (units/sec) = 2 sec
X10 C30 ; Move time = 30 units / 5 (units/sec) = 6 sec
C20 ; Move time = 20 units / 5 (units/sec) = 4 sec
See Also:
I-variables Isx89, Isx98, Isx13
If Isx88 is greater than zero, the acceleration will start at zero and linearly increase through Isx88 time,
then stay constant (for time TC) until Isx87-Isx88 time, and linearly decrease to zero at Isx87 time (that is
Isx87=2*Isx88 - TC).
If Isx88 is equal to Isx87/2, the entire acceleration will be spec in S-curve form (Isx88 values greater than
Isx87/2 override the Isx87 value; total acceleration time will be 2*Isx88).
Note:
The acceleration time will be extended automatically when any motor in the
coordinate system is asked to exceed its maximum acceleration rate (Ixx17) for a
programmed LINEAR-mode move with Isx13=0 (no move segmentation).
When polled, Isx88 will report the value from the most recently executed TS command in that coordinate
system.
Isx89 Coordinate System x Default Program Feedrate/Move Time
Range: positive floating point
Units: (user position units) / (Isx90 feedrate time units) or msec
Default: 1000.0
Isx89 sets the default feedrate (commanded speed) for programmed LINEAR and CIRCLE mode moves
in coordinate system x. The first use of an F or TM statement in a motion program overrides this value.
The velocity units are determined by the position and time units, as defined by axis definition statements
and Isx89. After power-up/reset, the coordinate system is in feedrate mode, not move-time mode.
Note:
Do not rely on this parameter but declare the feedrate in the program. This will
keep the move parameters with the move commands, lessening the chances of
future errors, and making debugging easier.
When polled, Isx89 will report the value from the most recently executed F or TM command in that
coordinate system.
Isx90 Coordinate System x Feedrate Time Units
Range: positive floating point
Units: msec
Default: 1000.0
Isx90 defines the time units used in commanded velocities (feedrates) in motion programs executed by
Coordinate System x. Velocity units are comprised of length or angle units divided by time units. The
length/angle units are determined in the axis definition statements for the coordinate system.
Isx90 sets the time units. Isx90 itself has units of milliseconds, so if Isx90 is 60,000, the time units are
60,000 milliseconds, or minutes. The default value of Ix90 is 1000 msec, specifying velocity time units
of seconds.
This affects two types of motion program values: F values (feedrate) for LINEAR- and CIRCLE-mode
moves; and the velocities in the actual move commands for PVT-mode moves.
Isx91 Coordinate System x Default Working Program Number
Range: 0 - 32,767
Units: Motion Program Numbers
Default: 0
Isx91 tells Turbo PMAC which motion program to run in Coordinate System x when commanded to run
from the control-panel input (START/ or STEP/ line taken low, or its equivalent in DPRAM). It performs
the same function for a hardware run command as the B command does for a software run command (R).
It is intended primarily for stand-alone Turbo PMAC applications. The first use of a B command from a
host computer for this coordinate system overrides this parameter.
Note:
Isx93 contains the address of the register that holds the time-base value (it is a
pointer to that register). Isx93 does not contain the time-base value itself.
slightly larger than twice the radius is given (for a half-circle move), and it is desired that this not create
an error condition.
Isx96 allows the user to set an error limit on the amount the move distance is greater than twice the
radius. If the move distance is greater than 2R, but by less than this limit, the move is done in a spiral
fashion to the endpoint, and no error condition is generated. If the distance error is greater than this limit,
the program will stop at the beginning of the move. Turbo PMAC will set this coordinate system’s circle
radius error status bit.
If Isx96 is set to 0, the error generation is disabled and any move distance greater than 2R is done in a
spiral fashion to the endpoint.
Example:
Given the program segment:
INC CIRCLE1 F2
X7.072 Y7.072 R5
2 2
Technically no circular arc path can be found, because the distance is SQRT(7.072 +7.072 ) = 10.003,
which is greater than twice the radius of 5. However, as long as Isx96 is greater than 0.003, PMAC will
create a near-circular path to the end point.
Isx97 Coordinate System x Minimum Arc Length
Range: Non-negative floating-point
Units: Semi-circles ( radians; 180 degrees)
Default: 0 (sets 2-20)
Isx97 sets the threshold between a short arc and a full circle for CIRCLE mode moves in Turbo PMAC’s
Coordinate System x. Isx97 is expressed as an angle, with units that represent a fraction of a half-circle.
It represents the smallest angle that can be covered by a programmed arc move.
Any programmed CIRCLE-mode move with an IJK-vector representation of the center that covers an
angle smaller than Isx97 is executed as a full circle plus the programmed angle change. Any such move
which covers an angle greater than Isx97 is executed as an arc smaller than a full circle.
The purpose of Isx97 is to support the circle programming standard that permits a full-circle move to be
commanded simply by making the end point equal to the starting point (0-degree arc), yet allow for
round-off errors.
Most users will be able to leave Isx97 at the default value of one-millionth of a semi-circle. This was
formerly the fixed threshold value. However, some users may want to enlarge the threshold to
compensate for round-off errors, particularly when using cutter-radius compensation in conjunction with
full-circle moves. Remember that no arc covering an angle less than Isx97 can be executed.
If a full-circle move is commanded with cutter compensation on, and the blending from the previous
move or into the next move creates a compensated outside corner without adding an arc (see Isx99),
PMAC will extend the compensated move past a full circle. If Isx97 is too small, it may execute this as a
very short arc, appearing to miss the move completely. Isx97 may have to be increased from its effective
default value to cover this case.
For backward compatibility reasons, if Isx97 is set to 0, a threshold value of 2 -20 (about one-millionth) of
a semi-circle will be used.
I6800 (etc.) controls these frequencies by setting the limits of the PWM up-down counter, which
increments and decrements at the PWMCLK frequency of 117,964.8 kHz (117.9648 MHz). The PWM
frequency of MACRO IC 0 determines the frequency of the two single-phase PWM outputs on the JHW
“Handwheel” connector.
The actual phase clock frequency is divided down from the maximum phase clock according to the setting
of I6801 (etc.). On the falling edge of the phase clock, PMAC2 samples any serial analog-to-digital
converters connected to its MACRO ICs (as for phase current measurement), and interrupts the processor
to start any necessary phase commutation and digital current-loop algorithms. Even if phasing and
current-loop algorithms are not used, the MaxPhase and Phase Clock frequencies are important because
the servo clock is derived from the phase clock.
The PWM frequency determines the actual switching frequency of amplifiers connected to any of four
machine interface channels with the direct PWM command. It is important only if the direct PWM
command signal format is used.
The maximum value that can be written into a PWM command register without full saturation is I6800+1
on the positive end, and -I6800-2 on the negative end.
If the MACRO IC is not used to generate the system clocks, this variable for the IC is generally set to the
same value as the comparable variable on the Servo IC (I7000, etc.) or MACRO IC (I6800, etc.) that is
used. The only time a different setting should be used is if it is desired that a different PWM frequency be
generated on the two channels (“DSPGATE2” ICs only) from that of the variable controlling the system
clocks. Certain different frequencies are possible, but they are restricted to the cases where:
2 * PWMFreq ( kHz )
{ Integer }
PhaseFreq
This will keep the PWM hardware on channels 1* and 2* in synchronization with the software algorithms
driven by the system’s Phase clock. For example if the system Phase clock frequency is 10 kHz, the
PWM frequency for channels from a different IC can be 5, 10, 15, 20, (etc.) kHz.
To set I6800 (etc.) for a desired PWM frequency, the following formula can be used:
117 ,964.8( kHz )
I 6800 1 (rounded down)
4 * PWM _ Freq( kHz )
To set I6800 (etc.) for a desired “maximum phase” clock frequency, the following formula can be used:
117 ,964.8( kHz )
I 6800 1 (rounded down)
2 * MaxPhaseFr eq( kHz )
Example:
To set a PWM frequency of 10 kHz and therefore a MaxPhase clock frequency of 20 kHz:
I6800 = (117,964.8 kHz / [4*10 kHz]) - 1 = 2948
To set a PWM frequency of 7.5 kHz and therefore a MaxPhase clock frequency of 15 kHz:
I6800 = (117,964.8 kHz / [4*7.5 kHz]) - 1 = 3931
See Also:
I7, I10, I67, I6801, I6802, I7000, I7001, I7002
I6802, I6852, I6902, and I6952, in conjunction with I6800 and I6801 (etc.), determine the frequency of
the Servo clock generated inside MACRO ICs 0, 1, 2, and 3, respectively. However, the internal clocks
on the IC are used only if the clock-direction control I-variable on the IC (I6807 I6857, I6907, or I6957)
is set to 0, specifying that this IC uses its own internal clocks. If this is the case, the IC outputs the clock
signals, and these variables determine the phase clock frequency for the entire PMAC2 system.
Typically, on a Turbo PMAC2 Ultralite board, MACRO IC 0 provides the Servo clock signal for the
entire board, so that I6800, I6801, and I6802 control the Ultralite Servo clock frequency.
Specifically, I6802 controls how many times the Servo clock frequency is divided down from the Phase
clock, whose frequency is set by I6801 and I6800. The Servo clock frequency is equal to the Phase clock
frequency divided by (I6802+1). I6802 has a range of 0 to 15, so the frequency division can be by a
factor of 1 to 16. The equation for I6802 is:
PhaseFreq ( kHz )
I 6802 1
ServoFreq( kHz )
The ratio of Phase Clock frequency to Servo Clock frequency must be an integer.
For execution of trajectories at the proper speed, I10 must be set properly to tell the trajectory generation
software what the Servo clock cycle time is. The formula for I10 is:
8 ,388 ,608
I 10
ServoFreq( kHz )
In terms of the variables that determine the Servo clock frequency on a Turbo PMAC2 Ultralite board, the
formula for I10 is:
I 10
640
2* I 6800 3I 6801 1I 6802 1
9
At the default servo clock frequency, I10 should be set to 3,713,992 in order that Turbo PMAC2’s
interpolation routines use the proper servo update time.
Note:
If the servo clock frequency is set too high, lower priority tasks such as
communications can be starved for time. If the background tasks are completely
starved, the watchdog timer will trip, shutting down the board. If a normal reset of
the board does not re-establish a state where the watchdog timer has not tripped
and communications works well, it will be necessary to re-initialize the board by
powering up with the E3 re-initialization jumper on. This restores default settings,
so communication is possible, and the Servo clock frequency can be set to a
supportable value.
Example:
With a 6.67 kHz Phase Clock frequency established by I6800 and I6801, and a desired 3.33 kHz Servo
Clock frequency:
I6802 = (6.67 / 3.33) - 1 = 2 - 1 = 1
See Also:
I10, I19, I6800, I6801, I7000, I7001, I7002
SCLK: The encoder sample clock signal SCLK controls how often the MACRO IC’s digital hardware
looks at the encoder and flag inputs. The MACRO IC can take at most one count per SCLK cycle, so the
SCLK frequency is the absolute maximum encoder count frequency. SCLK also controls the signal
propagation through the digital delay filters for the encoders and flags; the lower the SCLK frequency, the
greater the noise pulse that can be filtered out. The SCLK frequency should optimally be set to the lowest
value that can accept encoder counts at the maximum possible rate.
PFM_CLK: The pulse-frequency-modulation clock PFM_CLK controls the PFM circuitry that is
commonly used for stepper drives. The maximum pulse frequency possible is 1/4 of the PFM_CLK
frequency. The PFM_CLK frequency should optimally be set to the lowest value that can generate pulses
at the maximum frequency required.
DAC_CLK: The DAC_CLK controls the serial data frequency into D/A converters. If these converters
are on Delta Tau-provided accessories, the DAC_CLK setting should be left at the default value.
ADC_CLK: The ADC_CLK controls the serial data frequency from A/D converters. If these converters
are on Delta Tau-provided accessories, the ADC_CLK setting should be left at the default value.
Note:
By default, the DAC and ADC circuits of a MACRO IC are not used on a Turbo
PMAC2. The DAC and ADC lines are the alternate uses of pins on the
Multiplexer and I/O ports, respectively.
To determine the clock frequencies set by a given value of I6803 (etc.), use the following procedure:
1. Divide I6803 by 512 and round down to the nearest integer. This value N1 is the ADC_CLK divider.
2. Multiply N1 by 512 and subtract the product from I6803 to get I6803'. Divide I6803' by 64 and
round down to the nearest integer. This value N2 is the DAC_CLK divider.
3. Multiply N2 by 64 and subtract the product from I6803' to get I6803''. Divide I6803'' by 8 and round
down to the nearest integer. This value N3 is the PFM_CLK divider.
4. Multiply N3 by 8 and subtract the product from I6803''. The resulting value N4 is the SCLK divider.
Examples:
The maximum encoder count frequency in the application is 800 kHz, so the 1.2288 MHz SCLK
frequency is chosen. A pulse train up to 500 kHz needs to be generated, so the 2.4576 MHz PFM_CLK
frequency is chosen. The default serial DACs and ADCs provided by Delta Tau are used, so the default
DAC_CLK frequency of 4.9152 MHz and the default ADC_CLK frequency of 2.4576 MHz are chosen.
From the table:
SCLK Divider N: 5
PFM_CLK Divider N: 4
DAC_CLK Divider N: 3
ADC_CLK Divider N: 4
I6803 = 5 + (8 * 4) + (64 * 3) + (512 * 4) = 5 + 32 + 192 + 2048 = 2277
I6803 has been set to 3429. What clock frequencies does this set?
N1 = INT (3429/512) = 6 ADC_CLK = 611.44 kHz
I6803' = 3429 - (512*6) = 357
N2 = INT (357/64) = 5 DAC_CLK = 1.2288 MHz
I6803'' = 357 - (64*5) = 37
N3 = INT (37/8) = 4 PFM_CLK = 2.4576 MHz
N4 = 37 - (8*4) = 5 SCLK = 1.2288 MHz
See Also:
I-variables I7m03, I7m53
I6805, I6855, I6905, and I6955 control the DAC strobe signal for the two supplemental machine interface
channels of MACRO ICs 0, 1, 2, and 3, respectively, provided they are DSPGATE2 ICs.
The 24-bit word set by this variable for the IC is shifted out serially on the DAC_STROB lines, MSB
first, one bit per DAC_CLK cycle starting on the rising edge of the phase clock. The value in the LSB is
held until the next phase clock cycle.
For typical n-bit DACs, the strobe line is held high for n-1 clock cycles. Therefore, the common settings
of this variable are:
18-bit DACs: $7FFFC0 (high for 17 clock cycles)
16-bit DACs: $7FFF00 (high for 15 clock cycles)
12-bit DACs: $7FF000 (high for 11 clock cycles)
Note:
By default, the DAC circuitry of a MACRO IC is not used on a Turbo PMAC2.
The DAC lines are the alternate use of lines on the I/O port.
In any Turbo PMAC2 system, there must be only one source of servo and phase clock signals for the
system – either one of the Servo ICs or MACRO ICs, or a source external to the system. Only in a 3U-
format Turbo PMAC2 system (UMAC Turbo or 3U Turbo Stack) can the system clock signals come from
an accessory board. In all other Turbo PMAC2 systems, the system clock signals must come from and IC
on the base PMAC2 boards, or be brought from an external source through the serial port.
These variables are 2-bit values on DSPGATE2 MACRO ICs, but only 1-bit values on MACROGATE
MACRO ICs. Bit 0 is set to 0 for the IC to use its own Phase clock signal and output it; it is set to 1 to use
an externally input Phase clock signal. Bit 1 (DSPGATE2 only) is set to 1 for the IC to use its own Servo
clock signal and output it; it is set to 1 to use an externally input Servo clock signal. This yields four
possible values for I6807 (etc.):
I6807 = 0: Internal Phase clock; internal Servo clock
I6807 = 1: External Phase clock; internal Servo clock
I6807 = 2: Internal Phase clock; external Servo clock
I6807 = 3: External Phase clock; external Servo clock
In all normal use, I6807 (etc.) is either set to 0 (on at most one IC) or 3 (on all the other ICs – 1 on
MACROGATE ICs).
In typical use of the Turbo PMAC2 Ultralite, MACRO IC 0, whose Phase clock frequency is controlled
by I6800 and I6801, will generate the Phase clock signal for the entire board, so I6807 is set to 0, and
I6857, I6907, and I6957 should all be set to 1.
Note:
A MACROGATE MACRO IC cannot generate a servo clock signal internally.
Therefore, it cannot be used to provide the system clocks for the Turbo PMAC2
system.
During re-initialization, Turbo PMAC2 determines which IC it will use as the source of its system Phase
and Servo clock signals, setting I19 to the number of the clock-direction I-variable whose IC is selected as
the source. This clock-direction I-variable is then automatically set to 0; all other clock-direction I-
variables are set to 1 or 3. Most users will never change these settings.
When a clock-direction I-variable is commanded to its default value (e.g. I6857=*), Turbo PMAC2
looks to the value of I19 to determine whether this I-variable is set to 0 or 3 (0 or 1 on a MACROGATE
IC).
On the reset of a 3U-format Turbo PMAC2 system (UMAC Turbo or 3U Turbo Stack), the values set for
these I-variables are determined by the saved value of I19, and not by the saved values of these I-
variables themselves. On these systems, to change which IC is the source of the system clocks, change
the value of I19, save this setting, and reset the card.
To change which IC is the source of the system clocks in other Turbo PMAC2 systems, it is best to
change both clock-direction I-variables on a single command line (e.g. I6807=1 I7007=0), then
SAVE these new settings.
If all of the Servo ICs and MACRO ICs in a Turbo PMAC2 system have been set up for external phase
and servo clocks, but these clock signals are not provided, the Turbo PMAC2 will trip its watchdog timer
immediately.
Channel-Specific MACRO IC I-variables
(For MACRO IC Channel n*, where n* = 1 to 2)
I-Variables in the I6810s, I6820s, I6910s, and I6920s control the hardware aspects of the MACRO IC
DSPGATE2 ASIC that provides the machine interface for supplemental channels 1 and 2. Note that few
of these functions are used on the Turbo PMAC2s. By default, only the two encoder inputs and the two
C-channel PWM/PFM outputs are used. These I-variables are not active if the MACRO IC is not present,
or is a MACROGATE IC.
If I68n0/I69n0 is set to 8, the decoder inputs the pulse and direction signal generated by Channel n's pulse
frequency modulator (PFM) output circuitry. This permits the PMAC2 to create a phantom closed loop
when driving an open-loop stepper system. No jumpers or cables are needed to do this; the connection is
entirely within the MACRO IC. The counter polarity automatically matches the PFM output polarity.
If I68n0/I69n0 is set to 11 or 15, Channel n is expecting three Hall-sensor format inputs on CHAn, CHBn,
and CHCn, each with approximately 50% duty cycle, and approximately one-third (120oe) of a cycle out
of phase with each other. The decode circuitry will generate one count on each edge of each signal,
yielding six counts per signal cycle (x6 decode). The difference between 11 and 15 is which direction of
signal causes the counter to count up.
If I68n0/I69n0 is set to 12, the timer circuitry is set up to read magnetostrictive linear displacement
transducers (MLDTs) such as TemposonicsTM. In this mode, the timer is cleared when the PFM circuitry
sends out the excitation pulse to the sensor on PULSEn, and it is latched into the memory-mapped
register when the excitation pulse is received on CHAn.
I68n1/I69n1 MACRO IC Channel n* Position Compare Channel Select
Range: 0-1
Units: None
Default: 0
Note:
This I-variable is active only if the MACRO IC is present, and is a DSPGATE2 IC.
The presence and type of MACRO ICs are reported in I4902 and I4903.
I68n1 and I69n1 control which channel’s encoder counter is tied to the position compare circuitry for
Channel n* (n* = 1 to 2) on a “DSPGATE2” MACRO IC is decoded into counts. For MACRO ICs 0 and
2, n = n*; for MACRO ICs 1 and 3, n = n* + 5 (i.e. I6811 controls MACRO IC 0 Channel 1; I6971
controls MACRO IC 3 Channel 2). They have the following possible settings:
I68n1/I69n1 = 0: Use Channel n* encoder counter for position compare function
I68n1/I69n1 = 1: Use Channel 1* encoder counter on IC for position compare function
When I68n1/I69n1 is set to 0, Channel n*’s position compare registers tied to the channel’s own encoder
counter, and the position compare signal appears only on the EQU output for that channel.
When I68n1/I69n1 is set to 1, the channel's position compare register is tied to the first encoder counter
on the MACRO IC, and the position compare signal appears both on Channel n*’s EQU output, and
combined into the EQU output for Channel 1* on the MACRO IC (EQU1* on the board); executed as a
logical OR.
I68n1 for the first channel performs no effective function, so is always 1. It cannot be set to 0.
Note:
By default, the position compare circuitry on a MACRO IC is not used on Turbo
PMAC2 boards. The compare outputs are the alternate use of lines on the
Multiplexer port.
I68n2 and I69n2 determine which input signal or combination of signals, and which polarity, for Channel
n* (n* = 1 to 2) on a DSPGATE2 MACRO IC triggers a hardware position capture of the counter for
Encoder n*. For MACRO ICs 0 and 2, n = n*; for MACRO ICs 1 and 3, n = n* + 5 (i.e. I6812 controls
MACRO IC 0 Channel 1; I6972 controls MACRO IC 3 Channel 2). If a flag input (home, limit, or user)
is used, I68n3/I69n3 determines which flag. Proper setup of this variable is essential for a successful
homing search move or other move-until-trigger for the Motor xx using Channel n* for its position-loop
feedback and flags if the super-accurate hardware position capture function is used. If Ixx97 is at its
default value of 0 to select hardware capture and trigger, this variable must be set up properly.
The following settings of I68n2 may be used:
I68n2 = 0: Continuous capture
I68n2 = 1: Capture on Index (CHCn) high
I68n2 = 2: Capture on Flag n high
I68n2 = 3: Capture on (Index high AND Flag n high)
I68n2 = 4: Continuous capture
I68n2 = 5: Capture on Index (CHCn) low
I68n2 = 6: Capture on Flag n high
I68n2 = 7: Capture on (Index low AND Flag n high)
I68n2 = 8: Continuous capture
I68n2 = 9: Capture on Index (CHCn) high
I68n2 = 10: Capture on Flag n low
I68n2 = 11: Capture on (Index high AND Flag n low)
I68n2 = 12: Continuous capture
I68n2 = 13: Capture on Index (CHCn) low
I68n2 = 14: Capture on Flag n low
I68n2 = 15: Capture on (Index low and Flag n low)
Only flags and index inputs of the same channel number as the encoder may be used for hardware capture
of that encoder’s position. This means that to use the hardware capture feature for the homing search
move, Ixx25 must use flags of the same channel number as the encoder that Ixx03 uses for position-loop
feedback.
The trigger is armed when the position capture register is read. After this, as soon as the MACRO IC
hardware sees that the specified input lines are in the specified states, the trigger will occur -- it is level-
triggered, not edge-triggered.
Note:
By default, the index-channel and flag inputs of a MACRO IC are not used on a
Turbo PMAC2. The index inputs and flag inputs are alternate uses of pins on the
Multiplexer and I/O ports, respectively.
I68n3 and I69n3 determine which of the Flag inputs will be used for hardware position capture (if one is
used) of the encoder counter of Channel n* (n* = 1 to 2) on a DSPGATE2 MACRO IC. For MACRO
ICs 0 and 2, n = n*; for MACRO ICs 1 and 3, n = n* + 5 (i.e. I6813 controls MACRO IC 0 Channel 1;
I6973 controls MACRO IC 3 Channel 2). I68n2/I69n2 determines whether a flag is used and which
polarity of the flag will cause the trigger. The possible values of I68n3/I69n3 and the flag each selects is:
I68n3/I69n3 = 0: HOMEn (Home Flag n)
I68n3/I69n3 = 1: PLIMn (Positive End Limit Flag n)
I68n3/I69n3 = 2: MLIMn (Negative End Limit Flag n)
I68n3/I69n3 = 3: USERn (User Flag n)
I68n3/I69n3 is typically set to 0 for homing search moves in order to use the home flag for the channel.
Typically, it is set to 3 afterwards to select the User flag if other uses of the hardware position capture
function are desired, such as for probing and registration. To capture on the PLIMn or MLIMn overtravel
limit flags, disable their normal functions with Ixx25 or use a channel n where none of the flags is used
for the normal axis functions.
Note:
By default, the flag inputs of MACRO IC 0 are not used on a Turbo PMAC2.
Note:
By default, the index channels of a DSPGATE2 MACRO IC are not used on a
Turbo PMAC2. The index inputs are the “alternate” uses of pins on the
multiplexer port.
Note:
If the high/low polarity of the PWM signals is wrong for a particular amplifier,
what was intended to be deadtime between top and bottom on-states as set by
I6804 becomes overlap. If the amplifier input circuitry does not lock this out
properly, this causes an effective momentary short circuit between bus power and
ground. This would destroy the power transistors very quickly.
For PFM signals on Output C, non-inverted means that the pulse-on signal is high (direction polarity is
controlled by I68n8). During a change of direction, the direction bit will change synchronously with the
leading edge of the pulse, which in the non-inverted form is the rising edge. If the drive requires a set-up
time on the direction line before the rising edge of the pulse, the pulse output can be inverted so that the
rising edge is the trailing edge, and the pulse width (established by I6804) is the set-up time.
For DAC signals on Outputs A and B, non-inverted means that a 1 value to the DAC is high. DACs used
on Delta Tau accessory boards, as well as all other known DACs always expect non-inverted inputs, so
I68n7 should always be set to 0 or 2 when using DACs on Channel n.
Note:
Changing the high/low polarity of the digital data to the DACs has the effect of
inverting the voltage sense of the DACs’ analog outputs. This changes the polarity
match between output and feedback. If the feedback loop had been stable with
negative feedback, this change would create destabilizing positive feedback,
resulting in a dangerous runaway condition that would only be stopped when the
motor exceeded Ixx11 fatal following error
Note:
By default, only the C outputs (PWM or PFM) of MACRO IC 0 are used on a
Turbo PMAC2. The A and B outputs are the alternate use of pins on the I/O port.
Bits 16-19 together specify the slave number part of the packet address (0-15) that will cause a sync lock
pulse on the card, if this function is enabled by I6890/I6940/I6990. This function is useful for a PMAC2
that is a slave or non-synchronizing master on the ring, to keep it locked to the synchronizing master. If
the master address check for this node is disabled with I6890/I6940/I6990, only the slave number must
match to create the sync lock pulse. If the master address check is left enabled, the master number part of
the packet address must match the master number for the card, as set in bits 20-23 of I6891/I6941/I6991.
If this card is the synchronizing master, this function is not enabled, so the value of these bits does not
matter; they can be left at the default of 0.
Bits 20-23 specify the master number for the MACRO IC (0-15). Each MACRO IC on a ring must have
a separate master number, even multiple MACRO ICs on the same Turbo PMAC2 Ultralite. The number
must be specified whether the card is used as a master or a slave.
Hex ($) 0 0 0 0 0 0
Bit
If I78 is set greater than 0 to enable Type 1 master-to-slave auxiliary communications, then bit 15 of
I6891/I6941/I6991 is set to 1 automatically by the firmware at power-up/reset, regardless of the saved
value of I6891/I6941/I6991.
Examples:
Master number 0; Sync node address 0
Activated nodes 0-5; De-activated nodes 6-15:
I6891 =0000 0000 0000 0000 0011 1111 (binary) = $00003F
Master number 1; Sync node address 15 ($F)
Activated nodes 0, 2, 4, 6, 8, 10, 12; other nodes de-activated:
I6941 = 0001 1111 0001 0101 0101 0101 (binary) = $1F1555
Servo IC I-Variables
I-variables in the range I7000 to I7999 control the hardware setup of the Servo ICs in a Turbo PMAC
system.
There can be up to 10 Servo ICs in a Turbo PMAC system: Servo IC 0 to Servo IC 9; in the I-variable
numbering scheme, the Servo IC number determines the 100’s digit of the I-variable number, represented
by the letter m to refer to any IC generally (e.g. I7m00). Servo ICs 0 and 1 are on board the Turbo PMAC
itself, or on piggyback boards in the 3U Turbo Stack; Servo ICs 2 through 9 are off-board; on Acc-24 or
similar boards with their own Servo ICs.
Servo ICs can be either PMAC-style (DSPGATE) or PMAC2-style (DSPGATE1). The meaning of a
particular I-variable number can differ depending on which type of IC is used. The off-board ICs do not
have to be of the same type as the on-board ICs.
In firmware versions V1.933 and older, the user had tell Turbo PMAC which off-board Servo ICs were
present with I65, and which type they were with I66. In V1.934 and newer, Turbo PMAC automatically
detects the presence and type of all Servo ICs present at each power-up/reset, enables the I-variables for
those present, and selects the I-variables for type of each IC.
Each Servo IC has four channels of servo interface circuitry, numbered IC channels 1 to 4. In the I-
variable numbering scheme, the IC channel number determines the 10’s digit of the I-variable number,
represented by the letter ‘n’ to refer to any channel generally (e.g. I7mn3).
For even-numbered Servo ICs 0, 2, 4, 6, and 8, the channel numbers 1 – 4 on the IC match the channel
numbers 1 – 4 on the board. For odd-numbered Servo ICs 1, 3, 5, 7, and 9, which require the presence of
Option 1 on the board, the IC channel numbers 1 – 4 correspond to board channel numbers 5 – 8,
respectively.
The following table shows key data about each potential Servo IC in the system:
Servo Board Board I-Variables Base Default
IC # Channel #s Address Assignment
0 Turbo PMAC 1–4 I7000 – I7049 $078000 Motors 1-4
1 Turbo PMAC 5–8 I7100 – I7149 $078100 Motors 5-8
2 First Acc-24 1–4 I7200 – I7249 $078200 Motors 9-12
3 First Acc-24 5–8 I7300 – I7349 $078300 Motors 13-16
4 Second Acc-24 1–4 I7400 – I7449 $079200 Motors 17-20
5 Second Acc-24 5–8 I7500 – I7549 $079300 Motors 21-24
6 Third Acc-24 1–4 I7600 – I7649 $07A200 Motors 25-28
7 Third Acc-24 5–8 I7700 – I7749 $07A300 Motors 29-32
8 Fourth Acc-24 1–4 I7800 – I7849 $07B200 none
9 Fourth Acc-24 5–8 I7900 – I7949 $07B300 none
Note:
Some new accessory boards for the UMAC 3U-format Turbo PMAC employ
alternate addressing of Servo ICs, labeled Servo ICs 2* through 9*. Servo IC m*
is controlled by I-variables numbered 50 higher than Servo IC m,(e.g. I7250 –
I7299 for Servo IC 2*) and is addressed $20 higher (e.g. $078220 for Servo IC
2*).
PMAC2-Style Multi-Channel Servo IC I-Variables
I-variables in the range I7m00 to I7m09 control global and multi-channel aspects of the hardware setup
using the first “DSPGATE1” Servo IC on the Turbo PMAC2. On Turbo PMAC2 Ultralite boards, there
are no DSPGATE1 Servo ICs on board, so these functions are implemented in the DSPGATE2 ASIC,
which is controlled by variables in the I6800s.
I7m00 Servo IC m MaxPhase/PWM Frequency Control
Range: 0 - 32767
Units: MaxPhase Frequency = 117,964.8 kHz / [2*I7m00+3]
PWM Frequency = 117,964.8 kHz / [4*I7m00+6]
Default: 6527
MaxPhase Frequency = 117,964.8 / 13057 = 9.0346 kHz
PWM Frequency = 117,964.8 / 26114 = 4.5173 kHz
I7m00 controls the internal MaxPhase clock frequency, and the PWM frequency for the four machine
interface channels, on PMAC2-style Servo IC m (m = 0 to 9). The internally generated Phase and Servo
clocks on Servo IC m are derived from the MaxPhase clock.
If the Servo IC is used to generate the Phase and Servo clocks for the PMAC system (as set by I19 and
the I7m07 variables), this variable is part of the control for the frequency of these system clocks.
On Turbo PMAC2 boards that are not Ultralite, Servo IC 0 typically provides the Phase and Servo clock
signals for the entire board (I7007 = 0), so I7000 is used to derive the Phase clock and Servo clock
frequencies for the board, along with I7001 and I7002. (On Turbo PMAC2 Ultralite boards, this function
is controlled by I6800, I6801, and I6802, because MACRO IC 0 controls the board clock frequencies on
these boards.)
I7m00 controls these frequencies by setting the limits of the PWM up-down counter, which increments
and decrements at the PWMCLK frequency of 117,964.8 kHz (117.9648 MHz).
The actual Phase clock frequency is divided down from the maximum phase clock according to the
setting of I7001. On the falling edge of the phase clock, PMAC2 samples any serial analog-to-digital
converters connected to its Servo ICs (as for phase current measurement), and interrupts the processor to
start any necessary phase commutation and digital current-loop algorithms. Even if phasing and current-
loop algorithms are not used, the MaxPhase and Phase Clock frequencies are important because the servo
clock is derived from the phase clock.
The PWM frequency determines the actual switching frequency of amplifiers connected to any of four
machine interface channels with the direct PWM command. It is only important if the direct PWM
command signal format is used.
The maximum value that can be written into the PWM command register without full saturation is
I7m00+1 on the positive end, and –I7m00-2 on the negative end. Generally, the “PWM scale factor”
Ixx66 for Motor, which determines the maximum PWM command magnitude, is set to I7m00 + 10%.
Generally I7m00 for Servo IC m that is not controlling the system Phase clock frequency is set to the
same value as I7000 or I6800, which controls the board’s Phase clock frequency (with I7001 or I6801). If
a different PWM frequency is desired for the PWM outputs on Servo IC m, I7m00 should be set so that:
2 * PWMFreq ( kHz )
{ Integer }
PhaseFreq
This will keep the PWM hardware on these channels in synchronization with the software algorithms
driven by the system Phase clock.. For example, if the phase frequency is 10 kHz, the PWM frequency
for channels 5 to 8 can be 5, 10, 15, 20, (etc.) kHz.
To set I7m00 for a desired PWM frequency, the following formula can be used:
117 ,964.8( kHz )
I 7 m00 1 (rounded down)
4 * PWM _ Freq( kHz )
To set I7000 for a desired “maximum phase” clock frequency, the following formula can be used:
117 ,964.8( kHz )
I 7000 1 (rounded down)
2 * MaxPhaseFr eq( kHz )
For accessory boards in which alternate addressing of the Servo IC is used (labeled Servo IC m*), this
function is controlled by I7m50, not I7m00.
Example:
To set a PWM frequency of 10 kHz and therefore a MaxPhase clock frequency of 20 kHz:
I7000 = (117,964.8 kHz / [4*10 kHz]) - 1 = 2948
To set a PWM frequency of 7.5 kHz and therefore a MaxPhase clock frequency of 15 kHz:
I7000 = (117,964.8 kHz / [4*7.5 kHz]) - 1 = 3931
This means that I7002, in conjunction with I7001 and I7000, controls the Servo clock frequency for the
entire Turbo PMAC2 system. (For Turbo PMAC2 Ultralite boards, I6802, I6801 and I6800 control this.)
Each cycle of the Servo clock, Turbo PMAC2 updates the commanded position for each activated motor,
and executes the servo algorithm to compute the command to the amplifier or the commutation algorithm.
Specifically, I7m02 controls how many times the Servo clock frequency is divided down from the Phase
clock, whose frequency is set by I7m01 and I7m00. The Servo clock frequency is equal to the Phase
clock frequency divided by (I7m02+1). I7m02 has a range of 0 to 15, so the frequency division can be by
a factor of 1 to 16. The equation for I7m02 is:
PhaseFreq ( kHz )
I 7 m02 1
ServoFreq( kHz )
The ratio of Phase Clock frequency to Servo Clock frequency must be an integer.
For execution of trajectories at the proper speed, I10 must be set properly to tell the trajectory generation
software what the Servo clock cycle time is. The formula for I10 is:
8 ,388 ,608
I 10
ServoFreq( kHz )
In terms of the variables that determine the Servo clock frequency on a (non-Ultralite) Turbo PMAC2
board, the formula for I10 is:
I 10
640
2 * I 7000 3I 7001 1I 7002 1
9
At the default servo clock frequency, I10 should be set to 3,713,992 in order that Turbo PMAC2’s
interpolation routines use the proper servo update time.
Note:
If the servo clock frequency is set too high, lower priority tasks such as
communications can be starved for time. If the background tasks are completely
starved, the watchdog timer will trip, shutting down the board. If a normal reset of
the board does not re-establish a state where the watchdog timer has not tripped
and communications works well, it will be necessary to re-initialize the board by
powering up with the E3 re-initialization jumper on. This restores default settings,
so communication is possible, and I7000, I7001, and I7002 can be set to
supportable values.
For accessory boards in which alternate addressing of the Servo IC is used (labeled Servo IC m*), this
function is controlled by I7m52, not I7m02.
Example:
With a 6.67 kHz Phase Clock frequency established by I7000 and I7001, and a desired 3.33 kHz Servo
Clock frequency:
I7002 = (6.67 / 3.33) - 1 = 2 - 1 = 1
See Also: I10, I19, I7m00, I7m01, I7m07, I6800, I6801, I6802, I6807
To determine the clock frequencies set by a given value of I7m03, use the following procedure:
1. Divide I7m03 by 512 and round down to the nearest integer. This value N1 is the ADC_CLK divider.
2. Multiply N1 by 512 and subtract the product from I7m03 to get I7m03'. Divide I7m03' by 64 and
round down to the nearest integer. This value N2 is the DAC_CLK divider.
3. Multiply N2 by 64 and subtract the product from I7m03' to get I7m03''. Divide I7m03'' by 8 and
round down to the nearest integer. This value N3 is the PFM_CLK divider.
4. Multiply N3 by 8 and subtract the product from I7m03''. The resulting value N4 is the SCLK divider.
For accessory boards in which alternate addressing of the Servo IC is used (labeled Servo IC m*), this
function is controlled by I7m53, not I7m03.
Examples:
The maximum encoder count frequency in the application is 800 kHz, so the 1.2288 MHz SCLK
frequency is chosen. A pulse train up to 500 kHz needs to be generated, so the 2.4576 MHz PFM_CLK
frequency is chosen. The default serial DACs and ADCs provided by Delta Tau are used, so the default
DAC_CLK frequency of 4.9152 MHz and the default ADC_CLK frequency of 2.4576 MHz are chosen.
From the table:
SCLK Divider N: 5
PFM_CLK Divider N: 4
DAC_CLK Divider N: 3
ADC_CLK Divider N: 4
I7m03 = 5 + (8 * 4) + (64 * 3) + (512 * 4) = 5 + 32 + 192 + 2048 = 2277
I7m03 has been set to 3429. What clock frequencies does this set?
N1 = INT (3429/512) = 6 ADC_CLK = 611.44 kHz
I7m03' = 3429 - (512*6) = 357
N2 = INT (357/64) = 5 DAC_CLK = 1.2288 MHz
I7m03'' = 357 - (64*5) = 37
N3 = INT (37/8) = 4 PFM_CLK = 2.4576 MHz
N4 = 37 - (8*4) = 5 SCLK = 1.2288 MHz
See Also: I6803
I7m04 Servo IC m PWM Deadtime / PFM Pulse Width Control
Range: 0 - 255
Units: 16*PWM_CLK cycles / PFM_CLK cycles
PWM Deadtime = [16 / PWM_CLK (MHz)] * I7m04 = 0.135 usec * I7m04
PFM Pulse Width = [1 / PFM_CLK (MHz)] * I7m04
= PFM_CLK_period (usec) * I7m04
Default: 15
PWM Deadtime = 0.135 usec * 15 = 2.03 usec
PFM Pulse Width = [1 / 9.8304 MHz] * 15 = 1.526 usec (with default I7m03)
I7m04 controls the deadtime period between top and bottom on-times in the automatic PWM generation
for machine interface channels on PMAC2-style Servo IC m (m = 0 to 9). In conjunction with I7m03, it
also controls the pulse width for PMAC2's automatic pulse-frequency modulation generation for the
machine interface channels on Servo IC m.
The PWM deadtime, which is the delay between the top signal turning off and the bottom signal turning
on and vice versa, is specified in units of 16 PWM_CLK cycles. This means that the deadtime can be
specified in increments of 0.135 sec. The equation for I7m04 as a function of PWM deadtime is:
DeadTime( sec)
I 7 m04
0.135 sec
The PFM pulse width is specified in PFM_CLK cycles, as defined by I7m03. The equation for I7m04 as
a function of PFM pulse width and PFM_CLK frequency is:
I 7 m04 PFM _ CLK _ Freq( MHz ) * PFM _ Pulse _ Width( sec) + 1
In PFM pulse generation, the minimum off time between pulses is equal to the pulse width. This means
that the maximum PFM output frequency is
PFM _ CLK _ Freq ( MHz)
PFM _ Max _ Freq ( MHz)
2 * ( I 7m04 1)
For accessory boards in which alternate addressing of the Servo IC is used (labeled Servo IC m*), this
function is controlled by I7m54, not I7m04.
Examples:
A PWM deadtime of approximately 1 microsecond is desired:
I7m04 1 sec / 0.135 sec 7
With a 2.4576 MHz PFM_CLK frequency, a pulse width of 0.4 usec is desired:
I7m04 2.4576 MHz * 0.4 usec 1
See Also: I7m03, I6804
I7m05 Servo IC m DAC Strobe Word
Range: $000000 - $FFFFFF
Units: Serial Data Stream (MSB first, starting on rising edge of phase clock)
Default: $7FFFC0
I7m05 controls the DAC strobe signal for machine interface channels on Servo IC m. The 24-bit word set
by I7m05 is shifted out serially on the DAC_STROB lines, MSB first, one bit per DAC_CLK cycle
starting on the rising edge of the phase clock. The value in the LSB is held until the next phase clock
cycle.
For a typical n-bit DAC, the strobe line is held high for n-1 clock cycles. Therefore, the common settings
of this variable are:
18-bit DACs: $7FFFC0 (high for 17 clock cycles)
16-bit DACs: $7FFF00 (high for 15 clock cycles)
12-bit DACs: $7FF000 (high for 11 clock cycles)
The default I7m05 value of $7FFFC0 is suitable for the 18-bit DACs on the Acc-8E Analog Interface
Board. I7m05 should not be changed from the default unless different DACs are used.
For accessory boards in which alternate addressing of the Servo IC is used (labeled Servo IC m*), this
function is controlled by I7m55, not I7m05.
I7m06 Servo IC m ADC Strobe Word
Range: $000000 - $FFFFFF
Units: Serial Data Stream (MSB first, starting on rising edge of phase clock)
Default: $FFFFFE
I7m06 controls the ADC strobe signal for machine interface channels on Servo IC m. The 24-bit word set
by I7m06 is shifted out serially on the ADC_STROB lines, MSB first, one bit per ADC_CLK cycle starting
on the rising edge of the phase clock. The value in the LSB is held until the next phase clock cycle.
The first 1 creates a rising edge on the ADC_STROB output that is typically used as a start-convert
signal. Some A/D converters just need this rising edge for the conversion; others need the signal to stay
high all of the way through the conversion. The LSB of I7m06 should always be set to 0 so that a rising
edge is created on the next cycle. The default I7m06 value of $FFFFFE is suitable for virtually all A/D
converters.
The A/D converters used on matching Delta Tau products just need the rising edge at the start of a
conversion cycle; this permits intermediate bits in the data stream to be used as special control bits. Delta
Tau’s Acc-8T Supplemental Flag Multiplexer Board uses these bits to control the multiplexing; Delta
Tau’s Acc-8K1 Fanuc C/S-Series PWM Interface Board uses these bits to control the magnetic contactors
on the drives.
For accessory boards in which alternate addressing of the Servo IC is used (labeled Servo IC m*), this
function is controlled by I7m56, not I7m06.
I7m07 Servo IC m Phase/Servo Clock Direction
Range: 0-3
Units: None
Default: I7007 = 0 (non-Ultralite); = 3 (Ultralite)
I7107 – I7907 = 3
I7m07 controls whether Servo IC m uses its own internally generated Phase and Servo clock signals as
controlled by I7m00, I7m01, and I7m02, or whether it uses Phase and Servo clock signals from an outside
source.
In any Turbo PMAC2 system, there must be either one and only one source of servo and phase clock
signals for the system – one of the Servo ICs or MACRO ICs, or a source external to the system. Only in
a 3U-format Turbo PMAC2 system (UMAC Turbo or 3U Turbo Stack) can the system clock signals
come from an accessory board. In all other Turbo PMAC2 systems, the system clock signals must come
from and IC on the base PMAC2 boards, or be brought from an external source through the serial port.
I7m07 is a 2-bit value. Bit 0 is set to 0 for the IC to use its own Phase clock signal and output it; it is set
to 1 to use an externally input Phase clock signal. Bit 1 is set to 1 for the IC to use its own Servo clock
signal and output it; it is set to 1 to use an externally input Servo clock signal. This yields four possible
values for I7m07:
I7m07 = 0: Internal Phase clock; internal Servo clock
I7m07 = 1: External Phase clock; internal Servo clock
I7m07 = 2: Internal Phase clock; external Servo clock
I7m07 = 3: External Phase clock; external Servo clock
In all normal use, I7m07 is either set to 0 (on at most one IC) or 3 (on all the other ICs).
In general, Servo IC 0 or MACRO IC 0 (on an Ultralite board that has no Servo ICs) will be used to
generate Phase and Servo clock signals for the entire PMAC systems, so I7007 is set to 0 (or I6807 on an
Ultralite board), and I7107 through I7907 are set to 3.
During re-initialization, Turbo PMAC2 determines which IC it will use as the source of its system Phase
and Servo clock signals, setting I19 to the number of the clock-direction I-variable whose IC is selected as
the source. This clock-direction I-variable is then automatically set to 0; all other clock-direction I-
variables are set to 1 or 3. Most users will never change these settings.
When a clock-direction I-variable is commanded to its default value (e.g. I7207=*), Turbo PMAC2
looks to the value of I19 to determine whether this I-variable is set to 0 or 3.
On the reset of a 3U-format Turbo PMAC2 system (UMAC Turbo or 3U Turbo Stack), the values set for
these I-variables are determined by the saved value of I19, and not by the saved values of these I-
variables themselves. On these systems, to change which IC is the source of the system clocks, change
the value of I19, save this setting, and reset the card.
In other Turbo PMAC2 systems, to change which IC is the source of the system clocks, it is best to
change both clock-direction I-variables on a single command line (e.g. I6807=1 I7007=0), then
SAVE these new settings.
If all of the Servo and MACRO ICs in a Turbo PMAC2 system have been set up for external Phase and
Servo clocks, but these clock signals are not provided, the Turbo PMAC2 will immediately trip its
watchdog timer.
For accessory boards in which alternate addressing of the Servo IC is used (labeled Servo IC m*), this
function is controlled by I7m57, not I7m07.
PMAC2-Style Channel-Specific Servo IC I-Variables
(For Servo IC m Channel n, where m = 0 to 9, and n = 1 to 4)
I7mn0 Servo IC m Channel n Encoder/Timer Decode Control
Range: 0 - 15
Units: None
Default: 7
I7mn0 controls how the input signal for Encoder n on a PMAC2-style Servo IC m is decoded into counts.
As such, this defines the sign and magnitude of a count. The following settings may be used to decode an
input signal.
I7mn0 = 0: Pulse and direction CW
I7mn0 = 1: x1 quadrature decode CW
I7mn0 = 2: x2 quadrature decode CW
I7mn0 = 3: x4 quadrature decode CW
I7mn0 = 4: Pulse and direction CCW
I7mn0 = 5: x1 quadrature decode CCW
I7mn0 = 6: x2 quadrature decode CCW
I7mn0 = 7: x4 quadrature decode CCW
I7mn0 = 8: Internal pulse and direction
I7mn0 = 9: Not used
I7mn0 = 10: Not used
I7mn0 = 11: x6 hall-format decode CW*
I7mn0 = 12: MLDT pulse timer control
(internal pulse resets timer; external pulse latches timer)
I7mn0 = 13: Not used
I7mn0 = 14: Not used
I7mn0 = 15: x6 hall-format decode CCW*
*requires version B or newer of the DSPGATE1 Servo IC.
In any of the quadrature decode modes, the Servo IC is expecting two input waveforms on CHAn and
CHBn, each with approximately 50% duty cycle, and approximately one-quarter of a cycle out of phase
with each other. Times-one (x1) decode provides one count per cycle; x2 provides two counts per cycle;
and x4 provides four counts per cycle. The vast majority of users select x4 decode to get maximum
resolution.
The clockwise (CW) and counterclockwise (CCW) options simply control which direction counts up. If
the wrong direction sense is received, simply change to the other option (e.g. from 7 to 3 or vice versa).
WARNING:
Changing the direction sense of the decode for the feedback encoder of a motor
that is operating properly will result in unstable positive feedback and a dangerous
runaway condition in the absence of other changes. The output polarity must be
changed as well to re-establish polarity match for stable negative feedback.
In the pulse-and-direction decode modes, the Servo IC is expecting the pulse train on CHAn, and the
direction (sign) signal on CHBn. If the signal is unidirectional, the CHBn line can be allowed to pull up
to a high state, or it can be hardwired to a high or low state.
If I7mn0 is set to 8, the decoder inputs the pulse and direction signal generated by Channel n's pulse
frequency modulator (PFM) output circuitry. This permits the PMAC2 to create a phantom closed loop
when driving an open-loop stepper system. No jumpers or cables are needed to do this; the connection is
entirely within the Servo IC. The counter polarity automatically matches the PFM output polarity.
If I7mn0 is set to 11 or 15, Channel n is expecting three Hall-sensor format inputs on CHAn, CHBn, and
CHCn, each with approximately 50% duty cycle, and approximately one-third (120oe) of a cycle out of
phase with each other. The decode circuitry will generate one count on each edge of each signal, yielding
6 counts per signal cycle (x6 decode). The difference between 11 and 15 is which direction of signal
causes the counter to count up.
If I7mn0 is set to 12, the timer circuitry is set up to read magnetostrictive linear displacement transducers
(MLDTs) such as TemposonicsTM. In this mode, the timer is cleared when the PFM circuitry sends out
the excitation pulse to the sensor on PULSEn, and it is latched into the memory-mapped register when the
excitation pulse is received on CHAn.
I7mn1 Servo IC m Channel n Position Compare Channel Select
Range: 0-1
Units: None
Default: 0
I7mn1 controls which channel’s encoder counter is tied to the position compare circuitry for Channel n on
a PMAC2-style Servo IC m. It has the following possible settings:
I7mn1 = 0: Use Channel n encoder counter for position compare function
I7mn1 = 1: Use Channel 1 encoder counter on IC for position compare function
When I7mn1 is set to 0, Channel n’s position compare registers are tied to the channel's own encoder
counter, and the position compare signal appears only on the EQU output for that channel.
When I7mn1 is set to 1, the channel's position compare register is tied to the first encoder counter on the
Servo IC, and the position compare signal appears both on Channel n’s EQU output, and combined into
the EQU output for Channel 1 on the Servo IC (EQU1 or EQU5 on the board); executed as a logical
AND.
I7m11 performs no effective function, so is always 1. It cannot be set to 0.
I7mn2 Servo IC m Channel n Capture Control
Range: 0 - 15
Units: none
Default: 1
I7mn2 determines which input signal or combination of signals for Channel n of a PMAC2-style Servo IC
m, and which polarity, triggers a hardware position capture of the counter for Encoder n. If a flag input
(home, limit, or user) is used, I7mn3 determines which flag. Proper setup of this variable is essential for a
successful homing search move or other move-until-trigger for the Motor xx using Channel n for its
position-loop feedback and flags if the super-accurate hardware position capture function is used. If
Ixx97 is at its default value of 0 to select hardware capture and trigger, this variable must be set up
properly.
The following settings of I7mn2 may be used:
I7mn2 = 0: Immediate capture
I7mn2 = 1: Capture on Index (CHCn) high
I7mn2 = 2: Capture on Flag n high
When I7mn4 is set to 0, the encoder index channel input (CHCn) is passed directly into the position
capture circuitry.
When I7mn4 is set to 1, the encoder index channel input (CHCn) is logically combined with (gated by)
the quadrature signals of Encoder n before going to the position capture circuitry. The intent is to get a
gated index signal exactly one quadrature state wide. This provides a more accurate and repeatable
capture, and makes the use of the capture function to confirm the proper number of counts per revolution
very straightforward.
In order for the gated index capture to work reliably, the index pulse must reliably span one, but only one,
high-high or low-low AB quadrature state of the encoder. I7mn5 allows the selection of which of these
two possibilities is used.
Note:
If I7mn4 is set to 1, but I7mn2 bit 0 is set to 0, so the index is not used in the
position capture, then the encoder position is captured on the first edge of any of
the U, V, or W flag inputs for the channel. In this case, bits 0, 1, and 2 of the
channel status word tell what hall-state edge caused the capture.
Note:
Immediately after power-up, the Yaskawa encoder automatically cycles its AB
outputs forward and back through a full quadrature cycle to ensure that all of the
hall commutation states are available to the controller before any movement is
started. However, if the encoder is powered up at the same time as the Turbo
PMAC, this will happen before the Servo IC is ready to accept these signals. Bit 2
of the channel’s status word, Invalid De-multiplex, will be set to 1 if the Servo IC
has not seen all of these states when it was ready for them. To use this feature, it is
recommended that the power to the encoder be provided through a software-
controlled relay to ensure that valid readings of all states have been read before
using these signals for power-on phasing.
I7mn5 has the following possible settings:
I7mn5 = 0: Gate index with high-high quadrature state (GI = A and B and C), no demux
I7mn5 = 1: Gate index with low-low quadrature state (GI = A/ and B/ and C), no demux
I7mn5 = 2 or 3: De-multiplex hall and index from third channel, gating irrelevant
Note:
If the high/low polarity of the PWM signals is wrong for a particular amplifier,
what was intended to be deadtime between top and bottom on states, as set by
I6m04 becomes overlap. If the amplifier-input circuitry does not lock this out
properly, this causes an effective momentary short circuit between bus power and
ground. This would destroy the power transistors very quickly.
For PFM signals on Output C, non-inverted means that the pulse-on signal is high (direction polarity is
controlled by I7mn8). During a change of direction, the direction bit will change synchronously with the
leading edge of the pulse, which in the non-inverted form is the rising edge. If the drive requires a set-up
time on the direction line before the rising edge of the pulse, the pulse output can be inverted so that the
rising edge is the trailing edge, and the pulse width (established by I6m04) is the set-up time.
For DAC signals on Outputs A and B, non-inverted means that a 1 value to the DAC is high. DACs used
on Delta Tau accessory boards, as well as all other known DACs always expect non-inverted inputs, so
I6mn7 should always be set to 0 or 2 when using DACs on Channel n.
Note:
Changing the high/low polarity of the digital data to the DACs has the effect of
inverting the voltage sense of the DACs’ analog outputs. This changes the polarity
match between output and feedback. If the feedback loop had been stable with
negative feedback, this change would create destabilizing positive feedback,
resulting in a dangerous runaway condition that would only be stopped when the
motor exceeded Ixx11 fatal following error
When the hardware-1/T functionality is enabled, the IC computes a new fractional-count position estimate
based on timers every SCLK (encoder sample clock) cycle. This permits the fractional count data to be
used for hardware capture and compare functions, enhancing their resolution. The sub-count position-
capture data can be used automatically in Turbo PMAC triggered-move functions if bit 12 of Ixx24 is set
to 1. This is particularly useful when the IC is used on an Acc-51 high-resolution analog-encoder
interpolator board. However, it replaces the timer registers at the first two “Y” addresses for the channel
with fractional count position data, so the traditional software-1/T method of the conversion table cannot
work if this is enabled.
If the hardware-1/T functionality is enabled and to be able to use 1/T interpolation in the servo loop, use
the hardware-1/T extension method ($C method digit with the mode switch bit set to 1) in the encoder
conversion table.
PMAC-Style Servo IC Setup I-Variables
I7mn0 Servo IC m Channel n Encoder/Timer Decode Control
Range: 0 - 15
Units: None
Default: 7
I7mn0 controls how the input signal for Encoder n on PMAC-style Servo IC m is decoded into counts.
As such, this defines the sign and magnitude of a count. The following settings may be used to decode an
input signal.
I7mn0 = 0: Pulse and direction CW
I7mn0 = 1: x1 quadrature decode CW
I7mn0 = 2: x2 quadrature decode CW
I7mn0 = 3: x4 quadrature decode CW
I7mn0 = 4: Pulse and direction CCW
I7mn0 = 5: x1 quadrature decode CCW
I7mn0 = 6: x2 quadrature decode CCW
I7mn0 = 7: x4 quadrature decode CCW
In any of the quadrature decode modes, PMAC is expecting two input waveforms on CHAn and CHBn,
each with approximately 50% duty cycle, and approximately one-quarter of a cycle out of phase with
each other. Times-one (x1) decode provides one count per cycle; x2 provides two counts per cycle; and
x4 provides four counts per cycle. The vast majority of users select x4 decode to get maximum
resolution.
The clockwise (CW) and counterclockwise (CCW) options simply control which direction counts up. If
the wrong direction sense is received, simply change to the other option (e.g. from 7 to 3 or vice versa).
WARNING:
Changing the direction sense of the encoder decode for a motor that is servoing
properly will result in unstable positive feedback and a dangerous runaway
condition in the absence of other changes (for motors not commutated by PMAC
from the same encoder). The output polarity must be changed as well to re-
establish polarity match for stable negative feedback.
In the pulse-and-direction decode modes, PMAC is expecting the pulse train on CHAn, and the direction
(sign) signal on CHBn. If the signal is unidirectional, the CHBn input can be tied high (to +5V) or low
(to GND), or, if set up by E18-E21, E24-E27 for single-ended (non-differential) input, left to float high.
Any spare encoder counters may be used as fast and accurate timers by setting this parameter in the 8 to
15 range. In this range, any input signal is ignored.
Table Structure: The ECT consists of a series of entries, with each entry creating one processed
(converted) feedback value. An entry in the ECT can have 1, 2, or 3 lines, with each line containing a 24-
bit setup word (I-variable) in Y-memory, and a 24-bit result register in X-memory. Therefore, each entry
contains 1, 2, or 3 of these 24-bit I-variables. The final result is always in the X-memory register
matching the last I-variable in the entry.
The variables that commonly contain the address of the last line of the entry are Ixx03 Motor xx Position-
Loop Feedback Address, Ixx04 Motor xx Velocity-Loop Feedback Address, Ixx05 Motor xx Master
Position Address and Isx93 Coordinate System x Time-Base Address.
The addresses for these variables can be specified directly using the above table (e.g. I103=$3501) or
by reference to the table I-variable with the special on-line command I{constant}=@I{constant},
which sets the first I-variable to the address of the second (e.g. I103=@I8000).
Entry First Line: The first line’s setup register (I-variable) in each entry consists of a source address in
the low 19 bits (bits 0 – 18), which contains the Turbo PMAC address of the raw data to be processed, a
possible mode switch in bit 19 and a method value in the high 4 bits (first hex digit), which specifies how
this data is to be processed. If the first line (I-variable) in the entry is $000000, this signifies the end of
the active table, regardless of what subsequent entries in the table (higher numbered I-variables) contain.
Entry Additional Lines: Depending on the method, one or two additional lines (I-variables) may be
required in the entry to provide further instructions on processing.
The following table summarizes the content of entries in the Encoder Conversion Table:
Method # of Process Defined Mode Switch 1st Additional Line 2nd Additional
Digit lines Line
$0 1 1/T Extension of None - -
Incremental Encoder
$1 1 ACC-28 style A/D 0 = signed data - -
converter (high 16 bits,
1 = unsigned data
no rollover)
$2 2 Parallel Y-word data, no 0 = normal shift Width/Offset -
filtering Word
1 = unshifted
$3 3 Parallel Y-word data, 0 = normal shift Width/Offset Max Change per
with filtering Word Cycle
1 = unshifted
$4 2 “Time Base” scaled None Time Base Scale -
digital differentiation Factor
$5 2 Integrated ACC-28 style 0 = signed data Input Bias -
A/D converter
1 = unsigned data
$6 2 Parallel Y/X-word data, 0 = normal shift Width/Offset -
no filtering Word
1 = unshifted
$7 3 Parallel Y/X-word data, 0 = normal shift Width/Offset Max Change per
with filtering Word Cycle
1 = unshifted
$8 1 Parallel Extension of 0 = PMAC(1) IC - -
Incremental Encoder
1 = PMAC2 IC
$9 2 Triggered Time Base, 0 = PMAC(1) IC Time Base Scale -
frozen Factor
1 = PMAC2 IC
Incremental Encoder Entries ($0, $8, $C): These three conversion table methods utilize the
incremental encoder registers in the Servo ICs. Each method provides a processed result with the units of
(1/32) count – the low five bits of the result are fractional data.
Software 1/T Extension: With the $0 method, the fractional data is computed by dividing the Time Since
Last Count register by the Time Between Last 2 Counts register. This technique is known as 1/T
extension and is the default and most commonly used method. It can be used with a digital incremental
encoder connected directly to the Turbo PMAC, through either PMAC-style or PMAC2-style Servo ICs.
Note:
1/T extension with eight bits of fractional resolution (units of 1/256 count) can be
gotten using the intermediate result value of the triggered time-base conversion in
running mode. This intermediate result is in the first line of the entry. If used for
position data, one true count of the position is considered by Turbo PMAC
software to be eight counts.
Parallel Extension: With the $8 method, the fractional data is computed by reading the five inputs at bits
19-23 either of the specified address (USERn, Wn, Vn, Un, and Tn flag inputs, respectively) if the mode
switch bit of the setup I-variable is set to 1 for PMAC2-style Servo ICs, or of the specified address plus
four (CHC[n+1], HMFL[n+1], +LIM[n+1], -LIM[n+1], FAULT[n+1]) if the mode switch bit of the setup
I-variable is set to 0 for PMAC-style Servo ICs. This technique is known as “parallel extension”, and can
be used with an analog incremental encoder processed through an Acc-8D Option 8 Analog Encoder
Interpolator board or its equivalent.
No Extension: In the $C method with the mode switch bit set to 0, the fractional data is always set to
zero, which means there is no extension of the incremental encoder count. This setting is used mainly to
verify the effect of one of the two extension methods. It is also recommended when feeding back the
pulse-and-direction outputs for stepper drives.
Hardware 1/T Extension: In the $C method with the mode switch bit set to 1, the fractional data is read
from a special timer-based register in the Servo IC that has already computed the fractional-count data in
hardware. This feature is supported only in the D-revision or newer (first shipments around the beginning
of 2002) of the PMAC2-style DSPGATE1 Servo ICs. The alternate timer registers for the encoder
channel must be selected by setting I7mn9 for the channel to 1.
Using this mode, permits timer-based sub-count capture and compare features to be used on this encoder
channel.
With any of these three conversion methods, the source address in the low 19 bits (bits 0 - 18) is that of
the starting register of the machine interface channel.
The first table below shows the entries for PMAC-style encoder channels. The ‘m’ in the first hex digit
(bits 20 - 23) represents the conversion method ($0, $8, or $C). For the PMAC-style channels, the bit 19
mode switch is always 0, so the second hex digit is always ‘7’ for the hardware registers.
Entries for PMAC-Style Servo ICs
Servo Chan. 1 Chan. 2 Chan. 3 Chan. 4 Notes
IC #
0 $m78000 $m78004 $m78008 $m7800C First IC on board PMAC
1 $m78100 $m78104 $m78108 $m7810C Second IC on board PMAC
2 $m78200 $m78204 $m78208 $m7820C First IC on first Acc-24P/V
3 $m78300 $m78304 $m78308 $m7830C Second IC on first Acc-24P/V
4 $m79200 $m79204 $m79208 $m7920C First IC on second Acc-24P/V
5 $m79300 $m79304 $m79308 $m7930C Second IC on second Acc-24P/V
6 $m7A200 $m7A204 $m7A208 $m7A20C First IC on third Acc-24P/V
7 $m7A300 $m7A304 $m7A308 $m7A30C Second IC on third Acc-24P/V
8 $m7B200 $m7B204 $m7B208 $m7B20C First IC on fourth Acc-24P/V
9 $m7B300 $m7B304 $m7B308 $m7B30C Second IC on fourth Acc-24P/V
The next table shows the entry values for PMAC2-style encoder channels. The m in the first hex digit
(bits 20 – 23) represents the conversion method ($0, $8, or $C). The n in the second hex digit (bits 16 –
19) contains the bit 19 mode switch and the start of the source address. For methods $0 (software 1/T
extension) and $C (no extension), the bit 19 mode switch is 0, making the second hex digit 7. For method
$8 (parallel extension) or for method $C for hardware 1/T extension, the bit 19 mode switch is 1,
changing the second hex digit from 7 to F.
Entries for PMAC2-Style Servo ICs
Servo Chan. 1 Chan. 2 Chan. 3 Chan. 4 Notes
IC #
0 $mn8000 $mn8008 $mn8010 $mn8018 First IC on board PMAC2, 3U stack
1 $mn8100 $mn8108 $mn8010 $mn8018 Second IC on board PMAC2, 3U stack
2 $mn8200 $mn8208 $mn8210 $mn8218 First Acc-24E2x, first IC on first Acc-24P/V2
3 $mn8300 $mn8308 $mn8310 $mn8318 Second Acc-24E2x, second IC on first Acc-24P/V2
4 $mn9200 $mn9208 $mn9210 $mn9218 Third Acc-24E2x, first IC on second Acc-24P/V2
5 $mn9300 $mn9308 $mn9310 $mn9318 Fourth Acc-24E2x, second IC on second Acc-24P/V2
The next table shows the entry values that should be used for Acc-28B boards interfaced to PMAC2-style
Servo ICs (Acc-28A is not compatible with these ICs). The ‘m’ in the first hex digit refers to the method
digit – $1 for un-integrated; $5 for integrated. Note that setting the bit 19 mode switch bit to 1 for the
Acc-28B changes the second hex digit from 7 to F.
Entries for PMAC2-Style ADC Registers Using Acc-28B
Register PMAC2 First Second Third Fourth
Acc-24P/V2 Acc-24P/V2 Acc-24P/V2 Acc-24P/V2
ADC 1A $mF8005 $mF8205 $mF9205 $mFA205 $mFB205
ADC 1B $mF8006 $mF8206 $mF9206 $mFA206 $mFB206
ADC 2A $mF800D $mF820D $mF920D $mFA20D $mFB20D
ADC 2B $mF800E $mF820E $mF920E $mFA20E $mFB20E
ADC 3A $mF8015 $mF8215 $mF9215 $mFA215 $mFB215
ADC 3B $mF8016 $mF8216 $mF9216 $mFA216 $mFB216
ADC 4A $mF801D $mF821D $mF921D $mFA21D $mFB21D
ADC 4B $mF801E $mF821E $mF921E $mFA21E $mFB21E
ADC 5A $mF8105 $mF8305 $mF9305 $mFA305 $mFB305
ADC 5B $mF8106 $mF8306 $mF9306 $mFA306 $mFB306
ADC 6A $mF810D $mF830D $mF930D $mFA30D $mFB30D
ADC 6B $mF810E $mF830E $mF930E $mFA30E $mFB30E
ADC 7A $mF8115 $mF8315 $mF9315 $mFA315 $mFB315
ADC 7B $mF8116 $mF8316 $mF9316 $mFA316 $mFB316
ADC 8A $mF811D $mF831D $mF931D $mFA31D $mFB31D
ADC 8B $mF811E $mF831E $mF931E $mFA31E $mFB31E
The next table shows the entry values that should be used for Acc-28E boards in a UMAC Turbo system.
The m in the first hex digit refers to the method digit – $1 for un-integrated; $5 for integrated. Note that
setting the bit 19 mode switch bit to 1 for the Acc-28E changes the second hex digit from 7 to F.
Entries for UMAC Acc-28E ADCs
I/O IC # SW1-1 SW1-2 SW1-3 SW1-4 Chan. 1 Chan. 2 Chan. 3 Chan. 4
0 ON ON ON ON $mF8C00 $mF8C01 $mF8C02 $mF8C03
1 OFF ON ON ON $mF8D00 $mF8D01 $mF8D02 $mF8D03
2 ON OFF ON ON $mF8E00 $mF8E01 $mF8E02 $mF8E03
3 OFF OFF ON ON $mF8F00 $mF8F01 $mF8F02 $mF8F03
4 ON ON OFF ON $mF9C00 $mF9C01 $mF9C02 $mF9C03
5 OFF ON OFF ON $mF9D00 $mF9D01 $mF9D02 $mF9D03
6 ON OFF OFF ON $mF9E00 $mF9E01 $mF9E02 $mF9E03
7 OFF OFF OFF ON $mF9F00 $mF9F01 $mF9F02 $mF9F03
8 ON ON ON OFF $mFAC00 $mFAC01 $mFAC02 $mFAC03
3 OFF ON ON OFF $mFAD00 $mFAD01 $mFAD02 $mFAD03
4 ON OFF ON OFF $mFAE00 $mFAE01 $mFAE02 $mFAE03
5 OFF OFF ON OFF $mFAF00 $mFAF01 $mFAF02 $mFAF03
6 ON ON OFF OFF $mFBC00 $mFBC01 $mFBC02 $mFBC03
7 OFF ON OFF OFF $mFBD00 $mFBD01 $mFBD02 $mFBD03
8 ON OFF OFF OFF $mFBE00 $mFBE01 $mFBE02 $mFBE03
9 OFF OFF OFF OFF $mFBE00 $mFBE01 $mFBE00 $mFBE03
Integration Bias: The $5 integrated format requires a second line to specify the bias of the A/D converter.
This bias term is a signed quantity (even for an unsigned A/D converter), with units of 1/256 of the LSB
of the 16-bit A/D converter. This value is subtracted from the reading of the ADC before the integration
occurs.
For example, if there were an offset in a 16-bit ADC of +5 LSBs, this term would be set to 1280. If no
bias is desired, a zero value should be entered here. If the conversion is unsigned, the result after the bias
is not permitted to be less than zero. This term permits reasonable integration, even with an analog offset.
Parallel Feedback Entries ($2, $3, $6, $7): The parallel feedback entries read a word from the address
specified in the low 19 bits (bits 0 to 18) of the first line. The four methods in this class are:
$2: Y-word parallel, no filtering (2-line entry)
$3: Y-word parallel, with filtering (3-line entry)
$6: Y/X-word parallel, no filtering (2-line entry)
$7: Y/X-word parallel, with filtering (3-line entry)
The Bit-19 mode switch in the first line controls whether the least significant bit (LSB) of the source
register is placed in Bit 5 of the result register (normal shift), providing the standard 5 bits of (non-existent)
fraction, or the LSB is placed in Bit 0 of the result register (unshifted), creating no fractional bits.
Normally, the Bit-19 mode switch is set to 0 to place the source LSB in Bit 5 of the result register. Bit 19
is set to 1 to place to source LSB in Bit 0 of the result register for one of three reasons:
The data already comes with five bits of fraction, as from a Compact MACRO Station.
The normal shift limits the maximum velocity too much (Vmax<218 LSBs per servo cycle)
The normal shift limits the position range too much (Range<+247/Ix08/32 LSBs)
Unless this is done because the data already contains fractional information, the unshifted conversion will
mean that the motor position loop will consider 1 LSB of the source to be 1/32 of a count, instead of 1
count.
Width/Offset Word: The second setup line (I-variable) of a parallel read entry contains the width of the
data to be read, and the location of the LSB. This 24-bit value, usually represented as 6 hexadecimal digits,
is split evenly into two halves, each of 3 hex digits. The first half represents the width of the parallel data in
bits, and can range from $001 (1 bit wide – not of much practical use) to $018 (24 bits wide).
The second half of the line contains the bit location of the LSB of the data in the source word, and can
range from $000 (Bit 0 of the Y-word at the source address is the LSB), through $017 (Bit 23 of the Y-
word at the source address), and $018 (Bit 24, which is Bit 0 of the next word, is the LSB) to $02F (Bit
47, which is Bit 23 of the next word, is the LSB).
If the LSB bit location exceeds 23, or the sum of the LSB bit location and the bit width exceeds 24, the
source data extends into the next word. If the method character is $2 or $3, the next word is the Y-word
at the source address + 1. If the method character is $6 or $7, the next word is the X-word at the source
address.
For example, to use 20 bits starting at bit 0 (bits 0 – 19) of the Y-word of the source address, this word
would be set to $014000. To use all 24 bits of the X-word of the source address, this word would be set
to $018018. To use 24 bits starting at bit 12 of the specified address (with the highest 12 bits coming
from the X-word or the next higher Y-address, this word would be set to $01800C.
Maximum Change Word: If the method character for a parallel read is $3 or $7, specifying filtered
parallel read, there is a third setup line (I-variable) for the entry. This third line contains the maximum
change in the source data in a single cycle that will be reflected in the processed result, expressed in LSBs
per servo cycle. The filtering that this creates provides an important protection against noise and
misreading of data. This number is effectively a velocity value, and should be set slightly greater than the
maximum true velocity ever expected.
Acc-14: The Accessory 14 family of boards is often used to bring parallel data feedback to the Turbo
PMAC, such as that from parallel absolute encoders, and from interferometers. The following table
shows the first line of the entries for Acc-14D/V boards connected to a Turbo PMAC controller over a
JEXP expansion port cable:
Entries for Acc-14D/V Registers
Register First Line Value Register First Line Value
First Acc-14D/V Port A $m78A00 Fourth Acc-14D/V Port A $m78D00
First Acc-14D/V Port B $m78A01 Fourth Acc-14D/V Port B $m78D01
Second Acc-14D/V Port A $m78B00 Fifth Acc-14D/V Port A $m78E00
Note:
The bit 19 mode switch has been set to 1 so that the data out of the previous phase
position register from the MACRO ring is not shifted. This changes the second
hex digit from 0 to 8. Type 1 MACRO feedback comes with fractional count
information in the low five bits, so it does not need to be shifted.
The second line of an entry for previous phase position feedback should be $018000 to specify the use of
24 bits ($018) starting at bit 0 ($000).
MLDT Feedback: PMAC2-style Servo ICs have the ability to interface directly to magnetostrictive linear
displacement transducers (MLDTs), outputting the excitation pulse, receiving the echo pulse, and
measuring the time between the two. This time is directly proportional to the distance. For this feedback
the time between last two counts register is used like an absolute encoder. The following table shows the
first line of the parallel feedback entry for each channel’s timer register:
Entries for PMAC2-Style MLDT Timer Registers
Servo Chan. 1 Chan. 2 Chan. 3 Chan. 4 Notes
IC #
0 $378000 $378008 $378010 $378018 First IC on board PMAC2, 3U stack
1 $378100 $378108 $378010 $378018 Second IC on board PMAC2, 3U stack
2 $378200 $378208 $378210 $378218 First Acc-24E2x, first IC on first Acc-24P/V2
3 $378300 $378308 $378310 $378318 Second Acc-24E2x, second IC on first Acc-24P/V2
4 $379200 $379208 $379210 $379218 Third Acc-24E2x, first IC on second Acc-24P/V2
5 $379300 $379308 $379310 $379318 Fourth Acc-24E2x, second IC on second Acc-24P/V2
6 $37A200 $37A208 $37A210 $37A218 Fifth Acc-24E2x, first IC on third Acc-24P/V2
7 $37A300 $37A308 $37A310 $37A318 Sixth Acc-24E2x, second IC on third Acc-24P/V2
8 $37B200 $37B208 $37B210 $37B218 Seventh Acc-24E2x, first IC on fourth Acc-24P/V2
9 $37B300 $37B308 $37B310 $37B318 Eighth Acc-24E2x, second IC on fourth Acc-24P/V2
The second line in an MLDT entry should be $013000 to specify the use of 19 bits ($013) starting at bit 0
($000).
The third line in an MLDT entry should contain a number slightly greater than the maximum velocity
ever expected, expressed as timer increments per servo cycle. An increment of the 120 MHz timer
represents about 0.024mm (0.0009 in) on a typical MLDT device. This value represents the maximum
change in position reading that will be passed through the conversion table in a single servo cycle, and it
provides an important protection against missing or spurious echo pulses.
Time-Base Entries ($4, $9, $A, $B): A time-base entry performs a scaled digital differentiation of the
value in the source register. It is most often used to perform electronic cam functions, slaving a motion
sequence to the frequency of a master encoder. There are two types of time-base entries: “untriggered”
and triggered. An untriggered time base does not provide a specific starting point in the master source
data. A triggered time base starts the differentiation upon receipt of a hardware trigger on the master
encoder’s channel, referenced to the position captured by that trigger. This can be used to create an
absolute synchronization between the master position and the slave trajectory.
Time-base entries are two-line entries. The first setup line (I-variable) contains the method digit and the
address of the source-data register. The second setup line (I-variable) contains the time-base scale factor.
The first result line contains the intermediate result value of the source data, saved for the next cycle to be
able to compute the differentiation. The second result line contains the final result, which is the
differentiated value. Most commonly this result is used as the time-base source for a coordinate system,
so Isx93 for the coordinate system points to this second line.
Untriggered Time Base ($4): In an untriggered time-base entry, the first setup line (I-variable) contains a
4 in the method digit (bits 20 – 23) and the address of the source register in bits 0 – 18. The source
register is usually the result register of an incremental encoder entry (e.g. 1/T) higher in the table
(addresses $3501 to $35C0). Refer to the table above, which lists the addresses of each line in the
encoder conversion table. For example, to use the result of the fourth line of the conversion table as a
source, this I-variable would be $403504.
The second setup line (I-variable) is the “time-base scale factor” which multiplies the differentiated
source value. The final result value equals 2 * Time-Base-Scale-Factor * (New Source Value - Old
Source Value).
Typically, New Source Value and Old Source Value (stored from the previous servo cycle) are in units of
1/32 of a count, the usual scaling of a 1/T encoder conversion result.
When this time base entry is used to calculate a frequency-based time base for a coordinate system, the
TBSF should be set to 217/Real-Time Input Frequency (131,072/RTIF), where the Real-Time Input
Frequency (RTIF) in counts per millisecond, is the frequency at which motion trajectories using this time
base will execute at the programmed speed or in the programmed time. The motion sequence to be slaved
to this frequency should be written assuming that the master is always generating this real-time input
frequency (so always moving at the real-time speed). The true speed of trajectories using this time base
will vary proportionately with the actual input frequency.
Example:
The application requires the use of Encoder 4 on board a Turbo PMAC2 as an untriggered time-base
master for Coordinate System 1. The real-time input frequency is selected as 256 counts/msec. The
conversion table starts with eight single-line entries in I8000 – I8007, with the 4th line (I8003) doing a 1/T
conversion of Encoder 4.
Setup On-line Commands
I8003=$078018 ; 1/T conversion of Encoder 4
I8008=$403504 ; Unriggered time base from 1/T encoder
I8009=512 ; TBSF=131072/256
I5193=@I8009 ; C.S.1 use I8009 result for time base
Triggered Time Base ($9, $A, $B): A triggered time-base entry is like a regular untriggered time-base
entry, except that it is easy to freeze the time base, then start it exactly on receipt of a trigger that captures
the starting master position or time.
In a triggered time-base entry, the first setup line (I-variable) contains a 9 A or B in the method digit (bits
20 – 23), depending on its present state. It contains the address of the source register in bits 0 – 18. The
source register for triggered time base must be the starting (X) address for one of the machine interface
channels of a Servo IC. The bit 19 mode switch must be set to 0 if a PMAC-style Servo IC (DSPGATE)
is addressed; it must be set to 1 if a PMAC2-style Servo or MACRO IC (DSPGATE1 or DSPGATE2) is
addressed. Note that setting bit 19 to 1 changes the second hex digit of the I-variable from 7 to F.
The second setup line (I-variable) is the time-base scale factor which multiplies the differentiated source
value. The final result value (when running) equals 512 * Time-Base-Scale-Factor * (New Source Count
- Old Source Count). New Source Count and Old Source Count are the values of the addressed encoder
counter, in counts.
When this time-base entry is used to calculate a frequency-based time base for a coordinate system, the
TBSF should be set to 214/Real-Time Input Frequency (16,384/RTIF), where the Real-Time Input
Frequency (RTIF) in counts per millisecond, is the frequency at which motion trajectories using this time
base will execute at the programmed speed or in the programmed time. (Note that the TBSF is 1/8 of the
value for an untriggered time base, because the triggered time base creates an extra 3 bits [8x] of
fractional information with its 1/T extension.) The motion sequence to be slaved to this frequency should
be written assuming that the master is always generating this real-time input frequency (so always moving
at the real-time speed). The true speed of trajectories using this time base will vary proportionately with
the actual input frequency.
A triggered time-base entry in Turbo PMAC automatically computes the 1/T count extension of the input
frequency itself before the differentiation. It computes this to 1/256 of a count. This is compared to the
1/32 of a count that the separate 1/T encoder extension uses.
The extra fractional information can reduce the quantization noise created by the differentiation and
provide smoother operation under external time base.
Note:
The intermediate result in the first line of a triggered time-base entry contains the
undifferentiated 1/T extension of the source encoder position, in units of 1/256 of a
count. This value can be used as feedback data or master position data, with more
resolution than the standard 1/T extension.
In use, the method digit (comprising bits 20-23 of the first line) is changed as needed by setting of the I-
variable. Triggered time base has three states, frozen, armed, and running, all of which must be used to
utilize the triggering feature.
First, the method digit is set to $9 (e.g. I8010=$978008) before the calculations of the triggered move are
started, to freeze the time base (and therefore the motion) while the move calculations are done. This is
typically done in the user’s motion program. When this entry is in the frozen state, the table reads the
channel’s capture position register each servo cycle to ensure the triggering logic is reset for the next
capture. The final result of the entry is always 0 when frozen.
Note:
In a Turbo PMAC application with a light computational load, it is possible that
the entry will not be in the frozen state during a servo interrupt, and the table will
not get a chance to reset the trigger logic. Therefore, it is advisable to reset the
triggering logic explicitly in the user program with a dummy read of the channel’s
captured position register, which is the X-register with an address 3 greater than
the address specified in the entry (e.g. X:$07800B if the entry specifies $078008).
The suggested M-variable for the captured position register is Mxx03.
Next, the method digit is set to $B (e.g. I8010=$B78008) after the calculations of the triggered move are
finished, to arm the time base for the trigger. Typically, this is done in a PLC program that looks to see if
the entry is frozen and changes it to the armed state. The final result of the entry is always 0 when armed.
In the armed state, the Table checks every servo cycle for the channel’s trigger bit to be set. When the
Table sees the trigger (the capture trigger for the machine interface channel as defined by I7mn2 and
I7mn3 for Servo IC m Channel n, or by I68n2 and I68n3 for MACRO IC 0 Channel n), it sets the method
digit to $A for running time base automatically. It uses the position captured by the trigger as the starting
position (time zero) for the running time base. (Those using this method for the reduced quantization
noise may simply leave the method digit at $A.)
The following tables show the possible first-line entries for triggered time base (running mode):
Low-Pass Filter Entries ($D): The $D entry is used to create one of two types of low-pass filters on a
word of input data to provide smoothing of noisy measurements. The two types of filter are distinguished
by bit 19 of the first setup line of the entry. If the bit-19 mode-switch bit is 0, typically making the
second hex digit $0, the filter is a simple exponential filter. If the bit-19 mode-switch bit is 1, typically
making the second hex digit $8, the filter is a more sophisticated tracking filter that includes an integrator
to eliminate steady-state errors.
The simpler exponential filter, which is a three-line entry in the table, is suitable for the smoothing of
noisy master data used for electronic gearing (position following) or electronic cams (external time base).
However, it will produce lags even in the steady state (e.g. at constant velocity), so it is usually not
suitable for smoothing servo feedback data because of the delays it introduces.
The more complex tracking filter, which is a five-line entry in the table, is suitable for smoothing either
master data or feedback data, because its integrator eliminates steady-state errors. Still, its filtering can
introduce delays in responding to dynamic changes (e.g. accelerations), so it needs to be set up carefully.
This software tracking filter is dynamically equivalent to the hardware tracking filters common in
resolver-to-digital converter ICs. It is commonly used to smooth the results of direct conversion of
sinusoidal encoders.
Warning: Attempting to enter a tracking filter into a Turbo PMAC with firmware that does not support it
(V1.940 or older) will result in disturbing or disabling any subsequent entries in the table as well as the
filter entry.
Exponential Filter ($Dxxxxx, bit 19 = 0)
The equation of the exponential filter executed every servo cycle n is:
If [In(n) - In(n-1)] > Max_change, In(n) = In(n-1) + Max_change
If [In(n) - In(n-1)] < -Max_change, In(n) = In(n-1) - Max_change
Out(n) = Out(n-1) + (K/223)*[In(n)-Out(n-1)]
In, Out, and K are all signed 24-bit numbers (range -8,388,608 to 8,388,607). The difference [In(n)-
Out(n-1)] is truncated to 24 bits to handle rollover properly.
The time constant of the filter, in servo cycles, is (2 23/K)-1. The lower the value of K, the longer the time
constant.
No shifting action is performed. Any operations such as 1/T interpolation should have been done on the
data already, so the source register for this filter is typically the result register of the previous operation in
the conversion table.
Method/Address Word: The first setup line (I-variable) of an exponential filter entry contains a ‘D’ in the
first hex digit (bits 20 – 23), a ‘0’ in bit 19, and the address of the source X-register in bits 0 – 18. If it is
desired to execute an exponential filter on the contents of a Y-register, the contents of the Y-register must
first be copied to an X-register in the conversion table with a “parallel” entry ($2) higher in the table. The
source addresses for exponential filter entries are almost always from the conversion table itself
(X:$003501 – X:$0035BC). Since bits 16 – 18 of conversion table registers are 0, this makes the entire
second hex digit of this line ‘0’. For example, to perform an exponential filter on the result of the fourth
line of the table, the first setup line of the filter entry would be $D03504.
Maximum Change Word: The second setup line (I-variable) of an exponential filter entry contains the
value “max change” that limits how much the entry can change in one servo cycle. The units of this entry
are whatever the units of the input register are, typically 1/32 of a count. For example, to limit the change
in one servo cycle to 64 counts with an input register in units of 1/32 count, this third line would be 64*32
= 2048.
Filter Gain Word: The third setup line (I-variable) of an exponential filter entry contains the filter gain
value K, which sets a filter time constant Tf of (223/K)-1 servo cycles. Therefore, the gain value K can be
set as 223/(Tf+1). For example, to set a filter time constant of 7 servo cycles, the filter gain word would be
8,388,608/(7+1) = 1,048,576.
Result Word: The output value of the exponential filter is placed in the X register of the third line of the
conversion table entry. An operation that uses this value should address this third register; for example
Ixx05 for position following, or the source address for a time-base conversion-table entry (to keep
position lock in time base, this filter must be executed before the time-base differentiation, not afterward).
Tracking Filter ($Dxxxxx, bit 19 = 1)
For the tracking filter, the equation of the filter every servo cycle n is:
If [In(n) - In(n-1)] > Max_change, In(n) = In(n-1) + Max_change
If [In(n) - In(n-1)] < -Max_change, In(n) = In(n-1) - Max_change
Err(n) = In(n) – Out(n-1)
Temp1 = (Kp/223) * Err(n)
Int(n) = Int(n-1) + (Ki/223) * Err(n)
Out(n) = Out(n-1) + Temp1 + Int(n)
In, Out, Kp and Ki are all signed 24-bit numbers (range -8,388,608 to 8,388,607). The difference [In(n)-
Out(n-1)] is truncated to 24 bits to handle rollover properly.
The time constant of the filter, in servo cycles, is (2 23/Kp)-1. The lower the value of Kp, the longer the
time constant.
No shifting action is performed. Any operations such as 1/T interpolation should have been done on the
data already, so the source register for this filter is typically the result register of the previous operation in
the conversion table.
Method/Address Word: The first setup line (I-variable) of a tracking filter entry contains a ‘D’ in the first
hex digit (bits 20 – 23), a 1 in the bit-19 mode-switch bit, and the address of the source X-register in bits
0 – 18. If it is desired to execute a tracking filter on the contents of a Y-register, the contents of the Y-
register must first be copied to an X-register in the conversion table with a “parallel” entry ($2) higher in
the table. The source addresses for tracking filter entries are almost always from the conversion table
itself (X:$003501 – X:$0035BC). Since bits 16 – 18 of conversion table registers are 0, this makes the
entire second hex digit of this line ‘8’. For example, to perform an tracking filter on the result of the
fourth line of the table, the first setup line of the filter entry would be $D83504.
Maximum Change Word: The second setup line (I-variable) of a tracking filter entry contains the value
“max change” that limits how much the entry can change in one servo cycle. The units of this entry are
whatever the units of the input register are, typically 1/32 of a count. For example, to limit the change in
one servo cycle to 64 counts with an input register in units of 1/32 count, this third line would be 64*32 =
2048.
Filter Proportional Gain Word: The third setup line (I-variable) of a tracking filter entry contains the
filter proportional gain value Kp, which sets a filter time constant Tf of (223/Kp)-1 servo cycles. Therefore,
the proportional gain value Kp can be set as 223/(Tf+1). For example, to set a filter time constant of 7
servo cycles, the filter proportional gain word would be 8,388,608/(7+1) = 1,048,576.
Reserved Setup Word: The fourth setup line (I-variable) of a tracking filter entry is reserved for future use.
It is not presently used, and can be set to 0.
Filter Integral Gain Word: The fifth setup line (I-variable) of a tracking filter entry contains the filter
integral gain value Ki, which determines how quickly the integrated error contributes to the filter output.
Each servo cycle, the amount (Ki/223) * Err(n) is added to the integrator and to the filter output.
Result Word: The output value of the tracking filter is placed in the X-register of the fifth line of the
conversion table entry. An operation that uses this value should address this fifth register; for example
Ixx03 for position-loop feedback, or the source address for a time-base conversion-table entry (to keep
position lock in time base, this filter must be executed before the time-base differentiation, not afterward).
Addition/Subtraction of Entries ($E): The $E entry is used to add the results of two other entries in the
Table, possibly after negating one or both of them (which can effectively create subtraction), with the
option of integrating the sum. It is a single-line entry.
Control Digit: The second hex digit of the I-variable consists of four independent control bits (bits 19-16)
and determines whether the result is integrated or not, whether a second source entry is used or not, and
whether each of the source entries is negated before addition or not.
If the bit 19 mode switch bit is 0, which makes the second hex digit 0, the values in the two specified
entries are simply added. If the mode switch bit 19 is 1, the sum of the two entries.
If bit 18 is set to 1, the second entry to be added (as specified by bits 8-15) is not used. This permits easy
negation (change in sign) of a single entry. If bit 18 is set to 0, the second entry is used.
If bit 17 is set to 1, the second entry to be added (as specified by bits 8-15) is negated before the addition,
which means that it is effectively subtracted from the first entry. If bit 17 is not set to 1, the second entry
to be added is not negated.
If bit 16 is set to 1, the first entry to be added (as specified by bits 0-7) is negated before the addition,
which means that it is effectively subtracted. If bit 16 is not set to 1, the first entry to be added is not
negated.
Second Source Offset: Bits 8-15, which form the third and fourth hex digits of the entry, specify the
offset from the beginning of the table to the second entry to be used used, as an unsigned 8-bit quantity.
The value in these digits should equal the number of the I-variable matching the second entry minus 8000.
First Source Offset: Bits 0-7, which form the fifth and sixth hex digits of the entry, specify the address
offset from the beginning of the table to the first entry to be used, as an unsigned 8-bit quantity. The
value in these digits should equal the number of the I-variable matching the first entry minus 8000.
Examples:
To add the results of the first two lines in the table, from I8000 and I8001, the I-variable would be
$E00100. The E specifies addition, the 0 specifies no integration, using the second source, and no
negation of either source. The 01 specifies the second line of the table (matching I8001) as the second
source, and the final 00 specifies the first line of the table (matching I8000) as the first source.
To subtract the result of the second line (from I8001) of the table from that of the first line (from I8000),
the I-variable would be $E20100. The E specifies addition, the 2 (0010 binary) specifies no integration,
using the second source, negating the second source, but not the first source. The 01 specifies the second
line of the table (matching I8001) as the second source, and the final ‘00’ specifies the first line of the
table (matching I8000) as the first source.
To invert the 20th line of the table (from I8019), the I-variable would be $E50013. The E specifies
addition, the 5 (0101 binary) specifies no integration, not using the second source, and negating the first
source. The 00 is not important, because the second source is not used. The 13 (19 decimal) specifies the
result matching I8019 as the first source.
Extended Entries ($F): Encoder conversion table entries in which the first hex digit of the first line is
$F are extended entries. In these entries, the actual method is dependent on the first digit of the second
line. Extended entries are a minimum of two lines.
High-Resolution Interpolator Entries ($F/$0): An ECT entry in which the first hex digit of the first line
is $F and the first hex digit of the second line is $0 processes the result of a high-resolution interpolator
for analog “sine-wave” encoders, such as the ACC-51. This entry, when used with a high-resolution
interpolator, produces a value with 4096 states per line. The entry must read both an encoder channel for
the whole number of lines of the encoder, and a pair of A/D converters to determine the location within
the line, mathematically combining the values to produce a single position value.
Encoder Channel Address: The first line of the three-line entry contains $F in the first hex digit and the
base address of the encoder channel to be read in the low 19 bits (bits 0 to 18). If the bit-19 mode switch
of the line is set to 0, Turbo PMAC expects a PMAC(1)-style Servo IC on the interpolator, as in the ACC-
51P. If the bit-19 mode switch bit is set to1, Turbo PMAC expects a PMAC2-style Servo IC on the
interpolator, as in the ACC-51E, 51C, and 51P2.
The following table shows the possible entries when PMAC(1)-style Servo ICs are used, as in the ACC-
51P.
High-Res Interpolator Entry First Lines for PMAC(1)-Style Servo ICs
Servo IC # Channel 1 Channel 2 Channel 3 Channel 4
2 $F78200 $F78204 $F78208 $F7820C
3 $F78300 $F78304 $F78308 $F7830C
4 $F79200 $F79204 $F79208 $F7920C
5 $F79300 $F79304 $F79308 $F7930C
6 $F7A200 $F7A204 $F7A208 $F7A20C
7 $F7A300 $F7A304 $F7A308 $F7A30C
8 $F7B200 $F7B204 $F7B208 $F7B20C
9 $F7B300 $F7B304 $F7B308 $F7B30C
The following table shows the possible entries when PMAC2-style Servo ICs are used, as in the ACC-
51E, 51C, or 51P2:
High-Res Interpolator Entry First Lines for PMAC2-Style Servo ICs
Servo IC # Channel 1 Channel 2 Channel 3 Channel 4
2 $FF8200 $FF8208 $FF8210 $FF8218
3 $FF8300 $FF8308 $FF8310 $FF8318
4 $FF9200 $FF9208 $FF9210 $FF9218
5 $FF9300 $FF9308 $FF9310 $FF9318
6 $FFA200 $FFA208 $FFA210 $FFA218
7 $FFA300 $FFA308 $FFA310 $FFA318
8 $FFB200 $FFB208 $FFB210 $FFB218
9 $FFB300 $FFB308 $FFB310 $FFB318
Note that by setting the bit-19 mode switch to 1, the second hex digit changes from “7” to “F”.
A/D Converter Address: The second setup line (I-variable) of the entry contains $0 in the first hex digit
and the base address of the first of two A/D converters to be read in the low 19 bits (bits 0 to 18). The
second A/D converter will be read at the next higher address. The following table shows the possible
entries when the ACC-51P, with PMAC(1) style Servo ICs, is used:
High-Res Interpolator Entry Second Lines for PMAC(1)-Style Servo ICs
Servo IC # Channel 1 Channel 2 Channel 3 Channel 4
2 $078202 $078206 $07820A $07820E
3 $078302 $078306 $07830A $07830E
4 $079202 $079206 $07920A $07920E
5 $079302 $079306 $07930A $07930E
6 $07A202 $07A206 $07A20A $07A20E
7 $07A302 $07A306 $07A30A $07A30E
8 $07B202 $07B206 $07B20A $07B20E
9 $07B302 $07B306 $07B30A $07B30E
The following table shows the possible entries when PMAC2-style Servo ICs are used, as in the ACC-
51E, 51C, or 51P2:
High-Res Interpolator Entry Second Lines for PMAC2-Style Servo ICs
Servo IC # Channel 1 Channel 2 Channel 3 Channel 4
2 $078205 $07820D $078215 $07821D
3 $078305 $07830D $078315 $07831D
4 $079205 $07920D $079215 $07921D
5 $079305 $07930D $079315 $07931D
6 $07A205 $07A20D $07A215 $07A21D
7 $07A305 $07A30D $07A315 $07A31D
8 $07B205 $07B20D $07B215 $07B21D
9 $07B305 $07B30D $07B315 $07B31D
Sine/Cosine Bias Word: The third setup line (I-variable) in a high-resolution sinusoidal-encoder
conversion feedback entry contains bias-correction terms for the sine and cosine ADC values. The high
twelve bits (the first three hex digits) contain the bias-correction term for the sine input; the low twelve
bits (the last three hex digits) contain the bias-correction term for the cosine input. Each 12-bit section
should be treated as a signed 12-bit value (so if the most significant of the 12 bits is a 1, the bias value is
negative).
Each 12-bit bias-correction term should contain the value opposite that which the high 12 bits of the
matching A/D converter report when they should ideally report zero. In action, the bias term will be
added to the high 12 bits of the corresponding ADC reading before subsequent calculations are done.
For example, if the bias-correction word were set to $004FFA, the sine bias correction would be +4 LSBs
of a 12-bit ADC, and the cosine bias correction would be -6 LSBs ($FFA = -6) of a 12-bit ADC. In use, 4
12-bit LSBs would be added to the sine reading, and 6 12-bit LSBs would be subtracted from the cosine
reading each cycle before further processing.
In most cases, the bias-correction word will be determined automatically by a high-resolution
“diagnostic” entry (format $F/$1) in the conversion table. The result of that diagnostic entry, containing
both bias corrections, can simply be copied into this setup word.
Note: In firmware revisions 1.940 and older, the bias word contained a single 24-bit bias term that was
added to both the sine and the cosine terms.
Conversion Result: The result of the conversion is placed in the X-register of the third line of the entry.
Careful attention must be paid to the scaling of this 24-bit result. The least significant bit (Bit 0) of the
result represents 1/4096 of a line of the sine/cosine encoder.
When Turbo PMAC software reads this data for servo use with Ixx03, Ixx04, Ixx05, or Isx93, it expects
to find data in units of 1/32 of a “count”. Therefore, PMAC software regards this format as producing
128 “counts” per line. (The fact that the hardware counter used produces 4 counts per line is not relevant
to the actual use of this format; this fact would only be used when reading the actual hardware counter for
commutation or debugging purposes.)
Example: This format is used to interpolate a linear scale with a 40-micron pitch (40m/line), producing a
resolution of about 10 nanometers (40,000/4096), used as position feedback for a motor. PMAC
considers a “count” to be 1/128 of a line, yielding a count length of 40/128 = 0.3125 m. To set user
units of millimeters for the axis, the axis scale factor would be:
High-Resolution Interpolation Diagnostic Entry ($F/$1): An ECT entry in which the first hex digit of
the first line is $F and the first hex digit of the second line is $1 produces either vector magnitude or
analog-input bias terms for the sine and cosine inputs of a sinusoidal encoder or resolver. This is a five-
line entry. These result values can be used to verify proper setup and interface of the encoder and to
optimize the accuracy of the conversion during initial setup, and/or to check for loss of the encoder during
the actual application. Bit 0 of the second setup line determines whether the result produced is the sum of
the squares of the two analog inputs (bit 0 = 0) or the bias terms for the analog inputs (bit 0 = 1).
Method/Address Setup Word: The first setup line (I-variable) of the five-line entry contains $F in the first
hex digit, and the address of the first of the two A/D converters in the low 19 bits (bits 0 – 18). The
second A/D converter will be read at the next higher address.
The following table shows the possible entries when the ACC-51P, with PMAC(1) style Servo ICs, is
used:
High-Res Interpolator Diagnostic Entry First Lines for PMAC(1)-Style Servo ICs
Servo IC # Channel 1 Channel 2 Channel 3 Channel 4
2 $F78202 $F78206 $F7820A $F7820E
3 $F78302 $F78306 $F7830A $F7830E
4 $F79202 $F79206 $F7920A $F7920E
5 $F79302 $F79306 $F7930A $F7930E
6 $F7A202 $F7A206 $F7A20A $F7A20E
7 $F7A302 $F7A306 $F7A30A $F7A30E
8 $F7B202 $F7B206 $F7B20A $F7B20E
9 $F7B302 $F7B306 $F7B30A $F7B30E
The following table shows the possible entries when PMAC2-style Servo ICs are used, as in the ACC-
51E, 51C, or 51P2:
High-Res Interpolator Diagnostic Entry First Lines for PMAC2-Style Servo ICs
Servo IC # Channel 1 Channel 2 Channel 3 Channel 4
2 $F78205 $F7820D $F78215 $F7821D
3 $F78305 $F7830D $F78315 $F7831D
4 $F79205 $F7920D $F79215 $F7921D
5 $F79305 $F7930D $F79315 $F7931D
6 $F7A205 $F7A20D $F7A215 $F7A21D
7 $F7A305 $F7A30D $F7A315 $F7A31D
8 $F7B205 $F7B20D $F7B215 $F7B21D
9 $F7B305 $F7B30D $F7B315 $F7B31D
Diagnostic Mode Setup Word: The second setup line (I-variable) of the five-line entry contains $1 in the
first hex digit and $0000 in the second through fifth hex digits. Bits 0 and 1 in the sixth hex digit control
the diagnostic mode (bits 2 and 3 should be left at 0). If bit 0 is set to 0 (making the word $100000), the
entry computes the sum of squares of the sine and cosine ADCs, permitting monitoring of the vector
magnitude of the inputs.
If bit 0 is set to 1, the entry computes the bias in the sine and cosine terms as the negative of average of
the maximum positive and maximum negative values found for each term. Each cycle it checks the
present readings against the logged maximum and minimum values, changing these values if necessary,
then computing the averages and the resulting bias word. If bit 1 is set to 0, the maximum and minimum
values are cleared. This setting (second setup word set to $100001) is used to start a test to determine the
bias compensation word. As soon as Turbo PMAC starts accumulating maximum and minimum values
(the next servo cycle), bit 1 is set to 1, making this second setup word equal to $100003. If you want to
start a new test, for example after a circuit adjustment, you must set bit 1 to 0 again by setting this setup
word back to $100001.
Active Bias Correction Setup Word: The third setup line (I-variable) of the five-line entry contains the
sine and cosine bias terms that are used in the sum-of-squares calculations. Two signed 12-bit bias terms
are combined in a 24-bit word. The sine bias-correction term is in the high 12 bits (bits 12 – 23); the
cosine bias-correction term is in the low 12 bits (bits 0 – 11). These terms match the high 12 bits from the
corresponding A/D converters. This word does not necessarily match the bias “result” term derived from
using this entry to determine a suggested bias correction, or the bias correction used in the “feedback”
table entry for the encoder or resolver.
Reserved Setup Words: The fourth and fifth setup lines of this entry type are reserved for future use, and
should be left at 0.
Result Word (Sum of Squares): When bit 0 of the second setup line is 0, the final (fifth) result word
contains the sum of squares of the biased sine and cosine measurements for the most recent servo cycle.
Result = (SineADC + SineBias)2 + (Cosine ADC + CosineBias)2
The values SineADC and CosineADC are read from the A/D converters at the address specified in the first
setup line. The values SineBias and CosineBias are read from the third setup line.
To understand the scaling of the result word, it is best to think of all four of the values as being
normalized, that is, having a valid range of -1.0 to +1.0. With small bias terms, the sum of squares result
would have a possible normalized value of 0.0 to +2.0. When read as an unsigned integer, this register
has a range of 0 to 16,777,215 ($FFFFFFF), corresponding to a normalized range of 0.0 to 2.0.
When the encoder and interpolator circuitry, or the resolver and excitation circuitry, are working properly,
the sum of squares should have a normalized value of +0.25 to +0.9999 (2,097,152 to 8,388,607, or
$200000 to $7FFFFF). If the resulting normalized value is greater than or equal to +1.0 (8,388,608, or
$800000), meaning that the most significant bit (bit 23) is set to 1, at any point in the cycle, this indicates
that saturation has occurred in at least one of the readings due to either too large a signal or a significant
bias. This should be corrected before using this sensor in actual operation.
If the result has a normalized value of less than +0.25 (2,097,152, or $200000), meaning that bits 23, 22,
and 21 are all 0, at low sensor frequencies, the signals are too small to get full resolution from the result,
and this should be corrected before using this sensor in actual operation. Many sinusoidal encoders do
have a reduction in signal magnitude of up to one-half at their highest frequencies, reducing the
magnitude of this square term by three-quarters, and this is acceptable.
It is possible to monitor this term in the actual application to check for loss of the encoder. If the inputs
are no longer driven externally, for example because the cable has come undone, the positive and negative
input pair to the ADC will pull to substantially the same voltage, and the output of the ADC will be a very
small number, resulting in a small magnitude of the sum of squares in at least part of the cycle. (If both
signals cease to be driven externally, the sum of squares will be small over the entire cycle). The high
four bits (bits 20 – 23) of the sum-of-squares result can be monitored, and if the four-bit value goes to 0, it
can be concluded that the encoder has been “lost”, and the motor should be “killed”.
Ideally, the magnitude of the sum-of-squares result should be constant throughout the sine/cosine cycle, at
least at constant frequency. If there is significant variation, this is an indication of signal imperfection. In
most cases, the most important imperfection is a DC bias on the sine and/or cosine signals. This entry can
be used in its alternate format to determine the optimal bias correction. Once that bias correction has
been determined (the result word in that format), it can be copied into the active correction setup word for
the diagnostic entry, and the entry put back into sum-of-squares mode, as an important verification that a
good bias correction has been determined.
A/D Bias Result Word: When bit 0 of the second setup line is 1, the final (fifth) result word contains the
suggested bias correction word containing the bias correction terms for the sine and cosine terms. This
24-bit value, containing two signed 12-bit correction terms, can be copied into the third setup word for the
interpolator diagnostic entry for confirmation of its effect, and to the third line of the interpolator
feedback entry, or the resolver feedback entry, for actual use. The sine bias-correction term is in the high
12 bits (bits 12 – 23); the cosine bias-correction term is in the low 12 bits (bits 0 – 11).
In this mode, the encoder should be moved for several seconds (motion by hand is OK) to ensure good
sampling of maximums and minimums of both waveforms and accurate bias-correction terms. It is
probably best to do this test with the amplifier disabled to prevent the possibility of noise distorting the
maximum and minimum readings.
Byte-Wide Parallel Feedback Entries ($F/$2, $F/$3): An ECT entry in which the first hex digit of the
first line is $F and the first hex digit of the second line is $2 or $3 processes the result of a parallel data
feedback source whose data is in byte-wide pieces in consecutive Y-words. This is used to process
feedback from 3U-format parallel-data I/O boards: the Acc-3E in stack form, and the Acc-14E in pack
(UMAC) form.
Address Word: The first setup line (I-variable) of the entry contains $F in the first hex digit (bits 20-23).
The bit-19 mode-switch bit in the first line controls whether the least significant bit (LSB) of the source
register is placed in bit 5 of the result register (normal shift), providing the standard 5 bits of (non-existent)
fraction, or the LSB is placed in Bit 0 of the result register (unshifted), creating no fractional bits.
Normally, the Bit-19 mode switch is set to 0 to place the source LSB in Bit 5 of the result register. Bit 19
is set to 1 to place to source LSB in Bit 0 of the result register for one of three reasons:
The data already comes with five bits of fraction, as from a Compact MACRO Station.
The normal shift limits the maximum velocity too much (Vmax<218 LSBs per servo cycle)
The normal shift limits the position range too much (Range<+247/Ix08/32 LSBs)
Unless this is done because the data already contains fractional information, the unshifted conversion will
mean that the motor position loop will consider one LSB of the source to be 1/32 of a count, instead of one
count.
Bits 0 to 18 of the first line contain the base address of the parallel data to be read. This is the address of
the least significant byte in the parallel feedback word. The following table shows the possible entries
when an Acc-3E stack I/O board is used:
Entry First Lines for Acc-3E 3U-Stack I/O Boards
Acc-3E Address Jumper E1 E2 E3 E4
First-Line Value $F7880x $F7890x $F78A0x $F78B0x
The following table shows the possible entries when the Acc-14E UMAC I/O board is used:
Entry First Lines for Acc-14E UMAC I/O Boards
DIP-Switch SW1-1 ON (0) SW1-1 OFF (1) SW1-1 ON (0) SW1-1 OFF (1)
Setting SW1-2 ON (0) SW1-2 ON (0) SW1-2 OFF (1) SW1-2 OFF (1)
SW1-3 ON (0) $F78C0x $F78D0x $F78E0x $F78F0x
SW1-4 ON (0)
SW1-3 OFF (1) $F79C0x $F79D0x $F79E0x $F79F0x
SW1-4 ON (0)
SW1-3 ON (0) $F7AC0x $F7AD0x $F7AE0x $F7AF0x
SW1-4 OFF (1)
SW1-3 OFF (1) $F7BC0x $F7BD0x $F7BE0x $F7BF0x
SW1-4 OFF (1)
A switch that is ON is CLOSED; a switch that is OFF is OPEN.
In both of these tables, the second digit should be changed from a 7 to an F if bit 19 is set to 1 to disable
the data shift.
The final digit, represented by an x in both of these tables, can take a value of 0 to 5, depending on which
I/O point on the board is used for the LSB:
x=0: I/O00-07 I/O48-55 I/O96-103
x=1: I/O08-15 I/O56-63 I/O104-111
x=2: I/O16-23 I/O64-71 I/O112-119
x=3: I/O24-31 I/O72-79 I/O120-127
x=4: I/O32-39 I/O80-87 I/O128-135
x=5: I/O40-47 I/O88-95 I/O136-143
Width/Offset Word: The second setup line (I-variable) of this parallel read entry contains information
about what data is to be read starting at the base address. This 24-bit value, usually represented as 6
hexadecimal digits, is split into four parts, as shown in the following table.
Hex Digit 1 2 3 4 5 6
Contents 2 or 3 Bit Width Byte LSB Location
The first hex digit contains a 2 or a 3. If it has a 2, there is no filtering of the data, and the entry is a 2-line
entry. If it has a 3, the input data is filtered to protect against noise or data corruption, and the entry is a
3-line entry, with the third line controlling the filtering.
The second and third digits represent the width of the parallel data in bits, and can range from $01 (1 bit
wide – not of much practical use) to $18 (24 bits wide). If the value of these digits is from $01 to $08,
only the base address in the first line is used. If the value of these digits is from $09 to $10 (16), the base
address and the next higher-numbered address are used. If the value of these digits is from $11 to $18 (17
to 24), three addresses starting at the base address are used.
The fourth digit represents which byte of the source words is used. It has three valid values:
0: Low byte (bits 0 – 7)
1: Middle byte (bits 8 – 15)
2: High byte (bits 16 – 23)
The fifth and sixth digits contain the bit location of the LSB of the data in the source word at the base
address, and can range from $00 (Bit 0 of the source address is the LSB), through $07 (Bit 7 of the source
address is the LSB). To calculate this value, divide the number of the I/O point used for the LSB by 8
and use the remainder here. For example, if I/O19 is used for the LSB, the remainder of 19/16 is 3.
Maximum Change Word: If the method character for a parallel read is $3 or $7, specifying filtered
parallel read, there is a third setup line (I-variable) for the entry. This third line contains the maximum
change in the source data in a single cycle that will be reflected in the processed result, expressed in LSBs
per servo cycle. The filtering that this creates provides an important protection against noise and
misreading of data. This number is effectively a velocity value, and should be set slightly greater than the
maximum true velocity ever expected.
Resolver Conversion Entry ($F/$4): An ECT entry in which the first hex digit of the first line is $F and
the first hex digit of the second line is $4 converts the result of a pair of resolver sine/cosine A/D
converters (ADCs) to a resolver angle value with 14-bit resolution.
The $E entry converts the sine and cosine resolver feedback values processed through the Geo PMAC’s
A/D converter (ADC) registers to a 14-bit resolver angle value.
Method/Address Word: The first setup line of a resolver conversion entry contains $F in the first hex digit
and the Y-address of the first ADC register to be read in the low 19 bits (bits 0 – 18). The next ADC
register is read at the next higher Y-address. If bit 19 of the line is set to 0, the conversion creates a
“clockwise” rotation sense. If bit 19 of the line is set to 1, the conversion creates a “counter-clockwise”
rotation sense.
For example, if the first ADC register is at Y:$078C00, the first line would be set to $F78C00 for a
clockwise rotation sense, or to $FF8C00 for a counterclockwise rotation sense.
Excitation Address Setup Word: The second setup line in a resolver conversion entry contains $4 in the
first hex digit, and the Y-address of the excitation value register in the low 19 bits (bits 0 – 18), used to
correlate the excitation and the feedback values. Multiple resolver channels can use the same excitation
register. For example, if the excitation address is at Y:$078C10, the second setup line would be set to
$478C10
Sine/Cosine Bias Setup Word: The third setup line in a resolver conversion entry contains bias-correction
terms for the sine and cosine ADC values. The high twelve bits (the first three hex digits) contain the
bias-correction term for the sine input; the low twelve bits (the last three hex digits) contain the bias-
correction term for the cosine input. Each 12-bit section should be treated as a signed 12-bit value (so if
the most significant of the 12 bits is a 1, the bias value is negative).
Each 12-bit bias-correction term should contain the value opposite that which the high 12 bits of the
matching A/D converter report when they should ideally report zero. In action, the bias term will be
added to the high 12 bits of the corresponding ADC reading before subsequent calculations are done.
In most cases, the bias-correction word will be determined automatically by a high-resolution
“diagnostic” entry (format $F/$1) in the conversion table. The result of that diagnostic entry, containing
both bias corrections, can simply be copied into this setup word.
For example, if the bias-correction word were set to $004FFA, the sine bias correction would be +4 LSBs
of a 12-bit ADC, and the cosine bias correction would be -6 LSBs ($FFA = -6) of a 12-bit ADC. In use, 4
12-bit LSBs would be added to the sine reading, and 6 12-bit LSBs would be subtracted from the cosine
reading each cycle before further processing.
In most cases, the bias-correction word will be determined automatically by an analog “diagnostic” entry
in the conversion table (method $F/$1). The result of that diagnostic entry, containing both bias
corrections, can simply be copied into this setup word.
Result Word: The output value of the resolver conversion is placed in the 24-bit X-register of the third
line of the conversion table entry. The values in bits 5 – 16 of the result word contain the high 12 bits of
the calculated arctangent of the bias-corrected sine and cosine values from the resolver. Because PMAC
software considers the value in bit 5 to be a “count” for its scaling purposes, this conversion returns
resolver position values of a 12-bit conversion (4096 “counts” per cycle of the resolver).
However, because the conversion uses dual 14-bit converters and the arctangent calculations are valid to
15 bits, the result contains additional resolution in bits 0 – 4 that PMAC software considers to have
“fractional”, but still real, count resolution. If the electromagnetic noise levels are low and the signals use
near the full scale of the ADCs, a repeatable 14-bit resolution (16,384 states per cycle of the resolver) can
be achieved.
Bits 17 – 23 of the result contain cycle data from software extension of the result to multiple resolver
cycles. If the result is then used for feedback or master data, it will be further extended in the motor
algorithms.
This resolver conversion is a direct, and not a tracking, conversion. As such, it is more dynamically
responsive, but also more susceptible to measurement noise. If a more noise-immune result is desired, at
the cost of some dynamic responsiveness (but still no steady-state tracking errors), a digital tracking filter
can be implemented on this result with another conversion table entry (format $D8). The result of that
filter entry can then be used as the feedback or master data.
Each closed-loop motor will decelerate from its present command velocity to zero velocity at a rate
defined by its own motor I-variable Ixx15. Note that a multi-axis system may not stay on its programmed
path during this deceleration. If the time-base (override) value used by a motor is exactly 0% when the
<CTRL-A> command is given, the motor will abort at the present position even if the command velocity
is not zero; otherwise a ramp-down trajectory will be computed using Ixx15 and executed using the
override value.
A <CTRL-A> stop to a program is not meant to be recovered from gracefully, because the axes will in
general not stop at a programmed point. An on-line J= command may be issued to each motor to cause it
to move to the end point that was programmed when the abort occurred. Then the program(s) can be
resumed with an R (run) or <CTRL-R> command.
To stop a motion sequence in a manner that can be recovered from easily, use instead the Quit (Q or
<CTRL-Q>), the Hold (H or <CTRL-O>), the Quick Stop (\) or the Halt (/) commands.
When Turbo PMAC is set up to power on with all motors killed (Ixx80 = 0) and with I36 set to 0, this
command can be used to enable all of the motors (provided that they are not synchronous motors
commutated by Turbo PMAC – in that case, the motors should be enabled with the $ or $$ phase-
referencing command).
For multiple cards on a single serial daisy-chain, this command affects all cards on the chain, regardless
of the current software addressing.
See Also
Stop Commands (Making Your Application Safe)
On-line commands A, E, <CTRL-E> $, $$, /, \, J=, H, <CTRL-O>, Q, <CTRL-Q>
I-variables I36, Ixx15, Ixx80.
<CONTROL-B>
Function Report status word for eight motors.
Scope Global
Syntax ASCII Value 2D; $02
This command causes Turbo PMAC to report the status words for 8 selected motors to the host in
hexadecimal ASCII form, 12 characters per motor starting with the lowest-numbered of the selected
motors, with the characters for each motor separated by spaces. The characters reported for each motor
are the same as if the ? command had been issued for that motor.
The set of eight motors whose data is reported is selected by the most recent ##{constant} value for
this port:
##0: Motors 1 – 8 (default)
##1: Motors 9 – 16
##2: Motors 17 – 24
##3: Motors 25 – 32
The detailed meanings of the individual status bits are shown under the ? command description.
For multiple cards on a single serial daisy-chain, this command affects only the card currently addressed
in software (@n).
Example:
<CTRL-B>
812000804001 812000804001 812000A04001 812000B04001 050000000000 050000000000
050000000000 050000000000<CR>
See Also:
On-line commands <CTRL-C>, <CTRL-G>, ##, ##{constant}, ?, @n
Memory-map registers X:$0000B0, X:$000130, etc., Y:$0000C0, Y:$000140, etc.;
Suggested M-Variable definitions Mxx30-Mxx45.
<CONTROL-C>
Function: Report all coordinate system status words
Scope: Global
Syntax: ASCII Value 3D, $03
This command causes Turbo PMAC to report the status words for all 16 of the coordinate systems to the
host in hexadecimal ASCII form, 12 characters per coordinate system starting with coordinate system 1,
with the characters for each coordinate system separated by spaces. The characters reported for each
coordinate system are the same as the first twelve characters reported if the ?? command had been issued
for that coordinate system.
The detailed meanings of the individual status bits are shown under the ?? command description.
For multiple cards on a single serial daisy-chain, this command affects only the card currently addressed
in software (by the @n command).
Example:
<CTRL-C>
A80020020000 A80020020000 A80020020000 A80020020000 A80020000000 A80020000000
A80020000000 A80020000000 A80020020000 A80020020000 A80020020000 A80020020000
A80020000000 A80020000000 A80020000000 A80020000000<CR>
See Also:
On-line commands <CTRL-B>, <CTRL-G>, ??;
Memory-map registers X:$002040, X:$0020C0, etc., Y:$00203F, Y:$0020BF, etc.;
Suggested M-variable definitions Msx80-Msx90.
<CONTROL-D>
Function: Disable all PLC programs.
Scope: Global
Syntax: ASCII Value 4D; $04
This command causes all PLC programs to be disabled (i.e. stop executing). This is the equivalent of
DISABLE PLC 0..31 and DISABLE PLCC 0..31. It is especially useful if a CMD or SEND
statement in a PLC has run amok.
For multiple cards on a single serial daisy-chain, this command affects all cards on the chain, regardless
of the current software addressing.
Example:
TRIGGER FOUND
TRIGTRIGER FOTRIGGER FOUND
TRTRIGTRIGGER FOUND (Out-of-control SEND message from PLC)
<CTRL-D> ........ (Command to disable the PLCs)
.......................... (No more messages; can now edit PLC)
See Also:
On-line commands DISABLE PLC, ENABLE PLC, DISABLE PLCC, ENABLE PLCC, OPEN PLC
Program commands DISABLE PLC, ENABLE PLC, DISABLE PLCC, ENABLE PLCC, COMMAND,
SEND
<CONTROL-E>
Function: Enable disabled motors
Scope: Global
Syntax: ASCII value 5D,$05
This command enables all of the disabled motors on the Turbo PMAC, closing the position loop at the
present actual position. If a motor is open-loop enabled, it closes the position loop at the present actual
position. It has no effect on closed-loop enabled motors.
If I36 is set to 1, the <CTRL-A> (abort all) command does not enable disabled motors, so the <CTRL-E>
command is used for enabling all motors together. If I36 is set to 0, either the <CTRL-A> or <CTRL-E>
command could be used.
Note that if the motor is a synchronous (zero-slip – Ixx78 = 0) motor commutated by Turbo PMAC
(Ixx01 bit 0 = 1), a phase referencing is required after power-up/reset before the motor can be enabled.
This is done automatically on power-up/reset if Ixx80 for the motor is set to 1 or 3, or subsequently with
the motor-specific $ command, or the coordinate-system-specific $$ command. The <CTRL-E>
command does not cause a phase referencing to be performed on any motor.
The coordinate-system-specific E command performs the comparable action for just the motors of the
addressed coordinate system.
See Also
On-line commands A, <CTRL-A> E, $, $$
I-variables I36, Ixx80.
<CONTROL-F>
Function: Report following errors for 8 motors.
Scope: Global.
Syntax: ASCII Value 6D; $06
This command causes Turbo PMAC to report the following errors of a set of 8 motors to the host. The
errors are reported in an ASCII string, each error scaled in counts, rounded to the nearest tenth of a count.
A space character is returned between the reported errors for each motor.
The set of eight motors whose data is reported is selected by the most recent ##{constant} value for
this port:
##0: Motors 1 – 8 (default)
##1: Motors 9 – 16
##2: Motors 17 – 24
##3: Motors 25 – 32
Refer to the on-line F command for more detail as to how the following error is calculated.
For multiple cards on a single serial daisy-chain, this command affects only the card currently addressed
in software (by the @n command).
Example:
<CTRL-F>
0.5 7.2 -38.3 1.7 0 0 0 0<CR>
See Also:
I-variables Ixx11, Ixx12
On-line commands ##, ##{constant}, F, <CTRL-P>, <CTRL-V>
<CONTROL-G>
Function: Report global status word.
Scope: Global
Syntax: ASCII Value 7D; $07
This command causes Turbo PMAC to report the global status words to the host in hexadecimal ASCII
form, using 12 characters. The characters sent are the same as if the ??? command had been sent,
although no command acknowledgement character (<ACK> or <LF>, depending on I3) is sent at the end
of the response.
The detailed meanings of the individual status bits are shown under the ??? command description.
For multiple cards on a single serial daisy-chain, this command affects only the card currently addressed
in software (by the @n command).
Example:
<CTRL-G>
003000400000<CR>
See Also:
On-line commands <CTRL-B>, <CTRL-C>, ???
Memory-map registers X:$000006, Y:$000006.
<CONTROL-H>
Function: Erase last character.
Scope: Port specific
Syntax: ASCII Value 8D; $08 (<BACKSPACE>).
This character, usually entered by typing the <BACKSPACE> key when talking to Turbo PMAC in
terminal mode, causes the most recently entered character in Turbo PMAC's command-line-receive buffer
for this port to be erased.
See Also:
Talking to Turbo PMAC
On-line command <CTRL-O> (Feed Hold All)
<CONTROL-I>
Function: Repeat last command line.
Scope: Port specific
Syntax: ASCII Value 9D; $09 (<TAB>).
This character, sometimes entered by typing the <TAB> key, causes the most recently sent alphanumeric
command line to Turbo PMAC on this port to be re-commanded. It provides a convenient way to quicken
a repetitive task, particularly when working interactively with Turbo PMAC in terminal mode. Other
control-character commands cannot be repeated with this command.
Note:
Most versions of the PMAC Executive Program trap a <CTRL-I> or <TAB> for
their own purposes, and do not send it on to Turbo PMAC, even when in terminal
mode.
Example:
This example shows how the tab key can be used to look for some event:
PC<CR>
P1:10<CR>
<TAB>
P1:10<CR>
<TAB>
P1:10<CR>
<TAB>
P1:11<CR>
See Also:
On-line command <CONTROL-Y>.
<CONTROL-K>
Function: Kill all motors.
Scope: Global
Syntax: ASCII Value 11D; $0B
This command kills all motor outputs by opening the servo loop, commanding zero output, and taking the
amplifier enable signal (AENAn) false (polarity is determined by jumper E17x on Turbo PMAC boards)
for all motors on the card. If any motion programs are running, they will be aborted automatically.
(For the motor-specific K (kill) command, if the motor is in a coordinate system that is executing a motion
program, the program execution must be stopped with either an A (abort) or Q (quit) command before
Turbo PMAC will accept the K command.)
For multiple cards on a single serial daisy-chain, this command affects all cards on the chain, regardless
of the current software addressing.
See Also: On-line commands K, A, <CONTROL-A>.
<CONTROL-M>
Function: Enter command line.
Scope: Port specific
Syntax: ASCII Value 13D; $0D (<CR>)
This character, commonly known as <CR> (carriage return), causes the alphanumeric characters in the
Turbo PMAC's command-line-receive buffer for this port to be interpreted and acted upon. (Control-
character commands do not require a <CR> character to execute.)
Note that for multiple Turbo PMACs daisy-chained together on a serial interface, this will act on all cards
simultaneously, not just the software-addressed card. For simultaneous action on multiple cards, it is best
to load up the command-line-receive buffers on all cards before issuing the <CR> character.
Example:
#1J+<CR>
P1<CR>
@0&1B1R@1&1B7R<CR> (This causes card 0 on the serial daisychain to
.......................... have its CS 1 execute PROG 1 and card 1 to
.......................... have its CS 1 execute PROG 7 simultaneously.)
See Also: Talking to Turbo PMAC
<CONTROL-N>
Function: Report command line checksum.
Scope: Port specific
Syntax: ASCII Value 14D; $0E
This character causes Turbo PMAC to calculate and report the checksum of the alphanumeric characters
of the present command line (i.e. since the most recent carriage-return character) for this port.
As typically used, the host computer would send the entire command line up to, but not including, the
carriage return. It would then send the <CTRL-N> character, and Turbo PMAC would return the
checksum value. If this value agreed with the host's internally calculated checksum value, the host would
then send the <CR> and Turbo PMAC would execute the command line. If the values did not agree, the
host would send a <CTRL-X> command to erase the command line, then resend the line, repeating the
process.
Note:
The PMAC Executive Program terminal mode will not display the checksum
values resulting from a <CTRL-N> command.
Example:
With I4=1 and I3=2:
Host sends: ......... J+<CTRL-N>
Turbo PMAC sends: <117dec> (117=74[J] + 43[+]; correct)
Host sends: ......... <CR>
Turbo PMAC sends: <ACK><117dec> (handshake & checksum again)
Host sends: ......... J/<CTRL-N>
Turbo PMAC sends: <122dec> (122 != 74[J] +47[/]; incorrect)
Host sends: ......... <CTRL-X> (Erase the incorrect command)
.......................... J/<CTRL-N> (Send the command again)
For multiple cards on a single serial daisy-chain, this command affects only the card currently addressed
in software (by the @n command).
Example:
<CTRL-P>
9999.5 10001.2 5.7 -2.1 0 0 0 0<CR>
See Also:
On-line commands ##, ##{constant}, P, <CTRL-V>, <CTRL-F>.
<CONTROL-Q>
Function: Quit all executing motion programs.
Scope: Global
Syntax: ASCII Value 17D; $11
This command causes any and all motion programs running in any coordinate system to stop executing
either at the end of the currently executing move, or after the moves that have already been calculated are
finished, depending on the mode. It is equivalent to issuing the Q command to all coordinate systems.
Refer to the Q command description for more details.
Program execution may be resumed from this point with the R (run) or S (step) commands.
For multiple cards on a single serial daisy-chain, this command affects all cards on the chain, regardless
of the current software addressing.
See Also:
On-line commands <CTRL-A>, <CTRL-K>, <CTRL-O>, <CTRL-R>, <CTRL-S>, Q
Motion-program command STOP.
<CONTROL-R>
Function: Begin execution of motion programs in all coordinate systems.
Scope: Global
Syntax: ASCII Value 18D; $12
This command is the equivalent of issuing the R (run) command to all coordinate systems in Turbo
PMAC. Each active coordinate system (i.e. one that has at least one motor assigned to it) that is to run a
program must already be pointing to a motion program (initially this is done with a B{prog num}
command).
For multiple cards on a single serial daisy-chain, this command affects all cards on the chain, regardless
of the current software addressing.
Example:
&1B1&2B500<CR>
<CTRL-R>
See Also:
Executing a Motion Program (Writing and Executing Motion Programs)
Resetting Turbo PMAC (Talking to Turbo PMAC)
On-line commands R, B{constant}
<CONTROL-S>
Function: Step working motion programs in all coordinate systems.
Scope: Global
Syntax: ASCII Value 19D; $13
This command is the equivalent of issuing an S (step) command to all of the coordinate systems in Turbo
PMAC.
Each active coordinate system (i.e. one that has at least one motor assigned to it) that is to run a program
must already be pointing to a motion program (initially this is done with a B{prog num} command).
A program that is not running will execute all lines down to and including the next motion command
(move or dwell), or if it encounters a BLOCKSTART command first, all lines down to and including the
next BLOCKSTOP command.
If a program is already running in continuous execution mode (from an R (run) command), an S
command will put the program in single-step mode, stopping execution after the next motion command).
In this situation, it has exactly the same effect as a Q (quit) command.
For multiple cards on a single serial daisy chain, this command affects all cards on the chain, regardless of
the current software addressing.
See Also:
On-line commands <CTRL-A>, <CTRL-O>, <CTRL-Q>, <CTRL-R>, A, H, O, Q, R, S;
Motion-program commands BLOCKSTART, BLOCKSTOP, STOP.
Control-panel port (JPAN) input STEP/.
<CONTROL-T>
Function: Cancel MACRO pass-through mode
Scope: Global
Syntax: ASCII Value 20D; $14
This command causes Turbo PMAC to cancel the MACRO pass-through mode it had been put in with the
MACROMSTASCII or the MACROSTASCII command on this port. In the MACRO pass-through mode,
any command received on the port is passed on to another master on the ring through the MACRO link,
the response is received over the ring from the other master, and this response is reported back to the host
over this port.
The <CONTROL-T> command ends this mode, and resumes normal communications over this port.
Subsequent commands on the port are acted on by this Turbo PMAC, and responses go directly over the
communications port to the host computer.
If I63 is set to its default value of 0, Turbo PMAC sends no acknowledgment that it has finished its action
on the <CTRL-T> command. If I63 is set to 1, Turbo PMAC acknowledges that it has finished its action
by returning a <CTRL-X> character back to the host.
If the port that receives the <CONTROL-T> command is not currently in the MACRO pass-through
mode, Turbo PMAC will take no action on receipt of the command.
See Also:
MACRO Master-to-Master Communications
On-line command MACROMSTASCII, MACROSTASCII
<CONTROL-V>
Function: Report velocity for eight motors.
Scope: Global
Syntax: ASCII Value 22D; $16
This command causes Turbo PMAC to report the velocities of a selected set of eight motors to the host.
Typically, the velocity units are scaled in encoder counts per servo cycle, rounded to the nearest tenth.
The velocity window in the Turbo PMAC Executive program works by repeatedly issuing the <CTRL-
V> command and displaying the response on the screen.
To scale these values into counts/msec, multiply the response by 8,388,608/I10 (servo cycles/msec).
The set of eight motors whose data is reported is selected by the most recent ##{constant} value for
this port:
##0: Motors 1 – 8 (default)
##1: Motors 9 – 16
##2: Motors 17 – 24
##3: Motors 25 – 32
This command returns filtered velocity values, with the filter time constant controlled by global variables
I60 and I61. It does not report the raw velocity register calculated by the servo loop each servo cycle.
For multiple cards on a single serial daisy chain, this command affects only the card currently addressed
in software (@n).
See Also:
I-variables I10, I59 I60, I61 Ixx60
On-line commands <CTRL-B>, <CTRL-F>, <CTRL-P>, ##, ##{constant}, V
<CONTROL-X>
Function: Cancel in-process communications.
Scope: Port-specific
Syntax: ASCII Value 24D; $18
This command causes the Turbo PMAC to stop sending any messages that it had started to send, even
multi-line messages, on the port over which this command is sent. This also causes Turbo PMAC to
empty the port’s command queue from the host, so it will erase any partially sent commands.
It can be useful to send this before sending a query command for which an exact response format is
expected, if not sure what Turbo PMAC has been doing before, because it makes sure nothing else comes
through before the expected response. As such, it is often the first character sent to Turbo PMAC from
the host when trying to establish initial communications.
If I63 is set to its default value of 0, Turbo PMAC sends no acknowledgment that it has finished its action
on the <CTRL-X> command. If I63 is set to 1, Turbo PMAC acknowledges that it has finished its action
by echoing the <CTRL-X> character back to the host.
This can result in more efficient communications, and is supported in PCOMM32 communications
routines in V2.21 and newer (March 1999 and later).
Note:
This command empties the command queue in Turbo PMAC RAM, but it cannot
erase the 1 or 2 characters already in the response port. A robust algorithm for
clearing responses would include two-character read commands that can time-out
if necessary.
For multiple cards on a single serial daisy chain, this command affects all cards on the chain, regardless of
the current software addressing.
See Also:
I-variable I63
On-line command <CTRL-H>
!{axis}{constant}[{axis}{constant}…]
Function: Alter destination of RAPID move
Scope: Coordinate-system specific
Syntax: !{axis}{constant}[{axis}{constant}…]
where:
{axis} is the letter specifying which axis (X, Y, Z, A, B, C, U, V, W);
{constant} is a numerical value representing the end position;
[{axis}{constant}…] is the optional specification of simultaneous movement for more axes.
or
!{axis}Q{constant}[{axis}Q{constant}…]
where:
{axis} is the letter specifying which axis (X, Y, Z, A, B, C, U, V, W);
{constant} is a numerical value representing the number or the Q-variable whose value specifies
the end position;
[{axis}Q{constant}…] is the optional specification of simultaneous movement for more axes.
This command creates a RAPID-mode move of the specified axis or axes to the specified destinations. If
another RAPID-mode move of an axis is in progress, that move is broken into and the motion of the axes
is blended into the move to this new destination, effectively altering the destination of the move in
progress.
Each axis destination can be specified either directly as a numerical constant (e.g. !X63.72), or
indirectly by specifying the Q-variable whose value represents the axis destination (e.g. !XQ15).
In either case, the destination value for each axis is in the scaled engineering units for the axis. The
destination value always represents the end position for the axis, relative to program zero, even if the axis
is currently in incremental mode. Execution of this command does not change the mode of the axis. The
order in which the axes are specified in this command does not matter.
If a programmed move of a mode other than RAPID is in progress when this command is sent, this
command will be rejected with an error.
If no move is in progress when this command is sent, this command will simply execute a RAPID-mode
move to the specified destination. In this case, before starting the move, Turbo PMAC will execute the
PMATCH position-matching function automatically to make sure motor and axis positions are properly
linked in order for the move to execute properly.
Examples:
!X5
!X23.762 Y-345.124
!A-90.2 B37.3
!XQ152 YQ154
!XQ30 Y37.936
See Also:
Altered Destination Moves
RAPID-Mode Moves
I-Variables Ixx16, Ixx19, Ixx20, Ixx21, Ixx22, Ixx90, Ixx92
@
Function: Report currently addressed card on serial daisy-chain
Scope: Global
Syntax: @
This command causes the addressed Turbo PMAC on a serial daisy-chain to report its number to the host.
The number is set by variable I0 on the board, and can range from 0 to 15. If all cards are addressed, card
@0 will return an @ character.
I1 must be set to 2 or 3 for this command to be accepted. Otherwise, ERR003 is reported.
Example:
@ ; Ask Turbo PMAC chain which card is addressed
4 ; Turbo PMAC @4 reports that it is addressed
See Also:
Addressing Commands (Talking to Turbo PMAC)
Multiple-Card Applications (Synchronizing Turbo PMAC to External Events)
I-variables I0, I1
On-line commands #, #{constant}, &, &{constant}, @{constant}
@{card}
Function: Address a card on the serial daisychain.
Scope: Global
Syntax: @{card}
where:
{card} is a hexadecimal digit (0 to 9, A to F), representing the number of the card on the serial
daisychain to be addressed; or the @ character, denoting that all cards are to be addressed
simultaneously.
This command makes the Turbo PMAC board specified by {card} the addressed board on the serial
daisychain. (the one on which subsequent commands will act). The number for each board is set by
variable I0 on the board. The addressing is modal, so all further commands will affect this board until a
different board is addressed. At power-up/reset, Board @0 is addressed.
I1 must be set to 2 or 3 for this command to be accepted. Otherwise, ERR003 is reported.
To address all cards simultaneously, use the @@ command. Query commands (those requiring a data
response) will be rejected in this mode.
It is best to send a <CR> carriage return character immediately after the @{card} command before any
other command is sent, to give the card that had been addressed time to tri-state its serial port outputs so
that it will not interfere with the response of the newly addressed card.
This command should only be used when multiple Turbo PMAC cards are connected on a single serial
cable. In this case, I-variable I1 should be set to 2 or 3 on all boards.
Example:
I1=2@0 ; This sequence can be used the first time talking to
multiple cards on a chain to put them in the proper configuration.
@0#1J+ ; Jog motor 1 of Card 0.
@5P20 ; Request the value of P20 on card @5
@@R ; All cards, addressed C.S. run active program
See Also:
Addressing Commands (Talking to Turbo PMAC)
Multiple-Card Applications (Synchronizing Turbo PMAC to External Events)
I-variables I0, I1
On-line commands #, &, &{constant}, @
#
Function: Report port’s currently addressed motor
Scope: Port specific
Syntax: #
This command causes Turbo PMAC to return the number of the motor currently addressed for the
communications port over which this command is sent.
This is the motor that will act on subsequent motor-specific commands sent over this port until a different
motor is addressed with a #{constant} command.
Other communications ports may be addressing different motors at the same time, as set by
#{constant} commands sent over those ports. In addition, each background PLC program can
individually modally address a motor using the ADDRESS statement for subsequent COMMAND
statements, and the hardware control panel on a Turbo PMAC can separately select a motor for its
hardware inputs.
Note:
In firmware versions 1.934 and older, all communications ports addressed the
same motor, so a #{constant} command sent over any port set the addressed
motor for all ports.
Example:
# ; Ask Turbo PMAC which motor is addressed
2 ; Turbo PMAC reports that motor 2 is addressed
See Also:
Control-Panel Port Inputs (Connecting Turbo PMAC to the Machine)
On-line commands #{constant}, &, &{constant}, @{constant}
Program commands ADDRESS, COMMAND
#{constant}
Function: Select port’s addressed motor
Scope: Port specific
Syntax: #{constant}
where:
{constant} is an integer from 1 to 32, representing the number of the motor to be addressed
This command makes the motor specified by {constant} the addressed motor for the communications
port over which this command is sent. This is the motor that will act on subsequent motor-specific
commands sent over this port until a different motor is addressed with another #{constant}
command.
Other communications ports may be addressing different motors at the same time, as set by
#{constant} commands sent over those ports. In addition, each background PLC program can
individually modally address a motor using the ADDRESS statement for subsequent COMMAND
statements, and the hardware control panel on a Turbo PMAC can separately select a motor for its
hardware inputs.
Note:
In firmware versions 1.934 and older, all communications ports addressed the
same motor, so a #{constant} command sent over any port set the addressed
motor for all ports.
Example:
#1J+ ; Command Motor 1 to jog positive
J- ; Command Motor 1 to jog negative
#2J+ ; Command Motor 2 to jog positive
J/ ; Command Motor 2 to stop jogging
See Also:
Control-Panel Port Inputs (Connecting Turbo PMAC to the Machine)
Addressing commands (Talking to Turbo PMAC)
Program commands COMMAND, ADDRESS
On-line commands #, &, &{constant}, @{constant}
#{constant}->
Function: Report the specified motor's coordinate system axis definition.
Scope: Coordinate-system specific
Syntax: #{constant}->
where:
{constant} is an integer from 1 to 32 representing the number of the motor whose axis definition
is requested
Note:
No spaces are allowed in this command.
This command causes Turbo PMAC to report the current axis definition of the specified motor in the
currently addressed coordinate system. If the motor has not been defined to an axis in the currently
addressed system, Turbo PMAC will return a 0 (even if the motor has been assigned to an axis in another
coordinate system). A motor can have an axis definition in only one coordinate system at a time.
Example:
&1 ; Address Coordinate System 1
#1-> ; Request Motor 1 axis definition in C.S. 1
10000X ; Turbo PMAC responds with axis definition
&2 ; Address Coordinate System 2
#1-> ; Request Motor 1 axis definition in C.S. 2
0 ; Turbo PMAC shows no definition in this C.S.
See Also:
Axes, Coordinate Systems (Setting Up a Coordinate System)
On-line commands #{constant}->0, #{constant}->{axis definition}, UNDEFINE,
UNDEFINE ALL.
#{constant}->0
Function: Clear axis definition for specified motor.
Scope: Coordinate-system specific
Syntax: #{constant}->0
where:
{constant} is an integer from 1 to 32 representing the number of the motor whose axis definition
is to be cleared
Note:
No spaces are allowed in this command.
This command clears the axis definition for the specified motor if the motor has been defined to an axis in
the currently addressed coordinate system. If the motor is defined to an axis in another coordinate
system, this command will not be effective. This allows the motor to be redefined to another axis in this
coordinate system or a different coordinate system.
Compare this command to UNDEFINE, which erases all the axis definitions in the addressed coordinate
system, and to UNDEFINE ALL, which erases all the axis definitions in all coordinate systems.
Example:
This example shows how the command can be used to move a motor from one coordinate system to
another:
&1 ; Address C.S. 1
#4-> ; Request definition of #4
5000A ; Turbo PMAC responds
#4->0 ; Clear definition
&2 ; Address C.S. 2
#4->5000A ; Make new definition in C.S. 2
See Also:
Axes, Coordinate Systems (Setting Up a Coordinate System)
On-line commands UNDEFINE, UNDEFINE ALL, #{constant}->{axis definition}.
#{constant}->{axis definition}
Function: Assign an axis definition for the specified motor.
Scope: Coordinate-system specific
Syntax: #{constant}->{axis definition}
where:
{constant} is an integer from 1 to 32 representing the number of the motor whose axis definition
is to be made;
{axis definition} consists of 1 to 3 sets of [{scale factor}]{axis}, separated by the
+ character, in which:
the optional {scale factor} is a floating-point constant representing the number of motor
counts per axis unit (engineering unit); if none is specified, Turbo PMAC assumes a value of 1.0;
{axis} is a letter (X, Y, Z, A, B, C, U, V, W) representing the axis to which the motor is to be
matched;
[+{offset}] (optional) is a floating-point constant representing the difference between axis
zero position and motor zero (home) position, in motor counts; if none is specified, Turbo PMAC
assumes a value of 0.0
Note:
No space is allowed between the motor number and the arrow double character, or
between the scale factor and the axis letter.
This command assigns the specified motor to a set of axes in the addressed coordinate system. It also
defines the scaling and starting offset for the axis or axes.
In the vast majority of cases, there is a one-to-one matching between Turbo PMAC motors and axes, so
this axis definition statement only uses one axis name for the motor.
A scale factor is typically used with the axis character, so that axis moves can be specified in standard
units (e.g. millimeters, inches, degrees). This number is what defines what the user units will be for the
axis. If no scale factor is specified, a user unit for the axis is one motor count.
Occasionally an offset parameter is used to allow the axis zero position to be different from the motor
home position. (This is the starting offset; it can later be changed in several ways, including the PSET,
{axis}=, ADIS, and IDIS commands).
If the specified motor is currently assigned to an axis in a different coordinate system, Turbo PMAC will
reject this command (reporting an ERR003 if I6=1 or 3). If the specified motor is currently assigned to an
axis in the addressed coordinate system, the old definition will be overwritten by this new one.
To undo a motor's axis definition, address the coordinate system in which it has been defined, and use the
command #{constant}->0. To clear all of the axis definitions within a coordinate system, address
the coordinate system and use the UNDEFINE command. To clear all axis definitions in all coordinate
systems, use UNDEFINE ALL.
For more sophisticated systems, two or three cartesian axes may be defined as a linear combination of the
same number of motors. This allows coordinate system rotations and orthogonality corrections, among
other things. One to three axes may be specified (if only one, it amounts to the simpler definition above).
All axes specified in one definition must be from the same triplet set of cartesian axes: XYZ or UVW. If
this multi-axis definition is used, a command to move an axis will result in multiple motors moving.
Example:
#1->X ; User units = counts
#4->2000 A ; 2000 counts/user unit
#9->3333.333Z-666.667 ; Non-integers OK
#3->Y ; 2 motors may be assigned to the same axis;
#2->Y ; both motors move when a Y move is given
#1->8660X-5000Y ;This provides a 30o rotation of X and Y...
#2->5000X+8660Y ;with 10000 cts/unit -- this rotation does
#3->2000Z-6000 ;not involve Z, but it could have
This example corrects for a Y axis 1 arc minute out of square:
#5->100000X ;100000 cts/in
#6->-29.1X+100000Y ;sin and cos of 1/60
See Also:
Axes, Coordinate Systems (Setting Up a Coordinate System)
On-line commands #{constant}->, #{constant}->0, UNDEFINE, UNDEFINE ALL.
#{constant}->I
Function: Assign inverse-kinematic definition for specified motor
Scope: Coordinate-system specific
Syntax: #{constant}->I[+{offset}]
where:
{constant} is an integer from 1 to 32 representing the number of the motor whose axis definition
is to be made;
[+{offset}] (optional) is a floating-point constant representing the difference between axis zero
position and motor zero (home) position, in motor counts; if none is specified, Turbo PMAC assumes
a value of 0.0
Note:
No space is allowed between the motor number and the “arrow” double character.
This command assigns the specified motor to an inverse-kinematic axis in the addressed coordinate
system. It also defines the offset for the axis. A motor assigned in this way must get its commanded
positions each programmed move or segment from the inverse-kinematic program for the coordinate
system. This program, created with an OPEN INVERSE command, is executed automatically each
programmed move or segment if Isx50 for the coordinate system is set to 1.
At the end of each execution of the inverse-kinematic program for the coordinate system, Turbo PMAC
expects to find the motor position calculated by the program for each Motor xx in the coordinate system
defined as an inverse-kinematic axis in variable Pxx (e.g. P13 for Motor 13).
See Also:
Inverse Kinematics
I-variable Isx50
On-line commands OPEN FORWARD, OPEN INVERSE
##
Function: Report port’s motor group
Scope: Port specific
Syntax: ##
This command causes Turbo PMAC to return the number of the motor group currently selected on this
port for on-line commands <CTRL-B>, <CTRL-F>, <CTRL-P>, and <CTRL-V>. This value can be set
for the port by the ##{constant} command, and defaults to 0 on power-up/reset. Each
communications port can have a different value.
Note:
This is not related to the individual motor addressed with the # command, and
reported with the #{constant} command
The possible values returned and the motors they represent are:
0: Motors 1 – 8
1: Motors 9 – 16
2: Motors 17 – 24
3: Motors 25 – 32
Note:
In Turbo PMAC firmware versions 1.934 and older, this function was controlled
commonly for all ports by global I-variable I59.
See Also:
I-variable I59
On-line commands <CTRL-B>, <CTRL-F>, <CTRL-P>, <CTRL-V>, ##{constant}
##{constant}
Function: Select port’s motor group
Scope: Port specific
Syntax: ##{constant}
where:
{constant} is an integer from 0 to 3 representing the motor group
This command selects the group of eight motors whose data will be supplied in response to subsequent
<CTRL-B> (report motor status words), <CTRL-F> (report motor following errors), <CTRL-P> (report
motor positions), and <CTRL-V> (report motor velocities) commands issued on this same port. It does
not affect the behavior of these commands issued on any other port.
Note:
This is not related to the individual motor addressed with the # command, and
reported with the #{constant} command
The possible versions of the ##{constant} command and the motors they select are:
##0: Motors 1 – 8
##1: Motors 9 – 16
##2: Motors 17 – 24
##3: Motors 25 – 32
Note:
In Turbo PMAC firmware versions 1.934 and older, this function was controlled
commonly for all ports by global I-variable I59.
See Also:
I-variable I59
On-line commands <CTRL-B>, <CTRL-F>, <CTRL-P>, <CTRL-V>, ##
$
Function: Establish phase reference for motor
Scope: Motor specific
Syntax: $
This command causes Turbo PMAC to attempt to establish the phase reference and close the servo loop
for a PMAC-commutated (Ixx01 bit 0 = 1) synchronous (Ixx78 = 0) motor. On other types of motors,
where there is no need to establish a phase reference, the $ command will simply close the servo loop for
the motor (a J/ command is also suitable for these motors).
The phase reference for a synchronous PMAC-commutated can be established either by a phasing search
move if Ixx74 > 0, or by an absolute position read if Ixx81 > 0. If both of these variables are set to 0,
Turbo PMAC will set the phase reference error status bit for the motor on a $ command, leaving the
motor in the “killed” state, and not permitting the servo loop to be closed until the error status bit is
cleared.
If Ixx80 bit 0 is saved as 0, no phase reference is performed automatically at power-up or reset of the full
board, and the phase reference error bit is set, prohibiting the closing of the servo loop. A subsequent $
command, successfully executed, is required to establish the phase reference for synchronous, PMAC-
commutated motor.
If Ixx80 bit 0 is saved as 1, the phase reference operation is performed automatically at power-up or reset
of the full board. In this case it is possible, but not required, to re-establish the phase reference with a
subsequent $ command.
A phasing search move checks for any of the following error conditions both before and after the search:
Hardware overtravel limits
Amplifier fault
I2T overcurrent fault
Fatal following error fault
Integrated following error fault
If any of these error conditions is present, the phase reference is considered to have failed and the phase
reference error status bit is set. Also, if no movement is detected during the search, the error bit is set
An absolute phase position read checks for any of the above fault conditions shortly after the read. If any
of these is found, the read is presumed to have failed and the error bit is set. Also, if an illegal value is
read from the sensor (e.g. all 3 hall sensors at 0 or 1), the error bit is set.
If the $ command is issued while the motor is executing a move, the command will be rejected, with
Turbo PMAC reporting ERR018 if I6 is set to 1 or 3.
If another command to move the motor is issued while the phase reference is still in progress, that
command will be rejected, with Turbo PMAC reporting ERR018 if I6 is set to 1 or 3. The phase
reference in progress status bit is set to 1 while the reference is being done.
Example:
I180 ; Request value of #1 power-on mode variable
0 ; Turbo PMAC responds with 0 powers on unphased and killed
$$$ ; Reset card; motor is left in killed state
#1$ ; Initialize motor, phasing and reading as necessary
See Also:
Absolute Sensors (Setting Up a Motor)
Power-on Phasing (Setting Up Turbo PMAC Commutation)
I-variables Ixx10, Ixx73, Ixx74, Ixx75, Ixx80, Ixx81
On-line commands $*, $$, $$*, $$$, J/
$$
Function: Establish phase reference for motors in coordinate system
Scope: Coordinate system specific
Syntax: $$
This command causes Turbo PMAC to attempt to establish the phase references and close the servo loops
for all of the motors in the addressed coordinate system.
For PMAC-commutated (Ixx01 bit 0 = 1) synchronous (Ixx78 = 0) motors, a phasing search move (Ixx74
> 0) or absolute phase position read (Ixx81 > 0) is performed, and the servo loop is closed. For other
types of motors, where there is no need to establish a phase reference, the $$ command will simply close
the servo loop for the motor.
The action of the $$ command is equivalent to that of the $ command issued to each motor in the coordinate
system. For details on the action performed, refer to the specification of the $ command.
If the $$ command is issued while any motor is executing a move, the command will be rejected, with
Turbo PMAC reporting ERR018 if I6 is set to 1 or 3.
If another command to move a motor is issued while the phase reference for that motor is still in progress,
that command will be rejected, with Turbo PMAC reporting ERR018 if I6 is set to 1 or 3. The phase
reference in progress status bit for the motor is set to 1 while the reference is being done.
Example:
I180 ; Request value of #1 power-on mode variable
0 ; Turbo PMAC responds with 0
I280 ; Request value of #2 power-on mode variable
0 ; Turbo PMAC responds with 0 powers on unphased and killed
$$$ ; Reset card; motors are left in killed state
M100=1 M200=1 ; Manually supply power to drives
&1$$ ; Initialize motors, phasing and reading as necessary
See Also:
Absolute Sensors (Setting Up a Motor)
Power-on Phasing (Setting Up Turbo PMAC Commutation)
I-variables Ixx10, Ixx73, Ixx74, Ixx75, Ixx80, Ixx81
On-line commands $, $*, $$*, $$$, J/
$$$
Function: Full card reset.
Scope: Global
Syntax: $$$
This command causes Turbo PMAC to do a full card reset. The effect of $$$ is equivalent to that of
cycling power on Turbo PMAC, or taking the INIT/ line low, then high.
With the re-initialization jumper (E51 on a Turbo PMAC, E3 on a Turbo PMAC2) OFF, this command
does a standard reset of the Turbo PMAC. Turbo PMAC copies the contents of the flash memory into
active main memory during a normal reset cycle, overwriting any current contents. This means that
anything changed in Turbo PMAC's active main memory that was not saved to flash memory will be lost.
Contents of the Option 16 supplemental battery-backed parameter memory are not changed by the $$$
command.
With the re-initialization jumper ON, this command does a reset and re-initialization of the Turbo PMAC.
Instead of copying the last saved I-variable values from flash memory into active memory, Turbo PMAC
copies the factory default I-variable values into active memory.
Note:
Because this command immediately causes Turbo PMAC to enter its power-up/rest
cycle, there is no acknowledging character (<ACK> or <LF>) returned to the host.
Example:
I130=60000 ; Change #1 proportional gain
SAVE ; Copy active memory to non-volatile flash memory
I130=80000 ; Change gain again
$$$ ; Reset card
I130 ; Request value of parameter
60000 ; Turbo PMAC reports current value, which is saved value (Put E51 {E3} on)
$$$ ; Reset card
I130 ; Request value of parameter
2000 ; Turbo PMAC reports current value, which is default
See Also:
Resetting Turbo PMAC (Talking to Turbo PMAC)
Control-Panel Port INIT/ Input (Connecting Turbo PMAC to the Machine)
On-line command $$$***
I-variables I5, Ixx80
JPAN Connector Pin 15
Jumpers E3, E51.
$$$***
Function: Global card reset and reinitialization.
Scope: Global
Syntax: $$$***
This command performs a full reset of the card and re-initializes the memory. All programs and other
buffers are erased in active memory. All I-variables are returned to their factory defaults. (Previously
SAVEd states for these programs, buffers, and variables are still held in flash memory, and can be brought
into active memory with a subsequent $$$command). The $$$*** command will also recalculate the
firmware checksum reference value and eliminate any password that might have been entered.
M-variable definitions, P-variable values, Q-variable values, and axis definitions are not affected by this
command. They can be cleared by separate commands (e.g. M0..8191->*, P0..8191=0,
Q0..8191=0, UNDEFINE ALL).
This command is particularly useful if the program buffers have become corrupted. It clears the buffers
and buffer pointers so the files can be re-sent to Turbo PMAC. Regular backup of parameters and
programs to the disk of a host computer is strongly encouraged so this type of recovery is possible. The
PMAC Executive program has Save Full Turbo PMAC Configuration and Restore Full Turbo PMAC
Configuration functions to make this process easy.
Example:
I130=60000 ; Set #1 proportional gain
SAVE ; Save to non-volatile memory
$$$*** ; Reset and re-initialize card
I130 ; Request value of I130
2000 ; Turbo PMAC reports current value, which is default
$$$ ; Normal reset of card
I130 ; Request value of I130
60000 ; Turbo PMAC reports last saved value
See Also:
On-line command $$$, PASSWORD={string};
Jumper E3 (PMAC2), E51 (PMAC)
PMAC Executive Program Save/Restore Full Configuration.
$$*
Function: Read motor absolute positions
Scope: Coordinate system specific
Syntax: $$*
The $$* command causes PMAC to perform a read of the absolute positions for all motors in the
addressed coordinate system that require an absolute position read (Ixx10 > 0), as defined by Ixx10 and
Ixx95 for the motor. This command performs the same actions in reading the absolute position data that
are normally performed during the board’s power-up/reset cycle if Ixx80 bit 2 is set to the default of 0.
The action of this command is equivalent to that of a motor-specific $* command to each motor in the
coordinate system. Refer to the $* command description for the exact actions of this command.
$*
Function: Read motor absolute position
Scope: Motor specific
Syntax: $*
The $* command causes PMAC to perform a read of the absolute position for the addressed motor, as
defined by Ixx10 and Ixx95 for the motor. It performs the same actions that are normally performed
during the board’s power-up/reset cycle.
The $* command performs the following actions on the addressed motor:
The motor is killed (servo loop open, zero command, amplifier disabled).
If the motor is set up for local hardware encoder position capture by input flags, with bit 0 of Ixx97
set to 0 to specify hardware capture, and bit 18 of Ixx24 set to 0 to specify local, not MACRO, flag
operation (these are default values), the hardware encoder counter for the same channel as the flag
register specified by Ixx25 is set to 0 (e.g. if Ixx25 specifies flags from channel 3, then encoder
counter 3 is cleared).
See Also:
Time-Base Control (Synchronizing Turbo PMAC to External Events)
I-Variables I10, Isx93, Isx94, Isx95
On-line commands %{constant}, H
%{constant}
Function: Set the addressed coordinate system's feedrate override value.
Scope: Coordinate-system specific
Syntax: %{constant}
where:
{constant} is a non-negative floating point value specifying the desired feedrate override (time-
base) value (100 represents real-time)
This command specifies the feedrate override value for the currently addressed coordinate system. The
rate of change to this newly specified value is determined by coordinate system I-variable Isx94.
I-variable Isx93 for this coordinate system must be set to its default value (which tells to coordinate
system to take its time-base value from the % -command register) in order for this command to have any
effect.
23
The maximum % value that Turbo PMAC can implement is equal to (2 /I10)*100 or the (servo update
rate in kHz)*100. If a value greater than this is specified, Turbo PMAC will saturate at this value instead.
To control the time base based on a variable value, assign an M-variable (suggested Msx97) to the
commanded time base register (X:$002000, X:$002100, etc.), then assign a variable value to the M-
variable. The value assigned here should be equal to the desired % value times (I10/100).
Example:
%0 ; Command value of 0, stopping motion
%33.333 ; Command 1/3 of real-time speed
%100 ; Command real-time speed
%500 ; Command too high a value
% ; Request current value
225.88230574 ; Turbo PMAC responds; this is max allowed value
M5197->X:$002000,24,S ; Assign variable to C.S. 1 % command reg.
M5197=P1*I10/100 ; Equivalent to &1%(P1)
See Also:
Time-Base Control (Synchronizing Turbo PMAC to External Events)
I-Variables I10, Isx93, Isx94, Isx95
On-line commands %, H
Memory map registers X:$002000, X:$002100, etc.
&
Function: Report port’s currently addressed coordinate system.
Scope: Port specific
Syntax: &
This command causes Turbo PMAC to return the number of the coordinate system currently addressed
for the communications port over which this command is sent. This is the coordinate system that will act
on subsequent coordinate-system-specific commands sent over this port until a different coordinate
system is addressed with an &{constant} command.
Other communications ports may be addressing different coordinate systems at the same time, as set by
&{constant} commands sent over those ports. In addition, each background PLC program can
individually modally address a coordinate system using the ADDRESS statement for subsequent
COMMAND statements, and the hardware control panel on a Turbo PMAC can separately select a
coordinate system for its hardware inputs.
Note:
In firmware versions 1.934 and older, all communications ports addressed the
same coordinate system, so an &{constant} command sent over any port set
the addressed coordinate system for all ports.
Example:
& ; Ask Turbo PMAC which C.S. is addressed
4 ; Turbo PMAC reports that C.S. 4 is addressed
See Also:
I-variable I2
On-line commands #, #{constant},&{constant};
Program commands ADDRESS, COMMAND;
&{constant}
Function: Select port’s addressed coordinate system.
Scope: Port specific
Syntax: &{constant}
where:
{constant} is an integer from 1 to 16, representing the number of the coordinate system to be
addressed on this port
This command makes the coordinate system specified by {constant} the addressed coordinate system
for the communications port over which this command is sent. This is the coordinate system that will act
on subsequent coordinate-system -specific commands sent over this port until a different coordinate
system is addressed with another &{constant} command.
Other communications ports may be addressing different coordinate systems at the same time, as set by
&{constant} commands sent over those ports. In addition, each background PLC program can
individually modally address a coordinate system using the ADDRESS statement for subsequent
COMMAND statements, and the hardware control panel on a Turbo PMAC can separately select a
coordinate system for its hardware inputs.
Note:
In firmware versions 1.934 and older, all communications ports addressed the
same coordinate system, so an &{constant} command sent over any port set
the addressed coordinate system for all ports.
Example:
&1B4R ; C.S.1 point to Beginning of Prog 4 and Run
Q ; C.S.1 Quit running program
&3B6R ; C.S.3 point to Beginning of Prog 5 and Run
A ; C.S.3 Abort program
See Also:
I-variable I2
On-line commands #, #{constant}, &
Program commands ADDRESS, COMMAND
\
Function: Quick Stop in Lookahead / Feed Hold
Scope: Coordinate-system specific
Syntax: \
This command causes the Turbo PMAC to calculate and execute the quickest stop within the lookahead
buffer for the addressed coordinate system that does not violate acceleration constraints for any motor
within the coordinate system. Motion will continue to a controlled stop along the programmed path, but
the stop will not necessarily be at a programmed point.
The \ quick-stop command is generally the best command to stop motion interactively within lookahead.
Its function is much like that of a traditional feed-hold command, but unlike the regular H feed-hold
command in Turbo PMAC, it is guaranteed to observe constraints.
Note:
The use of DWELL, WHILE({condition})WAIT, and a violation of the double-
jump-back rule momentarily switches PMAC out of lookahead mode. Therefore,
these constructs should not be used in programs and sub-programs when the \
quick-stop command will be used to control their lookahead state.
Once stopped, several options are possible:
Jog axes away with any of the jogging commands. The on-line jog commands can be used to jog any
of the motors in the coordinate system away from the stopped point. However, before execution of
the programmed path can be resumed, all motors must be returned to the original stopping point with
the J= command.
Start reverse execution along the path with the < command.
Resume forward execution with the >, R, or S command.
End program execution with the A command.
This same functionality can be obtained from within a Turbo PMAC program by setting Isx21 to 4, which
executes more quickly than CMD “&n\”.
If the \ command is given to a coordinate system that is not currently executing moves within the
lookahead buffer, Turbo PMAC will execute the H feed-hold command instead.
See Also:
I-variables Isx13, Isx20, Isx21
On-line commands <, >, /, A, H, J=, R, S
<
Function: Back up through Lookahead Buffer
Scope: Coordinate-system specific
Syntax: <
This command causes the Turbo PMAC to start reverse execution in the lookahead buffer for the
addressed coordinate system. If the program is currently executing in the forward direction, it will be
brought to a quick stop (the equivalent of the \ command) first.
Execution proceeds backward through points buffered in the lookahead buffer, observing velocity and
acceleration constraints just as in the forward direction. This execution continues until one of the
following occurs:
Reverse execution reaches the beginning of the lookahead buffer – the oldest stored point still
remaining in the lookahead buffer – and it comes to a controlled stop at this point, observing
acceleration limits in decelerating to a stop.
The \ quick-stop command is given, which causes Turbo PMAC to come to the quickest possible
stop in the lookahead buffer.
The > resume-forward, R run, or S step command is given, which causes Turbo PMAC to resume
normal forward execution of the program, adding to the lookahead buffer as necessary.
An error condition occurs, or a non-recoverable stopping command is given.
If any motor has been jogged away from the quick-stop point, and not returned with a J= command,
Turbo PMAC will reject the < back-up command, reporting ERR017 if I6 is set to 1 or 3.
This same functionality can be obtained from within a Turbo PMAC program by setting Isx21 to 7, which
executes more quickly than CMD “&n<”.
If the coordinate system is not currently in the middle of a lookahead sequence, Turbo PMAC will treat
this command as an H feed-hold command.
See Also:
I-variables Isx13, Isx20, Isx21
On-line commands \, >, /, A, H, J=, R, S
>
Function: Resume Forward Execution in Lookahead Buffer
Scope: Coordinate-system specific
Syntax: >
This command causes the Turbo PMAC to resume forward execution in the lookahead buffer for the
addressed coordinate system. Typically, it is used to resume normal operation after a \ quick-stop
command, or a < back-up command. If the program is currently executing in the backward direction, it
will be brought to a quick stop (the equivalent of the \ command) first.
If previous forward execution had been in continuous mode (started with the R command), the >
command will resume it in continuous mode. If previous forward execution had been in single-step mode
(started with the S command), the > command will resume it in single-step mode.
The R and S commands can also be used to resume forward execution, but they may change the
continuous/single-step mode.
Deceleration from a backward move (if any) and acceleration in the forward direction observe the Ixx17
acceleration limits.
If any motor has been jogged away from the quick-stop point, and not returned with a J= command,
Turbo PMAC will reject the > resume command, reporting ERR017 if I6 is set to 1 or 3.
This same functionality can be obtained from within a Turbo PMAC program by setting Isx21 to 6, which
executes more quickly than CMD “&n>”.
If the coordinate system is not currently in the middle of a lookahead sequence, Turbo PMAC will treat
this command as an R run command.
See Also:
I-variables Isx13, Isx20, Isx21
On-line commands \, <, /, A, H, J=, R, S
/
Function: Halt Motion at End of Block
Scope: Coordinate-system specific
Syntax: /
This command causes PMAC to halt the execution of the motion program running in the currently
addressed coordinate system at the end of the currently executing move, provided the coordinate system is
in segmentation mode (Isx13 > 0). If the coordinate system is not in segmentation mode (Isx13 = 0), the
/ end-block command has the same effect as the Q or S command. It will halt execution at the end of the
latest calculated move, which can be 1 or 2 moves past the currently executing move.
If the coordinate system is currently executing moves with the special lookahead function, motion will stop
at the end of the move currently being added to the lookahead buffer. This is not necessarily the move that
is currently executing from the lookahead buffer, and there can be a significant delay before motion is
halted. Acceleration limits will be observed while ramping down to a stop at the programmed point.
Once halted at the end of the move, program execution can be resumed with the R run or S single-step
command. In the meantime, the individual motors may be jogged way from this point, but they must all
be returned to this point using the J= command before program execution may be resumed.
An attempt to resume program execution from a different point will result in an error (ERR017 reported if
I6 = 1 or 3). If resumption of this program from this point is not desired, the A (abort) command should
be issued before other programs are run.
See Also:
I-variables Isx13, Isx20, Isx21
On-line commands \, <, >, A, H, J=, R, S
?
Function: Report motor status words
Scope: Motor specific
Syntax: ?
This command causes Turbo PMAC to report the motor status bits as an ASCII hexadecimal word.
Turbo PMAC returns twelve characters, representing two status words. Each character represents four
status bits. The first character represents Bits 20-23 of the first word; the second shows Bits 16-19; and
so on, to the sixth character representing Bits 0-3. The seventh character represents Bits 20-23 of the
second word; the twelfth character represents Bits 0-3.
If the Turbo PMAC is in bootstrap mode (suitable for the downloading of new firmware) instead of the
normal operational mode, its response to this command will simply be BOOTSTRAP PROM.
The value of a bit is 1 when the condition is true; 0 when it is false. The meaning of the individual bits is:
First Word Returned (X:$0000B0, X:$000130, etc.):
First character returned:
Bit 23 Motor Activated: This bit is 1 when Ixx00 is 1 and the motor calculations are active; it is 0 when
Ixx00 is 0 and motor calculations are deactivated.
Bit 22 Negative End Limit Set: This bit is 1 when motor actual position is less than the software
negative position limit (Ixx14), or when the hardware limit on this end (+LIMn on Turbo PMAC1 – note)
has been tripped; it is 0 otherwise. If the motor is deactivated (bit 23 of the first motor status word set to
zero) or killed (bit 19 of the first motor status word set to zero), this bit is not updated.
Bit 21 Positive End Limit Set: This bit is 1 when motor actual position is greater than the software
positive position limit (Ixx13), or when the hardware limit on this end (-LIMn – note!) has been tripped; it
is 0 otherwise. If the motor is deactivated (bit 23 of the first motor status word set to zero) or killed (bit
14 of the second motor status word set to zero), this bit is not updated.
Bit 20 Extended Servo Algorithm Enabled: This bit is 1 when Iyy00/Iyy50 for the motor is set to 1 and
the extended servo algorithm for the motor is selected. It is 0 when Iyy00/Iyy50 is 0 and the PID servo
algorithm is selected.
Bit 5 Following Offset Mode: This bit is 1 when Ixx06 bit 1 is 1 and position following is executed in
“offset mode”, in which the motor’s programming reference position moves with the following. This bit
is 0 when Ixx06 bit 1 is 0 and position following is executed in “normal mode”, in which the motor’s
programming reference does not move with the following.
Bit 4 Following Enabled: This bit is 1 when Ixx06 bit 0 is 1 and position following for this axis is
enabled; it is 0 when Ixx06 bit 0is 0 and position following is disabled.
Sixth character returned:
Bit 3 Error Trigger: This bit is 1 when Ixx97 bit 1 is set to 1 and the motor’s triggered moves trigger
on the warning following error limit being exceeded. Itis 0 when Ixx97 bit 1 is set to 0 and the motor’s
triggered moves trigger on a specified input flag state.
Bit 2 Software Position Capture: This bit is 1 when Ixx97 bit 0 is set to 1 and the motor’s triggered
moves use a software-captured position as the reference for the post-trigger move. It is 0 when Ixx97 bit
0 is set to 0 and the motor’s triggered moves use the hardware-captured counter position as the reference
for the post-trigger move.
Bit 1 Integrator in Velocity Loop: This bit is 1 when bit 1 of Ixx96 is set to 1 and the PID integrator is
inside the velocity loop, acting on the velocity error. This bit is 0 when bit 1 of Ixx96 is 0 and the PID
integrator is in the position loop, acting on the position error. (In firmware revisions V1.940 and older,
this status bit was bit 0 of Ixx96.)
Bit 0 Alternate Command-Output Mode: This bit is 1 when bit 0 of Ixx96 is set to 1 and the motor’s
commands are output in the alternate mode. If Ixx01 bit 0 is 1, this means that open-loop direct-
microstepping commutation is performed instead of the normal closed-loop commutation. If Ixx01 bit 0 is
0, this means that the motor’s non-commutated output is formatted as a sign-and-magnitude signal pair,
instead of a single bipolar signal output. This bit is 0 when bit 0 of Ixx96 is set to 0 and the motor’s
commands are output in the standard mode. (In firmware revisions V1.940 and older, this status bit was
the Ixx90 rapid speed control.)
Second Word Returned (Y:$0000C0, Y:$000140, etc.):
Seventh character returned:
Bits 20-23 (C.S. - 1) Number: These three bits together hold a value equal to the (Coordinate System
number minus one) to which the motor is assigned. Bit 23 is the MSB, and bit 20 is the LSB. For
instance, if the motor is assigned to an axis in C. S. 6, these bits would hold a value of 5: bit 23 = 0, bit 22
= 1, bit 21 = 0, and bit 20 = 1.
Eighth character returned:
Bits 16-19 Coordinate Definition: These four bits tell what axis or axes this motor has been
assigned to in an axis definition statement. The following values are currently used:
0: No definition
1: Assigned to A-axis
2: Assigned to B-axis
3: Assigned to C-axis
4: Assigned to UVW axes
7: Assigned to XYZ axes
Ninth Character Returned:
Bit 15 Assigned to C.S.: This bit is 1 when the motor has been assigned to an axis in any coordinate
system through an axis definition statement. It is 0 when the motor is not assigned to an axis in any
coordinate system.
Bit 14 (Reserved for future use)
Bit 13 Foreground In-Position: This bit is 1 when the foreground in-position checking is enabled with
I13=1 and when four conditions are satisfied: the loop is closed, the desired velocity zero bit is 1 (which
requires closed-loop control and no commanded move); the program timer is off (not currently executing
any move, DWELL, or DELAY), and the magnitude of the following error is smaller than Ixx28. It is 0
otherwise.
Bit 12 Stopped on Desired Position Limit: This bit is 1 if the motor has stopped because the desired
position has exceeded the software overtravel limit parameters (Ixx24 bit 15 must be 1 to enable this
function). It is 0 otherwise.
Tenth Character Returned:
Bit 11 Stopped on Position Limit: This bit is 1 if this motor has stopped because of either a software or
a hardware position (overtravel) limit, even if the condition that caused the stop has gone away. It is 0 at
all other times, even when into a limit but moving out of it.
Bit 10 Home Complete: This bit, set to 0 on power-up or reset, becomes 1 when the homing move
successfully locates the home trigger. Usually, at this point in time the motor is decelerating to a stop or
moving to an offset from the trigger determined by Ixx26. If a second homing move is done, this bit is set
to 0 at the beginning of the move, and only becomes 1 again if that homing move successfully locates the
home trigger. Use the Desired Velocity Zero bit and/or the In Position bit to monitor for the end of motor
motion.
Bit 9 Phasing Search/Read Active: This bit is set to 1 if the phasing search move or phasing absolute
position read is currently ongoing for the motor. It is set to 0 otherwise.
Bit 8 Phasing Reference Error: This bit is set to 1 on power-up/reset for a PMAC-commutated (Ixx01
bit 0 = 1) synchronous motor. It is also set to 1 at the beginning of a phasing search move or phasing
absolute position read for such a motor. It is set to 0 on the successful completion of a phasing search
move or phasing absolute position read. If this bit is 1, the position/velocity servo loop cannot be closed
for this motor.
This bit is set to 1 if the phasing search move for a Turbo PMAC-commutated motor has failed due to
amplifier fault, overtravel limit, or lack of detected motion. It is set to 0 if the phasing search move did
not fail by any of these conditions (not an absolute guarantee of a successful phasing search).
Eleventh Character Returned:
Bit 7 Trigger Move: This bit is set to 1 at the beginning of a jog-until-trigger or motion program move-
until-trigger. It is set to 0 on finding the trigger (at the beginning of the post-trigger move section), but
remains at 1 if the move ends with no trigger found. This bit is useful to determine whether the move was
successful in finding the trigger.
Bit 6 Integrated Fatal Following Error: This bit is 1 if this motor has been disabled due to an
integrated following error fault, as set by Ixx11 and Ixx63. The fatal following error bit (bit 2) will also
be set in this case. Bit 6 is zero at all other times, becoming 0 again when the motor is re-enabled.
Bit 5 I2T Amplifier Fault Error: This bit is 1 if this motor has been disabled by an integrated current
fault. The amplifier fault bit (bit 3) will also be set in this case. Bit 5 is 0 at all other times, becoming 0
again when the motor is re-enabled.
Bit 4 Backlash Direction Flag: This bit is 1 if backlash has been activated in the negative direction. It
is 0 otherwise.
Twelfth Character Returned:
Bit 3 Amplifier Fault Error: This bit is 1 if this motor has been disabled because of an amplifier fault
signal, even if the amplifier fault signal has gone away, or if this motor has been disabled due to an I2T
integrated current fault (in which case bit 5 is also set). It is 0 at all other times, becoming 0 again when
the motor is re-enabled.
Bit 2 Fatal Following Error: This bit is 1 if this motor has been disabled because it exceeded its fatal
following error limit (Ixx11) or because it exceeded its integrated following error limit (Ixx63; in which
case bit 6 is also set). It is 0 at all other times, becoming 0 again when the motor is re-enabled.
Bit 1 Warning Following Error: This bit is 1 if the following error for the motor exceeds its warning
following error limit (Ixx12). It stays at 1 if the motor is killed due to fatal following error. It is 0 at all
other times, changing from 1 to 0 when the motor's following error reduces to under the limit, or if killed,
is re-enabled.
Bit 0 In Position: This bit is 1 when five conditions are satisfied: the loop is closed, the desired
velocity zero bit is 1 (which requires closed-loop control and no commanded move); the program timer is
off (not currently executing any move, DWELL, or DELAY), the magnitude of the following error is
smaller than Ixx28 and the first four conditions have been satisfied for (Ixx88+1) consecutive scans.
Example:
#1? ; Request status of Motor 1
81200001C401 ; PMAC responds with 12 hex digits representing 48 bits
; The following bits are true (all others are false):
; Word 1 Bit 23: Motor Activated
; Bit 16: Integration Mode
; Bit 13: Desired Velocity Zero
; Word 2 (Bits 20-23 all 0 – assigned to C.S.1)
; (Bits 16-19 form 1 – assigned to A-axis)
; Bit 15: Assigned to Coordinate System
; Bit 14: Amplifier Enabled
; Bit 10: Home Complete
; Bit 0: In Position
See Also:
On-line commands <CTRL-B>, ??, ???
Memory-map registers X:$0000B0, X:$000130, etc., Y:$0000C0, Y:$000140, etc.;
Suggested M-Variable definitions Mxx30-Mxx45.
??
Function: Report the status words of the addressed coordinate system.
Scope: Coordinate-system specific
Syntax: ??
This command causes Turbo PMAC to report status bits of the addressed coordinate system as an ASCII
hexadecimal word. Turbo PMAC returns eighteen characters, representing three 24-bit status words.
Each character represents four status bits. The first character represents bits 20-23 of the first word; the
second shows bits 16-19; and so on, to the sixth character representing bits 0-3. The seventh character
represents bits 20-23 of the second word; the twelfth character represents bits 0-3.
If the Turbo PMAC is in bootstrap mode (suitable for the downloading of new firmware) instead of the
normal operational mode, its response to this command will simply be BOOTSTRAP PROM.
The value of a bit is 1 when the condition is true; 0 when it is false. The meanings of the individual bits are:
First Word Returned (X:$002040, X:$0020C0, etc.)
First character returned:
Bit 23 Z-Axis Used in Feedrate Calculations: This bit is 1 if this axis is used in the vector feedrate
calculations for F-based moves in the coordinate system; it is 0 if this axis is not used. See the FRAX
command.
Bit 22 Z-Axis Incremental Mode: This bit is 1 if this axis is in incremental mode -- moves specified by
distance from the last programmed point. It is 0 if this axis is in absolute mode -- moves specified by end
position, not distance. See the INC and ABS commands.
Bit 21 Y-Axis Used in Feedrate Calculations: (See bit 23 description.)
Bit 20 Y-Axis Incremental Mode: (See bit 22 description.)
Second character returned:
Bit 19 X-Axis Used in Feedrate Calculations: (See bit 23 description.)
Bit 18 X-Axis Incremental Mode: (See bit 22 description.)
Bit 20 Amplifier Fault Error: This bit is 1 when any motor in the coordinate system has been killed due
to receiving an amplifier fault signal. It is 0 at other times, changing from 1 to 0 when the offending
motor is re-enabled.
Eighth character returned:
Bit 19 Fatal Following Error: This bit is 1 when any motor in the coordinate system has been killed
due to exceeding its fatal following error limit (Ixx11). It is 0 at other times. The change from 1 to 0
occurs when the offending motor is re-enabled.
Bit 18 Warning Following Error: This bit is 1 when any motor in the coordinate system has exceeded
its warning following error limit (Ixx12). It stays at 1 if a motor has been killed due to fatal following
error limit. It is 0 at all other times. The change from 1 to 0 occurs when the offending motor's following
error is reduced to under the limit, or if killed on fatal following error as well, when it is re-enabled.
Bit 17 In Position: This bit is 1 when all motors in the coordinate system are in position. Five
conditions must apply for all of these motors for this to be true:, the loops must be closed, the desired
velocity must be zero for all motors, the coordinate system cannot be in any timed move (even zero
distance) or DWELL, all motors must have a following error smaller than their respective Ixx28 in-position
bands, and the above conditions must have been satisfied for (Ixx88+1) consecutive scans.
Bit 16 Rotary Buffer Request: This bit is 1 when a rotary buffer exists for the coordinate system and
enough program lines have been sent to it so that the buffer contains at least I17 lines ahead of what has
been calculated. Once this bit has been set to 1 it will not be set to 0 until there are less than I16 program
lines ahead of what has been calculated. The PR command may be used to find the current number of
program lines ahead of what has been calculated.
Ninth character returned:
Bit 15 Delayed Calculation Flag: (for internal use)
Bit 14 End of Block Stop: This bit is 1 when a motion program running in the currently addressed
Coordinate System is stopped using the ' / ' command from a segmented move (Linear or Circular mode
with Isx13 > 0).
Bit 13 Synchronous M-variable One-Shot: (for internal use)
Bit 12 Dwell Move Buffered: (for internal use)
Tenth character returned:
Bit 11 Cutter Comp Outside Corner: This bit is 1 when the coordinate system is executing an added
outside corner move with cutter compensation on. It is 0 otherwise.
Bit 10 Cutter Comp Move Stop Request: This bit is 1 when the coordinate system is executing moves
with cutter compensation enabled, and has been asked to stop move execution. This is primarily for
internal use.
Bit 9 Cutter Comp Move Buffered: This bit is 1 when the coordinate system is executing moves with
cutter compensation enabled, and the next move has been calculated and buffered. This is primarily for
internal use.
Bit 8 Cutter Comp Move Executing: This bit is 1 when the coordinate system is executing a move
with cutter compensation on. It is 0 otherwise.
Eleventh character returned:
Bit 7 Segmented Move in Progress: This bit is 1 when the coordinate system is executing motion
program moves in segmentation mode (Isx13>0). It is 0 otherwise. This is primarily for internal use.
Bit 6 Segmented Move Acceleration: This bit is 1 when the coordinate system is executing motion
program moves in segmentation mode (Isx13>0) and accelerating from a stop. It is 0 otherwise. This is
primarily for internal use.
Bit 5 Segmented Move Stop Request: This bit is 1 when the coordinate system is executing motion
program move in segmentation mode (Isx13>0) and it is decelerating to a stop. It is 0 otherwise. This is
primarily for internal use.
Bit 4 PVT/SPLINE Move Mode: This bit is 1 if this coordinate system is in either PVT move mode or
SPLINE move mode. (If bit 0 of this word is 0, this means PVT mode; if bit 0 is 1, this means SPLINE
mode.) This bit is 0 if the coordinate system is in a different move mode (LINEAR, CIRCLE, or
RAPID). See the table below.
Twelfth character returned:
Bit 3 2D Cutter Comp Left/3D Cutter Comp On: With bit 2 equal to 1, this bit is 1 if the coordinate
system has 2D cutter compensation on, compensating to the left when looking in the direction of motion.
It is 0 if 2D compensation is to the right. With bit 2 equal to 0, this bit is 1 if the coordinate system has
3D cutter compensation on. It is 0 if no cutter compensation is on.
Bit 2 2D Cutter Comp On: This bit is 1 if the coordinate system has 2D cutter compensation on. It is
0 if 2D cutter compensation is off (but 3D cutter compensation may be on if bit 3 is 1).
Bit 1 CCW Circle\Rapid Mode: When bit 0 is 1 and bit 4 is 0, this bit is set to 0 if the coordinate
system is in CIRCLE1 (clockwise arc) move mode and 1 if the coordinate system is in CIRCLE2
(counterclockwise arc) move mode. If both bits 0 and 4 are 0, this bit is set to 1 if the coordinate system
is in RAPID move mode. Otherwise this bit is 0. See the table below.
Bit 0 CIRCLE/SPLINE Move Mode: This bit is 1 if the coordinate system is in either CIRCLE or
SPLINE move mode. (If bit 4 of this word is 0, this means CIRCLE mode; if bit 4 is 1, this means
SPLINE mode.) This bit is 0 if the coordinate system is in a different move mode (LINEAR, PVT, or
RAPID.). See the table below.
The states of bits 4, 1, and 0 in the different move modes are summarized in the following table:
Mode Bit 4 Bit 1 Bit 0
LINEAR 0 0 0
RAPID 0 1 0
SPLINE 1 0 1
CIRCLE1 0 0 1
CIRCLE2 0 1 1
PVT 1 1 0
Third Word Returned (Y:$002040, Y:$0020C0, etc.)
Thirteenth character returned:
Bit 23 Lookahead Buffer Wrap: This bit is 1 when the lookahead buffer for the coordinate system is
active and has “wrapped around” since the beginning of the current continuous motion sequence, meaning
that retrace back to the beginning of the sequence is no longer possible. It is 0 otherwise.
Bit 22 Lookahead Lookback Active: (For internal use)
Bit 21 Lookahead Buffer End: (For internal use)
Bit 20 Lookahead Synchronous M-variable: (For internal use)
Fourteenth character returned:
Bit 19 Lookahead Synchronous M-variable Overflow: This bit is 1 if the program has attempted to put
more synchronous M-variable assignments into the lookahead buffer than the buffer has room for. If this
bit is set, one or more synchronous M-variable assignments have failed to execute or will fail to execute.
Bit 18 Lookahead Buffer Direction: This bit is 1 if the lookahead buffer is executing in the reverse
direction, or has executed a quick stop from the reverse direction. It is 0 if the lookahead buffer is
executing in the forward direction, has executed a quick stop for the forward direction, or is not executing.
Bit 17 Lookahead Buffer Stop: This bit is 1 if the lookahead buffer execution is stopping due to a
quick-stop command or request. It is 0 otherwise.
Bit 16 Lookahead Buffer Change: This bit is 1 if the lookahead buffer is currently changing state
between forward and reverse direction, or between executing and stopped. It is 0 otherwise.
Fifteenth character returned:
Bit 15 Lookahead Buffer Last Segment: This bit is 1 if the lookahead buffer is currently executing the
last segment before the end of a sequence. It is 0 otherwise.
Bit 14 Lookahead Buffer Recalculate: This bit is 1 if the lookahead buffer is recalculating segments
already in the buffer due to a change in the state of the buffer. It is 0 otherwise.
Bit 13 Lookahead Buffer Flush: This bit is 1 if the lookahead buffer is executing segments but not
adding any new segments. It is 0 otherwise.
Bit 12 Lookahead Buffer Last Move: This bit is 1 if the last programmed move in the buffer has
reached speed. It is 0 otherwise.
Sixteenth character returned:
(Bits 8 – 11 form variable Isx21.)
Bit 11 Lookahead Buffer Single-Segment Request: This bit can be set to 1 by the user as part of a
request to change the state of the lookahead buffer. It should be set to 1 to request the buffer to move
only a single segment from a stopped state (in either direction). It should be set to 0 otherwise. Turbo
PMAC leaves this bit in the state of the last request, even after the request has been processed.
Bit 10 Lookahead Buffer Change Request: This bit can be set to 1 by the user to request a change in
the state of the lookahead buffer. It remains at 1 until the Turbo PMAC processes the change, at which
time Turbo PMAC changes it to 0.
Bit 9 Lookahead Buffer Movement Request: This bit can be set by the user as part of a request to
change the state of the lookahead buffer. It should be set to 1 to request the buffer to operate (in either the
forward or reverse direction); it should be set to 0 to request the buffer to execute a quick stop. Turbo
PMAC leaves this bit in the state of the last request, even after the request has been processed.
Bit 8 Lookahead Buffer Direction Request: This bit can be set by the user as part of a request to
change the state of the lookahead buffer. It should be set to 1 to request operation in the reverse direction;
it should be set to 0 to request operation in the forward direction. Its state does not matter in a request to
execute a quick stop. Turbo PMAC leaves this bit in the state of the last request, even after the request
has been processed.
Seventeenth character returned:
Bits 4 – 7 (Reserved for future use)
Eighteenth character returned:
Bit 3 Radius Error: This bit is 1 when a motion program has been stopped because it was asked to do
an arc move whose distance was more than twice the radius (by an amount greater than Ixx96).
Bit 2 Program Resume Error: This bit is 1 when the user has tried to resume program operation after
a feed-hold or quick-stop, but one or more of the motors in the coordinate system are not at the location of
the feed-hold or quick-stop. It is 0 otherwise.
Bit 1 Desired Position Limit Stop: This bit is 1 if the motion program in the coordinate system has
stopped due to the desired position of a motor exceeding a limit.
Bit 0 In-Program PMATCH: This bit is 1 if Turbo PMAC is executing the PMATCH function
automatically, as at the end of a move-until-trigger. It is 0 otherwise. This bit is primarily for internal use.
Example:
?? ; Request coordinate system status words
A8002A020010000000
; Turbo PMAC responds; the following bits are true:
; Word 1 Bit 23: Z-axis used in feedrate calcs
; Bit 21: Y-axis used in feedrate calcs
; Bit 19: X-axis used in feedrate calcs
; Bit 5: Radius vector incremental mode
; Bit 3: Move specified by time
; Bit 1: Single-step mode
; Word 2 Bit 17: In-position
; Bit 4: PVT/Spline mode
; Word 3 no bits set – no lookahead active
See Also:
On-line commands <CONTROL-C>, ?, ???
Memory-map registers X/Y:$002040, X/Y:$0020C0, etc., Y:$00203F, Y:$0020BF, etc.;
Suggested M-variable definitions Msx80-Msx90.
???
Function: Report global status words
Scope: Global
Syntax: ???
This command causes Turbo PMAC to return the global status bits in ASCII hexadecimal form. Turbo
PMAC returns twelve characters, representing two status words. Each character represents four status
bits. The first character represents Bits 20-23 of the first word, the second shows Bits 16-19; and so on,
to the sixth character representing Bits 0-3. The seventh character represents Bits 20-23 of the second
word; the twelfth character represents Bits 0-3 of the second word.
If the Turbo PMAC is in “bootstrap mode” (suitable for the downloading of new firmware) instead of the
normal operational mode, its response to this command will simply be BOOTSTRAP PROM.
A bit has a value of 1 when the condition is true; 0 when false. The meaning of the individual status bits is:
First Word Returned (X:$000006):
First character returned:
Bit 23 (Reserved for future use)
Bit 22 Real-Time Interrupt Re-entry: This bit is 1 if a real-time interrupt task has taken long enough so
that it was still executing when the next real-time interrupt came (I8+1 servo cycles later). It stays at 1
until the card is reset, or until this bit is manually changed to 0. If motion program calculations cause this
it is not a serious problem. If PLC 0 causes this (no motion programs running) it could be serious.
Bit 21 CPU Type Bit 1: This bit is 1 if the Turbo PMAC has an Option 5Ex DSP56311 or an Option
5Fx DSP56321 processor. It is 0 if it has an Option 5Cx DSP56303 or an Option 5Dx DSP56309
processor. In both cases, bit 21 in the second word returned (Y:$000006) distinguishes between
processor types.
Bit 20 Servo Error: This bit is 1 if Turbo PMAC could not properly complete its servo routines. This is
a serious error condition. It is 0 if the servo operations have been completing properly.
Second character returned:
Bit 19 Data Gathering Function On: This bit is 1 when the data gathering function is active; it is 0
when the function is not active.
Bit 18 (Reserved for future use)
Bit 17 Data Gather to Start on Trigger: This bit is 1 when the data gathering function is set up to start
on the rising edge of Machine Input 2. It is 0 otherwise. It changes from 1 to 0 as soon as the gathering
function actually starts.
Bit 16 Servo Request: (Internal use).
Third character returned:
Bit 15 Watchdog Timer: (Internal use)
Bit 14 Leadscrew Compensation On: This bit is 1 if leadscrew compensation is currently active in
Turbo PMAC. It is 0 if the compensation is not active.
Bit 13 Any Memory Checksum Error: This bit is 1 if a checksum error has been detected for either the
Turbo PMAC firmware or the user program buffer space. Bit 12 of this word distinguishes between the
two cases.
Bit 12 PROM Checksum Active: This bit is 1 if Turbo PMAC is currently evaluating a firmware
checksum (Bit 13 = 0), or has found a firmware checksum error (Bit 13 = 1). It is 0 if Turbo PMAC is
evaluating a user program checksum (Bit 13 = 0), or has found a user program checksum error (Bit 13 = 1).
Fourth character returned:
Bit 11 DPRAM Error: This bit is 1 if Turbo PMAC detected an error in its automatic DPRAM check
function at power-up/reset due to missing or defective DPRAM. It is 0 otherwise.
Bit 10 Flash Error: This bit is 1 if Turbo PMAC detected a checksum error in reading saved data from
the flash memory on board reset. It is 0 otherwise.
Bit 9 Real-Time Interrupt Warning: This bit is 1 if a real-time interrupt task (motion program or PLC
0) has taken more than one interrupt period – a possible sign of CPU loading problems. It is 0 otherwise.
Bit 8 Illegal L-Variable Definition: This bit is 1 if a compiled PLC has failed because it used an L-
variable pointer that accessed an illegal M-variable definition. It is 0 otherwise.
Fifth character returned:
Bit 7 Configuration Error: This bit is 1 if the Turbo PMAC detects a change in the configuration of
Servo and MACRO ICs since the last re-initialization, or if the MACRO ring reports a conflict in the
node configuration (multiple active nodes at the same ring address). It is 0 otherwise. If this bit is set to 1,
no motors can be enabled.
Bit 6 TWS Variable Parity Error: This bit is 1 if the most recent TWS-format M-variable read or
write operation with a device supporting parity had a parity error; it is 0 if the operation with such a
device had no parity error. The bit status is indeterminate if the operation was with a device that does not
support parity.
Bit 5 MACRO Auxiliary Communications Error: This bit is 1 if the most recent MACRO auxiliary
read or write command has failed. It is set to 0 at the beginning of each MACRO auxiliary read or write
command.
Bit 4 MACRO Ring Check Error: This bit is 1 if the MACRO ring check function is enabled (I80 > 0)
and Turbo PMAC has either detected at least I81 ring communication errors in an I80-servo-cycle period,
or has failed to detect the receipt of I82 ring sync packets.
Sixth character returned:
Bit 3 Phase Clock Missing: This bit is set to 1 if the CPU received no hardware-generated phase clock
from a source external to it (Servo IC, MACRO IC, or through serial port). If this bit is set, no motor may
be enabled (starting in V1.940). This bit is 0 otherwise.
Bit 2 (Reserved for future use)
Bit 1 All Cards Addressed: This bit is set to 1 if all cards on a serial daisychain have been addressed
simultaneously with the @@ command. It is 0 otherwise.
Bit 0 This Card Addressed: This bit is set to 1 if this card is on a serial daisychain and has been
addressed with the @n command. It is 0 otherwise.
Second Word Returned (Y:$000006)
Seventh character returned:
Bit 23 Turbo Ultralite: This bit is 1 if Turbo PMAC has detected that it is an Ultralite PMAC2 with no
Servo ICs on board. It is 0 if Turbo PMAC has detected that it has Servo ICs on board.
Bit 22 Turbo VME: This bit is 1 if Turbo PMAC has detected that it has a VME bus interface on board.
It is 0 otherwise.
Bit 21 CPU Type Bit 0: This bit is 1 if the Turbo PMAC has an Option 5Dx DSP56309 or an Option 5Fx
DSP56321 processor. It is 0 if it has an Option 5Cx DSP56303 or an Option 5Dx DSP56311 processor. In
both cases, bit 21 in the first word returned (X:$000006) distinguishes between processor types.
Bit 20 Binary Rotary Buffers Open: This bit is 1 if the rotary motion program buffers on Turbo PMAC
are open for binary-format entry through the DPRAM. It is 0 otherwise.
Eighth character returned:
Bit 19 Motion Buffer Open: This bit is 1 if any motion program buffer (PROG or ROT) is open for
entry. It is 0 if none of these buffers is open.
Bit 18 ASCII Rotary Buffer Open: This bit is 1 if the rotary motion program buffers on Turbo PMAC
are open for ASCII-format entry. It is 0 otherwise.
Bit 17 PLC Buffer Open: This bit is 1 if a PLC program buffer is open for entry. It is 0 if none of these
buffers is open.
Bit 16 UMAC System: This bit is 1 if the Turbo PMAC is a 3U Turbo system (UMAC or Stack). It is 0
otherwise.
This command causes all closed-loop motors defined in the addressed coordinate system to begin
immediately to decelerate to a stop, aborting the currently running motion program (if any). It also brings
any open-loop enabled motors in the coordinate system to an enabled zero-velocity closed-loop state at
the present position. If global I-variable I36 is set to 0, it will also enable any disabled motors in the
coordinate system, bringing them to a zero-velocity closed-loop state at the present position. However if
I36 is set to 1, it will have no effect on disabled motors; the E command should be used for these instead.
Each closed-loop motor in the coordinate system will decelerate from its present command velocity to
zero velocity at a rate defined by its own motor I-variable Ixx15. Note that a multi-axis system may not
stay on its programmed path during this deceleration. If the time-base (override) value for the coordinate
system is exactly 0% when the A command is given, the motor will abort at the present position even if
the command velocity is not zero; otherwise a ramp-down trajectory will be computed using Ixx15 and
executed using the override value.
An A (abort) stop to a program is not meant to be recovered from gracefully, because the axes will in
general not stop at a programmed point. An on-line J= command may be issued to each motor to cause it
to move to the end point that was programmed when the abort occurred. Then the program(s) can be
resumed with an R (run) command.
To stop a motion sequence in a manner that can be recovered from easily, use instead the Quit (Q or
<CTRL-Q>), the Hold (H or <CTRL-O>), the Quick Stop (\) or the Halt (/) commands.
Example
B1R.................. ; Start Motion Program 1
A ...................... ; Abort the program
#1J=#2J= ...... ; Jog motors to original move-end position
R ...................... ; Resume program with next move
See Also
Stop Commands (Making Your Application Safe)
Control-Panel Port STOP/ Input (Connecting Turbo PMAC to the Machine)
I-variables I36, Ixx15, Ixx80
On-line commands <CTRL-A>, <CTRL-E>, E, H, J/, K, Q
JPAN connector pin 10
ABR[{constant}]
Function: Abort currently running motion program and start another
Scope: Coordinate-system specific
Syntax: ABR[{constant}]
where:
{constant} is a numerical value whose integer part specifies the number of the program to be run,
and whose fractional part (if any) specifies the line label of that program where execution is to begin.
The ABR command permits a very quick end to the execution of one motion program and starting (or
restarting) of another (or the same) motion program. It performs the following tasks for the addressed
coordinate system, all in a unitary command:
It immediately stops execution of the currently running motion program in the addressed coordinate
system.
It brings the commanded trajectories of all motors in the coordinate system to stop at the rate set by
Ixx15 for each motor.
It points the coordinate system’s program counter to a specific location in that program or another
program. If stopping and resuming the rotary motion program buffer, it immediately clears the rotary
buffer of unexecuted lines.
As soon as the commanded trajectories of all motors in the coordinate system have stopped, it will
start execution of the newly addressed program (which could be the same program.
It is essentially a combination of the existing A (abort), B (point to beginning of program), and R (run)
commands. By combining these into a single command, all three actions are executed in a single
command cycle, speeding the transition.
If the ABR command is given without a numerical argument, Turbo PMAC will restart the presently
executing program at the top. If an ABR0 command is given, Turbo PMAC will end execution of the
currently executing program – if it is currently executing the rotary program buffer, clear the rotary buffer
– and point to the top of the rotary program buffer.
If an ABR{constant} command is given with a non-zero constant value, Turbo PMAC will start
execution of the program number specified by the integer part of the constant (valid values 1 – 32,767)
and at the numeric line label whose value is equal to the fractional part times 100,000 (10 5). If no
fractional part is specified, execution will start at the top of this program.
Examples:
ABR0 ; Stop execution of rotary buffer, clear, and restart at top
ABR20 ; Stop execution and start at top of program 20
ABR44.37 ; Stop execution and start at N37000 of program 44
ABS
Function: Select absolute position mode for axes in addressed coordinate system.
Scope: Coordinate-system specific
Syntax: ABS
ABS ({axis}[,{axis}...])
where:
{axis} is a letter (X, Y, Z, A, B, C, U, V, W) representing the axis to be specified, or the character
R to specify radial vector mode
No spaces are permitted in this command.
This command, without any arguments, causes all subsequent positions for all axes in the coordinate
system in motion commands to be treated as absolute positions (this is the default condition). An ABS
command with arguments causes the specified axes to be in absolute mode, and all others to remain
unchanged.
If R is specified as one of the 'axes', the I, J, and K terms of the circular move radius vector specification
will be specified in absolute form (i.e. as a vector from the origin, not from the move start point). An
ABS command without any arguments does not affect this vector specification. The default radial vector
specification is incremental.
If a motion program buffer is open when this command is sent to Turbo PMAC, the command will be
entered into the buffer for later execution.
Example:
ABS(X,Y) ; X and Y made absolute – other axes and radial vector left unchanged
ABS ; All axes made absolute – radial vector left unchanged
ABS(R) ; Radial vector made absolute – all axes left unchanged
See Also:
B{constant}
Function: Point the addressed coordinate system to a motion program.
Scope: Coordinate-system specific
Syntax: B{constant}
where:
{constant} is a floating point value from 0.0 to 32767.99999 representing the program and location to
point the coordinate system to; with the integer part representing the program number, and the fractional
part multiplied by 100,000 representing the line label (zero fractional part means the top of the program).
This command causes Turbo PMAC to set the program counter of the addressed coordinate system to the
specified motion program and location. It is usually used to set the program counter to the Beginning of a
motion program. The next R or S command will start execution at this point.
If {constant} is an integer, the program counter will point to the beginning of the program whose
number matches {constant}. Fixed motion program buffers (PROG) can have numbers from 1 to
32,767. The rotary motion program carries program number 0 for the purpose of this command.
If {constant} is not an integer, the fractional part of the number represents the line label (N or O) in
the program to which to point. The fractional value multiplied by 100,000 determines the number of the
line label to which to point (it fills the fraction to 5 decimal places with zeros).
Note:
If a motion program buffer (including ROTARY) is open when this command is
sent to Turbo PMAC, the command is entered into the buffer for later execution, to
be interpreted as a B-axis move command.
Example:
B7 ;points to the top of PROG 7
B0 ;points to the top of the rotary buffer
B12.6 ;points to label N60000 of PROG 12
B3.025R ;points to label N2500 of PROG 3 and runs
See Also:
On-line commands DEFINE ROT, R, S
Program commands B{data}, N{constant}, O{constant}.
CHECKSUM
Function: Report the firmware checksum value.
Scope: Global
Syntax: CHECKSUM
CHKS
This command causes Turbo PMAC to report the reference checksum value of the firmware revision that
it is using. The value is reported as a hexadecimal ASCII string. This value was computed during the
compilation of the firmware. It is mainly used for troubleshooting purposes.
The comparative checksum value that Turbo PMAC is continually computing by scanning the firmware
in active memory is stored in X:$001080. As long as there is no checksum error, this comparative value
is continually changing as PMAC continues its calculations. However, if during any pass of the
checksum calculations, if the final comparative checksum value does not agree with the reference value,
the calculations stop, and the final erroneous value is held in X:$001080.
Example:
CHECKSUM ; Request firmware reference checksum value
9FA263 ; Turbo PMAC returns hex value
See Also:
On-line commands DATE, VERSION
CID
Function: Report card ID or part number.
Scope: Global
Syntax: CID
This command causes Turbo PMAC to return the card’s part number. This can be used to confirm
exactly which type of Turbo PMAC is being used.
The currently existing types of Turbo PMAC and the values they return for CID are:
Turbo PMAC PC: 602191
Turbo PMAC VME: 602199
Turbo PMAC2 PC: 602404
Turbo PMAC2 VME: 602413
Turbo PMAC2 PC Ultralite: 603182
Turbo PMA2 PCI: 603367
3U Turbo PMAC2: 603382
See Also:
I-Variable I4909
On-line commands CPU, TYPE, VERSION, VID
CLEAR
Function: Erase currently opened buffer.
Scope: Port specific
Syntax: CLEAR
CLR
This command empties the program buffer (PROGRAM, PLC, ROTARY) that is currently opened on the
port over which the command is given. If used to empty an open rotary motion program buffer, it only
affects the buffer for the addressed coordinate system on that port.
If there is no open program buffer, or if the program buffer that is open was opened from another
communications port, the CLEAR command will be rejected with an error, reporting ERR007 if I6=1 or 3.
Note:
Prior to V1.936 firmware, an open buffer could be accessed from any port, and the
CLEAR command could be used on one port to empty a buffer that had been
opened on another port. Starting in V1.936, a CLEAR command could only be
used to empty a buffer opened from the same port.
Typically, as a buffer file is created in the host computer, start with the OPEN {buffer} and CLEAR
commands (even though these lines are technically not part of the buffer), and follow with the actual
contents. This will allow easy edit of the buffers from the host and repeated downloading of the buffers,
erasing the old buffer’s contents in the process.
Example:
OPEN PROG 1 ; Open motion program buffer 1
CLEAR ; Clear out this buffer
F1000 ; Program really starts here!
X2500 ;...and ends on this line!
CLOSE ; This closes the program buffer
OPEN PLC 3 CLEAR CLOSE ; This erases PLC 3
See Also:
Program Buffers (Talking to Turbo PMAC)
On-line commands OPEN, CLOSE, DELETE.
CLEAR ALL
Function: Erase all fixed motion, kinematic, and uncompiled PLC programs
Scope: Global
Syntax: CLEAR ALL
CLR ALL
This command causes Turbo PMAC to erase all fixed (not rotary) motion program buffers (PROGRAM),
all forward-kinematic program buffers (FORWARD), all inverse-kinematic program buffers (INVERSE),
and all uncompiled PLC program buffers (PLC) in the Turbo PMAC buffer space.
This command does not affect rotary motion program buffers (ROTARY), compiled PLC program buffers
(PLCC), or any non-program buffers, such as compensation tables and lookahead buffers.
See Also:
On-line commands CLEAR, CLEAR ALL PLCS, OPEN, DELETE ALL, DELETE ALL TEMP
CLEAR ALL PLCS
Function: Erase all uncompiled PLC programs
Scope: Global
Syntax: CLEAR ALL PLCS
CLR ALL PLCS
This command causes Turbo PMAC to erase all uncompiled PLC program buffers (PLC) in the Turbo
PMAC buffer space.
This command does not affect fixed motion program buffers (PROGRAM), forward-kinematic program
buffers (FORWARD), inverse-kinematic program buffers (INVERSE), rotary motion program buffers
(ROTARY), compiled PLC program buffers (PLCC), or any non-program buffers, such as compensation
tables and lookahead buffers.
See Also:
On-line commands CLEAR, CLEAR ALL, OPEN, DELETE ALL, DELETE ALL TEMP
CLOSE
Function: Close the currently opened buffer.
Scope: Global
Syntax: CLOSE
CLS
This command closes the program buffer (PROGRAM, PLC, ROTARY, BINARY ROTARY) that is
currently opened on the port over which the command is given. When Turbo PMAC receives a CLOSE
command, it automatically appends a RETURN statement to the end of the open program buffer. If used
to close open rotary motion program buffers, it closes the rotary program buffers for all coordinate
systems simultaneously.
If there is no open program buffer, or if the program buffer that is open was opened from another
communications port, the CLOSE command will be accepted, but no action will occur.
Note:
Prior to V1.936 firmware, an open buffer could be accessed from any port, and the
CLOSE command could be used on one port to close a buffer that had been opened
on another port. Starting in V1.936, if a CLOSE command could only be used to
close a buffer opened from the same port.
The CLOSE command should be used immediately after the entry of a motion, PLC, rotary, etc. buffer. If
the buffer is left open, subsequent statements that are intended as on-line commands (e.g. P1=0) will get
entered into the buffer instead. It is good practice to have CLOSE at the beginning and end of any file to
be downloaded to Turbo PMAC.
If the program buffer closed by the CLOSE command is improperly structured, structured (e.g. no ENDIF
or ENDWHILE to match an IF or WHILE), Turbo PMAC will report an error to the CLOSE command,
returning ERR009 if I6 is 1 or 3. However, the buffer will still be closed.
Example:
CLOSE ; This makes sure all buffers are closed
OPEN PROG 1 ; Open motion program buffer 1
CLEAR ; Clear out this buffer
F1000 ; Program actually starts here!...
X2500 ;...and ends on this line!
CLOSE ; This closes the program buffer
LIST PROG 1 ; Request listing of closed program
F1000 ; Turbo PMAC starts listing
X2500
RETURN ; This was appended by the CLOSE command
See Also:
Program Buffers (Talking to Turbo PMAC)
On-line commands OPEN, CLEAR, <CTRL-L>, <CTRL-U>
CLOSE ALL
Function: Close the currently opened buffer on any port
Scope: Global
Syntax: CLOSE ALL
CLS ALL
This command closes the program buffer (PROGRAM, PLC, ROTARY) that is currently opened,
regardless of the port over which the buffer was opened. When Turbo PMAC receives a CLOSE ALL
command, it automatically appends a RETURN statement to the end of the open program buffer (except
for rotary motion program buffers).
Note:
The similar CLOSE command can only affect a buffer that was opened on the same
port as which the CLOSE command is sent.
See Also:
On-line commands OPEN{buffer}, CLOSE
CLRF
Function: Clear faults on MACRO ring
Scope: Global
Syntax: CLRF
The CLRF command causes Turbo PMAC to send a command over the MACRO ring to clear any faults
on slave MACRO devices. The command is sent as a ring broadcast over Node 14 to all stations on the
MACRO ring. It is the “global” equivalent of the station-specific MS CLRFn command. It should only be
sent by the synchronizing master on the ring.
All stations receiving the command will clear any fault bits present and reset ring error counters to zero. If
a slave station had turned itself into a master to notify the synchronizing master of a ring break, it will
turn itself back into a slave. The Turbo PMAC sending the command will clear its own global “ring fault”
status bit and reset its ring-error counter (at Y:$343B) to zero.
Of course, if the underlying condition that caused the original fault is still present, fault bits can
immediately be set back to 1 and error counters incremented from zero.
{constant}
Function: Assign value to variable P0, or to table entry.
Scope: Global
Syntax: {constant}
where:
{constant} is a floating-point value
This command is the equivalent of P0={constant}. That is, a value entered by itself on a command
line will be assigned to P-variable P0. This allows simple operator entry of numeric values through a
dumb terminal interface. Where the value goes is hidden from the operator; the Turbo PMAC user
program must take P0 and use it as appropriate.
Note:
If a compensation table on Turbo PMAC (BLCOMP, COMP, or TCOMP) has been
defined but not filled, a constant value will be entered into this table, not into P0.
Example:
In a motion program:
P0=-1 ; Set P0 to an illegal value
SEND"Enter number of parts in run:"
; Prompt operator at dumb terminal
; Operator simply needs to type in number
WHILE (P0<1) DWELL10 ; Hold until get legal response
P1=0 ; Initialize part counter
WHILE (P0<P1) ; Loop once per part
P1=P1+1
...
P0=1 ; Temporary value for P0
#1DEFINE COMP 5,2000 ; Set up 5-entry table
32 48 –96 64 0 –1 ; Firt 5 numbers into table; sixth into P0
P0 ; Query P0 value
-1 ; Turbo PMAC responds
See Also:
On-line commands DEFINE BLCOMP, DEFINE COMP, DEFINE TCOMP,
P{constant}={expression}
CPU
Function: Report the Turbo PMAC CPU type.
Scope: Global
Syntax: CPU
This command causes Turbo PMAC to report the part number of the CPU used on the board. It is mainly
used for troubleshooting purposes.
Example:
CPU ; Request the CPU part number
56303 ; Turbo PMAC responds
See Also:
On-line commands TODAY, VERSION, TYPE
DATE
Function: Report the firmware release date.
Scope: Global
Syntax: DATE
DAT
This command causes Turbo PMAC to report the release date of the firmware revision that it is using.
The date is reported in the North American format:
{mm}/{dd}/{yyyy}
where:
{mm} is the 2-digit representation of the month
{dd} is the 2-digit representation of the day of the month
{yyyy} is the 4-digit representation of the year
The 4-digit representation of the year eliminates possible Year 2000 problems in user code processing the
date information.
The DATE command is not to be confused with the TODAY command, which causes Turbo PMAC to
report the current date.
Example:
DATE ; Request the firmware release date
07/17/1998 ; Turbo PMAC reports the firmware release date
See Also:
On-line commands CPU, TODAY, VERSION, TYPE
DEFINE BLCOMP
Function: Define backlash compensation table
Scope: Motor specific
Syntax: DEFINE BLCOMP {entries},{count length}
DEF BLCOMP {entries},{count length}
where:
{entries} is a positive integer constant representing the number of values in the table;
{count length} is a positive integer representing the span of the table in encoder counts of the
motor.
This command establishes a backlash compensation table for the addressed motor. The next
{entries} constants sent to Turbo PMAC will be placed into this table. The last item on the command
line {count length}, specifies the span of the backlash table in encoder counts of the motor. In use,
if the motor position goes outside of the range 0 to count-length, the position is rolled over to within this
range before the compensation is computed. The spacing between entries in the table is {count
length} divided by {entries}.
On succeeding lines will be given the actual entries of the table as constants separated by spaces and or
carriage return characters. The units of these entries are 1/16 count, and the entries must be integer
values. The first entry is the correction at one spacing from the motor zero position (as determined by the
most recent home search move or power-up/reset), the second entry is the correction two spacings away,
and so on. The correction from the table at motor zero position is zero by definition.
The correction is the amount subtracted (added in the negative direction) from the nominal commanded
position when the motor is moving in the negative direction to get the corrected position. The correction
from the backlash table is added to the Ixx86 constant backlash parameter before adjusting the motor
position. Corrections from any leadscrew compensation tables that have this motor as the target motor
are always active in both directions.
The last entry in the table represents the correction at {count length} distance from the motor’s zero
position. Since the table has the capability to roll over, this entry also represents the correction at the
motor’s zero position. If it is set to a non-zero value, the correction at zero will also be zero.
Note:
Turbo PMAC will reject this command, reporting an ERR003 if I6=1 or 3, if any
BLCOMP buffer exists for a lower numbered motor, or if any TBUF, ROTARY,
LOOKAHEAD or GATHER buffer exists. Any of these buffers must be deleted
first. BLCOMP buffers must be defined from high-numbered motor to low-
numbered motor, and deleted from low-numbered motor to high-numbered motor.
I51 must be set to 1 to enable the table.
Example:
#32 DEFINE BLCOMP 100, 100000
See Also:
Backlash Compensation (Setting Up a Motor)
Leadscrew Compensation (Setting Up a Motor)
I-variables Ixx85, Ixx86, Ixx87
On-line commands DEFINE COMP, DELETE BLCOMP
DEFINE CCBUF
Function: Define extended cutter-compensation buffer
Scope: Coordinate-system specific
Syntax: DEFINE CCBUF {constant}
DEF CCBUF {constant}
where:
{constant} is a positive integer constant representing the size of the buffer in programmed moves
This command establishes an extended cutter-radius compensation move buffer for the addressed
coordinate system. This buffer is required only if it is desired to maintain the compensation through one
or more moves perpendicular to the plane of compensation (e.g. Z-axis moves during XY-plane
compensation). The {constant} value in the command specifies the number of moves that can be
stored in this extended buffer. This number must be at least as large as the number of consecutive
perpendicular moves that may be executed between two moves with a component in the plane of
compensation.
Once this buffer is defined, its use is automatic and invisible to the user. If the number of consecutive
moves perpendicular to the plane of compensation exceeds this buffer size, Turbo PMAC will assume that
the incoming and outgoing moves to this point in the plane of compensation form an outside corner. If it
turns out that they form an inside corner, there will be an overcut, or gouge.
The CCBUF is a temporary buffer. Its contents are never held through a board reset or power cycling. Its
structure is only retained through a board reset or power cycling if the latest SAVE command was issued
with the buffer defined and with I14 = 1.
Turbo PMAC will reject this command, reporting an ERR003 if I6 = 1 or 3, if any CCBUFFER exists for
a lower-numbered coordinate system, or if any LOOKAHEAD or GATHER buffer exists on the board.
Any of these buffers must be deleted first. CCBUFFERs must be defined from high-numbered coordinate
system to low-numbered coordinate system.
Example:
DEFINE CCBUF 5
See Also:
Cutter Radius Compensation
On-line command DELETE CCBUF
Program commands CC0, CC1, CC2, CCR
DEFINE COMP (one-dimensional)
Function: Define Leadscrew Compensation Table
Scope: Motor specific
Syntax: DEFINE COMP {entries}, [#{source}[D],[#{target},]] {count
length}
where:
{entries} is a positive integer constant representing the number of numbers in the table;
{source} (optional) is a constant from 1 to 32 representing the motor whose position controls
which entries in the table are used for the active correction; if none is specified, Turbo PMAC
assumes the source is the addressed motor; if a D is specified after the source motor number, the
desired position of the motor is used to calculate the correction; otherwise the actual position is used;
{target} (optional) is a constant from 1 to 32 representing the motor that receives the correction; if
none is specified, Turbo PMAC assumes the target is the addressed motor;
{count length} is a positive integer representing the span of the table in encoder counts of the
source motor
This command establishes a leadscrew compensation table assigned to the addressed motor. The next
{entries} constants sent to Turbo PMAC will be placed into this table. Once defined the tables are
enabled and disabled with the variable I51.
The table belongs to the currently addressed motor, and unless otherwise specified in the command line, it
will use the addressed motor both for source position data and as the target for its corrections. Each
motor can only have one table that "belongs" to it (for a total of 32 tables in one Turbo PMAC), but it can
act as a source or a target for multiple motors.
Note:
Turbo PMAC will reject this command, reporting an ERR003 if I6=1 or 3, if any
COMP buffer exists for a lower numbered motor, or if any TCOMP, BLCOMP,
TBUF, ROTARY, LOOKAHEAD, or GATHER buffer exists. Any of these
buffers must be deleted first. COMP buffers must be defined from high-numbered
motor to low-numbered motor, and deleted from low-numbered motor to high-
numbered motor.
It is possible to directly specify a source motor (with #{source}), or source and target motors (with
#{source},#{target}), in this command. Either or both of them may be different from the motor
to which the table "belongs". (In other words, just because a table belongs to a motor does not necessarily
mean that it affects or is affected by that motor’s position.)
The table can operate as a function of either the desired (commanded) or actual position of the source
motor. If a D is entered immediately after the source motor number (which must be explicitly declared
here), the table operates as a function of the desired position of the source motor; if no D is entered, the
table operates as a function of the actual position of the source motor.
The last item on the command line, {count length}, specifies the span of the compensation table in
encoder counts of the source motor. In use, if the source motor position goes outside of the range 0 to
count-length, the source position is rolled over to within this range before the correction is computed.
The spacing between entries in the table is {count length} divided by {entries}.
On succeeding lines will be given the actual entries of the table. The units of these entries are 1/16 count,
and the entries must be integer values. The first entry is the correction at one spacing from the motor zero
position (as determined by the most recent home search move or power-up/reset), the second entry is the
correction two spacings away, and so on. The correction is the amount added to the nominal position to
get the corrected position. The correction at the zero position is zero by definition.
The last entry in the table represents the correction at {count length} distance from the motor’s zero
position. Since the table has the capability to roll over, this entry also represents the correction at the
motor’s zero position. If it is set to a non-zero value, the correction at zero will also be non-zero.
Example:
#1 DEFINE COMP 4,2000 ; Create table for motor 1
ERR003 ; Turbo PMAC rejects this command
DELETE GATHER ; Clear other buffers to allow loading
DELETE ROTARY
#8DEFINE COMP 500,20000 ; Uses motor 8 as source and target, 500 entries,
; spacing of 40 counts
#7DEFINE COMP 256,#3D,32768 ; Belongs to motor 7, uses #3 desired position as
; source, #7 as target, 256 entries, spacing of 128 counts
#6 DEFINE COMP 400,#5,#4,40000 ; Belongs to motor 6, uses #5 as source, #4 as target,
; 400 entries, spacing of 100 counts
#5 DEFINE COMP 200,#1D,#1,30000 ; Belongs to motor 5, uses #1 desired position as
; source and target, 200 entries, spacing of 150 count
I51=1 ; Enable compensation tables
See Also:
Leadscrew compensation (Setting Up a Motor)
I-variable I51
On-line commands {constant}, LIST COMP, LIST COMP DEF, DELETE COMP, DELETE
GATHER, DELETE ROTARY, SIZE
DEFINE COMP (two-dimensional)
Function: Define two-dimensional position compensation table
Scope: Motor-specific
Syntax: DEFINE COMP {Rows}.{Columns}, #{RowMotor}[D],
[#{ColumnMotor}[D], [#{TargetMotor}]],
{RowSpan},{ColumnSpan}
DEF COMP...
where:
{Rows} is a positive integer constant representing the number of rows in the table, where each row
represents a fixed location of the second (column) source motor;
{Columns} is a positive integer constant representing the number of columns in the table, where
each column represents a fixed location of the first (row) source motor;
{RowMotor} is an integer constant from 1 to 32 representing the number of the first source motor;
defaults to addressed motor; if a D is specified after the source motor number, the desired position of
the motor is used to calculate the correction; otherwise the actual position is used;
{ColumnMotor} is an integer constant from 1 to 32 representing the number of the second source
motor; if a D is specified after the source motor number, the desired position of the motor is used to
calculate the correction; otherwise the actual position is used;
{TargetMotor} is an integer constant from 1 to 32 representing the number of the target motor;
defaults to addressed motor;
{RowSpan} is the span of the table, in counts, along the first (row) source motor’s travel;
{ColumnSpan} is the span of the table, in counts, along the second (column) source motor’s travel.
This command establishes a two-dimensional position compensation table assigned to the addressed
motor. The next (Rows+1)*(Columns+1)-1 constants sent to Turbo PMAC will be placed into this table.
This type of table is usually used to correct a motor position (X, Y, or Z-axis) as a function of the planar
position of two motors (e.g. X and Y axes). Once defined, the tables are enabled and disabled with the
variable I51.
The table belongs to the currently addressed motor, and unless otherwise specified in the command line, it
will use the addressed motor both as the first-motor source position data and as the target for its
corrections. Each motor can only have one table that belongs to it (for a total of 32 tables in one PMAC),
but it can act as a source and/or a target for multiple tables.
Note:
PMAC will reject this command, reporting an ERR003 if I6=1 or 3, if any COMP
buffer exists for a lower numbered motor, or if any TCOMP, BLCOMP, TBUF,
ROTARY, or GATHER buffer exists. Any of these buffers must be deleted first.
COMP buffers must be defined from high-numbered motor to low-numbered
motor, and deleted from low-numbered motor to high-numbered motor.
The first source motor must be specified in the command line with #{RowMotor}. The second source
motor may be specified in the command line with #{ColumnMotor}; if it is not specified, Turbo
PMAC assumes that the second source motor is the currently addressed motor. The target motor may be
specified with #{TargetMotor}; if it is not specified, Turbo PMAC assumes that the target motor is
the currently addressed motor.
In other words, if only one motor is specified in the command line, it is the first (row) source motor, and
the second (column) source and target motors default to the addressed motor. If two motors are specified
in the command line, the first one specified is the first (row) source motor, the second is the second
(column) source motor, and the target motor defaults to the addressed motor. If three motors are
specified, the first is the first (row) source motor, the second is the second (column) source motor, and the
third is the target motor. None of these motors is required to be the addressed motor.
It is strongly recommended that both source motors and the target motor is specified in this command to
prevent possible confusion.
The table can operate as a function of either the desired (commanded) or actual position of the source
motors. If a D is entered immediately after the source motor number (which must be explicitly declared
here), the table operates as a function of the desired position of the source motor; if no D is entered, the
table operates as a function of the actual position of the source motor. If the target motor is also one of
the source motors, it is recommended that desired position be used, especially in high-gain systems, to
prevent interaction with the servo dynamics.
The last two items on the command line, {RowSpan} and {ColumnSpan}, specify the span of the
compensation table for the two source motors, row and column respectively, expressed in encoder counts
of those motors. In use, if the source motor position goes outside of the range 0 to {Span}, the source
position is rolled over to within this range along this axis before the correction is computed.
The count spacing between columns in the table is {RowSpan} divided by {Columns}. The count
spacing between rows in the table is {ColumnSpan} divided by {Rows}. Note carefully the
interaction between the row parameters and the column parameters.
On succeeding command lines will be given the actual correction entries of the table, given as integer
numerical constants in text form. The units of these entries are 1/16 count, and the entries must be integer
values. The first entry is the correction at one column spacing from the zero position of the RowMotor,
and the zero position of the ColumnMotor. The second entry is the correction at two column spacings
from the zero position of the RowMotor, and the zero position of the ColumnMotor, and so on. Entry
number Columns is the correction at RowSpan counts of the RowMotor, and at the zero position of the
ColumnMotor (this entry should be zero to use the table along the edge, to match the implied zero
correction at the origin). These entries should be considered as constituting Row 0 of the table.
The next entry (entry Columns+1, the first entry of Row 1) is the correction at the zero position of the
RowMotor, and one row spacing of the ColumnMotor. The following entry is the correction at one
column spacing of the RowMotor and one row spacing of the ColumnMotor. The entry after this is
the correction at two column spacing of the RowMotor and one row spacings of the ColumnMotor.,
and so on. The last entry of Row 1 (entry 2*Columns+1) is the correction at one row spacing of the
RowMotor, and RowSpan counts of the ColumnMotor.
Subsequent rows are added in this fashion, with the corrections of the entries for Row n being at n row
spacings from the zero position of the ColumnMotor. The last row (row Rows) contains corrections at
ColumnSpan counts of the ColumnMotor.
The size of the table is limited only by available data buffer space in Turbo PMAC’s memory.
The following chart shows the order of entries into a 2D table with r rows and c columns, covering a span
along the row motor of RowSpan, and along the column motor of ColSpan:
Column Motor
Position v Col 0 Col 1 Col 2 (Col j) Col c
Row Motor 0 RowSpan/c 2*RowSpan/c RowSpan
Position >
Row 0 0 [0] E1 E2 … Ec
Row 1 ColSpan/r Ec+1 Ec+2 Ec+3 … E2c+1
Row 2 2*ColSpan/r E2c+2 E2c+3 E2c+4 … E3c+2
(Row i) … … … (Eic+I+j) …
Row r ColSpan Erc+r Erc+r+1 Erc+r+2 Erc+r+c
There are several important details to note in the entry of a 2D table:
The number of rows and number of columns is separated by a period, not a comma.
The correction to the target motor at the zero position of both source motors is zero by definition.
This is an implied entry at the beginning of the table (shown by [0] in the above chart); it should not
be explicitly entered.
Consecutive entries in the table are in the same row (except at row’s end) separated by one column
spacing of the position of the first source (row) motor.
Both Row 0 and Row r must be entered into the table, so effectively (r+1) rows are being entered. If
there is any possibility that it may go beyond an edge of the table, matching entries of Row 0 and
Row r should have the same value to prevent a discontinuity in the correction. Row r in the table
may simply be an added row beyond the real range of concern used just to prevent possible
discontinuities at the edges of he real range of concern.
Both Column 0 and Column c must be entered into the table, so effectively (c+1) columns are being
entered. If there is any possibility that it may go beyond an edge of the table, matching entries of
Column 0 and Column c should have the same value to prevent a discontinuity in the correction.
Column c in the table may simply be an added column beyond the real range of concern used just to
prevent possible discontinuities at the edges of the real range of concern.
Because the outside rows and outside columns must match each other to prevent edge discontinuities,
the three explicitly entered corner corrections must be zero to match the implicit zero correction at the
first corner of the table.
Examples:
#1 DEFINE COMP 40.30,#1,#2,#3,300000,400000
; Create table belonging to Motor 1
ERR007 ; Turbo PMAC rejects this command
DELETE GATHER ; Clear other buffers to allow loading
&1 DELETE ROTARY
&2 DELETE ROTARY
#2 DELETE COMP
#3 DELETE COMP
#4 DEFINE COMP 30.40,#1,#2,#3,400000,300000
; Create same table, now belonging to Motor 4; #1 & #2 are sources, #3
; is target; 30 rows x 40 columns, spacing of 10,000 counts
(1270 entries) ; (30+1)*(40+1)-1 entries of constants
#3 DEFINE COMP 25.20,#2,#3,#1,200000,250000
; Create table belonging to Motor 3; #2 and #3 are sources, #1 is target;
; 25 rows x 20 columns, spacing of 10,000 counts
(545 entries) ;(25+1)*(20+1)-1 entries of constants
#2 DEFINE COMP 10.10,#1,#4,10000,20000
; Create table belonging to Motor 2; #1 and #4 are sources, #2 (default)
; is target; 10 rows x10 columns, spacing of 1000 cts between columns;
; spacing of 2000 cts between rows;
(120 entries) ; (10+1)*(10+1)-1 entries of constants
#1 DEFINE COMP 12.10,#4,1280,1200
; Create table belonging to Motor 1; #4 and #1 (default) are sources, #1
; (default) is target;12 rows x 10 columns; spacing of 128 cts between;
; columns spacing of 100 cts between rows
(142 entries) ; (12+1)*(10+1)-1 entries of constants
I51=1 ; Enable compensation tables
DEFINE GATHER
Function: Create a data gathering buffer.
Scope: Global
Syntax: DEFINE GATHER [{constant}]
DEF GAT [{constant}]
where:
{constant} is a positive integer representing the number of words of memory to be reserved for
the buffer
This command reserves space in Turbo PMAC’s memory or in DPRAM depending upon the setting of
I5000 for the data gathering buffer and prepares it for collecting data at the beginning of the buffer. If a
data gathering buffer already exists, its contents are not erased but the Data Gather Buffer Storage address
(Y:$003120) is reinitialized to the Data Gather Buffer Start address (X:$003120) and the LIST
GATHER command will no longer function. Data collection will again start at the beginning of the buffer
when the command GATHER is issued.
If Data Gathering is in progress (an ENDGATHER command has not been issued and the gather buffer has
not been filled up) Turbo PMAC will report an error on receipt of this command.
The optional {constant} specifies the number of long words to be reserved for the data gathering
buffer, leaving the remainder of Turbo PMAC's memory available for other buffers such as motion and
PLC programs. If {constant} is not specified, all of Turbo PMAC's unused buffer memory is
reserved for data gathering. Until this buffer is deleted (with the DELETE GATHER command), no new
motion or PLC programs may be entered into Turbo PMAC.
Note:
If I5000 = 2 or 3 the {size} requested in the DEFINE GATHER {size}
command refers to a DPRAM long word (32-bits). If the {size} is smaller than
required to hold an even multiple of the requested data, the actual data storage will
go beyond the requested {size} to the next higher multiple of memory words
required to hold the data. For example, if gathering one 24-bit value and one 48-
bit value, 3 DPRAM long words of memory is needed. If the {size} specified is
4000 words (not a multiple of 3), the actual storage size will be 4002 words (the
next higher multiple of 3).
The number of long words of unused buffer memory can be found by issuing the SIZE command.
Example:
DEFINE GATHER
DEFINE GATHER 1000
See Also:
I-variables I5000 – I5051
On-line commands GATHER, DELETE GATHER, <CTRL-G>, SIZE
DEFINE LOOKAHEAD
Function: Create a lookahead buffer
Scope: Coordinate-system specific
Syntax: DEFINE LOOKAHEAD {constant},{constant}
DEF LOOK {constant},{constant}
where:
the first {constant} is a positive integer representing the number of move segments that can be
stored in the buffer;
the second {constant} is a positive integer representing the number of synchronous M-variable
assignments that can be stored in the buffer
This command establishes a lookahead buffer for the addressed coordinate system. It reserves memory to
buffer both motion equations and synchronous M-variable output commands for the lookahead function.
Segment Buffer Size: The first constant value in the command determines the number of motion
segments that can be stored in the lookahead buffer. Each motion segment takes Isx13 milliseconds at the
motion program speeds and acceleration times (the velocity and acceleration limits may extend these
times). However, it is variable Isx20 for the coordinate system that determines how many motion
segments the coordinate system will actually look ahead in operation.
The lookahead buffer should be sized large enough to store all of the lookahead segments calculated,
which means that this constant value must be greater than or equal to Isx20. If backup capability is
desired, the buffer must be sized to be large enough to contain the desired lookahead distance plus the
desired backup distance.
The method for calculating the number of segments that must be stored ahead is explained in the Isx20
specification and in the Turbo PMAC User manual section on Lookahead. The fundamental equation is:
4 Ixx16 1
Isx20 * max * 2 * Isx13
3 Ixx 17 xx
If backup capability is desired, the buffer must be able to store an additional number of segments for the
entire distance to be covered in reversal. This number of segments can be calculated as:
BackupDist units * 1000( m sec/ sec)
BackSegments
Vmax units / sec * SegTime( m sec/ seg )
The total number of segments to reserve for the buffer is simply the sum of the forward and back
segments wishing to be able to hold:
TotalSegments Isx20 BackSegments
Memory Requirements: For each segment Turbo PMAC is told to reserve space for in the lookahead
buffer, Turbo PMAC will reserve (2x+4) 48-bit words of memory from the main buffer memory space,
where x is the number of motors in the coordinate system at the time that the buffer is defined. For
example, if there are 5 motors in the coordinate system, a command to reserve space for 50 segments will
reserve 50*(2*5 + 4) = 700 words of memory. If a motor is added to the coordinate system, or removed
from it, after the lookahead buffer has been defined, the lookahead buffer should be re-defined.
Output Buffer Size: The second constant value in the command determines the number of synchronous
M-variable assignments that can be stored in the lookahead buffer. Because these are evaluated at
lookahead time, but not actually implemented until move execution time, they must be buffered. This
section of the buffer must be large enough to store all of the assignments that could be made in the
lookahead distance. Synchronous M-variable assignments are not made during backup, so there is no
need to reserve memory to store assignments for the backup distance as well as the lookahead distance.
Memory Requirements: For each synchronous M-variable assignment Turbo PMAC is told to reserve
space for in the lookahead buffer, Turbo PMAC will reserve two 48-bit words of memory.
There are no performance penalties for making the lookahead buffer larger than required, but this does
limit the amount of Turbo PMAC memory free for other features.
A lookahead buffer is never retained through a power-down or board reset, so this command must be
issued after every power-up/reset if the lookahead function is to be used.
Note:
Turbo PMAC will reject the DEFINE LOOKAHEAD command, reporting an
ERR003 if I6=1 or 3, if any LOOKAHEAD buffer exists for a lower-numbered
coordinate system, or if a GATHER buffer exists. LOOKAHEAD buffers must be
defined from high-numbered coordinate system to low-numbered coordinate
system, and deleted from low-numbered coordinate system to high-numbered
coordinate system.
Example:
DELETE GATHER ; Ensure open memory
&2DEFINE LOOKAHEAD 1000,200 ; Create buffer for C.S. 2
&1DEFINE LOOKAHEAD 1500,20 ; Create buffer for C.S. 1
DEFINE ROTARY
Function: Define a rotary motion program buffer
Scope: Coordinate-system specific
Syntax: DEFINE ROTARY{constant}
DEF ROT{constant}
where:
{constant} is a positive integer representing the number of long words of memory to be reserved
for the buffer
This command causes Turbo PMAC to create a rotary motion program buffer for the addressed
coordinate system, allocating the specified number of long words of memory. Rotary buffers permit the
downloading of program lines during the execution of the program.
The buffer should be large enough to allow it to hold safely the number of lines anticipated to be
downloaded to Turbo PMAC ahead of the executing point. Each long word of memory can hold one sub-
block of a motion program (i.e. X1000 Y1000 is considered as two sub-blocks). The allocated memory
for this coordinate system’s rotary buffer remains resident until the buffer is deleted with DELETE ROT.
Note:
Turbo PMAC will reject this command, reporting an ERR003 if I6=1 or 3, if any
ROTARY buffer exists for a lower numbered coordinate system, or if a
LOOKAHEAD or GATHER buffer exists. Any of these buffers must be deleted
first. ROTARY buffers must be defined from high-numbered coordinate system to
low-numbered coordinate system, and deleted from low-numbered coordinate
system to high-numbered coordinate system.
Example:
DELETE GATHER ; Ensure open memory
&2DEFINE ROT 100 ; Create buffer for C.S. 2
&1DEFINE ROT 100 ; Create buffer for C.S. 1
&1B0 &2B0 ; Point to these buffers
OPEN ROT ; Open these buffers for entry
... ; enter program lines here
See Also:
Rotary Program Buffers (Writing and Executing Motion Programs)
On-line commands OPEN ROTARY, DELETE ROTARY, DELETE GATHER
DEFINE TBUF
Function: Create a buffer for axis transformation matrices.
Scope: Global
Syntax: DEFINE TBUF {constant}
DEF TBUF {constant}
where:
{constant} is a positive integer representing the number of transformation matrices to create
This command reserves space in Turbo PMAC’s memory for one or more axis transformation matrices.
These matrices can be used for real-time translation, rotation, scaling, and mirroring of the X, Y, and Z
axes of any coordinate system. A coordinate system selects which matrix to use with the TSELn
command, where n is an integer from 1 to the number of matrices created here.
Note:
Turbo PMAC will reject this command, reporting an ERR003 if I6=1 or 3, if any
LOOKAHEAD, ROTARY,or GATHER buffer exists. Any of these buffers must
be deleted first.
The number of long words of unused buffer memory can be found by issuing the SIZE command. Each
defined matrix takes 21 words of memory.
Example:
DELETE GATHER
DEF TBUF 1
DEFINE TBUF 8
See Also:
Axis Transformation Matrices (Writing and Executing Motion Programs)
On-line commands DELETE TBUF, DELETE GATHER, SIZE.
Program commands TSEL, ADIS, AROT, IDIS, IROT, TINIT
DEFINE TCOMP
Function: Define torque compensation table
Scope: Motor specific
Syntax: DEFINE TCOMP {entries},{count length}
DEF TCOMP {entries},{count length}
where:
{entries} is a positive integer constant representing the number of values in the table;
{count length} is a positive integer representing the span of the table in encoder counts of the
motor.
This command establishes a torque compensation table for the addressed motor. The next {entries}
constants sent to Turbo PMAC will be placed into this table. The last item on the command line {count
length}, specifies the span of the torque compensation table in encoder counts of the motor. In use, if
the motor position goes outside of the range 0 to count-length, the position is rolled over to within this
range before the compensation is computed. The spacing between entries in the table is {count
length} divided by {entries}.
On succeeding lines will be given the actual entries of the table as constants separated by spaces and or
carriage return characters. The units of these entries are bits of a 24-bit output (regardless of the actual
output device resolution), and the entries must be integer values. The first entry is the correction at one
spacing from the motor zero position (as determined by the most recent home search move or power-
up/reset), the second entry is the correction two spacings away, and so on. Turbo PMAC computes
corrections for positions between the table entries by a first-order interpolation between adjacent entries.
The correction from the table at motor zero position is zero by definition.
The correction is the magnitude added to Turbo PMAC’s servo loop output at that position. If Turbo
PMAC’s command is positive, a positive value from the table will increase the magnitude of the output; a
negative value will decrease the magnitude of the output. If Turbo PMAC’s command is negative, a
positive value from the table will increase the magnitude of the output in the negative direction; a
negative value will decrease the magnitude of the output.
The last entry in the table represents the correction at {count length} distance from the motor’s zero
position. Since the table has the capability to roll over, this entry also represents the correction at the
motor’s zero position. If it is set to a non-zero value, the correction at zero will also be zero.
Note:
Turbo PMAC will reject this command, reporting an ERR003 if I6=1 or 3, if any
TCOMP buffer exists for a lower numbered motor, or if any BLCOMP, TBUF,
LOOKAHEAD, ROTARY, or GATHER buffer exists. Any of these buffers must
be deleted first. TCOMP buffers must be defined from high-numbered motor to
low-numbered motor, and deleted from low-numbered motor to high-numbered
motor.
I51 must be set to 1 to enable the table.
See Also:
Torque Compensation (Setting Up a Motor)
I-variables I51
On-line command DELETE TCOMP
DEFINE UBUFFER [modified description]
Function: Create a buffer for user variable use.
Scope: Global
Syntax: DEFINE UBUFFER {constant}
DEF UBUF {constant}
where:
{constant} is a positive integer representing the number of 48-bit words of Turbo PMAC memory
to reserve for this purpose
This command reserves space in Turbo PMAC’s memory for the user’s discretionary use. This memory
space will be untouched by any Turbo PMAC automatic functions. User access to this buffer is through
M-variables, or possibly through on-line W (write) and R (read) commands.
The buffer starts at Turbo PMAC data memory end address ($0107FF for the standard data memory, and
$03FFFF for the extended data memory) and continues back toward the beginning of memory ($000000)
for the number of long (48-bit) words specified by {constant}. This memory space can be subdivided
any way the user sees fit. These registers are backed up by the flash memory, so the values in the buffer
at the last SAVE command will be copied from the flash memory into the buffer at power-up or reset.
All other buffers except for fixed motion programs (PROG) and PLC programs must be deleted before
Turbo PMAC will accept this command. There can be no rotary motion program, leadscrew
compensation table, transformation matrix, data gathering or lookahead buffers in Turbo PMAC memory
(any buffer created with a DEFINE command) for this command to be accepted. It is usually best to
reinitialize the card with a $$$*** command, or erase all defined buffers with the DELETE ALL
command, before sending the DEFINE UBUFFER command
The address of the end of unreserved memory is held in register X:$0031B2. If no UBUFFER is defined,
this register will hold a value of $010800 for the standard data memory configuration, or $040000 for the
extended data memory configuration. (Starting with V1.937 firmware, a Turbo PMAC with the extended
data memory configuration will at re-initialization have a UBUFFER of 65,536 words defined, causing
this register to hold a value of $030000.) Immediately after the user buffer has successfully been defined,
this register will hold the address of the start of the buffer (the end of the user buffer is always at the end
of data memory).
To free up this memory for other uses, the DEFINE UBUFFER 0 command should be used (there is no
DELETE UBUFFER command). It may be more convenient simply to re-initialize the board with a
$$$*** command.
Example:
RHX:$0031B2 ; Look for end of unreserved memory
00FC99 ; Reply indicates some reserved
$$$*** ; Re-initialize card to clear memory
RHX:$0031B2 ; Check end of unreserved memory
010800 ; Reply indicates none reserved
DEFINE UBUFFER 2048 ; Reserve memory for buffer
RHX:$0031B2 ; Check for beginning of buffer
010000 ; Reply confirms 2048 words reserved
M1000->D:$010000 ; Define M-variable to first word
M1010->Y:$010020,12,1 ; Define M-variable to a middle word
M1023->X:$0107FF,24,S ; Define M-variable to last word
See Also:
User Buffer, M-Variables (Computational Features)
I-variable I4908
On-line commands $$$***, R[H]{address}, W{address}
DELETE ALL
Function: Erase all defined permanent and temporary buffers
Scope: Global
Syntax: DELETE ALL
DEL ALL
This command causes Turbo PMAC to erase all buffers created with a DEFINE command, permanent
(fixed) and temporary, in Turbo PMAC’s memory space. These include:
User buffer (UBUFFER)
Leadscrew compensation tables (COMP)
Torque compensation tables (TCOMP)
Backlash compensation tables (BLCOMP)
Transformation matrix buffers (TBUF)
Rotary motion program buffers (ROTARY)
Segment lookahead buffers (LOOKAHEAD)
Extended cutter-radius compensation buffers (CCBUF)
Data gathering buffer (GATHER)
See Also:
On-line commands CLEAR, CLEAR ALL, CLEAR ALL PLCS, OPEN, DELETE ALL TEMP
DELETE CCUBUF
Function: Erase extended cutter-compensation buffer
Scope: Motor specific
Syntax: DELETE CCBUF
DEL CCBUF
This command causes Turbo PMAC to erase the extended cutter-radius compensation move buffer for the
addressed coordinate system, freeing that memory for other use.
Turbo PMAC will reject this command, reporting an ERR003 if I6 = 1 or 3, if any CCBUF exists for a
lower-numbered coordinate system, or if any LOOKAHEAD or GATHER buffer exists on the board.
Any of these buffers must be deleted first. CCBUFs must be deleted from low-numbered coordinate
system to high-numbered coordinate system.
See Also:
Cutter Radius Compensation
On-line command DEFINE CCBUF
Program commands CC0, CC1, CC2, CCR
DELETE COMP
Function: Erase leadscrew compensation table
Scope: Motor specific
Syntax: DELETE COMP
DEL COMP
This command causes Turbo PMAC to erase the compensation table belonging to the addressed motor,
freeing that memory for other use.
Note:
Turbo PMAC will reject this command, reporting an ERR003 if I6=1 or 3, if any
COMP buffer exists for a lower numbered motor, or if any TCOMP, BLCOMP,
TBUF, ROTARY, or GATHER buffer exists. Any of these buffers must be
deleted first. COMP buffers must be defined from high-numbered motor to low-
numbered motor, and deleted from low-numbered motor to high-numbered motor.
Remember that a compensation table belonging to a motor does not necessarily affect that motor or is not
necessarily affected by that motor. The command LIST COMP DEF will tell which motors it affects
and is affected by.
Example:
#2DEL COMP.... ; Erase table belonging to Motor 2
ERR003............. ; Turbo PMAC rejects this command
#1 DELETE COMP ; Erase table belonging to Motor 1
#2 DELETE COMP ; Erase table belonging to Motor 2
See Also:
Leadscrew compensation (Setting Up a Motor)
I-variable I51
On-line commands {constant}, LIST COMP, LIST COMP DEF, DEFINE COMP
DELETE LOOKAHEAD
Function: Erase the lookahead buffer.
Scope: Coordinate-system specific
Syntax: DELETE LOOKAHEAD
DEL LOOK
This command causes Turbo PMAC to erase the lookahead buffer for the addressed coordinate system,
freeing that memory for other use.
Note:
Turbo PMAC will reject this command, reporting an ERR003 if I6=1 or 3, if any
LOOKAHEAD buffer exists for a lower numbered coordinate system, or if any
ROTARY or GATHER buffer exists. Any of these buffers must be deleted first.
LOOKAHEAD buffers must be defined from high-numbered coordinate system to
low-numbered coordinate system, and deleted from low-numbered coordinate
system to high-numbered coordinate system.
Lookahead buffers are not maintained through a power-down or board reset, even if a SAVE command
has been done while the buffers exist. Therefore a board reset will automatically delete all lookahead
buffers.
DELETE GATHER
Function: Erase the data gather buffer.
Scope: Global
Syntax: DELETE GATHER
DEL GAT
This command causes the data gathering buffer to be erased. The memory that was reserved is now de-
allocated and is available for other buffers (motion programs, PLC programs, compensation tables, etc.).
If Data Gathering is in progress (an ENDGATHER command has not been issued and the gather buffer has
not been filled up) Turbo PMAC will report an error on receipt of this command.
Turbo PMAC's Executive Program automatically inserts this command at the top of a file when it uploads
a buffer from Turbo PMAC into its editor, so the next download will not be hampered by an existing
gather buffer. It is strongly recommended that this command be used as well when a program file is
created in the editor (see Examples below).
Note:
When the executive program's data gathering function operates, it automatically
reserves the entire open buffer space for gathered data. When this has happened,
no additional programs or program lines may be entered into Turbo PMAC's buffer
space until the DELETE GATHER command has freed this memory.
Example:
CLOSE ; Make sure no buffers are open
DELETE GATHER ; Free memory
OPEN PROG 50 ; Open new buffer for entry
CLEAR ; Erase contents of buffer
... ; Enter new contents here
See Also:
Buffered Commands (Talking to Turbo PMAC)
On-line commands GATHER, DEFINE GATHER, SIZE
DELETE PLCC
Function: Erase specified compiled PLC program
Scope: Global
Syntax: DELETE PLCC {constant}
DEL PLCC {constant}
where:
{constant} is an integer from 0 to 31, representing the program number
This command causes Turbo PMAC to erase the specified compiled PLC program. Remember that
because all of the compiled PLC programs must be downloaded to Turbo PMAC together, the only way
to restore this PLC is to download the entire set of compiled PLCs.
Only one PLCC program can be deleted in one command. Ranges and lists of PLCC program numbers
are not permitted in this command.
To perform the same function for an uncompiled PLC program, the command sequence would be OPEN
PLC n CLEAR CLOSE.
Example:
DELETE PLCC 5 ; Erase compiled PLC program 5
DEL PLCC 0.... ; Erase compiled PLC program 0
See Also:
Compiled PLCs (Writing a PLC Program)
I-variable I5
On-line commands DISABLE PLCC, ENABLE PLCC, CLEAR
DELETE ROTARY
Function: Delete rotary motion program buffer of addressed coordinate system
Scope: Coordinate-system specific
Syntax: DELETE ROTARY
DEL ROT
This command causes Turbo PMAC to erase the rotary buffer for the currently addressed coordinate
system and frees the memory that had been allocated for it.
Note:
Turbo PMAC will reject this command, reporting an ERR003 if I6=1 or 3, if the
ROTARY buffer for this coordinate system is open or executing, or if any
ROTARY buffer exists for a lower numbered coordinate system, or if a GATHER
buffer exists. Any of these buffers must be deleted first. ROTARY buffers must
be defined from high-numbered coordinate system to low-numbered coordinate
system, and deleted from low-numbered motor to high-numbered motor.
Example:
&2 DELETE ROTARY ; Try to erase C.S. 2’s rotary buffer
ERR003............. ; Turbo PMAC rejects this; C.S. 1 still has
............ ; a rotary buffer
&1 DELETE ROTARY ; Erase C.S. 1's rotary buffer
&2 DELETE ROTARY ; Erase C.S. 2's rotary buffer; OK now
See Also:
Rotary Program Buffers (Writing and Executing Motion Programs)
On-line commands DEFINE ROTARY, OPEN ROTARY.
DELETE TBUF
Function: Delete buffer for axis transformation matrices.
Scope: Global
Syntax: DELETE TBUF
DEL TBUF
This command frees up the space in Turbo PMAC's memory that was used for axis transformation
matrices. These matrices can be used for real-time translation, rotation, scaling, and mirroring of the X,
Y, and Z axes of any coordinate system.
Note:
Turbo PMAC will reject this command, reporting an ERR007 if I6=1 or 3, if any
ROTARYor GATHER buffer exists. Any of these buffers must be deleted first.
Example:
DEL TBUF
DELETE TBUF
See Also:
Axis Transformation Matrices (Writing and Executing Motion Programs)
On-line commands DEFINE TBUF
Program commands TSEL, ADIS, AROT, IDIS, IROT, TINIT
DELETE TCOMP
Function: Erase torque compensation table
Scope: Motor specific
Syntax: DELETE TCOMP
DEL TCOMP
This command causes Turbo PMAC to erase the torque compensation table for the addressed motor,
freeing that memory for other use.
Note:
Turbo PMAC will reject this command, reporting an ERR003 if I6=1 or 3, if any
TCOMP buffer exists for a lower numbered motor, or if any BLCOMP, TBUF,
ROTARY, or GATHER buffer exists. Any of these buffers must be deleted first.
TCOMP buffers must be defined from high-numbered motor to low-numbered
motor, and deleted from low-numbered motor to high-numbered motor.
Example:
#2 DEL TCOMP ; Erase table belonging to Motor 2
ERR003 ; Turbo PMAC rejects this command
#1 DEL TCOMP ; Erase table belonging to Motor 1
#2 DEL TCOMP ; Erase table belonging to Motor 2
See Also:
Torque Compensation (Setting Up a Motor)
I-variables I51
On-line command DEFINE TCOMP
DISABLE PLC
Function: Disable specified PLC programs.
Scope: Global
Syntax: DISABLE PLC {constant}[,{constant}]
DIS PLC {constant}[,{constant}]
DISABLE PLC {constant}..{constant}
DIS PLC {constant}..{constant}
where
{constant} is an integer from 0 to 31, representing the program number
This command causes Turbo PMAC to disable (stop executing) the specified uncompiled PLC program
or programs. Execution can subsequently be resumed at the top of the program with the ENABLE PLC
command. If it is desired to restart execution at the stopped point, execution should be stopped with the
PAUSE PLC command, and restarted with the RESUME PLC command
The on-line DISABLE PLC command can only suspend execution of a PLC program at the end of a
scan, which is either the end of the program, or after an ENDWHILE statement in the program. PLC
programs are specified by number, and may be specified in a command singularly, in a list (separated by
commas), or in a range of consecutively numbered programs. PLC programs can be re-enabled by using
the ENABLE PLC command. If a motion or PLC program buffer is open when this command is sent to
Turbo PMAC, the command will be entered into that buffer for later execution.
Example:
DISABLE PLC 1
DIS PLC 5
DIS PLC 3,4,7
DISABLE PLC 0..31
See Also:
I-variable I5
On-line commands ENABLE PLC, OPEN PLC, DISABLE PLCC, ENABLE PLCC, <CONTROL-D>.
Program commands DISABLE PLC, ENABLE PLC, DISABLE PLCC, ENABLE PLCC
DISABLE PLCC
Function: Disable compiled PLC programs.
Scope: Global
Syntax: DISABLE PLCC {constant}[,{constant}]
DIS PLCC {constant}[,{constant}]
PLCC {constant}..{constant}
DIS PLCC {constant}..{constant}
where:
{constant} is an integer from 0 to 31, representing the compiled PLC program number
This command causes Turbo PMAC to disable (stop executing) the specified compiled PLC program or
programs. Compiled PLC programs are specified by number, and may be specified in a command
singularly, in a list (separated by commas), or in a range of consecutively numbered programs. PLC
programs can be re-enabled by using the ENABLE PLCC command.
If a motion or PLC program buffer is open when this command is sent to Turbo PMAC, the command
will be entered into that buffer for later execution.
Example:
DISABLE PLCC 1
DIS PLCC 5
DIS PLCC 3,4,7
DISABLE PLCC 0..31
See Also:
I-variable I5
On-line commands DISABLE PLC, ENABLE PLC, ENABLE PLCC, OPEN PLC, <CONTROL-D>.
Program commands DISABLE PLC, DISABLE PLCC, ENABLE PLC, ENABLE PLCC
E
Function: Enable disabled motors
Scope: Coordinate-system specific
Syntax: E
This command enables the disabled motors of the addressed coordinate system, closing the position loop
at the present actual position. If a motor in the coordinate system is open-loop enabled, it closes the
position loop at the present actual position. It has no effect on closed-loop enabled motors.
If I36 is set to 1, the A (abort) command does not enable disabled motors, so the E command is used for
enabling the motors of a coordinate system. If I36 is set to 0, either the A or E command could be used.
Note that if the motor is a synchronous (zero-slip – Ixx78 = 0) motor commutated by Turbo PMAC
(Ixx01 bit 0 = 1), a phase referencing is required after power-up/reset before the motor can be enabled.
This is done automatically on power-up/reset if Ixx80 for the motor is set to 1 or 3, or subsequently with
the motor-specific $ command, or the coordinate-system-specific $$ command. The E command does
not cause a phase referencing to be performed on any motor.
The global <CTRL-E> command performs the comparable action for all of the motors on Turbo PMAC.
See Also
On-line commands A, <CTRL-A> <CTRL-E>, $, $$
I-variables I36, Ixx80.
EAVERSION
Function: Report firmware version information
Scope: Global
Syntax: EAVERSION
EAVER
This command causes Turbo PMAC to report information about the firmware version it is using. Turbo
PMAC responds with seven decimal digits.
The first four digits represent the firmware version number, without the decimal point (e.g. 1934 for
version 1.934).
The fifth digit is 0 for a released firmware version. If it has a value ‘n’ greater than 0, it is reporting the
‘nth’ test (pre-release) revision of this numerical firmware version.
The sixth digit is reserved for future use. It presently always reports a 0.
The seventh digit is a 0 for a Turbo PMAC1; it is a 1 for a Turbo PMAC2.
Example:
EAVERSION ; Ask Turbo PMAC for firmware version
1934201 ; Turbo PMAC responds Version 1.934 2nd test revision
; Turbo PMAC2 firmware
See Also:
Resetting Turbo PMAC (Talking to Turbo PMAC)
On-line command DATE, VERSION, TYPE
ENABLE PLC
Function: Enable specified PLC programs.
Scope: Global
Syntax: ENABLE PLC {constant}[,{constant}]
ENA PLC {constant}[,{constant}]
ENABLE PLC {constant}..{constant}
ENA PLC {constant}..{constant}
where:
{constant} is an integer from 0 to 31, representing the program number
This command causes Turbo PMAC to enable (start executing) the specified uncompiled PLC program or
programs at the top of the program. Execution of the PLC program may have been stopped with the
DISABLE PLC, PAUSE PLC, or OPEN PLC command.
If a motion or PLC program buffer is open when this command is sent to Turbo PMAC, the command
will be entered into that buffer for later execution.
I-variable I5 must be in the proper state to allow the PLC programs specified in this command to execute.
Note:
This command must be used to start operation of a PLC program after it has been
entered or edited, because the OPEN PLC command disables the program
automatically and CLOSE does not re-enable it.
Example:
ENABLE PLC 1
ENA PLC 2,7
ENABLE PLC 3,21
ENABLE PLC 0..31
This example shows the sequence of commands to download a very simple PLC program and have it
enabled on the download automatically:
OPEN PLC 7 CLEAR
P1=P1+1
CLOSE
ENABLE PLC 7
See Also:
I-variable I5
On-line commands ENABLE PLC, OPEN PLC, <CONTROL-D>.
Program commands DISABLE PLC, ENABLE PLC
ENABLE PLCC
Function: Enable specified compiled PLC programs.
Scope: Global
Syntax: ENABLE PLCC {constant}[,{constant}]
ENA PLCC {constant}[,{constant}]
PLCC {constant}..{constant}
ENA PLCC {constant}..{constant}
where:
{constant} is an integer from 0 to 31, representing the program number
This command causes Turbo PMAC to enable (start executing) the specified compiled PLC program or
programs. Compiled PLC programs are specified by number, and may be used singularly in this
command, in a list (separated by commas), or in a range of consecutively numbered programs.
If a motion or PLC program buffer is open when this command is sent to Turbo PMAC, the command
will be entered into that buffer for later execution.
I-variable I5 must be in the proper state to allow the compiled PLC programs specified in this command
to execute.
Example:
ENABLE PLCC 1
ENA PLCC 2,7
ENABLE PLCC 3,21
ENABLE PLCC 0..31
See Also:
I-variable I5
On-line commands DISABLE PLC, DISABLE PLCC, ENABLE PLC, OPEN PLC, <CONTROL-D>.
Program commands DISABLE PLC, DISABLE PLCC, ENABLE PLC, ENABLE PLCC
ENDGATHER
Function: Stop data gathering.
Scope: Global
Syntax: ENDGATHER
ENDG
This command causes data gathering to cease. Data gathering may start up again (without overwriting
old data) with another GATHER command.
Usually, this command is used in conjunction with the data gathering and plotting functions of the Turbo
PMAC Executive Program.
If a motion or PLC program buffer is open when this command is sent to Turbo PMAC, the command
will be entered into that buffer for later execution.
Examples:
GAT B1R ; Start gathering and run program 1
ENDG ; Stop gathering -- give this command when moves of interest are done
OPEN PROG2 CLEAR
X10
DWELL1000
CMD"GATHER" ; Program issues start command here
X20 ; Move of interest
DWELL50
CMD"ENDG" ; Program issues stop command here
CLOSE
See Also:
Data Gathering Function (Analysis Features)
I-variables I5000 – I5051
On-line commands DEFINE GATHER, GATHER, LIST GATHER, DELETE GATHER
Gathering and Plotting (Turbo PMAC Executive Program Manual)
F
Function: Report motor following error
Scope: Motor specific
Syntax: F
This command causes Turbo PMAC to report the present motor following error (in counts, rounded to the
nearest tenth of a count) for the addressed motor to the host. Following error is the difference between
motor desired and measured position at any instant. When the motor is open-loop (killed or enabled),
following error does not exist and Turbo PMAC reports a value of 0.
Example:
F ; Ask for following error of addressed motor
12 ; Turbo PMAC responds
#3F ; Ask for following error of Motor 3
-6.7 ; Turbo PMAC responds
See Also:
Following Error (Servo Features)
I-variables Ixx11, Ixx12, Ixx67
On-line commands <CTRL-F>, P, V
Suggested M-variable definitions Mxx61, Mxx62
Memory map registers D:$0000DB, D:$00015B, etc.
FRAX
Function: Specify the coordinate system's feedrate axes.
Scope: Coordinate-system specific
Syntax: FRAX
FRAX({axis}[,{axis}...])
where:
{axis} (optional) is a character (X, Y, Z, A, B, C, U, V, W) specifying which axis is to be used in
the vector feedrate calculations
No spaces are permitted in this command.
This command specifies which axes are to be involved in the vector-feedrate (velocity) calculations for
upcoming feedrate-specified (F) moves. Turbo PMAC calculates the time for these moves as the vector
distance (square root of the sum of the squares of the axis distances) of all the feedrate axes divided by the
feedrate. Any non-feedrate axes commanded on the same line will complete in the same amount of time,
moving at whatever speed is necessary to cover the distance in that time.
Vector feedrate has obvious geometrical meaning only in a Cartesian system, for which it results in
constant tool speed regardless of direction, but it is possible to specify for non-Cartesian systems, and for
more than three axes.
Note:
If the move time as calculated for the vector-feedrate axes is less than the time
computed as the distance of any non-feedrate axis commanded on the line divided
by the Isx86 alternate feedrate parameter, this longer time will be used for all axes
instead.
If a motion program buffer is open when this command is sent to Turbo PMAC, it will be entered into the
buffer for later execution.
For instance, in a Cartesian XYZ system, if using FRAX(X,Y), all of the feedrate-specified moves will
be at the specified vector feedrate in the XY-plane, but not necessarily in XYZ-space. If using
FRAX(X,Y,Z) or FRAX, feedrate-specified moves will be at the specified vector feedrate in XYZ-space.
Default feedrate axes for a coordinate system are X, Y, and Z.
Example:
FRAX ; Make all axes feedrate axes
FRAX(X,Y) ; Make X and Y axes only the feedrate axes
FRAX(X,Y,Z) ; Make X, Y, and Z axes only the feedrate axes
See Also:
Feedrate-Specified Moves (Writing and Executing Motion Programs)
Program commands F{data}, FRAX.
FREAD
Function: Read of parameters stored with FSAVE
Scope: Global
Syntax: FREAD
The FREAD command causes Turbo PMAC to copy the last values of P8107 – P8191 stored to a special
sector of non-volatile flash memory with a FSAVE command back into the variables in active RAM.
Values stored for these variables with the FSAVE command are never copied back into active RAM
without an FREAD command.
On power-up/reset, Turbo PMAC automatically copies the last values stored in the main bank of flash
memory by the most recent full SAVE command into active RAM (along with those for all of the other
variables). These values may not be the same as the last values stored with the FSAVE command. A
subsequent FREAD command will overwrite these values with the last values stored with an FSAVE
command.
If nothing has been saved to these sectors of flash memory since it was last cleared with an
FSAVECLEAR command, all values of P8107 – P8191 will be set to 0, but no error will be reported. If
the sector of flash memory is bad, this command will be rejected with an error (reporting ERR022 if I6 is
set to 1 or 3).
FSAVE
Function: Fast save of certain parameters
Scope: Global
Syntax: FSAVE
FSAV
The FSAVE command causes Turbo PMAC to do a fast copy of the values of the highest 85 P-variables
(P8107 – P8191) from active memory (RAM) to special sectors of non-volatile flash memory. This save
operation of 512 bytes occurs in a few milliseconds rather than the several seconds for a full SAVE
operation, so can be done without disrupting machine operation. (However, during the approximately 5
milliseconds it takes to execute the FSAVE command, no other background tasks, including safety
checks, are performed. Foreground tasks such as servo loop closure are performed during the FSAVE
process.) It is intended to permit the quick storage of machine-state information for proper start-up after a
quick, or especially an unexpected, power-down.
After a power-up/reset, the values stored with the FSAVE command are not copied back into the active
registers in RAM until an FREAD command is issued to the Turbo PMAC. On power-up/reset, Turbo
PMAC automatically copies the last values for these variables stored with a full SAVE command to the
main bank of flash memory. A subsequent FREAD command will overwrite these values with the last
values stored with an FSAVE command.
After every 256th FSAVE command, one of the two flash-memory sectors for this function is filled, and
Turbo PMAC must clear the other sector to enable further FSAVE commands, an operation that takes 1 –
2 seconds. This does not keep any other Turbo PMAC tasks from operating, but if another FSAVE
command is executed during this time, it will be rejected with an error (reporting ERR021 if I6 is set to 1
or 3), and bit 6 of global status word Y:$000006 is set to 1. Operation of the flash memory past 100,000
clear cycles cannot be guaranteed, so there should be no more than 25,000,000 FSAVE commands issued
over the lifetime of the machine.
If the saving operation fails due to a bad flash sector, the command will be rejected with an error
(reporting ERR022 if I6 is set to 1 or 3), and bit 7 of global status word Y:$000006 will be set to 1.
The FSAVE command works on all flash-memory ICs being used in manufacturing as of the
implementation of the command in 2005. However, it may not work on older Turbo PMACs. Bits 1 and
2 of I4904 must both be set to 1 (i.e. the last hex digit of I4904 must be $6 or $7) to permit operation of
the FASVE command. If the command is issued to a Turbo PMAC with an older flash-memory IC, the
command will be rejected with an error (reporting ERR020 if I6 is set to 1 or 3.)
FSAVECLEAR
Function: Clear FSAVE flash-memory sectors
Scope: Global
Syntax: FSAVECLEAR
FSAVCLR
The FSAVECLEAR command causes Turbo PMAC to clear both of the sectors of flash memory reserved
for the FSAVE “fast save” function. If an FREAD command is then issued before another FSAVE
command is used to save real data into these flash sectors, all of the variable values will be set to 0.
GATHER
Function: Begin data gathering.
Scope: Global
Syntax: GATHER [TRIGGER]
GAT [TRIG]
This command causes data gathering to commence according to the configuration defined in I-variables
I5000 – I5051. If TRIGGER is not used in the command, gathering will start on the next servo cycle. If
TRIGGER is used, gathering will start on the first servo cycle after machine input MI2 goes true.
Gathering will proceed at the frequency set by I5049 (in number of servo interrupt cycles). If I5049 is 0,
only one set of data will be gathered per GATHER command. If Turbo PMAC is already gathering data,
GATHER will cause resynchronization of the gathering cycle to the next servo cycle.
Gathering will continue until Turbo PMAC receives an ENDGATHER command, or until the buffer
created by the DEFINE GATHER command is full.
This command is usually used in conjunction with the data gathering and plotting functions of the Turbo
PMAC Executive Program.
If a motion or PLC program buffer is open when this command is sent to Turbo PMAC, the command
will be entered into that buffer for later execution.
Example:
GAT B1R ; Start gathering and run program 1
ENDG ; Stop gathering -- give this command when moves of interest are done
OPEN PROG2 CLEAR
X10
DWELL1000
CMD"GATHER" ; Program issues start command here
X20 ; Move of interest
DWELL50
CMD"ENDG" ; Program issues stop command here
CLOSE
See Also:
Data Gathering Function (Analysis Features)
I-variables I5000 – I5051
On-line commands DEFINE GATHER, GATHER, LIST GATHER, DELETE GATHER
Gathering and Plotting (Turbo PMAC Executive Program Manual)
H
Function: Perform a feedhold
Scope: Coordinate-system specific
Syntax: H
This causes the currently addressed coordinate system to suspend execution of the program starting
immediately by bringing its time base value to zero, decelerating along its path at a rate defined by the
coordinate system I-variable Isx95.
The program is suspended while in feedhold mode, but technically still executing. If it is subsequently
desired that program execution will not be resumed, program execution should be aborted with the A
command
The H command is very similar in effect to a %0 command, except that deceleration is controlled by
Isx95, not Isx94, and execution can be resumed with an R or an S command, instead of a %100
command. In addition, H works under external time base, whereas a %0 command does not.
Jogging moves are permitted while in feedhold mode (unlike in non-Turbo PMACs). However, all
motors must be returned to their exact feedhold position (using the J= command) before the program may
be resumed.
Full speed execution along the path will commence again on an R or S command. The ramp up to full
speed will also take place at a rate determined by Isx95 (full time-base value, either internally or
externally set). Once the full speed is reached, Isx94 determines any time-base changes.
If the R or S command is issued when any motor is not commanding its feedhold position, Turbo PMAC
will reject the command with an error, reporting an ERR0017 if I6 has been set to 1 or 3.
See Also:
Stopping Commands (Making an Application Safe)
Control-Panel Port HOLD/ Input (Connecting Turbo PMAC to the Machine)
Time-Base Control (Synchronizing Turbo PMAC to External Events)
I-variables Isx93, Isx94, Isx95
On-line commands <CTRL-O>, %, %{constant}, A, K, \, Q
JPAN Connector Pin 12
HOME
Function: Start Homing Search Move
Scope: Motor specific
Syntax: HOME
HM
This command causes the addressed motor to perform a homing search routine. The characteristics of the
homing search move are controlled by motor I-variables Ixx97 and Ixx19-Ixx26, plus encoder I-variables
2 and 3 for that motor's position encoder.
The on-line home command simply starts the homing search routine. Turbo PMAC provides no
automatic indication that the search has completed (although the In-Position interrupt could be used for
this purpose) or whether the move completed successfully. Polling, or a combination of polling and
interrupts, is generally used to determine completion and success.
By contrast, when a homing search move is given in a motion program (e.g. HOME1,2), the motion
program will keep track of completion by itself as part of its sequencing algorithms.
Note the difference in syntax between the on-line homing search move command (#xHOME) and the
buffered motion program homing search move statement (HOMEn)
If there is an axis offset in the axis-definition statement for the motor, and/or following error in the motor
servo loop, the reported position at the end of the homing search move will be equal to the axis offset
minus the following error, not to zero.
Example:
HOME ; Start homing search on the addressed motor
#1HM ; Start homing search on Motor 1
#3HM#4HM ; Start homing search on Motors 3 and 4
See Also:
Control Panel Port HOME/ Input (Connecting Turbo PMAC to the Machine)
Homing Moves (Basic Motor Moves)
I-variables Ixx03, Ixx19-Ixx26, Encoder I-Variables 2 & 3
On-line command HOMEZ
Program command HOME{constant}, HOMEZ{constant}
JPAN Connector Pin 11
HOMEZ
Function: Do a Zero-Move Homing
Scope: Motor specific
Syntax: HOMEZ
HMZ
This command causes the addressed motor to perform a zero-move homing search.
Instead of jogging until it finds a pre-defined trigger, and calling its position at the trigger the home
position, with this command, the motor calls wherever it is (commanded position) at the time of the
command the home position.
If there is an axis offset in the axis-definition statement for the motor, and/or following error in the motor
servo loop, the reported position at the end of the homing operation will be equal to the axis offset minus
the following error, not to zero.
Example:
On-line Command Examples:
HOMEZ ; Do zero-move homing search on the addressed motor
#1HMZ ; Do zero-move homing search on Motor 1
#3HMZ#4HMZ ; Do zero-move homing search on Motors 3 and 4
Buffered Motion Program Examples
HOMEZ1
HOMEZ2,3
On-line Commands Issued from PLC Program
IF (P1=1) ;
CMD"#5HOMEZ" ; Program issues on-line command
P1=0 ; So command is not repeatedly issued
ENDIF
See Also:
Homing Moves (Basic Motor Moves)
On-line command HOME
Program command HOME{constant}, HOMEZ{constant}
I{constant}
Function: Report the current I-variable values.
Scope: Global
Syntax: I{constant}[..{constant}]
where:
{constant} is an integer from 0 to 8191 representing the number of the I-variable;
the optional second{constant} must be at least as great as the first {constant} -- it represents
the number of the end of the range;
I{constant},{constant},{constant}
where:
the first {constant} is an integer from 0 to 8190 representing the number of the first I-variable;
the second {constant} is an integer from 1 to 8191 representing the number I-variables whose
value is to be reported;
the third {constant} is an integer from 1 to 8191 representing the numerical spacing between each
I-variable whose value is to be reported.
This command causes Turbo PMAC to report the current value of the specified I-variable, or range or set
of I-variables.
When I9 is 0 or 2, only the value of the I-variable itself is returned (e.g. 10000). When I9 is 1 or 3, the
entire variable value assignment statement (e.g. I130=10000) is returned by Turbo PMAC.
When I9 is 0 or 1, the values of address I-variables are reported in decimal form. When I9 is 2 or 3, the
values of these variables are reported in hexadecimal form.
Note:
If a motion program buffer (including a rotary buffer) is open, I{constant}
will be entered into that buffer for later execution, to be interpreted as a full-circle
move command with a vector to the center along the X-axis (see Circular Moves in
the Writing and Executing Motion Programs section).
Example:
I5 ; Request the value of I5
2 ; Turbo PMAC responds
I130..135 ; Request the value of I130 through I135
60000 ; Turbo PMAC responds with 6 lines
5000
5000
50000
1
20000
I130,4,100 ; Request the value of I130, I230, I330, I430
60000 ; Turbo PMAC responds with 4 lines
55000
60000
65000
To see the effect of I9 on the form of the response, observe the following:
I9=0 I125
491520 ; Short form, decimal
I9=1 I125
I125=491520 ; Long form, decimal
I9=2 I125
$78000 ; Short form, hexadecimal
I9=3 I125
I125=$78000 ; Long form, hexadecimal
See Also:
Initialization (I) Variables (Computational Features)
I-Variable Specifications
I-variable I9
On-line commands I{constant}={expression}, M{constant}, P{constant},
Q{constant}
Program commands {axis}{data}{vector}{data}, I{data}
I{data}={expression}
Function: Assign a value to an I-variable.
Scope: Global
Syntax: I{data}={expression}
where:
{data} is a constant, or an expression in parentheses, for an integer value from 0 to 8191
representing the I-variable number;
{expression} contains the value to be given to the specified I-variable
I{constant}..{constant}={constant}
where:
the first {constant} is an integer from 0 to 8190 representing the number of the first I-variable;
the second {constant} is an integer from 1 to 8191 representing the number of the last I-variable;
it must be at least as great as the first {constant}
the final {constant} contains the value to be given to the specified range of I-variables
I{constant},{constant},{constant}={constant}
where:
the first {constant} is an integer from 0 to 8190 representing the number of the first I-variable;
the second {constant} is an integer from 1 to 8191 representing the number of I-variables whose
value is to be set;
the third {constant} is an integer from 1 to 8191 representing the numerical spacing between each
I-variable whose value is to be set;
the final {constant} contains the value to be given to the specified set of I-variables
This command assigns the value on the right side of the equals sign to the specified I-variable, or range
or set of I-variables.
If a motion or PLC program buffer is open when the single-variable form of this command is sent to
Turbo PMAC, the command will be entered into the buffer for later execution. If a motion or PLC
program buffer is open when the multiple-variable form of this command is sent, Turbo PMAC will reject
the command with an error, reporting ERR003 if I6 is 1 or 3.
Examples:
I5=2
I130=1.25*I130
I(P1*100+30)=300000
I5001..5048=0
I102=$78003
I100,5,100=1 ; Sets I100, I200, I300, I400, I500 to 1
I104=I103
See Also:
Initialization (I) Variables (Computational Features)
I-Variable Specifications
On-line commands I{constant}, M{data}={expression}, P{data}={expression},
Q{data}={expression}
I{constant}=*
Function: Assign factory default value to an I-variable.
Scope: Global
Syntax: I{constant}[..{constant}]=*
where:
{constant} is an integer from 0 to 8191 representing the number of the I-variable;
the optional second{constant} must be at least as great as the first {constant} -- it represents
the number of the end of the range;
I{constant},{constant},{constant}
where:
the first {constant} is an integer from 0 to 8190 representing the number of the first I-variable;
the second {constant} is an integer from 1 to 8191 representing the number of I-variables to be
set to default values;
the third {constant} is an integer from 1 to 8191 representing the numerical spacing between each
I-variable to be set to default values
This command sets the specified I-variable or range of I-variables to the factor default value. Each I-
variable has its own factory default; these are shown in the I-Variable Specification section.
Example:
I13=*
I100..199=*
IDC
Function: Force active clock equal to ID-module clock
Scope: Global
Syntax: IDC
This command forces the active real-time clock in RAM to have the same time as the non-volatile real-
time clock in the Option 18B ID-number and clock/calendar module. It copies the time value from the ID
module into the active timer register in RAM, and reports this time back to the host computer. The time
is reported in the international 24-hour clock format:
{hh}:{mm}:{ss}
where:
{hh} is the 2-digit representation of the hour (00 <= {hh} <= 23)
{mm} is the 2-digit representation of the minute (00 <= {mm} <= 59)
{ss} is the 2-digit representation of the second (00 <= {ss} <= 59)
On power-up/reset, the time value in the Option 18B module is automatically copied into the timer
register in RAM. From that point on, however, both timers increment independently, and can drift apart.
The IDC command can be used periodically to force them back together.
See Also:
On-line commands TIME, TIME={time}, TODAY, UPDATE
IDNUMBER
Function: Report electronic identification number
Scope: Global
Syntax: IDNUMBER
IDNUM
This command causes Turbo PMAC to report the electronic identification number from the Option 18A
ID-number module, or the Option 18B ID-number & clock/calendar module.
The identification number is reported as a hexadecimal 16-digit ASCII string, representing a 64-bit value.
The first two hex digits represent the 8-bit checksum value for the module; these should match the
checksum digits engraved on the case of the module. The last two hex digits represent the module class;
these should match the class digits engraved on the case of the module (currently 01 for Option 18A, and
04 for Option 18B). The middle 12 hex digits represent the unique number for each module and board.
If no ID-number module is present, Turbo PMAC will return a 0.
The electronic identification number has no relationship to the serial number that is engraved on the
circuit board.
This command is identical to the SID command.
Example:
IDNUMBER
374A256E9014D101
INC
Function: Specify Incremental Move Mode
Scope: Coordinate-system specific
Syntax: INC
INC({axis}[,{axis}...])
where:
{axis} is a letter (X, Y, Z, A, B, C, U, V, W) representing the axis to be specified, or the character
R to specify radial vector mode
No spaces are permitted in this command.
The INC command without arguments causes all subsequent positions for all axes in position motion
commands to be treated as incremental distances. An INC statement with arguments causes the specified
axes to be in incremental mode, and all others stay the way they were before. The default axis specification
is absolute.
If R is specified as one of the axes, the I, J, and K terms of the circular move radius vector specification
will be specified in incremental form (i.e. as a vector from the move start point, not from the origin). An
INC command without any arguments does not affect this vector specification. The default vector
specification is incremental.
If a motion program buffer is open when this command is sent to Turbo PMAC, it will be entered into the
buffer as a program statement.
Example:
INC(A,B,C) ; A, B, and C axes made incremental other axes and rad vector left as is
INC ; All axes made incremental -- radius vector left as is
INC(R) ; Radius vector made incremental -- all axes left as is
See Also:
J-
Function: Jog Negative
Scope: Motor specific
Syntax: J-
This command causes the addressed motor to jog in the negative direction indefinitely. Jogging
acceleration and velocity are determined by the values of Ixx19-Ixx22 in force at the time of this
command.
Turbo PMAC will reject this command if the motor is in a coordinate system that is currently running a
motion program (reporting ERR001 if I6 is 1 or 3).
Example:
J- ; Jog addressed motor negative
#5J- ; Jog Motor 5 negative
#3J-#4J- ; Jog Motors 3 and 4 negative
See Also:
Control Panel Port JOG-/ Input (Connecting Turbo PMAC to the Machine)
JPAN Connector Pin 4
Jogging Moves (Basic Motor Moves)
I-variables Ixx19-Ixx22
On-line commands J+, J/, J=, J={constant}, J:{constant}, J^{constant}
J/
Function: Jog Stop
Scope: Motor specific
Syntax: J/
This command causes the addressed motor to stop jogging. It also restores position control if the motor's
servo loop has been opened (enabled or killed), with the new commanded position set equal to the actual
position at the time of the J/ command. Jogging deceleration is determined by the values of Ixx19-Ixx21
in force at the time of this command.
Turbo PMAC will reject this command if the motor is in a coordinate system that is currently running a
motion program (reporting ERR001 if I6 is 1 or 3).
Example:
#1J+ ; Jog Motor 1 positive
J/ ; Stop jogging Motor 1
O5 ; Open-loop output of 5% on Motor 1
O0 ; Open loop output of 0%
J/ ; Restore closed-loop control
K ; Kill output
J/ ; Restore closed-loop control
See Also:
Control Panel Port JOG+/, JOG-/ Inputs (Connecting Turbo PMAC to the Machine)
JPAN Connector Pin 4, 6
Jogging Moves (Basic Motor Moves)
I-variables Ixx19-Ixx22
On-line commands <CTRL-A>, A, J+, J-, J=, J={constant}, J:{constant}, J^{constant},
K, O{constant}
J:{constant}
Function: Jog Relative to Commanded Position
Scope: Motor specific
Syntax: J:{constant}
where:
{constant} is a floating point value specifying the distance to jog, in counts.
This command causes a motor to jog the distance specified by {constant} relative to the present
commanded position. Jogging acceleration and velocity are determined by the values of Ixx19-Ixx22 in
force at the time of this command. Compare to J^{constant}, which is a jog relative to the present
actual position.
A variable incremental jog command can be executed with the J:* command
Turbo PMAC will reject this command if the motor is in a coordinate system that is currently running a
motion program (reporting ERR001 if I6 is 1 or 3).
Example:
#1HM ; Do homing search move on Motor 1
J:2000 ; Jog a distance of 2000 counts (to 2000 counts)
J:2000 ; Jog a distance of 2000 counts (to 4000 counts)
See Also:
Jogging Moves (Basic Motor Moves)
I-variables Ixx19-Ixx22
On-line commands J+, J-, J/, J=, J={constant}, J^{constant}
J:*
Function: Jog to specified variable distance from present commanded position
Scope: Motor specific
Syntax: J:*
This command causes the addressed motor to jog the distance specified in the motor’s variable jog
position/distance register relative to the present commanded position. Jogging acceleration and velocity
are determined by the values of Ixx19-Ixx22 in force at the time of this command. Compare to J^* ,
which is a jog relative to the present actual position.
The variable jog position/distance register is a floating-point register with units of counts. The register is
located at Turbo PMAC address L:$0000D7 for motor 1, L:$000157 for motor 2, etc. It is best accessed
with a floating-point M-variable; the suggested M-variable is Mxx72. The usual procedure is to write the
destination position to this register by assigning a value to the M-variable, then issuing the J:*
command.
Turbo PMAC will reject this command if the motor is in a coordinate sytem that is currently running a
motion program (reporting ERR001 if I6 is 1 or 3).
Example:
M172->L:$0000D7 ; Define #1 variable jog position/distance reg.
#1HMZ ; Declare present position to be zero
M172=3000 ; Assign distance value to register
#1J:* ; Jog Motor 1 this distance; end cmd. pos. will be 3000
#1J:* ; Jog Motor 1 this distance; end cmd. pos. will be 6000
M172=P1*SIN(P2) ; Assign new distance value to register
#1J:* ; Jog Motor 1 this distance
#1J= ; Return to prejog target position
See Also:
Turbo PMAC will reject this command if the motor is in a coordinate system that is currently running a
motion program (reporting ERR001 if I6 is 1 or 3).
Example:
J=0 ; Jog addressed motor to position 0
#4J=5000 ; Jog Motor 4 to 5000 counts
#8J=-32000 ; Jog Motor 8 to -32000 counts
See Also:
Jogging Moves (Basic Motor Moves)
I-variables Ixx19-Ixx22
On-line commands J+, J-, J/, J=, J:{constant}, J^{constant}, J=*, J:*, J^*
J=*
Function: Jog to specified variable position
Scope: Motor specific
Syntax: J=*
This command causes the addressed motor to jog to the position specified in the motor's “variable jog
position/distance” register. Jogging acceleration and velocity are determined by the values of Ixx19-
Ixx22 in force at the time of this command.
The variable jog position/distance register is a floating-point register with units of counts. The register is
located at Turbo PMAC address L:$0000D7 for motor 1, L:$000157 for motor 2, etc. It is best accessed
with a floating-point M-variable; the suggested M-variable is Mxx72. The usual procedure is to write the
destination position to this register by assigning a value to the M-variable, then issuing the J=*
command.
Virtually the same result can be obtained by writing to the motor target position register and issuing the
J= command. However, using the J=* command permits the returning to the real target position
afterwards without having to restore the target position register. Also, the J=* command uses a register
whose value is scaled in counts, not fractions of a count.
Turbo PMAC will reject this command if the motor is in a coordinate sytem that is currently running a
motion program (reporting ERR001 if I6 is 1 or 3).
Example:
M172->L:$0000D7 ; Define #1 variable jog position/distance reg.
M172=3000 ; Assign position value to register
#1J=* ; Jog Motor 1 to this position
M172=P1*SIN(P2) ; Assign new position value to register
#1J=* ; Jog Motor 1 to this position
#1J= ; Return to prejog target position
See Also:
Jogging Moves (Basic Motor Moves)
I-variables Ixx19-Ixx22
Memory map registers L:$0000D7, L:$0000157, etc.
Suggested M-variable definitions M172, M272, etc.
On-line commands J=, J={constant}, J:*, J^*
J=={constant}
Function: Jog to specified motor position and make that position the “pre-jog” position
Scope: Motor specific
Syntax: J=={constant}
where:
{constant} is a floating point value specifying the location to which to jog, in encoder counts
This command causes the addressed motor to jog the position specified by {constant}. It also makes
this position the pre-jog position, so it will be the destination of subsequent J= commands. Jogging
acceleration and velocity are determined by the values of Ixx19-Ixx22 in force at the time of this
command.
Turbo PMAC will reject this command if the motor is in a coordinate system that is currently running a
motion program (reporting ERR001 if I6 is 1 or 3).
Example:
#1J==10000 ; Jog Motor 1 to 10000 counts and make that the pre-jog position.
J+ ; Jog indefinitely in the positive direction
J= ; Return to 10000 counts
See Also:
Jogging Moves (Basic Motor Moves)
I-variables Ixx19-Ixx22
On-line commands J=, J={constant}, J=*, J^*
J^{constant}
Function: Jog Relative to Actual Position
Scope: Motor specific
Syntax: J^{constant}
where:
{constant} is a floating point value specifying the distance to jog, in counts.
This causes a motor to jog the distance specified by {constant} relative to the present actual position.
Jogging acceleration and velocity are determined by the values of Ixx19-Ixx22 in force at the time of this
command. Compare to J:{constant}, which is a jog relative to the present commanded position.
Usually the J:{constant} command is more useful, because its destination is not dependent on the
following error at the instant of the command. The J^0 command can be useful for swallowing any
existing following error.
A variable incremental jog can be executed with the J^* command
Turbo PMAC will reject this command if the motor is in a coordinate system that is currently running a
motion program (reporting ERR001 if I6 is 1 or 3).
Example:
#1HM ; Do homing search move on Motor 1
J^2000 ; Jog a distance of 2000 counts from actual position
; If actual was -5 cts, new command pos is 1995 cts
J^2000 ; Jog a distance of 2000 counts from actual position
; If actual was 1992 cts, new cmd pos is 3992 cts
See Also:
Jogging Moves (Basic Motor Moves)
I-variables Ixx19-Ixx22
On-line commands J+, J-, J/, J=, J={constant}, J:{constant}, J=*, J:*, J^*
J^*
Function: Jog to specified variable distance from present actual position
Scope: Motor specific
Syntax: J^*
This command causes the addressed motor to jog the distance specified in the motor’s variable jog
position/distance register relative to the present actual position. Jogging acceleration and velocity are
determined by the values of Ixx19-Ixx22 in force at the time of this command. Compare to J:* , which
is a jog relative to the present commanded position.
The variable jog position/distance register is a floating-point register with units of counts. The register is
located at Turbo PMAC address L:$0000D7 for motor 1, L:$000157 for motor 2, etc. It is best accessed
with a floating-point M-variable; the suggested M-variable is Mxx72. The usual procedure is to write the
destination position to this register by assigning a value to the M-variable, then issuing the J^* command.
Turbo PMAC will reject this command if the motor is in a coordinate system that is currently running a
motion program (reporting ERR001 if I6 is 1 or 3).
Example:
M172->L:$0000D7 ; Define #1 variable jog position/distance reg.
#1HMZ ; Declare present position to be zero
M172=3000 ; Assign distance value to register
#1J^* ; Jog Motor 1 this distance; if following error at command was 3,
; end cmd. pos. will be 2997
#1J^* ; Jog Motor 1 this distance; if following error at command was 2, end cmd.
; pos. will be 5995
M172=P1*SIN(P2) ; Assign new distance value to register
#1J^* ; Jog Motor 1 this distance
#1J= ; Return to prejog target position
See Also:
Jogging Moves (Basic Motor Moves)
I-variables Ixx19-Ixx22
Memory map registers L:$0000D7, L:$000157, etc.
Suggested M-variable definitions M172, M272, etc.
On-line commands J=, J={constant}, J=*, J^*
{jog command}^{constant}
Function: Jog until trigger
Scope: Motor specific
Syntax: J=^{constant}
J={constant}^{constant}
J:{constant}^{constant}
J^{constant}^{constant}
J=*^{constant}
J:*^{constant}
J^*^{constant}
where:
{constant} after the ^ is a floating point value specifying the distance from the trigger to which to
jog after the trigger is found, in encoder counts
This command format permits a jog-until-trigger function. When the ^{constant} structure is added
to any definite jog command, the jog move can be interrupted by a pre-defined trigger condition, and the
motor will move to a point relative to the trigger position as specified by the final value in the command.
The indefinite jog commands J+ and J- cannot be turned into jog-until-trigger moves.
Jog-until-trigger moves are very similar to homing search moves, except they have a definite end position
in the absence of a trigger, and they do not change the motor zero position. In addition, in the absence of
a trigger, the move will simply stop at the first destination.
Trigger Condition: The trigger condition for a jog-until-trigger move can either be an input flag, or a
warning following error condition for the motor. If bit 1 of Ixx97 is 0 (the default), the trigger is a
transition of an input flag and/or encoder index channel from the set defined for the motor by Ixx25.
Encoder/flag variables 2 and 3 (I7mn2 and I7mn3) define which edges of which input signals create the
trigger.
If bit 1 of Ixx97 is 1, the trigger is the warning following error status bit of the motor becoming true.
Ixx12 for the motor sets the error threshold for this condition.
Trigger Position: The trigger position can either be the hardware-captured position for the, or a
software-read position. If bit 0 of Ixx97 is 0 (the default), the encoder position latched by the trigger in
Turbo PMAC’s DSPGATE hardware is used as the trigger position. This is the most accurate option
because it uses the position at the moment of the trigger, but it can be used only with incremental encoder
feedback brought in on the same channel number as the triggering flag set. This option cannot be used for
other types of feedback, or for triggering on following error.
If bit 0 of Ixx97 is 1, Turbo PMAC reads the present sensor position after it sees the trigger. This can be
used with any type of feedback and either trigger condition, but can be less accurate than the hardware
capture because of software delays.
Trigger Occurrence: The trigger move bit, bit 7 of the second motor status word (Y:$0000C0,
Y:$000140, etc.) is set to 1 at the beginning of the pre-trigger move, and cleared to 0 only when the
trigger is found. It can be checked at any time, including after the move, to see if the trigger has occurred.
Jogging acceleration and velocity are determined by the values of Ixx19-Ixx22 in force at the time of this
command.
Turbo PMAC will reject this command if the motor is in a coordinate system that is currently running a
motion program (reporting ERR001 if I6 is 1 or 3).
Example:
#1J=^1000 ; Jog to pre-jog position in the absence of a trigger, but if trigger is found,
; jog to +1000 cts from trigger.
#2J:5000^-100 ; Jog 5000 counts in the positive direction in the absence of a trigger,
; but if trigger is found, jog to -100 cts from trigger position.
#3J=20000^0 ; Jog to 20000 counts in the absence of a trigger, but if trigger is found,
; return to trigger position.
See Also:
Jogging Moves (Basic Motor Moves)
I-variables Ixx97, Ixx19-Ixx22, Ixx25, I7mn2, I7mn3
On-line commands J=, J={constant}, J:{constant}, J^{constant},
J=*, J:*, J^*
Program commands {axis}{data}^{data}
K
Function: Kill motor output
Scope: Motor specific
Syntax: K
This command causes Turbo PMAC kill the outputs for the addressed motor. The servo loop is disabled,
the position/velocity servo-loop output is set to zero (Ixx29 and/or Ixx79 offsets are still in effect), and the
AENA output for the motor is taken to the disable state (polarity is determined by E17 on PMAC-style
channels).
Closed-loop control of this motor can be resumed with a J/ command. The A command will re-establish
closed-loop control for all motors in the addressed coordinate system, and the <CTRL-A> command will
do so for all motors on Turbo PMAC.
The action on a K command is equivalent to what Turbo PMAC does automatically to the motor on an
amplifier fault or a fatal following error fault.
Turbo PMAC will reject this command if the motor is in a coordinate system that is currently running a
motion program (reporting ERR001 if I6 is 1 or 3). The program must be stopped first, usually with an A
command. However, the global <CTRL-K> command will kill all motors immediately, regardless of
whether any are running motion programs.
Example:
K ; Kill the addressed motor
#1K ; Kill Motor 1
J/ ; Re-establish closed-loop control of Motor 1
See Also:
Amplifier Fault, Following Error Limits, Stop Commands (Making an Application Safe)
I-variables Ixx29, Ixx79
On-line commands <CTRL-A>, <CTRL-K>, A, Q, H, J/
Jumpers E17, E17A-E17H
LEARN
Function: Learn present commanded position
Scope: Coordinate-system specific
Syntax: LEARN[({axis}[,{axis}...]]
[({axis}[,{axis}...]]
where:
{axis} (optional) is a character (X, Y, Z, A, B, C, U, V, W) specifying which axis’ position is to be
learned. If none are listed, the positions for all axes are learned.
No spaces are permitted in this command.
This command causes Turbo PMAC to add a line to the end of the open motion program buffer containing
axis position commands equal to the current commanded positions for some or all of the motors defined in
the addressed coordinate system. In this way Turbo PMAC can learn a sequence of points to be repeated by
subsequent execution of the motion program.
If no motion program buffer is open, or if the motion program buffer that is open has been opened from
another port, Turbo PMAC will reject this command and report an error (ERR003 if I6=1 or 3).
Turbo PMAC effectively performs a PMATCH function, reading motor commanded positions and
inverting the axis definition equations to compute axis positions.
If axis names are specified in the LEARN command, only position commands for those axes are used in
the line added to the motion program. If no axis names are specified in the learn command, position
commands for all nine possible axis names are used in the line added to the motion program. The
position command for an axis with no motor attached (“phantom” axis) will be zero.
Note:
If a motor is closed loop, the learned position will differ from the actual position
by the amount of the position following error because commanded position is used.
If a motor is open-loop or killed, Turbo PMAC automatically sets motor
commanded position equal to motor actual position, so the LEARN function can be
used regardless of the state of the motor.
Example:
&1 ; Address coordinate system 1
#1->10000X ; Define motor 1 in C.S. 1
#2->10000Y ; Define motor 2 in C.S. 1
OPEN PROG 1 CLEAR Prepare program buffer for entry
F10 TA200 TS50 ; Enter required non-move commands {move motors to a position,
; e.g. #1 to 13450 commanded, #2 to 29317 commanded}
LEARN(X,Y) ; Tell PMAC to learn these positions
X1.345 Y2.9317 ; This is the line that PMAC adds to PROG 1 {move motors to new
; position, e.g. #1 to 16752 cmd., #2 to 34726 cmd}
LEARN ; Tell PMAC to learn positions
A0 B0 C0 U0 V0 W0 X1.6752 Y3.4726 Z0
; PMAC adds positions for all axes to PROG 1
See Also:
Learning a Motion Program (Writing and Executing Motion Programs)
On-line command PMATCH
LIST
Function: List the contents of the currently opened buffer.
Scope: Global
Syntax: LIST
This command causes Turbo PMAC to report the contents of the currently opened buffer (PLC, PROG, or
ROT) to the host. If no buffer is open, or if the buffer that is open has been opened from another port,
Turbo PMAC will report an error (ERR003 if I6=1 or 3). Note that what is reported will not include any
OPEN, CLEAR, or CLOSE statements (since these are not program commands).
An unopened buffer can be listed by specifying the buffer name in the list command (e.g. LIST PROG
1). See further LIST commands, below.
Example:
OPEN PROG 1 ; Open buffer for entry
LIST ; Request listing of open buffer
LINEAR ; Turbo PMAC reports contents of open buffer
F10
X20 Y20
X0 Y0
RETURN
CLOSE ; Close buffer
LIST ; Request listing of open buffer
<BELL>ERR003 ; Turbo PMAC reports error because
; no open buffer
See Also:
On-line commands OPEN, CLOSE, LIST PLC, LIST PROGRAM
LIST BLCOMP
Function: List contents of addressed motor's backlash compensation table
Scope: Motor specific
Syntax: LIST BLCOMP
This command causes Turbo PMAC to report to the host the contents of the backlash compensation table
belonging to the addressed motor. The values are reported in decimal ASCII form, multiple values to a
line, with individual values separated by spaces.
The LIST BLCOMP DEF command should be used to report the header information for this table.
If there is no table for the addressed motor, Turbo PMAC will reject the command (reporting ERR003 if
I6=1 or 3).
Example:
LIST BLCOMP ; Request contents of backlash comp table
9 17 -3 6 35 87 65 24 18 -9 -16 -34 ; PMAC responds
-7 12 -3 -8 32 44 16 0 -20 -5 0 ; Continued response
See Also:
Backlash Compensation Tables (Setting Up a Motor)
On-line commands DEFINE BLCOMP, DELETE BLCOMP, LIST BLCOMP DEF
Example:
LIST COMP ; Request contents of compensation table
9 17 -3 6 35 87 65 24 18 -9 -16 -34 ; PMAC responds
-7 12 -3 -8 32 44 16 0 -20 -5 0 ; Continued response
See Also:
Leadscrew Compensation Tables (Setting Up a Motor)
On-line commands DEFINE COMP, DELETE COMP, LIST COMP DEF
LIST COMP DEF
Function: List definition of addressed motor's compensation table
Scope: Motor specific
Syntax: LIST COMP DEF
This command causes Turbo PMAC to report to the host the definition of the compensation table that
belongs to the addressed motor.
The definition reported consists of the four items established in the DEFINE COMP command that set up
the motor (even if some of those items were not specified explicitly):
1. The number of entries in the table (number of rows and number of columns for a two-dimensional
table)
2. The number of the motor whose position provides the source data for the table (both source motors
for a two-dimensional table)
3. The number of the motor whose position is modified by the table
4. The span of the table in counts of the source motor (in both dimensions for a two-dimensional table)
If there is no table for the addressed motor, Turbo PMAC will reject the command (reporting ERR003 if
I6=1 or 3).
Note:
The compensation table belonging to this motor may not affect this motor’s
position or be affected by it.
Example:
LIST COMP DEF ; Request definition of compensation table
100,#2,#2,100000 ; Turbo PMAC responds; 100 entries in table, Motor 2 is
; source and target, span is 100,000 counts
#3 LIST COMP DEF ; Request definition of comp table belonging to Motor 3
10,20,#4,#5,#6,50000,100000 ; Turbo PMAC responds A 2D 10x20 table, span of
; 50Kx100K counts #4 & #5 as source, #6 as target
See Also:
Leadscrew Compensation Tables (Setting Up a Motor)
On-line commands DEFINE COMP, DELETE COMP, LIST COMP
LIST FORWARD
Function: Report contents of forward-kinematic program buffer.
Scope: Coordinate-system specific
Syntax: LIST FORWARD
LIS FWD
This command causes Turbo PMAC to report the contents of the forward-kinematic program buffer for
the addressed coordinate system to the host. The contents are reported in ASCII text form. If I9 is 0 or 2,
the contents are reported in short form (e.g. ENDW). If I9 is 1 or 3, the contents are reported in long form
(e.g. ENDWHILE).
If the forward kinematic program requested by this command does not exist in Turbo PMAC, Turbo
PMAC will reject this command (reporting an ERR003 if I6 is 1 or 3).
Forward kinematic programs can be protected by password. If there is a password for the Turbo PMAC,
and the password has not been given, Turbo PMAC will reject this command (reporting an ERR002 if I6
is 1 or 3).
See Also:
Kinematic Calculations
I-variable Isx50
On-line commands LIST INVERSE, OPEN FORWARD, OPEN INVERSE
LIST GATHER
Function: Report contents of the data gathering buffer.
Scope: Global
Syntax: LIST GATHER [{start}] [,{length}]
LIS GAT [{start}] [,{length}]
where:
the optional {start} parameter is an integer constant specifying the distance from the start of the
buffer (in words of memory) to begin the listing (0 is the default);
the optional {length} parameter (after a comma) is an integer constant specifying the number of
words of the buffer to be sent to the host (to the end of the buffer is the default)
This command causes Turbo PMAC to report the contents of the data gathering buffer to the host. The
data is reported as 48-bit long words in hexadecimal format (12 characters per word) separated by spaces,
16 long words per line.
If neither {start} nor {length} is specified, the entire contents of the buffer will be reported. If
{start} is specified, the reporting will begin {start} words from the beginning of the buffer. If
{length} is specified, the reporting will continue for {length} words from the starting point. The
starting point is referenced to the beginning memory location of the buffer. If gathering has rolled over
the buffer, as it can with I5000 = 1 or 3, the reported contents may not come in the same order as they
were gathered.
Example:
LIST GATHER ; reports the whole buffer
LIST GATHER 256 ; skips the first 256 long words
LIST GATHER 0,32 ; reports the first 32 words
LIST GATHER ,32 ; does the same as above
LIST GATHER 64,128 ; skips the first 64 words, reports the next 128
See Also:
Data Gathering Function (Analysis Features)
I-variables I5049, I5050 and I5051, I5001-I5048.
On-line commands GATHER, ENDGATHER, DEFINE GATHER
Gathering and Plotting (Turbo PMAC Executive Program Manual)
LIST INVERSE
Function: Report contents of inverse-kinematic program buffer.
Scope: Coordinate-system specific
Syntax: LIST INVERSE
LIS INV
This command causes Turbo PMAC to report the contents of the inverse-kinematic program buffer for the
addressed coordinate system to the host.
The contents are reported in ASCII text form. If I9 is 0 or 2, the contents are reported in short form (e.g.
ENDW). If I9 is 1 or 3, the contents are reported in long form (e.g. ENDWHILE).
If the inverse kinematic program requested by this command does not exist in Turbo PMAC, Turbo
PMAC will reject this command (reporting an ERR003 if I6 is 1 or 3).
Inverse kinematic programs can be protected by password. If there is a password for the Turbo PMAC,
and the password has not been given, Turbo PMAC will reject this command (reporting an ERR002 if I6
is 1 or 3).
See Also:
Kinematic Calculations
I-variable Isx50
On-line commands LIST FORWARD, OPEN FORWARD, OPEN INVERSE
LIST LDS
Function: List Linking Addresses of Ladder Functions
Scope: Global
Syntax: LIST LDS
This command causes Turbo PMAC to list the addresses of the internal routines that the special ladder-
logic PLC cross-compiler needs to properly compile and link programs. This command is used
automatically by the cross-compiler; a user only needs it directly for special debugging.
See Also:
On-line commands LIST LINK
LIST LINK
Function: List Linking Addresses of Internal Turbo PMAC Routines
Scope: Global
Syntax: LIST LINK
This command causes Turbo PMAC to list the addresses of the internal routines that the PLC cross-
compiler needs to properly compile and link its programs. This command is used automatically by the
PLC cross-compiler in the Executive program.
For the standalone DOS cross-compiler, the ASCII characters of Turbo PMAC's response to this
command must be contained in a file named LISTLINK.TXT in the same directory and subdirectory as
the cross-compiler. Each separate version of Turbo PMAC's firmware potentially has different addresses
for these routines, so a new LISTLINK.TXT file must be created any time the Turbo PMAC firmware is
updated, even for a minor change such as from V2.01A to V2.01B.
Example:
LIST LINK ; Request linking addresses
004532 004A97 005619 005F21 0062FE 0063A4
; Turbo PMAC responds
See Also:
Compiled PLCs (Writing a PLC Program)
LIST PC
Function: List Program at Program Counter
Scope: Coordinate-system specific
Syntax: LIST PC[,[{constant}]]
where:
{constant} is a positive integer representing the number of words in the program to be listed
This command causes Turbo PMAC to list the program lines that it is (are) about to calculate in the
addressed coordinate system, with the first line preceded by the program number and each line preceded
by the address offset. LIST PC just lists the next line to be calculated. LIST PC, lists from the next
line to be calculated to the end of the program.
LIST PC,{constant} lists the specified address range size starting at the next line to be calculated.
To see the current line of execution, use the LIST PE command.
Because Turbo PMAC calculates ahead in a continuous sequence of moves, the LIST PC (Program
Calculation) command will in general return a program line further down in the program than LIST PE
will.
If the coordinate system is not pointing to any motion program, Turbo PMAC will return an error
(ERR003 if I6=1 or 3). Initially the pointing must be done with the B{constant} command.
Example:
LIST PC ; List next line to be calculated
P1:22:X10Y20 ; Turbo PMAC responds
LIST PC,4 ; List next 4 words of program to be calculated
P1:22:X10Y20 ; Turbo PMAC responds
24:X15Y30
LIST PC, ; List rest of program
P1:22:X10Y20 ; Turbo PMAC responds
24:X15Y30
26:M1=0
28:RETURN
See Also:
On-line commands B{constant}, LIST, PC, LIST PE, PE
LIST PE
Function: List Program at Program Execution
Scope: Coordinate-system specific
Syntax: LIST PE[,[{constant}]]
where:
{constant} is a positive integer representing the number of words in the program to be listed
This command causes Turbo PMAC to list the program lines starting with the line containing the move
that it is currently executing in the addressed coordinate system, with the first line preceded by the
program number, and each line preceded by the address offset.
Because Turbo PMAC calculates ahead in a continuous sequence of moves, the LIST PC (Program
Calculation) command will in general return a program line further down in the program than LIST PE will.
LIST PE returns only the currently executing line. LIST PE, returns from the currently executing line
to the end of the program. LIST PE,{constant} returns the specified number of words in the
program, starting at the currently executing line.
If the coordinate system is not pointing to any motion program, Turbo PMAC will return an error
(ERR003 if I6=1 or 3). Initially the pointing must be done with the B{constant} command.
Example:
LIST PE ; List presently executing line
P5:35:X5Y30 ; Turbo PMAC responds
LIST PE,4 ; List 4 program words, starting with executing line
P5:35:X5Y30 ; Turbo PMAC responds
37:X12Y32
LIST PE, ; List rest of program, starting with executing line
7:RETURN
See Also:
PLC Program Features
I-variables I3, I4, I9
On-line commands LIST, LIST PROG, PASSWORD={string}
Program Command Specification
LIST PROGRAM
Function: List the contents of the specified motion program.
Scope: Global
Syntax: LIST PROGRAM {constant} [{start}] [,{length}]
LIST PROG {constant} [{start}] [,{length}]
where:
{constant} is an integer from 1 to 32767 specifying the number of the motion program
the optional {start} parameter is an integer constant specifying the distance from the start of the
buffer (in words of memory) to begin the listing (0 is the default);
the optional {length} parameter (after a comma) is an integer constant specifying the number of
words of the buffer to be sent to the host (to the end of the buffer is the default)
This command causes Turbo PMAC to report the contents of the specified fixed motion program buffer
(PROG) to the host. The contents are reported in ASCII text form. If I9 is 0 or 2, the contents are
reported in short form (e.g. LIN). If I9 is 1 or 3, the contents are reported in long form (e.g. LINEAR).
If neither {start} nor {length} is specified, the entire contents of the buffer will be reported.
If {start} is specified, the reporting will begin {start} words from the beginning of the buffer.
If {length} is specified, the reporting will continue for {length} words from the starting point.
If either {start}, {length}, or both, or just the comma, is included in the command, the listing of
the program will include the buffer address offsets with each line. Having a listing with these offsets can
be useful in conjunction with later use of the PC (Program-Counter) and LIST PC commands. If the
motion program requested by this command does not exist in Turbo PMAC, Turbo PMAC will reject this
command (reporting an ERR003 if I6=1 or 3).
PROGs 1000-32767 can be protected by password. If the PROG is protected by password, and the proper
password has not been given, Turbo PMAC will reject this command (reporting an ERR002 if I6=1 or 3).
Example:
LIST PROG 9 ; Request listing of all of motion program 9
LINEAR ; Turbo PMAC responds
F10
X10Y10
X0Y0
RETURN
LIST PROG 9, ; Request listing of program w/ address offsets
0:LINEAR
1:F10
2:X10Y10 ; Note that a 2-axis command takes 2 addresses
4:X0Y0
6:RETURN
LIST PROG 9,4 ; Request listing starting at address 4
4:X0Y0
6:RETURN
LIST PROG 9,2,4 ; Request listing starting at 2, 4 words long
2:X10Y10
4:X0Y0
LIST PROG 9,,2 ; Request listing starting at top, 2 words long
0:LINEAR
1:F10
See Also:
Writing and Executing Motion Programs
I-variables I3, I4, I9
On-line commands LIST, PC, LIST PC., PASSWORD={string}.
Program Command Specification
LIST ROTARY
Function: List contents of addressed coordinate system’s rotary program buffer
Scope: Coordinate-system specific
Syntax: LIST ROTARY [{start}] [,{length}]
LIST ROT [{start}] [,{length}]
where:
the optional {start} parameter is an integer constant specifying the distance from the start of the
buffer (in words of memory) to begin the listing (0 is the default);
the optional {length} parameter (after a comma) is an integer constant specifying the number of
words of the buffer to be sent to the host (to the end of the buffer is the default)
This command causes Turbo PMAC to report the contents of the rotary motion program buffer for the
addressed coordinate system to the host. The contents are reported in ASCII text form. If I9 is 0 or 2, the
contents are reported in short form (e.g. LIN). If I9 is 1 or 3, the contents are reported in long form (e.g.
LINEAR).
If neither {start} nor {length} is specified, the entire contents of the buffer will be reported. If
{start} is specified, the reporting will begin {start} words from the beginning of the buffer. If
{length} is specified, the reporting will continue for {length} words from the starting point.
If either {start}, {length}, or both, or just the comma, is included in the command, the listing of
the program will include the buffer address offsets with each line. Having a listing with these offsets can
be useful in conjunction with later use of the PC (Program-Counter) and LIST PC commands.
If the loading of the rotary buffer has caused the buffer to “wrap around” and re-use the beginning of the
buffer, the listing will start relative to this new top of the buffer (even if there are previously loaded, and
still unexecuted, lines at the bottom of the buffer.
See Also:
Writing and Executing Motion Programs
I-variables I3, I4, I9
On-line commands LIST, PC, LIST PE,
Program Command Specification
LIST TCOMP
Function: List contents of addressed motor's torque compensation table
Scope: Motor specific
Syntax: LIST TCOMP
This command causes Turbo PMAC to report to the host the contents of the torque compensation table
belonging to the addressed motor. The values are reported in decimal ASCII form, multiple values to a
line, with individual values separated by spaces.
The LIST TCOMP DEF command should be used to report the header information for this table.
If there is no table for the addressed motor, Turbo PMAC will reject the command (reporting ERR003 if
I6=1 or 3).
Example:
LIST TCOMP ; Request contents of torque comp table
9 17 -3 6 35 87 65 24 18 -9 -16 -34 ; PMAC responds
-7 12 -3 -8 32 44 16 0 -20 -5 0 ; Continued response
See Also:
Torque Compensation Tables (Setting Up a Motor)
On-line commands DEFINE TCOMP, DELETE TCOMP, LIST TCOMP DEF
LIST TCOMP DEF
Function: List definition of addressed motor's torque compensation table
Scope: Motor specific
Syntax: LIST TCOMP DEF
This command causes Turbo PMAC to report to the host the definition of the torque compensation table
that belongs to the addressed motor. The definition reported consists of the two items established in the
DEFINE TCOMP command that set up the motor:
1. The number of entries in the table;
2. The span of the table in counts of the motor.
If there is no table for the addressed motor, Turbo PMAC will reject the command (reporting ERR003 if
I6=1 or 3).
Example:
LIST TCOMP DEF ; Request def of addressed motor torque comp table
100,100000 ; Turbo PMAC responds; 100 entries in table, span is 100,000 counts
See Also:
Torque Compensation Tables (Setting Up a Motor)
On-line commands DEFINE TCOMP, DELETE TCOMP, LIST TCOMP
LOCK{constant},P{constant}
Function: Check/set process locking bit
Scope: Global
Syntax: LOCK{constant},P{constant}
where:
the first {constant} is an integer from 0 to 7 representing the number of the locking bit
the second {constant} is an integer from 0 to 8191 specifying the number of the P-variable used
to report the status of the locking bit
The LOCK command permits the user to check and possibly take possession of one of the eight process
locking bits in Turbo PMAC. These locking bits can prevent conflicts between tasks of different
priorities attempting to manipulate the same register. On-line commands and PLCs 1 –31 are background
tasks; motion programs and PLC 0 are higher-priority foreground tasks.
When the LOCK command is invoked, the P-variable specified in the command takes the value of the
locking bit immediately before the command is invoked. It takes a value of 0 if the locking bit was not
set before the command (meaning the process is available for this task); it takes a value of 1 if the locking
bit was set before the command (meaning the process is not available for this task).
The locking bit itself is always set to 1 at the end of a LOCK command. It will stay at 1 until cleared by
an UNLOCK command.
M{constant}
Function: Report the current M-variable values.
Scope: Global
Syntax: M{constant}[..{constant}]
where:
{constant} is an integer from 0 to 8191 representing the number of the M-variable;
the optional second {constant} must be at least as great as the first {constant} -- it represents
the number of the end of the range;
M{constant},{constant},{constant}
where:
the first {constant} is an integer from 0 to 8190 representing the number of the first M-variable;
the second {constant} is an integer from 1 to 8191 representing the number M-variables whose
value is to be reported;
the third {constant} is an integer from 1 to 8191 representing the numerical spacing between each
M-variable whose value is to be reported;
This command causes Turbo PMAC to report the current value of the specified M-variable, or range or
set of M-Variables. It does not cause Turbo PMAC to report the definition (address) of the M-Variables;
that is done with the M{constant}-> command.
Note:
If a motion program buffer (including a rotary buffer) is open when this command
is sent to Turbo PMAC it will be entered into the buffer for later execution, to be
interpreted as an M-code subroutine call.
Example:
M0 ; Host asks for value
3548976 ; Turbo PMAC's response
M165
5.75
M1..3
1
0
1
M103,4,100 ; Request for values of M103, M203, M303, M403
34221 ; Turbo PMAC responds with 4 lines
29726
-38657
47
See Also:
M-Variables (Computational Features)
On-line commands M{data}={expression}, M{constant}->
Program commands M{data}, M{data}={expression}
M{data}={expression}
Function: Assign value to M-variables.
Scope: Global
Syntax: M{data}={expression}
where:
{data} is a constant, or an expression in parentheses, for an integer value from 0 to 8191
representing the M-variable number;
{expression} contains the value to be given to the specified M-variable
M{constant}..{constant}={constant}
where:
the first {constant} is an integer from 0 to 8190 representing the number of the first M-variable;
the second {constant} is an integer from 1 to 8191 representing the number of the last M-
variable; it must be at least as great as the first {constant}
the final {constant} contains the value to be given to the specified range of M-variables
M{constant},{constant},{constant}={constant}
where:
the first {constant} is an integer from 0 to 8190 representing the number of the first M-variable;
the second {constant} is an integer from 1 to 8191 representing the number M-variables whose
value is to be set;
the third {constant} is an integer from 1 to 8191 representing the numerical spacing between each
M-variable whose value is to be set;
the final {constant} contains the value to be given to the specified set of M-variables
This command assigns the value on the right side of the equals sign to the specified M-variables. It does
not assign a definition (address) to the M-variables; that is done with the M{constant}-
>{definition} command.
If a motion or PLC program buffer is open when the single-variable form of this command is sent to
Turbo PMAC, the command will be entered into the buffer for later execution. If a motion or PLC
program buffer is open when the multiple-variable form of this command is sent, Turbo PMAC will reject
the command with an error, reporting ERR003 if I6 is 1 or 3.
Example:
M1=1
M9=M9 & $20
M102=-16384
M1..8=0
M1,16,2=1 ; Sets M1, M3, M5 … , M31 to 1
See Also:
M-Variables (Computational Features)
On-line commands M{constant}, M{constant}->{definition}
Program commands M{data}, M{data}={expression}
M{constant}->
Function: Report current M-variable definitions
Scope: Global
Syntax: M{constant}[..{constant}]->
where:
{constant} is an integer from 0 to 8191 representing the number of the M-variable;
the optional second{constant} must be at least as great as the first {constant} -- it represents
the number of the end of the range;
This command causes Turbo PMAC to report the definition (address) of the specified M-variable or range
of M-variables. It does not cause Turbo PMAC to report the value of the M-variables; that is done with
the M{constant} command.
When I9 is 0 or 2, only the definition itself (e.g. Y:$078802,0) is returned. When I9 is 1or 3, the entire
definition statement (e.g. M11->Y:$078802,0) is returned.
Example:
M1-> ; Host requests definition
Y:$FFC2,8 ; Turbo PMAC's response
M101..103->
X:$C001,24,S
Y:$C003,8,16,S
X:$C003,24,S
See Also:
M-Variables (Computational Features)
On-line commands M{constant}, M{constant}->{definition},
M{constant}={expression}
Program command M{constant}={expression}
M{constant}->*
Function: Self-Referenced M-Variable Definition
Scope: Global
Syntax: M{constant}[..{constant}]->*
where:
{constant} is an integer from 0 to 8191 representing the number of the M-variable;
the optional second{constant} must be at least as great as the first {constant} -- it represents
the number of the end of the range.
This command causes Turbo PMAC to reference the specified M-variable or range of M-variables to its
own definition word. To use an M-variable as a flag, status bit, counter, or other simple variable, there is
no need to find an open area of memory, because it is possible to use some of the definition space to hold
the value. Simply define this form of the M-variable and this M-variable can be used much as a P-
variable would be, except it only takes integer values in the range -235 to 235-1. Note, however, that the
use of these self-referenced M-variables is less efficient for computation than using P or Q-variables.
When the definition is made, the value is set automatically to 0.
This command is also useful to erase an existing M-variable definition.
Example:
M100->*
M20..39->*
M0..8191->*. ; This erases all existing M-variable definitions
; It is a good idea to use this before loading new ones
See Also:
M-Variables (Computational Features)
Example:
M150->DP:$052000
M250->DP$052001
See Also:
M-Variables (Computational Features)
Dual-Ported RAM (Writing a Host Communications Program)
On-line commands M{constant}, M{constant}->,
.......... M{constant}->F:{address}, M{constant}={expression}
Program command M{constant}={expression}
M{constant}->F:{address}
Function: Dual-Ported RAM Floating-Point M-Variable Definition
Scope: Global
Syntax: M{constant}[..{constant}]->F[:]{address}
where:
{constant} is an integer from 0 to 8191 representing the number of the M-variable;
the optional second{constant} must be at least as great as the first {constant} -- it represents
the number of the end of the range;
{address} is an integer constant from $000000 to $FFFFFF (0 to 16,777,215 if specified in
decimal).
This command causes Turbo PMAC to define the specified M-variable or range of M-variables to point to
32 bits of data in the low 16 bits of both X and Y memory at the specified location in Turbo PMAC’s
address space. The data is interpreted as a floating-point value with the IEEE single-precision (32-bit)
format.
The definition consists of the letter F, an optional colon (:), and the word address.
This format is mainly useful only for dual-ported RAM locations $050000 to $05FFFF (Option 2
required). With this format, the host can read or write to the corresponding location with the standard
IEEE 32-bit floating-point data format.
The IEEE 32-bit floating point format has the sign bit in bit 31 (MSB); the biased exponent in bits 30 to
23 (the exponent is this value minus 127), and the fraction in bits 22 to 0 (there is an implied 1 added to
the fraction in the mantissa). The words are arranged in the standard Intel format.
Example:
M155->F:$054001
M255->F$05402
See Also:
M-Variables (Computational Features)
Dual-Ported RAM (Writing a Host Communications Program)
On-line commands M{constant}, M{constant}->,
.......... M{constant}->DP:{address}, M{constant}={expression}
Program command M{constant}={expression}
M{constant}->L:{address}
Function: Long Word Floating-Point M-Variable Definition
Scope: Global
Syntax: M{constant}[..{constant}]->L[:]{address}
where:
{constant} is an integer from 0 to 8191 representing the number of the M-variable;
the optional second{constant} must be at least as great as the first {constant} -- it represents
the number of the end of the range;
{address} is an integer constant from $000000 to $FFFFFF (0 to 16,777,215 if specified in
decimal).
This command causes Turbo PMAC to define the specified M-variable or range of M-variables to point to
a long word (48 bits) of data – both X and Y memory – at the specified location in Turbo PMAC's address
space. The data is interpreted as a floating-point value with Turbo PMAC’s own 48-bit floating-point
format.
The definition consists of the letter L, an optional colon (:), and the word address.
Memory locations for which this format is useful are labeled with 'L:' in the memory map.
Example:
M5147->L:$002047
M5148->L$02048
M5148->L8264
See Also:
M-Variables (Computational Features)
On-line commands M{constant}, M{constant}->,
.......... M{constant}->D:{address}, M{constant}={expression}
Program command M{constant}={expression}
M{constant}->TWB:{address}
Function: Binary Thumbwheel-Multiplexer Definition
Scope: Global
Syntax: M{constant}[..{constant}]->TWB[:]{multiplex address},
{offset},{size},{format}
where:
{constant} is an integer from 0 to 8191 representing the number of the M-variable;
the optional second{constant} must be at least as great as the first {constant} -- it represents
the number of the end of the range;
{multiplex address} is an integer constant in the range 0 to 255, representing the byte address
in the multiplexing scheme on the thumbwheel port of the least significant bit to be used in the M-
variables;
{offset} is an integer constant from 0 to 7, representing which bit of this byte is the least
significant bit to be used in the M-variable;
{size} is an integer constant from 1 to 32, representing the number of consecutive bits to be used in
the M-variables;
{format} (optional) is either U for unsigned, or S for signed (two's complement). If no format is
specified, U (unsigned) is assumed.
This command causes Turbo PMAC to define the specified M-variable or range of M-variables to a
consecutive of input bits multiplexed on the thumbwheel port with Accessory 18 or compatible hardware,
including the Advantage 500 NC control panel.
Example:
M0->TWB:0,0,1
M1->TWB:0,1,1
M10->TWB:3,4,4,U
M745->TWB:4,0,16,S
M872->TWB:0,4,1
See Also:
M-Variables (Computational Features)
On-line commands M{constant}, M{constant}->,
M{constant}->TWD:{address}
Thumbwheel Multiplexer Board (Acc-18) Manual
M{constant}->TWD:{address}
Function: BCD Thumbwheel-Multiplexer M-Variable Definition
Scope: Global
Syntax: M{constant}[..{constant}]->TWD[:]{multiplex address},
{offset},{size}[.{dp}],{format}
where:
{constant} is an integer from 0 to 8191 representing the number of the M-variable;
the optional second{constant} must be at least as great as the first {constant} -- it represents
the number of the end of the range;
{multiplex address} is an integer constant in the range 0 to 255, representing the address in
the multiplexing scheme on the thumbwheel port of the most significant digit (lowest address) to be
used in the M-variables;
{offset} is 0 or 4, representing whether the most significant digit is in the low nibble (left digit of
pair) or high nibble (right digit of pair) of the pair of digits at {multiplex address},
respectively;
{size} is an integer constant from 1 to 12, representing the number of digits to be used in the M-
variables;
{dp} (optional) is an integer constant from 0 to 8, representing the number of these digits to be
interpreted as being to the right of the decimal point;
{format} (optional) is either U for unsigned, or S for signed. If it is signed, the least significant
bit of the most significant digit is taken as the sign bit (the rest of the most significant digit is
ignored). If no format is specified, U (unsigned) is assumed.
This command causes Turbo PMAC to define the specified M-variable or range of M-variables to point to
a set of binary-coded-decimal digits multiplexed on the thumbwheel port with Accessory 18 or
compatible hardware.
Thumbwheel-multiplexer M-variables are read-only, floating-point variables. Once defined, they are to
be used in expressions, and queried. Each time one is used in an expression, the proper addresses on the
multiplexer boards are read.
Example:
M100->TWD:4,0,8.3,U means the most significant digit is at multiplex address 4, low nibble (left
digit); there are eight digits, three of which are fractional; and it is always interpreted as a positive value.
This corresponds to eight thumbwheel digits along the bottom row of the lowest-addressed thumbwheel
board, with the decimal point three digits in from the right.
M99->TWD:0,0,1,U means that a single digit is used, at multiplex address 0, low nibble (left digit).
This corresponds to the upper left thumbwheel on the lowest-addressed thumbwheel board.
See Also:
M-Variables (Computational Features)
On-line commands M{constant}, M{constant}->,
.......... M{constant}->TWB:{address}
Thumbwheel Multiplexer Board (Acc-18) Manual
M{constant}->TWR:{address}
Function: Resolver Thumbwheel-Multiplexer M-Variable Definition
Scope: Global
Syntax: M{constant}[..{constant}]->TWR[:]{multiplex address},
{offset}
where:
{constant} is an integer from 0 to 8191 representing the number of the M-variable;
the optional second {constant} must be at least as great as the first {constant} -- it represents
the number of the end of the range;
{multiplex address} is an integer constant, divisible by 2, in the range 0 to 254, representing
the address in the multiplexing scheme of the Acc-8D Option 7 resolver-to-digital converter board on
the thumbwheel multiplexer port, as determined by the DIP switch settings on the board
{offset} is an integer constant from 0 to 7, representing the location of the device at the specified
multiplexer address, as determined by in the buffer on the Acc-8D Option 7 and the actual pins to
which the device was wired.
This command causes Turbo PMAC to define the specified M-variable or range of M-variables to point to
a 12-bit word from a resolver-to-digital (R/D) converter or similar device serially multiplexed on the
thumbwheel port on an Acc-8D Option 7 or compatible board.
The address on the multiplex port specified here must match the address set by the DIP switches on board
the Acc-8D Option 7. The Acc-8D Option 7 manual contains a table listing all of the possibilities.
One of the DIP switches on the Acc-8D Option 7 board determines whether the R/D converters on board
have offset values of 0 to 3 or 4 to 7. The {offset} specifier must match this DIP switch setting and
the number of the R/D device on the board.
This is a read-only M-variable format. Use of this variable in an on-line query command or a program
statement will cause Turbo PMAC to clock in 12 bits of unsigned data (range 0 to 4095) from the
specified device through the multiplexer port.
Note:
It is not necessary to use an M-variable to access an R/D converter for actual servo
or phasing feedback purposes. I-variables (Ixx10, Ixx81, Ixx98, Ixx99) are used
for that purpose. However, even if this is the only use of the R/D converter,
usually it is desirable to assign M-variables to the R/D converters for set-up and
diagnostic purposes.
Example:
M100->TWR:0,0
M99->TWR:4,5
See Also:
M-Variables (Computational Features)
On-line commands M{constant}, M{constant}->,
M{constant}->TWS:{address}
Resolver-to-Digital Converter Board (Acc-8D Opt-7) Manual
M{constant}->TWS:{address}
Function: Serial Thumbwheel-Multiplexer M-Variable Definition
Scope: Global
Syntax: M{constant}[..{constant}]->TWS[:]{multiplex address}
where:
{constant} is an integer from 0 to 8191 representing the number of the M-variable;
the optional second{constant} must be at least as great as the first {constant} – it represents
the number of the end of the range;
{multiplex address} is an integer constant, divisible by 4, in the range 0 to 124, representing
the address in the multiplexing scheme of the first of four bytes in the 32-bit input or output word.
Adding 1 to the {multiplex address} designates it as a read-only variable and adding 2
designates it as a write-only variable.
This command causes Turbo PMAC to define the specified M-variable or range of M-variables to point to
a 32-bit word of input or output serially multiplexed on the thumbwheel port on an Accessory 34x board.
Note:
The individual bits of the thumbwheel port on an Acc-34x board cannot be directly
assigned to an M-variable. Only 32-bit words (ports) of input or output can be
accessed.
The base address of the Acc-34x on the multiplexer port is set by a DIP switch bank on the board. The
base address can take a value from 0 to 248, evenly divisible by 8.
The address of the 32-bit input port on the Acc-34x board is equal to the base address plus 1. (If the base
address is 16, the address of the input port is 17.)
The address of the 32-bit output port on the Acc-34x board is equal to the base address plus 6. (If the
base address is 32, the address of the output port is 38.)
The address of the optional supplemental input port available on some Acc-34x boards is equal to the
base address plus 3. (If the base address is 128, the address of the supplemental input port is 131.)
The address on the multiplex port specified here must match the address set by the DIP switch on board
the Acc-34x. The Acc-34x manual contains a table listing all of the possibilities.
Because the individual bits of the thumbwheel port cannot be accessed directly on an Accessory 34x
board and because of the relatively long time it takes to clock the data in or out of Turbo PMAC (A 32-bit
Read or a 32-bit Write to an individual port takes approximately 16 microseconds of time in the Turbo
PMAC's background time slot), it is best to keep an image of each M-variable of this type in internal
memory. The image variable would preferably be a 32-bit or 48-bit fixed point M-variable, but it could
also be a 48-bit floating point P or Q variable.
The best procedure for using TWS M-variables in a program is as follows. The input word (TWS M-
variable) should be copied into its image variable at the beginning of a sequence of operations. The
operations can then be done on the image variable without requiring Turbo PMAC to actually read or
write to the I/O port for each operation. The output word is first assembled into its image variable, then
copied to the actual output word once at the end of a sequence of operations. This procedure will allow
the most efficient and flexible use of TWS M-variables.
Note:
This type of variable can only be used in background tasks (on-line commands,
plus PLCs and PLCCs 1-31). They cannot be used in foreground tasks (motion
programs and PLC and PLCC 0).
Example:
For an Acc-34x board with base address 0 on the multiplexer port (all DIP switches ON): the the M-
variable for the input port would be:
M80->TWS:1 ;Input port at {base+1}
The definition for the output port would be:
M81->TWS:6 ;Output port at {base+6}
See Also:
M-Variables (Computational Features)
On-line commands M{constant}, M{constant}->,
M{constant}->TWR:{address}
Serial I/O Multiplexer Board (Acc-34x) Manuals
M{constant}->X/Y:{address}
Function: Short Word M-Variable Definition
Scope: Global
Syntax: M{constant}[..{constant}]->
X[:]{address},{offset}[,{width}[,{format}]]
M{constant}[..{constant}]->
Y[:]{address},{offset}[,{width}[,{format}]]
where:
{constant} is an integer from 0 to 8191 representing the number of the M-variable;
the optional second{constant} must be at least as great as the first {constant} -- it represents
the number of the end of the range;
{address} is an integer constant from $000000 to $FFFFFF (0 to 16,777,215 if specified in
decimal).
{offset} is an integer constant from 0 to 23, representing the starting (least significant) bit of the
word to be used in the M-variables, or 24 to specify the use of all 24 bits;
{width} (optional) is an integer constant from the set {1, 4, 8, 12, 16, 20, 24}, representing the
number of bits from the word to be used in the M-variables; if {width} is not specified, a value of 1
is assumed;
{format} (optional) is a letter from the set [U, S, D, C], specifying how Turbo PMAC is to
interpret this value: (U=Unsigned integer, S=Signed integer, D=Binary-coded Decimal,
C=Complementary binary-coded decimal); if {format} is not specified, U is assumed.
This command causes Turbo PMAC to define the specified M-variable or range of M-variables to point to
a location in one of the two halves (X or Y) of Turbo PMAC’s data memory. In this form, the variable
can have a width of 1 to 24 bits and can be decoded several different ways, so the bit offset, bit width, and
decoding format must be specified (the bit width and decoding format do have defaults.
The definition consists of the letter X or Y, an optional colon (:), the word address, the starting bit
number (offset), an optional bit width number, and an option format-specifying letter.
Legal values for bit width and bit offset are inter-related. The table below shows the possible values of
{width}, and the corresponding legal values of {offset} for each setting of {width}.
{width} {offset}
1 0 -- 23
4 0,4,8,12,16,20
8 0,4,8,12,16
12 0,4,8,12
16 0,4,8
20 0,4
24 0
The format is irrelevant for 1-bit M-variables, and should not be included for them. If no format is
specified, U is assumed.
Examples:
Machine Output 1
M1->Y:$078802,8,1 ; 1-bit (full spec.)
M1->Y$078802,8 ; 1-bit (short spec.)
Encoder 1 Capture/Compare Register
M103->X:$078003,0,24,U ; 24-bit (full spec.)
M103->X$078003,24 ; 24-bit (short spec.)
DAC 1 Output Register
M102->Y:$078003,8,16,S ; 16-bit value
M102->Y491523,8,16,S ; same, decimal address
See Also:
M-Variables (Computational Features)
On-line commands M{constant}, M{constant}->,
.......... M{constant}->D:{address}, M{constant}={expression}
Program command M{constant}={expression}
MACROASCII{master #} [replaced]
Function: Set port in MACRO pass-through mode
Scope: Global (MACRO Ring Master only)
Syntax: MACROASCII{master #}
Note:
This command has been replaced starting in V1.936 firmware by the
MACROMSTASCII command.
This command causes Turbo PMAC to write the specified constant value to the specified variable of the
Turbo PMAC acting as a MACRO slave station matching the specified node number on the Turbo
PMAC.
Only one auxiliary access (read or write) of a single node can be done on one command line.
If the slave node returns an error message or the slave node does not respond within the number of servo
cycles set by I78, Turbo PMAC will report ERR008. Bit 5 of global status register X:$000006 is set to
report such a MACRO auxiliary communications error. Register X:$00320E holds the error value. It is set
to $010000 for a timeout error, or $xxxxFE if the slave node reports an error, where xxxx is the 16-bit
error code reported by the slave node.
MACROAUX{node #},{param #}={constant}
Function: Set MACRO Type 0 auxiliary parameter value in slave node
Scope: Global
Syntax: MACROAUX{node #},{param #}={constant}
MX{node #},{param #}={constant}
where:
{node #} is a constant in the range 0 to 63 representing the number of the node on the Turbo
PMAC matching the slave node to be accessed, where the node number specification is:
{node #} = 0 – 15 specifies MACRO IC 0 nodes 0 – 15, which correspond to slave nodes 0 –
15 of the same master number as MACRO IC 0;
{node #} = 16 – 31 specifies MACRO IC 1 (Ultralites with Option 1A only) nodes 0 – 15,
which correspond to slave nodes 0 – 15 of the same master number as MACRO IC 1;
{node #} = 32 – 47 specifies MACRO IC 2 (Ultralites with Option 1B only) nodes 0 – 15,
which correspond to slave nodes 0 – 15 of the same master number as MACRO IC 2;
{node #} = 48 – 63 specifies MACRO IC 3 (Ultralites with Option 1C only) nodes 0 – 15,
which correspond to slave nodes 0 – 15 of the same master number as MACRO IC 3;
{param #} is an integer constant from 0 to 65535 specifying the auxiliary parameter number for
this node (2 to 253 required for a write operation)
{constant} is an integer constant from -32768 to +32767 representing the value to be written to
the specified parameter
This command causes Turbo PMAC to write the specified constant value to the variable of the MACRO
slave station at the specified node number using the MACRO Type 0 master-to-slave auxiliary protocol.
Only one auxiliary access (read or write) of a single node can be done on one command line.
The auxiliary register function for the specified node number must have been enabled by setting the
appropriate bit of I70, I72, I74, or I76 to 1. The Type 0 protocol for this node must have been selected by
setting the appropriate bit of I71, I73, I75, or I77 to 0.
If the slave node returns an error message or the slave node does not respond within 32 servo cycles,
Turbo PMAC will report ERR008. Bit 5 of global status register X:$000006 is set to report such a
MACRO auxiliary communications error. Register X:$0031EE holds the error value. It is set to $010000
for a timeout error, or $xxxxFE if the slave node reports an error, where xxxx is the 16-bit error code
reported by the slave node.
Note:
Delta Tau MACRO Station products use the Type 1 protocol, and so do not use
this command.
Example:
MACROAUX1,24=2000 ; Set Node 1 Parameter 24 to 2000
See Also:
On-line commands MACROAUXREAD, MACROAUXWRITE
PLC Program commands MACROAUXREAD, MACROAUXWRITE
MACROAUXREAD
Function: Read (copy) variable value from Turbo PMAC MACRO slave
Scope: Global
Syntax: MACROAUXREAD{node #},M{slave var},{variable}
MXR{node #},M{slave var},{variable}
where:
{node #} is a constant in the range 0 to 63 representing the number of the node on the Turbo
PMAC matching the slave node to be accessed, where the node number specification is:
o {node #} = 0 – 15 specifies MACRO IC 0 nodes 0 – 15, which correspond to slave
nodes 0 – 15 of the same master number as MACRO IC 0;
o {node #} = 16 – 31 specifies MACRO IC 1 nodes 0 – 15, which correspond to slave
nodes 0 – 15 of the same master number as MACRO IC 1;
o {node #} = 32 – 47 specifies MACRO IC 2 nodes 0 – 15, which correspond to slave
nodes 0 – 15 of the same master number as MACRO IC 2;
o {node #} = 48 – 63 specifies MACRO IC 3 nodes 0 – 15, which correspond to slave
nodes 0 – 15 of the same master number as MACRO IC 3;
{slave var} is the name of the variable of the Turbo PMAC acting as a MACRO slave to this
Turbo PMAC. It can be an I, P, Q, or M-variable with a number from 0 to 8191.
{variable} is the name of the variable on this Turbo PMAC. It can be an I, P, Q, or M-
variable with a number from 0 to 4095.
This command causes Turbo PMAC to copy the value of the specified variable of the Turbo PMAC
acting as a MACRO slave station matching the specified node number on the Turbo PMAC to the
specified variable on this Turbo PMAC.
If the slave node returns an error message or the slave node does not respond within the number of servo
cycles set by I78, Turbo PMAC will report ERR008. Bit 5 of global status register X:$000006 is set to
report such a MACRO auxiliary communications error. Register X:$00320E holds the error value. It is set
to $010000 for a timeout error, or $xxxxFE if the slave node reports an error, where xxxx is the 16-bit
error code reported by the slave node.
If this command is issued to a Turbo PMAC when a program buffer is open, it will be entered as a
program line into that buffer.
Examples:
MXR0,MP8191,P10 ; Copy slave P8191 into P10 here
MXR1,MM162,P4095 ; Copy slave MM162 into P4095
MACROAUXWRITE
Function: Write (copy) variable value to Turbo PMAC MACRO slave
Scope: Global
Syntax: MACROAUXWRITE{node #},M{slave var},{variable}
MXW{node #},M{slave var},{variable}
where:
{node #} is a constant in the range 0 to 63 representing the number of the node on the Turbo
PMAC matching the slave node to be accessed, where the node number specification is:
o {node #} = 0 – 15 specifies MACRO IC 0 nodes 0 – 15, which correspond to slave
nodes 0 – 15 of the same master number as MACRO IC 0;
o {node #} = 16 – 31 specifies MACRO IC 1 nodes 0 – 15, which correspond to slave
nodes 0 – 15 of the same master number as MACRO IC 1;
o {node #} = 32 – 47 specifies MACRO IC 2 nodes 0 – 15, which correspond to slave
nodes 0 – 15 of the same master number as MACRO IC 2;
o {node #} = 48 – 63 specifies MACRO IC 3 nodes 0 – 15, which correspond to slave
nodes 0 – 15 of the same master number as MACRO IC 3;
{slave var} is the name of the variable of the Turbo PMAC acting as a MACRO slave to this
Turbo PMAC. It can be an I, P, Q, or M-variable with a number from 0 to 8191.
{variable} is the name of the variable on this Turbo PMAC. . It can be an I, P, Q, or M-
variable with a number from 0 to 4095.
This command causes Turbo PMAC to copy the value of the specified variable on this Turbo PMAC to
the specified variable of the Turbo PMAC acting as a MACRO slave station matching the specified node
number.
If the slave node returns an error message or the slave node does not respond within the number of servo
cycles set by I78, Turbo PMAC will report ERR008. Bit 5 of global status register X:$000006 is set to
report such a MACRO auxiliary communications error. Register X:$00320E holds the error value. It is set
to $010000 for a timeout error, or $xxxxFE if the slave node reports an error, where xxxx is the 16-bit
error code reported by the slave node.
If this command is issued to a Turbo PMAC when no buffer is open, it will be executed as an on-line
command.
Examples:
MXW0,MP8191,P10 ; Copy P10 value here into slave P8191
MXW1,MM162,P4095 ; Copy P4095 value here into slave MM162
MACROMST{master#},{master variable}
Function: Report Type 1 MACRO master variable value
Scope: Global
Syntax: MACROMST{master #},{master variable}
MM{node #},{master variable}
where:
{master #} is a constant (1-15) representing the number of the remote master whose variable is to
be read;
{master variable} is the name of the variable on the remote master station whose value is to
be reported
This command causes the Turbo PMAC to query another master station on the ring for a variable value
using the MACRO Type 1 master-to-master auxiliary communications protocol, and report back the value
of the specified variable to the host computer.
In order for the Turbo PMAC to be able to execute this command, the following conditions must be true:
MACRO IC 0 on this Turbo PMAC must be set up as the synchronizing ring master (I6840 = $xx30);
MACRO IC 0 on this Turbo PMAC must be set up as Master 0 on the ring (I6841 = $0xxxxx);
MACRO IC 0 node 14 must be in broadcast mode (I6840 bit 14 = 1);
MACRO IC 0 node 14 auxiliary register copy function must be disabled (I70 bit 14 = 0);
MACROMST{master#},{master variable}={constant}
Function: Set Type 1 MACRO master auxiliary parameter value
Scope: Global
Syntax: MACROMST{master #},{master variable}={constant}
MM{node #},{master variable}={constant}
where:
{master #} is a constant (1-15) representing the number of the remote master whose variable is to
be read;
{master variable} is the name of the variable on the remote master station whose value is to
be set
{constant} is a number representing the value to be written to the specified variable on the remote
master station
This command causes the Turbo PMAC to set a variable value on another master station on the ring using
the MACRO Type 1 master-to-master auxiliary communications protocol.
In order for the Turbo PMAC to be able to execute this command, the following conditions must be true:
MACRO IC 0 on this Turbo PMAC must be set up as the synchronizing ring master (I6840 = $xx30);
MACRO IC 0 on this Turbo PMAC must be set up as Master 0 on the ring (I6841 = $0xxxxx);
MACRO IC 0 node 14 must be in broadcast mode (I6840 bit 14 = 1);
MACRO IC 0 node 14 auxiliary register copy function must be disabled (I70 bit 14 = 0);
MACRO IC 0 node 14 must not be used for any other function.
In order for another Turbo PMAC to be able to respond to the communications that this command creates
on the MACRO ring (to be the remote master), the following conditions must be true:
MACRO IC 0 on the Turbo PMAC must be set up as a master, but not the synchronizing ring master
(I6840 = $xx90);
MACRO IC 0 on the Turbo PMAC must be set up with a non-zero master number on the ring (I6841
= $nxxxxx, where n > 0);
MACROMSTASCII{master #}
Function: Set port in MACRO pass-through mode
Scope: Global (MACRO Ring Master only)
Syntax: MACROMSTASCII{master #}
MACMA{master #}
where:
{master #} is a constant in the range 1 to 15 representing the master number of the Turbo PMAC
to whom the communications will be passed
This command causes Turbo PMAC to put the port on which it receives this command in a MACRO
master-to-master pass-through mode. In this mode, commands received over this port are not acted on by
this Turbo PMAC. Instead, they are passed on over the MACRO ring to the Turbo PMAC with the
specified master number. Responses are received from the other Turbo PMAC over the MACRO ring
and passed back to the host computer over this port.
This mode of communications, which uses the Type 1 auxiliary communications protocol, requires
V1.936 or newer firmware on all Turbo PMACs on the ring. It permits the host computer to
communicate with remote Turbo PMACs as if they were directly connected to the host. Non-Turbo
PMACs on the ring will not respond to commands passed over the ring in this protocol.
If used to set up broadcast to multiple masters on the ring (MACROMSTACII0), no handshaking between
boards is possible on broadcast commands. In this mode, it is strongly suggested that only commands of
6 ASCII characters or less (including the terminating <CR> character) be used. This mode is intended
mainly to start or stop programs together on multiple cards.
This command can only be given to a Turbo PMAC that is the synchronizing ring master (ring controller)
set up for Type 1 auxiliary communications with Node 14 in broadcast mode. This requires that:
I79 > 0 (enable master-to-master, recommended I79 = 32)
I6840 = $4030 (ring controller with Node 14 in broadcast mode)*
I6841 bit 14 set to 1 (enable Node 14 communications)*
These values be saved, and the card reset, before this mode can be enabled
* These I-variables are used if MACRO IC 0 is used for this communications, the most common
configuration. If MACRO IC 1 is used, I6890 and I6891 must take these values; for MACRO IC 2, I6940
and I6941; for MACRO IC 3, I6990 and I6991.
On this Turbo PMAC, the commands will be sent out over the MACRO ring through the MACRO IC (0 –
3) whose number is specified by I84. The base address of MACRO IC n is specified by variable I2n.
Only one communications port of this ring controller Turbo PMAC may be in pass-through mode at any
time. The other ports are not in pass-through mode and may be used simultaneously for communications
with the ring controller Turbo PMAC itself.
Turbo PMACs on the ring to which these commands are passed through must be set as masters but not
ring controllers, with Node 14 enabled but not in broadcast mode. On these boards:
I6840 = $10 (master, but not ring controller; Node 14 not in broadcast mode)
I6841 bit 14 = 1 (Node 14 enabled)
These values be saved, and the card reset, before this mode can be enabled.
This port is taken out of MACRO pass-through mode if it is given the <CTRL-T> command. To change
which other master to which the commands are passed through, first take the port out of pass-through
mode with a <CTRL-T>, then enable the pass-through to another master. If another MACROMSTASCII
command is sent while the port is in pass-through mode, this command will be passed through and
rejected by the other master, returning an ERR008.
In pass-through mode, command errors are always reported in the form <BELL>ERRnnn<CR>,
regardless of the setting of I6.
See Also:
On-line commands <CTRL-T>, MACROSTASCII{station #}
MACROMSTREAD
Function: Read (copy) Type 1 MACRO master auxiliary parameter value
Scope: Global
Syntax: MACROMSTREAD{master #},{master variable},
{ring-master variable}
MMR{master #},{master variable},{ring-master variable}
where:
{master #} is a constant (1-15) representing the number of the remote master whose variable is to
be read;
{master variable} is the name of the variable on the remote master station whose value is to
be reported
{ring-master variable} is the name of the variable on the Turbo PMAC executing the
command into which the value of the remote master variable is to be copied
This command causes Turbo PMAC to copy the value of the specified variable on the remote master
station into the specified variable on the Turbo PMAC executing the command, using the MACRO Type
1 master-to-master auxiliary protocol.
In order for the Turbo PMAC to be able to execute this command, the following conditions must be true:
MACRO IC 0 on this Turbo PMAC must be set up as the synchronizing ring master (I6840 = $xx30);
MACRO IC 0 on this Turbo PMAC must be set up as Master 0 on the ring (I6841 = $0xxxxx);
MACRO IC 0 node 14 must be in broadcast mode (I6840 bit 14 = 1);
MACRO IC 0 node 14 auxiliary register copy function must be disabled (I70 bit 14 = 0);
MACRO IC 0 node 14 must not be used for any other function.
In order for another Turbo PMAC to be able to respond to the communications that this command creates
on the MACRO ring (to be the remote master), the following conditions must be true:
MACRO IC 0 on the Turbo PMAC must be set up as a master, but not the synchronizing ring master
(I6840 = $xx90);
MACRO IC 0 on the Turbo PMAC must be set up with a non-zero master number on the ring (I6841
= $nxxxxx, where n > 0);
MACRO IC 0 node 14 must normally be disabled (I6841 bit 14 = 0);
MACRO IC 0 node 14 must be in “broadcast mode” (I6840 bit 14 = 1);
MACRO IC 0 node 14 auxiliary register copy function must be disabled (I70 bit 14 = 0);
MACRO IC 0 node 14 must not be used for any other function.
If the remote master returns an error message or it does not respond within I79 servo cycles, Turbo
PMAC will report ERR008. Bit 5 of global status register X:$000006 is set to report such a MACRO
auxiliary communications error. Register X:$0031EE holds the error value. It is set to $010000 for a
timeout error, or $xxxxFE if the slave node reports an error, where xxxx is the 16-bit error code reported
by the slave node.
If this command is issued to a Turbo PMAC while a PLC buffer is open, it will be stored in the buffer as a
PLC command, not executed as an on-line command.
Examples:
MMR4,I10,P10 ; Copies value of remote master 4 variable I10 into Turbo PMAC variable P10
MMR1,P1,P1 ; Copies value of remote master 1 variable P1 into Turbo PMAC variable P1
MACROMSTWRITE
Function: Write (copy) Type 1 MACRO master auxiliary parameter value
Scope: Global
Syntax: MACROMSTWRITE{master #},{master variable},
{ring-master variable}
MMW{master #},{master variable},{ring-master variable}
where:
{master #} is a constant (1-15) representing the number of the remote master whose variable is to
be read;
{master variable} is the name of the variable on the remote master station whose value is to
be set;
{ring-master variable} is the name of the variable on the Turbo PMAC executing the
command from which the value of the remote master variable is to be copied.
This command causes Turbo PMAC to copy the value of the specified variable on the remote master
station from the specified variable on the Turbo PMAC executing the command, using the MACRO Type
1 master-to-master auxiliary protocol.
In order for the Turbo PMAC to be able to execute this command, the following conditions must be true:
MACRO IC 0 on this Turbo PMAC must be set up as the synchronizing ring master (I6840 = $xx30);
MACRO IC 0 on this Turbo PMAC must be set up as Master 0 on the ring (I6841 = $0xxxxx);
MACRO IC 0 node 14 must be in broadcast mode (I6840 bit 14 = 1);
MACRO IC 0 node 14 auxiliary register copy function must be disabled (I70 bit 14 = 0);
MACRO IC 0 node 14 must not be used for any other function.
In order for another Turbo PMAC to be able to respond to the communications that this command creates
on the MACRO ring (to be the remote master) the following conditions must be true:
MACRO IC 0 on the Turbo PMAC must be set up as a master, but not the synchronizing ring master
(I6480 = $xx90);
MACRO IC 0 on the Turbo PMAC must be set up with a non-zero master number on the ring (I6841
= $nxxxxx, where n > 0);
MACRO IC 0 node 14 must normally be disabled (I6841 bit 14 = 0);
MACRO IC 0 node 14 must be in broadcast mode (I6840 bit 14 = 1);
MACRO IC 0 node 14 auxiliary register copy function must be disabled (I70 bit 14 = 0);
MACRO IC 0 node 14 must not be used for any other function.
If the remote master returns an error message or it does not respond within I79 servo cycles, Turbo
PMAC will report ERR008. Bit 5 of global status register X:$000006 is set to report such a MACRO
auxiliary communications error. Register X:$0031EE holds the error value. It is set to $010000 for a
timeout error, or $xxxxFE if the slave node reports an error, where xxxx is the 16-bit error code reported
by the slave node.
If this command is issued to a Turbo PMAC while a PLC buffer is open, it will be stored in the buffer as a
PLC command, not executed as an on-line command.
Examples:
MMW4,I10,P10 ; Copies value of Turbo PMAC variable P10 into remote master 4 variable I10
MMW1,P1,P1 ; Copies value of Turbo PMAC variable P1 into remote master 1 variable P1
MACROSLV{command} {node#}
Function: Send command to Type 1 MACRO slave
Scope: Global
Syntax: MACROSLAVE{command}{node #}
MS{command}{node #}
where:
{command} is one of the following text strings:
$$$ normal station reset
$$$*** station reset and re-initialize
CLRF station fault clear for
CONFIG report station configuration value
DATE report station firmware date
SAVE save station setup
VER report station firmware version
{node #} is a constant in the range 0 to 63 representing the number of the node on the Turbo
PMAC matching the slave node to be accessed, where the node number specification is:
{node #} = 0 – 15 specifies MACRO IC 0 nodes 0 – 15, which correspond to slave nodes 0 –
15 of the same master number as MACRO IC 0;
{node #} = 16 – 31 specifies MACRO IC 1 (Ultralites with Option 1A only) nodes 0 – 15,
which correspond to slave nodes 0 – 15 of the same master number as MACRO IC 1;
{node #} = 32 – 47 specifies MACRO IC 2 (Ultralites with Option 1B only) nodes 0 – 15,
which correspond to slave nodes 0 – 15 of the same master number as MACRO IC 2;
{node #} = 48 – 63 specifies MACRO IC 3 (Ultralites with Option 1C only) nodes 0 – 15,
which correspond to slave nodes 0 – 15 of the same master number as MACRO IC 3;
This command causes Turbo PMAC to issue the specified command to a MACRO slave station using the
Type 1 auxiliary master-to-slave protocol. {node #} can be the number of any active node on the slave
station. If {node #} is set to the highest node number for the MACRO IC (15, 31, 47, or 63), the action
automatically applies to all slave stations commanded from that MACRO IC.
The MS CONFIG command allows the user to set and report a user-specified configuration value. This
provides any easy way for the user to see if the MACRO station has already been configured to the user’s
specifications.
The factory default configuration value is 0. It is recommended that after the user finishes the software
configuration of the station, a special number be given to the configuration value with the MS
CONFIG{node #}={constant} command. This number will be saved to the non-volatile memory
with the MS SAVE command.
Subsequently, when the system is powered up, the station can be polled with the MS CONFIG {node
#} command. If the expected value is returned, the station can be assumed to have the proper software
setup. If the expected value is not returned (for instance, when a replacement station has just been
installed) then the setup will have to be transmitted to the station.
In order for the Turbo PMAC to be able to execute this command, the following conditions must be true:
The MACRO IC used must be set up as a master or the synchronizing ring master
(I6840/6890/6940/6990 = $xx90 or $xx30);
MACRO IC 0 node 15 auxiliary register copy function must be disabled (I70 bit 15 = 0);
MACRO IC 0 node 15 must not be used for any other function.
If the slave node returns an error message or it does not respond within I78 servo cycles, Turbo PMAC
will report ERR008. Bit 5 of global status register X:$000006 is set to report such a MACRO auxiliary
communications error. Register X:$0031EE holds the error value. It is set to $010000 for a timeout
error, or $xxxxFE if the slave node reports an error, where xxxx is the 16-bit error code reported by the
slave node.
Examples:
MS $$$0 ; Resets MACRO station which has active node 0
MS $$$***4 ; Reinitializes MACRO station which has active node 4
MS CLRF8 ; Clears fault on Node 8 of MACRO station
MS CONFIG12 ; Causes MACRO station to report its configuration #
37 ; PMAC reports MACRO station configuration # to host
MS CONFIG12=37 ; Sets MACRO station configuration number
MS DATE 0 ; Causes MACRO station to report its firmware date
03/27/97 ; PMAC reports MACRO station firmware date to host
MS SAVE 4 ; Causes MACRO station to save setup variables
MS VER 8 ; Causes MACRO station to report its firmware version
1.104 ; PMAC reports MACRO station firmware version to host
MACROSLV{node#},{slave variable}
Function: Report Type 1 MACRO auxiliary parameter value
Scope: Global
Syntax: MACROSLAVE{node #},{slave variable}
MS{node #},{slave variable}
where:
{node #} is a constant in the range 0 to 63 representing the number of the node on the Turbo
PMAC matching the slave node to be accessed, where the node number specification is:
{node #} = 0 – 15 specifies MACRO IC 0 nodes 0 – 15, which correspond to slave nodes 0 –
15 of the same master number as MACRO IC 0;
{node #} = 16 – 31 specifies MACRO IC 1 (Ultralites with Option 1A only) nodes 0 – 15,
which correspond to slave nodes 0 – 15 of the same master number as MACRO IC 1;
{node #} = 32 – 47 specifies MACRO IC 2 (Ultralites with Option 1B only) nodes 0 – 15,
which correspond to slave nodes 0 – 15 of the same master number as MACRO IC 2;
{node #} = 48 – 63 specifies MACRO IC 3 (Ultralites with Option 1C only) nodes 0 – 15,
which correspond to slave nodes 0 – 15 of the same master number as MACRO IC 3;
{slave variable} is the name of the variable on the slave station whose value is to be reported
This command causes Turbo PMAC to query the MACRO slave station at the specified node number
using the MACRO Type 1 master-to-slave auxiliary protocol, and report back the value of the specified
slave station variable to the host computer. If the variable is not node-specific, {node #} can represent
the number of any active node on the slave station.
In order for the Turbo PMAC to be able to execute this command, the following conditions must be true:
The MACRO IC used must be set up as a master or the synchronizing ring master
(I6840/6890/6940/6990 = $xx90 or $xx30);
MACRO IC 0 node 15 auxiliary register copy function must be disabled (I70 bit 15 = 0);
MACRO IC 0 node 15 must not be used for any other function.
If the slave node returns an error message or it does not respond within I78 servo cycles, Turbo PMAC
will report ERR008. Bit 5 of global status register X:$000006 is set to report such a MACRO auxiliary
communications error. Register X:$0031EE holds the error value. It is set to $010000 for a timeout
error, or $xxxxFE if the slave node reports an error, where xxxx is the 16-bit error code reported by the
slave node.
Examples:
MS0,MI910 ; Causes slave to report value of Node 0 variable MI910
7 ; PMAC reports this value back to host
MS1,MI997 ; Causes slave to report value global variable MI997
6258 ; PMAC reports this value back to host
MACROSLV{node#},{slave variable}={constant}
Function: Set Type 1 MACRO auxiliary parameter value
Scope: Global
Syntax: MACROSLAVE{node #},{slave variable}={constant}
MS{node #},{slave variable}={constant}
where:
{node #} is a constant in the range 0 to 63 representing the number of the node on the Turbo
PMAC matching the slave node to be accessed, where the node number specification is:
{node #} = 0 – 15 specifies MACRO IC 0 nodes 0 – 15, which correspond to slave nodes 0 –
15 of the same master number as MACRO IC 0;
{node #} = 16 – 31 specifies MACRO IC 1 (Ultralites with Option 1A only) nodes 0 – 15,
which correspond to slave nodes 0 – 15 of the same master number as MACRO IC 1;
{node #} = 32 – 47 specifies MACRO IC 2 (Ultralites with Option 1B only) nodes 0 – 15,
which correspond to slave nodes 0 – 15 of the same master number as MACRO IC 2;
{node #} = 48 – 63 specifies MACRO IC 3 (Ultralites with Option 1C only) nodes 0 – 15,
which correspond to slave nodes 0 – 15 of the same master number as MACRO IC 3;
{slave variable} is the name of the MI-variable or C-command on the slave station whose
value is to be set;
{constant} is a number representing the value to be written to the specified MI-variable
This command causes Turbo PMAC to write the specified constant value to the variable of the MACRO
slave station at the specified node number using the MACRO Type 1 master-to-slave auxiliary protocol.
If the variable is not node-specific, {node #} can represent the number of any active node on the slave
station.
In order for the Turbo PMAC to be able to execute this command, the following conditions must be true:
The MACRO IC used must be set up as a master or the synchronizing ring master
(I6840/6890/6940/6990 = $xx90 or $xx30);
MACRO IC 0 node 15 auxiliary register copy function must be disabled (I70 bit 15 = 0);
MACRO IC 0 node 15 must not be used for any other function.
If the slave node returns an error message or it does not respond within I78 servo cycles, Turbo PMAC
will report ERR008. Bit 5 of global status register X:$000006 is set to report such a MACRO auxiliary
communications error. Register X:$0031EE holds the error value. It is set to $010000 for a timeout
error, or $xxxxFE if the slave node reports an error, where xxxx is the 16-bit error code reported by the
slave node.
Examples:
MS0,MI910=7 ; Causes slave to set value of Node 0 variable MI910 to 7
MS1,MI997=6528 ; Causes slave to set value global variable MI997 to 6528
MS8,C2=0 ; Causes slave at node 8 to reset
MACROSLVREAD
Function: Read (copy) Type 1 MACRO auxiliary parameter value
Scope: Global
Syntax: MACROSLVREAD{node #},{slave variable},{PMAC variable}
MSR{node #},{slave variable},{PMAC variable}
where:
{node #} is a constant in the range 0 to 63 representing the number of the node on the Turbo
PMAC matching the slave node to be accessed, where the node number specification is:
{node #} = 0 – 15 specifies MACRO IC 0 nodes 0 – 15, which correspond to slave nodes 0 –
15 of the same master number as MACRO IC 0;
{node #} = 16 – 31 specifies MACRO IC 1 (Ultralites with Option 1A only) nodes 0 – 15,
which correspond to slave nodes 0 – 15 of the same master number as MACRO IC 1;
{node #} = 32 – 47 specifies MACRO IC 2 (Ultralites with Option 1B only) nodes 0 – 15,
which correspond to slave nodes 0 – 15 of the same master number as MACRO IC 2;
{node #} = 48 – 63 specifies MACRO IC 3 (Ultralites with Option 1C only) nodes 0 – 15,
which correspond to slave nodes 0 – 15 of the same master number as MACRO IC 3;
{slave variable} is the name of the variable on the slave station whose value is to be reported
{PMAC variable} is the name of the variable on the Turbo PMAC into which the value of the
slave station variable is to be copied
This command causes Turbo PMAC to copy the value of the specified variable of the MACRO slave
station matching the specified node number on the Turbo PMAC to the specified Turbo PMAC variable,
using the MACRO Type 1 master-to-slave auxiliary protocol. If the slave station variable is not node-
specific, {node #} can represent the number of any active node on the slave station.
The variable on the Turbo PMAC can be any of the I, P, Q, or M-variable on the card.
If this command is issued to the Turbo PMAC while a PLC buffer is open, it will be stored in the buffer
as a PLC command, not executed as an on-line command.
In order for the Turbo PMAC to be able to execute this command, the following conditions must be true:
The MACRO IC used must be set up as a master or the synchronizing ring master
(I6840/6890/6940/6990 = $xx90 or $xx30);
MACRO IC 0 node 15 auxiliary register copy function must be disabled (I70 bit 15 = 0);
MACRO IC 0 node 15 must not be used for any other function.
If the slave node returns an error message or it does not respond within I78 servo cycles, Turbo PMAC
will report ERR008. Bit 5 of global status register X:$000006 is set to report such a MACRO auxiliary
communications error. Register X:$0031EE holds the error value. It is set to $010000 for a timeout
error, or $xxxxFE if the slave node reports an error, where xxxx is the 16-bit error code reported by the
slave node.
Examples:
MSR0,MI910,P1 ; Copies value of slave Node 0 variable MI910 into PMAC variable P1
MSR1,MI997,M10 ; Copies value of slave Node 1 variable MI997 into PMAC variable M10
MACROSLVWRITE
Function: Write (copy) Type 1 MACRO auxiliary parameter value
Scope: Global
Syntax: MACROSLVWRITE{node #},{slave variable},{PMAC variable}
MSW{node #},{slave variable},{PMAC variable}
where:
{node #} is a constant in the range 0 to 63 representing the number of the node on the Turbo
PMAC matching the slave node to be accessed, where the node number specification is:
{node #} = 0 – 15 specifies MACRO IC 0 nodes 0 – 15, which correspond to slave nodes 0 –
15 of the same master number as MACRO IC 0;
{node #} = 16 – 31 specifies MACRO IC 1 (Ultralites with Option 1A only) nodes 0 – 15,
which correspond to slave nodes 0 – 15 of the same master number as MACRO IC 1;
{node #} = 32 – 47 specifies MACRO IC 2 (Ultralites with Option 1B only) nodes 0 – 15,
which correspond to slave nodes 0 – 15 of the same master number as MACRO IC 2;
{node #} = 48 – 63 specifies MACRO IC 3 (Ultralites with Option 1C only) nodes 0 – 15,
which correspond to slave nodes 0 – 15 of the same master number as MACRO IC 3;
{slave variable} is the name of the MI-variable or C-command on the slave station whose
value is to be set;
{PMAC variable} is the name of the variable on the PMAC from which the value of the slave
station variable is to be copied
This command causes Turbo PMAC to copy the value of the specified variable on Turbo PMAC to the
specified variable of the MACRO slave station matching the specified node number on the Turbo PMAC,
using the MACRO Type 1 master-to-slave auxiliary protocol. If the slave station variable is not node-
specific, {node #} can represent the number of any active node on the slave station.
The variable on the Turbo PMAC can be any of the I, P, Q, or M-variables on the card.
If this command is issued to the Turbo PMAC while a PLC buffer is open, it will be stored in the buffer
as a PLC command, not executed as an on-line command.
In order for the Turbo PMAC to be able to execute this command, the following conditions must be true:
The MACRO IC used must be set up as a master or the synchronizing ring master
(I6840/6890/6940/6990 = $xx90 or $xx30);
MACRO IC 0 node 15 auxiliary register copy function must be disabled (I70 bit 15 = 0);
MACRO IC 0 node 15 must not be used for any other function.
If the slave node returns an error message or it does not respond within I78 servo cycles, Turbo PMAC
will report ERR008. Bit 5 of global status register X:$000006 is set to report such a MACRO auxiliary
communications error. Register X:$0031EE holds the error value. It is set to $010000 for a timeout
error, or $xxxxFE if the slave node reports an error, where xxxx is the 16-bit error code reported by the
slave node.
Examples:
MSW0,MI910,P35 ; Copies value of PMAC P35 into MACRO station node 0 variable MI910
MSW4,C4,P0 ; Causes MACRO station with active node 4 to execute Command #4, saving its
; setup variable values to non-volatile memory (P0 is a dummy variable here)
MACROSTASCII {station #}
Function: Set port in MACRO pass-through mode
Scope: Global (MACRO Ring Master only)
Syntax: MACROSTASCII{master #}
MACSTA{master #}
where:
{station #} is a constant in the range 0 to 255 representing the order number of the station on the
ring to whom the communications will be passed. If a 0 is used, subsequent commands will be
broadcast to all masters on the ring. If a 255 is used, subsequent commands will be sent to the next
unordered (station number 0) station on the ring.
This command causes Turbo PMAC to put the port on which it receives this command in a MACRO
master-to-station pass-through mode. In this mode, commands received over this port are not acted on by
this Turbo PMAC. Instead, they are passed on over the MACRO ring to the master or slave station on the
ring with the specified station-order number. Responses are received from the other station over the
MACRO ring and passed back to the host computer over this port.
The main purpose of this mode of communications is to be able to go around the MACRO ring, station by
station, and communicate with each station, even if the normal ring addressing is not set up, not set up
properly, or unknown to the system. This mode of communications, which uses the Type 1 auxiliary
communications protocol, requires V1.936 or newer firmware on all Turbo PMACs on the ring, and
V1.1114 or newer firmware on all MACRO Stations on the ring. Non-Turbo PMACs on the ring will not
respond to commands passed over the ring in this protocol.
A MACROSTASCII255 command will set up communications with the first unordered station (station
order number of 0) on the ring. Query commands can detect information about this station, then a station
order number assigned to this station with the STN={constant} or I85={constant} command.
(Typically, ring-order numbers are given sequentially to stations along the ring, but this is not required.)
Once a station order number is assigned to a station, it will no longer respond to commands given in
MACROSTASCII255 mode, and the next unordered (STN=0) station will respond to these commands
instead.
A MACROSTASCII0 command will broadcast subsequent commands to all stations on the ring. In this
mode, a STN=0 or I85=0 command will unorder all stations on the ring so that they can be isolated one
by one using the above technique. In this mode, no handshaking between boards is possible on broadcast
commands. In this mode, it is strongly suggested that only commands of 6 ASCII characters or less
(including the terminating <CR> character) be used. This mode is intended mainly to re-initialize the
ordering on the ring.
This command can only be given to a Turbo PMAC that is the synchronizing ring master (ring controller)
set up for Type 1 auxiliary communications with Node 14 in broadcast mode. This requires that:
I79 > 0 (enable master-to-master, recommended I79 = 32)
I6840 = $4030 (ring controller with Node 14 in broadcast mode)*
I6841 bit 14 set to 1 (enable Node 14 communications)*
These values be saved, and the card reset, before this mode can be enabled
* These I-variables are used if MACRO IC 0 is used for this communications, the most common
configuration. If MACRO IC 1 is used, I6890 and I6891 must take these values; for MACRO IC 2, I6940
and I6941; for MACRO IC 3, I6990 and I6991.
On this Turbo PMAC, the commands will be sent out over the MACRO ring through the MACRO IC (0 –
3) whose number is specified by I84. The base address of MACRO IC n is specified by variable I2n.
Only one communications port of this ring controller Turbo PMAC may be in “pass-through” mode at
any time. The other ports are not in pass-through mode and may be used simultaneously for
communications with the ring controller Turbo PMAC itself.
This port is taken out of MACRO pass-through mode if it is given the <CTRL-T> command. If another
MACROSTASCII command is sent while the port is in pass-through mode, this command will be passed
through and rejected by the other station, returning an ERR008.
In pass-through mode, command errors are always reported in the form <BELL>ERRnnn<CR>,
regardless of the setting of I6.
See Also:
On-line commands <CTRL-T>, MACROMSTASCII{station #}
MACROSTASCIIFREQ
Function: Report value of variable controlling MACRO ring frequency
Scope: Global
Syntax: MACROSTASCIIFREQ
MACSTAFREQ
This command, when sent to the Turbo PMAC that is the MACRO ring controller, causes it to report the
value of the variable that is controlling the MACRO ring frequency. Usually this variable is I6800. The
ring frequency is inversely proportional to the setting of this value. Refer to the description of I6800 for
details.
MACROSTASCIIFREQ={constant}
Function: Set value of variable controlling MACRO ring frequency
Scope: Global
Syntax: MACROSTASCIIFREQ={constant}
MACSTAFREQ={constant}
This command, when sent to the Turbo PMAC that is the MACRO ring controller, causes it to set the
value of the variable that is controlling the MACRO ring frequency, both on itself, and on all devices on
the MACRO ring, to the specified value. The ring frequency is inversely proportional to the setting of this
value. Refer to the description of I6800 for details.
MACROSTASCIIFREQ=*
Function: Set value of variable controlling MACRO ring frequency to default
Scope: Global
Syntax: MACROSTASCIIFREQ=*
MACSTAFREQ=*
This command, when sent to the Turbo PMAC that is the MACRO ring controller, causes it to set the
value of the variable that is controlling the MACRO ring frequency, both on itself, and on all devices on
the MACRO ring, to the default value of 6527, which sets a 9.03 kHz “MaxPhase” frequency. The ring
frequency is inversely proportional to the setting of this value. Refer to the description of I6800 for
details.
MFLUSH
Function: Clear pending synchronous M-variable assignments
Scope: Coordinate-system specific
Syntax: MFLUSH
This command permits the user to clear synchronous M-variable assignment commands that have been
put on the stack for intended execution with a subsequent move (without executing the commands). As
an on-line command, it is useful for making sure pending outputs are not executed after a program has
been stopped.
Examples:
Q ; Stop execution of a program
MFLUSH ; Clear M-variable stack
B1R ; Start another program; formerly pending M-variables will not execute
See Also:
Program commands M{data}=={expression},
M{data}&={expression},
M{data}|={expression},
M{data}^={expression}
MOVETIME
Function: Report time left in presently executing move
Scope: Coordinate-system specific
Syntax: MOVETIME
MVTM
The MOVETIME command causes Turbo PMAC to report the time left in the currently executing
commanded move in the addressed coordinate system, scaled in milliseconds (at 100%). If variable Isx14
for the addressed coordinate system is set to a non-zero value, the value of Isx14 is subtracted from this
value calculated for response, the difference is converted to servo cycles, and this result is written to the
Isx11 automatic countdown timer. This additional functionality facilitates anticipating the end of the
commanded move.
This “time remaining” function is not active if the addressed coordinate system is executing moves in the
special lookahead buffer.
NOFRAX
Function: Remove all axes from list of vector feedrate axes
Scope: Coordinate-system specific
Syntax: NOFRAX
This command causes Turbo PMAC to remove all axes from the list of vector feedrate axes for the
addressed coordinate system. In this mode, any feedrate-specified move in the coordinate system will
yield a vector distance of 0, forcing the use of the Isx86 alternate feedrate. This can be useful to create a
“dry run” of a motion program, overriding the feedrates specified in the motion-program F commands.
Axes can be restored to the vector feedrate list with the FRAX command.
See Also:
I-variables Isx86, Isx89, Isx90, Isx98
On-line command FRAX
Program commands F, FRAX, NOFRAX
NORMAL
Function: Report circle-plane unit normal vector
Scope: Coordinate system specific
Syntax: NORMAL
NRM
This command causes Turbo PMAC to report the unit normal vector for the addressed coordinate system.
This normal vector defines the plane for circular interpolation and cutter radius compensation.
Turbo PMAC reports the vector by displaying its I, J, and K components, parallel to the X, Y, and Z axes,
respectively. If a component is zero, it will not be reported. The vector sum of the components is 1.0
because this is a vector of unit magnitude.
The default normal vector is K-1.0, which specifies the XY plane. This can be modified by the motion
program NORMAL I{data} J{data} K{data} statement. Note that the vector magnitude of the
commanded normal vector does not need to be equal to 1.0 – Turbo PMAC will store a scaled version of
it.
Syntax:
NORMAL
K-1
NORMAL
I0.7071 J0.7071
O{constant}
Function: Open loop output
Scope: Motor specific
Syntax: O{constant}
where:
{constant} is a floating-point value representing the magnitude of the output as a percentage of
Ixx69 for the motor, with a range of +/-100
This command causes Turbo PMAC to put the motor in open-loop mode and force an output of the
specified magnitude, expressed as a percentage of the maximum output parameter for the motor (Ixx69).
This command is commonly used for set-up and diagnostic purposes (for instance, a positive O command
must cause position to count in the positive direction, or closed-loop control cannot be established), but it
can also be used in actual applications.
If the motor is not Turbo PMAC-commutated, this command will create a DC output voltage on the
single DAC for the motor. If the motor is commutated by Turbo PMAC, the commutation algorithm is
still active, and the specified magnitude of output is apportioned between the two DAC outputs or the
three PWM outputs for the motor according to the instantaneous commutation phase angle.
If the value specified is outside the range +/-100, the output will saturate at +/-100% of Ixx69.
Closed-loop control for the motor can be re-established with the J/ command. It is a good idea to stop
the motor first with an O0 command if it has been moving in open-loop mode.
To do a variable O-command, define an M-variable to the filter result register (X:$0000AE, etc.,
suggested M-variable Mxx79), command an O0 to the motor to put it in open-loop mode, then assign a
variable value to the M-variable. This technique will even work on Turbo PMAC-commutated motors.
Turbo PMAC will reject this command if the motor is in a coordinate system that is currently running a
motion program (reporting ERR001 if I6 is 1 or 3).
Example:
O50 ; Open-loop output 50% of Ixx69 for addressed motor
#2O33.333 ; Open-loop output 1/3 of Ixx69 for Motor 2
O0 ; Open-loop output of zero magnitude
J/ ; Re-establish closed-loop control
See Also:
On-line commands J/, K
Memory-map registers X:$0000BF, X:$00013F, etc.
Suggested M-variable definitions Mxx68.
OPEN BINARY ROTARY
Function: Open all existing rotary buffers for binary DPRAM entry
Scope: Port specific
Syntax: OPEN BINARY ROTARY
OPEN BIN ROT
This command causes Turbo PMAC to open all existing rotary motion program buffers for entry of
binary-formatted program lines through the DPRAM.
In order to be able to send binary-formatted program lines to a coordinate system’s rotary buffer, three
steps must first have been performed:
1. Room must have been reserved for the coordinate system’s rotary buffer in internal PMAC memory
since the last power-up/reset with the DEFINE ROTARY command.
2. Room must have been reserved for data transfer for the coordinate system in the DPRAM by setting
up pointers in the DPRAM (usually done by PCOMM32 subroutines).
3. The buffers must have been enabled for entry with the OPEN BIN ROT command.
No other program buffers (PLC, fixed motion program, or rotary buffers with ASCII input) may be open
when this command is sent (Turbo PMAC will report ERR007 if I6 = 1 or 3). It is a good idea always to
preced an OPEN command with a CLOSE command to make sure no other buffers have been left open.
The actual downloading of binary-formatted program lines is almost always done with PCOMM32
software routines.
ASCII text commands sent through any port to the Turbo PMAC while the binary rotary program buffers
are open are treated as on-line commands. ASCII text commands sent at this time that can only be
interpreted as buffered program commands will be rejected (Turbo PMAC will report ERR005 if I6 is 1
or 3).
The CLOSE command issued on this same port will close all open binary rotary buffers.
This function is controlled by variable I57 on non-Turbo PMACs.
OPEN FORWARD
Function: Open a forward-kinematic program buffer for entry
Scope: Port, coordinate-system specific
Syntax: OPEN FORWARD
OPEN FWD
This command causes Turbo PMAC to open the forward-kinematic program buffer for the addressed
coordinate system for entry or editing through this port. Subsequent program commands valid for these
programs sent from this port will be entered into this buffer. Kinematic programs can accept all
commands that are valid for PLC programs except ADDRESS, CMD, and SEND commands. When entry
of the program is finished, the CLOSE command should be used to prevent further lines from being put in
this buffer.
If the kinematic-enable variable Isx50 for the coordinate system is set to 1, Turbo PMAC will
automatically execute the forward-kinematic program for the coordinate system any time an R (run), S
(step), or PMATCH command is given to the coordinate system. Before running the program PMAC will
place the commanded position value (in counts) for each Motor xx in the coordinate system into global
variable Pxx.
After the program is run, Turbo PMAC will take the values in Q1 – Q9 for the coordinate system and use
them as the starting positions for the A, B, C, U, V, W, X, Y, and Z axes, respectively (in engineering
units).
No other program buffers (PLC, fixed or rotary motion) may be open when this command is sent (Turbo
PMAC will report ERR007 if I6=1 or 3). It is a good idea always to precede an OPEN command with a
CLOSE command to make sure no other buffers have been left open.
No motion programs may be running in any coordinate system when this command is sent (Turbo PMAC
will report ERR001 if I6=1 or 3). As long as a forward kinematic program buffer is open, no motion
program may be run in any coordinate system (Turbo PMAC will report ERR015 if I6=1 or 3).
Forward kinematic programs can be protected by password. If there is a password for the Turbo PMAC,
and the password has not been given, Turbo PMAC will reject this command (reporting an ERR002 if I6
is 1 or 3).
See Also:
Kinematic Calculations
I-variable Isx50
On-line commands LIST FORWARD, LIST INVERSE, OPEN INVERSE
OPEN INVERSE
Function: Open an inverse-kinematic program buffer for entry
Scope: Port, coordinate-system specific
Syntax: OPEN INVERSE
OPEN INV
This command causes Turbo PMAC to open the inverse-kinematic program buffer for the addressed
coordinate system for entry or editing through this port. Subsequent program commands valid for these
programs sent on this port will be entered into this buffer. Kinematic programs can accept all commands
that are valid for PLC programs except ADDRESS, CMD, and SEND commands. When entry of the
program is finished, the CLOSE command should be used to prevent further lines from being put in this
buffer.
If the kinematic-enable variable Isx50 for the coordinate system is set to 1, Turbo PMAC will
automatically execute the inverse-kinematic program for the coordinate system any time axis positions
are calculated during motion program execution. This is either the end of the programmed move for non-
segmented moves, or the end of each move segment for segmented LINEAR and CIRCLE-mode moves
with Isx13 greater than 0.
Before each instance of running the inverse-kinematic program, Turbo PMAC will automatically place
the commanded position values (in engineering units) for the A, B, C, U, V, W, X, Y, and Z axes into Q1
– Q9, respectively, for the coordinate system. After the program is run, for each Motor xx in the
coordinate system whose axis definition statement is #xx->I, Turbo PMAC automatically places the
value of Pxx into the target position register for the motor. If executing a PVT-mode move, Turbo PMAC
will also place the commanded velocity value (in engineering units) for the axes into Q11 – Q19 before,
and place the value of P1xx into the motor target velocity register after.
No other program buffers (PLC, fixed or rotary motion) may be open when this command is sent (Turbo
PMAC will report ERR007 if I6=1 or 3). It is a good idea always to precede an OPEN command with a
CLOSE command to make sure no other buffers have been left open.
No motion programs may be running in any coordinate system when this command is sent (Turbo PMAC
will report ERR001 if I6=1 or 3). As long as a forward kinematic program buffer is open, no motion
program may be run in any coordinate system (Turbo PMAC will report ERR015 if I6=1 or 3).
Inverse kinematic programs can be protected by password. If there is a password for the Turbo PMAC,
and the password has not been given, Turbo PMAC will reject this command (reporting an ERR002 if I6
is 1 or 3).
See Also:
Kinematic Calculations
I-variable Isx50
On-line commands LIST FORWARD, LIST INVERSE, OPEN FORWARD
OPEN PLC
Function: Open a PLC program buffer for entry
Scope: Port specific
Syntax: OPEN PLC {constant}
where:
{constant} is an integer from 0 to 31 representing the PLC program to be opened
This command causes Turbo PMAC to open the specified PLC program buffer for entry and editing on
this port. This permits subsequent program lines that are valid for a PLC to be entered into this buffer
from this port only. When entry of the program is finished, the CLOSE command should be sent on this
port to prevent further lines from being put in the buffer.
No other program buffers (PLC, fixed or rotary motion) may be open when this command is sent (Turbo
PMAC will report ERR007 if I6=1 or 3). It is a good idea always to precede an OPEN command with a
CLOSE or CLOSE ALL command to make sure no other buffers have been left open.
PLCs 0-15 can be protected by password. If the PLC is protected by password, and the proper password
has not been given, Turbo PMAC will reject this command (reporting an ERR002 if I6=1 or 3).
Opening a PLC program buffer automatically disables that PLC program. Other PLC programs and
motion programs will keep executing. Closing the PLC program buffer after entry does not re-enable the
program. To re-enable the program, the ENABLE PLC command must be used, or Turbo PMAC must be
reset (with a saved value of I5 permitting this PLC program to execute).
Example:
CLOSE ; Make sure other buffers are closed
DELETE GATHER ; Make sure memory is free
OPEN PLC 7 ; Open buffer for entry, disabling program
CLEAR ; Erase existing contents
IF (M11=1) ; Enter new version of program...
CLOSE ; Close buffer at end of program
ENABLE PLC 7 ; Re-enable program
See Also:
PLC Program Features
I-variable I5
On-line commands CLOSE, DELETE GATHER, ENABLE PLC
OPEN PROGRAM
Function: Open a fixed motion program buffer for entry
Scope: Port specific
Syntax: OPEN PROGRAM {constant}
OPEN PROG {constant}
where:
{constant} is an integer from 1 to 32767 representing the motion program to be opened
This command causes Turbo PMAC to open the specified fixed (non-rotary) motion program buffer for
entry or editing on this port. Subsequent program commands valid for motion programs sent from this
port will be entered into this buffer. When entry of the program is finished, the CLOSE or CLOSE ALL
command should be used to prevent further lines from being put in the buffer.
No other program buffers (PLC, fixed or rotary motion) may be open when this command is sent (Turbo
PMAC will report ERR007 if I6=1 or 3). It is a good idea always to precede an OPEN command with a
CLOSE command to make sure no other buffers have been left open.
No motion programs may be running in any coordinate system when this command is sent (Turbo PMAC
will report ERR001 if I6=1 or 3). As long as a fixed motion program buffer is open, no motion program
may be run in any coordinate system (Turbo PMAC will report ERR015 if I6=1 or 3).
PROGs 1000-32767 can be protected by password. If the PROG is protected by password, and the proper
password has not been given, Turbo PMAC will reject this command (reporting an ERR002 if I6=1 or 3).
After any fixed motion program buffer has been opened, each coordinate system must be commanded to
point to a motion program with the B{constant} command before it can run a motion command
(otherwise Turbo PMAC will report ERR015 if I6=1 or 3)
Example:
CLOSE ; Make sure other buffers are closed
DELETE GATHER ; Make sure memory is free
OPEN PROG 255 ; Open buffer for entry, disabling program
CLEAR ; Erase existing contents
X10 Y20 F5 ; Enter new version of program...
...
CLOSE ; Close buffer at end of program
&1B255R ; Point to this program and run it
See Also:
Writing and Executing Motion Programs
On-line commands CLEAR, CLOSE, DELETE GATHER
Program Command Specification
OPEN ROTARY
Function: Open all existing rotary motion program buffers for text entry
Scope: Port specific
Syntax: OPEN ROTARY
OPEN ROT
This command causes Turbo PMAC to open all existing rotary motion program buffers (created with the
DEFINE ROTARY command) for entry with ASCII text program lines from this port. Subsequent
program commands valid for rotary motion programs sent on this port are entered into the rotary program
buffer of the coordinate system addressed at the time of that command.
No other program buffers (PLC, or fixed motion programs) may be open when this command is sent
(Turbo PMAC will report ERR007 if I6=1 or 3). It is a good idea always to precede an OPEN command
with a CLOSE or CLOSE ALL command to make sure no other buffers have been left open.
Note:
The B0 command that points the coordinate system to the rotary buffer cannot be
given while the rotary buffers are open, because Turbo PMAC will interpret the
command as a B-axis move command.
Example:
&2 DEFINE ROT 100 ; Create C.S. 2 rotary buffer
&1 DEFINE ROT 100 ; Create C.S. 1 rotary buffer
&1 B0 &2 B0 ; Point both C.S.s to rotary buffers
OPEN ROT ; Open buffers for entry
&1 X10 Y10 F5 ; Write to C.S. 1's buffer
&2 X30 Y30 F10 ; Write to C.S. 2's buffer
&1R &2R ; Start executing both buffers
See Also:
Rotary Motion Programs (Writing and Executing Motion Programs)
On-line commands CLOSE, DEFINE ROT, B{constant}, R
P
Function: Report motor position
Scope: Motor specific
Syntax: P
This command causes Turbo PMAC to report the present actual position for the addressed motor to the
host as a decimal ASCII string, scaled in counts, rounded to the nearest 1/32 of a count.
Turbo PMAC reports the value of the actual position register plus the position bias register plus the
compensation correction register, and if bit 1 of Ixx06 is 1 (handwheel offset mode), minus the master
position register.
Example:
P ; Request the position of the addressed motor
1995 ; Turbo PMAC responds
#1P ; Request position of Motor 1
-0.5 ; Turbo PMAC responds
#3P ; Request position of Motor 3
2.03125 ; Turbo PMAC responds
#2P#4P ; Request positions of Motors 2 and 4
9998 ; Turbo PMAC responds with Motor 2 position first
10002 ; Turbo PMAC responds with Motor 4 position next
See Also:
On-line commands <CTRL-P>, F, V
Suggested M-variable definitions Mxx62, Mxx64, Mxx67, Mxx69
P{constant}
Function: Report the current P-variable values.
Scope: Global
Syntax: P{constant}[..{constant}]
where:
{constant} is an integer from 0 to 8191 representing the number of the P-variable;
the optional second{constant} must be at least as great as the first {constant} – it represents
the number of the end of the range;
P{constant},{constant},{constant}
where:
the first {constant} is an integer from 0 to 8190 representing the number of the first P-variable;
the second {constant} is an integer from 1 to 8191 representing the number P-variables whose
value is to be reported;
the third {constant} is an integer from 1 to 8191 representing the numerical spacing between each
P-variable whose value is to be reported;
This command causes Turbo PMAC to report the current value of the specified P-variable, or range or set
of P-variables.
Example:
P1 ; Host asks for value
25 ; Turbo PMAC responds
P1005
3.444444444
P100..102
17.5
-373
0.0005
P100,3,100 ; Request for value of P100, P200, P300
33.7
92.13
8.05
See Also:
P-Variables (Computational Features)
On-line commands I{constant}, M{constant}, Q{constant}, P{data}={expression}
P{data}={expression}
Function: Assign a value to a P-variable.
Scope: Global
Syntax: P{data}={expression}
where:
{data} is a constant, or an expression in parentheses, for an integer value from 0 to 8191
representing the P-variable number;
{expression} contains the value to be given to the specified P-variable
P{constant}..{constant}={constant}
where:
the first {constant} is an integer from 0 to 8190 representing the number of the first P-variable;
the second {constant} is an integer from 1 to 8191 representing the number of the last P-variable;
it must be at least as great as the first {constant}
the final {constant} contains the value to be given to the specified range of P-variables
P{constant},{constant},{constant}={constant}
where:
the first {constant} is an integer from 0 to 8190 representing the number of the first P-variable;
the second {constant} is an integer from 1 to 8191 representing the number P-variables whose
value is to be set;
the third {constant} is an integer from 1 to 8191 representing the numerical spacing between each
P-variable whose value is to be set;
the final {constant} contains the value to be given to the specified set of P-variables
This command causes Turbo PMAC to set the specified P-variable or range of P-variables equal to the
value on the right side of the equals sign.
If a motion or PLC program buffer is open when the single-variable form of this command is sent to
Turbo PMAC, the command will be entered into the buffer for later execution. If a motion or PLC
program buffer is open when the multiple-variable form of this command is sent, Turbo PMAC will reject
the command with an error, reporting ERR003 if I6 is 1 or 3.
Example:
P1=1
P75=P32+P10
P100..199=0
P10=$2000
P832=SIN(3.14159*Q10)
P(10*Q5)=72
P101,16,100=50 ; Set P101, P201, P301, … P1601 to 50
See Also:
P-Variables (Computational Features)
On-line commands I{data}={expression}, M{data}={expression},
Q{data}={expression}, P{constant}
Program command P{data}={expression}
PASSWORD={string}
Function: Enter/Set Program Password
Scope: Global
Syntax: PASSWORD={string}
where:
{string} is a series of non-control ASCII characters (values from 32 decimal to 255 decimal).
The password string is case sensitive.
This command permits the user to enter the card’s password, or once entered properly, to change it.
Without a properly entered password, Turbo PMAC will not open or list the contents of any motion
program numbered 1000 or greater, or of PLC programs 0-15. If asked to do so, it will return an error
(ERR002 reported if I6 is set to 1 or 3).
The default password is the null password (which means no password is needed to list the programs).
This is how the card is shipped from the factory, and also after a $$$*** re-initialization command.
When there is a null password, it is automatically considered that the correct password has been entered
on power-up/reset.
If the correct password has been entered (which is always the case for the null password), Turbo PMAC
interprets the PASSWORD={string} command as changing the password, and it can be changed to
anything else. When the password is changed, it has been matched automatically and the host computer
has access to the protected programs.
Note:
The password does not require quote marks. If using quote marks when the
password string is entered for the first time, use them every time this password
string is matched.
If the correct password has not been entered since the latest power-up/reset, Turbo PMAC interprets the
PASSWORD={string} command as an attempt to match the existing password. If the command
matches the existing password correctly, Turbo PMAC accepts it as a valid command, and the host
computer has access to the protected programs until the Turbo PMAC is reset or has its power cycled.
If the command does not match the existing password correctly, Turbo PMAC returns an error (reporting
ERR002 if I6=1 or 3), and the host computer does not have access to the protected programs. The host
computer is free to attempt to match the existing password.
There is no way to read the current password. If the password is forgotten and access to the protected
programs is required, the card must be re-initialized with the $$$*** command, which clears all program
buffers as well as the password. Then the programs must be reloaded, and a new password entered.
Example:
{Starting from power-up/reset with a null password}
LIST PLC 1 ; Request listing of protected program
P1=P1+1 ; PMAC responds because there is no password
RETURN
PASSWORD=Bush ; This sets the password to "Bush"
LIST PLC 1 ; Request listing of protected program
P1=P1+1 ; PMAC responds because password has been
RETURN ; matched by changing it.
$$$ ; Reset the card
LIST PLC 1 ; Request listing of protected program
ERR002 ; PMAC rejects because password not entered
PASSWORD=Reagan ; Attempt to enter password
ERR002 ; PMAC rejects as incorrect password
PASSWORD=BUSH ; Attempt to enter password
ERR002 ; PMAC rejects as incorrect (wrong case)
PASSWORD=Bush ; Attempt to enter password; PMAC accepts as correct password
LIST PLC 1 ; Request listing of protected program
P1=P1+1 ; PMAC responds because password matched
RETURN
PASSWORD=Clinton ; This changes password to Clinton
LIST PLC 1 ; Request listing of protected program
P1=P1+1 ; PMAC responds because password has been
RETURN ; matched by changing it.
$$$ ; Reset the card
PASSWORD=Clinton ; Attempt to enter password
; PMAC accepts as correct password
LIST PLC 1 ; Request listing of protected program
P1=P1+1 ; PMAC responds because password matched
RETURN
See Also:
On-line commands LIST, LIST PC, LIST PE, OPEN
PAUSE PLC
Function: Pause specified PLC programs.
Scope: Global
Syntax: PAUSE PLC {constant}[,{constant}...]
PAU PLC {constant}[,{constant}...]
PAUSE PLC {constant}[..{constant}]
PLC {constant}[..{constant}]
where:
{constant} is an integer from 0 to 31, representing the program number
This command causes Turbo PMAC to stop execution of the specified uncompiled PLC program or
programs, with the capability to restart execution at this point (not necessarily at the top) with a RESUME
PLC command. Execution can also be restarted at the top of the program with the ENABLE PLC
command.
The on-line PAUSE PLC command can only suspend execution of a PLC program at the end of a scan,
which is either the end of the program, or at an ENDWHILE statement in the program.
PLC programs are specified by number, and may be specified in a command singularly, in a list
(separated by commas), or in a range of consecutively numbered programs.
If a motion or PLC program buffer is open when this command is sent to Turbo PMAC, the command
will be entered into that buffer for later execution.
Example:
PAUSE PLC 1
PAU PLC 5
PAU PLC 3,4,7
PAUSE PLC 0..31
See Also:
I-variable I5
On-line commands DISABLE PLC, ENABLE PLC, OPEN PLC, RESUME PLC, LIST PLC,
<CONTROL-D>.
Program commands DISABLE PLC, ENABLE PLC, PAUSE PLC, RESUME PLC
PC
Function: Report Program Counter
Scope: Coordinate-system specific
Syntax: PC
This command causes Turbo PMAC to report the motion program number and address offset of the line
in that program that it will next calculate (in the addressed coordinate system). It will also report the
program number and address offset of any lines it must RETURN to if it is inside a GOSUB or CALL jump
(up to 15 deep).
The number reported after the colon is not a line number; as an address offset, it is the number of words
of memory from the top of the program. The LIST PROGRAM command, when used with comma
delimiters, shows the program or section of the program with address offsets for each line. The LIST
PC command can show lines of the program with address offsets from the point of calculation.
Because Turbo PMAC calculates ahead in a continuous sequence of moves, the PC (Program Calculation)
command will in general return a program line further down in the program than PE will.
If the coordinate system is not pointing to any motion program, Turbo PMAC will return an error
(ERR003 if I6=1 or 3). Initially the pointing must be done with the B{constant} command.
Example:
PC
P1:0 ; Ready to execute at the top of PROG 1
PC
P76:22 ; Ready to execute at 22nd word of PROG 76
LIST PC
P76:22:X10Y20 ; Program line at 22nd word of PROG 76
PC
P1001:35>P3.12 ; Execution will return to PROG 3, address 12
See Also:
On-line commands B{constant}, LIST, LIST PC, LIST PE, LIST PROGRAM, PE
PE
Function: Report Program Execution Pointer
Scope: Coordinate-system specific
Syntax: PE
This command causes Turbo PMAC to report the motion program number and address offset of the
currently executing programmed move in the addressed coordinate system. This is similar to the PC
command, which reports the program number and address offset of the next move to be calculated. Since
Turbo PMAC is calculating ahead in a continuous sequence of moves, PC will in general report a move
line several moves ahead of PE.
If the coordinate system is not pointing to any motion program, Turbo PMAC will return an error
(ERR003 if I6=1 or 3). Initially the pointing must be done with the B{constant} command.
Example:
PE
P1:2
PE
P1:5
See Also:
On-line commands B{constant}, LIST, LIST PC, LIST PE, PC
PMATCH
Function: Re-match Axis Positions to Motor Positions
Scope: Coordinate-system specific
Syntax: PMATCH
This command causes Turbo PMAC to recalculate the axis starting positions for the coordinate system to
match the current motor commanded positions (by inverting the axis definition statement equations and
solving for the axis position).
This function is executed automatically by Turbo PMAC each time an R (run) or S (step) command is
given, to make sure the first move is executed properly.
The PMATCH command does not need to be executed under normal circumstances. However, if
something has changed the relationship between motor and axis in the middle of a motion program, this
command should be issued – usually with CMD "PMATCH" surrounded by DWELLs from within the
motion program – before the next move command in the program.
These changes include changing the Ixx06 position following mode between normal and offset mode,
bringing a new axis into the coordinate system, and changing an axis definition in the coordinate system.
If an axis move is then attempted without the use of the PMATCH command, Turbo PMAC will use the
wrong axis starting point in its calculations, resulting in a jump at the beginning of the move.
If more than one motor is defined to a given axis (as in a gantry system), the commanded position of the
lower-numbered motor is used in the Turbo PMAC calculations.
Example:
OPEN PROG 10 CLEAR
...
CMD"&1#4->100C" ; Bring C-axis into coordinate system
DWELL20
CMD"PMATCH" ; Issue PMATCH so C-axis has proper start position
DWELL20
C90
...
See Also:
Further Position Processing (Setting Up a Motor)
Axes, Coordinate Systems (Setting Up a Coordinate System)
I-variable Ixx06
PR
Function: Report Rotary Program Remaining
Scope: Coordinate-system specific
Syntax: PR
This command causes Turbo PMAC to report the number of program lines that have been entered in the
rotary buffer for the addressed coordinate system but have not yet been executed (program remaining).
This command can be useful for finding out if it is time to send new lines to the buffer. The value
returned is accurate only if the rotary program buffer is open.
Example:
B0 ; Point to rotary buffer
OPEN ROT ; Open rotary buffer
X10F10 ; Enter first line
X20 ; Enter second line
X30 ; Enter third line
X40 ; Enter fourth line
PR ; Ask for program remaining
4 ; Turbo PMAC responds that four lines remain
R ; Start running the program
PR ; Ask for program remaining
2 ; Turbo PMAC responds that two lines remain
See Also:
Rotary Program Buffers (Writing and Executing Motion Programs)
BREQ interrupt (Using Interrupts -- Writing a Host Communications Program)
I-variables I16, I17
Q
Function: Quit Program at End of Move
Scope: Coordinate-system specific
Syntax: Q
This causes the currently addressed coordinate system to cease execution of the program either at the end
of the currently executing move, or at the end of the last move that has been calculated.
If the coordinate system is in segmentation mode (Isx13 > 0) without buffered lookahead (Isx20 = 0),
execution will stop at the end of the currently executing move, even if the next move has already been
calculated. In this mode, if axes are jogged away, they must be returned to the quit point with the J=
command before program execution is resumed. Otherwise, Turbo PMAC will reject the resumption
command, reporting ERR017 if I6 = 1 or 3.
If the coordinate system is executing with buffered lookahead (Isx13 > 0, Isx20 > 0), no more moves will
be added to the lookahead buffer, but all moves in the lookahead buffer will be executed.
If the coordinate system is not in segmentation mode (Isx13 = 0), execution will stop either at the end of
the currently executing move, or if one more move has already been calculated, at the end of that move.
The program counter is set to the next line in the program, so execution may be resumed at that point with
an R or S command.
Example:
Q{constant}..{constant}={constant}
where:
the first {constant} is an integer from 0 to 8190 representing the number of the first Q-variable;
the second {constant} is an integer from 1 to 8191 representing the number of the last Q-variable;
it must be at least as great as the first {constant}
the final {constant} contains the value to be given to the specified range of Q-variables
Q{constant},{constant},{constant}={constant}
where:
the first {constant} is an integer from 0 to 8190 representing the number of the first Q-variable;
the second {constant} is an integer from 1 to 8191 representing the number Q-variables whose
value is to be set;
the third {constant} is an integer from 1 to 8191 representing the numerical spacing between each
Q-variable whose value is to be set;
the final {constant} contains the value to be given to the specified set of Q-variables
This command causes Turbo PMAC to assign the value of the expression to the specified Q-variable or
range of Q-variables for the addressed coordinate system.
If a motion or PLC program buffer is open when the single-variable form of this command is sent to
Turbo PMAC, the command will be entered into the buffer for later execution. If a motion or PLC
program buffer is open when the multiple-variable form of this command is sent, Turbo PMAC will reject
the command with an error, reporting ERR003 if I6 is 1 or 3.
Example:
Q100=2.5
Q20= Q18*SIN(Q19)
Q(P1+P2)=2.71828
Q(200+Q1)=P1*LN(7.5)
Q1..10=0
Q20,5,10=7.5 ; Sets Q20, Q40, Q60, Q80, & Q100 to 7.5
See Also:
Q-Variables (Computational Features)
On-line commands I{data}={expression}, M{data}={expression},
P{data}={expression}, Q{constant}
Program command Q{data}={expression}
R
Function: Run Motion Program
Scope: Coordinate-system specific
Syntax: R
This command causes the addressed Turbo PMAC coordinate system to start continuous execution of the
motion program addressed by the coordinate system’s program counter from the location of the program
counter. Alternately, it will restore operation after a \ or H command has been issued (even if a program
was or is not running). Addressing of the program counter is done initially using the B{constant}
command.
The coordinate system must be in a proper condition in order for Turbo PMAC to accept this command.
Otherwise Turbo PMAC will reject this command with an error; if I6 is 1 or 3, it will report the error
number. The following conditions can cause Turbo PMAC to reject this command (also listed are the
remedies):
Both limits set for a motor in coordinate system (ERR010); clear limits
Another move in progress (ERR011); stop move (e.g. with J/)
Open-loop motor in coordinate system (ERR012); close loop with J/ or A
Unactivated motor in coordinate system (ERR013); change Ixx00 to 1 or remove motor from
coordinate system
No motors in the coordinate system (ERR014); put at least 1 motor in C.S.
Fixed motion program buffer open (ERR015); close buffer and point to program
No program pointed to (ERR015); point to program with B command
Program structured improperly (ERR016); correct program structure
Motors not at same position as stopped with H or Q command (ERR017); move back to stopped
position with J=
Example:
&1B1R ; C.S.1 point to PROG 1 and run
&2B200.06 ; C.S.2 point to N6000 of PROG 200 and run
Q ; Quit this program
R ; Resume running from point where stopped
H ; Do a feed hold on this program
R ; Resume running from point where stopped
See Also:
Control Panel Port START/ Input (Connecting Turbo PMAC to the Machine)
Running a Motion Program (Writing and Executing Motion Programs)
I-variable I6
On-line commands <CTRL-R>, A, H, Q, S
JPAN Connector Pin 8
R[H]{address}
Function: Report the contents of specified memory address[es]
Scope: Global
Syntax: R[H]{address} [,{constant}[,{constant}]]
where:
{address} consists of a letter X, Y, or L; an optional colon (:); and an integer value from $000000
to $FFFFFF (0 to 16,777,215); specifying the starting Turbo PMAC memory or I/O address to be
read;
The RESUME PLC command cannot be used to restart execution of a PLC program that has been stopped
with a DISABLE PLC command. However, after a PLC has been stopped with a DISABLE PLC
command, if a PAUSE PLC command is then given for that PLC, then a RESUME PLC command can
be given to start operation at the point at which it has been stopped.
Note:
RESUME PLC 0..31 will restart all PLCs that have been paused, but not any
that have been disabled.
The line of the PLC at which execution will be resumed can be read with the LIST PLC,,1 command
PLC programs are specified by number, and may be used singularly in this command, in a list (separated
by commas), or in a range of consecutively numbered programs.
If a motion or PLC program buffer is open when this command is sent to Turbo PMAC, the command
will be entered into that buffer for later execution.
I-variable I5 must be in the proper state to allow the PLC programs specified in this command to execute.
Example:
RESUME PLC 1
RES PLC 2,7
RESUME PLC 3,21
RESUME PLC 0..31
Note:
If the RESUME command refers to multiple PLCs, only those PLCs that have been
stopped with the PAUSE command will be resumed.
See Also:
I-variable I5
On-line commands DISABLE PLC, ENABLE PLC, OPEN PLC, PAUSE PLC, LIST PLC,
<CONTROL-D>.
Program commands DISABLE PLC, ENABLE PLC, PAUSE PLC, RESUME PLC
S
Function: Execute One Move (Step) of Motion Program
Scope: Coordinate-system specific
Syntax: S
This command causes the addressed Turbo PMAC coordinate system to start single-step execution of the
motion program addressed by the coordinate system’s program counter from the location of the program
counter. Addressing of the program counter is done initially using the B{constant} command.
At the default Isx53 value of zero, a STEP command causes program execution through the next move or
DWELL command in the program, even if this takes multiple program lines.
When Isx53 is set to 1, a STEP command causes program execution of only a single program line, even if
there is no move or DWELL command on that line. If there is more than one DWELL or DELAY command
on a program line, a single STEP command will only execute one of the DWELL or DELAY commands.
Regardless of the setting of Isx53, if program execution on a STEP command encounters a
BLOCKSTART statement in the program, execution will continue until a BLOCKSTOP statement is
encountered.
If the coordinate system is already executing a motion program when this command is sent, the command
puts the program in single-step mode, so execution will stop at the end of the latest calculated move. In
this case, its action is the equivalent of the Q command.
The coordinate system must be in a proper condition in order for Turbo PMAC to accept this command.
Otherwise Turbo PMAC will reject this command with an error; if I6 is 1 or 3, it will report the error
number. The same conditions that cause Turbo PMAC to reject an R command will cause it to reject an S
command; refer to those conditions under the R command specification.
Example:
&3B20S ; C.S.3 point to beginning of PROG 20 and step
P1 ; Ask for value of P1
1 ; Turbo PMAC responds
S ; Do next step in program
P1 ; Ask for value of P1 again
-3472563 ; Turbo PMAC responds --probable problem
See Also:
Control Panel Port STEP/ Input (Connecting Turbo PMAC to the Machine)
Running a Motion Program (Writing and Executing Motion Programs)
I-variable I6, Isx53
On-line commands <CTRL-S>, A, H, Q, R, /, \
Program commands {axis}{data}, BLOCKSTART, BLOCKSTOP, DWELL, DELAY
SAVE
Function: Copy setup parameters to non-volatile memory.
Scope: Global
Syntax: SAVE
This command causes Turbo PMAC to copy setup information from active memory to non-volatile
memory, so this information can be retained through power-down or reset.
All user setup information, including programs, buffers, and definitions, is copied to flash memory with
the SAVE command. This information is copied back from flash to active memory during a normal
power-up/reset operation. This means that anything changed in Turbo PMAC’s active memory that is not
saved to flash memory will be lost in a power-on/reset cycle.
The retrieval of information from non-volatile memory on power-up/reset can be inhibited by a jumper on
E51 for a Turbo PMAC, or on E3 for a Turbo PMAC2.
Note:
Turbo PMAC does not provide the acknowledging handshake character to the
SAVE command until it has finished the saving operation, about one to two
seconds. The host program should be prepared to wait much longer for this
character than is necessary on most commands. Usually for this reason, it is not a
good idea to include the SAVE command as part of a dump download of a large
file.
Note:
During execution of the SAVE command, Turbo PMAC will execute no other
background tasks, including user PLCs and automatic safety checks, such as
following error and overtravel limits. Make sure the system is not depending on
these tasks for safety when the SAVE command is issued.
Example:
I130=60000 ; Set Motor 1 proportional gain
SAVE ; Save to non-volatile memory
I130=80000 ; Set new value
$$$ ; Reset card
Example:
IDNUMBER
374A256E9014D101
SIZE
Function: Report the amount of unused buffer memory in Turbo PMAC.
Scope: Global
Syntax: SIZE
This command causes Turbo PMAC to report to the host the amount of unused long words of memory
available for buffers. If no program buffer (motion, PLC or rotary buffer) is open, this value is reported
as a positive number. If a buffer is currently open, the value is reported as a negative number.
Example:
DEFINE GATHER ; Reserve all remaining memory for gathering
SIZE ; Ask for amount of open memory
0 ; PMAC reports none available
DELETE GATHER ; Free up memory from gathering buffer
SIZE ; Ask for amount of open memory
25232 ; PMAC reports number of words available
OPEN PROG 10 ; Open a motion program buffer
SIZE ; Ask for amount of open memory
-25232 ; The negative sign shows a buffer is open
See Also:
I-Variable I18
On-line commands DELETE GATHER
STN
Function: Report MACRO station order number
Scope: Global
Syntax: STN
This command causes Turbo PMAC to return its station order number, intended to represent the order of
the Turbo PMAC in the MACRO ring. This value is stored in variable I85, and can take a value of 0 to
254. When the Turbo PMAC has a station order number of 1 to 254, and receives a
MACROSTASCII{constant} command whose {constant} value matches the station order
number, it will respond to the command.
This station order number is set with the STN={constant} or the I85={constant} command. If
no station order number has been assigned to the Turbo PMAC, it will return a value of 0 to this
command. The first device in the ring with a station order number of 0 will respond to a
MACROSTASCII255 command.
See Also:
I-variable I85
Commands STN={constant}, MACROSTASCII
STN={constant}
Function: Set MACRO station order number
Scope: Global
Syntax: STN={constant}
where:
{constant} is a value in the range 0 to 254 representing the order of the Turbo PMAC in the
MACRO ring
This command causes Turbo PMAC to set its station order number, intended to be the order of the Turbo
PMAC in the MACRO ring. When the Turbo PMAC has a station order number of 1 to 254, and receives
a MACROSTASCII{constant} command whose {constant} value matches the station order
number, it will respond to the command. The first device in the ring with a station order number of 0 (no
order established) will respond to a MACROSTASCII255 command.
See Also:
I-variable I85
Commands STN, MACROSTASCII
TIME
Function: Report present time
Scope: Global
Syntax: TIME
This command causes Turbo PMAC to report the current time of day. The time is reported in the
international 24-hour clock format:
{hh}:{mm}:{ss}
where:
{hh} is the 2-digit representation of the hour (00 <= {hh} <= 23)
{mm} is the 2-digit representation of the minute (00 <= {mm} <= 59)
{ss} is the 2-digit representation of the second (00 <= {ss} <= 59)
The time must originally have been set with the TIME={time} command for the time reported here to
be valid. If the Option 18B non-volatile clock/calendar IC is present, this IC will retain and advance the
time information even while no external power is applied. On power-up or reset of the Turbo PMAC, the
present date and time are copied from the module into active memory, and the time information is then
advanced in active memory. The TIME command reports from active memory.
If the Option 18B is not present, Turbo PMAC will default to Jan. 1, 2000, at 00:00:00, on power-
up/reset, and date and time will advance in active memory from this point. The actual date may be loaded
into active memory after power-up/reset, and the date and time will advance from this point.
Examples:
TIME
00:01:42 ; 0 hours, 1 minute, 42 seconds
TIME
13:47:22 ; 13 hours, 47 minutes, 22 seconds (1:47:22 pm)
TIME={time}
Function: Set the present time
Scope: Global
Syntax: TIME={hh}:{mm}[:{ss}]
where:
{hh} is the 2-digit representation of the hour (00 <= {hh} <= 23)
{mm} is the 2-digit representation of the minute (00 <= {mm} <= 59)
{ss} is the 2-digit representation of the second (00 <= {ss} <= 59)
This command sets the current time in Turbo PMAC’s active (volatile) memory. The time is entered in
the international 24-hour clock format, as hour/minute/second.
Entering of the seconds is optional; if the seconds are not entered, Turbo PMAC will use 0 seconds. Date
and time automatically advance in Turbo PMAC’s active memory, and the present time can be queried at
any time with the TIME command.
This time information is not retained through a power-down or board reset unless the Option 18B non-
volatile clock/calendar IC is present and the active date and time information has been copied into the
non-volatile IC with the UPDATE command.
The present date can be set with the TODAY={date} command.
Examples:
TIME=08:30 ; Set time to 8:30:00 am
TIME=17:45:24 ; Set time to 5:45:24 pm
TODAY
Function: Report present date
Scope: Global
Syntax: TODAY
This command causes Turbo PMAC to report the current date. The date is reported in the North
American format:
{day} {mm}/{dd}/{yyyy}
where:
{day} is the 3-letter abbreviation for the day of the week
{mm} is the 2-digit representation of the month
{dd} is the 2-digit representation of the day of the month
{yyyy} is the 4-digit representation of the year
The date must originally have been set with the TODAY={date} command for an accurate date to be
reported here. If the Option 18B non-volatile clock/calendar IC is present, this IC will retain and advance
the date information even while no external power is applied. On power-up or reset of the Turbo PMAC,
the present date and time are copied into active memory, and then they advance automatically in the
active memory. The TODAY command reports from active memory.
If the Option 18B is not present, Turbo PMAC will default to Jan. 1, 2000, at 00:00:00, on power-
up/reset, and date and time will advance in active memory from this point. The actual date may be loaded
into active memory after power-up/reset, and the date and time will advance from this point.
Note:
The 4-digit representation of the year eliminates possible Year 2000 problems in
user code processing the date information.
Examples:
TODAY
WED 09/09/1998
TODAY
FRI 04/22/2000
TODAY={date}
Function: Set the present date
Scope: Global
Syntax: TODAY={mm}/{dd}/{yyyy}
where:
{mm} is the 2-digit representation of the month
{dd} is the 2-digit representation of the day of the month
{yyyy} is the 4-digit representation of the year
This command sets the current date in Turbo PMAC’s active (volatile) memory. The date is entered in
the North American style, as month/day/year. Date and time advance automatically in Turbo PMAC’s
active memory, and the present date can be queried at any time with the TODAY command.
Note:
The 4-digit representation of the year eliminates possible Year 2000 problems in
user code processing the date information.
This date information is not retained through a power-down or board reset unless the Option 18B non-
volatile clock/calendar IC is present and the active date and time information have been copied into the
non-volatile IC with the UPDATE command.
The present time can be set with the TIME={time} command.
Examples:
TODAY=10/30/1998 ; Set date to October 30, 1998
TODAY=01/02/1999 ; Set date to January 2, 1999
TODAY=05/09/2001 ; Set date to May 9, 2001
TYPE
Function: Report type of Turbo PMAC
Scope: Global
Syntax: TYPE
This command causes Turbo PMAC to return a string reporting the configuration of the card. It will
report the configuration as a text string in the format:
{Turbo PMAC type},{Clock Multiplier}
where:
{Turbo PMAC type} can take the following values:
TURBO1 Turbo PMAC (1)
TURBO2 Turbo PMAC2 (non-Ultralite)
TURBOU Turbo PMAC2 Ultralite (MACRO only)
{Clock multiplier} is reported in the format
Xn
where n is the multiplication of crystal frequency to CPU frequency.
Since the crystal frequency is always 20 MHz, an X4 value reports 80 MHz operation. The reported
clock multiplier value shows at what frequency the CPU is actually operating, as controlled by I52, not
necessarily the maximum frequency rating of the CPU hardware.
Examples:
TYPE
TURBO1, X4
TYPE
TURBO2, X4
TYPE
TURBOU, X5
See Also:
On-line commands VERSION, DATE
UNDEFINE
Function: Erase Coordinate System Definition
Scope: Coordinate-system specific
Syntax: UNDEFINE
UNDEF
This command causes Turbo PMAC to erase all of the axis definition statements in the addressed
coordinate system. It does not affect the axis definition statements in any other coordinate systems. It
can be useful to use before making new axis definitions.
To erase the axis definition statement of a single motor only, use the #{constant}->0 command; to
erase all the axis definition statements in every coordinate system, use the UNDEFINE ALL command.
Example:
&1 ; Address C.S.1
#1-> ; Ask for axis definition of Motor 1
10000X ; Turbo PMAC responds
#2-> ; Ask for axis definition of Motor 2
10000Y ; Turbo PMAC responds
UNDEFINE ; Erase axis definitions
&2 ; Address C.S.2
#1->10000X ; Redefine Motor 1 as X-axis in C.S.2
#2->10000Y ; Redefine Motor 2 as Y-axis in C.S.2
See Also:
Axes, Coordinate Systems (Setting Up a Coordinate System)
On-line commands #{constant}->, #{constant}->0, UNDEFINE ALL
UNDEFINE ALL
Function: Erase coordinate definitions in all coordinate systems
Scope: Global
Syntax: UNDEFINE ALL
UNDEF ALL
This command causes all of the axis definition statements in all coordinate systems to be cleared. It is a
useful way of starting over on a reload of Turbo PMAC's coordinate system definitions.
Example:
&1#1-> ; Request axis definition of Motor 1 in C.S. 1
1000X ; Turbo PMAC responds
&2#5-> ; Request axis definition of Motor 5 in C.S. 2
1000X ; Turbo PMAC responds
UNDEFINE ALL ; Erase all axis definitions
&1#1-> ; Request axis definition of Motor 1 in C.S. 1
0 ; Turbo PMAC responds that there is no definition
&2#5-> ; Request axis definition of Motor 5 in C.S. 2
0 ; Turbo PMAC responds that there is no definition
See Also:
Axes, Coordinate Systems (Setting Up a Coordinate System)
V
Function: Report motor velocity
Scope: Motor specific
Syntax: V
This command causes Turbo PMAC to report the velocities of the addressed motor to the host. The
velocity units are typically scaled in encoder counts per servo cycle, rounded to the nearest tenth.
To scale these values into counts/msec, multiply the response by 8,388,608/I10 (servo cycles/msec).
This command returns filtered velocity values, with the filter time constant controlled by global variables
I60 and I61. It does not report the raw velocity register calculated by the servo loop each servo cycle.
Example:
V ; Request actual velocity of addressed motor
21.9 ; Turbo PMAC responds with 21.9 cts/cycle
; (*8,388,608/3,713,707 = 49.5 cts/msec)
#6V ; Request velocity of Motor 6
-4.2 ; Turbo PMAC responds
#5V#2V ; Request velocities of Motors 5 and 2
0 ; Turbo PMAC responds with Motor 5 first
7.6 ; Turbo PMAC responds with Motor 2 second
See Also:
I-variables I10, Ixx09, Ixx60
On-line commands <CTRL-V>, F, P
VERSION
Function: Report PROM firmware version number
Scope: Global
Syntax: VERSION
VER
This command causes Turbo PMAC to report the firmware version it is using.
When a Turbo PMAC is in bootstrap mode (powering up with bootstrap jumper on) for re-load of the
operational firmware, Turbo PMAC will report the version of the bootstrap firmware, not the operational
firmware. Otherwise, it will report the operational firmware version.
Example:
VERSION ; Ask Turbo PMAC for firmware version
1.934 ; Turbo PMAC responds
See Also:
Resetting Turbo PMAC (Talking to Turbo PMAC)
On-line command DATE, EAVERSION, TYPE
VID
Function: Report vendor identification number
Scope: Global
Syntax: VID
This command causes Turbo PMAC to return the vendor ID number. For a Delta Tau product such as the
Turbo PMAC, the vendor ID number is 1. This command is part of a multi-vendor identification
architecture for the MACRO ring.
See Also:
Commands CID, IDNUMBER, SID, VID
W{address}
Function: Write values to a specified address(es).
Scope: Global
Syntax: W{address},{value} [,{value}...]
where:
{address} consists of a letter X, Y, or L; an option colon (:); and an integer value from , $000000
to $FFFFFF (0 to 16,777,215); specifying the starting Turbo PMAC memory or I/O address to be
read;
{constant} is an integer, specified in decimal or hexadecimal, specifying the value to be written
to the specified address;
further {constants} specify integer values to be written into subsequent consecutive higher
addresses
This command causes Turbo PMAC to write the specified {constant} value to the specified memory
word address, or if a series of {constant} values is specified, to write them to consecutive memory
locations starting at the specified address (it is essentially a memory POKE command). The command
can specify either short (24-bit) words in Turbo PMAC’s X-memory, short (24-bit) words in Turbo
PMAC's Y-memory, or long (48-bit) words covering both X and Y memory (X-word more significant).
This choice is controlled by the use of the X, Y, or L address prefix in the command, respectively.
Example:
WY:$078002,4194304 ; This should put 5V on DAC2
; (provided I200=0 so servo does not overwrite)
WY$003501,$078000,$078004,$078008,$07800C
; This writes the first four entries to the
; encoder conversion table
See Also:
On-line command R[H]{address}
Memory and I/O Map.
Z
Function: Make commanded axis positions zero.
Scope: Coordinate-system specific
Syntax: Z
This command causes Turbo PMAC to re-label the current commanded axis positions for all axes in the
coordinate system as zero. It does not cause any movement; it merely re-names the current position.
This command is simply a short way of executing {axis}=0 for all axes in the coordinate system.
PSET X0 Y0 (etc.) is the equivalent motion program command.
This does not set the motor position registers to zero; it changes motor position bias registers to reflect the
new offset between motor zero positions and axis zero positions. However, the motor reported positions
will reflect the new bias, and report positions of zero (+/- the following error)
Example:
<CTRL-P> ; Ask for reported motor positions
2001 5002 3000 0 0 0 0 0 ; Turbo PMAC reports positions
Z ; Zero axis positions
<CTRL-P> ; Ask for reported motor positions again
1 2 -1 0 0 0 0 0 ; Turbo PMAC responds
See Also:
On-line commands {axis}={constant}
Memory map registers D:$0000CC, D:$00014C, etc.
Suggested M-variable definitions Mxx64.
The first data item for each axis is the scaled ending position or distance (depending on whether the axis
is in absolute (ABS) or incremental (INC) mode; position scaling is determined by the axis definition
statement), and the second data item (after the colon) is the ending velocity.
The velocity units are the scaled position units as established by the axis definition statements divided by
the time units as set by Isx90 for Coordinate System x. The velocity here is a signed quantity, not just a
magnitude. See the examples in the PVT mode description of the Writing and Executing Motion
Programs section.
The time for the segment is the argument for the most recently executed PVT or TM command.
In PVT mode, if no velocity is given for the segment, Turbo PMAC assumes an ending velocity of zero
for the segment.
Examples:
X1000:50
Y500:-32 Z737.2:68.93
A(P1+P2):(P3) B(SIN(Q1)):0
See Also:
PVT Mode Moves (Writing and Executing Motion Programs)
Axis Definition Statements (Setting Up a Coordinate System)
I-variables Isx89, Isx90
Motion program commands PVT, TM
{axis}{data}^{data}[{axis}{data}^{data}...]
Function: Move Until Trigger
Type: Motion program
Syntax: {axis}{data}^{data}[{axis}{data}^{data}...]
where:
{axis} is the character specifying which axis (X, Y, Z, A, B, C, U, V, W);
the first {data} is a constant (no parentheses) or expression (in parentheses) representing the end
position or distance in the absence of a trigger;
the second {data} (after the ^ arrow) is a constant (no parentheses) or expression (in parentheses)
representing the distance from the trigger position;
[{axis}{data}^{data}...] is the optional specification of simultaneous movement for more
axes
In the RAPID move mode, this move specification permits a move-until-trigger function. The first part of
the move description for an axis – before the ^ sign – specifies where to move in the absence of a trigger.
It is a position if the axis is in absolute mode; it is a distance if the axis is in incremental mode. In both
cases the units are the scaled axis user units. If no trigger is found before this destination is reached, the
move is a standard RAPID move.
The second part of the move description for an axis – after the ^ sign – specifies the distance from the
trigger position to end the post-trigger move if a trigger is found. The distance is expressed in the scaled
axis user units.
Each motor assigned to an axis specified in the command executes a separate move-until-trigger. All the
assigned motors will start together, but each can have its own trigger condition. If a common trigger is
required, the trigger signal must be wired into all motor interfaces. Each motor can finish at a separate
time; the next line in the program will not start to execute until all motors have finished their moves. No
blending into the next move is possible.
The trigger for a motor can be either a hardware input trigger if bit 1 of Ixx97 is 0, or the motor warning
following error status bit if bit 1 of Ixx97 is 1 (bit 0 of Ixx97 should also be set to 1 in this case). If a
hardware input trigger is used, I-variables I7mn2 and I7mn3 (e.g. I7012 and I7013) for the flag channel
specified by Ixx25 determine which edges of which flags cause the trigger. If the warning following error
bit is used for torque-limited triggering, then Ixx12 sets the size of the warning following error.
The speed of the move, both before the trigger and after, is set by Ixx22 if Ixx90=0 or by Ixx16 if
Ixx90=1. The acceleration is set by Ixx19 to Ixx21.
On the same line, some axes may be specified for normal untriggered RAPID moves that will execute
starting simultaneously.
If the move ends for a motor without a trigger being found, the “trigger move” status bit (bit 7 of the
second motor status word returned on a ? command) is left set after the end of the move. If the trigger
has been found, this bit is cleared to 0 at the end of the move.
Example:
X1000^0
X10^-0.01 Y5.43^0.05
A(P1)^(P2) B10^200 C(P3)^0 X10
See Also:
Move-Until-Trigger (Writing and Executing Motion Programs)
Torque-Limited Triggering (Setting Up a Motor)
RAPID-mode moves (Writing and Executing Motion Programs)
{axis}{data}[{axis}{data}…] {vector}{data} [{vector}{data}…]
Function: Circular Arc Move Specification
Type: Motion program (PROG and ROT)
Syntax: {axis}{data} [{axis}{data}...] {vector}{data}
[{vector}{data}...]
where:
{axis} is a character specifying which axis (X, Y, Z, A, B, C, U, V, W);
{data} is a constant (no parentheses) or an expression (in parentheses) representing the end position
or distance;
[{axis}{data}...] is the optional specification of simultaneous movement for more axes;
{vector} is a character (I, J, or K) specifying a vector component (parallel to the X, Y, or Z axis,
respectively) to the center of the arc; or the character R specifying the magnitude of the vector;
{data} specifies the magnitude of the vector component;
[{vector}{data}...] is the optional specification of more vector components.
For a blended circular mode move, both the move endpoint and the vector to the arc center are specified.
The endpoint is specified just as in a LINEAR mode move, either by position (referenced to the
coordinate system origin), or distance (referenced to the starting position).
The center of the arc for a circular move must also be specified in the move command. Usually this is
done by defining the vector to the center. This vector can either be referenced to the starting point of the
move (incremental radial vector mode – the default, or if an INC (R) command has been given), or it
can be referenced to the coordinate system origin (absolute radial vector mode – if an ABS (R)
command has been given).
Alternatively, just the magnitude of the vector to the center can be specified with R{data} on the
command line. If this is the case, Turbo PMAC will calculate the location of the center itself. If the value
specified by {data} is positive, Turbo PMAC will compute the short arc path to the destination (<=
180o); if it is negative, Turbo PMAC will compute the long arc path (>= 180 o). It is not possible to
specify a full circle in one command with the R vector specifier.
The plane for the circular arc must have been defined by the NORMAL command (the default -- NORMAL
K-1 -- defines the XY plane). This command can only define planes in XYZ-space, which means that
only the X, Y, and Z axes can be used for circular interpolation. Other axes specified in the same move
command will be interpolated linearly to finish in the same time.
The direction of the arc to the destination point – clockwise or counterclockwise – is controlled by
whether the card is in CIRCLE1 (clockwise) or CIRCLE2 (counterclockwise) mode. The sense of
clockwise in the plane is determined by the direction of the NORMAL vector to the plane.
If the destination point is a different distance from the center point than is the starting point, the radius is
changed smoothly through the course of the move, creating a spiral. This is useful in compensating for any
round off errors in the specifications. However, if the distance from either the starting point or the
destination point to the center point is zero, and error condition will be generated and the program will stop.
If the vector from the starting point to the center point does not lie in the circular interpolation plane, the
projection of that vector into the plane is used. If the destination point does not lie in the same circular
interpolation plane as the starting point, a helical move is done to the destination point.
If the destination point (or its projection into the circular interpolation plane containing the starting point)
is the same as the starting point, a full 360o arc is made in the specified direction (provided that IJK
vector specification is used). In this case, only the vector needs to be specified in the move command,
because for any axis whose destination is not specified, the destination point is automatically taken to be
the same as the starting point.
If no vector, and no radial magnitude, is specified in the move command, a linear move will be done to
the destination point, even if the program is in circular mode.
Note:
Turbo PMAC performs arc moves by segmenting the arc and performing the best
cubic fit on each segment. I-variable Isx13 determines the time for each segment.
Isx 13 must be set greater than zero to put the coordinate system into this
segmentation mode in order for arc moves to be done. If Isx13 is set to zero,
circular arc moves will be done in linear fashion.
Examples:
X5000 Y3000 I1000 J1000
X(P101) Z(P102) I(P201) K(P202)
X10 I5
X10 Y20 C5 I5 J5
Y5 Z3 R2
J10 ; Specifies a full circle of 10 unit radius
See Also:
Circular Moves (Writing and Executing Motion Programs)
I-variables Isx13, Isx87, Isx88, Isx89, Isx90
Program commands NORMAL, ABS, INC, CIRCLE1, CIRCLE2, TA, TS, TM, F
A{data}
Function: A-Axis Move
Type: Motion program (PROG or ROT)
Syntax: A{data}
where:
{data} is a floating-point constant or expression representing the position or distance in user units
for the A-axis
This command causes a move of the A-axis. (See {axis}{data} descriptions, above.) If it follows a
subroutine call (explicit or with PRELUDE) on a program line, it can be used instead to pass its value to
the subroutine through use of the READ command.
Examples:
A10
A(P23)
A25 B10 Z35
A(20*SIN(Q5))
CALL50 A-10
See Also:
Program commands {axis}{data}, B, C, U, V, W, X, Y, Z, CALL, PRELUDE, READ
ABS
Function: Absolute Move Mode
Type: Motion program (PROG and ROT)
Syntax: ABS [({axis}[,{axis}...])]
where:
{axis} is a character (X,Y,Z,A,B,C,U,V,W) representing the axis to be specified, or the character R
to specify radial vector mode
Note:
No spaces are permitted in this command.
The ABS command without arguments causes all subsequent positions in motion commands for all axes
in the coordinate system running the motion program to be treated as absolute positions. This is known as
absolute mode and it is the power-on default condition.
An ABS statement with arguments causes the specified axes in the coordinate system running the program
to be in absolute mode, and all others stay the way they were before.
If R is specified as one of the axes, the I, J, and K terms of the circular move radius vector specification
will be specified in absolute form (i.e. as a vector from the origin, not from the move start point). An
ABS command without any arguments does not affect this vector specification. The default radial vector
specification is incremental.
If no motion program buffer is open when this command is sent to Turbo PMAC, it will be executed as an
on-line coordinate system command.
Examples:
ABS(X,Y)
ABS
ABS(V)
ABS(R)
See Also:
Circular Moves (Writing and Executing Motion Programs)
This statement permits the user to mathematically determine which motor will be addressed. The value of
the floating-point P-variable is rounded to the nearest integer, and if this integer value is out of the range 1
– 32, the remainder of the number when divided by 32 is used. For example, if the P-variable had a value
of 34.3, Motor 2 would be addressed (remainder of 34/32 is 2).
This statement does not affect subsequent COMMAND statements in this PLC that explicitly address a
motor. It does not affect COMMAND statements in any other PLC program. It does not affect any motor-
specific commands from a host computer issued over any of the communications ports
Examples:
P4=12 ; Set value of P4 to 12
ADDRESS#P4 ; Address Motor 12
COMMAND “J+” ; Jog addressed motor (#12) in positive direction
COMMAND “#11J-” ; Jog motor 11 in negative direction
COMMAND “J/” ; Stop jogging addressed motor (#12 still). Routine to home all odd-numbered motors
P100=1
WHILE (P100<32) ; Loop thru motors
ADDRESS#P100 ; Address motor using P100 value
COMMAND “HM” ; Start homing addressed motor
P100=P100+2 ; Increment to next odd-numbered motor
ENDWHILE
ADDRESS&P{constant}
Function: Select program’s addressed coordinate system
Type: PLC programs 1 to 31 only
Syntax: ADDRESS&P{constant}
ADR&P{constant}
where:
{constant} is an integer from 0 to 8191 representing the P-variable number whose value
determines the coordinate to be addressed
This statement, when executed, selects the coordinate system that will be addressed by this particular PLC
program when it issues coordinate-system-specific commands with subsequent COMMAND statements and
Q-variable assignments. The statement specifies the number of a P-variable whose value determines
which coordinate system is addressed. For example, if variable P4 had a value of 12, the statement
ADDRESS&P4, when executed, would select Motor 12.
This statement permits the user to mathematically determine which coordinate system will be addressed.
The value of the floating-point P-variable is rounded to the nearest integer, and if this integer value is out of
the range 1 – 16, the remainder of the number when divided by 16 is used. For example, if the P-variable
had a value of 19.2, Motor 3 would be addressed (remainder of 19/16 is 3).
This statement does not affect subsequent COMMAND statements in this PLC that explicitly address a
coordinate system. It does not affect COMMAND statements in any other PLC program. It does not affect
any coordinate-system-specific commands from a host computer issued over any of the communications
ports.
Examples:
P9=11 ; Set value of P9 to 11
ADDRESS&P9 ; Address C.S. 11
COMMAND “R” ; Run program in addressed C.S.
COMMAND “&2S” ; Single-step program in C.S. 2
Q10=3 ; Set value of Q10 in addressed C.S. (&11 still!)
ADIS{constant}
Function: Absolute displacement of X, Y, and Z axes
Type: Motion program (PROG and ROT)
Syntax: ADIS{constant}
where:
{constant} is an integer constant representing the number of the first of three consecutive Q-
variables to be used in the displacement vector
This command loads the currently selected (with TSEL) transformation matrix for the coordinate system
with offset values contained in the three Q-variables starting with the specified one. This has the effect of
renaming the current commanded X, Y, and Z axis positions (from the latest programmed move) to the
values of these variables (X=Q{data}, Y=Q({data}+1), Z=Q({data}+2)).
This command does not cause any movement of any axes; it simply renames the present positions.
This command is almost equivalent to a PSET X(Q{data}) Y(Q({data}+1))
Z(Q({data}+2)) command, except that ADIS does not force a stop between moves, as PSET does.
Examples:
Q20=7.5
Q21=12.5
Q22=25
ADIS 20 ; This makes the current X position 7.5, Y 12.5, Z25
See Also:
Axis Matrix Transformations (Writing and Executing Motion Programs)
On-line command DEFINE TBUF
Program commands TSEL, AROT, IDIS, IROT, TINIT
AND ({condition})
Function: Conditional AND
Type: PLC program only
Syntax: AND ({condition})
where:
{condition} is a simple or compound condition
This statement forms part of an extended compound IF or WHILE condition to be evaluated in a PLC
program. It must immediately follow an IF, WHILE, AND, or OR statement. This AND is a Boolean operator
logically combining the full conditions on its line and the program line immediately above. It takes lower
precedence than AND or OR operators within a compound condition on a single line (the parentheses cause
those to be executed first), but it takes higher precedence than an OR operator that starts a line.
In motion programs, there can be compound conditions within one program line, but not across multiple
program lines, so this statement is not permitted in motion programs.
Note:
This logical AND command, which acts on conditions, should not be confused with
the bit-by-bit & (ampersand) operator that acts on values.
Examples:
IF (M11=1) ; This branch will start a motion program running
AND (M12=1) ; on a cycle where inputs M11 and M12 are 1 and
AND (M21=0) ; M21 is still zero. Note that M21 is immediately
CMD"R" ; set to one so the run command will not be given
M21=1 ; again in the next cycle.
ENDIF
See Also:
Writing a PLC Program
Conditions (Program Computational Features)
Program Commands IF, WHILE, OR
AROT{constant}
Function: Absolute rotation/scaling of X, Y, and Z axes
Type: Motion program (PROG and ROT)
Syntax: AROT{constant}
where:
{constant} is an integer representing the number of the first of nine consecutive Q-variables to be
used in the rotation/scaling matrix
This command loads the currently selected (with TSEL) transformation matrix for the coordinate system
with rotation/scaling values contained in the nine Q-variables starting with the specified one. This has the
effect of renaming the current commanded X, Y, and Z axis positions (from the latest programmed move)
by multiplying the XYZ vector by this matrix.
The rotation and scaling is done relative to the base XYZ coordinate system, defined by the axis
definition statements. The math performed is:
[Xrot Yrot Zrot]T = [Rot Matrix] [Xbase Ybase Zbase]T
This command does not cause any movement of axes; it simply renames the present positions.
Note:
When using this command to scale the coordinate system, do not use the radius
center specification for circle commands. The radius does not get scaled. Use the
I, J, K vector specification instead.
Examples:
Create a 3x3 matrix to rotate the XY plane by 30 degrees about the origin
Q40=COS(30) Q41=SIN(30) Q42=0
Q43=-SIN(30) Q44=COS(30) Q45=0
Q46=0 Q47=0 Q48=1
AROT 40 ; Implement the change
Create a 3x3 matrix to scale the XYZ space by a factor of 3
Q50=3 Q51=0 Q52=0
Q53=0 Q54=3 Q55=0
Q56=0 Q57=0 Q58=3
AROT 50 ; Implement the change
See Also:
Axis Matrix Transformations (Writing and Executing Motion Programs)
{letter} is any letter of the English alphabet, except N or O, representing the variable into which
the value following it will be placed (Q101 to Q126 for A to Z respectively);
following {data} is a floating-point constant or expression representing the value to be put into the
variable
This command allows the program to execute a subprogram and then return execution to the next line in
the program. A subprogram is entered into Turbo PMAC the same as a program, and is labeled as
PROGn (so one program can call another as a subprogram). The number n of the PROG heading is the
one to which the value after CALL refers: CALL7 would execute PROG7 and return. Commanding
execution of a non-existent subprogram will cause program execution to stop in an error condition.
The value immediately following CALL can take fractional values. If there is no fractional component,
the called program starts at the beginning. If there is a fractional component, the called program is
entered at a line label specified by the fractional component (if this label does not exist, Turbo PMAC
will generate an error and stop execution). Turbo PMAC works with five fractional digits to specify the
line label; if fewer are used, it fills out the rest with zeros automatically. For instance, CALL 35.1 is
interpreted as CALL 35.10000, which causes a jump to label N10000 of program 35. CALL
47.123 causes a jump to label N12300 of program 47.
If letters and data (e.g. X1000) follow the CALL{data}, these can be arguments to be passed to the
subprogram. If arguments are to be passed, the first line executed in the subroutine should be a READ
statement. This statement will take the values associated with the specified letters and place them in the
appropriate Q-variable. For instance, the data following A is placed in variable Q101 for the coordinate
system executing the program; that following B is placed in Q102; and so on, to the data following Z
being placed in Q126. The subprogram can then use these variables. If the subprogram calls another
subprogram with arguments, the same Q-variables are used. Refer to READ for more details.
If there is no READ statement in the subroutine, or if not all the letter values in the CALL line are “read”
(the READ statement stops as soon as it sees a letter in the calling line that is not in its list of letters to
read), the remaining letter commands are executed upon return from the subroutine according to their
normal function. For example, G01 X10 Y10 is equivalent to a CALL 1000.01 X10 Y10. To
implement the normal function for G01 (linear move mode), there would be the following subroutine in
PROG 1000:
N1000 LINEAR RETURN
Upon the return, X10 Y10 would be executed as a move according to the move mode in force, which is
LINEAR.
If the specified program and line label do not exist, the CALL command is ignored, and the program
continues as if it were not there.
Examples:
CALL500 ; to Prog 500 at the top (N0)
CALL500.1 ; to Prog 500 label N10000
CALL500.12 ; to Prog 500 label N12000
CALL500.123 ; to Prog 500 label N12300
CALL500.1234 ; to Prog 500 label N12340
CALL500.12345 ; to Prog 500 label N12345
CALL700 D10 E20 ; to Prog 700 passing D and E
See Also:
On-line command B{constant}
Program commands GOTO, GOSUB, READ, RETURN, G{data}, M{data}, T{data},
D{data}, N{constant}, O{constant}, PRELUDE
CC0
Function: Turn Off Cutter Radius Compensation
Type: Motion program (PROG and ROT)
Syntax: CC0
This turns off the cutter radius compensation mode, reducing it gradually through the next move. This is
equivalent to the G40 command of the machine-tool standard RS-274 language.
Examples:
CCR0.5 ; 1/2 unit cutter radius
CC1 ; Cutter compensation on to the left
X10 Y10 ; Compensation introduced during this move
X10 Y20
X20 Y20
X20 Y10
X10 Y10
CC0 ; Cutter compensation off
X0 Y0 ; Compensation eliminated during this move
OPEN PROG 1000 ; G-Code Subprogram
...
N40000 CC0 RETURN ; To implement G40 directly in Turbo PMAC
See Also:
Cutter (Tool) Radius Compensation
Program commands CC1, CC2, CCR{data}.
CC1
Function: Turn On 2D Cutter Radius Compensation Left
Type: Motion program (PROG and ROT)
Syntax: CC1
This turns on the cutter radius compensation mode, introducing the compensation gradually through the
next move. The cutter is offset to the left of the programmed tool path, looking in the direction of cutter
movement. The plane of the compensation is determined by the NORMAL command. This is equivalent
to the G41 command of the machine-tool standard RS-274 language.
Note:
The coordinate system must be in move segmentation mode (Isx13>0) in order to
perform cutter radius compensation. If Isx13=0 (no move segmentation), the
moves will be executed without compensation.
Examples:
CCR0.25 ; 1/4 unit cutter radius
CC1 ; Cutter compensation on to the left
X10 Y10 ; Compensation introduced during this move
X10 Y20
X20 Y20
X20 Y10
X10 Y10
CC0 ; Cutter compensation off
X0 Y0 ; Compensation eliminated during this move
OPEN PROG 1000 ; G-Code Subprogram
...
N41000 CC1 RETURN ; To implement G41 directly in Turbo PMAC
See Also:
Cutter (Tool) Radius Compensation
Program commands CC2, CC0, CCR{data}, NORMAL
CC2
Function: Turn On 2D Cutter Radius Compensation Right
Type: Motion program (PROG and ROT)
Syntax: CC2
This turns on the cutter radius compensation mode, introducing the compensation gradually through the
next move. The cutter is offset to the right of the programmed tool path, looking in the direction of cutter
movement. The plane of the compensation is determined by the NORMAL command. This is equivalent
to the G42 command of the machine-tool standard RS-274 language.
Note:
The coordinate system must be in move segmentation mode (Isx13>0) in order to
perform cutter radius compensation. If Isx13=0 (no move segmentation), the
moves will be executed without compensation.
Examples:
CCR1.5 ; 1-1/2 unit cutter radius
CC2 ; Cutter compensation on to the right
X10 Y10 ; Compensation introduced during this move
X10 Y20
X20 Y20
X20 Y10
X10 Y10
CC0 ; Cutter compensation off
X0 Y0 ; Compensation eliminated during this move
OPEN PROG 1000 ; G-Code Subprogram
...
N42000 CC2 RETURN ; To implement G42 directly in Turbo PMAC
See Also:
Tool Radius Compensation
Program commands CC1, CC0, CCR, NORMAL
CC3
Function: Turn On 3D Cutter Radius Compensation
Type: Motion program (PROG and ROT)
Syntax: CC3
This statement turns on three-dimensional cutter-radius compensation mode, introducing the
compensation gradually through the next move. Because the offset vectors are explicitly specified in 3D
compensation, there is no need to declare a left or right mode, as there is in 2D compensation.
When the CC3 statement is executed, both the tool-orientation and the surface-normal vector are
automatically set to the null vector. The tool-orientation vector can subsequently be modified by TX, TY,
and TZ values. A non-zero surface-normal vector must be declared with NX, NY, and NZ values before
any compensation will actually occur.
3D cutter-radius compensation remains active until the CC0 statement is executed.
CC4
Function: Turn Off Cutter Radius Compensation
Type: Motion program (PROG and ROT)
Default: CC4
This turns off the cutter radius compensation mode, reducing it gradually through the next move. Unlike
CC0, it does not automatically add a zero-distance move if it does not immediately find a programmed
lead-out move. CC4 is equivalent to the G40 command of the machine-tool standard RS-274 language.
See Also:
Cutter (Tool) Radius Compensation
Program commands CC0, CC1, CC2, CC3, CCR{data}
See Also:
Three-Dimensional Compensation, Program commands CC0, CCR{data}, NX{data}, NY{data},
NZ{data}, TR{data}, TX{data}, TY{data}, TZ{data}
CCR{data}
Function: Set Cutter Compensation Radius (2D & 3D)
Type: Motion program (PROG and ROT)
Syntax: CCR{data}
where:
{data} is a floating-point constant or expression representing the magnitude of the cutter’s end
radius
This statement sets the magnitude of the radius of the cutter for two-dimensional and three-dimensional
cutter-radius compensation, expressed in the user units of the X, Y, and Z axes. This function is often
part of the D tool data used in the machine-tool standard RS-274 (G) code.
In 2D compensation, an offset of this magnitude is made in the plane defined by the NORMAL vector,
perpendicular to the programmed path direction.
In 3D compensation, there are two radius values. The first is the radius of the cutter’s end, defined by this
CCR command. The second is the radius of the cutter’s shaft, defined by the TR command. In operation,
an offset is first made in the direction of the surface-normal vector of a magnitude defined by the CCR
cutter-end radius command. Then an offset is made of a magnitude equal to the TR tool radius minus the
CCR cutter-end radius. This offset is made in the plane of the surface-normal vector and the tool-
orientation vector, perpendicular to the tool-orientation vector.
The CCR cutter-end radius should be zero for a flat-end cutter; it should be equal to the TR tool-shaft
radius for a ball-end cutter; it should be somewhere in between for a partially rounded end. If the CCR
value is set greater than the TR value, the TR value is effectively increased to be equal to the CCR value
The value declared here affects the compensation of all subsequent moves until another value is declared.
See Also:
Cutter-Radius Compensation, Three-Dimensional Compensation
Program commands CC1, CC2, CC3, CC0, CCR{data}, NORMAL, NX{data}, NY{data},
NZ{data}, TR{data}, TX{data}, TY{data}, TZ{data}
CIRCLE1
Function: Set Blended Clockwise Circular Move Mode
Type: Motion program (PROG and ROT)
Syntax: CIRCLE1
CIR1
This command puts the program into clockwise circular move mode. The plane for the circular
interpolation is defined by the most recent NORMAL command, which has also defined the sense of
clockwise and counterclockwise in the plane.
The program is taken out of this circular move mode by another move mode command: the other
CIRCLE mode, LINEAR, PVT, RAPID etc. Any circular move command must have either an R or an
IJK vector specification; otherwise it will be performed as a linear move even when in CIRCLE mode.
Note:
The coordinate system must be in move segmentation mode (Isx13>0) in order to
perform circular interpolation. If Isx13=0 (no move segmentation), the moves will
be linearly interpolated.
Examples:
LINEAR ; Linear interpolation mode
X10Y10 F2 ; Linear move
CIRCLE1 ; Clockwise circular interpolation mode
X20 Y20 I10 ; Arc of 10-unit radius
X25 Y15 J-5 ; Arc of 5-unit radius
LINEAR ; Go back to linear mode
X25 Y5 ; Linear move
See Also:
Circular Moves (Writing and Executing Motion Programs)
I-variable Isx13
Program commands NORMAL, CIRCLE2, LINEAR, PVT, RAPID, SPLINE1,
{axis}{data}{vector}{data}
CIRCLE2
Function: Set Blended Counterclockwise Circular Move Mode
Type: Motion program (PROG and ROT)
Syntax: CIRCLE2
CIR2
The CIRCLE2 command puts the program into counterclockwise circular move mode. The plane for the
circular interpolation is defined by the most recent NORMAL command, which has also defined the sense
of clockwise and counterclockwise in the plane.
The program is taken out of this circular move mode by another move mode command: the other
CIRCLE mode, LINEAR, PVT, RAPID etc. Any circular move command must have either an R or an
IJK vector specification; otherwise it will be performed as a linear move even when in CIRCLE mode.
Note:
The coordinate system must be in move segmentation mode (Isx13>0) in order to
perform circular interpolation. If Isx13=0 (no move segmentation), the moves will
be linearly interpolated.
Examples:
LINEAR ; Linear interpolation mode
X10Y0 F2 ; Linear move
CIRCLE2 ; Counterclockwise circular interpolation mode
X20 Y10 J10 ; Arc of 10-unit radius
X15 Y15 I-5 ; Arc of 5-unit radius
CIRCLE1 ; Clockwise circle mode
X5 Y25 J10 ; Arc move of 10-unit radius
See Also:
Circular Moves (Writing and Executing Motion Programs)
I-variable Isx13
Program commands NORMAL, CIRCLE1, LINEAR, PVT, RAPID, SPLINE1,
{axis}{data}{vector}{data}
COMMANDx"{command}"
Function: Command issuance from internal program
Type: Motion program (PROG and ROT); PLC program
Syntax: COMMAND "{command}"
CMD "{command}"
COMMANDS "{command}"
CMDS "{command}"
COMMANDP "{command}"
CMDP "{command}"
COMMANDR "{command}"
CMDR "{command}"
COMMANDA "{command}"
CMDA"{command}"
This statement causes the program to issue a command to Turbo PMAC as if it came from the host
(except for addressing modes and response direction).
If there is a motor- or coordinate-system-specifier (#n or &n) within the quoted string, a motor- or
coordinate-system-specific command will be directed to that motor or coordinate system. If there is no
specifier, a motor- or coordinate-system-specific command will be directed to the first motor or
coordinate system. Any specifier within a COMMAND statement is not modal; it does not affect the host
addressing specifications or the modal addressing of any program, including its own.
Any data or error response for the command given inside the quote marks is directed to the port specified
by the letter at the end of COMMAND:
COMMAND provides no response to any port
COMMANDS provides a response to the main serial port
COMMANDP provides a response to the parallel bus port
COMMANDR provides a response to the DPRAM ASCII response buffer
COMMANDA provides a response to the Option 9T auxiliary serial port
If I62=0, Turbo PMAC issues a carriage-return (<CR>) character automatically at the end of any data
response to the command. If I62=1, Turbo PMAC does not issue a <CR> character at the end of the data
response; a SEND^M must be used to issue an <CR> in this case.
Each PLC program has its own addressing mode for both motors and coordinate systems, independent of
each other and independent of the host addressing modes. These are controlled by the PLC program
ADDRESS command. This modal addressing affects commands issued from within a PLC program that
do not have motor or coordinate-system specifiers. At power-up/reset, all PLC programs are addressing
Motor 1 and C.S.1.
There is no modal ADDRESS command in motion programs. Any motor-specific or coordinate-system-
specific command issued from within a motion program without a specifier is automatically addressed to
Motor 1 or C.S.1, respectively.
Commands issued from within a program are placed in the command queue, to be parsed and acted upon
at the appropriate time by Turbo PMAC’s command interpreter, which operates in background, between
other background tasks. If issued from a motion program, the command will not be interpreted before the
next move or dwell command in the motion program is calculated. If issued from a PLC program, the
command will not be interpreted before the end of the current scan of the PLC. This delay can make the
action appear to execute out of sequence.
Because of the queuing of commands and the fact that command interpretation is a lower priority than
command issuing, it is possible to overflow the queue. If there is no room for a new command, program
execution is temporarily halted until the new command can be placed on the queue.
Also, commands that generate a response to the host (including errors if I6 is not equal to 2) potentially
can fill up the response queue if there is no host or the host is not prepared to read the responses. This
will temporarily halt program execution until the response queue is emptied. In standalone applications,
it is a good idea to set I1 to 1, disabling the serial handshake, so any responses can be sent out the serial
port (the default response port) at any time, even if there is no host to receive it.
In a PLC program, it is a good idea to have at least one of the conditions that caused the command
issuance to occur set false immediately. This will prevent the same command from being issued again on
succeeding scans of the PLC, overflowing the command and/or response queues. Typically in a motion
program, the time between moves prevents this overflow unless there are a lot of commands and the
moves take a very short time.
Turbo PMAC will not issue an acknowledging character (<ACK> or <LF>) to a valid command issued
from an internal program. It will issue a <BELL> character for an invalid command issued from a
program unless I6 is set to 2. It is a good idea to have I6 not set to 2 in early development so that it will
be known when Turbo PMAC has rejected such a command. Setting I6 to 2 in the actual application can
prevent program hang-up from a full response queue, or from disturbing the normal host communications
protocol.
Many otherwise valid commands will be rejected when issued from a motion program. For instance, any
motor cannot jogged in the coordinate system executing the program because all these motors are
considered to be running in the program, even if the program is not requesting a move of the motors at
that time.
When issuing commands from a program, be sure to include all the necessary syntax (motor and/or
coordinate system specifiers) in the command statement or use the ADDRESS command. For example,
use CMD"#4HM" and CMD"&1A" instead of CMD"HM" and CMD"A". Otherwise, motor and coordinate
system commands will be sent to the most recently addressed motor and coordinate system which may
not always be intended.
Examples:
COMMAND"#1J+"
CMD"#4HM"
CMD"&1B5R"
CMDP"P1"
47.5
ADDRESS#3
COMMAND"J-"
IF(M40=1 AND M41=1)
CMD"&4R"
M41=0
ENDIF
See Also:
Addressing Modes, On-Line Commands (Talking t Turbo PMAC)
I-variables I1, I3, I6.
Program commands ADDRESS, COMMAND^{letter}
Writing A PLC Program
COMMANDx^{letter}
Function: Control-Character Command Issuance from Internal Program
Type: Motion program (PROG or ROT), PLC program
Syntax: COMMAND^{letter}
CMD^{letter}
COMMANDS^{letter}
CMDS^{letter}
COMMANDP^{letter}
CMDP^{letter}
COMMANDR^{letter}
CMDR^{letter}
COMMANDA^{letter}
CMDA^{letter}
where:
{letter} is a letter character from A to Z (upper or lowercase) representing the corresponding
control character
This statement causes the motion program to issue a control-character command as if it came from the
host, except for the direction of the response. All control-character commands are global, so there are no
addressing concerns.
Any data or error response for the control-character command is directed to the port specified by the letter
at the end of COMMAND:
COMMAND provides no response to any port
COMMANDS provides a response to the main serial port
COMMANDP provides a response to the parallel bus port
COMMANDR provides a response to the DPRAM ASCII response buffer
COMMANDA provides a response to the Option 9T auxiliary serial port
Note:
Do not put the up-arrow character and the letter in quotes (do not use
COMMANDx"^A") or Turbo PMAC will attempt to issue a command with the two
non-control characters, ^ and A in this example, instead of the control character.
Commands issued from within a program are placed in the command queue, to be parsed and acted upon
at the appropriate time by Turbo PMAC’ command interpreter, which operates in background, between
other background tasks. If issued from a motion program, the command will not be interpreted before the
next move or dwell command in the motion program is calculated. If issued from a PLC program, the
command will not be interpreted before the end of the current scan of the PLC. This delay can make the
action appear to execute out of sequence.
Because of the queuing of commands and the fact that command interpretation is a lower priority than
command issuing, it is possible to overflow the queue. If there is no room for a new command, program
execution is temporarily halted until the new command can be placed on the queue.
Also, commands that generate a response to the host (including errors if I6 is not equal to 2) potentially
can fill up the response queue if there is no host or the host is not prepared to read the responses. This
will temporarily halt program execution until the response queue is emptied. In standalone applications,
it is a good idea to set I1 to 1, disabling the serial handshake, so any responses can be sent out the serial
port (the default response port) at any time, even if there is no host to receive it.
In a PLC program, it is a good idea to have at least one of the conditions that caused the command
issuance to occur set false immediately. This will prevent the same command from being issued again on
succeeding scans of the PLC, overflowing the command and/or response queues. Typically in a motion
program, the time between moves prevents this overflow unless there are a lot of commands and the
moves take a very short time.
Turbo PMAC will not issue an acknowledging character (<ACK> or <LF>) to a valid command issued
from a program. It will issue a <BELL> character for an invalid command issued from a program unless
I6 is set to 2. It is a good idea to have I6 not set to 2 in early development so it is known when Turbo
PMAC has rejected such a command. Setting I6 to 2 in the actual application can prevent program hang-
up from a full response queue, or from disturbing the normal host communications protocol.
Examples:
CMD^D would disable all PLC programs (equivalent to issuing a <CONTROL-D> from the host).
CMD^K would kill (disable) all motors on Turbo PMAC
CMD^A would stop all programs and moves on Turbo PMAC, also closing any loops that were open.
CMDS^P would cause Turbo PMAC to report the positions for 8 motors to the main serial port
See Also:
I-variables I1, I6
On-line commands <CONTROL-A> to <CONTROL-Z>
Program command COMMANDx"{command}"
CREAD
Function: Read latest computed axis destination coordinates
Type: Motion program (PROG and ROT)
Syntax: CREAD [({axis}[,{axis}…])]
where:
{axis} is a character (X, Y, Z, A, B, C, U, V, W) specifying which axis’ destination coordinate
is to be read
The CREAD (Coordinate READ) command causes Turbo PMAC to read the most recently computed
move-destination coordinates for all axes or the specified axes in the coordinate system running the
program, and place these values in particular Q-variables for the coordinate system. From these Q-
variables, these values can then be synchronously assigned to floating-point M-variables, so these M-
variables will hold the axis destination values when the move is actually executing. This facilitates the
calculation of features such as “distance-to-go” reporting.
If no axis list follows CREAD, all nine axis destination values are placed in Q-variables. If there is an axis
list in the command, only the values for the specified axes are placed in Q-variables
The following table shows which Q-variable for the coordinate system is used for each axis destination
value:
Axis Q-Variable Axis Q-Variable Axis Q-Variable
A Q91 U Q94 X Q97
B Q92 V Q95 Y Q98
C Q93 W Q96 Z Q99
Examples:
; Without subroutine
A27 B35 CREAD(A,B) M91==Q91 M92==Q92
See Also:
Program commands CALL{data}, G{data}, M{data}, T{data}, RETURN
DELAY{data}
Function: Delay for Specified Time
Type: Motion program
Syntax: DELAY{data}
DLY{data}
where:
{data} is a floating-point constant or expression, specifying the delay time in milliseconds
This command causes Turbo PMAC to keep the command positions of all axes in the coordinate system
constant (no movement) for the time specified in {data}.
There are three differences between DELAY and DWELL. First, if DELAY comes after a blended move,
the TA deceleration time from the move occurs within the Delay time, not before it. Second, the actual
time for Delay does varies with a changing time base (current % value, from whatever source), whereas
DWELL always uses the fixed time base (%100). Third, Turbo PMAC precomputes upcoming moves
(and the lines preceding them) during a DELAY, but it does not do so during a DWELL.
A DELAY command is equivalent to a zero-distance move of the time specified in milliseconds. As for a
move, if the specified Delay time is less than the acceleration time currently in force (TA or 2*TS), the
delay will be for the acceleration time, not the specified Delay time.
Examples:
DELAY750
DELAY(Q1+100)
See Also:
Time-Base Control (Synchronizing Turbo PMAC to External Events)
I-variables I10, Isx87, Isx88
On-line command %{constant}
Program commands DWELL, TA, TS
DISABLE PLC {constant}[,{constant}...]
Function: Disable PLC Programs
Type: Motion program (PROG or ROT), PLC program
Syntax: DISABLE PLC {constant}[,{constant}...]
DISABLE PLC {constant}[..{constant}]
DIS PLC {constant}[,{constant}...]
DIS PLC {constant}[..{constant}]
where:
each {constant} is an integer from 0 to 31 representing the PLC number
This command causes Turbo PMAC to disable (stop executing) the specified uncompiled PLC program
or programs. Execution can subsequently be resumed at the top of the program with the ENABLE PLC
command. To restart execution at the stopped point, execution should be stopped with the PAUSE PLC
command and restarted with the RESUME PLC command
Execution of a PLC program can only be disabled at the end of a scan, which is either the end of the
program, or after executing an ENDWHILE statement in the program. (A PLC program can be paused in
the middle of a scan, however.)
PLC programs are specified by number, and may be specified in a command singularly, in a list
(separated by commas), or in a range of consecutively numbered programs.
If no buffer is open when this command is sent to PMAC, it will be executed immediately as an on-line
command.
Examples:
DISABLE PLC 1
DISABLE PLC 4,5
DISABLE PLC 7..20
DIS PLC 3,8,11
DIS PLC 0..31
See Also:
I-variable I5
On-line commands ENABLE PLC, DISABLE PLC, ENABLE PLCC, DISABLE PLCC, PAUSE PLC,
RESUME PLC, <CONTROL-D>
Program command ENABLE PLC, DISABLE PLCC, ENABLE PLCC, PAUSE PLC, RESUME PLC
DISABLE PLCC {constant}[,{constant}...]
Function: Disable Compiled PLC Programs
Type: Motion program (PROG or ROT), PLC program (uncompiled or compiled),
except for PLC 0 and PLCC 0
Syntax: DISABLE PLCC {constant}[,{constant}...]
DISABLE PLCC {constant}[..{constant}]
DIS PLCC {constant}[,{constant}...]
DIS PLCC {constant}[..{constant}]
where:
each {constant} is an integer from 0 to 31 representing the compiled PLC number
This command disables the operation of the specified compiled PLC (PLCC) programs. The programs
are specified by number, and can be used singly, in a list separated by commas, or in a continuous range.
Note:
This command should not be used in a foreground PLC – either uncompiled PLC 0
or compiled PLCC 0 – as its operation cannot be guaranteed in these programs.
I-variable I5 is a separate master control of PLC program operation. Think of the two bits of I5 as two
master circuit breakers for a house, and the individual PLC and PLCC enable/disable bits as separate light
switches within the house. Both the master breaker and the switch must be on for the PLC to operate.
The breakers and the switches can be operated independently without affecting the setting of the others.
Examples:
DISABLE PLCC 1
DISABLE PLCC 4,5
DISABLE PLCC 7..20
DIS PLCC 3,8,11
DIS PLC 0..31
See Also:
I-variable I5
On-line commands ENABLE PLC, DISABLE PLC, ENABLE PLCC, DISABLE PLCC, <CONTROL-D>
Program command ENABLE PLC, DISABLE PLC, ENABLE PLCC
See Also:
Display Port (Connecting Turbo PMAC to the Machine);
Accessory 12 (Basic Specifications)
Program commands DISPLAY"{message}", COMMAND"{command}"
DWELL
Function: Dwell for Specified Time
Type: Motion program (PROG and ROT)
Syntax: DWELL{data}
DWE{data}
where:
{data} is a non-negative floating point constant or expression representing the dwell time in
milliseconds
This command causes the card to keep the commanded positions of all axes in the coordinate system
constant for the time specified in {data}. The maximum dwell time is 8,388,607 msec (about 2 hours
and 20 minutes). If a longer time is specified in the command, the actual dwell time will be limited to this
amount.
There are three differences between DWELL and the similar DELAY command. First, if the previous servo
command was a blended move, there will be a TA time deceleration to a stop before the dwell time starts.
Second, DWELL is not sensitive to a varying time base – it always operates in real time (as defined by
I10). Third, Turbo PMAC does not pre-compute upcoming moves (and the program lines before them
during the DWELL; it waits until after it is done to start further calculations, which it performs in the time
specified by I11 or Ixx12.
Use of any DWELL command, even a DWELL0, while in external time base will cause a loss of
synchronicity with the master signal.
Examples:
DWELL250
DWELL(P1+P2)
DWE0
See Also:
Dwell and Delay (Writing and Executing Motion Programs)
I-variables I10, I11, I12.
Program command DELAY
ELSE
Function: Start False Condition Branch
Type: Motion program (PROG only), PLC program
Syntax: ELSE (Motion or PLC Program)
ELSE {action} (Motion Program only)
where:
{action} is a program command
This statement must be matched with an IF statement (ELSE requires a preceding IF, but IF does not
require a following ELSE). It follows the statements executed upon a true IF condition. It is followed
by the statements to be executed upon a false IF condition.
Note:
With nested IF branches, be careful to match the ELSE statements to the proper
IF statement. In a motion program, it is possible to have a single-line IF
statement (IF({condition}) {action}). An ELSE statement on the next
program line is matched to this IF statement automatically, even if wanting to
match a previous IF statement. Put a non-ELSE statement in between to make the
next ELSE statement match a previous IF statement.
ELSE lines can take two forms (only the first of which is valid in a PLC program):
With no statement following on that line, all subsequent statements down to the next ENDIF statement
will be executed provided that the preceding IF condition is false.
ELSE
{statement}
[{statement}
...]
ENDIF
With a statement or statements following on that line, the single statement will be executed provided that
the preceding IF condition is false. No ENDIF statement should be used in this case
ELSE {statement} [{statement}...]
Note:
(This single-line ELSE branch form is valid only in motion programs. If this is
tried in a PLC program, Turbo PMAC will put the statements on the next program
line and expect an ENDIF to close the branch. The logic will not be as expected.)
Examples:
This first example has multi-line true and false branches. It could be used in either a motion program or a
PLC program.
IF (M11=1)
P1=17
P2=13
ELSE
P1=13
P2=17
ENDIF
This second example has a multi-line true branch, and a single-line false branch. This structure could
only be used in a motion program.
IF (M11=0)
X(P1)
DWELL 1000
ELSE DWELL 500
This example has a single-line true branch, and a multi-line false branch. This structure could be used
only in a motion program.
IF (SIN(P1)>0.5) Y(1000*SIN(P1))
ELSE
P1=P1+5
Y(1100*SIN(P1))
ENDIF
This example has single-line true and false branches. This structure could be used only in a motion
program.
IF (P1 !< 5) X10
ELSE X-10
See Also:
Program commands IF, ENDIF.
ENABLE PLC
Function: Enable PLC Buffers
Type: Motion program (PROG and ROT), PLC program
Syntax: ENABLE PLC {constant}[,{constant}...]
ENABLE PLC {constant}[..{constant}]
ENA PLC {constant}[,{constant}...]
ENA PLC {constant}[..{constant}]
where:
each {constant} is an integer from 0 to 31 representing the PLC number
This command causes Turbo PMAC to enable (start executing) the specified uncompiled PLC program or
programs at the top of the program. Execution of the PLC program may have been stopped with the
DISABLE PLC, PAUSE PLC, or OPEN PLC command.
PLC programs are specified by number, and may be used singularly in this command, in a list (separated
by commas), or in a range of consecutively numbered programs.
If no buffer is open when this command is sent to PMAC, it will be executed immediately as an on-line
command.
Examples:
ENABLE PLC 0
ENABLE PLC 1,2,5
ENABLE PLC 1..16
ENA PLC 7
See Also:
I-variable I5
On-line commands ENABLE PLC, DISABLE PLC, <CONTROL-D>
Program command DISABLE PLC, PAUSE PLC, RESUME PLC
ENABLE PLCC
Function: Enable Compiled PLC Programs
Type: Motion program (PROG and ROT), PLC program (uncompiled and compiled)
Syntax: ENABLE PLCC {constant}[,{constant}...]
ENABLE PLCC {constant}[..{constant}]
ENA PLCC {constant}[,{constant}...]
ENA PLCC {constant}[..{constant}]
where:
each {constant} is an integer from 0 to 31 representing the compiled PLC number
This command enables the operation of the specified compiled PLC (PLCC) buffers, provided I5 is set
properly to allow their operation. The programs are specified by number and can be used singly, in a list
separated by commas, or in a continuous range.
I-variable I5 is a separate master control of PLC program operation. Think of the two bits of I5 as two
master circuit breakers for a house, and the individual PLC and PLCC enable/disable bits as separate light
switches within the house. Both the master breaker and the switch must be on for the PLC to operate.
The breakers and the switches can be operated independently without affecting the setting of the others.
Examples:
ENABLE PLCC 0
In the execution of a PLC program, when an ENDWHILE statement is encountered, that scan of the PLC
is ended, and Turbo PMAC goes onto other tasks (communications, other PLCs). The next scan of this
PLC will start at the matching WHILE statement.
In the execution of a motion program, if Turbo PMAC finds two jumps backward (toward the top) in the
program while looking for the next move command, Turbo PMAC will pause execution of the program
and not try to blend the moves together. It will go on to other tasks and resume execution of the motion
program on a later scan. Two statements can cause such a jump back: ENDWHILE and GOTO (RETURN
does not count).
The pertinent result is that Turbo PMAC will not blend moves when it hits two ENDWHILE statements
(or the same ENDWHILE twice) between execution of move commands.
Examples:
WHILE (Q10<10)
Q10=Q10+1
ENDWHILE
See Also:
Program commands WHILE, ENDIF
F{data}
Function: Set Move Feedrate (Velocity)
Type: Motion program (PROG and ROT)
Syntax: F{data}
where:
{data} is a positive floating-point constant or expression representing the vector velocity in user
length units per user time units
This statement sets the commanded velocity for upcoming LINEAR and CIRCLE mode blended moves.
It will be ignored in other types of moves (SPLINE, PVT, and RAPID). It overrides any previous TM or
F statement, and is overridden by any following TM or F statement.
The units of velocity specified in an F command are scaled position units (as set by the axis definition
statements) per time unit (defined by the Isx90 Feedrate Time Unit I-variable for the coordinate system).
The velocity specified here is the vector velocity of all of the vector-feedrate axes of the coordinate
system. That is, the move time is calculated as the vector distance of the feedrate axes (square root of the
sum of the squares of the individual axes), divided by the feedrate value specified here. Any non-feedrate
axes commanded to move on the same move-command line will move at the speed necessary to finish in
this same amount of time.
Axes are designated as vector-feedrate axes with the FRAX command. If no FRAX command is used, the
default feedrate axes are the X, Y, and Z axes. Any axis involved in circular interpolation is
automatically a feedrate axis, regardless of whether it was specified in the latest FRAX command. In
multi-axis systems, feedrate specification of moves is useful only for systems with Cartesian geometries,
for which these moves give a constant velocity in the plane or in 3D space, regardless of movement
direction.
There are several cases in which Turbo PMAC will not use the feedrate commanded with the F statement:
If the specified feedrate causes a move time of over 223 msec (about 2 hours 20 minutes) to be
calculated, the move will be executed in 223 msec, at a higher speed than what was programmed.
If the feedrate programmed with the F statement exceeds the Isx98 maximum feedrate parameter for
the coordinate system, the Isx98 value will be used instead.
If the feedrate programmed with the F statement causes any motor in the coordinate system to exceed
its Ixx16 velocity limit (when active), all axes will be slowed so that no motor exceeds its limit.
If the vector distance of a feedrate-specified move is so short that the computed move time (vector
distance divided by feedrate) would be less than the acceleration time currently in force (TA or 2*TS
or the time set by the Ixx17 limit when active), the move will take the full acceleration time instead,
and the axes will move more slowly than specified by the F command. If the acceleration time is 0,
the minimum permitted move time is 0.5 msec.
If vector-feedrate axes and non-feedrate axes are commanded together on the same program line, and
the time for any non-feedrate axis, computed as the axis distance divided by the alternate feedrate
parameter Isx86, is greater than the move time calculated for the vector-feedrate axes, then Turbo
PMAC will use this longer time for the move, resulting in a lower vector feedrate.
If only non-feedrate axes are commanded to move in a feedrate-specified move, Turbo PMAC will
compute the move time as the longest distance commanded for any axis divided by the Isx86 alternate
feedrate parameter. If Isx86 is set to zero, it will compute the move time as the longest distance
divided by the programmed feedrate. Use of the Isx86 parameter for all moves can be forced by
using the NOFRAX command, which makes all axes non-feedrate axes.
If the % override value for the coordinate system is at other than %100 when the move is executed,
the move will not execute at the specified speed. The actual speed varies in direct proportion to the %
value.
Examples:
F100
F31.25
F(Q10)
F(SIN(P8*P9))
See Also:
I-variables Isx86, Isx87, Isx88, Isx89, Isx90, Isx98
On-line commands #{constant}->{axis definition}, FRAX
Program commands FRAX, LINEAR, NOFRAX, CIRCLE, TM, TA, TS
FRAX
Function: Specify Feedrate Axes
Type: Motion program (PROG and ROT)
Syntax: FRAX [({axis}[,{axis}...])]
where:
{axis} is a character (X, Y, Z, A, B, C, U, V, W) specifying which axis is to be used in the vector
feedrate calculations.
This command specifies which axes are to be involved in the vector-feedrate (velocity) calculations for
upcoming feedrate-specified (F) moves. Turbo PMAC calculates the time for these moves as the vector
distance (square root of the sum of the squares of the axis distances) of all the feedrate axes divided by the
feedrate. Any non-feedrate axes commanded on the same line will complete in the same amount of time,
moving at whatever speed is necessary to cover the distance in that time.
Vector feedrate has obvious geometrical meaning only in a Cartesian system, for which it results in
constant tool speed regardless of direction, but it is possible to specify for non-Cartesian systems and for
more than three axes.
Note:
In a feedrate-specified move, if the move time for any non-feedrate axis, computed
as axis distance divided by Isx86, is greater than the move time for the feedrate
axes, computed as the vector distance divided by the feedrate, Turbo PMAC will
use the move time for the non-feedrate axis instead.
The FRAX command without arguments causes all axes in the coordinate system to be feedrate axes in
subsequent move commands. The FRAX command with arguments causes the specified axes to be
feedrate axes, and all axes not specified to be non-feedrate axes, in subsequent move commands.
If no motion program buffer is open when this command is sent to Turbo PMAC, it will be executed as an
on-line coordinate system command.
Examples:
For a three-axis cartesian system scaled in millimeters:
FRAX(X,Y)
INC
X30 Y40 Z10 F100
2 2
Vector distance is SQRT(30 + 40 ) = 50 mm. At a speed of 100 mm/sec, move time (unblended) is 0.5
sec. X-axis speed is 30/0.5 = 60 mm/sec; Y-axis speed is 40/0.5 = 80 mm/sec; Z-axis speed is 10/0.5 =
20 mm/sec.
Z20
2 2
Vector distance is SQRT(0 +0 ) = 0 mm. With Isx86 = 50 (mm/sec), Z-axis speed is 50 mm/sec, move
time (unblended) is 0.4 sec.
FRAX(X,Y,Z)
INC
X-30 Y-40 Z120 F65
2 2 2
Vector distance is SQRT(-30 + -40 +120 ) = 130 mm. Move time is 130/65 = 2.0 sec. X-axis speed is
30/2.0 = 15 mm/sec; Y-axis speed is 40/2.0 = 20 mm/sec; Z-axis speed is 120/2.0 = 60 mm/sec.
See Also:
I-variables Isx86 Isx87, Isx88, Isx89, Isx90
On-line command FRAX, NOFRAX
Program commands F, NOFRAX, LINEAR, CIRCLE, {axis}{data}.
G{data}
Function: Preparatory Code (G-Code)
Type: Motion program
Syntax: G{data}
where:
{data} is a floating-point constant or expression in the range 0.000 to 999.999, specifying the
program number and the line label to jump to
Turbo PMAC interprets this statement as a CALL 10n0.({data’}*1000) command, where n is the
hundreds’digit of {data}, and {data’} is the value of {data} without the hundred’s digit (modulo
100 in mathematical terms). That is, this statement causes a jump (with return) to motion program 10n0,
and the specified line label. (Usually, programs 10n0 are used to implement the preparatory codes as the
system designer sees fit.) The value of {data’} can be from 0.0 to 99.999, corresponding to line labels
N0 to N99999.
This structure permits the implementation of customizable G-Code routines for machine-tool style
applications by the writing of subroutines in motion programs 10n0. Arguments can be passed to these
subroutines by following the G-Code with one or more sets of {letter}{data}, as in CALL and
READ statements.
Most users will have G-codes only in the range 0-99, which permits the use of PROG 1000 only and
allows {data’} to equal {data} for direct specification of the line label.
Example:
G01 jumps to N1000 of PROG 1000
G12 jumps to N12000 of PROG 1000
G115 jumps to N15000 of PROG 1010
See Also:
Program commands CALL{data}, D{data}, M{data}, T{data}, RETURN
GOSUB
Function: Unconditional Jump With Return
Type: Motion program (PROG only)
Syntax: GOSUB{data}
where:
{data} is a constant or expression representing the line label to jump to
This command causes the motion program execution to jump to the line label (N or O) of the same motion
program specified in {data}, with a jump back to the commands immediately following the GOSUB
upon encountering the next RETURN command.
If {data} is a constant, the path to the subroutine will have been linked before program run time, so the
jump is very quick. If {data} is a variable expression, it must be evaluated at run time, and the
appropriate label then searched for. The search starts downward in the program to the end, then continues
(if necessary) from the top of the program down.
A variable GOSUB command permits the equivalent structure to the CASE statement found in many high-
level languages.
If the specified line label is not found, the GOSUB command will be ignored, and the program will
continue as if the command had not occurred.
The CALL command is similar, except that it can jump to another motion program.
Examples:
GOSUB300 jumps to N300 of this program, to jump back on RETURN
GOSUB8743 jumps to N8743 of this program, to jump back on RETURN
GOSUB(P17) jumps to the line label of this program whose number matches the current value of P17, to jump back
on RETURN
See Also:
Writing and Executing Motion Programs
Program commands CALL, GOTO, N, O, RETURN
GOTO
Function: Unconditional Jump without Return
Type: Motion program (PROG only)
Syntax: GOTO{data}
where:
{data} is an integer constant or expression with a value from 0 to 99,999.
This command causes the motion program execution to jump to the line label (N or O) specified in
{data}, with no jump back.
If {data} is a constant, the path to the label will have been linked before program run time, so the jump
is very quick. If {data} is a variable expression, it must be evaluated at run time, and the appropriate
label then searched for. The search starts downward in the program to the end, and then continues (if
necessary) from the top of the program down.
A variable GOTO command permits the equivalent structure to the CASE statement found in many high-
level languages (see Examples, below).
If the specified line label is not found, the program will stop, and the coordinate system’s Run-Time-Error
bit will be set.
Note:
Modern philosophies of the proper structuring of computer code strongly
discourage the use of GOTO, because of its tendency to make code undecipherable.
Examples:
GOTO750
GOTO35000
GOTO1
GOTO(50+P1)
N51 P10=50*SIN(P11)
GOTO60
N52 P10=50*COS(P11)
GOTO60
N53 P10=50*TAN(P11)
N60 X(P10)
See Also:
Writing and Executing Motion Programs;
Program commands CALL, GOSUB, N, O.
HOME
Function: Programmed Homing
Type: Motion program
Syntax: HOME {constant} [,{constant}...]
HOME {constant}..{constant} [,{constant}..{constant}...]
HM {constant} [,{constant}...]
HM {constant}..{constant} [,{constant}..{constant}...]
where:
{constant} is an integer from 1 to 32 representing a motor number.
This causes the specified motors to go through their homing search cycles. Note that the motors must be
specified directly by number, not the matching axis letters. Specify which motors are to be homed. All
motors specified in a single HOME command (e.g. HOME1,2) will start their homing cycles
simultaneously; to home some motors sequentially, specify them in consecutive commands (e.g. HOME1
HOME2), even if on the same line.
Any previous moves will come to a stop before the home moves start. No other program statement will
be executed until all specified motors have finished homing. Homing direction, speed, acceleration, etc.
are determined by motor I-variables. If a motor is specified that is not in the coordinate system running
the program, the command or portion of the command will be ignored, but an error will not be generated.
The speed of the home search move is determined by Ixx23. If Ixx23=0 then the programmed home
command for that axis is ignored.
Note:
Unlike an on-line homing command, the motor numbers in a program homing
command are specified after the word HOME itself, not before. In addition, an on-
line homing command simply starts the homing search – it does not give any
indication when the search is complete; but a program homing command
automatically recognizes the end of the search, and then continues on in the
program. A PLC program can only issue an on-line HOME command.
Examples:
HOME1 ;These are motion program commands
HM1,2,3
HOME1..3,5..7
HM1..8
#1HOME ;These are on-line commands
#1HM,#2HM,#3HM
See Also:
Homing-Search Moves (Basic Motor Moves)
On-line motor commands HOME, HOMEZ
Program command HOMEZ
HOMEZ
Function: Programmed Zero-Move Homing
Type: Motion program
Syntax: HOMEZ {constant} [,{constant}...]
HOMEZ {constant}..{constant} [,{constant}..{constant}...]
HMZ {constant} [,{constant}...]
HMZ {constant}..{constant} [,{constant}..{constant}...]
where:
{constant} is an integer from 1 to 32 representing a motor number.
This commands causes the specified motors to go through pseudo-homing search cycles. In this
operation, the present commanded position of the motor is made the zero position for the motor and the
new commanded position for the motor.
If there is following error and/or an axis definition offset at the time of the HOMEZ command, the reported
position after the command will be equal to the negative of the following error plus the axis definition
offset.
Note that the motors must be specified directly by number, not the matching axis letters. Specify which
motors are to be homed. All motors specified in a single HOMEZ command (e.g. HOMEZ1,2) will home
simultaneously.
Note:
Unlike an on-line homing command, the motor numbers in a program homing
command are specified after the word HOMEZ itself, not before.
Examples:
HOMEZ1 ;These are motion program commands
HMZ1,2,3
HOMEZ1..3,5..7
HMZ1..8
#1HOMEZ ;These are on-line commands
#1HMZ,#2HMZ,#3HMZ
See Also:
Homing-Search Moves (Basic Motor Moves)
On-line motor command HOME, HOMEZ
Program command HOME
I{data}
Function: I-Vector Specification for Circular Moves or Normal Vectors
Type: Motion program (PROG or ROT)
Syntax: I{data}
where:
{data} is a floating-point constant or expression representing the magnitude of the I-component of
the vector in scaled user axis units.
In circular moves, this specifies the component of the vector to the arc center that is parallel to the X-axis.
The starting point of the vector is either the move start point (for INC (R) mode – default) or the XYZ-
origin (for ABS (R) mode).
In a NORMAL command, this specifies the component of the normal vector to the plane of circular
interpolation and tool radius compensation that is parallel to the X-axis.
Examples:
X10 Y20 I5 J5
X(2*P1) I(P1)
I33.333 ; specifies a full circle whose center is 33.333 units in the
; positive X-direction from the start and end point
NORMAL I-1 ; specifies a vector normal to the YZ plane
See Also:
Circular Interpolation, Tool Radius Compensation (Writing and Executing Motion Programs)
On-line command I{constant}
Program Commands {axis}{data}{vector}{data}, ABS, INC, NORMAL, J, K,
I{constant}={expression}
I{data}={expression}
Function: Set I-Variable Value
Type: Motion program (PROG and ROT), PLC Program
Syntax: I{data}={expression}
where:
{data} is a constant, or an expression in parentheses, for an integer value from 0 to 8191
representing the I-variable number;
{expression) represents the value to be assigned to the specified I-variable.
This command sets the value of the specified I-variable to that of the expression on the right side of the
equals sign. The assignment is done as the line is processed, which in a motion program is usually one or
two moves ahead of the move actually executing at the time (because of the need to calculate ahead in the
program).
Note:
To have the assignment of the I-variable value to be synchronous with the
beginning of the next move in the program, assign an M-variable to the register of
the I-variable and use a synchronous M-variable assignment statement
(M{data}=={expression}).
Examples:
I130=30000
I902=1
I131=P131+1000
See Also:
How Turbo PMAC Executes a Motion Program (Writing and Executing Motion Programs)
On-line command I{constant}={expression}
Program commands M{data}={expression), P{data}={expression},
Q{data}={expression}, M{data}=={expression}
IDIS{constant}
Function: Incremental displacement of X, Y, and Z axes
Type: Motion program (PROG and ROT)
Syntax: IDIS{constant}
where:
{constant} is an integer representing the number of the first of three consecutive Q-variables to
be used in the displacement vector
This command adds to the offset values of the currently selected (with TSEL) transformation matrix for
the coordinate system the values contained in the three Q-variables starting with the specified one. This
has the effect of renaming the current commanded X, Y, and Z axis positions (from the latest
programmed move) by adding the values of these variables (Xnew=Xold+Q{constant},
Ynew=Yold+Q({constant}+1), Znew=Zold+Q({constant}+2)).
This command does not cause any movement of any axes; it simply renames the present positions.
This command is similar to a PSET command, except that IDIS is incremental and does not force a stop
between moves, as PSET does.
Examples:
X0 Y0 Z0
Q20=7.5
Q21=12.5
Q22=20
IDIS 20 ; This makes the current position X7.5, Y12.5, Z20
IDIS 20 ; This makes the current position X15 Y25 Z40
See Also:
Axis Matrix Transformations (Writing and Executing Motion Programs)
On-line command DEFINE TBUF
Program commands TSEL, ADIS, AROT, IROT, TINIT
IF ({condition})
Function: Conditional branch
Type: Motion and PLC program
Syntax: IF ({condition}) (Valid in fixed motion (PROG) or PLC program only)
IF ({condition}) {action} [{action}...](Valid in rotary or
fixed motion program only)
where:
{condition} consists of one or more sets of {expression} {comparator}
{expression}, joined by logical operators AND or OR.
{action} is a program command
This command allows conditional branching in the program.
With an action statement or statements following on that line, it will execute those statements provided
the condition is true (this syntax is valid in motion programs only). If the condition is false, it will not
execute those statements; it will only execute any statements on a false condition if the line immediately
following begins with ELSE. If the next line does not begin with ELSE, there is an implied ENDIF at the
end of the line.
Note:
When there is an ELSE statement on the motion-program line immediately
following an IF statement with actions on the same line, that ELSE statement is
automatically matched to this IF statement, not to any preceding IF statements
under which this IF statement may be nested.
With no statement following on that line, if the condition is true, Turbo PMAC will execute all
subsequent statements on following lines down to the next ENDIF or ELSE statement (this syntax is valid
in motion and PLC programs). If the condition is false, it will skip to the ENDIF or ELSE statement and
continue execution there.
In a rotary motion program, only the single-line version of the IF statement is permitted. No ELSE or
ENDIF statements are allowed.
In a PLC program, compound conditions can be extended onto multiple program lines with subsequent
AND and OR statements.
There is no limit on nesting of IF conditions and WHILE loops (other than total buffer size) in fixed
motion and PLC programs. No nesting is allowed in rotary motion programs.
Examples:
IF (P1>10) M1=1
IF (M11=0 AND M12!=0) M2=1 M3=1
IF (M1=0) P1=P1-1
ELSE P1=P1+1
IF (M11=0)
P1=1000*SIN(P5)
X(P1)
ENDIF
IF (P1<0 OR P2!<0)
AND (P50=1)
X(P1)
DWELL 1000
ELSE
X(P1*2)
DWELL 2000
ENDIF
See Also:
Conditions (Program Computational Features)
Program commands ELSE, ENDIF, WHILE, AND, OR
INC
Function: Incremental Move Mode
Type: Motion program
Syntax: INC [({axis}[,{axis}...])]
where:
{axis} is a letter specifying a motion axis (X, Y, Z, A, B, C, U, V, W), or the letter R specifying the
arc center radial vector.
The INC command without arguments causes all subsequent command positions in motion commands for
all axes in the coordinate system running the motion program to be treated as incremental distances from
the latest command point. This is known as incremental mode, as opposed to the default absolute mode.
An INC statement with arguments causes the specified axes to be in incremental mode, and all others stay
the way they were before.
If R is specified as one of the axes, the I, J, and K terms of the circular move radius vector specification
will be specified in incremental form (i.e. as a vector from the move start point, not from the origin). An
INC command without any arguments does not affect this vector specification. The default radial vector
specification is incremental.
If no motion program buffer is open when this command is sent to Turbo PMAC, it will be executed as an
on-line coordinate system command.
Examples:
INC(A,B,C)
INC
INC(U)
INC(R)
See Also:
Circular Moves (Writing and Executing Motion Programs)
On-line commands ABS, INC
Program commands {axis}{data}, {axis}{data}{vector}{data}, ABS.
IROT{constant}
Function: Incremental rotation/scaling of X, Y, and Z axes
Type: Motion program (PROG and ROT)
Syntax: IROT{constant}
where:
{constant} is an integer representing the number of the first of nine consecutive Q-variables to be
used in the rotation/scaling matrix
This command multiplies the currently selected (with TSEL) transformation matrix for the coordinate
system by the rotation/scaling values contained in the nine Q-variables starting with the specified one.
This has the effect of renaming the current commanded X, Y, and Z axis positions (from the latest
programmed move) by multiplying the existing rotation/scaling matrix by the matrix containing these Q-
variables, adding angles of rotation and multiplying scale factors.
The rotation and scaling is done relative to the latest rotation and scaling of the XYZ coordinate system,
defined by the most recent AROT or IROT commands. The math performed is:
[New Rot Matrix] = [Old Rot Matrix] [Incremental Rot Matrix]
[Xrot Yrot Zrot]T = [New Rot Matrix] [Xbase Ybase Zbase]T
This command does not cause any movement of any axes; it simply renames the present positions.
Note:
When using this command to scale the coordinate system, do not use the radius
center specification for circle commands. The radius does not get scaled. Use the
I, J, K vector specification instead.
Examples:
Create a 3x3 matrix to rotate the XY plane by 30 degrees about the origin
Q40=COS(30) Q41=SIN(30) Q42=0
Q43=-SIN(30) Q44=COS(30) Q45=0
Q46=0 Q47=0 Q48=1
Examples:
X10 Z20 I5 K5
Z(2*P1) K(P1)
K33.333 ; Specifies a full circle whose center is 33.333 units in the
; positive Z-direction from the start and end point
NORMAL K-1 ; Specifies a vector normal to the XY plane
See Also:
Circular Interpolation, Tool Radius Compensation (Writing and Executing Motion Programs)
Motion Program Commands {axis}{data}{vector}{data}, ABS, INC, NORMAL, I, J.
LINEAR
Function: Blended Linear Interpolation Move Mode
Type: Motion program (PROG and ROT)
Syntax: LINEAR
LIN
The LINEAR command puts the program in blended linear move mode (this is the default condition on
power-up/reset). Subsequent move commands in the program will be processed according to the rules of
this mode. On each axis, the card attempts to reach a constant velocity that is determined by the most
recent feedrate (F) or move time (TM) command.
The LINEAR command takes the program out of any of the other move modes (CIRCLE, PVT, RAPID,
SPLINE). A command for any of these other move modes takes the program out of LINEAR mode.
Examples:
LINEAR ABS
CIRCLE1 X10 Y20 I5
LINEAR X10 Y0
OPEN PROG 1000 CLEAR
N1000 LINEAR RETURN
See Also:
Linear Blended Moves (Writing and Executing Motion Programs);
I-variables Isx87, Isx88, Isx89, Isx90;
Program commands CIRCLE, PVT, RAPID, SPLINE, TA, TS, TM, F, {axis}{data}.
LOCK{constant},P{constant}
Function: Check/set process locking bit
Type: Motion program/PLC program
Syntax: LOCK{constant},P{constant}
where:
the first {constant} is an integer from 0 to 7 representing the number of the locking bit;
the second {constant} is an integer from 0 to 8191 specifying the number of the P-variable used
to report the status of the locking bit.
The LOCK command permits the user to check and possibly take possession of one of the eight process
locking bits in Turbo PMAC. These locking bits can prevent conflicts between tasks of different
priorities attempting to manipulate the same register. On-line commands and PLCs 1-31 are background
tasks; motion programs and PLC 0 are higher-priority foreground tasks.
When the LOCK command is invoked, the P-variable specified in the command takes the value of the
locking bit immediately before the command is invoked. It takes a value of 0 if the locking bit was not
set before the command (meaning the process is available for this task); it takes a value of 1 if the locking
bit was set before the command (meaning the process is not available for this task).
The locking bit itself is always set to 1 at the end of a LOCK command. It will stay at 1 until cleared by
an UNLOCK command.
The status of locking bits 0-7 is reported as bits 4-11, respectively, of I4904.
If no motion program buffer or PLC program buffer is open when this command is issued, this command
will be executed immediately as an on-line command.
Example:
P10=1 ; Assume locked to start
WHILE(P10=1) ; Loop until unlocked
LOCK4,P10 ; Check status of locking bit 4
ENDWHILE
M1=M1^1 ; Invert Machine Output 1
UNLOCK4 ; Release process 4 for other tasks
M{data}
Function: Machine Code (M-Code)
Type: Motion program
Syntax: M{data}
where:
{data} is a floating-point constant or expression in the range 0.000 to 999.999, specifying the
program number and the line label to jump to
Turbo PMAC interprets this statement as a CALL 10n1.({data’}*1000) command, where n is the
hundreds’digit of {data}, and {data’} is the value of {data} without the hundred’s digit (modulo
100 in mathematical terms). That is, this statement causes a jump (with return) to motion program 10n1,
and the specified line label. (Usually programs 10n1 are used to implement the machine codes as the
system designer sees fit.) The value of {data’} can be from 0.0 to 99.999, corresponding to line labels
N0 to N99999.
This structure permits the implementation of customizable M-Code routines for machine-tool style
applications by the writing of subroutines in motion programs 10n1. Arguments can be passed to these
subroutines by following the M-Code with one or more sets of {letter}{data}, as in CALL and
READ statements.
Most users will have M-codes only in the range 0-99, which permits the use of PROG 1001 only, and
allows {data’} to equal {data} for direct specification of the line label.
Example:
M01 jumps to N1000 of PROG 1001
M12 jumps to N12000 of PROG 1001
M115 jumps to N15000 of PROG 1011
See Also:
Program commands CALL{data}, D{data}, M{data}, T{data}, RETURN
M{data}={expression}
Function: Set M-Variable Value
Type: Motion program (PROG and ROT)
Syntax: M{data}={expression}
where:
{data} is a constant, or an expression in parentheses, for an integer value from 0 to 8191
representing the M-variable number;
Examples:
X10
M1==1 ; Set Output 1 at start of actual blending to next move.
X20
M60==P1+P2
M(Q5000)==0
See Also:
How Turbo PMAC Executes a Motion Program, Synchronous Variable Assignment (Writing and
Executing Motion Programs)
Program Commands I{data}=, P{data}=, Q{data}=, M{data}=, M{data}&=, M{data}|=,
M{data}^=.
M{data}&={expression}
Function: M-Variable Synchronous And-Equals Assignment
Type: Motion program (PROG and ROT)
Syntax: M{data}&={expression}
where:
{data} is a constant, or an expression in parentheses, for an integer value from 0 to 8191
representing the M-variable number;
{expression} is a mathematical expression representing the value to be ANDed with this M-
variable.
This command is equivalent to M{data}=M{data}&{expression}, except that the bit-by-bit AND
and the assignment of the resulting value to the M-variable do not happen until the start of the actual
execution of the following motion command. The expression itself is evaluated when the program line is
encountered, as in a non-synchronous statement.
Note:
This command may not be used with any of the thumbwheel-multiplexer forms of
M-variables (TWB, TWD, TWR, or TWS), or with any of the double-word forms
(L, D, or F).
Remember that if this M-variable is used in further expressions before the next
move in the program is started, the value assigned in this statement will not be
received.
Examples:
M20&=$FE ; Mask out LSB of byte M20
M346&=2 ; Clear all bits except bit 1
M(P3+2)&=$55
See Also:
How Turbo PMAC Executes a Motion Program, Synchronous Variable Assignment (Writing and
Executing Motion Programs)
Program Commands M{data}=, M{data}==, M{data}|=, M{data}^=
M{data}|={expression}
Function: M Variable Synchronous “Or-Equals” Assignment
Type: Motion program (PROG and ROT)
Syntax: M{data}|={expression}
where:
{data} is a constant, or an expression in parentheses, for an integer value from 0 to 8191
representing the M-variable number;
See Also:
How Turbo PMAC Executes a Motion Program, Synchronous Variable Assignment (Writing and
Executing Motion Programs)
Program Commands M{data}=, M{data}==, M{data}&=, M{data}|=
MACROAUXREAD
Function: Read (copy) variable value from Turbo PMAC MACRO slave
Type: Uncompiled PLC 1 – 31 only
Syntax: MACROAUXREAD{node #},M{slave var},{variable}
MXR{node #},M{slave var},{variable}
where:
{node #} is a constant in the range 0 to 63 representing the number of the node on the Turbo
PMAC matching the slave node to be accessed, where the node number specification is:
o {node #} = 0 – 15 specifies MACRO IC 0 nodes 0 – 15, which correspond to slave
nodes 0 – 15 of the same master number as MACRO IC 0;
o {node #} = 16 – 31 specifies MACRO IC 1 nodes 0 – 15, which correspond to slave
nodes 0 – 15 of the same master number as MACRO IC 1;
o {node #} = 32 – 47 specifies MACRO IC 2 nodes 0 – 15, which correspond to slave
nodes 0 – 15 of the same master number as MACRO IC 2;
o {node #} = 48 – 63 specifies MACRO IC 3 nodes 0 – 15, which correspond to slave
nodes 0 – 15 of the same master number as MACRO IC 3;
{slave var} is the name of the variable of the Turbo PMAC acting as a MACRO slave to this
Turbo PMAC. It can be an I, P, Q, or M-variable with a number from 0 to 8191.
{variable} is the name of the variable on this Turbo PMAC. . It can be an I, P, Q, or M-
variable with a number from 0 to 4095.
This command causes Turbo PMAC to copy the value of the specified variable of the Turbo PMAC
acting as a MACRO slave station matching the specified node number on the Turbo PMAC to the
specified variable on this Turbo PMAC.
If the slave node returns an error message or the slave node does not respond within the number of servo
cycles set by I78, Turbo PMAC will report ERR008. Bit 5 of global status register X:$000006 is set to
report such a MACRO auxiliary communications error. Register X:$00320E holds the error value. It is set
to $010000 for a timeout error, or $xxxxFE if the slave node reports an error, where xxxx is the 16-bit
error code reported by the slave node.
When Turbo PMAC executes this command in a PLC, it ends the present scan of that PLC. Execution of
the PLC resumes on the next line of the PLC in the next scan.
If this command is issued to a Turbo PMAC when no buffer is open, it will be executed as an on-line
command.
Examples:
MACROAUXWRITE
Function: Write (copy) variable value to Turbo PMAC MACRO slave
Type: Uncompiled PLC 1 – 31 only
Syntax: MACROAUXWRITE{node #},M{slave var},{variable}
MXW{node #},M{slave var},{variable}
where:
{node #} is a constant in the range 0 to 63 representing the number of the node on the Turbo
PMAC matching the slave node to be accessed, where the node number specification is:
o {node #} = 0 – 15 specifies MACRO IC 0 nodes 0 – 15, which correspond to slave
nodes 0 – 15 of the same master number as MACRO IC 0;
o {node #} = 16 – 31 specifies MACRO IC 1 nodes 0 – 15, which correspond to slave
nodes 0 – 15 of the same master number as MACRO IC 1;
o {node #} = 32 – 47 specifies MACRO IC 2 nodes 0 – 15, which correspond to slave
nodes 0 – 15 of the same master number as MACRO IC 2;
o {node #} = 48 – 63 specifies MACRO IC 3 nodes 0 – 15, which correspond to slave
nodes 0 – 15 of the same master number as MACRO IC 3;
{slave var} is the name of the variable of the Turbo PMAC acting as a MACRO slave to this
Turbo PMAC. It can be an I, P, Q, or M-variable with a number from 0 to 8191.
{variable} is the name of the variable on this Turbo PMAC. . It can be an I, P, Q, or M-
variable with a number from 0 to 4095.
This command causes Turbo PMAC to copy the value of the specified variable on this Turbo PMAC to
the specified variable of the Turbo PMAC acting as a MACRO slave station matching the specified node
number.
If the slave node returns an error message or the slave node does not respond within the number of servo
cycles set by I78, Turbo PMAC will report ERR008. Bit 5 of global status register X:$000006 is set to
report such a MACRO auxiliary communications error. Register X:$00320E holds the error value. It is set
to $010000 for a timeout error, or $xxxxFE if the slave node reports an error, where xxxx is the 16-bit
error code reported by the slave node.
When Turbo PMAC executes this command in a PLC, it ends the present scan of that PLC. Execution of
the PLC resumes on the next line of the PLC in the next scan.
If this command is issued to a Turbo PMAC when no buffer is open, it will be executed as an on-line
command.
Examples:
MACROMSTREAD
Function: Read (copy) Type 1 MACRO master auxiliary parameter value
Type: Uncompiled PLC 1 – 31 only
Syntax: MACROMSTREAD{master #},{master variable},
{ring-master variable}
MMR{master #},{master variable},{ring-master variable}
where:
{master #} is a constant (1-15) representing the number of the remote master whose variable is to
be read;
{master variable} is the name of the variable on the remote master station whose value is to
be reported
{ring-master variable} is the name of the variable on the Turbo PMAC executing the
command into which the value of the remote master variable is to be copied
This command causes Turbo PMAC to copy the value of the specified variable on the remote master
station into the specified variable on the Turbo PMAC executing the command, using the MACRO Type
1 master-to-master auxiliary protocol.
In order for the Turbo PMAC to be able to execute this command, the following conditions must be true:
MACRO IC 0 on this Turbo PMAC must be set up as the synchronizing ring master (I6840 = $xx30);
MACRO IC 0 on this Turbo PMAC must be set up as Master 0 on the ring (I6841 = $0xxxxx);
MACRO IC 0 node 14 must be in broadcast mode (I6840 bit 14 = 1);
MACRO IC 0 node 14 auxiliary register copy function must be disabled (I70 bit 14 = 0);
MACRO IC 0 node 14 must not be used for any other function.
In order for another Turbo PMAC to be able to respond to the communications that this command creates
on the MACRO ring (to be the remote master) the following conditions must be true:
MACRO IC 0 on the Turbo PMAC must be set up as a master, but not the synchronizing ring master
(I6480 = $xx90);
MACRO IC 0 on the Turbo PMAC must be set up with a non-zero master number on the ring (I6841
= $nxxxxx, where n > 0);
MACRO IC 0 node 14 normally must be disabled (I6841 bit 14 = 1);
MACRO IC 0 node 14 must be in “broadcast mode” (I6840 bit 14 = 1);
MACRO IC 0 node 14 auxiliary register copy function must be disabled (I70 bit 14 = 0);
MACRO IC 0 node 14 must not be used for any other function.
If the remote master returns an error message or it does not respond within I79 servo cycles, Turbo
PMAC will report ERR008. Bit 5 of global status register X:$000006 is set to report such a MACRO
auxiliary communications error. Register X:$0031EE holds the error value. It is set to $010000 for a
timeout error, or $xxxxFE if the slave node reports an error, where xxxx is the 16-bit error code reported
by the slave node.
When Turbo PMAC executes this command in a PLC, it ends the present scan of that PLC. Execution of
the PLC resumes on the next line of the PLC in the next scan.
If this command is issued to a Turbo PMAC when no buffer is open, it will be executed as an on-line
command.
Examples:
MMR4,I10,P10 ; Copies value of remote master 4 variable I10 into
; Turbo PMAC variable P10
MMR1,P1,P1 ; Copies value of remote master 1 variable P1 into
; Turbo PMAC variable P1
MACROMSTWRITE
Function: Write (copy) Type 1 MACRO master auxiliary parameter value
Type: Uncompiled PLC 1 – 31 only
Syntax: MACROMSTWRITE{master #},{master variable},
{ring-master variable}
MMW{master #},{master variable},{ring-master variable}
where:
{master #} is a constant (1-15) representing the number of the remote master whose variable is to
be read;
{master variable} is the name of the variable on the remote master station whose value is to
be set;
{ring-master variable} is the name of the variable on the Turbo PMAC executing the
command from which the value of the remote master variable is to be copied.
This command causes Turbo PMAC to copy the value of the specified variable on the remote master
station from the specified variable on the Turbo PMAC executing the command, using the MACRO Type
1 master-to-master auxiliary protocol.
In order for the Turbo PMAC to be able to execute this command, the following conditions must be true:
MACRO IC 0 on this Turbo PMAC must be set up as the synchronizing ring master (I6840 = $xx30);
MACRO IC 0 on this Turbo PMAC must be set up as Master 0 on the ring (I6841 = $0xxxxx);
MACRO IC 0 node 14 must be in broadcast mode (I6840 bit 14 = 1);
MACRO IC 0 node 14 auxiliary register copy function must be disabled (I70 bit 14 = 0);
MACRO IC 0 node 14 must not be used for any other function.
In order for another Turbo PMAC to be able to respond to the communications that this command creates
on the MACRO ring (to be the remote master) the following conditions must be true:
MACRO IC 0 on the Turbo PMAC must be set up as a master, but not the synchronizing ring master
(I6480 = $xx90);
MACRO IC 0 on the Turbo PMAC must be set up with a non-zero master number on the ring (I6841
= $nxxxxx, where n > 0);
MACRO IC 0 node 14 must normally be disabled (I6841 bit 14 = 1);
MACRO IC 0 node 14 must be in broadcast mode (I6840 bit 14 = 1);
MACRO IC 0 node 14 auxiliary register copy function must be disabled (I70 bit 14 = 0);
MACRO IC 0 node 14 must not be used for any other function.
If the remote master returns an error message or it does not respond within I79 servo cycles, Turbo
PMAC will report ERR008. Bit 5 of global status register X:$000006 is set to report such a MACRO
auxiliary communications error. Register X:$0031EE holds the error value. It is set to $010000 for a
timeout error, or $xxxxFE if the slave node reports an error, where xxxx is the 16-bit error code reported
by the slave node.
When Turbo PMAC executes this command in a PLC, it ends the present scan of that PLC. Execution of
the PLC resumes on the next line of the PLC in the next scan.
If this command is issued to a Turbo PMAC when no buffer is open, it will be executed as an on-line
command.
Examples:
MMW4,I10,P10 ; Copies value of Turbo PMAC variable P10 into remote master 4 variable I10
MMW1,P1,P1 ; Copies value of Turbo PMAC variable P1 into remote master 1 variable P1
MACROSLVREAD
Function: Read (copy) Type 1 MACRO auxiliary parameter value
Type: Uncompiled PLC 1 – 31 only
Syntax: MACROSLVREAD{node #},{slave variable},{PMAC variable}
MSR{node #},{slave variable},{PMAC variable}
where:
{node #} is a constant in the range 0 to 63 representing the number of the node on the Turbo PMAC
matching the slave node to be accessed, where the node number specification is:
MACROSLVWRITE
Function: Write (copy) Type 1 MACRO auxiliary parameter value
Type: Uncompiled PLC 1 – 31 only
Syntax: MACROSLVWRITE{node #},{slave variable},{PMAC variable}
MSW{node #},{slave variable},{PMAC variable}
where:
{node #} is a constant in the range 0 to 63 representing the number of the node on the Turbo PMAC
matching the slave node to be accessed, where the node number specification is:
{node #} = 0 – 15 specifies MACRO IC 0 nodes 0 – 15, which correspond to slave nodes 0 –
15 of the same master number as MACRO IC 0;
{node #} = 16 – 31 specifies MACRO IC 1 (Ultralites with Option 1A only) nodes 0 – 15,
which correspond to slave nodes 0 – 15 of the same master number as MACRO IC 1;
{node #} = 32 – 47 specifies MACRO IC 2 (Ultralites with Option 1B only) nodes 0 – 15,
which correspond to slave nodes 0 – 15 of the same master number as MACRO IC 2;
{node #} = 48 – 63 specifies MACRO IC 3 (Ultralites with Option 1C only) nodes 0 – 15,
which correspond to slave nodes 0 – 15 of the same master number as MACRO IC 3;
{slave variable} is the name of the MI-variable or C-command on the slave station whose
value is to be set;
{PMAC variable} is the name of the variable on the PMAC from which the value of the slave
station variable is to be copied
This command causes Turbo PMAC to copy the value of the specified variable on Turbo PMAC to the
specified variable of the MACRO slave station matching the specified node number on the Turbo PMAC,
using the MACRO Type 1 master-to-slave auxiliary protocol.
The variable on the Turbo PMAC can be any of the I, P, Q, or M-variables on the card.
In order for the Turbo PMAC to be able to execute this command, the following conditions must be true:
The MACRO IC used must be set up as a master or the synchronizing ring master
(I6840/6890/6940/6990 = $xx90 or $xx30);
MACRO IC 0 node 15 auxiliary register copy function must be disabled (I70 bit 15 = 0);
MACRO IC 0 node 15 must not be used for any other function.
If the slave node returns an error message or it does not respond within I78 servo cycles, Turbo PMAC
will report ERR008. Bit 5 of global status register X:$000006 is set to report such a MACRO auxiliary
communications error. Register X:$0031EE holds the error value. It is set to $010000 for a timeout
error, or $xxxxFE if the slave node reports an error, where xxxx is the 16-bit error code reported by the
slave node.
When Turbo PMAC executes this command in a PLC, it ends the present scan of that PLC. Execution of
the PLC resumes on the next line of the PLC in the next scan.
If this command is issued to a Turbo PMAC when no buffer is open, it will be executed as an on-line
command.
Examples:
MSW0,MI910,P35 ; Copies value of PMAC P35 into MACRO station node 0 variable MI910
MSW4,C4,P0 ; Causes MACRO station with active node 4 to execute Command #4, saving
; its setup variable values to non-volatile memory (P0 is a dummy variable here)
N{constant}
Function: Program Line Label
Type: Motion program (PROG and ROT)
Syntax: N{constant}
where:
18
{constant} is an integer from 0 to 262,143 (2 -1)
This is a label for a line in the program that allows the flow of execution to jump to that line with a GOTO,
GOSUB, CALL, G, M, T, or D statement or a B command.
A line needs only a label if the user wishes to be able to jump to that line. Line labels do not have to be in
any sort of numerical order. The label must be at the beginning of a line. Remember that each location
label takes up space in Turbo PMAC memory.
Note:
There is always an implied N0 at the beginning of every motion program. Putting
an explicit N0 at the beginning may be useful for people reading the program.
Putting an N0 anywhere else in the program is useless and may confuse people
reading the program.
Examples:
N1
N65537 X1000
See Also:
Subroutines and Subprograms (Writing and Executing Motion Programs)
On-line command B{constant}
Program commands O{constant}, GOTO, GOSUB, CALL, G, M, T, D.
NOFRAX
Function: Remove all axes from list of vector feedrate axes
Type: Motion program (PROG and ROT)
Syntax: NOFRAX
This command causes Turbo PMAC to remove all axes from the list of vector feedrate axes for the
addressed coordinate system. In this mode, any feedrate-specified move in the coordinate system will
yield a vector distance of 0, forcing the use of the Isx86 alternate feedrate.
This can be useful to create a dry run of a motion program, overriding the feedrates specified in the
motion-program F commands.
Axes can be restored to the vector feedrate list with the FRAX command.
See Also:
I-variables Isx86, Isx89, Isx90, Isx98
On-line commands NOFRAX, FRAX
Program commands F, FRAX
NORMAL
Function: Define Normal Vector to Plane of Circular Interpolation and Cutter Radius
Compensation
Type: Motion program (PROG and ROT)
Syntax: NORMAL {vector}{data} [{vector}{data}...]
NRM {vector}{data} [{vector}{data}...]
where:
{vector} is one of the letters I, J, and K, representing components of the total vector parallel to the
X, Y, and Z axes, respectively
{data} is a constant or expression representing the magnitude of the particular vector component.
This statement defines the orientation of the plane in XYZ-space in which circular interpolation and cutter
radius compensation will take place by setting the normal (perpendicular) vector to that plane.
The vector components that can be specified are I (X-axis direction), J (Y-axis direction), and K (Z-axis
direction). The ratio of the component magnitudes determines the orientation of the normal vector, and
therefore, of the plane. The length of this vector does not matter – it does not have to be a unit vector.
The direction sense of the vector does matter, because it defines the clockwise sense of an arc move, and
the sense of cutter-compensation offset. Turbo PMAC uses a right-hand rule; that is, in a right-handed
coordinate system (I x J = K), if a right thumb points in the direction of the normal vector specified here,
the right fingers will curl in the direction of a clockwise arc in the circular plane, and in the direction of
offset-right from direction of movement in the compensation plane. In general, the negative normal
vector produces the clockwise/counterclockwise sense expected.
Examples:
The standard settings to produce circles in the principal planes will therefore be:
NORMAL K-1 ; XY plane -- equivalent to G17
NORMAL J-1 ; ZX plane -- equivalent to G18
NORMAL I-1 ; YZ plane -- equivalent to G19
By using more than one vector component, a circular plane skewed from the principal planes can be defined:
NORMAL I0.866 J0.500
NORMAL J25 K-25
NORMAL J(-SIN(Q1)) K(-COS(Q1))
NORMAL I(P101) J(P201) K(301)
See Also:
Circular Blended Moves, Cutter Radius Compensation (Writing and Executing Motion Programs)
Cartesian Axes (Setting Up a Coordinate System)
Program Commands CIRCLE1, CIRCLE2, CC0, CC1, CC2
NX{data}
Function: Set 3D-comp surface-normal vector X-component
Type: Motion program (PROG and ROT)
Syntax: NX{data}
where:
{data} is a signed floating-point constant or expression representing the X-component of the
surface-normal vector
This statement specifies the X-component of the surface-normal vector used for three-dimensional cutter-
radius compensation. This value is used along with the Y and Z-components specified by the NY{data}
and NZ{data} statements, respectively, to compute the orientation of the vector.
The total magnitude of the surface-normal vector specified with these three components does not matter,
although a unit-magnitude vector is typically specified. The relative magnitudes (including signs) of the
three components are what determine the orientation of the vector. The vector must be defined from the
surface toward the tool. Generally, all three components be declared together on one line; if only one or
two components are declared, the others are left at their old values, possibly leading to unpredictable
results.
The surface-normal vector affects the compensation for the end-point of the move commanded on the
same line as the surface-normal vector. It also affects the compensation for subsequent moves until
another surface-normal vector is declared. In typical use, a new surface-normal vector is declared with
each move, so the vector only affects the move on the same line in this case.
Example:
X3.76 Y8.29 Z-4.83 A34.32 C-29.75 NX0.866 NY0 NZ-0.5
See Also:
Three-Dimensional Compensation
Program commands CC3, CCR{data}, NY{data}, NZ{data}, TR{data}, TX{data},
TY{data}, TZ{data}
NY{data}
Function: Set 3D-comp surface-normal vector Y-component
Type: Motion program (PROG and ROT)
Syntax: NY{data}
where:
{data} is a signed floating-point constant or expression representing the Y-component of the
surface-normal vector
This statement specifies the Y-component of the surface-normal vector used for three-dimensional cutter-
radius compensation. This value is used along with the X and Z-components specified by the NX{data}
and NZ{data} statements, respectively, to compute the orientation of the vector.
The total magnitude of the surface-normal vector specified with these three components does not matter,
although a unit-magnitude vector is typically specified. The relative magnitudes (including signs) of the
three components are what determine the orientation of the vector. The vector must be defined from the
surface toward the tool. Generally, all three components be declared together on one line; if only one or
two components are declared, the others are left at their old values, possibly leading to unpredictable
results.
The surface-normal vector affects the compensation for the end-point of the move commanded on the
same line as the surface-normal vector. It also affects the compensation for subsequent moves until
another surface-normal vector is declared. In typical use, a new surface-normal vector is declared with
each move, so the vector only affects the move on the same line in this case.
Example:
X3.76 Y8.29 Z-4.83 A34.32 C-29.75 NX0.866 NY0 NZ-0.5
See Also:
Three-Dimensional Compensation
Program commands CC3, CCR{data}, NX{data}, NZ{data}, TR{data}, TX{data},
TY{data}, TZ{data}
NZ{data}
Function: Set 3D-comp surface-normal vector Z-component
Type: Motion program (PROG and ROT)
Syntax: NZ{data}
where:
{data} is a signed floating-point constant or expression representing the Z-component of the
surface-normal vector
This statement specifies the Z-component of the surface-normal vector used for three-dimensional cutter-
radius compensation. This value is used along with the X and Y-components specified by the
NX{data} and NY{data} statements, respectively, to compute the orientation of the vector.
The total magnitude of the surface-normal vector specified with these three components does not matter,
although typically a unit-magnitude vector is specified. The relative magnitudes (including signs) of the
three components are what determine the orientation of the vector. The vector must be defined from the
surface toward the tool. Generally, all three components be declared together on one line; if only one or
two components are declared, the others are left at their old values, possibly leading to unpredictable
results.
The surface-normal vector affects the compensation for the end-point of the move commanded on the
same line as the surface-normal vector. It also affects the compensation for subsequent moves until
another surface-normal vector is declared. In typical use, a new surface-normal vector is declared with
each move, so the vector only affects the move on the same line in this case.
Example:
X3.76 Y8.29 Z-4.83 A34.32 C-29.75 NX0.866 NY0 NZ-0.5
See Also:
Three-Dimensional Compensation
Program commands CC3, CCR{data}, NX{data}, NY{data}, TR{data}, TX{data},
TY{data}, TZ{data}
O{constant}
Function: Alternate Line Label
Type: Motion program (PROG and ROT)
Syntax: O{constant}
where:
18
{constant} is an integer from 0 to 262,143 (2 -1)
This is an alternate form of label in the motion program. It allows the flow of execution to jump to that
line with a GOTO, GOSUB, CALL, G, M, T, or D statement or a B command.
Turbo PMAC will store and report this as an N{constant} statement, but O labels are legal to send to
the program buffer. (N10 and O10 are identical labels to Turbo PMAC.)
A line only needs a label if the user wishes to be able to jump to that line. Line labels do not have to be in
any sort of numerical order. The label must be at the beginning of a line. Remember that each location
label takes up space in Turbo PMAC memory.
Examples:
O1
O65537 X1000
See Also:
Subroutines and Subprograms (Writing and Executing Motion Programs)
On-line command B{constant}
Program commands O{constant}, GOTO, GOSUB, CALL, G, M, T, D.
OR({condition})
Function: Conditional OR
Type: PLC program
Syntax: OR ({condition})
This statement forms part of an extended compound condition to be evaluated in a PLC program. It must
immediately follow an IF, WHILE, AND, or OR statement. This OR is a boolean operator logically
combining the condition on its line with the condition on the program line above.
It takes lower precedence than operators within a compound condition on a single line (those within
parentheses), and also lower precedence than an AND operator that starts a line. (ORs operate on groups
of ANDed conditions.)
In motion programs, there can be compound conditions within one program line, but not across multiple
program lines, so this statement is not permitted in motion programs.
Note:
This logical OR, which acts on conditions, should not be confused with the bit-by-
bit | (vertical bar) or-operator, which operates on values.
Examples:
IF (M11=1) ; This branch increments P1 every cycle that
AND (M12=0) ; inputs M11 and M12 are different, and decrements
OR (M11=0) ; them every cycle that they are the same.
AND (M12=1)
P1=P1+1
ELSE
P1=P1-1
ENDIF
IF (M11=1 AND M12=0) ; This does the same as above
OR (M11=0 AND M12=1)
P1=P1+1
ELSE
P1=P1-1
ENDIF
See Also:
Conditions (Program Computational Features)
Writing a PLC Program
Program commands IF, WHILE, AND
P{data}={expression}
Function: Set P-Variable Value
Type: Motion program (PROG and ROT)
Syntax: P{data}={expression}
where:
{data} is a constant, or an expression in parentheses, for an integer value from 0 to 8191
representing the P-variable number;
{expression} represents the value to be assigned to this P-variable.
This command sets the value of the specified P-variable to that of the expression on the right side of the
equals sign. The assignment is done as the line is processed, which usually in a motion program is one or
two moves ahead of the move actually executing at the time (because of the need to calculate ahead in the
program).
Examples:
P1=0
P746=P20+P40
P893=SIN(Q100)-0.5
See Also:
How Turbo PMAC Executes a Motion Program (Writing and Executing Motion Programs)
On-line command P{constant}={expression}
Program commands I{data}={expression}, M{data}={expression},
Q{data}={expression}.
PAUSE PLC
Function: Pause execution of PLC programs
Type: Motion program (PROG or ROT), PLC program
Syntax: PAUSE PLC {constant}[,{constant}...]
PAU PLC {constant}[,{constant}...]
PAUSE PLC {constant}[..{constant}]
PAU PLC {constant}[..{constant}]
where:
each {constant} is an integer from 0 to 31 representing the PLC number
This command causes Turbo PMAC to stop execution of the specified uncompiled PLC program or
programs, with the capability to restart execution at this point (not necessarily at the top) with a RESUME
PLC command. Execution can also be restarted at the top of the program with the ENABLE PLC
command.
If the PLC program is paused from within that PLC, execution is stopped immediately after the PAUSE
PLC command.
If the PLC program is paused while it is not in the middle of a scan, which is always the case if it is
paused from another background PLC, it will obviously be paused at the end of a scan – after an
ENDWHILE or after the last line.
If the PLC program is paused while it has been interrupted in the middle of a scan (for example, from a
motion program), its execution will resume after the interrupt and continue until after it executes any of
the following:
Any ENABLE PLC, DISABLE PLC, PAUSE PLC, or RESUME PLC command
An ENDWHILE command
The last line of the program
Execution will be paused at this point.
PLC programs are specified by number, and may be specified in a command singularly, in a list
(separated by commas), or in a range of consecutively numbered programs.
If no buffer is open when this command is sent to Turbo PMAC, it will be executed immediately as an
on-line command.
Examples:
PAUSE PLC 1
PAUSE PLC 4,5
PAUSE PLC 7..20
PAU PLC 3,8,11
PAU PLC 0..31
See Also:
I-variable I5
On-line commands ENABLE PLC, DISABLE PLC, <CONTROL-D>, PAUSE PLC, RESUME PLC,
LIST PLC
Program command ENABLE PLC, DISABLE PLC, RESUME PLC
PRELUDE
Function: Specify automatic subroutine call function
Type: Motion program
Syntax: PRELUDE1{command}
PRELUDE0
where:
{command} is a subprogram call from the set CALL{data}, G{data}, M{data},
T{data}, D{data}
The PRELUDE1 command permits automatic insertion of a subprogram call before each subsequent
motion command (e.g. X10Y10) or other letter-number command (e.g. L10) other than a line label in the
motion program. The action taken is equivalent to inserting the call into the program text before each
subsequent motion command or letter-number command.
The subprogram call to be performed can be specified in the PRELUDE1 command either as a CALL
command, or as a G, M, T, or D code. The value following the Call or code letter must be a constant; it
cannot be a variable or expression. It does not have to be an integer. If the routine called in the subprogram
starts with a READ statement, the motion or letter-number command itself can become arguments for the
subprogram call. Any motion command within a PRELUDE1 subroutine or subprogram call is executed
directly as a motion command, without an automatic subroutine call in front of it..
Turbo PMAC will only execute the PRELUDE1 function if the motion or letter-number command is
found at the beginning of a program line or immediately after the line label. If another type of command
occurs earlier on the program line, no PRELUDE1 function will be executed before the motion or letter-
number command. If the command is on a line that is already in a subroutine or subprogram reached by a
CALL or GOSUB command, no PRELUDE1 function will be executed.
Each PRELUDE1 command supersedes the previous PRELUDE1 command. It is not possible to nest
automatic PRELUDE1 calls, but an automatic PRELUDE1 call can be nested within explicit subroutine
and subprogram calls.
PRELUDE0 disables any automatic subroutine call.
Examples:
PRELUDE1 CALL10 ; Insert a CALL10 before subsequent moves
X10 Y20 ; Implicit CALL10 before this move
X20 Y30 ; Implicit CALL10 before this move
...
OPEN PROG 10 CLEAR ; Subprogram
Z-1 ; Move down
DWELL 500 ; Hold position
Z1 ; Move up
RETURN
...
G71 X7 Y15 P5 ; G71 calls PROG 1000 N71000
X8 Y16 P5 ; With PRELUDE, G71 is implied (modal)
X9 Y15 P8 ; With PRELUDE, G71 is implied (modal)
G70 ; Stop modal canned cycles
...
OPEN PROG 1000
...
N70000 ; G70 subroutine
PRELUDE0 ; Stop PRELUDE calls
RETURN
N71000 ; G71 subroutine
PRELUDE1 G71.1 ; Make G71 modal by using PRELUDE
RETURN
N71100 ; G71.1 routine is what executes G71 modally
READ(X,Y,P) ; Read values associated with X, Y, and P
{action based on parameters}
RETURN
See Also:
Subroutines and Subprograms (Writing and Executing Motion Programs)
Program commands CALL, GOSUB, READ, G, M, T, D
PSET
Function: Redefine current axis positions (Position SET)
Type: Motion program
Syntax: PSET{axis}{data} [{axis}{data}...]
where:
{axis} is the character specifying which axis (X, Y, Z, A, B, C, U, V, W);
{data} is a constant or an expression representing the new value for this axis position
This command allows the user to re-define the value of an axis position in the middle of the program. It
is equivalent to the RS-274 G-Code G92. No move is made on any axis as a result of this command – the
value of the present commanded position for the axis is merely set to the specified value.
Internally, this command changes the value of the position bias register for each motor attached to an axis
named in the command. This register holds the difference between the axis zero point and the motor zero
(home) point.
This command automatically forces a temporary pause in the motion of the axes; no moves are blended
through a PSET command. For more powerful and flexible offsets that can be done on the fly (X, Y, and
Z axes only), refer to the matrix manipulation commands such as ADIS and IDIS.
Examples:
X10Y20
PSET X0 Y0 ; Call this position (0,0)
N92000 READ(X,Y,Z) ; To implement G92 in PROG 1000
PSET X(Q124)Y(Q125)Z(Q126) ; Equivalent of G92 X..Y..Z..
See Also:
Axes (Setting Up a Coordinate System)
On-line command {axis}={expression}
Program commands ADIS, AROT, IDIS, IROT
Suggested M-variable definitions Mxx64
PVT{data}
Function: Set Position-Velocity-Time mode
Type: Motion program (PROG and ROT)
Syntax: PVT{data}
where:
{data} is a positive constant or expression representing the time of a segment in milliseconds
This command puts the motion program into Position-Velocity-Time move mode, and specifies the time
for each segment of the move, in milliseconds. In this mode, each move segment in the program must
specify the ending position and velocity for the axis. Taking the starting position and velocity (from the
previous segment), the ending position and velocity, and the segment time, Turbo PMAC computes the
unique cubic position profile (parabolic velocity profile) to meet these constraints.
If global I-variable I42 is set to the default value of 0, the specified time uses the move time register, and
has a range of 0 to 4095.9998 milliseconds, with a resolution of ¼-microsecond. In this case, if the
segment time in a sequence of moves is changed on the fly, either another PVT command is used, or a TM
command.
If I42 is set to 1, the specified time uses the acceleration time register, and has a range of 0 to 8,388,607
milliseconds(about 2 hours, 20 minutes), with a resolution of 1 millisecond. In this case, if the segment
time in a sequence of moves is changed on the fly, either another PVT command is used, or a TA
command.
The segment time in a sequence of moves can be changed on the fly, either with another PVT command,
or with a TM command. TS, TA, and F settings are irrelevant in this mode.
The PVT command takes the program out of any of the other move modes (LINEAR, CIRCLE, SPLINE,
RAPID), and any of the other move mode commands takes the program out of PVT move mode.
Refer to the Writing and Executing Motion Programs section of this manual for more details of this mode.
Examples:
INC ; incremental mode, specify moves by distance
PVT200 ; enter this mode -- move time 200ms
X100:1500 ; cover 100 units ending at 1500 units/sec
X500:3000 ; cover 500 units ending at 3000 units/sec
X500:1500 ; cover 500 units ending at 1500 units/sec
X100:0 ; cover 100 units ending at 0 units/sec
PVT(P37)
See Also:
Position-Velocity-Time Mode Moves (Writing and Executing Motion Programs)
Program commands {axis}{data}:{data}..., TA, LINEAR, CIRCLEn, RAPID, SPLINE1.
Q{data}={expression}
Function: Set Q-Variable Value
Type: Motion program (PROG and ROT); PLC program
Syntax: Q{data}={expression}
where:
{data} is a constant, or an expression in parentheses, for an integer value from 0 to 8191
representing the Q-variable number;
{expression} represents the value to be assigned to the specified Q-variable.
This command sets the value of the specified Q-variable to that of the expression on the right side of the
equals sign. The assignment is done as the line is processed, which in a motion program performing a
continuous move sequence is usually one or two moves ahead of the move actually executing at the time
(because of the need to calculate ahead in the program).
Because each coordinate system has its own set of Q-variables, it is important to know which coordinate
system's Q-variable is affected by this command. When executed from inside a motion program, this
command affects the specified Q-variable of the coordinate system running the motion program.
When executed from inside a PLC program, this command affects the specified Q-variable of the
coordinate system specified by the most recent ADDRESS command executed inside that PLC program.
If there has been no ADDRESS command executed since power-on/reset, it affects the Q-variable of
Coordinate System 1.
Examples:
Q1=3
Q99=2.71828
Q124=P100+ATAN(Q120)
See Also:
Q-Variables (Program Computational Features)
On-line command Q{constant}={expression}
Program commands ADDRESS, I{data}={expression}, M{data}={expression},
P{data}={expression}
R{data}
Function: Set Circle Radius
Type: Motion program (PROG or ROT)
Syntax: R{data}
where:
{data} is a constant or expression representing the radius of the arc move specified in user length
units.
This partial command defines the magnitude of the radius for the circular move specified on that
command line. It does not affect the moves on any other command lines. (If there is no R radius
specification and no IJK vector specification on a move command line, the move will be done linearly,
even if the program is in CIRCLE mode.)
If the radius value specified in {data} is greater than zero, the circular move to the specified end point
will describe an arc of less than or equal to 180o with a radial length of the specified value. If the radius
value specified in {data} is less than zero, the circular move to the specified end point will describe an
arc of greater than or equal to 180o with a radial length equal to the absolute value of {data}.
Note:
If using the AROT or IROT commands to scale the coordinate system, do not use
the radius center specification for circle commands. The radius does not get
scaled. Use the I, J, K vector specification instead.
Note:
If the distance from the start point to the end point is more than twice the
magnitude specified in {data}, there is no circular arc move possible. If the
distance is greater than twice {data} by an amount less than Isx96 (expressed in
user length units), Turbo PMAC will execute a spiral to the end point. If the
distance is greater by more than Isx96, Turbo PMAC will stop the program with a
run-time error.
Examples:
RAPID X0 Y0 ; Move to origin
CIRCLE1 ; Clockwise circle mode
X10 Y10 R10 ; Quarter circle to (10, 10)
X0 Y0 R-10 ; Three-quarters circle back to (0, 0)
X(P101) R(P101/2) ; Half circle to (P101, 0)
See Also:
Circular Blended Moves (Writing and Executing Motion Programs);
I-variables Isx13, Isx96
Program commands CIRCLE1, CIRCLE2, {axis}{data}{vector}{data}...
RAPID
Function: Set Rapid Traverse Mode
Type: Motion program (PROG and ROT)
Syntax: RAPID
RPD
This command puts the program into a mode in which all motors defined to the commanded axes move to
their destination points in jog-style moves. This mode is intended to create the minimum-time move from
one point to another. Successive moves are not blended together in this mode, and the different motors do
not necessarily all reach their end points at the same time.
The accelerations and decelerations in this mode are controlled by motor jog-acceleration I-variables
Ixx19, Ixx20, and Ixx21. If motor I-variable Ixx90 is set to 0, the velocities in this mode are controlled by
the motor jog speed I-variables Ixx22. If Ixx90 is set to 1, they are controlled by the motor maximum
speed I-variables Ixx16. Only the motor with the greatest distance-to-speed ratio for the move actually
moves at this speed; all other motors are slowed from the specified speed to complete the move in
approximately the same time, so that the move is nearly linear.
The RAPID command takes the program out of any of the other move modes (LINEAR, CIRCLE, PVT,
SPLINE); any of the other move-mode commands takes the program out of RAPID mode.
Examples:
RAPID X10 Y20 ; Move quickly to starting cut position
M1=1 ; Turn on cutter
LINEAR X12 Y25 F2 ; Start cutting moves
...
M1=0 ; Turn off cutter
RAPID X0 Y0 ; Move quickly back to home position
See Also:
Rapid Mode Moves (Writing and Executing Motion Programs)
I-variables Ixx90, Ixx16, Ixx19, Ixx22
Program commands LINEAR, CIRCLE, PVT, SPLINE
READ
Function: Read Arguments for Subroutine
Type: Motion program (PROG only)
Syntax: READ({letter},[{letter}...])
where:
{letter} is any letter of the English alphabet, except N or O, representing the letter on the calling
program line whose following value is to be read into a variable
Note:
No space is allowed between READ and the left parenthesis.
This statement allows a subprogram or subroutine to take arguments from the calling routine. It looks at
the remainder of the line calling this routine (CALL, G, M, T, D), takes the values following the specified
letters and puts them into particular Q-variables for the coordinate system. For the Nth letter of the
alphabet, the value is put in Q(100+N).
It scans the calling line until it sees a letter that is not in the list of letters to READ, or until the end of the
calling line. (Note that if it encounters a letter not to be read, it stops, even if some letters have not yet
been read.) Each letter value successfully read into a Q-variable causes a bit to be set in Q100, noting that
it was read (bit N-1 for the Nth letter of the alphabet). For any letter not successfully read in the most
recent READ command, the corresponding bit of Q100 is set to zero.
The Q-variable and flag bit of Q100 associated with each letter are shown in the following table:
Letter Target Variable Q100 Bit Bit Value Decimal Bit Value Hex
A Q101 0 1 $01
B Q102 1 2 $02
C Q103 2 4 $04
D Q104 3 8 $08
E Q105 4 16 $10
F Q106 5 32 $20
G Q107 6 64 $40
H Q108 7 128 $80
I Q109 8 256 $100
J Q110 9 512 $200
K Q111 10 1,024 $400
L Q112 11 2,048 $800
M Q113 12 4,096 $1000
N* Q114* 13* 8,192* $2000*
O* Q115* 14* 16,384* $4000*
P Q116 15 32,768 $8000
Q Q117 16 65,536 $10000
R Q118 17 131,072 $20000
S Q119 18 262,144 $40000
T Q120 19 524,288 $80000
U Q121 20 1,048,57 $100000
V Q122 21 2,097,15 $200000
W Q123 22 4,194,304 $400000
X Q124 23 8,388,608 $800000
Y Q125 24 16,777,216 $1000000
Z Q126 25 33,554,432 $2000000
*Cannot be used
Any letter may be READ except N or O, which are reserved for line labels (and should only be at the
beginning of a line anyway). If a letter value is read from the calling line, the normal function of the
letter (e.g. an axis move) is overridden, so that letter serves merely to pass a parameter to the subroutine.
If there are remaining letter values on the calling line that are not read, those will be executed according
to their normal function after the return from the subroutine.
Examples:
In standard machine tool code, a two-second DWELL would be commanded in the program as a G04
X2000, for instance. In Turbo PMAC, a G04 is interpreted as a CALL to label N04000 of PROG 1000,
so to implement this function properly, PROG 1000 would contain the following code:
N04000 READ(X)
DWELL (Q124)
RETURN
Also, in standard machine tool code, the value assigned to the current position of the axis may be changed
with the G92 code, followed by the letters and the new assigned values of any axes (e.g. G92 X20
Y30). It is important only to assign new values to axes specified in this particular G92 command, so the
Turbo PMAC subroutine implementing G92 with the PSET command must check to see if that particular
axis is specified:
N92000 READ(X,Y,Z)
IF (Q100 & $800000 > 0) PSET X(Q124)
IF (Q100 & $1000000 > 0) PSET Y(Q125)
IF (Q100 & $2000000 > 0) PSET Z(Q126)
RETURN
See Also:
Subroutines and Subprograms (Writing and Executing Motion Programs)
Program commands CALL, GOSUB, G, M, T, D
RESUME PLC
Function: Resume execution of PLC programss
Type: Motion program (PROG and ROT), PLC program
Syntax: RESUME PLC {constant}[,{constant}...]
RES PLC {constant}[,{constant}...]
RESUME PLC{constant}[..{constant}]
RES PLC {constant}[..{constant}]
where:
each {constant} is an integer from 0 to 31 representing the PLC number
This command causes Turbo PMAC to resume execution of the specified uncompiled PLC program or
programs at the point where execution was suspended with the PAUSE PLC command, which is not
necessarily at the top of the program.
The RESUME PLC command cannot be used to restart execution of a PLC program that has been stopped
with a DISABLE PLC command. However, after a PLC has been stopped with a DISABLE PLC
command, if a PAUSE PLC command is then given for that PLC, then a RESUME PLC command can
be given to start operation at the point at which it has been stopped.
PLC programs are specified by number, and may be used singularly in this command, in a list (separated
by commas), or in a range of consecutively numbered programs.
If no buffer is open when this command is sent to Turbo PMAC, it will be executed immediately as an
on-line command.
Examples:
RESUME PLC 0
RESUME PLC 1,2,5
RESUME PLC 1..16
RES PLC 7
See Also:
I-variable I5
On-line commands ENABLE PLC, DISABLE PLC, <CONTROL-D>, PAUSE PLC, RESUME PLC
Program commands ENABLE PLC, DISABLE PLC, PAUSE PLC
RETURN
Function: Return From Subroutine Jump/End Main Program
Type: Motion program (PROG only)
Syntax: RETURN
RET
The RETURN command tells the motion program to jump back to the routine that called the execution of
this routine. If this routine was started from an on-line command (RUN), program execution stops and the
program pointer is reset to the top of this motion program – control is returned to the Turbo PMAC
operating system.
If this routine was started from a GOSUB, CALL, G, M, T, or D command in a motion program, program
execution jumps back to the command immediately following the calling command.
When the CLOSE command is sent to end the entry into a motion program buffer, Turbo PMAC
automatically appends a RETURN command to the end of that program. When the OPEN command is
sent to an existing motion program buffer, the final RETURN command is automatically removed.
Examples:
OPEN PROG 1 CLEAR
X20 F10
X0
CLOSE ; Turbo PMAC places a RETURN here
OPEN PROG 1000 CLEAR
N0 RAPID RETURN ; Execution jumps back after one-line routine
N1000 LINEAR RETURN ; Ditto
N2000 CIRCLE1 RETURN ; Ditto
...
CLOSE ; Turbo PMAC places a RETURN here
See Also:
Subroutines and Subprograms (Writing and Executing Motion Programs)
On-line commands OPEN, CLOSE
Program commands CALL, GOSUB, G, M, T, D
S{data}
Function: Spindle data command
Type: Motion program (PROG and ROT)
Syntax: S{data}
where:
{data} is a constant or expression representing the value to be passed to the storage variable for
later use
This command causes the value in {data} to be loaded in variable Q127 for the coordinate system
executing the motion program. It takes no other action. It is intended to pass spindle speed data in
machine tool programs. The algorithms that actually control the spindle would then use Q127 in their
routines; for instance, to set jog speed, or voltage output.
Note:
This command is distinct from S{data} information passed as part of a
subroutine call through a READs command; in that form, the value is placed in
Q119 for the coordinate system.
Examples:
S1800 ; This puts a value of 1800 in Q127
S(P1) ; This puts the value of P1 in Q127
G96 S50 ; Here the S-term is an argument in the G-code call
(PROG 1000) ; This is the subroutine that executes G96
N96000 READs ; This puts a value of 50 in Q119
See Also:
Q-variables (Program Computational Features)
Implementing a Machine-Tool Style Program (Writing and Executing Motion Programs)
Motion program command READ
Example program SPINDLE.PMC
SENDx
Function: Cause Turbo PMAC to Send Message
Type: Motion program (PROG and ROT); PLC program
Syntax: SENDS"{message}"
SENDP"{message}"
SENDR"{message}"
SENDA"{message}"
This command causes Turbo PMAC to send the specified message out a specified communications port.
This is particularly useful in the debugging of applications. It can also be used to prompt an operator, or
to notify the host computer of certain conditions.
If I62=0, Turbo PMAC issues a carriage-return (<CR>) character at the end of the message automatically.
If I62=1, Turbo PMAC does not issue a <CR> character at the end of the message; a SENDx^M must be
used to issue a <CR> in this case.
Note:
If there is no host on the port to which the message is sent, or the host is not ready
to read the message, the message is left in the queue. If several messages back up
in the queue this way, the program issuing the messages will halt execution until
the messages are read. This is a common mistake when the SENDx command is
used outside of an Edge-Triggered condition in a PLC program. See Writing a
PLC Program for more details.
On the serial port, it is possible to send messages to a non-existent host by
disabling the port handshaking with I1=1.
SENDS transmits the message to the main serial port.
SENDP transmits the message to the parallel bus port: ISA, VME, or PCI, whichever is present on the
board.
SENDR transmits the message through the DPRAM ASCII response buffer.
The byte value of the control character sent is 64 ($40) less than the byte value of {letter}. The
letters that can be used and their corresponding control characters are:
{letter} Letter Value Control Character Value
@ 64 NULL 0
A 65 <CTRL-A> 1
B 66 <CTRL-B> 2
C 67 <CTRL-C> 3
...
X 88 <CTRL-X> 24
Y 89 <CTRL-Y> 25
Z 90 <CTRL-Z> 26
[ 91 ESC 27
\ 92 28
] 93 29
^ 94 30
_ 95 31
Note: Do not put the up-arrow character and the letter in quotes (e.g. do not use SENDx"^A")
or Turbo PMAC will attempt to send the two non-control characters ^ and A for this example,
instead of the control character.
SENDS transmits the control character to the main serial port.
SENDP transmits the control character to the parallel bus port: ISA, VME, or PCI, whichever is present
on the board.
SENDR transmits the control character through the DPRAM ASCII response buffer.
SENDA transmits the control character to the Option 9T auxiliary serial port.
When Turbo PMAC powers up or resets, the active response port is the serial port. When any command
is received over a bus port, the active response port becomes the bus port. Turbo PMAC must then
receive a <CONTROL-Z> command to cause the response port to revert back to the serial port.
It is possible, particularly in PLC programs, to order the sending of messages faster than the port can handle
them. Usually, this will happen if the same SEND command is executed every scan through the PLC.
For this reason, it is good practice to have at least one of the conditions that causes the SEND command to
execute to be set false immediately to prevent execution of this SEND command on subsequent scans of
the PLC.
See Also:
On-line command <CTRL-Z>
Program commands SEND"{message}", COMMAND"{command}", COMMAND^{letter}
SETPHASE
Function: Set commutation phase position value
Type: Motion and PLC programs
Syntax: SETPHASE {constant} [,{constant}…]
SETPHASE {constant}..{constant}
[,{constant}..{constant}]
where:
{constant} is an integer from 1 to 32 representing a motor number
The SETPHASE command causes Turbo PMAC to immediately copy the value of Ixx75 for the specified
motor or motors into the active phase position register for that motor or motors.
Typically, this command is used to correct the phasing of a motor at a known angle (such as the index
pulse of the encoder) after an initial rough phasing (such as from Hall commutation registers).
The copying action is done immediately on execution of the command. In a motion program, this is done
at program calculation, which can be ahead of execution of the accompanying moves if the command is in
the middle of a blended sequence of moves.
To determine the value of Ixx75 to be used, first force an unloaded motor to the zero position in its
phasing cycle. Next, manually set the phase position register (suggested M-variable Mxx71) to zero.
Finally, move the motor to the known position, usually with a homing search move to the index pulse or
other trigger. Read the phase position register at this point and set Ixx75 to this value. For more details,
see the Ixx75 description and the Commutation section of the User Manual.
If no motion program buffer or PLC program buffer is open when this command is issued, this command
will be executed immediately as an on-line command.
Examples:
HOME1
WHILE(M140=0)
ENDWHILE
SETPHASE1
SPLINE1
Function: Put program in uniform cubic spline motion mode
Type: Motion program (PROG and ROT)
Syntax: SPLINE1
This modal command puts the program in cubic B-spline mode. In SPLINE1 mode, each programmed
move takes either the TM time (Isx89 is default) if global variable I42 is set to the default value of 0, or
the TA time (Isx87 is the default) if I42 is set to 1 — there is no feedrate specification allowed. Each
move on each axis is computed as a cubic position trajectory in which the intermediate positions are
relaxed somewhat so there are no velocity or acceleration discontinuities in blending the moves together.
If I42 is set to 0, the move time specified by TM has a range of 0 to 4095.9998 milliseconds, with a
resolution of ¼-microsecond, floating point. If I42 is set to 1, the specified TA time has a range of 0 to
8,388,607 milliseconds (about 2 hours, 20 minutes), with a resolution of 1 millisecond, integer only.
Before the first move in any series of consecutive moves, a starting move of TM or TA time is added to
blend smoothly from a stop. After the last move in any series of consecutive moves, an ending move of
TM or TA time is added to blend smoothly to a stop.
This command will take the program out of any of the other move modes (LINEAR, CIRCLE, PVT,
RAPID). The program will stay in this mode until another move mode command is executed.
Examples:
RAPID X10 Y10
SPLINE1 TM100
X20 Y15
X32 Y21
X43 Y26
X50 Y30
DWELL100
RAPID X0 Y0
See Also:
Cubic Spline Mode (Writing and Executing Motion Programs)
Program commands LINEAR, CIRCLE, RAPID, PVT, SPLINE2, TA
SPLINE2
Function: Put program in non-uniform cubic spline motion mode
Type: Motion program (PROG and ROT)
Syntax: SPLINE2
This modal command puts the program in non-uniform cubic spline mode. This mode is virtually
identical to the SPLINE1 uniform cubic spline mode described above, except that the TM segment time
can vary in a continuous spline. This makes SPLINE2 mode more flexible than SPLINE1 mode, but it
takes slightly more computation time.
Examples:
RAPID X10 Y10
SPLINE2
X20 Y15 TA100
X32 Y21 TA120
X43 Y26 TA87
X50 Y30 TA62
DWELL100
RAPID X0 Y0
See Also:
Cubic Spline Mode (Writing and Executing Motion Programs)
Program commands LINEAR, CIRCLE, RAPID, PVT, SPLINE1, TA
STOP
Function: Stop program execution
Type: Motion program (PROG)
Syntax: STOP
This command suspends program execution, whether started by run or step, keeping the program counter
pointing to the next line in the program, so that execution may be resumed with a RUN or STEP command.
Examples:
A10 B10
A20 B0
STOP
A0 B0
See Also:
On-line commands <CONTROL-Q>, Q, R, S
Program commands BLOCKSTART, BLOCKSTOP
T{data}
Function: Tool Select Code (T-Code)
Type: Motion program
Syntax: T{data}
where:
{data} is a floating-point constant or expression in the range 0.000 to 999.999, specifying the
program number and the line label to jump to
Turbo PMAC interprets this statement as a CALL 10n2.({data’}*1000) command, where n is the
hundreds’digit of {data}, and {data’} is the value of {data} without the hundred’s digit (modulo
100 in mathematical terms). That is, this statement causes a jump (with return) to motion program 10n2,
and the specified line label.
(Usually, programs 10n2 are used to implement the machine codes as the system designer sees fit.) The
value of {data’} can be from 0.0 to 99.999, corresponding to line labels N0 to N99999.
This structure permits the implementation of customizable T-Code routines for machine-tool style
applications by the writing of subroutines in motion programs 10n2. Arguments can be passed to these
subroutines by following the T-Code with one or more sets of {letter}{data}, as in CALL and
READ statements.
Most users will have T-codes only in the range 0-99, which permits the use of PROG 1002 only, and
allows {data’} to equal {data} for direct specification of the line label.
Examples:
T01 jumps to N1000 of PROG 1002
T12 jumps to N12000 of PROG 1002
T115 jumps to N15000 of PROG 1012
See Also:
Program commands CALL{data}, D{data}, M{data}, T{data}, RETURN
TA{data}
Function: Set Acceleration Time
Type: Motion program (PROG and ROT)
Syntax: TA{data}
where:
{data} is a constant or expression representing the acceleration time in milliseconds
This statement specifies the commanded acceleration time between blended moves (LINEAR and
CIRCLE mode), and from and to a stop for these moves. If global variable I42 is set to 1, it also specifies
the segment time for PVT and SPLINE mode moves. The units are milliseconds, and the range is 0 to
8,388,607 msec (about 2 hours, 20 minutes). Turbo PMAC will round the specified value to the nearest
integer number of milliseconds when executing this command (no rounding is done in storing the value in
the buffer).
Note:
If the coordinate system is not in segmentation mode (Isx13 = 0), make sure the
specified acceleration time (TA or 2*TS) is greater than zero, even if planning to
rely on the maximum acceleration rate parameters (Ixx17). A specified
acceleration time of zero will cause a divide-by-zero error. The minimum
specified time in this case should be TA1 TS0.
If the specified S-curve time (from TS, or Isx88) is greater than half the TA time, the time used for the
acceleration for blended moves will be twice the specified S-curve time.
The acceleration time is also the minimum time for a blended move; if the distance on a feedrate-
specified (F) move is so short that the calculated move time is less than the acceleration time, or the time
of a time-specified (TM) move is less than the acceleration time, the move will be done in the acceleration
time instead. This will slow down the move. If TA controls the move time it must be greater than the
Isx13 time and the I8 period.
Note:
The acceleration time will be extended automatically when any motor in the
coordinate system is asked to exceed its maximum acceleration rate (Ixx17) for a
programmed LINEAR mode move with Isx13=0 (no move segmentation).
A move executed in a program before any TA statement will use the default acceleration time specified by
coordinate system I-variable Isx87.
Examples:
TA100
TA(P20)
TA(45.3+SQRT(Q10))
See Also:
Linear, Circular Blended Moves, Cubic Spline Moves, PVT Moves (Writing and Executing Motion
Programs)
I-variables Ixx17, Isx87, Isx88
Program commands TS, TM
TINIT
Function: Initialize selected transformation matrix
Type: Motion program (PROG and ROT)
Syntax: TINIT
This command initializes the currently selected (with TSEL) transformation matrix for the coordinate
system by setting it to the identity matrix. This makes the rotation angle 0, the scaling 1, and the
displacement 0, so the XYZ points for the coordinate system are as the axis definition statements created
them. Turbo PMAC will still perform the matrix calculations, even though they have no effect. TSEL0
should be used to stop the matrix calculations
The matrix can subsequently be changed with the ADIS, IDIS, AROT, and IROT commands.
Examples:
TSEL 4 ; Select transformation matrix 4
TINIT ; Initialize it to the identity matrix
IROT 71 ; Do incremental rotation/scaling with Q71-Q79
See Also:
Axis Matrix Transformations (Writing and Executing Motion Programs)
On-line command DEFINE TBUF
Program commands TSEL, ADIS, IDIS, AROT, IROT
TM{data}
Function: Set Move Time
Type: Motion program
Syntax: TM{data}
where:
{data} is a floating-point constant or expression representing the move time in milliseconds.
This command establishes the time to be taken by subsequent LINEAR and CIRCLE, mode moves. If
global variable I42 is set to the default value of 0, it also established the time to be taken by subsequent
SPLINE and PVT mode moves. It overrides any previous TM or F statement, and is overridden by any
subsequent TM or F statement. It is irrelevant in RAPID move mode (or in SPLINE or PVT move mode
if I42 is set to 1), but the latest value will stay active through that mode for the next return to TM-
controlled move modes.
For LINEAR and CIRCLE mode moves, the effective move time can range from 0.5 msec to 223 msec
(about 2 hours 20 minutes), with floating-point resolution. For SPLINE and PVT mode moves, the
effective move time can range from 1 servo cycle to 4096 msec (about 4 seconds), with resolution of ¼-
microsecond.
There are several cases in which Turbo PMAC will not use the move time commanded with the TM
statement:
If the specified move time is over the maximum – 2 msec for LINEAR or CIRCLE moves, 4096
23
msec for SPLINE and PVT moves – the move will be executed in the maximum allowed time, at a
higher speed than what was programmed.
If the move time programmed with the TM statement causes any motor in the coordinate system to
exceed its Ixx16 velocity limit (when active), all axes will be slowed so that no motor exceeds its
limit.
If the specified move time is less than the acceleration time currently in force (TA or 2*TS or the time
set by the Ixx17 limit when active), the move will take the full acceleration time instead, and the axes
will move more slowly than specified by the TM command. If the acceleration time is 0, the
minimum permitted move time is 0.5 msec.
If the % override value for the coordinate system is at other than %100 when the move is executed,
the move will not execute in the specified time. The actual move time varies in inverse proportion to
the % value.
If TM controls the move time it must be greater than the Isx13 time and the I8 period. Otherwise, the
program can fail on a run-time error because the calculations for the next move may not be completed in
time.
Examples:
TM30
TM47.635
TM(P1/3)
See Also:
Linear and Circular Blended Moves (Writing and Executing Motion Programs)
I-variables I8, Ixx16, Ixx17, Isx13, Isx89
Program commands F, TA, TS, LINEAR, CIRCLE
TR{data}
Function: Set 3D-comp tool-shaft radius magnitude
Type: Motion program (PROG and ROT)
Syntax: TR{data}
where:
{data} is a signed floating-point constant or expression representing the magnitude of the tool’s
shaft radius
This statement sets the magnitude of the radius of the cutting tool’s shaft for three-dimensional cutter-
radius compensation, expressed in the user units of the X, Y, and Z axes. It is used in conjunction with
the cutter’s end radius declared by the CCR statement. This function is often part of the D tool data used
in the machine-tool standard RS-274 (G) code.
The default value of the tool-shaft radius at power-up/reset is zero. If the tool-shaft radius declared with
the TR statement is less than the cutter-end radius set with the CCR statement, the CCR value will be used
instead for the tool-shaft radius.
In operation of 3D compensation, after an offset of the cutter-end radius along the surface-normal vector,
there is a second offset of the tool-shaft radius minus the cutter-end radius, perpendicular to the tool-
orientation vector.
The tool-shaft value declared with the TR statement affects all subsequent moves with 3D compensation
active, until another tool-shaft radius value is declared.
Examples:
TR1.356
TR(Q10)
See Also:
Three-Dimensional Compensation
Program commands CC3, CCR{data}, NX{data}, NY{data}, NZ{data}, TX{data},
TY{data}, TZ{data}
TS{data}
Function: Set S-Curve Acceleration Time
Type: Motion program (PROG and ROT)
Syntax: TS{data}
where:
{data} is a positive constant or expression representing the S-curve time in milliseconds.
This command specifies the time, at both the beginning and end of the total acceleration time, in LINEAR
and CIRCLE mode blended moves that is spent in S-curve acceleration. The units are milliseconds.
Turbo PMAC will round the specified value to the nearest integer number of milliseconds when executing
this command (no rounding is done when storing the value in the buffer).
If TS is zero, the acceleration is constant throughout the TA time and the velocity profile is trapezoidal.
If TS is greater than zero, the acceleration will start at zero and linearly increase through TS time, then
stay constant (for time TC) until TA-TS time, and linearly decrease to zero at TA time (that is,
TA=2TS+TC).
If TS is equal to TA/2, the entire acceleration will be spent in S-curve form (TS values greater than
TA/2 override the TA value; total acceleration time will be 2TS.
Note:
For LINEAR mode moves with Turbo PMAC not in segmentation mode
(Isx13=0), if the rate of acceleration for any motor in the coordinate system
exceeds that motor’s maximum as specified by Ixx17, the acceleration time for all
motors is increased so that no motor exceeds its maximum acceleration rate.
TS does not affect RAPID, PVT, or SPLINE mode moves, but it stays valid for the next return to blended
moves.
Note:
If the coordinate system is not in segmentation mode (Isx13 = 0), make sure the
specified acceleration time (TA or 2*TS) is greater than zero, even if planning to
rely on the maximum acceleration rate parameters (Ixx17). A specified
acceleration time of zero will cause a divide-by-zero error. In this case, the
minimum specified time should be TA1 TS0.
In executing the TS command, Turbo PMAC rounds the specified value to the nearest integer number of
milliseconds (there is no rounding done when storing the command in the buffer).
A blended move executed in a program before any TS statement will use the default S-curve time
specified by coordinate system I-variable Isx88.
Examples:
TS20
TS(Q17)
TS(39.32+P43)
See Also:
Linear and Circular Blended Moves (Writing and Executing Motion Programs)
I-variables Isx13, Ixx17, Ixx21, Isx87, Isx88
Program commands TA, TM, F, LINEAR, CIRCLE
TSELECT{constant}
Function: Select active transformation matrix for X, Y, and Z axes
Type: Motion program (PROG and ROT)
Syntax: TSELECT{constant}
TSEL{constant}
where:
{constant} is an integer representing the number of the matrix to be used
This command selects the specified matrix for use as the active transformation matrix for the X, Y, and Z
axes of the coordinate system running the motion program. This matrix can then be modified using the
TINIT, ADIS, AROT, IDIS, and IROT commands to perform translations, rotations, and scaling of the
three axes. This matrix will be used until another one is selected.
This matrix must already have been created with the on-line DEFINE TBUF command. That command
specifies the number of matrices to create and it must have specified a number at least as high as the
number used in TSEL (a matrix that has not been created cannot be selected).
TSEL0 deselects all transformation matrices, saving calculation time.
Examples:
DEFINE TBUF 5 ; Create 5 transformation matrices
OPEN PROG 10 CLEAR
...
TSEL 3 ; Select transformation matrix 3 (of 5)
TINIT ; Make matrix 3 the identity matrix
See Also:
Axis Matrix Transformations (Writing and Executing Motion Programs)
On-line command DEFINE TBUF
Program commands AROT, IROT, ADIS, IDIS, TINIT
TX{data}
Function: Set 3D-comp tool-orientation vector X-component
Type: Motion program (PROG and ROT)
Syntax: TX{data}
where:
{data} is a signed floating-point constant or expression representing the X-component of the tool-
orientation vector
This statement specifies the X-component of the tool-orientation vector used for three-dimensional cutter-
radius compensation. This value is used along with the Y and Z-components specified by the TY{data}
and TZ{data} statements, respectively, to compute the orientation of the vector.
The total magnitude of the tool-orientation vector specified with these three components does not matter,
although typically a unit-magnitude vector is specified. The relative magnitudes (including signs) of the
three components are what determine the orientation of the vector. The direction sense of the vector does
not matter – base to tip, or tip to base. Generally, all three components are declared together on one line;
if only one or two components are declared, the others are left at their old values, possibly leading to
unpredictable results.
The tool-orientation vector affects the compensation for the end-point of the move commanded on the
same line as the tool-orientation vector. It also affects the compensation for subsequent moves until
another tool-orientation vector is declared. In typical use, a new tool-orientation vector is declared with
each move, so the vector only affects the move on the same line in this case.
Examples:
X3.76 Y8.29 Z-4.83 A34.32 C-29.75 NX0.866 NY0 NZ-0.5 TX-0.707 TY0.707 TZ0
See Also:
Three-Dimensional Compensation
Program commands CC3, CCR{data}, NX{data}, NY{data}, NZ{data}, TR{data},
TY{data}, TZ{data}
TY{data}
Function: Set 3D-comp tool-orientation vector Y-component
Type: Motion program (PROG and ROT)
Syntax: TY{data}
where:
{data} is a signed floating-point constant or expression representing the Y-component of the tool-
orientation vector
This statement specifies the Y-component of the tool-orientation vector used for three-dimensional cutter-
radius compensation. This value is used along with the X and Z-components specified by the TX{data}
and TZ{data} statements, respectively, to compute the orientation of the vector.
The total magnitude of the tool-orientation vector specified with these three components does not matter,
although typically a unit-magnitude vector is specified. The relative magnitudes (including signs) of the
three components are what determine the orientation of the vector. The direction sense of the vector does
not matter – base to tip, or tip to base. Generally, all three components are declared together on one line;
if only one or two components are declared, the others are left at their old values, possibly leading to
unpredictable results.
The tool-orientation vector affects the compensation for the end-point of the move commanded on the
same line as the tool-orientation vector. It also affects the compensation for subsequent moves until
another tool-orientation vector is declared. In typical use, a new tool-orientation vector is declared with
each move, so the vector only affects the move on the same line in this case.
Examples:
X3.76 Y8.29 Z-4.83 A34.32 C-29.75 NX0.866 NY0 NZ-0.5 TX-0.707 TY0.707 TZ0
See Also:
Three-Dimensional Compensation
Program commands CC3, CCR{data}, NX{data}, NY{data}, NZ{data}, TR{data},
TX{data}, TZ{data}
TZ{data}
Function: Set 3D-comp tool-orientation vector Z-component
Type: Motion program (PROG and ROT)
Syntax: TZ{data}
where:
{data} is a signed floating-point constant or expression representing the Z-component of the tool-
orientation vector
This statement specifies the Z-component of the tool-orientation vector used for three-dimensional cutter-
radius compensation. This value is used along with the X and Y-components specified by the
TX{data} and TY{data} statements, respectively, to compute the orientation of the vector.
The total magnitude of the tool-orientation vector specified with these three components does not matter,
although typically a unit-magnitude vector is specified. The relative magnitudes (including signs) of the
three components are what determine the orientation of the vector. The direction sense of the vector does
not matter – base to tip, or tip to base. Generally, all three components are declared together on one line;
if only one or two components are declared, the others are left at their old values, possibly leading to
unpredictable results.
The tool-orientation vector affects the compensation for the end-point of the move commanded on the
same line as the tool-orientation vector. It also affects the compensation for subsequent moves until
another tool-orientation vector is declared. In typical use, a new tool-orientation vector is declared with
each move, so the vector only affects the move on the same line in this case.
Examples:
X3.76 Y8.29 Z-4.83 A34.32 C-29.75 NX0.866 NY0 NZ-0.5 TX-0.707 TY0.707 TZ0
See Also:
Three-Dimensional Compensation
Program commands CC3, CCR{data}, NX{data}, NY{data}, NZ{data}, TR{data},
TX{data}, TY{data}
U{data}
Function: U-Axis Move
Type: Motion program
Syntax: U{data}
where:
{data} is a floating point constant or expression representing the position or distance in user units
for the U-axis.
This command causes a move of the U-axis. (See {axis}{data} description, above.) If it follows a
subroutine call (explicit or with PRELUDE) on a program line, it can be used instead to pass its value to
the subroutine through use of the READ command.
Examples:
U10
U(P17+2.345)
X20 U20
U(COS(Q10)) V(SIN(Q10))
G77 U40
See Also:
Program commands {axis}{data}, A, B, C, V, W, X, Y, Z, CALL, PRELUDE, READ
UNLOCK{constant}
Function: Clear process locking bit
Type: Motion and PLC programs
Syntax: UNLOCK{constant}
where:
{constant} is an integer from 0 to 7 representing the number of the locking bit
The UNLOCK command permits the user to clear one of the eight process locking bits in Turbo PMAC,
releasing the process for other tasks. These locking bits can prevent conflicts between tasks of different
priorities attempting to manipulate the same register. On-line commands and PLCs 1-31 are background
tasks; motion programs and PLC 0 are higher-priority foreground tasks.
The user can check the status of a locking bit with the LOCK command.
The status of locking bits 0-7 is reported as bits 4-11, respectively, of I4904.
If no motion program buffer or PLC program buffer is open when this command is issued, this command
will be executed immediately as an on-line command.
Examples:
P10=1 ; Assume locked to start
WHILE(P10=1) ; Loop until unlocked
LOCK4,P10 ; Check status of locking bit 4
ENDWHILE
M1=M1^1 ; Invert Machine Output 1
UNLOCK4 ; Release process 4 for other tasks
V{data}
Function: V-Axis Move
Type: Motion program (PROG and ROT)
Syntax: V{data}
where:
{data} is a floating point constant or expression representing the position or distance in user units
for the V-axis.
This command causes a move of the V-axis. (See {axis}{data} description, above.) If it follows a
subroutine call (explicit or with PRELUDE) on a program line, it can be used instead to pass its value to
the subroutine through use of the READ command.
Examples:
V20
U56.5 V(P320)
Y10 V10
V(SQRT(Q20*Q20+Q21*Q21))
CALL300 V(Q400)
See Also:
Program commands {axis}{data}, A, B, C, U, W, X, Y, Z, CALL, PRELUDE, READ
W{data}
Function: W-Axis Move
Type: Motion program
Syntax: W{data}
where:
{data} is a floating point constant or expression representing the position or distance in user units
for the W-axis.
This command causes a move of the W-axis. (See {axis}{data} description, above.) If it follows a
subroutine call (explicit or with PRELUDE) on a program line, it can be used instead to pass its value to
the subroutine through use of the READ command.
Examples:
W5
W(P10+33.5)
Z10 W10
W(ABS(Q22*Q22))
M50 W1
See Also:
Program commands {axis}{data}, A, B, C, U, V, X, Y, Z, CALL, PRELUDE, READ
WAIT
Function: Suspend program execution
Type: Motion program (PROG and ROT)
Syntax: WAIT
This command may be used on the same line as a WHILE condition to hold up execution of the program
until the condition goes false. When the condition goes false, program execution resumes on the next
line. Turbo PMAC will not blend moves through a true WHILE…WAIT loop.
Use of the WAIT statement allows indefinite pauses without the need for repeated use of a servo
command (e.g. DWELL or DELAY) to eat up the time. However, it is impossible to predict how long the
pause will be.
WAIT permits a faster resumption of the program upon the WHILE condition going false. Also, the
program timer is halted when WAITing, which allows the “in-position” bit to go true (which can be used
to trigger an action, or the next move).
Since Turbo PMAC executes a WHILE ({condition}) WAIT statement every Real Time Interrupt
until the condition goes false, it is essentially the same as a PLC0. This could use excessive processor
time and in severe cases trip the watchdog timer on Turbo PMAC’s that simultaneously run several
motion programs that use WAIT statements and or large PLC0 programs. For example, if the condition
needs to be checked only every 20 msec and not every Real Time Interrupt, consider using a DWELL
command to regulate the execution time of the WHILE loop.
Examples:
WHILE ({condition})
DWELL20
ENDW
WHILE (M11=0) WAIT ; Pause here until Machine Input 1 set
WHILE (M187=0) WAIT ; Pause here until all axes in-position
M1=1 ; Turn on Output 1 to activate punch
See Also:
I-variable Ixx28
Program commands DWELL, DELAY, STOP
WHILE({condition})
Function: Conditional looping
Type: Motion program (PROG only); PLC program
Syntax: WHILE ({condition})
WHILE ({condition}) {action}
where:
{condition} consists of one or more sets of {expression} {comparator}
{expression}, joined by logical operators AND or OR.
{action} is a program command
This statement allows repeated execution of a statement or series of statements as long as the condition is
true. It is Turbo PMAC’s only looping construct. It can take two forms:
(Valid in motion program only) With a statement following on the same line, it will repeatedly execute
that statement as long as the condition is true. No ENDWHILE is used to terminate the loop.
WHILE ({condition}) {action}
(Valid in motion and PLC programs) With no statement following on the same line, it will execute
statements on subsequent lines down to the next ENDWHILE statement.
WHILE ({condition})
{statement}
[{statement}
...]
ENDWHILE
If a WHILE loop in a motion program has no move, DWELL, or DELAY inside, Turbo PMAC will attempt
to execute the loop twice (while true) each real-time interrupt cycle (stopped from more loops only by the
double-jump-back rule), much like a PLC0. This can starve the background tasks for time, possibly even
tripping the watchdog timer. Turbo PMAC will not attempt to blend moves through such an “empty”
WHILE loop if it finds the loop condition true twice or more. A WHILE…WAIT loop will operate this way
on a single jump back.
In PLC programs, extended compound WHILE conditions can be formed on multiple program lines
through use of AND and OR commands on the program lines immediately following the WHILE command
itself (this structure is not available in motion programs). Conditions in each program line can be either
simple or compound. AND and OR operations within a program line take precedence over AND and OR
operations between lines.
Examples:
WHILE (P20=0)
...
ENDWHILE
WHILE (Q10<5 AND Q11>1)
...
ENDWHILE
WHILE (M11=0) WAIT ; sit until input goes true
INC
WHILE (M11=0 OR M12=0) X100 ; increment until 2 inputs true
To do the equivalent of a For/Next loop:
P1=0 ; Initialize loop counter
WHILE (P1<10) ; Loop until counter exceeds limit
X1000 ; Perform action to be repeated
P1=P1+1 ; Increment loop counter
ENDWHILE ; Loop back
To do a timed wait in a PLC program, use the servo cycle counter as timer
P90=16777216 ; Counter rollover value (2^24)
P91=M0 ; Store starting value of M0 (X:$0) counter
P92=0 ; Time elapsed so far
WHILE (P92<P93) ; Loop until past specified time
P92=(M0-P91)%P90 ; Calculate time elapsed
; Modulo (%) operation to handle rollover
ENDWHILE ; Loop back
To do extended compound conditions in a PLC program
WHILE (M11=1 AND M12=1)
OR (M13=1 AND M14=1)
AND (P1>0)
...
ENDWHILE
See Also:
Program Logic (Writing and Executing Motion Programs, Writing a PLC Program)
How Turbo PMAC Executes a Motion Program (Writing and Executing Motion Programs)
Program commands AND, OR, IF, ELSE, ENDIF, ENDWHILE
X{data}
Function: X-Axis Move
Type: Motion program
Syntax: X{data}
where:
{data} is a floating point constant or expression representing the position or distance in user units
for the X-axis.
This command causes a move of the X-axis. (See {axis}{data} description, above.) If it follows a
subroutine call (explicit or with PRELUDE) on a program line, it can be used instead to pass its value to
the subroutine through use of the READ command.
Examples:
X10
X15 Y20
X(P1) Y30
X(Q10*COS(Q1)) Y(Q10*SIN(Q1))
X3.76 Z2.92 I0.075 K3.42
CALL100 X5 Y10
See Also:
Program commands {axis}{data}, A, B, C, U, V, W, Y, Z, CALL, PRELUDE, READ
Y{data}
Function: Y-Axis Move
Type: Motion program
Syntax: Y{data}
where:
{data} is a floating point constant or expression representing the position or distance in user units
for the Y-axis.
This command causes a move of the Y-axis. (See {axis}{data} description, above.) If it follows a
subroutine call (explicit or with PRELUDE) on a program line, it can be used instead to pass its value to
the subroutine through use of the READ command.
Examples:
Y50
Y(P100)
X35 Y75
Y-0.221 Z3.475
Y(ABS(P3+P4)) A(INT(P3-P4))
G73 Y20
See Also:
Program commands {axis}{data}, A, B, C, U, V, W, X, Z, CALL, PRELUDE, READ
Z{data}
Function: Z-Axis Move
Type: Motion program
Syntax: Z{data}
where:
{data} is a floating point constant or expression representing the position or distance in user units
for the Z-axis.
This command causes a move of the Z-axis. (See {axis}{data} description, above.) If it follows a
subroutine call (explicit or with PRELUDE) on a program line, it can be used instead to pass its value to
the subroutine through use of the READ command.
Examples:
Z20
Z(Q25)
X10 Y20 Z30
Z23.4 R10.5
Z(P301+2*P302/P303)
See Also:
Program commands {axis}{data}, A, B, C, U, V, W, X, Y, CALL, PRELUDE, READ
If the divisor is equal to 0, the result will saturate at +/-247 (+/-223 for an integer division in a compiled
PLC). No error will be reported, and the program will not stop. It is the programmer’s responsibility to
check for possible division-by-zero errors.
Execution time, 80 MHz CPU: 3.6 µsec interpreted, 1.6 µsec compiled floating-point, 0.73 µsec compiled
fixed-point
Examples:
(L1 and M1 are integer variables; P1 is a floating-point variable)
Command Result
P1=10*2/3 6.666666667
P1=10*(2/3) 6.666666667
M1=10*2/3 7
M1=10*(2/3) 7
L1=10*2/3 7
L1=10*(2/3) 10
%
Function: Modulo (remainder)
The % sign causes the calculation of the remainder due to the division of the numerical value preceding it
by the numerical value following it. Unless the division is executed in a compiled PLC on a line with
only L-variables and integers, the division operation is always a floating-point calculation (even if integer
values are used). The quotient is computed as a floating-point value, then truncated to the next lowest
(i.e. toward -∞) integer so the remainder can be computed.
If the divisor “n” is a positive value, the modulo result is in the range 0 ≤ Result < n. If the divisor “n” is
a negative value, the modulo result is in the range –n ≤ Result < n.
Multiplication, division, modulo (remainder), and bit-by-bit and operations have higher priority than
addition, subtraction, bit-by-bit or, and bit-by-bit exclusive-or operations. Operations of the same priority
are implemented from left to right.
If the divisor is equal to 0, the division will saturate and the modulo result will be 0. No error will be
reported, and the program will not stop. It is the programmer’s responsibility to check for possible
division-by-zero errors.
Execution time, 80 MHz CPU: 3.3 µsec interpreted, 1.4 µsec compiled floating-point, 0.78 µsec compiled
fixed-point
Examples:
Operation Result
11%4 3
-11%4 1
11%-4 3
-11%-4 -3
3%2.5 0.5
-3%2.5 2
3%-2.5 -2
-3%-2.5 2
&
Function: Bit-by-bit and
The & sign implements the bit-by-bit logical and of the numerical value preceding it and the numerical
value following it. A given bit of the result is equal to 1 if and only if the matching bits of both operands
are equal to 1. The operation is done both on integer bits and fractional bits (if any).
Multiplication, division, modulo (remainder), and bit-by-bit and operations have higher priority than
addition, subtraction, bit-by-bit or, and bit-by-bit exclusive-or operations. Operations of the same priority
are implemented from left to right.
This bit-by-bit and operator that logically combines the bits of numerical values is not to be confused with
the AND command, which logically combines conditions.
Execution time, 80 MHz CPU: 3.4 µsec interpreted, 1.4 µsec compiled floating-point, 0.10 µsec compiled
fixed-point
Examples:
Operation Result
3&1 1
3&2 2
3&3 3
3&4 0
3&-3 1
0.875&1.75 0.75
0.875&-1.75 0.25
|
Function: Bit-by-bit or
The | sign implements the bit-by-bit logical o” of the numerical value preceding it and the numerical
value following it. A given bit of the result is equal to 1 if the matching bit of either operand is equal to
1. The operation is done both on integer bits and fractional bits (if any).
Multiplication, division, modulo (remainder), and bit-by-bit and operations have higher priority than
addition, subtraction, bit-by-bit or, and bit-by-bit exclusive-or operations. Operations of the same priority
are implemented from left to right.
This bit-by-bit or operator that logically combines the bits of numerical values is not to be confused with
the OR command, which logically combines conditions.
Execution time, 80 MHz CPU: 3.2 µsec interpreted, 1.4 µsec compiled floating-point, 0.10 µsec compiled
fixed-point
Examples:
Operation Result
4|3 7
3|2 3
3|3 3
$F0|$4 $F4
3|-3 -1
0.5|0.375 0.875
0.875|-1.75 -0.375
^
Function: Bit-by-bit exclusive or
The ^ sign implements the bit-by-bit logical exclusive or (xor) of the numerical value preceding it and the
numerical value following it. A given bit of the result is equal to 1 if and only if the matching bits of the
two operands are different from each other. The operation is done both on integer bits and fractional bits
(if any).
Multiplication, division, modulo (remainder), and bit-by-bit and operations have higher priority than
addition, subtraction, bit-by-bit or, and bit-by-bit exclusive-or operations. Operations of the same priority
are implemented from left to right.
Execution time, 80 MHz CPU: 3.1 µsec interpreted, 1.4 µsec compiled floating-point, 0.10 µsec compiled
fixed-point
Examples:
Operation Result
2^1 3
2^2 0
5^7 2
$AA^$55 $FF
3^-3 -2
0.5^0.875 0.375
Mathematical Functions
ABS
Function: Absolute value
Syntax: ABS({expression})
Domain: All real numbers
Domain units: User-determined
Range: Non-negative real numbers
Range units: User-determined
ABS implements the absolute value, or magnitude, function, of the mathematical expression contained
inside the following parentheses.
Execution time, 80 MHz CPU: 3.1 µsec interpreted, 0.6 µsec compiled
Examples:
P8=ABS(P7) ; Computes magnitude of P7
IF(Q200!=0) ; Divide by 0 check
Q240=ABS(Q200)/Q200 ; Computes sign (-1 or 1) of Q200
ELSE
Q240=0 ; Sign value is 0
ENDIF
ACOS
Function: Trigonometric arc-cosine
Syntax: ACOS({expression})
Domain: -1.0 to +1.0
Domain units: none
Range: 0 to Pi radians (0 to 180 degrees)
Range units: Radians/degrees
ACOS implements the inverse cosine, or arc-cosine, function, of the mathematical expression contained
inside the following parentheses.
This function returns values in degrees if I15 is set to the default value of 0; it returns values in radians if
I15 is set to 1.
If the argument inside the parentheses is outside of the legal domain of –1.0 to +1.0, an arbitrary value
will be returned. No error will be reported, and the program will not stop. It is the programmer’s
responsibility to check for possible domain errors.
Execution time, 80 MHz CPU: 6.7 µsec interpreted, 4.3 µsec compiled
Examples:
P50=ACOS(P48/P49) ; Computes angle whose cos is P48/P49
C(ACOS(Q70/10)) ; Move C axis to specified angle
ASIN
Function: Trigonometric arc-sine
Syntax: ASIN({expression})
Domain: -1.0 to +1.0
Domain units: none
Range: -π /2 to +π/2 radians (-90 to +90 degrees)
Range units: Radians/degrees
ASIN implements the inverse sine, or arc-sine, function, of the mathematical expression contained inside
the following parentheses.
This function returns values in degrees if I15 is set to the default value of 0; it returns values in radians if
I15 is set to 1.
If the argument inside the parentheses is outside of the legal domain of –1.0 to +1.0, an arbitrary value
will be returned. No error will be reported, and the program will not stop. It is the programmer’s
responsibility to check for possible domain errors.
Execution time, 80 MHz CPU: 7.0 µsec interpreted, 4.7 µsec compiled
Examples:
P50=ASIN(P48/P49) ; Computes angle whose sin is P48/P49
C(ASIN(Q70/10)) ; Move C axis to specified angle
ATAN
Function: Trigonometric arc-tangent
Syntax: ATAN({expression})
Domain: All real numbers
Domain units: none
Range: -Pi/2 to +Pi/2 radians (-90 to +90 degrees)
Range units: Radians/degrees
ATAN implements the standard inverse tangent, or arc-tangent, function, of the mathematical expression
contained inside the following parentheses. This standard arc-tangent function returns values only in the
+/-90-degree range; if a full +/-180-degree range is desired, the ATAN2 function should be used instead.
This function returns values in degrees if I15 is set to the default value of 0; it returns values in radians if
I15 is set to 1.
Execution time, 80 MHz CPU: 5.9 µsec interpreted, 3.5 µsec compiled
Examples:
P50=ATAN(P48/P49) ; Computes angle whose tan is P48/P49
C(ATAN(Q70/10)) ; Move C axis to specified angle
ATAN2
Function: Two-argument trigonometric arc-tangent
Syntax: ATAN2({expression})
Domain: All real numbers in both arguments
Domain units: none
Range: -Pi to +Pi radians (-180 to +180 degrees)
Range units: Radians/degrees
ATAN2 implements the expanded (two-argument) inverse tangent, or arc-tangent, function, of the
mathematical expression contained inside the following parentheses, and the value of variable Q0 for the
coordinate system used. (If this function is used inside a PLC program, make sure the desired coordinate
system has been selected with the ADDRESS command.)
This expanded arc-tangent function returns values in the full +/-180-degree range; if only the +/-90-
degree range is desired, the standard ATAN function should be used instead. The ATAN2 function makes
use of the signs of both arguments, as well as the ratio of their magnitudes, to extend the range to a full
360 degrees. The value in the parentheses following ATAN2 is the “sine” argument; the value in Q0 is the
“cosine” argument.
This function returns values in degrees if I15 is set to the default value of 0; it returns values in radians if
I15 is set to 1.
If both arguments for the ATAN2 function are equal to exactly 0.0, an internal division-by-zero error will
result, and an arbitrary value will be returned. No error will be reported, and the program will not stop. It
is the programmer’s responsibility to check for these possible domain errors.
Execution time, 80 MHz CPU: 5.1 µsec interpreted, 3.5 µsec compiled
Examples:
Q30=-0.707 ; Cosine argument
Q31=-0.707 ; Sine argument
Q32=ATAN(Q31/Q30) ; Single-argument arctangent
Q32 ; Query resulting value
45 ; Returns value in +/-90 range
Q0=Q30 ; Prepare cosine for ATAN2
Q33=ATAN2(Q31) ; Two-argument arctangent
Q33 ; Query resulting value
-135 ; Note different result
Q0=M163-M161 ; X target – X present position
Q1=M263-M261 ; Y target – Y present position
IF (ABS(Q0)>0.001 OR ABS(Q1)>0.001) ; Div by 0 check
Q2=ATAN2(Q1) ; Calculate directed angle
ENDIF
COS
Function: Trigonometric cosine
Syntax: COS({expression})
Domain: All real numbers
Domain units: Radians/degrees
Range: -1.0 to +1.0
Range units: none
COS implements the trigonometric cosine function of the mathematical expression contained inside the
following parentheses.
This function interprets its argument in degrees if I15 is set to the default value of 0; it interprets its
argument in radians if I15 is set to 1.
Execution time, 80 MHz CPU: 5.6 µsec interpreted, 3.2 µsec compiled
Examples:
P60=COS(30) ; Computes cosine of 30
X(Q80*COS(Q81)) ; Move X axis to calculated value
EXP
Function: Exponentiation (ex)
Syntax: EXP({expression})
Domain: All real numbers
Domain units: User-determined
Range: Positive real numbers
Range units: User-determined
EXP implements the standard exponentiation function of the mathematical expression contained inside
the following parentheses, raising e to the power of this expression.
To implement the yx function, use ex ln(y) instead.
Execution time, 80 MHz CPU: 5.6 µsec interpreted, 3.2 µsec compiled
Examples:
P20=EXP(P19) ; Raises e to the power of P19
P3=EXP(P2*LN(P1)) ; Raises P1 to the power of P2
INT
Function: Truncation to integer
Syntax: INT({expression})
Domain: All real numbers
Domain units: User-determined
Range: All integers
Range units: User-determined
INT implements the truncation to integer function of the mathematical expression contained inside the
following parentheses. The truncation is always done in the negative direction.
Note that while the result is an integer number, it is still represented as a floating-point value.
Execution time, 80 MHz CPU: 3.3 µsec interpreted, 1.0 µsec compiled
Examples:
P50=2.5 ;
P51=INT(P50) ; Take INT of positive value
P51 ; Query resulting value
2 ; Next lower integer value
P52=INT(-P50) ; Take INT of negative value
P52 ; Query resulting value
-3 ; Next lower integer value
LN
Function: Natural logarithm
Syntax: EXP({expression})
Domain: Positive real numbers
Domain units: User-determined
Range: All real numbers
Range units: User-determined
LN implements the natural logarithm (logarithm base “e”) function of the mathematical expression
contained inside the following parentheses.
To implement the logarithm using another base, divide the natural logarithm of the value by the natural
logarithm of the base (logyx = ln x / ln y). The natural logarithm of 10 is equal to 2.302585.
If the argument inside the parentheses is outside of the legal domain of positive numbers, a 0 value will be
returned. No error will be reported, and the program will not stop. It is the programmer’s responsibility
to check for possible domain errors.
Execution time, 80 MHz CPU: 4.3 µsec interpreted, 1.4 µsec compiled
Examples:
P19=LN(P20) ; Takes the natural log of P20
P6=LN(P5)/LN(10) ; Takes the log base 10 of P5
SIN
Function: Trigonometric sine
Syntax: SIN({expression})
Domain: All real numbers
Domain units: Radians/degrees
Range: -1.0 to +1.0
Range units: none
SIN implements the trigonometric sine function of the mathematical expression contained inside the
following parentheses.
This function interprets its argument in degrees if I15 is set to the default value of 0; it interprets its
argument in radians if I15 is set to 1.
Execution time, 80 MHz CPU: 5.6 µsec interpreted, 3.2 µsec compiled
Examples:
P60=SIN(30) ; Computes cosine of 30
Y(Q80*SIN(Q81)) ; Move Y axis to calculated value
SQRT
Function: Square root
Syntax: SQRT({expression})
Domain: Non-negative real numbers
Domain units: User-determined
Range: Non-negative real numbers
Range units: User-determined
SQRT implements the positive square-root function of the mathematical expression contained inside the
following parentheses.
If the argument inside the parentheses is outside of the legal domain of non-negative numbers, an
arbitrary value will be returned. No error will be reported, and the program will not stop. It is the
programmer’s responsibility to check for possible domain errors.
Execution time, 80 MHz CPU: 3.7 µsec interpreted, 1.4 µsec compiled
Examples:
P19=SQRT(P20) ; Takes the square root of P20
P50=SQRT(P8*P8+P9*P9) ; Pythagorean theorem calculation
TAN
Function: Trigonometric tangent
Syntax: TAN({expression})
Domain: All real numbers except +/-(2N-1)*90 degrees
Domain units: Radians/degrees
Range: All real numbers
Range units: none
TAN implements the trigonometric tangent function of the mathematical expression contained inside the
following parentheses.
This function interprets its argument in degrees if I15 is set to the default value of 0; it interprets its
argument in radians if I15 is set to 1.
If the argument inside the parentheses approaches +/-(2N-1)*90 degrees (+/-90, 270, 450, etc.), the TAN
function will blow up and a very large value will be returned. If the argument inside the parentheses is
exactly equal to one of these quantities, an internal division-by-zero error will occur and the resulting
value will saturate at +/-247. No error will be reported, and the program will not stop. It is the
programmer’s responsibility to check for possible domain errors.
Execution time, 80 MHz CPU: 6.8µsec interpreted, 4.5 µsec compiled
Examples:
P60=TAN(30) ; Computes cosine of 30
Y(Q80*TAN(Q81)) ; Move Y axis to calculated value
Motor # 1 2 3 4 5 6 7 8
Address $0000Bx $00013x $0001Bx $00023x $0002Bx $00033x $0003Bx $00043x
Motor # 9 10 11 12 13 14 15 16
Address $0004Bx $00053x $0005Bx $00063x $0006Bx $00073x $0007Bx $00083x
Motor # 17 18 19 20 21 22 23 24
Address $0008Bx $00093x $0009Bx $000A3x $000ABx $000B3x $000BBx $000C3x
Motor # 25 26 27 28 29 30 31 32
Address $000CBx $000D3x $000DBx $000E3x $000EBx $000F3x $000FBx $00103x
Communication Buffers
X/Y:$001900 - $0019FF Foreground Program Command/Response Buffers
X/Y:$001A00 - $001AFF Background PLC Command/Response Buffers
X/Y:$001B00 - $001BFF DPRAM Command/Response Buffers
X/Y:$001C00 - $001CFF Auxiliary Serial Command/Response Buffers
X/Y:$001D00 - $001DFF MACRO Master-to-Master Command/Response Buffers
X/Y:$001E00 - $001FFF Synchronous M-variable queue (non-lookahead)
(>= V1.939 only; at X/Y:$003600 - $0037FF in older)
X/Y:$001E00 - $001EFF Main Serial Command/Response Buffers
(<= V1.938 only; at X/Y:$003600 - $0036FF in newer)
X/Y:$001F00 - $001FFF Bus Command/Response Buffers
(<= V1.938 only; at X/Y:$003700 - $0037FF in newer)
Coordinate System Registers
C. S. # 1 2 3 4 5 6 7 8
Address $00200x $00210x $00220x $00230x $00240x $00250x $00260x $00270x
C. S. # 9 10 11 12 13 14 15 16
Address $00280x $00290x $002A0x $002B0x $002C0x $002D0x $002E0x $002F0x
Y:$002x01 C.S. time base active address (from Isx93 or hold [=$3202])
X:$002x02 C.S. actual slew-limited time base value (units of I10)
Y:$002x02 C.S. actual time base slew rate (from Isx94 or Isx95)
X:$002x03 C.S. feed hold slew rate (Isx95)
Y:$002x03 C.S. time base slew rate (Isx94)
D:$002x04 C.S. motor definition word
X:$002x05 C.S. S-curve time (Isx88, TS)
Y:$002x05 C.S. acceleration time (Isx87, TA)
L:$002x06 C.S. feedrate / move time (Isx89, F, TM)
L:$002x07 C.S. velocity time units (Isx90)
D:$002x08 C.S. PRELUDE command buffer
X:$002x09 C.S. coordinate transformation matrix number
Y:$002x09 C.S. PRELUDE command stack pointer
X/Y:$002x0A - $002x0E C.S. execution pointers
L:$002x0F C.S. cutter compensation radius (from CCR)
C. S. # 1 2 3 4 5 6 7 8
Address $00201x $00211x $00221x $00231x $00241x $00251x $00261x $00271x
C. S. # 9 10 11 12 13 14 15 16
Address $00281x $00291x $002A1x $002B1x $002C1x $002D1x $002E1x $002F1x
C. S. # 1 2 3 4 5 6 7 8
Address $00203x $00213x $00223x $00233x $00243x $00253x $00263x $00273x
C. S. # 9 10 11 12 13 14 15 16
Address $00283x $00293x $002A3x $002B3x $002C3x $002D3x $002E3x $002F3x
The maximum number of errors this register can hold is 4. This number
of errors is compared to the tolerable number of errors defined by I81.
Buffer Pointers
X/Y:$003600 - $0036FF Main Serial Command/Response Buffers
(>= V1.939 only: at X/Y:$001E00 - $001EFF in older)
X/Y:$003700 - $0037FF Bus Command/Response Buffers
(>= V1.939 only: at X/Y:$001F00 - $001FFF in older)
X/Y:$003600 - $0037FF Synchronous M-variable queue (non-lookahead)
(<= V1.938 only; at X/Y:$001E00 - $001FFF in newer)
Commutation Sine Table
X:$003800 – $003FFF Commutation cos table [223*cos((address-$3800)*360o/2048)]
Y:$003800 – $003FFF Commutation sine table [223*sin((address-$3800)*360o/2048)]
Note:
Addresses specified with ‘0x’ prefix are host-computer address offsets from the
base address of the DPRAM, as set by I92, I93, I94, and I97 for the VME bus, by
I93 and I94 for the ISA and PC/104 buses, by the operating system for PCI bus, or
by the communications microcontroller for the USB and Ethernet links.
(Note: Setting Bit 9 and 8 together creates Jog Stop (J/) command)
Command is executed on setting matching enable bit of Y:$060000.
Motor # 1 2 3 4 5 6 7 8
Host 0x0074 0x00A4 0x00D4 0x0104 0x0134 0x0164 0x0194 0x01C4
Address
Address $06001D $060029 $060035 $060041 $06004D $060059 $060065 $060071
Motor # 9 10 11 12 13 14 15 16
Host 0x01F4 0x0224 0x0254 0x0284 0x02B4 0x02E4 0x0314 0x0344
Address
Address $06007D $060089 $060095 $0600A1 $0600AD $0600B9 $0600C5 $0600D1
Motor # 17 18 19 20 21 22 23 24
Host 0x0374 0x03A4 0x03D4 0x0404 0x0434 0x0464 0x0494 0x04C4
Address
Address $0600DD $0600E9 $0600F5 $060101 $06010D $060119 $060125 $060131
Motor # 25 26 27 28 29 30 31 32
Host 0x04F4 0x0524 0x0554 0x0584 0x05B4 0x05E4 0x0614 0x0644
Address
Address $06013D $060149 $060155 $060161 $06016D $060179 $060185 $060191
DP:$060xxx-$060xxx+1 Motor following error (1/[Ixx08*32] cts)
(=CmdPos+MasterPos-CompPos-ActPos)
[from D:$88 + D:$8D + D:$90 – D:$8B, etc.]
Motor # 1 2 3 4 5 6 7 8
Host 0x007C 0x00AC 0x00DC 0x010C 0x013C 0x016C 0x019C 0x01CC
Address
Address $06001F $06002B $060037 $060043 $06004F $06005B $060067 $060073
Motor # 9 10 11 12 13 14 15 16
Host 0x01FC 0x022C 0x025C 0x028C 0x02BC 0x02EC 0x031C 0x034C
Address
Address $06007F $06008B $060097 $0600A3 $0600AF $0600BB $0600C7 $0600D3
Motor # 17 18 19 20 21 22 23 24
Host 0x037C 0x03AC 0x03DC 0x040C 0x043C 0x046C 0x049C 0x04CC
Address
Address $0600DF $0600EB $0600F7 $060103 $06010F $06011B $060127 $060133
Motor # 25 26 27 28 29 30 31 32
Host 0x04FC 0x052C 0x055C 0x058C 0x05BC 0x05EC 0x061C 0x064C
Address
Address $06013F $06014B $060157 $060163 $06016F $06017B $060187 $060193
DP:$060xxx Motor servo command (upper 16 bits have units of 16-bit DAC)
[from X:$BF, etc.]
Motor # 1 2 3 4 5 6 7 8
Host 0x0080 0x00B0 0x00E0 0x0110 0x0140 0x0170 0x01A0 0x01D0
Address
Address $060020 $06002C $060038 $060044 $060050 $06005C $060068 $060074
Motor # 9 10 11 12 13 14 15 16
Host 0x0200 0x0230 0x0260 0x0290 0x02C0 0x02F0 0x0320 0x0350
Address
Address $060080 $06008C $060098 $0600A4 $0600B0 $0600BC $0600C8 $0600D4
Motor # 17 18 19 20 21 22 23 24
Host 0x0380 0x03B0 0x03E0 0x0410 0x0440 0x0470 0x04A0 0x04D0
Address
Address $0600E0 $0600EC $0600F8 $060104 $060110 $06011C $060128 $060134
Motor # 25 26 27 28 29 30 31 32
Host 0x0500 0x0530 0x0560 0x0590 0x05C0 0x05F0 0x0620 0x0650
Address
Address $060140 $06014C $060158 $060164 $060170 $06017C $060188 $060194
Motor # 1 2 3 4 5 6 7 8
Host 0x0084 0x00B4 0x00E4 0x0114 0x0144 0x0174 0x01A4 0x01D0
Address
Address $060021 $06002D $060039 $060045 $060051 $06005D $060069 $060075
Motor # 9 10 11 12 13 14 15 16
Host 0x0204 0x0234 0x0264 0x0294 0x02C4 0x02F4 0x0324 0x0354
Address
Address $060081 $06008D $060099 $0600A5 $0600B1 $0600BD $0600C9 $0600D5
Motor # 17 18 19 20 21 22 23 24
Host 0x0384 0x03B4 0x03E4 0x0414 0x0444 0x0474 0x04A4 0x04D4
Address
Address $0600E1 $0600ED $0600F9 $060105 $060111 $06011D $060129 $060135
Motor # 25 26 27 28 29 30 31 32
Host 0x0504 0x0534 0x0564 0x0594 0x05C4 0x05F4 0x0624 0x0654
Address
Address $060141 $06014D $060159 $060165 $060171 $06017D $060189 $060195
Motor # 1 2 3 4 5 6 7 8
Host 0x0088 0x00B8 0x00E8 0x0118 0x0148 0x0178 0x01A8 0x01D8
Address
Address $060022 $06002E $06003A $060046 $060052 $06005E $06006A $060076
Motor # 9 10 11 12 13 14 15 16
Host 0x0208 0x0238 0x0268 0x0298 0x02C8 0x02F8 0x0328 0x0358
Address
Address $060082 $06008E $06009A $0600A6 $0600B2 $0600BE $0600CA $0600D6
Motor # 17 18 19 20 21 22 23 24
Host 0x0388 0x03B8 0x03E8 0x0418 0x0448 0x0478 0x04A8 0x04D8
Address
Address $0600E2 $0600EE $0600FA $060106 $060112 $06011E $06012A $060136
Motor # 25 26 27 28 29 30 31 32
Host 0x0508 0x0538 0x0568 0x0598 0x05C8 0x05F8 0x0628 0x0658
Address
Address $060142 $06014E $06015A $060166 $060172 $06017E $06018A $060196
Motor # 1 2 3 4 5 6 7 8
Host 0x0090 0x00C0 0x00F0 0x0120 0x0150 0x0180 0x01B0 0x01E0
Address
Address $060024 $060030 $06003C $060048 $060054 $060060 $06006C $060078
Motor # 9 10 11 12 13 14 15 16
Host 0x0210 0x0240 0x0270 0x02A0 0x02D0 0x0300 0x0330 0x0360
Address
Address $060084 $060090 $06009C $0600A8 $0600B4 $0600C0 $0600CC $0600D8
Motor # 17 18 19 20 21 22 23 24
Host 0x0390 0x03C0 0x03F0 0x0420 0x0450 0x0480 0x04B0 0x04E0
Address
Address $0600E4 $0600F0 $0600FC $060108 $060114 $060120 $06012C $060138
Motor # 25 26 27 28 29 30 31 32
Host 0x0510 0x0540 0x0570 0x05A0 0x05D0 0x0600 0x0630 0x0660
Address
Address $060144 $060150 $06015C $060168 $060174 $060180 $06018C $060198
Motor # 1 2 3 4 5 6 7 8
Host 0x0094 0x00C4 0x00F4 0x0124 0x0154 0x0184 0x01B4 0x01E4
Address
Address $060025 $060031 $06003D $060049 $060055 $060061 $06006D $060079
Motor # 9 10 11 12 13 14 15 16
Host 0x0214 0x0244 0x0274 0x02A4 0x02D4 0x0304 0x0334 0x0364
Address
Address $060085 $060091 $06009D $0600A9 $0600B5 $0600C1 $0600CD $0600D9
Motor # 17 18 19 20 21 22 23 24
Host 0x0394 0x03C4 0x03F4 0x0424 0x0454 0x0484 0x04B4 0x04E4
Address
Address $0600E5 $0600F1 $0600FD $060109 $060115 $060121 $06012D $060139
Motor # 25 26 27 28 29 30 31 32
Host 0x0514 0x0544 0x0574 0x05A4 0x05D4 0x0604 0x0634 0x0664
Address
Address $060145 $060151 $06015B $060169 $060175 $060181 $06018D $060199
C. S. # 1 2 3 4 5 6 7 8
Host Adr 0x069C 0x071C 0x079C 0x081C 0x089C 0x091C 0x099C 0x0A1C
Address $0601A7 $0601C7 $0601E7 $060207 $060227 $060247 $060267 $060287
C. S. # 9 10 11 12 13 14 15 16
Host Adr 0x0A9C 0x0B1C 0x0B9C 0x0C1C 0x0C9C 0x0D1C 0x0D9C 0x0E1C
Address $0602A7 $0602C7 $0602E7 $060307 $060327 $060347 $060367 $060387
C. S. # 1 2 3 4 5 6 7 8
Host Adr 0x06A4 0x0724 0x07A4 0x0824 0x08A4 0x0924 0x09A4 0x0A24
Address $0601A9 $0601C9 $0601E9 $060209 $060229 $060249 $060269 $060289
C. S. # 9 10 11 12 13 14 15 16
Host Adr 0x0AA4 0x0B24 0x0BA4 0x0C24 0x0CA4 0x0D24 0x0DA4 0x0E24
Address $0602A9 $0602C9 $0602E9 $060309 $060329 $060349 $060369 $060389
C. S. # 1 2 3 4 5 6 7 8
Host Adr 0x06A8 0x0728 0x07A8 0x0828 0x08A8 0x0928 0x09A8 0x0A28
Address $0601AA $0601CA $0601EA $06020A $06022A $06024A $06026A $06028A
C. S. # 9 10 11 12 13 14 15 16
Host Adr 0x0AA8 0x0B24 0x0BA8 0x0C28 0x0CA8 0x0D28 0x0DA8 0x0E28
Address $0602AA $0602CA $0602EA $06030A $06032A $06034A $06036A $06038A
C. S. # 1 2 3 4 5 6 7 8
Host Adr 0x06AC 0x072C 0x07AC 0x082C 0x08AC 0x092C 0x09AC 0x0A2C
Address $0601AB $0601CB $0601EB $06020B $06022B $06024B $06026B $06028B
C. S. # 9 10 11 12 13 14 15 16
Host Adr 0x0AAC 0x0B2C 0x0BAC 0x0C2C 0x0CAC 0x0D2C 0x0DAC 0x0E2C
Address $0602AB $0602CB $0602EB $06030B $06032B $06034B $06036B $06038B
C. S. # 1 2 3 4 5 6 7 8
Host Adr 0x06B4 0x0734 0x07B4 0x0834 0x08B4 0x0934 0x09B4 0x0A34
Address $0601AD $0601CD $0601ED $06020D $06022D $06024D $06026D $06028D
C. S. # 9 10 11 12 13 14 15 16
Host Adr 0x0AB4 0x0B34 0x0BB4 0x0C34 0x0CB4 0x0D34 0x0DB4 0x0E34
Address $0602AD $0602CD $0602ED $06030D $06032D $06034D $06036D $06038D
C. S. # 1 2 3 4 5 6 7 8
Host Adr 0x06BC 0x073C 0x07BC 0x083C 0x08BC 0x093C 0x09BC 0x0A3C
Address $0601AF $0601CF $0601EF $06020F $06022F $06024F $06026F $06028F
C. S. # 9 10 11 12 13 14 15 16
Host Adr 0x0ABC 0x0B3C 0x0BBC 0x0C3C 0x0CBC 0x0D3C 0x0DBC 0x0E3C
Address $0602AF $0602CF $0602EF $06030F $06032F $06034F $06036F $06038F
C. S. # 1 2 3 4 5 6 7 8
Host Adr 0x06C4 0x0744 0x07C4 0x0844 0x08C4 0x0944 0x09C4 0x0A44
Address $0601B1 $0601D1 $0601F1 $060211 $060231 $060251 $060271 $060291
C. S. # 9 10 11 12 13 14 15 16
Host Adr 0x0AC4 0x0B44 0x0BC4 0x0C44 0x0CC4 0x0D44 0x0DC4 0x0E44
Address $0602B1 $0602D1 $0602F1 $060311 $060331 $060351 $060371 $060391
C. S. # 1 2 3 4 5 6 7 8
Host Adr 0x06CC 0x074C 0x07CC 0x084C 0x08CC 0x094C 0x09CC 0x0A4C
Address $0601B3 $0601D3 $0601F3 $060213 $060233 $060253 $060273 $060293
C. S. # 9 10 11 12 13 14 15 16
Host Adr 0x0ACC 0x0B4C 0x0BCC 0x0C4C 0x0CCC 0x0D4C 0x0DCC 0x0E4C
Address $0602B3 $0602D3 $0602F3 $060313 $060333 $060353 $060373 $060393
C. S. # 1 2 3 4 5 6 7 8
Host Adr 0x06D4 0x0754 0x07D4 0x0854 0x08D4 0x0954 0x09D4 0x0A54
Address $0601B5 $0601D5 $0601F5 $060215 $060235 $060255 $060275 $060295
C. S. # 9 10 11 12 13 14 15 16
Host Adr 0x0AD4 0x0B54 0x0BD4 0x0C54 0x0CD4 0x0D54 0x0DD4 0x0E54
Address $0602B5 $0602D5 $0602F5 $060315 $060335 $060355 $060375 $060395
C. S. # 1 2 3 4 5 6 7 8
Host Adr 0x06DC 0x075C 0x07DC 0x085C 0x08DC 0x095C 0x09DC 0x0A5C
Address $0601B7 $0601D7 $0601F7 $060217 $060237 $060257 $060277 $060297
C. S. # 9 10 11 12 13 14 15 16
Host Adr 0x0ADC 0x0B5C 0x0BDC 0x0C5C 0x0CDC 0x0D5C 0x0DDC 0x0E5C
Address $0602B7 $0602D7 $0602F7 $060317 $060337 $060357 $060377 $060397
C. S. # 1 2 3 4 5 6 7 8
Host Adr 0x06E4 0x0764 0x07E4 0x0864 0x08E4 0x0964 0x09E4 0x0A64
Address $0601B9 $0601D9 $0601F9 $060219 $060239 $060259 $060279 $060299
C. S. # 9 10 11 12 13 14 15 16
Host Adr 0x0AE4 0x0B64 0x0BE4 0x0C64 0x0CE4 0x0D64 0x0DE4 0x0E64
Address $0602B9 $0602D9 $0602F9 $060319 $060339 $060359 $060379 $060399
C. S. # 1 2 3 4 5 6 7 8
Host Adr 0x06EC 0x076C 0x07EC 0x086C 0x08EC 0x096C 0x09EC 0x0A6C
Address $0601BB $0601DB $0601FB $06021B $06023B $06025B $06027B $06029B
C. S. # 9 10 11 12 13 14 15 16
Host Adr 0x0AEC 0x0B6C 0x0BEC 0x0C6C 0x0CEC 0x0D6C 0x0DEC 0x0E6C
Address $0602BB $0602DB $0602FB $06031B $06033B $06035B $06037B $06039B
C. S. # 1 2 3 4 5 6 7 8
Host Adr 0x06F4 0x0774 0x07F4 0x0874 0x08F4 0x0974 0x09F4 0x0A74
Address $0601BD $0601DD $0601FD $06021D $06023D $06025D $06027D $06029D
C. S. # 9 10 11 12 13 14 15 16
Host Adr 0x0AF4 0x0B74 0x0BF4 0x0C74 0x0CF4 0x0D74 0x0DF4 0x0E74
Address $0602BD $0602DD $0602FD $06031D $06033D $06035D $06037D $06039D
C. S. # 1 2 3 4 5 6 7 8
Host Adr 0x06FC 0x077C 0x07FC 0x087C 0x08FC 0x097C 0x09FC 0x0A7C
Address $0601BF $0601DF $0601FF $06021F $06023F $06025F $06027F $06029F
C. S. # 9 10 11 12 13 14 15 16
Host Adr 0x0AFC 0x0B7C 0x0BFC 0x0C7C 0x0CFC 0x0D7C 0x0DFC 0x0E7C
Address $0602BF $0602DF $0602FF $06031F $06033F $06035F $06037F $06039F
C. S. # 1 2 3 4 5 6 7 8
Host 0x0700 0x0780 0x0800 0x0880 0x0900 0x0980 0x0A00 0x0A80
Address
Address $0601C0 $0601E0 $060200 $060220 $060240 $060260 $060280 $0602A0
C. S. # 9 10 11 12 13 14 15 16
Host 0x0B00 0x0B80 0x0C00 0x0C80 0x0D00 0x0D80 0x0E00 0x0E80
Addess
Address $0602C0 $0602E0 $060300 $060320 $060340 $060360 $060380 $0603A0
C. S. # 1 2 3 4 5 6 7 8
Host Adr 0x0704 0x0784 0x0804 0x0884 0x0904 0x0984 0x0A04 0x0A84
Address $0601C1 $0601E1 $060201 $060221 $060241 $060261 $060281 $0602A1
C. S. # 9 10 11 12 13 14 15 16
Host Adr 0x0B04 0x0B84 0x0C04 0x0C84 0x0D04 0x0D84 0x0E04 0x0E84
Address $0602C1 $0602E1 $060301 $060321 $060341 $060361 $060381 $0603A1
C. S. # 1 2 3 4 5 6 7 8
Host 0x0708 0x0788 0x0808 0x0888 0x0908 0x0988 0x0A08 0x0A88
Adr
Address $0601C2 $0601E2 $060202 $060222 $060242 $060262 $060282 $0602A2
C. S. # 9 10 11 12 13 14 15 16
Host 0x0B08 0x0B88 0x0C08 0x0C88 0x0D08 0x0D88 0x0E08 0x0E88
Adr
Address $0602C2 $0602E2 $060302 $060322 $060342 $060362 $060382 $0603A2
C. S. # 1 2 3 4 5 6 7 8
Host 0x070C 0x078C 0x080C 0x088C 0x090C 0x098C 0x0A0C 0x0A8C
Address
Address $0601C3 $0601E3 $060203 $060223 $060243 $060263 $060283 $0602A3
C. S. # 9 10 11 12 13 14 15 16
Host 0x0B0C 0x0B8C 0x0C0C 0x0C8C 0x0D0C 0x0D8C 0x0E0C 0x0E8C
Address
Address $0602C3 $0602E3 $060303 $060323 $060343 $060363 $060383 $0603A3
C. S. # 1 2 3 4 5 6 7 8
Host 0x0710 0x0790 0x0810 0x0890 0x0910 0x0990 0x0A10 0x0A90
Adr
Address $0601C4 $0601E4 $060204 $060224 $060244 $060264 $060284 $0602A4
C. S. # 9 10 11 12 13 14 15 16
Host 0x0B10 0x0B90 0x0C10 0x0C90 0x0D10 0x0D90 0x0E10 0x0E90
Adr
Address $0602C4 $0602E4 $060304 $060324 $060344 $060364 $060384 $0603A4
Binary Rotary Program Buffer Control (used after OPEN BIN ROT)
C. S. # 1 2 3 4 5 6 7 8
Host Adr 0x1050 0x105C 0x1068 0x1074 0x1080 0x108C 0x1098 0x10A4
Address $060414 $060417 $06041A $06041D $060420 $060423 $060426 $060429
C. S. # 9 10 11 12 13 14 15 16
Host Adr 0x10B0 0x10BC 0x10C8 0x10D4 0x10E0 0x10EC 0x10F8 0x1104
Address $06042C $06042F $060432 $060435 $060438 $06043B $06043E $060441
IC# - Chan# 0-1 0-2 0-3 0-4 1-1 1-2 1-3 1-4
Board - PMAC - 1 PMAC - 2 PMAC - 3 PMAC - 4 PMAC - 5 PMAC - 6 PMAC - 7 PMAC -8
Chan#
Address $078001 $078005 $078009 $07800D $078101 $078105 $078109 $07810D
IC# - Chan# 2-1 2-2 2-3 2-4 3-1 3-2 3-3 3-4
Board - 24P/V 24P/V 24P/V 24P/V 24P/V 24P/V 24P/V 24P/V
Chan# #1 - 1 #1 - 2 #1 - 3 #1 - 4 #1 - 5 #1 - 6 #1 - 7 #1 - 8
Address $078201 $078205 $078209 $07820D $078301 $078305 $078309 $07830D
IC# - Chan# 4-1 4-2 4-3 4-4 5-1 5-2 5-3 5-4
Board - 24P/V 24P/V 24P/V 24P/V 24P/V 24P/V 24P/V 24P/V
Chan# #2 - 1 #2 - 2 #2 - 3 #2 - 4 #2 - 5 #2 - 6 #2 - 7 #2 - 8
Address $079201 $079205 $079209 $07920D $079301 $079305 $079309 $07930D
IC# - Chan# 6-1 6-2 6-3 6-4 7-1 7-2 7-3 7-4
Board - 24P/V 24P/V 24P/V 24P/V 24P/V 24P/V 24P/V 24P/V
Chan# #3 - 1 #3 - 2 #3 - 3 #3 - 4 #3 - 5 #3 - 6 #3 - 7 #3 - 8
Address $07A201 $07A205 $07A209 $07A20D $07A301 $07A305 $07A309 $07A30D
IC# - Chan# 8-1 8-2 8-3 8-4 9-1 9-2 9-3 9-4
Board - 24P/V 24P/V 24P/V 24P/V 24P/V 24P/V 24P/V 24P/V
Chan# #4 - 1 #4 - 2 #4 - 3 #4 - 4 #4 - 5 #4 - 6 #4 - 7 #4 - 8
Address $07B201 $07B205 $07B209 $07B20D $07B301 $07B305 $07B309 $07B30D
Y:$07x0xx Channel n Time since last encoder count (SCLK cycles)
Alternate use if Channel Control Word bit 18 set to 1 (Rev “D” or newer IC only):
Channel n Timer-Based Fractional Count Data (unsigned)
Bits: 0-11 Compare “A” fractional count (bit 11 = ½-count; bit 10 = ¼-count; etc.)
12-23 Servo-captured fractional count (bit 23 = ½-count; bit 22 = ¼-count; etc.)
X:$07xx0x Encoder phase position (counts)
IC# - Chan# 0-1 0-2 0-3 0-4 1-1 1-2 1-3 1-4
Board - PMAC - 1 PMAC - 2 PMAC - 3 PMAC - 4 PMAC - 5 PMAC - 6 PMAC - 7 PMAC - 8
Chan#
Address $078002 $078006 $07800A $07800E $078102 $078106 $07810A $07810E
IC# - Chan# 2-1 2-2 2-3 2-4 3-1 3-2 3-3 3-4
Board - 24P/V 24P/V 24P/V 24P/V 24P/V 24P/V 24P/V 24P/V
Chan# #1 - 1 #1 - 2 #1 - 3 #1 - 4 #1 - 5 #1 - 6 #1 - 7 #1 - 8
Address $078202 $078206 $07820A $07820E $078302 $078306 $07830A $07830E
IC# - Chan# 4-1 4-2 4-3 4-4 5-1 5-2 5-3 5-4
Board - 24P/V 24P/V 24P/V 24P/V 24P/V 24P/V 24P/V 24P/V
Chan# #2 - 1 #2 - 2 #2 - 3 #2 - 4 #2 - 5 #2 - 6 #2 - 7 #2 - 8
Address $079202 $079206 $07920A $07920E $079302 $079306 $07930A $07930E
IC# - Chan# 6-1 6-2 6-3 6-4 7-1 7-2 7-3 7-4
Board - 24P/V 24P/V 24P/V 24P/V 24P/V 24P/V 24P/V 24P/V
Chan# #3 - 1 #3 - 2 #3 - 3 #3 - 4 #3 - 5 #3 - 6 #3 - 7 #3 - 8
Address $07A202 $07A206 $07A20A $07A20E $07A302 $07A306 $07A30A $07A30E
IC# - Chan# 8-1 8-2 8-3 8-4 9-1 9-2 9-3 9-4
Board - 24P/V 24P/V 24P/V 24P/V 24P/V 24P/V 24P/V 24P/V
Chan# #4 - 1 #4 - 2 #4 - 3 #4 - 4 #4 - 5 #4 - 6 #4 - 7 #4 - 8
Address $07B202 $07B206 $07B20A $07B20E $07B302 $07B306 $07B30A $07B30E
IC# - Chan# 0-1 0-2 0-3 0-4 1-1 1-2 1-3 1-4
Board - PMAC - 1 PMAC - 2 PMAC - 3 PMAC - 4 PMAC - 5 PMAC - 6 PMAC - 7 PMAC - 8
Chan#
Address $078003 $078007 $07800B $07800F $078103 $078107 $07810B $07810F
IC# - Chan# 2-1 2-2 2-3 2-4 3-1 3-2 3-3 3-4
Board - 24P/V 24P/V 24P/V 24P/V 24P/V 24P/V 24P/V 24P/V
Chan# #1 - 1 #1 - 2 #1 - 3 #1 - 4 #1 - 5 #1 - 6 #1 - 7 #1 - 8
Address $078203 $078207 $07820B $07820F $078303 $078307 $07830B $07830F
IC# - Chan# 4-1 4-2 4-3 4-4 5-1 5-2 5-3 5-4
Board - 24P/V 24P/V 24P/V 24P/V 24P/V 24P/V 24P/V 24P/V
Chan# #2 - 1 #2 - 2 #2 - 3 #2 - 4 #2 - 5 #2 - 6 #2 - 7 #2 - 8
Address $079203 $079207 $07920B $07920F $079303 $079307 $07930B $07930F
IC# - Chan# 6-1 6-2 6-3 6-4 7-1 7-2 7-3 7-4
Board - 24P/V 24P/V 24P/V 24P/V 24P/V 24P/V 24P/V 24P/V
Chan# #3 - 1 #3 - 2 #3 - 3 #3 - 4 #3 - 5 #3 - 6 #3 - 7 #3 - 8
Address $07A203 $07A207 $07A20B $07A20F $07A303 $07A307 $07A30B $07A30F
IC# - Chan# 8-1 8-2 8-3 8-4 9-1 9-2 9-3 9-4
Board - 24P/V 24P/V 24P/V 24P/V 24P/V 24P/V 24P/V 24P/V
Chan# #4 - 1 #4 - 2 #4 - 3 #4 - 4 #4 - 5 #4 - 6 #4 - 7 #4 - 8
Address $07B203 $07B207 $07B20B $07B20F $07B303 $07B307 $07B30B $07B30F
IC# - Chan# 0-1 0-2 0-3 0-4 1-1 1-2 1-3 1-4
Board - PMAC2-1 PMAC2-2 PMAC2-3 PMAC2-4 PMAC2-5 PMAC2-6 PMAC2-7 PMAC2-8
Chan#
Address $078000 $078008 $078010 $078018 $078100 $078108 $078110 $078118
IC# - Chan# 2-1 2-2 2-3 2-4 3-1 3-2 3-3 3-4
Board - 24P/V/E2 24P/V/E2 #1 24P/V/E2 24P/V/E2 24P/V/E2 24P/V/E2 24P/V/E2 24P/V/E2
Chan# #1 - 1 -2 #1 - 3 #1 - 4 #1 - 5 #1 - 6 #1 - 7 #1 - 8
Address $078200 $078208 $078210 $078218 $078300 $078308 $078310 $078318
IC# - Chan# 4-1 4-2 4-3 4-4 5-1 5-2 5-3 5-4
Board - 24P/V/E2 24P/V/E2 24P/V/E2 24P/V/E2 24P/V/E2 24P/V/E2 24P/V/E2 24P/V/E2
Chan# #2 - 1 #2 - 2 #2 - 3 #2 - 4 #2 - 5 #2 - 6 #2 - 7 #2 - 8
Address $079200 $079208 $079210 $079218 $079300 $079308 $079310 $079318
IC# - Chan# 6-1 6-2 6-3 6-4 7-1 7-2 7-3 7-4
Board - 24P/V/E2 24P/V/E2 24P/V/E2 24P/V/E2 24P/V/E2 24P/V/E2 24P/V/E2 24P/V/E2
Chan# #3 - 1 #3 - 2 #3 - 3 #3 - 4 #3 - 5 #3 - 6 #3 - 7 #3 - 8
Address $07A200 $07A208 $07A210 $07A218 $07A300 $07A308 $07A310 $07A318
IC# - Chan# 8-1 8-2 8-3 8-4 9-1 9-2 9-3 9-4
Board - 24P/V/E2 24P/V/E2 24P/V/E2 24P/V/E2 24P/V/E2 24P/V/E2 24P/V/E2 24P/V/E2
Chan# #4 - 1 #4 - 2 #4 - 3 #4 - 4 #4 - 5 #4 - 6 #4 - 7 #4 - 8
Address $07B200 $07B208 $07B210 $07B218 $07B300 $07B308 $07B310 $07B318
Y:$07x0xx . Channel n Time between last two encoder counts (SCLK cycles)
Bits: 0-22: Timer (units of SCLK cycles)
23: Change-of-direction flag
Alternate use if Channel Control Word bit 18 set to 1 (Rev “D” or newer IC only):
Channel n Timer-Based Fractional Count Data (unsigned)
Bits: 0-11 Compare “A” fractional count (bit 11 = ½-count; bit 10 = ¼-count; etc.)
12-23 Servo-captured fractional count (bit 23 = ½-count; bit 22 = ¼-count; etc.)
X:$07xx0x Channel n Status Word
Bits: 0-2 Capture Hall Effect Device State
3 Invalid demultiplex of C, U, V, & W
4-7 Reserved for future use (reports as 0)
8 Encoder Count Error (0 on counter reset, 1 on illegal transition)
9 Position Compare (EQUn) output value
10 Position-Captured-On-Gated-Index Flag
(=0 on read of captured position register, =1 on trigger capture)
11 Position-Captured Flag (on any trigger)
(=0 on read of captured position register, =1 on trigger capture)
12 Encoder Channel A (CHAn) Input Value
13 Encoder Channel B (CHBn) Input Value
14 Encoder Channel C (Index, CHCn) Input Value (ungated)
15 Amplifier Fault (FAULTn) Input Value
16 Home Flag (HMFLn) Input Value
17 Positive End Limit (PLIMn) Input Value
IC# - Chan# 0-1 0-2 0-3 0-4 1-1 1-2 1-3 1-4
Board - Chan# PMAC2- PMAC2-
PMAC2-1 PMAC2-3 PMAC2-4 PMAC2-5 PMAC2-6 PMAC2-8
2 7
Address $078001 $078009 $078011 $078019 $078101 $078109 $078111 $078119
IC# - Chan# 2-1 2-2 2-3 2-4 3-1 3-2 3-3 3-4
Board - Chan# 24P/V/E2 24P/V/E2 24P/V/E2 24P/V/E2 24P/V/E2 24P/V/E2 24P/V/E2 24P/V/E2
#1 - 1 #1 - 2 #1 - 3 #1 - 4 #1 - 5 #1 - 6 #1 - 7 #1 - 8
Address $078201 $078209 $078211 $078219 $078301 $078309 $078311 $078319
IC# - Chan# 4-1 4-2 4-3 4-4 5-1 5-2 5-3 5-4
Board - Chan# 24P/V/E2 24P/V/E2 24P/V/E2 24P/V/E2 24P/V/E2 24P/V/E2 24P/V/E2 24P/V/E2
#2 - 1 #2 - 2 #2 - 3 #2 - 4 #2 - 5 #2 - 6 #2 - 7 #2 - 8
Address $079201 $079209 $079211 $079219 $079301 $079309 $079311 $079319
IC# - Chan# 6-1 6-2 6-3 6-4 7-1 7-2 7-3 7-4
Board - Chan# 24P/V/E2 24P/V/E2 24P/V/E2 24P/V/E2 24P/V/E2 24P/V/E2 24P/V/E2 24P/V/E2
#3 - 1 #3 - 2 #3 - 3 #3 - 4 #3 - 5 #3 - 6 #3 - 7 #3 - 8
Address $07A201 $07A209 $07A211 $07A219 $07A301 $07A309 $07A311 $07A319
IC# - Chan# 8-1 8-2 8-3 8-4 9-1 9-2 9-3 9-4
Board - Chan# 24P/V/E2 24P/V/E2 24P/V/E2 24P/V/E2 24P/V/E2 24P/V/E2 24P/V/E2 24P/V/E2
#4 - 1 #4 - 2 #4 - 3 #4 - 4 #4 - 5 #4 - 6 #4 - 7 #4 - 8
Address $07B201 $07B209 $07B211 $07B219 $07B301 $07B309 $07B311 $07B319
IC# - Chan# 0-1 0-2 0-3 0-4 1-1 1-2 1-3 1-4
Board - PMAC2-1 PMAC2-2 PMAC2-3 PMAC2-4 PMAC2-5 PMAC2-6 PMAC2-7 PMAC2-8
Chan#
Address $078002 $07800A $078012 $07801A $078102 $07810A $078112 $07811A
IC# - Chan# 2-1 2-2 2-3 2-4 3-1 3-2 3-3 3-4
Board - 24P/V/E2 24P/V/E2 24P/V/E2 24P/V/E2 24P/V/E2 24P/V/E2 24P/V/E2 24P/V/E2
Chan# #1 - 1 #1 - 2 #1 - 3 #1 - 4 #1 - 5 #1 - 6 #1 - 7 #1 - 8
Address $078202 $07820A $078212 $07821A $078302 $07830A $078312 $07831A
IC# - Chan# 4-1 4-2 4-3 4-4 5-1 5-2 5-3 5-4
Board - 24P/V/E2 24P/V/E2 24P/V/E2 24P/V/E2 24P/V/E2 24P/V/E2 24P/V/E2 24P/V/E2
Chan# #2 - 1 #2 - 2 #2 - 3 #2 - 4 #2 - 5 #2 - 6 #2 - 7 #2 - 8
Address $079202 $07920A $079212 $07921A $079302 $07930A $079312 $07931A
IC# - Chan# 6-1 6-2 6-3 6-4 7-1 7-2 7-3 7-4
Board - 24P/V/E2 24P/V/E2 24P/V/E2 24P/V/E2 24P/V/E2 24P/V/E2 24P/V/E2 24P/V/E2
Chan# #3 - 1 #3 - 2 #3 - 3 #3 - 4 #3 - 5 #3 - 6 #3 - 7 #3 - 8
Address $07A202 $07A20A $07A212 $07A21A $07A302 $07A30A $07A312 $07A31A
IC# - Chan# 8-1 8-2 8-3 8-4 9-1 9-2 9-3 9-4
Board - 24P/V/E2 24P/V/E2 24P/V/E2 24P/V/E2 24P/V/E2 24P/V/E2 24P/V/E2 24P/V/E2
Chan# #4 - 1 #4 - 2 #4 - 3 #4 - 4 #4 - 5 #4 - 6 #4 - 7 #4 - 8
Address $07B202 $07B20A $07B212 $07B21A $07B302 $07B30A $07B312 $07B31A
IC# - Chan# 0-1 0-2 0-3 0-4 1-1 1-2 1-3 1-4
Board - PMAC2-1 PMAC2-2 PMAC2-3 PMAC2-4 PMAC2-5 PMAC2-6 PMAC2-7 PMAC2-8
Chan#
Address $078003 $07800B $078013 $07801B $078103 $07810B $078113 $07811B
IC# - Chan# 2-1 2-2 2-3 2-4 3-1 3-2 3-3 3-4
Board - 24P/V/E2 24P/V/E2 24P/V/E2 24P/V/E2 24P/V/E2 24P/V/E2 24P/V/E2 24P/V/E2
Chan# #1 - 1 #1 - 2 #1 - 3 #1 - 4 #1 - 5 #1 - 6 #1 - 7 #1 - 8
Address $078203 $07820B $078213 $07821B $078303 $07830B $078313 $07831B
IC# - Chan# 4-1 4-2 4-3 4-4 5-1 5-2 5-3 5-4
Board - 24P/V/E2 24P/V/E2 24P/V/E2 24P/V/E2 24P/V/E2 24P/V/E2 24P/V/E2 24P/V/E2
Chan# #2 - 1 #2 - 2 #2 - 3 #2 - 4 #2 - 5 #2 - 6 #2 - 7 #2 - 8
Address $079203 $07920B $079213 $07921B $079303 $07930B $079313 $07931B
IC# - Chan# 6-1 6-2 6-3 6-4 7-1 7-2 7-3 7-4
Board - 24P/V/E2 24P/V/E2 24P/V/E2 24P/V/E2 24P/V/E2 24P/V/E2 24P/V/E2 24P/V/E2
Chan# #3 - 1 #3 - 2 #3 - 3 #3 - 4 #3 - 5 #3 - 6 #3 - 7 #3 - 8
Address $07A203 $07A20B $07A213 $07A21B $07A303 $07A30B $07A313 $07A31B
IC# - Chan# 8-1 8-2 8-3 8-4 9-1 9-2 9-3 9-4
Board - 24P/V/E2 24P/V/E2 24P/V/E2 24P/V/E2 24P/V/E2 24P/V/E2 24P/V/E2 24P/V/E2
Chan# #4 - 1 #4 - 2 #4 - 3 #4 - 4 #4 - 5 #4 - 6 #4 - 7 #4 - 8
Address $07B203 $07B20B $07B213 $07B21B $07B303 $07B30B $07B313 $07B31B
IC# - Chan# 0-1 0-2 0-3 0-4 1-1 1-2 1-3 1-4
Board - PMAC2-1 PMAC2-2 PMAC2-3 PMAC2-4 PMAC2-5 PMAC2-6 PMAC2-7 PMAC2-8
Chan#
Address $078004 $07800C $078014 $07801C $078104 $07810C $078114 $07811C
IC# - Chan# 2-1 2-2 2-3 2-4 3-1 3-2 3-3 3-4
Board - 24P/V/E2 24P/V/E2 24P/V/E2 24P/V/E2 24P/V/E2 24P/V/E2 24P/V/E2 24P/V/E2
Chan# #1 - 1 #1 - 2 #1 - 3 #1 - 4 #1 - 5 #1 - 6 #1 - 7 #1 - 8
Address $078204 $07820C $078214 $07821C $078304 $07830C $078314 $07831C
IC# - Chan# 4-1 4-2 4-3 4-4 5-1 5-2 5-3 5-4
Board - 24P/V/E2 24P/V/E2 24P/V/E2 24P/V/E2 24P/V/E2 24P/V/E2 24P/V/E2 24P/V/E2
Chan# #2 - 1 #2 - 2 #2 - 3 #2 - 4 #2 - 5 #2 - 6 #2 - 7 #2 - 8
Address $079204 $07920C $079214 $07921C $079304 $07930C $079314 $07931C
IC# - Chan# 6-1 6-2 6-3 6-4 7-1 7-2 7-3 7-4
Board - 24P/V/E2 24P/V/E2 24P/V/E2 24P/V/E2 24P/V/E2 24P/V/E2 24P/V/E2 24P/V/E2
Chan# #3 - 1 #3 - 2 #3 - 3 #3 - 4 #3 - 5 #3 - 6 #3 - 7 #3 - 8
Address $07A204 $07A20C $07A214 $07A21C $07A304 $07A30C $07A314 $07A31C
IC# - Chan# 8-1 8-2 8-3 8-4 9-1 9-2 9-3 9-4
Board - 24P/V/E2 24P/V/E2 24P/V/E2 24P/V/E2 24P/V/E2 24P/V/E2 24P/V/E2 24P/V/E2
Chan# #4 - 1 #4 - 2 #4 - 3 #4 - 4 #4 - 5 #4 - 6 #4 - 7 #4 - 8
Address $07B204 $07B20C $07B214 $07B21C $07B304 $07B30C $07B314 $07B31C
Y:$07xx0x Channel n Output C Command Value
Bits: 8-23: PWM Command Value
0-23: PFM Command Value
IC# - Chan# 0-1 0-2 0-3 0-4 1-1 1-2 1-3 1-4
Board - PMAC2-1 PMAC2-2 PMAC2-3 PMAC2-4 PMAC2-5 PMAC2-6 PMAC2-7 PMAC2-8
Chan#
Address $078005 $07800D $078015 $07801D $078105 $07810D $078115 $07811D
IC# - Chan# 2-1 2-2 2-3 2-4 3-1 3-2 3-3 3-4
Board - 24P/V/E2 24P/V/E2 24P/V/E2 24P/V/E2 24P/V/E2 24P/V/E2 24P/V/E2 24P/V/E2
Chan# #1 - 1 #1 - 2 #1 - 3 #1 - 4 #1 - 5 #1 - 6 #1 - 7 #1 - 8
Address $078205 $07820D $078215 $07821D $078305 $07830D $078315 $07831D
IC# - Chan# 4-1 4-2 4-3 4-4 5-1 5-2 5-3 5-4
Board - 24P/V/E2 24P/V/E2 24P/V/E2 24P/V/E2 24P/V/E2 24P/V/E2 24P/V/E2 24P/V/E2
Chan# #2 - 1 #2 - 2 #2 - 3 #2 - 4 #2 - 5 #2 - 6 #2 - 7 #2 - 8
Address $079205 $07920D $079215 $07921D $079305 $07930D $079315 $07931D
IC# - Chan# 6-1 6-2 6-3 6-4 7-1 7-2 7-3 7-4
Board - 24P/V/E2 24P/V/E2 24P/V/E2 24P/V/E2 24P/V/E2 24P/V/E2 24P/V/E2 24P/V/E2
Chan# #3 - 1 #3 - 2 #3 - 3 #3 - 4 #3 - 5 #3 - 6 #3 - 7 #3 - 8
Address $07A205 $07A20D $07A215 $07A21D $07A305 $07A30D $07A315 $07A31D
IC# - Chan# 8-1 8-2 8-3 8-4 9-1 9-2 9-3 9-4
Board - 24P/V/E2 24P/V/E2 24P/V/E2 24P/V/E2 24P/V/E2 24P/V/E2 24P/V/E2 24P/V/E2
Chan# #4 - 1 #4 - 2 #4 - 3 #4 - 4 #4 - 5 #4 - 6 #4 - 7 #4 - 8
Address $07B205 $07B20D $07B215 $07B21D $07B305 $07B30D $07B315 $07B31D
IC# - Chan# 0-1 0-2 0-3 0-4 1-1 1-2 1-3 1-4
Board - PMAC2-1 PMAC2-2 PMAC2-3 PMAC2-4 PMAC2-5 PMAC2-6 PMAC2-7 PMAC2-8
Chan#
Address $078006 $07800E $078016 $07801E $078106 $07810E $078116 $07811E
IC# - Chan# 2-1 2-2 2-3 2-4 3-1 3-2 3-3 3-4
Board - 24P/V/E2 24P/V/E2 24P/V/E2 24P/V/E2 24P/V/E2 24P/V/E2 24P/V/E2 24P/V/E2
Chan# #1 - 1 #1 - 2 #1 - 3 #1 - 4 #1 - 5 #1 - 6 #1 - 7 #1 - 8
Address $078206 $07820E $078216 $07821E $078306 $07830E $078316 $07831E
IC# - Chan# 4-1 4-2 4-3 4-4 5-1 5-2 5-3 5-4
Board - 24P/V/E2 24P/V/E2 24P/V/E2 24P/V/E2 24P/V/E2 24P/V/E2 24P/V/E2 24P/V/E2
Chan# #2 - 1 #2 - 2 #2 - 3 #2 - 4 #2 - 5 #2 - 6 #2 - 7 #2 - 8
Address $079206 $07920E $079216 $07921E $079306 $07930E $079316 $07931E
IC# - Chan# 6-1 6-2 6-3 6-4 7-1 7-2 7-3 7-4
Board - 24P/V/E2 24P/V/E2 24P/V/E2 24P/V/E2 24P/V/E2 24P/V/E2 24P/V/E2 24P/V/E2
Chan# #3 - 1 #3 - 2 #3 - 3 #3 - 4 #3 - 5 #3 - 6 #3 - 7 #3 - 8
Address $07A206 $07A20E $07A216 $07A21E $07A306 $07A30E $07A316 $07A31E
IC# - Chan# 8-1 8-2 8-3 8-4 9-1 9-2 9-3 9-4
Board - 24P/V/E2 24P/V/E2 24P/V/E2 24P/V/E2 24P/V/E2 24P/V/E2 24P/V/E2 24P/V/E2
Chan# #4 - 1 #4 - 2 #4 - 3 #4 - 4 #4 - 5 #4 - 6 #4 - 7 #4 - 8
Address $07B206 $07B20E $07B216 $07B21E $07B306 $07B30E $07B316 $07B31E
...
15 SEL7 Data Value
16-23 Not used
X:$078402 JTHW Port Data Direction Control Register (when used as general I/O; see
Y:$078406)
Bits: 0 DAT0 Direction Control (Must be 0 to use standard port accessories)
...
7 DAT7 Direction Control (Must be 0 to use standard port accessories)
8 SEL0 Direction Control (Must be 1 to use standard port accessories)
...
15 SEL7 Direction Control (Must be 1 to use standard port accessories)
(All bits: 0=Input; 1=Output)
16-23 Not used
Y:$078403 JDISP, J??? Port Data Register
Bits: 0 DISP0 Data Value
...
7 DISP7 Data Value
8 CTRL0 Data Value
...
11 CTRL3 Data Value
12-23 Not used
X:$078403 JDISP, J??? Port Data Direction Control Register
Bits: 0 DISP0 Direction Control (Must be 1 for display to function)
...
7 DISP7 Direction Control (Must be 1 for display to function)
8 CTRL0 Direction Control (Must be 1 for ??? to function)
...
11 CTRL3 Direction Control (Must be 1 for ??? to function)
(All bits: 0=Input; 1=Output)
12-23 Not used
Y:$078404 JI/O Port Data Type Control Register
Bits: 0 I/O00 Data Type Control (0=FlagW1*; 1=I/O00)
1 I/O01 Data Type Control (0=FlagV1*; 1=I/O01)
2 I/O02 Data Type Control (0=FlagU1*; 1=I/O02)
3 I/O03 Data Type Control (0=FlagT1*; 1=I/O03)
4 I/O04 Data Type Control (0=USER1*; 1=I/O04)
5 I/O05 Data Type Control (0=MLIM1*; 1=I/O05)
6 I/O06 Data Type Control (0=PLIM1*; 1=I/O06)
7 I/O07 Data Type Control (0=HMFL1*; 1=I/O07)
8 I/O08 Data Type Control (0=PWM_B_BOT1*; 1=I/O08)
9 I/O09 Data Type Control (0=PWM_B_TOP1*; 1=I/O09)
10 I/O10 Data Type Control (0=PWM_A_BOT1*; 1=I/O10)
11 I/O11 Data Type Control (0=PWM_A_TOP1*; 1=I/O11)
12 I/O12 Data Type Control (0=PWM_B_BOT2*; 1=I/O12)
13 I/O13 Data Type Control (0=PWM_B_TOP2*; 1=I/O13)
14 I/O14 Data Type Control (0=PWM_A_BOT2*; 1=I/O14)
15 I/O15 Data Type Control (0=PWM_A_TOP2*; 1=I/O15)
16 I/O16 Data Type Control (0=HMFL2*; 1=I/O16)
17 I/O17 Data Type Control (0=PLIM2*; 1=I/O17)
Bits:
0 DAT0 Inversion Control
...
7 DAT7 Inversion Control
8 SEL0 Inversion Control
...
15 SEL7 Inversion Control
(All bits: 0=Non-inverting; 1=Inverting)
(All bits must be 0 to use standard port accessories)
16-23 Not used
Y:$078407 JDISP, J??? Port Data Type Control Register
Bits: 0 DISP0 Data Type Control
...
7 DISP7 Data Type Control
8 CTRL0 Data Type Control
...
11 CTRL3 Data Type Control
(These bits are always 1; there is no alternate mode for these pins)
12-23 Not used
X:$078407 JDISP, J??? Port Data Inversion Control Register
Bits: 0 DISP0 Inversion Control
...
7 DISP7 Inversion Control
8 CTRL0 Inversion Control
...
11 CTRL3 Inversion Control
(All bits: 0=Non-inverting; 1=Inverting)
(All bits must be 0 to use standard port accessories)
12-23 Not used
Y:$078408-$07840B Not used
X:$078408-$07840B Not used
Y:$07840C Pure binary conversion from gray code input on I/O00 to I/O23
X:$07840C Not used
Y:$07840D Gray-to-binary conversion bit-length control
Bits: 0-3 Bit length of less significant word portion (I/O00 - I/Onn)
4 =1 specifies 16-bit lower / 8-bit upper conversion
5-23 Not used
X:$07840D Not used
MACRO Ring Control Registers
MACRO IC# 0 1 2 3
Address $07840E $07940E $07A40E $07B40E
Y:$07x40F MACRO Ring Status and Control (I6840, I6890, I6940, I6990)
Bits: 0 Data overrun error (cleared when read)
1 Byte violation error (cleared when read)
2 Packet parity error (cleared when read)
3 Data underrun error (cleared when read)
4 Master station enable
5 Synchronizing master station enable
6 Sync packet received (cleared when read)
7 Sync packet phase lock enable
8 Node 8 master address check disable
9 Node 9 master address check disable
10 Node 10 master address check disable
11 Node 11 master address check disable
12 Node 12 master address check disable
13 Node 13 master address check disable
14 Node 14 master address check disable
15 Node 15 master address check disable
X:$07x40F MACRO IC clock control register
Bits (Bits 0-11 form I6803 – MACRO IC 0 only)
0-2: Handwheel SCLK* Frequency Control n (f=39.3216MHz/2n, n=0-7)
3-5: JHW/PD PFM Clock* Frequency Control n (f=39.3216MHz/2n, n=0-7)
6-8: DAC Clock* Frequency Control n (f=39.3216MHz / 2n, n=0-7)
9-11: ADC Clock* Frequency Control n (f=39.3216MHz / 2n, n=0-7)
(Bits 12-13 form I6807, I6857, I6907, I6957)
12: Phase Clock Direction (0=output, 1=input)
(This must be 1)
13: Servo Clock Direction (0=output, 1=input)
(This must be 1)
14-15: Not used (report as zero)
(Bits 16-19 form I6801, I6851, I6901, I6951)
16-19: Phase Clock* Frequency Control n
(f = MAXPHASE* / [n+1], n=0-15)
(Bits 20-23 form I6802 – MACRO IC 0 only)
20-23: Servo Clock* Frequency Control n
(f = PHASE* / [n+1], n=0-15)
Supplemental Servo Channel Registers (MACRO IC 0 only)
Chan # 1* 2*
Address $078410 $078418
Y:$07841x Handwheel n Time between last two encoder counts (SCLK cycles)
X:$07841x Supplementary Channel n* (Handwheel n) Status Word
Bits: 0-2 Capture Hall Effect Device State
3 Invalid demultiplex of C, U, V, & W
4-6 Reserved for future use (reports as 0)
(Shifted out MSB first one bit per DAC_CLK cycle, starting on rising
edge of phase clock; appears on SEL0 if in dedicated mode)
X:$07841C Supplementary PWM, PFM, MaxPhase* Control Word
Bits: 0-7: PWM* Dead Time (16*PWM* CLK cycles) (I6804)
also PFM* pulse width (PFM* CLK cycles)
8-23: PWM* Max Count Value (I6800)
PWM* Frequency = 117.96MHz / [2*(MaxCount+1)]
"MaxPhase*" Frequency = 2*PWM* Frequency
Chan # 1* 2*
Address $078415 $07841D
Y:$07841x Supplementary Channel n* ADC A Input Value (uses SEL2 in dedicated mode)
Bits: 6-23: Serial ADC Value
0-5: Not used
X:$07841x Supplementary Channel n* (Handwheel n) Control Word
(Bits 0-3 form I68n0)
Bits 0-1: Encoder Decode Control
00: Pulse and direction decode
01: x1 quadrature decode
10: x2 quadrature decode
11: x4 quadrature decode
2-3: Direction & Timer Control
00: Standard timer control, external signal source, no inversion
01: Standard timer control, external signal source, invert direction
10: Standard timer control, internal PFM source, no inversion
11: Alternate timer control, external signal source
(Bits 4-7 form I68n2)
4-5: Position Capture Control
00: Software capture (by setting bit 6)
01: Use encoder index alone
10: Use capture flag alone
11: Use encoder index and capture flag
6: Index Capture Invert Control (0=no inversion, 1=inversion)
7: Flag Capture Invert Control (0=no inversion, 1=inversion)
8-9: Capture Flag Select Control (I68n3)
00: Home Flag (HMFLn*)
01: Positive Limit (PLIMn*)
10: Negative Limit (MLIMn*)
11: User Flag (USERn*)
10: Encoder Counter Reset Control (1=reset)
11: Position Compare Initial State Write Enable
12: Position Compare Initial State Value
13: Position Compare Channel Select (I68n1)
(0= use this channel's encoder; 1=use first encoder on IC)
14: AENAn* output value
15: Gated Index Select for Position Capture (I68n4)
(0=ungated index, 1=gated index)
16: Invert AB for Gated Index (I68n5)
(0: Gated Signal=A&B&C; 1: Gated Signal=A/&B/&C)
17: De-multiplex Index Channel Control
Y:$07841x Supplementary Channel n* ADC B Input Value (uses SEL3 in dedicated mode)
Bits: 6-23: Serial ADC Value
0-5: Not used
X:$07841x Handwheel n Compare Auto-increment value (24 bits, units of counts)
Chan # 1* 2*
Address $078417 $07841F
Servo IC 2 Registers for First Acc-24 Channel 3 (usually for Motor #11)
M1101->X:$078209,0,24,S ; ENC3 24-bit counter position
M1102->Y:$07820B,8,16,S ; DAC3 16-bit analog output
M1103->X:$07820B,0,24,S ; ENC3 capture/compare position register
M1105->Y:$07820E,8,16,S ; ADC3 16-bit analog input
M1106->Y:$078208,0,24,U ; ENC3 time between counts (SCLK cycles)
M1110->X:$078208,10,1 ; ENC3 count-write enable control
M1111->X:$078208,11,1 ; EQU3 compare flag latch control
M1112->X:$078208,12,1 ; EQU3 compare output enable
M1113->X:$078208,13,1 ; EQU3 compare invert enable
M1114->X:$078208,14,1 ; AENA3/DIR3 Output
M1116->X:$078208,16,1 ; EQU3 compare flag
M1117->X:$078208,17,1 ; ENC3 position-captured flag
M1118->X:$078208,18,1 ; ENC3 Count-error flag
M1119->X:$078208,19,1 ; ENC3 3rd channel input status
M1120->X:$078208,20,1 ; HMFL3 input status
M1121->X:$078208,21,1 ; -LIM3 (positive end) input status
M1122->X:$078208,22,1 ; +LIM3 (negative end) input status
M1123->X:$078208,23,1 ; FAULT3 input status
Motor #11 Status Bits
M1130->Y:$0005C0,11,1 ; #11 Stopped-on-position-limit bit
M1131->X:$0005B0,21,1 ; #11 Positive-end-limit-set bit
M1132->X:$0005B0,22,1 ; #11 Negative-end-limit-set bit
M1133->X:$0005B0,13,1 ; #11 Desired-velocity-zero bit
M1135->X:$0005B0,15,1 ; #11 Dwell-in-progress bit
M1137->X:$0005B0,17,1 ; #11 Running-program bit
M1138->X:$0005B0,18,1 ; #11 Open-loop-mode bit
M1139->X:$0005B0,19,1 ; #11 Amplifier-enabled status bit
M1140->Y:$0005C0,0,1 ; #11 Background in-position bit
M1141->Y:$0005C0,1,1 ; #11 Warning-following error bit
M1142->Y:$0005C0,2,1 ; #11 Fatal-following-error bit
M1143->Y:$0005C0,3,1 ; #11 Amplifier-fault-error bit
M1144->Y:$0005C0,13,1 ; #11 Foreground in-position bit
M1145->Y:$0005C0,10,1 ; #11 Home-complete bit
M1146->Y:$0005C0,6,1 ; #11 Integrated following error fault bit
M1147->Y:$0005C0,5,1 ; #11 I2T fault bit
M1148->Y:$0005C0,8,1 ; #11 Phasing error fault bit
M1149->Y:$0005C0,9,1 ; #11 Phasing search-in-progress bit
Motor #11 Move Registers
M1161->D:$000588 ; #11 Commanded position (1/[Ixx08*32] cts)
M1162->D:$00058B ; #11 Actual position (1/[Ixx08*32] cts)
M1163->D:$0005C7 ; #11 Target (end) position (1/[Ixx08*32] cts)
M1164->D:$0005CC ; #11 Position bias (1/[Ixx08*32] cts)
M1166->X:$00059D,0,24,S ; #11 Actual velocity (1/[Ixx09*32] cts/cyc)
M1167->D:$00058D ; #11 Present master pos (1/[Ixx07*32] cts)
M1168->X:$0005BF,8,16,S ; #11 Filter Output (16-bit DAC bits)
M1169->D:$000590 ; #11 Compensation correction (1/[Ixx08*32] cts)
M1170->D:$0005B4 ; #11 Present phase position (including fraction)
M1171->X:$0005B4,24,S ; #11 Present phase position (counts *Ixx70)
M1172->L:$0005D7 ; #11 Variable jog position/distance (cts)
M1173->Y:$0005CE,0,24,S ; #11 Encoder home capture position (cts)
Servo IC 5 Registers for Second Acc-24 Channel 8 (usually for Motor #24)
M2401->X:$07930D,0,24,S ; ENC8 24-bit counter position
M2402->Y:$07930A,8,16,S ; DAC8 16-bit analog output
M2403->X:$07930F,0,24,S ; ENC8 capture/compare position register
M2405->Y:$07930F,8,16,S ; ADC8 16-bit analog input
M2406->Y:$07930C,0,24,U ; ENC8 time between counts (SCLK cycles)
M2410->X:$07930C,10,1 ; ENC8 count-write enable control
M2411->X:$07930C,11,1 ; EQU8 compare flag latch control
M2412->X:$07930C,12,1 ; EQU8 compare output enable
M2413->X:$07930C,13,1 ; EQU8 compare invert enable
M2414->X:$07930C,14,1 ; AENA8/DIR8 Output
M2416->X:$07930C,16,1 ; EQU8 compare flag
M2417->X:$07930C,17,1 ; ENC8 position-captured flag
M2418->X:$07930C,18,1 ; ENC8 Count-error flag
M2419->X:$07930C,19,1 ; ENC8 3rd channel input status
M2420->X:$07930C,20,1 ; HMFL8 input status
M2421->X:$07930C,21,1 ; -LIM8 (positive end) input status
M2422->X:$07930C,22,1 ; +LIM8 (negative end) input status
M2423->X:$07930C,23,1 ; FAULT8 input status
Motor #24 Status Bits
M2430->Y:$000C40,11,1 ; #24 Stopped-on-position-limit bit
M2431->X:$000C30,21,1 ; #24 Positive-end-limit-set bit
M2432->X:$000C30,22,1 ; #24 Negative-end-limit-set bit
M2433->X:$000C30,13,1 ; #24 Desired-velocity-zero bit
M2435->X:$000C30,15,1 ; #24 Dwell-in-progress bit
M2437->X:$000C30,17,1 ; #24 Running-program bit
M2438->X:$000C30,18,1 ; #24 Open-loop-mode bit
M2439->X:$000C30,19,1 ; #24 Amplifier-enabled status bit
M2440->Y:$000C40,0,1 ; #24 Background in-position bit
M2441->Y:$000C40,1,1 ; #24 Warning-following error bit
M2442->Y:$000C40,2,1 ; #24 Fatal-following-error bit
M2443->Y:$000C40,3,1 ; #24 Amplifier-fault-error bit
M2444->Y:$000C40,13,1 ; #24 Foreground in-position bit
M2445->Y:$000C40,10,1 ; #24 Home-complete bit
M2446->Y:$000C40,6,1 ; #24 Integrated following error fault bit
M2447->Y:$000C40,5,1 ; #24 I2T fault bit
M2448->Y:$000C40,8,1 ; #24 Phasing error fault bit
M2449->Y:$000C40,9,1 ; #24 Phasing search-in-progress bit
Motor #24 Move Registers
M2461->D:$000C08 ; #24 Commanded position (1/[Ixx08*32] cts)
M2462->D:$000C0B ; #24 Actual position (1/[Ixx08*32] cts)
M2463->D:$000C47 ; #24 Target (end) position (1/[Ixx08*32] cts)
M2464->D:$000C4C ; #24 Position bias (1/[Ixx08*32] cts)
M2466->X:$000C1D,0,24,S ; #24 Actual velocity (1/[Ixx09*32] cts/cyc)
M2467->D:$000C0D ; #24 Present master pos (1/[Ixx07*32] cts)
M2468->X:$000C3F,8,16,S ; #24 Filter Output (16-bit DAC bits)
M2469->D:$000C10 ; #24 Compensation correction (1/[Ixx08*32] cts)
M2470->D:$000C34 ; #24 Present phase position (including fraction)
M2471->X:$000C34,24,S ; #24 Present phase position (counts *Ixx70)
M2472->L:$000C57 ; #24 Variable jog position/distance (cts)
M2473->Y:$000C4E,0,24,S ; #24 Encoder home capture position (cts)
M7017->Y:$078A00,17,1 ; MI/O17
M7018->Y:$078A00,18,1 ; MI/O18
M7019->Y:$078A00,19,1 ; MI/O19
M7020->Y:$078A00,20,1 ; MI/O20
M7021->Y:$078A00,21,1 ; MI/O21
M7022->Y:$078A00,22,1 ; MI/O22
M7023->Y:$078A00,23,1 ; MI/O23
M7024->Y:$078A01,0,1 ; MI/O24
M7025->Y:$078A01,1,1 ; MI/O25
M7026->Y:$078A01,2,1 ; MI/O26
M7027->Y:$078A01,3,1 ; MI/O27
M7028->Y:$078A01,4,1 ; MI/O28
M7029->Y:$078A01,5,1 ; MI/O29
M7030->Y:$078A01,6,1 ; MI/O30
M7031->Y:$078A01,7,1 ; MI/O31
M7032->Y:$078A01,8,1 ; MI/O32
M7033->Y:$078A01,9,1 ; MI/O33
M7034->Y:$078A01,10,1 ; MI/O34
M7035->Y:$078A01,11,1 ; MI/O35
M7036->Y:$078A01,12,1 ; MI/O36
M7037->Y:$078A01,13,1 ; MI/O37
M7038->Y:$078A01,14,1 ; MI/O38
M7039->Y:$078A01,15,1 ; MI/O39
M7040->Y:$078A01,16,1 ; MI/O40
M7041->Y:$078A01,17,1 ; MI/O41
M7042->Y:$078A01,18,1 ; MI/O42
M7043->Y:$078A01,19,1 ; MI/O43
M7044->Y:$078A01,20,1 ; MI/O44
M7045->Y:$078A01,21,1 ; MI/O45
M7046->Y:$078A01,22,1 ; MI/O46
M7047->Y:$078A01,23,1 ; MI/O47
Encoder Conversion Table Result Registers (M8xxx matches I8xxx)
M8000->X:$003501,0,24,S ; Line 0 result from conversion table
M8001->X:$003502,0,24,S ; Line 1 result from conversion table
M8002->X:$003503,0,24,S ; Line 2 result from conversion table
M8003->X:$003504,0,24,S ; Line 3 result from conversion table
M8004->X:$003505,0,24,S ; Line 4 result from conversion table
M8005->X:$003506,0,24,S ; Line 5 result from conversion table
M8006->X:$003507,0,24,S ; Line 6 result from conversion table
M8007->X:$003508,0,24,S ; Line 7 result from conversion table
M8008->X:$003509,0,24,S ; Line 8 result from conversion table
M8009->X:$00350A,0,24,S ; Line 9 result from conversion table
M8010->X:$00350B,0,24,S ; Line 10 result from conversion table
M8011->X:$00350C,0,24,S ; Line 11 result from conversion table
M8012->X:$00350D,0,24,S ; Line 12 result from conversion table
M8013->X:$00350E,0,24,S ; Line 13 result from conversion table
M8014->X:$00350F,0,24,S ; Line 14 result from conversion table
M8015->X:$003510,0,24,S ; Line 15 result from conversion table
M8016->X:$003511,0,24,S ; Line 16 result from conversion table
M8017->X:$003512,0,24,S ; Line 17 result from conversion table
M8018->X:$003513,0,24,S ; Line 18 result from conversion table
M8019->X:$003514,0,24,S ; Line 19 result from conversion table
Servo Cycle Counter (Read Only) – counts up once per servo cycle
M100->X:$000000,0,24,S ; 24-bit servo cycle counter
Servo IC 0 Registers for PMAC2 Channel 1 (usually for Motor #1)
M101->X:$078001,0,24,S ; ENC1 24-bit counter position
M102->Y:$078002,8,16,S ; OUT1A command value; DAC or PWM
M103->X:$078003,0,24,S ; ENC1 captured position
M104->Y:$078003,8,16,S ; OUT1B command value; DAC or PWM
M105->Y:$078005,8,16,S ; ADC1A input value
M106->Y:$078006,8,16,S ; ADC1B input value
M107->Y:$078004,8,16,S ; OUT1C command value; PFM or PWM
M108->Y:$078007,0,24,S ; ENC1 compare A position
M109->X:$078007,0,24,S ; ENC1 compare B position
M110->X:$078006,0,24,S ; ENC1 compare autoincrement value
M111->X:$078005,11 ; ENC1 compare initial state write enable
M112->X:$078005,12 ; ENC1 compare initial state
M114->X:$078005,14 ; AENA1 output status
M115->X:$078000,19 ; USER1 flag input status
M116->X:$078000,9 ; ENC1 compare output value
M117->X:$078000,11 ; ENC1 capture flag
M118->X:$078000,8 ; ENC1 count error flag
M119->X:$078000,14 ; CHC1 input status
M120->X:$078000,16 ; HMFL1 flag input status
M121->X:$078000,17 ; PLIM1 flag input status
M122->X:$078000,18 ; MLIM1 flag input status
M123->X:$078000,15 ; FAULT1 flag input status
M124->X:$078000,20 ; Channel 1 W flag input status
M125->X:$078000,21 ; Channel 1 V flag input status
M126->X:$078000,22 ; Channel 1 U flag input status
M127->X:$078000,23 ; Channel 1 T flag input status
M128->X:$078000,20,4 ; Channel 1 TUVW inputs as 4-bit value
Motor #1 Status Bits
M130->Y:$0000C0,11,1 ; #1 Stopped-on-position-limit bit
M131->X:$0000B0,21,1 ; #1 Positive-end-limit-set bit
M132->X:$0000B0,22,1 ; #1 Negative-end-limit-set bit
M133->X:$0000B0,13,1 ; #1 Desired-velocity-zero bit
M135->X:$0000B0,15,1 ; #1 Dwell-in-progress bit
M137->X:$0000B0,17,1 ; #1 Running-program bit
M138->X:$0000B0,18,1 ; #1 Open-loop-mode bit
M139->X:$0000B0,19,1 ; #1 Amplifier-enabled status bit
M140->Y:$0000C0,0,1 ; #1 Background in-position bit
M141->Y:$0000C0,1,1 ; #1 Warning-following error bit
M142->Y:$0000C0,2,1 ; #1 Fatal-following-error bit
M143->Y:$0000C0,3,1 ; #1 Amplifier-fault-error bit
M144->Y:$0000C0,13,1 ; #1 Foreground in-position bit
M145->Y:$0000C0,10,1 ; #1 Home-complete bit
M146->Y:$0000C0,6,1 ; #1 Integrated following error fault bit
M147->Y:$0000C0,5,1 ; #1 I2T fault bit
M148->Y:$0000C0,8,1 ; #1 Phasing error fault bit
M149->Y:$0000C0,9,1 ; #1 Phasing search-in-progress bit
Servo IC 3 Registers for First Acc-24 Channel 7 (usually for Motor #15)
M1501->X:$078311,0,24,S ; ENC7 24-bit counter position
M1502->Y:$078312,8,16,S ; OUT7A command value; DAC or PWM
M1503->X:$078313,0,24,S ; ENC7 captured position
M1504->Y:$078313,8,16,S ; OUT7B command value; DAC or PWM
M1505->Y:$078315,8,16,S ; ADC7A input value
M1506->Y:$078316,8,16,S ; ADC7B input value
M1507->Y:$078314,8,16,S ; OUT7C command value; PFM or PWM
M1508->Y:$078317,0,24,S ; ENC7 compare A position
M1509->X:$078317,0,24,S ; ENC7 compare B position
M1510->X:$078316,0,24,S ; ENC7 compare autoincrement value
M1511->X:$078315,11 ; ENC7 compare initial state write enable
M1512->X:$078315,12 ; ENC7 compare initial state
M1514->X:$078315,14 ; AENA7 output status
M1515->X:$078310,19 ; CHC7 input status
M1516->X:$078310,9 ; ENC7 compare output value
M1517->X:$078310,11 ; ENC7 capture flag
M1518->X:$078310,8 ; ENC7 count error flag
M1519->X:$078310,14 ; CHC7 input status
M1520->X:$078310,16 ; HMFL7 flag input status
M1521->X:$078310,17 ; PLIM7 flag input status
M1522->X:$078310,18 ; MLIM7 flag input status
M1523->X:$078310,15 ; FAULT7 flag input status
M1524->X:$078310,20 ; Channel 7 W flag input status
M1525->X:$078310,21 ; Channel 7 V flag input status
M1526->X:$078310,22 ; Channel 7 U flag input status
M1527->X:$078310,23 ; Channel 7 T flag input status
M1528->X:$078310,20,4 ; Channel 7 TUVW inputs as 4-bit value
Motor #15 Status Bits
M1530->Y:$0007C0,11,1 ; #15 Stopped-on-position-limit bit
M1531->X:$0007B0,21,1 ; #15 Positive-end-limit-set bit
M1532->X:$0007B0,22,1 ; #15 Negative-end-limit-set bit
M1533->X:$0007B0,13,1 ; #15 Desired-velocity-zero bit
M1535->X:$0007B0,15,1 ; #15 Dwell-in-progress bit
M1537->X:$0007B0,17,1 ; #15 Running-program bit
M1538->X:$0007B0,18,1 ; #15 Open-loop-mode bit
M1539->X:$0007B0,19,1 ; #15 Amplifier-enabled status bit
M1540->Y:$0007C0,0,1 ; #15 Background in-position bit
M1541->Y:$0007C0,1,1 ; #15 Warning-following error bit
M1542->Y:$0007C0,2,1 ; #15 Fatal-following-error bit
M1543->Y:$0007C0,3,1 ; #15 Amplifier-fault-error bit
M1544->Y:$0007C0,13,1 ; #15 Foreground in-position bit
M1545->Y:$0007C0,10,1 ; #15 Home-complete bit
M1546->Y:$0007C0,6,1 ; #15 Integrated following error fault bit
M1547->Y:$0007C0,5,1 ; #15 I2T fault bit
M1548->Y:$0007C0,8,1 ; #15 Phasing error fault bit
M1549->Y:$0007C0,9,1 ; #15 Phasing search-in-progress bit
MACRO IC 1 Node 12 Flag Registers (usually used for Motor #15)
M1550->X:$00345C,0,24 ; MACRO IC 1 Node 12 flag status register
M1551->Y:$00345C,0,24 ; MACRO IC 1 Node 12 flag command register
M1553->X:$00345C,20,4 ; MACRO IC 1 Node 12 TUVW flags
Servo IC 6 Registers for Third Acc-24 Channel 2 (usually for Motor #26)
M2601->X:$07A209,0,24,S ; ENC2 24-bit counter position
M2602->Y:$07A20A,8,16,S ; OUT2A command value; DAC or PWM
M2603->X:$07A20B,0,24,S ; ENC2 captured position
M2604->Y:$07A20B,8,16,S ; OUT2B command value; DAC or PWM
M2605->Y:$07A20D,8,16,S ; ADC2A input value
M2606->Y:$07A20E,8,16,S ; ADC2B input value
M2607->Y:$07A20C,8,16,S ; OUT2C command value; PFM or PWM
M2608->Y:$07A20F,0,24,S ; ENC2 compare A position
M2609->X:$07A20F,0,24,S ; ENC2 compare B position
M2610->X:$07A20E,0,24,S ; ENC2 compare autoincrement value
M2611->X:$07A20D,11 ; ENC2 compare initial state write enable
M2612->X:$07A20D,12 ; ENC2 compare initial state
M2614->X:$07A20D,14 ; AENA2 output status
M2615->X:$07A208,19 ; USER2 flag input status
M2616->X:$07A208,9 ; ENC2 compare output value
M2617->X:$07A208,11 ; ENC2 capture flag
M2618->X:$07A208,8 ; ENC2 count error flag
M2619->X:$07A208,14 ; CHC2 input status
M2620->X:$07A208,16 ; HMFL2 flag input status
M2621->X:$07A208,17 ; PLIM2 flag input status
M2622->X:$07A208,18 ; MLIM2 flag input status
M2623->X:$07A208,15 ; FAULT2 flag input status
M2624->X:$07A208,20 ; Channel 2 W flag input status
M2625->X:$07A208,21 ; Channel 2 V flag input status
M2626->X:$07A208,22 ; Channel 2 U flag input status
M2627->X:$07A208,23 ; Channel 2 T flag input status
M2628->X:$07A208,20,4 ; Channel 2 TUVW inputs as 4-bit value
Motor #26 Status Bits
M2630->Y:$000D40,11,1 ; #26 Stopped-on-position-limit bit
M2631->X:$000D30,21,1 ; #26 Positive-end-limit-set bit
M2632->X:$000D30,22,1 ; #26 Negative-end-limit-set bit
M2633->X:$000D30,13,1 ; #26 Desired-velocity-zero bit
M2635->X:$000D30,15,1 ; #26 Dwell-in-progress bit
M2637->X:$000D30,17,1 ; #26 Running-program bit
M2638->X:$000D30,18,1 ; #26 Open-loop-mode bit
M2639->X:$000D30,19,1 ; #26 Amplifier-enabled status bit
M2640->Y:$000D40,0,1 ; #26 Background in-position bit
M2641->Y:$000D40,1,1 ; #26 Warning-following error bit
M2642->Y:$000D40,2,1 ; #26 Fatal-following-error bit
M2643->Y:$000D40,3,1 ; #26 Amplifier-fault-error bit
M2644->Y:$000D40,13,1 ; #26 Foreground in-position bit
M2645->Y:$000D40,10,1 ; #26 Home-complete bit
M2646->Y:$000D40,6,1 ; #26 Integrated following error fault bit
M2647->Y:$000D40,5,1 ; #26 I2T fault bit
M2648->Y:$000D40,8,1 ; #26 Phasing error fault bit
M2649->Y:$000D40,9,1 ; #26 Phasing search-in-progress bit
MACRO IC 3 Node 1 Flag Registers (usually used for Motor #26)
M2650->X:$003471,0,24 ; MACRO IC 3 Node 1 flag status register
M2651->Y:$003471,0,24 ; MACRO IC 3 Node 1 flag command register
M2653->X:$003471,20,4 ; MACRO IC 3 Node 1 TUVW flags
M7010->Y:$078C01,2,1 ; MI/O10
M7011->Y:$078C01,3,1 ; MI/O11
M7012->Y:$078C01,4,1 ; MI/O12
M7013->Y:$078C01,5,1 ; MI/O13
M7014->Y:$078C01,6,1 ; MI/O14
M7015->Y:$078C01,7,1 ; MI/O15
M7016->Y:$078C02,0,1 ; MI/O16
M7017->Y:$078C02,1,1 ; MI/O17
M7018->Y:$078C02,2,1 ; MI/O18
M7019->Y:$078C02,3,1 ; MI/O19
M7020->Y:$078C02,4,1 ; MI/O20
M7021->Y:$078C02,5,1 ; MI/O21
M7022->Y:$078C02,6,1 ; MI/O22
M7023->Y:$078C02,7,1 ; MI/O23
M7024->Y:$078C03,0,1 ; MI/O24
M7025->Y:$078C03,1,1 ; MI/O25
M7026->Y:$078C03,2,1 ; MI/O26
M7027->Y:$078C03,3,1 ; MI/O27
M7028->Y:$078C03,4,1 ; MI/O28
M7029->Y:$078C03,5,1 ; MI/O29
M7030->Y:$078C03,6,1 ; MI/O30
M7031->Y:$078C03,7,1 ; MI/O31
M7032->Y:$078C04,0,1 ; MI/O32
M7033->Y:$078C04,1,1 ; MI/O33
M7034->Y:$078C04,2,1 ; MI/O34
M7035->Y:$078C04,3,1 ; MI/O35
M7036->Y:$078C04,4,1 ; MI/O36
M7037->Y:$078C04,5,1 ; MI/O37
M7038->Y:$078C04,6,1 ; MI/O38
M7039->Y:$078C04,7,1 ; MI/O39
M7040->Y:$078C05,0,1 ; MI/O40
M7041->Y:$078C05,1,1 ; MI/O41
M7042->Y:$078C05,2,1 ; MI/O42
M7043->Y:$078C05,3,1 ; MI/O43
M7044->Y:$078C05,4,1 ; MI/O44
M7045->Y:$078C05,5,1 ; MI/O45
M7046->Y:$078C05,6,1 ; MI/O46
M7047->Y:$078C05,7,1 ; MI/O47
Encoder Conversion Table Result Registers (M8xxx matches I8xxx)
M8000->X:$003501,0,24,S ; Line 0 result from conversion table
M8001->X:$003502,0,24,S ; Line 1 result from conversion table
M8002->X:$003503,0,24,S ; Line 2 result from conversion table
M8003->X:$003504,0,24,S ; Line 3 result from conversion table
M8004->X:$003505,0,24,S ; Line 4 result from conversion table
M8005->X:$003506,0,24,S ; Line 5 result from conversion table
M8006->X:$003507,0,24,S ; Line 6 result from conversion table
M8007->X:$003508,0,24,S ; Line 7 result from conversion table
M8008->X:$003509,0,24,S ; Line 8 result from conversion table
M8009->X:$00350A,0,24,S ; Line 9 result from conversion table
M8010->X:$00350B,0,24,S ; Line 10 result from conversion table
M8011->X:$00350C,0,24,S ; Line 11 result from conversion table
M8012->X:$00350D,0,24,S ; Line 12 result from conversion table
I-Variable Changes
PMAC/PMAC2 Turbo PMAC/PMAC2
Ix00 – Ix86 (x = 1 to 8) Motor I-Variables Ixx00 – Ixx99 (xx = 1 to 32) Motor I-Variables
Ix30 – Ix58 (x = 1 to 8) Option 6 Extended Servo Iyy10 – Iyy39 (xx = 2*[yy-32]-1) for odd-numbered
Algorithm Gains motors;
Iyy60 – Iyy89 (xx = 2*[yy-32]) for even-numbered
motors:
Extended Servo Algorithm Gains (Standard)
Ix87 – Ix99 (x = 1 to 8) Coordinate System I- I5x00 – I5x99 (x = 1 to 9) Coordinate System I-
Variables Variables
I6y00 – I6y99 (y = x – 10; x = 10 to 16) C.S. I-
Variables
I900 – I904, I905 – I909, … I975 – I979 PMAC I7mn0 – I7mn4 (m = 0 to 9, n = 1 to 4) PMAC
Encoder Setup I-Variables Servo IC m Channel n Encoder Setup I-Variables
I900 – I909 PMAC2 Multi-Channel Hardware I7m00 – I7m05 (m = 0 to 9) Servo IC m Multi-
Setup I-Variables Channel Hardware Setup I-Variables
I9n0 – I9n9 (n = 1 to 8) PMAC2 Channel n I7mn0 – I7mn9 (m = 0 to 9, n = 1 to 4) PMAC2
Hardware Setup I-Variables Servo IC m Channel n Hardware Setup I-Variables
I990 – I999 MACRO & Supplemental Channel I6800 – I6849 MACRO IC 0 Hardware Setup I-
Hardware Setup I-Variables Variables
I1000 – I1005 MACRO Software Setup I-Variables I70 – I82 MACRO Software Setup I-Variables
X/Y:$0700 - $0701 User Countdown Timers Isx11, Isx12 Coordinate System Countdown Timers
Y:$0720 – Y:$073F Encoder Conversion Table I8000 – I8191 Encoder Conversion Table Setup
Setup
X:$0783 – X:$078C VME/DPRAM Setup I90 – I99 VME/DPRAM Setup
I7 In-Position Number of Cycles (Global) Ixx88 Motor xx In-Position Number of Cycles
I12 Jog Calculation Time (Global) Ixx92 Motor xx Jog Calculation Time
I13 Move Segmentation Time (Global) Isx13 Coord. Sys. x Move Segmentation Time
I14 Auto Position Match on Run (Global) No I-variable – function always active
I19 Data Gathering Period I47 DPRAM Servo Data Reporting Period
I5049 Data Gathering Period
I20 Data Gathering Mask I5050, I5051 Data Gathering Masks
I21-I44 Data Gathering Source Addresses I5001-I5048 Data Gathering Source Addresses
I45 Data Gathering Buffer Location and Mode I5000 Data Gathering Buffer Location and Mode
I47 Pointer Address for <CTRL-W> Command No I-variable – function not used
I50 Rapid Speed Select (Global) Ixx90 Motor xx Rapid Speed Select
I52 ‘\’ Program Hold Slew Rate (Global) No program hold: ‘\’ is “quick stop” within
lookahead, using Ixx17; “feed hold” out of
lookahead, using Ix95
I53 Single Step Mode (Global) Isx53 Coord. Sys. x Single Step Move
I57 DPRAM Binary Rotary Buffer Enable On-line command OPEN BIN ROT
I59 DPRAM Buffer Max. Motor/C.S. Number DPRAM Motor Enable Mask Word
DPRAM Maximum C.S. Transfer Number
I60, I61 [PMAC] or X:$0708 – X:$070F [PMAC2] I5060 – I5096 A/D Processing Table Setup
A/D Processing Table Setup
I8x Motor x third Resolver Gear Ratio Ixx98 Motor xx third Resolver Gear Ratio
I89 Cutter Comp Outside Corner Break Angle Isx99 Coordinate System x Cutter Comp Outside
(Global) Corner Break Angle
I90 Minimum Arc Length (Global) Isx97 Coordinate System x Minimum Arc Length
I9x Motor x second Resolver Gear Ratio / Yaskawa Ixx99 Motor xx second Resolver Gear Ratio /
Absolute Encoder Ratio Yaskawa Absolute Encoder Ratio
I99 Backlash Hysteresis (Global) Ixx87 Motor xx Backlash Hysteresis
Commutation Changes
PMAC/PMAC2 Turbo PMAC/PMAC2
Commutation lookup table has 256 entries; direct Commutation lookup table has 2048 entries; direct
microstepping yields 64 microsteps per step microstepping yields 512 microsteps per step
Phase reference error bit only set on unsuccessful For any synchronous motor commutated by Turbo
phasing search or read. Loop is not closed then, but PMAC, phase reference error bit set automatically
may be subsequently closed. on power-up/reset. Cleared only on successful
phasing search or read. Loop cannot be closed if bit
is set.
Phasing search move on $ command is exclusive Phasing search move on $ command is non-
background task. No other background task can exclusive background task. Other background tasks
execute until phasing search move is complete. can execute while phasing search move is in
Command acknowledgment to host is not given progress. Command acknowledgment to host is
until move is complete. given when move starts.
Communications Changes
PMAC/PMAC2 Turbo PMAC/PMAC2
Characters received on any communications port are Characters received on each communications port
loaded into a common command queue, so are loaded into a separate command queue for that
simultaneous commands from multiple ports are port, so that simultaneous commands from multiple
intermixed and garbled. ports can be accepted properly.
When a program buffer is open, it can accept A program buffer is opened for a particular port
commands from any port into the buffer, so another only; only commands from that port can be entered
port cannot give on-line commands (in general). into the buffer; other ports can only give on-line
commands.
Jumper Changes
PMAC/PMAC2 Turbo PMAC/PMAC2
PMAC E40 – E43 Card Number/Clock Direction Turbo PMAC E40 – E43 Clock Direction
I0 Serial Card Number
PMAC E44 – E47 Serial Baud Rate Turbo PMAC E44 – E47 (not used)
I54 Serial Baud Rate
PMAC E48 Wait State Control Turbo PMAC E48 (not used)
PMAC1.5 E48 CPU Frequency Control Turbo PMAC E48 (not used)
I52 CPU Frequency Multiplier
PMAC2 E2, E4 CPU Frequency Control I52 CPU Frequency Multiplier
PMAC E50 Save Enable Control Turbo PMAC E50 (not used)
9. Fixed operation of DEFINE GATHER command without argument when gathering set up for dual-
ported RAM.
10. Corrected arctangent calculations for high-resolution encoder interpolation and “two-guess” phasing
search.
11. Fixed the blocking of interrupts around writing to M-variables in background routines to ensure no
corruption when foreground and background routines write to M-variables in the same word.
12. Added capability to stop on desired position limit if Bit 15 of Ixx24 is set to 1. Positive desired
position limit is (Ixx13 – Ixx41); negative desired position limit is (Ixx13 + Ixx41). If Bit 14 of Ixx24
is also set to 1, program will not stop, but motor will saturate at the limit value.
13. Added “auto-detect” capability for Servo ICs and MACRO ICs. I65, I66, I67, and I69, which user
formerly set to tell Turbo which ICs were present, are no longer used. I4900 and I4901 now report
which ICs are present and which type.
14. I19 now specifies which Servo IC or MACRO IC is the source of the servo and phase clock signals
for the system.
15. Added six more hex digits (24 status bits) to the response for the ?? coordinate-system status-query
command, for a total of 18.
16. Improved operation of watchdog timer, so less likely to trip on heavy, but valid, CPU loading. Now
permits user to set required background period for watchdog timer with I20.
17. MSDATE{node#} now returns 4-digit year value.
18. Implemented special forward-kinematic and inverse-kinematic motion-program subroutine buffers for
each coordinate system, created with new OPEN FORWARD and OPEN INVERSE commands. New
variable Isx50 set to 1 causes these buffers to be used. New axis-definition command #{motor}-
>I causes Turbo PMAC to use inverse kinematic routine to convert from axis to motor coordinates.
Number of regular motion program buffers reduced from 256 to 224 to accommodate these new
buffers.
19. Added new run-time error codes 7 (arc radius smaller than tool radius), 8 (forward-kinematic
equation error), and 9 (inverse-kinematic equation error).
20. Added new on-line command EAVERSION to give more complete listing of firmware revision and
type.
21. Added new command IDC to force synchronization of PMAC’s RAM timer with Option 18B non-
volatile timer.
22. Password protection extended to compiled PLCs, user-written servo algorithms, user-written phase
algorithms, forward-kinematic programs, and inverse-kinematic programs.
23. Improved communications response time when multiple ports are used simultaneously.
24. If all motors in a coordinate system are undefined while coordinate system is running a motion
program, program will now stop with a run-time error
25. New variable I21 now permits lockout of changes to classes of I-variables
26. New variable I14 permits retention of structure of temporary buffers through power-down or reset so
they do not have to be redefined.
2. Added new variables I20-I23 to specify base addresses of MACRO ICs 0-3 respectively, providing
flexibility in MACRO ring configurations on UMAC Turbo. These must be set properly to support
automatic firmware functions using these ICs, including multiplexer port functions, display port, and
I6800-I6999.
3. Moved old variables I20 (watchdog timer reset value) and I21 (I-variable lockout control) to their
proper locations of I40 and I41.
4. Default values of address I-variables made more system-specific to reflect what components such as
Servo ICs and MACRO ICs are actually found by the processor.
5. Added 3D cutter-radius compensation with new program commands CC3, NX{data}, NY{data},
NZ(data}, TR{data}, TX{data}, TY{data}, and TZ{data}.
6. Added altered destination RAPID mode move on-line command !{axis}{data} to be able to
break into currently executing RAPID-mode move and change the move on the fly to a new
destination, or execute a RAPID-mode move directly from an on-line command.
7. Extended I49nn controller configuration status I-variables.
8. Made the communications ports independent with respect to opening of program buffers. Only the
port over which the OPEN command was issued can accept buffered program commands, list the open
buffer, learn points into the open buffer, and close the buffer. Other ports can be used simultaneously
for on-line commands.
9. Refined error reporting when closing a program buffer missing ENDIF and/or ENDWHILE. Now
reports ERR009 (program structure error) and only reports the error on closing this particular buffer.
10. Extended Ixx91, Ixx95, and I8000 – I8191 to support parallel position reads in byte-wide sections
from Acc-3E1 and Acc-14E boards.
11. Corrected problem with hardware position capture over MACRO in V.1933,4,5.
12. Corrected problem in DELETE GATHER command that could cause buffer management problems.
13. Corrected problem in cutter compensation in sequencing with non-compensated moves (RAPID,
DWELL, out-of-plane).
14. Corrected problem in cutter compensation with CIRCLE mode lead-in moves.
15. Corrected operation of Isx91 default program parameter after $$$ software reset and in repeated
execution of program.
16. Corrected absolute phase position read of resolver-to-digital converter through MACRO station.
17. Corrected pmatch problem when linear set of axes X, Y, and Z, or U, V, and W were defined out of
order (e.g. #1->X, #2->Z, #3->Y).
18. Corrected operation of pmatch when called from within a motion program (CMD “&nPMATCH”).
6. Added foreground in-position check in servo interrupt, enabled by I13=1. Added foreground in-
position motor status bit (bit 13 of Y:$0000C0, etc.).
7. Permitted disabling of automatic command parsing on Option 9T auxiliary serial port by setting I43
to 1, permitting custom parsing algorithms to be written for serial input of data that is not in PMAC
command format.
8. Permitted loading of binary rotary motion program commands from DPRAM to internal buffer as a
foreground real-time interrupt task instead of a background task with I45=1.
9. Permitted disabling of A/D de-multiplexing with I5080=0.
10. Implemented alternate rotary-axis rollover mode in which the sign of the specified destination value
also specifies the direction to turn to that point. Setting Ixx27 to a negative value enables this mode.
11. Implemented |I|T integrated current limiting function as alternate to existing I2T integrated current
limiting. In |I|T, the magnitude of the current itself, not the square of the current, is integrated and
compared to the Ixx58 limit. Setting the Ixx57 continuous current magnitude value to a negative
number enables this alternate mode. This more accurately tracks the thermal behavior of a constant
voltage-drop device such as an IGBT, whereas I2T is better for constant-resistance devices such as
MOSFETs and motor windings.
12. Implemented automatic clearing of direct current-loop registers to improve direct-PWM control of
permanent-magnet brush motors. This mode is enabled by setting Ixx96 to 1 when Ixx01 bit 0 = 1
(enabling commutation) and Ixx82 > 0 (enabling current loop).
13. Implemented ABR command, permitting fastest possible abort of currently executing program, and
start or restart of a motion program.
14. Implemented time remaining in move register and MOVETIME query command, to support functions
initiated at a fixed time before the end of a commanded move.
15. Implemented SETPHASE command (on-line and buffered) to copy Ixx75 phase value into phase
position register. Useful for correcting the phase position at a known point (e.g. the index pulse) after
an initial rough phasing (e.g. from Hall commutation sensors).
16. Implemented LOCK and UNLOCK commands (on-line and buffered) to control up to eight process
locking bits that can prevent possible conflict of foreground and background tasks attempting to
manipulate the same register.
17. Implemented on-line I{constant}=@I{constant} command, permitting the value of one I-
variable to be set to the address of another I-variable. The main purpose of this command is to be
able to set an address I-variable (e.g. Ixx03, Ixx04, Ixx05, Isx93) to the address of a conversion-table
entry without having to look up the address of that entry.
18. Added capability for UMAC Turbo CPUs to generate their own servo and phase clock signals when
expected clock source is not found. Keeps watchdog timer from tripping so that new clock source
can be established. Bit 3 of X:$000006 set if CPU is generating its own clocks.
19. Resolution of (previously undocumented) real-time clock register L:$000017 changed from 1/256
second to 1/1024 second.
20. Turbo PMACs with extended user data memory options (5x1 or 5x3) have default user buffer of
65,536 words.
21. I52 CPU clock speed multiplier parameter range extended to 14 to support CPU speeds of up to 150
MHz.
22. Resolution of (previously undocumented) real-time interrupt cycle time registers X:$00000B (latest
time) and Y:$00000B (maximum time) changed to 2 CPU clock cycles.
23. Added background cycle time registers X:$000022 (latest time) and Y:$000022 (maximum time)
with resolution of two CPU clock cycles.
24. Internal-use global status bits Servo Active (X:$000006 bit 21) and RTI Active (X:$000006 bit 23)
removed.
25. Implemented anti-windup protection for current-loop integrators. If calculated output is more than
9/8 of saturated output, integrator value is reduced to that which would produce 9/8 of saturation.
26. Corrected operation of cutter compensation for compensated inside corner immediately following
inside-corner introduction of compensation.
27. Extended I68n5/I69n5 and I7mn5 encoder variables to support de-multiplexing of hall commutation
states from Yaskawa encoder third channel (B or newer revision of DSPGATE1/2 Servo/MACRO IC
required).
28. Corrected operation of LIST BLCOMP DEF and LIST TCOMP DEF commands.
29. Corrected algorithm in compiled PLCs for taking INT of a quotient.
30. Corrected deadband gain algorithm for true deadband (Ixx64=-8) with small motor scale factor
(Ixx08~1). With pulse-and-direction output, the previous small remaining residual could cause
dithering.
31. Fixed action of BREQ (Buffer Request) interrupt and control-panel output when entering rotary
motion program commands. This did not work properly in V1.935 and V1.936.
V1.938 Updates (June, 2001)
1. Corrected operation of the UNDEFINE command so it only clears axis definitions in the addressed
coordinate system.
2. Corrected operation of DPRAM binary rotary buffer download through USB interface.
3. Increased commanded velocity saturation value for jog-to-position and RAPID-mode moves from
256M/Ix08 counts/second to 768M/Ix08 counts/second, consistent with other types of moves.
4. Improved noise immunity in conversion-table algorithms for Acc-51 high-resolution analog-encoder
interpolators to decrease chance of quadrant errors due to high noise on analog lines.
5. Corrected VME mailbox communications so that responses of more than 15 characters can be read
properly.
6. Implemented support for Acc-57E Yaskawa/Mitsubishi absolute encoder interface board in Ixx10 and
Ixx95 variables. See Acc-57E manual for details.
7. Implemented support for I-button real-time clock/calendar chip on new Flex CPU design.
8. Limited number of commands that can possibly be pulled off individual port in one background cycle
to 8 to prevent possibility of trapping the background cycle with very high-speed communications.
9. Corrected problem with DEFINE UBUF when background PLCs are enabled.
10. Added support for on-board IEC-1131 ladder/sequential-function-chart programs.
11. Added support for Open Servo compiled servo algorithms
12. Supported negative values of Ixx99 for Yaskawa Sigma I absolute encoders to permit reversal of the
direction sense.
13. Corrected saving and restoring of the value of new variable I7mn9.
V1.939 Updates (March, 2002)
1. Added support for DSP56311 CPU (Option 5Ex).
2. Added new status bit at X:$000006 bit 21 that is set to 1 to indicate that CPU is DSP56311 type
(X:$000006 bit 21 also set to 1 in this case).
3. Moved location of main serial-port communications buffer from $001Exx to $0036xx. Moved
location of host-bus port communications buffer from $001Fxx to $0037xx. Moved location of
synchronous M-variable buffer from $0036xx and $0037xx to $001Exx and $001Fxx. Changes
necessary to support DSP56311 (Option 5Ex) properly.
4. Increased maximum value of Ixx71 Commutation Cycle Size variable from 8,388,607 to 16,777,215.
5. Changed range of Ixx75 Phase Position Offset variable from –8,388,608 – +8,388,607 to 0 –
16,777,215. If a negative value of Ixx75 is specified, it is stored as (Ixx71 + Ixx75), which provides
the same effect (the proper value of Ixx71 must already be specified for the motor).
6. Added new variable I12 to better support on-the-fly changes in vector feedrate during lookahead.
7. Added new variable I30 to support automatic wrapping of compensation tables (the last entry in the
table wraps to become the correction at zero position as well). Existing documentation incorrectly
reported that this was done always in earlier firmware versions, but correction at zero position was
always zero, regardless of last entry.
8. Added support for hardware 1/T using D-revision or newer PMAC2-style DSPGATE1 Servo ICs. In
new conversion table method ($C with mode bit set), the IC computes the timer-based fractional
count value in hardware; the conversion table simply combines it with the whole-count value. This
permits use of the alternate timer mode for sub-count capture and compare.
9. Computational efficiency of dual-ported RAM data reporting buffers was improved.
10. Computational efficiency of commutation calculations was improved about 20%.
11. Permitted foreign characters (ASCII value > 127) to be accepted in comments (after semi-colon)
without causing an error to be reported.
12. Modified timing of multiplexer port interface signals to Acc-34 boards so they will work properly
with Option 5Ex 160MHz CPUs.
13. Fixed problem with BREQ “buffer request” interrupt on ISA/PCI bus.
V1.940 Updates (June, 2003)
1. Added support for DSP56321 CPU (Option 5Fx). Range of I52 CPU Frequency Control variable
extended to 31 (Option 5Fx can run at up to 240 MHz, with I52=23).
2. Implemented support for separate flag addresses for limits, amp flags, and capture flags with new
variables Ixx42 (separate amplifier-flag address) and Ixx43 (separate limit-flag address).
3. Implemented support for sub-count position capture from Revision D PMAC2-style Servo ICs for
move-until-trigger functions with bits 11 and 12 of Ixx24.
4. Does not permit enabling of any motors if global phase clock error bit (X:$000006 bit 3) is set.
Enabling command is rejected in this case with ERR018.
5. Fixed lead-out move problem of 2D cutter compensation.
6. Fixed operation of I2T protection.
7. Improved operation of Extended Servo Algorithm when saturated.
8. Fixed execution of phasing read so will work correctly even when in an overtravel limit.
9. Fixed listing of DISPLAY {variable} statement when 0 fractional digits specified.
10. Fixed operation of on-line coordinate-system Z command.
11. Implemented new variable I37 that can specify additional wait states above the default when
accessing memory and/or I/O.
1. Added new features to manage behavior on cornering and when blending is disabled for other
reasons.
a. Isx81 permits in-position check when blending is disabled (not just momentary stop in
commanded velocity).
b. Isx82 permits an automatic added dwell when blending is disabled.
c. Isx83 sets corner angle threshold between blended and non-blended corners.
d. Isx84 determines whether stop is at beginning or end of added arc for outside corners in
cutter radius compensation when blending disabled on sharp corner.
e. Isx85 sets corner angle threshold between non-blended corners where dwell is added and
where no dwell is added.
2. Added new coordinate system I-variable Isx14 to provide end-of-move anticipation feature.
When MOVETIME command is given to coordinate system and Isx14 is not equal to 0, the sum of
the remaining time and Isx14 is scaled into servo cycles and placed into the Isx11 timer.
3. Added new coordinate-system I-variable Isx78 that specifies maximum centripetal acceleration
for circle moves. If programmed feedrate would cause this limit to be violated, feedrate is
reduced so as not to violate this limit.
4. Added new coordinate-system I-variable Isx79 to control whether axes with a shorter distance in
a multi-axis RAPID move are slowed to finish synchronously with the longest axis, or move at
their own RAPID speed.
5. Added new motion program command CC4 to turn off cutter radius compensation, but without
automatically adding a zero-distance lead-out move when no programmed lead-out move
immediately follows.
6. Added new coordinate-system I-variables Isx15 and Isx16 to support feedrate override at the
segmentation stage.
7. Added new global I-variable I38 to permit execution of a single-line subroutine called from the
same program line as a move command after the move command before the suspension of
program calculations.
8. Added new global “do-nothing” I-variable I65 to permit the user to verify configuration
download.
9. Changed reporting of motor I-variable Ixx68 from unsigned to signed (no change in
functionality).
10. Corrected action of $$$*** command for Option 5Fx 240 MHz CPUs.
11. Corrected checksum reporting over auxiliary serial port.
12. Corrected problem with opening FORWARD or INVERSE kinematic subroutine when PLC is
executing a WHILE loop.
13. Corrected action of IDNUMBER and SID commands with Option 5Fx 240 MHz CPUs.
14. Added support for hardware position capture with high-resolution interpolation of sinusoidal
encoders over the MACRO ring. Requires V1.117 or newer firmware on 8-axis MACRO Station,
V1.203 or newer firmware on 16-axis MACRO Station or MACRO Peripherals.
15. Added support for Modbus Ethernet I/O with new I-variables I67 and I69.
16. Enhanced MACRO ring-break detection
a. Automatically broadcasts ring-break message if detected here
b. Automatically responds to received ring-break message
c. Properly detects ring breaks found at power-up/reset
d. Accepts CLEARFAULT (CLRF) command to reset ring-break fault status
17. Added five-line tracking-filter variant of exponential-filter conversion method ($D) to encoder
conversion table, enabled by setting bit 19 of first setup line to 1, permitting low-pass filter
without steady-state error – suitable for processing feedback data.
18. Changed bias word (third setup I-variable) for high-resolution sinusoidal encoder conversion
($F/$0) in encoder conversion table from a single 24-bit term used on both sine and cosine to two
12-bit terms, one for each signal.
19. Added five-line diagnostic method entry for highly interpolated sinusoidal encoders ($F/$1) in
encoder conversion table to calculate sum-of-squares magnitude or sine/cosine bias word.
20. Added direct resolver conversion method entry ($F/$4) to encoder conversion table.
21. Modified action of “MaxChange” filter in conversion table methods $3, $7, and $F/$3. If
MaxChange is exceeded, result is now changed by “LastChange”, not “MaxChange”, if previous
cycle’s result was good.
22. Added new global status bits for MACRO ring status and Modbus TCP network.
23. Added capability for disabling automatic parser of main serial port with (new) bit 1 of I43.
24. Added capability for fast save of 85 P-variables to special sectors of flash memory with FSAVE,
FREAD, and FSAVECLEAR commands.
25. Added capability to move PID integrator to inside of velocity loop for improved disturbance
rejection with (new) bit 1 of Ixx96. This changes meanings of bits 0 and 1 of first motor status
word.
26. Added automatic emergency-stop function for Turbo PMAC integrated amplifier configurations
(such as Geo Brick).
27. Added new variable I36 to permit separation of abort and enable functions. With I36=1, abort
commands do not enable disabled motors. New commands E and <CTRL-E> enable disabled
motors.
28. Added new single-bit variable I27 to permit input data in TWS-format M-variables from ACC-34
boards to be read on signal line DAT7 instead of the default DAT0 on the JTHW multiplexer
port.
1. Fixed operation of acceleration feedforward gain that was present in V1.941 release.
1. Added new single-bit variable I28 to permit disabling of automatic update of LCD display port.
This allows use of DISP0-7 I/O lines for general purpose I/O.
2. Fixed operation of high-resolution sinusoidal-encoder interpolation conversion using the ACC-
51S interpolator with Turbo PMAC2A-PC/104 and Turbo PMAC2A-Eth Lite (“Clipper”).
3. Will not attempt absolute position read over MACRO ring when there is a MACRO ring fault.
4. After a MACRO-ring “clear fault”, will immediately read ring error status bits in I6840 and
declare a MACRO-ring fault again before trying any ring operations – this prevents possible lock-
ups.
5. Added new control bit (bit 10) to Ixx24 to permit direct-PWM control of two-phase motors.
6. (Geo Brick firmware only) Improved power-on testing of amplifier functions.
1. Added automatic clear of MACRO ring errors before attempting to read absolute power-on servo
and/or phase positions. If ring errors persist after clear, do not perform these reads.
2. Added MACROSTASCIIFREQ set and query commands to facilitate reading and writing of ring
frequencies for all stations.
3. Added new setup variable I29 to permit alternate address for automatic multiplexer port functions
such as TWS-format M-variables for ACC-34 I/O boards.
4. Changed functionality of obsolete MACROAUX (MX), MACROAUXREAD (MXR), and
MACROAUXWRITE (MXW) commands so they now support communications from Turbo
PMAC acting as ring master to Turbo PMACs acting as MACRO-ring slaves.
5. Changed functionality of I71, I73, I75, and I77 MACRO setup variables. Bit values of 0 no
longer specify obsolete “Type 0” slaves; instead support Turbo PMAC as MACRO slave.
6. Added new setup variable Ixx44 to permit motor to run as MACRO slave, accepting cyclical
commands over the MACRO ring.
7. If receives MACRO flag status bit indicating multiple active nodes at same ring address, will set
global status bit X:$6 bit 7 (configuration error) and kill all motors. If this status bit, which also
can be set to indicate a change in the number or type of Servo or MACRO ICs found since last
saved configuration, is set, no motors can be enabled.
1. Added AMPCLRF (amplifier clear fault) command for Geo Brick firmware
2. Cleared “configuration error” global status bit on MACRO “CLRF” (clear fault) command when
in MACRO slave mode.
1. Geo Brick version “A” firmware only: Set “configuration error” global status bit if do not receive
proper response to AMPVER command, preventing subsequent operation. (This means that Geo
Brick LV and Brick Controller cannot use Geo Brick “A” firmware.)
2. Geo Brick version “A” firmware only: No user-write access to I7mn7 output-polarity variables.
3. Geo Brick version “A” firmware only: I7m06 (ADC strobe word) default values changed to
$3FFFFF.
5. Fixed sharp-corner blend threshold decision (Isx83) when spiral move (circle mode with
changing radius) involved at the corner.
6. Fixed ACC-34 access from Turbo PMAC2 Ethernet Ultralite and Turbo PMAC2 RTEX
controllers.
8. Fixed 1ppm error in computed SIN and COS in certain narrow (0.006°) bands – had been correct
to single-precision floating point resolution only before in these bands.
10. Implemented new option to “kill” motors on hitting hardware limits. The motor will be “killed”
(open-loop, zero-output, disabled) rather than “aborted” (closed-loop, zero-velocity, enabled) on
hitting a hardware overtravel limit if following conditions are true: (a) bit 8 of Ixx24 is set to 1;
(b) software overtravel limit in that direction (Ixx13, Ixx14) is enabled (!= 0); (c) software limit
in that direction not already hit.
11. New I-variable I35 permits implementation of fail-safe E-stop circuit on Geo Brick LV
controller/amplifier and Brick Controller.
Bits:
20 – 23 Motor Coordinate System Number (-1)
19 TBD
16 –18 Coordinate Definition
15 Motor Defined In Coordinate System
14 Homez Flag
13 Servo In Position
12 Dpos Limit Stop Flag
11 Pos Limit Stop Flag
10 Home Complete Flag
9 $ - Mtr Phase Find Request
8 Phase Finding Error Flag
7 Trigger/Home Move Flag
6 Integrated Following Error Fault
5 I2t Amp Fault
4 Backlash Direction Flag
3 Amp Fault Error
2 Fatal Following Error
1 Soft Following Error
0 In Position