JP7264274B2 - Sensor system, sensor device and host device used therein, and information transmission method in sensor system - Google Patents

Description

The present disclosure relates to a sensor system, a sensor device and host apparatus used therein, and an information transmission method in the sensor system.

As a general-purpose interface for connecting a host device such as a personal computer or a server and various devices (peripherals), a USB (Universal Serial Bus) standard connector may be used. The USB connection supports plug-and-play, which allows devices to be connected and removed without stopping the host device.

In information transmission using USB, the data format between a device and a host device generally differs for each device. In such a system, in order to correctly transmit data between the device and the host device, a process of installing dedicated firmware in the control device of the device and/or the host device and converting the data format into a predetermined format. is performed. As described above, the data format between the device and the host device differs for each device. Therefore, each time a new device is connected to the host device, the corresponding firmware is installed on the device side or the host device side. need to be installed on.

Japanese Patent Laying-Open No. 2006-323612 (Patent Document 1) discloses a configuration in which a host device automatically writes a firmware file to a device when the device is connected to an information processing device (host device).

JP 2006-323612 A

In recent years, as sensors for detecting environmental conditions such as temperature and humidity, sensor devices capable of USB connection have been developed. In such sensor devices, the data format to be transmitted may differ depending on the type of sensor or the manufacturer of the sensor device. In this case, the firmware needs to be set every time a new sensor device is connected to the host device.

The present disclosure has been made to solve the problems described above, and an object of the present disclosure is to provide a sensor system in which a sensor device is connected to a host device, when a sensor device is added, without setting firmware. It is to enable transmission of information between the sensor device and the host device.

A sensor system according to one aspect of the present disclosure includes a host device and at least one sensor device. A plurality of sensor devices can be connected to the host device. Information is transmitted between the host device and the sensor device in a predetermined data format. The predetermined data format is set to a common data format regardless of the type of sensor included in the sensor device connected to the host device.

A sensor device according to another aspect of the present disclosure is connectable to a host device. A sensor device comprises at least one sensor and a processor for processing information from the at least one sensor. The processing device converts information from at least one sensor into a predetermined data format and transmits the data to the host device. The predetermined data format is set to a common data format regardless of the type of the at least one sensor.

A host device according to still another aspect of the present disclosure is connectable to a plurality of sensor devices. The host device has a control device that acquires information in a predetermined data format from the connected sensor device. The predetermined data format is set to a common data format regardless of the type of sensor included in the sensor device connected to the host device.

A method according to still another aspect of the present disclosure relates to a method of transmitting information in a sensor system including a host device to which a plurality of sensor devices can be connected, and sensor devices connected to the host device. A sensor device includes at least one sensor and a processor. The method includes the steps of acquiring information from the at least one sensor, converting the acquired information into a predetermined data format in a processing device, and sending the information converted into the predetermined data format from the processing device to a host. and sending to the device. The predetermined data format is set to a common data format regardless of the type of sensor included in the sensor device connected to the host device.

In the sensor system according to the present disclosure, the data format between the sensor device and the host device is set to a common format regardless of the type of sensor device. This eliminates the need to rewrite the firmware in the host device or the sensor device even when different types of sensor devices are connected to the host device. Therefore, when adding a sensor device, it is possible to transmit information between the sensor device and the host device without newly setting the firmware.

1 is an overall configuration diagram of a sensor system according to an embodiment; FIG. 2 is a functional block diagram of a sensor unit 20 in FIG. 1. FIG. 2 is a functional block diagram of a sensor unit 20A in FIG. 1; FIG. It is a functional block diagram of a sensor unit in a comparative example. It is a figure which shows an example of a sensor ID definition list. It is an example of a command used in information transmission. FIG. 2 is a diagram for explaining a data format used in information transmission between a host device and a sensor device; FIG. 4 is a flowchart for explaining processing of a dev command; FIG. 10 is a flowchart for explaining read command processing; FIG. 4 is a flowchart for explaining processing of a write command; FIG. 10 is a flowchart for explaining processing of an observe/cancel command; FIG.

