TECH. Running RSNetWorx in Windows 95. Setting Up the 1784-PCMK Card with RSLinx under Windows NT 4.0

Transcription

1 TECH These technical tips 1 were contributed by the following support specialists and project engineers: Lisa Fekter, Chris Griffith, Kurt Helfrich, Celestino Mastrangelo, Bill McKinley, Tim Menge, Ned Myers, and Don Pavlovich. In the technical tips displaying code, the characters may be too long to display on a single line. In such cases, multiple lines of text that should be entered as one line will end with a line continuation character. This character is a single space followed by the underscore ( _ ). Running RSNetWorx in Windows 95 This technical tip applies if you are using RSLinx release 1.7. These quick instructions can help you install RSNetWorx for ControlNet software on a computer running Windows In Windows NT, go to Start > Settings > Control Panel > Devices. 3. Scroll down to Pcmcia and click Startup. Select System, then click OK. 1. Locate Dcom95.exe on the RSNetWorx installation CD-ROM. 2. Run Dcom95.exe to install it. 3. Install or reinstall RSLinx software from the RSNetWorx CD-ROM. You must install DCOM95 prior to installing RSLinx software so RSLinx will work properly with RSNetWorx software. If you have RSLinx installed before DCOM95, then RSNetWorx cannot go online to a ControlNet network. 4. Install RSNetWorx software. Setting Up the 1784-PCMK Card with RSLinx under Windows NT 4.0 Here's how to set up the 1784-PCMK card if you are running RSLinx communication software under Windows NT 4.0. Before you begin, be sure you are logged in as the system administrator. You may also need to establish NDIS services so your system recognizes the 1784-PCMK card. 1. Be sure that the 1784-PCMK card is not yet inserted in the system. Starting up PCMCIA System Settings 4. Shut down the system and turn the power off. 5. Insert the 1784-PCMK card in its socket and power up your system. 6. Go to Start > Settings > Control Panel > PC Card (PCMCIA). The 1784-PCMK card should appear in the socket where you have it installed. It should have a red slash through it. 7. Find an open interrupt request (IRQ) by clicking Start > Programs > Administrative Tools. Then select Windows NT Diagnostics, and click the Resources tab. 1 The information contained in these technical tips is subject to change without notice. It is provided to the reader on an AS IS basis without representation or warranty of any kind as to the content or technical accuracy of such information. ROCKWELL SOFTWARE INC. DISCLAIMS ALL WARRANTIES WHETHER EXPRESS, IMPLIED, OR STATUTORY, INCLUDING IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS. 5

2 Converting RSLogix 5 Projects to and from 6200 Series PLC-5 Software Windows NT Diagnostics 8. If the IRQs on the list are in use, select an IRQ that is not on that list and set that IRQ for the 1784-PCMK card in RSLinx software. Remember, the lower the IRQ number, the higher the priority. 9. Exit from Windows NT Diagnostics. 10. Start RSLinx by clicking Communications > Configure Drivers. 11. Select 1784-KT/KTXD (PCMK), then click Add New. Under board type, select PCMK, then select a board address. DC00 works well as a board address. 12. Under Interrupt, select the open IRQ located under Windows NT Diagnostics. 13. For Station Number, indicate any open station number on the DH+ network. 14. For Network Type, select DHPLUS if you are using a PLC-5 or SLC 5/04 processor, and DH485 if you are using an SLC 5/03, SLC 5/02, SLC 5/01, or Fixed Unit processor. The Baud Rate should match your processor. Click OK. This technical tip helps you convert RSLogix 5 projects to and from 6200 Series PLC-5 software. Converting RSLogix 5 Projects to 6200 Series PLC-5 Software Use these steps to convert a project in RSLogix 5 to 6200 Series PLC-5 software: 1. From the RSLogix 5 Main menu, select File > Save As. Change the Save As Type field to PLC5 Programs(*.x5). 2. Select Tools > Database > ASCII Export. Click the AB6200 radio button. 3. Click OK, then select the folder where you want to store the.txt file. For example, the default folder is located at C:\ipds\text\plc5. 4. You may need to use a text editor such as WordPad to remove the line %WIDTH 20 at the end of the text file. Importing the Ladder File 1. From the 6200 Series PLC-5 Main menu, select [F7] - File Utils > [F6] - Import > [F8] from AI/WinLogic5. 2. Highlight the.x5 file and select [F3] - Select Source. 3. Select [F4] - Destination. Change the name, if desired, then press [Enter]. 4. Select [F6] - Select Data, then scroll down to Comments and Symbols. 5. Select [F3] to toggle this selection off, then press either [F9] - Save Config or [Esc]. 6. Select [F1] - Begin Oper to begin the import procedure. 15. Exit RSLinx software and restart your system. Then open RSLinx. Your 1784-PCMK driver should be running. The Configure Allen-Bradley KT(x) / PCMK Devices Window Importing the Database 1. From the 6200 Series PLC-5 Main menu, select [F7] - File Utils > [F6] - Import > [F3] - Comments and Symbols. 2. Highlight the.txt file and select [F3] - Select Source and [F4] - Destination. 3. Type in the name of the destination file, if desired, then press [Enter]. If you change the name, be sure to use the same project name as in the ladder file destination. Note that, in RSLogix 5, symbols that export to.txt truncate to 10 6

