SatView

SatView is a real-time interactive data logging and display application for use with Satlantic radiometers. SatView makes it easy to connect to your Satlantic instruments and view time series, spectral plots, and depth profiles while capturing data for subsequent conversion and post-processing.

SatView Features

SatView is a real-time interactive data logging and display application for use with Satlantic radiometers. SatView makes it easy to connect to your Satlantic instruments and view time series, spectral plots, and depth profiles while capturing data for subsequent conversion and post-processing.

SatView features include:

  • Easy set up and configuration management
  • Serial communications direct to instruments
  • Real-time graphical display of incoming data
  • Ancillary sensor integration
  • Custom log file headers
  • Surface pressure tare
  • Support for profiling, in-situ and towing deployments

SatView 2.9.5

April 11, 2014

SatView 2.9 provides Windows 7 compatibility, improved PAR sensor support, wavelength range settings for spectral views, additional cast card fields for post-processing, support for up to 96 serial ports, GPS data validation and many more. Please refer to the release notes for a detailed list of recent improvements.

File SatView-2.9.5-b7-x86.exe for Microsoft Windows

Latest Update: April 11, 2014

New features/fixes for version 2.9.5

  • [M20141804-1] - Add support for BETA_IRED backscatter sensor on BB2FL
  • [2006-132-204] - A frame counter error prevents validation using checksum sensor
  • [2006-132-203] - Increase the supported comm port number upper limit from 16 to 96
  • [2006-132-197] - Connect All button opens all available serial ports
  • [2006-132-196] - Make the logging of appended frame time-stamps more robust
  • [2006-132-194] - Add GPS frame validation using the supplied NMEA checksum field

New features/fixes for version 2.9.4

  • [2006-132-192] - Support the AU data type for unsigned long sensor values

New features/fixes for version 2.9.3

  • [2006-132-182] - Make compatible with Windows 7
  • [2006-132-178] - Support displaying multiple PAR sensors in Ancillary View
  • [2006-132-176] - Add Fit Type POW10 to support Log PAR sensor
  • [2006-132-171] - Display data for PAR Sensor with OPTIC2 Fit Type
  • [2006-132-168] - Add SATNXC as a Profiler to the SatView .ini file
  • [2006-132-175] - Package Ancillary View must not derive fields for T and COND sensor with NONE Fit Type 
  • [2006-132-181] - Package Ancillary View pressure tare button disappears if package properties values are adjusted.
  • [2006-132-187] - Water Temperature sensor with COUNT Fit Type prevents detection.

New features/fixes for version 2.9.2

  • [2006-132-126] - Replace the Win32 Help file with an HTML Help file to support Vista 
  • [2006-132-136] - Add new fields to cast card to support Prosoft
  • [2006-132-150] - Add Wavelength Range settings for a Spectral View
  • [2006-132-151] - Add Cruise Report Document field to cast card
  • [2006-132-156] - Logging Inactive Warning Time to have minimum limit of 60 sec
  • [2006-132-157] - Package Ancillary NO3 value not plotted in Package Time Series View
  • [2006-132-108] - SatView can not display com ports higher then COM9
  • [2006-132-125] - Directory browse buttons don't work when directory is "C:\"
  • [2006-132-132] - Install script needs to be improved to support Windows Vista
  • [2006-132-134] - Non "SAT" frame prevents synchronization of  "SAT" frames
  • [2006-132-155] - Read-only CAL files in SIP file causes: "Access denied" error.
  • [2006-132-158] - GPS and MET Instrument Icons in panel do not display Frame Sync box
  • [2006-132-159] - Comm Port Wait Timeout default value is not long enough.
  • [2006-132-164] - Communication Resource Buffer Size value 32768 not restored

New features/fixes for version 2.9.1

  • [2006-132-119] - Add AFFILIATION and INVESTIGATOR Header Records

New features/fixes for version 2.8.3

  • [2006-132-87] - Delimiter length in TDF file can only be '1'
  • [2006-132-90] - Add pressure plot to Time Series View
  • [2006-132-91] - Lat/long format should be dd mm.mmm(m)
  • [2006-132-98] - Option to have fixed limit on a Time Series X (time) axis
  • [2006-132-101] - Spectral View needs to merge plots from telemetry frame sensor
  • [2006-132-113] - Validation of CheckSum for a Variable Length ASCII Frame does not work.
  • [2006-132-115] - Support Sensors with FitType THERM1 and Field Length of 0

New features/fixes for version 2.8.2

  • A conductivity sensor that does not require calibration can now be detected for salinity calculation.
  • The baud rate of 230400 is now supported.
  • Fixed restoring the instrument Immersion flag from a saved session.

New features for version 2.8.1

  • A STOR-X instrument is now automatically recognized as a Profiler instrument.

