ERROR(OPCS)		Optical Printer Control System		ERROR(OPCS)

    NAME
	error - a description of OPCS error/warning messages

    DESCRIPTIONS

	UNKNOWN COMMAND
	    The command that was executed is not known to the interpreter, and
	    probably has a typo. Try '?' to list all the commands.

	FADER NOT FULLY OPEN   FOR FDO/DXO
	FADER NOT FULLY CLOSED FOR FDI/DXI
	    When trying to do a fade/dx in, the shutter must first be 
	    completly closed, and when trying to do a fade/dx out, the shutter
	    must be completly open. 

	FILM BUCKLE or VIEWER OPEN
	HIT RETURN to CONTINUE or ALLSTOP to ABORT:
	    While trying to run the camera, the film buckle switch has been
	    tripped or the viewer is open.

	RECURSION ERROR
	    The RUN command prevents you from running a script that is
	    already running, to prevent infinite recursion.

	    A run script calling itself, or a child script that calls a 
	    parent is considered 'recursion'. Here a script calls itself:

       fred.run: cam 1 pro 1
                 run fred.run  <-- fails here

	    In this example, a child script calls one of its parents:

       test1.run: fdi 10 rep 10
                  run test2.run

       test2.run: fdo 10 rep 10
                  run test1.run  <-- fails here
					  The way to get the desired result
					  is to remove this line, and start
					  the scripts by executing e.g.:
					      DO 12 RUN TEST1.RUN

	NESTED TOO DEEP
	    Too many run script levels. When a script calls another script,
	    that is '2 levels' of nesting. Up to 10 levels of nesting are
	    allowed, before this error occurs.

	CANT OPEN
	    Could not open a file. Either the file dosn't exist, or part
	    of the pathname is invalid, or a file opened for writing to
	    is read only.

	*** EOF: (script.run)
	    This message is printed whenever the end of a run script is
	    reached.

	STOPPED AT LINE (#) OF (#)>(filename)
	    An error occurred in a run script, and this message indicates
	    the line number, nesting level, and the name of the script
	    where the initial error occurred. One message per nesting level
	    is printed, with the FIRST MESSAGE being the script containing
	    the error.

	INVALID REPEAT COUNT
	    In a DO command, the value specified was negative, or not a number.

	SPEED OUT OF RANGE OR INVALID
	    In a SPD command, the number specified was too low (0 or below)
	    or too high. Normally, the software cannot run the motors slower
	    than a 10 second exposure speed, but depends on the motor ramping
	    and acceleration values. Have you changed your ACC or RAMP values?

	INTERNAL FUNCTION UNDEFINED
	    A command that is not yet implemented was called. This kind of
	    error should be brought to the attention of the programmer.

	UNKNOWN OPCSDEFS COMMAND
	    A command in an OPCSDEFS file was invalid.

	INVALID FEET/FRAMES
	    A specified feet/frames value was invalid. Usually, the frames
	    value exceeded the number of frames in a foot.

	MISSING ARGUMENT AFTER 'command'
	    The software expected an argument where one wasn't supplied.

	OUT OF MEMORY
	    The software did not have enough memory to execute. Usually,
	    the cause is that there are too many levels of DOS shells, or
	    too many 'residing' programs in memory.

	    This can happen by incorrectly exiting software (via ^BREAK)
	    or by invoking a shell, and forgetting to exit the shell (via
	    ! vi, and then doing a :sh and running opcs again) or by having
	    too many resident programs in your \AUTOEXEC.BAT or \CONFIG.SYS 
	    files.

	    Or your machine does not have enough memory. OPCS should be able
	    to run on machines with 256k or more.
	    
	STACK OVERFLOW
	MEMORY ALLOCATION ERROR
	MALLOC ERROR
	    These are internal errors that indicate something really went
	    wrong in the software. A bug in the software can cause this
	    error, and should be brought to the attention of the OPCS
	    system programmer. Also, power glitches can cause these errors.

	SYNC FAULT
	    The software was not able to feed values fast enough to the motors. 
	    Get a faster computer. Seriously. 

            This is a fatal error which means the motors probably stalled
	    because the software couldn't feed velocities fast enough to 
	    the motors, ie. cpu is too slow. Get a faster cpu.

	    This error can also occur when debugging is enabled; debugging
	    messages can sometimes slow the software down enough to where
	    it can't update the motors quickly enough.

    SPD: SPEED TOO SMALL (IGNORED)
	    The resulting speed set by the SPD(OPCS) command would have been
	    a value too small. 

    SEE ALSO
	Documentation on the commands that caused the errors you encountered.

    ORIGIN
	Gregory Ercolano, Los Feliz California 12/15/89

© Copyright 1997 Greg Ercolano. All rights reserved.