3 characters, while 6200 Series PLC-5 release 5.01 and above accepts symbol names of up to 20 characters. Description capacity is the same for both packages. 4. Select [F1] - Begin Oper to begin the import procedure. Converting a 6200 Series PLC-5 Project to RSLogix 5 Software Use these steps to convert a 6200 Series PLC-5 project to RSLogix From the RSLogix 5 Main menu, select File > Open. 2. Change the directory to point to your.af5 file. Select Open. 3. Select File > Save to save the project as an.rsp file in RSLogix 5 format. Conversion is complete. Converting RSLogix 5 Projects to and from PLC-5 A.I. Series Software This technical tip helps you convert RSLogix 5 projects to and from PLC-5 A.I. Series software. You may also wish to apply this tip to converting RSLogix 5 projects to WINtelligent LOGIC 5 software. Though not exactly the same, the steps are quite similar. Converting an RSLogix 5 Project to PLC-5 A.I. Series Use these steps to convert a project in RSLogix 5 to PLC-5 A.I. Series software. 1. From the RSLogix 5 Main menu, select File > Save As. Change the Save As Type field to PLC5 Programs(*.x5). 2. Select Tools > Database > ASCII Export. Click the AI radio button. 3. Click OK, then select the folder where you want to store the documentation. Importing the Ladder File 1. In PLC-5 A.I. Series software, select [F1] - Select Program/PLC-5 addr. 2. Highlight the.x5 file and press [Enter]. Importing the Database 1. In PLC-5 A.I. Series software, select [F5] - Utility Options > [F5] - Import Program/Database > [F1] - Import Descriptions and Symbols. 2. Highlight the.eas file, then press [Enter] to begin importing the symbols and addresses. 3. Select [F1] - Overwrite Database Record with ASCII File Data. 4. Select [F5] - Utility Options > [F5] - Import Program/Database > [F1] - Import Rung Descriptions and Page Titles. 5. Highlight the.erp file, then press [Enter] to begin importing the symbols and addresses. 6. Select [F1] - Overwrite Database Record with ASCII File Data. Converting a PLC-5 A.I. Series Project to RSLogix 5 Software Use these steps to convert a PLC-5 A.I. Series project to RSLogix 5 software. 1. From the RSLogix 5 Main menu, select File > Open. 2. Change the directory to point to the location of your.x5 file. Select Open. 3. Select File > Save to save the project as an.rsp file in RSLogix 5 format. Conversion is complete. Connecting 6200 Series PLC-5 Software and RSLinx After you start 6200 Series PLC-5 software from a shortcut on the Windows desktop, you may be unsuccessful trying to connect 6200 Series PLC-5 software with RSLinx software. Although RSLinx is running and its SuperWho screen shows the processor, the two packages still do not connect. This connection difficulty occurs because the shortcut setting can prevent MS-DOS -based programs from seeing Windows applications like RSLinx software. To connect properly, first disable the shortcut setting: 1. Right click the shortcut and select Properties. 2. Click the Program tab, then the Advanced button. 3. If the Prevent MS-DOS-based programs from detecting Windows option is checked, uncheck it and accept the changes. Detecting RSLinx or WINtelligent LINX in Your RSTools Visual Basic Application Visual Basic applications that use RSTools components usually require either RSLinx or WINtelligent LINX as a dynamic data exchange (DDE) communication server. When an RSTools application starts without an RSLinx or WINtelligent LINX communication package running, a dialog box prompts you to start the required package. When this occurs, the application must set the LinkMode 7

