JP2025104069A - Embedded Devices - Google Patents

Abstract

An object of the present invention is to provide an embedded device that can reliably hold a large capacity operation log without affecting the device configuration, even if the embedded device is small in size.
[Solution] The coin mech 11 is an embedded device incorporated in a higher-level main device, and is equipped with an EEPROM 24 that is connected to a CPU 21 on a control board 20 inside the coin mech 11 and temporarily stores operation logs handled by the coin mech 11 in real time, and when a predetermined condition is met, the CPU 21 transfers the operation logs temporarily stored in the EEPROM 24 to another storage medium inside the coin mech 11 or outside the coin mech 11. For example, the operation logs in the EEPROM 24 are transferred all at once to an operation log area in a flash ROM 23.
[Selected figure] Figure 2

Description

The present invention relates to an embedded device that can reliably store large volumes of operation logs without affecting the device configuration, even if the device is small-scale.

Vending machines are equipped with built-in devices such as a coin handling device (coin mechanism) and a bill validator (bill validator). These built-in devices can malfunction due to dirt on the currency, friction, dust, etc., so they have an operating lifespan and it is necessary to know the operating status when a malfunction occurs. For this reason, these built-in devices are designed to store operation logs. Operational data includes the operating time that determines the warranty period of the built-in device, the number of accepted and dispensed currency that determines the operating lifespan, the history and number of malfunctions, sensor data on accepted currency, and communication logs with the higher-level main unit.

Here, in Patent Document 1, an EEPROM (Electronically Erasable and Programmable Read Only Memory), which is a non-volatile memory, is installed in the embedded device, and operation logs within the embedded device are selectively stored.

JP 2004-318472 A

Incidentally, it is desirable to store a large amount of operation log information within an embedded device, but small, inexpensive embedded devices are limited in the amount of non-volatile memory that can be installed. In this case, it is possible to use non-volatile memory such as EEPROM, but increasing the memory capacity will affect the size of the embedded device and increase costs.

The present invention has been made in consideration of the above, and aims to provide an embedded device that can reliably store large amounts of operation logs without affecting the device configuration, even if the embedded device is small in size.

To solve the above problems and achieve the object, the present invention provides an embedded device that is incorporated into a higher-level main unit, and includes an EEPROM that is connected to a CPU on a control board within the embedded device and temporarily stores operation logs handled by the embedded device in real time, and the CPU transfers the operation logs temporarily stored in the EEPROM to another storage medium within the embedded device or outside the embedded device when a predetermined condition is met.

In the above invention, the predetermined condition is when the free space in the EEPROM is less than a predetermined value.

In the above invention, the predetermined condition is when the main device is in an idle state.

The present invention is also characterized in that, in the above invention, the predetermined condition is when a regular predetermined time is reached.

The present invention is also characterized in that, in the above invention, the other storage medium is a flash ROM of the CPU, the flash ROM is divided into a device control program area and an operation log area, and the CPU transfers the operation log temporarily stored in the EEPROM to the operation log area.

The present invention is also characterized in that, in the above invention, the storage capacity of the EEPROM is smaller than the storage capacity of the flash ROM.

In the above invention, the CPU erases the operation log temporarily stored in the EEPROM when the transfer of the operation log to the other storage medium is completed.

In the above invention, when the CPU transfers the operation log to another storage medium outside the embedded device, the operation log is assigned the identification number of the embedded device.

According to the present invention, even small-scale embedded devices can reliably store large volumes of operation logs without affecting the device configuration.

FIG. 1 is a block diagram showing the general configuration of a vending machine, which is a higher-level main device equipped with a coin mechanism and a bill validator, which are built-in devices. FIG. 2 is a block diagram showing the configuration of a coin mechanism which is an embedded device. FIG. 3 is an explanatory diagram illustrating the operation log storage process. FIG. 4 is a diagram showing an example of an operation log of the coin mechanism. FIG. 5 is a flowchart showing a procedure of the operation log storage process performed by the CPU. FIG. 6 is a flowchart showing a process of storing an operation log by a CPU according to the first modification. FIG. 7 is a flowchart showing a process of storing an operation log by a CPU according to the second modification.

