Support import from computer to watch

[GoogleCodeExporter]

Some watches such as onMove 510 have a navigation function. GPX tracks can be 
imported and then followed during a training session. It would be interesting 
to add that functionnality to your tool.

Original issue reported on code.google.com by col.patr...@gmail.com on 15 Sep 2014 at 6:57

[GoogleCodeExporter]

Hello, 

this should be supported for all watches using Kalenji driver.
You just need to use -o Kalenji option. It is advised to use ReducePoints 
filter as it's not possible to upload a track with more than 200 points.

Here is an example of a command to do that. I suppose you have a file called 
'myTrack.gpx':

./kalenji_reader -D GPX -i myTrack.gpx -f 
FixElevation,ReducePoints,ComputeSessionStats -o Kalenji

There's even an helper script in svn repository: scripts/kalenji_export.sh.

Additionally, there's some explanation in the FAQ on how to create a GPX file 
from GoogleMap:
https://code.google.com/p/kalenji-gps-watch-reader/wiki/FAQ#How_can_I_easily_cre
ate_GPX_files_to_upload_to_my_watch_?

Tell me if you have an issue, or if anything is missing.

Regards,
Colin

Original comment by colin.pi...@gmail.com on 15 Sep 2014 at 7:09

• Changed state: Invalid
• Added labels: Type-Enhancement
• Removed labels: Type-Defect

[GoogleCodeExporter]

Hi,

I didn't noticed you've already developped it! I've just tried but it
didn't work :

D:\GPS>kalenji-gps-watch-reader-4.9.1_win\kalenji-gps-watch-reader\kalenji_reade
r.exe -D GPX -i Tour_etang_viry.gpx -f
FixElevation,ReducePoints,ComputeSessionS
tats -o Kalenji
  Applying filter FixElevation
    Fixed elevation of 140 points.
  Applying filter ReducePoints
    Reduced session from 219 to 219 points (min angle = pi/64).
  Applying filter ComputeSessionStats
Ascent is 126 and descent is 126
Error: couldn't export to output Kalenji:USB device not found !

Here is what I have in my conf file :
device=OnMove710
import=new
source=Path
path=F:\
directory=D:\GPS

Where is the mistake?

Patrick

2014-09-15 21:09 GMT+02:00 <kalenji-gps-watch-reader@googlecode.com>:

Original comment by col.patr...@gmail.com on 16 Sep 2014 at 5:38

[GoogleCodeExporter]

Sorry, my bad !
This is not yet supported for OnMove510 and OnMove710. I must have been tired, 
when I read your message my mind thought "Keymaze 500 Hike" for which it's 
supported through Kalenji device.

Do you have more information on how the upload works for OnMove 510 / 710 ?
This device is mounted as a USB mass storage. Can you try to upload a session 
on it with the official software under windows and see if new files are 
created, and if yes which ones ?

Once done, can you please send them to me with the GPX file you used to create 
it so that I can understand how it works ? If you don't want to put them in 
attachment (in case you want to keep them private) you can send it to me by 
mail. 

Regards,
Colin

Original comment by colin.pi...@gmail.com on 16 Sep 2014 at 6:39

• Changed state: Accepted

[GoogleCodeExporter]

Original comment by colin.pi...@gmail.com on 16 Sep 2014 at 6:40

[GoogleCodeExporter]

Here is an example : a gpx file and the 2 files created on my watch after 
import. Let me know if you need anything else.

Original comment by col.patr...@gmail.com on 17 Sep 2014 at 2:51

Attachments:

• Tour_etang_viry.zip

[GoogleCodeExporter]

Hello,

can you give me more details of what information is available for the session 
once imported on the watch ?

I see the file contains the name of the session (Tour_etang_viry). I also see 
the coordinates of the points. But I also have a few information that I don't 
know where to take from. In your example, I have the following numbers:
 - 40
 - 117 (the 40 and 117 could also be interpreted together as 10357, maybe the total distance in meters ?)
 - 135 (2 times, maybe ascent / descent ?)
 - 98

Does it ring a bell ? Do you have info visible on the watch or functionalities 
that would require some data it would represent ? 

