Slo_crx1

BRE Forum on PGMFI
http://forum.pgmfi.org/viewforum.php?f=36

OBD0 VTEC Forum on PGMFI
http://forum.pgmfi.org/viewforum.php?f=14

Ben Ogle's ROM Editor Site READ ME
http://www.ef-honda.com/ben/bre/maindoc/index.html



Been playing around with the willem burner I got off here a couple days ago, and I figured I'd like to take the chip out of my ecu that's currently in there for my old boosted setup and just burn a stock pr3 bin onto a new chip with a fuel adjustment for 450's since I'm feeling lazy and don't want to take them back out again. I got the map adjusted for the 450's no problem (duh :1) and it has vtec set to turn on at 4804 rpm's on the stock bin. Burned the bin onto a SST27SF512 chip, popped it into my socketed pr3 and tried it. No solid cel, car seemed to do ok on quick runs so I thought nothing of it. Well, I drove it to work this morning and noticed that vtec wouldn't activate until almost 6k, and it seemed very doggy on the bottom end, much more so than my old 29c chip with some timing taken out and fuel added. So tonight I figured I'd read the chip and open it in BRE to see what's going on with it. Read the chip fine, saved it, went to open it with BRE, and nothing...tells me it's an invalid bin file...wtf is this? I read my old 29c's bin, and it would open it just fine...what am I doing wrong here? Oh, and I'm using the Willem program 0.97g, don't know if it will make a difference. And yes, I set all my jumpers and dip switches correctly and used the 8000 hex offset and the PCB3 setting that I read to do. Even tried 0000 offset and no luck.

Slo_crx1

Also just tried opening the test bins in TE, Uber, and Crome...no luck, none of them will read it.

*Edit: Just found out something interesting...original bin is 32k, the file being saved from the Willem is 64k. If I can find a way to reduce it back down to 32k it might work.

Chris Harris

use 08000 and 0FFFF as your offsets so it only takes 32k of data when it reads the upper half of the SST chip...

Slo_crx1

Please explain?...I'm using the 0x8000 offset (typed 8000 into the offset box in the program) and it still comes up with 64 bit on the read. Maybe I should just get the 256 chips instead if it'll make a difference.
I did run across an article on HT about someone who ran into the same problem. He said he deleted all the "y"'s (which is blank space anyway from what I can gather) before the actual section of code and it came up as 32bit on the save. I tried this, and it works, only problem is it now sits in .txt format instead of .bin format. I'm going to take a guess and say that you can't really read burns on the SST27sf512's unless you can copy and paste in a hex editor.

Slo_crx1

*Update: Hex editor trick works...came up in BRE normally. Only thing I still can't figure out is why vtec engagement was so high when the bin file says 4804 engagement and 4576 disengagement. I'll try the chip again tomorrow and see what happens...maybe I had the dip switches set wrong. :P

udaredme

which version of BRE are you using?

Slo_crx1

Newest version now...2.2.4b2 beta. Lost my old copy when I had to wipe my HD.

udaredme

you could try going back one release. Ive had a few issues with tuning on the newest release..which details are in the BRE forum on pgmfi.org...

Chris Harris

Yeah, had issues with the latest Beta as well...but I dont use BRE enough to keep up with it

udaredme

working with the ostrich and the autotune functions..works well except it automatically leans out at idle..so bad it'll cut off..if youve read the posts on pgmfi youll see...i sent ben the datalog of it acting up..he thinks its o2 disable related..but that hasnt changed anything..