Abstract: Vapors in the fuel tank of a vehicle are collected in a carbon canister. An ejector or aspirator is used to purge the carbon canister in a pressure-charged engine in which a positive pressure exists in the intake. A compact ejector includes a substantially planar flange and a venturi tube coupled to the flange with a central axis of the venturi tube substantially parallel to the flange. By manufacturing the ejector in two pieces, dimensions within the ejector: throat, converging section, and diverging section, is more accurate than prior art manufacturing techniques thereby providing better flow characteristics throughout the boost range.

Abstract: Vapors in the fuel tank of a vehicle are collected in a carbon canister. An ejector or aspirator is used to purge the carbon canister in a pressure-charged engine in which a positive pressure exists in the intake. A compact ejector includes a substantially planar flange and a venturi tube coupled to the flange with a central axis of the venturi tube substantially parallel to the flange. By manufacturing the ejector in two pieces, dimensions within the ejector: throat, converging section, and diverging section, is more accurate than prior art manufacturing techniques thereby providing better flow characteristics throughout the boost range.

Abstract: Connectivity is tested using different locations and contexts selected from different possible failure zones. The failure zones may include: client failure zones; Internet failure zones; and online service failure zones. The results relating to different connectivity tests performed using the different failure zones are correlated and analyzed in an attempt to determine a root cause of the connectivity issue. For example, the root cause may be determined to be a configuration problem of the client, a problem with the client's networking equipment, an ISP problem, an Internet backbone problem; a problem of the online service, and the like. Different contexts may also be used when performing the tests. These results may be compared to the other connectivity test results. The results from the tests may be provided to the client experiencing the problem. Aggregated test results may also be used to detect service wide issues and trigger an alert.

Abstract: Connectivity is tested using different locations and contexts selected from different possible failure zones. The failure zones may include: client failure zones; Internet failure zones; and online service failure zones. The results relating to different connectivity tests performed using the different failure zones are correlated and analyzed in an attempt to determine a root cause of the connectivity issue. For example, the root cause may be determined to be a configuration problem of the client, a problem with the client's networking equipment, an ISP problem, an Internet backbone problem; a problem of the online service, and the like. Different contexts may also be used when performing the tests. These results may be compared to the other connectivity test results. The results from the tests may be provided to the client experiencing the problem. Aggregated test results may also be used to detect service wide issues and trigger an alert.