Thread: [insert name of project] worklog

What kind of 3G model are you using? i looked into this but couldn't find any that were Linux compatible. Only other idea i had was to tether a cellphone. Next you need to work and remote car functions; lock unlock the doors.

Great work btw.

Originally Posted by smp4488

What kind of 3G model are you using? i looked into this but couldn't find any that were Linux compatible. Only other idea i had was to tether a cellphone. Next you need to work and remote car functions; lock unlock the doors.

Great work btw.

http://www.mp3car.com/vbulletin/work...ml#post1398549

With that, all I need is working wifi.

cheers.

Im liking the sound of this project, curious what you have done with MeeGo and any info you have on that. Looking to put that on my current system but would like to get some feedback on it.

Also, if you could give more details about how you are handling the bluetooth lock and unlock of the care that would be great, its a feature I would like to add to my car

Originally Posted by NightJumper

Im liking the sound of this project, curious what you have done with MeeGo and any info you have on that. Looking to put that on my current system but would like to get some feedback on it.

Also, if you could give more details about how you are handling the bluetooth lock and unlock of the care that would be great, its a feature I would like to add to my car

There's some good work being done on meego with regard to how it runs on the beagleboard and igepv2 boards. Creating meego images requires some Linux knowledge but it's not too tough. It runs pretty good on the igepv2. I'm in the process of creating a new image that should have some more ARM optimizations which should help performance as well. It also uses the meego kernel sources so hopefully that will resolve some of my issues that i'm having with usb using my own kernel...

I'm handling the bluetooth lock+unlock using a combination of proximity and nobdy and a custom app I wrote. Proximity will fire a notification when my cell phone enters within bluetooth range of the car (up to 300 feet away) and I could have it just tell nobdy, the software interface to the can bus network, to lock or unlock the car. However, I wanted a bit more control so I wrote a custom app called "bluemonkey" that sits in between proximity and nobdy do give me more control of how it works. Right now I have it so there is a slight delay between the bluetooth device being detected and when the starting and unlocking happens. That way it'll be less error prone if I'm just walking by the car to get the mail or something. Of course, all this behavior will require lots of real life testing which I'm working hard to get everything working in a condition that I can put it in the car and do long-term testing and tweaking.

Ok i see how that works, now is there a way to make something like that work with a system that isnt on 24/7 as my current system drains to much power to be on constantly. Also what exactly is Nobdy. Ive searched around and seen you talk about it several times but cant seem to figure it out

Originally Posted by NightJumper

Ok i see how that works, now is there a way to make something like that work with a system that isnt on 24/7 as my current system drains to much power to be on constantly. Also what exactly is Nobdy. Ive searched around and seen you talk about it several times but cant seem to figure it out

It's more difficult to do with a power sucking system, but not impossible. one thing you can do is what bugbyte and paulf are doing which is a hybrid approach. They use something like the sheevaplug or igepv2 to do the always-on stuff in addition to the normal, more traditional carpc.

Nobdy is a system daemon that provides an application interface to the vehicle. It provides access to obd-ii and optionally to the can bus. It has a high-level interface for doing things like locking doors and stuff. It supports GM vehicles the best right now but hopefully, interest will eventually rise and more people will add support for their vehicles.

In more simple terms, it allows you to talk to your car in a more consistent/standard way. Here's the wiki page on it: http://wiki.openice.org/index.php?title=Nobdy

Although not really in the scope of this project but one can program a remote starter to fire the engine when your voltage gets below 12 volts and let it run for 15 minutes. PC Will run for weeks..

Provided the vehicle has a full tank

Anyway just checking in, I still have not acquired a MoBo for my bybyte build yet. I've been trying to get a hold of a Via NX15000

Originally Posted by blk02si

Although not really in the scope of this project but one can program a remote starter to fire the engine when your voltage gets below 12 volts and let it run for 15 minutes. PC Will run for weeks..

Provided the vehicle has a full tank

Anyway just checking in, I still have not acquired a MoBo for my bybyte build yet. I've been trying to get a hold of a Via NX15000

amd showed off a nano-itx board at ces running their new low power chip. it may be worth waiting a bit longer for.

I still think that any decently powered board (one that keeps up with the demand of multi-zone etc.) will not be low-power enough to keep on 24-7.

I know TripZero's project with the igepv2 looks quite promising. But would it handle more than the basic 1 zone, keep-the-driver-happy scenario?

As a supervisor piece, that would wake up the main computer is, IMHO, a great idea. I hope to use an Arduino Nano (can be tucked away just about anywhere) and try to set it up for some functions, and perhaps because of threads like this, make it a supervisory circuit of sort that could also trigger the remote starter to fire up if necessary. I just need to dig into the remote box to figure out what on-board trace would do that, or use a spare remote. Hmmmm.....

I love these forums.

John