Benji_603 (Customer) asked a question.

Read/Write to Lenze SMVector VFD from Click Plus (Ethernet/IP)

Hey Everyone,

 

I have been struggling to get the Click Plus to establish communication with my Lenze VFD over Ethernet/IP.

 

I have read through the comms manual for the lenze chip several times ( https://download.lenze.com/TD/COM__ESV__SMV%20EtherNet-IP%20module__v2-0B__EN.pdf) - however they only have the RSLogix example in the manual.

LenzeEthernetGenericWhen I go to set up the Ethernet/IP Adapter Settings for the CLICK Plus, I notice that I cannot change the Instance, Connection point, attribute etc. Isn't editability in these fields needed to read or write the correct register for the VFD? I feel like this is the reason I can't get communications between the PLC and VFD.

ClickEthernetSettingsPlease, if you've successfully implemented Lenze VFD control over ethernet/ip in a Click PLC or Click Plus please let me know. I am starting to wonder if I should just cut bait and go with MODBUS....


Benji_603 likes this.
  • ADC Community_02 (Automationdirect.com)

    Both the Lenze VFD and CLICK PLC are EtherNet/IP Adapters. You would need to add in an EtherNet IP Scanner like a P1000 to communicate to both devices.

     

    I would recommend to go with Modbus with the Click as the Master and Lenze VFD as the slave device.

     

    Definitions below for EtherNet I/P:

     

    Explicit Message Server: An explicit message server responds to request/response oriented communications initiated by explicit message clients. An example of an explicit message server is a bar code reader.

     

    Explicit Message Client: An explicit message client initiates request/response oriented communications with other devices. Message rates and latency requirements are typically not too demanding. Examples of explicit message clients are HMI devices, programming tools, or PC or Linux based applications that gather data from control devices.

     

    I/O Adapter: An I/O adapter receives implicit communication connection requests from an I/O scanner then produces its I/O data at the requested rate. An I/O adapter is also an explicit message server. An I/O adapter can be a simple digital input device, or something more complex such as a modular pneumatic valve system.

     

    I/O Scanner: An I/O scanner initiates implicit communications with I/O adapter devices. A scanner is typically the most complex type of EtherNet/IP device, as it must deal with issues such as configuration of which connections to make, and how to configure the adapter device. Scanners also typically support initiating explicit messages. A programmable controller is an example of an I/O scanner.

    Expand Post
    • Benji_603 (Customer)

      Thank you for the reply. Is there any plan or ability to add I/O scanner functionality to the CLICK series of PLCs in a future firmware or software update? I think this would really unlock the potential of the product line.

    • Benji_603 (Customer)

      Thank you for the help. I got a P1000 and things are going great - reading values like a pro and writing (sometimes) while messing with RPI settings. Loving the ease of use for the P1000 too. Thanks again!

      • Garry (Customer)

        Thanks for the update. I'm glad you got it working. The productivity series is one of the easiest controllers to set up for communication.

        Garry

      • z28z34man (Customer)

        I am glad you got it going with the P1000.

         

        If you are anything like me you wont look back from the productivity series. Before the P1000 even existed i got a P3000 for a project because a control logix was over budget and i liked liked the productivity series so much that i haven't looked back