Specifications

No
EPSON
TITLE
EPSON Advanced Printer Driver for TM series
StatusAPI
Reference Manual
Revision
L
NEXT
109
SHEET
108
5. Notes
1)
There are certain computers with which printing will not be performed normally and the status API cannot be used when the
parallel operations mode is set to the ECP mode. In this event, cancel the ECP mode.
2)
When using the printer driver for EPSON Terminal Printers (Page printer, ink-jet printer and others ) and TM printer driver
at the same time, the installation and uninstallation goes by the following order:
[Installation]
1.
EPSON Terminal Printer driver
2.
TM printer driver
[Uninstallation]
1.
TM printer driver
2.
EPSON Terminal Printer driver
Furthermore, after installation pay attention to the following:
• When installing the EPSON Terminal Printer driver after the TM printer driver is installed, uninstall first the TM printer
driver.
• When EPSON Printer Port is unwanted, make BIOS LPT setting other than ECP mode.
• When uninstalling the EPSON Printer Port after the TM printer driver is installed, uninstall first the TM printer driver.
3)
During status API monitoring, macro execution for DM-D is not working correctly.
4)
When printer is connected to an Ethernet and is reset (e.g. OFF to ON), the printer is unusable for 20 seconds. Therefore,
error is returned when using API within this duration.
5)
Status API can only monitor printers that are local connected. If the printer is connected over Ethernet I/F, it cannot monitor
the shared printer via print server.
6)
When using MICR in a high speed interface connection, set the handshake to Xon/Xoff. DTR/DSR cannot use MICR
functions.
7)
TM printers other than the following printer must be set to "Receive buffer full" for the BUSY condition with the DIP
switch. However, the following printer can be set automatically with BiOpenMonPrinter:
TM-T90, TM-L90, TM-J2000/2100, TM-J7000/7100
8) It is set that a log is output with StatusAPI installed. If outputting a log is not necessary, change a folder name so that
LogPath does not exist or change LogLevel to 0.
9)
If printing is executed under the following conditions, the whole print job may not be completed normally. To recover from
this, click the “Details” tub in the printer’s “Properties” dialog, and change the “Timeout settings Transmission retry:” to
3sec.
When using Windows 95/98 and
When selecting ECP mode and
When using the low speed printer such as Slip printer.
10) A status callback doesn’t occur when the following conditions exist.
• If multiple status information is received simultaneously, the latest status only is notified. Simultaneous is the case
where the status changes within an interval of approximately 400 msec or less.
• In some cases, the status that is received during callback processing is not notified. As a criterion, this may occur
in cases where a callback processing time of approximately 800 msec or longer is required.
• If the receiving buffer is specified in BiDirectIOEx (if ASB suppression is not specified), the altered Status is not
sent back during execution of BiDirectIO or BiDirectIOEx. BiDirectIO or BiDirectIOEx read the Status, so
processing of the receiving data should be done by the calling side.
• If BiDirectIO and BiDirectIOEx (if ASB suppression is specified) do not specify the receiving buffer, the altered
Status is not sent back during command execution and for approximately 1.5 sec. after BiDirectIO or
BiDirectIOEx is executed.
• After the above conditions exist, changes in the Status cannot be detected just as in the case when BiGetStatus is
used, so the Status acquired last is sent back.
11)
When an Ethernet connection is used, t
he following functions related to Check Scanner are not
supported.
BiSCNSetImageQuality, BiSCNSetImageFormat, BiSCNSetScanArea, BiSCNPreScan, BiSCNGetImageQuality,
BiSCNGetImageFormat, BiSCNGetScanArea, BiSCNSetReadBackFunction, BiSCNSetReadBackWnd,
BiSCNCancelReadBack, BiSCNReadImage, BiSCNRetransmissionImage, BiSCNGetClumpStatus,
BiSCNClumpPaper, BiSCNSetCroppingArea, BiSCNGetCroppingArea, BiSCNDeleteCroppingArea
12) If printer status is checked by BiGetStatus continuously, it is recommended to have an appropriate Sleep setting so
that the resource is not occupied.