pcmhacking.net

Tazzi wrote:

rolls wrote:I'll set the timeout to 5 seconds, currently they are about a second. BA seems to be about 5-10x slower than the BF which is interesting.

Perfect. Plenty of wiggle room for the BA that way.

Yeah the BF erase takes about 5 seconds, the BA takes almost 40 seconds.

I'm putting in a bunch more debugging when errors occur so you can tell exactly what routine failed and what packet was begin sent (or was not received that it expected).

Hopefully that helps Frankys PCM recovery.

rolls wrote:

Tazzi wrote:

MeZmeriZe wrote:well I've bricked two PCM's now, a BA turbo and an FG.. The BA was probably due to me trying to log the write, but the FG one was by the book and had the exact same error.

Tried using VCM yet?

Might need to get a separate CAN sniffer up and running.. and see exactly where it fails. Makes it easy to diagnose any issues such as what I was getting before without FEPs

Think he only has a Mongoose and a VCX which doesn't have FEPS

Either way should be able to figure it out, at least with the new version it'll say exactly what packet it sent last when it times out. Curious if it gets any reply at all, if it doesn't then it would be bricked but I have no idea how as I can't brick either of mine even when I'm trying to! Tried pulling power during erase and the flash write, writing all zeros, FF etc but no dice it won't die! Lol

Maybe the mongoose does something interesting with the packets when they are sent but not when it reads. Quite lost as to what it would be doing differently as the flash read works fine.

Curious, have you loaded the flash read in a binary editor? Is it actually read successfully, it isn't corrupted etc? I guess it didn't even write one single block successfully though so I doubt that is the issue.

Nope, I've wasted way more money than that..

I have two of these too:


They were both bought from a time when I really really needed to do a lot of PATS resets for people.. (I got into all this to stop people getting ripped off thousands from Ford franchies and mechanics with 2500 dollar quotes for column replacements.) so I bought these after the mongoose because back then I'd have to pay 30 bucks for a 3 day FMP subscription every time I needed to do one. The VCM's don't need that.

Ironically, 6 months after that they added PATS to forscan and now anyone with a laptop and a 4 dollar ebay bluetooth OBD2 adaptor can do pats resets. (and steering calibrations etc)

So the VCM's set in the cupboard idle as I hate using them.. big bulky fragile and IDS/FMP looks like it was designed by an 8yo to be used by 4year olds.

They run a linux system, was on my list of things to do to try messing with that.. the possibilities are interesting to having Linux with all the relevant drivers already in place..

I thought with FORScan to do pats & steering calibration you have to pay for some sort of licensing too?

VX L67 Getrag wrote:I thought with FORScan to do pats & steering calibration you have to pay for some sort of licensing too?

nope, unless it's changed, the extended license is free.
http://forscan.org/forum/viewtopic.php?f=5&t=836


just read though and nothing has changed.. every 2 months you'll need to go back and do it again.. but no biggie and still doesn't cost anything. I've done it about 30 times now.

Ok so I found an issue that may or may be related to your problem. As tazzy found with the canbus sniff tester present was getting a not supported response at times. I've put more thought into when I enable and disable it. It appears it was sending a reply to tester presentable up to 5 seconds after I last sent it causing an error in a mode other than the one I was expecting.

Seems much more robust now, it could do with some more tweaks though so I'll only send this version to franky to see of it gets his pcm going.

The funny thing is I never have to use recovery mode now. My BF pcm will even take a fg tune and hold it on power reset now, not sure what I did to make that work. I did add ecu reset at the end of a download that I didn't have before.

Something else, if the PCM is blank and in recovery mode it doesn't appear to require FEPS to program it, only found this on the BA PCM. Strange.

Ok Franky I just sent you a new version. 5 second timeouts, no tester present message pump unless its required and better logging of the errors so it is more specific where it is failing and what response it got vs what it expected.

rolls wrote:.

The funny thing is I never have to use recovery mode now. My BF pcm will even take a fg tune and hold it on power reset now, not sure what I did to make that work. I did add ecu reset at the end of a download that I didn't have before.

Have you tried running a ECU that you have done this with, that would be a great thing to have if it worked, would make getting the ecus so much easier.
is this on the 2.0 release?

Yesterday I found some time to try it out and I cloned my BA ecu with the tactrix.
Both BA ecu's wouldn't show the VIN on the vehicle information tab but it shows the VIN ok under the flash toolbox tab; detect vehicle.
I'm very happy now I have a spare ecu for my ute with the pats disabled.
I haven't tried the update yet.

I have a innovate mtx-l wideband gauge with bosch lsu 4.9 sensor & a Innovate ssi-4 as well that I would like to get working with the tactrix too.
Its pig rich at anything above 50% throttle. Needs a remap big time.
I'm looking forward to being able to tune it in the near future.
I was going to use logworks to tune the fuel table.

Thanks again rolls!
Awesome stuff!

rolls wrote:Ok Franky I just sent you a new version. 5 second timeouts, no tester present message pump unless its required and better logging of the errors so it is more specific where it is failing and what response it got vs what it expected.

Can you fire that one on through as well Rolls. Im having to attempt reading a few times before it gets it in one go.

I'll log at the same time and see if there any other hickups occurring.