Optical communication device, work machine, and communication method

Abstract

The present invention provides an optical communication device, an operating machine, and a communication method that can detect and report the occurrence and the probability of occurrence of a communication failure in optical communication.　The optical communication device includes an optical reception device that performs optical communication using an optical signal, a detection device that detects errors in received data received by the optical reception device, and a determination device that determines an increase in a detection count indicating the number of times errors are detected by the detection device and reports notification information on communication failures on the basis of a determination that the detection count has increased.

Description

[Technical Field]

[0001] The present disclosure relates to an optical communication device that performs optical communication using optical signals. [Background technology]

[0002] Various devices that transmit and receive data via optical communication have been proposed. For example, the electronic component mounting device disclosed in Patent Document 1 below connects a control device and a Y-axis slide device with an optical fiber cable, and performs optical communication using optical signals. The control device controls each device in the electronic component mounting device based on the data transmitted and received via optical communication. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] International Publication No. WO2015 / 052843 Summary of the Invention [Problem to be solved by the invention]

[0004] In the communication device that performs the above-mentioned optical communication, for example, as the deterioration of the light emitting element or the optical fiber cable progresses, a communication failure state occurs in which the communication connection cannot be established. When a communication failure occurs, work such as replacing the optical fiber cable becomes necessary. Therefore, a technology that can detect the occurrence or possibility of a communication failure at an early stage is required.

[0005] The present disclosure has been made in consideration of the above-mentioned problems, and aims to provide an optical communication device, work machine, and communication method that can detect and notify of the occurrence or possibility of communication failure in optical communication. [Means for solving the problem]

[0006] In order to solve the above problem, this specification provides a system for transmitting information relating to a communication abnormality, the system comprising: an optical receiving device that performs optical communication using an optical signal; a detection device that detects data errors in data received by the optical receiving device; and a determination device that determines an increase in the number of detections of errors detected by the detection device and notifies notification information relating to a communication abnormality based on the determination that the number of detections has increased. The determination device determines whether the number of detections detected by the detection device within a predetermined time is equal to or greater than a threshold number, and if it determines that the number of detections is equal to or greater than the threshold number, determines that the number of detections has increased, the optical receiving device is connected to the optical transmitting device via a wired cable, and if the number of detections is equal to or greater than a first threshold number, the determination device issues a notification information instructing to replace the wired cable, and if the number of detections is equal to or greater than a second threshold number which is less than the first threshold number, the determination device issues a notification information instructing to clean the connection portion of the wired cable. An optical communication device is disclosed.

[0007] Furthermore, the contents of the present disclosure are not limited to implementation as an optical communication device, but are also extremely useful when implemented as a work machine equipped with an optical communication device or as a communication method in a work machine. [Effects of the Invention]

[0008] According to the optical communication device etc. disclosed herein, when communication quality deteriorates due to deterioration of the light-emitting element or optical fiber cable and data errors increase, the user can be notified of the occurrence or possibility of a communication failure through notification information. [Brief explanation of the drawings]

[0009] [Figure 1] 1 is a plan view showing a schematic configuration of a component mounting system according to an embodiment of the present invention; [Figure 2] FIG. 2 is a perspective view showing a schematic configuration of a component mounting machine and a loader. [Figure 3] Block diagram of a multiplex communication system. [Figure 4] 10A and 10B are diagrams showing the contents of multiplexed data transmitted from the fixed part substrate to the mounting head in multiplex communication using an optical fiber cable. [Figure 5] 10A and 10B are diagrams showing the contents of multiplexed data transmitted from the mounting head to the fixed part substrate in multiplex communication using an optical fiber cable. [Figure 6] 10 is a flowchart showing a notification control process performed by the component mounting machine. [Figure 7] FIG. 10 is a diagram showing an example of a display screen displayed on a touch panel in the first notification process. [Figure 8] FIG. 10 is a diagram showing an example of a display screen displayed on a touch panel in the second notification process. DETAILED DESCRIPTION OF THE INVENTION

[0010] An embodiment of the optical communication device of the present disclosure will be described below with reference to the drawings. FIG. 1 is a plan view showing a schematic configuration of a component mounting system 10 of this embodiment. FIG. 2 is a perspective view showing a schematic configuration of a component mounting machine 20 and a loader 13. In the following description, the left-right direction in FIG. 1 is referred to as the X-axis direction, the up-down direction in FIG. 1 is referred to as the Y-axis direction (front-rear direction), and the direction perpendicular to the X-axis direction and the Y-axis direction is referred to as the Z-axis direction (up-down direction). The X-axis direction is the transport direction of a substrate 17 (described later), and the Y-axis direction is the direction parallel to the plane of the substrate 17 being transported and perpendicular to the X-axis direction.

[0011] 1, a component mounting system 10 includes a production line 11, a loader 13, and a host computer 15. The production line 11 has a plurality of component mounting machines 20 arranged in the X-axis direction, and performs operations such as mounting electronic components (not shown) onto a board 17. For example, the board 17 is transported from the component mounting machine 20 on the left side to the component mounting machine 20 on the right side, and mounting of electronic components is performed during transport.

[0012] As shown in FIG. 2 , the component mounting machine 20 includes a base 21 and a module 22. The base 21 has a generally rectangular parallelepiped shape that is elongated in the Y-axis direction, and is placed on the floor of a factory where the component mounting machine 20 is installed. The position of the base 21 is adjusted in the vertical direction, for example, so as to align the positions of the board transport devices 23 of adjacent modules 22. The base 21 is fixed to the base 21 of an adjacent component mounting machine 20. The module 22 is a device that mounts electronic components on the board 17, and is placed on the base 21. The module 22 can be pulled out forward in the front-to-rear direction relative to the base 21, and is replaceable with another module 22.

[0013] The module 22 includes a board transport device 23, a feeder table 24, a mounting head 25, and a head moving mechanism 27. The board transport device 23 is provided within the module 22 and transports the board 17 in the X-axis direction. The feeder table 24 is provided on the front side of the module 22 and is an L-shaped table when viewed from the side. The feeder table 24 includes a plurality of slots (not shown) arranged in the X-axis direction. A feeder 28 that supplies electronic components is attached to each slot of the feeder table 24. The feeder 28 is, for example, a tape feeder that supplies electronic components from a tape that stores electronic components at a predetermined pitch. As shown in FIG. 1, an operation unit 29 that inputs operations to the component mounting machine 20 is provided on the top cover of the module 22. FIG. 2 shows the module 22 with the top cover and operation unit 29 removed.

[0014] The placing head 25 has holding members (not shown) that hold electronic components supplied from the feeder 28. Examples of the holding members that can be used include suction nozzles that receive negative pressure to hold electronic components, and chucks that grip and hold electronic components. The placing head 25 has, for example, multiple servo motors 75 (see FIG. 3) as drive sources that change the overall position of the multiple holding members and the position of each individual holding member. The holding members rotate around a rotation axis parallel to the Z-axis direction, for example, based on the drive of the servo motors 75. The placing head 25 places the electronic components held by the holding members onto the board 17.

[0015] The head moving mechanism 27 also moves the mounting head 25 to any position in the X-axis and Y-axis directions in the upper portion of the module 22. More specifically, the head moving mechanism 27 includes an X-axis slide mechanism 27A that moves the mounting head 25 in the X-axis direction, and a Y-axis slide mechanism 27B that moves the mounting head 25 in the Y-axis direction. The X-axis slide mechanism 27A is attached to the Y-axis slide mechanism 27B.

[0016] The X-axis slide mechanism 27A also includes a slave 61 (see FIG. 3) connected to an industrial network, for example. The industrial network here is, for example, EtherCAT (registered trademark). Note that the industrial network of the present disclosure is not limited to EtherCAT (registered trademark), and other networks (communication standards) such as MECHATROLINK (registered trademark)-III and Profinet (registered trademark) can also be used. The slave 61 is connected to various elements such as relays and sensors provided in the X-axis slide mechanism 27A, and processes signals input and output from the various elements based on control data received from the device main body 41 (see FIG. 3) of the component mounting machine 20.

