SAFphire Application Notes

(1)

(2)

(3)

Introduction to SAFphire Application Notes

This collection of SAFphire Application Notes is designed to aid SAFphire users and SBL Programmers in the design of SAFphire systems. These App. Notes are designed to explain how to use SAFphire to accomplish a specific task. Typical App Note Topics Include:

communicating between SAFphire and a specific PLC or MMI connecting SAFphire to a specific external device

performing a specific software function in SBL

These App Notes will show very specific examples, but can be modified to suit individual applications.

Assumptions

It is assumed that the reader will be familiar with SAFphire basics as well as SBL programming. This manual is designed to allow the reader to very quickly learn advanced topics after the basics have been mastered.

SAFphire RS232 Communications Overview

The CA418 Processor Card for SAFphire and the OEM SAFphire allow for communications using industry standard protocols without adding

additional SAFphire hardware. This allows for a cost effective connection to PLC's MMI's or other compatible devices.

Communications to other devices is achieved by using one of the on board serial ports of the processor card. (processor card refers to either a CA418 or to an OEM SAFphire) Because the onboard serial ports are RS232 ports, only point to point connections are supported. The actual communications supported is a subset of the full protocol. Please see the appropriate App Note for implementation details.

Supported Protocols

Supported protocols include:

• Allen-Bradley DF1

• Modicon Modbus RTU Master

• Modicon Modbus RTU Slave

Other communication networks are available for SAFphire by using the CA414 SAF-Link communications Gateway.

(6)

The above configuration would be used for communicating to both a programming computer and the handheld terminal

The above configuration would be used to communicate to both a PLC or MMI and the Hand Held Terminal at the same time.

(7)

registers and 64 write registers that can be transferred between SAFphire and the PLC or MMI.

These registers are accessed from the SBL program by using either a COMM READ REG block or a COMM WRITE REG block. Diagnostic information is available from a COMM STATUS block. For more information on using the individual blocks, please consult the Block Description Manual. All individual protocol parameters, i.e. baud rate, parity, etc. are not configurable. Please consult the appropriate App Note for individual protocol parameters. Both ports are accessed using the same COMM READ REG and COMM WRITE REG blocks. This allows a change in hardware configuration without changing the program.

(8)

SAFphire Ethernet Communications

The CA418 Processor Card for SAFphire supports 10 MegaBaud ethernet communications between racks and for programming / annunciating. Physical connection to SAFphire can be made directly by using

Unshielded Twisted Pair (UTP) cable with a RJ45 connector(10BaseT), or if a different physical medium is preferred, an AUI port is provided.

Convertors can be purchased to convert AUI to any other physical meduim.

The communication protocol used is IP. The IP address of each SAFphire is 192.168.250.Node. Node refers to the SAFphire Node Address which is set by SW1 and J7 (1-31).

Note: For more information on switch settings, see CA418 Hardware Description.

(9)

kbytes per seconds can be achieved. When used for annunciating, update times of 5 msec. are achievable. In order to communicate to SAFphire from SBL for Windows, the computer must have an ethernet card with the TCP/IP protocol installed.

TCPIP Protocol Installation

Using Windows 95 Control Panel, select Network.

Check to see if TCP/IP is listed as one of the installed network components

(10)

The Select Network Component Type Dialog Box will appear. Select Protocol, select ADD

(11)

Select the newly installed TCP/IP protocol and select properties. If only using the TCP/IP protocol for SAFphire communications, the only property that needs to be modified from default is the IP Address. Select the IP Address TAB, select Specify an IP address, change the IP Address to 192.168.250.X, where X is in the range of 33 to 254. This IP Address must be unique from other computers on the network. Set the Subnet Mask to 255.255.255.0. If TCP/IP is being used for more than SAFphire communications, please contact your network administrator for proper settings of the TCP/IP properties.

(12)

Configuring SBL

To configure SBL for Windows for Ethernet Communications, select Options, Communications. Change the Protocol to UDP (the portion of IP that SBL uses).

Select Setup, leave the Base IP Address at the default of 192.168.250.0,

select OK,

At this point if the communication module is successfully installed, the following dialog box will appear. Select OK, OK to return to SBL.

(13)

Rack to Rack Communications

The built-in Ethernet port of the CA418 can be used to provide fast, deterministic Rack to Rack communications. SAFphires that are

connected together on an ethernet network can broadcast Global Data to all other nodes on the network. Each node has 128 Global Data registers that are accessed by GLOBAL WRITE blocks. Each node can access the Global Data transmitted from any other nodes using GLOBAL READ blocks. Multiple SAFphires on the same ethernet network must all have unique node numbers as set by SW1 and J7.

