| Technical Support | |
| |
|
| • | drivers |
| • | firmware upgrades |
| • | FAQs |
| • | product documentation |
| • | cabling |
| • | support tools |
| • | legacy products |
| • | about digi support |
| • | knowledge base |
| • | online support request |
| • | support feedback |
| • | support feedback |
| • | FTP site |
| • | inside out networks |
While the following procedure is sufficient for most cases, it may be necessary to take additional steps to properly configure your reader or to set up the OS for a specific application.
Software flow control can usually be accomplished with a 4 wire cable in most cases. The cable specification below is recommended to allow interchangeability of cables between terminals and printers, and to allow easy migration to hardware flow control if this proves necessary for a given terminal or application.
1) The Cable
Use the Standard Terminal Cable as diagrammed in The Digi Standard Cable FAQ2) The Portserver
from factory defaults:- connect a terminal (set for 9600, 8-N-1, vt100 emulation) to a
port on the portserver
set conf ip=%%.%%.%%.%% subm=%%.%%.%%.%% [%% is the correct ip number] set conf gateway=%%.%%.%%.%%
- then telnet to the portserver from your host and
set port dev=prn ra=## [## is a port number] set flow ra=## altpin=on [for those ports using 8 wire RJ45 cable]
3) The Unix Server
Configure your program to read data from the terminal (non-modem device) port, as per a terminal, but do not enable a getty or ttymon on the port unless the program documentation specifically says to do so.If the port is not working at this point, see the FAQ: Testing and Troubleshooting Portserver Ports Revised 4/15/98: BT