[0017] The Y-axis slide mechanism 27B has a linear motor (not shown) as a drive source. The X-axis slide mechanism 27A moves to any position in the Y-axis direction based on the drive of the linear motor of the Y-axis slide mechanism 27B. The X-axis slide mechanism 27A also has a linear motor 77 (see FIG. 3) as a drive source. The mounting head 25 is attached to the X-axis slide mechanism 27A and moves to any position in the X-axis direction based on the drive of the linear motor 77 of the X-axis slide mechanism 27A. Therefore, the mounting head 25 moves to any position in the X-axis and Y-axis directions within the module 22 in accordance with the drive of the X-axis slide mechanism 27A and the Y-axis slide mechanism 27B.

[0018] The placement head 25 is attached to the X-axis slide mechanism 27A via a connector and can be easily attached and detached, allowing for a change to a different type of placement head 25, such as a dispenser head. Therefore, the placement head 25 of this embodiment is detachable from the component placement machine 20. A mark camera 69 (see FIG. 3) for photographing the board 17 is fixed to the X-axis slide mechanism 27A facing downward. The mark camera 69 can capture images of any position on the board 17 from above as the head movement mechanism 27 moves. Image data captured by the mark camera 69 is transmitted from the X-axis slide mechanism 27A to the device main body 41 via multiplex communication, which will be described later, and then processed by the image processing board 87 (see FIG. 3) of the device main body 41. The image processing board 87 acquires information about the board 17 (such as marks), placement position errors, and the like, through image processing.

[0019] The placing head 25 also includes a slave 62 (see FIG. 3) connected to the above-mentioned industrial network. The slave 62 is connected to various elements such as relays and sensors provided on the placing head 25. The slave 62 processes signals input to and output from the various elements of the placing head 25 based on control data received from the device main body 41 (see FIG. 3). The placing head 25 also includes a part camera 71 that captures images of electronic components held on the holder. Image data captured by the part camera 71 is transmitted from the placing head 25 to the device main body 41 via multiplex communication and is subjected to image processing on an image processing board 87 (see FIG. 3) of the device main body 41. The image processing board 87 acquires, through image processing, errors in the holding position of the electronic components on the holder, etc.

[0020] 1 and 3, the component mounting machine 20 also includes an operation unit 29. The operation unit 29 includes, for example, a touch panel 29A and hard keys 29B and functions as a user interface. The component mounting machine 20 outputs a signal corresponding to an operation input received from a user via the touch panel 29A or the hard keys 29B to the device main body 41. The operation unit 29 also changes the display content of the touch panel 29A under the control of the device main body 41. Note that the configuration of the operation unit 29 described above is merely an example. For example, the operation unit 29 does not necessarily have to include the hard keys 29B. Alternatively, for example, the operation unit 29 may not include the operation unit 29, but may instead include a display unit such as an LCD screen and the hard keys 29B.

[0021] As shown in FIG. 2 , an upper guide rail 31, a lower guide rail 33, a rack gear 35, and a non-contact power transfer coil 37 are provided on the front surface of the base 21. The upper guide rail 31 is a rail with a U-shaped cross section extending in the X-axis direction, with its opening facing downward. The lower guide rail 33 is a rail with an L-shaped cross section extending in the X-axis direction, with its vertical surface attached to the front surface of the base 21 and its horizontal surface extending forward. The rack gear 35 is provided below the lower guide rail 33, extends in the X-axis direction, and is a gear with multiple vertical grooves on its front surface. The upper guide rail 31, the lower guide rail 33, and the rack gear 35 of one base 21 can be detachably connected to the upper guide rail 31, the lower guide rail 33, and the rack gear 35 of an adjacent base 21. This allows the component mounting system 10 to increase or decrease the number of component mounting machines 20 arranged on the production line 11. The non-contact power supply coil 37 is a coil provided on the upper portion of the upper guide rail 31 and arranged along the X-axis direction, and supplies power to the loader 13.

[0022] The loader 13 is a device that automatically replenishes and retrieves feeders 28 from the component mounting machine 20, and includes a gripper (not shown) that clamps the feeder 28. The loader 13 includes an upper roller (not shown) that is inserted into an upper guide rail 31 and a lower roller (not shown) that is inserted into a lower guide rail 33. The loader 13 also includes a motor as a drive source. A gear that meshes with a rack gear 35 is attached to the output shaft of the motor. The loader 13 includes a power receiving coil that receives power from a non-contact power feeding coil 37 of the component mounting machine 20. The loader 13 supplies the power received from the non-contact power feeding coil 37 to the motor. This allows the loader 13 to move in the X-axis direction (left and right direction) by rotating the gear using the motor. The loader 13 also rotates the rollers within the upper guide rail 31 and the lower guide rail 33, allowing it to move in the X-axis direction while maintaining its position in the up-down and front-back directions.

[0023] The host computer 15 shown in FIG. 1 is, for example, a personal computer, and is a device that manages the component mounting system 10. A production program (a so-called recipe) is stored in a storage device (such as a hard disk drive) of the host computer 15. This production program contains information such as the type of components to be mounted by each component mounting machine 20, the mounting order, and the number of components to be produced. The host computer 15 is connected to the device main body 41 of each component mounting machine 20 via a wire to enable bidirectional communication. For example, the component mounting machine 20 starts the mounting operation of electronic components based on the production program acquired from the host computer 15. The component mounting machine 20 performs the mounting operation of electronic components using the mounting head 25 while transporting the board 17.

[0024] The host computer 15 is also connected to an optical signal transmitter / receiver 51, which is a communication device for communicating with the loader 13. As shown in FIG. 1 , the optical signal transmitter / receiver 51 includes a light-emitting element 51A and a light-receiving element 51B, and is installed at the upstream end of the production line 11. The loader 13 also includes an optical signal transmitter / receiver 52, which is capable of communicating with the optical signal transmitter / receiver 51, located, for example, at the top of the device. The optical signal transmitter / receiver 52 includes a light-emitting element 52A and a light-receiving element 52B. The light-emitting element 51A and the light-receiving element 51B of the optical signal transmitter / receiver 51 are wirelessly connected to the light-receiving element 52B and the light-emitting element 52A of the optical signal transmitter / receiver 52 of the loader 13 via an optical wireless communication path 53, respectively, using optical signals, so as to be able to communicate wirelessly with the optical signal transmitter / receiver 52. The optical signal transmitter / receiver 51 is capable of bidirectional communication with the optical signal transmitter / receiver 52 via the optical wireless communication path 53. The optical wireless communication path 53 is a path along the X-axis direction, i.e., the direction in which the multiple component mounting machines 20 are lined up. While the loader 13 moves from the left end to the right end of the production line 11, it is capable of communicating with the optical signal transceiver 52, i.e., the host computer 15, via an optical wireless communication path 53. As the optical signal, for example, visible light can be used, but other optical signals such as infrared light can also be used.

[0025] The host computer 15 transmits operation instruction data to the loader 13, for example, via the optical wireless communication path 53. The loader 13 determines the replacement work and movement destination of the feeder 28 based on the data received by the optical signal transmitter / receiver 52. The loader 13 also transmits various I / O data, error information, and the like to the host computer 15 via the optical wireless communication path 53. The host computer 15 determines the control content of the loader 13 and executes error response processing, etc., based on the data received via the optical signal transmitter / receiver 51.

[0026] The host computer 15 also monitors the number of electronic components remaining in the feeder 28. For example, if the host computer 15 determines that a feeder 28 needs to be replenished, the host computer 15 displays on the screen an instruction to set the feeder 28 containing the component type that needs to be replenished on a placement table (not shown) provided upstream of the production line 11. The user checks the screen and sets the feeder 28 on the placement table. When the host computer 15 detects that the desired feeder 28 has been set on the placement table, it instructs the loader 13 to start the replenishment operation via the optical wireless communication path 53. After receiving the feeder 28 from the placement table, the loader 13 moves to the front of the component mounting machine 20 that received the instruction and mounts the feeder 28 received from the placement table into a slot on the feeder table 24. This allows a new feeder 28 to be replenished to the component mounting machine 20. The loader 13 also grips the out-of-component feeder 28 with its gripping section, pulls it out of the feeder table 24, retrieves it, and ejects it onto the placement table. In this way, the loader 13 can automatically supply new feeders 28 and collect feeders 28 that have run out of components.

