Self-configurable driver device for lighting systems, corresponding method and computer program product

Abstract

A driver device (10) for lighting sources, for example LED sources, comprises output nodes (N1, N2, N3, N4) for connecting lighting sources (L1, L2, L3, L4) to be driven, and a controller (12) with storage circuitry (120) configured to store within it a plurality of sets of driver configuration data. The device (10) is configured to drive the lighting sources (L1, L2, L3, L4) in one of a number of different driving modes in response to selection of a respective set of driver configuration data. The device (10) comprises load-detection circuitry (V1, Q1, R1, 16; R2, 18) configured to be coupled (M1, M2, M3, M4) to the output nodes (N1, N2, N3, N4) in order to produce a load-detection signal (D; M) indicative of the number of output nodes (N1, N2, N3, N4) that have a lighting source (L1, L2, L3, L4) connected to them. The device is able to self-configure by automatically selecting the aforesaid respective set of driver configuration data on the basis of the load-detection signal (D; M) indicative of the number of output nodes (N1, N2, N3, N4) that have a lighting source (L1, L2, L3, L4) connected to them.

Description

Technical field

[0001] The present disclosure relates to lighting systems.

[0002] One or more embodiments may find use, for example, in driver devices (for example, in so-called Electronic Control Gear or ECG) that are programmable with multiple-output DALI interface.Description of the prior art

[0003] The term DALI (Digital Addressable Lighting Interface) indicates a bidirectional-communication protocol that can be used for carrying out control of, and communication between, the components of a lighting system.

[0004] DALI is a communication protocol designed for programming of, and exchange of information between, devices related to lighting, and can be used not only for ECGs in a strict sense, but also for associated devices, such as sensors, pushbuttons, dimmers, and so forth.

[0005] The DALI protocol forms the subject of the international specification IEC 62386 with all its subparts (-1xx, -2xx, -3xx).

[0006] Once connected to a DALI network, a component can be addressed by means of a "short address" assigned thereto, which is unique for a given device in a given network.

[0007] The identifier of the device type (DT) identifies the specific set of features afforded by the connected device. As regards ECG, each DT forms the subject of a subpart of the IEC 62386-2xx specification.

[0008] For instance, as regards ECGs: DT-6 LED ECGs use a single DALI short address for controlling a single output, for example, for changing the level of light emission of a set of connected LEDs; one and the same ECG may have a number of outputs: in this case a short address is provided for each output (DT-6 multiple devices);

[0009] DT-8 LED ECGs can, instead, use a single DALI short address for controlling two or more outputs: in the case of the DT-8 identifier, it is possible to control a number of parameters, such as the colour temperature and the brightness of an apparatus via a single channel.

[0010] The DT-8 identifier is mainly designed for LED sources of a multicolour type, with up to six different colours, each identified by a letter: for example, "RGBWAF" is the maximum complete set of colour channels, which comprises Red, Green, Blue, White, Amber, and "Free" (i.e., not assigned to any specific colour).

[0011] Before being actually used in a system network, a DALI device usually needs to be configured. This particularly applies to devices with a number of outputs, and even more for DT-8 ones for which setting of a number of parameters is envisaged.

[0012] When an ECG is expected to support different configurations, it is desirable to be able to program at least the number of output channels physically available.

[0013] Programming of the configuration (i.e., setting) of the DALI device can be performed through an autonomous hardware user interface or with external software tools.

[0014] Hardware tools may comprise: switches of a dip-switch type; rotary switches or encoders; and local displays with pushbuttons or similar interactive interfaces.

[0015] Hardware tools present various drawbacks, for example, in so far as they involve additional costs for each DALI device produced and occupy space in the device (which may not be available); they moreover entail management of firmware and additional resources and may prove inconvenient in so far as, once installed in the final position of use, the DALI device may prove not easily accessible.

[0016] Software tools can be installed on a host PC or similar device (mobile phone, tablet) and may comprise: DALI interface applications, which use the DALI communication itself to program setting of the configuration: to carry out configuration of the device, these applications may use special DALI modes and / or hardware interfaces specific for DALI; software that uses other communication channels with the DALI device, either of a wireless type (for example, Wi-Fi, Bluetooth or NFC) or of a wired type (for example, 4-pin or single-wire TTL interfaces).

[0017] Each manufacturer usually adopts a strategy of its own, providing the user with specific configuration tools. In the absence of interoperability between software tools of different manufacturers and in the case where it is impossible to use the interfaces themselves, the user finds himself having to get equipped with (frequently having to purchase) different tools for each specific manufacturer or for successive generations of products.

[0018] For instance, the products available at Tridonic offer the configuration tools known as DeviceConfigurator and 4service NFC, whereas the products manufactured by Signify adopt the configuration tool MultiOne.

[0019] For OSRAM-Inventronics products, a configuration software Tuner4TRONIC (T4T) is available that is able to connect up to a DALI device through a specific DALI interface (DALImagic, which is in turn connected via USB) or via the NFC port when this is available in the DALI device.

[0020] There exist, however, legacy OSRAM-Inventronics products that use a different, not DALI-compatible, interface with a software called MultiProgrammer.

[0021] Moreover, in addition to having to procure these tools, the end user must learn how to use them, which may prove rather complex and hence pose problems for the user.

[0022] Documents US 2018 / 116025 A1, US 2012 / 187845 A1 and US 11 849 517 B1 are exemplary of related art.Object and summary

[0023] The object of one or more embodiments is to contribute to overcoming the drawbacks outlined previously.

[0024] According to one or more embodiments, the above object is achieved thanks to a device having the characteristics recalled in the ensuing claims.

[0025] One or more embodiments regard a corresponding method.

[0026] One or more embodiments regard a corresponding permanent computer program product that can be loaded into the memory of a processing circuit and comprises portions of software code that, when run on the above circuit, are able to implement the method described herein.

[0027] One or more embodiments hence envisage the use of a computer program product that can be loaded into the memory of at least one processing circuit (for example, a microcontroller) and comprises portions of software code for executing the steps of the method when the product is run on at least one processing circuit. As used herein, reference to such a computer program product is understood as being equivalent to reference to a microcontroller-readable medium containing, in a permanent way, instructions for controlling a processing system in order to coordinate implementation of the method according to one or more embodiments.

