THE OCULUS-F/64 FRAME GRABBER User's Manual

THE OCULUS-F/64
FRAME GRABBER
User's Manual
Edition 2.0, Revision 0
preliminary
CORECO INC.
6969 Trans-Canada Hwy, Suite 142
St-Laurent, Quebec
H4T 1V8
Canada
Technical Support: (514) 333-1301
BBS: (514) 333-6592
24 Hour FAX: (514) 333-1388

NOTICE
Every effort is made to ensure the information in this manual is accurate and
reliable. When changes are made, the manual is updated accordingly in a new
version. Minor changes affect the manual revision number. Major changes,
such as a software update, change the edition number.
When requesting a new manual, please specify the product and software
version you are using, so we can send you the appropriate manual and edition.
CORECO Inc. reserves the right to make changes in specifications at any time
and without notice.
Printing History:
Edition 1 Revision 0 June 1994
Edition 1 Revision 1 June 1994
Edition 1 Revision 2 June 1994
Stock Number:
The Oculus-F/64 Frame Grabber User's Manual WA-F64M-USERM

Welcome
Congratulations on the purchase of your new Oculus-F/64 1 video digitizer
from CORECO.
If this is your first Oculus-F/64 product, please read carefully chapter 2 for
procedures that are essential to the proper installation, configuration, and
operation of the Oculus-F/64 video digitizer.
In addition please read the manual summary that follows. The summary along
with the index will allow you to find the information you need for efficient use
of the Oculus-F/64.
Experienced users should review this manual for changes and addendum's
concerning the Oculus-F/64.
1 Oculus is Latin for eye.
Coreco Inc. Page iii

HOW TO USE THIS MANUAL
Chapter I General Overview
Provides a general introduction to the Oculus-F/64, where hardware
features, options and abilities are summarized.
Chapter II Installation and Configuration
An essential chapter detailing installation and configuration, both for
the hardware and software, of the Oculus-F/64.
Chapter III The Oculus-F/64 Block Diagram
Provides a descriptive review of the Oculus-F/64 hardware structure.
This chapter describes the various hardware systems such that the user
may have an understanding of the standard and optional capabilities
of the Oculus-F/64.
Chapter IV OCULUS-F/64 Development Toolkits
Provides a descriptive overview of the ODX Programmers Toolkit
and its use with the Oculus-F/64. Application features and
capabilities are highlighted.
Appendix A Summary of Specifications
Provides full specification details pertaining to the Oculus-F/64 both
for standard and optional configurations.
Appendix B The OCULUS-F/64 Configuration Switches
Describes the configuration switches for setting the base I/O address
and interrupt channel. Refer to this section if you need to make
changes because of conflicts in your system.
Appendix C Input / Output Connectors
Index
Refer to this appendix for specifications on all Oculus-F/64
connectors.
Page iv The OCULUS-F/64 User's Manual

TABLE OF CONTENTS
Welcome......................................................................................... iii
How to Use This Manual .............................................................. iv
Table Of Contents ......................................................................... v
1.0 GENERAL OVERVIEW....................................................... 1-1
1.1 Introduction............................................................................... 1-3
1.2 Oculus-F/64-Compatibility........................................................ 1-3
1.3 Camera Interface ....................................................................... 1-3
1.4 Acquisition Rate........................................................................ 1-3
1.5 Acquisition Resolution.............................................................. 1-4
1.6 Signal Conditioning................................................................... 1-4
1.7 Processing ................................................................................. 1-4
1.8 Memory..................................................................................... 1-5
1.9 Display ...................................................................................... 1-6
1.10 Software Compatibility ........................................................... 1-6
1.11 Oculus-F/64 Part Numbers...................................................... 1-8
2.0 INSTALLATION AND CONFIGURATION ....................... 2-1
2.1 Introduction............................................................................... 2-3
2.2 Oculus-F/64 Installation............................................................ 2-4
2.3 Hardware Configuration............................................................ 2-6
2.4 Oculus Intelligent Configuration Program ................................ 2-23
2.5 F64PRO Installation.................................................................. 2-23
3.0 THE OCULUS-F/64 BLOCK DIAGRAM............................ 3-1
2.1 Introduction............................................................................... 3-3
3.2 Input .......................................................................................... 3-4
3.3 Processing ................................................................................. 3-7
3.4 Output ....................................................................................... 3-9
4.0 OCULUS-F/64 Development Toolkits ................................... 4-1
4.1 info ............................................................................................ 4-3
4.5 Computer Platforms and Operating Systems:............................ 4-3
Appendix A OCULUS-F/64 SPECIFICATIONS ...................... 5-1
A.1 Oculus-F/64 Configurations ..................................................... 5-3
A.2 Acquisition ............................................................................... 5-3
A.3 Synchronization........................................................................ 5-3
A.4 Camera Inputs .......................................................................... 5-4
A.5 Processing ................................................................................ 5-4
A.6 Memory .................................................................................... 5-4
A.7 Display ..................................................................................... 5-5
A.8 Environmental Conditions........................................................ 5-6
Appendix B OCULUS-F/64 Configuration Switches ................ 6-1
B.1 I/O Base Address Selection ...................................................... 6-3
B.2 Interrupt Channel Selection ...................................................... 6-4
B.3 Configuration Jumpers ............................................................. 6-5
B.4 Physical Location ..................................................................... 6-6
Appendix C OCULUS-F/64 Connectors .................................... 7-2
C.1 Analog Video Input Connector................................................. 7-4
Coreco Inc. Page v

C.2 Analog Video Output Connector .............................................. 7-5
C.3 TTL Digital Video Interface Connector ................................... 7-6
C.4 VGA Pass-Through Connector................................................. 7-7
C.5 Connector Locations................................................................. 7-8
INDEX............................................................................................ 8-1
Page vi The OCULUS-F/64 User's Manual

• • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • •
CHAPTER 1
• • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • •
• • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • •
GENERAL OVERVIEW
• • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • •
• • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • •
This chapter covers: ■ Introduction
■ Oculus-F/64 compatibility
■ Camera Interface
■ Acquisition Rate
■ Acquisition Resolution
■ Signal Conditioning
■ Processing
■ Memory
■ Display
■ Software Compatibility
■ Oculus-F/64 Part Numbers

Page 1-2 The OCULUS-F/64 User's Manual

1.1 INTRODUCTION
The Oculus-F/64 is a high performance image acquisition and processing
board for the ISA 16-bit bus. Targeted at sophisticated image processing
applications, Oculus-F/64 incorporates several dedicated processors which
operate in conjunction with a unique memory architecture to deliver real-time
histograms, real-time arithmetic operations, and high speed 32 bit floating
point image processing. The Oculus-F/64 reflects Coreco's continuing
commitment to deliver innovative and quality products.
1.2 OCULUS-F/64 COMPATIBILITY
The Oculus-F/64 is for use ISA standard computers complying with the IEEE
ISA standard. It occupies one or two 16 bit ISA position in the computer
system.
Optional plug-on adapter modules provide industry standard connections to
various cameras. With the adapter installed, the Oculus-F/64 occupies two slot
positions.
1.3 CAMERA INTERFACE
The Oculus-F/64 was designed to acquire data from virtually any source and to
simplify interfacing camera and frame grabber. Compatible with RS-170,
CCIR, large array area scan cameras and line scan cameras, the Oculus-F/64
supports a wide range of resolutions, frame rates and pixel depths. Up to four
analog cameras, (one capable of accepting a differential signal) and one digital
camera (with a 8/10/or 12 bit data path) can be connected to the Oculus-F/64.
An optional EIA-422 digital interface supports differential output cameras
typically used in noisy environments. Other connections include horizontal
and vertical sync inputs-and-outputs, trigger inputs-and-outputs for external
event synchronization, a pixel clock input-and-output, and general I/O lines.
Image acquisition from non-standard sources is simplified through Coreco's
Oculus Configuration Program, an interactive program which allows users to
adjust video parameters including pixel clock frequency, sync source, vertical
resolution and other video timing parameters. Timing parameters can then be
stored for later recall.
1.4 ACQUISITION RATE
The Oculus-F/64 is capable of acquiring data at a rate of up to 40 million
pixels per second. By utilizing a sophisticated digital phase lock loop, the
sampling clock frequency (pixel clock) can be varied from 510 kHz to 40 MHz
in increments of less than 10 kHz, while maintaining pixel jitter to less than
1/6th of a pixel. For applications requiring higher accuracy, the Oculus-F/64
can accept an external pixel clock.
Coreco Inc., General Overview Page 1-3

1.5 ACQUISITION RESOLUTION
Resolutions ranging from 32 x 32 up to 4k x 4k are possible. Variable frame
rate capability allows data to be captured from high or slow frame rate
cameras, freezing data for later analysis and viewing. The table below
demonstrates capture rates for various types of cameras.
Camera Type Capture Resolution Maximum Capture
Speed
RS-170 640 x 480 30 Frames/sec
CCIR 768 x 575 25 Frames/sec
Large Area Array 1k x 1k 35 Frames/sec
Large Area Array 2k x 2k 9 Frames/sec
Line Scan Camera 1k elements 35,000 Lines/sec
High Frame Rate 512 x512 140 Frames/sec
High Frame Rate 256 x 256 560 Frames/sec
1.6 SIGNAL CONDITIONING
1.7 PROCESSING
Programmable anti-aliasing filter along with range and offset adjustments
allow precise digitization control, maximizing the digitization range over the
video level of interest. After digitization, pixel data passes through input lookup
tables (ILUT), for thresholding, gamma correction or other signal
conditioning functions. For 8 bit data, one-of-thirty two 256 entry look-up
tables can be selected, for 10 bit data, one-of-eight 1024 entry look-up tables
can be selected, and for 12 bit digital data, one-of-two 4096 entry input lookup
tables is available.
The processing and memory architecture of the Oculus-F/64 was designed for
simultaneous image acquisition and processing. Images can be analyzed in
less than one frame or line time. The high speed memory communications
bandwidth provides access to previously stored images for analysis even while
acquisition is occurring.
Page 1-4 The OCULUS-F/64 User's Manual

