Troubleshooting

Microsoft Windows Vista and later operating system versions have increased support for touch devices:

1. Touch control completely supported under Windows Vista / 7 Professional and later OS versions.
2. Touch function settings only partially supported under Windows Vista / 7 Starter.
3. The Tablet PC Feature Suite must be selected to use touch control under Windows Embedded Standard 7.
4. The Desktop Experience Suite must be separately installed to use touch control under Windows Server 2008 / 2008 R2.
5. Windows 8 / Windows Embedded 8 Standard / Windows Server 2012 support touch functions by default.

Install the latest PenMount driver V2.4.2.325, the Windows 2000/ XP system will emulate a mouse device.  If installed in Windows 2008/Vista/ 7/ 8 mouse emulation or touch device can be selected in the installation process.

Note: Since default Windows Server 2008 does not include the “Desktop Experience” suite, we recommend you install mouse emulation to avoid false touch issues.

Yes, please contact us to obtain multiple monitor setting instructions for touch controllers.

• The S1 wake up mechanism supports RS-232 and USB interfaces.
• The S3 wake up mechanism does not support the RS-232 interface. If an USB interface is used, you should note whether the BIOS supports the S3 wake up mechanism, and you must enable “allow this device to restart standby computer” in Windows [Device Manager]→PenMount Devices [Content]→[Power Management]→restart.

Yes, please reference the following command to run the calibration program directly from the command line:

<Path To Install Dir>DmcCtrl.exe -calibration [ 0 | 4 | 9 | 16 | 25 ]

Remark: 0 refers to standard calibration; 4, 9, 16, 25 refer to advanced calibration (4, 9, 16, 25 points)

Please install the latest driver.  Updated device functions have been added to the latest driver.

PenMount’s advanced calibration function can correct touch panel linearity issues.  Normally, accuracy can be achieved after 9 point calibration.  When executing advanced calibration, please do not use your finger.  We recommend using a PenMount stylus to confirm touch and calibration points.  If there is still a large deviation after completing 25 point calibration, it is possible that your touch panel has aged to the point of severe linearity deviation and cannot be effectively corrected using PenMount calibration software.

Since this is a Microsoft OEM version of the system, normal operation is limited to Touch logo touch devices. Microsoft recently removed the 8.1 OEM limit for touch operation, you only need to install the linked service update and you will be able to use touch devices not authenticated in Windows 8 on your system.

Link: //support.microsoft.com/en-us/kb/3095649

The virtual keyboard is controlled by the Microsoft system. When the Digitizer device is detected on the system side, the system will automatically activate the virtual keyboard function. During the installation of the PenMount driver, select “No” to simulate the device as a Digitizer device.

It is recommended to only execute the calibration provided by PenMount device drivers. The PenMount calibration can achieve the best linear correction result and support the calibration values to be saved to the controller to avoid conflicts with the system calibration data. If you have executed Microsoft’s built-in calibration, please go to Tablet In the PC Settings > Display page, execute the “Reset” function key to remove the system calibration data.

The device driver user guide provides information on changing the default values in the install.ini file. Please contact your providers for the document.

In a multiple monitor system, it is always necessary to perform monitor mapping even when there is only one PenMount device.

Please perform monitor mapping after the PenMount device driver is installed. Please notice that the PenMount device driver will not recognize other brand controllers.

The first time a PenMount touch monitor is connected and configured as extended display, touch operation could make mouse cursor move though all displays. After multi-monitor mapping is performed, the cursor will be accurate again.

Yes. When install the device driver for resistive products, please select the Digitizer device mode. The monitor mapping for digitizer device mode is supported by Windows system directly..

Open the “Control Panel”, select “Tablet PC Settings”, on the “Display” page, click the “Settings” button, and follow the steps indicated on the screen to complete the monitor mapping.

The Windows NT 4.0 only supports RS-232 interface. The PenMount 9000 RS-232 Windows NT 4.0 device driver is available for download from PenMount website.

