JP4360888B2 - File writing system - Google Patents

Description

  The present invention relates to a file writing system, for example, a system file (for example, an operating system for driving a LAN system) in all or part of a blank storage means of a device (for example, a terminal adapter, an IP telephone) having a LAN interface. (OS) and application software).

  For example, terminal adapters, IP telephones, and the like have a built-in LAN interface for LAN communication, and an OS, application software, etc. for driving the LAN system in the process of manufacturing a device incorporating such a LAN interface. It is necessary to store the system file in a nonvolatile storage means (for example, a FLASH memory) of the device.

  Conventionally, in the process of manufacturing a device incorporating a LAN interface, the process of writing a system file to the nonvolatile storage means is individually performed for each device (hereinafter referred to as a product) incorporating a LAN interface to be manufactured. Was supposed to write a system file.

  For example, in the conventional system file writing processing method, a file writing device for writing a system file is connected to a product via an interface such as LAN, RS232C, or JTAG, and the file is directly written by accessing the FLASH memory of the product. In the process of manufacturing parts, a file is written into the FLASH memory chip itself using a FLASH memory writer, and the FLASH memory chip into which the system file has been written is mounted on the product.

  However, the conventional system file write processing method described above has the following problems.

  Conventionally, since writing was individually performed for each product, the writing process for the total number of manufactured units requires time of "FLASH memory writing time per unit x number of manufactured units". For example, even when writing a single type of system file, if the production quantity is large, the completion time of writing all the files has naturally become longer.

  On the other hand, in order to shorten the system file writing work to the product, conventionally, a plurality of file writing devices are provided and a plurality of file writing systems are provided to perform processing in parallel. In order to provide the file writing system, there is a problem that the cost for the construction of the equipment and the labor cost related to the equipment increase.

  In addition, when a small number of various types of products are manufactured, that is, the number of manufactured units is small, but multiple types of system files of different types are written to the non-volatile storage means of each product, it takes a long time to write a single type of system file. Although it is not necessary, on the other hand, it is necessary to prepare the writing environment in order to write various types of system files, and the operating rate of the writing environment is lower than that of the normal single type, and the manufacturing space is reduced. There has been a situation in which the above efficiency has deteriorated, or a lot of costs for constructing a writing environment for each model have to be generated.

  Even if it is possible to share the writing environment among models and reduce the cost of equipment, it is possible to write individually for each product. As a result, as a result, the time required for writing in all models was “total number of all types × manufactured units”.

  In addition, when sharing the writing environment, it is necessary to set up the environment for each model when the model is changed. In this respect as well, the work efficiency has deteriorated due to the necessity of changing work and the like.

  Therefore, there is a need for a file writing system capable of simultaneously writing system files from a single file writing device to a large number of devices and simultaneously writing a plurality of types of system files in the manufacturing process of a device having a LAN interface. .