Note: For more information on switch settings, see CA418 Hardware Description.

The frequency of the transmission of each nodes Global Data (if present) is determined by the total amount of global data present on the network. The following table indicates the time between successive transmissions of global data from any node. Because the transmissions are

synchronous to the block program scans, the following times are

minimums. Maximum times may be up to one program scan time longer

Total Global Data (words) Time between transmissions (Msec.) 250 5 500 10 1000 20 4096 82

Each GLOBAL READ and GLOBAL WRITE block, reads or writes 8 words.

The total Global Data can be calculated by simply summing the amount of Global Data transmitted by individual nodes on the network. The amount of Global Data transmitted by any individual node is equal to the largest offset in any of the Global Write blocks + 8. If no GLOBAL WRITE blocks are present, no Global Data is transmitted. For this reason, the first GLOBAL WRITE block should have an offset of 0, the second 8 etc. up to a maximum offset of 120 (128 registers minus 8)

(14)

READ block has a STATUS output that will be ON if error free Global Data has been received from that node within the last 250 ms.

Note: In order to minimize collisions, retries and possibly TIME OUTs due to an excessively loaded network, a dedicated ethernet network should be used for SAFphire.

SBL Programming

(15)

The following block will check the above blocks for a communication timeout.

Note: only one status from each node must be checked.

(16)

SAFphire to Allen-Bradley PLC Communications

Using DF1

The CA418 Processor Card for SAFphire and the OEM SAFphire allow for direct communications to Allen-Bradley PLC's using the DF1 protocol. DF1 is a full-duplex, point to point, RS232 communication link found on many Allen-Bradley PLC's. SAFphire will respond to messages initiated by a PLC. Using DF1, up to 64 words in both directions, can be

transferred between a PLC and SAFphire. The following example transfers 64 words in both directions between a SLC504 and SAFphire. The PLC initiates all communications, with MSG blocks. Both the COMM READ REGISTERS and the COMM WRITE REGISTERS in SAFphire are mapped into N7:0. Doing reads or writes outside the range of N7:0 -N7:63 will give error responses.

SBL Configuration

DF1 Communications is available on either the HAND TERMINAL PORT or the DOWNLOAD PORT. Setting the

appropriate switch (SW2 for the DOWNLOAD PORT, SW3 for the HAND TERMINAL PORT) to a setting of 1 will enable DF1 communications.

(17)

The following 4 blocks will load the first 32 COMM WRITE registers with data. This data is then read by the PLC as N7:0-N7:31. Four more blocks with offsets of 32, 40, 48, 56, would be required to load all 64 words with data

(18)

The following 4 blocks will read data from the first 32 COMM READ registers. This data must be sent from the PLC as a write to N7:0-N7:31. Four more blocks with offsets of 32, 40, 48, 56, would be required to read all 64 words.

(19)

PLC Configuration -SLC Family

The PLC must have its RS232 port (also referred to as PROG TERM or CHANNEL 0) configured as follows

The actual transfers of data occur using 2 MSG blocks.

The ENABLE of the control block for the MSG instruction (bit 15 of the first word of the Control Block) is unlatched by the logical OR of the DONE (bit 13 of the first word of the Control Block) with the ERROR (bit 12 of the first word of the Control Block)

The example rungs will continuously read 64 words from SAFphire at N7:0 and place them into N9:0. Also 64 words from N9:80 will be written to SAFphire at N7:0. Even though both the READS and WRITES use N7:0,

(20)

The following rungs will read 64 words from SAFphire at N7:0 to N9:0

The Setup Screen for the MSG Block is as follows. The Target Node is irrelevant as SAFphire will respond to all nodes.

SAFphire only acknowledges messages with PLC5 addressing (Target Device must be set to PLC5)

(21)

The following rungs will write 64 words from N9:80 to SAFphire

The Setup Screen for the MSG block is as follows

The Target Node is irrelevant as SAFphire will respond to all nodes. SAFphire only acknowledges messages with PLC5 addressing (Target Device must be set to PLC5)

(22)

PLC Configuration -PLC 5 Family

Newer PLC 5s have an additional file of type MG (message file). This should be used as the source of the Control Block. If your PLC 5 does not have files of type MG, please follow the SLC example.

The PLC must have its RS232 port (also referred to as PROG TERM or CHANNEL 0) configured as follows

The actual transfers of data occur using 2 MSG blocks.

The ENABLE of the control block for the MSG instruction is unlatched by the logical OR of the DONE with the ERROR

