Enhanced Machine Controller

Having just received my industrial monitor and keyboard that 
I considered a score when I got it, I realized that the description 
I originally read was *not* a mistake, and that I really did just 
purchase an LCD display with touchscreen capability.
http://luckyweyland.com/IMAGES/pendant1.jpg
http://luckyweyland.com/IMAGES/pendant2.jpg

And then I seemed to remember that someone had 
written a touchscreen interface to EMC a while back...

Was that a hallucination?

Any idea on where to find it?

Any idea on how to interface to the touchscreen capabilities?
(I think I need a card for that...)

Thanks,

Weyland

On Wednesday 18 June 2003 04:26 pm, Paul spake: 

> Now that the old mailing list is obsolete, I'm uploading the archive to
> Sourceforge where it will hopefully remain long after the NIST server is
> shut down.

I guess I've missed a few meetings.
Can someone tell me what happened with the NIST's server?
If it needs to be offlist, that's fine.

I'm just curious...

Thanks,

Weyland

On 06/18/03, at 08:27 PM, Weyland <weyland@...> said:

>Any idea on how to interface to the touchscreen capabilities?
>(I think I need a card for that...)

I have a Gunze LCD/touchscreen (unfortunately not using EMC yet). The touchscreen interfaces via the 9-pin serial port and works like a serial mouse, no card needed. You may need to track down a driver. The Linux driver for the Gunze is called "gunzets". Step one would be to identify the hardware.

-- 
-----------------------------------------------------------
Carl Brown cbsled@...
------------------------------------------------------
When there's no plan, there's one less thing to go wrong.
    -Joe Redington Sr.
-----

On Thursday 19 June 2003 09:35 am, cbsled@... spake:

> I have a Gunze LCD/touchscreen (unfortunately not using EMC yet). The
> touchscreen interfaces via the 9-pin serial port and works like a seria=
l
> mouse, no card needed. You may need to track down a driver. The Linux
> driver for the Gunze is called "gunzets". Step one would be to identify=
 the
> hardware.

Outstanding~!
Thank you for that bit'o'info.
Yes, this has the 9 pin serial connection as well.
I'll have to check around some, as the monitor "says" Advan,=20
but upon detection by Red Hat, it is described as a Mitsubishi.

Thanks for the pointer~!

Best,

Weyland

I spend a good part of my day job playing around with touchscreens under 
linux.  The majority of the monitor touchscreens are either Microtouch/3m
or Elographics.  Both have fairly good support under linux.  Microtouch
also has a closed sourced linux driver.

The open source drivers are handled by xfree.  Some simple hand editing of the 
XF86Config-4 file will get you going.  A nice feature is that you can run 
both the mouse and the touchscreen simultaneously.

The only tough part is calibration, as there yet are no good open sourced 
programs for this.  Most programs that use a touchscreen perform calibration 
themselfs.  

anyhow, just let me know if you have any trouble setting it up.    


On Thursday 19 June 2003 10:12 am, Weyland wrote:
> On Thursday 19 June 2003 09:35 am, cbsled@... spake:
> > I have a Gunze LCD/touchscreen (unfortunately not using EMC yet). The
> > touchscreen interfaces via the 9-pin serial port and works like a serial
> > mouse, no card needed. You may need to track down a driver. The Linux
> > driver for the Gunze is called "gunzets". Step one would be to identify
> > the hardware.
>
> Outstanding~!
> Thank you for that bit'o'info.
> Yes, this has the 9 pin serial connection as well.
> I'll have to check around some, as the monitor "says" Advan,
> but upon detection by Red Hat, it is described as a Mitsubishi.
>
> Thanks for the pointer~!
>
> Best,
>
> Weyland

On Saturday 21 June 2003 12:35 am, Dean Hedin spake: 

> I spend a good part of my day job playing around with touchscreens under
> linux.  The majority of the monitor touchscreens are either Microtouch/3m
> or Elographics.  Both have fairly good support under linux.  Microtouch
> also has a closed sourced linux driver.

That is good news.
I noted that Red Hat doesn't seem to recognize it 
overtly, but does recognize the Advan monitor as a Mitsubishi.

