Where does this wire go?

I don’t know how interesting it will be to people. But I think it looks pretty cool. I still have to clean up the install as you can see. But overall I think it looks okay.

carpc

I got the music working. And I’m making progress with the gps and elmscaner. Instead of nghost reporting plugin not loaded I now get -1 for the data at the ncarinfo screen, and gps shows some bogus data as well.

It might have to do with the d-bus error messages that are spewing in the shell.

Also for some reason the touch screen isn’t responsive. But sometimes it works normally. I’m thinking it is because there is some process hogging resources and when it is done the touchscreen works fine. This is only a guess though.

I added some udev rules to have the gps and elmscan have a permanent device. I set them up as gps0 and elm0.

It turns out the chip in the elmscan is also used in some gps’s So I justed edited the line in my gps udev rule to make it be elm0. My system was creating a gps0 and gps1 previously.

Today I worked with the guys at openice.org and we found that the elmscan seems to be communicating with the carputer. For some reason though nghost doesn’t think the plugin for it is installed.

I got KDM autoloading and autologing in. And the mouse works fine when I do that.

I’m thinking I have to do something with the udev rules to make sure the elmscan and gps receiver are given unique names so I can always count on a specific name for each. Right now each can turn up as either ttyUSB0 or ttyUSB1 and I have no way of knowing which device is which.