1.8 MEMORY
The Oculus-F/64 incorporates a high speed digital signal processor and graphic
signal processor, both of which operate in conjunction with a real-time
histogram processor and Coreco's proprietary “Image Processing Engine” (IP-
Engine). These elements, combined with a high memory communications
bandwidth, (80 Mbytes/sec on the VRAM bus plus 40 Mbytes/sec on the
DRAM [DSP] bus for a total of 120 Mbytes/sec), provide enough processing
throughput for any imaging application. The following table lists performance
specifications for a standard RS-170 camera with 512 x 512 images.
Function Performed By Time
Histogram Histogram Processor Frame Time
Addition IP-Engine Frame Time
Subtraction IP-Engine Frame Time
Division DSP TBA
Convolution
(Laplacian)
DSP TBA
2D FFT DSP TBA
The Oculus-F/64 uses VRAM memory to image display and both DRAM and
VRAM memory for image acquisition and processing. Physical frame buffer
arrays can be programmed into smaller logical frame buffers enabling
acquisition and processing of multiple images.
1.8.1 FIELD UPGRADEABLE MEMORY MODULES
Field upgradeable VRAM memory modules, available in sizes of 2, 4, or 8
Mbytes, simplify memory expansion. Oculus-F/64 products can accommodate
up to 16 Mbytes of VRAM memory and 32 Mbytes of DSP DRAM memory,
and 32 Mbytes GSP DRAM memory for a total of 80 Mbytes of on board
memory.
1.8.2 PROGRAM AND OVERLAY MEMORY
Oculus-F/64 products accommodate up to 4 Mbytes of graphic and text overlay
memory. TMS34020 GSP program code is stored in on-board DRAM
memory, expandable to a maximum of 32 megabytes. GSP memory can also
be used to store and process image data. TMS320C40 DSP program code is
stored in 128 kbyte of 0 wait-state SRAM memory while operating on DRAM
memory frame buffer which can be expanded to a maximum of 32 Mbytes.
1.8.3 16 BIT FRAME BUFFER
Coreco Inc., General Overview Page 1-5

1.9 DISPLAY
The Oculus-F/64-DSP16 has a 16 bit frame buffer. In addition to acquiring
and storing highly dynamic images, the Oculus-F/64-DSP16 has the added
benefit of allowing mathematical operations to be performed without overflow
or underflow results. When displaying 16 bit images, a display level controller
is used to select which group of 8 bits drives the display circuits.
The Oculus-F/64 supports single screen operation by overlaying VGA graphic
information (from a VESA standard VGA feature connector) onto the video
from the VRAM frame buffer. All standard VGA and SVGA resolutions are
supported including 1024 x 768 NI and 1280 x 1024 I. (See appendix A for a
list of supported resolutions).
Users of Windows 3.1 can display live, still or processed images in a scaleable
window. Image size can be scaled to fit in a window or for large images, such
as 2k x 2k images, users can pan and scroll to view the entire image.
The Oculus-F/64 also supports dual screen operation driving VGA, SVGA or
high resolution RGB monitors in addition to RS-170, CCIR or RS-343
monitors. To view very high resolution images the Oculus-F/64-DSP16
supports a maximum display resolution of 1600-by-1280.
Three independent output look-up tables offer maximum flexibility in single
screen or dual screen mode. In dual screen mode, independent frame buffer
and overlay output lookup tables allow for graphic overlays and pseudo
colored video images. In single screen mode, VGA information also passes
through an output look-up table, providing a large degree of flexibility.
1.10 SOFTWARE COMPATIBILITY
1.10.1 F/64PRO
Oculus-F/64 ships with a the Windows application, F64Pro. Supported
functions are image acquisition, images storage and retrieval, range and offset
controls and a library of image processing functions.
1.10.2 ODX: OCULUS DRIVER FOR OC-X DEVICES
The Oculus-F/64 is supported by a device independent software interface that
provide access to, and enables processing of, digital images. Each driver
function is optimized to use the hardware capabilities of the device for the
fastest results. The programming toolkit is detailed below.
• Oculus Driver Programmers ToolKit (for MS-DOS and MS-Windows).
• Oculus Driver Command Interpreter (ODCI).
• Compilers supported: Microsoft C/C++
Borland C/C++
Page 1-6 The OCULUS-F/64 User's Manual

The Oculus library of C-callable functions provides complete control of the
board. Typical functions include acquisition and display control, frame buffer
read and write operations, and graphic operations. Image processing functions
include histograms, contour following, convolutions and morphological
operations.
1.10.3 OKS: OCULUS KERNEL SYSTEM
INTEGRATED SOFTWARE PLATFORM DEDICATED TO IMAGE PROCESSING AND
MACHINE VISION
HIGHLIGHTS:
OKS provides a multilayered, open architecture designed for applications
written for single task operating systems (such as DOS) or multitasking
operating systems (such as Windows). Applications can interface to OKS at
any layer. All layers of OKS are accessible and the interconnection between
layers is automatic. Each layer of OKS is thoroughly documented. (See
chapter 3 for a detailed description).
Allows system integrators to design image processing applications using a
standard platform.
Allows implementing new algorithms quickly and efficiently with its open
architecture.
Provides a device independent interface allowing applications to be ported to
future CORECO boards without modification.
Provides access to fast and flexible graphic and vision primitives.
Coreco Inc., General Overview Page 1-7

1.11 OCULUS-F/64 PART NUMBERS
Part No. DESCRIPTION
6480-00080 F/64, High Performance Frame Grabber
TMS34020 based frame grabber with 1024 x 1024 x 8 bit frame buffer.
Includes real-time histogram processor, IP-Engine and one megabyte
VRAM memory. The maximum digitization rate is 40 MHz, 20 Mhz
when using IP-Engine with frame buffer.
6480-DSP80 F/64-DSP, DSP based Image Processor
TMS320C40 based image processing board with 2048 x 1024 x 8 bit
frame buffer and no overlay. Image processing performed by high speed
TMS320C40 DSP, real-time histogram processor and Coreco's IP-
Engine. Inlcudes TMS34020 GSP for display and host control, 2
megabytes VRAM memory and one megabyte DRAM. Maximum
digitization rate is 40 MHz. Maximum display resolution 1280 x 1024.
6480-DSP60 F/64-DSP16, 16 bit DSP based Image Processor
TMS320C40 based image processing board with 2048 x 1024 x 16 bit
frame buffer. Image processing performed by high speed TMS320C40
DSP, real-time histogram processor and Coreco's IP-Engine. Inlcudes
TMS34020 GSP for display and host control, 4 megabytes VRAM and 4
megabytes of DRAM. Maximum digitization rate is 40 MHz. Display
level controller permits viewing any 8 bits amongst 16. Maximum
display resolution 1600 x 1280.
Accesories Memory Expansion Modules
VRAM expansion modules can be used for image capture, processing
and display
6480-62200 Oculus-F/64 VRAM memory expansion module, 2 Mbyte
2 Mbyte memory for overlay or frame buffer
6480-62400 Oculus-F/64 VRAM memory expansion module, 4 Mbyte
4 Mbyte memory for overlay or frame buffer
6480-62800 Oculus-F/64 VRAM memory expansion module, 8 Mbyte
8 Mbyte memory for overlay or frame buffer
Page 1-8 The OCULUS-F/64 User's Manual

Part No. DESCRIPTION
DRAM expansion modules can be used for image capture and processing
X273-83322 Oculus-F/64 DRAM memory expansion module, 1 Mbyte
1 Mbyte memory for frame buffer
X273-06322 Oculus-F/64 DRAM memory expansion module, 4 Mbyte
4 Mbyte display memory for frame buffer
X273-26322 Oculus-F/64 DRAM memory expansion module, 16 Mbyte
16 Mbyte display memory for frame buffer
X273-46322 Oculus-F/64 DRAM memory expansion module, 32 Mbyte
Accessories
32 Mbyte display memory for frame buffer
6480-42237 EIA-422, 12 bit digital interface
EIA-422 digital interface module. Accepts 12 bit digital information
with DB-37 connector
6480-42268 EIA-422, 12 bit digital interface
EIA-422 digital interface module. Accepts 12 bit digital information
with SCSI -2 connector
CM84-VGAC0 VGA Feature Connector
CM84-33800 VGA Terminator
Required for Single Monitor Applications
Required for Single Monitor Applications
6480-AD100 Oculus-F/64 -AD10
10 Bit Interface A/D
Coreco Inc., General Overview Page 1-9

Software
090-99600 Oculus-F/64 Software Package
Includes TC-Pro executable software, Oculus-F/64 DOS and Windows
device driver and User's Manual (included with every board)
090-99001 DOS Developers Toolkit (required for DOS development)
Includes a library of C-callable routines and manuals.
090-99003 Windows Developers Toolkit ( for Windows development)
Includes a library of C-callable routines, TC-Pro source code, DLL and
programmers manual.
090-99??? COOL: Coreco Object Oriented Library
Cables
CM84-33100 Video output cable
Analog Cameras
Implemented as an object oriented architecture.
Provides easy application development for supported CORECO devices.
Increases reliability and readability of application software.
CM84-03200 Four camera analog input cable
CM84-60000 Four camera analog input cable, 3 analog, 1 differential
Manual
6482-60000 Oculus-F/64 Users Manual
Page 1-10 The OCULUS-F/64 User's Manual

• • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • •
CHAPTER 2
• • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • •
• • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • •
INSTALLATION AND CONFIGURATION
• • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • •
• • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • •
This chapter covers: ■ Introduction
■ Oculus-F/64 Installation
■ Hardware Configuration
■ Oculus Intelligent Configuration
Program
■ F64PRO Installation

Page 2-2 The OCULUS-F/64 User's Manual

2.1 INTRODUCTION
This manual assumes that you have a basic knowledge of DOS, Windows, and
how to install hardware into a PC. The hardware installation consists of a few
simple steps as outlined below.
• Verify the factory default base address of the Oculus-F/64 for conflict in
your computer. If it needs to be changed, please turn to appendix B for
information on changing the base address.
• Opening your computer and selecting a full-length slot (two slot position
for an Oculus-F/64 with a optional camera adapter module).
• Inserting the Oculus-F/64 into the PC and securing the bracket.
• Connecting the VGA feature cable and the supplied VGA board
terminator, if using the single monitor mode.
• Connecting the Video Cables.
• Installing configuration software (DOS or windows version) and the
F/64Pro demonstration application.
CAUTION: STATIC DISCHARGE
Static electricity can damage the Oculus-F/64 and other components in your
computer. Always discharge yourself by touching the metallic case of the
computer (with the computer power cord plugged into a grounded outlet),
before handling any computer hardware. Keep the Oculus-F/64 in its antistatic
bag when it's not installed in a computer.
Coreco Inc., Installation and Configuration Page 2-3

