smokymtn65
Full Access Member
Mine has as well be cause it have used it to set timing offset on the 95 burb and timing retard on '98 L29 but the CANDI thing has frustrated me..
Tech 2 Purchase
- Thread starter Costal_Cat
- Start date
Disclaimer: Links on this page pointing to Amazon, eBay and other sites may include affiliate code. If you click them and make a purchase, we may earn a small commission.
Anyone done the DC to DC converter upgrade, as DrShock details?
Hi all, got my Denali few weeks ago so still learning the ropes. Went through this thread, lots of info, wow, thanks to everyone who contributed!
I'm settling on VXDIAG VCX Nano
I'm comfortable with computers and got few old laptops lying around.
But I also came across this
Seems cool, I'm sure not as fully featured as Tech2Win. I'm looking for something to provide me with full diagnostics, not necessarily interested in programming. It looks slick with iPhone app.
Did anyone have any experience with this one? Would it give detailed info on '08 Denali or should I stick with Tech2win?
I'm settling on VXDIAG VCX Nano
I'm comfortable with computers and got few old laptops lying around.
But I also came across this
Seems cool, I'm sure not as fully featured as Tech2Win. I'm looking for something to provide me with full diagnostics, not necessarily interested in programming. It looks slick with iPhone app.
Did anyone have any experience with this one? Would it give detailed info on '08 Denali or should I stick with Tech2win?
Sparksalot
Elite Member
I’ve got a BlueDriver. It does work to tell you codes and what the probable causes might be.
George B
¯\_(ツ)_/¯
You would be happy with both. The VXDIAD would work well on a touchscreen or tablet. @Doubeleive has one connected to a tablet.
the vxdiag works fine but it is a pita to setup, you have to follow the directions given and turn off any windows security or antivirus because it is hacked software and it has to change windows files to make it work., if you install it on a tablet be sure it is in pc mode or it won't work and then once you get it working if you update anything sometimes it stops working and you have to start all over. There was a issue as well with the software license expiring at the end of 2020 so if you get the old software you have to download a patch file to get around that.
smokymtn65
Full Access Member
I have a MX obdlink https://www.obdlink.com/products/obdlink-mxp/
It works great with all the OBD apps on Andriod (i'm not an APPLE person) on driod it is bi-directional if you ever get into other stuff.
It works great with all the OBD apps on Andriod (i'm not an APPLE person) on driod it is bi-directional if you ever get into other stuff.
Sounds like MX OBDLink and BlueDriver have full diagnostics capabilities. So it's just a matter of preference. Although BlueDriver claims they provide suggested fixes. @Sparksalot you have one, what do you think about their claims:
One difference is Bluedriver does NOT work with apps like Torque Pro
Sparksalot
Elite Member
It gives you a starting point. You can also use it to see historical info and codes. Also reset them.
gooffeyguy
Tom
I have an OBDLink MX for sale in the classifieds
George B
¯\_(ツ)_/¯
Just placed an order for another VCI module. Will try and see if it works better or differently.
@George B
With the Envoy, have you any other
systems not always working just right? Symptoms of a bad ground maybe? I don't think you do or at least you haven't mentioned any.
However, I once read of a fellow who posted pictures of OBD2 port and OBD2 adapter that had 'shorted out' and partially melted. From the picture it could be seen that the apparent path of current involved only the 2 ground circuits. Turns out that on the GMT360 these 2 ground circuits, pins 4 & 5 of the OBD2 DLC connection, go to two different chassis ground points. Both of these ground points serve multiple systems and each has a splice point or two where their respective systems are collected before going on the ground point.
So if a vehicle had a poor or weak ground at one these 2 ground points the systems served by that ground might present an occasional glitch. The two ground pins are isolated at the DLC connector, until someone plugs in a scantool which may offer a path between pins 4 and 5. If a path then exists, the systems operating on the weaker ground point may seek a ground path through the scantool to a better ground point on the other DLC terminal. In the case of the thread I refer to the owner discovered that when he had the carpet replaced the G201 ground beneath the carpet was not resecured well, creating an intermittent ground. The HVAC blower was the big draw that ran through his DLC, through the scantool, and out the other ground, causing an overcurrent through the DLC connector that was never intended for that kind of current.
So why is this pertinent here?? It just bugs me that your cluster resets, like its power was lost momentarily. And the cluster uses both of the same grounds as the DLC connector. The cluster uses G201 for the lighting and it uses G102 for the electronics.
With the Envoy, have you any other
systems not always working just right? Symptoms of a bad ground maybe? I don't think you do or at least you haven't mentioned any.
However, I once read of a fellow who posted pictures of OBD2 port and OBD2 adapter that had 'shorted out' and partially melted. From the picture it could be seen that the apparent path of current involved only the 2 ground circuits. Turns out that on the GMT360 these 2 ground circuits, pins 4 & 5 of the OBD2 DLC connection, go to two different chassis ground points. Both of these ground points serve multiple systems and each has a splice point or two where their respective systems are collected before going on the ground point.
So if a vehicle had a poor or weak ground at one these 2 ground points the systems served by that ground might present an occasional glitch. The two ground pins are isolated at the DLC connector, until someone plugs in a scantool which may offer a path between pins 4 and 5. If a path then exists, the systems operating on the weaker ground point may seek a ground path through the scantool to a better ground point on the other DLC terminal. In the case of the thread I refer to the owner discovered that when he had the carpet replaced the G201 ground beneath the carpet was not resecured well, creating an intermittent ground. The HVAC blower was the big draw that ran through his DLC, through the scantool, and out the other ground, causing an overcurrent through the DLC connector that was never intended for that kind of current.
So why is this pertinent here?? It just bugs me that your cluster resets, like its power was lost momentarily. And the cluster uses both of the same grounds as the DLC connector. The cluster uses G201 for the lighting and it uses G102 for the electronics.
Very strange. To the best of my knowledge there is nothing that will cause the cluster to reset except a power cutoff. No scantool command, no loss of serial data connection, and so on.
George B
¯\_(ツ)_/¯
Here is a video I made. I also snapped photos of the codes produced. Is there a way to test if the VCIM of the Tech2 is shorting the serial data side to ground?
Attachments
![IMG_5306[1].JPG](/data/attachments/292/292142-2d5939a1ea8000829a11a6726a17698a.jpg)
![IMG_5307[1].JPG](/data/attachments/292/292144-9d1e3a837594aeeb6a371a9702fbaee4.jpg)
![IMG_5308[1].JPG](/data/attachments/292/292145-de6c616298d8ad42f9fc3f20c606f34a.jpg)
![IMG_5309[1].JPG](/data/attachments/292/292146-cece19e5aa5a53d13f2656228e6b8696.jpg)
I will do some retesting today. Just by looking at the video I would say the gauge sweep to zero you have there is NOT a cluster reset of the sort that I have seen from a power loss. A power loss reset I think moves all needles to zero much more rapidly.
I have recently tried a 'short to ground' of the serial data line and I don't think it did what yours is doing. But I want to recheck.
The codes make it clear... something IS fouling the data bus. You are reading the PCM saying that it has lost comms with those modules. The "Unknown Driver" message is a direct result of a loss of comms between the BCM amd the instrument cluster.
Here is a short video of me grounding out the data bus and the results seen at cluster and on the message stream as well.
youtube.com
Grounding the GM Class 2 Serial Data Bus
Here I show the effect of grounding out the GM class 2 Serial Data bus. Note that the cluster doesn't reset, it only stops updating. On the phone screen seen...
youtube.com
George B
¯\_(ツ)_/¯
I guess it’s a mystery until we can see what the tool is doing when booting. I am hopeful my new VCI works differently and that I can send you the goofy one for testing. It would be interesting to see what is going on.Here is a short video of me grounding out the data bus and the results seen at cluster and on the message stream as well.
Grounding the GM Class 2 Serial Data Bus
Here I show the effect of grounding out the GM class 2 Serial Data bus. Note that the cluster doesn't reset, it only stops updating. On the phone screen seen...
Similar threads
