Maintenance Method and Configuration Method for Luminaire Assemblies

Abstract

Example embodiments relate to maintenance methods and configuration methods for luminaire assemblies. One example maintenance method for replacing a component in a luminaire assembly includes obtaining desired operational information of the luminaire assembly. The method also includes obtaining identification information of a replacement programmable component. Additionally, the method includes creating a feature file based on the desired operational information and the component identification information. The feature file includes programming instructions for programming the replacement programmable component to obtain the desired operation as defined by the desired operational information. Further, the method includes replacing the previous component by the replacement programmable component. In addition, the method includes configuring the replacement programmable component using the created feature file.

Claims

1. (canceled)

2. (canceled)

3. (canceled)

4. (canceled)

5. (canceled)

6. (canceled)

7. (canceled)

8. (canceled)

9. (canceled)

10. (canceled)

11. (canceled)

12. (canceled)

13. (canceled)

14. (canceled)

15. (canceled)

16. (canceled)

17. (canceled)

18. (canceled)

19. (canceled)

20. (canceled)

21. (canceled)

22. (canceled)

23. (canceled)

24. (canceled)

25. (canceled)

26. (canceled)

27. (canceled)

28. (canceled)

29. (canceled)

30. (canceled)

31. (canceled)

32. (canceled)

33. (canceled)

34. (canceled)

35. (canceled)

36. A maintenance method for replacing a component in a luminaire assembly, said method comprising: obtaining desired operational information of the luminaire assembly; obtaining identification information of a replacement programmable component; creating a feature file based on the desired operational information and the component identification information, said feature file comprising programming instructions for programming the replacement programmable component to obtain the desired operation as defined by the desired operational information; replacing the previous component by the replacement programmable component; and configuring the replacement programmable component using the created feature file.

37. The method according to claim 36, wherein the programmable component is a driver, the identification information being preferably defined by a driver code representative for the technical characteristics of the driver, more preferably the name and/or brand and/or model of the driver.

38. The method according to claim 36, wherein the desired operational information comprises desired dimming information.

39. The method according to claim 38, wherein the obtaining of desired dimming information comprises obtaining a dimming code representative for at least a drive current and a type of dimming, the dimming code being preferably further representative for at least an additional parameter selected from: a dimming profile over time, a thermal protection feature, a constant lumen output, a CLO feature, geographical information, and additional functionalities information.

40. The method according to claim 37, wherein creating a feature file based on the desired dimming information and the identification information comprises the step of using a mapping table between the dimming information and programming parameters of programmable drivers defined by their respective identification information.

41. The method according to claim 36, further comprising the additional step of verifying the compatibility between the identification information and the desired operational information, wherein preferably the additional step of verifying the compatibility comprises verifying if the type of dimming of the desired dimming information is supported by the programmable component corresponding with the identification information.

42. The method according to claim 36, wherein obtaining the identification information comprises reading the identification information using near field communication, NFC on the replacement programmable component, preferably on the replacement driver and/or wherein obtaining the identification information comprises entering the identification information by an operator.

43. The method according to claim 36, wherein obtaining the desired operational information of the luminaire assembly comprises machine reading a QR code or a bar code, and/or wherein obtaining the desired operational information of the luminaire assembly comprises reading an operational information using near field communication, NFC, and/or wherein obtaining the desired operational information of the luminaire assembly comprises entering an operational information by an operator.

44. The method according to claim 36, wherein the step of configuring the replacement programmable component using the created feature file comprises transferring the feature file to the replacement programmable component using near field communication, NFC and/or Bluetooth, and/or wherein the step of configuring the replacement programmable component using the created feature file comprises transferring the created feature file using a first protocol to a transfer device and transferring the created feature file using a second protocol different from the first protocol from the transfer device to the programmable component.

45. The method according to claim 36, wherein the programmable component is any one of the following: a driver, a controller, a sensor, a communication device, and a human-interface device, and/or wherein the desired operational information comprises any one or more of the following: a protocol type, e.g. a type of communication protocol used by the programmable component, a power related parameter, a control parameter, and a control profile.

46. The method according to claim 36, further comprising a step of encrypting the created feature file, transferring the encrypted feature file, and decrypting the encrypted feature file.

