2008-11-14

I finally found the culprit

One month ago, my wife's car had a dead cylinder. It was cylinder #3. It passed all the usual tests: spark plug sparking, compression test showed 170psi across all cylinders, fuel injector ticking, presence of fuel injector signal. But it just didn't want to start.

Peering down the cylinder hole, I noticed a pool of oil on top of the piston. A leaking valve stem seal could put too much oil into they cylinder and foiled the proper mixture for combustion. So I replaced them and cylinder #3 was still dead.

I then wanted to double check the compression test figures. It showed 170psi for all cylinders. That was a good figure, but it measured only the peak compression and did not show there was enough compression at the right time. So I bought Harbor Freight Tool's leak down cylinder tester for $30.
   

But they showed minimal leakage.

I was desperate by this time. I decided to take a look at the fuel injector. Two years ago I replaced fuel injector for cylinder #3 because it went bad. So I was very doubtful that the fuel injector could go bad again within just 2 years. But I was desperate. 

Just for the record, it's possible to remove the fuel injector harness (fuel rail) without removing the intake plenum. You need to remove the bracket that secures the accelerator cable though. The bracket is secured by 1 bolt on the cylinder head and 2 studs on the intake plenum. Remove the bolt and twist open the studs with vice grips. Doing so will damage the studs. I replaced the studs with bolts. Good riddance since I hate dealing with studs in general. 

That's when I found the culprit. Compare cylinder 1 and 3's fuel injectors:



No wonder cylinder #3 was dead. The bad o-ring must had been leaking fuel into the cylinder.
It seemed that the replacement pintle cap I used was too wide. When securing the fuel injector into the harness, the smaller opening on the harness pushed the cap against the o-ring.

Fortunately I had spare pintle caps. It was a good thing I didn't cheapen out two years ago by ordering more than I needed. I trimmed the rim of one and installed it.

That's all it took to bring the cylinder operational again.

Installing and removing recessed valve keepers

Nissan Sentra GA16DE, as is the case with many other Japanese engines, have recessed valve. As such, a common valve spring compressor design like the one below won't work.



One tool that can work (or rather be made to work) with recessed valves is Leslie 36200.



To install the valve keepers, use it without the black attachment. Just position it on top of the valve keepers and push down. It has a strong magnet at the end so as you push down the valve spring retainer,  the magnet will capture the keepers. 


A valve spring retainer and valve keepers.


But as it was, its diameter was too big for the valve cylinder. So it needed to be filed. I didn't have a grinder so  it took me 3 hours while watching Pink Panther to file it down. Oh good times.




The yellow zip tie represented my target diameter. It was set to a slightly smaller diameter than the valve cylinder's.



I pushed the zip tie as far down as possible and marked places that were still thick.



1.5" was deep enough for GA16DE.

I don't have a picture of using it to remove the valve keepers, but here's one of me using the installation attachment. Just assemble the valve spring, retainer and keeper, and push down with the tool. Note that I was posing for the picture because I didn't take some while I was doing the actual installation. In a real installation picture, you should see an air compressor hose going into the cylinder or a string of nylon rope to float the valves up.


If you do not have enough power to push down the tool with your hand (awkward position, short stature, etc.), you can try pushing down the tool with your body weight as pictured above. Use a piece of wood to spread the pressure and push down. This works for the intake valves too which are positioned further inside the engine and may not allow you to push down effectively.

Water pump old vs new

From 1994 Sentra GA16DE 1.6L:


new vs old water pump. The old one had been on the car for 5 years and was leaking.


2008-09-25

darcs recorded modifications to ghost files

I was trying to branch out a one year old project, but got a strange error:

$ darcs get +DBMigration DBMigration.copy
Unapplicable patch:
Mon Jul 23 14:53:41 EDT 2007 Yohanes Santoso
* added sisc-1.16.6 external package
darcs: ./src/com/example/DBMigration/Frob1.class: openBinaryFile: does not exist (No such file or directory)



I checked the changelog and found that the second patch on the tree recorded modifications to files that were never added to the repository:


$ darcs changes -s | tail
Mon Jul 23 14:53:41 EDT 2007 Yohanes Santoso
* added sisc-1.16.6 external package

A ./external_package/
A ./external_package/sisc-1.16.6.zip
M ./src/com/example/DBMigration/Frob1.class
M ./src/com/example/DBMigration/Migrate.class
M ./src/com/example/DBMigration/TemplateRepository.class

