Silicon Investor (SI) -- The First Internet Community

STOCKTALK

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor. We ask that you disable ad blocking while on Silicon Investor in the best interests of our community. If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.

Technology Stocks : All About Sun Microsystems -- Ignore unavailable to you. Want to Upgrade?

To: Michael F. Donadio who wrote (36240)	10/7/2000 8:43:56 PM
From: Charles Tutt	Read Replies (2) \| Respond to of 64865

How do you assign an IP address to a pothole? Charles Tutt (TM)

To: Michael F. Donadio who wrote (36240)	10/7/2000 11:46:43 PM
From: tiquer	Read Replies (1) \| Respond to of 64865

Oh please Michael.. I have changed many light bulbs in industrial situations... the issues you are bringing up are mostly manpower and difficulty issues and not needing to know when the light bulb is going to burn out... If a light bulb signals it needs to be changed out they're still going to change em all out in the difficult to do areas... Knowing when a light bulb is going to burn out is not the first thought Scott should be mentioning in how vast the internet will be.. IMO... Cheers, Roger

To: Michael F. Donadio who wrote (36240)	10/8/2000 1:52:11 PM
From: rudedog	Read Replies (2) \| Respond to of 64865

Michael - a light bulb connected to the internet????? Give me a break! I saw an article about that and thought it must be a joke. I did an energy management and maintenance system for a GM plant in the early 80s which monitored the state and energy consumption of every piece of equipment in the plant - every light, every switch, every motor, every HVAC unit. It used an IEEE488 carrier on the power lines to transmit data, so no additional wiring was required in most cases. Current monitoring techniques were used to track the condition of both incandescent and fluorescent lighting - those same techniques appeared in high end GM cars a few years later (for example the 1989 Cadillacs provide indications for any burned out bulbs via current monitoring). The system also predicted when bulbs might fail before they actually did fail, as in most cases, incandescent bulbs show a rise in current draw shortly before they fail. Fluorescent show a decay in current draw when running and an increase in starting draw as they approach the end of their useful life, so maintenance can be scheduled when convenient, not when the lights fail. The cost per monitored point on that system was less than $0.50 and it worked fine - it is still in use nearly 20 years later. It would be trivial to put that reporting onto TCP/IP but what would the point be? Seems like an overly complex way to re-invent capability that has been around in a cheap and reliable form for a long time.