This is a list of GPS Logger Devices that BT747 supports. In general, BT747 supports devices with a MTK/MTK II-Chipset.
Support for other Chipset types/loggers is added bit by bit.
And even if your GPS is not a logger, BT747 may support GPS Chipset configuration.
IMPORTANT: BT747 is updated with a CERTIFICATE to comply with JAVA 7 (1.7.0_51) security.
(I bought a trusted certificate (provided by a trusted authority) for about $300. Received it on Jan. 17, 2014.
Thank you (!) to the users that donated a bit (thanks!) to partially cover the cost of the certificate.
If every person using BT747 would donate $1 the cost would be covered in about two weeks (luckyly for you, I did not wait to cover the cost).
Installing the desktop version of BT747 for GPS control is fairly easy through the 'Java Web Start' system. This system works on Windows flavours, MacOS and Linux.
To download zip files follow this link.
On Ubuntu it is recommended to Install sun-java6 first
For easy installation (RECOMMENDED!), use one of these links:
Try the desktop version of BT747 or Install the desktop version of BT747
Try the development version, Install the current development version or keep it up to date automatically.
On recent machines or in case of trouble with the serial link: BT747 Latest using RxTx 2.2pre2 (RxTx dev version) for Windows 32 & 64 bit, MacOSX, Linux or Install the development version using RXTX2.2pre or Install the stable version using RXTX2.2pre
I'm currently using BT747 for downloading GPS tracks from Holux M-1200E device via USB cable, and it works just fine. But my attempts to do the same via Bluetooth connection are unsuccessfull: it just does not see the logger on the COM port created by Windows XP for BT connection (the BT pairing & connectivity itself is fine).
I'm starting to think that BT part of that tracker can be used for live GPS data transmitting only, while its internal memory content isn't accessible from BT side, and this design is preventing me from downloading stored tracks.
Tested only with java Web Start. Command line for launcher:
In menus select:
Settings - Device Protocol - "Holux M-1000C / GPSport 245"
To connect to device via USB data cable (not USB power cable from HOLUX package):
or via blueman (pincode for pairing 0000):
"/dev/rfcomm0" "115200" (port must be not used by gpsd)
For a while I wasn't figuring out what happened a while ago (between 2.x.1704 and 2.x.1887) which simply made gps data transfer not working with my Holux M-1000C, but yesterday I've been determined to look around the menus for new features which may have broken it and yes, there's a new device protocol called "Holux M-1000C", which was autoselected.
And it doesn't work.
Selecting old "Holux" (first option) just works.