USRE36263E - Peer-to-peer register exchange controller for PLCS - Google Patents

Peer-to-peer register exchange controller for PLCS Download PDF

Info

Publication number
USRE36263E
USRE36263E US08/645,606 US64560696A USRE36263E US RE36263 E USRE36263 E US RE36263E US 64560696 A US64560696 A US 64560696A US RE36263 E USRE36263 E US RE36263E
Authority
US
United States
Prior art keywords
peer
iaddend
iadd
plc
blocks
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
US08/645,606
Inventor
Donald R. Janke
Kim J. Watt
Dirk I. Gates
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.)
Schneider Electric USA Inc
Original Assignee
Schneider Automation Inc
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 Schneider Automation Inc filed Critical Schneider Automation Inc
Priority to US08/645,606 priority Critical patent/USRE36263E/en
Assigned to SCHNEIDER AUTOMATION, INC. reassignment SCHNEIDER AUTOMATION, INC. ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: AEG SCHNEIDER AUTOMATION, INC.
Assigned to SCHNEIDER AUTOMATION INC. reassignment SCHNEIDER AUTOMATION INC. CHANGE OF NAME (SEE DOCUMENT FOR DETAILS). Assignors: AEG SCHNEIDER AUTOMATION, INC.
Application granted granted Critical
Publication of USRE36263E publication Critical patent/USRE36263E/en
Anticipated expiration legal-status Critical
Expired - Lifetime legal-status Critical Current

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F15/00Digital computers in general; Data processing equipment in general
    • G06F15/16Combinations of two or more digital computers each having at least an arithmetic unit, a program unit and a register, e.g. for a simultaneous processing of several programs
    • GPHYSICS
    • G05CONTROLLING; REGULATING
    • G05BCONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
    • G05B19/00Programme-control systems
    • G05B19/02Programme-control systems electric
    • G05B19/04Programme control other than numerical control, i.e. in sequence controllers or logic controllers
    • G05B19/05Programmable logic controllers, e.g. simulating logic interconnections of signals according to ladder diagrams or function charts
    • G05B19/052Linking several PLC's
    • GPHYSICS
    • G05CONTROLLING; REGULATING
    • G05BCONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
    • G05B2219/00Program-control systems
    • G05B2219/10Plc systems
    • G05B2219/11Plc I-O input output
    • G05B2219/1132High speed bus between plc and plc or programming device
    • GPHYSICS
    • G05CONTROLLING; REGULATING
    • G05BCONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
    • G05B2219/00Program-control systems
    • G05B2219/10Plc systems
    • G05B2219/11Plc I-O input output
    • G05B2219/1159Image table, memory
    • GPHYSICS
    • G05CONTROLLING; REGULATING
    • G05BCONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
    • G05B2219/00Program-control systems
    • G05B2219/10Plc systems
    • G05B2219/12Plc mp multi processor system
    • G05B2219/1208Communication, exchange of control, I-O data between different plc