(23)

The following rungs will read 64 words from SAFphire at N7:0 to N9:0

The Setup Screen for the MSG Block is as follows. The Target Node is irrelevant as SAFphire will respond to all nodes.

SAFphire only acknowledges messages with PLC5 addressing (Command must be a PLC5 Typed Read)

(24)

The Setup Screen for the MSG block is as follows

The Target Node is irrelevant as SAFphire will respond to all nodes. SAFphire only acknowledges messages with PLC5 addressing (Command must be a PLC5 Typed Write)

(25)

Compatible Devices

Compatible devices include SLC503, SLC 504, MicroLogix controllers, and the PLC5 family of A-B processors.

NOTE: To ensure proper operation of the MSG instruction, upgrade the firmware of the PLC to the latest version available from A-B.

Connections

The RS232 port of A-B PLC's can be in the form of either a DB9 Male or a DB25 Female connector (a MiniDin style connector may also be available) Because no handshaking lines are used, only 3 terminals must be

connecting. Connecting other terminals normally used for handshaking signals will not cause problems.

DB9 Male (PLC) DB9 Male (SAFphire)

2 - Receive Data 3 - Transmit Data 3 - Transmit Data 2 - Receive Data 5 - Common 5 - Common

DB25 Female (PLC) DB9 Male (SAFphire)

NOTE: PLC5s can be configured for either RS422/485 or RS232 operation. (typically through DIP SWITCHES). Ensure RS232 is selected.

(26)

SAFphire to Modicon PLC Communications Using

Modbus

The CA418 Processor Card for SAFphire and the OEM SAFphire allow for direct communications to Modicon PLCs or other compatible devices using Modbus RTU. When connected to Modicon PLCs, SAFphire acts as a master on the network with the PLC being a slave device.

Modbus RTU is a point to point, RS232 communication link found on many Modicon PLC's. SAFphire will initiate both READ HOLDING REGISTERS (0x03) messages and PRESET MULTIPLE HOLDING REGISTER (0x10) messages. Using MODBUS, up to 64 words total can be transferred between a PLC and SAFphire. The following example transfers 32 words in both directions between a Modicon PLC and SAFphire. SAFphire initiates all communications (master). SAFphire COMM READ REGISTERS and the COMM WRITE REGISTERS are mapped to holding registers 40001 to 40064 in the PLC.

SBL Configuration

(27)

The following 4 blocks will write data to holding registers 40001 to 400032 in the connected PLC.

(28)

The following 4 blocks will read data from the holding registers 40033 to 40064 of the connected PLC.

NOTE: A block offset of 32 will read from holding register 40033-40040

(29)

The PLC must have its RS232 port configured for Modbus RTU (not ascii). The PLC Address must be 1. The RS232 settings must be EVEN parity, 8 data bits, 1 stop bits. The baud rate setting must match the switch settings on SAFphire.

Note: Modicon Micro PLC's do not support communications at 19200 baud

Compatible Devices

Compatible Modicon devices include the Micro, 984, and Quantum families of PLCs. Many other manufacturers also support Modbus communications.

Connections

The RS232 port of Modicon PLC's can be in the form of either a DB9 Female or a RJ45 Modular Connector. Modicon supplied cables are available for RJ45 to DB9 conversion. Because no handshaking lines are used, only 3 terminals must be connecting. Connecting other terminals normally used for handshaking signals will not cause problems.

DB9 Female (PLC) DB9 Male (SAFphire)

(30)

SAFphire to Man-Machine-Interface Communications

Using Modbus

The CA418 Processor Card for SAFphire and the OEM SAFphire allow for direct communications to Man Machine Interfaces (MMIs) or other

compatible devices using Modbus RTU. When connected to MMIs SAFphire acts as a slave device on the network with the MMI being a master device.

SAFphire is also capable of being a Modbus Master device. See SAFphire to Modicon PLC App Note for more information.

Modbus RTU is a point to point, RS232 communication link available with most MMIs. SAFphire will reply to READ HOLDING REGISTERS (0x03) messages, PRESET SINGLE HOLDING REGISTER (0x06), and

PRESET MULTIPLE HOLDING REGISTER (0x10) messages. Using MODBUS, up to 64 words total can be transferred between a MMI and SAFphire. The following example transfers 32 words in both directions between a MMI and SAFphire. SAFphire only responds to MMI initiated messages (slave). SAFphire COMM READ REGISTERS and the COMM WRITE REGISTERS are presented to the MMI as to holding registers 40001 to 40064.

(31)

The following 4 blocks will write data that can be read as holding registers 40001 to 400032 from the MMI.

