MP3Car.com - View Single Post

NSFW · 07-04-2008, 01:52 AM

Quote: Originally Posted by Mork0075

Thanks a lot for your reply

My concern is, that i'am doing something wrong, sending wrong bytes through the channel, which causes a damage. I've done some socket programming in Java, which is really close to what you've described (sending some bytes, waiting for the answer, adjusting the program). But writing your own test environement makes a lot of assumptions, which are perhaps wrong. So a pre build car emulator would give me the confidence, to not damage my car.

I wouldn't worry about damaging the car. If you send the wrong series of bytes, the car is most likely to just ignore the data. Especially if you stick to just the read side of the protocol - where you send packets that mean "what is the value in register X?" with a response from car like "register X contains value Y." If you just implement that stuff you're very unlikely to cause any trouble. When you're confident that you have that stuff working, and working well, then ask yourself if you're ready to tackle writes. If you are, you are. If you aren't, then find some more cool stuff to do with reads. There's plenty of opportunity there.

Frankly I wouldn't bother even trying to do writes. Mostly the software I use just reads data to display it or log it, and that's enough for me. I do use one piece of software to write (for tuning), and it makes me nervous every time I run it.

07-04-2008, 01:52 AM	#14
NSFW Constant Bitrate Join Date: Nov 2007 Posts: 112	Quote: Originally Posted by Mork0075 Thanks a lot for your reply My concern is, that i'am doing something wrong, sending wrong bytes through the channel, which causes a damage. I've done some socket programming in Java, which is really close to what you've described (sending some bytes, waiting for the answer, adjusting the program). But writing your own test environement makes a lot of assumptions, which are perhaps wrong. So a pre build car emulator would give me the confidence, to not damage my car. I wouldn't worry about damaging the car. If you send the wrong series of bytes, the car is most likely to just ignore the data. Especially if you stick to just the read side of the protocol - where you send packets that mean "what is the value in register X?" with a response from car like "register X contains value Y." If you just implement that stuff you're very unlikely to cause any trouble. When you're confident that you have that stuff working, and working well, then ask yourself if you're ready to tackle writes. If you are, you are. If you aren't, then find some more cool stuff to do with reads. There's plenty of opportunity there. Frankly I wouldn't bother even trying to do writes. Mostly the software I use just reads data to display it or log it, and that's enough for me. I do use one piece of software to write (for tuning), and it makes me nervous every time I run it.