TephraMOD V6 - testing!
Well i gave another shot at v7.5 and have a better log. It did the same thing as last time, but i held it longer and at wot. Here is the link. http://www.mediafire.com/?sharekey=a...4e75f6e8ebb871
When You look at the part of the log where I am wot, you can see that my rpms don't climb over 3500.
And just for the hell of it, I flashed v5.10. Took it for a spin and it ran perfect.....I don't understand
When You look at the part of the log where I am wot, you can see that my rpms don't climb over 3500.
And just for the hell of it, I flashed v5.10. Took it for a spin and it ran perfect.....I don't understand
Last edited by tom04841; May 12, 2009 at 05:50 PM.
I still can't read your load for some reason even though I've switched to 1byte load now and it works fine reading my logs.
Except for your quick spike it looks like you are bouncing off a rev limiter. What is your NLTS set at? Are you an automatic or a manual? What about stationary rev limit? Would you check your moving rev limit just for ****s and giggles? If you are a manual try pulling the wires on your clutch switch(es) and/or changing the rev limit for NLTS.
I have an automatic and I have also turned off NLTS, I have no idea what sort of behavior I might witness if it wasn't off.
Except for your quick spike it looks like you are bouncing off a rev limiter. What is your NLTS set at? Are you an automatic or a manual? What about stationary rev limit? Would you check your moving rev limit just for ****s and giggles? If you are a manual try pulling the wires on your clutch switch(es) and/or changing the rev limit for NLTS.
I have an automatic and I have also turned off NLTS, I have no idea what sort of behavior I might witness if it wasn't off.
I still can't read your load for some reason even though I've switched to 1byte load now and it works fine reading my logs.
Except for your quick spike it looks like you are bouncing off a rev limiter. What is your NLTS set at? Are you an automatic or a manual? What about stationary rev limit? Would you check your moving rev limit just for ****s and giggles? If you are a manual try pulling the wires on your clutch switch(es) and/or changing the rev limit for NLTS.
I have an automatic and I have also turned off NLTS, I have no idea what sort of behavior I might witness if it wasn't off.
Except for your quick spike it looks like you are bouncing off a rev limiter. What is your NLTS set at? Are you an automatic or a manual? What about stationary rev limit? Would you check your moving rev limit just for ****s and giggles? If you are a manual try pulling the wires on your clutch switch(es) and/or changing the rev limit for NLTS.
I have an automatic and I have also turned off NLTS, I have no idea what sort of behavior I might witness if it wasn't off.
how about it guys is p0505 involved in t706?
I was getting the P0505 code, I set my idle screw and everything and still got it.
Since then I have set Periphery2, bit 08 (idle test) to 0 and haven't seen that code come up yet. I haven't driven the car a lot (about 10 miles) but I still haven't gotten the code....
Since then I have set Periphery2, bit 08 (idle test) to 0 and haven't seen that code come up yet. I haven't driven the car a lot (about 10 miles) but I still haven't gotten the code....
Sorry if you have mentioned it already, but have you set the BISS using the SAS mode in EvoScan? I have been using the 96530006 ROM in place of 96940011 and never threw a cel with it.
Now that I have the Periphery bit set I have not gotten it yet....
That's interesting then. Wonder why some have the issue and some don't then.
What about the other ISCV tables and idle tables? Did you copy them from your old ROM or leave the stock 9653 tables in place. I left the stock 9653 tables in there. Maybe that has something to do with it?
Anyway, using the periphery bit you mentioned should keep the cel from coming on, but I'm still curious why the cel only comes on for some people.
What about the other ISCV tables and idle tables? Did you copy them from your old ROM or leave the stock 9653 tables in place. I left the stock 9653 tables in there. Maybe that has something to do with it?
Anyway, using the periphery bit you mentioned should keep the cel from coming on, but I'm still curious why the cel only comes on for some people.
That's interesting then. Wonder why some have the issue and some don't then.
What about the other ISCV tables and idle tables? Did you copy them from your old ROM or leave the stock 9653 tables in place. I left the stock 9653 tables in there. Maybe that has something to do with it?
Anyway, using the periphery bit you mentioned should keep the cel from coming on, but I'm still curious why the cel only comes on for some people.
What about the other ISCV tables and idle tables? Did you copy them from your old ROM or leave the stock 9653 tables in place. I left the stock 9653 tables in there. Maybe that has something to do with it?
Anyway, using the periphery bit you mentioned should keep the cel from coming on, but I'm still curious why the cel only comes on for some people.
Now that I have set the periphery set I hope the code stays away.....
Actually, when I adjusted the BISS, I forgot that the ISCSteps take a long time to adjust downwards, so I actually adjusted the BISS so that idle was below my target idle. I forget the exact number I used.
I think my idle in my ECU is set at 850 or 900 (have to check my ROM). I actually set the BISS slightly lower than that. I was going to fix it up to my ECU value, but it drives fine, doesn't throw a CEL, so I left it as is. I did adjust it to be higher than it was (almost stalling in SAS mode).
I think my idle in my ECU is set at 850 or 900 (have to check my ROM). I actually set the BISS slightly lower than that. I was going to fix it up to my ECU value, but it drives fine, doesn't throw a CEL, so I left it as is. I did adjust it to be higher than it was (almost stalling in SAS mode).



