Originally Posted by ShelGame
How so? I can see where it could help identify bad sensors, but what else?
How so? I can see where it could help identify bad sensors, but what else?
Agree. Never data log, my car runs 20 psi and still together. Ostrich does make real-time tuning super easy for us LM users.
You CANNOT tune when your hardware are not up to spec!!! Nothing to be "lol" at, unless you really hate your engine and want to drown it with gasoline.
You CANNOT tune when your hardware are not up to spec!!! Nothing to be "lol" at, unless you really hate your engine and want to drown it with gasoline.[/QUOTE]
My fp is set lower than 55 psi right now. The cal was supposed to be for 55 like stock. I have an afpr and have it turned down and it's still that rich at idle. It's the cal I'm not an idiot
The problems I've had and had been chasing all turned out to be items that would net set codes. VSS, MAP etc. Would logging help this? Maybe. I think these items were on the brink and in unison where creating gremlins. Plus I fed them after midnight..my bad.
A simple otc 4000e scanner would be just fine.
https://www.youtube.com/watch?v=F83NtIg4x7I
I think Asa's point is, if you get logging setup, MP Scan can do everything a scantool can for the price of a $40 (or less) cable.
Of course, setting up MP Scan can be difficult, hence the reason for wanting it to be part of the wiki.
The same way a Chrysler DRB II /OTC is used as a diagnostic tool?
Yep!
And simultaneously, getting MPSCAN logging means you have established communication with the ECU and are laying the foundation for flashing.
OTOH, if you have too much trouble getting logging working, then it probably makes more sense to get a dedicated scan tool to get your engine working if its a daily driver.
I am sensing some odd perceptions of data logging, almost as if its some kind of aristocratic thing or should somehow be avoided as a badge of honor or that its some kind of cheating or crutch? Data logging is having the ECU tell you what all its inputs (and outputs) are, and recording all of it for easy review later. I also include in the term "logging" diagnostic functions like reading fault codes or activating the many ECU outputs. I think its sort of strange anyone would intentionally avoid this bag of tools when it costs so little, make detailed analysis both for troubleshooting and tuning much easier and more thorough, and gives the beginner a much clearer idea of whats happening in the engine and how your cal is operating.
Well I'm rather 'tech savy' I set up logging on the lancer. I had a heck of a time getting the gauges setup and displaying what I wanted for some reason. Some of the gauges that were named a certain way, at least what I thought they were, did nothing or showed something that made no sense.
Perhaps this is an exposure thing where I need to just sit in the car on a saturday morning with a pot of coffee and just work the problem.
I would say give it another shot.
Some things to remember:
-if you are not using a boostbutton SCI cable, I cant help you because I dont know about other cables (someone else might be able to though)
-make sure MPSCAN says "FTDI" at the bottom of the window. This tells you it is definitely using the boostbutton cable and not some other random serial device.
-if anything goes wrong with communication, the ECU will start ignoring your attempts, and you will need to cycle the key on and off to try again. In this situation, MPSCAN will tell you there is a USB/serial port problem, which is not true.
-it may be easier to try basic reading of sensors while you are initially getting MPSCAN going, instead of setting up gauges
-setting up gauges for logging is a somewhat convoluted process and does not intuitively flow. Once you've done it once its no big deal, but the first time can be odd. Heres my instructions on doing it:
http://www.turbododge.com/forums/f4/...ml#post3375194
Shel-game, why dont we start laying out the skeleton for an invincible MPSCAN/logging procedure? I'll start:
***THIS IS A PRELIMINARY PROCEDURE AND MAY NOT BE CORRECT***
a- verify computer/OS is proper for MPSCAN (where are the specific system requirements, including any additional packages/frameworks needed?)
b- make sure Boostbutton SCI cable is NOT plugged into computer and NOT plugged into vehicle
c- Download and install MPSCAN software. Or install using included CD from boost button. (where is official place to get it?)
d- Do not open MPSCAN. If you have opened it, close it.
e- Install boost button SCI cable into USB port. (do the correct drivers automatically load properly in EVERY situation?)
f- determine what com port the SCI cable installed to by going into control panel/system/ports/com ports/properties (is this required or will MPSCAN autodetect?)
g- Run MPSCAN
h- select the com port from (f) in MPSCAN
i- verify the bottom of the MPSCAN window says "FTDI blah blah"
j- turn key off in car
k- plug cable into vehicle diagnostic connector
l- turn key on in car
m- in MPSCAN, go to the sensor window, click "connect to ecu" and request a sensor update for TPS volts or something
n- confirm that the in the lower right part of the window, the sensor data appeared
o- if this did not work, try turning the key on and off, then repeat from m)
And this concludes getting MPSCAN communication established.
I have a boost button cable and had to jump through some major hoops to get ftdi to work on my computer.
Last edited by going4speed; 01-19-2015 at 03:00 PM.
Would be good to hear what Shelgame has to say about this. Also do you remember what you had to do to get it to work?
I dont really remember. Kind of burned out on it if you know what I mean.
Have not tried in some time. That's why I'm in here to try learn before I dedicate any time to it. Dont have much time to mess around with stuff and go through a major learning curve right now.
The official location is wowzers google site - https://sites.google.com/site/mpsuite/mpscan
Not automatically. You need to follow this - http://www.boostbutton.com/turbonato...id=cable_setupd- Do not open MPSCAN. If you have opened it, close it.
e- Install boost button SCI cable into USB port. (do the correct drivers automatically load properly in EVERY situation?)
At least, from step 8 if you bought the cable from me. It's a 1-time deal. Once Windows is setup to read it as a COM port, it's OK.
MPScan should auto detect if it's the only port you have. If there's another one for a WB controller for example, it might get confused and pick the lowest number one. I'm not 100% sure.f- determine what com port the SCI cable installed to by going into control panel/system/ports/com ports/properties (is this required or will MPSCAN autodetect?)
Anyway, you should already know the COM port number from the step above.
I think there should be a step in here to confirm the ECU type? Definitely not all ECU's use the exact same protocol for sensor check. I don't remember how wowzer set this up, but I think it maybe only works for SMEC and SBEC. I'm not positive, though.g- Run MPSCAN
h- select the com port from (f) in MPSCAN
i- verify the bottom of the MPSCAN window says "FTDI blah blah"
j- turn key off in car
k- plug cable into vehicle diagnostic connector
l- turn key on in car
m- in MPSCAN, go to the sensor window, click "connect to ecu" and request a sensor update for TPS volts or something
n- confirm that the in the lower right part of the window, the sensor data appeared
o- if this did not work, try turning the key on and off, then repeat from m)
And this concludes getting MPSCAN communication established.
I totally understand. If you end up giving it a shot, please try the procedure skeleton you see laid out here, and let us know what goes wrong, and we'll adjust it until it works. Your suffering will be remembered forever by all
I'm not picking on anyone, but this is exactly what I was getting on about. OK, so I'm going to adjust the "pumping table". Why? "Because it works" doesn't do it for me. OK...it works. What am I really changing? How does this interact with the rest of the tables? What does it do in terms of affecting how the engine runs? What parameters of the engine affect the table?
(Note: I have read the description on the linked site and that is getting very close to what I was looking for, so good job!The only thing I see left out is if it affects other tables and if so which ones.)
Like I said before, I understand this is super high level and is supposed to be a very basic tutorial for people like me who have been kicking this idea around for the last 15 years and still have yet to try and connect a laptop to my SMEC! LOL However, I might be more inclined if I didn't feel like I was just doing things "because it works".
I would have to agree. I think the TD/TM world has enough equipment and know-how now with folks like Shelgame and lots of other people to move to the next level and have a pretty good grip on what we are doing when we change the cal.I'm not picking on anyone, but this is exactly what I was getting on about. OK, so I'm going to adjust the "pumping table". Why? "Because it works" doesn't do it for me. OK...it works. What am I really changing? How does this interact with the rest of the tables? What does it do in terms of affecting how the engine runs? What parameters of the engine affect the table?
(Note: I have read the description on the linked site and that is getting very close to what I was looking for, so good job!
Like I said before, I understand this is super high level and is supposed to be a very basic tutorial for people like me who have been kicking this idea around for the last 15 years and still have yet to try and connect a laptop to my SMEC! LOL However, I might be more inclined if I didn't feel like I was just doing things "because it works".
I think most people who know how to adjust fuel pressure manually with an AFPR to meet an AFR could grasp whats going on when they change the cal. Its just there is such a steep learning STEP to get the hardware and software operational first. Then you can finally start learning about tuning.
http://www.boostbutton.com/turbonato...?id=fuel_setupI'm not picking on anyone, but this is exactly what I was getting on about. OK, so I'm going to adjust the "pumping table". Why? "Because it works" doesn't do it for me. OK...it works. What am I really changing? How does this interact with the rest of the tables? What does it do in terms of affecting how the engine runs? What parameters of the engine affect the table?
(Note: I have read the description on the linked site and that is getting very close to what I was looking for, so good job!
Like I said before, I understand this is super high level and is supposed to be a very basic tutorial for people like me who have been kicking this idea around for the last 15 years and still have yet to try and connect a laptop to my SMEC! LOL However, I might be more inclined if I didn't feel like I was just doing things "because it works".
Too much?
That information is very good Rob, but it wont be much use to people who dont already have a solid understanding of whats going on. Its sort of a seminar on "How the Chrysler ECU does things you already know other ECU's do.". But I think there needs to be a seminar "How an ECU manages an engine." to get more people on board.
Posting Permissions
Reply With Quote