Specifications for Alpine's M-BUS Protocol?
An Anonymous Coward asks: "Like every geek on the planet, I have attempted to create a slick, well integrated MP3 player for my car. I have the unit in place, a biscuit pc running of a dc power supply that is ACC line aware, wireless 802.11 to download music from my home server when parked in the driveway, and it sends its sound signal to the receiver via the Alpine cd changer connector in my car. What I have looked for religiously is the specification for the Alpine M-BUS protocol so I can cleanly integrate it with my in-dash Alpine receiver. I see lots of questions but no answers when I search the web and newsgroups. Any one out there reverse engineered this spec? I just want to know before I go try to reverse engineer it myself." I've gotta admit, the 802.11 extension is a new twist on the traditional car MP3 player! Pretty slick, that. Are there any projects currently in the works to reverse engineer the M-BUS protocol, or will our anonymous friend here need to start this off on his own?
I've been keeping an eye on these guys for a while, after searching for a spec for the Sony changer protocol, for similar reasons.
They currently have a changer box that will talk to Kenwood head units, and takes hard-disk cartridges. They claim to have have compatibility for other brands (Sony, Alpine etc) in the works.
Nice looking kit, too.
"don't fall into the fallacy of believing that Perl can solve social problems. Maybe Perl 6 can, but that's a ways off"
*snip*
...
...
...
wireless 802.11 to download music from my home server when parked in the driveway
...
*snip*
I've gotta admit, the 802.11 extension is a new twist on the traditional car MP3 player!
*snip*
Does this mean that when going on long trips (and even around town, I guess), you could download/trade songs from neighboring vehicles? Napster-on-the-go, anyone?
Seriously though, how could we implement something like this? I'm trying to figure out how this would work, using my Linux background as a basis for information. Since there really wouldn't/couldn't be a centralized server, it would be up to the individual vehicles to negotiate connections with each other. I guess some sort of daemon performing a multicast broadcast to announce availability every few seconds would be needed to share the files, and then a client listening for those broadcasts and handling the connection for those wishing to search for and download files. Of course, some type of MD5SUM or something would have to be generated for each file to do integrity checking, and the thought of using something like rsync just popped into my head. I think I like that idea better. I'm actually surprised more of these file sharing programs don't use rsync, a well-established download-and-resume-incomplete-files protocol (or do they, and I just don't know?). Considering you'll be going in and out of range of vehicles quickly and frequently, I think resume is important, especially with an MD5SUM system, so you can resume the same file from a different vehicle.
Once that's in place, I guess you need to think about the interface.. not really too easy to do on an in-dash system (especially while driving!). That is one of the bigger headaches.
Okay, here's a plan.. someone feel like developing it? Let me know if you do.
Oh, by the way, if you decide to use this idea, it better be an open protocol/standard/codec and open sourced, or I'll come after you. I'm tired of proprietary junk.
Don Head
UNIX/Linux Administrator
just think. if you integrated a decent text to speech system, you could have the car tell you "dave, i'm sorry, i cant snort that WEP key if you drive this fast"
or...
"well here's another unsecured network! oh look! he's surfing goatse.cx !"
or...
"well we now have his passport account information, shall we go buy me a new set of tires?"
We want to see what you built! Post the specs, and some pictures, damnit!
...contacting Alpine?
I know it sounds stupid, but it couldn't hurt - since you have already come so far, explain it to them, and what you want to do - hell, they may want to help you for promotional reasons (you may want to mention this to them). Or, you may have to buy the spec (which may be cheap - or could be INSANELY expensive).
If they flat out won't help, then you have lost nothing. Go ahead and RE it...
I can't imagine that they won't help in some way - why create the interface and publicize it, if it is proprietary and only used by them anyway? I would think they have created it to allow third party manufacturers to interface to it (maybe find who those manufacturers are, and contact them as well).
Reason is the Path to God - Anon
This guy has pinouts and protocols for Kenwood, Panasonic and Pioneed changers. Might give you some ideas.
m
http://www-user.tu-chemnitz.de/~harn/mp3_cdc.ht
Mark
Check the mp3car webboard.
www.mp3car.com
and click the link at the bottom. Tell them lstrunk sent you. Make sure to use the search button first before asking a new question though.
One thing I always wanted to do with my future car mp3 player is to have 802.11 sync up mp3s with other cars on the road. You should design an open protocol for sharing mp3s between your house and car that would also adapt to the open road.
Sure it'll be useless in the near future, but could be usefull later on.
I parked next to a denny's on senior night, and now my hard drive is full of Harry Belafonte, Frank Sinatra, and Sammy Davis Jr. songs. Maybe this 802.11b sharing thing isn't such a great idea... Well, serves them right! They're probably starting up their El Dorados right now and are shocked to hear old punk covers of 80's tunes.