Why does my modular EDS file not work?
- Frank Fährmann
- David Tsaava
Owned by Frank Fährmann
Q
Why does my modular EDS file not work?
A
To support modular functionality it is necessary that the “ProxyConnectN (N = 1, 2,…)” entries are defined in EDS section [Connection Manager] of communication Adapter and the corresponding “ProxiedConnectN” entries are defined in the same section of IO Module.
Examples:
Communication Adapter EDS
[Connection Manager] ProxyConnect1 = 0x04010002, $ trigger & transport $ 0-15 = supported transport classes (class 1) $ 16 = cyclic (1 = supported) $ 17 = change of state (0 = not supported) $ 18 = on demand (0 = not supported) $ 19-23 = reserved (must be zero) $ 24-27 = exclusive owner $ 28-30 = reserved (must be zero) $ 31 = client 0 (don't care for classes 0 and 1 0x44240405, $ point/multicast & priority & realtime format $ 0 = O=>T fixed (1 = supported) $ 1 = O=>T variable (0 = not supported) $ 2 = T=>O fixed (1 = supported) $ 3 = T=>O variable (0 = not supported) $ 4-7 = reserved (must be zero) $ 8-10 = O=>T header (4 byte run/idle) $ 11 = reserved (must be zero) $ 12-14 = T=>O header $ 15 = reserved (must be zero) $ 16-19 = O=>T point-to-point $ 20-23 = T=>O multicast $ 24-27 = O=>T scheduled $ 28-31 = T=>O scheduled ,ProxyParam7,ProxyAssem3, $ O=>T default,description ,ProxyParam1,Assem5, $ T=>O default,description ,Assem3, $ config part 1 (dynamic assemblies) ,ProxyAssem5, $ config part 2 (module configuration) "Exclusive Owner", $ connection name "", $ Help string "01 SLOT_MINUS_ONE 20 04 24 03 2C 01 2C 02";
IO Module EDS
[Connection Manager] ProxiedConnect1 = 0x00000000, 0x00000000, ,,, $ O=>T ,,, $ T=>O ,, $ Config #1 ,, $ Config #2 "", "", "";
Reference:
P1219, 7-3.7.2 Modular Additions to Basic EDS Sections, The CIP Networks Library Volume 1, Edit 3.8. April 2010.
See also...