theshadow27, I have thought about doing this for my current car and I may start it and see where it goes, but its not going to be a small task. Ill see how it goes and if its possible to do on mine, yet alone other cars.
Printable View
theshadow27, I have thought about doing this for my current car and I may start it and see where it goes, but its not going to be a small task. Ill see how it goes and if its possible to do on mine, yet alone other cars.
Cool. Keep us posted. I picked up two of these kits:Quote:
Originally Posted by CityFan86
http://www.microchip.com/stellent/id...t=MCP2515DM-BM
And will play around when they show up. The order has been pushed back until 30-october though :/
FYI, I looked into the CAN project for my car. Looks like it should be pretty simple. I know the hardware I need and will start looking into making one after this current project gets more stable.
The hard part for my car (05 Volvo S40) is that the control module addresses vary between vehicles. It may be a VIN-block thing, or may be randomized, I'm not sure, but there's nowhere that says "Dashboard = 0x3A" which would be very useful.
I've talked to folks who have tried similar things and supposedly the best way to sniff CAN is to hook up and start unplugging things. When that address drops off the trace, plug it back in and filter it out. Eventually you're only left with the thing you're looking for. This sounds like a tremendous PITA though.
What I'd like to do is come up with a method of "searching" for the correct address with the embedded system in it's final form. This may not be possible between different makes, but I'd bet that all Volvo's use the same type of command to put messages on the LCD screen. Other car makers probably do the same. It just doesn't make sense to re-invent the wheel every time you change the background color of the gauge cluster...
The Microchip boards are backordered and will take until the end of October to arrive :(
I think the only way is the PITA way. You could log all the messages and try and look to see if one makes sense. You should in theory be able to see the ASCII characters being transmitted that correlate to the display, so may not be too bad. But yes, all message ids will vary between makes and probably between models. Email me or lets make another thread to discuss.
Sorry, wasn't trying to hijack.Quote:
Originally Posted by CityFan86
http://www.mp3car.com/vbulletin/hard...interface.html
:focus:
Beta-testing of the V1Connect is nearing completion and development of a Centrafuse plugin is underway. I am hoping that the developer of this plugin will announce the features and other information on this plugin in the coming weeks. Some info is available here: http://forums.v1connect.com/smf/index.php?topic=7.0
At this time I have opened up the website to pre-orders. All devices will be shipped out on Monday November 2nd 2009. I only have 15-20 devices remaining. I am beginning to order parts for my next larger batch of 50 devices, but this depends on how fast these current ones sell out. Any questions please email me.
Email: sales@v1connect.com.
Order: http://www.v1connect.com/Purchase.aspx
FYI Centrafuse Plugin is under development: http://forums.fluxmedia.net/plugin-d...html#post55948
It'd be cool to get a *nix library or daemon going for the V1. There are a lot of Linux and Mac users who would love it. Any documentation on the interface protocol?
Yes it would be awesome to have *nix support. That is why the protocol is openly documented and the hardware should have no issues what so ever working with a *nix machine.
Protocol Info: http://www.v1connect.com/Protocol.aspx
Any questions just ask.