MSPNP Pro, 2004 MSM Engine turns over, won't start
2 Attachment(s)
I took this log file while key was being turned.
|
The composite log shows a good RPM signal, but it can only show the RPM input. So we can rule out "does not have a crank or cam signal" as a cause, but can't go much further than that from this one file. Can you post your MSQ and a standard data log of an attempted start, too?
|
Originally Posted by Matt Cramer
(Post 1334141)
The composite log shows a good RPM signal, but it can only show the RPM input. So we can rule out "does not have a crank or cam signal" as a cause, but can't go much further than that from this one file. Can you post your MSQ and a standard data log of an attempted start, too?
Msq is the basemap for the 2004 MSM from DIY's website. I'll grab that file when I get home if nobody has it on their PC. Also it might be worth noting that the car has no MAF sensor and I've changed the setting that allows the ECU to read based off speed density instead. I honestly thought that was a general log, I guess not. How do you make a normal one? :noob: |
2 Attachment(s)
Is this a detailed enough log? Still trying to figure TS out.
|
The Engine Logger is a weird, highly specialized thing. What you want is a normal data log. To get a data log, go to the Data Logging menu and click Start Logging. You will be prompted for a file name. The log starts when you save the file (this is an easy one to get tripped up on as a lot of people expect saving the file to be what you do at the end of the log). Once you have recorded what you need, go to the Data Logging Menu and click Stop.
|
Originally Posted by Matt Cramer
(Post 1334667)
The Engine Logger is a weird, highly specialized thing. What you want is a normal data log. To get a data log, go to the Data Logging menu and click Start Logging. You will be prompted for a file name. The log starts when you save the file (this is an easy one to get tripped up on as a lot of people expect saving the file to be what you do at the end of the log). Once you have recorded what you need, go to the Data Logging Menu and click Stop.
|
The datalogging menu in the menu bar at the very top of the screen. Same place as the file and communication menus.
|
Originally Posted by aidandj
(Post 1334819)
The datalogging menu in the menu bar at the very top of the screen. Same place as the file and communication menus.
Thanks dude. |
4 Attachment(s)
Okay finally got around to getting the right logs done. There were a few turnovers attempted for the same log. Tell me what you guys think. Much appreciated.
|
Sigh...did a compression test. All cylinders are at 60 something. Thats at least ONE of my issues getting it fired up. Should've known with a completely fresh rebuild. :facepalm:
Oh well, gonna try some tricks in the morning to raise it and get these rings to seal hopefully. |
Also check your cam timing to be sure that's not causing the low compression.
|
Cam timing was the first thing we checked. I redid it, had my engine builder redo it, then I called an ASE Master Tech to do it and he did it according to AllData. Nobody was even off by a tooth.
What do you think of the new logs I sent, Matt? |
Originally Posted by hraday93
(Post 1335778)
What do you think of the new logs I sent, Matt?
|
Originally Posted by Matt Cramer
(Post 1336057)
Either your MAP sensor is disconnected, or your engine has raised "won't pull any vacuum" to an art form.
|
That was all I spotted, and that plus low compression could be enough to account for it not starting.
|
Alright cool so it's just low compression then at this point, as the vacuum hose was plugged in the rest of the time we tried to start on MS. I appreciate you looking into that, Matt!
|
All times are GMT -4. The time now is 08:33 PM. |
© 2024 MH Sub I, LLC dba Internet Brands