Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Chriss Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
PCL XL Error
- Thread starter moshry
- Start date
Error = IllegalStreamHeader means that the stream header bytes are in a format not recognised by the PCLXL interpreter.
The stream header should follow immediately on from the
@PJL ENTER LANGUAGE=PCLXL<LF>
statement (which is terminated by a LineFeed character).
The header provides the target device with details of the protocol level and version of the language which is required, and also the 'binding' (usually indicating either big-Endian or little-Endian binary) in use in the following stream body.
It seems that whatever driver you are using to create your output is not generating syntactically correct PCLXL.
The stream header should follow immediately on from the
@PJL ENTER LANGUAGE=PCLXL<LF>
statement (which is terminated by a LineFeed character).
The header provides the target device with details of the protocol level and version of the language which is required, and also the 'binding' (usually indicating either big-Endian or little-Endian binary) in use in the following stream body.
It seems that whatever driver you are using to create your output is not generating syntactically correct PCLXL.
Or it could possibly be that the link (parallel port, or communications network) between the sending regime and the device is 'garbling' some of the stream.
This happens more with PCLXL (PCL6) than with PCL5 because the former is primarily a binary protocol (so is more prone to substitutions/inserts, like changing LineFeed to CarriageReturn LineFeed). With PCL5, such tampering is more likely to cause corrupt raster images, but pages will still print; with PCLXL, the interpeter 'polices' the protocol much more strictly.
Having said that, the stream header itself uses ASCII text, so comms problems are more likely to affect the body, not the header.
This happens more with PCLXL (PCL6) than with PCL5 because the former is primarily a binary protocol (so is more prone to substitutions/inserts, like changing LineFeed to CarriageReturn LineFeed). With PCL5, such tampering is more likely to cause corrupt raster images, but pages will still print; with PCLXL, the interpeter 'polices' the protocol much more strictly.
Having said that, the stream header itself uses ASCII text, so comms problems are more likely to affect the body, not the header.
- Status
Similar threads
- Locked
- Locked
- Question
- Locked
- Question