Touchscreen support - howto please

Hi,
I want to use a Hampshire TSHARC12 touchscreen controller, which I am
told by the manufacturer should work with the dynapro drivers (anybody
know better?). Anyway, I need to know how to set things up in QNX6.
First off, if I run devi-dyna dyna fd -d/dev/ser3 (from memory, may not
be exact syntax) it won’t start because there is no calibration file.
But how it be calibrated without the driver running?? Also, the docs
for calib say “start a pterm and type calib”, but calib is not found. I
have an older copy I begged from QNX a while back but if I load it I end
up having to power down the computer because it wants touchscreen input
but there is no driver running!! Help please.

If you do a “use devi-dyna”, under the abs filter module you will see an
option “-c”. This means run the driver in calibrate mode (i.e. it wont
expect to see a calibration file); therefore:

devi-dyna dyna fd -d/dev/ser3 abs -c

should do the trick (i.e. it should start without complaining, allowing
you to run calib).

-----Original Message-----
From: Bruce Davis [mailto:bruce.r.davis@boeing.com]
Posted At: Monday, April 16, 2001 4:49 PM
Posted To: installation
Conversation: Touchscreen support - howto please
Subject: Touchscreen support - howto please


Hi,
I want to use a Hampshire TSHARC12 touchscreen controller, which I am
told by the manufacturer should work with the dynapro drivers (anybody
know better?). Anyway, I need to know how to set things up in QNX6.
First off, if I run devi-dyna dyna fd -d/dev/ser3 (from memory, may not
be exact syntax) it won’t start because there is no calibration file.
But how it be calibrated without the driver running?? Also, the docs
for calib say “start a pterm and type calib”, but calib is not found. I
have an older copy I begged from QNX a while back but if I load it I end
up having to power down the computer because it wants touchscreen input
but there is no driver running!! Help please.

Bruce Davis <bruce.r.davis@boeing.com> wrote:

Hi,
I want to use a Hampshire TSHARC12 touchscreen controller, which I am
told by the manufacturer should work with the dynapro drivers (anybody
know better?). Anyway, I need to know how to set things up in QNX6.
First off, if I run devi-dyna dyna fd -d/dev/ser3 (from memory, may not
be exact syntax) it won’t start because there is no calibration file.
But how it be calibrated without the driver running?? Also, the docs
for calib say “start a pterm and type calib”, but calib is not found. I
have an older copy I begged from QNX a while back but if I load it I end
up having to power down the computer because it wants touchscreen input
but there is no driver running!! Help please.

There is a touch screen driver update that includes calib, and a devi-hirun
that does not lock up when you run calib available at

ftp://install.qnx.com/repository
username: beta
password: b3t4

Thanks! that very nearly got me there. But something very strange happened.
I used devi-dyna dyna -b9600 fd -d/dev/ser3, then ran calib successfully. The
touchscreen seems to work fine. But the keyboad went away ?!? One odd thing
is that the keyboard is on a normal keyboard port but when QNX loads (patch B)
I see the line devi-hirun kbd fd -d/dev/kbd msoft fd -d /dev/ser4, which is
very odd. I do have a fourth serial port but it is certainly not connected to
the keyboard. So how do I get the touch screen and the keyboard working at the
same time? (I don’t see why there would be any interaction between them - the
keyboard is supposed to be using IRQ1, COM3 is on IRQ 10, and COM4 is on
IRQ11).

pete@qnx.com wrote:

Bruce Davis <> bruce.r.davis@boeing.com> > wrote:
Hi,
I want to use a Hampshire TSHARC12 touchscreen controller, which I am
told by the manufacturer should work with the dynapro drivers (anybody
know better?). Anyway, I need to know how to set things up in QNX6.
First off, if I run devi-dyna dyna fd -d/dev/ser3 (from memory, may not
be exact syntax) it won’t start because there is no calibration file.
But how it be calibrated without the driver running?? Also, the docs
for calib say “start a pterm and type calib”, but calib is not found. I
have an older copy I begged from QNX a while back but if I load it I end
up having to power down the computer because it wants touchscreen input
but there is no driver running!! Help please.

There is a touch screen driver update that includes calib, and a devi-hirun
that does not lock up when you run calib available at

ftp://install.qnx.com/repository
username: beta
password: b3t4

I’ve got a little more information - it seems like calib is somehow nuking the
keyboard. If I don’t run calib everything seems to work ok.

Follow on question - how do I set up the startup scripts so that photon uses the
touchscreen when it loads? Thanks.

Bruce Davis wrote:

I’ve got a little more information - it seems like calib is somehow nuking the
keyboard. If I don’t run calib everything seems to work ok.

Follow on question - how do I set up the startup scripts so that photon uses the
touchscreen when it loads? Thanks.

it should probably be sufficient to put the commands needed to enable
the touchscreen
(such as loading drivers etc) in a file rc.local under /etc/rc.d
then qnx will load it during the boot process…
(make sure that the rc.local got the execute bit set)

as I understand it Photon will use whatever devices that has been loaded
by QNX when it starts up

Well I tried it - it doesn’t work (at least not for me). My guess is that devi-dyna
needs photon to be running and it is not (?) when rc.local is executed.

Crudbreeder wrote:

Bruce Davis wrote:

I’ve got a little more information - it seems like calib is somehow nuking the
keyboard. If I don’t run calib everything seems to work ok.

Follow on question - how do I set up the startup scripts so that photon uses the
touchscreen when it loads? Thanks.

it should probably be sufficient to put the commands needed to enable
the touchscreen
(such as loading drivers etc) in a file rc.local under /etc/rc.d
then qnx will load it during the boot process…
(make sure that the rc.local got the execute bit set)

as I understand it Photon will use whatever devices that has been loaded
by QNX when it starts up

Bruce Davis wrote:

Well I tried it - it doesn’t work (at least not for me). My guess is that devi-dyna
needs photon to be running and it is not (?) when rc.local is executed.

no, photon is started first after all the rc.* scripts have been run.

After what I can find on qdn, photon uses a script file called phapps in
your ~/.ph dir to run things when it start.

There is some more info about it in this article:

http://qdn.qnx.com/support/bok/solution.qnx?10162

(the second half of the article)