2.2 OCULUS-F/64 INSTALLATION
SETTING THE BASE ADDRESS DIP SWITCH
The SW1 DIP switch is used to set the I/O base address of the Oculus-F/64
board. The factory default Base Address is 280h. The location of SW1 on the
board and diagrams for various address selections, are found in Appendix B of
this manual.
Typically there is no address conflict requiring a change in I/O address. But if
there is, the new address chosen must differ from the addresses of other boards
residing in the computer. Both the DOS and Windows configuration programs
have a configuration item for selecting the new I/O address and both programs
will display a pictorial of the required switch positions.
Caution: Do not use a pencil to set the miniature switches, because the
graphite residue can cause damage to the switches.
OTHER SWITCHES AND JUMPERS
In all normal situations, there is no need to change other configuration switches
and jumpers from their factory default. Appendix B details what these defaults
are and when they may need changing.
INSTALLING THE OCULUS-F/64 INTO THE PC
To install the Oculus-F/64 into a PC use the following procedure. Please
ensure that you have discharged any static electricity by grounding yourself to
the chassis of the PC before you begin.
• Turn off your computer, but keep it connected to the AC power source.
This maintains a ground connection to the computer chassis. Remove the
cover.
• Choose an available 16-bit full length expansion slot. (Two slots are
required for Oculus-F/64's with camera adapter modules).
• Install the Oculus-F/64 and secure the bracket with the fastening screw.
This provides a solid electrical ground to prevent damage from static
discharge when connecting or disconnecting cameras and monitors.
• Connect camera and display monitor as described in the following
sections. The suggested power on sequence is display monitor, computer,
and camera.
Page 2-4 The OCULUS-F/64 User's Manual

CONNECTING THE VGA FEATURE CABLE FOR SINGLE MONITOR SOLUTIONS
Use of the VGA feature connector is required for single screen operation,
(wherein VGA and video information are both displayed on the same monitor).
The feature connector, (supplied with the Oculus-F/64) is the flat ribbon cable.
Connect the cable to the Oculus-F/64 feature connector (J18) located on top of
the board and the other end to the VGA card feature connector. Never connect
the feature cable with the power on.
Also supplied with the Oculus-F/64 is a VGA terminator required to simulate a
monitor load on the VGA card. (In single screen operation the VGA monitor
is connected to the Oculus-F/64 card). The VGA terminator is an encapsulated
plastic DB-15 pin connector.
The feature cable is not required when a separate monitor is used to display
the video images (dual monitor mode) and should be removed from the
Oculus-F/64 card.
CONNECTING THE INPUT VIDEO CABLES
Analog Input Cables
The video source is connected to DB2, the 9 pin connector on the Oculus-F/64
(see appendix C). Use video input cable Part CM84-03200 (4 analog input) or
Part CM84-60000 (3 analog, 1 differential analog).
Connect the BNC connector marked M1 (Camera #1), M2 (Camera #2), M3
(Camera #3), or M4 (Camera #4) to the video output of the camera.
Digital Input Cables
TBA TBA TBA TBA TBA TBA TBA TBA
CONNECTING THE OUTPUT CABLES
Single Monitor Setup
Disconnect your VGA monitor from the VGA card and connect it to the
Oculus-F/64 board connector labeled DB1, the 15 pin output connector (see
appendix C for location). Connect the VGA terminator provided with the
Oculus-F/64, on the output of the VGA card. Connect the feature connector
cable between the Oculus-F/64 (J18) and the VGA card feature connector.
Dual Monitor Setup
Dual monitor applications do not require the feature connector to be installed.
Carefully remove the feature cable from the Oculus-F/64 main board. Store it
in the box that the Oculus-F/64 was shipped in.
Depending on the auxiliary video monitor, the following connections are made.
Coreco Inc., Installation and Configuration Page 2-5

VGA
• Connect the DB15 connector of the auxiliary VGA monitor directly onto
the Oculus-F/64 board.
RGB
• Connection to an RGB monitor requires the DB15 to BNC cable
(Part 84331). The RGB output cables, R MON, G MON, and B MON
are attached to the corresponding inputs on the auxiliary monitor. The
composite sync cable marked CS MON is also connected to the composite
sync input on the monitor.
• Some RGB monitors require separate horizontal and vertical sync signals.
In this case, HSOUT and VSOUT outputs are connected to the
corresponding inputs on the monitor, instead of CS MON. Other
monitors require a sync signal on one of the color lines. In this case only
the R MON, G MON, and B MON cables need to be connected and sync
is enabled on one of the RGB lines with the hardware configuration
program for the Oculus-F/64, as detailed later in this chapter.
RS170 or CCIR Monitor
Use the GREEN output cable and enable sync on green in the display sync
selection of the configuration program. The correct output frequency is
also set via the configuration program.
2.3 HARDWARE CONFIGURATION
INSTALLING THE OCULUS-F/64 DEVICE DRIVER
The Device Driver must be installed and configured in order for the Oculus-
F/64 board to function properly. The installation procedure is:
• Insert the diskette labeled Oculus-F/64 Device Driver into a drive
of your computer.
• Make that drive the current drive.
• Type INSTALL.
This will install the contents of the diskette into a sub directory called
C:\ODF64 on the hard disk of your computer and run the Oculus-F/64
Configuration program. After configuring the Oculus-F/64 you should take the
time to read and print the various text files in the \ODF64 directory for
supplemental information.
During installation you are prompted to select the DOS or Windows
configuration program that you want to execute. Please note that both the DOS
configuration program (CONFIG.EXE) and the windows configuration
program (ODF64STP.EXE) are installed in the \ODF64 directory for your use
when required.
Page 2-6 The OCULUS-F/64 User's Manual

For simplicity, the following information is based on the basic DOS
configuration program. The windows version has the same configuration items
but looks different.
INITIAL CONFIGURATION MENU
The initial setup screen allows you to change various default selections as
described below.
Oculus-F/64 INSTALLATION PROGRAM Version 1.0
[ 1 ] Installation Type WINDOWS
[ 2 ] Oculus-F/64 Directory c:\ODF64
[ 3 ] Base Address (hex) 280
Board Revision B
[ 4 ] Quit Installation
[ 5 ] Start Installation
ITEM [ 1 ] INSTALLATION TYPE
Enter Selection: 1
A DOS installation loads the software onto your disk and starts the DOS based
configuration program. The ODF64.EXE file is then used to load the
configuration parameters when you use the Oculus-F/64. A Windows
installation will additionally start Windows, create a Oculus-F/64 program
group with icons, and start the windows based configuration program.
ITEM [ 2 ] OCULUS-F/64 DIRECTORY
Allows changing the default drive and directory for the driver installation.
ITEM [ 3 ] BASE ADDRESS
If you have changed the base address on the Oculus-F/64 , please enter the new
address here.
ITEM [ 5 ] START INSTALLATION
Select to copy all Oculus-F/64 driver files to the chosen directory.
CONFIGURING THE OCULUS-F/64 DEVICE DRIVER
The following description of the Oculus-F/64 configuration is based on the
DOS configuration program. This is identical to the windows configuration
except for screen design. Both configuration programs create and update the
ODX.INI file located in the windows directory or directory specified by the
DOS environment variable ODXPATH.
Coreco Inc., Installation and Configuration Page 2-7

The initial menu screen of the configuration program appears as follows.
Configuration File Setup
[ 1 ] Directory to ODX.INI: C:\ODF64
[ 2 ] Boot Drive: C
Note: The Directory to the ODX Configuration file ODX.INI will be
saved in a DOS Environment Variable called ODXPATH. This variable
will be set in the AUTOEXEC.BAT File.
ITEM [ 1 ] DIRECTORY TO ODX.INI
Enter Selection (ESC for Main Menu): 1
By default, the directory where the configuration parameter file (ODX.INI) is
saved is C:\ODF64. A different drive and directory can be specified, as
required.
ITEM [ 2 ] BOOT DRIVE
If the boot drive is other than drive C, please specify that drive, so that
AUTOEXEC.BAT can be modified. Your original AUTOEXEC.BAT file
will be renamed to AUTOEXEC.COR.
MAIN MENU: OCULUS-F/64 CONFIGURATION PROGRAM
Oculus-F/64 CONFIGURATION PROGRAM Version 0.02
MAIN MENU
[ 1 ] Current Device 1
[ 2 ] Number of Device(s) 1
[ 3 ] Hardware/Software Information
[ 4 ] Base Address (hex) 280
[ 5 ] Reset to Default Configuration
[ 6 ] Configure Device
[ 7 ] Configuration File Setup
[ 8 ] Cancel Configuration Program
[ 9 ] Save current Configuration and Quit
Enter Selection: 1
Page 2-8 The OCULUS-F/64 User's Manual

ITEM [ 1 ] CURRENT DEVICE
The Current Device refers to the Oculus-F/64 board that will be configured.
The default setting of Current Device = 1 assumes the typical case where there
is only one Oculus-F/64 installed. When multiple Oculus-F/64 are installed,
the board being configured is selected here. Note that each Oculus-F/64
installed must be set with different I/O base addresses.
ITEM [ 2 ] NUMBER OF DEVICE(S)
This item declares the number of Oculus-F/64 boards installed in the computer.
The total number must be entered before any one board can be configured.
The default case assumes that there is one Oculus-F/64.
ITEM [ 3 ] HARDWARE/SOFTWARE INFORMATION
Selection of Item 3 presents a screen with information about the installed
Oculus-F/64, such as board revision, installed memory, software driver
version, etc. If a board fault is suspected, selection of item 3 may display a
message stating that there is a communications error. This will be useful for
problem diagnoses. Please note that the I/O base address must be set correctly.
ITEM [ 4 ] BASE ADDRESS (HEX)
The factory default address is 280h. If a different address is required because
of a conflict in your computer, select an alternative address here. There are
six possible addresses for the Oculus-F/64. When a new address is selected, a
screen will display a graphic drawing to assist you with setting the new DIP
switch settings (SW1). Refer to appendix B for the location of SW1.
Base Address (hex)
[ 1 ] 280
[ 2 ] 290
[ 3 ] 2a0
[ 4 ] 2b0
[ 5 ] 2c0
[ 6 ] 2d0
Enter Selection: 2
ITEM [ 5 ] RESET TO DEFAULT CONFIGURATION
Selecting item 5 resets all configuration parameters to a factory default state, if
required.
ITEM [ 6 ] CONFIGURE DEVICE
Coreco Inc., Installation and Configuration Page 2-9

Selecting item 6 will present the Oculus-F/64 Configuration Menu. The menu
will display the current state of the driver. This state is either defined by the
Oculus-F/64 section of the ODX.INI file if it exists or the factory defaults for
the Oculus-F/64.
Select and modify the configuration items as required to match your setup, as
detailed below.
Configuration Menu
Current Device: 1
[ 1 ] Acqu. Sync Source: Camera Master (Sync on composite
Video)
[ 2 ] Acqu. Type Generic RS-170 / NTSC
[ 3 ] Acqu. Video Format: RS-170 (American) 10.00 MHz
(512x484)
[ 4 ] Camera Connector: Camera #1
[ 5 ] Display Video Format: 512 hor. x 480 ver. pixels
Non-Interlaced
[ 6 ] Memory Format: 512 hor. x 512 ver. pixels
[ 7 ] Output Sync Enable: None
[ 8 ] Pixel Size: 8 bits/pixel
[ 9 ] Custom Camera
[ 10 ] Custom Display
[ 11 ] Bus Interface
[ 12 ] VGA PassThrough
Enter Selection (ESC for Main Menu): 1
SELECTION [ 1 ] ACQU. SYNC SOURCE
The Acquisition Sync Source setting determines whether the input device or
the Oculus-F/64 board issues the sync information by selecting "Camera
Master" or "Camera Slave" respectively. In the case of "Camera Master" the
user selects the type of sync signal provided by the input device, as shown
below. For monochrome cameras (CCIR, RS170), the selection is Camera
Master (Sync on Composite Video).
For cameras that are driven with separate sync or composite sync, choose
“Camera Slave” and make the appropriate connections using the sync drives
available on the Oculus-F/64 input cable.
Page 2-10 The OCULUS-F/64 User's Manual

Acquistion Sync Source
[ 1 ] Camera Master (Sync on Composite Video)
[ 2 ] Camera Master (Sync on Composite Sync)
[ 3 ] Camera Master (Separate Sync)
[ 4 ] Camera Slave
SELECTION [ 2 ] ACQU. TYPE
Enter Selection: 1
Acquisition Type allows selecting the camera type. A number of popular
camera types are supported. Note that *.VID files are still required to control
timing parameters except for generic RS-170 or CCIR cameras.
As an example, the Cohu camera (item 6) will operate as a standard RS-170
camera when the acquisition type is Generic RS-170. But if the acquisition
type is specified as the Cohu 4910 Series, the Oculus-F/64 will support the
Cohu camera's integration mode.
[ 1 ] Other
Acquistion Type
[ 2 ] Generic RS-170/NTSC
[ 3 ] Generic CCIR/PAL
[ 4 ] Kodak MegaPlus XHF, Single Channel
[ 5 ] Kodak MegaPlus XHF, Dual Channel
[ 6 ] Cohu 4910 Series
[ 7 ] Kodak MegaPlus M1.4
[ 8 ] Kodak MegaPlus M1.6
[ 9 ] Kodak MegaPlus M4.2
[ 10 ] Cohu 4110 Digital
[ 11 ] Hamamatsu C4742
[ 12 ] Xillix MicroImager Model 1400
Enter Selection:
Coreco Inc., Installation and Configuration Page 2-11

SELECTION [ 3 ] ACQU. VIDEO FORMAT
The Acquisition Video Format for standard cameras should correspond to the
type of video source that is being used. Choose between RS-170 or CCIR
video source. The pixel clock frequency, expressed in MegaHz determines the
number of pixels digitized per horizontal video line.
Note: For square pixels, choose RS-170 12.27 MHz or CCIR 14.75 MHz.
Acquisition Video Format
Format Pixel Clock Width and Height
[ 1 ] RS-170 (American) 12.27 MHz (640 x 484)
[ 2 ] RS-170 (American) 10.00 MHz (512 x 484)
[ 3 ] CCIR (European) 14.75 MHz (768 x 574)
[ 4 ] CCIR (European) 10.00 MHz (512 x 574)
Enter Selection: 2
SELECTION [ 4 ] CAMERA CONNECTOR
Select the camera input that will be used for the monochrome camera.
Multiple cameras can be connected and selected individually via the
application software.
Camera Connector
[ 1 ] Camera #1
[ 2 ] Camera #2
[ 3 ] Camera #3
[ 4 ] Camera #4
Enter Selection: 1
Page 2-12 The OCULUS-F/64 User's Manual

SELECTION [ 5 ] DISPLAY VIDEO FORMAT
This selection defines the standard Display Video Format of the Oculus-F/64.
In dual monitor applications, select the display mode appropriate to the
monitor that will be connected as the display device for the Oculus-F/64. As
an example, Super VGA monitors (which connect directly onto the Oculus-
F/64), can be typically driven by the Oculus-F/64 at 640 by 480 (72 Hz) or 800
by 600 (72 Hz). The specifications of the monitor should be consulted when
selecting a display resolution.
When the Oculus-F/64 is configured in the single monitor mode using the
VGA feature cable, the display format must match the video format and
vertical refresh rate that the VGA video board will operate at when in graphics
mode. Please refer to the VGA board manual when verifying the possible
operating modes.
The Oculus-F/64 supports a wide range of super VGA resolutions and vertical
refresh rates, but there may be modes offered by certain VGA boards that are
not supported. In such cases, use the utilities provided by the VGA board to
set the refresh rate to a combination supported by the Oculus-F/64 as listed
below. Please note that the Oculus-F/64 does not require a specific
combination of sync polarity on the video pass-through. All four combinations
are supported.
Coreco Inc., Installation and Configuration Page 2-13

Display Video Format
Hfreq. Vfreq. Interlaced Hpixels Vpixels
(kHz) (Hz)
[ 1 ] 15.734 30 Yes 512 484
[ 2 ] 15.734 30 Yes 640 484
[ 3 ] 15.625 25 Yes 512 576
[ 4 ] 15.625 25 Yes 768 576
[ 5 ] 31.50 60 No 512 480
[ 6 ] 37.90 72 No 512 480
[ 7 ] 31.48 60 No 640 480
[ 8 ] 37.88 72 No 640 480
[ 9 ] 31.47 70 No 720 400
[ 10 ] 35.20 56 No 800 600
[ 11 ] 37.90 60 No 800 600
[ 12 ] 44.00 70 No 800 600
[ 13 ] 48.10 72 No 800 600
[ 14 ] 35.60 87 Yes 1024 768
[ 15 ] 48.40 60 No 1024 768
[ 16 ] 56.50 70 No 1024 768
[ 17 ] 57.90 72 No 1024 768
[ 18 ] 48.90 87 Yes 1280 1024
[ 19 ] 63.70 60 No 1280 1024
[ 20 ] 74.00 70 No 1280 1024
[ 21 ] 76.00 60 No 1600 1200
SELECTION [ 6 ] MEMORY FORMAT
Enter Selection: 7
This selection specifies the dimensions of the logical frame buffers. Physical
memory installed on the Oculus-F/64 is best utilized when divided up into
multiple, smaller frame buffers, which are still large enough for the camera
acquisition. Each logical frame buffer can be operated on, independently from
image data stored in other logical frame buffers.
Page 2-14 The OCULUS-F/64 User's Manual

The Memory Format should equal or exceed the size of the digitized image so
as to not crop the camera image. Alternatively, using a smaller Memory format
has the advantage of increasing the number of logical frame buffers.
Entry 5, as shown below, allows user defined logical frame buffer
specifications. There are no limitations to the setting except the size of
physical memory.
Memory Format
Width Height
( [5]: User Defined )
[ 1 ] 256 256
[ 2 ] 512 512
[ 3 ] 1024 512
[ 4 ] 1024 1024
[ 5 ] 512 512
Enter Selection: 2
SELECTION [ 7 ] OUTPUT SYNC ENABLE
Output Sync Enable is normally set to NONE. This is the default case where
the display monitor, such as a VGA display, gets horizontal and vertical sync
drive from the separate outputs on the display connector. When required, sync
can be enabled on one of the RGB color outputs, such as when the monitor
used is a RS-170, and requires sync-on-green.
Output Synchronization Enable
[ 1 ] None
[ 2 ] Red Channel
[ 3 ] Green Channel
[ 4 ] Blue Channel
Enter Selection: 1
Coreco Inc., Installation and Configuration Page 2-15

SELECTION [ 8 ] PIXEL SIZE
This selection is applicable only on the Oculus-F/64 DSP16. Pixel Size
specifies whether a pixel is 8 bits or 16 bits. Note that when using 8 bit pixels,
the number of logical frame buffers is doubled.
Pixel Size
[ 1 ] 8
[ 2 ] 16
Enter Selection: 1
SELECTION [ 9 ] CUSTOM CAMERA
If you require a custom camera definition file, configured with the
CAMERA.EXE program, enter the full path and file name here (such as
c:\path\user.vid).
SELECTION [ 10 ] CUSTOM DISPLAY
If you require a custom display definition file, configured with the
DISPLAY.EXE program, enter the full path and file name here (such as
c:\path\user.vod).
SELECTION [ 11 ] BUS INTERFACE SETUP
The Bus Interface Setup screen defines the method of communication with the
Oculus-F/64 and the host computer system. The Bus Interface main menu is as
shown below.
Bus Interface Setup
[ 1 ] Mapping: I/O Mapped
[ 2 ] Memory Map Address: D0
[ 3 ] Memory Map Size: 8K
[ 4 ] Memory Map Bus Width: 16-bit
Enter Selection (ESC for Configuration Menu): 1
The first item, Bus Interface Mapping, configures the Oculus-F/64 for I/O
addressed communications and data transfers or direct memory mapped
transfers.
Page 2-16 The OCULUS-F/64 User's Manual

I/O addressed communication is the default case, where the base address set by
switches SW1 defines the 16 address block used by the Oculus-F/64. This is
the most trouble free configuration, requiring only that the base address be
unused in the host computer. As an example, using the factory default I/O
address of 280, the I/O address range 280 to 28f needs to be free. (Note that all
addressing is described in hex format).
Bus Interface Mapping
[ 1 ] Memory Mapped
[ 2 ] I/O Mapped
Enter Selection: 2
The alternative mode of communication is by memory map addressing. This
method requires that a portion of the computer's address space be mapped to
access a portion of the Oculus-F/64 frame buffer memory. The potential for
conflict is high unless the various preparations, as described below, are
performed. If the Oculus-F/64 is configured for memory mapped interfacing,
conflicts will quickly show themselves by a crashed application or computer,
since all communications are via memory map.
For memory mapped communications, two items need to be defined. Memory
Map Address defines the base memory of the block of addresses that will be
pointed to the Oculus-F/64. The second is Memory Map Size which defines
the size of the continuous addresses used for direct memory addressing. The
two selection screens are shown below.
Memory Map Address (ie: D0000 = D0)
Enter Value [ C8..FFE] ( D0) ? D0
Coreco Inc., Installation and Configuration Page 2-17

Memory Map Size
[ 1 ] 8K
[ 2 ] 16K
[ 3 ] 32K
[ 4 ] 64K
[ 5 ] 128K
[ 6 ] 256K
[ 7 ] 512K
[ 8 ] 1Mb
[ 9 ] 2Mb
[ 10 ] 4Mb
Enter Selection: 1
DOS MEMORY MAP SETUP EXAMPLE
Oculus-F/64 DOS applications are able to use memory mapping in an unused
upper memory block (below 1Mbyte) of the host computer. As an example,
suppose you want to configure a 64k memory map size starting at address
D0000. (Note that PC addressing is often described using the segment portion
only, such as D000).
The required steps are as follows:
• Verify that your computer system BIOS does not shadow the upper
memory block that you wish to use. In this example, the block from
D0000 to DFFFF must not be shadowed. Please refer to your computer
system manual for information on upper memory or adapter BIOS
shadowing selection.
Page 2-18 The OCULUS-F/64 User's Manual

• Configure your memory manager to not use the memory block you wish to
use. As examples, various memory managers are described below.
MS-DOS EMM386 (Expanded-Memory Emulator)
Modify the command line by adding the exclude option:
(i.e. device=EMM386.EXE x=D000-DFFF)
386MAX (Qualitas)
Add the following line to the file 386max.pro:
RAM = D000-DFFF
QEMM-386 (Quarterdeck Expanded Memory Manager-386)
Add the following command line option:
x=D000-DFFF
• Configure the Oculus-F/64 board to use memory mapping at starting
address D0 and that the memory map size is 64k.
Warning: Errors in memory mapped interfacing configuration can crash
your computer system when executing Oculus-F/64 applications.
WINDOWS MEMORY MAP SETUP EXAMPLE
Oculus-F/64 windows applications such as F64PRO.EXE can utilize memory
mapped interfacing, where the memory mapped block is located below the 1
Mbyte boundary or above. The requirements are defined below.
Memory Mapping Below 1 Mbyte: In this case all of the setup requirements
for DOS applications must be performed, as stated in the previous section.
In addition, windows must be made aware of the memory range required, so as
to prevent a conflict. For the same example as above where the required
memory map block is D0000 to DFFFF, modify SYSTEM.INI (located in your
windows directory), as shown below.
In SYSTEM.INI under the section [386Enh] add the statement:
EMMExclude=D000-DFFF
Memory Mapping Above 1 Mbyte: In this case the constraints described for
DOS and windows application for memory mapping below 1 Mbyte, do not
exist. The only requirement is that there is no physical memory located in the
address space that will be used for memory mapping. This includes system
memory and memory located on other plug in boards. Additionally, the
Oculus-F/64 has an upper limit for the start of the memory mapped block at
FFE000 (8k below the 16 Mbyte address) and the memory mapped block can
not go above 16 Mbyte. Note that the 16 Mbyte limitation is because the PC
ISA 16 bit expansion slot can not address above that boundary.
Coreco Inc., Installation and Configuration Page 2-19

As an example suppose that your computer system has 8 Mbyte of memory
installed with no other adapter board using any memory space. The Oculus-
F/64 memory mapped block can be assigned to start at the 8 Mbyte address
and can be as large as 4 Mbyte if that amount of memory is installed on the
Oculus-F/64.
Thus first choose the Memory Map Address as 800 (which implies 800000),
then select the Memory Map Size between 8k to 4 Mbyte (limited by the
memory on the Oculus-F/64.
MEMORY MAP BUS WIDTH
The last configuration item for Memory Mapped communications is the data
word width used. The factory default is 16 bit accesses, but can be change to 8
bit. You need to change it to 8 bit if you experience data corruption or other
signs of conflicts.
One example of possible conflict is when a memory map block is assigned to
start at the C8000 address. VGA video boards have BIOS PROMs addressed
typically at C0000 to C7FFF. If the VGA BIOS access is 8 bits, limitations in
PC expansion bus design specifications for plug-in boards, might unknowingly
cause conflicts with 16 bit Oculus-F/64 communication. Changing the Oculus-
F/64 Memory Map Bus Width to 8 bits should solve the problem.
Memory Map Bus Width
[ 1 ] 8-bit
[ 2 ] 16-bit
Enter Selection: 2
SELECTION [ 12 ] VGA PASSTHROUGH SETUP
For single monitor DOS applications, the default VGA video mode is 16 color.
If your DOS application is written for the 256 color VGA mode, you need to
change the VGA Mode configuration here to 256 Color.
Please note that Windows applications using the ODF64.DLL, (such as
F64PRO), automatically detect the number of colors (16 or 256) of the
windows video driver. The windows configuration program does not have this
configuration item. If you are using the DOS configuration program, you do
not need to change this configuration item.
Page 2-20 The OCULUS-F/64 User's Manual

VGA PassThrough Setup
[ 1 ] VGA Mode 16 Colors
[ 2 ] VGA 16-color Keying Color 4
[ 3 ] VGA 256-color Keying Color 239
[ 4 ] VGA Clock Phase Normal
Enter Selection (ESC for Configuration Menu): 1
Vga Mode
[ 1 ] 16 Colors
[ 2 ] 256 Colors
Enter Selection: 1
The VGA keying color used in an application can be changed from the factory
default choices to any one of the available colors in both 16 and 256 color
mode. The two choices are independent of each other. The defaults are 4 in
16 color mode and 239 in 256 color mode. Enter the value of the keying color
used in your application if different then the factory defaults.
VGA 16-color Keying Color
Enter Value [ 0.. 15] ( 4) ? 4
VGA 256-color Keying Color
Enter Value [ 0..255] (239) ? 239
The last selection box of the VGA PassThrough Setup is for VGA Clock
Phase. This item is a simple phase invert switch identified as Normal or Invert.
There is no right or wrong position and is totally dependent on the
characteristics of the VGA board being used. If there seems to be image jitter
when in single monitor mode, select the alternate VGA clock phase. One of
the two positions will provide a stable image.
Coreco Inc., Installation and Configuration Page 2-21

ITEM [ 7 ] CONFIGURATION FILE SETUP -
This selection on the main menu selects the Configuration File Setup screen.
This is the same screen that is initially presented when installing the Oculus-
F/64 driver. Select this item if you need to make changes to Oculus-F/64 file
locations. Refer to the description near the beginning of this section for more
information.
ITEM [ 8 ] CANCEL CONFIGURATION PROGRAM
Select this item if you wish to quit the configuration program without making
any changes.
ITEM [ 9 ] SAVE CURRENT CONFIGURATION AND QUIT
Select this item when you have completed the Oculus-F/64 configuration. The
ODX.INI file will be updated with all modified parameters.
Windows applications for the Oculus-F/64 (such as F64PRO) automatically
utilize the configuration information in ODX.INI via the ODF64.DLL (see
Oculus-F/64 windows development toolkit for implementation information).
For DOS Oculus-F/64 applications, the Oculus-F/64 driver interface (which
reads the ODX.INI file), is loaded into memory via the F64.BAT file.
F64.BAT needs to be executed before any Oculus-F/64 DOS application can
run. Thus F64.BAT can be executed from AUTOEXEC.BAT for
convenience, and only needs to be run again between computer boot-ups if the
configuration of the Oculus-F/64 is changed.
Page 2-22 The OCULUS-F/64 User's Manual

2.4 OCULUS INTELLIGENT CONFIGURATION PROGRAM
TBA TBA TBA TBA TBA TBA TBA TBA TBA
2.5 F64PRO INSTALLATION
F64PRO.EXE is Coreco's Oculus-F/64 demo windows application. It allows
acquisition control, frame buffer selection, various video data filter operations,
and file I/O. F64PRO provides simple diagnostic functions along with basic
frame buffer operations, such that a Oculus-F/64 user can be acquiring and
saving images immediately. In addition, the source code for F64PRO forms
the main programming example for the Oculus-F/64 Windows development
toolkit.
Installation is straight forward, as most windows applications are.
• Insert the distribution disk into a floppy drive.
• Within windows Program Manager, select File Run and type a:install (or
b:install).
• Accept the default drive and directory offered for installation or change it
if you wish.
• The install program will create a Oculus-F/64 program group if it does not
exist and a F64PRO icon will be placed in it. Start F64PRO as any other
windows application.
Coreco Inc., Installation and Configuration Page 2-23

• • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • •
CHAPTER 3
• • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • •
• • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • •
THE OCULUS-F/64 BLOCK DIAGRAM
• • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • •
• • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • •
This chapter covers: ■ Introduction
■ Input
■ Processing
■ Output

Page 3-2 The OCULUS-F/64 User's Manual

3.1 INTRODUCTION
The OCULUS-F/64 monochrome frame grabber is a singleor dual slot ISA bus
board. There are three versions available:
• Oculus F/64 Acquisition, processing and display with 8 bit
frame buffer
• Oculus F/64-DSP Acquisition, processing, display with 8 bit frame
buffer and high performance DSP
• Oculus F/64-DSP16 High performance imaging board with DSP and 16
bit frame buffer
The Oculus-F/64 has a flexible acquisition section which provides easy
interfacing to different video sources. The input video format is programmable
and limited only by the amount of memory installed on board and the 40 MHz
maximum sampling rate. The TMS34020 graphic processor provides basic
image processing functionality and also provides acquisition control (up to 40
MegaSamples/sec).
The Oculus-F/64-DSP and F/64-DSP16 are equipped with the TMS320C40
DSP. This provides enhanced acquisition sampling rates, a powerful general
image processing engine, and control for the Oculus-F/64 bus interface.
Real-time IP Engine and histogram processor provide point processing on
incoming or feedback images. Optional 16-bit ( Oculus-F/64-DSP16) point
processing is also available at half the speed when feedback is used (up to 20
MegaSamples/sec with feedback).
There are two types of memory used as frame buffer memory on the
Oculus-F/64, VRAM and DRAM, up to a total of 80 Mbytes. A maximum of
16 Mbytes VRAM memory can be installed. The VRAM memory stores
images that can be viewed via the Oculus-F/64 display system. The remaining
memory is composed of standard 32-bit SIMM DRAM but its contents can not
be viewed directly via the display circuits. A maximum of 32 Mbytes of
DRAM can be installed for the DSP system and another 32 Mbytes of DRAM
can be installed for the GSP. The minimal configuration is 1Mb of frame
buffer memory and 1Mb of GSP memory.
The acquisition and display sections are totally independent. The display
frequencies can be genlocked to a VGA board (VGA pass-through) or
generated on the board. The highest display resolution is 1600-by-1280 at
60Hz. Three separate Look-Up-Tables for VGA, overlay, and video buffer are
provided and can be used simultaneously. The Oculus-F/64-DSP16 also
incorporates a display leveling circuit for displaying any 8 bits from the 16-bit
images.
Coreco Inc., The OCULUS-F/64 Block Diagram Page 3-3

3.2 INPUT
DB9
1
2
3
4 (Diff)
CS
VS
Analog Input
HS/CS
Optional Camera
Adapter Module
34 Pin Header
Analog Input
Source
Selector and
Anti-alaising
Filter
Digital Interface
Control signals
Trigger
Clock
40 MHz A/D
8 Bits
Sync
Separator
and
Acquisition
Control
12 Bit Digital Data path
General I/O
3.2.1 ANALOG INPUT SELECTOR AND ANTI-ALAISING FILTER
8
Input
Look-Up
Table
8/16
Bit
Data
Four analog cameras can be connected via the male DB-9 input connector.
One input is capable of accepting a differential camera output signal typically
used in electrically noisy environments. The input selection is made by
software commands.
Two software selectable anti-alaising filters are available. One with low-pass
filter corner set at 20 Mhz and the second is programmable to have a corner
frequency from 1Mhz to 10 Mhz. Additionally, a filter by-pass selection is
available, if required.
Inputs are by default AC coupled but can be DC coupled. Selection of input
coupling is made by software.
3.2.2 ANALOG TO DIGITAL CONVERTER
Input video is digitized via the analog to digital converter at various standard
sampling rates or optionally at custom rates up to 40 million pixels per second.
The sampling clock frequency (pixel clock) can be varied from 510 kHz to 40
MHz in increments of less than 10 kHz, while maintaining pixel jitter to less
than 1/6th of a pixel.
A/D converter range and offset controls allow adjusting the digitized range of
the input video. As shown in the figures below any portion of the video input
can be selected for digitization to one of 256 gray levels, over the selected
range. The effects of range and offset on the acquired image are similar to
brightness and contrast controls on a video monitor.
Page 3-4 The OCULUS-F/64 User's Manual

Error! Not a valid filename.
Digitizing the entire signal. Digitizing a lower portion only.
Range Control
Error! Not a valid filename.
Digitizing a central portion. Digitizing a small portion.
3.2.3 DIGITAL INPUT INTERFACE
Offset Control
The Digital Interface port (J18) provides a general purpose TTL video
interface. As detailed in appendix C, the 34 pin interface provides a flexible
means of connecting a large variety of digital sources or analog sources via
supplemental . Industry standard input and output control signals (such as
external horizontal and vertical sync, external pixel clock, external trigger) are
supplemented by 8 general I/O pins that are defined in software by using the
Oculus Configuration Program. Video data words can be 8, 10, or 12 bits.
With 10 or 12 bit sources captured on an Oculus-F/64 16 bit board, the
acquisition data is justified to the lower bits of the 16 bit word. For example, a
12 bit source uses data bits 0 to 11, with bits 12 to 15 set to 0.
Coreco Inc., The OCULUS-F/64 Block Diagram Page 3-5

3.2.4 OPTIONAL DIGITAL INPUT ADAPTER MODULES
To facilitate connecting various cameras, plug on adapter modules are
available that translate the Oculus-F/64 digital input connector to the required
connector mounted on a standard PC expansion card bracket. Note that the
Oculus-F/64 requires two slots in the computer when the adapter is installed.
Various adapters are available such as the standard EIA-422 interface used by
various camera manufacturers, and other varieties such as the 68 pin SCSI type
connector.
3.2.5 VARIABLE ACQUISITION PARAMETERS
Image acquisition from non-standard sources is simplified through Coreco's
Oculus Configuration Program, an interactive program which allows users to
adjust video parameters including pixel clock frequency, sync source, vertical
resolution and other video timing parameters. Timing parameters can then be
stored for later recall.
3.2.6 INPUT LOOK-UP TABLE
After digitization, pixel data passes through an input look-up table (ILUT), for
thresholding, gamma correction or other signal conditioning functions. The
driver default loads the ILUT with a linear ramp such that there is a one-to-one
correspondence between input data and output data.
For 8 bit data, one-of-thirty two 256 entry look-up tables can be selected, for
10 bit data one-of-eight 1024 entry tables are available, and for 12 bit data, two
4096 entry look-up tables are available.
Users can pre-program the available ILUTs with various transformation
functions and switch between them with a single instruction.
Page 3-6 The OCULUS-F/64 User's Manual

3.3 PROCESSING
From
Acquisition
Section
8/16 Bit
Data
Coreco
F/64 Bus
Coreco
IP-Engine
Feedback
8/16 Bit, 40 Mbyte/sec
DRAM Frame
Buffer
1-32 Mbytes
6 Channels, 8 Bits each
20 Mbytes/sec
16 Bit
3.3.1 IP ENGINE
10 Bit
MUX /
DEMUX
8/16 to 32
Bus
Arbitrator
Histogram
Processor
TMS320C40
40 MHz DSP
(optional)
80 Mbyte/sec
To 16 Bit ISA Bus
TMS34020
40 MHz GSP
TMS34094
Host
Interface
VRAM Frame
Buffer
1-16 Mbytes
To Display
Section
4 Channels,
8 Bits each
To Overlay
LUT
Coreco Inc., The OCULUS-F/64 Block Diagram Page 3-7
32 Bits
GSP DRAM
1 to 32 Mbytes
Overlay
Frame
Buffer
Coreco's proprietary IP-Engine performs real-time image averaging,
subtractions, and logical operations. The IP-Engine is a 40 MIP processor
which performs mathematical operations between incoming images and images
already stored in a selected frame buffer. The flexibility of the IP-Engine
allows it to be factory programmed with custom functions, for real-time
execution of repetitive operations.
3.3.2 HISTOGRAM PROCESSOR
The Oculus-F/64 series incorporates a real-time histogram processor which
produces histograms on images ranging in size up to 4k by 4k. Real-time
histograms facilitate object identification, object detection and intensity
analysis. The histogram processor operates independently of any other
processor, with input data (8 or 10 bit only) read from the IP-Engine output
bus. The histogram processor result data is read directly by the GSP, allowing
for display of that data or transfer to the on-board DSP or host system
application.
3.3.3 TMS34020 GRAPHIC SIGNAL PROCESSOR
The TMS34020 GSP advanced 32 bit processor is standard on all Oculus-F/64
boards. This high performance 40 MHz processor is optimized for imaging
and graphics applications because of its unique array addressing support and
efficient manipulation of hardware-supported data types such as pixels and
2-dimensional pixel arrays. The GSP architecture provides for high
performance in moving large blocks of data, data management, display control
and refresh, image processing, and host communications. The TMS34020 is
also responsible for all operations within the graphics overlay plane.

On Oculus-F/64 boards without the optional DSP installed, the TMS34020
GSP is responsible for data acquisition, at a maximum digitization rate of 40
million samples/sec. When the IP-Engine is being used, for example during
real-time additions or subtractions, the maximum acquisition rate is limited to
20 million samples/sec. The GSP operates with the VRAM frame buffer, the
GSP program memory which can also be used for frame buffers, and the
Overlay frame buffer.
3.3.4 TMS320C40 DIGITAL SIGNAL PROCESSOR
For applications requiring even higher performance, the OCULUS-F/64 can be
supplemented with the TMS320C40, a 32 bit floating point digital signal
processor capable of performing over 250 Million Operations Per Second
(MOPS). The TMS320C40's high performance is achieved through the
precision and wide dynamic range of the floating-point units, multiple
operations per clock cycle, large on-chip memory, a high degree of parallelism,
six full duplex communications channels controlled by a DMA coprocessor,
and two 80 Mbyte/sec local buses for connection to high speed memory.
The local buses provide enough data throughput to process and acquire images
simultaneously. Convolutions, complex 2D filters or FFT's are accelerated by
using the 32 bit floating point processing unit of the TMS320C40, which
performs over 20 million floating point operations per second.
3.3.5 DISPLAY MEMORY
Display memory (also used for image acquisition and processing) is composed
of VRAM type memory. The minimum memory installation is 1 Mbyte
(soldered on board) and field upgradeable VRAM modules, available in 2, 4 or
8 Mbytes, can be added to a maximum of 16 Mbytes. See appendix B for
jumper positions when adding VRAM display memory.
To achieve a high data transmission bandwidth to the display section, 4
channels of 8 bit data (16 bit data on the 16 Bit Oculus-F/64) are implemented.
3.3.6 PROGRAM AND OVERLAY MEMORY
Oculus-F/64 products accommodate up to 4 Mbytes of graphic and text overlay
memory. TMS34020 GSP program code is stored in on-board DRAM
memory, expandable to a maximum of 32 megabytes. GSP memory can also
be used to store and process image data. TMS320C40 DSP program code is
stored in the DRAM frame buffer and can be expanded to a maximum of 32
Mbytes.
3.3.7 CORECO'S-F/64 BUS
Six channels of 8 bit data form the Coreco's-F/64 Bus. Available only with the
optional DSP, these channels support an 20 Mbyte/sec data transfer rate for
interfacing to compatable products.
Page 3-8 The OCULUS-F/64 User's Manual

3.4 OUTPUT
VGA Feature
Connector
16 Bit to 8 Bit
Display Level
Controller
From VRAM Frame Buffer
From GSP
32 Bits
8 Bits
VGA
LUT
Video
LUT
Overlay
LUT
3.4.1 DISPLAY LEVEL CONTROLLER
VGA /
Overlay
Keyer
Video
Output
MUX
The Display Level Controller is implement only on Oculus-F/64's with the 16
Bit data option. Any 8 bit portion of the 16 bit frame buffer video can be
selected as the input to the Video Output LUT.
3.4. 2 VIDEO OUTPUT LUT
The high bandwidth data channels from the Display Memory forms the input to
the Video Output Look-Up Table. The video LUT is a set of three 256-by-8
tables, providing a RGB output for the monochrome frame buffer data. This
provides for user programmed pseudo color display data for image
enhancement. The driver default loads the video LUT with linear ramps for
unaltered monochrome output video.
3.4.3 OVERLAY FRAME BUFFER AND LUT
The Overlay Frame Buffer is a 7 bit data buffer typically used for static
graphics such as text annotation. Camera images can not be directly acquired
in the overlay buffer but image data can be transferred to it by the application.
The output of the Overlay feeds a dedicated RGB Look-Up Table providing
color attributes applied to the overlay video.
3.4.4 VGA PASS THROUGH, LUT, AND KEYER
For single monitor applications, a dedicated RGB VGA LUT is implemented
for storing a copy of the VGA board's color palette. The VGA LUT is updated
automatically whenever a DOS or Windows application changes the VGA
board palette. Standard VGA, super VGA, and 8514 type boards are
supported.
Coreco Inc., The OCULUS-F/64 Block Diagram Page 3-9
R
G
B

The VGA Keyer manages the keying of frame buffer video into the VGA pass
through video. The keying color is selected via software.
3.4.5 OUTPUT MUX
The Output Mux performs the multiplexing of the various display sources and
pass through video if in one monitor mode. The combined RGB output then
drives the digital-to-analog converter for output to VGA, Super VGA, or
RS170 display monitors.
Note that when pass through video is used, the VGA monitor is driven by the
computer's VGA board. Thus the Oculus F/64 video output format must match
the computer's VGA resolution and refresh rate for proper operation.
Page 3-10 The OCULUS-F/64 User's Manual

• • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • •
CHAPTER 4
• • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • •
• • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • •
OCULUS-F/64 Development Toolkits
• • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • •
• • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • •
This chapter covers: ■ info

Page 4-2 The OCULUS-F/64 User's Manual

4.1 INFO
4.5 COMPUTER PLATFORMS AND OPERATING
SYSTEMS:
COMPILERS:
COOL DOS based Imaging Applications require:
AT class or later computers & DOS 3.0 or later.
COOL Windows based Imaging Applications require:
386 class or later computers & Windows 3.1 or later.
COOL Applications
require:
ODX Applications
require:
Microsoft Visual C++ (Version 1.0 or later)
and Borland C++ (Version 3.1 or later)
compilers are supported (large memory
model).
Microsoft C (Version 7.0 or later), Turbo C
(Version 2.0 and later), Borland C (Version
3.0 and later).
Coreco Inc., The OCULUS-F/64 Development Toolkits Page 4-3

Page 4-4 The OCULUS-F/64 User's Manual

• • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • •
APPENDIX A
• • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • •
• • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • •
OCULUS-F/64 SPECIFICATIONS
• • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • •
• • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • •
This chapter covers: ■ Oculus-F/64 Configurations
■ Acquisition
■ Synchronization
■ Camera Inputs
■ Processing
■ Memory
■ Display
■ Environmental Conditions

Page 5-2 The OCULUS-F/64 User's Manual

A.1 OCULUS-F/64 CONFIGURATIONS
Oculus F/64 Acquisition, processing and display with 8 bit frame buffer
Oculus F/64-DSP Acquisition, processing, display with 8 bit frame buffer and
high performance DSP
Oculus F/64-DSP16 High performance imaging board with DSP and 16 bit
frame buffer
A.2 ACQUISITION
Digitization rate (no IP-Engine
operations)
Digitization rate (with IP-Engine
operations)
F/64 F/64-DSP F/64-DSP16
40 MHz 40 MHz 40 Mhz (8 or
16 bit data)
20 MHz 40 MHz 20 Mhz (16
bit data)
Digitization accuracy 8 bits 8 bits 10 bits
Digital input 8 bits 8 bits 12 bits
Input look-up tables 32 x 256
entry
Maximum acquisition resolution 4k x 4k
w/ optional
memory
A.3 SYNCHRONIZATION
Applies to all Oculus-F/64 Products
32 x 256
entry
32 x 256,
8 x 1024
2 x 4096
4k x 4k 4k x 4k
Pixel clock range 510 kHz to 40 MHz, increments of about 10 kHz
Pixel clock jitter 1/6th pixel worst case
Input signals Hsync, Vsync, trigger, pixel clock, control
Output signals Hsync, Vsync, trigger, pixel clock, control
Coreco Inc., Apendix A OCULUS-F/64 Specifications Page 5-3

A.4 CAMERA INPUTS
A.5 PROCESSING
Four analog video inputs are provided. Three are 75 ohm single ended video
inputs and the fourth can be single ended or differential input.
A connector provides a general purpose TTL digital video interface. An
optional RS-422 converter board can be added to this added to interface RS-
422 output digital cameras.
F/64 F/64-DSP F/64-DSP16
Control processor TMS34020 TMS34020 TMS34020
Image processor TMS34020 TMS320C40 TMS320C40
Arithmetic processor IP-Engine IP-Engine IP-Engine
Statistical processor Histogram Processor with 24 bit results
A.6 MEMORY
F/64 F/64-DSP F/64-DSP16
VRAM frame buffer (standard) 1 Mbyte 2 Mbytes 4 Mbytes
DRAM frame buffer (standard) ◆ 1 Mbyte 4 Mbytes
GSP program memory 1 Mbyte standard, expandable to 32 Mbytes
Overlay memory (standard) ◆ ◆ ◆
Maximum VRAM memory
expansion
Maximum DRAM memory
expansion
16 Mbytes 16 Mbytes 16 Mbytes
◆ 32 Mbytes 32 Mbytes
Overlay memory expansion 4 Mbytes 4 Mbytes 4 Mbytes
Page 5-4 The OCULUS-F/64 User's Manual

A.7 DISPLAY
RESOLUTION TYPE VERTICAL
FREQUENCY
(Hz)
HORIZONTAL
FREQUENCY
(Khz)
PIXEL
CLOCK
(Mhz)
ASPECT
RATIO
SCANNING
TYPE
512 x 484 NTSC 30 Hz 15.734 10.133 5:4 int.
640 x 484 NTSC 30 Hz 15.734 12.270 1:1 int.
512 x 576 PAL 25 15.625 10.000 5:4 int.
768 x 576 PAL 25 15.625 14.750 1:1 int.
512 x 480 VGA 60 31.5 20.000 5:4 non-int.
512 x 480 VGA 72 37.9 24.786 5:4 non-int.
640 x 480 VGA 60 31.48 25.175 1:1 non-int.
640 x 480 VGA 72 37.88 31.200 1:1 non-int.
720 x 400 TEXT 70 31.47 27.600 non-int
800 x 600 SVGA 56 35.2 36.000 1:1 non-int.
800 x 600 SVGA 60 37.9 40.000 1:1 non-int.
800 x 600 SVGA 70 44.0 48.600 1:1 non-int.
800 x 600 SVGA 72 48.1 50.000 1:1 non-int
1024 x 768 8514 86 35.6 44.900 1:1 int.
1024 x 768 SVGA 60 48.4 65.000 1:1 non-int.
1024 x 768 SVGA 70 56.5 75.000 1:1 non-int.
1024 x 768 SVGA 72 57.9 78.000 1:1 non-int.
1280 x 1024 SVGA 87 48.9 77.300 1:1 int
1280 x 1024 SVGA 60 63.7 110.000 1:1 non-int.
1280 x 1024 SVGA 70 74 135.000 1:1 non-int.
1600 x 1200 SVGA 60 76 170.00 1:1 non-int.
Coreco Inc., Apendix A OCULUS-F/64 Specifications Page 5-5

A.8 ENVIRONMENTAL CONDITIONS
Temperature range 0 - 70 Celsius
Humidity 90% non-condensing
FCC Class A
Typical Power Consumption.
Voltage Without DSP With DSP
(Volts) Current
(Amp.)
Power (Watts) Current
(Amp.)
Power
(Watts)
+ 5 3 15 4 20
+12 tbd tbd tbd tbd
- 12 tbd tbd tbd tbd
- 5 tbd tbd tbd tbd
Total ??? tbd tbd tbd
Page 5-6 The OCULUS-F/64 User's Manual

• • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • •
APPENDIX B
• • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • •
• • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • •
OCULUS-F/64 Configuration Switches
• • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • •
• • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • •
This chapter covers: ■ I/O Base Address Selection
■ Interrupt Channel Selection
■ Configuration Jumpers
■ Physical Location

Page 6-2 The OCULUS-F/64 User's Manual

B.1 I/O BASE ADDRESS SELECTION
The I/O Base Address is set by dipswitch SW1-1 to SW1-3 as shown in the
figure below.
ON
1 2 3 4 5 6 7 8
ON ON
Bit Set to 1 Bit Set to 0
I/O Base Address Select
I/O Base Address Select
I/O Base Address Select
The following page shows switch positions for various IO base addresses.
Please verify that the factory default IO address or your chosen IO address is
not in use by other optional devices installed in your computer.
Coreco Inc., Appendix B OCULUS-F/64 Configuration Switches Page 6-3

1 2 3 4 5 6 7 8
1 2 3 4 5 6 7 8
1 2 3 4 5 6 7 8
1 2 3 4 5 6 7 8
1 2 3 4 5 6 7 8
1 2 3 4 5 6 7 8
B.2 INTERRUPT CHANNEL SELECTION
IO-Address = 2D0 hex
IO-Address = 2C0 hex
IO-Address = 2B0 hex
IO-Address = 2A0 hex
IO-Address = 290 hex
IO-Address = 280 hex
Normally, interrupt channels are not used. With certain applications utilizing
custom firmware, the use of an interrupt channel might be required. In this
case, the interrupt channel selected must not be in use by any other device
installed in your computer.
The Interrupt Channel is selected via SW1-4 to SW1-8 as shown below.
Page 6-4 The OCULUS-F/64 User's Manual
ON
ON
ON
ON
ON
ON

ON
1 2 3 4 5 6 7 8
ON ON
Interrupt Channel
NOT Selected
B.3 CONFIGURATION JUMPERS
GSP PROGRAM MEMORY SIZE SELECTION
B3
B3
Interrupt Channel 15 Select
Interrupt Channel 14 Select
Interrupt Channel 12 Select
Interrupt Channel 11 Select
Interrupt Channel 10 Select
Interrupt Channel
Selected
GSP Program memory size: 1Mb (256k x 32)
GSP Program memory size: 4Mb, 16Mb, or 32Mb
1 Mbyte is the factory default GSP DRAM memory that is installed. If
additional DRAM modules are required, then jumper B3 must be moved as
shown above. Refer to the last page of this appendix for the physical location
of B3.
Coreco Inc., Appendix B OCULUS-F/64 Configuration Switches Page 6-5

J10 - LATTICE FPGA DECODE PROGRAMMING
J10
The jumper J10 is installed only for field programming of the FPGA. It is not
required for normal board operation.
B.4 PHYSICAL LOCATION
J10
SW1
B3
Location of B3, J10 and SW1.
• • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • •
Page 6-6 The OCULUS-F/64 User's Manual

APPENDIX C
• • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • •
• • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • •
OCULUS-F/64 Connectors
• • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • •
• • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • •
This chapter covers: ■ Analog Video Input Connector
■ Analog Video Output Connector
■ TTL Digital Video Interface
Connector
■ VGA Pass-through Connector
■ Connector Locations
Page 7-2 The OCULUS-F/64 User's Manual

Coreco Inc., OCULUS-F/64 Index Page 7-3

C.1 Analog Video Input Connector
Pin No. Description ( DB2 )
1 Analog Video Input 3
2 Differential Analog Video Input [-]
3 Analog Video Input 2
4 Differential Analog Video Input [+]
5 Analog Video Input 1
6 Active Low Composite Sync Input (analog or TTL)
7 Analog Video Input 4
8 Active Low Vertical Sync Output (TTL) in master mode
9 Active Low Horizonal Sync or Composite Sync Output (TTL) in
master mode
DB9 Case All Ground Shields
1 2 3 4 5
6 7 8 9
Male DB-9 connector (DB2) as viewed facing the mounting bracket of the
board, from the rear of the computer.
Page 7-4 The OCULUS-F/64 User's Manual

C.2 Analog Video Output Connector
Pin No. Description ( DB1 )
1 Analog Red
2 Analog Green
3 Analog Blue
4, 9, 12, 15 No Connection
6 Red Ground
7 Green Ground
8 Blue Ground
5, 10, 11 Digital Ground
13 Horizontal Display Sync.
14 Vertical Display Sync.
5 4 3 2 1
10 9 8 7 6
15 14 13 12 11
Female DB-15 connector (DB1) as viewed facing the mounting bracket of the
board, from the rear of the computer.
Coreco Inc., OCULUS-F/64 Index Page 7-5

C.3 TTL Digital Video Interface Connector
Pin No. Name Description ( J17 )
34 GROUND Digital Ground
1, 2, 3, 4, 5, 6, 7, 8,
9, 10, 11, 12
13, 14, 15, 16, 17,
18, 19, 20
TTLVIN [ 0:11 ] TTL Digital Video Inputs
GIO [ 0:7 ] General I/O bits
22 VINSEL3 Video Input Select bit 3
31 -ECS Active low Composite Sync Input (TTL)
28 -EHS Active low Horizontal Sync Input (TTL)
27 -EVS Active low Vertical Sync Input (TTL)
26 -EBLK Active low Vertical Blanking Input (TTL)
30 -EODD Active low ODD Field Input (TTL)
29 OUTCLK TTL Output Clock (to video source)
21 ECLK Active high Clock Input (TTL)
25 -ECLK Active low Clock Input (TTL)
23 -AVS Active low Vertical Sync Output (TTL) in master mode
24 -AHS Active low Horizonal Sync or Composite Sync Output
(TTL) in master mode
32 EXTRG Active high External Trigger Input
33 reserved reserved
34 - Pin Male Header Connector ( J17 ) view when facing the board.
2 4 ... 32 34
1 3 ... 31 33
Page 7-6 The OCULUS-F/64 User's Manual

C.4 VGA Pass-Through Connector
Pin No. Name Description ( J18 )
1, 3, 5, 13, 15, 17,
19, 21, 23
GROUND Digital Ground
2, 4, 6, 8, 10, 12, 14, 16 VD[0:7] VGA Data (color index, Hi-color, True color)
7, 9, 11, 25 NC No Connection
18 VGADOT VGA Pixel Clock
20 VGABLK VGA Blanking
22 VGAHS VGA Horizontal Sync
24 VGAVS VGA Vertical Sync
26 - Pin Male Header Connector ( J18 ) view when facing the board.
25 23 ... 3 1
26 24 ... 4 2
Coreco Inc., OCULUS-F/64 Index Page 7-7

C.5 Connector Locations
J18
DB1 DB2
J17
Page 7-8 The OCULUS-F/64 User's Manual

Coreco Inc., OCULUS-F/64 Index Page 7-9

• • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • •
INDEX
• • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • •
• • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • •
OCULUS-F/64 User's Manual
• • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • •
• • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • •

Page 8-2 The OCULUS-F/64 User's Manual

A
Accesories. See Part Numbers
Acquisition Sync Source, 2-10
Acquisition Video Format, 2-12
adapter modules, 3-6
ALU, 3-3
Analog Input Cables, 2-5
Analog Input Selector, 3-4
analog to digital converter, 3-4
Anti-alaising Filter, 3-4
architecture-software. See OKS
B
base address, 2-4, 2-9
BLOCK DIAGRAM-chapter, 3-1
Bus Interface, 2-16
Bus Interface Mapping. See Bus Interface
C
Cables. See Part Numbers
camera input, 2-12
Camera Slave, 2-10
CAMERA.EXE. See Custom Camera
camera-supported, 1-3
CCIR Monitor, 2-6
communications error, 2-9
compatibility-Oculus-F/64, 1-3
Compilers, 1-6, 4-3
CONFIG.EXE, 2-6
Configuration Switches, 6-1
Connectors, 7-2
Coreco’s-F/64 Bus, 3-8
Custom Camera, 2-16
Custom Display, 2-16
D
Development Toolkits, 4-1
Device Driver, 2-6
digital input, 3-6
Digital Input Cables, 2-5
Digital Interface port, 3-5
display leveling, 3-3
Display Video Format, 2-13
DISPLAY.EXE. See Custom Display
display-supported, 1-6
DRAM, 3-3
DSP, 3-8
DSP16, 1-6
Coreco Inc., OCULUS-F/64 Index Page 8-3

E
EIA-422 interface, 3-6
F
F/64Pro, 1-6
F64.BAT, 2-22
F64PRO Installation, 2-23
GSP, 3-7
G
H
Hardware Configuration, 2-6
histogram, 3-3
histogram processor, 3-7
ILUT, 3-6
input coupling, 3-4
input look-up table. See ILUT
installation-hardware, 2-4
IP-Engine, 3-7
I
L
local buses, 3-8
Look-Up-Tables, 3-3
M
memory, 1-5
Memory Format, 2-14
Memory Map Address. See Bus Interface
Memory Map Bus Width. See Bus Interface
O
Oculus Kernel System. See OKS
Oculus-F/64 Part Numbers. See Part Numbers
OCULUS-F/64 SPECIFICATIONS, 5-1
ODF64.DLL, 2-22
ODF64STP.EXE, 2-6
ODx, 1-6
ODX.INI, 2-7
ODXPATH, 2-7
Page 8-4 The OCULUS-F/64 User's Manual

OKS, 1-7
OLUT, 3-9
Output Cables, 2-5
Output Mux, 3-10
Output Sync Enable, 2-15
Overlay Frame Buffer, 3-9
overlay memory, 3-8
P
Part Numbers, 1-8
pixel clock, 1-3, 3-4
pixel jitter, 3-4
pixel size, 2-16
processing, 1-4
program memory, 3-8
range and offset, 3-4
resolution, 1-4
RGB monitor, 2-6
RS170 Monitor, 2-6
R
S
signal conditioning, 1-4
single monitor mode, 2-13
single screen operation, 2-5
software-tools, 1-6
SW1, 2-4
TMS320C40, 3-3
TMS34020, 3-3
T
V
Variable Acquisition Parameters, 3-6
versions-Oculus-F/64, 3-3
VGA feature connector, 2-5
VGA keying color, 2-21
VGA monitor, 2-6
VGA Pass Through, LUT, and Keyer, 3-9
VGA PassThrough Setup, 2-20
VGA terminator, 2-5
video output LUT. See OLUT
VRAM, 3-3
Coreco Inc., OCULUS-F/64 Index Page 8-5