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. -
-
@XC90-joch Obbe is a partner of D5T5 and makes all tunes for Vdash. So I would expect him to deliver the same adapters as D5T5, with the same quality and 100% tested to work as expected. You might want to check the USB connector of your adapter. There was a bad batch of adapters which had connectors that got damaged in USB ports that are a little bit to tight.
Here is some info about it https://svdns.info/2024/12/09/super-j2534-v2/ -
-
@alienek I know of the third-party services
But I've already bought the adapter & credits for the D5T5-route, so i expected to get some better results & support. The ticket i submitted @ D5T5 has had the same status for a month now: "Unassigned".Pretty lacking for a paid service..
-
@alienek if you know which hw-numbers are hard or even impossible to crack, would it be possible to add a warning message to Vdash for those units, so users know that the slow cracking speed or failed/impossible cracking is expected? Do you also know if such problems exist for certain P3 CEMs? My 2018 V60CC took around 130 hours to crack, if I remember correctly, which wasn't a big deal for me. But anyway, knowing that you have to expect much more than usual time for cracking before you even start would be really nice, and will definitely will result in less frustration on the user side. Especially as there are lots of complaints and irritations about vdash regarding cracking and also lack support in general, if you look across popular Volvo forums.
-
@VOLOK Hi mate. Any chances I could ask you for a help with PIN for my V90? I spent 5 weekends already trying to decode it with Vdash but its absolute joke. 20 keys per second on exactly the same setup that did my P3 in 10hrs at nearly 200 keys per second.
And sorry for resurrecting an old thread.
Thanks -
@HoodedLime Not a helpful answer, I know, but 200 keys/s on a P3 are a clear indicator that your setup is slow or has some sort of bottleneck. 450-500 keys/s on a P3 are possible on good setups. Atleast with P3tool and P3Dx. Not sure about Vdash as I'm not using that for P3 cracking anymore.
-
@T5-T6-Schnappi thanks for the reply. I assume that was due to cheap chinese DICE I was using. But still, 200per/s was light years above my current 20 lol. Anyway, I folded and just ordered myself an Orbit with PIN retrieval so hopefully will get my code very shortly
-
@HoodedLime Good luck!
200keys/s is actually okay for a DICE. But on a SPA you should definitely use a Super J2534 or a VOE adapter and not a DICE. -
@T5-T6-Schnappi I actually swapped to enet cable to see but it made no difference to speed. Anyway, received my PIN from Orbit guys 15mins after ordering, outstanding service
-
@HoodedLime I didn't mean for cracking, but for coding/programming your car. The DICE should still work, but is too slow and therefore risky to use.
