1

This is a question for discussion... I have recently started looking in to home automation and "smart devices" and see a clear tendency for everything to run on WiFi, with some exceptions of bluetooth, Zigbee and Z-wave.

But why data transfer via power line (PLC) is not a thing, really? It sounds much cleaner without all that RF noise?

I've looked in to power line modem chips and they are quite expensive ($3 and up), compared to ESP chipset. Is this the reason?

Multiple PLC devices also need a single interface ("hub") to WiFi. Is this another reason?


From comments it looks like main issue with power line communication is noise. An example of X-10 was mentioned and I have quickly found this product, which has been discontinued: http://www.csi3.com/homevis2.htm There's a PDF explaining all sorts of problems the X-10 protocol suffers from: http://www.csi3.com/app_x10.pdf

Basically X-10 will be killed by any equipment that injects noise close to zero-cross, for example brushed motors.

From quick search it looks like X-10 is a very primitive protocol and has no error correction or other more modern means of noise immunity or bandwidth sharing.

There are LAN modules out there, sold even today (and not that cheap), but these were outperformed by WiFi some time ago, so WiFi is an obvious choice for high speed connection. However low-speed communication potential seems to be forgotten... If only there was a way to combine robustness of LAN-over-AC and low price at low speed...

Dave Tweed
  • 168,369
  • 17
  • 228
  • 393
elektrinis
  • 110
  • 1
  • 6
  • 1
    My guess is that the complexity of home wiring is a problem. Two sockets near each other can easily be on different legs of a transformer with hundreds of feet of wiring between them, which makes for a very weak signal, or even no signal at all. Compared to that, wireless is very simple. Just put them close enough and they'll talk to each other. – user1850479 Dec 28 '19 at 17:57
  • 3
    Voting to close due to it being opinion-based. Alas, long discussions aren't a StackExchange thing. – TimWescott Dec 28 '19 at 17:59
  • I briefly worked on a project for in-building connectivity using the power line, right before wireless routers hit the market in a big way. The bottom line is that powerlines just aren't made to carry data well; any solutions end up being fragile, and require far more fussing for far less bandwidth than wireless -- this was the case even in 1999, or whenever it was that I got sucked into that effort. – TimWescott Dec 28 '19 at 18:01
  • Home wiring used to be used back in the day. Look up X10. It was marginally reliable at best and eventually stopped working. (not sure why) – Jeff Wahaus Dec 28 '19 at 18:01
  • Will look in to X10, as proposed. After a quick search it looks like there is no encryption or any other means of error correction? In case of home automation, you don't need much bandwidth to operate switches and dim your lights. Would be very interesting to read a case study if someone has it on hand. – elektrinis Dec 28 '19 at 18:04
  • @elektrinis channel coding mathematically makes no sense in the least-SNR regime: limiting your transmit power, below a certain bit energy-to-noise ratio, adding redundancy for error correction reduces the energy you have per bit, more than it makes error correctable, making your communication *less* reliable instead of *more* reliable. – Marcus Müller Dec 28 '19 at 18:36
  • Error correction isn't really needed if you just send the same packet many times. – Jeff Wahaus Dec 28 '19 at 18:39
  • @JeffWahaus that's channel coding / forward error correction, it's called *repetition code*, and it's basically the least efficient code you can build; there's always a better code than that. – Marcus Müller Dec 28 '19 at 18:49
  • I wasn't proposing redundant packets as a solution. It is how the X10 protocol dealt with transmission error problems. – Jeff Wahaus Dec 28 '19 at 19:20
  • I've used powerline ethernet in a home where wifi wasn't really a good option. It is severely limited -- you an only get rated speed for hosts on the same house circuit, GFCI interferes with it, and a couple of other issues. I was able to get okay speed with it across a breaker -- fast enough to stream 20Mbit/s videos locally. But that was still slower than the internet pipe into my home at the time. Now I'm running real ethernet and easily get 15x the speed (like 800Mbit/s locally). That said, most home automation protocols aren't going to need any "speed" at all, just low latency. – nomen Dec 29 '19 at 04:54
  • But what about all those smart power meters? Also what about KNX communication? STKNX chip is only $2 at quantity ant this seems fairly fresh. – elektrinis Dec 29 '19 at 14:53

4 Answers4

8

But why data transfer via power line (PLC) is not a thing, really? It sounds much cleaner without all that RF noise?

As someone having worked with the powerline channel: Hahahahaaa.... hahaha.

The noise on a power line that is meant to transport power to power supplies, small fast-turning commutated motors, large slow-turning motors, large heaters, and a bazillion of electronic devices is by far worse in any usable bandwidth compared to what you see in RF on an ISM band.

And to make matter worse: where it's very doable to impedance-match an antenna for a range of frequencies large enough for communication, powerline has a very frequency-dependent impedance, and especially the frequencies with low noise are the ones that are lower in impedance and thus require more power to drive.

Oh, and to make matters even worse: even for very narrowband usage, the channel isn't stationary, but at the very least highly cyclostationary (with grid frequency), where there's times that are very badly usable, at all. One can deal with that, but it comes with an inevitable waste of power, or with an non-deterministic latency in the order of a grid period, making this a very undesirable medium for time-critical control.

