GunLink Software Release Notes 4.

7 patches

Version History
4.7.8- 17/10/2022
4.7.7- 28/03/2022
4.7.6- 25/10/2021
4.7.5- 22/10/2021
4.7.4- 28/07/2021
4.7.3- 21/04/2021
4.7.2- 18/02/2021
4.7.1- 5/12/2020

Patch notes
Patches are cumulative - that is you only ever need the latest one installed, you do not need to install intermediate versions.

Patches are specific to the GunLink minor release number. The release number format is <major>.<minor>.<patch>. They will only
install on that release. IE a 4.2.y patch will apply to 4.2.* systems.

But if you ever need to unroll a patch then this will take you back to the original major release of the most recent installation performed
on the machine.

If you wanted to go back to the previous version of a patch you will need to re-install that after unrolling.

Patches are stored in /opt/gunlink/patches/patchname. Within each patch directory you can find a copy of the latest patch file that you
can use to unroll it (or any previous version) and a copy of the release notes. These directories do not get deleted even if you unroll a
patch.

Installation
The patch file name will be something like abc.bin.gz for example. In these notes replace 'xxxx' with in this case 'abc'. The directory
created will be /opt/gunlink/patches/abc replace 'yyyy' with this.

Copy the distribution file which will have a .bin.gz extension to a USB memory stick and insert that in the host machine, a
desktop icon should appear.
open a terminal and become root using 'su -', you must use this command not just 'su'.
Copy the file to root's home directory. The USB stick will be mounted as '/media/disk/' or possibly '/media/USBsomething' look
at the desktop icon to see what the name is. 'cp /media/disk/xxxx.bin.gz ./'
Check the file checksum for corruption 'sha256sum xxxx.bin.gz' the correct value should have been given to you when you got
the file.
Unzip the file 'gunzip xxxx.bin.gz' this will unzip the file and remove the '.gz' extension.
Check the checksum again using the other value you were given 'sha256sum xxxx.bin'
Ensure the file is executable 'chmod u+x xxxx.bin'
Install it './xxxx.bin', read the release notes and reboot as required. If you have a previous patch for this release installed you
will be prompted to overwrite it.
Use updateAllFirmware to update any new firmware (see the operator's manual).
Repeat installation on spare host machine and any remote display machine.

Unrolling
To unroll a patch and restore the system to the base install:

open a terminal and become root using 'su -', you must use this command not just 'su'.
Change to the patch directory 'cd /opt/gunlink/patches/yyyy'
Execute the patch file with the '--unroll' option. './xxxx.bin --unroll'
If you need to revert to a previous patch version you need to re-install it now.
Reboot the machine and all GCUs or TEMS.
Unroll the same patch on the spare machine and any remote display machines.
Remember this cannot roll back any database or firmware updates and they may not be compatible with the older
code.
Generally patches will not contain database changes (that would imply a major change) but may include new firmware.

Determining patch version (if any)

From release 4.0.0, the patch version will be shown on the title bar of the Display program. You can also look in the 'documents' section
of GunLink Web, if no patch release notes are shown no patches are installed.

Release 4.7.8 patch - 17th October 2022

 Bugs Fixed
FS#3001Gun Fire Module voltages all zeroThe GFM voltages were displayed as zero on the Hardware Tab and
gunlinkInfo

Release 4.7.7 patch - 28th March 2022

Bugs Fixed
FS#2921 ETB voltage not correctly maintained over host program restarts and not reliable for enable/disable Fixed a
bug where the Teledyne Bolt eSource (Bolt_eSc) sensor power defaulted to be ON but the Display program showed the
state to be unknown "?". Now Display does NOT show the "?" for unknown state and that the power can be reliably
disabled and enabled.
Note: Status is not maintained correctly after bus resets. This will be fixed in GunLink 4.8.

FS#2920 SEGD Pressures expected 14 found 20 Fixed a bug where ipt pressures were being recorded in SEGD even if
the ipt was not present

FS#2916 SOL and EOL Pressure and Volume information missing from the Gun log Fixed a bug where the pressure and
volume information was missing from the logs at SOL and EOL

FS#2914 Line start delayed by 1 shot from what might be expected A vessel reported that for the first shot after a 'Begin
Line' (BL) GCS90 message, the SEGD file was sometimes stored in the 'Offline' directory. Fixed an internal race
condition which occurred if the NAV system sent BL/SS/SP messages in very quick succession

FS#2910 GunLink 2500 - ERROR reading from port /dev/ttyS1,S2,S5 errors Fixed a bug where a single corrupt
message was causing many error messages of the format 'ERROR reading from port /dev/ttyS1'

FS#2900 Logs PTs showing as killed for the whole line when they are not bad Fixed a bug where dandp logs showed
complete lines with all phones marked as OK, Killed, but there was data for every shotpoint for that PT.

FS#2899 Sercel eSc gun type causing autofires Fixed a bug where a vessel using Teledyne Bolt eSource (eSc) guns
was causing continuous autofires.

FS#2861 Internal phones show no history in GL_Web when tracked through the GFSM Fixed a bug where, in Web, if
you followed the trail for an integral GFSM phone via the config viewer then the system stated that it had no location
history (even though it was on the active array on an active GFSM)

FS#2546 Bubble test missing shots - vessel reported Tckt#4202916 Fixed a bug where while performing a bubble test
on 2 guns on port side in the same cluster, a vessel reported that not all the warm-up shots were fired.

Maintenance
FS#2938 Display Depth and Pressure tab - SEGD index column and headers Updated the depth and pressure tab with
a new column that displays the SEGD index

FS#2923 Make the Display/Hydrophone Channel trim value symmetric around 1 Adjusted the channel trim range
(formerly between 0.9 and 1.5) to be based on the default/centre of 1. This is now symmetric around 1 (so 0.5 to 1.5) to
allow more symmetric calibration adjustments.

FS#2913 DEM over-temperature warning values update The DEM temperature warning values have been updated to
better reflect the actual temperature capability of the DEM. GunLink will now display Amber at 60degC, Red at 70DegC

FS#2904 Instrument test specs for GunLink 2000 Updated the Instrument test specs for GunLink 2000 so that the driven
test matches the specification for fundamental sine

FS#2856 Updated calibrated hydrophone temperature profiling Updated GunLink to include hydrophone temperature
profiling for the newer Seamap calibrated hydrophones sensors. GunLink uses the appropriate capacitor and sensitivity
coefficients based on the hydrophone type. The model of sensor is stored in the hydrophone and read automatically by
GunLink, there is no need for the operator to configure the hydrophone type. This update includes a minor database
upgrade.
NOTE: Old type could be PVDF or LZT as HRVU not updated so the best guess cut-off used is 9.5nF and below
is LZT above is PVDF

Clarifications
FS#2902 Display/line stats tab/context help needs to be more descriptive about line selection Updated the help
comments

Firmware updates
FireModule2p0p1.elf FireModule version 2.0.1 New GFM firmware. Supports the new Air Valve Module which will be
available for use in GunLink version 4.8.

Release 4.7.6 patch - 25th October 2021

Enhancements and New Features

 FS#2829 New Display trace layout options Added two new layout options.
1) Place the Hydrophone Traces Below the Sensor Traces. This displays the hydrophone traces below the sensor traces
(limited to 8 strings)

