SR3001 Trident JSATS
Autonomous Node Receiver Manual
Version 4.0

Functionality

The autonomous node receiver is designed to be a self-sufficient, data-logging unit anchored to the bottom of marine and freshwater environments. The major components of the receiver are shown in Figure 1-1.

The hydrophone receives the high frequency mechanical vibrations sent through the water by the JSATS transmitter (in the fish) and converts them to weak electrical voltages. These weak voltages are amplified and filtered by the preamplifier of the Control circuit (to reduce noise) and then sent to the DSP circuit for processing.
The DSP circuit converts the incoming filtered signals to digital numbers for use by the DSP in its detection and decoding algorithm. The detection algorithm looks for the existence of a tag and the decoding algorithm determines what specific tag code is present.
When a valid code is verified by the DSP it sends the code and the time of decode to the supervisory processor for storage on the SDHC (High capacity SD flash memory) card. The supervisory processor manages the storage of data on the SDHC card as well as communication with the external computer’s USB connection. The Power circuit supplies power for the many different voltage requirements of the system.
The receiver is optionally equipped with sensors for pressure, temperature, and tilt to obtain environmental information as well as the orientation of the receiver. If the optional sensor(s) are not included, the data read will be displayed as “N/A”. The receiver is currently set to query the sensors and voltage every 15 seconds. If no tags are  present this data will be saved to be written to the flash card as a dummy tag data once every minute.
The receiver is equipped with a USB port that can be used to see real-time data. This port can be accessed when the housing is open and uses a standard USB cable. The receiver software checks for a USB connection once every 30 seconds. If the USB connection should hang up, unplug and re-plug the connection to reestablish communication.
The receiver is powered through the means of an on-board battery pack. The battery pack yields approximately 3.6V and comes as either a rechargeable or non-rechargeable package.
Notes:

1. The power consumption of the receiver is approximately 80 milliamps during normal operation. Under normal operation the 6 D-cell battery pack will yield a theoretical life of 50 days.

2. The recommended SDHC flash card is the SanDisk with a capacity of 32GB or smaller.
   Important Note: Make sure the flash card has been formatted using the Default format options. The file system usually will be FAT32. DO NOT format using the quick format option.

3. A card reader (not supplied) is required for the SDHC.

Start-up

With the housing open, place a SDHC flash card in the slot. Connect the power by inserting the male end connector from the battery pack into the female end connector from the electronics on the top end of the receiver. The rechargeable battery pack requires an additional power cable. See Figure 2-1 for the location of the memory card and top end battery connection.
Observe the different status LEDs to understand what is taking place. There are a number of small LEDs located on the board. Only two can be seen while the board is placed in the tube.
There is a small yellow GPS status LED back behind the USB connector on the edge of the board. This yellow LED will only flash and be seen when the GPS functionality is powered and no fix lock has been obtained. This will happen shortly after the unit is powered up. If the unit is struggling to obtain a GPS fix it could remain in this mode for a while before giving up. It uses the GPS signal to set the time and sync the onboard clocks. If the GPS signal is not picked up it will use the time the onboard clock is currently set to.
The blue SDHC LED will turn on whenever the flash card is being read from or written to. It is located next to the USB connector on the corner of the board.
The main unit status LEDs in the hydrophone cone are located at the end of the receiver housing. See Table 2-1 below.

Sequence| Yellow LED| Green LED| Red LED| Event| Description
---|---|---|---|---|---
Initialization Sequence
1| On| On| On| Power Up| Long solid pulse.
2| On| On| Off/On| Power Up| Flashing Red
3| On or On/Off| Off| On or On/Off| Clock calibration and time sync|
4| Off or On/Off| On or On/Off| On| DSP Reset scheduled| Flashing Yellow indicates the GPS sync pulse is present and will be used to sync the clocks. The green will flash as the reset happens.
Windows Interface Routines
1| Off| On| Off| Clock Timing Routine. Entered and exited via user entered USB command| A solid Green LED remains on while in this loop. No logging is occurring at this time. Do a power reset to escape.
2| x| Off| On| Logging Routine. Entered via user entered USB

command

| A solid Red LED remains on while logging and sending that data via the USB to the ATS Trident PC software. Do a power reset to escape.
Main Routine
1| On or Off| On| Off On/Off| Reading sensors and voltage values| This happens every fifteen seconds. The Red LED will flash during reading if there is one or more bad sensors. The yellow LED will appear if the current logging session was started using a GPS
sync.
2| On/Off| On/Off| On/Off| SDHC
flash card not inserted in slot| If the SDHC card is not inserted and ready to go the Yellow, Green and Red will flash together.
3| Off| Off| On| Tag detected| Flashes for the first 2400 detections then quits.

