Presentation is loading. Please wait.

Presentation is loading. Please wait.

SERCOS III Technical Introduction SERCOS Seminar, Atlanta September 16, 2009.

Similar presentations


Presentation on theme: "SERCOS III Technical Introduction SERCOS Seminar, Atlanta September 16, 2009."— Presentation transcript:

1 SERCOS III Technical Introduction SERCOS Seminar, Atlanta September 16, 2009

2 (c) SERCOS International 2009No. 2 Evolution of SERCOS Innovation by Combining Ethernet and SERCOS Servo & Motion Profile SERCON816 (optical transmission) 2, 4, 8, 16 Mbit/s SERCOS II RT-Data Sync SVC Channel Master Slave comm. Hardware Function Specific Profile (FSP) SERCOS Communication Profile (SCP) Innovation by combination of SERCOS and Ethernet SERCOS III NRT-Channel … 2 RT Channel (P&S) SERCON100 Master or SERCON100 Slave Ethernet Dual PHY IP UDP/TCP Ethernet 100 Mbit/s Standard IP Applic- ations Standard IP Applic- ations Sync … I/O´s Connections of Producer and Consumer Drives SVC S/IP Safety Generic Device Profile GDP SERCOS Applications netX with SERCOS III Master or SERCOS III Slave or

3 Topology

4 (c) SERCOS International 2009No. 4 Topology Line and Ring Master P1 P2 Line Slave 2 P1 P2 Slave 3 P2 P1 Slave 1 P1 P2 primary or secondary channel Master P1 P2 Ring Slave 2 P1 P2 Slave 3 P2 P1 Slave 1 P1 P2 secondary channel primary channel Cyclic redundant transmission of real-time data in primary and secondary channel

5 (c) SERCOS International 2009No. 5 Topology (not permitted) No switches, no hubs Master I/O RT Channel Ethernet (Office) P2 P1 Switches or Hubs are not needed and are not permitted as intermediate infrastructure components within a SERCOS III network

6 (c) SERCOS International 2009No. 6 Master Standard Switch S III Telegrams using broadcast address Ethernet (Office) Topology (not permitted) Line with switch

7 Communication Redundancy with Ring Topology

8 (c) SERCOS International 2009No. 8 Redundancy Ring break Step 1 Ring OK Step 2 Ring break slave n-1 master slave n Fast-Forward slave n-1 master slave n Loopback & Forward S-Channel P-Channel S-Channel X X P-Channel Communication recovery time < 25 µs

9 (c) SERCOS International 2009No. 9 Redundancy Ring recovery Step 3 P-Link OK S-Link OK slave n-1 master slave n Loopback & Forward Slave signals P-Link OK in ATn-S P-LINK P-Channel S-Channel S-LINK Step 4 Ring recovery slave n-1 master slave n Master commands Fast-Forward P-Channel S-Channel Master commands Fast-Forward Loopback & Forward Slave signals S-Link OK in ATn-P

10 Wiring Cables Connectors

11 (c) SERCOS International 2009No. 11 Flexibility in wiring P2 P1 P2 P1 P2 P1  Each Slave has two Ports (P1 and P2)  Port 1 and Port 2 are interchangeable  No error can happen in wiring  Simplification during commissioning

12 (c) SERCOS International 2009No. 12 Flexibility in the choice of the cable type  Useful for industrial applications, suitable for trailing cable  Cable type and Shielding  min. CAT5e with S/UTP  Industry: CAT5e with S/STP (SERCOS III)  Use of Patch cable or Crossover cable possible  Flexible in the choice of the cable type  Simplification in commissioning  Length 100m (max.)  S III specifies ground connection of shielding and unused wires RJ 45 IP 20 RJ 45, M12, IP 67  Recommendation of connectors and sockets  Selection of certified components  SERCOS III (RJ45 & M12, IP 20 & IP 67)

13 Communication and Telegram structure

14 (c) SERCOS International 2009No. 14 General telegram structure  SERCOS III based on Standard Ethernet according ISO/IEC PreambleIFG Destination address Source address Ethernet Type data fieldFCSSFD MST (S3H) 7+1 Byte 6 Byte 2 Byte 4 Byte  12 Byte Byte S III data checked via FCS S III Ethernet type = 0x88CD  Media layer: (overhead = 38 bytes)  min. telegram length: 84 bytes  6,8 µs  max. telegram length: 1538 bytes  123,1µs  MAC layer: (overhead = 26 bytes)  min. telegram length: 72 bytes  5,8 µs  max. telegram length: 1526 bytes  122,1µs S III HEADER

