sensors and embedded systems in the era of the iot final e-book

7/24/2019 Sensors and Embedded Systems in the Era of the IoT FINAL E-Book

1/12

INTRO

CHALLENGE 1

The complexity

CHALLENGE 2

The interdisciplin

CHALLENGE 3

The need to unddatasheets requ

CHALLENGE 4

The security issu

CHALLENGE 5

Managing the in

CHALLENGE 6

The need for ana

CHALLENGE 7

The cloud

CONCLUSION

SPONSORS

CONTACT

Your Technical Resource Sensing Communication

Resource and Refe

Produced by:

Sensors and Embedded Systems

in the Era of the IoT:The Top 7 Challenges and What Engineers Need to Do Today to Succeed

Sponsored by:

DIGITAL E-BOOK

INTRO

CHALLENGE 1

The complexity

CHALLENGE 2

The interdisciplin

CHALLENGE 3


CHALLENGE 4

The security issu

CHALLENGE 5

Managing the in

CHALLENGE 6

The need for ana

CHALLENGE 7

The cloud

CONCLUSION

SPONSORS

CONTACT


2/12

Sponsored by:

Produced by:


Sensors and Embedded Systems in the Era of the IoT:The Top 7 Challenges and What Engineers Need to Do Today to Succeed

INTRO

CHALLENGE 1

The complexity

CHALLENGE 2

The interdisciplin

CHALLENGE 3


CHALLENGE 4

The security issu

CHALLENGE 5

Managing the in

CHALLENGE 6

The need for ana

CHALLENGE 7

The cloud

CONCLUSION

SPONSORS

CONTACT

What embedded topics are youinterested in learning more about?

The Internet of Thingsquite possibly represents the biggest challenge many engineers will face in their careers.

QFrom the need to cope with small memories, power constraints, andsystem complexity to wrestling with the interfaces, evolving standards, and

understanding enough analog in order to ex tract meaningful information out

of sensors, engineers are being forced to move out of their comfort zones and

acquire new skill sets. In fact, two-thirds of respondents in a recent survey by

Sensors Magazine said that the y want more information on connected devices

and the IoT.

In this special report, we look at the key issues and challenges impacting

engineers designing for the IoT and the steps they can take to develop

reliable and resilient products.

EMBEDDED SYSTEMSDESIGN

CONNECTED DEVICES

AND IoT

EMBEDDED SOFTWAREDESIGN

PROGRAMMING

HARDWARE: DESIGN, I/O ANDINTERFACING

OTHER

Source: 2015 Sensors Magazine Embedded Survey


3/12

Sponsored by:

Produced by:



INTRO

CHALLENGE 1

The complexity

CHALLENGE 2

The interdisciplin

CHALLENGE 3


CHALLENGE 4

The security issu

CHALLENGE 5

Managing the in

CHALLENGE 6

The need for ana

CHALLENGE 7

The cloud

CONCLUSION

SPONSORS

CONTACT

CHALLENGE 1

The complexityChris Svec,a Senior Principal Software Engineer at iRobot, is

used to working on complex embedded systems. So he wasappreciative of all the layers in a new IoT project he was recently

involved with. I think the thing that struck me most was how

many moving pieces there are with an IoT device, he says.

Svec points out that with the IoT, there are more concerns for

embedded engineers than just worrying about the firmware and

the device and how to update the device. An IoT design involves

many layers of decisions, and each decision triggers a cascading

set of consequences that can completely change the system

architecture. That requires more iterations.

I have to think about whether I want WiFi or Bluetooth. And if I am

not using video, then I dont need the bandwidth so it should be

okay to use Bluetooth. But I cant use Bluetooth and connect to theInternet without another WiFi chip in the mix. And then I have to

think about the Internet side of things and how my data is going to

be stored and processed--on a dedicated server, in the cloud and so

on, explains Svec.

Its enough to trigger a migraine. Svecs advice for engineers who

are new to the world of IoT is this: Choose a simple end-to-end

system, for example a basement water leak monitoring system,

using any of the open source hardware tools available. Thats what

he did.

I found out that you could actually prototype something fairly easily and get a reasonable amount of functionality done

