where is the OBDII port?
Banned
Joined: Feb 2008
Posts: 0
Likes: 118
These are the specs:
• Automatic or manual selection of OBD II protocol
• High speed automatic protocol scan (between 0.1 to 2.6 s per protocol)
• Quick software boot sequence (ready to go after just one second after switch on)
• Read and display important vehicle information (depending on the vehicle)
• Real-time sensor readings (selectable)
• Vehicle chassis number display (if supported by the vehicle manufacturer)
• Readout and display of the trouble code memory
• Read out and display of Freeze-Frame data
• Erasure of trouble code memory (can cost 100’s of dollars if done by a shop)
• Language selection (English or German, other languages will come soon)
• 580 trouble codes with description in running text
• All existing OBD protocols for private vehicles are supported:
o ISO9141-2
o ISO14230-4 (KWP2000)
o J1850 PWM
o J1850 VPWM
o ISO15765-4 (CAN, 11/29 Bit, 250/500 kbits/s)
• Power for the analyzer is supplied from the vehicle’s OBD-2 connector (12 V)
• Backlit 3-line LC display with adjustable contrast
• Acoustic signal gives audible feedback and beeps when trouble codes recognized
• LED Indicators for connection status and data traffic flow
• Simple operation using just two push buttons
• Connection for a standard OBD-2 cable
• Handheld format: 80x135x30 mm (W x H x D), weight 150 g (approx.)
• High speed automatic protocol scan (between 0.1 to 2.6 s per protocol)
• Quick software boot sequence (ready to go after just one second after switch on)
• Read and display important vehicle information (depending on the vehicle)
• Real-time sensor readings (selectable)
• Vehicle chassis number display (if supported by the vehicle manufacturer)
• Readout and display of the trouble code memory
• Read out and display of Freeze-Frame data
• Erasure of trouble code memory (can cost 100’s of dollars if done by a shop)
• Language selection (English or German, other languages will come soon)
• 580 trouble codes with description in running text
• All existing OBD protocols for private vehicles are supported:
o ISO9141-2
o ISO14230-4 (KWP2000)
o J1850 PWM
o J1850 VPWM
o ISO15765-4 (CAN, 11/29 Bit, 250/500 kbits/s)
• Power for the analyzer is supplied from the vehicle’s OBD-2 connector (12 V)
• Backlit 3-line LC display with adjustable contrast
• Acoustic signal gives audible feedback and beeps when trouble codes recognized
• LED Indicators for connection status and data traffic flow
• Simple operation using just two push buttons
• Connection for a standard OBD-2 cable
• Handheld format: 80x135x30 mm (W x H x D), weight 150 g (approx.)
Thread Starter
Member
Joined: Nov 2009
Posts: 149
Likes: 1
From: austin, texas, usa
2006 e320 cdi
Thank you for the offer! I understand the convenient factor in a hand held device, but I imagine a PC reader would be more flexible in terms of upgrading software, even choice of software packages. So, I'm leaning towards a PC config. Thanks!
Member
Joined: Nov 2009
Posts: 91
Likes: 1
From: Auckland New Zealand
E500 2002. Supra TT 97, Supra NA-T 94, Glanza 96, Starlet 90
Please let us or atleast me know what you work out to be the best
I am also looking to get ahold of something, sick of paying 100 bucks just to read the damm codes !
