Patent Description:
Industrial automation systems may be used to provide automated control of one or more actuators. A controller may output a conditioned power signal to an actuator to control movement of the actuator. The controller may also receive signals from sensors connected to the system for diagnostics, machine health, safety, etc. By transforming these field sensors and actuators from analog devices to interactive digital devices, better control and information integration can be achieved. However, there is a need for a way to efficiently integrate such devices into the network infrastructure of current systems that enables their intelligent use. <CIT> relates to techniques for splicing single pair ethernet cables. By creating a T-shaped intersection, the splicing device allows for sensors and other devices to run perpendicular in relation to the original cable. The splicing device further enables the cable to have multiple drop points along the cable. <CIT> relates to a switch for use with single pair ethernet on four-pair cabling. An apparatus includes four independent single pair ethernet ports coupled to a cable comprising four wire pairs for communication with a micro-switch, the micro-switch configured for communication with four endpoint devices, each of the endpoint devices in communication with the micro-switch over a single pair ethernet cable comprising one of the four wire pairs. Each of the four independent single pair ethernet ports comprises an echo canceller for receiving input from a transmitter at one of the independent single pair ethernet ports and each of the other independent single pair ethernet ports to cancel alien crosstalk between the four wire pairs.

It is the object of the present invention to improve prior systems.

In some embodiments, an industrial Single Pair Ethernet (SPE) system to be installed within an industrial automation system is provided. The industrial SPE system comprises a linking device, a first device (one of a sensor and an actuator), a second device (one of a sensor and an actuator), and a trunk-drop infrastructure connecting the first device and the second device to the linking device. The trunk-drop infrastructure comprises a first tap, a first drop cable connecting the first tap to the first device, a second tap, a second drop cable connecting the second tap to the second device, a trunk cable connected between the linking device, the first tap, and the second tap, and an end cap connected to the second tap. The trunk cable includes a first pair of cables configured to transmit power and a second pair of cables configured as single pair ethernet cables. At least one of the first device, the second device, the first tap, and the second tap includes a dual-port SPE switch.

In some embodiments, a method of forming an SPE network within an industrial automation system is provided. The method includes forming an IP subnet trunkline using trunk cables having a power cable pair and an SPE cable pair and connecting a first device to the IP subnet trunkline by connecting a first pair of trunk ports of a first tap to the trunk cables, connecting a first drop port of the first tap to a first drop cable, and connecting the first device to the first drop cable. The method also includes connecting a second device to the IP subnet trunkline by connecting one of a second pair of trunk ports of a second tap to the trunk cables, connecting a second drop port of the second tap to a second drop cable, and connecting the second device to the second drop cable. At least one of the first device, the second device, the first tap, and the second tap includes a dual-port SPE switch. The method further includes connecting an end cap to another one of the second pair of trunk ports of the second tap, and connecting one of the trunk cables to a linking device that is connected to a wired network of the industrial automation system.

In some embodiments, an industrial SPE system for connecting devices within an industrial automation system is provided. The industrial SPE system comprises a trunkline formed by a series of trunk cables, where each trunk cable in the series of trunk cables includes a power pair and an SPE pair, and one or more taps connected between the trunk cables of the trunkline. The industrial SPE system further comprises a drop line connected to each of the one or more taps, and a device connected to each of one or more taps via the drop lines. The device is an actuator or a sensor, and at least one of the device and the one or more taps includes a dual-port SPE switch.

The present disclosure will be better understood and features, aspects and advantages other than those set forth above will become apparent when consideration is given to the following detailed description thereof. Such detailed description makes reference to the following drawings, wherein:.

Before any embodiments of the invention are explained in detail, it is to be understood that the embodiments are not limited in its application to the details of construction and the arrangement of components set forth in the following description or illustrated in the following drawings. Aspects of the present disclosure are capable of other embodiments and of being practiced or of being carried out in various ways. Also, it is to be understood that the use the phraseology and terminology used herein is for the purpose of description and should not be regarded as limiting. Furthermore, the use of "right", "left", "front", "back", "upper", "lower", "above", "below", "top", or "bottom" and variations thereof herein is for the purpose of description and should not be regarded as limiting.

The following discussion is presented to enable a person skilled in the art to make and use embodiments of the present disclosure. Various modifications to the illustrated embodiments will be readily apparent to those skilled in the art, and the generic principles herein can be applied to other embodiments and applications without departing from embodiments of the present disclosure. Thus, embodiments of the present disclosure are not intended to be limited to embodiments shown, but are to be accorded the widest scope consistent with the principles and features disclosed herein. The following detailed description is to be read with reference to the figures, in which like elements in different figures have like reference numerals. The figures, which are not necessarily to scale, depict selected embodiments and are not intended to limit the scope of embodiments of the present disclosure. Skilled artisans will recognize the examples provided herein have many useful alternatives and fall within the scope of embodiments of the present disclosure.

<FIG> is a schematic view of an example industrial automation system <NUM> in which embodiments described herein may be implemented. As shown, the system <NUM> can include a controller <NUM>, one or more drives <NUM>, and a user interface <NUM>, such as a human machine interface (HMI). In some applications, the system <NUM> can further include one or more safety relays <NUM>, and one or more input/output (I/O) modules <NUM>, <NUM>, <NUM>. Furthermore, the system <NUM> can include actuators (e.g., motors) <NUM> and sensors or switches <NUM>, <NUM>. As shown, the controller <NUM>, the drives <NUM>, the user interface <NUM>, the safety relay <NUM>, and one (or more) of the I/O modules <NUM>, as well as various other components of the system <NUM> not specifically shown or described herein, can be housed within a cabinet <NUM>. The other I/O modules <NUM>, <NUM>, the actuators <NUM>, the sensors <NUM>, <NUM> and/or other components of the system <NUM> not specifically shown or described herein, can be located outside the cabinet <NUM>, such as near, on, or within individual machines (not shown) operating in the system <NUM>.

The controller <NUM> may be programmed (e.g., via computer readable code or instructions stored on memory <NUM> and configured to be executed by a processor <NUM>) to provide signals to the drives <NUM> for driving the actuators <NUM>. Generally, the controller <NUM> may be programmed according to a specific configuration desired for a particular application. For example, the controller <NUM> may be programmed to respond to external inputs, such as reference signals, alarms, command/status signals, etc. The external inputs may originate from one or more relays or other electronic devices (such as the safety relay <NUM>, the I/O modules <NUM>, <NUM>, <NUM>, or other devices). The controller <NUM> may also respond to a defined set of operating parameters. The settings of the various operating parameters determine the operating characteristics of the controller <NUM>. For example, various operating parameters may determine the speed or torque of the drive(s) <NUM> or may determine how the controller <NUM> responds to the various external inputs. As such, the operating parameters may be used to map control variables within the controller <NUM> or to control other devices communicatively coupled to the controller <NUM>.

