Rxtx - User contributions [en]

Download

2013-06-28T02:25:11Z

Tjarvi:

== Distributables ==
RXTX 2.1 Is the main development branch for RXTX. The namespace used is gnu.io.*. Unless you have any specific reasons, this is the recommended download. If you need to be compatible with javax.comm.* then download RXTX 2.0, but note that not much development effort is provided for this branch so you will be missing out on all the fixes that the main branch is getting.

It should also be noted that there was a change in the way things were distributed. 2.1 includes a binary package that contains the binaries for the various platforms and a source package. 2.0 on the other hand is not well maintained and hard to find all of the requirements.

=== Pre-Built Binaries ===

{|
|- style="background-color: #ddddff"
! Release !! Binary !! Source
|-
| rxtx 2.1-7r2 (stable)
| [http://rxtx.qbang.org/pub/rxtx/rxtx-2.1-7-bins-r2.zip rxtx-2.1-7-bins-r2.zip]
| [http://rxtx.qbang.org/pub/rxtx/rxtx-2.1-7r2.zip rxtx-2.1-7r2.zip]
|-
| rxtx 2.0-7pre2 (stable)
| [http://rxtx.qbang.org/pub/rxtx/rxtx-2.0-7pre1-i686-pc-linux-gnu.tar.gz Linux/x86] [http://rxtx.qbang.org/pub/rxtx/rxtx-2.0-7pre1-i386-pc-mingw32.zip Win32 (incomplete)]
| [http://rxtx.qbang.org/pub/rxtx/rxtx-2.0-7pre1.tar.gz source]
|}

RXTX 2.2 will replace RXTX 2.1 once it is stable.

{|
|- style="background-color: #ddddff"
! Release !! Binary !! Source
|-
| rxtx 2.2pre2 (prerelease)
| [http://rxtx.qbang.org/pub/rxtx/rxtx-2.2pre2-bins.zip rxtx-2.2pre2-bins.zip]
| [http://rxtx.qbang.org/pub/rxtx/rxtx-2.2pre2.zip rxtx-2.2pre2.zip]
|}

TODO: The 2.2pre2 bins contain the 2.2pre1 jar file and the 2.2pre2 native lib which causes a mismatch warning

Other releases can be found in the [http://rxtx.qbang.org/pub/rxtx/ archive] and you can also check the change history in the [[change log]].

{|
|- style="background-color: #ddddff"
! How to extract the files
|-
|unzip rxtx-[].zip or
|-
|rename to rxtx-[].jar and jar -xf rxtx-[].jar;
|}

=== Eclipse Plugins ===

Eclipse Plugins of RXTX-2.1-7r2 are available for [http://rxtx.qbang.org/eclipse/downloads/ download] or as an [http://rxtx.qbang.org/eclipse/ update site].

=== ToyBox Distributables ===

The ToyBox has about 35 platforms (and growing). If you have a toy (even an s390), we have the ToyBox. Find the OS, Libc, and CPU You are looking for. Please report any problems to the mail-list. Unix users can extract zip files with jar -xf foo.zip. It works fine and on all platforms we support. Distributables can be found in the [http://rxtx.qbang.org//ToyBox ToyBox directory].

=== x64 Binaries ===

Should you wish to use RxTx on a x64 based computer, note that the downloads on this page will not work, for x64 compiled binaries go to: [http://mfizz.com/oss/rxtx-for-java Mfizz RxTx page]. Binaries have been tested successfully on Windows Server 2008 R2, although they are slightly outdated (december 2008), and known to crash when unplugging an USB serial adapter. Another option obtaining prebuilt binaries for x64 is one of the [[#Known RXTX forks]] below.

=== Other Builds ===

Several Linux distributions include RXTX in their package management system out-of-the-box, some even integrate their preinstalled RXTX with the JRE or Eclipse. Please check your distribution's package management system for "rxtx", or look at the [http://users.frii.com/jarvi/rxtx/download.html legacy downloads page] for more builds.

== Known RXTX forks ==

* [http://code.google.com/p/nrjavaserial/ NRJavaSerial]: Forked 12-Oct-2010, fairly active, with several [http://code.google.com/p/nrjavaserial/issues/list issues] reported and worked on. Automated Maven builds on several Platforms (Windows, Linux, Mac: x86 32-bit and 64-bit, as well as Linux-ARM-Android). Includes couple [http://mailman.qbang.org/pipermail/rxtx/2011-March/11981216.html improvements] for deployment and ease-of-use; extracts jar-bundled binary DLL's to a tmp folder.
* [http://code.google.com/p/create-lab-commons/source/browse/trunk/java/lib/rxtx/README.txt Create-Lab-Commons]: Forked 3-Feb-2011 (see [http://mailman.qbang.org/pipermail/rxtx/2011-February/9005917.html announcement], provides binaries for Windows, Linux and Mac (32-bit and 64-bit). Slight modifications in the code for loading the DLL's.

== Source Repository ==

If you wish to get the latest code from CVS see [[Retrieving Source Code]].

Download

2011-11-13T17:54:22Z

Tjarvi: /* Distributables */

Download

2011-07-08T04:24:55Z

Tjarvi: Reverted edits by Jeno (Talk) to last revision by Tjarvi

Download

2011-07-07T23:55:48Z

Tjarvi:

Download

2011-07-07T23:52:16Z

Tjarvi: Reverted edits by Jmorris14 (Talk) to last revision by Jamesanderson

== Distributables ==
RXTX 2.1 Is the main development branch for RXTX. The [http://www.cassetteplayer.org cassette player] namespace used is gnu.io.*. Unless you have any specific reasons, this is the recommended download. If you need to be compatible with javax.comm.* then download RXTX 2.0, but note that not much development effort is provided for this branch so you will be missing out on all the fixes that the main branch is getting.

It should also be [http://www.pacquiaomarquezfight.com pacquiao vs marquez] noted that there was a change in the way things were distributed. 2.1 includes a binary package that contains the binaries for the various platforms and a source package. 2.0 on the [http://www.url.vn Thiet ke web] [http://seoph2.cafe24.com/wordpress seo blog] [http://www.diamondlinks.net link building service][http://www.seo.url.vn SEO] [http://mesoblog.org/mesothelioma/pleural-mesothelioma.php Pleural Mesothelioma]other hand is a bit of a muddle. Things change, things improve.

Binary version <strike>rxtx 2.0-7pre1 (stable)</strike> is incomplete, at least for Windows. Use newer binary version such as <strong>rxtx 2.1-7r2 (stable)</strong>, which does work on Windows.

{|
|- style="background-color: #ddddff"
! Release !! Binary !! Source
|-
| rxtx 2.1-7r2 (stable)
| [http://rxtx.qbang.org/pub/rxtx/rxtx-2.1-7-bins-r2.zip rxtx-2.1-7-bins-r2.zip]
| [http://rxtx.qbang.org/pub/rxtx/rxtx-2.1-7r2.zip rxtx-2.1-7r2.zip]
|-
| rxtx 2.0-7pre2 (stable)
| [http://rxtx.qbang.org/pub/rxtx/rxtx-2.0-7pre1-i686-pc-linux-gnu.tar.gz Linux/x86] [http://rxtx.qbang.org/pub/rxtx/rxtx-2.0-7pre1-i386-pc-mingw32.zip Win32 (incomplete)]
| [http://rxtx.qbang.org/pub/rxtx/rxtx-2.0-7pre1.tar.gz source]
|}

RXTX 2.2 will replace RXTX 2.1 once it is stable.

{|
|- style="background-color: #ddddff"
! Release !! Binary !! Source
|-
| rxtx 2.2pre2 (prerelease)
| [http://rxtx.qbang.org/pub/rxtx/rxtx-2.2pre2-bins.zip rxtx-2.2pre2-bins.zip]
| [http://rxtx.qbang.org/pub/rxtx/rxtx-2.2pre2.zip rxtx-2.2pre2.zip]
|}

TODO: The 2.2pre2 bins contain the 2.2pre1 jar file and the 2.2pre2 native lib which causes a mismatch warning

Other releases can be found in the [http://rxtx.qbang.org/pub/rxtx/ archive] and you can also check the change history in the [[change log]].

{|
|- style="background-color: #ddddff"
! How to extract the files
|-
|unzip rxtx-[].zip or
|-
|rename to rxtx-[].jar and jar -xf rxtx-[].jar;
|}

== ToyBox Distributables ==

The ToyBox has about 35 platforms (and growing). If you have a toy (even an s390), we have the ToyBox. Find the OS, Libc, and CPU You are looking for. Please report any problems to the mail-list. Unix users can extract zip files with jar -xf foo.zip. It works fine and on all platforms we support. Distributables can be found in the [http://rxtx.qbang.org//ToyBox ToyBox ] [http://www.chickenrecipesecret.com/ directory].

== Source Repository ==

If you wish to get the latest code from CVS see [[Retrieving Source Code]].

== x64 Binaries ==

Should you wish to use RxTx on a x64 based computer, note that the downloads on this page will not work, for x64 compiled binaries go to: [http://www.cloudhopper.com/opensource/rxtx/ Cloudhopper RxTx page]. Binaries have been tested successfully on Windows Server 2008 R2, although they are slightly outdated (december 2008).

Main Page

2011-07-07T23:51:18Z

Tjarvi: Undo revision 6709 by Shepanc (Talk)

<div id="mainpage_topbox">
<div id="mainpage_pagetitle"><b>Welcome to the <strong class="selflink"><span id="mainpage_mwtitle">RXTX wiki</span></strong></b></div>

<div class="mainpage_boxcontents">
This Wiki is intended to be by and for RXTX users and developers. There is already a lot of information provided, but feel free to add your own content. Note that you will need to create an account before editing pages, as part of an effort to battle spambots.

If after checking through the Wiki you don't find an answer to your question, then you can ask your question on the [[mailing-list]]. Posting questions in the talk pages is not the right place to ask your questions.

There is also the [http://users.frii.com/jarvi/rxtx/ original RXTX website], which is still around, though most of the information has been migrated to the Wiki.

{| style="background-color: #ffffdd"
|Send mail to [mailto:tjarvi@qbang.org Trent] if you spot spambot activity.
|}
</div>
</div>

<table style="border:0; margin: 0;" width="100%" cellspacing="10">
<tr>

<td valign="top" class="mainpage_hubbox" width="25%" style="border: 1px #ddd solid;" >
<div class="mainpage_hubtitle" style="border: 1px #ddd solid; background: #016597; color: #FFF;">'''Community'''</div>
<div class="mainpage_boxcontents">
<table style="border: 0; margin: 0;" cellpadding="3">
<tr>

<td valign="top">
*[[Projects | Projects using RXTX]]
*[http://users.frii.com/jarvi/rxtx/license.html License] LGPL v2.1 + Linking Over Controlled Interface.
</td>
</tr>
</table>
</div>
</td>

<td valign="top" class="mainpage_hubbox" width="25%" style="border: 1px #ddd solid;" >
<div class="mainpage_hubtitle" style="border: 1px #ddd solid; background: #016597; color: #FFF;">'''Development and Usage'''</div>
<div class="mainpage_boxcontents">
<table style="border: 0; margin: 0;" cellpadding="3">
<tr>

<td valign="top">
* [[FAQ]]
* [[Download]]
* [[Installation]]
* [[Using RXTX]]
* [[Development]]
* [http://bugzilla.qbang.org Reporting Bugs]
</td>
</tr>
</table>
</div>
</td>

<td valign="top" class="mainpage_hubbox" width="25%" style="border: 1px #ddd solid;" >
<div class="mainpage_hubtitle" style="border: 1px #ddd solid; background: #016597; color: #FFF;">'''Quick Links'''</div>
<div class="mainpage_boxcontents">
<table style="border: 0; margin: 0;" cellpadding="3">
<tr>

<td valign="top">
* [http://users.frii.com/jarvi/rxtx/ Old RXTX home page] This wiki will be the RXTX Home Page when 2.2 is released.
</td>
</tr>
</table>
</div>
</td>

</tr>
</table>

Download

2011-05-28T02:29:57Z

Tjarvi: Reverted edits by Henryford (Talk) to last revision by Freecity

Development

2011-04-10T16:16:06Z

Tjarvi:

This page is for content regarding programming rxtx and writing programs that use rxtx. Feel free to add your own content and links.

*[[Retrieving Source Code]] - How to get the source code from CVS
*[[Development/Source Code|Source Code]] - explanation of the source code and conventions in use.
*[http://users.frii.com/jarvi/rxtx/doc/index.html gnu.io JavaDoc]
*[http://java.sun.com/products/javacomm/reference/api/index.html javax.comm JavaDoc] - provided as a point of comparison.
*[[WebStart]]
*[[Examples]]

Download

2011-04-10T15:04:44Z

Tjarvi: /* Distributables */

Download

2011-04-10T15:03:27Z

Tjarvi: /* Distributables */

Download

2011-04-10T15:01:14Z

Tjarvi: /* Distributables */

Download

2011-04-06T23:52:00Z

Tjarvi: Protected "Download" ([edit=autoconfirmed] (indefinite) [move=autoconfirmed] (indefinite))

== Distributables ==
RXTX 2.1 Is the main development branch for RXTX. The namespace used is gnu.io.*. Unless you have any specific reasons, this is the recommended download. If you need to be comptable with javax.comm.* then download RXTX 2.0, but note that not much development effort is provided for this branch so you will be missing out on all the fixes that the main branch is getting.

It should also be noted that there was a change in the way things were distributed. 2.1 includes a binary package that contains the binaries for the various platforms and a source package. 2.0 on the other hand is a bit of a muddle. Things change, things improve.

Binary version <strike>rxtx 2.0-7pre1 (stable)</strike> is incomplete, at least for Windows. Use newer binary version such as <strong>rxtx 2.1-7r2 (stable)</strong>, which does work on Windows.

{|
|- style="background-color: #ddddff"
! Release !! Binary !! Source
|-
| rxtx 2.1-7r2 (stable)
| [http://rxtx.qbang.org/pub/rxtx/rxtx-2.1-7-bins-r2.zip rxtx-2.1-7-bins-r2.zip]
| [http://rxtx.qbang.org/pub/rxtx/rxtx-2.1-7r2.zip rxtx-2.1-7r2.zip]
|-
| rxtx 2.0-7pre2 (stable)
| [http://rxtx.qbang.org/pub/rxtx/rxtx-2.0-7pre1-i686-pc-linux-gnu.tar.gz Linux/x86] [http://rxtx.qbang.org/pub/rxtx/rxtx-2.0-7pre1-i386-pc-mingw32.zip Win32 (incomplete)]
| [http://rxtx.qbang.org/pub/rxtx/rxtx-2.0-7pre1.tar.gz source]
|}

RXTX 2.2 will replace RXTX 2.1 once it is stable.

{|
|- style="background-color: #ddddff"
! Release !! Binary !! Source
|-
| rxtx 2.2pre2 (prerelease)
| [http://rxtx.qbang.org/pub/rxtx/rxtx-2.2pre2-bins.zip rxtx-2.2pre2-bins.zip]
| [http://rxtx.qbang.org/pub/rxtx/rxtx-2.2pre2.zip rxtx-2.2pre2.zip]
| [http://www.thebestpokersite.com/shop/Tables-amp-Chairs/Premium-Poker-Tables-c19/ bbo poker tables]
| [http://www.moralesvsmaidana.co.cc/2011/02/morales-vs-maidana-live-streaming/ morales vs maidana live streaming]
| [http://digital-printers.blogspot.com digital printers]
|}

TODO: The 2.2pre2 bins contain the 2.2pre1 jar file and the 2.2pre2 native lib which causes a mismatch warning

Other releases can be found in the [http://rxtx.qbang.org/pub/rxtx/ archive] and you can also check the change history in the [[change log]].

{|
|- style="background-color: #ddddff"
! UN-ZIP Procedure
|-
|cp/mv the download rxtx-[].zip to rxtx-[].jar.gz;
|gunzip rxtx-[].jar.gz;
|jar -xf rxtx-[].jar;
|}

== ToyBox Distributables ==

The ToyBox has about 35 platforms (and growing). If you have a toy (even an s390), we have the ToyBox. Find the OS, Libc, and CPU You are looking for. Please report any problems to the mail-list. Unix users can extract zip files with jar -xf foo.zip. It works fine and on all platforms we support. Distributables can be found in the [http://rxtx.qbang.org//ToyBox ToyBox directory].

== Source Repository ==

If you wish to get the latest code from CVS see [[Retrieving Source Code]].

== x64 Binaries ==

Should you wish to use RxTx on a x64 based computer, note that the downloads on this page will not work, for x64 compiled binaries go to: [http://www.cloudhopper.com/opensource/rxtx/ Cloudhopper RxTx page]. Binaries have been tested successfully on Windows Server 2008 R2, although they are slightly outdated (december 2008).

Download

2011-04-06T23:51:38Z

Tjarvi:

== Distributables ==
RXTX 2.1 Is the main development branch for RXTX. The namespace used is gnu.io.*. Unless you have any specific reasons, this is the recommended download. If you need to be comptable with javax.comm.* then download RXTX 2.0, but note that not much development effort is provided for this branch so you will be missing out on all the fixes that the main branch is getting.

It should also be noted that there was a change in the way things were distributed. 2.1 includes a binary package that contains the binaries for the various platforms and a source package. 2.0 on the other hand is a bit of a muddle. Things change, things improve.

Binary version <strike>rxtx 2.0-7pre1 (stable)</strike> is incomplete, at least for Windows. Use newer binary version such as <strong>rxtx 2.1-7r2 (stable)</strong>, which does work on Windows.

{|
|- style="background-color: #ddddff"
! Release !! Binary !! Source
|-
| rxtx 2.1-7r2 (stable)
| [http://rxtx.qbang.org/pub/rxtx/rxtx-2.1-7-bins-r2.zip rxtx-2.1-7-bins-r2.zip]
| [http://rxtx.qbang.org/pub/rxtx/rxtx-2.1-7r2.zip rxtx-2.1-7r2.zip]
|-
| rxtx 2.0-7pre2 (stable)
| [http://rxtx.qbang.org/pub/rxtx/rxtx-2.0-7pre1-i686-pc-linux-gnu.tar.gz Linux/x86] [http://rxtx.qbang.org/pub/rxtx/rxtx-2.0-7pre1-i386-pc-mingw32.zip Win32 (incomplete)]
| [http://rxtx.qbang.org/pub/rxtx/rxtx-2.0-7pre1.tar.gz source]
|}

RXTX 2.2 will replace RXTX 2.1 once it is stable.

{|
|- style="background-color: #ddddff"
! Release !! Binary !! Source
|-
| rxtx 2.2pre2 (prerelease)
| [http://rxtx.qbang.org/pub/rxtx/rxtx-2.2pre2-bins.zip rxtx-2.2pre2-bins.zip]
| [http://rxtx.qbang.org/pub/rxtx/rxtx-2.2pre2.zip rxtx-2.2pre2.zip]
| [http://www.thebestpokersite.com/shop/Tables-amp-Chairs/Premium-Poker-Tables-c19/ bbo poker tables]
| [http://www.moralesvsmaidana.co.cc/2011/02/morales-vs-maidana-live-streaming/ morales vs maidana live streaming]
| [http://digital-printers.blogspot.com digital printers]
|}

TODO: The 2.2pre2 bins contain the 2.2pre1 jar file and the 2.2pre2 native lib which causes a mismatch warning

Other releases can be found in the [http://rxtx.qbang.org/pub/rxtx/ archive] and you can also check the change history in the [[change log]].

{|
|- style="background-color: #ddddff"
! UN-ZIP Procedure
|-
|cp/mv the download rxtx-[].zip to rxtx-[].jar.gz;
|gunzip rxtx-[].jar.gz;
|jar -xf rxtx-[].jar;
|}

== ToyBox Distributables ==

The ToyBox has about 35 platforms (and growing). If you have a toy (even an s390), we have the ToyBox. Find the OS, Libc, and CPU You are looking for. Please report any problems to the mail-list. Unix users can extract zip files with jar -xf foo.zip. It works fine and on all platforms we support. Distributables can be found in the [http://rxtx.qbang.org//ToyBox ToyBox directory].

== Source Repository ==

If you wish to get the latest code from CVS see [[Retrieving Source Code]].

== x64 Binaries ==

Should you wish to use RxTx on a x64 based computer, note that the downloads on this page will not work, for x64 compiled binaries go to: [http://www.cloudhopper.com/opensource/rxtx/ Cloudhopper RxTx page]. Binaries have been tested successfully on Windows Server 2008 R2, although they are slightly outdated (december 2008).

Download

2011-04-05T14:08:25Z

Tjarvi: /* External Links */

== Distributables ==
RXTX 2.1 Is the main development branch for RXTX. The namespace used is gnu.io.*. Unless you have any specific reasons, this is the recommended download. If you need to be comptable with javax.comm.* then download RXTX 2.0, but note that not much development effort is provided for this branch so you will be missing out on all the fixes that the main branch is getting.

It should also be noted that there was a change in the way things were distributed. 2.1 includes a binary package that contains the binaries for the various platforms and a source package. 2.0 on the other hand is a bit of a muddle. Things change, things improve.

Binary version <strike>rxtx 2.0-7pre1 (stable)</strike> is incomplete, at least for Windows. Use newer binary version such as <strong>rxtx 2.1-7r2 (stable)</strong>, which does work on Windows.

{|
|- style="background-color: #ddddff"
! Release !! Binary !! Source
|-
| rxtx 2.1-7r2 (stable)
| [http://rxtx.qbang.org/pub/rxtx/rxtx-2.1-7-bins-r2.zip rxtx-2.1-7-bins-r2.zip]
| [http://rxtx.qbang.org/pub/rxtx/rxtx-2.1-7r2.zip rxtx-2.1-7r2.zip]
|-
| rxtx 2.0-7pre2 (stable)
| [http://rxtx.qbang.org/pub/rxtx/rxtx-2.0-7pre1-i686-pc-linux-gnu.tar.gz Linux/x86] [http://rxtx.qbang.org/pub/rxtx/rxtx-2.0-7pre1-i386-pc-mingw32.zip Win32 (incomplete)]
| [http://rxtx.qbang.org/pub/rxtx/rxtx-2.0-7pre1.tar.gz source]
|}

RXTX 2.2 will replace RXTX 2.1 once it is stable.

{|
|- style="background-color: #ddddff"
! Release !! Binary !! Source
|-
| rxtx 2.2pre2 (prerelease)
| [http://rxtx.qbang.org/pub/rxtx/rxtx-2.2pre2-bins.zip rxtx-2.2pre2-bins.zip]
| [http://rxtx.qbang.org/pub/rxtx/rxtx-2.2pre2.zip rxtx-2.2pre2.zip]
| [http://www.thebestpokersite.com/shop/Tables-amp-Chairs/Premium-Poker-Tables-c19/ bbo poker tables]
| [http://www.moralesvsmaidana.co.cc/2011/02/morales-vs-maidana-live-streaming/ morales vs maidana live streaming]
| [http://digital-printers.blogspot.com digital printers]
|}

TODO: The 2.2pre2 bins contain the 2.2pre1 jar file and the 2.2pre2 native lib which causes a mismatch warning

Other releases can be found in the [http://rxtx.qbang.org/pub/rxtx/ archive] and you can also check the change history in the [[change log]].

{|
|- style="background-color: #ddddff"
! UN-ZIP Procedure
|-
|cp/mv the download rxtx-[].zip to rxtx-[].jar.gz;
|gunzip rxtx-[].jar.gz;
|jar -xf rxtx-[].jar;
|}

== ToyBox Distributables ==

The ToyBox has about 35 platforms (and growing). If you have a toy (even an s390), we have the ToyBox. Find the OS, Libc, and CPU You are looking for. Please report any problems to the mail-list. Unix users can extract zip files with jar -xf foo.zip. It works fine and on all platforms we support. Distributables can be found in the [http://rxtx.qbang.org//ToyBox ToyBox directory]. [http://www.iwanttosellmydiamond.net sell a diamond]

== Source Repository ==

If you wish to get the latest code from CVS see [[Retrieving Source Code]].

== x64 Binaries ==

Should you wish to use RxTx on a x64 based computer, note that the downloads on this page will not work, for x64 compiled binaries go to: [http://www.cloudhopper.com/opensource/rxtx/ Cloudhopper RxTx page]. Binaries have been tested successfully on Windows Server 2008 R2, although they are slightly outdated (december 2008).

Download

2011-04-05T14:07:41Z

Tjarvi: Reverted edits by Tjarvi (Talk) to last revision by Brianpalmer2010

== Distributables ==
RXTX 2.1 Is the main development branch for RXTX. The namespace used is gnu.io.*. Unless you have any specific reasons, this is the recommended download. If you need to be comptable with javax.comm.* then download RXTX 2.0, but note that not much development effort is provided for this branch so you will be missing out on all the fixes that the main branch is getting.

It should also be noted that there was a change in the way things were distributed. 2.1 includes a binary package that contains the binaries for the various platforms and a source package. 2.0 on the other hand is a bit of a muddle. Things change, things improve.

Binary version <strike>rxtx 2.0-7pre1 (stable)</strike> is incomplete, at least for Windows. Use newer binary version such as <strong>rxtx 2.1-7r2 (stable)</strong>, which does work on Windows.

{|
|- style="background-color: #ddddff"
! Release !! Binary !! Source
|-
| rxtx 2.1-7r2 (stable)
| [http://rxtx.qbang.org/pub/rxtx/rxtx-2.1-7-bins-r2.zip rxtx-2.1-7-bins-r2.zip]
| [http://rxtx.qbang.org/pub/rxtx/rxtx-2.1-7r2.zip rxtx-2.1-7r2.zip]
|-
| rxtx 2.0-7pre2 (stable)
| [http://rxtx.qbang.org/pub/rxtx/rxtx-2.0-7pre1-i686-pc-linux-gnu.tar.gz Linux/x86] [http://rxtx.qbang.org/pub/rxtx/rxtx-2.0-7pre1-i386-pc-mingw32.zip Win32 (incomplete)]
| [http://rxtx.qbang.org/pub/rxtx/rxtx-2.0-7pre1.tar.gz source]
|}

RXTX 2.2 will replace RXTX 2.1 once it is stable.

{|
|- style="background-color: #ddddff"
! Release !! Binary !! Source
|-
| rxtx 2.2pre2 (prerelease)
| [http://rxtx.qbang.org/pub/rxtx/rxtx-2.2pre2-bins.zip rxtx-2.2pre2-bins.zip]
| [http://rxtx.qbang.org/pub/rxtx/rxtx-2.2pre2.zip rxtx-2.2pre2.zip]
| [http://www.thebestpokersite.com/shop/Tables-amp-Chairs/Premium-Poker-Tables-c19/ bbo poker tables]
| [http://www.moralesvsmaidana.co.cc/2011/02/morales-vs-maidana-live-streaming/ morales vs maidana live streaming]
| [http://digital-printers.blogspot.com digital printers]
|}

TODO: The 2.2pre2 bins contain the 2.2pre1 jar file and the 2.2pre2 native lib which causes a mismatch warning

Other releases can be found in the [http://rxtx.qbang.org/pub/rxtx/ archive] and you can also check the change history in the [[change log]].

{|
|- style="background-color: #ddddff"
! UN-ZIP Procedure
|-
|cp/mv the download rxtx-[].zip to rxtx-[].jar.gz;
|gunzip rxtx-[].jar.gz;
|jar -xf rxtx-[].jar;
|}

== ToyBox Distributables ==

The ToyBox has about 35 platforms (and growing). If you have a toy (even an s390), we have the ToyBox. Find the OS, Libc, and CPU You are looking for. Please report any problems to the mail-list. Unix users can extract zip files with jar -xf foo.zip. It works fine and on all platforms we support. Distributables can be found in the [http://rxtx.qbang.org//ToyBox ToyBox directory]. [http://www.iwanttosellmydiamond.net sell a diamond]

== Source Repository ==

If you wish to get the latest code from CVS see [[Retrieving Source Code]].

== x64 Binaries ==

Should you wish to use RxTx on a x64 based computer, note that the downloads on this page will not work, for x64 compiled binaries go to: [http://www.cloudhopper.com/opensource/rxtx/ Cloudhopper RxTx page]. Binaries have been tested successfully on Windows Server 2008 R2, although they are slightly outdated (december 2008).

== External Links ==

[http://www.pacquiaomosley.co.cc pacquiao vs mosley]
[http://www.antiqueszaar.com/ antique]

Download

2011-04-05T14:07:22Z

Tjarvi: Undo revision 6645 by Simonatkins (Talk)

== Distributables ==
RXTX 2.1 Is the main development branch for RXTX. The namespace used is gnu.io.*. Unless you have any specific reasons, this is the recommended download. If you need to be comptable with javax.comm.* then download RXTX 2.0, but note that not much development effort is provided for this branch so you will be missing out on all the fixes that the main branch is getting.

It should also be noted that there was a change in the way things were distributed. 2.1 includes a binary package that contains the binaries for the various platforms and a source package. 2.0 on the other hand is a bit of a muddle. Things change, things improve.

Binary version <strike>rxtx 2.0-7pre1 (stable)</strike> is incomplete, at least for Windows. Use newer binary version such as <strong>rxtx 2.1-7r2 (stable)</strong>, which does work on Windows.

{|
|- style="background-color: #ddddff"
! Release !! Binary !! Source
|-
| rxtx 2.1-7r2 (stable)
| [http://rxtx.qbang.org/pub/rxtx/rxtx-2.1-7-bins-r2.zip rxtx-2.1-7-bins-r2.zip]
| [http://rxtx.qbang.org/pub/rxtx/rxtx-2.1-7r2.zip rxtx-2.1-7r2.zip]
|-
| rxtx 2.0-7pre2 (stable)
| [http://rxtx.qbang.org/pub/rxtx/rxtx-2.0-7pre1-i686-pc-linux-gnu.tar.gz Linux/x86] [http://rxtx.qbang.org/pub/rxtx/rxtx-2.0-7pre1-i386-pc-mingw32.zip Win32 (incomplete)]
| [http://rxtx.qbang.org/pub/rxtx/rxtx-2.0-7pre1.tar.gz source]
|}

RXTX 2.2 will replace RXTX 2.1 once it is stable.

{|
|- style="background-color: #ddddff"
! Release !! Binary !! Source
|-
| rxtx 2.2pre2 (prerelease)
| [http://rxtx.qbang.org/pub/rxtx/rxtx-2.2pre2-bins.zip rxtx-2.2pre2-bins.zip]
| [http://rxtx.qbang.org/pub/rxtx/rxtx-2.2pre2.zip rxtx-2.2pre2.zip]
|}

TODO: The 2.2pre2 bins contain the 2.2pre1 jar file and the 2.2pre2 native lib which causes a mismatch warning

Other releases can be found in the [http://rxtx.qbang.org/pub/rxtx/ archive] and you can also check the change history in the [[change log]].

{|
|- style="background-color: #ddddff"
! UN-ZIP Procedure
|-
|cp/mv the download rxtx-[].zip to rxtx-[].jar.gz;
|gunzip rxtx-[].jar.gz;
|jar -xf rxtx-[].jar;
|}

== ToyBox Distributables ==

The ToyBox has about 35 platforms (and growing). If you have a toy (even an s390), we have the ToyBox. Find the OS, Libc, and CPU You are looking for. Please report any problems to the mail-list. Unix users can extract zip files with jar -xf foo.zip. It works fine and on all platforms we support. Distributables can be found in the [http://rxtx.qbang.org//ToyBox ToyBox directory]. [http://www.iwanttosellmydiamond.net sell a diamond]

== Source Repository ==

If you wish to get the latest code from CVS see [[Retrieving Source Code]].

== x64 Binaries ==

Should you wish to use RxTx on a x64 based computer, note that the downloads on this page will not work, for x64 compiled binaries go to: [http://www.cloudhopper.com/opensource/rxtx/ Cloudhopper RxTx page]. Binaries have been tested successfully on Windows Server 2008 R2, although they are slightly outdated (december 2008).

== External Links ==

[http://www.pacquiaomosley.co.cc pacquiao vs mosley]
[http://www.antiqueszaar.com/ antique]

Wrapping RXTX in an Eclipse Plugin

2011-03-16T01:11:57Z

Tjarvi: Undo revision 6574 by Haleigha28 (Talk)

This would be done to simplify the development of [[http://www.eclipse.org/ Eclipse]] Plug-ins and RCP applications that use rxtx.

Wrapping this code in a plug-in gives the following advantages:
*A link to the javadoc can be associated with the jar, so users of the newly created plug-in can easily pull up the javadoc inside eclipse.
*The native libraries can all be associated with this jar, so the newly created plug-in can support multiple targets OS & CPU architectures.
*Associating the javadoc and grabbing the right native library only has to be done once for all projects using rxtx.
*You don't have to modify the JRE of any machine. Eclipse will package the jar and corresponding native libraries in your RCP/plug-in application. Upon startup, it will select the appropriate .dll or .so file to unpack and add the .jar file to the classpath.

Please note that I've used my RXTX plugin for Mac OS X (ppc) and Windows (x86) only. I haven't tested this configuration on the other targets setup in this tutorial.

==Procedure (Using Eclipse 3.3 - Europa)==
*In the New Project Wizard, select Plug-in Development->Plug-in from existing JAR archives and click Next.
*Use the Add External... button to add the downloaded RXTXcomm.jar file to include in the plugin and click Next.
*Fill in the Plug-in Project Properties and click Finish. '''Make sure "Unzip the JAR archives into the project" is unchecked''' or you will not be able to associate the javadoc. Otherwise, you can do what you want. Here's an example:
**Project Name: rxtx plugin
**Plug-in ID: org.rxtx
**Plug-in Version: (insert the version of rxtx that your are wrapping)
**Plug-in Name: rxtx Plug-in
**Plug-in Provider: rxtx.org
*You will now see your new plugin project in the Package Explorer. Notice that if you open the manifest, META-INF->MANIFEST.MF, in the editor and switch to the Runtime tab, you will find gnu.io in the Exported Packages (and also RXTXcomm.jar in the Classpath). This is what lets you use the java libraries when you include this new plugin in your dependency list.
*Create a new folder in your project called nativelib (or whatever you want).
*Import all the native libraries (.dll, .so, etc.) from your rxtx download under this folder.
*Add the following [http://www.osgi.org/ OSGI] directive to the Manifest to tell the OSGI framework how to select the appropriate native libs at startup (MANIFEST.MF tab of the MANIFEST editor).
**Make sure to have single spaces in the following locations: After the Bundle-Nativecode: directive, on all line continuations, and on all blank lines.
**Make sure to adjust the folder structure to your folder structure.
**Make sure to change the file names to the appropriate ones (i.e. the files that have the version number in them might change).
**Make sure to adjust the native lib references to the ones that you actually have.
**''Please note that I'm not sure about the OSGI processor name, Sparc64.''
<pre>
Bundle-NativeCode:
nativelib/Linux/i686-unknown-linux-gnu/librxtxParallel.so;
nativelib/Linux/i686-unknown-linux-gnu/librxtxSerial.so;
osname=Linux; processor=x86,

nativelib/Linux/ia64-unknown-linux-gnu/librxtxSerial.so;
osname=Linux; processor=ia64,

nativelib/Linux/x86_64-unknown-linux-gnu/librxtxSerial.so;
osname=Linux; processor=x86-64,

nativelib/Mac_OS_X/librxtxSerial.jnilib;
osname=Mac OS X; processor=x86; processor=PowerPC; processor=x86-64,

nativelib/Solaris/sparc-solaris/sparc32-sun-solaris2.8/librxtxSerial-2.1-7.so;
nativelib/Solaris/sparc-solaris/sparc32-sun-solaris2.8/librxtxSerial.so;
osname=Solaris; processor=Sparc,

nativelib/Solaris/sparc-solaris/sparc64-sun-solaris2.8/librxtxSerial-2.1-7.so;
nativelib/Solaris/sparc-solaris/sparc64-sun-solaris2.8/librxtxSerial.so;
osname=Solaris; processor=Sparc64,

nativelib/Windows/i368-mingw32/rxtxParallel.dll;
nativelib/Windows/i368-mingw32/rxtxSerial.dll;
osname=Win32; processor=x86
</pre>
*Right click on the .jar file (Referenced Libraries->RXTXComm.jar and select Properties
*Select Javadoc Location and enter the link to this wiki's javadoc (i.e. http://users.frii.com/jarvi/rxtx/doc/). Use the Validate... button to make sure you have it right (Make sure index.html is not at the end of your link). Click Apply and then OK.

You're done! Now you can use this plugin in your other projects as long as it remains open in your project directory. If you like, you can use the Export Wizard in the Overview tab of the manifest editor to distribute this. You can even create a feature project and include this plug-in if you want to distribute via an eclipse update site. The feature project is nice in any case from a usability standpoint because it allows you to specify all of the target OS's and architectures (CPU's) this supports.

Projects

2011-03-16T01:00:10Z

Tjarvi: Reverted edits by Venkat (Talk) to last revision by Wido

This page lists (some of) the projects that are using RXTX. Links are either to the projects home web pages, or to a Wiki page here that talks about how the project uses RXTX. See also the [http://users.frii.com/jarvi/rxtx/projects.html original RXTX projects page].

{| class="wikitable sortable"
|- style="background: #dddddd;"
! Project
! Description
! Source available
! License
|-
| [http://jmri.sourceforge.net/ JMRI]
| Software for model railroads
|
|
|-
| [http://www.bikeXperience.de BikeXperience]
| Software for manage of cycling computers (German Site)
| <center>No</center>
| <center>Donateware</center>
|-
| [http://home.arcor.de/i.fischer/modelledit/ ModellEditor]
| Software to edit models in r/c-transmitter.
| <center>No</center>
| <center>Donateware</center>
|-
| [http://www.code-skin.com/c2oooProg.html C2oooProg]
| Flash programmer for TI C2000 DSPs.
|
|
|-
| [http://www.sump.org/projects/analyzer/ Sump's Logic Analyzer]
| Home made FPGA based analyzer with Java client.
|
|
|-
| [http://triptracker.sourceforge.net/ Trip Tracker]
| A GPS based real time position tracking client-server system.
| <center>Yes</center>
| <center>GPL</center>
|-
| [http://www.lavrsen.dk/twiki/bin/view/Open2300/OpenJ2300 OpenJ2300]
| Software for driving the Lacross 23** series weather stations.
|
|
|-
| [http://adtpro.sourceforge.net/ ADTPro]
| Communications package for transfering Apple II-era diskettes and hard drives.
| <center>Yes</center>
| <center>GPL</center>
|-
| [http://a2gameserver.berlios.de/ Apple Game Server]
| Sends games directly to an old Apple // computer without floppies.
| <center>Yes</center>
| <center>GPL</center>
|-
| [http://vars.sourceforge.net/ Video Annotation and Reference System]
| Software for creating and managing video annotations.
|
|
|-
| [http://code.google.com/p/vcr4j/ VCR4J]
| A Java API for communicating with video cassette recorders
|
|
|-
| [http://remotej.sourceforge.net/ Remotej]
| RemoteJ is an application for adding remote control capability to your k750 like mobile phone.
| <center>Yes</center>
| <center>GPL</center>
|-
| [http://www.jcontrol.org// JControl]
| Java platform optimized for measurement, control and automation applications.
| <center>No</center>
| <center></center>
|-
| [http://jergometer.org/ JErgometer]
| Java ergometer software that communicates with Kettler ergometers.
| <center>Yes</center>
| <center>GPLv2</center>
|-
| [http://gpsmap.sourceforge.net/ GPSMap]
| Application that is able to display maps like in an atlas and show your position by the use of a gps device.
| <center>Yes</center>
| <center>LGPL</center>
|-
| [http://servomaster.sourceforge.net/ ServoMaster]
| Project dedicated to providing a consistent hardware independent way of controlling the servos with a PC.
| <center>Yes</center>
| <center>GPL/LGPL</center>
|-
| [http://jreceiver.sourceforge.net/ JReceiver]
| Servlet-based audio server
| <center>Yes</center>
| <center>BSD</center>
|-
| [http://www.javapos.com/jcl.html JavaPOS]
| Solution for supporting multiple POS configurations.
| <center>Yes</center>
| <center>CPL</center>
|-
| [http://jcrystal.com/steffenweber/JAVA/ipc/IPR.html IPR/IPC]
| IPR is a companion program to IPC. IPR is a software for controlling our MAC-Science IP-reader.
| <center>No</center>
|
|-
| [http://www.itl.nist.gov/div897/ctg/aroma/pages/projector/proj3.html The Aroma Project]
| Remote Projector Control/Display Solution.
|
|
|-
| [http://rossum.sourceforge.net/ The Rossum Project]
| Open-source robotics project
| <center>Yes</center>
| <center>GPL</center>
|-
| [http://www.iau.dtu.dk/~lego/lego3/rcxcomm/ rcxcomm]
| Communication package for leJOS
| <center>No</center>
|
|-
| [http://www.linuxha.com/ Linux Home Automation]
| Home automation and home control (HA) Software
| <center>Yes</center>
|
|-
| [http://jusb.sourceforge.net/?selected=types jUSB]
| Java API for USB.
| <center>Yes</center>
| <center>GPL/LGPL</center>
|
|-
| [http://bt747.free.fr BT747]
| Software for configuring, downloading data from and conversion thereof related to MTK Chipset GPS Loggers.
| <center>Yes</center>
| <center>GPL V3</center>
|
|-
| [http://taiyaki.googlecode.com Taiyaki]
| Home automation solution working with an iPhone
| <center>Yes</center>
| <center>GPL</center>
|
|-
| [http://sourceforge.net/projects/tolk Tolk]
| RFID Sensor Network - developers framework
| <center>Yes</center>
| <center>BSD</center>
|-
| [http://sourceforge.net/projects/modbuspal ModbusPal]
| Realistic Modbus slaves simulator
| <center>Yes</center>
| <center>GPL</center>
|-
| [http://tlcdcemu.sourceforge.net TLCDCemu]
| Tuner List CD Changer Emulator for Renault cars
| <center>Yes</center>
| <center>GPL</center>
|-
| [http://ggc.sourceforge.net GGC]
| Gnu Gluco Control - application for managing diabetes
| <center>Yes</center>
| <center>LGPL</center>
|-
| [http://sourceforge.net/projects/vna-j vna/J]
| Control program for miniRadioSolutions miniVNA vector-network-analyzer.
| <center>Yes</center>
| <center>GPL</center>
|-
| [http://sourceforge.net/projects/drivewireserver/ DriveWire]
| A drive block and networking server for the TRS-80 Color Computer family
| <center>Yes</center>
| <center>GPL</center>
|-
| [http://www.pbcontrol.net/ PBControl]
| A platform independent program for controller paintball game (competitions) flag stations.
| <center>Yes</center>
| <center>BSD</center>
|}

Note: when adding you project to the list, please try to keep the description short and to the point. It should not be longer than one sentence or line, in order to keep the formatting of the table consistent. Also note this page does not currently list all projects on the [http://users.frii.com/jarvi/rxtx/projects.html original RXTX projects page], so if you have time please copy over the ones which aren't listed here yet.

Download

2011-03-16T00:57:00Z

Tjarvi:

Download

2011-03-16T00:54:24Z

Tjarvi: Reverted edits by Venkat (Talk) to last revision by Randybosh

== Distributables ==
RXTX 2.1 Is the main development branch for RXTX. The namespace used is gnu.io.*. Unless you have any specific reasons, this is the recommended download. If you need to be comptable with javax.comm.* then download RXTX 2.0, but note that not much development effort is provided for this branch so you will be missing out on all the fixes that the main branch is getting.

It should also be noted that there was a change in the way things were distributed. 2.1 includes a <span class="plainlinks">[http://www.merchantos.com <span style="color:black;font-weight:normal; text-decoration:none!important; background:none!important; text-decoration:none;">point of sale system</span>] binary package that contains the binaries for the various platforms and a source package. 2.0 on the other hand is a bit of a muddle. Things change, things improve.

Binary version <strike>rxtx 2.0-7pre1 (stable)</strike> is incomplete, at least for Windows. Use newer binary version such as <strong>rxtx 2.1-7r2 (stable)</strong>, which does work on Windows.

{|
|- style="background-color: #ddddff"
! Release !! Binary !! Source
|-
| rxtx 2.1-7r2 (stable)
| [http://rxtx.qbang.org/pub/rxtx/rxtx-2.1-7-bins-r2.zip rxtx-2.1-7-bins-r2.zip]
| [http://rxtx.qbang.org/pub/rxtx/rxtx-2.1-7r2.zip rxtx-2.1-7r2.zip]
|-
| rxtx 2.0-7pre2 (stable)
| [http://rxtx.qbang.org/pub/rxtx/rxtx-2.0-7pre1-i686-pc-linux-gnu.tar.gz Linux/x86] [http://rxtx.qbang.org/pub/rxtx/rxtx-2.0-7pre1-i386-pc-mingw32.zip Win32 (incomplete)]
| [http://rxtx.qbang.org/pub/rxtx/rxtx-2.0-7pre1.tar.gz source]
|}

RXTX 2.2 will replace RXTX 2.1 once it is stable.

{|
|- style="background-color: #ddddff"
! Release !! Binary !! Source
|-
| rxtx 2.2pre2 (prerelease)
| [http://rxtx.qbang.org/pub/rxtx/rxtx-2.2pre2-bins.zip rxtx-2.2pre2-bins.zip]
| [http://rxtx.qbang.org/pub/rxtx/rxtx-2.2pre2.zip rxtx-2.2pre2.zip]
|}

TODO: The 2.2pre2 bins contain the 2.2pre1 jar file and the 2.2pre2 native lib which causes a mismatch warning

Other releases can be found in the [http://rxtx.qbang.org/pub/rxtx/ archive] and you can also check the change history in the [[change log]].

{|
|- style="background-color: #ddddff"
! UN-ZIP Procedure
|-
|cp/mv the download rxtx-[].zip to rxtx-[].jar.gz;
|gunzip rxtx-[].jar.gz;
|jar -xf rxtx-[].jar;
|}

== ToyBox Distributables ==

The ToyBox has about 35 platforms (and growing). If you have a toy (even an s390), we have the ToyBox. Find the OS, Libc, and CPU You are looking for. Please report any problems to the mail-list. Unix users can extract zip files with jar -xf foo.zip. It works fine and on all platforms we support. Distributables can be found in the [http://rxtx.qbang.org//ToyBox ToyBox directory].

== Source Repository ==

If you wish to get the latest code from CVS see [[Retrieving Source Code]].

== x64 Binaries ==

Should you wish to use RxTx on a x64 based computer, note that the downloads on this page will not work, for x64 compiled binaries go to: [http://www.cloudhopper.com/opensource/rxtx/ Cloudhopper RxTx page]. Binaries have been tested successfully on Windows Server 2008 R2, although they are slightly outdated (december 2008).

Retrieving Source Code

2011-01-28T15:55:04Z

Tjarvi:

Note: CVS is not intended for people looking for a stable copy of the rxtx package. If your interested in submitting changes via CVS please email taj@www.linux.org.uk.

Feel free to examine the latest CVS copy of rxtx. CVS information is now included in the latest source tar archives. After extracting the files from the tar archive simply change into the rxtx directory and type 'cvs update' to get the latest changes. One may also get the latest changes without downloading the tar files...

*CVSROOT=:pserver:anonymous@qbang.org:/var/cvs/cvsroot

*PASSWORD is not required.

The following is an example session checking out via cvs.

Note: there are two branches of RXTX, which should not be confused. The first branch is for the javax.comm based library and the second is for the gnu.io based library. The former does not include the javax.comm jar file, so you will need to ensure you have it to do development with it.

Follows are steps to follow for a typical checkout.

[user@myhost]$ export CVSROOT=:pserver:anonymous@qbang.org:/var/cvs/cvsroot
[user@myhost]$ cvs login
(Logging in to anonymous@qbang.org)
CVS password:

Password is not required.

If you want the 'gnu.io' (recommended) native library, and Java source (this corresponds to the 2.1/2.2 branch):

[user@myhost]$ temp]$ cvs checkout -r commapi-0-0-1 rxtx-devel

or if you want the 'javax.comm' native library (this corresponds to the 2.0 branch):

[user@myhost]$ temp]$ cvs checkout rxtx-devel

At this point the source code will be retrieved and placed in the local directory 'rxtx-devel'.

If you want at a later date you wish to update the source code, using the same branch, then from the directory containing the rxtx-devel folder, follow the instructions as for the checkout, but instead of the checkout command use:

cvs update rxtx-devel

Main Page

2011-01-28T15:53:29Z

Tjarvi:

Writing "Hello World" to a USB to serial converter

2010-01-29T20:03:13Z

Tjarvi: /* Installing JavaVM and RXTX */

== General Instructions ==
This example shows how write a Java program to write out "Hello World" to a serial port or to a USB to serial converter. Before you start you will need to ensure that a suitable Java VM is installed, along with the RXTX Libraries (see platform specifc instructions below).

These instructions all make use of the [http://java.sun.com/developer/releases/javacomm/SimpleWrite.java SimpleWrite.java] example file, which you will need to download. Once downloaded to a folder of your choice, from an editor:

*Change the third import statement "import javax.comm.*;" to read:

<pre> import gnu.io.*; </pre>

*Change the line "String defaultPort = "/dev/term/a";" to refer to your serial device (see platform specifc instructions below). For example on Windows:

<pre> String defaultPort = "COM4"; </pre>

This Java program can be compiled and run by typing the following from the command line:

<pre>
javac SimpleWrite.java
java SimpleWrite
</pre>

"Hello World" should then appear on the device connected to the serial port, assuming that it has been set up to receive a 9600 baud rate, 8 data bits, 1 stop bit, no parity and no handshaking.

== Windows XP ==

=== Installing JavaVM and RXTX ===

[http://java.sun.com/javase/downloads/index.jsp Download] and Install Sun's Java software (JDK 6 Update 3 at time of writing). The JDK files are placed at C:\Program Files\Java\jdk1.6.0_03\ and the runtime files are placed at C:\Program Files\Java\jre1.6.0_03\. Ensure the System Variable "path" (held in My Computer->properties->Advanced->Environment Varables->System Variables) includes ";C:\Program Files\Java\jdk1.6.0_03\bin" at the end.

{| style="background-color: #ffffee"
| Note: JDK 1.4 will work with RXTX, but there is not harm in being up to date.
|}

Install RxTx. This involves placing rxtxSerial.dll and rxtxParallell.dll in both C:\Program Files\Java\jdk1.6.0_03\jre\bin and C:\Program Files\Java\jre1.6.0_03\bin. It also involves placing RXTXcomm.jar in both C:\Program Files\Java\jdk1.6.0_03\jre\lib\ext and C:\Program Files\Java\jre1.6.0_03\lib\ext.

=== The Serial Port Name ===

If the machine doesn't have a serial port, install a USB to serial converter following the manufacturer's instructions. Select My Computer->Properties->Hardware->Device Manager->Ports(COM&LPT)->USB - Serial Comm Port (COM4). This shows a COM port to which the device was installed - in this case COM4.

Serial ports on MS-Windows based systems are of the form COMn, where n is a number. For example COM4. To define the variable in the example program:

<pre>
String defaultPort = "COM4";
</pre>

== UBUNTU Linux ==

=== Installing JavaVM and RXTX ===

Sun Java RTE is installed at /usr/lib/jvm/java-1.5.0-sun-1.5.0.06/jre and RXTXcomm.jar must be placed at /usr/lib/jvm/java-1.5.0-sun-1.5.0.06/jre/lib/ext and the librxtxSerial.so and librxtxParallel.so files are placed at /usr/lib/jvm/java-1.5.0-sun-1.5.0.06/jre/lib/i386.

=== The Serial Port Name ===

On Unix machines the serial port ID can be found by typing:

<pre>
sudo dmesg | grep tty
</pre>

This is likely to show the port to be "/dev/ttyS0".

The defaultPort line in the SimpleWrite Java file (see above) must now be changed to:

<pre>
String defaultPort = "/dev/ttyS0";
</pre>

== MacOS X ==

=== Installing JavaVM and RXTX ===

MacOS X already comes with a JavaVM installed, so you will not need to install one.

The first thing to do is ensure that the java library and the native library are available to your program. If you want them to be available to all programs, then the standard locations are:
* /Library/Java/Extensions - to make available to all users
* ~/Library/Java/Extensions - to make available to only your user

Also, if you are using an IDE such as Eclipse, you can opt to include them in your project instead. If your project is MyHelloWorld then locations would be:
* MyHelloWorld/lib/RXTXcomm.jar
* MyHelloWorld/librxtxSerial.jnilib
Don't forget to include them in your build path.

=== The Serial Port Name ===
On MacOS X serial devices have a 'device file' defined in <tt>/dev</tt>, and are of the form tty.* or cu.*. If you don't see the one corresponding to your device then you probably don't have the appropriate driver installed. Bluetooth devices and 'USB to RS232' all appear as serial devices. If you have device called <tt>/dev/tty.mydevice</tt>, then in the SimpleWrite.java file change the value of the 'defaultPort' variable to refer to it:

<pre>
String defaultPort = "/dev/tty.mydevice";
</pre>

Main Page

2010-01-29T19:59:01Z

Tjarvi: Reverted edits by AmeliaEera (Talk) to last revision by Rbreznak

<div id="mainpage_topbox">
<div id="mainpage_pagetitle"><b>Welcome to the <strong class="selflink"><span id="mainpage_mwtitle">RXTX wiki</span></strong></b></div>

<div class="mainpage_boxcontents">
This Wiki is intended to be by and for RXTX users and developers. There is already a lot of information provided, but feel free to add your own content. Note that you will need to create an account before editing pages, as part of an effort to battle spambots.

If after checking through the Wiki you don't find an answer to your question, then you can ask your question on the [[mailing-list]]. Posting questions in the talk pages is not the right place to ask your questions.

There is also the [http://users.frii.com/jarvi/rxtx/ original RXTX website], which is still around, though most of the information has been migrated to the Wiki.

{| style="background-color: #ffffdd"
|Send mail to [mailto:tjarvi@qbang.org Trent] if you spot spambot activity.
|}
</div>
</div>

<table style="border:0; margin: 0;" width="100%" cellspacing="10">
<tr>

<td valign="top" class="mainpage_hubbox" width="25%" style="border: 1px #ddd solid;" >
<div class="mainpage_hubtitle" style="border: 1px #ddd solid; background: #016597; color: #FFF;">'''Community'''</div>
<div class="mainpage_boxcontents">
<table style="border: 0; margin: 0;" cellpadding="3">
<tr>

<td valign="top">
*[[Projects | Projects using RXTX]]
*[http://users.frii.com/jarvi/rxtx/license.html License] LGPL v2.1 + Linking Over Controlled Interface.
</td>
</tr>
</table>
</div>
</td>

<td valign="top" class="mainpage_hubbox" width="25%" style="border: 1px #ddd solid;" >
<div class="mainpage_hubtitle" style="border: 1px #ddd solid; background: #016597; color: #FFF;">'''Development and Usage'''</div>
<div class="mainpage_boxcontents">
<table style="border: 0; margin: 0;" cellpadding="3">
<tr>

<td valign="top">
* [[FAQ]]
* [[Download]]
* [[Installation]]
* [[Using RXTX]]
* [[Development]]
* [http://bugzilla.qbang.org Reporting Bugs]
</td>
</tr>
</table>
</div>
</td>

<td valign="top" class="mainpage_hubbox" width="25%" style="border: 1px #ddd solid;" >
<div class="mainpage_hubtitle" style="border: 1px #ddd solid; background: #016597; color: #FFF;">'''Quick Links'''</div>
<div class="mainpage_boxcontents">
<table style="border: 0; margin: 0;" cellpadding="3">
<tr>

<td valign="top">
* [http://www.rxtx.org Old RXTX home page] This wiki will be the RXTX Home Page when 2.2 is released.
</td>
</tr>
</table>
</div>
</td>

</tr>
</table>

Retrieving Source Code

2009-08-31T23:13:34Z

Tjarvi:

Note: CVS is not intended for people looking for a stable copy of the rxtx package. If your interested in submitting changes via CVS please email taj@www.linux.org.uk.

Feel free to examine the latest CVS copy of rxtx. CVS information is now included in the latest source tar archives. After extracting the files from the tar archive simply change into the rxtx directory and type 'cvs update' to get the latest changes. One may also get the latest changes without downloading the tar files...

*CVSROOT=:pserver:anonymous@qbang.org:/var/cvs/cvsroot

*PASSWORD is not required.

The following is an example session checking out via cvs.

Note: there are two branches of RXTX, which should not be confused. The first branch is for the javax.comm based library and the second is for the gnu.io based library. The former does not include the javax.comm jar file, so you will need to ensure you have it to do development with it.

Follows are steps to follow for a typical checkout.

[user@myhost]$ export CVSROOT=:pserver:anonymous@qbang.org:/var/cvs/cvsroot
[user@myhost]$ cvs login
(Logging in to anonymous@qbang.org)
CVS password:

Password is not required.

If you want the 'gnu.io' (recommended) native library, and Java source (this corresponds to the 2.1 branch):

[user@myhost]$ temp]$ cvs checkout -r commapi-0-0-1 rxtx-devel

or if you want the 'javax.comm' native library (this corresponds to the 2.0 branch):

[user@myhost]$ temp]$ cvs checkout rxtx-devel

At this point the source code will be retrieved and placed in the local directory 'rxtx-devel'.

If you want at a later date you wish to update the source code, using the same branch, then from the directory containing the rxtx-devel folder, follow the instructions as for the checkout, but instead of the checkout command use:

cvs update rxtx-devel

FAQ

2009-07-20T02:24:25Z

Tjarvi: Undo revision 6496 by DelroLraca (Talk)

== General ==

=== What is RXTX? ===

RXTX is a Java library, using a native implementation (via JNI), providing serial and parallel communication for the Java Development Toolkit (JDK). All deliverables are under the GNU LGPL license. It is based on the specification for Sun's [http://java.sun.com/products/javacomm/index.jsp Java Communications API], though while many of the class descriptions are the same the package used it not, since gnu.io is used instead. A certain amount of compatibility is intended with API, though this project should be considered as a fork and therefore compatible in spirit, but not in implementation.

=== Do you have a Mailing List? ===

Yes, see the [[mailing-list]] page for details.

=== Where can I find information about how to write apps using RXTX? ===

Take a look at the [[Examples]]

=== What does RXTX install where? ===

The RXTX installation procedures installs files directly underneath $JAVA_HOME, i.e. directly into the JDK distribution.

In case you are using the Sun JDK:

The 'gnu.io' Java .class files are all packed into:

$JAVA_HOME/jre/lib/ext/RXTXcomm.jar

The [http://en.wikipedia.org/wiki/Library_(computer_science)#Shared_library Shared Object] files necessary to access OS-level functionality can be found underneath:

$JAVA_HOME/jre/lib/<architecture>/

and they are:

librxtxI2C-2.1-7.so
librxtxI2C.la
librxtxI2C.so -> librxtxI2C-2.1-7.so

librxtxParallel-2.1-7.so
librxtxParallel.la
librxtxParallel.so -> librxtxParallel-2.1-7.so

librxtxRaw-2.1-7.so
librxtxRaw.la
librxtxRaw.so -> librxtxRaw-2.1-7.so

librxtxRS485-2.1-7.so
librxtxRS485.la
librxtxRS485.so -> librxtxRS485-2.1-7.so

librxtxSerial-2.1-7.so
librxtxSerial.la
librxtxSerial.so -> librxtxSerial-2.1-7.so

Also see the '[[installation]]' page for more information.

=== Is there a Change Log? ===

Yes, see the '[[Change Log]]' page.

=== What License does RXTX use? ===

RXTX is license under the LGPL with an exception for linking over controlled interfaces, a copy of which can be found in the '[[License]]' page. The exception allows people to use RXTX as a service plugin with Sun's CommAPI: 'A Controlled Interface.'

=== What Platforms does RXTX run on? ===

See the page entitled '[[Porting]]', for more information.

== Problems and Workarounds ==

=== On MacOS X I get a 'PortInUseException', even though it isn't? ===

Versions prior to 2.1-8 use lock files, which is not the MacOS X way of doing things, and therefore has issues. For this reason make sure that you have version 2.1-8 or higher, which makes use of [http://developer.apple.com/documentation/DeviceDrivers/Conceptual/IOKitFundamentals/ I/O Kit]. At this point in time 2.1-8 is only availble from CVS, in source form. See the section [[Retrieving Source Code]], on getting the latest code - be sure to get the code from the 'gnu.io' branch.

'TODO': Can anyone who knows how please make an easy download available like the 2.1-7 version?
There you go: http://www.mediafire.com/download.php?zx1hlhghyyh
'TODO': Can anyone who knows how please upload this file to rxtx.org?

=== RXTX does not find my device, what's wrong? ===

There may be a number of reasons, but most often it is because your operating system can't find it either. RXTX is built upon the functionality provided by your operating system, and therefore is dependent on its limitations. For this reason find out whether your system can find the port, if it can and you still can't work what is going on, then there may be some help on the [[Mailing-List]].

You can specify the available ports by
System.setProperty("gnu.io.rxtx.SerialPorts", portFileNames);
where the file names of the ports are separated by File.pathSeparator.

=== RXTX installation fails with JDK 1.6 ===

This applies to the source package of RXTX 2.1-7r2.

After having run ''./configure; make; make install'', the following message appears:

make all-am
make[1]: Entering directory `/<mumble mumble your directory>/rxtx-2.1-7r2'
make[1]: Nothing to be done for `all-am'.
make[1]: Leaving directory `/<mumble mumble your directory>/rxtx-2.1-7r2'
libtool: install: `x86_64-unknown-linux-gnu/librxtxRS485.la' is not a directory
Try `libtool --help --mode=install' for more information.
make: *** [install] Error 1

This is caused by a missing case in the 'configure' script generated from 'configure.in', which
causes the variable RXTX_PATH to not be set which causes the above confusion.
You can change the 'configure' script directly. Look for the case instruction that matches JDK version strings:

1.2*|1.3*|1.4*|1.5*

and extend it to

1.2*|1.3*|1.4*|1.5*|1.6*

Note that there are matches for Linux, BSD, Solaris and Win32.

Then run ''./configure; make; make install'' as usual.

=== RXTX and the Equinox SST-4P/LP multiport card ===

A note for those who want to install an Equinox board (in this case "SST-4P/LP") and try to
run it with RXTX under Linux (in this case, Red Hat ES 4)

Get the driver source from the [http://www.equinox.com/support/download-drivers/ www.equinox.com driver page] and
compile it as described therein.

The four serial ports of the Equinox SST-4P are available as the device files:

/dev/ttyQ1a1 ... /dev/ttyQ1a4

These device files are created by the 'ssmkn' (alias 'make device nodes') executable.

In order to make things work, you have to:

Modify the 'eqnx' startup script '/etc/rc.d/init.d/eqnx'
and make it set the permissions of the devices files in the
'start' section, immediately after the call to 'ssmkn':

# create device files
/usr/bin/ssmkn
# fix rights on device files
LIST=`ls /dev/ttyQ*`
for DEV in $LIST; do
chown root.uucp $DEV
chmod 660 $DEV
done

Modify 'src/RXTXCommDriver.java' in the RXTX distribution. Add
the 'ttyQ1a' radical to the list of port radicals that RXTX checks:

if(osName.equals("Linux"))
{
String[] Temp = {
"ttyS", // linux Serial Ports
"ttySA", // for the IPAQs
"ttyUSB", // for USB frobs
"ttyQ1a" // Equinox
};
CandidatePortPrefixes=Temp;
}

Then recompile and reinstall.

=== Is there a way to access serial and parallel port with standard Java API ? ===

Currently no. This includes all Java versions including JDK 1.6 and probably JDK 1.7 when it is released. The [http://java.sun.com/products/javacomm/ Java Communications] API is a Java extension providing the necessary support for serial and parallel communication. RxTx is the most complete and currently maintained implementation of this API.

Development

2009-07-20T02:22:25Z

Tjarvi: Undo revision 6495 by VidelDomra (Talk)

This page is for content regarding programming rxtx and writing programs that use rxtx. Feel free to add your own content and links.

*[[Retrieving Source Code]] - How to get the source code from CVS
*[http://users.frii.com/jarvi/rxtx/doc/index.html gnu.io JavaDoc]
*[http://java.sun.com/products/javacomm/reference/api/index.html javax.comm JavaDoc] - provided as a point of comparison.
*[[Installers]]
*[[WebStart]]
*[[Examples]]

Talk:Main Page

2009-07-20T02:20:19Z

Tjarvi: Undo revision 6499 by TrdroNroor (Talk)

'''Note:''' Please post ask your questions on the [[mailing-list]], that's what it is there for. Questions will NOT be answered in the discussion pages of the wiki.

Rxtx:Community Portal

2009-07-20T02:18:57Z

Tjarvi: spam

Installation for Windows

2009-07-20T02:15:25Z

Tjarvi: Undo revision 6497 by DroneLortr (Talk)

http://www.textzeldrontr.com
RXTX installation procedure if you want to run RXTX enabled programs ==

If you just want to run RXTX enabled programs, follow this procedure.

Identify your Java Runtime Environment's folder. For version <code>1.6.0</code>, this usually is
:<code>c:\Program Files\Java\jre1.6.0_01\</code>

* Copy <code>rxtxParallel.dll</code> to <code>c:\Program Files\Java\jre1.6.0_01\bin\</code>
* Copy <code>rxtxSerial.dll</code> to <code>c:\Program Files\Java\jre1.6.0_01\bin\</code>
* Copy <code>RXTXcomm.jar</code> to <code>c:\Program Files\Java\jre1.6.0_01\lib\ext\</code>

''NOTE: When installing on Windows XP Embedded, make sure you include crtdll.dll (in the C Runtime Component) as it is required by rxtxSerial.dll''

==RXTX installation procedure if you want to develop or compile RXTX enabled programs ==

If you want to develop and compile RXTX enabled programs, for example with the NetBeans IDE, follow this procedure.

Identify your Java Development Kit's folder. For version <code>1.6.0</code>, this usually is
:<code>c:\Program Files\Java\jdk1.6.0_01\</code>

* Copy <code>rxtxParallel.dll</code> to <code>c:\Program Files\Java\jdk1.6.0_01\jre\bin\</code>
* Copy <code>rxtxSerial.dll</code> to <code>c:\Program Files\Java\jdk1.6.0_01\jre\bin\</code>
* Copy <code>RXTXcomm.jar</code> to <code>c:\Program Files\Java\jdk1.6.0_01\jre\lib\ext\</code>

Note that there is an additional <code>\jre\</code> subfolder in this path!

Development

2009-07-19T02:52:16Z

Tjarvi:

This page is for content regarding programming rxtx and writing programs that use rxtx. Feel free to add your own content and links.

*[[Retrieving Source Code]] - How to get the source code from CVS
*[http://users.frii.com/jarvi/rxtx/doc/index.html gnu.io JavaDoc]
*[http://java.sun.com/products/javacomm/reference/api/index.html javax.comm JavaDoc] - provided as a point of comparison.
*[[Installers]]
*[[WebStart]]
*[[Examples]]

Retrieving Source Code

2009-07-19T02:47:49Z

Tjarvi: Undo revision 6488 by AcacpAsrol (Talk)

Note: CVS is not intended for people looking for a stable copy of the rxtx package. If your interested in submitting changes via CVS please email taj@www.linux.org.uk.

Feel free to examine the latest CVS copy of rxtx. CVS information is now included in the latest source tar archives. After extracting the files from the tar archive simply change into the rxtx directory and type 'cvs update' to get the latest changes. One may also get the latest changes without downloading the tar files...

*CVSROOT=:pserver:anonymous@cvs.milestonesolutions.com:/usr/local/cvsroot

*PASSWORD=mousy

The following is an example session checking out via cvs.

Note: there are two branches of RXTX, which should not be confused. The first branch is for the javax.comm based library and the second is for the gnu.io based library. The former does not include the javax.comm jar file, so you will need to ensure you have it to do development with it.

Follows are steps to follow for a typical checkout.

[user@myhost]$ export CVSROOT=:pserver:anonymous@cvs.milestonesolutions.com:/usr/local/cvsroot
[user@myhost]$ cvs login
(Logging in to anonymous@cvs.milestonesolutions.com)
CVS password:

Password is 'mousy' (lower case).

If you want the 'gnu.io' (recommended) native library, and Java source (this corresponds to the 2.1 branch):

[user@myhost]$ temp]$ cvs checkout -r commapi-0-0-1 rxtx-devel

or if you want the 'javax.comm' native library (this corresponds to the 2.0 branch):

[user@myhost]$ temp]$ cvs checkout rxtx-devel

At this point the source code will be retrieved and placed in the local directory 'rxtx-devel'.

If you want at a later date you wish to update the source code, using the same branch, then from the directory containing the rxtx-devel folder, follow the instructions as for the checkout, but instead of the checkout command use:

cvs update rxtx-devel

User:203.88.192.104

2009-07-19T02:46:43Z

Tjarvi: Undo revision 6487 by DomlaBorac (Talk)

Rxtx:Privacy policy

2009-07-19T02:43:39Z

Tjarvi: Undo revision 6485 by OlogeTrobo (Talk)

Main Page

2009-07-19T02:42:27Z

Tjarvi: Undo revision 6484 by Staffelsocial (Talk)

Welcome to the RXTX wiki!

This Wiki is intended to be by and for RXTX users and developers. There is already a lot of information provided, but feel free to add your own content. Note that you will need to create an account before editing pages, as part of an effort to battle spambots.

*[http://www.rxtx.org Old RXTX home page] This wiki will be the RXTX Home Page when 2.2 is released.
*[[FAQ]]
*[[Download]] and [[Installation]]
*[[Using RXTX]]
*[[Development]]
*[http://bugzilla.qbang.org Reporting Bugs]
*[[Projects | Projects using RXTX]]
*[http://users.frii.com/jarvi/rxtx/license.html License] LGPL v2.1 + Linking Over Controlled Interface.
If after checking through the Wiki you don't find an answer to your question, then you can ask your question on the [[mailing-list]]. Posting questions in the talk pages is not the right place to ask your questions.

There is also the [http://users.frii.com/jarvi/rxtx/ original RXTX website], which is still around, though most of the information has been migrated to the Wiki.

{| style="background-color: #ffffdd"
|Send mail to [mailto:tjarvi@qbang.org Trent] if you spot spambot activity.
|}

Rxtx:Privacy policy

2009-06-28T22:53:37Z

Tjarvi: Undo revision 6460 by OlogeTrobo (Talk)

Retrieving Source Code

2009-06-28T22:51:52Z

Tjarvi: Undo revision 6463 by AcacpAsrol (Talk)

Note: CVS is not intended for people looking for a stable copy of the rxtx package. If your interested in submitting changes via CVS please email taj@www.linux.org.uk.

Feel free to examine the latest CVS copy of rxtx. CVS information is now included in the latest source tar archives. After extracting the files from the tar archive simply change into the rxtx directory and type 'cvs update' to get the latest changes. One may also get the latest changes without downloading the tar files...

*CVSROOT=:pserver:anonymous@cvs.milestonesolutions.com:/usr/local/cvsroot

*PASSWORD=mousy

The following is an example session checking out via cvs.

Note: there are two branches of RXTX, which should not be confused. The first branch is for the javax.comm based library and the second is for the gnu.io based library. The former does not include the javax.comm jar file, so you will need to ensure you have it to do development with it.

Follows are steps to follow for a typical checkout.

[user@myhost]$ export CVSROOT=:pserver:anonymous@cvs.milestonesolutions.com:/usr/local/cvsroot
[user@myhost]$ cvs login
(Logging in to anonymous@cvs.milestonesolutions.com)
CVS password:

Password is 'mousy' (lower case).

If you want the 'gnu.io' (recommended) native library, and Java source (this corresponds to the 2.1 branch):

[user@myhost]$ temp]$ cvs checkout -r commapi-0-0-1 rxtx-devel

or if you want the 'javax.comm' native library (this corresponds to the 2.0 branch):

[user@myhost]$ temp]$ cvs checkout rxtx-devel

At this point the source code will be retrieved and placed in the local directory 'rxtx-devel'.

If you want at a later date you wish to update the source code, using the same branch, then from the directory containing the rxtx-devel folder, follow the instructions as for the checkout, but instead of the checkout command use:

cvs update rxtx-devel

User talk:203.88.192.104

2009-06-28T22:49:11Z

Tjarvi: spam

User:203.88.192.104

2009-06-28T22:47:43Z

Tjarvi: spam urls

Talk:Main Page

2009-06-28T22:42:17Z

Tjarvi:

'''Note:''' Please post ask your questions on the [[mailing-list]], that's what it is there for. Questions will NOT be answered in the discussion pages of the wiki.

Download

2009-02-05T01:30:19Z

Tjarvi: /* Distributables */

Download

2009-02-05T01:29:57Z

Tjarvi: /* Distributables */

Trouble shooting

2009-01-29T00:31:17Z

Tjarvi: usermod -aG (a for add instead of replace)....

== Introduction ==

Below are issues that you might experience and possible solutions. If you don't find an answer to your problem, then there is always the [[mailing-list]].

== Issues and Answers ==

==== I Can Not Open the Port. ====

If you're not able to open the port (read the errors carefully) then you
may not have permission to use the device.

In particular, Red Hat Linux ships with the following permissions on the /dev/ttyS* device files:

crw-rw---- 1 root uucp /dev/ttyS*

Which means that generally, users do not have read or write access to the serial device.

You could increase the device files' access permissions. Log in as root, then run:

chmod o+rw /dev/ttyS*

Now everyone can read and write the serial devices:

crw-rw-rw- 1 root uucp /dev/ttyS*

However, this is probably not the ideal situation. At the next reboot, the
permissions may have been reset. You may want to have only some users access the device.

Another way of proceeding is to add the user that wants to access /dev/ttyS* to the
"uucp" group as (as can be seen above) group "uucp" has read/write access to the file.

This is done with the command "usermod" or by directly editing "/etc/group" with "vigr".

usermod -aG uucp <user-that-wants-access>

Be sure to check the file "CommAPI" for common mistakes.

Also make sure that the user can create lock files.
See [[Installation#How_can_I_use_Lock_Files_with_rxtx.3F|Lockfiles]].
Take note, particularly if you are trying to get 2.1-7r2(final) working on Mac Os X!

==== java.lang.NoClassDefFoundError: gnu/io/CommPort ====

RXTXcomm.jar is probably not in your classpath or not located in
the proper directory.

for example, lets not include RXTXcomm.jar

export CLASSPATH=../java/lib/classes.zip
$ java BlackBoxException in thread "main"
java.lang.NoClassDefFoundError: gnu/io/CommPort

==== The Compiler Cannot Find Java Include Files ====

Check to top of the Makefile to make sure we agree on the location of
the include files that came with the jdk. Specifically:

JAVAINCLUDE = -I /usr/local/java/include/
JAVANATINC = -I /usr/local/java/include/genunix
also check the classpath
CLASSPATH = ...

==== Configure says 'unterminated sed command' and stops ====

Unterminated sed command errors usually result from `find` producing
unexpected results. If you are unsure remove all comm.jar and
configure to place in in the correct place.

==== Java Can Not Find libstdc++-libc6.0-1.so.2 ====

jdk-1.2 on redhat systems may note that Java complains about not being
able to find libstdc++-libc6.0-1.so.2. A symbolic link can be used to
get around this feature.

ln -s /usr/lib/libstdc++ /usr/lib/libstdc++-libc6.0-1.so.2
ls -l /usr/lib/libstdc++-libc6.0-1.so.2
/usr/lib/libstdc++-libc6.0-1.so.2 -> libstdc++.so.2.8.0

==== BlackBox Can Not Handle all the ports! ====

BlackBox has a hard coded limit in BlackBox.java that prevents it from
running if you don't specify a port. We are considering alternative
ways of handling the large number of port names in Unix. The line in
question

is:

portDisp = new SerialPortDisplay[50];

just change 50 to say 256.

==== Illegal use of nonvirtal function call! ====
<pre>
Exception in thread "main" java.lang.VerifyError: (class:
gnu/io/RXTXPort$SerialOutputStream, method: flush signature: ()V)
Illegal use of nonvirtual function call
at gnu.io.RXTXCommDriver.getCommPort(Compiled Code)
at gnu.io.CommPortIdentifier.open(Compiled Code)
at SerialPortDisplay.openBBPort(Compiled Code)
at SerialPortDisplay.<init>(Compiled Code)
at BlackBox.addPort(Compiled Code)
at BlackBox.main(Compiled Code)
</pre>
"1.1 compilers sometimes generate code that won't verify under 1.2.

If you don't have the sources for the offending class to recompile with
a 1.2 javac, the only solution I know of is to launch the VM with the
-noverify option.

Louis"

In other words start with a fresh build directory, rebuild, and
reinstall to avoid the problem.

==== My libc5 Linux system is generating SIGSEGV ====

Older Linux Systems (libc5) should upgrade to a glibc system with
libpthread-0.7 or newer. We have run into many problems with older
libraries. SIGSEGV was the most common symptom. Reported by Peter
Bennett <bencom at bencom.co.nz>

==== AM_PROG_LIBTOOL not found in library ====

cd. && aclocal
aclocal:configure.in: 23: macro 'AM_PROG_LIBTOOL' not found in library
make:***[aclocal.m4]Error 1

If you're positive things are setup right you may try the autogen.sh
script to try regenerating the scripts with your tools.

==== Problems with RMISecurityManager() ====

Please see the file RMISecurityManager.html

==== Which Wires Should be Connected ====

With the DB25 use 2 (TX), 3 (RX) and 7 (GD) to connect to the device.
With the DB9 use 2 (RX), 3 (TX) and 5 (GD) to connect to the device.

You will need to hook up more than that for hardware flow control.

==== Which Device Should be Used? ====

* Linux serial ports should use <tt>/dev/ttyS*</tt>., specialx, cyclades and isdn4 linux have been reported to work. As many as 64 ports have worked at one time.
* FreeBSD uses <tt>cuaa*</tt>
* netbsd uses <tt>tty0*</tt>
* Irix uses <tt>ttyd* ttym* ttyf*</tt>
* HP-UX uses <tt>tty0p* tty1p*</tt>
* BeOS uses <tt>/dev/ports/serial*</tt>
* Win32 uses <tt>COM*</tt>

==== It Did Not Work! ====

There are sure to be bugs. The goal is to make the install as painless
as possible. Send back comments if something could be easier.

If you run into a problem building the rxtx package please include the
output generated by the following script.
<pre>
---------------clip-----------------
#!/bin/sh
which java
java -version
uname -a
autoconf --version
automake --version
libtool --version
make --version
---------------clip-----------------
</pre>
Here's what's on my system for comparison. Older make is known to cause
problems.

java 1.4
autoconf-2.53
automake-1.6.3
libtool-1.4.2
gnu make-3.79.1

mail any bugs to taj@www.linux.org.uk.

==== Which jdk should be used? ====

This is dated.

Ideally any jdk would be fine. Here is a list of jdk's tried on
RedHat 6.0/kernel 2.2.17pre13 with various versions of glibc.
<pre>
Sun IBM Blackdown
2.1.2_006 1.3.0 1.1.8v1
green native green native green native
------------------------------------------
glibc-2.1.1-6 | OK | *1 | *2 | *2 | OK | *3 |
-------------------------------------------
glibc-2.1.2-11 | OK | *1 | OK | OK | OK | OK |
-------------------------------------------
glibc-2.1.2-17 | OK | *1 | OK | OK | OK | OK |
-------------------------------------------
glibc-2.1.3-15 | OK | *1 | OK | OK | OK | OK |
-------------------------------------------
</pre>
1) BlackBox (a demo application shipped with CommAPI locks after multiple open()/close()

2) java wont start "Unable to load /usr/local/java/jre/bin/libhpi.so: symbol
sem_wait, version GLIBC_2.1 not defined in file libpthread.so.0 with link time
reference Could not create the Java virtual machine."

3) java wont start "error in loading shared libraries:
/usr/local/java/bin/../lib/i686/native_threads/libjava.so: symbol sem_init,
version GLIBC_2.1 not defined in file libpthread.so.0 with link time reference"

Conclusion? Avoid Sun's native threads unless you can figure out whats going wrong. (this is dated)

==== How does rxtx detect ports? Can I override it? ====

rxtx tries to detect ports on by scanning /dev for files matching any
of a set of known-good prefixes, such as 'ttyS', 'ttym', and so on.
Any ones that exist, are supposed to be good for the current operating
system, and that can be read and written are offered back from
CommPortIdentifier.getPortIdentifiers(), and only these can be used as
ports.

If you wish, you can set the system properties gnu.io.rxtx.SerialPorts
and gnu.io.rxtx.ParallelPorts. If either of these is set, then no
scanning will be carried out and only the specified ports will be
available. You can use this to make one platform look like another,
to restrict Java access to ports, or possibly for other reasons. For
example

java -Dgnu.io.rxtx.SerialPorts=/dev/cua/a:/dev/cua/b com.foo.MyApp

will look kind of like Solaris, if you have created the appropriate
device nodes.

A note on Linux port enumeration. We have set most ports aside. Once the
number of possible devices started getting into the thousands, checking them
all made little sense. Look in RXTXCommDriver.java and search for Linux.

You will see that only /dev/ttyS* is searched but the possible addition ports
that can be used are listed under it. Just copy the few you need.

A brief note on '''How to add new enumeration to existing list of ports in Linux?'''

The RXTXcomm.jar file contains all the required classes that work with javax.comm API.
One of them is RXTXCommDriver.class. RXTXCommDriver.java is available in ftp://ftp.qbang.org/pub/rxtx/rxtx-2.0-7pre2/src/
Download the RXTXCommDriver.java. In this code, you will find

if (osName.equals ("Linux"))
{
String[]Temp =
{
"ttyS", // linux Serial Ports
"ttySA" // for the IPAQs
};
CandidatePortPrefixes = Temp;

Replace this code with

if (osName.equals ("Linux"))
{
String[]Temp =
{
"ttyS", "ttyUSB", // linux Serial Ports
"ttySA" // for the IPAQs
};
CandidatePortPrefixes = Temp;
}

Compile the RXTXCommDriver.java and add the resulting RXTXCommDriver.class file to RXTXcomm.jar in
/usr/java/jdk1.5.0_07/jre/lib/ext/RXTXcomm.jar

P.S. : RXTXcomm.jar has two sub directories. gnu->io->RXTXCommDriver.class. Make sure the new compiled file goes into the right place. One way is to extract all files from RXTXcomm.jar. Replace the RXTXCommDriver.class with the new file. Create a new RXTXcomm.jar file using the following command

#jar cvf RXTXcomm.jar gnu META-INF

Replace this new updated jar file with the old one. Then USB to Serial Converters should work great.

==== How can I use Lock Files with rxtx? ====

RXTX uses lock files by default. Lock files are used to prevent more than one program accessing a port at a
time. Lock files may require a bit of sysadmin to work properly.

If you do not want to use lockfiles in RXTX, run 'configure' with option '--disable-lockfiles'.
It is however strongly recommended that you do use lock files to prevent RXTX from stomping on
other programs that might use the serial ports concurrently.

(Don't know if the following is still current. Trent?)

RXTX has support for lock files on Linux only. It may work on other
platforms but read the source before blindly trying it.

The lock file code does not support kermit style lock files or lock files in
'/var/spool'. It is sure to fail if you're using subdirectories in '/dev' or do not
have '/dev'.

Before you use lock files you need to do one of two things:

# Be user 'root' or user 'uucp' on your machine whenever you use RXTX .. or ..
# Add the specific user that needs to use RXTX to the group 'uucp' (preferred)

(On Red Hat, use group 'lock' in addition to 'uucp', see further below.)

To add a user to the 'uucp' group edit '/etc/group' as 'root' (using 'vigr' or your
preferred editor) and change the following:

uucp::14:uucp

to something like:

uucp::14:uucp,jarvi

It may be simpler to just run

usermod -aG uucp jarvi

which does exactly the same.

In this case 'jarvi' is the login name for the user that needs to use lock files.
Do not change the number (14). Whatever is in your group file is correct. (On
Red Hat, do this also for group 'lock')

User 'jarvi' in this case can now use RXTX with lock files.

===== Red Hat users =====

In Red Hat, lock files are supposed to be handled by group 'lock' instead of group 'uucp'.

Why: from Red Hat 7.2 upwards. the directory into which lock files are written, '/var/lock',
can only be written to by members of group 'lock'. On the other hand, the serial device
files are owned by group 'uucp' and are not world-writeable by default.

Thus any user (which may or may not actually be using [http://www.uucp.org/index.shtml uucp] ... do people still know what
that was?) that accesses the serial device files must belong to group 'lock' (to create lockfiles) and to group 'uucp'
(to access the device files proper). See also [[Installation#I_Can_Not_Open_the_Port.|I cannot open the port.]]

===== Mandrake users =====

'/var/lock' needs to be owned by group 'uucp'.

===== Mac OS X users =====

You may need to create the lock directory with group 'uucp' ownership. There is a script
in 'contrib' called 'fixperm.sh' to help with this on Mac OS X.

In 2.1-7r2(final) there is a mis-match between the lock file directory given in 'fixperm.sh' that in the source file SerialImp.h (/var/spool/uucp and /var/lock respectively). If you want the binaries to work, you need to replace /var/spool/uucp by /var/lock in fixperm.sh, and run that as root.

===== Lock File server =====

As another option it is possible to use a Lock File Server. In this case,
a server runs in group 'uucp' or 'lock' and rxtx then connects to localhost
to lock and unlock the port. The server and install instructions can be
found in 'src/lfd'. RXTX will need to be configured to use the server:

configure --enable-lockfile_server

Any user can then lock the ports if they are not already locked.

===== Arcana =====

Still cant get things to run under a root account?

Vadim Tkachenko writes:

"Maybe you remember - couple of months back I've run into inability to
run the JDK 1.3+ from under root account.

Today, absolutely suddenly, something clicked in my head and the cause
was found: libsafe. To make JDK work, it is enough to disable libsafe
(unset LD_PRELOAD)."

==== How can I tell which version of rxtx is installed? ====

Version information is not documented in Sun's CommAPI so this is probably
unique to RXTX.

As of rxtx-1.5-4 and rxtx-1.4-6 a class has been added to allow developers to
check which version of rxtx is installed. The class is RXTXVersion.

The static method: System.out.println(RXTXVersion.getVersion());

will print the rxtx version as a String in the following format:

"RXTX-MAJOR.MINOR-PATCH".

an example would be:

"RXTX-1.5-4"

A change in the MAJOR version would suggest you're in trouble.

Odd MINOR version are reserved for development. Even MINOR versions are
reserved for 'stable' releases.

PATCH is used to differentiate incremental releases of the MINOR releases.

CommPortIdentifier is expected to support getVersion() in the RXTX-1.5 series.

==== What Type of Latency can I expect with RXTX ====

frantz <fcapiez at club-internet.fr> put RXTX under a scope and found
the following:

RXTX currently has a latency of 150-200ms on a PII at 450mhz.
The latency can be reduced to 70-80ms by reducing the usleep()
value in SerialImp.c:eventLoop() to usleep(5000)).

Much lower latencies should be possible but the maintainer does not
have equipment to test changes.

He is going to look at this further. He needs 20 ms or less latency.

==== I got rxtx working on a new OS but I can't read from the port ====
<pre>
> Now my java program starts up nicely without complaining. However, it does
> never read any data from the serial port. It looks like it can write data,
> because if I start a terminal program after I tried to run my program, I get
> all the return stuff from the modem that my program wrote.
>
> I hacked around abit and found out that it hangs in the select() call which
> simply never returns.
>
On Sun, 28 Jan 2001, Baldur Norddahl wrote:
> HPUX 11:
>
> As I wrote to the mailinglist I had some wierd problems where it apparently
> could write data to the modem, but not read anything back. My terminal
> programs had no problem using the port. A few days after I reported the
> problem to the mailinglist, I had given up for now, but then I noticed that
> it suddenly worked! So it remains a mystery what was wrong as I did not
> change anything at all, neither in my program nor on the host.
>
> Baldur
>
</pre>

I suspect two java applications had the port open. Its easy to do while
developing. Perhaps <ctl> z instead of <ctl> c was entered.

This is the reason for adding lockfile support to rxtx. If another application
has opened the port, a second application will appear to not be able to
read or get only part of the data. ..because the first one is reading. Only
one of the select()s are waken.

Its possible to put lockfile support in for HPUX if it is known where other
applications place their lockfiles. The easiest way to find out where is
to fire up minicom, kermit, ... and see where its lockfile is placed.

Here are the known suspects:

const char *lockdirs[]={ "/etc/locks", "/usr/spool/kermit",
"/usr/spool/locks", "/usr/spool/uucp", "/usr/spool/uucp/",
"/usr/spool/uucp/LCK", "/var/lock", "/var/lock/modem",
"/var/spool/lock", "/var/spool/locks", "/var/spool/uucp",NULL
};

freebsd uses /var/spool/uucp/, linux uses /var/lock those are the only two
I've done so far. Adding the support is trivial once a directory is
decided upon.

Lockfiles are rather simple. when an application opens a port it first checks
if there is a file with the ports name. If there is it grabs the PID from the
file. If that PID is still active the application does not open the port.

If the PID is not active or there is no lockfile, the application creates one
with its own PID in it.

The confusion starts when you have to decide where (see above) to put the
lockfile, what the name format is for the file and how to store the PID.

rxtx follows The File System Hierarchy Standard http://www.pathname.com/fhs/
on linux. I'm not positive what is normal on other OS's.

more reading:

The File System Hierarchy Standard
http://www.pathname.com/fhs/

FSSTND
ftp://tsx-11.mit.edu/pub/linux/docs/linux-standards/fsstnd/

Proposed Changes to the File System Hierarchy Standard
ftp://scicom.alphacdc.com/pub/linux/devlock-0.X.tgz

"UNIX Network Programming", W. Richard Stevens,
Prentice-Hall, 1990, pages 96-101.
more reading:

==== My ThinkPad is Not Working! ====

Scott Burleigh <Scott.Burleigh at jpl.nasa.gov> writes:

For your files, and in case anybody asks in the
future, IBM Thinkpads ship with the external serial port
*disabled* by default. The Thinkpad configuration utility
supplied with the machine (under Windows) says it's enabled,
and the device manager in the System dialog of the Control
panel says it's enabled, but they lie. In order to enable the
port you have to use the old DOS ps2.exe bios configuration
utility which, under Windows 2000, is in
c:\Program Files\Thinkpad\utilities:

ps2 sera enable

Until you do, "setserial -ga /dev/ttyS0" will always tell you
the UART is unknown.

=== APPLETS ===

More info is needed on signing applets. This is an exchange from the rxtx mail-
list.

==== Using Applets ====

prashantg10 at yahoo.com asked:

Hi All !

I am trying to use applet on thin terminal which has
Linux base Kernel.For testing I am using Linux
machine.I have install all the required components.
e.g. JDK, RXTX. Everthing is fine. BlackBox runs ,even
my application runs. When It comes to applet,
everything is halts. It does not even show the listing
of ports. Is it because applet can't run under root
account or what might be the reasons. Can anybody tell
me solution.

Son To <son@openbx.net> replied:

Java applets run withing the sandbox of the security manager.
Applets must be signed to access the com port, but for development
purposes you can put

user_pref("signed.applets.codebase_principal_support", true);

in your prefs.js located in ~/.mozilla/default/XYYrandomDirName

I didn't use Java applet for my application. I used XUL and CSS for
the GUI development and used mozilla Javascript SOAP library to
communicate with apache Axis webservice backend which uses RXTX to
access the com port.

Download

2008-12-31T03:10:22Z

Tjarvi: /* Distributables */

FAQ

2008-08-23T19:53:00Z

Tjarvi: /* What License does RXTX use? */

== General ==

=== What RXTX? ===

RXTX is a Java library, using a native implementation (via JNI), providing serial and parallel communication for the Java Development Toolkit (JDK). All deliverables are under the GNU LGPL license. It is based on the specification for Sun's [http://java.sun.com/products/javacomm/index.jsp Java Communications API], though while many of the class descriptions are the same the package used it not, since gnu.io is used instead. A certain amount of compatibility is intended with API, though this project should be considered as a fork and therefore compatible in spirit, but not in implementation.

=== Do you have a Mailing List? ===

Yes, see the [[mailing-list]] page for details.

=== Where can I find information about how to write apps using RXTX? ===

Take a look at the [[Examples]]

=== What does RXTX install where? ===

The RXTX installation procedures installs files directly underneath $JAVA_HOME, i.e. directly into the JDK distribution.

In case you are using the Sun JDK:

The 'gnu.io' Java .class files are all packed into:

$JAVA_HOME/jre/lib/ext/RXTXcomm.jar

The [http://en.wikipedia.org/wiki/Library_(computer_science)#Shared_library Shared Object] files necessary to access OS-level functionality can be found underneath:

$JAVA_HOME/jre/lib/<architecture>/

and they are:

librxtxI2C-2.1-7.so
librxtxI2C.la
librxtxI2C.so -> librxtxI2C-2.1-7.so

librxtxParallel-2.1-7.so
librxtxParallel.la
librxtxParallel.so -> librxtxParallel-2.1-7.so

librxtxRaw-2.1-7.so
librxtxRaw.la
librxtxRaw.so -> librxtxRaw-2.1-7.so

librxtxRS485-2.1-7.so
librxtxRS485.la
librxtxRS485.so -> librxtxRS485-2.1-7.so

librxtxSerial-2.1-7.so
librxtxSerial.la
librxtxSerial.so -> librxtxSerial-2.1-7.so

Also see the '[[installation]]' page for more information.

=== Is there a Change Log? ===

Yes, see the '[[Change Log]]' page.

=== What License does RXTX use? ===

RXTX is license under the LGPL with an exception for linking over controlled interfaces, a copy of which can be found in the '[[License]]' page. The exception allows people to use RXTX as a service plugin with Sun's CommAPI: 'A Controlled Interface.'

=== What Platforms does RXTX run on? ===

See the page entitled '[[Porting]]', for more information.

== Problems and Workarounds ==

=== On MacOS X I get a 'PortInUseException', even though it isn't? ===

Versions prior to 2.1-8 use lock files, which is not the MacOS X way of doing things, and therefore has issues. For this reason make sure that you have version 2.1-8 or higher, which makes use of [http://developer.apple.com/documentation/DeviceDrivers/Conceptual/IOKitFundamentals/ I/O Kit]. At this point in time 2.1-8 is only availble from CVS, in source form. See the section [[Retrieving Source Code]], on getting the latest code - be sure to get the code from the 'gnu.io' branch.

'TODO': Can anyone who knows how please make an easy download available like the 2.1-7 version?

=== RXTX does not find my device, what's wrong? ===

There may be a number of reasons, but most often it is because your operating system can't find it either. RXTX is built upon the functionality provided by your operating system, and therefore is dependent on its limitations. For this reason find out whether your system can find the port, if it can and you still can't work what is going on, then there may be some help on the [[Mailing-List]].

=== RXTX installation fails with JDK 1.6 ===

This applies to the source package of RXTX 2.1-7r2.

After having run ''./configure; make; make install'', the following message appears:

make all-am
make[1]: Entering directory `/<mumble mumble your directory>/rxtx-2.1-7r2'
make[1]: Nothing to be done for `all-am'.
make[1]: Leaving directory `/<mumble mumble your directory>/rxtx-2.1-7r2'
libtool: install: `x86_64-unknown-linux-gnu/librxtxRS485.la' is not a directory
Try `libtool --help --mode=install' for more information.
make: *** [install] Error 1

This is caused by a missing case in the 'configure' script generated from 'configure.in', which
causes the variable RXTX_PATH to not be set which causes the above confusion.
You can change the 'configure' script directly. Look for the case instruction that matches JDK version strings:

1.2*|1.3*|1.4*|1.5*

and extend it to

1.2*|1.3*|1.4*|1.5*|1.6*

Note that there are matches for Linux, BSD, Solaris and Win32.

Then run ''./configure; make; make install'' as usual.

=== RXTX and the Equinox SST-4P/LP multiport card ===

A note for those who want to install an Equinox board (in this case "SST-4P/LP") and try to
run it with RXTX under Linux (in this case, Red Hat ES 4)

Get the driver source from the [http://www.equinox.com/support/download-drivers/ www.equinox.com driver page] and
compile it as described therein.

The four serial ports of the Equinox SST-4P are available as the device files:

/dev/ttyQ1a1 ... /dev/ttyQ1a4

These device files are created by the 'ssmkn' (alias 'make device nodes') executable.

In order to make things work, you have to:

Modify the 'eqnx' startup script '/etc/rc.d/init.d/eqnx'
and make it set the permissions of the devices files in the
'start' section, immediately after the call to 'ssmkn':

# create device files
/usr/bin/ssmkn
# fix rights on device files
LIST=`ls /dev/ttyQ*`
for DEV in $LIST; do
chown root.uucp $DEV
chmod 660 $DEV
done

Modify 'src/RXTXCommDriver.java' in the RXTX distribution. Add
the 'ttyQ1a' radical to the list of port radicals that RXTX checks:

if(osName.equals("Linux"))
{
String[] Temp = {
"ttyS", // linux Serial Ports
"ttySA", // for the IPAQs
"ttyUSB", // for USB frobs
"ttyQ1a" // Equinox
};
CandidatePortPrefixes=Temp;
}

Then recompile and reinstall.

=== Is there a way to access seria and parallel port with standard Java API ? ===

Answer wanted ...

Wiki/wiki/wiki/index.php

2007-09-29T20:46:47Z

Tjarvi: Wiki/wiki/wiki/index.php moved to Junk

#REDIRECT [[Junk]]

Rxtx:About

2007-09-29T20:44:45Z

Tjarvi: revert changes

RXTX is a native serial library for java serial communication that runs on many operating systems.

[http://www.rxtx.org www.rxtx.org]

Partial Question

2006-10-12T18:32:19Z

Tjarvi:

This question was left on the front page but appears to be missing bits.

<pre>
hi!!

How to close COM port??
I want changing port by flexibly(?) ..

so.. example

1> com1 open
2> recv & send (communication)
3> com1 close
4> com2 open
5> recv & send (communication)
6> com2 close

or

1> com1 open
2> com2 open
3> com1 recv & send (communication)
3> com2 recv & send (communication)
4> com1 close
5> com2 close

im very ....
</pre>

Main Page

2006-10-12T18:31:37Z

Tjarvi:

Welcome to the RXTX wiki!

This is intended to be by and for RXTX users and developers. To get things started, we will put the INSTALL information here. But feel free to add your own content.

*[http://www.rxtx.org RXTX home page]
*[[Installation|INSTALL File]] (RXTX 2.1)
*[[Installation for Windows]] (RXTX 2.1)
*[[Using RXTX]]
*[[Development]]
*[http://bugzilla.qbang.org/ Reporting Bugs]
*[[Projects]] using RXTX

If you don't find an answer to your questions, create one here and ask on the rxtx [http://mailman.qbang.org/mailman/listinfo/rxtx mail-list].

We can fill it in from there.

[[Partial Question]]

Development

2006-03-20T17:19:18Z

Tjarvi:

This page is for content regarding programming rxtx and writing programs that use rxtx. Feel free to add your own content and links.

[[Installers]]