usb device

Device::USB::FAQ Perl module contains Frequently Asked Questions for Device::USB.

This is an attempt to answer some of the frequently asked questions about the Device::USB module.

Which platforms does Device::USB support?

Device:USB supports any platform that libusb supports. This list currently includes Linux, FreeBSD, NetBSD, OpenBSD, Darwin, and MacOS X.

There is a port of the libusb library to the Windows environment called LibUsb-Win32. Because I dont have a development environment for testing this library, Device::USB does not yet support this library.

Do I have to use Device::USB as root?

By default, access to the USB devices on a Unix-based system appear to be limited to the root account. This usually causes access to most of the libusb features to fail with a permission error.

Using the Device::USB module as root avoids this feature, but is not very satisfying from a security standpoint. (See the next question for more options.)

How do I enable use of Device::USB as a non-root user?

Some of the attributes of USB devices are available to non-root users, but accessing many of the more interesting features require special privileges. According to the libusb source, the open() function requires either device nodes to be present or the usbfs file system to be mounted in specific locations. Those places in order are:

1)
/dev/bus/usb - pre-2.6.11: via devfs / post-2.6.11: via udev
2)
/proc/bus/usb - usbfs

Look in both locations on your system for which of these two methods your libusb will use.

No matter which method your system uses, you will probably want to create a separate group to control access. Run this command to add a system group:

addgroup --system usb

or

groupadd --system usb

You can then add users to that group to allow access to your usb devices.

It is highly recommended to always use the most recent driver version available.
Do not forget to check with our site as often as possible in order to stay updated on the latest drivers, software and games.

Try to set a system restore point before installing a device driver. This will help if you installed a wrong driver. Problems can arise when your hardware device is too old or not supported any longer.

Since 1988, EXP Computer, Inc. has been manufacturing and marketing quality PC Card upgrades for notebook computer users. EXP was one of the first pioneer companies of PC Card technology offering a full line of portable PC Card CD-ROM kits, external hard drives, modems, ethernet adapters, and multi-function cards.

With over a decade of commitment in advance mobile computing technology, EXP is now expanding on its line of PC Card offerings by introducing USB to its highly successful multimedia, storage, networking, and communication products. Now, with EXPs diverse interface options (PCMCIA, USB, Parallel), notebook users will have the flexibility to use EXPs products with their notebook and desktop computers conveniently, completing their mobile computing office.

EXP is constantly on the cutting edge of technology in developing new products for the growing and ever changing notebook and PC Card market. EXP also is committed to living up to the high expectations that were established when the company was first founded: Bringing Quality and Innovative products to market before the competition.

Privately held, EXP is a multi-million dollar company with the office in New York. EXP is staffed with a full team of sales, engineering and support personnel. EXP also owns a state of the art manufacturing facility in Taiwan and also in partnership with a number of domestic assembly facilities. EXPs products are distributed and available worldwide.

It is highly recommended to always use the most recent driver version available.
Do not forget to check with our site as often as possible in order to stay updated on the latest drivers, software and games.

Try to set a system restore point before installing a device driver. This will help if you installed a wrong driver. Problems can arise when your hardware device is too old or not supported any longer.

Device Watchman Application includes two components: Device Watchman configuration tool to assign custom drive letters to all your USB devices and Device Watchman Windows Service to keep your drive assignments as you specify on any number of PCs.

When you insert your USB device will always get the same drive letter you have chosen in the configuration on all your PCs. The Device Watchman also executes any program or command you want to run on the device insertion or when the device is turned on.

Limitations:

· 15 Days Trial

Device::Serdisp is a Perl extension for talking to the serdisplib.

SYNOPSIS

use Device::Serdisp;

my $d = Device::Serdisp->new(USB:7c0/1501, ctinclud);
$d->init();
$d->clear();

# reserves a color-indexed picture
my $image = GD::Image->new(128,64);
my $black = $image->colorAllocate(0,0,0);
my $white = $image->colorAllocate(255,255,255);

$image->transparent($black);
$image->arc(10,10,10,10,0,270, $white);
$d->copyGD($image);

SysUtils Device Manager the removable device access control solution. Once SysUtils Device Manager is installed, administrators are able to control access to floppies, CDROMs, and other devices.

