

                     6400/6500/FP40 RS232 FIPP TEST program                
                                    01/08/02 -med 


        To run the TEST16 program in MSDOS or Win3.1, you will also need 
        the file FRYERS.COM from this disk.  The FRYERS.COM driver must 
        be run at least once prior to using a program that uses it to 
        talk to the Frye Electronics instrumentation.  See the Fryers 
        documentation for further information on the usage of the 
        FRYERS.COM driver.

        TEST16 is a real mode MS-DOS program. WTEST is a Windows 3.1 
        program. TEST16 and WTEST require FRYERS.COMM to be loaded first 
        before they will work. TEST16.EXE and WTEST.EXE will not run on 
        a WinNT machine because WinNT will not allow FRYERS.COM to 
        be loaded.

        Use TEST32.EXE for WinNT. TEST32 requires FRYERS32.DLL to be 
        loaded in the Windows directory, or in the directory in which 
        TEST32 is located. TEST32 will also run under Win95. TEST32 will 
        not run under Windows 3.xx.

        The TEST program is provided as a way to test the communications 
        between a Frye Instrument and the PC. To see the available 
        commands enter the command "H" at the command prompt.  
        To return to the DOS prompt, enter the command "X". 

        For more information on the commands available and their use with 
        specific Frye instruments, refer to the Fryers and FIPP 
        documents, and the related manual for your instrument.

        Note that the TEST program is designed for use with all possible 
        modes of operation. Some of the commands listed in the TEST 
        program may not be available on all instruments or in a specific 
        mode on the instrument. On newer instruments, the TEST program 
        may not directly have available all commands that can be 
        performed. The "B"uild command can be used to create a command 
        that is not specifically supported by the test program. Refer to 
        the appendix of the instrument being tested for the list of 
        available commands and modes of operation.

        The TEST program will adapt itself to most commands that it knows 
        about. When building an unknown command, you may need to set the 
        timeout values longer than the default standard. The "T"ime 
        command allows you to adjust the default timeouts in TEST.

        The TEST program is provided only as a means of testing the 
        operation of the RS232 communications link, no attempt has been 
        made to insure that it will work flawlessly in all situations. In 
        fact, entering other than a numeric value at the prompt will 
        cause the program to terminate with an error.





                                        1


        Requirements:

        The test program requires an IBM PC or compatible computer. You 
        will also need a serial port on the computer.  While the program 
        will run without an instrument connected to the serial port, 
        communications cannot occur unless an instrument with an RS232 
        option is attached to the PC's serial port. 


        Windows or MSDOS:

        Several versions of the TEST program are provided, Windows 
        versions and MSDOS versions. The standard real mode MSDOS version 
        is TEST16.EXE, the Windows 3.1 version is WTEST.EXE, and the 
        Win32 (95/98/NT/2K/ME/XP) version is TEST32.EXE.

        Note: The Windows versions WTEST.EXE can be found in the archive 
        file TEST.PAK (see end of this document).

             To run the test program from DOS:

        1. Connect the instrument to the PC's COM1 or COM2 RS232 port
           (if you will be using COM3 or COM4, see the note below about 
            using the SETPORT program).
        2. Run the FRYERS program to load the RS232 driver into the PC. 
        3. Turn on the instrument and configure it for normal operation.
        4. To run the program:
             a. if you are using Port 1 (COM1) on the PC
                 enter the command "TEST16"
             b. if you are using Port 2 (COM2) on the PC
                 enter the command "TEST16 2"      ( <--note the space )

        5. If everything is setup properly you should see the TEST 
           command prompt:


          Fryers RS232 Test Program - Version n.nn as of day month year
          Copyright 1988,2002 Frye Electronics, Inc.  (MS-DOS Version)
          Fryers Vn.nn using COMn  with IRQn  at 9600 baud  (A)

          Verify=TRUE - Enter function to perform (H for help) :  


        To see if the instrument is communicating, enter the command 
        number 28. This should respond with the instrument 
        identification and software version of the instrument and the 
        Fryers driver being used.

        At this point you may enter any command to tell the instrument to 
        perform an operation.  To get a list of the available commands 
        enter "H".  To return to DOS enter "Q", or press "Escape". 
        Remember, not all commands will work in all modes of operation or 
        on all instruments.  



                                        2


             To run the test program from Windows 3.1:

        1. Before entering Windows, insure that the FRYERS.COM driver is    
           loaded. This is most easily done by including the FRYERS.COM    
           file in your AUTOEXEC.BAT file to automatically load it when    
           you start up your computer.
        2. From Windows, install the WTEST.EXE program using the 
           Program Manager. Alternately, you can use the Run command to 
           run the program without installing it, but it is easier to 
           install it once and use the icon to launch the program.
        3. Be sure to add the "C2" command option to the command line 
           if you will be using COM2. 
        4. If everything is setup properly, a window should appear and 
           you should see the TEST command prompt in it (see above).



             To run the test program from Win95/98/NT/ME/2K/XP:

        1. Insure that the FRYERS32.DLL driver is located in the Windows 
           directory, or in the same directory where the TEST32.EXE 
           program is located.
        2. From Windows, use the Windows Explorer to find and run the
           TEST32.EXE program. Alternately, you can drag a copy of the 
           TEST32 icon to a folder or the desktop if you want to place it 
           in a location that is easier to find.
        3. Be sure to add the "C2" command option to the command line 
           (see file menu - properties selection) if you will be using 
           COM2 or another serial port. TEST32 supports up to 9 ports.
        4. If everything is setup properly, a window should appear and 
           you should see the TEST command prompt in it (see above).

























                                        3


        Using other serial ports on the PC: 

        COM1 and COM2 are the standard serial ports on the PC which most 
        devices that communicate serially will be connected to. Some 
        systems need more ports to communicate. To handle this, some PCs 
        have two additional ports available called COM3 and COM4. 

        To help those users who might need to use the extra ports, the 
        SETPORT program has been provided to modify the operation of 
        FRYERS.COM to use the alternate ports. (Note: the SETPORT program 
        is not needed with the TEST32 program.)

        To tell FRYERS.COM to set its Port 1 to use COM3, use the 
        following command:

          SETPORT P:1 C:3 

        To tell FRYERS.COM to set its Port 2 to use COM4, use the 
        following command:

          SETPORT P:2 C:4

        The SETPORT program has the ability to provide some limited 
        adaptation of the FRYERS.COM program to support non-standard 
        serial port configurations as well. See the SETPORT.TXT file for 
        more information on how to use the SETPORT program to adapt 
        Fryers to non-standard serial port configurations.

        Keep in mind that in most systems only two serial ports may be 
        active at any one time. This is a limitation of the PC hardware. 
        It is possible to set up the system to have more than two serial 
        ports active, but these are non-standard systems requiring 
        custom configuration. 

        In the TEST32 program, the multiple port issue is not a problem 
        because TEST32 uses the Windows API calls to access the serial 
        ports. Thus if Windows knows about the port, the TEST32 program 
        can use it without having to go through the manipulation 
        mechanism that FRYERS.COM requires with MS-DOS. 

        If you find that the port selected was incorrect, or you don't 
        know for sure which port is in use, either use the FCHECK program 
        to determine the correct COM port, or you can use the "C"omPort
        command to change the selected COM port while TEST is running. 

        Note that TEST will attempt to find the correct baudrate if you 
        give it an incorrect baudrate value. It may take a minute or two 
        to find the correct baudrate if an incorrect value was given. 
        Currently there should not be a need to specify a baudrate since 
        all Fonix equipment communicates at 9600 baud which is the 
        default baudrate used by the TEST program. Future Fonix 
        instruments may communicate at a faster speed which is the reason 
        for the ability to select an alternate baudrate.



                                        4


        Using the TEST program:

        Some test commands are machine specific. If the instrument does 
        not support the command, you will get an error message. The TEST 
        program is self-adapting to the instrument. Some commands will 
        operate slightly differently on different instruments. Normally 
        the TEST program will try to automatically adapt itself where 
        this is required by running the Version command (28) to determine 
        the instrument it is connected to.

        The "V"erify flag controls the error checking. Verify On (true) 
        is the standard operating default.  When Verify is On, each 
        command operation will be followed up with a Command Status check 
        on the instrument to verify that the command was processed 
        correctly. 

        In the case where a new command has been added that is not yet 
        supported by the existing command set in the TEST program, 
        the "B"uild command provides a mechanism to build a command from 
        scratch.

        The "M"onitor port command will show the continuous status 
        information of the COM port in use. This is primarily intended 
        for debugging the operation of the instrument interface.
        Refer to the Fryers documentation for a detailed description of 
        the register values being displayed.

        Commands that receive large data sets will write the data to an 
        ASCII text file. Each data point will be in absolute integer form 
        with one data point per line. Any existing file by the same name 
        will be overwritten. This is only true of known large data sets.
        Commands initiated by the build command function will only be 
        displayed on the screen. 

        The current three get commands that create large data files are:

          Command           file
        Get Curve       - CURVE?.DAT  : ? = curve number used
        Get Blob        - BLOB.DAT
        Get Probe Curve - PCURVE.DAT
















                                        5


        Commands which send large data sets expect the data to be 
        available in a ASCII text file. These files must consist of the 
        required data in ASCII form, one line per data point. The data 
        must be in absolute integer form (no decimal points).

        The current three set commands that expect data files are:

          Command         file
        Set Curve       - CURVE?.DAT     : ? = curve number used
        Set Phase       - PHASE.DAT
        Set Spectrum    - SPECTRUM.DAT

        These files must exist for the Set command to function.
        Sample data files are provided for reference purposes.

        The Label commands 6 and 66 will request the label be entered 
        from the keyboard and provide a simple editor to allow you to 
        enter the label data. 

        Source Code:

        The source code for the TEST program can be found in the 
        TEST.PAK file. Use the UNPACK.EXE program which can be found in 
        the INSTALL directory on this disk to unpack the source files 
        from the archive.

        Note: This program is for testing hearing aid analyzers. To test 
        the operation of an audiometer, see the ATEST program.

        *WARNING* *WARNING* *WARNING* *WARNING* *WARNING* *WARNING* 
        If you run the TEST16 or WTEST program in Win95/98, you must 
        close the MSDOS prompt window before you can run the TEST32 
        version of the program. When a MSDOS program grabs the serial 
        port hardware, the MSDOS prompt window retains ownership of the 
        hardware. The only way it can be released back to Windows is by 
        closing the MSDOS prompt window. 
        *WARNING* *WARNING* *WARNING* *WARNING* *WARNING* *WARNING* 
        -------------------------------------------------------------
        History:      01/04/89 med - original program
                      06/29/89 med - expanded menu
                      05/07/90 med - misc description cleanup 
                      01/20/92 med - added new commands to test
                      10/19/92 med - Windows version
                      12/17/92 med - moved windows code to archive
                      10/04/93 med - added FP40 functionality
                                      renamed to TEST (was TEST65)
                      09/27/94 med - added new supported fipp cmds
                      05/01/97 med - added fryers V5.0 support
                      01/08/02 med - revised 16 bit documentation
        <end>






                                        6