[0028] One or more embodiments are able to facilitate the task of the installer and users, enabling, so to speak, to skip manual configuration of a DALI device, such as ECGs with multiple output channels.

[0029] Solutions like the ones described herein make it possible to provide in an ECG (assumed as example of a DALI device) a sort of self-configuration such as to cause the device to be able to (self-)configure automatically for the most common cases of use.

[0030] Solutions like the ones described herein can operate also in multimodal devices. For instance, in the case of DT-6 / DT-8 ECGs it is possible to implement a simple manual selection between DT-6 and DT-8, while the specific configuration is completed automatically.

[0031] Solutions like the ones described herein can be applied both to constant-current ECGs and to constant-voltage ECGs, with particular advantage when the ECGs have more than two output channels.

[0032] Solutions like the ones described herein are based upon a load-detection mechanism, capable of detecting the existence of a load connected to a specific output channel.

[0033] For instance, this mechanism is able to detect that an output channel is connected to a load, being also able to detect (measure) the magnitude of the load, so as to detect automatically, in a device with a number of channels (i.e., a number of outputs), how many outputs have a load, such as a lighting source, connected to them.

[0034] Advantageously, it is also possible to intervene on self-configuration via a software tool by accessing the ECG via the DALI port itself or via some other wireless or wired communication port (Wi-Fi, Bluetooth, IR, NFC, etc.). For instance, the T4T tool itself (already cited previously) can access the ECG and overwrite the self-programming code previously contained therein.

[0035] Solutions like the ones described herein make it possible to afford a solution ready for use for its application, via a product that is able to self-configure, at least for the most common cases of use. This helps to save time and money, avoiding installation of software tools and purchase of specific interfaces that can be used only for configuring devices (for example, ECGs) of a certain manufacturer.

[0036] Furthermore, the installer / user can avoid having to learn how to set a certain device, which may prove in the final analysis far from appreciated.Brief description of the annexed drawings

[0037] One or more embodiments will now be described, purely by way of non-limiting example, with reference to the annexed drawings, wherein: Figure 1 is a possible embodiment exemplifying a device like the one described herein; and Figures 2, 3, 4 and 5 are flowcharts exemplifying possible operating modes allowed for a device like the one described herein.

[0038] It will be appreciated that, except where the context indicates otherwise, parts or elements that are similar are designated in the various figures by the same references.

[0039] Consequently, for reasons of brevity and simplicity of illustration, a detailed description of such parts or elements will not be repeated for each figure.

[0040] Once again, for reasons of brevity and simplicity of illustration, in the present description one and the same reference may possibly be used to denote both a certain node or line and a signal present on that particular node or line.Detailed description

[0041] In the ensuing description various specific details are illustrated in order to enable an in-depth understanding of various examples of embodiments according to the disclosure. The embodiments may be obtained without one or more of the specific details, or with other methods, components, materials, etc. In other cases, known structures, materials, or operations are not illustrated or described in detail so that the salient aspects of the embodiments will not be obscured.

[0042] Reference to "an embodiment" or "one embodiment" in the framework of the present description is intended to indicate that a particular configuration, structure, or characteristic described in relation to the embodiment is comprised in at least one embodiment. Phrases such as "in an embodiment" or "in one embodiment" that may be present in various points of the present description do not necessarily refer exactly to one and the same embodiment.

[0043] The references used herein are provided merely for convenience and hence do not define the sphere of protection or the scope of the embodiments.

[0044] To sum up what has been said at the outset of the present description, the abbreviations DT-6 and DT-8 identify categories of device defined by the DALI specifications basically on the basis of a set of features that an ECG is expected to provide.

[0045] The manufacturer checks / guarantees that the device (for simplicity reference is here made in particular to an ECG, taken as example) is conformable to the DTxx identifier declared.

[0046] For instance, in the case of the DT-6 identifier a short address is assigned to each individual channel, and hence in an ECG with a number of channels, DT-6 requires that each channel should have a short address, whereas for DT-8 a single short address is assigned to a number of channels. More precisely, logic units are used, and each logic unit has an address.

[0047] Once again for the purposes of illustration of the relevant art, the term Tuner4TRONIC (T4T) identifies a software available for OSRAM / Inventronics products that communicates using the DALI protocol via a hardware external to the ECG (known as DALI Magic) connected to the DALI lines and to a USB port, or else via an NFC peripheral, in some way connected to the processing system.

[0048] In the case of DT-6, the installer / user does not have in practice to decide on any operating mode: each channel has its short address (self-configuration of the channels). The operating mode of the ECG is already defined, without any need for specific instructions by the installer, except as regards the number of the channels.

[0049] For DT-6 multiple-channel devices it is possible to adopt in this regard an automatic detection mode.

[0050] In actual fact, there exist various operating modes, but in the majority of cases the predefined configuration chosen is correct (whatever the number of channels) and does not need to be modified.

[0051] There exist on the other hand external devices (we shall return to this subject in the sequel) that can affect the operating mode, for example, by entering into an operating mode known as Touch DIM by pressing a pushbutton.

[0052] In the case of the DT-8 there are various possible operating modes of the ECG - different from one another - in so far as more than one channel corresponds to a single address, so that the installer / user is required to select / configure the operating mode.

[0053] Solutions like the ones described herein facilitate recognition of the load or loads connected to the ECG and automatic setting of the operating mode (self-configuration).

[0054] For instance, it is possible in this regard to use memory banks containing registers for DALI configuration.

[0055] In solutions like the ones described herein, these memory banks are in general pre-defined during production, without necessarily requiring any intervention at the app or hardware level by the installer / user. For completeness, it will be noted that there exist on the other hand various other registers configured to control the behaviour of the ECG: these registers do not assume particular importance for the purposes of implementation of solutions like the ones described herein, given also the underlying difference in the mode of access to these registers.

[0056] In solutions like the ones described herein, it is possible to envisage that, during the set-up step, the device (ECG) will "understand" whether it has to implement a load-diagnostic feature during run-time or else whether the load connected is not suitable for the ECG.

