Low Power Ethernet Hubs?
mike.851 asks: "I'm an engineer working in the embedded systems field. For the past few years, I've been using RS-232 to interconnect various modules into the embedded systems that I build. Lately, I've found that RS-232 simply isn't flexible enough for my growing needs. I need to switch to something else, and I don't think that USB is really an option for me. I've been looking into embedded ethernet as an alternative. I've found several great low-power platforms for hardware development including several of the uClinux kits as well as products from Rabbitsemiconductor. However, I'm having trouble finding ethernet hubs that meet my power requirements (my goal is 2W or better for the hub). So far I've found Ctrlink and W-linx, and I've considered replacing the power supplies in commodity hubs with switching regulators. Does anyone have experience with these products? Does anyone know of other low-power hubs? Thanks."
you could always invent wireless power... just a thought
"I hate people, but i love Gatherings. Isn't it ironic?" -- Randall Graves, Clerks
What about FireWire faster than fast ethernet and is peerless. Apple just released a reference driver.
You could always take a step back in time and use 10base-2. Yeah, coaxial cable sucks and you're limited to 10 Mbps.
Also, I have no idea if any embedded ethernet controllers support BNC connectors, but this would allow to you take one device out of the power consumption equation.
Starting references: here and here.
Ethernet is designed for relatively long distances, and has high power requirements to support those distances. I've worked building embedded systems that used lower power trancievers on the backplane and on each board to save power. Obviously if you do something like this you won't be standards compliant anymore, but if you're only talking to your own devices it could work for you. If not, there are high speed serial interfaces availble on telecom chips that you could use. Search google for HDLC and you'll find exactly what you're looking for.
I ran into a similar perdicament last year where I needed a low power ethernet switch/hub to connect two wireless units on a tower where the cable lengths to the ground were too long.
We ended up using industrial ethernet switches from Sixnet. The price wasn't _too_ bad, I seem to recall $500 for a 5 port switch. Their site is: here
Taking a look at the specifications located here they have units in the 2W Range.
I hope this helps. BTW, we've had no problems with the unit, even after a lightning strike that nuked two of the connected radios.
While Ethernet is one option, it might be a poor fit for your needs.
Some of the things you left out were the ability to survive in harsh environments, dirty power tolerance, price considerations, distance, etc.
There are a number of other bus systems that have made a few trade offs in these areas vs. total speed. Many of them are derived from work for the aerospace and automotive markets.
A few systems you might consider are:
LIN - very very low cost, but probably not fast enough for you.
CAN - up to 1 mb/Sec, lots of low cost off the shelf parts available, developed mostly by Bosch.
Flexray - faster yet, parts are more expensive, but it is faster
MOST - very fast, but targeted at moving multi-media data.
TTCAN - a modification of CAN for real time.
Most of these will support power on connects/disconnects, and are very fault tolerent.
Places to go:
www.flexray.com
www.can.bosch.com
www.ami-c.org/downloads1.htm
These are automotive focused (I'm NOT a "Car guy"), but that is because the industry is very cost aware and very big into reliability. What they tend to use is 10 year old technology that has been beat to death, has all the bugs worked out, has bunches of development tools, and all the hard parts (chips, in this case) are commodity items.
----- Lotus Super 7 - A real car.
is about as low-power as it gets, heh.
Have you considered PoE-based solutions? Here's one from 3Com, the NJ100 Network Jack (and a review of it by Tom's Hardware). While the NJ100 is not intended for use inside a closed box, using one of these would allow you to route power along with data between the various modules in one of your systems.
Depends how much width you really need- I've heard the venerable ArcNet technology is quite popular among the embedded set, and that updates to the spec have catered to that market, as regards noise-resistance, power, etc.
Stay away from 100Mb ethernet- by design, if you have a 100MB link, there is a continuous stream of a pseudo-random code being transmitted by each side, which means, basically, 40mW per port, no matter the activity. 10Mb uses much less frequent link test pulses. You can also go in and remove the LEDs, which are probably unnecessary in your application. If you really want to go hard-core, you can hack your way into the part using the MDIO interface (Similar to I2C) and disable unused ports individually.
The Altima AC205 is an "ultra low power" part that may be used in the hub you want. It is 100Mb, but to use the power hungry 100Mb mode, both sides have to be 100Mb.
The same I2C protocol used in PCs for environmental monitoring and whatnot is useful for embedded too. You can string several devices on a two-wire bus, you get 2Mbps of speed (I think, it's been a while), and I've seen embeeded systems boards as well as devices like lcd display units that support this protocol for generic communication. There's also the I2C-variant "SMBus", not really sure what the difference is between the two.
11*43+456^2
If you only need to connect 2 devices, you could use a crossed/null ethernet cable and connect them directly- without a hub. Works with 10 or 100 mb/s.
It's probably not applicable for your use, but there are at least 4 manufacturers out there producing a combined PCI NIC (rtl8139) and 5 port 100Mb switch or 10Mb hub.
One port is used internally for the NIC and the PC presents 4 ports out the back, with one having a rollover switch for uplinking.
My own experience with small external hubs is that there's more power dissipated in the wall-wart transformer than in the hub itself. This also applies to modems. Most of the wall warts are pretty ineficiently designed and produce about 9-10W worth of heat.
(This is significant when you have 70 modems in a cabinet. As a small ISP, we converted the modem pool to one big-ass transformer and a bus feed, which dropped power consumption by 600W and the AC bills by a few dollars a month.)
If every mW counts, consider clipping the leds.
Have you actually measured the current consumption of a DC hub to see how much they're chewing?
Most of the DC hubs(*) I've encountered are being fed from 9VDC/250mA PSUs, so can't be exceeding 3 watts in the first place.
(*)AC-fed ones are more common, usually with 9-12V 250mA PSUs feeding them, so the power consumption stacks up to much the same thing.
If you reall only need the equivalent of an RS232 connection, then you may only need a crossover cable. Similarly, it may be cheaper to provide two or three ethernet trancievers and crossover cables to the associated units, than it would be to pay for a third-party low-power hub.
Free Software: Like love, it grows best when given away.
Maybe the "picnic" would be useful to you... its an open source TCP/IP stack for a PIC microcontroller...