This is because the original Windows 7/8 system does not support SHA-2.

(1) Install Windows 7 system update and then install the new version of PenMount driver.

(2) If your system cannot be updated, you can choose to install older versions of PenMount device driver.

Yes, please install the PenMount driver, you can choose to make a sound from the buzzer or the horn.

Please install the latest driver version and select “use system touch gestures” during the installation process.

Without special application development, under Windows systems, the system can only allow one touch device operating system interface.

Not supported due to limitations of the WINDOWS system.

The latest version of PenMount Driver can be installed for support. Capacitive products can maintain multi-finger mode by selecting “use system touch gestures” during the installation process.

This message is a related message that the system will only display when the device reports to the system that it is a touch device type.

No, WinCE cannot simultaneously support 2 or more devices.  If you need to use 2 PenMount devices, please contact your sales window.

• Determine whether there is a conflict with the COM port resources used by your PenMount RS-232 device and exclude the effect of the Debug Port.
• Please ensure the system COM Port driver load sequence is earlier than the PenMount driver sequence.

Please ensure you added the Beep Driver when compiling the Windows XP Embedded system. Otherwise, there will be no Beep.

The embedded driver downloaded from the PenMount website is for Platform Builder. After the system image is generated, the driver will be built into the system. If your Windows Embedded Compact system comes without PenMount device driver, and please ask contact window for a suitable solution.

Please check whether the PenMount device has enabled save to EEPROM feature. If you prefer using calibration in system, please confirm whether the write protect mechanism is disabled, or the utility will not be able to save values in registry.

ARM and MIPS architecture uses reduced instruction set (RISC) processors.  Please contact your sales window.  After you have filled out and signed a NDA, we will provide you with the PenMount Linux kernel driver source code.  After compiling your system, you will be able to drive the PenMount device.

Please follow the link below to confirm your PenMount model and the Linux kernel version used, and refer to the first chapter of the documentation.

File download link

If your Linux kernel already contains a driver that supports PenMount, you can directly follow the steps in the documentation. Otherwise, please follow the steps in the documentation. Item (1) is processed.

No, Linux can only support 1 PenMount device. If you need to use 2 PenMount devices, please contact your sales window.

Yes, PenMount Linux Driver V2.0 or later can support these functions.

Yes, please use driver version V2.3.0.15 or later.  The PenMount Linux Driver supports xrandr V1.2.

After switching USB Ports, Linux will switch to its built-in HID driver to drive the PenMount USB device.  Thus, the device can function but cannot communicate with PenMount calibration software.

Hot swapping is only fully supported on Linux X window 1.5 or later versions.  Hot swapping functionality supported for PenMount devices when paired with PenMount Linux driver V3.6.1 or later versions.

After switching USB Ports, Linux will switch to its built-in HID driver to drive the PenMount USB device.  Thus, the device can function but cannot communicate with PenMount calibration software.

Hot swapping is only fully supported on Linux X window 1.5 or later versions.  Hot swapping functionality supported for PenMount devices when paired with PenMount Linux driver V3.6.1 or later versions.

In the standard Linux system default setting, COM1/ COM2 resources do not conflict.  Please confirm whether your Linux system is allocating COM3 resources normally and whether this is the same as BIOS settings.

No, the PenMount Linux Drivers provided on the website can only be used with the X window GUI.  Please contact your sales window.  After you have filled out and signed a NDA, we will provide you with the PenMount Linux kernel driver source code.  Use with Tslib calibration procedures.

PenMount Linux Driver 4.0 and later versions support multiple display settings. Please reference the following steps to setup a corresponding number of displays:

1. Obtain corresponding monitor designations on the system:
   Please execute xrandr to obtain corresponding display designations. In this example, the display designation is “VGA1”:
   $ xrandr
   Screen 0: minimum 320 x 200, current 800 x 600, maximum 3840 x 1920
   VGA1 connected 800×600+0+0 0mm x 0mm
   800×600        60.0*    56.0      0.0
