adccommunitymod (AutomationDirect) asked a question.

GS-EDRV 100 Communication with RSLogix 5000

Created Date: June 22,2012

Created By: jefrob4

**** This post has been imported from our legacy forum. Information in this post may be outdated and links contained in the post may no longer work.****

I am trying to get a GS serier drive to talk to RSLogix 5000 through the GS-EDRV 100 module. I have the module setup with the ip address and I can see it over the web, but when I create a generic ethernet module in rslogix I cannot get it to communicate. I attached a screen shot of the rslogix screen for setting up communication. I noted three fields that I cannot find information for in the literature for the module. Any help would be appreciated.


  • adccommunitymod (AutomationDirect)

    Created Date: June 22,2012

    Created by: Do-more PE

    The GS-EDRV100 can only communicate via MODBUS TCP/IP which is vastly different than Ethernet IP which is used by Allen Bradley equipment.

    Some Allen Bradley controllers can talk MODBUS TCP/IP, but I do not have a list of which ones have the capability.

  • adccommunitymod (AutomationDirect)

    Created Date: June 25,2012

    Created by: jefrob4

    Gs-edrv 100

    I am told that Version 16 and up of rslogix 5000 will talk modbus and we have setup some modbus on our systems, but the gs-edrv 100 talks ethernet ip and then modbus. I am trying to get it to talk to rslogix before i connect it to the gs drive.

  • adccommunitymod (AutomationDirect)

    Created Date: June 25,2012

    Created by: dnj

    the GS-EDRV100 only talks Modbus TCP/IP, Ethernet IP is not supported. This is stated in the specifications:

    http://www.automationdirect.com/static/specs/gsedrv100.pdf

    If version 16 can talk Modbus, does it support both client & server (or master/slave)connections? Since the EDRV100 is a slave device, you will need to set up communications in the AB device to read/write to the EDRV100 the addresses you read out of the drive:

    http://www.automationdirect.com/static/manuals/gsedrvm/ch1.pdf

    refer to page 27 of the above manaul for Modbus addressing

    Expand Post
  • adccommunitymod (AutomationDirect)

    Created Date: June 25,2012

    Created by: franji1

    Found this app note on AB website: Looks to be serial only (Modbus/RTU), not Modbus/TCP

  • adccommunitymod (AutomationDirect)

    Created Date: June 26,2012

    Created by: jefrob4

    Gs-edrv 100

    Great comments guys. Thanks for all the input. To address some of the questions given as followup:

    "The GS-EDRV100 provides a low cost, high-performance 10/100Mbps Ethernet

    link between a control system and a GS Series AC Drive. The control system can

    be any of the following:

    • DL205 CPU, DL405 CPU, or a WinPLC, with the appropriate Ethernet Remote

    Master module (H2-ERM or H4-ERM).

    • A Productivity3000 CPU using the onboard Ethernet port.

    • A PC running Entivity’s ThinknDo software, a PC using a custom device driver that

    was developed using our Ethernet SDK, or a PC running KEPDirect EBC or OPC

    Server.

    Any independent I/O controller with a Modbus TCP/IP driver. Page 10 of the user manual

    According to Allen Bradley, they would qualify to speak to this device. And it says specifically Modbus TCP/IP.

    Now a second point on the AB article speaking about Modbus. This is speaking specifically about serial communication from AB to other modbus devices, and not over TCP/IP.

    Conclusion, I am still looking for a usable answer to the communication issue.

    Expand Post
  • adccommunitymod (AutomationDirect)

    Created Date: June 26,2012

    Created by: dnj

    Have you tried just using Modbus Slave, this is a Modbus simulator software, if you can communicate successfully to this, then talking to the EDRV100 is the same thing.

    http://www.modbustools.com/modbus_slave.asp

    You could also use Modbus Poll, this acts like a Modbus master, if you can successfully talk to the EDRV100, then it is a setup issue on the AB side.

    Expand Post
  • adccommunitymod (AutomationDirect)

    Created Date: June 27,2012

    Created by: GKiser

    jefrob4, I don't want you to get confused. When the manual says, "Any independent I/O controller with a Modbus TCP/IP driver " it means that any 3rd-party device that has Modbus TCP/IP master capability can talk to the GS-EDRV100 slave. So if your AB Ethernet module can be a Modbus TCP Master device, then it most certainly can talk to the GS-EDRV100 with no problems. The issue becomes only what Modbus addresses you want to read and write to in the GS-drive itself. These are listed in the GS-drive manual.

    For example to read P0.00 (Motor Nameplate Voltage) from a GS2, you would read Holding Register 1 (i.e. nomenclature 40001) (pg. 4-11 in my GS2 manual).

    Expand Post
  • adccommunitymod (AutomationDirect)

    Created Date: July 13,2012

    Created by: Nucor_Dave

    Modbus Master

    You can use a Prosoft card (MVI56-MNETR) This is a Modbus Ethernet Master. Prosoft has rslogix program examples. The modbus gateway can be used instead of the GS-EDRV.

  • adccommunitymod (AutomationDirect)

    Created Date: July 16,2012

    Created by: jefrob4

    Gs-edrv 100

    Thanks for the info. I believe I will just stick with the Powerflex 40's from AB. They are much simplier to configure and not that much more expensive now.

10 of 11