Posts Tagged ‘future’

h1

Call for Proposals

December 4, 2014

The embedded systems conference (finally renamed the “Embedded Systems Conference”, yay!) and O’Reilly’s Solid conference have opened their call for proposals (Solid’s and ESC’s). After telling everyone that I’m tired of giving conference presentations, tired of attending conferences without talks that I want to see, that presentations take way too much time to prepare, presenting leads to no goodness for me, I have nothing to talk about, and I have way more fun (and reach more people) on the podcast, I’ve put in three proposals.

Faker to Maker in 30 Minutes

The Maker revolution is obviously here.

What does that mean for those of us who aren’t Makers? We worked hard for these engineering degrees and now sometimes feel daunted (even intimidated?) by the free sharing, open source, do anything, tinker in their obviously copious spare time hackers.

Wait, weren’t hackers the bad guys? (Sometimes, semantics change.)

Will there still be a space for careful, professional engineering? (Hint: yes.)

Most importantly, how can we join forces to get the best of both worlds?

Low Power Strategies for Wearables (and Everything Else)

Sleep early and often. Reduce your clock speed. Turn off your IOs and unneeded subsystems.

Excellent tactical advice only goes so far, this talk will help you understand how to architect software to reduce power usage. Focusing on ST’s Cortex-M0 and Atmel’s ATMega328, Elecia White will describe how to start from a clean slate to get great results and how to utilize some of these techniques on to existing code bases.

Intro to Inertial Sensors: From Taps to Gestures to Location

What is the difference between an accelerometer, a gyroscope, and a magnetometer? What would you use each for? If you aren’t sure, let me explain.

The entertaining host of the Embedded.fm podcast, Elecia White will explain the differences and each sensor’s best uses, on their own and in combination. She will detail the most common ways to put them together and help you determine which are the best choices for your products.

The talk will discuss how to replace buttons with accelerometers, how that leads to gesture recognition, and why integrating to get location is a more difficult problem that it sounds. While you might not be able to implement a Kalman filter by the end of the talk, you will know why it matters.

***

What do you think? One fluffy and two technical. I had a third technical one but it seemed like an awful lot of prep work:

How to Choose a Micro for Your Application

Price, performance, and power war for supremacy. We all want the cheapest, lowest-power processor for our application. But at the beginning of development, we may not know how much performance we truly need. Choosing the wrong processor may lead to a complete redesign, a time to market disaster. How to estimate which family of processors is the best for your application?

Unaffiliated with any chip or compiler vendors, Elecia White is an experienced embedded systems consultant and host of the Embedded.fm podcast. She will explain her methodology, using examples across consumer applications.

The talk will tackle such estimation issues as where to start if you need to run WiFi—that often means running an Ethernet (TCP/IP) stack which means you probably need an RTOS. If you need an RTOS, you probably don’t want an 8-bit ATMega (not that it isn’t possible, just that it isn’t likely to be timely). Start with a Cortex-M3 range and look for the next set of requirements. Power might push you down to a cramped Cortex-M0 or heavy processing might sends you up to the Cortex-M4 (or a dual processor DSP/C-M0 option).

There are tradeoffs everywhere; this road map will help you choose a path.

***

That one also seems like one hundred thousand ways to be wrong since someone will always disagree. I can offer my opinion but I’m sure to frustrate some developer with a crush on PICs. (Because PICs are my least favorite processor. I don’t know why you’d choose a PIC over an ATTiny or an MSP430. Ok, I said it. AVR Freaks unite!)

Anyway, the proposals have been submitted on the idea that I should want to speak, that I should do my part for women-in-tech (bleah), and that I want more listeners for the podcast (which I should remember to mention this time, not like the last presentation I gave, urk).

The proposal deadlines are Jan 9th and 12th so get yours in. I’m only going to the conferences if there is someone I want to see speak. Go propose something amusing and informative, please.

 

 

h1

Forecasting from the Tesla

September 15, 2013

C and I were driving to the beach yesterday and started talking about the future of technology. We don’t normally do this, while we will talk about clients in our off time, we don’t just gab about tech so this was special.

