--- Log opened Fri Sep 22 00:00:50 2017
00:22 -!- pmckinley [~Peter_McK@88-110-216-192.dynamic.dsl.as9105.com] has left #navit []
00:39 #navit: < Navit> The following compiles failed: http://download.navit-project.org/logs/navit/android_armv5te/svn/navit-svn-.failed http://download.navit-project.org/logs/navit/osm-exp/svn/navit-svn-.failed http://download.navit-project.org/logs/navit/src/svn/navit-svn-.failed http://download.navit-project.org/logs/navit/openmoko/svn/navit-svn-.failed http://download.navit-project.org/logs/navit/win32/svn/navit-svn-.failed http://download.navit-project.org/logs/navit/n
00:39 #navit: < Navit> oad.navit-project.org/logs/navit/android_armv4t/svn/navit-svn-.failed http://download.navit-project.org/logs/navit/android_x86/svn/navit-svn-.failed http://download.navit-project.org/logs/navit/tomtom/svn/navit-svn-.failed
00:39 #navit: < Navit> See compile results history at http://download.navit-project.org/logs/navit/stats.html
00:55 -!- youte [~youte@AStrasbourg-651-1-285-204.w86-235.abo.wanadoo.fr] has joined #navit
00:59 -!- youte [~youte@AStrasbourg-651-1-285-204.w86-235.abo.wanadoo.fr] has quit [Ping timeout: 240 seconds]
02:31 -!- youte [~youte@AStrasbourg-651-1-285-204.w86-235.abo.wanadoo.fr] has joined #navit
03:11 -!- noradtux [~noradtux@port-11914.pppoe.wtnet.de] has quit [Ping timeout: 252 seconds]
03:11 -!- noradtux [~noradtux@port-54129.pppoe.wtnet.de] has joined #navit
04:10 -!- xenos1984 [~xenos1984@22-164-191-90.dyn.estpak.ee] has joined #navit
04:53 -!- youte [~youte@AStrasbourg-651-1-285-204.w86-235.abo.wanadoo.fr] has quit [Ping timeout: 248 seconds]
05:39 #navit: < jkoan> Only thrown in the room, probably we can compile navit as webassembly like the browser plugin before. The difference would be that it is a website including the assembly, so no installation is needed
05:41 #navit: < jkoan> I think it should be possible : http://qtandeverything.blogspot.de/2017/06/qt-for-web-assembly.html?m=1
05:42 #navit: < jkoan> Also with qml2 so we could provide a demo online for everyone
05:42 #navit: < jkoan> Probably we can also include a tutorial how to test best :)
05:44 #navit: < jkoan> Also then it could help if we could have a Javascript api which is probably not such a big problem because we already have the binding support, only a new binding is need
06:28 -!- naggety [028e2e25@gateway/web/freenode/ip.2.142.46.37] has joined #navit
06:36 #navit: < jkoan> Hi naggety
06:37 #navit: < naggety> Hi!
06:42 #navit: < jkoan> Have you seen the answers to your questions?
06:45 #navit: < jkoan> kazer answerd you while you were offline
06:47 #navit: < naggety> Yes, I was reading them
06:48 #navit: < naggety> But I'm not sure if it is possible to do what he says. The talker ID can be different between 2 nmea messages of the same device.
06:49 #navit: < naggety> So I don't know if saving it makes any sense, it will be overwritten by the next nmea message with a different talker id.
06:51 #navit: < naggety> My GPS module sends some messages with talker ID "GN", but others with talker id "GP". I guess the seconds contains data provided only by GPS system, and not by GLONASS.
06:55 #navit: < jkoan> But read it out or at least have the code committed out could help in future if we need it, of course we don't need it right now
06:55 #navit: < jkoan> BTW may I ask you what company you working for? :)
06:57 #navit: < naggety> It's call Fanamoel. We are a very small spanish company.
06:59 #navit: < jkoan> i just looked on your website, really interesting :)
07:00 #navit: < jkoan> and you are in a project or something to build an decent navigation system?
07:02 -!- youte [~youte@AStrasbourg-651-1-285-204.w86-235.abo.wanadoo.fr] has joined #navit
07:02 #navit: < jkoan> hi youte
07:05 #navit: < naggety> We are in a project for a display for the bus drivers, to control all stuff of the bus: temperature, doors, music, cameras... and also GPS navigator
07:06 #navit: < jkoan> is the bus an CAN bus? :D
07:08 #navit: < naggety> Yes
07:09 #navit: < naggety> But with bus I meant the vehicle, not the communication bus
07:09 #navit: < naggety> xD
07:09 #navit: < jkoan> oh :D
07:09 #navit: < jkoan> sounds really interesting anyway
07:10 #navit: < naggety> But the bus vehicle has a CAN bus, and the display sends and receive the data throught it
07:10 #navit: < naggety> Yes, this is a nice project
07:11 #navit: < jkoan> is the displa something like a 7 segment display or more like a screen with pixels?
07:13 #navit: < naggety> Its a 7'' TFT display
07:14 #navit: < naggety> 800x480px, if I remember well
07:15 #navit: < jkoan> nice :) 
07:20 #navit: < naggety> Navit will be very useful for us. It would be very hard for such a small company to develop our own navigator, and very expensive to pay the license of a propietary one.
07:20 #navit: < naggety> And regarding myself, I always try to use free software, so I'm happy to use navit instead a propietary software  :D
07:22 #navit: < jkoan> so in future you company wants to build an own navigation system?
07:23 #navit: < jkoan> with navit inside? :)
07:27 #navit: < naggety> We are doing right now, inside the screen I told before
07:27 #navit: < jkoan> thats so interesting :O
07:28 #navit: < naggety> The bus driver (the person who drives ;-p) taps on the screen to open navit, like if it was an app
07:28 #navit: < naggety> We can say that our "screen" is like the "screens" that comes nowadays with new cars, to control music, temperature, navigation...
07:29 #navit: < jkoan> so its more build in instead of a on top device like old tomtom systems?
07:32 #navit: < naggety> Yes, it is part of the bus vehicle
07:39 #navit: < naggety> Yesterday I was translating some untranslated strings, but there is one I don't know what it means: The route must cross at least 2 heightlines
07:39 #navit: < naggety> What are heightlines? I don't know the work and I can't find it in google
07:40 #navit: < naggety> (*the word)
07:45 #navit: < jkoan> this are the lines when you look at a map and have a line on for example 400m hight around the mountain
07:45 #navit: < jkoan> on this screenshot you can see the lines: http://static.jkoan.de/cloud/index.php/s/tZi4owi6r2IypLC
07:45 #navit: < jkoan> the dotted ones
07:49 #navit: < jkoan> i tink this should be right: https://es.wikipedia.org/wiki/Isol%C3%ADnea
07:53 #navit: < naggety> Ok, the lines that mark the land heights in topographic maps
07:54 #navit: < naggety> And why is navit giving this warning? Does it matter?
07:58 #navit: < jkoan> this warning is shown if you try to look at a hight profile from a route where the profile could not been generated
07:59 #navit: < jkoan> or also if no map with heightlines is installed
08:00 #navit: < naggety> Well, I have just translated it
08:01 #navit: < jkoan> another question, how do you integrate updates of navit and maps in the bus?
08:20 #navit: < naggety> Well, we don't know yet, the product is a prototype and I have just started to integrate navit
08:23 #navit: < naggety> In fact, navit isn't running on the device yet, I have only tested it in my laptop
08:31 -!- ZeroOne [~ZeroOne@91.114.11.118] has joined #navit
08:36 #navit: < jkoan> hi ZeroOne
08:39 #navit: < ZeroOne> hi
09:54 -!- youte [~youte@AStrasbourg-651-1-285-204.w86-235.abo.wanadoo.fr] has quit [Ping timeout: 252 seconds]
09:55 -!- ZeroOne [~ZeroOne@91.114.11.118] has quit [Read error: Connection reset by peer]
10:42 -!- xenos1984 [~xenos1984@22-164-191-90.dyn.estpak.ee] has quit [Ping timeout: 248 seconds]
11:49 #navit: < naggety> I've been researching about talker IDs, and doing some tests with my gps module.
11:50 #navit: < naggety> My module allows to select which navigation system are activated, among GPS, GLONASS and BeiDu. However, only one of them must be activated at a time, except GPS+GLONASS which is allowed.
11:51 #navit: < naggety> If only one system is activated, there is no problem, because there is only one talker ID being sent.
11:53 #navit: < naggety> However, if GPS+GLONASS is activated, there are up to 3 talker ID sent. For position, speed, etc it is used 'GN'. For satellites view separated messages for each system are sent, with talker IDs 'GP' and 'GL'.
11:57 #navit: < naggety> For position and speed the module does the calculation combining the data it has gotten from both systems, so it doesn't send one message for GPS and another for GLONASS.
11:59 #navit: < naggety> The problem is that the code has a variable sats_visible and other variables about each satellite status that is only thought for GPS satellites.
12:16 #navit: < naggety> The best thing to do would be sum the satellites count from both systems, and collecting the data of the status of the satellites of both systems, indicating from which system is each one
12:17 #navit: < naggety> But I don't know if GPS+GLONASS is the single combined system that exists, so I don't know if this must be done in more cases than GPS+GLONASS
12:19 #navit: < jkoan> is this MNEA standart or is this a proprietar addition to the MNEA standart?
12:19 #navit: < naggety> I don't know
12:20 #navit: < naggety> http://www.catb.org/gpsd/NMEA.html
12:20 #navit: < naggety> http://www.catb.org/gpsd/NMEA.html#_talker_ids
12:35 -!- xenos1984 [~xenos1984@22-164-191-90.dyn.estpak.ee] has joined #navit
12:36 #navit: < naggety> I can't find a complete information, but it seems that GN means GNSS (global navigation system), and it is used when a combination of two or more systems is used
12:52 -!- magruder [redurgam@gateway/shell/panicbnc/x-mikrzslflglzlswk] has quit [Ping timeout: 255 seconds]
12:58 -!- youte [~youte@AStrasbourg-651-1-285-204.w86-235.abo.wanadoo.fr] has joined #navit
12:59 #navit: < naggety> I think it's NMEA standard. I can't find very good info about this, but it seems to be quite common among various vendors, not only mine one.
13:01 #navit: < naggety> And in the docs of my GPS module, there are separated chapters for NMEA standard sentences and propietary additions. And this is in the NMEA standard sentences chapter.
13:02 #navit: < youte> hi all !
13:04 -!- naggety [028e2e25@gateway/web/freenode/ip.2.142.46.37] has quit [Quit: Page closed]
13:32 -!- redurgam [redurgam@gateway/shell/panicbnc/x-sdtafeacaenspajt] has joined #navit
13:55 #navit: < jkoan> Hi youte
13:58 -!- youte [~youte@AStrasbourg-651-1-285-204.w86-235.abo.wanadoo.fr] has quit [Read error: Connection reset by peer]
13:58 -!- youte [~youte@AStrasbourg-651-1-285-204.w86-235.abo.wanadoo.fr] has joined #navit
14:23 -!- youte [~youte@AStrasbourg-651-1-285-204.w86-235.abo.wanadoo.fr] has quit [Ping timeout: 264 seconds]
15:38 #navit: < jkoan> The tmc module just arrived :)
16:09 -!- noradtux [~noradtux@port-54129.pppoe.wtnet.de] has quit [Quit: Bye]
16:15 -!- noradtux [~noradtux@port-54129.pppoe.wtnet.de] has joined #navit
16:25 -!- noradtux [~noradtux@port-54129.pppoe.wtnet.de] has quit [Read error: Connection reset by peer]
16:25 -!- noradtux_ [~noradtux@port-54129.pppoe.wtnet.de] has joined #navit
16:26 -!- noradtux_ is now known as noradtux
17:02 -!- youte [~youte@23-74-190-109.dsl.ovh.fr] has joined #navit
17:02 #navit: < youte> hi
17:30 #navit: < jkoan> Hi youte :D
17:40 -!- youte [~youte@23-74-190-109.dsl.ovh.fr] has quit [Ping timeout: 240 seconds]
18:03 #navit: < ilovekiruna> hi all
18:04 #navit: < jkoan> hi ilovekiruna
18:04 #navit: < ilovekiruna> jkoan: interesting comment on the js interface
18:09 #navit: < jkoan> thx
18:10 #navit: < jkoan> the biggest problem could be the graphics driver
18:16 #navit: < ilovekiruna> would the whole computing done in JS?
19:07 -!- youte [~youte@23-74-190-109.dsl.ovh.fr] has joined #navit
19:12 #navit: < jkoan> no it would been done in webassembly which is translated c code
19:13 #navit: < jkoan> sorry was afk in order to test tmc
19:13 #navit: < ilovekiruna> I c
19:15 #navit: < jkoan> at least rds is working, inside the rds we can find the rds
19:16 #navit: < ilovekiruna> i think i had sth else in mind
19:17 #navit: < ilovekiruna> i think for some reason or another emscripten was in my mind
19:17 #navit: < ilovekiruna> jkoan: hv u heard of that?
19:18 #navit: < jkoan> its about trafic informations
19:19 #navit: < ilovekiruna> emscripten about traffic informations?
19:19 #navit: < jkoan> wait, this are two different things
19:19 #navit: < ilovekiruna> yes
19:20 #navit: < ilovekiruna> emscripten is a LLVM based infrastructure to compile c code to asm.js based js code
19:20 #navit: < jkoan> emscripten is related to webassembly but i dont know how
19:21 #navit: < ilovekiruna> WebAssembly is a new binary format for executing code on the web, allowing much faster start times (smaller download, much faster parsing in browsers) for Emscripten projects. Emscripten supports compiling to WebAssembly with a compiler flag, so it is easy for projects to target both WebAssembly and asm.js.'
19:21 #navit: < ilovekiruna> so webassembly is a format
19:21 #navit: < ilovekiruna> like asm.js based one
19:21 #navit: < ilovekiruna> emscripten is more the compiler, but supports both
19:21 #navit: < jkoan> yes
19:22 #navit: < jkoan> 4
19:22 #navit: < jkoan> ups :D
19:22 #navit: < ilovekiruna> interesting, didnt know that in details, just learned now :D
19:22 #navit: < jkoan> but the thing i working on right now are traffic messages
19:23 #navit: < jkoan> not related to the other topic
19:23 #navit: < ilovekiruna> i know
19:23 #navit: < ilovekiruna> just thought about it, because of that webinterface
19:23 #navit: < jkoan> which webinterface
19:24 #navit: < jkoan> ?
19:24 #navit: < ilovekiruna> just wondering, could the navit algorithm also be provided like mapzen or osrm
19:24 #navit: < jkoan> probably, we can try it
19:24 #navit: < ilovekiruna> two chats i have in mind
19:24 #navit: < ilovekiruna> 1. your messages in the morning
19:25 #navit: < ilovekiruna> 2. i think some days ago, it was discussed that navit had a web-interface in its past at some point
19:26 #navit: < jkoan> Yes that's right, but it's not the same
19:27 #navit: < jkoan> The web interface you think of in 2 is a plugin, like the legacy Firefox addons
19:28 #navit: < jkoan> But exactly this was my idea in the morning. Because I just remembered that webassembly exists and compiles c code
19:42 #navit: < ilovekiruna> I c
21:33 #navit: <@KaZeR> hi there
21:34 #navit: <@KaZeR> jkoan: i love the qt for web assembly idea.
21:38 #navit: <@KaZeR> lots of cool stuffs have been discussed yesterday, nice :)
22:36 #navit: < youte> ^^
22:43 #navit: < jkoan> KaZeR: but first I will work on the rds and tmc thing. Tomorrow I will try to write a Firmware for arduino and Si4703 combo so we can probably use that. The main part was working today, but I have decided decrypted the tmc messages for now
22:44 #navit: < jkoan> What do you think, should I create a new repo for the firmware?
22:44 #navit: < jkoan> Like arduino-tmc?
22:45 #navit: <@KaZeR> yeah a new repo would be a good idea
22:52 #navit: < jkoan> I will create one after I have some encryption ready. Also I need to write a mechanism to ssek to the best Radio station to obtain rds signals. The question is if the car is moving and going outside the area, when we should switch to a new station. Probably the alternative frequencies and the signal strength could be an indicator. But what do you think would be the best?
22:56 #navit: <@KaZeR> yeah usually you have a signal level indicator. i don't remember which device you are using exactly but i remember that it's a really common one, so you should be fine
22:57 #navit: < jkoan> Okay, I will try tomorrow
22:57 #navit: < jkoan> Do you also have seen my private messages?
22:57 #navit: < jkoan> Those for open collective
23:14 -!- Horwitz [~mich1@p200300800E041000022268FFFE64E7C4.dip0.t-ipconnect.de] has quit [Ping timeout: 252 seconds]
23:15 #navit: <@KaZeR> ha, let me check. my irc client does not make pm very visible
23:27 -!- Horwitz [~mich1@p200300800E71F300022268FFFE64E7C4.dip0.t-ipconnect.de] has joined #navit
23:27 -!- mode/#navit [+o Horwitz] by ChanServ
23:59 #navit: < ilovekiruna> hi KaZer
--- Log closed Sat Sep 23 00:00:52 2017