Technical data

2. Set the serial port language sensing mode to Automatic. (On the
front panel: Serial, Printer Type = PS/PCL Sensing), and define the
DCPS$queuename_NO_SYNC logical. In this mode, the printer responds to
PJL sequences and switches to native PCL 5 or PostScript as indicated by
the datastream.
10.6.2 Interaction Between Communication Protocol and Native PCL
Support
The optional network card supports switching to native PCL; however, the
protocol must be set to autosensing.
10.6.3 NIC Does Not Work with Raw TCP/IP
DCPS cannot communicate with the printer via a raw TCP/IP connection
because the NIC does not support bidirectional TCP/IP communication.
As an alternative, you can connect the printer to a print server (for example,
the Rapidprint 500) or a terminal server, or use a LAT connection instead.
10.7 DIGITAL DEClaser 5100 Printer
10.7.1 Native PCL Is Unavailable with EtherTalk Protocol on NIC
Because of a problem with the Network Interface Card (NIC), DCPS cannot
switch the printer into native PCL when using the EtherTalk protocol. Users
will see the error:
%DCPS-W-UNDEF, undefined: Name not known - offending command is <1B>
%DCPS-E-FLUSHING, Rest of Job (to EOJ) will be ignored
A partial workaround is possible by specifying a default print job parameter of
PAGE_LIMIT=999999 for the queue when you create it in DCPS$STARTUP.COM.
This parameter forces any PCL files to be printed through the PCL translator.
Remember, though, that the PCL translator is PCL 4 rather than PCL 5.
10.7.2 NIC Does Not Work with Raw TCP/IP
DCPS cannot communicate with the printer via a raw TCP/IP connection
because the NIC does not support bidirectional TCP/IP communication.
As an alternative, you can connect the printer to a print server (for example,
the Rapidprint 500) or a terminal server, or use a LAT connection instead.
10–6 Printer-Specific Information