got my rom burner and datalogging stuff, having some issues...
07-03-2005, 06:21 PM
#1
0.5 BAR
Thread Starter
Join Date: Jul 2005
Posts: 148
got my rom burner and datalogging stuff, having some issues...
ok well the other day i got my rom burner and datalogging stuff from -------------. very good prices and service btw, the owner has been very helpful 
.
anyway i picked up the willem dual power rom burner. seen here:
now the first problem im having is erasing a chip thats already been burned. the chips im using are the SST 27SF512 chips. i know these are eraseable. when i try to erase them, the burner tells me something about the jumpers and something about 12.75V. im guessing i need the AC adapter hooked up? also it doesnt tell me what jumpers to change or how to arrange them, just that they need to be moved.
next problem im having is with the rom burner burning the chips. now this could be an issue with uberdata or something too but i dont know. ive tried burning a few chips just to test it out and make sure im doing it right. i burned a stock gsr map and disabled the knock sensor (because im using a p2
and disabled closed loop (because i want to datalog). well i popped the chip into the ecu and turned the key to ON to check it before starting the engine. cel stays on. i go to check it and its just solid, great. i start the engine and it almost doesnt want to start, but does without much hassle. idle is pretty rough. revving it up i can see and smell smoke from the exhaust and it back fires pretty good, so im guessing the solid cell is causing it to dump tons of fuel and retard timing. so i try another chip same stock gsr map, except i left the closed loop on and still disabled knock sensor. put it in, same thing.
onto datalogging issues.
im using uberdata 1.7. i first tried to dataloglog with my chip that i had burned for me from a guy on h-t. i have no idea what program he used or what kind of chip hes using so i couldnt really copy the map off the chip. i hooked up the cable and it just gives me rediculous numbers. it does the same exact thing with the cable completely unhooked so maybe its just an issue with my port settings? i dont think its a problem with my soldering job, it looks fine to me. ill let you be the judge
any help is appreciated. also i dont know what the ---- is with http://uberdata.pgmfi.org but i cant log on for the life of me. ive tried making a new username for the longest time but it keeps just giving me an error. its so frustrating, cause i wish i could post this there.
. anyway i picked up the willem dual power rom burner. seen here:
now the first problem im having is erasing a chip thats already been burned. the chips im using are the SST 27SF512 chips. i know these are eraseable. when i try to erase them, the burner tells me something about the jumpers and something about 12.75V. im guessing i need the AC adapter hooked up? also it doesnt tell me what jumpers to change or how to arrange them, just that they need to be moved.
next problem im having is with the rom burner burning the chips. now this could be an issue with uberdata or something too but i dont know. ive tried burning a few chips just to test it out and make sure im doing it right. i burned a stock gsr map and disabled the knock sensor (because im using a p2
and disabled closed loop (because i want to datalog). well i popped the chip into the ecu and turned the key to ON to check it before starting the engine. cel stays on. i go to check it and its just solid, great. i start the engine and it almost doesnt want to start, but does without much hassle. idle is pretty rough. revving it up i can see and smell smoke from the exhaust and it back fires pretty good, so im guessing the solid cell is causing it to dump tons of fuel and retard timing. so i try another chip same stock gsr map, except i left the closed loop on and still disabled knock sensor. put it in, same thing.onto datalogging issues.
im using uberdata 1.7. i first tried to dataloglog with my chip that i had burned for me from a guy on h-t. i have no idea what program he used or what kind of chip hes using so i couldnt really copy the map off the chip. i hooked up the cable and it just gives me rediculous numbers. it does the same exact thing with the cable completely unhooked so maybe its just an issue with my port settings? i dont think its a problem with my soldering job, it looks fine to me. ill let you be the judge
any help is appreciated. also i dont know what the ---- is with http://uberdata.pgmfi.org but i cant log on for the life of me. ive tried making a new username for the longest time but it keeps just giving me an error. its so frustrating, cause i wish i could post this there.
07-03-2005, 06:43 PM
#2
Guest
Posts: n/a
Re: got my rom burner and datalogging stuff, having some issues...
First, when burning that chip you need to have the offset set at 8000 because it is twice as large as the 256 chips.
When erasing, it will say something like "Set jumper to W27" or some crap like that. If you look on the pcb of the burner itself you can see about 6 or 8 different diagrams for the jumpers pictured on the board and labeled. One of them will be labeled W27 or whatever the message on your computer said. Place the jumpers like that in the picture and you can erase. You will have to switch the jumpers every time you change from burning to erasing a chip.
When erasing, it will say something like "Set jumper to W27" or some crap like that. If you look on the pcb of the burner itself you can see about 6 or 8 different diagrams for the jumpers pictured on the board and labeled. One of them will be labeled W27 or whatever the message on your computer said. Place the jumpers like that in the picture and you can erase. You will have to switch the jumpers every time you change from burning to erasing a chip.
07-03-2005, 07:24 PM
#5
Guest
Posts: n/a
Re: got my rom burner and datalogging stuff, having some issues...
When you open up the eeprom program to use the willem, there are a few fields near the lower right corner. One of them says offset. Change the 0 to 8000 and burn. No more check engine light 
Unless some other ---- is fucked up of course.
Unless some other ---- is fucked up of course.
