re:indexerLPT

Jon,

Good additional info.

The structure of the indexerLPT commands (and the program)
make 'adding' B/L comp equivalent to Mission: Impossible III . So
maybe it CAN be done, but IMO it will be a kludgy useless workaround,
AT BEST.(those who feel challenged by this, GO FOR IT!)
Your 'subroutine idea will involve "breaking into the 'queue'
(indexers' lookahead buffer) which will 'cost you' constant vector
velocity contouring, at least..

It's hard enough to do GOOD backlash comp when you have FULL access
to the code...

The usual way to send a bit pattern (number) to the p-port in BASIC
is with the 'OUT' command. Usage is: OUT port number,bitpattern
Bitpattern is a number from 0 to 255, whose binary representation
will appear on the p port pins.

BTW, who is mr. batwings?

The indexerLPT limit is six axes, which will take THREE p ports. You
will lose the ability to have a pendant control since this capability
normally 'uses' one of the available ports.

A drilling machine doesn't need? coordinated motion, so you may be
able to do this with luberths' or stepster code as a base. Indexer is
a good product, but it is definitely one of those "good enough"
implementations I've ranted about here before. it would be SO easy to
make it a GREAT product, IMO!

Hope this helps.

Ballendo

>It will also digest a plain text file, I think the command would be
>copy filename.xxx prn, or something like that. It runs on pure simple
>text, and any means of getting text to the printer port work.

>>It does NOT support backlash compensation.

>For all his controversy here, Mr batwings has proven that LPT can
>really dance with some effort.

<s>I see no reason why one couldn't invoke a subroutine at a change

>in axis direction. This would be a bit of a hassle unless the
>program could be made to watch for an axis reversal and
>automatically call the appropriate subroutine.
>In basic, actual motion commands are sent out as PPRINT commands I
>believe, so I really think you could do some pretty powerful stuff
>with it, although it would certainly take some time to develop.
>I've been considering it for an automated drilling machine since I'd
>need to control more than 4 axis.
>Jon