(32)

The following 4 blocks will read data that was written to holding registers 40033 to 40064 by the MMI.

NOTE: A block offset of 32 will read data written to holding register 40033-40040

(33)

Compatible Devices

Compatible devices include most MMI devices on the market

Connections

The connections for the RS232 ports of SAFphire are shown below. If the MMI requires the use of handshake signals (RTS, CTS, DTR, DSR), these must be connected internally to the MMI. Connecting other terminals normally used for handshaking signals will not cause problems.

DB9 Male (SAFphire)

3 - Transmit Data 2 - Receive Data 5 - Common

(34)

SAF to ABB Drives Communications Using DDCS

(point to point connection)

DDCS is an ABB communications network implemented with fibre optics at 4 Mbaud. It is typically used for communications between SAFphire and an ABB Drive. Suitable SAFphire devices include an OEM SAFphire or a SAFphire with a CA417 or CA419. Suitable ABB drives include ACS600 and DCS500.

SAFphire

OEM SAFphire

D D C S

ACS600

O I FUS E FU SE FU S E C BI TBUS™ D _ D R _ R RC POWER 8044 STATUS 320 STATUS 1 2 3 4 5 6 CA408 M ULTI PROCESSOR CARD HAND TERMINAL CA409 SAF BUS TERMINATI ON/ FAULT RELAY CARD STATUS 1 2 CA401 DI GI TAL I NPUT CARD SAF BUS STATUS I NPUTS A C T IV E IN P U T S 1 2 3 4 5 6 78 -9 10 11 12 13 14 15 16 -1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 CA402 DI GI TAL OUTPUT CARD SAF BUS STATUS OUTPUTS ACT I V E O U T P UT S 1 23 4 5 6 7 8 -9 10 11 12 13 14 15 16 -1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 CA403 MULTIPLE I NPUT/ OUTPUT CARD SAF BUS STATUS I / P A2 O/ P2 O/ P1 I / P B2 I / P A1 I / P B1 1 13 7 19 2 14 8 20 3 15 9 21 4 16 10 22 5 17 11 23 24 6 18 12 CA403 MULTIPLE I NPUT/ OUTPUT CARD SAF BUS STATUS I / P A2 O/ P 2 O/ P 1 I / P B2 I / P A1 I / P B1 1 13 7 19 2 14 8 20 3 15 9 21 4 16 10 22 5 17 11 23 24 6 18 12 1 2345 6 7 8 1 23456 78 7 6 5 4 3 2 1 CA410 MODBUS PLUS™ I NTERFACE CARD 1 1 2 2 3 3 4 4 5 5 6 6 7 7 8 8 NO DE I D M O DBUS P L U S CO NF IG PS C A A _ B B _ M M _ C PS I C C 1 2 3 4 5 6 7 8 9 10 11 12 13 CA407 DRI VE I NTERFACE/ ENCODER CARD TO C A 3 8 3 C A R D SAF BUS STATUS PS C A A _ B B _ M M _ C PS I C C 1 2 3 4 5 6 7 8 9 10 11 12 13 CA407 DRI VE I NTERFACE/ ENCODER CARD TO C A 3 8 3 C A R D SAF BUS STATUS

(35)

Implementation

DDCS is a master, slave protocol. The OEM SAFphire , CA417 or CA419 card is always the master and is assigned node 0. When using a CA417 card, the ACS600 or DCS500 drive should be configured as node 1 (node 1 is default setting). Both the OEM SAFphire and the CA419 support multiple nodes on the same channel in a ring configuration. This allows the node to be set in the range of 1 to 8.

Information is exchanged in the form of datasets. A dataset consists of three 16 bit words (-32768 to 32767). Multiple datasets exist in the drive and are distinguished by number. Odd number datasets (i.e. 1,3and 5…) are written from the master to the slave (from SAFphire to the drive), whereas even number datasets (i.e. 2,4 and 6…) are read from the slave by the master (from the drive to SAFphire). Datasets are always used in pairs (i.e. 1&2, 3&4, 5&6). One pair of datasets provides 3 words of communications in both directions.

NOTE CA417 ONLY (When using more than one pair of datasets they

must be used in numeric order. Therefore using datasets 1&2 and 3&4 is valid but using datasets 1&2 and 5&6 is not valid and erroneous data will be passed back and forth. A maximum of 3 datasets (9 words) can be passed each way.)

The number of datasets available from a given drive and their contents, is variable. With the DDCS protocol, one pair of datasets is updated every millisecond. If a slave device with one pair of datasets is being used, those datasets will be updated every millisecond. If a slave device with two pairs of datasets is being used, 1 pair of datasets will be updated every millisecond for a total update time of 2 milliseconds.

