last revision 2021-07-02


by David N. Sands

Introduction 1.1
Hardware overview1.2
Powering up1.3
About FORTH2.1 Instructions for using Z-cards11
Understanding FORTH2.2 Available modules11.1
Structure of FORTH2.3 Z-card bus11.2
Getting Started2.4 Input-output addressing11.3
Interfacing with the outside world3 Basic robot I/O (input/output)11.4
Mixed precision and Trigonometry4 Serial ports11.5
Saving on Disk5 Electric Gripper drive11.6
Supervisory software6 Power Supply11.7
Turnkey operation7 General purpose I/O expansion11.14
Interrupts 8 Analog and Digital I/O card11.15
Memory Map 9.1 I/O signal conditioners11.16
TIL Characteristics9.2 Remote E-stop circuit11.17
Information block9.2.8 Connector Pin-outs 12
FORTH Glossary10
Terminal and Input/Output Words10.2
Data Words and Constants10.2
Arithmetic Words 10.4
Defining Words 10.5
Control Words 10.6
Timing Words 10.7


The K11R robot controller is modular system based on the eZ80L92 pipelined 16-bit microprocessor. Memory is static RAM which is loaded from flash EPROM upon power up or reset. All the I/O devices and RAM run at the full processor clock speed without wait states and there are no system interrupts unless you create them. So input/output oriented software runs much faster. The controller's language is an implementation of FORTH called Tiny FORTH or TIL (Threaded Interpretive Language) which is concise and efficient. It has the dual advantages of speed and very low memory usage which has made it possible to get a highly complex system into the controller's minimal address space.

Back to Contents


The controller comprises a bench top rack style enclosure containing all power supplies, motor drives and logic cards. There are two logic cards, the CPU and the DSP plugged into an internal bus with space for 2 more cards.

Communication with the computer is via an RS232 connector on the front panel and the teach pendant also connects there. All other connections are to the rear panel. If your computer has USB but not RS232 then ST will supply a converter.

Front Panel

The reset button is only for use in dire circumstances. If it is pressed the robot will have to be initialized again.
Any software you have written which has not been saved with the USAVE command will be lost, but you can reload it from computer.
The other button is the soft stop button -- see
Stop button
The key switch is the power up mode. The modes are:
cold start - this initializes the static RAM and ROBOFORTH ready for use.
warm start - this permits continuing after a reset or power up without having to reload your software (providing it was saved to flash ROM with USAVE).
auto start - this is like warm start except that a chosen word can be made to execute immediately on power up or reset without having to type anything (providing it was saved to flash ROM with USAVE).
The front panel has four lamps: (top to bottom)
Power fail (red) - lights when power is bad. It also lights when the reset button is pressed.
Power OK (green) - indicates power is satisfactory.
When power is turned on the red lamp lights for 1-2 secs then goes out and the green lamp lights. If power fails e.g. a brown-out the red lamp lights and green goes out. Power must be good for 1-2 seconds before it is deemed OK again. See Power Supply, 11.7. When the reset button is pressed both lamps light.
TX (amber) - (Transmit) lights when CPU is transitting characters. When power is first turned on or reset is pressed it flashes briefly as the herald message is sent to the computer. Therefore if no message appears on the computer the problem lies with the computer or cables.
RX (red) - (Receive) lights when character streams are received from the computer e.g. loading project.

There are two relays in the the enclosure: one is a reservior discharge relay as required for CE safety marking and the other is the E-stop extension relay whereby all external E-stop devices are in series and if any device breaks a connection the relay drops out and sends a signal to the software to stop all motors. The circuit runs via a rear jack socket and the controller has a jack plug in that socket with its two terminals linked. Therefore if the jack is removed the robot can not run.

Back to Contents


Cold start

When powered up for the very first time all the system variables must be initialised, For example pointers to the start and finish of user programs will be random in RAM which has not been used before. Before powering up for the first time select COLD on the front panel key switch.

Now connect the computer and switch on the power. The PC should display a message which includes the words "COLD START". The key may now be turned (with power on or off) to the warm start position once you have USAVED your program. If you leave it in the cold start position then any programming you do will be lost when power is next switched on. Note that pressing the reset button is the same as switching power off/on. Cold start could be re-selected deliberately, however, to erase all programs e.g. after a practice session.

Enter ROBOFORTH and press return.

Warm start

Warm start may be selected to retain your programming. When the power is switched on you will see the message "WARM START". All your previously programmed definitions will then be reloaded to RAM from flash memory and still be there without downloading them again (providing they were saved to flash ROM with USAVE).. (Note: ROBWIN downloads them anyway)

Auto start

This is the turnkey mode. See
turnkey operation

Back to Contents


All the key-words and commands in FORTH are organised as a linked list or "dictionary". With each word in the dictionary is kept its definition, as with a conventional dictionary. Each word in the command line is looked up in the dictionary and its "meaning" is executed. If FORTH cannot find the word and it is not a number the word is rejected and the rest of the line ignored.

At its lower levels FORTH can be somewhat cryptic, but it does allow access to the whole machine, like assembly language, yet permits the generation of very high level functions. Programming the machine is done by adding new words to the dictionary, defined in terms of existing words, Yet user software is semi- compiled so is much faster than an interpreter. This combination of speed and high level power makes FORTH particularly suited to the control of machinery. It is also concise and compact (i.e. occupies less memory).

Back to Contents


If you already know about FORTH please skip this section. Go directly to 3. Interfacing with the Outside World

Without wishing to embark on a tutorial on FORTH, I would just like to outline the fundamentals of FORTH for the benefit of readers not acquainted with the language.
Note: In all my examples of exchanges between man and machine I will show text typed in by the user in green and underlined. I won't keep mentioning the need for the RETURN (or ENTER) key. The computer's response will be in upper case, and not in green. My comments will be in lower case.

There are probably five fundamental characteristics-

2.2.1 - Command line.

Commands and numbers are typed in by the user, separated by spaces, finishing with return. FORTH then scans the user's line acting on each word, and if everything works out OK then FORTH types OK.

2.2.2 - the Stack

All arguments are passed between procedures on a data stack. A stack is an area of memory into which values are placed temporarily on a last-in first-out basis. Variables are used, but not as much as in other languages.

Part of the reason for this is to maximise the performance of the system. Suppose you wish to add 4 and 5 together and print the result:- In the BASIC statement PRINT 4 + 5 the operator '+' gets one of its "arguments" (values) from its left, and the other from its right. This may seem logical to humans but a machine must first organise its arguments before it can do arithmetic, and almost any language will first convert a formula to items on a stack. The equivalent in FORTH is therefore:-

>4 5 + . (return) 9 OK

FORTH scans the user's input line and first puts 4 on the stack, then puts 5 on the stack. The FORTH word '+' then takes two values off the stack ( 5 and 4 ). adds them together and puts the answer back on the stack, the value 9. The FORTH abbreviation '.' then prints it. This is sometimes called post-fix notation.

There is now nothing on the stack. If we try to print again we get the message "STACK UNDERFLOW!" which is not OK.

But the FORTH data stack doesn't exist to make everyone think like a machine. At worst post-fix notation is a minor inconvenience. Imagine that we wish to calculate the total content of two tanks of chemical. Each tank has a transducer in it with a complicated service routine, as follows:-

1 Select the transducer and energise.
2 Allow the signal conditioners to settle.
3 Read the ADC.
4 Scale the result according to the calibration factor of the transducer.
5 Leave the scaled result on the stack.

Each tank has it's own service routine, called LEFT-TANK and RIGHT-TANK. The total of both tanks is given by:-


Now LEFT-TANK and RIGHT-TANK are not values! Nor variables. We are not doing PRINT X + Y. They are whole procedures which leave their results on the stack. There can even be other words between LEFT-TANK and RIGHT-TANK as long as they don't take off or put on extra items on the stack for example:-


Though the stack is used extensively to pass arguments, variables also exist and are handled with the words ! ("store") and @ ("fetch"). ! means "store the second value down on the stack into the address which is the top item on the stack. @ means "fetch the contents of the address on the stack and leave it in its place".

2.2.3 - the Dictionary

Instead of a handful of keywords as in, for example BASIC, there are hundreds of words, which are organised in a "dictionary". FORTH interprets a user's word by searching down the dictionary until it finds it, then carries out the activity which is in the "definition" of the word. If the word isn't in the dictionary then FORTH tries to convert it as a number. If it isn't a valid number either then FORTH declares it an error.

Most LOW level words in FORTH tend to be abbreviations, or single characters, for example the FORTH word for "print" is just a dot (.) whereas higher level procedures tend to have highly descriptive names. Abbreviations have agreed pronunciations, e.g. dot (.) is pronounced "print", ! is pronounced "store", @ is pronounced "fetch" etc. Pronunciations will be given as they arise.

2.2.4 - Definitions

This principle is fundamental to FORTH users. It is the building-block approach to programming.

FORTH, in its basic form, consists of a "kernel" of some 150 or so "words" or commands, most of which are "primitives" i.e. they directly execute machine code whenever they are used. The programmer must define new words in terms of words already in the kernel. He/she can then define higher level words in terms of words he/she has already defined plus words from the kernel as necessary. These new words are added to the existing dictionary.
Hence the programmer begins by defining short concise procedures which can be tested individually. In this way the user builds up a range of fully tested modules which are then used to construct more powerful procedures, and so on until the final application programme is complete, which can be just one word. The modular approach imparts a very high degree of confidence to the final application.

New procedures are created using a colon sign, followed by the name of the procedure, then the definition ending with a semi- colon, for example-


Now all you have to do is type TANKS? to yield the total in both tanks, or alternatively TANKS? can be included in the definition of some grander procedure.