The following describes the embodiment of the invention with reference to the attached drawings.

<Vending machine configuration>
1 is a block diagram showing the general configuration of a vending machine 1, which is a higher-level main device equipped with a built-in device such as a coin mechanism 11 and a bill validator 12. The vending machine 1 is further connected to a higher-level management server 100 via a network or the like. The vending machine 1 is a vending machine that sells products such as canned drinks, bottled drinks, and PET bottled drinks, but it may be any type of vending machine, such as a cup-type vending machine.

As shown in FIG. 1, the vending machine 1 has a vending machine main control unit 8, which is connected to a display unit 2, a product selection unit 3, a money handling unit 4, a product dispensing unit 5, a cooling/heating unit 6, and a communication unit 7.

The display unit 2 displays various information such as on sale, out of change, in preparation, and bill cancellation, as well as the amount inserted and information on various settings. The product selection unit 3 is a product selection button, and also has the function of displaying product prices and sales status.

The money processing unit 4 has a coin mech 11, a bill validator 12, and an electronic payment unit 13. The coin mech 11 organizes the numbers of various coins inserted and sends this to the vending machine main control unit 8, while dispensing various coins according to instructions from the vending machine main control unit 8. The coin mech 11 also has a money identification function that identifies the authenticity and denomination of coins.

The bill validator 12 counts the number of bills inserted and sends this to the vending machine main control unit 8, while dispensing the bills according to instructions from the vending machine main control unit 8. The bill validator 12 also has a money identification function that identifies the authenticity and denomination of bills.

The electronic payment unit 13 is, for example, an electronic money reader/writer, and performs a process of reading the electronic money loaded onto the electronic money card and writing the electronic money after payment. The electronic payment unit 13 also performs a writing process of loading the electronic money for change onto the electronic money card. The electronic payment unit 13 has an electronic money identification function that detects the electronic money card and identifies whether the electronic money card is valid or invalid and the type of the electronic money card.

The product dispensing unit 5 manages the bend solenoids and sold-out switches provided for each rack, and dispenses products from the rack in accordance with dispense commands sent from the vending machine main control unit 8. The product dispensing unit 5 also outputs a sold-out signal to the vending machine main control unit 8 when all products stored in the rack have been dispensed.

The cooling/heating section 6 manages the product storage compartments in the main cabinet to a set state, cooling the inside of the product storage compartments that are set to be cooled, while heating the inside of the product storage compartments that are set to be heated.

The communication unit 7 is a communication interface for communicating with an external management server 100.

The vending machine main control unit 8 dispenses the product selected by the product selection unit 3, processes payments, etc. The memory 18 stores sales data, setting data, and control programs.

<Configuration of embedded devices>
Fig. 2 is a block diagram showing the configuration of the coin mech 11, which is an embedded device. As shown in Fig. 2, the coin mech 11 has a control board 20, a money receiving mechanism 31, and a money dispensing mechanism 32. The control board 20 is a board that has the function of controlling the entire coin mech 11. The money receiving mechanism 31 is a mechanism that receives and identifies coins. Furthermore, the money dispensing mechanism 32 is a mechanism that pays out coins when change is available. Note that if the coin mech 11 cannot identify the coin, it pays it out as is.

The control board has a CPU 21, an EEPROM 24, a coin validation and identification circuit 25, a device drive control circuit 26, and a sensor unit 27. The CPU 21 has a static random access memory (SRAM) 22, which is a volatile memory, and a flash ROM (Flash ROM) 23, which is a non-volatile memory. The CPU 21 performs various calculation processes based on the device control program stored in the flash ROM 23. At this time, the SRAM 22 functions as a cache memory. The EEPROM 24 is a non-volatile memory that temporarily stores operation data of the coin mechanism 11 in real time as an operation log. The storage capacity of this EEPROM 24 is smaller than that of the flash ROM 23, and it temporarily stores a certain amount of operation log.