Hereinafter, embodiments of the present disclosure will be described in detail with reference to the drawings. The same or corresponding parts in the drawings are denoted by the same reference numerals, and the description thereof will not be repeated.

[Overall Configuration of Sensor Stem]
FIG. 1 is an overall configuration diagram of a sensor system 10 according to this embodiment. The sensor system 10 includes sensor units 20 and 20A (hereinafter also collectively referred to as “sensor unit 20”) and a server 40 . The sensor unit 20 and the server 40 are wirelessly or wiredly connected to a network 30 such as the Internet or a LAN (Local Area Network), and are configured to exchange information with each other via the network 30 .

Schematically, in the sensor system 10 , detected values such as temperature detected by sensors included in the sensor unit 20 are transmitted to the server 40 via the network 30 . The server 40 stores sensor detection values received from the sensor unit 20, and processes the stored detection values as necessary. The server 40 also transmits the stored detection values to another control device (not shown).

Sensor unit 20 includes sensor device 100 and host device 200 . The sensor device 100 can be connected to the host device 200 using a USB standard compliant connector. Sensor device 100 includes at least one sensor, as detailed in FIG. The sensor device 100 transmits detection values of the built-in sensor to the host device 200 .

The host device 200 receives sensor detection values from the sensor device 100 . The host device 200 is configured to be capable of wireless communication such as Wi-Fi, and transmits the received sensor detection values to a base station connected to the network 30 using the wireless communication.

The sensor unit 20A is an example in which it is connected to the network 30 by wire. Also, in the sensor unit 20A, a plurality of sensor devices 100A and 100B are connected to the host device 200A. In the following description, the sensor devices 100, 100A, and 100B are also collectively referred to as the "sensor device 100." Also, the host devices 200 and 200A are collectively referred to as the "host device 200".

Note that the host device does not necessarily have to have a communication function with the outside, and may be, for example, a single device without a communication function. Also, when the sensor device 100 is directly connected to the server 40 , the server 40 also functions as the host device 200 .

[Configuration of sensor unit]
(1) Sensor unit 20
FIG. 2 is a functional block diagram for explaining details of the sensor unit 20. As shown in FIG. Referring to FIG. 2, sensor unit 20 includes sensor device 100 and host device 200 as described above.

(sensor device)
Sensor device 100 includes two sensors 110 , 115 , processing unit 120 and USB connector 130 .

Types of sensors included in the sensor device 100 include, for example, temperature, humidity, air pressure, acceleration, angular velocity, illuminance, environmental sound, and the like. Each of sensors 110 and 115 outputs a signal corresponding to the detected physical quantity to processor 120 . In the sensor device 100 of the present embodiment, a case in which two sensors 110 and 115 are provided will be described as an example, but the number of sensors included in the sensor device 100 is not limited to this, and may be one or three. The above sensors may be provided. The type of sensor 110 and the type of sensor 115 may be the same or different.

The processing device 120 includes, for example, a CPU (Central Processing Unit), and executes processing according to pre-stored programs. The processing device 120 acquires detection values detected by the sensors 110 and 115 according to commands from the host device 200 , processes the detection values, and outputs them to the host device 200 .

Processing unit 120 includes sensor firmware 121 and 122 and common firmware 125 . The sensor firmware 121, 122 is software for acquiring information from the sensors 110, 115, respectively. The sensor firmware converts a signal from the corresponding sensor into a physical quantity to be measured. For example, if the sensor is a temperature sensor, the sensor firmware converts the voltage signal output from the sensor into a corresponding temperature value. Therefore, basically, the sensor firmware is different for each corresponding sensor.

The common firmware 125 is software for converting the sensor information converted by each sensor firmware into a predetermined data format. The data format of information output from the common firmware 125 is defined to be common among sensor devices. Therefore, even if the types of sensors included in the sensor devices are different, information can be transmitted to and from the host device 200 in a common data format. A data format in the common firmware 125 will be described later with reference to FIG.