Note: The programming port can be used to update the firmware that is used in the Control circuit.
Secure the housing for deployment. Ensure the #342 EPDM O-ring is seated in the flange groove and the sealing area is clean. Use five inch spanner wrenches to firmly seat the O-ring. It should not be possible for the O-ring to squeeze from the groove.

Status Check

While the housing is closed, a basic status check shown below can be initiated. To start place a magnet near the tip of the hydrophone cone near the location of the LEDs.

• Green, Red and Yellow LEDs will turn on when the reed switch is triggered.
• Checks if it is logging to the SDHC card.
• Checks battery voltage.
• Checks basic sensor functionality.
• Attempts to acquire the GPS timing pulse and use that to check the system clocks.
• Green and Yellow LED will be on constantly with a few flashes but the red LED remains solid, while system check is in progress.
• If the test is a fail, it will turn keep the red LED on. If it is a pass, the Green LED will turn on. It will remain with the Red or Green LED slowly flashing until a magnet switch is activated. A system reset will be scheduled at the finish of the test and normal operation will proceed.

Data File Format

All tag detections are stored in “.csv” files that can be read directly by most text editors such as Microsoft’s “Excel” and “Notepad”. The receiver is set up to use only one file. It will continuously append to the same file with footer and header breaks between logging sessions. The filename consists of the serial number and creation timestamps. The
naming convention is listed below:
SR17036_yymmdd_hhmmss.csv
A snippet of an example data file is shown in Figure 4-1
4.1 Header Format
Table 4-1 gives a description of the information contained in lines 1-10 shown in Figure 4-1.

