High Resolution Catch and Effort Data Collection

Collection of High Resolution Spatial and Temporal Fishery Dependent Data to Support Scientific Research

FLDRS_Administrators Guide

High Resolution Catch and Effort Data Collection

OMB: 0648-0803

Document [pdf]
Download: pdf | pdf
FLDRS
Administrator’s Guide
Version 4.1.9

FLDRS Administrator’s Guide

About the FLDRS Application ...................................................... 1

If you’ve used FLDRS before ...............................................................1
Specifications ..................................................................................1

Installing the FLDRS Software ..................................................... 2

FLDRS 4.1.9 installation .....................................................................2
ODBC driver configuration ..................................................................4
Installing supporting software .............................................................5
FLDRS directory structure ..................................................................6

Starting FLDRS ........................................................................ 7
Table Import .......................................................................... 8

Importing a support table ...................................................................8
Exporting a support table ................................................................. 10
Reloading a support table ................................................................. 10
System data backup ........................................................................ 11
System data recovery ...................................................................... 12

Software Setup ...................................................................... 12
Data Feeds Tab .............................................................................. 12
Data Export Tab ............................................................................. 16
Data backup.................................................................................. 18
Transaction logging......................................................................... 18
GNU Encryption ............................................................................. 19
Configure Email ............................................................................. 19
Sentences Tab ............................................................................... 21
Users Tab ..................................................................................... 22
Program Terms Tab ........................................................................ 23
Dynamic Data Tab .......................................................................... 25
Support Tables Tab ......................................................................... 27
Setting User Defaults ...................................................................... 31

Manage Trips ......................................................................... 32
View or print trip reports ................................................................. 32
Delete old trips.............................................................................. 32
Retransmit or re-export a trip ........................................................... 32

Troubleshooting ..................................................................... 34
GPS status says “GPS Signal: GPS Off” ................................................. 34
Jumping cursor when GPS is connected ............................................... 34
Depth sounder says FA but no depth values appear ................................ 34
Exported files do not arrive when using SkyMate® ................................. 34
Exported files do not arrive when using McMurdo FMCT/G (formerly Boatracs®)
................................................................................................. 35

FLDRS Error Messages .............................................................. 37

i

FLDRS Administrator’s Guide

About the FLDRS Application
The Fisheries Logbook Data Recording Software (FLDRS) application allows fishermen to
enter catch data. There are two modules within FLDRS:
•

The Administration module simplifies application maintenance and the control of
application settings. FLDRS has two administration roles. An Administrator has
access to the Administration module of the FLDRS application, such as a sector
manager, field technician, or scientist. The eVTR Database Administrator has
authorization to add or modify codes in the master in-house database where FLDRS
data are processed and archived.

•

The Logbook module captures information on fishing activity, catch, landings, and any
additional data defined by an eVTR Database Administrator. The user can change some
setup options.

This document explains how to use the tools in the Administration module.

If you’ve used FLDRS before
Here is a brief summary of the new features/fixes in version 4.1.6:
•

Fixed bug with Dynamic Data numeric data validation.

•

Ability to add multiple instances of a species with different dispositions.

•

Fixed bug with Apportionment and Landing records during trip re-export file
creation.

Specifications
The FLDRS application can run on most Windows® operating systems. It supports a connection
to a global positioning system (GPS) that provides location data to the FLDRS software, and
may also connect to a depth sounder. A connection to a satellite communications system (e.g.,
McMurdo FMCT/G (formerly Boatracs®), SkyMate®) is desirable, so that catch data can be
sent electronically while at sea.
Here are the minimum and recommended systems specifications for PC to run FLDRS:
Specification

Minimum

Recommended

Operating System

Windows XP®

Windows 7®, Windows 8®, or Windows 10®

Memory

Intel Pentium® III
or equivalent
256 MB

2+ GB

Hard Drive

20 GB

60+ GB

USB Drive

2 USB 1.1 ports

4 or more USB 2.0 ports

Screen Resolution

1024 X 768