Note that the processor 120 of the sensor device 100 may calculate not only the physical quantity detected by the sensor alone, but also an estimated quantity that can be calculated from the physical quantity. Examples of estimated quantities that can be calculated from physical quantities include a discomfort index calculated from temperature and humidity, or a device failure prediction estimated from acceleration.

The USB connector 130 can be connected to a USB connector 210 provided on the host device 200 . By connecting the sensor device 100 to the host device 200 using the USB connector 130, information can be transferred between the sensor device 100 and the host device 200. FIG. By connecting the host device 200 and the sensor device 100 using a USB connector, the sensor device 100 can be connected to and removed from the host device 200 without stopping the host device 200 .

(host device)
Host device 200 includes a plurality of USB connectors 210 , USB hub 220 , processing device 230 and communication circuitry 240 . USB connector 210 is connected to USB hub 220 . The USB hub 220 individually controls each connection port of the plurality of USB connectors 210 (hereinafter also referred to as “USB port”) to exchange information between the sensor device connected to each USB connector and the processing device 230. to communicate.

Processing device 230 is connected to network 30 via communication circuit 240 and transmits information to and from server 40 . The processing unit 230 acquires sensor information from the sensor device 100 connected to the designated USB port according to the command from the server 40 . The processing unit 230 contains common firmware 235 corresponding to the common firmware 125 of the sensor device 100 . Thereby, the processing device 230 can acquire the sensor information contained in the information in the predetermined data format converted by each sensor device.

(2) Sensor unit 20A
An example of a sensor unit 20A in which sensor devices are connected to different USB ports of a host device will be described with reference to FIG. Referring to FIG. 3, sensor unit 20A includes two sensor devices 100A and 100B and host device 200A. Since host device 200A has the same configuration as host device 200 in FIG. 2, detailed description will not be repeated.

Sensor device 100A includes sensor 110, processing unit 120A, and USB connector 130. As shown in FIG. The sensor device 100B also includes a sensor 115, a processing unit 120B, and a USB connector .

The processing device 120A of the sensor device 100A includes sensor firmware 121 corresponding to the sensor 110 and common firmware 125 . The processor 120A converts the signal from the sensor 110A into the first data format using the sensor firmware 121 and the common firmware 125, and transmits the information to the host device 200A.

The processor 120B of the sensor device 100B includes sensor firmware 122 corresponding to the sensor 115 and common firmware 125 . The processor 120B converts the signal from the sensor 110B into the second data format using the sensor firmware 122 and the common firmware 125, and transmits the information to the host device 200A.

As described above, the common firmware 125 is software that converts sensor information from each sensor firmware into a common data format. That is, the first data format output from the sensor device 100A and the second data format output from the sensor device 100B are common data formats.

Thus, in the sensor unit of the present embodiment, communication is performed between the sensor device and the host device using a common data format regardless of the type of sensor included in the sensor device. Thus, even if the host device does not have firmware for sensors, it is possible to correctly acquire information on sensors of different types.

Information is also transmitted between the host device 200 and the server 40 in the data format used by the common firmware.

(Comparison with Comparative Example)
FIG. 4 is a functional block diagram of sensor unit 20# in a comparative example. Sensor devices 100#1 and 100#2 of sensor unit 20# of the comparative example do not include processor 120 like sensor unit 20 of the embodiment, and sensors 110 and 115 each have USB connector 130. connected directly to Therefore, sensor firmware 231 and 232 corresponding to each sensor is included in processing device 230# of host device 200#.

In sensor unit 20# of the comparative example, signals detected by sensor devices 100#1 and 100#2 are converted into physical quantities to be measured by processor 230# of host device 200#. Therefore, when a sensor device containing a new type of sensor is connected to host device 200# and used, the sensor firmware corresponding to the sensor to be added is transferred to processing device 230# of host device 200#. Additional installation work is required.

On the other hand, in the sensor unit 20 of the present embodiment, the sensor firmware corresponding to each sensor is included in the processor 120 of the sensor device 100, and between the sensor device 100 and the host device 200, the sensor Information is conveyed using a common data format independent of the type of Therefore, even if a sensor device including a new type of sensor is connected to the host device 200, the sensor device can be connected to the sensor without installing the sensor firmware corresponding to the added sensor on the host device 200 side. Information can be obtained.