The device control program in the flash ROM includes a program that temporarily stores operation data in EEPROM 24 in real time, and transfers the operation log temporarily stored in EEPROM 24 to flash ROM 23 when a specified condition is met. This specified condition is, for example, when the free space in EEPROM 24 falls below a specified value. In other words, the amount of storage of the operation log temporarily stored in EEPROM 24 plus a specified margin (free space) exceeds the storage capacity of EEPROM 24.

The validation and identification circuit 25 determines whether the inserted coins are genuine and identifies the denomination. The device drive control circuit 26 is a circuit that drives and controls the money receiving mechanism 31 and the money dispensing mechanism 32. The sensor unit 27 detects the state of the money receiving mechanism 31 and the money dispensing mechanism 32. The validation and identification circuit 25 or the device drive control circuit 26 operates the circuit based on the detection result.

<Operation log storage process>
Fig. 3 is an explanatory diagram illustrating the operation log storage process. As shown in Fig. 3, the CPU 21 temporarily stores operation data generated in real time in the EEPROM 24 as an operation log. This operation log is temporarily stored in the operation log temporary storage area E10. Then, when the free space in the EEPROM 24 falls below a predetermined value, the operation log is transferred in one go to the operation log area E1 in the flash ROM 23, and after the transfer, the operation logs in the operation log temporary storage area E10 are erased to make the area free.

The flash ROM 23 basically stores the device control program, but it also has free space, and is divided into an operation log area E1 and a device control program area E2. Operation logs transferred in bulk are stored sequentially in the operation log area E1. Meanwhile, the device control program area E2 stores the device control program. Some flash ROMs 23 have around 512 Kbytes even on small 16-bit CPUs, and half of this, 256 Kbytes, can be used as the operation log area E1. This 256 Kbyte capacity is 256 times the capacity of the relatively large 8 Kbit EEPROM 24.

Therefore, the EEPROM 24 requires a smaller storage capacity than the flash ROM 23, and can store large volumes of operation logs generated within the embedded device by temporarily storing the logs in real time and transferring them all at once. Furthermore, because the operation logs are always stored in non-volatile memory, all operation logs can be reliably retained even if a failure occurs that cuts off the power to the embedded device.

In addition, since embedded devices may need to be updated due to their lifespan or replaced due to malfunction, if operation data is stored only on the vending machine 1 main unit, inconsistencies in the operation data are likely to occur, and there is a possibility that inconsistencies in the operation data will occur. In this embodiment, the operation log is stored within the embedded device, so inconsistencies in the operation logs will not occur.

Since EEPROM has a smaller erase/write block than flash ROM, it is useful for storing and erasing very small data sets, and is suitable for storing and erasing small data such as 1 byte or individual words at a time. EEPROM can be written to 10 times as many times as flash ROM, making it suitable as a temporary storage medium for transfer purposes. On the other hand, flash ROM generally has a longer write time than EEPROM, making it unsuitable for storing real-time operation logs. In this embodiment, the characteristics of memory (flash ROM and EEPROM) are utilized to make the most of the memory in the right place.

<Example of operation log>
FIG. 4 is a diagram showing an example of an operation log of the coin mechanism 11. As shown in FIG. 4, in the coin mechanism 11, operation logs such as validation data, inserted denomination data, and payout denomination data are generated in association with the purchase of a product. Specifically, when a 500 yen coin is inserted to purchase a product, validation data (identified as a genuine 500 yen coin) is generated, and as a result, inserted denomination data (500 yen inserted data) is generated. Here, when a product purchaser selects and purchases a 400 yen product, the coin mechanism 11 pays out 100 yen as change, and payout denomination data (100 yen paid data) is generated. Thereafter, when a 100 yen coin is inserted to purchase a product, validation data (identified as a genuine 100 yen coin) is generated, and as a result, inserted denomination data (100 yen inserted data) is generated. In this case, since there is no change, payout denomination data is not generated. Thereafter, in a similar manner, operation data at the time of purchasing a product is generated as an operation log, and the operation data is sequentially written as a temporary storage area E11 in the operation log temporary storage area E10 of the EEPROM 24.