Definitions

  • This invention relates generally to interconnecting programmable logic controllers . .connected together.!. to effect sequential program instructions and particularly relates to interconnecting image memory portions of several programmable logic controllers to enable operation at a speed much greater than the operating speed of the programmable logic controllers functioning independently.
  • programmable logic controllers have received sensor information over a communications network or over discrete leads from . .the.!. .Iadd.a .Iaddend.machine tool being controlled.
  • the programmable logic controller or PLC processes the sensor information according to sequential instructions contained in its program memory portion. . .
  • the result of the processing of.!. .Iadd.Processing .Iaddend.the sensor information often results in command information that the PLC transmits to switches or actuators on the controlled machine tool over the communications network or on discrete leads.
  • PLCs normally include an image memory which contains registers and addresses assigned to reflect the condition of the various sensors monitoring the machine tool. Information from the sensors and received at the PLC becomes stored . .at.!. .Iadd.in .Iaddend.certain registers .Iadd.of the image memory .Iaddend.and the processing instructions in the PLC operate on . .the.!. .Iadd.this .Iaddend.information contained in the image memory.
  • Some PLCs include two processors to obtain increased operating speed. .: one.!. .Iadd.. The first such processor .Iaddend.is a control processor that handles communications with the sensors and drivers to move information to and from the image memory and . .that assigns.!.
  • the invention provides a high-speed interconnection between the image memory portions of several PLCs operating together. This allows each PLC to operate on a portion of a sequential instruction set and for the solution obtained by each PLC to appear in the image memory portions of the other PLCs at a time that is effectively simultaneous with the solution.
  • the high-speed image memory transfers between the PLCs occur with parity and CRC checking at each PLC before the information is written into the image memory of that PLC to verify the accuracy of the information transfer between the image memories.
  • the foregoing not only obtains increased operating speed but guarantees the accuracy of the information transferred between image memory portions of the PLCs.
  • FIG. 1 is a block diagram of four programmable logic controllers (PLCs) . .connecting.!. .Iadd.connected .Iaddend.to a communications . .network.!. .Iadd.bus.Iaddend.;
  • PLCs programmable logic controllers
  • FIG. 2 is a block diagram of a modification of the diagram of FIG. 1 which includes a high-speed .Iadd.image .Iaddend.memory transfer . .network.!. .Iadd.bus .Iaddend.in accordance with the invention;
  • FIG. 3 is a block diagram showing transferable . .register.!. .Iadd.registers .Iaddend.of each of the four PLCs and indicating transfer of blocks between the registers by the arrowed lines; and,
  • FIG. 4 shows the manner of connection between two communications . .networks.!. .Iadd.buses.Iaddend..
  • FIG. 1 . .shows.!. .Iadd.illustrates .Iaddend.a presently used . .communications.!. .Iadd.PLC .Iaddend.network .Iadd.11 .Iaddend.including a group of . .4.!. .Iadd.four .Iaddend.programmable logic controllers (PLCs) numbered . .1.!. .Iadd.1A .Iaddend.to 4A.
  • PLCs numbered . .1.!. .Iadd.1A .Iaddend.to 4A.
  • the memory 16A is accessed by the control processor 12A to obtain or provide communications and control data.
  • the scan processor 14A in turn accesses the . .image.!. memory 16A and then through the control processor 12A to the communications . .network.!. .Iadd.bus .Iaddend.20A.
  • FIG. 2 . .shows.!. .Iadd.illustrated .Iaddend.a . .communications.!. .Iadd.PLC .Iaddend.network 21 of the .Iadd.present .Iaddend.invention including four programmable logic controllers (PLCs) .Iadd.numbered .Iaddend.1 to 4, .Iadd.interconnected via a communications bus 20, .Iaddend.although up to . .16.!. .Iadd.sixteen .Iaddend.PLC's can be used.
  • Each of the PLCs includes a control processor 12, a scan processor 14, and a memory 16. Referring to FIG.
  • each of the PLCs further . .include.!. .Iadd.includes .Iaddend.a communications processor 18, a local RAM (Random Access Memory) . .20.!. .Iadd.19 .Iaddend.and a local area network interface 22.
  • the local area network interface 22 connects to a high speed image memory transfer . .network 21.!. .Iadd.bus 17.Iaddend..
  • the image memories . .16.!. of each of the PLCs . .1 to 4.!. are interconnected and are, in effect, commonly accessed by the network devices and by the other PLCs to provide a higher speed of network communication and transfer of data.
  • FIG. 3 . .which shows.!. .Iadd.illustrates .Iaddend.the image memory . .16.!. map 16-1, 16-2, 16-3 and 16-4 of each of the PLCs . .1 to 4.!. .Iadd.PLC1 to PLC4.Iaddend..
  • the memory maps of the PLCs are similar and each consists of . .2.!. .Iadd.two .Iaddend.to . .16.!. .Iadd.sixteen .Iaddend.blocks .Iadd.of registers.Iaddend..
  • the transferable memory of each PLC represented in FIG. 3 will be divided .
  • each device sends a different block of registers. This is . .shown.!. .Iadd.illustrated .Iaddend.in FIG. 3 wherein the arrowed line generally marked as 30 indicates the transfer of block . .register.!. .Iadd.of registers .Iaddend.1 of PLC 1 to PLC 2, PLC 3 and PLC 4.
  • PLC 3 transfers the block .Iadd.of .Iaddend.registers 3 to PLC 1, PLC 2 and PLC 4
  • PLC 4 transfers the block of registers 4 to PLC 1, PLC 2 and PLC 3.
  • FIG. 4 . .shows.!. .Iadd.illustrates .Iaddend.circuitry for coupling from a first communications . .network.!. .Iadd.bus .Iaddend.23 to a second communications . .network.!. .Iadd.bus .Iaddend.25.
  • This is accomplished through a dual port network interface module 26 as explained in co-pending U.S. patent application Ser. No. 179,756 entitled "Network Interface Board System".
  • FIG. 4 .Iadd.the second .Iaddend.communications . .network.!. .Iadd.bus .Iaddend.25 communicates through . .a.!.
  • the peer-to-peer network is able to transfer blocks of registers between 2 to 16 devices, each device sending a different block of registers.
  • Each block of registers is assigned a mailbox location. The location of the mailbox is dependent on the ID number that each device is assigned.
  • each device sends a loop formation packet onto the network.
  • the packet is identified as a loop formation packet, and contains information on the address of the sender, and size of blocks.
  • loop formation the following is set up.
  • the number of units on the network is determined, verification is made that all units have the same block size, each unit tests its address against the address of the other devices, and time slices for each device on the network are defined, that is, each device on the network calculates during what time slice it is to transmit, and what block it should be receiving during any given time slice.
  • Each device sends a packet when it detects that the network is free. In the event there is a collision, the colliding units back off, and after a random delay, they resend their packets.
  • the sending device After a formation packet is sent, the sending device delays the time necessary to receive and process one packet. If a packet is received, it will again delay the time necessary to receive and process a packet. This will continue until no more packets are received. This means that all units will have time to send their packets to all other devices. After the last packet has been received, and the last time out, normal loop operation commences.
  • the transmitter waits one packet time before sending the first packet.
  • the receivers will wait three packet times before timing out.
  • loop formation is a function of the block size, and the number of units on the network.
  • formation time is determined by the following equation:
  • Each device on the network sends its packet during the time slice defined during loop formation.
  • the transmitted data is direct memory accessed out of the shared register RAM allowing the communication processor to handle necessary processing tasks such as updating the overall communication status bits.
  • each device When not transmitting data, each device waits for a packet from another device. When a packet is received, its CRC is validated, and a check is made if the sender of the packet is in the correct time slice. If the packet is totally validated, it is moved to the shared RAM.
  • the device will drop out of normal operation and go to loop formation mode.
  • the update time for a given installation can be determined by multiplying the block time for a single update by the actual number of units on the network.
  • the communication update rate is a function of the actual number of units on the network and the block size.
  • Ladder scans of some or all of the processors on the network can be automatically synchronized. This allows the processors to scan at the same time and facilitates parallel processing.
  • the serial network interface receives and transmits data over the peer-to-peer network.
  • the data is sent in block form with CRC protection and parity protection on each block.
  • the transmission method does not use collision detection schemes and is completely deterministic in the time domain.
  • the serial network interface uses the shared register area (two port) as storage or the location to get messages.
  • the communication processor takes care of all processing required by the peer-to-peer network. It has access to the serial network interface and two port memory. It also has inputs to the setup switches. The communication processor sets up the network protocols and reports network status to the user through the two port memory.
  • the communication processor does most communication with the control processor through the two port memory.
  • Each PLC device has a bank of switches for setup. The state of the switches is read once at power up by the communication processor.
  • One switch is a rotary switch to set up the identification number of the device from O to F. Every device connected to the peer-to-peer network must have a unique identification number or the network will not operate properly. Labeling on the front panel allows the user to indicate the device ID number.
  • the other switches are arranged as follows:
  • This code indicates the block size.
  • the block size is the number of registers sent from a device on the network to all other devices on the network. All devices on the network must have the same code or the network will not operate properly.
  • the code is as follows:
  • the AUTO position automatically configures the maximum number of registers possible based on the setting of the Maximum Number of Units on the Network switch.
  • the following table describes this relationship:
  • the 1024 "shared data registers" can be arranged in any one of 4 different block size configurations. They are: 2 blocks of 512 registers, 4 blocks of 256 registers, 8 blocks of 128 registers or 16 blocks of 64 registers.
  • the PLC device has a "peer-to-peer control register" at location 8096.
  • This register will allow the user to configure the shared registers for the particular application.
  • the bits in this register are dynamic in that they can be changed by the user program at any time.
  • Table 1 contains a map of the shared registers which are divided into 5 main sections. There are 8 control data registers, 5 spare registers, 3 miscellaneous registers, 16 communications status registers, and 1024 data registers. An explanation of the register follows:
  • the communication processor If the communication processor detects an error, it will post an error code in this register.
  • the Dip Switch Image (7999) register contains an image of the peer-to-peer dip switch. The user can read this register to find out how the dip switch is set without removing the device from the rack. The communication processor writes the data to this location.
  • the Device ID (7998) register contains the ID code assigned to this unit.
  • the communication processor decodes the ID code from the dip switch settings and places it here.
  • the Block Size (7997) register contains the peer-to-peer block size.
  • the communication processor decodes the block size.
  • the communication processor decodes the block size from the dip switch settings and places it here.
  • the Number of Blocks (7996) register contains the maximum number of blocks transferred by the peer-to-peer network.
  • the communication processor decodes the maximum number of blocks from the dip switch setting and places it here.
  • the Comms to CPU Handshake (7995) is an internal register used by communication processor to handshake with the control processor.
  • the Main CPU Handshake (7994) is an internal register used by control processor to handshake with the communication processor.
  • the Time Domain Reflectometry Counter (7993) counts proportional to the length of the cable. A counter is started when a transmission is started from a unit. Reflections from the cable end terminate the count. The value should be constant for a given installation and device on the network. It has a value as a trouble shooting tool.
  • the network may be automatically reformed.
  • the Count of Loop Formations (7987) register contains a count of the number of times the network has been reformed.
  • the Maximum Consecutive Block Errors (7986) register is programmed by the user to indicate the maximum number of consecutive block errors before the system automatically generates an error and goes to HALT.
  • the PLC When the bits in the Failure Override Control (7985) registers are zero, the PLC will generate an error if the communication processor detects (n) consecutive errors in a row where (n) is determined by the contents of the previous maximum consecutive block errors. If a bit is set to one, the error will not be generated. Bit 1 corresponds to PLC device 1, Bit 2 to PLC device 2 and so on, up to PLC device 15.
  • the Communication Status Registers (CSR) (7984-7969) are written to by the communication processor to give the status of individual communication channels. There is one register for each communications register.

Abstract

A communication network for programmable logic controllers (PLCs) wherein selected memory means of each PLC have at least two ports directly accessible by other PLCs and certain registers of the PLCs are identical to enable efficient, high-speed transfer of blocks of data between the PLCs.

Description

