nycgps

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 ...

bse50

Why are you writing here *******? Go there and write a check!

nycgps

iTrader: (1)

rofl !!! this is called BAD influence !

I will probably do it this coming Sunday or Monday.

Brettus

iTrader: (2)

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 !!!!!!

Harlan

iTrader: (3)

Ok, how do you know it isn't detonation? or are you just guessing? Yes this is very good news!

nycgps

iTrader: (1)

the stock knock sensor is retarded, it detects non-knock as knock, but when a real knock comes it does not sense it !

it is good news indeed. I'm not FI but... someday ...

Brettus

iTrader: (2)

I don't know 100% it isn't detonation but I do know :

*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.

Harlan

iTrader: (3)

Fair enough. Regardless I don't think it would do any harm. Raising the threshold is a lot safer than advancing the timing to remove the knock control. I see interesting changes around the corner.

Driffill

how do i get the newer version? i was just re-directed to the "downloads" page where the pro link does nothing

Brettus

iTrader: (2)

Email epifan direct .

FazdaRX_8

iTrader: (1)

Fixed

nycgps

iTrader: (1)

rofl ! well, that could be true ... unfortunately

the S2 setup works better (2 knock sensor for each housing), just gotta have someone to be the sheep and try it on.

Brettus

iTrader: (2)

You will be the sheep -sheep follow . I'm from NZ , we know about sheep.

FazdaRX_8

iTrader: (1)

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!

Brettus

iTrader: (2)

hmmmm - my understanding is that knock control ceases after 5000 on the stock maps . Did you alter them ?

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.

Harlan

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.

FazdaRX_8

iTrader: (1)

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.

Harlan

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.

Brettus

iTrader: (2)

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.

nycgps

iTrader: (1)

rofl !


****, grr paypal messed up, can't get open port next week, grrr. *sob*

FazdaRX_8

iTrader: (1)

Wow not sure what to make of that. Check out slash128 1.29 log. You can see what i see. Clearly the cars are acting different

ShellDude

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.

Brettus

iTrader: (2)

Not sure what you are trying to say here . I have experienced a boat load of issues with ME but they seem to get sorted out one by one . I think perhaps I am too forgiving of these issues and don't make a big deal about it . This is mainly because I'm actually getting some support with ME. Whereas all the other tuning options i've tried have had ZERO.

ShellDude

iTrader: (12)

TRANSLATION:

Hey everybody, epifan just released an update to the personal version. Any idea what he changed / fixed as there is no change log?

better?

Brettus

iTrader: (2)

ah gotya now Don,t know about the personal edition but the full version was updated in a major way about 2 weeks ago , **** loads more tables defined.