2) Place the Hydrophone Traces Above the Sensor Traces. This displays the sensor traces below the Hydrophone
traces (limited to 8 strings)

Bugs Fixed
FS#2855 Serial Devices tab no longer able to "commit" changes unless a new display added A breaking change in the
previous patch caused the thresholds entry to fail validation and prevent any changes from being accepted in the RPD2
configuration.

FS#2854 GL2500: Reporting serial comms errors too often Fixed a bug where a serial control comms error for a GL2500
bus was being reported every 10ms. This caused a high volume of error messages which caused the node to lock up.

FS#2850 updateAllFirmware not reporting firmware status of slave TCU From a report of a vessel with dual TCUs the
updateAllFirmware output did not report the second TCU. GunLink will now report the firmware and update it if required

FS#2848 Unable to update General Info for PTs in GunLink Web Fixed a bug where the user could not update general
information in GunLink Web for an individual Pressure Transducer

FS#2846 Bubble Test doesn't commit edits to atmospheric pressure on focus loss When a value was entered in the
Bubble Test atmospheric pressure entry field, if focus was lost (for example clicking on Start) then the value entered was
not committed before the test started, leading to misleading results. This has been fixed.

FS#2836 Multipoint reset at BL does not work Fixed a bug where the sequence number was not being reset back to 1 at
BL.