Another 'problem' I have is how to name the file ... Could you try multiple 
export and see how the names vary ? If you copy a file and give it a custom 
name (for example TEST.GHR, or if it doesn't work something closer to the 
normal names like E9HG0000.GHR), does the watch see and recognize it ?

Once I have this information, implementing the export shouldn't be an issue.

Regards,
Colin

Original comment by colin.pi...@gmail.com on 23 Sep 2014 at 8:06

[GoogleCodeExporter]

I forgot one point, it would help me to have 2 more examples with names of 
different length. Maybe one with a small name (4 or 5 letters) and one with a 
longer name (20 letters or more).

Regards,
Colin

Original comment by colin.pi...@gmail.com on 23 Sep 2014 at 8:28

[GoogleCodeExporter]

I just commited a first attempt to support the export.
It may not fully work, in particular because of filename and session name. If 
the session name is 15 letters (as in your example), I think this should be 
fine but shorter or longer may result in an invalid result. For the filename, 
if not recognized properly by the watch, I expect the session to not appear at 
all on it.

To test it:
kalenji_reader -D GPX -f ReducePoints,ComputeSessionStats -o OnMove710 -i 
Tour_etang_viry.gpx

Note that the filter ReducePoints is needed because it seems the file cannot 
contain more than 200 points (it has a fixed size).

Regards,
Colin

Original comment by colin.pi...@gmail.com on 24 Sep 2014 at 9:14

• Changed state: Started

[GoogleCodeExporter]

I'd like to test it on my side. Can you give me a compiled version for
windows?

2014-09-24 23:14 GMT+02:00 <kalenji-gps-watch-reader@googlecode.com>:

Original comment by col.patr...@gmail.com on 25 Sep 2014 at 7:35

[GoogleCodeExporter]

Here is a windows version with this just for you.
Don't hesitate if you meet any issue with it.

Regards,
Colin

Original comment by colin.pi...@gmail.com on 26 Sep 2014 at 3:55

Attachments:

• kalenji_reader.exe

[GoogleCodeExporter]

Hello, 

did you have the opportunity to test it ? Does it work well ?

Regards,
Colin

Original comment by colin.pi...@gmail.com on 8 Nov 2014 at 9:55

[GoogleCodeExporter]

Hi,

Sorry, I've been injured for a few weeks and I didn't have any opportunity to 
test it. I'll let you know as soon as I've tried it, hopefully this week.

Best, 

Patrick 

Original comment by col.patr...@gmail.com on 8 Nov 2014 at 10:39

[GoogleCodeExporter]

Hi,

Finally, I'm back on my running shoes and I've made some tests but results
are not so good. :-S

*Test 1* :
Unable to launch kalenki_reader.exe because libcurl.dll was missing =>
After copying and pasting all the dlls from the 4.9.1 version into the same
directory as the beta version you sent me, problem was solved.

*Test 2* : 20141125_131937.gpx (see enclosed)
Filename : less than 15 characters
Session name = 15 characters

Command used : kalenji_reader -D GPX -f ReducePoints,ComputeSessionStats -o
OnMove710 -i ..\Test\20141125_131937.gpx

kalenki_reader crashed (sorry crash details are in French) :
"Signature du problème :
  Nom d’événement de problème: APPCRASH
  Nom de l’application: kalenji_reader.exe
  Version de l’application: 0.0.0.0
  Horodatage de l’application: 5425884e
  Nom du module par défaut: ntdll.dll
  Version du module par défaut: 6.1.7600.16385
  Horodateur du module par défaut: 4a5bdb3b
  Code de l’exception: c0000005
  Décalage de l’exception: 00052374
  Version du système: 6.1.7600.2.0.0.256.48
  Identificateur de paramètres régionaux: 1036
  Information supplémentaire n° 1: 72a5
  Information supplémentaire n° 2: 72a5bd4f3bed0d3b12fe6df059653792
  Information supplémentaire n° 3: 92bf
  Information supplémentaire n° 4: 92bf38eb9a7c6c5f657f23af040ec631"

