[go: up one dir, main page]

WO2013121568A1 - Procédé de synchronisation de nœud, système de transmission en réseau et dispositif de nœud - Google Patents

Procédé de synchronisation de nœud, système de transmission en réseau et dispositif de nœud Download PDF

Info

Publication number
WO2013121568A1
WO2013121568A1 PCT/JP2012/053724 JP2012053724W WO2013121568A1 WO 2013121568 A1 WO2013121568 A1 WO 2013121568A1 JP 2012053724 W JP2012053724 W JP 2012053724W WO 2013121568 A1 WO2013121568 A1 WO 2013121568A1
Authority
WO
WIPO (PCT)
Prior art keywords
node
frame
slave
time
synchronization
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/JP2012/053724
Other languages
English (en)
Japanese (ja)
Inventor
幸輝 湯尾
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Fuji Electric Co Ltd
Original Assignee
Fuji Electric Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Fuji Electric Co Ltd filed Critical Fuji Electric Co Ltd
Priority to PCT/JP2012/053724 priority Critical patent/WO2013121568A1/fr
Publication of WO2013121568A1 publication Critical patent/WO2013121568A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/40—Bus networks
    • H04L12/403—Bus networks with centralised control, e.g. polling
    • H04L12/4035—Bus networks with centralised control, e.g. polling in which slots of a TDMA packet structure are assigned based on a contention resolution carried out at a master unit
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04J—MULTIPLEX COMMUNICATION
    • H04J3/00—Time-division multiplex systems
    • H04J3/02—Details
    • H04J3/06—Synchronising arrangements
    • H04J3/0635—Clock or time synchronisation in a network
    • H04J3/0638—Clock or time synchronisation among nodes; Internode synchronisation
    • H04J3/0647—Synchronisation among TDM nodes
    • H04J3/065—Synchronisation among TDM nodes using timestamps