FS#2835 In multipoint we still need access to the "Set Firing Sources" selection Fixed a bug where Multipoint would give
an error if some guns were not included in a source. GunLink now checks all guns and if any are not assigned a source,
 it will give them the default 1

FS#2834 Bubble Test GUI shows "External" checkbox when it shouldn't Fixed a bug where ‘External mode’ checkbox
was sometimes incorrectly visible on the Bubble Test GUI

FS#2832 Serial numbers in SEGD headers (Config vs EEPROM) If the hydrophone serial number stored in the config
did not match the serial number stored on the hydrophone, GunLink incorrectly used the serial number from the config.
What now happens is that the data stored on the hydrophone is used in the SEGD, regardless of if it matches the data in
the config. If the data cannot be read from the hydrophone, then the data from the config is used.

FS#2827 Gl2500 modem control messages shown in error Gl2500 system errors (to be decoded by the host) were
being logged as normal messages. These un-readable messages have been removed from the logs.

FS#2825 Incorrect “SOL Phones not enabled for Far Field” warnings Fixed a bug where the warning: “SOL Phones not
enabled for Far Field” were logged incorrectly when using Far field

FS#2808 PT index in Display is not sensible Fixed a bug where an incorrect PT index value was displayed in the PT
section of the depth/pressure tab

FS#2807 PT depth offsets not able to be changed Fixed a bug where when changing the PTs depth offsets and saving
the configuration, the values reverted to the original values.

FS#2798 GunLink web allowed editing Seamap integrated phone calibration details When viewing the Seamap Integral
phone calibration details in GunLink web all 5 calibration points are displayed and all the options to change are now
greyed out (the same as for a cabled phone).

FS#2793 Fresh install and Display doesn't start Fixed a bug here Display would sometimes not start when using a
GunLink 2000 config

FS#2791 DTs and PTs that are non-integral cannot attach to a GPM/GFSM/ACV Fixed a bug in Configure where non-
integral DTs and PTs could be attached to a GPM/GFSM/ACV . Only integral or remote transducers should be
connected.

FS#2790 Zero depth gun display issue Fixed an issue where only half a gun was visible on Display when the gun depth
was zero

FS#2788 A GL4K system with a mixture of integral and cabled PTs is not able to set the PTs as expected We now have
GFSMs that have the option for a cabled PT as well as an integral PT. This cabled PT is now able to be set as gun
reading, but defaults to be a cluster reading.

FS#2787 Display Override on shallow/low pressure tick boxes inverted Fixed a bug where if you had a minimum firing
depth and pressure set then the system was not overriding the settings. The selection was doing the opposite of what
was intended.

FS#2786 Configure does not always update the layout when removing devices Fixed a bug where when adding and
removing guns on clusters the views did not always update and require the operator to move off the layout tab and back.

FS#2785 Unable to un-zoom single trace plot Fix a bug where sometimes it was not possible to un-zoom a single trace
frame.

FS#2713 Multipoint Builder does not fully load the whole ini file on first try Fixed a bug where loading a new multipoint ini
file into the Multipoint Builder it does not appear to load the full file.

FS#2711 Inconsistent phone ordering with dual phones Hydrophones are now ordered in a cluster on hardware channel
instead of the order added

FS#2695 Triple Gun Clusters stop Display from showing tabs Fixed a bug where a GL2000 config with 3 guns on a
cluster would cause some of the tabs on Display to disappear

FS#2694 Adding triple gun to a 2K cluster does not auto name Fixed a bug in In Configure, where for a new config when
adding a third gun to a cluster (for a triple gun cluster) the third gun did not get auto assigned a name (although the first
two did).

FS#2543 Configure not handling "corrupt configs" without having problems Fixed a bug which was caused when using a
historic config that had devices that appeared to have been replaced since last use. For example, if a GFSM has
previously had the PTs removed or replaced and the database had been maintained to reflect this, then the historic
config still had references to the old devices.

FS#2473 Gun auto-naming includes Ghost guns in the numbering Fixed a bug where when changing configs with ghost
guns (ghost at position 1) then the first real gun was named as Gun 2. New configure option the ghost guns should not
influence the real gun numbers