4 for each RSTools control to None, start RSLinx or WINtelligent LINX software, then set the LinkMode back to the desired mode once the package is running. However, it is much easier to determine if your RSLinx or WINtelligent LINX communication package is running before loading a form that contains RSTools controls. This technical tip gives you an example of how to use Visual Basic 5.0 to determine whether or not an RSLinx or WINtelligent LINX communication package is running on your machine. The example prompts you to start your communication package before a form loads that uses RSTools. This example also determines the RSLinx or WINtelligent LINX version you are running. With additional modifications, you can use the example to verify that an appropriate version is executing for your application. Before you begin, use this table to assess your software version so you can apply this technical tip correctly. Version Catalog # Comments RSLinx Gateway 9355-WABGW Supports DDE communication RSLinx 9355-WAB Supports DDE communication RSLinx OEM 9355-WABOEM Only supports Packed DDE via RSJunctionBox software RSLinx Lite Only available in Does not support DDE communication software bundles WINtelligent LINX 9352-WABGW Supports DDE communication Gateway WINtelligent LINX 9352-WAB Supports DDE communication WINtelligent LINX Lite Only available in Does not support DDE communication software bundles For simplicity, this example does not use any RSTools components. The application consists of a Form (Form1.frm), its associated code module, and a Code Module (Main.bas). Use these steps: 1. Start Visual Basic 5.0 and create a new.exe project. 2. Create a form similar to Form1 below that includes a label and command button. Set the label's AutoSize property to True. 3. Add this code for the specific events: Form1 with a Label and Command Button Private Sub Command1_Click() Unload Me End Sub Private Sub Form_Load() Label1.Caption = vbcrlf & LinxApp & vbcrlf & _ "is running" & vbcrlf End Sub 4. Add a code module to the project. This module will include items you create later, such as the required general declaration statements, the function that determines that the RSLinx or WINtelligent LINX communication package is executing, and the subroutine Main that executes when the application starts. 5. Enter the following declarations in the code module. Please continue to observe the line continuation characters ( _ ) for code text wrapping. Declare Function FindWindow Lib "user32" Alias _ "FindWindowA" (ByVal lpclassname As String, ByVal _ lpwindowname As String) As Long Public LinxApp As String 6. Create the FindLinx function to determine if RSLinx or WINtelligent LINX is running and if so, what version. Public Function FindLinx() As Integer Const FirstVer = -2, LastVer = 5 Dim lpclassname As String Dim lpwindowname(firstver To LastVer) As String Dim iindex As Integer 'These versions DO NOT support any form of 'DDE communication lpwindowname(-2) = "Rockwell Software _ RSLinx Lite" lpwindowname(-1) = "Rockwell Software _ WINtelligent LINX Lite" 'This entry is simply a place holder lpwindowname(0) = "Linx not running" 'These versions of WINtelligent LINX provide 'full support for DDE communication lpwindowname(1) = "Rockwell Software _ WINtelligent LINX" lpwindowname(2) = "Rockwell Software _ WINtelligent LINX Gateway" 'RSLinx OEM requires that RSJunctionBox is 'installed and activated to perform DDE 'communication lpwindowname(3) = "Rockwell Software _ RSLinx OEM" 'These versions of RSLinx provide full support 'for DDE communication lpwindowname(4) = "Rockwell Software RSLinx" lpwindowname(5) = "Rockwell Software RSLinx _ Gateway" 8