*Test 3* : 111111111111111.gpx
Filename : 15 characters
Session name = 15 characters
Command used : kalenji_reader -D GPX -f ReducePoints,ComputeSessionStats -o
OnMove710 -i ..\Test\111111111111111.gpx

kalenki_reader also crashed

*Test 4* : 111111111111111.gpx
Filename : 15 characters
Session name = 15 characters
Command used : kalenji_reader -D GPX -f ReducePoints,ComputeSessionStats -o
OnMove710 -i 111111111111111.gpx

kalenki_reader also crashed (I thought that the problem was in the file
path but not...)

Best,

Patrick

2014-11-08 23:38 GMT+01:00 Collignon Patrick <col.patrick@gmail.com>:

Original comment by col.patr...@gmail.com on 4 Dec 2014 at 8:49

[GoogleCodeExporter]

Hello,

thanks for your feedback.
I think the crash you had are linked to issue 43.
I fixed it in svn, I'm attaching a fixed version for windows. Another way to 
test could be to use the following command:

kalenji_reader -D GPX -f ReducePoints,ComputeSessionStats -o
OnMove710 -p E:\ -i 111111111111111.gpx 

(assuming 111111111111111.gpx is in current directory and the watch is mounted 
on E:\)

Tell me if it doesn't fix your issue or if you encounter a new one.

Regards,
Colin

Original comment by colin.pi...@gmail.com on 9 Dec 2014 at 8:03

• Changed state: Accepted

Attachments:

• kalenji_reader.exe

[GoogleCodeExporter]

Hello,

Perhaps I can be of any assistence. 
I have tested this file kalenji_reader with my Onmove710, using Win7.
Here is what I did:

First I run about 12 km with the watch.
Then I imported this file with the kalenji_reader.
I renamed this file to 123456789012345.gpx.
Then I tried to upload this file to the watch, using the following command:

kalenji_uploader -D GPX -f ReducePoints,ComputeSessionStats -o OnMove710 -p G:\ 
-i 123456789012345.gpx 

(I renamed kalenji_reader to kalenji_uploader. Watch was mounted on G:).

During upload following errors occurred several times:
Warning: parsing of element 'bounds' in metadata not implemented in device::GPX
Warning: parcing of element 'TrackPointExtension' in trackPoint extensions not 
implemented in device::GPX
Warning: parsing of element 'lap' in trackPoint extensions not implemented in 
device::GPX

Here are the results after completing the upload process:

* Some data is imported in the watch. 

* Text on the screen says ^ no Name. This was retrieved from the Metadata in 
123456789012345.gpx.
   I changed the name in the Metadata to 123 and uploaded again. Then display shows ^ 123.

* The picture on the screen shows part of the route (seems to be the first 50 
points).
   I did tests with other files. Route seems always be limited to about 50 points.

* Text under the picture says 15009 km. Should be something like 12.44 km

Please, let me know how I can help you further.
FYI, I do have a Kalenji CW 700 too, so I can do tests on both watches. 

Best regards,
Nicolas

Original comment by eindhove...@gmail.com on 8 Mar 2015 at 9:34

[GoogleCodeExporter]

Hello,

If you want me to do some test with specific gpx-files, please upload them. I 
will perform the tests and report about the results.

Regards,
Nicolas

Original comment by eindhove...@gmail.com on 8 Mar 2015 at 11:12

[GoogleCodeExporter]

One thing I didn't noticed before. Route seems to be correct in the watch
when Metadata is filled with 'no name' (although limited to a certain maximum 
amount of point).

When changing the name in Metadata the route in the watch is corrupted.
The picture of the route is wrong and so is the text under it (something like 
-452926208 m).
The name out of the Metadata however is correctly displayed above the picture.

Original comment by eindhove...@gmail.com on 8 Mar 2015 at 12:45

[GoogleCodeExporter]

Hello, 

I have done some more testing. Here are the results.

* problems with the gpx-file *
I originally used an gpx-file generated by the kalenji-reader to avoid 
incompatibility-issues,
however it turns out that this file was causing problems after all. I replaced 
this gpx-file
by another and now uploading is working fine under some specific circumstances. 
If those
conditions are met, then the preview is oke and so are the data in the 
detailfield.

