SPA CEM PIN Decode: 29 keys/s (160 hours) despite stable connection and low ping
-
Hi everyone,
I’m sharing my experience regarding a CEM PIN decode on my 2016 XC90 T8 (SPA), as I’ve hit a technical brick wall that makes the process impossible.
My VDASH session is consistently stuck at a rate of only 29 keys per second, resulting in an estimated time of 160 hours (nearly a full week).
Technical Setup & Troubleshooting performed:
Connection: Switched from Wi-Fi to a dedicated 200 Mbit wired Ethernet (UTP) line.
Network Latency: A manual ping test to d5t5.com shows a stable 40ms. However, VDASH fluctuates wildly, showing a "red" latency of 1752ms at times, and staying around 143ms at best.
Hardware: Tested with two different laptops and various USB ports to rule out driver/OS bottlenecks.
Power: Car is connected to a 20A Victron charger, maintaining 13.9V.
Interface: Using the Super J2534 cable.The Issue:
Despite the healthy 40ms internet connection, there is a massive bottleneck in the communication between VDASH and the servers. A 160-hour decoding time is not feasible for a home setup.I opened a support ticket 9 days ago but have received zero response.
Is anyone else experiencing this 29 keys/s limit on the SPA platform? Is this a server-side throttle, or is there a specific J2534 driver setting that needs to be tweaked to get closer to the expected 100+ keys/s?
I would appreciate any insights from the developers or the community, as the current performance makes the PIN recovery feature unusable.
-
@XC90-joch could you do a test with a different charger, or for some short time period (few minutes) without a charger attached? Some chargers create heavy interferences that make the cracking really slow or even impossible. You should also remove any third party security software from your Vdash laptops, as some of those interfere with Vdash. Avast, Norton, Avira for example. Could you also test at a different time of the day, to rule out excessive server load caused by too many users online at the same time and/or ongoing ddos-attacks, that also happen from time to time.
-
Hi Schnappi,
Thanks for the suggestions!
Regarding the charger: I am using a professional Victron power supply, which is usually very 'clean', but I will definitely try a session without the charger attached for a few minutes to see if the keys/s rate improves. It's a good point about potential EMI interference.
As for the laptops: I will make sure to disable Windows Defender and Firewall completely during the next test to ensure no background process is throttling the connection to the D5T5 servers.
I've tried at various times during the week, but the result has been a consistent 29 keys/s. I’ll report back if the 'no-charger' or 'no-firewall' approach makes any difference in the latency.
Thanks for thinking along!
-
@XC90-joch Windows Defender and firewall usually don't make any problems with Vdash. But you might want to create an exeption for Vdash in the defender by adding the hidden install path "C:\Users{YourWindowsUserName}\AppData\Local\VDASH" to the list of excluded folders and also add C:\Users{YourWindowsUserName}\AppData\Local\VDASH\VDASH2\Frontend.exe and C:\Users{YourWindowsUserName}\AppData\Local\VDASH\VDASH2\Vdash.Frontend.exe to the list of excluded processes/files.
Also check the active power plan of Windows. For the cracking it should be set to "high performance". Also check the power saving setting of the USB ports and disable any power saving modes.
And the most important question. Where did you buy your adapter? 95% of all Mongoose/Super J2534 adapters sold on chinese plattforms don't use the original Atmel chipset and perform like crap.