Connections

Hardware connection consists of two fiber optic cables. The first cable connects the transmitter of one device to the receiver of the second device. The second cable connects the receiver of the first device to the transmitter of the second device. Typically both fiber optic cables are bundled into one physical package (duplex cable). The two cable ends (transmitter and receiver) are colour coded. Insert the cable into the like coloured connector.

(36)

SBL Block Programming

The following blocks would be used in the OEM SAFphire to read and write one pair of datasets to a ABB Drive setup as node 1. When acting as a master the node input of the DDCS blocks represents the node that you are requesting data from or writing data to.

(37)

The following blocks would be used in the SAFphire to read and write one pair of datasets to a ABB Drive setup as node 1. The card address input refers to the SAF Bus address being used by the CA417 or CA419 card. This input must match the setting of SW1 on the card. Valid addresses are 0-3 for a CA417 and 0-15 for a CA419.

(38)

SAFphire to DCS500B drive

When using a DCS500 Drive, an additional communications board must be installed in the drive for DDCS communications. Either a COM1 or a COM5 board are suitable. A DCS500B Drive comes complete with the DDCS port included with the Drive. No additional communication board is required.

A standard DCS500B drive has 4 Data Sets (1-4). Connect the onboard DDCS port of the DCS500B drive to the DDCS channel of SAFphire. The DDCS Node number of the drive is set in parameter 12.13. This must be 1 (default) when communicating to a CA417 card or equal to the NODE input of the DDCS blocks when using a CA419 card or OEM SAFphire. Data Sets 1 and 3 are used to send data from SAFphire to the drive. The parameters that contain the data from the Data Sets are shown below.

Data Set Word Parameter

DataSet 1 Word 1 10122 DataSet 1 Word 2 10123 DataSet 1 Word 3 10124 DataSet 3 Word 1 10125 DataSet 3 Word 2 10126 DataSet 3 Word 3 10127

In order to convert from a word to 16 individual bits, a function block must be enabled in the drive.

NOTE: These instructions are written for a DDCS500B drive with firmware version 21.226. The firmware version of a particular drive can be found in parameter 112.18 CNT SW VERSION. The parameter numbers will be the same as far back as 21.105. For parameter numbers for future versions of firmware, or more information on function block programming, consult the APPLICATION BLOCKS for

DCS500 Standard Drives Manual from ABB.

1) Using the Keypad, press FUNC followed by the double up arrow key then ENTER

2) Select (up/down arrows) ADD FUNCTION BLOCK, press ENTER 3) At the ENTER TASK NUMBER prompt press ENTER for TASK 1 (the

fastest task time)

4) Using the double arrow keys select the first CONV IB (convert integer to bit) function block (442), press ENTER.

(39)

8) Tune parameter 25.04 FB_APPL_ENABLE to 1 to enable the added function blocks.

9) Tune parameter112.02 BACKUPSTOREMODE to SAVE MOT SET1 to save all changes

10) Cycle Power

11) The individual bits are now available in parameters 129.61 to 129.77 Data Sets 2 and 4 are used to send data from the drive to SAFphire. The parameters used to select which data is to be sent to SAFphire are shown below

Data Set Word Parameter

DataSet 2 Word 1 209 DataSet 2 Word 2 210 DataSet 2 Word 3 211 DataSet 4 Word 1 212 DataSet 4 Word 2 213 DataSet 4 Word 3 214

If individual bits are to be sent to SAFphire, They must first be converted to a word.

1) Using the Keypad, press FUNC followed by the double up arrow key then ENTER

2) Select (up/down arrows) ADD FUNCTION BLOCK, press ENTER

3) At the ENTER TASK NUMBER prompt press ENTER for TASK 1 (the fastest task time)

4) Using the double arrow keys select the first CONV BI (convert bit to integer) function block (445), press ENTER.

5) At the ENTER FB TAST POS prompt, press ENTER (selecting the next available function block position)

6) Select (up/down arrows) TERMINATE FB PROGR, press ENTER

7) The Function block is now added, its inputs must now be connected before the outputs can be used.

8) Press PAR on the Keypad, The inputs to the function block are found at parameters 33.17 to 33.35. Tune CONV-BI[S] (33.17) to 125.02(on), Tune CONV-BI[L] (33.18) to 125.01(off). Tune CONV-BI[R] (33.19) to 125.01(off). Tune CONV-BI[I1-i16] (33.20-35) to the parameters to be converted to a word.