* requirements for uploading *
The gpx-file should be in the correct format. I don't know yet what caused the 
problems with
the first gpx-file. Should be investigated.

Furthermore the name of track as used in de gpx-file (metadata) should be
exactly 15 characters long, otherwise the route gets corrupted in the watch. So 
as
an example: 123456789012345 is working fine. Longer or shorter causes problems.

  <metadata>
    <name>123456789012345</name>
  </metadata>

The name of the gpx-file seems not relevant. Also the length of it seems not 
relevant.
For example, I tested with the same file under different names, e.q. 
123456789012345.gpx
and 12345678901234.gpx and 1234.gpx. Results were all the same and oke.

* Further testing *
If you can upload some specific gpx-files, I will upload them to the watch. I 
can do that
with the kalenji-reader and with the original uploader. The watch is mounted as 
an USB-device
and produces GHR-files. I can share these files with you. 

Other suggestions for testing are appreciated.

Regards,
Nicolas

Original comment by eindhove...@gmail.com on 9 Mar 2015 at 10:52

[GoogleCodeExporter]

Hello,

that's a lot of info :-)

So if I sum up:
 - you had an issue importing a GPX file created by kalenji_reader. Did you check this GPX file was what you expected with another software ? If it is, can you please attach the file so that I can try to understand what went wrong when importing it ?

 - length of the name must be 15 char so that it works. Did you try with kalenji_reader 4.9.2 available in download tab or with the executable I attached to my update #14 in this issue ? The latter should fix it but I never delivered it as I didn't get a confirmation !

 - you say that text on the screen shows "^ No name", is it expected ? (In particular, is the ^ an issue or is it the same display you have when uploading with the original uploader ?)

 - you said initially that map was wrong but I understand that with the right gpx this is OK ?

 - you said also that the distance was wrong, is this one fixed also with the right gpx when the name length is 15 char ? 

Thanks for your feedback.

Regards,
Colin

Original comment by colin.pi...@gmail.com on 9 Mar 2015 at 3:38

[GoogleCodeExporter]

Hello Colin,

I will repeat the tests to be sure and to see if I can reproduce the results. I 
will describe the steps as detailled as possible.

Q: you had an issue importing a GPX file created by kalenji_reader. Did you 
check this GPX file was what you expected with another software ? If it is, can 
you please attach the file so that I can try to understand what went wrong when 
importing it ?

A: the file created by kalenji_reader is 20150305_165657.gpx. I will upload it. 
It's quite a large file (889 kB and it contains 2896 points). I imported this 
file in SportTracks 3.1 and it looks fine. Exactly the route as it's suppose to 
be. But something went wrong during upload process.

Q: length of the name must be 15 char so that it works. Did you try with 
kalenji_reader 4.9.2 available in download tab or with the executable I 
attached to my update #14 in this issue ? The latter should fix it but I never 
delivered it as 
I didn't get a confirmation !

A: I used above mentioned 20150305_165657.gpx. And I used the executable from 
update #14. I wil upload the executable so that you can check what version it 
is. I used command: 
kalenji_uploader -D GPX -f ReducePoints,ComputeSessionStats -o OnMove710 -p G:\ 
-i 123456789012345.gpx 

I renamed kalenji_reader to kalenji_uploader. Watch was mounted on G. During 
upload the following happened:

* on the computer *
a lot of warnings on the screen
.
.
Applying filter ReducePoints
Reduced session from 2896 to 185 points (min angle = pi/59).
Applying filter ComputeSessionStat
Ascent is 143 and descent is 136
Transferred session No Name

* information on the watch *
preview screen:
No name
preview shows about the 1/3 of the route
8913 km

detailscreen:
8913 km
up: 7.54 km
down: 785 m

I opened 20150305_165657.gpx and noticed that the following was in the 
<metadata>:

  <metadata>
    <name>No name</name>
    <time>2015-03-05T15:56:57Z</time>
  </metadata>

I changed that to:

  <metadata>
    <name>123456789012345</name>
    <time>2015-03-05T15:56:57Z</time>
  </metadata>