DESCRIPTION
1. Reference to Related Applications
This application is related to applications filed concurrently herewith, entitled "Network Communications System", . .Ser. No. 179,969.!. .Iadd.issued as U.S. Pat. No. 4,912,623.Iaddend.; "Ladder Sequence Controller" Ser. No. 180,093.Iadd., now abandoned.Iaddend.; High-Speed Press Control System" . .Ser. No. 179,743.!..Iadd., issued as U.S. Pat. No. 5,023,770.Iaddend.; and, "Network Interface Board System", Ser. No. 179,756.Iadd., now abandoned.Iaddend.. The contents of these applications are incorporated herein by reference.
2. Technical Field
This invention relates generally to interconnecting programmable logic controllers . .connected together.!. to effect sequential program instructions and particularly relates to interconnecting image memory portions of several programmable logic controllers to enable operation at a speed much greater than the operating speed of the programmable logic controllers functioning independently.
3. Background of the Invention
In the past, programmable logic controllers have received sensor information over a communications network or over discrete leads from . .the.!. .Iadd.a .Iaddend.machine tool being controlled. The programmable logic controller or PLC processes the sensor information according to sequential instructions contained in its program memory portion. . .The result of the processing of.!. .Iadd.Processing .Iaddend.the sensor information often results in command information that the PLC transmits to switches or actuators on the controlled machine tool over the communications network or on discrete leads.
PLCs normally include an image memory which contains registers and addresses assigned to reflect the condition of the various sensors monitoring the machine tool. Information from the sensors and received at the PLC becomes stored . .at.!. .Iadd.in .Iaddend.certain registers .Iadd.of the image memory .Iaddend.and the processing instructions in the PLC operate on . .the.!. .Iadd.this .Iaddend.information contained in the image memory. Some PLCs include two processors to obtain increased operating speed. .: one.!. .Iadd.. The first such processor .Iaddend.is a control processor that handles communications with the sensors and drivers to move information to and from the image memory and . .that assigns.!. .Iadd.to assign .Iaddend.tasks to the second processor. .; and the.!. .Iadd.. The .Iaddend.second .Iadd.such processor .Iaddend.is a . .SCAN.!. .Iadd.scan .Iaddend.processor that . .effects the.!. .Iadd.executes .Iaddend.sequential processing instructions to obtain information from the image memory and provide solutions to other certain addresses in the image memory under control of the control processor.
While this latter arrangement has obtained higher processing speeds, further speed increases are desired.
SUMMARY OF THE INVENTION
The invention provides a high-speed interconnection between the image memory portions of several PLCs operating together. This allows each PLC to operate on a portion of a sequential instruction set and for the solution obtained by each PLC to appear in the image memory portions of the other PLCs at a time that is effectively simultaneous with the solution.
Moreover, the high-speed image memory transfers between the PLCs occur with parity and CRC checking at each PLC before the information is written into the image memory of that PLC to verify the accuracy of the information transfer between the image memories. The foregoing not only obtains increased operating speed but guarantees the accuracy of the information transferred between image memory portions of the PLCs.
Other advantages and aspects of the invention will become apparent upon making the reference to the specification, claims, and drawings to follow.
DESCRIPTION OF THE DRAWINGS
FIG. 1 is a block diagram of four programmable logic controllers (PLCs) . .connecting.!. .Iadd.connected .Iaddend.to a communications . .network.!. .Iadd.bus.Iaddend.;
FIG. 2 is a block diagram of a modification of the diagram of FIG. 1 which includes a high-speed .Iadd.image .Iaddend.memory transfer . .network.!. .Iadd.bus .Iaddend.in accordance with the invention;
FIG. 3 is a block diagram showing transferable . .register.!. .Iadd.registers .Iaddend.of each of the four PLCs and indicating transfer of blocks between the registers by the arrowed lines; and,
FIG. 4 shows the manner of connection between two communications . .networks.!. .Iadd.buses.Iaddend..
DETAILED DESCRIPTION OF THE INVENTION
While this invention is susceptible of embodiment in many different forms, there is shown in the drawings and will herein be described in detail a preferred embodiment of the invention. The present disclosure is to be considered as an exemplification of the principles of the invention and is not intended to limit the broad aspect of the invention to .Iadd.the .Iaddend.embodiment illustrated.
FIG. 1 . .shows.!. .Iadd.illustrates .Iaddend.a presently used . .communications.!. .Iadd.PLC .Iaddend.network .Iadd.11 .Iaddend.including a group of . .4.!. .Iadd.four .Iaddend.programmable logic controllers (PLCs) numbered . .1.!. .Iadd.1A .Iaddend.to 4A. Each of the PLCs . .include.!. .Iadd.includes .Iaddend.a control processor . .12.!. .Iadd.12A.Iaddend., a scan processor 14A and . .an image.!. .Iadd.a .Iaddend.memory 16A. As . .noted.!. .Iadd.illustrated .Iaddend.in FIG. 1, the memory 16A is accessed by the control processor 12A to obtain or provide communications and control data. The scan processor 14A in turn accesses the . .image.!. memory 16A and then through the control processor 12A to the communications . .network.!. .Iadd.bus .Iaddend.20A.
FIG. 2 . .shows.!. .Iadd.illustrated .Iaddend.a . .communications.!. .Iadd.PLC .Iaddend.network 21 of the .Iadd.present .Iaddend.invention including four programmable logic controllers (PLCs) .Iadd.numbered .Iaddend.1 to 4, .Iadd.interconnected via a communications bus 20, .Iaddend.although up to . .16.!. .Iadd.sixteen .Iaddend.PLC's can be used. Each of the PLCs includes a control processor 12, a scan processor 14, and a memory 16. Referring to FIG. 2, the memory 16, for a device with peer-to-peer communications, is further divided into three sections, . .the.!. .Iadd.a .Iaddend.normal memory, .Iadd.an .Iaddend.image memory and . .the.!. .Iadd.a .Iaddend.two port shared memory. It is this shared memory and its operation that allow these programmable logic controllers to operate in a peer-to-peer (slave-to-slave) fashion. Importantly, each of the PLCs further . .include.!. .Iadd.includes .Iaddend.a communications processor 18, a local RAM (Random Access Memory) . .20.!. .Iadd.19 .Iaddend.and a local area network interface 22. The local area network interface 22 connects to a high speed image memory transfer . .network 21.!. .Iadd.bus 17.Iaddend..
As mentioned above, and as will be explained in detail hereinbelow, the image memories . .16.!. of each of the PLCs . .1 to 4.!. are interconnected and are, in effect, commonly accessed by the network devices and by the other PLCs to provide a higher speed of network communication and transfer of data.
. .Refer now to.!. FIG. 3 . .which shows.!. .Iadd.illustrates .Iaddend.the image memory . .16.!. map 16-1, 16-2, 16-3 and 16-4 of each of the PLCs . .1 to 4.!. .Iadd.PLC1 to PLC4.Iaddend.. The memory maps of the PLCs are similar and each consists of . .2.!. .Iadd.two .Iaddend.to . .16.!. .Iadd.sixteen .Iaddend.blocks .Iadd.of registers.Iaddend.. For simplicity of explanation, the transferable memory of each PLC represented in FIG. 3 will be divided . .with 4.!. .Iadd.into four .Iaddend.blocks. As each block of registers has an assigned time slot when it transfers blocks of registers, each device sends a different block of registers. This is . .shown.!. .Iadd.illustrated .Iaddend.in FIG. 3 wherein the arrowed line generally marked as 30 indicates the transfer of block . .register.!. .Iadd.of registers .Iaddend.1 of PLC 1 to PLC 2, PLC 3 and PLC 4. PLC 3 transfers the block .Iadd.of .Iaddend.registers 3 to PLC 1, PLC 2 and PLC 4, and PLC 4 transfers the block of registers 4 to PLC 1, PLC 2 and PLC 3.
FIG. 4 . .shows.!. .Iadd.illustrates .Iaddend.circuitry for coupling from a first communications . .network.!. .Iadd.bus .Iaddend.23 to a second communications . .network.!. .Iadd.bus .Iaddend.25. This is accomplished through a dual port network interface module 26 as explained in co-pending U.S. patent application Ser. No. 179,756 entitled "Network Interface Board System". As clearly shown in FIG. 4, .Iadd.the second .Iaddend.communications . .network.!. .Iadd.bus .Iaddend.25 communicates through . .a.!. .Iadd.the .Iaddend.network interface module 26 with RS-422 port in PLC 3 and a software switch 29 to .Iadd.the first .Iaddend.communications . .network.!. .Iadd.bus .Iaddend.23. This type of connection may be made necessary when the first . .network.!. .Iadd.communications bus .Iaddend.23 is supporting or has connected to it its maximum load of . .100.!. .Iadd.one hundred .Iaddend.network interface modules 26 and . .200.!. .Iadd.two hundred .Iaddend.devices (machines to be controlled, printers, terminals, computers, etc.).
The peer-to-peer network is able to transfer blocks of registers between 2 to 16 devices, each device sending a different block of registers. Each block of registers is assigned a mailbox location. The location of the mailbox is dependent on the ID number that each device is assigned.
When first powered up, when a device is added or removed from the network or in the event of noise, the network will need to be reformed.
In the formation process, each device sends a loop formation packet onto the network. The packet is identified as a loop formation packet, and contains information on the address of the sender, and size of blocks. During loop formation, the following is set up. The number of units on the network is determined, verification is made that all units have the same block size, each unit tests its address against the address of the other devices, and time slices for each device on the network are defined, that is, each device on the network calculates during what time slice it is to transmit, and what block it should be receiving during any given time slice. Each device sends a packet when it detects that the network is free. In the event there is a collision, the colliding units back off, and after a random delay, they resend their packets.
After a formation packet is sent, the sending device delays the time necessary to receive and process one packet. If a packet is received, it will again delay the time necessary to receive and process a packet. This will continue until no more packets are received. This means that all units will have time to send their packets to all other devices. After the last packet has been received, and the last time out, normal loop operation commences.
During the first loop, the transmitter waits one packet time before sending the first packet. The receivers will wait three packet times before timing out.
As mentioned above, loop formation is a function of the block size, and the number of units on the network. In general, formation time is determined by the following equation:
"Formation Time=K+Block Size (Number of Devices on the Network)"
Each device on the network sends its packet during the time slice defined during loop formation. The transmitted data is direct memory accessed out of the shared register RAM allowing the communication processor to handle necessary processing tasks such as updating the overall communication status bits.
When not transmitting data, each device waits for a packet from another device. When a packet is received, its CRC is validated, and a check is made if the sender of the packet is in the correct time slice. If the packet is totally validated, it is moved to the shared RAM.
If, during normal operation, a loop formation packet is received, the device will drop out of normal operation and go to loop formation mode.
The update time for a given installation can be determined by multiplying the block time for a single update by the actual number of units on the network.
The communication update rate is a function of the actual number of units on the network and the block size.
Ladder scans of some or all of the processors on the network can be automatically synchronized. This allows the processors to scan at the same time and facilitates parallel processing.
The serial network interface receives and transmits data over the peer-to-peer network. The data is sent in block form with CRC protection and parity protection on each block. The transmission method does not use collision detection schemes and is completely deterministic in the time domain. The serial network interface uses the shared register area (two port) as storage or the location to get messages.
The communication processor takes care of all processing required by the peer-to-peer network. It has access to the serial network interface and two port memory. It also has inputs to the setup switches. The communication processor sets up the network protocols and reports network status to the user through the two port memory.
The communication processor does most communication with the control processor through the two port memory.
Each PLC device has a bank of switches for setup. The state of the switches is read once at power up by the communication processor.
One switch is a rotary switch to set up the identification number of the device from O to F. Every device connected to the peer-to-peer network must have a unique identification number or the network will not operate properly. Labeling on the front panel allows the user to indicate the device ID number.
The other switches are arranged as follows:
1. (Bit 1-2) This code indicates the maximum number of units in the network. For fastest network formation time, the smallest possible number should be selected. All devices on the network must have the same code set up or the network will not operate properly. The code is as follows:
______________________________________
          Max. Number of Units on