One form of external inputs to the controller <NUM> can include feedback data from one or more of the sensors <NUM>, <NUM>. More specifically, the sensors <NUM>, <NUM> can be located outside the cabinet <NUM>, such as on or near machines within the system <NUM>, and can provide information, such as feedback data, to the controller <NUM> via the safety relay <NUM> and the I/O modules <NUM>, <NUM>, <NUM>. For example, the controller <NUM> can be communicatively coupled to the sensors <NUM>, <NUM> through the safety relay <NUM> and the I/O modules <NUM>, <NUM>, <NUM> for detecting conditions such as operating temperatures, voltages, currents, pressures, flow rates, actual motor speed, voltage, frequency, power quality, alarm conditions, proximity, emergency stops, machine positions, hazardous locations, or other parameters within the industrial automation system <NUM>. With feedback data from the sensors <NUM>, <NUM>, the controller <NUM> can keep detailed track of the various conditions under which the industrial automation system <NUM> may be operating. Some sensors, such as sensors <NUM>, maybe considered safety sensors while others, such as sensors <NUM>, may be considered standard (e.g., non-safety) sensors. For example, safety sensors may include, but are not limited to, safety interlock switches, safety limit switches, emergency stop devices, absolute encoders, hazardous location switches, and presence sensing safety devices. Standard sensors may include, but are not limited to, inductive proximity sensors, photoelectric sensors, ultrasonic sensors, and light arrays.

The components within the cabinet <NUM>, including the controller <NUM>, the drives <NUM>, the user interface <NUM>, the safety relay <NUM>, and the I/O module <NUM> may be communicatively coupled via a wired IP subnet. More specifically, as shown in <FIG>, the components within the cabinet <NUM> may join the IP subnet by coupling to one or more cables <NUM> that extend through the cabinet <NUM>. In some embodiments, the cables <NUM> may use an industrial Ethernet network protocol (EtherNet/IP).

As shown in <FIG>, however, the sensors <NUM>, <NUM> of the system <NUM> are not EtherNet/IP-connected. That is, they do not directly connect to the cables <NUM> of the IP subnet and are not capable of communicating via IP subnet protocols, such as EtherNet/IP. Rather, they must be integrated into the system <NUM> via the I/O modules <NUM>, <NUM>, <NUM> or the safety relay <NUM>. As a result, sensor performance and data access from the sensors <NUM>, <NUM> to the controller <NUM> may be limited. Furthermore, as shown in <FIG>, safety and standard sensors <NUM>, <NUM> require different integration tools. For example, the I/O module <NUM> and the safety relay <NUM> may be required to integrate safety sensors <NUM> into the system <NUM>, while the I/O modules <NUM>, <NUM> may be required to integrate standard sensors <NUM> into the system <NUM>.

<FIG> illustrates a schematic view of another industrial automation system <NUM>, including an industrial single pair Ethernet (SPE) system <NUM> according to some embodiments. Like the system <NUM> of <FIG>, the system <NUM> can include a controller <NUM>, one or more drives <NUM>, a user interface <NUM>, as well as other devices <NUM>, stored in a cabinet <NUM>. The system <NUM> can also include an in-cabinet power supply <NUM>, though, in some embodiments, power may be provided by an external power supply (not shown). As shown in <FIG>, the components within the cabinet <NUM> can be part of a full EtherNet/IP network (e.g., part of a wired network or IP subnet) by connecting to Ethernet cable(s) <NUM> running through the cabinet <NUM>.

Referring still to <FIG>, according to some embodiments, the SPE system <NUM> can enable "smart" and/or "non-smart" sensors and other devices to connect to the EtherNet/IP network of the industrial automation system <NUM>, allowing for better control and information integration within the system <NUM> and removing the need for additional integration devices (such as relays and I/O modules). More specifically, in recent years, SPE technologies have developed enough that standards and chips are available to enable sensors and actuators that are capable of connecting to an Ethernet network. As such, "smart" sensors and actuators may be considered digital devices with such connection capabilities, while "non-smart" devices (also considered "legacy" devices) may be analog devices or digital devices without such connection capabilities. Such smart sensors and actuators with these capabilities may also be referred to as SPE sensors and SPE actuators or, collectively, smart devices or SPE devices. The SPE system <NUM> of some embodiments addresses the need to better integrate resource-constrained devices into an industrial automation system <NUM>. The SPE system <NUM> of some embodiments further enables integration of both smart devices as well as non-smart devices, and both safety and standard sensors, all on the same network using a trunk-drop infrastructure, thus providing a simplified network infrastructure and reducing the skill level of labor in building the industrial automation system <NUM> (e.g., compared to the system <NUM> of <FIG>). Furthermore, because the SPE system <NUM> of some embodiments can incorporate both smart and legacy devices on the same network, the SPE system <NUM> can serve both Brownfield (e.g., existing) applications and Greenfield (e.g., new) applications.

As shown in <FIG>, the SPE system <NUM> includes one or more taps <NUM> (including tap 46A, tap 46B, tap 46C, tap 46D, and/or tap 46E, shown in <FIG>, tap 46F, shown in <FIG>, tap <NUM>, shown in <FIG>, tap <NUM>, shown in <FIG>, and/or tap 46I, shown in <FIG>), one or more trunk cables <NUM>, one or more drop cables <NUM>, and an end cap <NUM>, as well as one or more safety sensors <NUM> (including legacy safety sensors 30A and/or smart safety sensors 30B), one or more standard sensors <NUM> (including legacy standard sensors 32A and/or smart standard sensors 32B), and/or one or more actuators (not shown). These components <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM> can be external to the cabinet <NUM>, such as on a machine within the industrial automation system <NUM>. As such, the SPE system <NUM> can be considered an "on-machine" SPE system <NUM>.

Furthermore, the SPE system <NUM> includes a linking device <NUM> to link the SPE system <NUM> to the EtherNet/IP network in the cabinet <NUM>. That is, as shown in <FIG>, the linking device <NUM> can be connected to the cable <NUM> of the EtherNet/IP network of the industrial automation system <NUM>, and a first one of the trunk cables <NUM> is connected to the linking device <NUM> as well as the in-house power supply <NUM>. In some embodiments, the linking device <NUM> can be housed in the cabinet <NUM>, as shown in <FIG>, or can be housed outside the cabinet <NUM>, such as on a machine. As a result, the SPE system <NUM> can provide both an SPE network and bus power network in a physical trunk-drop network infrastructure (e.g., provided by the trunk cables <NUM> and the drop cables <NUM>, as further described below). This trunk-drop network infrastructure of the SPE system <NUM> can simplify the power and communication infrastructure of the industrial automation system <NUM> and also enables easily adding, removing, or replacing devices within the SPE system <NUM> without changing configurations of other devices or software.

More specifically, as shown in <FIG>, the trunk-drop infrastructure of the SPE system <NUM> comprises the trunk cables <NUM>, the taps <NUM>, and the drop cables <NUM>, and terminates with the end cap <NUM>. Each of the taps <NUM> is a three-way connector with a first port, a second port, and a third port, where the first and second ports ("trunk" ports) are coupled to trunk cables <NUM> and the third port ("drop" port) is coupled to a drop cable <NUM>. The SPE system <NUM> forms an IP subnet trunkline <NUM> (e.g., formed by a series of trunk cables <NUM>) that connects to the linking device <NUM>, with multiple drop lines (e.g., drop cables <NUM>) coming off the trunkline <NUM>, and the SPE system <NUM> can include multiple devices connected to the trunkline <NUM> (e.g., to the trunk cables <NUM>), via the drop lines (e.g., via the drop cables <NUM>). In some embodiments, the SPE system <NUM> includes long trunks <NUM> between drop lines <NUM>, or may include no drop lines <NUM> at all, and can allow for new drop lines <NUM> to be added as needed.

