IMDHMIControls LibraryShop main store

Troubleshooting

Why an FSoE connection is not established on a safety PLC

PLC programming Published 8 min read

Short answer

The controller stays in RunIntern and the drive holds EMERGENCY STOP because the FSoE master-slave connection never reaches the established state, so the command bits in the 2Byte Bit-Coded SMM (780-784) function are never transmitted. Match the FSoE addresses, put the correct module in the FSoE master slot, copy the master slot data to the slave slot and back, and in ctrlX SAFETY Engineering 1.7.1.8239 replace the ctrlX DRIVEplus slave object with the IndraDrive MPx20/21 FSoE slave.

On this page
  1. The deciding state: the FSoE session, not the EtherCAT link
  2. Why the safety command bits do nothing
  3. Why RunIntern raises no alarm
  4. Fix the connection in this order
  5. The ctrlX DRIVEplus slave defect in 1.7.1.8239
  6. The %IB25 and %QB56 gap is layout, not a fault
  7. Symptom-to-cause map
  8. Confirm the link, then return to production
  9. Questions asked

The FSoE connection is not established, and that one fact explains the whole symptom set: the C15 safety controller stays in RunIntern, the device diagnostic lightpipe shows yellow instead of green, and the ctrlX DRIVE holds EMERGENCY STOP no matter what you write into the safety command bits. Until the master and slave establish their session, the frames that carry those bits are never sent, so the drive never sees them. The fixes are concrete: match the FSoE address on the master and slave sides, put the proper module in the FSoE master slot of the EtherCAT configuration, copy the master slot data to the slave slot and the slave slot data back, and on ctrlX SAFETY Engineering 1.7.1.8239 replace the defective ctrlX DRIVEplus slave object with the IndraDrive MPx20/21 FSoE slave. The gap at %IB25 and %QB56 is not a fault; it is the documented firmware header plus block placement.

One quantity decides the drive-side case: whether the FSoE master-slave connection has reached the established state. The EtherCAT transport and the safety session are separate layers, and a healthy network proves nothing about the second one. The same layering is why a CODESYS EtherCAT master can leave xError false even when a cable is pulled, as described in why a CODESYS EtherCAT master reports xError false on cable pull. Judge this fault by the safety session's own state, never by the network LEDs.

With the session down you will see, together:

  • The C15 status bar shows RunIntern: the controller stays in RunIntern for exactly as long as its FSoE connections are not established.
  • The device diagnostic lightpipe is yellow instead of green.
  • The FSoE status word reads all zero: no session counters, no established partner.
  • The drive holds EMERGENCY STOP although the 2Byte Bit-Coded SMM (780-784) (Slave 1) bits read true in your program.

That stop is the safe state working as designed, because a slave without an established master must hold it. Never bridge, jumper or time out the condition to keep the machine moving; bring the link up and release the stop through the machine's documented reset.

Why the safety command bits do nothing #

The bits of the 2Byte Bit-Coded SMM (780-784) (Slave 1) function are application data, and FSoE carries application data only inside its safety frames. No established connection means no frames, so the drive never sees the bits whatever their value. For the same reason, acknowledging or resetting the drive's safety state cannot clear EMERGENCY STOP: the slave leaves its safe state only after a master connection exists, and only then does the machine's normal acknowledgment sequence apply.

So no change to the C15 program moves the drive. The safety logic is irrelevant until the link exists. Decision: fix the connection first and treat the command bits as unread until the FSoE status word stops reading zero.

Why RunIntern raises no alarm #

The default project setting has the FSoE diagnostics switched off. In that mode the application handles a missing or interrupted connection by treating every safety signal as safe, meaning 0, and the controller raises no alarm. It only shows RunIntern, which is exactly why the fault looks like a logic problem. With the diagnostics enabled, every interruption raises an Alarm and stops or passivates the controller outputs, which makes a dead session visible the moment it happens.

Decision: enable the diagnostics for this commissioning and switch them back off once the link is stable, as the vendor recommends, so production interruptions drive the signals to the safe state instead of passivating outputs. For a longer walkthrough of this state and its settings, the troubleshooting guide for the RunIntern state and its FSoE diagnostics follows the same path.