[0027] (Configuration of component mounting machine 20) Next, a multiplex communication system provided in the component mounting machine 20 will be described. As shown in Fig. 2, the component mounting machine 20 includes an apparatus main body 41 and a fixed part board 45 in a module 22. The apparatus main body 41 and the fixed part board 45 are provided in the module 22 below the board transport device 23. Fig. 3 is a block diagram showing the configuration of a multiplex communication system applied to the component mounting machine 20. As shown in Figs. 2 and 3, in the component mounting machine 20 of this embodiment, data transmission between the fixed part board 45 fixed in the module 22 and the movable part (X-axis slide mechanism 27A and mounting head 25) that moves within the module 22 is performed by optical communication (multiplex communication) via optical fiber cables 81 and 82.

[0028] The device main body 41 has a servo amplifier 83, a device control main board 85, and an image processing board 87. The device control main board 85 is a device that comprehensively controls the operation of the component placement machine 20. The device control main board 85 is a computer-based device that includes, for example, a CPU, ROM, HDD, RAM, etc., and controls the board transport device 23, the placement head 25, the head moving mechanism 27, etc. The servo amplifier 83 is a device that controls the power supplied to the linear motor 77 of the X-axis slide mechanism 27A (described later) and the servo motor 75 of the placement head 25. The image processing board 87 is a board that receives and processes image data from the mark camera 69 of the X-axis slide mechanism 27A (described later) and the part camera 71 of the placement head 25.

[0029] Furthermore, fixed portion substrate 45 has an FPGA (Field Programmable Gate Array) 91, transmitting-side photoelectric converters 93A and 94A, and receiving-side photoelectric converters 93B and 94B. Furthermore, X-axis slide mechanism 27A has an X-axis substrate 95, mark camera 69, slave 61, linear motor 77, and linear scale 78. Furthermore, mounting head 25 has a head substrate 97, part camera 71, slave 62, servo motor 75, and encoder 76.

[0030] The component mounting machine 20 transmits and receives various data of the devices of the mounting head 25 and the X-axis slide mechanism 27A through multiplexed optical communication. The various data here refers to, for example, the linear scale signal of the linear scale 78 of the X-axis slide mechanism 27A and the encoder signal of the encoder 76 of the mounting head 25. The various data also refers to, for example, image data of the mark camera 69 and the parts camera 71. The various data also refers to control data of the slave 61 of the X-axis slide mechanism 27A and the slave 62 of the mounting head 25. An example of the multiplexed data will be described later using FIGS. 4 and 5, but the present invention is not limited to this.

[0031] The FPGA 91 on the fixed portion board 45 multiplexes data input from the servo amplifier 83, device control main board 85, and image processing board 87 of the device main body 41. For example, at startup, the FPGA 91 reads configuration information from a non-volatile memory (not shown) and constructs a logic circuit that performs the multiplexing process. The FPGA 91 multiplexes the input data, for example, using time division multiplexing (TDM). For example, the FPGA 91 multiplexes various data input from the servo amplifier 83, etc., according to a fixed time (time slot) assigned to each input port, and transmits the multiplexed data to the X-axis slide mechanism 27A and the mounting head 25 via the transmitting photoelectric converters 93A and 94A.

[0032] Furthermore, the X-axis substrate 95 of the X-axis slide mechanism 27A has a transmitting photoelectric converter 101A, a receiving photoelectric converter 101B, and an FPGA 103. The X-axis substrate 95 of the X-axis slide mechanism 27A and the head substrate 97 of the mounting head 25 have the same configuration as the fixed substrate 45. Therefore, in describing the X-axis substrate 95 and the head substrate 97, descriptions of the same configuration as the fixed substrate 45 will be omitted as appropriate. The transmitting photoelectric converter 93A and the receiving photoelectric converter 93B of the fixed substrate 45 are connected to the transmitting photoelectric converter 101A and the receiving photoelectric converter 101B of the X-axis slide mechanism 27A via an optical fiber cable 81. The FPGA 103 multiplexes the image data of the mark camera 69, the linear scale signal of the linear scale 78, the control data of the slave 61, etc.

[0033] Similarly, the head substrate 97 of the mounting head 25 has a transmitting photoelectric converter 111A, a receiving photoelectric converter 111B, and an FPGA 113. The transmitting photoelectric converter 94A and the receiving photoelectric converter 94B of the fixed portion substrate 45 are connected to the transmitting photoelectric converter 111A and the receiving photoelectric converter 111B of the mounting head 25 via an optical fiber cable 82. The FPGA 113 multiplexes image data from the part camera 71 of the mounting head 25, the encoder signal from the encoder 76, control data from the slave 62, and the like. Note that the circuits (FPGAs 91, 103, 113) that perform the multiplexing process are not limited to FPGAs and may also be programmable logic devices (PLDs) or complex programmable logic devices (CPLDs). The multiplexing process may also be realized by processing using an application-specific integrated circuit (ASIC) or software processing by a CPU.

[0034] The optical fiber cables 81 and 82 have enhanced bending resistance, for example, by adjusting the arrangement and thickness of the optical fiber wires within the cables. This allows stable data transmission without damaging the optical fiber wires even when the optical fiber cables 81 and 82 are bent due to movement of the mounting head 25 or the X-axis slide mechanism 27A. As shown in FIG. 1 , the optical fiber cables 81 and 82 are attached to, for example, the frame 22A of the module 22 that supports the device cover of the component mounting machine 20. They are arranged in a direction parallel to the Z-axis direction from the fixed part board 45 within the module 22 and connected to the mounting head 25 and the X-axis slide mechanism 27A. The optical fiber cable 81 connects two optical fiber cables via, for example, a repeater 81A attached to the frame 22A, and connects the fixed part board 45 to the X-axis board 95 of the X-axis slide mechanism 27A. The repeater 81A is attached, for example, to the middle position of the frame 22A extending in the Z-axis direction and has two connection ports. The repeater 81A has one connection port into which the optical fiber cable on the X-axis substrate 95 side is inserted, and the other connection port into which the optical fiber cable on the fixed portion substrate 45 side is inserted. The repeater 81A relays optical signals between the two optical fiber cables.

[0035] Similarly, the optical fiber cable 82 connects two optical fiber cables via a repeater 82A attached to the frame 22A, connecting the fixed unit substrate 45 and the head substrate 97 of the mounting head 25. With this configuration, for example, if a fault such as a crack occurs in a portion of the optical fiber cable 81, of the two optical fiber cables relayed by the repeater 81A, the optical fiber cable connected to the X-axis substrate 95 or the optical fiber cable connected to the fixed unit substrate 45 can be replaced. In other words, there is no need to replace all of the optical fiber cables from the fixed unit substrate 45 to the movable unit (X-axis slide mechanism 27A and the mounting head 25), and the fault can be restored by simply replacing one of the two optical fiber cables relayed by the repeaters 81A and 82A. Note that the optical fiber cables 81 and 82 may be configured to connect the fixed unit substrate 45 and the movable unit with a single optical fiber cable without using the repeaters 81A and 82A. Furthermore, the communication connecting the fixed portion substrate 45, the mounting head 25, and the X-axis slide mechanism 27A is not limited to wired communication, but may be optical wireless communication such as the optical wireless communication path 53 of the loader 13 (see FIG. 1).

[0036] The transmitting-side photoelectric converter 93A on the fixed portion substrate 45 converts the multiplexed data multiplexed by the FPGA 91 into an optical signal and transmits it to the receiving-side photoelectric converter 101B on the X-axis substrate 95 via the optical fiber cable 81. The receiving-side photoelectric converter 101B converts the optical signal received from the transmitting-side photoelectric converter 93A into a photocurrent, which is an electrical signal, and outputs it to the FPGA 103. The FPGA 103 of this embodiment has an AD conversion circuit and the like, and converts the analog photocurrent into a digital signal for processing.

