(Page 3 of 3 in this chapter)


4.2 Verification Procedure

To verify that an AG Connect board is operational:

  1. Determine the device number of the board you wish to test.

    • Under OS/2, the device number of a board is determined by the position in which the board's I/O address appears in the AGCX environment variable in CONFIG.SYS. Devices are numbered from 0 upward. For example, if two boards are referenced in the variable as follows:

          set AGCX=m:0x0640,0x2140
      
      ...then the board at 0x0640 is device number 0, and the board at 0x2140 is device number 1.
    • Under NT, you assign your boards their device numbers during installation. For details, see section 3.3.

      
      
    • Under UNIX, the device number of a board is determined by the order in which you select its address during installation. For details, see section 3.4.

      
      
    • Start up the SW Utility in interactive mode. To do so, enter the following at the operating system prompt:

         sw
      
      The SW utility starts up, and displays its prompt:
         SW:
      
      The SW utility is ready for you to begin entering commands.
    • Direct the SW Utility to open the device driver and assign a handle to one of your boards. The command to do this is different under different operating systems:

      • Under UNIX, enter a command like the following at the SW: prompt:

            drv.OpenDevice /dev/agcx0x handle
        
        where x is the device number of the board you wish to test, and handle is the handle to give the device. For example, to assign handle "cx" to board 0, you would issue this command:
            drv.OpenDevice /dev/agcx00 cx
        
      • Under Windows NT or OS/2, enter a command like the following at the SW prompt:

            drv.LoadDriver handle=agcxsw x
        
        ...where x is the device number of the board you wish to test, and handle is the handle to give the device. For example, to assign handle "cx" to board 0, you would issue this command:
            drv.LoadDriver cx=agcxsw 0
        
        SW opens the driver and assigns handle "cx" to the device. Then the SW: prompt reappears.
      • Enter the following command to reset the board to a known initial state (replacing "cx" in the command with the handle of the board you are testing):

           drv.ResetSwitch cx
        
        The SW: prompt reappears.
      • Enter the following command to read the types of line interfaces installed on the board (replacing "cx" in the command with the handle of the board you are testing):

           drv.QueryTmSlot cx ID 16:0..n
        
        ...where n is the number of line interfaces your board has, minus 1. For example, if you had an S/T Connect board with handle "cx", you would enter:
           drv.QueryTmSlot cx ID 16:0..23
        
        ...since this board type has 24 line interfaces.
        The type of each line interface should appear on your display:
           Hybrid IDs:
        16:0: 0x10 16:1: 0x10 16:2: 0x10 16:3: 0x10
        16:4: 0x10 16:5: 0x10 16:6: 0x10 16:7: 0x10
        16:8: 0x40 16:9: 0x40 16:10: 0x40 16:11: 0x40
        16:12: 0x40 16:13: 0x40 16:14: 0x40 16:15: 0x40
        16:16: 0x40 16:17: 0x40 16:18: 0x40 16:19: 0x40
        16:20: 0x40 16:21: 0x40 16:22: 0x40 16:23: 0x40
        Note: This display will differ from board model to board model. "0x40" indicates a loop-start line interface, designed to connect to the public service telephone network. "0x10" indicates an operator work station line interface.
      • Repeat this test for each AG Connect board you have installed in your system.

        
        Note:  Make sure to assign each board a unique handle.
        
        
      • When you have finished testing your boards, enter the following command to exit the SW utility:

           xct.Exit 
        
        The operating system prompt reappears.


      (Page 3 of 3 in this chapter)


      Tech_Support@nmss.com
      Copyright © 1996, Natural MicroSystems, Inc. All rights reserved.