^ Nice, thanks for posting it up!

 

I am able to log via EVO Scan to the pc but i am not able to log to the memory card on the OP2. Running 53040010 and i have modified my logcfg file for this ecu.

When i hit start log on evoscan the colors on the OP2 are solid red and yellow. Before hitting start they are doing the red,blue,yellow dance. With the memory card in and log trigger (rpm in my case) activated i still get the red, blue, yellow dance.

Any help on this?

 

Does it log without the trigger?

 

No, I cant get it log to the memory card at all. It works fine with EVOSCAN though. Would be very useful if someone has a working logcfg file for the 53040010 that way i can compare and see if i missed something.

 

We can't help much without your logcfg... but I don't think it will log to SD when it is plugged in to something via USB. I think that puts it in "computer attached" mode.

 

I dont log with the usb connected, just with the card in the OP2. Here is my log.cfg file.

 

If you comment out the "debug=noout" line by putting a semi-colon in front of it the line the logfile it generates may show you an obvious answer.

I assume the ECU dropdown option you use in EvoScan is: "Mode23 JP/EU/AU EVOX" correct? Have you checked the log from that to verify that RPM is actually > 0 and its not just successfully connecting?

Also, are you running the 1.43.3150 beta?

 

Ok problem resolved. I did two things at once not sure what solved it.

1. full format of memory card
2. renamed the file from my.logcfg.txt to logcfg.txt

It works!

 

- Yes i am running Mode23 JP/EU/AU EVOX
- Yes logs on EVOSCAN are fine and RPM reads fine there (RPM does not read correctly in the standalone though it gives me very large numbers) Will go back and double check what i entered into the logcfg file
- I am running 1.42.2595

Many thanks for the help though.

 

That would be the explanation. I assumed you had just done that for the forum. Glad to see it works

 

I have a 512mb card formatted to 483MB. I checked the card a week ago and had 135mb of space consumed. Come 4 days later, I had a engine failure, and do not have a log of the event because I was using fat16.

Though the maximum disk storage for fat16 is 2gb, there is a maximum files per folder of 512. I forgot about this limit until today, and though the documentation recommends fat16 for less overhead and faster writes, it does not mention this fact. I have 479 files (including hidden files of which there are none) in the main folder, and would have dropped them into a subfolder had I known.



It has only taken 3-4 months to consume that many files, and I typically drive for 30min+ at a time, and generally only 3 working days out of the week. With more than double what I have consumed the free space, I feel this is a fatal flaw in my implementation.

Another note, I would recommend not stopping your logs until RPM=0 AND speed=0 (or even better, some sort of a countdown parameter if possible). When the engine failed, it may have taken out the crank angle sensor because RPM went to 0 immediately. I had initially thought this was why I was unable to log the event.

I'm pretty frustrated right now, but this is not in any way a slam on the product. This is something that should have been mentioned but I should have also known. In any case, I highly recommend against fat16 unless some sort of fix is put in place to create a subdirectory of logs when file count is > ~400.

 

oh no - what happened with your motor dude?

 

Not sure... logs are "inconclusive" . Short shifted 2 -> 3, went 50% throttle for a second, punched it, then tach went to 0 and vents pumped in the smell of oil. Metal shavings in the bay and I can see my reflection in the spark plug hole of #4.

I should be getting a house in about 3 weeks, so I'll just have to make better, stronger, faster once I have a garage.

Driving derekste's ultra-beater rabbit until then, unless I pick up a track car in the interim.

Big changes this month!

.... I'm curious if the OP2.0 could have slowed down the car's ECU with its broken requests to write a file, but I'd doubt it.

 

damn... i take it there isn't any holes in the block?

could be a blessing in disguise...

shame about the log - would have been interesting to see what occured...

 

Definitely would have been nice to have a log for myself and everyone else.

We'll see once I get a look at it. No obvious holes, but oil and metal on the undertray toward the front of the car isn't a good sign.