Applies To: |
|
Summary: |
Problem: Citect is printing each of the alarms on a new page, what is wrong with my configuration? |
Solution: |
The Windows print manager has been
designed for page-based printers, for example, laser printers and
shared network printers. The print manager does not print anything
on the printer until the entire page is complete. It then prints
the page. This is the preferred printing method (when printers are
shared on a network) because it prevents conflict of data when
different operators use the print facility.
However this is not the preferred method when you are logging alarms. If you send alarm logging to this type of printer, Citect flushes the data to the printer when the current page is full, or when the [DEVICE] FlushTime (parameter) time has expired (the default is 10 seconds). If, for example, you have one alarm occurring each minute, each alarm is printed on a new page. You can bypass the Windows print manager by writing the output to a file. Set the device type to ASCII_DEV (ASCII File) and specify the file name as LPT1.DOS, LPT2.DOS or LPT3.DOS. When you log to this device, the data is printed immediately on the printer with no extra form feeds. For correct logging operation, you should reserve one printer to be your logging printer. Use a local printer, not the network printer. You can then send any other non logging printouts (for example reports) to a shared network or local printer. |
Keywords: |
Related Links
Attachments