GettingStartedControls Solution
Overview
The GettingStartedControls solution is a sample solution for a gauge cluster and a center cluster. Various controls are used to realize an advanced gauge cluster and a center cluster. In addition, interactions between those controls are built to realize HMI logic.
For information on how to create the main scenes of this sample solution and how to implement HMI logic using controls, please refer to GettingStartedControls tutorial.
Description
Scene
The GettingStartedControls solution consists of the scenes listed in the table below.
| Scene name | Description |
| SceneHome |
Scene for the main screen. The speedometer is displayed in the center of the screen, and navigation information, time, display, various indicators, etc. are displayed around it. In addition, the SceneMenuTabs scene is overlaid at the bottom of the display area. |
| SceneClimate | Scenes for screen for air conditioners and various heaters setting. |
| ScenePhone | Scene for the phone screen. Displays the phone book, dialing, answering, and number of incoming calls. |
| SceneOptions | A scene for the selection screen of various settings. |
| ClimateOptions | Scene for the setting screen of air conditioners and various heaters. |
| SoundOptions | A scene for audio-related settings screen. |
| TimeOptions | A scene for time-related settings screen. |
| PhoneOptions | A scene for phone-related settings screen. |
| ConnectionOptions | A scene for the phone connection settings screen. |
| SceneMenuTabs |
Scene for the screen switching tabs of SceneHome/SceneClimate/ScenePhone/SceneOptions. |
| SceneBack | Background scene. |
| SceneBreadcrumb | A scene for the breadcrumb list that appears at the top of SceneOptions. |
Control
The following table lists the featured controls used in the GettingStartedControls solution. For more information about each control, please refer to Predefined Controls.
| Control name | Description |
| BreadCrumb | The Options screen was mainly introduced to show how the BreadCrumb works. There are various subscreens in the options menu that can be accessed via the BreadCrumb. Further wise a state machine has been added just for the BreadCrumb which manages the transitions between the BreadCrumb scenes and the BreadCrumb actions. |
| List | The phone screen consists of a dynamic list. It is important to know that in the Player some code had to be implemented that allows phone-book entries and adding them. By pressing the "Add Contact"-Button of the phone screen a input mask will appear that allows to pass contact data. |
| Drawer |
The drawer is used two times in the sample. First of all the menu in the bottom of the screen appears as a drawer if the user hovers over the corresponding Control (at the bottom of the screen). To close the menu-drawer the "X"-Button in the right side of the menu has to be pressed. The second appearance of the Drawer Control is in the phone screen. The input mask after pressing the "Add Contact"-Button is realized as a drawer. |
| Roll | The time-options screen includes three rolls for setting the time (seconds, minutes and hours). |
| Keyboard | When clicking on of the time-rolls an on-screen keyboard appears which allows setting the time-values. |
| Various Core Controls | In the SoundOptions scene, Core controls are used to display various audio-related settings. |
This Core Controls sample solution showcases a lightweight Control Set optimized for low-end devices. It includes only essential controls, enabling safe performance testing and validation on memory-constrained platforms.
Behavior
Behaviors are set for each control to exchange data with other nodes as needed. Behavior settings can be viewed in the Extra Scene Tree or Fusion panel of the relevant node.
The image below shows an example of behavior settings for Button_TempInc (Button control) in the SceneClimate scene. Button_TempInc is a button used to increase the air conditioner's temperature setting in 0.5°C increments. Due to the behavior settings, each time Button_TempInc is pressed, a value of 0.5 is passed to Slider_Temperature (Slider control), synchronizing the button press action with the slider display.
State Machine
The transitions between each scene are configured using a State Machine (MenuStateMachine). Subchart is used for transitions between option scenes.
The configuration of the State Machine transitions of between scenes can be viewed in the State Machine Editor.
Transition
A Slide transition is set for transitions between SceneHome, SceneClimate, ScenePhone, and SceneOptions scenes. This causes a scene to slide from left to right to reveal the next scene. A Fade transition is set for transitions between option-related scenes (achieved using a Variant in the Transition Rule Editor).
Transition settings can be viewed in the Transition Rule Editor.
Play/Operation using Player
Click the [ Play Selected Scenario... ] icon on the toolbar to launch the Player, and the Advanced Cluster solution will be displayed in the Player view. The UI on the right side of the display screen allows you to control the display of the main screen.
The initial screen of the GettingStartedControls solution is the SceneHome scene. If you move the cursor to the bottom of the screen, a tab menu will appear, and you can move to each scene from the tab menu. In each scene, you can check the operation of various controls used in the GettingStartedControl solution.
| (1) | Each time you click, the display screen will change in the following order: SceneHome -> SceneClimate -> ScenePhone -> SceneOptions (after SceneOptions, you will return to SceneHome). |
| (2) | When clicked, SceneHome will be displayed. |
| (3) | When clicked, SceneClimate will be displayed. |
| (4) | When clicked, ScenePhone will be displayed. |
| (5) | When clicked, SceneOptions will be displayed. |
| (6) | When clicked, the SceneMenuTabs will be hidden. |
From the SceneOptions scene, you can transition to scenes for various options.