quickly with a board like an Arduino, he explains. And youll build something that works and looks complete, even though

youre not going to be able to actually manufacture and sell it or anything.

The power of working on a real-world hobby project is that an engineer will gain hands-on experience in

defining the architecture and wrestling with the associated trade-offs in a situation where the stakes are low.

I found out that you could actuallyprototype something fairly easily

and get a reasonable amount of

functionality done quickly with a board

like an Arduino...

Please indicate Embedded Technologies you workwith, are expecting to work with in the future, or donot expext to work with.Q

These are justa list of typical

technologies with

embedded plusIoT and there are

many more!

Source: 2015

Sensors MagazineEmbedded Survey

SINGLEBOARDCOMPUTERS SBCS

INTERFACEBOARDS

SIGNALCONDITIONING BOARDS

DATAACQUISITIONDAQ BOARDS

DISPLAYS

OFFTHESHELFSOFTWARE

COMPONENTS

NETWORKING, IT, ISP

SECURITY

CUSTOM DEVELOPEDSOFTWARE

CUSTOM DEVELOPEDHARDWARE

IMAGE SENSORS,CAMERAS, OR

CAMERA MODULES

PROCESSORS

FPGAS

MICROCONTROLLERS

W or k w it h E xp ec t t o w or k w it h D on t ex pe ct to w or k w it h


4/12

Sponsored by:

Produced by:



INTRO

CHALLENGE 1

The complexity

CHALLENGE 2

The interdisciplin

CHALLENGE 3


CHALLENGE 4

The security issu

CHALLENGE 5

Managing the in

CHALLENGE 6

The need for ana

CHALLENGE 7

The cloud

CONCLUSION

SPONSORS

CONTACT

CHALLENGE 2

The interdisciplinary skills required

...projects require a huge diversityof knowledge that engineers have to

pick up to be successful...

Which of the terms below best describeswhat you do?Q

While engineerstoday arebeginning to pick up both

hardware and software skills, in

the not-so-recent past, the roles

and responsibilities of engineers

were relatively narrow. An engineer

who just did embedded software,

for example, just did embedded

software. That engineer did not

have to worry about things like

applications or connectivity.

Engineers had to do that thing they

did really well, which was to make

sure that the system came out ofreset, detected faults and recovered,

and performed reliably, says Matt

Liberty, President of Jetperch LLC, a

DSP, FPGA and embedded software

consultancy firm.

A lot of these IoT devices are smallcompared to a typical embedded

system, say like one used in test

equipment. Yet, something like LED

lighting is incredibly complicated--

projects require a huge diversity of

knowledge that engineers have to

pick up to be successful, he stresses.

Theres back-end issues too, as well

as connectivity, privacy, and security

concerns that when combined

together quickly thrust many

engineers into foreign territory.

Compounding the problem is the

fact that engineering team sizes have

been decreasing, forcing engineers

to pick up even more skills that are

not in their domain expertise. Couple

that with time-to-market pressures,

which have always been an issue for

embedded developers and are just

as prevalent with IoT devices, and

one cant help but wonder how any

engineer can keep up.

Liberty points out that because

microcontrollers have gone from8-bit to full 32-bit machines that

are better than the early PCs and

consume just a fraction of power,

there is an opportunity now to do

things that have not been possible

before. The technology is all there.But in the big rush to get products

to market, I think what is being lost

a lot of the time is the really strong

engineering. And thats because its

hard, says Liberty.

He believes that engineers need to

remember that they will still need

to deal with all the usual issues such

as buffer overflows and uninitialized

memory, and strive to develop safe,

secure, and reliable productseven

if those products are simple in nature.

Of course, that should be a no-

brainer for embedded developers,

who are used to working to such

exacting requirements. But non-

embedded types are likely to be

frustrated by the skimpy memory

and power resources available.

As far as gaining new skill sets, theres

no one easy answer. Liberty says that

he himself is constantly challenged

to learn new things, while at the

same time focusing on his day job. I

think that the key for any engineeris to learn as much as you can in the

areas that you are interested in. But

not to try and go too deep with too

many topics because youll lose s ight

of the bigger issues.

