Using AxRM on Windows
The AxRM software allows system administrators to manage and configure Axel TCP/IP products remotely over a network.
For example, AxRM is used for rebooting the
terminal, downloading firmware or remotely
configuring the terminal.
Click here to get more information about AxRM.
Click here to download AxRM.
Top
Downloading Firmware by TFTP Protocol
The tftp protocol is available as a standard feature on Unix/Linux
but is not enabled by default.
Setting-Up the TFTP Protocol
Modify the file /etc/inetd.conf by removing the '#' comment
character from the beginning of the line associated with tftp.
For information, please find below typical tftp lines according
to the used Unix system:
SCO OpenServer
|
tftp dgram udp wait nouser /etc/tftpd tftpd |
AIX 4.x
|
tftp dgram udp nowait nobody /usr/sbin/tftpd tftpd -n |
LINUX
|
tftp dgram udp wait root /usr/sbin/tcpd in.tftpd / |
UNIXWARE 7
|
tftp dgram udp wait nobody /usr/sbin/in.tftpd in.tftpd |
Note: we advise the tftp public mode (no username checking
and no pre-defined tftp directory).
Enabling the TFTP Protocol
These modifications take effect after rebooting the UNIX host
or sending the signal 1 to the inetd process (kill -1 pid).
Top
Using BOOTP Protocol in
Event of Problem
This protocol is available on Unix as a standard feature.
Setting-Up and Enabling BOOTP protocol: Modify the file /etc/inetd.conf by removing the '#' comment character, from the
beginning of the line associated with bootp. These modifications
take effect after rebooting the UNIX host or sending the signal
1 to the inetd process (kill -1 pid).
Setting BOOPT environment: the bootp protocol is based
on a file parameter: /etc/bootptab. This file describes the network
and attached TCP/IP devices and gives all device information needed
for tftp (firmware filename, IP addresses, etc).
Example of /etc/bootptab (the first line describes network and
the second line describes the Office Server):
default:hn:df=/etc/btdump:ht=ethernet:sa=192.168.1.252:to=auto:
axel1:tc=default:ht=ethernet:ha=00A034000001:ip=192.168.1.242:bf=/tmp/axel: |
Note: the main capabilities are as follows:
- sa: tftp host IP address
- ha: AX3000 Ethernet address
- ip: AX3000 IP address
- bf: firmware filename
Running BOOTP: a bootp request can be run from both
the AX3000 interactive set-up or by an rsh command (or rcmd for
SCO UNIX):
When the bootp request is answered, theAX3000 firmware is downloaded
by using tftp. Click here for more information
about tftp.
Top
Printers: LPD Protocol or TTY Protocol?
Printers connected to an
AX3000 can be handled by:
- lpd
- tty
The following tables list operational characteristics for each
protocol .Select the one most suited to your needs.
LPD Protocol:
|
BENEFITS |
DRAWBACKS |
- This protocol is available as a standard feature for major
operating systems (Unix, Windows NT, AS/400, etc).
- The printer port is locked by LPD only during the printing.
That means several hosts can print on a single AX3000 port.
- The LPD printer is a standard system printer (controlled by
the spooler). |
- On Unix, an LPD printer can only used by its spooler name.
No tty is associated with an LPD printer.
- On SCO Unix, it is not possible to associate a driver with
an LPD printer. That means the application must create a print
file preformatted for the LPD printer. |
TTY Protocol:
|
BENEFITS |
DRAWBACKS |
- A port controlled by the tty protocol is seen as a local port
(as a multi I/O board)
- A printer can be accessed either by its spooler name or by
its tty. |
- This protocol is additional Unix software designed by Axel.
It must be installed and set up on the Unix box.
- A serial port controlled by the tty protocol can only be addressed
by a single Unix box. |
Top
Connecting a Dumb Terminal
to AUX1 or AUX2Two bi-directional serial ports are provided by the AX3000.
Dumb terminals can be connected to these ports.
To connect a dumb terminal, enter the AX3000 Set-Up, select
the AUX port, set the "bi-directional" mode and communication
parameters (baud rate, handshake...). Then associate the "telnet"
service and enter the requested information (the name of the Unix
host for example).
The dumb terminal is now ready to be used (a login request
is displayed) without additional Unix settings. The ptty associated
with the dumb terminal has been dynamically assigned. .
Note: if a predefined tty is required, you must use
the tty protocol instead of telnet.
Top
Controlling a Device
by Using Escape Sequences
To control a device by escape sequence, enter the AX3000 Set-Up,
select the [Configuration]-[Terminal]-[General] menu and set the
'Default Auxiliary Port" parameter to must be modified to
AUX1, AUX2 or PARALLEL.
1 - Sending Data to the Device (a Printer for Instance)
To send data, two escape sequences are needed: one to begin
the printing, one to stop the printing:
<beginning seq><data><ending
seq>
These sequences are predefined by the emulation used:
|
Emulation |
Beginning Sequence |
Ending Sequence |
|
ANSI and VT220 |
Esc [ 5 i |
Esc [ 4 i |
|
WYSE |
Esc d # |
14h |
Note: during the printing, we advise the AX3000's user
doesn't use his keyboard. To grant correct behaviour, the AX3000
keyboard can be locked by escape sequences (Esc [ ? 2 h and Esc
[ 2 l).
Example: Unix script to print a file in Ansi emulation:
echo "\033[2h\033[5i\c" # lock kbd and start printing
cat $1
echo "\014\033[4i\033[2l\c" # Form feed, end printing
and unlock kbd |
Receiving Data from the Device (a Card Reader for Instance)
Data from the device can be read. This function is only available
with the AUX1 or AUX2 port. To enable the data receipt, enter
the AX3000 Set-Up, select the AUX port, set the "bi-directional"
mode.
Now, data from the device is put in the "keyboard buffer"
of the AX3000 screen session. To get data, a simple read keyboard
instruction is needed.
Top
Associating a tty to an AX3000 auxiliary port or an
AX3000 Screen Session
The tty protocol allows a Unix pseudo-terminal (ptty) to be
associated to an AX3000 resource (auxiliary port or screen session).
Effectively the AX3000 resource is seen as multi I/O board channel.
Setting-Up the AX3000
Enter the AX3000 Set-Up, select the session or the auxiliary
port, set the "tty" service and enter the needed information
(the name of the Unix host for example).
Installing axttyd on Unix/Linux
Copy the following onto Unix/Linux:
|
File |
Destination |
Comment |
|
axttyd |
/etc |
Daemon (tty server) |
|
axfile |
/etc |
Association File |
|
S91axel |
/etc/rc2.d |
Unix Boot Script |
|
S91axttyl |
boot folder |
Linux Boot Script |
Setting-Up axttyd
The AXEL tty server uses a configuration file, which lists
all authorised associations between AX3000 resources and Unix/Linux
pttys. Example:
#AX3000
axel1
axel1
axel2
axel2 |
Resource
aux1
parallel
sess2
sess8 |
Master
/dev/ptyp12
/dev/ptmx
/dev/ptyp1
/dev/ptyp2 |
Slave
/dev/ttyp12
/dev/pts/13
/dev/ttyp1
/dev/ttyp2 |
Each entry in this file contains four parameters:
- AX3000 hostname (see /etc/hosts)
- AX3000 resource:
- screen sessions: sess1, sess2, ..., sess8
- auxiliary ports: aux1, aux2 or parallel
- the master file of the ptty: /dev/ptypx or /dev/ptmx
- the slave file of the ptty: /dev/ttypx or /dev/pts/x
Running axttyd
The command to start the AXEL tty server is:
Using Ptty
The AX3000 resources can be addressed by the ptty slave
part: /dev/ttypx.
Note: when a dumb terminal is attached to an AX3000
serial port the following line must be added to /etc/inittab to
initiate a login prompt:
|
px:234:respawn:/etc/getty ttypx m |
Top
What are printd and
rtty?
The printd protocol has been designed for printer support and
the rtty protocol has been designed to bi-directional device support.
For compatibility reasons, these protocols are still available.
But rather than using these legacy protocol, we advice you to
use lpd (printers) or tty (any devices).Top
How Can Software Identify
an AX3000?
Sometimes, terminal identification is required by a software.
Three methods are offered by the AX3000:
- IP Address Identification
The IP Address of a TCP/IP AX3000 can be obtained by sending
the following escape sequence: "Esc [<a".
On receipt of this escape sequence, the AX3000 places its IP
address (plus an 0Dh character) in its keyboard buffer. So the
IP address can be retrieved by a simple read instruction in the
software as shown in the following Unix script shell:
oldtty=`stty -g`
stty -opost -echo -echoe -echok -icanon eof "^@" eol
"^T"
echo "\033[<a\c"
read ADR_IP
stty $oldtty
if [ -z "$ADR_IP" ]; then
#Not an AX3000
else
#This is an AX3000
fi |
Once the AX3000 identified, it can be interesting to identify
the AX3000 session. Two methods:
- Session number: on receipt of the "Esc [ < 5
a" escape sequence, the AX3000 places its IP address (plus
an 0Dh character) in its keyboard buffer..
- Anwserback message: this string is associated
with a session through the AX3000 Set-Up. The ANSI "Esc
[ < 4 a" sequence or the VT220 "Ctrl-E" control
code can be used to get this answerback message.
- TERM Variable Identification
The AX3000 allows a given session to be associated with a
specific UNIX Host and TERM value. Generally this character string
is composed by only one word (ansi, vt220, etc.). But other words
can be added: "vt220 platine" or "ansi store1
axel". The following Unix script shows how a unique word
can be used for the TERM variable:
set `echo $TERM`
TERM=$1
LOCATION=$2
TYPE=$3
export TERM LOCATION TYPE |
TTY Identification
The telnet protocol assigns a dynamic tty to each AX3000 session.
This dynamic allocation prevents an identification mechanism.
To solve this problem, Axel designed the tty protocol which associates
a pre-defined tty with an AX3000 session. Click
here for more information about tty protocol.
Top
Using a Script to Set-Up
an AX3000The AX3000 can also be set up with a script. The remote set-up
functions are performed by a rsh command (or rcmd for SCO UNIX):
Setting-Up an AX3000
Use the following command to set-up an AX3000:
|
rsh axname setup_send < file |
Note: axname is the AX3000 name (listed in /etc/hosts),
setup_send is the remote set-up command and file is the
AX3000 configuration file (this configuration file can be created
using a text editor or obtained using the command 'rsh setup_get').
The Office Server must read this new set-up before it will
take effect. This can be achieved either by power-cycling the
AX3000 or by issuing the following remote reboot command:
Obtaining a Configuration
To obtain an AX3000 configuration, use the rsh command together
with the setup_get option:
|
rsh axname setup_get > file |
The created configuration file lists each AX3000 set-up parameter.
Top
Using the Keyboard in
Scancode ModeSCO UNIX 3.2v4 (and later) allows the use of scancode mode.
The following section applies to scancode mode with SCO UNIX.
To switch scancode mode on or off, a terminfo entry must be
used that sets the 'smsc' and 'rmsc' capabilities for the Axel
escape sequences (Esc [< Ps A).
The following example shows how the ansi terminfo entry may
be modified:
- Create the ansi terminfo source file:
# cd /usr/lib/terminfo
# infocmp ansi > ansi.src |
- Add the following line to this file, at any position except
the beginning or end of the file:
|
smsc=\E[<0A, rmsc=\E[<1A, xonc=e, xoffc=g, |
- Enter the command 'tic ansi' at the UNIX prompt.
The terminfo entry supports now the scan mode. Use the two
following script to switch mode:
Enabling scancode mode:
tput smsc ; stty isscancode xscancode
mapkey /usr/lib/keyboard/ps.ibm.uk |
Enabling ASCII mode:
|
tput rmsc ; stty -isscancode |
Note: When scancode mode is switched on, the keyboard
Leds can be turned on or off by means of the following escape
sequence: CSI < p1;p2;p3 O. (where Pn1, Pn2 and Pn3 are the
status of NUM, CAPS and SCROLL). Possible values of these parameters
are:
- 0: does not modify the led status
- 1: turn the led on
- 2: turn the led off
Top
Erratic Display
The AX3000 input data flow is not continuous (the display stops
for a second, then resumes for several seconds, stops again and
so on).
This trouble is almost certainly due to a bad network communication.
The AX3000 drop frames. These frames are re-sent but this gives
a non-continuous display. Possible causes are:
- Cable: too long or low-quality
cables corrupt frames.
- Frame size: received frames
which can not be stored by the AX3000 are dropped. This is not
normal because TCP/IP is an adaptive protocol which is able to
reduce the flow according to the connected TCP/IP device. But
if this is the problem, the frame size can be reduced through
the AX3000 Set-Up ('mss' and 'windows' parameters in [Configuration]-[Advanced]-[Tunings]).
Note: Statistics can be consulted through the AX3000
Set-Up ([Diagnostic]-[Statistics]-[Ethernet] menu).
Top
The LPD Printer Doesn't Work
First Checks:
- Use a standard cable length (1.5 meter for a parallel one)
and don't use a sharing printer box.
- If a parallel printer is used, check the cable is connected
to the AX3000 parallel port (and not to the serial AUX1 DB25
port)
Testing Locally the Printer
Setting-Up the AX3000: Reset the
network service (lpd) associated with the auxiliary port to none
([Aux Ports]-[Aux1 or Aux2 or Parallel]-[Network Service]-[none]).
Then set this port as the 'default auxiliary port' (this parameter
is accessed by the [Configuration]-[Terminal]-[General] menu).
Power off the AX3000, unplug the network cable and power cycle
the AX3000.
Testing: Enter the AX3000 Set-Up
and press <Print Screen>. A set-up hardcopy should be printed.
If the hardcopy test doesn't work, the problem is local (AX3000
connector, cable or printer). Otherwhise the problem is due to
the lpd settings or the operating systems settings.
Other Checks
- Check the printer name set through the AX3000 Set-Up (no
extra spaces, case sensitive) and compare it the name you entered
at the operating system level.
- Use the lpstat Unix command (or rlpstat) to check is the
printer can be reached.
Top
On AIX, the LPD Printer is Disabled When Jobs are Printed
On AIX, the LPD Printer is Disabled When Jobs are Printed
Normally printing functions are performed well, but occasionally
print jobs are truncated and the printer is disabled by AIX.
To fix this, a timer value must be increased (1 minute by default).
Use a text editor to modify /etc/qconfig. Seek the entry dedicated
to the Office Server printer. Add the '-T xx' option (where xx
is a number of minutes). Example:
axel:
/usr/lib/lpd/rembak -T 5 |
Top
On SCO, Some LPD Print
Jobs are Truncated
On SCO, long LPD print jobs can be stopped before reaching
the end. This is due to a SCO default setting which doesn't allows
print jobs greater than 1 Mb.
To fix this, modify the /etc/printcap file which describes
SCO LPD printer. Add the mx#0 capability (no size limit) to the
printer description. Example:
prnaxel:\
:lp=:rm=ax3002:ex:rp=prnaxel:sd=/usr/spool/lpd/prnaxel:mx#0: |
Top
Printers Controlled by the TTY Protocol Don't Work When the SCO Box is Rebooted
The following problem has been reported when printers are controlled
by the tty protocol:
When the SCO box is powered off with the shutdown command
and if the Office Server hosting the printer is not powered off,
at the next SCO boot the printer won't work.
This is caused by the shutdown command not closing open TCP/IP
connections (this is not the case with haltsys). There are two
ways to resolve this problem:
- Power cycle the AX3000
- Adding a boot script to reboot Office Server at each SCO
boot time. Contact us to get this script.
Top
|
