Unable to compile uinput module on cRIO 9030

[BradM]

Where did you download the driver from? This will be the single biggest assistance.

As far as lsusb:

opkg update

opkg install lsusb

lsusb -v

You should probably try to find someone who's a bit more familiar with Linux, especially working with the kernel at your business or school. A few issues I've noted with your commands:

• Don't try to directly execute source .c files, that's not how to use them.
• Unsure what you were trying to do with "./module", but again, that's not a valid command here. It seems that's a kernel build makefile component, based on the errors that are returned from attempting to run that as a script.
• You need to configure the kernel to build the uinput module, not just try to go to the directory that contains the driver and call "make"

[Reji.V]

Hi BradM & m-power,

      The problem was solved. The driver for the PALAS touchscreen monitor was not required..I solved the problem by calibraring the touch number of times until the arrow comes to the position where i m touching..

Thanq you very much for your reply..

[m-power]

I'm very pleased that you also have solved the problem..

[BradM]

Reji.V wrote:

Hi BradM & m-power,

      The problem was solved. The driver for the PALAS touchscreen monitor was not required..

...

This, I suspect, is really the biggest issue that we have to face: when are the provided (and often outdated) drivers from the vendor needed or will the basic evdev support work (basic meaning included, it's a fairly complete driver).

I'm glad to see you got things working and it simply required running the calibration tool a few times.

[rha25]

Hi everybody

I am running a NI-IC3120 with linux-rt, and I am using a touchscreen from iTech which uses eGalaxTouch driver.

Following the helps of this thread I've been able to rebuild the kernel to insert the proper driver supports, and now the touchscreen works through the USB interface (many thanks to everybody for this!!!).

Everything is fine, except that I was using the RAD utility to download system images from/to the IC3120. That stopped working... the RAD utility version should be 14.0.0

Does anybody ever faced this?

Thanks

[BradM]

More recent kernels (I think from RIO 16.0 or later) do not require extra modules or rebuilding the kernel. What version of the OS (as reported by MAX) are you using?

[rha25]

Thanks for the reply first.

From the shell I get:

admin@NI-IC-3120-01C370D9:~# uname -a
Linux NI-IC-3120-01C370D9 4.1.15-rt17-g7b45851-dirty #6 SMP PREEMPT RT Tue Aug 29 10:50:29 UTC 2017 x86_64 GNU/Linux

The NI-MAX I get the same information, plus I know a "firmware version" equal to 4.0.0f0

I can make another attempt, restoring the initial configuration if you think it could be the solution 🙂

Thanks

[rha25]

Update on this: I've used a brand-new IC-3120

1. on the first power-on, the touch wasn't working
2. I've installed the device drivers version 16 on it, but still not working
3. I've tried the install of eGalaxTouch driver from here for the kernel 2.6.24 and upwards (is it correct?) following the "patches" described in this discussion, the setup.sh closes nicely, but then no touch after rebooting
4. I've also ran updateNIDrivers on the second attempt but still, the touch doesn't accept the click event, only the mouse pointer moves

Following, the list of software of the package I've installed with NI-MAX

NI Industrial Controller 16.0 - August 2016

Industrial Controller Monitoring Support 16.0.0
Industrial Controller Support 16.0.0
LabVIEW Real-Time 16.0.0
NI System Configuration 16.0.0
NI System Configuration Remote Support 16.0.0
NI-RIO 16.0
Run-Time Engine for Web Services 16.0.0
SSL Support for LabVIEW RT 16.0.0
WebDAV Server 16.0.0

Available add-ons:
HTTP Client with SSL Support 16.0.0
Hardware Configuration Web Support 16.0.0
I/O Variable Remote Configuration Web Service 16.0
Language Support for Japanese 16.0.0
Language Support for Simplified Chinese 16.0.0
Legacy FTP Server (deprecated) 1.3.0
NI Application Web Server 16.0.0
NI Scan Engine 5.0
NI Vision-RIO 16.0.0
NI Web-based Configuration and Monitoring 16.0.0
NI Wireless Certificate Management Web Service 3.0
NI-RIO IO Scan 16.1.1
NI-VISA 16.0.0
NI-VISA ENET Passport 16.0.0
NI-VISA ENET-ASRL Passport 16.0.0
NI-VISA PXI Passport 16.0.0
NI-VISA Remote Passport 16.0.0
NI-VISA Server 16.0.0
NI-VISA USB Passport 16.0.0
NI-Watchdog 16.0.0
Network Configuration Web Support 16.0.0
Remote Panel Server for LabVIEW RT 16.0.0
SMTP Client with SSL Support 16.0.0
Software Management Web Support 16.0.0
System State Publisher 4.0.0
Time Configuration Web Support 16.0.0
Variable Legacy Protocol Support 5.8.0
Variable Legacy Server Support 5.8.0
WebDAV Client with SSL Support 16.0.0

Unavailable add-ons:
Network Variable Engine 16.0.0 (not available on host)
EPICS Client I/O Server 16.0.0 (not available on host)
GigE Vision Camera Support 16.0.0 (not available on host)
NI-Industrial Communications for EtherCAT 16.0 (not available on host)
NI Vision RT 16.0.0 (not available on host)
Network Streams 16.0 (not available on host)
Modbus I/O Server 16.0.0 (not available on host)
IP Camera Support 16.0.0 (not available on host)
NI-Industrial Communications for EtherNet/IP 16.0.0 (not available on host)
NI-IMAQdx 16.0.0 (not available on host)
DataSocket for LabVIEW Real-Time 5.4.0 (not available on host)
USB3 Vision Support 16.0.0 (not available on host)
NI-TimeSync Time Reference for IEEE 1588-2008 16.0.0 (not available on host)
EPICS Server I/O Server 16.0.0 (not available on host)
USB Webcam Support 16.0.0 (not available on host)
LabVIEW Control Design and Simulation 16.0 (not available on host)
Variable Client Support for LabVIEW RT 16.0.0 (not available on host)
LabVIEW SoftMotion Module 16.0.0 (not available on host)
OPC UA Client API 16.0.0 (not available on host)
OPC UA Server API 16.0.0 (not available on host)

Is there maybe some package I am missing through opkg system? Something I can check?

[BradM]

"Touch working for mouse movements but not for clicks" is an Xorg misconfiguration issue, I recall. Check the Xorg log, xinput --list --long output, and the output of xev.

I'm a little surprised that the default 16.0 kernel did not work (I have one particular eGalax touchscreen at my desk that worked without issue with the 2016 kernel). Can you post the result of running lsusb with the touchscreen plugged in (you will need to install it first, opkg install usbutils).

This sort of issue, unfortunately, takes a bit of work, debugging, and troubleshooting since the manufacturer usually doesn't spend too much time and effort in Linux support. If there's anything, it's only for primary distributions (this is in contrast to working with the upstream community to get support for their device in the upstream source of the various components)

[rha25]

I am attaching the result of the xinput --list and lsusb -v here, as you can see the single USB plug creates 2 devices:

1. eGalax Inc. USB TouchController
2. eGalax Inc. USB TouchController Pen

I ran:

xinput test <device name>

using the two device names upthere, while I can see ouptut for the first one (both dragging and clicking) the second one produces no output at all.

Before rebuilding the kernel, last week, I've been playing for some time with /etc/X11/xorg.conf (which was already modified by the setup.sh in eGalax package) but I didn't succeed, eventually I also broke it so the pointer stopped working.

Maybe I am missing something from the two file attached?

I also read somewhere in this forum that from the two devices listed above I should blacklist the one which is not producing output. I remember to be trying that as well, but no success.