-
Notifications
You must be signed in to change notification settings - Fork 11
Install and use (Linux)
To retrieve sources from git repository and build the software, you can use the following commands:
git clone https://github.com/ColinPitrat/kalenji-gps-watch-reader.git
cd kalenji-gps-watch-reader
make
If you don't want to install git, you can retrieve a zip file of the repository from the project page by clicking on 'Download ZIP' button.
Note that some dependencies are needed to build the software. You need to install the following package with your distribution's package manager:
- make
- gcc
- libusb
- libxml2
- libcurl
Additionally, if you want to build in debug mode (for reporting a bug or developing) you will need:
- ctags
- gtest
- gcov
On Move 510 and On Move 710 watches are handled as USB mass storage devices so they require a specific configuration.
You need to either give the path to the mount point where the watch content is available with -p option or specify it using path option in your configuration file (see ConfigurationFile for details).
By default, data is imported in /tmp/kalenji_import. You can modify it by editing your Configuration File. If the directory doesn't exist, it will be created.
From the directory where you built the tool:
./kalenji_reader
GPX files created can be imported in your favorite software.
This is supported for the following devices:
- W Kalenji 300 GPS
- CW Kalenji 700 GPS
- GPS On Move 500
- GPS On Move 700
- Keymaze 700 Trail
- OnMove510
- OnMove710
Let's say you have a file myRoute.gpx containing the route you want to put on your watch. You can use the following command to do so:
./kalenji_reader -D GPX -i /path/to/myRoute.gpx -f FixElevation,ComputeSessionStats,ReducePoints -o Kalenji
Note that the same kind of command can be used with different -o option to convert a GPX file to apply a filter to a GPX file or to export it to another format. See Configuration File and -h option for more details.
See Frequently Asked Questions for how to create a GPX file.
In case you encounter a core and you want to report it, you will need to use debug mode to produce a file containing debug information. You may want to build a separate version from the software in a different directory to ensure you have the last version and to not interfere with your usual working directories and configuration.
Typically:
mkdir debug_kalenji_reader
cd debug_kalenji_reader
git clone https://github.com/ColinPitrat/kalenji-gps-watch-reader.git
cd kalenji-gps-watch-reader
make debug
mkdir -p /tmp/kalenji_import
./kalenji_reader 2>&1 | tee kalenji_reader_output.txt
The output of kalenji_reader will be written in kalenji_reader_output.txt. You can attach this file, an eventual core and logs of the import to a bug report to provide more information on the problem.