Maintenance
FS#2830 Improved settings/geometry checks GunLink now checks if all string lateral offsets are set to zero

FS#2821 Add the test conditions of the iTest to the pdf report Added test conditions to the pdf file

FS#2816 Add GUN depths and pressures to isct.asc files Previously, the isct.asc files only had the depth and pressure
transducer values. Gun depths and pressures as well as the transducer depths have been added.

FS#2806 Incorrect warnings for low main manifold pressure Fixed an error that would cause warnings if non Seamap
Atmospheric or main manifold pressure transducers were used, due to an incorrect internal offset.

FS#2805 add raw depth/pressure transducer logging to envLog and add manifold pressure to gun depth logging Add the
raw DT/PT transducer readings to envLog and add the manifold sensor value to the gun pressures

FS#2804 Add pressure to Low Main Manifold Pressure warning message When the Low Main Manifold Pressure
warning message appears, it now also displays the main manifold pressure
 FS#2803 Clarify the start of line messages for phones enabled/killed/not in far field Now separate list log entry for killed
and far-field Hydrophones

FS#2792 Increase the max separation for gun arrays on the Display/positions tab The max separation has been
changed from 300m to 1000m.

FS#2784 In bus monitor display the temps as text as well as just a bar graph In bus monitor when the temps are chosen
in the cable view, only a visual bar graph was displayed. A text display of the temperature on the bar graph has been
added.

FS#2778 Water ingress possibility message added The system logs a message water ingress possibility message. This
may be changed in a future patch release to a higher level of warning that will produce a pop-up window which will alert
the operator and expect them to respond to it. With this in mind, we’ve added a parameter to Host System Preferences
called “Water_Ingress”. If ticked it will suppress the pop-up on the GFSM internal water alarms, otherwise it will report
possible ingress every minute. This option has been added in Display to disable this warning, to disable readings that
are faulty or too sensitive.

FS#2767 Add backup of /opt/gunlink/conf/system.conf to the v4SysDetails script Additional file added to the backup
script

FS#2700 In Configure GFSM/GSM inventory show which is IPT and channel numbers Updated the GFSM display in
Configure to show what channel the hydrophones and transducers are on. For example:

Release 4.7.5 patch - 22th October 2021

Bugs Fixed
FS#2874 single internal phone on channel 2 of rear entry string caused incorrect device/slot allocation Fixed a bug
where incorrect hydrophone allocation caused an invalid config.ini state to be reported in Host Status

FS#2872 Dummy cluster on 2k5/4k bus issue Fixed a bug where using an dummy cluster sometimes caused a GPM
bus to fail to initialise

Release 4.7.4 patch - 28th July 2021

Bugs Fixed
FS#2472 Dual phone GSM in 2K5 config does not show phone traces when only internal phones in use Fixed a bug
where hydrophone data was not recorded when a single integral phone was used on a dual hydrophone GL2500 GSM

FS#2838 GL2500: GL2500: Error messages cluttering up the logs Changed message 'dry end not responding' from
ERROR to INFO

Release 4.7.3 patch - 21st April 2021

User Manual Updates

20-00-0142 GunLink header Format (Revision RH)

10-94-2162 Pressure/Fill/Vacuum Test Kit Operation Manual (Revision RD)>

Enhancements and New Features

FS#2758 Allow SegD and Nav to the use different version of GunLink1 header Make the GunLink revB and revC
headers distinct so that Nav could use revB and segd could use revC.. for example

FS#2732 Update envLog to do all nodes instead of just one envLog can now automatically loop through all nodes.
Previously you could specify just one.
 FS#2531 Sum of Hydrophones update The system will now allow up-to 6 plots but they are limited to the first 6 Firing
Sources, and are no longer shot number incremented

Bugs Fixed
FS#2780 Nodes comms drop out and guns don't fire when trying to enable Gun 14(cluster 7) Fixed a bug where
‘solenoid peak current’ logging messages were being sent from the Node to the Host too often and causing the comms
to drop out. These messages were added for development purposes only so have been removed

FS#2775 Web/Search devices does not show correct details for solenoids When in web, go to the search devices tab
and search for any device and use both in use and not in use, solenoids now show correctly.

