EP0444535B1 - Programmierbare Steuereinrichtung mit automatischer Steuerung des Verriegelungsprozesses - Google Patents

Programmierbare Steuereinrichtung mit automatischer Steuerung des Verriegelungsprozesses Download PDF

Info

Publication number
EP0444535B1
EP0444535B1 EP91102560A EP91102560A EP0444535B1 EP 0444535 B1 EP0444535 B1 EP 0444535B1 EP 91102560 A EP91102560 A EP 91102560A EP 91102560 A EP91102560 A EP 91102560A EP 0444535 B1 EP0444535 B1 EP 0444535B1
Authority
EP
European Patent Office
Prior art keywords
communication
memory
flag
complete flag
operation complete
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.)
Expired - Lifetime
Application number
EP91102560A
Other languages
English (en)
French (fr)
Other versions
EP0444535A3 (en
EP0444535A2 (de
Inventor
Hideaki C/O Mitsubishi Denki K.K. Morita
Teruyo C/O Mitsubishi Denki K.K. Yamaguchi
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.)
Mitsubishi Electric Corp
Original Assignee
Mitsubishi Electric Corp
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 Mitsubishi Electric Corp filed Critical Mitsubishi Electric Corp
Publication of EP0444535A2 publication Critical patent/EP0444535A2/de
Publication of EP0444535A3 publication Critical patent/EP0444535A3/en
Application granted granted Critical
Publication of EP0444535B1 publication Critical patent/EP0444535B1/de
Anticipated expiration legal-status Critical
Expired - Lifetime legal-status Critical Current

Links

Images

Classifications

    • G—PHYSICS
    • G05—CONTROLLING; REGULATING
    • G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
    • G05B19/00—Programme-control systems
    • G05B19/02—Programme-control systems electric
    • G05B19/04—Programme control other than numerical control, i.e. in sequence controllers or logic controllers
    • G05B19/05—Programmable logic controllers, e.g. simulating logic interconnections of signals according to ladder diagrams or function charts
    • G05B19/052—Linking several PLC's
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F13/00—Interconnection of, or transfer of information or other signals between, memories, input/output devices or central processing units
    • G06F13/14—Handling requests for interconnection or transfer
    • G06F13/36—Handling requests for interconnection or transfer for access to common bus or bus system
    • G06F13/362—Handling requests for interconnection or transfer for access to common bus or bus system with centralised access control
    • G06F13/366—Handling requests for interconnection or transfer for access to common bus or bus system with centralised access control using a centralised polling arbiter
    • G—PHYSICS
    • G05—CONTROLLING; REGULATING
    • G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
    • G05B2219/00—Program-control systems
    • G05B2219/10—Plc systems
    • G05B2219/12—Plc mp multi processor system
    • G05B2219/1208—Communication, exchange of control, I-O data between different plc
    • G—PHYSICS
    • G05—CONTROLLING; REGULATING
    • G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
    • G05B2219/00—Program-control systems
    • G05B2219/10—Plc systems
    • G05B2219/12—Plc mp multi processor system
    • G05B2219/1216—Interlock problem, avoid sending data to slave when slave processes data
    • G—PHYSICS
    • G05—CONTROLLING; REGULATING
    • G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
    • G05B2219/00—Program-control systems
    • G05B2219/10—Plc systems
    • G05B2219/13—Plc programming
    • G05B2219/13017—Macro instructions

Definitions

  • the present invention relates to a system and a process of controlling a programmable controller acting as a master station for transferring data to and from a slave station.
  • the European Patent Application EP-A-0 187 677 discloses a linking system for a programmable controller.
  • a plurality of slave programmable controllers are connected to one master controller, the slave controllers having inner relays for linking their operation with one another according to link tables.
  • the master controller collects the link tables from the respective slaves.
  • the master controller prepares an edit link table for subsequent program control making use of the slaves.
  • Fig. 8A shows an example of another configuration of a programmable controller having a slave station 3A, to which a programmable controller controlling process of the background art is applied.
  • a master station 1 is connected via a link cable 2 to slave station 3A.
  • a central data processing module 4 provided in the master station 1 utilizes a program memory 5 for storing sequence programs.
  • An internal device memory 6 is also provided in the central data processing module 4, and includes a link register 6a for holding information identical to that transmitted on the link cable 2, a register for storing PROCESSING EXECUTING flag 6b for indicating that data transfer to and from a slave station, e.g.
  • the processing module 4 further includes an operation processor 7 for running the sequence program sequentially and a system program memory 9 for storing an operating system and other programs for operating the central data processing module 4.
  • a link module 8 is provided in the master station 1 between the link cable 2 and the central data processing module 4 for converting information transmitted by the link cable 2 into information acceptable by the central data processing module 4 as well as converting information in the central data processing module 4 into information transmittable by the link cable 2.
  • An I/O module 10 is for controlling a unit to be controlled (not illustrated) that is connected to the master station 1.
  • the slave station is at least one processing module 11 for transferring data to and from the central data processing module 4 in the master station 1.
  • a link module 12 is provided between the processing module 11 and the link cable 2 for converting information transmitted by the link cable 2 into information acceptable by the processing module 11 as well as converting information in the processing module 11 into information transmittable by the link cable 2.
  • a memory 13 is provided in the processing module 11, as well as an I/O module 14 for controlling a unit to be controlled (not illustrated) that is connected to the slave station 3A.
  • Fig. 9 shows a conventional program in ladder form for executing an RFRP instruction.
  • the RFRP instruction causes data to be received by the master station via the link cable from a slave station.
  • a corresponding instruction is RTOP, which causes data to be transmitted by the master to a slave station.
  • the RFRP instruction in Figure 9 is an example of a conventional program for transferring data between the master station 1 and slave station 3A.
  • the state symbol ⁇ indicates a "contact A" state condition and the state symbol ⁇ indicates a "contact B" state condition for the execution of an identified function.
  • the state symbol 901 shows an active state condition for the START flag 6e that is provided in the internal device memory 6.
  • the flag is set in the active state in order to initiate execution of the RFRP instruction in accordance with a program in the processing module 11.
  • the inactive state condition of the PROCESSING EXECUTING flag 6b, and the inactive state condition of the PROCESSING COMPLETE flag 6c are shown by symbols 902 and 903, respectively.
  • a 6D SET instruction 904 for setting a START CONDITION can be executed.
  • This START CONDITION ESTABLISHING flag 6d is stored at an address indicated by 6D (904a) in the internal device memory 6.
  • the state symbol 905 indicates the active state of the START CONDITION ESTABLISHING flag 6d.
  • the START CONDITION ESTABLISHING flag 6d is set as a result of step S901
  • the condition precedent to execution of step S902 is satisfied and RFRP instruction 906 is executed. Since the PROCESSING EXECUTING flag 6b and the PROCESSING COMPLETE flag 6c are stored at addresses which depend on the hardware configuration, it is necessary to check the hardware configuration and specify calculated addresses in the sequence program when performing a read or write.
  • the RFRP instruction 906 has operands nl (906a), n2 (906b), n3 (906d) and D (906c).
  • the instruction is used to transfer data from a particular slave station 3 to the master station 1 via the link cable 2.
  • the instruction identifies the number of words, n3 (906d), starting at address n2 (906b) in the memory 13 of the processing module 11 of a slave station identified by n1 (906a), which are to be transferred to positions starting at address D (906c) of the link register 6a provided in the internal device memory 6 of the central data processing module 4 in the master station 1.
  • the PROCESSING COMPLETE flag 6c is set.
  • the input conditions of steps S903 and S904 are satisfied, and a 6d reset instruction 907 and a 6b reset instruction 908 are executed.
  • Address 6D (907a) identifies the location at which the START CONDITION ESTABLISHING flag 6d is stored, and address 6B (908a) identifies the location at which the PROCESSING EXECUTING flag 6b is stored.
  • Fig. 9 The operation of the ladder language program shown in Fig. 9 may be described with reference to a timing chart illustrated in Figs. 10A and 10B.
  • the PROCESSING EXECUTING flag 6b is set at a point (1001) shown in Fig. 10A. This prevents execution of step S901 again until flag 6b is reset.
  • the PROCESSING COMPLETE flag 6c is set at a point 1002 shown in Fig. 10B.
  • the PROCESSING COMPLETE flag 6c is set at step S903 in Fig.
  • the 6D RESET instruction 907 is executed, the START CONDITION ESTABLISHING flag 6d is reset, the 6B RESET instruction 908 is executed at step S904, and the PROCESSING EXECUTING flag 6b is reset at point 1003 shown in Fig. 10A.
  • the PROCESSING COMPLETE flag 6c is automatically reset at a point 1004 after the PROCESSING EXECUTING flag 6b is reset, as shown in Fig. 10B.
  • flags 6b and 6c act as interlock conditions that assure that there is no overlap in the execution of program instructions. Thus, until flags 6b and 6c are both reset, the initial conditions of instruction S901 cannot be met, preventing further execution of that instruction until the current instruction has been completed. If instructions subsequent to those shown in S901-S904 are provided with initial conditions like those in S901, an effective step-by-step interlock can be achieved.
  • the aforementioned process has disadvantages in that it is required to check whether or not the operation of the processing module 11 is complete in the sequence program itself. Interlock processing has to be performed in the sequence program itself rather than by the operating system (OS). Because they serve interlock functions, it is necessary to check the PROCESSING EXECUTING flag 6b and the PROCESSING COMPLETE flag 6c, the addresses of which depend on several factors including the hardware configuration and the processing module loading position, and to specify these addresses in the sequence program.
  • OS operating system
  • an object of the present invention to overcome the disadvantages in the prior art process by providing a programmable controller controlling process which will not require an interlock processing program to be written and the addresses of the flags, depending on the hardware configuration, to be specified in the program, and which will ensure ease of program creation and maintenance.
  • the programmable controller employed as the master station executes the data link instruction to transmit data between the master station and the slave station
  • the address information of the operation complete flag memory specified beforehand in the sequence program is recorded into the operation complete flag address memory
  • the communicating information indicating that communication is being made with the relevant slave station is entered into the communication entry memory provided in correspondence with each slave station
  • the flag at the corresponding address in the operation complete flag memory is set in accordance with the address information recorded in the operation complete flag address memory.
  • the flag of the operation complete flag memory is reset and the information entered in the communication entry memory is erased.
  • Fig. 1 illustrates an overall configuration of a programmable controller and a slave station to which one embodiment of the present invention is applied.
  • Figs. 2A and 2B provide a program example of an MRFRP instruction written in ladder language in one embodiment of the present invention.
  • Fig. 3 is an operation flowchart of an operating system for executing the MRFRP instruction in one embodiment of the present invention.
  • Fig. 4 is an operation flowchart of an operating system for performing END processing for the MRFRP instruction in one embodiment of the present invention.
  • Figs. 5A-5C are operation timing charts of a processing executing flag, a processing complete flag and an operation complete flag, respectively, in one embodiment of the present invention.
  • Fig. 6 illustrates a communication entry memory in one embodiment of the present invention.
  • Fig. 7 illustrates an operation complete flag address memory in one embodiment of the present invention.
  • Fig. 8A illustrates the overall configuration of a programmable controller and a slave station to which a conventional programmable controller controlling process is applied.
  • Fig. 9 illustrates a conventional program written in ladder language for executing an RFRP instruction.
  • Fig. 10 is an operation timing chart of a processing executing flag and a processing complete flag in the conventional system.
  • FIG. 1 is an overall configuration diagram of a programmable controller to which the present invention is applied.
  • the overall configuration in Fig. 1 is identical to that of the conventional configuration shown in Fig. 8, with the exception of storage locations for additional information in the internal device memory 6 and the system program memory 9.
  • memory 6 further includes an OPERATION COMPLETE flag memory 6f and memory 9 includes a communications entry memory 9a and an OPERATION COMPLETE flag address memory 9b.
  • Fig. 2A illustrates a program written in ladder diagram form for executing in a single step S201 an "MRFRP" instruction 202.
  • the MRFRP instruction causes the master station 1 to receive data from a slave station 3 via the link cable 2 and is thus functionally the same as the prior art sequence of four instructions seen in Fig. 9.
  • a similar instruction MRTOP will cause the master station 1 to transmit data to a slave station 3 via the link cable 2.
  • the designation of the instruction with an "M" indicates that there is a "macro" function. In particular the macro function in the present embodiment will cause the OS to process the interlock flags 6b and 6c automatically.
  • symbol 901 shows a START flag 6e which it is set for executing the MRFRP instruction 202.
  • step S201 When the START flag 6e is set, the input condition of step S201 is established and the MRFRP instruction 202 is executed. Operands n1 (202a), n2 (202b), D (202c) and n3 (202d) of the MRFRP instruction 202 have the same meanings as those of the RFRP instruction 906 in the conventional process.
  • the address 6f identifies a memory location (202e) for storing an OPERATION COMPLETE flag 6f for indicating whether or not the operation of the MRFRP instruction 202 is complete.
  • the OPERATION COMPLETE flag 6f is referenced by other instructions in the sequence program in order to identify whether or not the predetermined operation by the MRFRP instruction 202 is complete, and may be located at any arbitrary memory location.
  • the single step S201 in Fig. 2A is equivalent to the four steps (S901 to S904) in Fig. 9 of the conventional process. Whether or not the operation of the relevant instruction is complete may be checked simply by executing an OPERATION COMPLETE flag reference instruction which refers to the OPERATION COMPLETE flag 6f stored at address 6F. As a result, it is not necessary to refer, in the sequence program, to the PROCESSING EXECUTING flag 6b and the PROCESSING COMPLETE flag 6c, whose addresses depend on the hardware configuration and loading position, in order to determine the completion of an instruction, as required by the conventional process illustrated in Fig. 9.
  • Figure 2B illustrates the basic instruction processing that is conducted with the use of the macro instruction of the present invention, beginning with a START command from the master station and ending with an END command.
  • Several such processing functions are conducted in series in a sequence program, and overlap is avoided.
  • Fig. 3 is an operation flowchart for an operating system, starting from step S300, for executing the MRFRP instruction 202, as an example of the instruction shown in Fig. 2 for transferring data between the master station 1 and slave station.
  • the central data processing module 4 runs the sequence program repeatedly.
  • step S301 checks whether or not the identity of a processing module 11 of a slave station 3A...3N has been entered into the communication entry memory 9a provided in the system program memory 9 in master station 1. This entry is made by setting a bit in the communication entry memory 9a corresponding to one of a plurality of processing modules 11.
  • Memory 9a has a bit location corresponding to each unit in the network that communicates with the central data processing module 4 in the master station 1. As shown in Fig. 6, up to 64 units can be accommodated in this particular system, though there is no practical limit.
  • step S301 If the identity of a specific processing module 11 already has been entered in memory 9a, it is concluded at step S301 that the processing module 11 is already operating. Hence, the MRFRP instruction 202 is terminated at step S306 without any operation. If it is determined that the identity of a specific processing module 11 has not been entered in memory 9a, the process proceeds to the next step S302, which checks the PROCESSING EXECUTING flag 6b and the PROCESSING COMPLETE flag 6c, which are the same as those in the conventional process of Fig. 9. If both flags have already been reset, indicating the absence of an interlock condition, execution progresses to the next step S303, which enters into the communication entry memory 9a communication information indicating that the processing module 11 has started operation.
  • an address of the OPERATION COMPLETE flag 6f in the processing module 11 is then stored in the OPERATION COMPLETE flag address memory 9b provided in the system program memory 9.
  • the operation performed is the same as that of the RFRP instruction 906 shown in Fig. 9 in the conventional process. Specifically, as shown in Fig. 10, at the point 1001 the PROCESSING EXECUTING flag 6b is set and data transmission from the processing module 11 in the slave station to the central data processing module 4 in the master station 1 is initiated. When the data transmission is complete, execution progresses to the next step in the sequence program.
  • step S306 the process is terminated without any execution of the new instruction. The operation then progresses to the next step (not shown) in the sequence program.
  • Fig. 4 is an operation flowchart of the operating system in an END processing mode, indicated by step S400.
  • the mode is performed when one cycle of the sequence program is terminated in a process in which the central data processing module 4 runs the sequence program repeatedly.
  • step S401 a check is made of whether the identity of a processing module 11 has been entered at step S303 in Fig. 3. Since no instruction is being executed for the processing module 11 if there has not yet been an entry, END processing is not required and is terminated at step S409 without any execution.
  • step S402 If the identity of a processing module 11 has been entered at step S303, an instruction has been provided to the processing module 11, and so program execution then progresses to step S402, where a check is made of the status of the PROCESSING COMPLETE flag 6c in order to determine whether or not that instruction has been completed, as seen in Fig. 5B.
  • the PROCESSING COMPLETE flag 6c is set at a point 502 (Fig. 5B) when the data transmission from the processing module 11 is terminated as in the conventional process shown in Fig. 10. Flag 6c is automatically reset at point 505 after the sequence program has completed two cycles.
  • step S403 If the PROCESSING COMPLETE flag 6c has not yet been set at step S402, the execution progresses to step S403, which checks the OPERATION COMPLETE flag 6f. If the flag has not yet been set, step S403 judges that data transmission from the processing module 11 to the central data processing module 4 is not yet complete and terminates the END processing at step S409 without any operation.
  • step S404 If it is determined that the PROCESSING COMPLETE flag 6c has been set at step S402, program execution progresses to step S404, which checks the OPERATION COMPLETE flag 6f. If it is determined that that flag has not yet been set, the execution progresses to step S405, which sets the OPERATION COMPLETE flag 6f at point 503 in Fig. 5C, immediately following the setting of the PROCESSING COMPLETE flag 6c at point 502. Step S406 resets the PROCESSING EXECUTING flag 6b at point 504 as shown in Fig. 5A, and terminates the operation at step S409.
  • step S404 If the OPERATION COMPLETE flag 6f has been set at step S404, then the execution is terminated at step S409 without any operation.
  • step S402 If a reset of the PROCESSING COMPLETE flag 6c at step S402 had caused the execution to progress to step S403, which then determined that the OPERATION COMPLETE flag 6f was already set, the execution next progresses to step S407, which resets the OPERATION COMPLETE flag 6f at a point 506 subsequent to the point 505 as shown in Figs. 5B and 5C. Execution then progresses to step S408, which erases the communication information of the processing module 11 from the communication entry memory 9a and terminates the END processing at step S409.
  • slave stations 3A-3N may be used instead of one slave station 3 pictured in Fig. 1, and several processing modules 11 may also be used.
  • data transmission may be made from the master station 1 to the slave station 3, using an instruction MRTOP, in addition to the data transfer from the slave station 3 to the master station made by the MRFRP data link instruction in the above embodiment.
  • one memory may be used as both the communication entry memory 9a and the operation complete flag address memory 9b instead of the two provided separately in the above embodiment.

Landscapes

  • Engineering & Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Theoretical Computer Science (AREA)
  • General Engineering & Computer Science (AREA)
  • Automation & Control Theory (AREA)
  • Programmable Controllers (AREA)

Claims (10)

  1. Verfahren zum Steuern der Kommunikation zwischen einer Hauptstation (1) und einer Vielzahl von Unterstationen (3A), wobei die Hauptstation (1) eine programmierbare Steuerung hat, die einen Operationsprozessor (7) zur zyklischen Ausführung eines Ablaufprogramms aufweist, und weiterhin folgendes aufweist: einen Operation-beendet-Flagspeicher (6f) zum Speichern eines Flags, das die Beendigung einer Operation anzeigt, die durch einen Datenübertragungsbefehl (202), der in dem Ablaufprogramm enthalten ist, bezeichnet ist, einen Operation-beendet-Flagadreßspeicher (9b) für jede Unterstation (3A) zum Speichern von Adreßinformation für den Operation-beendet-Flagspeicher, und einen Kommunikationseingabespeicher (9a) für jede Unterstation (3A) zur Eingabe von Kommunikationsinformation, die anzeigt, daß mit einer bestimmten Unterstation (3A) kommuniziert wird,
    wobei das Verfahren die folgenden Schritte aufweist:
    a) Ausführen des Datenübertragungsbefehls (202), um Daten zwischen der speziellen Unterstation (3A) und der Hauptstation (1) zu übertragen,
    b) Einschreiben (5304) der Adreßinformation des Operation-beendet-Flagspeichers (6f), der in dem Ablaufprogramm bezeichnet ist, in den Operation-beendet-Flagadreßspeicher (9b), der der speziellen Unterstation (3A) entspricht,
    c) Eingeben (S305) der Kommunikationsinformation in den Kommunikationseingabespeicher (9a), der der speziellen Unterstation (3A) entspricht,
    und vor der Ausführung in Schritt (a) des Datenübertragungsbefehls (202), die folgenden Schritte aufweist:
    a1) Setzen (S405) eines Flags an einer entsprechenden Adresse in dem Operation-beendet-Flagspeicher (6f) nach Maßgabe von Adreßinformation, die in den Operation-beendet-Flagadreßspeicher (9b) eingeschrieben ist, bei Beendigung der durch den Datenübertragungsbefehl (202) bezeichneten Operation, und
    a2) Rücksetzen (S406) des Flags des Operation-beendet-Flagspeichers (6f) und Löschen (S408) der in den Kommunikationseingabespeicher (9a) eingegebenen Kommunikationsinformation nach Ausführung von wenigstens einem Zyklus des Ablaufprogramms.
  2. Verfahren nach Anspruch 1, das ferner den Schritt aufweist: Prüfen (S403, S404) des Operation-beendet-Flagspeichers (6f) in bezug auf ein Operation-beendet-Flag, das die Beendigung des Datenübertragungsbefehls (202) bezeichnet.
  3. Verfahren nach Anspruch 2, wobei der Prüfschritt (S403, S404) durchgeführt wird durch Ausführen eines Befehls in dem Ablaufprogramm, der sich auf ein Operation-beendet-Flag bezieht, das in dem Operation-beendet-Flagspeicher (6f) gespeichert ist.
  4. Verfahren nach Anspruch 1, das weiterhin die folgenden Schritte aufweist:
    es wird auf der Basis des Datenübertragungsbefehls (202) und des Inhalts des Kommunikationseingabespeichers (9a) beurteilt, ob eine Kommunikation stattfindet oder nicht, und wenn eine Kommunikation stattfindet, wird diese Kommunikation verriegelt, oder wenn eine Kommunikation nicht stattfindet, wird diese Kommunikation hergestellt, und Information, die anzeigt, daß eine Kommunikation stattfindet, wird in den Kommunikations-Eingabespeicher (9a) auf der Basis des Datenübertragungsbefehls (202) eingegeben; und
    nach Beendigung dieser Kommunikation wird der Inhalt des Kommunikationseingabespeichers (9a) geändert, um anzuzeigen, daß momentan nicht kommuniziert wird.
  5. Verfahren nach Anspruch 1, das weiterhin die folgenden Schritte aufweist:
    ein Kettenbefehl wird als der Datenübertragungsbefehl (202) eingegeben, um mit der Unterstation (3A) zu kommunizieren;
    es wird beurteilt, ob auf der Basis des Inhalts des Kommunikationseingabespeichers (9a) kommuniziert wird oder nicht, und wenn kommuniziert wird, wird diese Kommunikation verriegelt, oder wenn nicht kommuniziert wird, wird die Kommunikation hergestellt, und Information, die anzeigt, daß kommuniziert wird, wird in den Kommunikationseingabespeicher (9a) auf der Basis des Kettenbefehls eingegeben;
    nach Beendigung der Kommunikation werden die Inhalte einer Speicheradresse gesetzt, während gleichzeitig mehr als ein Zyklus des Ablaufprogramms ausgeführt wird, so daß ein anderer Befehl, der auf dem Ablaufprogramm beschrieben ist, auf die Beendigung der Kommunikation Bezug nehmen kann, und der Inhalt des Kommunikationseingabespeichers (9a) wird geändert, um anzuzeigen, daß nicht kommuniziert wird.
  6. System, das eine Hauptstation (1) und eine Vielzahl von damit kommunizierenden Unterstationen (3A) hat, wobei die Hauptstation (1) eine programmierbare Steuerung hat, die einen Operationsprozessor (7) zum Ausführen eines Ablaufprogramms aufweist, das eine Vielzahl von Datenübertragungsbefehlen (202) aufweist, von denen jeder eine Datenübertragung zwischen der Hauptstation (1) und einer bezeichneten Unterstation (3A) definiert,
    wobei der Operationsprozessor ausgebildet ist, um das Ablaufprogramm zyklisch auszuführen, und die Hauptstation gekennzeichnet ist durch:
    einen Operation-beendet-Flagspeicher (6f) zum Speichern eines Flags, das die Beendigung einer Operation anzeigt, die durch einen in dem Ablaufprogramm enthaltenen Datenübertragungsbefehl bezeichnet ist,
    einen Operation-beendet-Flagadreßspeicher (9b), der einen Speicherplatz für jede Unterstation (3A) hat, um Adreßinformation des Operation-beendet-Flagspeichers (6f) zu speichern, und
    einen Kommunikationseingabespeicher (9a) für jede Unterstation (3A), um Information einzugeben, die anzeigt, daß mit einer entsprechenden Unterstation (3A) kommuniziert wird.
  7. System nach Anspruch 6, wobei jede der Unterstationen (3A) eine Einrichtung zum Erzeugen eines Datenübertragungs-Endesignals aufweist, und daß die Hauptstation eine auf das Datenübertragungs-Endesignal ansprechende Einrichtung hat, um das Operation-beendet-Flag in dem Operation-beendet-Flagspeicher (6f) zu speichern.
  8. System nach Anspruch 6 oder 7, wobei die programmierbare Steuerung weiterhin aufweist:
    eine Einrichtung zum Setzen eines Flags an einer entsprechenden Adresse in dem Operation-beendet-Flagspeicher (6f) nach Maßgabe von Adreßinformation, die in dem Operation-beendet-Flagadreßspeicher (9b) gespeichert ist, bei Beendigung der durch einen Datenübertragungsbefehl (202) gestarteten Operation, und
    eine Einrichtung zum Rücksetzen des Flags des Operation-beendet-Flagspeichers (6f) und zum Löschen der in den Kommunikationseingabespeicher (9a) eingegebenen Kommunikationsinformation nach Ausführung von wenigstens einem Zyklus des Ablaufprogramms.
  9. System nach einem der Ansprüche 6 bis 8, wobei jede durch einen Datenübertragungsbefehl (202) bezeichnete Operation während ihrer Ausführung verriegelt ist.
  10. System nach Anspruch 6, wobei jeder Datenübertragungsbefehl (202) des Ablaufprogramms durch Start- und Endebefehle definiert ist, und wobei der Operationsprozessor (7) aufweist: eine Makrobefehlseinrichtung, die auf die Beendigung der durch den Datenübertragungsbefehl bezeichneten Operation anspricht und das Flag in den Operation-beendet-Flagspeicher (6f) setzt, und eine Einrichtung zum Rücksetzen des Flags des Operation-beendet-Flagspeichers (6f) und zum Löschen der in den Kommunikationseingabespeicher (9a) eingegebenen Kommunikationsinformation nach Ausführung von wenigstens einem Zyklus des Ablaufprogramms.
