With no knock buffer hooked up, what knock values (Y-axis on SMART timing table) are you seeing? 0% or something else?

Shiv

 

havent looked...will check tomorrow

is it a problem that i have it setup this way?

 

Yes there is a problem with that. With no knock signal going into AN0in, the input voltage defaults to 50% (2.5v). This will mean that you are operating in the 50% row of the SMART timing table. This will be pulling out unnecessary amounts of ignition advance. Safe, yes. But not optimal

Might want to zero out that table

Shiv

 

ohhh will do...

i thought with no signal it would read 0%

car seems to run strong...but ill zero out that table and see how it does

 

Nope, all the analog inputs default to the middle of the road. Take a look at AN0 in and AN1 in. They'll both show about 49.7 with nothing plugged in. Better yet, take a look at this guy's log file.

https://www.evolutionm.net/forums/sh...d.php?t=153416

d

 

Back to launch control....

With it ON the car's RPMs drop really slow when clutching in or even when the car is in neutral (this is coming out of any gear). 75% of the time it happens.

Now with it OFF the car is fine.

It's a buddys 05 MR.

Any thoughts?

 

Hey Shiv, I went out to try and get an idea of my noise floor like you suggested. I dumped the boost table and did a run, no knock. So then I put the boost back to where it was (around 19 psi tapering, still taking it easy) and there was a LOT more noise. The funny thing is, the noise looks just like a seismograph plot, no spikes (I have seen knock spikes in other loggs, very sharp hits), there is just a lot more of it. It seems to rise faster and it oscillates rapidly, well, just like the seismograph plot! I ran to the same RPM, just a lot harder with the added boost. Is this normal or am I getting cotinuous small knock events? I have some colums retarded up to 2.1 degree's already, how much retardation is deemed normal? I do not want any knock, but conversly I do not want to kill of timing un-necissarily.

 

Do you have an example of a smart timing table for stock cams or a suggestion on modifying the zero'ed region for the maps published to date?

 

'eh? The SMART template should be fine for car's with stock cams. I think his point is that stock cams produce less noise than ones with longer duration (264s, 272s, 280s). Actually, my noise level is astonishingly low. With 101 gas on a 91 map, I peak at about 35% @ 7000 RPMS. EDIT: on stock cams

d

 

Mine goes up to around 55%, but also a built engine, 2.3, no balence shafts, etc.

 

I guess my real question is if I should lower the upper end of the map to account for the lesser noise of a stock cam'ed engine, thus proving a (minimal?) level of extra protection?

 

Assuming more maps are not added back in, would this feature reduce the map loading time for the Xede?

What I found yesterday is that ~1:10 starts without waiting for the maps to load yielded some strange and disturbing engine noise (misfire?). Is it possible to botch the timing on start when the Xede is still loading the map?

 

Pardon my ignorance, but does the LED indicate that the maps didn't load correctly.

My mechanism for making sure that the maps get loaded is to get in, power the car on, buckle my seatbelt, then start.

d

 

On that note, can I order the "remote LED" from Vishnu, and does it have any install instructions? I don't feel comfortable cracking the case on the Xede.

 

Nope. To be honest, the wait time we suggest is to prevent that misfire which could occur if you just happen to crank up the engine for that millisecond the XEDE is doing a certain step in its start up/map loading routine. If you just happen to catch it right as it doing that, it will hiccup. That's what the 2 second wait is for. To be honest, you don't even have to wait those two seconds. The XEDE will come on-line (solid green LED) regardless within ~2 seconds.

Shiv