PDA

View Full Version : Transporter/SB3 Display Life



newy
2008-12-04, 15:12
Hello. I have finally given in and decided to leave my computer on 24-7 to alleviate all the associated hassles w/ the computer going into standy and wirelessley WOL.

That said, I now have the capapbility of displaying info on the screen 24-7. My question - how long can I expect the pretty green display to last if info is displayed constatntly? A year? 2? 3? 10? 100? 1,000,000 years?

Thanks.

garym
2008-12-04, 15:28
I'm also curious about screen burn-in. I have a boom, and when the alarm turns itself off in the morning, it moves to the "now playing screen" where it stays until I turn off the boom. But sometimes I'm out for a week or so, thus the now playing screen may be on for days. I don't think this is the sort of screen that has a "burn" issue, but just curious.

funkstar
2008-12-04, 15:33
Well there have been very few cases of any kind of screen problems reported on the forums, and probably most of them have been to do with damaged, dead or dieing screens (only part of the display working for example), rather than ones with burn in or a loss in brighness.

Don't get me wrong it does happen, it's just not really that common.

toby10
2008-12-04, 15:36
Hello. I have finally given in and decided to leave my computer on 24-7 to alleviate all the associated hassles w/ the computer going into standy and wirelessley WOL.

That said, I now have the capapbility of displaying info on the screen 24-7. My question - how long can I expect the pretty green display to last if info is displayed constatntly? A year? 2? 3? 10? 100? 1,000,000 years?

Thanks.

I don't have a TP, just an SB3. The SB3 VFD display (same as Boom) was rated at 100,000 hours of use. Run 24/7 that's over 11 years.
And I *think* the 100,000 hours was "half life" meaning the VFD will be "half as bright as new" for the rated hours.

norman12
2008-12-04, 15:38
I've had a SB3 permanently on and running the weather date and time plug-in for 3 years and not noticed any screen problems.
I do have the brightness set to 3 though.

funkstar
2008-12-04, 16:02
The SB3 VFD display (same as Boom) was rated at 100,000 hours of use.
SB3 and boom use completely different VFD's, the SB3 and transporter share the same ones though :)

Not that it matters, I'm sure the quoted lifetime would be the same on both.

CatBus
2008-12-04, 16:07
From what I've read, VFDs tend to dim with age rather than fail catastrophically, and they are favored by consumer electronics manufacturers for devices with long real-world lifetimes (10 years and longer). However, I don't know specific longevity figures for these particular displays, so I can't say.

Personally, I use the PowerSave plugin to make sure the displays are turned off when not in use. It just doesn't feel right to leave it on all the time.

JJZolx
2008-12-04, 20:26
I have an SB2 that has fairly pronounced screen burn in (or burn out?) from leaving it run the date/time screensaver at maximum brightness for a couple of years. The pixels in the center of the display are noticeably dimmer than those to either side.

I have a feeling that had it been run at lesser brightness there would be little noticeable degradation of the display, but I would recommend a 'blank' screensaver for any display that you value. How many clocks does anyone need, anyway?

peterw
2008-12-04, 20:55
I have an SB2 that has fairly pronounced screen burn in (or burn out?) from leaving it run the date/time screensaver at maximum brightness for a couple of years. The pixels in the center of the display are noticeably dimmer than those to either side.

I have a feeling that had it been run at lesser brightness there would be little noticeable degradation of the display, but I would recommend a 'blank' screensaver for any display that you value. How many clocks does anyone need, anyway?

For the curious, my FuzzyTime plugin (see below) can be set to move the displayed time slowly from side to side to help distribute the work over more pixels. On my own system I have a copy of SuperDateTime that I've modified to use FuzzyTime's shifting API so that its output moves every time SDT updates its forecast.

-Peter

Sike
2008-12-05, 03:23
I have an SB2 that has fairly pronounced screen burn in (or burn out?) from leaving it run the date/time screensaver at maximum brightness for a couple of years. The pixels in the center of the display are noticeably dimmer than those to either side.

I have a feeling that had it been run at lesser brightness there would be little noticeable degradation of the display, but I would recommend a 'blank' screensaver for any display that you value. How many clocks does anyone need, anyway?

Ditto here.

It is nice to have the 'real' time around the house though.

amey01
2008-12-05, 19:07
My listening room Squeezebox is used very lightly (only for serious listening - never just left on in the background - so that equates to maybe 3-5 hours a week max).

I can see the burn-out from the analogue VU meters on the display - not in general use, but when the whole display alights such as when pressing the volume control when it's set at MAX.

It's less than two years old and has never displayed a turned off screensaver.

I'll be placing a warranty claim when I get around to it.

sgmlaw
2008-12-05, 19:17
I keep our displays on our SB3s "off" when turned off, and in a pitch black room, you can still see the filaments glowing a gentle orange.

So I think unless you pull the power plug, the VFDs will continue to "burn". But I prefer the electronic stability of leaving the circuits powered 24/7.

FWIW, I've other VFDs that are approaching 20 years old, and they still work just fine.

GoCubs
2008-12-06, 15:24
For the curious, my FuzzyTime plugin (see below) can be set to move the displayed time slowly from side to side to help distribute the work over more pixels. On my own system I have a copy of SuperDateTime that I've modified to use FuzzyTime's shifting API so that its output moves every time SDT updates its forecast.

-Peter

Speaking of FuzzyTime w/SDT... When you have a sec can you see if FuzzyTime is correctly using the date/time formatting selected by the user? I had to update the plugin today as something changed in SC that broke it... I'm not using FuzzyTime so I don't have a system to test it with, but my guess it it isn't using the correct format string.

-Greg