The Device Heard Something That Wasn't Said

The recognizer produces an output when the operator did not speak a word in the vocabulary of the recognizer. This can result from the worker having a side conversation without putting the Honeywell Voice device to sleep or from background noise due to machinery or other workers.

The device is more likely to hear non-vocabulary words when the worker is using short vocabulary words, where there are long waits at a node for operator input, and where there is a large number of vocabulary words available at a prompt.

This condition is also more likely when a worker trains his templates in a noisy environment, with poor microphone position, or noises or side speech make it into the templates during training.

Possible Causes

If the resolution requires an application or system change that could affect all operators, the resolution is labeled with “SITE:".

Poor microphone placement

Emphasize proper microphone placement. Proper placement maximizes the amplitude of the operator’s speech compared to that of the background noise.

Excessive dirt embedded in microphone grill

Replace the headset or send it in for repair.

The application is used in an atypical noise environment

SITE: An increase of one of the sensitivity parameter values may help, especially if it is still set to the default value. Increase the appropriate value (according to which recognizer you are using) in either the Bluestreak_Decode_Sensitivity or PnG_Decode_Sensitivity parameter. Honeywell strongly recommends that you work with your Honeywell certified support representative to determine if a change to this parameter is necessary.

Poor template

If the same word is repeatedly being inserted, instruct the worker to retrain the word using the "update train" method.

Worker speech not related to workflow

If the words being inserted are mainly due to the worker having side conversations, encourage the worker to put the device to sleep before speaking. Make sure he’s aware that he can use either the button or the voice commands "Talkman sleep" and "Talkman wakeup".

Static caused by a poor connection between the headset and the device or a bad headset

See Troubleshooting General Recognition Problems for more information.

Short vocabulary words were used in the application

If update training does not appear to help, instruct the worker to train the word as a different word. Longer words are less likely to be misrecognized.

SITE: If it seems short words used in the application are frequently being misrecognized by multiple operators, it may be necessary to change them to longer words site-wide. Your Honeywell certified support representative can assist with changing this within the software or performing a phonetic substitution configuration change.

This can only work properly for words not used in an embedded context

Breath noises are being mistaken for speech

Make sure the operator is using a windscreen and positions the microphone out of the breath stream.

The application has too many unused words

SITE: If there are extra words which are not used, these should be considered for removal. See the DisableVocabWord_{word} parameter. This should be done with the assistance of a Honeywell certified support representative.

Customer expectations are atypical

Some amount of repeating is normal. See Other Non-Recognition Issues for more information.

The design of the application or the way the application is used is not appropriate for this site

Depending on the problems encountered, the application or processes could be better optimized so that fewer problems are encountered. Work with your Honeywell certified support representative to determine if application design may be increasing the likelihood of recognition problems.