omniomni/omni-engineering huggingface dataset:
Mitsubishi 3B2 engine. The Mitsubishi 3B2 engine is a family of all-alloy three cylinder engines developed by Mitsubishi Motors, first produced in December 2005 at the company's Mizushima powertrain facility in Kurashiki, Okayama, for introduction in their 2006 Mitsubishi i kei car. All engines developed within this family have aluminum cylinder block and head, double overhead camshafts, four valves per cylinder, and MIVEC continuous variable valve timing.

The 3B20 was designed with the "rear midship" layout in mind but is not limited to that. The basic dimensions chosen reduced the powerplant's height, the cylinder block's structure was simplified, a timing chain was adopted, modularized components were used for the oil and water pumps, engine mounts, and fuel system. The aluminum construction and lightweight parts and materials in the manifolds helped reduce the weight of the engine by 20 percent compared with its iron-block 3G83 predecessor, while gains were also seen in torque, fuel economy and emissions. Bore pitch is 80 mm.

The preliminary version of the  engine was first seen in the "i" Concept test car introduced in 2003, and used Mitsubishi's Smart Idling system which turns off the engine automatically when the vehicle is stationary, and can restart it within 0.2 seconds. So equipped, Mitsubishi claimed the prototype was capable of fulfilling the "three litre initiative" for gasoline engines, meaning fuel consumption of no more than .

The larger  capacity of the development engine was outside the limits of the kei class in Japan and was introduced in the second generation of the smart fortwo.

Specifications

3B20 

Applications:
 2006 - 2013 Mitsubishi i
 2013 - 2019 Mitsubishi eK 
 2013 - 2019 Nissan Dayz
 2014 - 2020 Mitsubishi eK Space 
 2014 - 2020 Nissan Dayz Roox

3B20T 

Applications:
 2006 - 2013 Mitsubishi i
 2013 - 2019 Mitsubishi eK 
 2013 - 2019 Nissan Dayz
 2014 - 2020 Mitsubishi eK Space 
 2014 - 2020 Nissan Dayz Roox

3B21 
This engine is also known as Mercedes-Benz M132 E10

Applications:
 2007 - 2014 Smart Fortwo

3B21T 
This engine is also known as Mercedes-Benz M132 E10 AL

Applications:
 2007 - 2014 Smart Fortwo

See also 
 List of Mitsubishi engines

References 

3B2
Straight-three engines
Gasoline engines by model
XPP. XPP may refer to:
 Poplar River Airport, the IATA code for the airport in Canada
 XML Professional Publisher, a standards-based, high performance, content formatting and publishing application
 XML Pull Parsing, a method of parsing an XML document, StAX parsers are an implementation of a pull parser.
 eXtreme Processing Platform, a processor architecture
 XPP-AUT, a tool for solving stochastic, differential, and difference equations, amongst others. 
 X++, the programming language behind Microsoft Dynamics AX
Gate (airport). A gate is an area in an airport terminal that controls access to a passenger aircraft. While the exact specifications vary from airport to airport and country to country, most gates consist of a seated waiting area, a counter and a doorway leading to the aircraft. A gate adjacent to the stand where the aircraft is parked may be a contact gate, providing access by way of a jet bridge, or a ground-loaded gate, providing a path for passengers to leave the building to board via mobile stairs or airstairs built into the aircraft itself. A remote stand serves an aircraft stand further away, providing access to ground transportation to move passengers between the gate and the stand, where they board via stairs.

Each gate typically corresponds to one parking stand on the airport's apron. A gate that provides access to multiple stands/jet bridges may have separate, designated doorways – sometimes termed sub-gates – for each stand. Commercial airport stands have airside components to facilitate passenger boarding and aircraft ground handling.

While the term gate precisely refers only to the point of access for passengers, and the area where the aircraft itself is parked is precisely termed an aircraft stand, in commercial passenger aviation the term gate is also used to refer to the gate and aircraft stand together as a single area.

Customs and immigration controls

United States
At most domestic gates, a single doorway connects the passenger waiting area with the jet bridge.  International gates at U.S. international airports always have a second doorway to a separate corridor system that leads directly to the airport's U.S. Customs and Border Protection port of entry facility.  For international arrivals from airports without preclearance, the door leading to the waiting area is closed and all arriving passengers are directed through the second doorway to CBP immigration and customs inspection.

