Didactum Monitoring & InterMapper Integration
Complete step-by-step guide for integrating Didactum monitoring devices and sensors into InterMapper (Fortra InterMapper) via SNMP – including the device on the map, Basic OID probe, complete custom SNMP probe file for all sensor types, SNMP trap probe, and email notifier.
Product note: InterMapper was acquired by HelpSystems (now Fortra). The product is officially called Fortra InterMapper. All configuration steps apply equally to InterMapper 6.x and current Fortra versions. InterMapper supports SNMP v1, v2c, and v3 and allows the creation of fully customized probe files for any SNMP device.
- Software: Fortra InterMapper (formerly HelpSystems / Dartware InterMapper)
- Configuration: Web interface + custom probe files (text format)
- Protocol: SNMP v1 / v2c / v3
- Devices: Didactum Monitoring System 100T / 300T / 500T / 550T
- Sensors: Temperature, leakage, humidity, door contact, smoke
1. Prerequisites & System Overview
InterMapper server
- InterMapper Server installed (Windows, macOS, or Linux)
- InterMapper RemoteAccess or web interface reachable
- UDP port 161 open outbound for SNMP polling
- UDP port 162 open inbound for SNMP traps
- Network access to the Didactum device
Didactum device
- Monitoring System 100T, 300T, 500T, or 550T
- SNMP enabled (v2c recommended)
- Device reachable by ICMP (ping) from the InterMapper server
- MIB file available in the web interface
InterMapper probe directories
Windows: C:\Program Files\InterMapper\InterMapper Settings\Probes\ macOS: /var/db/intermapper/InterMapper Settings/Probes/ Linux: /var/db/intermapper/InterMapper Settings/Probes/ Recommended subfolder: Probes/com.didactum/ <-- store custom Didactum probes here
2. Enable SNMP on the Didactum device
Step 1 – Open the web interface
Open in browser: 192.168.1.50 (adjust the IP of the Didactum device)
Step 2 – Open SNMP settings
System settings → SNMP
Step 3 – Enter the following values
| Field in the Didactum web interface | Value |
|---|---|
| Enable SNMP | Enabled |
| SNMP version | v2c (recommended) |
| Community string | didactum_imap (do not use "public"!) |
| SNMP port | 161 |
| Trap receiver IP | 192.168.1.10 (IP of the InterMapper server) |
| Trap port | 162 |
| Trap version | v2c |
SNMPv3 settings (optional)
| Field | Value |
|---|---|
| Security name | imap_user |
| Auth protocol | SHA |
| Auth password | at least 8 characters |
| Priv protocol | AES |
| Priv password | at least 8 characters |
| Security level | authPriv |
3. Import the MIB file into InterMapper
Symbolic OID names work only if the corresponding MIB file is loaded in InterMapper. If InterMapper cannot resolve the symbolic OID, it is treated as a syntax error. MIB import is therefore recommended, but not mandatory — numeric OIDs always work.
Step 1 – Download the MIB from the Didactum web interface
System settings → SNMP → "Download MIB file" → didactum.mib
Step 2 – Import the MIB into InterMapper
InterMapper → Menu: File → Import → MIB... → Select file didactum.mib → Open → InterMapper compiles the MIB automatically → Success message: "MIB imported successfully"
Step 3 – Check the MIB in the SNMP MIB Browser
InterMapper → Menu: Monitor → SNMP MIB Browser... → IP: 192.168.1.50 → Community: didactum_imap → OID: .1.3.6.1.4.1.46501.5.1.1 → Click "Walk" → All sensor OIDs appear in the results table
4. Add the Didactum device to the map
Step 1 – Add the device by drag & drop or menu
InterMapper Map → Menu: Insert → Device... (or double-click an empty map area)
| Field | Value |
|---|---|
| Device name / DNS name or IP | 192.168.1.50 |
| Probe type | Automatic (initially, probe will be set later) |
| SNMP community | didactum_imap |
| SNMP version | SNMPv2c |
Click OK. InterMapper immediately sends an SNMP test.
Step 2 – Assign a probe
Right-click device on map → "Set Probe..." → Select category: "SNMP" or "Custom" → Initially: "SNMP/Basic OID" for a quick test → After custom probe import (section 7): select category "Didactum/"
Step 3 – Sort the device into its own group
Map → Menu: Insert → Group... Group name: Didactum Monitoring → Drag and drop the device into the group
5. Quick start: Basic OID probe for individual sensors
The Basic OID probe retrieves a single SNMP MIB variable and compares it with defined thresholds. If the value exceeds a threshold, the device changes to the corresponding state. Ideal for an initial test without a custom probe file.
Navigation
Right-click device → "Set Probe..." → SNMP → "Basic OID"
Settings for temperature sensor
| Field | Value |
|---|---|
| Variable (OID) | .1.3.6.1.4.1.46501.5.1.1.7.101001 |
| Legend (display name) | Temperature Sensor 01 |
| Units | 0.1 degree C |
| Warning threshold | 280 (= 28.0 °C – raw value × 10) |
| Alarm threshold | 350 (= 35.0 °C – raw value × 10) |
| SNMP version | SNMPv2c |
| Read community | didactum_imap |
Settings for leakage sensor
| Field | Value |
|---|---|
| Variable (OID) | .1.3.6.1.4.1.46501.5.1.1.7.107001 |
| Legend | Leakage Sensor 01 (0=OK, 1=water) |
| Warning threshold | empty |
| Alarm threshold | 1 (from value 1 = water detected = alarm) |
Note on temperature thresholds:
Scalar values must use the suffix ".0" in their OIDs in custom probe files. In the Basic OID probe, enter the OID without a trailing .0 — InterMapper adds this automatically for scalar values. Enter all temperature thresholds × 10: 28 °C = 280.
6. Complete custom SNMP probe file for Didactum
The custom probe file monitors all Didactum sensors in a single probe, shows all values in the status window, and reacts to threshold violations with individual alarm levels.
Create probe file
Save the following file as com.didactum.monitoring.txt:
<!-- =================================================================
Didactum Monitoring System – InterMapper Custom SNMP Probe
Filename: com.didactum.monitoring.txt
Import path: InterMapper Settings/Probes/com.didactum/
Monitors: temperature sensor, leakage, humidity,
door contact, smoke detector via SNMPv2c
Enterprise OID (older devices): .1.3.6.1.4.1.46501
Enterprise OID (newer devices): .1.3.6.1.4.1.39052
IMPORTANT – temperature thresholds:
Didactum outputs temperature as raw value x10.
25.5 °C = OID value 255. Parameter WarnTemp/CritTemp
therefore must also be entered x10 (28°C = 280, 35°C = 350).
================================================================= -->
<header>
"type" = "custom-snmp"
"package" = "com.didactum"
"probe_name" = "monitoring.sensors"
"human_name" = "Didactum Monitoring System"
"version" = "1.0"
"address_type" = "IP,AT"
"port_number" = "161"
"display_name" = "Didactum/Didactum Monitoring System"
</header>
<description>
\GB\Didactum Monitoring System\P\
Monitors all sensors of a Didactum Environmental Monitoring
System via SNMP v2c. Includes:
- Temperature sensor (raw value ÷ 10 = degrees Celsius)
- Leakage / water sensor
- Humidity sensor
- Door contact
- Smoke detector
Enterprise OID: .1.3.6.1.4.1.46501 (older devices)
or .1.3.6.1.4.1.39052 (newer devices)
Sensor ID from Didactum web interface: system tree → sensor → details
Append this ID to the end of the OID.
</description>
<parameters>
"Community" = "didactum_imap"
"WarnTemp" = "280"
"CritTemp" = "350"
"WarnHumidity" = "80"
"CritHumidity" = "90"
"OID_Temp" = "1.3.6.1.4.1.46501.5.1.1.7.101001"
"OID_TempStatus" = "1.3.6.1.4.1.46501.5.1.1.6.101001"
"OID_Leak" = "1.3.6.1.4.1.46501.5.1.1.7.107001"
"OID_Humidity" = "1.3.6.1.4.1.46501.5.1.1.7.102001"
"OID_Door" = "1.3.6.1.4.1.46501.5.1.1.7.104001"
"OID_Smoke" = "1.3.6.1.4.1.46501.5.1.1.7.106001"
</parameters>
<snmp-device-properties>
nomib2 = "true"
pdutype = "get-request"
</snmp-device-properties>
<snmp-device-variables>
-- Temperature sensor: raw value (e.g. 235 = 23.5 degrees C)
sensorTemp, $OID_Temp, DEFAULT, "Temperature (raw value)"
-- Temperature calculated (raw value divided by 10)
tempCelsius, (($sensorTemp) / 10.0), CALCULATION, "Temperature in degrees C"
-- Temperature sensor status (0=OK, 1=Alarm, 2=No signal)
sensorTempStatus, $OID_TempStatus, DEFAULT, "Temp status"
-- Leakage sensor (0=dry, 1=water detected)
sensorLeak, $OID_Leak, DEFAULT, "Leakage"
-- Humidity (direct % value)
sensorHumidity, $OID_Humidity, DEFAULT, "Humidity %"
-- Door contact (0=closed, 1=open)
sensorDoor, $OID_Door, DEFAULT, "Door contact"
-- Smoke detector (0=OK, 1=Alarm)
sensorSmoke, $OID_Smoke, DEFAULT, "Smoke detector"
</snmp-device-variables>
<snmp-device-thresholds>
-- Temperature: warning and alarm
-- Thresholds as raw value x10 (28C = 280, 35C = 350)
warning: $sensorTemp > $WarnTemp, "Temperature Warning: $tempCelsius degrees C (limit: 28.0)"
alarm: $sensorTemp > $CritTemp, "Temperature ALARM: $tempCelsius degrees C (limit: 35.0)"
-- Temperature sensor connection status
alarm: $sensorTempStatus == 2, "Temperature sensor: no signal (status=2)"
warning: $sensorTempStatus == 1, "Temperature sensor: alarm status reported (status=1)"
-- Leakage: immediate alarm at value 1
alarm: $sensorLeak >= 1, "LEAKAGE ALARM: water detected! (value=$sensorLeak)"
-- Humidity: warning and alarm
warning: $sensorHumidity > $WarnHumidity, "Humidity Warning: $sensorHumidity %"
alarm: $sensorHumidity > $CritHumidity, "Humidity ALARM: $sensorHumidity %"
-- Door contact: warning when door is open
warning: $sensorDoor >= 1, "Door contact: door open! (value=$sensorDoor)"
-- Smoke detector: immediate alarm
alarm: $sensorSmoke >= 1, "SMOKE DETECTOR ALARM: smoke detected! (value=$sensorSmoke)"
</snmp-device-thresholds>... <snmp-device-display>
\B5\Didactum Monitoring System\0P\
\4\
Temperature: \0P\$tempCelsius \3G\degrees C\0P\
Temp status: \0P\$sensorTempStatus \3G\(0=OK, 1=Alarm, 2=no signal)\0P\
\4\
Leakage sensor: \0P\$sensorLeak \3G\(0=dry, 1=water)\0P\
Humidity: \0P\$sensorHumidity \3G\%\0P\
Door contact: \0P\$sensorDoor \3G\(0=closed, 1=open)\0P\
Smoke detector: \0P\$sensorSmoke \3G\(0=OK, 1=Alarm)\0P\
</snmp-device-display>
<datasets>
$tempCelsius, "temperature", "degrees C", "true", "Temperature"
$sensorLeak, "leakage", "", "true", "Leakage"
$sensorHumidity, "humidity", "%", "true", "Humidity"
$sensorDoor, "door", "", "true", "Door contact"
$sensorSmoke, "smoke", "", "true", "Smoke detector"
</datasets>
Important OID adjustments for second sensors
If multiple sensors of the same type are connected, the OIDs in the parameters can be adjusted. Simply change the sensor ID (last part of the OID):
Sensor 01 (ID 101001): OID = .1.3.6.1.4.1.46501.5.1.1.7.101001 Sensor 02 (ID 102001): OID = .1.3.6.1.4.1.46501.5.1.1.7.102001 Create a second probe file as com.didactum.monitoring.sensor2.txt and adjust OID_Temp to the second sensor ID.
7. Import the probe file into InterMapper
Variant A – Via the menu (recommended)
InterMapper → Menu: File → Import → Probe... → Select file com.didactum.monitoring.txt → Open → InterMapper compiles and activates the probe → Success message: "Probe imported successfully"
Variant B – Copy file directly into probe directory
# Open the probe directory and create subfolder: Windows: C:\Program Files\InterMapper\InterMapper Settings\Probes\com.didactum\ Linux: /var/db/intermapper/InterMapper Settings/Probes/com.didactum/ # Store the probe file there # InterMapper automatically recognizes new probes on restart # Or: File → Reload Probes
Assign the probe to the Didactum device
Right-click device on map → "Set Probe..."
→ Select category: Didactum → "Didactum Monitoring System"
→ Enter parameters:
Community: didactum_imap
WarnTemp: 280 (= 28.0 °C)
CritTemp: 350 (= 35.0 °C)
WarnHumidity: 80
CritHumidity: 90
OID_Temp: 1.3.6.1.4.1.46501.5.1.1.7.101001
OID_TempStatus: 1.3.6.1.4.1.46501.5.1.1.6.101001
OID_Leak: 1.3.6.1.4.1.46501.5.1.1.7.107001
OID_Humidity: 1.3.6.1.4.1.46501.5.1.1.7.102001
OID_Door: 1.3.6.1.4.1.46501.5.1.1.7.104001
OID_Smoke: 1.3.6.1.4.1.46501.5.1.1.7.106001
→ Click OK
All sensor values now appear in real time in the status window (double-click the device).
8. Configure the SNMP trap probe
In addition to active polling, InterMapper can also receive SNMP traps from the Didactum device. Trap probes wait passively for incoming traps without active polling.
Step 1 – Create trap probe file
Save as com.didactum.trap.txt:
<!-- =================================================================
Didactum SNMP Trap probe for InterMapper
Filename: com.didactum.trap.txt
================================================================= -->
<header>
"type" = "custom-snmp-trap"
"package" = "com.didactum"
"probe_name" = "trap.sensor"
"human_name" = "Didactum SNMP trap receiver"
"version" = "1.0"
"address_type" = "IP,AT"
"port_number" = "162"
"display_name" = "Didactum/Didactum SNMP trap receiver"
</header>
<description>
\GB\Didactum SNMP trap receiver\P\
Receives SNMP traps from the Didactum Monitoring System.
No active polling – the device sends traps on alarm.
Trap enterprise OID: .1.3.6.1.4.1.46501 (older devices)
or .1.3.6.1.4.1.39052 (newer devices)
Enter the trap receiver IP in the Didactum web interface as this
InterMapper server IP!
</description>
<parameters>
"Community" = "didactum_imap"
</parameters>
<snmp-device-variables>
-- Trap variables are set automatically when a trap is received
trapOID, 1.3.6.1.6.3.1.1.4.1.0, DEFAULT, "Trap OID"
trapSource, 1.3.6.1.2.1.1.5.0, DEFAULT, "Trap source"
sensorValue, 1.3.6.1.4.1.46501.5.1.1.7, DEFAULT, "Sensor value"
</snmp-device-variables>
<snmp-device-thresholds>
-- Leakage trap (OID .107001 value 1)
alarm: ($trapOID == "1.3.6.1.4.1.46501.5.1.1.7.107001") AND ($sensorValue >= 1), "LEAKAGE TRAP received!"
-- Smoke detector trap
alarm: ($trapOID == "1.3.6.1.4.1.46501.5.1.1.7.106001") AND ($sensorValue >= 1), "SMOKE TRAP received!"
-- Temperature alarm trap (status OID)
alarm: ($trapOID == "1.3.6.1.4.1.46501.5.1.1.6.101001") AND ($sensorValue >= 1), "TEMPERATURE ALARM TRAP!"
-- Door contact trap
warning: ($trapOID == "1.3.6.1.4.1.46501.5.1.1.7.104001") AND ($sensorValue >= 1), "DOOR open (trap)"
</snmp-device-thresholds>
<snmp-device-display>
\B5\Didactum SNMP trap receiver\0P\
Last trap OID: \0P\$trapOID\0P\
Last sensor value:\0P\$sensorValue\0P\
</snmp-device-display>
Step 2 – Import trap probe and add device
File → Import → Probe... → import com.didactum.trap.txt... Then create a separate trap receiver device on the map: Map → Insert → Device... IP: 192.168.1.50 (Didactum IP) Probe: Didactum/Didactum SNMP trap receiver Community: didactum_imap
9. Set up email notifier
Step 1 – Create email notifier
InterMapper → Menu: Server Settings → Notifiers → click "Add Notifier..."
| Field | Value |
|---|---|
| Notifier name | Didactum Email Admin |
| Notifier type | |
| To address | admin@ihredomain.de |
| From address | intermapper@ihredomain.de |
| Subject | [InterMapper ALARM] ${device}: ${message} |
| Notify on alarm | Yes |
| Notify on warning | Yes |
| Notify on recovery | Yes |
Step 2 – Configure SMTP settings
InterMapper → Server Settings → E-mail Preferences SMTP server: mail.ihredomain.de SMTP port: 587 Use TLS: Yes Auth user: intermapper@ihredomain.de Auth password: YourPassword → Send "Test E-mail" → check inbox
Step 3 – Assign notifier to the device
Right-click device → "Edit Notifiers..." → activate "Didactum Email Admin" from the list (check Alarm, Warning, OK) → Click OK
Step 4 – Notifier for all Didactum devices (group assignment)
Right-click group "Didactum Monitoring" → "Edit Notifiers..." → activate "Didactum Email Admin" → select "Apply to all devices in group" → OK
10. SNMP OID reference
All Didactum OIDs begin with 1.3.6.1.4.1.46501 (older firmware) or 1.3.6.1.4.1.39052 (newer models). The sensor ID is appended at the end.
Important for InterMapper: Scalar values must have a ".0" suffix in their OIDs in custom probe files. Since Didactum OIDs are table entries (not scalars), no trailing .0 is required.
OID fields per sensor
| Field | Meaning | Example |
|---|---|---|
| .1.x.SENSOR_ID | Sensor ID | 1.3.6.1.4.1.46501.5.1.1.1.101001 |
| .5.x.SENSOR_ID | Sensor name | 1.3.6.1.4.1.46501.5.1.1.5.101001 |
| .6.x.SENSOR_ID | Status (0=OK, 1=Alarm, 2=No signal) | 1.3.6.1.4.1.46501.5.1.1.6.101001 |
| .7.x.SENSOR_ID | Measured value (current) | 1.3.6.1.4.1.46501.5.1.1.7.101001 |
Sensor types with OIDs and InterMapper parameters
| Sensor type | Sensor ID | OID measured value | OID status | Probe parameter / threshold |
|---|---|---|---|---|
| Temperature sensor (digital) | 101001 | 1.3.6.1.4.1.46501.5.1.1.7.101001 | 1.3.6.1.4.1.46501.5.1.1.6.101001 | WarnTemp: 280 / CritTemp: 350 (raw value × 10) |
| Temperature sensor (analog) | 201001 | 1.3.6.1.4.1.39052.5.2.1.7.201001 | 1.3.6.1.4.1.39052.5.2.1.6.201001 | Raw value × 10; divisor 10 in CALCULATION |
| Water sensor / leakage | 107001 | 1.3.6.1.4.1.46501.5.1.1.7.107001 | 1.3.6.1.4.1.46501.5.1.1.6.107001 | alarm: value >= 1 (1 = water detected) |
| Humidity | 102001 | 1.3.6.1.4.1.46501.5.1.1.7.102001 | 1.3.6.1.4.1.46501.5.1.1.6.102001 | WarnHumidity: 80 / CritHumidity: 90 (direct %) |
| Potential-free contact | 101003 | 1.3.6.1.4.1.39052.5.1.1.7.101003 | 1.3.6.1.4.1.39052.5.1.1.6.101003 | warning: value >= 1 (1 = closed) |
| Door contact | 104001 | 1.3.6.1.4.1.46501.5.1.1.7.104001 | 1.3.6.1.4.1.46501.5.1.1.6.104001 | warning: value >= 1 (1 = open) |
| Smoke detector | 106001 | 1.3.6.1.4.1.46501.5.1.1.7.106001 | 1.3.6.1.4.1.46501.5.1.1.6.106001 | alarm: value >= 1 (1 = alarm) |
Find the sensor ID:
In the Didactum web interface under System tree → select sensor → Details. This ID is appended to the end of the OID.
Temperature thresholds in InterMapper:
Didactum outputs temperature values as raw value × 10. 28.0 °C = OID value 280. In the probe, the raw value is queried and divided by 10 in the CALCULATION variable (tempCelsius = sensorTemp / 10). Threshold checking is done against the raw value (WarnTemp=280). The display in the status window shows the calculated Celsius value.
MIB prefix per model:
Older devices use 1.3.6.1.4.1.46501, newer ones may use 1.3.6.1.4.1.39052. Take the exact OIDs from your device’s MIB file.
11. Test & troubleshooting
SNMP MIB browser for direct OID test
InterMapper → Monitor → SNMP MIB Browser → IP: 192.168.1.50 → Community: didactum_imap → SNMP version: SNMPv2c → OID: 1.3.6.1.4.1.46501.5.1.1.7.101001 → Click "Get" → raw value appears (e.g. 235 = 23.5 °C) → Click "Walk" → all sensor OIDs are listed
Check probe file for syntax errors
After import, a syntax error message appears if there is a problem. Open the probe file in a text editor and check: - Are all sections (<header>, <parameters>, etc.) properly closed? - Are quotation marks correct? - OIDs without a leading dot (InterMapper prefers OIDs without a dot)
Check device status in the status window
Double-click device on map → status window opens → All sensor values are displayed → Temperature shown as calculated Celsius value (after division by 10) → Color status: Green=OK, Yellow=Warning, Red=Alarm
Error messages and solutions
| Problem | Cause & solution |
|---|---|
| Device appears red without probe error | SNMP connection failed → check community string, IP, firewall UDP 161 |
| Probe import fails | Syntax error in the probe file → read the error message; check section tags |
| "Symbolic OID could not be resolved" | MIB file not imported → File → Import → MIB → didactum.mib |
| Temperature value is 10× too high in the status | CALCULATION variable missing → check probe file: tempCelsius = ($sensorTemp) / 10.0 |
| Threshold never triggers alarm | WarnTemp/CritTemp × 10 not taken into account → set parameters to 280 / 350 |
| Probe not visible in "Set Probe..." | Probe not imported or saved incorrectly → File → Reload Probes |
| No SNMP trap received | Trap receiver IP wrong in Didactum; UDP 162 blocked; trap probe not assigned |
| No email on alarm | Check SMTP settings; notifier not assigned to the device; send test email |
View InterMapper logs
InterMapper → Server Settings → Log Files → "Event Log" – all device status changes → "Debug Log" – detailed SNMP communication (when debug mode is enabled)... File paths: Windows: C:\Program Files\InterMapper\InterMapper Settings\Logs\ Linux: /var/db/intermapper/InterMapper Settings/Logs/
12. Final checklist
Didactum device
- SNMP enabled (v2c or v3)
- Community string set (not "public"): didactum_imap
- Device reachable by ping from the InterMapper server
- Trap receiver IP set to the InterMapper server
- Trap port 162 entered
- MIB file downloaded
InterMapper configuration
- MIB file didactum.mib imported (File → Import → MIB)
- SNMP MIB Browser test successful (sensor values visible)
- Didactum device added to map (IP: 192.168.1.50)
- Custom probe com.didactum.monitoring.txt created
- Probe imported (File → Import → Probe)
- Probe assigned to device (Set Probe... → Didactum)
- Parameters entered (Community, WarnTemp=280, CritTemp=350)
- Status window shows all sensor values correctly
Thresholds & alarms
- Temperature thresholds entered × 10 (28°C = 280)
- Celsius display correct (CALCULATION / 10 gives e.g. 23.5 °C)
- Leakage alarm configured (alarm at value >= 1)
- Smoke detector alarm configured
- Door contact warning configured
- Trap probe imported and device assigned
Notifier & notification
- SMTP settings configured (Server Settings → E-mail)
- Test email received successfully
- Notifier "Didactum Email Admin" created
- Notifier assigned to the device or group
- Alarm triggered and email received