Navigating car diagnostics can sometimes feel like wading through treacle, especially when your tools seem to be working against you. Recently, while using Xentry for a routine check, the initial connection phase crawled at a snail’s pace. Could the use of an OpenPort interface be the culprit behind this sluggishness? My setup, which includes a robust software configuration running on a 4-core Intel i7 (Stepping 8) CPU paired with a speedy Samsung NAND v3 SSD, and a Thunderbolt 3 connection for the multiplexer, should have been more than capable. Yet, the connection process was surprisingly slow.
Despite the slow start, the connection eventually established. However, generating even a short test report revealed a cascade of errors. It was a bit alarming to see 34 errors across 61 electronic control units. This initial diagnostic snapshot certainly painted a concerning picture.
Taking a closer look at the error details brought a sense of relief. Almost all errors pointed to “undervoltage at terminal 15.” This made sense in the context of a recent attempt to use a substitute battery that turned out to be faulty. Clearing these voltage-related error codes was a straightforward step, and with that done, I could move on to the more intriguing aspects of the diagnostic session – exploring the control units I intended to delve into for potential modifications and customizations.
However, another hurdle emerged when I tried to access the instrument cluster for localization adjustments. Specifically, I was aiming for the developer section within variant coding to switch from the Imperial system of measurements, which felt quite alien, back to the metric system I’m accustomed to. Navigating to what I believed was the correct area for these adjustments, I encountered an unexpected message:
The message “Systembedingt können einzelne Fragmente in der Liste fehlen!” which translates to “Due to the system, individual fragments in the list may be missing!” was displayed. Ignoring this warning, I proceeded by clicking “Next,” hoping to access the variant coding parameters. Instead, I was met with another error message:
This point raises a question: Is this error normal given my current setup and software configuration, or am I overlooking something crucial in the process? To investigate further, I turned to Vediamo, seeking more detailed information about the instrument cluster from a comprehensive Xentry report.
My understanding is that to connect to the instrument cluster in Vediamo, I need a specific file, likely named similarly to “IC213_IC205_213_222_E0.” However, within the VediamoData folder from Amazing Road, I only found files like “ic_204” and “ic172.” Attempting to connect using these available files resulted in a timeout error. This leaves me wondering – what step am I missing, or what am I doing incorrectly in trying to establish a connection with Vediamo for instrument cluster modifications? Could the issue be related to the specific “Startkey Xentry грн” configuration I am using, or is it a matter of file compatibility or connection protocols?