commas (e.g. “ATS, NC, 02).
File Name| 8 character site name which consists of “SR” followed by the serial number then a “_”, ”H”, or “D” depending on whether it is a single, hourly or daily type file. This is followed by date and time of file creation (e.g. “SRser##_yymmdd_hhmmss.csv”)
Receiver Serial Number| A five character serial number that designates the year of receiver production and three characters that designate sequential production number (e.g. “17035”)
Receiver Firmware Version| The name and version of the receiver supervisory firmware and the name.
DSP Firmware Version| The name and version of the DSP firmware.
File Format Version| Version number of the file format
File Start Date| Date and time signal acquisition began (mm/dd/yyyy hh:mm:ss)
File End Date| Date and time signal acquisition ended (mm/dd/yyyy hh:mm:ss) Appears at the end of the data set.

Table 4-1
4.2 Data Format
Table 4-2 gives a description of the columns listed in line 11 shown in Figure 4-1.

the version.
SiteName| Descriptive name defined by the user and separated by two commas (e.g. “ATS , NC, 02”).
DateTime| Date recorded as mm/dd/yyyy. Time of detection, defined as the time the signal arrives at the hydrophone (TOA) and shall be recorded with microsecond precision  (hh:mm:ss.ssssss)
TagCode| 9 digit tag code as decoded by receiver (e.g. “G720837eb”) G72ffffff is used as a dummy tag for data recorded when no tag is present. Also one line of text:“Old Clock” followed by a line of text: “New Clock” will appear in this field when the configuration window sends over a new time.
Tilt| Tilt of the receiver (degrees). This typically will appear as “N/A” since this sensor is normally not included.
VBatt| Voltage of the receiver batteries (V.VV).
Temp| Temperature (C.CCº).
Pressure| Pressure outside of receiver (absolute PSI). This typically will appear as “N/A” since this sensor is normally not included.
SigStr| The logarithmic value for signal strength (in DB) “-99” signifies a signal strength value for an absent tag
BitPeriod| Optimal sample rate at 10 M samples per sec. To convert to frequency in kHz divide into 100,000.
Threshold| The logarithmic measurement of background noise used for tag detection threshold.

Table 4-2

Note: If the SDHC card (or the CF card on the older 3000 and 5000 Trident models) was formatted using the quick format option the flash card still will contain the previous file data. Only the file name(s) will have been removed. When this happens you will see some of the old data appearing after the file end footer and before the header of the next logging session. To avoid this avoid using the quick format option. Allow about an hour to format a 32GB SDHC SanDisk card.

Trident Receiver USB Interface and Filter Software

The ATS Trident Receiver USB interface and filter software can be downloaded from our website. The software is compatible with Windows 7 and Windows 10 operating systems. After downloading the software click on the setup executable and follow the instructions.
USB Driver Installation: The Trident software will walk you through installing the USB driver on its first boot up. If it is not done here the USB driver will need to be installed as a separate step. The driver installation can be initiated by going into the Settings menu of the main command window and selecting Install Driver.
5.1 Select Sonic Receiver (Change Receiver)
The first screen that appears when the software is run is shown in Figure 5-1.

The USB Communication mode allows for real-time data viewing while a computer is attached to the USB port. Enter the serial number of the receiver. This can be found on a label attached to the receiver housing. Click OK.
5.2 Main Command Window
Next, the Main Command window appears as shown in Figure 5-2.

The USB connection allows you to update the receiver’s configuration – Edit
Configuration and view the tags as they are being decoded – View Real Time Logging.
5.3 Edit Configuration 

This function accessed by the USB connection allows access to the Trident receiver’s configuration. Upon entering this screen, the receiver will also enter a special timekeeping mode so that it can continuously update the time portion of the display in real time. While in this mode, the green status LED will be lit continously.
To update the time and date on the receiver so it matches the PC’s, click on the blue button Set Receiver Clock to PC Clock, and the PC time and date will be sent to the Trident receiver, synchronizing the two clocks. When the Trident receiver updates its clock it sends to the SDHC card two lines of data. The first represents the time of the update using the old time, and the second the time of the update using the newly corrected time.
The Site Name for the SR3001 is fixed. It will be “SR” followed by the receiver serial number. The Site/System Name is customizable and will be sent over as it appears on the screen but is done as a separate step by clicking on the green button Send to Receiver located at the bottom of the screen. When finished, make sure to click on the red Close button so the receiver will get the command to exit the timekeeping mode. Cycling the power on the receiver will accomplish the same thing. The time setting here will be overwritten by GPS time on boot up if a GPS fix is acceived. If you will have access to GPS during deployment you will only need to do this configuration step once. This step will save the timezone stored on your PC which will allow your GPS sync’d timestamps to appear as local time. The GPS sync’d time will never be in daylight savings time. Using the GPS to set the clock provides improved time syncing across different SR3001 units.i
5.4 View Real Time Logging

You may view real time datalogging of tag data using the USB connection by selecting the View Realtime Logging button, and then selecting the green Start button at the bottom of the screen. This displays the data as it is being captured by the Trident Receiver. If the SDHC card is present in the SD card slot of the receiver, data will appear in blocks of fifteen seconds of accumulated data, with data appearing every 15 seconds on the screen. If the SD card slot is empty, the data will be displayed immediately as it is detected. Over time this data will develop a time lag depending on the amount of data being printed to the screen and the speed of the PC.

The View Real Time Logging function has a number of display options to facilitate viewing the incoming data. These options can be selected from the Settings drop-down menu at the top of the screen. For example, detections can be shown as separate lines of data, as shown in Figure 5-4, or by using the Summarize Data option. The Summarize Data option will display one data line per tag. The screen is refreshed for each new data point. It can be selected to filter detections having periods too large or too small to be valid. This option is shown below in Figure 5-6 and in Figure 5-7.

If the log file option is selected a new log file will be opened at the start of the logging session that saves a copy of the incoming data. These log files are kept in the ‘C:\ Advanced Telemetry Systems, Inc\ATS Trident Receiver\Log’ folder. With the log file option you also have the option to hook up a GPS receiver to the PC that spits NMEA sentences out a serial port. This information will then be saved to the log file.

This screen also shows in the farthest left column a speaker icon followed by a column of check boxes. If a tag code is checked it will play a tone that will be tied to it’s last signal strength value. It will change the tone’s pitch and duration accordingly. Since playing the tone pauses the operation momentarily it will slow screen updates down a bit. Ideally keep the number of boxes checked to a small number.
5.5 Filter Data

5.5.1 Standard JSAT’s Coded Tags
This option does not make use of an active USB connection. It takes as input one or more of the Trident Receiver files residing on your computer that have been copied over from the SDHC card(s). It post processes the data by filtering out invalid data, splitting the files into smaller chunks and summarizing run data.
There are two filtering methods to choose from. They give slightly different results.
Method “A-Default” and method “B-Minimum Mode”.
Method “A” (Default – SVP) looks for tags with consecutive repeating periods that are within a certain range of the selected nominal period(s). These periods need to stay within a narrow range of each other.
Method B developed by Pacific Northwest National Laboratory (PNNL) uses a moving window. The window size is about 12 times the estimated pulse rate interval. In this window the tag period used is the minimum mode value close to the nominal.
Both of these routines can take a while to process all the data. It does allow a number of files to be processed at a time. As it processes, the data summary information will be displayed. Before starting the routine, make sure to check the boxes next to the periods of the sonic transmitters you used.
5.5.2 Temperature and Depth Tags
ATS manufactures in addition to standard JSAT’s coded tags, tags that transmit the JSATs code along with the tag’s current temperature and/or depth. This data can be retrieved and deciphered by clicking on the check box located at the bottom of the screen shown in Figure 5-8. This option is only available using Filter Method “A-Default”.
Processing the temperature and depth tag data will require additional input into the filter program.
5.5.2.1 Barometric Pressure
Depth measurement is really a measurement of pressure. To calculate depth the local barometric pressure needs to be taken into account. This pressure frequently changes, but the filter can only use one value for its depth calculation. Pick a midrange value that is fairly representative of the site’s average barometric pressure during the time the data was collected.
The value entered can be designated in units of atmospheres (atm), mercurial inches (inHg), kilopascals (kPa), millibars (mBar), mercurial millimeters (mmHg), or pounds per square inch (psi). Ensure that the correct type of units are selected or else incorrect results will be calculated.

5.5.2.2 Depth Temperature Tag Code List
A simple “.csv” file is needed for input containing a list of the temperature and depth tag codes that were deployed. Below is what the contents of a possible file would look like:
G724995A7
G724D5B49
G72453398
G72452BC7
G724A9193
G722A9375
G724BA92B
G724A2D02

Filter Data File Format

When the filter option from the File Data dialog is finished running there will be a number of new files created. They will consist of 5 different types.
Example input file name:
SR17102_171027_110750.csv
One example each of the 5 types of output files:
Type 1) SR17102_171027_110750_Log1_1027_1107_2.csv
Type 2) SR17102_171027_110750_DData_Log1_1027_1107_2.csv
Type 3) SR17102_171027_110750_RejectedTags_Log1_1027_1107_2.csv
Type 4) SR17102_171027_110750_Cleaned_Log1_1027_1107_2.csv
Type 5) SR17102_171027_110750_summary_Log1_1027_1107_2.csv
6.1 Filter File Output Type 1
Example type 1 output file names:
SR17102_171027_110750_Log1_1.csv
SR17102_171027_110750_Log1_1027_1107_2.csv
SR17102_171027_110750_Log2_1027_1110_1.csv
SR17102_171027_110750_Log2_1027_1110_2.csv
The input file can contain multiple logging sessions which are defined to be a power on off or the insert and removal of a SDHC card. The input file can be larger than some programs like Excel can handle. Type 1 files are partitioned copies of the input file.
These partitions isolate data into files according to the log session and they keep the files smaller than 50,000 lines of data.
6.2 Filter File Output Type 2
Example type 2 output file names when the “A – Default” selection in the File Data dialog was selected:
SR17102_171027_110750_DData_Log1_1027_1107_1.csv
SR17102_171027_110750_DData_Log1_1027_1107_2.csv
SR17102_171027_110750_DData_Log2_1027_1110_1.csv
SR17102_171027_110750_DData_Log2_1027_1110_2.csv
Example type 2 output file names when the “B – Minimum Mode” selection in the File Data dialog was selected:
SR17102_171027_110750_MData_Log1_1027_1107_1.csv
SR17102_171027_110750_MData_Log1_1027_1107_2.csv
SR17102_171027_110750_MData_Log2_1027_1110_1.csv
SR17102_171027_110750_MData_Log2_1027_1110_2.csv
Type 2 files have all the information of the Type 1 files with additional information added on. This file will not include rejected data if the filter was run with the
Remove Filtered Hits from Final Data checkbox checked from the File Data dialog.