Code      the Network
______________________________________
0         2
1         4
2         8
3         16
______________________________________
2. (Bit 3-4) This code indicates the block size. The block size is the number of registers sent from a device on the network to all other devices on the network. All devices on the network must have the same code or the network will not operate properly. The code is as follows:
______________________________________
Code       Size of Block (Registers)
______________________________________
0          32
1          64
2          128
3          AUTO
______________________________________
The AUTO position automatically configures the maximum number of registers possible based on the setting of the Maximum Number of Units on the Network switch. The following table describes this relationship:
______________________________________
Max. Number of Units On
The Network     Number of AUTO Register
______________________________________
2               512
4               256
8               128
16               64
______________________________________
The 1024 "shared data registers" can be arranged in any one of 4 different block size configurations. They are: 2 blocks of 512 registers, 4 blocks of 256 registers, 8 blocks of 128 registers or 16 blocks of 64 registers.
In addition to the above shared registers, the PLC device has a "peer-to-peer control register" at location 8096. This register will allow the user to configure the shared registers for the particular application. The bits in this register are dynamic in that they can be changed by the user program at any time.
Table 1 contains a map of the shared registers which are divided into 5 main sections. There are 8 control data registers, 5 spare registers, 3 miscellaneous registers, 16 communications status registers, and 1024 data registers. An explanation of the register follows:
              TABLE 1
______________________________________
SHARED REGISTERS MEMORY MAP
______________________________________
Control   8000     Error Code
Date Write
          7999     DIP Switch Image
Protected 7998     Device ID
(8)       7997     Block Size
          7996     Number of Blocks
          7995     Comm to CPU Handshake
          7994     Main-CPU Handshake
          7993     Reflectometry Counter
Share     7992     Spare
(5)       7991     Spare
          7990     Spare
          7989     Spare
          7988     Spare
Misc      7987     Count of Loop Formation
(3)       7986     Max Consecutive Block Errors
          7985     Failure Override Control
          7984     PLC Device         0
          7983                        1
          7982                        2
          7981                        3
          7980                        4
Communi-  7979                        5
cation    7978                        6
Status    7977                        7
Registers 7976                        8
(16)      7975                        9
          7974                        10
          7973                        11
          7972                        12
          7971                        13
          7970                        14
          7969                        15
Data      7968     Shared Data
Registers 7968     Shared Data
(1024)    7968     Shared Data
          6945     Shared Data
______________________________________
Error Code (8000)
If the communication processor detects an error, it will post an error code in this register.
The following error codes are supported:
______________________________________
Code    Meaning
______________________________________
A    O      No error
B    1      Address Error
C    2      Bus Error
D    3      Parity Error
E    4      Handshake Failure
F    S      Main Processor Failure
G    6      PROM Checksum Test Failure
H    7      Local RAM Read After Write Test Failure
I    8      Local RAM Destructive Test Failure
3    9      Share RAM Read After Write Test Failure
K    10     Shared RAM Destructive Test Failure
L    11     Local Area Network Controller Test Failure
M    12     Shared Register Block Exceeds 1024 Registers
N    13     Incorrect Block Size Received
O    14     Address greater than Number of Devices on the Network
P    15     Duplicate Address Detected
Q    16     Block Error Limit Exceeded
______________________________________
The Dip Switch Image (7999) register contains an image of the peer-to-peer dip switch. The user can read this register to find out how the dip switch is set without removing the device from the rack. The communication processor writes the data to this location.
The Device ID (7998) register contains the ID code assigned to this unit. The communication processor decodes the ID code from the dip switch settings and places it here.
The Block Size (7997) register contains the peer-to-peer block size. The communication processor decodes the block size. The communication processor decodes the block size from the dip switch settings and places it here.
The Number of Blocks (7996) register contains the maximum number of blocks transferred by the peer-to-peer network. The communication processor decodes the maximum number of blocks from the dip switch setting and places it here.
The Comms to CPU Handshake (7995) is an internal register used by communication processor to handshake with the control processor.
The Main CPU Handshake (7994) is an internal register used by control processor to handshake with the communication processor.
The Time Domain Reflectometry Counter (7993) counts proportional to the length of the cable. A counter is started when a transmission is started from a unit. Reflections from the cable end terminate the count. The value should be constant for a given installation and device on the network. It has a value as a trouble shooting tool.
Spare Registers for Future Expansion (7992-7988) are registers reserved for future expansion.
During power up and conditions of extraordinary network disturbances, the network may be automatically reformed. The Count of Loop Formations (7987) register contains a count of the number of times the network has been reformed. The Maximum Consecutive Block Errors (7986) register is programmed by the user to indicate the maximum number of consecutive block errors before the system automatically generates an error and goes to HALT.
When the bits in the Failure Override Control (7985) registers are zero, the PLC will generate an error if the communication processor detects (n) consecutive errors in a row where (n) is determined by the contents of the previous maximum consecutive block errors. If a bit is set to one, the error will not be generated. Bit 1 corresponds to PLC device 1, Bit 2 to PLC device 2 and so on, up to PLC device 15.
The Communication Status Registers (CSR) (7984-7969) are written to by the communication processor to give the status of individual communication channels. There is one register for each communications register.
While the invention has been described with reference to a preferred embodiment, it will be understood by those skilled in the art that various changes may be made and equivalents may be substituted for elements thereof without departing from the broader aspects of the invention. Also, it is intended that broad claims not specifying details of a particular embodiment disclosed herein as the best mode contemplated for carrying out the invention should not be limited to such details.

