After reading your 'Meep' blog, I cannot stop thinking in a chapter of the Simpsons -- yes, I know I've a problem... I watch too much TV!!
In a chapter called "The Wizard of Evergreen Terrace", Homer tries to emulate Thomas A. Edison and develops some crazy inventions. One of them is an alarm that beeps every three seconds when everything is alright... so maybe this can solve the isolated 'meeps' in the night issue ;-)
@Caleb: I've actualy seen a device that will give you a nice little "meep" at random intervals. It is meant to be hidden as a prank and since it is somewhat random it is very hard to locate
It's the Anoy-a-tron from Think Geek -- it really is diabolical, you can attach it to a the back of a filing cabinet via its magnet -- thereby making it louder and even harder to find. A bargain at only $9.99
@Max: @DMcCunney: Go ahead. Unwrap it. Pass the jeans back to me on my birthday. Bet you can't... Hmmm, I wonder what my brother would say if I did something like this to him.
Something not printable in a family publication like EETimes?
Do it and report back...
As it happens, though, I had a "meep" moment last night. Something meeped in my general area. Let's see, What was it? My main cell phone? Nope. My secondary cell phone? Nope. My PDA? Nope. My SO's primary cell phone? Nope. The desktop under my desk running Ubuntu? Couldn't be. That's turned off at the moment. My SO's secondary cell phone? Nope, she gave that to a worthy charity and hadn't mentioned it to me. The laptop she was using at the time? Nope. She would have noticed and it wasn't in my general area. The pre-owned Nook Tablet that recently joined the family? Nope. While I think it can meep, it's not yet configured to. We both prefer machines that don't speak until spoken to.
I finally muted the sound globally on the machine I'm on at the moment and things were quiet, but I still can't be sure just what was meeping...
What are the engineering and design challenges in creating successful IoT devices? These devices are usually small, resource-constrained electronics designed to sense, collect, send, and/or interpret data. Some of the devices need to be smart enough to act upon data in real time, 24/7. Are the design challenges the same as with embedded systems, but with a little developer- and IT-skills added in? What do engineers need to know? Rick Merritt talks with two experts about the tools and best options for designing IoT devices in 2016. Specifically the guests will discuss sensors, security, and lessons from IoT deployments.