[0057] Solutions like the ones described herein facilitate production of a device such as a DT-8 ECG that self-configures as such and can possibly pass - if so required or desired by the installer / user - from a (self-configured) DT-8 mode to a DT-6 mode.

[0058] It is also possible to add further devices (e.g., touch DIM devices, sensors, etc.) to the auxiliary inputs. In fact, the DT-8 ECG can be self-configured to be able to recognise such additional devices.

[0059] As already noted, automatic self-configuration (for example, as DT-8) is not an imperative option in so far as the installer / user retains the faculty of proceeding in a non-automatic way.

[0060] Again, if further devices are connected, these are recognised, and it is possible to carry out again a self-configuration that is able to take into account these devices.

[0061] Finally, it will be noted - in general terms - that in describing the various solutions presented herein no particular emphasis is laid either on the contents or on the specific modalities of implementation of the configuration of the device: these are aspects that depend upon the nature of the device and may be deemed in themselves known from the specifications (e.g., DALI).

[0062] In describing the various solutions presented herein, attention will, instead, be paid to the functions that enable the device to implement the configuration in the form of an automatic self-configuration, retaining on the other hand the possibility of defining the configuration in a traditional way, under the control of an operator.

[0063] Figure 1 illustrates by way of example a possible circuit diagram of a device 10 - hereinafter constant reference will be made for simplicity to an ECG - that is able to (self-)configure to behave differently on the basis of the number of loads detected.

[0064] Figure 1 refers, by way of example, to a four-channel DT-8 ECG, i.e., one with four loads L1, L2, L3, and L4 connected to a voltage Voutput referred to ground GND and driven via respective electronic switches M1, M2, M3, and M4, such as MOSFETs under the control of a processing unit (controller) 12.

[0065] For instance, and according to criteria in themselves known to persons skilled in the sector, the device 10 is a driver device (ECG) for lighting sources comprising a plurality of output nodes N1, N2, N3, N4 that are candidates for having connected thereto lighting sources L1, L2, L3, L4 to be driven.

[0066] The term "candidates" highlights the fact that, even though they are configurable for this purpose, the nodes N1, N2, N3, N4 do not necessarily all have to have connected to them a respective lighting source L1, L2, L3, L4: as will be seen again hereinafter, the ECG 10 presented herein by way of example is a driver device that is able to self-configure as a function of the number of the nodes N1, N2, N3, N4 actually connected to which is a load L1, L2, L3, or L4 (for example, a lighting source).

[0067] The device 10 as exemplified herein comprises a controller 12 that acts upon a plurality of electronic switches M1, M2, M3, M4 (for example, MOSFETs) coupled to respective output nodes N1, N2, N3, N4.

[0068] The electronic switches M1, M2, M3, M4 are configured to be rendered selectively conductive (switched on) by the controller 12.

[0069] The scheme of connection of the loads L1, L2, L3, L4 between the supply source Voutput and the nodes N1, N2, N3, N4 is such that through a load L1, L2, L3, L4 connected to a given node N1, N2, N3, N4 a current flow is created in response to the respective switch M1, M2, M3, M4 associated to that node N1, N2, N3, N4 being conductive.

[0070] Once again it is recalled that the nodes N1, N2, N3, N4 do not necessarily all need to have connected to them a respective lighting source L1, L2, L3, L4: the ECG 10 presented herein by way of example, with four output nodes, is in fact able to self-configure (automatically) as a function of the number of the nodes (not necessarily all four nodes N1, N2, N3, N4) to which a load L1, L2, L3, or L4 is actually connected.

[0071] The action of control of the switches M1, M2, M3, M4 by the controller 12, here represented schematically by an arrow C, is carried out, in a way in itself known, for example, via application to the control terminals of the switches M1, M2, M3, and M4 (the gates, in the case of field-effect transistors, such as MOSFETs) of respective PWM (Pulse-Width Modulation) signals - emitted by the controller C so as to render the electronic switches M1, M2, M3, M4 alternatively conductive (switched on) and non-conductive (switched off) according to modalities (for example, the frequency and duty-cycle of the PWM signal) dictated by the configuration of the controller 12.

[0072] In the solutions like the ones described herein, the switches M1, M2, M3, M4 may be used also to perform functions of detection / measurement of the load.

[0073] The diagram, provided purely by way of example, of Figure 1 illustrates the possible presence of a load-detection current generator comprising (in the example of embodiment presented herein, which - it is emphasized - is merely an example) a voltage generator V1 referred to ground GND acting upon the control terminal (the base, in the case presented here as example, of a bipolar transistor) of a transistor Q1 arranged with the emitter connected to a resistor R1 referred to ground GND and the collector coming under a load-detection line, which, for the purposes of performance of the load-detection function described hereinafter, is connected via (the cathodes of) respective diodes D1, D2, D3, and D4 to detection nodes N1, N2, N3 and N4 set between the switches M1, M2, M3, and M4 and (the anodes of) the diodes D1, D2, D3, and D4.

[0074] The node, denoted by P, between the transistor Q1 and the resistor R1 is connected to a threshold comparator 16, the output of which is able to supply to the controller 12 a load-detection signal D.

[0075] The terminals (in the case exemplified here, the source terminals, since they are field-effect transistors, such as MOSFETs) of the switches M1, M2, M3, and M4 opposite to the nodes N1, N2, N3, and N4 are connected together to a node S and come under a further resistor R2 referred to ground GND, which is connected at the node S to an output stage (buffer amplifier) 18 configured to supply to the controller 12 a load-measurement signal M.

[0076] In particular, by rendering the switches M1, M2, M3, and M4 selectively conductive, the controller 12 can couple the nodes N1, N2, N3, and N4 (via the diodes D1, D2, D3, and D4, which implement a wired OR function) to the transistor Q1 (which constitutes, together with the resistor R1 and the source V1, a load-detection current generator).