Jet bridge vs airstair
Before the era of the jet bridge or jetway, airline passengers embarked onto the aircraft from ground level via airstairs. If initially indoors, passengers would exit the waiting area through a door to the outside and then passengers would proceed to the airstairs leading to the aircraft door. This method is still used for boarding smaller planes or boarding at smaller airports.

Ownership
The equipment is either airport or airline property, in most cases airport infrastructure.

Gallery

References

Types of gates
Airport infrastructure
ZyWeb. ZyWeb is an online webpage authoring tool, created and owned by ZyNet Ltd, and is currently at version 3.1. It was an early adopter of an entirely server-based solution. ZyWeb was created to enable non-technical users to create and publish websites without the need for any design, authoring or technical skills.

History
ZyWeb has been in service since 1998. The initial development was by two British companies with a common background in the world of Acorn Computers, part of the ancient history of personal computing. Xara Ltd (www.xara.com), which had grown out of Computer Concepts, brought their experience with vector graphics to provide what remains one of ZyWeb's USPs, its "smart graphics". ZyNet Ltd (www.zynet.net), which had grown out of Minerva Software, brought their experience as one of the earliest ISPs in the UK. 

Once the product was launched, the two companies joined to form a new company, known as Zy.com, and this company followed the all-too-familiar progress of so many others during the dot com bubble of the 1990s. A something-for-nothing business model drove explosive growth in the user base, with numbers in the millions at its peak. Venture capital was attracted and millions of dollars were burned before the bubble burst and Zy.com collapsed. However, unlike so many other services, ZyWeb survived this period intact. One of the original founders, ZyNet Ltd, purchased the assets from the liquidated company and continued to develop and improve the service with a more viable business model.

Information
ZyWeb is founded on a Windows platform, using ASP/VBScript to wrap up custom COM objects, largely written in C++. When development started in 1998, the available platform was Windows NT3.51 running IIS3. This suffered from a host of serious technical problems which had to be solved by either writing replacement code (e.g. the system uses its own session manager rather than the one provided by IIS) or by delegating operations to other platforms. A Linux based accelerator sits between the Windows cluster and the Internet and this provides a range of other services which were unavailable or unusable on Windows NT3.51. All this ran on a large collection of commodity servers which grew rapidly as the userbase expanded and came to include specialist hardware such as a NetApp filer. Today, things have moved on and ZyWeb runs on a relatively small cluster of modern servers with current editions of Windows which do not suffer nearly as many problems. However an updated Linux accelerator remains in place and continues to provide important additional services, particularly email management.

See also
 BrowserStack

External links
Official Website (Archived)
Web Design & Development

Web development software
HTML editors
GAM-67 Crossbow. The GAM-67 Crossbow was a turbojet-powered anti-radar missile built by Northrop's Ventura Division, the successor to the Radioplane Company who developed the Crossbow's predecessor, the Q-1 target drone.

Development
In the late 1940s, the Radioplane Company developed a set of prototypes of the Q-1 target series, which used pulsejet or small turbojet engines. Although the Q-1 series was not put into production as a target, it did evolve into the USAF RP-54D / XB-67 / XGAM-67 Crossbow anti-radar missile, which was first flown in 1956. It was also considered as a platform for reconnaissance, electronic countermeasures, and decoy roles.

The Crossbow had a cigar-shaped fuselage, straight wings, a straight twin-fin tail, and an engine inlet under the belly. It was powered by a Continental J69 turbojet engine, with 4.41 kN (450 kgf/1,000 lbf) thrust. Two Crossbows could be carried by a Boeing B-50 Superfortress bomber, while four Crossbows could be carried by a Boeing B-47 Stratojet bomber.

The Crossbow's speed was not enough to allow it to get far ahead of the launching bomber before it ran out of fuel. Only 14 Crossbows were built before the program was cancelled in 1957, in favor of the Longbow, essentially a supersonic version of the same concept. Longbow was eventually cancelled as well. None of the alternative roles were taken up either, with all work on the concept ending in 1960. However, it did point the way to the range of missions that would be performed by UAVs in later decades.

References

 Early versions of this article contained material that originally came from the web article Unmanned Aerial Vehicles by Greg Goebel, which was published into the Public Domain.

