Delta Watch: Upgrading to v2.15

With the introduction of Delta Watch v2.15 there are some significant changes made in the software. Some of these changes require the user to perform some adjustment to the setup of Delta Watch after the database is upgraded to the new version. This article covers the steps required for this process. You can check your current Delta Watch version in the menu item MENU: HELP -> ABOUT DELTA WATCH.

We strongly suggest that if you are upgrading an existing Delta Watch system, which is used to actively process data, that you contact your Topcon support for advice and possibly assistance with the process.

a) License file update

If upgrading from Delta Watch (DW) v2.11 you would need to have a new license for your existing installation. If this is not send to you then please request one. Ensure you refer to the original order for your Delta Watch software. If you later purchased any additional module or sensor capacity then please mention this. Additionally; in your existing setup make a screenshot of the ‘About Delta Watch’ dialog for validation purposes. Once received we will generate an updated license for DW v2.15 for you.

b) Free space

As with any database (DB) where continues data is fed into, we need to keep an eye on the available disk space. The upgrade process does offer you the option to make a backup of the current DB before upgrading. We strongly advice to do so, but we have to make sure we got enough space to perform this action.

To check how much space we need we simply multiply the current DB size by 2 and add 500MB to the value.

The resulting figure is a safe value to install the new DW and create a backup copy of your DB. You can check the size of your current DB in your ‘Topcon Delta Watch/Database’ folder. Here there will be a file called ‘TUNIS.FDB’

This would also be the ideal time to clean-up your data and reduce your DB size; BEFORE you upgrade! Please look for ‘Delta Watch – DB Management’ for details.

c) Select the right time

Because the upgrade from v2.11 to v2.15 does require manual adjustments the upgrade process will take longer than normal. It is therefore important to schedule the update and notify others as the system might be offline for one or more epochs, depending on your settings.

Alternatively, if your current DW installation does not exceed 500 sensors and/or 5 project you could use a second computer and completely prepare the DB on this. The trial version of DW could be installed on a computer on which DW was not installed before. Now make a copy of your current DB and transfer this temporarily to this second computer, make sure the used folder structure and drive names are completely mirrored on this second computer. Now start DW 2.15, let it do its automated DB upgrade and then follow the rest of the document to do the manual adjustments. You can also check the importing and exporting using a few new datasets. Once all is satisfactory you can then close down the active DW, upgrade to v2.15, transfer the DB and start DW again.

NOTE:   Whenever making a copy of the DB or putting a copy back, ensure DW is completely closed and not running. There is always a second file in the Database folder called ‘SCHEDULER.FDB’ make sure this file is always copied together with your DB.

d) Collecting required information

To avoid unnecessary delays, we advise to note down some details and information that is required to be entered in the new installation. Below a checklist.

1. Project specific
   1. Time zone
   2. Coordinate reference system
   3. Archive directory, see notes
   4. Data Export path for Processed point export, see notes
   5. Data export configuration for export to information system ,see notes on end of article
      1. Path
      2. Point group(s)
2. Email server settings
   1. Current settings can be found in ‘DW > ADMINISTRATION > SYSTEM CONFIGURATION > MAIL SERVER’. See change notes about improved email server options
3. Check your coordinate transformations
   1. v2.15 only supports the following transformation, check you are not using other types. If you are then convert them to one of the below. You can find this under ‘DW > ADMINISTRATION > COORDINATE TRANSFORMATION’
      1. LQS-Alignment
      2. LQS-Two point
      3. Rotation

Installed DW on a different location?

If you had chosen to install DW on a different location on the same computer than you will need to transfer your DB files first. To do so, navigate to the database folder of your previous installation and manually copy the files ‘TUNIS.FDB’ and ‘SCHEDULER.FDB’ to the database folder of the new installation.

NOTE:   As you have chosen for this process be aware that DW has not made a DB backup for you. It is advised to do this yourself. Simply copy/archive the above mentioned files to a save place making a note of the version of DW these were from and at what date it was made.

Don’t forget to update any ‘start menu’ items, shortcuts or batch files etc that are used for launching Delta Watch.

Install the updated license file

The updated license file, called ‘Tunis.lic’, will needs to be put in the correct location.

• Navigate to your Delta watch installation folder and locate the ‘Configuration’ folder. A default installation would find this under ‘Topcon Delta Watch/Configuration’.
• Copy your new supplied ‘Tunis.lic’ file here, overwriting any existing file if found. You might want to make a backup of the old license file, just in case, before doing so.

Additional project separation is implemented but this now requires us to configure some additional information. Navigate to the ‘DW > ADMINISTRATION > PROJECTS’ module. For each project enter the required information, your earlier taken notes can assist here:

1. Time zone
2. Coordinate reference system
3. Archive path, DW will always create a new folder with the project name on the location you specify.

If you are using DW to send report; alarms or warnings of any kind using email then the email server settings need to be entered again. This might also be a good time to change the email account if you want to use a more secure email connection method. The settings can be found under ‘ADMINISTRATION > SYSTEM CONFIGURATION > MAIL SERVER’

For each project the network adjustment settings have to be converted. To optimize the DB the adjustment settings are not stored with each epoch but only with the network settings. If a network does not have adjustment settings then it will copy these from the first epoch, if there is one. If the network has no adjustment settings and no epoch then the default settings will be copied as defined in ‘ADMINISTRATION > SYSTEM CONFIGURATION > PROCESSING TOTAL STATION DATA’. Networks that already have adjustment settings remain unchanged. Repeat usage of the conversion function has no effect.