In order to solve such a problem, the file writing system of the present invention (1) associates a plurality of types of system files corresponding to the model, the model of the device to which each system file is to be transmitted, and the multicast MAC address. A file writing device comprising a database storing multicast MAC address information; and (2) a plurality of network interfaces that are connected to the file writing device via a network and assigned a MAC address , and storage means . and a device, file writing device, (1-1) waiting for power-on of all the devices, the broadcast frame comprising a broadcast address to all the MAC address of the network interface and the destination as a MAC destination address, Delivered to the network multicast MAC address information in the broadcast, each device, (2-1) and received based broadcast frame to a broadcast address, based on the models included in the received multicast MAC address information, itself system check whether the file to be distributed, in the case of (2-2) themselves delivery target, and stores the multicast MAC address corresponding to its own model in the storing means, corresponding to the model response information indicating a request for transmission of system files, in response to the file write device, the file writing device, the system file has been requested (1-2) response information from each device, for each model, the model multicast containing the corresponding multicast MAC address as a MAC destination address Delivered to the network by the frame, each device, (2 -3) multicast MAC address contained in the multicast frame received is, in the case of a multicast MAC address stored in the storage means, the storage means system file received It is memorized.

  According to the file writing system of the present invention, a system file corresponding to a model can be simultaneously written to a plurality of products having a network interface, and a plurality of system files can be performed in a common system environment. The production efficiency of a wide range of production forms can be improved from single-product mass production to multi-product small-quantity production.

  The best mode for carrying out the file writing system of the present invention will be described with reference to the following examples.

  The first embodiment of the file writing system of the present invention will be described below.

  FIG. 1 is a conceptual diagram showing the overall configuration of the file writing system of this embodiment.

  As shown in FIG. 1, the file writing system 10 includes a file writing device 1 and a plurality of communication interfaces 2 for connecting to a plurality of products having a LAN interface, which are connected via a LAN 3.

  FIG. 1 shows a state in which a device (product) having a LAN interface to which a system file is written is connected to each of a plurality of communication interfaces 2.

  This system file includes drive software (OS) for driving the LAN system in which the product is installed or application software used for a specific purpose by storing the product in the nonvolatile storage means of the product. . The system file also includes a lot number and a production number related to the production line.

  The file writing system 10 can communicate as a LAN network, and in this embodiment, for example, the case of Ethernet (registered trademark) will be described. Of course, a LAN other than Ethernet (registered trademark) can be applied.

  The products 21 to 27 can be widely applied as long as they have a built-in LAN interface. For example, other devices such as a terminal adapter, an IP telephone, and a personal computer can be applied. The products 21 to 27 have nonvolatile storage means (for example, FLASH memory), and store the system file received from the file writing device 1 described later via the LAN 3 in the nonvolatile storage means.

  In addition, when the products 21 to 27 are connected to the communication interface 2, the setting is switched to the operation mode (“factory file writing mode”) in which the system file is written, and then the LAN 21 is connected to the file writing device 1 and the multicast method. The desired system file is received and written by performing the above communication.

  In FIG. 1, when seven products 21 to 27 are connected on the LAN, A to D shown in FIG. 1 express the model type of the system file written in the nonvolatile storage means of each product.

  The communication interface 2 is an interface unit (for example, a connection connector) with the products 21 to 27 to which system files such as software and applications for operating the LAN interface are written.

  The communication interface 2 can be connected to a plurality of products 21 to 27, and can be connected to a plurality of products 21 to 27 even when the system files written to the products 21 to 27 are different. is there.

  The file writing apparatus 1 has a database 11 and stores system files of a plurality of models in advance. The system file stored in the database 11 by the file writing apparatus 1 can be added / changed / deleted.

  The file writing device 1 also defines a MAC (Media Access Control) address (multicast MAC address) for a multicast frame for distributing each system file to each product.

  The file writing device 1 is always connected to the LAN 3, the products 21 to 27 connected to the communication interface 2 are turned on, and the products 21 to 27 are switched to the factory file writing mode and are in a standby state. In this case, file write processing by multicast is performed.

  Further, the file writing device 1 manages the communication status with each product 21 to 27 and the system file writing status, and the operator manages the management data of the file writing device 1 through the display means 12 connected to the file writing device 1. You can check the writing status of system files.

  FIG. 2 shows a schematic diagram of a communication protocol layer performed on the LAN 3 during normal time (after shipment) and a message format.

  As shown in FIG. 2, when communication between products is performed in a normal state, the products in the second layer (data link layer) of the OSI reference model and the third layer (network layer) of the OSI reference model. It has an address for connecting each other.

  For example, on Ethernet (registered trademark), TCP / IP protocol communication is shown, using a MAC address (hardware address) at the second layer level and an IP address (logical address) at the third layer level. Yes.

  As shown in FIG. 2B, a normal MAC address and an IP address are included in a message transmitted and received by a product in a normal state. Each address has a source and destination address.

  The MAC address is fixedly set in advance for each of the communication interfaces 2. As a result, the MAC address of each product connected to each communication interface 2 can also be fixedly set, and the MAC address can be fixed even when the system file writing environment changes. Can do.

  The IP address is a logical address that sets necessary conditions according to the environment to be used.

  Next, the operation of the file writing process of the present embodiment will be described in detail according to the flowcharts of FIGS. 3 to 5 with reference to the operation images of FIGS.

  First, in the system file writing operation start state to the product, only the file writing device 1 is connected to the LAN environment as shown in FIG. 6 (S301).

  As described above, the system file writing device 1 stores in advance a plurality of system files that can be used for each model. In the present embodiment, for convenience of explanation, it is assumed that the file writing apparatus 1 stores system files of model types A to C.

  When processing for writing a system file in the storage means of each product is performed, the target product is connected to the LAN 3 via the communication interface 2 (S302).

  In FIG. 7, the number of products connected to the LAN 3 is seven, three model type A products, two model type B products, one model type C product, and model type D product. Are connected to the LAN 3 and each model type is displayed as “product A” or the like.

  “MAC: 1 to 7” shown in FIG. 7 indicates a MAC address fixedly assigned to the communication interface 2 to which each product 21 to 27 is connected. Therefore, during the file writing process, the products 21 to 27 connected to the LAN 3 perform communication using the MAC address of the corresponding communication interface 2.

  Further, when connecting the products 21 to 27 to the LAN 3, the products 21 to 27 are connected after the operation mode of the products 21 to 27 is set to the factory file writing mode.

  The factory file writing mode may be set, for example, by a combination of setting terminals such as DIPSW (dip switches) provided in advance in the products 21 to 27.

  As described above, the operation mode of each of the products 21 to 27 is set to the factory file writing mode, not in the normal format as shown in FIG. 2, but between the products in the system file writing process described below. In communication using a LAN interface, communication using a unique format that uses only an Ethernet (registered trademark) frame and does not use the higher-level protocol TCP / IP occurs. Since this is the case only, it is connected to the LAN after this mode is set.

  That is, in general, communication is performed using the TCP / IP protocol on the Ethernet (registered trademark), whereas the file writing system 10 according to the present embodiment performs communication with other products via the LAN interface. At any time, communication is performed using the hierarchical communication protocol up to the second layer as described above.

  When the products 21 to 27 are connected to the LAN 3, the products 21 to 27 are powered on, and as shown in FIG. 8, the products 21 to 27 enter a state of waiting for data reception from the LAN interface. (S303).

  When each of the products 21 to 27 is in a standby state, as shown in FIG. 9, a multicast MAC attached to a multicast frame for each manufacturer-specific system file transfer, which will be described later, in a broadcast frame from the file writing device 1 Address information is distributed (S304).

  The format of the broadcast frame distributed from the file writing apparatus 1 is roughly divided into a header part, a user data part, and a footer part as shown in FIG. The broadcast frame does not include the third layer address (IP address) of the OSI reference model. For this reason, for example, communication is possible through a network communication device up to the second layer of the OSI reference model such as a repeater or a bridge, but for example, a communication range such as a router is available. Communication via a network communication device as the third layer of the OSI reference model cannot be performed.

  Note that a broadcast frame is a broadcast frame that is generally distributed throughout the second layer network of the OSI reference model, and is performed by devices throughout the second layer network.

  The header part has a destination MAC address, a source MAC address (a unique address of the file writing device 1), and other header information.

  The user data part has a plurality of information elements, and at least the system file distribution information as the use (message type) of this frame and the relationship between the multicast MAC addresses that need to be received for each of the products 21 to 27 (for example, , Model A: Multicast MAC1, etc.). The file writing apparatus 1 writes and notifies all information related to the system files of each model stored in advance as information elements.

  The footer unit has a frame check sequence (FCS).

  Returning to FIG. 9, the file writing apparatus 1 of the present embodiment stores system files corresponding to the model types A, B, and C in the database 11, and as shown in FIG. Information elements are included.

  When the broadcast frame is distributed from the file writing device 1 to each of the products 21 to 27, each product 21 to 27 needs to receive it from the information elements included in the user data part of the broadcast frame. The presence / absence of a multicast MAC address is determined. Then, as shown in FIG. 10, broadcast reception responses corresponding to the determinations of the products 21 to 27 are transmitted from the products 21 to 27 to the file writing device 1 by unicast frames (S305). Here, unicast generally refers to one-to-one communication, and is received only by the device designated as the destination of the unicast frame.

  As described above, the reception response from each of the products 21 to 27 is obtained when there is a multicast MAC address to be received in the broadcast frame based on the presence or absence of the multicast MAC address in the user data part of the broadcast frame. Either a “ready to receive” response or a “no applicable data” response to be added if there is no multicast MAC address to be received in the broadcast frame is determined.

  In each of the products 21 to 27, after the power is turned on, its own model conditions can be recognized in advance (for example, the model conditions are stored in advance in the storage means included in each of the products 21 to 27). The multicast MAC address that needs to be received by itself was checked by checking the model conditions of the above and the information indicated by the content of the user data part of the broadcast from the file writing device 1, and the multicast MAC address could be confirmed. The products 21 to 27 transmit a “reception ready” response to the file writing device 1.

  If the contents of the broadcast user data portion from the file writing device 1 do not include a multicast MAC address that needs to be received by the device itself, the products 21 to 27 send “no corresponding data” to the file writing device 1. "Send response.

  As shown in FIG. 22, the format of the broadcast reception response frame transmitted from each product 21 to 27 is roughly divided into a header part, a user data part, and a footer part.

  The broadcast reception response frame does not include the third layer address (IP address) of the OSI reference model. Therefore, as in the case of a broadcast frame, for example, communication is possible through a network communication device up to the second layer of the OSI reference model, such as a repeater or a bridge. As described above, communication via a network communication device whose communication range is the third layer of the OSI reference model cannot be performed.

  The header part includes a destination MAC address (address of the file writing device 1), a corresponding transmission source MAC address uniquely assigned to the communication interface 2 of each product 21 to 27 (for example, “MAC: 1” in the case of the product A21). Etc.) with other header information. As the destination MAC address, each product 21 to 27 stores the address included in the broadcast frame from the file writing device 1, and uses the stored address.

  The user data part is attached with the contents of the reception response to the file writing device 1. FIG. 22A shows a format when a “reception ready” response is sent, and FIG. 22B shows a format when a “no corresponding data” response is sent.

  As shown in FIG. 22 (A), the user data part of the “reception ready” response has at least two information elements, and the reception ready response as the message type and each of the products 21 to 27 themselves Include the type information of the system file to be received.

  Further, as shown in FIG. 22B, the user data portion of the “no corresponding data” response has at least two information elements, the no data corresponding response as the message type, and the products 21 to 27. Include the required model conditions that the terminal expects to receive.

  The footer unit has a frame check sequence (FCS).

  Returning to FIG. 10, the products 21 to 26 determine a broadcast frame from the file writing device 1, and transmit a broadcast reception response frame of a “reception ready” response to the file writing device 1 by unicast. Then, the broadcast frame is judged, and a broadcast reception response frame of “no corresponding data” response is transmitted to the file writing apparatus 1 by unicast.

  The file writing device 1 monitors reception responses from the products 21 to 27 for a predetermined time. When each broadcast reception response frame from each product 21 to 27 is given, each broadcast reception response frame is received by the file writing device 1. The response content is checked (S306).

  If all the check results of the file writing device 1 are “reception ready” responses, the process proceeds to S308.

  If the check result of the file writing device 1 includes a “no applicable data” response, based on the broadcast reception response frame of the “no applicable data” response, the MAC address of the product, the requested model code, and The included information is referred to as “installed NG device information”) and is displayed on the display unit of the file writing apparatus 1 and stored in the database 11 (S307).

  For example, in FIG. 11, a broadcast reception response frame “no corresponding data” is sent from the product D27 in which the multicast MAC address necessary for reception is not included in the user data portion of the broadcast frame to the file writing device 1. Indicates the case where is transmitted.

  The file writing device 1 that has received the response “no corresponding data” from the product D27 identifies the source MAC address and the requested model code from the broadcast reception response frame, and displays “model D (MAC: 7) ”(see FIG. 11). The source MAC address and the requested model code are stored in the database 11.

  The display means 12 in FIG. 11 is an operator's operation terminal and can be connected to the file writing apparatus 1. The display unit 12 can be connected to the LAN 3 and may be a component of the LAN 3.

  This “no corresponding data” response occurs when a system file corresponding to the model is not stored in the database 11 of the file writing apparatus 1.

  Therefore, in this case, a new system file is added and stored in the database 11 of the file writing device 1, and an additional definition of the destination MAC address (multicast MAC address) of the multicast frame used when transferring the added system file is defined. It is necessary to do. Here, these processes are omitted.

  Then, after the addition of the system file and the addition definition of the multicast MAC address are completed, the file writing process of the product is necessary.

  In this way, the operator can identify the product for which the writing process has been interrupted and the model code of the system file that needs to be newly added based on the installation NG information displayed on the display means. .

  Further, the installation NG information is stored in the database 11 so that the operator can separately confirm it later.

  Note that the content of the installation NG information is not limited to this, and may include other information. For example, the error occurrence time, the total number of products in which an error has occurred, and the like may be included.

  When the file writing device 1 receives a “ready to receive” response from each product 21 to 26, the file writing device 1 needs at least the MAC address of each product 21 to 27 and its product from the broadcast reception response frame. The system file for each model is stored in the database 11 (S308).

  In the database 11, information on the stored system file (“stored model information” in FIG. 11) and the MAC addresses of the products 21 to 26 that have returned reception responses are stored in association with each other. The file writing device 1 can know which products 21 to 26 are waiting to receive and which model system file should be transmitted to which MAC address.

  When the file writing device 1 determines the system file to be transmitted to each of the products 21 to 26 that have returned the “ready for reception” response, the file writing device 1 refers to the database 11 and, as shown in FIG. A multicast frame including the system file for each model is transmitted in parallel to the product that requests the system file (S309).

  The file writing device 1 includes a transmission timer for managing a transmission cycle, and performs predetermined transmission to each product 21 to 27 so as not to exceed a preset multicast frame reception processing capability for each model. A multicast frame including a system file is transmitted at a period. As a result, it is possible to prevent the received data from being lost on each product side.

  FIG. 23 shows a format of a multicast frame including a system file transmitted from the file writing apparatus 1.

  As shown in FIG. 23, a multicast frame including a system file is roughly divided into a header part, a user data part, and a footer part.

  A multicast MAC address of the products 21 to 26 that request a system file for each model to be transmitted is attached to the destination MAC address in the header part for each model. For example, when a model type A system file is transmitted, the multicast MAC address (multicast MAC1) assigned to the products A21, 22, and 23 is attached, and when a model type B system file is transmitted, the product B24 is assigned. , 25, the multicast MAC address assigned to product C26 (multicast MAC3) is assigned when a model type C system file is transmitted.

  The user data section has at least system file data transmission and a model-specific system file data block as the use (message type) of this frame.

  This system file data block is a fixed-length block. When the size of the system file data is smaller than the fixed length, a multicast frame to be transmitted is transmitted as the final data block. Further, when the size of the data block of the system file is larger than the fixed length, it is divided into the fixed length and transmitted.

  If the system file data happens to be divisible by the length of the data block and the final data block size is the same as the specified fixed length, the data block size of the next frame to be transmitted is set to zero. By transmitting the dummy frame, each product side can recognize that the frame transmitted before that is the last data block.

  The multicast frame including the system file does not include the third layer address (IP address) of the OSI reference model. Therefore, as in the case of a broadcast frame, for example, communication is possible through a network communication device up to the second layer of the OSI reference model, such as a repeater or a bridge. As described above, communication via a network communication device whose communication range is the third layer of the OSI reference model cannot be performed.

  A multicast frame is a broadcast frame that is generally distributed throughout the second layer network of the OSI reference model, but only a product that needs to be received performs a reception process.

  Further, as shown in FIG. 13, since the file writing device 1 does not store the system file of the model requested by the product D27, the multicast frame is not transmitted to the product D27, and the system writing of the system file is set in the file writing device 1. Again after completion.

  When a multicast frame including a system file is given from the file writing device 1 to each product 21-26, the corresponding system file data is taken out by each product 21-26, and the storage means (for example, FLASH memory etc.) of each product 21-26 (S310).

  When each of the products 21 to 26 receives all the system files normally and writes them normally, a multicast reception response frame of a “reception normal” response is transmitted to the file writing device 1. If each product 21 to 26 has not received all system files normally, a multicast reception response frame of a “reception abnormality” response is transmitted to the file writing device 1, and each product 21 to 26 waits for reception. A state is entered (S310).

  When each product 21 to 26 receives each multicast frame from the file writing device 1 and reconfigures the system file from all the received system file data blocks divided into fixed lengths, for example, the SUM check is used. Check whether the data is received normally. At this time, when the normality is confirmed, each of the products 21 to 26 transmits a “reception normal” response to the file writing apparatus 1.

  Each of the products 21 to 26 displays a message indicating the end of normal processing after transmitting a “reception normal” response, so that the operator can check the product for which normal processing has been completed. For example, a lighting lamp, an audible sound, a display display, or the like can be applied to the display indicating the end of the normal processing.

  In addition, each product 21 to 26 has a multicast frame discarded on the LAN 3, the order of the system file data is changed, or the receiving part of the LAN interface of each product 21 to 26 has a problem. Since all the data blocks included in the file cannot be received normally, when the system file is reconstructed from all the data blocks received inside the product, the file content normality confirmation becomes NG, or the normal system file Even if it is the content, when writing into the FLASH memory fails to write normally due to a defect in the FLASH memory, a “reception abnormality” response is transmitted.

  FIG. 24 shows a format of a multicast reception response frame transmitted by the products 21 to 26.

  The multicast reception response frame of the “reception normal” response has information on the file reception normal response as the message type in the information element 1 and information on the type of the system file normally received by itself in the information element 2.

  The multicast reception response frame of the “reception abnormality” response has information on the file reception abnormality response as the message type in the information element 1 and information on the type of the system file received normally abnormally in the information element 2.

  This multicast reception response frame also does not include the third layer address (IP address).

  In this embodiment, as shown in FIG. 14, because product B25 failed to write a system file, a multicast frame of a “reception abnormality” response is sent to the file writing device 1, and product A23 writes the system file. Cannot proceed, and the multicast reception response frame cannot be transmitted, and there is no response. The other products 21, 22, 24, and 26 have successfully completed file writing and transmitted a “reception normal” response.

  The file writing device 1 monitors the reception responses from the products 21 to 26 for a predetermined time, and checks the response contents of the received reception responses (S311).

  If the response content of the reception response by the file writing device 1 is a “reception normal” response, the process proceeds to S315.

  When the response content of the reception response by the file writing device 1 is a “reception abnormality” response, the file writing device 1 first checks the number of retransmissions of the system file related to the model in which the reception abnormality has occurred (S312). ).

  If the number of retransmissions of the system file has not reached the predetermined number, the system file of the model is retransmitted (S313). The system file transmission method in this case is the same as that described in step S309, and thus description thereof is omitted. After resending the system file, the process returns to S310, and the reception response from the product 25 whose previous reception response is the “reception abnormality” response is monitored.

  If the number of retransmissions of the system file has reached the predetermined number, the system file writing apparatus 1 displays “installed NG device information” and saves it in the database 11 (S314).

  As shown in FIG. 15, the information content displayed when the “installed NG device information” is displayed is, for example, information indicating the reason for abnormal reception and whether the product has abnormal reception. FIG. 15 shows a case where “model B (MAC: 5)” is displayed as “reception abnormality information display”.

  The reason for this reception abnormality can be known based on the information included in the information element 2 of the multicast reception response frame, and the product having the reception abnormality is based on the source MAC address of the multicast reception response frame. Can know.

  Each product or each communication interface includes an abnormality detection means for detecting the type of reception abnormality, and information corresponding to the specific content of the reception abnormality detected by the abnormality detection means may be written in the information element 2. Good. As a result, it is possible to display specific contents of reception abnormality as “installed NG device information”.

  Further, this “installed NG device information” is stored in the database 11 of the file writing apparatus 1 as shown in FIG. FIG. 15 shows an example of saving in the database 11. The database 11 stores the model information (stored model information) of the system file to be stored in association with the MAC address information (reception abnormality information) that caused the reception abnormality.

  In this way, the “installed NG device information” is displayed and stored. The product 25 in which the reception error has occurred is displayed after the cause of the reception error is resolved by the operator who has viewed the “installed NG device information” display. The system file writing process described in S309 may be performed again.

  When a “reception normal” response is given from the product to the file writing device 1, the file writing device 1 stores the MAC address of the product that has transmitted the “reception normal” response in the database 11 for each model (S315).

  In FIG. 16, the “reception completed device information” stored in the database 11 corresponds to the model information (stored model information) of the system file stored in the database 11 and the MAC address of the product that has transmitted the “reception normal” response. Let

  In FIG. 16, the products that have received the model type A system file are the products A 21 and 22, and the MAC addresses “MAC: 1” and “MAC: 2” are associated with the model A. Similarly, the MAC address “MAC: 4” of the product B24 that received the system file of the model type B is made to correspond to the model B, and the MAC address “MAC: 6” of the product C26 that received the system file of the model type C is set. Correspond to model C.

  Since the product A23 is in a no-response state, information regarding the product A23 is not stored.

  When the “reception completed device information” of the product that has transmitted the “reception normal” response is stored in the database 11, the file writing device 1 stores “reception ready device information” and “reception abnormality information” stored in the database 11. Based on the “reception completion device information”, it is checked whether there is a product that has not responded in the file writing process (S316).

  The non-response product checking method by the file writing device 1 is the MAC address stored as “reception completed device information” and “reception abnormality information” stored in the database 11 and “reception ready device information”. Compared with the saved MAC address, if there is a MAC address that is saved in “Reception ready device information” but not saved in “Reception completed device information” and “Reception abnormality information”, It is assumed that there is a non-response product, and the product corresponding to the MAC address is identified as a non-response product.

  In this way, if there is no product with no response as a result of the check by the file writing apparatus 1, the process proceeds to S318.

  If there is a non-response product as a result of checking by the file writing device 1, the specified non-response product information is displayed (S317).

  As shown in FIG. 17, the information content displayed when the “non-response product information” is displayed is, for example, information indicating that the reception response is non-response and which product is non-response. . FIG. 17 shows a case where “model A (MAC: 3)” is displayed as “non-response product information display”. Thereby, the operator can know which product of which model was unresponsive.

  Further, the “non-response product information” is stored in the database 11 of the file writing apparatus 1 as shown in FIG. FIG. 17 shows an example of saving in the database 11. The database 11 stores the model information (stored model information) of the system file to be stored in association with the MAC address information (non-response product information) whose reception response is no response.

  When the “non-response product information” is stored in the database 11, the power supplies of the products 21 to 27 connected on the LAN 3 are turned off (S318).

  At this time, for the products 21, 22, 24, and 26 for which the writing of the system file has been normally completed, a display indicating that the writing process has been completed is displayed on each product. For example, lamp lighting or audible sounding can be applied to the display indicating the end of the writing process.

  When the power supplies of the products 21 to 27 are turned off, the products 21 to 27 are removed from the LAN 3 as shown in FIG. 19, and the operation mode is returned to the normal mode (S319).

