Knock sensor doesn't work that way. It's a microphone. The ECU processes the audio to listen for knock.
I understand the knock sensor is essentially a microphone, but I though the signal from the microphone was processed and converted to a voltage before it ever reaches the ECU.
Interesting. If that's true, there goes that idea.
Advertisement
To browse the forums without the advertisements above, Login/Register
I understand the knock sensor is essentially a microphone, but I though the signal from the microphone was processed and converted to a voltage before it ever reaches the ECU.
No it's a raw sensor with possibly an amplifier. While the amplitude varies it's the processing the ECU does on the frequencies received looking for the sounds of knock at the right times to be knock.
But we now have control over internal ECU calculations and outputs so why can't we take a look at 2g code that makes the boost gauge work for knock and just borrow the output structure then all that we would have to do is get the knock count exported to an already existing function.
I'm not really a programmer so I'm not sure how hard that would be but it seems more useful than straight knock voltage which would never mean anything except to verify that the engine is running.
But we now have control over internal ECU calculations and outputs so why can't we take a look at 2g code that makes the boost gauge work for knock and just borrow the output structure then all that we would have to do is get the knock count exported to an already existing function.
This is what we do on the other DSM ECUs but I'm not convinced that you (ie. most people) have the needed "control over internal ECU calculations and outputs" yet. Your on the right track but I don't know very many people who can actually write code for this CPU and have disassembled the stock code to know where to get the correct places are to do this.
Does the code that people are basing this conversion on support a boost gauge?
Evoscan supports warnings for knock so you can set a switch for say 0-3 counts of knock and your computer will say "engine knock detected". You can make it say basically anything for a switch as long as you have the audio file. You could make it say something like "unicorns detected in filters" for example.
Evoscan supports warnings for knock so you can set a switch for say 0-3 counts of knock and your computer will say "engine knock detected". You can make it say basically anything for a switch as long as you have the audio file. You could make it say something like "unicorns detected in filters" for example.
True, but this requires you to have a laptop on in the car running EvoScan. It would be really convenient if there was a way to trigger a switch in EcuFlash, kind of like the way you can trigger your CEL to flash with DSMLink with a user-defined knock level. This way you could always be aware of knock, even if you don't happen to have a laptop on you.
There is a way to do a CEL with a certain amount of knock on an Evo...
but I haven't tried it and definately haven't tried it on an Evo ecu in 2g.
Anyway there's a guy in Austraila that is very good at coding and patching for Evos. His stuff is on evolutionm () but a lot of evos are running around on his stuff. His name is tephra and here's the thread; PATCH: NLTS + Valet + KnockCEL - evolutionm.net
Like I said I haven't tried it, but a brainiac could take a look at the code and maybe make it work.
I don't know what ROM you're running and I don't even know if you could switch to another VIII ROM and still run it on a 2g, but this is really exciting stuff and it makes me want to scoop up a 2g gsx.
There is a way to do a CEL with a certain amount of knock on an Evo...
but I haven't tried it and definately haven't tried it on an Evo ecu in 2g.
Anyway there's a guy in Austraila that is very good at coding and patching for Evos. His stuff is on evolutionm () but a lot of evos are running around on his stuff. His name is tephra and here's the thread; PATCH: NLTS + Valet + KnockCEL - evolutionm.net
Like I said I haven't tried it, but a brainiac could take a look at the code and maybe make it work.
I don't know what ROM you're running and I don't even know if you could switch to another VIII ROM and still run it on a 2g, but this is really exciting stuff and it makes me want to scoop up a 2g gsx.
AWESOME!!!!
Thanks so much for sharing. It all actually looks fairly straight forward and simple, up until the immobilizer part. I will play around with this and see if i can get it working.
There is a way to do a CEL with a certain amount of knock on an Evo...
but I haven't tried it and definately haven't tried it on an Evo ecu in 2g.
Anyway there's a guy in Austraila that is very good at coding and patching for Evos. His stuff is on evolutionm () but a lot of evos are running around on his stuff. His name is tephra and here's the thread; PATCH: NLTS + Valet + KnockCEL - evolutionm.net
Like I said I haven't tried it, but a brainiac could take a look at the code and maybe make it work.
I don't know what ROM you're running and I don't even know if you could switch to another VIII ROM and still run it on a 2g, but this is really exciting stuff and it makes me want to scoop up a 2g gsx.
K, I just tried these patches out. I was able to get EcuFlash to recognize and display the new features like the CEL knock light and the valet mode option by tweaking the XML file. However, the base "hacked" ROM he provides as a template does not have the immobilizer disabled. Therefore, when I flashed the new ROM to my car, the car wouldn't start (which is what I expected). I tried PMing tephra but his inbox is full.
If there is anyone out there who knows how to edit a hex file, all we need to do is compare the immobilizer code from the hex file on my base
ROM (that has the immobilizer disabled) to the hex file that tephra provided as a template ROM for all those awesome extra features, tweak some code, and everything should work.
Any takers? I've never edited a hex file before, but I'll take a stab at it if there is no one else willing.
He gave up on trying to keep up with PM's and I don't blame him because everyone is always asking him for help.
There is a way to disable the immoblizer.
Which ROM are you using?
He gave up on trying to keep up with PM's and I don't blame him because everyone is always asking him for help.
There is a way to disable the immoblizer.
Which ROM are you using?
I'm using the ROM he includes in the zip file on the forum link you posted above. If I knew what the hex address was for the immobilizer, it may not be too difficult.
I'm also using the ROM metadata XML file in his zip file as well. I tried typing in "FFFF" in EcuFlash to disable the immobilizer, but that didn't work.
If there is anyone out there who knows how to edit a hex file, all we need to do is compare the immobilizer code from the hex file on my base
ROM (that has the immobilizer disabled) to the hex file that tephra provided as a template ROM for all those awesome extra features, tweak some code, and everything should work.
Any takers? I've never edited a hex file before, but I'll take a stab at it if there is no one else willing.
According to the post, it's the same for all EVO ECU's (except maybe the new X's).
I was able to get in touch with a guy from the OpenEcu forums that has experience disabling immobilizers, so he's taking a look at it my new Tephra ROM for me. Hopefully I should have some results in the next few days.
wow dave, you took this and ran with it. Im impressed.
Thanks Sam. I wouldn't have made it this far without your help with getting the car running initially.
I Just bought a new clutch, and I'm looking into larger injectors now. When all that is done (hopefully in the next 1-2 months), I'll be calling you for a final tune.
I just want to make sure I am on the right track here with this. I picked up an ECU from a guy on evolutionm.net but i am waiting for my cable to come in from limitless.co.nz before i start the swap.
On a 96GST I will either have to install a CAS at the back of the head or change the firing order by either swaping the plug wires or switching the pins at the ecu for the power transistors... correct?
A new member on here named Diiirk had some input on this thread but wasnt able to post in this thread so he was asking for someone to post this information on here for him. why cant i post yet. help.
Ok guys, did the swap today. Flashes, starts up but the tach is screwy jumping around and here is whats bothering me the most. I turn the key OFF and take it out with the TT off and the car doesnt stop running. The ignition wires for the 2g and evo are the same so theres no reason why it worked before but not now after the evo ecu is in. Anyone have any ideas??
Another thing, I broke the ecu pin for the fuel pump relay and never hooked it up. But the thing is, I have the fuel pump hooked up to a hardwire/switch so I didnt think I'd need to hook that pin up for the evo ecu. But would something in the circuit cause a problem and still need it to be hooked up even if its not in use?
I just did the swap on my 2g. After installing the Evo ecu and swapping the necessary pins
(mainly pin 79 which is the flash port), I can't read or write to the evo ecu. I can log with evoscan tho.
At first I installed ecuflash 1.4, but as soon as i tried to read the ecu, ecuflash would
crash. I then uninstalled 1.4, and installed 1.29a. I am able to attempt a read without
crashing. It goes thru 3 init sequences, but i end up getting and error of "no
response to any known code". I even tried running ECU Unlocker in the background
before opening ecuflash....still same error, but with one more init sequence.
I have spent the last 2 days searching the net, openecu.org, and aktivematrix. Some have
has cable issues, some haven't. I just need to get this working one way or another so I
can flash a rom to the ecu with the immobilizer disabled so I can actually start the car.
Try reading that thread, it was the first one that came up when I put the error in the search terms at evolutionm.net but there are a bunch more if that doesn't answer your questions. From my reading it sounds like there could be a problem with your in car flash connector, you could be using more than one program that accesses the cable, or you could have a problem with your cable.
No flash connector. I added a pin in the ecu harness at pin 79 and wired it directly to the flash wire coming off my openport cable. I only installed ecuflash on my brand new laptop so there wouldn't be any possible conflicts, and still nothing
Has anyone had problems with the tach bouncing around? I know the car isnt tuning nearly to where its supposed to be but at idle the tach drops to 0 then back up to 1000 then back to 0 every once in awhile. Im having weird problems haha, but the flashing and start up is flawless
Also for my other problem, Im going to try hooking up that fuel pump relay wire again. Im thinking even though it has a hardwire, the ecu/car needs it to shut the car down. I don't know why but I'll give it a shot, its an easy fix if it is...
I know others are having minor problems with the tach but AFAIK no one else is having problem with shutdown. You could possibly be dieseling but it seems unlikely.
) but a lot of evos are running around on his stuff. His name is tephra and here's the thread;