EP91102560A 1990-02-27 1991-02-21 Programmierbare Steuereinrichtung mit automatischer Steuerung des Verriegelungsprozesses Expired - Lifetime EP0444535B1 (de)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
JP2046540A JP2508872B2 (ja) 1990-02-27 1990-02-27 プログラマブルコントロ―ラの制御方法
JP46540/90 1990-02-27

Publications (3)

Publication Number Publication Date
EP0444535A2 EP0444535A2 (de) 1991-09-04
EP0444535A3 EP0444535A3 (en) 1994-06-29
EP0444535B1 true EP0444535B1 (de) 1997-11-12

Family

ID=12750129

Family Applications (1)

Application Number Title Priority Date Filing Date
EP91102560A Expired - Lifetime EP0444535B1 (de) 1990-02-27 1991-02-21 Programmierbare Steuereinrichtung mit automatischer Steuerung des Verriegelungsprozesses

Country Status (4)

Country Link
US (1) US5437048A (de)
EP (1) EP0444535B1 (de)
JP (1) JP2508872B2 (de)
DE (1) DE69128159T2 (de)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP0936515A1 (de) * 1998-02-17 1999-08-18 Robert Bosch Gmbh Mehrprozessor-Steuervorrichtung

Families Citing this family (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP3322754B2 (ja) * 1994-05-17 2002-09-09 富士通株式会社 並列計算機
US6272578B1 (en) * 1995-12-25 2001-08-07 Omron Corporation Programmable controller
JP5552042B2 (ja) * 2010-12-27 2014-07-16 インターナショナル・ビジネス・マシーンズ・コーポレーション プログラム解析の方法、システムおよびプログラム
CN111984608B (zh) * 2020-08-19 2024-10-15 北京龙鼎源科技股份有限公司 数据存储方法、装置、存储介质和处理器
KR102543841B1 (ko) * 2021-04-06 2023-06-14 엘에스일렉트릭(주) 통신 기반 제어 시스템의 효율적 슬레이브 파라미터 관리 방법 및 그 장치

Family Cites Families (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US3728693A (en) * 1972-04-28 1973-04-17 Burroughs Corp Programmatically controlled interrupt system for controlling input/output operations in a digital computer
DE3242631A1 (de) * 1981-11-18 1983-05-26 Omron Tateisi Electronics Co., Kyoto Programmierbare steuereinrichtung
US4689739A (en) * 1983-03-28 1987-08-25 Xerox Corporation Method for providing priority interrupts in an electrophotographic machine
JPS59205605A (ja) * 1983-05-07 1984-11-21 Hitachi Ltd シ−ケンス制御装置
JPS60114908A (ja) * 1983-11-25 1985-06-21 Mitsubishi Electric Corp 運転優先順序制御装置
JPS60117998A (ja) * 1983-11-30 1985-06-25 Mitsubishi Electric Corp プログラマブルコントロ−ラ
JPS60262204A (ja) * 1984-06-07 1985-12-25 Omron Tateisi Electronics Co プログラマブル・コントロ−ラ
JPS61161506A (ja) * 1985-01-11 1986-07-22 Toshiba Mach Co Ltd プログラマブルコントロ−ラのリンク方式
JPS62226234A (ja) * 1986-03-28 1987-10-05 Toshiba Corp スタツクポインタ制御回路
US4888726A (en) * 1987-04-22 1989-12-19 Allen-Bradley Company. Inc. Distributed processing in a cluster of industrial controls linked by a communications network
JPH01118902A (ja) * 1987-10-30 1989-05-11 Fanuc Ltd Ｐｃのデータ転送制御方式
CA2007140A1 (en) * 1989-08-09 1991-02-09 Toshiji Senda Method of sequence control

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP0936515A1 (de) * 1998-02-17 1999-08-18 Robert Bosch Gmbh Mehrprozessor-Steuervorrichtung

Also Published As

Publication number Publication date
JPH03248204A (ja) 1991-11-06
JP2508872B2 (ja) 1996-06-19
US5437048A (en) 1995-07-25
EP0444535A3 (en) 1994-06-29
DE69128159D1 (de) 1997-12-18
DE69128159T2 (de) 1998-06-10
EP0444535A2 (de) 1991-09-04

Similar Documents

Publication Publication Date Title
EP0311007B1 (de) Speicherprogammierbare Steuerung mit mehreren Taskprozessoren
US4918589A (en) Method and apparatus for linking processors in a hierarchical control system
CN112000351A (zh) Bmc固件的更新方法、更新装置、更新设备及存储介质
EP0444535B1 (de) Programmierbare Steuereinrichtung mit automatischer Steuerung des Verriegelungsprozesses
JPS582761A (ja) ユニツトのテスト方法
US4999554A (en) Method of loading control program for numerical control apparatus
JPH0776932B2 (ja) デ−タ伝送方式
US6374335B1 (en) Data loading process
JPH03136107A (ja) プログラマブルコントローラ
US5530888A (en) Process and apparatus for controlling a programmable controller with efficient identification of operation completion
JPH0871979A (ja) ロボットコントローラ
JP3269164B2 (ja) プログラマブルコントローラの周辺装置
JP3216020B2 (ja) プログラマブルコントローラのリンク装置
JP2014127055A (ja) Ｐｌｃの周辺装置
JP3005379B2 (ja) プログラマブルコントローラ間通信システム
JPH0155617B2 (de)
JP3227273B2 (ja) プログラマブルコントローラのリンク処理方式
EP0089194B1 (de) Verfahren und Gerät zum Anzeigen von Leiterdiagrammen
JP2605491B2 (ja) 設備管理コントローラ
CN119025462A (zh) 内部总线转换为spi接口协议的交互方法、装置及相关设备
JP2697022B2 (ja) ユニットの動作設定方法
JP2735112B2 (ja) 数値制御装置のデータ・リード・ライト方式
JP7016229B2 (ja) 鉄道用信号保安システム及び制御方法
JPH04172503A (ja) Ｆａコントローラ
JP2862151B2 (ja) プログラマブルコントローラ

Legal Events

Date Code Title Description
PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

AK Designated contracting states

Kind code of ref document: A2

Designated state(s): DE FR SE

PUAL Search report despatched

Free format text: ORIGINAL CODE: 0009013

AK Designated contracting states

Kind code of ref document: A3

Designated state(s): DE FR SE

17P Request for examination filed

Effective date: 19940801

17Q First examination report despatched

Effective date: 19960311

GRAG Despatch of communication of intention to grant

Free format text: ORIGINAL CODE: EPIDOS AGRA

GRAH Despatch of communication of intention to grant a patent

Free format text: ORIGINAL CODE: EPIDOS IGRA

GRAH Despatch of communication of intention to grant a patent

Free format text: ORIGINAL CODE: EPIDOS IGRA

GRAA (expected) grant

Free format text: ORIGINAL CODE: 0009210

AK Designated contracting states

Kind code of ref document: B1

Designated state(s): DE FR SE

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: FR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 19971112

REF Corresponds to:

Ref document number: 69128159

Country of ref document: DE

Date of ref document: 19971218

EN Fr: translation not filed
PLBE No opposition filed within time limit

Free format text: ORIGINAL CODE: 0009261

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: NO OPPOSITION FILED WITHIN TIME LIMIT

26N No opposition filed
PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: SE

Payment date: 20020206

Year of fee payment: 12

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: SE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20030222

EUG Se: european patent has lapsed
PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: DE

Payment date: 20100303

Year of fee payment: 20

REG Reference to a national code

Ref country code: DE

Ref legal event code: R071

Ref document number: 69128159

Country of ref document: DE

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: DE

Free format text: LAPSE BECAUSE OF EXPIRATION OF PROTECTION

Effective date: 20110221