[Communication protocol]
Next, a communication protocol based on a data format using common firmware will be described with reference to FIGS. 5 to 7. FIG.

(Sensor ID)
FIG. 5 is a diagram showing an example of a sensor ID definition list for defining sensors included in the sensor device 100. As shown in FIG. As noted above, sensor device 100 includes one or more sensors. Therefore, the host device 200 needs to know the type of sensor included in the connected sensor device 100 .

In the example of FIG. 5, sensor IDs are defined according to sensor types included in the sensor device 100 . For example, in the example of FIG. 5, the temperature sensor ID is defined as "AA", the humidity sensor ID as "BB", the illuminance sensor ID as "CC", and the acceleration sensor ID as "DD". An ID corresponding to the sensor type is predetermined and shared between server 40 and sensor device 100 .

Moreover, when the sensor device 100 includes a plurality of sensors, a sensor ID is defined as a combination of the above IDs. For example, for a sensor device containing two temperature sensors, the sensor ID is defined as "AAAA". For sensor devices that include a temperature sensor and a humidity sensor, the sensor ID is defined as "AABB". Furthermore, in the case of a sensor device including three sensors, a temperature sensor, a humidity sensor and an illuminance sensor, the sensor ID is defined as "AABBCC".

This sensor ID is transmitted from the sensor device 100 to the host device 200 and the server 40 when the sensor device 100 is connected to the host device 200 . The server 40 and the host device 200 store a "sensor ID list" (connection information) that associates each port of the host device 200 with the sensor ID of the sensor device 100 connected thereto. This "sensor ID list" allows the server 40 and the host device 200 to grasp the types of sensors included in the sensor devices 100 connected to the respective USB ports of the host device 200. FIG. Based on the "sensor ID list", the server 40 specifies the sensor from which data should be obtained, and outputs a command to the corresponding host device 200 to obtain the detected value of the desired sensor.

When the sensor device 100 is newly connected to the host device 200 and when the sensor device is removed from the host device 200, the "sensor ID list" is updated in the server 40 and the host device 200. FIG.

Note that the sensor ID shown in FIG. 5 is an example, and the sensor ID may be defined in a format other than the above as long as each sensor can be identified.

(command)
FIG. 6 shows an example of instructions (commands) used in information transmission between the host device 200 and the sensor device 100. FIG. In this embodiment, the commands include a "dev" command, a "read" command, a "write" command, an "observe" command, and a "cancel" command.

A “dev” command is a command for acquiring the sensor ID of the sensor device 100 . When the host device 200 detects that the sensor device 100 is connected to the USB port, the host device 200 transmits a “dev” command to the sensor device 100 . Upon receiving the “dev” command from the host device 200 , the sensor device 100 returns its own sensor ID to the host device 200 . The host device 200 updates and stores the sensor ID list based on the received sensor IDs, and transmits the updated sensor ID list to the server 40 .

A “read” command is a command for acquiring the detection value of each sensor in the sensor device 100 . The host device 200 transmits a "read" command to the sensor device 100 of the port specified by the server 40 based on the sensor ID list. The "read" command contains the sensor ID. When the sensor ID included in the “read” command from the host device 200 matches its own sensor ID, the sensor device 100 returns the detection values of each sensor to the host device 200 . For example, when the sensor IDs are defined as shown in FIG. 5, the sensor device 100 returns to the host device 200 data describing the detected values in the order of temperature and humidity when the sensor ID is "AABB".

The “write” command is a command for setting (writing) a predetermined value in the designated sensor device 100 . In the sensor device 100, the state of the sensor device 100 is changed according to the set value. For example, when controlling the lighting/extinguishing of an LED in the sensor device 100 , the host device 200 transmits a “write” command to the target sensor device 100 . In the sensor device 100, the LED corresponding to the value set in the "write" command is lit (or extinguished).

