You are currently viewing our community as a guest, which gives you limited access to view most discussions and access our other features. By joining our Member Supported community you will have access to post topics, communicate privately with other members (PM), respond to polls, upload photos, 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 us.
Engine & DrivetrainDiscussions about the engine and drivetrain of your vehicle.
This is a discussion thread titled "(OBDII) Computer Interface, anyone tried it?", within the Engine & Drivetrain forum, part of the Technical & Vehicle Assistance Forums category.
Has anyone hooked up a laptop to their Tundra to retrieve the OBDII scan codes?
I'm looking at a piece of hardware (BR-2 that costs $85.00 (software for Windows and DOS is free and included) to run on an old laptop. The BR-2 hooks the serial port of a computer to the OBDII port on any OBDII (post 1996) vehicle. Has anyone tried something like this?
BTW here's an email exchange between me and the BR-2 manufacturer:
From: B. Roadman <bvrd@usa.net>
To: "David"
Date: 02/28/2003 12:41:49 PM
Subject: Re: [BR-2 (OBDII) Interface (completed unit) question]
Hi, David;
By "codes", I assume you mean diagnostic trouble codes (DTC). If so, it will
retrieve any powertrain dtc that the vehicle sends. These are of the form
Pxxxx. DTCs up to P1000 are generic, that is, they are defined by SAE for
general use. DTCs from P1000 up are defined by manufacturers. There is a
pretty long list of both types of dtcs in the windows help function, but if
you retrieve one that isn't there, usually it can be found with a quick net
search or in a repair manual.
It WILL NOT retrieve other types of dtcs, such as B, C, and U codes which are
related to body, chassis, etc. So it won't be usefull for things like ABS
brakes, ride control or restraint systems. Only usefull for powertrain dtcs.
"David" wrote:
> B
>
> I have a 2002 Toyota Tundra SR-5, is there a way to find out what kind
> of codes your product will pull for this specific vehicle? If you
> aren't familiar with the Tundra do you know anyone who may have tried
> it?
>
> Thank you!
>
> David
Well I ordered the BR-3 (OBDII) Interface (completed unit) for PWM, VPW, ISO9141 unit from http://obddiagnostics.com/order.html today. I'll let everyone know what I think when I get it.
I haven't had my check engine light on yet, but my gf's F-250 Superduty's light is on
Originally posted by davidk Well I ordered the BR-3 (OBDII) Interface (completed unit) for PWM, VPW, ISO9141 unit from http://obddiagnostics.com/order.html today. I'll let everyone know what I think when I get it.
I haven't had my check engine light on yet, but my gf's F-250 Superduty's light is on
Dave
The BR-3 is nice because it supports ALL of the standard communication protocols [VPW (General Motors), PWM (Ford), and ISO9141 (Chrysler, Asian, and European), all data defined by SAE J1979] so one single device which costs $85 will work on all cars. Most companies make you purchase a separate piece of hardware for each standard.
It also has software for DOS (nice for old laptops) and Windows.
Originally posted by davidk The BR-3 is nice because it supports ALL of the standard communication protocols [VPW (General Motors), PWM (Ford), and ISO9141 (Chrysler, Asian, and European), all data defined by SAE J1979] so one single device which costs $85 will work on all cars. Most companies make you purchase a separate piece of hardware for each standard.
It also has software for DOS (nice for old laptops) and Windows.
Can't wait to get it and try it first hand!
So David, how well did the BR-3 work for your Tundra? The price seems right...are you happy with it?
Thanks!
Jim.
__________________ Base: '02 Tundra SR5 Imperial Jade Mica 4WD w/ TRD Off-Road, EVP Convenience & Tow Packages, Oak Interior & Captains Chairs, 6 Speaker/6-Disk CD, VIP 3K, Chrome Wheel Locks, & Anti-lock Brakes with DRL Mods: K&N FIPK II, Ram Air Performance System (RAPS), Unichip, Ivan Stewart Flares and TRD Grille, 2" Cornfed Front Suspension Lift (How-To Guide), BFG A/T 265/75's, Hellwig Rear Anti-Sway Bar (How-To Guide), JBA Headers & 2" Highflow Y-Pipe, 2.5" Exhaust Cutout with QuickTime Performance Electric Cutout (QTEC), Flowmaster 50 Series™ Delta Flow® Performance Muffler with Dual 2.5" x 18" Chrome Tips, ASP Racing Underdrive Pulley, PPD Billet Goodies, Rhino Liner, Tinted-windows, etc. Planned: My Tundra is done for now. Next up: Build new 400ci for my '69 Pontiac Custom S
Several months ago I purchased an ISO OBD-II scanner (~$100) from www.ScanTool.net. I wanted to be prepared to troubleshoot, due to the many oxygen sensor failures reported on TS. Today my check engine light came on and I finally tried the product. I’m very pleased; it couldn’t have been easier to use.
1. Connected from the vehicle plug to the ScanTool & from ScanTool to laptop.
2. Ran the ScanTool executable file in Windows.
3. ScanTool immediately began trying to communicate with the vehicle.
4. Started the engine and the ScanTool began displaying realtime data.
Besides all the usual parameters (speed, temp, RPM, MAF, timing advance, etc.), the software displays a couple parameters from each of the four oxygen sensors, so theoretically if you have a bad sensor, you’ll be able to not only see the DTC, but also observe the reading or lack thereof, from the sensor. My code turned out not to be sensor related, so this is still just my theory.
The ScanTool software is extremely simple and easy to use (and allows you to turn off the check engine light, clearing your computer log). Not as comprehensive as some other products, but the interface can’t be beat. VERY intuitive; there are no instructions and none are needed. There are plans to release v2.0 in the next few months, so it could get even better; then again, it’s a one-man outfit, so v2.0 could be vaporware. For now, the software lacks freeze-frame data (to display engine parameters your vehicle records at the time an event is logged), which is the only thing on my wish list. The ScanTool web site is easy to navigate and includes a user forum, to observe actual user/vendor Q&A (always a good sign, IMO).
I would strongly recommend this product for its ease of use, simplicity and low cost (also available in kit form for even lower cost, if you’re handy with a soldering iron).
Originally posted by tremo So David, how well did the BR-3 work for your Tundra? The price seems right...are you happy with it?
Thanks!
Jim.
Works great, haven't had any check engine light yet on my Tundra. Helped me diagnose my friend's F-250 P.O.S though
It's a simple hand-made box, but it's inexpensive and works on GM, Ford, Chrysler, Toyota, etc. Most only work on one type of system and require you to buy additional hardware for each protocol.
Also it has software for Windows and DOS, so I use an old laptop with DOS for convenience.
TundraSolutions.com is a registered trademark of Tundra Solutions, Inc.
Other trademarks and brands are the property of their respective owners. Use of this Web site constitutes acceptance of the TundraSolutions.com User Agreement and Privacy Policy.