Upload
socaciu-viorica
View
223
Download
0
Embed Size (px)
Citation preview
7/30/2019 CIP Modbus Integration Hanover Fair_0408
1/65
H an n o v e r M e ss e 2 0 0 8Apr i l 21 -25 , 2008
page 1w w w . o d v a . o r gw w w . m o d b u s . o r g
CI P-M odbu s I n t eg r at i on Tod d A. Sn id e
7/30/2019 CIP Modbus Integration Hanover Fair_0408
2/65
Hannover Messe 2008
April 21-25, 2008page 2
AgendaSch n e i d er / M od b u s - I DA / ODVA Re la t i o n sh i pX Value of ODVA to Schneider
X Value of Schneider to ODVA
Cur ren t CI P Modbu s St a tu s
Pu r p o s e a n d m a j o r r e q u i r e m e n t sTechn i ca l so l u t i on r equ i rem en t s & goa l s
Techn i ca l so l u t i on sum m ary
Techn ica l so lu t ion de t a i l s
X Modbus FeaturesX CIP Functions supported with Modbus
X Explicit message
X Implicit I/O
X CIP object representing Modbus/TCP device
X
New Modbus TCP CIP objectX EDS
X Impact on CIP
Br ie f Modbu s/ TCP t u t o r i a l
7/30/2019 CIP Modbus Integration Hanover Fair_0408
3/65
Hannover Messe 2008
April 21-25, 2008page 3
Schn eider Elect r i c/ Modbus - I DA/ ODVA
Coopera t ion
Th e Mo d b u s p r o t o co l an d t h e Et h e r N et / I P p r o t o co l m a k e u pt he m a j o r i t y o f t he i nsta l l ed dev i ce level p rodu ct s t o d a te
Both a re w ide ly accep ted st anda rds w i t h ou t st and ingm em bersh i p and par t i ci pa t i on
The re i s a la rge over l ap o f m em bersh i p bet w een Modbus - I DAand t he ODVA
Seam l ess in t eg ra t i on b e tw een t he p r o toco ls is now ava il ab l e
A larg e r i ns ta l l ed base i s ava i l ab le to bo t h Modbu s - I DA andODVA m em bers t h r ough CI P connect i v i t y t o o th e r p ro t oco l s
Supp l i e r s bene f i t f r om t h i s coope ra t i on t h rou gh t he ab il i t y t or e ach n e w m a r k et s
7/30/2019 CIP Modbus Integration Hanover Fair_0408
4/65
Hannover Messe 2008
April 21-25, 2008page 4
Schn eider Elect r i c/ Modbus - I DA/ ODVA
Coopera t ionCus tom ers w an t a cos t -e f fec t i ve , coher en tn e t w o r k i n g so l u t i o n f r o m p l an t f l o o r t o b o a r d r o o m
Cus tom ers w an t an i ndu st r i a l Eth e rne t so l u t i on
t h a t p r o v i d es in t e r o p er a b i l i t y o f m u l t i - v e n d o rsys tem s and p ro t ect s t he i r i nvest m en t .
Schn e ider Elect r i c has fo r m ed a new coopera t i on w i th ODVA tocom b ine t he tw o m ost successfu l I ndu st r i al Et he rne t so l u t i ons
i n t o a d ef act o st a n d ar d
Th is al l i ance del i ve rs on t he p r om ise o f a b road , st andar d andunm od i f i ed Et he rne t -based f i el dbus f o r t he p l an t f l oo r andaccess t o t ha t i n fo r m a t i on f o r t he rest o f t he en t e rp r i se
Mu l t i - v endo r , st anda rd so l u t i on t o com pe te w i t h c l osedso lu t i ons , l i ke Pro f i ne t .
7/30/2019 CIP Modbus Integration Hanover Fair_0408
5/65
Hannover Messe 2008
April 21-25, 2008page 5
Coopera t ion t o Acce le ra t e Tran sparen t Ready
Schn e ider Elect r i c w an t s to acce lera t e cus to m eradop t i on o f Transpa ren t Ready .
X Reduce the risk of making a decision to use todaysIndustrial Ethernet solutions.
X Protect investment for existing users
To ach iev e t h is , Schn eider Elec t r ic h as decided
t o p u r su e a p a r t n e r sh i p a g r e em e n t
Key pa r t ne r c r i t e r i a :
X Shares philosophy around standard Ethernet
X Collaborative organization not single vendor drivenX Appreciation for Schneider Electrics commitment to
installed base and forward migration
7/30/2019 CIP Modbus Integration Hanover Fair_0408
6/65
Hannover Messe 2008
April 21-25, 2008page 6
W h y a Net w or k Coop er at ion w i t h ODVA
Co o per a t i on co m b in e s M od b u s a n d Et h e r N et / I PX Brings together the market power of the two most
successful protocols.X Both protocols are based on standard Ethernet
technology
ODVA w i l l t ake advan t age o f ModbusX Leverages Modbus installed base & market share
Schne ider Elect r i c can eas i l y t ake adv ant age o fEt h er N e t / I P ser v i ce sX No custom hardware requiredX Existing products can be migratedX Unique values of EtherNet/IP complement simplicity of
Modbus
7/30/2019 CIP Modbus Integration Hanover Fair_0408
7/65
Hannover Messe 2008
April 21-25, 2008page 7
Natu r e o f Cooper a t i onODVA annou nces t ha t Schn e ider Elect r i c w i l l be i nv i t ed t o
becom e an ODVA Pr in cipa l Mem ber , j o i n ing Rockw e l l,Ea t on , Om r on , and CI SCO, and p r ov id e ind iv idu a ls t ose rve on t he ODVA Board o f D i rect o rs and t heTechn ica l Rev iew Board a long w i th act i ve pa r t i ci pan t sin o t he r key ODVA act i v i t i es .
Schne ider Elect r i c has expan ded i t s Tr anspar ent Readyarch i tec tu re by supp or t i ng bo t h Modbu s TCP and
Et he rNe t / I P p ro t oco l and se rv i ces.
ODVA s Et he rNe t / I P t echno logy i s be ing enhanced t osup por t t he Modbus TCP p r o t oco l and t he ModbusSer ia l p ro t oco l .
ODVA s t echn i c al w o rk w i l l p ro t ect t h e invest m en t o fex i s t i ng Modb us TCP. Modbus Ser ia l and Et he r Ne t / I Pdev i ce vendor s and cus to m ers .
7/30/2019 CIP Modbus Integration Hanover Fair_0408
8/65
Hannover Messe 2008
April 21-25, 2008page 8
Techn ica l So lu t i on Sum m ary
CI P st andard has been enh anced t o p r ov ideseam less access t o Mod bu s dev ices
So lu t i on Requ i rem en t s and Com m i t m en t s:X The solution fits within the ODVA frameworkX No change for Modbus target devicesX No change for EtherNet/IP target devices
Schn e ider Elect r i c w i l l u pgr ade i t s PLCm o d u les t o in co r p o r a te Et h e r N et / I P p r o t o co lw h i l e en su r i n g co m p at i b i l i t y w i t h e x i st i n gModbu s dev ices and syst em s
7/30/2019 CIP Modbus Integration Hanover Fair_0408
9/65
Hannover Messe 2008
April 21-25, 2008page 9
AgendaSch n e i d er / M od b u s - I D A / ODVA Re la t i o n sh i pX Value of ODVA to Schneider
X Value of Schneider to ODVA
Cur ren t CI P Modbu s St a tu s
Pu r p o s e a n d m a j o r r e q u ir e m e n t s
Techn i ca l so l u t i on r equ i rem en t s & goa ls
Techn i ca l so l u t i on sum m ary
Techn ica l so lu t ion de t a i l sX Modbus Features
X CIP Functions supported with Modbus
X Explicit message
X Implicit I/O
X CIP object representing Modbus/TCP device
X new Modbus/TCP CIP objectX EDS
X Impact on CIP
Br ie f Mod bu s TCP t u t o r ia l
7/30/2019 CIP Modbus Integration Hanover Fair_0408
10/65
Hannover Messe 2008
April 21-25, 2008page 10
Cu r r e n t Mod b u s I n t eg r a t i on St at u s
Fo r m ed t h e Mo d b u s I n t e g r a t i on j SI G w i t h i n t h e ODVA
X 20 different companies are members
X Have held over 40 meetings since inception
X Ongoing topics to enhance and improve the new Volume 7
Volum e 7 : I n t eg ra t i on o f Modbus Dev i ces i n t o CI P
X Version 1.0 has been published by the ODVA.
Covers Modbus TCP and hooks for Modbus Serial
X An updated version is expected in the next publication cycle fromthe ODVA.
The next version will include Modbus Serial requirements.
ODVA Con for m ance Test ingX Updating ODVA conformance tests with Modbus translator
capabilities.
7/30/2019 CIP Modbus Integration Hanover Fair_0408
11/65
Hannover Messe 2008
April 21-25, 2008page 11
AgendaSch n e i d er / M od b u s - I DA / ODVA Re la t i o n sh i pX Value of ODVA to Schneider
X Value of Schneider to ODVA
Cur ren t CI P Modbu s St a tu s
Pu r p o s e a n d m a j o r r e q u i r e m e n t sTechn i ca l so l u t i on r equ i rem en ts & goa l s
Techn i ca l so l u t i on sum m ary
Techn ica l so lu t ion de t a i l sX Modbus Features
X CIP Functions supported with Modbus
X Explicit message
X Implicit I/O
X CIP object representing Modbus/TCP device
X New Modbus/TCP CIP objectX EDS
X Impact on CIP
Br ie f Modbu s/ TCP t u t o r i a l
7/30/2019 CIP Modbus Integration Hanover Fair_0408
12/65
Hannover Messe 2008
April 21-25, 2008page 12
Pur pose & Requ i r em en t
Ex t end t he CI P s tandar d t o p r ov ide seam less access toModb us dev ices
Requ i remen ts
X The solution fits within the ODVA framework The solution is consistent with the existing CIP model
The solution has significant technical merit, as viewedfrom outside ODVA
X No change for the Modbus target devicesX No change for the EtherNet/IP target devices
Cons t ra in ts
X Minimize impact to existing EtherNet/IP originator
7/30/2019 CIP Modbus Integration Hanover Fair_0408
13/65
Hannover Messe 2008
April 21-25, 2008page 13
AgendaSch n e i d er / M od b u s - I DA / ODVA Re la t i o n sh i pX Value of ODVA to Schneider
X Value of Schneider to ODVA
Cur r en t CI P Modbu s St a tu s
Pu r p o s e a n d m a j o r r e q u i r e m e n t s
Techn i ca l so l u t i on r equ i rem en ts & goa l s
Techn i ca l so l u t i on sum m ary
Techn ical so lu t ion de t a i l sX Modbus Features
X CIP Functions supported with Modbus
X Explicit message
X Implicit I/O
X CIP object representing Modbus/TCP device
X New Modbus/TCP CIP objectX EDS
X Impact on CIP
Br ie f Mod bu s TCP t u t o r ia l
7/30/2019 CIP Modbus Integration Hanover Fair_0408
14/65
Hannover Messe 2008
April 21-25, 2008page 14
Tech n i ca l So lu t i on Req u i r e m en t s 1 / 2
Techn ica l r equ i r em ent
X The solution allows Modbus devices to be integrated andaccessed from CIP originators and software tools
X The solution allows CIP originators basic read/write accessto data in Modbus devices
X The solution allows the CIP originator to bring Modbusdata into the CIP application in a way that is consistentwith the CIP communications model
X Support all existing devices that can function as a Modbusserver device ( including simple devices and complexsuch as a programmable controller)
7/30/2019 CIP Modbus Integration Hanover Fair_0408
15/65
Hannover Messe 2008
April 21-25, 2008page 15
Techn i ca l So lu t i on Requ i rem en t s 2 / 2
Techn ica l r equ i r em ent
X Integration of Modbus devices is consistent with theexisting CIP application and communication models
Minimize impact to existing CIP originator devices
No impact to existing CIP target devices
No Impact to existing Modbus server devices
X Allow existing vendor specific CIP Modbus gatewayproducts to work without change.
Desirable that the new mechanism be feasible forimplementation in existing products.
7/30/2019 CIP Modbus Integration Hanover Fair_0408
16/65
Hannover Messe 2008
April 21-25, 2008page 16
Agenda
Sch n e i d er / M od b u s- I DA / ODVA Re la t i o n sh i pX Value of ODVA to Schneider
X Value of Schneider to ODVA
Cur r en t CI P Modbu s St a tu s
Pu r p o s e a n d m a j o r r e q u i r e m e n t s
Techn i ca l so l u t i on r equ i rem en ts & goa l s
Techn i ca l so l u t i on sum m ary
Techn ical so lu t ion de t a i l sX Modbus Features
X CIP Functions supported with Modbus
X Explicit message
X Implicit I/O
X CIP object representing Modbus/TCP device
X new Modbus/TCP CIP object
X EDS
X Impact on CIP
Br ie f Modbus/ TCP t u t o r i a l
7/30/2019 CIP Modbus Integration Hanover Fair_0408
17/65
Hannover Messe 2008
April 21-25, 2008page 17
Su m m ar y o f Tech n i ca l So lu t i on 1 / 5
Th e Mo d b u s I n t eg r a t i o n m e ch a n i sm :
X The Modbus translator translates CIP objects and services toModbus messages. The translator can be implemented in
the CIP originator or a CIP router .
X Defined CIP objects and services that provide read andwrite access to Modbus data. Allows Modbus function code
execution via the Modbus Object.X Explicit and implicit messaging from the CIP originator to
the Modbus target device. Conversion of CIP messaging toModbus requests and Modbus responses to CIP messages.
X EDS files that describe the Modbus capabilities in CIP terms.A generic Modbus file or optionally a device specific file.
7/30/2019 CIP Modbus Integration Hanover Fair_0408
18/65
Hannover Messe 2008
April 21-25, 2008page 18
The Targ e t Au d ien ce:
Deve lopers o f CI P o r i g ina t o r s w h o w i sh t o im p lem en tt he Modbus Trans lat o r i n t he i r dev i ce , o r w i sh t o a l lowt he i r dev i ces t o com m un i ca te v i a a CI P- t o -Modbusr o u t e r .
Deve lopers o f CI P rou t e r d ev i ces w h o w ish t o
im p lem en t t he Modbus Trans lat o r i n a CI P- t o -Modbusr o u t er ( e .g ., a n Et h e r N et / I P t o M od b u s Se r i al r o u t e r ) .
Modbu s dev i ce vendor s w h o w i sh t o u n d e r st a n d h o w
t he i r dev i ce can be i n teg r a ted i n t o t he CI P t o Modbusin t eg ra t i on so lu t i on ( e .g . , t o be ab le t o c rea te EDS f i l esfo r Modb us dev i ces) .
Su m m ar y o f Tech n i ca l So lu t i on 2 / 5
7/30/2019 CIP Modbus Integration Hanover Fair_0408
19/65
Hannover Messe 2008
April 21-25, 2008page 19
App can sendCIP messages tonative EIPdevices
App can send CIP
messages toModbus devicesvia the CIP-Modbus translation
CIP-Modbustranslation
Explicit Messages, I/O Messages
Connection Management, Routing
Object Library
Application functions
TCP/IP Stack
Ethernet data link & physical layers
Modbus/TCPEtherNet/IP
Dev ice arch i t ect u r e v iew : CI P o r i g i na t o r t oMod b u s TCP
Su m m a r y o f Tech n i ca l So lu t i on 3 / 5
7/30/2019 CIP Modbus Integration Hanover Fair_0408
20/65
Hannover Messe 2008April 21-25, 2008
page 20
Modbu s TCP t r ans la t ionX En d dev ice I d en t i f y t h r o ug h
CI P path
X Transla t ion laye rt r a n sl at i n g Mo d bu s
r e q u est s i n CI P ob j e ct
X New CI P Modbus Ob j ects
CIP Originator View
Su m m a r y o f Tech n i ca l So lu t i on 4 / 5
7/30/2019 CIP Modbus Integration Hanover Fair_0408
21/65
Hannover Messe 2008April 21-25, 2008
page 21
Backplane
Prog tool
Scanner Config
Download
EIP Config
N ew CI P co m m u n i ca t i o n m e ch a n i sm s al lo w e x i st i n g ,un m od i f ied Modbu s dev ices t o be seam less ly accessedf r om a CI P-o r i g i na to r d ev i ces
Modbus/TCP DeviceEtherNet/IP Device
Controller
Explicit Messages, I/O Messages
Connection Management, Routing
Object Library
Application functions
TCP/IP Stack
Ethernet data link & physical layers
Modbus/TCP
CIP-Modbus translation
EtherNet/IP
Su m m a r y o f Tech n i ca l So lu t i on 5 / 5
7/30/2019 CIP Modbus Integration Hanover Fair_0408
22/65
Hannover Messe 2008April 21-25, 2008
page 22
AgendaSch n e i d er / M od b u s- I DA / ODVA Re la t i o n sh i pX Value of ODVA to Schneider
X Value of Schneider to ODVA
Cur ren t CI P Modbu s St a tu s
Pu r p o s e a n d m a j o r r e q u ir e m e n t sTechn i ca l so l u t i on r equ i rem en t s & goa ls
Techn i ca l so l u t i on sum m ary
Techn ica l so lu t ion de t a i l sX Modbu s Featu resX CIP Functions supported with Modbus
X Explicit message
X Implicit I/O
X CIP object representing Modbus TCP device
X New Modbus TCP CIP objectX EDS
X Impact on CIP
Br ief Modbus/ TCP t u t o r i a l
7/30/2019 CIP Modbus Integration Hanover Fair_0408
23/65
Hannover Messe 2008April 21-25, 2008
page 23
Mod b u s Feat u r es Used w i t h CI P 1 / 4
Ther e a re no r equ i red Modbus f unc t i on codes fo r u sew i t h CI P
X Modbus devices do not share common function codes.
X
Required to work with any Modbus device
Recommended Modbus fun ct i on codes are :
X FC 03 Read Holding Registers
X FC 16 Write Multiple Registers
X FC 23 Read/Write Multiple Registers
X FC 43/14 Read Device Identification
Use w ou ld a l low a Modbu s dev i ce t o m or e eas il yi n t e gr a t e w i t h CI P.
X Vendors designing new Modbus products or updating existingfirmware are strongly encouraged to support at least thisrecommended function list
7/30/2019 CIP Modbus Integration Hanover Fair_0408
24/65
Hannover Messe 2008April 21-25, 2008
page 24
CI P does no t speci f y a con f i gu ra t i on m e thod . ForModb us TCP conf ig u r a t ion BootP, DHCP, in t eg ra ted HMIo r a n e x t e r n a l p o r t cou ld be u sed .
X DHCP is recommended since this is the methodrecommended by Ethernet/IP
For dev i ce con f i gu r a t i on use o f con t i guous reg i st e r s isrecom m ended as t hen t he dev i ce can r ece ive
co n f i g u r a t i o n u p o n t h e o p en i n g o f a CI P I / O co n n e ct i o n .X Vendors are encouraged not to mix read-only and read-
write registers or to create holesof unsupportedregisters within configuration areas.
Use of an EDS f i l e i s recom m end ed t o h e lp CI P-basedcon f i gu ra t i on t oo l s.
Mod b u s Feat u r es Used w i t h CI P 2 / 4
7/30/2019 CIP Modbus Integration Hanover Fair_0408
25/65
Hannover Messe 2008April 21-25, 2008
page 25
CI P i s no t aw are o f Modbus t im eou ts .
X Mismatched timeout lengths between CIP and Modbus needto be considered.
The Modbu s Trans lat o r w i l l hand le by te sw app ing t o t h eModb us dev ice.
X CIP is Little Endian and Modbus is Big Endian, the translatortakes care of this for the user.
For I / O Conn ect i ons t h e connect i on s ize i nd i ca tes howm a n y r e g ist er s w i l l b e r e ad o r w r i t t e n o n t h e d ev i ce .
X This is indicated by the Instance ID.
For b est use in CI P, de t a i led da t a m ap o f t he Modbu st a b l es on t h e M od b u s d ev i ce f r o m t h e v en d o r i s i m p o r t a n t .
Mod b u s Feat u r es Used w i t h CI P 3 / 4
7/30/2019 CIP Modbus Integration Hanover Fair_0408
26/65
Hannover Messe 2008April 21-25, 2008
page 26
Care i s needed t o be su r e CI P re f r esh ra t e i s no t fast e rt han t he ra te a t t he t a rg e t Modbus dev i ce can consum et h e co r r e sp o n d i n g w r i t e s.
X
Mismatched timeout lengths between CIP and Modbus need tobe considered.
X It is possible to have multiple writes from the CIP side throughthe Modbus translator to the target Modbus device.
X There is no correlation between the CIP sequence number and
the Modbus transaction identifier .
Modbus dev i ces requ i r e an i ndependen t r ead f un ct i on i no r d er t o w o r k w i t h CI P I / O co n n ect i on s.
X Devices that otherwise would use Function Code 23 (FC23) onlyare recommended to also implement the read Function Code 03.Schneider does not have devices using only FC23.
Mod b u s Feat u r es Used w i t h CI P 4 / 4
7/30/2019 CIP Modbus Integration Hanover Fair_0408
27/65
Hannover Messe 2008April 21-25, 2008
page 27
AgendaSch n e i d er / M od b u s- I DA / OD VA Re la t i o n sh i pX Value of ODVA to Schneider
X Value of Schneider to ODVA
Cur ren t CI P Modbu s St a tu s
Pu r p o s e a n d m a j o r r e q u ir e m e n t sTechn i ca l so l u t i on r equ i rem en t s & goa ls
Techn i ca l so l u t i on sum m ary
Techn ica l so lu t ion de t a i l s
X Modbus FeaturesX CI P Func t i ons suppo r t ed w i t h Modbus
X Explicit message
X Implicit I/O
X CIP object representing Modbus TCP device
X New Modbus TCP CIP object
X EDS
X Impact on CIP
Br ie f Mod bu s TCP t u t o r ia l
7/30/2019 CIP Modbus Integration Hanover Fair_0408
28/65
Hannover Messe 2008April 21-25, 2008
page 28
CI P Fu n ct i on s Su p p o r t ed w i t h Mo d b u s 1 / 2
Unconn ect ed Ex p l i c i t Messag in g
Con n ect ed Class 3 Ex p l i c i t Messagin g
Con nec t ed Class 1 I m p l i c i t Messag in g
X With Cyclic triggering
Connect ed I m p l i ci t
X works with transport class 3
3 2 - b i t Ru n / I d le h ead er s f o r O- > T
X Modeless in the T->O direction
Un i cast i n t h e T- > O an d O- > T d i r ect i o n s
7/30/2019 CIP Modbus Integration Hanover Fair_0408
29/65
Hannover Messe 2008April 21-25, 2008
page 29
M u lt i ca st f o r T- > O ( w i t h RPI m a t ch i n g )
Dat a Segm ent
X For Modbus devices with their configuration data in a
contiguous item block
I m p l i ci t Ex cl u si v eOw n er a n d I n p u t On l y
X There is no notion of redundant ownership
Param e te r Ob j ect s
Assem b ly Ob j ect s
I d e n t i t y Ob j e ct
Modbus Ob jec t
CI P Fu n ct i on s Su p p o r t ed w i t h Mo d b u s 2 / 2
7/30/2019 CIP Modbus Integration Hanover Fair_0408
30/65
Hannover Messe 2008April 21-25, 2008
page 30
AgendaSch n e i d er / M od b u s- I DA / OD VA Re la t i o n sh i pX Value of ODVA to Schneider
X Value of Schneider to ODVA
Cur ren t CI P Modbu s St a tu s
Pu r p o s e a n d m a j o r r e q u ir e m e n t sTechn i ca l so l u t i on r equ i rem en t s & goa ls
Techn i ca l so l u t i on sum m ary
Techn ica l so lu t ion de t a i l sX Modbus FeaturesX CIP Functions supported with Modbus
X Exp l ic i t m essage
X Implicit I/O
X CIP object representing Modbus TCP device
X
New Modbus TCP CIP objectX EDS
X Impact on CIP
Br ie f Mod bu s TCP t u t o r ia l
7/30/2019 CIP Modbus Integration Hanover Fair_0408
31/65
Hannover Messe 2008April 21-25, 2008
page 31
Ex p l i c it Message : W hat t he CI P Or ig in a t o r Sees
Ex p l i c i t m essag in g
X Explicit messages support connected and unconnectedmode .
Modb us TCP is iden t i f i ed CI P conn ect ion v ia th e pa t h
X Both Modbus TCP and Modbus Serial have specific CIP PortTypes. The port number signifies connection to a Modbustarget.
Each Mod bu s dev ice appear s as a CI P dev ice w i t h CI Papp l ica t i on ob j ect s and na t i ve CI P com m un i ca t i ons .
X List of CIP objects (parameter object or Modbus object)
and services exposed for the Modbus TCP device arereferred in CIP Object translation.
X The Modbus Translator provides the CIP capability.
7/30/2019 CIP Modbus Integration Hanover Fair_0408
32/65
Hannover Messe 2008April 21-25, 2008
page 32
Ex pl ic i t Con n ect ed Message t o Mod bu s TCP
CIP Originator Modbus TCPTarget
Open TCP connection
Modbus request
TCP connection opened
Explicit msg request, class=Param or MBobject
FwdOpen request
FwdOpen reply
Translator
Modbus reply
CIP reply
FwdClose Request
FwdClose reply
Close TCP connection
TCP connection closed
7/30/2019 CIP Modbus Integration Hanover Fair_0408
33/65
Hannover Messe 2008April 21-25, 2008
page 33
Ex pl ic i t Con n ect ed Message t o Mod bu s TCPw i t h No Modbus Rep ly
CIP Originator Modbus TCPTarget
Open TCP connection
Modbus request
CIP retry at each RPI
TCP connection opened
Explicit msg request, class=Param or MBobject
FwdOpen request
FwdOpen reply
Translator
TCP retransmission algorithm startedStart inactivity timer (e.g. 4*RPI)
Modbus request
CIP retry at each RPI
Modbus request
CIP retry at each RPI
Modbus request
CIP retry at each RPI
Modbus request
Inactivity timer expires
Delete CIP connection
No CIP reply
Delete CIP connection
Reset and restart
Inactivity timer (e.g.4*RPI) at each receptionof a CIP message.
Inactivity timer expires
TCP Retransmission finished; TCP connection is reset
7/30/2019 CIP Modbus Integration Hanover Fair_0408
34/65
Hannover Messe 2008April 21-25, 2008
page 34
Ex p l ic i t Un con n ect ed Message t o Mod bu s TCP
CIP Originator
Open TCP connection
Modbus request
TCP connection opened
Modbus reply
UnconnectedSend
UnconnectedSend reply
Translator Modbus TCPTarget
Close TCP connection
TCP connection closed
7/30/2019 CIP Modbus Integration Hanover Fair_0408
35/65
Hannover Messe 2008April 21-25, 2008
page 35
Ex p l ic i t Unconn ect ed Message t o Mod bu s TCPw i th No Modbus Rep ly
CIP Originator
Open TCP connection
Modbus request
TCP connection opened
UnconnectedSend
UnconnectedSend reply indicating a RoutingError
Translator Modbus TCPTarget
Start Modbus Response Timer = CIP Request Timeout
(provided by CIP Request) and TCP retransmission
No Modbus reply
Request Time-out Timer expires
TCP Retransmission finished: TCP connection isreset
7/30/2019 CIP Modbus Integration Hanover Fair_0408
36/65
Hannover Messe 2008April 21-25, 2008
page 36
Ex pl ic i t Message : CI P Obj ect t o Mod bu s TCP
The Param ete r Ob j ect i ns tan ces a re u sed fo r exp l i c i tmessag ing
X Get/Set single Attribute service for reading/writing one
data items
New Modb us TCP app l i ca t ion o b j ect a l low s access t om u l t i p le da t a i t em s and add i t i ona l Modbu s TCP fu nc t i oncodes
X Services for read and write of multiple data items (HoldingRegisters, Coils, etc.)
X Service to allow explicit pass through of any Modbus TCPfunction code
X Appropriate EDS constructs if needed to support the newobject (in the translation device and/or the Modbus TCPdevice EDS)
7/30/2019 CIP Modbus Integration Hanover Fair_0408
37/65
Hannover Messe 2008April 21-25, 2008
page 37
Ex p l i ci t Con n ect ion Ex am ple
t o read 4 con t i guous input registers st a r t i ng a t i ndex 11
X calling the service Get_Member ,
X for Class ID = 0x04 (Assembly Class ID),
X Instance ID = 0 x 0 0 0 1 0 0 0 B
X with the parameter Mem b er I D = 1 ,
X Using the Member Services Multiple Sequential Member
protocol, specify 4 members
7/30/2019 CIP Modbus Integration Hanover Fair_0408
38/65
Hannover Messe 2008April 21-25, 2008
page 38
Ex p l i c it Conn ect ion Ex am ple : Al t e rn a t i ves
t o read 4 c o n t i g u o u s input registers st a r t i n g a t i n d ex 11,Using t he Modb us Ob j ect .
X
calling the service Read I npu t Reg i ste r s(0x4D),
X for Class ID = 0x?? (Modbus Class ID),
X Instance ID = 1 ,
X with the Sta r t i ng Add ress parameter = 11 and the Quan t i t yo f I n p u t Re g ist e r s parameter = 4,
Can a l so be accessed on e at a t im e w i t h t he Param ete rob j ect . Us ing t he GetA t t r i bu teS ing le serv ice.
7/30/2019 CIP Modbus Integration Hanover Fair_0408
39/65
Hannover Messe 2008April 21-25, 2008
page 39
Agenda
Sch n e i d er / M od b u s- I DA / OD VA Re la t i o n sh i pX Value of ODVA to Schneider
X Value of Schneider to ODVA
Cur ren t CI P Modbu s St a tu s
Pu r p o s e a n d m a j o r r e q u ir e m en t sTechn i ca l so l u t i on r equ i rem en t s & goa ls
Techn i ca l so l u t i on sum m ary
Techn ica l so lu t ion de t a i l sX Modbus FeaturesX CIP Functions supported with Modbus
X Explicit message
X I m p li ci t I / O
X CIP object representing Modbus TCP device
X
New Modbus TCP CIP objectX EDS
X Impact on CIP
Br ie f Modbu s/ TCP t u t o r i a l
7/30/2019 CIP Modbus Integration Hanover Fair_0408
40/65
Hannover Messe 2008April 21-25, 2008
page 40
I m p l i ci t I / O : Mo d bu s TCP Tr a n sl at i on 1 / 4
Assem b l y Ob j ect s po in t t o 250 by t e b l ocks w i t h i n t h e f ou rModbus dat a i t em s tab l es
Pa ram e te r Ob j ect s po i n t t o i nd i v i dua l da ta i t em i n t he t ab l es
Each Mod bu s da ta t ab le i s assign ed a b lock o f Assem bly an dPa r am e t e r I n s t a n ce s
X Holding Registers (table of 0x10000 data)=> accessible through Assembly Instance #0x00001, to instance #0x10000
X Input Registers ( table of 0x10000 data)
=> accessible through Assembly instance #0x10001 to instance #0x20000X Coils ( table of 0x10000 data)
=> accessible through Assembly instance #0x20001 to instance #0x30000
X Discrete Input ( table of 0x10000 data)=> accessible through Assembly instance #0x30001 to instance #0x40000
Each Modbu s TCP dat a i t em s o f f set in a tab le i s r epr esent edby an i ns tance num ber ( 1 based o f f se t )
7/30/2019 CIP Modbus Integration Hanover Fair_0408
41/65
Hannover Messe 2008April 21-25, 2008
page 41
I m p l i ci t I / O: Mo d bu s TCP Tr a n sl at i on 2 / 4
Th e n u m b er o f d at a i t e m s t o be r ead / w r i t t e n isd et e r m i n ed b y t h e p r o d u ced / co n su m ed connec t ion
si ze w i t h i n t h e Fo r w a r d Op e n.
Ex am p le: t o w r i t e 4 Ho ld i n g Reg i st e r s, st a r t i ng a treg is te r n u m b er 2 0 ( t a b le o f f set 1 9 ) :
X O->T Connection path of Class Assembly, Instance 20
X O->T Connection size of 8
I / O co n nect i on t o read 8 I n pu t Reg ist er s,st a r t i ng a t r eg i st e r n u m b er 4 ( t a b le o f f set 3 ) :
X T->O Connection path of Class Assembly, Instance
0x10004X T->O Connection size of 16 (connection size is specified
in bytes)
7/30/2019 CIP Modbus Integration Hanover Fair_0408
42/65
Hannover Messe 2008April 21-25, 2008
page 42
I m p l ici t I / O: Mo d bu s TCP Tr a n sl at i on 3 / 4
CIPOriginator Translator Modbus/TCPTarget
Open TCP connection
Modbus write request (FC 16)
Fwd Close request
TCP connection opened
Output packet (originator-to-target)
Modbus reply
FwdOpen request : assembly , instance xx, connectionsize
Close TCP connection
TCP connection closedFwd Close reply
FwdOpen reply
Input packet (target-to-originator)
Modbus reply
Modbus read request (FC 03)
Note: Output packet triggersModbus write. Timer triggersModbus read. Reply triggers Inputpacket.
This sequence is repeatedindefinitely.
I m p l i ci t I / O: Modbus TCP Trans la t i on
7/30/2019 CIP Modbus Integration Hanover Fair_0408
43/65
Hannover Messe 2008April 21-25, 2008
page 43
I m p l i ci t I / O: Modbus TCP Trans la t i onw i t h N o Mo db u s Rep ly 4 / 4
CIPOriginator Translator Modbus/TCPTarget
Modbus write request (FC 16)
Output packet (originator-to-target)
Modbus reply
Modbus read request (FC 03)
input packet (target-to-originator)
No Modbus reply
TCP Retransmission finished: TCP connection isreset
Output packet (originator-to-target)
Output packet (originator-to-target)
Delete CIP connection (T->O and O->T)
Reset Inactivity timer(e.g. 4*RPI) at eachreception of a CIPmessage.
Inactivity timer expires
TCP retransmission algorithm started
Start inactivity timer (e.g. 4*RPI)
Inactivity timer expires
Delete CIP connection (T->O and O->T)
No Input Packet
7/30/2019 CIP Modbus Integration Hanover Fair_0408
44/65
Hannover Messe 2008April 21-25, 2008
page 44
Agenda
Sch n e i d er / M od b u s- I DA / OD VA Re la t i o n sh i pX Value of ODVA to Schneider
X Value of Schneider to ODVA
Cur ren t CI P Modbu s St a tu s
Pu r p o s e a n d m a j o r r e q u ir e m en t sTechn i ca l so l u t i on r equ i rem en t s & goa ls
Techn i ca l so l u t i on sum m ary
Techn ica l so lu t ion de t a i l s
X Modbus FeaturesX CIP Functions supported with Modbus
X Explicit message
X Implicit I/O
X CI P ob j ec t repr esent in g Modbu s TCP dev ice
X New Modbus TCP CIP object
X EDS
X Impact on CIP
Br ie f Modbu s/ TCP t u t o r i a l
7/30/2019 CIP Modbus Integration Hanover Fair_0408
45/65
Hannover Messe 2008April 21-25, 2008
page 45
CI P Ob j ect Represen t ing a Modbus Dev ice 1 / 4
Min im um CI P Ob j ect s Requ i r ed :
Device Specific1 .. nRequiredAssembly
Device Specific1 .. nRequiredParameter
1RequiredModbus
1RequiredConnectionManager
1RequiredMessageRouter
1RequiredIdentity
Note# of InstancesOptional /Required
Object Class
7/30/2019 CIP Modbus Integration Hanover Fair_0408
46/65
Hannover Messe 2008April 21-25, 2008
page 46
I d en t i t y :
X A minimum set of attributes, populated with data from the
Modbus device
Message Rou t e r : supp or t ed
X behavior will be managed by the translator
Connect i on m anager : suppo r t ed
X behavior will be managed by the translator
Modbu s :X Provides Modbus Table specific services
Parame te r :
X Provides access to an individual data item within the Modbus
data tablesAssemb ly :
X Provides a translation into the Modbus data item tables
CI P Ob j ect Represen t ing a Modbus Dev ice 2 / 4
7/30/2019 CIP Modbus Integration Hanover Fair_0408
47/65
Hannover Messe 2008April 21-25, 2008
page 47
I d en t i t y Ob j ect t r a n sl at i on
X Attributes of the Identity Object will be
populated using data obtained throughModbus Services.
An example is FC 43/14
X Device Identification Objects notsupported by the Modbus device arerepresented by zero length strings.
X If a Modbus device does not support theRead Device Identification function then itreturns Unknown Modbus Device.
CI P Ob j ect Represen t ing a Modbus Dev ice 3 / 4
7/30/2019 CIP Modbus Integration Hanover Fair_0408
48/65
Hannover Messe 2008April 21-25, 2008
page 48
Modbus Speci f i c I ns tance At t r i bu t es
X All information in ASCII string with no standardizationabout the content
N ot a l l ow edA l l o the rs
Cond i t iona l : requ i red fo r FC 43 / 14Devicedependen t
M odbus I D i n fo1 8
N o t a l l ow ed8 - 1 7
Requ i red : r e tu rns unknow n M odbus dev i ce w / o FC 4 3/ 1 4
ASCI I St r ingProduc t N am e7
Requi redASCI I St r ingSer ia l Num ber6
Requi redASCI I St r ingSta tus5Requi redASCI I St r ingRevis ion4
Requi redASCI I St r ingProd uct Code3
Requi redASCI I St r ingDevice Typ e2
Requi redASCI I St r ingVe n do r I D1
Required/ConditionalData TypeNameID
CI P Ob j ect Represen t ing a Modbus Dev ice 4 / 4
A d
7/30/2019 CIP Modbus Integration Hanover Fair_0408
49/65
Hannover Messe 2008April 21-25, 2008
page 49
Agenda
Sch n e i d er / M od b u s- I D A/ ODVA Re la t i o n sh i pX Value of ODVA to Schneider
X Value of Schneider to ODVA
Cur r en t CI P Modbu s St a tu s
Pu r p o se an d m a j o r r e q u ir e m e n t sTechn i ca l so l u t i on r equ i rem en ts & goa l s
Techn i ca l so l u t i on sum m ary
Techn ical so lu t ion de t a i l sX
Modbus FeaturesX CIP Functions supported with Modbus
X Explicit message
X Implicit I/O
X CIP object representing Modbus/TCP device
X new Modbus/TCP CIP object
X EDS
X Impact on CIP
Br ief Modbus/ TCP t u t o r i a l
EDS f i les
7/30/2019 CIP Modbus Integration Hanover Fair_0408
50/65
Hannover Messe 2008April 21-25, 2008
page 50
EDS f i les
Modb us dev ices a re no t r equ i r ed t o have EDS f i les
X GenericModbusDevice EDS files allow EDS-based originators toconnect to Modbus target devices
Indicate use of the Assembly Object instances for I/O
connections
Modbu s dev i ces m ay , i f d esi r ed , p r ov ide an EDS f i l e t obe t t e r descr ib e t he d ev i ce s speci f i c da ta
X E.g., indicate which Modbus data items are in the device; use
Param entries to detail device-specific parameters
Th e Gener icModb usDev ice EDS f i l e p r ov i des a st a r t i ngp o in t f o r a co n f ig u r a t i o n t o ol t o cr e at e t h e I / OConn ect i on set up f o r a Modbu s dev i ce rep r esen t ed by aCI P m ode l.
X Defines the potential CIP capability in any Modbus device.
A d
7/30/2019 CIP Modbus Integration Hanover Fair_0408
51/65
Hannover Messe 2008April 21-25, 2008
page 51
Agenda
Sch n e i d er / M od b u s- I DA / ODVA Re la t i o n sh i pX Value of ODVA to Schneider
X Value of Schneider to ODVA
Cur ren t CI P Modbu s St a tu s
Pu r p o se a n d m a j o r r e q u ir e m e n t sTechn i ca l so l u t i on r equ i rem en t s & goa ls
Techn i ca l so l u t i on sum m ary
Techn ica l so lu t ion de t a i l sX
Modbus FeaturesX CIP Functions supported with Modbus
X Explicit message
X Implicit I/O
X CIP object representing Modbus TCP device
X New Modbus TCP CIP object
X EDS
X I m p act o n CI P
Br ief Modbus/ TCP t u t o r i a l
I m p act o n CI P
7/30/2019 CIP Modbus Integration Hanover Fair_0408
52/65
Hannover Messe 2008April 21-25, 2008
page 52
I m p act o n CI P
The goa l w as t o m i n im i ze t h e im p act o fi nco rpo ra t i ng Modbus in t o CI P.
Ther e i s som e im pact on CI P because o f Modb us .
CI P Com m on Speci f i cat ion Enh ancem ent CI PSE-0 0 1 - 0 7 8 w as approv ed by t he ODVA to suppor t
t h ese chan ges.
The possib le and l i k e ly shar in g o f a ph ys ica l
Et he rne t po r t by Et he rNet / I P and Modbus TCPcrea tes th e need f o r t he changes.
I m pact on CI P: Po r t Ob j ect
7/30/2019 CIP Modbus Integration Hanover Fair_0408
53/65
Hannover Messe 2008April 21-25, 2008
page 53
I m pact on CI P: Po r t Ob j ect
Ther e ar e t w o new p or t t y pes t o t h e Po r tOb j ect ( Po r t Ob j ect I n st an ce At t r i b u t es) :
X Modbus/TCP
X Modbus/SL
ModbusTCP ind icat es i t i s a Mod b u s TCP p or t .
X Indicated by the semantic 201
ModbusSL ind i ca tes i t i s a Modbu s Ser ia l po r t .
X Indicated by the semantic 202
I m pact on CI P: Po r t Ob j ect
7/30/2019 CIP Modbus Integration Hanover Fair_0408
54/65
Hannover Messe 2008April 21-25, 2008
page 54
I m pact on CI P: Po r t Ob j ect
Upda ted t h e f ou r t h a t t r i bu t e t o t h ePor t Ob j ect ca l l ed t h e Po r t N am e.
X Requires all CIP Ports that share the samephysical network to have the same Port Name.
X SHORT _STRING which names the PhysicalNetwork Port. (maximum of 64 characters,
example Port A).
X Must be unique for each port.
One cannot apply the same Port Name to two
(or more) Physical Network Ports.
I m pact on CI P: Ob j ect Li b ra r y
7/30/2019 CIP Modbus Integration Hanover Fair_0408
55/65
Hannover Messe 2008April 21-25, 2008
page 55
I m pact on CI P: Ob j ect Li b ra r y
Th e Modbus Ob j ect has been added t o t heOb j ect Speci f i cat ions in t he CI P Ob j ect Lib r a ry
X The Class Code is 44 Hex.
Ad d i t i o n o f t h e Mod bu s I d en t i t y I n f o
at t r i bu t e t o t h e I d en t i t y Ob j e ct I n st a n ceA t t r i b u te s .
X A conditional attribute for Modbus devices only.
I m pact on CI P: EDS
7/30/2019 CIP Modbus Integration Hanover Fair_0408
56/65
Hannover Messe 2008April 21-25, 2008
page 56
I m pact on CI P: EDS
W r i t e On ly pa ram et er added t o t he Dev icePro f i les
X Added to the Parameter Object Descriptor Attribute.
X
Indicate the Parameter Value attribute can be set and NOTread.
Tw o n ew Dev ice Class i f i cat ion s :
X Modbus/TCP
X Modbus/SL
Th e Por t Nam e f ield i s n ow cond i t i ona l .
X Was optional
X Required if the CIP port shares a physical network withanother CIP port
I m pact on CI P: EDS
7/30/2019 CIP Modbus Integration Hanover Fair_0408
57/65
Hannover Messe 2008April 21-25, 2008
page 57
I m pact on CI P: EDS
Scal in g Of f set f ie ld w as changed
X A Field in the Parameter Section, Field Number16
X Was a data type INT
X Changed to data type DINT
X Increases the range to accommodate Modbus,the mapping is hidden in the translator.
I m pact on CI P: Gene r a l
7/30/2019 CIP Modbus Integration Hanover Fair_0408
58/65
Hannover Messe 2008April 21-25, 2008
page 58
I m pact on CI P: Gene r a l
A n e w g en e r a l er r o r co d e added fo rMo d b u s I n t eg r a t i on
X Unknown Modbus Errorhex code 2B
X When an unknown Modbus Exception code isseen be the Modbus translator.
Agenda
7/30/2019 CIP Modbus Integration Hanover Fair_0408
59/65
Hannover Messe 2008April 21-25, 2008
page 59
Agenda
Sch n e i d er / M od b u s- I DA / ODVA Re la t i o n sh i pX Value of ODVA to Schneider
X Value of Schneider to ODVA
Cur ren t CI P Modbu s St a tu s
Pu r p o se a n d m a j o r r e q u ir e m e n t s
Techn i ca l so l u t i on r equ i rem en t s & goa ls
Techn i ca l so l u t i on sum m ary
Techn ica l so lu t ion de t a i l sX Modbus Features
X CIP Functions supported with Modbus
X Explicit message
X Implicit I/O
X CIP object representing Modbus TCP device
X New Modbus TCP CIP object
X EDS
X Impact on CIP
Br ief Modbus/ TCP t u t o r i a l
Modbu s TCP Tu t o r ia l : The Modbu s Pr o t oco l 1 / 6
7/30/2019 CIP Modbus Integration Hanover Fair_0408
60/65
Hannover Messe 2008April 21-25, 2008
page 60
MODBUS Protocol is a messaging structure introduced to themarket by Modicon in 1979, used to establish master-slave/client-server communication between intelligent devices.
Since Modbus protocol is just a messaging structure, it isindependent of the underlying physical layer.
It is usually implemented usingX RS23 2, RS42 2, RS48 5,
X TCP I P over Et her netX Over a va r ie t y o f o t he r m ed ia ( e .g . w i re less, f i be r , rad io , ce l lu la r ,
e tc . )
X Modbus Plus , a h igh speed t ok en passing ne t w ork
MODBUS is a de facto standard and open. Schneider Electric hastransferred the Specifications for Modbus and MODBUS TCP protocolsto Modbus-IDA.
Modbus TCP Tu t o r ia l : Techn o logy Overv iew 2 / 6
7/30/2019 CIP Modbus Integration Hanover Fair_0408
61/65
Hannover Messe 2008April 21-25, 2008
page 61
gy
TIA/EIA-232 -F Ethernet Physical LayerTIA/EIA-485 -AOther
MODBUS APPLICATION LAYERModbus Application protocol specification
MODBUS MAPPING ONTCP/IPModbus messaging on TCP/IP
Implementation guide
TCP
IETF RFC 793
IPIETF RFC 791
Ethernet II / 802.3
IEEE 802.2
SERIAL LINE MASTER / SLAVE
Modbus messaging on Serialline implementation guide(Under dev.)
Other
Modbus TCP Tu t o r i a l : App l i ca t i on Laye r 3 / 6
7/30/2019 CIP Modbus Integration Hanover Fair_0408
62/65
Hannover Messe 2008April 21-25, 2008
page 62
Modbus is a simple Master (Client) / Slave (Server)Application protocolX The Client prepares and sends a Request to the server
X The Server analyses the request, processes the request, and
sends an answer to the Client.
Modbus is a scalable protocolX A server can implement a subset of Modbus protocol
Modbus comprises Public and User Defined function
codes
Modbus application protocol proposes a list offunctioncodes to read or write data or to activate remoteprocessing on a remote serverX Read / Write list of data words, Read/Write list of bits
X Diagnostic, Identification
pp y
Modbus TCP Tut o r i al : App l i ca t i on Dat a Un i t 4 / 6
7/30/2019 CIP Modbus Integration Hanover Fair_0408
63/65
Hannover Messe 2008April 21-25, 2008
page 63
MBAP (Modbus ApplicationProtocol ) TCP/IPencapsulation header
Additionaladdress Function code Data Error check
ADU
PDU
Modbus TCP Tu t o r i al : App l i ca t i on Dat a Un i t 4 / 6
The MODBUS protocol defines a simple protocol data unit (PDU)independent of the underlying communication layers. The translationof MODBUS protocol on specific buses or network can introduce someadditional fields on the application data unit (ADU).
Function code DataMBAP Header
MODBUS PDU
MODBUS TCP/IP ADU
For Ethernet TCP/IP
Mod bu s TCP Tu t or ia l :Fun ct i on Codes Read & W r i t e Da ta 5 / 6
7/30/2019 CIP Modbus Integration Hanover Fair_0408
64/65
Hannover Messe 2008April 21-25, 2008
page 64
Fun ct i on Codes Read & W r i t e Da ta 5 / 6
MODBUS uses a b ig -End ian rep r esen t a t i on fo r som e addr essesand da ta i t em s.
MODBUS bases i t s da ta on a ser ies o f t ab les . The f ou r p r im ary
t ab les a re :
Mod bu s TCP Tu t or ia l :A l l Pub l i c Fun ct i on Code Def in i t i ons 6 / 6
7/30/2019 CIP Modbus Integration Hanover Fair_0408
65/65
Hannover Messe 2008April 21-25, 2008
page 65
All Pub l i c Fun ct i on Code De f in i t i ons 6 / 6
Public function codes:X cover b o t h Mod bu s TCP and Modbu s SL
X co v er Read / w r i t e d at a a n d o t h er c om m a n d / se r v ice s