Wi t h the At ten t ion c h a r act e r set up t 0 b e 0 a hex, transmitting a string of characters from 030 to 03F hex caused character X to enter the Main Channel receive buffer.
ATTENTION CHARACTER X ENTERS BUFFER
Reception by the Main Channel began with Attention character X (OO-OFF hex) rather than the character immediately following it.
CHARACTERS RECEIVED BEFORE ATTENTION CHARACTER X
A t ten t i on charac ter X (OO-OFF hex) was not necessary to begin reception by the Main Channel, nor did Attention character X restart the receiver.
UNEXPECTED PATTERN IN CHARACTERS RECEIVED FOR ATTENTION CHARACTER X
For Attention character X the receive buffer contained a character that could not be processed. Either the character was received incorrectly or reception did not begin.
RECEPTION BEGINS X CHARACTERS AFTER ATTENTION CHARACTER Y
The first character in the Main Channel buffer should be the character that immediately followed the Attention character in the transmitted string. If the first received character was indeed part of the transmitted string but not the character immediately following the Attention character, its position in reference to the Attention character in the transmitted string is determined (X) along with the Attention character causing the fault.
INTERRUPT PRIORITY LEVEL NO.7 NOT ISSUED BY RECEIVING ATTENTION CHARACTER X Reception began properly on the Main Channel but Interrupt 7 was not issued by the reception of Attention character X on the Secondary Channel.
A SECOND ATTENTION CHARACTER DOES NOT RESTART RECEPTION
Upon completion of transmitting a string of characters containing two Attention characters, the first character in the Main Channel buffer was not the character immediately following the second Attention character.
Test 22 - Test Receive Data with Attention Recognition
Te s t t ha t the Main Channel does begin reception prior to an Attention character being received by the Secondary Chann~l.
Also, test that an Attention character restarts reception.
RECEPTION DOES NOT START WITHOUT AN ATTENTION CHARACTER
Transmi t ting a known string of characters not containing an Attention character did not cause the Main Channel to begin reception.
AN ATTENTION CHARACTER DOES NOT RESTART RECEPTION
After transmi tting a known string of characters containing an Attention character, the first character in the Main Channel buffer was not the character immediately following the Attention character.
Test 23 - Test Receive Data with Attention Recognition and Redundancy NOTE: For Dash 1 thru 5 only.
Test that the
oee
is being genera ted beginning wi th the fi rs t charac ter received, and that receiving an Attention character will restart theoee
generation.ERROR IN OCC GENERATION
Transmitting a known string of characters without an Attention character did not generate the expected
oee
value in the receive buffer.ATTENTION CHARACTER DOES NOT RESTART
oce
GENERATIONTransmi tting a known string of characters containing an Attention character did not cause the
oee
genera tion to be restarted with the character following the Attention character.Test 24 - Test Attention Receive Data with Redundancy NOTE: For Dash 1 thru 5 only.
Test that the OCC is being generated beginning with the first character received after the Attention character, and that receiving a second Attention character will restart the
oee
generation.ERROR IN
oce
GENERATIONTransmitting a known string of characters with an Attention character did not generate the expected OCC value in the receive buffer.
A SECOND ATTENTION CHARACTER DOES NOT RESTART OCC GENERATION
Transmitting a known string of characters containing two AttentIon characters did not cause the OCC generation to be restarted wi th the character immediately following the second Attention character.
Test 25 - Test Auto Answer
NOTE: For Dash 1 arId 6 only.
Tests that when a ring is detected or carrier is removed, Interrupt 7 will be generated along with either the Ring Detector flag (IFL bit 0) for ring indication or the Loss of Carrier flag (IFL bit 4) for carrier loss indication.
INTERRUPT GENERATED WITH CARRIER DETECTOR SET AND RING DETECTOR RESET
With carrier present and no ring indication, Interrupt 7 was generated, after issuing an Auto Answer (COM2).
RING INDICATOR DOES NOT GENERATE INTERRUPT PRIORITY LEVEL NO.7
With carrier and ring indication presen t, Interrupt 7 was not generated after issuing an Auto Answer (COM2).
RESETTING CARRIER DETECTOR DOES NOT SET LOSS OF CARRIER
With carrier present and no ring indication, issuing an Auto Answer (COM2) then dropping carrier did not set the Loss of Carrier flag (IFL bit 4).
LOSS OF CARRIER DOES NOT GENERATE INTERRUPT PRIORITY LEVEL NO.7
With carrier present and no ring indication, issuing an Auto Answer (COM2) then dropping carrier did not generate Interrupt 7.
TEST 26 - TEST DATA TERMINAL READY
NOTE: For Dash 4 and 9 only.
Tests that the Data Terminal Ready flag (OFL bi t 1) can be properly set and reset.
DATA TERMINAL READY OR RING DETECTOR STUCK HIGH
The known good Ring Detector flag (IFL bit 0) could not be reset by issuing an INIT and an OFL wi th th e D a taT e rm ina I Ready flag (OFL bit 1) reset.
DATA TERMINAL READY OR RING DETECTOR STUCK HIGH
The known good Ring Detector flag (IFL bit 0) could not be set by issuing an OFL with the Data Terminal Ready flag (OFL bit 1) set.
DVCL RESETS DATA TERMINAL READY
Issuing a DVCL with the Data Terminal Ready flag (OFL bit 1) set, reset the known good Ring Detector flag (IFL bit 0).
INIT DOES NOT RESET DATA TERMINAL READY
Issuing an IN IT with the Data Terminal Ready flag (IFL bit 1) set, does not reset the known good Ring Detector flag (IFL bit 0).
ASYNCHRONOUS 1I0.ADAPTER