• ADC TechnologyGroup_05 (AutomationDirect)

    I would recommend using EtherNet/IP Implicit Messaging (I/O Messing). Using the CompactLogix as the originating Scanner device and the BRX PLC as the target Adapter. The AutomationDirect video Team has a video that shows exactly this. 

    See link below.

    https://youtu.be/qsj8899fRNs

    Selected as Best
  • HOST_franji1 (HOST Engineering)

    Two common protocols between the two are probably

    1. Modbus TCP or RTU
    2. EtherNet/IP Explicit Messaging

     

    I do not know CompactLogix, but BRX PLC can be Master or Slave on either 1 or 2. How familiar are you with the two protocols on CompactLogix, as either master and/or slave? We can definitely help on the D-more/BRX side, and I'm sure there's others out there that can help with CompactLogix if you need help there.

    Expand Post
  • ADC TechnologyGroup_05 (AutomationDirect)

    I would recommend using EtherNet/IP Implicit Messaging (I/O Messing). Using the CompactLogix as the originating Scanner device and the BRX PLC as the target Adapter. The AutomationDirect video Team has a video that shows exactly this. 

    See link below.

    https://youtu.be/qsj8899fRNs

    Selected as Best
  • JWBaker3 (Customer)

    Thanks, will it work with strings? SS0-SS10 and/or SL0 - SL10? If not I can work around that by using the string to int conversion, but would be cleaner if it will work with strings directly

    Thanks again great help.

    JW

    • HOST_franji1 (HOST Engineering)

      Sorry, no strings. What is your data?

       

      If it's a structure, you could create a UDT in Do-more to match exactly what is in the CompactLogix, then use MEMCOPY to copy it into/out of D or N or whatever memory. Then configure your Implicit I/O to work with the D or N or whatever memory.

  • ADC TechnologyGroup_05 (AutomationDirect)

    I typically work with byte arrays when it comes to the device level exchange of EtherNet/IP Input Data (T->O) and Output Data (O->T). In Do-more Designer, I create Memory Blocks for Input and Output Data. I then use these in my EtherNet/IP Adapter setup. Moving raw bytes of O->T data into Strings, UDTs, and other data types is easy in Do-More Designer.

     

    Dmd_MemBlock_InputDataDmd_MemBlock_OutputDataDmd_AdapterSetup_InputDataDmd_AdapterSetup_OutputData

    Expand Post