9) Tune parameter 25.04 FB_APPL_ENABLE to 1 to enable the added function blocks.

(40)

Parameters of interest

Parameter Function

125.02 Always ON

(41)

SAFphire to DCS400 drive

A DCS400 Drive comes complete with the DDCS port included. Connect the onboard DDCS port (V800) of the DCS400 drive to the

DDCS channel of SAFphire. The DDCS Node number of the drive is set in parameter 2.10. This must be 1 (default) when communicating to a

CA417 card or equal to the NODE input of the DDCS blocks when using a CA419 card or OEM SAFphire.

Datasets From SAF to DCS400

Data Set Word Description Scaling Parameter

To enable DDCS 8.01 = “fieldbus

Bit0=drive on Command 2.02=“Bus”

Bit1=not coast Word 2.02=“Bus”

Bit2=e-stop Can 2.02=“Bus”

Bit3=drive run Be 2.02=“Bus”

Bit4=not used Monitored

Bit5=not used At Bit6=not used 2.05 Bit7=reset 2.02=“Bus” Bit8=jog 1 2.02=“Bus” Bit9=jog 2 2.02=“Bus” Bit10=not used Bit11=MCW BIT 11 9.05 Bit12= MCW BIT 12 9.05 Bit13= MCW BIT 13 9.05 Bit14= MCW BIT 14 9.05 DataSet 1 Word 1 Bit15= MCW BIT 15 9.05

DataSet 1 Word 2 Bus Main Ref 20000=max speed 3.14, 3.15,5.01,

DataSet 1 Word 3 Bus Aux Ref 4096=max cur 3.14, 3.15,5.01

DataSet 3 Word 1 Digital outputs 1-5 6.11-6.15 = 32

DataSet 3 Word 2 Analog Out 1 ±4096=±10V 6.05=9

(42)

Datasets From SAF to DCS400

Data Set Word Description Scaling Parameter

Bit0=rdy for on Status

Bit1=rdy for run Word

Bit2=running Can

Bit3=faulted Be

Bit4=not coast Monitored

Bit5=not e-stop At Bit6=not used 2.06 Bit7=alarm Bit8=at setpoint Bit9=remote Bit10=above limit Bit11=MSW BIT 11 6.22 Bit12=MSW BIT 12 6.23 Bit13=MSW BIT 13 6.24 Bit14=MSW BIT 14 6.25 DataSet 2 Word 1 Bit15=not used

DataSet 2 Word 2 Actual 1 20000=maxspeed

±4096=±10V ana in Set by 6.20

DataSet 2 Word 3 Actual 2 4096 = max curr

±4096=±10V ana in Set by 6.21

DataSet 4 Word 1 Fld Cur Act 4096 = nom.cur

DataSet 4 Word 2 Power Act 4096 = nom.power

DataSet 4 Word 3 Torque Act 4096 = 100%

The DCS400 detects a communication fault by monitoring for incoming messages. Even if the messages are erroneous or at the wrong baud rate the drive thinks everything is OK. Therefore if you only disconnect the transmitter from the drive the drive will not trip because it is still

receiving initialization messages at different baud rates from the Safphire. You must monitor the communication in SAFphire and externally trip the drive on a communication fault.

(43)

SAFphire to ACS600 release 5 Drive

Release 3 drives had the CH0 DDCS port included in the drive, release 5 drives require an NDCO card for DDCS communications to SAFphire. Connect CH0 from the NDCO card to SAFphire.

Parameter Settings

The ABB Manual for parameter descriptions for a standard drive is

ACS600 Firmware Manual – Standard Application Program 5.0

Most parameters are set according to the desired application. Some parameters that may be set differently or that have different options when using DDCS communications are shown below.

No. Parameter Default Optional Setting

98.02 COMM MODULE NO FIELDBUS

70.01 CHANNEL 0 ADDR 1 NODE NUMBER*

90.01 D SET 3 VAL 1 0 DATA POINTER1*

10.01 EXT1 STRT/STP/DIR D1,D2 COMM MODULE

10.02 EXT2 STRT/STP/DIR NOT SEL COMM MODULE

10.03 DIRECTION FORWARD REQUEST

11.02 EXT1/EXT2 SELECT EXT 1 COMM REF

11.03 EXT REF 1 SELECT AI1 COMM REF

11.06 EXT REF 2 SELECT KEYPAD COMM REF

14.01 RELAY RO1 OUTPUT READY COMM MODULE

14.02 RELAY RO2 OUTPUT RUNNING COMM MODULE

