Free device software for linux

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::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::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);

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.

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::ISO9660 is a Perl module for ISO 9660 handling.

SYNOPSIS

This encapsulates IS9660 filesystem handling. This library however needs to be used in conjunction with Device::Cdio, Device::Cdio::ISO9660::IFS and Device::Cdio::ISO::FS.

use Device::Cdio::ISO9660;
$name = Device::Cdio::ISO9660::name_translate(COPYING.;1);
$bool = Device::Cdio::ISO9660::is_achar(A);

This is an Object-Oriented Perl interface to the GNU CD Input and Control librarys ISO 9660 library, libiso9660.
Encapsulation is done in two parts. The lower-level Perl interface is called perliso9660 and is generated by SWIG.

The more object-oriented package Device::Cdio::ISO9660 and uses perliso9660. Actually, there are no objects in Device::Cdio::ISO9660, but there are in its sub packages Device::Cdio::ISO9660::IFS, Device::Cdio::ISO9660::FS (and in the future Device::Cdio::ISO9660::PVD).

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