--- Log opened Fri Nov 09 00:00:59 2018
06:03 -!- xenos1984 [~xenos1984@2001:bb8:2002:200:6651:6ff:fe53:a120] has joined #navit
06:03 -!- mode/#navit [+v xenos1984] by ChanServ
06:07 #navit: <+Navit> <jkoan> @KaZeR the it begun : https://twitter.com/BBBikeWorld/status/266654253882417152?s=19 Exactly 6 years ago
07:24 -!- naggety [~naggety@168.red-79-149-27.dynamicip.rima-tde.net] has joined #navit
09:10 -!- naggety [~naggety@168.red-79-149-27.dynamicip.rima-tde.net] has quit [Quit: Konversation terminated!]
12:23 -!- naggety [~naggety@197.red-2-141-101.dynamicip.rima-tde.net] has joined #navit
13:07 -!- rokm [rokm@freeshell.de] has joined #navit
13:07 #navit: < rokm> Hi, Is someone here who can help me with my problem ?
13:35 #navit: < naggety> hi rokm: some people here are usually able to help with many problems, but they may not be reading the chat all the time. I suggest you to explain your problem, and when they can they will answer. If you have gone when they answer, you can connect later and read the logs.
13:37 #navit: < rokm> Sure
13:41 #navit: < rokm> I tried to simulate keyboard keys via /dev/uinput to Navit, I tested my simple app and events are visible on /dev/input/event1, evtest also shows that on this part all is OK. On Navit side there is no action (I binded character with button with accesskey= in navit.xml)
13:42 #navit: < rokm> So there is my question is it possible to inject keyboard event to Navit in that way ?
14:03 -!- naggety [~naggety@197.red-2-141-101.dynamicip.rima-tde.net] has quit [Quit: Konversation terminated!]
15:41 -!- xenos1984 [~xenos1984@2001:bb8:2002:200:6651:6ff:fe53:a120] has quit [Quit: Leaving.]
16:03 -!- xenos1984 [~xenos1984@22-164-191-90.dyn.estpak.ee] has joined #navit
16:03 -!- mode/#navit [+v xenos1984] by ChanServ
17:21 #navit: <@KaZeR> hi there
17:22 #navit: <@KaZeR> rokm: i did something similar a while ago let's see if i can find it
17:22 -!- basilic_ [~basilic@228-221-190-109.dsl.ovh.fr] has joined #navit
17:22 #navit: < basilic_> hello all
17:23 #navit: <@KaZeR> rokm: while this might work it's still a bit hacky and maybe there's a better way. what's your end goal?
17:23 #navit: <@KaZeR> hi basilic_ !
17:23 #navit: < basilic_> what's news on navit since last years (or maybe 2...)
17:24 #navit: < basilic_> seems nothing :) last release was 2015 :)
17:27 #navit: <@KaZeR> basilic_: really? https://github.com/navit-gps/navit/releases
17:27 #navit: <@KaZeR> where did you see that?
17:27 #navit: <@KaZeR> we also have a new website
17:28 #navit: < basilic_> here: https://wiki.openstreetmap.org/wiki/FR:Navit
17:29 #navit: < basilic_> that good, I will start (with 3 ou 4 years of late) start my car gps
17:30 #navit: < basilic_> The last part to done is only the install of raspberry pi and peripherical :)
17:30 #navit: < basilic_> and Navit
17:31 #navit: <@KaZeR> basilic_: thanks we'll add a note to update that page to our release procedure!
17:31 #navit: <@KaZeR> we've also done a lot of progress on supporting the raspberry pi. we have a buildroot setup for example now, that allows you to easily build a very small image optimized for the pi
17:32 #navit: < basilic_> cool
17:32 #navit: < basilic_> where is it?
17:32 #navit: < basilic_> based on raspbian?
17:34 #navit: <@KaZeR> buildroot isn't based on raspbian, it's a different way of building images. For example, by default it doesn't contain a package manager
17:35 #navit: <@KaZeR> https://github.com/pgrandin/navit-buildroot i need to move it under the navit-gps org at some point
17:35 #navit: <@KaZeR> if you tell me more about what you want in the image we can customize it for your needs
17:35 #navit: < basilic_> the MP3 branch is always active?
17:36 #navit: < basilic_> In fact I would like play MP3 and run navit basicly
17:37 #navit: <@KaZeR> robert was the one working on that. he's been quite lately but i can ping him
17:37 #navit: <@KaZeR> are you using a pi2 or a pi3 ?
17:37 #navit: < basilic_> pi 3 B+
17:38 #navit: < basilic_> I have build my hardware for drive screen and manage power
17:39 #navit: < basilic_> I need, display with S-video
17:39 #navit: < basilic_> shutdown with GPIO signal
17:39 #navit: <@KaZeR> is your hardware open source?
17:40 #navit: < basilic_> for function need GPS and MP3 player
17:40 #navit: < basilic_> Yes and not
17:40 #navit: < basilic_> :)
17:40 #navit: < basilic_> in few weeks I commit it in github
17:40 #navit: < basilic_> but for the moment I run test
17:41 #navit: < basilic_> https://drive.google.com/file/d/1d9Z7IjxW7kSH4gTraAdEQEmTk5dCj_vm/view
17:41 #navit: < basilic_> here you can see the green board
17:41 #navit: < basilic_> and it's work: https://drive.google.com/file/d/1zJhxBUqZ2Lcyj_f1SvZbz_RM7Bu5eGsH/view
17:42 #navit: < basilic_> on a table
17:42 #navit: < basilic_> I need to done some adjust in timing
17:42 #navit: < basilic_> at start on the video I have a long temporisation (15sec) before autorize open
17:43 #navit: < basilic_> the board is use for drive the motor
17:43 #navit: < basilic_> manage the power
17:43 #navit: < basilic_> power of the board and raspberry pI
17:44 #navit: < basilic_> by switching between power after contact and permanent power
17:44 #navit: < basilic_> manage the LCD power
17:44 #navit: < basilic_> not visible on the video
17:44 #navit: < basilic_> but power on the LCD when open and power off if close
17:44 #navit: < basilic_> and for the shutdown, send a contact to the raspberry pi
17:45 #navit: < basilic_> and for my usage the board use the orignal connector of my car
17:45 #navit: < basilic_> no need to modify
17:46 #navit: < basilic_> i already done the main connector: https://drive.google.com/open?id=1nKROJnn5kigm8XUh_nTZDjTsIrmzIAlC
17:46 #navit: <@KaZeR> really nice! you HAVE to publish this
17:46 #navit: < basilic_> Yes I have prepare it
17:47 #navit: <@KaZeR> i love the 3d printed connector. very smart
17:47 #navit: < basilic_> https://github.com/Basilic/RX8_CARPC_Screen
17:47 #navit: < basilic_> here
17:47 #navit: < basilic_> :)
17:47 #navit: < basilic_> in a future
17:47 #navit: < basilic_> yes I don't find the good connector after long search
17:48 #navit: < basilic_> The next board if for connect the orignal command on the raspberry
17:48 #navit: < basilic_> using and HID interface
17:48 #navit: < basilic_> using as HID interface
17:49 #navit: < rokm> KaZeR: I have two HW buttons and want to bind them to Navit, So my app handles press/release actions and sends input events to uinput with defined by me key. I binded this key in navit.xml for menu button.  So as a result hw button should open navit menu.
17:49 #navit: < basilic_> this: https://www.picclickimg.com/d/l400/pict/153216762039_/04-08-Mazda-RX-8-RX8-GPS-Navigation-Navi-Display.jpg
17:51 #navit: <@KaZeR> rokm: yeah i've done the exact same thing in the past so it should work. Although eventually i moved that code (which was a python script) to a navit plugin : https://github.com/navit-gps/navit/blob/trunk/navit/plugin/j1850/j1850.c
17:52 #navit: < rokm> I will check, thanks
17:52 #navit: < basilic_> KaZeR, how did you connected to the bus?
17:52 #navit: <@KaZeR> this plugins does a little more than waiting for an event now, but here's the gist of it : https://github.com/navit-gps/navit/blob/trunk/navit/plugin/j1850/j1850.c#L207-L209 
17:52 #navit: <@KaZeR> basilic_: using a cheap obd bluetooth adapter
17:52 #navit: < basilic_> oki
17:53 #navit: < basilic_> you never has problem with it?
17:53 #navit: < basilic_> mine never shutdown and after 1 or 2 weeks the batery is empty
17:53 #navit: < basilic_> 1 or 2 weeks without use the car
17:54 #navit: <@KaZeR> well i don't use that car so much and didn't have this issue. That's the one i've been using : https://www.amazon.com/gp/product/B009NPAORC/ 
17:56 #navit: < basilic_> I get a similar
17:56 #navit: < basilic_> but maybe is my car 
17:56 #navit: < basilic_> never cut the power on the OBD
18:00 #navit: < basilic_> how I can get a map for europe?
18:00 #navit: < basilic_> where I can get a map for europe?
18:00 #navit: < rokm>  KaZeR : So it looks like I have to write own plugin which will read /dev/input/eventX and triger gui action?
18:00 #navit: <@KaZeR> basilic http://maps.navit-project.org/
18:01 #navit: <@KaZeR> rokm: my suggestion here was more to replace your app with a plugin, if all your app do is to send the events to uinput
18:01 #navit: < basilic_> what!! 13Gb for the map!
18:01 #navit: <@KaZeR> basilic_: you asked for all EUROPE :)
18:03 #navit: < basilic_> yes but don't need all path I have a car not a tractors
18:05 #navit: < rokm> KaZeR: there is much more in my app. So I would prefer to do this from app to navit directly or via bash sript that I can execute from my app.
18:05 #navit: < basilic_> I will start with france only lol
18:05 #navit: < rokm> is there any other way to do this?
18:06 #navit: < rokm> uinput was first thing which I take into account
18:09 #navit: <@KaZeR> basilic_: you can also download the countries you are intested in and use mutiple maps at the same time. It'll work.
18:10 #navit: < basilic_> I have select my country
18:10 #navit: < basilic_> If a day I need I download other :)
18:10 #navit: < basilic_> and It's with this car I'm not sure to go out of my country
18:10 #navit: <@KaZeR> rokm: i see ok. so let's figure out what's going on. Another way would be dbus also
18:13 #navit: < rokm> KaZeR: Im using SDL So maybe there is a way to inject key via SDL_pushEvent?
18:13 #navit: < rokm> I tried but without luck
18:14 #navit: < rokm> Thi probably could be done in the same binary
18:14 #navit: < rokm> but not in my case
18:15 #navit: <@KaZeR> rokm: well uinput should work anyway so we can focus on that. I've used it so we should be able to figure it out
18:16 #navit: <@KaZeR> basilic_: would you mind updating the osm wiki page for us? Looks like i lost my credentials :(
18:22 #navit: < rokm> KaZeR: So back to my first question on the beggining, /dev/input/event1 notifies button state changes (checked with evtest tool), in navit.xml I extended button according to keybindings (So accesskey= and use_overlay=1)
18:24 #navit: < rokm> I had suspicion that maybe SDL was compiled without some flags
18:26 #navit: < rokm> I found SDL_INPUT_LINUXEV but in all cases Iends up in joystick functionality 
18:27 #navit: < rokm> I also noticed that uinput doesnt start evdev daemon
18:27 #navit: < rokm> which I see when ts is enabled
18:27 #navit: < rokm> so maybe in this direction
18:44 #navit: <@KaZeR> you might be on the right track indeed
18:54 #navit: < rokm> maybe
18:55 #navit: <@KaZeR> you are using the vanilla navit code right?
18:57 #navit: < rokm> Hmmm I think it is 0.5.1
18:59 #navit: <@KaZeR> ok. we haven't changed much regarding sdl since 0.5, i mostly wanted to make sure that you didn't have any custom patches or things like that
19:03 #navit: < rokm>  Is my understanding is OK that event from uinput shoild ends up as SDL event?
19:05 #navit: < rokm> I enabled debug prints in Navit and nothing happens related to button handling
19:07 #navit: < rokm> looks like all ends on /eventX and no one is reading/handling what happens there
19:08 #navit: < rokm> and I even dont know how to trace this on Navit side
19:08 #navit: < rokm> that I asked here ;)
19:36 #navit: <@KaZeR> have to say that i am not too familiar with the sdl code. When i used this i used it with the gtk graphics driver. But we'll figure it out. I'm looking at the code
22:32 -!- xenos1984 [~xenos1984@22-164-191-90.dyn.estpak.ee] has quit [Quit: Leaving.]
--- Log closed Sat Nov 10 00:00:01 2018