Archive for December, 2014

h1

Hackaday: Wordy

December 9, 2014

I wanted to make build instructions for Wordy but since it uses both SparkFun and Adafruit parts, I couldn’t decide where. Though I did say I was going to put my next project up on Hackaday. I did that. There is a link to the code there as well as build instructions. Anyone here want to check it out for me? Maybe suggest what I forgot?

Wordy Ring

One thing already on my list is a project log of different ring making methods I tried. I’m going to do another pass with Sculpey, taking pics as I go. I also need a final picture of it all together, I plan to take that when I wear it out tonight.

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

Giant rings are IN, right?

December 3, 2014

I finished up the working modes of my ring, so rev1 of the software is done. Here’s what it does:

On TAP: shows a vocabulary word. On tap or double tap, shows definition.

On DOUBLE TAP: starts Pong game, paddle position set by tilt of accelerometer.

On UPSIDE DOWN SHAKE: says to consider a question, waits for upside down shake (or punch) to give a response.

On PUNCH: puts up a punch word and a couple rectangles for emphasis.

As long as the wires are secure, this all works pretty well. I still need to format some of the Magic 8 ball style responses. And I could go through the vocabulary words to make shorter (better) definitions. I can probably pick up about 50 words too (yay!). I may continue to get rid of nonsensical floating point stuff so I can put more definitions in. Oh, and I should check the power usage, I didn’t minimize the accelerometer’s draw.

However, those tweaks can all wait as I need to make it wearable again. The button version was wearable but the ring blanks from that are a little too small for the accelerometer+battery stack up.

microView with accelerometer and battery

From another angle

MicroView, accelerometer and battery

 

On the back of the MicroView is a dab of funtac (that stretchy sticky stuff you might have used to hang posters in your dorm room), a modified Adafruit 5V tolerant MMA8451 board (ahem, they didn’t need all that space for logos and mounting holes). Tiny wires are soldered to the board, then hot glued. On the other side, they are soldered to the MicroView.

On top of the accelerometer is a SparkFun 40mAh LiPo battery with its connector snipped. It is held on to the accelerometer with funtac (sometimes I build things entirely from funtac). I needed the battery on the outside so I can remove it for charging. The

This all stacks up higher than I wanted and doesn’t leave much space for attaching the ring to the device. With the button+battery version of the ring, I pressed the MicroView pins into the ring blank and press fit it all together. That doesn’t work so well now, especially as the poorly pressed fit doesn’t hold the power on.

Add connectors

 

I snipped some jumper wire so I could build a connector on the inside of the ring blank. This was just a trial run. It worked out ok but I think I want to do something a little different for the real ones, maybe destroy 8 wires to get 16 connectors. Having attachments only on the pins of interest has some downsides (especially if I don’t line them up properly). More connector ends also lets me add some needed rigidity. Even these few fix the press fit problem. The female connectors are all too bulky though I may look around some more.

Ring on

 

It doesn’t look too bad. Though I think the new black version are going to be better (still waiting for those to dry).

photo 4

Well, let’s see it on!

OnThe 5s timeout on the screen makes it impossible to get an in-focus shot by myself.  Ahh well, you get the idea. This angle is probably the nicest. From the side where you can see the stackup, not so nice. (Realistically, it wouldn’t be hard to cover this.)

head on

But I can’t leave it on that shot, one more, a little prettier.

Sideview

h1

Stuff I need

December 2, 2014

I know, I write this blog so people can read it. But then I hope only my husband reads it. Which he does but usually only after I’ve told him about whatever I wrote.

Anyway, I find myself going to the same pages a lot. I figure I can reduce my tabs by putting a few links here:

Yeah, I’m still working on my little ring. With a tap, it gives a word. Another tap, the definition. With a double tap, it starts pong (you tilt your hand to move the paddle). Another double tap (or win/lose), pong ends.

Today I hope to use the motion thresholds on the MMA8451 to detect when you turn your hand upside-down and shake (ahem, ask me a question!). I’ve already got the answer strings in there and I’m using 27166 bytes, out of 32k. Though I’m down to 100 words (instead of the 200 I started with).

Better get to work now that I can close some of these tabs.