Configuration for General DIP Devices. Setting Up RSLinx

Transcription

1 Configuration for General DIP Devices Setting Up RSLinx Start Up RSLinx Program. Go to Communications Configure Drivers. Then, select an Available Driver Type (example, DeviceNet drivers). Once the appropriate driver is selected, click Add New. Then, click Select if the correct DeviceNet driver is highlighted, otherwise try selecting another one. A dialog box showing the Driver Configuration should appear. Choose the appropriate port and data rate for the device and click on OK. Following this, the program will try to detect the device according to the configurations selected. If the device is detected according to the specifications chosen, a dialog box should appear, asking the user to select a name for the device. Choose a name and click OK. The device should appear under the Configured Drivers List with the following format: Name, MAC ID, Baud Rate, and Status. If this is not the case, the configuration chosen for the driver is incorrect. Determine the correct specifications for setting up the driver and try again. Repeat the above steps for each driver needed. Once all the necessary drivers are configured and running correctly, they should appear in the left-most network box under the workstation icon. Each driver listed can either be expanded or contracted using the plus or minus button appearing to the leftmost side of the driver. Clicking on the autobrowse box will allow RSLinx to continually browse the network for any new nodes that may have been added to the system. After browsing the entire system and once all devices have been displayed correctly, proceed to the next step of setting up RSNetWorx. Setting Up RSNetWorx Be sure that the RSLinx program is up and running correctly before starting RSNetWorx. Start RSNetWorx. Go to Network Single Pass Browse. You should see a message box indicating that the network is being browsed, and should see the program cycling through all 64 DeviceNet nodes. Note that at any time during the execution of RSNetWorx commands, if an error has occurred, the cause of failure will appear in a small dialog box at the bottom of the screen, showing the error code and description. Following the online browse, you should see all devices currently on the network. If a device appears with the message Unrecognized Device, it means that RSNetWorx has detected the device, but that the EDS file for the device is either not present or is present but not configured correctly. Check to make sure that the current EDS file for the device has been registered on RSNetWorx. An EDS file can be registered by clicking on Tools EDS Wizard. While in the Wizard, simply choose Register an EDS file, click next and follow the simple instructions. Be sure to specify the correct path name of the EDS file location by clicking Choose File. Once the EDS file has been registered, repeat the Single Pass Browse explained above. This procedure should correct the previous error message Unrecognized Device. However, if a new error message comes up, as indicated by a red-dash mark above the device, it means that the EDS file specifications do not match the internal specifications of the device. To correct this problem, start by double-clicking on the device icon in RSNetWorx. A dialog box should appear on the screen. Copy on a piece of paper the values listed for Vendor, Device,

2 Product, and Revision. The Vendor, Device, and Product are all decimal numbers, which should be enclosed in parenthesis and appear after a short description. The revision number will consist of two parts. The first number appearing before the decimal point indicates the major revision, while the second number(s) appearing after the decimal point indicate the minor revision. Copy down both numbers. Next, open the EDS File (it can be opened using Notepad) and note the values for VendCode, ProdType, ProdCode, MajRev, and MinRev. Compare these values to the numbers copied down earlier on a piece of paper representing the internal values of the device itself. These four values should match the device s Vendor, Device, Product, Major Revision, and Minor Revision, respectively. If the values do not match, change the values in the EDS file to match the values in the device. Then, save the EDS file, and before registering the file on RSNetWorx using the EDS Wizard, be sure to unregister the previous EDS file which contained the incorrect values for the device. Do this by following the same procedure to register an EDS file explained above, but instead of selecting Register an EDS File, choose the option Unregister an EDS file. Choose the appropriate device for which you want to unregister the EDS file, and proceed in the same manner as indicated above. Then, after the device is unregistered, register the new EDS file. Then, do a Single Pass Browse of the network again and no errors should appear. If the error does not go away or if new errors come up, the device may be faulty and may need to be replaced. Once all devices have appeared on the network, they can be accessed by simply double-clicking on the device s icon. A device s attributes may be accessed by clicking on the Device Parameters tab once the appropriate device has been selected. A device s parameters may be changed by simply double-clicking on the appropriate one and changing it to the desired value. Setting Up Scanlist in RSNetWorx Once all the devices are showing up correctly on the DeviceNet network, the next step is to add the device(s) to the 1747 SDN Scanner Module s Scanlist. Before this step, however, make sure the network is online. This can be accomplished by clicking on the Online icon located under the main menu bar, or by Choosing Network from the main menu bar, then selecting Online. A dialog box should appear in the middle of the screen indicating that the network is being browsed, along with the various nodes being scanned. Following this, make sure that the device s parameters are correct, and have been uploaded to the device. Once all devices are configured, add them to the Scanlist by double-clicking on the 1747 SDN Scanner Module, click on the Scanlist tab, then choose Download from device. This will download the Scanner s current configuration from the Scanlist. Once the Scanlist tab appears, choose the appropriate device and click on the right arrow button located in between the two small windows at the top of the Scanlist tab. Once all devices have been added to the Scanlist, the next step is to click on the Edit I/O Parameters box for each device. Check off each applicable communication protocol for the device (eg. Polled and Change of State/Cyclic). For the CDN066 device, under the Polled connection, make sure that the Rx size and Tx size take into account the 3 possible additional bytes that must be added to both values, depending upon whether or not certain criteria have been met. For the CDN066, if the String Format bit (bit 0 of the Data Format Attribute) is low, an additional byte must be added. Another byte should be

