Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.arch.embedded > #13857
| From | Don Y <this@isnotme.com> |
|---|---|
| Newsgroups | comp.arch.embedded |
| Subject | Re: Counting 2ms long pulses on several input pins |
| Date | 2013-09-24 11:03 -0700 |
| Organization | Aioe.org NNTP Server |
| Message-ID | <l1sk5d$ida$1@speranza.aioe.org> (permalink) |
| References | (2 earlier) <52412bde$0$15931$e4fe514c@news2.news.xs4all.nl> <l1rffo$37b$2@speranza.aioe.org> <52414c4e$0$15979$e4fe514c@news2.news.xs4all.nl> <l1sg5m$6it$1@speranza.aioe.org> <mLj0u.134853$Iu6.39313@fx31.am4> |
Hi Tom, On 9/24/2013 10:13 AM, Tom Gardner wrote: > On 24/09/13 17:55, Don Y wrote: >> [E.g., you're never completely sure you have returned the >> controller to the "full off" condition -- or, if you have just >> selected a slow blink pattern!] > > A terrible variant of that is my car's remote control. > > Click it and if it *changed* to open or locked, the lights > flash and you know its state. > > But if the lights don't flash you don't know whether > - you are too far away > - a door wasn't shut properly > - it in the desired state > > So, unless you see the lights flash, you have to try > the other state then re-try the state you want. Argh. IMO, this makes for a bad user experience. You don't want to have to *think* about trivial little actions like this. E.g., when we lift our *ringing* cordless phone off the cradle, it automatically answers. But, if the answering machine has already engaged, you must press the TALK button to be connected to the caller. So, you lift the handset -- and *hope*! "Hello?" Wait a while to see if the other party is there. If not, they are undoubtedly speaking to the answering machine and *you* just spoke to "dead air". Quickly press the talk button and reannounce yourself -- interrupting the caller in the middle of leaving a message, etc. Of course, it could be *worse*! Imagine if the TALK button served as the "on hook" (hangup) button, as well! You'd *always* be leary of pressing it for fear you *are* connected to the caller and pressing that button would hang up the phone! :< > Apart from that, the Mazda 2 has been remarkably > reliable, touchwood. But, this other behavior rises to a level where you are aware enough about it that it persists in your impressions of the vehicle! I'm sure Mazda would rather your comments have been *unconditional* praise (regardless of how "trivial" this other issue might be considered). My old TV was a delight! *But*, the MUTE function on the remote did not operate independently of the other functions. E.g., if you muted the volume and then changed channels, the mute was canceled. I.e., if you wanted to mute the TV and channel surf without sound (e.g., maybe you or someone else in the room is talking on the phone), you had to drive the volume all the way down to '0' -- where it would persist as you changed channels. So, in practice, you hit MUTE, changed channels, cursed because the mute was released and instinctively hit MUTE again. Paused as you recalled the "decrease volume" trick. Cursed again because pressing Volume Down automatically un-MUTEs the set (again). Wait for the volume to get down to '0'. *THEN*, start flipping through channels. Again, the conditional endorsement of the product: "a delight BUT..." Sort of like climbing Everest and then planting the flag *in* your big toe! Sure, you remember the satisfaction of the accomplishment. But, you also remember (and recount to others!) the hole you poked through your toe at the time! :-/ (which becomes the part of the story that folks MOST remember)
Back to comp.arch.embedded | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Counting 2ms long pulses on several input pins pozz <pozzugno@gmail.com> - 2013-09-23 23:42 +0200
Re: Counting 2ms long pulses on several input pins mike <ham789@netzero.net> - 2013-09-23 15:00 -0700
Re: Counting 2ms long pulses on several input pins Don Y <this@isnotme.com> - 2013-09-23 16:12 -0700
Re: Counting 2ms long pulses on several input pins Paul Rubin <no.email@nospam.invalid> - 2013-09-23 18:45 -0700
Re: Counting 2ms long pulses on several input pins Arlet Ottens <usenet+5@c-scape.nl> - 2013-09-24 08:06 +0200
Re: Counting 2ms long pulses on several input pins Don Y <this@isnotme.com> - 2013-09-24 00:37 -0700
Re: Counting 2ms long pulses on several input pins Arlet Ottens <usenet+5@c-scape.nl> - 2013-09-24 10:24 +0200
Re: Counting 2ms long pulses on several input pins Paul Rubin <no.email@nospam.invalid> - 2013-09-24 02:05 -0700
Re: Counting 2ms long pulses on several input pins Arlet Ottens <usenet+5@c-scape.nl> - 2013-09-24 11:01 +0200
Re: Counting 2ms long pulses on several input pins Don Y <this@isnotme.com> - 2013-09-24 09:55 -0700
Re: Counting 2ms long pulses on several input pins Tom Gardner <spamjunk@blueyonder.co.uk> - 2013-09-24 18:13 +0100
Re: Counting 2ms long pulses on several input pins Don Y <this@isnotme.com> - 2013-09-24 11:03 -0700
Re: Counting 2ms long pulses on several input pins Arlet Ottens <usenet+5@c-scape.nl> - 2013-09-24 19:38 +0200
Re: Counting 2ms long pulses on several input pins Don Y <this@isnotme.com> - 2013-09-24 11:13 -0700
Re: Counting 2ms long pulses on several input pins Arlet Ottens <usenet+5@c-scape.nl> - 2013-09-24 20:30 +0200
Re: Counting 2ms long pulses on several input pins Paul E Bennett <Paul_E.Bennett@topmail.co.uk> - 2013-09-24 21:20 +0100
Re: Counting 2ms long pulses on several input pins Don Y <this@isnotme.com> - 2013-09-24 16:08 -0700
Re: Counting 2ms long pulses on several input pins Don Y <this@isnotme.com> - 2013-09-24 00:34 -0700
Re: Counting 2ms long pulses on several input pins Andrew Smallshaw <andrews@sdf.lonestar.org> - 2013-09-24 04:31 +0000
Re: Counting 2ms long pulses on several input pins Paul E Bennett <Paul_E.Bennett@topmail.co.uk> - 2013-09-24 11:15 +0100
Re: Counting 2ms long pulses on several input pins Paul <paul@pcserviceselectronics.co.uk> - 2013-09-24 15:51 +0100
Re: Counting 2ms long pulses on several input pins pozz <pozzugno@gmail.com> - 2013-09-25 00:33 +0200
Re: Counting 2ms long pulses on several input pins Don Y <this@isnotme.com> - 2013-09-24 16:36 -0700
Re: Counting 2ms long pulses on several input pins pozz <pozzugno@gmail.com> - 2013-09-25 07:39 +0200
Re: Counting 2ms long pulses on several input pins Don Y <this@isnotme.com> - 2013-09-24 23:37 -0700
Re: Counting 2ms long pulses on several input pins pozz <pozzugno@gmail.com> - 2013-09-27 15:54 +0200
Re: Counting 2ms long pulses on several input pins Don Y <this@isnotme.com> - 2013-09-27 12:35 -0700
Re: Counting 2ms long pulses on several input pins mike <ham789@netzero.net> - 2013-09-24 16:43 -0700
Re: Counting 2ms long pulses on several input pins j.m.granville@gmail.com - 2013-09-24 17:32 -0700
Re: Counting 2ms long pulses on several input pins Tauno Voipio <tauno.voipio@notused.fi.invalid> - 2013-09-25 09:52 +0300
Re: Counting 2ms long pulses on several input pins Don Y <this@isnotme.com> - 2013-09-25 00:09 -0700
Re: Counting 2ms long pulses on several input pins j.m.granville@gmail.com - 2013-09-25 16:53 -0700
csiph-web