Here's how immo emulation on an Arduino works.
I did some work on the algorithm but it worked.
In preparation, reading PIN - we will see - I have some ideas - I wonder how they will work.
[movie: 03c0cd6e5e]
https://filmy.elektroda.pl/11_1639950825.mp4 [/ movie: 03c0cd6e5e]
I am after trying to read the PIN from the engine controller:
First, I performed the tests on the EDC17C60 because I knew the PIN
And then on VD56.1
The tests were successful - the PIN was successfully read
I HAVE 3 ideas how to do it
1 - FIRST IDEA - effective
Querying the ECU for all PIN codes
Already tested on the purchased VD56.1 - I did not know the pin of this ECU before.
Time consuming
The number of different PIN codes is 34 ^ 4
34 because we have so many characters available 0-9 A- Z (excluding o, and) capital letters.
^ 4 because we have 4 PIN code fields
the number of combinations is therefore: 1,336,336
The method of polling (ARDUINO) gives the possibility to perform 4 queries per second
And receiving 4 answers and information confirming unlocking or not unlocking.
The time-based loop runs look like this:
.......... 92h 45` .................. 163`45`` ............ 4` 48`` .......... 8.5``
... ok (3 days 20h 40min) ....... ok (2h 45min) ........ ok 5 min ......... approx 9 sec
............... X .............................. X ... .................... X ...................... X
Assuming that our PIN code is: ZZZZ
You have to be patient (it is not a very efficient method).
But it's not that bad - this is how this type of encryption and polling is not super perfect (similar to SEED and SEED KEY) - I've already described it before.
- I got the first working random pairs after 5 minutes and the next two after an hour.
This suggests a slightly different sampling algorithm
(IDEA # 2).
I think getting a PIN code should take 15 minutes to 30 minutes
and at worst 2-3 hours
And that's acceptable for my needs.
I will test.
I gave it for free for the new year ...
