Windows 1.7 version - unexpected header

[GoogleCodeExporter]

steps to reproduce:

* Running zadig
** Options list all devices
** stm32 virtual com port -> winusb install driver
* run kalenji_reader -d . -o tcx

Output:
Using device type Kalenji 500 or 700: GH-675
Unexpected header for getList: 16
Unexpected size in header for getList: ♫ (!= 116 - 4)
Size is not a multiple of 24 in getList !

Original issue reported on code.google.com by steven.leeman on 4 May 2014 at 3:44

[GoogleCodeExporter]

Hello,

does this problem occur everytime you run the program ?
Which watch do you own ? Can you activate logs and provide it (cf 
http://code.google.com/p/kalenji-gps-watch-reader/wiki/ConfigurationFile#Log_tra
nsactions) ?
Do you have the possibility to build the software in debug and run it ? If yes, 
can you please attach the output ?

Thanks for your reports.

Regards,
Colin

Original comment by colin.pi...@gmail.com on 4 May 2014 at 3:58

[GoogleCodeExporter]

kalenji geonaute 700

It just succeeded connecting to it...
i've also installed WCD driver with zadig...although it still lists with a red X

The log file has the following info:
 => 02 00 01 85 84 
 <= 85 00 56 47 48 2d 36 37 35 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 79 00 bd 07 01 01 17 10 00 00 47 48 2d 36 37 35 00 00 00 00 00 00 00 00 4c b4 b9 07 09 12 37 c7 00 01 00 00 04 01 05 00 04 04 04 04 01 0e 05 23 00 23 2a 26 25 0f 11 13 0e 0e 23 23 23 00 00 00 33 
 => 02 00 01 78 79 
 <= 16 97 0e e1 26 01 00 aa b0 00 00 01 00 4e 00 05 00 00 00 0e 04 19 13 10 0b de 0c dd 03 01 00 15 81 00 00 01 00 68 00 06 00 00 00 0e 05 01 0b 31 1c a6 0a 29 d7 00 00 fa 67 00 00 01 00 7f 00 07 00 00 00 0e 05 02 14 05 0b 5a 07 91 94 00 00 fc 4e 00 00 01 00 92 00 08 00 00 00 0e 05 04 09 39 30 93 12 64 77 01 00 53 e2 00 00 01 00 9f 00 09 00 00 00 0a 

C:\kalenji\kalenji-gps-watch-reader>kalenji_reader.exe -d . -o TCX
Using device type Kalenji 500 or 700: GH-675
Retrieved session from 2014-04-10T22:05:41Z
Retrieved session from 2014-04-11T19:36:18Z
Retrieved session from 2014-04-13T10:23:29Z
Retrieved session from 2014-04-16T19:23:53Z
Retrieved session from 2014-04-18T19:23:09Z
Retrieved session from 2014-04-22T18:32:22Z
Retrieved session from 2014-04-25T19:16:11Z
Retrieved session from 2014-05-01T11:49:28Z
Retrieved session from 2014-05-02T20:05:11Z
Retrieved session from 2014-05-04T09:57:48Z
  Applying filter UnreliablePoints
  Applying filter EmptyLaps
Creating ./20140410_220541.tcx
  Applying filter UnreliablePoints
  Applying filter EmptyLaps
Creating ./20140411_193618.tcx
  Applying filter UnreliablePoints
  Applying filter EmptyLaps
Creating ./20140413_102329.tcx
  Applying filter UnreliablePoints
  Applying filter EmptyLaps
Creating ./20140416_192353.tcx
  Applying filter UnreliablePoints
  Applying filter EmptyLaps
Creating ./20140418_192309.tcx
  Applying filter UnreliablePoints
  Applying filter EmptyLaps
Creating ./20140422_183222.tcx
  Applying filter UnreliablePoints
  Applying filter EmptyLaps
Creating ./20140425_191611.tcx
  Applying filter UnreliablePoints
  Applying filter EmptyLaps
Creating ./20140501_114928.tcx
  Applying filter UnreliablePoints
  Applying filter EmptyLaps
Creating ./20140502_200511.tcx
  Applying filter UnreliablePoints
  Applying filter EmptyLaps
Creating ./20140504_095748.tcx

Original comment by steven.leeman on 4 May 2014 at 4:58

[GoogleCodeExporter]

Hello,

If it happens from time to time, both under windows and linux, it might be a 
communication error. I had the issue when I had this model of watch. Issue 15 
is about this. Unfortunately, I've never been able to reproduce the issue while 
sniffing USB traffic with the 'official software' under windows. I suspect 
there is a way to ask for retransmission of the packet.

Another option would be to restart the whole transfer. This would take more 
time but would allow to hide the error from the end user.

Please let me know if I misunderstood and if the error is not occuring randomly.

Regards,
Colin

Original comment by colin.pi...@gmail.com on 4 May 2014 at 7:16

[ColinPitrat]

Considering this issue as a duplicate of issue 15. Do not hesitate to reopen or open a new one if you manage to reproduce with more debug info.