I just download a difffernt rom, v7 96531706. What changes do I make to it for the spoolinup harness and omni 4 bar? Im not talking about the tuning tables, I know what to do there.

 

Cam sensor OK?

 

I believe so, its the same one I was using before when I didnt have this issue. Same goes for all sensors, execpt the tps but I highly doubt its causing this. And well the omni 4bar and gm iat.

Still havnt found the intake for the maf.

 

ok so I think it is either the cable as mensioned or the ecu itself. As I cant even connect to flash the ecu anymore, I get:

[16:41:37.254] Using interface OpenPort 1.3 Universal TX2AEkWNd2733ff1054babb2c9199edd3295a5e31603b7c9
[16:41:39.212] sending init sequence 1 (0001)
[16:41:42.415] sending init sequence 1 (0003)
[16:41:45.618] sending init sequence 1 (FFFF)
[16:41:48.321] no response to any known code
[16:41:48.321] interface close

And to make it worse I can start the car anymore as it was in the process of flashing a rom.

 

do i have to go out to my car and set the knock sensor back to stock to prove it to you? my cable works fine also. I'm just telling you what it shows.. why would it lie? The cable clearly works fine, i use it all the time. Infact I have 2 tactrix cables and both did the same thing, and evoscan works fine.

Do you have any kind of disassembly of the 94170015 ROM to prove the knock threshhold is 36? Where did this number come from is what i want to know. Have any decompiled code to show?

Im not argueing, im just curious. equipment aside, my stuff works.. so do not point fingers at that.

 

Want to sell the extra cable?

 

well is the car cranking? if you loaded another rom and did not transfer over the immobilizer code it will not start. also the ecu will disable any kind of flashing to its memory if a certain voltage level isnt seen from the battery. I guess they do this incase of hope to stop corrupted flashes.

 

no because i use it for flashing. sorry. I have a older tactrix cable and then a newer one. the older one doesnt blink the ABS light and the newer one does. The older one doesnt flash anymore though, but the newer one does, so i use them both. ignore the knock ........... but the 2000 load you mentioned? that ive never seen ever.. the only time ive ever seen load go nuts is when the 1byte to 2 byte conversion isnt set properly and the load blacks out on the log.

 

It has to be the cable I started evoscan with the key "on" and everything was going crazy. The car wont crank, could be the battery causing that, Im gonna throw the charger on and see if it starts.

 

When a battery reaches a certain voltage and is unable to provide the car with proper voltage everything will go nuts. its common electronic behavior. is it clicking like crazy when you try to start it up? just give the battery a full charge and start over. if its still going nuts then its the cable in your case. my new redtop makes my alarm go nuts after 2 weeks of sitting outside in 30F.

 

Yes, it absolutely has been disassembled and proven a very long time ago. I'm not just making it up.

If you're logging more than 36 counts of knock, then you're either using an incorrect scaling, longing and incorrect address, or something else like the cable (which isn't your case as you mention).

 

No clicking, thats why I wasnt thinking the battery was low/dead.

 

do the lights turn on? turn the lights on then try to crank it and see if they dim out. i hope the ecu is ok.

 

alright, well cant argue with code. i will blame it on evoscan then

 

Like l2r99gst, I don't pluck random 36's out of the air and make stuff up... do a search yourself.