> The open source drivers are handled by xfree.  Some simple hand editing of
> the XF86Config-4 file will get you going.  A nice feature is that you can
> run both the mouse and the touchscreen simultaneously.

Excellent news.
Not skeered to edit the config... :)

> The only tough part is calibration, as there yet are no good open sourced
> programs for this.  Most programs that use a touchscreen perform
> calibration themselfs.
>
> anyhow, just let me know if you have any trouble setting it up.

Yes, please~!
Feel free to write me directly if anyone 
feels that this is too off topic for this list.
My goal is to indeed use the touchscreen as a mouse in the workshop.

Any tips you can give are appreciated~!

Best,

Weyland

Hi Weyland

I too have a touch screen on a couple of computers - One of them uses a 
Magictouch kit from Keytech. Their closed source driver didn't work so I 
ended up writing my own. For the most part, it isn't very difficult..

XFree86 setup for both 3.3.x and 4.x.x is also straight forward, but there 
are differences in the way a couple of sections are configured (assuming you 
want a mouse and TC screen). Both of these, I'm happy to discuss on list as 
this has an EMC-Usage connection.

Regards, Paul.


On Saturday 21 June 2003 5:33 am, Weyland wrote:
> > I spend a good part of my day job playing around with touchscreens under
> > linux.  The majority of the monitor touchscreens are either Microtouch/3m
> > or Elographics.  Both have fairly good support under linux.  Microtouch
> > also has a closed sourced linux driver.

> > The only tough part is calibration, as there yet are no good open sourced
> > programs for this.  Most programs that use a touchscreen perform
> > calibration themselfs.

> Feel free to write me directly if anyone
> feels that this is too off topic for this list.
> My goal is to indeed use the touchscreen as a mouse in the workshop.

-- 
irc channel for EMC users at irc.freenode.org
/join #emc
and chat to other users (not many there yet).

On Saturday 21 June 2003 12:35 am, Dean Hedin spake:

> I spend a good part of my day job playing around with touchscreens unde=
r
> linux.  The majority of the monitor touchscreens are either Microtouch/=
3m
> or Elographics.  Both have fairly good support under linux.  Microtouch
> also has a closed sourced linux driver.

I'm still not able to find out what this is yet.
Monitor is labeled an Advan, but is recognized as Mitsubishi.

> The open source drivers are handled by xfree.  Some simple hand editing=
 of
> the XF86Config-4 file will get you going.  A nice feature is that you c=
an
> run both the mouse and the touchscreen simultaneously.

I've been trying this all weekend, to no avail.
Care to share an example...? :)

> The only tough part is calibration, as there yet are no good open sourc=
ed
> programs for this.  Most programs that use a touchscreen perform
> calibration themselfs.

I saw where Elo gives you parameters in the XF86Config file.

> anyhow, just let me know if you have any trouble setting it up.

I'm letting you know... :)

Thanks,=20

Weyland

Weyland,

The monitor part is usually irevelant as the touchscreen portion is usually
OEM'd from one of the touchscreen companies. What I would do is open up the
monitor, and follow the RS232 connector from the back of the monitor to the
touch screen controller board and look for a number or name on it. I suppose
it is possible that this is not the case and it is all built in to the main
board but it's worth a try. CAUTION CAUTION CAUTION. Monitors can kill you
or at least hurt really bad if you touch areas inside EVEN WITH THE POWER
REMOVED. Don't touch anything inside the monitor if you don't know what it
is. Just look for a touchscreen controller board and close it back up.

I started on a touchscreen interface GUI for EMC and even though I use it,
it is far from complete. If you get the touch part working and wish to try
it out, let me know and I'll send you a copy.

Bill

----- Original Message -----
From: "Weyland" <weyland@...>
To: <emc-users@...>; "Dean Hedin" <dhedin@...>
Sent: Tuesday, June 24, 2003 7:50 AM
Subject: Re: [Emc-users] EMC & touchscreens


On Saturday 21 June 2003 12:35 am, Dean Hedin spake:

> I spend a good part of my day job playing around with touchscreens under
> linux.  The majority of the monitor touchscreens are either Microtouch/3m
> or Elographics.  Both have fairly good support under linux.  Microtouch
> also has a closed sourced linux driver.

I'm still not able to find out what this is yet.
Monitor is labeled an Advan, but is recognized as Mitsubishi.