FS#2772 Zero or Force Zero disabled in DandP Permissions could prevent GunLink from running Fixed a bug that could
cause GunLink not to run

FS#2763 PTs being used for string pressures when the valve is shut Fixed a bug where strings pressures were being
calculated using pressure transducers values on closed valves.

FS#2761 Display/Hardware Tab not showing phone calibration details Fixed a bug where the hardware tab was not
displaying the correct phone calibration details for Seamap calibrated phones

FS#2749 Bus monitor cable view display bug Fixed a bug where Bus monitor was not displaying "All Errors", "Overall
Error Rate" and temperatures correctly

Maintenance
FS#2767 Add backup of /opt/gunlink/conf/system.conf to the v4SysDetails script Additional file added to the backup
script

FS#2750 Disable "Force Zero" option on the GunSrings2 tab if "Display options" DandP tab says to not allow Force In
the GunStrings2 tab the “Force Zero” option is disabled if the Display options does not allow the use of "Force Zero".

Release 4.7.2 patch - 18th February 2021

Enhancements and New Features

FS#2745 Soft Start: New option to use the smallest initial volume A new option has been added to Soft Start: Use
Smallest Initial Volume, in the Sequence section.
The default is False, which is the original behaviour: Soft Start will choose the largest of the smallest volumes of each
source in Soft Start. This ensures that in External shooting, Soft Start will always start when requested no matter which
source navigation selects to start the sequence with.
The new option of True is the new behaviour. This will start the sequence from the smallest available source allowed.
However, there is a caveat: in External shooting, if navigation chooses to fire the first source with a slightly higher
smallest source, Soft Start *will not start* as no guns will fire. Operators should be made aware of this behaviour.

Bugs Fixed
FS#2751 Gunstrings2 showing wrong enabled status for gun with bad substatus Fixed a bug In the Gunstrings2 tab,
where a gun showed an enabled state when it had just fired and had a bad substatus such as "bad timing"

FS#2747 Start Line when already on Production line not ending line correctly Fixed a bug if the user meant to end the
production line, but selected start line by mistake, the end of line pdf files weren’t created

FS#2746 Web CM management does not allow you to exit without applying changes Fixed a bug where if a user made a
"swap" using the CM management tool in Web (to swap DTs/PTs/Phones on a GFSM or GSM) but didn’t want to save
the changes, it asked if you really wanted to leave and discard the changes but when you clicked OK it didn’t let you out

FS#2743 Soft start broken for partial array Fixed a bug where soft start can sometimes end up firing the whole array if
the full source is removed from soft start. Have a single standard string enabled for soft start worked as expected

FS#2737 Display line stats graph for far field does not have a valid Y-axis Fixed the Y-axis on the far field graph in
Display/Line Stats

FS#2716 Gunlink1 header does not record Version B in segd files unless Nav header is set to Version B Fixed a bug
where if the segd header format is set to Gunlink1 version B but the Nav header is set to anything other than Gunlink1
version B then the segd file would have Gunlink1 version C header regardless of which header format was selected

FS#2540 String name in configure plan views not always to the left Fixed a bug where the string names/numbers were
fixed around the 0m inline position and were overwritten by the devices and so were not visible

Maintenance
FS#2744 The user can now manually disable/enable guns in Soft Start if max volume set If Soft Start is active, and if
Soft Start is configured to disable spares at termination, then "lenient" mode is activated, where the total volume
calculated for each source ignores spares, *even if they are enabled*. Furthermore, this check is only made on the
Gunstrings1, Gunstrings2, and Gun Parameters tab when enabling/disabling.
If Soft start is not active, or if Soft Start is not configured to disable spares at termination, or when editing source
memberships in the Gun Parameters tab or the Set Firing Sources tab, lenient mode is *disabled* and the system
makes its calculations as normal. (Adding and removing guns from actual firing sources during Soft Start is not
 recommended!)
The check is now more "lenient" but only in specific circumstances to minimise the chance of an operator error

FS#2742 Reduce debug trace in the logs With fast shooting and multipoint modes becoming more popular the amount
of trace output to the message monitor logs was excessive. Detailed developer type info & general progress info with no
real value have been removed

FS#2731 Add simulated node run hours and fan hours for 4k nodes Additional values to be simulated