as the time the signal arrives at the hydrophone (TOA) and shall be recorded with microsecond precision  (hh:mm:ss.ssssss)
TagCode| 9 digit tag code as decoded by receiver (e.g. “G7280070C”) G72ffffff is used as a dummy tag for data recorded when no tag is present.
RecSerialNum| A five character serial number that designates the year of receiver production and three characters that designate sequential production number (e.g. “18035”)
FirmwareVer| The version of the receiver supervisory firmware.
DspVer| The version of the DSP firmware.
FileFormatVer| Version number of the file format.
LogStartDate| Date and time signal acquisition began for this logging session (mm/dd/yyyy hh:mm:ss)
LogEndDate| Date and time signal acquisition finished for this logging session (mm/dd/yyyy hh:mm:ss *####+mmddhhmmss)
FileName| Diagnostic and timing information. Data here will vary depending on the version.

Table 6-1

since this sensor is normally not included.
VBatt| Voltage of the receiver batteries (V.VV).
Temp| Temperature (C.CCº).
Pressure| Pressure outside of receiver (absolute PSI). This typically will appear as “N/A” since this sensor is normally not included.
SigStr| The logarithmic value for signal strength (in DB) “-99” signifies a signal strength value for an absent tag
BitPrd| Optimal sample rate at 10 M samples per sec (related to tag frequency)
Threshold| The logarithmic measurement of background noise used for tag detection threshold.
ImportTime| Date and time this file was created (mm/dd/yyyy hh:mm:ss)
TimeSince LastDet| Elapsed time in seconds since the last detection of this code.
Multipath| Yes/No value indicating if the detection was from a reflected signal.
FilterType| SVP (Default)/ MinMode value indicating the choice of filtering algorithm used on this data.
Filtered| Yes/No value indicating if this data has been rejected.
NominalPRI| The assumed programmed value for the tag’s pulse rate interval.

Table 6-2

DetNum| The current detection number for this accepted code, or if followed by an asterisk, the count of previously rejected hits for this code.
---|---
EventNum| This count increases if there is a reacquisition of this code after an acquisition loss.
For the SVP method this loss needs to be >= 30 minutes.
For MinMode an acquisition loss happens if there are less than 4 hits contained within an acceptance window of 12 nominal PRIs.
EstPRI| The estimated PRI value.
AvePRI| The average PRI value.
ReleasedDate|
Notes|

6.3 Filter File Output Type 3
Type 3 files have the detection data for rejected codes.
Example type 3 for the Default SVP filter output file names:
SR17102_171027_110750_RejectedTags_Log1_1027_1107_1.csv
SR17102_171027_110750_RejectedTags_Log1_1027_1107_2.csv
SR17102_171027_110750_RejectedTags_Log2_1027_1110_1.csv
SR17102_171027_110750_RejectedTags_Log2_1027_1110_2.csv
6.4 Filter File Output Type 4
Type 4 files are Type 1 files with the invalid tag detections removed.
Example type 4 output file names:
SR17102_171027_110750_Cleaned_Log1_1027_1107_1.csv
SR17102_171027_110750_Cleaned_Log1_1027_1107_2.csv
SR17102_171027_110750_Cleaned_Log2_1027_1110_1.csv
SR17102_171027_110750_Cleaned_Log2_1027_1110_2.csv
6.5 Filter File Output Type 5
Example type 5 output file names:
SR17102_171027_110750_summary_Log1_1027_1107_1.csv
SR17102_171027_110750_summary_Log1_1027_1107_2.csv
SR17102_171027_110750_summary_Log2_1027_1110_1.csv
SR17102_171027_110750_summary_Log2_1027_1110_2.csv
Type 5 files have the synopsis of data contained in the earlier files.

Date recorded as mm/dd/yyyy. Time of detection, defined as the time the signal arrives at the hydrophone (TOA) and shall be recorded with microsecond precision  (hh:mm:ss.ssssss)
Last Date/Time| Date and Time of last acquisition of the listed Tag Code. Date recorded as mm/dd/yyyy. Time of detection, defined as the time the signal arrives at the hydrophone (TOA) and shall be recorded with microsecond precision  (hh:mm:ss.ssssss)
Elapsed| Time difference in seconds between the first two columns.
Tag Code| 9 digit tag code as decoded by receiver (e.g. “G7229A8BE”)
Det Num| The number of valid detections for the listed tag code. If an “” is present the Tag Code was filtered out as a false positive.
Nominal| The assumed programmed value for the tag codes’ pulse rate interval.
Ave| The average PRI value. An adjacent “” indicates it was > then 7 periods long.
Est| The estimated PRI value.
Smallest| The smallest PRI that was a valid value.  The PRIs checked off in the File Data dialog are used to determine the set of acceptable PRIs.
Largest| The largest PRI that was a valid value. The PRIs checked off in the File Data dialog are used to determine the set of acceptable PRIs.
Sig Str Ave| The average signal strength of the valid data for the listed tag code.
Min Allowed| Lower Signal strength values are filtered out.

Filtered| Number of acquisitions for the listed tag code that have been

filtered out.

Table 6-4
6.6 Additional Output (Temperature and Depth Tags)
When the filter is done running there will be the same output as with running without the temperature depth tag option selected with a few additions.
One additional file type:
Type 6) SR17102_171027_110750_SensorTagData_Log1_1027_1107_2.csv
And additions to the following file types:
Type 2) SR17102_171027_110750_DData_Log1_1027_1107_2.csv
Type 4) SR17102_171027_110750_Cleaned_Log1_1027_1107_2.csv
Type 5) SR17102_171027_110750_summary_Log1_1027_1107_2.csv
6.6.1 Data Appended to Filter File Output Type 2
The following is an example of the data appearing as additional columns appended to the dataset after the column labeled “Notes”.

