|
Nanovison Mimo touchscreen display
configuration
30th May 10 As suppliers of the Mimo touch screen driver we are often contacted if any
issues are encountered with the Windows touch driver supplied with the device
or the Mac and Linux driver supplied directly from us. This is in part because there is little or
no direct support offered by the manufacturers or suppliers of the device. We have no problem with assisting with Mimo touch queries but we have found by experience that
many issues arise from either the supply of old out-of-date drivers or user
misunderstanding of the use of our driver. The Mimo
device uses a resistive touch controller from a company called e2i which
later became SJT. The graphics USB
interface comes from a company called DisplayLink and
latest drivers are available on the web site at http://www.displaylink.com/support/downloads.php.
It is always recommended you download
and install the latest graphics drivers
along with the latest touch screen driver, see below This document is mainly
aimed at the Windows users but the same advice applies to the Mac OS X and
Linux users. Touch-Base Mac and Linux
drivers are not automatically supplied for this device but drivers are
available from the download
page of our web site or from links at the bottom of
this document. Regarding the touch
driver, called UPDD, we initially supplied version 3.x.x of our Windows
driver. This was superseded with 4.0.x and recently the suppliers were shipping
4.1.6. We are now shipping 4.1.8 for full Vista and Windows 7 touch
utilisation – See note 1). Our driver is supplied in the form of an
executable called setup.exe. A lot of Mimo users
seem to be supplied version 4.0.3 or 4.0.6, 32 bit support only, which in the
UPDD software names the touch device as “e2i Technologies, NTR, USB”. There are also some 4.1.x drivers using this name but
when e2i became SJT we supplied a 4.1.6 driver for 32 and 64 bit in which the
device is referred to as “SJT, USB”.
Both these names refer to the same device. In addition, 4.1.6
automatically recognises when the device is rotated and adjusts the calibration
accordingly. From our records we
believe that 4.0.x, depending on the build, may have some calibration
issues. We also know that when these
earlier versions are installed the Windows desktop associated with the touch
device by default is the primary monitor, in UPDD terms this is called the
‘Whole Desktop” and therefore the calibration screen and mouse movements will
occur on the primary monitor, not the Mimo device! Given that the Mimo device is normally an extra monitor on a Windows
system then the UPDD Console program needs to reflect the relationship
between the touch device and the Windows monitor associated to the Mimo device. So, for example, if you attach a Mimo to a single monitor computer the Mimo
device is likely to become Monitor 2, attached to a 2 monitor system it is
likely to become Monitor 3 etc. In this example a Mimo device is connected to a Single monitor system to
create a dual monitor system whereby the Mimo
device becomes Monitor 2. In this case
the UPDD setting is as shown.
In the above example,
when you run Calibrate the calibration screen will be displayed on the Mimo device and when you touch the screen the touch will
also relate to Monitor 2. Since UPDD 4.1.x the
driver supplied to e2i/SJT tries to automatically make this desktop
association (See note 2) once the Mimo
touch device is detected so it is possible that the setting will be correct
after install. If this is not the case then manually change the setting. The latest 4.1.6 driver
for the ‘SJT, USB’ device can be downloaded from here. (http://touch-base.com/downloads/production/mimo/setup.exe) Supported Operating
Systems: Windows XP Windows Windows 7 ------------------------- (UPDD 4.1.6 does not invoke Windows 7
advanced touch features) 32 and 64 Bit Support The latest 4.1.8 driver
for the ‘SJT, USB’ device can be downloaded from here. (http://touch-base.com/downloads/production/mimo/Win7/setup.exe).
This supports the same OSes as above. Due to the current restrictions (Note 1) the extended touch option
is disabled by default. Documentation A full set of UPDD
documentation is available on our web site at http://www.touch-base.com/documentation.asp,
specifically: Windows Install: http://www.touch-base.com/documentation/WindowsPlatformNotes.htm UPDD Console: http://www.touch-base.com/documentation/UPDD%20console.htm Windows 7 extended
features: http://touch-base.com/documentation/OS%20Extended%20Touch%20Features.htm TroubleShooting We recommend that you use
the latest graphics driver from DisplayLink and the
latest UPDD driver. With these drivers in
place if the touch still fails to work, then, unless there is a hardware
error with the touch hardware, it is likely that the system has not
associated UPDD with the touch USB controller. To confirm this is the case open up the
UPDD Console. In a working system the touch device name should be shown in
black. This means that the driver is associated with the device. If the name is shown in red (e2i
Technologies, NTR or SJT) or missing then the driver is not
associated with the device, as shown here:
In this instance unplug
and replug the USB device. If this does not correct the problem and
the touch does still not work then run up the Windows Device Manager (Start
> Control Panel > System > Hardware > Device Manager) and look
for a device called USB Touchpanel. If this entry is missing the system is not
physically seeing the device and there may be a hardware fault. If it is listed it will have a yellow
exclamation mark to indicate the driver is missing.
Right click on the device
and select the option to manually update the driver and follow the
instructions, selecting the UPDD driver when prompted to select a
driver. More information on this
procedure is available here. Notes:
1)
At
time or writing (May 2010) UPDD 4.1.8 with extended touch mode enabled the
touch input is directed to the primary monitor only. In normal touch mode the
touch input is directed to the assigned desktop, e.g. Monitor 2. To utilise extended touch features with the
mimo device set the device to be the primary
monitor. A future release of UPDD will remove this restriction and all UPDD
supported devices will be able to use extended touch features. 2)
The
driver searches internal structures looking for an attached video device with
the characteristics of a Mimo device. This method
is not 100% reliable. The Displaylink interface now offers an API to identify the
associated monitor and in a future release of the driver we will be using
this API. Links:
Trial drivers for both
Linux and Mac OSX are available for the Mimo
device. Costs for production drivers
are here. The Linux driver is
available here.
Please read documentation here.
The MacOSX driver is
available here
(Intel) and here
(Power PC). Please read documentation here. |