potential alignment of 1722.1 and “tsn for industrial” · 2015. 4. 27. · potential alignment...

13
ni.com Potential Alignment of 1722.1 and “TSN for Industrial” Eric Gardiner ([email protected])

Upload: others

Post on 28-Jan-2021

2 views

Category:

Documents


0 download

TRANSCRIPT

  • ni.com

    Potential Alignment of 1722.1 and

    “TSN for Industrial”Eric Gardiner ([email protected])

  • 2ni.com

    Key IdeasMany industrial applications need capabilities defined in the 802.1 TSN Task Group

    • Examples: ASrev, Qbv, Qbu, CB, Qci, Qcc, etc.

    Some new TSN capabilities require centralized network management

    • i.e., these applications require a “God box” to configure paths, reserve bandwidth, connect streams, etc.

    802.1 Qcc is defining a data model for centrally managing TSN services, but it does not specify protocols

    1722.1’s new work can potentially select/specify protocols for configuring centrally-managed TSN networks generally and TSN-based industrial networks specifically

    • We want to explore areas of potential alignment

  • 3ni.com

    Example Industrial Application: Machine Control

    Electron Beam Welding Machine

  • 4ni.com

    Example Industrial Application: Machine Control

    Machine-Machine Integration

    Local HMI

    Multi-axes Motion Controller

    High Performance IO

    Process and Machine Health Monitoring

    Safety Systems

    Machine Vision

    Plant integration, PLM, SCADA

  • 5ni.com

    Example Industrial Application: Machine Control

    Machine-Machine Integration

    Local HMI

    Multi-axes Motion Controller

    High Performance IO

    Process and Machine Health Monitoring

    Safety Systems

    Machine Vision

    Plant integration, PLM, SCADA

    1uS1uS

    1uS 1uS

  • 6ni.com

    Example Industrial Application: Machine Control

    Machine-Machine Integration

    Local HMI

    Multi-axes Motion Controller

    High Performance IO

    Process and Machine Health Monitoring

    Safety Systems

    Machine Vision

    Plant integration, PLM, SCADA

    Closed Loop Control @ 5kHz

    1uS1uS

    1uS 1uS

  • 7ni.com

    Example Industrial Application: Machine Control

    Machine-Machine Integration

    Local HMI

    Multi-axes Motion Controller

    High Performance IO

    Process and Machine Health Monitoring

    Safety Systems

    Machine Vision

    Plant integration, PLM, SCADA

    Closed Loop Control @ 5kHz

    1uS1uS

    1uS 1uS

    Waveform Streaming for Video and Vibration data

    (50-500Mb/s)

  • 8ni.com

    Example Industrial Application: Machine Control

    Machine-Machine Integration

    Local HMI

    Multi-axes Motion Controller

    High Performance IO

    Process and Machine Health Monitoring

    Safety Systems

    Machine Vision

    Plant integration, PLM, SCADA

    Closed Loop Control @ 5kHz

    1uS1uS

    1uS 1uS

    Waveform Streaming for Video and Vibration data

    (50-500Mb/s)

    Security and IT

    integration

    Interoperability with other equipment

    (ECAT, PROFINET, EIP, OPC-UA, ModbusTCP)

  • 9ni.com

    What This Application Needs

    • Synchronized time (< µS, and support for multiple timescales)

    • Guaranteed, low latency (10s of µS)

    • Bandwidth (Gb+)

    • Path redundancy for data and control planes

    • Fault tolerance

    • Network convergence (interoperability with “best effort” traffic)

    • Topology flexibility (line, ring, tree)

    • Security (access control, etc.)

  • 10ni.com

    802.1ASrev is Enabling Support for Multiple Timescales

    End stations and switches can be grouped according to time domain

    • A common “working clock” defines the domain

    • Working clock enables time-based scheduling, synchronized I/O, etc.

    • Domain has its own GM

    “Universal clock“ can apply to multiple working clock domains

    • Enables correlation to global traceable time (GPS, etc.)

    • Implemented as second timescale

    Image source: http://www.ieee802.org/1/files/public/docs2012/as-goetz-ind-req-5014-v1.pdf

  • 11ni.com

    802.1Qcc is Enabling Fully Centralized Network Management

    “Centralized User Configuration” manages end stations

    • Requires “User-only protocol”

    “Centralized Network Configuration” manages network (switches, routers)

    • Requires “Management Protocol”

    “User/Network Protocol” abstracts network configuration for CUC

    Image source: P802.1Qcc/D0.3

  • 12ni.com

    Potential Alignment With 1722.1 New WorkDefinition of a “User-only Protocol” for configuring TSN services on end stations

    • Schedule management, talker/listener state management, etc.

    Selection of a “Management Protocol” for configuring TSN services on bridges/routers

    • Schedule management, path management, etc.

    Definition of a “User/Network Protocol” for CUC CNC communication

    • Schedule management, path management, etc.

    Image source: P802.1Qcc/D0.3

  • 13ni.com

    Key IdeasMany industrial applications need capabilities defined in the 802.1 TSN Task Group

    • Examples: ASrev, Qbv, Qbu, CB, Qci, Qcc, etc.

    Some new TSN capabilities require centralized network management

    • i.e., these applications require a “God box” to configure paths, reserve bandwidth, connect streams, etc.

    802.1 Qcc is defining a data model for centrally managing TSN services, but it does not specify protocols

    1722.1’s new work can potentially select/specify protocols for configuring centrally-managed TSN networks generally and TSN-based industrial networks specifically

    • We want to explore areas of potential alignment