I don't think that's going to work... where does "User 4" come from? ...and you've got two things pointing to "Freq0 Out".

Try this one...

 

Its because I'm an idiot and forgot to look at the inputs/outputs of the launch control map

 

I'll give it a shot tonight. Hoping the car isn't missing any maps. I noticed in my older pre-SMART maps there is a knock, absolute 0-20% map.

Also what did the Fuel Threshold map do in the old set?

 

Pre-SMART, you didn't have the knock buffer that comes with SMART.

How is your knock signal wired on your car? AFAIK, if it passes through the Xede, then a map is needed for it... even if it's just a blank map.

 

I had smart for awhile but "it just wasn't for me" so I am back to base configuration.

Its odd that you say you need a map for it.....because the people that never purchased SMART and only upgraded from V2 to V3 they haven't rewired anything but are still using the zero'd out SMART maps without the KNOCK map.

 

Now that you mention that... and now that I've thought about it... I'm more than likely in the wrong.
I just remember reading something like that a while back (signals just passing through need a map), but I guess it is no longer an issue in newer firmware..? ...or was it *ever* an issue?

 

I'm glad Shiv released the new maps and I'm glad they upgraded to V3 but I sure wish I could find more information about what the car really needs to function safely.

Does it need a fuel threshold map with -100 across the board?

Does it need a knock map with -20 across the board?

I'm cautious about just removing maps.

 

Just follow the logic laid out by the inputs and outputs when you look at the map Summary Info (under the File menu).

On a SMART map, the fuel threshold serves to "turn off" SMART fueling below a certain TPS.
If you have the logic "rerouted" correctly, what's the point of having a fuel threshold map if you're not running SMART?

Vishnu's SMART and SMART-disabled maps don't have it... so I would have to say it's not needed.

That's why I didn't "just remove maps". Look at the summary info.

 

Thanks!

Summary info....I'll look into that.

What did the knock map do in the first place?

 

As wrong as this sounds... it looks like sends a flat 1V knock signal to the ECU...?

The knock map is set up for a range of 0-20% absolute output (still on a 0-5V scale?)... and the map is filled with "20.0". If true, this would effectively disable the knock sensor.

...OR...

Maybe it's increasing the knock signal 20% across the board. This makes a bit more sense...

 

Hmmm

So it either enhances or disables - but - its no longer there so it doesn't do either anymore!

Shiv?

 

Just a follow-up on these maps......

So the above NO-SMART map works like a charm. But even with the smaller maps I still have to wait a few second for the XEDE to boot or the car runs a default map.

Anyway I thought I would attach my dyno tuned V390 map here as well. On the dyno I sniffed the V390-2005-93 and V390-2003-93 maps and both were way too lean and a tad too aggressive on timing. Both down low and up high the AFR went above 12:1 which didn't make me feel comfortable at all. A few tweaks here and there I managed to keep a rock solid 11.5:1 AFR and avoid all knock even on back to back runs.

I'm not sure what the other fellas with 2003's and 10.5 hotsides are doing but the 2005 map was WAY TOO LEAN for me. The 2003 map was safer but still produced some knock up top.

At least you can take a looks and see how this compares to your maps whether they are custom or standard.