FURNITURE CONTROL SYSTEM AND METHOD FOR CONTROLLING AN ADJUSTABLE FURNITURE SYSTEM

Abstract

A furniture control system has a first and a second control unit to which a first and a second actuator are connectable. The first control unit is configured to control the first actuator based on first actuation data and comprises a first data pool unit for storing first data including the first actuation data. The second control unit is configured to control the second actuator based on second actuation data and comprises a second data pool unit for storing second data including the second actuation data. The control system is configured to synchronize the first and second data upon a change of the first and/or the second actuation data.

Claims

1. A furniture control system, comprising a first control unit, to which a first actuator is connectable, the first control unit being configured to control the first actuator based on first actuation data and comprising a first data pool unit for storing first data including the first actuation data; a second control unit, to which a second actuator is connectable, the second control unit being configured to control the second actuator based on second actuation data and comprising a second data pool unit for storing second data including the second actuation data; wherein the control system is configured to synchronize the first and second data upon a change of the first and/or the second actuation data.

2. The furniture control system according to claim 1, wherein the first and/or the second actuation data include at least one of the following: a driving command for the connected actuator; a target position for the actuator; a driving speed; an acceleration profile; a deceleration profile.

3. The furniture control system according to claim 1, wherein the first control unit is configured to receive first event data; the second control unit is configured to receive second event data; the first control unit is configured to set or change the first actuation data based on the first event data; and the second control unit is configured to set or change the second actuation data based on the second event data.

4. The furniture control system according to claim 3, wherein the first data further include the first event data; the second data further include the second event data; and the control system is configured to synchronize the first and second data upon a change of the first and/or the second event data.

5. The furniture control system according to claim 3, wherein the first and/or the second event data include at least one of the following: a command received from a user input device connected to the control system; an error condition signaled by at least one of the first actuator and the second actuator; a hardware fault signaled by at least one of the first actuator and the second actuator; a signal that a target position cannot be reached by at least one of the first actuator and the second actuator; a signal that a driving command cannot be executed by at least one of the first actuator and the second actuator; an event that is suitable for inducing a change of state of at least one of the first actuator and the second actuator.

6. The furniture control system according to claim 3, further comprising a user input device connected to the control system or to one of the first and the second control unit, the user input device configured to provide commands to the control system or to one of the first and the second control unit in response to a user input.

7. The furniture control system according to claim 1, wherein the first and the second control unit are configured to execute a driving command for the respective connected actuator only after synchronization of the first and the second data.

8. The furniture control system according to claim 1, wherein the control system is configured to withhold from synchronizing the first and second data if no change of any of the first and the second data occurs.

9. The furniture control system according to claim 1, wherein the first and the second data pool unit are configured to withhold from communicating with each other if no change of any of the first and the second data occurs.

10. A furniture system including a furniture control system according to claim 1 and at least two parts of adjustable furniture comprising the first and the second actuator.

11. The furniture system according to claim 10, wherein the at least two parts of adjustable furniture comprise a first adjustable table and at least a second adjustable table, wherein the first table includes the first control unit and the first actuator and wherein the second table includes the second control unit and the second actuator.

12. The furniture system according to claim 10, wherein the at least two parts of adjustable furniture comprise a first adjustable bed and a second adjustable bed, wherein the first bed includes the first control unit and the first actuator and wherein the second bed includes the second control unit and the second actuator.

13. A method for controlling an adjustable furniture system comprising a user input device, a first and a second actuator and a first and a second control unit with a first and a second data pool unit, the method comprising: the user input device sending command data to the first control unit; the first control unit generating first actuation data based on the command data and storing the first actuation data in the first data pool unit; after detection of the storage of the first actuation data in the first data pool unit, storing second actuation data in the second data pool unit by synchronizing the first data pool unit to the second data pool unit; wherein after completion of the synchronization the first control unit controlling the first actuator based on the first actuation data; and the second control unit controlling the second actuator based on the second actuation data.

14. The method according to claim 13, wherein the first and/or the second actuation data include at least one of the following: a driving command for the connected actuator; a target position for the actuator; a driving speed; an acceleration profile; a deceleration profile.

15. The method according to claim 13, wherein controlling the first and the second actuator comprises executing a driving command included in the first and second actuation data.

16. The method according to claim 13, further comprising receiving event data by the first and/or the second control unit; storing the event data in the first or the second data pool unit; and synchronizing the first data pool unit to the second data pool unit after detection of the storage of the event data.

17. The method according to claim 16, wherein the first or the second actuation data are generated based on the event data.

18. The method according to claim 16, wherein the event data include at least one of the following: a command received from the user input device; an error condition signaled by at least one of the first actuator and the second actuator; a hardware fault signaled by at least one of the first actuator and the second actuator; a signal that a target position cannot be reached by at least one of the first actuator and the second actuator; a signal that a driving command cannot be executed by at least one of the first actuator and the second actuator; an event that is suitable for inducing a change of state of at least one of the first actuator and the second actuator.

19. The method according to claim 13, further comprising withholding from synchronizing the first and the second data pool unit if no change of any of the first and the second actuation data occurs.

