hardware and software
Sponsored Links
Sponsored Links
Secleted [ 0 ] software to compare
Results 1 - 15 of about 923
Hardware Monitor 1.4
Hardware Monitor is a multi-purpose, beautiful system-monitoring applet. more>>
Hardware Monitor is a multi-purpose, beautiful system-monitoring applet.
The Hardware Monitor applet is an applet for the GNOME panel which tries to be a beautiful all-around solution to system monitoring. It also strives to be user-friendly and generally nice and sensible, integrating pleasantly with the rest of your GNOME desktop.
Includes different viewers, including a flame effect, allows multiple devices to be monitored in the samme applet, uses smooth updating, polished graphs, clean HIG-compliant interface.
Main features:
- A graphical view where each monitor is represented by a (time, measurement) colored curve
- A bar-plot view with a horizontal bar per monitor
- A column view with a column (time, measurement) diagram for each monitor
- A textual view which simply lists the monitors and the currently measured values
- A flame view which produces spiffy flames, the sizes of which are determined by the values of the monitored device
And the applet supports monitoring the following hardware characteristics:
- CPU usage (all CPUs, or one at the time) - niced background processes such as SETI@home are automatically ignored
- Memory usage - cache and buffers are automatically ignored
- Swap usage
- Load average
- Disk usage (or disk space free)
- Network throughput (Ethernet, wireless, modem, serial link), either incoming or outgoing or both
- Temperatures from internal sensors (e.g. system board and CPU temperatures)
- Fan speeds from internal sensors
<<lessThe Hardware Monitor applet is an applet for the GNOME panel which tries to be a beautiful all-around solution to system monitoring. It also strives to be user-friendly and generally nice and sensible, integrating pleasantly with the rest of your GNOME desktop.
Includes different viewers, including a flame effect, allows multiple devices to be monitored in the samme applet, uses smooth updating, polished graphs, clean HIG-compliant interface.
Main features:
- A graphical view where each monitor is represented by a (time, measurement) colored curve
- A bar-plot view with a horizontal bar per monitor
- A column view with a column (time, measurement) diagram for each monitor
- A textual view which simply lists the monitors and the currently measured values
- A flame view which produces spiffy flames, the sizes of which are determined by the values of the monitored device
And the applet supports monitoring the following hardware characteristics:
- CPU usage (all CPUs, or one at the time) - niced background processes such as SETI@home are automatically ignored
- Memory usage - cache and buffers are automatically ignored
- Swap usage
- Load average
- Disk usage (or disk space free)
- Network throughput (Ethernet, wireless, modem, serial link), either incoming or outgoing or both
- Temperatures from internal sensors (e.g. system board and CPU temperatures)
- Fan speeds from internal sensors
Download (0.29MB)
Added: 2007-01-13 License: GPL (GNU General Public License) Price:
1037 downloads
X Hardware Monitor 1.0
X Hardware Monitor is monitor hardware indicators for temperature, voltage etc... of a running system with a graphical panel. more>>
X Hardware Monitor is a hardware monitor that shows indicators for temperature, voltage, fan speed etc, of a running system with a graphical panel.
The default configuration allows to monitor up to 3 temperatures, 3 fan speeds and 6 voltages. This tool is more particularly adequate for bi-processor systems.
<<lessThe default configuration allows to monitor up to 3 temperatures, 3 fan speeds and 6 voltages. This tool is more particularly adequate for bi-processor systems.
Download (0.015MB)
Added: 2005-09-22 License: Freeware Price:
1496 downloads
Hardware Monitor applet 1.4
The Hardware Monitor applet is a small program for the Gnome panel. more>>
Hardware Monitor applet is a small program for the Gnome panel which tries to be a beautiful all-round solution to hardware monitoring.
It also tries to be user-friendly and generally nice and sensible, integrating pleasantly with the rest of your Gnome desktop.
Main features:
- A graphical view where each monitor is represented by a (time, measurement) colored curve
- A bar-plot view with a horizontal bar per monitor
- A column view with a column (time, measurement) diagram for each monitor
- A textual view which simply lists the monitors and the currently measured values
- A flame view which produces spiffy flames, the sizes of which are determined by the values of the monitored device
And the applet supports monitoring the following hardware characteristics:
- CPU usage (all CPUs, or one at the time) - niced background processes such as SETI@home are automatically ignored
- Memory usage - cache and buffers are automatically ignored
- Swap usage
- Load average
- Disk usage (or disk space free)
- Network throughput (Ethernet, wireless, modem, serial link), either incoming or outgoing or both
- Temperatures from internal sensors (e.g. system board and CPU temperatures)
- Fan speeds from internal sensors
- To avoid eating CPU time when it is scarce, the applet lowers its priority.
<<lessIt also tries to be user-friendly and generally nice and sensible, integrating pleasantly with the rest of your Gnome desktop.
Main features:
- A graphical view where each monitor is represented by a (time, measurement) colored curve
- A bar-plot view with a horizontal bar per monitor
- A column view with a column (time, measurement) diagram for each monitor
- A textual view which simply lists the monitors and the currently measured values
- A flame view which produces spiffy flames, the sizes of which are determined by the values of the monitored device
And the applet supports monitoring the following hardware characteristics:
- CPU usage (all CPUs, or one at the time) - niced background processes such as SETI@home are automatically ignored
- Memory usage - cache and buffers are automatically ignored
- Swap usage
- Load average
- Disk usage (or disk space free)
- Network throughput (Ethernet, wireless, modem, serial link), either incoming or outgoing or both
- Temperatures from internal sensors (e.g. system board and CPU temperatures)
- Fan speeds from internal sensors
- To avoid eating CPU time when it is scarce, the applet lowers its priority.
Download (0.30MB)
Added: 2007-01-17 License: GPL (GNU General Public License) Price:
601 downloads
Hardware lister B.02.11.01
Hardware Lister is a small tool to provide detailed information on the hardware configuration of the machine. more>>
lshw (Hardware Lister) is a small tool to provide detailed information on the hardware configuration of the machine.
Hardware lister can report exact memory configuration, firmware version, CPU version and speed, cache configuration, bus speed, mainboard configuration, etc. On DMI-capable x86 or EFI (IA-64) systems and on some PowerPC machines (PowerMac G4 is known to work).
Information can be output in plain text, XML or HTML.
It currently supports DMI (x86 and EFI only), OpenFirmware device tree (PowerPC only), PCI/AGP, ISA PnP (x86), CPUID (x86), IDE/ATA/ATAPI, PCMCIA (only tested on x86), USB and SCSI.
<<lessHardware lister can report exact memory configuration, firmware version, CPU version and speed, cache configuration, bus speed, mainboard configuration, etc. On DMI-capable x86 or EFI (IA-64) systems and on some PowerPC machines (PowerMac G4 is known to work).
Information can be output in plain text, XML or HTML.
It currently supports DMI (x86 and EFI only), OpenFirmware device tree (PowerPC only), PCI/AGP, ISA PnP (x86), CPUID (x86), IDE/ATA/ATAPI, PCMCIA (only tested on x86), USB and SCSI.
Download (1.1MB)
Added: 2007-08-06 License: GPL (GNU General Public License) Price:
819 downloads
Hardware 4 Linux 0.9.3
Hardware 4 Linux project contains a set of tools to report Linux-compatible hardware to hardware4linux.info. more>>
Hardware 4 Linux project contains a set of tools to report Linux-compatible hardware to hardware4linux.info.
Enhancements:
- This release anonymizes dmidecode output, collects OS version files instead of calling osinfo, collects audio codec files, adds a README, and collects PCI modules.
<<lessEnhancements:
- This release anonymizes dmidecode output, collects OS version files instead of calling osinfo, collects audio codec files, adds a README, and collects PCI modules.
Download (MB)
Added: 2007-08-11 License: GPL (GNU General Public License) Price:
494 downloads
Hardware::Simulator 0000_0005
Hardware::Simulator is a Perl extension for Perl Hardware Descriptor Language. more>>
Hardware::Simulator is a Perl extension for Perl Hardware Descriptor Language.
SYNOPSIS
use Hardware::Simulator;
# NewSignal( perl_variable [, initial_value]);
# create a signal called $in_clk, give it an initial value of 1
NewSignal(my $in_clk,1);
# Repeater ( time_units , code_ref)
# every time_units, call the code reference, starting at the current time
Repeater ( 5, sub{if ( $in_clk==0) { $in_clk=1;} else { $in_clk=0;}});
# Responder ( [signal_name ... signal_name], code_ref );
# respond to any changes to signals by calling code reference.
# any time out_clk changes, print value of clock and simulation time.
Responder ( $out_clk, sub
{
my $time = SimTime();
print "out_clk = $out_clk. time=$timen";
});
# start processing of events and event scheduling.
EventLoop();
Hardware::Simulator ==> a Perl Hardware Descriptor Language
Hardware::Simulator is a lightweight version of VHDL or Verilog HDL. All of these languages were developed as means to describe hardware.
Hardware::Simulator was created as a means to quickly prototype a basic hardware design and simulate it. VHDL and Verilog are both restrictive in their own ways. Hardware::Simulator was created to quickly put something together as a "proof of concept", to show that a design concept would work or not. and then the design could be translated to VHDL or Verilog.
The problem that started all of this was designing a fifo for a video scaling asic. The chip used a buffer to store incoming video data. The asic read the buffer to generate the outgoing video image. We estimated how large we thought the buffer needed to be, but we wanted to confirm that our numbers were right by running simulations.
The problem was we needed to run hundreds of different simulations, given the permutations of input image formats, output image formats, and input/output clock frequencies. We also had text files containing valid formats and frequencies. A text file as input called for perl to manipulate, split, format, and extract the data properly.
This data then had to be translated onto the a HDL simulation. The problem was that there was no easy way to write a perl script that would simulate hardware, so the only solution was to have perl drive a Verilog simulator and pass all these parameters via command line parameters. so then verilog files had to be created, and the simulator had to be driven, and the end result was a lot of work to simulate a simple fifo.
Time contraints did not allow me to develop a HDL package for perl to solve the original problem, but I took it on in my spare time. and eventually Hardware::Simulator was born.
<<lessSYNOPSIS
use Hardware::Simulator;
# NewSignal( perl_variable [, initial_value]);
# create a signal called $in_clk, give it an initial value of 1
NewSignal(my $in_clk,1);
# Repeater ( time_units , code_ref)
# every time_units, call the code reference, starting at the current time
Repeater ( 5, sub{if ( $in_clk==0) { $in_clk=1;} else { $in_clk=0;}});
# Responder ( [signal_name ... signal_name], code_ref );
# respond to any changes to signals by calling code reference.
# any time out_clk changes, print value of clock and simulation time.
Responder ( $out_clk, sub
{
my $time = SimTime();
print "out_clk = $out_clk. time=$timen";
});
# start processing of events and event scheduling.
EventLoop();
Hardware::Simulator ==> a Perl Hardware Descriptor Language
Hardware::Simulator is a lightweight version of VHDL or Verilog HDL. All of these languages were developed as means to describe hardware.
Hardware::Simulator was created as a means to quickly prototype a basic hardware design and simulate it. VHDL and Verilog are both restrictive in their own ways. Hardware::Simulator was created to quickly put something together as a "proof of concept", to show that a design concept would work or not. and then the design could be translated to VHDL or Verilog.
The problem that started all of this was designing a fifo for a video scaling asic. The chip used a buffer to store incoming video data. The asic read the buffer to generate the outgoing video image. We estimated how large we thought the buffer needed to be, but we wanted to confirm that our numbers were right by running simulations.
The problem was we needed to run hundreds of different simulations, given the permutations of input image formats, output image formats, and input/output clock frequencies. We also had text files containing valid formats and frequencies. A text file as input called for perl to manipulate, split, format, and extract the data properly.
This data then had to be translated onto the a HDL simulation. The problem was that there was no easy way to write a perl script that would simulate hardware, so the only solution was to have perl drive a Verilog simulator and pass all these parameters via command line parameters. so then verilog files had to be created, and the simulator had to be driven, and the end result was a lot of work to simulate a simple fifo.
Time contraints did not allow me to develop a HDL package for perl to solve the original problem, but I took it on in my spare time. and eventually Hardware::Simulator was born.
Download (0.010MB)
Added: 2007-07-20 License: Perl Artistic License Price:
840 downloads
Hardware::Vhdl::Lexer 1.00
Hardware::Vhdl::Lexer is a Perl module that can split VHDL code into lexical tokens. more>>
Hardware::Vhdl::Lexer is a Perl module that can split VHDL code into lexical tokens.
SYNOPSIS
use Hardware::Vhdl::Lexer;
# Open the file to get the VHDL code from
my $fh;
open $fh, new({ linesource => $fh });
# Dump all the tokens
my ($token, $type);
while( (($token, $type) = $lexer->get_next_token) && defined $token) {
print "# type = $type token=$tokenn";
}
Hardware::Vhdl::Lexer splits VHDL code into lexical tokens. To use it, you need to first create a lexer object, passing in something which will supply chunks of VHDL code to the lexer. Repeated calls to the get_next_token method of the lexer will then return VHDL tokens (in scalar context) or a token type code and the token (in list context). get_next_token returns undef when there are no more tokens to be read.
NB: in this documentation I refer to "lines" of VHDL code and "line" sources etc., but in fact the chunks of code dont have to be broken up at line-ends - they can be broken anywhere that isnt in the middle of a token. New-line characters just happen to be a simple and safe way to split up a file. You dont even have to split up the VHDL at all, you can pass in the whole thing as the first and only "line".
<<lessSYNOPSIS
use Hardware::Vhdl::Lexer;
# Open the file to get the VHDL code from
my $fh;
open $fh, new({ linesource => $fh });
# Dump all the tokens
my ($token, $type);
while( (($token, $type) = $lexer->get_next_token) && defined $token) {
print "# type = $type token=$tokenn";
}
Hardware::Vhdl::Lexer splits VHDL code into lexical tokens. To use it, you need to first create a lexer object, passing in something which will supply chunks of VHDL code to the lexer. Repeated calls to the get_next_token method of the lexer will then return VHDL tokens (in scalar context) or a token type code and the token (in list context). get_next_token returns undef when there are no more tokens to be read.
NB: in this documentation I refer to "lines" of VHDL code and "line" sources etc., but in fact the chunks of code dont have to be broken up at line-ends - they can be broken anywhere that isnt in the middle of a token. New-line characters just happen to be a simple and safe way to split up a file. You dont even have to split up the VHDL at all, you can pass in the whole thing as the first and only "line".
Download (0.011MB)
Added: 2007-04-20 License: Perl Artistic License Price:
926 downloads
Hardware::iButton 0.03
Hardware::iButton is a Perl module that allows to talk to DalSemi iButtons via a DS2480 serial widget. more>>
Hardware::iButton is a Perl module that allows to talk to DalSemi iButtons via a DS2480 serial widget.
SYNOPSIS
use Hardware::iButton::Connection;
$c = new Hardware::iButton::Connection "/dev/ttyS0";
@b = $c->scan();
foreach $b (@b) {
print "family: ",$b->family(), "serial number: ", $b->serial(),"n";
print "id: ",$b->id(),"n"; # id = family . serial . crc
print "reg0: ",$b->readreg(0),"n";
}
This module talks to iButtons via the "active" serial interface (anything using the DS2480, including the DS1411k and the DS 9097U). It builds up a list of devices available, lets you read and write their registers, etc.
The connection object is an Hardware::iButton::Connection. The main user-visible purpose of it is to provide a list of Hardware::iButton::Device objects. These can be subclassed once their family codes are known to provide specialized methods unique to the capabilities of that device. Those devices will then be Hardware::iButton::Device::DS1920, etc.
iButtons and solder-mount Touch Memory devices are each identified with a unique 64-bit number. This is broken up into 8 bits of a "family code", which specifies the part number (and consequently the capabilities), then 48 bits of device ID (which Dallas insures is globally unique), then 8 bits of CRC. When you pass these IDs to and from this package, use hex strings like "0123456789ab".
<<lessSYNOPSIS
use Hardware::iButton::Connection;
$c = new Hardware::iButton::Connection "/dev/ttyS0";
@b = $c->scan();
foreach $b (@b) {
print "family: ",$b->family(), "serial number: ", $b->serial(),"n";
print "id: ",$b->id(),"n"; # id = family . serial . crc
print "reg0: ",$b->readreg(0),"n";
}
This module talks to iButtons via the "active" serial interface (anything using the DS2480, including the DS1411k and the DS 9097U). It builds up a list of devices available, lets you read and write their registers, etc.
The connection object is an Hardware::iButton::Connection. The main user-visible purpose of it is to provide a list of Hardware::iButton::Device objects. These can be subclassed once their family codes are known to provide specialized methods unique to the capabilities of that device. Those devices will then be Hardware::iButton::Device::DS1920, etc.
iButtons and solder-mount Touch Memory devices are each identified with a unique 64-bit number. This is broken up into 8 bits of a "family code", which specifies the part number (and consequently the capabilities), then 48 bits of device ID (which Dallas insures is globally unique), then 8 bits of CRC. When you pass these IDs to and from this package, use hex strings like "0123456789ab".
Download (0.021MB)
Added: 2007-08-15 License: Perl Artistic License Price:
808 downloads
Ivy software bus 3.8.1
Ivy is a simple protocol and a set of open-source libraries and programs that allows applications to broadcast information. more>>
Ivy is a simple protocol and a set of open-source libraries and programs that allows applications to broadcast information through text messages, with a subscription mechanism based on regular expressions.
Ivy libraries are available in C, C++, Java and Perl, on Windows and Unix boxes and on Macs. Several Ivy utilities and hardware drivers are available too.
Ivy is currently used in research projects in the air traffic control and human-computer interaction research communities as well as in commercial products. It is also taught to CS students.
Ivy is a CENA product.
Main features:
- Ivy is not based on a centralised server. Actually, Ivy is mostly a communication convention, implemented through a collection of libraries for various languages and platforms. The current version of the Ivy protocol is version 3, which has been stable for the last 3 years.
- Language bindings are available in C (Unix and Windows), C++ (Mac, Unix, Windows), Java and Perl. There have been successful uses through the C library
- Messages are formatted in text, and subscriptions are based on regular expressions. Plans to move to an XML-based subscription language are on their way.
- From the programmers point of view, Ivy is an information broadcasting channel. The main functions are:
- connecting to a bus. Example: IvyInit (b, "192.126:2011")
- sending a message. Example: IvySend (b, "HELLO %s", world)
- binding a message pattern to a callback function. Example: IvyBind (b, "HELLO (.*)", cb)
- the main loop. Example : IvyLoop ()
- Subscriptions are managed on the emitters side, which limits the actual network traffic.
- Direct point-to-point messages are also available.
- Ivy was designed by a research group in Human-Computer Interaction, with the goals of connecting applications written on different toolkits/languages/platforms (such as an OpenGL application on a SGI connected to a PerlTk application on a Linux box), while keeping it simple: no server to be lauched and supervised, a simplistic API, and a communication model compatible with classical event-based GUI progamming. We think we have somewhat reached our goal...
Enhancements:
- This release mostly contains bugfixes and code cleanup.
<<lessIvy libraries are available in C, C++, Java and Perl, on Windows and Unix boxes and on Macs. Several Ivy utilities and hardware drivers are available too.
Ivy is currently used in research projects in the air traffic control and human-computer interaction research communities as well as in commercial products. It is also taught to CS students.
Ivy is a CENA product.
Main features:
- Ivy is not based on a centralised server. Actually, Ivy is mostly a communication convention, implemented through a collection of libraries for various languages and platforms. The current version of the Ivy protocol is version 3, which has been stable for the last 3 years.
- Language bindings are available in C (Unix and Windows), C++ (Mac, Unix, Windows), Java and Perl. There have been successful uses through the C library
- Messages are formatted in text, and subscriptions are based on regular expressions. Plans to move to an XML-based subscription language are on their way.
- From the programmers point of view, Ivy is an information broadcasting channel. The main functions are:
- connecting to a bus. Example: IvyInit (b, "192.126:2011")
- sending a message. Example: IvySend (b, "HELLO %s", world)
- binding a message pattern to a callback function. Example: IvyBind (b, "HELLO (.*)", cb)
- the main loop. Example : IvyLoop ()
- Subscriptions are managed on the emitters side, which limits the actual network traffic.
- Direct point-to-point messages are also available.
- Ivy was designed by a research group in Human-Computer Interaction, with the goals of connecting applications written on different toolkits/languages/platforms (such as an OpenGL application on a SGI connected to a PerlTk application on a Linux box), while keeping it simple: no server to be lauched and supervised, a simplistic API, and a communication model compatible with classical event-based GUI progamming. We think we have somewhat reached our goal...
Enhancements:
- This release mostly contains bugfixes and code cleanup.
Download (0.064MB)
Added: 2006-06-14 License: LGPL (GNU Lesser General Public License) Price:
1227 downloads
Open RObot COntrol Software 1.2.1
Open RObot COntrol Software (Orocos) framework applies software patterns in C++ to achieve real-time execution of software... more>>
Open RObot COntrol Software (Orocos) framework applies software patterns in C++ to achieve real-time execution of software components and provides an infrastructure to quickly integrate them in a real-time operating system such as RTAI or RTLinux, although it can be tested on normal Linux systems.
The Orocos project started as a Free Software project for robotics, but it has outgrown its robotics-dependent roots. Hence, "Orocos" now consists of two decoupled but integrated sub-projects:
Open Realtime Control Services.
This is a hard realtime Software Framework for all possible machine control applications, fully independent of the projects original robotics focus. It is designed to run safely parallel user defined tasks, on both vanilla Linux 2.6 and hard realtime RTAI. Extensive graphical configuration support is available.
Available features: hardware abstraction, operating system abstraction, event handling, hierarchical and parallel state machines, realtime "PLC" scripting, command parsing, online property configuration, multiple time- and event-triggered threads, advanced data protection for synchronous/asynchronous data flow, strongly typed data flow, (on-line) configuration support, ...
Integration between RTAI and TAO and ACE is also part of the ongoing work towards a hard realtime distributed control infastructure based on CORBA.
Open Robot Control Software.
A set of class libraries and an application framework offering generic functionality for machine tools and robots: cascaded control loops and control components, motion generation and interpolation; kinematics and dynamics; robot-specific control algorithms; estimation and identification; etc.
The following families of applications have working implementations available: force-controlled 6R manipulator arm and Cartesian XYZ machine tools. We would welcome developers to start mobile robot and humanoid robot application(s). In those efforts, much of the material of the above-mentioned applications can be reused. In addition, detailed support is available through the Developers mailing list. So, each new application requires moderate programming effort. (Not taking into account system-dependent modules such as device drivers, or kinematic routines.)
Open RObot COntrol Software is designed to appeal to roboticists. See the Orocos project homepage for an automated download script.
Enhancements:
- Support for RTAI 3.4 and 3.5 was improved.
- Various fixes were made in the CORBA support layer.
- The example code and documentation had a review.
<<lessThe Orocos project started as a Free Software project for robotics, but it has outgrown its robotics-dependent roots. Hence, "Orocos" now consists of two decoupled but integrated sub-projects:
Open Realtime Control Services.
This is a hard realtime Software Framework for all possible machine control applications, fully independent of the projects original robotics focus. It is designed to run safely parallel user defined tasks, on both vanilla Linux 2.6 and hard realtime RTAI. Extensive graphical configuration support is available.
Available features: hardware abstraction, operating system abstraction, event handling, hierarchical and parallel state machines, realtime "PLC" scripting, command parsing, online property configuration, multiple time- and event-triggered threads, advanced data protection for synchronous/asynchronous data flow, strongly typed data flow, (on-line) configuration support, ...
Integration between RTAI and TAO and ACE is also part of the ongoing work towards a hard realtime distributed control infastructure based on CORBA.
Open Robot Control Software.
A set of class libraries and an application framework offering generic functionality for machine tools and robots: cascaded control loops and control components, motion generation and interpolation; kinematics and dynamics; robot-specific control algorithms; estimation and identification; etc.
The following families of applications have working implementations available: force-controlled 6R manipulator arm and Cartesian XYZ machine tools. We would welcome developers to start mobile robot and humanoid robot application(s). In those efforts, much of the material of the above-mentioned applications can be reused. In addition, detailed support is available through the Developers mailing list. So, each new application requires moderate programming effort. (Not taking into account system-dependent modules such as device drivers, or kinematic routines.)
Open RObot COntrol Software is designed to appeal to roboticists. See the Orocos project homepage for an automated download script.
Enhancements:
- Support for RTAI 3.4 and 3.5 was improved.
- Various fixes were made in the CORBA support layer.
- The example code and documentation had a review.
Download (3.0MB)
Added: 2007-07-04 License: LGPL (GNU Lesser General Public License) Price:
852 downloads
Hardware::iButton::Device 0.03
Hardware::iButton::Device is a Perl object to represent iButtons. more>>
Hardware::iButton::Device is a Perl object to represent iButtons.
SYNOPSIS
use Hardware::iButton::Connection;
$c = new Hardware::iButton::Connection "/dev/ttyS0";
@b = $c->scan();
foreach $b (@b) {
print "id: ", $b->id(), ", reg0: ",$b->readreg(0),"n";
}
This module talks to iButtons via the "active" serial interface (anything using the DS2480, including the DS1411k and the DS 9097U). It builds up a list of devices available, lets you read and write their registers, etc.
The connection object is an Hardware::iButton::Connection. The main user-visible purpose of it is to provide a list of Hardware::iButton::Device objects. These can be subclassed once their family codes are known to provide specialized methods unique to the capabilities of that device. Those devices will then be Hardware::iButton::Device::DS1920, etc.
<<lessSYNOPSIS
use Hardware::iButton::Connection;
$c = new Hardware::iButton::Connection "/dev/ttyS0";
@b = $c->scan();
foreach $b (@b) {
print "id: ", $b->id(), ", reg0: ",$b->readreg(0),"n";
}
This module talks to iButtons via the "active" serial interface (anything using the DS2480, including the DS1411k and the DS 9097U). It builds up a list of devices available, lets you read and write their registers, etc.
The connection object is an Hardware::iButton::Connection. The main user-visible purpose of it is to provide a list of Hardware::iButton::Device objects. These can be subclassed once their family codes are known to provide specialized methods unique to the capabilities of that device. Those devices will then be Hardware::iButton::Device::DS1920, etc.
Download (0.021MB)
Added: 2007-06-18 License: Perl Artistic License Price:
861 downloads
Lightscribe System Software and SDK 1.4.136.1
Lightscribe System Software and SDK provides libraries and a software development kit for Lightscribe Direct Disc Labeling. more>>
Lightscribe System Software and SDK provides libraries and a software development kit for Lightscribe Direct Disc Labeling of special writable DVD media.
Keep burning beautiful LightScribe discs by regularly updating your LightScribe System Software.
The LightScribe System Software is required for proper operation of your LightScribe system. Updates are released regularly to support new hardware or recently introduced LightScribe CDs and DVDs, and will ensure optimal and reliable operation of your LightScribe Labeling system.
Your LightScribe product manufacturer may have the best knowledge of your specific configuration and needs, and they are recommended as your first source of updates whenever possible.
This limited support universal version of the LightScribe System Software offered here has not been specifically tested by your hardware provider, and is provided as an alternative should you have problems with obtaining an update.
Enhancements:
- New drive and media support was added.
- Minor fixes were made.
<<lessKeep burning beautiful LightScribe discs by regularly updating your LightScribe System Software.
The LightScribe System Software is required for proper operation of your LightScribe system. Updates are released regularly to support new hardware or recently introduced LightScribe CDs and DVDs, and will ensure optimal and reliable operation of your LightScribe Labeling system.
Your LightScribe product manufacturer may have the best knowledge of your specific configuration and needs, and they are recommended as your first source of updates whenever possible.
This limited support universal version of the LightScribe System Software offered here has not been specifically tested by your hardware provider, and is provided as an alternative should you have problems with obtaining an update.
Enhancements:
- New drive and media support was added.
- Minor fixes were made.
Download (MB)
Added: 2007-01-23 License: Free To Use But Restricted Price:
599 downloads
Distributed Hardware Evolution Project
Distributed Hardware Evolution Project is populations of circuits evolving in a distributed online genetic algorithm. more>>
The Distributed Hardware Evolution Project allows the distribution of a genetic algorithm evolving hardware designs across the Internet by setting up an island on each clients PC which will evolve during idle time. Individuals from these islands will migrate between each other as they compete for survival.
All source code is available at Sourceforge under the projects named JaGa, DistrIT, and IslandEv. The source code is generalizable to any genetic algorithm or distributed processing task.
<<lessAll source code is available at Sourceforge under the projects named JaGa, DistrIT, and IslandEv. The source code is generalizable to any genetic algorithm or distributed processing task.
Download (0.006MB)
Added: 2005-04-01 License: GPL (GNU General Public License) Price:
1670 downloads
Bio::MAGE::Protocol::Software 20020902.6
Bio::MAGE::Protocol::Software - Software represents the software used. more>>
Bio::MAGE::Protocol::Software - Software represents the software used.
SYNOPSIS
use Bio::MAGE::Protocol::Software;
# creating an empty instance
my $software = Bio::MAGE::Protocol::Software->new();
# creating an already populated instance
my $software = Bio::MAGE::Protocol::Software->new(softwareManufacturers=>$softwareManufacturers_value,
softwares=>$softwares_value,
hardware=>$hardware_value,
type=>$type_value);
# setting and retrieving object associations
my $softwareManufacturers_val = $software->softwareManufacturers();
$software->softwareManufacturers($value);
my $softwares_val = $software->softwares();
$software->softwares($value);
my $hardware_val = $software->hardware();
$software->hardware($value);
my $type_val = $software->type();
$software->type($value);
<<lessSYNOPSIS
use Bio::MAGE::Protocol::Software;
# creating an empty instance
my $software = Bio::MAGE::Protocol::Software->new();
# creating an already populated instance
my $software = Bio::MAGE::Protocol::Software->new(softwareManufacturers=>$softwareManufacturers_value,
softwares=>$softwares_value,
hardware=>$hardware_value,
type=>$type_value);
# setting and retrieving object associations
my $softwareManufacturers_val = $software->softwareManufacturers();
$software->softwareManufacturers($value);
my $softwares_val = $software->softwares();
$software->softwares($value);
my $hardware_val = $software->hardware();
$software->hardware($value);
my $type_val = $software->type();
$software->type($value);
Download (0.45MB)
Added: 2007-01-08 License: Perl Artistic License Price:
1021 downloads
HCS Open Source Project Beta
HCS Open Source Project consists of a do-it-yourself home automation hardware and software system. more>>
HCS Open Source Project consists of a do-it-yourself home automation hardware and software system.
The HCS Open Source Project is a stand-alone home automation control system which consists of hardware (main controllers and remote networked controllers) and software to monitor and control various devices around your house.
The current plans support using wired and wireless X10 modules, as well as analog, digital, and voice input and output. Once the HCS is programmed, the use of a PC is not required.
CS stands for Home Control System. Originally designed by Steve Ciarcia for the article "Home Run Control System" for Byte magazine.
What is the HCS II? The HCS II is an expandable, network-based (RS485), intelligent-node, industrial-oriented supervisory control system intended for demanding home control applications.
The HCS incorporates direct and remote digital inputs and outputs, direct and remote analog inputs and outputs, real-time or Boolean decision event triggering, X-10 transmission and reception, infrared remote control transmission and reception, remote LCD displays, and a master console.
The HCS II system architecture consists of a central supervisory controller (SC) connected to up to 32 other functional modules (called links) via a RS485 serial network. The SC and the COMM-Links can operate independently and dont need each other to function.
This allows easy testing or incorporation as intelligent subsystems in other control equipment. Initially the subsystems links all shared a comon 8031 controller board (generically called a COMM-Link) with the I/O customized for each application.
<<lessThe HCS Open Source Project is a stand-alone home automation control system which consists of hardware (main controllers and remote networked controllers) and software to monitor and control various devices around your house.
The current plans support using wired and wireless X10 modules, as well as analog, digital, and voice input and output. Once the HCS is programmed, the use of a PC is not required.
CS stands for Home Control System. Originally designed by Steve Ciarcia for the article "Home Run Control System" for Byte magazine.
What is the HCS II? The HCS II is an expandable, network-based (RS485), intelligent-node, industrial-oriented supervisory control system intended for demanding home control applications.
The HCS incorporates direct and remote digital inputs and outputs, direct and remote analog inputs and outputs, real-time or Boolean decision event triggering, X-10 transmission and reception, infrared remote control transmission and reception, remote LCD displays, and a master console.
The HCS II system architecture consists of a central supervisory controller (SC) connected to up to 32 other functional modules (called links) via a RS485 serial network. The SC and the COMM-Links can operate independently and dont need each other to function.
This allows easy testing or incorporation as intelligent subsystems in other control equipment. Initially the subsystems links all shared a comon 8031 controller board (generically called a COMM-Link) with the I/O customized for each application.
Download (0.005MB)
Added: 2007-01-16 License: GPL (GNU General Public License) Price:
1014 downloads
Secleted [ 0 ] software to compare
Copyright Notice:
Software piracy is theft, Using crack, password, serial numbers, registration codes, key generators is illegal and prevent future software development. The above hardware and software search only lists software in full, demo and trial versions for free download. Download links are directly from our mirror sites or publisher sites, torrent files or links from rapidshare.com, yousendit.com or megaupload.com are not allowed
