Specifications
Table Of Contents
- Overview
- Configuration
- Configuration Profiles
- General Profile Settings
- Configuring Devices
- Activating Tag Actions
- Validation Constraints
- Audible Alert Sound Events
- Data Collection and Validation
- Importing and Exporting
- Tools
- Tag Actions
- Tag Action Manager
- Tag Action Settings and Commands
- 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.
- Tag Actions and Data Entry
- Digitizer Maps
- Searching Data
- Replacing Data Values
- Merging Tag Sessions
- Dot-Out Wizard
- Remove Dot-Outs
- Duplicate Viewer
- Validation Codes
- Database Maintenance
- Tag Actions
- Appendix
- Frequently Asked Questions
- Hardware Support
- Troubleshooting Common Tag Reader Problems
- Troubleshooting Common Digitizer Tablets Problems
- Digitizer Tablet Doesn't Register Pen Clicks
- WinTab Digitizer Tablet Won't Communicate with a PC
- ASCII Digitizer Tablet Won't Communicate with a PC via Serial Port
- Digitizer Tablet doesn't Communicate with P3
- Digitizer Tablet is Sending the Wrong Commands
- Digitizer Tablet is Sending Wrong Lengths
- Digitizer Tablet Hangs P3 when Connected via Baytech Multiport
- Operating the Destron 400 kHz Benchtop Tag Reader
- Configuring Calcomp Drawing Board III
- Index
P3 Help
24
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.
Only sound events that have been previously assigned an external wave file can be
enabled within a profile.
To enable a sound event within a profile, click on the check box under the Enabled
column for the specific Sound Event.
Types of Sound Events:
Sound Event Description
Accept
Record
Fires when the current detail record is accepted, either by
the user manually pressing the accept
command or a new
tag code generated the auto accept
event.
Action Event Fires when an action Lookup event occurs.
Attention A general purpose sound event, usually when the user
must respond to a dialog box before processing can
continue.
Constraint
Violation
Fires whenever a validation constraint occurs while
processing the current detail record.