VXDIAG J2534 GM Techline Connect Error UEH101: null Solution
Problem:
Tried to use VXDIAG VCX SE GM with GM Techline Connect SPS2 for ECM programming. TLC reported an error “UEH101:null”. Anyone gotten this error before?
Solution 1:
Delete it and reinstall happened to some others.
If hit uninstall then redownloaded. Same problem. You have to uninstall everything that involved it’s. There’s like 15-20 different things that tie in to it. Have to go to add remove programs and remove it all.
Solution 2:
Had this happen not too long ago called tech support and 3 hours later they said it was my computer. New laptop. I was using google chrome to sign in to tds, but when I switched to Microsoft edge I worked and went through and working ever since. Hope you get it resolved!
VXDIAG Tested Working with J2534 Hyundai Kia
VXDIAG VCX SE was tested working as a passthru device for US J2534 Hyundai/Kia software. Here's the review from Mr. Nick Mayer.
"Just for your info vxdiag vcx se interface works no problem with J2534
Hyundai/Kia usa market
2018-2023.
https://www.hyundaitechinfo.com/
https://www.kiatechinfo.snapon.com/default.aspx
Software work with vxdiag programming and diagnostic 2018 ad passthru.
2019 KIA rio EOL CODING out tpms ( Variant Coding) is done with vxdiag. I remove tpms completely from the car.
Also bitbox, alexflasher, gromcalc so far i checked and it worked."
Hyundai/Kia J2534 Diagnostic Tool Software:
The Hyundai/Kia J2534 Diagnostic Tool software is available for use on 2018 model year and newer Hyundai/Kia vehicles sold in the United States market. Utilizing Hyundai's/Kia's J2534 Diagnostic Tool software to diagnosis Hyundai/Kia vehicles requires a current paid J2534 Diagnostic Tool subscription and a compatible SAE J2534-1/2 compliant pass-thru vehicle communication interface (VCI) device.
PCM Update with VXDIAG and Chrylser J2534 Application
VXDIAG VCX SE can be used as J2534 passthru device for OEM software programs. Some users tested working with Chrysler J2534 application.
Chrysler GPEC module calibration example:
Change of calibration to GPEC PCM Dodge Avenger 2008 with the vxdiag vcx se pro/scantech interface.
NOTE: scantech interface is the same as vxdiag vcx se j2534 passthru. It is customized by South American dealer.
Free to test by your side. You are at your risk.
Correct Mustang Speedmeter with VXDIAG & Forscan
Tutorial: How to correct Ford Mustang Speedmeter (if your car is just off from the factory or you've changed tire sizes) with Forscan and VXDIAG J2534 passthru.
What's required:
A laptop running Windows
Free Forscan software with a free extended license
OBD scanner that works with Forscan ((VXDIAG VCX NANO Ford, VCX SE pro or other J2534 passthru))
How does it work?
For 2015-2019 Mustangs, Ford programs the tire size of the car on BCM line 726-12-01 in the second four-digit block of hex. For 2020+ Mustangs, it's split between 726-15-01 and 726-15-02 as described below. It's stored as the nominal circumference of the driven wheel in millimeters with a revs/mile conversion factor of 96.7%. To save you the trouble of doing a bunch of math and conversions between decimal and hexadecimal, I've come up with a hex calculator that you can use here: click here
This is covered in the spreadsheet, but for example my 2017 GT PP currently has this in the BCM as-built:
726-12-01 xxxx 0858 xxxx
If I changed my rear tires to 305/35R19's, my calculated value is this:
726-12-01 xxxx 0843 xxxx
The x's mean to leave whatever value is already there.
2015-2019 Mustangs share the 726-12-01 address. For 2020+ Mustangs, the location has changed to this:
726-15-01 xxxx xxxx ABxx
726-15-02 CDxx xxxx
xxxx
ABCD = your calculated value. It's split between the two addresses for 2020+ cars.
You also have two options here. You can simply enter the size of your current rear tires as in my example above, and using the nominal diameter of that tire size the calculator will give you a hex value you can program to get pretty close (maybe even dead on) with the speedometer. Tire manufacturers vary of course, and your car's speedometer may be a little weird. So below the tire size calculator is a truing calculator that relies on a precise measurement from GPS.
As stated in the calculator, I recommend that you use a GPS that can output in tenths of a mile per hour, that you set the cruise on level ground as high as reasonable (eg 75mph) and that you use the needle rather than the digital speedo or digital cruise setting to set your speed, since the digital outputs are rounded to the nearest whole MPH. That is to say, you might see that the car is set to 75mph, but internally the car could be set to 74.5 or 75.4, and you'd never know because it's rounded before it's shown to you. Here is an example screen showing tenths of a MPH from a Garmin on the satellite info page (press and hold on the satellite reception strength bars in the upper left corner to get to this page.)
Try to set the needle exactly on one of the MPH hash marks on your speedometer for best results. Move your head to the right to eliminate parallax error at that speed, see the below video.
FWIW, if you have other Ford vehicles this seems to work on them as well. I've personally confirmed that it works on F150s so if you've got a giant bro-dozer with 35″ tires, it's time to fix that speedometer!
I have a DTC now.
You WILL get a non-MIL DTC P160A (Control Module Vehicle Options Reconfiguration Error) when you change this in the PCM.
Thanks to the FORScan devs and some beta testing adventurers, we are able to reliably remove this DTC now using a new feature.
This new feature is only available in FORScan 2.3.11 or higher.
What you want to do is go into the computer-chip-looking tab in FORScan where you normally edit as-built. At the top, you'll see a new function for the PCM – "Module initialization/relearn vehicle data" – see this screen shot:
Highlight that function and hit the play button, and follow the onscreen instructions to the letter.
Once it's finished, rescan for DTC's and remove the P160A DTC. Go drive around and scan for DTC's again. You should be in the clear.
Note that if you ever wish to return to stock, you'll have to run this procedure again after setting the as-built values for the tire size back to stock.
What should I do if I haven't changed my tires but my speedometer doesn't match my cruise setting? The speedo reads fast!
I feel this needs to be addressed, because people don't seem to believe it.
There is a *large* amount of parallax error in these cars when the needle is pointed up, which it is when you're at highway speeds of around 70-80. At those speeds your speedometer will appear to read 2-3mph faster than your cruise setting.
Why? The needle is thick and spaced out from the gauge face, so the perceived "needle" (the illuminated red center section) will give a great deal of parallax error unless you're viewing perfectly perpendicular to the needle.
Unfortunately, the designers chose to put the speedometer in such a position that reading the speedo with your head perfectly perpendicular to the needle means moving your head WAY right, far away from any natural position in the car.
Can I Use VXDIAG J2534 with Renault Clip?
Is it possible to use vxdiag vcx nano or vcx se as Renault can clip Passthru interface?
Users have tested it but no luck.
Test report:
I have try with VXDIAG interface on Renault Megane 2015, it detects the
interface and also detect the car very fast,
but after enter the network test
the software crash, something about CAN1, CAN2 etc error.
The error comes from AcqBoardJ2534Adapter.dll and it was on Clip 198.
VXDiag supports Can / Can PS but does not support Can CH1 / Can CH2, the firmware is too old for Clip and the new RSN interface.
VCX Nano will not work interface is limited by licensed. It is not recommended as passthru for CLIP.
VXdiag j2534 is known good working with Benz, GM, Ford, Toyota, JLR etc passthru devices.