GAM-067
GAM-067
Beechcraft MQM-61 Cardinal. The MQM-61 Cardinal is a target drone designed and built by Beechcraft.

Development

While the Radioplane BTT was a popular piston-powered target, such a simple target was relatively easy to build and it developed competition. In 1955 Beechcraft designed the Model 1001, as the initial version of this target drone was designated, in response to a US Navy requirement for gunnery and air-to-air combat training. Production of the type began in 1959, with the drone being given the Navy designation of KDB-1, later MQM-39A. The Model 1001 led to the similar Model 1025 for the US Army, which gave it the MQM-61A designation. Beech also designed a variant powered by a turbojet engine and designated Model 1025TJ, but nobody bought it.

The MQM-61A was a simple monoplane with a vee tail. It was substantially larger than the MQM-36 Shelduck, and powered by a 94 kW (125 hp) McCulloch TC6150-J-2 flat-six, air-cooled, two-stroke piston engine driving a two-blade propeller. It could tow banners or targets of its own, with two targets under each wing, and also carried scoring devices. Launch was by RATO booster, recovery was by parachute.

A total of 2,200 Cardinals of all variants were built, the majority for the US Army, with the rest operated by the US Navy, the US Marine Corps.

Variants 
Model 1001
Designated KDB-1 by the US Navy, later redesignated MQM-39A.
Model 1013
Development of the Model 1001 for aerial reconnaissance powered by a six-cylinder  McCulloch engine.
Model 1025
Designated MQM-61A by the US Army.
Model 1025TJ
Proposed turbojet-powered variant of the Model 1025.

Surviving aircraft
 MQM-61 on display at the Aviation Unmanned Vehicle Museum in Caddo Mills, Texas.

Specifications (MQM-61A)

References

External links

MQM-061
1950s United States special-purpose aircraft
Target drones of the United States
Single-engined tractor aircraft
High-wing aircraft
Single-engined piston aircraft
Aircraft with auxiliary rocket engines
Aircraft first flown in 1957
Miller Electric. Miller Electric is an American arc welding and cutting equipment manufacturing company based in Appleton, Wisconsin. Miller Electric, has grown from a one-man operation selling products in northeastern Wisconsin to what is today one of the world's largest manufacturers of arc welding and cutting equipment.

Overview 
In 1929, Niels Miller designed a small arc welder for "stick welding" that could operate on the electrical supplies in rural Wisconsin that was lighter and less expensive than the DC rotary units previously available. The first machine was built from recycled scrap steel and coil windings in his basement.

In 1935, Miller Electric Mfg. Co. was incorporated. Al Mulder, Miller's sole engineer, invented the world's first high frequency-stabilized AC industrial welder, making AC welding practical for use in factories and construction.

Miller Electric developed the Millermatic in 1971, combining the previously separate units of power source and wire feed into one unit, bringing MIG welding within reach of a wider market.

In 1993, following the death of the company's heir, Miller Electric was purchased by Illinois Tool Works (ITW), a multi-national company based near Chicago.

The company regularly exhibits new products at trade fairs including SEMA.

ITW 

ITW had much in common with Miller Electric in terms of business philosophy, and in 1992 it was ranked as one of the 100 "Most Admired American Corporations" by Fortune magazine. ITW brought to Miller the resource base and global perspective needed to further strengthen the company's position as a world leader in the welding industry.

In 2002, it became the first U.S. welding equipment manufacturer to comply with the new ISO 9001:2000 standard.

Products list 
Miller electric manufactures a lot of products related to arc welding. Some of the important products they manufacture are listed below:

 Welders
 MIG(GMAW)
 TIG(GTAW)
 Stick(SMAW)
 Engine Driven
 Wire Feeders
 Welding Intelligence
 Welding safety equipment
 Helmets
 Weld Mask
 Caps
 Safety Glasses
 Gloves
 Apparel
 Fume Extractors
 Respiratory

References

External links 
 Official Website

Companies based in Wisconsin
Machine tool builders
Hassan Allam Holding. Hassan Allam Holding is one of the largest companies in Egypt and the MENA region, with more than 85 years of experience in the engineering, construction, and infrastructure spaces. It specializes in engineering and construction and investment and development. The company also taking solid strides in renewable energy, water, logistics, mobility, and social infrastructure.

