- This topic has 1 reply, 1 voice, and was last updated 3 years, 4 months ago by .
Hello all!
For the last 3 days I have been beating my head against the wall trying to figure this out so any help would be much appreciated!
I have everything working – except for the buttons. I bought a USB HID Programable Quad Button Switch from Delcom to do certain things like make it rain, make it dry up, take a screen shot and remove the colors when the table is running:
http://www.delcomproducts.com/productdetails.asp?PartNumber=706504I programmed the Delcom (using a Windows box – ouch) so the buttons emulate Joystick Buttons.
I plugged the Switch into my Linux Mint box and although lsusb shows it, and some references to it show up in the various logfiles, it looks like the OS really doesn’t know what to do with it. Nothing shows up in /dev/input.
I tested the switch by plugging it into a raspberry pi and saw that the switch indeed shows up and creates an event in /dev/input/js0.
I’m running a pretty new version of Linux Mint:
Linux AugmentedRealityTable 4.8.0-58-generic #63~16.04.1-Ubuntu SMP Mon Jun 26 18:08:51 UTC 2017 x86_64 x86_64 x86_64 GNU/Linuxlsusb sees it:
peggy@AugmentedRealityTable /run/udev/data $ lsusb
device-enumerator: scan all dirs
device-enumerator: scanning /sys/bus
device-enumerator: scanning /sys/class
unable to receive message
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 007: ID 0bda:0153 Realtek Semiconductor Corp. Mass Storage Device
Bus 001 Device 006: ID 04ca:008a Lite-On Technology Corp.
Bus 001 Device 005: ID 0461:4e6f Primax Electronics, Ltd
Bus 001 Device 003: ID 0fc5:b080 Delcom Engineering
Bus 001 Device 008: ID 8087:0a2a Intel Corp.
Bus 001 Device 010: ID 045e:02bf Microsoft Corp. Kinect for Windows NUI Camera
Bus 001 Device 009: ID 045e:02be Microsoft Corp. Kinect for Windows NUI Audio
Bus 001 Device 004: ID 045e:02c2 Microsoft Corp. Kinect for Windows NUI Motor
Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hubBut /dev/input isn’t getting populated (I tried plugging it in and back out to see if anything was added or removed):
peggy@AugmentedRealityTable /run/udev/data $ ls /dev/input
by-id event0 event10 event12 event14 event3 event5 event7 event9 mouse0
by-path event1 event11 event13 event2 event4 event6 event8 micedmesg sees it as well:
[ 3798.490884] usb 1-3: New USB device found, idVendor=0fc5, idProduct=b080
[ 3798.490885] usb 1-3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 3798.490886] usb 1-3: Product: USB FS IO
[ 3798.490886] usb 1-3: Manufacturer: Delcom Products Inc.I’ve tried all sorts of udev rules.. here’s the one currently in play:
peggy@AugmentedRealityTable /etc/udev/rules.d $ cat 69-Sandbox.rules
SUBSYSTEMS”usb”, ATTR{idVendor}”0fc5″, ATTR{idProduct}”b080″, MODE=”0666″Also tried:
# Rule for Delcom quad switch
ACTION”add”, SUBSYSTEMS”usb”, ATTRS{idVendor}”0fc5″, ATTRS{idProduct}”b080″, TAG+=”uaccess”, TAG+=”udev-acl”Lots of reboots, lots of reloading of udev.
The software also refuses to see it:
Vrui: Initializing Vrui environment…InputDeviceManager: Ignoring input device adapter HIDAdapter due to exception InputDeviceAdapterHID::InputDeviceAdapterHID: No match for vendorId:productId “0fc5:b080” for device ButtonBox
OkI ran sudo update-usbids to make sure I had the most up to date USB ids.
I’m wondering if it’s a driver issue?
I really really don’t want to recompile the Linux kernel (either to downgrade or enable better debugging). I’m hoping that there is some other solution. I’m so sad. It is such a beautiful box and it’s so close to being ready to be delivered to school but we really do want these buttons to work.
ANY help is most appreciated. I really want to get this working for the elementary kids – they will love it!
Thanks again,
Peggy- Posts
Download Delcom USB IO Driver for Windows to uSB driver. Join or Sign In. Sign in to add and modify your software. Connect your Samsung mobile device to PC via USB port. Download drivers to communicate with NI products or third-party instruments. Delcom USB Visual Signal Device Delcom Visual Signal USB Driver USB ready computer running Win98, ME, Win 2000, or XP. Microsoft Visual C version 4.0 or better, or equivalent 32 bit compiler for x86 based system, or Visual basic compiler. Knowledge of C/C or Visual basic. Delcom DLL files and manual. The Delcom DLL allows simple integration between the Delcom USB devices. Delcom G1 Windows Drivers: Windows drivers for the Delcom G1 Products. Foot Switch VB Code: Foot Switch Visual Basic Sample Code: Google Go example: Google Go example on how to read the buttons on the Delcom USB input devices. HID C Example Code.
Comments are closed.
The new Intel Android* USB Driver package 1. 10.0 that supports Windows* 10 is available for download at the Intel Developer Zone. It enables you to connect your Windows*-based machine to your Android* device that contains an Intel® Atom™ processor inside. This includes the latest Intel® Atom™ x3 and x5 processor families (SoFIA devices are not supported in this version) and supported host systems with Windows* 10 (32/64-bit) and Android devices including those with Android* 5.x – Lollipop.
USB drivers for Android devices are platform-specific, and there is no guarantee that this Intel USB driver will work for every OEM device. Since most OEMs develop the USB driver for all devices that they sell, we recommend that you also check out the Android* OEM USB driver page that lists the OEM drivers.
This installation instructions document will guide you through installing the Intel® Android* USB Driver package which will enable you to connect your Windows* based machine to your Android device that contains an Intel® Atom™ processor inside.
Supported USB profiles
After installing the USB driver package, plug in your Android* device to your computer using your micro-USB to USB cable. The following are the supported USB profiles via the Intel Android USB Driver package:
- ADB (Android Debug Bridge): This is the debug interface of Android. It is mandatory to use in order to re-flash, and debug.
- MTP (Media Transfer Protocol): This is the Windows* protocol to facilitate the transfer of media files.
- PTP (Picture Transfer Protocol): This is the Windows* protocol to allow the transfer of images from digital cameras to computers.
- RNDIS: This provides a virtual Ethernet link using phone network.
- CDC Serial (Modem AT Proxy): This provides the link to Modem to allow to use AT commands through a virtual com port.
Troubleshooting Errors
Device is not recognized at all
These drivers are only for Intel® devices. If you’re using a device from one of our OEM, please get the drivers directly from their web site, or you can use this list of drivers on the Android* site.
Download Delcom Products Usb Devices Driver Updater
Errors in the Windows* Device Manager
Download Delcom Products Usb Devices Driver Windows 10
Open Windows Device Manager:
- If USB Mass Storage is visible instead of ADB Device, then right click on the Mass Storage device icon and select ‘Uninstall’.
Then unplug your device from the computer and install drivers’ setup again. - If Android Device is visible with a yellow warning icon, then right click on the Android Device icon and select ‘Uninstall’.
Then unplug your device from the computer and install drivers’ setup again.
Download Delcom Products Usb Devices Drivers
Portable Device that has no 'USB debugging' option
Download Delcom Products Usb Devices Driver Download
There may not be an enabled “USB Debugging” option. The developer options on a phone are hidden by default. Open the settings on a phone, and find the About section. Look through it until the 'Build number' entry is visible. Tap if five times in quick succession, and there should be a small dialog stating it’s now set to developer. Come back to Settings main menu and go into Developer Options, then enable USB Debugging.
Download Delcom Products USB Devices Driver
Windows XP: When I activate MTP there is no pop-up to allow me to access phone file system or transfer media files.
MTP is not supported by default with Windows XP. You have to install Windows Media Player 10 or later.