[0077] In this way, it is possible to give rise at the node P to values of load-detection current that differ according to whether the node N1, N2, N3, or N4 each time involved (for example, in so far as the switch M1, M2, M3, or M4 associated thereto is rendered non-conductive) has a load coupled thereto or not. The output signal D of the comparator 16 (which compares the signal on the node P with a reference threshold) hence assumes logic values that differ according to whether the node N1, N2, N3, or N4 each time involved in the action of detection has a load coupled thereto or not.

[0078] The number of cases where the output signal D of the comparator 16 assumes a "low" (or "0") logic value or a "high" (or "1") logic value hence indicates how many loads are connected to the device 10.

[0079] Likewise, by rendering the switches M1, M2, M3, and M4 selectively conductive (even just the ones for which the presence of a load coupled to the respective node N1, N2, N3, or N4 has been detected), the controller 12 can couple the loads involved to the node S, thus giving rise at the node S itself to a signal on the resistor R2 that is a function of the value of the load each time involved. The resistor R2 in practice functions as shunt resistor, for measuring the current "consumed" by the LEDs L1, L2, L3, or L4 (it is recalled once again that not all the output nodes N1, N2, N3, and N4 necessarily have a load L1, L2, L3, or L4 coupled thereto).

[0080] The signal M produced by the output stage 18 (possibly converted into digital format) hence supplies to the controller 12 a measurement of the value of the load involved.

[0081] It will be noted once again that the switches M1, M2, M3, M4 can be used (for example, in PWM mode) for normal driving of the loads (lighting sources L1, L2, L3, and L4, whatever their number) via the source Voutput, it being also possible to use them: thanks to the current generator, for detecting the load of the generator comprising the voltage source V1, the transistor Q1, and the resistor R1, as well as, thanks to the diodes D1, D2, D3, and D4, for detecting the number of sources connected as loads to the nodes N1, N2, N3, and N4 to produce the signal supplied to the comparator 16 (and consequently the load-detection signal D); and thanks to the signal supplied by the stage 18, for measuring the value of the corresponding electrical load (load-measurement signal M).

[0082] It will be appreciated on the other hand that Figure 1 is a diagram provided purely by way of example, it being possible to contemplate various other ways to obtain the same signals.

[0083] Basically, the device 10 exemplified herein comprises load-detection circuitry comprising a signal generator (the source V1, the transistor Q1, and the resistor R1) that can be coupled (via the diodes D1, D2, D3, and D4) to the output nodes N1, N2, N3, N4 so as to apply to the nodes N1, N2, N3, N4 what can be seen as a probe signal for probing, starting from the voltage V1, the existence of an applied load obtained.

[0084] In response to the aforesaid probe signal, the nodes N1, N2, N3, N4 yield at the node P load-sensing signals that have a value that is different according to whether the node N1, N2, N3, N4 to which the load-detection action is each time aimed has a load L1, L2, L3, L4 coupled thereto or else does not have a load L1, L2, L3, L4 coupled thereto.

[0085] The comparator 16 is configured to compare with its detection threshold the aforesaid load-sensing signals received starting from the nodes N1, N2, N3, N4 in response to the probe signals applied thereto.

[0086] The outcome of the comparison made by the comparator 16 (expressed by the signal D) hence depends upon whether each node N1, N2, N3, N4 has a load L1, L2, L3, L4 connected to it or not. The signal D is consequently indicative of the connection of lighting sources L1, L2, L3, L4 to the output nodes N1, N2, N3, N4, which makes it possible to establish how many of the nodes N1, N2, N3, N4 (i.e., the number of the nodes that) have loads (lighting sources L1, L2, L3, L4) connected to them.

[0087] The device 10 exemplified herein likewise comprises circuitry (the elements designated by the references R2, 18) configured to be coupled (via the electronic switches M1, M2, M3, M4) to the output nodes N1, N2, N3, N4 so as to produce the load-measurement signal M, which is indicative of the magnitude of the load deriving from lighting sources (L1, L2, L3, L4) connected to the output nodes N1, N2, N3, N4, it hence possibly being, like the signal D, indicative of the number of loads connected to the nodes N1, N2, N3, N4.

[0088] More specifically, in the case where the ECG is equipped (in a way in itself known to persons skilled in the sector) with a diagnostic feature based upon a measurement of the load, the self-configuration mechanism described herein can intervene on the basis of the signal M by enabling or disabling run-time diagnostics according to the magnitude of the load detected in the set-up stage.

[0089] As has already been said, rather than regarding the modalities of implementation of the configuration of the device 10, which are modalities that depend upon the nature of the device and are such as to be deemed in themselves known from the specifications (e.g., DALI), the solutions described herein primarily regard the functions that enable the device to implement an automatic self-configuration, albeit retaining the possibility of defining the configuration in a traditional way, under the control of an operator.

[0090] Purely by way of example, it is possible to contemplate that the controller 12 has within it - for example, in the block 120 - DALI registers and the memory banks such as to enable the device 10 to self-configure (in a way in itself known, for example, according to a DT-8 DALI configuration) on the basis of the loads detected, according to various operating modes that differ from one another, such as: in tunable-white (TW) mode, in practice with the capacity of controlling the colour temperature of a white light emitted, in the case where only two loads are found to be connected; in RGB mode, in the case where three loads are detected (for example, three lighting generators operating in the red = R, green = G, and blue = B); in RGBW mode, in the case where four loads are detected (for example, four lighting generators of which three generators operating in the red = R, green = G, and blue = B, plus a generator of white light = W).

[0091] All the DALI registers and the corresponding memory banks are self-programmed (in a way in itself known) on the basis of the most suitable or common settings according to the specific number of channels detected.

[0092] In a diagram like the one represented in Figure 1, the order of connection of the loads is irrespective of the sequence of the output terminals: for example, in the case where (just) two loads are connected at the first output and the third output to a four-output ECG, leaving the second output and the fourth output disconnected, a TW operating mode is in any case selected.

[0093] It is on the other hand also possible to contemplate solutions in which, taking into account the sequence with which the various output nodes N1, N2, N3, N4 are subjected to the load-detection action (and, possibly, taking into account a load-measurement signal, such as the signal M), the action of driving of the sources L1, L2, L3, L4 by the controller 12 can be rendered specific according to each individual load.