5 'Reset returned values for function FindLinx = 0 LinxApp = lpwindowname(0) 'Search for each version to determine if one 'is running For iindex = FirstVer To LastVer A% = FindWindow(lpClassName, _ lpwindowname(iindex)) If A% <> 0 Then 'A version was found running FindLinx = iindex LinxApp = lpwindowname(iindex) End If Next iindex End Function 7. Create the subroutine Main that uses the FindLinx function. Sub Main() Dim ibutton, iresults As Integer 'Determine if RSLinx or WINtelligent LINX is 'running. If it is not, pause the application 'until user starts communication package or 'terminates application iresults = FindLinx While iresults = 0 'RSLinx or 'WINtelligent LINX is not running ibutton = MsgBox("Linx is not running." _ & vbcrlf & "Start Linx and click OK. Click Cancel _ to terminate application", _ vbexclamation + vbokcancel) If ibutton = vbcancel Then End iresults = FindLinx Wend Form1.Show 'Start the application End Sub The subroutine Main executes FindLinx to determine whether or not RSLinx or WINtelligent LINX software is running before loading any form that uses RSTools components. Once the subroutine determines that RSLinx or WINtelligent LINX is running, the subroutine loads the main form (Form1) of the application. 8. Under Project > Project Properties, set Sub Main as the Startup Object for the application. You may wish to omit the code for detecting the versions of RSLinx or WINtelligent LINX communication software and simply develop your program for one particular version. You can also modify this example to detect other applications. Project Properties Dialog with Startup Object as Sub Main To download the example code shown in this technical tip, visit the Support Web pages at Search for Product = RSTools/Box/PowerTools. Receiving PCL_Link_Error -101 with the RSLinx Driver in Windows 95 You may receive the following error report when attempting to go online with a processor using the RSLinx driver in Windows 95. The full error report is PCL_Link_Error returned an error code of This error occurs with 7.x releases of PLC-5 A.I. Series software. These releases were designed for use with RSLinx releases up to 1.60.x, which ran strictly in Windows NT. Windows 95 functionality began with RSLinx release , and support for this release starts with PLC-5 A.I. Series release If your PLC-5 A.I. Series package does not have the RSLinx Driver under Win95 entry, you cannot use RSLinx in Windows 95, regardless of the RSLinx release you are using. We recommend that you upgrade to at least release 8.03 of PLC-5 A.I. Series software to avoid the error report we describe in this technical tip. If your software is under support, you can download the latest release from our Web site at Just click Software Updates. You need to know the name of the registered owner and the serial number to download software. 9

6 Using the 1784-PCMK Plug and Play Driver under Windows 98 During installation of the 1784-PCMK Plug and Play driver under Windows 98, you may receive the following warning for CBSS.VXD: A file being copied is older than the file currently on your computer. At the prompt, Do you want to keep this file? for Windows 98, always answer Yes (the default). Failing to do so overwrite the Windows 98 version of CBSS.VXD with an older version meant for Windows 95. This may cause problems with your other PCMCIA cards. Communicating with SLC Processors Using the Appropriate Protocols Like humans, SLC processors can speak different "languages", called communication protocols. The table below lists protocols for the family of SLC processors, as well as the appropriate RSLinx Lite drivers for each protocol. Selected hardware devices, mainly cables for connecting to the processors, also appear in the list. Optimizing Serial Communication Here are some tips that will help you set up your computer, especially laptops, for optimum serial communication. Shut down power management in both the Control Panel and CMOS Setup. Look for the battery or power plug icon in the Processors Control Panel of your Windows 95 or Windows NT 4.0 computer. Check your computer manual to find out how to get into the CMOS setup area. Disable the infrared port if your computer has one. You do this in the CMOS setup. Make sure modems or other devices are not conflicting with the serial communication port you are using. If you are using Com 1 to communicate to the SLC processor, then make sure there are no devices on Com 1 or Com 3. Turn off the FIFO buffers for the communication port you are using to connect to the SLC processor. To do this, click Start > Settings > Control Panel > System > Device Manager tab. Select comm ports and comm port 1, for example. Next, click the Advanced button and un-check the FIFO buffers box. SLC 5/05 Ch 0 default Ch 0 option Ch 0 option 1 Ch 1 default SLC 5/04 Ch 0 default Ch 0 option Ch 0 option 1 Ch 1 default SLC 5/03 Ch 0 default Ch 0 option Ch 1 default Ch 0 option1 SLC 5/02 RS-232 Full-Duplex default SLC 5/01 default 2 SLC 500 Fixed default 2 Half-Duplex DH-485 DH+ Ethernet MicroLogix Ch 0 default Ch 0 option 3 AIC+ or CBL-PM02 cable MicroLogix AIC+ or 1000 Analog Ch 0 default Ch 0 option CBL-PM02 cable RSLinx Driver RS-232 RS PIC 1784-KT Ethernet to DF-1 devices DF-1 devices devices or a 1784-KTX(D), the PLC KT, 1784-PCMK, or processor or 1784-KTX(D) 1784-PKTX(D) 5280-EI 1784-PCMK, or card module 1784-PKTX(D) card Hardware 1784-CP CP PIC, 1784-PCMK, 10 Base For the For the 1784-PCMK, 1784KTX(D), T HUB and MicroLogix 1000, MicroLogix 1000, 1784-KTX(D), 1784-KT Ethernet use 1761CBL-PM02 use 1761CBL-PM PKTX(D) 1784-PKTX(D) cable Series B 1 On these processors, you can configure channel 0 for DH-485. The SLC 5/03 channel 1 is DH-485 by default and channel 0 by option. 2 These processors cannot initiate communication. They can only act as responders. 3 This option only applies to MicroLogix 1000 Series D and Analog. 10