When each of the products 21 to 27 is removed from the LAN 3, the file writing process ends (S320).
The operator can check defective product information based on the information stored in the database 11 of the file writing apparatus 1, and the defective product is subjected to file writing processing again after failure analysis and repair. Measures can be taken.

  As described above, according to this embodiment, it is possible to simultaneously write system files for a plurality of products having a LAN interface.

  In addition, according to the present embodiment, it is possible to improve the production efficiency of a wide variety of production modes (shortening the total production time and minimizing the production cost) from single-item mass production to multi-product small-quantity production.

  Specifically, in the conventional processing method of individually writing system files one by one, a processing time of “FLASH memory writing time per unit × manufactured number of units” occurs even if a single product is used. On the other hand, according to the present embodiment, since the system file can be written to a plurality of products at the same time, the system file writing operation time can be reduced.

  In addition, it is possible to greatly suppress the construction of equipment for proceeding processing in parallel and the significant investment in capital.

  Also, as in the past, when producing a small number of models with a variety of products, it was necessary to prepare a system environment for writing a system file of a different product type. Since the writing process can be performed in a common system environment at the same time, the manufacturing space and cost required for constructing the system environment can be reduced, and the time required for the writing operation can be reduced.

  In the above-described embodiments, the case where the product has a LAN interface has been described. However, by providing the communication interface 2 with a file installation LAN interface used only at the time of manufacture, a product that does not have a built-in LAN interface can be provided at the time of manufacture. You may make it apply.

  Further, the communication interface 2 may be provided with, for example, a writing function (for example, a FLASH memory writer) to the nonvolatile storage means so that the system file can be directly written to the nonvolatile storage means itself. Then, the system file may be stored in the nonvolatile storage means and then mounted on the product.

  Although not shown in each drawing referred to in the first embodiment, a relay device (for example, a repeater or a bridge) that uses one or more OSI reference models as a communicable range may be provided on the LAN 3.