2. Before installing the PenMount Linux driver, you must first setup the display. Please insert the display designation obtained in step 1 into “Monitor=” of penmount.ini as follows:
   ##############################################################################
   #  Mapped Monitor Settings
   ##############################################################################
   Monitor=VGA1
3. After installing the PenMount Linux driver, please assign corresponding monitors as follows:
   3.1 If your system uses /etc/X11/xorg.conf to setup PenMount devices, please insert the display designation as follows:
   Section “InputDevice”
   Identifier “PenMount”
   Option “Monitor” “VGA1″
   EndSection

3.2 If your system uses /usr/share/hal/fdi/policy/20thirdparty/99-x11-penmount.fdi to setup PenMount devices, please insert the display designation as follows:
<merge key=”input.x11_options.Monitor” type=”string”>VGA1</merge>

3.3 If your system locates the PenMount setup file in the xorg.conf.d folder such as /etc/X11/xorg.conf.d/99-input-penmount.conf, please insert the display designation as follows:
Section “InputClass”
Identifier “PenMount Touch Screen”
Option “Monitor” “VGA1″
EndSection

The Wayland is the default mode in Linux login screen that uses GDM3, so it will be normal again after you logged in to X-Window desktop. Our solution is to modify custom.conf file. Please set the WaylandEnable value to false in this file.

/etc/gdm3/custom.conf

[daemon]

WaylandEnable=false

Customers can manually open “Universal Access” from the Login screen. Select Screen Keyboard from the drop-down menu.

Because QT does not support hot swap, please ask for the auxiliary program and follow the steps below to permanently mount the device:

1. Set the system so that it will execute the auxiliary program when it is turned on.
2. Confirm that the PenMount device has appeared from /proc/bus/input/devices.
3. Install the X Server driver.

When the ARM version of Linux’s kernel 4.X does not include the PM6000 USB kernel driver hid-penmount, it will not work.

Regarding the hid-penmount driver, the description is as follows:

Please set as follows in the kernel config,

CONFIG_HID_PENMOUNT=y

And recompile the kernel, and add the hid-penmount module (link).

Yes, strictly speaking yocto is a software framework for creating Embedded Linux, allowing developers to create Embedded Linux distributions for specific hardware platforms, such as NXP iMX.

When you use the tools provided by the yocto project to generate a Linux system, the matching kernel already includes PenMount support. Please set up and enable PenMount driver-related projects.

If the graphical interface you use is X Window, you can also install the standard version of PenMount Linux driver and location program.

Please download the pm-gcalib calibration utility, aarch64 version. After decompression, run the program:

# ./pm-gcalib

Follow the onscreen instructions and finish calibration.

a) Confirm whether the following calibration files are generated. Normally, this file will be generated when the calibration is completed.

If this file exists, please also copy it to the following path:

Then restart the system.

b) To determine if the system has loaded the calibration file, please execute the following command:

Normally one of the event devices representing PenMount 6000 USB will have LIBINPUT_CALIBRATION_MATRIX setting. Please provide the generated udev.log file to your contact window.

Please login the system as a non-root user and install with the sudo command.

$ sudo ./install.sh

When logging in to the system, enter the system with root authority, and install according to the following instructions.

#./install.sh -svc

Yes, please download it from the PenMount website. Please select “Linux (X11)” under “Operating System” and relevant download links will appear.

Yes, please install the PenMount driver. Currently, the buzzer is supported. If you need to make a sound from the speaker, you can ask your technical window.

It is recommended to try Wayland in the desktop environment.

1. Description

PenMount 5000 / 6000 USB touch screen controllers are standard HID complant devices, therefore they are directly supported by the QNX HID device driver and calibration utility.
To enable PenMount USB touch screen input, please follow the steps described in the following section.

2. Device Setup

(1). Touch Screen Setup

Check if the file /etc/system/trap/input.${HOSTNAME} exists.

