The SeaSave data visualization and processing software relies on a few factors in order to establish communications with your CTD and to process your data correctly. Some issues prevent good data from being displayed, while others will prevent communication entirely. Here are a few of the most commonly encountered issues we’ve seen.
First, since SeaSave uses serial connections, establishing the correct COM port and Baud Rate for your instrument is crucial. Choosing the wrong COM port will give you no communication at all, whereas choosing the wrong baud rate can give you either no response or a set of ‘garbage’ characters as the software attempts to interpret the data. One can think of this as speaking different languages- the baud rate establishes that both your CTD system and your computer are talking in the same language, so matching them is essential. There are defaults listed for most systems, but you can also check your User Manual for options. To identify your correct COM port, use Window’s Device Manager app, which is built in to all Windows computers, to identify the COM port that is added to the list of available Ports when you plug it in to the computer.
Another common real time issue is the Scan Length Error. Our software uses a file that contains your instrument’s calibration and hardware setup information called the .XMLCON. This file is used by the software to determine how many hexadecimal bits per line it should expect to convert. For more information refer to the FAQ “What is a configuration (.con or .xmlcon) file and how is it used?”. However, the CTD is not using the xmlcon to determine what voltage channels or serial data is enabled, those are all controlled via settings in the firmware that you can control. If the number of enabled channels on your CTD doesn’t match the xmlcon, the ‘scan length’, that is the number of bits per line, won’t match either. This causes the error, and prevents any data from being converted. To fix it, compare your xmlcon file to your CTD setup with diagnostic commands like DS or GETHD (refer to your user manual) and ensure that everything on your CTD that is active is represented in the xmlcon.
Another common source of confusion can be how the software maintains the ranges and outputs of displays and plots. You may need to double check if the ranges and variables you’ve chosen match those of your data. One simple way to do so is to look at the converted CNV data’s header, where it lists the range for each column of data under the lines marked with “#span”. If your CTD is connected but your plot doesn’t seem to be updating, this is a great place to start.