Definitions

  • the present invention relates to a node synchronization method, a network transmission system, and a node device for realizing stabilization of a data exchange cycle of each node.
  • each device has a virtual shared memory (common memory) and transmits its own station (own node) data to all stations on the network at the update timing.
  • each received station updates its data and accesses an application, thereby realizing a data exchange system that guarantees real-time performance.
  • Patent Document 1 a method for realizing efficient broadcast communication (broadcast communication) on the network at the time of data exchange described above has been proposed (see, for example, Patent Document 1).
  • the time division multiple access method using the internal timer of each node and the internal timer correction of the slave node using the synchronization frame from the master node are used together.
  • the transmission path is configured as a network connected by a bus or a serial cable.
  • Ethernet registered trademark
  • Patent Document 1 When the technique as disclosed in Patent Document 1 is applied to a line using Ethernet as a physical layer, there are the following problems.
  • the physical layer is a cascade of buses or serial cables. Therefore, it can be assumed that the reception timing of the data transmitted by broadcast is a time difference that can be ignored at the same time or almost at each station.
  • Ethernet such as 100BASE-TX or 1000BASE-T
  • a star type is adopted as a topology
  • a configuration including a relay device such as a HUB (hub) is adopted.
  • HUB employs a relay method called store & forward when relaying frame data, and transmission to the destination node is not performed unless all the frame data is received. For this reason, the reception timing delay at each node of the broadcast transmission data varies depending on the number of HUB stages that pass through. Therefore, for example, when a high-efficiency data exchange is realized using a high-speed communication line such as 1000BASE-T, the delay as described above cannot be ignored.
  • the timer correction timing of each slave station varies, resulting in duplication (congestion) of data transmission timing in each station.
  • Congestion is fatal for an industrial network because frame data is discarded due to buffer capacity such as HUB as well as data delay.
  • the reception timing of the synchronization frame is not only delayed even if the frame is not discarded, but also delayed depending on the size and type of the congested frame. Time is indeterminate. Therefore, the conventional method has a problem that the data exchange cycle in the entire system is disturbed.
  • the present invention has been made in view of the above points, and an object thereof is to provide a node synchronization method, a network transmission system, and a node device for realizing stabilization of a data exchange cycle of each node.
  • the present invention provides a node synchronization method in which a master node having a timer and a plurality of slave nodes are connected via a communication path, and the timers of the respective nodes are synchronized.
  • the slave node After receiving the synchronization frame transmitted by the master node, the slave node initializes the timer of the slave node and transmits a reception completion frame to the master node.
  • the master node transmits by the slave node.
  • Round-trip transmission between the master node and the slave node from the difference between the time of the timer at the time of reception and the timer time at the time of transmission of the synchronization frame transmitted from the own node
  • the delay time is calculated, and the calculated round trip transmission delay time is notified to the slave node.
  • the slave node receives the round-trip transmission delay time notification frame, and sets the timer in the own node based on the round-trip transmission delay time included in the notification frame. Synchronize with.
  • a timer of a node (station) configuring a network is adjusted not to a synchronization frame reception timing but to a synchronization frame transmission timing of a master station.
  • the present invention performs synchronization matching that minimizes the influence (for example, synchronization error) due to the relay delay of a frame such as a relay device (for example, HUB) inserted into a communication path (network), for example.
  • the synchronization in the present embodiment refers to a state in which, for example, the phase (timer) of the counter operation of each node is matched, but is not limited to this.
  • the present invention can perform communication without causing data congestion on the network at the time of transmission of the synchronization frame by having a margin before transmission of the synchronization frame.
  • FIG. 1 is a diagram illustrating an example of a schematic configuration of a network transmission system according to the present embodiment.
  • the network transmission system 10 shown in FIG. 1 includes a plurality of node devices 11 (node devices 11-1 to 11-3 in the example of FIG. 1) and a HUB (hub) 12 as one or a plurality of relay devices. (HUBs 12-1 to 12-5 in the example of FIG. 1). Note that the number and types of node devices and relay devices, and connection methods are not limited to this.
  • the node device 11-1 as the node A is a master node (master station), and the node device 11-2 as the node B and the node device 11-3 as the node C are slave nodes ( Slave station).
  • the communication path of the network transmission system 10 is, for example, a star type having a relay device between the master node 11-1 and the slave node 11-2.
  • the relay apparatus uses HUB as an example, but the present invention is not limited to this, and for example, a router, a repeater, an optical converter, or the like can be used.
  • the master node and the slave node are connected via a communication path.
  • the master node and the slave node are used as, for example, a network of controllers (control devices), basically, devices used in the controller system are targets of masters or slaves.
  • the device include a controller, a PC (Personal Computer), a server, an input / output (IO) module, and a drive device (for example, an inverter and a servo).
  • the node device 11-1 and the node device 11-3 are connected to the same HUB 12-1, and the node device 11-2 passes through a 5-stage HUB (relay device).
  • the node device 11-1 and the node device 11-3 are connected.
  • FIG. 2 is a diagram illustrating an example of data transmission before node synchronization correction.
  • FIG. 2 an example of data transmission when the node device 11-2 (node B) or the connected HUB 11-2 is powered on and the node device 11-2 newly joins a communication path (network). Is shown. Note that the node device 11-1 (node A) and the node device 11-3 (node C) at this time are already synchronized.
  • each node has a cycle timer (first timer) and a send timer (second timer).
  • the synchronization frame 21 (in the example of FIG. 2, the synchronization frames 21-1 to 21-4) is transmitted according to the cycle T of the cycle timer (A) of the node device 11-1. Yes.
  • the node device 11-1 also clears the send timer 22 (send timers 22-1 to 22-3 in the example of FIG. 2) at the cycle timer clear timing. Thereafter, the node device 11-1 transmits the transmission data 23 (transmission data 23-1 to 23-3 in the example of FIG. 2) of each node at the timing of the send timer up.
  • the node device 11-2 receives the synchronization frame 21 from the node device 11-1 via the HUB 12-1. Therefore, a delay 24 occurs at the reception timing of the synchronization frame 21. At this time, since the node device 11-2 (node B) is not synchronized, the cycle T and the send timer (B) of the node device 11-2 are cleared at the reception timing of the synchronization frame 21. Done.
  • the send timer (B) operates in a state including the delay 24.
  • the node device 11-3 node C also includes a delay corresponding to one HUB, but here it is not considered because it is a little in time.
  • data 25 (data 25-1 to 25-3 in the example of FIG. 2) is transmitted at the timing of the send timer up of the node device 11-2 in the state described above.
  • the node device 11-1 and the node device 11-3 overlap with, for example, the synchronization frames 21-2 to 21-4 at the timing of receiving the data 25, and congestion occurs.
  • control can be performed so that data transmission from a participating node (for example, the node device 11-1) is not performed until synchronization is completed.
  • an example expressing congestion is shown.
  • a general Ethernet HUB employs an interface method called store & forward.
  • all the sent frames are stored in the reception buffer in the HUB, and are transmitted after performing the HUB internal processing (for example, abnormality determination, destination determination, etc.).
  • the reception buffer assuming that the destination port is in use has a sufficient size. If there is some congestion, communication is performed without data loss. be able to.
  • the reception timing of the synchronization frame is an important element for synchronization, and delayed reception of the synchronization frame is fatal.
  • frame priority control can be performed by QoS (Quality of Service) or the like.
  • QoS Quality of Service
  • the synchronization frame 21 is also delayed in reception by the node device 11-3 regardless of the priority setting. The synchronization of each node on the system will be lost.
  • HUB used in Ethernet does not have an IP address (Internet Protocol Address) and is not normally recognized by the system configuration node.
  • IP address Internet Protocol Address
  • a HUB can be constructed in a star topology, it is possible to construct a system via a number of stages of HUB between system configuration nodes, and the delay time due to the HUB varies depending on the manufacturer, model, etc. There are many cases. Therefore, in practice, it has been difficult to set a delay time from the master node to each slave node until the system is configured.
  • the transmission delay time between the master node and the joining slave node is determined, and this is set as the joining slave node, so that the master timer and the joining slave timer are synchronized, and then joined to the system. Can be made.
  • FIG. 3 is a diagram showing an example of a data exchange procedure for correcting the slave node time.
  • TC bands 31 and 37 indicate the transmission band (timer clear) of the synchronization frame
  • TS bands 32 and 38 indicate the data transmission band (timer send), and each is transmitted at a predetermined cycle. Is done.
  • nodes A, B, and C in the example of FIG. 3 correspond to the node devices 11-1, 11-2, and 11-3, respectively.
  • the squares shown in FIG. 3 indicate frames
  • the squares on the lines for the nodes A to C indicate transmission frames
  • the squares below the lines indicate reception frames.
  • the TC frame indicates a synchronization frame
  • the TS * (* indicates any of A to C) frames indicates node data from any of the nodes A to C.
  • TSA indicates that the node data is from node A (node device 11-1).
  • a req frame 33 indicates subscription request data
  • an OK frame 34 indicates subscription permission data
  • a dly frame 35 indicates a TC reception delay
  • a SET frame 36 indicates a delay time setting (specifically, Indicates round trip transmission delay time setting).
  • the node B (node device 11-2) that is the joining node transmits the subscription request req frame 33 in the TS band 38 to the node A (node device 11-1) that is the master node.
  • the node A determines whether or not the participation requesting node can participate, and if the participation is permitted, the node A issues an OK frame 34 for permission to join following the synchronization frame TC.
  • the OK frame 34 is expressed as a separate frame.
  • the present invention is not limited to this.
  • the OK frame 34 may be configured as data on the synchronization frame TC.
  • the node B (node device 11-2) as a slave node that has received the OK frame 34 that has been permitted to join from the node A transmits a dly frame 35 that is a TC reception delay frame to the master at the next synchronization frame TC reception timing. To do. This frame is transmitted at the timing of receiving the synchronization frame TC.
  • the node device B which is a joining node, has already received the synchronization frame TC several times, and has cleared (initialized) the internal timer at that timing. For this reason, the node B, which is a joining node, may transmit at the clear timing of the cycle timer of the own node (own station) in the same manner as the synchronization frame TC transmission of the master.
  • the dly frame 35 which is a TC reception delay frame, is unicast (one-to-one) communication to the master node, and thus overlaps the reception of the synchronization frame TC to the slave node that has already joined the network transmission system. There is nothing.
  • the node A that has received the dly frame 35 records the value of the cycle timer at that timing.
  • the node A sets the transmission time obtained above in the SET frame 36 for setting the delay time for the joining slave node (node B), and uses this SET frame 36 as a round trip transmission delay time notification frame.
  • the Node B that has received the SET frame 36 subtracts the round-trip transmission delay time set in the SET frame 36 from its own cycle timer (accelerates timer up) (for example, time 39 shown in FIG. 3),
  • the cycle timer is synchronized with the timer of the node A that is the master node.
  • the cycle timer of the node B is delayed from the timer of the node A, and thus the synchronization is performed by the above-described subtraction process.
  • the present invention is not limited to this.
  • the round-trip transmission delay time set in the SET frame 36 is added to the own cycle timer so that the own cycle timer is set at the master node. It can be synchronized with the timer of a certain node A.
  • the delay time setting SET frame 36 may also be data of the synchronization frame TC, similar to the subscription-permitted OK frame 34. In this way, the node that has finished adjusting the cycle timer is allowed to transmit data in the TS band, assuming that it is permitted to join the system.
  • the req frame 33 is used as the subscription request data and the OK frame 34 is used as the subscription permission data frame for the node subscription.
  • the present invention is not limited to this.
  • the synchronization in this embodiment can be performed even in a procedure in which station numbers are sequentially designated in the framing frame TC and a station scheduled to join among the designated stations (nodes) responds with the dly frame 35.
  • a node far in terms of transmission time is, for example, a node having a predetermined number or more of the number of HUB stages passed through.
  • a margin time can be provided between the timing of the final data transmission and the transmission timing of the synchronization frame TC.
  • the conventional method depends on the system configuration and is not uniquely determined by the number of nodes or the like.
  • the master node (node device 11-1) in the present embodiment performs the above-described joining process for all slave nodes of the network transmission system 10, the transmission delay time between the master and each slave is maintained. Yes. Therefore, although the master node is not necessarily at the center of the configuration, for example, a predetermined value based on the maximum transmission delay time (round-trip transmission delay time) for all slave nodes can be set as the margin time.
  • the margin time in the present embodiment is a time during which data transmission or the like provided for avoiding congestion, collision, etc. of data flowing through the network is not performed. In the present embodiment, it is possible to prevent the synchronization frame TC from being congested by providing a margin time as described above.
  • the margin time may be longer than the maximum round trip transmission delay time, for example, preferably about 2 to 3 times.
  • FIG. 4 is a diagram showing an example of data transmission after node synchronization correction.
  • the margin time 41 is set as described above.
  • data transmission between nodes can be completed by setting a margin time 41 as shown in FIG. That is, in the present embodiment, a value that allows for the margin time 41 is set for the cycle T of the cycle timer.
  • the slave node when synchronization is performed between the master node and the slave node, the slave node sequentially responds simultaneously with a preset send timer up after the master node transmits a synchronization frame.
  • the margin time 41 means, for example, a time until the next synchronization frame transmission of the master node with respect to the transmission timing of the last slave node. That is, the margin time 41 means the time from the timing at which all the slave nodes have transmitted responses to the synchronization frame transmission of the master node to the timing at which the next synchronization frame is transmitted.
  • FIG. 5 is a diagram illustrating an example of a system configuration for explaining how to determine the allowance time.
  • the margin time is set in accordance with the number of data relay apparatuses in the system configuration. Specifically, for example, the data arrival time of the route having the largest number of data relay apparatuses among the communication between nodes can be used, but the present invention is not limited to this.
  • the master node is not determined in advance, but is determined by, for example, a master determination method in node synchronization processing of the present embodiment described later. Therefore, all of the nodes A to H can be master nodes unless the node device 51 has a special setting (such as a slave mode).
  • the system can be operated without problems such as data congestion and collision by setting a margin time based on, for example, the data arrival time from the node A to the node H, the maximum delay time, and the like.
  • the maximum delay time detected is the number of relay stages from the node D or node E to the node A or node H (four stages in the example of FIG. 5). It turns out that. Further, the detected maximum delay time is minimum when the central node of the system configuration becomes the master. In the example of the network transmission system 50 in FIG. 5, the maximum delay time is minimum when the node D or the node E is the master node. Become. In other words, if the master node is at the center of the system configuration, the maximum delay time in that configuration is between the slaves arranged opposite to each other across the master node (in the example of FIG. 5, node A, node H).
  • the margin time when setting the margin time, it is possible to include the delay time between all nodes by setting about 2 to 3 times the maximum delay time from the master node as a reference. It becomes possible. Note that the margin time increases as the master node deviates from the center of the system configuration.
  • the “maximum cascade stage number ⁇ 2 times” of the relay device can be uniquely determined as a margin time.
  • the maximum number of stages of the relay device of the system can be set in advance by the user, and abnormal termination or the like can be performed when the number of stages is exceeded.
  • a node exceeding a preset margin time is prevented from joining the system.
  • the master node cannot receive within the TC band when receiving a subscription request, it is possible to control the subscription to the system by determining that a node exceeding the margin time has been inserted.
  • the master node refuses to join a node that exceeds the above-described margin time, and the slave node notifies the user that there is an abnormality in joining.
  • processing such as setting no delay time or responding abnormally is performed.
  • the resetting of synchronization means, for example, recalculation or resetting of delay when there is a configuration change.
  • the delay time is set, for example, when the node system is joined or when the master is disconnected.
  • the delay time may be measured a plurality of times (several tens of times) when the system joins or the master leaves, and the average value may be set as the delay time between nodes.
  • the state may change due to aging of nodes and devices, ambient environment (for example, temperature, noise), and the like.
  • delay time measurement is performed for all nodes participating in the network transmission system, for example, at a constant cycle (for example, once every several seconds), and the delay time is set again.
  • the synchronization is basically adjusted on the slave side. For example, in the present embodiment, a delay time is distributed from the master node to each slave node, and the timer is adjusted correspondingly. While the slave node participating in the system can synchronize with the master node, the synchronization frame TC transmitted from the master node is received with a delay of the delay time.
  • the reception timing of the synchronization frame TC is measured by the timer of the own node (own station), and the time is compared with a preset delay time at the time of synchronization with the master node. It is possible to detect whether or not synchronization has occurred.
  • the present embodiment for example, when the TC reception timing is confirmed a plurality of times, and reception of TC is delayed from a set delay time in advance by a predetermined number (for example, 5 times) in advance, etc. Based on the set condition, the delay or advance of its own timer is detected. Further, in the present embodiment, based on the amount of delay or advance of own timer obtained at the time of detection described above, a correction for synchronizing the timer in the own node with the timer of the master node so as to eliminate the above-described synchronization deviation. I do.
  • FIG. 6 is a flowchart illustrating an example of master determination in node synchronization processing. 6 illustrates a procedure in which one of a plurality of node devices connected to the network is determined and operated as a master node, but is not limited thereto.
  • the node synchronization process first initializes each resource of the node device (S01), and monitors the initial line when it is normally initialized (S02).
  • monitoring of the initial line means monitoring of the line during initial (initialization), for example, and is distinguished from monitoring during operation.
  • frames such as TC (synchronization frame transmission band (timer clear)), TS (data transmission band (timer send)), and ITC (TC frame used only during system initialization) are included. There is a possibility of flowing.
  • the ITC does not flow during operation, unlike during initial operation.
  • a line status check is performed. The check cycle can be checked at a timing such as “maximum cycle time ⁇ 3 times”, but is not limited to this, and may be checked at another timing.
  • the node synchronization process determines whether the monitoring timer is up (UP) without receiving the above-described TS, ITC, or TC as a result of monitoring (S03).
  • an initial temporary master is determined (S04).
  • the initial temporary master monitors, for example, a station number (node number), a refresh cycle delay, TC reception of other node devices (other stations), and the like.
  • the initial temporary master controls ITC transmission.
  • the master right is acquired and the master operation is performed (S06).
  • the master operation in the present embodiment is, for example, at least one of the above-described TS reception monitoring, joining node management, transmission delay time calculation, message transmission control, delay time setting transmission for each slave node, and the like.
  • the present invention is not limited to this.
  • the node synchronization process if the above-described condition of S05 is not satisfied (NO in S05), it is determined whether another node apparatus TC is received or an ITC having a higher priority than the own node is received. Judgment is made (S07). In the node synchronization process, when another node apparatus TC is received or an ITC having a higher priority than the own node is received (YES in S07), a process for slave operation described later is performed (S08).
  • the process described above is repeated when there is a mild abnormality that can be easily recovered, such as a process delay in memory read / write or a minor communication failure. Done.
  • a process of notifying error information may be included.
  • FIG. 7 is a flowchart showing an example of slave determination in the node synchronization processing.
  • a procedure is shown in which one of a plurality of node devices connected to the network is determined and operated as a slave node, but is not limited thereto.
  • the node synchronization process first initializes each resource of the node device (S11), and monitors the initial line when it is normally initialized (S12). In the process of S12, for example, the line status is checked.
  • the check cycle can be checked at a timing such as “maximum cycle time ⁇ 3 times”, but is not limited thereto.
  • the node synchronization processing determines whether there is reception of TS, ITC, or TC as a result of monitoring (S13).
  • S13 the condition of S13 described above is satisfied (YES in S13)
  • S14 an initial master is determined (S14).
  • the initial master determination in the process of S14 includes, for example, “a state in which there is a master (or master candidate) other than the own node and the own node may become a slave”.
  • the own node when the own node is in the line monitoring state after initialization and a frame such as TC has already flowed, the own node may be a slave.
  • monitoring is performed for a predetermined period (for example, three periods), and if that is all right, the node that transmits TC (or ITC) is recognized as a master, and the own node tries to become a slave. To do.
  • the initial master monitors for example, TC, TS, etc., receives ITC or TC, and checks the master station number. This monitoring is performed with reference to, for example, three laps, but is not limited to this.
  • a TC or ITC of the same node it is determined whether or not a TC or ITC of the same node has been received for a predetermined number of consecutive times (for example, three consecutive) (S15), and a TC or ITC of the same node has been received for a predetermined number of consecutive times If this is the case (YES in S15), a slave operation confirmation wait state is entered (S16). At this time, in this embodiment, the network cannot be joined. In the process of S16, for example, a TS transmission delay time is set and a delay time backup for the connection node is performed.
  • the node synchronization processing determines whether or not the master is permitted to join and the delay time setting is completed (S17). If the master is permitted to join and the delay time setting is completed (YES in S17). Then, slave operation is performed (S18).
  • the node synchronization processing is terminated.
  • the process of S15 described above when the condition of S15 is not satisfied within a predetermined time, the own node may try to become the master. In this case, after the slave operation is confirmed, if the master is not allowed to join, an error notification may be given due to network setting abnormality or the like.
  • the node synchronization process when the condition of S17 is not satisfied within the predetermined time in the process of S17 (NO in S17), the node synchronization process is terminated.
  • the process described above is repeated when there is a mild abnormality that can be easily recovered, such as a process delay in memory read / write or a minor communication failure. Done.
  • a process of notifying error information may be included.
  • FIG. 8 is a flowchart showing an example of switching from the slave to the master in the node synchronization processing.
  • S21 node synchronization processing
  • the node synchronization processing makes an inquiry about master right transfer on the network (S23). Specifically, the TS with the inquiry bit turned ON is transmitted (S24).
  • the node synchronization processing is performed for a predetermined time. Wait for operation master switching.
  • the node synchronization processing is set as an operational temporary master when it is detected that the master has been dropped in the operation master switching waiting state in the processing of S22 described above (S25). At this time, the node synchronization processing performs ITC transmission at a predetermined timing. Further, the node synchronization processing waits for switching of the operation master when ITC or TC having a higher priority than the own node is received.
  • the node synchronization process it is determined whether or not the ITC has been transmitted continuously for a predetermined number of times (for example, three times) within a predetermined time (S26), and when the predetermined number has been transmitted continuously (YES in S26).
  • the master operation is switched (S27). Further, in the node synchronization process, when a predetermined number of ITCs cannot be transmitted continuously within a predetermined time (NO in S26), the process is terminated and the operation master is waited for switching.
  • the participating nodes of the network in operation always monitor the frame
  • the master node monitors the TC frame from the master having higher priority than itself
  • the slave node monitors the drop of the master node.
  • the slave node that detects the drop of the master node adds a master transfer inquiry to the TS frame, and performs a master transfer process.
  • the master switching state is entered, and the normal operation is entered after the master is determined.
  • the priority described above is determined by, for example, the type of node (for example, module shape, PCI-e (Peripheral Components Interconnect-express) board), the network station number (node number) in ascending order, and the like.
  • FIG. 9 is a diagram illustrating an example of a functional configuration of the node device according to the present embodiment.
  • the node device 60 shown in FIG. 9 includes a communication interface (IF) means 61, a load command means 62, a storage management means 63, a system management means 64, a switch (SW) management means 65, and a time management means (timer). ) 66, application control means 67, network control means 68, and input / output (IO) control means 69.
  • IF communication interface
  • load command means 62 includes a storage management means 63, a system management means 64, a switch (SW) management means 65, and a time management means (timer).
  • SW switch
  • timer time management means
  • the node device 60 shown in FIG. 9 has a common configuration for both the master node and the slave node. Also, the node device 60 shown in FIG. 9 has a configuration including both functions of the controller and the network.
  • the processing of the controller is performed, for example, with a constant cycle as a control unit (scan cycle).
  • a control LSI Large Scale Integration
  • an interrupt with a constant cycle from a control LSI (Large Scale Integration) (for example, a master LSI) is performed.
  • LSI Large Scale Integration
  • the present invention is not limited to this. For example, processing may be performed based on a built-in timer of a microcomputer.
  • the reception interrupt of the inter-controller network is used, the delay time is calculated from the difference between the TC reception timing and the scan cycle interrupt from the master LSI, and correction is performed.
  • the controller can operate by downloading a support program (loader) on the PC, a combination program, and an operation definition.
  • the node device 60 as a normal controller and a loader is connected to an external device or the like by a communication IF means 61 via, for example, a serial cable or a USB (Universal Serial Bus).
  • a communication IF means 61 via, for example, a serial cable or a USB (Universal Serial Bus).
  • the transmitted / received communication is output from the communication IF unit 61 to the loader command unit 62.
  • loader command means 62 exchanges corresponding processing by a protocol called a loader command.
  • loader commands include commands such as application start / stop (system management control), application data monitoring and modification (application management control), program, definition download (storage management control), etc. Acts on function.
  • the storage management means 63 is rewritable and stores various information in a flash memory such as an SD memory card, which is a non-volatile semiconductor memory that does not lose data even when the power is turned off. Management such as reading.
  • the storage management unit 63 outputs the acquired information to at least one of the system management unit 64, the application control unit 67, and the network control unit 68 as necessary.
  • the system management unit 64 executes preset processing (for example, execution cycle, memory allocation, IO configuration management, initialization of each resource, etc.), status monitoring (failure diagnosis) of the node device 60, IO data exchange processing Etc.
  • the system management means 64 performs processing as described above based on various data obtained from the storage management means 63, loader command means 62, SW monitoring means 65, time management means 66, application control means 67, and IO control means 69. Execute.
  • the system management means 64 receives the synchronization frame transmitted after the master node timer is up when the network control means 68 is set as a slave node. Further, the system management means 64 initializes the above-described timer for the TC and TS transmission periods in correspondence with the received synchronization frame, and transmits the reception completion frame from the communication IF means 61 to the master node after the initialization.
  • the system management unit 64 receives the transmission delay time notification frame from the master node when the network control unit 68 sets the slave node, and based on the received transmission delay time, Adjust. Specifically, when the timer in its own node is delayed from the transmission delay time of the master node, the system management means 64, for example, uses the received transmission delay time (specifically, the round-trip transmission delay time) as its own. By subtracting from the current time of the timer of the node, the node device 60 can synchronize the current time of the local node timer with the master timer.
  • the received transmission delay time specifically, the round-trip transmission delay time
  • the system management means 64 adds the above-described transmission delay time to the current time of the own node timer, so that the master timer Synchronize with.
  • system management unit 64 receives the synchronization frame reception completion frame from the slave node when the network control unit 68 sets the master node. Further, the system management unit 64 records the current time obtained from the RTC in the above-described timer of the TC and TS transmission cycle in the time management unit 66 based on the received synchronization frame reception completion frame.
  • the system management means 64 determines the round-trip transmission delay between the master node and the slave node from the difference between the current time of the timer when receiving the reception completion frame and the timer time when transmitting the synchronization frame transmitted from the own node. Calculate time. Further, the system management means 64 notifies the calculated round trip transmission delay time to the slave node.
  • the system management means 64 sets a margin time during which data transmission or the like is not performed at the master node with reference to the maximum transmission delay time between a plurality of slave nodes. Further, the system management means 64 uses the interval from the slave node data transmission to the master node synchronization frame transmission as a margin time. As a result, in the present embodiment, it is possible to prevent communication congestion from occurring during transmission of the synchronization frame.
  • system management means 64 performs various settings, control, monitoring, and the like.
  • the settings in the system management means 64 are basically read from the storage management means 63.
  • the setting file writing for storage management is stored from the outside via the communication IF means 61 and the loader command means 62, for example.
  • the setting contents include, for example, system settings (for example, IO module configuration, control cycle settings, etc.), module settings (for example, module initialization operation settings, etc.), but are not limited thereto. is not.
  • system settings for example, IO module configuration, control cycle settings, etc.
  • module settings for example, module initialization operation settings, etc.
  • the system settings described above are settings for the entire system. For this reason, settings for individual modules are transmitted as messages through network control or IO control.
  • control in the system management means 64 performs operation control such as starting and stopping of applications, and other resets (initialization), for example. These operation controls are instructed from the loader command means 62 or the SW monitoring means 65, for example. Moreover, as control in the system management means 64, in addition to the content described above, for example, control of exchange processing of IO data during operation, network data, and the like is performed.
  • monitoring in the system management means 64 monitors module hardware failures, network, and system-wide abnormality information collected by network control at regular intervals.
  • monitoring by the system management means 64 includes system shutdown, notification to the user (for example, notification using voice, light, etc.), notification to a predetermined computer (for example, management terminal) using a loader command (for example, an error message or the like is performed.
  • the SW monitoring unit 65 monitors an external key switch (Key SW) (for example, power ON / OFF, etc.), a station number SW, and the like, and sends each SW signal obtained by, for example, a user operation to the system management unit 64. Output.
  • Key SW for example, power ON / OFF, etc.
  • the time management means 66 acquires time information that serves as a reference for synchronization. Specifically, the date information acquisition unit 66 acquires a signal from, for example, an RTC (Real Time Clock), and manages time and the like by a calendar function or the like.
  • the time management means 66 may have the cycle timer (first timer) and the send timer (second timer) described above. Further, the time management unit 66 may manage the above-described margin time obtained from the system management unit 64. The time management unit 66 outputs the acquired time information to the system management unit 64.
  • the application control means 67 stores various application programs for controlling applications such as the above-described various node synchronization processes implemented in the present embodiment. Control signals from the loader command means 62 and the system management means 64 are stored. Various application processes are executed based on the above.
  • the network control means 68 controls the entire network for sending and receiving messages and control data with other nodes, for example. Further, the network control unit 68 performs control for the own node to set to either the master node or the slave node based on the connection state with other node devices as described above.
  • the network control means 68 performs control so as to reject the subscription when the slave node requesting to join is a slave node exceeding the margin time when the own node is the master node. Further, the network control unit 68 determines a temporary master from a plurality of node devices, operates the temporary master as a master node when the ITC transmission is a predetermined number or more and a slave join notification is received from another node device. Then, other node devices are operated as slave nodes.
  • the network control unit 68 executes predetermined processing when a node device is newly joined to a plurality of node devices connected to the communication path (communication network) or when the master node is dropped from the communication path. Re-execute the process to synchronize. Further, when the node is a slave node, the network control unit 68 measures the TC reception timing with the timer of the node, and compares the measured time with a preset delay time, thereby It is detected whether or not synchronization has occurred, and correction is performed so that the above-described synchronization is eliminated in accordance with the delay or advance of the timer obtained from the detection result.
  • the IO control means 69 controls the overall input / output of messages and control data with the connected external device.
  • the network function is described on the same functional block.
  • the present invention is not limited to this.
  • the IO control unit 69 is divided into separate modules. It can be implemented to exchange messages and control data between modules.
  • FIG. 10 is a diagram illustrating an example of a hardware configuration of the node device.
  • the node device 70 includes a basic system unit 71, an application control unit 72, and a network control unit 73.
  • the basic system unit 71 corresponds to the system management unit 64 described above
  • the application control unit 72 corresponds to the application control unit 67
  • the network control unit 73 corresponds to the network control unit 68.
  • the basic system unit 71 includes system control means 81, SDRAM (Synchronous DRAM) 82, LAN (Local Area Network) 83, RTC 84, SD memory (Secure Digital memory) 85, and flash memory (Flash Memory) 86. And an internal bus management LSI 87, an SRAM (Static Random Access Memory) 88, and a master LSI 89.
  • the application control unit 72 includes an application network unit 91, a master LSI 92, an SRAM 93, a flash memory 94, and a DDR-SDRAM (Double-Data-Rate Synchronous Random Access Memory) 95. Yes.
  • the SX bus (high-speed bus) and the E-SX bus (super high-speed bus) are predetermined input / output (IO) control buses.
  • the system control 81 performs control in the basic system of the node device 70.
  • the system control 81 controls transmission / reception of various data from an external device connected via the LAN 83, controls the operation of the entire system based on time information obtained from the RTC 84, and an application (program) such as the SD memory 85. Is read and executed.
  • the system control unit 81 may input / output various data from an external device via a USB or the like.
  • Master LSIs 89 and 92 are control LSIs for the IO control bus.
  • DDR-SDRAM 95, SDRAM 82, and SRAMs 88 and 93 are volatile memories
  • flash memories 86 and 94 are writable nonvolatile memories.
  • the internal bus management LSI 87 is an LSI (FPGA (Field-Programmable Gate Array) for connecting microcomputers.
  • the internal bus management LSI 87 is connected to, for example, a shared memory (for example, a shared memory included in the master LSI 92 shown in FIG. 10).
  • the internal bus management LSI 87 controls access to the SRAM of another CPU (Central Processing Unit) connected by the SX bus.
  • CPU module such as PLC (Programmable Logic Controller), etc. It means a module that performs application computations, and the internal bus management LSI 87 handles interrupts between microcomputers. Do.
  • the own node (own station) area corresponds to the processor bus space in FIG.
  • the above-described processor means a module that executes, for example, a PLC application.
  • the application network means 91 has a structure that mainly uses, for example, a dual-core microcomputer and processes each application and network.
  • the hardware configuration described above is not limited to this in the present invention.
  • one microcomputer may be used.
  • each function as shown in FIG. 9 can be realized by using the hardware configuration shown in FIG. Specifically, the node device 60 in this embodiment is set to either a master node or a slave node based on the connection state with other node devices. Further, when the node device 60 is set as a slave node, the node device 60 receives a synchronization frame transmitted by the master node, thereby initializing a timer of the slave node and transmitting a reception completion frame to the master node.
  • the node device 60 when the node device 60 is set as the master node, the node device 60 receives the reception completion frame transmitted by the slave node, and the timer at the time of transmission and the timer at the time of transmission of the synchronization frame transmitted from the own node.
  • the round trip transmission delay time between the master node and the slave node is calculated from the difference with the time.
  • the node device 60 transmits a round trip transmission delay time notification frame for notifying the slave node of the calculated round trip transmission delay time, causes the slave node to receive the round trip transmission delay time notification frame, and is included in the notification frame. Based on the round-trip transmission delay time, the timer in the own node is synchronized with the timer of the master node.
  • a program for causing a computer to function as each unit included in the node device 60 described above is generated, and the generated program is installed in a computer such as a PC.
  • a program for causing a computer to function as each unit included in the node device 60 described above is generated, and the generated program is installed in a computer such as a PC.
  • stabilization of the data exchange cycle of each node can be realized.
  • a timer of each node is synchronized with a shared memory network using a time division multiplex transmission method, thereby improving transmission efficiency and data exchange.
  • Efficiency and stabilization of the data exchange cycle can be realized.
  • this embodiment can be applied to a synchronization method when performing a series of operations in a large-scale facility such as a steel plant using a plurality of operations. It can be widely applied as a synchronization method.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Small-Scale Networks (AREA)
  • Synchronisation In Digital Transmission Systems (AREA)
PCT/JP2012/053724 2012-02-16 2012-02-16 Procédé de synchronisation de nœud, système de transmission en réseau et dispositif de nœud Ceased WO2013121568A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/JP2012/053724 WO2013121568A1 (fr) 2012-02-16 2012-02-16 Procédé de synchronisation de nœud, système de transmission en réseau et dispositif de nœud

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/JP2012/053724 WO2013121568A1 (fr) 2012-02-16 2012-02-16 Procédé de synchronisation de nœud, système de transmission en réseau et dispositif de nœud

Publications (1)

Publication Number Publication Date
WO2013121568A1 true WO2013121568A1 (fr) 2013-08-22

Family

ID=48983725

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2012/053724 Ceased WO2013121568A1 (fr) 2012-02-16 2012-02-16 Procédé de synchronisation de nœud, système de transmission en réseau et dispositif de nœud

Country Status (1)

Country Link
WO (1) WO2013121568A1 (fr)

Cited By (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2015154212A (ja) * 2014-02-13 2015-08-24 富士電機株式会社 ネットワークシステム、そのパラメータ決定装置
JP2016005247A (ja) * 2014-06-19 2016-01-12 富士電機株式会社 ネットワーク伝送システム、そのマスタノード、スレーブノード
JP2016009944A (ja) * 2014-06-23 2016-01-18 富士電機株式会社 ネットワーク通信システム、そのマスタノード
JP2016012815A (ja) * 2014-06-27 2016-01-21 富士電機株式会社 ネットワーク通信システム、そのマスタノード
JP2016170065A (ja) * 2015-03-13 2016-09-23 日本電気株式会社 信号処理制御装置、信号処理制御方法、２次監視レーダーシステム、並びにコンピュータ・プログラム
KR20160125942A (ko) 2014-02-27 2016-11-01 후지 덴키 가부시키가이샤 프로그래머블 컨트롤러 시스템, 그 컨트롤러
KR20180099777A (ko) 2016-08-05 2018-09-05 후지 덴키 가부시키가이샤 제어 네트워크 시스템, 그 노드 장치
CN112596423A (zh) * 2020-11-27 2021-04-02 斐思光电科技武汉有限公司 基于空间光调制器的集群控制方法及一种空间光调制器
CN114245453A (zh) * 2021-12-27 2022-03-25 东莞市阿尔法电子科技有限公司 时间同步方法、装置、tws耳机、计算机设备及存储介质
CN117042079A (zh) * 2023-10-09 2023-11-10 深圳鹏龙通科技有限公司 数据传输方法、装置、设备和计算机可读存储介质

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2009290626A (ja) * 2008-05-30 2009-12-10 Kddi Corp 光伝送システム及び時刻基準パルス同期方法
JP2012009977A (ja) * 2010-06-23 2012-01-12 Panasonic Corp ネットワークシステム

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2009290626A (ja) * 2008-05-30 2009-12-10 Kddi Corp 光伝送システム及び時刻基準パルス同期方法
JP2012009977A (ja) * 2010-06-23 2012-01-12 Panasonic Corp ネットワークシステム

Cited By (14)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2015154212A (ja) * 2014-02-13 2015-08-24 富士電機株式会社 ネットワークシステム、そのパラメータ決定装置
KR20160125942A (ko) 2014-02-27 2016-11-01 후지 덴키 가부시키가이샤 프로그래머블 컨트롤러 시스템, 그 컨트롤러
JP2016005247A (ja) * 2014-06-19 2016-01-12 富士電機株式会社 ネットワーク伝送システム、そのマスタノード、スレーブノード
JP2016009944A (ja) * 2014-06-23 2016-01-18 富士電機株式会社 ネットワーク通信システム、そのマスタノード
JP2016012815A (ja) * 2014-06-27 2016-01-21 富士電機株式会社 ネットワーク通信システム、そのマスタノード
JP2016170065A (ja) * 2015-03-13 2016-09-23 日本電気株式会社 信号処理制御装置、信号処理制御方法、２次監視レーダーシステム、並びにコンピュータ・プログラム
KR20180099777A (ko) 2016-08-05 2018-09-05 후지 덴키 가부시키가이샤 제어 네트워크 시스템, 그 노드 장치
JPWO2018025491A1 (ja) * 2016-08-05 2018-11-22 富士電機株式会社 制御ネットワークシステム、そのノード装置
CN112596423A (zh) * 2020-11-27 2021-04-02 斐思光电科技武汉有限公司 基于空间光调制器的集群控制方法及一种空间光调制器
CN112596423B (zh) * 2020-11-27 2022-02-18 斐思光电科技武汉有限公司 基于空间光调制器的集群控制方法及一种空间光调制器
CN114245453A (zh) * 2021-12-27 2022-03-25 东莞市阿尔法电子科技有限公司 时间同步方法、装置、tws耳机、计算机设备及存储介质
CN114245453B (zh) * 2021-12-27 2023-10-13 东莞市阿尔法电子科技有限公司 时间同步方法、装置、tws耳机、计算机设备及存储介质
CN117042079A (zh) * 2023-10-09 2023-11-10 深圳鹏龙通科技有限公司 数据传输方法、装置、设备和计算机可读存储介质
CN117042079B (zh) * 2023-10-09 2023-12-08 深圳鹏龙通科技有限公司 数据传输方法、装置、设备和计算机可读存储介质

Similar Documents

Publication Publication Date Title
WO2013121568A1 (fr) Procédé de synchronisation de nœud, système de transmission en réseau et dispositif de nœud
US10715411B1 (en) Altering networking switch priority responsive to compute node fitness
US10868754B2 (en) High availability input/output management nodes
CN106685735B (zh) Epa片上系统、epa通信系统及通信方法
JP6265058B2 (ja) ネットワーク伝送システム、そのマスタノード、スレーブノード
CN109040184B (zh) 一种主节点的选举方法及服务器
CN102984042A (zh) 一种实现总线通信的确定性调度方法及系统
JP4884557B2 (ja) データ通信システムおよびデータ通信装置
JP4241343B2 (ja) 送信タイミング決定方法、バス使用権の調停方法、ネットワークシステム、プログラム
CN105450717A (zh) 集群脑裂处理方法和装置
Du et al. Software-defined networking for real-time ethernet
CN107508694A (zh) 一种集群内的节点管理方法及节点设备
FR3025617A1 (fr) Architecture bi-voies
US11853175B2 (en) Cluster system and restoration method that performs failover control
KR101358995B1 (ko) 고가용성 관리 방법 및 시스템
US20220137604A1 (en) Coordination Device and Method for Providing Control Applications via a Communication Network for Transmitting Time-Critical Data
JP6745106B2 (ja) ゲートウェイ装置およびセンサネットワークシステム
JP6554405B2 (ja) リングネットワークシステム、及び、ネットワークノード
US11012301B2 (en) Notification and transfer of link aggregation group control in anticipation of a primary node reboot
JP5711420B2 (ja) イーサネットノードの検出フレームタイムアウト時間の設定方法及びシステム
US20160164771A1 (en) Partner discovery in control clusters using shared vlan
WO2023007209A1 (fr) Calcul distribué tolérant aux défaillances pour systèmes de véhicules
US10122588B2 (en) Ring network uplink designation
JP2015207239A (ja) 制御システム、制御装置およびプログラム
JP2016099634A (ja) 制御システム、中継装置、および制御装置

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 12868645

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 12868645

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: JP