mspaziani@seymour-at.com (Customer) asked a question.

January 10, 2023 at 7:18 PM
How to communicate to a SureServo2 AC servo drive via ETH/IP with a 1769- L38ERM Allen Bradley PLC. (Implicit Messaging)

I have the servo drive set up to communicate with the PLC and the PLC sees the module but when I try and push values to certain addresses through Implicit messaging I get no feedback. I generated an EDS file via the Servo software and used that to create my addresses. i am not seeing any information pulled from the servo or able to push anything as well Is there something I am missing in the configuration side of the Servo drive?

  • 7 answers
  • 1.87K views

  • ADC TechnologyGroup_05 (AutomationDirect)

    The 'Studio5kNoValues.jpg' image shows you highlighting and referencing the tag 'SureServo2:C.Address_of_P0_000x.' This is a Configuration Assembly tag which indicates the pointer ADDRESS for P0.000 (which is 0). You need to view the Input Assembly tags (T->O) that are probably labeled similar to 'SureServo2:I.Data[0]'.

     

    On positive note, this image also indicates that you successfully connected to the SureServo2 with your1769-L38ERM and have no errors.

    Expand Post
    Selected as Best

  • mspaziani@seymour-at.com (Customer)

    I've been through both videos thoroughly and even rewrote my EDS file to match verbatim. We aren't getting any error codes nor connection problems on our PLC and Drive. What's strange is that the PLC can see the module installed correctly with the right addresses pulled from the EDS, it just won't read/write data to the servo. Is it likely to be a problem with our PLC not communicating the correct datatypes, or even the ETH/IP module on the SureServo not communicating to the drive itself? Perhaps there's a setting I'm missing on the drive and/or PLC to specify Implicit Messaging?

    Expand Post

  • ADC TechnologyGroup_05 (AutomationDirect)

    If I were having this issue, I would divide my troubleshooting into separate tasks.

     

    Task 1: Confirm that the Drive and the SV2-CM-ENETIP module are successfully communicating. Parameter P3.045 in the Drive should be reporting the connected communication module type. If the Drive is successfully identifying the SV2-CM-ENETIP, the value should display a value of 5.

     

    Task 2: Confirm successful I/O messaging connection between the PLC and the SV2-CM-ENETIP. It sounds like you have already confirmed this.

     

    Task 3: Confirm a simple non-zero input value. In the SureServo2 Pro software, under the T->O PLC Input Values section, set IN_VALUE_1 to Parameter P0.000 and generate the EDS file. This will result in an EDS file that maps the first 32 bits of T->O data being sent from the SV2-CM-ENETIP to the PLC to be the drive's firmware version. I find it very beneficial to test with feedback that is a non-zero value. The current firmware version for the SureServo2 Drives at the time of this post is v1.0003.

     

    If all of this results in successful communication between the PLC and the SV2-CM-ENETIP, yet the drive is not executing moves as you would expect, then I suspect an incorrect configuration of the parameter values in the drive. The SureServo2 Drives are quite intricate. In order to get a full understanding of your scenario, you would need to provide the following:

    • Drive Configuration file (.par)
    • EDC file (.edc)
    • EDS file (.eds)
    • LogixDesigner project (.ACD)
    Expand Post

  • mspaziani@seymour-at.com (Customer)

    Task 1: On the digital display we are getting a 5 confirming it is a ETH/IP module and it has successful coms to the drive. There are also no errors shown that relate to the ETH/IP parameters.

     

    Task 2: Our PLC is displaying a connection to the IP address that we set for the SureServo2 Module in the Studio 5000 software. However it is hard to confirm the connection because we are not getting the transferring of values the would normally be pushed from the drive to the PLC.

     

    Task 3: After uploading just the firmware in the EDS file we are still getting no values from the T->O. It is showing a 0 as the value while the digital display is showing a 10003.

     

    Below I have attached the files from the sureservo2 along with the Studio 5000 program that we just created to test this. Also note the screenshots: Pro Software shows good connection to the drive via USB, reading params etc. No errors showing via USB (for ETH/IP). Studio 5000 showing connection to the module on the designated IP (we have the A-B on 192.168.0.10 and the Servo on 192.168.0.40) but reading no firmware data at all.

     

    Expand Post

  • ADC TechnologyGroup_05 (AutomationDirect)

    The 'Studio5kNoValues.jpg' image shows you highlighting and referencing the tag 'SureServo2:C.Address_of_P0_000x.' This is a Configuration Assembly tag which indicates the pointer ADDRESS for P0.000 (which is 0). You need to view the Input Assembly tags (T->O) that are probably labeled similar to 'SureServo2:I.Data[0]'.

     

    On positive note, this image also indicates that you successfully connected to the SureServo2 with your1769-L38ERM and have no errors.

    Expand Post
    Selected as Best

  • mspaziani@seymour-at.com (Customer)

    I can't believe such a simple mistake was throwing us off so much! That in conjunction with A-B bringing in the data as SINTs made it so we thought it was just pulling in garbage data. It's now reading/writing simple commands but not yet pathing. But we haven't had much time to play with that yet anyway. Thanks for all the help.

 

Did this information resolve your issue?