Fix the connection in this order #

  1. Record the firmware version, the ctrlX SAFETY Engineering version, and which FSoE slave object the project selects, meaning the ctrlX DRIVEplus object or an IndraDrive stand-in. Whether the version defect below applies depends on this record.
  2. In the C15 safety project settings, clear the check box that switches the FSoE diagnostics off, so a failed session raises an Alarm while you work.
  3. Set the FSoE address on the slave side, the ctrlX DRIVE, and on the FSoE master side in the safety project, and make the two match exactly. A mismatched address is a leading cause of a session that never establishes.
  4. In the EtherCAT configuration, check the module assigned to the FSoE master slot of the FSoE master. An improper FSoE module in that slot blocks the connection on its own.
  5. Verify the slot data copy in both directions: master slot data to the FSoE slave slot, and slave slot data back to the master slot, exactly as the selected slave object defines them. A wrong copy in either direction leaves the session down.
  6. If the ctrlX DRIVEplus FSoE slave object is selected under ctrlX SAFETY Engineering 1.7.1.8239, replace it with the IndraDrive MPx20/21 FSoE slave object and assign that object to the ctrlX DRIVE in the EtherCAT configuration.
  7. Rebuild, download to the C15 and start it, then confirm with the checks in the last section.

The ctrlX DRIVEplus slave defect in 1.7.1.8239 #

In ctrlX SAFETY Engineering 1.7.1.8239, the ctrlX DRIVEplus FSoE slave object carries a defect that prevents the connection even when the address, the master slot module and both copy directions are correct. The defect is fixed with the RM23.03 release. Until your installation runs a release that includes that fix, select the IndraDrive MPx20/21 FSoE slave object instead: it provides the same 3 assemblies as the ctrlX DRIVE object, among others, so it works as a stand-in. After the swap, rerun the order above from the address check onward, and plan the update to a fixed release so the substitution comes out at the next scheduled revision.

The %IB25 and %QB56 gap is layout, not a fault #

The layout is documented in Section 9.2, Functional Output, of the ctrlX SAFETY Programming Manual: the first 5 bytes of the functional output image are generated by the firmware and consist of the state, an alive counter, reserved bytes and the Error indication (Alarm, Fatal Error). Only at byte 5 does the application-defined I/O image start. The gap you see in the PLC is that header plus the place where the C15 block sits in the ctrlX CORE process image.

Worked example, input side of this installation. The C15's input block starts at byte 12 of the EtherCAT cyclic image and the application data lands at %IB25 in the PLC, so the offset is 25 - 12 = 13 bytes. The documented firmware header accounts for 5 of them, leaving 13 - 5 = 8 bytes of block placement. If the application data begins 5 bytes into the delivered block, the header sits at %IB25 - 5 = %IB20, so the five bytes %IB20 to %IB24 carry the state, the alive counter and the error indication, and %IB25 is the first application byte. Confirm the base against the slot start address in the ctrlX CORE I/O mapping rather than trusting the assumption.

The write side follows the same rule: %QB56 is where the application image for C15 inputs 0-3 begins, %QB24 is the slot's first output address, and the bytes ahead of %QB56 belong to the header and the placement the mapping shows. Never shift application variables into those bytes. Overlaying them reads state, counter and alarm bytes as process bits and hands your logic plausible-looking garbage.

Symptom-to-cause map #

Observation Cause Action
C15 status bar shows RunIntern FSoE connection not established Enable the FSoE diagnostics; correct the address pair, the master slot module and the slot copy
Device diagnostic lightpipe yellow, not green Same dead session Run the same three checks
FSoE status word all zero No master-slave session Match addresses, verify the module type and the copy in both directions
Drive in EMERGENCY STOP while SMM bits true Bits never transmitted Fix the connection first; the bits do nothing until it exists
All checks correct, no connection, ctrlX DRIVEplus slave on 1.7.1.8239 Engineering-version slave defect Substitute the IndraDrive MPx20/21 FSoE slave object
Inputs at %IB25 though the slot starts at byte 12 5-byte firmware header plus 8 bytes of placement Read the slot start in the I/O mapping; use %IB20 to %IB24 as the diagnostics window
  • The C15 leaves RunIntern and the device diagnostic lightpipe turns green.
  • The FSoE status word is no longer all zero.
  • The alive counter in %IB20 to %IB24 advances from scan to scan, which means frames are actually flowing.
  • The drive leaves EMERGENCY STOP only through the machine's normal reset sequence, now that a master connection exists.
  • After the link survives a few start-stop cycles, switch the FSoE diagnostics back off, per the vendor recommendation for production.

