VXDIAG VCX NANO, VCX SE, VCX Plus, VCX DoIP multi diagnostic tool software and hardware support from vxdiagshop.com
Problem:
The vx manager detected the VXDIAG VCX SE Benz VCI information, but there was no network connection, VCI was not connected. The vx manager showed offline. Any solution?
Solution:
Vxdiagshop.com engineer did a Teamviewer check and found he did not install Passthru and Benz C6 driver.
So vx manager shows offline status.
After installing C6 driver, it shows online status and the VCX SE Benz VCI is well connected.
If vx manager says No device and offline, check solution here
Problem:
It is an Infiniti ex35 2009 North American model. VXDIAG VCX SE Nissan Consult 3 plus v240 software is stuck on the scanning system page. How to fix it?
Try to connect to each single module, it stuck on this page and did not proceed.
Solution:
Patch issue.
Old patch (for Consult3 plus 226) is not working with the V240 or later Nissan software. Otherwise will fail to scan/diagnose systems.
Solved!
Use new patch. It communicates with system now.
Question:
My Renault CLIP V222 version cannot detect vxdiag vcx se Renault DoIP cable.
Do i need older or newer version or patch or something? Driver is installed and have renault active license.
Solution:
V219 Clip version works fine.
The latest version tested working is V237. You can use both V219 or V237.
vxdiag works with CLIP 237. Just need to use proper driver.
contact vxdiagshop.com for VCI driver or check here directly.
Free Download and Install VXDIAG Renault CLIP V237
Works fine with CLIP237 and is definitely not crap.
Works fine for diagnostic functions and repairs.
Just learn how to do proper installations and work with software and hardware.
Pay attention to the driver installation. Install Renault driver separately. Don’t need to install Renault driver in vx manager.
VXDIAG VCX SE and Scanmatik 2 Pro which is a better J2534 Passthru device for Xentry Passthru software?
Here is the clue.
Scanmatik 2 Pro (SM2 pro) J2534 is great solution for small car repair shops or car repair shops where Mercedes is a frequent but not core brand. With these devices, you can use DAS/Xentry/Vediamo 4/Monaco almost to the fullest. But passenger cars older than 2005 – most likely, not all units will be seen or the car will not be detected at all. Trucks that open via DAS will be ignored right away. But, for example, Xentry Cars 2024.09, Xentry Trucks 23.12 and newer do not officially recognize SD Connect C4 and work fine via Passthru.
VXDIAG VCX SE Benz is the most universal device at the moment, with support for DoIP and fresh versions of Xentry. It can be used with both Xentry Openshell and Passthru version. with Xentry 2023.12 XDOS and it takes everything it needs. In PassThru mode, it works better than Chinese clone of Scanmatic.
On diagnostics of MB w167 2021 year Xentry PT 2023.12 + SM2 did not work. Xentry XDOS 2023.12 + VXDIAG worked.
It gave Login fail on Xentry Cars 2023.12 Passthru and at the same time were perfectly diagnosed through the same Xentry Cars 2023.12 XDOS with exactly the same set of certificates.
So it is necessary to use both Xentry XDOS and Passthru version. If Passthru fails, use XDOS. In this case, vxdiag vcx se is a better option.
Problem:
One of our customers tried to diagnose an electrical car Mercedes EQE 350 SUV with VXDIAG VCX SE Benz and 2024.03 xentry, software failed to access and asked to log in.
Run Xentry Cars software on desktop, using the login user name and password on the note pad (check images below).
If still cannot diagnose this electrical car, you may need Zenzefi license.
After uploading Zenzefi license, run Xentry car software on desktop and login with that user name and password again.
VXDIAG Benz C6 driver is ready for 2024.09 Xentry. The new Xentry software hard drive is available at www.vxdiagshop.com.
2024.09 VXDIAG Benz Software List
Xentry/DAS: 2024.09
DTS Monaco 8.13.029/ 9.02
Vediamo 5.01.01
StarFinder 2024
WIS/EPC
The hard drive contains Vediamo engineering software now.
NOTE: 2024.09 software does not support Benz trucks. If need to diagnose Benz trucks, choose 2023.09 version xentry.
For VXDIAG VCX SE and VCX DoIP Benz multiplexers.
Driver version
Choose VCI version as 202409 in Xentry Diagnosis VCI Update tool.
2024.09 VXDIAG Benz Software Display
Tutorial: How to program 2017 Chevrolet Volt LT to allow Openpilot Operation using Techline Connect SPS.
Several people have successfully enabled Openpilot operation on 2017 LT Volts without stock Premier features. This section will cover the firmware modifications required to enable Openpilot. Hardware modifications are also required. Stock cruise control will be inoperative after these modifications, only cruise available will be Openpilot once it is booted.
Introduction
The Chevrolet Volt (2016-2018) is a popular vehicle to use with OpenPilot and the C2/C3. Out of the box, only the Premier optioned Volt with the Driver Convenience II package is supported. This model includes a radar behind the bow tie on the grille, LKAS, and Adaptive Cruise Control. The LT version is not officially supported, nor is the Premier version without radar Adaptive Cruise Control. But…. There is a way! Either way you have to have a radar which can easily be bought on eBay and wired to the OBDII port, as well as the radar transparent bow tie which is much harder to come by. I believe this is optional if you want to use the very Alpha E2E longitudinal model.
All of the main modules in the vehicle are the same between LT and Premier versions. This means that the only limitation is in software, i.e. which commands the ECM (Engine Control Module), BCM (Body Control Module), Brake Module, Power Steering Module, and Cluster are willing to accept/transmit between each other and OpenPilot. GM may change their software in the future, breaking the process. As always, do at your own risk. Worst case scenario can leave a vehicle module inoperative if done incorrectly. Firmware modification like this will result in DTC (Diagnostic Trouble Codes) that will be invisible to the user (no dash icons) but will be visible if you take the vehicle to the dealer. All codes reference lost communication with Premier modules that do not exist such as Park Assist and Blind Spot Monitoring and do not affect normal operation.
After programming, stock cruise control will cease to exist, you must always use Openpilot.
If you do not disable Anti-Virus and firewall you will have issues! VX Manager is highlighted as a virus for some reason. I installed on a fresh Windows install out of caution.
ACDelcoTDS is GM’s online portal to vehicle diagnostics and programming. A single VIN costs $45 for a year.
Sign into https://www.acdelcotds.com/subscriptions, or create an account if needed.
When purchasing a VIN through the system, you will need to find a VIN that has the software you desire. i.e. a Premier with Driver Confidence II package (make sure it has a flat plastic trim where the bow tie is on the grille). Also, ensure the VIN you select is the same year as your vehicle.
Optionally purchase another VIN that is the actual vehicle that you own, in case things don’t work you can flash the original firmware back to the car (or if you sell the car and wish to return to stock).
Once purchased you will see your active VINs under “My Subscriptions”. Click “View”, then select the Premier VIN. This will bring you to a page to download and install TechLine Connect if you have not already. If TechLine Connect is installed, you will see an option to start it. Before running/installing TechLine Connect, open VX Manager, your VCX Nano will beep to verify connection, if it does not, select reconnect on the main screen.
VIN Subscriptions.
VXManager Reconnect if needed.
Once TechLine connect is opened, make sure your Premier VIN is selected, then click “Select”.
A dialog box will pop up to select the interface with the vehicle, select “VXDIAG”.
Ensure Premier VIN is selected at top dropdown box. Click “Next”.
A listing of all the control modules from the Premier VIN is shown. From this point forward, this screen will be where you select the module you would like to program.
The system will give you an error at the selection of each module, letting you know the VIN selected does not match your VIN, always select “OVERRIDE”.
The following photos show the programming process as well as the ECU list. It will be the same process for each module, although the information displayed will vary.
ECU List Page 1-3
ECU Programming Page 1-4
Body control module programming is required to allow lateral/longitudinal operation of Openpilot. This module may not need to be programmed if you already have lateral control with Openpilot and are currently using a Pedal for longitudinal control.
Engine control module programming is required to enable longitudinal operation of Openpilot
Power Steering Control Module programming is required to enable lateral operation of Openpilot. Not required for Volts that already have LKAS
Electronic Brake Control Module programming is required to enable longitudinal operation of Openpilot
Brake Booster Control Module programming is required to enable longitudinal operation of Openpilot
Instrument Cluster programming is not required for Openpilot operation, although it does offer a more streamlined user experience.
Without programming: Cruise Control icons will appear distorted
With programming:
Instrument Cluster programming is a bit more involved. If you flash with the Premier firmware, you will fix the above issues, but the cluster will also display errors for ECUs that your vehicle does not have (for an LT Volt you will receive “Service Park Assist” and “Service Blind Spot Monitor” errors EVERY TIME YOU START THE VEHICLE. It will also dash out the mileage after an undetermined amount of time due to a VIN MISMATCH. We need to tell the Instrument Cluster that we do not have these systems installed so we no longer receive these errors AND keep our original VIN. This is done using an XML/RPO Build File. A “recipe” per se for the cluster firmware.
At the end of this document, I will document how these files are acquired. For your enjoyment I have attached this file, for a 2017 Volt, here. (unzip it). I have also attached an example XMLFile.txt here. All you need to do is replace YOUR_VIN with, well, your VIN.
NOTE: Using the following directions, you will temporarily receive a "Service Front Camera" error anytime Openpilot is disconnected or not fully booted. Go to the next section to see how to fix this issue if you find it to be annoying.
Copy “XMLFile.xml” to /DPS/Config.
Open “Developmental Programming System”. Select “Program” at the top of the window, then “Dev. Programming Tool”
Select “1 (33.3KBd)” from the “Diagnostic Pin” dropdown box. Select “ECU Configuration”.
Select “Select XML Config File”, choose the file you just copied to /DPS/Config. Select “Create Build Data File .TXT”
Ensure the VIN at the top is populated with YOUR VIN. Select options under “RPO Selections”.
For an LT Volt:
Select “Write RPO Build Data”
Ensure “Build Data File” box has been populated with the file you just created.
Select “Execute”, do not interrupt process until it finishes or errors out.
To quickly verify correct execution, try to turn on cruise control on the steering wheel, you will see the new icons!
In short, the firmware is a generic cake (could be chocolate, could be vanilla) lol. The XMLFile.xml is the recipe to make any generic cake minus the flavor. The XMLFile.txt file that we create tells the recipe XMLFile.xml to make a chocolate cake vs a vanilla cake. Make sense?
GMs intention is to make this process seamless, and for most users this is fine. But when we want to modify the firmware we have to do this manually. Timing is important for this, the XMLFile.xml is temporary while the firmware is being downloaded and is immediately deleted. We have to copy the file at JUST the right moment.
In Windows File Explorer, navigate to /USERNAME/sps/type4, if this folder does not exist, create and open it. Keep it visible alongside the TechLine Connect software.
Go through the process of programming the “Instrument Cluster” just like you would any of the other modules, get to the point where you select “Start Programming”
After clicking “Start Programming”, the program will have a spinning circle as it makes connection with the vehicle. As SOON as it gets to the next step of downloading the firmware, pull the VCX Nano out of the OBDII port (to prevent actually programming anything). AT THE SAME TIME there should be a new folder in the type4 folder. Either open it and drag the XMLFile.xml to the desktop, or drag the entire folder to the desktop. At this point TechLine Connect will report an error (because the precious files are gone). That’s fine. Exit TechLine Connect and use the XMLFile.xml in DPS as described earlier. Even better, open that file in notepad and you can see what each RPO code in the build file does.
Note: Not all ECUs have an XMLFile.xml, there seems to be no reason an ECU has it vs not. What’s important is the Instrument Cluster has this file and allows us to cherry pick the features we want and don’t want, allowing an LT Volt to have Premier ACC icons without additional system errors, while at the same time keeping YOUR VIN on the ECU, preventing a VIN mismatch error (dashed out mileage).
One of the things that bothered me with this setup is the “Service Front Camera” error that temporarily pops up before Openpilot is fully booted. So I dove down the task of getting rid of it, and sure enough, it's possible! I have loaded the modified XMLFile.xml here.
Two RPO codes when applied to the IPC create this DTC/error. KSG: CRUISE CONTROL AUTOMATIC, ADAPTIVE WITH STOP/GO, and UHX: LANE ACTIVE SAFETY-KEEP ASSIST. This makes sense as the stock Premium Volt has a camera for both of these systems.
The file that will be edited for this is the XMLFile.xml
This file has several sections that are important. DPS looks at the XMLFile.txt on how to build the instruction set to the IPC. So everything is based solely off RPO codes.
At the very bottom of the file, there is a section that simply lists RPO codes, for example:
<RpoCodeItem>
<OptionCodeID>OCKSG</OptionCodeID>
<OptionCode>KSG</OptionCode>
<Description>CRUISE CONTROL-AUTOMATIC, ADAPTIVE, WITH STOP/GO</Description>
</RpoCodeItem>"
Above this section are the RPO options themselves.
Then above that, there are DTCs that can be set! For example:
<Parameter ParamDefaultValue="00">
<ParameterName>P_ENABLE_DTC_C23A_FTB_00</ParameterName>
<StartByte>3</StartByte>
<StartBit>4</StartBit>
<BitLength>1</BitLength>
<ConfData useConfData="true">
<ConfigData Value="00" AutoGenExpression="(!KSG)">
<Product>
<RpoCodeRef IDREF="OCKSG" hasToBeAvailable="false" />
</Product>
</ConfigData>
<ConfigData Value="01" AutoGenExpression="(KSG)">
<Product>
<RpoCodeRef IDREF="OCKSG" hasToBeAvailable="true" />
</Product>
</ConfigData>
</ConfData>
<ServiceSection IsServiceAccessAllowed="false">
<Interpretation Text="Disable" Value="00" />
<Interpretation Text="Enable" Value="01" />
</ServiceSection>
</Parameter>
The first RPO code that will throw DTCs, as well as the "Service Front Camera" error, is KSG: CRUISE CONTROL AUTOMATIC, ADAPTIVE WITH STOP/GO. Pay attention to the above section. First, you can see that this block of code references setting a DTC if the RPO code of KSG is selected. For the ParamDefaultValue, it shows 00 meaning this DTC is set to DISABLED. But, if you have the KSG option, the DTC value is 01, meaning this DTC is set to ENABLED so if the IPC finds an issue with option KSG you will get an error on the display. Changing the 01 to 00 disables the DTC even with this RPO code selected! This will have to be completed on line 969. No more “Service Front Camera”, for Adaptive Cruise Control!!!
The second RPO code that will throw DTCs, as well as the “Service Front Camera” error, is the UHX: LANE ACTIVE SAFETY-KEEP ASSIST. Notice in the DTC list of XMLFile.xml, there is no DTC item matching up to the RPO code of UHX. BUT… notice that there are two different sections for UHX. One is P_LANE_KEEPER_ASSIST_INDICATOR_ENABLED and the other is P_OPTION_LANE_KEEPER_PRESENT. So on line 1595, we change the 01 to 00. This tells the IPC not to look for the system on the CANBUS, while the indicator is still enabled.
After editing the XMLFile.xml, load it into DPS as the instructions dictate, and flash the IPC. You will never receive “Service Front Camera” ever again.
FINAL NOTES: Like I said earlier, do all this AT YOUR OWN RISK. It worked on mine, but differing models/years could be different. After programming, you may need to use GDS2 to remove all DTCs, or a code reader to clear out the check engine light. This is normal. Also needed is a window re-calibration (move driver’s window full up and full down to calibrate automatic operation). Last but not least, you may have to accomplish a parking brake re-calibration through GDS2, which basically walks you through setting the electronic parking brake while the system reads it’s position. Viewing all DTCs in GDS2 will let you know if you need to accomplish this. GDS2 will list “Parking Brake Relearn Required” under the full list of DTCs.
Troubleshooting
If you're getting a "Cruise Fault" and unable to enable openpilot control after confirming all firmware has flashed correctly, try recalibrating the brake pedal position sensor through SPS.