Here are some of the things we decided while driving about:

  1. Virtual reality is neat and it is really, truly, finally coming. I’ll be able to put on a helmet and see a different world, be able to put virtual objects in places and move through them instead of working in a two dimensional environment. Our brains are wired for this: we are supposed to live in a 3D world. When this happens, the whole world will accelerate (again) as we share our mindscapes with other people. Motion sensitive people beware (that would be me, I get carsick just by thinking about being in a car).
  2. Augmented reality, where you see the real world with information overlaid on it, is also coming. The physical world will become a playground, mashed up with our mental models. Google glass is dorktastic but only the start.
  3. To get AR and VR to really work, we need to interact with the items that are not really there. Haptic feedback must come soon, driven by the virtual environments. C wants a glove that will make him believe he is holding a tennis ball when he is wearing an Occulus Rift VR headset. We talked about balance muscle wires, small solenoids (to put pressure on the fingertips), and those bed of nails things you see at museum stores with actuators.
  4. The iphone’s new 64 bit architecture is strange and interesting. Why does it need that much computing power? What purpose does it serve?
    1. First, the oomph will make it more usable as an enterprise (and government) device. It has three factor authentication now (something you have: the phone; something you know: a password; something you are: your fingerprint… and probably your voiceprint).
    2. The new iphone 64 bit architecture is on the path to the phone replacing computers. Now all they need is a generic dock (one for work, one for home) that has a keyboard and display. Then all your computer information comes and goes with you, all the time. No more laptops. No more computers. Your phone is everything, including your ID.
    3. Finally, the additional iphone computing power comes into play as a game console (like Wii, Playstation, even PCs). Add a game controller, plug the iphone into your TV, and have a serious physics engine simulate a system with intelligent agents.
  5. Energy harvesting is neat. We used to have it with solar powered calculators but now our devices are too powerful (and power hungry). The harvesting technology is coming, probably over the next five years. I think it will hit consumers in augmentation of battery devices (making them last longer), not eliminating batteries entirely. We agree that energy harvesting is more interesting in small, pervasive devices; it is less interesting in large scale energy generation where more traditional sources will continue to improve (e.g. wind, solar).

 

We’ll see how these turn out. And what are we missing?

 

h1

Trip report: Shaping the Future of MEMS and Sensors

September 10, 2013

I went to STM's one day conference on MEMS and sensors. When C asked what I was expecting, I said I didn't know. I remember going to an Atmel mini-conf and got some neat technical information about their MCUs and a dev kit or two… but that was many years ago. Since this was less technical, less hands on, I figured I'd hear more about theory and future plans. I was still hoping for a dev kit. (I always hope for a dev kit. Even when I go to the grocery store.)

It was good that I didn't have a particular goal because it was nothing like what my unformed expectations were.

Taking a step backward, Karen Lightman and I got to talking at DesignWest this year. We've chatted a few times (once on my podcast) and she invited me to the MEMS Industry Group Executive Congress. I suppose I thought this event would be somewhat similar, a little less business focus but still a very “where is MEMS headed?” approach.

