Moving from RxTx to jSSC

[theborax]

I created this proof of concept commit just to test moving from RxTx (which seems like a hopeless library when it comes to maintainance) to jSSC (https://github.com/scream3r/java-simple-serial-connector/releases/ which is more active). Currently I just did quite a dirty implementation to see if it works, which it actually does. It would also be quite easy to use the abstraction I currently have to support both the serial libraries.

I've tested it on win64 (which RxTx doesn't support at all AFAIK) and ubuntu 14.10 x64. I do also have access to an Raspberry Pi which I could test this on if there's an interest in that.

@andrewrapp if you want me to I can clean this up to make it more "production worthy"?

Br
Ola

[andrewrapp]

Nice work! I've been wanting to get off RXTX but it's been one of those tasks I haven't had time to get to. I think it's important to support the same platforms as RXTX, which includes linux/arm. How's it working? Any issues?

[theborax]

I've been playing around with it a bit on my raspi 2 and it's working just fine as far as I've seen. I've been thinking about adding some automated tests that can run to validate if it works or not. Just retrieving the ID etc from the device ought to be enough to see if the serial IO is working on the OS under test. Just realized that I have a Mac lying around so I could also check if it works in OSX.

So, to get some steps ahead (I work as a developer so I like to have a plan ;)), I can clean this up if you want me to and basically remove all RXTX related code / dependencies. jSSC has a slightly different approach when it comes to working with serial IO compared to RXTX so the code could/will be optimized a bit more. I can also add some commandline tests for use with the lib itself just to make further validation of devices on different platforms easier.

[edpi]

Hi,

I'll try to test jsCC, as I have found some errors with RTXT when changing from WinXP to Win64 on an application tested for some years. Error I have found are related to issue #11 on Google code (Occasional XBeeParseException: Read -1 from input stream while reading packet).

Same code tested on a Win7 with several java versiones get these results:

• JRE7 32 bits, RXTX 2.1.7: Works ok
• JRE7 64 bits, RXTX 2.2-pre2: Errors
• JRE8 64 bits, RXTX 2.2-pre2: Errors

@theborax, did you finally make a "clean" version of your code? Or should I test this "proof of concept"?

Regards

[mjs513]

I was wondering what the status of these commits are as I am very interested in getting operational with Processing 3.

If not can you let me know where to get the changes to make it work with JSSC. I am running win10 - 64bit.

Thanks
Mike

[theborax]

Hi, I chose to use a different tech for my hobby project so this commit was left on ice. Functionally this is fully working, the code is not that good looking though.

[theborax]

Ok, so code cleaned up but as always there is more I would like to do :). Code has been tested on Win10x64 and RasPi2 and it works on both. Also removed all libs/unnecessary stuff and changed the project structure and pom to reflect a more typical maven project. Added a skeleton for some basictests / abstracted the serial connection (so we actually could add some code to validate how the logic is working without depending on HW).

@andrewrapp and @mjs513 please try it out and see how it works for you guys. Would be great to get someone testing this on x86 *nix as well.

Took the liberty to step the versionnumber one minor step as there are quite the changes here.

[mjs513]

Will give it a try as soon as I can. I am just finishing up some tests with the new Arduino 101 board. Will let you know how it works out.

[Bwtbo]

I am new to java and I have a 64 bit javafx application that uses rxtx that works on windows 10 with jre 8 update 8 (build 1.8.0_171-b11). But it crashes when I try to run it on windows 10 64 bit java10. Do you know if Jscc will work on windows 10 64 bit with java10? I have a log file, but I am not sure what to do next.
hs_err_pid5224.log