--- Log opened Wed Sep 23 00:00:18 2015
01:31 -!- jawood [79d920ea@gateway/web/freenode/ip.121.217.32.234] has joined #navit
02:39 -!- jjelen [jjelen@nat/redhat/x-lnjxgnsbocudjuns] has joined #navit
02:47 -!- Robotaxi [3ef5dbf5@gateway/web/freenode/ip.62.245.219.245] has joined #navit
03:44 #navit: < RobertP> Hi all
04:41 -!- KaZeR [~KaZeR@c-67-161-64-186.hsd1.ca.comcast.net] has quit [Ping timeout: 268 seconds]
04:50 -!- jonathanmaw [~jonathanm@82-70-136-246.dsl.in-addr.zen.co.uk] has joined #navit
05:37 -!- KaZeR [~KaZeR@c-67-161-64-186.hsd1.ca.comcast.net] has joined #navit
05:53 -!- KaZeR [~KaZeR@c-67-161-64-186.hsd1.ca.comcast.net] has quit [Ping timeout: 260 seconds]
06:07 -!- RobertP [bc5c2133@gateway/web/freenode/ip.188.92.33.51] has quit []
06:21 -!- KaZeR [~KaZeR@c-67-161-64-186.hsd1.ca.comcast.net] has joined #navit
07:37 -!- tg [~x@unaffiliated/tg] has quit [Ping timeout: 256 seconds]
07:41 -!- tg [~x@unaffiliated/tg] has joined #navit
07:56 -!- pini [~pini@bou-fi.pustule.org] has joined #navit
09:57 -!- RobertP [5cd9e500@gateway/web/freenode/ip.92.217.229.0] has joined #navit
09:57 #navit: < RobertP> Hi all
11:04 -!- RobertP [5cd9e500@gateway/web/freenode/ip.92.217.229.0] has quit [Ping timeout: 246 seconds]
11:56 -!- jjelen [jjelen@nat/redhat/x-lnjxgnsbocudjuns] has quit [Ping timeout: 246 seconds]
11:58 -!- jonathanmaw [~jonathanm@82-70-136-246.dsl.in-addr.zen.co.uk] has quit [Quit: Ex-Chat]
12:00 -!- Robotaxi [3ef5dbf5@gateway/web/freenode/ip.62.245.219.245] has quit [Ping timeout: 246 seconds]
12:07 -!- RobertP [5cd9e500@gateway/web/freenode/ip.92.217.229.0] has joined #navit
12:50 -!- jandegr [5bb55716@gateway/web/freenode/ip.91.181.87.22] has joined #navit
12:51 -!- xenos1984 [~xenos1984@55-10-196-88.dyn.estpak.ee] has joined #navit
13:09 -!- jandegr [5bb55716@gateway/web/freenode/ip.91.181.87.22] has quit [Quit: Page closed]
13:28 #navit: < KaZeR> hi there
13:32 #navit: < RobertP> Hi
13:44 #navit: < KaZeR> yeah it looks great. i also love the idea that almost no cables are required. For a carputer that's great. in my current setup for example i have a bulky hdmi cable + a power cable that waste a lot of space.
13:46 -!- jandegr [5bb55716@gateway/web/freenode/ip.91.181.87.22] has joined #navit
13:55 #navit: < RobertP> is it possible to drive multiple displays with the 7" and additional a HDMI/Composite display? That would pay the bill. :D
13:57 #navit: < KaZeR> i believe that it should yes. i've already used spi + hdmi. since this new screen is on the DSI port i think it should work. i will confirm asap :)
14:02 #navit: < RobertP> this display would fit as a second monitor at the back of my seat, so that the kids can watch a movie on long trips.
14:02 -!- RobertP [5cd9e500@gateway/web/freenode/ip.92.217.229.0] has quit [Quit: i'm afk for a while]
14:06 #navit: < KaZeR> you would have to relocate the pi tho, as i don't expect DSI to be able to route signal on a long distance
14:36 -!- gernot_ [5496956c@gateway/web/freenode/ip.84.150.149.108] has joined #navit
14:36 #navit: < gernot_> hi
14:37 #navit: < gernot_> KaZeR: tried you omxplayer on 7" display?
14:38 #navit: < KaZeR> not yet. but i have it running on some 40" displays at work ( dashboards )
14:38 #navit: < KaZeR> i haven't even plugged the display to my pi yet, did not have time :)
14:38 #navit: < KaZeR> i meant :(
14:38 #navit: < gernot_> KaZeR: i'm not sure DSI has its own framebuffer
14:39 #navit: < gernot_> ok
14:39 #navit: < KaZeR> good point. i will try and report :)
15:48 -!- tryagain [~quassel@178.216.76.157] has joined #navit
15:48 -!- jandegr [5bb55716@gateway/web/freenode/ip.91.181.87.22] has quit [Quit: Page closed]
15:49 -!- gernot_ [5496956c@gateway/web/freenode/ip.84.150.149.108] has quit []
17:16 -!- circleci-bot [~circleci-@ec2-54-197-103-170.compute-1.amazonaws.com] has joined #navit
17:16 #navit: < circleci-bot> Success: sleske's build (#624; push) in navit-gps/navit (trunk) -- https://circleci.com/gh/navit-gps/navit/624
17:16 -!- circleci-bot [~circleci-@ec2-54-197-103-170.compute-1.amazonaws.com] has quit [Client Quit]
17:28 -!- circleci-bot [~circleci-@ec2-54-90-199-106.compute-1.amazonaws.com] has joined #navit
17:28 #navit: < circleci-bot> Success: pgrandin's build (#625; push) in navit-gps/navit (master) -- https://circleci.com/gh/navit-gps/navit/625
17:28 -!- circleci-bot [~circleci-@ec2-54-90-199-106.compute-1.amazonaws.com] has quit [Client Quit]
18:13 -!- tryagain [~quassel@178.216.76.157] has quit [Remote host closed the connection]
18:37 -!- pini [~pini@bou-fi.pustule.org] has quit [Ping timeout: 260 seconds]
18:41 -!- xenos1984 [~xenos1984@55-10-196-88.dyn.estpak.ee] has quit [Quit: Leaving.]
20:21 #navit: < jawood> Hi Kazer just wondering if you have some time this morning?
20:21 #navit: < KaZeR> yep give me 15 minutes
20:28 #navit: < jawood> no probs thanks
21:17 #navit: < KaZeR> oh wow that wasn't 15 minutes :)
21:17 #navit: < KaZeR> i suck at estimating time :)
21:18 #navit: < KaZeR> i'm still doing smth else at the same time but should be able to help now
21:20 #navit: < jawood> no worries i just have two questions one is about the display it goes into night mode no problems every night but it wont switch back to day mode in the morning
21:24 #navit: < jawood> the other thing is to do with that pesky USB OBDII serial device killing the GPS I have posted for help on the Pi forums but no one has responded with a solution, was hoping you might have some ideas on why. I even plugged the Pi into a different power supply to the the touch screen and USB OBDII device and still get the same problem so defiantly not a power issue
21:34 #navit: < KaZeR> ok. i'll have to check the wiki for your day/night issue. i know that you can define a night layout from a layout, need to check if we should cross-define the day layout from the night layout
21:35 #navit: < KaZeR> maybe you are the very first user of navit who drove all night long and found a new bug / missing feature :)
21:35 #navit: < KaZeR> for your obd2 device : reboot, ensure that gps is working. then let's tail the system log, and plug the obd device
21:39 #navit: < jawood> i have just had the unit sitting on my desk running for the past few days and have noticed that if i start it in the day it switches to night mode ok but when i get up in the morning its still in night mode and stays there unless i exit navit reboot and restart navit then its in day mode again
21:40 #navit: < jawood> the gps is connected and running with a 3d fix when i connect the USB OBDII it keeps working as soon as i reboot the gps no longer works
21:49 #navit: < KaZeR> for the layout i'll check the config. for the gps then i completely misunderstood your issue :)
21:50 #navit: < jawood> cheers i have had a look thru the configuration section on the wiki but couldnt find anything on the auto night mode switching.
21:51 #navit: < jawood> Everything works fine as a GPS navigation i even got voice prompts working
21:52 #navit: < KaZeR> nice :)
21:52 #navit: < jawood> just when i connect the usb obdii device and reboot i no longer get signal from the gps - the gps is connected to the gpio pins on the pi
21:52 #navit: < KaZeR> ok. what port is your gps using? ttyACMA something?
21:53 #navit: < jawood> g
21:53 #navit: < jawood> gps on ttyAMA0
21:59 #navit: < KaZeR> ok. and then your obd2 device gets a ttyUSB0 right? not a ttyAMA1 ?
22:00 #navit: < jawood> yes i think so
22:16 #navit: < KaZeR> mmm
22:16 #navit: < KaZeR> after a reboot, do you see a ttyUSB* ?
22:16 #navit: < KaZeR> after a reboot with the obdii device plugged i mean
22:17 #navit: < jawood> how to i list the tty devices i tried /dev/tty* but that dosent work
22:18 #navit: < KaZeR> ls /dev/tty*
22:18 #navit: < jawood> got /dev/ttyUSB0
22:19 #navit: < jawood> and i can see the /dev/ttyAMA0 is listed still but getting no signal from it with cgps -s
22:21 #navit: < KaZeR> mmm
22:22 #navit: < KaZeR> no signal as in no fix, or as in gpsd not being able to communicate with the device?
22:22 #navit: < jawood> my thoughts exactly I have been google searching it for a week now and the only thing i could find was a power issue which i have eliminated as the cause
22:22 #navit: < jawood> cant communicate with the gps at all
22:23 #navit: < jawood> get gps timeout when run the cgps -s
22:27 #navit: < KaZeR> mmm. i remember having a similar issue with my adafruit gps
22:27 #navit: < KaZeR> but i don't remember what i did to fix it :)
22:28 #navit: < KaZeR> how do you start gpsd ?
22:28 #navit: < jawood> which is basically what im using same interface anyway
22:28 #navit: < jawood> did this dpkg-rconfigure gpsd
22:30 #navit: < jawood> Adding Support for UART Serial GPS connect VCC to pin 1, RX to pin 8 TX to pin 10 and Ground to pin 6 on GPIO for Pi2 Do sudo apt-get install gpsd gpsd-clients python-gps Then sudo gpsd /dev/ttyAMA0 -F /var/run/gpsd.sock test with cpgs -s to autostart gpsd type sudo dpkg-rconfigure gpsd select yes add /dev/ttyAMA0 defaults for everything else.
22:32 #navit: < KaZeR> ok. i will have to try again using my pi. i *think* that the issue in my case was too much delay to get a fix
22:32 #navit: < KaZeR> there's a flag in gpsd to have it query the device even without clients. you issue is maybe that cgps times out before you are able to get a fix
22:32 #navit: < KaZeR> and when cgps exits, gpsd stops polling the device
22:33 #navit: < KaZeR> you can try two approaches to confirm that : configure gpsd to poll even if there is no clients connected, or run "gpspipe -r" which will continuously poll the daemon
22:33 #navit: < KaZeR> ah, the gpsd flag is -n
22:34 #navit: < KaZeR> Don't wait for a client to connect before polling whatever GPS is associated with it. Some RS232 GPSes wait in a standby mode (drawing less power) when the host machine is not asserting DTR, and some cellphone and handheld embedded GPSes have similar behaviors. Accordingly, waiting for a watch request to open the device may save battery power. (This capability is rare in consumer-grade devices).
22:34 #navit: < KaZeR> i will have to go afk soon but i'll be back in 2 or 3 hours
22:35 #navit: < jawood> ok so i need to set the gps to not go into low power mode?
22:36 #navit: < KaZeR> that's my guess. is navit running when you have this issue?
22:36 #navit: < jawood> thats fine i have to go shortly myself, if you can have a think about it and hopefully find a solution would be awesome
22:36 #navit: < jawood> no
22:37 #navit: < jawood> if i open navit i get no fix
22:37 #navit: < jawood> i have left navit open for some time over 5mins and still no gps fix
22:38 #navit: < KaZeR> ok. gpspipe should be able to give us some hints. but having navit running should prevent gpsd from closing the device.
22:38 #navit: < KaZeR> -n is worth testing
22:39 #navit: < jawood> how do i do that?
22:41 #navit: < jawood> when i do gpspip -r i get a heap of stuff but i think the important bit is class:DEVICE, path /dev/ttyUSB0
22:43 #navit: < jawood> i run the gpspipe -r while navit is running
22:46 #navit: < jawood> im assuming you mean that when i start gpsd with sudo gpsd /dev/ttyAMAo -F i should put gpsd -n //dev/ttyAMA0 -F
23:01 #navit: < jawood> just fyi if i disconnect obdii device reboot and run that gpspipe -r it works and selects the ttyAMA0 unlike when the obdii device is connected it selects /dev/ttyUSB0 so i guess thats where the problem lies just need to work out how to fix that!
--- Log closed Thu Sep 24 00:00:20 2015