Also SysUtils Device Manager can protect network and local computers against viruses, trojan horses, and other malicious programs often introduced by removable media.

Developments in removable media technology are escalating. The newer versions of portable devices, such as flash memory, have been increasing in capacity and performance making them:

· Easy and fast to install.
· Capable of storing huge amounts of data.
· Physically small enough to carry in a pocket.

As a result, internal users may deliberately or accidentally:
· Expose confidential information.
· Introduce malicious code (e.g. viruses, trojans) which can bring the entire corporate network down.
· Make personal copies of company information and intellectual property.

In an attempt to control these threats organizations have started to prohibit the use of portable devices at work. The challenge with controlling devices attached to USB ports is to distinguish between devices that have a legitimate use and devices that may be of cause of concern for security reasons.

A simple solution could be to disable USB ports in the computer s BIOS and effectively disable all USB attached devices. However, this would also disable devices such as printers, pointing devices or keyboards.

SysUtils Device Manager provides the flexibility to control access on a per user basis to:
· External Storage Devices;
· CD-ROM/DVD Drives;
· Floppy Disks;
· Digital Cameras.

Every time the user wants to access a device, SysUtils Device Manager Agent intercepts this request at the kernel level of the operating system. SysUtils Device Manager Agent checks the user rights in the appropriate Access Control List (ACL). If the user does not have rights to access this device, an "access denied" error message is returned.

SysUtils Device Manager consists of two parts: the Agent (SysUtils Device Manager Agent Service) and the administration console.

SysUtils Device Manager Agent is installed on each client system, runs automatically, and provides device protection on the client machine while remaining invisible to that computers local users.

The administration console is the control interface that systems administrators use to remotely manage each system that has Device Manager Agent.

Limitations:

· 15 day trial

Device::Gsm is a Perl extension to interface GSM phones / modems.

SYNOPSIS

use Device::Gsm;

my $gsm = new Device::Gsm( port => /dev/ttyS1, pin => xxxx );

if( $gsm->connect() ) {
print "connected!n";
} else {
print "sorry, no connection with gsm phone on serial port!n";
}

# Register to GSM network (you must supply PIN number in above new() call)
$gsm->register();

# Send quickly a short text message
$gsm->send_sms(
recipient => +3934910203040,
content => Hello world! from Device::Gsm
);

# Get list of Device::Gsm::Sms message objects
# see `examples/read_messages.pl for all the details
my @messages = $gsm->messages();

Device::Gsm class implements basic GSM functions, network registration and SMS sending.

This class supports also PDU mode to send SMS messages, and should be fairly usable. In the past, I have developed and tested it under Linux RedHat 7.1 with a 16550 serial port and Siemens C35i/C45 GSM phones attached with a Siemens-compatible serial cable. Currently, Im developing and testing this stuff with Linux Slackware 10.2 and a Cambridge Silicon Radio (CSR) USB bluetooth dongle, connecting to a Nokia 6600 phone.

Please be kind to the universe and contact me if you have troubles or you are interested in this.

Please be monstruosly kind to the universe and (if you dont mind spending an SMS) use the examples/send_to_cosimo.pl script to make me know that Device::Gsm works with your device (thanks!).

Recent versions of Device::Gsm have also an utility called autoscan in the bin/ folder, that creates a little profile of the devices it runs against, that contains information about supported commands and exact output of commands to help recognize similar devices.

Be sure to send me your profile by email (if you want to), so I can add better support for your device in the future!

Device::Cdio::Device is a class for disc and device aspects of Cdio.

SYNOPSIS

use Device::Cdio::Device;
$d = Device::Cdio::Device->new(-driver_id=>$perlcdio::DRIVER_DEVICE);
$drive_name = $d->get_device();
($i_read_cap, $i_write_cap, $i_misc_cap) = $d->get_drive_cap();

$start_lsn = $d->get_first_track()->get_lsn();
$end_lsn=$d->get_disc_last_lsn();
$drc = $d->audio_play_lsn($start_lsn, $end_lsn);
($vendor, $model, $release, $drc) = $d->get_hwinfo();

Device::ParallelPort is a Parallel Port Driver for Perl.

SYNOPSIS

my $port = Device::ParallelPort->new();
$port->set_bit(3,1);
print $port->get_bit(3) . "n";
print ord($port->get_byte(0)) . "n";
$port->set_byte(0, chr(255));

