Intended UseΒΆ


Do not use the Ethernet-Mux for any other use cases than the ones listed below.

  • The Ethernet-Mux is intended to be used during the development of embedded devices with a 10-BaseT, 100-BaseT or 1000-BaseT Ethernet connection. The Ethernet-Mux uses transformers to galvanic isolate its input and outputs, restricting its use to Ethernet and Ethernet-like protocols.

  • The Ethernet-Mux does not provide a DC-connection between its Ethernet Ports. This means that it can not pass through power via PoE to a DUT.

  • The Ethernet-Mux is intended to switch a single Ethernet port between two Ethernet-ports. The switching is performed using a low-level analog switch, and therefore transparent to the connected devices.

  • The Ethernet-Mux can be used to simulate attaching and detaching of an Ethernet cable by leaving one of the upstream port unconnected.

  • The Ethernet-Mux can be utilized to multiplex an Ethernet link between two devices - for example a network switch with access to your TFTP- and NFS- development infrastructure and an auxiliary device.


The Ethernet-Mux is designed to be used with a maximum cable length of 10m on each RJ45-connector. The use of longer cables may result in unstable Ethernet links.

  • The Ethernet-Mux is controlled using a combined CAN-Bus and power connector.


Make sure the voltage on the power input stays within the safe 9V to 13V working range of the Ethernet-Mux.

  • The Ethernet-Mux is intended to be controlled by a CANopen-inspired protocol via the lxa-iobus-server. The server provides a web-based interface, as well as a REST-based API. The server allows controlling multiple IOBus devices on a bus.

  • If control via CAN is not an option, the Ethernet-Mux can be controlled using a GPIO-pin inside the housing. This usecase is only intended for well experienced users in an ESD-protected work environment.