FS#2721 Add TEM Run and Fan hours to envLog envLog has been updated to record these values

FS#2723 Add date and time to Display/Configure reported java errors Added the date and time to the java errors
reported in the Error tab to help locate other information from lzma logs etc

FS#2572 Gun Strings 2 - Temps clipped in "default" mode Updated the GunStrings2 tab to prevent the temperature
display being partially hidden

Known Issues
FS#2714 Simulation for large arrays can give errors due to processor having to simulate When running demo/simulation
on a virtual machine with arrays containing more than 6 strings the system has difficulty in simulating all the data as well
as plotting etc. This can show as missed shots in MultiPoint shooting

FS#2713 Multipoint Builder does not fully load the whole ini file on first try When first loading a new multipoint file into the
Multipoint Builder, the first time the file is loaded the first sequence is loaded, but if you scroll to sequence 2 then that
shows as blank. When loading the same file again all the sequences are loaded.

FS#2699 Configure does not update PT names and details when swapping GFSMs with differing numbers of PTs For
example: If you drag/drop new 2PT GFSMs onto 1PT GFSMs already on the config the details will not be updated
Workaround: Remove the existing GFSM/GSM from the cluster and then add the new one back to the cluster.
NOTE: Channels will have to be checked/reassigned manually

FS#2662 Soft start will not complete in certain modes if Max Volume is set When using soft start with Toggle Spares set
to NO and with a max volume set in HSP (of the volume not including spares), soft start may not complete

FS#2661 Discrepancy between Display and Soft start for ideal volume (final target) In some shooting modes the ideal
shot volume reported by Display is different to the one reported by Soft start (The correct reported volume is done by
Soft start)

FS#2659 adread - getBinSlot errors required a host restart to clear In eSeismic mode, if a getBinSlot – no empty bin
found error occurs it is necessary to restart host programs

FS#2651 Soft start in eSeismic causes no-fire/autofire on sensors (demo) When in demo mode, Soft start in eSeismic
mode can give no fire or autofire errors if the config contains spare guns in the array

FS#2585 Web Live Displays/Depth, Pressure Full shot history no longer work These graphing functions rely on obsolete
technology which is no longer supported. This will be addressed in a future release.

FS#2543 Configure not handling "corrupt configs" without having problems Sometimes a corrupt config file is difficult to
fix. Please contact GunLink support if this occurs.

FS#2296 Web plots can't cope with decreasing shotpoints It is common for shotpoint sequence numbers to advance
decreasing order for some shooting patterns. Unfortunately, GunLink Web plots cannot display these lines correctly after
they have been summarised. This will be addressed in a forthcoming patch.

FS#2478 Far-field: Adjusting string separations while online The Far-field function is set up in such a way that it
initialises at the start of shooting with a set of known parameters that are not expected to change. Adjusting string
separations while online may cause Far Field calculations to produce incorrect results. It is advised that shooting is
stopped, and the system put into OFFLINE if string separation distances need to change while using Far-field

Further details
Soft Start Soft Start guidelines concerning lone spares Please be aware that including a lone spare gun on a cluster
(that is, a cluster with only a single gun on it, that is designated as a spare) in the Soft Start set, will not toggle the spare
on and off as there is no complementary gun to toggle with. In this case, the spare gun will be included in Soft Start as
part of the target volume and will fire if enabled.
It is advisable that you check the target volume of Soft Start if you have single spare guns on clusters to ensure it does
not exceed the contract MMO specification.

Display Display will no longer start without the Host Programs running Previously it was possible to start Display without
the Host Programs running. Additional checks and validation performed by the Host Programs means it is now
necessary to start these before opening Display. This does not affect performing a Host Programs Restart while Display
is open.

Release 4.7.1 patch - 5th December 2020

Enhancements and New Features

FS#2683 Allow dumpHeader to output the raw bytes instead of decoded The dumpHeader script can now log as raw
bytes. Previously it was only decoded.

FS#2666 Allow the Nav controlled firing t0 command to be aimpoint via the HSP/TCU GPS time option Added the ability
to use aimpoint or t0 based on the same option in Host System Preferences. "Nav GPS time” represents that is used for
 the GS message in conventional GCS90 protocol.

FS#2595 Have Gunstrings2 tab able to set spare guns (from right click menu only) You can now set spare guns on the
Gunstrings2 tab

