Tech 2 Purchase

[George B]

It is your phrase "first connecting" that I was trying to pin down.

When you power up the Tech 2, there is no "connection" by which I mean that there has been zero communications between the Tech 2 and anything in the truck. If you select say Diagnostics, the select your year, vehicle type, powertrain, engine, transmission, Transfer case, Data Display (example), Engine Data Display,,,, up to this point there has been no communications attempted by the Tech 2 and the vehicle.

Only when you select, for example "Engine Data 1",, where the next screen normally flashes "waiting for data", only then are communications attempted.

Is this where you get the error(s).

Here is a little better explanation. Two scenarios with out the candi.
1. 2002 Envoy
Connect cable to truck and turn ignition to KOEO. Power up tech2. Gauges jump to full then zero in the cluster and DIC reads UNKNOWN DRIVER. I have to cycle the power button on the tech2 and reboot a couple times and when it doesn’t do the above shenanigans it works fine.
2. 2005 gmc canyon
Connect cable to truck and turn ignition to KOEO. Power up tech2. Don’t notice any weird shenanigans but in this case was trying to communicate with the PCM. Received a NO COMMUNICATION error. After rebooting the tech2 several times it works and I can do the operation I want to.

With the Candi on my 2013 suburban KOEO the tech2 fails to recognize the candi but after several power cycles and a wiggle of the connector at the candi it connects but it occasionally causes the truck to display weird service messages. I have reloaded the firmware and tried a new main cable.

 

[George B]

Do you have anything aftermarket wired into the vehicle, like stereo or anything not stock?

Sent from my SM-G930V using Tapatalk

No, all stock equipment all give a handshake once I get the tool to communicate.

 

[kbuskill]

@kbuskill would you look at your VCI when you get a chance. I found this page that discusses an issue with the VCI. Mine lacks the QC mark near the top.

View attachment 281206 View attachment 281207

I looked at mine today. I don't see any QC markings, or any other markings, on the VCI.

 

[George B]

Well, I don’t know what to do. I was hoping I had a unique VCI and everyone else had a QC mark.
I hate to buy another VCI to find out it’s not the issue. I wish it would fail a self test so I could pinpoint the issue. Even the Candi tests ok once it is detected.

 

[gooffeyguy]

Well, I don’t know what to do. I was hoping I had a unique VCI and everyone else had a QC mark.
I hate to buy another VCI to find out it’s not the issue. I wish it would fail a self test so I could pinpoint the issue. Even the Candi tests ok once it is detected.

Do you run the tests that are in the submenu and also require the loopback plugged into the side jack?

Sent from my SM-G930V using Tapatalk

 

[George B]

Do you run the tests that are in the submenu and also require the loopback plugged into the side jack?

Sent from my SM-G930V using Tapatalk

Yes, I run all the tests and all pass.

I ordered a new OBD end on amazon to try that.

 

[Tonyrodz]

Do you run the tests that are in the submenu and also require the loopback plugged into the side jack?

Sent from my SM-G930V using Tapatalk

You need that loop back plug to run tests on the tech2 or the vehicle?

 

[gooffeyguy]

You need that loop back plug to run tests on the tech2 or the vehicle?

To run internal tests on the Tech2

Sent from my SM-G930V using Tapatalk

 

[George B]

@Tonyrodz

 

[Doubeleive]

might want to cut your losses and sell it, just be honest and say it is a little goofy but works and try to recoup some money and buy another one.
that's my advice.