If the free space E12 in the EEPROM 24 falls below a predetermined value, for example 5%, the operation logs that have been temporarily stored up to that point are transferred in one go to the operation log area E1 in the flash ROM 23, and then erased.

<Operation log storage process procedure>
5 is a flowchart showing the procedure for storing an operation log by the CPU 21. As shown in FIG. 5, the CPU 21 first determines whether operation data has been generated (step S101). If operation data has not been generated (step S101: No), the CPU 21 repeats this determination process. On the other hand, if operation data has been generated (step S101: Yes), the CPU 21 writes the generated operation data as an operation log in the EEPROM 24 (step S102).

Then, the CPU 21 determines whether the free space in the EEPROM 24 is less than a predetermined value (step S103). If the free space in the EEPROM 24 is not less than the predetermined value (step S103: No), the CPU 21 proceeds to step S101 and repeats the above process. On the other hand, if the free space in the EEPROM 24 is less than the predetermined value (step S103: Yes), the CPU 21 transfers the operation logs in the EEPROM 24 to the operation log area E1 of the flash ROM 23 in one batch (step S104).

Then, the CPU 21 determines whether the batch transfer has been completed successfully (step S105). If the batch transfer has not been completed successfully (step S105: No), this determination process is repeated. Note that if this determination process has not been completed successfully after a predetermined time has elapsed, an error notification is sent to the vending machine main control unit 8, etc.

On the other hand, if the batch transfer is completed successfully (step S105: Yes), all active ROMs in the EEPROM 24 are erased (step S106), and the process returns to step S101 and the above process is repeated.

In this embodiment, a small-capacity EEPROM 24 is sufficient, so even embedded devices with limited mounting space can reliably store all large-capacity operation logs.

<Modification 1>
In the above embodiment, the specified condition for transferring all the operational data in EEPROM 24 in one batch was that the free space in EEPROM 24 was less than a specified value, but in this variant example 1, the specified condition for transferring all the operational data in one batch is that the operation of the vending machine 1 main body is in an idle state.

Figure 6 is a flow chart showing the procedure for storing an operation log by the CPU 21 in Variation 1. As shown in Figure 6, after the CPU 21 writes operation data to the EEPROM 24 as an operation log (step S202), it determines whether the operation of the vending machine 1 main body is in an idle state (step S203), and if the operation of the vending machine 1 main body is in an idle state (step S203: Yes), it transfers the operation data in one batch to the operation log area E1 of the flash ROM 23. Note that steps S201, S202, S204 to S206 are the same processes as steps S101, S102, S104 to S106.

Generally, writing to the flash ROM 23 takes anywhere from a few seconds to a few minutes. For this reason, if the original processing between the CPU 21 and the vending machine main control unit 8 occurs while the writing process is being performed, this processing will be affected. Therefore, in this variation 1, the writing process is performed when the vending machine 1 is in an idle state, so that the original processing of the vending machine 1 is not affected.

<Modification 2>
In the above embodiment, the specified condition for transferring the operational data in EEPROM 24 in bulk was that the free space in EEPROM 24 was less than a specified value, but in this second variant, the specified condition for transferring the operational data in bulk is when a regularly scheduled time has arrived.

Figure 7 is a flowchart showing the procedure for storing an operation log by the CPU 21 in Modification 2. As shown in Figure 7, after the CPU 21 writes operation data to the EEPROM 24 as an operation log (step S302), it determines whether a predetermined time has arrived (step S303), and if the predetermined time has arrived (step S303: Yes), it transfers the operation data in one batch to the operation log area E1 of the flash ROM 23. Note that steps S301, S302, S304 to S306 are the same process as steps S101, S102, S104 to S106.

