> For the complete documentation index, see [llms.txt](https://wiki.inels.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.inels.com/inels-bus/inels-design-manager-idm3/idm3-managers-reference.md). # Managers *Part 3 — Reference.* *** ## 19.1 Where the managers are **Six** buttons on the **Managers** ribbon tab: | Button | Covered in | | ------------------------- | ----------------------------------------------------------------------------------- | | **Group manager** | §19.2 | | **System manager** | [Chapter 20](/inels-bus/inels-design-manager-idm3/idm3-system-manager-reference.md) | | **Persons manager** | §19.5 | | **Communication centrum** | §19.6 | | **Dali manager** | [Chapter 21](/inels-bus/inels-design-manager-idm3/idm3-dali-manager-reference.md) | | **Monitor** | [Chapter 26](/inels-bus/inels-design-manager-idm3/idm3-simulation-and-monitor.md) | **Four** more on the **Functions** ribbon tab: | Button | Covered in | | -------------------------- | ------------------------------------------------------------------------------------------ | | **Wire manager** | [Chapter 18](/inels-bus/inels-design-manager-idm3/idm3-wire-editor-reference.md) | | **Function manager** | §19.3 | | **Macro manager** | §19.4 | | **Function block manager** | [Tutorial 10](/inels-bus/inels-design-manager-idm3/tutorial-macros-and-function-blocks.md) | And **Device manager** on the **Project** tab — [Chapter 16](/inels-bus/inels-design-manager-idm3/idm3-device-manager-reference.md). > **Managers that no longer exist as buttons.** Older documentation refers to a *Program manager*, *Alarm manager*, *Message manager*, *Periodic action manager*, *User manager* and *Heat cool program manager*. **In 3.5.3 these are not separate buttons.** Programs and heating live inside **System manager**; messages inside **Communication centrum**; alarms are a group type. The old labels survive in the software's translation files but nothing opens them. *** ## 19.2 Group manager **Managers** → **Group manager**. Groups let many consumers be controlled as one. | Side | Contents | | ------------------ | ------------------------------------------------------------------------- | | **Groups** (left) | Existing groups — name and type. **Add** and **Delete** above the list. | | **Detail** (right) | **Unicate name:** and **Type**, with **✓** to confirm and **✗** to cancel | Types: `Digital` (outputs), `Analog` (outputs), `Alarm` (inputs), `Temperature`. Defining a group does not fill it. Members are added on the **Groups** workspace tab — click the group icon so it turns blue, then click each object to add it. Full walkthrough: [Tutorial 4](/inels-bus/inels-design-manager-idm3/tutorial-groups-and-scenes.md). *** ## 19.3 Function manager **Functions** → **Function manager**. Defines the named, reusable effects that wires use. | Side | Contents | | ----- | ----------------------------------------------------------------------------------------- | | Left | Defined functions — name, function, parameters. **+** adds, **–** deletes. | | Right | **Name:**, **Function type:**, **Select function:**, and the **Params** for that function | **✓** saves, **✗** discards. Clicking an existing entry opens it for editing; changes show immediately in the list and are applied with **✓**. The grid columns include **Unicate function key**, **Name** and **Function**. **Function type** determines which effects **Select function** offers: | Type | For | | ---------- | --------------------------------- | | `Digital` | relay outputs | | `Analog` | dimmers | | `Timer` | timers | | `Counter` | counters | | `Alarm` | alarm groups | | `HeatCool` | heating and cooling areas | | `Group` | groups | | `System` | system bits, integers, GSM, email | **A project started from the default arrives with 61 functions already defined** — see [Appendix B](/inels-bus/inels-design-manager-idm3/idm3-function-reference.md). *** ## 19.4 Macro manager **Functions** → **Macro manager**. A macro is a saved bundle of actions and functions applied to wires as you draw them. | Side | Contents | | ----- | ------------------------------------------------------------------------------- | | Left | Macros by name, with add, copy and delete buttons | | Right | **Name**, **Type** (the **actor** type), **Description**, and the function list | Buttons: **Add macro**, **Edit macro**, **Copy macro**, **Remove function** — the first three open the **Wire function** window. To apply: tick **Use selected macro** on the **Functions** ribbon tab, pick the macro, then draw wires. Any wire whose actor type matches is filled in automatically. > **A macro is copied into the wire, not linked.** Editing it later does not change wires already made. *** ## 19.5 Persons manager **Managers** → **Persons manager**. People, their access cards, and their contact details. ### Person details | Field | | ----------------------------- | | **Name** | | **Surname** | | **Password** | | **Email** | | **Phone** | | **Card n.** / **Card number** | | **PIN** | **Read card number** puts a reader into learn mode — it shows **Reading...** while waiting, and you present the card. Far more reliable than typing a card number by hand. **Select card reader** chooses which reader to read from. Right-click offers **Copy card number** and **Paste card number**. ### Tabs | Tab | Contents | | ---------------- | ---------------------------------------------------- | | **Contacts** | Phone numbers, shared with the Communication centrum | | **EZS zones** | Which security zones this person may use | | **Card readers** | Which readers accept their card | **Select and add item...** adds entries to these lists. > **Card numbers, PINs and passwords are credentials.** Treat a project file containing them accordingly — do not email `.elp` files around, and do not leave them on shared drives. *** ## 19.6 Communication centrum **Managers** → **Communication centrum**. SMS, calls and contacts. Needs a **GSM3-01M**. ### Contacts | Field | Notes | | ----------- | --------------------------------------------------------------- | | **Value:** | The phone number, in **international format** — `+420xxxyyyyyy` | | **Person:** | Filled from the Persons manager | | **GSM:** | Click the plug icon to bind the number to a GSM unit | **The plug must turn green.** A red plug means nothing will be sent or received on that number. Deleting a number removes it from every message and call slot that used it. ### Messages | Field | | ----------- | | **Name:** | | **Type:** | | **Body:** | | **Phones:** | | List | Slots | Behaviour | | ---------------- | ----- | ----------------------------------------------------------- | | **Income SMS** | 32 | Matches arriving text; sets `SMS IN` **ON for one second** | | **Outcome SMS** | 32 | Sends to up to **8** numbers | | **Income call** | 8 | `CALL IN` is ON for the duration of a call from that number | | **Outcome call** | 8 | Dials for **20 seconds** | **Text length is limited to 32 characters.** ### Notices Logs **Income SMS**, **Outcome SMS**, **Income call** and **Outcome call** traffic. The first place to look when messaging misbehaves. Full walkthrough: [Tutorial 9](/inels-bus/inels-design-manager-idm3/tutorial-alarms-and-sms-messaging.md). *** **Next:** [Chapter 20 — System manager](/inels-bus/inels-design-manager-idm3/idm3-system-manager-reference.md).