> The open source drivers are handled by xfree.  Some simple hand editing of
> the XF86Config-4 file will get you going.  A nice feature is that you can
> run both the mouse and the touchscreen simultaneously.

I've been trying this all weekend, to no avail.
Care to share an example...? :)

> The only tough part is calibration, as there yet are no good open sourced
> programs for this.  Most programs that use a touchscreen perform
> calibration themselfs.

I saw where Elo gives you parameters in the XF86Config file.

> anyhow, just let me know if you have any trouble setting it up.

I'm letting you know... :)

Thanks,

Weyland


-------------------------------------------------------
This SF.Net email is sponsored by: INetU
Attention Web Developers & Consultants: Become An INetU Hosting Partner.
Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission!
INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php
_______________________________________________
Emc-users mailing list
Emc-users@...
https://lists.sourceforge.net/lists/listinfo/emc-users

Hey Bill~!

On Tuesday 24 June 2003 12:42 pm, William Scalione spake:

> The monitor part is usually irevelant as the touchscreen portion is usu=
ally
> OEM'd from one of the touchscreen companies. What I would do is open up=
 the
> monitor, and follow the RS232 connector from the back of the monitor to=
 the
> touch screen controller board and look for a number or name on it.=20

Yeah..., I was hoping to not have to go that far... <sigh>
I've been searching and searching to no avail.
It's an Advan AGM15T, which is theoretically a Mitsubishi LCD50 (LXA520W)=
=2E
I simply can't find *anything* on either one with regards to touchscreens=
,=20
and calls to Advan have been linguistically challenged as I don't speak
Chinese, Korean, or Japanese, even though I'm calling California...

<shrug>

> I started on a touchscreen interface GUI for EMC and even though I use =
it,
> it is far from complete. If you get the touch part working and wish to =
try
> it out, let me know and I'll send you a copy.

AaaaHAAA~! It was _YOU_~!
I knew I recalled *someone* working on one. :)
Yes, if I can get this thing running=20
(responding) I'd love to see what you've done.
I really think that touchscreen is the way to go if you have one.
Personally, I think it should be a part of EMC.
(whether or not I had one)

Thanks,

Weyland

I think touchscreens should be part of EMC too and I'd be willing to
work on the code to get them going. 

We also need feedwheels !  

Kim 



On Tue, 2003-06-24 at 11:16, Weyland wrote:
> Hey Bill~!
> 
> On Tuesday 24 June 2003 12:42 pm, William Scalione spake:
> 
> > The monitor part is usually irevelant as the touchscreen portion is usually
> > OEM'd from one of the touchscreen companies. What I would do is open up the
> > monitor, and follow the RS232 connector from the back of the monitor to the
> > touch screen controller board and look for a number or name on it. 
> 
> Yeah..., I was hoping to not have to go that far... <sigh>
> I've been searching and searching to no avail.
> It's an Advan AGM15T, which is theoretically a Mitsubishi LCD50 (LXA520W).
> I simply can't find *anything* on either one with regards to touchscreens, 
> and calls to Advan have been linguistically challenged as I don't speak
> Chinese, Korean, or Japanese, even though I'm calling California...
> 
> <shrug>
> 
> > I started on a touchscreen interface GUI for EMC and even though I use it,
> > it is far from complete. If you get the touch part working and wish to try
> > it out, let me know and I'll send you a copy.
> 
> AaaaHAAA~! It was _YOU_~!
> I knew I recalled *someone* working on one. :)
> Yes, if I can get this thing running 
> (responding) I'd love to see what you've done.
> I really think that touchscreen is the way to go if you have one.
> Personally, I think it should be a part of EMC.
> (whether or not I had one)
> 
> Thanks,
> 
> Weyland
> 
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by: INetU
> Attention Web Developers & Consultants: Become An INetU Hosting Partner.
> Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission!
> INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php
> _______________________________________________
> Emc-users mailing list
> Emc-users@...
> https://lists.sourceforge.net/lists/listinfo/emc-users
-- 
Kim Lux <lux@...>

On Tuesday 24 June 2003 18:16, Weyland wrote:

> I really think that touchscreen is the way to go if you have one.