SOFTWAREENGINEERING

HARDWAREENGINEERING

BOTH HARDWARE ANDSOFTWARE

ENGINEERING


This is a subset of the entire respondents


5/12Sponsored by:

Produced by:



INTRO

CHALLENGE 1

The complexity

CHALLENGE 2

The interdisciplin

CHALLENGE 3


CHALLENGE 4

The security issu

CHALLENGE 5

Managing the in

CHALLENGE 6

The need for ana

CHALLENGE 7

The cloud

CONCLUSION

SPONSORS

CONTACT

CHALLENGE 3

The need to understand datasheets

What types of sensors do you use?QAdvanced sensors today offer powerful new capabilities fordesigners of IoT devices. But the more capable sensors become,

the more complex the interfaces. And that can mean spending

more time reading datasheets, something software engineers

arent necessarily comfortable doing.

You can search the web for all kinds of things. There is

information out there on how to normalize a database or figure

out how HTTP works. But, there is very little on how to read a

datasheet. And, you need to read the datasheet to figure out

how the hardware works, says Michael Anderson, C TO and Chief

Scientist for The PTR Group, Inc. He has over 35 years experience

in the embedded and real-time computing industry.

Time and time again, I am dealing with mid- or even seniorlevel- software engineers who dont really understand how

things like registers or caches work, and often they dont

understand how to read a datasheet or a timing diagram. If

thats the case, then they cant understand how to program the

device to make sure that it functions correctly. And, the closer

they get to the sensor the more likely they are to get into these

hardware-related issues, explains Anderson.

One of the problems Anderson sees for engineers who deal with

sensors is that their use in the field at the edge is all over the

map in terms of duty cycles. You have some sensors running

continuously, say monitoring the motor vibration. And then

you have more periodic situations, like growing a field full of

lettuce and you want to know whether you should turn on thesprinklers. You probably only need that data a few times a day.

In an ideal world, someone has already read the datasheet

and written a software library for the particular application.

What every engineer would like to do is take an open-source

library for something like the Arduino, look at the source code,

look at the datasheet, and figure out how the individual who

wrote the library interpreted the datasheet and turned it into

code, describes Anderson.

What a lot of us end up doing, he adds, if we dont want

to take the time to read the datasheets is to see if there is a

software library and just grab the source code, as long as its

legal to do so of course!

For engineers who need to come up to speed on reading

datasheets, Anderson suggests taking a simple single board

computer and sensor that has a software library already written

for it. The job then is to look at the library and make the sensor

work, but change up some things. For example, if the sample

library for an accelerometer runs 2X gravity mode, then run

it in 16X gravity mode. You might discover that one of the

downsides of this is that, because of the resolution, it gives you

13 bits worth of data instead of 8 and it comes out i n the wrongendian format, which means you have to flip the bytes.

Again, better to learn to do it on a hobby project than

in a real world application where speed and/or safety is

everything.

Wireless

44%Source: 2015 Sensors Magazine Embedded Survey

ACCELERATION

ACOUSTIC/ULTRASONIC

CHEMICAL/GAS

DISPLACEMENT

ELECTRICAL PROPERTIES

ENCODERS/LVDTS

FLOW

FORCE/STRAIN/LOAD/TORQUE

HALL EFFECT

INFRARED DETECTORS

LEAK/LEVEL

MAGNETIC

MOISTURE/HUMIDITY

MOTION/VELOCITY

OPTICAL

PIEZOELECTRIC/RESTRICTIVE

POSITION/PRESENCE/PROXIMITY

PRESSURE

RADIATION

SAFETY/SECURITY

SPEED

TEMPERATURE

VIBRATION

WIRELESS


6/12

Sponsored by:

Produced by:



INTRO

CHALLENGE 1

The complexity

CHALLENGE 2

The interdisciplin

CHALLENGE 3


CHALLENGE 4

The security issu

CHALLENGE 5

Managing the in

CHALLENGE 6

The need for ana

CHALLENGE 7

The cloud

CONCLUSION

SPONSORS

CONTACT

CHALLENGE 4

The security issuesQ

Security may not be top of mind for everyengineer who is developing connected

devices. But every device that talks all the way

