000			02019cam a2200253 4500
001			0471253103
005			20240202104637.0
008			000324s2018 enk 01 | eng
020			_a9781726662567
040			_aMiTN _beng _cMiTN _dMiTN
050		4	_aTK5105.8 .E83 _bR56 2018
100	1		_aRinaldi, John S.
245	1	0	_aEthernet/IP : _bthe everyman's guide to the industry's leading automation protocol / _cJohn S. Rinaldi with Jamin Wendorf.
246	3	3	_aEtherNet/IP : the everyman's guide to EtherNet/IP; a handy guide to EtherNet/IP, the industry's leading automation protocol.
260			_a[Place of publication not identified] : _bReal Time Automation, _c2018.
300			_a153 pages : _billustrations ; _c23 cm
336			_atext _btxt _2rdacontent
337			_aunmediated _bn _2rdamedia
338			_avolume _bnc _2rdacarrier
520			_a"EtherNet/IP came roaring into the 21st century on the backs of DeviceNet and ControlNet, claiming world domination (almost) as the most widely used protocol in manufacturing. While it's pervasive, EtherNet/IP isn't necessarily standard knowledge to everyone on the factory floor. Admit it; maybe you find yourself losing sleep over questions like... Is EtherNet/IP an IoT transport protocol? Are EDS files important for an EtherNet/IP adapter device? Which is better: EtherNet/IP or PROFINET IO? Isn't EtherNet/IP just CIP over an Ethernet connection? How many ways are there to organize device data into a CIP Object Model? What is the Assembly Object Class? Can the EtherNet/IP encapsulation to encapsulate other automation protocols? Does it matter which TCP/IP stack we use to build an EtherNet/IP device? Is DeviceNet obsolete or complementary to EtherNet/IP? How important is the compliance test process? Is CoCO good for an EtherNet/IP scanner device, or delicious with marshmallows?" - from the publisher
650		0	_aEthernet (Local area network system)
650		0	_aLocal area networks (Computer networks)
700	1		_aWendorf, Jamin.
999			_c524136 _d524136