The "observe" command is a command for periodically notifying the sensor device 100 of the designated port of the detected value. Also, the "cancel" command is a command for stopping the periodical detection value notification set by the "observe" command. When the sensor device 100 receives the "observe" command from the host device 200, the sensor device 100 sends the detection values of the sensors included in the sensor device 100 to the host device 200 at predetermined intervals until it receives the "cancel" command. Send. When the sensor device 100 receives the “cancel” command, it stops the periodic notification of the detected value of the sensor.

(data format)
FIG. 7 is a diagram for explaining a data format used for information transmission between the sensor device 100 and the host device 200. As shown in FIG. FIG. 7(a) shows the data format used in the common firmware of this embodiment, and FIG. 7(b) shows the data format used in the comparative example.

Referring to FIG. 7(a), the data format used in the common firmware includes command ID (id), command name (cmd), receiver status (sts), sensor ID (req/res), and A sensor detection value (val) is included.

A command ID (id) is information for specifying a command, and is represented by an arbitrary character string such as "0001" or "abcd". A command ID is uniquely set for each command, and a command output from the host device 200 to the sensor device 100 and a response from the sensor device 100 to the command are linked by the command ID.

The command name (cmd) is information indicating an instruction from the host device 200 to the sensor device 100, and specifically, the command shown in FIG. 6 is set.

The state of the receiving side (sts) is information included in the response of the sensor device 100 to the command from the host device 200 and is information indicating the state of the sensor device 100 . For example, in the response to the "dev" command or "read" command, information indicating that the command from host device 200 was correctly received (for example, a character string of "ok") is set. Note that if there is an error in the command from the host device 200 (for example, the sensor ID does not match), the character string "ng" is set. When the sensor device 100 periodically notifies the host device 200 of the sensor detection value in response to the "observe" command, the character string "notify" is set to indicate notification information.

The sensor ID (req/res) is information for specifying the target sensor, and specifically, the sensor ID information shown in FIG. 5 is set. Further, when the sensor device 100 includes a plurality of sensors having the same sensor ID, the channel number of the target sensor may be set in addition to the sensor ID. For example, if the sensor device 100 includes a temperature sensor (channel 1) and a temperature sensor (channel 2), and you want to obtain the value of the temperature sensor on channel 2, enter the sensor ID "AA" and the channel number "2". A combined character string such as "AA2" is set. Note that “req” is used when the host device 200 makes a request to the sensor device 100 , and “res” is used when the sensor device 100 sends a response to the host device 200 .

As another example, when the character string "AA1CC" is set in the "read" command, a sensor device including three sensors, two temperature sensors (channel 1 and channel 2) and an illuminance sensor, It indicates that the data of the temperature sensor and illuminance sensor of channel 1 are being requested. If the channel number is not set, it means to acquire sensor data of all channels.

The sensor detection value (val) is set with a character string indicating the data of the detection value corresponding to the sensor specified by the sensor ID (res). The information of the sensor detection value (val) is indicated by a list of character strings representing the detection value (numerical value). can be identified. For example, if the sensor detection value (val) is set to "20.1, 60.3" and the sensor ID (res) is set to "AABBCC12", the temperature sensor detection value is 20.1°C. and the detected value of the humidity sensor can be identified as 60.3%.

On the other hand, in the data format in the comparative example of FIG. (val1) to (val4) are set. That is, in the data format of the comparative example, the number of transmittable sensor detection values is limited. Therefore, for example, when a sensor device 100 including five sensors is connected, detection values of all sensors cannot be transmitted.

On the other hand, in the data format of the embodiment, there is one area (val) for storing sensor detection values, and the correspondence between detection values and sensors included in the area is specified by sensor ID information. be. As a result, even if the number of sensors included in the sensor device 100 is five or more, it is possible to transmit the detection value as long as the range of the character string does not exceed the area for storing the sensor detection value.

An example of the "read" command from the host device 200 and the response of the sensor device 100 to it is shown below. Note that the description on the right side of the "semicolon (;)" in each line describes the contents of each line.

