serial communication is broken on Solaris.

Hi,

I use javax.comm to communicate with a serial device, it work well on Windows(using comm2.0). But when I tested it on Solaris 10(using comm3.0 tested on aparc and x86 ), the reply lost continually and I could get the correct reply once in a while.

If I use a adapter, MOXA w2150, to tranform serial to tcp, the device can work with solaris, so the device should be no problem.

Because it need work on Solaris based on X86, rxtx is not a selection.

Anyone has some suggestion?

[511 byte] By [OZKINGa] at [2007-11-27 4:44:37]
# 1

The problem should be a bug.

When I set SerialPort.addEventListener and notifyOnDataAvailable(true), I found the reply's length often is 8 . If the correct reply shoudd be 56 chars, it return 8 chars several times and some chars lost.

If don't use Event mode, the communication can work.

OZKINGa at 2007-7-12 9:56:39 > top of Java-index,Core,Core APIs...
# 2

My understanding was that was a reference implementation so you are on your own. I can't find that documented though.

You can report bugs in the bug database.

That will take a while unless you have an existing account with Sun that actually produces money for Sun. If you have such an account then you should post the bug and then talk to your sales person (not technical) to have them push a solution.

You might want to look for a commercial solution.

jschella at 2007-7-12 9:56:40 > top of Java-index,Core,Core APIs...
# 3

I am the RD chief of Wireless NPort in Moxa.

We are more than happy that you used our products without trouble. But we are also very sorry to hear your cannot use the native com by javax.comm. We are not be able to solve Javax.comm's trouble. But if you have any question about our Wireless NPort, then, please contact us or Moxa's technical support directly. We will do our best to answer. You can contact me or write to support@moxa.com.

shinhaya at 2007-7-12 9:56:40 > top of Java-index,Core,Core APIs...