Peter J Eriksson, BU RP Technology Management/Partner Technology Forum, Network Communication and Field busses

Size: px

Start display at page:

Download "Peter J Eriksson, BU RP Technology Management/Partner Technology Forum, Network Communication and Field busses"

Arleen Gaines
7 years ago
Views:

1 Peter J Eriksson, BU RP Technology Management/Partner Technology Forum, Network Communication and Field busses March 4, 2009 Slide 1

2 Content Introduction History Case studies Trends Current Status Generic Communiation (Socket, FTP, Robot API (Windows) Field bus Protocols (ProfiNet, Ethernet/IP Other info (DeviceNet Lean, etc) Future Workshop March 4, 2009 Slide 2

3 History IO and Communication Local IO Field bus IO Ethernet IO Serial RS232 Ethernet (Option) Ethernet Standard March 4, 2009 Slide 3

4 Case A Traditional Communication architecture Plant control MIS/MES Ethernet Station control Profibus DP Complex devices Weld Controller Standard IO Safety IO Simple devices DeviceNet March 4, 2009 Slide 4 Robot-Tool Operator Light Screen E-Stop

5 Case B Unified communication architecture ERP Plant control Ethernet Station control Complex Devices Weld Controller Simple Devices Robot-Tool Field bus coupler E-Stop Operator Light Screen March 4, 2009 Slide 5

6 Overview Robot Controller Communication Strategies Client e.g. Pendant, RobotStudio, OPC Client, RAP, Client initiate Communication IRC5 Robot Server and Sensor/Process Client IRC5 initiate Device Communication Servers e.g. I/O, Sensors, Process Control, March 4, 2009 Slide 6

7 Client Communication IRC5 Socket FTP RobAPI Windows based solutions RAB OPC Integrated in ABB tools e.g. RobotStudio, Pickmaster, Signal interface System inputs/outputs (field bus) March 4, 2009 Slide 7

8 Device Communication IRC5 Traditional Field buses Special Ethernet protocols for integrating device specific communication e.g. tracking sensors, vision, Ethernet based Field buses March 4, 2009 Slide 8

9 PROFINET in IRC5 Master / Slave (Controller / Device) solution uses Siemens CP1616 (DSQC 678) Step 7 configuration software. PROFINET option support 30 I/O units. PROFINET option allows 8192 I/O signals. Slave (Device) only solution uses the PROFINET Fieldbus Adapter (DSQC 688) from HMS. Step 7 configuration software (or equivalent) ProfiNet IO Device 512 IN / 512 OUT Signals RJ45-Connector Plug-in Module March 4, 2009 Slide 9

10 PROFINET in IRC5 Configuration DSQC 678 master configuration is done in two steps Create a project in Siemens Step 7 that reflects the hardware setup and download the configuration to the flash memory of the DSQC 678. Add I/O unit and signal configuration to the IRC5 controller using Robot Studio. March 4, 2009 Slide 10

11 PROFINET in IRC5 Configuration All units are of type PN_GENERIC Unit parameters is configured in Step 7 Input / output size as well Profinet Address in Robot Studio is Device address in Step 7 March 4, 2009 Slide 11

12 PROFINET in IRC5 Configuration The Internal PROFINET slave (Device) of the DSQC 678 is configured in Robot Studio. Add a unit of type PN_INTERNAL_SLAVE Modify the unit type PN_INTERNAL_SLAVE to set different input / output size. March 4, 2009 Slide 12

13 PROFINET in IRC5 Configuration The DSQC 688 is configured in Robot Studio. Need PROFINET configuration software to set IP address. DSQC 688 is supplied with a custom ABB GSDML file for PLC users. An integrated 2 port switch version soon available. Configure a unit with unit type PN_SLAVE_FA. March 4, 2009 Slide 13

14 PROFINET in IRC5 Configuration Modify the PN_SLAVE_FA unit type to change input / output size. March 4, 2009 Slide 14

15 EtherNet/IP in IRC5 Master / Slave solution uses a software stack running on the main computer. Ethernet ports Integrated LAN port DSQC 612 IPC Card (Multimove). CIP routing to DeviceNet or DeviceNet Lean Slave only solution uses the EtherNet/IP Fieldbus Adapter (DSQC 669) from HMS. CIP routing to DeviceNet or DeviceNet Lean 512 IN / 512 OUT Signals RJ45-Connector Plug-in Module March 4, 2009 Slide 15

16 EtherNet/IP in IRC5 Configuration The software solution is configured thru Robot Studio. Will support the COCO object. User need some unit information contained in the EDS-file. Three predefined unit types: EN_SLAVE IRC5 -> IRC5 / Generic I/O module EN_INTERNAL_SLAVE Opens our internal slave. EN_FA Predefined unit for connections against a DSQC 669 March 4, 2009 Slide 16

17 EtherNet/IP in IRC5 Configuration When configuring an I/O unit: Make a copy of unit type EN_SLAVE Change parameters according to EDS-file. March 4, 2009 Slide 17

18 EtherNet/IP in IRC5 Configuration Configured in Robot Studio: Set IP-address of the Fieldbus Adapter by edit the bus parameter EtherNet/IP Address. Add a unit of unit type EN_SLAVE_FA March 4, 2009 Slide 18

19 EtherNet/IP in IRC5 Configuration Change input / output size by edit the unit type EN_SLAVE_FA March 4, 2009 Slide 19

20 DeviceNet Lean DeviceNet Lean is configured in Robot Studio. DeviceNet master software solution with passive hardware board (DSQC 572). Supports up to 6 DeviceNet I/O units. Must be of ABB unit types (DSQC 651, 652 or 653) March 4, 2009 Slide 20

21 I/O System Changes Robotware 5.12 PROFINET option support 30 I/O units instead of max 20. PROFINET option allows 8192 I/O signals. Digital Output signals can be configured to Read Only. Possible to make cross connections with Group signals. RAPID now support 32-bit signals (before 24 bit). March 4, 2009 Slide 21

22 Summary All units connected via a common network Common infrastructure All types of communication Real-time, Safe, Diagnostics, Supervision, Control, Seamless and fast data access across complete factories/companies Integration of existing fieldbuses New threats March 4, 2009 Slide 22

23 March 4, 2009 Slide 23

Using the AnyBus -X Gateway to Communicate between a DVT camera and a Profibus Master

Using the AnyBus -X Gateway to Communicate between a DVT camera and a Profibus Master Page 1 of 13 Table of Contents 1 OVERVIEW... 3 2 INSTALLING AND CONFIGURING THE ANYBUS -X GENERIC GATEWAY AND ETHERNET