To convert all networks in a project:

1. Activate the project in ‘ADMINISTRATION > PROJECTS > PROJECTS’.
2. Navigate to ‘ADMINISTRATION > MANUAL GEODETIC NETWORKS’, item 1 in image below
3. Select your project in the project tree, item 2 in image below, the project is highlighted orange
4. Click on [ Convert adjustment ], item 3 in image below
5. Now repeat the steps for the automated networks, item 4 in image below
6. Once manual and automated geodetic networks have been converted repeat the above steps for each project in your DW.

Not all transformations are supported anymore, if you were using any coordinate transformation to apply to point groups for specific reporting and/or alarming purposes then check the settings.

The only supported coordinate transformation types are:

• LQS-Alignment
• LQS-Two point
• Rotation

DW also applied some more checks on each definition and does not allow empty label fields anymore. To adjust this, select each definition in turn and check/edit the label field to ensure all is compatible, see image for example; all required field are marked with a red dot.

If you have multiple projects then due to the conversion from a previous version of DW it might be possible that you see some Coordinate transformation definitions in your project that belong to another project. As these are most likely still in use by the other project you will not be able to remove them. Simplest way to mark them as not applicable is to rename them in all projects except in the project where they belong.

This Delta Watch version introduces a new Import / Export module. All DW import and exports are going to be managed from within this module. It is not possible anymore to configure automatic exports from within a geodetic network setup. You would therefore need to re-create the exports that you had running before the upgrade. Please use your notes as taken during the preparation phase.

KRONOS compatible exports
This version of Delta Watch introduces an extra field called ‘External name’. This field will also be used by any predefined KRONOS exports format. If you are using a KRONOS format for exporting data then we need to ensure this field has the right content. You can either manually edit this field OR use a script to copy all ‘Remark’ fields to ‘External Name’ field and then empty the Remarks. This task needs to be done before setting up your exports! See the notes on ‘External name field’ at the end of this article under Data export.

In Delta Watch navigate to ‘INTERFACES > IMPORT & EXPORT’ for these configurations. This module is not project specific so all exports can be configured without project switching.

For details on How To configure the exports we refer you to the document ‘Delta Watch – How to configure data exports’. Pictured below is a typical setup to recreate the ‘processed point export’.

This version of Delta Watch introduces the ‘External name’ field which replaces the function of the ‘Remark’ field when doing a Kronos export. Please see notes un the end of the document for more details.

THP data import was previously completely configured in the Point and Limit management module but with the introduction of the ‘Import & Export’ module some minor adjustments are required and the import definition needs to be created. This allows you to see all imports on one location and simplifies management. For details on how to configure please refer to the document ‘Delta Watch – How to setup THP data import’.

In Delta Watch navigate to ‘INTERFACES > IMPORT & EXPORT’ to configure the THP import.

Below two screenshots from a typical import configuration for meteorological data from a Delta Link THP sensor.

This new DW version has some major improvements. Below here are some highlighted as they are important to know about when upgrading working DB’s.

• Email Server

The mail server configuration is improved by supporting secure connections. This does however require the user to re-enter all mail server details.

• Archive folders

The Archive folders are now more structured and the root archive folder can be specified per project. This means that files that were previously archived in ‘Topcon Delta Watch/Archive’ can now be archived in a user configurable location.

• Data Import

This new version of Delta Watch introduces the import & export module. THP data import, for example, will be done from here and if you previously where importing THP data files you would now need to re-configure it to work with the new module. Data import for the new hardware diagnostic module is also configured here.

• Data Export

Export Types

This new version of Delta Watch introduces the Import & Export module. All data export will be done from here and is much more flexible in setup and export options. Therefore if you are currently making use of any of the data export options, it would be good to review your requirements as there might be better option now available. If you want to continue using the same export files/formats then be aware of using the correct definition.

1. ‘Export to information system’, when done from import and export module, has got all the old export formats, as could be written by DW, predefined:
   1. Iris (Group; Name) -> Iris geodetic point export
   2. Iris (Name; Group) -> Iris geodetic point export
   3. Kronos_3Ddeformation
2. ‘Processed point export’ has retained its name

External name

This version of Delta Watch also has a minor change in the use of the ‘Remark’ column, as found in the Point and Limit management, with regards to data exports. A new column called ‘External name’ is introduced and this column is now used by any predefined KRONOS compatible export. Thus, if you were using for example a Kronos 3D export than there is a need to move the content from the ‘Remark’ column to the ‘External name’ column.  This can be done in two ways:

1. Manually edit the ‘External Name’ field for the points that are exported
2. Use the provided conversion batch file. This is a script that checks for any content in the ‘Remark’ field and if this does not contain more than 1 word it is assumed to be a KRONOS External name. It then simply copies the ‘Remark’ field content to the ‘External name’ field and then empty the ‘Remark field’. The Script can only be used once the DB is converted by DW to v2.15. Once converted follow the next steps:
   1. Close Delta Watch
   2. Copy the provided batch file to the same folder as the DB found in ‘Topcon Delta Watch/Database’
   3. Execute the batch file called: ‘DBScript - 2.11.x_copy_entries_from_comment_to_external_name_v2.bat’
   4. When done, restart Delta Watch
   5. Check in the Point and Limit management table of each project if the conversion was performed correctly
   6. Delete the batch script to prevent running it again!
   7. Continue setting up your export jobs