to the cloud is a potential access point; entire

sensor networks chatting on the Internet

create a huge attack surface.

The IoT will become the playground of

the cybercriminal, predicts Jonny Doin,

Founder and CEO, Gridvortex Systems. With

over 25 years of experience in developing

systems, Doin says, Exploiters will be able

to compromise very small things in an

orchestrated way. In fact, this is already taking

place--just imagine a massive attack on somevery easy things to compromise, you can

imagine all kinds of scenarios for science

fiction movies.

In todays connected world, virtually every

system that surrounds us is connected with

another system, upstream or downstream.

If those systems fail and send the wrong

information downstream or the wrong

state downstream or the wrong feedback

possibly due to a security breach--dangerous

situations can be created.

The challenge is that with things loaded withsensors, the perception of what is the threat

level and what is the hazard level of those

failures is extremely difficult to know, said

Doin. When you are dealing with a generic

sensor that is capable of behavior, it has

intelligence, how can you attribute a criticalityor a hazard function to that sensor?

The only acceptable approach, he argues, is

that the designer of the thing should design it

as if it would be a live threat in the device. Its

firmware should be designed to be as robust

as possible to counter cyber attacks.

Other steps like actively authenticating the

communications of this sensor to the cloud

and to peers at all levels, as well as encrypting

information stored inside the node can help

deter would-be cyber attackers.

The technological conundrum that the

designers are facing right now is that they

dont even perceive the threat of these

so-called non-functional requirements in

software and hardware developments,

Doin says.

He argues that engineers must transform

requirements from non-functional to

functional requirements in order to ensure

the safety and security in all things, because

you dont always know where the sensor will

be used in the system.

Josh Thomas, a Security Researcher with

a background in advanced software

development, advises engineers to step back

a couple of levels and look at the architecture

they are designing and how they are

designing it. At that level, you can start seeinglogical flaws in what you are doing, Thomas

explains.

He knows what hes talking about. A

Founding Partner and Research Scientist at

the computer and network security firm,

Atredis, he describes what he does this way:

I used to write hard things and now I enjoy

breaking them.

Engineers make design decisions like, Lets

just put a web server inside the coffee maker

were building, because it is the easiest way

to solve the problem, he says, But they doit without thinking about the implications of

that decision or thinking about other ways

to achieve connectivity without throwing

their device directly into the big, wide, open

Internet.

Like every other design decision, Thomas

argues that security is not a zero or a

one. Rather, it is a set of trade-offs and

compromises made in the face of the

business drivers for the product and the cost

and resources it takes to design in a particular

level of security.

His advice? When it comes to security,

engineers should be constantly

analyzing their designs and determining

what level of security is good enough for

a particular product.

Indicate what EmbeddedTechnologies you work with, areexpecting to work with in the future,or do not expect to work with.

SINGLEBOARDCOMPUTERS SBCS

INTERFACE

BOARDS

SIGNALCONDITIONING BOARDS

DATAACQUISITIONDAQ BOARDS

DISPLAYS

OFFTHESHELFSOFTWARE

COMPONENTS

NETWORKING, IT, ISP

SECURITY

CUSTOM DEVELOPEDSOFTWARE

CUSTOM DEVELOPED

HARDWARE

IMAGE SENSORS,CAMERAS, OR

CAMERA MODULES

PROCESSORS

FPGAS

MICROCONTROLLERS

Source:2015 Sensors

MagazineEmbeddedSurvey

W or k w it h E xp ec t t o w or k w it h D on t ex pe ct t o w or k w it h


7/12

Sponsored by:

Produced by:



INTRO

CHALLENGE 1

The complexity

CHALLENGE 2

The interdisciplin

CHALLENGE 3


CHALLENGE 4

The security issu

CHALLENGE 5

Managing the in

CHALLENGE 6

The need for ana

CHALLENGE 7

The cloud

CONCLUSION

SPONSORS

CONTACT

CHALLENGE 5

Managing the interfaces

Embeddedconsultant, Jacob Beningo, has oneimportant rule when it comes to designing an IoT

device: Whenever possible, choose sensors that

have a standard interface.

