igotu2gpx team mailing list archive

[Jan-Gerard <729004@xxxxxxxxxxxxxxxxxx>]

Hereby, the response of the INFO command: 
>>>>>

C:\localdata\bin\GPS_Trackloggers\igotu2gpx-0.3.0\bin>igotu2gpx.exe -v -d serial:4 info
Downloading configuration...
Command: 930101030000000000000000000000
Result:
Command: 930a00000000000000000000000000
Result: c2860400051800030000
Command: 9305040003019f0000000000000000
Result: c22017
Command: 930b03001d00000000000000000000
Result: 00157e
Command: 930507100004030000000000000000
Protocol violated : Invalid response packet: 00157e
Command: 930507100004030000000000000000
Device error: Device responded with error code: -2
Command: 930507100004030000000000000000
Device error: Device responded with error code: -1
Command: 930507100004030000000000000000
Device error: Device responded with error code: -1
Command: 930507100004030000000000000000
Failed: Device responded with error code: -1
Unable to download configuration from GPS tracker: Device responded with error code: -1

>>>>

Maybe this can help to identify the issue.

-- 
You received this bug notification because you are a member of
MobileAction i-gotU USB GPS travel logger Mac/Linux developers, which is
subscribed to igotu2gpx.
https://bugs.launchpad.net/bugs/729004

Title:
  Track download from GT-600 fails with errors

Status in MobileAction i-gotU USB GPS travel logger Mac/Linux support:
  New

Bug description:
  Connecting to the GT-600 fails many times, but when the iGotU is recognized, I get an error message and no track.
  When issuing the command: igotu2gpx.exe -v -d serial:4 dump
  this is te response: >>>>

  Downloading tracks...
  Command: 930101030000000000000000000000
  Protocol violated : Response too short: expected 3, got 0 bytes
  Command: 930101030000000000000000000000
  Protocol violated : Response too short: expected 3, got 0 bytes
  Command: 930101030000000000000000000000
  Protocol violated : Response too short: expected 3, got 0 bytes
  Command: 930101030000000000000000000000
  Protocol violated : Response too short: expected 3, got 0 bytes
  Command: 930101030000000000000000000000
  Protocol violated : Response too short: expected 3, got 0 bytes
  Command: 930101030000000000000000000000
  Failed: Response too short: expected 3, got 0 bytes
  Unable to download trackpoints from GPS tracker: Response too short: expected 3,
   got 0 bytes
  >>>>

  Meanwhile, I made a log of the serial port with
  sysinternals/portmon.exe: >>>>

  0.00006509	igotu2gpx.exe	IRP_MJ_CREATE	gpstracer@9	SUCCESS	Options: Open 	
  0.00000279	igotu2gpx.exe	IOCTL_SERIAL_SET_TIMEOUTS	gpstracer@9	SUCCESS	RI:10 RM:0 RC:200 WM:2 WC:1000	
  0.00000223	igotu2gpx.exe	IOCTL_SERIAL_PURGE	gpstracer@9	SUCCESS	Purge: TXCLEAR RXCLEAR	
  0.00000112	igotu2gpx.exe	IOCTL_SERIAL_PURGE	gpstracer@9	SUCCESS	Purge: TXCLEAR RXCLEAR	
  0.00028300	igotu2gpx.exe	IRP_MJ_WRITE	gpstracer@9	* 0xC0000001	Length 8: ........	
  0.00000112	igotu2gpx.exe	IRP_MJ_CLEANUP	gpstracer@9	INVALID DEVICE REQUEST		
  0.00000754	igotu2gpx.exe	IRP_MJ_CLOSE	gpstracer@9	SUCCESS		

  >>>>

  It seems like the igotu does not respond at all to this command. It is connected, however, because I once got this response: >>>>
  C:\localdata\bin\GPS_Trackloggers\igotu2gpx-0.3.0\bin>igotu2gpx.exe -v -d serial
  :4 dump
  Downloading tracks...
  Command: 930101030000000000000000000000
  Device error: Device responded with error code: -2
  Command: 930101030000000000000000000000
  Result:
  Command: 930a00000000000000000000000000
  Result: c2860400051800030000
  Command: 930b03001d00000000000000000000
  Result: 00157e
  Downloaded block 0/44
  Command: 930507100004030000000000000000
  Protocol violated : Invalid response packet: 00157e
  Command: 930507100004030000000000000000
  Failed: Unable to send data to device: A device attached to the system is not fu
  nctioning.

  Unable to download trackpoints from GPS tracker: Unable to send data to device:
  A device attached to the system is not functioning.
  >>>>>

  It started downloading a block of data, but failed. 
  Do I have to set serial port settings of the virtual com port, like baudrate, etc? 

  Kind regards, 
  Jan-Gerard