armindoantunes / gh615

Automatically exported from code.google.com/p/gh615
0 stars 0 forks source link

Can't autodetect old firmware. #20

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1. No firmware detection in the config.ini e.g. autodetect
2. Old firmware e.g. 2.08 F-OTH-ON-0709031
3. python gh600_console.py

What is the expected output? What do you see instead?

It cant detect the old firmware e.g.

zingo@dual:~/bin/globalsat/gh6xx/globalsat/src$ python gh600_console.py
DEBUG _connectSerial(516): serial connection on /dev/ttyUSB0
DEBUG _writeSerial(533): writing to serialport: 020001BFBE
DEBUG _writeSerial(537): waiting at serialport: 0
DEBUG _readSerial(543): serial port returned: 
DEBUG _querySerial(556): no data at serial port, retry command #1
DEBUG _writeSerial(533): writing to serialport: 020001BFBE
DEBUG _writeSerial(537): waiting at serialport: 0
DEBUG _readSerial(543): serial port returned: 
DEBUG _disconnectSerial(524): serial connection closed
Traceback (most recent call last):
  File "gh600_console.py", line 6, in <module>
    gh = GH600()
  File "/home/zingo/bin/globalsat/gh6xx/globalsat/src/gh600.py", line 617,
in __init__
    product = self.getProductModel()
  File "/home/zingo/bin/globalsat/gh6xx/globalsat/src/gh600.py", line 499,
in serial_required_wrapper
    return function(x, *args, **kw)
  File "/home/zingo/bin/globalsat/gh6xx/globalsat/src/gh600.py", line 627,
in getProductModel
    response = self._querySerial('whoAmI')
  File "/home/zingo/bin/globalsat/gh6xx/globalsat/src/gh600.py", line 560,
in _querySerial
    raise GH600SerialException
gh600.GH600SerialException: <gh600.GH600SerialException instance at 0xb7b32f6c>

What version of the product are you using? On what operating system?

Checked out revision 163 from SVN
Watch Firmware 2.08 F-OTH-ON-0709031
Linux (Ubuntu)

Please provide any additional information below.

If I force it to "firmware: 1" in the config.ini everything seem to works ok.

Original issue reported on code.google.com by ZingoAnd...@gmail.com on 31 Aug 2008 at 12:53

GoogleCodeExporter commented 8 years ago
Well maybe not all I tried a "c" and got this...
---------------
=>c
DEBUG _connectSerial(516): serial connection on /dev/ttyUSB0
DEBUG _writeSerial(533): writing to serialport: 0200017879
DEBUG _writeSerial(537): waiting at serialport: 76
DEBUG _readSerial(543): 780048080817072023000085510000... (truncated)
INFO getTracklist(827): 3 tracks found
DEBUG _disconnectSerial(524): serial connection closed
DEBUG _connectSerial(516): serial connection on /dev/ttyUSB0
DEBUG _writeSerial(533): writing to serialport: 020009800003004D00000008CF
DEBUG _writeSerial(537): waiting at serialport: 2070
DEBUG _readSerial(543): 800812080817072023000085510000... (truncated)
DEBUG getTracks(854): initalizing new track
DEBUG getTracks(859): getting trackpoints 0-135
0:00:00
2008-08-23 07:32:35
0:00:00.100000
2008-08-23 07:32:35.100000
0:00:00.900000
2008-08-23 07:32:36
0:00:01.100000
...
2008-08-28 06:59:23.400000
0:00:00.800000
2008-08-28 06:59:24.200000
DEBUG _writeSerial(533): writing to serialport: 0200018180
DEBUG _writeSerial(537): waiting at serialport: 4
DEBUG _readSerial(543): serial port returned: 8A000000
INFO getTracks(877): number of tracks 3
DEBUG _disconnectSerial(524): serial connection closed
Traceback (most recent call last):
  File "gh600_console.py", line 223, in <module>
    main()
  File "gh600_console.py", line 130, in main
    choose()
  File "gh600_console.py", line 64, in choose
    results = gh.exportTracks(tracks,'gpx')
AttributeError: GH615 instance has no attribute 'exportTracks'
zingo@dual:~/bin/globalsat/gh6xx/globalsat/src$ 

Original comment by ZingoAnd...@gmail.com on 31 Aug 2008 at 12:58

GoogleCodeExporter commented 8 years ago
Thank you, I hope I fixed both in r164 (please test).

The GH615-part is currently hard for me to test, as I have upgraded my unit to 
the 
new firmware, and I have yet to receive word from Globalsat, that downgrading 
is 
doable. So if you find any more bugs (i am sure you will), please post them. 
Thanls.

Original comment by spei...@gmail.com on 31 Aug 2008 at 2:08