Mazdaedit
#376
Out of NYC
iTrader: (1)
...
Never!!!
Well, I moved outta NYC for 1/2 yr, met some people, and came across to this REALLY @#$@#$#@ nice RX-8 ! it was well kept and has lots of mods, owner selling it BECAUSE his wife wants him to get a Mini Van ...
and he just sold his Veilside RX-7 for roughy to 10K USD ... and he JUST had his engine rebuild by The ex-Knightsports lead builder last week ... mind you, the "legit" Veilside kit from Japan cost MORE than 10 grand .... does not include the new engine, new Knight Sports Turbo, etc etc ...
Never!!!
Well, I moved outta NYC for 1/2 yr, met some people, and came across to this REALLY @#$@#$#@ nice RX-8 ! it was well kept and has lots of mods, owner selling it BECAUSE his wife wants him to get a Mini Van ...
and he just sold his Veilside RX-7 for roughy to 10K USD ... and he JUST had his engine rebuild by The ex-Knightsports lead builder last week ... mind you, the "legit" Veilside kit from Japan cost MORE than 10 grand .... does not include the new engine, new Knight Sports Turbo, etc etc ...
#379
Had a play with this today . ECU was retarding timing so i tried reducing timing to prevent it without success. Decided it was not detonation but some other vibration causing it and set about playing with the above table .
20% reduction in above settings did the trick so went back to 12% and the retardation started up again. Split the difference at 16% and that got rid of it again.
Then decided to extend the retardation tables right out to redline instead of capped at 5000 per the stock maps.
This could be good news for us FI guys , maybe we can get knock protection on the stock ECU afterall !!!!!!
20% reduction in above settings did the trick so went back to 12% and the retardation started up again. Split the difference at 16% and that got rid of it again.
Then decided to extend the retardation tables right out to redline instead of capped at 5000 per the stock maps.
This could be good news for us FI guys , maybe we can get knock protection on the stock ECU afterall !!!!!!
Last edited by Brettus; 04-11-2013 at 07:00 PM.
#382
*Reducing the timing down to 4 degrees didn't prevent the retardation
*It was a nice cool day - so likelyhood of knock is low
*I couldn't hear anything untoward
*Have run same timing on old engine and did not get this retardation nearly as regularly
*New engine has stiffer mounts so ......
*My timing map is consistent with what others are running
*Last time on dyno the operator didn't detect knock till much later in rpm range - around 6000
Feel it is worth the risk based on above because Detonation events that cause a failure on FI engines are not the type of event you cannot hear. This way I can extend the tables to red line where there was previously no protection . I also increased the decrement value from 1.0 to 2.5 so if an event happens the timing is pulled quicker and previous tests have shown that the decrement table does exaclty what you expect it to.
Last edited by Brettus; 04-11-2013 at 07:45 PM.
#386
#389
Had a play with this today . ECU was retarding timing so i tried reducing timing to prevent it without success. Decided it was not detonation but some other vibration causing it and set about playing with the above table .
20% reduction in above settings did the trick so went back to 12% and the retardation started up again. Split the difference at 16% and that got rid of it again.
Then decided to extend the retardation tables right out to redline instead of capped at 5000 per the stock maps.
This could be good news for us FI guys , maybe we can get knock protection on the stock ECU afterall !!!!!!
20% reduction in above settings did the trick so went back to 12% and the retardation started up again. Split the difference at 16% and that got rid of it again.
Then decided to extend the retardation tables right out to redline instead of capped at 5000 per the stock maps.
This could be good news for us FI guys , maybe we can get knock protection on the stock ECU afterall !!!!!!
wishing I had your scale about now to fix it!
#390
I had seen something similar, but instead of reducing timing I added fuel and that seem to help alot. now its only in two places instead of 4. the two is right around 5250, and 6500rpms the first one is peak torque and the second is apv.
wishing I had your scale about now to fix it!
wishing I had your scale about now to fix it!
These are the stock maps I have . The base retard map stops at 5000 and that is where i see retard stopping on the car.
Last edited by Brettus; 04-12-2013 at 04:19 PM.
#391
Registered
iTrader: (3)
I don't think that's what base retard is. I think the ecu initially pulls 10deg below 5k and then uses knock sensing to add the timing back on the Fine learning table. Above 5K it just starts with the base maps and alters them with knock control . Above 7k it probably goes into Feedback knock control. Really wish we still had some ecu hackers they would know for sure.
Might be wrong though, just played with my new toy, and somewhere above 5k knock goes off the chart. (Maybe I need to set a larger chart.) It may be a quirk of the rotary I'll do more research.
Might be wrong though, just played with my new toy, and somewhere above 5k knock goes off the chart. (Maybe I need to set a larger chart.) It may be a quirk of the rotary I'll do more research.
#392
see the knock retard max table, it will pull -10 degree's up until 7krpms, for some reason my maps are only -5. but the car will pull timing to 7krpms, after that I think the knock sensor is ignored,
I have no idea or seen what the base knock table does or seen it work really.
I have no idea or seen what the base knock table does or seen it work really.
#393
Registered
iTrader: (3)
If it's pulling 10deg until 7k, then it's seeing enough knock to prevent it from adding timing and keep it at max retard. So if you add more timing knock retard can do NOTHING because it's already at its limit. Is this on a tuned engine or stock? If you tuned it there then it's already in the danger zone.
#394
see the knock retard max table, it will pull -10 degree's up until 7krpms, for some reason my maps are only -5. but the car will pull timing to 7krpms, after that I think the knock sensor is ignored,
I have no idea or seen what the base knock table does or seen it work really.
I have no idea or seen what the base knock table does or seen it work really.
To me this indicated that the Base map (not the max retard map) is the map that actually controls it .
Your maps being -5 could go back a few years when i was helping you out because that is the setting I've always used.
Last edited by Brettus; 04-12-2013 at 07:50 PM.
#396
Here is a log from a few days ago . The timing being pulled is 5 degrees and the decrements match the setting . It starts incrementing at the correct rate but as soon as it nears 5000 it suddenly goes to stock timing.
To me this indicated that the Base map (not the max retard map) is the map that actually controls it .
Your maps being -5 could go back a few years when i was helping you out because that is the setting I've always used.
To me this indicated that the Base map (not the max retard map) is the map that actually controls it .
Your maps being -5 could go back a few years when i was helping you out because that is the setting I've always used.
#397
weeeeeeeeee
iTrader: (12)
Sorry Brett --- going OT.
I just got an update notification while firing up mep. Pushed me to 2.0.1.755 .. I only did the EXE install as the setup wizard implied that was all I needed to do... and was fearful that a full install would force me to have to go through the whole key registration process again.
No change log included ... haven't checked the site for any info, and didn't notice any differences after a quick glance. Maybe he fixed the MazdaCANalyser thing as I've noticed a couple subtle bugs in it... will have to plug in to validate.
I just got an update notification while firing up mep. Pushed me to 2.0.1.755 .. I only did the EXE install as the setup wizard implied that was all I needed to do... and was fearful that a full install would force me to have to go through the whole key registration process again.
No change log included ... haven't checked the site for any info, and didn't notice any differences after a quick glance. Maybe he fixed the MazdaCANalyser thing as I've noticed a couple subtle bugs in it... will have to plug in to validate.
#398
Sorry Brett --- going OT.
I just got an update notification while firing up mep. Pushed me to 2.0.1.755 .. I only did the EXE install as the setup wizard implied that was all I needed to do... and was fearful that a full install would force me to have to go through the whole key registration process again.
No change log included ... haven't checked the site for any info, and didn't notice any differences after a quick glance. Maybe he fixed the MazdaCANalyser thing as I've noticed a couple subtle bugs in it... will have to plug in to validate.
I just got an update notification while firing up mep. Pushed me to 2.0.1.755 .. I only did the EXE install as the setup wizard implied that was all I needed to do... and was fearful that a full install would force me to have to go through the whole key registration process again.
No change log included ... haven't checked the site for any info, and didn't notice any differences after a quick glance. Maybe he fixed the MazdaCANalyser thing as I've noticed a couple subtle bugs in it... will have to plug in to validate.