depends. Making wood-dust or routing plastics, yes probably.  Making metal 
chippings with coolant, swarf .. or dust from a plasma ... a touchscreen gets 
pretty useless fairly quickly.

-- 
Robin Szemeti

Redpoint Consulting Limited
Real Solutions For A Virtual World

Woo Hoo~!

Finally got a call back from someone that=20
spoke English well enough to understand.
Seems my touchscreen is a fairly=20
common Elo-touch 2210 controller
I'll let ya know how it goes.
(and hopefully tell ya to send that interface)

Thanks for your help~!

Best,

Weyland

You better send it to me. (wink)  I'll get it going... it might get lost
in shipping though.  We've got a computer here that desperately needs a
touchscreen.  Actually we've got several that need touchscreens.   

Kim 

On Tue, 2003-06-24 at 12:23, Weyland wrote:
> Woo Hoo~!
> 
> Finally got a call back from someone that 
> spoke English well enough to understand.
> Seems my touchscreen is a fairly 
> common Elo-touch 2210 controller
> I'll let ya know how it goes.
> (and hopefully tell ya to send that interface)
> 
> Thanks for your help~!
> 
> Best,
> 
> Weyland
> 
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by: INetU
> Attention Web Developers & Consultants: Become An INetU Hosting Partner.
> Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission!
> INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php
> _______________________________________________
> Emc-users mailing list
> Emc-users@...
> https://lists.sourceforge.net/lists/listinfo/emc-users
-- 
Kim Lux <lux@...>

On Tuesday 24 June 2003 02:19 pm, Kim Lux spake:

> I think touchscreens should be part of EMC too and I'd be willing to
> work on the code to get them going.
>
> We also need feedwheels !

Mmmmmmmm...feeeeeedwheeeeels....
Three please.

Weyland

On Tuesday 24 June 2003 02:19 pm, Robin Szemeti spake:

> On Tuesday 24 June 2003 18:16, Weyland wrote:
> > I really think that touchscreen is the way to go if you have one.
>
> depends. Making wood-dust or routing plastics, yes probably.  Making me=
tal
> chippings with coolant, swarf .. or dust from a plasma ... a touchscree=
n
> gets pretty useless fairly quickly.

