`Dube' et al.
`
`USOO6434157B1
`(10) Patent No.:
`US 6,434,157 B1
`(45) Date of Patent:
`Aug. 13, 2002
`
`(54)
`(75)
`
`(73)
`
`(21)
`(22)
`(51)
`(52)
`(58)
`(56)
`
`MODBUS PLUS ETHERNET BRIDGE
`
`Inventors: Denis W. Dube, Pelham; Andrew G.
`Swales, Windham, both of NH (US);
`Cynthia Davies, Lowell, MA (US)
`Assignee: Schneider Automation, Inc., North
`Andover, MA (US)
`Subject to any disclaimer, the term of this
`patent is extended or adjusted under 35
`U.S.C. 154(b) by 0 days.
`
`Notice:
`
`Appl. No.: 09/167,251
`Filed:
`Oct. 6, 1998
`Int. Cl................................................. H04L 12/28
`U.S. Cl. ........................................ 370/401; 370/402
`Field of Search .................................. 370/401-405
`
`References Cited
`
`U.S. PATENT DOCUMENTS
`
`3,971,000 A 7/1976 Cromwell
`4,319.338 A 3/1982 Grudowski et al.
`4,688,167 A 8/1987 Agarwal
`4,845,644 A 7/1989 Anthias et al.
`4,858,152 A 8/1989 Estes
`4,897,777 A
`1/1990 Janke et al.
`4.912,623 A 3/1990 Rantala et al.
`4.937,777 A
`6/1990 Flood et al.
`4,949.274 A 8/1990 Hollander et al.
`4,953,074 A 8/1990 Kametani et al.
`4992,926 A 2/1991 Janke et al.
`(List continued on next page.)
`FOREIGN PATENT DOCUMENTS
`
`DE
`DE
`DE
`EP
`EP
`WO
`WO
`
`3/1997
`296 OO 609 U1
`4/1997
`441 0171 C1
`196 15 093 A1 10/1997
`O 542 657 A1
`5/1993
`O 814 393 A1 12/1997
`WO 97/18636
`5/1997
`WO 98/53581
`11/1998
`
`THERNE
`
`OTHER PUBLICATIONS
`Groupe Schneider, Modicon Modibus Plus Network BM85
`Bridge Multiplexer User's Guide, Aug. 1995.*
`When Technology Standards Become Counterproductive,
`Kenneth C. Crater, President, Control Technology Corpora
`tion, Hopkinton, MA dated Jul. 9, 1999, pp. 1-5.
`A White Paper State Language for Machine Control, Ken
`neth C. Crater, President, Control Technology Corporation,
`Hopkinton, MA dated Jul. 9, 1999, pp. 1-11.
`New PC-based Process Control & Data Acquisition Soft
`ware Integrates Remote Internet Capabilities with Fast Pen
`tium Support, Fred A. Putnam, LabTech President, pp. 1-3.
`Aug. 1996 Control Magazine-In The News-Electric Util
`ity Industry Embarks on Automation Overhaul, pp. 1-10.
`Jul. 1997 Control Magazine-Magazine Software
`Review-NT Package Give Plant Access Through the Web,
`pp. 1-3.
`Oct. 1996 Control Magazine-Software Review-Article
`Archives, pp. 1-2.
`(List continued on next page.)
`Primary Examiner Melvin Marcelo
`ASSistant Examiner Ron Abelson
`(74) Attorney, Agent, or Firm Michael J. Femal; Larry I.
`Golden
`ABSTRACT
`(57)
`A bridge is disclosed for providing a connection between a
`MODBUS Plus network and an Ethernet network. The
`bridge includes a MODBUS circuit board, an Ethernet
`circuit board, and a CPU. The MODBUS circuit board is
`operably coupled to the local area network for receiving a
`message from an originating node having a five-byte routing
`path field. The CPU is operably connected to the circuit
`board for extracting a table location in response to a third
`byte within the routing path field. The Ethernet circuit board
`is operably connected to the CPU and the Ethernet network
`for forwarding the message to an IP destination in response
`to the table location.
`
`26 Claims, 12 Drawing Sheets
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`TCPip
`NTERFACE
`
`BRIDGE
`8 DATA PATHS
`8 PROGRAM PATHS
`
`MODBUS PUS
`NTERFACE
`
`18
`
`10
`
`16
`
`MODEUSPLUS
`
`
`
`
`
`MOBUS PUS
`BRIDGE
`
`ADDITIONAL
`MODBUS PLUS
`NETWORKS
`
`Page 1 of 21
`
`
`
`US 6,434,157 B1
`Page 2
`
`U.S. PATENT DOCUMENTS
`5,012.402 A
`4/1991 Akiyama
`5,023,770 A
`6/1991 Siverling
`5,047,959 A
`9/1991 Phillips et al.
`5,072,356 A 12/1991 Watt et al.
`5,072,412 A 12/1991 Henderson, Jr. et al.
`5,109,487 A 4/1992 Ohgomori et al.
`5,122,948 A
`6/1992 Zapolin
`5,131,092 A 7/1992 Sackmann et al.
`5,134,574 A 7/1992 Beaverstock et al.
`5,151,896 A 9/1992 Bowman et al.
`5,151,978 A 9/1992 Bronikowski
`5,157,595 A 10/1992 Lovrenich
`5,159,673 A 10/1992 Sackmann et al.
`5,161,211 A 11/1992 Taguchi et al.
`5,165,030 A 11/1992 Barker
`5,179,700 A
`1/1993 Aihara et al.
`5,225.974 A 7/1993 Mathews et al.
`5.245,704 A 9/1993 Weber et al.
`5,251,302 A 10/1993 Weigl et al.
`5,283,861 A 2/1994 Dangler et al.
`5,297.257 A
`3/1994 Struger et al.
`5,307.463 A
`4/1994 Hyatt et al.
`5,321,829. A 6/1994 Zifferer
`5,349,675 A 9/1994 Fitzgerald et al.
`5,398.336 A 3/1995 Tantry et al.
`5,406,473 A 4/1995 Yoshikura et al.
`5,420,977 A 5/1995 Sztipanovits et al.
`5,440,699 A 8/1995 Farrand et al.
`5,446,868 A 8/1995 Gardea et al.
`5,528,503 A 6/1996 Moore et al.
`5,598.536 A
`1/1997 Slaughter, III et al.
`5,613,115 A 3/1997 Gihi et al.
`5,623,652 A 4/1997 Vora et al.
`5,625,781. A 4/1997 Cline et al.
`5,699,350 A 12/1997 Kraslavsky
`5,734,831 A 3/1998 Sanders
`5,805.442 A 9/1998 Crater et al.
`5,805,816 A * 9/1998 Picazo et al. .......... 395/200.53
`5,862,391 A 1/1999 Salas et al.
`5,950,006 A 9/1999 Crater et al.
`5.975.737 A 11/1999 Crater et al.
`5,982,362 A 11/1999 Crater et al.
`5.997,167 A 12/1999 Crater et al.
`
`OTHER PUBLICATIONS
`ICS Instrumentation & Control Systems-Windows NT for
`real-time control: Which way to go?-ICS Magazine, pp.
`1-8.
`I&CS Jul. 1999-Special Report Software-Software:
`Open source OSs, objects, Web-based communications
`challenge status quo, (Wayne Labs, Senior Technical Edi
`tor), pp. 24-49.
`Landis & Staefa MS 2000, pp. 1-2.
`Landis & Staefa Standards and Open Protocols Integration
`System Architecture, p. 1.
`Annabooks BookStore, Programming and Interfacing the
`8051, by Sencer Yeralan and Asutosh Ahluwalia, pp. 1-2.
`SoftPLC Corporation-Java Support in SoftPLC Corp.
`Products, pp. 1-5.
`Mach J. Company, Mach, an enbeddable, clean room Java
`Virtual Machine, p. 1.
`SoftPLC Corporation. The History of Programmable Con
`trollers, Looking Back From the Year 2000 A.D. (Or, How
`Computers Replaced Proprietary PLCS), pp. 1-7.
`SoftPLC Corporation-TOPDOC: Advanced PLC program
`development & documentation Software, pp. 1-12.
`
`Control Engineering Online Magazine Articles (Jul.1998)-
`No, that's not a PC, it’s a PLC, pp. 1-2.
`Rockwell International Corporation, Allen-Bradley Intro
`duces PLC-5/80E Controller for Ethernet Communication
`Networks.
`Rockwell Automation-Search Results, pp. 1-2.
`Rockwell International Corporation, Vision & Direction,
`The Direction of Automation Systems, pp. 1-4.
`Rockwell International Corporation, Vision & Direction,
`The Role of Open Systems, pp. 1-4.
`Rockwell International Corporation-Vision & Direction
`The Direction of Automation Systems-Emergence of
`Application-Specific Control Solutions, pp. 1-2.
`Rockwell International Corporation-Vision & Direction
`The Direction of Automation Systems. The New Factory
`Worker, pp. 1-2.
`Rockwell International Corporation, Vision & Direction,
`Control System Deliverables - The Next Step, pp. 1-2.
`Rockwell International Corporation, Vision & Direction,
`Conclusion & Acknowledgments, pp. 1-2.
`Rockwell International Corporation-Choices-Perspec
`tives on the Future of Automation Control, p. 1.
`Rockwell International Corporation-Allen-Bradley-Net
`works-Ethernet for Industrial Control-An Ethernet White
`Paper-Apr. 21, 1998, pp. 1-13.
`Rockwell International Corporation-Automation Systems
`Control-General13 World-Class Automation Systems
`from Allen-Bradley, Last Updated: May 7, 1998, pp. 1-12.
`PC Quest, Dec. 97-Point, click, Control-C-Program
`mable controllers take the pain out of embedded control, pp.
`1-2.
`berthel-automation with imagination-PCI 100-Pro
`grammable logic controller for SIMATIC/IBM IPC, pp. 1-3.
`YAHOO! Personalized Search Results for programmable
`logic controller internet acceSS, pp. 1-3.
`SIEMENS-SIMATIC report 1/97 New in the SIMATIC
`Library, pp. 1-2.
`Control Magazine Aug. 1998-Field Test-Dynamic Soft
`ware Makes Control Integration Easier, pp. 1-2.
`Design and Reuse Web Site-EDTN Network-Analyze IP
`Database Content-Analyse Reuse BlockS per taxonomy
`tree, pp. 1-10.
`Engineering Information, Inc.-Ei CPX Web 1990–94).
`“Internet Protocol, Darpa Internet Program, Protocol Speci
`fication-RFC:791.” Defense Advanced Research Projects
`Agency, Sep. 1981.
`“Transmission Control Protocol, Darpa Internet Program,
`Protocol Specification-RFC:793.” Defense Advanced
`Research Projects Agency, Sep. 1981.
`“Open MODBUS/TCP Specification.” A. Swales, Sep. 3,
`1997.
`“comp.unix.programmer Unix-Socket-FAQ For Network
`Programming,” Vic Metcalfe, Andrew Gierth and other
`contributors, Jan. 22, 1998.
`“TCP/IP Illustrated, vol. 2, The Implementation,” Gary R.
`Wright, W. Richard Stevens, 1997.
`“Winsock 2 Information.” Bob Quinn, 1995–1998 (last
`updated Dec. 5, 1998).
`Website Information of PROFIBUS; Technical Overview.
`Website Information of ODVA-The Open DeviceNet's
`Vendor ASSociation.
`Website of PROFIBUS International-Welcome Page.
`“Ethernet Base Gateway Product, AEG-Modicon, pub
`lished 1991.
`
`Page 2 of 21
`
`
`
`US 6,434,157 B1
`Page 3
`
`“Modicon Modbus Plus Network BM85 Bridge Multiplexer
`User's Guide,” Groupe Schneider, Aug. 1995.
`“Modicon Modbus Plus Network Planning and Installation
`Guide,” AEG Schneider Automation, Apr. 1996.
`“Open Modbus/TCP Specification,” A. Swales, Sep. 3,
`1997.
`“MEB Installation and Programming Manual,” Niobara
`Research and Development Corporation, Sep. 24, 1997.
`“MEB-TCP Installation and Programming Manual,”
`Niobara Research and Development Corporation, Oct. 1,
`1997.
`Abstract of “Implementing distributed controls for FMC's
`using Internet utilities,” S. S. Jagdale and N. Merchant;
`Computers of Industrial Engineering, Vol. 31 No. 1-2, p.
`87–90; Oct., 1996 (UK).
`Abstract of “Process Control takes to the Net,” Greg Paula,
`Mechanical Engineering vol. 118 No. 12 Dec. 1996, p. 55.
`Abstract of “Remote interrogation and control of Sensors via
`the internet, Peter L. Furh and Euan F. Mowat, Sensors, vol.
`12 No. 12, 6 pp.; Dec. 1995.
`Abstract of “Progress control takes to the Net,” G. Paula;
`Mechanical Engineering, vol. 118, No. 12, p. 55, Dec.,1996.
`Abstract of “Implementation of CAN/CAN bridges in dis
`tributed environments and performance analysis of bridged
`CAN systems using SAE benchmark, H. Ekiz, A. Kutlu and
`E. T. Powner; Conference Paper, IEEE Southeastern '97,
`Engineering the new energy, IEEE, p. 185–7, 1996.
`Abstract of “Managing interdisciplinary project teams
`through the Web,” R. E. Goodman and P. Chinowsky;
`Conference Paper, WebbNet 96-World Conference of the
`Web Society, pp. 180-185, 1996.
`Abstract of "Learning environment for a proceSS automation
`System using computer networks,” J. Lindfors, L. Yliniemi
`and K. Leivska; Conference Paper, Step t-Genes, Nets and
`Symbols, pp. 137-143, 1996 (Finland).
`Abstract of “Distributed agent Systems for intelligent manu
`facturing,'D. H. Norrie and B. R. Gaines; Canadian Artifi
`cial Intelligence, No. 40, p. 31-3, Autumn 1996 (Canada).
`Abstract of Proceedings of AutoEact 1995 Conference,
`“Today's Automated, Integrated Factory,” Soc. Manuf.,
`Eng., Dearborn, MI; 1995.
`Abstract of “The ECOSSE Control HyperCourse,” C. M.
`Merrick and J. W. Ponton; Computers & Chemical Engi
`neering, vol. 20, Part B, p. S 1353–8, 1996 (UK).
`Abstract of “Chemical-better batch controls.” T. Crowl;
`Contorl & Instrumentation, vol. 28, No. 5, p. 53-4, May
`1996 (UK).
`Abstract of “Industrial software does 32-bit Windows, pre
`pares for the net,” W. Labs; I 8CS, vol. 69, No. 3, p. 23–6,
`31–4, Mar. 1996, USA.
`Abstract of “A case Study of international remote machin
`ing;' G. C. I. Lin and Kao Yung-Chou; Conference Paper,
`Proc. SPIE-Int. Soc. Opt. Eng., vol. 2620, p 553–60, 1995.
`Abstract of “Standardization of long-distance protocols,” R.
`Dinges; Journal Paper, Generation Changes in Network
`Conductor Systems, ITG-Fachberichte, vol. 134, p.
`97-113, 1995 (West Germany).
`Abstract of “Proceedings of AutoEact Conference,” Soc.
`Manuf. Eng., , 684 pp., Dearborn, MI; 1993.
`Abstract of “Control system design V. Communications
`orchestrate process control,” F. Glow; In Tech, vol. 36, No.
`9, p. 68-74, Sep. 1989.
`
`Abstract of “Functions and characteristics of local networks
`adapted to industrial applications,” J. Morlais, Electronique
`Industrielle, No. 97, p. 56–63, Nov. 15, 1985; France.
`Abstract of “Intelligent Supervisory control of Submerged
`arc furnaces.” Markus A. Reuter, Carla Pretorius, Chloe
`West, Peter Dixon and Morne Oosthuizen, JOM vol. 48, No.
`12, Dec. 1996, p. 49-51.
`Abstract of “Simulation on the integration of process control
`Systems of rolling mill plants through Standard networks,
`'Choo Young Yeol, Hwang Hwa Won and Kim Cheeha,
`Proceedings of the Industrial Computing, Conference,
`Instrument Society of America, Research Triangle Park, NC,
`USA, P 1–14; vol. 6, No. 1, 1996.
`Abstract of “Environment waste control digest,” Clayton H.
`Billings; Public Works vol. 127 No. 7, 6 pp, Jun., 1996.
`Abstract of “Experiments in tele-handling and tele-machin
`ing at the macro and micro Scales, using the internet for
`operational environment transmission, Mamoru Mitsuishi,
`Toshio Hori, Tomaharu Hikita, Masao Teratani, Takuro
`Watanabe, Hirofumi Nakanishi and Bruce Kramer; IEEE
`International Conference on Intelligent Robots and Systems
`vol. 2, 1995.
`Abstract of "A phototyping and reverse engineering System
`for mechanical parts-on-demand on the national network,”
`Fred Hansen, Elias Pavlakos, Eric Hoffman, Takeo Kanade,
`Raj Reddy, Paul Wright; Journal of Manufacturing Systems,
`vol. 12 No. 4, p. 269-281; 1993.
`Abstract of “Mathematical model and optimization of fur
`fural treating process,” Tao Peng, Jinshou Yu and Huihe
`Shao, Huadong Huagong Xueyuan Xuebao/Journal of East
`China Institute of Chemical Technology vol. 17 No. 1, p.
`99-104; Feb. 1991.
`Abstract of User's Aspect of Telecommunication and Infor
`mation Processing in Plant Factory; Hashimoto Yasushi (1);
`Journal of the Institute of Electronics, Information and
`Communication Engineers, vol. 78, No. 5, p. 475-81, Fig. 3,
`Ref. 7, 1995. (Japan).
`Abstract of “High-efficient application technology of DCS
`from the viewpoint of users.” Oka Norihito (1); Narita
`Tsutomu (1); (1) Yamatake-Honeywell Co., Ltd., Otomes
`hon, vol. 40, No. 2, p. 24-28, Fig. 5, Part 2, 1995. (Japan).
`Abstract of Users experience with Software tools for pro
`ceSS integration. General results; Stougie, L.; Roeterink,
`H.J.H.; Van Wijk, A.; Stikkelman, R.M.; Nov. 1996.
`Abstract of “Integrated design and proceSS technology. Vol.
`1. Cooke, D.; Kraemer, B.J.; Sheu, P.C.Y., Tsai, J.P.,
`Mittermeir, R.; Society for Design and Process Science, p.
`51–57; 1996. (USA).
`Abstract of “Integrated design and proceSS technology. Vol.
`2; Tanik, M.M.; Bastani, F.B., Gibson, D.; Fielding, P.J.;
`Society for Design and Process Science, p. 423-430, 1996.
`(USA).
`Abstract of “Integrated design and proceSS technology. Vol.
`2” Tanik, M.M.; Bastani, F.B., Gibson, D.; Fielding, P.J.;
`Society for Design and Process Science, p. 306–312, 1996.
`Abstract of “Need low-cost networking consider
`DeviceNet,” W. H. Moss; InTech vol. 43:11; p. 30–31, Nov.
`1996.
`“Plastic Car Bodies Pass the Crash Test,” mechanical engi
`neering; vol. 118, No. 12; Dec. 1996.
`“Remote Interrogation and Control of Sensors via the Inter
`net,” Sensors and Systems; Peter L. Fuhr and Euan F.
`Mowat; University of Vermont; pp. 25–30; Dec., 1999.
`* cited by examiner
`
`Page 3 of 21
`
`
`
`U.S. Patent
`
`Aug. 13, 2002
`
`Sheet 1 of 12
`
`US 6,434,157 B1
`
`OPENED IN NODE OPENED FOR MODBUS COMMAND
`PATH TYPE
`ORIGINATOR
`DATA ACCESS
`DATA MASTER (DM)
`DESTINATION
`DATA ACCESS
`DATA SLAVE (DS)
`PROGRAM MASTER (PM) ORIGINATOR
`PROGRAMMING
`PROGRAM SLAVE (PS)
`DESTINATION
`PROGRAMMING
`
`
`
`Figure I
`
`ETHERNET
`
`
`
`MODBUS PLUS
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`TCP/IP
`INTERFACE
`
`BRIDGE
`8 DATA PATHS
`8 PROGRAM PATHS
`
`MODBUS PLUS
`INTERFACE
`
`18
`
`10
`
`16
`
`
`
`
`
`
`
`BP85
`
`MODBUS PLUS
`BRIDGE
`
`Figure 2
`
`ADDITIONAL
`MODBUS PLUS
`NETWORKS
`
`Page 4 of 21
`
`
`
`U.S. Patent
`
`Aug. 13, 2002
`
`Sheet 2 of 12
`
`US 6,434,157 B1
`
`EXCEPTION CODE
`(HEXADECIMAL)
`
`
`
`
`
`MEANING
`
`06
`08
`09
`
`Busy-- NoT READY To PERFORMREQUESTED operATION
`NAK-- REOUESTED OPERATION REJECTED
`COULD NOT OPEN MODBUS PLUS PATH
`ERRORDURING MODBUS PLUS SEND
`ERRORDURING MODBUS PLUS REPLY
`
`Figure 3
`
`FUNTION CODE
`(DECIMAL)
`
`COMMAND NAME
`
`15
`16
`
`Figure 4
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`Page 5 of 21
`
`
`
`U.S. Patent
`US. Patent
`
`Aug. 13, 2002
`Aug. 13, 2002
`
`Sheet 3 of 12
`Sheet 3 0f 12
`
`US 6,434,157 B1
`US 6,434,157 B1
`
`09
`om
`
`97
`mv
`
`>mO_>_m=>_Dz<3&0
`
`ZZ
`NN
`
`mzja¥o<m
`
`mw>>On_
`
`>IEn5w
`
`m.3me
`
`Page 6 of21
`
`Page 6 of 21
`
`
`
`U.S. Patent
`US. Patent
`
`Aug. 13, 2002
`Aug. 13, 2002
`
`Sheet 4 of 12
`Sheet 4 0f 12
`
`US 6,434,157 B1
`US 6,434,157 B1
`
`10
`10
`
`
`
`Page 7 of21
`
`Page 7 of 21
`
`
`
`U.S. Patent
`
`Aug. 13, 2002
`
`Sheet S of 12
`
`US 6,434,157 B1
`
`20
`
`VGA
`VIDEO
`
`PS/2
`MOUSE
`
`SERIAL
`PORT
`
`PS/2
`KEYBOARD
`
`RJ-45
`CONNECTION
`WALD
`
`34
`
`RJ-45
`1 OBASE-T
`(UTP CABLE)
`
`DB-15
`1 OBASE-5
`
`BNC
`1OBASE-2
`
`TCP/IP
`NETWORK 18
`ACTIVE
`
`36
`
`MODBUS
`PLUS
`PORT B
`
`MB PLUS
`ACTIVE
`
`
`
`
`
`ERROR
`CHANNEL B
`
`ERROR
`CHANNEL A
`
`MODBUS
`PLUS
`PORT A
`
`
`
`16
`
`38
`40
`
`42
`
`SLOT 1
`ACCESSORIES
`
`SLOT 2
`ETHERNET
`
`SLOT 3
`MODBUS PLUS
`
`Figure 7
`
`Page 8 of 21
`
`
`
`U.S. Patent
`
`Aug. 13, 2002
`
`Sheet 6 of 12
`
`US 6,434,157 B1
`
`ONE
`
`(Z-ESVGOL)
`
`
`
`§ 2.) nã?AI
`
`
`
`8 |
`
`Page 9 of 21
`
`
`
`US. Patent
`
`Aug. 13, 2002
`
`Sheet 7 0f 12
`
`US 6,434,157 B1
`
`\
`
`NL
`
`O
`
`
`
`OZ_n_n_<_>_n_0.r
`
`
`
`OZ_n_n_<_>_+m=>_
`
`¥w<_>_sz
`
`
`
`mm>mwwm=2<2
`
`
`
`><>>w.20
`
`Z_<_>_OD
`
`FDOME;NIH:
`
`.560mm.
`
`oom
`
`wwmmoo<n:
`
`n_._m=._Nn_OFOOEr30m0m
`
`
`
`.z>>On_0n_.nSOn..Z>>OD.n5
`
`
`
`
`.Z_>>>mmn_m<.r._.u__ImMZ_>>...X.n._zm<._.
`
`a95m:
`
`Page 10 of21
`
`Page 10 of 21
`
`
`
`U.S. Patent
`
`Aug. 13, 2002
`
`Sheet 8 of 12
`
`US 6,434,157 B1
`
`DESTINATION INDEX
`(DESTIDX)
`1 . . . 64
`
`MODBUS PLUS ROUTING PATH
`
`1. O. O. O. O. ... 64. O. O. O. O
`2 : 1 - O - O - O - 264. O. O. O
`3. 1 . O. O. O ... 3.. 64. O. O. O
`
`3. 2. 1 - O - O - 3 - 2 - 57. O. O
`
`Fig. 10
`
`
`
`BRIDGE
`PATH
`
`BRIDGE
`NODE
`ADDRESS
`1 . . .
`
`FIRST IP
`ROUTING
`BYTE
`
`1 . . . 255
`
`REQUIRED?
`
`DEFINES INDEX INTO THIS BRIDGE'S
`TCP MAPPING TABLE, AND ROUTES
`MESSAGE TO THE IP DESTINATION
`STORED IN THAT TABLE LOCATION.
`
`MB+ TABLE
`ROUTING
`BYTE
`1 . . . 249
`
`LAST
`ROUTING
`BYTE
`(NOTUSED)
`1. OPTIONAL
`IF IP DESTINATION IS ANOTHER
`TCP/IP-MB+ BRIDGE, THIS BYTE
`ROUTES MESSAGE TO THE MB+
`NODE ADDRESS IN THAT BRIDGE'S
`MB+ MAPPING TABLE.
`
`Fig. 12
`
`Page 11 of 21
`
`
`
`US. Patent
`
`Aug. 13, 2002
`
`Sheet 9 0f 12
`
`US 6,434,157 B1
`
`l
`
`NL
`
`O
`
`Oz_n_n_<_>_QB.
`
`mmmm
`
` 0.0.0.0.?
`
`
`
`Oz_n_n_<_>_+m_>_
`
` 0.0.0.0.:
`0100.2 0.0.0.“Nina: 0.0.0.900
`
`0.0.0.0
`
`0.0.0.00:002
`
`
`
`00.0.0.2Slams.
`HDOMEFMAD.
`
`
`
`_Hmm>mmwm_>_<ZH_
`
`_H><>>m_._.<0H—
`
`Z_<_>_OO
`
`.EXm0mm
`
`oom
`
`0.0.0.0.Nmnamg
`
` flxmflz.52Umwwwmogqn:H—
`
`
`
`
`
`n_._m_INn_O._.OOEr30m0m_2>>ODOn..n50n_.Z>>OQm3uz_>>>me9:.._...:ImMZ_>>kazmdF
`
`
`
`
`
`:950E
`
`Page 12 of21
`
`Page 12 of 21
`
`
`
`
`
`
`US. Patent
`
`Sheet 10 0f 12
`
`US 6,434,157 B1
`
`ma#Ezmn22yEzmm.man.
`
`mamas.N03200p0mwemmo3$900@0r0.09.08”0.AU9or
`
`szmmzkm
`
`
`
`m00.0.0.3”00:005.0t0Nmtmomntuaok0NM052
`
`
`
`
`
`NFMDOZ
`
`momma:@.@Gmamas.
`madQmod
`
`
`
`Dank—29mmHGz.._.DOm
`
`moOz
`
`ZO_._.<Z_._.wwDMDOZ
`
`OZ_._.<Z_O_N_O
`
`mN300%:
`
`mN
`
`Page 13 of21
`
`Page 13 of 21
`
`
`
`
`
`US. Patent
`
`Aug. 13, 2002
`
`Sheet 11 0f 12
`
`US 6,434,157 B1
`
`—nijNu.OFOOE
`
`Oz_n_n_<_>_QOF
`
`_‘.N..For.mom
`
`
`
`Oz_n_n_<_>_+m_>_
`
`wwmmoo<n:
`
`
`
`m©.~..wov.mom
`
`
`
`v5.32._.m_z
`
`o.mmN.mmN.mmN
`
`
`
`mw>mwmm=>_<Z
`
`N.n_.nm_..mom
`
`><>>wk<0
`
`N.h.Nb?.mom
`
`know—2Fmin:
`
`._._Xm_me
`
`oom
`
`
`
`
`
`JJOmow.Z>>On_0n_.n50n—.Z>>On_.n5uZ_>>>mmn_m<._.._.u:ImMZ_>>Hszm<._.
`
`
`
`
`
`
`
`Page 14 of21
`
`Page 14 of 21
`
`
`
`
`
`
`
`
`
`
`U.S. Patent
`
`Aug. 13, 2002
`
`Sheet 12 of 12
`
`US 6,434,157 B1
`
`
`
`HILSONETEdÅL
`
`
`
`E15)\/SSEWTOOO LO}{c}
`
`E. LÅ8 ||
`
`SE LÅ8 ZSE LÅ8 Z
`
`SE LÅ8 Z
`
`ÇI 3-anã,
`
`98
`
`78Z8
`
`08
`
`Page 15 of 21
`
`
`
`1
`MODBUS PLUS ETHERNET BRIDGE
`
`US 6,434,157 B1
`
`TECHNICAL FIELD
`The present invention relates to bridges for providing a
`connection between local area networks, and in particular to
`a bridge that provides a connection between a MODBUS
`Plus network and an Ethernet network.
`
`BACKGROUND OF THE INVENTION
`Local area networks are widely used for communicating
`between data processing Systems and peripherals Such as,
`for example, those disclosed by U.S. patent application Ser.
`No. 09/036,565, filed Mar. 9, 1998, now U.S. Pat. No. 6,016,
`523 and incorporated herein by reference, and German
`Patent No. DE 196 15093 A1, filed Apr. 17, 1996, and also
`incorporated herein by reference.
`AS is well known by those skilled in the art, local area
`networks use at least one of many network protocols for
`passing data along the network. Such widely used network
`protocols include the MODBUS Plus Protocol and the
`Ethernet Transport Control Protocol/Internet Protocol (TCP/
`IP).
`The MODBUS Application Protocol used for sending
`MODBUS messages over TCP/IP. The MODBUS Applica
`tion Protocol (MBAP), is a layer-7 protocol providing
`peer-to-peer communication between Programmable Logic
`Controllers and other host-based nodes on a local area
`network. Collectively, these nodes implement all or part of
`a control application widely used for industrial applications
`in the automotive, tire and rubber, food and beverage, and
`utilities industries to name a few.
`MODBUS protocol transactions are typical request
`response message pairs. MODBUS requests contain func
`tion codes representing Several classes of Service including
`data access, online programming, and program download
`and upload classes. MODBUS responses can be acknowl
`edgments with and without data, or non-acknowledgments
`with error information. The MODBUS protocol is described
`in a reference manual entitled MODBUS Protocol Reference
`Guide, publication PI-MBUS-300, incorporated herein by
`reference.
`Because of the widespread use of MODBUS Plus and
`TCP/IP Ethernet networks, there is a need to have these
`networks communicate with each other. To the knowledge of
`the inventors, no bridges are available for facilitating Such
`communication path(s). Accordingly, the present invention
`Satisfies this need.
`
`15
`
`25
`
`35
`
`40
`
`45
`
`50
`
`55
`
`SUMMARY OF THE INVENTION
`The inventive bridge disclosed herein provides a trans
`parent multipath connection between Ethernet host applica
`tions and a MODBUS Plus industrial network. The bridge
`functions as an addressable node on each network, manag
`ing the Ethernet and MODBUS Plus protocols and translat
`ing messages between the network applications in both
`directions.
`Ethernet hosts can establish connections to the bridge and
`send messages intended for MODBUS Plus nodes. The
`bridge accepts the messages, creates internal paths for the
`MODBUS Plus transactions, waits for the MODBUS Plus
`token frame, and forwards the messages to the destination
`nodes. It receives the data responses from the MODBUS
`Plus nodes, returns them to the Ethernet hosts, and closes the
`paths.
`65
`Messages sent to the bridge on either Ethernet or MOD
`BUS Plus contain an embedded MODBUS message, con
`
`60
`
`2
`Sisting of a function code and additional information Such as
`register addresses and data. The bridge uses the MODBUS
`function code to determine the type of internal path required
`for the transaction, and opens a path if one is available. If a
`path is not available, a MODBUS error code (exception
`code) is returned by the bridge to the requesting node.
`The bridge provides MODBUS Data Master, Data Slave,
`Program Master and Program Slave paths as defined by the
`MODBUS function codes in the messages. In one
`embodiment, the bridge Supports up to eight concurrent Data
`paths and eight concurrent Program paths. Moreover, the
`bridge supports full five-byte MODBUS Plus routing,
`enabling transactions through MODICON BP85 MODBUS
`Plus bridges to MODBUS Plus nodes on up to three net
`works beyond the Ethernet bridge.
`The bridge maintains two internal mapping tables that
`provide address mapping between Internet Protocol
`addresses (i.e., 255.255.255.255) and MODBUS Plus path
`addresses (i.e., 64.64.64.64.64). The user can define the
`mapping at a local keyboard and monitor connection, using
`a configuration utility that is Stored in the bridge. Mapping
`tables can also be downloaded by Hypertext Transfer Pro
`tocol (HTTP) from the Ethernet host to the bridge. If neither
`method is used, the bridge provides default mapping tables.
`The user can assign the bridge's Internet Protocol (IP)
`address through a Bootstrap Protocol (BOOTP) server using
`the bridge's Media Access Control (MAC) address, or
`locally by means of the bridge's configuration utility. The
`bridge’s MODBUS Plus address is assigned in hardware
`switches on the bridge’s MODBUS Plus circuit board.
`The bridge can be mounted on a vertical panel or hori
`Zontal shelf. Its rear panel has connectors for the networks
`and for operating power. Also, light emitting diode (LED)
`indicators are provided for power, Ethernet communication,
`and MODBUS Plus communication status.
`
`BRIEF DESCRIPTION OF THE DRAWINGS
`FIG. 1 is a table summarizing the four possible types of
`MODBUS Plus paths supported by the present invention;
`FIG. 2 is a block diagram of a bridge in accordance with
`the present invention connected between an Ethernet net
`work and a MODBUS Plus network;
`FIG. 3 is a table summarizing the MODBUS function
`codes which open Data Master and Data Slave paths;
`FIG. 4 is a table summarizing the MODBUS exception
`codes that may be returned by the present invention to a
`node originating a message;
`FIG. 5 is a simplified block diagram of the bridge of FIG.
`2,
`FIG. 6 is an elevated rear view of a bridge in accordance
`with the block diagram of FIG. 5 having a connector panel;
`FIG. 7 is an elevated view of the connectors provided by
`the connector panel of FIG. 6;
`FIG. 8 is a simplified perspective side view of an Ethernet
`circuit board within the bridge of FIG. 6;
`FIG. 9 depicts a menu provided by the bridge of FIG. 5
`upon execution of a configuration program;
`FIG. 10 illustrates, for the bridge of FIG. 5, default
`MODBUS Plus routing paths for Destination Indexes;
`FIG. 11 depicts an example of the bridge's default map
`ping with one custom entry made by a user;
`FIG. 12 depicts a five-byte routing path field within a
`message received by the bridge of FIG. 5 from a MODBUS
`Plus node;
`
`Page 16 of 21
`
`
`
`US 6,434,157 B1
`
`3
`FIG. 13 shows the mapping of a message between two
`MODBUS Plus nodes via a pair of Ethernet bridges depicted
`in FIG. 5;
`FIG. 14 illustrates an example of a typical default TCP
`mapping, with one custom routing entry made by the user;
`FIG. 15 depicts a MODBUS Application Protocol Header
`having four field comprising a transaction ID, protocol type,
`message length, and destination ID.
`
`4
`Central Processing Unit (CPU) circuit board 20 with
`memory, and a backplane 22.
`The bridge housing 12 preferably consists of sheet metal
`and is wall mountable. The circuit boards are mounted
`within the bridge 10 in IBM style board guides (not shown).
`All connectors are mounted to the Side of the housing. They
`include three Ethernet 10BASE connectors, two MODBUS
`Plus connectors, a keyboard plug, a Video plug, a mouse
`plug, and a power cord plug.
`The above listed circuit boards for the bridge 10 prefer
`ably consist of off the shelf components. In an embodiment,
`the CPU circuit board 20 preferably contains a 486DX 100
`Mhz. CPU, or better, on board keyboard interface, and a local
`VGA display controller (MB display memory). In addition,
`the Ethernet circuit board 18 consists of a standard ISA bus
`Ethernet board with a 10BASE Tunshielded connector to
`provide Ethernet connectivity. Moreover, the Modbus Plus
`circuit board 16 consists of a SA85-002 board by Schneider
`Automation Incorporated. Further, power for the boards is
`Supplied by an open frame 60 watt Single output Switching
`power Supply 14.
`In an alternative embodiment, the bridge 10 consists of a
`conventional personal computer having an Ethernet circuit
`board and a MODBUS Plus circuit board operably attached
`thereto.
`The MODBUS Plus node address for the Modbus circuit
`board 16 preferably is set before installing the bridge 10 on
`the networks. The address is set by Switches (not shown) on
`the MODBUS Plus circuit board 16. The MODBUS Plus
`node should have a unique address on the network with a
`default address of 1, but can be set from 1 to 64.
`Likewise, the type of physical connection used to connect
`the bridge to the Ethernet should be set. The type of physical
`connection is Set by internal Ethernet connector jumper JP2
`on the Ethernet circuit board 18 to define the type of physical
`connection. Preferably, as stated above, the bridge 10 pro
`vides three connectors comprising: connector 22 for an
`IEEE 802.3 10Base-T unshielded twisted pair cable (UTP
`RJ45); connector 24 for an IEEE 802.3 10Base-5 thick cable
`(AIDB-155); and connector 26 for an IEEE 802.3 10Base-2
`thin cable (BNC). Likewise, the jumper JP2 has two posi
`tions wherein the first position enables both the RJ-45 and
`the BNC connectors 22, 26 and the second position enables
`the AUI connector 24.
`If the bridge 10 is being installed at a site that must meet
`CE requirements, and the 10Base-T (RJ-45) connector 22 is
`being used, a ferrite bead should be installed on the Ethernet
`cable at the RJ-45 connector. For example, ferrite bead part
`number 28A2029-0A0 from Steward in Livingston,
`Scotland, UK.
`The bridge 10 can be physically installed on a vertical
`wall panel or a horizontal Shelf using conventional mounting
`brackets. However, clearance should be provided for venti
`lation and access to the bridge's rear panel connectors and
`indicators.
`The power Supply 14 is connected to a power input
`providing either about 110 or 220 V ac. When the power
`Supply 14 is enabled to Supply power to the board Set within
`the bridge housing 12 by toggling Switch 30, light emitting
`diode 32 (LED) is illuminated to show that power is applied
`to the bridge 10.
`Ethernet and MODBUS LEDs are also provided for
`verifying the operation of the bridge 10. In particular, the
`Ethernet board 18 has an indicator 34 for showing a valid
`connection between the board's RJ-45 (UTP) jack and the
`network. The Ethernet board also has another indicator 36
`
`15
`
`35
`
`40
`
`25
`
`DETAILED DESCRIPTION
`While this invention is susceptible of embodiments in
`many different forms, there is shown in the drawings and
`will herein be described in detail preferred embodiments of
`the invention with the understanding that the present dis
`closure 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 the embodiments illustrated.
`AS known by those having skill in the art, two types of
`messages can be initiated to MODBUS Plus nodes using
`MODBUS commands. Programming messages are used for
`logging into a node and controlling it, as in load/record/
`Verify operations. Data acceSS messages are used to read or
`write data at the node, or to get Statistics from the node.
`When a message transaction is initiated, a logical path is
`established between the originating node and the destination
`node. The path is maintained until the transaction is com
`pleted. The type of path that is Set in each device is
`determined by the MODBUS command embedded in the
`meSSage.
`FIG. 1 summarizes the four possible types of MODBUS
`Plus paths, wherein the present invention Supports each type
`comprising: Data Master (DM), Data Slave (DS), Program
`Master (PM), and Program Slave (PS).
`An embodiment of the present invention shown in FIG. 2
`has been built that Supports up to eight paths for each type
`of path shown in FIG.1. In this embodiment, the maximum
`amount of concurrent TCP/IP connections available is
`between 8 and 16, depending on the usage of paths in host
`applications. For example, up to 16 data connections can be
`active between TCP/IP hosts and MODBUS Plus nodes (a
`maximum of 8 active DM paths and 8 active DS paths). Up
`to 16 programming paths can be active (8 PM and 8 PS).
`If MODSOFT software is being used, it sets both a PM
`45
`and a DM path in the bridge for each active connection it
`maintains to a MODBUS Plus destination node. MODSOFT
`could be running on a single host, or simultaneously on
`multiple hosts. Thus, up to eight TCP/IP connections can be
`maintained with Modsoft running on one to eight hosts.
`FIG. 3 Summarizes the MODBUS function codes which
`open DM and DS paths in the respective nodes. Devices
`which use the MODBUS protocol accept incoming requests
`