Overview
The zc-smart-blind has a Fixed Calibration mode where the product does not require an initial calibration, nor does it perform self calibration. When in this mode, the product will not adhere to the current draw of the output and will instead run for the fixed period given. This allows for the use of outputs with a current draw lower than the specification. The zc-smart-blind modes and how to configure them can be found here.
No restart of device is required for these modifications to occur.
Configuring Fixed Calibration Period
The zc-smart-blind Fixed Calibration mode has a default calibration period of 30 seconds.
To calibrate the product the recommended process is to perform the following. Where you expect your runtime to be more than 30s, you should first update the timing to be longer than the default.
- Send Recall max
- Wait 60 seconds (or longer if you modified the time)
- Send Off
- Time the time in seconds rounded up for the blind to close completely
- Wait 60 seconds (or longer if you modified the time)
- Send Recall Max
- Time the time in seconds rounded up for the blind to open completely
- Set the times in the zencontrol cloud or via eDali as below.
Using the zencontrol Cloud
Make sure that the devices operation mode has been set to Fixed Calibration Mode before continuing.
On the zencontrol cloud this calibration is configurable via the Grid View>Device Types>Relay page. On this page, modifying the up on threshold and up off threshold will set configurations.
- Up on threshold is the time that the blind takes to go from the bottom to the top in seconds.
-
Up off threshold is the time that the blind takes to go from the top to the bottom in seconds
To make the arc level track the blind’s movement, adjust the product’s fade rate and fade time to match the configured travel time.
-
Fade rate: Calculate the required number of steps per 200 ms using:
Steps per 200 ms = 254 ÷ (travel time in seconds ÷ 0.2)
For example, a travel time of 10 seconds requires approximately 5 steps per 200 ms. Select the supported fade rate closest to this value.
- Fade time: Select the available fade time or extended fade time closest to the configured travel time. For example, if the blind takes 10 seconds to travel, select the setting closest to 10 seconds.
Overrun Time (introduced in v2.112)
As of firmware v2.112, blind controllers support an overrun time setting. This feature allows the controller to recover from limit-inducing commands by giving the blind extra time to reach its full top or bottom position, even if travel-time drift would otherwise leave it short. If you can get stuck at a position, you can continuously send the limit command (OFF / RECALL MAX) to get the blind back its limit.
- Down on threshold overrun: the additional time the blind will run past the calculated point when it receives an RECALL MAX command, to ensure it reaches the bottom limit.
- Down Off threshold overrun: the additional time the blind will run past the calculated point when it receives a OFF command, to ensure it reaches the top limit.
Using Express 2 (beta)
You can also use the express 2 beta app to connect to the device via bluetooth. This app allows you to configure the run times and will automatically set the fade time and fade rate.
You need to ensure you have change the operating mode of the smart blind to Fixed Calibration Mode to be able to configure the blind manually.
Using Raw Dali commands
This value can be modified by;
eDali
To modify the calibration period over edali, you should;
- Set ECG DTR2 to 21 (0x15)
- Set ECG DTR0 to the desired calibration period in seconds
- Send 0xDDxxC1
- Where xx is the ECG address byte (as documented in IEC 62386-102)
How to Query
This value can be queried by;
eDali
To query the calibration period over edali, you should;
- Set ECG DTR2 to 20 (0x14)
- Send 0xDDxxC1
- Where xx is the ECG address byte (as documented in IEC 62386-102)
- Set ECG DTR0 to 0 (0x0)
- Send 0xDDxxC2
- Where xx is the ECG address byte (as documented in IEC 62386-102)
- The reply will be the fixed calibration period in seconds
Comments
0 comments
Article is closed for comments.