On Sat, 28 Jun 2014 20:18:25 -0700, Knute Johnson wrote:
On 6/28/2014 15:12, Martin Gregorie wrote:
On Sat, 28 Jun 2014 13:45:17 -0700, ookachaka wrote:
On Sunday, February 15, 2009 9:46:50 PM UTC-8, Chanchal wrote:
Hello All,
Anyone having link to javadocs of RXTX Communication API, kindly
share.
Thanks and Regards
Chanchal
Yes, there's something wrong (in my case).
The fril javadocs are not downloadable.
RXTX appears to be fairly close to abandonware at present. The rxtx.org
host doesn't respond to HTTP requests or pinging. The domain is
registered by Godaddy until December, but ownership details just show
Domains by Proxy. There is a Sourceforge project but it has no files
and there is an Android port too.
The sources for Windows, IOS and Linux can be found at
http://rxtx.sourcearchive.com/
RXTX may be a Java class library, but there is evidently a healthy
amount of native code needed to interface the RxTx package to the
underlying OS,
primarily because serial i/o is anything but standardised outside the
POSIX world.
I think your best bet may be to grab the source tarball from
rxtx.sourcearchive.com, see what documentation there is in the tarball
and then feed the Java source through javadocs.
It is possibly a bad sign that I couldn't find either a build.xml (for
Ant) or a Makefile (for the C sources) in the published file list. I
have no idea what, if any, C documentation tool, should be used: you
might like to try Cdoc since I wrote it to do sensible things if you
point it at vanilla C.
Good luck.
If he is using any of the new Windows (Vista, 7 or 8) I would forget
serial IO and use some sort of conversion device. I've used a couple
that interface through TCP/IP and I know there are USB to serial devices
available. If he is developing for XP then the old Sun javax.comm
package is the way to go. It works pretty well and didn't have the bugs
that RXTX had. The Sun software has been unsupported for years but I
know it still works just fine on XP.
Some of the USB to serial adapters are a bit choosy or, I should say,
some applications can be choosy about the adapters they will talk to.
I've had good results with the unit that pfranc sold some years ago when
connecting to it from native C programs running under Linux, but Win95
apps running on Linux under Wine didn't want to know, even though they
worked just fine over a multi-port serial adapter card. I put that down
to the total lack of serial support provided by DOS or Windows 95 or
earlier. These simply let you access to bare metal UART, which I did via
a third party serial i/o library (Willies Software's COMM-DRV) but I
don't know how that would have interacted with a USB adapter and have no
idea what code the aforementioned applications I tried under Wine used
for serial access or where they got it from.
Another possibility would be to use an Ethernet to serial converter such
as:
- Lantronix Xport -http://gridconnect.com/network-components/xport.html
- NEMO10 - http://kanda.com/products/Sena/NEMO10.html
- LSHM-200 - http://www.radi.com/modular64.htm
These are all component-level devices that would need to be mounted and
connected to the UART and a power supply. Or, you can find commodity
adapters on eBay among other sources: they are typically a plastic case
with an RJ-45 socket in one end and a D-9 serial connector in the other.
IMO these are a better bet than USB adapters because Java has built-in
TCP/IP support but probably can't talk to a USB<->serial adapter at a low
enough level to set baud rate, parity and stop bits correctly. The
Ethernet to serial converter module takes care of this because it
connects locally a UART and takes care of configuring itself to talk to
the serial port (UART): some can be hard-wired while others are
configured with a web browser and keep the configuration in flash memory.
We used a Moxa NPort 5400 on our last project that needed serial IO. It
is connected via TCP/IP and configured with a browser. It has worked
flawlessly. They are rather expensive however but if you need the job