N – Detection information is for a non-sensor tag.
Y – Detection information is for a sensor tag but no sensor data was paired with this detection.
T – Detection information is for a sensor tag and is paired with temperature data only.
D- Detection information is for a sensor tag and is paired with depth data and possibly temperature data.
TempDateTime| Date recorded as mm/dd/yyyy. Time of detection, defined as the time the signal arrives at the hydrophone (TOA) and shall be recorded with microsecond precision (hh:mm:ss.ssssss). This timestamp is for the received code imparting a tag’s temperature information.
TempSensorCode| 9 digit tag code as decoded by receiver (e.g. “G7207975C”) representing the temperature information.
TagTemp(C)| The temperature (C.CCº) measured by the sensor tag.
DepthDateTime| Date recorded as mm/dd/yyyy. Time of detection, defined as the time the signal arrives at the hydrophone (TOA) and shall be recorded with microsecond precision (hh:mm:ss.ssssss). This timestamp is for the received code imparting a tag’s depth information.
DepthSensorCode| 9 digit tag code as decoded by receiver (e.g. “G720B3B1D”) representing the depth information.
TagPress(mBar)| The pressure (PPPP.P) in mBar measured by the sensor tag.
TagDepth(m)| The converted depth position (DDD.DD) in meters measured by the sensor tag.
SensorPrd| The period of the sensor codes in seconds appearing after the primary code.

