aduLogo.jpg (1752 bytes) LINUX SDK  

adutux - Installation

 

SDK Home
Installation
Application Programming Guide
Internal Details
Licensing

bang.gif (1007 bytes)Use at own risk

Use this program at your own risk. No warranty express or implied even as to merchantability. This driver is not supported by Ontrak Control Systems.
This is an experimental driver. You are responsible for testing it in your environment.

Binary Or Source Code

If you are lucky we have a pre-compiled binary module for your kernel release.
If not then you will have to compile the driver yourself.

Check the Binary Installation page to see if a binary driver module is available for your environment.

If not then you will have to Compile The Driver yourself.

Dependencies

  • module-init-tools (with updates for kernel 2.6.0)

    Warning: Read the module-init-tools installation instructions *CAREFULLY* before installing it. Your first install needs special parameters to ensure compatibility with prior modules.

    Device File System

    The adutux driver is not part of the official Linux kernel and thus has not been allocated any minor device numbers. We have unofficially borrowed the minor device numbers used by the Lego Tower. No problem.....unless you have a Lego Tower. The minor device numbers that we use are 179 through 188 inclusive.

    To add the /dev/usb/adutux device entries:

    cd to the /dev/usb directory.
    Create the device entries with the mknod command. 

        sudo mknod adutux0 c 180 179 
    sudo mknod adutux1 c 180 180 
    sudo mknod adutux2 c 180 181 
    sudo mknod adutux3 c 180 182 
    sudo mknod adutux4 c 180 183 
    sudo mknod adutux5 c 180 184 
    sudo mknod adutux6 c 180 185 
    sudo mknod adutux7 c 180 186 
    sudo mknod adutux8 c 180 187 
    sudo mknod adutux9 c 180 188

    Grant read/write permision on the /dev/usb/adutux0 to your users. 

        sudo chmod 666 /dev/usb/adutux*

    Plug the USB cable into your ADU device.
    Check the contents of /proc/bus/usb to ensure that the USB protocol stack detected the ADU device.
    If no entries appear then the host controller drivers must be started. (search the Web for an FAQ about this).

    USBFS Permissions

    add 3 lines to /etc/hotplug/usb.usermap so that adutux hotplug script gets associated with 0x0a07 and 0x0064,c8,d0 

    # usb module         match_flags idVendor idProduct >>additional fields
adutux               0x0003      0x0a07   0x0064
adutux               0x0003      0x0a07   0x00c8
adutux               0x0003      0x0a07   0x00d0

    Only the first 4 fields in each usb.usermap line contain significant data. All of the remaining fields in each line contain zeroes. Copy an existing line in the usb.usermap and modify to the values for the ADU devices that you plan to use.
    The first 4 fields are "usb module", "match_flags", "idVendor" and "idProduct". Thus we see that the usb.usermap will load the script adutux for idVendor=0x0a07, idProduct=(0x0064 | 0x00c8 | 0x00d0).

    Ontrak is planning additional products that are intended to be compatible with the adutux driver. Simply add a line to usb.usermap with the product id of the ADU device that you wish to use.

    add the adutux script to /etc/hotplug/usb directory 

        #!/bin/bash
    #
    # /etc/hotplug/usb/adutux
    # In the usermap file, the first field "usb module" should be named 
    # "adutux" like this script.
    chmod 0666 "${DEVICE}"

    Links

    Steven Haigh's Ontrak ADU-218 on Linux . Describes the steps to install the adutux driver on a Fedora Core distribution.