Note that in this version of FORTH all words are stored in the dictionary as a length figure followed by the first 5 characters only of the word. Sometimes ambiguity has to be avoided, for example LATHE1 and LATHE2 have the same lengths and the same first 5 characters so 1LATHE and 2LATHE are better words.

2.2.5 - Decisions

There are 3 main decision making forms: IF-THEN, BEGIN-UNTIL and DO-LOOP.

condition IF action THEN
IF needs a value on the stack. That is condition. If the value is non-zero then action happens but if the value is zero then your program jumps to the end after THEN. The word THEN marks the end of the IF statement. In some languages it is called ENDIF.
Unlike a syntactic language you can not use IF X = Y THEN action
The equivalent would be X @ Y @ = IF action THEN
This fetches the value from X then fetches the value from Y. Now both those values are on the stack. = compares them and if the two values are equal it leaves true on the stack (usually the value 1). If the values are not equal then it leaves zero.
So using the above examples you might write a definition

The BEGIN-UNTIL form is a loop, for example:
so the valve stays on until the total of LEFT-TANK and RIGHT-TANK adds up to more than 5000 then the valve goes off.

The DO-LOOP is like FOR-NEXT in BASIC. It requires a starting and finishing number.
However (unlike BASIC) the upper limit is never used so you would hear 4 BEEPs.
So you might want to increase the upper limit by 1.
: TEST 6 1 DO BEEP 1000 MSECS LOOP ; does 5 BEEPs at one second intervals
or : TEST 5 0 DO BEEP 500 MSECS LOOP ; which is the same.
You can leave off the upper limit and supply it later:
9 BEEPS - beeps 9 times at half second intervals.

: TEST 6 1 DO I . LOOP ;
I is the index of the loop and increments by 1 each time round. When the index reaches the upper limit the LOOP ends. TEST would result in:
TEST 1 2 3 4 5 OK

2.2.6 - Integers

The standard representation of a number in Forth is a 16 bit integer. A single stack entry is a 16-bit value (which occupies 2 bytes in a byte oriented machine). Arithmetic is done with 16-bit twos complement values in the range -32768 to +32767 unless unsigned integers are specified (0-65535). To assist with scaling mixed precision arithmetic is provided in which the intermediate result of a computation can occupy 32 bits (double precision), i.e two stack entries. Floating point arithmetic is provided in some FORTHs but integer arithmetic is much faster. Even trigonometry can be performed using integers (see trigonometry section) with an implied decimal point.

Because the K11 CPU (but not its DSP) is a byte (8-bit) oriented machine values are stored in two successive 8-bit memory locations. The highest value 8 bits occupies the highest memory address. The word @ fetches both bytes as a 16 bit value and the word ! writes back two 8-bit values in succession.
To obtain the necessary memory space the K11 has two banks of 64k 8 bit memory. These are addressed using one 16 bit address and a value in a location called BANK. When BANK is 0 this refers to the frst 64k and when BANK is 1 this refers to the second 64k. 8-bit (single byte) values can be manipulated using FORTH words like C@ C! C1SET (the C is historical and stands for character i.e. byte) and IN and OUT. These values occupy 16 bit stack entries, with the highest 8 bits all zero. There is also a 32-bit precision occupying 4 locations and accessed with 2@ and 2! (2 for double precision).
For extended memory the words are E@ and E! These fetch or store from 2 successive locations in memory bank 1.

Back to Contents


The structure of a FORTH word is as follows:-

First there is a header. This is the dictionary entry containing the spelling of the word plus a link to the previous word in the dictionary. The dictionary is a linked list of words which enables any word to be found by following the links. Next is the code field. This is the 16-bit address of some machine code which determines what the word is actually going to do.

Next is the parameter field. This is a list of 16-bit values which may be data, as in an array, or only one value for a variable or a constant. If you had defined the word as a procedure in terms of other words then the parameter list would comprise a list of the other words' code field addresses. These other words may also comprise lists of other words and so on, and this is why FORTH is called a "threaded interpreter". Whenever a word is executed the threads are followed deeper into the dictionary until machine code is found.
Please see
TIL Characteristics
Consider the example:

The header contains the word "STAR". The code field points to some machine code which takes the contents of the parameter field and puts it on the stack for following words to use, e.g.

The parameter field is 2 bytes long and contains the value 42. Words defined with the defining-word VARIABLE leave the address of their parameter fields on the stack, so that the contents of the parameter fields can be fetched using the @ sign, or values can be stored back using the ! sign. e.g.

>42 STAR ! OK

>STAR @ . 42 OK

To define a procedure the defining-word used is the colon sign (:) which puts the system into compile mode so that words which follow in the definition are looked up in the dictionary, and their code field addresses are added to the PARAMETER list of the new word. The value put into the CODE field is the address of some machine code which, when the new word is executed, will begin the process of following the threads and executing the machine code found at the bottom of each thread. The machine code which follows the threads down and back up, keeping track of where it has got to in each word, is called the "inner interpreter". Code at the end of each list tells the inner interpreter to end this word and return to the next level up. The inner interpreter is concise and efficient to ensure fast execution of high level definitions. The "outer interpreter" is itself a word which gets the users commands and executes them, checking for errors etc.

Back to Contents


When the system is cold-started (see powering up) it automatically adopts the hexadecimal numbering system. This is frequently more appropriate for controlling binary entities such as analog-to-digital converters, memory and port addresses etc. but real engineering units are best handled in decimal, so before anything else enter:


It is now ESSENTIAL to read a recommended book as it is beyond the scope of this manual to include a full tutorial. In the absence of such a book then refer to the GLOSSARY before continuing. By way of advice programming should begin by thinking out a control problem from the top down, i.e. try to decide the program flow at the highest level, and then break it down into smaller parts as you think out the problems of interfacing with external machinery etc. Then begin to code the lowest levels. Where possible try to use the stack and not variables because this can save alot of execution time in lower level words.

Keeping track of the stack

As an aid to stack use it is useful to draw up a list in which the stack values can be written next to the instructions. Consider the word PULSE which pulses an output port bit on for one second then off again:

The word PULSE is not part of FORTH or ROBOFORTH so you would add it thus:

Let us trace its operation on the values PA 2 e.g. PA 2 PULSE

      Stack | Instruction | Index
         PA | PA          |
       PA 2 | 2           |
    PA 2 PA | OVER        |
  PA 2 PA 2 | OVER        |
       PA 2 | ON          | (uses up one set of PA 2)
  PA 2 1000 | 1000        |
       PA 2 | MSECS       | (uses up the 1000 for 1sec delay)
            | OFF         | (OFF uses up the remaining PA 2)

Back to Contents


The following examples apply to the basic I/O which is part of the CPU card. Additional I/O cards such as 11-48 and 11-56 are similar but have different port names.

The CPU has three ports which are called PA PB and PC.

TO OUTPUT connect to PA as indicated on connector pinout. Suppose there were an air solenoid connected to PA 4. You could turn it on with:-
and off with:-

A better idea would be to define AIR as follows:-
: AIR PA 4 ;

Now you can type (or include in a higher level definition):-

TO INPUT connect to PB as indicated on connector pin-out. Suppose there were a switch on PB bit 4 which made PB 4 logic zero when closed, but logic '1' when open (see connector pin- outs) You could define a word:-

This can be tested thus:
SWITCH . 16 (meaning switch is open) (note 16 decimal = 10 hex)

SWITCH . 0 (meaning switch is closed)

Suppose you would like to synchronise some activity to an pushbutton connected to PB 4. For the purposes of words like IF and UNTIL any value is TRUE and zero is FALSE. Using the FORTH building block approach definitions could be built up as follows:-

BEGIN ... UNTIL is a loop which executes all the words between BEGIN and UNTIL. A condition (true of false) must be on the stack before UNTIL. If the condition is false (zero) then the program loops back to BEGIN but if it is true (non-zero) it drops through to the next word.

The word 0= takes a stack value and if it is zero leaves a true (non-zero) which satisfies UNTIL. This is similar but the signal must be zero to drop out of the loop.
So HI waits for the incoming signal to go high and LO to go low. : WAIT-PB LO HI ; waits for the pulse to go low then high i.e. the button must be pressed then released.

Back to Contents


Suppose you wanted to scale a measurement from the analog-to- digital converter by a factor of, say, 0.514 . You would expect to do this in FORTH as follows:
ADC 514 * 1000 /

The trouble is that if the ADC output is any larger than 63 the multiplication will produce NUMERIC OVERFLOW because the result would have been larger than 32767. We therefore need the precision of 32 bits for the multiplication only and so the correct expression is:
ADC 514 M* 1000 M/

M* multiplies two 16 bit values and leaves a 32 bit value. M/ divides a 32 bit value by a 16 bit value and leaves a 16 bit answer. 32-bit values occupy two stack levels, with the most significant 16 bits on the top of the stack.

Although all values are integers they can have implied decimal points. For trigonometry all angles are in degrees with two implied decimal points, for example the value 1234 represents 12.34 degrees; 90 degrees is entered as 9000. The result of a sine or cosine is a fraction with 4 implied decimal points. Note that hexadecimal numbering is not appropriate.

>6000 COS . 5000 OK i.e. the cosine of 60 degrees is 0.5.

>5000 ASIN . 3000 OK i.e. the arc-sine of 0.5 is 30 degrees.

Functions included are SIN (sine) COS (cosine) ASIN (arc-sine) ACOS (arc-cosine).
TAN is not included but TAN is SIN/COS. You could define your own function thus:
>: TAN DUP SIN 10000 M* ROT COS M/ ; OK

Back to Contents


5.1 Using ROBWIN click file, open (or file, new) to open a text file. To download this to the controller click file, download current. If you edit the text remember to FORGET the first word in the text before reloading. It is best that this word be a USER variable (see 10.5) because FORGETting a USER variable also recovers the data area as well as dictionary space.