Bugs Fixed
FS#2740 Start of line and end of line details missing from logs Fixed a bug in the line report logs in /var/gunlink/printfiles/
for gunlogXX.pdf and seislogXX.pdf which were missing the SOL/EOL info. This also affected the Display's View Log tab
which was missing SOL info and had the EOL info tagged to the wrong line

FS#2724 Display's Clone settings not working as expected Fix a bug where clone phone multitrace settings were not
cloning to all plots

FS#2692 Host System Prefs does not save when setting farfield to enabled Fixed a bug where the system sometimes
didn’t allow you to set farfield to enabled

FS#2690 MultiPoint error when .ini file does not match array size Fixed an exception error which occurred when the .ini
file array size didn’t match

FS#2689 Clicking rightmost column in Source Sequence editor Fixed a bug where a stacktrace was occurring in the
Source Sequence editor

FS#2688 Depth Specs entry can't be OKed when there are many strings Fixed a bug where the window created to edit
the depth specs in Display is too large to actually see the commit/cancel buttons at the bottom

FS#2679 Display/Simulation tab shows 4% SPSU Voltage Variation when opened and not the actual correct value The
SPSU voltage variation displayed value has been fixed

FS#2677 Display Source Sequence tab resets its focus on a new shot Highlighting a sequence step in the Source
Sequence tab would result in it being cleared and all guns going grey when a shot occurred. This has been fixed.

FS#2669 Bubble test offset calculation is incorrect Fixed a bug where even though the Sensor fires at 50ms, the bubble
test shows sensor pickpoint = 0ms.

FS#2667 Positions tab does not load values if started while display is already open Fixed a bug where sometimes when
opening the Positions tab in Display, the speed of sound, vessel speed and layback were all zero

FS#2665 Revisting Gunstrings tab causes sending of multiple Average Sea Temperature messages Fixed an issue
where each time the Gunstrings tab was selected a new process started which put a Sea Temperature message in the
logs. This would have swamped the logs with these messages if not corrected.

FS#2657 Disable Firing Sources and Source Sequence tools when not needed Grey out the option in the dropdown
menu to select “Firing Sources and Source Sequence” when in shooting modes where these tools are not required

FS#2641 Swapping GSMs with hydrophones on different channels error Fixed a bug where some of the internal devices
would still be swapped even if there was an error which prevented the GSMs swap from being applied.

FS#2640 Web does not allow to attach a phone to channel 1 of a GSM GunLink now allows phones to be attached to
channel 1 and channel 2 of GSMs. This was only allowed on channel 1 previously.

FS#2638 Copy paste string does not carry over "transducer onboard" check box Fixed an issue in configure where string
devices (such as a PT) lost some configuration details following the copy and paste of a string

FS#2637 Adding a phone on a GSM with bulkhead phone as Ch2 also puts external phone as ch 2 Fixed a bug in
Configure where adding a second hydrophone (external) to a GSM would create a duplicate channel and put the
additional phone on the same as the existing one.

FS#2632 Adding 3DTs and 3PTs to a 2K config does not assign channels for PT3 Fixed a bug where adding a third PT
to act as a manifold and the channels were not auto assigned for the node. The node was set, but not the channels.

FS#2584 Line Stats table shows percent bad as infinite when obviously not Fixed a bug where the line stats table
showed percent bad incorrectly as infinite.

FS#2577 Gunlink1 header issues with phones for 2K config. Fixed an issue where the hydrophone serial numbers and
calibration details were not being included in the header.

Clarifications
FS#2698 Minimum screen resolution to fit on screen The minimum screen resolution needed to use GunLink is
1280x1024. Setting the screen to a smaller resolution will prevent the user being able to locate some buttons.

FS#2680 GunLink1 header - MULTIP block gun numbering The MULTIP blocks were designed to be used with the
Multipoint firing mode. When we first designed Multipoint, it was expected that all guns would be fired with each shot,
just with each gun having a personalised offset. This meant that when only selected guns were fired, the numbering
didn’t match the gun indexes. The MULTIP field now uses the gun index.

FS#2524 Add warning if no guns selected to fire when entering internal mode Each source in a firing sequence should
have at least one gun in it. If not, GunLink will warn the operator before the system attempts to start shooting. Note that
GunLink will not check that the guns are actually enabled - only that there are guns present in each source.

