I just talked to Calvin @ Vishnu and he does not know which one it should be, but he is going to bring it to Dustin and Shiv's attention. Unfortunatly, niether of them are going to be in today so unless one or the other stumbles upon this post we may not have an answer until tomorrow.

 

I spoke with dustin a little while ago, but don't have a definitive answer.

d

 

Did they create the maps with a LM-1?

 

When will you be logging the smart info and AFR? and are real-time plots (or at least an easy way of plotting) coming in the next version?

And i'm sure you have a PDA version coming out soon too right?

 

I have been logging my AFR with the innovative software.......I'm not sure how to view my knock logs so I haven't made any changes to the fuel curves but its farely even at 10.7:1 WOT and 14.6:1 at cruise. Here is a log for a 1-5 gear burst. Once in 5th gear it drops to 10.3:1 but that is minor. What AFR are you fella's tuning for?

 

It is coming up as gibberish for me, can you convert it to some other kind of file?

 

You have to open his log in LogWorks2


Jeff, i think you should be tuning for low-11s on the AFRs on pump gas.

 

Low 11's......

I would love to run that but I would like to see if I am knocking in the current state of tune.
I wish there was an easier way to read knock. On my DSMLink they used to have the check engine light flash if you were getting X amout of knock....that way you could tune and then if you hit you max limit of knock ....lets say 4 degrees....then you get off the throttle and make adjustments to compensate.

I would pull some fuel out but honestly shouldn't the SMART system be doing that for me?

 

bump for vishnu... help us out with these AFR quesions!

 

My questions are:

1. At WOT, what AFR is the SMART configured to maintain?

2. How much of a AFR change can the smart system make? Lets say my baseline file runs my car at 10.3:1 AFR. With SMART turned on.....what would it strive to maintain?

3. When a knock event occures, does smart add fuel, pull timing, or do both?

4. Why did this kit require a C-reader?

5. If we forget to wait 3 seconds to let the SMART maps load before starting the car, what kind mapping is the Xede using?

6. Is high speed data logging supposed to be functional?

7. What is the best way to log knock on a second basis?

 

I talked to Dustin earlier, he said that he is looking in to which scale we should be using: 10:1 = 0% and 20:1 = 100%, or 7.35:1 = 0% and 22.39:1 = 100%. He also said that we need to download comlog6 ?? to enable the high speed data logging which should sample at a speed of every 0.1 second, in other words a hard 2nd gear pull would have no more then a 50 rpm gap. He is going to post which scale and where to download comlog6 (I think that is what he called it) a little later today. That should help a lot with the data-logging, but I do not know how the Xede maintains AFR, what maps it would be running if you do not wait 3 seconds, or why a c-reader is necissary. And I believe that the SMART is supposed to be capable of pulling timing, adding fuel, and pulling boost if need be. I think that Shiv posted these capabilities in the Yeeeaaahh!!!!! thread, but you would have to wade through that thread to find it.

 

This is a question I asked when SMART was first mentioned. Basically they want everybody to have a scantool so every user can begin to diagnose problems themselves. I already had a scantool, but they insisted that I get one with the kit. I think it's a policy issue more than a technical one.

d

 

5. If your forget, chances are the map will load anyway. If it doesn't, you are running on the stock ECU map with low boost(because the BCS pill is gone). It won't happen some times, and some times it will. If it does happen, you will know the first time you "get on it" and it runs 12psi. then you just turn the key off, then back on.

 

actually, the CReader does perform a (sometimes necessary) task.

If you search the forums and read up on the P0300 random misfire trouble code, you will find that somewhere, the CReader is mentioned. I remember almost exactly what shiv said about it:
'leaving the CReader plugged in seems to disable a diagnostic check that generates the P0300 code' (not a quote, but thats the gist of it)

You will also find some members had NOTICABLE misfires when this code came up, and after plugging in the CReader the misfires actually stopped. Coincidence or ignorance? maybe. but thats what was said about it.

 

The more i ready shiv's comments, the more it becomes apparent that the SMART system is merely modifying system parameters based on changes in condition, not to generate performance. it appears the system is being reactive, retarding the tuning after changes in conditions or knock are seen. Of course we all still have questions on the datalogging and AFR setup, so we havent been able to get some real good high-speed datalogs of what the smart system is doing. Heck, we dont even have instructions on how to datalog SMART yet.