<Command from host device>
{
”id”:”0001”, ; Command ID “0001”
”cmd”:”read”, ; command name “read” (reading)
”req”:”AABB” ; Sensor ID “AABB” (Temperature + Humidity)
}

<Response from sensor device>
{
”id”:”0001”, ; Command ID “0001”
”sts”:”ok”, ; Receiver information “ok” (normal reception)
”res”:”AABB”, ; Sensor ID “AABB” (Temperature + Humidity)
``val'': ``20.1, 60.3''; detected value ``20.1°C, 60.3%''
}

An example of periodic detection value notification from the sensor device 100 in response to the "observe" command from the host device 200 is shown below.

<Notification from sensor device>
{
”sts”:”notify”, ; receiver state “notify” (notify)
”res”:”AABB1”, ; Sensor ID “AABB1” (temperature + humidity, temperature only)
”val”:”27.2”; Detected value “27.2°C”
}

[Processing in each command]
Details of the processing executed by the server 40, the sensor device 100, and the host device 200 for each command will be described with reference to FIGS. 8 to 11. FIG.

(dev command)
FIG. 8 is a flow chart for the "dev" command. Referring to FIG. 8, when host device 200 detects that sensor device 100 is connected to the USB port at step (hereinafter step is abbreviated as “S”) 20, at S22 the connection is made. When the sensor device 100 receives the "dev" command from the host device 200 (S30), it sends the sensor ID of the sensor device 100 to the host device 100 in response. 200 (S32).

After acquiring the sensor ID from the sensor device 100 (S24), the host device 200 creates a sensor ID list based on the acquired sensor ID in S26. In the sensor ID list, the USB port to which the sensor device 100 is connected is associated with the sensor ID. Note that the sensor ID list may also include information about sensor devices connected to other USB ports of the host device 200 .

After that, the host device 200 transmits the created sensor ID list and the information of the connected USB port to the server 40 in S28. When the server 40 receives the sensor ID list from the host device 200, it updates the existing sensor ID list. Note that the sensor ID list in the server 40 may also include information on host devices other than the host device 200 that can communicate with the server 40 .

Although not shown in FIG. 8, when the sensor device is removed from the host device, the sensor ID for the corresponding USB port is deleted from the sensor ID list stored in the host device. It is sent to the server 40 .

By controlling the server, the host device, and the sensor device according to the processing described above, when a sensor device is newly connected to the host device, information on the sensor device is acquired using the "dev" command. be able to. This allows the host device and the server to recognize the sensors included in the connected sensor devices.

(read command)
FIG. 9 is a flow chart for the "read" command. Referring to FIG. 9 , when reading the detection value of the sensor included in sensor device 100 , server 40 sends the target USB port to target host device 200 according to the sensor ID list stored in server 40 . A port is designated and a "read" command is transmitted (S40).

When the host device 200 receives the "read" command transmitted from the server 40 (S50), it transfers the received "read" command to the sensor device 100 connected to the designated USB port (S52). .

When the sensor device 100 receives the "read" command transferred from the host device 200 (S60), it acquires the detection value of the target sensor according to the sensor ID described in the command (S62). Then, in S64, the sensor device 100 edits the information to be returned in the common firmware 125 according to the common data format described with reference to FIG. 7 (S64). After that, the edited data is transmitted to the host device 200 (S66).

The host device 200 receives the data including the sensor detection value transmitted from the sensor device 100, adds USB port information to the data, and transmits the data to the server 40 (S54). The server 40 receives the data transmitted from the sensor device 100 in S42. The server 40 extracts and stores desired sensor detection values from the received data. The server 40 displays the stored detection values on a display device (not shown) or transmits them to other control devices.

By performing control according to the processing as described above, the server can acquire the detection value of the desired sensor.

(write command)
FIG. 10 is a flow chart for the "write" command. Referring to FIG. 10 , when server 40 turns on an LED or writes specific data to a specific sensor device 100 , server 40 sends “write” to host device 200 according to the sensor ID list. A command is transmitted (S70). At this time, the server 40 designates the target USB port in the host device 200 .