15 (c) SERCOS International 2009No. 15 ETH telegrams method 2 Communication cycle RT channel NRT channel HDRHDR MSTMST MDT0 HDRHDR S3HS3H MDT1 HDRHDR S3HS3H MDT2 HDRHDR S3HS3H MDT3 AT0 HDRHDR S3HS3H AT1 HDRHDR S3HS3H AT2 HDRHDR S3HS3H AT3 HDRHDR S3HS3H HDRHDR MSTMST MDT0 method 1 Communication cycle RT channel (Ethertype = 0x88CD ) NRT channel (Ethertype <> 0x88CD) HDRHDR MSTMST MDT0 HDRHDR S3HS3H MDT1 HDRHDR S3HS3H MDT2 HDRHDR S3HS3H MDT3 AT0 HDRHDR S3HS3H AT1 HDRHDR S3HS3H AT2 HDRHDR S3HS3H AT3 HDRHDR S3HS3H HDRHDR MSTMST MDT0 ETH telegrams Communication Sequence in CP3/CP4  Communication cycle is partitioned in Real-Time channel and Non Real-Time channel  Up to 4 telegrams per data direction (max byte)  Master Data Telegrams and Acknowledgment Telegrams are transmitted by the master  NRT channel integrated in separate time slot, no modification of the ETHernet telegrams necessary

16 SERCOS III Telegram Structure S III Header (MST) Hot plug field Service channel (SVC) Real time data (RTD)

17 (c) SERCOS International 2009No. 17  MDT/AT data are protected via FCS and transmitted by the master.  MST is valid in MDT0...3 and AT0…3.  MDT  Every slave receives the MDT and take its data.  The MDT is repeated only, not changed by the slave  MST in MDT0 only is used for synchronization purposes.  AT  Slaves insert data in the AT data field  Slaves process cross communication in AT only  Every slave checks the Rx-FCS and determines the Tx-FCS preambleIFG destination address source address 0x88CD MDT/AT data field FCSSFD SERCOS type (MDT/AT) phaseCRC 1 Byte 4Byte 6 Byte 2 Byte MST (S3H) checked via CRC S III Header (MST)

18 (c) SERCOS International 2009No. 18 preamble destination address source address 0x88CD MDT/AT data field FCSIFGSFD MST (S3H) Service channel field of slaves Hot-plug field (new slaves) Real-time data field of connections  MDT/AT data field may contain up to 3 fields  Hot-plug (HP)  Service channel (SVC)  Real-time data (RTD) MDT and AT data fields

19 (c) SERCOS International 2009No. 19 Real-time data structure  Real-time data field contains:  Master/Slave data  Cross communication (CC) data  Length of real-time data field : configurable real-time data slave # 1 real-time data slave # 2 real-time data slave # K Service channel field of slaves Hot-plug field (new slaves) Real-time data field of connections M/S connection data slave # 1 CC data also possible slave # 1 Cross communication data of slaves MDT0-3 or AT0-3

20 Initialization

21 (c) SERCOS International 2009No. 21 Initialization Communication phases (CP0 to CP4) CP1 CP3 CP2 CP4 CP0 NRT mode MDT0-CP0 1 1 = no MDT0-CP0 within 65 ms CP = Communication phase NRTmode = non real-time mode Start Address allocation Slave identification Communication parameter setup Application parameter setup RTD are don‘t care Communication in operation S S store and forward

22 (c) SERCOS International 2009No. 22 CP0 MDT / AT structure preamble destination address source address type MDT/AT data field FCSIFGSFD MST (S3H) SERCOS type = MDT0-P/S phase = 0 CRC 36 bytes padding SERCOS type = AT0-P/S phase = 0 CRC 2 Byte TADR #1 SEQCNT 2 Byte            TADR #510 TADR # bytes AT0-P (primary channel)  Master set SEQCNT = 0x0001 AT0-S (secondary channel)  Master set SEQCNT = 0x8001 Master set all Topology ADdResses to 0xFFFF Comm. Version 4 Byte

