IMDHMIControls LibraryShop main store

How-to

Set up a PSTX softstarter on EtherNet/IP with a ControlLogix

Industrial networks Published 6 min read

Short answer

Set parameter group 12 on the PSTX first: 12.02 FB interface connector to Anybus, 12.03 Fieldbus control to On, and a static address in 12.05, 12.06 and 12.07 with 12.08 DHCP OFF. Then add a Generic Ethernet Module in Studio 5000 with input assembly instance 100 at 12 words and output assembly instance 150 at 5 words; any other size and the starter rejects the connection.

On this page
  1. Set the PSTX parameters in group 12
  2. Add the Generic Ethernet Module in Studio 5000
  3. Sizing the Generic Ethernet Module for a PSTX on a ControlLogix port
  4. Prove the connection end to end
  5. Read the fault before changing anything
  6. Questions asked

The PSTX softstarter joins an EtherNet/IP network through its Anybus fieldbus interface, and a ControlLogix reaches it with a plain Generic Ethernet Module — no vendor-specific module needed. Two things have to be exact. On the starter, parameter group 12 must select the Anybus interface, enable fieldbus control and hold a static address. In Studio 5000, the module must carry input assembly instance 100 at 12 words and output assembly instance 150 at 5 words. Miss either side and the module faults in the I/O tree without moving a word. Do the starter first, the module second, then prove the data.

Set the PSTX parameters in group 12 #

Motor data comes first: rated current and the ramp settings decide whether the start is right at all, and they are set the same way whatever supervises the starter — the base procedure is the one in PSTX softstarter setup for pumps, fans and conveyors. Once the start behaves, give the starter its network identity:

  1. Set 12.02 FB interface connector = Anybus. This is the switch that puts an EtherNet/IP adapter inside the starter. No other setting, and no EDS file on the controller side, can give it one — the same reason an EDS file will not add EtherNet/IP to a terminal server.
  2. Set 12.03 Fieldbus control = On when the PLC commands the start and stop. Left Off, the starter still serves status words but ignores the control word you write.
  3. Set 12.08 DHCP = OFF, then enter the identity: 12.05 IP address, 12.07 Subnet Mask, and 12.06 Gateway when the controller sits on another subnet. Static addressing only, because the Generic Ethernet Module stores one fixed address.
  4. Program 12.11-12.21 to choose the extra status bits that ride along in the input data.
  5. Program 12.22-12.31 Fieldbus AI with the values you want to monitor; each parameter contributes one input word.

Cycle control power after changing the interface and address parameters if the display still shows the old values — the installation manual lists which parameters take effect only after a restart.

Add the Generic Ethernet Module in Studio 5000 #

Adding the PSTX as a generic module trades a vendor faceplate for a fixed, documented assembly map. That trade-off is the one weighed in EDS versus generic Ethernet configuration in Studio 5000, and the generic side is the right side here because the assemblies are published and stable.

  1. Under the controller's Ethernet port, add a Generic Ethernet Module and enter the address from 12.05.
  2. Set the data format to a 16-bit integer type such as Data-INT, because the assembly sizes are specified in words.
  3. Input assembly: instance 100, size 12. This direction is data from the starter into the controller.
  4. Output assembly: instance 150, size 5. This direction is data from the controller to the starter.
  5. Configuration assembly: take the instance and size from the PSTX fieldbus documentation. The application note LVD-EOTN146U-EN publishes the I/O pair, but the configuration instance is not among the facts gathered here, so read it there — and never nudge it to make a fault go away. A wrong instance is a mismatch to correct, not a setting to tune.
  6. Run the RPI at 100 ms. A softstarter's status and start commands do not need 10 ms service, and the slower rate leaves connection bandwidth for I/O that does.

The module properties must match the starter word for word — the same exact-match discipline as sizing a Generic Ethernet Module connection for WAGO 750 I/O. Download and go online.

Sizing the Generic Ethernet Module for a PSTX on a ControlLogix port #

Inputs, each with its source:

  • Input assembly instance 100, size 12 words — PSTX EtherNet/IP application note LVD-EOTN146U-EN.
  • Output assembly instance 150, size 5 words — same note.
  • Ten Fieldbus AI parameters, 12.22-12.31, each contributing one input word — the parameter list in the note.
  • The status word, plus the bits chosen in 12.11-12.21, fill the remainder of the input data.
  • One word = 16 bits = 2 bytes.

The rule: a Generic Ethernet Module connection is accepted only on an exact match of instance number and size, and word counts convert to bytes at two per word.

The arithmetic:

  • Input bytes: 12 words × 2 bytes per word = 24 bytes each update.
  • Output bytes: 5 words × 2 bytes per word = 10 bytes each update.
  • Input word budget: 12 words total − 10 words from 12.22-12.31 = 2 words for the status word and its 12.11-12.21 bits.
  • Output word budget: 5 words total − 1 word control word = 4 words of additional output data, whose contents the note's output table defines.