Well, I can't speak to plasma dust, and that's=20
a good point I'd not considered, but as for the=20
rest, I'd never had a problem yet in the real world.
(and I've used them as an operator in some pretty sh|tt|e environs)

Best,

Weyland

Hi Weyland

http://www.elotouch.com/support/linux.asp tells us that you'll need

  Section "Inputdevice"
     Identifier "touchscreen1"
     Driver "elographics"
     Option "Device" "/dev/ttyS0"
     Option "AlwaysCore"
     Option "screenno" "0"
     Option "MinimumXPosition" "600"
     Option "MaximumXPosition" "3600"
     Option "MinimumYPosition" "600"
     Option "MaximumYPosition" "3600"
     Option "UntouchDelay" "3"
     Option "ReportDelay" "1"
     DebugLevel "3"
   EndSection

"man XFConfig" also suggests :

       Section "ServerLayout"
         yadda "foo" "bar"
         .....
         InputDevice "PS/2 Mouse" "CorePointer"
         Inputdevice "touchscreen1" "SendCoreEvents"
       EndSection

The elotouch site also describes setting up the screen coordinates, but I 
found it easier to set the DebugLevel and fudge the figures according to the 
raw data on tty0 (Ctrl-Alt-F1).

The above info assumes you're using XFree86 4.0 or above. If you're using 
this touchscreen with a BDI-2.xx, the configs are different (I can email mine 
over as an example).

Regards, Paul.




On Tuesday 24 June 2003 12:50 pm, Weyland wrote:
> I'm letting you know... :)

-- 

"To err is human...to really f*** things up requires the root password."
From a collection of quotes at http://www.indigo.org/quotes.html

On Tuesday 24 June 2003 06:47 pm, Paul spake: 

> http://www.elotouch.com/support/linux.asp tells us that you'll need

Yes, thank you.
I found this a little while ago, after a succesful call to them and Advan.
I told Kim earlier that the problem was kind of wierd in that it didn't 
respond to the diagnostic tools for a 2210, but rather for a 4000 and 140.
Advan told me I probably had one of 100 monitors made that were based on a 
2210 board, but were different, and that the one guy that knew what to do was 
dead....

...oh... goody...

Thankfully, it turned out that there was
a power problem due to a faulty connector.

I'm rockin' now~!
Kinda... (see below).

> The elotouch site also describes setting up the screen coordinates, but I
> found it easier to set the DebugLevel and fudge the figures according to
> the raw data on tty0 (Ctrl-Alt-F1).

How'd you do that?
Here's why -
The screen works wonderfully.
As long as everything I need is to the right and up from my finger.
Using a steel rule, it appears to be equally askew by 2" in each axis.
If I touch the center of the screen, the cursor jumps to 2" up and 2" to the 
right of my finger.

Ideas?

Thanks,

Weyland

Hi Weyland

No need to hit "Reply to All" - It confuses my mail filter...

To calibrate the t/s, initially set the min X & Y coordinates to zero and set 
DebugLevel to 3. Start up XFree86, and with a fine plastic pointer (assuming 
this is a resistive screen), touch the top left hand corner of the visable 
area. Switching to tty0 (Ctrl-Alt-F1), the raw data *should appear as an X 
and Y value. Use these numbers for the min values in the XF86Config.

The process is repeated for the maximum coordinates, but using, say 1600 
instead of zero. Each time you change a value, XFree86 will need to be 
restarted (use "X" instead of "startx" to save time).

There was talk of a calibration utility for touch screens under linux - I 
even came across some beta code a while back. Not sure if the project 
progressed any further since then...

Regards, Paul.

On Wednesday 25 June 2003 4:21 am, Weyland wrote:
> How'd you do that?
> Here's why -
> The screen works wonderfully.
> As long as everything I need is to the right and up from my finger.
> Using a steel rule, it appears to be equally askew by 2" in each axis.
> If I touch the center of the screen, the cursor jumps to 2" up and 2" to
> the right of my finger.

-- 
irc channel for EMC users at irc.freenode.org
/join #emc
and chat to other users (not many there yet).

On Wednesday 25 June 2003 01:13 pm, Paul spake:

> Hi Weyland
>
> No need to hit "Reply to All" - It confuses my mail filter...

Apologies, habit.

> To calibrate the t/s, initially set the min X & Y coordinates to zero a=
nd
> set DebugLevel to 3.=20

Yeah, that was the first problem.
X complained about the "DebugLevel" entry.
Didn't wanna start.

> Start up XFree86, and with a fine plastic pointer
> (assuming this is a resistive screen), touch the top left hand corner o=
f
> the visable area. Switching to tty0 (Ctrl-Alt-F1), the raw data *should
> appear as an X and Y value. Use these numbers for the min values in the
> XF86Config.

Intresting. Hopefully I'll be able to get this working.

> The process is repeated for the maximum coordinates, but using, say 160=
0
> instead of zero. Each time you change a value, XFree86 will need to be
> restarted (use "X" instead of "startx" to save time).

Of note - I played with this for HOURS last night after giggling=20
like an idiot for twenty minutes that it actually worked.
Changing X & Y values had *no* effect on it.
I even tried 0 and negative values.
Nothing seemed to change.
I had been restarting X with ctrl+alt+bkspc,=20
but even tried a few by completely rebooting.

No change. No observed effect.

> There was talk of a calibration utility for touch screens under linux -=
 I
> even came across some beta code a while back. Not sure if the project
> progressed any further since then...

Well, I spoke to Elo today, and they want me to do it in=20
Windows and DOS, as it's the only thing they understand.
The guy wants me to try a calibration utility, but when he told me it was=
=20
software calibration that didn't actually make any changes on the control=
ler,=20
I couldn't see the point.
Still, I'll try it to see the results for comparison.

Which X are you using?
Mine's 4.3.0-2 .

Best,

Weyland

Hi Weyland

I was using the XFree86-3.3.5 config that I use as a reference point, but 
some things have changed in the syntax of each entry.
Reading the xf86Elo.c code, DebugLevel is a valid parameter - Try adding

  Option "Debuglevel "3"

Using 4 will provide additional debugging info if required..

The calibration utility is not essential once you know exactly what it does.
The touch screen sends a raw x,y coordinate to the computer. It is the 
computer's task (via the driver) to translate the raw data into "real" 
coordinates using the following calculations.

  X = (input_x - min_x) * (Screen Width /(max_x - min_x))
  Y = (input_y - min_y) * (Screen Height /(max_y - min_y))

Where Screen Height & Width is in pixels as specified in the Screen section.


Regards, Paul.


On Wednesday 25 June 2003 6:41 pm, Weyland wrote:
> Yeah, that was the first problem.
> X complained about the "DebugLevel" entry.
> Didn't wanna start.

-- 
irc channel for EMC users at irc.freenode.org
/join #emc
and chat to other users (not many there yet).

On Wednesday 25 June 2003 03:12 pm, Paul spake:

>   Option "Debuglevel "3"

=2E..damn... shoulda seen that... everything's an "Option" in 4.
Thanks for the slap.

> Using 4 will provide additional debugging info if required..
>
> The calibration utility is not essential once you know exactly what it
> does. The touch screen sends a raw x,y coordinate to the computer. It i=
s
> the computer's task (via the driver) to translate the raw data into "re=
al"
> coordinates using the following calculations.
>
>   X =3D (input_x - min_x) * (Screen Width /(max_x - min_x))
>   Y =3D (input_y - min_y) * (Screen Height /(max_y - min_y))
>
> Where Screen Height & Width is in pixels as specified in the Screen
> section.

That's what I figured.
It's also what bothers me.
Seems to me I should've seen *SOME* kind of=20
difference in making all those changes to the config numbers.

Ideas?

I'll try this in a little while when I get home.
It's a little too difficult to judge a touchscreen's=20
reactions over ssh at this level of my learning curve. :)

