Not only MCU but also memory is a key factor for smart utility meters. TI is somehow leading the MCU part but not the memory, suprisingly even having a great technology called FRAM in Texas. FRAM makes the meter design extremely simple and flexible. Fujitsu and Ramtron leads the memory market for smart meters with FRAM. TI wake up...
But if this was so lucrative, then why did google retired their power-meter service ?
Its just that there isn't enough eco-system built around to manage|optimize energy. And also its usage is expensive.
Many companies have smart-metering products from long, but lack of government urgency, and tough norms are also pulling this market low.
Data is only useful to the extent that it can alter some outcome, in this case, a customer's use of electricity. Almost no electrical customer even knows that their new smart meter is capable of turning off their power. The above article states, "to enable utilities to ease peak power demand..." where ease should be read as: a) a total disconnect; b) a rolling brown out; c) by interfacing with your own personal in home network to turn off selective appliances such as A/C, dryers, heat pumps or any other device which has built in communication capability.
I can see a small business in modifying newer appliances (if possible) to make sure they cannot communicate. The polite way to modify power consumption is to let the consumer know (by checking an Internet site at their convenience) their current charge per kWh. Then let them decide what devices to turn off.
I see a whole lot of discussion about the technology for the communication with the smart meters but only a small amount about how this is going to save enough energy to be worth the effort. Of course, the very first use will be to raise prices a lot just when everybody wants power the most. We all know that is the primary goal of the two way system. The other goal is to eliminate the expense of manual meter reading, which will reduce the utilities costs quite a bit, but will not reduce our price for power at all.
The way to eliminate all of the privacy concerns is to keep the specific minute-by-minute consumption data in the meters, and to just totalize the product of KWH and the rate at the time of consumption. Then the utility could poll the meters to determine the charge for that month's power. No customer information except for the total charge would ever need to be sent out, just as in the past when meters were manually read. The utility has no need of individual household consumption at any particular time, only block by block, or subdivision by subdivision. The assertion that they need to know the individual rate of use at any particular instant is not valid.
What are the engineering and design challenges in creating successful IoT devices? These devices are usually small, resource-constrained electronics designed to sense, collect, send, and/or interpret data. Some of the devices need to be smart enough to act upon data in real time, 24/7. Are the design challenges the same as with embedded systems, but with a little developer- and IT-skills added in? What do engineers need to know? Rick Merritt talks with two experts about the tools and best options for designing IoT devices in 2016. Specifically the guests will discuss sensors, security, and lessons from IoT deployments.