I've looked in to power line modem chips and they are quite expensive ($3 and up), compared to ESP chipset. Is this the reason?

Cost is usually the result of technical complexity and volume. But yes, powerline comms requires a very strong driver frontend, because the impedance of power line of course is very low (you want that, or else you'd be losing a lot of energy when using the powerline for power). That's hard.

Also, powerline comms is inherently very frequency-selective, so very complicated equalizer systems are necesary, driving up processing complexity, too.

$3 for a PLC chip is pretty impressively cheap, by the way. One of the reason a very wideband, complex, impressive chip like the ESP32 is even cheaper is the economics of scale, and the different expectations for reliability.

Multiple PLC devices also need a single interface ("hub") to WiFi. Is this another reason?

That's not true. Network architecture has nothing to do with the physical medium. Just as you can have ad-hoc WiFi networks, you can have ad-hoc powerline networks. Both are a bad idea as soon as the network becomes sufficiently complex.

So, in the end:

But why data transfer via power line (PLC) is not a thing, really?

PLC is mostly dead, at least indoors, because RF turns out to be easier, requires less energy, can actually be made very robust (especially in the low-datarate regime), and doesn't require expensive couplers (you really don't want to connect your semiconductor PLC modem to your power line without protection, most often in the shape of a transformer), but only relatively small antennas. The high speed of modern semiconductors makes modulating a signal onto an RF carrier easier than putting it on a cable that was meant for power distribution, not data signalling.

I say mostly, because of course there are modern PLC standards – both for indoors, as well as for backhaul communications (e.g. for letting your smart electricity meter communicate with the power company, or the transformer station outside your block to the next substation). Some of them are very robust, others are nearly as fast as wired Gigabit ethernet, at least theoretically. But none of them are as cheap to build as RF comms.

Marcus Müller
  • 88,280
  • 5
  • 131
  • 237
  • And my experience with wireless says "that sucks." Ethernet over powerline works fine in my house. WLAN is spotty, to the point I have a WLAN extender over powerline ethernet so that wireless devices have WLAN upstairs. I'd hate to have to depend on wireless to get my PC upstairs connected to the router downstairs. YMMV. – JRE Dec 28 '19 at 18:44
  • 1
    @JRE yeah, but my wireless experience tells me "are you using the wireless standard you're looking for?"; i.e. I totally agree, obviously, 2.4 or 5 GHz high-rate comms within a house is obviously hard to do through steel-reinforced concrete, for example, but if you, like OP, are really in the single digit bits per second region, you can damn well turn on the compressor in someone else's cellar trash can across the city with < 200 mW of power at 2.4 GHz. – Marcus Müller Dec 28 '19 at 18:48
2

I'll answer from a different angle:

If you want to sell a product, the customer has to want to buy it...

The customer wants to slap a light switch where it is convenient on a wall where there are no wires installed, put temperature sensors in various places (indoors, outdoors), put sensors on doors and windows to detect when they are opened (for smart heating) or when a burglar breaks the glass...

Also it has to be good-looking, slick, thin, versatile, future-proof, and above all easy to install: just peel off the sticky tape!

enter image description here

Power line communication doesn't check the money-making boxes. It is expensive, bulky (ie, not thin), power-hungry, usually requires a transformer, and it requires wires, opening junction boxes or calling an electrician...

This means the customer has only a limited number of places where they can put your wired product. However, they probably have lots of doors, windows and walls so you can sell them 10 times more wireless gadgets. Profit!

ZigBee and the like (BTLE...) check all the boxes. Low power, tiny flat antenna... These small sensors last for several years on a small non-rechargeable battery. Switches only draw power when actuated. WiFi requires more power, so it won't run well on a battery.

enter image description here

Anyone can install them. This is an extremely efficient wallet draining system.

bobflux
  • 70,433
  • 3
  • 83
  • 203
1

I can say from practical experience of two separate efforts over the years of purchasing Ethernet over Power Line Adapters that the technology is not reliable and will often run at slow data rates due to excess noise on the power line. These adapters are also fairly expensive.

My experience also has shown that the Ethernet over Power Line adapters that I tried are unable to sustain the bandwidth to stream video for a pleasent viewing experience.

Someone else mentioned X10 technology. In the past I went into that in a big way to permit remote switching of lights in a basement without having to rewire anything. I found the X10 to work fairly well but there was a reliability problem. Almost every time there was a thunder storm with a little bit of lightening some of my X10 switches or load modules would be taken out due to surges on the power lines.

Michael Karas
  • 56,889
  • 3
  • 70
  • 138
0

I had power line ethernet adapters to link my PC to the ADSL internet connection of the house. 2 more PCs were plugged to the ADSL box directly. The system worked well enough, but I scrapped it and got a WiFi router quite soon after we got smartphones. People in our house wanted to use ADSL connection instead of the direct phone mobile data because

1) mobile data was frequently off say 1 second. There was no overpopulation, but phone operators simply do not want to keep strong field in an area where houses were at least 500 meters apart from each other and the nearest highway was at 1000 meters away

2)everyone didn't have fixed payment/month, the bill depended also on how many gigabytes they had got data

WiFi was needed because there was no acceptable way to link a smartphone via power lines.