Intermec PX4i Fingerprint Developer's Guide (old) - Page 146

Standard Error Handling, Choosing an Error Message Format

Page 146 highlights

Chapter 8 - Error Handling Standard Error Handling In most application programs, it is useful to include some kind of error handler. The complexity of the error handler depends on the application and how independently the printer works. For flexibility, Intermec Fingerprint includes a number of tools for designing custom error handling routines. Fingerprint includes hardware-based error handling, such as reporting "out of media" errors when the Print or Feed keys are pressed during a print job, or if batch printing is interrupted by pressing the Print or Pause keys. Additionally, during program execution, Fingerprint performs these checks: • Syntax Check. Each program line or instruction received on the standard IN channel is checked for possible syntax errors before it is accepted. If two-way communication is established, error messages (for example, "Feature not implemented" or "Font not found") are transmitted to the host on the standard OUT channel. • Execution Check. Any program or hardware error that stops the execution is reported on the standard OUT channel. In case of program errors, the number of the line where the error occurred is also reported (for example, "Field out of label in line 110"). After the error has been corrected, the execution must be restarted by means of a new RUN statement, unless the program includes a routine for dealing with the error condition. Note: For two-way communications, these conditions must be fulfilled: • Serial communications are established with the host • Std IN channel = Std OUT channel • Verbosity is enabled Choosing an Error Message Format Using the system variable SYSVAR(19), you can choose between four types of error messages. This is illustrated by the following examples using error #19: • "Invalid font in line 10" (default) • "Error 19 in line 10: Invalid font" • "E19" • "Error 19 in line 10" For more information, see the SYSVAR information in the Intermec Fingerprint Command Reference Manual. 130 Intermec Fingerprint Developer's Guide

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187

Chapter 8 — Error Handling
130
Intermec Fingerprint Developer’s Guide
Standard Error Handling
In most application programs, it is useful to include some kind of error handler. The
complexity of the error handler depends on the application and how independently
the printer works. For flexibility, Intermec Fingerprint includes a number of tools
for designing custom error handling routines.
Fingerprint includes hardware-based error handling, such as reporting “out of
media” errors when the
Print
or
Feed
keys are pressed during a print job, or if batch
printing is interrupted by pressing the
Print
or
Pause
keys.
Additionally, during program execution, Fingerprint performs these checks:
Syntax Check. Each program line or instruction received on the standard IN
channel is checked for possible syntax errors before it is accepted. If two-way
communication is established, error messages (for example, “Feature not
implemented” or “Font not found”) are transmitted to the host on the standard
OUT channel.
Execution Check. Any program or hardware error that stops the execution is
reported on the standard OUT channel. In case of program errors, the number of
the line where the error occurred is also reported (for example, “Field out of label
in line 110”). After the error has been corrected, the execution must be restarted
by means of a new RUN statement, unless the program includes a routine for
dealing with the error condition.
Choosing an Error Message Format
Using the system variable SYSVAR(19), you can choose between four types of error
messages. This is illustrated by the following examples using error #19:
“Invalid font in line 10” (default)
“Error 19 in line 10: Invalid font”
“E19”
“Error 19 in line 10”
For more information, see the SYSVAR information in the
Intermec Fingerprint
Command Reference Manual
.
Note:
For two-way communications, these conditions must be fulfilled:
Serial communications are established with the host
Std IN channel = Std OUT channel
Verbosity is enabled