47. A computer-implemented method for configuring a luminaire assembly comprising a programmable component, comprising: obtaining a desired operational information for the luminaire assembly; obtaining the identification information of the programmable component; creating a feature file based on the desired operational information and the identification information, said file comprising programming instructions for programming the programmable component to obtain the desired operation defined by the desired operational information; and configuring the programmable component using the created feature file.

48. The method according to claim 47, wherein the programmable component is a driver, and/or wherein the desired operational information comprises desired dimming information, the identification information being preferably defined by a driver code representative for the technical characteristics of the driver, more preferably the name and/or brand and/or model of the driver.

49. The method according to claim 48, wherein obtaining desired dimming information comprises obtaining a dimming code representative for at least a drive current and a type of dimming, the dimming code being preferably further representative for at least an additional parameter selected from: a dimming profile over time, a thermal protection feature, a constant lumen output (CLO) feature, geographical information, and additional functionalities information.

50. The method according to claim 47, wherein creating a feature file based on the desired operational information and the identification information comprises the step of using a mapping table between the operational information and programming parameters of programmable components defined by their respective identification information.

51. The method according to claim 47, further comprising the additional step of verifying the compatibility between the identification information and the desired operational information.

52. The method according to claim 47, wherein obtaining the identification information comprises reading the identification information using near field communication device, NFC, on the component, and/or wherein obtaining the identification information comprises entering the identification information by an operator.

53. The method according to claim 47, wherein obtaining the desired operational information of the luminaire assembly comprises machine reading a QR code or a bar code, and/or wherein obtaining the desired operational information of the luminaire assembly comprises reading an operational information using near field communication, NFC, and/or wherein obtaining the desired operational information of the luminaire assembly comprises entering an operational information by an operator, and/or wherein the step of configuring the programmable component using the created feature file comprises transferring the feature file to the component using near field communication and/or Bluetooth.

54. A computer-implemented method for configuring a luminaire assembly comprising a programmable component, comprising the steps of: obtaining desired operational information of the luminaire assembly; obtaining identification information of a replacement programmable component; verifying the compatibility between the identification information and the desired operational information; creating a feature file based on the desired operational information and the component identification information, said feature file comprising programming instructions for programming the replacement programmable component to obtain the desired operation as defined by the desired operational information; and configuring the replacement programmable component using the created feature file.

55. The method according to claim 54, wherein the desired operational information comprises desired dimming information and wherein the step of verifying the compatibility comprises verifying if a type of dimming of the desired dimming information is supported by the programmable component corresponding with the identification information.

Description

BRIEF DESCRIPTION OF THE FIGURES

[0055] This and other aspects of the present invention will now be described in more detail, with reference to the appended drawings showing currently preferred embodiments of the invention. Like numbers refer to like features throughout the drawings

[0056] FIG. 1 is a schematic drawing of a maintenance situation illustrating an exemplary embodiment of the maintenance method.

[0057] FIG. 2 is a schematic drawing of a configuration situation illustrating an exemplary embodiment of the method for configuring a luminaire.

[0058] FIG. 3 shows a flowchart illustrating an exemplary embodiment of the maintenance method for replacing a driver in a luminaire.

[0059] FIGS. 4A to 4D show schematic screen views of an exemplary embodiment of a program for executing the maintenance and configuration methods.

[0060] FIG. 5 shows a flowchart illustrating an exemplary embodiment of the method for configuring a luminaire.

[0061] FIGS. 6A and 6B show schematic views of further exemplary embodiments of the method.

DESCRIPTION OF THE EMBODIMENTS

[0062] FIG. 1 shows a maintenance situation in which an exemplary embodiment of the maintenance method is of particular interest. In particular, a system 1000 comprises a replacement driver 100 and computing means 30 for interacting with the replacement driver 100 and/or a driver 10 to be replaced and/or other parts of a luminaire 1. A maintenance specialist 20 comes to service a luminaire 1 comprising a driver 10 to be replaced due to obsolescence or failure. The case of a failure will be taken as hypothesis in the rest of the description as way of an example only. The maintenance specialist brings with him spare parts 100, 200, 300 . . . and computing means 30 with several peripherals 40, 50 and 60. Among the possible peripherals could be an NFC peripheral interface 40, a cabling interface 50 to interact with drivers via physical wiring and plugging, a bar code reading interface, a tablet or a mobile 60 for scanning QR codes. The computing means self may be comprised in a general computer, a laptop, a tablet, a mobile or a remote server. This list is not exclusive and is a mere illustration of possibilities a skilled person would understand as suitable for the present application. The spare parts 100, 200, 300, etc. are the new drivers for luminaire assemblies at the disposition of the maintenance specialist. They may be of different brands and/or different models. In practice drivers of different brands may support similar lighting situations and a skilled person, like a maintenance specialist, would know which of the spare parts at his disposal could possibly be used as replacement of the driver 10.