14.03 RELAY RO3 OUTPUT FAULT (-1) COMM MODULE

30.18 COMM FAULT FUNC FAULT FAULT

30.19 COMM FLT TIME OUT 1.00 s 1.00 s

30.20 COMM FLT RO/AO ZERO ZERO

*NODE NUMBER – This is the desired DDCS node number of the drive. This must match be 1 if using a CA417 card. If using OEM SAFphire or a CA419 card, this number must match the NODE input to the block.

*DATAPOINTER1 the function of the words in Data Set 3 are configurable by using pointers to the desired parameters to be written to. Setting a

(44)

SAF toACS600

DataSet Word Function

DataSet 1 Word 1 Bit 0 Enable (must see a OFF to ON transition after power up or after a fault

reset)

DataSet 1 Word 1 Bit 1 Reserved (turn ON)

DataSet 1 Word 1 Bit 3 Run

DataSet 1 Word 1 Bit 4 Zero Ramp Output (normal operation is ON)

DataSet 1 Word 1 Bit 5 Ramp Hold (normal operation is ON)

DataSet 1 Word 1 Bit 6 Zero Ramp Input (normal operation is ON)

DataSet 1 Word 1 Bit 7 Fault Reset

DataSet 1 Word 1 Bit 8 Reserved (turn off)

DataSet 1 Word 1 Bit 11 External Ctrl Loc (ON selects EXT CTRL 2, OFF selects EXT CTRL 1)

