Abstract: A light system (FIG. 2) is disclosed. The light system includes a plurality of series connected light emitting diodes (240-246). Each of a plurality of switching devices (230-236) has a control terminal and each has a current path coupled in parallel with a respective LED. A plurality of fault detector circuits (220-226) are each coupled in parallel with a respective light emitting diode. Each fault detector circuit has a first comparator (FIG. 7, 704) arranged to compare a voltage across the respective light emitting diode to a respective first reference voltage (708). When a fault is detected, a control signal is applied to the control terminal to turn on a respective switching device of the plurality of switching devices.

Abstract: A light system (FIG. 2) is disclosed. The light system includes a plurality of series connected light emitting diodes (240-246). Each of a plurality of switching devices (230-236) has a control terminal and each has a current path coupled in parallel with a respective LED. A plurality of fault detector circuits (220-226) are each coupled in parallel with a respective light emitting diode. Each fault detector circuit has a first comparator (FIG. 7, 704) arranged to compare a voltage across the respective light emitting diode to a respective first reference voltage (708). When a fault is detected, a control signal is applied to the control terminal to turn on a respective switching device of the plurality of switching devices.

Abstract: A light system (FIG. 2) is disclosed. The light system includes a plurality of series connected light emitting diodes (240-246). Each of a plurality of switching devices (230-236) has a control terminal and each has a current path coupled in parallel with a respective LED. A plurality of fault detector circuits (220-226) are each coupled in parallel with a respective light emitting diode. Each fault detector circuit has a first comparator (FIG. 7, 704) arranged to compare a voltage across the respective light emitting diode to a respective first reference voltage (708). When a fault is defected, a control signal is applied to the control terminal to turn on a respective switching device of the plurality of switching devices.

Abstract: A light system (FIG. 2) is disclosed. The light system includes a plurality of series connected light emitting diodes (240-246). Each of a plurality of switching devices (230-236) has a control terminal and each has a current path coupled in parallel with a respective LED. A plurality of fault detector circuits (220-226) are each coupled in parallel with a respective light emitting diode. Each fault detector circuit has a first comparator (FIG. 7, 704) arranged to compare a voltage across the respective light emitting diode to a respective first reference voltage (708). When a fault is defected, a control signal is applied to the control terminal to turn on a respective switching device of the plurality of switching devices.

Abstract: A system and method are disclosed for creating and describing a configurable data set, configuring the data set and merging a resulting configured data set into a target data set. One or more configurable data elements are stored in a configurable data set that forms part of a configurable merge module. The configurable merge module also includes metadata concerning the configurable data. The metadata describes the data elements and how they can be configured and how to implement changes to the configurable data. Each configurable data element can be presented to the configurable merge module consumer through a user interface. The configurable merge module consumer can thus make configuration choices. Also provided is a transformation engine for customizing the configurable data based on configurable merge module consumer choices and a merge engine for inserting configured data into a target data set.

Abstract: A system to deploy content from one network to another includes an export search component. During an export process, a level-based scan of a content database is performed to efficiently find children and dependencies of the object(s) to be deployed. An export object table is created and filled with the children and dependencies found in the level-based scan. The export object table is ordered based on object type so that for each object being exported, its parent and its dependencies will be exported before the object itself is exported. The system may selectively perform incremental deployments in which only objects that have changed since their last deployment will be exported. Objects have identifiers and the system maintains a change log using the object identifiers, which allows the system to determine whether an object should be included in the incremental deployment.

Abstract: Non-administrators selectively move content from a source network to a destination network. The source network includes a deployment server that can deploy an item and its dependencies (if any) listed in a quick deploy list without having to get specific administrator authorization for the deployment. The deployment server can be configured to check the quick deploy list relatively frequently so that any items listed in the quick deploy list are quickly deployed. The listing of items in the quick deploy list is organized into “jobs” and identifies a path that indicates the source and destination for each job. A job is associated with one path and specifies one or more items of the source to be deployed and a schedule to deploy the specified item(s). The deployment server is configured by the administrator with permissions for specific authors to list items in the quick deploy list.

Abstract: Described is managing the changing of software implementations such as applications deployed to enterprise client users or machines. Precedence relationships between deployed applications are specified. To determine which applications to install for a given client, the precedence is applied to the subset of applications assigned or published to the client. At logon or machine reboot, an upgrade process evaluates the deployed applications and any upgrade relationships, setting applications for removal or installation. A user may also install an application that has been designated as optional. Also described is an application lifecycle model for replacing applications. For example, administrators can phase in upgrades as a pilot to a small group of users, roll out upgrades to a larger group, and then provide the application to all users. Upgrades may be mandatory or optional, and replaced programs may be removed and then replaced, or overlaid during installation.