[0063] The maintenance method for replacing a driver in a luminaire in that situation will now be described with reference to the flowchart of FIG. 3. The method is in part computer-implemented on the computing means 30 connected to peripheral interfaces 40, 50 and 60.

[0064] Upon starting the maintenance, the first step Si is to obtain the desired dimming information of the luminaire assembly. The dimming information may be defined by a dimming code representative for at least a drive current and a type of dimming For instance the dimming code may stand for a feature table comprising at least a drive current and a type of dimming for simple cases. The drive current may be the maximum output current used to drive a light source, typically a plurality of LEDs of the luminaire assembly. The type of dimming can be e.g. amplitude dimming relating a voltage to the light output, scheduling dimming where several dimming levels are scheduled during the day, DALI, Bipower mode having two dimming levels, 0-10V, no dimming mode where the user chooses to operate without dimming, etc. The dimming code may further be representative for at least an additional parameter selected from: a dimming information, such as a dimming profile over time, a thermal protection feature and a constant lumen output (CLO) feature, a geographical information, further functionalities information. For example, the dimming code may indicate whether a thermal protection for protecting the LEDs from overheating is present, whether a CLO function is present, a type of CLO defined by a value of a start current in percentage and a maximum amount of time before full current, a dimming percentage in function of the time of the day, a dimming percentage in function of a sensed value (e.g. sensed light, sensed movement, etc.), dimming current levels and dimming starting times for scheduling dimming, an initial dimming level, a daylight saving time, a midnight shift information based on a country code, a time zone information, a latitude information, a longitude information, a time base dimming information relating the time elapsed and the light output, a sensor override information for overriding a photocell sensor on the basis of another information like the presence of a user, a light colour temperature output, etc. By desired dimming information is referred to information related to the future dimming characteristics intended for the luminaire in terms at least of drive current and type of dimming. In most maintenance cases, the future dimming characteristics as defined by the desired dimming information will be the same as the past dimming characteristics of the luminaire prior to the failure of the driver. In other cases, the future dimming characteristics may contain new dimming characteristics of the luminaire related to an upgrade or a downgrade of the luminaire.

[0065] Optionally, the dimming information may be retrieved from the driver to be replaced. The dimming information may be for instance read via QR code or a bar code on the defective driver or on the luminaire. A mobile 50 or a tablet transmits then to the computing means 30 the data concerning the dimming profile. The diming information may also be known from beforehand and manually entered in the form of a code of a limited number of digits by the maintenance specialist. During step S1, data concerning the desired dimming information is thus received.

[0066] The following step S2 is to obtain the identification information concerning a replacement programmable driver. By replacement driver is meant the new driver, as example here for the rest of the description the driver 100, intended to be used in the luminaire instead of the old and/or faulty driver 10. The identification information may be actually defined by a driver code representative for the technical characteristics of the driver, preferably the name and/or brand and/or model of the driver. The maintenance specialist 20 may use here his knowledge in selecting already one probably compatible driver: by selecting either the same driver (same brand same model) as previously or another driver (different brand and/or model) suitable for the dimming profile identified in Step S1. The step of obtaining the identification information is done preferably by reading the driver identification code by NFC on the replacement driver 100. The NFC peripheral interface 40 reads into the replacement driver 100 and transmits to the computing means 30 the data concerning the driver identification code of the replacement driver 100. During step S2, data concerning the identification information in the form of a driver identification code is thus received.

[0067] However the maintenance specialist may not know for sure which driver would be compatible or may unintentionally select a wrong driver. To cope with such issues, the next step S3 is to verify the compatibility between the identification information and the dimming information. In this way a safeguard against an improper matching between the intended use and the chosen replacement driver is introduced. In case the result of the compatibility check is negative, an error message indicating an incompatibility is shown to the user and the method loops back to step S2 by requesting new identification information of another driver. Other ways of communicating the error may be selected depending on circumstances, by for instance other visual or audio means. As an example of incompatibility, one can think of the situation where a certain selected driver does not support the option of thermal protection of the LEDs while the selected dimming code is representative of the presence of such a thermal protection, the combination selected driver/selected dimming information would then be incompatible. If the result of the compatibility test is positive and the dimming information and identification information are compatible, the method proceeds further to step 4.

