September 30th, 1980 is the day when Ethernet was first commercially introduced, making it exactly forty years ago this year. It was first defined in a patent filed by Xerox as a 10 Mb/s networking protocol in 1975, introduced to the market in 1980 and subsequently standardized in 1983 by the IEEE as IEEE 802.3. Over the next thirty-seven years, this standard would see numerous updates and revisions.
Included in the present Ethernet standard are not just the different speed grades from the original 10 Mbit/s to today’s maximum 400 Gb/s speeds, but also the countless changes to the core protocol to enable these ever higher data rates, not to mention new applications of Ethernet such as power delivery and backplane routing. The reliability and cost-effectiveness of Ethernet would result in the 1990 10BASE-T Ethernet standard (802.3i-1990) that gradually found itself implemented on desktop PCs.
As far as consumer network hardware goes, we’re all expected to be pretty happy with 802.11n WiFi and Gigabit Ethernet over Cat 6 cables. For most home users, that’s plenty of bandwidth for streaming movies and posting K-pop fancams to Twitter on a daily basis. If you want a fatter pipe, things can get expensive, fast. However, [TobleMiner] found a way to use surplus server-grade cards in a regular PC – providing huge bandwidth on a budget.
The adapter is designed to allow a FlexibleLOM card to fit into a regular ATX PCI-E card slot. A small additional bracket should be used to fix the card in place with the typical bracket retention screw.
HPE’s FlexibleLOM standard consists of a special edge connector on HPE servers that lets the end-user fit a variety of network adapters in a form factor designed specifically for blade and rack mount servers. At the electrical level, it’s simply PCI-Express 8x. FlexibleLOM network cards are built for high-speed data center use, often featuring SFP+ and QSFP+ interfaces capable of 10 gigabit and 40 gigabit speeds, respectively.
These cards can be had for under $20 on eBay, but won’t fit in a standard PCI-Express slot. Enter [ToberMiner]’s adapter, which hooks up the relevant PCI-Express lines to where they need to go, and mechanically adapts the FlexibleLOM hardware to fit in a regular ATX PC case.
As a project gets more complicated, some kind of internal communication network is often used to that all of the various modules and sensors can talk with each other. For hardware hackers like us, that usually means SPI, I2C, or maybe even good old fashioned UART. But if you’re pushing a lot of data around, like live video feeds from multiple cameras, you’ll need something a bit faster than that.
Which is why [Josh Elijah] has created the SwitchBlox Nano, a three port 10/100 Ethernet switch that fits on a one inch square PCB. All you need to do is provide it with power, with a generous input range of 5 to 50 volts, connect your devices to the Molex Picoblade connectors on the board, and away you go. There’s even a 5 V 1 A regulated output you can use to run your downstream devices.
If you’ve got a feeling that you’ve seen something very similar on these pages earlier in the year, you’re not imagining things. Back in April we covered the original five port SwitchBlox in a post that garnered quite a bit of attention. In fact, [Josh] tells us that the design of this new switch was driven largely by the feedback he got from Hackaday readers. The Nano is not only smaller and cheaper than the original, but now maintains full electrical isolation between each port.
The average Hackaday reader is as knowledgeable as they are opinionated, and we’re glad [Josh] was able to put the feedback he received to practical use. We’re proud that our community has had a hand in refining successful commercial products like the Arduboy handheld game system and the Mooltipass hardware password keeper. Now it looks like we can add a tiny Ethernet switch to the list of gadgets we’ve helped push up the hill. Maybe we should get a stamp or something…
It was only last August that PJRC released Teensy 4.0. At that time, the 4.0 became the fastest microcontroller development board on the planet, a title it still holds as of this writing — or, well, not exactly. Today the Teensy 4.1 has been released, and using the same 600 MHz ARM Cortex M7 under the hood, is now also the fastest microcontroller board. What the 4.1 brings to the table is more peripherals, memory, and GPIOs. While Teensy 4.0 used the same small form factor as the 3.2, Teensy 4.1 uses the larger board size of the 3.5/3.6 to expose the extra goodies.
The now slightly older Teensy 4.0 — released on August 7th of last year — is priced at $19.95, with the new 4.1 version offered at $26.85. It seems that the 4.1 isn’t intended as a replacement for the 4.0, as they serve different segments of the market. If you’re looking for an ultra-fast affordable microcontroller board that lives up to its Teensy name, the 4.0 fits the bill. On the other hand, if you need the additional peripherals broken out and can afford the space of the larger board, the not-as-teensy-sized 4.1 is for you. How big is it? The sample board I measured was 61 x 18 mm (2.4 x 0. 7″), not counting the small protrusion of the micro-usb jack on one end.
When you can get a WiFi-enabled microcontroller for $3, it’s little surprise that many of the projects we see these days have ditched Ethernet. But the days of wired networking are far from over, and there’s still plenty of hardware out there that can benefit from being plugged in. But putting an Ethernet network into your project requires a switch, and that means yet another piece of hardware that needs to get crammed into the build.
Seeing the need for a small and lightweight Ethernet switch, BotBlox has developed the SwitchBlox. This 45 mm square board has everything you need to build a five device wired network, and nothing you don’t. Gone are the bulky RJ45 jacks and rows of blinkenlights, they won’t do you any good on the inside of a robot’s chassis. But that’s not to say it’s a bare bones experience, either. The diminutive switch features automatic crossover, support for input voltages from 7 V all the way up to 40 V, and management functions accessible over SPI.
If you want to get up and running as quickly as possible, a fully assembled SwitchBlox is available to purchase directly from BotBlox for £149.00. But if you’re not in any particular rush and interested in saving on cost, you can spin up your own version of the Creative Commons licensed board. The C++ management firmware and Python management GUI isn’t ready for prime time just yet, but you’ll be able to build a “dumb” version of the switch with the provided KiCad design files.
The published schematic in their repo uses a Microchip KSZ8895MQXCA as the Ethernet controller, with a Pulse HX1344NL supplying the magnetics for all the ports in a single surface mount package. Interestingly, the two images that BotBlox shows on their product page include different part numbers like H1102FNL and PT61017PEL for the magnetics, and the Pulse H1164NL for the Ethernet controller.
Make Networks Wired Again
There’s no question that WiFi has dramatically changed the way we connect devices. In fact, there’s an excellent chance you’re currently reading these words from a device that doesn’t even have the capability to connect to a wired network. If you’re looking to connect a device to the Internet quickly, it’s tough to beat.
But WiFi certainly isn’t perfect. For one, you have to contend with issues that are inherent to wireless communications such as high latency and susceptibility to interference. There’s also the logistical issues involved in making that initial connection since you need to specify an Access Point and (hopefully) an encryption key. In comparison, Ethernet will give you consistent performance in more or less any environment, and configuration is usually as simple as plugging in the cable and letting DHCP sort the rest out.
Unfortunately, that whole “plugging in” part can get tricky. Given their size, putting an Ethernet switch into your project to act as an internal bus only works if you’ve got space to burn and weight is of little concern. So as appealing as it might be to build a network into your robot to connect the Raspberry Pi, motor controllers, cameras, etc, it’s rarely been practical.
This little switch could change that, and the fact it’s released under an open source license means hackers and makers will be free to integrate it into their designs. With the addition of an open source management firmware, this device has some truly fascinating potential. When combined with a single board computer or suitably powerful microcontroller, you have the makings of a fully open source home router; something that the privacy and security minded among us have been dreaming of for years.
We’re used to extending our network connections and being no longer constrained in our use of Ethernet by proximity to a switch or hub. Our houses routinely contain wireless networks, and of course powerline-Ethernet units passing data over our mains wiring. [Peter Franck] had a similar problem but without the mains power, for a distributed sprinkler system he needed to send Ethernet over DC cables.
The solution is a surprisingly simple one, taking one of those powerline Ethernet units and converting it by removing its mains power section. These devices contain the Ethernet and powerline modem chip with its associated circuitry, and a small switch-mode power supply. He’s removed the power supply and put in a capacitive coupling to the DC cabling, resulting in a relatively inexpensive DC powerline network device.
Powerline Ethernet devices are not without their own issues, for instance they are not popular with radio amateurs due to their effect on the RF noise floor. We’d therefore be curious to see what the RF emissions are like for this hack, but we still think it’s a useful weapon in the armoury as well as something to do with all those surplus powerline Ethernet bricks.
A remote Ethernet device needs two things: power and Ethernet. You might think that this also means two cables, a beefy one to carry the current needed to run the thing, and thin little twisted pairs for the data. But no!
Power over Ethernet (PoE) allows you to transmit power and data over to network devices. It does this through a twisted pair Ethernet cabling, which allows a single cable to drive the two connections. The main advantage of using PoE as opposed to having separate lines for power and data is to simplify the process of installation – there’s fewer cables to keep track of and purchase. For smaller offices, the hassle of having to wire new circuits or a transformer for converted AC to DC can be annoying.
PoE can also be an advantage in cases where power is not easily accessible or where additional wiring simply is not an option. Ethernet cables are often run in the ceiling, while power runs near the floor. Furthermore, PoE is protected from overload, short circuiting, and delivers power safely. No additional power supplies are necessary since the power is supplied centrally, and scaling the power delivery becomes a lot easier.
Devices Using PoE
[via PowerOverEthernet.com]VoIP phones are becoming increasingly prevalent as offices are opting to provide power for phones from a central supply rather than hosting smaller power supplies to supply separate phones. Smart cameras – or IP cameras – already use Ethernet to deliver video data, so using PoE simplifies the installation process. Wireless access points can be easily connected to Ethernet through a main router, which is more convenient than seeking out separate power supplies.
Other devices that use PoE include RFID readers, IPTV decoders, access control systems, and occasionally even wall clocks. If it already uses Ethernet, and it doesn’t draw too much power, it’s a good candidate for PoE.
On the supply side, given that the majority of devices that use PoE are in some form networking devices, it makes sense that the main device to provide power to a PoE system would be the Ethernet switch. Another option is to use a PoE injector, which works with non-PoE switches to ensure that the device is able to receive power from another source than the switch.
How it Works
Historically, PoE was implemented by simply hooking extra lines up to a DC power supply. Early power injectors did not provide any intelligent protocol, simply injecting power into a system. The most common method was to power a pair of wires not utilized by 100Base-TX Ethernet. This could easily destroy devices not designed to accept power, however. The IEEE 802.3 working group started their first official PoE project in 1999, titled the IEE 802.3af.
[via Fiber Optic Communication]This standard delivered up to 13 W to a powered device, utilizing two of the four twisted pairs in Ethernet cabling. This was adequate power for VoIP phones, IP cameras, door access control units, and other devices. In 2009, the IEEE 802.3 working group released the second PoE standard, IEEE 802.3at. This added a power class that could deliver up to 25.5 W, allowing for pan and tilt cameras to use the technology.
While further standards haven’t been released, proprietary technologies have used the PoE term to describe their methods of power delivery. A new project from the IEEE 802.3 working group was the 2018 released IEEE 802.3bt standard that utilizes all four twisted pairs to deliver up to 71 W to a powered device.
But this power comes at a cost: Ethernet cables simply don’t have the conductive cross-section that power cables do, and resistive losses are higher. Because power loss in a cable is proportional to the squared current, PoE systems minimize the current by using higher voltages, from 40 V to 60 V, which is then converted down in the receiving device. Even so, PoE specs allow for 15% power loss in the cable itself. For instance, your 12 W remote device might draw 14 W at the wall, with the remaining 2 W heating up your crawlspace. The proposed 70 W IEEE 802.3bt standard can put as much as 30 W of heat into the wires.
The bigger problem is typically insufficient power. The 802.4af PoE standard maximum power output is below 15.4 W (13 W delivered), which is enough to provide power for most networking devices. For higher power consumption devices, such as network PTZ cameras, this isn’t the case.
Although maximum power supply is specified in the standards, having a supply that supplied more power is necessary will not affect the performance of the device. The device will draw as much current as necessary to operate, so there is no risk of overload, just hot wires.
So PoE isn’t without its tradeoffs. Nevertheless, there’s certainly a lot of advantages to accepting PoE for devices, and of course we welcome a world with fewer wires. It’s fantastic for routers, phones, and their friends. But when your power-hungry devices are keeping you warm at night, it’s probably time to plug them into the wall.