At 96dpi: 1680x1050 pixels (W/H ratio =
1.6)
1280x1024 pixels (W/H ratio = 1.25) 1280x768
pixels (W/H ratio = 1.66) 1024x768 pixels (W/H
ratio = 1.33

Processor

Quad-core (or greater) processor

1

FLDRS Administrator’s Guide

Installing the FLDRS Software
The installation procedure for FLDRS 4.1.9 is new. Please read and follow the directions
carefully.
Windows Vista and 7 users may be asked during the installation if they
“…want to allow the following program from an unknown publisher…”
Click Yes.

FLDRS 4.1.9 installation
These instructions assume that FLDRS 4.1.9 has not been installed on the host machine.
FLDRS 4.1.9 requires that at minimum, Microsoft .NET Framework 4.0 be installed on
the host machine. Windows 7 machines should meet this requirement, but older operating
systems such as Windows XP may need these libraries installed.
To determine which versions of .NET Framework are installed:
1. Click Start, type regedit in the Search programs and files box, and then
press Enter. (For Windows XP, click Run and type regedit in the Run
dialog box.)
2. Expand, if necessary, the NET Framework Setup folder and then the NDP
folders. Look for the V4.0 folder, which indicates that Framework 4.0 or
higher is installed. If it is not, see “Installing supporting software” on page
5 to install the .NET Framework software.

3. Once the .NET Framework is installed, double click on setup.exe to start
the FLDRS installation:

4. Click the Next button.

2

FLDRS Administrator’s Guide

The setup process shows the location where FLDRS will be installed. Click Next to
accept the location and continue.

5. The setup process defines the name of the folder the user will see when
clicking on the Start Menu. Click Next to accept the name and continue.

6. Next, review the list of software selected for installation, scrolling down to
see the full list. FLDRS 4 requires several additional software programs
that are listed in the window.
If this the first installation of FLDRS 4, check the boxes to install all the programs listed
under “Additional Software Required” unless you know for certain that these programs
are already installed. For example, previous versions of FLDRS required 7-Zip and GNU
file encryption software, so if this machine already had FLDRS, you can uncheck those
boxes.
For this release, the user needs a PDF reader to read the FLDRS trips, so either make
sure that a reader is installed, or check the Install Adobe Reader box to install it now.

3

FLDRS Administrator’s Guide

7. Click the Next button when you have selected the software to install.
The installation process continues. Once FLDRS is installed, the installation proceeds to
install the software you selected earlier.
8. When the installation is complete, click the Finish button.

ODBC driver configuration
The FLDRS installation process will attempt to configure the necessary ODBC driver. If the
process is unsuccessful, a warning message will be displayed and the driver will need to be
manually configured by following the steps listed below.
After the installation program ends, you need to install both sqliteodbc.exe and
sqliteodbc_w64.exe. Follow the prompts, accepting the defaults where possible.
1. Go to Start, Control Panel, System and Security, Administrative Tools,
Data Sources (ODBC)
2. On the User DSN tab, click Add.
3. Double click SQLite3 ODBC Driver. Do not click SQLite.
4. For Data Source Name, type in FLDRS_SQLite The case must be exact.
5. For Database name, click Browse and navigate to
C:\NEFSC\FLDRS\Database.
6. Click fldrs.sqlite, then Open, then OK.

4

FLDRS Administrator’s Guide

Installing supporting software
You can install the required software directly, instead of running the FLDRS installation
program. All the supporting software is located in the SupportingFiles subdirectory of the
FLDRS installation. Windows XP® installations will not require installing
CRRuntime_64bit_13_0_15.msi.
Supporting software

Installation instructions

Microsoft .NET Framework
4.0

Double click on dotNetFx40_Full_x86_x64.exe and
complete the installation process, accepting the default
settings.

7-zip

Double-click on 7z465.exe and follow the prompts,
accepting the defaults where possible. Expected
Location:
C:\ Program Files\7-Zip\7z.exe
C:\ Program Files (x86)\7-Zip\7z.exe

GnuPG encryption software

Double-click on gpg4win-2_1_0.exe and follow the
prompts, accepting the defaults where possible. Install
only the GnuPG component, and deselect Kleopatra last.
Finish the GnuPG setup in FLDRS, logging in as an
administrator and clicking Software Setup. Click on the
Data Export tab, and make sure that the GNU Encryption
Path field is populated with something like:
C:\Program Files\GNU\GnuPG\pub\gpg.exe or
C:\Program Files (x86)\GNU\GnuPG\pub\gpg.exe
Next, switch tabs or exit and re-enter Software Setup, to
make sure that the encryption file path is saved to the
database.
Next, click the Setup Encryption button to launch a DOS
program that sets the trusted certificate for data
encryption.
At the gpg> prompt, enter the following sequence:
5 for the option
y for confirmation
quit to complete the GnuPG configuration.

Reporting software

Install both CRRuntime_32bit_13_0_15.msi and
CRRuntime_64bit_13_0_15.msi. Follow the prompts,
accepting the defaults where possible.

SQLite Database Drivers

Install both sqliteodbc.exe and sqliteodbc_w64.exe.
Follow the prompts, accepting the defaults where possible.

PDF reader software

If a PDF reader is not already installed, run the
AcroRdrDC1500920069_en_US.exe setup, accepting the
defaults where possible.

5

FLDRS Administrator’s Guide

FLDRS directory structure
When you install the FLDRS application, it creates these directories and files. You can install
to a different path, but by default, the installation process creates these directories in
C:\NEFSC\FLDRS.
Directory Name
C:\NEFSC\FLDRS
C:\NEFSC\FLDRS\Database
C:\NEFSC\FLDRS\GpsPolling
C:\NEFSC\FLDRS\Help
C:\NEFSC\FLDRS\LocalBackup
C:\NEFSC\FLDRS\Log
C:\NEFSC\FLDRS\PdfBackup
C:\NEFSC\FLDRS\SupportingFiles
C:\NEFSC\FLDRS\SupportTables
C:\NEFSC\FLDRS\SystemBackup

Contents
FLDRS parent directory for all FLDRS software
components
Help files for user and Administrator modules
GPS polling output files
Help files for user and Administrator modules
Backups created when fisherman saves a trip
FLDRS 4.1 log files
Location of .pdf trip reports
Additional software required for FLDRS
The tables that provide operational and default data for
FLDRS
Files used in database crash recovery

6

FLDRS Administrator’s Guide

Starting FLDRS
1. On the Windows desktop, find the FLDRS icon.
2. Double-click on the icon. The main FLDRS window appears.

3. Click the Login button.
4. Log in with a user name that has Administrator privileges. The first time you log in to
FLDRS, use the Administrator account with the username system and the password
System.1

5. The Fisheries Logbook Data Reporting Software window appears:

6. Change the password immediately; see “Users Tab” on page 22.
From this window, you can:
•

Import support tables; see below.

•

Set up FLDRS; see “Software Setup” on page 12.

•

Manage trip reports; see “Manage Trips” on page 32.
7

FLDRS Administrator’s Guide

Table Import
Use Table Import to update the support tables that provide basic data to the FLDRS application,
such as core support tables and system defaults.
Each support table contains a comprehensive list of all the possible codes that a Logbook user
might need. The tables can be customized for individual data collection programs, allowing
the software to be adapted for different regions, fisheries, or research projects. During the
initial setup phase, the Administrator works with the Logbook user to select a set of defaults
specific to the fishing vessel.
The Administrator maintains the tables by reloading them when significant updates are
distributed. However, importing a new table replaces the current table, and may affect the
Logbook user’s selections.

Importing a support table
An Administrator can import 14 tables:
Support Table
Name
Operators

Table Contents
Lists a subset of permitted operators. To view the table, see “Support Tables Tab” on page 27.

Gear

Lists all the possible types of gear that a fisherman may deploy, along with ranges
of acceptable values for the gear description. To view the table, see “Gear Tab” on page 28.

Species

Lists all the possible species that a fisherman can record as a catch or discard,
along with grade descriptions, market descriptions, and units of measure
combinations. To view the table, see “Species Tab” on page 28.
Lists all the ports where a fisherman can sail or land. To view the table, using Software Setup;
see “Ports Tab” on page 30.

Port
Sentence
Data

Lists the NMEA 0183 sentences and formats that FLDRS uses to obtain date, time,
position and depth information. To update these values, see “Sentences Tab” on page 20.

Species
Conversion

Lists the rules that determine which entries of retained catch (species, grade,
market, units of measure combinations) can be converted to different grades, market
categories, or units of measure when reporting fish landings. The table also contains
approximate conversion factors to assist the user in converting grades, market categories, or
units of measure. This table cannot be viewed or changed within Software Setup.

System
Defaults

Provides FLDRS with information on default dispositions to assign to the retained
and discarded catch, and to apportionment records. It also controls the codes that indicate no
catch is caught during a fishing effort, and maps dispositions to non- dealer dealer codes
(e.g., home consumption, bait, seized by enforcement). You cannot view or change this table
within Software Setup.
Lists a subset of permitted vessels. To view the table, see “Vessels Tab” on page 27.

Vessel
Dealer

Disposition

Lists all the permitted dealers to whom a fisherman can sell. The Dealer table is
restricted to sales; non-sales dispositions are in the Disposition table. To view the table, see
“Dealers Tab” on page 29.
Lists all the possible disposition categories for fish at both the catch (retained and
discarded) and apportionment (landings) levels. To view the table, see
“Dispositions Tab” on page 30.

8

FLDRS Administrator’s Guide
Support Table
Name
Statistical
Areas

DST Data

Program
Terms

Dynamic Data

Table Contents
Lists all the possible fishing locations, using standard statistical areas for the
appropriate region. FLDRS uses this table to assign a statistical area based on positional
information (latitude and longitude). This table subdivides each statistical area into ten
minutes squares. To view the list of statistical areas, see “Areas Tab” on page 31.
Controls adjustments for daylight savings time. Since these are time zone-specific,
you need to load a different version of the table if you use FLDRS in a different time
zone. You cannot view or change this table within Software Setup.
Lists all the fishery programs in which vessels can participate, along with rules,
events, and gear parameters for each program. To view the table, see “Program Terms Tab”
on page 23. If you import both this table and the Dynamic Data table, you must import
Program Terms first.
Lists all the different types of data that a user can be required or desired to collect,
along with parameters for each data element. To view the table, see “Dynamic Data Tab” on
page 25. If you import both this table and the Program Terms table, you must import
Program Terms first.

9

FLDRS Administrator’s Guide

Exporting a support table
Exporting a support table creates a file containing the table data, saved as comma-separated
values.
Currently, you can only export the Sentence Data table, which contains the NMEA strings and
default values that you entered in the Sentence Data tab in Software Setup.
You can copy the sentence data setup from one FLDRS computer to another by exporting the
file from FLDRS on the source installation, transferring the .csv file to the target installation, and
then importing the file into FLDRS on the target installation using Table Import.

Reloading a support table
When a support table changes, the eVTR Database Administrator propagates the change to
FLDRS installations in the field by providing an updated .csv file for Administrators to import
into the FLDRS application.
WARNING: UPDATING A SUPPORT TABLE SO IT NO LONGER CONTAINS
RECORDS USED IN A LOGBOOK USER’S SHORT LIST DELETES THOSE
RECORDS FROM THE SHORT LIST.
To reload a support table:
1. First, back up the existing database by copying it and placing a renamed copy in its
original location. This allows you to recover the original database if the support table
import fails.
2. Start the FLDRS software and log in as an Administrator.
3. Click the Table Import button.
4. Click the Browse button for the appropriate table, locate the .csv file, and click Open.
5. Click the appropriate Import button. FLDRS warns you if you are deleting a fisherman’s
default settings.
For gear only, FLDRS warns you if the values in the user’s default settings fall outside
the acceptable ranges of the new table. If default settings are outside the acceptable
ranges, double-check the default settings and/or consult an eVTR Database
Administrator.
6. Check the new table by navigating to the Administrator’s Software Setup and selecting
the appropriate Support Tables tab. If the support table is not viewable through
Software Setup, attempt a test trip and make sure the Logbook works as expected.
If the data does not appear properly in the Logbook user’s view of the table, use your saved
copy of the database to revert to the original table, and report the problem to an eVTR Database
Administrator.

10

FLDRS Administrator’s Guide

System data backup
FLDRS includes several levels and types of backup and recovery. You can set up FLDRS to
create automatic backups, or create a backup manually when desired.
Automatic backups
FLDRS automatically backs up the active trip at specified intervals (set in System
Settings’ “Data Export Tab” on page 16). In the unhappy event of a catastrophic database
failure, the fisherman can use this backup to recover data for the active trip.
When the trip is complete, FLDRS backs up trip, transmission, user and administrator
data. If necessary, these files can be imported using the System Data Recovery tab, as
described below.
In addition, FLDRS backs up the entire database. If necessary the backup file can be
imported as described below.
FLDRS does not automatically back up the entire database of settings. You should back up
these settings whenever changes occur; for example, if you have changed the user
configuration file but no trip has yet been created, the configuration has not yet been saved
automatically.
User backups
If desired, you can manually back up data using the System Data Backup tab in Table Import.
To back up system and user data manually:
1. Start the FLDRS software and log in as an Administrator.
2. Click the Table Import button.
3. Click the System Data Backup tab.
4. Click the appropriate Browse button, specify the location for the backup file, and click
OK.
5. Click the Export button. FLDRS informs you when the backup is complete.

11

FLDRS Administrator’s Guide

System data recovery
To use backed-up system data to help with crash recovery:
1. Start the FLDRS software and log in as an Administrator.
2. Click the Table Import button.
3. Click the System Data Recovery tab.
4. Click the appropriate Browse button, specify the backup file’s name and location, and
click OK.
5. Click the Import button. FLDRS informs you when the file has been loaded.

Software Setup
Software Setup provides a quick way to view and adjust many of the application’s most useful
options.
The FLDRS Software Setup provides tools for:
•

Setting up satellite communications and the export of trip data; see “Data Feeds Tab”
on page 12 and “Data Export Tab” on page 16.

•

Managing the links between FLDRS and a GPS unit (see “GPS Setup” on page 12) or
a depth sounder (see “Depth sounder” on page 15).

•

Setting up the NMEA strings to read from the GPS unit; see “Sentences Tab”
on page 20.

•

Managing user accounts and access to the FLDRS modules; see “Users Tab” on page 22.

•

Viewing details of the programs in which vessels may participate; see “Program Terms
Tab” on page 23.

•

Viewing the types and parameters of dynamic data that a Logbook user may collect;
see “Dynamic Data Tab” on page 25.

•

Viewing and controlling the Logbook user’s view of the major support tables;
see “Support Tables Tab” on page 27.

Data Feeds Tab
The Data Feeds tab contains options for configuring feeds from a GPS (see below) and depth
sounder (see “Depth sounder” on page 15).
GPS Setup
The GPS provides time and location information for the various fishing activities (sailing,
setting, hauling, landing, etc.). FLDRS uses data from the GPS to associate fishing events with
locations, so the fisherman does not have to enter positions manually.
FLDRS does not require a particular make or model of GPS, but the GPS device must receive
and transmit the NMEA 0183 sentences defined in the Sentences tab.
To set up a GPS for FLDRS, you need to connect the GPS to the computer running FLDRS,
and then configure the FLDRS application to read from the correct port, and to interpret the
NMEA sentences correctly.
You may write GPS data to a file by enabling GPS polling; see “GPS polling” on page 14. To
set up the GPS to work with FLDRS:
1. Start the FLDRS software and log in as an Administrator.
12

FLDRS Administrator’s Guide

2. Click the Software Setup button.
The Data Feeds tab shows information for setting up GPS communications. It controls
the format for entering latitude and longitude data manually, and the format for
showing time (in GMT/UTC or local time):
•

•

Normally, FLDRS uses a checksum to validate incoming GPS data. If the incoming
GPS data are corrupt, the invalid checksum prevents FLDRS from reading it. You
may turn off validation to allow such data to load.
Lat/Lon Format controls the way the fisherman enters positional information
when no GPS signal is available. Decimal minutes requires the latitude and
longitude in degrees, minutes, and thousandths of a minute. Seconds requires
the latitude in degrees, minutes, seconds, and hundredths of a second.

To set up communication between FLDRS and the GPS unit:
1. In the GPS Comm Port field, select the port where FLDRS listens for the input from the
GPS unit. To determine the correct COM port, use the Windows® Device Manager.
You can reach the Device Manager by starting the Windows Control Panel, doubleclicking on System, clicking the Hardware tab, and, finally, clicking the Device
Manager button. For Windows 7, use the Start menu’s Search Programs and Files box,
searching for Device Manager.
2. Next, click the Test Devices button. In the test window, click Test GPS. If you see a
stream of NMEA sentences in the test pane, the port is correct and you do not need to
change anything.
3. If you do not see a stream of GPS data, or you receive an Error opening port message,
change the COM port and try again. If you are certain that the COM port is correct,
check that the GPS device is turned on and the connection is working.

4. Check the list of GPS sentences in the test pane. Use this list to configure FLDRS to get
date, time, and position information from the GPS device; see “Sentences Tab” on page
20.

13

FLDRS Administrator’s Guide

GPS polling
FLDRS can be configured to poll the GPS unit at set intervals, and to write GPS and/or depth
sounder data to a file. To write data to the file, GPS polling must be turned on. By default, GPS
polling is turned off.
GPS polling starts when the user starts a trip and remains active until the user completes a trip
or exits from the Logbook.
To turn on GPS polling:
1. Start the FLDRS software and log in as an Administrator.
2. Click the Software Setup button.
3. In the Data Feeds tab, set the Enable GPS Polling option to On (polling active).
4. Set the desired interval between GPS observations in the polling file. A 20-second
polling frequency is recommended. Resolution can be decreased in post-processing, if
desired. Higher polling frequencies may lead to the over-estimation of distance
traveled.
Submitting the GPS polling file wirelessly
As of version 4.1.6, the GPS polling file can be submitted wirelessly if the computer has
strong WIFI signal. To enable this feature, switch the “Send GPS file” radio button to “Yes”.
The GPS polling file
When GPS polling is turned on, FLDRS writes the captured data to a file stored in the polling
file directory.
To set the directory where FLDRS stores GPS data:
1. Start the FLDRS software and log in as an Administrator.
2. Click the Software Setup button.
On the Data Feeds tab, the GPS Destination for Polling File field shows where FLDRS
saves the GPS data.
FLDRS does not write any data if GPS polling is turned off. The satellite communication
system does not automatically transmit the GPS polling file. This file must be manually
removed from the GPS polling directory.
The field format of the GPS polling file is:
DATE, TIME (GMT), LATITUDE, LONGITUDE, SPEED (KM/HR), COURSE (TRUE), FIX,
SAT_AVAIL, DEPTH (M), EFFORT_EVENT

Here is some sample data:
12/30/2015, 14:55:36, 4131.5610 N, 07040.4420 W, 000.0, 000.0, 2, 12, 0011.4,
12/30/2015, 14:55:56, 4131.5612 N, 07040.4422 W, 000.0, 000.0, 2, 12, 0011.3,
12/30/2015, 14:56:16, 4131.5611 N, 07040.4429 W, 000.0, 000.0, 2, 12, 0011.4,
12/30/2015, 14:56:20, 4131.5612 N, 07040.4431 W, 000.0, 000.0, 2, 12, 0011.5, End Set – Effort #2
12/30/2015, 14:56:36, 4131.5616 N, 07040.4432 W, 000.0, 000.0, 2, 12, 0012.5,
12/30/2015, 14:56:56, 4131.5615 N, 07040.4430 W, 000.0, 000.0, 2, 12, 0012.5,
12/30/2015, 14:57:16, 4131.5618 N, 07040.4424 W, 000.0, 000.0, 2, 12, 0012.3,
12/30/2015, 14:57:36, 4131.5619 N, 07040.4427 W, 000.0, 000.0, 2, 12, 0011.3,
12/30/2015, 14:57:56, 4131.5617 N, 07040.4428 W, 000.0, 000.0, 2, 12, 0012.4,
12/30/2015, 14:58:16, 4131.5613 N, 07040.4425 W, 000.0, 000.0, 2, 12, 0013.5,
12/30/2015, 14:58:36, 4131.5610 N, 07040.4419 W, 000.0, 000.0, 2, 12, 0013.4,

If no depth sounder is present, the depth readings in the GPS polling file are null.
14

FLDRS Administrator’s Guide

Depth sounder
FLDRS can receive data directly from the vessel’s depth sounder, if the depth sounder can
send data via a serial port to the computer running the FLDRS application. FLDRS does not
require a particular make or model of depth sounder. You must specify the sentence structure
of the incoming depth sounder feed; see “Sentences Tab” on page 19.
If no depth sounder is available, set the sounder option to Off. When it is off, the Logbook’s
depth sounder activity indicator shows no reading and FLDRS does not write depth
information to the GPS polling file.
In the Logbook’s Software Setup, the Defaults tab includes radio buttons to enable the depth
sounder. That Enable Depth Sounder option only affects whether the Average Depth field in
the Trip tab automatically gets a value from the depth sounder feed. If Enable Depth Sounder is
off, the fisherman must enter the depth fished manually. Typically, the Enable Depth Sounder
option is set to On for bottom fishing, and Off for midwater or other fisheries where fishing
depth should not be determined by bottom depth. FLDRS reads all depths from the depth
sounder in meters; though users may view the data as feet or fathoms, the values are converted
internally.
Setting up the depth sounder
To set up the depth sounder for FLDRS, add a serial port connection between the depth
sounder and the computer running FLDRS. Then set the FLDRS application to read depth from
that communications port.
To connect the depth sounder to the FLDRS application:
1. Connect the depth sounder and the computer running FLDRS and turn them both on.
2. Start the FLDRS software, log in as an Administrator, and click the Software Setup
button.
3. In the Depth Sounder Comm Port field, select the port where FLDRS listens for the
input from the depth sounder unit. To determine the correct COM port, use the
Windows® Device Manager. You can reach the Device Manager by starting the
Windows Control Panel, double-clicking on System, clicking the Hardware tab, and,
finally, clicking the Device Manager button. For Windows 7, use the Start menu’s
Search Programs and Files box, searching for Device Manager.
4. Click the Software Setup button. The Data Feeds tab shows depth sounder setup
information.
5. If desired, turn off checksum validation. Normally, FLDRS uses a checksum to validate
incoming depth sounder data. If the incoming data are corrupt, the invalid checksum
prevents FLDRS from reading it, so you may turn off validation to allow such data to
load.
6. Click the On (sounder active) radio button to activate depth sounder polling.
7. Select the correct COM port. If you are unsure of the correct port, either use Windows
Device Manager or start with COM1 and increment until you find the correct port:
•
•

•

Click the Test Devices button.
In the Test Serial Ports window, click the Test Sounder button. If you see a
stream of data displaying the $SDDBT sentence in the test pane, the port is
correct and you do not need to change anything.
If you do not see a stream of data, or you receive an Error opening port message,
click End Test and then Exit to close the test pane. Change the COM port
15

FLDRS Administrator’s Guide

•

number, and then try testing again.
If you are certain that the COM port is correct, check that the depth sounder is
turned on.

8. To check the format, click End Test after the test pane fills. If the results are not what
you expected, check the documentation for the device.
If you want to write depth data to the GPS polling file, turn GPS polling on; see “Data Feeds
Tab” on page 12.

Data Export Tab
The Data Export tab contains options for:
•

Trip transmission; see “Satellite communications and trip transmission” on page 17.

•

The electronic signing ceremony; see “Digital signing ceremony” on page 17.

•

File backup; see “Data backup” on page 18.

•

Transaction logging; see “Transaction logging” on page 18.

Choosing a satellite communications system
Transmission capabilities via Skymate have been temporarily suspended due to Skymate's
recent loss of certification in the Northeast Region.
FLDRS can use a satellite communications system to transmit a trip report. If no satellite
communications system is available, FLDRS can still operate, but trip data can’t be transmitted
at sea. Data transmission via satellite is facilitated through the Vessel Monitoring System
(VMS) and users are typically charged a transmission fee for this data transfer (contact the
vessel’s VMS vendor for specific costs).
Operating without a satellite communications system
If you select the None option, FLDRS makes no attempt to transmit the trip report. However,
the data file is archived as usual in the local backup directory; see “Data backup” on page 8.
You can remove the data manually from the computer using a USB drive or other memory
device.
Using a satellite communication systems
If you set up and select one of the satellite communication systems, FLDRS transmits the trip
report using one of these satellite communication systems.
First, install and configure the PC component of the satellite communication software on the
computer running the FLDRS application. Next, connect the physical satellite communication
unit to the computer running FLDRS, or network the FLDRS and the satellite communication
computers together. Finally, start FLDRS and set the options for the satellite communications
system.
Setting up FLDRS to use a satellite communication system
To have the FLDRS software send data to McMurdo FMCT/G (formerly Boatracs) or SkyMate:
1. Start FLDRS and log in as an Administrator.
2. Click the Software Setup button.
3. On the Data Export tab, set the Satellite Communication System to McMurdo
FMCT/G or SkyMate.
4. Set the satellite communications and trip transmission options:
16

FLDRS Administrator’s Guide
•

Check that the file destination for the export file is correct for the satellite
communications system you selected. For McMurdo FMCT/G,
C:\WBUI\OutBox is usually appropriate. For SkyMate, it is usually
C:\NEFSC\FLDRS\LocalBackup.

•

Check that the recipient address matches the email address provided by your
Program Administrator. The default email address is [email protected]; if this is
incorrect, change the Recipient Address field, described below.

5. For Skymate transmission, the computer's network must be connected to the Skymate
receiver via the password on the Skymate device.
6. You can verify transmission success by contacting your logbook administrator.
Satellite communications and trip transmission
When the fisherman clicks the Export Trip button, FLDRS writes an export file to the local
disk, compresses the file, and places this file in the appropriate directory for the satellite
communications system that you selected; see “Choosing a satellite communications system”
on page 16. The data file is not sent until the satellite communications system software is
launched.
To set options for the data export file:
1. Start the FLDRS software and log in as an Administrator.
2. Click the Software Setup button.
3. On the Data Export tab, four fields influence the satellite communications system
transmission:
•
•

•

The Destination for Export File field shows where FLDRS writes the export
file. Although FLDRS offers this directory as a default, it can be changed.
The Recipient Address field shows the email address where the satellite
communications system sends the export file. If you select the None option on
the Satellite Comm Tab, FLDRS does not send the export file. The recipient
address can be changed from the default.
The Compression Executable Path shows the program used to compress the trip
data file before transmission.

Digital signing ceremony
For compliance with electronic Vessel Trip Reporting (eVTR) technical requirements, FLDRS
includes an optional digital signing ceremony.
To require a user to complete the signing ceremony, check the Enable eVTR digital signing
ceremony box.
When the user completes the ceremony, FLDRS writes a secure copy of the trip data to the
directory specified in Destination for Secure File.
NMFS-supplied passwords
During the signing ceremony, the operator enters a NMFS-supplied password twice, correctly.
The password must be between 8 and 12 characters long and must contain:
•
•
•

At least one (1) capital alpha.
At least one (1) lower case alpha.
At least one (1) numeric.
17

FLDRS Administrator’s Guide
•

At least one (1) special character from the following list:
~ ! @ # $ % ^ & * ( ) _ - + = { } [ ] \ | : ; < > , . ? /.

If the first password entry does not match the second password entry, or the passwords
entered do not match the specified format, the user receives an error message.
FLDRS does not validate the entered passwords against the NMFS password of record. It only
checks to make sure the two passwords conform to the standards and match. More stringent
password validation occurs on the NMFS servers after receipt of the trip report.

Data backup
When the fisherman clicks the Export Trip button on the Transmit tab, FLDRS automatically
backs up the user and administrator configuration, trip data, and transmission data to flat files.
To set the directory where FLDRS backs up this data:
1. Start the FLDRS software and log in as an Administrator.
2. Click the Software Setup button.
3. On the Data Export tab, the Data Backup (export to local drive) field shows where
FLDRS backs up the trip (*.gpg) files. This directory appears by default when the
fisherman transmits a file, but the fisherman may override it. The folder where
FLDRS backs up the user and administrator configuration, trip data, and
transmission data is set in the System Backup section of the Data Export tab.
4. Choose a time interval between automatic backups by selecting it from the Backup
Frequency dropdown menu.
You can also back up data manually; see “System data backup” on page 11.

Transaction logging
Administrators can track users’ FLDRS activity by writing to a transaction log file each time
the user visits a module.
To write data to the file, transaction logging must be turned on. By default, transaction
logging is turned off.
Transaction logging starts when the user logs in, and remains active until the user exits from
the Logbook. You can view the transaction log file; see “View the transaction log” on page
33.
To turn on transaction logging:
1. Start the FLDRS software and log in as an Administrator.
2. Click the Software Setup button.
3. Click the Data Export tab.
4. Set the Enable Logging of Transactions option to On (logging active). To set the
directory where FLDRS stores transaction logging data:
5. Start the FLDRS software and log in as an Administrator.
6. Click the Software Setup button.
7. On the Data Export tab, the Destination for Logging File field shows where FLDRS
saves the transaction data.

18

FLDRS Administrator’s Guide

GNU Encryption
In order to encrypt a trip file, you must set the GNU Executable Path. To set the path:
1. Use the Browse button to navigate to the location where the GNU software is installed,
select the folder, and click Open.
2. Switch to another tab and then back to the Data Export tab to make sure the file path is
set.
3. Click the Setup Encryption button to configure GPG. You are prompted for the same
parameters you gave in the installation: 5, y, quit.

Configure Email
Click on the Configure Email button. By default, “Send Trip Files” is set to “No”. If wireless
trip transmission is desired, select “Yes”.
Note: If during the export process, the computer does not have an internet connection, trips will
not be sent. The trip file will be archived in the backup folder and can then be sent by going to
“Managed Trips”, selecting the trip, clicking on “Transmissions”, then clicking on “Email Trip”.
To submit data over the internet, FLDRS must be configured with a user’s valid email username
and password.
The SMTP host name must be entered. For example, Gmail accounts would use
“SMTP.gmail.com”. A list of common host values can be found by clicking on the

.

A valid Port must be selected. Most often the port will be “587”. But if that value does not
work, a list of other values is listed.
It is recommended that users test the email functionality by clicking on “Send test email”.
Note: Gmail users may need to configure email settings to 'allow access for less secure apps'.
GMAIL: Settings  Accounts and Import  Other Google Account settings  Connected apps
& sites (under Sign-in & security) 
Switch the 'Allow less secure apps' toggle to 'ON'
Note: Submission via email can be inhibited by the computer’s anti-virus software (if installed).
If this occurs, FLDRS will need to be added to the list of programs approved by the anti-virus
software. This process depends on the specific anti-virus software installed.
For computers with McAfee anti-virus, open the VirusScan Console. Right-click on “Access
Scan” and select “Properties”.

19

FLDRS Administrator’s Guide

On the “Access Protection” tab, highlight “Prevent mass mailing worms from sending mail” and
select “Edit”.

In the “Processes to exclude” section, add “FLDRS.exe” to the list. Make sure there is a comma
afterwards if not inserted at the end of the list. Click OK when finished.

20

FLDRS Administrator’s Guide

Sentences Tab
Use this tab to set up the NMEA sentences that FLDRS expects to receive from the GPS unit.
For each string in the Sentence Type list on the left, define the content on the right.
Many of the sentences contain duplicate information, but the FLDRS software scans all these
sentences so that it can accommodate a variety of GPS units. If duplicate information is
provided, FLDRS takes the information from the first available sentence.
At a minimum, FLDRS requires sentences that provide the date, time, latitude, longitude, and the
fix strength value. The optional values include the number of satellites in view (and indicator
for the quality of fix), the course (true), the speed (knots), and the depth (m). If you select a
depth sentence that requires an offset to record true bottom depth (m), then you should record
the offset value in the Depth Correction (m) position. For example, if you use the $SDDBT
(depth below transducer) sentence to record bottom depth, and the transducer sits two meters
below the surface, you would set the Depth Correction (m) value to 2.
FLDRS saves the NMEA string data you enter here in the Sentences table. You can propagate
the sentence settings to other FLDRS applications by exporting the Sentences table to a file
using Table Import, copying the exported file to the other computer, and then importing the file
into FLDRS on the other computer; see “Table Import” on page 8.

21

FLDRS Administrator’s Guide

Users Tab
An Administrator can add, delete, or change privileges for all users. The Administrator can
also set passwords. A FLDRS user may have either Administrator privileges or Logbook
privileges.
Changing user access privileges
To change access privileges for a FLDRS user:
1. Start the FLDRS software and log in as an Administrator.
2. Click the Software Setup button.
3. Click the Users tab.
4. In the list on the left, highlight the user name. The properties of that user name
appear on the right.
5. Use the radio buttons to control access to the FLDRS modules.
FLDRS saves the changes when you click on another user name in the list, click New User,
click on another tab, or click Exit Setup.
Adding a new user
When you add a new user, you must provide a password for the user and set access privileges.
User passwords must contain at least eight numbers or letters. At least one character must be a
non-numeric special character (!, $, &). It is strongly suggested that the FLDRS login differ
from the NMFS-supplied electronic VTR password; see ‘Digital signing ceremony’ on page 17.
To add a new user:
1. Start the FLDRS software and log in as an Administrator.
2. Click the Software Setup button.
3. Click the Users tab.
4. Click the New User button at the bottom of the window.
5. Complete the fields to give a name and password to the new user.
6. Use the radio buttons to control access to the FLDRS modules.
FLDRS saves the changes when you click on another user name in the list, click New User
again, click on another tab, or click Exit Setup.
Deleting a user
You can delete any user except the last established Administrator. There must always be one
FLDRS Administrator on record, to avoid accidentally locking Administrators out of FLDRS.
To delete a user from FLDRS:
1. Start the FLDRS software and log in as an Administrator.
2. Click the Software Setup button.
3. Click the Users tab.
4. In the list on the left, highlight the user name. The properties of that user appear on the
right.
5. Click the Delete User button at the bottom of the window.
6. Click Yes to confirm the deletion, or No to cancel. You cannot delete the last
Administrator account.
22

FLDRS Administrator’s Guide

Program Terms Tab
FLDRS uses fishery programs to set up and control options for collecting effort data in the
Logbook. The programs are flexible, so they can meet the various data collection requirements
that may exist across fleets, vessels, and gears. Within each program, different data collection
rules can apply to different gear types. A vessel may participate in only one program per trip,
and must be granted access to participate. The eVTR Database Administrator sets the data
collection rules for the program. The rules cannot be changed using the FLDRS application,
but you can view them using the Program Terms tab.
The Program Terms tab shows the list of vessels that participate, the list of gear types used in the
program, the gear handling events that the program collects (see “Gear handling events” on page
24), and its gear parameter rules (see “Gear parameter rules” on page 24).
Using the Program Terms tab
The upper left side of the Program Terms tab lists the valid programs. Clicking on a program
shows the details of the program. The vessels that may participate in that program appear on the
upper right, and the gears that those vessels may use on the lower left. Clicking on a gear name
shows the data collection rules for that particular gear type within the selected program. Gear
can be used in different programs, with different data collection rules in each program.

Example program

Here is an explanation of the program in the example:
•

The eVTR Database Administrator creates the program named Generic Haul by Haul.

•

The eVTR Database Administrator grants access to the program for two vessels,
F/V Stella Blue and F/V Tennessee Jed.

•

FLDRS lists the allowed gear types for the F/V Stella Blue and the F/V Tennessee Jed
based on the program code.

•

FLDRS displays which gear events and gear parameters are collected based of the
vessel and program selected. These values are set by the support tables and cannot be
altered.
23

FLDRS Administrator’s Guide

Gear handling events
A program can collect data for four gear-handling events, these options are set by the database
based on vessel and program code.
•

Set—Start: the user must provide the time, date, and position when the vessel starts to
set the gear, by clicking the Set—Start button on the Effort tab.

•

Set—End: the user must provide the time, date, and position when the vessel finished
setting the gear, by clicking the Set—End button on the Effort tab.

•

Haul—Start: the user must provide the time, date, and position when the vessel began
to haul the gear, by clicking the Haul—Start button on the Effort tab.

•

Haul—End: the user must provide the time, date, and position when the vessel finished
hauling the gear, by clicking the Haul—End button on the Effort tab.

Gear parameter rules
These options are set by the database based on vessel and program code.
•

Override Gear Size: the user can specify a different gear size in the Effort tab.

•

Override Gear Quantity: the user can specify a different gear quantity in the Effort
tab.

•

Override Mesh Size: the user can specify a different mesh size in the Effort tab.

•

Override Mesh Type: the user can specify a different mesh type in the Effort tab.

•

Calculate Soak Duration: the Logbook automatically calculates the soak/haul duration
for a particular haul. This option is available if the program collects both the Set—End
and Haul—Start events.

•

Haul-by-haul recording enabled: each haul is recorded as a separate effort. The Number
of Hauls field does not appear, and FLDRS sets that field’s value to 1 for each effort
record.

24

FLDRS Administrator’s Guide

Dynamic Data Tab
FLDRS allows fishermen to provide data that extend beyond the Logbook’s core set of data
elements. These data are flexible in nature, and can vary from program to program, so they are
referred to as dynamic data. The eVTR Database Administrator sets up the dynamic data
collection rules, which cannot be changed within the FLDRS application. However, you can
view the rules.
Use the Dynamic Data tab to view the dynamic data elements collected for a particular
program. The list on the bottom left of the window shows all the programs defined in the
Program Terms tab. Click on a program name to see the dynamic data elements it collects. The
attributes of that element appear in the top half of the window. If an element lets the user make
a choice, clicking on the element name shows those choices on the lower right side of the
window.
Example of dynamic data rules

This window shows the Generic Haul by Haul program. The Observed Trip dynamic data
element is highlighted, and the user’s possible choices appear on the lower right side of the
window.
Here is an explanation of the dynamic data collection elements in this example:
•
•

•

The program type is selected in the list on the lower left.
The dynamic data elements collected for the selected program appear in the top half of
the window, along with their attributes. For example, FLDRS collects the Observed
Trip element at the trip level (the fisherman enters it once for the entire trip). The
other attributes of this element control how it is stored within the FLDRS database.
For example, Observed Trip is a required element (the Req? attribute is set to Yes). In
the dialog box that prompts the fisherman for dynamic data at the trip level, Observed
Trip is the second item (the Seq attribute is set to 2). For a complete list of attributes
and their meanings, see below.
The list of possible values for the Observed Trip element appears on the lower
right. This element is a lookup list, and the user can choose No or Yes.
25

FLDRS Administrator’s Guide

Attributes of the dynamic data elements
Here is a complete list of the attributes for a dynamic data element.
Field
Name of
Element
Type of
Gear

Level
Data Type
Max Len
Dec Len
Min Val

Meaning
The name of the dynamic data element. In the Logbook, the name labels the field where
the fisherman enters the data.
The gear types for which this data is collected.
The data element applies only to the gear listed in this attribute. If this attribute is blank,
then the element applies to all efforts, regardless of gear type. This option is only available
for dynamic data collected at the Effort level.
When the element is collected (Trip, Effort, Retained/Discarded, Landing,
Apportionment). The level corresponds roughly to the major functions (tabs) of the
Logbook.
Either numeric (NUMBER) or character (VARCHAR).
The maximum number of characters or numbers that the user may enter for the element.
For numeric data elements, the level of decimal precision for the collected data.
For numeric data elements, the minimum value of the acceptable range of values. If the
user enters a value below the minimum, FLDRS warns the user in an informational
message. The user can override the warning.

Max Val

For numeric data elements, the maximum value for the acceptable range of values. If the
user enters a value greater than the maximum, FLDRS warns the user in a message. The
user can override the warning.

Req?

Whether the data element is required or optional. If the element is required, the user
cannot complete the trip without entering a value for the element.

Seq #

The sorting order for the elements. Elements appear on the entry dialog box in ascending
order; lower sequence numbers appear nearer the top of the dialog box.

You cannot edit the dynamic data in this window. If changes are needed to the dynamic data,
consult the eVTR Database Administrator. If changes are made, load the updates; see “Table
Import” on page 8.

26

FLDRS Administrator’s Guide

Support Tables Tab
Use the Support Tables tab to see the contents of the tables listed vertically on the right side of
the window.
For any support table in this tab, you can hide irrelevant entries from the Logbook user by
clicking on the values in the Display? field. A Logbook user can select any record that has
a display value of True. Records with the Display? value False do not appear in the
Logbook.
If you need to reload a support table, see “Reloading a support table” on page 10.
Operators Tab
The Operators tab shows the full list of operators available to Logbook users. You cannot edit
the list of operators, or change any values for a particular operator.
However, you can control the list of operators that the Logbook user sees. All operators with
the Display? attribute set to True appear in the Operators tab of the Logbook’s Software Setup.
To modify the list of operators available in the Logbook:
1. Start the FLDRS software and log in as an Administrator.
2. Click the Software Setup button.
3. Click the Support Tables tab.
4. On the right side of the window, click the Operators vertical tab.
The list shows all the operators in the table. The record for each operator includes a
display property, which controls whether the operator name is visible to the fisherman.
If the display property is set to True, the fisherman sees that operator in the Operator
tab of the Logbook’s Software Setup.
5. To change the display property for an operator, double-click on its Display? field. The
display state toggles between True and False.
6. Repeat the previous step for every operator you wish to exclude from the fisherman’s
view.
Your choices are saved when you click on another tab, or click the Exit Setup button.
Before using the Logbook to enter trip data, check that the operator list is appropriate for the
specific installation. Start FLDRS, and log in to the Logbook. In the Logbook’s Software Setup,
click the Operator tab, and make sure that the desired operator(s) is available.
Vessels Tab
The Vessels tab shows the full list of vessels available to users of the Logbook. You cannot
edit the list of vessels, or change the values for a particular vessel.
However, you can control the list of vessels that the Logbook user sees in Software Setup. All
vessels with the Display? attribute set to True appear in the Vessels tab of the Logbook’s
Software Setup.
To modify the list of vessels available through the Logbook:
1. Start the FLDRS software and log in as an Administrator.
2. Click the Software Setup button.
3. Click the Support Tables tab.
4. On the right side of the window, click the Vessels vertical tab.
27

FLDRS Administrator’s Guide

The list shows all the vessels in the table. The record for each vessel includes a display
property, which controls whether the vessel name is visible to the fisherman. If the
display property is set to True, the fisherman sees that vessel in the Vessels tab of the
Logbook’s Software Setup.
5. To change the display property for a vessel, double-click on its Display? field. The
display state toggles between True and False.
6. Repeat the previous step for every vessel you wish to exclude from the fisherman’s
view.
FLDRS saves your choices when you click on another tab, or click the Exit Setup button.
Before using the Logbook to enter trip data check that the vessel list is appropriate for the
specific installation. Log in to the Logbook, and use the Logbook’s Software Setup. In the
Vessel tab, make sure that the desired vessel(s) is available.
Species Tab
The Species support table stores the full list of species that FLDRS can make available to
Logbook users. Because the list is very long, the Administrator can (and should) use the
Species tab to hide irrelevant species from the fisherman.
You can control the species names that the Logbook user sees when adding and deleting
species, or setting up species lists. Only species with the Display? attribute set to True appear in
the user’s lists of species.
To modify the list of species that appear in the Logbook:
1. Start the FLDRS software and log in as an Administrator.
2. Click the Software Setup button.
3. Click the Support Tables tab.
4. On the right side of the window, click the Species vertical tab.
The list shows all the species in the table. The record for each species includes a display
property, which controls whether the species name is visible to the fisherman. If the
display property is set to True, the fisherman sees that species in the lists in the
Logbook’s Software Setup.
5. To change the display property for a species, double-click on its Display? field. The
display state toggles between True and False.
6. Repeat the previous step for every species you wish to exclude from the fisherman’s
view.
FLDRS saves your choices when you click on another tab, or click the Exit Setup button.
TIP: To restrict your view to a particular category of species, click the
dropdown list next to the All Categories button at the top of the window.
Selecting an item from the dropdown list restricts the list in the main
window to show only species in that category.
Before using the Logbook to enter trip data check that the species list is appropriate for the
specific installation. Log into the Logbook, and use the Logbook’s Software Setup. In the
Species List tab, click the Add Species button to see the list of species that the fisherman can
select.
Gear Tab
The Gear tab shows the full list of gear types available to users of the Logbook. You cannot
28

FLDRS Administrator’s Guide

edit the list of gear types, or change the values for a particular gear type.
However, you can control the list of gear types that the Logbook user sees in Software Setup. All
gear types with the Display? attribute set to True appear in the Gear tab of the Logbook’s
Software Setup.
To modify the list of gear types available through the Logbook:
1. Start the FLDRS software and log in as an Administrator.
2. Click the Software Setup button.
3. Click the Support Tables tab.
4. On the right side of the window, click the Gear vertical tab.
The list shows all the gear types in the table. The record for each gear type includes a
display property, which controls whether the gear type is visible to the fisherman. If the
display property is set to True, the Logbook user sees that gear type in the Gear tab of
the Logbook’s Software Setup.
5. To change the display property for a gear type, double-click on its Display? field. The
display state toggles between True and False.
6. Repeat the previous step for every gear type you wish to exclude from the Logbook
user’s view.
FLDRS saves your choices when you click on another tab, or click the Exit Setup button.
Before using the Logbook to enter trip data, make sure that the gear list is appropriate for the
specific installation. Log into the Logbook, and use the Logbook’s Software Setup. In the Gear
tab, the list on the upper right shows all the types of gear that the Logbook user can select.
TIP: To restrict your view to a particular category of gear, click the
dropdown list next to the All Categories button at the top of the window.
Selecting an item from the dropdown list restricts the list in the main
window to show only gear in that category.
Dealers Tab
The Dealers tab shows the full list of dealers available to users of the Logbook. You cannot
edit the list of dealers, or change the values for a particular dealer.
However, you can control the list of dealers that the Logbook user sees in Software Setup. All
dealers with the Display? attribute set to True appear in the Dealers tab of the Logbook’s
Software Setup.
To modify the list of dealers available through the Logbook:
1. Start the FLDRS software and log in as an Administrator.
2. Click the Software Setup button.
3. Click the Support Tables tab.
4. On the right side of the window, click the Dealers vertical tab.
The list shows all the dealers in the table. The record for each dealer includes a
display property, which controls whether the dealer name is visible to the Logbook
user. If the display property is set to True, the fisherman sees that dealer in the
Dealers tab of the Logbook’s Software Setup, and also when apportioning species in
the Landings tab.
5. To change the display property for a dealer, double-click on its Display? field. The
29

FLDRS Administrator’s Guide

display state toggles between True and False.
6. Repeat the previous step for every dealer you wish to exclude from the fisherman’s
view.
FLDRS saves your choices when you click on another tab, or click the Exit Setup button.
Before using the Logbook to enter trip data, check that the dealer list is appropriate for the
specific installation. To review the names of the dealers, log in to the Logbook, click Software
Setup, and then the Dealers tab.
Ports Tab
The Ports tab shows the full list of ports available to users of the Logbook. You cannot edit
the list of ports, or change the values for a particular port.
However, you can control the list of ports that the Logbook user sees in Software Setup. All
ports with the Display? attribute set to True appear in the Ports tab of the Logbook’s Software
Setup.
To modify the list of dealers available through the Logbook:
1. Start the FLDRS software and log in as an Administrator.
2. Click the Software Setup button.
3. Click the Support Tables tab.
4. On the right side of the window, click the Ports vertical tab.
The list shows all the ports in the table. The record for each port includes a display
property, which controls whether the port name is visible to the fisherman. If the
display property is set to True, the fisherman sees that port in the Ports tab of the
Logbook’s Software Setup.
5. To change the display property for a port, double-click on its Display? field. The
display state toggles between True and False.
6. Repeat the previous step for every port you wish to exclude from the fisherman’s view.
FLDRS saves your choices when you click on another tab, or click the Exit Setup button.
Before using the Logbook to enter trip data, check that the port list is appropriate for the
specific installation. Log in to the Logbook, and use Software Setup. In the Ports tab, review
the names of the ports.
Dispositions Tab
The Dispositions tab shows the full list of dispositions for the retained, discarded, and
apportioned catch that are available to users of the Logbook. Fishermen use the dispositions to
describe the fate of the fish.
You cannot edit the lists of dispositions, move them between categories, or change the values
for a particular disposition.
However, you can control the list of dispositions that the fisherman sees in the Logbook’s
Software Setup. All dispositions with the Display? attribute set to True appear in the
Logbook’s Landings tab, and also in the Logbook’s Species List tab.
To modify the list of dispositions that are available through the Logbook:
1. Start the FLDRS software and log in as an Administrator.
2. Click the Software Setup button.
3. Click the Support Tables tab.
30

FLDRS Administrator’s Guide

4. On the right side of the window, click the Dispositions vertical tab.
The list shows all the dispositions in the table, for kept species, discarded species, and
for landing apportionment. The record for each disposition includes a display property,
which controls whether the disposition is visible to the fisherman. If the display
property is set to True, the fisherman can use that disposition code in the Logbook.
5. To change the display property for a disposition, double-click on its Display? field. The
display state toggles between True and False.
6. Repeat the previous step for every disposition you wish to exclude from the
fisherman’s view.
FLDRS saves your choices when you click on another tab, or click the Exit Setup button.
Before using the Logbook to enter trip data, check that the dispositions in the species list are
appropriate for the specific installation. Log in to the Logbook, and use Software Setup. In the
Species Lists tab, double-click on any Disposition field to see the list of disposition codes.
Areas Tab
The Areas tab shows the full list of statistical areas. You cannot edit the lists of areas or
change the values for a particular area.
However, you can control the list of areas that the Logbook user sees in Software Setup. All
statistical areas with the Display? attribute set to True appear in the Logbook’s Effort tab.
To modify the list of statistical areas available in the Logbook:
1. Start the FLDRS software and log in as an Administrator.
2. Click the Software Setup button.
3. Click the Support Tables tab.
4. On the right side of the window, click the Areas vertical tab.
The list shows all the statistical areas defined in the table. The record for each area
includes a display property, which controls whether the area is available to the
fisherman. If the display property is set to True, the fisherman can report catch made in
that statistical area in the Logbook.
5. To change the display property for a statistical area, double-click on its Display? field.
The display state toggles between True and False.
6. Repeat the previous step for every statistical area you wish to exclude from the
fisherman’s view.
FLDRS saves your choices when you click on another tab, or click the Exit Setup button.
Before using the Logbook to enter trip data, check that the species list is appropriate for the
specific installation. Log in to the Logbook, and begin a trip. In the Effort tab, click on the Stat
Area field and review the list of statistical areas.

Setting User Defaults
A fisherman cannot record any trips until defaults are set up. Log in to the Logbook and use
Software Setup to configure the defaults; see the FLDRS user manual for instructions.

31

FLDRS Administrator’s Guide

Manage Trips
Use Manage Trips to view old trips, reports, back up trip data, and view the transaction log.

View or print trip reports
FLDRS keeps one saved trip and all recently transmitted trips. The transmitted trips can’t be
edited.
To view an old trip report:
1. On the main FLDRS window, click the Manage Trips button. A list of trips appears.
2. Highlight the trip report and then click the View Reports button.
3. FLDRS gives you options to:
•

View the trip report in a format similar to a paper VTR.
• Save it as an Adobe PDF file.
• View a catch summary, which lists the hail weights of all the species recorded
during a particular period of time. It includes catch data from all completed
trips in the date range, along with the current trip.
4. Choose a report type and click the OK button. For the catch report, FLDRS prompts you
to select a range of dates. The report includes amounts for all the species you kept and
discarded for all trips during the range of dates you selected.

Delete old trips
Only an Administrator can delete trips.
The delete trip function is intended to remove test/training/corrupt/garbage trips from the
system. Deletion of valid fishing trips will also remove all ‘legal’ records of those trips on
board the vessel, if the vessel is boarded by USCG they will be out of compliance and the
vessel could be fined.
In making the decision to delete a trip, keep in mind that the data from a
deleted trip is no longer available for analysis and compliance.
To delete old trips:
1. Log in as an Administrator, and click the Manage Trips button. A list of trips appears.
2. Highlight the trip report and then click the Delete Trip button. When you click Yes on
the warning message, FLDRS deletes the trip report from the database. Repeat this step
to delete another trip.
3. Click the Exit button when you are done.

Retransmit or re-export a trip
If a trip report that was transmitted using a satellite communication system fails to reach its
destination, you can retransmit the report. FLDRS just resends the encrypted file stored in the
backup folder. However, if that encrypted file is corrupted or cannot be found, you can reexport it, which regenerates the report from the database and then transmits it.
For partial trips, the Trip Exported? field always records No, regardless of the transmission
status.
To retransmit a report:
1. Make sure that the satellite communication system software has been launched and is
running properly.
32

FLDRS Administrator’s Guide

2. On the main FLDRS window, click the Manage Trips button.
3. Highlight the trip to resend and click the Transmissions button. A list of trips appears,
along with their status.
4. Click the Re-Transmit button.
FLDRS reports that the data has been resent. However, since it relies on the satellite
communication system software, the actual transmission may not occur instantly. If the
trip report is not received, see “Troubleshooting” on page 34.
To re-export a report:
1. Make sure that the satellite communication system software has been launched and is
running properly.
2. On the main FLDRS window, click the Manage Trips button.
3. Highlight the trip to resend and click the Transmissions button. A list of trips appears,
along with their status.
4. Click the Re-Export button.
FLDRS rebuilds the trip report by querying the database. It may prompt you to enter
and confirm a NMFS-supplied password, (see “Digital signing ceremony” on page 17),
and then report that the data has been resent.
However, since FLDRS relies on the satellite communication system software, the
actual transmission may not occur instantly. If the trip report is not received, see
“Troubleshooting” on page 34.
View a list of transmitted trips
If a fisherman transmitted a trip report, you can view the transmission history for that trip. For
each trip, the Transmission History dialog box gives the date and time of transmission, along
with summary data to help you identify a particular trip.
To see the transmission history, highlight the trip and click the Transmissions button. The
Transmission History dialog box appears.
If a complete trip was transmitted only once (there were no partial trips), the top section shows
a single record for the transmission, with the middle and bottom sections listing the efforts and
landing records for that transmission.
If there were partial transmissions for the trip, the top section lists all the partial trip
transmissions. Selecting a partial trip transmission in the top section fills the middle and bottom
sections with the effort and landing records sent in that partial trip transmission.
To send a trip report again, highlight the vessel in the list at the top of the dialog box, and then
click the Retransmit button.
If the trip report is not received, see “Troubleshooting” on page 34.
View the transaction log
Administrators can track users’ FLDRS activity by writing to a transaction log file each time
the user visits a module. Transaction logging starts when the user logs in, and continues until
the user exits from the Logbook.
To view the transaction log for a trip, highlight its name in the Manage Trips window, and
click Transaction Log. You can view, back up, or clear the log file using the buttons on the
Transaction Log window.
To turn logging on or off, see “Data Export Tab” on page 16.
33

FLDRS Administrator’s Guide

Troubleshooting
GPS status says “GPS Signal: GPS Off”
FLDRS is not receiving a signal from the GPS.
First, log out of the logbook, but don’t click the Exit button on the FLDRS home page. Click
the Login button on the home page. Logging back in should reinitiate the GPS connection if the
software dropped the connection.
If that doesn’t work, check the GPS feed; make sure the GPS unit is turned on and then check
cables and connections.
Physically unplug the USB cable that connects the GPS unit to the computer, and then plug it
back in to force the computer to reset the port.
Finally, try restarting the computer that is running FLDRS.
If necessary, have the fisherman use the globe icons on the Effort tab to enter the locations
manually.

Jumping cursor when GPS is connected
Microsoft® has discovered a jumping cursor problem, caused by a Windows® bug that detects
a connected GPS as a mouse. Microsoft support supplied these directions to correct the
problem:
1. Turn off the GPS and close the mapping software.
2. Right-click on the My Computer icon and select Properties.
3. Select the Hardware tab, and click the Device Manager button.
4. Next to "Mice and other pointing devices," click the plus (+) button to expand this list.
You should see at least two items listed. One is the mouse you normally use, and the
other is probably listed as "Microsoft Serial Ball Point."
5. Highlight “Microsoft Serial Ball Point” and click the Disable button at the top of the
window (it is usually the second button from the right; hover the cursor over it and
read the ToolTip to verify)
6. In the confirmation message window that appears, click Yes.
7. Close the Device Manager.
8. Plug in and turn on your GPS.
9. Restart the mapping software.

Depth sounder says FA but no depth values appear
FLDRS is not receiving a signal from the depth sounder.
First, log out of FLDRS, but don’t click the Exit button on the FLDRS home page. Click the
Login button on the home page. Logging back in should reinitiate the depth sounder
connection if the software dropped the connection.
If that doesn’t work, check the depth sounder feed; make sure the unit is turned on, and then
check cables and connections.
Finally, try restarting the computer that is running FLDRS.

Exported files do not arrive when using SkyMate®
If a file does not arrive at the email address specified in the Data Export tab, try these steps:
34

FLDRS Administrator’s Guide

1. Open the directory you specified in the Destination for Export file field and look for the
file. The file is named with the trip ID and the extension ENC (e.g.,
12345606051009.enc). SkyMate prefixes a sent file with SENT…, so if your file lacks
that prefix, SkyMate has not recognized it yet.
2. Make sure the SkyMate software is running on the computer running the FLDRS
application. You can only transmit files from the FLDRS to the SkyMate unit if
both FLDRS and SkyMate are running on the same computer.
3. If the SkyMate software is running and the file still has not been renamed with the
SENT… prefix, check the communication with the SkyMate unit. Files can only be
renamed if the PC can communicate with the SkyMate unit.
4. If the file has been renamed with the SENT prefix but has not been received, check the
email outbox, usually C:\Program Files\skymate\outbox. Any messages listed in the
email outbox are pending delivery. They remain in the outbox until the SkyMate unit
receives confirmation from SkyMate that the messages have been received.
5. If the file has been renamed in the dropbox and is not listed in the outbox, check the
sent directory, usually C:\Program Files\skymate\sent. If the message is listed in this
directory, it has left the transmit queue and has been sent from the system.
6. If the file is not listed in the outbox, check the inbox. Occasionally, SkyMate may send
an email back to the unit if an email cannot be transmitted. This may happen if the
SkyMate unit was powered down before the file could be fully transmitted.

Exported files do not arrive when using McMurdo FMCT/G (formerly
Boatracs®)
If the file does not appear in the recipient inbox, try these steps:
1. Check that WBUI’s long file name command is active. FLDRS uses the 14-character
trip ID in its file names.
2. Open the C:\WBUI\OutBox\ directory and look for the filename. The file name has 14
characters and ends in _outer.zip (for example, 12345609031815_1_outer.zip). If the file
is still in the main C:\WBUI\OutBox\ directory, it has not yet been sent to the FMCT
unit.
3. Make sure the WBUI software is running. You can only transmit files from the PC to the
FMCT unit if WBUI is running.
4. Another Boatracs requirement which may cause transmission issues is activation of the
Boatracs MCT data port. This can only be performed by contacting Boatracs directly,
the data port on the MCT unit is locked by default, and will remain so unless Boatracs
is contacted regarding unlock of the port to facilitate the submission of VTR data via
Boatracs MCT.
5. If WBUI is running and the file has not moved to any of the three subfolders, check the
directory scan rate. In the WBUI software, choose Options, Configuration and set the
Check for files to send automatically every _ minute to 1 (one).
6. If the file is not in the main C:\WBUI\OutBox\ directory, check the badfile folder. If the
file is here, then there is something wrong with the file. McMurdo FMCT/G does not
send files larger than 20KB, so check the file size. If the file is less than 20KB, doublecheck the wbui.ini file again and make sure enablelongfilenames=1.
7. If the file is not in the badfile folder, check the nak_sav folder. If the file is there, check
the File Segment reading in the WBUI software. If the value is not 0 (zero), the file is in
35

FLDRS Administrator’s Guide

the process of being transmitted. Satellite communications may be poor in the particular
location, and the antenna may have trouble establishing a strong connection. Check the
M0 reading on the MCT unit. In the New England area, the M0 reading should be > 15.
8. If the file is not in the nak_sav folder, check the files folder. If the file is there, it has
probably already been transmitted. Check the sent message directory (In the WBUI
application, choose Send, Sent Message Directory). If the file is in the files directory, it
has been sent to McMurdo FMCT/G.
9. Open the sent message directory by choosing Send, Sent Message Directory. Check the
Stat column in the list. If the status is ACKD, the message has been received by
McMurdo FMCT/G and the MCT unit has received confirmation of its receipt. Other
possible status are: PEND (the message is being sent to the MCT unit); and SENT (the
message has been transmitted, but confirmation of its receipt has not yet been
received).
10. If the file is listed as ACKD but does not show up in the recipient account, or if its
status remains SENT for a long period of time, the file may not have been received by
McMurdo FMCT/G in its entirety, or the vessel’s account may not be set up to transmit
data files to the recipient email account. Call McMurdo FMCT/G technical support, and
be sure to have the vessel’s MCT unit number ready. The phone number for the 24-hour
Networks Operations Center is 1-800-262-8722.
The MCT number appears on WBUI’s main window. To see it on the LCD display, press
View Status and then the Down button.

36

FLDRS Administrator’s Guide

FLDRS Error Messages
Message

Solution

A previous transmission exists for
this trip. Deleting this trip will
require completion of the signing
ceremony
Signing ceremony failed

Because data from this trip has already been
transmitted, the signing ceremony must be performed
again to confirm trip deletion. The deletion notice that
is generated must be transmitted to GARFO.
You have used up all your signing attempts. Reinitiate
the signing ceremony to complete transmission.
Location already in decimal
The location is already in decimal format. You do not
format.
have to enter it in decimal format.
FLDRS 4.1.9 already running!
Only one instance of FLDRS 4.1.9 can be open at a
time.
Encryption process failed. To
The encryption process failed but the trip information
export trip, install GNU
has been saved. Confirm that the encryption software
encryption software then re-export is installed correctly and that the application path is
trip through Manage Trips.
correct in the Administration Software Setup's Data
Export tab. You can then re-transmit the trip using
Managed Trips. Additionally, ensure the GNU
encryption has been properly configured (Page 17)
File zip process failed. Make sure Confirm that 7-Zip is properly installed and that the
7-Zip software is properly
application path is set correctly in the Administration
installed.
Software Setup's Data Export tab. The current trip has
been encrypted and stored in the local backup folder in
.gpg form.
Error -- Effort #  Enter a valid soak time.
is missing soak time value
Error -- Effort #  Enter a valid hour value (0-23).
hours is missing a time value
Error -- Effort #  Enter a valid minute value (0-59).
minutes is missing a time value
Error -- Effort #  Enter a valid depth value.
is missing average depth value
Error -- Effort #  Enter a valid gear quantity value.
is missing gear quantity value
Error -- Effort #  Enter a valid haul count value.
is missing haul count value
Error -- Effort #  Check that the effort times and durations are correct.
effort times are out of sequence
Error -- Effort #  Enter a valid date/time value.
is missing date/time value
Error -- Effort #  Enter a valid location value.
is missing location value
Error -- Effort #  Enter valid catch and/or discard data. If effort is a
contains no catch or discard
water haul, click on on the Water Haul button.
entries
Error -- Effort #  Enter in values for required dynamic data elements.
is missing required catch/discard
dynamic data element
37

FLDRS Administrator’s Guide

Message

Solution

Error -- Required effort element
not entered for effort # 
start time of effort  occurs before start of trip


Go to the Effort tab, select the effort, click the
Additional Data button, and enter the required data.

start time of effort  occurs after end of trip


end time of effort  occurs prior to start time of
effort 
Error -- Landing #  time of landing occurs
before trip departure
Error -- Landing #  time of landing occurs
after end of trip
Error -- Landing #  is missing required
landing dynamic data element
Error -- Landing #  is missing required
apportionment dynamic data
element
Can not perform import function
while a trip is active
Entry must be numeric
The converted amount falls
outside of the recommended range
Selected species not listed in
Conversions table.
Mesh size not within accepted
limits for: 

There is a conflict in dates and/or times between the
start of the trip and the start of the effort. Note the
effort number, then go to the Effort tab and check the
Set—Start time and date. If they are correct, go to the
Trip tab and check the departure date and time.
There is a conflict in dates and/or times between the
end of the trip and the start of the effort. Note the effort
number, then go to the Effort tab and check the Set—
Start time and date. If they are correct, go to the
Landings tab and check the date and time of landing at
the end port.
There is a conflict in dates and/or times between the
start and the end of the haul. Note the effort number.
Then go to the Effort tab and make sure that the Set—
Start and Haul—End dates/times are correct.
There is a conflict in dates and/or times between the
end of the trip and the landing. Go to the Landings tab
and check the date and time of landing at the end port.
There is a conflict in dates and/or times between the
end of the trip and the landing. Go to the Landings tab
and check the date and time of landing at the end port.
Go to the Landings tab, select the landing, click the
Additional Data button, and enter the required data.
You must enter additional data for this landing. Go to
the Landings tab, select the landing, click the
Additional Data button, and enter the required data.
Support tables cannot be loaded while there is an active
trip. Close the current trip and try again.
You can only enter numbers in this field.
Please check your conversion to verify that you have
reported the correct amount, grade code and unit of
measure.
Ensure that the proper support tables have been loaded.
You may not be able to convert species until new
support tables are loaded.
The values you entered are outside the range of sizes
that FLDRS considers typical. Check the values that
you entered and make sure you are reporting the
information correctly for that field. If you are still
certain it is correct, click the Ignore button.

38

FLDRS Administrator’s Guide

Message

Solution

Gear size not within accepted
limits for: 

The values you entered are outside the range of sizes
that FLDRS considers typical. Check the values that
you entered and make sure you are reporting the
information correctly for that field. If you are still
certain it is correct, click the Ignore button.
The values you entered are outside the range of sizes
that FLDRS considers typical. Check the values that
you entered and make sure you are reporting the
information correctly for that field. If you are still
certain it is correct, click the Ignore button.
The values you entered are outside the range that
FLDRS can record. Check the values that you entered.
FLDRS is unable to receive data from your GPS unit.
Check that the GPS unit is turned on and that all
connections are secure. Additionally, verify that the
correct COM port is selected in Software Setup.
FLDRS is unable to receive data from your depth
sounder. Check that the depth sounder is turned on and
that all connections are secure. Additionally, verify that
the correct COM port is selected in Software Setup.
Check that you have spelled the species name
correctly. If the spelling is correct, the species may not
be listed in the support table. Verify a current species
support table has been loaded.
The password for the signing ceremony must meet
these requirements.
The password for the signing ceremony must meet
these requirements.
The password for the signing ceremony must meet
these requirements.
The password for the signing ceremony must meet
these requirements.
The password for the signing ceremony must meet
these requirements.
The password for the signing ceremony must meet
these requirements.
The password for the signing ceremony must meet
these requirements.
The password must meet certain requirements; see
“Digital signing ceremony” page 16Error! Bookmark
not defined.. Check your entry carefully and try again.
There is no trip data for the identifier you selected, so
FLDRS cannot export or retransmit trip. The trip may
have been deleted.

Gear quantity not within accepted
limits for: 

# of hauls not within accepted
limits for: 
Error starting GPS

Error starting Depth Sounder

No species matches search pattern.

Password entry must be at least 8
characters in length.
Password entry must be no longer
than 12 characters in length.
At least one character must be a
capital letter.
At least one character must be a
lowercase letter.
At least one character must be
numeric.
At least one character must be
non-alphanumeric.
Single and double quotes may not
be used.
The operator password was not
confirmed. Please enter again.
No data associated with selected
trip identifier

39

FLDRS Administrator’s Guide

Message

Solution

File already exists

A file already exists with this filename. FLDRS does
not allow more than one file with the same name. You
may need to delete the previous version of the file.
The attempt to retransmit the file failed because the file
could not be copied to the transmission directory. The
trip may have been deleted.
FLDRS cannot find a trip file to retransmit. The trip
may have been deleted.
The transmission method must be set to Boatracs or
Skymate in order to retransmit trip data. Verify
transmission method in Admin Software Setup page.
You have used up all the signing attempts. To complete
the transmission, you have to reinitiate the signing
ceremony.
FLDRS is unable to receive data from your GPS unit.
Check that the GPS unit is turned on and that all
connections are secure. Additionally, verify that
correct COM port is selected.
FLDRS is unable to receive data from your depth
sounder. Check that the depth sounder is turned on and
that all connections are secure. Additionally, verify that
correct COM port is selected.
Only .csv files with proper filenames can be loaded.
Only .csv files with proper filenames can be loaded.
Input can only be a valid decimal value.
Input can only be a valid integer value.
At least one user record must remain in the database.
At least one administrator record must remain in the
database.
The username cannot be blank.
The user record already exists.
The password must meet these requirements.

File not copied

No file matching selected trip
identifier found
Re-Transmit button operational
only for Skymate or Boatracs
transmission methods
Signing ceremony failed

Error starting GPS

Error starting Depth Sounder

Invalid Support Table
Non-Compatible file import
Please enter a valid decimal value
Please enter a valid integer value
Can not delete last user
Cannot delete last administrator
Username must be entered
Cannot add duplicate user
Password entry must be at least 8
characters in length.
At least one character must be
non-alphanumeric.
Must confirm password
Cannot change type of user on last
administrator
Operator 
already exists in the shortlist.

The password must meet these requirements.
The password must be entered correctly twice for
FLDRS to save the record to the database.
At least one administrator record must remain in the
database.
The operator name is already in the shortlist, and
FLDRS does not allow duplicates in the list.

40

FLDRS Administrator’s Guide

Message

Solution

Operator is utilized as a default. If
this operator is deleted, a new
default operator must be selected
before trips can be entered.
Continue with delete?
Vessel  already
exists in the shortlist.
There are no vessels in the short
list to delete.
No species list to delete
No species list exists to copy
Cannot add species before at least
1 species list is created
Cannot delete species before at
least 1 species list is created
At least 1 species list must be set
up prior to gear configuration.
Haul Count cannot be null
Please enter a valid decimal value

You are trying to delete the operator that you set as the
default. Although you can go ahead and delete this
operator, you must select an operator to use as the
default operator.

Please enter a valid integer value
Dealer  already
exists in the shortlist.
There are no dealers in the short
list to delete.
There are no gear configurations
to delete.
Current effort has not ended

Cannot add duplicate vessel to the short list.
The vessel short list is empty.
There are no species lists.
There is no species list.
Before you can add species, you have to create a
species list.
There is no species list.
You must create a species list before you set up a gear
configuration.
You must enter a value for the haul count.
Enter a valid number. FLDRS could not interpret your
entry.
Enter a valid number. FLDRS could not interpret your
entry.
The dealer name is already in the shortlist, and FLDRS
does not allow duplicates in the list.
The dealer shortlist is empty.
The gear configuration shortlist is empty.

Cannot start a new effort until current effort is
completed or deleted.
Cannot start a new effort while a
Once you have recorded a landing, the trip is closed
landing for the trip exists.
and you cannot add more efforts to it.
Location missing. Cannot calculate Input a valid GPS location.
area
GPS not enabled
FLDRS is unable to receive data from your GPS unit.
Check that the GPS unit is turned on and that all
connections are secure. It may be necessary to
physically unplug the USB cable and plug it back in to
reset the port. Meanwhile, you may be able to enter
values by hand.
Error in reading GPS date/time
The GPS is no longer sending data to FLDRS. Check
that all connections are secure. Ensure that the correct
COM port is selected in Software Setup.
GPS signal lost. Manual entry of
The GPS is no longer sending data to FLDRS. Check
location required.
that all connections are secure. You will have to enter
fishing effort locations by hand.
41

FLDRS Administrator’s Guide

Message

Solution

Location value exists. Do you wish
to overwrite it?
Start of set occurs after end of set

If the location value is correct, do not overwrite it.

End of set occurs after start of
haul

Start of haul occurs after end of
haul

Current tow duration exceeds 8
hours.

Please enter value between 0 and
59
Please enter a valid decimal value
Please enter a valid integer value
Soak Minutes cannot be empty
Soak Minutes must be between 0
and 59
Soak Minutes must be an integer
Soak Hours cannot be empty
Soak Hours must be an integer
Average Depth cannot be empty
Average Depth must be an integer
Cannot edit catch once a landing
record is created
Effort has been transmitted
Current effort has not ended.
Cannot edit catch data
No landing has been generated.
GNU encryption software not
located. Trip can be archived but
not exported until software is
properly installed.

There is a conflict in dates and/or times between the
start of the set and the end of the set. Note the effort
number, then go to the Effort tab and check the Set—
Start time and date and Set - End Time.
There is a conflict in dates and/or times between the
start of the haul and the end of the set. Note the effort
number, then go to the Effort tab and check the Haul—
Start time and date and Set - End Time.
There is a conflict in dates and/or times between the
start of the haul and the end of the haul. Note the effort
number, then go to the Effort tab and check the Haul—
Start time and date and Haul - End Time.
The values you entered are outside the range of sizes
that FLDRS considers typical. Check the values that
you entered and make sure you are reporting the
information correctly for that field. If you are still
certain it is correct, click the Ignore button.
Minute values must be between 0 and 59.
Enter only numbers within the expected range. The
field must contain numbers and one decimal point.
Enter only numbers within the expected range.
Enter a valid value for Soak Minutes.
Minute values must be between 0 and 59.
Enter only numbers within the expected range.
Enter a valid value for Soak Hours.
Enter only numbers within the expected range.
Enter a valid value for Average Depth.
Enter a valid integer value
Changes to the catch data cannot be made once a
landing is generated.
Selected effort has already been transmitted. Changes
to catch data cannot be made.
Cannot enter catch data for an effort until effort has
ended.
No landing has been generated.
The encryption process failed but the trip information
has been saved. Confirm that the encryption software
is installed correctly and the application path is set in
Software Setup. Trip can then be re-transmitted
through the Managed Trips function.

42

FLDRS Administrator’s Guide

Message

Solution

7-Zip software not located. File
compression not possible until
software is properly installed.
There are no new efforts to export

Confirm 7-Zip is properly installed and application
path is set correctly.

You may not transmit trip data unless you have new
efforts to report.
Signing ceremony failed
Signing attempts maxed out. Will need to reinitiate
signing ceremony to complete transmission.
Database not successfully backed
Database could not be backed up. Either the database
up
could not be found or the System Backup folder not
present.
Trip was not exported
An error occurred in the trip export process. Verify that
transmission method is set correctly and reattempt
export process.
There are no trips to delete
Trip data does not exist for selected identifier.
No Trips for Report Generation.
Trip data does not exist for selected identifier.
No active trip backup file yet exists An attempt was made to recover a trip before the active
for this trip
trip backup file was created. If this is the case, recover
trip not possible.

43


File Typeapplication/pdf
File TitleFLDRS Administrator’s Guide
AuthorEmma
File Modified2022-02-09
File Created2018-04-24

© 2024 OMB.report | Privacy Policy