A Principal Consultant at Beningo Engineering,

a firm that focuses on embedded software

development and safety critical systems, he stresses

that unless there is a very specific need to use a

sensor with a non-standard interface, just dont.

Of course there are always projects that require

a cutting edge sensor that provides a unique

functionality and developers are racing to be first to

the market. But theres a penalty associated with it.

Ive worked on a couple of projects where

the engineers chose a custom sensor that had

a specialized interface for connecting to the

microcontroller, says Beningo. But there was no

code or drivers associated with it, in fact nothing

was provided by the sensor manufacturer. They

basically wound up reinventing the wheel, probably

along with a bunch of other companies.

On the flip side, projects tend to go much more

smoothly when using sensors with a standard

interface. The supplier will typically provide code

and drivers. If that is the case, engineers can simplyaccess the API, freeing themselves up to focus

on what truly differentiates the product in the

marketplace.

Fortunately, the world is becoming morestandardized--with I2C and SPI being two of the

most popular interfaces. And silicon vendors are

making the bare metal interface as simple as an

engineer could possibly hope for. But its still not

easy.

I2C and SPI Interface Samples

Engineers today not only need to know both hardware and software, they have to understand theintersection between those two in a way that was not required in the past, said Michael Anderson. Its not

as simple as, Okay, I am going to plug this USB device in and this is goin g to work. Its really forcing theissue of engineers having to spend the time to understand how the hardware functions and understand

the timing of the hardware.


Q How do you view your interfaces?HARDWARE

SOFTWARE

BOTH


8/12

Sponsored by:

Produced by:



INTRO

CHALLENGE 1

The complexity

CHALLENGE 2

The interdisciplin

CHALLENGE 3


CHALLENGE 4

The security issu

CHALLENGE 5

Managing the in

CHALLENGE 6

The need for ana

CHALLENGE 7

The cloud

CONCLUSION

SPONSORS

CONTACT

CHALLENGE 6

The need for analog

Evenfor analog engineers, analog is not an easy discipline to grasp; many engineers describeit as more of an art than science, a kind of engineering black magic.

But since the world is an ugly, noisy, drifty place that sensors interact with, engineers

designing for the IoT are being forced to deal with analogoften when they would prefer

not to.

Unfortunately, analog expertise isnt exactly something an engineer can pick up on the

weekends or by doing a hobby project. Stories routinely circulate about analog engineers

being lured out of retirement to work on projects because of the rarity of their skills.

This business is demanding more and more of engineers who know the disciplines of

traditional embedded stuff, says Jack Ganssle, an internationally recognized Embedded

Systems Engineer, Author and Speaker.

One of the particular challenges I see today is a consequence of the fact that you can buy a

nice sensor for almost nothing, says Ganssle. Fantastic! But with some of these sensors, you

have to know a fair amount of analog electronics like the use of log amps [a circuit that can

handle large dynamic ranges]. That technology is going to be outside of the comfort zone of

not just about every digital person, but many analog engineers who have never had to deal

with them.

Optical data, since it tends to have a huge dynamic range, is particularly problematic. It

means that an engineer has to do something ugly like log compressions before digitizing the

data, and then may have to do antilogs to restore the range, emphasized Ganssle. To do an

antilog in code is no fun. Its worse when the use of floating point isnt an option, perhaps for

speed constraints or for limited memory.

The situation is exacerbated by the fact that projects today get rushed. Engineers may takeanalog data into the processor without being sure of how to process that data or knowing

and understanding the algorithms necessary to extract meaningful information from it (the

exception may be firmware engineers, many of whom are EEs and generally have a good

math background).

Ganssle points to the fairly simple example of a bathroom scale. How do you know if its

right? Load cells are not always linearwill everyone trying to develop a weight tracking

app worry about that? Some will and some maybe wont, because you have to correct for

that non-linearity in the software. That takes a fair amount of testing, maybe even over a

temperature range. And some sensors need calibration how will the engineers handle

that?

One of the particular challenges I see today is aconsequence of the fact that you can buy a nice sensorfor almost nothing...


9/12

Sponsored by:

Produced by:



INTRO

CHALLENGE 1

The complexity