Decision, case by case. RunIntern with a yellow lightpipe and a zero status word: the session is down, so correct the FSoE address pair, the module in the FSoE master slot and the slot copy in both directions, because the command bits stay unread until the status word moves. Everything correct with a ctrlX DRIVEplus slave on 1.7.1.8239: substitute the IndraDrive MPx20/21 FSoE slave object and adopt a release containing the RM23.03 fix at the next revision. Inputs at %IB25 with the slot at byte 12: not a fault, so leave the header bytes alone and use them as your diagnostics window.

Questions asked

Can the EtherCAT network reach OP while the FSoE connection stays down?

Yes. The EtherCAT transport and the FSoE session are separate state machines: a ctrlX DRIVE and the safety controller can both reach EtherCAT operational mode while FSoE remains inactive, because OP only proves the cyclic transport. The safety session forms on top of that transport and needs its own address match and slot data exchange before any safety frame passes. Judge the safety link by the FSoE connection state, never by the network state.

What do the five header bytes show while the connection is still down?

Read as a window from %IB20 to %IB24, the state byte reports the controller as not connected, the alive counter holds one constant value because no frames arrive to advance it, and the error indication carries the Alarm flag once the FSoE diagnostics are enabled. A counter that never changes is itself evidence: it tells you the session is still dead while you correct the address, the master slot module and the slot copy.

Is the FSoE address the same as the EtherCAT slave address?

No. The EtherCAT configuration identifies the slave on the network; the FSoE address is a safety-layer value you assign in the safety project on both the master and the slave entry, and only those two must match. A correct EtherCAT configuration with a mismatched FSoE address is exactly the case where the network works, the drive still holds EMERGENCY STOP and the controller stays in RunIntern.

Does switching to the IndraDrive MPx20/21 slave object require revalidation?

The three assemblies it shares with the ctrlX DRIVE object keep the application image layout, so your program and mappings carry over, but the change is still a modification to a safety project. Rebuild and download to the C15, then return the machine to service under your site's safety recommissioning procedure and the vendor's validation requirements for modified safety projects. Note the engineering version in the project record so the RM23.03 fix gets adopted on the next update.

Keep reading

  • How-to

    Structure dock door conveyor interlocks in Studio 5000

    Run the conveyor on three explicit states — Ready, Running and Restart-required — with door-open, truck-present and curtain-clear as permissives. Truck departure mid-cycle stops the conveyor and latches a manual restart; the light curtain's protective stop stays in safety-rated equipment. Fix the door sensor before debouncing, then size the timer to the measured flicker — 600 ms against a 240 ms example.

    PLC programming

  • Troubleshooting

    Fixing a TwinCAT EtherNet/IP slave connection from an Omron PLC

    The CIP1 fault is a Forward Open mismatch: each Omron direction must carry the full serialized TwinCAT assembly, not the process variables alone. With 2 bytes in and 2 bytes out, the 4-byte ConnCtrl on outputs and ConnState on inputs make each direction 6 bytes, and the instances must follow producer and consumer roles. If a capture shows the request and a rejection, read the sizes and instances the originator actually serialized.

    Industrial networks

  • Troubleshooting

    PLC-5 not visible in RSLinx after processor replacement

    A replacement PLC-5 stays invisible in RSLinx because the 1785-ENET sidecar answers the network on its own while the processor waits for an application that configures the Ethernet channel 3A. Leave the non-isolated serial port disconnected until the cable is checked, bring the processor up over serial DF1 or DH+, download the saved program, and the Ethernet path returns.

    PLC programming