Went to the station and got EVAP and EGR not ready
Found the owner’s manual here. Page 613 has detailed steps about how to get the car ready for emission test.
It turns out that the car has self-test to see if the car is ready for emission test. You just need to do this:
To check if they are set, turn the ignition switch to ON, without starting the engine. The malfunction indicator lamp will come on for several seconds. If it then goes off, the readiness codes are set. If it blinks five times, the readiness codes are not set.
I followed the steps on my HRV and got the video(GIF) below. The engine (malfunction indicator lamp) did blink 5 times. No wonder my car failed the emission test.
(Going to follow the instructions on page 613 below)
Fill the gas tank to approximately 3/4 full.
Park the vehicle and leave the engine off for 6 hours or more.
Make sure the ambient temperature is between 40°F and 95°F (4°C and 35°C).
Start the engine without touching the accelerator pedal, and let it idle for 20 seconds.
Keep the vehicle in (P. Increase the engine speed to 2,000 rpm, and hold it there for about 3 minutes.
Let the engine idle with your foot off the accelerator for 20 seconds.
7. Select a nearby, lightly traveled major highway where you can maintain a speed of 50 to 60 mph (80 to 97 km/h) for at least 20 minutes. Drive on the highway in (D). Do not use cruise control. When traffic allows, drive for 90 seconds without moving the accelerator pedal. (Vehicle speed may vary slightly; this is okay.) If you cannot do this for a continuous 90 seconds because of traffic conditions, drive for at least 30 seconds, then repeat it two more times (for a total of 90 seconds).
Drive in city or suburban traffic for at least 10 minutes. When traffic conditions allow, let the vehicle coast for several seconds without using the accelerator pedal or the brake pedal.
Park the vehicle and leave the engine off for 30 minutes.
Sports have a lot of numbers to gauge how good a player is. In baseball, there are batting average, ERA, etc. I had been wondering about software developer metrics. We can judge how good a developer is by reviewing his code, but that is very subjective. I’d like to have metrics that show how a good developer brings values to the company.
When I got my second management position, I got my chance to try to develop and implement the metric. Luckily, I also go have a great project manager to work with. He helped collect and report the numbers.
Here are the metrics:
Net Daily Burn: This is the typical velocity in Agile per developer/working days. In a typical iteration, NDB is burned/days in an iteration. However, people can get sick or take vacation. We changed it working days. So this metric tells me how much work the developer can burn per working day.
A higher ADB tells me the developer is good. It could be that the developer works hard(long hours) or is very smart and efficient. For example, if the task is to time how long all data access methods take, instead of writing system.out.println in every data access method, he/she uses AOP.
Average Daily Burn: This is ADB + other dev tasks that are not considered when the estimates were made. Our typical ‘other dev tasks’ are extra time to deal with build issues, unit testing, etc.