Topic: P200

Communications Remote I/O and GS-Drives

 

 

 

 

 

 

 

 

 

 

 

 

 

Design Considerations for Remote I/O Network

It is important to understand that only one Remote I/O network can be on an unmanaged switch. If two or more Remote I/O networks are mixed into the same physical LAN (local area network), duplicate IP addressing will occur and the system will not function properly. Multiple Remote I/O networks can be used on a managed switch using the VLAN feature to create a virtual separation of the different networks, but multicasting messages are necessary for the network to function properly. Care must be taken when designing a system this way (using a managed switch).

 

Even if only one Remote I/O network is being used in a facility, it is strongly recommended to keep it on a dedicated network, physically isolated from other networks.  As mentioned above, the Productivity Suite Remote I/O network makes use of multi-casting messages and many devices will not function properly in this situation.

 

The GS Drive configuration does not use multicasting in its setup but there are some initial UDP broadcast messages that occur upon discovery when initiated from the software and at power up. This should be considered if installing the GS Drive network with other devices.

 

 

 

 

Configuration of Remote Slaves

(P3 Only)

The Productivity Suite Remote I/O is very easy to configure. Each P3-RS or P3-RX Remote Slave module’s address is set by rotary switches on the front of the module. The X1 switch is used to set the least significant digit and the X10 switch is used to set the most significant digit. So if the X10 switch were set to 2 and the X1 switch were set to 4, the Slave Address of that module would be 24. Valid addresses are 01-99. 00 is not valid.  Each slave module must have a unique address and up to 16 slave units are allowed on a single system.

 

 

The address rotary switches are only read by the P3-RS/RX at power up. Power must be cycled after an address change for it to take effect. Connect a straight through (patch) Ethernet cable from the front of the P3-RS/RX module to an Ethernet switch. Connect a straight through cable from the P3-550 Local Ethernet (Remote I/O) port (lower Ethernet port) to the same switch. Open up the Productivity Suite Programming software and connect to the P3-550. Once the software is connected, open Hardware Config. Select the “Read Configuration” button in the upper left hand corner of this dialog and the P3-550 will automatically discover the slave modules connected to the switch and return all found P3-RS/RX modules and their configurations (bases and I/O modules).

 

 

 

 

 

 

There are two fields that can be configured in regards to connectivity to the slave modules. The above diagram shows the CPU hardware configuration popup where these settings can be found.

 

  1. Timeout between data query and response: This is the time allowed (in 10 millisecond units) between when the CPU sends a message to the P3-RS/RX and when a response is required. If the CPU does not receive the response within the time specified, the outcome will depend on how the P3-RS/RX and its I/O modules are configured:

 

 

 

CAUTION: If a timeout occurs and a module within a P3-RS/RX base or expansion base connected to the P3-RS/RX has the “Automatic Module Verification” selection enabled, the CPU will go out of run mode and a critical error will be generated.

 

 

 

 

 

 

CAUTION: If a timeout occurs and the P3-RS/RX module has the “Automatic Remote Base Group Detection” selection enabled, the CPU will go out of run mode and a critical error will be generated.

 

 

 

 

 

 

  • If a timeout occurs but all of the modules within the P3-RS/RX base or expansion bases connected to the P3-RS/RX have the No Verification and Enable Hot Swap selection enabled and the P3-RS/RX module has the “Do not Detect if the Remote Base Group is Disconnected” selection enabled, the CPU will remain in Run and a non-critical error will be generated.
  1. Comm Heartbeat Value: This value is used to help the P3-RS/RX determine that the P3-550 is no longer communicating to it.  If the P3-RS/RX module does not receive a message from the P3-550 within the time frame specified in the “Comm Heartbeat Value” field in the P3-550 configuration window, the P3-RS/RX module will turn off all of its outputs.

 

 

 

Configuration of GS-Drive Connections

GS Drive connections are set up in a similar manner as the Remote Slaves. Set a unique address for each GS-EDRV100 using its DIP switches. Or set the DIP switches to 0 and select the address using NetEdit (free download at AutomationDirect.com). 01-64 are valid addresses for a GS-EDRV100 in a Productivity Suite system. Since the DIP switch settings can only represent 00-63, setting a GS-EDRV100 to address 64 must be done using NetEdit.

 

 

