Community
Participate
Working Groups
Since the fix of bug 170810, my virtual serial connections are not recognized by the the serial terminal. The javax.comm listed them in the settings dialog...
Can you be more explicit what the problem is? One difference between Sun javax.comm and rxtx is, that the Sun implementation uses a hard-coded file ("javax.comm.properties") to list serial ports, while rxtx always tries to automatically detect them. But I was told that rxtx allows to manually override the terminal devices detected, so it might be possible to have an editable combobox instead of the dropdown for selecting the port and allow the user enter the right device. Adding Uwe on CC since he might know more about that.
RXTX (2.1-7r2): CommPortIdentifier.addPortName(String name, int type, CommDriver driver) If the comm port selection control supports user editing, the above API can be used to extend the list returned by CommPortIdentifier.getPortIdentifiers().
Allowing the user to manually enter a comm port that has not been detected is certainly the best and safest option, so we should consider switching to editable listboxes. I also checked the RXTX mailing list, and there has been some discussion regarding virtual comm ports - one example below, there are more when searching for the same subject or looking at the thread: http://mailman.qbang.org/pipermail/rxtx/Week-of-Mon-20050613/793343.html basically, they recommend adding the comm port identifiers which are missing to RXTXCommDriver.java, so it can be detected automatically. What are the names of the virtual ports you are missing? RXTX seems to shoot for a new release early march, so there might be room to add these to the RXTX autodetecter: http://mailman.qbang.org/pipermail/rxtx/Week-of-Mon-20070129/795500.html
The serial connector now allows to enter names of devices that are not found by the rxtx discovery. rxtx either takes the ports from a System property "gnu.io.rxtx.SerialPorts" or using the native port discovery. The trick was to add all discovered ports to the System property when the user enters a custom port. Potential (hypothetical) problem with this approach: - a user uses a custom, port - new (physical) port is added to the system and the discovery process would normally find this new port ==> the new port might not be found. I don't know if it is possible to add new physical ports to a host that rxtx finds at runtime.
