P3 Help
Table Of Contents Overview ...................................................................................................... 1 What's new in version 1.4.4 .......................................................................... 1 Documentation ........................................................................................... 2 Installing P3 and Getting Updates .................................................................. 3 What's Installed ...............................................
P3 Help Configuring Devices ....................................................................................12 Device Profile Settings..............................................................................12 General Device Properties .........................................................................13 Serial Port Device Settings ........................................................................14 Tag Reader Devices .....................................................................
Table Of Contents Drop-Down Value Lists .............................................................................31 Session Header Note ................................................................................31 Saving Session Header Information ............................................................31 Tag Session Header Field Reference Guide .....................................................32 Tag Session Header Templates ..................................................................
P3 Help Upload Configuration Settings ...................................................................53 Uploading Data to PTAGIS ........................................................................53 Upload History ........................................................................................54 Importing and Exporting ................................................................................57 Exporting Data.............................................................................
Table Of Contents Tag Action Settings and Commands ...........................................................75 Tip: the Replace command will import tag codes much faster than the Import command. Use the Import command only when appending a relatively small number of tag codes (less than 25k) to a tag action. ....................................80 Tip: the Delete All and Replace commands will generate a lot of empty space in the P3 database.
P3 Help Deletion of Verbose Species, Run and Rear Codes ......................................101 Database Maintenance ..............................................................................102 Appendix ...................................................................................................103 Frequently Asked Questions .......................................................................103 Questions .......................................................................................
Table Of Contents Collecting Data on the Destron Reader......................................................110 Downloading Data from the Destron Reader into P3....................................110 Erasing Stored Records from the Destron Reader ....................................... 110 Configuring Calcomp Drawing Board III .......................................................111 Index ........................................................................................................
Overview Overview of the P3 Application P3, also known as PITTag3, is a data entry, edit, and validation tool developed expressly to facilitate the collection of PIT tag mark/recapture data in the Columbia/Snake river basins. P3 provides the user with a very fast data entry module that recognizes, coordinates, and assigns input from a number of peripheral electronic components.
P3 Help Other Fixes: • • • Layout of the exported tag file was changed to match previous versions of P3. The note in the detail records will have a blank like above and below the note. Default baud rate for Avid PowerTracker II is set to 2400 baud. When the user changes file name used for a tag session, all upload history for the old file will be erased to avoid confusion. Documentation This documentation is meant to provide quick, easily accessible information about the P3 application.
Overview Installing P3 and Getting Updates The P3 application can be downloaded from the P3 Home Page web site. There are two types of installation files that can be downloaded: Full Installation. This single setup file contains the setup program and all of the necessary components to install P3. This file is very large and should be used for the initial installation and/or used for installing on systems that do not have a connection to the Internet. Web Installation.
P3 Help The P3 installation program does not include the validation code libraries. These libraries are updated as necessary. P3 will prompt the user to download or import the current codes into the application the first time it is started. Customizing the P3 Installation By default, when the P3 application starts, it looks in the installation directory for the P3.mdb and Secured.mdw files. If these files are not found, it will prompt you to find them.
Overview • • • • Processor Type: Pentium Processor Clock Speed: 100 MHz Memory: 32 Megabytes RAM Hard Disk Space: 30 Megabytes free space Note: For optimal performance, additional memory (64 Megabytes or greater), disk space, and greater processor speed (300 MHz or faster) are highly recommended, as is the use of a mouse or other pointing device.
P3 Help A&D FX/FY3000 series with RS-232 kit. Sartorius Combics 1 models with RS-232. Digitizer Tablets CalComp Drawing Boards and Drawing Slates supporting the ASCII 2000 format. WinTab digitizer tablets. Multiports BayTech H-Series Multiport Controller.
Configuration Configuration Profiles Profiles contain all of the P3 configuration settings specific to the data collection environment such as device settings, audible alerts, and data logging. Multiple profiles can be created, copied, and modified using the profile manager accessed from the Tools menu, displayed below. In addition, profiles can be exported and imported into other P3 installations. Active Profile The active profile is defined to be the profile currently in use by the application.
P3 Help Note: Changing the active profile while a Tag Session is open will cause peripheral devices to be disconnected and reconnected to the application; it may also reset the default repeating comments. Tip: Clicking on the Active Profile label on the toolbar will automatically open the active profile for editing. Profile Settings Profile settings control how a tag session will collect and display data.
Configuration The following categories describe profile settings as they are grouped in the profile window: General Devices Tag Actions Species/Run/Rearing-Type Constraints Audible Alert Sounds General Profile Settings Most of the general profile settings effect how data will be collected and processed in a tag session.
P3 Help Navigating and Changing General Profile Settings P3 uses a standard tabular data entry mechanism. The ARROW keys move between fields and the TAB and SHIFT-TAB keys move forward and backwards between controls such as the data entry grid and command buttons. To edit a profile setting, do the following: 1. Double-click or press ENTER in the Value field you want to edit. The cell will display a cursor; this state is referred to as Edit Mode. 2.
Configuration Duplicate Tag Codes Auto Accept Verbose Species Run and Rear Mandatory Length Mandatory Weight Data Logging Log File this Tag File Prefix value. Changing this value in the Profile will not affect the tag file names in existing tag sessions. This setting determines what to do in the event a duplicate tag code is detected during data collection.
P3 Help Default Export Path Default Repeating Comments floppy drive may impact performance during the data collection process. This setting defines the default path for exported tag data information. If no path is defined, P3 will automatically create an Export sub-directory in the application path, by default. If this setting is set to 'Yes', default repeating comments will be applied each time the application is started or the active profile is changed.
Configuration settings. A device can be configured for each available serial port. Devices are no longer restricted to one serial port as with the PITTag2 application. Device Manager Functions Open - opens the selected device to modify its properties. New - creates a new device for this profile. Delete - deletes the selected device setting. Terminal - launches a terminal window connected to the selected device's serial port.
P3 Help Property Device Type Label Device Enabled Effect The field lists all of the supported peripheral devices. Changing this setting will automatically add or remove additional property settings associated with the type of device selected. Allows the user to customize the description of this device throughout the application so that it can be easily identified. This enables or disables device input when a tag session is opened.
Configuration Property Port Baud Parity Data Bits Stop Bits Flow Control Effect Selects an RS-232 serial port that the device is connected to on the PC. P3 supports serial ports ranging from COM1 to COM25. The baud rate determines the rate which data is sent to the PC from the device. Baud rates range from 1200 to 115200. An error-detection method that checks the validity of a transmitted character. P3 supports None, Odd, Even, Mark and Space parity settings.
P3 Help Device Action A device action is triggered when a tag code is received from a reader device. This is useful for identifying a tag code scanned from a particular device (e.g. scanning for recaptured fish). The user may want to be notified of such an event and an optional comment can be placed on the current detail record. Additionally, an optional sound event can be configured for this action in the profile's audible alert profile settings.
Configuration existing textual comment in the current detail record. Note: Leaving the Alert Message field blank will suppress the display of a visual alert when the device action is triggered. Balance Devices Balance devices input weight information, measured in grams and precise to one decimal place. This data is written to the weight field in the current detail record. The balance device type does not have any additional property settings.
P3 Help WinTab Digitizer Tablets WinTab digitizer tablets communicate to the application using an external device driver. This tablet must be installed using the manufacturer's installation program before it can be used with P3. This type of device cannot be connected to a multiport controller. When a tag session is not currently open, this device may control the mouse cursor. Note: Only one WinTab device can be configured for a single profile.
Configuration will be extended. Note: This setting can be enabled or disabled using a digitizer map command. By default, a non-zero nose stop extension is enabled whenever a tag session is opened or the active profile is changed. Baytech Multiport Controllers A Baytech multiport controller extends a single serial port into four or more additional serial ports. Devices are connected to the multiport so that each is uniquely addressed in such a way that the P3 application can identify and separate input.
P3 Help The terminal window connects directly to a serial port to help troubleshoot device connections. This tool provides raw data from the connected device and contains a set of device commands specific to the type of device selected. This tool is not available while a tag session is open. Also, the Terminal Window does not support WinTab type devices. This tool is selected by pressing the Terminal menu button on the device manager window.
Configuration Port Connection list to automatically invoke it. The commands can also be manually typed into the terminal window, followed by a RETURN. Pressing this button on the tool bar will toggle the connection on/off between serial port and terminal window. Activating Tag Actions Tag Actions trigger specific responses to tag code input and can be defined and enabled within a profile.
P3 Help Optionally, the user can assign to each constraint minimum and maximum expected values for length and weight data entry. If, during data entry, the user encounters a combination of Species, Run, and Rear- Type codes other than those that were predefined within a constraint, or a length or weight value outside the range defined for that code combination, they will be alerted to, but not prevented from, processing those data as part of the Tag Detail Record.
Configuration Property Species Run and Rear Min Length (mm) Max Length (mm) Min Weight (g) Max Weight (g) Effect Selects a specific species, run and rearing type code for this validation constraint. This required field may be verbose or coded and defines the restricted domain of allowable input. An optional minimum length constraint. The user will be alerted if the current detail record matches the specified species, run and rearing-type setting and the input length is less than this value.
P3 Help P3 uses audible alerts to confirm data entry and to signal various events, mostly within the data collection and validation process. By default, P3 issues a series of beeps through the computer's internal speaker to signify these events. The user can assign wave (*.wav) files to any or all of these events outside of the application using the Sounds applet in Window's Control Panel. This section of the profile settings allows users to enable or disable sound events.
Configuration Error Input Digitizer Command Input Length Input Tag Input Weight Device Action Reject Record Tag Buffer Event Duplicate Tag Code A general purpose sound event dedicated to runtime or system generated errors. Fires whenever a digitizer command is sent to the application. Fires whenever Fires whenever device. Fires whenever Fires whenever length input is sent from a digitizer tablet. a tag code input is sent from a reader weight input is sent from a balance device.
P3 Help 26
Data Collection and Validation Tag Session Overview A tag session contains individual records of each fish marked or recaptured with a PIT tag. These records are referred to as detail records. In addition, a tag session contains global information about the marking session, such as location, time and temperatures. This global information is stored in header fields. Tag sessions can be closed and reopened for data input at a later time. Only one tag session can be opened at any given time.
P3 Help templates allow the user to customize the header field names or hide fields that are not required. Incomplete Tag Sessions P3 allows users to save tag sessions that are incomplete or invalid. Incomplete tag sessions can not be exported or uploaded until all required data have been provided, and the session contents have been validated. P3 uses the following icons to identify tag sessions: Indicates a valid tag session. Indicates an incomplete or invalid tag session.
Data Collection and Validation Open Opens the selected tag session. This tool can be accessed from both the toolbar and right-click menu. New Creates a new tag session with blank header fields. This tool can be accessed from both the toolbar and the right-click menu. Deletes the selected tag session. This tool can be accessed from both the toolbar and right-click menu. Delete Large Icon Tag sessions will be displayed with large icons in the list. This tool is accessed from the toolbar only.
P3 Help Template This command, accessed from the right-click menu only, allows the user to change the header template association for the selected tag session. The user can select a different header template or set the association to "None". Tag Session Header The Tag Session Header contains global information about the tagging project. Header fields shown in bold are required fields which the user must enter data into before a tag session is considered valid and complete.
Data Collection and Validation 1. Double-click or press ENTER in the data field you want to edit. The cell will display a cursor; this state is referred to as Edit Mode. 2. Make any changes to the field contents or select a value from a drop-down list. 3. To complete your changes, press ENTER. 4. To cancel your changes, press ESC. 5. Use the DOWN-ARROW to move to the next field. Drop-Down Value Lists Some header fields have a limited set of values.
P3 Help confusion about what information is saved when the Accept command is pressed and any validation error messages will remain within the context of the Tag Session Header. Tag Session Header Field Reference Guide This topic provides a reference guide for all session header fields. Please consult the current PIT Tag Specification Document if you have further questions about these data fields.
Data Collection and Validation This is a required header field containing a code representing the geographical location of the tag event (e.g., a hatchery location for the original marking, or a trap or dam location of a subsequent recapture event). The code must be a code from a predefined drop-down value list. Tagger Lastname I Mandatory This is a required header field containing a last name and first initial (e.g., BODY A).
P3 Help Hatchery Site [Valid Hatchery] Optional When fish are tagged at a hatchery, this field contains the four-character abbreviation from the domain of hatchery codes. The code must from the predefined drop-down value list. Stock Text Optional This field contains a description of the genetic or geographic stock, to a maximum of 15 characters. Brood Year nn Optional This field contains the last two digits of the calendar year when eggs were deposited or collected, if known.
Data Collection and Validation This field indicates the point of release, in kilometers, and the default value is based on a value entered in the Release Site header field. This is a hierarchical coding scheme from the mouth of the Columbia River to the Point Release site or stream of release (up to 7th order streams), with each river segment delimited with a period.
P3 Help A tag file header template allows the user to customize header field labels, define default values, and/or hide selected fields. Templates are typically used to populate a header with specific field values and/or to prevent erroneous or extraneous data entry. When a tag session is created with a header template, it will apply any customization and default values defined in that template.
Data Collection and Validation Customizing Field Labels To customize a field label, select a field label, located under the Field column, by double-clicking or pressing ENTER, and type over the default field label. The field must contain at least one character and can contain a maximum of fifty characters. The new field label will be displayed in any tag sessions that are associated with this template. This allows the user to add more meaningful labels in the context of their tagging project.
P3 Help with a strike-through font and this field will be hidden in any associated tag sessions. Any default values associated with a hidden field will be ignored. Note: A tag session will always display a header field if it has data, regardless of any template setting. Tag Detail This section of a tag session provides data entry for a tag detail record. A detail record is comprised of data fields containing information about a specific fish marked with a PIT tag.
Data Collection and Validation Scrolling Between Detail Records The scroll bar is located at the bottom of the detail record. If the current detail record is modified, the scroll bar is disabled until the modification is accepted or rejected. The scroll bar has these functions, left to right: Scroll Function First Previous Record Number Next Last New Record Count Description Scrolls to first detail record. Scrolls to the previous detail record.
P3 Help This field can contain three types of data: • • • 10-character hex ID code characteristic of a 400 kHz PIT tag code. 14-character hex ID code comprised of a three-character hex country code, a period, and a 10-character hex ID code; this mask is typical of 134.2 kHz ISO-compliant Duplex-B PIT Tags. A "dot-out" value, which is a series of 10 periods that indicates the tag was removed from, or shed by, the original marked animal.
Data Collection and Validation Species Run and Rear [Valid Species Run and Rearing-Type code(s)] Mandatory This field (or fields) will be displayed one of two ways based upon the verbose profile setting: Character Codes In this format, the user must select individual codes for each field, using the mouse, keyboard or a digitizer command. Refer to the current PIT Tag Specification Document for more information about these validation codes.
P3 Help If the mandatory length setting is enabled in the active profile, this field will require input before the current detail record can be saved. The field name will contain a blue check mark to identify that it is required. The user can enter a null value (a series of four dash characters) using the dash command to satisfy the mandatory length requirement for the current record. nnnnn.
Data Collection and Validation There are 50 columns available to record Text Comments, a free-form annotation pertaining to the existing detail record. Data can be entered from a keyboard and recurring phrases can be entered from a digitizer command. Tag Detail Validation P3 performs a number of validation and verification routines on every processed Tag Detail Record.
P3 Help Record-Level Validation Mandatory Fields Constraint Validation Maximum Detail Records To complete a detail record, the Tag Code and Species, Run and Rearing-Type fields are mandatory and must have a valid value entered. Note: The active profile provides settings to optionally make the Length and Weight fields mandatory also. When the user presses the Accept button to save a complete detail record, the data entered is validated against any activated constraints.
Data Collection and Validation Code field and resets the detail record for new input. Replace Automatically scrolls to the detail record containing the first instance of the duplicate Tag Code. The user can edit the other detail fields in that record. Dot Out The original detail record containing the duplicate tag code is automatically dotted-out. The current detail record will contain the new tag code and the user can continue entering data into the other fields.
P3 Help Command Accept Scroll Detail Records Description Saves any changes to the current header fields and/or detail record. In the case of a new detail record, the record will be saved and the tag detail section will automatically scroll to the next new record for input. The user can toggle the Auto Accept profile setting to automate this command when tag codes are input from a device.
Data Collection and Validation Repeating Comments Set Repeating as Current Enable Repeating Comments Reset Comments Dot/Dash All Repeating comments supply default values for new detail records. This command displays a window to define those default values. If enabled, any value entered into a field will be the default value for each new record.
P3 Help Dash Length and Weight Undo DotOut Next Tag Code in Buffer Clear Tag Buffer Align Digitizer Map Dashes length and weight fields only. If the tag code field in the current detail record was dotted-out and the record has not yet been saved, this command will replace the dot-out with original tag code. If the tag code buffer is not empty, this command will automatically select the first buffered tag code and enter it into the tag code field of a new detail record.
Data Collection and Validation To assign a release date and time to a variable, double-click or press ENTER in the corresponding Date/Time cell and either type in the value or press [CTRL-;] (semicolon) to enter the system date and time, or press F4 to display a calendar. Press the OK button to save the assignments. All VRT codes must have a release date and time defined before a tag session is considered valid. All release times must be in Pacific Standard Time.
P3 Help The detail viewer has these features: • • • • • • Sort any column in ascending order by clicking on the column header; click again to sort in descending order. Resize columns by positioning the mouse at the edge of the column header and dragging. Lock columns and/or rows from scrolling by dragging the lock icon that's displayed when the mouse is at the edge of the row or column headers.
Data Collection and Validation Statistics Viewer The Statistics Viewer presents an up-to-date summary of Species Counts, Duplicate Tag Codes, and Reader Device Statistics for an open tag session. The viewer is automatically refreshed whenever data is changed in the open tag session or new information is recorded from a reader device. This feature can be accessed from under the Session menu or from a digitizer map command (there is also a digitizer map command to switch between sections of the viewer).
P3 Help Duplicate Tag Code This section presents all duplicate tag codes in the current detail record set. Although the user is alerted to duplicate Tag Codes during data entry, they have the option of accepting the duplicate, and it is here where two or more detail records with identical tag codes are displayed. Tip: Double-clicking any cell under the Record # column will switch to the tag detail tab page and automatically scroll to the corresponding detail record.
Data Collection and Validation Once data has been collected and validated, the next step is to upload the data to PTAGIS. In previous versions, this was accomplished by exporting the tag sessions into tag files and submitting them to PTAGIS via email. This manual process still works; however, P3 has a new feature that automates this task and keeps track of which tag sessions have been uploaded. To access the automated upload feature, select the Upload command located under the File menu.
P3 Help The Upload page of the Upload Manager displays a list of all valid tag sessions that can be selected for submission. To select a particular tag session for uploading, check the corresponding box in the Upload column. To submit the tag session as a correction, check the corresponding box in the Correction column. Note: When uploading multiple files, each file must have a unique Tag File Name.
Data Collection and Validation File Name column in the example above. Grouping columns is useful for viewing all tag sessions submitted on a certain date or for viewing all upload attempts for a particular tag session. The history report contains the following columns: Column Session Name File Name Upload Date Upload Complete Status Correction Message Description Name of the Tag Session that was uploaded. Name of the Tag File associated with the Tag Session. Date and time the upload attempt occurred.
P3 Help 56
Importing and Exporting Exporting Data P3 can export tag sessions as well as configuration information such as profiles, header templates, tag actions, and digitizer maps. This is useful for transferring information between multiple installations of the application. Only valid tag sessions can be exported. Tag sessions will be exported to individual text files using the Tag File header field as a name. Exporting configuration information is a little different than exporting tag sessions.
P3 Help 5. Once a location has been selected, press OK and the export process will start. 6. If any of the files already exist, a prompt will display asking whether to overwrite the existing file, overwrite all existing files, skip this file or skip all existing files: Importing Tag Files Tag files can be imported into P3 tag sessions. Multiple tag files from the same directory can be imported simultaneously. A tag session will be created with the name of the tag file.
Importing and Exporting 2. Next, select one or more files to import from the prompt. The default export path is used as the initial location. To select multiple files, press and hold the CTRL key while making your selections. Press the Open key once the file selections have been made. 3. P3 will begin importing each selected tag file. Before the import process is completed, the user will be prompted to confirm the results.
P3 Help 5. Select which tag sessions will be created by checking the corresponding box under the Save column. Use the Select All or Clear All buttons to quickly select/clear all of the imported tag files. Note: Some files that have too many validation errors or are not a tag file will not be allowed to be saved. These files will be marked with a large red 'X' (like 'Logfile.txt' in the example for step 3). 6. Optionally, select a header template to associate with all of the new tag sessions. 7.
Importing and Exporting 3. Select the tag sessions to import from the list. To select multiple tag sessions, use the mouse while pressing and holding the CTRL key. Once the tag sessions are selected, click the Import command to begin the import process. 4. P3 will begin importing each selected tag session. Before the import process is completed, the user will be prompted to confirm the results. The prompt reports each tag session that will be created when the OK button is pressed.
P3 Help 5. Review Import Status Messages for each tag session. The '# Msgs' column lists the number of messages associated with each tag session. To view messages for a tag session, select the tag session and the messages will be displayed in the Import Status Messages box below. 6. Select which tag sessions will be created by checking the corresponding box under the Save column. Use the Select All or Clear All buttons to quickly select/clear all of the tag sessions. 7.
Importing and Exporting 2. You will be prompted to select a text file to import. Once a file is selected, press Open. 3. The selected file is opened in the Import CSV Wizard. This wizard will guide you through the rest of the import process. Complete the first page of the CSV Wizard by selecting the correct delimiter that separates the fields in the selected text file. The Preview pane displays the first few lines parsed from the text file.
P3 Help For each row under the 'File Field' column, select a corresponding 'Detail Record Field'. Use the {Skip} selection to ignore the file field (or leave the assignment blank). Note that only single-character species, run and rearingtype codes can be mapped. There must be at least one field mapped for the import process to start. Press the Next button when the field mapping is complete. Click Save Fields to save the mapping to the registry. Click Clear Fields to delete registry entries.
Importing and Exporting 5. Optionally apply any repeating comments to detail records where there are no values from the text file; repeating comments will not overwrite values from the text file. Go to the next page. 6. You can create a new tag session or append the imported data to the detail records of an existing tag session. Keep in mind, tag sessions have a limit of 9,999 tag detail records. Press the Next button to go to the next page. 7.
P3 Help Importing and Exporting VRT Tables P3 can import and export VRT tables. VRT tables are exported to CSV (commaseparated values) files into your default Export directory. They are imported from CSV files. Exporting VRT Tables 1. Open a tag session from which you'd like to export VRT values and open VRT table by clicking on Assign VRT... icon on the toolbar or choosing Assign VRT... command from Session menu. 2. Click Export button. Save As dialog will be displayed.
Importing and Exporting 3. Click Save. If a file with the same name exists, you will be prompted by the program. You can overwrite existing file, or change the name of the export file. The program will display Success message when export is finished. Importing VRT Tables 1. Open a tag session to which you would like the codes to be imported. Open VRT table by clicking on Assign VRT... icon on the toolbar or choosing Assign VRT... command from Session menu.
P3 Help 2. Click Import button. Select import file dialog will be displayed. The dialog will open in your default export folder. 3. Select the file from which you want to import and click Open. Standard import wizard will be displayed.
Importing and Exporting 4. The first step of the wizard is to choose the separator, note if the first row contains field names, or if you need to filter quotes around text fields. The next step will filter invalid data. Note: The wizard expects that the VRT codes are stored in the first column and the dates are stored in the second column of the file. The second column data must be in valid date format. 5. The wizard will find and overwrite duplicates in your import file.
P3 Help 6. The wizard will not create new entries in the VRT table. It will only update dates of the codes that are in both the current VRT table and the import file. Downloading Data From a Tag Reader Some tag readers have the capability to store scanned tag codes. With P3 you can download these codes from the tag reader and create new detail records in a tag session.
Importing and Exporting 1. Select the Import->Reader Download command located under the File menu. 2. The Download Device Data wizard will guide you through the rest of the process. 3. The first page of the wizard asks you to select a tag reader configured in the active profile. Some advanced tag readers can store data in multiple files. Select a particular file number to download or by default all files will be downloaded. You can also filter any duplicate tag codes downloaded from the reader. 4.
P3 Help 6. The wizard prompts you to either create a new tag session (and optionally associate a template header) or append the new detail records to an existing tag session. Keep in mind, tag sessions are limited to 9,999 detail records. 7. Initiate the download from the last page of the wizard. Some tag readers, such as the Destron 2001F Portable Transceiver, will allow P3 to automatically initiate the download command from the reader when the Start button is pressed.
Importing and Exporting reader and the application. Press the Stop button (Start button toggles to the Stop button when pressed) if no data appears to be downloading. The application will stop the process after approximately 15 seconds if no data appear. Tip: to initiate a buffer download from a Destron 400kHz benchtop tag reader, cycle the power off and on, as necessary, and press the "MENU" button repeatedly until the reader displays "DUMP MEM TO PORT".
P3 Help You can import configuration data that was previously exported by a P3 application. This is a useful feature for transferring configuration information between multiple installations of the application. Steps for Importing Configuration Data 1. Select the Import->Configuration command located under the File menu command. 2. Select a file to import. Only configuration files previously exported from P3 can be imported. 3. P3 will analyze the file to determine the contents.
Tools Tag Actions When a new tag code is received during data entry, the new tag code can be matched against a group of codes in a tag action. If the tag look-up is successful (as defined below) P3 will display an alert and, if so configured, will automatically insert comment values into the current detail record. Tag actions have three modes of action: • • • Filter certain tag codes entered from a device. Generate an alert if a new tag code is in a list.
P3 Help Property Name Type Effect Identifies the tag action throughout the application. There are three tag action types: Filter If a tag code is entered from a reader device and it is a member of the list of tags in the action, it will be ignored. Tip: An action of this type is useful for testing the readability of a tag reader with a test tag without affecting the data of an open tag session.
Tools Message Alert Comments user to select one or more tag sessions as a source for tag code lookup. This text is displayed when an action event occurs. If no text is supplied, then no visual alert will be displayed. Any values entered into the comment fields will be applied to a new detail record when the action occurs. The Filter action type does not add comments, for obvious reasons.
P3 Help Tag Codes Note: If tag session is deleted, the source is also removed from any and all associated tag actions. This section is displayed only if Source is set to List of Tag Codes and allows the user to manage the list of tag codes associated with the tag action: Show Tags 78 By default, tag codes are not displayed until this command is pressed. This is to reduce the overhead for displaying tag actions with several thousand tag codes unnecessarily.
Tools Add Tag Prompts the user to enter a single tag code into the list. Import User can select one or more files containing a list of tag codes to import into the list. The tag codes in the file must be line and/or comma delimited. Only recognizable tag codes will be imported into the list - and a tag code can only appear once in the list; duplicate tag codes will be automatically filtered during the import process.
P3 Help Tip: the Replace command will import tag codes much faster than the Import command. Use the Import command only when appending a relatively small number of tag codes (less than 25k) to a tag action. Tip: the Delete All and Replace commands will generate a lot of empty space in the P3 database. We recommend running the Compact and Repair utility after running any of these commands to optimize the database.
Tools Digitizer Maps Note: A handy mm ruler for your digitizer can be downloaded on P3 ftp site. Digitizer maps define customizable data entry from a digitizer tablet device. A digitizer map contains a grid of cells in a specified number of rows and columns. Each cell is assigned a specific command, called a map command, that can input predefined data into the current detail record or evoke a tag session command. The user can adjust the display format and print size of the digitizer map.
P3 Help When a digitizer map is created, by default it will have 4 rows and 6 columns. To change the default settings of a digitizer map, select the Properties command located under the Edit menu on the digitizer map editor. The digitizer map editor has these commands: Command Description New Creates a new digitizer map. Open Opens an existing digitizer map. Save Saves any changes to the current digitizer map.
Tools Columns Height Width Default Format Zoom Add/Remove Columns/Rows Cell Formatting Commands digitizer map. Number of vertical columns in the digitizer map. The printed height of the map (in inches). The printed width of the map (in inches) Default cell attributes such as font style, background color, etc. Changes the magnification of the display from 'Fit to Window' to 25%-150% of the defined print size. Zoom settings are reset whenever the map is printed.
P3 Help Digitizer Map Commands Map commands are assigned to cells of a digitizer map and define what happens when the user clicks on a printed map located on top of a digitizer tablet. There are three types of map commands: Application, Comment and Device - which are represented as tab pages on the map command dialog window. The current page displayed determines the type of map command that will be associated with a digitizer map cell.
Tools Edit Repeating Comments Set Current as Repeating Comments Clear Comments Repeating Comments On/Off Reset Repeating Comments Replace Duplicate Tag Increment VRT Decrement VRT Scroll First Scroll Previous Scroll Next Scroll Last Scroll New Next Buffer Tag Clear Tag Buffer Dot/Dash All Dot-out Tag Code Dash Length Dash Weight Undo Dot-Out Time Check Validate Validate/Export View Header View Detail Show/Hide Statistics Viewer Change Make changes to the current repeating comments.
P3 Help Statistics Viewer Page Clear Additional Positional Clear Conditional Comment Clear Textual Comment Toggle Length Extension and Reader Devices) while the Statistics Viewer is open. Clears any codes currently in the Additional Positional comment field of the current detail record or repeating comment window. Clears and flag codes currently in the Conditional Comment field of the current detail record or repeating comment window.
Tools codes will be filtered. Text Comments in this command will be appended to the current detail record and duplicate comments are not filtered. Device Map Commands This type of command allows the user to control a peripheral device from the digitizer tablet, such as toggling the scan mode of a reader on and off or making a balance send a weight to the application. Once the user selects a Device Type, a list of commands associated with the device type will be displayed.
P3 Help The search feature is accessed using the Search command located under the Edit menu. Selecting the Search command will create a new search query. Clicking on the arrow to the right of the command will display a Manage Favorite Searches command and any saved searches below. Selecting the Manage Favorite Searches command will display a manager window where the user can copy, rename and delete saved searches. Creating a Search Query There are two basic steps for creating a search query.
Tools Note: The search feature displays Species, Run and Rearing-Type codes rather than the verbose string descriptor. Defining Search Criteria The search conditions define which records will be returned when the Search command is pressed.
P3 Help such as 'Records where Conditional Comment contains M'. The condition that logically combines one or more Elementary Conditions is called a Complex Condition, such as 'Select records where any of the following apply'. A search can have one or more Complex Conditions. To add or delete a condition, click the button. Elementary Conditions When creating an Elementary Condition, there are three statement components that must be defined: Field, Comparison and Value.
Tools Any All None Not All Any one of the elementary conditions is true. All of the elementary conditions must be true. None of the elementary conditions are true. At least one of the elementary conditions is false. Note: Complex Conditions can be nested (a Complex Condition containing another Complex Condition as a sub-condition). Designating which Fields to Display Clicking on the Fields tab displays a list of data fields that can be returned in the result set.
P3 Help When the Search command is pressed, the results of the search will be displayed in the box below the search definitions. Clicking on a column header will automatically sort the column. Clicking it again will sort the column in reverse order.
Tools This tool allows the user to change a value for a particular data field. To access this tool, select the Replace command located under the Edit menu. In the example above, a Text Comment field containing 'THIS VALUE' will be replaced with 'THAT VALUE' in all tag sessions.
P3 Help Confirm Replaced Values Pressing the Replace command button will start the replacement process. Before the process completes, the user is prompted with the results of the replacement and asked to confirm the changes: Merging Tag Sessions This tool allows two or more tag sessions to be combined into a single tag session. This may be convenient for management purposes, or may be necessary for updating detail records with additional information from another set of data.
Tools To perform a simple merge, select a Primary Tag Session to merge into and then select one or more Secondary Tag Sessions to merge from and press the Merge button. All of the detail records contained in the Secondary Tag Sessions will be appended to the Primary Tag Session. Only the primary tag session is affected in this operation. Note: Tag Sessions are limited to 9,999 detail records. Merged sessions will automatically truncate at this limit. Keep this in mind when merging several tag sessions.
P3 Help one. Set how duplicate record fields should Merge Filter out Dot-Outs in Secondary Tag Sessions Merge Duplicate Records Only If this setting is not checked, the following options are disabled and all detail records from the Secondary Tag Sessions will be appended to the Primary Tag Session regardless of any duplicate tag codes. If you choose to combine records with duplicate tag codes from multiple sessions, you can specify which value version (primary or secondary) to use for each field.
Tools 4. The wizard displays all tag sessions containing one or more of the tag codes from the source list. Select which of these tag sessions to apply the dotout(s) to by checking the box next to the name. The Detail button will display a report of specific tag detail records that will be dot-out when the Finish button is pressed. It will also display any tag codes that did not match with any other detail records for dotting-out. This report, as shown below, can be printed or saved to a file. 5.
P3 Help Simply select one or more tag sessions and press the Remove button. All dot-out records contained within the selected tag sessions will be removed. Duplicate Viewer The duplicate viewer prompts the user to select one or more Tag Sessions and then displays any tag detail records that have duplicate tag codes. All of the tag detail fields are displayed to help the user to decide which record may be valid.
Tools Duplicate detail records are initially ordered from older to new records, grouped together by tag codes in ascending order; the columns are ordered by 'Tag Code', 'Created On' and finally 'Record #'. Clicking on any columns will reorder the viewer. The 'Tag Code' column is fixed, so that it will always be displayed when scrolling the viewer horizontally. Selecting a record in the 'Dot-Out' column will mark that record for the 'Dot-Out Duplicates' command, described below.
P3 Help • • • Print... command will print the viewer exactly as displayed. Save to File... will save the contents of the detail viewer to a commaseparated file. Refresh will cause the viewer to scan the selected tag sessions and refresh the display of duplicate tag records in the grouping and order described above. Validation Codes This tool manages all of the runtime Validation codes maintained and generated by PTAGIS.
Tools generates for updating validation codes: rkmcodes.txt and validtbl.txt. Both of these files are available for download from the Download page on P3 Home Page. Pressing the Import File command will prompt the user to select one or both of these files; by default the prompt looks for these files in the ../P3/Config directory. Once the files are selected they are then imported into the P3 internal database, updating and replacing similarly-named codes.
P3 Help When the Type of Code selection is set to 'Verbose Species, Run and Rear Codes', the Delete command button will permanently remove one or more selected codes. This may be useful for restricting the number of codes displayed in the Species Run and Rear tag detail field (verbose mode only). Removing these validation codes applies for all tag sessions and is not associated with any profile.
Appendix Frequently Asked Questions Questions Do I have to export all of my tag sessions from PITTag2 to import them into P3? I have the wrong File Name Prefix for a tag session, how do I fix it? How do I determine which tag sessions were modified using the replace feature? How do I transfer a group of detail records from one tag session to another? Are the digitizer maps I created in PITTag2 compatible with P3? Why is my digitizer map printing on two pages? Why is my digitizer tablet moving the mouse curso
P3 Help How do I determine which tag sessions were modified using the replace feature? The Replace feature can perform a global update of a particular field, meaning several tag sessions can be updated at once. To find out which tag sessions were modified, open the tag session manager and sort the Modified column by clicking on it (clicking on it multiple times will toggle the sort in ascending and descending order).
Appendix What's the fastest way of importing a large number of tag codes into a tag action? Use the Replace command instead of the Import command. The Replace command is much faster, however it will overwrite any existing tag codes with new ones. The Import command will append new tags with existing tags, however it takes much longer to process. Hardware Support This page lists information about known devices used with the P3 application when this help file was compiled.
P3 Help tablet. Uses a proprietary cable to communicate RS-232 and a NULL modem adapter. Electronic Balance CT600/1200, Navigator and Scout series. A&D FX/FY Model 3000 Balance www.andweighing.com Suggested device parameter settings: C1-1;C2-1; C3-2; C4-4; C5-1;C6-0. Sartorius Combics 1 www.sartorius.com Default RS-232 settings: 1200 baud Odd parity 1 stop bit Handshake: none The user needs to press Print button to send current reading to PC.
Appendix Card # SL0723116 D-Link DSB-H4 4Port Universal Serial Bus USB Hub D-Link USB to Serial Port Converter Cable Belkin Model F5U014-OE 4-port USB hub Baytech Multiport 525/529 H Series www.dlink.com Expands the number of USB ports on your PC only (not serial ports). This device requires AC power supply to other operate peripheral devices. www.dlink.com There are many manufacturers of these types of cables, however this 6 ft. cable comes recommended by other P3 users. www.belkin.
P3 Help Make sure the serial cable is connected and functioning properly. Some tag readers may need a NULL modem adapter (refer to the online Hardware page for more information). Verify the communication settings using the Terminal Window. Sometimes tag readers operating on DC power will not communicate with laptops running on AC power due to grounding issues. Try operating the tag reader on AC power and see if this resolves the issue.
Appendix Make sure there is a valid device configuration in the active profile for the tablet. For ASCII tablets, makes sure the data format is set to ‘ASCII 2000’. For WinTab tablets, make sure there isn’t additional WinTab software such as KYE that prevents applications from intercepting messages from the WinTab driver. Digitizer Tablet is Sending the Wrong Commands Make sure the digitizer map that is assigned in the device configuration is the same version as the printed map on the tablet.
P3 Help 8. When the display cycles back to “SET SERIAL PORT” you may turn the reader off. Testing the Destron 400 kHz Reader and Antenna Assembly 1. Connect the antenna to the reader, ensuring the connector pins are properly aligned and fully inserted. 2. Turn the reader on. 3. Press the MENU button repeatedly, cycling through the options until “SCAN ONLY” is displayed. 4. Press START/STOP button – the reader should change to “WORKING”.
Appendix Configuring Calcomp Drawing Board III This section describes how to configure a Calcomp Drawing Board III for use with P3. To set up the tablet: 1. Turn on configuration mode by clicking on the Config/Exit key. The configuration light will turn on and remain on while the tablet is in configuration mode. 2. Click on the Bank key where you need to work (A,B, or C). You can determine which bank you are in by placing the pointing tool over one of the Bank keys.
P3 Help 112
Index 4 Buffer 39 400 kHz Benchtop Tag Reader 109 C A CalComp Drawing Boards 5 A&D Balances 5 Capture Method 32 Accept 45 Change a Value 92 Access another database 3 Clear Tag Buffer 45 Action 15 Clip-file Verification 75 Actions 75 Combine Tag Sessions 94 Activating Tag Actions 21 Comma Separated Files Ad Hoc Search 87 Alert Message 15 Align Digitizer Map 45 Importing 62 Commands Session 45 Application Map Commands 84 Comment Map Commands 84 ASCII 2000 Serial Digitizer Tablets 17 Com
P3 Help Creating a Header Template 35 Detail Records 38 Creating a Search Query 87 Detail Validation 43 Criteria for Search 89 Detail Viewer 45 CSV Wizard 62 Device 12 Custom Validation Codes 100 Device Action 15 Customizing Header Field Labels 35 Device Commands 19 Customizing the installation 3 device configuration 109 Customizing the Tag Session Tool Bar 45 Device drivers 3 Device Map Commands 84 D Dash Length and Weight 45 Data Bits 14 Data Logging 9 Database Maintenance 102 DataMars ISO
Index Importing 73 E Electronic Balances 5 Header Templates 27, 35 Elementary Search Conditions 89 Hiding Optional Header Fields 35 Enable a Device 13 History of Uploaded Data 52 Enable a Device Action 15 Hubs 105 Enable Repeating Comments 45 I Enable Tag Actions 21 Importing Configuration Data 73 Entering Default Data 35 Importing Tag Files 58 EULA.
P3 Help Mandatory Weight 9 Organization 32 Map Commands 84 Overview 1 Maps 81 P Marking Procedures 2 Parity 14 Maximum Detail Records 43 PCMCIA 105 Maximum Lengths and Weights 21 PIT Tag Specification Document 2 Memory 4 PITTag2 Tag Sessions Importing 60 Merging Tag Sessions 94 Migratory Year 32 Port 14 Minimum Hardware Requirements 4 Portable Transceiver 5 Minimum Lengths and Weights 21 Post Tag Temperature 32 Mortality Information Print Search Results 91 Update 96 Print Tag Detail R
Index Release Date 32 Serial Port Device Settings 14 Release Notes 2 Session Commands 45 Release Site 32 Session Header 30 Release Temperature 32 Session Header Note 30 Remove Dot-Out Records 97 Session Header Templates 35 Removing the installation 3 Session Message 32 Rename a Tag Session 28 Set Repeating as Current 45 Repair Database 102 Settings 7 Repeating Comments 9, 45 Sort Tag Sessions 28 Replacing Data Values 92 Sound card 4 Reset Repeating Comments 45 Sound Events 23 Resolutio
P3 Help Tag Date 32 Time Check 45 Tag Detail 38 Transceivers 15 Tag Detail Field Reference 39 Transect 32 Tag Detail Validation 43 Troubleshooting Device Connections 19 Tag Detail Viewer 45 Troubleshooting Digitizer Tablets 108 Tag File 32 Troubleshooting Tag Readers 107 Tag File Prefix 9 Types of Devices 12 Tag Files and Tag Sessions 27 Types of Sound Events 23 Tag Method 32 U Tag Reader Devices 15 Tag Readers 5, 105 Tag Session Commands 45 Tag Session Header 30 Tag Session Header Templates 35 Tag
Index Web installation 3 WinTab digitizer tablets 5, 17 Web site 2 X Weight 9, 39 XON/XOFF 14 Windows 4 119