7 Converting.lib Files for Use with PLC-5 A.I. Series and 6200 Series PLC-5 Software This technical tip helps you convert.lib files so you can use them with PLC-5 A.I. Series and 6200 Series PLC-5 programming packages. If you wish to convert.lib files for use with RSLogix 5 software, see Software Connection issue 98.1, page 11. ToPLC-5 A.I. Series software is a PLC-2 to PLC-5 software conversion utility. When you convert your PLC-2 A.I. Series program to a PLC-5 A.I. Series program using ToPLC-5 A.I. Series, the software generates an.lib file. Since RSLogix 5 Reading the.pc5 File PLC-5 A.I. Series Software If you are using PLC-5 A.I. Series software, follow these steps: 1. Select [F1] - Select Program/PLC-5 Addr. Next, press [Insert] and type up to eight characters for new file. Press [Enter]. 2. Select the correct PLC-5 address and press [Enter]. 3. Select [F2] - offline programming/doc. A message appears stating that no program was found or that there was an error reading the file. 4. At the prompt to create new program file, select [F1] - Yes, then select the correct processor type and series. Press [ESC] when you see the prompt. 5. Select [F3] - Edit > [F2] - Block > [F9] - Load. 6. Select [F1] - Library to import. 7. Change your directory to point to your.pc5 project (project name.pc5). 8. Select [F7] - Perform import operation. Using the A.I. Series PLC-2 to PLC-5 Conversion Program to Create an.lib File and 6200 Series software do not read.lib files, your next step is to use a utility from the ToPLC-5 directory that converts.lib files into a.pc5 file format. This utility is called Lib2pc5.exe. Once files are in.pc5 format, PLC-5 A.I. Series and/or 6200 Series PLC-5 software can read and integrate them. Converting the.lib File to a.pc5 File 1. Locate Lib2pc5.exe in the TOPLC5 directory. The path may be similar to C:\Toplc5\Lib2pc5. 2. Either copy the.lib file to the TOPLC5 directory, or copy the Lib2pc5.exe file to the directory where the.lib file resides Series PLC-5 Software If you are using 6200 Series PLC-5 software, follow these steps: 1. From the 6200 Series PLC-5 Main menu, select [F7] - File Utility > [F6] - Import > [F1] - Procssr Memory. 2. Select [F3] - Select Source > [F4] - Enter Destin. Fill in the correct destination file name. 3. If the path is incorrect, select [F7] - Define Dir, then select [F6] to change to the proper directory. 4. Select [F1] - Begin Oper. When an import completes, the system generates a.log file and stores it in the \Ipds\arch\plc5 directory. Any errors that occurred during the conversion appear in the.log file. You can view the contents of the.log file with an ASCII text editor. 3. Execute Lib2pc5.exe on the newly created.lib file. For example, type: Lib2pc5 C:\path\projectname.lib 4. When conversion is complete, start the software that will read the.pc5 file. Follow the steps below for your specific package. 11