In this second variation, the operation logs are transferred in bulk at a specified time when the vending machine 1 is not performing its normal processing, for example, at 3:00 a.m. This makes it possible to avoid affecting the vending machine 1's normal processing. The specified time may be once a day, or once every three or seven days.

The predetermined conditions in the above embodiment and modified examples may be a combination of multiple predetermined conditions. In other words, a batch transfer may be performed when any of the predetermined conditions are met, or when all or some of the conditions are met.

In addition, in the above embodiment and modified example, the data is transferred in bulk from EEPROM 24 to flash ROM 23, but the data may be transferred in bulk directly to another non-volatile memory (another storage area) within the embedded device or to another memory (another storage medium) outside the embedded device. The other memory (another storage medium) outside the embedded device may be memory 18 within the vending machine main control unit 8, a USB memory connected to the vending machine main control unit 8, or a storage medium within the management server 100. The operation log may be transferred to another memory (another storage medium) outside the embedded device after being transferred in bulk from EEPROM 24 to flash ROM 23, and then transferred from flash ROM 23.

When operation logs are transferred outside the embedded device, the identification number of the embedded device is assigned to each operation log. This makes it possible to identify all operation logs of the embedded device even if the operation logs are transferred outside the embedded device. Even when operation logs are transferred to another external storage medium, the most recent operation log is always stored in the EEPROM, so it is possible to reliably obtain all operation logs of the embedded device.

In addition, the configurations illustrated in the above embodiments and variations are merely functional schematics, and do not necessarily have to be physically configured as illustrated. In other words, the form of distribution and integration of each device and component is not limited to that illustrated, and all or part of them can be functionally or physically distributed and integrated in any unit depending on various usage conditions, etc.

REFERENCE SIGNS LIST 1 Vending machine 2 Display unit 3 Product selection unit 4 Money processing unit 5 Product dispensing unit 6 Heating and cooling unit 7 Communication unit 8 Vending machine main control unit 11 Coin mechanism 12 Bill validator 13 Electronic payment unit 18 Memory 20 Control board 21 CPU
22 SRAM
23 Flash ROM
24 EEPROM
25 Validation and discrimination circuit 26 Device drive control circuit 27 Sensor unit 31 Money receiving mechanism unit 32 Money dispensing mechanism unit 100 Management server E1 Operation log area E10 Operation log temporary storage area E11 Temporary storage area E12 Free area E2 Device control program area

Claims (8)

An embedded device that is incorporated into a host main device,
an EEPROM connected to a CPU on a control board in the embedded device and configured to temporarily store an operation log handled by the embedded device in real time;
The CPU transfers the operation log temporarily stored in the EEPROM to another storage medium within the embedded device or outside the embedded device when a predetermined condition is met. The embedded device according to claim 1, characterized in that the specified condition is when the free space in the EEPROM is less than a specified value. The embedded device according to claim 1, characterized in that the predetermined condition is when the main device is in an idle state. The embedded device according to claim 1, characterized in that the specified condition is when a regular specified time is reached. the other storage medium is a flash ROM of the CPU,
2. The embedded device according to claim 1, wherein the flash ROM is divided into a device control program area and an operation log area, and the CPU transfers the operation log temporarily stored in the EEPROM to the operation log area. The embedded device according to claim 5, characterized in that the storage capacity of the EEPROM is smaller than the storage capacity of the flash ROM. The embedded device according to claim 1, characterized in that the CPU erases the operation log in the EEPROM when the operation log temporarily stored in the EEPROM has been transferred to the other storage medium. The embedded device according to claim 1, characterized in that when the CPU transfers the operation log to another storage medium outside the embedded device, the identification number of the embedded device is added to the operation log.

Images