Weyland

Hi Weyland

I suppose it depends on the range of values you have been trying. The source 
code expects X in the range of 0 to 10500, and Y 0 to 9500 - If you were 
outside of this range, I doubt you would get the response you expected..

Send me the XF86Config-4 and /var/log/XFree86.0.log and I'll see if I can't 
spot any obvious errors.

Regards, Paul.


On Wednesday 25 June 2003 8:30 pm, Weyland wrote:
> That's what I figured.
> It's also what bothers me.
> Seems to me I should've seen *SOME* kind of
> difference in making all those changes to the config numbers.

-- 

"To err is human...to really f*** things up requires the root password."
From a collection of quotes at http://www.indigo.org/quotes.html

On Wednesday 25 June 2003 04:05 pm, Paul spake: 

> I suppose it depends on the range of values you have been trying. The
> source code expects X in the range of 0 to 10500, and Y 0 to 9500 - If you
> were outside of this range, I doubt you would get the response you
> expected..

I've been trying X in the range of 0 to 600 and Y in the range of 0 to 4500.
Differing values at differing times and no effect, seemingly.

> Send me the XF86Config-4 and /var/log/XFree86.0.log and I'll see if I can't
> spot any obvious errors.

Appreciated. And sent.

It's just wierd.
I'm gonna throw a spare drive in 
and see what it's like with windiws.
Personally, I think it a waste of time, but I 
also think I should at least eliminate it as a possibility.

Best,

Weyland

Weyland,

Do you get any response from the controller when you touch the screen?
You should see the cursor move when you touch the screen, albiet maybe not 
where you want it to be.

I'm just trying to seperate functionality from the calibration aspect.  If 
your not seeing any motion of the cursor then your problens could be more 
fundamental, like you don't have the serial port turned on in the BIOS,
cableing issues etc...

Examining the xfree log file should tell you weather or not  the xdriver sees 
the touch screen.

>Well, I spoke to Elo today, and they want me to do it in
>Windows and DOS, as it's the only thing they understand.
>The guy wants me to try a calibration utility, but when he told me it was
>software calibration that didn't actually make any changes on the
controller,
>I couldn't see the point.
>Still, I'll try it to see the results for comparison.
>

Weyland,

