Hardware review - scantool.net; OBDlink CI

**jusjake** · 09-07-2009, 11:48 AM

I was recently given the opportunity to complete a review of scantool.nets OBDlink CI by mp3 car.
After having tested The OBDlink CI on multiple makes and models I've found it's limited to vehicles newer than 2004. It does however work very well on all the U.S. Models as well as Honda's and Toyota's. This tool is also very simple to work with, after loading the software and choosing the correct com port I was up and running. It picked up multiple trouble codes and monitored each sensor on the vehicle just as accurately as my $2000 snap on scanner. After trying a couple more things to get the scanner to work on older vehicles and failing I contacted Vitaliy through the scantool.net forum because the new CI can have firmware upgrades made to it. I thought he would have some insight as to how I could set up the CI to work on vehicles like my 2001 Focus, or my fathers 2002 Cadillac DHS. Instead I was delightfully surprised at how personable and helpful he was (customer service is worth more than anything to me these days). Although there was no software or means to get the unit to work on older vehicles hen explained people that purchased the Cl were eligible to get a discount on the new OBDLINK which was coming out soon. We however worked out a deal where I would also get to review the new OBDLINK.

So here's the tool as it comes packaged. Literally everything you need to get started.

So the pluses are; Easy to load software, Easy to hook everything up, works great on vehicles newer than 2004. Easy to read sensor information, DTC's are not only shown but the description is given as well.

Negatives; This unit only works on vehicles newer than 2004.

**Bugbyte** · 09-07-2009, 07:38 PM

That's interesting. The OBDLINK CI that I was asked to test worked great on my 2001 VW Beetle. I wonder why that is?

More info on the OBDLINK software, please! What features does it have? Is there something that sets it apart from other software? Anything better or worse about it? How about some screenshots?

**jusjake** · 09-07-2009, 10:08 PM

It's likely the tool worked on your VW because it is a different OBD protocol than the different vehicles I had at my disposal

The software it comes with is fairly basic. It gives the sensor readings for all generic functions. It does make it easy to read while on the road, there's no clutter but again it won't monitor the "proprietary" information. I also can't monitor anything other than the engine sensors.

There's no gauges or charts but that's all available in the upgraded software. I've also been trying some opensource programs but haven't had any luck yet.

Here's a shot of the base software.

**Bugbyte** · 09-08-2009, 03:26 PM

So, will this work with ELM327 compatible software or is it different?

**jusjake** · 09-09-2009, 10:08 PM

Here it is connected to some elmscan software.

**Vitaliy** · 09-14-2009, 03:09 AM

Just a couple of points:

- OBDLink CI supports ISO9141-2, ISO14230-4 (KWP2000), and ISO15765-4 (CAN). Therefore, it can work on vehicles as old as model year 1994, as long as the vehicle in question uses one of the first two protocols.

- CI doesn't support J1850 VPW or PWM (old GM and Ford OBD protocols), however the new OBDLink supports ALL OBD-II protocols.

- CI and OBDLink are both compatible with the ELM327 command set.

- Jacob, OBDLink has been out for a while now; my apologies for the delay -- please email me your address and we'll send one out to you right away.

Vitaliy

**jusjake** · 09-14-2009, 11:37 AM

Thanks for the info Vitaliy.

I'm all set with the OBDLink, i received it and it's working out great. I have a review I'll be posting up here shortly.

**Bugbyte** · 09-14-2009, 02:46 PM

Originally Posted by Vitaliy

Just a couple of points:

- OBDLink CI supports ISO9141-2, ISO14230-4 (KWP2000), and ISO15765-4 (CAN). Therefore, it can work on vehicles as old as model year 1994, as long as the vehicle in question uses one of the first two protocols.

- CI doesn't support J1850 VPW or PWM (old GM and Ford OBD protocols), however the new OBDLink supports ALL OBD-II protocols.

- CI and OBDLink are both compatible with the ELM327 command set.

- Jacob, OBDLink has been out for a while now; my apologies for the delay -- please email me your address and we'll send one out to you right away.

Vitaliy

That clears it up, thanks. My VW is ISO 9141. I can say that not only did the OBDLINK-CI work on my car without issue, it also worked on my Intel Mac Mini running VMWARE Fusion and the OBDLINK-CI. I have to caution that I only tested it a little bit and it did seem to have a problem waking up from hibernation, but that is probably due to Fusion, not the OBDLINK-CI.

Good product and worked as advertised. I used all of the different test software that came on the install disk and it was able to find the OBCLINK-CI without issue. This included software that was looking for ELM-327 compatible interfaces.