After the GS-EDRV100 modules’ addresses have been set, be sure to connect the serial cable that comes with the GS-EDRV100 to the GS-Drive serial port.  The GS-EDRV100 will automatically configure the GS-Drive serial port to the correct settings. Once the GS-EDRV100 is properly addressed and connected to the GS-Drive, connect a straight through (patch) Ethernet cable from the Ethernet port of the GS-EDRV100 to an Ethernet switch. Connect a straight through cable from the P-Series CPU Local Ethernet Port (Remote I/O) to the same switch.

 

Open the Productivity Suite Programming software and go online with the P-Series CPU.  Select Setup and then Hardware Configuration. Select the “Read Configuration” button in the upper left hand corner of this dialog and the P-Series CPU will automatically discover all of the GS-EDRV100s connected to the switch and display all found GS-Drives.

 

 

 

 

 

 

 

 

Once the drives have been discovered, the configuration of each drive can be read and written from the programming software.

 

 

To allow the P-Series CPU to automatically write the drive parameters on each CPU project transfer and when the CPU is powered up, a setting must be configured in the P-Series CPU project. Go to Tools and Options and select the “Project Transfer” tab.  Select the “Transfer GS drive configuration” as shown below. Drive parameters are ONLY transferred to the GS Drive at project transfer or at boot up of the CPU.

 

 

To monitor the status of the connection between the P-Series CPU and the GS-EDRV100 modules, use the status bits of the GS Read and GS Write instructions as shown below.  If a Timeout occurs or an error is received, this can be monitored in the ladder code and appropriate action can be taken.

 

 

The Communications Heartbeat function is configured differently for the GS Drives than the Remote Slaves. Primarily because, as mentioned previously, there are two possible communication paths that could be lost:

 

  • P-Series CPU to GS-EDRV100
  • GS-EDRV100 to GS drive

 

To configure the GS-EDRV100 and GS Drive to detect and react to loss of communications, three parameters should be configured appropriately in the drive.

  

As shown below, parameter P9.03 determines what the drive will do when it detects loss of communications. Parameter P9.04 enables the transmission loss detection feature. Parameter P9.05 determines the amount of time the drive will wait for a transmission before assuming that the link is lost and react according to how parameter P9.03 is configured.

   

The GS-EDRV100 reads these configured parameters and if they are configured for detecting communications loss, it will also monitor for loss of communications on the Ethernet side. If communications are lost on the Ethernet side, the GS-EDRV100 will shut down the GS Drive.

   

 

 

 

 

 

 

 

It is very important to note that if the communications loss feature is enabled; either a GS Drive Read or GS Drive Write instruction needs to be configured to communicate to the GS-EDRV100 and GS Drive at a poll rate that will prevent the GS-EDRV100 and GS Drive from detecting a loss of communication.

 

There is also a parameter (P22.01) that can be monitored to check the health of the serial connection between the GS-EDRV100 and the GS Drive.  This parameter can be monitored in the ladder code and appropriate action taken if serial communications loss is detected.

 

 

 

 

 

 

 

 

 

Help File Feedback and Comments

 

THIS FEEDBACK IS ONLY FOR THE PRODUCTIVITY SUITE HELP FILE!!!

To submit Software Related Comments or Feedback , click on the green text.

As a continued effort to provide the best products to our Customers, we provide this Feedback Page where you, the User, can easily communicate to us any issues, suggestions, and comments (good or bad) about this Help File.

Your input is very important to us!  Please take a minute to complete the information below.  When finished, click the Send Feedback button and your email client will open with all the information already filled.  If satisfied with the information, go ahead and send the email.  Internet access and email account is required to send this email.

Thank you for helping us provide top quality products and for trusting AutomationDirect for your automation needs and services.

 

If we use the information you provide or post your comments on the official Productivity CPU Web Site or any other publication, we will send you a small gift as a way of thanking you for your input.  The gift depends on what's available at the moment and may consist of a Cap, T-shirt or some other ADC souvenir.

 

Complete the form provided below and click on the Send Feedback button when finished to open your email client and send the form.

Subject:

Name:

Company:

 

We will  ONLY use your email address if you request a reply or if we need an address to send you a thank you gift:

 

Email:

 

Please provide your Shirt Size just in case the gift is a T-shirt.

 

Shirt Size:

 

Enter your Comments below:

 

I give AutomationDirect.com permission to use my feedback,

my name, and my company name.