AutoXer wrote:cboles wrote:On a bench programming setup, you could let it run for a few days with a special program to try all 65536 combinations of init codes.
Looking at the log when I connect, it looks like it sends a byte(0x01), then gets a response, then sends another byte(0x00), then gets another response. If this is the case, couldn't you just brute force the first byte until you get a response. Then using the found first byte, brute force the second byte.
255 combos on the first + 255 combos on the second = 512 total tries possible
Maybe I'm over simplifying it.?
Surly, you need the whole init to be correct to get a response hence 65536…?
But the idea to code an option into the app to run through all 65536…?
If the ECU does not need to be reset during init attempts, I could leave it in the car running and logging the response. If the sequence can be paused (saved) and restarted from the last attempted init it can simply be done in runs until completed or a positive response received?
It sounds too simple. What are we missing?