ProgrammerMN (Customer) asked a question.

October 23, 2026 at 6:18 PM
P1-540 CPU to the new P1-UX Bus Coupler. Hardware configuration setup in the CPU to establish comms.

I am having issues getting these two to communicate. I have multiple ProtosX couplers connected. I assume based on the webbased setup for the P1-UX that it would be similar. I keep getting a "Invalid Target to Originator Network Connection Size" error message. I have tried setting up my Datatype as 16 bit unsigned, 32 bit 1D array. Changed both input and output instances to include run/idle header. Tried everything I can think of, but still get the same error.

  • 3 answers
  • 96 views

  • ADC_TechnologyGroup_06 (AutomationDirect)

    P1-UX example setup using P1-UX EDS file from EDS library.See image for reference to some things which may help out:

    1. The P1-UX uses byte arrays, so use Integer 8-bit Unsigned arrays in order to get properly sized arrays of 89 bytes and 33 bytes.
    2. Populate the Extended Status field with an array so that you can determine what error the P1-UX is returning to the P1-540 CPU. If it's something like 0x0127 or 0x0128 (shown as hex values in the help file, but decimal values equate to 295 or 296 by default in Data View) then it will be followed by the allowed array size.
    Expand Post
    Selected as Best

  • ADC_TechnologyGroup_06 (AutomationDirect)

    P1-UX example setup using P1-UX EDS file from EDS library.See image for reference to some things which may help out:

    1. The P1-UX uses byte arrays, so use Integer 8-bit Unsigned arrays in order to get properly sized arrays of 89 bytes and 33 bytes.
    2. Populate the Extended Status field with an array so that you can determine what error the P1-UX is returning to the P1-540 CPU. If it's something like 0x0127 or 0x0128 (shown as hex values in the help file, but decimal values equate to 295 or 296 by default in Data View) then it will be followed by the allowed array size.
    Expand Post
    Selected as Best

  • ProgrammerMN (Customer)

    Thank you for your response. That worked setting my DataType to 8-bit Unsigned. image

    • ADC_TechnologyGroup_06 (AutomationDirect)

      Great to hear! I realized from your post that others might assume that like ProtosX the P1-UX would be 16-bit data types, so I'll notify the product engineering team and get some documentation added to help clear that up!

 

Did this information resolve your issue?