[0037] The FPGA 103 also demultiplexes the converted digital signal, i.e., the multiplexed data, and separates the multiplexed data. The FPGA 103 outputs the separated data to the corresponding devices. This allows multiplexed communication (optical communication) between the fixed part substrate 45 and the X-axis slide mechanism 27A, in which the various data are multiplexed. Similarly, the FPGA 103 multiplexes image data from the mark camera 69 and transmits it to the receiving side photoelectric converter 93B of the fixed part substrate 45 via the transmitting side photoelectric converter 101A. The FPGA 91 demultiplexes the multiplexed data and outputs the separated data to the image processing board 87 of the device main body 41, etc.

[0038] Similarly to the X-axis slide mechanism 27A, the fixed portion substrate 45 also performs multiplexed optical communication with the mounting head 25. The transmitting side photoelectric converter 94A and the receiving side photoelectric converter 94B of the fixed portion substrate 45 are connected to the transmitting side photoelectric converter 111A and the receiving side photoelectric converter 111B of the head substrate 97 via optical fiber cables 82, respectively. The FPGA 91 of the fixed portion substrate 45 performs multiplexed communication with the FPGA 113 of the head substrate 97 via the optical fiber cable 82. The multiplexed communication line of the optical fiber cables 81 and 82 is full duplex communication of, for example, 5 Gbps.

[0039] In this embodiment, the device main body 41 controls the X-axis slide mechanism 27A and the mounting head 25 through the multiplexed optical communication. The servo amplifier 83 of the device main body 41 initializes the linear scale 78 of the X-axis slide mechanism 27A and acquires a linear scale signal. The linear scale 78 transmits a linear scale signal indicating the slide position of the X-axis slide mechanism 27A to the servo amplifier 83 via multiplexed communication. The servo amplifier 83 is connected to the linear motor 77 of the X-axis slide mechanism 27A via a power line (not shown) and performs feedback control of the linear motor 77 by changing the power supplied to the linear motor 77 based on the linear scale signal from the linear scale 78. The device control main board 85 controls the servo amplifier 83 based on the production program received from the host computer 15. As a result, the X-axis slide mechanism 27A moves to a position in the X-axis direction based on the production program.

[0040] Similarly, the servo amplifier 83 performs initialization processing for the encoder 76 of the mounting head 25, acquires the encoder signal, and the like. The encoder 76 transmits an encoder signal indicating the rotational position of the servo motor 75 to the servo amplifier 83 via multiplex communication. As described above, the servo motor 75 functions as a drive source for driving the holding member of the mounting head 25. The servo amplifier 83 is connected to the encoder 76 of the mounting head 25 via a power line (not shown), and performs feedback control of the servo motor 75 based on the encoder signal of the encoder 76. As a result, the mounting head 25 rotates and moves the holding member up and down based on the production program.

[0041] Furthermore, the device control main board 85 of the device body 41 is capable of controlling the relays, sensors, and the like provided in the X-axis slide mechanism 27A and the mounting head 25 via the above-mentioned industrial network. The device control main board 85 functions as a master in the industrial network and transmits control data to the slave 61 of the X-axis slide mechanism 27A and the slave 62 of the mounting head 25 via multiplex communication. The slaves 61 and 62 drive the relays and sensors of the X-axis slide mechanism 27A and the mounting head 25 based on the control data received from the device control main board 85. The slaves 61 and 62 also write the values ​​of signals acquired from the relays and sensors into control data and transmit it to the device control main board 85 via multiplex communication. This allows the device control main board 85 to control the relays, etc. of each device.

[0042] The configuration of the multiplex communication system shown in FIG. 3 is an example and can be modified as appropriate. For example, a linear scale signal attached to a linear motor (not shown) of the Y-axis slide mechanism 27B (see FIG. 2) may be transmitted by multiplex communication. Furthermore, signals from a relay or the like of the Y-axis slide mechanism 27B may be transmitted by multiplex communication. Furthermore, the fixed portion board 45 may include a slave controlled by the device control main board 85. Furthermore, the slave 61 may be a circuit block (such as an IP core) of the FPGA 103, i.e., a part of the FPGA 103. Furthermore, the component placement machine 20 may not include devices related to the industrial network (such as a circuit that functions as a master of the device control main board 85, slaves 61 and 62, etc.).

[0043] With the above-described configuration, the device control main board 85 controls the component placement machine 20 based on the production program received from the host computer 15. The device control main board 85 receives data collected via the industrial network, the linear scale signal of the linear scale 78, the encoder signal of the encoder 76, and the like via multiplex communication. The device control main board 85 also inputs the results (such as holding position errors) of image data captured by the mark camera 69 and the parts camera 71 processed by the image processing board 87. Based on this data, the device control main board 85 determines the next control content (such as the type of electronic component to be placed and the placement position). The device control main board 85 controls various devices according to the determined control content.

[0044] (Configuration of multiplexed data) Next, the contents of the multiplexed data transmitted by the above-mentioned multiplex communication will be described. Fig. 4 shows the contents of the multiplexed data transmitted from the fixed part substrate 45 to the mounting head 25 in the multiplex communication of the optical fiber cable 82. Fig. 5 shows the contents of the multiplexed data transmitted from the mounting head 25 to the fixed part substrate 45 in the optical fiber cable 82. Note that the data arrangement and data contents in Figs. 4 and 5 are merely examples. Furthermore, the multiplexed data transmitted by the optical fiber cable 81 connecting the fixed part substrate 45 and the X-axis slide mechanism 27A can have the same configuration as the multiplexed data of the optical fiber cable 82 (such as a configuration in which the part camera 71 is replaced with the mark camera 69 or a configuration in which the encoder 76 is replaced with the linear scale 78), and therefore description thereof will be omitted.

[0045] 4 and 5 each show 32 bits of multiplexed data (8-bit blocks A to D). For example, in order to maintain the DC balance of the transmission data, the multiplexed data is converted into 8B / 10B data for every 8 bits (each block), resulting in a total of 40 bits. Therefore, for example, one frame of multiplexed data is made up of 40 bits. For example, if the period per frame is set to 8 nsec (frequency is 125 MHz), the FPGA 91, 113 will build a multiplexed communication line of 5 Gbps (40 bits x 125 MHz).

[0046] 4 and 5 show multiplexed data for each clock (e.g., 8 nsec). Also, FIGS. 4 and 5 show data for 10 clocks, 0 to 9. Block A (bits 0 to 7) at the beginning of the multiplexed data transmitted from the fixed part substrate 45 shown in FIG. 4 is used, for example, to transmit a control command to the mounting head 25. This command is, for example, a control symbol for the K code in 8B / 10B conversion. Block B of the multiplexed data shown in FIG. 4 contains the same data as block A. Reed-Solomon coding, for example, can be used as a method for error correction of blocks A and B. For example, when receiving multiplexed data, the FPGAs 91 and 113 perform error detection and correction on the demultiplexed data of block A based on the Reed-Solomon coding. Blocks A and B contain a one-bit value indicating the presence or absence of data. This bit value indicating the presence or absence of data indicates whether valid data is set in blocks A and B when the communication speed between devices inputting and outputting data transmitted in blocks A and B is slower than the communication speed (5 Gbps) of multiplex communication. This allows the receiving device receiving the data in blocks A and B to detect whether valid data is set based on the bit value indicating the presence or absence of data, and can quickly process or discard the data.

[0047] 5, pixel values ​​(image data) of the part camera 71 are set in blocks A and B of the multiplexed data transmitted from the mounting head 25. Reed-Solomon coding, for example, can be used as an error correction method. If the mounting head 25 is equipped with multiple cameras, blocks A and B may be used to transmit image data from each camera.

[0048] 4, control signals for controlling the part camera 71 are set. The control signals here are, for example, control signals CC1 to CC4 in the Camera Link standard. Alternatively, the control signal is a trigger signal (CAM-TRG in the figure) that instructs the part camera 71 to capture an image. Furthermore, a bit value indicating the presence or absence of data in block C is set in BIT0 of block C.