The trunk cables <NUM> and, thus, the IP subnet trunkline <NUM>, are configured to facilitate communication via SPE. For example, as further described below with respect to <FIG>, the trunk cables <NUM> include transmission lines with an arrangement of conductors that enable power transmission as well as data transmission via EtherNet/IP. That is, the trunk cables <NUM>
include a pair of cables for power transmission to provide bus power across the SPE system <NUM> and at least one SPE cable pair for data communication. A dedicated bus power pair removes the need for complex and expensive power repeaters, which would otherwise limit the number of devices along the IP subnet trunkline <NUM>. Furthermore, the SPE pair enables common industrial protocol (CIP), IP, and SPE connectivity to the last-hop field-constrained device along the IP subnet trunkline <NUM>. Such connectivity can improve user experiences as well as provide better system integration and improved device data analytics (e.g., compared to the non-Ethernet-enabled infrastructure of the system <NUM> of <FIG>). That is, in addition to improved control of sensors, switches, and actuators within the industrial automation system <NUM> (e.g., due to their CIP, IP, SPE connectivity), the devices can provide additional diagnostic and analytics data to the controller <NUM> and higher level architecture of the system <NUM> (e.g., due to higher bandwidth capabilities, CIP integration eliminating need for protocol transformation, the switch-based daisy-chain network setup, and ability to provide run-time communications rather than only data after faults). In some embodiments, the IP subnet trunkline <NUM> may use user datagram protocol (UDP) EtherNet(IP, or another communication protocol.

As noted above, different numbers of devices can be added or removed to the IP subnet trunkline <NUM> due to its trunk-drop infrastructure. Furthermore, different types of devices may be used in different embodiments of the SPE system <NUM>, and different taps <NUM> can be used to connect any such device to the IP subnet trunkline <NUM>. More specifically, SPE devices 30B/32B can include circuitry that facilitates power transmission and Ethernet-enabled communication with power and data transmission lines, respectively, of the trunk cables <NUM>, while legacy devices may not. As such, in some embodiments, the SPE system <NUM> can include smart or SPE standard taps 46A configured to connect to legacy standard devices 32A, SPE safety taps 46B configured to connect to legacy safety devices 30A, and passive taps 46C configured to connect to SPE devices (e.g., standard SPE devices 32B, safety SPE devices 30B, or both standard SPE devices 32B and safety SPE devices 30B). Further details of the internal components of the SPE standard taps 46A and the SPE safety taps 46B are described below with reference to <FIG>, respectively, and it should be noted that any reference made throughout the description to an "SPE tap 46A/B" can be a reference to an SPE standard tap 46A or an SPE safety tap 46B. Alternatively, in some embodiments, SPE standard taps 46A and SPE safety taps 46B may have the same architecture such that they are not separate taps and, thus, may be referred to as SPE taps 46A/B. Additionally, in some embodiments, as shown in <FIG>, the SPE system <NUM> can include one or more power taps 46D configured to connect to an on-machine power supply <NUM>.

Generally, as further described below, the SPE taps 46A/B and the SPE devices 30B/32B of some embodiments can each include a dual-port SPE switch, facilitating connection to the SPE cable pair of the IP subnet trunkline and enabling location-based network service functionalities within the industrial automation system <NUM>. Such location-based network service functionalities can include, for example, auto-addressing, diagnostics, identification and verification, etc., and are generally not available using off-network devices or single-port-SPE devices. Accordingly, the SPE system <NUM> of some embodiments provides taps <NUM> that enable a single trunk-drop topology as well as SPE and IP protocol for both standard and safety, smart and legacy devices <NUM>, <NUM>. The taps <NUM> thus decouple traditional integration devices (such as relays, I/O modules, etc.) from the industrial automation system <NUM> and can enable better fault identification and diagnostics due to the switch-based daisy-chain network design.

Furthermore, the SPE system <NUM> can include different configurations and arrangements of trunk cables <NUM>, drop cables <NUM>, and taps <NUM> to enable different SPE network infrastructures. For example, <FIG> illustrates a block diagram of an SPE system <NUM> according to some embodiments. Generally, as shown in <FIG>, the SPE system <NUM> can include a linking device <NUM>, which may be connected to an EtherNet/IP switch <NUM> and a programmable logic controller (PLC) <NUM> (which may be the same as the controller <NUM> of <FIG> and <FIG>). The linking device <NUM> can be connected to SPE devices 30B/32B via passive taps 46C and legacy devices 30A/32A via SPE taps 46A/B. Furthermore, an end cap <NUM> can be placed after the last device <NUM>/<NUM> to terminate the system <NUM>. The SPE system <NUM> of <FIG> can be configured as a linear SPE network infrastructure <NUM>, coupled to a single SPE port <NUM> of the linking device <NUM>, as shown in <FIG>, <FIG>, and <FIG>, or a ring SPE network infrastructure <NUM>, coupled to dual SPE ports <NUM> of the linking device <NUM>, as shown in <FIG>, <FIG>, and <FIG>.

More specifically, a linear SPE network infrastructure <NUM>, as shown in <FIG> and <FIG>, may include a linear IP subnet trunkline <NUM> extending from the linking device <NUM> to a last hop device <NUM>/<NUM>, with an end cap <NUM> and, more specifically, a terminator 52A, positioned at the last hop device <NUM>/<NUM>. The trunk cables <NUM> and drop cables <NUM> may be configured to accommodate at least power transmission, as well as communication to and from the single SPE port <NUM>. A ring network infrastructure <NUM>, as shown in <FIG>, may include a ring IP subnet trunkline <NUM> that extends from the linking device <NUM> to the last hop device <NUM>/<NUM> and loops back around from the last hop device <NUM>/<NUM> to return to the linking device <NUM> using an end cap <NUM> in the form of a splicer 52B. The trunk cables <NUM> and drop cables <NUM> may be configured to accommodate at least power transmission, as well as communication to and from the two SPE ports <NUM>. <FIG>, <FIG>, and <FIG> illustrate a linear SPE network <NUM> converted into a ring SPE network <NUM> and a ring SPE network <NUM> converted into a linear SPE network <NUM>, respectively.

Accordingly, <FIG> is a schematic view of the SPE system <NUM> of <FIG> arranged as linear SPE network <NUM>, according to some embodiments. As shown in <FIG>, the linking device <NUM> can be a single-port SPE linking device, thus having an SPE port <NUM>. In some embodiments, the linking device <NUM> can include a media converter between SPE and multiple pair ethernet (MPE, such as standard four-cable pair ethernet), a sensor network manager (e.g., to perform topology discovery, device addressing, sensor network redundancy protocol, device replacement, etc.), a CIP router between the full EtherNet/IP network in the cabinet <NUM> and the UDP-only EtherNet/IP of the SPE system <NUM> (e.g., to integrate the two EtherNet/IP transport profiles seamlessly, including transport layer security (TLS)/ data transport layer security (DTLS) and cipher suite transformation), an I/O connection aggregator (e.g., to reduce the number of I/O connections of the controller <NUM> of the industrial automation system <NUM>, though safety I/O connections may not be aggregated in some embodiments), and a security proxy (e.g., to provide user access authorization on behalf of the network devices). Furthermore, the linking device <NUM> can recognize SPE devices (including taps <NUM>, sensors <NUM>, <NUM>, or actuators) and their location using linear network characteristics, can provide location-based network services (including device addressing, identification, verification, and diagnostics), and, in some embodiments, can provide a redundant network service (e.g., via a ring management protocol).

Furthermore, referring still to <FIG>, the trunk cable <NUM> can be a hybrid four-wire cable including a power cable pair (e.g., power and ground cables) and an SPE cable pair. More specifically, the trunk cable <NUM> can include a power cable pair <NUM> (such as a <NUM>-volt line and a ground line), which may connect to an in-cabinet power supply <NUM>, as shown in <FIG>, to provide power transmission across the network <NUM>. The trunk cable <NUM> can further include an SPE cable pair <NUM> (e.g., a linear SPE cable pair, denoted as D1+ and D1-), which connect to the SPE port <NUM> of the linking device <NUM>. For example, the power cable pair <NUM> may carry Direct Current (DC) power, while the SPE cable pair <NUM> may transmit communication signals (e.g., via EtherNet/IP).

Referring still to <FIG>, the SPE tap 46A/B, which can connect to a legacy device 30A/32A, can include a first port <NUM>, a second port <NUM>, and a third port <NUM>. The first and second ports <NUM>, <NUM> can each connect to the power cable pair <NUM> and the SPE cable pair <NUM> of the trunk cables <NUM>. Therefore, the first port <NUM> and the second port <NUM> can each include four pins (e.g., two pins for power bus connections and two pins for SPE connections). The third port <NUM> can connect to a drop cable 50A configured to connect to the legacy device 30A/32A. For example, the drop cable 50A can be a four-wire sensor cable including a pair of power wires and input/output wires and the third port <NUM> can include four pins to interface with the drop cable 50A (e.g., two pins for power bus connections and two pins for sensor interface connections). Thus, internally, the power cable pair <NUM> can extend across the SPE tap 46A/B between the first and second ports <NUM>, <NUM>, with connections branching off to the third port <NUM>, e.g., to connect bus power to the power pair of the drop cable 50A. The SPE cable pair <NUM> can connect from the first port <NUM> to the second port <NUM> via an internal dual-port SPE switch <NUM>.

Accordingly, the SPE tap 46A/B can include a dedicated SPE switch <NUM> to integrate legacy devices 30A/32A into the SPE system <NUM> through the trunk-drop infrastructure. For example, <FIG> is a schematic view illustrating further detail of an SPE standard tap 46A, according to some embodiments, for use with the SPE system <NUM>. And <FIG> is a schematic view illustrating further detail of an SPE safety tap 46B, according to some embodiments, for use with the SPE system <NUM>. As shown in <FIG>, the SPE standard tap 46A can include a first port <NUM>, a second port <NUM>, and a third port <NUM>, as described above. Internally, the SPE standard tap 46A can include a power management module <NUM> (e.g., coupled to the power cable pair <NUM>), the SPE switch <NUM> (e.g., a dual-port SPE and physical network (PHY) switch, coupled to the SPE cable pair <NUM>), a microcontroller unit (MCU) <NUM>, and a sensor interface <NUM>. The sensor interface <NUM> can provide connections, through the third port <NUM> (and, more specifically, through pins of the third port <NUM>), to a legacy standard sensor 32A including, for example, power connections (<NUM>-volt, ground) and sensor data connections (e.g., IO-Link, I/O). In some embodiments, the sensor interface <NUM> can include an IO-Link interface as shown in <FIG>, or a discrete sensor (or actuator) interface (not shown).

As shown in <FIG>, the SPE safety tap 46B can include a first port <NUM>, a second port <NUM>, and a third port <NUM>, as described above. Internally, the SPE safety tap 46B can include a power management module <NUM> (e.g., coupled to the power cable pair <NUM>), the SPE switch <NUM> (e.g., a dual-port SPE and physical network (PHY) switch, coupled to the SPE cable pair <NUM>), a first MCU <NUM>, a second MCU <NUM>, and safety input circuitry <NUM>. The safety input circuitry <NUM> can provide connections, through the third port <NUM> (and, more specifically, through pins of the third port <NUM>), to a legacy safety sensor 30A including, for example, power connections (<NUM>-volt, ground) and safety sensor data connections (e.g., Channel 1A, Channel 1B, Channel 2A, Channel 2B).

Referring back to <FIG>, the passive tap 46C, which can connect to an SPE device 30B/32B, can include a first port <NUM>, a second port <NUM>, and a third port <NUM>. The first and second ports <NUM>, <NUM> can each connect to the power cable pair <NUM> and the SPE cable pair <NUM> of the trunk cables <NUM>. Therefore, the first port <NUM> and the second port <NUM> can each include four pins (e.g., two pins for power bus connections and two pins for SPE connections). The third port <NUM> can connect to a drop cable 50B configured to connect to the SPE device 30B/32B. More specifically, the SPE device 30B/32B can be a dual-port SPE device, including a dual port SPE switch <NUM>, and the drop cable 50B can be a hybrid six-wire cable including a pair of power cables to transmit power from the trunk <NUM>, a first pair of SPE cables for uplink SPE between the trunk <NUM> and the SPE switch <NUM> and a second pair of SPE cables for downlink SPE between the trunk <NUM> and the SPE switch <NUM>. As such, the third port <NUM> can include six pins (e.g., two pins for power bus connections, two pins for uplink SPE connections, and two pins for downlink SPE connections). Thus, internally, the power cable pair <NUM> can extend through the passive tap 46C between the first and second ports <NUM>, <NUM>, with connections branching off to the third port <NUM>, e.g., to connect the power cable pair <NUM> to the drop cable 50B. The SPE cable pair <NUM> can connect from the first port <NUM> to the third port <NUM>, e.g., to connect to the uplink SPE pair of the drop cable 50B, and back from the third port <NUM> to the second port <NUM>, e.g., to connect to the downlink SPE pair of the drop cable 50B.

Accordingly, the passive tap 46C acts as a pass-through for power and data communication lines to the SPE device 30B/32B through the trunk-drop infrastructure, as the SPE device 30B/<NUM> includes its own dedicated SPE switch <NUM>. For example, <FIG> is a schematic view illustrating further detail of an SPE safety sensor 30B, according to some embodiments, for use with the SPE system <NUM>. <FIG> is a schematic view illustrating further detail of another SPE safety sensor 30B, according to some embodiments, for use with the SPE system <NUM>. And <FIG> is a schematic view illustrating further detail of an SPE standard sensor 32B, according to some embodiments, for use with the SPE system <NUM>.

As shown in <FIG>, the SPE sensors 30B, 32B can each include a port <NUM> configured to be communicatively coupled to the third port <NUM> of the passive tap 46C via the drop cable 50B. In some embodiments, as shown in <FIG>, the port <NUM> can include six pins to accommodate an uplink SPE pair (D1+, D1-), a power cable pair (<NUM>-volt, ground), and a downlink SPE pair (D2+, D2-). In other embodiments, as shown in <FIG>, the port <NUM> can include four pins to accommodate an uplink SPE pair (D1+, D1-) and a powered downlink SPE pair (<NUM>-volt/D2+, ground/D2-), and the SPE sensor 30B, 32B can include an internal power decoupler <NUM> connected to the powered downlink SPE pair (as described in more detail below). The SPE pairs can connect to the internal SPE switch <NUM> (e.g., a dual-port SPE and physical network (PHY) switch). The SPE sensors 30B, 32B can further each include a power management module <NUM> and the safety SPE sensor 30B can include a first microcontroller unit (MCU) <NUM>, a second MCU <NUM>, and a safety application <NUM>, as shown in <FIG>, or a first MCU <NUM>, a second MCU <NUM>, a third MCU <NUM>, and a safety application <NUM>, as shown in <FIG>. In some embodiments, the safety SPE sensor 30B may also include additional MCUs, such as more than three MCUs. The standard SPE sensor 32B can include an MCU <NUM> and an application <NUM>, as shown in <FIG>. It should be noted that the four-pin port <NUM> and power decoupler <NUM> shown in <FIG> can alternatively be incorporated into the safety SPE sensor 30B of <FIG> or the standard SPE sensor of <FIG>, and the six-pin port <NUM> shown in <FIG> can alternatively be incorporated into the safety SPE sensor 30B of <FIG>. Generally, the power decoupler <NUM> be used, in conjunction with a respective tap <NUM>, to enable power delivery through the SPE lines of a drop cable <NUM>.

More specifically, in some embodiments, the SPE system <NUM> may also be configured to be coupled to SPE devices 30B/32B that are internally powered. For example, <FIG> is another schematic view of the SPE system <NUM> of <FIG> arranged as a linear SPE network <NUM>, according to some embodiments. As shown in <FIG>, the linear SPE network <NUM> can include the passive tap 46C and the SPE tap 46A/B described above with respect to <FIG>, as well as a powered passive tap 46E to connect to a powered SPE device 30C/32C. The powered passive tap 46E can include a first port <NUM>, a second port <NUM>, and a third port <NUM>. The first and second ports <NUM>, <NUM> can connect to the power cable pair <NUM> and the SPE cable pair <NUM> of the trunk cables <NUM>. Therefore, the first port <NUM> and the second port <NUM> can each include four pins (e.g., two pins for power bus connections and two pins for SPE connections). The third port <NUM> can connect to a drop cable 50C configured to connect to the powered SPE device 30C/32C. More specifically, the powered SPE device 30C/32C can be a powered dual-port SPE device with an internal power decoupler <NUM>, and the drop cable 50C can be a four-wire cable including a first pair of SPE cables for uplink SPE to the trunk <NUM> and a second pair of SPE cables for powered downlink SPE to the trunk <NUM>.

As shown in <FIG>, internally, the power cable pair <NUM> can extend through the powered passive tap 46E between the first and second ports <NUM>, <NUM>, with connections branching off to an internal power coupler <NUM>. The SPE cable pair <NUM> can connect from the first port <NUM> to the third port <NUM>, e.g., to connect to the uplink SPE pair of the drop cable 50C. The SPE cable pair <NUM> can further connect from the third port <NUM> to the second port <NUM>, e.g., to connect to the powered downlink SPE pair of the drop cable 50C, and the power decoupler <NUM> within the powered SPE device 30C/32C and the power coupler <NUM> within the passive tap 46E can also internally connect to this powered downlink SPE line. As such, the passive tap 46E can couple power from the power cable pair <NUM> to the downlink SPE pair, and the powered SPE device 30C/32C decouples the power from the SPE pair. For example, the power coupler <NUM> can isolate common mode noise from the power cable pair <NUM> and isolate an SPE signal from the SPE cable pair <NUM>. Thus, the power decoupler <NUM> and power coupler <NUM> only need to pass current for one dedicated device 30C/32C, which enables the use of small, low-cost coupler circuitry. Additionally, as shown in <FIG>, the third port <NUM> can include four pins to interface with the four-wire drop cable 50C (e.g., two pins for uplink SPE connections and two pins for power and downlink SPE connections). Accordingly, two adjacent powered SPE devices 30C/32C can communicate over the SPE cable pair <NUM>, via the uplink and downlink SPE connections, and also receive power from the power cable pair <NUM> via the downlink SPE connection.

Additionally, though not shown in <FIG> and <FIG>, in some embodiments, the linear SPE network <NUM> may also include one or more power taps 46D configured to connect to an external power supply, such as an on-machine power supply <NUM> (as shown in <FIG>). For example, a power tap 46D can provide power when a first power supply cannot meet power requirements of the network <NUM>. <FIG> illustrates example power taps 46D-<NUM>, 46D-<NUM>, 46D-<NUM>, <NUM>-<NUM> according to some embodiments. Each power tap 46D-<NUM>, 46D-<NUM>, 46D-<NUM>, 46D-<NUM> can include a first port (e.g., a first trunk port) <NUM>, a second port (e.g., a second trunk port) <NUM>, and a third port (e.g., a power port) <NUM>. The first port <NUM> can connect to the SPE cable pair <NUM> of the trunk cables <NUM>, the second port <NUM> can connect to the power cable pair <NUM> and the SPE cable pair <NUM> of the trunk cables <NUM>, and the third port <NUM> can connect to a drop cable <NUM> configured to connect to a power supply <NUM>.

As shown in <FIG>, internally, an SPE cable pair <NUM> can connect from the first port <NUM> to the second port <NUM>, e.g., via a direct connection (as in power tap 46D-<NUM>), through an SPE switch <NUM> (as in power tap 46D-<NUM>), or through a fourth port <NUM> and connected device 30B/32B, 30C/32C (as in power taps 46D-<NUM>, 46D-<NUM>, respectively). That is, the fourth port <NUM> of power tap 46D-<NUM> can be similar to the third port <NUM> of the passive tap 46C and the fourth port <NUM> of power tap 46D-<NUM> can be similar to the third port <NUM> of the powered passive tap 46E, as shown in <FIG> and described above. Furthermore, the third port <NUM> can connect to a power pair (e.g., <NUM> volts and ground) from a connected power source <NUM>, and further connect the power pair to the second port <NUM> to be connected to the power cable pair <NUM> of a trunk cable <NUM> (as in power tap 46D-<NUM>), to the second port <NUM> and an SPE switch <NUM> (as in power tap 46D-<NUM>), to the second port <NUM> and the fourth port <NUM> (as in power tap 46D-<NUM>), or to the second port <NUM> and a power coupler <NUM> (as in power tap 46D-<NUM>).

Additionally, the power tap 46D can support a separated power zone, as shown in the example power taps <NUM>-<NUM> and 46D-<NUM>, or a continuous power zone via a diode on the power line, as shown in the example power taps 46D-<NUM> and 46D-<NUM>. Generally, a separated power zone means that the power pair from the connected power source <NUM> is only connected to a downlink power cable pair <NUM> of a trunk cable <NUM> (and additional connections discussed above specific to the corresponding power tap 46D-<NUM>, 46D-<NUM>, 46D-<NUM>). As a result, the power tap 46D only powers devices connected to its downlink port <NUM> (e.g., devices within its power "zone"). In this manner, the linear SPE network <NUM> can include separate power zones, each powered by different power sources. On the other hand, a continuous power zone means that the power pair from the connected power source <NUM> is connected to both the downlink power cable pair <NUM> of a trunk cable <NUM> as well as the uplink power cable pair <NUM> of a trunk cable <NUM>. In this manner, power taps 46D supporting a continuous power zone can provide power to both uplink and downlink devices. Thus, the linear SPE network <NUM> includes one continuous power zone, rather than separate power zones, as described above. For example, if an uplink device has no power source, the power tap 46D can provide power to the uplink device. If the uplink device has another power source (i.e., an uplink power source) with a higher voltage than that of the power source <NUM> connected to the power tap 46D, the diode within the power tap 46D helps isolate the power supply of the power tap 46D so that downlink devices can still be powered by the uplink power source. It should be noted that any of the power taps 46D-<NUM>, 46D-<NUM>, 46D-<NUM>, 46D-<NUM> can support a separated or continuous power zone via the deletion or addition of the diode and additional power pair connection to the uplink port <NUM>.

Finally, referring back to the linear SPE networks <NUM> of <FIG> and <FIG>, to terminate the linear SPE network <NUM>, the terminator 52A can be connected to the second port <NUM>/<NUM>/<NUM> of the tap <NUM> of the last device <NUM>/<NUM>. While a passive tap 46C is illustrated in <FIG> and <FIG> as the last tap <NUM> on the network <NUM>, in some applications, the last tap <NUM> may instead be an SPE tap 46A/B or a powered passive tap 46E. Alternatively, in some embodiments, the terminator 52A may be configured to be connected to a trunk cable <NUM> that extends from the second port <NUM>/<NUM>/<NUM> of the tap <NUM> of the last device <NUM>/<NUM>. As a result, if a further device <NUM>/<NUM> is to be added to the industrial automation system <NUM>, a new tap <NUM> can replace the terminator 52A along the trunk cable <NUM>, and the terminator 52A can be coupled to the second port <NUM>/<NUM>/<NUM> of the new tap <NUM>.

Referring now to a ring network structure of the SPE system <NUM>, <FIG> is a schematic view of the SPE system <NUM> of <FIG> arranged as ring SPE network <NUM>, according to some embodiments. As noted above, the ring SPE network <NUM> can be similar to the linear SPE network <NUM> of <FIG> and <FIG> and can include a linking device <NUM> connected to SPE devices 30B/32B via passive taps 46C and to legacy devices 30A/32A via SPE taps 46A/B. Furthermore, a splicer 52B can be placed after the last device <NUM>/<NUM>, e.g., rather than the terminator 52A of the linear SPE network <NUM>, in order to create the ring network structure.

More specifically, as shown in <FIG>, the linking device <NUM> can be a dual-port SPE linking device <NUM>, thus having two SPE ports <NUM>, and a ring management protocol. Furthermore, the trunk cable <NUM> can be a hybrid six-wire cable including a power cable pair (e.g., power and ground cables) and two SPE pairs. That is, the trunk cable <NUM> can include a power cable pair <NUM> (such as a <NUM>-volt line and a ground line), which may connect to an in-cabinet power supply <NUM>, as shown in <FIG>, to provide power transmission across the network <NUM>. The trunk cable <NUM> can further include two SPE cable pairs, e.g., a first, or linear, SPE cable pair <NUM>, denoted as D1+ and D1-, and a second, or loopback, SPE cable pair <NUM>, denoted as D2+ and D2-, which connect to the two SPE ports <NUM>, respectively, of the linking device <NUM>. For example, the power cable pair <NUM> may carry Direct Current (DC) power, while the SPE cable pairs <NUM>, <NUM> may transmit communication signals (e.g., via EtherNet/IP).

Furthermore, as shown in <FIG>, the taps <NUM> can include similar port connections as in the linear SPE network <NUM> described above. For example, the third port <NUM>, <NUM> of each tap 46C, 46A/B (as well as the third port <NUM> of a powered passive tap 46E, not shown) can be the same as described above with respect to <FIG> and <FIG> (e.g., have the same pin connections). The first ports <NUM>, <NUM> and second ports <NUM>, <NUM> of each tap 46C, 46A/B (and first and second ports <NUM>, <NUM> of a powered passive tap 46E, not shown) can connect the power cable pairs <NUM> as well as both SPE cable pairs <NUM>, <NUM> of the trunk cables <NUM>. More specifically, the first ports <NUM>, <NUM>, <NUM> and the second ports <NUM>, <NUM>, <NUM> of each tap 46C, 46A/B, 46E (e.g., the trunk ports) can connect the power cable pairs <NUM> and the first SPE cable pairs <NUM> of the trunk cables <NUM> to provide power transmission to and data communication with the respective sensor <NUM>/<NUM> through the third ports <NUM>, <NUM>, <NUM> (e.g., the drop ports), as described above with respect to <FIG>. The first ports <NUM>, <NUM>, <NUM> and the second ports <NUM>, <NUM>, <NUM> of each tap 46C, 46A/B, 46E can further connect the second SPE cable pair <NUM> of the trunk cables <NUM> so that the second SPE cable pair <NUM> can pass through the tap <NUM> between the first ports <NUM>, <NUM>, <NUM> and the second ports <NUM>, <NUM>, <NUM>. Therefore, the first ports <NUM>, <NUM>, <NUM> and the second port <NUM>, <NUM>, <NUM> within a ring SPE network <NUM> can each include six pins (e.g., two pins for power bus connections, two pins for linear SPE connections, and two pins for loopback SPE connections). Finally, as shown in <FIG>, the splicer 52B can be connected to the second port <NUM>/<NUM>/<NUM> of the tap <NUM> of the last device <NUM>/<NUM> and can connect the two pairs of SPE lines <NUM>, <NUM>, thus forming a ring where the second SPE pair <NUM> loops back to the linking device <NUM>.

In some embodiments, a splicer 52B can also be used as a placeholder on a drop line <NUM> within the linear or ring SPE network <NUM>, <NUM>. More specifically, the splicer 52B can be coupled to a third port <NUM>/<NUM>/<NUM> of a tap <NUM>, thus acting as a pass-through for the SPE cable pair <NUM> and reserving a space for a sensor <NUM>/<NUM> to be connected to the tap <NUM> at a later time. In some embodiments, the splicer 52B can include capacitors to isolate the power (e.g., the DC voltage) on the powered SPE pair (e.g., the downlink SPE pair) of a powered passive tap 46E. Additionally, in some embodiments, though not shown in <FIG>, <FIG>, and <FIG>, one or more of the sensors <NUM>/<NUM> may be replaced with other devices (e.g., legacy or smart devices), such as actuators. Furthermore, while the description herein refers to "sensors" <NUM>/<NUM>, it should be noted that this term may comprise sensors, switches, any of the specific examples provided for safety and standard sensors described above, or safety and/or standard sensor examples not specifically described herein.

It should be noted that, in some embodiments, a linear SPE network <NUM> can be converted to a ring SPE network <NUM> and vice versa. For example, <FIG> is another schematic view of a ring SPE network <NUM> according to some embodiments. The ring SPE network <NUM> of <FIG> can be similar to the linear SPE network <NUM> of <FIG> and <FIG>, including the hybrid four-wire trunk cable <NUM> coupled to the first SPE port <NUM> of the linking device <NUM>. However, a separate SPE pair cable <NUM> can be routed from the last tap <NUM> back to the second SPE port <NUM> of a dual-port linking device <NUM>, forming the ring SPE network <NUM>. Thus, a dedicated end cap 52C may be positioned at the second port <NUM>/<NUM>/<NUM> of the last tap <NUM> to terminate the power cable pair <NUM> while providing a pass-through for the SPE cable pair <NUM> to connect to the additional SPE cable <NUM>.

As another example, <FIG> is yet another schematic view of a ring SPE network <NUM> according to some embodiments. The ring SPE network <NUM> of <FIG> can be similar to the ring network of <FIG>, including the hybrid four-wire trunk cable <NUM> coupled to the first SPE port <NUM> of the linking device <NUM>. Furthermore, a separate four-wire cable <NUM> can be routed from the last tap <NUM> back to the dual-port linking device <NUM>. The four-wire cable <NUM> can include an SPE cable pair that connects SPE cable pair <NUM> and to the second SPE port <NUM> of the dual-port linking device <NUM>, forming the ring SPE network <NUM>, as well as a power cable pair that connects to the power cable pair <NUM>. The power cable pair of the four-wire cable <NUM> can be connected back to the in-cabinet power supply <NUM>, or a separate power supply, such an on-machine power supply, in order to provide a power redundancy for the network <NUM>. Thus, the four-wire cable <NUM> can provide both power and SPE network redundancy to the SPE system <NUM>. Additionally, a dedicated end cap 52D may be positioned at the second port <NUM>/<NUM>/<NUM> of the last tap <NUM> to provide a pass-through for the SPE cable pair <NUM> and the power cable pair <NUM> to connect to the additional cable <NUM>.

As yet another example, <FIG> is yet another schematic view of a linear SPE network <NUM> according to some embodiments. The linear SPE network <NUM> of <FIG> can be similar to the ring SPE network <NUM> of <FIG>, including the hybrid six-wire trunk cable <NUM>. However, the taps <NUM> can be connected to a single-port linking device <NUM> and a dedicated terminator 52E can be coupled to the last tap <NUM> (e.g., rather than a splicer 52B). In some embodiments, the terminator 52E and the terminator 52A may be the same or different components. Furthermore, in some embodiments, an end cap (not shown) may cover the second SPE cable pair <NUM> of the leading trunk cable <NUM> prior to the first tap <NUM> along the network <NUM>.

As described above, the SPE system <NUM> can provide a trunk-drop infrastructure via taps <NUM> that comprise two trunk ports and a drop port. In some embodiments, as shown in <FIG>, <FIG>, the SPE system <NUM> can include multi-drop taps 46F, <NUM>, <NUM>, 46I respectively, that comprise two trunk ports and two or more drop ports. More specifically, <FIG> is a schematic view of a multi-drop passive tap 46F, according to some embodiments, for use with the SPE system <NUM>. <FIG> is a schematic view of a multi-drop SPE tap <NUM>, according to some embodiments, for use with the SPE system <NUM>. <FIG> is a schematic view of a multi-drop powered passive tap <NUM>, according to some embodiments, for use with the SPE system <NUM>. <FIG> is a schematic view of a mixed multi-drop tap 46I, according to some embodiments, for use with the SPE system <NUM>.

With reference to <FIG>, the multi-drop passive tap 46F may act similar to the passive tap 46C of <FIG>, but is capable of being coupled to multiple SPE devices 30B/32B. Accordingly, like the passive tap 46C of <FIG>, the multi-drop passive tap 46F can include a first trunk port <NUM>, a second trunk port <NUM>, and multiple third drop ports <NUM> (e.g., <NUM>-<NUM>. More specifically, the first and second ports <NUM>, <NUM> can each connect to a power cable pair <NUM>, a first SPE cable pair <NUM>, and a second SPE cable pair <NUM> of trunk cables <NUM>. Each third port <NUM> can connect to a drop cable <NUM> (e.g., drop cable 50B, not shown in <FIG>) configured to connect to an SPE device 30B/32B. For example, internally, the power cable pair <NUM> can extend through the multi-drop passive tap 46F between the first and second ports <NUM>, <NUM>, with connections branching off to the third ports <NUM>-<NUM>. <NUM>-n, e.g., to connect the power cable pair <NUM> to the respective drop cables 50B. The first SPE cable pair <NUM> can connect from the first port <NUM> to the third port <NUM>-<NUM>, and back from the third port <NUM>-<NUM> to the third port <NUM>-n, and back from the third port <NUM>-n to the second port <NUM>, thus coupling each SPE device 30B/32B connected to a respective third port <NUM> to the IP subnet trunkline <NUM>. Additionally, the second SPE cable pair <NUM> can pass through the tap 46F between the first port <NUM> and the second port <NUM> to create a ring network infrastructure (e.g., when coupled between a linking device <NUM> and a splicer 52B). Accordingly, the multi-drop passive tap 46F can act as a pass-through for power and data communication lines to multiple SPE devices 30B/32B. Furthermore, the multi-drop passive tap 46F can provide linear-style connections (e.g., multiple devices 30B/32B arranged in a linear formation off of the tap 46F), or star- or tree-style connections (e.g., multiple devices 30B/32B arranged in a star or tree-like formation off of the tap 46F).

With reference to <FIG>, the multi-drop SPE tap <NUM> may act similar to the SPE tap 46A/B of <FIG>, but is capable of being coupled to multiple legacy devices 30A/32A. Accordingly, like the SPE tap 46A/B of <FIG>, the multi-drop SPE tap <NUM> can include a first trunk port <NUM>, a second trunk port <NUM>, and multiple third drop ports <NUM> (e.g., <NUM>-<NUM>. More specifically, the first and second ports <NUM>, <NUM> can each connect to a power cable pair <NUM>, a first SPE cable pair <NUM>, and a second SPE cable pair <NUM> of trunk cables <NUM>. Each third port <NUM> can connect to a drop cable <NUM> (e.g., drop cable 50A, not shown in <FIG>) configured to connect to a legacy device 30A/32A. For example, internally, the power cable pair <NUM> can extend through the multi-drop SPE tap <NUM> between the first and second ports <NUM>, <NUM>, with connections branching off to the third ports <NUM>-<NUM>. <NUM>-n, e.g., to connect the power cable pair <NUM> to the respective drop cables 50A. The first SPE cable pair <NUM> can connect from the first port <NUM> to the second port <NUM> via an internal dual-port SPE switch <NUM>. Additionally, the second SPE cable pair <NUM> can pass through the tap <NUM> between the first port <NUM> and the second port <NUM> to create a ring network infrastructure (e.g., when coupled between a linking device <NUM> and a splicer 52B). Accordingly, the multi-drop SPE tap <NUM> can include a dedicated SPE switch <NUM> (or multiple SPE switches <NUM>, in some embodiments) to integrate multiple legacy devices 30A/32A into the SPE system <NUM> through the trunk-drop infrastructure. Furthermore, the multi-drop SPE tap <NUM> can provide linear-style connections (e.g., multiple devices 30A/32A arranged in a linear formation off of the tap <NUM>), or star- or tree-style connections (e.g., multiple devices 30A/32A arranged in a star or tree-like formation off of the tap <NUM>).

With reference to <FIG>, the multi-drop powered passive tap <NUM> may act similar to the powered passive tap 46E of <FIG>, but is capable of being coupled to multiple powered SPE devices 30C/32C. Accordingly, like the powered passive tap 46E of <FIG>, the multi-drop powered passive tap <NUM> can include a first trunk port <NUM>, a second trunk port <NUM>, and multiple third drop ports <NUM> (e.g., <NUM>-<NUM>. More specifically, the first and second ports <NUM>, <NUM> can each connect to a power cable pair <NUM> and an SPE cable pair <NUM> of trunk cables <NUM>. Each third port <NUM> can connect to a drop cable <NUM> (e.g., drop cable 50C, not shown in <FIG>) configured to connect to a powered SPE device 30C/32C. For example, internally, the power cable pair <NUM> can extend through the multi-drop powered passive tap <NUM> between the first and second ports <NUM>, <NUM>, with connections branching off to power couplers <NUM>, e.g., to connect the power cable pair <NUM> to SPE downlink pairs of the third ports <NUM>-<NUM>. <NUM>-n and respective drop cables 50C. The SPE cable pair <NUM> can connect from the first port <NUM> to the third port <NUM>-<NUM>, and back from the third port <NUM>-<NUM> to the third port <NUM>-n, and back from the third port <NUM>-n to the second port <NUM>, thus coupling each powered SPE device 30C/32C connected to a respective third port <NUM> to the IP subnet trunkline <NUM>. Accordingly, the multi-drop powered passive tap <NUM> can act as a pass-through for power and data communication lines to multiple powered SPE devices 30C/32C. Furthermore, the multi-drop powered passive tap <NUM> can provide linear-style connections (e.g., multiple devices 30C/32C arranged in a linear formation off of the tap <NUM>), or star- or tree-style connections (e.g., multiple devices 30C/32C arranged in a star or tree-like formation off of the tap <NUM>).

With reference to <FIG>, the mixed multi-drop tap <NUM> incorporate connections similar to different kinds of taps <NUM> described above, such as the passive tap 46C and the powered passive tap 46E of <FIG> so that it is capable of being coupled to multiple different types of SPE devices 30B/32B, 30C/32C. Accordingly, the mixed multi-drop tap 46I can include a first trunk port <NUM>, a second trunk port <NUM>, and multiple third drop ports <NUM> (e.g., <NUM>-<NUM>. Accordingly, the first and second ports <NUM>, <NUM> can each connect to a power cable pair <NUM> and an SPE cable pair <NUM> of trunk cables <NUM>. Each third port <NUM> can connect to a drop cable <NUM> (e.g., drop cable 50B or drop cable 50C, not shown in <FIG>) configured to connect to an SPE device 30B/32B or powered SPE device 30C/32C. For example, internally, the power cable pair <NUM> can extend through the mixed multi-drop tap 46I between the first and second ports <NUM>, <NUM>, with connections branching off to power couplers <NUM>, e.g., to connect the power cable pair <NUM> to SPE downlink pairs of the third ports <NUM>-<NUM>. <NUM>-n and respective drop cables 50C, or with connections branching off to the third ports <NUM>-<NUM>. <NUM>-n, e.g., to connect the power cable pair <NUM> to the respective drop cables 50B. The SPE cable pair <NUM> can connect from the first port <NUM> to the third port <NUM>-<NUM>, and back from the third port <NUM>-<NUM> to the third port <NUM>-n, and back from the third port <NUM>-n to the second port <NUM>, thus coupling each SPE device 30B/32B, 30C/32C connected to a respective third port <NUM> to the IP subnet trunkline <NUM>. Accordingly, the mixed multi-drop tap <NUM> can act as a pass-through for power and data communication lines to multiple SPE device 30B/32B and/or powered SPE devices 30C/32C. Furthermore, the mixed multi-drop tap 46I can provide linear-style connections (e.g., multiple devices 30B/32B, 30C/32C arranged in a linear formation off of the tap 46I), or star- or tree-style connections (e.g., multiple devices 30B/32B, 30C/32C arranged in a star or tree-like formation off of the tap <NUM>). It should also be noted that, while the multi-drop passive tap 46F and the multi-drop SPE tap <NUM> are shown and described with connections for a ring SPE network <NUM>, and the multi-drop powered passive tap <NUM> and the mixed multi-drop tap <NUM> are shown and described with connections for a linear SPE network <NUM>, it is within the scope of this disclosure to include multi-drop tap 46F, <NUM>, <NUM>, <NUM> having respective connections for a linear SPE network <NUM> or a ring SPE network <NUM>.

Additionally, embodiments provide a method of forming an SPE network <NUM>/<NUM> within an industrial automation system <NUM>. The method includes forming the IP subnet trunkline <NUM> using the trunk cables <NUM>, connecting a first device <NUM>/<NUM> to the IP subnet trunkline <NUM> by connecting the trunk ports of a respective tap <NUM> to the trunk cables <NUM>, connecting a drop port of the tap <NUM> to a drop cable <NUM>, and connecting the first device <NUM>/<NUM> to the drop cable <NUM>. The method also includes connecting subsequent devices <NUM>/<NUM> to the IP subnet trunkline <NUM> in the same manner ( by connecting the trunk ports of a respective tap <NUM> to the trunk cables <NUM>, connecting a drop port of the tap <NUM> to a drop cable <NUM>, and connecting the respective device <NUM>/<NUM> to the drop cable <NUM>. The method further includes connecting a final, last-hop device <NUM>/<NUM> to the IP subnet trunkline <NUM> by connecting one of the trunk ports of a final tap <NUM> to the trunk cable <NUM>, connecting a drop port of the final tap <NUM> to a drop cable <NUM>, and connecting the last-hop device <NUM>/<NUM> to the drop cable <NUM>. The method also includes connecting an end cap <NUM> to the other trunk port of the final tap <NUM>, and connecting one of the trunk cables <NUM> to the linking device <NUM> (e.g., that is connected to a wired network of the industrial automation system <NUM>).

Additionally, by using a terminator 52A as the end cap <NUM>, a linear SPE network can be formed. Alternatively, by using a splicer 52B as the end cap <NUM>, a ring SPE network can be formed. Also, a placeholder can be added to the IP subnet trunkline <NUM> by connecting the trunk ports of a respective tap <NUM> to the trunk cables <NUM> and connecting a drop port of the tap <NUM> to a splicer 52B.

In light of the above, embodiments provide an industrial SPE network including a linking device, sensor and/or actuator devices, and a trunk-drop network infrastructure connecting the sensor/actuator devices, including passive or SPE taps (such as three-port or multiport taps), trunk cables, drop cables, and an end cap. The trunk-drop infrastructure can form a linear SPE network with bus power using a two-pair trunk cable (e.g., a first cable pair for linear SPE and a second cable pair as a power bus) and a terminator. The trunk-drop infrastructure can form a ring-SPE network with bus power using a two-pair trunk cable (e.g., a first cable pair for linear SPE and a second cable pair as a power bus) and a separate single-pair cable (e.g., a loopback SPE pair). The trunk-drop infrastructure can form a ring-SPE network with bus power using a three-pair trunk cable (e.g., a first cable pair for forward linear SPE, a second cable pair as a power bus, and a third cable pair for loop-back SPE), and a splicer creating a ring by connecting the forward linear SPE pair and the loop-back SPE pair. The trunk-drop infrastructure can form a linear SPE network with bus power using a three-pair trunk cable (e.g., a first cable pair for forward linear SPE, a second cable pair as a power bus, and a third cable pair for loop-back SPE), where the third cable pair remains open.

Generally, the on-machine industrial SPE systems described herein provide a combination of an SPE network (with linear or ring arrangement) and a bus power network in a physical trunk-drop network infrastructure, which can simplify the power and communication infrastructure compared to prior systems and can enable location-based services. The SPE systems described herein can further provide CIP, IP, and SPE connectivity to the last-hop field-constrained devices, which can provide great user experiences and better system integration, and also can improve device data analytics capabilities, thus enabling a new series of innovation in industrial automation. The SPE systems described herein can also include safety and standard constrained devices, as well as legacy and new SPE devices, all on the same SPE network, which further simplifies network infrastructure, reduces the skill level of labor when building such systems, and can thus serve both Brownfield and Greenfield applications.

Claim 1:
An industrial Single Pair Ethernet, SPE, system to be installed within an industrial automation system, the industrial SPE system comprising:
a linking device (<NUM>);
a first device (30A, 30B, 32A, 32B) comprising one of a sensor and an actuator;
a second device (30A, 30B, 32A, 32B) comprising one of a sensor and an actuator;
a trunk-drop infrastructure (<NUM>) connecting the first device and the second device to the linking device, the trunk-drop infrastructure comprising:
a first tap (46A, 46B, 46C, 46C, 46D, 46E, 46F, <NUM>, <NUM>);
a first drop cable (<NUM>) connecting the first tap to the first device;
a second tap (46A, 46B, 46C, 46C, 46D, 46E, 46F, <NUM>, <NUM>);
a second drop cable (<NUM>) connecting the second tap to the second device;
a trunk cable (<NUM>) connected between the linking device, the first tap, and the second tap, the trunk cable including a first pair of cables (<NUM>) configured to transmit power and a second pair of cables (<NUM>) configured as single pair ethernet cables; and
an end cap (<NUM>) connected to the second tap,
wherein at least one of the first device, the second device, the first tap, and the second tap includes a dual-port SPE switch (<NUM>, <NUM>).