DataSet 1 Word 2 Speed Reference (-20000 to 20000 scaled to parameter 11.3 in ACS600

DataSet 1 Word 3 Torque Reference (see below for scaling)

Torque ref scaling – If the torque control macro is selected, The torque reference is scaled such that –10000 to 10000 is scaled to parameter 11.8. If the standard macro is selected, The torque reference is scaled such that –20000 to 20000 is scaled to parameter 11.8.

DataSet 3 Word 1 Bit 13 Relay Output 1 (if parameter 14.01 set to COMM MODULE)

DataSet 3 Word 2 Analog Output 1 (20000 = 20 mA) (if parameter 15.01 set to COMM

MODULE)

DataSet 3 Word 3 Analog Output 2 (20000 = 20 mA) (if parameter 15.01 set to COMM

MODULE) ACS to SAF

DataSet 2 Word 1 Bit 0 Ready to switch ON

DataSet 2 Word 1 Bit 1 Ready to Operate

DataSet 2 Word 1 Bit 2 Operation Enabled

(45)

DataSet 2 Word 1 Bit 15 DDCS error

DataSet 2 Word 2 Parameter Selected by 92.02

DataSet 2 Word 3 Parameter Selected by 92.03

See ACS600 Firmware Manual – Standard Application Program 5.0 Appendix C for more information on Control and Status words. These datasets are for a standard drive. Custom firmware is available that may have different datasets. Consult the vendor for information on custom firmware.

Multi Node DDCS Communications

Note: Users without basic DDCS knowledge should first consult the SAFphire to ABB Drives Communications App Note.

Multi Node DDCS communications can be used to communicate from one DDCS master to multiple DDCS slaves connected in a ring configuration. Suitable DDCS Master devices OEM SAFphire. Suitable DDCS Slave devices include ACS600 drives, DCS500 drives, OEM SAFphires or a SAFphire with a CA417 card (node 1 only).

The master and slave nodes will be connected in a ring configuration. The transmitter of the master is connected to the receiver of the first slave. The transmitter of the first slave is connected to the receiver of the next slave. This continues until the transmitter of the last slave is

connected to the receiver of the master.

The update time for the DDCS protocol is one pair of datasets per node per 1 msec. A network of one slave device and using only one pair of datasets will have an update time of 1 msec. A network with 2 slave devices, each with 2 datasets, will have an update time of 4 msec

The node number of an ACS600 drive is controlled from parameter 60.5

OEM SAFphire Network OEM SAFphire & ABB Drives

Master(node 0) Slave(node 3)

Slave(Node 1) Slave(node2)

(46)

SBL Block Programming

The following 4 blocks would be used in the master node OEM SAFphire to read and write one pair of datasets to two slave devices setup as node 1 and node 2. When acting as a master the node input of the DDCS blocks represents the node that you are requesting data from or writing data to.

(47)

The following 2 blocks would be used in the slave OEM SAFphire (node 1) to reply to the master OEM

SAFphire’s request for data. When acting as a slave the node input on the DDCS blocks represents the slave node number that you would like the OEM SAFphire to be defined as.

The following 2 blocks would be used in the slave OEM SAFphire (node 2) to reply to the master OEM SAFphire’s request for data. When acting as a slave the node input on the DDCS blocks represents the slave node number that you would like the OEM SAFphire to be defined as.

(48)

SAFphire to SAFphire Communications Using DDCS

(point to point)

Note: Users without basic DDCS knowledge should first consult the SAFphire to ABB Drives Communications App Note.

DDCS can be used for communication between two DDCS capable SAFphire devices. DDCS capable devices include OEM SAFphire or a SAFphire with a CA417 card. DDCS is a master, slave protocol.

SAFphire with a CA417 card can be a master or a slave with a node number of 1. OEM SAFphires can be a master or a slave devices with a node number of 1-8. Information is passed between nodes in the form of datasets. Each dataset consists of three 16 bit words (-32768 to 32767), and is assigned a number. Odd number datasets (i.e. 1,3and 5) are written by the master node to the slave node. Even number datasets (i.e. 2,4 and 6) are read by the master node from the slave node. For this reason the datasets are always used in pairs (i.e. 1&2, 3&4, 5&6). When using more than one pair of datasets they must be used in numeric order. Using datasets 1&2 and 3&4 is valid but using datasets 1&2 and 5&6 is not valid and erroneous data will be passed back and forth. A maximum of 3 datasets (9 words) can be passed each way. The update time for the DDCS protocol is equal to one pair of datasets per msec. A network consisting of one slave device with one pair of datasets would be updated once every millisecond. If you are using two pairs of datasets each pair of datasets will be updated once every two milliseconds.

(49)

Connections

Hardware connection consists of two fiber optic cables. The first cable connects the transmitter of one device to the receiver of the second device. The second cable connects the receiver of the first device to the transmitter of the second device. Typically both fiber optic cables are bundled into one physical package (duplex cable). The two cable ends (transmitter and receiver) are colour coded. Insert the cable into the like coloured connector. OEM SAFphire and CA417 connections are shown below. Communications between CA417 and OEM SAFphire is also valid.

(50)

SBL Block Programming

OEM SAFphire Master

The following 4 blocks would be used in the master node OEM SAFphire to read and write two pairs of datasets to a DDCS slave setup as node 1. When acting as a master the node input of the DDCS blocks

represents the node that you are requesting data from or writing data to.

(51)

OEM SAFphire Slave

The following 4 blocks would be used in the slave OEM SAFphire to reply to the DDCS master

messages for datasets 1 and 2. When acting as a slave the node input on the DDCS blocks represents the slave node number that you would like the OEM SAFphire to be defined as.

(52)

SAFphire and CA417 as Master

The following 4 blocks would be used in the master CA417 to read and write two pairs of datasets to DDCS Slave configured as node 1. There is no node input because a master CA417 is always node 0 and can only communicate to node 1. The card address input refers to the card

address being used by the CA417 card. This input must match the setting of SW1 on the CA417 card (range is 0-3).

(53)

SAFphire and CA417 as Slave

The following 4 blocks would be used in the slave CA417 to reply to the DDCS master messages for datasets 1 and 2. There is no node input because a slave CA417 is always node 1. The card address input refers to the card address being used by the CA417 card. This input must match the setting of SW1 on the CA417 card (range is 0-3).

(54)

(55)

New Hamburg,ON Canada

N3A 4G7

TollFree:1-800 3 ASK SAF (Canada/US)

T

Tel:519-662-6489

Fax:1-866-280-5247

email:[email protected]

(56)

SAFphire Application Notes

Table of Contents

Introduction to SAFphire Application Notes

Assumptions

SAFphire RS232 Communications Overview

Supported Protocols

SAFphire Ethernet Communications

Rack to Rack Communications

SBL Programming

SAFphire to Allen-Bradley PLC Communications

Using DF1

SBL Configuration

PLC Configuration -SLC Family

PLC Configuration -PLC 5 Family

Compatible Devices

Connections

SAFphire to Modicon PLC Communications Using

Modbus

SBL Configuration

Compatible Devices

Connections

SAFphire to Man-Machine-Interface Communications

Using Modbus

Compatible Devices

Connections

SAF to ABB Drives Communications Using DDCS

(point to point connection)

SAFphire

OEM SAFphire

D D C S

D D C S

ACS600

ACS600

Implementation

Connections

SBL Block Programming

SAFphire to DCS500B drive

SAFphire to DCS400 drive

SAFphire to ACS600 release 5 Drive

Multi Node DDCS Communications

SBL Block Programming

SAFphire to SAFphire Communications Using DDCS

(point to point)

Connections

SBL Block Programming