8 Using Rockwell Software SLC 500 Programming Packages with Allen-Bradley SLC 500 Processors The table that follows lists Allen-Bradley SLC 500 processors and the corresponding release of each Rockwell Software programming package that supports those processors. Each release number indicates the earliest release that supports each processor. Releases available after the indicated release also support their respective processors. RSLogix 500 PLC-500 A.I PA2E Processor/Series Release Series Release SLC 500 MODULAR PROCESSORS L553 5/05 (64K OS500) Not supported Not supported L552 5/05 (32K OS500) Not supported Not supported L551 5/05 (16K O500) Not supported Not supported L543 5/04 (64K O401) Any L542B 5/04 (32K OS401) Any L541 5/04 (16K OS401) Any L542A 5/04 (24K OS400) Any L532C/D 5/03 (16K OS302) Any L531 5/03 (8K OS302) Not supported L532B 5/03 (16K OS301) Any L532 5/03 (16K OS300) Any L524 5/02 (4K) Any Any 3.21 L514 5/01 (4K) Any Any Any L511 5/01 (1K) Any Any Any MICROLOGIX 1000 CONTROLLER Bulletin 1761 Micro Analog Not supported Not supported Bulletin 1761 Micro DH-485/ Not supported HD Slave only Full-duplex only Bulletin 1761 Micro Any SLC 500 PACKAGED CONTROLLERS L40A Any Any Any L40B Any Any Any L40C/F Any Any Any L40E Any Any Any L40L Any Any Any L40P Any Any Any L30A Any Any Any L30B Any Any Any L30C Any Any Any L30D Any Any Any L30L Any Any Any L30P Any Any Any L20A Any Any Any L20B Any Any Any L20C/F Any Any Any L20D Any Any Any L20E/G Any Any Any L20L/N Any Any Any L20P Any Any Any L20R Any Any Any Installing Evrsi.sys Activations on Your Network You can install Evrsi.sys activation keys on your network server for multiple-user access of a limited number of activation keys. Moving activation keys onto a server is different from moving them onto your local hard drive and requires involving your system administrator in the process. You can move EVRSI activation keys on to these network operating systems: Novell, Windows 95, and Windows NT. Use these steps to install activations on the server: 1. Determine the software configuration of the server and all the clients, making sure the network operating system and client operating system(s) are compatible. For example, use Windows NT clients with Windows NT or Novell 4.x servers. You cannot move an activation from a 32-bit operating system to a 16-bit server such as Novell 3.x. 2. Have the system administrator create a shared directory by creating a directory off the root of one of the drives on the server. If, for example, the server has drives C, D, E, and F, and drive F is for manufacturing file storage, the administrator can create the directory on drive F. The name of the directory should reflect its contents, such as Activations. You may wish to use the serial number on the master disk as the directory name. Notes to the system administrator: If you back up the server periodically, remove any directories containing activation keys from the backup list. Backing up activation files will set the archive bits on the files, thus corrupting the activation keys. Certain antivirus software, such as Norton Antivirus, will corrupt the Evrsi.sys activation file. Configure the antivirus software to avoid checking this file. 3. Have the administrator set permissions for the directory according to the table below. For this operating system: Windows 95 Windows NT Novell Set the following permission level: Full access Full access Read, write, create The permissions set depends on the network operating system installed on server. The number of activation directories on the server and the number of mapped drives created on the clients depend on the clients' operating systems and the number of total activation keys moved onto the server. 12

