Honeywell VoiceCatalyst 2.4 Release Notes
Pub:2020-01-17
What's in this Release
This release of VoiceCatalyst runs on Talkman A700 series devices and includes support for these devices, including the A710, A720, and A730. This software release is only for the A700 devices.
This release addresses several issues that exist in the previous release and supports the use of the SRX3 headset.
Help documentation is now available to customers online at https://help.honeywellaidc.com.
IMPORTANT
To prevent a potential lockup issue when using certain Cisco controllers, IPv6 support on the terminal has been disabled by default. It can be enabled by adding the following configuration setting:
[HKEY LOCAL MACHINE\Software\Vocollect\IPv6] "IsEnabled"=dword:1
Features and Improvements in This Release
Honeywell VoiceCatalyst 2.4 includes the following features and improvements.
New Features
SRX3 Headset Support
This release supports the use of the SRX3 headset. This headset is targeted for use in all environments. Contact your partner or business development manager for more information on the SRX3 headset.
Load Operator by Scan
This release enables loading an operator by scanning the bar code on the operator's badge. This feature is enabled for:
- Any Bluetooth scanner that is supported by and paired to the A700
- The A730 internal scanner
This feature is not enabled for serial scanners.
NOTE: See Honeywell VoiceConsole Online Help for instructions on creating an operator, loading a device profile, and loading a task.
Load Operator by Scan Instructions
- In VoiceConsole, ensure that the operator has an Operator Number.
- On the device, press the Operator button.
- Press the + or - button to scroll through the menu.
- When the device speaks the menu item, "Load operator by scanning badge," press the Operator button to select the item.
- Scan the bar code on the operator's badge. The bar code contains the operator number, which must match the Operator Number in VoiceConsole.
- The device speaks:
"Operator number <number> selected."
"Current operator is <name>."
"Loading operator."
"Loading voice templates."
"Please wait."
"Current operator <name>."
"Goodnight."
NOTE: If the operator number in the badge bar code does not match the Operator Number in VoiceConsole, then the device speaks, "No operator exists for operator <number>. Operation canceled. Goodnight."
Honeywell 8680i Wearable Mini Mobile Computer
This release supports the use of the Honeywell 8680i Wearable Mini Mobile Computer. See Honeywell 8680i Scanner for configuration instructions.
ECSs Included in This Release
The following issues were fixed in Emergency Customer Shipments (ECSs) and are included in this release.
ECS Description | Issue ID |
---|---|
007-ECS VCY_2.3.1_007-ECS creates a snapshot file when a 1450 error occurs in Bluetooth receive. | VCYCAT-1567 |
005-ECS This ECS resolves the issue of the A700 going to sleep or becoming unresponsive if it enters in and out of the Powered VMT too quickly. | VCYCAT-1456 |
008-ECS Improvements to Bulgarian TTS VCY_2.3.1_008-ECS includes a fix to improve a few Bulgarian systrings. | VCYCAT-1594 VCYCAT-541 VCYCAT-746 |
013-ECS VCY_2.3.1_013-ECS adds a filter in the driver for discarding packets with a zero source MAC address. | VOCWEX-737 |
004-ECS VCY_2.3.2_004-ECS adds support for SRX3 headset. | VCYCAT-1948 |
Issues Resolved in This Release
The following issue was resolved in this release.
Issue Description | Issue ID |
---|---|
Automatic Voice Load by Operator with Mixed Devices Automatic Voice Load by Operator using mixed devices is supported on VoiceConsole 5.2 and greater. A VoiceConsole ECS must be installed to support this feature:
| VOCECRT-4213 |
Customer Experience
- Use the Talkman Startup Tool to load profiles.
- VoiceConsole 5.0 and 5.1: This tool's functionality replaces the VoiceConsole 5.0 and 5.1 Load selected profile with cable option in VoiceConsole. The old functionality within VoiceConsole may still work, but the new tool is the mechanism moving forward. The Talkman Startup Tool must be accessed from outside VoiceConsole.
- VoiceConsole 5.2 or greater: Talkman Startup Tool is integrated and launches when Load selected profile with cable is chosen.
- Customers can use the same device configuration files on both A700 and A700x series devices.
- TouchConfig has the following limitation:
- Incompatible protocols prevent an A700x from transferring the config.vrg file either to or from an A700.
- Honeywell recommends creating a channel list when setting up the profile in VoiceConsole. Without a channel list, the radio scans all channels. With a channel list, the radio only scans the listed channels which improves performance, reduces interference, and reduces latency. This advice is applicable to all Talkman devices (A700x, A700, A500).
- Ensure Bluetooth peripherals have properly charged batteries. When a peripheral battery has a low charge, it is possible the peripheral may not stay connected. This advice is applicable to all Talkman devices (A700x, A700, A500).
- Honeywell recommends users of wired headsets allow the Talkman device to power on before donning the headset and to remove the headset before powering off the device. There may be a popping noise as the device powers on or off and task settings (i.e.: audio_shift_db) may make the popping noise more prominent. This advice is applicable to all Talkman devices (A700x, A700, A500).
Known Issues
Issue Description | Issue ID |
---|---|
"Headset Maintenance is Needed" Message If the SRX2/SRX3 headset plays this message when used in a freezer environment, contact your support representative for information. Do not return the headset to Honeywell unless directed to do so by your representative. | YETI-3 |
Mode Switch Causes Load Fail or Device Hang During a mode switch:
| |
Spell Tags Disabled for Languages Other Than English Spell tags are disabled for all languages other than English. If you have non-English tasks with spell tags, operators will not hear the prompts in the way that they may expect. | NGVPL-3337 |
Power Supply Version Unpopulated When using an A700 VMT, the power supply version field in device and VoiceConsole logs is unpopulated. | |
Pending File Loads with Vehicle Mounted Configuration If a device has a pending task, operator, or device profile load that would normally occur once the device is placed in a charger, if an A700 device is moved to the vehicle-mounted power supply, the pending load may not occur. | |
TTS Slowdown If you slow the TTS down on the device below defaults and notice issues scanning, you may need to increase the BarcodeMaxTimeScanAhead and BarcodeBufferDataTimeout parameters to accommodate the additional amount of time required by the slowing down of the TTS. | |
Failure to Shut Down If you attempt to shut down an A700 device and the device state LED remains in the rotating red state and fails to shut down completely, remove the battery and replace it. | RBIRDCLI-2173 |
A700 Becomes Unresponsive The A700 can become unresponsive and requires a power cycle to restore operation. | VVCAT-2253 |
Prompt to Train Vocabulary After Receiving Message If you have disabled the control word "say again", and the operator receives a message from VoiceConsole, then restarts the task, the operator will be prompted to train "say again". Workaround: Do not set parameter DisableControlFunction SAY AGAIN to 1. | RBIRDCLI-2120 |
Switching to TaskBuilder Task Doesn't Retain Templates If you load a VoiceArtisan task and need to train templates, train those templates, then load a TaskBuilder task with the same vocabulary, you will be prompted again to train the same templates. | RBIRDCLI-2140 |
Profile Load Percentages Fluctuate When loading a device profile and viewing the View Action Items page in VoiceConsole, you may see the percentage of completeness go from a higher percentage to a lower percentage. Workaround: Wait until the profile is completely loaded. This is a display issue and will not affect the profile load. | MBL-2598 |
Device Profile Shows Incorrect Platform Version After loading a device profile with one platform version to a device that has a different platform version already loaded, clicking on the profile link will display the new platform, not the one already loaded. Workaround: Turn the device off and on again. | MBL-2593 |
Configuration Only Profile Load Not Displayed in VoiceConsole If only a configuration file (.cci) is loaded onto a device through TouchConfig or serial loading, the device profile displayed in VoiceConsole is not updated. The displayed information is only updated if a complete device profile is loaded. | RBIRDCLI-1646 |
Double-byte Characters Not Updating Device Display If a pairing name contains double-byte characters, and an operator or task is loaded to the device, these pieces of information are not updated in VoiceConsole. Workaround: Use only single-byte characters for naming pairings. | RBIRDCLI-1574 |
Delay When Shutting Device Down There may be a delay when shutting down a device out of Wi-Fi range when VoiceConsole logging is enabled. Workaround: Turn the device off while in Wi-Fi range or disable VoiceConsole logging. | RBIRDCLI-1583 |
VoiceCatalyst Incompatibility with Newer Devices Versions of VoiceCatalyst prior to 2.0 may be incompatible with the hardware in newer devices. This causes the upgrade to fail and the device will revert to the previous version of VoiceCatalyst. Note, however, that the failure may not occur until the end of the profile load. Workaround: Upgrade to VoiceCatalyst 2.0 or newer. | |
Delay on Device's First Power On after Profile Load We now erase the flash file system as part of the process of loading profiles, configuration files or firmware. This insures that the software running on the device and the files loaded onto the device are compatible. However, this will cause approximately a 45-second delay from the time the operator powers on the device to the time he first hears a prompt. This occurs only the first time the operator powers on the device. | |
Voice Not Changing If you place a Talkman device that has a currently associated operator, task and voice in the charger, then load a new operator, task and voice from VoiceConsole to that device, the operator and task will load correctly, but the voice will not change. Workaround: Manually load the voice. | RBIRDCLI-759 |
Incorrect Gender Voice When you switch back to a previously loaded operator after having loaded a different operator and voice, the voice for the previously loaded operator may speak in a different gender voice than it is set to speak. Workaround: If this occurs, reload the operator. | RBIRDCLI-756 |
Device Attempting to Pair with Headset After Breaking Pairing If you have the auto-pairing feature enabled and you break the pairing through pressing the SRX2's + and - buttons, the device will search for headsets and will likely pair with the headset again. Workaround: Set SRXAutoPairEnable to 0. | RBIRDCLI-980 |
Device Not Going into Auto-Pairing Mode If you have the auto-pairing feature enabled and you clear the pairing through VoiceConsole, the device will not go into auto-pairing mode to locate the headset again. Workaround: Do not clear the pairing through VoiceConsole. If you do, press the device's Play/Pause button twice in a row to reset the device to auto-pairing mode. | RBIRDCLI-1043 |
Previous Operator's Name Spoken If you load a new operator to a voice application that speaks the current operator's name in a prompt, put the device to sleep immediately after that prompt was spoken, then load another operator, when you turn the device back on, you will hear the original operator's name. If you go into the prompt that speaks the operator's name again, you will hear the current operator's name. Workaround: Consider developing an operator changed callback for prompts where this could cause confusion. See the VoiceArtisan help for more details. | RBIRD-278, RBIRDCLI-991 |
Control Words in English with Non-English Voice If you load a non-English voice to the device and train templates, when you are prompted to train the control words, these will be in English. Workaround: Be sure to translate the control words along with the rest of the application's vocabulary. Use the Phonetic Words tab in the Voice Configuration editor in VoiceArtisan to provide the correct language's substitutions. | RBIRDCLI-787 |
MaxSpeakAsNumber Considerations The MaxSpeakAsNumber parameter determines the number of digits that will be spoken as a number, for example twenty-three rather than two, three. If you set the MaxSpeakAsNumber parameter to something other than an integer, rather than changing to the default value of 99, the parameter will be set to 0. Also, the MaxSpeakAsNumber parameter now has a range of 0 to 999,999,999. | RBIRDCLI-183 |
Restarttask Parameter Persisting With VoiceCatalyst, if you set the restarttask parameter to 1 for an operator, then remove that parameter from the operator, when you replace the device in its cradle, both the operator and the task will load as if that parameter still exists. Once the operator is manually loaded using button presses or a manual load through VoiceConsole, the parameter will be cleared. | RBIRDCLI-184 |
Loading a Task When ODRs are Present If there are Output Data Records (ODRs) present on a device and you attempt to load a task, the task load will fail because the ODRs are being preserved. The worker will hear a message that the task load failed, but this will not appear in VoiceConsole. Workaround: Load the task after the ODRs are transmitted and cleared from flash. | RBIRDCLI-646 |
Failing to Connect to Restricted Network with PEAPvO Security If you have an unrestricted network with PEAPvO security configured and the device is given incorrect credentials for that network, the device will not connect to the restricted network to obtain the proper credentials. Workaround: Try to connect using the correct credentials. | RBIRDCLI-563 |
Operator Load Failing After Changing from Restricted to Unrestricted Network Using operator-based EAP, if you change from restricted network to unrestricted network credentials, and load the operator, the operator load may fail due to dropping the original network connection. Workaround: Attempt to load the operator again. | RBIRDCLI-975 |
Failing to Load Operator's Work Application After Training Application If the VoiceConsole server is configured to use HTTPS, the operator's work application will not automatically be loaded when he completes the Vocollect Training Application. Workaround: Use the device's buttons to load the work application. | VSCVAAPPS-3 |
Operator Name Not Appearing in VoiceClient Mode When in VoiceClient mode, the operator name is not shown in some Operational Acuity data streams after startup. | VVCAT-274 |
Output Audio Stuttering with Wired Headset Operators using the SR20 (or other wired headsets) may experience output audio stuttering or stammering. This is more common if the TTS speed is set near or at the highest speed possible. If stuttering occurs, set the TTS speed to a lower level. | VVCAT-2259 |
Supported Environments
Component | Minimum / Required Version |
---|---|
Platform | WEX-90 |
Platform SDK | WEX-90 |
VoiceConsole | Version 5.0 or greater is required. Version 5.2.1 or greater with 001-ECS is required to support the SRX3 headset. |
TaskBuilder Tasks | All versions are supported. |
VoiceArtisan Voice Applications | All versions are supported for A700; however, for sites that also use A700x, see VoiceArtisan Voice Applications in Mixed Deployments. |
Customer Agent | 1.5.1 or greater |
VoiceArtisan / VCE | All versions / version 2.3.1 or earlier |
SRX2 Firmware | Tested with firmware version 3.12 |
SRX-SL Firmware | Tested with firmware version 5.12 |
SRX3 Firmware | Tested with firmware version 6.05 |
Peripherals Supported | See Peripherals Tested with A700 in this Release for information about supported peripherals, the peripherals tested with the A700, and instructions for using the tested peripherals. |
Talkman Startup Tool
TIP
In VoiceConsole 5.2 or greater, the user can access the Talkman Startup Tool by selecting Load selected profile with cable.
Use the Talkman Startup Tool to load profiles to new devices. This section assumes:
- The user has created an appropriate profile for the A700 in VoiceConsole.
TALKMAN STARTUP TOOL
1. Copy the Talkman Startup Tool zip file from the DVD to your computer.
2. Extract the zip file.
3. Click on the exe file to launch the Talkman Startup Tool.
4. Enter the server address of the VoiceConsole server.
VoiceConsole URL: http://100.100.100.100:9090/VoiceConsole/
5. Enter the username and password for VoiceConsole.
The Talkman Startup Tool reads the sites and profiles from VoiceConsole.
NOTE: The Talkman Startup Tool does not store the VoiceConsole password.
6. Ensure the correct site is selected from the list in the upper left of the screen.
7. The A700 must be off. Connect the device to the computer using a standard Micro-USB cable. The USB cable connects to the A700 maintenance port. This port is located under the flap on the side of the A700 next to the Play/Pause button as shown below.
If the A700 powers on when connecting the USB cable, remove the cable and power the A700 off.
Then press and hold the operator button while reconnecting the USB cable.
8. Press and hold the Operator button on the device.
9. Press and release the Play/Pause button.
10. When the device's LED turns solid green, release the Operator button.
11. When the device is recognized, the device serial number and device image are displayed.
DEVICE INFORMATION
Serial Number: 7518490305
12. Open the Settings menu and select the profile load type. The VoiceConsole Settings will be populated with what was entered when opening the utility.
13. Select the profile to load. Information about the selected profile is displayed.
14. Click Begin Profile Load.
If the device type does not match the profile, an error message is displayed and the Begin Profile Load button is not active.
15. The number of voice components to load will be displayed.
16. Click Start.
The progress of the component loading is displayed.
17. When complete, the device reboots. The user should follow the instructions and place the device in the charger to complete the profile load.
VoiceArtisan Voice Applications in Mixed Deployments
When a site deploys both A700 and A700x series devices, some VADs may need to be updated for the A700x, because it uses Python 3.6. Honeywell provides the Voice Application Compatibility Tool (VACT) to check VADs for Python constructs that may need rework for the A700x.
NOTE: When making changes, it is desirable that the VAD is compatible with both the A700x and A700 devices for site mixed deployments.
See the Release Notes for Honeywell VoiceCatalyst 4.x for information on the A700x, Python 3.6 VAD compatibility, and the Voice Application Compatibility Tool.
Peripherals Tested with A700 in This Release
The A700 continues to support the peripherals that are supported in Honeywell VoiceCatalyst 2.3.2. The peripherals in this section are those that were tested for VoiceCatalyst 2.4.
Bluetooth Peripherals
Pairing Bluetooth peripherals is most reliable when pairing via VoiceConsole. Honeywell recommends taking available precautions for secure Bluetooth communications. See the Voice Solutions Network and Security Guide for Bluetooth security recommendations. Manual pairing of peripherals is possible in some instances (more likely if the device and peripheral are close together), but may take several attempts. Peripheral-specific information is included below.
Bluetooth Headsets
Headset Firmware
During A700 testing, the following headset firmware versions were used. Headsets should be upgraded to these versions.
- SRX2: firmware version 3.12
- SRX-SL: firmware version 5.12
- SRX3: firmware version 6.05
Obtain the latest headset software from Honeywell or your Honeywell reseller and use the Honeywell Accessory Update Utility to upgrade your headsets.
SRX2/SRX3 Headset
To pair an SRX2/SRX3 headset with an A700 using TouchConnect:
- Turn on the SRX2/SRX3 headset.
- If the headset's LED is blinking blue, it is currently paired to a device. Clear the pairing by pressing the + and – buttons simultaneously on the headset.
- If you are sharing headsets at your site, you must first obtain the operator ID by reading the headband:
- Touch area of the SRX2/SRX3 t-bar (headband) with the symbol to center of the raised oval on the side of the A700 with the symbol, until the device state (ring) indicator blinks green. This associates the operator's headband to the device enabling VoiceConsole to recognize the operator.
- Touch the side of the A700 device that has the symbol and the oval area of the SRX2/SRX3 keypad section together, aligning the ovals on each and holding them together steadily, until the A700 device state (ring) indicator blinks green. The headset sounds three ascending tones on connection and the headset's LED flashes blue slowly after connection. Note that there is a 30-second timeout after a headband is recognized in step one. You must pair the electronics module within 30 seconds from associating the headband for full functionality.
- If you are not sharing headsets at your site, you only need to pair the device to the SRX2/SRX3 electronics module:
- Touch the side of the A700 device that has the symbol and the oval area of the SRX2/SRX3 keypad section together, aligning the ovals on each and holding them together steadily, until the A700 device state (ring) indicator blinks green. The headset sounds three ascending tones on connection and the headset's LED flashes blue slowly after connection.
When the device starts the task, VoiceConsole recognizes the pairing.
NOTE: If TouchConnect pairing fails as indicated by the A700 device state (ring) indicator blinking red, the workaround is to power off the headset and attempt to re-pair the device.
SRX-SL Headset
To pair an SRX-SL headset with an A700 using TouchConnect:
- Turn on the SRX-SL headset.
- If the headset's LED is blinking blue, it is currently paired to a device. Clear the pairing by pressing the Volume Up and Volume Down buttons simultaneously on the headset.
- Touch the side of the A700 device that has the symbol and area of the SRX-SL eModule between the power button and LED together, holding them together steadily, until the A700 device state (ring) indicator blinks green. The headset sounds three ascending tones on connection and the headset's LED flashes blue slowly after connection.
When the device starts the task, VoiceConsole recognizes the pairing.
NOTE: If TouchConnect pairing fails as indicated by the A700 device state (ring) indicator blinking red, the workaround is to power off the headset and attempt to re-pair the device.
Bluetooth Scanners
The Honeywell 8680i, Intermec SF51, and Intermec SR61B Bluetooth scanners have been tested with the A700.
Honeywell 8680i Scanner
NOTE: Refer to the 8680i User Guide available at www.honeywellaidc.com for additional information and configuration bar codes.
NOTE: For sites that are using both A700 and A700x series devices, the A700x supports TouchConnect pairing with the 8680i scanner, but the A700 does not support this.
A700 Device as Initiator
Configure 8680i Scanner
- The 8680i scanner must be set to Host Reconnect Mode (the 8680i will attempt to connect to the A700 host, and if disconnected the A700 will manage the reconnection).
- The 8680i must be configured to add termination characters (i.e.: <CR><LF>).
- Restore factory defaults by scanning the Remove Custom Defaults and Activate Defaults bar codes.
- Scan the Host Reconnect Mode bar code.
- Scan the bar code to add a carriage return and line feed as termination characters.
Additional information:
- The 8680i User Guide contains bar codes to set other combinations of termination characters. To add a different termination suffix, scan the SUFBK2 (Add Suffix) bar code, then scan the bar codes for the desired suffix.
Configure task and VoiceConsole
- Set the following advanced parameter in Task config
barcodeport = bt_scan - Turn on Bluetooth on the A700.
- View the properties of the A700 and ensure Bluetooth is enabled. If it is not enabled, click Edit this device and set Bluetooth Enabled to "enabled".
- Select Pair this device with a peripheral.
- For Pairing type select "Bluetooth Scanner".
- For Connection Mode select "Device initiates connection with peripheral".
- In the Bluetooth Address field enter the Bluetooth MAC address of the scanner. This 12-character ID is labeled "MAC ID" and is found on the side of the battery unit of the scanner.
- For Security select "Enabled."
- For Security Key enter "0000".
- Click Pair with peripheral to initiate pairing.
8680i Scanner as Initiator
- The 8680i scanner must be set to Scanner Reconnect Mode (the scanner will continuously attempt to connect to the A700 host, and if disconnected the scanner will manage the reconnection).
- Restore factory defaults by scanning the Remove Custom Defaults and Activate Defaults bar codes.
- Scan the Scanner Reconnect Mode bar code.
IMPORTANT: The bar code above is different from the one included in earler versions of VoiceCatalyst 4.x Release Notes.
- For an 8680i running firmware version EE000071BAC or greater - this bar code is required.
- For an 8680i running earlier versions of the firmware – this bar code is recommended although the bar code provided in earlier versions of the release notes does work with these earlier firware versions.
3. Scan the bar code to add a carriage return and line feed as termination characters.
4. For scan-based pairing, create a pairing bar code for each A700. The bar code begins with {FNC3}LnkB followed by the 12-digit Bluetooth MAC address for the A700:
Additional information:
- The 8680i User Guide contains bar codes to set other combinations of termination characters. To add a different termination suffix, scan the SUFBK2 (Add Suffix) bar code, then scan the bar codes for the desired suffix.
- Use the Bluetooth Disconnect bar code to unlink the scanner from the A700.
Configure task and VoiceConsole
- Set the following advanced parameter in Task config
barcodeport = bt_scan - Turn on Bluetooth on the A700.
- View the properties of the A700 and ensure Bluetooth is enabled. If it is not enabled, click Edit this device and set Bluetooth Enabled to "enabled".
- Select Pair this device with a peripheral.
- For Pairing type select "Bluetooth Scanner".
- For Connection Mode select "Device listens for peripheral connection".
- Scan the LnkB bar code created above to initiate pairing.
- On the 8680i, observe the Bluetooth symbol in the user window status screen. The symbol will change from cross out or flashing to continuously lit when the 8680i is paired with the host A700.
Intermec SF51 and SR61B Scanners
Configure SF51 or SR61B Scanner
To use either of these scanners with an A700, you need to generate and scan configuration bar codes:
- Install the following on your PC:
- EasySet (to generate configuration bar codes for the scanner), download from Software > Barcode Scanners > Printer Drivers > Intermec Windows driver using the link below
These items can be downloaded from the Honeywell Technical Support Downloads portal: https://hsmftp.honeywell.com. - InterDriver_7.4.3_M-3 (to allow the PC to detect the PB50 printer when the printer is connected to the PC), download from Software > Printers > Printer Drivers > Intermec Windows driver using the link below
These items can be downloaded from the Honeywell Technical Support Downloads portal: https://hsmftp.honeywell.com.
- EasySet (to generate configuration bar codes for the scanner), download from Software > Barcode Scanners > Printer Drivers > Intermec Windows driver using the link below
- You must have an account to download software. Create an account if you don't already have one.
- If you have not previously installed the Honeywell Download Manager, you must download and install it before downloading these items.
- After installing EasySet, start the program and select your scanner model.
- Generate a restore factory settings bar code by selecting 2. Reset all parameters > Reset factory defaults (SR61B) or administrator reset factory defaults (SF51).
- Scan the bar code, either from onscreen or print the bar code.
- Use EasySet to generate a security enabled bar code by selecting 3. Interface > Bluetooth > Security > Enable.
- Scan the bar code.
- Optional: generate and scan a bar code to set a custom pin by selecting 3. Interface > Bluetooth > Security> Compose PIN:.
Configure task and VoiceConsole
- Set the following advanced parameter in Task config
barcodeport = bt_scan - Turn on Bluetooth on the A700.
- View the properties of the A700 and ensure Bluetooth is enabled. If it is not enabled, click Edit this device and set Bluetooth Enabled to "enabled".
- Select Pair this device with a peripheral.
- For Pairing type select "Bluetooth Scanner".
- For Connection Mode select "Device initiates connection with peripheral".
- In the Bluetooth Address field enter the Bluetooth MAC address of the scanner. This 12-character ID is labeled "MAC ID" or "BDA" and is found on a label on the scanner.
- For Security select "Enabled."
- For Security Key enter "0000" or the PIN entered when generating the custom PIN bar code.
- Click Pair with peripheral to initiate pairing.
Bluetooth Printers
Intermec PB50 Printer
Configure PB50 Printer
The PB50 must be configured to enable authentication. For more information on the process below, refer to the PB50 and PB51 User Guide available at honeywellaidc.com.
- Install the following on your PC:
- PrintSet 4 utility (to configure PB50 settings), download from Software > Printers > Printer Applications > PrintSet 4 using the link below
- InterDriver_7.4.3_M-3 (to allow the PC to detect the PB50 printer when the printer is connected to the PC), download from Software > Printers > Printer Drivers > Intermec Windows driver using the link below
These items can be downloaded from the Honeywell Technical Support Downloads portal: https://hsmftp.honeywell.com.
- You must have an account to download software. Create an account if you don't already have one.
- If you have not previously installed the Honeywell Download Manager, you must download and install it before downloading these items.
- After the items above are installed on the PC, power on the PB50 printer.
- Attach the PB50 printer to the PC using the printer cable with a serial port on one end and a printer port on the other end.
- Open the PrintSet 4 program.
- Select File > Add Printer. The Add Printer Wizard starts.
- In the Add Printer Wizard, select Connection Type as "Serial".
- The wizard detects the connected PB50 printer and it is then shown under "My Printers" in PrintSet 4.
- Double-click Bluetooth in the Properties tab.
- In the Bluetooth Settings window, complete these items under Security:
- Require Security = "Enable"
- Passcode = (user selected 4-digit PIN)
TIP: You may wish to record the MAC address (shown as Device Address in this window) as the printer's MAC address is necessary to complete the paring process.
- Select Apply to save and close the Bluetooth settings.
- Select Apply under Printer Tasks.
- The settings are applied to the PB50 printer and the printer reboots.
If you want to confirm printer settings, delete the PB50 printer from PrintSet 4 then add it again to view the latest configuration.
Configure task and VoiceConsole
- Set the following advanced parameter in Task config
printerport = bt_print - Turn on Bluetooth on the A700.
- View the properties of the A700 and ensure Bluetooth is enabled. If it is not enabled, click Edit this device and set Bluetooth Enabled to "enabled".
- Select Pair this device with a peripheral.
- For Pairing type select "Bluetooth Printer".
- For Connection Mode select "Device initiates connection with peripheral".
- In the Bluetooth Address field enter the Bluetooth MAC address of the scanner. This 12-character ID is found
- From the PB50 display under Bluetooth settings
- From PrintSet 4 (when the PB50 is attached to a PC) under Bluetooth Settings in the Device Address field.
- For Security select "Enabled."
- For Security Key enter the key entered when enabling authentication for the PB50 in PrintSet 4.
- Click Pair with peripheral to initiate pairing.
Serial Peripherals
Serial Scanners
To use a serial scanner with the A700:
- Set the following advanced parameter in Task config
barcodeport = blue - Connect the serial scanner.
Training Devices
QTERM-G55
The QTERM-G55 training device can be used with the A720. Refer to the online instructions for using the QTERM-G55.
NOTE: The QTERM-G55 has reached end-of-life. Honeywell recommends the Dolphin CT60 for training with the A700.
Honeywell Dolphin CT60
The Honeywell Dolphin CT60 is an Android™™™-based hand-held computer that can be used as a training device. For CT60 configuration information refer to the product documentation at https://www.honeywellaidc.com/products/computer-devices/handheld/dolphin-ct60.
To use the CT60 as a training device:
- Configure the CT60 to connect to your network.
- Open the Chrome™™™ browser on the CT60.
- Enter the IP address of the A700 in the browser address bar on the CT60.
- Tap on the Train Words icon.
Getting Help
Product documentation is available at https://help.honeywellaidc.com.
NOTE: If you purchased Vocollect equipment from a reseller, please contact the reseller.
For order placement or customer service inquiries, contact Honeywell – Vocollect Customer Service at:
- Customer Service Email: acshsmvocollectrequests@vocollect.com
- Customer Service Phone (US): +1-866-862-6553
- Customer Service Phone (Outside the US): +1 412-829-8145
For returns or to check the status of an RMA, contact Honeywell – Vocollect Customer Service at:
- Email (US): acshsmvocollectrma@honeywell.com
To report Vocollect system support incidents or related technical issues, contact the Honeywell Technical Support Center at:
- Technical Support Email: workflowsolutionsupport@honeywell.com
- Technical Support Phone (US): +1 866-862-7877
- Technical Support Phone (Outside the US): +1 412-829-8145
To contact Vocollect Europe, Middle East, and Africa:
- Customer Service Email: acshsmvocollectcustomerservicesemea@honeywell.com
- Customer Service Phone: +44(0) 1628.55.2903
- Technical Support Email: workflowsolutionsupport@honeywell.com
- Technical Support Phone: +44 (0) 1628.55.2902
For sales or any other inquiry, please contact Vocollect at ACSHSMVocollectInfo@honeywell.com or 412.829.8145.
Honeywell Vocollect Solutions
703 Rodi Road
Pittsburgh, PA 15235-4558 USA
Phone +1 412-829-8145
Fax +1 412-829-0972
ACSHSMVocollectInfo@honeywell.com
www.vocollect.com
info@vocollect.com
Honeywell Vocollect Solutions Europe
Gemini House
Mercury Park
Woodburn Green
High Wycombe
United Kingdom
Honeywell Vocollect Solutions Japan
New Pier Takeshiba South Tower 20F
1-16-1 Kaigan, Minato-ku,
Tokyo 105-0022, Japan
Phone: +813 6730-7234
Fax: +810 3769-5608
vocollect.japan@honeywell.com
Honeywell Vocollect Solutions Asia-Pacific
2903 Sino Plaza, 255-257 Gloucester Road
Causeway Bay
Hong Kong
Phone: + 852 3915-7000
Fax: + 852 3051-8209
ACSHSMVocollectAsiaPacific@honeywell.com
Honeywell Vocollect Solutions Latin America
North: +52 55-5241-4800 ext. 4915
South: +1 412-349-2477
ACSHSMVocollectLatin_America@honeywell.com
Honeywell Vocollect Solutions Singapore
151 Lorong Chuan
#05-02A/03 (Lobby C)
New Tech Park
Singapore 556741
Main Phone: +65 6303-2100
DID: +65 6305-2369
ACSHSMVocollectsingapore@honeywell.com
Honeywell Vocollect Solutions Europe
HP10 OHH UK
Phone: +44 (0)870-600-8255
ACSHSMVocollectEMEA@honeywell.com
Third Party Software
The information for software packages included in this version of VoiceCatalyst are located at https://help.honeywellaidc.com/Content/ThirdPartyLicenseAgreements.htm.
Disclaimer
Honeywell International Inc. (“HII”) reserves the right to make changes in specifications and other information contained in this document without prior notice, and the reader should in all cases consult HII to determine whether any such changes have been made. The information in this publication does not represent a commitment on the part of HII.
HII shall not be liable for technical or editorial errors or omissions contained herein; nor for incidental or consequential damages resulting from the furnishing, performance, or use of this material.
This document contains proprietary information that is protected by copyright. All rights are reserved. No part of this document may be photocopied, reproduced, or translated into another language without the prior written consent of HII.
Copyright © 2020 Honeywell International Inc. All rights reserved.
Other product names or marks mentioned in this document may be trademarks or registered trademarks of other companies and are the property of their respective owners.
Web Address: www.honeywellaidc.com
Patents
For patent information, please refer to www.hsmpats.com.