A parallel port driver module. This module provides an API to all parallel ports, by providing the ability to write any number of drivers. Modules are available for linux (both directly and via parport), win32 and a simple script version.
NOTE - This actual module is a factory class only - it is used to automatically return the correct class and has not other intelligence / purpose.

DRIVER MODULES

NOTE - You MUST load one of the drivers for your operating system before this module will correctly work - they are in separate CPAN Modules.

L - Direct hardware access to a base address.
L - Linux access to /dev/parport drivers
L - Run a script with parameters
L - Pretending byte driver for testing
L - Pretending bit driver for testing
L - Windows 32 DLL access driver
DEVICE MODULES ^
L - An example that can talk to a printer
L - Simple JayCar electronics latched, addressable controller
L - SerialFlash of bits - useful for many driver chips

Device Control Device is a platform independent remote telescope and device control program compatible with the INDI standard (see http://indi.sourceforge.net/).

This program is a client (a user interface) and provides functions to control devices connected to a remote system that is running an INDI server.

The features and the structure of the GUI are similar to the Kstars INDI client. The only advantages are support for Windows and lower resource requirements.

Device::Cdio is a Perl module for CD Input and Control library.

SYNOPSIS

This encapsulates CD-ROM reading and control. Applications wishing to be oblivious of the OS- and device-dependent properties of a CD-ROM can use this library.

use Device::Cdio;
use Device::Cdio::Device;

@cd_drives = Device::Cdio::get_devices($perlcdio::DRIVER_DEVICE);
@cd_drives = Device::Cdio::get_devices_with_cap($perlcdio::FS_AUDIO, 0);
foreach my $drive (@cd_drives) {
print "Drive $driven";
}
foreach my $driver_name (sort keys(%Device::Cdio::drivers)) {
print "Driver $driver_name is installed.n"
if Device::Cdio::have_driver($driver_name) and
$driver_name !~ m{device|Unknown};
}

This is an Perl Object-Oriented interface to the GNU CD Input and Control library, libcdio, written in C. The library encapsulates CD-ROM reading and control. Perl programs wishing to be oblivious of the OS- and device-dependent properties of a CD-ROM can use this library.

The encapsulation is done in two parts. The lower-level Perl interface is called perlcdio and is generated by SWIG.
The more object-oriented package Device::Cdio and uses perlcdio. Actually, there are no objects in Device::Cdio, but there are in its sub packages Device::Cdio::Device and Device::Cdio::Tracks.

Although perlcdio is perfectly usable on its own, it is expected that Cdio is what most people will use. As perlcdio more closely models the C interface libcdio, it is conceivable (if unlikely) that die-hard libcdio C users who are very familiar with that interface could prefer that.

Device::SNP is a Perl extension for the GE Fanuc SNP-X serial protocol as used by GE Fanuc DataPanel data terminals. See http://www.gefanuc.com/en/ProductServices/VisPCSolutions/DataPanel/index.html

SYNOPSIS

use Device::SNP;

my $s = new Device::SNP::Slave(
Portname => /dev/ttyUSB0,
Debug => 0);
$s->run();
Amarok serial interface program: datapanel.pl [-h] [-d] [-p portdevice]
portdevice defaults to /dev/ttyUSB0

ABSTRACT

This Device::SNP module contains an implementation of the GE Fanuc SNP-X serial protocol as used by GE Fanuc DataPanel data terminals. See http://www.gefanuc.com/en/ProductServices/VisPCSolutions/DataPanel/index.html

DESCRIPTION

DataPanels are usually used with PLCs to monitor and control industrial equipment. They provide a programmable bitmap display, programmable function keys, and can poll and display data values and set data values in a remote PLC using the SNP-X serial protocol.

The Device::SNP::Slave object implements an SNP-X slave, opens a Device::Serial port and answers SNP-X requests to read and write data to a simulated PLC.
This package also contains a sample application that uses a DataPanel 160 to implement a remote control panel for the Amarok music player on Linux, allowing you to play, pause, next, prev tracks etc.

DataPanels are programmed with a GE application called DataDesigner, available from the GE web site for registered customers. Included in this package is a database for DataDesigner 5.2 for the Amarok remote control application. You will need DataDesigner 5.2 to download the datadesigner/linux.DTB database to the DataPanel 160

Tested on SuSE linux, but should run on pretty well any Linux or Unix.

Device::TNC is a Perl module that acts like a generic interface to a TNC.

This module implements a generic interface to a Terminal Node Controller (TNC).

It loads sub classes that provide the low level interface for the appropriate TNC to be used and provides higher level methods to return frames of data to the user is human readable form.

SYNOPSIS

use Device::TNC;
my $tnc_type = KISS;
my %tnc_config = (
port => ($Config{osname} eq "MSWin32") ? "COM3" : "/dev/TNC-X",
baudrate => 9600,
warn_malformed_kiss => 1,
raw_log => "raw_packet.log",
);
my $tnc = new Device::TNC($tnc_type, %tnc_config);
die "Error: Something went wrong connecting to the TNC.n" unless $tnc;

while (1)
{
my $data = $tnc->read_frame();
my $repeaters = join ", ", @{$data->{ADDRESS}->{REPEATERS}};
my $info = join "", @{$data->{INFO}};
print "From: $data->{ADDRESS}->{SOURCE} ";
print "To: $data->{ADDRESS}->{DESTINATION} ";
print "via $repeatersn";
print "Data: $infon";
}
new()
my $type = "KISS";
my %tnc_data = { option => value };
my $tnc = new Device::TNC($type, %tnc_data);

The new method creates and returns a new Device::TNC object that can be used to communicate with a Terminal Node Controller (TNC) of the type passed.

The method requires that the first passed argument be the type of TNC to connect to. This will try and load the appropriate module for the TNC type.
The subsequent options are passed to the module that is loaded to connect to the desired TNC.

For more details on these options see the module documentation for the TNC type.

read_frame()
my $frame_data = $tnc->read_frame();
my %frame_data = $tnc->read_frame();

This method reads a HDLC frame from the TNC and returns a structure as either a hash or a hash reference that contains the fields of the frame.

The structure of the returned data is like the following.

{
INFO => [
/, 0, 6, 4, 6, 5, 8, h, 3, 3, 5, 0, ., 0, 0,
S, \, 1, 5, 1, 1, 2, ., 0, 0, E, O, 2, 2, 6,
/, 0, 0, 0, /, A, =, 0, 0, 0, 1, 1, 1
],
PID => F0,
CONTROL => {
POLL_FINAL => 0,
FIELD_TYPE => UI,
FRAME_TYPE => U
},
ADDRESS => {
DESTINATION => APT311,
REPEATERS => [
WIDE1-1,
WIDE2-2
],
SOURCE => VK2KFJ-7
}
}

While developing this module I only received U (UI) type frames and so development of the code to work with I and S frames didnt really progress. If anyone wants to read I or S frames please let me know and Ill have a look at implementing them. Please create a KISS log of the data and email it to me.

Device::Audiotron provides a tie-in into the API included in the latest firmware for Voyetra Turtle Beachs Audiotron.

SYNOPSIS

use Device::Audiotron; $at = new Device::Audiotron("Audiotron IP address","username","password"); if(!$at){die "Audiotron object failed to initialize.";}
my ($ref_status, $ref_shares, $ref_hosts) = $at->GlobalInfo(); my $firmware_version = $ref_status->{"Version"};

Device::Audiotron provides a tie-in into the API included in the latest firmware for Voyetra Turtle Beachs Audiotron.

I highly suggest reading through the API documentation located at http://www.turtlebeach.com/site/products/audiotron/api/dl_api.asp before attempting to implement this module.

The available methods for the Audiotron object and an example of usage for each are listed below. The native API call is listed in brackets below each method for informational purposes and for ease in referencing Voyetras API documentation.

GetInfo(Type,[Count],[Criteria])
[Apigetinfo.asp]

Returns a string containing the results from the command request.

$type = "Global";
$info = $at->GetInfo($type);

OR

$type = "artist";
$count = 4;
$criteria = "Staind";
$info = $at->GetInfo($type,$count,$criteria);


Qfile(Type,Criteria)
[Apiqfile.asp]

Returns a string containing the results from the command request.

$type = "File";
$file = q|LITHIUMMP3BushdeconstructedComedown.mp3|;
$cmd_result = $at->Qfile($type, $file);


AddFile(Full_File_Name)
[Apiaddfile.asp]

Returns a string containing the results from the command request.

$file = q|COBALTMP3new_song.mp3|;
$cmd_result = $at->AddFile($file);


Cmd(Command,[Arg])
[Apicmd.asp]

Returns a string containing the results from the command request.

$cmd_name = "play";
$cmd_result = $at->Cmd($cmd_name);

OR

$cmd_name = "goto";
$cmd_arg = "18";
$cmd_result = $at->Cmd($cmd_name, $cmd_arg);


GetStatus()
[Apigetstatus.asp]

Returns a hash containing element names equivalent to the field names returned by the Audiotron.

%status = $at->GetStatus();
print $status{State};


GlobalInfo()
[See GetInfo]

Returns references to a hash, an array, and an array of hashes.

This is simply a call to GetInfo with "Global" passed as the type but has been customized to pre-parse the results.

($ref_status, $ref_shares, $ref_hosts) = $at->GlobalInfo();

In the above example $ref_status is a reference to a hash containing element names equivalent to the field names returned from the "status" portion of the results. So for example, to get the version number of the firmware:

$firmware_version = $ref_status->{"Version"};

Next, $ref_shares is a reference to an array where each element contains the UNC name for the share as listed in the Audiotron.

Lastly, $ref_hosts is a reference to an array of hashes, one hash per host known by the Audiotron. Each hash in the array contains three elements named Host,IP, and State. So for example, to get the IP address of the first host in the array:

$ip_add = $ref_hosts->[0]->{"IP"};


Msg(Text_line1,[Text_line2],[Timeout])
[Apimsg.api]

Returns a string containing the results from the command request.

$line1 = "This is a test.";
$line2 = "Just Another Perl Hacker";
$time_out = "5";
$cmd_result = $at->Msg($line1, $line2, $time_out);


DumpToc(Share_name)
[Apidumptoc.asp]

Returns a (sometimes huge!) string containing the results from the command request.

$share = q|LITHIUMMP3|;
$toc = $at->DumpToc($share);

NOTE:

This is here just as a placeholder, newer versions will allow the output to be written to a file instead of be handed back as a string. Very inefficient in its current form.

Transfer to Media Device is a script that creates a new Playlist Right Click Menu item for transferring selected playlist items to your iPod via the Media Device Browser.

This script now also supports generic copy to operation for USB mass storage devices. Currently the script will prompt for a destination directory on first copy, in the future this setting will be saved in a configuration file.

This script works with amaroK 1.3beta3 and above.

Usage:

Run from the amaroK script manager. A new menu item will appear in the Playlist right mouse button menu.

Select files in the playlist and Right click -> Transfer to -> iPod for transfering to an iPod.

Select files in the playlist and Right click -> Transfer to -> USB Device for transfering to a USB device.

Whats New in This Release:

· Add support for Creative Nomad Jukebox devices using the kionjb kioslave. Thanks to Ralf T for the patch.

DVD Device Lock description
Hide or disable access to removable devices like CD, DVD, floppy, flash, USB. DVD Device Lock is a program used to restrict read or write access to removable media devices such as CD, DVD, floppy, flash and USB drives.

You can also restrict access to partitions of hard disk drives. You are given two choices when you secure your data: you can hide your devices or lock access to them.

Access password has to be entered to gain access to the devices back.

DVD Device Lock is designed in such way that it will never endanger your protected data.

If you lose or forget your password, youll never lose your data stored on the protected media. Moreover, it works much more faster than any other software using cryptooperation mechanisms.

The main purpose of DVD Device Lock is to restrict an ability of copying data between removable media and hard disk drives. You can also deny access to the media itself.

DVD Device Lock also allows you to avoid many of headaches connected with unauthorized software installations from any removable media and it prevents data leaks through removable media.

DVD Device Lock can help you to control access to device drives with file system to avoid most of risks of copying data to/from your PC.

Here are some key features of "DVD Device Lock":

· Instantly prompts a password when device drive is accessed.
· Password and data recovery mechanisms are available.
· Hides/locks any device drives with any file system.
· Keeps your device drives hidden/locked even in the Safe Mode.
· Very easy-to-learn and easy-to-configure.
· You do not have to reboot your system after you apply the new settings.
· The program can handle read-only device drives.


Limitations:

· 30 days trial