Ethernet/IP Device is faulty configured

    Good day.

    Been having trouble with communicating with an I/O node.

    We are using ethernet/ip and Allen Bradley system for this project, we are used to Profinet and siemens.

    Currently, communication with main PLC is fine. we recieve and send data through the internal device without problems.

    Also, at the tool of the robot there is a laser measurement device(sick), which is connected through an I/O module, and then to an I/O node (I call it an I/O node, i dont actually know what the correct word is) then from there to our ethernet/ip network.

    However the device comes up as faulty configured in robotstudio/flexpendant. Sometimes after restart it throws the error 71500.

    ive tried different EDS files, currently im using an EDS file ive downloaded directly from the node's webserver.

    I can ping the I/O node with the assigned IP adress.

    I can access the webserver of the node with the assigned IP adress.

    I can see it inside RSlinx software, where it has the correct IP adress.

    I've double checked with PLC guys to double check the IP adress list to check for double assigned.

    Products:

    I/O node: Allen-bradley 1734-aent/a

    I/O module: Allen-bradley 1734-IE4C

    Robot: ABB IRC5 6.12.04 /w relevant options 841-1, 997-3.

    Quote from verove

    Hey Landqvisttim,

    This error usually stems from a from EDS. The IP setting for the IO module is fine. You've probably been provided the wrong EDS file, or you've chosen the wrong setting for this specific IO module.

    Hello Verove.

    Thank you for your reply. How would you go about to do theese settings? And where would i find the correct EDS file? Ive browsed both AB webpage and ive tried the supplied EDS file from modules webserver.

    I dont feel like im making progress anywhere at the moment,

    In my experience, dealing with EDS files for Ethernet can be really tedious. It looks like you've imported an EDS directly and used all the data in the EDS template.

    In reality, you only need a few fields needed for the EDS to be able to talk to the module. And every now and then, the error on the FP will actually tell you which field is the incorrect one.

    I'd suggest you start a new adapter (as opposed to importing the whole EDS template) and start with the simplest, necessary fields you know are correct. Normally, the fields just must enter are:

    • Name
    • Label
    • Address
    • Vendor ID
    • Product code
    • Device type
    • Input size
    • Output size

    You'll have to dig through the EDS file (they'll open up in any text editor) to find these. When these are correct, the error will go away. The input / output assembly also needs to be entered, but when these fields are incorrect the error is not severe. This approach will also help you narrow down which field is not correct.

    I'm not familiar with the specific IO module you're using, but the input and output size are really important, and it must match exactly with how many bytes of data you're trying to transfer in either direction. With the current configuration shown in your screenshot, it looks like your device has only inputs and no outputs, is that correct?

    Quote from verove

    In my experience, dealing with EDS files for Ethernet can be really tedious. It looks like you've imported an EDS directly and used all the data in the EDS template.

    In reality, you only need a few fields needed for the EDS to be able to talk to the module. And every now and then, the error on the FP will actually tell you which field is the incorrect one.

    I'd suggest you start a new adapter (as opposed to importing the whole EDS template) and start with the simplest, necessary fields you know are correct. Normally, the fields just must enter are:

    • Name
    • Label
    • Address
    • Vendor ID
    • Product code
    • Device type
    • Input size
    • Output size

    You'll have to dig through the EDS file (they'll open up in any text editor) to find these. When these are correct, the error will go away. The input / output assembly also needs to be entered, but when these fields are incorrect the error is not severe. This approach will also help you narrow down which field is not correct.

    I'm not familiar with the specific IO module you're using, but the input and output size are really important, and it must match exactly with how many bytes of data you're trying to transfer in either direction. With the current configuration shown in your screenshot, it looks like your device has only inputs and no outputs, is that correct?

    -With the current configuration shown in your screenshot, it looks like your device has only inputs and no outputs, is that correct?

    Correct, we will only use analog values from a sick laser.


    So heres where im at right now.

    • Name AENT_Laser
    • Label AENT-1734 (?)
    • Address 192.168.1.14
    • Vendor ID 1 (same for all the EDS files ive searched through)
    • Product code 108 (Same for all the EDS files ive searched through)
    • Device type 12 (Same for all the EDS files ive searched through)
    • Input size 8 i think?
    • Output size 0

    When i try theese settings i get error message 71500,

    Ethernet/ip connection failure.

    Quote from Lemster68

    You are using outputs from the device, not to the device. The output size reflects, at least, the size needed for the analog signal. Have you tried connecting directly to the robot? "IO node", is that a switch?

    I/O node is an 1734-aent point I/O, Ethernet adapter.

    You are using outputs from the device, not to the device. The output size reflects, at least, the size needed for the analog signal

    So it seems i have gotten this twisted around? i.e output in settings becomes input in the robotsystem?

    We have gotten it to work through main PLC, but we would like to cut the main plc it doesnt need to use that data.

    Quote from Landqvisttim

    Correct, we will only use analog values from a sick laser.

    This means it's 8 outputs from the module (i.e., 8 inputs to the robot), and 0 inputs to the module (i.e., 0 outputs from the robot).

    Remember the input and output size is in bytes, not bits or words.

    Keep in mind that the input and output size does not mean the number of inputs / outputs you're using. It must match what the module physically has. So if the module has, say, 10 input bytes but you're only using 8, the configuration must still include all 10 bytes.

    Quote from verove

    This means it's 8 outputs from the module (i.e., 8 inputs to the robot), and 0 inputs to the module (i.e., 0 outputs from the robot).

    Remember the input and output size is in bytes, not bits or words.

    Keep in mind that the input and output size does not mean the number of inputs / outputs you're using. It must match what the module physically has. So if the module has, say, 10 input bytes but you're only using 8, the configuration must still include all 10 bytes.

    i will have to look into this tomorrow morning, I tried quickly to find howm any bytes theese two modules use with no success. The manual doesnt seem to declare it.

    One other thing: I've run into issues using AB 1734-series I/O modules in the past. Sometimes they simply don't work "out of the box" -- they need to be connected to an AB PLC first and have their internal configuration set properly (using RSLynx or some other part of the RSLogix software chain) before they will communicate with any Master/Scanner device.

    HI,

    I am stuck in configuring the AB 1734 with 1 input (1 byte) card and 1 output(1 byte) card.

    I have configured IP(192.168.0.10) and chassis(3) within the AB 1734 module.

    But I am unable to find the right EDS configurations for it, So I tried some from the net which end up giving me faulty configuration error.

    I couldn't find any manuals\doc which explains the parameters like Input assembly, output assembly, configuration assembly, configuration size.

    Please help me solve this!!

    IRB 6700

    IRC 5 CONTROLLER

    Rw: 6.13


    Thankyou

    Hi,

    At first glance, I see that you've configured the module as 1 output byte, and 2 input bytes, as opposed to the 1 output / 1 input that you've mentioned. Remember that these values are what the module has not what the module uses.

    You don't always need all the fields filled out before you can configure it--you can seen my comment above on which are the more necessary ones. I'd recommend starting by filling only the necessary fields first, instead of importing the whole template.

    You can find all these values in the EDS file, depending on what your application is.

    Thank you, Verove. It is now working properly. I would like to share the steps I followed to configure the Allen-Bradley 1734 module and integrate it using an Ethernet/IP interface.

    First, I configured the AB module on their webpage and downloaded the EDS template from the "Diagnostic overview" window at the bottom of the screen. Then, I moved the EDS file to the controller's home EDS folder.

    Next, I used the "Scan EDS files" function in the RS I/O system > EthernetIP > StartAutoconfiguration to make the EDS file available for use when adding a new "Ethernetip\Device."

    In the Instance Editor, I set the input size and output size according to the total number of inputs and outputs in the modules. In my case, I had 3 input modules with 8 inputs each and 3 output modules with 3 outputs each. Therefore, I set the input size to 6 (the total of all inputs and outputs) and the output size to 3 (the number of output modules).

    I'm not sure why the input size needs to be set as the sum of inputs and outputs, but any other value results in an error.

    I followed Verove's advice didn't change anything else.

    Quote from verove

    You don't always need all the fields filled out before you can configure it--

    Now all the input and Output are working, tomorrow am going to add an analog card to it hope it works too.

    Quote from athuludayan

    I'm not sure why the input size needs to be set as the sum of inputs and outputs, but any other value results in an error.

    If this module works like other AB modules I've encountered in the past, each Output module probably has an "status" byte that comes back to the robot or PLC as an Input. The detailed documentation for the Output module probably has the details buried in a footnote somewhere.

    Quote from SkyeFire

    If this module works like other AB modules I've encountered in the past, each Output module probably has an "status" byte that comes back to the robot or PLC as an Input. The detailed documentation for the Output module probably has the details buried in a footnote somewhere.

    I have carefully reviewed the manual multiple times, but unfortunately, I was unable to find any information regarding the desired configuration. Despite reaching out to AB for assistance, their response did not prove to be very helpful. However, if I am able to successfully configure it, I plan on creating a manual of my own to share with others who may encounter this issue in the future. It took me two days to work on this

    Quote from athuludayan

    However, if I am able to successfully configure it, I plan on creating a manual of my own to share with others who may encounter this issue in the future. It took me two days to work on this

    It's always good when posters publish their final resolution to a an issue.

    Keep in mind that the "extra" inputs could potentially be before or after your "real" inputs, and when you add additional I/O modules to the AB backplane, the byte addresses could move around. So your "real" inputs might be bytes 0-2 of the entire 1734 assembly (most likely), or might be byte 5-7 (less likely, but not impossible).

    It's annoying, which is one reason I tend to avoid AB I/O modules for robots. But they can be made to work, you just need to be aware that you might need to map all 8 Input bytes and test them out to determine which 3 bytes are the actual discrete I/O points on the Input cards. Then you can remove the mapping to the "extra" input bytes to simplify your I/O table.

Advertising from our partners