skytraq-datalogger doesn't work with GT-730F

[GoogleCodeExporter]

I have a GT-730F, ubuntu linux 10.04
I'm using skytrack-datalogger recompiled with -DDEBUG_ALL flag

The gps works on windows with provided viewer software.

below fragment of debug output:

$ skytraq-datalogger  --info
...
testing for 4800 baud-rate
timeout hit
len=86
current ascii output: 
received 86 bytes
buffer as ascii contains: 
x3�&v��v�Vc&�f�6F�v��v���Sf
$GPVTG,134.7,T,,M,002.6,N,004.9,K,A*05

found needle at offset 46
NMEA detection succeeded
detected speed is 4800
>>> a0 a1 00 01 17 17 0d 0a 
Waiting for ACK with msg id 0x17
skytraq_read_next_package
PACKAGE ( length=2, msg-id=0x83, data=00 )
got ACK for msg id: 0x00
skytraq_read_next_package
PACKAGE ( length=2, msg-id=0x84, data=17 )
got NACK
No response from datalogger.

Original issue reported on code.google.com by r.krupin...@gmail.com on 8 Jul 2010 at 2:27

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

I have a ventus G730 and it works ok with Ubuntu 10.04, it's a bit of a silly 
question but have you turned the device on ?

Regards,

D

Original comment by DSRest...@gmail.com on 20 Jul 2010 at 8:46

[GoogleCodeExporter]

Thank you for answering

it doesn't have an off-switch
LED starts blinking right after I plug it in USB, just as it's supposed to.

Original comment by r.krupin...@gmail.com on 21 Jul 2010 at 12:16

[GoogleCodeExporter]

OK.  My ventus has an on/off switch and definitely doesn't work with it off.  
When I do a :-
./skytraq-datalogger --info

I get :-

kernel version: 1.4.8 -- ODM version: 1.8.22 -- revision: 2008-10-23
log_wr_ptr:      233304
total sectors:   510
sectors left:    458
max time:        3600 s
min time:        5 s
max distance:    1000 m
min distance:    0 m
max speed:       1000 km/h
min speed:       0 km/h
datalog enable:  1
log fifo mode:   0
AGPS enabled:    0
AGPS data left:  none
baud-rate:       38400 bps

which shows 38400bps, have you tried manually setting the data rate to 38400bps 
(ISTR seeing 38400 as being the default rate).

Certainly looking at the garbled output from your device, it does look like 
it's a baud rate mismatch :)

Regards,

D

Original comment by DSRest...@gmail.com on 21 Jul 2010 at 8:08

[GoogleCodeExporter]

the program scans baud rates and finds a proper one.
Initially i communicated at 4800 (or so) later I've set it up on windows to 
other rates.

In all cases it works on windows and on linux communication is dropped after 
second packet.

I really don't understand it - as seen in my first post, during baud rate scan 
the device talks, but when program actually tries to do something, it fails :-(

Original comment by r.krupin...@gmail.com on 22 Jul 2010 at 11:43