Result: the module properties must read input instance 100 at 12 words and output instance 150 at 5 words in a 16-bit format — 24 bytes in and 10 bytes out on every update.

Decision: enter those numbers and nothing else. A rejected connection with any other pair is a properties error, not a starter fault. Because 2 words is all the room the input has for status, confirm the layout of those two words against the note's input table before wiring ladder logic to bit positions — the arithmetic tells you the room, the table tells you the order.

Prove the connection end to end #

  1. Confirm the module sits in the I/O tree without a fault and the connection is running.
  2. Force a state change from a source you already trust — the keypad or the hardwired circuit — and watch the status word in the input array move.
  3. Check one mapped value end to end: whatever quantity you programmed into 12.22-12.31, its input word should track the real thing.
  4. Only when the machine is safe to start — guards closed and everyone clear — set the start bit in the control word, see the run state appear in the status word, then clear it and see the stop.
  5. Pull the Ethernet cable: the module must fault in the controller, and the starter must do exactly what its configured fieldbus-loss behavior says.

Writing that start bit is the same pattern used to start and stop a PowerFlex 700 over EtherNet/IP from CompactLogix — one control word with defined bits. The pattern transfers between vendors; the bit positions never do. Take the PSTX control word layout from the application note, not from a drive profile.

If a start the network says it commanded never reaches the status word, suspect the hardwired start path before the network — the failures collected in troubleshooting a PSTX softstarter that ignores hardwire start.

Read the fault before changing anything #

Symptom in the cabinet Check first
Module faults on download; starter does not answer ping 12.02 not on Anybus, a wrong 12.05 entry, or a subnet mismatch with the controller
Ran fine, faulted after a power cycle 12.08 DHCP left On, so the address moved
Connects, every input word reads zero Directions or sizes swapped: 100 is the input, 150 is the output
Status word updates, start bit does nothing 12.03 Off, the wrong control word bit, or a hardwired start holding it off
Extra bits or values read wrong 12.11-12.21 and 12.22-12.31 not programmed to what the logic expects

Ping the starter from the engineering PC before touching Studio 5000 at all. A failed ping removes the controller and its module properties from the suspect list in one step.

Questions asked

Why does the Generic Ethernet Module fault as soon as I download?

The controller tried to open a connection to an adapter that is not there or does not match. Ping the address first: if ping fails, it is 12.02, 12.05 or the subnet; if ping works, it is the module properties. The input assembly must be instance 100 at 12 words and the output instance 150 at 5 words, in a 16-bit format.

Why did the connection work on the bench and fail after a power cycle?

12.08 DHCP is still On. The starter came back up on a different address than the one stored in the Generic Ethernet Module, so the controller connects to nothing. Set 12.08 to OFF, re-enter 12.05, 12.06 and 12.07, cycle control power, and the address stays where you put it.

The status word updates but the start bit does nothing. Is the network down?

No, the input path is alive. Check that 12.03 Fieldbus control is On, confirm you are setting the bit the control word table in the application note defines, and verify the hardwired start path is not holding the starter off. One of those three gates every start.

What do parameters 12.11 through 12.21 actually do?

They choose which additional status bits the starter packs into the input data next to the status word. Decide them before you write logic, because the ladder reads fixed bit positions in those words: change a selection after the fact and the meaning of the bits your code watches can move.

Can I read motor data through this connection, or only start and stop?

You can read values. Program the quantity you want into one of the Fieldbus AI parameters 12.22 through 12.31 and it arrives as one of the input words in assembly 100. The input table in the application note gives the word order, so read the position from it rather than assuming word one is the status word.

Keep reading

  • How-to

    Set up Micro850E implicit messaging to a Kinetix 5100 servo

    The implicit connection to a Kinetix 5100 is created in the Micro850E controller's EtherNet/IP module configuration under Ethernet > Modules, not by a UDFB. The drive is added as a natively supported motion slave, the UDFBs then run above the active connection producing commands and decoding status, and the same controllers accept up to eight generic EtherNet/IP slave devices.

    Industrial networks

  • How-to

    Configure a PowerFlex 525 on EtherNet/IP from an Omron NJ301

    The tag data link fails after a good ping because the NJ, as the EtherNet/IP originator, must send the drive's chosen output assembly plus a 32-bit Run/Idle header: error 0x0127 means the output connection size is wrong. Import the revision-matched EDS, select the target assemblies it lists, create Input and Output network variables of exactly those sizes with the header included, and register them on the Tag Set tab.

    Industrial networks

  • How-to

    Connect an Omron PLC to Smart Function Kit Pressing

    Use EtherNet/IP between the Omron NX/NJ/NY PLC and the Smart Function Kit Pressing: Omron's EtherCAT runs CoE, the kit's runs SoE, and the two profiles cannot exchange data. Load the Sysmac Studio example project and drive the kit with the SFK_Command, SFK_Fast_Variable_Access, SFK_SerialNumberConverter and SFK_GetNotification blocks.

    Industrial networks