--- Log opened Thu Sep 03 00:00:49 2015
00:30 -!- xenos1984 [~xenos1984@127-166-191-90.dyn.estpak.ee] has joined #navit
01:11 -!- juse [~juse@fox5.kyla.fi] has joined #navit
01:50 -!- juse [~juse@fox5.kyla.fi] has quit [Ping timeout: 256 seconds]
02:32 -!- Robotaxi [3ef5dbf5@gateway/web/freenode/ip.62.245.219.245] has joined #navit
02:35 -!- jjelen [jjelen@nat/redhat/x-lyetwjeuupumafux] has joined #navit
02:35 -!- rd_ [~rd@p57A0FB49.dip0.t-ipconnect.de] has joined #navit
03:09 -!- rd_ [~rd@p57A0FB49.dip0.t-ipconnect.de] has quit [Ping timeout: 255 seconds]
04:02 -!- rd_ [~rd@p57A0FB49.dip0.t-ipconnect.de] has joined #navit
04:15 -!- jonathanmaw [~jonathanm@82-70-136-246.dsl.in-addr.zen.co.uk] has joined #navit
04:42 -!- jonathanmaw [~jonathanm@82-70-136-246.dsl.in-addr.zen.co.uk] has quit [Read error: Connection reset by peer]
04:43 -!- jonathanmaw [~jonathanm@82-70-136-246.dsl.in-addr.zen.co.uk] has joined #navit
06:58 -!- _rd_ [~rd@p4FD1C003.dip0.t-ipconnect.de] has joined #navit
07:01 -!- rd_ [~rd@p57A0FB49.dip0.t-ipconnect.de] has quit [Ping timeout: 250 seconds]
07:16 -!- _rd_ [~rd@p4FD1C003.dip0.t-ipconnect.de] has quit [Ping timeout: 244 seconds]
07:17 -!- _rd_ [~rd@p4FD1C003.dip0.t-ipconnect.de] has joined #navit
07:25 -!- robertp [bc5c2134@gateway/web/freenode/ip.188.92.33.52] has joined #navit
07:30 -!- _rd_ [~rd@p4FD1C003.dip0.t-ipconnect.de] has quit [Ping timeout: 265 seconds]
10:00 -!- jjelen [jjelen@nat/redhat/x-lyetwjeuupumafux] has quit [Ping timeout: 244 seconds]
10:44 -!- jandegr [50c83746@gateway/web/freenode/ip.80.200.55.70] has joined #navit
11:22 -!- _rd_ [~rd@p4FD1C003.dip0.t-ipconnect.de] has joined #navit
11:44 -!- _rd_ [~rd@p4FD1C003.dip0.t-ipconnect.de] has quit [Ping timeout: 246 seconds]
11:58 -!- Robotaxi [3ef5dbf5@gateway/web/freenode/ip.62.245.219.245] has quit [Ping timeout: 246 seconds]
11:58 -!- _rd_ [~rd@p4FD1C003.dip0.t-ipconnect.de] has joined #navit
12:24 -!- juse [~juse@fox5.kyla.fi] has joined #navit
12:27 -!- jonathanmaw [~jonathanm@82-70-136-246.dsl.in-addr.zen.co.uk] has quit [Quit: Ex-Chat]
12:42 #navit: < KaZeR> hi there
13:08 -!- tryagain_ [~nobody@217.118.95.118] has joined #navit
13:09 #navit: < tryagain_> KaZeR: hi
13:15 -!- tryagain_ [~nobody@217.118.95.118] has quit [Remote host closed the connection]
13:15 -!- _rd_ [~rd@p4FD1C003.dip0.t-ipconnect.de] has quit [Ping timeout: 256 seconds]
13:19 -!- _rd_ [~rd@p4FD1C003.dip0.t-ipconnect.de] has joined #navit
13:33 -!- robertp_ [584aaf83@gateway/web/freenode/ip.88.74.175.131] has joined #navit
13:40 -!- juse [~juse@fox5.kyla.fi] has quit [Ping timeout: 250 seconds]
13:49 -!- zoff99 [~chatzilla@unaffiliated/zoff99] has joined #navit
14:05 -!- pini [~pini@bou-fi.pustule.org] has joined #navit
14:09 -!- pini [~pini@bou-fi.pustule.org] has quit [Ping timeout: 244 seconds]
14:12 -!- circleci-bot [~circleci-@ec2-54-87-79-121.compute-1.amazonaws.com] has joined #navit
14:12 #navit: < circleci-bot> Failed: pgrandin's build (#563; push) in navit-gps/navit (i18n/en_GB.po) -- https://circleci.com/gh/navit-gps/navit/563
14:12 -!- circleci-bot [~circleci-@ec2-54-87-79-121.compute-1.amazonaws.com] has quit [Client Quit]
14:31 #navit: < Marc0> hi
14:32 #navit: < Marc0> back from holidays
14:32 -!- circleci-bot [~circleci-@ec2-54-237-108-148.compute-1.amazonaws.com] has joined #navit
14:32 #navit: < circleci-bot> Failed: pgrandin's build (#565; push) in navit-gps/navit (i18n/en_GB.po) -- https://circleci.com/gh/navit-gps/navit/565
14:32 -!- circleci-bot [~circleci-@ec2-54-237-108-148.compute-1.amazonaws.com] has quit [Client Quit]
14:35 #navit: < Marc0> I was abroad, at it was quite expensive to always chose the country as this seems to be "determined" by the localization of the app, no?
14:36 #navit: < Marc0> isn't it more probable that my destination is within the country I'm currently in?
14:37 #navit: < Marc0> so shouldn't the default country be determined by my current GPS coordinates?
14:38 -!- zoff99 [~chatzilla@unaffiliated/zoff99] has quit [Read error: Connection reset by peer]
14:38 -!- zoff99_ [~chatzilla@chello062178222003.13.15.vie.surfer.at] has joined #navit
14:38 -!- zoff99_ is now known as zoff99
14:39 -!- _rd_ [~rd@p4FD1C003.dip0.t-ipconnect.de] has quit [Ping timeout: 250 seconds]
14:45 -!- juse [~juse@82.130.13.181] has joined #navit
14:51 -!- circleci-bot [~circleci-@ec2-54-166-108-178.compute-1.amazonaws.com] has joined #navit
14:51 #navit: < circleci-bot> Failed: pgrandin's build (#564; ssh by pgrandin) in navit-gps/navit (trunk) -- https://circleci.com/gh/navit-gps/navit/564
14:51 -!- circleci-bot [~circleci-@ec2-54-166-108-178.compute-1.amazonaws.com] has quit [Client Quit]
14:55 -!- zoff99 [~chatzilla@chello062178222003.13.15.vie.surfer.at] has quit [Quit: ChatZilla 0.9.86-rdmsoft [XULRunner 1.9.1/20090707221522]]
14:57 -!- zoff99 [~chatzilla@unaffiliated/zoff99] has joined #navit
15:00 -!- _rd_ [~rd@p4FD1C003.dip0.t-ipconnect.de] has joined #navit
15:14 -!- _rd_ [~rd@p4FD1C003.dip0.t-ipconnect.de] has quit [Ping timeout: 244 seconds]
15:18 -!- tryagain [~quassel@178.216.76.79] has joined #navit
15:19 #navit: < KaZeR> hey Marc0
15:19 #navit: < KaZeR> mmm. not sure i understand your concern. can you elaborate please ?
15:32 #navit: < tryagain> i guess the problem is that in town search in internal gui we always start searching in the country determined by curent locale, not current location.
15:36 #navit: < Marc0> tryagain: exactly
15:37 #navit: < Marc0> I was in Czech republic, and no matter which address I was searching, I started "in Germany"
15:39 #navit: < tryagain> yes, that should really be changed. But i'm unsure if "by current location" is proper way. I think "most recently used" is better way to go. Also a list of recent selections would be useful.
15:40 #navit: < tryagain> current location is best right after installation, when no recent selection available
15:41 #navit: < Marc0> tryagain: don't get that. why not current location?
15:42 #navit: < tryagain> sometimes you may plan a route to a different country, so searching for some towns you plan to visit in a row
15:43 #navit: < tryagain> with "by location" way you would always have to choose your planned country
15:44 -!- robertp_ [584aaf83@gateway/web/freenode/ip.88.74.175.131] has quit [Ping timeout: 246 seconds]
15:44 #navit: < Marc0> I see, when using additional waypoints, no?
15:45 #navit: < tryagain> yep, additional waypoints, or maybe just willing to become a bit more familar with some towns you will be driving through
15:47 #navit: < Marc0> that's really another way to navigate than I'm used to ;)
15:47 #navit: < Marc0> I always have "a destination"
15:52 #navit: < tryagain> even when you travel for a business, you may wish to go siteseeing, or decide to choose one or another town for a night stop
15:53 #navit: < Marc0> additionally searching Czech street names was a mess
15:53 #navit: < Marc0> but that could be due to OSM data
15:56 #navit: < Marc0> searching for "Nova" in Mělník didn't find any result
15:56 #navit: < Marc0> but the street is displayed correctly
16:04 -!- myself [~myself@ignignokt.mudkips.net] has joined #navit
16:07 #navit: < tryagain> Marc0 navit needs town boundary to find streets correctly. In Czech, we use default: there has to be a polygone tagged as place=town/village/city around it
16:08 #navit: < tryagain> we need additional info about Czech town boundary taging practice, see http://trac.navit-project.org/ticket/1097#comment:4
16:09 -!- jandegr [50c83746@gateway/web/freenode/ip.80.200.55.70] has quit [Quit: Page closed]
16:10 #navit: < Marc0> I see
16:11 #navit: < Marc0> like this? http://www.openstreetmap.org/relation/437581
16:15 #navit: < Marc0> so admin_level=8
16:18 -!- zoff99 [~chatzilla@unaffiliated/zoff99] has quit [Quit: ChatZilla 0.9.86-rdmsoft [XULRunner 1.9.1/20090707221522]]
16:20 #navit: < Marc0> should maptool "translate" this admin_level to a town boundary?
16:20 #navit: < Marc0> (by country)
16:24 #navit: < tryagain> Probably yes. We also could use some additional higher level admin_levels to mark country subdivisions to distinguish towns with identical names
16:33 #navit: < myself> Can navit make productive use of a GPS that provides solutions more often than 0.5Hz (NMEA default)? I'm using a Ublox 5-series and not sure how to configure the update rate. (I can go up to 10Hz, not sure how often actual solutions are calculated but I know it's at least 4Hz.)
16:34 #navit: < KaZeR> hey myself. an easy way to solve that is to delegate this setting to gpsd
16:35 #navit: < KaZeR> altough, i believe that some gps devices send less accurate position if they send it more often (would have to check that)
16:40 #navit: < Marc0> I'm finished for today... good night
16:40 #navit: < myself> Nah, I know the UBX behavior pretty well. Some chips will send the same position in subsequent packets if they haven't had time to compute a new solution, but they don't *lose* precision in doing so. From what I've seen, gpsd can recognize higher update rates, it's more a question of whether navit will ask gpsd for that data. Harmless to crank it up, I suppose...
16:41 #navit: < KaZeR> bye Marc0
16:41 #navit: < KaZeR> myself: navit does not ask for that data, it processes as an event whenever it is received. is this for linux ?
16:42 #navit: < myself> It'll be on linux, yeah. I'm the guy with the soldering-iron and the UART pinout hooking up the GPS receiver and not sure how to configure it, someone else will be doing the software side of things. If it's event-driven then I'm certain it'll be happy with higher rates, that's what I needed to know.
16:45 -!- circleci-bot [~circleci-@ec2-54-157-61-47.compute-1.amazonaws.com] has joined #navit
16:45 #navit: < circleci-bot> Failed: pgrandin's build (#566; ssh by pgrandin) in navit-gps/navit (i18n/en_GB.po) -- https://circleci.com/gh/navit-gps/navit/566
16:45 -!- circleci-bot [~circleci-@ec2-54-157-61-47.compute-1.amazonaws.com] has quit [Client Quit]
16:46 #navit: < KaZeR> cool. what are you building? i love to hear about projects!
16:47 #navit: < myself> Genivi demo platform, at the moment.
16:48 #navit: < KaZeR> oh ok. i was curious about the progress of this. it's quite difficult to find updates
16:48 #navit: < myself> That's why I'm so glad I'm responsible for the hardware part :P
16:49 #navit: < KaZeR> you work directly for Genivi? They are base in my area IIRC..
16:49 #navit: < KaZeR> *based*
16:50 #navit: < myself> Nope, just that my group at another company decided to try to implement genivi to see if we could do it.
16:50 #navit: < KaZeR> ok. can you tell us more?
16:51 #navit: < myself> There's not much more to say yet. We've ripped the old stereo/cluster out of a vehicle, and our project is to replace that with an embedded board running Genivi.
16:51 #navit: < myself> And maybe bolt on some other functions if we're able. :)
16:53 #navit: < KaZeR> are you doing this for a company funded project? or mostly by yourself?
16:54 #navit: < myself> It's company funded. I've made sure they know, in no uncertain terms, that if they make fixes to the opensource stuff, checking them back into the codebase is part of the bargain. :)
16:55 #navit: < KaZeR> cool. it wasn't the idea behind my question, but it's nice to know :)
16:55 #navit: < KaZeR> i'm curious about that because i've been thinking about swapping the cluster in my car a couple of times ( to have a small LCD there)
16:55 #navit: < myself> Hehe. It's easy to get caught up in the NDA-happy attitude of industry, I've taken it as my job to make sure people understand that opensource is more than free shit. :P
16:56 #navit: < KaZeR> awesome :D
16:56 #navit: < myself> Ahh. That's the hard part, getting the data for all the gauges and idiot-lights on the cluster.
16:56 #navit: < KaZeR> yeah. what car are you working on?
16:56 #navit: < KaZeR> can you tell us your company name?
16:57 #navit: < myself> A 5-year-old nissan, and no I don't think I should at this point :)
16:57 #navit: < KaZeR> ok np.
16:58 #navit: < myself> In many vehicles, the cluster also acts as a gateway between different buses in the vehicle, so you might not be able to remove it completely (without doing a LOT of work, like, years of development), so you could possibly relocate it somewhere hidden and just put an LCD in its place.
16:58 #navit: < myself> Also there's often a legal requirement to keep the odometer connected whenever the vehicle is being driven, otehrwise you have to file papers when you sell the car explaining the "malfunction" and missing mileage
16:59 #navit: < KaZeR> yeah. and actually accurate mileage is something i'd like to keep. part of why i never really dug into this idea too much.
17:01 #navit: < myself> Well, if you look at the service manuals' wiring diagrams, you can build a list of all the signals that go into the cluster, and figure out what's needed to replace it.
17:04 #navit: < KaZeR> i dug into the bus a bit already. i know that the mileage is broadcasted on the bus for example. but indeed i don't know if it's sent from the cluster, or if it's read from there
17:05 #navit: < myself> In most cars, the ABS module reads the wheel-tick and sends distance packets, then the cluster accumulates the mileage and sends the totalized odometer for anyone who needs it
17:05 #navit: < myself> s/distance/speed-and-distance/
17:05 #navit: < myself> so the cluster is reading that for the speedometer
17:23 #navit: < KaZeR> ok. makes sense.
17:24 #navit: < KaZeR> actually i've been trying to figure out the SAE j1850 protocol. i got some useful items, some less useful, and i'm still looking for some informations ( external temperature, for example)
17:30 -!- juse [~juse@82.130.13.181] has quit [Ping timeout: 272 seconds]
17:49 -!- xenos1984 [~xenos1984@127-166-191-90.dyn.estpak.ee] has quit [Quit: Leaving.]
17:56 #navit: < myself> that's not standard, but intake air temperature might be pretty close
17:56 #navit: < myself> but yeah, if your car has an external temp display, there's a good chance it comes in as a single analog wire from the sensor
17:57 #navit: < KaZeR> i haven't looked into it for some time, but i'd like to crack a few more items.
17:58 #navit: < KaZeR> single analog wire from the sensor -> so you think this is not sent over can-bus?
18:11 -!- tg [~x@unaffiliated/tg] has quit [Ping timeout: 240 seconds]
18:13 -!- tg [~x@unaffiliated/tg] has joined #navit
18:23 #navit: < myself> the wiring diagrams will show you where the sensor wiring goes and what signals to expect on it, for diagnostic reasons
18:23 #navit: < myself> if it specifies an analog signal, there's your answer!
18:27 #navit: < KaZeR> indeed. thanks!
18:28 #navit: < KaZeR> "The temperature function is supported by the ambient temperature sensor, a wiring circuit, the Body Control Module (BCM), the Programmable Communications Interface (PCI) data bus, and a portion of the Electronic Vehicle Information Center (EVIC) module. "
18:28 #navit: < KaZeR> so it has to be there. damn it.
18:34 #navit: < myself> You're using Busmaster to do the spying, I assume? Unplug the sensor and see what changes.
18:34 #navit: < myself> the free version of VehicleSpy is pretty sweet too, if you have a supported interface
18:34 -!- tryagain [~quassel@178.216.76.79] has quit [Remote host closed the connection]
18:36 #navit: < KaZeR> actually i'm using a cheapo usb obd2 device, and some home made code. i'm able to dump the frames, and i analyze them seperately. i'll look into vehiclespy tho
18:37 #navit: < KaZeR> but yeah that idea with the sensor is great. the spec sheet says that i should read -40F if the device is unplugged
20:39 #navit: < Navit> The following compiles failed: http://download.navit-project.org/logs/navit/android_armv5te/svn/navit-svn-12310.failed http://download.navit-project.org/logs/navit/osm/svn/navit-svn-12310.failed http://download.navit-project.org/logs/navit/src/svn/navit-svn-12310.failed http://download.navit-project.org/logs/navit/wince_386/svn/navit-svn-12310.failed http://download.navit-project.org/logs/navit/wince_cmake/svn/navit-svn-12310.failed http://download.na
20:39 #navit: < Navit> avit-svn-12310.failed http://download.navit-project.org/logs/navit/openmoko/svn/navit-svn-12310.failed http://download.navit-project.org/logs/navit/win32_cmake/svn/navit-svn-12310.failed http://download.navit-project.org/logs/navit/win32/svn/navit-svn-12310.failed http://download.navit-project.org/logs/navit/win32_gtk_cmake/svn/navit-svn-12310.failed http://download.navit-project.org/logs/navit/n800/svn/navit-svn-12310.failed http://download.navit-pro
20:39 #navit: < Navit> /navit-svn-12310.failed http://download.navit-project.org/logs/navit/android_x86/svn/navit-svn-12310.failed http://download.navit-project.org/logs/navit/tomtom/svn/navit-svn-12310.failed http://download.navit-project.org/logs/navit/iphone/svn/navit-svn-12310.failed
20:39 #navit: < Navit> See compile results history at http://download.navit-project.org/logs/navit/stats.html
21:38 #navit: < Navit> The following compiles failed: http://download.navit-project.org/logs/navit/android_armv5te/svn/navit-svn-12310.failed http://download.navit-project.org/logs/navit/osm/svn/navit-svn-12310.failed http://download.navit-project.org/logs/navit/src/svn/navit-svn-12310.failed http://download.navit-project.org/logs/navit/wince_386/svn/navit-svn-12310.failed http://download.navit-project.org/logs/navit/wince_cmake/svn/navit-svn-12310.failed http://download.na
21:38 #navit: < Navit> avit-svn-12310.failed http://download.navit-project.org/logs/navit/openmoko/svn/navit-svn-12310.failed http://download.navit-project.org/logs/navit/win32_cmake/svn/navit-svn-12310.failed http://download.navit-project.org/logs/navit/win32/svn/navit-svn-12310.failed http://download.navit-project.org/logs/navit/win32_gtk_cmake/svn/navit-svn-12310.failed http://download.navit-project.org/logs/navit/n800/svn/navit-svn-12310.failed http://download.navit-pro
21:38 #navit: < Navit> /navit-svn-12310.failed http://download.navit-project.org/logs/navit/android_x86/svn/navit-svn-12310.failed http://download.navit-project.org/logs/navit/tomtom/svn/navit-svn-12310.failed http://download.navit-project.org/logs/navit/iphone/svn/navit-svn-12310.failed
21:38 #navit: < Navit> See compile results history at http://download.navit-project.org/logs/navit/stats.html
--- Log closed Fri Sep 04 00:00:50 2015