33 Ethernet: Links and Standard Selection
33.1 Overview
This first route covers link identity, standard selection, device fit, and the evidence behind a wired choice.
This is part 1 of 2. Continue with Ethernet: PoE and Operations for the second focused route.
33.2 Start With a Link You Can Inspect
33.2.1 Prove One Cable Path
The physical layer is the part of a network that carries signals through cable, fibre, or radio. A protocol is an agreed set of rules for an exchange. A gateway is a bridge between this network and another service.
Picture a clinic gateway connected to a switch in another room. The link light is on, yet alarm data arrives in bursts. The cause might be a damaged pair, a speed mismatch, a weak power budget, a loop, or congestion beyond this cable. One green light cannot choose among them.
Trace the path from device socket to switch port. Record cable type and length, negotiated speed and duplex, delivered power, error counters, and the next network hop. Move the cable, interrupt power, and add the expected load. Check which signs change and whether the operator can locate the fault.
Make the test easy to repeat. Label both ends. Save the port name. Save the speed. Save the error count before and after load. Swap one known-good lead. Move one known-good device. Each step rules out one part of the path.
This proof covers the named link and its local service boundary. It does not prove the application, remote service, or user action. The deeper sections explain Ethernet frames, switching, power delivery, industrial choices, and the measurements needed for longer or harsher links.
Ethernet gives IoT systems a physical path with visible link state, negotiated speed, switch ports, and often power delivery. That makes it a strong choice when reliability, serviceability, and predictable capacity matter more than cable-free installation.
Use the chapter as a deployment checklist. The story is not just “plug in a cable”; it is proving cable length, PoE budget, duplex and speed negotiation, switch path, and what happens when the device must share the network.
Packet Pete
“A cable is a promise with a length limit — show me the run, the port, and the record that proves it holds.”
Here Pete follows the physical link itself: the conductor, the record it needs, and the fault it can point back to.
By the end of this section, you will be able to:
- Explain the role of Ethernet (IEEE 802.3) in IoT deployments and justify when it is preferable to wireless alternatives
- Compare and differentiate Ethernet standards (10BASE-T, 100BASE-T, 1000BASE-T) by speed, application, and physical layer characteristics
- Select appropriate Ethernet standards for given IoT use cases based on bandwidth and latency requirements
- Evaluate trade-offs between wired Ethernet and wireless connectivity for specific IoT deployment scenarios
- Calculate PoE power budgets for IoT installations using IEEE 802.3af, 802.3at, and 802.3bt standards
Use the chapter as an Ethernet release checklist:
- First identify what 10BASE-T, 100BASE-T, 1000BASE-T, cable category, and auto-negotiation prove about the link.
- Then decide when wired service beats Wi-Fi for cameras, robots, and other stationary IoT devices.
- Next calculate PoE budget, cable length, and switch capacity before the device is installed.
- Finally turn link speed, duplex, PoE class, VLAN, route, and error counters into a deployment record.
Checkpoints recap the design decisions; calculators, quizzes, and the reliability contract provide the evidence trail.
33.4 Prerequisites
Before diving into this chapter, you should be familiar with:
- Network Access and Physical Layer Overview: Understanding the role of physical and network access layers in the OSI model
- Networking Basics: Understanding fundamental networking concepts including protocol layers and data transmission principles
Ethernet is the most common wired networking technology. Think of Ethernet cables as highways for data - they’re fast, reliable, and can carry lots of traffic without interruption.
When you plug your computer into a router with a cable, that’s Ethernet! The cable has 8 wires inside arranged in twisted pairs that carry electrical signals representing your data.
| Term | Simple Explanation |
|---|---|
| Ethernet | Wired connection using twisted-pair cables (like RJ45 “phone jack” connectors) |
| 100BASE-T | Fast Ethernet - 100 Mbps (megabits per second) |
| 1000BASE-T | Gigabit Ethernet - 1000 Mbps (10x faster than 100BASE-T) |
| PoE | Power over Ethernet - delivers both data AND electricity through one cable |
| Cat5e/Cat6 | Cable quality ratings - higher numbers = better performance |
“Why would anyone use wires when wireless is so convenient?” asked Temperature Terry. the microcontroller had a quick answer. “Reliability! Ethernet never drops out because of interference, it delivers data at consistent speed, and it can even provide power through the same cable.”
“Power over Ethernet is amazing,” said the LED. “A single Ethernet cable plugs into a security camera and delivers both the network connection AND up to 90 watts of power. No separate power cable needed! That is why PoE is so popular for IP cameras, Wi-Fi access points, and building sensors.”
“Ethernet also has zero radio interference,” added the battery. “In a factory with lots of motors, welders, and heavy machinery that mess up wireless signals, a wired Ethernet connection keeps working perfectly. For critical infrastructure like factory control systems and building automation gateways, wired is the way to go.”
“The trade-off is obvious though,” said Sammy. “You cannot put Ethernet cables in a farmer’s field or on a moving robot. Ethernet is perfect for STATIONARY devices where reliability matters more than mobility. Match the connection type to the job!”
33.5 Powerline Networking as a Retrofit Link
Powerline networking carries data over the building’s existing mains wiring. A typical retrofit uses one adapter beside the router or switch and a second beside the endpoint; short Ethernet leads join each adapter to the equipment, while the electrical circuit becomes the link between them. This can cross a concrete floor or other radio-unfriendly boundary without pulling a new data cable, so it is worth testing when direct Ethernet is impractical and Wi-Fi is unreliable.
The convenience does not make the wiring a clean network medium. Performance changes with circuit topology, distance, consumer appliances, switch-mode power supplies, surge protectors, and whether the two outlets cross distribution-board boundaries. Several adapters also share the same medium, so added nodes and electrical noise can reduce useful throughput or make a previously stable path intermittent. Powerline equipment can emit radio-frequency energy through wiring that was never designed as a shielded data cable; use approved equipment for the jurisdiction and investigate interference reports rather than assuming the signal remains inside the walls.
Treat a HomePlug-class link as measured retrofit infrastructure, not as invisible Ethernet. Before accepting it, record the outlet pair, electrical phase or circuit boundary, adapter model and security pairing, useful throughput and loss during representative appliance activity, behavior after a power interruption, and a fallback path. For example, a gateway in a utility room may reach an upstairs controller reliably through paired adapters even though reinforced concrete defeats Wi-Fi. The acceptance test should then repeat while high-load appliances operate and after each adapter has restarted. If that evidence is unstable, install a data cable, move the gateway, or choose another radio path.
33.6 IEEE 802.3 Ethernet for IoT
Start with the physical promise: Ethernet can be inspected. The first pass names the standards, speed choices, cable limit, and negotiation evidence you need before comparing it with wireless options.
IoT devices may be connected via a wired connection. For permanent installations, Ethernet is commonly used. The data rate using Ethernet can range from 10 Mbps to more than 1 Gbps (1000 Mbps).
To test ieee 802.3 ethernet for iot, open the diagram in Figure 33.1. Ethernet Evolution and PoE Capability supplies one named condition; 10BASE-T supplies the necessary comparison for evolution of ethernet standards showing increased speeds and power over ethernet capabilities.
Within the diagram, Ethernet Evolution and PoE Capability opens Figure 33.1; 10BASE-T provides the counterpoint, and 10 Mb/s closes the inspection. This reading constrains evolution of ethernet standards showing increased speeds and power over ethernet capabilities and supplies the visual evidence for ieee 802.3 ethernet for iot.
33.6.1 Common Ethernet Standards
10BASE-T: 10 Mbps, found on small microcontrollers and legacy industrial equipment
100BASE-T: 100 Mbps (Fast Ethernet), common on higher-powered microcontrollers or single-board computers like Raspberry Pi
1000BASE-T: 1000 Mbps (Gigabit Ethernet), used for high-bandwidth applications like IP cameras and industrial gateways
Checkpoint: Link Identity
You now know:
- 10BASE-T, 100BASE-T, and 1000BASE-T describe 10 Mbps, 100 Mbps, and 1000 Mbps Ethernet links.
- Cat5e supports Gigabit Ethernet up to 100 m, while Cat6 improves crosstalk performance.
- Auto-negotiation can only select a speed supported by both ends of the link.
33.7 Which Speed Will The Link Negotiate?
- IP Cameras: 4K video transmission. Transmitting 4K quality video over Wi-Fi may create problems due to data speed constraints
- VoIP Devices: Voice over IP communications requiring consistent quality
- Set-top Boxes: Video/audio streaming and storage
- Game Applications and Systems: Low-latency gaming
- Static Industrial Equipment: Manufacturing machinery, process control
- High-Security Sensors: Transmitting via wireless is viewed as high-risk; wired preferred
- High-Reliability Control: Robotics, medical applications requiring deterministic communication
33.7.1 Advantages of Ethernet for IoT
| Advantage | Description |
|---|---|
| High bandwidth | 10 Mbps to 10+ Gbps - supports any IoT data rate |
| High reliability | No radio interference, consistent performance |
| Low latency | Sub-millisecond latency for real-time control |
| Deterministic | Predictable timing (critical for industrial) |
| PoE capability | Single cable for data AND power |
| Security | Physical access required - no wireless eavesdropping |
Ethernet’s maximum cable length is set by signal attenuation physics. Cat6 cable attenuation at 100 MHz is approximately 20 dB per 100 meters (per TIA-568-C standard).
For Gigabit Ethernet (1000BASE-T), the 100 m limit is derived from the signal-to-noise ratio needed for reliable PAM-5 decoding across four wire pairs. The IEEE 802.3 standard specifies an end-to-end channel loss budget:
At 100 m, the received signal is close to the noise floor, leaving minimal margin. Beyond 100 m, bit error rates rise sharply and automatic repeat request (ARQ) overhead degrades throughput. A repeater or switch must be placed every 100 m to regenerate the signal.
For 10 Gbps (10GBASE-T), the more demanding modulation scheme (PAM-16) requires better SNR, which is why it is limited to 55 m on Cat6 cable and requires Cat6A (10GBASE-T is specified for 100 m only on Cat6A or Cat7).
33.7.2 Cable Construction and Deployment Evidence
Before applying the specification, inspect the real ethernet cable (cat5e/cat6, rj45 connector) below: its package, terminals, scale, and installation context are part of the engineering evidence.
Carry those visible constraints into the surrounding analysis; the abstract symbol or capability name does not capture mounting, wiring, protection, or service access.
Ethernet cabling is not only a connector choice. The conductor, shield, insulation, jacket rating, and route all change whether the link keeps its margin after installation. Copper is the normal data conductor because it combines low resistance, cost, and flexibility. Aluminium, steel, nickel, tin, and silver appear in specialized cable or connector contexts, but they usually represent a tradeoff: lower cost, corrosion resistance, solderability, strength, or high-frequency surface performance rather than a blanket improvement over copper.
Figure 33.2 makes cable construction and deployment evidence inspectable through A blue Ethernet patch cable and a clear RJ45 modular plug showing the eight conductors. Those diagram labels establish the scope of a terminated ethernet patch lead exposes the physical evidence a protocol name omits: eight conductors carried through an rj45 plug, a flexible.
Begin Figure 33.2 with A blue Ethernet patch cable, then distinguish a clear RJ45 modular plug showing the eight conductors and A terminated Ethernet patch lead exposes the physical. The diagram separates A blue Ethernet patch cable from a clear RJ45 modular plug showing the eight conductors within a terminated ethernet patch lead exposes the physical evidence a protocol name omits: eight conductors carried through an rj45 plug, a flexible. Keep both distinctions explicit in cable construction and deployment evidence.
At high frequency, current concentrates near the outside of a conductor. This skin effect is one reason cable construction, plating, and stranding matter more as data rates rise. Silver-plated copper can reduce high-frequency surface loss, tinned copper improves solderability and corrosion behavior, and nickel plating can survive harsher temperatures, but each choice must be justified against cost, bend radius, connector compatibility, and standards compliance.
For building Ethernet, the practical review is usually simpler: verify the cable category, pair twist, shield choice, and jacket rating. Twisted pairs reduce coupled noise because interference tends to affect both wires similarly, while the receiver reads the difference between them. Shielded cable can help near motors, drives, fluorescent ballasts, or radio equipment, but only when grounding and termination are planned; a badly bonded shield can become part of the noise problem. Plenum, riser, general-purpose, and low-smoke-zero-halogen jacket ratings are safety and code decisions, not performance labels. They say where a cable is allowed to run and what smoke or flame behavior is expected.
Long or harsh routes add another evidence layer. A data-center patch lead, an industrial tray cable, a marine cable, and an undersea fibre cable are all “wired links,” but their release evidence is different. Submarine systems care about water blocking, armour, repeater power, burial depth, repair access, and shore landing protection. The IoT lesson is to record the physical route beside the protocol: cable type, pathway, bend radius, shield bond, fire rating, moisture exposure, and acceptance test are part of the link contract.
33.7.2.1 Harsh-route layers and wildlife protection
The submarine-cable cross-section in the source names optical fibres alongside petroleum jelly, a copper or aluminium tube, polycarbonate, an aluminium water barrier, stranded steel wires, Mylar tape, and polyethylene. The list is useful as a construction-reading exercise: the signal carrier is only one part of a cable, while water exclusion, mechanical strength, and the outer environment demand additional materials around it. A deployment record should identify which installed layer provides each protection rather than calling the whole assembly simply “fibre.”
Animals create a different physical failure path. The source groups the exposure by installed location: rats and termites mainly affect underground cable, rodents and moths affect aerial cable, crows affect drop cable, and ants can invade closures and chew cable or fibre. It links rodent chewing to tooth maintenance, insects to plant-like material and egg-laying or burrowing behaviour, and birds to collecting twig-like material for nests.
Countermeasures in the source include a high-strength sheath, PVC-wrapped stainless steel, cable wrap, a stainless-steel mesh inside a PVC sheet, and closing gaps with silicone adhesive. It also names PVC infused with irritants such as capsaicin or the bitter compound denatonium benzoate. Treat those as candidate physical controls to evaluate for the exact route, not substitutes for inspection: record the damaged location, selected barrier, closure detail, and the retest that shows the cable and link remain intact.
Pete’s Delivery Slip
- Address: copper is the default conductor for a reason -- low resistance, cost, and flexibility.
- Route: twisted pairs reject coupled noise by reading the difference between two wires, not by shielding alone.
- Receipt: plenum, riser, and low-smoke jacket ratings are fire-code decisions, not performance labels -- record them beside the protocol.
33.7.3 Disadvantages of Ethernet for IoT
| Disadvantage | Description |
|---|---|
| Physical cabling | Requires cable runs to each device |
| Installation cost | Labor-intensive, especially retrofit |
| Limited mobility | Devices must be stationary |
| Not battery-powered | Requires mains or PoE infrastructure |
| Inflexible | Difficult to relocate devices |
Core Concept: PoE delivers DC power (15-90W) alongside data over standard Ethernet cables, eliminating separate power wiring for IoT devices like IP cameras, access points, and sensors.
Why It Matters: A single cable installation reduces deployment cost by 30-50% for devices that would otherwise need both Ethernet and power outlets. PoE switches also enable centralized power management and UPS backup for all connected devices.
Key Takeaway: Use PoE (802.3af, 15.4W) or PoE+ (802.3at, 30W) for cameras, access points, sensors, and thin clients. PoE++ (802.3bt Type 3: 60W, Type 4: 100W) supports higher-power devices like PTZ cameras and small displays. Always verify both the switch and the device support the same PoE standard before deployment.
Scenario: A warehouse needs 50 IP cameras for security. Each camera streams 4K video at 25 Mbps. The warehouse is 200m x 150m with metal shelving causing RF interference.
Given:
- 50 cameras, each producing 25 Mbps video stream
- Total bandwidth: 50 x 25 Mbps = 1,250 Mbps (1.25 Gbps)
- Distance from cameras to switches: 50-80 meters
- Environment: Metal shelving, forklifts, variable lighting
Analysis:
Option A: Wi-Fi 5 (802.11ac)
- Theoretical: 3.5 Gbps shared (8x8 MU-MIMO, 160 MHz)
- Practical: 1-2 Gbps shared across all devices
- 50 cameras competing for airtime
- Metal interference causes unpredictable dropouts
- Result: Insufficient - video stuttering, dropped frames
Option B: Gigabit Ethernet with PoE+
- Each camera gets dedicated 1 Gbps port
- 25 Mbps uses only 2.5% of available bandwidth
- No radio interference
- PoE+ provides up to 30W power per camera
- Result: Optimal - consistent 4K streaming
Cost Comparison (50 cameras):
| Item | Wi-Fi | Ethernet |
|---|---|---|
| Infrastructure | $3,000 (6 APs) | $8,000 (2x 24-port PoE switches) |
| Cabling | $500 (power drops) | $5,000 (Cat6 runs) |
| Power outlets | $2,500 (50 outlets) | $0 (PoE) |
| Total | $6,000 | $13,000 |
| Reliability | Variable | Excellent |
Result: Ethernet costs more upfront but provides guaranteed performance. For mission-critical surveillance, the additional $7,000 is justified by eliminating video loss during incidents.
Key Insight: The text states cameras are Ethernet examples because “Transmitting 4K quality video over Wi-Fi may create problems due to data speed constraints.” Ethernet’s deterministic performance is essential for security applications.
Checkpoint: Wired Fit
You now know:
- A 50-camera warehouse at 25 Mbps per camera needs 1,250 Mbps before management overhead.
- Ethernet gives each camera a dedicated 1 Gbps port; Wi-Fi shares airtime and can drop frames in metal-heavy spaces.
- Robot control with a 100 ms update interval and a less-than-10 ms latency target belongs on deterministic Ethernet+TSN, not a best-effort wireless link.
Scenario: A factory needs to connect 50 industrial robots across a 200m x 150m floor. Robots require telemetry every 100 ms with <10 ms latency and zero packet loss for safety.
Given:
- 50 robots with 100 ms update interval
- Latency requirement: <10 ms
- Packet loss: Zero tolerance (safety-critical)
- Data per update: 500 bytes
- Total bandwidth: 50 x (500 bytes x 8 / 0.1s) = 2 Mbps
Requirements Analysis:
| Requirement | Wi-Fi 6 | LoRaWAN | Zigbee | Ethernet+TSN |
|---|---|---|---|---|
| Latency | 3-200 ms | 2500 ms | 60 ms | 0.069 ms |
| Packet Loss | 1-5% | 5-10% | 5-10% | 0% |
| Deterministic | No | No | No | Yes |
| Bandwidth | 9.6 Gbps | 50 kbps | 250 kbps | 1 Gbps |
Analysis:
The text explicitly lists “Robotics, medical applications requiring deterministic communication” as Ethernet examples, citing advantages of “Low latency and jitter” and “Deterministic performance.”
- Wi-Fi: 3.7 ms typical but 50-200 ms worst-case spikes (non-deterministic). 1-5% packet loss unacceptable for robot safety.
- LoRaWAN: 2,500 ms latency is 250x too slow. Transmission time (1.45s) exceeds update interval (100 ms).
- Zigbee: 60 ms latency > 10 ms requirement. 250 kbps cannot support 50 robots reliably.
- Ethernet + TSN: 0.069 ms latency with zero jitter. Time-Sensitive Networking guarantees bounded latency.
Result: Gigabit Ethernet with TSN (Time-Sensitive Networking) is the only viable option. TSN extensions (IEEE 802.1Qbv) provide deterministic scheduling, ensuring robot control packets are never delayed.
Key Insight: For safety-critical industrial control, only wired Ethernet can guarantee the bounded latency and zero packet loss required. Wireless protocols are fundamentally non-deterministic due to shared medium access.
33.8 Knowledge Check
33.9 Continue to Part 2
Continue with Ethernet: PoE and Operations.