20. The method according to claim 13, further comprising the first and the second data pool unit withholding from communicating with each other if no change of any of the first and the second actuation data occurs.

21. The method according to claims 13, further comprising the first and the second control unit executing a driving command for the respective connected actuator only after synchronization of the first and the second data.

Description

BRIEF DESCRIPTION OF THE DRAWINGS

[0038] In the following, the improved communication concept is explained in detail with the aid of exemplary implementations by reference to the drawings. Components or elements that are functionally identical or have an identical effect may be denoted by identical references. Identical components and/or components with identical effects may be described only with respect to the figure where they occur first. The description is not necessarily repeated in subsequent figures.

[0039] In the drawings:

[0040] FIG. 1 shows an example implementation of a furniture control system according to the improved communication concept;

[0041] FIG. 2 shows a table system with a furniture control system according to the improved communication concept;

[0042] FIG. 3 shows a bed system with a furniture control system according to the improved communication concept;

[0043] FIG. 4 shows a further example implementation of a furniture control system; and

[0044] FIG. 5A to FIG. 5F show an example time flow during application of the improved communication concept.

DETAILED DESCRIPTION

[0045] FIG. 1 shows an example implementation of a furniture control system with a first control unit CU1 and a second control unit CU2. In addition, a user interface device UID is provided which may be part of the furniture control system or be external to the furniture control system. A first actuator ACT1 is connected to the first control unit CU1, and a second actuator ACT2 is connected to the second control unit CU2. The first control unit CU1 includes a first data pool unit DP1 for storing first actuation data actd1 and optionally storing first event data evnt1. Similarly, the second control unit CU2 includes a second data pool unit DP2 for storing second actuation data actd2 and optionally storing second event data evnt2.

[0046] The first and the second data pool unit DP1, DP2 form parts of a data pool DP that has a synchronization mechanism DP SYNC.

[0047] The user interface device UID is shown with example buttons, like a first memory button M1, a second memory button M2, an up button and a down button. These buttons may be physically present and e.g. implemented as mechanical buttons of any kind, or may also be interactive buttons displayed on a display of a handset, a mobile device or a computer screen. The user interface device UID may be connected to one of the control units CU1, CU2 by means of a tethered connection or alternatively with a wireless connection. It is also possible that the connection type can be switched.

[0048] The furniture control system may be implemented in any furniture system where two or more adjustable furniture parts are included and which should be controlled synchronously.

[0049] Referring to FIG. 2, a table system with a furniture control system according to the improved communication concept is shown, for example according to the implementation shown in FIG. 1. The table system comprises a first table TBL1 having the first control unit CU1 and a pair of first actuators ACT1, ACT1a. In addition, a user input device UID is provided at the first table TBL1. Similarly, the second table TBL2 has the second control unit CU2, to which a second pair of actuators ACT2, ACT2a is connected. Optionally, a second user interface device UID2 can be provided at the second table TBL2.

[0050] Each of the tables TBL1, TBL2 can be controlled individually. With the furniture control system, synchronous operation, e.g. height adjustment of both tables TBL1, TBL2, is possible.

[0051] Referring to FIG. 3, a bed system with a first bed BED1 and a second bed BED2 and a furniture control system with a first and a second control unit CU1, CU2 and a first and a second actuator ACT1, ACT2 is shown. For example, each of the actuators ACT1, ACT2 is able to change an angle of elevation of a head part of the respective bed. With the furniture control system, synchronous operation of both actuators ACT1, ACT2 is possible. Hence, the two single beds BED1, BED2 are operated like one king-size bed or the like. A user interface device for the bed system is omitted in FIG. 3 for a better overview but can be provided for user interaction.

[0052] Referring back to FIG. 1, operation of the furniture control system is described. The first control unit CU1 is configured to control the first actuator based on the first actuation data actd1, and the second control unit CU2 is configured to control the second actuator ACT2 based on the second actuation data actd2.

[0053] During operation of the furniture control system, a user may initiate a command via the user input device UID. This command is provided for example to the first control unit CU1. The first control unit CU1 recognizes the command as an event that, for example, is suitable for inducing a change of state of at least one of the first and the second actuators ACT1, ACT2. Consequently, the first control unit CU1 generates or derives first actuation data actd1 from the command, respectively event, and stores the actuation data actd1 in the first data pool unit DP1. In other words, the content of the data stored in the data pool unit DP1 is changed. Upon this change, respectively the detection of such change, the data pool DP, respectively the control system, initiates a synchronization between the first and the second data pool unit DP1, DP2, such that the first actuation data actd1 are synchronized to the second actuation data actd2 stored in the second data pool unit DP2.

[0054] Preferably, such synchronization DPSYNC is transparent to the user and even to the control unit CU1, CU2. For example, a specific synchronization protocol is established between the first and the second data pool unit DP1, DP2. The communication between the data pool units DP1, DP2 for this synchronization DP SYNC takes place over a tethered or wired connection or via a wireless connection, whatever is more suitable in the respective configuration.

