XMSG-HDLC-TEST

From NDWiki
Revision as of 15:01, 11 October 2024 by RHansen (talk | contribs) (Created page with "==HDLC / MEGALINK Test Program (1.13)== === Startup === Select controller/unit and give some parameters: Sintran Log.Unit No for HDLC/MEGALINK input (oct.) (def=1360): Sintran Logical Unit No (LUN) for HDLC-DMA or MEGALINK are : 1360 for link 0 (octal) 1362 for link 1 1364 for link 2 etc. Loop on interface? (N/y): This program transmits frames (data blocks) and expects these frames back again unchanged. This echoing can be done in the following ways:...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

HDLC / MEGALINK Test Program (1.13)

Startup

Select controller/unit and give some parameters:

Sintran Log.Unit No for HDLC/MEGALINK input (oct.) (def=1360):

Sintran Logical Unit No (LUN) for HDLC-DMA or MEGALINK are :
 1360  for link 0   (octal)
 1362  for link 1
 1364  for link 2
 etc.

Loop on interface? (N/y):

 This program transmits frames (data blocks) and expects these frames back again unchanged. This echoing can be done in the following ways:
 Loop on interface:
   All data transmitted is looped back internally on the
   interface. No external cable or equipment is needed.
   Answer Y  to the question.
 External loop via cable.
   All data is looped back via the external cable.
   An external loop-back plug is needed,
   Answer N or CR (default) to the question.
 External loop via echo-program.
   The echo function can be provided by this program (or any other)
   running in a ND-100 at the other side of the link to be tested.
   This program will return all received frames unchanged when running in
   echo mode
   Answer N or CR to the question.

Max frame size (dec.) bytes (def=128):

 The maximum frame size used by IS-XMSG is 256 bytes. A practical value for the max. frame size is 128 bytes. The HDLC driver needs buffer space in Sintran to run this test program. The amount required is (Input-Driver-Window + Output-Driver-Window)*(Max-frame-size+10) bytes.

Commands

HELP

ECHO-MODE

  • Enables this controller to echo back to remote controller

SEND

  • No of frames to send:

RESTART

CHANGE-WINDOWS

 Driver Input window (def=4): 
   The Driver-Input-Window denotes the number of data buffers given to the input driver in advance of incoming data frames. I.e. The program will try to keep the input driver in posession of D-I-W input buffers so that frames are not lost because of lack of input buffers.
 Driver Output window (def=3):
   The Driver-Output-Window is the max. number of frames beeing sent to the output driver simultaneously. When D-O-W frames are under transmission, the program will not stop sending until the output driver signals transmission complete for at least one of these frames. The D-O-W must be less than the D-I-W.
 Real window (unacked)(3):
   The Real-Window put a limit on the number of frames transmitted before receiving an answer. This is to adapt the sending rate to the speed of the echoing program. If f.i. R-W is set to 3 the program will send at most 3 frames before waiting for an answer. For each returning frame a new one can be sent.
 If R-W is set to  -1  the sending program will send at top speed without waiting for answers.


EXIT

GIVE-OUTPUT-EXPLANATION

 Output from SEND and ECHO command is presented as:
 FRAMES Sent  / Received = number of frames sent / received.
 TIME  = Elapsed time in seconds since last command.
 ERRORS = Subdivided into:
   Data errors : wrong data contents in frame that was received with correct CRC
   Input err.  : number of times CRC/Overrun/Too large frame on input.
   Output error: number of error returns from output driver.
   Sequence err: Number of frames received out of sequence.

CHANGE-ERROR-REPORTING