CHALLENGE 2

The interdisciplin

CHALLENGE 3


CHALLENGE 4

The security issu

CHALLENGE 5

Managing the in

CHALLENGE 6

The need for ana

CHALLENGE 7

The cloud

CONCLUSION

SPONSORS

CONTACT

Whenit comes to

connecting to the

Internet, the big issue

that I see is that a lot of

embedded engineers

dont have experience

with Wi-Fi or Bluetooth

or even Zigbee, says

Beningo. Its completely

unfamiliar territory that

they are struggling to navigate while at the same time theyre

under pressure to get the product out the door.

For engineers more familiar with embedded systems there

is yet another wrinkle. If you have an unconnected device,

everything happens in the hardware, says Beningo. As soon

as you have a connected component, you have to choose

to do none, or some, or all of the data processing on the

actual device or do the computation and the processing

and analytics in the cloud or some server in your computer

warehouse.

Offloading more processor chores to other parts of the

system frees up designers from having to worry about the

constraints of what often is a li ttle, cheap device. But it does

add a second piece to the puzzle that needs consideration.

Adrian Fernandez, a Microcontroller Customer Experience

Manager at Texas Instruments, sees more choices in where

the processing gets done as a benefit to developers. Lots of

applications rely on the core duty cycle of an MCU, and now

that we have the smarter sensors and the cloud I see it asmore knobs that engineers can turn.

He points to the example of an intelligent sensor device

that can do a little bit of preprocessing, which eliminates the

need for the MCU to wake up. And if I can do a little more

math on the sensor maybe that means I can minimize or

limit the need to poke the MCU with new data to process,

he explains. And maybe I can also minimize the number of

times that I send data up to the cloud, which means less Wi-Fi

transmission. There are so many more options.

Engineers develop skills in doing that kind of trade-off

analysis and managing the consequences of the decisions

they make through time and experience. In an ideal world,

Beningo recommends that engineers should find someone

who has worked on an IoT system and is willing to talk

through the step-by-step process of not just the what of the

software and hardware components, but also the why.

Understanding how others have worked through a design

and their thought process, in a sense looking over their

shoulder, is one of the most important ways that engineers

learn, says Beningo.

In addition, he says a multi-pronged attack is the best

approach for maintaining relevant engineering skills today.

Acquire a very high-level understanding over the whole

broad area so you have a basic understanding of the IoT

protocol, sensor interfacing and connectivity. But in the areas

where you are most knowledgeablesay low-level drive

development and interfacingmaintain the expertise to do

a deep dive into the details.

Q What types of sensors do you use?

Wireless

43%

CHALLENGE 7

The cloudACCELERATION

ACOUSTIC/ULTRASONIC

CHEMICAL/GAS

DISPLACEMENT

ELECTRICAL PROPERTIES

ENCODERS/LVDTS

FLOW

FORCE/STRAIN/LOAD/TORQUE

HALL EFFECT

INFRARED DETECTORS

LEAK/LEVEL

MAGNETIC

MOISTURE/HUMIDITY

MOTION/VELOCITY

OPTICAL

PIEZOELECTRIC/RESTRICTIVE

POSITION/PRESENCE/PROXIMITY

PRESSURE

RADIATION

SAFETY/SECURITY

SPEED

TEMPERATURE

VIBRATION

WIRELESS



10/12

Sponsored by:

Produced by:



INTRO

CHALLENGE 1

The complexity

CHALLENGE 2

The interdisciplin

CHALLENGE 3


CHALLENGE 4

The security issu

CHALLENGE 5

Managing the in

CHALLENGE 6

The need for ana

CHALLENGE 7

The cloud

CONCLUSION

SPONSORS

CONTACT

Conclusion

Experienced embedded developers recommend the following:

1. Complete a sample, end-to-end IoT design in your spare time

2. Use devices with standard interfaces whenever possible

3. Leverage software libraries whenever possible

4. Complete a sample IoT project using a sensor with an existing

software library, but tweak the parameters

5. Maintain a broad and not too deep skillbase

6. Spend time to understand how the hardware functions and

understand the timing of the hardware

7. Hang out with engineers who have done an IoT project before

