Language selection:
Skip to main navigation Skip to main content Skip to page footer

Didactum Monitoring & NeuralStar Integration

Complete step-by-step guide for integrating Didactum Monitoring devices and sensors into NeuralStar NMS via SNMP – including device discovery, MIB import, threshold configuration, complete OID reference for all sensor types (Temperature, Leakage, Humidity, Door Contact, Smoke) as well as alarm and notification configuration.

Architecture Note: NeuralStar communicates directly with the Didactum device via SNMP. The NeuralStar server sends SNMP GET/WALK requests to UDP port 161 of the Didactum device. SNMP Traps are actively sent from the Didactum device to the NeuralStar server (UDP port 162).

  • Software: NeuralStar NMS (current version)
  • Protocol: SNMP v1 / v2c / v3
  • Devices: Didactum Monitoring System 100T / 300T / 500T / 550T
  • Sensors: Temperature, Leakage, Humidity, Door Contact, Smoke

1. Prerequisites & System Overview

NeuralStar Server

RequirementDetails
Operating SystemWindows Server 2016/2019/2022 or Linux (Ubuntu 20.04 / 22.04)
NeuralStar VersionCurrent release recommended (integrated MIB Browser)
NetworkUDP Port 161 outbound (SNMP Polling), UDP Port 162 inbound (SNMP Traps)
Network AccessIP reachability to the Didactum device required

Didactum Device

RequirementDetails
ModelMonitoring System 100T, 300T, 500T or 550T
SNMPSNMP enabled (v2c recommended)
ReachabilityDevice reachable via network from the NeuralStar server
MIB FileAvailable in the Web Interface under System Settings → SNMP

Enterprise OIDs by Firmware Generation

Device / FirmwareEnterprise OID (Base)
Older models / older firmware.1.3.6.1.4.1.46501
Newer models / current firmware.1.3.6.1.4.1.39052

Note: To determine which Enterprise OID your device uses, check the MIB file from the Web Interface or determine it with:
snmpwalk -v 2c -c public 192.168.1.50 .1.3.6.1.2.1.1.2.0

2. Enable SNMP on the Didactum Device

Step 1 – Open Web Interface

Open the IP address of the Didactum device in the browser:

192.168.1.50 (adjust Didactum device IP)

Step 2 – Access SNMP Settings

System Settings → SNMP

Step 3 – Enter the following values