Table 6-5
6.6.2 Data Appended to Filter File Output Type 4
The following is an example of the data appearing as additional columns appended to the data after the column labeled “Threshold”.

as the time the signal arrives at the hydrophone (TOA) and shall be recorded with microsecond precision (hh:mm:ss.ssssss). This timestamp is for the received code imparting a tag’s temperature information.
Temp SensorCode| 9 digit tag code as decoded by receiver (e.g. “G7207975C”) representing the temperature information.
Tag Temp(C)| The temperature (C.CCº) measured by the sensor tag.
Depth Date/Time| Date recorded as mm/dd/yyyy. Time of detection, defined as the time the signal arrives at the hydrophone (TOA) and shall be recorded with microsecond precision (hh:mm:ss.ssssss). This timestamp is for the received code imparting a tag’s depth information.
Depth SensorCode| 9 digit tag code as decoded by receiver (e.g. “G720B3B1D”) representing the depth information.
Tag Press(mBar)| The pressure (PPPP.P) in mBar measured by the sensor tag.
Tag Depth(m)| The converted depth position (DDD.DD) in meters measured by the sensor tag.

6.6.3 Data Appended to Filter File Output Type 5
This file has only one additional columns appended to it. It appears after the column labeled “# Filtered”. It is labeled “Sensor Tag” and just indicates whether the code listed belongs to a sensor tag with the indicator “Y” or “N”.
6.6.4 Additional Filter File Output Type 6
Example type 6 output file names:
SR17102_171027110750 SensorTagData _Log1_1027_1107_1.csv
SR17102_171027110750 SensorTagData _Log1_1027_1107_2.csv
SR17102_171027110750 SensorTagData _Log2_1027_1110_1.csv
SR17102_171027110750 SensorTagData _Log2_1027_1110_2.csv
Type 6 files have the just the code, temperature and depth data broken down by the time the data was received.