[0055] After completion of the synchronization process, the first and the second control units execute the respective driving command defined by the actuation data actd1, actd2, thereby ensuring synchronicity between the two actuators ACT1, ACT2.

[0056] As indicted by the ellipsis symbol in the data pool DP, the furniture control system may include further control units with respective data pool units that may be synchronized in the same manner as described above.

[0057] In preferable implementations the control system is configured to withhold from synchronizing the first and second data pool unit DP1, DP2 if no change of any of the data stored in the data pool units DP1, DP2 occurs. Moreover, preferably the first and the second data pool units DP1, DP2 withhold from communicating with each other if no change of any of the data stored in the first and the second data pool unit DP1, DP2 occurs.

[0058] However, besides the actuation data actd1, actd2, the data pool units DP1, DP2 may be configured to also store the event data evnt1, evnt2. Such event data generally may relate to event information that is suitable for inducing a change of state of at least one of the first and the second actuator ACT1, ACT2.

[0059] FIG. 4 shows a further example implementation of a furniture control system according to the improved communication concept that is based on the embodiment of FIG. 1. A main difference is given by the implementation and inclusion of the user interface device into the control system, e.g. into the data pool DP. Hence, only those differences will be described in the following.

[0060] In the example implementation of FIG. 4, the user interface device UID includes a separate data pool unit DPU that is part of the data pool DP together with its synchronization mechanism. For example, a user-induced event can be directly stored in the data pool unit DPU, which will be synchronized to the other data pool units DP1, DP2 after detection of the changed data. Following that synchronization, at least one of the control units may generate respective actuation data that will also be synchronized. After that synchronization, a respective driving command associated with the actuation data can be executed, i.e. the actuators ACT1, ACT2 perform the desired action.

[0061] It should be apparent to the skilled reader that also the implementation of FIG. 4 can be applied to the furniture systems shown in FIG. 2 and FIG. 3.

[0062] The scenario shown in FIG. 5A to FIG. 5F shows the usage of the improved communication concept based on the following system structure:

[0063] two cascaded control units: first control unit CU1 and second control unit CU2;

[0064] one actuator is connected to each of the control units; actuator ACT1 is connected to first control unit CU1 and actuator ACT2 is connected to second control unit CU2;

[0065] a user input device UID, such as a handset, is connected to first control unit CU1.

[0066] FIG. 5A shows the state of the system and the data pool DP in idle state. The user presses the Memo1 button on the handset UID, and the first control unit CU1 receives the handset command. No other communications are shown taking place. In this scenario the handset communication protocol does not matter.

[0067] After receiving the command from the handset UID, the first control unit CU1 transforms the handset command Memo1 to a target positions of 20.0, and sends the desired user input to the data pool DP as depicted in FIG. 5B. The data pool DP can be seen as a virtual blackboard, in practice a memory structure within the control units and appropriate R/W methods represent the data pool DP. No other communications are shown taking place.

[0068] After both control units CU1, CU2 received/read the new information written to the data pool DP, that is driven to position 20.0 (in this example, position 20.0 has been stored as memory position 1), each control unit independently sets its target position to 20.0 as shown in FIG. 5C. At this point in time the movement of the actuators ACT1 and ACT2 starts. Based on a soft start mechanism the desired position for the next time interval (e.g. 1 s) is computed.

[0069] After this time period the actuators ACT1 and ACT2 of each of the control units CU1 and CU2 approximately reach the desired position for this point in time as shown in FIG. 5D. Due to individual deviations such as load conditions the positions reached may vary within a certain limit, or at different driving speeds. In another aspect of the disclosure, the driving rates can be synchronized or aligned for co-movement between the multiple motors of the actuators ACT1, ACT2. In another aspect, the cascading communication addressed within this disclosure can include synchronized co-movement of multiple motors. The phrase within a certain limit can refer to when a motor, respectively actuator, reaches its final position, there is usually a deceleration ramp in place, i.e. the motor does not stop from 5000 rpm to 0 rpm within one step. Based on the actual mechanical load of the motor the last few revolutions of two synchronized motors might differ, i.e. the first actuator ACT1 stops after a total of 50.000 revolutions, the second actuator ACT2 stops after a total of 49.970 revolutions.

[0070] FIG. 5E shows the driving example further advanced in time. The control units CU1 and CU2 perform identical computations, and thus, they keep the positions of the actuators ACT1 and ACT2 synchronized.

[0071] FIG. 5F shows the end of the driving scenario. The actuators ACT1 and ACT2 connected to the control units CU1 and CU2, respectively, have reached their target position within a certain limit. The control units CU1 and CU2 have stopped their driving routine. The illustrated aspect of the disclosure shows a certain limit of 0.1 positional units. Higher or lower tolerances can be included.

[0072] This driving example impressively shows the following: except for two points in time no communication is necessary between the cascaded control units. These two points are shown in FIG. 5B where the first control unit CU1 writes the driving command to the data pool DP and in FIG. 5C where the first control unit CU1 and second control unit CU2 read the driving command together with the target value from the data pool DP.