10Mb/S Extended Reach Single Twisted Pair Ethernet PHY Call for Interest

10Mb/S Extended Reach Single Twisted Pair Ethernet PHY Call for Interest

10Mb/s Extended Reach Single Twisted Pair Ethernet PHY Call for Interest IEEE 802.3 Ethernet Working Group 1 CFI Panel Members Chair and Presenter: Supporters and experts for the Question and Answer session 2 Supporters - Page 1 3 Supporters - Page 2 4 CFI Objective . To gauge the interest in starting a Study Group for: 10Mb/s Extended Reach Single Twisted Pair Ethernet PHY . This meeting will NOT: . Fully explore the problem . Debate strengths and weaknesses of solutions . Choose a solution . Create a PAR or 5 Criteria . Create a standard or specification 5 Agenda . Industrial Networking Market Need . Industrial Networking Solution Requirements . Target Markets . Market Potential . Technical Feasibility . CFI Proposal . Q&A . Straw Polls 6 Industrial Networking Market Need 7 Industrial Automation Landscape Factory . Factory Automation Automation . Discrete units of output (Discrete) . Rapid operations . Process Automation . Continuous output . Expansive applications Batch . Often hazardous Automation (Hybrid) . Batch Automation . Batch output Process . Combination of both Automation continuous and discrete (Continuous) 8 Ethernet Conversion Gap in Industrial Networking . Ethernet is propagating . Desire to converge on one network type . Non-Ethernet fieldbuses still required to complete communications to the edge . Challenges: Cost, reach, special environments Credit: Dr. Raimund Sommer, Endress + Hauser, ODVA Industry Conference, Oct. 2014. Ethernet Gap 9 Too Many Fieldbus Variants Partial list… . Big challenges for end users Process Discrete . Labor skills FOUNDATION PROFIBUS DP . Installation complexity Fieldbus H1 PROFIBUS PA DeviceNet . Maintenance complexity HART CANOpen . Interoperation issues Modbus CC-Link Many Ethernet Variant Application INTERBUS EtherNet/IP Gateways PROFINET CompoNet FF HSE AS-Interface Modbus TCP HART-IP IO-Link Fieldbus 10 Cannot Meet New Application Needs: Higher Rates from the Edge . IIoT, Big Data, and Analytics . Embedded web servers . High-speed data logging . Installation and . Production details, equipment maintenance conditions, environment state, energy consumption,… . Optimization, maintenance, . Video safety, compliance,… . Reduced footsteps . Safety . Product quality sensor . Security 11 Industrial Networking Solution Requirements: Why 10Mb/s Extended Reach Single Twisted Pair Ethernet PHY? 12 Why Ethernet to the Edge? . Single network paradigm . Contemporary features . Leverages of economy of scale . Security . Reduces complex gateways . Embedded web servers . More rapid commissioning . No dongles or special apps . More rapid fault diagnosis and repair . Larger pool of talent to install and manage 13 Why 10Mb/s and Extended Reach? Fieldbus Longest Reach Highest Rate . Common fieldbuses PROFIBUS DP 9.6kb/s @ 1200m 12Mb/s @ 100m reach 400-5000m CANopen 10kb/s @ 5000m 1Mb/s @ 20m . 1200m believed to address most fieldbus Modbus RTU 100kb/s @ 1200m 2Mb/s @ 50m applications CC-Link 156kb/s @ 1200m 10Mb/s @ 100m 1200 baud @ 1524m (24AWG) HART No enhanced rate . Common fieldbuses 1200 baud @ 3048m have rates up to 12Mb/s (20AWG) DeviceNet 125kb/s @ 500m 500kb/s @ 100m . 10Mb/s addresses most fieldbus applications ControlNet 5Mb/s @ 1000m No enhanced rate INTERBUS 500kb/s @ 400m No enhanced rate . Enables a standard MAC FOUNDATION H1 31.25kb/s @ 1900m No enhanced rate PROFIBUS PA 31.25kb/s @ 1900m No enhanced rate 14 Why Single Twisted Pair? . Many applications run for Fieldbus Cable Type Cable Power decades and upgrade multiple times FOUNDATION H1 FF-844 specified Yes . Lengthy fieldbus cables are HART Various Yes expensive to run (often in conduit) PROFIBUS PA IEC 61158 Type A* Yes . End nodes are easy to replace 4-20mA SP-50 instrumentation cable Yes Cable Reuse Valuable Cable Reuse . Certain cables are certified CANopen EIA-485* Yes Modbus RTU EIA-485* No CC-Link, Ver.1.10 specified . Single Twisted Pair is most CC-Link No common Shielded, 3- & 5-core ODVA DeviceNet specified DeviceNet Yes . Usually shielded (5-core, various classes) . Some devices require power ControlNet RG-6/U Coaxial No over the same pair INTERBUS 3 / 6 no. twisted pairs, various Yes . New PoDL CFI / Amendment? PROFIBUS DP IEC 61158 Type A (22AWG?) No 15 Why Single Twisted Pair? . Expected benefits: . Less complex to install . Lower cost . Smaller size . Benefits enable a large volume of small and cost-sensitive Factory Automation components to migrate to Ethernet . Previously un-networked discrete devices . Low end fieldbus devices 16 Summary: Why 10Mb/s Extended Reach Single Twisted Pair Ethernet PHY? . Desire to have one network type throughout facility/factory/plant . Alternative to hugely fragmented Fieldbus landscape . Ease of installation . Single pair essential – lower skilled labour force . Ease of maintenance . Availability of Ethernet knowledge and networking configuration . Lower Total Cost of Ownership . Greater bandwidth required to support Industry 4.0 / Smart Factory / IIoT . Enabling new use cases with higher throughput, lower latency . Sensors running web servers! . Improved efficiencies . Existing Ethernet standards not addressing needs 17 Target Markets 18 Potential Markets . Industrial Automation . The dominant driving market for this CFI . Landscape breakdown described previously: . Process Automation . Factory Automation . Hybrid . Large market potential (i.e. port count) A 10Mb/s Extended Reach Single Twisted Pair Ethernet PHY anticipates significant leverage across other segments including: . Building Automation . Lighting Systems (Reference July 2014 IEEE 802 BoF “I Feel the Need… for Low Speed” (Carlson/Kennedy)) 19 Case Study – Process Automation Networked Devices . Largely Ethernet . Controllers . Stations . Servers . Largely Fieldbus . Flow . Level . Pressure . Temperature . Loggers and displays . Analytics . Bulk of nodes 20 Case Study – Process Automation Application Characteristics Same Devices Some Low Cost Extended Reach Shorter Reach Process Plants Process Skids 21 Case Study – Process Automation Networking History & Trends Pneumatics -> Electronics Analog -> Digital Pt-Pt -> Networks Ethernet Increased rates 10/100M Increased devices Fieldbus <100m, non-IS Mostly “Brownfield” updates 31.25 kb/s Digital HART Network 1200 baud 4-20 mA Instruments Pt-Pt CFI Pneumatic Actuators Pneumatics ~1950 1986 1996 2005 22 Case Study – Process Automation User Requirements . NAMUR Example . User Association of Automation Technology in Process Industries . Defines requirements for Fieldbus in Process Organisation (NE 74) . Select NE 74 Highlights . Flexible topology, cable length up to 1000m, spur up to 200m . 2-wire cable for data and power . Connection technology must be robust and easy to use, if possible by using existing cable infrastructure 23 Case Study – Process Automation Intrinsic Safety . “Intrinsic safety (IS) is a protection technique for safe operation of electrical equipment in hazardous areas by limiting the energy, electrical and thermal, available for ignition” - Wikipedia . Requirement within Industrial Process and Batch . Certification is of the networked equipment – not of the IEEE PHY . The PHY should not preclude the design of IS networked equipment Credit: Example Ignition Curve from CENELEC standard EN 50020 24 Case Study – Discrete Automation . On-machine devices Discrete Devices . Sensors (e.g. proximity, photoelectric,…) . Pushbutton stations, Tower Lights . Motor starters . In-cabinet devices . Pushbuttons Industrial Ethernet . Indicators . Overload relays . Motor starters . Soft starters . Power supplies Discrete wires Discrete wires Discrete wires . Safety sensors and actuators . E-Stops, Light curtains, Safety sensors, safety Safety contactors,… In-cabinet On-machine 25 Case Study – Discrete Automation Fieldbus Devices . Sensors . Valves . Encoders . Pushbutton stations Industrial Ethernet . Tower lights . Motor starters . Overload relays Fieldbus1 Fieldbus2 . Soft starters . Power supplies . …… 26 Case Study – Discrete Automation Networking History & Trends Fieldbus Industrial Ethernet Discrete wires Industrial Ethernet Discrete wires IO-Link Fieldbus S S S S S S S S S S S S Industrial Ethernet for Local I/O Remote I/O Industrial Ethernet for both control and field discrete wires, Fieldbus, control, fieldbus/IO-Link smart devices? Dumb devices Dumb devices for smart devices 1980s 1990s 2000s-2010s 2020s? 27 Case Study – Discrete Automation In-cabinet Application . IP20 protection level . Open connection . Manual wiring . Bus or daisy-chain topology . Short distance (<5m) . High node density . Pushbuttons, indicator and displays on door, other components in cabinet; . Mix of dumb wired and fieldbus devices 28 Case Study – Discrete Automation On-Machine Application . IP60 and higher protection level . Simple installation . Fast maintenance . Daisy-chain or Star topology . Most <50m distance . Mixed with extended reach . Power and communication in one cable . Standard and safety control 29 Case Study – Discrete Automation User Requirements ► Low cost ($1-2 incremental cost) ► Small size (<10cm2, 5cm2 may be typical) ► Low device power (<1W, 500mW may be typical) ► Adequate bandwidth (10Mb/s) ► Simple installation (wire reduction) ► Easy to use (common standard technology, good integration into control and supervisory system) 30 Case Study – Discrete Automation Challenges and Needs ► Today’s Industrial Ethernet M12-D can not meet smart devices’ Cat5e or above requirements . Cost is not low enough . Size is not small enough . Power is not low enough ► Lower cost,

View Full Text

Details

  • File Type
    pdf
  • Upload Time
    -
  • Content Languages
    English
  • Upload User
    Anonymous/Not logged-in
  • File Pages
    46 Page
  • File Size
    -

Download

Channel Download Status
Express Download Enable

Copyright

We respect the copyrights and intellectual property rights of all users. All uploaded documents are either original works of the uploader or authorized works of the rightful owners.

  • Not to be reproduced or distributed without explicit permission.
  • Not used for commercial purposes outside of approved use cases.
  • Not used to infringe on the rights of the original creators.
  • If you believe any content infringes your copyright, please contact us immediately.

Support

For help with questions, suggestions, or problems, please contact us