The side entry is best suited for mounting the device on a surface. Flash on time tunable offline. This option includes a micro usb connector that allows the USB cable to pass thru the mounting pole. AppSettings “TfsProject”. It requires Node 4. Buzzer repeat count tunable offline. Delcom Products – USB Visual Signal Indicator Lights.
- 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
Comments are closed.
Need a Bluetooth Driver for your accessory? If you are having Bluetooth trouble, updates should be available through Microsoft's Windows Update service. If drivers were not downloaded automatically by Windows Update, use Device Manager to refresh the driver from Windows Update, or contact the device manufacturer. The latest USB drivers for various Omron devices can be found in the myOMRON Downloads section.You must be a registered user to access this area. The drivers for each device can be found in the following sub-folders. It is highly recommended to always use the most recent driver version available. Try to set a system restore point before installing a device driver. This will help if you installed an incorrect or mismatched driver. Problems can arise when your hardware device is too old or not supported any longer. 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.
Here at ACCES we pride ourselves on our commitment to service. If you can't find what you're looking for below, please, contact us.
Drivers & Software
The best way to find your updated driver and software package is to navigate to the specific product page (starting with the product category, in the menu / navigation side-bar to the left.)
The packages are listed on each product's page, both in the 'Manuals / Software' tab, and in the navigation side-bar to the left.
You can also use the Latest Driver / Software Package Installer List.
USB | PCI | PCIe | mPCIe | Wireless | PC/104 |
---|---|---|---|---|---|
Misc | Serial Converter | DAQ PACK | Ethernet | PCMCIA | Remote ACCES |
The Software Packages include Windows Drivers (32- and 64-bit), Samples, Utilities, Documentation, etc.
We also provide a Driver Only package, for production deployment.
All of these packages are redistributable .EXEs, and don't require an internet connection to be installed (nor during use).
Download Delcom Products Usb Devices Driver Updater
Supported Windows Versions
ACCES supports every version of Windows we can. The packages described above support retail and OEM versions of every edition of Windows from XP through 10 including the Embedded Standard editions (XPe, Win7ES, Win8ES, etc.) and all the related Server editions (Windows 2008R2 etc), in both 64-bit and 32-bit. The packages also include limited support for Windows 98se, Windows 95, Windows 3.11 for Workgroups, and DOS, for older products.
We also provide macOS, DOS, and VxWorks 7 software and drivers, for some products or product families — as well as others upon request, just ask us. Keep scrolling down for more details about our non-Windows software.
Operating Systems Supported
All our software supports both 32-bit (x86) and 64-bit ('x64', AMD64) versions of the following Windows operating systems.
Supported Windows desktop / client versions
- Windows 10
- Windows 8, 8.1
- Windows 7*
- Windows Vista*
- Windows XP*
Supported Windows Server versions
- Windows Server 2016
- Windows Server 2012 R2
- Windows Server 2012
- Windows Server 2008 R2*
- Windows Server 2008*
- Windows Server 2003 R2*
* Note: Windows versions prior to the NT6.2 kernel (prior to Windows 8 and Server 2012) are not recommended for use in new applications due to lack of support from Microsoft. ACCES will continue supporting them, until we cannot.
Linux, macOS, and more
ACCES provides Linux drivers primarily via our git repositories. The following are just a few examples of what's available:
- AIOUSB library and documentation, including how to use .rules files to get fxload to automatically load the device's firmware when the USB cable is connected
- APCI library and documentation, including support for register and IRQ access from userland applications
- PCI Express Serial documentation, including how to configure individual ports for RS232/422/485 modes (on supporting hardware)
The Linux software for some products is available on those product pages (under the Manuals / Software tab, and in the navigation column to the left.)
If you would like the Linux software package for any product and do not see it on the specific product's page, please call us
VxWorks
Among the many RTOS only one stands above the rest: VxWorks by Wind River® — 'Wind River VxWorks is an embedded Real Time Operating System (RTOS) that focuses on scalability and modularity. Kernel profiles allow customization specific to the needs of an organization whether it be safety, security or graphics. Kernels can be 32-bit or 64-bit and can be built to provide Symmetrical Multiprocessing (SMP) or Asymmetrical Multiprocessing (AMP) where supported.
Visit our Wind River partner page for more information about our VxWorks offerings.
Download Delcom Products Usb Devices Drivers
LabVIEW
ACCES has VIs for LabVIEW 5 through 7, and 8.5, for most of our products, and USB boards have VIs demonstrating use in LabVIEW 8.5 through 2013. You can find the drivers for LabVIEW 5 through 7 in the /Drivers/LabVIEW directory on the Software Master CD. The LabVIEW 8.5+ drivers are available in the /Drivers/LabVIEW 8.5+ directory on the CD, and on the products' pages, both in the Manuals / Software tab, and in the navigation column to the left.
For your convenience, the two major LabVIEW packages are available here:
- USB devices (other than serial ports)
- Register-based cards (other than serial ports). This includes ISA, PC/104, PCI, PCI Express, and all related devices with I/O register address ranges.
- Serial devices are supported directly by the Operating System and LabVIEW itself.
Download Delcom Products Usb Devices Driver Windows 10
Supported Legacy Versions
- 7.9 Driver Package
This is primarily useful for USB products. The later USB drivers are mainly not a bugfix, but exist to add 64-bit Windows support. Further, it can be tricky to move from 7.x to 8.x or 9.x. So, you can continue using 7.x drivers via this package, which does include any bugfixes.
Please note: ACCES USB devices invented after January 2001 are not supported by this package. (contact us if you need support added. We're here to help you succeed.) - 8.10 Driver Package
This is the oldest supported driver with 64-bit support. Notably, USB products use Microsoft WinUSB.dll in this version, instead of CyUSB.dll (in the 9.x drivers), or CyUSB3.dll (in the 10.x, current, driver package)
- 9.63 Driver Package
This is the most recent driver using CyUSB to interface to USB devices (the current '10.x' drivers use CyUSB3 instead). Some customers have reported problems installing the 10.x drivers on some Windows XP systems: the 9.63 Driver Package should be used in those situations.
Datasheets / Manuals
To find your updated manual and/or datasheet, please navigate to the specific product page (starting with the product category, in the left NAV bar).
The manuals and datasheets are listed on each product's page, both in the 'Manuals / Software' tab, and in the navigation column to the left.
Download Delcom Products Usb Devices Driver Download
Other, Unusual, or Rare Downloads
The following software applies to just a few models we produce. Most customers looking for software for our cards should click the product packages link, or download the software from the product's page, itself.
USB Serial Adapter Drivers for Windows
This section applies to the following serial communication models:
- USB-485
- USB-422
- USB-232
- USB-COM-4S
- USB-COM-4SM
- USB-COM232-4
- USB-FLEXCOM4
- USB-COM232-4A
Our 9.x Driver release supports all relatively recent revisions of these devices.
Download Delcom Products USB Devices Driver
Significantly older versions of the hardware may require older versions of the driver, which can be downloaded here, here, here and here.
To install the older, '.zip' driver package:
- Unzip the package.
- Uninstall the card from Device Manager if it's already installed. To get to Device Manager in 98 / ME, right-click on My Computer, choose Properties, then choose the Device Manager tab. To get to Device Manager in 2000 / XP, right-click on My Computer, choose Properties, choose the Hardware tab, then click Device Manager. The card will be in the Multifunction Adapters and/or Ports categories.
- Click Refresh in Device Manager to re-detect the card. Choose Search For The Best Driver, then check only Specific Location, and enter the location to which you unzipped the package.