The MP3car.com Store  

Welcome to the MP3Car.com forums.

You are currently viewing our boards as a guest which gives you limited access to view most discussions and access our other features. Registering will also remove advertisements. By joining our free community you will have access to post topics, communicate privately with other members (PM), respond to polls, upload content and access many other special features. Registration is fast, simple and absolutely free so please, join our community today!

If you have any problems with the registration process or your account login, please contact contact us.

Go Back   MP3Car.com > Mp3Car Technical > Engine Management, OBD-II, Engine Diagnostics, etc.

Reply
 
Thread Tools Display Modes
Old 11-27-2007, 01:41 PM   #1
Low Bitrate
 
reece146's Avatar
 
Join Date: Sep 2004
Location: ON, Canada
Vehicle: 2000 Honda S2000, 2001 Jeep Cherokee
Posts: 98
My Photos: (0)
OBD-II connected all the time?

I was talking to a vendor about my project and they stated that their ODB-II cable is not meant for "permanently connecting" a car PC to the OBD-II port.

I can see the point regarding the whole baud change negotiation thing at initial but...

Is the vendor just being overly cautious or is there a type of cable that is meant for permanent connection? Some kind of a buffered assembly that keeps the conversation with the ECU/PCM "clean" for the PC?

I'm working with a Jeep Cherokee (ISO9141-2) and freediag/scantool.

TIA
reece146 is offline   Reply With Quote
Sponsored Links
Old 11-27-2007, 02:49 PM   #2
Newbie
HNaga's CarPC Specs
 
Join Date: Oct 2007
Posts: 50
My Photos: (4)
I don't think the is a problem in keeping it all the time.

Car with trip computer already reqading from ECU all the time.
HNaga is offline   Reply With Quote
Old 11-27-2007, 02:54 PM   #3
Low Bitrate
 
reece146's Avatar
 
Join Date: Sep 2004
Location: ON, Canada
Vehicle: 2000 Honda S2000, 2001 Jeep Cherokee
Posts: 98
My Photos: (0)
Yes, but that is something designed in versus the service port. Trip computers likely bypass the OBD system entirely.

I don't know, just throwing that out there.
reece146 is offline   Reply With Quote
Old 11-27-2007, 02:55 PM   #4
Newbie
HNaga's CarPC Specs
 
Join Date: Oct 2007
Posts: 50
My Photos: (4)
I'm not expert but logically no problem it in
HNaga is offline   Reply With Quote
Old 11-27-2007, 03:40 PM   #5
FLAC
muldrick's CarPC Specs
 
muldrick's Avatar
 
Join Date: Jun 2004
Location: South-Central PA
Vehicle: 2004 Hyundai Accent
Posts: 1,211
My Photos: (2)
Yes, logically, I agree. All you are doing is displaying OBD information, your just receiving info, not pushing it. Mine's been hooked up forever, no problems.
__________________
Now faith is being sure of what we hope for and certain of what we do not see.
muldrick is offline   Reply With Quote
Old 11-27-2007, 04:24 PM   #6
Constant Bitrate
 
joeyoravec's Avatar
 
Join Date: Oct 2005
Location: Livonia, MI
Vehicle: 2003 Mustang GT
Posts: 147
My Photos: (0)
Quote: Originally Posted by reece146 View Post
I was talking to a vendor about my project and they stated that their ODB-II cable is not meant for "permanently connecting" a car PC to the OBD-II port.

It all depends on the quality of the wiring, the interface, the software, and the car. Lousy wiring can act like a giant antenna that injects noise and corruption into the network. Lousy tools will do the same thing, or worse they carry voltage spikes and blow out your PC. Lots of cars are robust, but some cars are so touchy that anything out-of-spec pushes them over the edge.

Other vendors will stand by their equipment for semi-permanant installation, rough conditions, etc. Look around a little more before you settle on a solution.

Quote: Originally Posted by reece146 View Post
I can see the point regarding the whole baud change negotiation thing at initial but...

The ECU should spend its time running the engine and refuse commands or delay responses when its busy. Of course there are a few buggy ECUs as exceptions to the rule (often solved by a flash update!). BUT.... If you both you and the ECU follow the protocol, distance limitations, and electrical specifications then it will work just as well as it was designed to work.

Generic OBD-II has no negotiation and fixed baud rates. You may be thinking of ISO which has an unusual init sequence (a few bytes at 5 baud) and drops out of diagnostic mode with 5 seconds of no activity. Seems overly cautious in hindsight.

