Name

SBRecord - Softboard instructor module

Synopsis

java SBRecord [-d]

Availability

Source is available at here, with all files here.

Description

The SBRecord module interacts with a Softboard driver that could be both locally and remotely located. The instructor module directs the driver to download the DSP code to the Softboard, and then receives messages from the driver.  Upon message receipt, the module displays the action on the console, as well as multicasts it to the group of student computers which are running SBView modules. The messages that are multicasted have an RTP header and thus can be used further by a server listening to RTP packets.

Options

 
-d  Print out debug information.
 
 

Installation

            Make sure that linux and solaris directories of the driver are under the directory containing SBRecord.java and SBRecord.conf files.
            sbdriver should point to either linux or solaris directory depending on the platform.

            Compile SBRecord.java using jdk1.1.6 or above.
                     javac SBRecord.java
 
 

Configuration

SBRecord instructor module

All of the configuration information for the instructor module is stored in SBRecord.conf file.  The order of items is important.

Here is an example:

TTL=5
Multicast Port=2255
Multicast IP=225.225.225.225
Driver Port=6666
Driver IP=128.59.16.150
Local Server Port=7777
PT=50

TTL is the time-to-live for multicast. Multicast Port and Multicast IP are for the server to use when sending strokes via multicast.
Driver Port and Driver IP are of the machine local to the Softboard, in most cases it will be the same as the instructor's machine, however
one can change them in case the local machine is very slow. Local Server Port is the port used by the Instructor's module in
communicating back with the driver. PT is part of the RTP header that is settable from the outside. PT is 0-127.

 

          Driver Module

          All of the configuration information for the Driver Module is stored in sbdriver.conf in the driver directory. The order of items is
          important.

          Example:
 

          Local Port=6666
          Remote IP=128.59.16.3
          Remote Port=7777

          Local Port is the port that the driver is listening on, the instructor will connect to this port. Remote IP and Port are those of the instructor machine.
 
 
 

Running

            From the directory containing SBRecord.java run:

                # For Linux
                cd sbdriver; sbdriver /dev/ttyS0; cd ..
 
                # For Solaris
                cd sbdriver; sbdriver /dev/ttya; cd ..

                If the local machine is not too slow open another xterm and run instructor's module:

                        java SBRecord
                        OR
                        java SBRecord -d # to see the debug information

                If the local machine is too slow, login to the remote machine to be used as the instructor's machine, export the display and run
                        java SBRecord.

                Make sure that the configuration file reflects your physical computer setup.

 

See Also

Author

Ilya Gaysinskiy, Columbia University

Copyright

Copyright 1998 by Columbia University; all rights reserved

Permission to use, copy, modify, and distribute this software and its documentation for research and educational purpose and without fee is hereby granted, provided that the above copyright notice appear in all copies and that both that the copyright notice and warranty disclaimer appear in supporting documentation, and that the names of the copyright holders or any of their entities not be used in advertising or publicity pertaining to distribution of the software without specific, written prior permission. Use of this software in whole or in parts for direct commercial advantage requires explicit prior permission.

The copyright holders disclaim all warranties with regard to this software, including all implied warranties of merchantability and fitness. In no event shall the copyright holders be liable for any special, indirect or consequential damages or any damages whatsoever resulting from loss of use, data or profits, whether in an action of contract, negligence or other tortuous action, arising out of or in connection with the use or performance of this software.


Last modified: 1998-09-17 by Ilya Gaysinskiy