rolls wrote:I've seen it but I don't have an MSC eepod to test with. Looked into trying to get the software to work with a J2534 cable however I didn't get very far. The exe seems to export all of the J2534 library functions and the eepod msc1 supports J2534 however it looks as though they talk a proprietary serial protocol to the device. Without actually getting one would be too much work to write an intermediate driver that translates it back to J2534 and if you counted your hours by the dollar probably cheaper to just buy an MSC1. One nice thing is ptDiag seems to have been written in C with minimal optimisation/no obfuscation many many years ago, this makes the ASM code extremely readable compared to recent C++ programs which are close to impossible to follow the ASM these days.Tazzi wrote:Played around with PTdiag's PATS functions? Might be of help there?rolls wrote:If you can get me the binary of the ECU I can tell you where the PATS bit is but I personally have not disabled it and I've been told there are other things that need doing as well as switching it off in the ECU.
I know there is a bloke I was talking to who is buying one though, so might be interesting to see what it turns up on the sniffer during a PATS disable if he still gets it.
I have the msc1 and was testing ptdiag on the bench with a few ecms. Mostly diesel stuff a 6.0 great oak and a 6.4 Powerstroke Siemens ECM. If you want I can hook it up on the bench and you can TeamViewer in to check it out if you like.