[0094] As has already been said, in the case where the ECG is provided with a diagnostic feature based upon a measurement of the load, the self-configuration mechanism described herein can intervene (for example, on the basis of the signal M) enabling or disabling run-time diagnostics according to the magnitude of the load detected in the set-up stage.

[0095] It may, in fact, be contemplated that the load connected be recognised in the set-up stage, without envisaging a further run-time check.

[0096] As has already been said, Figure 1 is a diagram provided purely by way of example, it being possible to envisage various other ways of implementing the same functions as those described herein.

[0097] For instance, detection of the loads connected to the output nodes can be made in a completely different way, for example, by means of current transformers, Hall sensors, possibly operating not in a sequential way but in parallel (i.e., all the channels at the same time) without using any switch.

[0098] Detection of the loads connected to the output nodes may also be carried out by exploiting the load-measurement signal M, which, as has already been noted, may (also) be viewed as a load-detection signal indicative of the number of loads connected to the output nodes N1, N2, N3, N4 precisely in so far as it is indicative of the magnitude of the load deriving, for example, from the lighting sources (L1, L2, L3, L4) connected to the aforesaid nodes: the magnitude of the load measured via the signal M is in fact a function of the number of the output nodes N1, N2, N3, N4 that have a load (for example, a lighting source L1, L2, L3, or L4) connected to them.

[0099] At least in principle, there may also be contemplated solutions that do not envisage performance of a diagnostic feature based upon a measurement of the load.

[0100] Consequently, it is possible to contemplate solutions that do not envisage generation of two distinct signals D and M as in the case of the example presented herein. The reason for the above is, as has been seen, that the load-measurement signal M can in itself (also) provide an indication of the number of loads connected to the nodes N1, N2, N3, N4.

[0101] Likewise, it is possible to envisage generation of (just) one signal like the signal D, without envisaging generation of the signal M.

[0102] Solutions that, as in the example presented herein, envisage generation of two distinct signals D and M may prove advantageous for various reasons, such as: the different level of accuracy envisaged for the load-detection action and for the load-measurement action: a load-measuring circuit might not be sufficiently sensitive to detect small loads, detection of which is, however, to be desired for the purposes of (self)-configuration; and / or the fact that the load-detection action is in general envisaged for the purposes of initial configuration of the ECG, whereas the load-measurement action for diagnostic purposes must usually be maintained during run-time.

[0103] Albeit not represented in Figure 1 for reasons of simplicity of illustration, it is possible to envisage (for example, at the level of software or hardware tool some examples will be explicitly mentioned hereinafter) a selection feature that can be used by an operator to: switch the ECG 10 between DT-8 operation and a non-DALI operation; switch the ECG 10 between DT-8 operation and a different DALI operation, for example, DT-6; restore the self-configured DT-8 DALI configuration; make a selection from among different self-configuration modes.

[0104] In other words, it is possible to exclude or modify the self-configuration using a software tool that is able to access the device 10 via the DALI port itself or some other communication port, whether wired or wireless (Wi-Fi, Bluetooth, IR, NFC, etc.), with the possibility, for example, of overwriting the (self)programming code via a tool such as the T4T tool.

[0105] The device 10 is an example of a DALI or DALI+ DT-8 ECG with more than two outputs (four in the example illustrated), which is able to self-configure on the basis of the number of loads connected. Self-configuration consists in a specific setting of the DALI registers and of the corresponding memory banks.

[0106] It is possible to envisage a selection feature for switching, for example, between DT-8 and a different operating mode, whether DALI or non-DALI. The selection can be carried out subject to the choice of an operator, and not automatically. The selector may be a physical device (e.g., a DIP switch) or any other type of actuator of choice, such as a jumper, a magnet, or else may be implemented by an action at a software level or by any other means such as to enable a choice.

[0107] The selection feature itself can bring the ECG back to a default state and restart a self-configuration, or else establish different types of self-configurations.

[0108] For instance, the ECG can be switched between DT-8 and DT-6, where in DT-6 one DALI address is assigned for each load found.

[0109] As has been seen, the order of connection of the physical loads to the output terminals is not important, so that it is possible to connect the load to any terminal of the device, given that only the total number of terminals occupied is important.

[0110] In the case of the example presented herein (which, it is once again emphasised, is merely an example) the load-detection circuit may comprise a load-detection current generator having a voltage generator V1 referred to ground GND that acts on the control terminal of a transistor Q1 arranged with the emitter connected to a resistor R1, which is itself also referred to ground GND, it being possible to connect the detection-current generator selectively to the load terminals (nodes N1, N2, N3, and N4 in Figure 1), hence detecting a signal that, compared with a certain threshold (comparator 16 in Figure 1), defines whether an actual load is connected or not.

[0111] A load-measuring circuit (stage 18 in Figure 1) makes it possible to define whether a load is measurable during run-time or not. In the case where the load is measurable during run-time, it is possible to activate a diagnostic feature on the respective output channel.

[0112] Moreover, the magnitude of the load can lead to a different automatic configuration of the ECG, not only for activation of the diagnostics, but also for normal operation.

[0113] As has been seen, it is possible to envisage a tool (for example, a software tool) for overwriting, restoring, modifying, or inhibiting the self-configuration, accessing the device 10 via the DALI interface itself or some other port, whether wired or wireless. Detection of the state of possible auxiliary inputs can modify the self-configuration so that it is possible to use such auxiliary inputs to modify the behaviour or further govern the device 10 during operation. In some cases, certain auxiliary devices, such as touch DIM devices, sensors, etc., can exploit the DALI pins themselves, at the level of physical connection, but with different communication modes, and also different electrical levels.

[0114] As exemplified in Figure 1, the same electronic switches (for example, solid-state switches such as MOSFETs M1, M2, M3, and M4) can be used both for the action of driving of the load (for example, via PWM signals) during normal operation and for the process of detection and measurement of the load.

[0115] Figures 2, 3, 4, and 5 are flowcharts exemplifying possible operating modes allowed for a device like the one described herein.