the time the signal arrives at the hydrophone (TOA) and shall be recorded with microsecond precision (hh:mm:ss.ssssss)
TagCode| 9 digit tag code as decoded by receiver (e.g. “G7229A8BE”)
Secs| A decimal representation in seconds of the time the primary code was decoded.
Temperature Date/Time| Date recorded as mm/dd/yyyy. Time of detection, defined as the time the signal arrives at the hydrophone (TOA) and shall be recorded with microsecond precision (hh:mm:ss.ssssss) . This timestamp is for the received code imparting a tag’s temperature information.
TempCode| 9 digit tag code as decoded by receiver (e.g. “G7207975C”) representing the temperature information.
TempSecs| A decimal representation in seconds of the time the temperature code was decoded.
TempTimeSinceCode| The elapsed decimal time that has elapsed since the primary sensor tag’s code was detected.
Temp(C)| The temperature (C.CCº). measured by the sensor tag

Table 6-7

the time the signal arrives at the hydrophone (TOA) and shall be recorded with microsecond precision (hh:mm:ss.ssssss) . This timestamp is for the received code imparting a tag’s depth information.
DepthCode| 9 digit tag code as decoded by receiver (e.g. “G720B3B1D”)

representing the depth information.

DepthTimeSinceCode| The elapsed decimal time that has elapsed since the primary sensor tag’s code was detected.
DepthTimeSinceTemp| The elapsed decimal time that has elapsed since the temperature sensor tag’s code was detected
Press(mBar)| The pressure (PPPP.P) in mBar measured by the sensor tag.
Depth(m)| The converted depth position (DDD.DD) in meters measured by the sensor tag.

Table 6-8

Addendum: Rechargeable Battery Pack (ATS PN 19421)

Battery pack size

Diameter:| 2.9” Max (7.4 cm)
Length:| 11.5” (29.2 cm)
Weight:| 4.6 lbs (2.1 kg)
Operating Voltage range:| 2.5VDC to 4.2VDC
Nominal Capacity:| 140,800 mAh / 516.7 Wh
Maximum Discharge Current:| 2 Amps DC
Maximum Charge Current:| 30 Amps DC
Cycle Life (Charge/Discharge):| 500
Connectors
Charge connector:| D-SUB PLUG 7Pos (2 Power, 5 Data)
SR3001 connector:| ATS PN 19420 (D-SUB connector to receiver 4 Pos connector)

Shelf Life: 12 Months*
*Note: If batteries are to be in storage longer than 12 months, it is recommended to cycle the battery in storage mode for another 12 months of shelf life.
Temperature Ratings

Addendum: Battery Charger (ATS PN 18970)

ATS sells a battery charger that can charge up to 4 rechargeable battery packs at a timeThe battery charger specifications are listed below:

0°C
Storage Temperature:| -40°C to +85°C*

Charging

Operation
Automatically starts charging when battery is connected, and AC power is applied to charger.
Start; Pre-Current Charge to determine battery condition, then switches to Fast Charge Current.
Display Indicators
State of Charge Display
4 – LED display indicating battery state of charge (See LED Display table on next page for complete details.)
Mode Display
Mode indicates if charge is optimal for storage or normal use.
Also serves as an error code.
(See LED Display Table on next page for complete details.)
LED Display Table operation/Fault table (see next page)
Storage Mode
With a discharged battery connected to charger, press Storage button.
Battery will only charge to 50% capacity for long term battery storage (12 months).
After 12 months, it is recommended to cycle Storage mode again if battery is to remain in storage.
Battery Charger LED Display Table:

Battery Charger Fault LED Display Table:

charging at pre-charge current limit for more than 10 hours.
2 x 250ms blinks

every 5 seconds

| Fast charge mode timeout| Battery has been charging at fast charge current limit for more than 10 hours.
3 x 250ms blinks every 5 seconds| Battery over temperature| Battery temperature is too high to charge as measured by the thermistor.
4 x 250ms blinks

every 5 seconds

| Battery under temperature| Battery temperature is too low to charge as measured by the thermistor.
5 x 250ms blinks every 5 seconds| Over charge voltage| Charger output current is higher than control settings.
6 x 250ms blinks every 5 seconds| Over charge current| Charger output voltage is higher than control settings.

****470 FIRST AVE NW ISANTI, MN 55040
sales@atstrack.com
www.atstrack.com
763-444-9267

Read User Manual Online (PDF format)

Read User Manual Online (PDF format)  >>

Download This Manual (PDF format)

Download this manual  >>