dallas semiconductor
Sponsored Links
Sponsored Links
Secleted [ 0 ] software to compare
Results 1 - 15 of about 18
dsflasher 0.9
dsflasher is a utility to flash Dallas (Maxim) DS89C450 microcontrollers using a ROM loader. more>>
dsflasher is a utility to flash Dallas (Maxim) DS89C450 microcontrollers using a ROM loader.
Usage:
dsflasher -f [input filename] -p [serial port]
<<lessUsage:
dsflasher -f [input filename] -p [serial port]
Download (0.003MB)
Added: 2007-08-22 License: GPL (GNU General Public License) Price:
797 downloads
Data::SecsPack 0.06
Data::SecsPack is a Perl module pack and unpack numbers in accordance with SEMI E5-94. more>>
Data::SecsPack is a Perl module pack and unpack numbers in accordance with SEMI E5-94.
SYNOPSIS
#####
# Subroutine interface
#
use Data::SecsPack qw(bytes2int config float2binary
ifloat2binary int2bytes
pack_float pack_int pack_num
str2float str2int
unpack_float unpack_int unpack_num);
$big_integer = bytes2int( @bytes );
$old_value = config( $option );
$old_value = config( $option => $new_value);
($binary_magnitude, $binary_exponent) = float2binary($magnitude, $exponent, @options);
($binary_magnitude, $binary_exponent) = ifloat2binary($imagnitude, $iexponent, @options);
@bytes = int2bytes( $big_integer );
($format, $floats) = pack_float($format, @string_floats, [@options]);
($format, $integers) = pack_int($format, @string_integers, [@options]);
($format, $numbers, @string) = pack_num($format, @strings, [@options]);
$float = str2float($string, [@options]);
(@strings, @floats) = str2float(@strings, [@options]);
$integer = str2int($string, [@options]);
(@strings, @integers) = str2int(@strings, [@options]);
@ingegers = unpack_int($format, $integer_string, @options);
@floats = unpack_float($format, $float_string, @options);
@numbers = unpack_num($format, $number_string), @options;
#####
# Class, Object interface
#
# For class interface, use Data::SecsPack instead of $self
#
use Data::SecsPack;
$secspack = Data::SecsPack; # uses built-in config object
$secspack = new Data::SecsPack(@options);
$big_integer = bytes2int( @bytes );
($binary_magnitude, $binary_exponent) = $secspack->float2binary($magnitude, $exponent, @options);
($binary_magnitude, $binary_exponent) = $secspack->ifloat2binary($imagnitude, $iexponent, @options);
@bytes = $secspack->int2bytes( $big_integer );
($format, $floats) = $secspack->pack_float($format, @string_integers, [@options]);
($format, $integers) = $secspack->pack_int($format, @string_integers, [@options]);
($format, $numbers, @strings) = $secspack->pack_num($format, @strings, [@options]);
$integer = $secspack->str2int($string, [@options])
(@strings, @integers) = $secspack->str2int(@strings, [@options]);
$float = $secspack->str2float($string, [@options]);
(@strings, @floats) = $secspack->str2float(@strings, [@options]);
@ingegers = $secspack->unpack_int($format, $integer_string, @options);
@floats = $secspack->unpack_float($format, $float_string, @options);
@numbers = $secspack->unpack_num($format, $number_string, @options);
Generally, if a subroutine will process a list of options, @options, that subroutine will also process an array reference, @options, [@options], or hash reference, %options, {@options}. If a subroutine will process an array reference, @options, [@options], that subroutine will also process a hash reference, %options, {@options}. See the description for a subroutine for details and exceptions.
The subroutines in the Data::SecsPack module packs and unpacks numbers in accordance with SEMI E5-94. The E5-94 establishes the standard for communication between the equipment used to fabricate semiconductors and the host computer that controls the fabrication. The equipment in a semiconductor factory (fab) or any other fab contains every conceivable known microprocessor and operating system known to man. And there are a lot of specialize real-time embedded processors and speciallize real-time embedded operating systems in addition to the those in the PC world.
The communcication between host and equipment used packed nested list data structures that include arrays of characters, integers and floats. The standard has been in place and widely used in China, Germany, Korea, Japan, France, Italy and the most remote corners on this planent for decades. The basic data structure and packed data formats have not changed for decades.
This stands in direct contradiction to the common conceptions of many in the Perl community and most other communities. The following quote is taken from page 761, Programming Perl third edition, discussing the pack subroutine:
"Floating-point numbers are in the native machine format only. Because of the variety of floating format and lack of a standard "network" represenation, no facility for interchange has been made. This means that packed floating-point data written on one machine may not be readable on another. That is a problem even when both machines use IEEE floating-point arithmetic, because the endian-ness of memory representation is not part of the IEEE spec."
There are a lot of things that go over the net that have industry or military standards but no RFCs. So unless you dig them out, you will never know they exist. While RFC and military standards may be freely copyied, industry standards are usually copyrighted. This means if you want to read the standard, you have to pay whatever the market bears. ISO standards, SEMI stardards, American National Standards, IEEE standards beside being boring are expensive. In other words, you do not see them flying out the door at the local Barnes and Nobles. In fact, you will not even find them inside the door.
It very easy to run these non RFC standard protocols over the net. Out of 64,000 ports, pick a port of opportunity (hopefully not one of those low RFC preassigned ports) and configure the equipment and host to the same IP and port. Many times the software will allow a remote console that is watch only. The watch console may even be a web server on port 80. If there is a remote soft console, you can call up or e-mail the equipment manufacturers engineer in say Glouster, MA, USA and tell him the IP and port so he can watch his manchine mangle a cassette of wafers with a potential retail value of half million dollars.
SEMI E5-94 and their precessors do standardize the endian-ness of floating point, the packing of nested data, used in many programming languages, and much, much more. The endian-ness of SEMI E5-94 is the first MSB byte, floats sign bit first. Maybe this is because it makes it easy to spot numbers in a packed data structure.
The nested data has many performance advantages over the common SQL culture of viewing and representing data as tables. The automated fabs of the world make use of SEMI E5-94 nested data not only for real-time communication (TCP/IP RS-2332 etc) between machines but also for snail-time processing as such things as logs and performance data.
Does this standard communications protocol ensure that everything goes smoothly without any glitches with this wild mixture of hardware and software talking to each other in real time? Of course not. Bytes get reverse. Data gets jumbled from point A to point B. Machine time to test software is non-existance. Big ticket, multi-million dollar fab equipment has to work to earn its keep. And, then there is the everyday business of suiting up, with humblizing hair nets, going through air and other showers with your favorite or not so favorite co-worker just to get into the clean room. And make sure not to do anything that will scatch a wafer with a lot of Intel Pentiums on them. It is totally amazing that the product does get out the door.
<<lessSYNOPSIS
#####
# Subroutine interface
#
use Data::SecsPack qw(bytes2int config float2binary
ifloat2binary int2bytes
pack_float pack_int pack_num
str2float str2int
unpack_float unpack_int unpack_num);
$big_integer = bytes2int( @bytes );
$old_value = config( $option );
$old_value = config( $option => $new_value);
($binary_magnitude, $binary_exponent) = float2binary($magnitude, $exponent, @options);
($binary_magnitude, $binary_exponent) = ifloat2binary($imagnitude, $iexponent, @options);
@bytes = int2bytes( $big_integer );
($format, $floats) = pack_float($format, @string_floats, [@options]);
($format, $integers) = pack_int($format, @string_integers, [@options]);
($format, $numbers, @string) = pack_num($format, @strings, [@options]);
$float = str2float($string, [@options]);
(@strings, @floats) = str2float(@strings, [@options]);
$integer = str2int($string, [@options]);
(@strings, @integers) = str2int(@strings, [@options]);
@ingegers = unpack_int($format, $integer_string, @options);
@floats = unpack_float($format, $float_string, @options);
@numbers = unpack_num($format, $number_string), @options;
#####
# Class, Object interface
#
# For class interface, use Data::SecsPack instead of $self
#
use Data::SecsPack;
$secspack = Data::SecsPack; # uses built-in config object
$secspack = new Data::SecsPack(@options);
$big_integer = bytes2int( @bytes );
($binary_magnitude, $binary_exponent) = $secspack->float2binary($magnitude, $exponent, @options);
($binary_magnitude, $binary_exponent) = $secspack->ifloat2binary($imagnitude, $iexponent, @options);
@bytes = $secspack->int2bytes( $big_integer );
($format, $floats) = $secspack->pack_float($format, @string_integers, [@options]);
($format, $integers) = $secspack->pack_int($format, @string_integers, [@options]);
($format, $numbers, @strings) = $secspack->pack_num($format, @strings, [@options]);
$integer = $secspack->str2int($string, [@options])
(@strings, @integers) = $secspack->str2int(@strings, [@options]);
$float = $secspack->str2float($string, [@options]);
(@strings, @floats) = $secspack->str2float(@strings, [@options]);
@ingegers = $secspack->unpack_int($format, $integer_string, @options);
@floats = $secspack->unpack_float($format, $float_string, @options);
@numbers = $secspack->unpack_num($format, $number_string, @options);
Generally, if a subroutine will process a list of options, @options, that subroutine will also process an array reference, @options, [@options], or hash reference, %options, {@options}. If a subroutine will process an array reference, @options, [@options], that subroutine will also process a hash reference, %options, {@options}. See the description for a subroutine for details and exceptions.
The subroutines in the Data::SecsPack module packs and unpacks numbers in accordance with SEMI E5-94. The E5-94 establishes the standard for communication between the equipment used to fabricate semiconductors and the host computer that controls the fabrication. The equipment in a semiconductor factory (fab) or any other fab contains every conceivable known microprocessor and operating system known to man. And there are a lot of specialize real-time embedded processors and speciallize real-time embedded operating systems in addition to the those in the PC world.
The communcication between host and equipment used packed nested list data structures that include arrays of characters, integers and floats. The standard has been in place and widely used in China, Germany, Korea, Japan, France, Italy and the most remote corners on this planent for decades. The basic data structure and packed data formats have not changed for decades.
This stands in direct contradiction to the common conceptions of many in the Perl community and most other communities. The following quote is taken from page 761, Programming Perl third edition, discussing the pack subroutine:
"Floating-point numbers are in the native machine format only. Because of the variety of floating format and lack of a standard "network" represenation, no facility for interchange has been made. This means that packed floating-point data written on one machine may not be readable on another. That is a problem even when both machines use IEEE floating-point arithmetic, because the endian-ness of memory representation is not part of the IEEE spec."
There are a lot of things that go over the net that have industry or military standards but no RFCs. So unless you dig them out, you will never know they exist. While RFC and military standards may be freely copyied, industry standards are usually copyrighted. This means if you want to read the standard, you have to pay whatever the market bears. ISO standards, SEMI stardards, American National Standards, IEEE standards beside being boring are expensive. In other words, you do not see them flying out the door at the local Barnes and Nobles. In fact, you will not even find them inside the door.
It very easy to run these non RFC standard protocols over the net. Out of 64,000 ports, pick a port of opportunity (hopefully not one of those low RFC preassigned ports) and configure the equipment and host to the same IP and port. Many times the software will allow a remote console that is watch only. The watch console may even be a web server on port 80. If there is a remote soft console, you can call up or e-mail the equipment manufacturers engineer in say Glouster, MA, USA and tell him the IP and port so he can watch his manchine mangle a cassette of wafers with a potential retail value of half million dollars.
SEMI E5-94 and their precessors do standardize the endian-ness of floating point, the packing of nested data, used in many programming languages, and much, much more. The endian-ness of SEMI E5-94 is the first MSB byte, floats sign bit first. Maybe this is because it makes it easy to spot numbers in a packed data structure.
The nested data has many performance advantages over the common SQL culture of viewing and representing data as tables. The automated fabs of the world make use of SEMI E5-94 nested data not only for real-time communication (TCP/IP RS-2332 etc) between machines but also for snail-time processing as such things as logs and performance data.
Does this standard communications protocol ensure that everything goes smoothly without any glitches with this wild mixture of hardware and software talking to each other in real time? Of course not. Bytes get reverse. Data gets jumbled from point A to point B. Machine time to test software is non-existance. Big ticket, multi-million dollar fab equipment has to work to earn its keep. And, then there is the everyday business of suiting up, with humblizing hair nets, going through air and other showers with your favorite or not so favorite co-worker just to get into the clean room. And make sure not to do anything that will scatch a wafer with a lot of Intel Pentiums on them. It is totally amazing that the product does get out the door.
Download (0.10MB)
Added: 2007-01-15 License: Perl Artistic License Price:
1014 downloads
ASCO 0.4.6
ASCO project aims to bring circuit optimization capabilities to existing SPICE simulators. more>>
ASCO aka A SPICE Circuit Optimizer project aims to bring circuit optimization capabilities to existing SPICE simulators.
Main features:
ASCO is the result of an academic research which in itself did not intended to create a new tool, but only to design high performance analog low-power low-voltage circuits for mobile communications. Interaction with other experienced designers has resulted in the ideas existing in the ASCO tool. With the exception of the DE optimizer all code has been personally written. The key features of the ASCO tool are:
- Simulator independent: currently out-of-the-box support for Eldo (TM), HSPICE (R), LTSpice (TM) and Spectre (R) exist. More are to be included in future releases.
- Number of variables: there is, in theory, no limit to the number of circuit variables that can be optimized, except those constraints imposed by the available computer memory and/or the time required to generate a functional circuit. It is currently hardcoded in the C code.
- PVT corners: by using the simulator functionality, the possibility to test various design corners and Monte Carlo analysis is only limited to the simulator capability and by the time it takes to finish the optimization.
- Efficiency: the optimization algorithm features a global optimization using differential evolution. It has been used on a variety of applications and is know to produce good results in an acceptable time.
- Within the supported SPICE simulators, arbitrary netlist can be optimized on different conditions without having to recompile the code.
- File format: all outputted data and log information is stored in plain text format. This guarantees that they will be always readable in the future. In addition, it makes possible to use other existing tools to post-process the optimization results.
- Its free software: the code is available under the GNU GPL license.
ASCO has been designed to address problems that are particular of electric circuits. Although not limited, some possible applications can include:
- Fully redesign a new circuit described in a SPICE netlist.
- Reuse, optimize an existing circuit.
- Migrated an existing and working design to a more advanced semiconductor technology process effortlessly.
- Increase the robustness and yield of an already designed circuit by guaranteeing that it comply with all design goals and constraints in some/all process corners at will.
- Easily explore a new operating point (design space) for an already existing topology, to reduce power consumption, area or both.
- Look for a feasible new design topology before investing a considerable time trying to derive equations that describe its operation.
- Refer to Chapter 5 for ready to use practical examples to introduce you to ASCO, a SPICE circuit optimization tool. Bellow is a list of the examples that can be found with the objective of introducing the tool, its usage and applications.
- Optimization from scratch a digital inverter circuit to achieve minimum power consumption while fulfilling the design constraints; guarantee that this is valid for different process corners and also take into account device parameter mismatch (Monte Carlo).
- Optimization of a three stage operation amplifier featuring the frequency compensation technique described in [Ram05]. A total of 21 variables and five constraints/performance goals are used with the objective of obtaining the most power efficient circuit.
- The simple class-E amplifier intended for operation in the GSM-850 band is given. A more realistic model representing a differential two stage power amplifier, including all relevant circuit and board parasitics to better describe the circuit measurement performance alongside with measurements from a manufactured chip in a 0.35 um CMOS commercial technology, is given in [Ram05].
Enhancements:
- Improvements were made in the RF module functionality.
- Support was included for logarithmic search space for the existing variables.
- Code refinements and bugfixes were made.
<<lessMain features:
ASCO is the result of an academic research which in itself did not intended to create a new tool, but only to design high performance analog low-power low-voltage circuits for mobile communications. Interaction with other experienced designers has resulted in the ideas existing in the ASCO tool. With the exception of the DE optimizer all code has been personally written. The key features of the ASCO tool are:
- Simulator independent: currently out-of-the-box support for Eldo (TM), HSPICE (R), LTSpice (TM) and Spectre (R) exist. More are to be included in future releases.
- Number of variables: there is, in theory, no limit to the number of circuit variables that can be optimized, except those constraints imposed by the available computer memory and/or the time required to generate a functional circuit. It is currently hardcoded in the C code.
- PVT corners: by using the simulator functionality, the possibility to test various design corners and Monte Carlo analysis is only limited to the simulator capability and by the time it takes to finish the optimization.
- Efficiency: the optimization algorithm features a global optimization using differential evolution. It has been used on a variety of applications and is know to produce good results in an acceptable time.
- Within the supported SPICE simulators, arbitrary netlist can be optimized on different conditions without having to recompile the code.
- File format: all outputted data and log information is stored in plain text format. This guarantees that they will be always readable in the future. In addition, it makes possible to use other existing tools to post-process the optimization results.
- Its free software: the code is available under the GNU GPL license.
ASCO has been designed to address problems that are particular of electric circuits. Although not limited, some possible applications can include:
- Fully redesign a new circuit described in a SPICE netlist.
- Reuse, optimize an existing circuit.
- Migrated an existing and working design to a more advanced semiconductor technology process effortlessly.
- Increase the robustness and yield of an already designed circuit by guaranteeing that it comply with all design goals and constraints in some/all process corners at will.
- Easily explore a new operating point (design space) for an already existing topology, to reduce power consumption, area or both.
- Look for a feasible new design topology before investing a considerable time trying to derive equations that describe its operation.
- Refer to Chapter 5 for ready to use practical examples to introduce you to ASCO, a SPICE circuit optimization tool. Bellow is a list of the examples that can be found with the objective of introducing the tool, its usage and applications.
- Optimization from scratch a digital inverter circuit to achieve minimum power consumption while fulfilling the design constraints; guarantee that this is valid for different process corners and also take into account device parameter mismatch (Monte Carlo).
- Optimization of a three stage operation amplifier featuring the frequency compensation technique described in [Ram05]. A total of 21 variables and five constraints/performance goals are used with the objective of obtaining the most power efficient circuit.
- The simple class-E amplifier intended for operation in the GSM-850 band is given. A more realistic model representing a differential two stage power amplifier, including all relevant circuit and board parasitics to better describe the circuit measurement performance alongside with measurements from a manufactured chip in a 0.35 um CMOS commercial technology, is given in [Ram05].
Enhancements:
- Improvements were made in the RF module functionality.
- Support was included for logarithmic search space for the existing variables.
- Code refinements and bugfixes were made.
Download (0.38MB)
Added: 2007-03-26 License: GPL (GNU General Public License) Price:
947 downloads
LAMMPS 01-Feb-2007
LAMMPS project is a Molecular Dynamics Simulator. more>>
LAMMPS project is a Molecular Dynamics Simulator.
LAMMPS has potentials for soft materials (biomolecules, polymers) and solid-state materials (metals, semiconductors) and coarse-grain systems. It can be used to model atoms or, more generically, as a parallel particle simulator at the mesoscale or continuum levels.
LAMMPS runs on single-processor machines or in parallel using message-passing techniques and a spatial-decomposition of the simulation domain. The code is designed to be easy to modify or extend with new functionality.
LAMMPS is distributed as an open source code under the terms of the GPL license.
Enhancements:
- Changed to using NIST values for constants.
- A potential problem with alloy interactions has been fixed.
- Improved flexibility of user customization of output.
- The ability to add new styles of atom has been improved.
- A new atom method library, non-orthogonal lattice support, and support for semiconductors have been added.
- There are code speedups and bugfixes.
<<lessLAMMPS has potentials for soft materials (biomolecules, polymers) and solid-state materials (metals, semiconductors) and coarse-grain systems. It can be used to model atoms or, more generically, as a parallel particle simulator at the mesoscale or continuum levels.
LAMMPS runs on single-processor machines or in parallel using message-passing techniques and a spatial-decomposition of the simulation domain. The code is designed to be easy to modify or extend with new functionality.
LAMMPS is distributed as an open source code under the terms of the GPL license.
Enhancements:
- Changed to using NIST values for constants.
- A potential problem with alloy interactions has been fixed.
- Improved flexibility of user customization of output.
- The ability to add new styles of atom has been improved.
- A new atom method library, non-orthogonal lattice support, and support for semiconductors have been added.
- There are code speedups and bugfixes.
Download (MB)
Added: 2007-02-16 License: GPL (GNU General Public License) Price:
981 downloads
IOSEMU 0.2.5
IOSEMU is a Cisco 7200 emulator that uses JIT to achieve good performance. more>>
IOSEMU is a Cisco 7200 emulator that uses JIT to achieve good performance. The project is able to boot real Cisco IOS images.
At this time, the emulator I have programmed is able to boot a large number of Cisco IOS releases available for the 7200 platform, including the latest 12.2S and 12.4. The following devices are emulated:
MIPS64 CPU processor. The instruction set is not completely emulated now (FPU support is lacking, TLB support is not finished and other minor things), but it is sufficient for IOS ;
DRAM and Packet SRAM memory ;
Non-Volatile Memory (NVRAM) ;
Dallas DS1620 Temperature Sensors and Voltage Sensors, allowing the Environmental Monitor to work properly ;
NMC93C46 Serial EEPROM ;
I/O and Midplane FPGA specific to the C7200 platform ;
Basic support of Serial interfaces (PA-8T) and Ethernet IOCard based on DEC21140 (Tulip) chip.
Basic Galileo GT64010 PCI controller, DEC 21050 PCI bridges and so.
To run at a decent speed, the emulator uses a JIT (Just In Time) compiler, which is working on x86 CPU (like Pentium) and x86_64 CPU (AMD64/Intel EM64T).
<<lessAt this time, the emulator I have programmed is able to boot a large number of Cisco IOS releases available for the 7200 platform, including the latest 12.2S and 12.4. The following devices are emulated:
MIPS64 CPU processor. The instruction set is not completely emulated now (FPU support is lacking, TLB support is not finished and other minor things), but it is sufficient for IOS ;
DRAM and Packet SRAM memory ;
Non-Volatile Memory (NVRAM) ;
Dallas DS1620 Temperature Sensors and Voltage Sensors, allowing the Environmental Monitor to work properly ;
NMC93C46 Serial EEPROM ;
I/O and Midplane FPGA specific to the C7200 platform ;
Basic support of Serial interfaces (PA-8T) and Ethernet IOCard based on DEC21140 (Tulip) chip.
Basic Galileo GT64010 PCI controller, DEC 21050 PCI bridges and so.
To run at a decent speed, the emulator uses a JIT (Just In Time) compiler, which is working on x86 CPU (like Pentium) and x86_64 CPU (AMD64/Intel EM64T).
Download (0.12MB)
Added: 2006-10-29 License: GPL (GNU General Public License) Price:
1100 downloads
plconfig 0.2
plconfig is a tool for configuring HomePlug powerline bridges. more>>
plconfig is a tool for configuring HomePlug powerline bridges. HomePlug specification based powerline bridges are becoming increasingly popular. Ive got myself two of them; the brand name is "ZEUS"; a strange brand that only seems to exist in Switzerland, and some people say its actually ZyXEL (have a look at the guts). Whatever, according to the HomePlug alliance homepage (www.homeplug.org), there are only two manufacturers of powerline ICs at the moment: Intellon and Cogency Semiconductor. My bridges have the Intellon chipset (INT5130 integrated powerline MAC-PHY transceiver and INT1000 analog conversion IC). Intellon calls their implementation "PowerPacket".
Now, about the only thing that has to be configured with these is the encryption password, so your neighbor wont be able to sniff your data. A Windows program is provided for that purpose - you hook up the bridge directly to your PC, enter a 2-24 character password, and the password is saved into the bridges EEPROM.
This is a bit of an inconvenience to non-Windows users, and even if you keep Windows boxes around, at least to me the software looks ugly. It keeps running strange daemons (WinPlcMan.exe, BridgeDeCor.exe, etc.) that use up to 100% CPU at times, and sometimes its not possible to set the password without power cycling the bridge first (although that seems to be the fault of the bridge).
So I made an attempt at writing a program to set up the encryption key. I found some inofficial information on the web, and it agreed with what I learned from sniffing the communication between the PowerPacket setup software and the bridge.
Im making the program available here for you to try; its status is currently somewhere in between an ugly hack and a simple use-once-and-throw-away tool. I have no idea if it works with other powerline bridges; although it should work with all Intellon-based ones. If youve had success with a particular product, please let me know!
Besides setting the encryption key, it can also capture and display powerline bridge management-related packets and request statistics from the bridge(s).
Enhancements:
- plaintext passwords are now hashed correctly as per the HomePlug specification (no longer homebrew MD5); as such passwords should now be compatible with the Windows setup software supplied by Intellon (note that -s does no longer set up the same key as in 0.1! Of course -s 0x behaves as before...)
<<lessNow, about the only thing that has to be configured with these is the encryption password, so your neighbor wont be able to sniff your data. A Windows program is provided for that purpose - you hook up the bridge directly to your PC, enter a 2-24 character password, and the password is saved into the bridges EEPROM.
This is a bit of an inconvenience to non-Windows users, and even if you keep Windows boxes around, at least to me the software looks ugly. It keeps running strange daemons (WinPlcMan.exe, BridgeDeCor.exe, etc.) that use up to 100% CPU at times, and sometimes its not possible to set the password without power cycling the bridge first (although that seems to be the fault of the bridge).
So I made an attempt at writing a program to set up the encryption key. I found some inofficial information on the web, and it agreed with what I learned from sniffing the communication between the PowerPacket setup software and the bridge.
Im making the program available here for you to try; its status is currently somewhere in between an ugly hack and a simple use-once-and-throw-away tool. I have no idea if it works with other powerline bridges; although it should work with all Intellon-based ones. If youve had success with a particular product, please let me know!
Besides setting the encryption key, it can also capture and display powerline bridge management-related packets and request statistics from the bridge(s).
Enhancements:
- plaintext passwords are now hashed correctly as per the HomePlug specification (no longer homebrew MD5); as such passwords should now be compatible with the Windows setup software supplied by Intellon (note that -s does no longer set up the same key as in 0.1! Of course -s 0x behaves as before...)
Download (0.008MB)
Added: 2006-07-03 License: GPL (GNU General Public License) Price:
699 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
Text::LooseCSV 1.5
Text::LooseCSV is a highly forgiving variable length record text parser; compare to MS Excel. more>>
Text::LooseCSV is a highly forgiving variable length record text parser; compare to MS Excel.
SYNOPSIS
use Text::LooseCSV;
use IO::File;
$fh = new IO::File $fname;
$f = new Text::LooseCSV($fh);
# Some optional settings
$f->word_delimiter("t");
$f->line_delimiter("n");
$f->no_quotes(1);
# Parse/split a line
while ($rec = $f->next_record())
{
if ($rec == -1)
{
warn("corrupt rec: ", $f->cur_line);
next;
}
# process $rec as arrayref
...
}
# Or, (vice-versa) create a variable-length record file
$line = $f->form_record( [ Debbie Does Dallas,30.00,VHS,Classic ] );
Why another variable-length text record parser? Ive had the privilege to parse some of the gnarliest data ever seen and everything else I tried on CPAN choked (at the time I wrote this module). This module has been munching on millions of records of the filthiest data imaginable at several production sites so I thought Id contribute.
This module follows somewhat loose rules (compare to MS Excel) and will handle embedded newlines, etc. It is capable of handling large files and processes data in line-chunks. If MAX_LINEBUF is reached, however, it will mark the current record as corrupt, return -1 and start over again at the very next line. This will (of course) process tab-delimited data or whatever value you set for word_delimiter.
Methods are called in perl OO fashion.
WARNING this module messes with $/ line_delimiter sets $/ and is always called during construction. Dont change $/ during program execution!
<<lessSYNOPSIS
use Text::LooseCSV;
use IO::File;
$fh = new IO::File $fname;
$f = new Text::LooseCSV($fh);
# Some optional settings
$f->word_delimiter("t");
$f->line_delimiter("n");
$f->no_quotes(1);
# Parse/split a line
while ($rec = $f->next_record())
{
if ($rec == -1)
{
warn("corrupt rec: ", $f->cur_line);
next;
}
# process $rec as arrayref
...
}
# Or, (vice-versa) create a variable-length record file
$line = $f->form_record( [ Debbie Does Dallas,30.00,VHS,Classic ] );
Why another variable-length text record parser? Ive had the privilege to parse some of the gnarliest data ever seen and everything else I tried on CPAN choked (at the time I wrote this module). This module has been munching on millions of records of the filthiest data imaginable at several production sites so I thought Id contribute.
This module follows somewhat loose rules (compare to MS Excel) and will handle embedded newlines, etc. It is capable of handling large files and processes data in line-chunks. If MAX_LINEBUF is reached, however, it will mark the current record as corrupt, return -1 and start over again at the very next line. This will (of course) process tab-delimited data or whatever value you set for word_delimiter.
Methods are called in perl OO fashion.
WARNING this module messes with $/ line_delimiter sets $/ and is always called during construction. Dont change $/ during program execution!
Download (0.006MB)
Added: 2006-12-21 License: Perl Artistic License Price:
1037 downloads
xmbmon 2.05
xmbmon is a monitoring program for motherboards. more>>
xmbmon is a monitoring program for motherboards.
Recent motherboards have functionalities to monitor the CPU temperatures and the frequency of CPU cooling fans etc.
Although some programs utilizing these hardware monitoring facilities have been developed for the Microsoft Windows platforms, no programs seem to exist for PC-UNIX and the X Windows System platforms.
Thus, I have tried to make small programs. They have only least functionalities, the one "mbmon" used at the command line reports the temperatures, voltages and rpm (rounds per minute) of cooling fans, and the other "xmbmon" displays the three temperatures and a core voltage as simple curves.
The following hardware monitor chips are supported and the programs will work if your motherboard uses one of them or their compatible chip:
1. National Semiconductor co.
LM78/LM79, LM75, LM90, LM80, LM85
2. WinBond co.
W83781D, W83782D, W83783S, W83627HF, W83697HF built-in, W83L784R, W83L785R, W83L785TS-S, W83627THF
3. ASUSTek co.
AS99127F, ASB100 (Bach), ASM58 etc. (Mozart-2)
4. VIA Technology co.
VT82C686A/B built-in
5. Integrated Technology Express co.
IT8705F, IT8712F built-in
6. Genesys Logic
GL518SM, GL520SM
7. Analog Devices
ADM1024/1025/1027, ADT7463, ADM1020/1021/1023
8. Standard Microsystem co.
EMC6D100/101/102
Enhancements:
- Bugs for detecting ALi chipset fixed.
- Further smoothing for plotting curves in xmbmon.
- SMBus accesses of VIA VT8237 and Intel ICH6 are supported.
- Problem related to select() system call fixed.
- The part of IO port read/write is unified into an gas in-line assembler code (so, gcc with x86-gas is assumed!).
- Changes to work on Solaris for x86 platform and others for cleaning up the codes.
<<lessRecent motherboards have functionalities to monitor the CPU temperatures and the frequency of CPU cooling fans etc.
Although some programs utilizing these hardware monitoring facilities have been developed for the Microsoft Windows platforms, no programs seem to exist for PC-UNIX and the X Windows System platforms.
Thus, I have tried to make small programs. They have only least functionalities, the one "mbmon" used at the command line reports the temperatures, voltages and rpm (rounds per minute) of cooling fans, and the other "xmbmon" displays the three temperatures and a core voltage as simple curves.
The following hardware monitor chips are supported and the programs will work if your motherboard uses one of them or their compatible chip:
1. National Semiconductor co.
LM78/LM79, LM75, LM90, LM80, LM85
2. WinBond co.
W83781D, W83782D, W83783S, W83627HF, W83697HF built-in, W83L784R, W83L785R, W83L785TS-S, W83627THF
3. ASUSTek co.
AS99127F, ASB100 (Bach), ASM58 etc. (Mozart-2)
4. VIA Technology co.
VT82C686A/B built-in
5. Integrated Technology Express co.
IT8705F, IT8712F built-in
6. Genesys Logic
GL518SM, GL520SM
7. Analog Devices
ADM1024/1025/1027, ADT7463, ADM1020/1021/1023
8. Standard Microsystem co.
EMC6D100/101/102
Enhancements:
- Bugs for detecting ALi chipset fixed.
- Further smoothing for plotting curves in xmbmon.
- SMBus accesses of VIA VT8237 and Intel ICH6 are supported.
- Problem related to select() system call fixed.
- The part of IO port read/write is unified into an gas in-line assembler code (so, gcc with x86-gas is assumed!).
- Changes to work on Solaris for x86 platform and others for cleaning up the codes.
Download (0.14MB)
Added: 2005-10-07 License: GPL (GNU General Public License) Price:
1488 downloads
DigiTemp 3.5.0
DigiTemp uses a simple serial port adapter to read temperatures from the Dallas Semiconductor 1-Wire DS1820. more>>
DigiTemp uses a simple serial port adapter to read temperatures from the Dallas Semiconductor 1-Wire DS1820 digital temperature sensors.
DigiTemp supports the DS9097-U adapter, supports DS2409 based 1-Wire hubs, and features a 1-Wire walk that will display all devices on the LAN, not just temperature sensors.
Enhancements:
- This release combines all the binary releases into a single tar.gz, including Windows binaries compiled with Cygwin.
- It adds DS1923 Hygrochron support, and fixes some small bugs in the userial driver.
- A lockdev bug was fixed (wasnt unlocking when done).
- A crash in free_couplers() was fixed.
- There is better error reporting when trying to access serial ports that dont exist.
- This release is compiled for Windows with Cygwin.
- DS2490/9490 support still doesnt work well for the author, although others have had success with it.
<<lessDigiTemp supports the DS9097-U adapter, supports DS2409 based 1-Wire hubs, and features a 1-Wire walk that will display all devices on the LAN, not just temperature sensors.
Enhancements:
- This release combines all the binary releases into a single tar.gz, including Windows binaries compiled with Cygwin.
- It adds DS1923 Hygrochron support, and fixes some small bugs in the userial driver.
- A lockdev bug was fixed (wasnt unlocking when done).
- A crash in free_couplers() was fixed.
- There is better error reporting when trying to access serial ports that dont exist.
- This release is compiled for Windows with Cygwin.
- DS2490/9490 support still doesnt work well for the author, although others have had success with it.
Download (0.26MB)
Added: 2007-01-04 License: GPL (GNU General Public License) Price:
1034 downloads
jHomenet 0.5.0
jHomenet is a home automation application. more>>
jHomenet is a home automation application. jHomenet uses both X-10 and Dallas Semiconductor 1-Wire network sensors and devices to collect sensor data and control devices.
jHomenet project can be programmed to respond to events, including particular sensor data values or time-of-day events.
Enhancements:
- This is a binary only release that includes several changes.
- Most noticable is the change in the versioning format.
- This change, however, also includes a drastic change in the library versioning and dependency framework.
- Other changes include a revised EventLogger, some UI tweaks, and several new jhomenet-commons JUnit unit tests.
- Some significant changes were also made to the Ant build setup.
<<lessjHomenet project can be programmed to respond to events, including particular sensor data values or time-of-day events.
Enhancements:
- This is a binary only release that includes several changes.
- Most noticable is the change in the versioning format.
- This change, however, also includes a drastic change in the library versioning and dependency framework.
- Other changes include a revised EventLogger, some UI tweaks, and several new jhomenet-commons JUnit unit tests.
- Some significant changes were also made to the Ant build setup.
Download (9.1MB)
Added: 2007-07-16 License: LGPL (GNU Lesser General Public License) Price:
832 downloads
Regress Pro 1.1
Regress Pro is scientific/industrial software that can be used to study experimental data. more>>
Regress Pro is scientific/industrial software that can be used to study experimental data coming from spectroscopic ellipsometers or reflectometers.
Regress Pro has been developed mainly for the application of thin film measurement in the semiconductor industry.
The software is suitable both to determine the thickness of the layers and to determine the optical properties of dielectric materials.
<<lessRegress Pro has been developed mainly for the application of thin film measurement in the semiconductor industry.
The software is suitable both to determine the thickness of the layers and to determine the optical properties of dielectric materials.
Download (0.080MB)
Added: 2006-10-31 License: GPL (GNU General Public License) Price:
1091 downloads
Archimedes 0.0.4
GNU Archimedes is the GNU package for the design and simulation of submicron semiconductor devices. more>>
GNU Archimedes is the GNU package for the design and simulation of submicron semiconductor devices. Archimedes is a 2D Fast Monte Carlo simulator which can take into account all the relevant quantum effects, thank to the implementation of the Bohm effective potential method.
The physics and geometry of a general device is introduced by typing a simple script, which makes, in this sense, GNU Archimedes a powerfull tool for the simulation of quite general semiconductor devices.
In the present release, GNU Archimedes is able to simulate electrons and heavy holes in Silicon and GaAs (Gamma and L-valleys) devices (holes are simulated by means of a simplified MEP model), and in the next release, which is in preparation, it will be able to make simulations in 1D, 2D and 3D (this release will be delivered as soon as possible).
The Scientifical and Industrial Motivations
In today semiconductor technology, the miniaturization of devices is more and more progressing. In this context, it is easy to see that numerical simulations play an important role at every level of device manufacture. In fact, the cost of designing and physically constructing prototypes for VLSI semiconductor devices is very high and without the availability of advanced simulators the efforts for devices miniaturization would, likely, be brought to a halt. From assessing the performance of individual transistors, to circuits and systems, and, consequently, with the promise of improved device performance, industries are encouraged to keep on miniaturizing with lower manufacture costs.
But, unfortunately, such simulations are not whithout their challenges... A first consequence of device miniaturization is that simulations of submicron semicondutor devices requires advanced transport models. Because of the presence of very high and rapidly varying electric field, phenomena occur which cannot be described by means of the well-known drift-diffusion models, which do not incorporate energy as a dynamical variable.
That is why some generalization has been sought in order to obtain more physically accurate models, like energy-transport and hydrodynamical models. The energy-transport models which are implemented in commercial simulators are based on phenomenological constitutive equations for the particle flux and energy flux depending on a set of parameters which are fitted to homogeneous bulk material Monte Carlo simulations. So, this is not, certainly, a satisfactory physical description of the internal electronic dynamics in a semiconductor device.
As current device technologies quickly approach the scales whereby quantum effects due to strong confinement of carriers and direct source-drain tunneling will begin to dominate, new simulation techniques are required in order to fully understand and acurately simulate the physics behind the technology operation.
Of all the simulation methods currently employed, ensemble Monte Carlo has always been, both in the accademic and industrial community, the most vigorous and trusted method for device simulation, as it is proven to be reliable and predictive, as one can easily see from the vast bibliography on this subject.
However, as Monte Carlo relies on the particle nature of the electron (in fact we consider an electron like a biliard ball), quantum effects associated with the wave-like nature of electrons cannot fully incorporated into the actual simulators, i.e. the ensemble Monte Carlo have to be lightly (or strongly, it depends on the point of view and on the methods implemented...) modified to take into account the quantum effects, at least at a first order of approximation, which is certainly enough to take into account correctly all the relevant quantum effects present in the present-day semiconductor devices (till 2015 probably...). In order to take into account the wave-like nature of electrons we use a recently introduced quantum theory, the so-called Bohm effective potential theory.
So it is challenging and very interesting to develop such a code for 2D quantum submicron semiconductor devices. This is why I have decided to implement this code, but these are not the only motivations...
The Ethical Motivations
The very sad situation you quickly observe working in a semiconductor industry, but also in all places in which researches about semiconductor devices are made, the only codes for simulation you can find are not free and are proprietary codes.
That is a very bad situation because, at the present time, if you need to develop your own code for the purpose of simulating a device it is IMPOSSIBLE to obtain an advanced one in a short time, and, trust me, this is EXTREMELY BAD for scientific research... (Immagine if you had to re-discover the Newtonian laws every time you need them...) So, you can find a huge amount of papers describing a lot of numerical methods for simulating, in a very advanced way, semiconductor devices (even in the quantum case), but nobody will give you a code on which you can construct your own method (with the unlikely exception that at least one of the programmers is a friend of yours :) ).
Even worst, if you are a semiconductor device designer and you want to simulate "realistically" a new device, you have to pay (trust me, at very high costs!) a BINARY (just a binary and not the code!) from some well-known software industry. This binary will certainly have some bugs (because it is coded by humans which are not perfect...) and you will never have the possibility of fix them on your own. Of course, you can write to the software house and tell them that there is a bug, but, how many time do you will wait for a new release without those bugs? I dont think it will be a short time...
My impression is that, after a long research on the Web for a Free Software dealing with advanced 2D semiconductor device simulation, there was not a free code for the purpose of semiconductor devices simulation (i mean under GPL license). To be sure about it, I asked to the great Richard Stallman (by mail) if it will be worth to do a code like this and he encouraged me to code it, because there wasnt a code like this as free. So I decided to write this code..
<<lessThe physics and geometry of a general device is introduced by typing a simple script, which makes, in this sense, GNU Archimedes a powerfull tool for the simulation of quite general semiconductor devices.
In the present release, GNU Archimedes is able to simulate electrons and heavy holes in Silicon and GaAs (Gamma and L-valleys) devices (holes are simulated by means of a simplified MEP model), and in the next release, which is in preparation, it will be able to make simulations in 1D, 2D and 3D (this release will be delivered as soon as possible).
The Scientifical and Industrial Motivations
In today semiconductor technology, the miniaturization of devices is more and more progressing. In this context, it is easy to see that numerical simulations play an important role at every level of device manufacture. In fact, the cost of designing and physically constructing prototypes for VLSI semiconductor devices is very high and without the availability of advanced simulators the efforts for devices miniaturization would, likely, be brought to a halt. From assessing the performance of individual transistors, to circuits and systems, and, consequently, with the promise of improved device performance, industries are encouraged to keep on miniaturizing with lower manufacture costs.
But, unfortunately, such simulations are not whithout their challenges... A first consequence of device miniaturization is that simulations of submicron semicondutor devices requires advanced transport models. Because of the presence of very high and rapidly varying electric field, phenomena occur which cannot be described by means of the well-known drift-diffusion models, which do not incorporate energy as a dynamical variable.
That is why some generalization has been sought in order to obtain more physically accurate models, like energy-transport and hydrodynamical models. The energy-transport models which are implemented in commercial simulators are based on phenomenological constitutive equations for the particle flux and energy flux depending on a set of parameters which are fitted to homogeneous bulk material Monte Carlo simulations. So, this is not, certainly, a satisfactory physical description of the internal electronic dynamics in a semiconductor device.
As current device technologies quickly approach the scales whereby quantum effects due to strong confinement of carriers and direct source-drain tunneling will begin to dominate, new simulation techniques are required in order to fully understand and acurately simulate the physics behind the technology operation.
Of all the simulation methods currently employed, ensemble Monte Carlo has always been, both in the accademic and industrial community, the most vigorous and trusted method for device simulation, as it is proven to be reliable and predictive, as one can easily see from the vast bibliography on this subject.
However, as Monte Carlo relies on the particle nature of the electron (in fact we consider an electron like a biliard ball), quantum effects associated with the wave-like nature of electrons cannot fully incorporated into the actual simulators, i.e. the ensemble Monte Carlo have to be lightly (or strongly, it depends on the point of view and on the methods implemented...) modified to take into account the quantum effects, at least at a first order of approximation, which is certainly enough to take into account correctly all the relevant quantum effects present in the present-day semiconductor devices (till 2015 probably...). In order to take into account the wave-like nature of electrons we use a recently introduced quantum theory, the so-called Bohm effective potential theory.
So it is challenging and very interesting to develop such a code for 2D quantum submicron semiconductor devices. This is why I have decided to implement this code, but these are not the only motivations...
The Ethical Motivations
The very sad situation you quickly observe working in a semiconductor industry, but also in all places in which researches about semiconductor devices are made, the only codes for simulation you can find are not free and are proprietary codes.
That is a very bad situation because, at the present time, if you need to develop your own code for the purpose of simulating a device it is IMPOSSIBLE to obtain an advanced one in a short time, and, trust me, this is EXTREMELY BAD for scientific research... (Immagine if you had to re-discover the Newtonian laws every time you need them...) So, you can find a huge amount of papers describing a lot of numerical methods for simulating, in a very advanced way, semiconductor devices (even in the quantum case), but nobody will give you a code on which you can construct your own method (with the unlikely exception that at least one of the programmers is a friend of yours :) ).
Even worst, if you are a semiconductor device designer and you want to simulate "realistically" a new device, you have to pay (trust me, at very high costs!) a BINARY (just a binary and not the code!) from some well-known software industry. This binary will certainly have some bugs (because it is coded by humans which are not perfect...) and you will never have the possibility of fix them on your own. Of course, you can write to the software house and tell them that there is a bug, but, how many time do you will wait for a new release without those bugs? I dont think it will be a short time...
My impression is that, after a long research on the Web for a Free Software dealing with advanced 2D semiconductor device simulation, there was not a free code for the purpose of semiconductor devices simulation (i mean under GPL license). To be sure about it, I asked to the great Richard Stallman (by mail) if it will be worth to do a code like this and he encouraged me to code it, because there wasnt a code like this as free. So I decided to write this code..
Download (0.57MB)
Added: 2006-06-07 License: GPL (GNU General Public License) Price:
712 downloads
WWW::Mechanize::Examples 1.30
WWW::Mechanize::Examples is a Perl module with sample programs that use WWW::Mechanize. more>>
SYNOPSIS
Plenty of people have learned WWW::Mechanize, and now, you can too!
Following are user-supplied samples of WWW::Mechanize in action.
You can also look at the t/*.t files in the distribution.
Please note that these examples are not intended to do any specific task. For all I know, theyre no longer functional because the sites they hit have changed. Theyre here to give examples of how people have used WWW::Mechanize.
Note that the examples are in reverse order of my having received them, so the freshest examples are always at the top.
Starbucks Density Calculator, by Nat Torkington
Heres a pair of scripts from Nat Torkington, editor for OReilly Media and co-author of the Perl Cookbook.
Rael [Dornfest] discovered that you can easily find out how many Starbucks there are in an area by searching for "Starbucks". So I wrote a silly scraper for some old census data and came up with some Starbucks density figures. Theres no meaning to these numbers thanks to errors from using old census data coupled with false positives in Yahoo search (e.g., "Dodie Starbuck-Your Style Desgn" in Portland OR). But it was fun to waste a night on.
Here are the top twenty cities in descending order of population, with the amount of territory each Starbucks has. E.g., A New York NY Starbucks covers 1.7 square miles of ground.
New York, NY 1.7
Los Angeles, CA 1.2
Chicago, IL 1.0
Houston, TX 4.6
Philadelphia, PA 6.8
San Diego, CA 2.7
Detroit, MI 19.9
Dallas, TX 2.7
Phoenix, AZ 4.1
San Antonio, TX 12.3
San Jose, CA 1.1
Baltimore, MD 3.9
Indianapolis, IN 12.1
San Francisco, CA 0.5
Jacksonville, FL 39.9
Columbus, OH 7.3
Milwaukee, WI 5.1
Memphis, TN 15.1
Washington, DC 1.4
Boston, MA 0.5
Download (0.10MB)
Added: 2007-07-20 License: Perl Artistic License Price:
828 downloads
QCADesigner 2.0.3
QCADesigner is a CAD-like tool for the design and simulation of circuits based on Quantum Cellular Automata. more>>
QCADesigner is the product of an ongoing research effort at the University of Calgary ATIPS Laboratory to create a design and simulation tool for Quantum Dot Cellular Automata (QCA). This tool is still under development and is provided free of cost to the research community "as is".
QCA is an emerging nanotechnology concept for the realization of a computer built with arrays of nano-scale QCA cells. These QCA cells are capable of performing all complex computational functions required for general-purpose computation.
QCA has been listed as one of the six emerging nanotechnologies with applications in future computers by the International Technology Roadmap For Semiconductors (ITRS). QCADesigner facilitates rapid design, layout and simulation of QCA circuits by providing powerful CAD features available in more complex circuit design tools.
Main features:
- Intuitive CAD-like user interface
- Easy drag-and-drop circuit design
- Encapsulated PostScript (EPS) printing
- Support for multiple layers (for signal crossover)
- Multilingual support (de hu ro fr - so far)
Enhancements:
- This is a minor bugfix release featuring an improved layer mapping dialog.
- However, the most important change is on the Windows front: The Windows version of QCADesigner now uses the Gaim version of the GTK+ Runtime Environment.
- The new version allows you to upgrade from the dropline.net version of GTK+.
<<lessQCA is an emerging nanotechnology concept for the realization of a computer built with arrays of nano-scale QCA cells. These QCA cells are capable of performing all complex computational functions required for general-purpose computation.
QCA has been listed as one of the six emerging nanotechnologies with applications in future computers by the International Technology Roadmap For Semiconductors (ITRS). QCADesigner facilitates rapid design, layout and simulation of QCA circuits by providing powerful CAD features available in more complex circuit design tools.
Main features:
- Intuitive CAD-like user interface
- Easy drag-and-drop circuit design
- Encapsulated PostScript (EPS) printing
- Support for multiple layers (for signal crossover)
- Multilingual support (de hu ro fr - so far)
Enhancements:
- This is a minor bugfix release featuring an improved layer mapping dialog.
- However, the most important change is on the Windows front: The Windows version of QCADesigner now uses the Gaim version of the GTK+ Runtime Environment.
- The new version allows you to upgrade from the dropline.net version of GTK+.
Download (2.5MB)
Added: 2005-08-04 License: GPL (GNU General Public License) Price:
1547 downloads
Secleted [ 0 ] software to compare
- Page: 1 of 2
- 1
- 2
Copyright Notice:
Software piracy is theft, Using crack, password, serial numbers, registration codes, key generators is illegal and prevent future software development. The above dallas semiconductor 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