Mon Jul 23 10:19:02 EDT 2007 Yohanes Santoso
* initial import

A ./src/
A ./src/com/
A ./src/com/example/
A ./src/com/example/DBMigration/
A ./src/com/example/DBMigration/Frob1.java
A ./src/com/example/DBMigration/Migrate.java
A ./src/com/example/DBMigration/TemplateRepository.java


The imported files were the java source files, but somehow that patch recorded modifications to the class files which were never imported.

I tried many ways to fix this so I can get my branch, but found modifying the patches repository directly was the only one that worked.

Patch files are stored in _darcs/patches directory. They are gzip-ed text files. Each represent a changeset (darcs record). I located all the files that contain references to these .class files, and edited them out. It worked!

2008-09-19

Brokers meltdown

Today started with yet another rally. S&P 500 is currently at 105% of yesterday's closing, which itself was also a 105% of the closing on the day before yesterday.

Crazy. Now I'm trying to dump stocks I've been buying on the cheap, but my brokers (tradeking and etrade) websites are absolutely crawling. The tradeking one even crashed briefly.

Come on, come back up quickly, I need to sell my stocks to this frenzied people.

2008-09-04

Which of the following is the largest?

Gish Gallop

Hah! I've been looking for this exact phrase for sometime:

Gish Gallop


it is a debate technique that drowns the opponent in bullshits, lies and half-truths. The opponent is left having to explain and correct the claims lest he is assumed to accept them.

2008-08-14

A much easier way to access Samba share on Linux guest on Windows host

There is a much simpler solution to my earlier's one.

Steps:

  1. Create a VirtualBox's HIF and attach it to the VM.
  2. Set its IP address to, say, 192.168.2.1.
  3. Start the guest OS.
  4. From within the guest OS, give a static address to the HIF, say, 192.168.2.2.
  5. From host OS, make sure you can ping 192.168.2.2
  6. From the guest OS, make sure you can ping 192.168.2.1

This establishes a private network between the host and the guest. The guest is perceived as another node in the network hosting a Samba share.

VirtualBox: Accessing Samba share on Linux guest on Windows host

Environment: VirtualBox 1.6.4 (latest as of 2008-08-14) running on Windows XP SP3. Guest is a Debian GNU/Linux.

The goal is to have the host Windows able to mount a Samba share provided by the guest as long as the Samba instance is running. To accomplish that, we are going to create a loopback adapter interface on the host, use VirtualBox's HIF on the guest, and bridge the two interfaces together.

Steps:

  1. Add a Microsoft Loopback Adapter device (through ControlPanel->Add Hardware).
  2. Create a VirtualBox's HIF and attach it to the VM.
  3. Go to Control Panel->Network Connections.
  4. Highlight the loopback device and the HIF, and right-click 'Create Bridge'.
  5. Go to the newly created bridge's property and set its IP address to, say, 192.168.2.1. The guest OS will be able to contact the host OS with this address.
  6. Start the guest OS.
  7. From within the guest OS, give a static address to the HIF, say, 192.168.2.2.
  8. From host OS, make sure you can ping 192.168.2.2
  9. From the guest OS, make sure you can ping 192.168.2.1
At this point, from the host Windows, you should be able to do this:

net use e: \\192.168.2.2\the_share_name "password_for_share" /user:username_for_share /persistent:no


Update 2008-08-14: You don't have to create a bridge. There's a simpler method.

2008-07-23

Apheresis left me weak

Yesterday a blood donation bus came by the office for the quarterly donation drive. I'd donated whole blood twice before; but this time, the bus had an apheresis machine for doing Double Red Blood Cell process.

Human has an average of 12 units of blood (a unit is 450ml). It is composed primarily of plasma (55%) and red blood cells (45%). A whole blood donation removes one unit of this mixture. A Double Red Blood Cell procedure removes one unit of only RBC, which is about the same amount of RBC removed in 1/4.5= 2.2 whole blood donation.

I had one needle stuck into a vein on the inside of elbow. Blood was first drawn into the machine. It then separated out the whole blood to plasma and RBC. The plasma and some saline were returned to the vein through the same needle. This cycle was repeated four times. The procedure took 40 minutes vs. 30 minutes for whole blood.

When the plasma was being returned, I could feel that it was cold. My fingertips and lips were prickling because of the cold. I was at that point where I would almost start shivering.

I felt weak throughout the day, weaker than after doing whole blood donation. When I got home, I slept almost immediately. I felt good about donating, though.