1. An engine for a leisure vehicle equipped with an electronic control throttle system configured to operate an actuator for driving a throttle valve based on a drive signal sent from a controller to the actuator in response to a rider’s operation of a throttle operation device to cause the throttle valve of an air-intake device to open or close, the engine comprising:
a first throttle position sensor configured to detect a movement position of the throttle valve; and
a detection device configured to detect at least a predetermined position in an open state or a closed state of the throttle valve;
wherein the controller determines a deviation between the at least predetermined position received from the detection device and the movement position of the throttle valve corresponding to the predetermined position that has been detected by the first throttle position sensor, compensates for a deviation by adjusting the drive signal based on the deviation if the deviation is above a preset value, and sends the adjusted drive signal to the actuator to cause the throttle valve to open or close.
2. The engine for a leisure vehicle according to claim 1, wherein the detection device is an ON-OFF switch, and the predetermined position is obtained from an on-state or an off-state of the ON-OFF switch.
3. The engine for a leisure vehicle according to claim 1, wherein the detection device is a negative pressure sensor configured to detect a negative pressure in a region downstream of the throttle valve of an air-intake passage of the air-intake device, and the predetermined position is obtained from the value detected by the negative pressure sensor.
4. The engine for a leisure vehicle according to claim 1, wherein the detection device is a second throttle position sensor disposed on or in close proximity to a movable member of the throttle valve, and the predetermined position is obtained from the value detected by the second throttle position sensor.
5. The engine for a leisure vehicle according to claim 4, wherein detecting precision of the second throttle position sensor is higher than detecting precision of the first throttle position sensor.
6. The engine for a leisure vehicle according to claim 1, wherein the controller adjusts the drive signal based on the deviation such that a compensation amount per unit time increases as a value of the deviation increases.
7. The engine for a leisure vehicle according to claim 1, wherein the controller is configured to decrease at least one of the number of times of ignition and a fuel feed amount as well as adjust the drive signal, when a value of the deviation is positive and the drive signal is adjusted to decrease an engine speed of the engine.
8. The engine for a leisure vehicle according to claim 7, wherein the controller is configured to determine a rate of decrease in the engine speed per unit time that is associated with the adjusting of the drive signal, based on the engine speed at that point of time such that the rate decreases as the engine speed decreases.
9. The engine for a leisure vehicle according to claim 1, wherein the predetermined position is a slight open position of the throttle valve.
The claims below are in addition to those above.
All refrences to claim(s) which appear below refer to the numbering after this setence.
1. A host client plug-and-play system in a host client communication system where at least one client is controlled by at least one host, comprising:
a host which automatically installs a device driver and control software for identifying and controlling a client to control the client when the client is connected to the host through communication means; and
a client which is connected to the host through the communication means and controlled with the control software installed in the host.
2. The host client plug-and-play system according to claim 1, further comprising a device server which is connected to the host through a wiredwireless network and provides to the host the device driver and control software for allowing the host to identify and control the client.
3. The host client plug-and-play system according to claim 1, further comprising a service server which is connected to the host through a wiredwireless network and provides client based service software and service to the host.
4. The host client plug-and-play system according to claim 2, wherein the device server comprises an authentication unit which authenticates transmission and installation of the device driver and software provided to the host.
5. The host client plug-and-play system according to claim 1, wherein the client comprises a memory which stores the device driver and software for allowing the host to identify and control the client.
6. The host client plug-and-play system according to claim 5, wherein the memory is a non-volatile memory.
7. The host client plug-and-play system according to claim 1, wherein the host and the client are connected to each other through wired or wireless communication means.
8. The host client plug-and-play system according to claim 7, wherein the communication means is one selected among Infrared data association communication (IrDA), universal serial bus (USB), IEEE 1394, RS-232, RS422, RS-485, and Bluetooth communication schemes.
9. A host client plug-and-play method in a host client communication system where at least one client is controlled by at least one host, comprising:
(a) a step of performing device connection between the client and the host;
(b) a step of performing communication compatible operation step between the client and the host;
(c) a step where the host receives a device driver and control software for allowing the host to identify and control the client;
(d) a step where the host installs the received device driver and control software;
(e) a step of performing device identification and communication compatible operation between the host and the client by using the device deriver installed in the host; and
(f) a step where the host controls the client by using the control software installed in the host.
10. The host client play-and-play method according to claim 9, further comprising, after the step (e):
a step where the host connects the service server to transmit client terminal information;
a step where the service server searches supportable client based service software from the client terminal information; and
a step where the host receives the client based service software from the service server and install the client based service software.
11. The host client play-and-play method according to claim 9, wherein the step (b) comprises:
a step where the client loads a virtual device driver of the memory on a controller and executes the virtual device driver;
a step where the client executes a virtual device response process to transmit a client connection response signal to the host;
a step where the host analyses the received client connection response signal to search a standard device driver;
a step where the host loads the searched standard device driver on a memory; and
a step where the host identifies the client and performs communication compatible operation by using the standard device driver.
12. The host client play-and-play method according to claim 9, wherein the step (b) comprises:
a step where the client executes a standard device driver;
a step where the client executes a standard device response process to transmit a client connection response signal to the host;
a step where the host analyzes the received client connection response signal to search the standard device driver;
a step where the host loads the searched standard device driver on a memory; and
a step where the host identifies the client and performs communication compatible operation by using the standard device driver.
13. The host client play-and-play method according to claim 9, wherein the step (c) comprises a step where the client transmits the device driver and control software stored in the memory to the host.
14. The host client play-and-play method according to claim 9, wherein the step (c) comprises:
a step where the client transmits an installation agent to the host;
a step where the host executes the transmitted installation agent to transmit a list of the device drivers and control software which are to be installed in the host to the client; and
a step where the client transmits the device drivers and control software requested by the installation agent to the host.
15. The host client play-and-play method according to claim 9, wherein the step (c) comprises:
a step where the client transmits position information of the device driver and control software to the host;
a step where the host requests the device server for the device driver and control software;
a step where the device serve transmits the requested device driver and control software to the host.
16. The host client play-and-play method according to claim 9, wherein the step (c) comprises:
a step where the client transmits an installation agent to the host;
a step where the host executes the transmitted installation agent to transmit a list of the device drivers and control software which are to be installed in the host to the device server; and
a step where the device server transmits the requested device drivers and control software to the host.
17. The host client play-and-play method according to claim 9, wherein the step (c) comprises:
a step where the clients connects the device server to receive the device driver and control software;
a step where the client transmits the received device driver and control software to the host.
18. The host client play-and-play method according to claim 9, wherein the step (c) comprises:
a step where the client connects the device server to request the device server to transmit the device driver and control software to the host; and
a step where the device server transmits the device driver and control software to the host.
19. The host client play-and-play method according to claim 9, wherein the step (e) comprises:
a step where the host transmits device driver install completion information to the client;
a step where the client executes the device driver;
a step where the client transmits execution information of the device driver to the host and ends executing of a virtual device driver or a standard device driver;
a step of performing device identification and connection between the host and the client by using the device driver; and
a step where the host loads the device driver on a memory and executes the control software.
20. The host client play-and-play method according to claim 9, further comprising, before the step (c), an authentication step for transmitting the device driver and control software.
21. The host client play-and-play method according to claim 20, wherein the authentication step comprises:
a step where the host receives authentication information;
a step where the host transmits the transmitted authentication information to an authentication server;
a step where the authentication server verifies the transmitted authentication information;
a step where authentication success information is transmitted to the host where the authentication succeeds as a verification result;
a step where the host analyzes the authentication success information to inform data transmission permission;
a step where authentication failure information is transmitted to the host where the authentication does not succeed as a verification result; and
a step where the host analyzes the authentication failure information to inform data transmission prohibition.
22. The host client play-and-play method according to claim 9, further comprising, before the step (d), an authentication step for installing the device driver and control software.
23. The host client play-and-play method according to claim 22, wherein the authentication step comprises:
a step where the host transmits terminal information and installation file information to an authentication server;
a step where the authentication server determines where not the terminal information and the installation file information are equal to each other;
a step where authentication success information is transmitted to the host when a file is a normally authenticated file as a determination result;
a step where the host analyzes transmitted authentication success information to install the file;
a step where authentication failure information is transmitted to the host when a file is not a normally authenticated file as a determination result;
a step where the host stop installing the file due to the authentication failure.
24. A host client plug-and-play method in a host client communication system where at least one client is controlled by at least one host, comprising:
(a) a step of performing device connection between the client and the host;
(b) a step of performing communication compatible operation step between the client and the host by using a translation process;
(c) a step where the host receives control software for allowing the host to control the client and installs the control software;
(d) a step where the host performs device identification and communication compatible operation between the host and the client by using a standard device driver; and
(e) a step where the host controls the client by using the control software installed in the host,
25. The host client play-and-play method according to claim 24, wherein the step (b) comprises:
a step where the client executes the standard device driver and the translation process;
a step where the client executes a standard device response process to transmit a client connection response signal to the host;
a step where the host analyzes the received the client connection response signal to search the standard device driver;
a step where the host loads the searched standard device driver on a memory; and
a step where the host identifies the client and performs communication compatible operation by using the standard device driver
26. The host client play-and-play method according to claim 25, wherein the communication compatible operation step comprises:
a step where the host transmits a control command to the client by using the standard device driver;
a step of the client translates the transmitted control command into a form which the client can recognize by using the translation process; and
a step where the client executes the translated control command.