Turbonator SMEC codebase

[wheming]

I have my MPSciLink working in the Lancer, so I should hopefully be able to begin logging now. We'll see how that adventure goes for me.That's a big milestone!

Sent from my KB2005 using Tapatalk

[cordes]

Thanks Wayne. I'm really looking forward to it.

["Top Fuel" Bender]

please forgive me for not fully reading through the last 101 pages LOL
trying to play with tuning the Charger some more
I "believe" what have is socketed '89 T1 SMEC (2.5) with a 2.2 TII manual

I fought for like ever to get this running and stay running
throwing all sorts of chips/injector/map sensor ect... combos at it
FINALLY before SDAC the magic combo of the socketed '89 2.5 T1 SMEC , ostrich , 75lb/hr ,3-bar

now for the weird part , it seems to only like the T-SMEC_B151_24_basecal
which I think is a setup to run the 2.4 on the SMEC correct ?

obviously the fueling and timing is probably way off on this but I was desperately trying everything and this worked good enough to drive around at SDAC
I tried running other chipped cals. that have worked for me before in this SMEC and they either don't start or run super rich die while driving
A few people have sent me my old bin files from the burned chips or created new ones for me and have the same issues
I tried a Staged Cal with no luck

T-SMEC_22_MTX_A553_Stock (set for my injectors/map ect.. ) will start and run, runs rich , dies at intersections ect...
no check engine light but has multiple "stored" codes via MP Scan.... map/tps/vehicle ect...

T-SMEC_22_MTX_S-IV same thing runs real rough ,rich , tons of codes "stored codes" via MP Scan ect..

One of the BIN files that wouldn't start the car or even fire the fuel pump gave me a "53 Internal controller failure" during the key dance since the MP Scan wouldn't communicate


what makes the B151 work fine in my car (no codes) and not the ones I should be using ?
is there a 2.2 version of this B151 that I should try ?
Suppose I could go table by table and copy the timing/fuel curves over right ? but shouldn't have to

[cordes]

Back when, one would get a code 53 with a custom cal in the car. Many didn't work with the scan tool, because things got moved around and it wasn't where the scan tool was looking for it. Neither was uncommon, but that was a long time ago.

["Top Fuel" Bender]

Back when, one would get a code 53 with a custom cal in the car. Many didn't work with the scan tool, because things got moved around and it wasn't where the scan tool was looking for it. Neither was uncommon, but that was a long time ago.Gotcha , that kind makes sense
This is an OLD CAL.
Ran great in the car before with a different socketed SMEC , the chip had corrosion so the gentleman sent me the .bin files for that one. Now this was a pre-MPTuner days calibration but I'm not modifying anything in it so that shouldn't matter correct?

Just write file, select .bin and go

Sent from my SM-N981U using Tapatalk

[cordes]

Gotcha , that kind makes sense
This is an OLD CAL.
Ran great in the car before with a different socketed SMEC , the chip had corrosion so the gentleman sent me the .bin files for that one. Now this was a pre-MPTuner days calibration but I'm not modifying anything in it so that shouldn't matter correct?

Just write file, select .bin and go

Sent from my SM-N981U using Tapatalk

That's right. If it's a really old cal, I would expect the code 53 and that perhaps a scanner would not be able to read it. I had a FWD Performance cal back when which would throw a code 53. It was really common for the longest time.