New to TBI Data logging and such.

[georgeb]

Sorry for this dumb question but by using do you mean you are using those file parameters to control your engine or just loading them up into tunerpro for data logging. I really have no clue how this all works.

[jim_in_dorris]

The bin is just used for data logging at this point. I actually am running the ASDU bin in my truck. If you were to actually start tuning, I would start with the ASDX bin, burn that, then data log with it. To get an idea of how stuff works, ASDX will work fine.

[georgeb]

Thank you so much!!!!!

[georgeb]

I have my cable made and am able to log data! I recorded a luke warm start up in the hopes of catching it hunting for idle and was successful. You can see it in the log. Can anyone point me in the right direction with this? Is the timing advance supposed to do that? I am not sure what is all happening and why.

[jim_in_dorris]

I just took a quick look, one thing that you should do, is make sure it is completely warmed up to do logs. EagleMark always said, to take it out, drive it until is goes closed loop, then bring it back, idle it drive for 3 minutes, then put it in park and let it idle for 3 minutes. While the engine it warming up, it can be difficult to know what is going on. Try the drive then idle test. make another log and post it.

[georgeb]

Ok, will do! In the mean time, any thoughts on the ignition timing moving up and down so much in the early part of the log?

[jim_in_dorris]

You have an error 42, est that you should clear. That must be from timing it. Where are you seeing the timing change? to see spark advance in the data stream, you must apply the BPW and Spark advance Hack to the bin.