The group have more than 45,000 employees and a portfolio of projects spanning from solar power and water to petrochemicals facilities, museums, airports, and thousands of kilometers of roads and bridges across the region.

On the engineering and construction front, the group is ranked as one of the Top 250 Global Contractors and ranked in the Top 225 International Design Firms. The group offers a robust, fully integrated engineering and turnkey contractor solutions for the full scope of EPC services in power, petrochemical, oil & gas, water, and wastewater treatment plants and transmission lines, roads & bridges, industrial plants, malls, hotels, stadiums and sports facilities and mixed-use developments.

On the investment and development front, Hassan Allam Utilities is the investment and development arm for the group operating across four key verticals focused on sustainable infrastructure to address service and availability gaps in water, energy, social infrastructure, and transport and logistics across Egypt and MEA.

See also 
List of companies of Egypt

References

External links 
 

1975 establishments in Egypt
Construction and civil engineering companies of Egypt
Construction and civil engineering companies established in 1975
Conglomerate companies of Egypt
BNU (software). BNU is a high-performance communications device driver designed to provide enhanced support for serial port communications. The BNU serial port driver was specifically targeted for use with early (late 1980s - 1990s) DOS-based BBS software. The reason for BNU and other similar enhanced serial port drivers was to provide better support for serial communications software than what was offered by the machine's BIOS and/or DOS being used on the machine. Having serial port support as provided by BNU and other similar drivers allowed the communications software programmers to spend more time on the actual applications instead of the depths and details of how to talk to the serial ports and the modems connected to them. Sending communications data across a modem link was a lot more involved than sending data to a serial printer which was basically all that was originally capable of being done with the existing serial port software support.

BNU was written by David Nugent as an experimental driver for serial communications following the FOSSIL specification. David released BNU to the public in 1989 and its use in the BBS world spread rapidly. BNU was one of only two or three available FOSSIL drivers for the IBM PC compatible hardware and MS-DOS/PC DOS operating system. Because of this, BNU has been one of the most widely used MS-DOS FOSSIL communications drivers. 

BNU was mainly used with DOS-based Bulletin Board System (BBS) software written in the late 1980s to mid-1990s. It is not used by Windows-based BBS software, but BNU can be used under Windows NTVDM to run DOS-based BBS software under Windows. BNU and other similar drivers were not limited solely to being used in the BBS world. The enhanced capabilities they offered were also used to easily communicate with other serially connected devices for the same reasons that the FOSSIL specification and FOSSIL drivers were originally created. That reason, as noted above, was to separate the details of serial port communications from the actual application. The software's programmers only needed to talk to the serial driver in a standardized way to send and receive their data.

The name "BNU" was originally a rip-off of AT&T's "BNU UUCP", and in that context meant "Basic Networking Utilities". The author of BNU, David Nugent, felt that the acronym was particularly apt for BNU's function. BNU was also called "Bloody Nugent's Utility" because it was written by David Nugent as one of his many BBS related utilities and it was not known at the time what the acronym "BNU" actually stood for.

The BNUFAQ used to be posted in the Fidonet BNU support echo by the author. This saved text file is the last official posting of this FAQ by David Nugent, BNU's author.

References 

Device drivers
FOSSIL
NetFoss. NetFoss is a popular Network FOSSIL driver for Windows.
A FOSSIL is a serial communications layer to allow DOS based software to talk to modems without dealing with hardware I/O and interrupts.

A Network FOSSIL redirects such software to a TCP/IP address rather than to a serial modem.
NetFoss is faster than other FOSSIL drivers, due to being written in 32-bit assembly language.
It allows Zmodem transfers at up to 280,000 CPS.

NetFoss was developed in 2001 by pcmicro, and was released as freeware. Several minor updates have been released since then. The current version can be downloaded from http://netfoss.com.

References
 NetFoss Users Guide
 FOSSIL implementation and use, FidoNet Technical Standards Committee
 Interfacing to a FOSSIL Communication Driver, Dr. Dobb's Journal 
 The BBS FAQ, Chapter 6.09: FOSSIL DRIVERS

External links
 http://netfoss.com

FOSSIL

sv:Fido Opus Seadog Standard Interface Layer
zh:FOSSIL
X00. X00 was a popular DOS-based FOSSIL driver which was commonly used in the mid-1980s to the late 1990s and is even still used today.  FOSSIL drivers were mainly used to run BBS software under MS-DOS. X00 can also be run under Windows, or even Linux and DOSEMU environments, to allow FOSSIL-aware MS-DOS based applications to function.

