update problem

Orthello · Post by **Orthello** » Wed Jul 16, 2008 4:15 am

Almighty-Si wrote:I just force updated and it went back to 59. I will take it out in the morning and test datalogging on the way to work and report back.

LOL.. done exactly the same thing at 7.15am CET

Maddog20 · Post by **Maddog20** » Wed Jul 16, 2008 9:35 am

Orthello wrote:It takes a while before the first recorded values appear. Force updated eCtune about 1 hour ago and I'm fully capable of creating nice logs, including the log window.

can you go in to detail about this? Sometimes the recorded values dont display for me either. I guess I dont fully understand the overlay settings completely.

Maddog20 · Post by **Maddog20** » Wed Jul 16, 2008 9:36 am

Orthello wrote:It takes a while before the first recorded values appear. Force updated eCtune about 1 hour ago and I'm fully capable of creating nice logs, including the log window.

can you go in to detail about this? Sometimes the recorded values dont display for me either. I guess I dont fully understand the overlay settings completely.

Almighty-Si · Post by **Almighty-Si** » Wed Jul 16, 2008 9:48 am

Well, datalogged on the way to work and for some reason the map trace is white and it won't log idle. I have all the gears selected and tps is -13 to 113 so it should log idle but it doesn't for whatever reason. I will look through my settings some more but from what I saw everything is ok. It does however log just fine on the throttle from what I could see. I didn't get a good log because I had to re-install the drivers this morning and was a bit rushed and forgot to set the correct baud rate and latency timer in the com port and realized that when I got to work (which is when I adjusted them and it won't log idle) so now that they are set correct I will get a nice log for the ride home if you need it.

Orthello · Post by **Orthello** » Wed Jul 16, 2008 9:52 am

AFR values in the log window are cummulated/averaged over a set amount of samples, to get a more reliable measurement in the log and to partly eliminate interpolation issues. So let's say eCtune averages 20 samples per cel. So when a cell is touched 20 times, finaly an AFR value will appear. It's not axacly what happens, but this is the best explanation I have from the top of my head at this moment. Correct me if I'm wrong/incomplete.

Almighty-Si · Post by **Almighty-Si** » Wed Jul 16, 2008 9:54 am

Sorry, I suck and double posted...damn blackberry.

Post by **calvin** » Wed Jul 16, 2008 10:28 am

Almighty-Si wrote:Well, datalogged on the way to work and for some reason the map trace is white and it won't log idle. I have all the gears selected and tps is -13 to 113 so it should log idle but it doesn't for whatever reason. I will look through my settings some more but from what I saw everything is ok. It does however log just fine on the throttle from what I could see. I didn't get a good log because I had to re-install the drivers this morning and was a bit rushed and forgot to set the correct baud rate and latency timer in the com port and realized that when I got to work (which is when I adjusted them and it won't log idle) so now that they are set correct I will get a nice log for the ride home if you need it.

select gear 0(afr overlay) for idle logging

Almighty-Si · Post by **Almighty-Si** » Wed Jul 16, 2008 12:33 pm

I did have gear 0 selected and it still wouldn't log idle. If I free reved the motor it would log but just those 4 cells where it idles wouldn't log any A/F ratios. I will log on the way home again and see what happens and report back.

Post by **calvin** » Wed Jul 16, 2008 5:08 pm

it's just condition checking one of your condition are not met

Almighty-Si · Post by **Almighty-Si** » Wed Jul 16, 2008 5:20 pm

Well just tried to log on the way home and the idle cels again werent working but I gave it a rev and it logged other cels so I closed the lid and went on my way. When I stopped I got an overflow error and then checked my com port settings and the baud rate adjusted itself back to 9600. Well I will go over all my settings now again, going to update drivers and try again tomorrow, will report back then.

Almighty-Si · Post by **Almighty-Si** » Thu Jul 17, 2008 8:35 am

Ok well I updated my drivers (02.04.06 from FDTI website) and connection is much better and its actually saving my settings now but trying to log on the way to work got me an overflow error again. Going to try and get it to pop up again on the way home and take a screen shot of it to post up later on. Also my trace is still white but I did get it to log at idle. One of the settings were off don't know how I missed it, sorry !

Almighty-Si · Post by **Almighty-Si** » Thu Jul 17, 2008 7:33 pm

Well datalogging is still weird...trace is still white and the car actually stalled on me 3 times today. Had the overflow error come up but I adjusted it according to the sticky on the top of this page so we'll see how that works tomorrow. The stalling is a weird issue...something just clicks and stall...but re-fires fine.

Post by **calvin** » Fri Jul 18, 2008 5:56 am

let me know...

Almighty-Si · Post by **Almighty-Si** » Fri Jul 18, 2008 8:43 am

Well got the overflow error again. Had it at 90 then 85 then 80 now 70 and it finally stopped giving the message but the trace still jumps to the last column on decelleration. It didn't stall on me today but the datalogger did lock up on me 2 times, the trace is still white after trying an update again and the car revs a little connecting and disconnecting to the datalogger. When it locked up it froze the program to where I had to close it out and open it up again, pull the USB (or it wouldn't recogize the ECU) and click connect again. Never knew how difficult that all was to do while at highway speed

Good thing I goto work at 5am. That's it for now, the car seems to be running fine though without datalogging connected and its weird but I don't get any error messages when things lock up on me. I will log on the way home and see if anything happens again and will report back.

Post by **calvin** » Fri Jul 18, 2008 8:53 am

find out how it locks up