a1exander wrote:
As in cylinder compression and if so why given that all is new?
Exactly because ALL is new and untested.
There was a lot of variation on the first compression test, which is expected with brand new unseated parts. Now that its run a bit I'd expect things to be getting more consitand and that is almost what I found.
9 cylinders were in the 150-160 range. Cylinder 6 where I see oil was 175, which means the oil is helping it seal and therefore most likely coming in through the intake for some reason.
Cylinder...4(? without my notes in front of me) was 140, not awful but something to keep an eye on.
Then there is cylinder 8 at 110. Last test it was 125 so its gone backwards and I'm certain I hear a leak during the test. I need to go back through my notes, I think this one was prone to a valve leak but a gentle tap on the bucket to pop it open and let it slam fixed it so I thoght it was fine.....that may have been a bad call on my part. For the moment I'll watch it, but if it persists this and the oil in 6 mean the engine needs to come apart, the only question is now of winter.
After all that I put clean plugs in, loaded the lastest version of the model into the ECU and....couldn't get it started but did manage some really loud back fires. WTF is it now?
I need to go through the log data. I had cranked it a lot before trying to start it so the battery was low and at the very end when I was done and picking up I saw that the wire I had clipped the timing light to had logged itself in the throttle linkage preventing at least cylinder 7 throttle from closing so I don't know what that means and will need to take a closer look tonight.
The model I loaded last night remover the cylinder O2 stuff that the sensor response time was just not fast engough to support and added new code to do misfire detection using crank speed variations. The new misfire code seemed to work....there was a problem with a math function that worked on the simulator not being accepted as valid by the ecu, but a quit edit and it was solved and pretty obvious that a couple cylinders were firing and the rest weren't but until its running I can't be certain the ones I think are firing are the ones that actually are. I found some data that says velocity peaks around 150ATDC so that is about where I'm looking....but with 12 cylinder one hits the top of compression which should cause a slowing every 60 degrees and at 150ATDC, 3 or maybe 4 cylinders have fired depending on timing advance.....but it seems to be working during cranking at least with the crank moving about 30% faster if the cylinder fired (though I'm not currently positive I'm calling it the correct cylinder) . I need to see it in action on a running enine though.
I also added a misfire count.....but thinking I'm not sure how useful it is since the function its not synced to engine cycles its just running in a timed loop so during crank and low rpm the same misfire coud be counted multiple times and at high rpm it might not be counted at all. I need to rethink this part but its not important at the monent, I just look at a graph of the log file of misfire vs crank position and its obvisous whats going on, but long term I'd like to light a malfuction light on the dash so this will need to be sorted.
Tonights focus will sorting out or trying to sort out why it didn't start last night.