# SAMPLE

<figure><img src="https://lh7-us.googleusercontent.com/slidesz/AGV_vUcB3kAZ6N01WvgPq_pzLqFTvxIr2kNmEUEq4qJii5dw_T5KBcvLZjM7eZ7lxibwWtfub6Dde1CkWJXbBKwj8CnimQyLdGUwRAcgOnI9AgtimSTxKMmw-HdnU5iQZj2AoGPfAsTo1sf4bw9dQhyy5AhYXwMTiP0B=s2048?key=npIi8zOHIy81LrwrrhJT2w" alt=""><figcaption></figcaption></figure>

In this example, the **Astronomical Clock** is configured to control garden lighting in Istanbul. It turns off the lighting at sunrise (by sending a "0" when it receives a "1") and turns it on at sunset. The region can be adjusted within the block settings.

The **Schedule** is set to turn on the door lighting at a specific time. It incorporates a **Delay** of 5000 milliseconds, so the lighting will activate 5 seconds after the command is received. The **Scenario** connected to the trigger allows for manual activation of the scenario without waiting for the scheduled time.

It's important to note that the Schedule block in this setup is designed for a single command—either turning the lighting on or off. In this scenario, it is used to turn the lighting on. If it is also necessary to turn the lighting off, a second Schedule block must be added.

\


<figure><img src="https://lh7-us.googleusercontent.com/slidesz/AGV_vUcYciP1J9ID3-q-jWyOLbK-3c0oFj0j-EOCbpxjRaalJeyLEOw9wDugZmviVFZ3U0nyz-PatDPQRPXVMB0BlyWhlmrL9Q4F3CJf5tPTIkdJkCBlJOxt1tTutD1Yc4r-0LPBGBO0uxEnjVtmZvABaUmVcKeGWIBb=s2048?key=npIi8zOHIy81LrwrrhJT2w" alt=""><figcaption></figcaption></figure>

In the example setup, the **VRF Schedule** object is used in conjunction with the VRF block and UI. The connection is established with the assumption that the air conditioner can be controlled both from the UI and through the wired controller of the unit.

In this configuration, all commands—whether came from the UI or directly from the VRF unit—are routed through the **VRF Schedule** object. This ensures that all controls are managed and monitored effectively, allowing for centralized control over the VRF system.

\