When the host device 200 receives the "write" command from the server 40 (S80), it transfers the received "write" command to the sensor device 100 connected to the designated USB port (S82).

When the sensor device 100 receives the "write" command transferred from the host device 200 (S90), the sensor device 100 writes designated data to the target sensor according to the sensor ID described in the command (S92).

Data can be written from the server to a desired sensor by performing control according to the above processing.

(observe/cancel command)
FIG. 11 is a flow chart for the "observe" command and the "cancel" command. Referring to FIG. 11, server 40 issues an “observe” command to target host device 200 according to the sensor ID list stored in server 40 when periodically acquiring the detection value of a specific sensor. Send (S100). At this time, the server 40 designates the target USB port in the host device 200 .

When the host device 200 receives the "observe" command from the server 40 (S200), it transfers the received "observe" command to the sensor device 100 connected to the designated USB port (S210).

When the sensor device 100 receives the "observe" command transferred from the host device 200 (S300), it acquires the detection value of the target sensor according to the sensor ID described in the command (S310). Then, in S320, the sensor device 100 edits the information to be returned in accordance with the common data format in the common firmware 125 (S320). After that, the edited data is transmitted to the host device 200 (S330).

The host device 200 receives the sensor information transmitted from the sensor device 100, adds USB port information to the data, and transmits the data to the server 40 (S220). The server 40 receives and stores the data transmitted from the sensor device 100 (S110).

In S<b>120 , the server 40 determines whether or not the user has given an instruction to stop the periodical reading of the sensor detection value to the corresponding sensor (that is, the presence or absence of a cancel instruction). If there is no cancellation instruction from the user (NO at S120), the process returns to S110, and server 40 continues receiving/storing sensor information periodically notified from host device 200. FIG.

When the data transmission to the host device 200 is completed, the sensor device 100 advances the process to S340 and determines whether or not a “cancel” command has been received from the server 40 via the host device 200. FIG. If the "cancel" command transmitted from the server 40 has not been received (NO at S340), the process proceeds to S350, and the sensor device 100 next determines whether or not the predetermined interval time has elapsed. judge.

If the predetermined interval time has not elapsed (NO at S350), the process returns to S340 to determine whether or not the "cancel" command has been received, and waits for the predetermined interval time to elapse. Then, when the predetermined interval time elapses (YES in S350), the process returns to S310, and the sensor device 100 acquires the detection value of the designated sensor, edits it into a common data format (S320 ), the sensor information is transmitted to the host device 200 (S330). That is, when the "cancel" command is not received, the sensor device 100 acquires the detection value of the designated sensor each time the predetermined interval time elapses, and stores the acquired sensor information in the common data format. to the host device 200.

On the other hand, if there is a cancel instruction from the user (YES in S120), the process proceeds to S130 in server 40, and server 40 specifies the USB port of the target sensor and sends host device 200 " send a cancel command.

When the host device 200 receives the "cancel" command from the server 40 (S230), it transfers the received "cancel" command to the sensor device of the designated USB port (S240).

When sensor device 100 receives the “cancel” command from server 40 (YES in S340), it skips step S350 and ends the process. As a result, periodic notification of sensor information from the sensor device 100 is stopped.

By controlling the server, the host device, and the sensor device according to the processing described above, the server and the host device can periodically acquire sensor information from desired sensors.

In the above explanation, the case where a connector conforming to the USB standard is used for connection between the sensor device and the host device, and in particular the case where a connector of USB type-A is used is explained as an example. The connector is not limited to this, and a USB connector of another type (type-B, C, or mini/micro) may be used, or a connector other than the USB connector may be used.

The embodiments disclosed this time should be considered as examples and not restrictive in all respects. The scope of the present disclosure is indicated by the scope of the claims rather than the description of the above-described embodiments, and is intended to include all modifications within the meaning and scope equivalent to the scope of the claims.