3 added if the Synchronous bit (bit 6 of the Block Mode) is set to a 1. Finally, if the Status Enable Attribute is set to a non-zero value, an additional byte should be added to the Rx size, and if the Status Clear Enable Attribute is a non-zero value, an additional byte should be added to the Tx size. Remember that all of these additional bytes should be factored into the Rx size and Tx size inside the Scanlist alone, and not the actual device itself. If, for instance, the CDN066 device is setup for a Maximum Transmit and Receive size of 16 bytes, and if the String Format bit is low, the Synchronous bit is high, and both the Status Enable and Status Clear Enable Attributes are low, then both the Rx size and Tx size in the Scanner module s Scanlist should be setup for 18 bytes. This is due to the fact that the String Format bit is low and the Synchronous bit is high. Both of these bits contribute an additional byte to the data travelling from the CDN066 module to the PLC. Once all the devices have been added to the Scanlist, and once any additional bytes have been added to the Tx and Rx sizes in the Scanlist, the network is complete and ready for communication protocol to take place between the PLC and the slave devices on the DeviceNet network.

4 Configuration for CDN066 with Rockwell Software Setting Up CDN066 with RSLinx and RSNetWorx Follow the above procedure for Setting up RSLinx and Setting up RSNetworx to get the CDN066 device up on the network. Make sure that the EDS file for the CDN066 device has been registered on RSNetworx before attempting to connect the device to the network and performing an online browse of the system. The process of registering an EDS file is explained above under the heading Setting up RSNetWorx. Also, be sure that the Baud Rate of the device on the DeviceNet side matches the baud rate setup on the network. The node address of the CDN066 device should not conflict with the addresses any other slave devices on the DeviceNet network. The best method for adding devices to the DeviceNet network is to first connect only the Allen Bradley 1770-KFD module and 1747 SDN Scanner module to the network, get them to display and operate correctly, then add slave devices to the network one device at a time. This minimizes the chances for multiple errors appearing at the same time, and allows the user to solve any network protocol or communication problems one device at a time. Configuring CDN066 with RSNetWorx Once the CDN066 device appears correctly on both RSLinx and RSNetWorx, proceed to configure the CDN066 device to the specifications desired for serial communications protocol. Make sure that the DeviceNet network is Online before proceeding to the next step. Start by double clicking on the CDN066 device in RSNetWorx, and clicking on the Device Parameters tab. Upload the Instance 1 Attributes from the device when prompted to do so. The parameters appearing on the screen having a small lock symbol to the left of the parameter name are attributes which are fixed and cannot be changed by the user. All other attributes can be changed to the user s specifications. Please see the DeviceNet specifications for an explanation of each attributes properties. For common setup procedures for the CDN066 device, see the Configuring a CDN066 device for use with an Allen Bradley 1747 SDN Scanner Module document. The most important parameters which the user should pay particular attention to are the Data Format and Block Mode Attributes. Of particular interest is the String Format bit (bit 0 of Data Format) and the Synchronous bit (bit 6 of the Block Mode). Both of these bits affect the Maximum Transmit and Receive sizes depending upon how they are configured. If the String Format bit is low, it will contribute an additional byte to both the Maximum Transmit and Receive sizes, as will the Synchronous bit if it is set to a 1 (high). The additional bytes should be added to the device in the Scanlist of the 1747 Scanner module, and NOT in the device itself. If both the String format bit is low and the Synchronous bit is high, and the user wants to scan a barcode of length 16, then he should make both the transmit and receive size in the CDN066 module to 16, and set both the transmit and receive size of the device in the Scanlist to 18, accounting for the 2 additional bytes. Setting the String Format bit to low will process the data packets as a DeviceNet defined SHORT_STRING, which means that the first byte in data packet transferred over the DeviceNet channel will contain a byte indicating the data length, followed by the actual data itself. Setting the Synchronous bit to a 1 indicates that handshaking protocol will be

5 used in the communication protocol sequence. Please see the DeviceNet specifications for more information on how exactly this protocol is setup in the CDN066 module. Once the device is configured correctly in the device itself and in the Scanlist, serial communication will be possible between the PLC, the 1747 SDN Scanner module, and the CDN066 device.