33 Ethernet: Links and Standard Selection
More
Depth: Practitioner
Progress saves as you read. Mark sections complete as you go; your progress appears in the sidebar.
33.1 Overview
This section: Overview — This first route covers link identity, standard selection, device fit, and the evidence behind a wired choice.
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
This section: 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.
- 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
This section: 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-TX | Fast Ethernet over twisted pair - 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! Radio interference can’t knock a cable offline, so data arrives at a steady speed, and it can even carry power.”
“Power over Ethernet is amazing,” said the LED. “One cable can give up to 90 watts from the switch — a bit less reaches the camera — and carry data for cameras, Wi-Fi access points, and building sensors.”
“Ethernet also avoids radio interference,” added the battery. “In a factory full of motors and welders, a cable can keep the message moving when radio has trouble.”
“The trade-off is obvious though,” said Sammy. “It’s hard to run a cable across a farmer’s field or to a robot that moves around. Ethernet suits stationary devices. Match the connection type to the job!”
33.5 Powerline Networking as a Retrofit Link
This section: Powerline Networking as a Retrofit Link — Powerline networking carries data over the building’s existing mains wiring.
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
This section: IEEE 802.3 Ethernet for IoT — Start with the physical promise: Ethernet can be inspected.
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).
Read Figure 33.1 for the two things it separates: how fast a link runs, and what else the same cable can deliver.
The speed line runs in decade steps, from 10BASE-T at 10 Mb/s, through 100BASE-TX at 100 Mb/s, to Gigabit at 1 Gb/s and 10G at 10 Gb/s. Modern building LANs sit in the 2.5, 5 and 10G group. Read that line as a range of choices, not a ranking, because IoT endpoints are often happiest at the slow end. The branch to PoE is the separate point in Figure 33.1. It carries power and data on one cable, which is what makes a wired camera or reader practical. Speed and power are budgeted apart, and a switch has to satisfy both.
33.6.1 Common Ethernet Standards
10BASE-T: 10 Mbps, found on small microcontrollers and legacy industrial equipment
100BASE-TX: 100 Mbps (Fast Ethernet over two twisted pairs), common on higher-powered microcontrollers or single-board computers
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-TX, 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?
This section: 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 Mb/s to 10+ Gb/s — far above most IoT data rates; check shared uplinks |
| High reliability | No radio interference; consistent performance |
| Low latency | Typically sub-millisecond on a lightly loaded LAN |
| Predictable timing | Managed traffic and, where needed, time-sensitive networking can bound delay after validation |
| PoE capability | Single cable for data AND power |
| Security | A cable removes radio interception, but switch ports and network traffic still need access controls |
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 channel specification accounts for insertion loss, crosstalk, return loss, and the SNR needed to decode PAM-5 across four pairs. Do not confuse cable-only insertion loss with the full channel limit:
Beyond 100 m, errors rise; use a switch, extender or fibre.
10GBASE-T’s PAM-16 signalling needs a better channel: Cat6A/Cat7 for 100 m; Cat6 up to 37–55 m depending on alien crosstalk (TIA TSB-155).
33.7.2 Cable Construction and Deployment Evidence
Inspect the clear RJ45 plug at the end of the cable. The contact row, latch, and moulded boot are visible; the cable’s category and hidden conductor construction are not.
The plug can prompt checks of contact order, latch access, and strain at the cable exit. It cannot establish Cat5e or Cat6 rating, jacket suitability, shield, or installed route. Use the cable markings and field test for those claims, then continue with the construction choices below.
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.
Look closely at the plug in Figure 33.2, because the parts a datasheet leaves out are all visible there.
The clear plug shows eight gold contacts and coloured conductors. The opaque boot covers the cable exit, so this photo cannot prove pair twist, termination quality, or how strain is transferred. The cable is coiled, but its category, installed route, and measured performance need markings and tests.
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 |
| Usually mains or PoE powered | Ethernet PHYs draw too much for long battery life |
| Inflexible | Difficult to relocate devices |
Core Concept: PoE sources DC power alongside data over suitable Ethernet cabling for IP cameras, access points and sensors. Standard PSE port classes reach 15.4 W, 30 W, 60 W, or 90 W; cable losses leave less at the powered device.
Why It Matters: One cable can avoid a separate power outlet for a suitable device. Savings depend on the installation. A PoE switch can also centralize power management and UPS backup if its own supply and budget are designed for that load.
Key Takeaway: IEEE 802.3af sources up to 15.4 W, 802.3at up to 30 W, and 802.3bt Type 3 or Type 4 up to 60 W or 90 W at the PSE port; use 802.3bt for PTZ cameras, small displays and thin clients. Device-available power is lower after cable loss. Check each device’s class, port support, cable route, and switch total budget.
Illustrative scenario: A warehouse needs 50 IP cameras for security. Assume each camera streams 4K video at 25 Mbps. The warehouse is 200m x 150m with metal shelving that can reflect or obstruct radio signals.
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 Gb/s PHY (4 spatial streams, 160 MHz)
- Practical: typically 1–2 Gb/s shared across all devices
- 50 cameras competing for airtime
- Metal shelving can cause reflection or shadowing
- Result: High risk / likely insufficient — 1.25 Gb/s of continuous uplink video is near practical capacity and 802.11ac MU-MIMO does not help uplink; a survey would be needed to prove otherwise
Option B: Gigabit Ethernet with PoE+
- Each camera gets dedicated 1 Gbps port
- 25 Mbps uses only 2.5% of available bandwidth
- No radio contention on the camera-to-switch cable; shared uplinks still need capacity
- PoE+ (IEEE 802.3at) supplies 30 W at the switch port, with 25.5 W available at the camera
- Result: Strong candidate if aggregate uplinks and PoE budgets pass testing
Illustrative cost assumptions (50 cameras; obtain site quotations before deciding). The Ethernet example assumes three 24-port switches with enough aggregate PoE budget for the selected cameras:
| Item | Wi-Fi | Ethernet |
|---|---|---|
| Infrastructure | $3,000 (6 APs) | $12,000 (3x 24-port PoE switches) |
| Cabling | $500 (power drops) | $5,000 (Cat6 runs) |
| Power outlets | $2,500 (50 outlets) | $0 (PoE) |
| Total | $6,000 | $17,000 |
| Reliability | Variable (shared airtime) | Consistent (dedicated port) |
Result: Ethernet costs $11,000 more up front, but for mission-critical surveillance it buys a dedicated, interference-free port per camera; still size uplinks and PoE.
Key Insight: Cameras are good Ethernet candidates when predictable access capacity and central power justify cabling. Video reliability still depends on shared uplinks, storage, power, and monitoring.
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.
- A robot control path with a 100 ms update interval and a less-than-10 ms latency target belongs on Ethernet with TSN rather than a best-effort wireless link; still verify the worst case.
Illustrative scenario: A factory needs to connect 50 industrial robots across a 200m x 150m floor. Assume telemetry every 100 ms with a <10 ms network deadline. Safety functions require a separate fail-safe design; no network can promise zero packet loss.
Given:
- 50 robots with 100 ms update interval
- Latency requirement: <10 ms
- Packet loss: Define a measured loss target and fail-safe response for missed updates
- 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; verify worst case |
| Packet Loss | typ. 1–5% | typ. 5–10% | typ. 5–10% | ≈0 (BER ≤10⁻¹², IEEE 802.3 Cl.40); never assume 0% |
| Bounded timing | Requires a validated design | Unsuitable for this 100 ms cadence | Requires a validated design | Possible with a validated TSN path |
| Link rate | Up to 9.6 Gbps 802.11ax PHY under maximum configuration | Profile dependent; 50 kb/s is an illustrative setting | 250 kb/s at 2.4 GHz 802.15.4 PHY | 1 Gb/s for the chosen 1000BASE-T link |
These are illustrative values; validate the selected site’s timing, loss, and throughput.
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: The illustrative 3-200 ms latency span fails this deadline at its upper end. A real deployment needs its own worst-case and loss measurements.
- LoRaWAN: The illustrative 2,500 ms latency is 250 times the 10 ms deadline. A 1.45 s transmission, if that is the chosen profile’s measured airtime, also exceeds the 100 ms update interval.
- Zigbee: The 60 ms latency exceeds this 10 ms deadline. The robots need 2 Mb/s versus a 250 kb/s PHY rate — 8× too little, before overhead.
- Ethernet + TSN: IEEE 802.1Qbv schedules give bounded latency on every configured hop; 0.069 ms is one measured example.
Result: Gigabit Ethernet with a validated TSN profile is a strong candidate for this timing contract. Verify worst-case end-to-end delay, loss, recovery, and the independent safety response before selecting it.
Key Insight: A nominal link speed cannot guarantee a safety deadline or zero loss. Choose and test the complete communication path, then design the safety behavior for missed or late messages.
33.8 Knowledge Check
This section: Knowledge Check
33.9 Continue to Part 2
This section: Continue to Part 2 — Continue with Ethernet: PoE and Operations.
Continue with Ethernet: PoE and Operations.
Find help
3 reviewed answers.
Where should I start in a module?
Open the module page from the sidebar to see its chapters in order. Use the module map to return to a topic you need.
Modules and pathsReviewed
What can I try when a project does not work?
Check the symptom, then work through the diagnostic steps. Keep the error message and the smallest example that reproduces it.
When you are stuckReviewed
How do interactive examples work?
Use the interactive guide to check how examples and simulations work before changing your project.
Interactive examples guideReviewed