(A). If yes, append the following text at the end of the file :

devi-hid touch

(B) If no, create a new file by using the following command :

#inputtrap query > /etc/system/trap/input.${HOSTNAME}

After the file is created, use text editor and add the following text :

devi-hid mouse kbd touch

Save the file and restart the system to make the changes take effect.

(2) Touch Screen Calibration

To calibrate the touch screen, please open Terminal, then run the following command :

#calib

This will launch the QNX calibration utility. By default, the utility will use 3 point calibration algorithm.
If you need more control on calibration, please read the documentation on QNX website

//www.qnx.com/developers/docs/6.4.0/neutrino/utilities/c/calib.html

This is because system procedures will switch to reading input.${HOSTNAME} to intitiate driving. Thus, please open file input.${HOSTNAME} and add devi-hid mouse kbd touch to ensure normal USB mouse and keyboard operation.

The DOS system limits you to one device.

Please ensure Buzzer is installed on your computer.

• When pressing the touch panel, the LED will illuminate. When nothing is pressing on the touch panel, the LED will be dark. This indicates the circuit between “computer – controller – touch panel” is normal.
• If the LED is constantly illuminated, the touch panel’s active area is being compressed by a mechanism or object or there is a pin correspondence error between the touch panel and controller.

(Remark: if the driver for the PenMount 6000 RS-232 has not been installed, the LED will be constantly illuminated.)

• When pressing the touch panel, if the LED does not illuminate, the following reasons may be the cause: no power supply, touch panel malfunction, controller malfunction, connector error, or operation is occurring on the wrong side of the touch panel.

You can first confirm the system’s COM Port is operating normally or use the following PenMount provided testing software to determine whether the COM Port is occupied by other software or drivers:

Step 1: Connect the PenMount device to the COM Port.

Step 2: Uninstall PenMount RS-232 driver to prevent the driver occupying COM Port resources.

Step 3: Use the following testing tool accoding to operating system to determine whether COM Port resources are normal:

Remarks: Please fill in 19200 or 9600 according to your hardware baud rate setting. If you use 6000 RS232 interface and have RTS pin connected, you will need to send command to enable touch function. Please type t when 232nt utility is running, and the program will prompt for “Input HEX :”.

Please type the following six values with space between each value, and press Enter to send the command:

f1 00 00 00 00 0e

Step 4: After executing the aforementioned software, when you press the touch panel, touch data will be sent and indicate your COM Port is normal.  If no signal appears, COM Port resources may be occupied, making the PenMount driver unable to communicate with the PenMount hardware device.

Please select the following links. [ PenMount Touch Controller Support Form ] After detailing your needs and submitting these forms, we will resolve your issues as soon as possible.

If you have any needs, please feel free to contact us for discussion.

Control Board

1. Go to task manager to confirm whether device is connected.
   If device has not been acquired, please confirm the following items:
   • Confirm whether the cable connection is normal.
   • Confirm cable: please replace cable.
   • Confirm cable and control board connection: confirm whether control board probe is crooked.
   • Confirm touch panel and control board connection: clean the pin connector with an eraser and reconnect the control board.
   • Confirm whether operating voltage meets Controller Board Datasheet requirements.
2. If task manager acquire the device, start PCIUtility to see whether the device is recognized.
3. If PCIUtility does not recognize device, firmware settings may be different than the interface in use. Please refer to the Controller Board Datasheet to correct hardware settings.
4. When PCIUtility recognizes the device, please confirm the following items:
   • PCIUtility→Diagnostic→open-short: confirm whether panel is normal
   • PCIUtility→Diagnostic→Noise Level: confirm whether environment is normal
   • PCIUtility→Diagnostic→System Reference: perform calibration
5. If the item “4” tests fail or problems persist, please retrieve the log file from Debug→Log Current Device Information and send it to AMT for analysis.

COF(ZIF)