[0049] In addition, bit 6 of block C is set with a parity bit (K code flag in the figure) to detect whether a burst error exceeding the correction capability has occurred during Reed-Solomon coding of block B. Specifically, for example, the Reed-Solomon coding is set to correct consecutive errors in two consecutive blocks. In this case, if consecutive errors in three or more blocks occur during multiplex communication, the receiving side (mounting head 25) cannot correct the data. Therefore, bit 6 of block C is set with even parity corresponding to, for example, the 8 bits of block B. If consecutive errors in three or more blocks are detected on the receiving side, an abnormal stop or image data correction (when the fixed part board 45 in Figure 5 is the receiving side) is performed. In addition, bit 7 of block C is set with a parity bit corresponding to block A, just like bit 6. In addition, in block C of the multiplexed data shown in Figure 5, parity bits (K code flag in the figure) are set in bits 6 and 7, just like in Figure 4. The blank areas shown in FIG. 5 (BIT0 to BIT5 of block C) indicate empty bits to which no data is set.

[0050] 4 and 5, the encoder signal of the encoder 76 of the mounting head 25 is set in BITs 0 to 3 of block D. In the case of FIG. 4, the encoder signal refers to an initial setting signal sent from the servo amplifier 83 to the encoder 76, a signal for inquiring about the status, a signal for acquiring position information, and the like. In the case of FIG. 5, the encoder signal refers to a signal indicating position information and the like sent from the encoder 76 to the servo amplifier 83. For example, the mounting head 25 includes four sets of servo motors 75 and encoders 76. In this case, the mounting head 25 can move the holding member in four movement directions. In FIGS. 4 and 5, four BITs 0 to 3 are set corresponding to the four encoders 76. In addition, a Hamming code, for example, can be used as a method for correcting errors in the data of block D.

[0051] In BIT0 of block D, data of the encoder signal is set in the first four clocks (clocks 0 to 4 in FIGS. 4 and 5) out of 10 clocks (E1 in FIGS. 4 and 5). The encoder signal is bit-assigned to each bit position in clocks 0 and 2. Furthermore, information indicating the presence or absence of encoder signal data ("E1 presence / absence" in FIGS. 4 and 5) is bit-assigned to each bit position in clocks 1 and 3. As described above, this information indicating the presence or absence of data is information for indicating whether or not a slow encoder signal is set in each bit position (clocks 0 and 1 of BIT0) when, for example, the data transfer rate of the encoder signal is slower than the data transfer rate of the multiplexed data. The encoder signal and the information indicating the presence or absence of that encoder signal are set alternately every cycle.

[0052] In addition, clock 4 of BIT0 is set with timeout information indicating whether a timeout error has occurred in the communication between the servo amplifier 83 and the encoder 76. In addition, a bit value for a cyclic redundancy check (CRC) is set by the transmitting side in clock 5 of BIT0 ("CRC abnormality" in FIGS. 4 and 5). In clocks 6 to 9 of BIT0, a 4-bit code bit, which is a Hamming code for forward error correction, is set. The error correction code is, for example, a shortened form of the Hamming code (15, 11). In addition, in clocks 6 to 9 of BIT1 to 7, a 4-bit code bit is set, similar to BIT0. When receiving multiplexed data, the FPGAs 91 and 113 perform error detection and correction on the data, such as the demultiplexed encoder signal, based on the error correction code. In addition, in BIT1 to BIT3, data related to the encoder signal is set, similar to BIT0.

[0053] 4 and 5, a control signal for the part camera 71 is set in BIT4 of block D. The control signal here is, for example, a UART communication control signal that controls the illumination of the part camera 71, for example, if the part camera 71 is a camera conforming to the Camera Link standard. Information related to the data values ​​of clocks 0 to 3 is set in clocks 4 and 5 of BIT4.

[0054] Furthermore, data relating to an industrial network, for example, EtherCAT (registered trademark), is set in bits 5 and 6 of block D shown in FIGS. 4 and 5 (such as "EC" in FIGS. 4 and 5). This data is control data for the slave 62. EtherCAT (registered trademark) control data is set in four bits of clocks 0 to 3 of bits 5 and 6. Information indicating the presence or absence of data is set in clock 4 of bits 5 and 6. Furthermore, a bit value for a cyclic redundancy check (CRC) is set in clock 5 of bit 5 by the transmitting side.

[0055] Furthermore, data related to a digital input / output signal (DIO signal) is set in BIT7 of block D shown in FIGS. 4 and 5. This DIO signal is a signal that drives various relays, sensors, etc. attached to the module 22 or the mounting head 25, or a signal output from the relays, sensors, etc. For example, the device main body 41 uses the DIO signal to drive various relays and sensors and acquires signals from the relays and sensors. A bit value indicating the content of the DIO signal is set in four bits of clocks 0 to 3 of BIT7. Furthermore, a parity code of the DIO signal is set in two bits of clocks 4 and 5 of BIT7. For example, in error detection processing of the DIO signal, in addition to error correction using a Hamming code, multiple match checks are performed using the parity code of clocks 4 and 5. Specifically, the transmitted data is acquired after confirming that all data have the same data value in a predetermined number of consecutive transmissions. If the data value differs even once during the consecutive transmissions, the data transmission is canceled. Incidentally, the error detection and correction process for the DIO signal may be performed using only either the Hamming code or the parity code.

[0056] 4 and 5 are merely examples. For example, the signal from a board height sensor attached to the X-axis slide mechanism 27A may be transmitted via multiplex communication to detect data errors. The board height sensor here refers to a sensor that measures the height of the top surface of the board 17 based on a reference height position set in the component mounting machine 20. For example, the device main body 41 may acquire the board height sensor signal using data at a bit position in a predetermined block of multiplex communication. In this case, a Hamming code, for example, may be used as the error detection and correction code for the board height sensor signal.

[0057] (Error detection and correction in multiplexed communications) Next, we will explain the data error detection and correction process performed by the component placement machine 20 of this embodiment in the above-mentioned multiplex communication system. Each of the FPGAs 91, 103, and 113 separates various data from the multiplexed data received in the multiplex communication and performs error detection and correction on the separated data using the Reed-Solomon code or Hamming code described above. Each of the FPGAs 91, 103, and 113 records the number of error corrections performed as a log and notifies the device control main board 85 of the device main body 41 that the correction has been performed. The FPGAs 103 and 113 record the number of error corrections performed and notify the device control main board 85 of the device main body 41 that the correction has been performed via the multiplex communication of the optical fiber cables 81 and 82 and the FPGA 91. The FPGAs 103 and 113 notify the device control main board 85 that the correction has been performed, for example, using the empty bits (BIT0 to BIT5) of block C in FIG. 5. The device control main board 85 issues notification information related to a communication abnormality when the number of corrections notified from the FPGAs 91, 103, and 113 exceeds a predetermined threshold number within a predetermined time. For example, the device control main board 85 displays the notification information on the touch panel 29A of the operation unit 29. The error detection and stop processing by the FPGAs 103 and 113 is the same as that by the FPGA 91. Therefore, the following description will mainly focus on the error detection and correction processing by the FPGA 91, and will omit the processing by the FPGAs 103 and 113 as appropriate. Furthermore, the description will mainly focus on the case where the FPGA 91 detects and corrects data errors in the multiplexed data received from the mounting head 25 (FPGA 113). Furthermore, the FPGAs 91, 103, and 113 perform multiple match checks using parity codes on the digital input / output signals of BIT7 of block D shown in Figures 4 and 5. The FPGAs 91, 103, and 113 may record the number of error detections by multiple match checks, similar to the number of error corrections described above, and may notify the device control main board 85 that an error has been detected. Then, the device control main board 85 may notify notification information related to a communication abnormality when the number of error detections notified from the FPGAs 91, 103, and 113 reaches or exceeds a predetermined threshold number within a predetermined time period.

[0058] FIG. 6 shows the notification control process executed by the component placement machine 20. First, in step (hereinafter simply referred to as S) 11 of FIG. 6, the device main body 41 of the component placement machine 20 starts system startup when the user turns on the power. The device main body 41 controls a power supply (not shown) to supply power to each device of the component placement machine 20. When power is supplied and the FPGA 91 starts up, it reads configuration information from a nonvolatile memory (not shown) and builds a logic circuit that performs multiplexing processing (S13). This logic circuit includes a logic circuit that multiplexes data, a logic circuit that separates received multiplexed data, a logic circuit that performs error detection and correction on various separated data (see FIGS. 4 and 5), and a logic circuit that records the number of error corrections that have been performed.

