(((Mitsubishi MUT-II/MUT-III Datalogger)))

[John Monnin]

Originally Posted by tfw a-ok

I hope to have something more substantial to report by this weekend. Stay tuned.......

Is he planning on doing the OBD I version for first gens? I would be great to be able to reset SRS lights without having to buy a DRBII

[StealthCRF]

didn't know people were having this much trouble clearing their SRS lights. If you need a 1st gen one cleared you can ship it to your local stealthcrf and have him clear it :P

[TwIzTeD_3kGt]

I cleared mine and it came back...think my clockspring is broke.

Any requirements on the laptop to support this? If it logs knock at a good rate, i'm buying a cheap laptop just for this.

[braxthnc]

^^
so does this work fine for everyone who purchased one? was it able to log knock after all? any gripes about this thing?
thanks

[Let-luse]

Originally Posted by braxthnc

^^
so does this work fine for everyone who purchased one? was it able to log knock after all? any gripes about this thing?
thanks

OK guys. I have had the chance to test the logger on my 99 VR4. I didn't really test it extensively since I have been pretty busy lately (we have a baby girl that's eating up all our free time... ).

Good news is that it works and it seems like it's logging knock and the sampling rate looks good (way better than the pocket logger anyways).

Bad news is that some data seems a bit off. TPS for example is at 13.75% with the thottle closed (the scanmaster and the AFC Neo both read 0% so it's not my TPS sensor). Also, I have some part throttle knock (5 counts max).

It worried me at first but I am pretty sure that I can attribute it to phantom knock (maybe due to the poly mounts)since I wasn't running high boost (12 psi) and it was a pretty conservative tune (10.8 to 11.5 AFR). Also, I revved the engine when the car was stopped and the logger showed 3 to 4 counts of knock repeatedly.

I tried to replay the saved log files and got the following error message "Input string was not in a correct format. Couldn't store <13.725490> in TPS Column. Expected type is Double." So I am pretty sure that there's something wrong with the TPS values.

Finally, I tried to display the logs on excel (CSV files) but data was all over the place. I have limited experience with loggers and with excel so if someone can help me there, I'll post these logs.

The only replay feature that I was able to use is the graph one. I am posting a screenshot of a part of my log. For clarity purposes, I have only included knock, rpm, timing and TPS on the graph. Feel free to comment.

Bottom line is I'll wait for the software version co-developped with tommy to run more extensive tests (and some free time!!! LOL) but, from the very short test I have done, I can say that things look promising for us OBD-II guys!!

GRAPH SCREENSHOT:



And that's the reason why I've been quite busy lately (can't complain as it's pure joy EVERYDAY!)

[Hannibalzero]

Cute kid.

Originally Posted by Let-luse

Bad news is that some data seems a bit off. TPS for example is at 13.75% with the thottle closed (the scanmaster and the AFC Neo both read 0% so it's not my TPS sensor). Also, I have some part throttle knock (5 counts max).

The SAFC measures depression of the throttle pedal. Unless things have changed on the Neo, you have to calibrate the TPS measure yourself. Fully depressed = 100%, unpressed = 0%. The SAFC doesn't know what the ECU actually reads from the TPS, it just assumes the position of your throttle plate based on how hard you stomp on the gas. If you disconnected your throttle cable, the SAFC could hit 100% without even moving the throttle plate.

The Mirage Corp logger also reads around 13% at idle. I don't recall exactly what the manual said is within spec, but 13% should be within range. It sounds like your logger is reading the TPS correctly.

Originally Posted by Let-luse

The only replay feature that I was able to use is the graph one. I am posting a screenshot of a part of my log. For clarity purposes, I have only included knock, rpm, timing and TPS on the graph. Feel free to comment.

Bottom line is I'll wait for the software version co-developped with tommy to run more extensive tests (and some free time!!! LOL) but, from the very short test I have done, I can say that things look promising for us OBD-II guys!!

The HHH logger also uses a graphical playback system to review logs. Once you get used to it, it is actually fairly easy to use. For tuning purposes, I think it makes a lot more sense. But if you want to use your logger more as a guage that provides instantaneous readouts (ie. a knock meter), then using the graph is a little bit cumbersome.

[Let-luse]

Originally Posted by Hannibalzero

Cute kid.

Thanks!! I know it's unusual to post baby pictures (in the advanced technical discussions mind you! LOL) but she's the joy of my life and I don't mean to sound cheesy but, to me 3si, is like a family (just look at your sig) and I felt like sharing my joy with you all.

BTW, if anyone feels that, for any reason, these pictures do not belong here, feel free to let me know and I'll remove them instantly.

The SAFC measures depression of the throttle pedal. Unless things have changed on the Neo, you have to calibrate the TPS measure yourself. Fully depressed = 100%, unpressed = 0%. The SAFC doesn't know what the ECU actually reads from the TPS, it just assumes the position of your throttle plate based on how hard you stomp on the gas. If you disconnected your throttle cable, the SAFC could hit 100% without even moving the throttle plate.

Yeah I know that. But the scanmaster gets values from the OBD-II port and it shows 0 at idle. Even the evoscan software doesn't accept my TPS values cause when I try to replay the log I get the following error message "Input string was not in a correct format. Couldn't store <13.725490> in TPS Column. Expected type is Double."

So I am pretty sure that there's something wrong with the TPS values. Add to that that I was WOT on the pull and the logger only recorded 55% max TPS. Plus the progress on the graph itself is not right. TPS values shouldn't go up gradually since I stomped on the gas pedal for the pull. It should go from closed to WOT almost instantly.

The HHH logger also uses a graphical playback system to review logs. Once you get used to it, it is actually fairly easy to use. For tuning purposes, I think it makes a lot more sense. But if you want to use your logger more as a guage that provides instantaneous readouts (ie. a knock meter), then using the graph is a little bit cumbersome.

I like the graph readouts. I just would like to see the values in excel correctly. Right now it's all over the place so I can't figure out the values. Maybe there's something I am not doing right. Let me know.

Reda/

[rcleeny]

The HHH logger has a dash board display too. You can put in any 4 sensors - like knock, TPS, O2 - to see "numbers". The dash board also remembers min. and max.

The OBDI and hybrid (beta now but final coming very soon) also have "skins". You can make all kinds of neat displays for whatever you want and they can produce audible alarms.

[tfw a-ok]

Originally Posted by Let-luse

I like the graph readouts. I just would like to see the values in excel correctly. Right now it's all over the place so I can't figure out the values. Maybe there's something I am not doing right. Let me know.

Reda/

Do you have any problems getting the software to connect initially. How many retry attemps does it take to connect please?

Tommy

[Let-luse]

Originally Posted by tfw a-ok

Do you have any problems getting the software to connect initially. How many retry attemps does it take to connect please?

Tommy

Nope. The software connected on the first attempt. Didn't have a problem with that. I did about a dozen logs and it connected on the first attempt everytime.

Reda/