Field in Didactum Web InterfaceRecommended Value
Enable SNMPEnabled
SNMP Versionv2c (recommended)
Community String (Read)didactum_neuralstar (do not use „public"!)
SNMP Port161
Trap DestinationIP address of the NeuralStar server
Trap Communitydidactum_trap
Trap Port162

Step 4 – Download MIB File

System Settings → SNMP → "Download MIB File"
File will be downloaded as didactum.mib.
This file will be imported into NeuralStar in step 3.

Save settings and restart the device if necessary.

3. Import MIB File into NeuralStar

Step 1 – Open MIB Manager

NeuralStar → Administration → MIB Manager
Alternatively: Tools → MIB Browser → Import MIB

Step 2 – Import MIB File

→ Click "Import MIB" / "Upload MIB"
→ Select downloaded file didactum.mib
→ Confirm import

Step 3 – Check Import Result

After successful import, DIDACTUM-MIB (or DIDACTUM-MIB2 for newer devices) appears in the MIB tree view under iso → org → dod → internet → private → enterprises. The OID .1.3.6.1.4.1.46501 or .1.3.6.1.4.1.39052 should now be resolved with symbolic names.

Note: If NeuralStar requests dependent MIBs during import (e.g. RFC1213-MIB, SNMPv2-SMI), these can be obtained via the integrated MIB Manager or from circitor.fr and imported first.

Ready MIB Import Configuration (DIDACTUM-MIB.txt)

If no MIB file is available from the device, the following minimal MIB structure can be saved manually as text file DIDACTUM-MIB.txt and imported:

-- ================================================================
-- DIDACTUM-MIB – Minimal MIB for NeuralStar Import
-- File: DIDACTUM-MIB.txt
-- For older devices: enterprises.46501
-- For newer devices: enterprises.39052 (adjust OID)
-- ================================================================
DIDACTUM-MIB DEFINITIONS ::= BEGIN
IMPORTS
    MODULE-IDENTITY, OBJECT-TYPE, Integer32, enterprises
        FROM SNMPv2-SMI
    NOTIFICATION-TYPE
        FROM SNMPv2-SMI;
didactum MODULE-IDENTITY
    LAST-UPDATED "202401010000Z"
    ORGANIZATION "Didactum Security GmbH"
    CONTACT-INFO "support@didactum-security.com"
    DESCRIPTION "Didactum Monitoring System MIB"
    ::= { enterprises 46501 }
-- Sensor Table (sensorTable)
sensorTable OBJECT-TYPE
    SYNTAX SEQUENCE OF SensorEntry
    MAX-ACCESS not-accessible
    STATUS current
    DESCRIPTION "Table of all connected sensors"
    ::= { didactum 5 1 1 }
sensorEntry OBJECT-TYPE
    SYNTAX SensorEntry
    MAX-ACCESS not-accessible
    STATUS current
    DESCRIPTION "Single sensor entry"
    INDEX { sensorIndex }
    ::= { sensorTable 1 }
SensorEntry ::= SEQUENCE {
    sensorIndex Integer32,
    sensorID Integer32,
    sensorType Integer32,
    sensorName OCTET STRING,
    sensorStatus Integer32,
    sensorValue Integer32
}
sensorIndex OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-only STATUS current
    DESCRIPTION "Index" ::= { sensorEntry 1 }
sensorID OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-only STATUS current
    DESCRIPTION "Sensor ID" ::= { sensorEntry 2 }
sensorType OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-only STATUS current
    DESCRIPTION "Sensor Type" ::= { sensorEntry 3 }
sensorName OBJECT-TYPE SYNTAX OCTET STRING MAX-ACCESS read-only STATUS current
    DESCRIPTION "Sensor Name" ::= { sensorEntry 5 }
sensorStatus OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-only STATUS current
    DESCRIPTION "0=OK 1=Alarm 2=No Signal" ::= { sensorEntry 6 }
sensorValue OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-only STATUS current
    DESCRIPTION "Measured value (Temperature: x10)" ::= { sensorEntry 7 }
-- SNMP Traps
didactumAlarmTrap NOTIFICATION-TYPE
    OBJECTS { sensorName, sensorStatus, sensorValue }
    STATUS current
    DESCRIPTION "Alarm Trap on sensor status change"
    ::= { didactum 1 1 }
END

4. Add Didactum Device in NeuralStar

Variant A – Automatic Discovery

Step 1 – Start Discovery

NeuralStar → Discovery → New Discovery Job
  IP Range: 192.168.1.50 – 192.168.1.50
  SNMP Version: SNMPv2c
  Community String: didactum_neuralstar
  Port: 161
  Timeout: 5 seconds
  Retries: 3

Step 2 – Check Discovery Result

After successful discovery, the device appears in the device list with the name Didactum Monitoring System (sysDescr from the MIB). If no name is resolved, set the sysName manually.

Variant B – Manual Addition

NeuralStar → Devices → Add Device
  Device Name: Didactum-Monitor-01
  IP Address: 192.168.1.50
  Device Type: Generic SNMP Device (or "Environmental Monitor")
  SNMP Version: v2c
  Community: didactum_neuralstar
  Port: 161
  Description: Didactum Monitoring System 300T – Server Room

Step 3 – Assign Device to a Group (optional)

NeuralStar → Devices → Didactum-Monitor-01 → Groups
→ Select "Environmental" or custom group "Serverroom Monitoring"

5. Configure SNMP Monitoring for Didactum Sensors

Important – Temperature Thresholds: The Didactum device delivers temperature values as raw value × 10. 25.5 °C = OID value 255. Thresholds in NeuralStar must therefore also be specified × 10!

Create Monitoring Objects (SNMP Data Points)

NeuralStar → Devices → Didactum-Monitor-01 → Monitoring → Add Monitor

Monitor 1 – Temperature Sensor (digital, Sensor ID 101001)

 Monitor Name: Temperature Sensor 01
  Monitor Type: SNMP Get
  OID: .1.3.6.1.4.1.46501.5.1.1.7.101001
  SNMP Version: v2c
  Community: didactum_neuralstar
  Interval: 60 seconds
  Data Type: Integer
  Unit: (x0.1 °C)
  Warning High: 280 (= 28.0 °C)
  Critical High: 350 (= 35.0 °C)
  Description: Raw value divided by 10 results in degrees Celsius

Monitor 2 – Temperature Status (0=OK / 1=Alarm / 2=No Signal)

 Monitor Name: Temp Sensor Status
  OID: .1.3.6.1.4.1.46501.5.1.1.6.101001
  Data Type: Integer
  Warning High: 1
  Critical High: 2

Monitor 3 – Water Sensor / Leakage (Sensor ID 107001)

 Monitor Name: Leakage Sensor 01
  OID: .1.3.6.1.4.1.46501.5.1.1.7.107001
  Data Type: Integer
  Critical High: 1 (0 = dry / OK, 1 = water detected / CRITICAL)

Monitor 4 – Humidity (Sensor ID 102001)

 Monitor Name: Humidity Sensor 01
  OID: .1.3.6.1.4.1.46501.5.1.1.7.102001
  Data Type: Integer
  Unit: %
  Warning High: 80
  Critical High: 90

Monitor 5 – Door Contact (Sensor ID 104001)

 Monitor Name: Door Contact 01
  OID: .1.3.6.1.4.1.46501.5.1.1.7.104001
  Data Type: Integer
  Warning High: 1 (0 = closed / OK, 1 = open / Warning)

Monitor 6 – Smoke Detector (Sensor ID 106001)

 Monitor Name: Smoke Detector 01
  OID: .1.3.6.1.4.1.46501.5.1.1.7.106001
  Data Type: Integer
  Critical High: 1 (0 = no smoke / OK, 1 = Alarm / CRITICAL)

6. Configure SNMP Trap Reception

The Didactum device can actively send SNMP Traps to NeuralStar on alarm events. This way NeuralStar is immediately informed of an alarm – without polling interval.

Step 1 – Enable Trap Receiver in NeuralStar

NeuralStar → Administration → SNMP Trap Receiver
  Trap Port: 162
  Trap Community: didactum_trap
  MIB for Trap Decode: DIDACTUM-MIB (previously imported)
  → Enable "Enable Trap Receiver"
  → Save

Step 2 – Assign Trap Source to the Device

NeuralStar → Devices → Didactum-Monitor-01 → SNMP Traps
  → Enable "Accept Traps from this Device"
  → Trap Community: didactum_trap
  → Save

Step 3 – Configure Trap Forwarding in Didactum Web Interface

Didactum Web Interface → System Settings → SNMP → Trap Destinations
  Trap Destination 1: 192.168.1.100 (IP of NeuralStar server)
  Trap Community: didactum_trap
  Trap Version: v2c
  Trap Port: 162
  → Save

Recommendation: Enable both SNMP Polling (regular queries) and SNMP Traps (immediate alarms) simultaneously. Polling is used for trend monitoring and graph creation, Traps for immediate alerting.

7. Configure Alarms and Notifications

Create Alert Policy

NeuralStar → Alerts → Alert Policies → New Policy
  Policy Name: Didactum Sensor Alarms
  Applies to: Device Group "Environmental" or individual device
  Trigger: Monitor threshold exceeded OR SNMP Trap received
  -- Email Notification --
  Action: Send Email
  Recipients: admin@yourdomain.com
  Subject: [NeuralStar] Didactum Alarm: ${device.name} – ${monitor.name}
  Body:
    Timestamp: ${alert.timestamp}
    Device: ${device.name} (${device.ip})
    Monitor: ${monitor.name}
    Status: ${alert.severity}
    Value: ${monitor.value} ${monitor.unit}
    Threshold: ${monitor.threshold}
    Description: ${monitor.description}

Configure Escalation Levels

NeuralStar → Alerts → Alert Policies → Didactum Sensor Alarms → Escalation
  Level 1 (Warning): Email to admin@yourdomain.com after 0 minutes
  Level 2 (Critical): Email to it-management@yourdomain.com after 5 minutes
  Level 3 (Critical): SMS / Call (if configured) after 15 minutes

8. Set Up Dashboard and Graphs in NeuralStar

Step 1 – Create New Dashboard

NeuralStar → Dashboards → New Dashboard
  Dashboard Name: Server Room Monitoring
  Layout: Grid (2 × 3 widgets recommended)

Step 2 – Add Widgets for Didactum Sensors

Widget 1: Temperature Trend (Line Chart)
  Widget Type: Line Chart / Time Series
  Device: Didactum-Monitor-01
  Monitor: Temperature Sensor 01
  Time Range: Last 24 hours
  Y-Axis Label: Raw value (÷10 = °C)
  Threshold Line: Warning 280 / Critical 350
Widget 2: Leakage Status (Status Indicator)
  Widget Type: Status Indicator / LED
  Monitor: Leakage Sensor 01
  OK Color: Green (value = 0)
  Critical Color: Red (value ≥ 1)
Widget 3: Humidity (Gauge)
  Widget Type: Gauge
  Monitor: Humidity Sensor 01
  Min: 0 / Max: 100
  Warning Zone: 80–90 %
  Critical Zone: >90 %
Widget 4: Door Contact Status
  Widget Type: Status Indicator
  Monitor: Door Contact 01
Widget 5: Smoke Detector Status
  Widget Type: Status Indicator
  Monitor: Smoke Detector 01
Widget 6: Overall Status Table
  Widget Type: Device Status Table
  Device: Didactum-Monitor-01
  Shows: All configured monitors with current status

9. SNMP OID Reference for Didactum Sensors

All Didactum OIDs start 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.

OID fields per sensor

FieldOID SuffixMeaningExample (Sensor 101001)
Sensor Index.5.1.1.1.SENSOR_IDInternal index.1.3.6.1.4.1.46501.5.1.1.1.101001
Sensor ID.5.1.1.2.SENSOR_IDNumeric sensor ID.1.3.6.1.4.1.46501.5.1.1.2.101001
Sensor Type.5.1.1.3.SENSOR_IDType identifier.1.3.6.1.4.1.46501.5.1.1.3.101001
Sensor Name.5.1.1.5.SENSOR_IDDesignation (String).1.3.6.1.4.1.46501.5.1.1.5.101001
Sensor Status.5.1.1.6.SENSOR_ID0=OK, 1=Alarm, 2=No Signal.1.3.6.1.4.1.46501.5.1.1.6.101001
Sensor Measured Value.5.1.1.7.SENSOR_IDCurrent measured value.1.3.6.1.4.1.46501.5.1.1.7.101001

Sensor types with complete OIDs and NeuralStar thresholds

Sensor TypeSensor IDOID Measured ValueOID StatusNeuralStar 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.101001Warning 280 / Critical 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.201001Warning 280 / Critical 350 (× 10)
Water Sensor / Leakage107001.1.3.6.1.4.1.46501.5.1.1.7.107001.1.3.6.1.4.1.46501.5.1.1.6.107001Critical ≥ 1 (0 = dry)
Humidity102001.1.3.6.1.4.1.46501.5.1.1.7.102001.1.3.6.1.4.1.46501.5.1.1.6.102001Warning 80 / Critical 90 (direct %)
Dry Contact101003.1.3.6.1.4.1.39052.5.1.1.7.101003.1.3.6.1.4.1.39052.5.1.1.6.101003Warning ≥ 1 (0 = open / inactive)
Door Contact104001.1.3.6.1.4.1.46501.5.1.1.7.104001.1.3.6.1.4.1.46501.5.1.1.6.104001Warning ≥ 1 (0 = closed)
Smoke Detector106001.1.3.6.1.4.1.46501.5.1.1.7.106001.1.3.6.1.4.1.46501.5.1.1.6.106001Critical ≥ 1 (0 = no smoke)

Determine Sensor ID: In the Didactum Web Interface under System Tree → Select Sensor → Details. The displayed sensor ID is appended as the last element to the OID. For multiple sensors of the same type, the last digit increases (101001, 101002, 101003 …).

Temperature Thresholds in NeuralStar: The Didactum device delivers temperature values as raw value × 10. 28.0 °C = OID value 280. NeuralStar thresholds (Warning/Critical) must therefore also be specified × 10.

10. Test SNMP Connection

Test via Command Line (Linux / Windows with Net-SNMP)

# snmpwalk – list all sensor values
snmpwalk -v 2c -c didactum_neuralstar 192.168.1.50 \
    .1.3.6.1.4.1.46501.5.1.1
# snmpget – query single temperature value (raw value ÷ 10 = °C)
snmpget -v 2c -c didactum_neuralstar 192.168.1.50 \
    .1.3.6.1.4.1.46501.5.1.1.7.101001
# Expected output: INTEGER: 235 (= 23.5 °C)
# snmpget – query leakage status
snmpget -v 2c -c didactum_neuralstar 192.168.1.50 \
    .1.3.6.1.4.1.46501.5.1.1.7.107001
# Expected output (dry): INTEGER: 0
# snmpget – query sensor status
snmpget -v 2c -c didactum_neuralstar 192.168.1.50 \
    .1.3.6.1.4.1.46501.5.1.1.6.101001
# Expected output (OK): INTEGER: 0
# Test with MIB names (after MIB import)
snmpwalk -v 2c -c didactum_neuralstar -m ALL 192.168.1.50 \
    DIDACTUM-MIB::sensorValue

Test via NeuralStar MIB Browser

NeuralStar → Tools → MIB Browser
  Host: 192.168.1.50
  Community: didactum_neuralstar
  Version: v2c
  OID: .1.3.6.1.4.1.46501.5.1.1.7.101001
  → Click "Get" → Value should appear (e.g. 235)

11. Troubleshooting

ProblemCause & Solution
NeuralStar does not find device during discoverySNMP not enabled on Didactum device; Community String wrong; UDP port 161 blocked by firewall → check firewall rule and verify SNMP settings in Web Interface
MIB import failsDependent MIBs missing (RFC1213-MIB, SNMPv2-SMI) → import base MIBs first or use the DIDACTUM-MIB.txt from section 3
OID returns „No Such Object"Wrong Enterprise OID (46501 vs. 39052) → check with snmpwalk -v 2c -c COMMUNITY IP .1.3.6.1.2.1.1.2.0 sysObjectID
Temperature value appears 10× too highNot an error – Didactum delivers raw value × 10. Set thresholds accordingly × 10 (28 °C = threshold 280)
SNMP Traps do not arriveTrap destination IP not configured in Didactum Web Interface; UDP port 162 blocked by firewall; Trap Community does not match
Sensor value always remains 0 (Leakage / Door Contact)Normal in non-critical state (0 = OK). Test sensor by briefly triggering it; verify OID with snmpget
No email on alarmCheck SMTP settings in NeuralStar; Alert Policy assigned to device?; check spam folder
Graph shows no dataWait for monitor interval (first data point after first polling cycle); test SNMP connection via MIB Browser

12. Final Checklist

Didactum Device

  • SNMP enabled (v2c)
  • Community String set (not „public"): didactum_neuralstar
  • Trap destination set to IP of NeuralStar server
  • Trap Community set: didactum_trap
  • MIB file downloaded (didactum.mib)
  • snmpwalk from NeuralStar server successful

NeuralStar Server

  • DIDACTUM-MIB successfully imported
  • Didactum device found via discovery or added manually
  • SNMP Community configured in device profile
  • All monitoring objects (OIDs) for temperature, leakage, humidity, door contact, smoke created
  • Temperature thresholds set as raw value × 10 (Warning 280 / Critical 350)
  • Leakage and smoke detector critical threshold set to 1
  • SNMP Trap Receiver enabled (Port 162)
  • Alert Policy "Didactum Sensor Alarms" created and assigned to device
  • Email notification configured and test email received

Dashboard & Tests

  • Dashboard "Server Room Monitoring" created with sensor widgets
  • Temperature graph shows measured values (after first polling interval)
  • SNMP Trap test: manually trigger sensor → alarm appears in NeuralStar
  • Email received on test alarm
  • All sensor statuses green in dashboard (normal operation)

This website uses cookies

This website uses cookies to improve user experience. By using our website you consent to all cookies in accordance with our Cookie Policy.

Essential cookies enable basic functions and are necessary for the website to function properly.
Statistics cookies collect information anonymously. This information helps us to understand how our visitors use our website.
Marketing cookies are used by third parties or publishers to display personalized advertisements. They do this by tracking visitors across websites.