I run the test again (exactly the same way) with the changed file. I did not 
change the filename. So filename remains 20150305_165657.gpx. During upload the 
following happened:

* on the computer *
a lot of warnings on the screen
.
.
Applying filter ReducePoints
Reduced session from 2896 to 185 points (min angle = pi/59).
Applying filter ComputeSessionStat
Ascent is 143 and descent is 136
Transferred session 123456789012345

* information on the watch *
preview screen:
123456789012345
preview shows correct route
11.03 km

detailscreen:
11.03 km
up: 143 m
down: 136 m

Conclusion: everything seems to be oke when the name in <metadata> is 15 
characters long.

Q: you say that text on the screen shows "^ No name", is it expected ? (In 
particular, is the ^ an issue or is it the same display you have when uploading 
with the original uploader ?)

A: During this test it did not show ^. So I don't think it's an issue.

Q: You said initially that map was wrong but I understand that with the right 
gpx this is OK ?

A: Everything is oke when the filename in de <metadata> is exactly 15 
characters long.

Q: you said also that the distance was wrong, is this one fixed also with the 
right gpx when the name length is 15 char ? 

A: Yes, when the filename in <metadata> is 15 characters long.

Regards,
Nicolas

Original comment by eindhove...@gmail.com on 9 Mar 2015 at 5:56

Attachments:

• kalenji_uploader.exe
• 20150305_165657.gpx

[GoogleCodeExporter]

Hello,

here is a new version of kalenji_reader.exe that I just compiled from svn.
Looking at the history, the fix I made is from Dec 13, 2014 so it can't be in 
the file I attached in comment #14. I shouldn't trust my memory :-)

This one should work with file name longer or shorter than 15 char, truncating 
it if it's longer.

I checked the parsing of the GPX file you attached and it works well (despite 
all the warnings that are just here to inform about data that is not considered 
during the import, I should remove them). So I think the issue you had were 
really only about the name needing to be a fixed 15 char string whereas I was 
sending a variable length one.

If you confirm this new kalenji_reader.exe fixes this issue, I'll redeliver a 
new version in Download section.

Regards,
Colin

Original comment by colin.pi...@gmail.com on 10 Mar 2015 at 4:04

Attachments:

• kalenji_reader.exe

[GoogleCodeExporter]

Hello Colin,

Thank you for the good work! This version looks fine. I have three small 
remarks:

1. At first attempt I got the following error:

Error: c:\tmp\kalenji_import doesn't exist and I couldn't create it

So I created the directory c:\tmp\kalenji_import manually and then the 
programme works fine. The programme doesn't seem to use this directory however?

2. If name is emtpy, like <name></name>, then kalenji_reader gives following 
error:

error basic_string::_S_construct null not valid

3. Your suggestion to suppress warnings and non-critical-errors sounds good to 
me. Perhaps with a switch (on/off) in the command line? It isn't very important 
though, so forget it if it means a lot of work.

I have no further comments yet, but I will perform some thorough testing in the 
coming month. I will inform you if any new problems occur.

Regards,
Nicolas

Original comment by eindhove...@gmail.com on 10 Mar 2015 at 7:40

[GoogleCodeExporter]

Three valid remarks !
I will look deeper into it tomorrow.

Original comment by colin.pi...@gmail.com on 10 Mar 2015 at 8:22

[GoogleCodeExporter]

Today I used guiding intensively and I found the tool to be usefull, but not 
perfect yet however. I encoutered some minor issues during the upload-process 
which I tried to solve using gpsbabel. That seemed to work out fine, but during 
guiding itself, I encoutered problems again. I will look into it deeper, to 
find out if the problems are caused by the preprocessing with gpsbabel or by 
the kalenji-reader. 

I will return the results to you. 

However that can take som time, because I'am going abroad the coming weeks. I 
plan to use the watch a lot there, so if you never hear from me againg, I'am 
probably stuck at the middle of nowhere with my watch and that guiding did'n 
turn out to be a success after all ;-) 

Original comment by eindhove...@gmail.com on 15 Mar 2015 at 11:42