Overview
When a printed ticket shows “Value Error”, it means the Sentry firmware cannot parse the ticket’s monetary value correctly. This commonly occurs when the ticket format from the Phoenix or Reliance Tools app uses value formatting the firmware does not recognize. This article explains how to update the parsing settings so the value is read and encrypted correctly.
Examples shown below are identical for both Phoenix and Reliance Tools.
Test tickets printed from the Phoenix or Reliance Tools apps will always print with a Value Error.
System Requirements
- A Phoenix SEN02 or Reliance model printer
- The Phoenix Tools or Reliance Tools application installed on a PC
- A ticket sample that shows the current format
Fix for Single Value Tickets
Use this method if the ticket has a single line showing its value, preceded by a currency symbol (for example, $100).
- In the Tools app, click Sentry on the right panel.
- Under Parsing Mode, select Custom Keyword.
- In the Parsing Keyword field, enter the character or string that appears immediately before the monetary value (for example,
$). - Click Apply.
- Print a test ticket from the intended machine. Confirm the ticket no longer displays “Value Error” and the value is recognized.
Fix for Embedded Value Phrase Tickets
Use this method if the value is part of a specific phrase (for example, “Good for $100”).
- In the Tools app, click Sentry on the right panel.
- Under Parsing Mode, select Custom Keyword.
- In the Parsing Keyword field, enter the exact word or phrase that appears immediately before the value.
Example: If the ticket shows “Good for $50”, enter “Good for”. - Enable Case Sensitive to ensure the keyword matches the ticket text exactly.
- Click Apply.
- Print a test ticket from the intended machine. Confirm the ticket no longer displays “Value Error” and the value is recognized.
If you are using a Pulse configuration on a Phoenix printer, ensure the Data option is selected on at least one line in the Layout tab. This ensures the ticket prints with a value.
Troubleshooting
If the ticket still shows a Value Error:
- Verify the parsing keyword exactly matches the ticket text. Case sensitivity applies if enabled.
- Check for unexpected whitespace or special characters in the ticket text.
- Try alternate keywords, such as including a space before or after the word.
Comments
0 comments
Please sign in to leave a comment.