I was all excited to try this out tonight, but things didn't go so well.
The car is a 94 Stealth (electrically identical to the 3000GT). I've never had an issue using my OP2 and EvoScan with MUTIII to log the car. I've tested it with multiple bench ECUs from multiple years of Mitsus (anything from 94 to 2003) and never had an issue with normal logging. I've also used Mitsulogger without issue.
I got a generic 2GB MicroSD card from my old cell phone, formatted it Fat16 and wrote a logcfg.txt file to it. When I tried it in my car, I had my start parameter for >500 rpm and my stop parameter for <400 rpm. I did this to test it and because at the moment, I want the logger to be running whenever the engine is.
I started the engine, the OP2 wrote out a logcfg.out (8k) to the card, and that's it.
I tried it with one of my bench ECUs with the sole change being to set it to trigger a start if the battery voltage was over 10v. My bench units usually show 11.6 or more. Still nothing.
I plugged in with my laptop and EvoScan and it fired up with no problem. The red and yellow lights flash rapidly. When it's just the OP2 with no cable or PC attached, all I get is the slow cycle of red to blue to yellow and back again. It does the same thing when connected to my car.
I've read through this thread several times and I don't
think I'm doing anything wrong.
Here's a sample of my current log parameters.
- Code: Select all
type=mut2
paramname=Battery
paramid=0x14
scale1=0.0733
trigparam=Battery
condition=gt
value=10.00
action=start
trigparam=Battery
condition=lt
value=5.00
action=stop
The only difference with my 'live' config was that the trigparam was RPM and the value was 500. Stop value was 400.
I've attached the entire log file for comparison. Let me know if there's anything else I can add or check or whatever.