One thing I should mention is that this mini-conference was free to attend. And they fed us several times. It is at the Santa Clara Marriott which is a nice location (though I'm going to have a nightmare that involves the garish pattern of the rug). Cherche la femme. Except with money.

And yet, unlike the Atmel processor event, this has not been an overt advertisement. I'm having trouble describing what the conference has been like, hence the roundaboutness. Let me continue with what the day has not been:

  • It has not been very technical. A few sessions got into technical details but most were high level information, more like an introduction why wireless sensors are neat or how the MEMS industry has changed over time, particularly in the morning.
  • It has not been particularly future looking. (It is called “Shaping the Future”.) While there are some microfluidics actuators that I was unaware of, I haven't learned much about sensors that exist now (or that will exist in 3 months, 6 months, or 2 years.

Continuing my randomwalk to getting to the point, I misread the email and went to the Santa Clara Convention center this morning. I saw many tech people streaming in the building: backpacks, jeans, a few suit jackets, all men, mostly with bad posture. I wondered very briefly if I was in the right spot but it seemed like my normal sort of crowd so I followed them in.

 

I was wrong. The people here are more like VP of Engineering level or managers. There are application engineers and some development engineers (and consultants, ahem). There are more suites than jeans at this conference and very few backpacks (oops, though my blue backpack really is a lovely specimen of backpackdom). Shoes are mainly leather with very few sneakers, lots of nice heels. Oh, and lots of women. I don't know how they got such a good ratio but they did. Maybe MEMS has more women?

 

Anyway, these are the grownups. So why are they here?

 

The speakers seem to be trying to convince me that wireless sensors, sensor fusion, and wearable technology are important (and coming soon). Ummm… Some of that is already here, I know, I've shipped those products. For the rest, we've got all the pieces, we just need to figure out how to put it together, make it cheap and easy to use, and then ship it. I suppose I'm too tactical given that I already accept these proposed strategies.

I suppose if I wasn't already in this industry, maybe this would be new information to me. But I like MEMS sensors and I've been working with them for two different clients. And I do tend to try to be industry current and this is, I suppose, relatively current.

Still, the level of material is different from my normal conferences, not technical enough to satisfy me as an engineer and not future-looking enough to make me excited as an architect looking at far-off products. Maybe if I was more used to be only in the role of manager, this might satisfy a need to know what's new and likely to be on the schedule in the next year.

For the most part, the people I met were more interesting than the talks. But there were some good talks so let me start there.

My favorite talk was from Jon Kindred from Starkley. He spoke on hearing aids, the current technology and the future plans. He was not only a good speaker, I was jaw-droppingly interested in the technology contained in the tiny, tiny super power efficient, more smarts than my 1992 computer, in-ear-canal hearing aid. I meant to leave to go see another session but I stuck around after (even ambushed him later). So, that was good. I do so like looking at other peoples' technical underwear. And I'd love to work on that technology and application. And have him on my podcast.

I think my second favorite was from Alissa Fitzgerald. She designs custom MEMS sensors, particularly for medical applications. She talked about the risks of putting things in human bodies. I mean, the risks to the chips, a different perspective. I met Alissa doing the DesignWest sensors in health panel so seeing her talk was one of my main reasons to attend. Not disappoointed.

Finally, I enjoyed Michael Emerson's talk about Preventice, an Android phone connected EKG monitor. It made me think of the podcast with Dr. Edward White about medical technology. I wish I could get them to talk to each other (and let me listen).

As for the people, let me start with people I already knew. Mike Perkins was my boss' boss at HP (omg, that was so long ago) and then again at LeapFrog (that was still more than a decade ago). I wish he'd had his own session, I'd like to hear more about his opinions on the industry and his role at Neato Robot.

I also met Eric Wilson, my boss at the six-week, seldom-spoken-of stint at Steve Wozniak's Wheels of Zeus. I sat next to him at lunch, 75% confident it was him. He didn't recognize me. He seemed awkward about it though I felt it was funny.

Other people I met, I wonder if I'll meet them again at the MEMS Executive Council. Some of them, I think. Though that will be very business related, not technology related. I suspect that will be a very strange conference for me, outside my normal realm. I'm pleased to be going as an expert in shipping embedded products, I'm comfortable in that role though it isn't one I tend to introduce myself as.

I handed out my card, both book cards and Logical Elegance business cards. I'd love to work on hearing aids or something neat like that. But I didn't hear about a lot of super whizzy product using little-heard-of sensors. Maybe during the ending networking session.

 

 

h1

What I want from a watch

May 6, 2013

There is a lot of talk (and rumors) about watches.  I keep thinking “we don’t need no stinking watches”.

I like not wearing a watch. Having something on my wrist decreases ease of melding with my computer. I like the flow-state where it is just me and the bits, working together to make each other work.

Thus, if I was to give up my previous wrist space, it would have to be for a good reason.  It would not be a pedometer ( lives in my pocket), a GPS (lives on my phone), or a sports anything (lives nowhere on my person).

I’d consider a health monitor but I don’t think the technology is there. I’d want it to monitor core body temperature, heart rate, glucose levels, and blood pressure. Basically, it would be a wrist mounter tricorder. None of those are easy to do on the wrist (also, noninvasive was implied) so this seems like a pipe dream.

But I’m not completely unreasonable. I’d settle for an auxiliary screen for my phone. It would have to be light, more like one of those rubber cause wrist bands (i.e. livestrong) than a proper watch.

I’ve heard rumors of Apple and a slap band style. I could get into that. Say it is two inches wide and eight inches long. When flat, it could show me movies via, I dunno, Bluetooth (or BTLE). My headphones would plug into my phone so the wristband doesn’t need a jack. Though it could have one which would let me watch movies with someone, that’d be neat.

Given my goal “watch” is now about 2″ wide and 8″ long, the screen could be about 2″ x 4.5″ which would show movies in widescreen (16/9).

I could see using the wristlet in flat form as a display, using my phone’s screen for a larger keyboard. But I don’t have any problem with typing and seeing on my phone (most of this blog post was written on my phone).

When the wristlet is in coiled mode, it should show time and some chosen info from my phone: texts, emails from VIPs, tweets, etc. I’d like to be able to press something and say show me more and dismiss (also pause, forward, and back for movies). I don’t know if that means I need a touchscreen or just a few buttons on the end. With feature creep, I could see a stopwatch but I don’t really need a features I’ve got elsewhere.

I understand a lot of people are trying to make a wrist based phone and I can understand that. But even if they succeed, I don’t want that. How about instead of another me-too product, we get something really spiffy?

If you want my wrist, be innovative.

 

h1

I don’t know why she ate the fly

January 16, 2013

There is a guy crawling around my ceiling right now. On the upper side. And this is literal, not my usual metaphoric guy crawling around my head.

The guy is from a Solar City, he’s looking at the roof, at what would need to be replaced.  Because all or part of our roof will need to be replaced before we get solar panels. I’ve wanted solar panels for a long time. It just meets some check on the list of “living in the future”.

Solar City at our house

When we moved in to the house, they said the roof would last 3-5 years and need re-doing. That was 15 years ago and every year we wonder if THIS is the year. And every year, including this one, we call a roofer to check it out and they do a couple repairs then say it will last 3-5 years.

So why is there another guy planning to destroy the roof? We’ve been waiting to get solar until the roof went. But the tail is going to wag the dog a bit:

We want a new roof because we want solar. We want solar because if we get solar, the panel upgrade is free. We need a panel upgrade because 100A is not enough to run the oven, the microwave and the charging station. We need the charging station for the new car. We need the new car because we got the garage re-done.

 

Garage workspaceGarage floorGarage cabinets

No, that last part isn’t right. We got the garage re-done because of the new car. And because the garage was horrific but it is super nifty now. And the floor will match the new car.

Which we will get on Saturday. Hopefully.