It is all software calibration, none of the calibration programs actually
change the touchscreen controller parameters. When you use a calibration
program all you are doing is finding out the X and Y position of your touch
at a known point on the screen and using those numbers in the touchscreen
driver to figure where the position of the cursor should be when you touch
the screen. You can use a DOS boot disk with the ELO touchscreen drivers and
calibration program. Write down the numbers you get and enter them into your
XF86Config file and that should do it. I remember something about this when
trying to get my touchscreen working. The XF86Config file is in a different
place with version 4.xx of X than with version 3. I vaguely remember
changing the config file and nothing happening. Found another directory with
another config file and changed that one and all worked well.

Bill

ps. If you really can't get that baby working I'll be happy to take it off
your hands :) ,but if it sees your touch, there is nothing wrong with it
except a setup problem.

On Thursday 26 June 2003 12:51 am, Dean Hedin spake: 

> Do you get any response from the controller when you touch the screen?
> You should see the cursor move when you touch the screen, albiet maybe not
> where you want it to be.
> I'm just trying to seperate functionality from the calibration aspect.  If
> your not seeing any motion of the cursor then your problens could be more
> fundamental, like you don't have the serial port turned on in the BIOS,
> cableing issues etc...
> Examining the xfree log file should tell you weather or not  the xdriver
> sees the touch screen.

Oh, yeah, X sees it. It just doesn't 
seem to wanna let me *play* with it.
Like I explained later in the thread, 
it moves very well anywhere I put it.
It's just _offset_ from *me*.
I've tried just about every diagnostic 
tool I can find from Elo, to no avail.
Everything from them says the controller and screen are good.

I'm very open to ideas right now.

(No Kim, shipping isn't one of them) :)

Thanks,

Weyland

Hey Bill~!

On Thursday 26 June 2003 12:48 am, William Scalione spake: 

> It is all software calibration, none of the calibration programs actually
> change the touchscreen controller parameters. When you use a calibration
> program all you are doing is finding out the X and Y position of your touch
> at a known point on the screen and using those numbers in the touchscreen
> driver to figure where the position of the cursor should be when you touch
> the screen. You can use a DOS boot disk with the ELO touchscreen drivers
> and calibration program. Write down the numbers you get and enter them into
> your XF86Config file and that should do it. I remember something about this
> when trying to get my touchscreen working. The XF86Config file is in a
> different place with version 4.xx of X than with version 3. I vaguely
> remember changing the config file and nothing happening. Found another
> directory with another config file and changed that one and all worked
> well.

Intrestingly enough, ther *ARE* two XF86Config files on my drive.
Sadly, both are identical... 
I thought you had it there for a minute.

Also, there *is* a utility that you can make changes to the controller with.
It's called SmartSet, and is also DOS based.

Tried it. No love.
This is really, really bothering me for some reason....

> ps. If you really can't get that baby working I'll be happy to take it off
> your hands :) ,but if it sees your touch, there is nothing wrong with it
> except a setup problem.

Yeah, you and Kim both. :)
I'll keep it for now. <grins>

Best,

Weyland

On 06/26/03, at 12:48 AM, "William Scalione" <wscalione@...> said:

>if it sees your touch, there is nothing wrong with it
>except a setup problem.

I had a bad one that worked but wouldn't hold calibration. 
I replaced it after it put the pointer about an inch and a half off and shut the spindle down in the middle of a cut.
My theory is that the touch screen was damaged by improper storage, specifically spending a winter in a barn in CT.
The key symptom was inconsistent behaviour, so if Weyland's is consistent, then it's not the same problem that I saw.

-- 
-----------------------------------------------------------
Carl Brown cbsled@...
------------------------------------------------------
When there's no plan, there's one less thing to go wrong.
    -Joe Redington Sr.
-----

On Thursday 26 June 2003 09:03 am, cbsled@... spake:

> I had a bad one that worked but wouldn't hold calibration.
> I replaced it after it put the pointer about an inch and a half off and
> shut the spindle down in the middle of a cut. My theory is that the tou=
ch
> screen was damaged by improper storage, specifically spending a winter =
in a
> barn in CT. The key symptom was inconsistent behaviour, so if Weyland's=
 is
> consistent, then it's not the same problem that I saw.

*That* is what's bugging me so much.
It's _perfectly_ consistent.
It's like it's just gotta be told "Hey~! Yer off by *this* much..."
Now, that _should_ have happened in the XF86Config=20
from everything I've been told and read, but it ain't.

Stumped.

Weyland