FS#2552 The GunLink1 Header Manual Revisions B and C differences The GunLink1 header revisions B and C are
identical except for the addition of an extra hydrophone sensitivity data block in revision C.

Maintenance
 FS#2610 If there is a large array the Gunstrings error bar charts do not fit There is a new display option on Gunstrings to
turn the error bar charts off.

FS#2609 Gunstrings tab needs to have the string Enable/Disable on one line The Sea temperature controls were not
visible when using large arrays. The sting enable/disable button has been made smaller to accommodate this.

Known Issues / Further details

FS#2714 Simulation for large arrays can give errors due to processor having to simulate When running demo/simulation
on a virtual machine with arrays containing more than 6 strings the system has difficulty in simulating all the data as well
as plotting etc. This can show as missed shots in MultiPoint shooting.

FS#2713 Multipoint Builder does not fully load the whole ini file on first try When first loading a new multipoint file into the
Multipoint Builder, the first time the file is loaded the first sequence is loaded, but if you scroll to sequence 2 then that
shows as blank. When loading the same file again all the sequences are loaded..

FS#2699 Configure does not update PT names and details when swapping GFSMs with differing numbers of PTs For
example: If you drag/drop new 2PT GFSMs onto 1PT GFSMs already on the config the details will not be updated
Workaround: Remove the existing GFSM/GSM from the cluster and then add the new one back to the cluster. NOTE:
Channels will have to be checked/reassigned manually.

FS#2716 Gunlink1 header version recorded in the segd files is set by the Nav header version setting The Gunlink1
version used in the segd header is incorrectly set from the Nav header setting, rather than the sedg setting in Host
System Preferences.

FS#2662 Soft start will not complete in certain modes if Max Volume is set When using soft start with Toggle Spares set
to NO and with a max volume set in HSP (of the volume not including spares), soft start may not complete

FS#2661 Discrepancy between Display and Soft start for ideal volume (final target) In some shooting modes the ideal
shot volume reported by Display is different to the one reported by Soft start (The correct reported volume is done by
Soft start)

FS#2659 adread - getBinSlot errors required a host restart to clear In eSeismic mode, if a getBinSlot – no empty bin
found error occurs it is necessary to restart host programs

FS#2651 Soft start in eSeismic causes no-fire/autofire on sensors (demo) When in demo mode, Soft start in eSeismic
mode can give no fire or autofire errors if the config contains spare guns in the array

FS#2585 Web Live Displays/Depth, Pressure Full shot history no longer work These graphing functions rely on obsolete
technology which is no longer supported. This will be addressed in a future release.

FS#2543 Configure not handling "corrupt configs" without having problems Sometimes a corrupt config file is difficult to
fix. Please contact GunLink support if this occurs.

FS#2296 Web plots can't cope with decreasing shotpoints It is common for shotpoint sequence numbers to advance
decreasing order for some shooting patterns. Unfortunately, GunLink Web plots cannot display these lines correctly after
they have been summarised. This will be addressed in a forthcoming patch.

FS#2478 Far-field: Adjusting string separations while online The Far-field function is set up in such a way that it
initialises at the start of shooting with a set of known parameters that are not expected to change. Adjusting string
separations while online may cause Far Field calculations to produce incorrect results. It is advised that shooting is
stopped and the system put into OFFLINE if string separation distances need to change while using Far-field

Further details
Soft Start Soft Start guidelines concerning lone spares Please be aware that including a lone spare gun on a cluster
(that is, a cluster with only a single gun on it, that is designated as a spare) in the Soft Start set, will not toggle the spare
on and off as there is no complementary gun to toggle with. In this case, the spare gun will be included in Soft Start as
part of the target volume and will fire if enabled. It is advisable that you check the target volume of Soft Start if you have
single spare guns on clusters to ensure it does not exceed the contract MMO specification.

Display Display will no longer start without the Host Programs running Previously it was possible to start Display without
the Host Programs running. Additional checks and validation performed by the Host Programs means it is now
necessary to start these before opening Display. This does not affect performing a Host Programs Restart while Display
is open.

Documentation
Web manual update10-94-7571Soft Start Technical Manual revC