New features/fixes for version 2.8

  • An Instrument Package now provides the Time Series View.
  • Added support for the SATFLC instrument and updated the Instrument Package Ancillary View to display its CDOM sensor values.
  • Instrument Package Ancillary View now displays the Nitrate Concentration [NO3-] values for an ISUS Instrument.
  • When Log Options are set to enable Automatic Logging the starting and stopping of logging also controls the plotting of the selected data/sensor fields in both the Depth Profile and Time Series Views.
  • Optical View non-saturated sensor value text colour is now green instead of red.
  • Fixed bug that caused program to crash when an Instrument Frame contains either a sensor of type BD or BF.
  • Fixed bug that prevented Instrument Package Ancillary View Attenuation Coefficient values from being updated when multiple Instrument Packages are in use.
  • Fixed the Instrument Package View labels used for data fields derived from the BETA_RED sensor so that they contain the correct wavelength value.
  • Fixed the calculation of PAR(Z) and PAR(0+) values.
  • Fixed Instrument Frame type initialization to include a flag to indicate if an Instrument Frame is either "Dark" or "Light" so that PAR is not calculated for "Dark" frame types.
  • Fixed the frames selected for the calculation of the attenuation coefficient (K) to be the "Light" frame type.

New fixes for version 2.7.1

  • Fixed bug that caused the GPS Latitude and Longitude to not be used in the header of a Telemetry Log when this option is enabled in the Log Options dialog and when multiple Instrument Packages are in use.

New features/fixes for version 2.7

  • The Instrument Package Ancillary View can now display the attenuation coefficient(K) for Ed, Lu and Eu (approx. wavelength 490) when the required optical sensor for each is present. K is calculated over approx. 2m using linear regression.
  • Instrument Package Ancillary View dialog is now created even when the use of a default salinity value is required to calculate backscattering coefficients and it is not enabled.
  • The number of "Hardware framing error" and "Break error" session log messages output when the baud rate is incorrect is now limited to five for each time that a communication resource is selected to read from it.
  • The Start/Stop Logging button now also starts/finishes plotting for an Instrument Package Depth Profile View when one exists and it has been configured.
  • The Cast string used for AutoCast now requires two letters (AA - AZ, ..., ZA - ZZ) to increase the number of possible autocast log files.
  • A Spectral View display can now be resized.
  • A Spectral View's Absolute graph can be used to plot raw counts.
  • A Spectral View's graph background and axis colours can now be specified using the Spectral View Options dialog.
  • A Spectral View's Absolute and Logarithmic Y-Axis automatically expands its range to include values outside of the configured range.
  • An Optical View's Scroll Bar position is now stored to and restored from a session so that Optical View wavelengths initialy displayed when the session was saved are the same wavelengths that are visible when the session is opened.
  • An Instrument Package is now prevented from reading from a communication resource that another Instrument Package is already reading from.
  • Fixed bug that left a communication resource connected after an Insrument Package was selected to read from another communication resource.
  • Fixed bug that prevented Resource Control Panels that were open when a session was saved from being re-opened when the session is opened.
  • Fixed bug so that communication resource settings such as "Global Sync" and "Wait Timeout" can now be restored when a session is opened.
  • Fixed bug that caused dialog warning the user about telemetry not being logged from one or more instruments after the log inactivity timeout expired to be displayed when it should not have been.
  • Fixed bug so that an Instrument Package's Spectral View now displays each instrument's wavelength spectrum as a seperate plot instead of being merged into one wavelength spectrum.
  • Fixed bug that caused poor performance when Spectral Views are displayed for sensors that are defined as variable length fields.
  • Fixed the calculation of PAR values for the Ancillary and Depth Profile Views so that the values are in uMol/m^2/s.

New features for version 2.6.1

  • The BETA_BLUE and BETA_RED sensors can now be detected regardless of the wavelength speciefied for each in the TDF file.
  • Fixed bug in Package Ancillary View so that all values derived from the BETA_BLUE and BETA_RED sensors are now only updated when a telemetry frame from the BB2F instrument is received.
  • Fixed bug that prevented saved session file from opening when the session is using a virtual instrument package.
  • The Instrument Ancillary View Dialog when first opened now displays the Sensor page instead of the Data page.

New features for version 2.6

  • An Instrument Package that contains an instrument with a sensor for depth enables the creation of the Instrument Package Depth Profile View.
  • A TDF instrument file can now have sensors with the FIT-TYPE field set to NONE.

New fixes for version 2.5.1

  • Instrument Optical and Spectral Views displayed when a session is saved are now redisplayed when the session is opened.
  • A serial port that occurs in a non-consecutive list of serial ports after a non existant serial port can now have its parameters configured before an instrument is attached to it.
  • The Instrument Properties dialog for the Weather Station and GPS Data instruments can now be displayed without causing the program to crash.

New features for version 2.5:

  • Instrument Packages can now be added using the Add New Instrument Package or Instrument dialog that is displayed when either the Add Instrument tool bar button or Setup menu item is selected.