The host must be connected via its serial port set up for 19200 baud, no parity, 8 bits, 1 stop bit. The baud rate can be changed to higher (or lower values) (see 11.5. An extremely simple protocol is employed:


To initiate uploading from the controller to the host the host must send an ENQ (5) character to the controller. The controller has first been given the TRANSMIT command and the host computer must also be in some routine to upload and write data to disk, with the file already open.
The controller then sends an STX (2) to the host followed immediately by one block of 256 (100hex) bytes of data. The controller then waits for the host to send another ENQ and sends another STX(2) and the next block of 256 bytes. This repeats until all blocks are sent. When all data is transfered the controller's answer to ENQ is not STX but ETX (3). When the host receives ETX instead of STX it finishes the routine and closed the file.


To initiate downloading from host to controller the host sends an ENQ and waits for STX from the controller. The controller must first have been given the RECEIVE command and the host must also be in some routine to read data from disk and download it.
The host then sends one block (256 bytes) to the controller. The host then sends another ENQ and waits for another STX then sends the next block. This repeats until all the blocks have been downloaded.
The host then sends sends ETX instead of ENQ meaning no more data and the host then stops.

Before using either of the above commands you must specify which of the two memory banks you want to read/load. All coordinates data is in bank 1 so before sending TRANSMIT or RECEIVE use
Or, if the data is in low memory use

Back to Contents


The host computer can control the controller by sending commands down the RS232 serial link. The host software should start by opening the serial channel e.g.

OPEN "COM1:19200,N,8,1,CS,DS,CD" AS #1

The commands can then be PRINTed to the controller e.g. PRINT#1,"PURGE". Each character you send to the controller is echoed back (unless you are in HIDE mode) until the 0D (return) is sent then the controller sends back a space character (20h). There is then no response until the controller has completed the command. All these echoed characters can be allowed to accumulate in the input buffer.
After executing the command the response should always end in a sequence of 5 characters:

O K cr lf >

This response may come (a) immediately, (b) after some unkown time, (c) not at all (in the case of some task which never ends). The host software should look for the >. The preceding string should therefore be OK, if not then there was some error message. In case (c) the host can continue some other task without waiting.
Suggested flow chart for communication with the controller:

NOTE: All characters which come back from the controller must be used up or "buffer overflow" will occur.


In many cases it is desirable to have a program run as soon as power is switched on rather than have to type something every time. In these cases the program to run is a single word, or you might have to generate a new word e.g.:-


The word DEMO can be made to execute immediately on power-up by setting the switch on the front panel to the auto position (see diagram 2) and entering:-

AUTO DEMO and follow with USAVE to save to flash ROM.

Before ever DEMO is forgotten, or words below it re-compiled the key switch must be put back to warm start position until AUTO is used again.

Back to Contents

8. INTERRUPTS (Forth v8 up and Roboforth v11 up)

The BIOS has some code to set up EZ80L92 interrupts. Forth words may be executed by putting the CFA of the word in address Intvec - see information block. INTVEC is defined in ROBOFORTH. The word must end with a direct jump back into the BIOS at address intret (see
Information block) to complete the interrupt. Roboforth has a word RETURN which does this - see Roboforth V11 manual.

The interrupt vector table has only two entries, both to the same interrupt code:
Interrupt from external signal.
A PB input (usually PB 6) should be connected to TP1 on the CPU card.
Look for TP1 on the top side of the board and insert a short piece of tinned copper wire through the hole. Solder one side. Turn over the card and put a length of insulated wire from TP1 to PB 6 (or any PB you prefer). A large orange wire was used in the picture below for visibility but normally a thin prototype wire would be used.

If enabled the chosen word in Intvec will execute upon change of state of PB 6 from high to low.
Enable interrupts with a jump to enh (see Information block). Disable with a jump to dish (see information block).
In RoboForth see section 8.5 On an interrupt occurring further interrupts are disabled. The jump to intret re-enables interrupts. Using a jump to xintret (see Information block) instead of intret leaves interrupts disabled.

Timer interrupt.
A CPU timer can be set to interrupt every n milliseconds. Every n mSecs the chosen word in Intvec is executed. The maximum time is 500 mSecs. To start the timer put the value in mSecs times 125 on the stack and jump to entim (see Information block). To stop the timer jump to distim (see Information block). On an interrupt occurring further interrupts are disabled. The jump to intret re-enables interrupts.
Because of interrupt conflicts do not use the word USECS in any interrupt definition.
You should find it easier to use higher level RoboForth commands

NMI (non maskable interrupt) works as before. Any NMI will cause a call to 66hex and place the value 80hex in INTFLAG at address 9D03 (only one byte). It is up to ROBOFORTH programming to read INTFLAG (with INTFLAG C@) and take any necessary action.

Back to Contents


Back to Contents



Byte Function
1 length of word string plus control bit
2-6 first 5 characters of word
7,8 link address i.e. address of next word down in list
found by FIND
If a primitive: a pointer to the next 2 bytes where machine code starts
If CREATEd or a VARIABLE: a pointer to routine which puts the address
of the parameter field on the stack
If a CONSTANT: a pointer to code which will put the contents of the parameter field on the stack.
If a word definition: a pointer to the inner interpreter to start
interpretation of the parameter list (colon).
If a word defined by a defining word: a pointer to code following DOES>
found by ' (single quote - "tick")
If a primitive: machine code. If a CONSTANT: value of constant.
If word definition: parameter list i.e list of codes of compiled words,
finishing with a pointer to the inner interpreter to stop (semi-colon).
If a VARIABLE: stored value of the variable.
If a USER variable (see 10.5): it is the address of the actual RAM location
of the value.

From above you may see that ambiguous word names are possible because the word is represented as a length plus only the first five letters. If you type VLIST the entire vocabulary will be listed, and the missing characters are printed out as dots. Some FORTHs have variable length headers but the fixed length makes for a faster dictionary search resulting in faster compilation of new words.
If a new word has the same 5 starting letters as a previous word then check the lengths. If same then choose a new name.

Back to Contents


Some words in TIL behave differently from their equivalents in FIG ( Forth Interest Group ) or FORTH '79 standard. These words are listed below:

DUMP (and EDUMP) - prints contents of memory in hexadecimal The start of the dump is rounded down with the actual address indicated by an asterisk in the top line. In other FORTHs this has two arguments: memory address and number of bytes to dump. In TIL only the address is required. Press space bar for the next line of 16 bytes, press return to stop the dump.

LOAD - in other FORTHs n LOAD loads the screen n from disk. In TIL n is a memory address. v15 up - disabled.

VLIST - in other FORTHs this lists the entire vocabulary across the screen, unformatted. In TIL, VLIST lists the vocabulary in the following format: address of dictionary entry i.e. header, not CFA or PFA; length of word name; word name, with any characters after the fifth printed as dots. See variant 'VLIST below. VLIST will print "0 words" when tried the first time with un-initialised memory - repeat the command.

<# # #S and #> work with 16-bit numbers only.

Back to Contents

9.2.3 - NEW WORDS

Words which do not exist in other FORTHs are:

See section 10.

Back to Contents

9.2.4 - 'DEAD' WORDS

Some words exist in the system but cannot be used:

FREEZE - sets the cold start parameters for example pointer to the top of the basic (kernel) dictionary when powered up in cold start mode. Has no effect because these parameters are in EPROM.

SETFORTH - sets the boundary of the FORTH vocabulary at cold start. Has no effect because this is also in read only memory.

DOS - exit TIL to SSD disk operating system which is not installed.

DLOAD, READ, WRITE, DLIST, DLOOK - disk commands - would apply only to the solid state disk system if installed.

Back to Contents

9.2.5 - ERRORS

If you use up a stack value when there is none the message is "STACK UNDERFLOW". This check is not made until your word has fully executed and command mode is re-entered, so too much stack underflow in your word can crash the system.

"NUMERIC OVERFLOW" - result of signed multiply exceeding 32767 or 7FFF hex, or unsigned multiply exceeding FFFF hex or the result of M* exceeding 7FFF FFFF hex.

"DIVIDE BY ZERO" - also fatal error i.e. program cannot continue through such an error.

"ILLEGAL" means you used a compile-only word e.g. a control word or sem-colon (;) when not in compile mode.

"NO DOS" no disk operating system installed.

"DISK ERROR" worse!

While compiling there are no syntax checks in TIL to make sure you use the same number of opening control words as closing control words - e.g. same number of IFs and THENs. During compilation of control loops starting words push addresses to the stack, which are then popped off when ending words are compiled. Thus if loop starts are not matched with loop ends then stack errors will occur:

"STACK UNDERFLOW" - indicates more ending words than starting words eg. more THENs than IFs.

After a definition try X. You should, of course, get the stack underflow message, so if you do not then it is an indication of more starting words than ending words.

If there is no response at all to typing X. then you are still in compile mode (missing semi colon).

Unexplained errors such as unwelcome cold starts or total crashes are usually the result of mis-matched IFs and THENs, or AN IF- THEN or DO-LOOP or BEGIN-UNTIL loop which is physically longer than 127 bytes after compilation. (Remember that each word in a definition reduces to 2 bytes.) Use of ! or any word containing it with incorrect or missing arguments could store some unknown value in some unknown part of memory, for example in the middle of your dictionary. This condition can be corrected by doing a cold start and re-entering or re-loading your software.

Back to Contents


New words are linked to the FORTH vocabulary but form part of the user's vocabulary. Searches start from the top of the dictionary downwards, so if the user creates a word identical to that in the original FORTH then only the new definition will be found.
ROBOFORTH and the user's dictionary are treated as one vocabulary. There is a boundary between words in the original FORTH vocabulary and the ROBOFORTH plus user vocabulary. By typing FORTH searches will begin at this boundary; by typing ROBOT then searches will start from the top of the dictionary.


TEST uses ASPACE in two contexts, and prints two asterisks separated by a space.

Back to Contents



In order to get a word to execute itself it is necessary to push up the dictionary pointers prematurely so to speak, so that the new word is already included in the dictionary when needed within its own definition. To do this use the word LATEST. Ideally you could enter:-

: Q 1- DUP 0 > IF Q THEN ;

Q will recursively decrement the value on TOS to zero. Unfortunately the second Q will not compile, being not yet part of the vocabulary until after the definition is complete (semi- colon). The line would, therefore, be entered as follows:


Back to Contents


The following addresses are significant:

0400 : start of FORTH kernel, cold start entry point.
0417 : High byte of address of start of RAM area.
0418 : FORTH vocabulary boundary.
041A : Version number.
041B : Maximum number of characters stored for each word.
041C : Low byte address of upper limit of dictionary area.
041D : High byte address of upper limit of dictionary area.
041E : Low byte address of outer interpreter.
041F : High byte address of outer interpreter.
0420 : Warm start entry point.
0423 : Auto-start entry point.
042B : Vector to input routines CIN.
042F : Start up number base.
A022 : Intvec (address for the CFA of an interrupting word.)
03C4 : Address of the above. To change the address of intvec change the contents of 03C4.*
0360 : entim
0363 : distim
0366 : enh
0369 : dish
036C : intret
036F : xintret

* note that the values in these addresses are in a protected part of memory and can not be saved to flash. Any changes to these values are lost if the system resets.

Back to Contents


Note: TOS means top of stack.
Note: 1 byte variables must be moved with C@ or C!
Back to Contents


HERE - puts dictionary pointer on stack.
STATE (1 byte) - puts address of mode byte to stack (contents: 1 = compile, 0 = interpret).
DP - puts address of dictionary pointer to stack.
UVP - puts address of user variable pointer to stack.
UVP @ is the next address for the next user variable.
CONTEXT - puts address of context pointer to stack. This contains the address of the word at which the dictionary search starts.
CURRENT - puts address of current pointer to stack. This contains the address of the word to which any newly created word is linked.
DEFINITIONS - causes new words to be added to the current vocabulary
FIND (word) - returns address of code field of the word following FIND. If not found leaves zero.
' (word) - ("tick",single quote) - returns address of parameter field of the word following tick. If not found then aborts.
EXECUTE - (addr) EXECUTE - executes the word whose code field address is on the stack.
BASE (1 byte) - contains ruling number radix.
DECIMAL - converts number system to base 10.
HEX - converts number system to base 16.
CALL - (addr) CALL - calls code at address (addr) which must end in RET if it is intended to return to FORTH. Do not use EXX as FORTH needs those registers, also do not use the IY or IX registers. (unless you save them first)
( - comment. All text after "(" is ignored, until a ")" character is encountered.
FORTH - makes the FORTH vocabulary the context vocabulary, by- passing user's vocabulary.
ROBOT - makes the ROBOT vocabulary the context vocabulary.
LATEST - makes the LATEST vocabulary the context vocabulary including the word currenty being defined. (see
Vocabularies and Recursion)
'S - puts the address of the start of the data stack onto the stack.
S0 - puts the address on the stack of a pointer to a location of the value of the stack pointer, i.e S0 @ X. yields stack pointer.
.S - prints out the contents of the stack without losing them.
>IN - address of the variable holding a pointer to the position in the line input buffer currently being read.
PAD - a constant location of RAM used by text input and output.
TOP - a constant, value is the address of the top of the RAM area used for user variables, system variables and stacks.
QUIT - restarts outer interpreter.
EDIT - OBSOLETE - do not use (jumps to an editor which is no longer installed).
FREEZE - sets cold start parameters for a cold start. (dead)
SETFORTH - sets FORTH boundary to top of dictionary. (dead)
(n) SAVE - writes RAM to FLASH ROM. n is a sector number 0 to 7, where a sector is 4000hex. Sectors 0-3 are in bank 0 and 4-7 are in bank 1. Sector 0 is protected EPROM.
DICLEN (constant) - number of characters stored in a dictionary entry (see information block)
AUTO (word) - makes the following word execute on power up.
TURNKEY - variable containing the code-field-address of the word which is executed on power up.
BANK - pseudo-variable containing bank number - 0 is first 64k, 1 is 2nd 64k and so on.
(n) JUMP - jump to address n. Re-enter FORTH at 420hex. Do a cold start with ORG JUMP or 0 JUMP.

Back to Contents


CR - carriage return and line feed.
X. - (n) X. - prints (n) in hex, 4 digits followed by space.
KEY - wait for key to be pressed, leaves its ASCII value on stack
EMIT - (n) EMIT - send (n) to screen.
BEEP - beeps computer (sends ASCII 7)
OUT - (n) (port) OUT - sends (n) out via port address.
IN - (port) IN - reads port address (n), leaves value on TOS
." ("dot-quote") - syntax: ."(space) (text)" types text as written including any inbedded control characters up to " mark. Note: CAN ONLY BE USED WITHIN A COLON DEFINITION
TYPE - (addr) (n) TYPE - types out (n) characters from address (addr). Printing will stop if an ETX (3) is encountered.
EXPECT - (addr) (n) EXPECT - waits for (n) characters to be typed by the user, these are directed to a string address (addr). Terminates when return key is pressed. The string will end with ETX (3). All positions in the string from when return is pressed until (addr)+(n) are filled with space characters. (see NUMBER) The rules for entering type string are the same as for entering commands. Control characters are: rub-out or back-space = delete last character typed, control-Y = delete entire line, return = enter the line, esc key = abort whatever is happening and go to command level.
WORD - (n) WORD (word or string) - reads further along the input buffer and copies the next word in the buffer to HERE and leaves its address on the stack. (n) is the ASCII value of the character at which copying will stop ( normally 20 hex (space)). The first byte at the address (HERE) is a character count, followed by the actual characters, followed by a space character. No use in immediate mode because as overwritten by next command.
NUMBER - (addr) NUMBER - where (addr) is the address of a numeric string. If the first byte is a character count this will be ignored. The string delimiter will be any non-numeric character.
COUNT - (addr) COUNT - taking a string at address (addr) which starts with a character count it leaves the count on the stack with the address of the string itself (addr+1) below that.
LOAD - (addr) LOAD - reads text from the RAM address given into the line input buffer as if it had been typed. The delimiter for the edit buffer text is the byte FF hex. v15 up. (discontinued)
IOFLAG (1 byte) - bit 7 set means read disk buffer, lower 4 bits are device no. for prints and EMIT.
? - immediate examination of a variable, pseudo-variable or any memory address in bank 0.
Addresses and pseudo-variables in high memory must be examined with E@ .
EDBUF - constant, leaves address of edit buffer. (discontinued)
EDLOAD - compiles edit buffer contents - as EDBUF LOAD (discontinued)
INTERPRET - acts on next word in input stream (line buffer).
INKEY - tests the terminal to see if a key has been pressed. If so leaves the ASCII value; if not leaves zero on TOS. Does not wait for key to be pressed.
(n) LINES - line feeds n times
?TERMINAL - test the terminal to see if escape has been pressed. If so leaves true (1) else leaves zero on TOS.
CTRL-C - test the terminal to see if control-C has been pressed. If so leaves true (1) else leaves zero on TOS.
control-C is ETX (end of text) code 3 (See STX and ETX below)
ASK - gets a signed number from user straight to stack in ruling number system. If number is invalid a zero is returned.
DUMP - (addr) DUMP - dumps memory contents of low memory (bank 0) starting at (addr), 16 bytes per line advanced by space bar. Return key to stop dump.
EDUMP - (addr) EDUMP - dumps memory contents of hi memory (bank 1) starting at (addr), 16 bytes per line advanced by space bar. Return key to stop dump.
. ("dot") - (n) . - prints (n) from the stack according to ruling number base preceded by sign or space and followed by one space. Use of .(dot) resets BANK to zero.
SGN - flag used by <# and SIGN, used for "dot".
SPACE - prints one space character.
SPACES - (n) SPACES - prints (n) spaces.

The following words are for formatted print. They are the same as FORTH '79 but work with single length numbers not double length.
<# - prepares PAD for number conversion, used in . (dot).
HOLD - inserts character into PAD, during . (dot).
# - converts one digit from TOS to PAD.
#S - converts all TOS to digits in PAD, destroys TOS.
SIGN - inserts sign into PAD during . (dot).
#> - finishes number conversion and leaves the number of characters on TOS and the address of them at TOS-1.
#. - prints TOS in an 8 character field including a space and a negative sign if negative
(n) HEXDIGIT - prints (n) as a hexadecimal digit, 16 > (n) > 0
VLIST - lists entire (selected) vocabulary in the format: address of dictionary entry ( 6 bytes less than CFA ), character count, word spelling up to 5 characters, excess (unknown) characters as dots. When VLIST is used the first time, i.e. with un-initialised memory, it may only yield "0 words". Simply repeat the command.
'VLIST (word) - (pronounced tick-vee-list) lists all words in the dictionary of a particular type, follow with an example of the type of word. For example if SPEED is a variable then 'VLIST SPEED will list all variables.

Back to Contents


note TOS means Top Of Stack. TOS-1 means next on stack, also called NOS.

ASPACE - pushes a space character to stack - i.e. a constant of value 20 hex.
0 - A constant of value 0
1 - A constant of value 1
STX - A constant of value 2
ETX - A constant of value 3
ENQ - A constant of value 5
! ("store") - stores TOS-1 into address on TOS. Both removed from stack.
@ ("fetch") - gets data from address on TOS and replaces TOS.
+! - adds TOS-1 to location given at TOS ie. the expression b=b+a would be written a b +!
C! ("see store") - stores 1 byte of TOS-1 at TOS address. Both removed from stack.
C@ ("see fetch") - gets 1 byte from address at TOS and replaces TOS with it.
E! ("E-store") - stores TOS-1 into address in high memory on TOS. Both removed from stack.
E@ ("E-fetch") - gets data from address in hi memory on TOS and replaces TOS.
EC! ("E-C store") - stores 1 byte of TOS-1 at TOS address in high memory. Both removed from stack.
EC@ ("E-C fetch") - gets 1 byte from address at TOS and replaces TOS with it.
X! ("X-store") - stores TOS-1 into address on TOS in low or high memory depending on the value in BANK. Both removed from stack.
X@ ("X-fetch") - gets data from address in low or high memory depending on the value in BANK on TOS and replaces TOS.
X+! ("X-plus-store") - adds TOS-1 into address on TOS in low or high memory depending on the value in BANK. Both removed from stack.
2! ("two-store") - stores TOS-2 into address on TOS and TOS-1 into the next address.
2@ ("two-fetch") - fetches data from address on TOS and next address leaving data from the address on TOS-1 and data from address+2 on TOS.
DUP ("doop") - a DUP --> a a.
DROP - removes top of stack.
SWAP - a b SWAP --> b a
OVER - a b OVER --> a b a
ROT - a b c ROT --> b c a
PICK - (n) PICK - picks the nth item from the stack and places a copy on top of stack, e.g. a b c d 2 PICK leaves a b c d c.
C0SET - changes byte at location given at TOS to zero.
C1SET - changes byte at location given at TOS to 01.
1+ - increment TOS.
1- - decrement TOS.
2+ - increment TOS twice (adds 2 to TOS).
2- - subtract 2 from TOS.
2* - multiply TOS by 2, unsigned (shift left).
2/ - divide TOS by 2, unsigned (shift right).
R> - move top of return stack to top of data stack.
>R - move top of data stack to top of return stack.
R - copies top of return stack to top of data stack.
= syntax: a b = leaves 1 if a=b or 0 if not (1=true).
> syntax: a b > leaves 1 if a greater than b
< syntax: a b < leaves 1 if a less than b
<> ("not equal") syntax: a b <> leaves 0 if equal, 1 if not equal.
0= - removes TOS and leaves true if TOS was zero
OR - 16 bit inclusive OR.
XOR - 16 bit exclusive OR.
AND - 16 bit and.
INC - increments contents of address on stack.
CMOVE - moves data block from one memory area to another, syntax: (source) (destination) (number of bytes) CMOVE.
ECMOVE - moves data block from one memory area to another both within high memory (bank 1), syntax: (source) (destination) (number of bytes) ECMOVE.
The destination and source data must not overlap.
MOVUP - moves data block from low memory to high memory, syntax: (source in bank 0) (destination in bank 1) (number of bytes) MOVUP.
MOVDN - moves data block from high memory area to low memory, syntax: (source in bank 1) (destination in bank 0) (number of bytes) MOVDN.
FILL - (n)(a)(b) FILL - fills memory from (a) to (b) (inclusive) with value (n)
Back to Contents


+ - adds TOS to TOS-1, replaces both with answer.
- - subtracts TOS from TOS-1, replaces both with answer.
* - multiplies TOS * TOS-1, replaces both with answer.
U* - as above but with unsigned 16 bit integers.
ABS - changes TOS if negative to positive.
/MOD - TOS-1 divided by TOS: TOS is answer, TOS-1 is remainder.
U/MOD - as above but with unsigned integers.
M* - as * but leaving 32 bit answer; TOS= high 16 TOS-1= low.
D+ - adds 2 32-bit values leaving 32-bit answer.
D- - subtracts 32-bit value from 32-bit value, answer 32 bits.
D< - compares 2 32 bit values, leaves true if TOS-3,TOS-2 less than TOS-1,TOS.
D= - compares 2 32 bit values (4 stack entries) and leaves true if equal else false (1 stack entry).
/ - TOS-1 divided by TOS, replace both with answer.
U/ - as above but with unsigned integers.
M/ - divides a 32 bit value (TOS-1 & TOS-2) by 16 bit value (TOS) leaving a 16 bit value.
MSQ - squares a 16 bit value leaving 32 bit answer.
MSQR - takes square root of 32 bit value leaving 16 bit answer.
SIN - converts angle in degrees to 2 decimal places to sine fraction to 4 decimal places.
COS - as SIN but cosine.
ASIN - takes arcsine of fraction to 4 decimal places to angle in degrees to 2 decimal places.
ACOS - as ASIN but arc-cos.
(b) BIT - leaves numeric value of bit number (b) i.e. 2^b

Back to Contents


: ("colon") - this is the main defining word for defining a new word. Must be followed by the new word. Puts system into compile mode.
; ("semi colon") - end of definition (immediate word - means will act immediately when system is in compile mode).
CONSTANT - syntax: (value) CONSTANT (name).
VARIABLE - syntax: VARIABLE (name) reserves 2 bytes in the dictionary for a variable.
USER - syntax USER (name) - like VARIABLE but creates a new user variable in the RAM area, incrementing UVP by 2. When invoked the address of the variable is pushed to the stack. The advantage of a USER variable over the normal VARIABLE is that after editing and re-compiling the dictionary the value of a USER variable will not have changed. When a USER variable is used it resets BANK to zero. To use the variable enter (value) (name) ! and (name) @ etc.
USARRAY - syntax (n) USARRAY (name) - is an array in the user variable area of (n) elements (n * 2 bytes). To use the array enter (value) (element-number) (name) ! and (element-number) (name) @ etc.
IMMEDIATE - makes a new word just defined operate immediately and only when in compile mode, ie. when inside a : --- ; construct.
FORGET (word) - removes word and all subsequent words from dictionary. Resets the DP (dictionary pointer) to the position previously occupied by the word.
If the word is a user variable then UVP is set back to the address previously occupied by the variable, recovering the user variable space.
(RoboForth only) If the word is a PLACE or ROUTE then NEXT is set back to the address previously occupied by the place or route, recovering the data space.
, ("comma") - incorporates the 2-byte value on the stack into dictionary. Advances the DP by 2.
C, ("see comma") - incorporates the low byte from the stack into the dictionary. Advances the DP by 1.
LITERAL - incorporates that value which is on the stack into the word being compiled as if it were a constant.
ALLOT - (n) ALLOT - change no. bytes allotted to a variable, where (n) is added to the two bytes already reserved for the variable. syntax: VARIABLE (name) (no. extra bytes) ALLOT
[ ("bracket") - switch to immediate mode
] - switch back to compile mode. When in compile mode these allow insertion of words which are executed immediately and not compiled.
['] ("bracket-tick-bracket")- like ' but for use in a definition. It compiles the PFA of following word as a literal.
[COMPILE] - compiles the following word even if it is an immediate word.

CREATE (word) - creates an INCOMPLETE dictionary entry for the new word. Adds a new 8-byte header to the dictionary plus the first 2 bytes of the parameter field. DP is advanced by 10. When (word) is invoked the PFA address is pushed to stack.
DOES> - within the definition of a new defining word DOES> marks the start of the run-time activity of the words which will be defined using the new defining word.
(starts with colon)  :  (defining-word name)  CREATE  (activity when defining-word is used)  DOES>  (activity when final defined word is used)  ;  (ends with semi-colon)
When the defining word is used the CREATE part of it adds the defined word to the dictionary. When the final created word is used its PFA goes on the stack and the words after DOES> should make use of this value or DROP it.

CODE - generates header for machine code. Follow with the name of the code then the machine code installed by C, or , then finish with the code for PCIY.
For example a word
REVERSE (definition : REVERSE MEP C@ MDP C! ;)
could be coded LDA MEP STA MDP PCIY e.g. in machine code:-
( Or you can use the word PCIY instead of E9FD )

Back to Contents


WARNING: All control loops are implemented using conditional short jump machine instructions. This means there is a maximum number of words between the beginning and end of a loop or decision tree of approximately 63 words. If exceeded the system will crash.

a (condition) is true if it is non zero (any value, not just 1), false if zero.
control words can not be used in immediate mode, only compiled into definitions.


Form 1 syntax:
(condition) IF
(words executed if true)
for example

Form 2 syntax:
(condition) IF
(words executed if true)
(words executed if false)
for example


Repeating loops

Form 1 syntax:
(function - repeats every time round the loop)
(condition) UNTIL ( leaves the loop when condition is true
for example
  PRESSURE 1000 >
Form 2 syntax:
(action, unconditional once only) (condition) WHILE
(function every time round the loop while condition is true)
REPEAT (repeat so long as the condition is true.
drops through as soon as condition is false. for example

Counting loops

Form 1 syntax:
(upper limit) (lower limit) DO
(words - executed for upper minus lower number of times)
The loop ends when the index reaches the upper limit so the words are never executed with the index equal to the upper limit.
for example
: EX1
10 0 DO
EX1 10 OK

Form 2 syntax:
(upper limit) (lower limit) DO
(step) +LOOP
This counts from (lower) to (upper) in increments of (step) and finishes when the index equals or exceeds the upper limit. Then this value of index is NOT executed within the loop.
for example

: EX2
10 0 DO
EX2 5 OK

In the case
5 0 DO
The loop exits when the index reaches 6 which is greater than the upper limit. blah is executed only for indexes 0, 2 and 4 and not for 6.
In the case
6 0 DO
The loop exits when the index reaches 6 which is equal to the upper limit. blah is executed only for indexes 0, 2 and 4 and not for 6.
In the case
7 0 DO
The loop exits when the index reaches 8 which is greater than the upper limit. blah is executed for indexes 0, 2, 4 and 6.

indexes of counting loops

I - index of inner do loop is moved to stack.
J - index of next (second) loop.
: EX3
10 0 DO
  I .
EX3 0 1 2 3 4 5 6 7 8 9 OK

: EX4
5 0 DO
  I .
EX4 0 2 4 OK

: EX5
4 1 DO
  3 0 DO
    J . I .
1 0 1 1 1 2
2 0 2 1 2 2
3 0 3 1 3 2
counting backwards - example
: EX6
0 10 DO
  I .
-1 +LOOP
EX6 10 9 8 7 6 5 4 3 2 1 0 OK

: EX7
0 10 DO
  I .
-2 +LOOP
EX7 10 8 6 4 2 0 OK

LEAVE - syntax:
(upper limit) (lower limit) DO
(condition for leaving) IF LEAVE THEN
(maybe more words)

On executing LEAVE the loop terminates when, and not until, LOOP is next executed. This means that any more words after THEN will be executed before the loop is left.

: EX8
100 0 DO
  100 MSECS
This word will run for 10 seconds (100 * 100mS) but if the temperature reaches 500 (e.g. 50.0 deg C) befofre the 10 secs are up then there is one more 100mS delay before the heater is turned off.

EXIT - leaves the entire word if executed- i.e. effectively jumps to the semi-colon.
syntax: (condition) IF EXIT THEN.
Not to be used within a DO - LOOP.

WARNING: All control loops are implemented using conditional short jump machine instructions. This means there is a maximum distance between IF and THEN or BEGIN and UNTIL etc. of 127 bytes (approximately 63 words). If exceeded the system will crash.


Simple delays can be introduced into any word with (n) USECS e.g.
500 USECS (500 microseconds)
MSECS is a ROBOFORTH word and without ROBOFORTH you can make it with
DECIMAL : MSECS 1000 0 DO 1000 USECS LOOP ; then for e.g. a 5 second delay enter 5000 MSECS

Back to Contents


Note: these words exist in K11 but will not function unless the RAMDISK solid state disk system is installed. This system is based on an obsolete but highly efficient North Star DOS and is designed for rapid transfer of data to and from SD card to main memory, for example overlaying matrix coordinates without delaying robot activity as would be the case if data were transferred from PC.

DLOAD (filename) - loads file of FORTH text to edit buffer then reads into line buffer as if typed. The filename must be the last word in the command line. Extra words are ignored. Each file may DLOAD another file (last line).
READ disk to memory. (memory addr) (disk addr) (no. of blocks) (drive no.) READ
WRITE memory to disk. (memory addr) (disk addr) (no. of blocks) (drive no.) WRITE
DLIST (disabled) - directory of RAMDISK.
DLOOK (disabled) (address of string which is the filename, ending in return (0D) or space (20) ) - DLOOK --> leaves address of location in DOS of the directory entry + 8 i.e. to 2 bytes which contain the disk address. The next 2 bytes are the file length.
DOS (disabled) - enter DOS command area.

Back to Contents



CPU card: carries eZ80L92 processor, RAM memory, flash/rom memory and basic I/O. It carries the PB inputs, the PA buffered outputs and interfaces with the teach pad. It also carries main RS232 channel for the terminal and one spare RS232.
This card is part of basic K11 system.

DSP card: carries the DSP which controls the motor drives and also reads back from the encoders.
This card is part of basic K11 system.

MULTI-I/O card: Provides 48 lines of I/O programmable as input or output, a 4-channel analog-to-digital converter and a 2-channel digital-analog converter.

8-LINE BUFFER CARD: has 8 opto-isolated inputs or 8 opto-isolated outputs.

16-line opto-isolated I/O card providing 8 opto-isolated inputs and 8 opto-isolated and buffered outputs.

Back to Contents


The cards conform to the ST bus which is roughly equivalent to the Z80 pin-out except that it serves I/O only. EZ80L92 extended address and data lines, clock and other signals are not brought out on to the bus.
All signals which are low true are prefixed with '-' e.g. -WR meaning not-write.

           (a)                            (c)
 1   +15v                |  1  A0
 2   -15V                |  2  A1
 3   0V DIGITAL          |  3  A2
 4   -WAIT               |  4  A3
 5   -HALT               |  5  A4
 6   -M1                 |  6  A5
 7   -RFRSH              |  7  A6
 8   -WR                 |  8  A7
 9   -RD                 |  9  A8
10   n/c                 | 10  -RESET IN
11   -IORQ               | 11  IOSEL
12   +5V                 | 12  +5V
13   n/c                 | 13  n/c
14   -NMI                | 14  -PF ( -POWERFAIL )
15   OV ANALOG           | 15  OV ANALOG
16   -BUSRQ              | 16  n/c
17   -INT                | 17  n/c
18   -RESET ( OUT )      | 18  n/c
19   -BUSAK              | 19  n/c
20   -INTAK              | 20  n/c
21   n/c                 | 21  n/c
22   RESET ( OUT )       | 22  n/c
23   0V DIGITAL          | 23  0V DIGITAL
24   n/c                 | 24  n/c
25   n/c                 | 25  n/c
26   n/c                 | 26  SERIAL OUT (slot 1 only)
27   n/c                 | 27  SERIAL IN (slot 1 only)
28   n/c                 | 28  n/c
29   D7                  | 29  D6
30   D5                  | 30  D4
31   D3                  | 31  D2
32   D1                  | 32  D0

Pins 26 and 27 c are not 'bussed but are reserved for signals unique to particular cards. The CPU card should be fitted in the lowest slot because of its unique RS232 connections. The remaining cards can occupy the remaining slots in any order.

Back to Contents


I/O cards are all addressed with address lines A0 to A7 only as per original INTEL 8080 convention, plus -WR , -RD , -IORQ from the eZ80L92 CPU. Every card has a board address which is a multiple of 10 hex. The address of any device is NX where N is the board address and X is the address of the device within the card.
ST FORTH has certain words such as ADC which are pre-coded device routines which expect to find certain cards at certain addresses, although the device routines themselves are given below and may be re-coded to different addresses. The normal address for each card is given with the card details below.

0x Reserved
1x DSP
2x Multi-function I/O card primary
3x General purpose opto-isolated cards
9x Reserved for PA, PB and PC I/O addresses
Ax Reserved for PD I/O address

Back to Contents


There are 4 ports which are called PA, PB, PC and PD whose addresses are 96, 9A, 9E, A2.


All standard (unexpanded) outputs are controlled by PA. These are open collector Darlington drivers with a common rail of zero volts. There is a nominal 12 volt supply on the same connector, pins 11-15. This an unregulated supply which is nominaly 12 volts but could be as much as 15v, protected by a fuse in the rear panel. The 5v supply to the internal logic is derived from this 12v so if you blow the fuse the entire controller will stop.
Each output has a flywheel diode to the 12 volts line. Therefore if you use an external power supply you must not use more than 12 volts. Connect the ground of the external supply to the 0v line on pins 9 or 10.
The supply may optionally be 24 volts if ordered at time of purchase. It is changed by moving a soldered wire from the 12v fuse holder to the 24v fuse holder inside the controller.

An output bit may be controlled by the words ON and OFF e.g. PA 0 ON will energise the gripper.
The robot gripper is controlled by bit 0, all other outputs are available to the user.

To turn any output bit on i.e. to a logic '1', say bit 1 of port PA, the syntax is e.g.:-
which sets PA 1 to '1' but leaves all other bits unchanged.
PA 1 OFF OK turns it off again.
The electric gripper uses PA 0 and PA 1 (see Roboforth manual).

Suppose this were a pump, you could define PUMP:-
: PUMP PA 1 ; (which is the same as : PUMP 96 1 ;) thereafter use PUMP ON and PUMP OFF.

How to use open collector outputs:

Using open collector outputs with an external supply:

IMPORTANT: When using an external power supply and loads are inductive (e.g. solenoids) then flywheel diode must be fitted.


All inputs are through port PB. The first 3 to 6 (least significant) bits are reserved for the proximity detectors on the robot for calibration - bit 0 for motor 1, bit 1 motor 2 etc. Any remaining inputs are available to the user. Gripper confirmation is usually connected to PB 7.
All the inputs are logic with 1K pullups to the controller's 12 volt line. So no input must exceed 12 volts. There is no opto-isolation so the user must provide noise free signals, although all inputs are filtered against high frequencies.

Inputs may be read back with PB IN e.g.
An input bit may be interrogated with the word BIT? e.g. PB 0 BIT? leaves true if the input is at a '1'. This may be used in decision constructs e.g. PB 0 BIT? IF

How to use inputs:

The teach box is connected to PC, whose upper 4 bits are programmed as outputs and PD lower 4 bits programmed as inputs. The teach box is arranged as a matrix between outputs and inputs giving 16 combinations which are decoded by the software. Diodes are fitted in case a user presses two keys together.

Back to Contents


The main port is serial port 0 and the second is serial port 1. The second port is optionally connected to a 9w D connector that connects to the CPU card - obtainable from ST Robotics. The second port is useful for connecting RS232 instruments to the controller so that the instrument can be read during robot motion. It can also be used to accept commands from another RS232 device such as another computer.

Changing baud rate on port 0
The Baud rate always defaults to 19200 on a cold start. But you can change the baud rate temporarily.

The Baud rate factor is in location 9D44 named BAUD. The value of this factor is 2,000,000 divided by the required baud rate. So the default value is 2,000,000 / 19,200 = 104 (round to nearest integer) or 68 hex. So if you type:
HEX BAUD ? you should see 68 To change the baud rate enter a new value into BAUD then call the bit of code that programs the port to the new baud rate then change ROBWIN to the same baud rate.
For example to change to 56,000 (factor 2000/56 = 36 or 24 hex):
24 BAUD !
BA CALL (reprograms port) You will lose communication with the controller. Click Comm, configuration and select 56,000 in the drop-down menu. Communication restores at 56k. If you mis-enter the baud rate and get lost simply press reset on the controller and restore RobWin to 19200. The fastest practical speed is 256,000 baud, using HEX 8 BAUD ! BA CALL
Note that this may only work using the USB converter. The standard serial port may not go that fast.
If you USAVE then switch off the controller, then switch on with the key in warm start position then the higher baud rate remains. Cold start resets the baud rate to 19200.

Second serial port
You will first need to initialize the port using a value calculated as above to set the baud rate. Put the value on the stack then jump to location 001F, for example
will initialize the port to 19200 baud.
To access the second serial port change the value of IOFLAG from 0 to 1 with
From this point on you can only communicate with the controller through the second serial port. Therefore make sure you issue all commands to end with
will send a space character out of serial port 1 then return control to port 0.
will wait for a character into serial port 1 then return control to port 0.
You could define, say : KEY1 IOFLAG C1SET KEY IOFLAG C0SET ;
This word will of course hang until a character arrives. You may wish to check the status of the port before you change to channel 1.
You can do this:

D9 C,             ( EXX
3E C, 0 C,        ( LD A,0
ED C, 38 C, D5 C, ( READ FLAG
F5 C,             ( PUSH FLAG TO STACK
D9 C,             ( EXX
PCIY ,            ( END
This leaves 4 on the stack if there is no character and 0 if a character has arrived at the port.
You could use : K2 K2? 4 AND 0= IF KEY1 ELSE 0 THEN ; or similar in a definition

Note that while KEY works with port 1, INKEY does not. INKEY still only returns the ascii value at port 0.

If you simply enter IOFLAG C1SET then control will simply switch to port 1. You can then send or type commands into port 1 as you did with port 0. To return to port 0 enter IOFLAG C0SET into port 1.
BUG: for EPROMS version 10 (VA) and below the > character still appears on port 0 even though OK is on port 1. To correct this (if you wish) then perform the following patch:
3A 1FE2 C! 06 1FE3 C! A0 1FE4 C! C3 1FE5 C! C7 1FE6 C! 05 1FE7 C!
This should be typed all on one line at one time. Hit enter at the end.

Connections to the second serial port (1) are on the 6-way HE-14 connector on the CPU board. Port 0 is also there. If fitted port 1 is wired to a rear 9-w D male connector.
Port, function HE-14 pin 9w D if fitted
port 0 TX 1
port 0 RX 2
ground (0v) 3
port 1 TX 4 2
port 1 RX 5 3
ground (0v) 6 5
+5v 9


The electric gripper employs a 800mA constant current half bridge drive. This is fitted in the controller.

Wiring colors for electric gripper drive module:
Yellow/orange signal IN
Red Power +12-18v
Black Ground
White/Grey Outputs to motor


The power supply has a built in monitor to detect failing AC power. When AC power is satisfactory the green LED is on and the red LED is off. When AC power falls below a set level the red LED on the front panel lights and the green LED goes out. A reset is applied to the processor. When power is restored the RAM is reloaded from FLASH and any RAM contents prior to the power fail will be lost.

To change the AC voltage setting remove the controller lid and locate a 6-way screw terminal block. The mains power is connected on one side of the block and the other side has all the transformer taps. Refer to the diagram below. Choose as near to your AC voltage as possible.
"Live" and "Neutral" refer to power where one side is at the line voltage and the other side is around earth potential. For US 110v supplies neither side is neutral but each is 55v AC around earth potential. For this reason there are 2 fuses fitted in the IEC power connector at the rear of the controller.

How to increase the speed of the robot

The top speed of the robot is limited by motor back-emf which in turn can only be overcome by high voltage. The HT is normally set to approximately 55v DC and the maximum voltage on the drivers is 80v. However you can not just increase the voltage to 80v because the chopping magnetic activity in the motor gets it hot. For a small increase in top speed you can increase the voltage by 10% as follows: remove the lid and locate the rectifier between the HT capacitor and the transformer. Normally this will have a yellow and orange wire from the transformer with push-on connectors. Simply remove the orange wire and replace it with the red wire.
Replacing the yellow wire with the blue wire raises the HT to 80v but this can only be used with R15 systems.

11.14 General purpose opto-isolated I/O expansion

11-56 8 in 8 out opto-coupled IO board (AKA IO1)

The inputs are separately opto-coupled and should work with voltages from 5V to 24V.
The inputs are on a 25 way socket which connects to a 16 way 2 row HE14 connector J4 as in the table.
The outputs are in 2 separate groups of 4.
They have 1.5A Darlington drivers which pull down to the common ground for each group.
The positive supplies must also be brought to the connectors.
The outputs are on two 8 way 2 row HE14 connectors J2 and J3 as follows.
25w D skt Function 8W J2/J3
1 output 7 J3-1
2 output 6 J3-3
3 output 5 J3-5
4 output 4 J3-7
5 output 3 J2-1
6 output 2 J2-3
7 output 1 J2-5
8 output 0 J2-7
14 positive supply for outputs 4,5,6,7 J3-2
15 common ground for outputs 4,5,6,7 J3-4
16 common ground for outputs 4,5,6,7 J3-6
17 common ground for outputs 4,5,6,7 J3-8
18 positive supply for outputs 0,1,2,3 J2-2
19 common ground for outputs 0,1,2,3 J2-4
20 common ground for outputs 0,1,2,3 J2-6
21 common ground for outputs 0,1,2,3 J2-8
25w D plug Function 16w J4
1 input 7 neg 1
2 input 6 neg 3
3 input 5 neg 5
4 input 4 neg 7
5 input 3 neg 9
6 input 2 neg 11
7 input 1 neg 13
8 input 0 neg 15
14 input 7 pos 2
15 input 6 pos 4
16 input 5 pos 6
17 input 4 pos 8
18 input 3 pos 10
19 input 2 pos 12
20 input 1 pos 14
21 input 0 pos 16

How to connect an input:

Simply apply a voltage to neg and pos to read an input as a '1'

How to connect an output:

Connect your external power supply pos and ground to the pin marked "pos supply" and the ground (negative) of your power supply to the pin marked "common ground".
The outputs are in two groups of 4 so can use two different supplies or the same supply.
Connect your load between the output pin and your power supply positive.

Board I/O address

The board uses 2 addresses in io space: base and base+1.
The output data can be read or written at the base address.
The input data can be read at base+1.

The link LK1 selects from 2 base addresses. The default is
Link fitted 30hex. So you can enter e.g. HEX 30 0 ON or 31 IN
The two addresses are named SA and SB
Then you can type e.g. SA 1 ON or SB IN
In some versions you may find that SA and SB do not exist so you can create them with:
Link not fitted 32hex. The two addresses are named TA and TB
So for example you could type TA 1 ON or TB IN

11.15 MULTI-FUNCTION I/O 11-48 (AKA IO3)


Analog input: 4 channels –10V to +10V.
Analog output: 2 channels –10V to +10V.
Digital I/O: 48 lines programmable.


The IDC connectors on the board are brought out to chassis-mounted 25 way D plugs.


The board uses a block of 16 addresses in i/o space. The default base address is 32. If more than one board is used in a system each has a different base address (programmed into the PLD on the board).

Analog Input

A Burr-Brown (now Texas Instruments) ADS7824 4-channel 12-bit A/D converter is used. Additional buffer amplifiers protect the inputs. The range is –10V to +10V. On the board the 10-way IDC connector J2 is used for inputs also the rear panel connector AN (25w D socket) as shown in the table:

AN pin (25w D socket)
J2 pin
In 0
In 1
In 2
In 3

Refer to the
ads7824 data sheet (pdf) for a detailed description of operation. The convertor uses a block of 4 addresses at offset 4 from the board base address. The functions are shown in the table:

Address offset
Write function
Read function
Write any data to select ADC channel 0 Start Convert and latch address for next conversion
Write any data to select ADC channel 1

Write any data to select ADC channel 2
Read most significant byte
Write any data to select ADC channel 3
Read Least significant 4 bits on D4 to D7, 0 on D0 to D3

5 microseconds must be allowed for acquisition and 20 microseconds for conversion.
Valid data (from the previous conversion) can be read up to 12 microseconds after 'start convert' and then the new data after 20 microseconds.
The ROBOFORTH program below reads data from the specified channel and is fast enough for most applications. When a sequence of data values is to be read as quickly as possible the following procedure is suggested:

Initialise: Set a timer for a 25-microsecond interval and start it.

Then repeat the following:
1 Wait for the timer and restart it.
2 Select the channel for the conversion after next.
3 Start convert .
4 Read the data from the previous conversion.

Note that the operation is pipelined: When a channel is selected its data will be read two steps later. Thus the first two readings in the above sequence will be undefined.

One of the timers on the controller's ez80 may be used to time conversions. (see the ez80L92 data sheet)
This may be done from ROBOFORTH e.g.
25 USECS (25 microseconds)

Analog Output

An Analog Devices AD7237 2-channel 12-bit D/A converter is used. The outputs are amplified to a range of –10V to +10V. The outputs are brought out on a 10-way IDC connector J3 and the rear panel connector AN (25wD socket) as shown in the table:

AN pin (25wD socket)
J3 pin
Output B
Output A

Refer to the AD7237 data sheet (pdf) for a detailed description of operation. The convertor uses a block of 4 addresses at the board base as shown in the table:

Address offset
Write function
Read function
Write DAC A input latch least significant byte Load DACs A & B from respective input latches
Write DAC A input latch most significant 4 bits on D0 to D3
Write DAC B input latch least significant byte
Write DAC B input latch most significant 4 bits on D0 to D3

Note that it is necessary to load the data to the input latches and then transfer the data to the converters by reading at offset 0.

ROBOFORTH CODE The base board address is usually 20hex. This is defined in ROBOFORTH as a constant IOBASE

: ADC ( read ADC onto stack
 ADBASE 2 + IN 128 XOR 16 * ADBASE 3 + IN 16 / + ;
: DACA ( output stack to DAC channel A
: DACB ( output stack to DAC channel B
NOTE: ALL THESE WORDS ARE ALREADY PART OF ROBOFORTH - the definition is shown here for information only.

n ADC ( leaves value from ADC channel n on the stach
v DACA ( outputs v to DAC channel A
v DACB ( outputs v to DAC channel B

All inputs and outputs are offset by 2048 (800 hex)
So 0 DACA will ooutput minus 10 volts on channel A
2048 DACA will output zero volts on channel A
4095 DACA (FFF hex) will output plus 10 volts on channel A
Likewise the inputs are offset by 2048 so if zero is input on channel 0
0 ADC . will print 2048
plus 10 volts in will result in 4095 and minus 10 volts will result in zero.
Simply add/subtract 2048 (800 hex) from all calculations.

Digital IO

One or two (see note) 82C55 Programmable peripheral interfaces are used. Refer to the 82C55 data sheet for a detailed description of operation.
Note that PA PB etc in the data sheet is names QA QB etc in RoboForth. The devices are referred to as Q and R and their ports QA,QB,QC and RA,RB,RC. Q is addressed at (base+8), R is addressed at (base+12 decimal)(base+0C hex)
so the address of RA is base+8, RB base+9, RC base+10 and the R control port is at base+11 (base+0B hex).
Connections are brought out on three 20-way connectors: J4, J5 and J6. The pinout enables simple connections to be made to opto-coupled i/o boards 11-36 and 11-37. The onnections may also be brought out to 25w D male connectors (refered to as QQ, QR & RR).

NOTE: Since 2010 due to speed problems only 1 82C55 device is fitted, total 24 bits. Therefore only the Q ports are fitted and the R ports are not fitted. Your card may have both devices fitted but the card may freeze and ST makes no guarantees. If you have problems remove the second 82C55 device from its socket.

The following table shows the pin connections for the board connectors and rear panel connectors:

J4, J5, J6 pin
(on the card)
QQ, QR, RR pin
(25 w D)
J4 & QQ function
J5 & QR function
J6 & RR function
+5V +5V
+5V +5V

Roboforth Software is same as for basic I/O, i.e. (value) QA OUT, QB IN (value), QA (bit) ON or OFF, QB (bit) BIT? (leaves true/false), QB 0 1 WAIT - waits for QB bit 0 to go to a 1 etc.
PROGPIA (Program Peripheral Interface Adaptor) writes the value 83 hex into each control port and programs the I/O ports as follows:
QA out QB in QC lower 4 bits out, upper 4 bits in
RA out RB in RC lower 4 bits out, upper 4 bits in
You can redefine PROGPIA (add a new definition which will be higher in the dictionary than the original PROGPIA) for different input/output combinations. The built-in definition of PROGPIA is:
If you wanted, for example to change QA to input and QB to output you could add a new definition thus:

Don't forget that any numbers in definitions in your text file following this will be treated as HEX numbers so if they are to be decimal numbers follow with

(port) WATCH (e.g. QB WATCH) will display 8 bits from the specified port as 1s and 0s (see PP in Roboforth manual)

Back to Contents


This unit comprises a box containing opto-coupled input 11-36 and output 11-37 modules which should sit on or near the robot controller. It requires the multi-I/O board 11-48 (IO3)
Each input module has 8 independently isolated channels. Each output module has 8 output channels arranged in two independent groups of four. A total of 23 channels are available. 3 or 4 boards can be fitted to give any compination of inputs and outputs in multiples of 4 as follows
IP Modules O/P modules Inputs Outputs
3 0 24 0
3 1 20 4
2 1 16 8
2 2 12 12
1 2 8 16
1 3 4 20
0 3 0 24
The unit is connected to the controller by a screened cable to a 25 way connector on the rear panel of the controller.

Opto-coupled input module 11-36

This module has 8 independent input channels. These are accessed by a 16-way connector marked J3 and labeled in pairs + and - numbered 0 to 7. A LED indicates the state of each input. If no current flows in the input the controller reads a 1 sate and the LED is extinguished. A current of at least 5mA is required to turn the input on. The board has 2K2 resistors fitted suitable for use on 12V to 30V supplies. For 5V use 330R should be fitted.

The diagrams show how to use the module to interface to a NPN or PNP proximity sensor or similar device or to a switch.

Opto-coupled output module 11-37

The output module has 8 NPN Darlington outputs arranged in two independent groups of four. Thus devices connected to two different supplies may be driven. There are two 6-way connectors marked J3 and J4 with connections for the four outputs each, marked 0 to 3 on J4 and 4 to 7 on J3 together with supply connections 0V and +V. It is important that both the ground and supply voltage are connected to each connector so that the catching diodes in the output drivers can prevent possible damage if driving an inductive load. The board has input pull-down resistors so that if its input is not connected the outputs will be switched off. It is normally driven by an 8255 PIA on the 11-48 card in the controller. When the controller is switched on the PIA is reset to input mode so in this case also the outputs will be turned off. Maximum ratings: Current 1.5 Amps per channel Voltage 35 Volts The diagram shows how a lamp load can be connected.

Back to Contents

11.17 E-stop circuit

On the rear is a jack plug and socket. The controller is shipped with the jack already in the socket, see below.

The jack is supplied with the two terminals shorted. You can instead wire this to any number of external normally closed safety devices. The circuit must be closed for the robot to run. If any device breaks the circuit the robot will stop and the software executes the contents of STOPVEC. This is the same as pressing the stop button on the front panel or teach pad. Normally there is an error message. See ROBOFORTH manual section 6.1 for software details.
The jack must not be removed even if you have no external circuit, it is the same as breaking the circuit so the shorted jack must be left in.


Front Panel

Connections from computer to controller are via an RS232 'null modem' cable. The controller has a 25w connector and the computer end is a 9 way connector. If you are using a USB converter it will have a 9 way connector.

Serial (RS232) port interface pinout and signals
pin #
Acronym Full name Direction Mean
Transmit Data
Transmits bytes out of PC
Receive Data
Receives bytes into PC
Request To Send
RTS/CTS flow control
Clear To Send
RTS/CTS flow control
Data Set Ready
I'm ready to communicate
Data Terminal Ready
I'm ready to communicate
Data Carrier Detect
Modem connected to another
Ring Indicator
Telephone line ringing
Signal Ground    
Note that Ring Indicator has no modern purpose and is used for 5v supply.

Teach Pad connections
1 PD 4 6 PC 6
2 PD 5 7 PC 5
3 PD 6 8 PC 4
4 PD 7 9 screen (0v)
5 PC 7
PD are inputs, PC are outputs. STOP button connects to pins 4 and 5

Rear Panel
Robot Motor Drives (Bayonet) Sensor (datum) inputs (J6,25way)
A motor 1 coil 1 1 Sensor 1 (PB 0)
B motor 1 coil 1 2 Sensor 2 (PB 1)
C motor 1 coil 2 3 Sensor 3 (PB 2)
D motor 1 coil 2 4 Sensor 4 (PB 3)
E motor 2 coil 1 5 Sensor 5 (PB 4)
F motor 2 coil 1 6 encoder 1 up
G motor 2 coil 2 7 encoder 1 down
H motor 2 coil 2 8 encoder 2 up
J motor 3 coil 1 9 encoder 2 down
K motor 3 coil 1 10 encoder 3 up
L motor 3 coil 2 11 encoder 3 down
M motor 3 coil 2 12 encoder 4 up
chassis 13 encoder 4 down
N motor 4 coil 1 14 encoder 5 up
P motor 4 coil 1 15 encoder 5 down
R motor 4 coil 2 16 +24-30v DC
S motor 4 coil 2 17 digital 0volts (sensors)
T motor 5 coil 1 18 15-20v for sensors
U motor 5 coil 1 19 dig. 0v (encoders)
ground to robot
V motor 5 coil 2 20 +5v for encoders
W motor 5 coil 2 21 Sensor 6 (PB 5)
X motor 6 coil 1 22 elec gripper
Y motor 6 coil 1 23 encoder 6 up
Z motor 6 coil 2 24 encoder 6 down
a motor 6 coil 2 25 elec gripper
b high power elec gripper
c high power elec gripper
User outputs - 15w D User inputs - 9w D
1 PA 7 1 PB 6
2 PA 6 2 PB 5 see note 2
3 PA 5 3 Ovolts
4 PA 4 4 PB 3 see note 1
5 PA 3 5 +12V
6 PA 2 6 PB 7
7 PA 1 (elec grip) 7 0 volts
8 PA 0 (gripper) 8 PB 4 see note 1
9 0 volts 9 +12 volts
10 0 volts
11 +12v
12 +12v
13 +12v
14 +12v
15 +12v
note 1 These inputs are shared with robot sensors.
They can not be used with R12.
note 2 This input is shared with robot 6th axis
sensors. It can not be used with R12.

It is possible to share these inputs with an R17
providing the axis does not reach a sensor while an
input state is important. R17 sensors pull down.
Also make sure you do not hold down an input
shared by a sensor while the robot calibrates.

PB 5 may not be used at all with a 6th axis.
PA 0 and 1 not available if electric motor gripper is fitted.
Electric gripper may connect via the motor connector or sensor connector.

©1989-2016 David N Sands