9 4. If a client computer on the network is running Windows 95, create a directory and corresponding mapped drive for each activation key you will move onto the server. For example, if you move five activation keys onto the server, you need five separate directories on the server and five separate mapped drives on each of the clients. If you move 10 or more activation keys onto the server, we recommend splitting up the activation keys into separate directories. You can do this by product group (all activation keys for one product group in one directory) or by placing a number of activation keys in separate directories. If corruption should occur, separate directories help prevent losing all activation keys on the server at one time. For example, if one activation directory becomes corrupt, you only lose the activation keys in that directory and not all the activation keys on the server. An activation key can become corrupt if there are problems on the hard drive, if you back up activation directories, or if someone attempts to move an activation key to or from an activation file on the server while the EVRSI file is open. The EVRSI file is in an open state whenever an activation key that is normally stored in the file is in use. 5. Have the administrator go to one of the client systems and map the shared file folder on the server as a networked drive on the client system. This file folder should now appear as a mapped drive on the client. 6. While the administrator is still logged on, place each master disk in the drive and run the EVMOVE program to move the activation key from the master disk to the appropriate mapped drive on the server. It is necessary to perform this operation from one of the clients when the software is installed on the client and only the activation keys are on the server. Note to the system administrator: If clients attached to the server have multiple operating systems, such as some running Windows 95 and others running Windows NT, move the activation keys from one of the Windows NT systems onto the server. This is necessary because Windows NT systems have security features that Windows 95 does not. 7. Once you move the activation keys to the server, make the necessary changes to the appropriate system files as shown in the following table, and to each of the clients as well. You do this so the software can locate the activation on the mapped network drive. The changes you make depend on the Rockwell Software products installed on the client systems. In the table, the letter X represents the letter of the mapped drive(s). For this type of software: A.I. Series software Windows-based Rockwell products that use the Icom.ini and/or Rocksoft.ini files, such as RSLogix 500 revisions 1.26 and below, and RSView32 software. These files are normally found in the Windows directory in Windows 95 and in the Windows NT directory directory in Windows NT. Windows-based products that do not use the Icom.ini and/or Rocksoft.ini files, such as RSLogix 5 and RSLogix 500 revisions 2.0 and above. Make these changes to the system files: Add this line to the Autoexec.bat file: SET CHECKDRIVES = XCA Under the [COMMON] heading, change KEYDISK = FALSE to KEYDISK = TRUE and add this line: CHECKDRIVES = XCA For Windows 95: Add this line to the Autoexec.bat file: SET CHECKDRIVES = XCA For Windows NT 4.0 and above: Set an environment variable for the system. To do this, access the Control Panel, click System, then click the Environment tab. In the Variable text box, type: Checkdrives. In the Value text box, type: XCA 13

10 Tutorial: Executing Remote I/O Channel Configuration and I/O Configuration for PLC-5 Processors There are two distinct parts to a PLC-5 project that relate to I/O, remote I/O (RIO) channel configuration and I/O configuration. The following table gives you some important differences between the two. Remote I/O Channel Configuration I/O Configuration When do I need REQUIRED - Remote I/O will not function if you do not OPTIONAL - I/O configuration provides a convenient method for this configuration? configure it in the RIO channel scan list. You can complete documenting, setting up, and monitoring block transfer channel configuration manually or automatically. modules. You can always configure all modules in all programming packages manually by using the data table editor Channel configuration is not necessary for I/O resident to alter the bits in the block transfer write (BTW) data blocks, in the local chassis. according to the data table maps in the modules' user manuals. What does this Channel configuration sets up communication to remote I/O. I/O configuration programs operating parameters for configuration do? The scan list tells the processor the adapters on each configured modules. You must show each module's starting channel and the addresses assigned to each one. rack-group address as active in the channel configuration. What does this Channel configuration sets up I/O at the adapter level I/O configuration addresses individual I/O modules. configuration affect? without taking specific modules into account. Is configuration You can execute channel configuration automatically. I/O configuration always requires some manual operation. automatic or manual? All I/O adapters can report their existence and the Depending on the programming package, it may be possible amount of I/O they control. However, you must define an to graphically choose the BTW and block transfer read (BTR) I/O Status file to Auto-config. instructions for a particular module. The information that follows is about remote I/O channel configuration, part I of this technical tip. In issue 98.3, we will discuss I/O configuration, part II. The examples we cite in both parts I and II apply to an enhanced PLC-5 processor, which includes the enhanced, Ethernet, ControlNet, or VME processors. RSLogix 5 software is the programming package. This tutorial only applies to remote I/O, which is very different from ControlNet channel configuration. PART I: Remote I/O Channel Configuration Channel configuration tells the processor the rack/group address of each adapter on the RIO channel, as well as the span, or amount of address space, the adapter controls or occupies. Adapters include processor channels in adapter mode, 1771-ASB, 1794-ASB, 1203-series modules, and others. The list of adapters communicating on a RIO channel is called its scan list. If you do not enter an adapter in a scan list for the processor RIO channel, the processor cannot control that I/O or block transfer to any module in that chassis. Adding Entries to the Scan List Manual Configuration To set up channel configuration manually in RSLogix 5 software: 1. Double-click Channel Configuration and select the tab for the scanner channel. 2. Enter data manually by clicking 0 under Rack, and typing the rack number. Then press: [Enter]. This creates a new entry starting at the selected rack, group 0, size 1/4 rack. You can click the group number Channel Configuration Dialog to change it. You can change the size by clicking it and pulling down the selections. The only valid selections for size are 1/4, 1/2, 3/4, and Full. Adapter type is not relevant to the scan list, so it does not appear. Adapter type is only relevant in the context of I/O configuration. Automatic Configuration If you can go online with the processor, it is better to use automatic configuration for the scan list. Automatic configuration instructs the processor to poll all possible addresses and compile a list. If the I/O address doesn't appear in the scan list, the processor cannot access it. 14

