Troubleshooting
Part 4 — Operate and fix.
30.1 Start here
Nine times out of ten it is one of these:
1
Yellow dots on a floor plan
Design tab
2
Addresses do not match the hardware
Device manager
3
The project was never uploaded
[☰] → Save to central unit
4
The CU is running a different project
"Projects are the same."
5
The wire points the wrong way
Wire manager — actor and consumer
6
The wire has no function on it
Wire manager → Functions:
7
A condition never passes
Wire function → Conditions
8
The function is the wrong type
Digital on a dimmer, or the reverse
9
The fault is electrical, not in the project
Monitor — is the output switching?
Check 9 settles most arguments. If Monitor shows the relay switching and the light stays off, your project is right and the wiring is not.
30.2 Connection problems
Disconnected
No connection
Check IP, cabling, power
BadPassword — "Please try it again."
Wrong CU password
Get the right one
Error
Connection failed
Read the information console
Ping test fails
It is a network problem
Fix the network before anything else
Run Ping test first, always. It separates a network fault from a software fault in one click.
30.3 Compile errors
When iDM3 cannot turn your project into something the CU can run, the Compile error button on the Project ribbon tab lights up. Nothing is uploaded.
Click it and read the error. Common causes: a device removed but still referenced, a function whose type no longer matches its consumer, a condition pointing at something deleted, an exceeded limit.
30.4 CU error codes
[☰] → CU configuration → CU setting shows Error code:, with Title:, Body:, ExtendedInfo: and Code:.
Reset error clears it — but read it first. A code that returns immediately is telling you something.
The full code list is in Advance/Languages/CUErrors.*.lang, and Rev19 chapter 18 has a state-code overview.
30.5 Project and device messages
"Projects are NOT the same!"
The CU is running something different
"Projects tree is [x], system tree is [y]."
Which parts differ
"Unable to delete this object because is i use!"
Something still references it
"Not remapped devices detected"
Devices left unmapped after conversion
"Please remap device or change/remove its links"
Use ReMap unit
"Module type [0x…] is not supported."
Not available in this version
"Max count of modules type"
A module limit reached
"The item can not be inserted here!"
Wrong place in the device tree
"Unable to add item"
Usually a group type mismatch
"Error when loading file."
The project file may be damaged
"Unable to find selected disk location!"
Use Save as and choose a new path
30.6 iDM3 itself
Will not start
Confirm .NET Framework 4.8
Starts then closes
Read Exception.excp and IDM.log
Opens with a project error
New, then reopen your project
Wrong language
Settings → Localization → Select language
A recent project will not open
"File '…' could not be opened. Do you want to remove this item from Recent list?" — the file moved or is damaged
Very slow on a large project
Turn off both animations in Settings → Visual effects
Log files
In the install folder:
IDM.log
General application log
comunication.log
Communication with the CU (spelled that way)
monitoring.log
Monitoring activity
monitorData.log
Monitored data
Exception.excp
The last unhandled exception
Attach these when contacting support. They usually contain the answer.
30.7 Behaviour that looks wrong but is not
Pressing the button again does nothing
Digital switch ON is not toggle — use DIGITAL_SWITCH
The impulse does not restart on a second press
Digital_Impulse_ON ignores an output already on — use a timer
The light runs to 100 % after dimming
Missing ANALOG_STOP_LEVEL_CHANGE on Long up
A 10-second ramp takes 2 seconds
Ramp length is the 0→100 % time; partial changes are proportional
A group refuses a device
Wrong group type — relays and dimmers cannot share a group
The dimmer forgets its level
Analog switch value only moves between 0 % and 100 %
A program cannot be saved
No day or month ticked in Periodical settings
Sunset switching is an hour out
The CU's Time zone
Holiday mode lost after a power cut
non volatile not ticked on the system bit
SMS never arrives
The GSM: plug is red, not green
An incoming SMS does nothing lasting
It gives a one-second pulse — latch it into a system bit
A function block does nothing
Its inputs and outputs are not plugged in, or Connect was not pressed
A macro did not apply
Its Type does not match the actor type
Editing a macro changed nothing
Macros are copied into wires, not linked
30.8 Heating
Nothing heats
Monitor → Heat/Cool areas — is Required-Heat-AOUT demanding?
Required temperature is wrong
The time plan, and which plan the area uses
Heating and cooling fight
Check the difference between temperature of heating and cooling → On
One room never heats
Its Heating output; the shared Heating supply
No room heats
The Heating supply relay
It heats then stops
Maximal temperature; the window detector
It runs all night
The schedule; look for a stuck manual override
Monitor → Heat/Cool areas is the tool for all of these. Comparing Actual-Therm-AOUT with Required-Therm-AOUT tells you immediately whether the problem is the schedule or the plumbing.
30.9 Getting help
Installation manual
Advance/Documentation/EN_iDM3_installation_manual_Rev19.pdf
Change log
Advance/Documentation/Change log.txt
Minimum firmware versions
Advance/Documentation/Recommended minimal firmware version.txt
Firmware history
Advance/Documentation/Firmware history\
MQTT unit support
Advance/Documentation/BUS unit to MQTT.txt
ELKO EP
Extended history
http://www.inels.com/idm3
When contacting support, have ready: the iDM3 version and revision, the CU type and firmware version, the project file, and the log files from §30.6.
Back to the index.