editor's blog
Subscribe Now

Old-School Analog Outputs

Today we looked at the role of Freescale’s new FXLN83xxQ accelerometer for analyzing vibrations. But one feature of the accelerometer had me cocking an eyebrow: analog outputs.

We’ve covered a lot about sensors here before, and in the huge majority of the cases, a sensor consists of a MEMS (or other) sensing element, an ASIC to clean up and digitize the signal, and then a series of registers where all the relevant data gets placed.

An outside entity, like a sensor hub, can then read those registers over a bus connection – typically I2C or SPI. What could be simpler?

Well, I guess an analog output could be simpler: you eliminate all of that messy digital stuff. But it seems to me that, running an analog signal halfway across town to get it to the analog inputs of a microcontroller (aka MCU, or whatever hub is used) would run the risk of seriously degrading the analog value in a way that wouldn’t happen with a digital signal.

XL_schematic_red.jpg

 

(Click to enlarge)

Image courtesy Freescale.

I asked Freescale about this, and they justify it based on the wide variety of digital interfaces in use, in particular in industrial settings. Heck, they say that even CAN bus is leaving the confines of vehicles and moving into other applications.

Freescale makes lots of microcontrollers. This variety of MCUs partly reflects the diversity of interfaces they may talk to: Rather than having one large unit with all possible interfaces, they offer different devices. And yes, they’re assuming (or at least hoping) that you’ll be using their MCU.

So the idea goes thusly: first off, you simply don’t run the analog signals halfway across town. In these applications, an MCU is likely to be right nearby. (If not, then you want to move it so that it is nearby.) The MCU you choose will then reflect whatever bus you’re using, and that’s where you go digital. They prefer this, obviously, to having to have a bunch of different versions of the sensor to suit the various digital protocols.

There’s one other convenient thing about digital registers, however: they’re good at storing values while the rest of the system goes to sleep for a while to reduce power. Well, apparently these analog outputs can manage the same trick. The internal electronics shut down between samples, but the output is held between samples. This decouples the rate at which the MCU samples the analog outputs from the rate at which the sensor samples the system and allows power as low as 200 µA when running.

That’s how they see it; if you see it differently, then your comments are encouraged below.

Leave a Reply

featured blogs
Nov 13, 2019
At the third stroke of midnight on 30 September 2019, Australia's talking clock fell silent....
Nov 13, 2019
By Elven Huang – Mentor, A Siemens Business SRAM debugging at advanced nodes is challenging. With pattern matching and similarity checking, Calibre tools enable designers to more quickly and precisely locate SRAM modification errors and determine the correct fix. Static...
Nov 13, 2019
Decisions, Decisions … I may be in the market for a new car in the near future. Unless you'€™ve got a strong preference (and most car buyers DO have a strong preference, IMO), choosing a vehicle is a series of trade-offs.  Fuel efficiency vs. horsepower. Functionali...
Nov 13, 2019
One of the big trends that has been happening somewhat below the radar is the growth of various forms of 3D packaging. I noted this at HOT CHIPS in summer, when a big percentage of the designs were... [[ Click on the title to access the full blog on the Cadence Community sit...
Nov 8, 2019
[From the last episode: we looked at the differences between computing at the edge and in the cloud.] We'€™ve looked at the differences between MCUs and SoCs, but the one major thing that they have in common is that they have a CPU. Now'€¦ anyone can define their own CPU ...