Page 27 of 27 FirstFirst ... 172324252627
Results 521 to 533 of 533

Thread: MPScan

  1. #521
    Supporting Member II Turbo Mopar Contributor 83scamp's Avatar
    Join Date
    Mar 2013
    Location
    Columbia City, Indiana
    Posts
    1,078

    Re: MPScan

    Is there a list somewhere of what all the memory locations are? Looks like you can monitor 40-50 different points, but what do the names mean? For example, I was looking at temps, and there are like 9 different ones. Is Temp0 the correct one? Just for giggles, I put Temp0 & temp1 on my dashboard, they were not in sync. Some are easy to figure out, some I have no clue what I would be monitoring if I added them...
    83 Scamp GT, 2.5 TII/A-520
    89 Dodge Daytona ES turbo, Daily driver

  2. #522
    Supporting Member II Turbo Mopar Contributor
    Join Date
    Jun 2006
    Location
    Spearfish SD
    Posts
    1,745

    Re: MPScan

    the only "easy" way to see the memory locations that are valid is to go to settings/layout files/xref file, click on the header for the ecu you are interested in, and then look at all the items that have a ram location >= 0. all the long/short names are what rob L uses in the turbonator cals. a number of them are just temporary storage areas used by the program and may have no real meaning other than for a value used in some calculation that is then replaced and used in an unrelated calc. if you are really adventurous you can open up the .lst file that is created when you compile and look at where the code uses those variable names.
    89 Voyager LE, 2.5T2 - rest in peace
    87 Charger Shelby T2 (2.4 conversion in process)

  3. #523
    Supporting Member II Turbo Mopar Contributor 83scamp's Avatar
    Join Date
    Mar 2013
    Location
    Columbia City, Indiana
    Posts
    1,078

    Re: MPScan

    Quote Originally Posted by wowzer View Post
    the only "easy" way to see the memory locations that are valid is to go to settings/layout files/xref file, click on the header for the ecu you are interested in, and then look at all the items that have a ram location >= 0. all the long/short names are what rob L uses in the turbonator cals. a number of them are just temporary storage areas used by the program and may have no real meaning other than for a value used in some calculation that is then replaced and used in an unrelated calc. if you are really adventurous you can open up the .lst file that is created when you compile and look at where the code uses those variable names.

    Thanks.

    I am certainly not that adventurous, at least not yet. Still very, very green at this whole tuning thing. So far I'm just happy my laptop is talking to the ECU via MPScan.
    83 Scamp GT, 2.5 TII/A-520
    89 Dodge Daytona ES turbo, Daily driver

  4. #524
    Visit www.boostbutton.com... Turbo Mopar Contributor ShelGame's Avatar
    Join Date
    Dec 2005
    Location
    Whitmore Lake, Michigan, Unite
    Posts
    9,884

    Re: MPScan

    Quote Originally Posted by 83scamp View Post
    Is there a list somewhere of what all the memory locations are? Looks like you can monitor 40-50 different points, but what do the names mean? For example, I was looking at temps, and there are like 9 different ones. Is Temp0 the correct one? Just for giggles, I put Temp0 & temp1 on my dashboard, they were not in sync. Some are easy to figure out, some I have no clue what I would be monitoring if I added them...
    TempX = Temporary, not Temperature. They are RAM locations used only within a single routine (usually) and have a different meaning in a different routine. Logging them would seem pretty useless.
    https://db.tt/SV7ONZpQ
    Rob Lloyd
    '89 Daytona C/S

    2.5 T1 Auto
    13.24 @ 100.5mph
    NHRA #3728 AF/S

    boostbutton.com
    tuning wiki

  5. #525
    Supporting Member II Turbo Mopar Contributor 83scamp's Avatar
    Join Date
    Mar 2013
    Location
    Columbia City, Indiana
    Posts
    1,078

    Re: MPScan

    Quote Originally Posted by ShelGame View Post
    TempX = Temporary, not Temperature. They are RAM locations used only within a single routine (usually) and have a different meaning in a different routine. Logging them would seem pretty useless.
    Well, that makes sense. Guess I need to find the actual CTS location. Any suggestions???
    83 Scamp GT, 2.5 TII/A-520
    89 Dodge Daytona ES turbo, Daily driver

  6. #526
    Hybrid booster
    Join Date
    Mar 2009
    Location
    Tampa Bay
    Posts
    291

    Re: MPScan

    Look for "COOL" in the list

  7. #527
    Slugmobile & MeanMini Caretaker Turbo Mopar Contributor wheming's Avatar
    Join Date
    Nov 2010
    Location
    Raleigh Area, NC
    Posts
    3,594

    Re: MPScan

    Turbonator Flags question.
    In the bit descriptions list on the Turbonator Flags gauge, bit2 hasn't had a description other than bit2. The other bit descriptions are all identified.
    Is bit2 Overboost?
    Wayne H.

    '91 Dodge Spirit ES 2.5L turbo 5spd
    '05 PT GT 2.4T HO autostick
    '89 Plymouth Acclaim 2.5L turbo auto, "Slugmobile" yes, THE Slugmobile!
    '89 Dodge Caravan SE 2.5L turbo auto, "Mean Mini" yes, Gus' Mean Mini! (Current best 11.7786@113.04 mph! - Jan 15th, 2017 Fayetteville Dragway, NC)
    MeanMini dragracing videos: https://www.youtube.com/playlist?lis...URZLB1RxGYF6vw
    and other cars, trucks and motorcycles
    https://www.youtube.com/user/SlugmobileMeanMini

  8. #528
    Supporting Member II Turbo Mopar Contributor
    Join Date
    Jun 2006
    Location
    Spearfish SD
    Posts
    1,745

    Re: MPScan

    wayne, here are the descriptions from the code:

    bit 7 - sparkcut ; Turbonator - Spark-based rev limiter
    bit 6 - staging ; Turbonator - staging limiter is active
    bit 5 - fueloff ;Turbonator - Fuel-based rev limiter
    bit 4 - OverRev ; over rev - replaced the original flag for simplicity
    bit 3 - AntiLag ; AntiLag is active
    bit 2 - MainFuelOf; Main rev limiter fuel cut
    bit 1 - AllowSpark ; Allow spark for only this cycle
    bit 0 - DecelFuelCut ; use decel fuel cut
    89 Voyager LE, 2.5T2 - rest in peace
    87 Charger Shelby T2 (2.4 conversion in process)

  9. #529
    Slugmobile & MeanMini Caretaker Turbo Mopar Contributor wheming's Avatar
    Join Date
    Nov 2010
    Location
    Raleigh Area, NC
    Posts
    3,594

    Re: MPScan

    Thanks Morris. I was seeing occasionally the bit2 on my turbonator_flags, and suspected it could be overboost cutout, but then sometimes i knew i wasn't near overboost but might be a rev limit and saw bit2.
    This helps explain this. But also should we see both bit2 and bit5 active on rev limit? Or just bit5?
    And then i should see bit2 active during overboost since the smec cuts fuel?
    Wayne H.

    '91 Dodge Spirit ES 2.5L turbo 5spd
    '05 PT GT 2.4T HO autostick
    '89 Plymouth Acclaim 2.5L turbo auto, "Slugmobile" yes, THE Slugmobile!
    '89 Dodge Caravan SE 2.5L turbo auto, "Mean Mini" yes, Gus' Mean Mini! (Current best 11.7786@113.04 mph! - Jan 15th, 2017 Fayetteville Dragway, NC)
    MeanMini dragracing videos: https://www.youtube.com/playlist?lis...URZLB1RxGYF6vw
    and other cars, trucks and motorcycles
    https://www.youtube.com/user/SlugmobileMeanMini

  10. #530
    Slugmobile & MeanMini Caretaker Turbo Mopar Contributor wheming's Avatar
    Join Date
    Nov 2010
    Location
    Raleigh Area, NC
    Posts
    3,594

    Re: MPScan

    Got a question that i have wondered alot about, but never really bothered to ask.
    I guess this goes across all the MPSuite line of logging: MPScan, MPScanDroid, and MPSciLink...
    When logging Advance, (Adv) is this total calculated advance? Or is this calculated advance, but for total advance you ADD the base timing??

    I've seen this number be single digits at +25psi, and always wondered if i was supposed to be adding 12 deg (the base timing in turbonator ) to this for a total timing advance number.
    For reference i am logging SMEC T1.

    Thanks.
    Wayne H.

    '91 Dodge Spirit ES 2.5L turbo 5spd
    '05 PT GT 2.4T HO autostick
    '89 Plymouth Acclaim 2.5L turbo auto, "Slugmobile" yes, THE Slugmobile!
    '89 Dodge Caravan SE 2.5L turbo auto, "Mean Mini" yes, Gus' Mean Mini! (Current best 11.7786@113.04 mph! - Jan 15th, 2017 Fayetteville Dragway, NC)
    MeanMini dragracing videos: https://www.youtube.com/playlist?lis...URZLB1RxGYF6vw
    and other cars, trucks and motorcycles
    https://www.youtube.com/user/SlugmobileMeanMini

  11. #531
    Visit www.boostbutton.com... Turbo Mopar Contributor ShelGame's Avatar
    Join Date
    Dec 2005
    Location
    Whitmore Lake, Michigan, Unite
    Posts
    9,884

    Re: MPScan

    Quote Originally Posted by wheming View Post
    Got a question that i have wondered alot about, but never really bothered to ask.
    I guess this goes across all the MPSuite line of logging: MPScan, MPScanDroid, and MPSciLink...
    When logging Advance, (Adv) is this total calculated advance? Or is this calculated advance, but for total advance you ADD the base timing??

    I've seen this number be single digits at +25psi, and always wondered if i was supposed to be adding 12 deg (the base timing in turbonator ) to this for a total timing advance number.
    For reference i am logging SMEC T1.

    Thanks.
    This is in my tuning wiki. This page (http://www.boostbutton.com/turbonato...oku.php?id=faq) near the bottom:

    Ignition Timing
    Q - So I am clear on this.... The timing shown in the cal, and on a Scan Tool, will be the total timing. This number assumes the base timing of 12* (or whatever is called for on the emissions label) is there. So the number shown in a cal is not necessarily the number used in a calculation, correct?

    Answered:

    There is no such thing as ‘base timing’. The 12* is just the fixed timing used to set the sync between the distributor and the crank. The reason they chose 12* is simply because an engine generally will not run well @ 0* advance. The 12* is not a 'base' timing at all. It's simply a reference point. It never gets 'added' to anything. All the timing figures in the cal are relative to TDC (0*).

    If the sync is in fact wrong (ie, you set the sync at 14* instead of 12*), then the actual timing will be off by the same amount (2* in this example). But, the ECU will not know about that difference and will not be able to report it to a scan tool.
    Or, in this case, MP Scan...
    https://db.tt/SV7ONZpQ
    Rob Lloyd
    '89 Daytona C/S

    2.5 T1 Auto
    13.24 @ 100.5mph
    NHRA #3728 AF/S

    boostbutton.com
    tuning wiki

  12. #532
    Slugmobile & MeanMini Caretaker Turbo Mopar Contributor wheming's Avatar
    Join Date
    Nov 2010
    Location
    Raleigh Area, NC
    Posts
    3,594

    Re: MPScan

    Quote Originally Posted by ShelGame View Post
    This is in my tuning wiki. This page (http://www.boostbutton.com/turbonato...oku.php?id=faq) near the bottom:



    Or, in this case, MP Scan...
    Thanks Rob! I appreciate your insight!
    What's odd is I have read that in the past, so that's why i was taking my log reading of Adv to be total advance. But, when i showed or discussed my timing with much more knowledgeable folks, they thought if that number was correct my timing was severely retarded.

    So the DefaultSparkAdvance is added to that already? I meant to use that term, not the incorrect "base timing". Or that default is used during diagnostics or faults?
    My timing reference set at the distributor is 12deg.
    But my Adv in my logs is single digits at 25psi. Doesn't quite make sense going 113mph in the 1/4, in a van, with only 8 deg of advance, does it?
    Wayne H.

    '91 Dodge Spirit ES 2.5L turbo 5spd
    '05 PT GT 2.4T HO autostick
    '89 Plymouth Acclaim 2.5L turbo auto, "Slugmobile" yes, THE Slugmobile!
    '89 Dodge Caravan SE 2.5L turbo auto, "Mean Mini" yes, Gus' Mean Mini! (Current best 11.7786@113.04 mph! - Jan 15th, 2017 Fayetteville Dragway, NC)
    MeanMini dragracing videos: https://www.youtube.com/playlist?lis...URZLB1RxGYF6vw
    and other cars, trucks and motorcycles
    https://www.youtube.com/user/SlugmobileMeanMini

  13. #533
    Moderator Turbo Mopar Staff Force Fed Mopar's Avatar
    Join Date
    Dec 2005
    Location
    Greenville/Spartanburg SC area
    Posts
    7,219

    Re: MPScan

    Quote Originally Posted by wheming View Post
    Thanks Rob! I appreciate your insight!
    What's odd is I have read that in the past, so that's why i was taking my log reading of Adv to be total advance. But, when i showed or discussed my timing with much more knowledgeable folks, they thought if that number was correct my timing was severely retarded.

    So the DefaultSparkAdvance is added to that already? I meant to use that term, not the incorrect "base timing". Or that default is used during diagnostics or faults?
    My timing reference set at the distributor is 12deg.
    But my Adv in my logs is single digits at 25psi. Doesn't quite make sense going 113mph in the 1/4, in a van, with only 8 deg of advance, does it?
    I was running 1* total in my Lebaron in many areas above 16psi and below 4k rpm. It ran just fine, pulled 80mph in the 8th.

    Rob M.
    '89 Turbo GTC
    2.5 TIII swap is here!

    Project LookOwt
    '91 Daytona ES, 61k original miles, Rick Lozier's old 3.0 nitrous car
    Back to basics, then the mods go back on....

Page 27 of 27 FirstFirst ... 172324252627

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •