KROHNE ALTOSONIC V EN - Manual (Page 74)

ALTOSONIC V
Operating Manual rev02 E 7.30850.34.00 Page 74 of 106
Printer task at : 011%
It is always possible to reset the printer buffer in the UFP, this will cause the print task to start at the
beginning of the ticket again.
Note that it can be necessary to reboot the printer itself on a real print failure.
Stopping a batch holds the following “manual actions” / “ModBus commands”:
•
After ticket is printed, confirm the printed ticket is printed successful and is the same as shown on
screen.
•
If the printing has failed the software generates an alarm and no confirmation can be given only a
reset of the printer. Check and reset the printer. After reset, the complete ticket is printed again. If
the ticket is printed correct a confirmation can be given.
Note that a next batch can only be started when the previous batch is confirmed.
If any CRC is corrupted this will be indicated on the ticket Printout
•
In the header of the ticket, that the ticket is invalid due to system errors
•
At the end of the ticket, the explanation of the system errors and so that there was a crc checksum
failure
If status batch files are all corrupt at initialisation of the UFP-Program, a new status file is made. The
ticket number can then be set to desired value (for logistical reasons) and the DAT data set will have
CRC checksum update.
6.11.1 Possible errors that cause an Invalid Batch ticket
In the header of the ticket one of the 3 following messages will be printed
•
Decisive presentation: Valid
•
Decisive presentation: Not valid, crc-checksum error (ticket)
• Decisive presentation: Not valid, system errors during batch
At the end of the ticket, there will be an explanation of the system errors if they have occurred:
Error in batch by:
•
During read/write of start/stop value files
•
During making ticket file (write errors)
• During batch: batch status files
•
During batch: batch totaliser files
•
During batch: batch average files
•
During batch: system stopped during batch
• During batch: measurement alarms possibly cause > 0.04 percent deviation
•
During batch: batch status file saving