AENT 138 Slave Communication with R-30iA Fanuc Master

    Hello All,

    We purchased a used robot cell with Fanuc R-30iA robots. The cell came with Allen Bradley 1738-AENT IO blocks installed but they will no communicate with the Robots over Ethernet IP.

    It had been a few years since the modules were powered on so we had to re initialize a lot of settings to get the IO blocks status lights all to Green(chassis size, IP address etc) but now we are still unable to get the devices to "Running" state through the Ethernet IP section on the FANUC robot.

    We can successfully ping our device and have tried a variety of different settings to no avail.

    The rack consists of 10 "1738-IB8M12" Input modules, and 1 "1738-OB8EM23" output module.

    We were convinced it was an issues with the IO modules because we couldn't get the "PointBus Status" light to stop blinking red, but then we adjusted out chassis size and that went away and we are now convinced it is an issue on the robot side, but have run out of ideas as how to remedy this.

    Any info that could be shared on how to properly set your ethernet IP settings(Input assembly size, configuration instance etc) would be greatly appreciated, as right now we are basically going through other peoples examples and trying to copy them with no success.

    Cheers,

    Do you have an EDS file for the modules you are using? I usually open the EDS file in EZ-EDS software and find the assembly instances, vendor, device type, etc.

    What settings are you trying?

    We have had to use Multicast for Target to Originator Type for other AB IO modules.

    We found the EDS files via the web browser interface. Making sense of them is another question.

    That is an example of what the EDS file says and we aren't sure how make it work for us.


    We've been trying a variety of settings based on what we have found other people have used but we still havent been successful.

    The Settings that were previously on the robot for this were:

    Vendor ID: 1

    Device Type:7 (although pretty much everything we've looked up says it should be 12)
    Product Code:210

    Input Size: 5

    Output Size: 1

    RPI: 20

    Input assembly instance:44

    Output Assembly instance:34

    Configuration instance: 123

    I/O Data Type: 8 bit

    Timeout Multiplier: 4

    Reconnect: True

    Major Revision:3

    Minor Revision:18

    Alarm Severity: WARN

    RPI: 20

    Transport Type; Multicast

    RPI: 20

    O=>T: Run/Idle Header

    T=>0: Modeless

    Configuration String Status Size: 12 (when we try to make up a new connection, it does not allow us to edit this)

Advertising from our partners