I had the same problem and first landed on this post when looking for a solution.
As mdeweerd said, the version mismatch is not an issue (It's explained on the website of RXTX, http://rxtx.qbang.org/wiki/index.php/Download "TODO: The 2.2pre2 bins contain the 2.2pre1 jar file and the 2.2pre2 native lib which causes a mismatch warning").
In my case the problem was (on a quite fresh installed Ubuntu 16.04) that I hadn't the rights to access /dev/ttyUSB0 (To test if you have the rights simply try to call "cat /dev/ttyUSB0"). If you do a "ll /dev/ttyUSB0" you will see that ttyUSB is in the group "dialout". The solution for me, was to add myself to this group: "sudo usermod -a -G dialout hereyourusername" (a restart or logout/login seems to be necessary after that).
No problem here (openSUSE
No problem here (openSUSE Tumbleweed 64Bit).
...Rolf
BT747 works on many platforms
BT747 works on many platforms including Linux 64bit.
You can get the ZIP and try to do 'run_j2se64.sh'.
However, the exact version to run depends on your java - if your java installation is 32bit, you must run the 32 bit version.
Using the versions from http://soft.bt747.org the selection is automatic.
May this be the source of my
May this be the source of my problem?
WARNING: RXTX Version mismatch
Jar version = RXTX-2.2pre1
native lib Version = RXTX-2.2pre2
Sorry for double post. May
Sorry for double post.
May this be the source of my problem?
WARNING: RXTX Version mismatch
Jar version = RXTX-2.2pre1
native lib Version = RXTX-2.2pre2
The version mismatch is not
The version mismatch is not an issue - the java itself did not evolve, but the native version may be different depending on the platform.
That is not an issue.
Just in case it might be
Just in case it might be usefull for others:
I had the same problem and first landed on this post when looking for a solution.
As mdeweerd said, the version mismatch is not an issue (It's explained on the website of RXTX, http://rxtx.qbang.org/wiki/index.php/Download "TODO: The 2.2pre2 bins contain the 2.2pre1 jar file and the 2.2pre2 native lib which causes a mismatch warning").
In my case the problem was (on a quite fresh installed Ubuntu 16.04) that I hadn't the rights to access /dev/ttyUSB0 (To test if you have the rights simply try to call "cat /dev/ttyUSB0"). If you do a "ll /dev/ttyUSB0" you will see that ttyUSB is in the group "dialout". The solution for me, was to add myself to this group: "sudo usermod -a -G dialout hereyourusername" (a restart or logout/login seems to be necessary after that).
what else is the problem
what else is the problem JNI/VM ??
why does gpsbabel work then ??