X00 was developed by Raymond L. Gwinn from 1989 until 1993. The final release version was version 1.50, with a later beta version 1.53 which added support for baud rates above 38400. X00 is free for non-commercial usage.  X00 included many enhancements to the FTSC FOSSIL revision 5 specifications, which were later used in other FOSSIL drivers such as ADF and NetFoss.

Gwinn moved on to develop a replacement serial port driver for OS/2 called SIO. SIO contained a virtualized FOSSIL (VX00) that could be loaded if applications needed FOSSIL support.

References

Device drivers
FOSSIL
Hawker Hawfinch. The Hawker Hawfinch was a British single-engined biplane fighter of the 1920s. It was unsuccessful, with the Bristol Bulldog being selected instead.

Development
The Hawker Hawfinch fighter aircraft was designed in 1925 as a replacement for both the Armstrong-Whitworth Siskin and the Gloster Gamecock fighters. It participated in the  competition to meet Specification F9/26, together with other aircraft manufacturers, that included nine different designs, of which five were built. The Hawfinch first flew in March 1927. The Bristol Bulldog and the Hawfinch were considered to be the best of the aircraft evaluated, and were selected for more detailed evaluation. The contract was finally awarded to the Bristol Bulldog, because of its slightly higher maximum speed as well as being easier to maintain. After the completion of the competition, the prototype Hawfinch was used for experimental purposes, being tested with single-bay wings and with a twin-float undercarriage.

Only one prototype was built.

Description
The Hawfinch was a two-bay biplane with staggered wings. The structure was the patented Hawker metal tube & "fishplate" system, with fabric covering. It was the first all-metal fighter to be built by Hawker. The powerplant was initially a Bristol Jupiter VI engine, but this was changed to a Jupiter VII (450 hp/336 kW) before the performance trials. The armament consisted of two Vickers machine guns synchronised to fire through the propeller.

Specifications (Hawfinch (Jupiter VII))

See also

References

  

1920s British fighter aircraft
Hawfinch
Single-engined tractor aircraft
Biplanes
Aircraft first flown in 1927
Powerware. Powerware is an Eaton Corporation brand (registered in some countries) for power quality related products such as uninterruptible power supplies (UPS) and surge protection, ranging from protection of single computers (PCs) to industrial power backup systems. The brand also includes DC products for IT and telecommunications applications ranging from small customer-premises equipment to the largest telephone exchanges and switching centers.

Eaton Corporation acquired the Powerware company from Invensys in 2004, and after fully integrating the workforce into its Power Quality Services division, has continued to use the Powerware brand.

External links
Eaton's Power Quality products

2004 mergers and acquisitions

pl:Eaton
Primearth EV Energy. Primearth EV Energy Co., Ltd. (abbreviated as PEVE) is a Japanese manufacturer of prismatic nickel–metal hydride (NiMH) and lithium-ion battery packs for hybrid electric vehicles, located in Shizuoka Prefecture, Japan. PEVE's products had been solely based on NiMH until early 2011 when the company has started mass production of Li-ion battery.

History
The company, originally called Panasonic EV Energy Co. until 2 June 2010, was founded in 1996 as a joint venture between Toyota and Panasonic, with Panasonic holding 60% of the capital. Panasonic sold 40.5% of the company to Toyota as a condition of purchasing Sanyo. Panasonic decided to reduce its stake in PEVE to speed up the process of getting approvals from antitrust authorities in China and the U.S. The planned purchase of Sanyo would hand Panasonic a market share of around 80% in nickel hydride batteries.

PEVE has supplied battery packs for HEVs and PHEVs mainly of Toyota, including the Toyota Prius, but also of Honda and General Motors.

In 2020, Panasonic and Toyota have formed the second EV battery joint venture named Prime Planet Energy & Solutions (PPES) that would focus on the development and manufacturing of Li-ion battery and a solid-state battery.

See also
 Sony Energy Devices Corporation
 Prime Planet Energy & Solutions

References

External links
Official Website
LiFePO4 Battery
P970BAT-4 Battery

Electric vehicle battery manufacturers
Motor vehicle battery manufacturers
Panasonic