Home/Support/Support Forum/Portserver prints Trash
Welcome to Digi Forum, where you can ask questions and receive answers from other members of the community.

Portserver prints Trash

0 votes
Hello,

I am having a problem with a Portserver 8. I have installed realport software dgrp-1.9-4 on a Debian 3.1 (Sarge) machine. Whenever I try to print anything to it all that comes out is trash. The printers are brand new Okidata Microline 320 Turbos. The printers are configured the same as other printers connected to other Digi portservers on the network.
Any suggestions on where to begin looking?

Also kernel is 2.6.8.

Thanks


--michael kotschi
asked Mar 10, 2006 in Realport by mkotschi New to the Community (2 points)

Please log in or register to answer this question.

3 Answers

0 votes
Typically, garbage points to a mis-match in the settings between the spooler/port and the attached printer. Confirm the "ditty-rp -a ttyx##" results match the settings applied on the Okidata printer with regards to baud rate, parity, flow control, etc...

Are you able to cat data directly to the printer and have it print properly?

cat /etc/inittab > /dev/ttyx##

Also, confirm the port on the PortServer is configured for use with RealPort. I'm not sure what PortServer model you have, however "prn" works on all models. Telnet to the PortServer and login as root:

#> set port dev=prn range=port#
#> kill tty=(port#)

If there is still a problem, you should contact Digi Tech. Support to pursue this further:

http://www.digi.com/support/eservice/eservicelogin.jsp
answered Mar 10, 2006 by userid0 Veteran of the Digi Community (2,158 points)
0 votes
Sorry for not replying sooner the equipment is at a remote customer site, I can't get out there as often as I'd like.

ditty-rp -a ttyst01

gives:

onstr \033[5i offstr \033[4i term ansi
maxcps 100 maxchar 50 bufsize 100 edelay 100
-forcedcd -altpin -fastbaud (9600) -printer -rtstoggle
-rtspace -dtrpace -ctspace -dsrpace -dcdpace
DTR+ RTS+ CTS- CD- DSR- RI-
startc = 0x11 stopc = 0x13
-aixon astartc = 0x0 astopc = 0x0
speed 9600 baud; rows 0; columns 0; line = 0;
intr = ^C; quit = ^\; erase = ^?; kill = ^U; eof = ^D; eol = <undef>;
eol2 = <undef>; start = ^Q; stop = ^S; susp = ^Z; rprnt = ^R; werase = ^W;
lnext = ^V; flush = ^O; min = 1; time = 0;
-parenb -parodd cs8 hupcl -cstopb cread clocal -crtscts
-ignbrk -brkint -ignpar -parmrk -inpck -istrip -inlcr -igncr icrnl ixon -ixoff
-iuclc -ixany -imaxbel
opost -olcuc -ocrnl onlcr -onocr -onlret -ofill -ofdel nl0 cr0 tab0 bs0 vt0 ff0
isig icanon iexten echo echoe echok -echonl -noflsh -xcase -tostop -echoprt
echoctl echoke

The printers are Okidata microline 320 turbo models and are set to 9600 baud, 8 bits Data and flow control of x-on/x-off. Correct me if I am wrong, but the above
ditty command confirms these settings for the portserver.

I cannot cat data to the device, it comes out trash.
I ran my tests again after setting the ports as described in the above post.

this is what pops up when doing #> set config


PortServer Version 3.5.5 May 15, 2001

Copyright 1990-2001 DigiBoard. All Rights Reserved.

myname : termserver domain : DOMAIN

ip : 192.168.2.200 submask : 255.255.0.0

gateway : 192.168.2.1 nameserv : 192.168.2.1

ether : 00:40:9d:00:36:e7

boothost : 65.xx.xx.xx bootfile : 40001080_n.bin

realport : 771

0 corrected errors in EEPROM



Sticker on the bottom of the portserver says:

Portserver/8 RJ45 Domestic
P/N: (1/P)50000254
S/N: (S)A3503569

Could the portserver just be toast?
answered Mar 16, 2006 by mkotschi New to the Community (2 points)
0 votes
Can't tell if the unit is toast. Here are a few things to try/confirm:

The ditty-rp results show -ixoff, you will want to activate this setting:

ditty-rp ixoff ttyx##

On the Okidata printers, confirm the following settings:

Protocol: XON/XOFF
Ready/Busy: SSD-
DSR: Invalid

Telnet to the PortServer, login as root and confirm the port device type is set to "prn":

#> set port range=(port#)

If not:

#> set port range=(port#) dev=prn

The unit should then be rebooted, if the setting is changed:

#> boot action=reset

If garbage continues to print, you may want to try another port to see if the port has gone bad.
answered Mar 16, 2006 by userid0 Veteran of the Digi Community (2,158 points)
...