TephraXMOD V1
It is not too difficult but every minute of your time spent on the interface unlocks a geat deal of new power potential, safely.
I just switched my buddy's EvoX to Tephramods V1 yesterday. However, I noticed that his CEL would flash when Evoscan wasn't picking up any knock. The only time it would pull timing is when Evoscan read the knock, so I'm assuming Evoscan is the correct one. He came from rom 52680020 and I switched him over to 52680122. Anyone know why this is happening?
I'd question the knocklite as well...I was getting it all the time on spool up but everytime i logged the car...nothing. However, typically while logging for some reason I couldn't get the light to pop on, so I still treated the knockcel as bad and let off when I saw it. Not sure if the knockcel is set too sensitive or what.
I'd question the knocklite as well...I was getting it all the time on spool up but everytime i logged the car...nothing. However, typically while logging for some reason I couldn't get the light to pop on, so I still treated the knockcel as bad and let off when I saw it. Not sure if the knockcel is set too sensitive or what.

I have a 40,000 sample log from a drive yesterday....
I borrowed Scheides stand alone logger and that is what I did some of my logging on. It seems like it only wants to knock when i am not logging, lol.
I would question my fueling setup or something i guess before Tephras Mod especially since I have never seen the knocklite and not seen knock in evoscan yet.
So I guess I am not sure why I even commented, lol. Was just a random though
I would question my fueling setup or something i guess before Tephras Mod especially since I have never seen the knocklite and not seen knock in evoscan yet.
So I guess I am not sure why I even commented, lol. Was just a random though
Thread Starter
Joined: Feb 2007
Posts: 9,486
Likes: 67
From: Melbourne, Australia
either...
keep in mind that knockcel pics up events 100 times a second.
evoscan only does 10 a second (assuming you are logging a few things)
knock events can come and go quickly...
what are you settings?
keep in mind that knockcel pics up events 100 times a second.
evoscan only does 10 a second (assuming you are logging a few things)
knock events can come and go quickly...
what are you settings?
I am not sure on mine, I'd have to ask my tuner. Mine always seems to happen on spool and it cleans up after 5.5k-6k...I have had both slow and fast, mostly slow though, only had fast a few times.
I have a vid that shows it at the end, but it will get deleted again if I post it as I was going too fast for EvoM i guess
I have a vid that shows it at the end, but it will get deleted again if I post it as I was going too fast for EvoM i guess
I have low flash at 3 counts and fast flash at 5 counts...1000 milleseconds duration.
I'm not sure how similar the Evo8, 9, and 10's are, but when I tune for Evo8's and 9s, the CEL and Evoscan logger corresponds very well.
Thread Starter
Joined: Feb 2007
Posts: 9,486
Likes: 67
From: Melbourne, Australia
I set the load to 40 originally, but then upped it to 100 since we were getting the light showing so much down low.
I have low flash at 3 counts and fast flash at 5 counts...1000 milleseconds duration.
I'm not sure how similar the Evo8, 9, and 10's are, but when I tune for Evo8's and 9s, the CEL and Evoscan logger corresponds very well.
I have low flash at 3 counts and fast flash at 5 counts...1000 milleseconds duration.
I'm not sure how similar the Evo8, 9, and 10's are, but when I tune for Evo8's and 9s, the CEL and Evoscan logger corresponds very well.
K, I'll try tonight. One way to get the knock to light up really easily is if you floor it on a higher gear at a very low rpm. That or floor it quickly--rolling on the throttle doesn't really do it.
On the dyno it never knocked which is the weird part. We had det cans on it and had people listening at the motor and running logs...nothing...just the street...it is frustrating. I will get it checked out this spring when it comes out of storage for sure though.