1 is a diagram illustrating an outline of an overall configuration of a file writing system at a normal time (after shipment) according to a first embodiment. FIG. 3 is a diagram illustrating a communication protocol layer and a message format according to the first embodiment. 6 is a flowchart illustrating a file writing operation according to the first exemplary embodiment. 6 is a flowchart illustrating a file writing operation according to the first exemplary embodiment. 6 is a flowchart illustrating a file writing operation according to the first exemplary embodiment. FIG. 6 is an image diagram of a file writing operation according to the first embodiment. FIG. 6 is an image diagram of a file writing operation according to the first embodiment. FIG. 6 is an image diagram of a file writing operation according to the first embodiment. FIG. 6 is an image diagram of a file writing operation according to the first embodiment. FIG. 6 is an image diagram of a file writing operation according to the first embodiment. FIG. 6 is an image diagram of a file writing operation according to the first embodiment. FIG. 6 is an image diagram of a file writing operation according to the first embodiment. FIG. 6 is an image diagram of a file writing operation according to the first embodiment. FIG. 6 is an image diagram of a file writing operation according to the first embodiment. FIG. 6 is an image diagram of a file writing operation according to the first embodiment. FIG. 6 is an image diagram of a file writing operation according to the first embodiment. FIG. 6 is an image diagram of a file writing operation according to the first embodiment. FIG. 6 is an image diagram of a file writing operation according to the first embodiment. FIG. 6 is an image diagram of a file writing operation according to the first embodiment. FIG. 6 is an image diagram of a file writing operation according to the first embodiment. It is explanatory drawing explaining the format of the broadcast frame transmitted from the file writing apparatus 1 of Example 1. FIG. It is explanatory drawing explaining the format of the broadcast reception response frame transmitted from each product of Example 1. FIG. It is explanatory drawing explaining the format of the multicast frame sent out from the file writing apparatus 1 of Example 1. FIG. FIG. 3 is an explanatory diagram illustrating a format of a multicast reception response frame transmitted from each product according to the first embodiment.