1. Go to task manager to confirm whether device is connected.
   If device has not been acquired, please confirm the following items:
   • Confirm connection between touch panel and mother board: clean the pin connector with an eraser and reconnect the control board.
   • Confirm whether driver version is correct.
   • Confirm whether operating voltage meets Controller Board Datasheet requirements.
2. If task manager acquire the device, start PCIUtility to see whether the device is recognized.
3. If PCIUtility does not recognize device, firmware settings may be different than the interface in use. Please refer to the Controller Board Datasheet to correct hardware settings.
4. When PCIUtility recognizes the device, please confirm the following items:
   • PCIUtility→Diagnostic→open-short: confirm whether panel is normal
   • PCIUtility→Diagnostic→Noise Level: confirm whether environment is normal
   • PCIUtility→Diagnostic→System Reference: perform calibration
5. If the item “4” tests fail or problems persist, please retrieve the log file from Debug→Log Current Device Information and send it to AMT for analysis.

Control Board

1. Go to task manager to confirm whether device is connected.
   If device has not been acquired, please confirm the following items:
   • Confirm whether the cable connection is normal.
   • Confirm cable: please replace cable.
   • Confirm cable and control board connection: confirm whether control board probe is crooked.
   • Confirm touch panel and control board connection: clean the pin connector with an eraser and reconnect the control board.
   • Confirm whether operating voltage meets Controller Board Datasheet requirements.
2. If task manager acquire the device, start PCIUtility to see whether the device is recognized.
3. If PCIUtility does not recognize device, firmware settings may be different than the interface in use. Please refer to the Controller Board Datasheet to correct hardware settings.
4. When PCIUtility recognizes the device, please confirm the following items:
   • PCIUtility→Diagnostic→open-short: confirm whether panel is normal
   • PCIUtility→Diagnostic→Noise Level: confirm whether environment is normal
   • PCIUtility→Diagnostic→System Reference: perform calibration
5. If the item “4” tests fail or problems persist, please retrieve the log file from Debug→Log Current Device Information and send it to AMT for analysis.

COF(ZIF)

1. Go to task manager to confirm whether device is connected.
   If device has not been acquired, please confirm the following items:
   • Confirm connection between touch panel and mother board: clean the pin connector with an eraser and reconnect the control board.
   • Confirm whether driver version is correct.
   • Confirm whether operating voltage meets Controller Board Datasheet requirements.
2. If task manager acquire the device, start PCIUtility to see whether the device is recognized.
3. If PCIUtility does not recognize device, firmware settings may be different than the interface in use. Please refer to the Controller Board Datasheet to correct hardware settings.
4. When PCIUtility recognizes the device, please confirm the following items:
   • PCIUtility→Diagnostic→open-short: confirm whether panel is normal
   • PCIUtility→Diagnostic→Noise Level: confirm whether environment is normal
   • PCIUtility→Diagnostic→System Reference: perform calibration
5. If the item “4” tests fail or problems persist, please retrieve the log file from Debug→Log Current Device Information and send it to AMT for analysis.

Control Board

1. Go to task manager to confirm whether device is connected.
   If device has not been acquired, please confirm the following items:
   • Confirm whether the cable connection is normal.
   • Confirm cable: please replace cable.
   • Confirm cable and control board connection: confirm whether control board probe is crooked.
   • Confirm touch panel and control board connection: clean the pin connector with an eraser and reconnect the control board.
   • Confirm whether operating voltage meets Controller Board Datasheet requirements.
2. If task manager acquire the device, start PCIUtility to see whether the device is recognized.
3. If PCIUtility does not recognize device, firmware settings may be different than the interface in use. Please refer to the Controller Board Datasheet to correct hardware settings.
4. When PCIUtility recognizes the device, please confirm the following items:
   • PCIUtility→Diagnostic→open-short: confirm whether panel is normal
   • PCIUtility→Diagnostic→Noise Level: confirm whether environment is normal
   • PCIUtility→Diagnostic→System Reference: perform calibration
