JP2005051508A - Ieee 1394 network system - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To set/alter an apparatus ID of FA apparatus only if wiring information on the FA apparatus is known. <P>SOLUTION: The network system in which a controller 20 and a plurality of pieces of FA apparatus 40i are connected by an IEEE 1394 network 10 comprises an apparatus ID allotment processing part 21 where a controller edits apparatus connection related data from a topology map and allots the apparatus ID to the FA apparatus. The FA apparatus is equipped with an apparatus ID holding means 43i for holding its own apparatus ID, and the controller and the FA apparatus are provided with communication means 22 and 41i for transmitting and receiving an apparatus ID allotment request. <P>COPYRIGHT: (C)2005,JPO&NCIPI

Description

  The present invention relates to an IEEE1394 network system for setting an FA device identification code in a network system in which a controller and a plurality of FA devices are connected by an IEEE1394 network.

In a network system in which a controller and a plurality of FA devices are connected, there are technologies for setting or changing device IDs and node IDs to identify FA devices, and there are some known technologies (for example, (See Non-Patent Document 1 and Non-Patent Document 2).
The prior art will be described below with reference to FIG. In the figure, reference numeral 20b denotes a controller, which includes a device ID assignment processing unit 21b and a communication processing unit 22b. Reference numeral 60i denotes a plurality of FA devices, which include a communication unit 61i, a device ID holding register 63i for storing a set device ID, and a device ID display unit 62i. In the following, i is a natural number 1, 2, 3,..., And is a number that is sequentially assigned to a plurality of FA devices.
In such a system, when the controller 20b transmits the device ID setting request 13 according to an instruction from the system operator, the device ID holding register 63i of the FA device 60i is rewritten. As the destination address included in the device ID setting request 13, the device ID set in the FA device 60i at that time is used, and the device ID to be set is used in the data portion.

Next, the operation of the conventional network system will be described in order with reference to the flowchart of FIG.
(S20, S21) First, the controller 20b and the FA device 60i are powered on.
(S22) The system operator confirms the current device ID setting displayed on the device ID display means 62i for each FA device 60i, and assigns the device ID to be set to each.
(S23) Based on the assigned result, the device ID setting request 13 is transmitted to the FA device 60i via the communication means 22b.
(S24) A device ID setting request 13 having the destination as the current device ID is transmitted to the FA device 60i.
(S25) The device ID setting request 13 is received by the communication means 61i of the target FA device 60i,
(S26) The received device ID is written in the device ID holding register 63i of the FA device 60i and updated.
PROFIBUS Specification (No.0.032) Edition 1.0, 1998, p.704, published by PNO (PROFIBUS International) DeviceNet Specifications (Release 2.0), 1997, Volume I p.5-51 to 5-52, published by Open DeviceNet Vendor Association, Inc.

However, in the conventional technique, the currently set device ID is designated as the transmission destination address and transmitted, and rewriting of the changed device ID is requested. Therefore, the initial device ID is assigned in advance, There is a problem that communication is not possible without a local device ID setting means, and the device ID cannot be set via the network. In addition, when setting / changing, since it is impossible to specify an address unless the device ID currently set for the device to be set / changed is known, a display means such as a 7-segment LED is required. The setter has to set and change the device ID while confirming this display, and the work is complicated. In particular, when the FA device is attached to the machine, there is a problem that when the device ID is set, the visual recognition is not easy and work for disassembling the machine is required.
The present invention has been made in view of such various problems, and if the wiring information of the FA device is known, the device ID of each FA device can be obtained via the network without knowing the current device ID. The purpose is to be able to set and change.

In order to solve the above problem, the present invention provides a network system in which a controller and a plurality of FA devices are connected via an IEEE1394 network, and the controller sets identification codes for the plurality of FA devices. A device ID assignment processing unit that edits device connection relation data from a topology map managed by a bus manager and assigns device IDs of the plurality of FA devices is provided, and the plurality of FA devices hold device IDs of the FA devices. The device and the plurality of FA devices include communication means for transmitting and receiving a device ID assignment request using a node ID temporarily assigned by the IEEE1394 physical layer.
Thus, the system operator does not need to know what device ID each FA device 30i has, and does not need to know where the device is installed in the machine. A device ID assignment request 50 for assigning a device ID is transmitted to each FA device 30i based on the device connection relation data collected from the network, and each FA device sets and changes the device ID from itself based on this. Can do it.

  According to the present invention, it is possible to allow the system operator to confirm the device connection relationship at the time of starting the system, so that it is possible to assign the device ID even if the device connection relationship is unknown. In addition, since communication means are used, communication is performed using a node ID that is assigned temporarily each time the system is started, instead of a device ID set in advance, and the controller has a device ID that each FA device has in advance. Even if it is not known, there is an effect that a device ID setting request can be transmitted to each FA device, and device IDs can be assigned.

  Hereinafter, embodiments of the present invention will be described with reference to the drawings.

  FIG. 1 is a block diagram showing a configuration of a network system of the present invention in which a controller and a plurality of FA devices are connected via an IEEE1394 network. In the figure, reference numeral 24 denotes a topology map holding register “TOPOLOGY_MAP” defined by IEEE1394, which stores a topology map that is edited when the system is activated or when the network configuration is changed by the function of the IEEE1394PHY layer. Reference numerals 25 and 42i are registers for holding node IDs ("node_ID" to "phy_ID") defined by IEEE1394. When the system is started or the network configuration is changed by the function of the IEEE1394 physical layer, that is, for each BusReset. The node IDs (0 to 62) determined for each node are stored for each node. In addition to the topology map holding register 24 and the node ID holding register 25, the controller 20 includes a device ID assignment processing unit 21 and a communication unit 22. The device ID assignment processing unit 21 reads the topology map read from the topology map holding register 24. The device connection relation data 23 can be edited based on the above, and the controller 20 can edit and display the wiring status of the FA device 40i so that the controller operator can understand it. The FA device 40i includes a communication unit 41i, a node ID holding register 42i that stores an IEEE1394 node ID, and a device ID holding register 43i that stores a setting value of the own device ID. In the data included in the device ID setting request 12, the node ID is used as the destination address, and the device ID set in the data portion is used.

  Next, the controller 20 and the FA device 40i will be described. FIG. 2 is a functional block diagram showing the configuration of the controller 20, and FIG. 3 is a functional block diagram showing the configuration of the FA device 40i. The communication unit 22 includes a transmission / reception signal processing unit 29, a PHY communication control unit 30, an IEEE1394 LINK layer processing unit 31, an application layer communication control unit 32, and other communication functions that are standardly implemented by IEEE1394. The transmission / reception signal processing unit 49i, the PHY communication control unit 50i, the IEEE1394 LINK layer processing unit 51i, the application layer communication control unit 52i, and other communication functions that are standardly implemented by IEEE1394. The register access processing unit 46i is a processing block for a so-called “Transaction Layer” that performs processing such as register read and register write of the asynchronous communication function defined by IEEE1394. The device ID holding register 43i is placed in the RAM area 45i and is mapped to a register address space of CSR (“Control and Satatu Registers”) architecture defined by IEEE1394 or IEEE1212. The device ID setting request 12 is read / written by designating the destination node ID by a standard function of Asynchronous communication.

  FIG. 4 shows the structure of the device connection relation data used in the network system of the present invention. The device connection relation data has a node data block 500j for each node, 501j is a field indicating the number of communication ports installed in the node, and 502j to 517j are each communication port connected to which port of which node ID. The pointer field 518j indicates whether or not the node ID determined by the IEEE1394 PHY layer is stored, and the information up to this point is information that can be developed by processing the topology map. Reference numerals 519j to 521j are fields of additional information indicating vendor ID, product ID, and device type, which are attribute values for specifying nodes, and are collected using the IEEE1394 Asynchronou communication function. The collection method is different from that of the present invention and will not be described. Reference numeral 522j denotes a field for storing the device ID assigned by the system operator.

Next, the method of the present invention will be described step by step using the flowchart of FIG. 5 showing the processing procedure of the entire network system.
(S1, S2) First, when the controller 20 and the FA device 40i are powered on,
(S3) The IEEE1394PHY communication control units 30 and 50i of the respective communication means 22 and 41i exchange information with each other, and the bus manager defined by IEEE1394, that is, the topology map holding register 24 of the controller 20 in this embodiment, The topology map information that reflects the network connection status is edited. Also, node IDs are assigned to all nodes, and the values are stored in the node ID holding registers 25 and 42i.
(S4) Next, the device ID assignment processing unit 21 reads the latest topology map stored in the topology map holding register 24,
(S5) The device connection relation data 23 is edited based on the information.
(S6) Based on the edited device connection relation data 23, the system operator assigns a device ID to each FA device 40i. This process is a manual operation with an HMI such as a setting screen, and there are various means, but since it is a general technique, a description thereof is omitted here. The device ID allocated in this way is stored in the device ID field 522j corresponding to the FA device 40i in the device connection relation data 23.
(S7) Next, sequentially follow the node data block 500j of the device connection relation data, write the device ID value in the device ID field 522j to the node ID written in the node ID field 518j, and set the device ID. The transmission message of the request 12 is edited and delivered to the communication means 22 and transmitted to the FA device 40i having the destination node ID.
(S8) Upon receiving the device ID setting request 12, the communication means 22 edits the register write request by asynchronous communication and transmits the request message to the destination node ID.
(S9) The communication means 41i of the FA device 40i of the destination node ID that has received this passes the device ID setting request 12 to the register access processing unit 46i.
(S10) Then, the register access manual processing unit 46i writes the value of the device ID setting register 43i mapped to the CSR register.

In this way, the device connection relation data on the network can be shown to the system operator based on the topology map collected and edited when the system is started, so the system operator can attach each FA device 40i to any position of the machine. It is possible to assign a device ID from the wiring status of the device without knowing whether it is.
Further, since the communication means performs communication using a node ID that is temporarily assigned each time the system is started, instead of a device ID set in advance for communication, the controller 20 determines in advance which device each FA device 40i is. Even if the user does not know whether the user has an ID, the device ID setting request 12 can be transmitted to each FA device 40i, and the device ID can be assigned.
In the present embodiment, the system operator visually assigned the device connection relation data 23 and assigned the device ID in (S6). However, separately from this, data equivalent to the device connection relation data is edited offline beforehand. In this regard, this data can be compared with the actual device connection relation data 23 edited online, and the device ID can be assigned by the device ID assignment processing unit 21 of the controller 20 without human intervention.
Regarding the logic for editing the device connection relation data from the topology map shown in (S5) of the flowchart of FIG. 5, the connection relation of nodes is already graphically displayed by an IEEE 1394 network analyzer or the like, which is known in the IEEE 1394 standard. Since it is realizable with this technique, the description is omitted.
In this embodiment, the controller 20 also serves as an IEEE1394 bus manager for editing the topology map. However, according to the IEEE1394 standard, the bus manager itself may be another node, and another node can be a bus manager. For example, the topology map can be read from the node.

The block diagram which shows the structure of the IEEE1394 network system of this invention Block diagram of controller 20 Block diagram of FA device 30i Device connection data structure Flow chart showing operation procedure Block diagram showing the configuration of a conventional network system Flow chart showing the operation procedure of the prior art

Explanation of symbols

10 IEEE1394 network, 11 FA system network,
12, 13 Device ID setting request, 20, 20b Controller,
21, 21b Device ID assignment processing unit 22, 22b Communication means,
23 device connection data, 24 topology map holding register,
25, 42i node ID holding register, 26, 47i IEEE1394PHY layer processing unit,
27 RAM area, 28, 48i IEEE1394 application layer processing unit,
29, 49i transmission / reception signal processing unit, 30, 50i PHY communication control unit,
31, 51i IEEE1394 LINK layer processing unit, 32, 52i Application layer communication control unit,
33 Controller-specific processing section,
40i FA device (i = 1, 2,..., N),
41i, 61i communication means (i = 1, 2,..., N),
43i device ID holding register, 44i, 45i RAM area,
46 register access processing unit, 53i FA device specific processing unit,
62i Device ID display means

Claims (1)

In a network system in which a controller and a plurality of FA devices are connected via an IEEE1394 network and the controller sets identification codes for the plurality of FA devices.
The controller includes a device ID assignment processing unit that edits device connection relation data from a topology map managed by the IEEE1394 physical layer serial bus manager and assigns device IDs of the plurality of FA devices.
The plurality of FA devices comprise device ID holding means for holding the device ID of each FA device,
The IEEE 1394 network system, wherein the controller and the plurality of FA devices include communication means for transmitting and receiving a device ID assignment request using a node ID temporarily assigned by the IEEE 1394 physical layer.