8. Learn to read a datasheet if you dont know how to already

9. Keep your skills relevant by scanning the Internet and publications,

going to conferences and shows, and getting some hands-on time

with hardware

10. Consider the security implications of your design decisions (puttingyour coffee maker on the world wide web, really?) and maintain a

balance in your business model and level of product security

10Things to Do to Succeed in the Era of the IoT

Whilethe IoT will require engineers to pay closer attention to power, analog, and systems connectivity, embedded developers should also consider taking a crash course in

data analytics. It may seem like a stretch, but the amount, type and frequency of data collec tion and communication directly affects system performance in terms of memory

requirements and power consumption, as well as the type of wired or wireless interface needed. I n addition, many organizations struggle with Big Data because it involvesstakeholders across the organization, many of whom may still operate in a siloed fashion. If you can add value to this discussion of the ultimate goals and objectives of a data

analytics initiativeand what data needs to be gathered and how oftenyou go from that person who assembles Lego blocks to give us our data to being seen as strategic data

partner with an end-to-end perspective and with a strong voice in the boardroom.

And as is true for engineers doing any type of designIoT or otherwisecontinuously scan news and information, learning is a lifelong endeavor: Take courses, go to conferences,

scan news and trends, read what you get your hands on in order to keep up with technology advancements, new ways of thinking, and the ever-evolving landscape of standards.


11/12

Sponsored by:

Produced by:



INTRO

CHALLENGE 1

The complexity

CHALLENGE 2

The interdisciplin

CHALLENGE 3


CHALLENGE 4

The security issu

CHALLENGE 5

Managing the in

CHALLENGE 6

The need for ana

CHALLENGE 7

The cloud

CONCLUSION

SPONSORS

CONTACT

Sponsored by:

Kionix, Inc., a ROHM Group Company and a global leader in MEMS inertial sensor manufacturing, offers high-performance, low-power

accelerometers, gyroscopes, and combination sensors along with comprehensive software libraries that support a full range of sensors,

operating systems and hardware platforms in the consumer, automotive, health & fitness, and industrial sectors.

ROHM, an industry leader in system LSI, discrete components and module products, leverages the latest semiconductor technologies and

utilizes a streamlined, completely in-house production system to ensure unmatched quality and provide the flexibility to respond to a wide

range of applications requirements in a variety of markets.

LAPIS Semiconductor, a ROHM Group Company, offers a wide variety of industry-leading IC solutions, from ultra-low-power 8bit/16bit and

ARM-based microcontrollers, communication ICs, speech synthesis ICs, and display drivers to ICs for battery monitoring, communication, and

audio/video applications. Services such as wafer foundry and WL-CSP assembly and testing are also offered.

2323 Owen Street

Santa Clara, CA 95054

2323 Owen Street

Santa Clara, CA 95054

408-720-1900

[email protected]

408-720-1900

[email protected]

36 Thornwood Drive

Ithaca, NY 14850

408-720-1900

[email protected]


12/12

For our 2016 Digital E-Book Series,is there research youd like to see?

Contact:

Mat DirijshExecutive Editor(718) 793-5501 [email protected]

Learn more by attending Sensors Expo & Conference

www.sensorsmag.com

MEMS

EnergyHarvesting Temperature

Chemical/ Gas

Position/Presence/Proximity

Acceleration/Vibration

Force/Strain/Load/Torque

Flow

Moisture/Humidity

Manufacturing

IoT

InstrumentalControl

Automotive

SpecialtyMarkets

Aerospace/Defense/Military

Process Industries

BuildingAutomation

Healthcare/Medical Devices/Pharmacy

Consumer

Electronics /Appliances

EmbeddedSystems

- 65+ Technical sessions

- Dedicated 2-day track onEmbedded Systems & Sensors

- 250+ best-in-class exhibitors

- Embedded Systems Pavilion

- Hands-on workshops

- And more!

Sensors Expo & ConferenceJune 21-23, 2016McEnery Convention Center | San Jose, Californiawww.sensorsexpo.com

In the heart ofSilicon Valley

new location!

New!

New!

New!

sensors and embedded systems in the era of the iot final e-book

Documents