5. If the item “4” tests fail or problems persist, please retrieve the log file from Debug→Log Current Device Information and send it to AMT for analysis.

COF(ZIF)

1. Go to task manager to confirm whether device is connected.
   If device has not been acquired, please confirm the following items:
   • Confirm connection between touch panel and mother board: clean the pin connector with an eraser and reconnect the control board.
   • Confirm whether driver version is correct.
   • Confirm whether operating voltage meets Controller Board Datasheet requirements.
2. If task manager acquire the device, start PCIUtility to see whether the device is recognized.
3. If PCIUtility does not recognize device, firmware settings may be different than the interface in use. Please refer to the Controller Board Datasheet to correct hardware settings.
4. When PCIUtility recognizes the device, please confirm the following items:
   • PCIUtility→Diagnostic→open-short: confirm whether panel is normal
   • PCIUtility→Diagnostic→Noise Level: confirm whether environment is normal
   • PCIUtility→Diagnostic→System Reference: perform calibration
5. If the item “4” tests fail or problems persist, please retrieve the log file from Debug→Log Current Device Information and send it to AMT for analysis.

Control Board

1. Go to task manager to confirm whether device is connected.
   If device has not been acquired, please confirm the following items:
   • Confirm whether the cable connection is normal.
   • Confirm cable: please replace cable.
   • Confirm cable and control board connection: confirm whether control board probe is crooked.
   • Confirm touch panel and control board connection: clean the pin connector with an eraser and reconnect the control board.
   • Confirm whether operating voltage meets Controller Board Datasheet requirements.
2. If task manager acquire the device, start PCIUtility to see whether the device is recognized.
3. If PCIUtility does not recognize device, firmware settings may be different than the interface in use. Please refer to the Controller Board Datasheet to correct hardware settings.
4. When PCIUtility recognizes the device, please confirm the following items:
   • PCIUtility→Diagnostic→open-short: confirm whether panel is normal
   • PCIUtility→Diagnostic→Noise Level: confirm whether environment is normal
   • PCIUtility→Diagnostic→System Reference: perform calibration
5. If the item “4” tests fail or problems persist, please retrieve the log file from Debug→Log Current Device Information and send it to AMT for analysis.

COF(ZIF)

1. Go to task manager to confirm whether device is connected.
   If device has not been acquired, please confirm the following items:
   • Confirm connection between touch panel and mother board: clean the pin connector with an eraser and reconnect the control board.
   • Confirm whether driver version is correct.
   • Confirm whether operating voltage meets Controller Board Datasheet requirements.
2. If task manager acquire the device, start PCIUtility to see whether the device is recognized.
3. If PCIUtility does not recognize device, firmware settings may be different than the interface in use. Please refer to the Controller Board Datasheet to correct hardware settings.
4. When PCIUtility recognizes the device, please confirm the following items:
   • PCIUtility→Diagnostic→open-short: confirm whether panel is normal
   • PCIUtility→Diagnostic→Noise Level: confirm whether environment is normal
   • PCIUtility→Diagnostic→System Reference: perform calibration
5. If the item “4” tests fail or problems persist, please retrieve the log file from Debug→Log Current Device Information and send it to AMT for analysis.

A. Basic Testing
i.Confirm firmware version.
ii.PCIUtility→Diagnostic→open-short: confirm whether panel is normal
iii.PCIUtility→Diagnostic→Noise Level: confirm whether environment is normal
iv.PCIUtility→Diagnostic→System Reference: perform calibration

B. Adjust edge compensation parameters: PCIUtility→Coordinate→Edge Compensation
C. If line drawing is still impossible after performing steps “1” & “2” please provide entire system assembly diagram (including relative LCM position) to AMT.

The interface provided by PenMount control board is RS232 signal, and a RS485 (RS422) to RS232 signal adapter should be used for communication.

If using mouse type, the double click tolerance range and speed should be adjusted to larger values. Reinstalling the device driver could fix this issue.