[0059] After constructing the logic circuit, the FPGA 91 establishes multiplexed communication with the FPGAs 103 and 113 (S15). If the communication is successfully established, the FPGA 91 notifies the device main body 41 that the communication has been established. Once the establishment of multiplexed communication and preparation of various devices are complete, the device control main board 85 of the device main body 41 starts the electronic component mounting work (S17). The device control main board 85 acquires a production program from the host computer 15, for example, and starts the mounting work when it acquires an instruction to start the work.

[0060] On the other hand, after establishing multiplex communication in S15, the FPGAs 91, 103, and 113 perform error detection processing on the multiplexed data received in the multiplex communication (S19). The FPGAs 91, 103, and 113 perform error detection processing using Reed-Solomon codes or Hamming codes. Note that the timing at which the FPGAs 91, 103, and 113 start error detection processing is not limited to the timing at which the mounting operation begins, but may also be the timing at which the multiplex communication is established.

[0061] For example, during the mounting operation, the FPGA 91 determines whether an error has been detected in the multiplexed data received from the head substrate 97 (FPGA 113) (S19). If no error is detected in the FPGAs 91, 103, and 113 (S19: NO), for example, if no error detection notification is received from any of the FPGAs 91, 103, and 113 for a certain period of time, the device main body 41 determines whether the mounting operation has been completed using the device control main board 85 (S29). If the device control main board 85 determines that the operation based on the production program has not been completed (S29: NO), the device main body 41 causes the FPGAs 91, 103, and 113 to perform the determination process of S19 again. As a result, the device main body 41 causes the FPGAs 91, 103, and 113 to perform data error detection (S19), while also causing the device control main board 85 to determine whether the mounting operation has been completed (S29). When the device control main board 85 determines that the mounting operation has been completed (S29: YES), the device main body 41 ends the processing shown in Fig. 6. For example, when the device main body 41 receives an instruction to start the next mounting operation from the host computer 15, it executes the processing from S17.

[0062] In S19, for example, the FPGA 91 detects a data error for each unit of data to which a predetermined number of symbols in a Reed-Solomon code or a Hamming code has been added, and if an error is detected, a positive determination is made in S19 (S19: YES). If the FPGA 91 detects an error (S19: YES), it executes a process to correct the detected error (S21). If the FPGA 91 corrects the error, it stores information related to the error correction as a log in the FPGA 91's memory or the like (S23). The FPGA 91 stores information such as the time the error was corrected and the type of corrected data. The FPGA 91 also notifies the device control main board 85 that the error correction has been executed (S23). The FPGA 91 notifies the device control main board 85 of, for example, the communication path (optical fiber cables 81, 82) on which the error correction was executed, the type of data on which the correction was executed (block name, bit position (in the case of a Hamming code), data name, type of error correction code, etc.), and time information on the correction. Like the FPGA 91, the FPGAs 103 and 113 perform data error detection and correction on the received multiplexed data, and perform log recording and notification to the device control main board 85.

[0063] For example, when the device control main board 85 receives the notification of S23 from the FPGA 91, it determines whether the number of error corrections N performed by the FPGA 91 within a predetermined time period is equal to or greater than a first threshold number of corrections TH1 (S25). The predetermined time period in S25 is, for example, one hour. The first threshold number of corrections TH1 is, for example, 20 times. For example, as shown in FIG. 5, the FPGA 91 performs error detection and correction for each of blocks A, B, and C using a Reed-Solomon code, or for each bit position of block D using a Hamming code. The FPGA 91 performs error detection and correction for each block or bit position (hereinafter referred to as "each block, etc.") and notifies the device control main board 85 of the number of corrections for each block, etc. For example, the device control main board 85 stores the notifications from the FPGA 91 as a history, and when a new notification is received, it retrieves the number of notifications received within the past hour from the history. The device control main board 85 determines the number of corrections N for each block individually, and if error corrections have been performed 20 or more times within one hour for at least one block (at least one bit position for block C) among the four blocks A to D, it makes a positive determination in S25 (S25: YES) and executes S27. Furthermore, if the number of error corrections N within one hour for all four blocks (all bit positions for block C) is less than 20, the device control main board 85 makes a negative determination in S25 (S25: NO) and executes S31. The device control main board 85 may determine the number of corrections N for each line, rather than for each block. For example, the device control main board 85 may make a positive determination in S25 if the cumulative total of the number of corrections N for blocks A to D within one hour in the multiplexed data received from the mounting head 25 is equal to or greater than the first threshold number TH1.

[0064] In S27, the device control main board 85 executes a first notification process and displays notification information on the touch panel 29A instructing the user to replace the optical fiber cable 82. FIG. 7 shows an example of a display screen 121 displayed on the touch panel 29A during the first notification process of S27. As shown in FIG. 7, the device control main board 85 displays, for example, a replacement message 123 and a work instruction message 124 on the display screen 121. As the replacement message 123, the device control main board 85 displays text indicating that data errors are increasing and urging the user to replace the optical fiber cable 82. If the number of data errors increases significantly, it is highly likely that the optical fiber cable 82 is cracked, making it difficult to maintain communication quality. On the other hand, if the number of data errors increases only slightly, possible causes include an improper connection of the optical fiber cable 82 or the user touching the connection during replacement and making it dirty. In other words, it is possible that data errors can be reduced by cleaning or other methods without replacing the optical fiber cable 82. Therefore, if corrections equal to or greater than a first threshold number TH1, which is greater than a second threshold number TH2 (described later), occur within a predetermined time, the device control main board 85 displays a replacement message 123 urging the user to replace the optical fiber cable 82. This allows the user to quickly replace the optical fiber cable 82, shortening the downtime during which the mounting operation of the component mounting machine 20 is suspended, and improving productivity. Therefore, the first threshold number TH1 used in S25 is a value that can detect the number of occurrences of data errors (number of corrections N) that has increased due to factors that require replacement of the optical fiber cable 82, such as a crack in the optical fiber cable 82.

[0065] Furthermore, the device control main board 85 displays information in the replacement message 123 indicating which of the optical fiber cables 81 and 82 is the optical fiber cable to be replaced. For example, the device control main board 85 has numbers NO: 01 and 02 set for each of the optical fiber cables 81 and 82. Numbers are also affixed to the coatings of the actual optical fiber cables. Then, in S27, the device control main board 85 displays, as the cable NO, the number corresponding to the optical fiber cable 81 or 82 whose number of corrections N has increased in the replacement message 123. This allows the user to easily determine which optical fiber cable is to be replaced by looking at the displayed cable NO.

[0066] Furthermore, the device control main board 85 displays, as a work instruction message 124, notification information urging the user to perform maintenance on the device that processed the data on the transmitting side for which the number of error corrections N has increased. The device control main board 85 can identify the data for which the number of corrections N has increased and the device that processes that data on the transmitting side based on the information (such as block name and bit position) notified from the FPGA 91. FIG. 7 shows, as an example, a work instruction message 124 when the number of corrections N for image data from the part camera 71 (see blocks A and B in FIG. 5) has increased. As shown in FIG. 7, the device control main board 85 displays, as the work instruction message 124, a message indicating that the number of data errors in the part camera 71 has increased and urging the user to check the operation of the part camera 71.

[0067] Therefore, the device control main board 85 displays notification information urging the user to perform maintenance on the device (e.g., part camera 71) that processed the data on the transmitting side for which the number of error corrections N has increased among the multiplexed data. This allows the user to focus on maintenance items related to the part camera 71, such as taking test images of the part camera 71 or reconstructing the logic circuit that processes the image data from the part camera 71. The cause of the data error can be identified and resolved more quickly.