11 To use automatic configuration: 1. Define the I/O Status file (S:16) on the Main tab of the Processor Status dialog. For example, a 1771-ASB adapter in a 1771-A3B 12-slot chassis starting at rack 2, group 0, with one-slot addressing generates two entries: Rack: Group: Size: 2 0 Full 3 0 1/2 If the local chassis does not end on a logical rack boundary, you cannot use any I/O addresses remaining in the logical rack for remote I/O. Process Status Dialog 2. Enter an unused data table file number. If programming online, put the processor in remote program mode. Type in an unused integer file number. If programming offline, type in an unused integer file number. The software creates an integer file of the correct size named IOSTAT, usually 48 words. The I/O Status file is now defined. Do not increase or decrease this file size. Also, do not use this file for other program functions. 3. Take the processor on line, then click the Auto-config button. The processor returns a list of all adapters it can find on the channel. 4. If the list doesn't have all the entries you expect, check the cables, adapter switch, and processor switch settings. You may also create a diagnostic file for the scanner channel. When online, put the processor in remote program mode. Select Channel Configuration in the project view, click on the tab for the desired scanner channel, and type in an unused file number. The software will create an integer file of the correct size and name it CONFIG. Files for any additional scanner channels will also be named CONFIG. Each channel s diagnostic file must be unique. You must choose a new, different, unused file for each channel. The diagnostic file keeps statistics on the communications between the PLC and I/O. This data is helpful when troubleshooting communications problems. Working with Scan List Limitations The scan list can hold a maximum of 32 entries. Each channel can use up to 16 different logical rack numbers within those 32 entries. Each adapter device counts as one entry. Adapters controlling or occupying more than one logical rack (eight words) of I/O take two entries. For example, if the local chassis is a 12-slot chassis with 1-slot addressing, it will cover Rack 0, Group 0, to Rack 1, Group 3. You cannot use Rack 1, Group 4 to Rack 1, Group 7. You can use logical rack numbers on more than one RIO scanner channel, but you cannot use the same or overlapping spans on more than one channel. For example, you can have Rack 2, Group 0, Size 1/2 on a different channel than Rack 2, Group 4, Size 1/2. If Rack 3, Group 0, Size 1/2 is on one channel, Rack 3, Group 2, Size 1/2 cannot be on another channel, since the spans overlap. Speeding the Scanning Rate Using Multiple Entries of the Same Adapter You can place the same device entry on the scan list more than once to speed up the scanning rate for that I/O. Each copy of the entry counts toward the limit of 32. Communicating Faster with Local I/O Transfers If possible, place critical I/O in the local chassis or, if you have a PLC-5/40L or PLC-5/60L processor, in an extended local chassis. This is because local I/O will always communicate faster than any remote I/O, even when scanned more than once in the scan list. Avoiding Timeouts If you have a PLC-5/30, PLC-5/40, PLC-5/60, or PLC-5/80 processor, consider putting the RIO connections on channels 2A or 2B. One communication microprocessor on the processor motherboard handles channels 0, 1A, and 1B. If you have a lot of traffic on all these channels, such as serial communication in user mode to an intelligent device, messaging between processors, MMI data, and/or many RIOs, this may overwhelm the communication processor and cause timeouts. Channels 2A and 2B are controlled by a different communication microprocessor. To help avoid timeouts with other processors, since there is no other communication processor to use for partitioning communication traffic, slow down the rate of block transfers, messages, and MMI polling. 15