pkhoury
That guy with the goats
Even better! Thank you Greg.It turns out that OS/2 article is online here: https://www.linuxjournal.com/article/2734
Even better! Thank you Greg.It turns out that OS/2 article is online here: https://www.linuxjournal.com/article/2734
It's been MANY years since I stopped running O/S 2.I'm also bummed the magazine above has the OS/2 article covered up. I was in high school in the mid-90s, and was an OS/2 zealot then. Not so much anymore, but I still like reading about it. Amazing to think how far we've come along since then (also toyed with Debian 2 around 1996, and that was quite fun as well).
I haven't actually used ecomstation, aside from a demo, though I have installed Warp 4.52 on some vintage ThinkPads I collect. And relating to this thread, I was actually running VDS-Pro on a restored ThinkPad 755 (rebuilt the battery pack, so I was able to take it outside). VDS-Pro's UI sucks. kw1281test makes a lot more sense!It's been MANY years since I stopped running O/S 2.
I ran a dial in bulletin board on it for years and house lighting control.
Its currently being developed as eComStation.
ecomstation.com
The good old days.
I second this, and vote for kwHack as the nameQuestion @gmenounos : Since KW1281Test Isn't really a test anymore, do you plan on changing the name of the software? I don't mind the name but curious if you were planning on a more permanent sounding name change.
I will most likely change the name at some point, especially since it now can also speak a little bit of the KW2089 protocol. It's not currently a priority, but I do understand that "kw1281test" is not the easiest thing to type or remember.Question @gmenounos : Since KW1281Test Isn't really a test anymore, do you plan on changing the name of the software? I don't mind the name but curious if you were planning on a more permanent sounding name change.
Oh, I'd definitely make a GUI for it if I develop an Android version.I feel like an Android version would be pretty klunky to use without a graphical interface, however I know there are other apps out there that use FTDI-based devices well (like ALDLDroid which is designed mostly with OBDI GM in mind but supports most things that are supported by TunerPro)
When did I ever say this would work on Audis?Hi guys, Been reading this thread with a great deal of intrest, as I have a vdo cluster in a 2003 TT roadster which I need to extract the SKC from.
gave the kw1281 a whirl on an old KKL lead and came back with this...
KW1281Test 0.48-beta (https://github.com/gmenounos/kw1281test/releases)
Args: com3 9600 17 ReadEeprom 204 6
Opening serial port com3
Sending wakeup message
Reading sync byte
Keyword Lsb $01
Keyword Msb $8A
Protocol is KW 1281 (8N1)
ECU: 8N2920980A KOMBI+WEGFAHRS. M73 D14
Software Coding 00444, Workshop Code: 00029
Sending Custom "Read Software Version" blocks
Sending Custom "Unlock Additional Commands" block
Received NAK block
Received NAK block
Received NAK block
Received NAK block
Received NAK block
Sending Custom "Unlock partial EEPROM read" block
Unhandled exception: System.Collections.Generic.KeyNotFoundException: The given key '0' was not present in the dictionary.
Really frustrated as the program was really quick to establish a connection. Well once i realised the Baud speed was 9600 not 10400.
Thought I'd be on a winner as the cluster is VDO And stamped with vw as well as audi...
This is such a powerful tool. Any ideas?
Alan
I've just published a new release with experimental support for your cluster: https://github.com/gmenounos/kw1281test/releases/tag/v0.49-betaHi, no you never said it would work on Audis
I was just so impressed with it, I thought id give it a whirl!!
I didnt think it was, but I'm probably wrong..
should I give it a try with those paramiters?
Seriously though, keep up the great work!
.\kw1281test.exe COM3 9600 17 DumpBeetleMem 14336 2048
That's great that it worked on the TT. Looks like I'll have to change the name of the DumpBeetleMem comand to DumpMarelliMem.Well... it seems to have worked, got a dump from the tt just looking up the skc location to convert and then verify. will post back results
Not that I know of. You could either remove/tape-over the immo light or else remove the immo delete and match the cluster to the ECU.I got an immo delete for my ecu but now the immo light in the cluster keeps flashing.
Is there a way to use this to shut it off?
Of course you say this right after I order an ECU flashing cable!For anyone interested, I bumped into this other GitHub project a while ago: https://github.com/fjvva/ecu-tool
and completely forgot about it until yesterday. It's a hardware project to read and flash EDC15 ECUs, sort of like a poor-man's FlashZilla/QLoader. All the source code to talk to the EDC15 is included in the project and it looks like it might not be that hard to merge it into kw1281test. No hardware would be needed other than a KKL cable and a laptop. I'll give it a whirl when I get time.