[0068] The following step S4 is then to create a feature file based on the desired dimming information and the identification information. The feature file comprises programming instructions for programming the replacement programmable driver to obtain the desired dimming as defined by the desired dimming information. A mapping table may be used between the dimming information and the programming parameters of programmable drivers defined by their respective identification information. In this manner, the desired dimming information for the luminaire assembly may be translated into a language specific to a specific driver, and can be used to generate a feature file with the right instructions for the specific driver. The mapping table may link the vocabulary used in the source code specific to each driver to the parameters of the dimming information in order to obtain a universal tool to create feature files for various drivers.

[0069] The following Step S5 is to replace the previous driver 10 by the new replacement driver 100. This step may be performed by a qualified person, like the maintenance specialist 20, as it may imply accessing the inside of the housing of the luminaire and disconnecting and reconnecting, potentially dangerous, electrical connections.

[0070] The final step S6 is to configure the replacement driver using the created feature file. In particular the feature file is transferred, transmitted, written using for instance near field communication (NFC) to the replacement driver. Other wired or wireless transfer alternatives may also be used. When a user approaches the NFC peripheral interface 40 to the NFC interface of the driver 100, the replacement driver 100 is thus programmed to operate under the desired dimming information and ready to be exchanged with the faulty driver 10 for further use in the serviced luminaire.

[0071] It is here noted that the step S5 of replacing the previous driver by a replacement driver may be split in two steps of first removing the previous driver and second installing the replacement driver. In addition these two steps may be performed prior or after any of the other steps S1-S4, S6 depending on circumstances and as obvious to a skilled person. For instance a maintenance specialist may first remove the old driver in the luminaire, program the replacement driver (new driver) on the ground and then install the new driver in the luminaire, or remove the old one, install the new one and then program the new one among other possibilities. According to another example one could even first program the new driver, then remove the old driver and next install the new one.

[0072] As illustrated further in FIGS. 4A to 4D showing several screen views, a computer program comprising instructions is used to cause the maintenance system 1000 comprising the replacement driver 100 and the computing means 30 to execute the steps of the maintenance method described above.

[0073] First a window 401 as in FIG. 4A may open on a graphical interface requesting first a dimming code 410. A dimming code 410 may be either selected from a scrolling menu 415 or retrieved by clicking on a “read” button 420 activating a peripheral interface 40 to read the dimming code. An “Add” button 425 may enable the user to add a new dimming code 410, in case a new dimming information is desired. This functionality may open a further interface (not shown here) for customizing dimming information.

[0074] In the same window 401 identification information may be requested in the form of a driver code 430. The driver code 430 may be entered either via a scrolling menu 435 or retrieved by clicking on a “read” button 450, activating a peripheral interface 40-60 to read the driver code 430, for instance by NFC via the NFC peripheral 40. When using NFC, the user 20 approaches the NFC peripheral interface 40 to the driver 100 such that the driver code 430 is retrieved automatically.

[0075] When both fields of the dimming code 410 and driver code 430 have been filled (Steps S1 and S2), the user is asked to validate a “create feature file” button 460. If the dimming code 410 and driver code 430 are not compatible with each other, an error window 501 as illustrated in FIG. 4B will then pop up with a message 510 indicating an error in the result of the incompatibility test of step S3. Upon validating the error message 510 using a validating button 520, the first window 401 of steps S1 and S2 is presented again, to change either the dimming code 410 and/or the driver code 430. If the new combination of dimming code 410 and driver code 430 is compatible, the feature file is generated as illustrated on FIG. 4C (step S4). A new pop up windows 601 indicates a message 610 that the generation was successful as well as the name and saving location of the newly generated feature file.

[0076] Finally, in a new window 701 illustrated in FIG. 4D, the user is requested to retrieve the generated feature file 710 using a scrolling menu 715 and/or a search tool (not represented). After validating the “Write feature” button 720, a transfer of the feature file to the driver is activated (step S5). In particular after pressing the “write feature” button 720, when a user 20 approaches e.g. the NFC peripheral interface 40 to the driver 100, the feature file is written into the driver 100, and the driver 100 is programmed to operate under the desired dimming information.