[0068] After executing S27, the device control main board 85 determines whether or not to end the mounting work (S29). If the device control main board 85 determines that the mounting work has not been completed (S29: NO), the device main body 41 causes the FPGAs 91, 103, and 113 to execute the determination process of S19. If the device control main board 85 determines that the mounting work has been completed (S29: YES), the device main body 41 ends the process shown in FIG. 6. The device control main board 85 may stop the mounting work depending on the occurrence of errors in the multiplexed data. For example, the device control main board 85 may stop the mounting work if the number of error corrections performed within a predetermined time exceeds an upper limit. This allows the mounting work to be quickly stopped if, for example, the optical fiber cables 81 and 82 are completely disconnected.

[0069] Meanwhile, in S31, the device control main board 85 determines whether the number of corrections N performed by the FPGA 91 within a predetermined time is equal to or greater than a second threshold number of corrections TH2. The predetermined time in S31 is, for example, one hour. The second threshold number of corrections TH1 is, for example, 10 times. Therefore, the second threshold number of corrections TH2 is less than the first threshold number of corrections TH1 described above. More specifically, the second threshold number of corrections TH2 is a value that can detect the number of corrections N that occurs due to, for example, dirt on the connection portion of the optical fiber cable 81, and is a value that can detect the occurrence of a data error in a situation where replacement of the optical fiber cable 82 is not required.

[0070] If error correction has been performed 10 or more times within one hour for at least one block (for block C, at least one bit position) among the four blocks A to D, the device control main board 85 makes a positive determination in S31 (S31: YES) and executes S33. If the number of error corrections N within one hour for all four blocks is less than 10, the device control main board 85 makes a negative determination in S31 (S31: NO) and executes S19 again. Therefore, if the number of corrections N is less than the second threshold number TH2, the component mounting machine 20 continues the mounting operation without executing the notification process.

[0071] In S33, the device control main board 85 executes the second notification process, and displays a cleaning message 127 and a work instruction message 128 on the display screen 125 of the touch panel 29A, as shown in FIG. 8. As shown in FIG. 8, the device control main board 85 displays the cleaning message 127, informing the user that data errors have increased, urging the user to clean the connection of the optical fiber cable 82, and displaying the cable number. This urges the user to check and clean the connection of the optical fiber cable 82, for example, the connection between the optical fiber cable 82 and the mounting head 25, or the connection between the repeater 82A. Similarly to S27, the device control main board 85 also displays a work instruction message 128 urging the user to perform maintenance on the device that processed the data with an increased number of corrections N on the transmitting side. FIG. 7 shows, as an example, the work instruction message 128 when the number of corrections N of the encoder data (BIT1 to BIT4 of block D in FIG. 5) of the encoder 76 has increased. The device control main board 85 determines the number of corrections N for each of the four encoder data (BIT1 to BIT4 of block D in FIG. 5), and displays information that enables identification of the encoder 76 for which the number of corrections N has increased in the work instruction message 128. The device control main board 85 displays, for example, information about the rotation axis of the servo motor 75 to which the encoder 76 is attached (Z-axis in the illustrated example) in the work instruction message 128. The device control main board 85 displays, in the work instruction message 128, that there has been an increase in data errors in the Z-axis encoder 76 and that a check of the operation of the encoder 76 and the servo motor 75 is urged. After executing S33, the device control main board 85 determines whether or not to end the mounting work (S29).

[0072] If a certain number of data errors continue to occur, the device control main board 85 may urge the user to, for example, replace the optical fiber cable 82. For example, if the number of corrections N is equal to or less than the second threshold number of times TH2, or if the number of corrections N is less than the first threshold number of times TH1 and equal to or greater than the second threshold number of times TH2 continues for a certain period of time, the device control main board 85 may display a message on the touch panel 29A indicating that the optical fiber cable 82 should be replaced, for example.

[0073] Furthermore, in the above explanation, the multiplexed data received by the FPGA 91 via the optical fiber cable 82 has been mainly described, but the number of data corrections can also be monitored and notification information can be reported for the multiplexed data received by the FPGA 91 via the optical fiber cable 81 and the multiplexed data received by the FPGAs 103 and 113 in a similar manner. For example, the FPGA 113 of the mounting head 25 detects and corrects data errors in the multiplexed data (see FIG. 4) received from the fixed part substrate 45, in the same manner as the FPGA 91 described above. The FPGA 113 detects data errors for each block of the multiplexed data shown in FIG. 4 and notifies the device control main substrate 85.

[0074] As described above, the device control main board 85 determines whether the number of corrections N that occurred in the FPGA 91 within a predetermined time (e.g., one hour) is equal to or greater than the first threshold number TH1 or the second threshold number TH2 (S25, S31), thereby determining whether the number of detected data errors has increased. In this configuration, an increase in data errors can be detected using the first threshold number TH1 or the second threshold number TH2. Furthermore, by adjusting the values ​​of the first threshold number TH1, etc., a notification can be issued at a desired timing.

[0075] Furthermore, if the number of corrections N is equal to or greater than the first threshold number of times TH1 (S25: YES), the device control main board 85 displays an instruction to replace the optical fiber cable 81 (see FIG. 7). Furthermore, if the number of corrections N is equal to or greater than a second threshold number of times TH2 that is less than the first threshold number of times TH1 (S31: YES), the device control main board 85 displays an instruction to clean the connection portion of the optical fiber cable 81 (see FIG. 8). This allows instructions to be given to the user according to the increase in the number of corrections N, allowing the user to take more appropriate action. For example, if cleaning the optical fiber cable 82 is sufficient, the installation work can be resumed without performing unnecessary work such as replacing the optical fiber cable 82.

[0076] Furthermore, the FPGA 91 performs error correction based on an error correction code such as a Reed-Solomon code or a Hamming code for each of the plurality of data separated from the received multiplexed data (S21). The device control main board 85 determines the number of times an error in at least one of the plurality of data multiplexed into the multiplexed data (the data for each of blocks A to C and the data at each bit position of block D) has been corrected as the number of corrections N, and determines whether the number of corrections N has increased (S25, S31). This allows for faster detection of a fault by monitoring each piece of data when a bend or disconnection occurs in the optical fiber cable 82 and the number of errors occurring in any of the multiplexed data increases.

[0077] The FPGA 91 also detects and corrects data errors in the multiplexed data received via each of the optical fiber cables 81 and 82. The device control main board 85 determines an increase in the number of corrections N for each of the optical fiber cables 81 and 82 individually and issues a notification. This allows the number of error corrections N to be monitored individually for each of the two optical fiber cables 81 and 82 connected to one optical receiving device. In particular, the optical fiber cables 81 and 82 connected to movable devices such as the X-axis slide mechanism 27A and the mounting head 25 of this embodiment are likely to suffer from cracks or breaks in the signal lines. For this reason, it is extremely effective to individually monitor data errors in the optical fiber cables 81 and 82 connecting such movable devices.

[0078] Incidentally, in the above embodiment, the substrate 17 is an example of a workpiece of the present disclosure. The mounting head 25 is an example of a head. The X-axis slide mechanism 27A is an example of a first moving device. The Y-axis slide mechanism 27B is an example of a second moving device. The component mounting machine 20, the device main body 41, and the fixed part substrate 45 are examples of optical communication devices. The optical fiber cables 81 and 82 are an example of wired cables. The optical fiber cable 81 is an example of a second wired cable. The optical fiber cable 82 is an example of a first wired cable. The FPGAs 91, 103, and 113 are examples of detection devices. The device control main board 85 is an example of a determination device. The transmitting-side photoelectric converters 93A, 94A, 101A, and 111A and the light-emitting elements 51A and 52A are examples of optical transmitting devices. The transmitting-side photoelectric converter 101A is an example of a first moving device optical transmitting device. The transmitting side photoelectric converter 111A is an example of a head side optical transmitting device. The receiving side photoelectric converters 93B, 94B, 101B, 111B and the light receiving elements 51B, 52B are examples of an optical receiving device. The replacement message 123, the work instruction messages 124, 128, and the cleaning message 127 are examples of notification information. The multiplexed data is an example of received data. The X-axis direction is an example of a first direction. The Y-axis direction is an example of a second direction. S19 is an example of a detection process. S25, S27, S31, and S33 are examples of a notification process.

