i assume you are all running a T-LM? which cal? (have you seen my post on the aisposition table?) also, does it act that way when you run a stock cal?
89 Voyager LE, 2.5T2 - rest in peace
87 Charger Shelby T2 (2.4 conversion in process)
T-LM 2.5 custom mtx.
I have to change alot of hardware to run a completely stock cal. Injectors and map sensor and engine lol :-)
You want me to use portmon to see what it's doing when it's doing its thing?
Brian
- - - Updated - - -
Yes I saw your post. What is the exact issue? Can we just copy different table data into the tpl for those Cals and produce T-LM 13.1 or something?
Originally Posted by turbovanman
I'm running a turbonator stage 4 87lm and don't remember having any issues with mpscan in my limited time playing with it in the driveway. Gotta fix a leaky rear main seal before I can actually datalog.
I seem to recall this issue as well. I'm having trouble getting MPScan to connect lately so I can't check it out now. I think I've got a broken wire somewhere or something. Just haven't bothered to look in to it yet.
Both of my cars are difficult to connect to MPScan as well. Some days no go, other could take 15-20 minutes of frigging.
I built an ardinuo to attempt to switch the LM from slow speed to high speed communications. It work great in my electronic shop on the bench but no go in the real world one evening. BTW "csxtra" warned me of difficultly connecting to an LM at the reported baud rate. He had to slow up the baud rate for good performance.
Regards,
Miles
DD '87 Sundance T1, SLH with rear disks
'87 CSX #432 2.5 CB TII, SLH
Mine had been working flawlessly for a long time, but then I was over near the LM messing with wiring. I probably just knocked something loose or broke one of the wires inside the case. I've got an FTDI chip soldered directly to the MCU.