New features for version 2.4:

  • Instrument Packages now supported. An Instrument Package file (.sip) can be dropped onto the Instrument Package Control panel to load all the Instruments that it contains.
  • The automatic event: "Auto Read From" is now located in an Instrument Package's Properties Dialog.
  • An Instrument Package includes a file "Properties.txt" that is used to specify properties such as the Instrument Package's name and baud rate. If the baud rate is not specified the default value is 19200.
  • The baud rate is to configure the serial port that an Instrument Package is attached to.
  • An Instrument Package provides a pop-up menu from which its "View List", "Read From" and "Properties" Dialogs can be displayed. 
  • Instrument Packages have an Ancillary View that displays "Data" values obtained from all its Instruments. Instrument Ancillary View "Data" values removed except for Tilt, PAR(Z) and PAR(0+).
  • The Pressure Tare value is now obtained from an Instrument Package's Ancillary View.
  • An Instrument Package's Ancillary PAR(Z) and PAR(0+) values are based on a merger of all the relevant optical sensors from all of its Instruments.
  • Instrument Packages have Spectral Views when its Instruments contain optical sensors. Each Spectral View is a merged view of all the optical sensors of the same type for all its Instruments.
  • A "View List" Dialog now remains visible when a selected View is opened.
  • Instrument Telemetry Error Checking is now always enabled for both the Frame Counter and Check Sum sensors. The warning messages for reporting that either of these sensors was not found now output to session log.
  • Instrument can be added either to a new Instrument Package or to an existing Instrument Package in the Instrument Package Panel.

New features for version 2.3:

  • Improved instrument file handling.
  • Automated data collection can now be performed with task scheduling software.
  • Support for some non-Satlantic instruments
  • Time tag option removed from Logging Options dialog box.
  • Time tag information is now always appended to each logged telemetry frame (required for ProSoft 7.x processing).
  • Warning message displayed if one or more communication resources have not read any telemetry frames 10 seconds after logging was started.
  • HyperSpectral Profiler Ancilliary Dialog velocity values now calculated based on actual frame rate.
  • Single Optical and Spectral view for each type of optical sensor from multiple heads defined in the same calibration file.
  • Log Options Dialog now has an Inactive Warning Time option to allow setting the amount of time to wait until the logging inactive warning message is possibly displayed.
  • Default Frame Rate for telemetry is now 6.0 Hz.
  • An Instrument's Type set automatically to its default value.
  • An Instrument's Immersed flag set automatically to its default value.
  • Logging Mode option removed from Log Options dialog.
  • A communications resource automatically sets its baud rate when it is attached to an instrument if that instrument has a defined baud rate.
  • All existing communication resources are automatically detected and added to the communications resource list when a new session is started.
  • PAR(Z) and PAR(0+) values are displayed in the Ancillary View Dialog for instruments with the required sensors.
  • Light Saturation value is displayed in the Ancillary View Dialog of a Profiler instrument if the instrument containing the PAR(0+) sensors is defined to be a Reference instrument.
  • Fixed bug in the display of values of the data type binary signed.

We appreciate feedback. Please send any bug reports, comments, or suggestions to:

Satlantic Inc.
Richmond Terminal, Pier 9
3481 North Marginal Road
Halifax, Nova Scotia, Canada
B3K 5X8

Tel: (902) 492-4780
Fax: (902) 492-4781
Email: support@satlantic.com

Product Manual

SatView Manual

Thursday, October 2, 2008
PDF icon SatView-Manual.pdf

What GPS unit is compatible with SatView?

The requirements of a GPS to enable data collection with Satlantic's SatView software are: 

1. NMEA 0183 Output 
2. Serial connection 

The SAS GPS option includes a prewired Garmin model GPS 17xHVS. 
This model is designed for marine use, and connects to serial port on your computer. It can be mounted to a pole for the duration of the cruise. 

A suitable hand held model, is the GPS 72H from Garmin and has both the NEMA output and a serial connection. A optional serial cable is required, and also a power cable, if running from an external power source is desired.

What are SIP files?

Files that are delivered with Satlantic and third party equipment to describe the sensors data output and calibration coefficients come in two types. Calibration files or *.cal files and telemetry definition format files or *.tdf files. In some cases, systems are created that network many sensors together and their combined data is provided in one serial output.

The simplest example is a HOCR sensor that generates both light and dark frames. A more complex example is a HPROII profiling system that may contain as many as 5 sensors and 7 individual calibration and tdf files. These files must be used to both collect and process the data.

This can become quite confusing to keep track of all these files so Satlantic developed SIP files. All CAL and TDF files required for a system are zipped using winzip and the extension changed from *.ZIP to *.SIP. The file name includes the system description (usually the network master serial number) and the creation date. This SIP file can then be used in place of individual files to collect and process data.