[0079] As described above, the present embodiment provides the following effects. In one aspect of this embodiment, the FPGA 91 detects data errors in the multiplexed data received by the receiving-side photoelectric converter 94B (S19) and corrects the data errors (S21). The device control main board 85 determines an increase in the number of error corrections N by the FPGA 91 (S25, S31), and based on the determination that the number of corrections N has increased, issues notification information related to a communication abnormality (S27, S33). In this way, when the quality of communication decreases and data errors increase due to deterioration of the light-emitting elements of the optical communication or the optical fiber cables 81, 82, the occurrence or possibility of a communication failure can be notified to the user by the notification information.

[0080] It goes without saying that the present disclosure is not limited to the above-described embodiments, and various improvements and modifications are possible within the scope of the present disclosure. For example, the optical communication device that performs the optical communication of the present disclosure may be configured such that both the transmitting and receiving devices are movable, or may be configured such that both devices are fixed. Furthermore, the detection device of the present disclosure does not have to be a programmable logic device such as the FPGA 91. For example, the process of detecting data errors may be realized by hardware processing such as ASCI, or may be realized by software processing such as by executing a program on a CPU. 6 are merely examples. For example, in the above embodiment, the determination process using the first threshold number of times TH1 in S25 and the determination process using the second threshold number of times TH2 in S31 are executed by the device control main board 85, but these may also be executed by the FPGA 91. Furthermore, the data error detection process in S19 may also be executed by the device control main board 85. Furthermore, in the above example, the FPGAs 91, 103, and 113 correct errors, but they may also only detect errors. For example, the FPGA 91 may only detect errors in the multiplexed data received from the mounting head 25 and notify the device control main board 85. Specifically, the FPGA 91 performs multiple match checks using parity codes on the digital input / output signals shown in FIGS. 4 and 5 and notifies the device control main board 85 that an error has been detected. The device control main board 85 may then notify information related to a communication abnormality when the number of error detections notified by the FPGA 91 exceeds a predetermined threshold number within a predetermined time period. Therefore, instead of Reed-Solomon codes or Hamming codes, parity codes or the like that can detect errors but do not have a correction function may also be used.

[0081] In addition, the device control main board 85 notifies notification information when the number of corrections N of at least one of the multiple data multiplexed into the multiplexed data increases, but the notification may be performed only when the number of corrections N of all data (blocks A to D) increases. In the above embodiment, multiplex communication using optical fiber cables 81 and 82 has been described as an example of optical communication according to the present disclosure, but the present disclosure is not limited to this. Optical communication may also be optical wireless communication between optical signal transceiver 51 and optical signal transceiver 52 shown in FIG. 1. In this case, for example, optical signal transceiver 51 may perform data error detection and correction on the optical wireless communication data (position information and error information) received from optical signal transceiver 52. Furthermore, optical communication according to the present disclosure may also be communication that does not implement multiplexing. In the above embodiment, the device control main board 85 detects an increase in data errors by comparing the number of times N that data errors that occurred within a predetermined time were corrected with thresholds (first threshold number TH1, second threshold number TH2), but the method of detecting an increase in data errors is not limited to this. For example, the device control main board 85 may compare the time interval between corrections of data errors with a threshold, and issue notification information when the time interval becomes equal to or less than a predetermined threshold.

[0082] In the above embodiment, the notification method using characters is used as the notification method for notification of notification information, but this is not limited to this. For example, the occurrence of a data error or the need to clean the optical fiber cable 82 may be notified to the user by voice. The device control main board 85 may also notify a device external to the component mounting machine 20, such as the host computer 15. The first direction in the present disclosure may also be the Y-axis direction. Furthermore, in the above embodiment, the component mounting machine 20 that mounts electronic components on the board 17 is employed as the work machine of the present disclosure, but this is not limited thereto. For example, the work machine may be a solder application device that applies solder to the board 17. In this case, a device that holds a squeegee that applies solder to the board is an example of a head of the present disclosure. Furthermore, the work machine may be a board inspection device that inspects the board after electronic components are mounted by the component mounting machine 20, solder is applied by an application device, and the solder is melted and baked in a reflow furnace. In this case, the camera head that inspects the board is an example of a head of the present disclosure. Alternatively, the work machine may be a machine tool that performs processing on an object other than a board, such as a workpiece. In this case, the head of a robot (loader) that grips the workpiece and moves in the Z-axis or X-axis direction is an example of a head of the present disclosure. [Explanation of symbols]

[0083] 17 Board (work), 20 Component mounting machine (work machine, optical communication device), 25 Mounting head (head), 27A X-axis slide mechanism (first moving device), 27B Y-axis slide mechanism (second moving device), 41 Device main body (optical communication device), 45 Fixed part board (optical communication device), 85 Device control main board (determination device), 91, 103, 113 FPGA (detection device), 81 Optical fiber cable (wired cable, second wired cable), 82 Optical fiber cable (wired cable, first wired cable), 93A, 94A, 101A, 111A Transmission side photoelectric converter (optical transmitting device), 101A Transmission side photoelectric converter (first moving device side optical transmitting device), 111A Transmission side photoelectric converter (head side optical transmitting device), 93B, 94B, 101B, 111B Receiving side photoelectric converter (optical receiving device), 51A, 52A light emitting element (optical transmitting device), 51B, 52B light receiving element (optical receiving device), 123 exchange message (alert information), 124, 128 work instruction message (alert information), 127 cleaning message (alert information), TH1 first threshold number of times, TH2 second threshold number of times.

Claims

1. an optical receiving device that performs optical communication using an optical signal; a detection device for detecting data errors in the received data received by the optical receiving device; a determination device that determines an increase in the number of times errors are detected by the detection device, and notifies notification information related to a communication abnormality based on the determination that the number of times the errors are detected has increased; Equipped with The determination device determining whether the number of detections made by the detection device within a predetermined time is equal to or greater than a threshold number of times, and if it is determined that the number of detections is equal to or greater than the threshold number of times, determining that the number of detections has increased; The optical receiving device connected to an optical transmitter via a wired cable, The determination device When the number of detections is equal to or greater than a first threshold number, an instruction to replace the wired cable is notified as the notification information, and when the number of detections is equal to or greater than a second threshold number that is less than the first threshold number, an instruction to clean the connection portion of the wired cable is notified as the notification information.

2. The received data is A plurality of data are multiplexed, and an error correction code is assigned to each of the plurality of data; the detection device that performs error correction based on the error correction code on each of the plurality of data separated from the received data; the determination device that determines an increase in the number of detections by determining the number of times an error in at least one of the plurality of data has been corrected as the number of detections; The optical communication device according to claim 1 , comprising:

3. 3. The optical communication device according to claim 2, further comprising a judgment device that notifies a device that processes data on the transmitting side for which the number of error corrections has increased among the plurality of data, of the notification information prompting the performance of maintenance.

4. An optical communication device according to any one of claims 1 to 3; a head that performs work on the workpiece; a first moving device that moves the head in a first moving direction; a second moving device that moves the head in a second moving direction different from the first moving direction; a head-side optical transmitter connected to the optical receiving device via a first wired cable and provided in the head; a first mobile device-side optical transmitting device connected to the optical receiving device via a second wired cable and provided in the first mobile device; Equipped with the detection device that detects data errors in the received data received by the optical receiving device via each of the first wired cable and the second wired cable; a determining device that determines an increase in the number of times the error detected by the detecting device is detected for each of the first wired cable and the second wired cable, and notifies the notification information; A work machine equipped with:

5. An optical communication device according to any one of claims 1 to 3; a head that performs work on the workpiece; a first moving device that moves the head in a first moving direction; a second moving device that moves the head in a second moving direction different from the first moving direction; a head-side optical transmitter connected to the optical receiving device via a first wired cable and provided in the head; a first mobile device-side optical transmitting device connected to the optical receiving device via a second wired cable and provided in the first mobile device; A communication method for a work machine comprising: a detecting step of detecting, by the detecting device, a data error in the received data received by the optical receiving device via each of the first wired cable and the second wired cable; a notification step of determining an increase in the number of times the error detected by the detection device is detected for each of the first wired cable and the second wired cable by the determination device, and notifying the notification information by the determination device; A communication method, including:

Images