I am supporting eB2 application. Recently in one of our office, they changed a color printer to a black and white one.. i.e from Xerox Apeosport c3300 to Xerox FX APeosPort-Iv C3370 resp.

Now the problem is , the control codes used for the new printer is the same which was working for the old one. But the print from the new printer is showing all squashed up letters.


Please see the attached files. One jpeg file is the control codes used for this printer and the other is the squashed up output from this printer with the said control codes.

The present control codes used :

80 Column Start: /027E/027&I2A/027&I66P/027&I0O/027(8U/027(s0p14.h9
v0s0b3T/027&6E/027&17.8689C/027&I66F/027&k2G
132 Column Start: /027E/027&I2A/027&I66P/027&I0O/027(0O/027&I66F/027
(s0p16.66h8.5v0s0b0T/027&12E/027&17.8689C/027&k2G
Reset Ctrl: /027E

Waiting for all your valuable comments.

Greetings,

Well I looked at your sample page and it looks as if your vertical spacing is incorrect.

Two possible solutions, one is to increase the vertical spacing for the printer. The other is to decrease the height of the font being used.

Unfortunately, I have to umpire some softball games this evening so I'll be prevented from going through the command sets.

If no one else can do this for you this evening, I'll try to get it done tomorrow.

Oh, one other thing. There is a setting in PCL that allows you to vary the vertical motion index. For example, if printer1 has a VMI (Vertical Motion Index) of 6/8 and printer 2 has a setting of say 34/48, the vertical spacing will be different and it will cause the failure you are seeing.

Any chance you can generate a print to file of the faiing document, that way I could look at the file with a tool I have.

Don

Quote:

---

Originally Posted by donf

Greetings,

Well I looked at your sample page and it looks as if your vertical spacing is incorrect.

Two possible solutions, one is to increase the vertical spacing for the printer. The other is to decrease the height of the font being used.

Unfortunately, I have to umpire some softball games this evening so I'll be prevented from going through the command sets.

If no one else can do this for you this evening, I'll try to get it done tomorrow.

Oh, one other thing. There is a setting in PCL that allows you to vary the vertical motion index. For example, if printer1 has a VMI (Vertical Motion Index) of 6/8 and printer 2 has a setting of say 34/48, the vertical spacing will be different and it will cause the failure you are seeing.

Any chance you can generate a print to file of the faiing document, that way I could look at the file with a tool I have.

Don

---

Hello Donf..

I have already attached a pdf file which shows squashed up output..
I am attaching the txt file which is an output SO print to a local file from eB2 system.. and this is what we do print to a printer..
If you need more info, then please let me know...
I would like to love to get a resolution soon.. and I know your brilliance in
Resolving such kind of issues.. :p :-)

A print file is useless because all the printer control calls are stripped out of the file and you are left with a flat ASCII file.

I'll take a shot at your codes from the sample you have.

Hello,

The problem is not with the printer, it is in the PCL being sent to the printer. Okay, whoever told you that this is valid PCL commands did not tell you the truth. I spent 2 hours this evening taking apart the PCL strings and found a bunch of junk. Some of the commands were:
"<esc>&I (as in "Ida") instead of
<esc>&l (as in "Larry").

Also, the command to set the Vertical Motion Index is incorrect. They set it at 17.8689. However the command does not take a decimal point. It is an Integer only command.

If the font call is to be believed, then the vertical height in the command is wrong.

In short, this is trash PCL. One more thng, I did not see the "SO" command. Does the datafile that is being sent to the printer contain control/escape commands in it?

I did not take the time to start column 132 but a quick look assured me that it also was poorly written.

Well I have a working PCL "80 Column Start" string.

However, there is nothing in the string to actually start the column at position 80.

I'm not going to to correct the 132 Column until I hear back for you.

Quote:

---

Originally Posted by donf

Well I have a working PCL "80 Column Start" string.

However, there is nothing in the string to actually start the column at position 80.

I'm not going to to correct the 132 Column until I hear back for you.

---

Hello Don,

Thank you very much for helping in this issue..
I do have few updates for you.
I found few control codes for Xerox and applied the same and found its working.. (attached pdf) but the problem is that its giving an extra blank sheet as a print along with the original print.. can you help me with that now ?

Xerox codes which is working now :

80 Column Start: /027&k0S

132 Column Start: /027&k2S/013

Reset Ctrl: /027&k0S

As I told only problem existing is a blank page is also gettng out from printer..!

Are you sure you are using Xerox XES codes, because what you are showing me does not look at all like the XES data stream. They sure look and behave like HP PCL5 codes.

Where can I get a look at the Xerox code set?

Please, let's move this off this forum. Contact me at [email protected]

There is no way you and I are getting the same print out. Did you magnify the printout?

Also, the Sample Sales Order is not a properly formated page. For one thing, the data in the left column is starting above the Sales Order heading and the "Simulation" is below the heading.

What is really going on here?

Sreekuak,

I'm appending a binary file named "Australia.txt" for you to run a test with. You may have to convert the file to a ".bmp" file to download it as a binary file to the printer.

Do a "Put" command to the printer and then attach the output back to this thread. I want to make sure we are getting the same output, please.