Claims (13)

We claim:
1. A peer-to-peer communications network for high speed transfer of data between devices comprising in combination:
a communications . .network.!. .Iadd.bus.Iaddend.;
at least two programmable logic controllers (PLC's) connected to communicate with said . .network.!. .Iadd.communications bus.Iaddend., each of said PLC's including a control processor for sequentially performing a series of instructions, a multi-port image memory . .coupled between said control processor and said communications network and.!. having a plurality of blocks, a first one of said plurality of blocks corresponding to its respective one of said PLC's, the other of said plurality of blocks corresponding to respective ones of the others of said . .PLS's.!. .Iadd.PLCs.Iaddend., an input/output device, means for storing status data representing a status of said input/output device in said first one of said blocks; and
means for transferring said input/output status from each of said first ones of said blocks of said respective multi-port image memories to said respective blocks of said other of said multi-port image memories of said other PLC's independent of operation of said control processors and.Iadd.,
wherein said multi-port image memory of each of said at least two PLCs is coupled between said control processor of each of said at least two PLCs and said means for transferring said input/output status.Iaddend..
2. The peer-to-peer communications network of claim 1, wherein each of said .Iadd.respective .Iaddend.multi-port .Iadd.image .Iaddend.memories comprise registers containing transferable data which is transferable between the others of said multi-port memories.
3. The peer-to-peer communications network of claim 2, wherein each of said blocks includes a plurality of registers and the size of the registers containing data being transferred from one of said .Iadd.respective .Iaddend.multi-port .Iadd.image .Iaddend.memories to the other of said multi-port memories matches the size of said registers to which they are being transferred.
4. The peer-to-peer communications network of claim 3, wherein each of said registers has an address including a first PLC ID number and a second, mailbox number, and the mailbox numbers of the blocks of registers are identical.
5. The peer-to-peer communications network of claim 1, wherein each of said PLC's includes a dedicated communications processor to coordinate the transfer of data between the respective blocks.
6. The peer-to-peer communications network of claim 1, including between 2 to 16 PLC's.
7. The peer-to-peer communications network of claim 1 wherein each of said plurality of control processors can be selectively connected to a common communication bus.
8. A peer-to-peer communications network for high speed transfer of data comprising:
a communications . .network.!. .Iadd.bus.Iaddend.;
a first programmable logic controller (PLC) communicatively coupled to said . .network.!. .Iadd.bus.Iaddend., said first PLC including a first control processor for sequentially performing a series of instructions, a first input/output device, a first multi-port image memory . .coupled between said first control processor and said communications network bus and.!. having a plurality of first memory blocks, a first one of said first memory blocks corresponding to said first PLC, and means for storing status data representing a status of said first input/output device in said first one of said first memory blocks;
a second programmable logic controller (PLC) communicatively coupled to said . .network.!. .Iadd.bus.Iaddend., said second PLC including a second control processor for sequentially performing a series of instructions, a second input/output device, a second multi-port image memory . .coupled between said second control processor and said communications network and.!. having a plurality of second memory blocks, a second one of said second memory blocks corresponding to said second PLC, means for storing status data representing a status of said second input/output device in said first one of said second memory blocks; and
means for transferring said data in said first one of said first memory blocks into said first one of said second memory blocks and for transferring said data in said second one of said second memory blocks into said second one of said first memory blocks independent of operation of said control processors.Iadd., said multi-port image memory of each of said at least two PLCs further being coupled between said control processor of each of said at least two PLCs and said means for transferring said input/output status.Iaddend..
9. The peer-to-peer communications network of claim 8, wherein each of said first and second memory blocks includes a plurality of registers, and the size of the registers containing data being transferred from one . .of said.!. multi-port . .memories.!. .Iadd.image memory .Iaddend.to . .the other of said.!. .Iadd.another .Iaddend.multi-port . .memories.!. .Iadd.image memory .Iaddend.matches the size of said registers to which they are being transferred.
10. The peer-to-peer communications network of claim 8 wherein each of said registers has an address including a first, PLC ID number and a second, mailbox number, and the mailbox numbers of the blocks of registers are identical.
11. The peer-to-peer communications network of claim 8, wherein each of said first and second PLC's includes a dedicated communications processor to coordinate the transfer of data between the respective blocks.
12. The peer-to-peer communications network of claim 8, including between 2 to 16 PLC's.
13. The peer-to-peer communications network of claim 8 wherein each of said first and second control processors can be selectively connected to a common communication bus.
US08/645,606 1988-04-11 1996-05-14 Peer-to-peer register exchange controller for PLCS Expired - Lifetime USRE36263E (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US08/645,606 USRE36263E (en) 1988-04-11 1996-05-14 Peer-to-peer register exchange controller for PLCS

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US07/179,674 US4897777A (en) 1988-04-11 1988-04-11 Peer-to-peer register exchange controller for PLCS
US08/645,606 USRE36263E (en) 1988-04-11 1996-05-14 Peer-to-peer register exchange controller for PLCS

Related Parent Applications (1)

Application Number Title Priority Date Filing Date
US07/179,674 Reissue US4897777A (en) 1988-04-11 1988-04-11 Peer-to-peer register exchange controller for PLCS

Publications (1)

Publication Number Publication Date
USRE36263E true USRE36263E (en) 1999-08-03

Family

ID=22657519

Family Applications (2)

Application Number Title Priority Date Filing Date
US07/179,674 Ceased US4897777A (en) 1988-04-11 1988-04-11 Peer-to-peer register exchange controller for PLCS
US08/645,606 Expired - Lifetime USRE36263E (en) 1988-04-11 1996-05-14 Peer-to-peer register exchange controller for PLCS

Family Applications Before (1)

Application Number Title Priority Date Filing Date
US07/179,674 Ceased US4897777A (en) 1988-04-11 1988-04-11 Peer-to-peer register exchange controller for PLCS

Country Status (11)

Country Link
US (2) US4897777A (en)
EP (1) EP0365673B1 (en)
JP (1) JPH03500703A (en)
KR (1) KR0154857B1 (en)
AU (1) AU626880B2 (en)
BR (1) BR8906814A (en)
CA (1) CA1325683C (en)
DE (1) DE68928121T2 (en)
DK (1) DK618989A (en)
MX (1) MX169856B (en)
WO (1) WO1989009974A1 (en)

Cited By (17)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6169928B1 (en) * 1998-06-30 2001-01-02 Ge Fanuc Automation North America, Inc. Apparatus and method for sharing data among a plurality of control devices on a communications network
US6424872B1 (en) 1996-08-23 2002-07-23 Fieldbus Foundation Block oriented control system
US20030004987A1 (en) * 1996-08-23 2003-01-02 Glanzer David A. Integrated fieldbus data server architecture
US6826590B1 (en) 1996-08-23 2004-11-30 Fieldbus Foundation Block-oriented control system on high speed ethernet
US20050015001A1 (en) * 2003-04-16 2005-01-20 Lec Ryszard M. Acoustic blood analyzer for assessing blood properties
US6938111B2 (en) * 2002-04-19 2005-08-30 Siemens Aktiengesellschaft Method for operating automation control equipment applications
US20050256939A1 (en) * 2004-05-03 2005-11-17 Schneider Automation Sas Automatic Configuration of Network Automation Devices
US20060025872A1 (en) * 1997-08-21 2006-02-02 Glanzer David A System and method for implementing safety instrumented systems in a fieldbus architecture
US20060206218A1 (en) * 1996-08-23 2006-09-14 Glanzer David A Flexible Function Blocks
US20070101178A1 (en) * 2005-10-27 2007-05-03 General Electric Company Automatic remote monitoring and diagnostics system and communication method for communicating between a programmable logic controller and a central unit
US20070142939A1 (en) * 2005-12-20 2007-06-21 Fieldbus Foundation System and method for implementing time synchronization monitoring and detection in a safety instrumented system
US20070142934A1 (en) * 2005-12-20 2007-06-21 Fieldbus Foundation System and method for implementing an extended safety instrumented system
WO2008049753A1 (en) * 2006-10-25 2008-05-02 Endress+Hauser Gmbh+Co.Kg Process automation system for determining, for monitoring and/or for influencing different process variables and/or state variables
US20090302588A1 (en) * 2008-06-05 2009-12-10 Autoliv Asp, Inc. Systems and methods for airbag tether release
US20100011356A1 (en) * 2008-07-10 2010-01-14 Electrowave Usa, Inc. Intelligent distributed controller
US20110077749A1 (en) * 2009-09-30 2011-03-31 General Electric Company Multi-processor based programmable logic controller and method for operating the same
CN102540954A (en) * 2010-12-24 2012-07-04 深圳市合信自动化技术有限公司 Programmable logic controller and control method thereof

Families Citing this family (75)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5251302A (en) * 1988-04-11 1993-10-05 Square D Company Network interface board having memory mapped mailbox registers including alarm registers for storing prioritized alarm messages from programmable logic controllers
US5131092A (en) * 1989-09-01 1992-07-14 Square D Company Communication system enabling programmable logic controllers access to host computer tasks and host computer access to programmable logic controllers without polling
US5245704A (en) * 1990-03-22 1993-09-14 Square D Company System for sharing data between microprocessor based devices
DE4207826C2 (en) * 1992-03-12 1995-06-14 Deutsche Aerospace Path and attitude control system (AOCS) with test system
EP0810499B1 (en) * 1992-06-12 2001-10-17 The Dow Chemical Company Secure front end communication system and method for process control computers
AU4400793A (en) * 1992-06-12 1994-01-04 Dow Chemical Company, The Intelligent process control communication system and method
JP2590045B2 (en) * 1994-02-16 1997-03-12 日本アイ・ビー・エム株式会社 Distributed processing control method and distributed processing system
JP3481308B2 (en) * 1994-07-12 2003-12-22 富士通株式会社 Interface device, data transfer system and data transfer method
US5764155A (en) * 1996-04-03 1998-06-09 General Electric Company Dynamic data exchange server
US5805442A (en) * 1996-05-30 1998-09-08 Control Technology Corporation Distributed interface architecture for programmable industrial control systems
US7146408B1 (en) 1996-05-30 2006-12-05 Schneider Automation Inc. Method and system for monitoring a controller and displaying data from the controller in a format provided by the controller
EP0825506B1 (en) 1996-08-20 2013-03-06 Invensys Systems, Inc. Methods and apparatus for remote process control
CN1182818C (en) * 1996-08-29 2005-01-05 博士伦外科公司 Dual loop frequency and power control
US7058693B1 (en) 1997-09-10 2006-06-06 Schneider Automation Inc. System for programming a programmable logic controller using a web browser
US7035898B1 (en) 1997-09-10 2006-04-25 Schneider Automation Inc. System for programming a factory automation device using a web browser
US20020091784A1 (en) * 1997-09-10 2002-07-11 Baker Richard A. Web interface to a device and an electrical network control system
US6282454B1 (en) 1997-09-10 2001-08-28 Schneider Automation Inc. Web interface to a programmable controller
US20020152289A1 (en) * 1997-09-10 2002-10-17 Schneider Automation Inc. System and method for accessing devices in a factory automation network
US6732191B1 (en) 1997-09-10 2004-05-04 Schneider Automation Inc. Web interface to an input/output device
US7162510B2 (en) * 1998-03-16 2007-01-09 Schneider Automation Inc. Communication system for a control system over Ethernet and IP networks
US6233626B1 (en) 1998-10-06 2001-05-15 Schneider Automation Inc. System for a modular terminal input/output interface for communicating messaging application layer over encoded ethernet to transport layer
US6434157B1 (en) 1998-10-06 2002-08-13 Schneider Automation, Inc. MODBUS plus ethernet bridge
US6327511B1 (en) 1998-12-30 2001-12-04 Schneider Automation, Inc. Input/output (I/O) scanner for a control system with peer determination
US6853867B1 (en) 1998-12-30 2005-02-08 Schneider Automation Inc. Interface to a programmable logic controller
US6845401B1 (en) 1998-12-30 2005-01-18 Schneider Automation Inc. Embedded file system for a programmable logic controller
US6754885B1 (en) 1999-05-17 2004-06-22 Invensys Systems, Inc. Methods and apparatus for controlling object appearance in a process control configuration system
US7272815B1 (en) 1999-05-17 2007-09-18 Invensys Systems, Inc. Methods and apparatus for control configuration with versioning, security, composite blocks, edit selection, object swapping, formulaic values and other aspects
US7096465B1 (en) 1999-05-17 2006-08-22 Invensys Systems, Inc. Process control configuration system with parameterized objects
WO2000070531A2 (en) * 1999-05-17 2000-11-23 The Foxboro Company Methods and apparatus for control configuration
US7089530B1 (en) * 1999-05-17 2006-08-08 Invensys Systems, Inc. Process control configuration system with connection validation and configuration
US6978294B1 (en) 2000-03-20 2005-12-20 Invensys Systems, Inc. Peer-to-peer hosting of intelligent field devices
US6501995B1 (en) 1999-06-30 2002-12-31 The Foxboro Company Process control system and method with improved distribution, installation and validation of components
US6788980B1 (en) * 1999-06-11 2004-09-07 Invensys Systems, Inc. Methods and apparatus for control using control devices that provide a virtual machine environment and that communicate via an IP network
AU6615600A (en) 1999-07-29 2001-02-19 Foxboro Company, The Methods and apparatus for object-based process control
US6473660B1 (en) 1999-12-03 2002-10-29 The Foxboro Company Process control system and method with automatic fault avoidance
US7519737B2 (en) * 2000-07-07 2009-04-14 Schneider Automation Inc. Input/output (I/O) scanner for a control system with peer determination
US7032029B1 (en) 2000-07-07 2006-04-18 Schneider Automation Inc. Method and apparatus for an active standby control system on a network
US7181487B1 (en) 2000-07-07 2007-02-20 Schneider Automation Inc. Method and system for transmitting and activating an application requesting human intervention in an automation network
US7028204B2 (en) * 2000-09-06 2006-04-11 Schneider Automation Inc. Method and apparatus for ethernet prioritized device clock synchronization
US20020167967A1 (en) * 2000-09-06 2002-11-14 Schneider Electric Method for managing bandwidth on an ethernet network
US7023795B1 (en) 2000-11-07 2006-04-04 Schneider Automation Inc. Method and apparatus for an active standby control system on a network
US10173008B2 (en) 2002-01-29 2019-01-08 Baxter International Inc. System and method for communicating with a dialysis machine through a network
US20030204419A1 (en) * 2002-04-30 2003-10-30 Wilkes Gordon J. Automated messaging center system and method for use with a healthcare system
US8775196B2 (en) * 2002-01-29 2014-07-08 Baxter International Inc. System and method for notification and escalation of medical data
US20030140928A1 (en) * 2002-01-29 2003-07-31 Tuan Bui Medical treatment verification system and method
EP1502218A4 (en) * 2002-04-15 2005-08-17 Invensys Sys Inc Methods and apparatus for process, factory-floor, environmental, computer aided manufacturing-based or other control system with real-time data distribution
US20040167804A1 (en) * 2002-04-30 2004-08-26 Simpson Thomas L.C. Medical data communication notification and messaging system and method
US20030201697A1 (en) * 2002-04-30 2003-10-30 Richardson William R. Storage device for health care facility
US20040172300A1 (en) * 2002-04-30 2004-09-02 Mihai Dan M. Method and system for integrating data flows
US20040172301A1 (en) * 2002-04-30 2004-09-02 Mihai Dan M. Remote multi-purpose user interface for a healthcare system
US20040176667A1 (en) * 2002-04-30 2004-09-09 Mihai Dan M. Method and system for medical device connectivity
US8234128B2 (en) 2002-04-30 2012-07-31 Baxter International, Inc. System and method for verifying medical device operational parameters
US20030225596A1 (en) * 2002-05-31 2003-12-04 Richardson Bill R. Biometric security for access to a storage device for a healthcare facility
US20040210664A1 (en) * 2003-04-17 2004-10-21 Schneider Automation Inc. System and method for transmitting data
US7761923B2 (en) * 2004-03-01 2010-07-20 Invensys Systems, Inc. Process control methods and apparatus for intrusion detection, protection and network hardening
US7130196B2 (en) * 2005-01-19 2006-10-31 General Electric Company Apparatus and method for transferring heat from control devices
JP4722613B2 (en) * 2005-08-02 2011-07-13 株式会社ジェイテクト Distributed control system
US7860857B2 (en) 2006-03-30 2010-12-28 Invensys Systems, Inc. Digital data processing apparatus and methods for improving plant performance
EP2304536A4 (en) 2008-06-20 2012-08-15 Invensys Sys Inc Systems and methods for immersive interaction with actual and/or simulated facilities for process, environmental and industrial control
US8057679B2 (en) 2008-07-09 2011-11-15 Baxter International Inc. Dialysis system having trending and alert generation
US10089443B2 (en) 2012-05-15 2018-10-02 Baxter International Inc. Home medical device systems and methods for therapy prescription and tracking, servicing and inventory
US8554579B2 (en) 2008-10-13 2013-10-08 Fht, Inc. Management, reporting and benchmarking of medication preparation
US8463964B2 (en) * 2009-05-29 2013-06-11 Invensys Systems, Inc. Methods and apparatus for control configuration with enhanced change-tracking
US8127060B2 (en) * 2009-05-29 2012-02-28 Invensys Systems, Inc Methods and apparatus for control configuration with control objects that are fieldbus protocol-aware
JP5735711B2 (en) * 2012-06-26 2015-06-17 東芝三菱電機産業システム株式会社 Data collection device and data collection program
BR112015003914A2 (en) 2012-08-31 2019-11-19 Baxter Corp Englewood systems for executing a medication request and for managing medication request, and method for executing a medication request
CA2889210C (en) 2012-10-26 2020-12-15 Baxter Corporation Englewood Improved image acquisition for medical dose preparation system
NZ707430A (en) 2012-10-26 2016-04-29 Baxter Corp Englewood Improved work station for medical dose preparation system
CA2953392A1 (en) 2014-06-30 2016-01-07 Baxter Corporation Englewood Managed medical information exchange
US11107574B2 (en) 2014-09-30 2021-08-31 Baxter Corporation Englewood Management of medication preparation with formulary management
US11575673B2 (en) 2014-09-30 2023-02-07 Baxter Corporation Englewood Central user management in a distributed healthcare information management system
JP2018503180A (en) 2014-12-05 2018-02-01 バクスター・コーポレーション・イングルウッドBaxter Corporation Englewood Dose preparation data analysis
EP3314488A1 (en) 2015-06-25 2018-05-02 Gambro Lundia AB Medical device system and method having a distributed database
CN110100283B (en) 2016-12-21 2023-07-04 甘布罗伦迪亚股份公司 Medical device system including information technology infrastructure with secure cluster domain supporting external domain
JP7276265B2 (en) * 2020-06-30 2023-05-18 株式会社安川電機 Production system, host control device, control device, communication method, and program

Citations (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US4253148A (en) * 1979-05-08 1981-02-24 Forney Engineering Company Distributed single board computer industrial control system
US4304001A (en) * 1980-01-24 1981-12-01 Forney Engineering Company Industrial control system with interconnected remotely located computer control units
US4459655A (en) * 1980-03-27 1984-07-10 Willemin Machines S.A. Control system for a machine or for an installation
US4486856A (en) * 1982-05-10 1984-12-04 Teletype Corporation Cache memory and control circuit
US4550366A (en) * 1981-10-17 1985-10-29 Toshiba Kikai Kabushiki Kaisha Programmable sequence controller and system
US4607256A (en) * 1983-10-07 1986-08-19 Honeywell, Inc. Plant management system
US4608661A (en) * 1981-11-16 1986-08-26 Toshiba Kikai Kabushiki Kaisha Programmable sequence controller
EP0200365A2 (en) * 1985-04-03 1986-11-05 Siemens Aktiengesellschaft System and method for controlling network bus communications for tightly coupled information among distributed programmable controllers
US4718039A (en) * 1984-06-29 1988-01-05 International Business Machines Intermediate memory array with a parallel port and a buffered serial port
US4754427A (en) * 1985-01-11 1988-06-28 Toshiba Kikai Kabushiki Kaisha Linking system for programmable controller

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JPS60217446A (en) * 1984-04-13 1985-10-31 Hitachi Ltd High speed programmable logic controller

Patent Citations (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US4253148A (en) * 1979-05-08 1981-02-24 Forney Engineering Company Distributed single board computer industrial control system
US4304001A (en) * 1980-01-24 1981-12-01 Forney Engineering Company Industrial control system with interconnected remotely located computer control units
US4459655A (en) * 1980-03-27 1984-07-10 Willemin Machines S.A. Control system for a machine or for an installation
US4550366A (en) * 1981-10-17 1985-10-29 Toshiba Kikai Kabushiki Kaisha Programmable sequence controller and system
US4608661A (en) * 1981-11-16 1986-08-26 Toshiba Kikai Kabushiki Kaisha Programmable sequence controller
US4486856A (en) * 1982-05-10 1984-12-04 Teletype Corporation Cache memory and control circuit
US4607256A (en) * 1983-10-07 1986-08-19 Honeywell, Inc. Plant management system
US4718039A (en) * 1984-06-29 1988-01-05 International Business Machines Intermediate memory array with a parallel port and a buffered serial port
US4754427A (en) * 1985-01-11 1988-06-28 Toshiba Kikai Kabushiki Kaisha Linking system for programmable controller
EP0200365A2 (en) * 1985-04-03 1986-11-05 Siemens Aktiengesellschaft System and method for controlling network bus communications for tightly coupled information among distributed programmable controllers

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
Patent Abstracts of Japan, vol. 10, No. 80 (P 441) (2137) Mar. 29, 1986. *
Patent Abstracts of Japan, vol. 10, No. 80 (P-441) (2137) Mar. 29, 1986.

Cited By (37)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20080004727A1 (en) * 1996-08-23 2008-01-03 Fieldbus Foundation Flexible function blocks
US20060206218A1 (en) * 1996-08-23 2006-09-14 Glanzer David A Flexible Function Blocks
US20030004987A1 (en) * 1996-08-23 2003-01-02 Glanzer David A. Integrated fieldbus data server architecture
US6424872B1 (en) 1996-08-23 2002-07-23 Fieldbus Foundation Block oriented control system
US6826590B1 (en) 1996-08-23 2004-11-30 Fieldbus Foundation Block-oriented control system on high speed ethernet
US7272457B2 (en) 1996-08-23 2007-09-18 Fieldbus Foundation Flexible function blocks
US20050240287A1 (en) * 1996-08-23 2005-10-27 Glanzer David A Block-oriented control system on high speed ethernet
US20070129820A1 (en) * 1996-08-23 2007-06-07 Glanzer David A Integrated fieldbus data server architecture
US7146230B2 (en) 1996-08-23 2006-12-05 Fieldbus Foundation Integrated fieldbus data server architecture
US7167762B2 (en) 1997-08-21 2007-01-23 Fieldbus Foundation System and method for implementing safety instrumented systems in a fieldbus architecture
US20060025872A1 (en) * 1997-08-21 2006-02-02 Glanzer David A System and method for implementing safety instrumented systems in a fieldbus architecture
US20070213853A1 (en) * 1997-08-21 2007-09-13 Fieldbus Foundation System and method for implementing safety instrumented systems in a fieldbus architecture
US7486999B2 (en) 1997-08-21 2009-02-03 Fieldbus Foundation System and method for implementing safety instrumented systems in a fieldbus architecture
US6169928B1 (en) * 1998-06-30 2001-01-02 Ge Fanuc Automation North America, Inc. Apparatus and method for sharing data among a plurality of control devices on a communications network
US6938111B2 (en) * 2002-04-19 2005-08-30 Siemens Aktiengesellschaft Method for operating automation control equipment applications
US7857761B2 (en) 2003-04-16 2010-12-28 Drexel University Acoustic blood analyzer for assessing blood properties
US20050015001A1 (en) * 2003-04-16 2005-01-20 Lec Ryszard M. Acoustic blood analyzer for assessing blood properties
US20050256939A1 (en) * 2004-05-03 2005-11-17 Schneider Automation Sas Automatic Configuration of Network Automation Devices
US7720639B2 (en) * 2005-10-27 2010-05-18 General Electric Company Automatic remote monitoring and diagnostics system and communication method for communicating between a programmable logic controller and a central unit
US20070101178A1 (en) * 2005-10-27 2007-05-03 General Electric Company Automatic remote monitoring and diagnostics system and communication method for communicating between a programmable logic controller and a central unit
US8126679B2 (en) 2005-10-27 2012-02-28 General Electric Company Automatic remote monitoring and diagnostics system
US20100235142A1 (en) * 2005-10-27 2010-09-16 Vinay Bhaskar Jammu Automatic remote monitoring and diagnostics system
US8676357B2 (en) 2005-12-20 2014-03-18 Fieldbus Foundation System and method for implementing an extended safety instrumented system
US7489977B2 (en) 2005-12-20 2009-02-10 Fieldbus Foundation System and method for implementing time synchronization monitoring and detection in a safety instrumented system
US20070142939A1 (en) * 2005-12-20 2007-06-21 Fieldbus Foundation System and method for implementing time synchronization monitoring and detection in a safety instrumented system
US20070142934A1 (en) * 2005-12-20 2007-06-21 Fieldbus Foundation System and method for implementing an extended safety instrumented system
CN101529352B (en) * 2006-10-25 2012-09-05 恩德莱斯和豪瑟尔两合公司 Process automation system for determining, for monitoring and/or for influencing different process variables and/or state variables
US20100145493A1 (en) * 2006-10-25 2010-06-10 Endress + Hauser Gmbh + Co Kg Process automation system for determining, monitoring and/or influencing different process variables and/or state variables
US8311651B2 (en) 2006-10-25 2012-11-13 Endress + Hauser Gmbh + Co. Kg Process automation system for determining, monitoring and/or influencing different process variables and/or state variables
WO2008049753A1 (en) * 2006-10-25 2008-05-02 Endress+Hauser Gmbh+Co.Kg Process automation system for determining, for monitoring and/or for influencing different process variables and/or state variables
US20090302588A1 (en) * 2008-06-05 2009-12-10 Autoliv Asp, Inc. Systems and methods for airbag tether release
US20100011356A1 (en) * 2008-07-10 2010-01-14 Electrowave Usa, Inc. Intelligent distributed controller
US20110077749A1 (en) * 2009-09-30 2011-03-31 General Electric Company Multi-processor based programmable logic controller and method for operating the same
WO2011041150A1 (en) * 2009-09-30 2011-04-07 General Electric Company Multi-processor based programmable logic controller and method for operating the same
US8347044B2 (en) 2009-09-30 2013-01-01 General Electric Company Multi-processor based programmable logic controller and method for operating the same
CN102540954A (en) * 2010-12-24 2012-07-04 深圳市合信自动化技术有限公司 Programmable logic controller and control method thereof
CN102540954B (en) * 2010-12-24 2015-03-11 深圳市合信自动化技术有限公司 Programmable logic controller and control method thereof

Also Published As

Publication number Publication date
KR0154857B1 (en) 1998-11-16
CA1325683C (en) 1993-12-28
WO1989009974A1 (en) 1989-10-19
DE68928121D1 (en) 1997-07-17
EP0365673A1 (en) 1990-05-02
EP0365673B1 (en) 1997-06-11
DK618989D0 (en) 1989-12-08
US4897777A (en) 1990-01-30
BR8906814A (en) 1990-11-13
DK618989A (en) 1990-02-08
MX169856B (en) 1993-07-28
KR900700968A (en) 1990-08-17
DE68928121T2 (en) 1997-12-11
AU626880B2 (en) 1992-08-13
JPH03500703A (en) 1991-02-14
EP0365673A4 (en) 1992-11-04
AU3688489A (en) 1989-11-03

Similar Documents

Publication Publication Date Title
USRE36263E (en) Peer-to-peer register exchange controller for PLCS
US4992926A (en) Peer-to-peer register exchange controller for industrial programmable controllers
US4809217A (en) Remote I/O port for transfer of I/O data in a programmable controller
EP0427502A2 (en) Programmable logic controllers
US5012468A (en) Master slave industrial token passing network
US5283869A (en) Interrupt structure for network interface circuit
EP3547049B1 (en) Safety control system and safety control unit
US11398919B2 (en) Method for detecting network subscribers in an automation network and automation network
US5847659A (en) Electronic wiring system using automatic cyclic, communication means
EP1255375B1 (en) Plural station memory data sharing system
US6970961B1 (en) Reliable and redundant control signals in a multi-master system
JPH02100538A (en) Data communication method for local area network
KR920001859B1 (en) Time switch control memory device
JP2002015968A (en) Automatic recognition method for input/output board of semiconductor manufacturing apparatus, and semiconductor manufacturing device
JP3505540B2 (en) Data transfer device
JPS6365509A (en) Data transmission equipment for numerical controller
EP0076494A2 (en) Data transmission bus system for a plurality of processors
KR200218315Y1 (en) I/O interfacing system of power plant simulator
KR0174652B1 (en) Method and apparatus for data transmission in burst mode multiple monitoring method
KR100724881B1 (en) Switching system for implementing line access unit switching and control method thereof
JP2998186B2 (en) Data transfer device
JPH11296211A (en) Input/output device
JPH09135260A (en) Hierarchical method for programmable logic controller by network
JPH1155346A (en) Communication equipment between program logic controller with different communication program
JPS58197538A (en) Terminal controller

Legal Events

Date Code Title Description
AS Assignment

Owner name: SCHNEIDER AUTOMATION, INC., MASSACHUSETTS

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:AEG SCHNEIDER AUTOMATION, INC.;REEL/FRAME:008649/0310

Effective date: 19970718

AS Assignment

Owner name: SCHNEIDER AUTOMATION INC., MASSACHUSETTS

Free format text: CHANGE OF NAME;ASSIGNOR:AEG SCHNEIDER AUTOMATION, INC.;REEL/FRAME:008855/0799

Effective date: 19960801

FPAY Fee payment

Year of fee payment: 12