lol, Tom, just post up your paypal info.

Seriously, thank you. When's this next amazing bundle due?

gonna post up a request on the site soon but fig. I'd ask here in case I dont get time:
can we log OBDII data? I'd like to log fuel trims and stuff (MAS in lb/hr), all that good stuff.
edit: I see that you've said something about this to Jack in another thread. I'll wait in anticipation (as always)

double edit: usefull input: I think that on the all-in-one screen, the legend should include the scale of each element next to the element's name, so that you don't have to look it up or remember.

 

This would take away some space from the main graph area, so I'm thinking that wouldn't be what you'd want. Three things I've noticed when using this:

1. The scale is usually easy to figure out. Ex: 50 for 5 volts on TPS, 100 for 1 volt on the front O2.

2. I usually glance over at the engine monitor when moving the cursor, and that clears up the absolute values.

3. You don't spend all that much time looking at the real values. Instead, you look at the trends ("AFR isn't flat") and then look at the engine monitor to see how far off you are.

Try out the beta, and see if you still think the scaling is needed.

Tom

 

am I brain dead today? Either I don't see a current beta posted anywhere or It got lost in the e-mail.

 

I e-mail betas, and post release stuff. I'll send you over the beta after a snudge more work on it.

Anyone else that wants to try it, just send me an e-mail.

Tom

 

One suggestion in the new beta, Setting a default path where the files are saved for the autonaming.. Other than that, I'm pretty happy with how its working (now that it isn't crashing on me)

But the beta firmware is giving me P0300's still.. Should I revert to the beta 1?

 

There is a setting for that... 'splain further.

I'd like to see the freeze frame data for any codes you get. But something else is going on. A while back you said that you rarely got the P0300, and now it happens more often. What else has changed about the tune of your car?

Tom

 

The change was the install of the ECU+ thats the only thing that changed... I did spend some time on the tune recently and perhaps that will solve it but honestly the only thing that changed was the ECU+, prior to that I had the GT35r installed for several weeks prior, and the cams for several months with no P0300

I must have missed the default path if its already there.

I did raise the MAF output on the blowthrough sensor, it didn't throw a P0300 today after that, so thats a possibility.. only its been the same setting since before the turbo was installed.. I'll let you know how this affects it.
BTW, since the P0300 code throws a CEL, can a car still pass an OBD-II inspection with it? Since its a known problem on our cars. All the tests complete sucessfully with no other errors or codes.. I can live with the light and code.. It only happens at very low engine RPM and around or under 20mph it only hits when I'm leaving the parking lot at work, or pulling up my block real slowly.

 

DUH I'm a retard... I overlooked the tab in the settings.. LOL found the autonaming path...

 

I was curious, because even with the original firmware there was a time when you said you rarely got the P0300, and then some time later, with no firmware change, you started getting it all of the time. So, it seems like something has to change. If you're using the flash software, tuning changes there could affect the problem, methinks.

Tom

 

Its certainly possible, but I also need to add that I always had a CEL light on prior until I resolved another issue (Disconnected Boost solenoid) so I was not certain I was getting it for the first 2 weeks of it..

Good news is I altered my MAF output from the Karmann converter slightly, I haven't gotten the P0300 in 2 days, but I also haven't driven up my "Typical day from work" Where I would be in first gear, at 2500-3000rpm, driving up a ramp in an underground garage.. I'll have to wait until I do that drive again to see what happens.

I always attributed the more frequent P0300's to my exhaust downpipe rattling, but I recently rectified that and hopefully that also helps.

I did put the newest beta firmware on my car and I only got a P0300 once or twice since then.. So it did improve it FWIW.. I'll collect snapshot data over the weekend.. At least now I just get a "Too rich" CEL occasionally, and thats something I can easily fix with a bit of tuning, I spent alot of time altering my blowthrough adjustments to more closely match the stock MAF output, although it reads high, I now have AFR"s that closely match the ECU's derived AFR's..

I'll keep you posted..

 

Also, although the P0300 was infrequent, it definitely never happened before the ECU+ was installed (I had the UTEC Prior)


Ya know, in reality I don't care if the CEL light is on, but do you know if the car would pass an inspection if it completes all of the tests, and has no CEL but the P0300? That CEL is a known issue with Mitsubishi and I'm wondering if its something that would affect an inspection (I'm overdue for mine and have been putting it off until I can resolve the CEL light) Sadly, I have tested the car otherwise and it will pass a safety and sniffer test if I was asked..

 

I can't say for sure, but I think if the code is set or pending, you won't pass the test. Always hard to say, though, as it's probably different from state to state.

Tom

 

In georgia it will not pass if there is a dtc set. I had to go back to beta1 to get it to go a few days without the code so i could get tested and pass.

I also never had a p0300 before the ecu+. I also have the same ecu model as jack from a first allocation 03.

 

It turns out to be the same thing here in NY.. However I have not gotten a P0300 since the newest beta was sent to me. I have gotten a rich code a few times, but that was specifically from me working on my blowthrough MAF.

 

When is this beta software going to be released with the hardware? I am looking to purchase a ECU+ soon, and would not mind using the latest software.