For the complete documentation index, see llms.txt. This page is also available as Markdown.

Appendix F — Files and folders

Where iDM3 keeps everything, and what is safe to touch.


Install location

By default, inside your user profile — no administrator rights needed:

%USERPROFILE%\ELKO EP\iNELS BUS System\iNELS3 03.05.03 Designer & Manager for CU3-07M

The folder name still says "for CU3-07M". Historical naming — this version supports CU3-08M, CU3-09M and CU3-10M as well, and CU3-07M is obsolete. See Chapter 3.


What is in there

Item
Contents
Safe to touch?

IDM3.exe

The program

Don't

IDM3.SuperUser.cmd

Launches super-user mode

Only when support asks

Projects\

Your .elp project files

Back this up

funcBloks\

Function block templates (.fncb)

Back this up

Firmwares\

~170 firmware packages

Don't

Documentation\

Installation manual, change log, firmware history

Read freely

Languages\

Interface translations (.lang)

Don't

Images\, gallery\

Icons and floor-plan images

gallery holds your images

web\

Web content

Don't

_updater\

Update mechanism

Don't

ELKODefaultProject\

The factory default project

Don't

storage\, spool\, TMP\

Working folders iDM3 manages itself

Leave alone

default.elp

Factory default

Don't

userDefault.elp

Your saved default

Yours

UserSett.hdb

Your settings — survives reinstalls

Yours

IDM.config

Program configuration

Don't

News.hdb

News

Don't

cmp.exe

The project compiler

Don't

firmDepends.xml

Firmware dependencies

Don't

elkoep.ico

Application icon


Log files

In the install folder. Attach these when contacting support.

File
Contents

IDM.log

General application log

comunication.log

Communication with the central unit (spelled that way)

monitoring.log

Monitoring activity

monitorData.log

Monitored data

Exception.excp

The last unhandled exception


Inside a project file

An .elp is a ZIP archive of XML files. You never need to open it this way, but it explains why .elp files compress well and why a damaged archive loses everything rather than part.

File inside
Holds

project.xml

Floors, users, gallery, version, encryption flag

projectInfo.xml

Version and structure version

config.xml

Project configuration

cuSettings.xml

Central unit settings

functions.xml

User functions — 61 of them in the default project

wires.xml

Wires

groups.xml

Groups

macros.xml

Macros

programs.xml

Time programs

system-devices.xml

Timers, counters, system bits and integers

persons.xml

People

contacts.xml

Phone numbers

DT_Notices.xml

Notices

DT_funcBlocks

Function blocks used

RT_Relations

Relations


Windows registry

HKCU\Software\ELKO EP\iDM3

Value
Contents

InstallDir

Install location

Version

Version and revision

Plus an uninstall entry under HKCU\Software\Microsoft\Windows\CurrentVersion\Uninstall\iDM3.


What survives an uninstall

The uninstaller deliberately leaves:

  • Projects\ — your projects

  • funcBloks\ — your function block templates

  • gallery\, web\, _updater\

  • UserSett.hdb — your settings

Copy your projects out before deleting the folder by hand.


What to back up

Priority
What
Why

1

Projects\*.elp

Irreplaceable

2

funcBloks\*.fncb

Not stored in the project file

3

userDefault.elp

Your company standard

4

UserSett.hdb

Convenience

Priority 2 catches people out. A project using custom function blocks is incomplete without the templates, and they live outside the .elp. Either back the folder up, or turn on SettingsSave function blocks templates to project file.


See also: Chapter 3 — Install iDM3 · Chapter 15 — Projects and files