[0116] The above operating modes can be implemented via a computer program product that can be loaded into the controller 12 of a driver device (ECG) as described herein, such a computer program product comprising portions of software code that cause the driver device 10 to operate with the methods described herein when the product is run on the aforesaid controller 12.

[0117] It will be appreciated on the other hand that the sequence of the steps of Figures 2 to 5 is provided merely by way of example in so far as: one or more steps illustrated in Figures 2 to 5 may be omitted, executed in a different way (for example, with other tools) and / or replaced by other steps; it is possible to add further steps; and one or more steps can be executed in a sequence different from the one illustrated.

[0118] The blocks of the diagram of Figure 2, which refers to a DT-8 self-configuration with a possible reset of a "manual" type (i.e., performed by an operator), exemplify the possible following steps: 1000 - exit of the device 10 from the production plant 1001 - default configuration (e.g., 1xDT-6) 1002 - load detection 1003 - determination of load absence / presence, with return to step 1001 in the absence of load (outcome Y = Yes from step 1003) 1004 - just one load present? If so (Y = Yes), go to step 1005A; otherwise (N = No), go to step 1005 1005 - (just) two loads present? If so (Y = Yes), go to step 1005A, where, for instance, referring back to the example given previously, the device is configured in the mode known as tunable-white (TW); otherwise (N = No), go to step 1006 1006 - (just) three loads present? If so (Y = Yes), go to step 1006A, where, for instance, once again referring back to the example given previously, the device is configured in RGB mode (with white, amber, and free colour that are masked), different from the TW mode seen previously; otherwise (N = No), go to step 1007 1007 - four loads present? If so (Y = Yes; this on the other hand is the only possible outcome, given that in the present case we are dealing with a device with 4 channels) go to step 1007A, where, for instance, once again referring back to the example given previously, the device is configured in the RGB mode (with amber and free colour that are masked), different both from the TW mode and from the RGB mode seen previously, and then go to step 1008 1008 - setting of DALI operating mode 1009 - completion of self-configuration 1010 - device ready for operation 1011 - check on possible "manual" reset, with return upstream in the case of negative outcome (N = No) 1012 - return to step of block 1001 in the case of positive outcome (Y = Yes) consequent to a possible reset.

[0119] In brief, the flowchart of Figure 2 provides an example of a device 10 in which a controller 12 is envisaged, comprising: data-storage circuitry 120 configured to store a plurality of sets of driver configuration data, where the driver device 10 is configured to drive lighting sources L1, L2, L3, L4 in one of a plurality of driving modes, different from one another (for example, TW, RGB, RGBW), in response to selection (implemented in blocks 1005A, 1006A, 1007A) of a respective set of driver configuration data of the aforesaid plurality of sets of driver configuration data; and load-detection circuitry V1, Q1, R1, 16 configured to be coupled (for example, through the switches M1, M2, M3, M4 and the diodes D1, D2, D3, D4) to the aforesaid output nodes N1, N2, N3, N4 to produce a load-detection signal (the signal D) that is indicative (as ascertained in steps 1004, 1005, 1006, 1007) of the number of output nodes N1, N2, N3, N4 that have a lighting source L1, L2, L3, L4 connected to them, so that the controller 12 is configured to select automatically (in steps 1005A, 1006A, 1007A) the aforesaid respective set of driver configuration data on the basis of the load-detection signal D indicative of the number of said output nodes that have a lighting source connected to them, automatically self-configuring, for example, in a DT-8 field: according to the TW mode, in the presence of two loads detected; according to the RGB mode, in the presence of three loads detected; and according to the RGBW mode, in the presence of four loads detected.

[0120] As discussed previously, there may also be contemplated the possibility of performing the load-detection function in a different way, for example, by exploiting for this purpose the load-measuring circuitry (elements 18 and R2 in Figure 1), the output signal M of which may also be in itself indicative of the number of the output nodes N1, N2, N3, N4 that have a lighting source thereto L1, L2, L3, L4 connected to them.

[0121] The flowchart of Figure 3 refers to an example of operation in which the scheme represented in the flowchart of Figure 2 is integrated with a function of determination of the load value (for example, via the signal M emitted by the output stage 18 of Figure 1) for the purposes of a run-time check on the load.

[0122] In the flowchart of Figure 3, blocks and corresponding functions already described in relation to the flowchart of Figure 2 are denoted by the same references, without their corresponding description being repeated, for reasons of brevity.

[0123] As compared to the flowchart of Figure 2, the flowchart of Figure 3 envisages the following further blocks / functions: 2000 - evaluation of the load, before the configuration steps 1004, 1005, 1005A, 1006, 1006A, 1007, 1007A, with prosecution in parallel to a step 2001 2001 - check on run-time detectability of the loads following upon completion of self-configuration in step 1009 2002 - following upon a positive outcome (Y = Yes) from the step of check on run-time detectability of the loads, execution of the corresponding function of detection and check

[0124] In brief, the flowchart of Figure 3 provides an example of a device 10, wherein: load-measuring circuitry (the elements R2, 18) is provided, configured to be coupled (for example, via the electronic switches M1, M2, M3, M4) to the output nodes N1, N2, N3, N4 so as to produce (block 2000) a load-measurement signal M indicative of the magnitude of the load deriving from lighting sources L1, L2, L3, L4 connected to the output nodes N1, N2, N3, N4; and the controller (12) is configured to: select automatically (in steps 1005A, 1006A, 1007A) the aforesaid respective set of driver configuration data on the basis of the load-measurement signal M (which is, in any case, indicative of the number of output nodes N1, N2, N3, N4, connected to which is a lighting source L1, L2, L3, L4); and / or activate (in step 2002) a diagnostic feature on the lighting sources L1, L2, L3, L4 connected to output nodes N1, N2, N3, N4 on the basis of the aforesaid load-measurement signal M.

[0125] The flowchart of Figure 4 refers to an example of operation in which the scheme represented in the flowchart of Figure 2 (possibly this may apply, mutatis mutandis, also to the scheme represented in the flowchart of Figure 3) is integrated with functions that also envisage at least one possible alternative configuration (different from the configuration as DT-8 device discussed previously), such as: a possible configuration via the T4T tool already recalled several times previously or another simple hardware means, such as a switch, with effect in the step represented by block 3002; and / or a possible configuration as DT-6 device with a possible overriding software intervention and a final configuration of a single type, for example, of a RGBWAF type (Red = R, Green = G, Blue = B, White = W, Amber = A, plus Free colour = F).

