Gippy-ai-ai . . .

[ata382]

Thanks a lot for a nice piece of SW!
One possible bug or problem: I can not get 24 hour time show correctly. 12 hour time shows correctly with AM or PM, but 24 hour clock is shown 00:00 to 12:00 and then starts over again at 00:00 (and without any AM or PM notification). Bug or my misunderstanding?

/Janne

[manimaul]

Originally Posted by ata382

Thanks a lot for a nice piece of SW!
One possible bug or problem: I can not get 24 hour time show correctly. 12 hour time shows correctly with AM or PM, but 24 hour clock is shown 00:00 to 12:00 and then starts over again at 00:00 (and without any AM or PM notification). Bug or my misunderstanding?

/Janne

I'm not sure I understand the problem you are seeing. Gippy does not have the capability to display a 24 hour clock and should always show am or pm.

If you would like a 24 hour clock display. It will be an option in a future version.

[idpnd]

Originally Posted by manimaul

If you would like a 24 hour clock display. It will be an option in a future version.

yes please! the am/pm makes as much sense to us Europeans as any good old non-decimal imperial units

[ata382]

Yes please
Fully agree with idpnd.

/Janne

[svaletheia]

... If you're going to add a 24-hour option, please make it possible to eliminate the separator ":", e.g. instead of "17:24" make it possible to read "1724" for those of us used to military time formats? I would greatly appreciate it. Or perhaps just pull the time format from the system - my linux systems often have an option for that format string which I customize to remove the separator.

[Sequel]

Great program and a good addition to OpenCPN. Haven't tried it for real, 'cause the boat is still on the hard, but summer is coming...

One note though, I have not figured out how to have Gippy "remember" my settings after a session is closed down. This means that I must re-enter my settings before things work the next time (note that Gippy also "forgets" to open a virtual gps, so OpenCPN doesn't work either.)

It would also be nice if Gippy remembered where the window was parked for the last session. When it opens in the center of the screen I can't see my boat in OpenCPN.

Thanks for the good work.

[manimaul]

Gippy-1.1beta.deb

Changes:
Configuration now saved and remembered
24 hour clock available with or without : delineation

I also found a threading bug in the Google Earth KML output. This will be resolved in the next beta.

Will

[Sequel]

Thanks for quick response. Downloaded and installed 1.1beta. Installed and opened fine. Closed, tried to reopen just to check, wouldn't reopen. Ubuntu 9.10 on Dell Mini 10v, the poor man's chart plotter.

[sredna]

Why is it designed that way? I thought one of the purposes of gpsd is to let multiple apps use the same gps device, so a client wanting to do something like instrument display or posting to google would just read of the existing gpsd socket?

[manimaul]

Originally Posted by Sequel

Thanks for quick response. Downloaded and installed 1.1beta. Installed and opened fine. Closed, tried to reopen just to check, wouldn't reopen. Ubuntu 9.10 on Dell Mini 10v, the poor man's chart plotter.

Interesting...1.1 works fine on 3 of my Ubuntu test machines. Can you run gippy from the command line and tell me what terminal output get returned?

Will

[Sequel]

sequel@sequel-laptop:~$ gippy
using config file
Traceback (most recent call last):
File "/usr/bin/gippy", line 16, in <module>
frame = mainwindow.MainWindow(None, wx.ID_ANY)
File "/usr/lib/gippy/mainwindow.py", line 84, in __init__
repeatTTy.spawnVgps(globals.SerDev, int(globals.vttys), 'vgps') #create [vttys] number of virtual serials
File "/usr/lib/gippy/repeatTTy.py", line 46, in spawnVgps
termios.tcsetattr(slave_fd, termios.TCSANOW, TCatt) #set serial device attributes
TypeError: tcsetattr, arg 3: must be 7 element list (Hangs here)

NB--GPS is BU-353

Thanks for your help

[manimaul]

Gippy-1.11beta.deb

Sequel: It looks like there was a problem replicating your gps serial port attributes. I added some logic for Gippy to fall back to standard 4800 baud NMEA0183 serial port attributes for the virtual devices if it can't determine it from your gps.

Other fixes:
gpsd will autostart if specified in config
kml output will autostart if specified in config
improved serial port replication logic
improved kml output format and more robust handling of data
you can now create up to 5 virtual gps/serial output ports

Please let me know if you have problems.

Will

[manimaul]

Originally Posted by sredna

Why is it designed that way? I thought one of the purposes of gpsd is to let multiple apps use the same gps device, so a client wanting to do something like instrument display or posting to google would just read of the existing gpsd socket?

As far as I know gpsd does not handle non gps nmea sentences like depth, wind or weather. I plan on adding these capabilities to Gippy, so I decided to read directly from the 0183 data. And then optionally provide gps 0183 output to gpsd for apps that can only read from gpsd.

I am open to suggestions if I am wrong about gpsd here. I'm sure Hamish will chime in here if that is the case.

Will

[cagney]

Will
I get exactly the same error message on EeePC 901(Ubuntu 10.04) as Sequel above, even after your latest beta.
Same message if gpsd is on or off, if gps is connected or not. I have the same gps as well.
No error message on my "big" old box(Kubunto 9.10) though!
Thomas

[Sequel]

Manimaul--The link in your reply loaded 1.1beta. I tried loading from your gippy site, and 1.11beta installed and ran well. Thanks for your efforts.