display device

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::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 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::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 <device::parallelport::drv::linux> device::parallelport::drv::linux> - Direct hardware access to a base address.
L <device::parallelport::drv::parport> device::parallelport::drv::parport> - Linux access to /dev/parport drivers
L <device::parallelport::drv::script> device::parallelport::drv::script> - Run a script with parameters
L <device::parallelport::drv::dummy_byte> device::parallelport::drv::dummy_byte> - Pretending byte driver for testing
L <device::parallelport::drv::dummy_bit> device::parallelport::drv::dummy_bit> - Pretending bit driver for testing
L <device::parallelport::drv::win32> device::parallelport::drv::win32> - Windows 32 DLL access driver
DEVICE MODULES ^
L <device::parallelport::printer> device::parallelport::printer> - An example that can talk to a printer
L <device::parallelport::jaycar> device::parallelport::jaycar> - Simple JayCar electronics latched, addressable controller
L <device::parallelport::serialflash> device::parallelport::serialflash> - SerialFlash of bits - useful for many driver chips

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::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::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::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.

Display is a reliable program that will display the quoted parameter as text in a window on screen. It will wait until the OK button is pushed.

Specially created to facilitate PC-administrators to build smooth scripts or logon procedures.

With PromOffice Device Registrar you can build and maintain a database of measuring devices, allowing effectively to serve all complex of devices and to analyze its condition. PromOffice Device Registrar contain: device account ; device types; routine maintenance information; annual reports and charts; malfunctions; logs: shift/service/edit.

Device Checker allows you to define which device will be authorised to be connected to your PC or laptop. As soon as you have identified and authorised the device you whish to use, any other device is denied by default. The technology used is patented by MobileGov in Europe and in the United Stated. MobileGov Device Checker enforce your sensitive data security and gives you the control of the use of any internal or external device on you computer.

SysUtils Device Manager - the removable device access control solution. Once SysUtils Device Manager is installed, administrators can 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. 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 works on any computer using Windows 2000/XP or Windows Server 2003. To install and control SysUtils Device Manager, you must have administrative privileges.

With PromOffice Device Registrar you can build and maintain a database of measuring devices, allowing effectively to serve all complex of devices and to analyze its condition.

PromOffice Device Registrar contain: device account ; device types; routine maintenance information; annual reports and charts; malfunctions; logs: shift/service/edit.

PromOffice Device Registrar is a database builder and maintainer of measuring devices.

Here are some key features of "PromOffice Device Registrar":

· a lot of device attributes;
· popular MS Access (.mdb) database format, allowing data to export and to import;
· enable to filter, search, group the data;
· enable to make forecasts.


Limitations:

· This program is neither freeware nor public domain. Use after the 30 day trial period requires registration.

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::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.