I have logged a couple (10 or so) runs with evoscan this afternoon and am having an issue. It seems to only want to log in 1 second intervals... It then waits about 5 seconds and then logs another 1 second interval. This is pretty annoying. I cut down the number of things that it was logging (to RPM, TPS, knocksum, and timing advance) and deselected the log to screen option and selected the logger Superspeed option. My timeout is set to 500ms and the Baudrate is 15625. I am also using the FTDI selection. No other programs were running while I was logging.

I am sure that there is an easy fix for this but I have looked in threads for over an hour and a half now and haven't found the answer I am looking for.

Thanks in advance!

 

My IBM laptop was doing something similar. I realized after a few runs that the hard drive protection algorithm was spinning down the HD.

 

I noticed if the "init" doesnt work correctly, the software runs very slowly, I've seen this on my program and on Evoscan.

Have you used the cable for anything other than logging, and is it working okay on other cars (have you had a chance to check it?)

Are you also logging AFR with a wideband? If you are, try unplugging or disconnecting/disabling wideband logging.. etc..

It could be funky drivers, or whatnot.. But go through the simple stuff first.

 

The cable worked fine for downloading my stock ROM and I haven't tried it on any other cars yet. I am going to try the other port tomorrow and see if that clears up the issue.

I don't have a wideband yet so haven't tried that yet.

Hopefully it isn't an issue with drivers...

It very well may be the hard drive protection kicking in. Is there any way to disable it for a few seconds? I am sure that the sudden jolt from the acceleration of the car is kicking the HD protection on.

 

There would be an option somewhere (either a program or control panel) to disable it.

 

Got it figured out folks. Thanks for the help.

Evidently my tablet was shaking a bit on launching the car and kicking the HD protection on. I just put the screen in the down position and used the stylus to start the log. No problems now .

 

Cool.. fortunately it was easy to figure out.. I actually had reduced the sensitivity on my HDD protection before I ever had evoscan/mitsulogger set up so I never noticed if it interrupted disk activity would prevent logging. Its something to keep in mind (write to memory and commit to disk less frequently) in new versions of my logging tools.

 

Good point.

Of course, the HD protection function helps if you accidentally had a bump or crashed your car or similar... touch wood that doesn't happen, but it is there for a purpose.

I would say, if you have a laptop, try putting some breathable padding (like the grey soft padding that lots of motherboards, PCI cards, etc. come with) under the laptop for vibration damping. That will still allow the fans to work (in fact, it will act as a filter for the fan) and will ensure the bumps on the road don't screw with the laptop. Thats what I did and it certainly helps (and I had the laptop under the passenger side seat).

 

hehe. The bumps are only part of the story. The acceleration of the Evo was enough to trigger spindown on my laptop.