SmartGuard QuickStartContents Loading USB drivers .......................................................................................................... 3 Configuring the USB driver in RSLinx .............................................................................. 7 Communicating to PVP600 over DeviceNet .................................................................... 13 Configure Communications between a PanelView Terminal and SmartGuard 600 Controller over and EtherNet/IP Network ........................................................................ 41 Configuring the SmartGuard 600 and DeviceNet safety I/O modules as standard slaves 45 Explicit Messaging of the SmartGuard 600 over DeviceNet............................................ 60 Explicit Messaging of the 1791DS modules from Logix ................................................. 66 Configure EtherNet/IP Target IO in RSNetWorx for DeviceNet Software ..................... 73 Setup EtherNet/IP Communications between a Logix5000 Controller and the SmartGuard 600 Safety Controller........................................................................................................ 77 Explicit Message of the SmartGuard 600 Controller over EtherNet/IP with a MicroLogix Controller .......................................................................................................................... 79 SmartGuard Wiring Diagrams: Common Safety Devices ................................................ 83 SmartGuard Quickstart 1 SmartGuard Quickstart 2 Loading USB drivers First, you will have to load the SmartGuard USB drivers onto your PC. The files are shown in the image below; in case you ever need to search for them. Note the folder you put them into, as you will browse to it later. Attach USB cable between SmartGuard600 and PC. The following Wizard should appear. SmartGuard Quickstart 3 Select; YES this time only, and click NEXT The following appears: SmartGuard Quickstart 4 SmartGuard Quickstart 5 .Select ‘Install from a list or specific location’ and select NEXT The following appears. the following image is simply an example of such a browse. and then the following window appears if successful. Select FINISH. Select OK. then NEXT The SmartGuard drivers are loaded.Browse to the folder that the SmartGuard USB drivers were placed into. SmartGuard Quickstart 6 . Obviously. 51 or later. Select Communications. SmartGuard Quickstart 7 . Configure Drivers.Configuring the USB driver in RSLinx Open RSLinx 2. SmartGuard Quickstart 8 .Select the ‘SmartGuard USB Driver’ from the ‘Available Driver Types’ pulldown. The following window appears. Select ‘Add New’. Select OK. Select ‘1752 SmartGuard USB Port’.There is a ‘Select Interface’ pulldown on this window with only one selection. The SmartGuard driver should now be running. Select OK. The MAC Address and Baud Rate should automatically fill in with the proper information if the SmartGuard is connected properly on the USB link. SmartGuard Quickstart 9 . The ‘OK’ button will highlight as well. The following window appears. SmartGuard Quickstart 10 . there is a single 1791DS safety I/O module on DeviceNet with the SmartGuard controller.Close the ‘Configure Drivers’ window. RSNetworx should as well. In this example. If RSLinx sees the nodes on DeviceNet. Open RSWho within RSLinx and select the SmartGuard driver (see below) to initiate browsing the DeviceNet network connected to the SmartGuard. The nice images of the 1791DS and SmartGuard (1752) show up because I had previously loaded the proper EDS files using the ‘EDS Hardware Installation Tool’. and hit the Online icon. When the following window appears. you will see the following message. create a new project. If you have created a new project in RSNetworx. SmartGuard Quickstart 11 . Hit OK. select the SmartGuard driver and hit OK.Open RSNetWorx. RSNetWorx also finds both the SmartGuard and 1791DS module on the DeviceNet network. SmartGuard Quickstart 12 . Note that the exclamation mark represents an issue with the safety network number of the 1791DS module. Hit the online icon again to put RSNetworx in Offline mode. The following from the SmartGuard users manual describes the limitations. SmartGuard Quickstart 13 . the controller can perform standard I/O communication with 1 standard master for up to 2 connections. The SmartGuard 600 is a DeviceNet slave. using up to 16 bytes per connection. As a standard slave.Communicating to PVP600 over DeviceNet PVP has a RN10C card that is the DeviceNet scanner. It is documented later in this document. Note that both Polled and COS/Cyclic allow both input and outputs (read and write) in a single connection.The two (2) connections can be selected from the 4 types. that can have an additional 16 Bytes as well. This configuration was tested and found to work. one (1) polled connection and one (1) COS connection can be made. A Polled connection that uses both inputs and outputs can have 16 Bytes of input data and 16 Bytes of output data. My testing discovered that if you use the Polled connection. This means that the maximum data configuration is as follows: This configuration allows 32 Bytes of input data (16 via Polled and 16 via COS or Cyclic) and 16 bytes of output data via the Polled connection. but not two (2) polled connections. SmartGuard Quickstart 14 . but only one connection of each type can be made. the output of this connection is grayed out. For example. And if you add a second connection. and then added a COS/Cyclic connection. In this case. SmartGuard Quickstart 15 . These 4 bytes are can be read by the PVP.How to read BOOLs from the SmartGuard and display them on the PVP600 Open up the SmartGuard Slave I/O configuration tab. Tags that are being read by the PVP should be entered into the IN tab. a single 4 byte tag has been created and will use a polled connection. SmartGuard Quickstart 16 . The sample SmartGuard code is controlling two (2) of the 32 bits. That is all you have to do in the SmartGuard 600. Note that those 2 tags are BOLD in the taglist because they are being used in code.But you have access to all 32 bits of the DWORD within SmartGuard editor. Because the Automap on Add button on the scanlist page was checked the following mapping occurred automatically. you must configure the scan list. The SmartGuard 600 must be added to the scan list. SmartGuard Quickstart 17 . Then select the ‘Edit I/O Parameters’ button.Just download this configuration to the SmartGuard 600 controller. But either way. Recall that our example has a 4 byte polled connection that will be an input to the PVP. For the PVP DeviceNet scanner. and verify it is configured as follows. verify that the 4 bytes of input data are mapped as follows. SmartGuard Quickstart 18 . The shortcut in RSLinx Enterprise should appear similar to what follows. Just download this configuration to the PVP. The next step is to configure the RN10C DeviceNet Scanner.That is all you have to do in the PVP DeviceNet Scanner. (left/left/left/right from top to bottom). Right click on the RN10C and select properties. Right click on Input and select t Add Address Block. SmartGuard Quickstart 19 . Configure the properties as below.Note that the slot number of the RN10C is slot 2. Then select the I/O configuration tab on this scanner properties window. So you can select the baud rate that it correct for your application. I am unsure if it has to be slot 2. The PVP in this example is configured for DeviceNet node 7. but suggest you use the same. The SmartGuard in my example had the dip switches set for auto-sensing. It now should appear as below. SmartGuard Quickstart 20 . Right click on 0-3 Bytes and select Add Device.Set the length to 4 bytes to match what the scanner is reading from the SmartGuard. To read a BOOL that represents bit 0 of the first byte.Set the node number to match your SmartGuard. 2 in this example. SmartGuard Quickstart 21 . Right click on 0-3 Bytes and select Add Alias. configure it as below. It should appear as below: SmartGuard Quickstart 22 . SmartGuard Quickstart 23 . Configure it as follows.Lets add a second BOOL that represents bit 1 of the first byte. You should now see: Hit OK to accept these properties. Right click on 0-3 Bytes and select Add Alias. All that is left now is to create the PVP graphic that reads these Alias tags. This example will use two (2) mulistate indicators that read the two aliases. The tags for each of the multistate indicators can be browsed using RSLinx Enterprise. Select the tags as shown below: Save your project, generate a Runtime file and download it to the PVP. Observations: - There are three (3) downloads that must take place for this to operate: o RSNetworx to SmartGuard o RSNetworx to RN10C DeviceNet Scanner o Runtime file (.mer) to PVP It appeared that the download to the RN10C DeviceNet Scanner must be done last. If changes to the RN10C device properties do not show up in the View Studio tag browser (even after Refresh All Folders); stopping/restarting the RSView Enterprise service from the Device Manager does get the tag browser to update. SmartGuard Quickstart 24 How to Read/Write from/to the SmartGuard from the PVP concurrently This example is going to show how to use two (2) maintained pushbuttons on a PVP screen to control two (2) tags within the SmartGuard 600 controller. To accomplish this, a single BYTE of data will actually be sent from the PVP to SmartGuard. BYTE is the smallest piece of data that can be sent. There is no concept of a BOOL in either the PVP Scanner Properties or the SmartGuard controller. Even if you create a BOOL tag in the SmartGuard to accept data from the PVP, it uses a BYTE of data. There also are NO ANALOG values within the SmartGuard controller that you can access programmatically. All the instructions are BOOLEAN with the exceptions of timers and counters. But the presets for the timers and counters are NOT accessible programmatically. The presets are parameters within the instructions that cannot be changed online. This means that there is NO reason to send anything but BOOLean data values to the SmartGuard. And since the smallest data type within the SmartGuard is a BYTE, I see no reason to ever send less than a BYTE from the PVP to SmartGuard, even if you only are using a couple bits. The example that follows configures a BYTE of output data to be sent to the SmartGuard, but only uses two (2) buttons. If you need to send more than 8 BOOLs to the SmartGuard from the PVP, just edit the following example and change 1 BYTE to X BYTEs in all the ‘output’ parameters. Open up the SmartGuard Slave I/O configuration tab. Tags that are being read by the PVP should be entered into the IN tab. Tags that are being written to by the PVP should be entered into the OUT tab. SmartGuard Quickstart 25 In this case, a polled connection with 4 bytes that can be read and 1 byte that can be written to will be used. But you have access to all the bits of both the DWORD and BYTE within SmartGuard editor. SmartGuard Quickstart 26 The sample SmartGuard code shown below is using two (2) bits in both buffers. Note that those 4 tags are BOLD in the taglist because they are being used in code. The Input tab is being shown in the image below. The SG_to_PV tags are located in the Output tab. That is all you have to do in the SmartGuard 600. Just download this configuration to the SmartGuard 600 controller. SmartGuard Quickstart 27 Recall that our example has a polled connection that will read 4 bytes and write 1 byte between the SmartGuard and PVP. The SmartGuard 600 must be added to the scan list. SmartGuard Quickstart 28 .For the PVP DeviceNet scanner. Then select the ‘Edit I/O Parameters’ button. and verify it is configured as follows. you must configure the scan list. Just download this configuration to the PVP. SmartGuard Quickstart 29 . verify that the 4 bytes of input and single byte of output data are mapped as follows. The shortcut in RSLinx Enterprise should appear similar to what follows. The next step is to configure the RN10C DeviceNet Scanner.Because the Automap on Add button on the scanlist page was checked the following mapping occurred automatically. That is all you have to do in the PVP DeviceNet Scanner. But either way. I am unsure if it has to be slot 2. So you can select the baud rate that it correct for your application. Configure the properties as below. but suggest you use the same. SmartGuard Quickstart 30 .Note that the slot number of the RN10C is slot 2. Then select the I/O configuration tab on this scanner properties window. The PVP in this example is configured for DeviceNet node 7. (left/left/left/right from top to bottom). The SmartGuard in my example had the dip switches set for auto-sensing. Right click on the RN10C and select properties. Refer to that section to configure the data that will be read from the SmartGuard and displayed on the PVP. Right click on Output and select Add Address Block. We will now show you how to configure the data that will be written from the PVP screen to the SmartGuard. SmartGuard Quickstart 31 .The configuration of the input block is covered in the ‘How to Read BOOLs’ section of this document. It now should appear as below. Set the length to 1 byte to match what the scanner is writing to the SmartGuard. Right click on 0-0 Bytes and select Add Device. Set the node number to match your SmartGuard. SmartGuard Quickstart 32 . 2 in this example. To write a BOOL to bit 0 of the first byte. configure it as below. It should appear as below: SmartGuard Quickstart 33 .Right click on 0-0 Bytes and select Add Alias. Configure it as follows. Right click on 0-0 Bytes again and select Add Alias. You should now see: Hit OK to accept these properties. SmartGuard Quickstart 34 .Lets add a second BOOL to write to bit 1 of the first byte. All that is left now is to create or add to the PVP graphic that writes these Alias tags. This example will use two (2) Maintained buttons to write the two aliases. Select the tags as shown below: Save your project. They are circled below: The tags for each of the maintained buttons can be browsed using RSLinx Enterprise. generate a Runtime file and download it to the PVP. SmartGuard Quickstart 35 . SmartGuard Quickstart 36 . The screens do not care how the scanner gets the data over DeviceNet. I was able to change all the appropriate settings from Polled to COS and all still worked just fine.COS versus POLLED The examples above used Polled to read/write data over DeviceNet. The following edits take place in the SmartGuard Slave I/O configuration. I have documented the changes required in SmartGuard and DeviceNet Scanner properties. Note NO changes in Factory Talk View are required. SmartGuard Quickstart 37 .The following edits take place in the RN10C DeviceNet Scanner configuration in RSNetWorx. SmartGuard Quickstart 38 . The following images show the changes required to support this configuration. I added a second connection (cyclic) with 16 Bytes input.Maximum Connection Sizes I created a Polled connection with 16 Bytes input and 16 Bytes output. Within SmartGuard Within DeviceNet Scanner SmartGuard Quickstart 39 . Within Factory Talk View RSLinx Enterprise SmartGuard Quickstart 40 . Configure Communications between a PanelView Terminal and SmartGuard 600 Controller over and EtherNet/IP Network Configure the SmartGuard Open up the SmartGuard EtherNet/IP Target I/O configuration tab. Select New to configure a new assembly: For Input assemblies you can add predefined status data to your assembly by selecting the corresponding check boxes. Here you can configure up to 4 target assemblies (2 input. Configure an Input assembly for data you wish to send from the SmartGuard to the PanelView. Each assembly can be up to 16 bytes. SmartGuard Quickstart 41 . 2 output). Configure an Output assembly for data you wish to send from the PanelView to the SmartGuard. The tags you create are accessible within your logic program in the SmartGuard: SmartGuard Quickstart 42 .Select New under the Routing I/O section allows you to add status information from distributed safety I/O to the Input assembly: You can also add tags to the assembly. The first step is to define the communications path between the PanelView and the SmartGuard 600.When your assemblies have been configured they will be displayed on this tab. Configure the PanelView Open your PanelView application within PanelBuilder32 software. Open Communications Setup in the Application Explorer. SmartGuard Quickstart 43 . This is configured in the Communications Setup dialog. press Insert on your keyboard to insert a new node. From the Communications Setup – Ethernet dialog. enter a Tag Name. and Node Name (which matches the Node Name you defined for the SmartGuard in the Communications Setup). class. Click OK to confirm the Communications Setup. instance and attribute codes for the tag in order to access the correct target I/O assemblies in the SmartGuard controller. enter the Node Address of the SmartGuard. There can be up to 4 target I/O assemblies configured in the SmartGuard (2 input and 2 output). Open the Tag Editor in the Application Explorer. a Data Type. In the new tag cells. define a Node Name. select ENet – CIP: Click Insert to add a new tag. The next step is to define tags within the PanelView tag database that will access the target I/O assemblies in the SmartGuard 600. and define the node type as Generic CIP.In the cells. SmartGuard Quickstart 44 . The next step is to define the CIP service. On the bottom of the Tag Editor. we will choose DINT as the data type. In this example. The maximum size of a single member tag defined in the PanelView is a DINT (4 bytes). Part 1: configure the SmartGuard 600 as a standard slave to a 1756-DNB. In order to access all of the bytes in the target assembly. Configuring the SmartGuard 600 and DeviceNet safety I/O modules as standard slaves Configuring the SmartGuard 600 and DeviceNet safety I/O modules as standard slaves. the CIP message codes are as follows: Service: 0x10 – Set Single Attribute Class: 4 Instance: 102 or 103 (Output1 or Output2 respectively) Attribute: 3 This example shows a CIP message code that accesses Input Assembly 1 of the SmartGuard Controller: The Member field will always be defined as 1. A target I/O assembly in the SmartGuard can be as large as 16 bytes. Both devices can also concurrently be configured as standard slaves to a standard scanner (such as a 1756-DNB) to obtain status. SmartGuard Quickstart 45 . where an Offset is defined for each tag to correspond with the target bytes of said tag. A typical architecture has the SmartGuard 600 configured as a safety scanner with a connection to a 1791DS safety I/O module slave. This application note will describe the steps required to configure the standard side of this architecture. it may be required that you create up to 4 DINT tags. When the 1756-DNB scanlist is viewed. the CIP message codes are as follows: • • • • • • • • Service: 0xE – Get Single Attribute Class: 4 Instance: 100 or 101 (Input1 or Input2 respectively) Attribute: 3 For Output Assemblies.For Input Assemblies. notice that the SmartGuard 600 does not appear in the list of available devices. even though a safety connection exists between the two devices. SmartGuard Quickstart 46 . The standard data is configured in the Slave I/O tab of the SmartGuard 600. it will appear in the ‘available devices’.This is because no data has been placed in the SmartGuard 600 Slave I/O tab. The following window appears. This tab is circled below: Select the Slave I/O tab. Once you place data in the slave I/O tab. Select New (circled above) to add data. SmartGuard Quickstart 47 . Notice there are two tabs. The OUT tab is data that will be sent from the Scanner to the SmartGuard 600. These are in relation to the scanner. Reset buttons are one example of this type of data. This is typically status data. OUT and IN. The IN tab is data sent from the SmartGuard 600 to the Scanner. The following window appears. and then added a COS/Cyclic connection. Polled. Bit-Strobe. that can have an additional 16 Bytes of inputs as well. The two (2) connections can be selected from the 4 types. but not two (2) polled connections. the controller can perform standard I/O communication with 1 standard master for up to 2 connections. COS. or Cyclic. using up to 16 bytes per connection. My testing discovered that if you use the Polled connection. COS. and Cyclic allow both input and outputs (read and write) in a single connection. the output of this connection is grayed out. This means that the maximum data configuration is as follows: SmartGuard Quickstart 48 . For example. Bit-Strobe only allows data to be sent to the Scanner. Poll. As a standard slave. A connection that uses both inputs and outputs can have 16 Bytes of input data and 16 Bytes of output data. The first selection is which I/O type of connection to use. The following screen appears.Select the IN tab. And if you add a second connection. but only one connection of each type can be made. one (1) polled connection and one (1) COS connection can be made. The following information should be helpful in determining which type to use. General Status is 8 bits of data: Bit0 – Input Power Supply Voltage status OFF.Power supply is ON (Normal) ON – Power supply error or OFF Bit2 – Standard I/O comms error flag OFF – No error ON – Error Bit3 – Standard I/O comms Status flag OFF – comms stopped or error ON – comms normal Bit4 – Safety I/O comms error flag OFF – No error ON – Error Bit5 – Safety I/O comms Status flag OFF – comms stopped or error ON – comms normal Bit6 – Operating Mode Flag OFF – Not in RUN mode ON – RUN mode Bit7 – Controller Status Flag OFF – Error ON – Normal Local Input Status – Status of the 16 local inputs (OFF – channel fault) (ON-normal) Local Output status – Status of the 8 local outputs (OFF – channel fault) (ON-normal) Test Output / Muting Lamp status – Status of the 4 test outputs Local I/O Input Monitor – Current Data Value of the 16 local inputs Local I/O Output Monitor – Current Data Value of the 8 local outputs SmartGuard Quickstart 49 .Power supply is ON (Normal) ON – Power supply error or OFF Bit1 – Output Power Supply Voltage status OFF. the data to be sent over this connection is chosen. then there are predefined boxes that can be checked. Once the type of connection has been selected. If you wish to send the data values and channel status. This configuration was tested and found to work.This configuration allows 32 Bytes of input data (16 via Polled and 16 via COS or Cyclic) and 16 bytes of output data via the Polled connection. see below. If you wish to add tags that are being controlled programmatically to the data send to the scanner using the Input Polled connection. The following screen appears after OK is selected. any.None. If all are selected. SmartGuard Quickstart 50 . Select the Input tab and the following should re-appear. Notice this is a Polled connection. 8 bytes of data are required. click on the Edit button circled above. or all of the above can be selected. DATA_to_SCANNER.Click the New button and the following window appears. Enter the name of the tag that will be sent to the Scanner. This tag will then appear in the standard outputs of the SmartGuard 600 and can be used programmatically. if I call the tag. and make it a DWORD. SmartGuard Quickstart 51 . For example. then the following will appear in the SmartGuard editor. WORD. BYTE is the smallest piece of data that will be sent to the Scanner. SmartGuard Quickstart 52 . The suggestion is to use BYTE. or DWORD to create 8. The input tab will appear as follows after the DWORD is added. There is no concept of a BOOL in the SmartGuard controller. 16.Notice that since the tag was a DWORD. or 32 tags that can be used programmatically. it uses a BYTE of data. 32 bits are available to use within the SmartGuard program. Even if you create a BOOL tag in the SmartGuard to be sent to the Scanner. Hit Apply. SmartGuard Quickstart 53 . The following should appear. then OK to close the SmartGuard properties. Place the SmartGuard in the scanlist. and select Edit I/O Parameters. Take a look at the 1756-DNB scanlist and you will see that the SmartGuard 600 [1752L24BBB] has appeared in the available device list. As expected. the Polled connection of the Scanner will read 12 bytes of data from the SmartGuard. you would do the following. Verify that you are in the OUT (output) tab circled below. Return to the SmartGuard Slave I/O tab. If you wanted to send data from the Scanner to the SmartGuard. The mapping of these 12 bytes defaults to the following. SmartGuard Quickstart 54 . and select edit to add data to the Polled connection. Again. resets are one example of this type of data. if the tag is called.Notice that the Status and Local I/O monitor are grayed out because this is data sent from the Scanner to the SmartGuard Slave. Enter the name of the tag that will be sent from the Scanner. For example. DATA_from_SCANNER. then the following will appear in the SmartGuard editor. This tag will then appear in the standard inputs of the SmartGuard 600 and can be used programmatically. SmartGuard Quickstart 55 . Select New and the following window appears. and made a DWORD. even if you only are using a couple bits. there is little reason to ever send less than a BYTE from the Scanner to SmartGuard. This means that there is NO reason to send anything but BOOLean data values to the SmartGuard. There is no concept of a BOOL in the SmartGuard controller. After the tag is added. There also are NO ANALOG values within the SmartGuard controller that you can access programmatically. But the presets for the timers and counters are NOT accessible programmatically. BYTE is the smallest piece of data that can be received. it uses a BYTE of data. And since the smallest data type within the SmartGuard is a BYTE. the input connection will appear as shown below. SmartGuard Quickstart 56 .As with outbound data. All the instructions are BOOLEAN with the exceptions of timers and counters. The presets are parameters within the instructions that cannot be changed online. Even if you create a BOOL tag in the SmartGuard to accept data from the Scanner. That completes the slave configuration for the SmartGuard controller. Edit the I/O parameters of the SmartGuard and they should appear as shown below. and open the scanlist of the 1756-DNB. The 1791DS module should automatically appear in the 1756-DNB list of available devices. SmartGuard Quickstart 57 . Now lets configure the standard slave configuration for the 1791DS safety I/O module.There are now 12 bytes being sent to the Scanner and 4 bytes being sent to the SmartGuard. Hit apply. then OK. SmartGuard Quickstart 58 . These sizes and data contained within them cannot be altered.The reason is that the 1791DS module has pre-configured options for reading standard data. They are as follows. To view them. open the properties of the 1791DS module and select the I/O data tab. COS and Cyclic provide Power Status. You should see something similar to the following window. move the 1791DS module into the 1756-DNB scanlist and select Edit I/O Parameters. but in general the Bit-Strobe and Polled connection provide the I/O data values and channel status. To select one of these connection types. two connections can be made simultaneously to the 1791DS module. In fact.These will appear differently based on which safety I/O module has been selected. That completes the slave configuration for the 1791DS safety I/O module. SmartGuard Quickstart 59 . Any of the four (4) connection types will work individually. and those standard outputs can then be controlled from the Scanner. The input and output sizes cannot be changed because the sizes are fixed within the 1791DS module. which cannot be obtained from Bit Strobe or Polled. This only is used if the Test Outputs have been configured as standard outputs. Note that the Polled connection even has the ability to write standard data to the I/O module. you can easily select the types of status and data to obtain by simply checking the appropriate boxes as shown below. This is described in chapter 4 of this document But these types of data and status can also be obtained from the SmartGuard 600 using explicit message instructions. this is generally done by placing the SmartGuard into the scanlist of a DeviceNet Scanner.Explicit Messaging of the SmartGuard 600 over DeviceNet If you are going to obtain input data. SmartGuard Quickstart 60 . When configured as a slave. output data. and general status from the SmartGuard 600. . SmartGuard Quickstart 61 .The example above shows three separate MSG instructions. The Source Element is an array of SINT[4] with the following values. two for the 16 input data channels and two for the status of the16 input channels. The second reads the General Status information. The Destination is also an array of SINT[4] to hold these 4 bytes of data. The input data will be in the first 2 bytes (0/1). and the input status will be in the last 2 bytes (2/3). Input Data and Input Status The MSG instruction is configured as shown below. The first reads the input data and input status for the 16 local SmartGuard input channels. The value of 4 enables the reading of 4 bytes. The third reads the output data for the 8 local SmartGuard output channels and the four (4) test outputs. General Status The MSG instruction is configured as shown below. No Source element is required because the service type is GET ATTRIBUTE SINGLE. SmartGuard Quickstart 62 . The Destination is a single SINT. because the General Status returns just a single byte of information. This byte is described in detail in chapter 4 of this document. The output data will be in the first byte(0). SmartGuard Quickstart 63 . and the test output data will be in the 2nd byte(1). The following example shows how to read whether the SmartGuard 600 is locked or unlocked. The upper 4 bits of the second byte are reserved.Output Data and Test Output Data The MSG instruction is configured as shown below. As discussed earlier. one for the 8 output data channels and one for the 4 test outputs. The Destination is an array of SINT[2] to hold both bytes of data. The value of 2 enables the reading of 2 bytes. the data above can easily be read by putting the SG in scan list of DNet scanner. The Source Element is an array of SINT[4] with the following values. The more likely scenario is to use the explicit messaging to read more specific data such as lock/unlock status as well as individual fault codes for input and output channels. the following explicit message can be used to obtain the fault code for that individual channel. because the General Status returns just a single byte of information. A value of 1 in bit0 of this byte indicates the SmartGuard is locked. If the channel status is faulted. No Source element is required because the service type is GET ATTRIBUTE SINGLE. The following is an example that shows how to read fault code for an input channel.Lock Status The MSG instruction is configured as shown below. The Destination is a single SINT. A value of 0 represents unlocked. The status (NORMAL/FAULTED) of the channel would typically be obtained by putting the SmartGuard in the scanlist of a scanner or doing the explicit message for input data/status described earlier in this section. SmartGuard Quickstart 64 . Input Channel Fault Code The MSG instruction is configured as shown below. SmartGuard Quickstart 65 . No Source element is required because the service type is GET ATTRIBUTE SINGLE. because the Fault Code returns just a single byte of information. The Destination is a single SINT. The fault code values are as follows: Value = 2 typically would be a pulse test fault Value = 4 typically means that dual channel devices are diverse Value = 5 typically means that the channels partner (dual channel) has faulted Refer to the SmartGuard Users Manual for more information on data that can be read via explicit messaging. Note that a value of 5 in the instance field represents channel 4. channels begin at 0. Instances begin at 1. Explicit Messaging of the 1791DS modules from Logix It is common for users to use the implicit I/O connection to read the combined status of the inputs and outputs. An example from this manual is show here: The values of the safety inputs. The following example uses assembly 344 to explicitly read from the 1791DSIB8xOBV4 module. If the combined status bit indicates an issue. The 1791DS Users Manual (1791DS-UM001x) shows the different assemblies that can be read from the module. then the user can utilize explicit messaging to gather detailed status information to the point level. safety input status. SmartGuard Quickstart 66 . safety output status and muting lamp status are examples of data that can be explicitly read from these modules. Every time run_msg has a LO to HI transition. the message instruction is sent. a single DINT tag works perfectly. Configure the MSG as shown here: 836 is the decimal equivalent of 344(hex). When the message is done. Because assembly 836 requires 4 bytes. DS_IB8xOBV4_status is a standard tag and a DINT. the data appears as shown: SmartGuard Quickstart 67 . Note that you have to match up the assembly to the data above. bit 8 shows the status of safety input channel 0. The following UDT was created for assembly 836. SmartGuard Quickstart 68 . For example. A UDT can be used to easily describe the bits. SmartGuard Quickstart 69 .A tag was created that used this UDT data type. This new tag was placed into the Destination of the MSG instruction. the data appears in the UDT as shown: The tagnames are much more descriptive. Please take note of the fact that this status is NOT safe data.Now when the message is run. Just use it for HMIs. SmartGuard Quickstart 70 . Do not use the first byte in safety logic. If the channel status bit goes LO. The MSG instruction is configured as shown below. Note that a value of 5 in the instance field represents channel 4. SmartGuard Quickstart 71 . Instances begin at 1. channels begin at 0. then you can use the following explicit messages to get detailed information about the specific channel fault. because the Fault Code returns just a single byte of information. SmartGuard Quickstart 72 .No Source element is required because the service type is GET ATTRIBUTE SINGLE. The Destination is a single SINT. The fault code values are as follows: Value = 2 typically would be a pulse test fault Value = 4 typically means that dual channel devices are diverse Value = 5 typically means that the channels partner (dual channel) has faulted Refer to the 1791DS Users Manual for more information on data that can be read via explicit messaging. Configure EtherNet/IP Target IO in RSNetWorx for DeviceNet Software Follow these steps to create standard EtherNet/IP target I/O assemblies: 1. 2. The following dialog appears. Select the EtherNet/IP Target I/O tab. Click New. In RSNetWorx for DeviceNet software. 3. SmartGuard Quickstart 73 . right-click the SmartGuard controller and choose Properties. Select the byte you would like to add. Add local I/O monitor data for input types by checking the appropriate Local I/O Monitor checkbox. Add Routing I/O data for the modules. select either Target Input or Target Output. Add status information for input types by checking the Status checkboxes.4. Modules only appear in the routing I/O table after they have been added to the Safety Scan list and you have pressed Apply. Target Input means that this data is produced by the SmartGuard controller and read be the originating device. 6. b. a. you cannot directly write to them. SmartGuard Quickstart 74 . 7. If you have checked Target Input. Under I/O type. You can only read and input and output values. Tag Name Local Input Monitor 1 (Inputs 0…7) Local Input Monitor 2 (Inputs 8…15) Local Output Monitor (Outputs 0…7) Data Size Byte Attribute Type Non-Safety Output types cannot include local I/O monitor data. d. c. you can include the following status information in the I/O assembly. Target Output means that this data is produced by the originating device and is sent to the SmartGuard controller. click New. Expand one of the listed assemblies. Expand the node you would like to add routing data for. using the Routing I/O feature lets the values of the I/O points on the DIO modules to be passed to a standard controller or an HMI interface on the EtherNet/IP network. Tag Name General Status Local Input Status Local Output Status Test Output/Muting Lamp Status Data Size Byte Word Byte Attribute Type Non-safety 5. Under Routing I/O. If the SmartGuard controller is controlling safety DIO modules on the DeviceNet network. WORD. The following dialog box appears. and then be able to use it in your SmartGuard logic. 10.e. The I/O tags here can be used in the Logic Editor. I/O tags up to 16 bytes can be defined in each I/O assembly. . For example. The following dialog box appears. The choices are BOOL. 8. Click New to create an I/O tag. . Click OK. 9. Click OK. e to add additional Routing I/O. SmartGuard Quickstart 75 . Multiple I/O tags can be defined in an I/O assembly. or DWORD. Enter a name for the tag and check the type. f. Repeat steps a. BYTE. Under I/O Tag. you can use a signal from an HMI interface to perform a Circuit Reset function. You would define the tag here. 12. c. You can create additional input or output assemblies needed for your application by repeating steps 2.11. To save your configuration. Click OK to return to the EtherNet/IP Target I/O tab. . . b. The tag name comments entered here are displayed in the Logic Editor. Under I/O Tag. Create a tag name for each bit in an I/O assembly. select the applicable assembly and click Edit Comment.11. Enter a comment for each bit in the tag. choose File>Save. 13. a. SmartGuard Quickstart 76 . Expand the node that you would like to add routing data for. you can now use the RSLogix 5000 software and the standard generic profile to exchange that data with a Logix5000 controller.Setup EtherNet/IP Communications between a Logix5000 Controller and the SmartGuard 600 Safety Controller Once you have configured the data to be shared in the SmartGuard controller. SmartGuard Quickstart 77 . Right-click the Ethernet network in the controller organizer and choose New Module. Expand the Communications group and select ETHERNET-MODULE. Follow these steps to connect to the controller. 1. 2. 103 100. 101 102.3. Connection Type Input/Output Input only Input (SmartGuard to Logix) Output (Logix to SmartGuard) Input Output Instance Number 100. The table provides the instance values for an input/output connection and input only connection. Click OK. 101 199 5. This dialog shows the instance values for an input/output connection. set the parameters as needed. On the New Module dialog. Click OK. 4. SmartGuard Quickstart 78 . set the IP address of the MicroLogix controller: a. 1. 4. Right-click Channel Configuration and choose Open. Select the controller. Launch RSLogix 500 software. In the Channel Configuration dialog box. SmartGuard Quickstart 79 . 2. Open a new file. 3.Explicit Message of the SmartGuard 600 Controller over EtherNet/IP with a MicroLogix Controller Follow these steps to program a MicroLogix controller to explicitly message the EtherNet/IP target assemblies in the SmartGuard controller. configure an Extended Routing Information data file: a. SmartGuard Quickstart 80 . Right-click Data Files and choose New. 5. Type the IP address for the MicroLogix controller. In the Data File dialog.b. The MSG dialog box opens. enter an available File number and choose Extended Routing Information for the Type. Click OK. 6. In the Create Data File dialog.b. 8. Configure the message with the following properties: SmartGuard Quickstart 81 . c. Select Setup Screen to configure the message. Enter the following rung of ladder logic: 7. Place the MicroLogix controller in Run mode. The instance value corresponds to the input/output EtherNet/IP target assemblies in the SmartGuard controller. 9. 15. 13. Configure the routing to target the IP address of the SmartGuard 600 controller. Write Assembly – if you are writing to an output assembly in the SmartGuard controller. SmartGuard Quickstart 82 . Enter the Instance number based on this table. Verify your changes to the project. Download the project to the MicroLogix controller.The Service attribute should be configured as one of the following: • • Read Assembly – if you are reading an input assembly in the SmartGuard controller. 10. 12. Click the MulitHop tab. 14. The status information from the SmartGuard controller now populates the N7 file of the MicroLogix controller. Instance Number 100 (EtherNet/IP Input 1 in SmartGuard) 101 (EtherNet/IP Input 2 in SmartGuard) 103 (EtherNet/IP Output 1 in SmartGuard) 104 (EtherNet/IP Output 2 in SmartGuard) Connection Type Input (SmartGuard to MicroLogix) Input (SmartGuard to MicroLogix) Output (MicroLogix to SmartGuard) Output (MicroLogix to SmartGuard) The message size (in bytes) should be configured to match the target assembly size in the SmartGuard controller. Click OK. 11. SmartGuard Wiring Diagrams: Common Safety Devices EStop / Dry Contacts CAT 2 CAT 3 CAT 4 CAT2 CAT3 Tongue Interlocks/ Dry Contacts CAT4 SmartGuard Quickstart 83 . OSSD1 OSSD2 Devices CAT2 CAT3 CAT4 GuardShield CAT4 SmartGuard Quickstart 84 .Light Curtains. Solenoid Locking Switch / Dry Contacts CAT2 CAT3 CAT4 Electronic Sensors CAT2 CAT3 CAT4 N/A SmartGuard Quickstart 85 . Safety Contactors [OB Outputs] CAT2 CAT3/CAT4 Safety Contactors [OBV Outputs] CAT2 CAT3/CAT4 SmartGuard Quickstart 86 . Kinetix 6000 Safety Drives [OB Outputs] CAT2 CAT3 CAT4 Kinetix 6000 Safety Drives [OBV Outputs] CAT3 CAT4 SmartGuard Quickstart 87 . PowerFlex Safety Drives [OBV Outputs] CAT3 CAT4 Standard Drives [OBV Outputs] CAT2 CAT3/CAT4 SmartGuard Quickstart 88 . SmartGuard Quickstart 89 .