Free elecard avc serial software for linux

LibSerial provides a collection of C++ classes that allow one to access serial ports on POSIX systems like standard C++ iostream objects.

Member functions are provided for setting various parameters of the serial ports such as the baud rate, character size, flow control and others. LibSerials idea is to simplify serial port programming on POSIX systems.

When you have installed the above tools, run the following commands:

Installation:

./configure
make
make install

Note: The html documentation will not be installed by "make install". I will fix this in the future release.

Serial Over IP is a tool for the transport of serial interfaces over UDP/IP. It is very usefull for connecting distant equipment that run via a serial interfaces to a local computer.


One linux will be server and one will be client. On the server you can start the program typing the following command:

bash# serialoverip -d /dev/ttyS0 9600-8n1 -s 127.0.0.1 3000

... and on the client:

bash# serialoverip -c 127.0.0.1 3000 -d /dev/ttyS1 9600-8n1

In both commands the IP address is the server IP. Note that you have to start the server first, and it will be efectively be running only after the first packet received from the client.

YAuCP is a collection of tools for uC (micro-controller) development. Its designed mainly for AVR uControllers and aims to develop almost every part of the development chain, ranging from software tools to hardware designs.
Enhancements:
- This release of MagicTerm features a serial port terminal with some handy features.
- In addition to the default readline behaviour it can read an arbitrary number of bytes, has working string triggers, and makes all serial port configuration options avaliable in the configuration file.
- pySerial is now required.

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

slsnif is a serial line sniffer. It listens to the specified serial port and logs all data coming through it. slsnif works transparently for both the device connected to the serial port and the controlling software for this device. It operates by opening a pseudo tty (pty) and linking it to the actual serial port.
slsnif operates by opening a pty and linking it to the serial port. These are following parameters / options:
1. Serial port to open (required).
2. Name of the file to direct output to (optional, defaults to stdout).
3. Desired baudrate (optional, defaults to 9600 baud).
4. Timestamp On/Off (optional, defaults to Off).
5. Print ascii values in hex On/Off (optional, defaults to Off)
6. Print number of bytes transmitted On/Off (optional, defaults to Off).
7. Optional colors for timestamp, number of bytes transmitted and normal output.
8. Lock port On/Off (optional, defaults to On).
9. Use Unix98 ptys instead of BSD ptys (optional, defaults to BSD style).
10. Second serial port to open. If specified, this port will be used instead of a pty, thus providing an ability to log data between two serial ports.
Enhancements:
- Added ability to resynchronize ports at any time by sending a SIGUSR1 signal to slsnif. Useful for debugging applications that change port parameters mid-way, after starting the transmission. One example is pppd daemon, which sets initial parameters in the chat script, and changes them later, after chat script terminates.
- Added ability to use SYSV (Unix98) ptys instead of BSD ones (see -u and --unix98 parameters). This option can also be turned on/off from rc-file.

MobileRemoteSE is a light (non-Java), serial-over-bluetooth-based remote control for Amarok.
Uses the Sony Ericsson AT command set, and supports the following Sony Ericsson phone models: K750, W800, Z520, W550, W600, W900, W810, Z530, W300, K510, K310, W700, Z525, W710, Z550, Z558, K320
Main features:
- Appears under "Entertainment" menu on the phone.
- Supports Play/Pause, Next, Prev, Stop, Volume Up/Down operations from mobile phone.
- Displays the current running track on Amarok in the phone menu title.
- Since J2ME is not used (unlike some other alternatives), the remote control can be used while running some other application on non-multitasking models.
Instructions:
1) Bind /dev/rfcomm0 to the serial-over-bluetooth channel of your mobile. Please refer to your distro docs or howtos on the internet to find out how to do this.
2) Install Device::Modem package for Perl. You can either use your distro packages for this, or install through CPAN as:
cpan -i Device::Modem
3) Install and start script from Amarok.

