Sie sind auf Seite 1von 9

Add a driver

Communication drivers allow the communication device installed in a computer to communicate with the network it is attached to. You must configure the driver on the computer that the project will run on. To add a driver, from the Communication Setup dialog: If you are running on an Ethernet network If you are running any network other than Ethernet The following is a list of drivers available with this version of RSLinx Enterprise: Ethernet Serial DF1 DH+ (1784-PKTX, 2711P-RN6, 2711P-RN8) DH485 (1784-PKTX, 2711P-RN6) Serial DH485 (including 2711P-RN3, 2711-RN22C) Virtual Backplane Remote I/O (1784-PKTX, 2711P-RN6) Remote I/O (2711P-RN1 - PVPlus 400/600) ControlNet (1784-PCIC(S), 2711P-RN15S) ControlNet (1784-PKTCS, 2711P-RN15S. 2711P-RN15C) DeviceNet (1784-PCIDS, 2711P-RN10H, 2711P-RN10C)

How do I know which driver to add?


Use this driver Ethernet When you are running on this network And pointing to this target device Ethernet Ethernet IP devices Ethernet PLC5 devices Ethernet SLC devices PLC5 processors SLC DH+ devices SLC DH485 devices MicroLogix Logix processors (via the DHRIO module)

DH+

DH+

DH485 or Serial DH485

DH-485

DH485

DH-485

Logix processors SLC DH485 devices MicroLogix Logix processors PLC5 serial devices SLC DH+ serial devices SLC DH485 devices SoftLogix 1784-PCIC(S) 1771-RIO devices The local ControlNet card itself The local DeviceNet card itself

Serial DF1

DF1 point-to-point

Virtual ControlNet Backplane/ControlNet Remote I/O ControlNet I/O DeviceNet I/O Remote I/O ControlNet I/O DeviceNet I/O

Which daughter card applies to my application?


Catalog number 2711P-RN1 Application SRIO Network Interface Module for PanelView Plus 400/600 DH485 Isolated Network Interface Module for PanelView Plus 400/600 DH+ Network Interface Module for PanelView Plus 400/600 DeviceNet Scanner Card for PanelView Plus 400/600 RS232 Isolated Interface Module for PanelView Plus 400/600 DeviceNet Scanner Card for PanelView Plus and VersaView CE ControlNet Scanner Card for PanelView Plus 400/600 ControlNet Scanner Card for PanelView Plus and VersaView CE

2711P-RN3 2711P-RN8 2711P-RN10C 2711P-RN22C 2711P-RN10H 2711P-RN15S 2711P-RN15C Related topics

About the virtual backplane

Serial-DF1 driver properties, General tab


How do I access the dialog? The General tab on the Serial Properties dialog contains this information: Name

Displays the default name of the Serial driver. This name must be unique across the entire topology, and is limited to 255 characters. If you change this name, the new name displays in the Communications tree. COM Port This driver transmits data to a device connected to your computer's serial (com) port . Select a port from the list of all Comm Ports available on your computer. Available port numbers are 0 to 31 (default is 1). Device Choose the DF1 device that your computer is connected to. Channel 0 is used when connecting to the front port of PLC5, SLC 5/03, and SLC 5/04 processors. Station Number Enter the Station Number for this driver. All packets sent to this station address will be forwarded to RSLinx. Available station numbers are 0 to 254 decimal (default is 0). Use Auto-configuration Enable Use Auto-configuration to automatically detect the settings of the device connected to the specified COM port. Before using this, ensure the COM Port, Device, and Station Number settings are correct. When enabled, auto-configuration uses the Baud, Stop Bits, Parity, and Error Checking settings only as a starting point. Auto-configuration attempts the settings first, but their values do not reflect what autoconfiguration actually discovers. See the FactoryTalk Diagnostics window for the Auto-configuration settings the driver discovered. Related topics Serial DF1 driver properties, Link tab Add a driver Add a device Use the Communication Setup dialog

About the virtual backplane


