editor's blog
Subscribe Now

Just What Is the New IEEE Sensor Standard?

IEEE published a sensor-related standard recently. And, depending on what headline or report you read, you may end up with a wide variety of conclusions as to what it’s all about. The original press release linked it to an eHealth memorandum of understanding (MOU) between IEEE-SA and the MEMS Industry Group (MIG); NIST issued a press release regarding their participation; and various stories described it as a “sensor hub” standard.

All of which surprised me, because I was only aware of one standard effort underway, and it was none of those things. Well, not directly, anyway. Of course… things can happen without my knowing about them, so I scrambled to see what I had missed.

Turns out I hadn’t missed anything. This P2700 standard is the very same one we overviewed in May of 2013. Which is nine months before the eHealth MOU. It’s about sensor datasheet parameters. It’s also part of a process in which NIST was indeed involved, although the specific effort was spearheaded by a number of companies (as described in a yet earlier overview of MEMS standards efforts); NIST was in the list of acknowledgments, not the list of contributors. It is fair to say that some of the discussion probably got a start in yet another NIST effort regarding MEMS testing that predated all of this.

But the bottom line is that the main motivator was the fact that different sensor manufacturers were defining their datasheet parameters differently, making it impossible to compare one sensor’s performance to that of another. This is a fundamental driver of standards, and has been for a long time.

Here are the purpose and scope of the standard, as included in the draft submitted to IEEE:

1.1 Purpose of Document

This document presents a standard methodology for defining sensor performance parameters with the intent to ease system integration burden and accelerate TTM. Here within, a minimum set of performance parameters are defined with required units, conditions and distributions for each sensor. Note that these performance parameters shall be included with all other industry accepted performance parameters.

1.2 Document Scope

This document is intended to drive the sensor industry toward common nomenclature and practices as cooperatively requested by mobile platform architects. It clearly outlines a common framework for sensor performance specification terminology, units, conditions and limits. The intent is that this is a living document, scalable through future revisions to expand as new sensors are adopted by the platforms. The intended audience of this document is sensor vendors, ISVs, platform providers and OEMs.

Can the sensors affected by this be used in eHealth? Yes, of course. And all kinds of other things. It’s not specifically eHealth-related.

Was NIST involved? Yes, as was MIG, although more with coordination than with content.

Will the sensors involved in this standard be connected to sensor hubs? Undoubtedly. Will the sensor hub code be simplified, as claimed in some stories? That’s actually not clear to me. Sensor hubs need to talk to sensors, extract their values, and compute with them. There’s nothing in the standard that deals with how that’s done.

I suppose that, when doing sensor fusion, some adjustment algorithms might be needed to adapt to different sensors if the readings from different manufacturers mean different things. Then again, this standard is about what’s in the datasheet and the testing conditions for different parameters; it’s not clear if that affects the actual readings. I don’t think any chips are changing as a result of the standard.

One other quick note regarding IEEE. There are actually 2 flavors of IEEE, as we discussed a few years back. There’s IEEE-SA (“Standards Association”) and IEEE-ISTO (“Industry Standards and Technical Organization”). One is more “independent,” with a thorough vetting process; the other allows companies sponsoring efforts to keep some control over the process. It had been a while since I thought about that, and so I wanted to be sure about which IEEE this standard had gone through.

IEEE-SA is the traditional arm of IEEE. So this standard has received the nod from the more exacting side of IEEE. And it did so in relatively short time (for IEEE), with little in the way of change to the original submitted draft, as told to me by IEEE-SA’s Director of Global Business Strategy and Intelligence, Alpesh Shah.

All of which means that the team that put the draft together did yeoman’s work.

Leave a Reply

featured blogs
Jan 21, 2022
Here are a few teasers for what you'll find in this week's round-up of CFD news and notes. How AI can be trained to identify more objects than are in its learning dataset. Will GPUs really... [[ Click on the title to access the full blog on the Cadence Community si...
Jan 20, 2022
High performance computing continues to expand & evolve; our team shares their 2022 HPC predictions including new HPC applications and processor architectures. The post The Future of High-Performance Computing (HPC): Key Predictions for 2022 appeared first on From Silico...
Jan 20, 2022
As Josh Wardle famously said about his creation: "It's not trying to do anything shady with your data or your eyeballs ... It's just a game that's fun.'...

featured video

Synopsys & Samtec: Successful 112G PAM-4 System Interoperability

Sponsored by Synopsys

This Supercomputing Conference demo shows a seamless interoperability between Synopsys' DesignWare 112G Ethernet PHY IP and Samtec's NovaRay IO and cable assembly. The demo shows excellent performance, BER at 1e-08 and total insertion loss of 37dB. Synopsys and Samtec are enabling the industry with a complete 112G PAM-4 system, which is essential for high-performance computing.

Click here for more information about DesignWare Ethernet IP Solutions

featured paper

nanoPower Module Extends Battery Life in Space-Constrained Applications

Sponsored by Analog Devices

Designers can now increase battery life and reduce size in space-constrained IoT devices with a power module that features the lowest quiescent current compared to competitive solutions and uSLIC built-in inductor technology that reduces solution size by up to 37%.

Read Now

featured chalk talk

Software and Automotive Safety

Sponsored by Siemens Digital Industries Software

In the realm of automotive designs, safety must reign above all else. But the question remains: How can we innovate within the constraints of today’s safety standards? In this episode of Chalk Talk, Amelia Dalton chats with Rob Bates from Siemens about the role ISO 26262 plays when it comes to COTS and open source software, what certified software components are all about, and how heterogeneous multiprocessing can be helpful in your next automotive design.

Click here to download the whitepaper called "Is it Possible to know how Safe we are in a World of Autonomous Cars?