> 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-simulation-and-monitor.md). # Testing — Simulation and Monitor *Part 3 — Reference.* *** ## 26.1 Two different tools | | **Simulation** | **Monitor** | | -------------------- | --------------------------------------------- | ------------------------------------- | | Where | **Simulation** workspace tab | **Managers** → **Monitor** | | Needs a central unit | **No** | **Yes** | | Shows | what your logic *would* do | what the installation *is* doing | | Use it | while writing rules, before you have hardware | while commissioning and fault-finding | They answer different questions. Simulation asks *"is my logic right?"*. Monitor asks *"what is actually happening?"*. *** ## 26.2 Simulation Switch to the **Simulation** workspace tab and click objects on the floor plan. iDM3 evaluates your wires and shows the result. **What it catches:** a wire pointing the wrong way, a missing function, an action on the wrong button, a condition that never passes, a group with the wrong members. **What it cannot catch:** wrong addresses, unassigned icons, faulty wiring, missing units, timing that only matters on real hardware, anything involving GSM or the network. > **Simulate before you drive to site.** Logic errors found on your desk cost minutes; the same errors found on a ladder cost an afternoon. The floor plan image opacity for this tab is set separately in `[☰]` → **Settings** → **Floors image opacity** → **Simulation:**. *** ## 26.3 Monitor **Managers** → **Monitor**. Live data from the central unit. You must be `Connected`. ### Tabs | Tab | Shows | | ------------------- | ------------------------------------------------------- | | **Devices** | Every device and its live state | | **Timers** | **Timer name**, **Timer value**, **Timing value** | | **Counters** | **Counter name**, **Counter value**, **Counting value** | | **System bits** | Each bit's live state | | **System ints** | Each integer's live value | | **System programs** | Which programs are active | | **Heat/Cool areas** | The full heating picture — see below | | **EZS** | Security system state | | **GSM** | GSM module state | Common columns: **Status**, **Name**, **Value**. **Dynamic** controls live updating. ### Filters Large installations need them: | Filter | Narrows by | | ------------------------- | ------------------------- | | **Structure state** | position in the structure | | **Modules only** | modules, hiding units | | **Module filter** | a specific module | | **Unit type filter** | unit type | | **Devices filter** | specific devices | | **Device type filter** | device type | | **Active** / **Inactive** | current state | Right-click offers **Expand All** and **Collapse All**, and — on card data — **Copy card number** and **Paste card number**. ### Heat/Cool areas The most informative tab, because heating is otherwise invisible: | Row | Meaning | | ----------------------------------------------- | ---------------------------------- | | **Actual-Therm-AOUT** | Measured temperature | | **Required-Therm-AOUT** | Wanted temperature | | **Required-Heat-AOUT** / **Required-Cool-AOUT** | Heating and cooling demand | | **Required-Cool-Therm-AOUT** | Wanted cooling temperature | | **Maximal-Therm-AOUT** | Upper limit | | **Antifreeze-Therm-AOUT** | Lower limit | | **Critical-Therm-AOUT** | Critical sensor, for floor heating | | **Correction** | Applied correction | | **Window-Detector-DIN** | Window open | | **Control-IN** | Control input | | **Control-Manual-IN** | Manual override active | | **Control-Plan-IN** | Following the time plan | | **Control-HC-IN** | Heating/cooling selection | | **Status-AOUT** | Regulator status | | **HU** / **HSU** | Heating unit / heating source unit | | **CU** / **CSU** | Cooling unit / cooling source unit | **Compare Actual against Required.** If they match and nothing is heating, the fault is electrical. If Required is not what your schedule says, the fault is in the area configuration. ### Project comparison | Indicator | Meaning | | ------------------------------------ | ---------------------------------- | | **Set actions simulated by CU** | Action set the CU is running | | **Structure simulated on CU** | Structure the CU is running | | **System structure simulated on CU** | System structure the CU is running | These tell you whether the CU is running what you think it is — [Chapter 23](/inels-bus/inels-design-manager-idm3/connecting-and-uploading-to-the-central-unit.md). *** ## 26.4 Device monitoring The **Device manager** has its own **Monitoring** tab per device — live values for the selected unit, without leaving the tree. Useful while checking addresses. *** ## 26.5 A fault-finding order When something does not work, in this order: | # | Check | Where | | - | ------------------------------------------ | -------------------------------------------- | | 1 | Did the upload succeed? | Information console | | 2 | Is the CU running your project? | *"Projects are the same."* | | 3 | Is the logic right? | **Simulation** | | 4 | Are there yellow dots? | **Design** tab | | 5 | Are the addresses right? | **Device manager** | | 6 | Is the input arriving? | **Monitor → Devices** | | 7 | Is the output switching? | **Monitor → Devices** | | 8 | If the output switches but nothing happens | The fault is electrical, not in your project | Steps 6 and 7 are the ones that settle arguments. If Monitor shows the relay switching and the light stays off, the project is correct and the wiring is not. *** **Next:** [Chapter 27 — Settings and Preferences](/inels-bus/inels-design-manager-idm3/idm3-settings-and-preferences.md). *** ### Also on this wiki * [iDM Bus Analysis and Troubleshooting Software](https://wiki.inels.com/inels-bus/how-to-get-started/idm-bus-analysis-and-troubleshooting-software)