MPScan

[wowzer]

DD - in mpscan go to settings/layout files/gauge settings. click on the short name column header so it sorts by short name and go to the ADV gauge. in the ecu min change it from -64 to 0 and the ecu max from 63.5 to 128. also change the display min from -64 to 0. then save it. do you have a otc or drb2 scanner to confirm your actual timing degrees? might be the easiest way to get the settings correct.

don't know what to tell you in INJPW or trims. again, it would be interesting to see if an otc or drb2 scanner would show that info.

[DoubleD]

Wowzer, I changed my settings to exactly what you showed me, but my gauge did not change, I'll play around with it a little more on lunch today.

[wowzer]

you'll need to delete the gauge in the layout and re-add it.

[DoubleD]

Took some more tweaking, but the gauge is now updated on both of my profiles, goes from 0-64 now. Will test on the way home from work tonight and report after.

I just added charge volts to my gauge display, Would it be possible to convert this voltage into an actual number like coolant temp, or does someone have the voltage to temperature chart that I could use for reference, I am curious what my charge temps are.

[ShelGame]

Took some more tweaking, but the gauge is now updated on both of my profiles, goes from 0-64 now. Will test on the way home from work tonight and report after.

I just added charge volts to my gauge display, Would it be possible to convert this voltage into an actual number like coolant temp, or does someone have the voltage to temperature chart that I could use for reference, I am curious what my charge temps are.

0-64 is not right. I should go from 0-127.5

[DoubleD]

0-64 is not right. I should go from 0-127.5

Should if go from 0-127.5 on the gauge itself and 0-128 on the ECU then?

[ShelGame]

Should if go from 0-127.5 on the gauge itself and 0-128 on the ECU then?

Sorry, you can pick whatever scale you want on the gauge. The ECU scale should go from 0-127.5 (128 is OK also, but the rounding will be off a little).

[forcedfedmopar]

ok, I got my gauges set up, how do I change the MAP values higher than 15lbs?

[wowzer]

ok, I got my gauges set up, how do I change the MAP values higher than 15lbs?

look at post 192 in this link http://www.turbododge.com/forums/f4/...ml#post3440361

there should be a map3bar gauge sensor that is then available for you to use versus the standard 2 bar map gauge.

[forcedfedmopar]

look at post 192 in this link http://www.turbododge.com/forums/f4/...ml#post3440361

there should be a map3bar gauge sensor that is then available for you to use versus the standard 2 bar map gauge.

awesome thank you. took me awhile to find my password that site!

[wowzer]

i really need to work on pulling a lot of the tips/tricks together into one place. rob L and i had visited about this some time back. i'll try to get something done in the next couple months hopefully.

[krut]

Just want to make this clear: AEM Widebands do not work for wideband logging in mpscan, right?

[acannell]

Just want to make this clear: AEM Widebands do not work for wideband logging in mpscan, right?

Do they have an analog output that represents AFR? If so then I think they can be used in MPSCAN if you use a Turbonator cal and enable that feature.

[going4speed]

Yes if you use the O2 input for the wideband and activate the feature then the cal will scale the AEM output for the cal and also allow for the full scale output of the AEM to be logged.
This is my next project once I figure out how to stop the AEM from backfeeding a ground loop into the stereo system.

[krut]

Is there a way for MPScan to not scan for a com port, but manually set it during startup?

[wowzer]

not currently, i.e. this is no "setting" that prevents scanning - what are you attempting to do?

[krut]

I'm trying to get MPScan to work in wine under linux. I think I'm missing some steps in the progress. I have the program itself running, but it's not detecting any com ports. After doing some reading it looks like it is because I am missing the D2XX driver in /usr/lib, and there is a wrapper for it for wine.

The goal is to get this working on an embedded system so I can have mpscan automatically execute upon startup and make a headless datalogger I can leave in the car, and upload the csv's to a file server. Or at least that's how I hope it'll work. :P

[wowzer]

krut - you have a pm

[going4speed]

any tips on 'unable to communicate to port error? when i hit the record button it pops up the error. Do I need to tweak the baud rate?

[going4speed]

this is the contents of txt file

mpscan ver - 2.0.2.5
Microsoft Windows 8.1 - Win32NT
trying to open port COM3 - ctlrecord_click
got a good port back - ctlrecord_click
try to open port COM3 -initport
COM3 is a legit port -initport
usb is available on COM3 -initport
usb ftdi serial number BBXNEO3P is available - initport
setting port baud rate to 7812
ftdi open successful on COM3 -usbportinit
using protocol SMEC T2:2
attempt to change ecu baud rate to 62500
Sending byte 18
Received byte 0
Read confirm byte failed (status:0 - count:0)
Sending byte 18
Received byte 0
Read confirm byte failed (status:0 - count:0)
Sending byte 18
Received byte 0
Read confirm byte failed (status:0 - count:0)
Sending byte 18
Received byte 0
Read confirm byte failed (status:0 - count:0)
usbsethibaud failed - usbportinit
ftdi open unsuccessful - usbportinit
Sending byte 254
Received byte 0
Read confirm byte failed (status:0 - count:0)
Sending byte 254
Received byte 0
Read confirm byte failed (status:0 - count:0)
can't open ftdi port - usbportinit
Unable to open/setup port. - ctlrecord_click