The virtual backplane is a driver service that provides connectivity between RSLinx Enterprise and various device drivers and other applications within the RSLinx Enterprise server. It allows the software modules and communications resources contained in the server to be configured and visualized in a manner similar to the devices in a ControlLogix system. For example, both the PCICS and PKTCS device drivers plug into the virtual backplane. Packets received by one of these communications interface cards can be routed across the virtual backplane to (or through) any other interface card whose driver plugs into the virtual backplane, or to any application that plugs into the virtual backplane, such as the SoftLogix5xxx controller.

This is very similar to having a 1756-CNB and a 1756-ENBT module plugged into a ControlLogix chassis: packets received across the ENBT can be routed across the backplane out the CNB module, or to a controller sitting in the backplane. Note that RSLinx Enterprise occupies a slot in the virtual backplane (as can RSLinx Classis), which means that it is able to be both a source and a destination for packets sent over the backplane. This chassis-like model is carried over to the PanelView Plus (and VersaView CE) platforms in a minimalist fashion. For ControlNet support, those platforms implement two-slot virtual backplanes, where RSLinx Enterprise sits in one slot (slot #0) and the 2711P-RN15S ControlNet Scanner card sits in the other (slot #1).

Device Properties
When you add a device, the Device Properties dialog is displayed. The dialog contains this information: Name Displays the name of the device. This name must be unique to the entire network. When you add the device to the driver, you can assign a unique name to the device. For example, if you accept the default name when you add a 1756-ENB bridge device to an Ethernet network, the device will display below the driver as address, 1756-ENB, 1756-ENB. If you assign a unique name to the device, it will display below the driver as address, 1756-ENB, uniquename. Address Displays the location of the device. This address will vary based on the following:

A bridge device has an address for each incoming and outgoing port. The 1756-ENB below has an IP Address (111.111.111.111) for the incoming port, which is the address consumed on the Ethernet driver. The 1756-ENB also has an outgoing port that connects to the backplane. The 1756-ENB address (0) is the slot address the bridge device consumes on the backplane. The incoming device (1756-ENB) is not shown as a child on the backplane. For a non-bridge device, this is the address the device consumes on the driver. A non-bridge device only has an address for its incoming port. You can change this address by right-clicking the device and selecting Properties. In the example below, the address for the 1756-L1 processor is 1, and the address for the 1756-CNB processor is 2.

When you add a bridge device that connects a network to a backplane (e.g., when you add the 1756-ENB to the Ethernet), RSLinx Enterprise automatically assigns that device a default slot address in the backplane system. That default slot address assignment may conflict with the actual layout of the desired backplane system. In the illustration above, assume the 1756-L1 is in slot 0 and the 1756-ENB is in slot 1. When the 1756-ENB is added to the Ethernet network, it is automatically placed in slot 0 of the backplane; but you want to place the 1756-L1 in slot 0. Therefore, you need to modify the 1756-ENB slot address property, but there is no slot address on the 1756-ENB property page. That is because the slot address property for a bridge device that connects a network to a backplane (e.g., a 1756-ENB or 1756-CNB) is viewed and edited on the property page of the backplane itself. In the illustration above, right-click the 1756-A17 backplane to edit the connecting device's slot address. Tip: This situation exists when browsing networks containing bridge devices. If a browse does not display the expected results on the backplane, the bridge device's slot address property is probably incorrect. Select the backplane properties, ensure the slot address is set correctly, and then re-browse the backplane. Or, when you browse a network that contains a bridge device and you want to see what is on the other side of that bridge device, right-click on the bridge device itself and browse it. This determines the bridge

device's slot address in the backplane system. You will then see the expected results when you browse the backplane.

RSLinx Enterprise and RSLinx Classic side-byside operation


RSLinx Enterprise and RSLinx Classic can run simultaneously on the same computer, although there are some considerations that you must be aware of to avoid resource conflicts between these two applications.

Considerations
If your RSLinx Enterprise configuration consists of one of the following driver types and you need RSLinx Classic to communicate using that same driver, then you must share the driver within RSLinx Enterprise with RSLinx Classic:

Serial-DF1 1784-PKTX

To share one of these RSLinx Enterprise drivers with RSLinx Classic, execute the following steps: Tip: Serial DF1 is used in this example; however, the procedure is valid for the 1784-PKTX as well. 1. If you already have an RS232 DF1 driver configured in RSLinx Classic, select Communications > Configure Drivers. 2. From the Configure Drivers dialog, select the DF1 driver from the Configured Drivers list, and click Delete. The driver no longer appears in the Configured Drivers list. 3. Select View > Options and clear the Accept UDP Messages on Ethernet Port checkbox. Tip: Keep in mind that clearing this check-box in RSLinx Classic deactivates the Gateway Server in RSLinx Classic. You are also disabling RSLinx Classic from receiving unsolicited packets across Ethernet. Consider these facts when planning your side-by-side operation. 4. Exit and restart RSLinx Classic. 5. Launch either RSView Studio or the FactoryTalk Administration Console and navigate to the Communications tab. 6. Select the Ethernet driver, right-click the mouse, and select Properties. 7. Select the Advanced tab, and then click the Listen on Ethernet/IP Encapsulation Port checkbox. For more information on this checkbox, see Ethernet driver properties, Advanced tab. 8. If you do not already have a Serial-DF1 driver in RSLinx Enterprise, then add a Serial-DF1 driver. 9. Start RSLinx Classic and select Communications > Configure Drivers. 10. Select Remote Devices via Linx Gateway in the Available Drivers list and click Add New. 11. Name the driver, and click OK to display the Configure Remote Devices via Linx Gateway dialog. 12. Select your computer name in the Server Name selection list to display a list of drivers you can connect to. 13. Select the Serial DF1 driver you named from the Remote driver name list, and click OK. You now have connectivity for both RSLinx Enterprise and RSLinx Classic clients. When using RSLogix, remember to select the remote driver (e.g., TCP-1) instead of the direct serial DF1 (e.g., AB_DF1-1).

Tip: If you complete all of these steps and your local workstation does not show up in step 11 (above), then you need to restart the RSLinx Enterprise server so it can obtain sole ownership of the resources that were allocated by RSLinx Classic prior to clearing of the Accept UDP Messages on Ethernet Port checkbox. The easiest way to restart RSLinx Enterprise server is to reboot the host computer, although you can exit RSView Studio and use the Service Control Manager to restart the RSLinx Enterprise service. Notes: Please keep the following in mind:

The RSLinx Enterprise server only provides access to drivers for the RSLinx Classic package running on the local computer. Serial-DF1 (RS232 DF1 devices) and the 1784-PKTX/D drivers are the only driver types that can share access as described in this section. The virtual backplane is a sharable component between RSLinx Classic and RSLinx Enterprise. Since the PCICS plugs into the virtual backplane on the computer, it is sharable as well.

Related topics About the virtual backplane How do I set up my terminal to receive a file download across the serial port? When you run an HMI application, the question of whether or not to overwrite the RSLinx Enterprise configuration displays. When you select to overwrite the RSLinx Enterprise configuration on a terminal (or on the desktop), you are initializing RSLinx Enterprise with a new set of drivers and devices. If the RSLinx Enterprise configuration in the project does not contain a DF1 Serial Driver, the serial port will not be initialized and you will not be able to communicate across it. For example, assume you created a project that did not contain a DF1 Serial Driver, you downloaded that project to a CE terminal, and when presented with the overwrite question, you select Yes. This means now you cannot download subsequent projects across the serial port. Since you did not have a Serial Driver in the project, RSLinx Enterprise did not initialize the serial port when it consumed the new configuration during the overwrite process. There are two ways to ensure your terminal is prepared to receive a download across the serial port.

Always configure a DF1 Serial Driver as part of your terminal project even if you are not accessing data across it. Use the reset RSLinx Enterprise to defaults constructs available in ME Station. The default RSLinx Enterprise configuration on a terminal includes a DF1 Serial Driver.

If you have a serial cable from your desktop computer to the terminal, you can now add an autoconfigured Serial DF1 driver to your desktop configuration. The auto-configure logic detects the presence of the terminal and matches its settings accordingly. You are now ready to download across the serial port. Note that because the DF1 drivers auto-configure logic is a try once and then fail out body of logic, you must have the serial cable connected when the system executes its auto-configure logic.

Serial-DF1 driver properties, Link tab


How do I access the dialog? From the Explorer under the RSLinx Enterprise data server, double-click Communication Setup, rightclick the configured Serial driver, and select Properties. The Link tab on the Serial Properties dialog contains this information:

Baud This driver transmits data to your device at a specific baud rate. Match the setting of the device you are connected to Available rates are 110, 300, 600, 1200, 2400, 4800, 9600, 19200, 38400, 57600, and 115200. The default is 19200. Stop Bits Select the amount of time between data transmissions. Basic DF1 protocol generally uses 1 (default is 1). Parity Match the error checking method Error Check Match the setting of the device you are connected to (BCC must be configured the same. Ack/Poll Timeout (mSec) Enter an ACK Max. Retries Enter a value for the maximum number of times the system should retry. The default is 3. value. The default is 3000. or CRC ). All devices on the network of the driver you are connected to (None, Even, or Odd).

Glossary
access path An access path is used in OPC conversations to define the computer, driver, networks, and communication devices used to communicate with a destination device or processor. When RSLinx is functioning as an OPC server, an OPC client application can specify a DDE/OPC topic as the access path. ACK (acknowledgment) A control character used to acknowledge the reception and acceptance of a transmission block. address An address is a character string that uniquely identifies the physical location of an input or output circuit. In a processor, an address can also identify a memory location such as O0, B3, and N7. backplane A backplane is an interconnecting device that may or may not have intelligence, buy typically has sockets that cards or boards plug into. Passive backplanes add no processing in the circuit. A 1771 chassis, used for a PLC-5, is an example of a passive backplane. An intelligent, or active backplane may have microprocessor or controller-driven circuitry that provides additional functionality or processing. A 1756 chassis, used for ControlLogix, is an example of an active backplane. baud A unit of communication speed equal to the number of signal events per second. When one bit is encoded per each signaling event, the number of baud is the same as the number of bits per second. BCC Block Check Character (BCC) is an error checking method developed to improve error detection in data communications. The BCC is added to the end of each block of data before the block is transmitted.

block of data Reading or writing a block of data means exchanging more than one data element at a time as opposed to a single element. bridge device A bridge device is a module or device that converts communications from one protocol or network to another. bus In RSLinx Enterprise, a bus is defined as a network, driver, or chassis. channel A path for a signal. Several channels may share a common link. In RSLinx Enterprise, a channel is a driver. Channel 0 Refers to the DF1 serial port of an enhanced PLC5, an SLC5/03+, or a ControlLogix processor. CIP Control and Information Protocol. configuration A file that contains information about the physical structure you defined for your system. This file includes all network paths, defined drivers and devices, Data Providers, and object protocols. CRC Cyclical Redundancy Checking (CRC) is an error checking scheme where all characters in a message are treated as a string of bits representing a binary number. The number is divided by a predetermined binary number and the remainder is appended to the message as a CRC character. A similar operation occurs at the receiving end to prove transmission integrity. Data Provider The Data Provider is firmware residing in RSLinx Enterprise that provides connectivity to a particular class of devices, such as ControlNet, ControlLogix, and Remote I/O. driver The software that allows the communication device installed in your system to communicate over the network. Ethernet A local area network with a baseband communication rate of 10 megabits per second. jumper A short conductor with which you can connect two points. parity An error detection technique that tests the integrity of digital data within the computer system or over a network. Parity checking uses an extra bit that holds a 0 or 1 depending on the data content of the byte. Each time a byte is transferred or transmitted, the parity bit is tested. poll Systematically request data from a device. poll rate Often how data is requested from a device. Poll rates are typical specified in milliseconds. (A poll rate of 1000 ms results in data being requested every second). port The logic circuitry or software at a station that determines its communication parameters for a particular communication channel. shortcut Represents a specific path to a processor. This symbolic reference to a physical device is similar to a topic in RSLinx Classic. slot This is the node address of a selected device on the network. tag Represents a device on a network (usually a programmable controller), or an OPC server.

topology The way a network is physically structured. This includes all networks, devices, Data Provider, drivers/channels, and object protocols. In RSLinx Enterprise, the topology is structured as network.device.