🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: uk.tech.digital-tv
Article #54

Re: Using mobile phone as an internet radio

#54
From: George Herold
Date: Fri, 05 Oct 2012 20:01
58 lines
4129 bytes
On Oct 5, 2:51 pm, Jeff Liebermann <je...@cruzio.com> wrote:
> On Thu, 04 Oct 2012 10:03:21 -0400, Phil Hobbs
>
> <pcdhSpamMeSensel...@electrooptical.net> wrote:
> >> Yep.  As I understand it (possible wrong), AC filaments break in the
> >> middle, mostly from vibration flexing.
>
> >I don't think so, because there's no mechanism for that, as I said.  The
> >wire is fully annealed at all times, so there's no possibility of
> >progressive fatigue failure.
>
> Oscillating filament light bulb:
> <http://www.youtube.com/watch?v=t_DwwNVA-7Q>
> Whether the earths magnetic field is strong enough to induce such
> oscillations is questionable.
>
> While digging for the apparently mythical lifetime test data on
> incandescent light bulbs, I've found numerous theories on why
> filaments fail.

Grin,  the internet as a 'fire hose' of information.  I went searching
for something that contained "Philips tech. rev." and found a
reference to the following article,

H. Horster, E. Kauer and W. Lechner — The Burn-out Mechanism of
Incandescent Lamps Philips Technical Review 32,155-164, 1971.

It was referenced in "Illuminating Engineering - Page 32 - Google
Books"

But nothing about turn on failure... sigh.

Here is a patent by some of the same guys at Philips... lots of stuff
about the filament getting hottest in the middle.

http://www.freepatentsonline.com/3868159.html
(Actually a decently written patent.)

George H.



Tungsten evaporation, causing hot spots, is the most
> common.  One suggested that thermal cycling hardens the tungsten and
> makes it brittle.  Another suggested that the inrush current causes a
> mechanical shock if it hits at the 60Hz peak, instead of at the zero
> crossing.  Yet another speculates that the temperature differential
> between the hot filament, and the relatively cold mounting structure
> may cause cracking.
>
> --
> Jeff Liebermann     je...@cruzio.com
> 150 Felker St #D    http://www.LearnByDestroying.com
> Santa Cruz CA 95060http://802.11junk.com
> Skype: JeffLiebermann     AE6KS    831-336-2558

G
Technical Details
Message-ID: <ac87ddc4-2dc8-4d5e-a9ba-37d9465c0232@n9g2000yqn.googlegroups.com>
Path: arc1-ca.pugleaf.net!e10ni211270746qan.0!nntp.google.com!l8no27099315qao.0!postnews.google.com!n9g2000yqn.googlegroups.com!not-for-mail
References: <k4fn6h$1op$1@dont-email.me> <506b63ab$0$9840$607ed4bc@cv.net> <k4fq2l$ibq$1@dont-email.me> <506b7140$0$6053$607ed4bc@cv.net> <3atm68dko3vnjog3qfdrqeae6n39tf8kns@4ax.com> <ad1bkkF7pm9U1@mid.individual.net> <0ae7fdaf-9a45-4fd5-8800-9a6588a7f7f3@q4g2000vbg.googlegroups.com> <52d8ca03e8dave@davenoise.co.uk> <pcGdnWBMII4H0fHNnZ2dnUVZ_qudnZ2d@supernews.com> <q8kp68d48ekuj6fvlf411e2n20f14tbcdd@4ax.com> <E9WdnXGgld20CvDNnZ2dnUVZ_qCdnZ2d@supernews.com> <mu9u689h9q1o9p2l01umiri47o74l4m0pg@4ax.com>

Show Full Headers
Complete Article Headers
X-Google-Thread: b846822590,9bee37cb532a5f52
X-Google-Attributes: gidb846822590,public,usenet
X-Google-NewGroupId: yes
X-Google-Language: ENGLISH,CP1252
Received: by 10.224.70.131 with SMTP id d3mr8139714qaj.0.1349467272622;
        Fri, 05 Oct 2012 13:01:12 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.236.109.233 with SMTP id s69mr1226918yhg.11.1349467272536;
 Fri, 05 Oct 2012 13:01:12 -0700 (PDT)
Path: arc1-ca.pugleaf.net!e10ni211270746qan.0!nntp.google.com!l8no27099315qao.0!postnews.google.com!n9g2000yqn.googlegroups.com!not-for-mail
Newsgroups: uk.tech.digital-tv,24hoursupport.helpdesk,uk.telecom.mobile,sci.electronics.basics,sci.electronics.repair
Date: Fri, 5 Oct 2012 13:01:12 -0700 (PDT)
Complaints-To: groups-abuse@google.com
Injection-Info: n9g2000yqn.googlegroups.com; posting-host=129.44.255.154; posting-account=_kLX7QoAAAChyHRjRDyv2ieHnlQ_-li2
NNTP-Posting-Host: 129.44.255.154
References: <k4fn6h$1op$1@dont-email.me> <506b63ab$0$9840$607ed4bc@cv.net>
 <k4fq2l$ibq$1@dont-email.me> <506b7140$0$6053$607ed4bc@cv.net>
 <3atm68dko3vnjog3qfdrqeae6n39tf8kns@4ax.com> <ad1bkkF7pm9U1@mid.individual.net>
 <0ae7fdaf-9a45-4fd5-8800-9a6588a7f7f3@q4g2000vbg.googlegroups.com>
 <52d8ca03e8dave@davenoise.co.uk> <pcGdnWBMII4H0fHNnZ2dnUVZ_qudnZ2d@supernews.com>
 <q8kp68d48ekuj6fvlf411e2n20f14tbcdd@4ax.com> <E9WdnXGgld20CvDNnZ2dnUVZ_qCdnZ2d@supernews.com>
 <mu9u689h9q1o9p2l01umiri47o74l4m0pg@4ax.com>
User-Agent: G2/1.0
X-HTTP-UserAgent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 5.1;
 Trident/4.0; SU 3.95; .NET CLR 2.0.50727; .NET CLR 3.0.04506.648; .NET CLR
 3.5.21022; .NET CLR 3.0.4506.2152; .NET CLR 3.5.30729; .NET4.0C),gzip(gfe)
Message-ID: <ac87ddc4-2dc8-4d5e-a9ba-37d9465c0232@n9g2000yqn.googlegroups.com>
Subject: Re: Using mobile phone as an internet radio
From: George Herold <gherold@teachspin.com>
Injection-Date: Fri, 05 Oct 2012 20:01:12 +0000
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable