Author	[Modern View]
mEl 02-24-2013 04:48:00 71.241.104.174 Report to Moderator	If you don't have any luck with those suggestions which I am afraid will happen, remove the head and check the sleeve protrusion at the block, they should be even all around the sleeve and .002--.004 above the block. The sleeve should be clamped down hard when making this measurement. Back in the day we had many that the sleeves would settle and the gasket lose it's ability to seal. The 530 had "narrow flange sleeves" and later 188s were built with "wide flange sleeves" with more counterbore support. It was common practice to plane the block surface a few thou. and enlarge the counterbores and remachine the counterbore to set the newer sleeve to the right height. The later wide counterbore sleeves were then installed. This must be done by a competent machine shop and only the bare minimum material removed as piston to head and valve clearance can be an issue if care is not taken to check clearances. Only the bare minimum can be taken off the block surface, enough to get a clean counterbore where the sleeve sets. Also on the first 188s we experienced sleeve breakage about 1/4-5/16 down, a radial crack in the area where there is no stud. Sometimes the only way to find them was to dry everything up and look for a seep line on the interior of the sleeve. Great engines however after the changes to the blocks and sleeves were made problems dropped dramatically and they will be remembered as one of the best engines ever made. mEl [Reply]   [No Email]
Adirondack case guy 02-24-2013 05:39:15 74.69.160.79 Report to Moderator	Re: case 530ck pushes out coolant in reply to mEl, 02-24-2013 04:48:00   Mel, Does anyone offer the multi thickness fire rings yet? We had the the sleeve clamping tool that sat over the sleeve, to measure flange protrusion, and after measuring that, we selected the proper thickness fire rings for the head gasket. Just wondering about that. We had one of the first 630s produced, up on the farm and it was a real arz ache. Loren [Reply]  [No Email]