8.0 Suggestions for Application Developers
This chapter is to suggest some hints for the application programs to improve the performance.
•
If the totals in regular vouchers are calculated by the application instead of be requested to the fiscal
printer, generally takes less time.
•
ONLY FOR RS-485
After a PLD, read the
″
PLD STATUS
″
bit to determine if the last command sent before the PLD was
executed or not. This should avoid duplication of interrupted commands.
For 4610 SureMark RS-485: see 2.1, “For GR3/GR5 Models (RS-485)” on page 19 (byte 6 - bit 4).
•
We recommend the usage the DA (Electronic Read Fiscal Memory Tables) and DB (Electronic Read
Counters and Accumulators ) commands after any type of interrupts, like power down, paper out to
determine the state of the fiscal printer and the values of internal counters and accumulators to allow the
continuation of the current document in progress, if any.
Fiscal memory tables can also be interrogated.
•
In some countries, all the header and trailer lines are not mandatory, so the use of less lines result in a
better performance.
•
PLD or paper out during end transaction (06 cmd.)
After a PLD or paper out during the end transaction (06 cmd.) execution, applications will know
whether to cancel or re-end the transaction, querying the value of FENDTRA flag via DB command.
This value could be located in the DB Electronic Response (Byte 28 - bit 3 = End Transaction in
Progress). See 5.2.3.2, “Response to the Electronic Read Counters and Accumulators” on page 63
If this bit is OFF, it means that Fiscal Logo was not printed and the application is able to perform a
cancel transaction (07 cmd.).
Else, if this bit is ON, it means that the fiscal microcode will only accept to finish the voucher with the
reexecution of end transaction (06 cmd.) because the Fiscal Logo was printed or was about to be printed
(*). So, in this case, Applications are forced to resend the end transaction (06 cmd.).
(*) When I mean
″...
Fiscal Logo was about to be printed
″,
it means that it might be no visible sign of
the Fiscal Logo being printed on paper, but the request of the microcode to print the Fiscal logo was
already performed and stored into 4610 SureMark printing
′
s queue to be inmediately printed.
Suggestions for Application Developers — Page 183 of 183
Summary of Contents for 4610 SureMark GR3
Page 12: ...Page 12 of 183 IBM 4610 SureMark Fiscal Printer Turkey Models GR3 GR5 GB3 GB5 Programmin...
Page 14: ...Page 14 of 183 IBM 4610 SureMark Fiscal Printer Turkey Models GR3 GR5 GB3 GB5 Programmin...
Page 18: ...Page 18 of 183 IBM 4610 SureMark Fiscal Printer Turkey Models GR3 GR5 GB3 GB5 Programmin...
Page 26: ...Page 26 of 183 IBM 4610 SureMark Fiscal Printer Turkey Models GR3 GR5 GB3 GB5 Programmin...
Page 30: ...Page 30 of 183 IBM 4610 SureMark Fiscal Printer Turkey Models GR3 GR5 GB3 GB5 Programmin...
Page 44: ...Page 44 of 183 IBM 4610 SureMark Fiscal Printer Turkey Models GR3 GR5 GB3 GB5 Programmin...
Page 154: ...Page 154 of 183 IBM 4610 SureMark Fiscal Printer Turkey Models GR3 GR5 GB3 GB5 Programmi...
Page 178: ...Page 178 of 183 IBM 4610 SureMark Fiscal Printer Turkey Models GR3 GR5 GB3 GB5 Programmi...
Page 182: ...Page 182 of 183 IBM 4610 SureMark Fiscal Printer Turkey Models GR3 GR5 GB3 GB5 Programmi...