|
Title: Checksum fixing Post by: shuffled on July 23, 2015, 05:01:29 AM Hi guys,
I've been reading this thread from front to back a few times while I was waiting for my cable to flash my A box to an M box in my 2.7t swapped b6 to fix a bunch of my check engine lights. Which worked and I successfully passed emissions test in Ontario. My problems are coming when I used daz's supplied Mbox with Bosch MAF file on page 3(the stock file he modified for Bosch checks out fine with me7check), with the nefmoto stage 1 xdf for tunerpro, but even when I make a simple modification like RPM increase it comes up with the "64 errors" stuff and won't repair the file. Is that not the right xdf to use to modify that bin? Any help is appreciated, my car will be on the road and after some basic datalogging, I'll start making changes to push this thread along. Thanks, Josh Title: Checksum fixing Post by: therealnap0le0n on July 23, 2015, 05:29:00 AM Hi guys, I've been reading this thread from front to back a few times while I was waiting for my cable to flash my A box to an M box in my 2.7t swapped b6 to fix a bunch of my check engine lights. Which worked and I successfully passed emissions test in Ontario. My problems are coming when I used daz's supplied Mbox with Bosch MAF file on page 3(the stock file he modified for Bosch checks out fine with me7check), with the nefmoto stage 1 xdf for tunerpro, but even when I make a simple modification like RPM increase it comes up with the "64 errors" stuff and won't repair the file. Is that not the right xdf to use to modify that bin? Any help is appreciated, my car will be on the road and after some basic datalogging, I'll start making changes to push this thread along. Thanks, Josh There is a gui for ME7checker called me7checkergui . look for that and follow the instructions to check and fix the file. Any time you modify the .bin you will need to check it then fix it. Both steps have to have 100% of the time. The GUI makes this very simple with an easy to use interface. Title: Re: Checksum fixing Post by: nyet on July 23, 2015, 11:33:05 AM See my sig for checksum utility. Please don't clutter the tuning thread, thanks :)
Thread split from http://nefariousmotorsports.com/forum/index.php?topic=6695.0title= Title: Re: Checksum fixing Post by: shuffled on July 23, 2015, 01:21:22 PM Sorry about that,
I will post up the full output that the utility gives me tonight when I get home. I re-read that link just in case I missed something blatant, I will re-read it again. Title: Re: Checksum fixing Post by: nyet on July 23, 2015, 01:26:29 PM Also this
http://nefariousmotorsports.com/forum/index.php?topic=3347.0title= Title: Re: Checksum fixing Post by: shuffled on July 23, 2015, 03:43:37 PM So, I ran the me7check.exe against daz's bin that I was using, and it came out ok:
Code: ME7Check v1.12 (c) mki, 06/2004-05/2012 But when I ran it against me7sum it failed in the same way that my bin failed, something I might have overlooked previously: Code: *** Found 73 checksums in 551M Bosch.bin I have not had any problems with the car starting or driving, granted I have unplugged the battery terminal right now as I'm working on some fan wiring. I drove it for approx 2 hours on Wednesday night without issues. Title: Re: Checksum fixing Post by: nyet on July 23, 2015, 04:42:26 PM Looking into it now..
For ref http://nefariousmotorsports.com/forum/index.php?topic=6695.msg62391#msg62391 Title: Re: Checksum fixing Post by: nyet on July 23, 2015, 04:45:34 PM Definitely something screwy with that bin, I'll have to talk to daz about it.
Title: Re: Checksum fixing Post by: ddillenger on July 23, 2015, 04:52:36 PM Updated the original post. Looks like it may have been the read protection. My apologies. It snuck by me.
Title: Re: Checksum fixing Post by: shuffled on July 23, 2015, 05:11:07 PM Lol so I'm not insane.
I could have started out with the basic mbox file and do the mods, but why reinvent that wheel. Thanks a bunch everyone. |