[0077] The above described computer program may further be stored on a computer readable medium.

[0078] Although disclosed here for the purpose of servicing a luminaire having a faulty driver, the concept of the present method can be broadened to encompass situations beyond the normal use of the luminaire relating for instance to failure situations, surveillance and monitoring in general. A similar method and similar program would be used as a common way of monitoring various kinds of programmable components such as drivers independent of the brand and model. Indeed, a programmable component may be reprogrammed using a created feature file without replacing the programmable component. This may be useful if desired operational information for a luminaire has changed, e.g. because the environment around the luminaire has changed.

[0079] In addition although not represented here, the possibility of updating the program to a more recent version may be offered to the user in the graphical interface 401 and/or 701.

[0080] FIG. 2 shows a configuration situation in which an exemplary embodiment of the configuration method is of particular interest. A system 2000 may comprise a driver 100 and computing means 30 with peripherals 40-60. A driver 100 for a luminaire may be provided with a label 110 comprising among other at least one of the name, the model, the brand, the main characteristics of the driver. A QR code or a bar code may also be present on the label 110. Alternatively a label such as 110 may be provided on the luminaire The driver 100 may further be provided with a near field communication (NFC) interface 120 for reading-writing information from/into the driver 100. Among the possible peripherals could be an NFC peripheral interface 40, a cabling interface 50 to interact with drivers via physical wiring and plugging, a bar code reading interface, a tablet or a mobile 60 for scanning QR codes. The computing means self may be comprised in a general computer, a laptop, a tablet or a mobile. This list is not exclusive and is a mere illustration of possibilities a skilled person would understand as suitable for the present application.

[0081] FIG. 5 shows a configuration situation in which an exemplary embodiment of the method of the present application is of particular interest. During manufacturing, a luminaire comprising a driver 100 is to be configured to a particular use using computing means 30 with several peripherals 40, 50 and 60. The same reference numbers as used for the maintenance situation apply here as well.

[0082] The present method for configuring the luminaire in that situation will now be described with reference to the flowchart of FIG. 5. The method is computer-implemented on the computing means 30 connected to peripheral interfaces 40, 50 and 60. Upon starting up the configuration process of the driver, the first step S10 is to obtain the desired dimming information of the luminaire assembly. The dimming information may be defined by a dimming code representative for at least a drive current and a type of dimming For instance the dimming code may stand for a feature table comprising at least a drive current and a type of dimming for simple cases. The drive current may be the maximum output current used to drive a light source, typically a plurality of LEDs of the luminaire assembly. The type of dimming can be e.g. amplitude dimming relating a voltage to the light output, scheduling dimming where several dimming levels are scheduled during the day, DALI, Bipower mode having two dimming levels 0-10V, no dimming mode where the user chooses to operate without dimming, etc. The dimming code may further be representative for at least an additional parameter selected from dimming information, such as a dimming profile over time, a thermal protection feature and a constant lumen output (CLO) feature, a geographical information, further functionalities information. For example, the dimming code may indicate whether a thermal protection for protecting the LEDs from overheating is present, whether a CLO function is present, a type of CLO defined by a value of a start current in percentage and a maximum amount of time before full current, a dimming percentage in function of the time of the day, a dimming percentage in function of a sensed value (e.g. sensed light, sensed movement, etc.), dimming current levels and dimming starting times for scheduling dimming, an initial dimming level, a daylight saving time, a midnight shift information based on a country code, a time zone information, a latitude information, a longitude information, a time base dimming information relating the time elapsed and the light output, a sensor override information for overriding a photocell sensor on the basis of another information like the presence of a user, a light colour temperature output, etc. By desired dimming information is referred to information related to the future dimming characteristics intended for the luminaire in terms at least of drive current and type of dimming The dimming information may be known from beforehand and manually entered in the form of a code of a limited number of digits by the maintenance specialist. During step S1, data concerning the dimming information is thus received.