Explanation of symbols

DESCRIPTION OF SYMBOLS 1 ... File writer, 11 ... Database, 2 ... Communication interface,
21-27 ... Product, 3 ... LAN.

Claims (2)

A file writing device comprising a database storing a plurality of types of system files corresponding to the model, and multicast MAC address information in which the model of the device to which each system file is to be transmitted and the multicast MAC address are stored;
A plurality of devices that are connected to the file writing device via a network and are provided with a network interface to which a MAC address is assigned , and storage means ;
With
Upper Symbol file writing device, waiting for power-on of the all the devices, the broadcast frame comprising a broadcast address destined for all MAC addresses of the network interface as a MAC destination address, broadcast the multicast MAC address information To the network ,
Each of the above devices
The broadcast frame is received based on the broadcast address, and based on the model included in the received multicast MAC address information, it is confirmed whether itself is a system file distribution target ,
If themselves are distribution target, the multicast MAC address corresponding to its type is stored in the storage means, a response information indicating the transmission requirements of the system file corresponding to the model in response to the file write unit And
The file writing device is
On SL the system file has been requested by the response information from each device, for each model, and distributed to the network by a multicast frame including a multicast MAC address corresponding to the model as a MAC destination address,
It said each device, said multicast MAC address included in the multicast frame received is, in the case of a multicast MAC address stored in the storage means, and characterized in that stored on SL storage unit system file received File writing system. Each of the above devices
When the system file corresponding to the model is normally received and the storage means is normally written, a reception normal response is received or the system file corresponding to the model cannot be normally received and the storage If the data could not be successfully written to the means, a reception error response is sent to the file writing device by a multicast reception response frame,
The file writing device
Stored in said database for each type of the system files the MAC address of each device that has transmitted the above Symbol response information as a reception preparation completion equipment information,
And stored in the reception abnormal response as a receiving abnormality information the MAC address of the has transmitted each device of the system files for each type in the database, for each type of the system files equipment after performing reception abnormal response specific to, or the MAC address of each device that has transmitted the received normal response as reception completion equipment information stored in the database for each type of the system files have been stored as the reception preparation completion information by storing the MAC address that is not stored as the reception completion equipment information in the database as unresponsive device information, and characterized by that identifies each type of above SL system files the device without the reception response The file writing system according to claim 1.

Images