Blackberry

BT747 should work on Mobile Phones that supports CLDC 1.1 / MIDP 2.0 and JSR-82 (bluetooth library). Take a look into the list of working reported phones. Please report if you have run it on a unlisted device, so we can add this to the list. Thanks. Download the current stable version from BT747-Sourceforge-page (select the file BT_J2ME_version.zip). Unzip the content and change to "dist". There you found the needed "BT_J2ME.cod". Install that file in the usual way on your Blackberry. Development versions have more functionality but are not considered stable enough to share with the larger public.

Common issues with the Serial Link Setup

It can be that BT747 does not include the serial drivers for your system. In that case, go to http://rxtx.qbang.org/ToyBox to look if there are binaries for your system. If there are, they couild be included in the BT747 distribution or made available through the web application. Contact the author of BT747 for that: through the contact form on http://www.bt747.org, through a feature request on sourceforge or through e-mail (see the application).

Desktop GUI

Installing the desktop version is easiest from the web. A reference to the installation links can be found on the Easy install page on http:/www.bt747.org . Installation from the web requires that you have 'Java Web Start' installed. This is already available on most Desktop systems. Further, you still need to have the low level drivers for the serial link (over USB or bluetooth). These were in principle on the CD that came with your GPS Logger if you have windows. For other systems, you need to get them from the Silabs site. Here is a direct link to the CP210x USB to UART Bridge Virtual COM Port (VCP) drivers. Well known Linux systems have the driver installed, on Windows and MacOSX you will need to install it.

Linux - ubuntu

If Java not installed, go to Application / Add. Enter Java in Search. Now you have the choice between OpenJava and SunJava. BT747 works with both of them. A driver is not needed, its included in the Linux-kernel used by ubuntu. In the last step, you get BT747 to your comptuer. Go to the webinstall-page and try or install BT747. Or if you like to have all files on your local computer, go to the BT747-Sourceforge-page and download the current stable version. Unzip the content and run the desktop-version by clicking on „run_j2se.sh“ The correct port should be detected automaticaly by using "USB (for Linux, Mac)" - please connect and turn on the logger before you start BT747. For 64 bit, the same procedure should work because the startup script is improved and RXTX2.2pre binaries are joined.

MacOS X

First you have to download and install the usb-driver for the logger-device. You can use the universal one from the chip-manufacturer: SiLabs. The second step is a little bit complicated, but has to be done only once. First open the "Terminal" in "Application/Utilities". Then enter - as administrator - in that terminal (press return or enter after each line): sudo mkdir /var/lock sudo chmod 777 /var/lock The first line creates the directory "/var/lock" and the second makes it read/writeable for all users. In the future releases for bt747 (2.x) this step is not longer needed. In the last step, you get BT747 to your comptuer. Go to the webinstall-page and try or install BT747. Or if you like to have all files on your local computer, go to the BT747-Sourceforge-page and download the current stable version. Unzip the content and run the desktop-version by clicking on „bt747_macosX_j2se.command“. The correct port should be detected automaticaly by using "USB (for Linux, Mac)" - please connect and turn on the logger before you start BT747.

PDA

Go to the BT747-Sourceforge-page and download the current stable version. Unzip the content. Change to folder "dist", there you find the different distributions of BT747. Use

BT747.pdb und BT747.prc are for Palm PDAs, the appropriate CAB file is for your Windows Mobile PDA. Install them using the software provided by the manufacturer of the PDA (or any other other method that you are used to).

Also you need SuperWaba. Download them from Sourceforge. There are again different files available, select that one that you need for your PDA and install this the same way as above.

To run BT747 just click in the icon. SuperWaba will automaticaly start in the background. If you prefer another language click on the titlebar and select "Lang", choose the language you like.

Windows

You need to install the Windows device driver first if that is not done yet. Use the CD that come with the logger-device or visit the web-pages:

• Holux
• Qstarz
• Transystems (nothing available there (05/2009)
• universal driver, sucessful tested with Qstarz and Transystems devices

Did you already install Java (JRE, Java Runtime Environment)? Most users do, but if not so, go to Sun microsystems (file: JRE 6 update 13 (05/2009)). In the last step, you get BT747 to your comptuer. Go to the webinstall-page and try or install BT747. Or if you like to have all files on your local computer, go to the BT747-Sourceforge-page and download the current stable version. Unzip the content and run the desktop-version by clicking on „run_j2se.bat“ unter XP or "run_j2se64.bat" under the 64bit version of XP/Vista. To connect the device, select the correct COM-port. If you don't know them, go to the Device Manager and look for the COM-port with "CP210x in the description".

mobile phone

BT747 should work on mobile phones that supports CLDC 1.1 / MIDP 2.0 and JSR-82. Take a look into the list with as working reported phones. Please report if you have run it on a unlisted device, so we can add this to the list. Thanks. Go to the BT747-Sourceforge-page and download the current stable version (select the file BT_J2ME_version.zip). Unzip the content and change to "dist". There you found the needed files: "BT_J2ME.jad" and "BT_J2ME.jar". Install the files over the usally way on your mobile phone. Or put them on a memory card, insert them in you mobile phone and run "BT_J2ME.jad" there to start the installation.

Function Overview

• Use the SW on your PDA (and some phones) - No need to have your PC with you to change settings or know the device status;
• Download the log in raw format - the raw format is saved and can be appended to later on (fine grained incremental download) or converted at a later time;
• Archive the logs. You can keep the original 'bin' files and convert them at any later time. It is not required to be connected to the device to convert. You can name the file after the date or the trip that is logged in it.
• Convert the log to CSV, KML, GPX, NMEA, Google Maps (single HTML file), CompeGPS (TRK), or PLT (OziExplorer) format (CSV is improved over the original application);
  • Define the name and location of output (input) files ;
  • Get one output file per day in the log file;
  • Automatically seperate tracks.
• Subtract the difference between the MSL (geoid) and the WGS84 from the logged height. This difference is added to the height when it is logged in the device. That way the height is matched to what Google Maps expect and to what the user expects.
• Filter items written to these formats by:
  • date (start/end date);
  • log reason (time, speed, distance, button, and application specific);
  • fix type (no fix, sps, dgps, estimate, ...)Change the logging reason parameters (time, speed, distance). To change, check the tick box and then push SET;
  • record number, speed, distans, PDOP, HDOP, VDOP, NSAT (=Advanced).
• Change the log format (without erasing the log on the device);
• Set 5Hz logging (set Time=0.2 s and fix = 200 ms) or the button on the 'Easy' tab;
• Log positions from within the application (on the device) using extra log reasons.
• Start/Stop the log;
• Set some special settings (not available in the PC application delivered with the device): DGPS mode, test satellite, fix frequency (e.g., 5Hz setting)
• Avoid the bugs of the original application (V2.2):
  • Incomplete (incorrect) log download resulting in not being able to get all the log points;
  • Errors in HDOP value interpretation (1.09 is written as 1.9 by the original application);
  • Incorrect date given in the NMEA format.

Title Menu

Log Operations Panel

Output Settings Panel

Filters Panel

Device Settings Panel

Advanced Device Settings Panel

Advance File Settings Panel

BT747 1.60.11 Advanced File

Info Panel

AGPS Panel

The AGPS Panel (currently in the dev version) allows you to upload AGPS data to the device.

For the MTKII devices, this is called 'EPO' data which means 'Extended Prediction Orbit'. It is a format specific for the MTKII chipset.

As authorisation is currently lacking to integrate server location and login/password to connect to the FTP server is missing, you need to find that information for yourself. Your firewall can tell you what an application tries to connect to for instance.

Files to tag

Map

Track

Waypoints

Location Server Settings

The J2ME application can upload the current position to a server on the web.   For information on the web server set up, see /node/200.  This is a very short note on how to set it up.  The first version this stuff is available in is BT_J2ME 0.3.28

To set up BT747 on your phone for position serving, first find "Position" in the main menu:	Position menu in main menu
Selecting that will another screen initially telling you that no updating is done. However, the menu buttons (bottom) will allow you to select 'Menu' to show this the screen on the right. General will allow you to enable position serving and set the update rate (by default every 300 seconds, which is every 5 minutes). The last item 'Authentication' allows you to enter a user name and password if your server requires it (a '.htaccess' file can restrict access to the files showing where you are). The middle item, 'Server' is a little bit trickier and the configuration is show just below.	BT J2ME Location Configuration Menu
The hostname is the symbolic name or the IP address of the server that you want to talk to. Here it is a virtual hostname 'mylieu.bt747.org'. The port number is important too. This can be about anything, but here it is 80, the default http port. The last line is the actual path to the 'page' on the server accepting the position parameters. Here it is 'setUserPosition.php' as proposed by default in the mylieu project discussed on the page referred to above, but it could be 'private/setUserPosition.php' if you moved that to a subdirectory called private. Once this is set up correctly, and you have a valid data connection on your phone, the applilcation should start sharing the position with the server. In this development version, it will show a '!' (exclamation mark) when it did not succeed in connecting to the server and a '.' (dot) when it did succeed.	BT J2ME Location Server Configuration

Good luck.

AGPS

AGPS (assisted GPS) is a system that helps GPS devices in getting a FIX situation faster.
In a few words the EPO file contains "hints" that lead the device to find satellites faster.
To use the AGPS feature of your device you have to keep those "hints" updated.
This is useful in poor signal conditions, like when tall buildings or trees make the signal weak.

The new AGPS upload feature is available even in the command line version.
From the usage:
--agps Upload APGS data using the default URL
(or the provided url when available).
--agps-clear Clears the AGPS data in the device
(done before the upload).
--agps-url Specify the URL (file://, ftp://, http://)
to the AGPS (EPO) data.
The basename of this file is usually
MTK7d.EPO, MTK3d.EPO, MTK8d.EPO or
MTK14.EPO
Implies agps option.

If you use command line probably you are using it in some sort of BAT script.

This is my experience in mirroring EPO files to get a faster download (and my troubles...)
When uploading EPO files to many devices it could be faster to mirror an EPO file you got somewere, and then upload a local file to avoid a network transfer everytime you send data to the device.
But the EPO file has no checksum informations, so be careful you do not alter the file during the transfer.

Linux example:
cd /home/locale1/agpsdata ; wget ftp://username:password@ip.ad.dre.ss/path/to/file.EPO -O file.EPO
It works without damaging your file.

Win example:
we call ftp with a script file:
c:\windows\system32\ftp -s:c:\mailtrack_app\ftp.cmd

content of ftp.cmd:
open ip.ad.dre.ss
username
password
binary
get file.EPO C:\your\path\file.EPO
quit

Notice the "binary" command:
without this the file get corrupted, and you can notice this when - with the GUI - you see the expiration date of the EPO file very far in the future.

Overview

The next table has to be updated. Look at the help provided on the command line for up-to-date information.

Holux M-1200e

Characteristics

Download Instructions

Default settings seem to work, the transfer speed does not seem to have an effect.

Conversion Instructions

The log format type is special and known by BT747 as 'Holux GR-245'.  To make sure that conversion works in all cases, you have to set the correct device type on the far right of the convert button in the BT747 Desktop Application (or elsewhere in the other GUI's).

If you fail to set the correct device type, conversion may sometimes work because BT747 was able to detect hints of the device format in the device's log.