For initial setup, see the Setup Guide.
1. Monitoring Connection Health
The enaimco platform continuously monitors the DVR connection:
Health check: The platform polls the DVR's status endpoint every 1 second (with a 2-second timeout) to confirm the device is reachable
Status polling: When actively connected and running, the platform fetches full recording/clip status from the DVR every 15 seconds
Connection indicator: The DVR Settings panel displays a live indicator showing the current connectivity state (green = healthy, red = disconnected)
On failure: If the health check fails, the indicator turns red, status polling stops, and an error notification appears in the platform
2. Common Failure Modes & Diagnosis
"Test Connection" fails
Likely causes:
DVR unreachable on network
Verify the DVR is powered on and connected to the same network as the surface device
Confirm the IP address entered in enaimco matches the DVR's actual IP (run
ipconfigon the DVR to check)Verify port 8080 is open and not blocked by a firewall on either device
Browser blocking insecure content
The DVR uses HTTP while enaimco is served over HTTPS — the browser blocks mixed content by default
Configure the browser to allow insecure content for the enaimco site
In Chrome: click the lock/site info icon in the address bar > Site Settings > Insecure content > Allow, then reload the page
Another client already connected
The DVR only supports one HTTP connection at a time
Close any other browser tabs, applications, or devices that may be connected to the DVR
Connection drops intermittently
Likely causes:
Network instability on vessel
Check network cables, switches, or Wi-Fi stability between the surface device and the DVR
Verify the DVR is still powered on
The platform will auto-reconnect on the next successful health check — no manual action needed if the network recovers
Another client connected to the DVR
The DVR only supports one connection at a time — close any other clients connected to the DVR
Recording starts but file path shows as "pending"
Likely cause: The DigitalEdge device is still creating the recording file.
Wait approximately 5 seconds for the file path to resolve
If it remains pending, check the DVR's storage — the
E:drive may be full
"Failed to start recording" error
Likely cause: The DigitalEdge device returned an error.
Check the DVR device logs for details
Common causes: storage full, device already recording on another session
Overlay not updating
Likely cause: The overlay update request failed silently.
This is non-blocking — recordings and clips will continue to work
Check the browser developer console for warning messages
If persistent, disconnect and reconnect the DVR session
Recording "roll over"
This is normal behavior, not a failure.
Recordings have a 15-minute duration limit
When the limit is reached, the DVR automatically starts a new recording file
The platform detects this and logs the new file path
No action is required
Snapshot fails
Likely cause: The DVR's snapshot recorder is not ready.
Wait a moment and retry — the device may be mid-capture from a previous snapshot request
If persistent, check the DVR device logs for errors
3. Restarting / Re-establishing the Integration
Soft disconnect
Stops any active recordings and clips, clears the current asset group state, but keeps the connection configured (IP address and DVR type are preserved).
Use this when switching between inspections or asset groups.
Full disconnect
Stops all active recordings and clips, clears all connection state, and removes the saved configuration. You will need to re-enter the DVR IP address to reconnect.
Use this when the DVR session is complete or you need to connect to a different DVR.
Reconnecting after a disconnect
After soft disconnect: Click "Connect" to resume — no need to re-enter the IP
After full disconnect: Re-enter the DVR's IP address, click "Test Connection", then "Connect"
After a browser refresh
The connection configuration persists across browser refreshes. The platform will automatically resume status polling if a prior connection existed. No manual action is needed.
After a DVR device restart
If the DigitalEdge hardware is restarted:
The platform's health check will detect the DVR is unreachable and show a red indicator
Once the DVR finishes restarting and is back on the network, the health check will automatically detect it
The connection will resume without manual intervention
Any recordings that were in progress before the restart will have been interrupted — start a new recording when ready
4. Contact / Escalation Path
Level | Contact | Handles |
Level 1 — On-vessel | Trident IT contact (to be identified) | Network and hardware issues on the vessel |
Level 2 — Enaimco CS | Customer Success team | Platform configuration, integration behavior, user questions |
Level 3 — Enaimco Engineering | Engineering team | DVR integration bugs, API compatibility issues |
DigitalEdge vendor | DigitalEdge support | Device-specific firmware, configuration, and hardware issues |
When escalating, include:
Description of the issue and when it started
DVR IP address and connection state
Any error messages shown in the platform
Browser console logs (if available)
Whether the issue is reproducible