OPCSETUP(DOCS)		Optical Printer Control System		OPCSETUP(DOCS)

        opcsetup - opcs setup notes


	This text describes how to set up the OPCS software from scratch,
	especially for a NEW installation. To greatly simplify this text,
	it is assumed you know certain DOS techniques and terminology that
	is available from your DOS manual, such as copying files to and from
	floppies, what subdirectories are, how to create them, execution
	PATHs, etc.

	It is assumed you have:

		o A KUPER control card
		o An IBM AT compatible computer running at 25 MHz or more.
		o 512K or more of system memory.
		o Running MS-DOS 2.10 or higher
		o A hard disk (needed only for the online manual pages)
		o ANSI.SYS configured in your \CONFIG.SYS file (see your
		  DOS manual for installing ANSI.SYS)

	Assuming you only have the OPCS software on the distribution floppy,
	and a new hard disk with DOS setup on it, just execute the following 
	from DOS:

	This will automatically install the entire OPCS system on your
	hard disk in the directory \opcsk100.

	The software will create the following subdirectories (if they dont
	already exist):

		\OPCSK100\MAN		# online manual
		\OPCSK100\WORK		# the OPCS work directory
		\OPCSK100\BIN		# binaries (should be in your path)

	NOTE: If you don't want to use the AUTOEXEC.BAT that comes with the
	opcs installation floppy, you will need to modify the one on your
	hard disk so that it at *least* does the following:

		> The PATH contains \OPCSK100\BIN

		> The \OPCSK100\BIN\START.BAT program is executed

		> The current directory should be changed to \OPCSK100\WORK

        To verify that the software is installed properly, reboot the
	system (so changes to the AUTOEXEC.BAT and CONFIG.SYS file take
	effect), and type OPCS. The software should start, printing the
	copyright notice, and indicating the OPCSDEFS file loaded properly,
	and finally, displaying the large counters up on the screen.

	At any time, you can type 'q' or 'qq' to quit the software to 
	return to DOS.

	If you see error messages are being printed, the software either 
	cannot access the OPCSDEFS.OPC file which should be in your current 
	directory, or there are errors in the file. Use the text editor
	to correct or otherwise customize the OPCSDEFS.OPC file.

	Execute 'man cam' from within the software to verify that the 
	online manual has been installed properly. If so, documentation
	on the 'CAM' command should come up with a MORE prompt at the
	bottom of each page. Hit 'SPACEBAR' to advance a page, 'B' to 
	go back a page, or 'Q' to quit. Hitting RETURN will advance single

	If you see any errors while trying to run the MAN command, take 
	the following actions:

	'Bad command or filename'
	    Either the 'MAN.EXE' command or 'MORE.EXE' is not in the machine's
	    execution path. Make sure these files are in your executable
	    \BIN directory, and the directory is properly specified in 
	    DOS's execution PATH. Use the DOS 'set' command to check.

	'man: could not open map'
	    The file 'map' is not in the \USR\CATMAN directory, or the 
	    directory \USR\CATMAN does not exist.

	    MAN may be using DOS's inferior MORE program to view the manual
	    pages. Type ^C or ^BREAK to break out of DOS's MORE program,
	    and make sure the \BIN directory is in the execution path before
	    the DOS directory is. Example:

	    If your execution path is setup in your AUTOEXEC.BAT file to
	    check the DOS directory before checking the BIN directory, 
	    such as:


	    Then change it to read:


TUNING THE SOFTWARE FOR NEW HARDWARE It is probable that the software should now immediatly be able to make motors spin round and round, assuming the hardware is connected correctly. Maybe not smoothly, or making complete revolutions, but that comes next. You must now spend some time jumping in and out of the software, tuning your OPCSDEFS.OPC file to suit your hardware. Keep in mind that each time you make a change to the OPCSDEFS.OPC file, you must either rerun the OPCS software, or execute 'ldefs opcsdefs.opc' to force the software to recognize the changes. The following checklist should help you correct most problems: o If your motors stall when trying to run them at speeds that they SHOULD turn at, you may want to tune the RAMP(OPCSDEFS) and SPD(OPCSDEFS) values in your OPCSDEFS.OPC file If you think the motors may just be running too fast, modify the SPD(OPCSDEFS) commands in your OPCSDEFS.OPC file to run the motor slower. See man pages on this command for details. o If frame-oriented motors are not making complete revolutions, alter the PPR(OPCSDEFS) command to change the number of pulses in a revolution for your motor. Most shutters need 2000 pulses to revolve one full turn when using micro stepper drives. For those of you with VISTAVISION shutters, 4000 might be more suitable. o If a motor runs reverse when told to run forward, and vice versa, change the DIRXOR(OPCSDEFS) value for that motor. (see man pages on DIRXOR). This command allows you to invert the direction of a motor without modifying the hardware. o If your fader does not fully open, fully close, or does not do linear dissolves properly, see the INTERP(OPCSDEFS) documentation for setting interpolation positions for every 10 degrees on the fader. o If you dont like the initial speed the software comes up with for the camera or the default running speed for the projector, see the SPD(OPCSDEFS) documentation (which will come after the SPD(OPCS) docs). o If the fader appears to suffer from hardware slop (ie. the sequence 'cls shu 150' and 'opn shu 150' do not send the physical shutter to the exact same position, even though the motor does not appear to stall) this is due to mechanical hysterisis in the shutter mechanism, and can usually be alliviated ENTIRELY by use of the SLOP(OPCSDEFS) command, even in systems where slop of 5 to 10 degree deviations (typical of most old printers) is found. SLOP is a cool command, and can make really sloppy hardware work very accuratly. Once you have tuned the system, and wish to start learning the commands, type ? in the software to get a list of all available commands, and read the online MAN pages for each command that interests you. ORIGIN Gregory Ercolano, Los Feliz California 11/29/89
© Copyright 1997 Greg Ercolano. All rights reserved.