10 sensor system, 20, 20A sensor unit, 30 network, 40 server, 100, 100A, 100B sensor device, 110, 115 sensor, 120, 230 processor, 121, 122, 231, 232 firmware for sensor, 125, 235 common Firmware, 130, 210 USB connector, 200, 200A host device, 220 USB hub, 240 communication circuit.

Claims (13)

a host device to which multiple sensor devices can be connected;
at least one sensor device connected to the host device;
the host device and the at least one sensor device communicate information in a predetermined data format,
the predetermined data format is set to a common data format regardless of the type of sensor included in the sensor device connected to the host device;
The common data format includes a command ID, command name, receiver status, sensor ID, and sensor detection value;
The sensor system, wherein the host device and the at least one sensor device are connected using a USB (Universal Serial Bus) standard connector. the at least one sensor device comprising:
a first sensor device having a first sensor and communicating with the host device in a first data format;
a second sensor device having a second sensor of a type different from the first sensor and communicating information in a second data format with the host device;
2. The sensor system of claim 1, wherein said first data format and said second data format are said common data format. the at least one sensor device comprising:
at least one sensor;
a processor for processing information from the at least one sensor;
The processing device is
sensor firmware for obtaining information obtained from the at least one sensor;
3. The sensor system according to claim 1, further comprising common firmware for converting information acquired from said sensor firmware into said predetermined data format. further comprising a server configured to communicate with the host device,
4. The sensor system according to any one of claims 1 to 3, wherein said host device acquires information from a sensor device connected to a connection port specified by said server and transmits the information to said server. 5. The sensor system of claim 4, wherein the server communicates wirelessly with the host device. A channel number is set for the sensor included in the at least one sensor device,
The sensor system according to any one of claims 1 to 5, wherein said sensor ID included in said common data format includes said channel number information. A sensor device connectable to a host device,
at least one sensor;
a processor for processing information from the at least one sensor;
A USB standard connector for connecting with the host device,
The processing device converts information from the at least one sensor into a predetermined data format and transmits the information to the host device;
the predetermined data format is set to a common data format regardless of the type of the at least one sensor ;
The sensor device, wherein the common data format includes command ID, command name, receiver status, sensor ID, and sensor detection value . A host device to which a plurality of sensor devices can be connected,
a USB standard connector for connecting with each sensor device;
a control device that acquires information from the connected sensor device in a predetermined data format,
the predetermined data format is set to a common data format regardless of the type of sensor included in the sensor device connected to the host device ;
The host device , wherein the common data format includes command ID, command name, receiver status, sensor ID, and sensor detection value . The plurality of sensor devices are
a first sensor device having a first sensor and communicating with the host device in a first data format;
a second sensor device having a second sensor of a type different from the first sensor and communicating information in a second data format with the host device;
9. The host device of claim 8 , wherein said first data format and said second data format are said common data format. A method for transmitting information in a sensor system including a host device to which a plurality of sensor devices can be connected and the sensor devices connected to the host device,
the sensor device includes at least one sensor and a processor;
The host device and each sensor device are connected by a USB standard connector,
The method includes:
obtaining information from the at least one sensor;
a step of converting the acquired information into a predetermined data format in the processing device;
transmitting the information converted into the predetermined data format from the processing device to the host device;
the predetermined data format is set to a common data format regardless of the type of sensor included in the sensor device connected to the host device ;
The method , wherein the common data format includes command ID, command name, receiver status, sensor ID, and sensor detection value . a step of, when a sensor device is connected to a connection port of the host device, sending a command from the host device to the sensor device to send sensor information relating to the type of sensor included in the sensor device; ,
11. The method of claim 10 , further comprising transmitting said sensor information to said host device in response to said command. The host device is configured to be able to communicate with a server,
The method includes:
updating connection information indicating the connection status of each connection port in the host device when a sensor device is connected to the connection port and when the sensor device is removed from the connection port;
12. The method of claim 11 , further comprising transmitting said connection information from said host device to said server. A method according to any one of claims 10 to 12 , further comprising transmitting information from said at least one sensor to said host device at predetermined time intervals.

Images