[0083] The following step S20 is to obtain the identification information of the programmable driver of the luminaire. The identification information may be actually defined by a driver code representative for the technical characteristics of the driver, preferably the name and/or brand and/or model of the driver. The step of obtaining the identification information is done preferably by reading the identification information by NFC on the driver. The NFC peripheral interface 40 is brought in near proximity of the NFC interface 120 on the driver 100 to read into the driver 100 and transmit to the computing means 30 the data concerning the identification information of the driver 100. During step S20, data concerning the identification information is thus received. However during the manufacturing process the wrong driver may have been selected. The following step S30 is then to verify the compatibility between the identification information and the dimming information. In this way a safeguard against an improper matching between the intended use and the chosen driver is introduced. In case the result of the compatibility check is negative, an error message indicating an incompatibility is shown to the user and the method loops back to step S20 by requesting new identification information of another driver. In this way the driver may be changed and replaced by another suitable one. If the result of the compatibility test is positive and the dimming information and identification information are compatible, the method proceeds further to step 40.

[0084] The following step S40 is then to create a feature file based on the desired dimming information and the identification information. The feature file comprises programming instructions for programming the programmable driver to obtain the desired dimming information. A mapping table may be used between the dimming information and the programming parameters of programmable drivers defined by their respective identification information. In this manner, the desired dimming information for the luminaire assembly may be translated into a language specific to a specific driver, and can be used to generate a feature file with the right instructions for the specific driver. The mapping table may link the vocabulary used in the source code specific to each driver to the parameters of the dimming information in order to obtain a universal tool to create feature files for various drivers.

[0085] The final step S50 is to configure the driver using the created feature file. In particular the feature file may be transferred, transmitted, written using for instance near field communication (NFC) onto the driver 100. Other wired or wireless transfer alternatives may also used. When a user approaches the NFC peripheral interface 40 to the NFC interface 120 of the driver 100, the program is loaded into the driver and the driver is then programmed to operate under the desired dimming information and ready for further use in the luminaire.

[0086] The same software as described in FIGS. 4A-4D is used to perform the steps of the method described in FIG. 5.

[0087] In the examples of FIGS. 1-5 the programmable component is a driver for driving a light source. However, as explained in the summary, other programmable components such as a sensor, a communications means, a controller, a driver for powering a load which is not a light source, a human interface device, etc. may replaced and programmed in a similar way using any suitable operational information.

[0088] FIGS. 6A and 6B illustrate possible embodiments for transferring the created feature file to a replacement component 100. The creating of the feature file is done by a computer means based on the identification information corresponding with the programmable replacement component 100 and the desired operational information. According to an exemplary embodiment, the desired operational information comprises any one or more of the following: a dimming information, a protocol type, e.g. a type of communication protocol used by the programmable component 100, a power related parameter of the programmable component 100, a control parameter, a control profile. In an exemplary embodiment the programmable component 100 is a programmable sensor having a memory in which one or more control parameters are stored, e.g. during assembly of the luminaire in the factory, wherein the one or more control parameters are ensuring a good operation of the sensor within the luminaire assembly. The one or more control parameters may comprise any of the exemplary control parameters discussed above in the summary.

[0089] The method uses a computer means comprising a remote server 30 indicated as the “cloud” in FIGS. 6A and 6B. A mobile device 31 communicates with the remote server 30. For example, the remote server 30 may be connectable via a mobile phone application to the mobile device 31, e.g. a smart phone or a tablet. The mobile device 31 may be used to obtain the identification information of the replacement programmable component 100 and of the desired operational information. For example the mobile device 31 may read out the identification information and/or of the desired operational information using any one of the method steps disclosed in the summary. Based thereon the feature file is created e.g. by the remote server 30 and/or by the mobile device 31. It is noted that the feature file may be created by a single processor or may be created in a distributed manner. Also, for creating the feature file use may be made of data stored in the remote server.

[0090] In some embodiments, the created feature file is transferred directly from the mobile device 31 to the replacement programmable component 100, see FIG. 6A.

[0091] In other embodiments, the created feature file is transferred from the mobile device 31, to a transfer device 32, e.g. a brand-specific mobile device, and next from the transfer device 32 to the replacement programmable component 100. The transfer from the mobile device 31 to the transfer device 32 may use a first protocol, e.g. Bluetooth, and the transfer from the transfer device 32 to the replacement programmable component 100 may use a second protocol, e.g. NFC.

[0092] Optionally, the feature file may be encrypted, e.g. by the remote server 30 or by the mobile device 31. For example, the feature file may be created on the remote server 30 and encrypted before sending it to the mobile device 31. The decryption may take place e.g. in the replacement programmable component 100 or in the transfer device 32.

[0093] Whilst the principles of the invention have been set out above in connection with specific embodiments, it is understood that this description is merely made by way of example and not as a limitation of the scope of protection which is determined by the appended claims.