JKhepera is a Java class library for Khepera mini robots. It includes a class which allows you to open connections from a host computer to the Khepera robot via a serial interface easily.
Communication between Khepera and a computer is also simple, using methods like "setSpeed" or "readProximitySensors".
In addition, there are GUI classes to display the whole communication for debugging purposes and to control the robot manually.
Main features:
- Open Source - JKhepera is published under the terms of GPL.
- Easy to handle communication between Khepera robots and a host computer via serial interface.
- The gui component KheperaPanel, to control Khepera manually
- The gui component KheperaMonitor, to display the complete communication between Khepera and a host computer for debugging purposes
- An Interface KheperaMotionalAlgorithm, that allows the implementation of individual control algorithms (additionally to the existing BraitenbergAlgorithm) to control Khepera automatically.
- The KheperaAgent, to control Khepera by an individual algorithm in an independent thread.

COMSERV is a program that allows you to talk to a network terminal server such as a Xyplex MAXserver 1600.
The handy thing about this program is that the client side of the connection does not need to know anything about how to talk to the terminal server. COMSERV handles the connection details. Thus, you can use existing programs like tip to talk to devices attached to your network terminal server without any modification.
Also, you can use COMSERV to turn your Unix computer itself into a terminal server and serve up its own local serial ports over the network for remote systems to access. This is handy if you have several systems lying around and you want to utilize devices attached to their serial ports.
My primary motivation for writing this program was to expand the I/O capabilities of my FreeBSD home computer. I have many serial devices that I want to connect to my PC which include my modem, Palm Pilot, GPS, various micro-controllers, my EEPROM programmer, and other computers and printers. But with only two serial ports on my PC, I became annoyed at having to reach around the back of my computer and swap cables every time I wanted to plug in a different device. [I think all inventions are the product of the laziness of the inventor :-)] So I searched eBay and found a couple of these Xyplex terminal servers that looked promising, I bid on them, got them, and began hacking.
The only problem with using this type of device for serial expansion, is that if you use a program like tip on Unix (tip is a very basic but functional program to connect directly to a serial port), it expects to be able to open the serial port by opening a /dev/xyz device file that corresponds to a real serial device. The Xyplex, on the other hand, communicates to the Unix system via an ethernet network. In order to talk to one of the serial ports on the Xyplex, you need to establish a TCP/IP connection between your Unix computer and the Xyplex device at a particular TCP port. The TCP port you connect to determines which Xyplex serial port you connect to. For the Xyplex 1600, serial port 1 is TCP port 2100, serial port 2, is TCP port 2200 and so on.
Unfortuneately, tip, and programs like it, have no idea how to establish a TCP/IP connection to the Xyplex in order to transfer data to and from a serial device connected to the Xyplex.
This is what COMSERV does. COMSERV creates a set of pseudo-tty device files that are palatable to tip and other programs. COMSERV opens the master side of the pseudo terminal and the client program (tip in this case) opens the slave side. Data written on the slave endpoint comes out on the master endpoint and vice-versa. This mechanism establishes a connection between the client program and COMSERV. COMSERV then uses TCP/IP to establish a connection to the network terminal server.
Thus, data originating from the client program is written to the slave tty where is read by COMSERV. COMSERV then writes the data to the network socket to the Xyplex, which then passes it on to the designated serial port. Data originating from the serial device attached to the Xyplex takes the reverse path.
Only one instance of COMSERV is required to be running on your system to handle all of your network terminal servers (it can handle as many terminal servers and ports as the speed and resources of your system allows). COMSERV is designed to handle many connections in this fashion, and does so by multiplexing between them using asynchronous device and socket I/O.
While I wrote COMSERV to talk to a Xyplex MAXserver 1600, it should work with other manufacturers products as long as they follow a similar API. The Xyplex devices that I have are 16 port devices that connect serial devices to an ethernet network.
If COMSERV sounds useful to you, feel free to download and use it. The program is provided in source form, so you will need to extract it and compile it. If you use FreeBSD, simply do the following:
% cd /usr/ports/comms/comserv
% make install
I use it on FreeBSD 4-STABLE. I dont currently know of any outstanding bugs, but if you find and fix any bugs, please send me your fixes so that others can benefit from them as well.
If you do decide to use COMSERV, please note the accompanying license. In a nutshell, you can use it without restriction as long as you credit me and keep the copyright notice intact. If you happen to like it, feel free to send your thanks, letting me know. If you dont like it, let me know why, perhaps I can improve it. If you improve it, please send me your changes and Ill see about integrating them so that others can benefit from your improvements.
Enhancements:
- Implement a power of 2 backoff and retry for failing connections with a maximum 10 minute wait. This keeps from filling up the logs with failed repeated attempts.