Re: Operator Interface

[Jon Elson <jmelson-at-artsci.wustl.edu>]

Ray Henry wrote:

> 1.      The first is some kind of virtual interface that uses a touch screen and
> a set of windows that have hotspots for the control of all the functions
> essential to each kind of machine task.  This would be a lot like xemc but
> would have separate, larger button screens for each of the major operator
> functions.  Perhaps manual, mdi, auto, tool data, program entry and
> editing, and diagnostic screens.

These touch screens are available off the shelf.  There have been several
kinds, some give a character string that specifies the point touched, there
are also some that emulate (to the software) a user moving a mouse and
clicking the buttons.

>         I have done a little bit of experimentation with input through the
> keyboard port using a basic stamp2 chip.  The advantage of the embedded
> processor is that I can ask it to send any sequence of keyboard codes.
> Something like this would allow us to get at the entire set of keystrokes,
> even the graphic set, using single pushbuttons.  I've got a rough
> incremental handwheel wired all over a table here.  It uses a 100ppr
> quadrature encoder, momentary switches to activate it, select axis, and
> toggle increments.  The stamp looks at pulse and direction and sends a + or
> - keystroke for each cycle as well as the multiple codes required for
> activation.

I was pretty serious about doing something like this, before xemc was
written.  xemc is good enough that I don't have as strong a desire to change.
Still, I've made manual errors using the keyboard, and even mashed my
hand once, when I hit the wrong button and brought the quill down on
my hand instead of raising it.  No permanent damage, but I had two sore
fingers for a few days.  I would like jog dials and a joystick for jogging.
What you are working on sounds real interesting.

>
> I'm wondering what you presently do for operator interface and how you feel
> about each of these operator interface possibilities.  Or others that
> you've thought of.

The permanent buttons  sound quite desirable.  It could be expensive to
build, but if well thought out, it could reduce errors.  I got a $20 keyboard
protector for my keyboard.  After it is covered with chips, I just pick
it up and shake it upside down, and the chips fall off.

Jon