Quote: Originally Posted by reece146 View Post
Is the vendor just being overly cautious or is there a type of cable that is meant for permanent connection? Some kind of a buffered assembly that keeps the conversation with the ECU/PCM "clean" for the PC?

He knows his equipment best. If it's a cheapie solution its possible that they cut corners or don't spend the time to formally test and validate things. I really can't argue with somebody who says "don't use my equipment for this"

There are a million ways to break the rules so there's no buffer, filter, or magic fairy dust to stick in the middle and improve the situation. My only thought is to use different equipment and software where the vendor stands by the solution for semi-permanent installation.
joeyoravec is offline   Reply With Quote
Old 11-27-2007, 07:53 PM   #7
Low Bitrate
 
reece146's Avatar
 
Join Date: Sep 2004
Location: ON, Canada
Vehicle: 2000 Honda S2000, 2001 Jeep Cherokee
Posts: 98
My Photos: (0)
Yeah, my setup is ISO9141-2 with the wonky init...

Here's a published listing of what is supported by the software:

http://freediag.sourceforge.net/Supp...html#supported

Maybe the Multiplex Engineering "opto-isolated" interface would be a better choice for permanent mounting? I dunno - just throwing that out there.

Lot of fuss to get the ALSA master volume bumped up higher based upon vehicle speed, eh?
reece146 is offline   Reply With Quote
Old 11-27-2007, 09:26 PM   #8
Constant Bitrate
 
joeyoravec's Avatar
 
Join Date: Oct 2005
Location: Livonia, MI
Vehicle: 2003 Mustang GT
Posts: 147
My Photos: (0)
It is a lot of fuss, but I bet it'll be cool when it's done

Optical isolation is always a good thing so you don't risk blowing out the PC's serial port. If you're going to do any custom programming consider a real PassThru (SAE J2534) interface instead of hobbyist equipment. Other than that it's same as anything else -- go with a real company that you can reach by phone with business hours, not just email or a web store.

Good luck. Post your results! Do you have steering wheel volume controls? It would be cool to tap into those if they're on a network.
joeyoravec is offline   Reply With Quote
Old 11-28-2007, 07:06 PM   #9
Constant Bitrate
 
Join Date: Jul 2004
Posts: 129
My Photos: (2)
I have my OBDII hooked up all the time. No Problems with it.
__________________
2003 Black Impala
Dwaine is offline   Reply With Quote
Old 01-01-2008, 10:29 AM   #10
Newbie
 
RoadThunderS's Avatar
 
Join Date: Nov 2006
Location: Bellusco (Milano) - ITALY
Vehicle: 1993/BMW/E36
Posts: 20
My Photos: (2)
Hi to all. I have a BMW E36 of year 1992. This model have the OBDI protocol not OBDII.
I'd like realized custom software (in visual basic for istance) for reading data from the ECU.
I just have the hardware interface for using the BMW Carsoft Diagnostic Software.
Please, there is someone knows how I can write custom software for this my purpose ?

Many Thanks.
RoadThunderS is offline   Reply With Quote
Sponsored Links
Reply


Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)
 
Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are Off
Pingbacks are Off
Refbacks are Off

Similar Threads
Thread Thread Starter Forum Replies Last Post
OBD II and Citroen Xsara ThePohorc Engine Management, OBD-II, Engine Diagnostics, etc. 9 04-02-2008 08:41 AM
Need help to figure out OBD ii connections virengoyal Engine Management, OBD-II, Engine Diagnostics, etc. 5 12-03-2006 12:14 PM
OBD II software for bmw kostsour Engine Management, OBD-II, Engine Diagnostics, etc. 5 11-05-2006 12:50 PM
98 Nissan Altima OBD II? to carputer??? tsparks Engine Management, OBD-II, Engine Diagnostics, etc. 4 04-30-2006 09:09 AM
Radio and amp connected to speakers at the same time... MattW General Hardware Discussion 11 07-18-2001 09:41 AM


All times are GMT -5. The time now is 11:28 AM.


Sponsored Links
The MP3car.com Store

Powered by vBulletin® Version 3.6.8
Copyright ©2000 - 2008, Jelsoft Enterprises Ltd.
SEO by vBSEO 3.1.0
Copyright © 1999 - 2008 Mp3Car.com Inc.
Ad Management by RedTyger
Message Board Statistics