23 (c) SERCOS International 2009No. 23 Function of Slave with TADR #2 SADR is written in TADR the field of TDAR#2 CP0 Address allocation, Slave function SERCOS type = AT0 phase = 0 CRC TADR #1 SEQCNT            TADR #2 TADR #511 W SADR R W +1 TADR = Topology address SADR = SERCOS address, available via switch or parameter Slave reads and increments the content of SEQCNT in AT0 to determines the Topology address (TADR) Slave writes the SERCOS address in the corresponding TADR

24 (c) SERCOS International 2009No. 24 CP0 Address allocation, Master with ring (examples)  4 slaves without addressing error  SERCOS addresses #1, #10, #11 and #0 AT0-P data field contents AT0-P data field contents  4 slaves with addressing error  SERCOS addresses #1, #0, #1 and #254  Diagnostics in the Master  wrong SERCOS address (0 or >511)  same SERCOS address (add-on to S II)  additional SERCOS address TADR #3 0x000B TADR #2 0x000A TADR #4 0x0000 TADR #511 0xFFFF            TADR #1 0x0001 SEQCNT #0 0x0005 TADR #5 0xFFFF TADR #3 0x0001 TADR #2 0x0000 TADR #4 0x00FE TADR #511 0xFFFF            TADR #1 0x0001 SEQCNT #0 0x0005 TADR #5 0xFFFF

25 (c) SERCOS International 2009No. 25 Synchronization generation HDRHDR MSTMST MDT0AT0MDT0 IP telegrams HDRHDR S3HS3H HDRHDR MSTMST communication cycle RT channelIP channel synchronization signal (once per cycle) Synchronization is generated by the MST field of MDT0 only.

26 (c) SERCOS International 2009No. 26 Synchronization with MST preamble destination address source address type MDT data field FCSIFGSFD SERCOS type (MDT0) phaseCRC 1 Byte 4Byte 6 Byte 2 Byte4 Byte MST synchronization trigger SERCOS cycle (tScyc) AT0 transmission time (t1) NRT channel (t6, t7) Start in Master 2,24 µs (28 Byte, constant duration) Synchronization delay time propagation delay: checked via CRC 7+1 Byte

27 (c) SERCOS International 2009No. 27 Physical delay times Slave and cable PHY Rx PHY Tx Rx-Fifo Tx-Fifo FCS generator FCS ca ns ca ns SERCOS III Slave path delay  Slave delay (trep): FPGA and netX meas. 600ns  Cable delay (tcable):  CAT5e max. 5,56 ns / m (max. 556 ns / 100 m)  Glass fiber max. 5 ns / m (max. 500 ns / 100 m)

28 (c) SERCOS International 2009No. 28 Example: 4 slaves with addresses #1, #10, #11 and # slave addr. #254 slave addr. #11 slave addr. #1 slave addr. #10 control unit 0 SYNCCNT_P SYNCCNT_P Ring delay = Σtrep + Σtcable + safety margin Determine the SYNC time with Ring P1 P2 Ring delay is calculated by the master and transmitted to all slaves Every slave has a SYNC counter on P1 and P2

29 (c) SERCOS International 2009No Ring delay = 120 SYNCCNT_P1= 100 SYNCCNT_P2= 20 SYNCCNT_P1= 80 SYNCCNT_P2= 40 SYNCCNT_P1= 50 SYNCCNT_P2= 70 SYNCCNT_P1= 15 SYNCCNT_P2= 105 #10 #1 #11 # Slave_P1 2. Slave_P1 3. Slave_P1 4. Slave_P1 4. Slave_P2 3. Slave_P2 2. Slave_P2 1. Slave_P2 Determine the SYNC time Example with Ring SYNC ref time for all slaves

30 Hot-plugging

31 (c) SERCOS International 2009No. 31 Hot-plugging Hot-plug phases (HP0 to HP2) CP0 NRT mode MDT0-CP0 1 Start HP0 MDT0-CP4 HP2 HP1 CP3 OL = no MDT0-CP0 within 65 ms 2 = HP Slave activates Loopback Master commands FF to last slave 3 = Master switches from HP field to SVC 4 = Master activates timing of CP3/4 (S ) 5 = Master activates operation mode (S ) CP0 = Communication phase 0 NRTmode = non real-time mode HP = Hot-plugging OL = Operation level OM = Operation mode 4 CP4 OM S S  Hot-plugging is possible with line only  with ring, a ring break has to initiated first  Hot-plug function active on one channel only (P or S)  Master shall be prepared for the HP slave  Hot-plugging consists of 3 phases (HP0 to HP2)