[0126] By "and / or" it is meant to highlight the fact that, even though the two (or other) options are presented together for reasons of simplicity, not necessarily both of them have to be envisaged.

[0127] Once again, for reasons of brevity, in the flowchart of Figure 4, blocks and corresponding functions already described in relation to the flowcharts of Figures 2 and 3 are denoted by the same references, without their corresponding description being repeated.

[0128] As compared to the flowchart of Figure 2, the flowchart of Figure 4 envisages the following further blocks / functions: 3000 - detection of a T4T configuration option, performed by an operator 3001 - completion of the corresponding programming, with device ready for operation following upon T4T programming (block 1010') 3002 - check on whether activation of a possible DT-6 configuration option has taken place, for example, via a DIP switch; in the case of negative outcome (N = No) from the verification step, proceeding with the DT-8 (self-)configuration option through steps 1004, 1005, 1005A, 1006, 1006A, 1007, 1007A; in the case of positive outcome (Y = Yes) from the verification step 3002, execution of DT-6 configuration steps denoted by 1004', 1004A', 1005', 1005A', 1006', 1006A', 1007', 1007A' 3003 - check on whether activation of a possible DT-6 configuration option has taken place in step 3002, with return upstream in the case of negative outcome (N = No) and return, via step 1012, to step of block 1001 in the case of positive outcome (Y = Yes).

[0129] The steps of the blocks denoted by 1004', 1004A', 1005', 1005A', 1006', 1006A', 1007', 1007A' can be viewed as being as a whole dual with respect to the steps of the DT-8 configuration 1004, 1005, 1005A, 1006, 1006A, 1007, and 1007A, with the differences represented by the fact that: in the case of positive outcome (Y = Yes) from the step 1004' of check on whether just one load is connected, the same step is followed by the setting of the corresponding DT-6 configuration (1xDT-6); blocks 1005A', 1006A', and 1007A' correspond to the corresponding DT-6 settings (2xDT-6, 3xDT-6, 4xDT-6) .

[0130] In brief, the flowchart of Figure 4 provides an example of a device 10 configured to receive a user-generated configuration command (see blocks 3000, 3002), and the device 10 is configured to drive the lighting sources L1, L2, L3, L4 in one or more alternative driving modes (for example, following upon a T4T configuration option - see block 3001 - and / or DT-6 configuration option - see blocks 1004A', 1005A', 1006A', 1007A') different from the driving mode (for example, DT-8) self-configured in steps 1005A, 1006A, 1007A.

[0131] As has already been said, the functions presented in the flowchart of Figure 4 may be applied, not only to the example of operation exemplified in the flowchart of Figure 2, but also to the scheme represented in the flowchart of Figure 3.

[0132] The above possibility is exemplified by the flowchart of Figure 5, where, once again, blocks and corresponding functions already described in relation to the flowcharts of Figures 2, 3, and 4 are denoted by the same references, without their corresponding description being repeated, for reasons of brevity.

[0133] In practice, the flowchart of Figure 5 exemplifies the possibility of integrating the scheme of the flowchart of Figure 3, which envisages the functions of determination of the load value for the purposes of a run-time verification of the load, by envisaging a configuration via the T4T tool and / or a configuration as DT-6 device with final configuration of a RGBWAF type through functions such as: 3000 - detection of a T4T programming option, performed by an operator 3001 - completion of the corresponding programming, with device ready for operation following upon T4T programming (block 1010') 3002 - check on whether activation of a possible DT-6 configuration option has taken place, for example, via a DIP switch; in the case of negative outcome (N = No) from the verification step, proceeding with the DT-8 (self-)configuration option through steps 1004, 1005, 1005A, 1006, 1006A, 1007, 1007A; in the case positive outcome (Y = Yes) from the verification step 3002, execution of DT-6 configuration steps denoted by 1004', 1004A', 1005', 1005A', 1006', 1006A', 1007', 1007A' 3003 - check on whether activation of a possible DT-6 configuration option has taken place in step 3002, with return upstream in the case of negative outcome (N = No) and return, via step 1012, to step of block 1001 in the case of positive outcome (Y = Yes).

[0134] Of course, without prejudice to the underlying principles, the details and embodiments may vary with respect to what has been illustrated herein purely by way of example, without thereby departing from the sphere of protection as this is specified in the annexed claims. LIST OF REFERENCESDevice (ECG)10Load supply voltageVoutputLoadsL1, L2, L3, L4Load nodesN1, N2, N3, N4Switches (MOSFETs)M1, M2, M3, M4DiodesD1, D2, D3, D4Controller12Self-configuration function120Control functionCLoad-detection sourceV1Load-detection transistorQ1Load-detection resistorR1Load-detection comparator16Load-detection nodePLoad-detection signalDLoad-measuring nodeSLoad-measuring resistorR2Load-measuring stage18Load-measurement signalMGroundGNDExit of device from production plant1000Default configuration1001Load detection1002Absence / presence of load1003Just one load present?1004, 1004'1xDT-6 configuration1004A'Two loads present?10052xDT-6 / 2xDT-8 configuration1005A, 1005A'Three loads present?10063xDT-6 / 3xDT-8 configuration1006A, 1006A'Four loads present?10074xDT-6 / 4xDT-8 configuration1007A, 1007A'Setting of DALI operating mode1008Completion of self-configuration1009Device ready for operation1010, 1010'Check on possible reset1011Return upstream with positive outcome1012Load evaluation2000Check on load detectability2001Load detection and check2002T4T programming option3000Completion of T4T programming3001DT-6 configuration option3002Activation of DT-6 configuration3003

Claims

1. A driver device (10) for lighting sources, the driver device (10) comprising: a plurality of output nodes (N1, N2, N3, N4) connectable to lighting sources (L1, L2, L3, L4) to be driven thereby, a controller (12) including data-storage circuitry (120) configured to have stored therein a plurality of sets of driver configuration data wherein the driver device (10) is configured to drive said lighting sources (L1, L2, L3, L4) in one of a plurality of different driving modes in response to a respective set of driver configuration data being selected (1005A; 1006A, 1007A) out of said plurality of sets of driver configuration data, and load-detection circuitry (V1, Q1, R1, 16; R2, 18) configured to be coupled (M1, M2, M3, M4) to said output nodes of said plurality of output nodes (N1, N2, N3, N4) to produce a load-detection signal (D; M) indicative (1004, 1005, 1006, 1007) of the number of said output nodes of said plurality of output nodes (N1, N2, N3, N4) having a lighting source of said lighting sources (L1, L2, L3, L4) connected thereto, wherein the controller (12) is configured to automatically select (1005A; 1006A, 1007A) said respective set of driver configuration data based on said load-detection signal (D; M) indicative (1004, 1005, 1006, 1007) of the number of said output nodes of said plurality of output nodes (N1, N2, N3, N4) having a lighting source of said lighting sources (L1, L2, L3, L4) connected thereto.

2. The driver device (10) of claim 1, comprising a plurality of electronic switches (M1, M2, M3, M4) coupled to respective output nodes of said plurality of output nodes (N1, N2, N3, N4), said plurality electronic switches (M1, M2, M3, M4) configured to be alternatively made conductive and non-conductive, wherein current flows through a lighting source of said lighting sources (L1, L2, L3, L4) connected to any of said output nodes of said plurality of output nodes (N1, N2, N3, N4) in response to a respective electronic switch in said plurality electronic switches (M1, M2, M3, M4) being conductive.

3. The driver device (10) of claim 1 or claim 2, wherein the load-detection circuitry (V1, Q1, R1, 16) comprises: a signal generator (V1, Q1, R1) configured to be coupled to said output nodes of said plurality of output nodes (N1, N2, N3, N4) to apply thereto probe signals, and a comparator (16) configured to be coupled to said output nodes of said plurality of output nodes (N1, N2, N3, N4) to perform a comparison of load-detection sensing signals received from said nodes (N1, N2, N3, N4) in response to said probe signals being applied thereto with a detection threshold, wherein the outcome of said comparison (D) is indicative of lighting sources (L1, L2, L3, L4) being connected to said output nodes of said plurality of output nodes (N1, N2, N3, N4) .

4. The driver device (10) of claim 2 and claim 3, wherein said signal generator (V1, Q1, R1) in the load-detection circuitry (V1, Q1, R1, 16) is configured to be coupled (D1, D2, D3, D4) to said output nodes of said plurality of output nodes (N1, N2, N3, N4) via said plurality of electronic switches (M1, M2, M3, M4).

5. The driver device (10) of any of the previous claims, comprising load measuring circuitry (R2, 18) configured to be coupled (M1, M2, M3, M4) to said output nodes of said plurality of output nodes (N1, N2, N3, N4) to produce (2000) a load measurement signal (M) indicative (1004, 1005, 1006, 1007) of the magnitude of the load provided by lighting sources (L1, L2, L3, L4) connected to said output nodes of said plurality of output nodes (N1, N2, N3, N4), wherein the controller (12) is configured to: automatically select (1005A; 1006A, 1007A) said respective set of driver configuration data (1005A; 1006A, 1007A) based on said load measurement signal (M), and, preferably, activate (2002) a diagnostic feature of lighting sources (L1, L2, L3, L4) connected to said output nodes of said plurality of output nodes (N1, N2, N3, N4) based on said load measurement signal (M).

6. The driver device (10) of claim 2 and claim 5, wherein said load measuring circuitry (R2, 18) is configured to be coupled to said output nodes of said plurality of output nodes (N1, N2, N3, N4) to produce (2000) said load measurement signal (M) via said plurality of electronic switches (M1, M2, M3, M4).

7. The driver device (10) of any of the previous claims, wherein the driver device (10) is configured to receive a user-generated configuration command (3000, 3002) and to drive said lighting sources (L1, L2, L3, L4) in at least one alternative driving mode (3001; 1004A', 1005A'; 1006A', 1007A') alternative to said plurality of different driving modes (1005A; 1006A, 1007A) in response to said user-generated configuration command (3000, 3002).

8. The driver device (10) of any of the previous claims, wherein said plurality of different driving modes (1005A; 1006A, 1007A) comprises a DALI Device Type 8, DT-8 driving mode.

9. The driver device (10) of claim 7 and claim 8, wherein said at least one alternative driving mode comprises a DALI Device Type 6, DT-6 driving mode (1004A', 1005A'; 1006A', 1007A').

10. A method, comprising: connecting a number of lighting sources (L1, L2, 13, L4) to output nodes in said plurality of output nodes (N1, N2, N3, N4) of a driver device (10) for lighting sources according to any of claims 1 to 9, wherein said driver device (10) comprises said load detection circuitry (V1, Q1, R1, 16; R2, 18) configured to be coupled (M1, M2, M3, M4) to said output nodes in said plurality of output nodes (N1, N2, N3, N4) to produce a load detection signal (D; M) indicative (1004, 1005, 1006, 1007) of the number of said output nodes in said plurality of output nodes (N1, N2, N3, N4) having connected thereto a lighting source of said lighting sources (L1, L2, L3, L4), wherein the driver device (10) drives said number of lighting sources (L1, L2, L3, L4) in one of a plurality of different driving modes (1005A; 1006A, 1007A) in response to a respective set of driver configuration data automatically selected (1005A; 1006A, 1007A) based on said load-detection signal (D; M) indicative (1004, 1005, 1006, 1007) of the number of said output nodes of said plurality of output nodes (N1, N2, N3, N4) having connected thereto a lighting source of said number of lighting sources (L1, L2, L3, L4) .

11. A computer program product loadable into the controller (12) of a driver device (10) for lighting sources according to any of claims 1 to 9, the computer program product comprising software code portions that cause the driver device (10) to operate with the method according to claim 10 when the product is run on said controller (12).

Images