Messed with the kess v2, here's some CAN logs, not sure if there'll be anything of interest, lots of random chatter...... sorry.
Read takes roughly 1.5 mins, write a bit less and ID just pulls the security info.
- read.jpg (33.72 KiB) Viewed 13683 times
When I get some more ecu's that have faults but still have comms i'll mess with changing/cloning security details and get logs but it's a knockoff and has killed a few ecu's doing this so I'm hesitant unless it's sacrificial.
In case people missed it in other threads, the chockoff is a horrible flakey hit and miss piece of hardware with hacked drivers/software (with versions that don't exist) that will fubar an ecu.
Gampy wrote:
You just don't get it
Get what? log data, pull shit apart and rip roms with the end goal that shit is open source and can be made by anyone that is competent with a soldering iron?
There's so many clones of the vx and it's been around for so long that even the old clones don't work with new firmware/drivers anymore, what ever encryption they're using, we know/can see what goes in and what come out, constructive thought can be put elsewhere with a grander end goal.
Like this chineese knockoff kess pos, i'll never make money back on it but it's got the ins and outs that to make it tick that are interesting and semi useful without trying modify it, it has a SD Card in it with crap to make it work, the cheeky buggers take a FAT image and basically swap the bits to make it unreadable but it's built into the hardware to revert and decrypt a simple thing..... doesn't change that it's a clone that will %#^ s%$t up royally and you can't tell if you have a useable cheap clone or a really nasty cheap clone.
But if it's coded by people, built by people and for the people then that's a product I'd trust.
And by god I want one of those hammers now........