32 IP Communication (NRT-Channel)

33 (c) SERCOS International 2009No. 33 IP Communication General Master P1 P2 Line Slave 2 P1 P2 Slave 3 P2 P1 Slave 1 P1 P2 primary or secondary channel S III Telegrams and IP Telegrams IP Telegrams only Collision Buffer  Collision Buffer is available in each slave  PC receives S III telegrams and IP telegrams  PC transmits IP telegrams only

34 (c) SERCOS International 2009No. 34 IP Communication Ring topology I/O IP Ethernet (Office) PC1 Master P1P2

35 (c) SERCOS International 2009No. 35 IP Communication NRT-Plug with ring topology P1P2 NRT-Plug Standard Industrial Ethernet Switch Function of NRT-plug: - Only the NRT-channel is processed - Real-time telegram passes through / are forwarded Ethernet NRT domain SERCOS III

36 (c) SERCOS International 2009No. 36 IP Communication Line topology Master I/O IP PC3 P1P2 PC2 PC1 Ethernet (Office)

37 (c) SERCOS International 2009No. 37 I/O IP  Download/Upload via NRT-channel in non-real-time mode in line topology  PC is connected to a unused port IP Communication Commisioning without S III communication

38 Parameter Model Device Model

39 (c) SERCOS International 2009No. 39 Introduction to IDNs (1) SERCOS III Slave Device SERCOS Communication Profile Generic Device Profile FSP IO FSP Drive … Communication SERCOS III Master Device Communication Application & Communication Functions Mapped to IDNs SERCOS III IDN = Identification Number

40 (c) SERCOS International 2009No. 40 Introduction to IDNs (2): Example of IDNs  S Communication Cycle time (tScyc)  S Allowed MST losses in CP3/CP4  S Error counter Port1 and Port2  S SERCOS address  …. SCP  S Diagnostic number  S Diagnosis trace  …  S Position command value  S Velocity feedback value  …  S Digital Input  S Analog Output  … GDP FSP Drive FSP I/O

41 (c) SERCOS International 2009No. 41 Introduction to IDNs (3) SERCOS III Slave Device Communication SERCOS III Master Device Communication S S S-0-…. S S S-0-…. S S S-0-…. S S S-0-…. SCP GDP FSP Drive FSP I/O S S

42 (c) SERCOS International 2009No. 42 Introduction of 32-bit IDNs SERCOS II SERCOS III

43 (c) SERCOS International 2009No. 43 IO Addressing schema

44 Performance

45 (c) SERCOS International 2009No. 45 Communication performance 20 slaves with S II 10 slaves with S II 1) without NRT channel 2) with NRT channel: 1500 bytes = 125 µs 3) with NRT channel: 250 bytes = 20µs

46 Conclusion

47 (c) SERCOS International 2009No. 47  Communication redundancy (recovery time < 25 µs!)  Direct cross-communication (without master involvement)  Controller to Controller (C2C)  Slave to Slave (CC)  Standard TCP/IP communication  without additional hardware  without running S III Communication  Hot-plugging of slaves during operation  SERCOS SoftMaster supports standard Ethernet Controller when < 1µs determinism is not required. Technical characteristics (1) Top 5 differentiating advantages

48 (c) SERCOS International 2009No. 48 Technical characteristics (2) More advantages of SERCOS III  Diagnosis with standard sniffer-tools (freeware): telegram data recording within the topology (e.g. Ethereal / Wire shark), SERCOS III Plugin available  Physical and Logical addressing (up to 511 Slaves)  Physical addressing is used during initialization  Logical addressing is used in operation and parameter setup  Easy migration from SERCOS II to SERCOS III  Reduction of bus systems - one bus for all field devices  Cost reduction with CAT5e Cabling  Higher transmission rate (~ 6x faster than SERCOS II)

49 (c) SERCOS International 2009No. 49 SERCOS III SERCOS III – Ethernet based Real-time Communication for Motion, Safety and I/O Thank You for Your Attention More Questions?


Download ppt "SERCOS III Technical Introduction SERCOS Seminar, Atlanta September 16, 2009."

Similar presentations


Ads by Google