--- Log opened Mon Oct 12 00:00:47 2015
01:51 -!- _rd [~rd@pD9E7C4C1.dip0.t-ipconnect.de] has joined #navit
02:02 #navit: < ambientsound> myself: thanks. I've got the Adafruit GPS hat for raspberry pi: https://learn.adafruit.com/adafruit-ultimate-gps-hat-for-raspberry-pi/overview
02:03 #navit: < ambientsound> I have no idea whether or not it's possible to crank up the rate. Perhaps by setting a larger baud rate than 9600?
02:06 -!- _rd [~rd@pD9E7C4C1.dip0.t-ipconnect.de] has quit [Ping timeout: 272 seconds]
02:11 -!- xenos1984 [~xenos1984@127-166-191-90.dyn.estpak.ee] has joined #navit
02:44 -!- _rd [~rd@pD9E7C4C1.dip0.t-ipconnect.de] has joined #navit
02:53 -!- _rd [~rd@pD9E7C4C1.dip0.t-ipconnect.de] has quit [Ping timeout: 260 seconds]
03:02 -!- Robotaxi [3ef5dbf5@gateway/web/freenode/ip.62.245.219.245] has joined #navit
03:30 -!- _rd [~rd@pD9E7C4C1.dip0.t-ipconnect.de] has joined #navit
03:57 -!- _rd [~rd@pD9E7C4C1.dip0.t-ipconnect.de] has quit [Ping timeout: 260 seconds]
04:42 -!- jonathanmaw [~jonathanm@82-70-136-246.dsl.in-addr.zen.co.uk] has joined #navit
04:59 -!- RobertP [d9f3f0ac@gateway/web/freenode/ip.217.243.240.172] has joined #navit
04:59 #navit: < RobertP> hi all
06:43 -!- jjelen [jjelen@nat/redhat/x-nuvqjzbxntjaadty] has joined #navit
07:30 -!- _rd [~rd@pD9E7C4C1.dip0.t-ipconnect.de] has joined #navit
07:40 -!- _rd [~rd@pD9E7C4C1.dip0.t-ipconnect.de] has quit [Ping timeout: 244 seconds]
07:52 -!- _rd [~rd@pD9E7C4C1.dip0.t-ipconnect.de] has joined #navit
07:58 -!- jjelen [jjelen@nat/redhat/x-nuvqjzbxntjaadty] has quit [Ping timeout: 240 seconds]
08:13 -!- jjelen [jjelen@nat/redhat/x-iurwwqmrqtnajkrl] has joined #navit
08:14 -!- _rd [~rd@pD9E7C4C1.dip0.t-ipconnect.de] has quit [Ping timeout: 246 seconds]
08:36 -!- _rd [~rd@pD9E7C4C1.dip0.t-ipconnect.de] has joined #navit
08:52 -!- jjelen [jjelen@nat/redhat/x-iurwwqmrqtnajkrl] has quit [Ping timeout: 244 seconds]
09:05 -!- jjelen [jjelen@nat/redhat/x-mctfkrbdncqpzgms] has joined #navit
09:13 -!- _rd [~rd@pD9E7C4C1.dip0.t-ipconnect.de] has quit [Ping timeout: 250 seconds]
09:20 -!- RobertP [d9f3f0ac@gateway/web/freenode/ip.217.243.240.172] has quit [Ping timeout: 246 seconds]
09:36 -!- xenos1984 [~xenos1984@127-166-191-90.dyn.estpak.ee] has quit [Quit: Leaving.]
10:17 #navit: < myself> ambientsound: Yeah, 9600 isn't likely to keep up with a 10Hz update rate, at least if you have more than a miniscule number of sentences being reported each time. Good news is that your device connects to a real hardware UART on the Pi's side, so you can spin the baud rate up to 115200 and not worry about dropping bytes. According to the Globaltop PMTK command sheet (in the adafruit gps hat downloads page),
10:17 #navit: < myself> there's a packet type 251 PMTK_SET_NMEA_BAUDRATE which you should run first, crank it up to 115200 or something, maybe 38400 if you're feeling conservative; that should still be plenty.
10:21 #navit: < myself> ambientsound: Once you've done that, use command 220 PMTK_SET_NMEA_UPDATE_RATE to set the fix interval down too 100ms, which equates to 10Hz, the fastest supported by the chipset. This may mean it draws a little more power since it's cruching numbers to solve a fix more often, but that's probably negligible. Once you've done that, gpsd should see the data at 10Hz, and navit should update more smoothly. Also
10:21 #navit: < myself> consider using 314 to set GLL, RMC, VTG to output every fix, and GGA, GSA, GSV to output every 5 fixes. That'll reduce the amount of crap that gpsd has to parse and thus conserve CPU on the Pi.
10:24 #navit: < myself> Oh hell. Seriously? These settings don't stick. According to the command sheet, "Those commdn packet for module baud rate and update rate changed only temporary, when module power reset those update rate and baud rate must be back to original setting. If user want to change baud rate and update rate of module to other value that need GTop re-edit new firmware and burning it to module". That's a heaping pile
10:24 #navit: < myself> of bullshit.
10:39 -!- Epy [6d00f9ae@gateway/web/cgi-irc/kiwiirc.com/ip.109.0.249.174] has joined #navit
11:01 -!- fredcadete [d4a63893@gateway/web/freenode/ip.212.166.56.147] has joined #navit
11:11 -!- Robotaxi [3ef5dbf5@gateway/web/freenode/ip.62.245.219.245] has quit [Ping timeout: 246 seconds]
11:44 -!- Epy [6d00f9ae@gateway/web/cgi-irc/kiwiirc.com/ip.109.0.249.174] has quit [Quit: http://www.kiwiirc.com/ - A hand crafted IRC client]
12:03 -!- tg [~x@unaffiliated/tg] has quit [Ping timeout: 255 seconds]
12:04 #navit: < ambientsound> hey, thanks a lot. Matter of fact, I've got it battery powered, so the settings hould stick.
12:05 #navit: < ambientsound> I'm curious about why gpsd doesn't already do those commands. The docs says that gpsd selects the best mode automatically.
12:05 #navit: < ambientsound> probably unsupported chipset.
12:16 #navit: < myself> can you link me to those docs? or jump on the gpsd mailing list or whatever and see about adding support
12:16 -!- tg [~x@unaffiliated/tg] has joined #navit
12:16 #navit: < ambientsound> just the man page.
12:16 #navit: < myself> ahh, and it's a case of "read the source if you want to see how it does that"
12:21 #navit: < ambientsound> hm, the raspberry pi 2 is waaay too slow to draw Navit in 10Hz
12:27 #navit: < ambientsound> looks like it can manage about 3-4Hz
12:33 -!- xenos1984 [~xenos1984@127-166-191-90.dyn.estpak.ee] has joined #navit
12:34 #navit: < myself> I'm shocked!
12:34 #navit: < myself> On the other hand, that sounds like you've got 10Hz updates working :) neat
12:34 #navit: < ambientsound> well, no, I'm just replaying NMEA messages I captured yesterday :p
12:35 #navit: < ambientsound> so I'm driving 800 km/h
12:35 #navit: < ambientsound> pretty rad
12:35 #navit: < myself> Heh.
12:35 #navit: < myself> Getaway in Stockholm, anyone?
12:35 #navit: < ambientsound> 'cept my car isn't in the same ballpark :D
12:40 #navit: < myself> You're now witnessing your car's dreams..
12:42 #navit: < ambientsound> well, even if it can't do 10hz, it looks good enough to understand.
12:42 #navit: < ambientsound> now if I could just get anti-aliasing working...
12:43 #navit: < ambientsound> ah.. so it's not implemented! I see :)
12:45 -!- jonathanmaw [~jonathanm@82-70-136-246.dsl.in-addr.zen.co.uk] has quit [Quit: Ex-Chat]
12:52 -!- jjelen [jjelen@nat/redhat/x-mctfkrbdncqpzgms] has quit [Ping timeout: 252 seconds]
13:08 -!- RobertP [5cd9e500@gateway/web/freenode/ip.92.217.229.0] has joined #navit
13:08 #navit: < RobertP> Good Evening :D
13:55 -!- _rd [~rd@pD9E7C4C1.dip0.t-ipconnect.de] has joined #navit
15:15 -!- _rd [~rd@pD9E7C4C1.dip0.t-ipconnect.de] has quit [Ping timeout: 240 seconds]
15:16 -!- jandegr [574163d9@gateway/web/freenode/ip.87.65.99.217] has joined #navit
15:21 -!- _rd [~rd@pD9E7C4C1.dip0.t-ipconnect.de] has joined #navit
15:41 -!- jandegr [574163d9@gateway/web/freenode/ip.87.65.99.217] has quit [Ping timeout: 246 seconds]
16:12 -!- RobertP [5cd9e500@gateway/web/freenode/ip.92.217.229.0] has quit []
16:21 #navit: < ambientsound> is it possible to temporarily not follow the vehicle when in navigation mode?
16:24 -!- _rd [~rd@pD9E7C4C1.dip0.t-ipconnect.de] has quit [Ping timeout: 272 seconds]
18:46 -!- xenos1984 [~xenos1984@127-166-191-90.dyn.estpak.ee] has quit [Quit: Leaving.]
--- Log closed Tue Oct 13 00:00:48 2015