Professional Documents
Culture Documents
DESLTD-REF-5007 - Edge5DVR Std-PRO - Software Version 5.6.0 Manual Rev 3
DESLTD-REF-5007 - Edge5DVR Std-PRO - Software Version 5.6.0 Manual Rev 3
0
Digital Edge Subsea Limited Quality Management System
TABLE OF CONTENTS
1.0 Introduction 8
1.1. Abbreviations 9
1.0 Introduction
• AS OF VERSION 5.3.0, EXTERNAL STORAGE MAY NOT BE USED TO RECORD DATA AS MAIN
RECORDING LOCATIONS. See Section 3.2 for details.
• DO NOT CREATE A NEW USER ACCOUNT IN WINDOWS AS THIS WILL DISABLE SOME OF THE
FEATURES OF THE SOFTWARE. ALWAYS LOG IN TO WINDOWS AS AN ADMINISTRATOR.
• PASSWORD – DigitalEdgeDVR
• Please read Section 9 – Time Synchronisation, prior to trying to automatically sync the PC clock.
• Please read Sections 2.8.5, 2.9.5 and Section 14 prior to configuring Cable audio if a USB / Bluetooth /
IP microphone is used.
1.1. Abbreviations
Abbreviation Description
COM Communication
GB Gigabyte
HD High Definition
SD Standard Definition
TB Terabyte
The latest version of the Edge DVR comes with 3 software and 4 hardware options which are designed to suit the various
work scopes within the ROV and Diving industries.
This manual will deal with the setting up and operation of the Edge / Pro software.
For the Edge Lite manual please refer to DES Document DESLTD-REF-5003.
2.1. Edge LITE
Edge LITE is our Entry Level DVR designed for ROV and Diving projects that have no requirement for eventing. Dive logs
are therefore not editable and restricted to Events created by software controls. i.e. Start Clip.
• 4 Channel Recording
• Sonar / Navigation / Specialist equipment etc. recording via HDMI input (4U Rack mounted only)
• Network Viewer
• Client Viewer
Edge DVR is our Standard Level DVR designed for ROV and diving projects that require a job work scope importing with
real time and Offline eventing.
• Offline Eventing
EdgePro is our Advanced Level DVR designed for ROV and Diving projects that require a task based work scope with real
time and Offline eventing: The main features in addition to those in Section 2.2 are:
• Allows the User to add Inspection and Custom Tasks, along with notes and Tags to the Work pack
2.4. SD Hardware
• 1 x Ethernet port
There are 2 power switches on the DVR, one at the rear and one inside the front right door.
Connect the power lead to the rear mounted socket and turn switch to ‘I’.
Press the front power switch for 1 second, the DVR will now power up.
2.8.2 Monitor Connection
The Edge DVR has 2 x graphics cards installed. Each one has 4 Display Port outputs.
It is recommended that one card to be used for the desktop DVR monitor and the other to be used for the Live Video
Outputs (With Overlay).
• These outputs are used to display any live video channels, with overlay. This can be
configured in the Video Setup Page.
• It is best to have all monitors connected when the DVR is powered up, as Windows
needs to be able to identify these, before the Edge DVR program is started.
• It is also possible to give the pilot a dedicated output, this again can be configured
in the Video Setup Page. This can be setup to display a different overlay to that on
the recorded video.
SD Video Inputs
The Edge DVR uses a video breakout cable for the SD video inputs. The unit supports up to 6 inputs, although only 4 can
be recorded simultaneously. The yellow BNC type inputs are individually numbered. The system will auto-detect PAL/NTSC
in the Video Setup Page.
The EdgeDVR supports up to 4 HD-SDI Inputs, these are BNC inputs, directly on the card. The system will auto-detect
the format of the HD-SDI signal, in the Video Setup Page.
HDMI Input
Systems with an Intensity Pro 4k Card have two additional HDMI ports as shown above. The top HDMI port is an output;
the lower HDMI port is one an Input. The system will auto-detect the HDMI format.
Four separate serial ports are available via the above breakout cable. In early 2 DB9 male connectors may be present
with 2 further ports available internally.
Microphone Input
The microphone is connected to the Edge DVR motherboard, via the standard 3.5mm pink socket. A balanced
microphone cable and microphone is supplied. Do not use any other type of cable/extension.
To connect to diver’s comms etc, use the standard blue 3.5mm input socket on the motherboard. If both microphone
and diver comms are to be used simultaneously, an audio mixer may be required. This should take the diver comms and
microphone as inputs, and output to the DVR.
Network 2 Network 1
Press the white button below the Alienware label to switch on.
Connect the Thunderbolt power supply to the rear of the Thunderbolt enclosure. Connect the Thunderbolt cable to one
of the USB type C ports. Attach your HD Cameras to the x4 HD-SDI Inputs at Slot 1 (HD unit only). Connect the Magewell
SD Video Input Breakout cable to the port at Slot 2. Connect the Serial Input Breakout cable to the port at Slot 3.
Thunderbolt interface
Thunderbolt Power
SD Video Inputs
The EdgeDVR has up to 4 HD-SDI Inputs, these are BNC inputs, directly on the card. Again, the system will auto-sense
the format of the HD-SDI signal, in the video setup menu.
Shown above is the correct sequence for the HD inputs, Input 1 is HD-SDI 1:1, Input 2 is HD-SDI 1:2 and so on.
Serial Ports are split into 4 separate numbered ports via the above breakout cable.
Microphone Input
The microphone is connected to the left side of the DVR, via the standard 3.5mm socket. An unbalanced microphone
cable and microphone is supplied. Do not use any other type of cable / extension.
The DVR has an Ethernet port for internet and local network connection at the rear.
The EdgeDVR has twin 256Gb SSD operating system drives installed.
If Windows becomes unusable the user may switch to the reserve operating system drive.
The unit must be powered down and disconnected from the mains power before opening the DVR. Please contact Digital
Edge Subsea regarding this operation so as not to invalidate the warranty.
Note that any changes, including DVR configuration, will not automatically be applied to the reserve drive. A copy of the
DVR configuration is stored in the black box folder. Contact Digital Edge Support for further advice on migrating from the
live to reserve system drive.
For data storage there are 3x 4TB removable hard drives located inside the front right-hand side door.
Operations (E) - This drive stores the Project Primary data folder and the Operations Deliverable folder created by each
dive.
Inspections (F) – This drive stores the Inspection deliverable data folder and a Project Backup folder which duplicates the
Project Primary data held on the E Drive. The Inspection folder allows a Work scope specific data ordering structure via
the Workpack in Edge and Edge Pro versions. Work scope ordering is not available in EdgeLite.
Blackbox (G) – This drive Pre-allocates space and reserves it for data storage, it records all active channels continuously
while EdgeDVR is running. Data is recorded in an internal binary format and can be recovered with the Offline Editor
Page.
Client deliverable data is stored on an external USB SSD drive (capacity 2TB) connected to an available USB Type A port
on the right of the DVR. This drive contains 2 storage areas – Operations and Inspections. The DVR’s internal hard drive
is reserved for the Blackbox storage area and the Windows 10 operating system. This drive cannot be removed.
Operations (E) - Stores the Project Primary data folder and the Operations Deliverable folder created by each dive.
Inspections (F) – Stores the Inspection deliverable data folder and a Project Backup folder which duplicates the Project
Primary data held on the E Drive. The Inspection folder allows a Work scope specific Data ordering structure via the
Workpack in Edge and Edge Pro versions but is not used in EdgeLite.
Blackbox (G) – The Edge5 software pre-allocates this space and reserves it for data storage, it records all active channels
continuously while a project is open in a Raw data format. This data can be recovered and changed from Raw to. Mp4
using our offline editor.
• When operating the Edge5 software you must have both Dell power supplies attached to the DVR to operate
correctly, the security dongle attached, and the external USB hard drive connected.
• Never remove the Thunderbolt cable in operation. Always power off the DVR first before removing the
Thunderbolt cable, if not you may see a blue screen, or the Thunderbolt devices will not be detected correctly.
• If the DVR needs to be restarted, it is recommended to Shutdown Windows instead, then remove the
Thunderbolt cable and restart the DVR. When Windows has finished booting then attach the Thunderbolt
cable. If this is not performed the Thunderbolt devices may not be detected correctly.
• If the Serial COM ports and SD or HD Video capture cards are not detected, first power down the DVR and
remove the Thunderbolt cable. Restart the DVR and wait for Windows 10 to boot to desktop. Reconnect the
Thunderbolt cable, two sound chimes will be heard, and the devices will be reloaded. Open Edge5 to confirm
operation.
The Edge DVR Welcome Screen allows the user to select / create a project and setup the Edge DVR prior to commencing
any work.
3.1. Create a New Project
To create a new project, click on the Edge Lite, Edge, or Edge Pro icon on the Welcome Screen.
Enter the New Project Name. Each project on a single DVR must have a unique name. A project name must be useable
as a folder name i.e. some special characters (e.g. *? <), and some names (e.g. NUL, COM etc.) are not allowed.
The user will then be prompted to select a project Time Zone. This cannot be changed once the project has been created.
Internally all data is logged using UTC; the project time zone determines how dates and times are shown on screen, on
video overlays, and in reports. Black box file names are always generated using UTC.
If a time zone includes daylight saving adjustments, these will be applied automatically. Be aware that if recording when
daylight saving time is entered, video file names may appear to jump backwards or forwards (typically by an hour). The
order of log entries remains the same as the order in which they were generated.
When the user creates a new project, the Setup Wizard will guide the user through the setup process in a logical manner
prior to starting recording / operations. These settings can also be changed later, after the wizard completes.
System settings (e.g. recording folders) are note include in the new project wizard. These can be changed from the
Welcome Page. See Section 2.2 below for details.
3.2. System Settings
The System Settings Page allows the user to set the location of various recording folders. Blackbox file duration and total
Blackbox folder size are also set here. These must be configured prior to any recording/operations.
The factory default storage locations are chosen to ensure consistent DVR performance. Any deviation from this may
result in degraded performance and irrecoverable data loss. Selecting a Network Attached Storage (NAS) device for any
of the system folders will result in a configuration error. If the default storage locations do not meet your requirements,
please contact Digital Edge Subsea support to discuss alternatives.
The following shows the default file paths for all folders. These can be changed as required by clicking on the ‘…’ button,
however we strongly recommend these are not changed.
When EdgeDVR is opened, the Blackbox records automatically in the background. The duration of the Blackbox video
can be changed by clicking the dropdown box.
The Blackbox folder size can also be changed if required. When the Blackbox folder is full the system will automatically
delete the oldest files.
We specify a 4TB drive for the 4U, but not for the laptop internal drive. For a 4TB hard drive it is recommended the
Blackbox “limit total size to” does not exceed 2000Gb. A lower value means old Blackbox data will overwritten sooner. The
recommended folder for Blackbox Data is “G:\edge5_blackbox”
3.2.3 Project Data
The ‘Project (Primary)’ folder contains settings files and raw data for each project, this folder contains the Pre-Deliverable
data, and is required for editing of the project via the Offline Editor Page, or the standalone Edge Editor Application. The
recommended folder ‘Project (Primary)’ is “E:\edge5_project”
The ‘Project (Backup)’ folder is a mirror of the ‘Project (Primary)’ folder. The recommended Project (Backup)’ folder is
“F:\edge5_project_backup “
The Operations Deliverable folder contains video, clips, photos, and reports organised by dive. The default file path for
the Operations Deliverable is “E:\edge5_operations “
When a project is created, a matching folder will be created in the Operations Deliverable folder. When a dive is started,
a sub-folder will be created. Inside the dive folder, further sub folders store the video, clips photos and reports.
The Inspections Data folder contains video, clips, photos, and reports organised according to work pack levels. The work
pack is only available in EdgeDVR and EdgePro. The default file path is to “F:\edge5_inspection”
3.3. Mirror relevant data to an external NAS using 3rd party software.
Data Management -The easiest way to free up space from the DVR will be to use Edge Archive, However if a 3rd party
app is used (i.e. with Microsoft SyncToy), manual data management is the best way. This is to prevent a scheduled
backup preventing Edge DVR from writing to a Live recording file.
• Only run SyncToy manually i.e. not on a schedule or in response to file changes.
• Ensure SyncToy is configured to never delete files (either in the source or destination). Avoid modes like
‘mirror’ or ‘full sync’ where deletions in one folder are mirrored in the other.
• Manage data deletion from the DVR PC “by dive”: once you’re happy you’re finished with a dive i.e. no
more new clips, snapshots, or events are required:
Check all “Primary Project Folder” data for the dive has been backed up. This will include *.edge_raw
and *.edge_index files that start with “Dive##”.
Check all Operations deliverables associated with the dive have been backed up. These will be in a
“…/Dive ##/” sub folder of the Operations Folder. This includes videos, clips, and snapshots.
Check all Inspection deliverables associate with the dive have been backed up. These will be spread
throughout the Inspection Folder and includes videos, clips, and snapshots.
Use Windows explorer to delete all files associated with the dive. Do not delete any *.edge_project* or
*.edge_thumbs files. Data associated with the dive will appear in the following four folders:
Project Primary
Project Backup
Operations
Inspection
To backup editable data (Pre-Client deliverable) the folder containing the actual Project held on the Project Primary file
path must be copied. For example:
E:\edge5_project\<projectname>”
To back up the deliverable data, two options are available in Edge DVR and EdgePro. The choice of which to use depends
on how data is required to be accessed. EdgeLite only produces meaningful data in the Operations Folder.
Data in the Operations folder is organised by Dive. Data for each dive is stored in a sub folder with the same name as the
dive (e.g. ‘Dive 01 – calibrations’). The folder required to be copied containing the project is:
E:\edge5_operations/<projectname>
Data on the Inspections drive is structured via a work scope component tree called the Workpack, allowing for data to be
accessed according to work scope task. The folder required to be copied is located at:
F:\edge5_inspections/<projectname>
Failure to copy or backup the correct folder may create issues matching logs with collected data.
The following sections detail setting up the video on the Edge/Pro DVR system for operations.
Also included in the following setup instructions is the associated Icon for the setup wizard.
The Setup Wizard will prompt the user to setup the video, serial data and overlay, prior to operations.
When using the Setup Wizard, the following window will appear:
The Video Setup Page allows the user to setup the video sources and outputs.
Up to four (depending on licence) video sources can be displayed and recorded simultaneously.
There are three types of video device: directly connected (analogue, SDI, HDMI etc.), network camera (IP), and simulated.
Select the video source from the “Device” combo box.
SD Video Inputs – SD Analog (1:1), (1:2), (1:3), (1:4), (1:5), (1:6). 6 Inputs
4K Inputs – Pro Capture AIO 4K (1:1) 2 Inputs (HD-SDI or HDMI), Intensity pro 4k (HDMI)
Some video sources support automatic format detection. For these devices EdgeDVR tries to detect the format when the
‘Device’ is selected. Clicking “detect” will force automatic format detection to run again. Forcing automatic format
detection may be required if the video signal (camera output) changes during configuration.
Any input via the Magewell cards allows Brightness, Contrast, Hue and Saturation control.
Some types of IP camera are recognised by DVR. These automatically fill in parts of the connection URL. For other types
of IP camera, the entire connection URL must be entered manually. Select the appropriate IP camera “Type” to show
specific connection options:
The following IP cameras are recognised by DVR. More can be added upon request.
For recognised IP cameras the actual connection URL is shown under the cameras specific settings. This can be used with
third party video streaming clients (such as VLC) for troubleshooting.
Edge DVR can detect the video format sent by an IP camera, however the user must manually initiate this process.
Detecting the format of an IP camera can take a few seconds. The “detect” button has a yellow outline to remind the user
to initiate format detection when required.
DVR needs to know the frame rate of an IP camera, however not all cameras provide this information. In these cases, the
user must select the correct “Manual FPS”. Failure to do so will result in problems with video quality.
If DVR detects an appropriate video format, a preview of the IP camera video will appear.
If no live video source is available, the system has 5 simulated video inputs. Select one of the 5 simulated video options
and select the resolution.
There are several ways live video, with overlay, can be output from a DVR. Each video channel has an optional ‘Video
Output’.
There is also a dedicated “Pilot Output”. This mirrors one of the other video channels, but with a different overlay. Select
which source “Channel” should be used for the pilot output and select which “Device” should be used.
A DVR has two graphics cards, each with four Display Port outputs. Display Port outputs will appear in the “Video Output”
combo box as ‘Display 1’, ‘Display 2’ etc. To identify which monitor is attached to which Display Port click ‘Identify Displays’.
Attached monitors are detected when DVR starts. If a monitor is connected or removed when DVR is running, the “Device”
combo boxes may not update until the application is restarted.
A DVR with an Intensity Pro 4k card provides additional outputs. The active output is configured using Blackmagic Control
Panel.
Note: The DVR will select the most appropriate output resolution, based on the source channel, however some scaling
may take place (e.g. HD source channel to PAL composite output).
In the Video settings page, the recording Codec can be chosen within a drop-down menu, there are two options:
1. AVC H.264 – the most widely used format of compression. All Windows 10 machines are compatible with H.264 as
standard.
2. HEVC H.265 – Offers better compression than AVC but is not supported by default in Windows 10. Many third-party
applications can play this format.
DVR supports network video broadcast for each of the four source channels. The Edge Network Viewer application
automatically connects to all available channels. Third party streaming clients (such as VLC) can also be used. Section 2.8.6
covers network output in more detail.
3.5. Serial Data Setup
If / When using the Setup Wizard, the following window will appear:
Connect a null modem/crossover serial cable (If connecting to another PC) or a straight through serial cable (If connecting
directly to survey equipment) to one of the rear serial ports and select a port tab. Any COM device can be configured on
any DVR Port.
For standard RS-232 data, select Serial. Check all serial settings, match the data that is being transmitted by adjusting the
baud rate etc. Click Delimited text.
If all the settings are correct the live data should now be visible as seen below:
Each Field can now be renamed. This naming is then used to display the data on the overlay if required.
Assigning the fields, click on the dropdown “Type”. In this example we are assigning the heading and typing ‘Heading’
into the Name field.
The Edge/Pro DVR also has some industry standard ROV serial data strings, pre- programmed into the software to aid
setup. Contact Digital Edge, if standard ROV, Camera and 3rd party equipment strings need to be added.
The port number will usually be defined by the device sending the data.
3.5.3 Simulated Data
If a data input is not available, a simulated string can be setup. Click Simulated.
Enter the data to be simulated. Comma separate multiple fields. The fields will then be displayed, and these can be used
on the overlay and logs, as with normal RS-232 Data.
When using the Setup Wizard, the following window will appear:
There is one overlay for each configured video channel. In addition, there is a ‘master’ overlay which acts as a base or
template for all video channels. If a pilot output is used, then an independent pilot overlay is used.
The master overlay is automatically scaled for video channels with different resolutions. Any common overlay fields should
be placed on the master overlay. Channel specific overlay fields should be placed on the appropriate channel overlay.
The Pilot’s overlay is for display only and will not be recorded.
Video Channels, including Pilot Output must be setup before attempting to setup the overlay.
Free Text
Serial Data
Image/Logo
Shapes
To add free text, Click on the Text Icon. The “fixed text” field will appear on the overlay.
The font size and colour can be adjusted to suit using the interface below. The text can be changed by clicking the text
box and changing the text to suit.
The Anchor interface can be used to position the text to anchor to middle top or middle bottom etc.
The Alignment feature can be used to position the text within the defined boundary. The text boundary size can be
adjusted by changing the width(w) and the height(h). These position and size settings are available for all overlay fields.
Click the Time/date icon and select one of the 3 options. Position on screen as above.
Click the project buttons and select the project field to be displayed. Selecting the Custom Overlay Text allows the user
to add single line overlay to the screen during live operations. This is used for unexpected events etc. Position on screen
as above.
If required, a text prefix can be added. Enter the text into the Prefix box shown below.
Click the Serial Data Button and select the previously setup data field.
If required, a text prefix can be added. Enter the text into the Prefix box shown below. The units can also be added as a
post-fix. The user can also adjust the level of decimal places that will be displayed on the overlay, adjust up/down using
the arrows.
To add an image or logo, click on the Image button, then click browse to locate the image file path.
The image/logo can now be positioned using the drag and drop method. The width and height can also be adjusted to
suit.
If the logo is required to be transparent, adjust the Alpha Channel. This ranges from 255(solid) to 0 (Full Transparency).
There are 3 built-in shapes that can be used, click on the required shape and position. The shape can then be adjusted
for colour, outline and transparency as above.
The Edge PRO can display dynamic overlay which links to serial data to provide a visual indication of depth, heading etc.
Select the required Dynamic overlay, in this example we will select the Compass Rose.
The Compass Rose is now displayed on the overlay and can be positioned using the drag/drop method or by using the
Anchor positions. The colour and size can also be adjusted.
To link the Compass Rose to input serial data, click on the Main Heading dropdown and select the previously setup
Heading. The Compass Rose will now move in co-ordination with the heading value.
3.6.9 Adding Overlay Headers
This will then allow relevant Overlay fields to be selected and projected on to the Headers tab.
When a Main Video is started in the Dive page, the Header will be displayed until the User selects “End Header “.
When using the Setup Wizard, the following window will appear:
Online and offline eventing can be done in Edge and Edge Pro versions. Buttons are created and saved pre dive and are
displayed during the dive on the right-hand side of the main screen.
The events are then populated automatically into the excel dive, video, photo and anomaly logs. The0 event can also be
part of the photo and video clip filename. This is selectable when taking a photo.
3.7.1 Adding Buttons
To change the button text, double click the button text and add new text.
The buttons can also be configured to log anomalies. Click to enable. These anomaly events will then be displayed in all
logs and photos/video clips can also be flagged against any anomaly.
If any in depth information is needed to be added to the event, enable the pop-up box. When enabled, a popup dialogue
box appears in the centre screen. This allows the user to provide a text description for that event, this is also entered into
logs.
Data can also be assigned to a button, click on the data field dropdown and select the previously setup data set. In the
above example, we have assigned the Easting/Northing to the Position Fix button.
If a button is needed to be deleted, click on the button text, then click -. To delete all buttons, click Clear All.
Please note that the Button configuration file is saved with the Project, therefore if you want to use the same button
configuration for another project, it is advisable to use the Export button as shown below to save it to an external drive
which that can be imported into any future projects.
The Workpack Creator allows the user to create a list of items for inspection or a list of tasks in the form of a project tree.
When using the Setup Wizard, the following window will appear:
The following sections will guide the user on how to create a workpack (both versions) and add tasks (Pro version only),
and how this is displayed / used during Online operations.
For illustration purposes we will be using the following example as our basic component listing:
• A Platform
Members
Risers
To create a workpack the user may have a Workscope or a Project Document that will list the various items to include in
the tree.
When the workpack creator opens, you will see the following symbol. When you click on this the
following window appears prompting you to add a component name. This could be a location for
example. Using our example, we would enter ‘A Platform’ at this point.
As mentioned above, this is where you can add your first component. As this is the
top level of the tree this could be your location but this is completely up to the user.
For our example we have used A Platform as our top-level component, but this can
be anything that is suitable and relevant to your project.
When you have created your top-level component, it will look like this in the tree:
Now that you have created the top-level component you can start to build your tree. By right clicking on your component
(‘A Platform’ in this example), you will see the following menu with explanations of each option overleaf.
Add new at same level – This will create further top-level components. For example, if you had two (2) platforms for
inspection you would create another component at the same top level:
Add new at next level – This will create a component below the level above. So, in this example this would allow the user
to create a component below ‘A Platform’:
This can be repeated for as many components / items that the project requires:
Generate new at next level – This feature allows the user to add a batch of components at once, rather than individually.
This is a handy tool if you have several items under inspection that have the same prefix in their member ID:
For example, if your members for that level all had the same prefix you can insert the prefix into the ‘Pattern’ box (leaving
the ** in place), set the numerical values of the Ident and a batch of components can be created:
If you want to change the order of the components that have been created, the user can sort alphabetically as outlined
below or can manually change the order.
To do this click on the component to be moved. The user can choose whether to rearrange the order within that level,
or the user can ‘drop’ the component into another level. To rearrange the order drag the component to where it is to
be placed. This will be shown as a single white line. To move the component and drop it into another component listing,
wait until you see a white box and then drop into the new level.
Using our example as seen above, we can now right click on ‘Members’
and a menu is displayed with all of the options listed above plus
additional selections as seen in the image here.
Sort next level (5 components) – This will sort the list alphabetically.
Remove ‘Members’ including all deeper levels – This will remove the ‘Members’ and all components attributed to that
component in the levels below and you would only be left with ‘A Platform’:
Remove all unused at deeper levels – This will remove all components that have no data recorded against it. This is a
handy tool if a workpack has already been started as this will only display components that have data recorded.
Expand all – This will expand the whole tree so you can see all levels that have been created.
Collapse all – This will collapse the whole tree and show you just the top-level component (‘A Platform’ in our example).
The following buttons are shortcuts for the actions listed above:
This is a shortcut to add a ‘batch’ of components as described above, again to a lower level.
As the workpack is being created it will be saved with that specific project. The project details are displayed at the top of
the screen:
If the user wishes to use the structure of the workpack for another project, then the workpack should be saved to an
additional external drive by clicking the button below:
By clicking this button you can decide where you want an additional copy to be saved to. This
will be saved with the following extension:
Although this is a standard Edge workpack, it can also be imported for use in the Pro version (although there will be no
tasks as the addition of tasks is only facilitated in the EdgePro version of the software).
By clicking this button, the window below will open. This displays the licensing details for the current
unit.
This section will show the user how to add tasks to components included in the workpack.
The image below is the screen that is displayed for the Pro version of the Workpack creator:
As can be seen, the workpack that has been created is on the left-hand side, just as it is displayed in the Edge standard
version. With the Pro version of the software Tasks, Tags and Notes can be added to each component in the workpack.
There are 2 ways to add tasks in the Pro Version of the software. Firstly, the user can add a task(s) to each component
individually by clicking on the button below:
By clicking on this button, the selected task will be added to the highlighted component.
The image below shows the pre-defined list of tasks that can be selected.
These tasks are generic which is why they have been included.
As can be seen at the bottom of the list there is a ‘Custom’ button. Future version will allow the user to
customise task buttons.
There is also the option to batch add tasks to several components at once. This can be done by right clicking on your
component group, ‘Members’ in our example. The following menu will then be displayed:
As can be seen this has all the options that the Workpack creator in the
Standard version has, with the addition of ‘Add tasks to’ and ‘Remove all
tasks from’.
Add tasks to – This will add a number of selected tasks to the level below
the highlighted component. See examples below.
Remove all tasks from – This will remove all tasks attributed to all
components on the level below.
So, if the user wanted to add a GVI-2 (General Visual Inspection – 100% coverage), an AW (Anode Wastage) task and a
Contact CP task, it would be far quicker to add these tasks as a batch.
Right click on the correct component, in our example this would be ‘Members’. The following window appears. This is
informing the user that the selected tasks will be added to each of its 5 components on the level below. In our example
this would be to Member 01, 02, 03, 04 and 05:
The user can now add tasks to the 5 components from the pre-defined list.
The user can select as many tasks as required. GVI-2, Contact CP and AW have been
added in this example:
Once all the tasks have been selected, they will be displayed against the components as seen below:
Additional tasks can be added if required by clicking on the Tasks button. Also, if tasks have been added by mistake, just
click on the minus sign next to the task and it will be removed.
3.8.4 Notes
This feature of EdgePro allows the user to enter further instructions / clarifications on aspects of the workpack. These are
saved and are visible during online operations.
In our example we have added an instruction on where exactly to take contact CP readings:
The notes can be added to during live operations and with an unlimited number of characters they are also a handy tool
for the online personnel to note any items of importance as these are saved within the workpack.
3.8.5 Tags
Tags will add the ability to filter on certain aspects of a component. These could be position (North, East, South and
West), Wall Thickness, Outside Diameter etc. Currently tags can be entered but are not filterable.
To create a new dive, click on the icon on the main project page:
When a new dive is opened, the default dive number is set at 01. If the dive numbering needs to be changed, click on the
+/- or 01 and change to the new dive number or highlight the text and enter the correct number:
A Dive Name can also be added by clicking in the box and entering the dive name, and a video prefix if required:
Now enter the project details. Click on the + sign adjacent to the
project fields and add the Client, Contractor, Vessel and ROV/Diving
spread name.
When completed click the green tick and the user will be taken to the main recording
page as seen below. The user is now ready to start the dive and start recording.
Workpack Details (if using) Events Log Event Buttons Video Controls
The Start Video Button brings up the Start Video dialogue box. From here the user can select the
video channels to be recorded and set the Video Prefix.
The Instant Video Button starts recording the main video immediately when pressed and the
system remembers the last settings.
The Start Clip Button brings up the Start Video Clip dialogue box, from here the user can select
the video channels to be recorded and set the filename, by adding date/time, dive name and
current main video name, if required.
The Quick Clip Button starts recording a video clip immediately when pressed.
The Snapshot Button brings up the Snapshot dialogue box and allows the user to preview the
photo before saving. The overlay on the photo can also be shown or removed. Jpg or png photos
can be selected and the filename can be set by adding date/time, dive name and current main
video name, if required.
The Quickshot Button takes the photo immediately when pressed. No photo preview is displayed.
The Custom Text Button is used to add a quick line of text onto the overlay, without the need to
enter the overlay setup. This can be altered during a dive.
4.2. Workpack
If the user is utilising the option to use a workpack then prior to starting the main video, the user must select the
component that is planned for inspection from the workpack. The workpack tree can be seen on the left -hand side of
the main screen. This can be expanded to show all components in the workpack.
As can be seen above, the workpack also tells the user if any inspection of the components has started. In this example
there has been no data recorded against any of the components.
To select a component for inspecting the user must right-click on the appropriate component and select it as the Active
Component:
The user is now ready to commence recording video and carry out the inspection.
4.3. Recording Video
Click Start Video. This will start the main video recording.
During operations the video can be paused / re-started and stopped as required.
The Record Video Dialogue box allows the user to enter a video prefix if required.
The user has the choice to record all active channels or to disable the recording of a single channel, click the record button
adjacent to the channel number as can be seen in the image overleaf:
Once the main video has been started, each channel display with have a green border around it to show that recording
is taking place. Once the video is paused or stopped, the green border will disappear until recording starts again.
When the main video is started, an entry goes into the dive log to show start times and filenames. If using a workpack
this event will also include the component ID set as the active component. As we have selected Member 01 as our active
component, this is now displayed in the log, under Component, for each event logged against Member 01.
As the user progresses through the inspection the tasks associated with the Member 01 they can be ticked off when
completed as seen below:
If for some reason the task cannot be completed, we have included a list of generic options to select to provide the Client
with reasons as to why the inspection was not completed:
In our example we have stated the anode task cannot be completed as the anode was not observed:
This will then also be logged in the events table at the bottom of the screen:
When progressing through the inspection (if using the workpack feature) the user will be able to see the status of the
current workpack. The example below shows that Member 01 is incomplete due to a restraint on the anode task:
If there had been no restraint and the inspection was completed, the workpack tree would look like this which shows the
component Member 01 to be complete:
When recording a clip, the Video Clip Dialogue box allows the user to set how many channels are to be recorded which
is the same as the main video recording. There are several options as to what information is to be included in the file
name of the clip:
The video clip can also be assigned to a previous anomaly, or a new anomaly can be created.
When a clip is being recorded a film icon can be seen in the top right-hand corner of the channel to show that a clip is
being recorded:
The Video Clip can be paused and resumed if required. To stop the video clip, click End Clip.
The Snapshot feature can be configured to take photos across all 4 active video channels, or these can be manually
activated by clicking the Use button.
Each Photo can also be taken with or without overlay on each channel. Click the apply overlay button:
There are several options for inclusion in the filename of the snapshot as can be seen below:
The Instant Video feature allows the user to click and record video instantly. The system remembers the previous setting
from the Main Video Recording and applies them to the Instant Video. These video filenames are only time and date-
stamped with the previously set video prefix (if used), with no option for additional information in the filename.
When the instant video is started, an entry goes into the basic dive log, to show start times and filenames.
The video can be paused/re-started and stopped as required as in the Main Video recording.
The Quick Clip feature allows the user to click and record video clips instantly. The system remembers the previous settings
from the Main Video Recording and applies them to the Quick Clip. As with the Instant Video, the Quick clip filenames
are only time and date-stamped with the previously set video prefix (if used), with no option for additional information in
the filename.
The Quickshot feature, allows the user to click and take Photos instantly. The system remembers the previous setting from
the Snapshot feature and applies them to the Quickshot photos.
When a Quickshot is taken a log, entry is created with the ident (quick).
Video controls can also be operated by using the following keyboard shortcuts:
• F9 Snapshot Dialog
• F10 Quickshot
•
4.10. Online Eventing
The online event buttons are displayed on the right-hand side of the main screen, these buttons are setup pre-dive but
can also be changed during the dive.
The Offline editor will allow the user to view all anomalies, videos, video clips and photos that have been generated during
the dive.
The user can delete any item and can also take additional snapshots and clips within the video files. Additional events
can also be added and events can be deleted.
As can be seen below, the Black box tab lists all the black box video raw files which can be found on the Operations and
Inspections Drives:
To recover data from the Black box raw file the user must right-click on the appropriate file and the following will be
observed:
The user can now play the recovered video and export snapshots.
This button will export the video to the ‘Recovered’ folder on the Black Box drive
This dialogue appears once the Export Video button has been clicked, allowing the user to select
what channels to recover.
This allows the user to export a snapshot to the ‘Recovered’ folder on the Black Box drive.
The snapshot can be previewed just as in the main programme along with the ability to select
what channels to include in the snapshot. And as in the main program, file type can be selected
along with the ability to choose the filename.
This button will take the user to the location of the recovered files in Windows explorer as seen below,
both snapshots and videos:
Once the ‘Dive’ tab is selected there is a list of all videos, video clips and photos and the number of anomalies associated
with all dives in a particular project. 00000000000000000000It also lists a count of them all. If any are deleted offline then
this number will obviously change.
When the user clicks on videos, clips or photos, the list expands to show each individual video, clip and photo as shown
below:
A video, clip or photo will be displayed on the main video screen once the user clicks on the item in the left-hand pane
as shown below:
The user can now view the video selected by using the controls that are located above the events panel. The video can
be played at various speeds to allow additional clips or snapshots to be taken. The playback bar can be used to search
forwards / backwards within the video; skip back and forward; increase playback speed. The red line indicates the current
position within the video.
The user also has the option to view the video/clip/photo in Windows explorer by right clicking on the item in the left-
hand pane as shown below:
The selected video / video clip / photo can also be deleted by right clicking as also seen above. Any deletions would then
alter the total number of files displayed.
4.11.3 Inspection Tab
When the Inspection tab is selected, videos, clips and photos are displayed by the Workpack as seen below:
When the Offline Editor is opened and either the Dive or Inspection tab is selected, the following information will displayed
at the top of the screen:
When the user selects a video / clip / photo this is where the project information can be viewed. The Project name, the
Dive number, component (if using a workpack) and file name are displayed.
The Data box tells the viewer how many Video, Audio and Photo channels have been recorded. In our example we can
see four (4) video channels, one (1) audio channel and four (4) photo channels.
4.11.5 Offline Editing
The offline editor allows the user to add / delete events, videos, video clips and photos from the project. This can be
done within the Dive tab or the Inspection Tab.
When a video is highlighted from the list on the left-hand side of the screen, the associated events will be displayed in
the events pane at the bottom of the screen.
So as can be seen the video 2020-04-15_140441 has been selected for Offline checking:
By right clicking on any event the user can either remove the event or can view the individual video or photo channels
associated with the selected event:
The user can also add extra events that may have been missed during online operations. The event buttons are located
on the right-hand side of the screen, as in the main program:
To add an event, play the selected video / video clip to the time where the new event is to be added and simply log the
new event as you would do in the main software. Additional snapshots and video clips can be added too. This then
changes the summary of number of video / video clip / photos / anomalies.
By clicking this button, the user can manually enter an event into the log
A dialogue box will pop up prompting the user to enter the event text. This
will now appear in the logs as seen below:
In the Offline Editor you can also configure the events buttons to add / change / delete buttons, just as can be done in
the main software.
Once the relevant video or clip has been selected, the user can use the buttons below to take additional clips and
snapshots as required as is done in the main recording screen of the software:
Any additional clips and snapshots will now appear in the left-hand pane as detailed in Section 4.2.
4.11.7 Change Layout
Another feature is the ability to change the layout of the channels you are viewing by clicking the button below which is
situated in the top right-hand corner of the screen. This can be useful if the user needs to enlarge any items on any of
the recorded channels.
To this:
This is a utility used by the Software Development Team with no function for the user.
The EdgeDVR / Pro has 3 removable front mounted hard drives for project data storage.
Note – Do not manually move/delete any video, photos or video clips for any folder created by the EdgeDVR. Only do
edits from within the EdgeDVR software. The EdgeDVR relies on this file structure for the production of the logs, any
deletions will risk the integrity of the project.
4.14. Operations Drive
This drive stores the project in a dive by dive format. All video, photos, video clips and logs that are recorded during the
dive are stored in individual folders, within the project folder.
The dive folder contains sub folders, for Logs, Video, Photos and Video Clips.
The log folder contains the excel dive, video, photo and anomaly logs.
The EdgeDVR/Pro software produces excel dive, photo, video, and anomaly logs.
The video, video clips and photos can be viewed directly from the dive log, by holding down CTRL and clicking on the
link in the log.
Again, the video, video clips and photos can be viewed directly from the dive log, by holding down CTRL and clicking on
the link in the log.
The yellow bands separate each single video file, the Green band indicates a photo and a red band shows any anomalies.
The photo log is multi-channel, if required and shows the project info and related video info for the photos.
The anomaly log is a simple record list of all anomalies and the associated video is displayed by clicking the link as before.
Project video clips, within Dive 1 are in the Video Clips folder.
The EdgeDVR/Pro software also stores raw project data onto the operations drive. This is to be used for backup purposes
and should not be accessed by the user.
This drive stores the project by location. All video, photos, video clips and logs that are recorded at this location are stored
in individual folders, within the project folder.
The project is located within the edge5 inspection folder. The folders contained within this folder will depend on the
workpack associated with this project. When any data is recorded against a component in the workpack, a folder is created
for each component.
In the example below, we have ‘A Project’ and within the project we have ‘A platform’. All data associated within the
platform, will be stored in this folder.
In the example below, we have another level of components which are labelled Members.
In the above example, we have 2 folders. The log folder contains all master logs for this location.
These logs are in the same format as the operations drive, except, these are for the whole project location.
4.21. Blackbox
The EdgeDVR/Pro records automatically to blackbox when Edge DVR is opened. This blackbox is a raw format and it
records all active video channels and all survey data in real time. The Blackbox drive will automatically write over once its
limit has been reached. Factory set to 2tb.
It is possible to recover video and photos from the blackbox, using our online / offline editor only. See section 4.1.
Within the edge 5 blackbox folder the raw project data is stored, this raw data comprises of all blackbox video, project
video, clips, photos and all serial data.
The Program Data folder contains the current Edge/Pro config files, to enable recovery.
The Recovered folder contains any video or photos that have been recovered from the blackbox using the Edge
Online/Offline editor.
Included in the Installer is an application called Remote DVR. In circumstances where the DVR is the slave to a 3rd party
Inspection program such as COABIS, Nexus, or Apollo, Remote DVR can be used.
Select the relevant Inspection Client Application and Remote DVR will Slave to the parameters of the Client.
Camera Source can be configured within Remote DVR in the same manner as Edge5. Remote DVR currently supports a
single video channel. Future versions will support up to four channels when used in Nexus mode.
Overlay can also be configured constrained to the parameters of the Client Application.
Edge DVR supports network video broadcast for each of the four source channels. Network output is disabled by default.
The DVR has two network connections (See section 2.8.6), however video is only broadcast on one network at a time.
Network broadcast is configured from the Video Setup Page. Select the “Network” on which to broadcast video. Each
network is identified by the DVR IP address for that network. Selecting ‘127.0.0.1’ means network video will only be viewable
on the DVR (nowhere else on the network).
A number of UDP ports are used to broadcast video and other DVR data. The “Base Port” defines what UDP ports are
used. Ports in the range [base port] to [base port + 10] should be reserved for use by the DVR. For the default ‘Base Port’
of 8000, UDP ports 8000, 8001, 8002 … 8010 should be reserved for use by the DVR.
Once the network adapter and base port have been selected, video broadcast must be enabled for each required channel.
Note: Network video broadcast is suspended while on the Video Setup Page. Video broadcast will begin when navigating
away from the Video Setup Page.
Broadcast video can be viewed using the Edge Network Viewer application included in the Installer, or other third-party
streaming clients (e.g. VLC).
When using the Network Viewer, a connection to each video stream is automatically established using the defined ‘Base
Port’. Ensure the Base Port in DVR is the same as the Base Port in Network Viewer.
If using a third-party streaming application (e.g. VLC) the following URL should be used:
For example, if the selected “Network” is ‘192.168.1.100’ and the “Base Port” is ‘8000’ the following URLs should be used:
Channel 1: rtp://:8001
Channel 2: rtp://:8002
Channel 3: rtp://:8003
Channel 4: rtp://:8004
EdgeDVR uses UDP broadcast to send video data to viewers. For a typical small network this means all devices must be
configured to use the same subnet. For example, if the Netmask is 255.255.255.0, then the first three parts of the IP
address for each device must be the same (e.g. 192.168.1.*).
The Network Viewer application automatically discovers the DVR. This means no changes are required if DHCP assigns
the DVR a new IP address. If using a third-party streaming client (such as VLC) then changes to the DVR IP address will
require changes to the URL used.
Some networks (particularly those connected to corporate IT systems) may block UDP broadcast traffic. Contact your
network or system administrator to ensure UDP traffic is allowed on the required ports.
Video streaming can use a significant amount of bandwidth, especially with HD/4K video sources. It is recommended that
one network is used for video (and other low latency traffic) and another for general office devices such as printers and
network attached storage.
Edge5 Workpack Creator is a separate application that comes with the Installer.
This application allows the creation of either an Inspection based Tree of folders and Sub-Folders, with many Inspection
specific tasks pre-loaded, organising the Inspection workflow and arrangement of Data Storage, or a Project Task based
Work pack flexible enough to be utilised for Data arrangement of the Project.
By creating a Workpack and in Edge 5 activating the specific folder for Data to be recorded too during the Dive, it creates
an alternative way to view the Project rather than sequential Dive Numbers as it is stored on the Operations Drive.
Data stored via an Activated Workpack folder is found on the Inspections Drive, in the relevant Edge 5 Project folder.
Workpack Creator allows the user to construct a new Workpack Database, or a previously created one can be imported.
Workpack Creator will allow the import of legacy EdgeDVR V4 saved Workpacks by selecting the document type on
import.
Once a Workpack has been imported or created, a right click on the 1st folder will show options available for further
development of the database structure.
Shown below is a preloaded example of a Project Task based database in Workpack Creator.
Shown below is how the same Workpack is displayed in a Dive within Edge 5. For data to be recorded into the Workpack
the relevant component needs to be activated prior to selecting Record.
Edge Archive is a separately licensed application that creates a real time data Mirror of the Project from the two Client
Deliverable folders and the Raw editable Project within Edge DVR if required.
It allows for:
• Phased delivery
In Use cases where all data for a project fits on the 4U/Laptop internal drives:
Ie The user requires a complete copy of the raw project data and the operations/inspection deliverable at the end of the
project. The user doesn't have time for a complete copy during demob so uses Archive to make a real time mirror of the
raw project and deliverable data.
• Two archive destinations: one for raw project data and one deliverable data
• Each archive destination has a single archive folder on an external device (NAS, USB hard drive etc.).
• At the end of the project, once archiving has completed all data is set to offline and archive folders are
ejected. The user then closes Archive then deletes the original project using DVR.
Ie All data for a project fits on the 4U/Laptop, but the user needs to deliver data to the client after each dive. Another
arrangement (e.g. that outlined above) is in place for backing up data at the end of the job.
• One archive folder for each Dive (or however many dives the client needs grouped together). Each
archive folder can be on a separate external device (NAS, USB hard drive etc.) or multiple archive
folders can be on the same device.
• After each dive (or however many dives the client needs grouped together) the user creates a new
archive folder, sets the existing dives/folder offline, then ejects the old archive folder. The device
containing the ejected archive folder can be handed to the client while new data is copied to the new
'active' archive folder.
All data for a project fits on the 4U/Laptop, but the user requires one copy of the deliverable on a shared NAS, and two
further copies of the operations deliverable on external USB hard drives. The shared NAS is large enough to hold all the
data, but multiple USB hard drives are required.
• One archive destination with a single archive folder on the shared NAS
• One archive destination for deliverable "copy A", with an archive folder on the first batch of external
USB drives.
• Another archive destination for deliverable "copy B", with an archive folder the second batch of external
USB drives.
• As each external USB drive fills up, it's data is set offline, then the folder is ejected and shipped back to
the beach.
8.4. Simple data archiving
The 4U/Laptop does not have enough space for all project data, however a large external storage device (e.g. NAS) is
available.
• Three archive destinations (raw, operations, inspection), each with a single archive folder on the NAS,
are used.
• The user records, processes and reviews data using DVR as normal.
• Once a dive has been processed & reviewed the user sets it offline. This automatically deletes the data
files from the 4U/Laptop.
8.5. Complex data archiving
As for "simple data archiving" above, but each archive destination has multiple archive folders. This may be required if all
project data can't fit on a single external device (e.g. no NAS available, very long project etc.). External devices may be
ejected when they are full to free up USB ports.
Fig 1
Fig 1 shows some different scenarios of data archiving available in Edge Archive.
After a Project has been set up in Edge DVR, Open Edge Archive,
1. Add a Project.
3. Create a Folder save location for the Archive Destination to copy too.
When Edge Archive opens, the “Add Project” button will show any active projects stored locally on the DVR.
Select the Project you require to archive. – in the Example above Project TK-421 Post Inspection is available to archive.
Once the Project is selected, Edge Archive will ask you if you would like to create a default archive “Destination” for each
data type, if confirmed Edge Archive will create a Destination for all three types of data as detailed below and the next
step is to “Create a folder”, or, the User can choose to manually set up each “Destination” individually.
Project Raw data files: This will archive the data held in the DVR Projects folder. In order for Edge Archive to delete local
storage within a project, the Project Raw files must have been copied and verified.
This is the live database Raw files, in future this will be editable by Edge Editor Stand-alone app, or for a historic Archive
to be able to be re-imported onto a DVR from a NAS to make a live editable Project again. – not yet supported.
Operations Client Deliverable: This is a copy of the client deliverable Mp4 files, photo’s and associated logs, stored in
sequential Dive order. It is an archive of the DVR Operations folder.
Inspections Client Deliverable: This is a copy of the client deliverable Mp4 files, photo’s and associated logs, stored via
The Work pack Project Task based Tree. It is an archive of the Inspections folder.
Select if you want Edge Archive to create an archive Destination for all of the relevant data types, or manually create a
Single copy of one or all of the data types. Edge and Edge Pro can create an archive Destination for Project Raw files,
Operations Client Deliverable and Inspections Client deliverable folders for the Project.
To be able to mark data “Offline” a copy of the Project raw data files plus one Client Deliverable (Operations or Inspections
data) must have been previously “Verified” by Edge Archive.
Making data “Offline” is the process of removing files from the local storage on the DVR, done via the Offline Editor.
Edge Lite has no Inspection Work pack so will only create a Projects and Operations Destination.
Above Edge Archive created an archive Destination for Project Raw files, Operations Deliverable files and Inspections
Deliverable Work pack task-based files.
The next step is to Create a Folder save location for each Archive Destination on a NAS or external storage device such
as a usb drive. Archive can use UNC file paths or mapped drives.
Above “Create Folder” has been selected which opens the explore window for a mapped drive save location to be
allocated.
Archive will automatically name the folder in-case sequential folders are created.
Here the save folder has been created for the Inspection Deliverable Archive Destination.
The yellow warning flags remind the user that save Folders for the Operations Archive and Project Raw Archive
Destinations have not yet been created.
In the middle section data from the “Live Project” in Edge DVR is now Archiving for the Inspections Deliverable.
In the example below, all three save Folders have now been allocated on the NAS drive:
This completes the setup of a Live Archive for all three types of data collection available in Edge 5.
It must be noted when Archive is Open, a Project will not be able to be deleted in Edge DVR.
If the Archive is complete and Project completed, close Archive and the Project will then be able to be deleted.
When Edge DVR is also running, Archive has traffic light indicators to show it has comms with DVR, and has comms with
the NAS to be actively Archiving data.
For example Project / Operations and Inspections all copy to a NAS in one folder each. Each Folder holds a complete
copy of its Archived data.
At the same time a destination for the Operations Deliverable and Inspections Deliverable can be copied incrementally
on separate external USB hard drives for the Client’s Use or Project Engineer’s use etc.
In the DVR Online dive page, if the Project is Archiving this will be indicated in the top left of the Dive screen in the Project
window [Archiving] or [No Comms] indicating an error with Archive:
If a project is Archiving, in the Edge DVR Offline Editor at the end of the Project, with no further data required to be
collected, the Dives or Project Work pack Components can be marked “Offline” by Unlocking them and right clicking over
the Dive / Component:
If the files are left “Unlocked” be aware that this will pause Archive. Any file not completed will start archiving again once
“Locked”.
Setting Data Offline in the Offline editor will delete relevant files from the local storage of the DVR this will only be allowed
if both the “Project Raw files plus one Client Deliverable” have already been archived. Verification is done at time of copy.
The folders and logs will remain aware of the overall project, but mp4 files, snapshots and relevant Raw data will be
removed, freeing up space within the project.
The master copy now exists in the Archived data on external storage.
Once the Dives have been marked “Offline” “Lock” the files again before returning to the Edge Archive app. These files
are no longer able to be actively processed by Edge DVR locally.
In Edge Archive, active save folders can now be “Finalised” and “Ejected”. Once the project is completed close Archive
and Delete the Project from the local DVR in the DVR homepage.
Above Each save Folder is 1st Finalised, then Ejected by “Right Click” over the folder.
At this point, all data Archiving on the Project is done. The Project can be deleted via the Homepage in Edge
DVR, the USB drives can be removed and the NAS can be disconnected.
DVR and RemoteDvr place specific constraints on the Windows System Clock. Any reference to 'DVR' in this section also
applies to 'RemoteDvr'. If the DVR clock needs to be synchronised with another device then the user must carefully read
and understand this section before recording any data. Failure to do so may result in unexpected data artefacts, or system
crashes.
On some projects the data recorded by DVR may need to be cross referenced with data recorded on another device. To
do this the DVR computer Windows system clock must be kept in sync with another clock. We call these the "DVR clock"
and the "reference clock". There are various ways to synchronise the DVR clock with a reference clock; some require
regular action by the user while others are mostly automatic.
9.1. Clock Adjustment
There are two ways a clock can be adjusted to ensure it shows the correct time:
9.1.1 Jump
If the clock is 10 seconds slow, then it is instantly advanced by 10 seconds to read the correct time. This method can be
done by hand using the Windows "Date & Time" settings.
9.1.2 Drift
If the clock is 10 seconds slow, then it is set to run slightly fast. After a while the clock will match the correct time, at which
point it is set to run at normal speed. This method requires configuring the Window Time service, or a third-party
application.
9.2. Windows System Clock Requirements
DVR uses the Windows system clock to measure the passage of time. The Windows system clock internally tracks UTC
time, but uses a time zone (and optionally daylight-saving time) for display.
While DVR is open the Windows system clock must never go backwards (it must be monotonic). If DVR detects the
Windows system clock has gone backwards it will immediately show an error dialog then exit. If this happens while
recording, the associated video files may not be playable, or may be missing some data.
While DVR is open the Windows system clock must not jump (it must be steady). If DVR detects the Windows system clock
has jumped it will show an alert box informing the user. The effects of a forward clock jump are unlikely to cause data
loss, however subsequently using the data with the Offline Editor Page, Editor application, or Viewer application may not
behave as expected. A backwards clock jump will cause DVR to immediately close as described above.
This behaviour will likely change in a future release to allow the user more flexibility in how they perform time
synchronisation.
9.3. Third Party Time Synchronisation Tools
Prior to Windows 8, Microsoft did not provide a reliable, built in, way to synchronise the system clock. A number of third
party and in-house applications were developed to perform this task. Due to the way these applications adjust the system
clock, many are unsuitable for setting the DVR clock.
From Windows 8 onwards the built in Windows Time Service can provide very accurate clock synchronisation. Appendix
1 gives an example of configuring Windows to synchronise the system clock in a way compatible with DVR.
The user is responsible for ensuring any third-party time synchronisation tools do not jump the Windows system clock. As
a guideline: any application which uses the Windows function SetSystemTime() is unlikely to be suitable; any application
which uses the Windows function SetSystemTimeAdjustment() is likely to be compatible with DVR.
Also included in the Installer is a stand-alone application that enables a project client deliverable to be viewed but not
edited, as if it was within Edge 5 on any Windows 10 computer.
This can be either viewed via Dive number by accessing the relevant project in the Operations drive as below:
Or alternatively it could be viewed via the Workpack Tree database by accessing the relevant project file on the Inspections
drive.
Also, on the Desktop is a shortcut that can be seen above, that when opened creates a zip file of relevant data if a bug
or crash is encountered in Edge 5.
After encountering the error, prior to opening up Edge 5 again, click on the Edge Support shortcut, this will generate the
relevant data, which can then be sent to support@digitaledgesubsea.com for analysis.
The Button Editor allows the import of Edge5 Hotkey files or legacy V4 hotkey files in addition to being able to create a
new template from scratch.
To import a Legacy V4 hotkey file, select import and change the file type to legacy V4.bconf
The installer allows the installation of the different Edge apps, components can be selected to be installed or not.
The Network Viewer and Client Viewer can be installed on any Windows 10 Pc without need of a license dongle.
The Planning Tools adds the Workpack Creator and the Button Editor which can also be installed on any Windows 10 Pc
without need of a license dongle.
The DVR (4U/Laptop) component selection will install EdgeDVR, RemoteDVR (for Coabis, Nexus and Apollo integration),
and Edge Editor. All of these require a valid license dongle.
A 3rd party program called Virtual Cable is used to keep the Mic source selection constant. Windows 10 can offer changing
mic selections which can cause issues when hot plugging mic’s.
An unbalanced Mic as supplied with the DVR should always be connected even if not used.
For Setup, make sure the Mic is connected in the pink receptacle on the rear of the DVR, In the Windows 10 sound settings,
for Mic Input Virtual Cable should be selected.
The following use cases are only examples and do not form an exhaustive list. A different approach can be used as long
as it ensures the Windows system clock does not jump forwards or backwards while DVR is running. See Section 9 for
details of what DVR and RemoteDvr require from the Windows system clock.
If you have a special use case please contact Digital Edge Subsea Support for guidance.
There is no need for the DVR clock to precisely match any other clock.
Ensure no third-party time synchronisation programs are running. We recommend restarting the PC to check no third-
party time synchronization programs are configured to automatically run when Windows starts.
15.1.2 Windows Time Service
If the Windows system time is wrong, click 'Change' and enter the correct time.
In the 'Change the date and time' dialog click 'Change' to adjust the clock.
Note: the 'Change the date and time' dialog uses local time rather than UTC. This means the selected 'Time zone' and
'Adjust for daylight saving time automatically' settings are taken into consideration.
Launch DVR (or RemoteDvr) and do not adjust the Windows system clock again.
15.2. Example 2: Manual Clock Synchronisation
The DVR clock needs to match another clock; however, the DVR clock does not drift too much over the course of a dive.
Automatic time synchronisation is disabled, however built in or third-party tools may be used to adjust the clock.
15.2.1 Procedure
There are various ways to adjust the Window system clock at step 2. The following are some examples:
In the 'Change the date and time' dialog click 'Change' to adjust the clock.
Note: the 'Change the date and time' dialog uses local time rather than UTC. This means the selected 'Time zone' and
'Adjust for daylight saving time automatically' settings are taken into consideration.
If the DVR PC is connected to the internet then by default it will use time.windows.com as a reference clock. If a different
reference clock is required then it must provide an NTP server. To change the NTP server that windows uses:
Ensure 'Synchronise with an internet time server' is checked and enter the NTP 'Server' address.
Click 'OK' to close the 'Internet Time Settings' dialog, then 'OK' to close the 'Date and Time' dialog.
To use the time server to synchronise the DVR clock, perform the following after closing DVR (or RemoteDvr):
The Windows system clock should automatically change to the correct time. If it does not, click 'Sync now'.
Ensure that 'Set the time automatically' is off before starting DVR (or RemoteDvr)
A third-party tool may be used to adjust the Windows system clock. In this case the built-in option to 'Set the time
automatically' must be off.
In addition the third party tool must be configured so that it does not adjust the Windows system clock while DVR (or
RemoteDvr) are running. The user must ensure DVR (or RemoteDvr) are closed before manually triggering a clock
adjustment.
The DVR clock needs to closely match another clock, and the DVR clock drifts too much over the course of a dive.
This example uses the built in Windows time synchronisation tools however a third party program may be used as long
as it does not jump the system clock forwards or backwards as described in Section 9.
https://docs.microsoft.com/en-us/windows-server/networking/windows-time-service/configuring-systems-
for-high-accuracy
Microsoft also outline the requirements to achieve a given target accuracy (1 second, 50 milliseconds, or 1 millisecond) in
"Support boundary for high-accuracy time":
https://docs.microsoft.com/en-us/windows-server/networking/windows-time-service/support-boundary
The Windows Time service must be running. By default, this service is started and stopped automatically, however we
require it to be running all the time. Launch the 'Services' app
Scroll down to "Windows Time" and ensure its 'Startup Type' is "Automatic" and its 'Status' is "Running".
If the Windows Time service is not set to Automatic start-up: right click and select 'Properties'. Change 'Start-up type' to
"Automatic". Click 'OK'.
If the Windows Time service it is not running, right click and select 'Start'
Use the registry editor to ensure the following values are as shown
HKLM:\SYSTEM\CurrentControlSet\Services\W32Time\Config\
MinPolInterval Decimal 6
MaxPollInterval Decimal 6
FrequencyCorrectRate Decimal 2
MaxNegPhaseCorrection Decimal 0
Page 117 of 119 DESLTD-REF-5007 Rev 3 UNCONTROLLED IF PRINTED
Digital Edge Subsea Limited Quality Management System
MaxPosPhaseCorrection Decimal 0
HKLM:\SYSTEM\CurrentControlSet\Services\W32Time\TimeProviders\NtpClient\
SpecialPollInterval Decimal 64
If any registry settings are changed the Windows Time service must be restarted for them to take effect
The reference clock can be configured using either the Registry Editor, or the command line tool w32tm. If using the
w32tm command line tool an administrator command prompt is required.
The following registry key is used to specify the reference time server
HKLM:\SYSTEM\CurrentControlSet\Services\W32Time\Parameters\
The current reference time server can be checked with the following command
Information about the automatic time synchronisation is available through the following command
When configured as described above, Windows will never jump the system clock to match the reference clock. If there is
a large difference between the Windows system clock and the reference clock, a 'jump' adjustment can be forced by
running the following command. Ensure that DVR (or RemoteDvr) are not running.
If a DVR requires a license upgrade, this can be accomplished remotely when internet access to the DVR is unavailable.
Email support@digitaledgesubsea.com, provide the DVR serial number and version of software being utilised, request a
License upgrade with authorisation from the relevant party in the Client company.
This will provide you with the Dongle number and the update number.
you will need to provide this to Digital Edge Subsea ltd for each DVR and we can then generate a code and provide it to
you, this is to be copy and pasted into the "Enter Update Code Here" text box in Dinkey change.