MVS6000 - MIMOT · MVS6000 System Level Manual/1.0/Dec-2001 MVS6000 System Level Manual

MVS6000 System Level Manual/1.0/Dec-2001

MVS6000System Level Manual

This document con

information of ICOS

Copyright ICOS Vis

All rights reserved.

No part of this d

reproduced in any

from ICOS Vision S

The information co

been carefully chec

reliable and cons

describes. Howev

for inaccuracies.

assume any liabilit

use of any product

Vision Systems res

to any product an

effort to improve pe

T

VGA and SVGAInternational BusinDOS, MS-WindowsWindows 2000 Microsoft Corporacopyright of PKWANetwork AssociateAdobe Systems Iregistered trademCorporation. RoxCreator and DirectShockwave is copVirtuoso is register

COPYRIGHT

tains proprietary and confidential

Vision Systems N. V.

ion Systems N. V.

ocument may be translated or

form without written permission

ystems N. V.

DISCLAIMER

ntained within this document has

ked and is believed to be entirely

istent with the product that it

er, no responsibility is assumed

Nor does ICOS Vision Systems

y arising out of the application or

or circuit described herein. ICOS

erves the right to make changes

d product documentation in an

rformance, reliability or design.

RADEMARKS

are registered trademarks ofess Machines Corporation. MS-, Windows 95, Windows NT andare registered trademarks of

tion. PKZIP and PKUNZIP areRE Inc. VirusScan is copyright ofs. Acrobat is a trademark of

ncorporated. InstallShield is aark of InstallShield Software

io, the Roxio logo and Easy CD CD are trademarks of Roxio, Inc.yright of AtomShockwave Corp.ed trademark of Eonics.

CONTACT US

If you have any remarks or suggestions

concerning this manual, please do not

hesitate to contact us.

[email protected]

ORDERING INFORMATION

Specify order number MA6000 if you want

additional copies of this manual.

MVS6000 System Level Manual/1.0/Dec-2001 i

MVS6000

Table of ContentsPreface ..............................................................................................................................................v

1 Introduction.............................................................................................................................. 1-1

2 Hardware ................................................................................................................................. 2-12.1 MVS600x Board................................................................................................................. 2-2

2.1.1 Main Hardware Blocks ................................................................................................ 2-22.1.2 General Layout of the MVS6000 Family ..................................................................... 2-32.1.3 Power Consumption.................................................................................................... 2-42.1.4 Minimum PC Requirements ........................................................................................ 2-42.1.5 Communication ........................................................................................................... 2-52.1.6 Flat Cable Connectors ................................................................................................ 2-52.1.7 Block Diagram MVS600x ............................................................................................ 2-8

2.2 Racks................................................................................................................................. 2-92.3 Camera Connections and Cables.................................................................................... 2-11

2.3.1 Connectors and Cables ............................................................................................ 2-12

MVS6000

ii MVS6000 System Level Manual/1.0/Dec-2001

2.3.1.1 Connectors........................................................................................................ 2-122.3.1.2 Breakout Boxes and Cables.............................................................................. 2-13

2.3.2 Supported Cameras.................................................................................................. 2-16

3 Software .................................................................................................................................. 3-13.1 Software............................................................................................................................. 3-2

3.1.1 Windows 2000 ............................................................................................................ 3-23.1.2 Virtuoso....................................................................................................................... 3-23.1.3 PLX PCI ...................................................................................................................... 3-2

3.2 Installation of the Software ................................................................................................ 3-33.2.1 Install the Plug & Play Driver ...................................................................................... 3-33.2.2 Install the MVS6000 Hardware Files........................................................................... 3-93.2.3 Install the MVS Software........................................................................................... 3-12

3.2.3.1 Install MVS6000 Software when No MVS6000 Folder Exists ........................... 3-133.2.3.2 Upgrade the MVS6000 Software ..................................................................... 3-15

3.2.4 Install the MMI Software ........................................................................................... 3-193.3 System Configuration ...................................................................................................... 3-20

3.3.1 CNF_edit - General: .................................................................................................. 3-203.3.2 CNF_edit - MVS <n>:................................................................................................ 3-21

3.3.2.1 Slots .................................................................................................................. 3-223.3.2.2 Camera Type for a Specific Connector ............................................................. 3-223.3.2.3 Camera Numbering........................................................................................... 3-24

3.3.3 CNF_edit - Camera <n> of MVS<m>:....................................................................... 3-253.4 MMI.................................................................................................................................. 3-26

4 Image Acquisition .................................................................................................................... 4-14.1 Memory Storage ................................................................................................................ 4-24.2 Timing Kits ......................................................................................................................... 4-24.3 Camera Selection .............................................................................................................. 4-24.4 Illumination Settings........................................................................................................... 4-3

4.4.1 Rough Illumination Settings ........................................................................................ 4-34.4.2 Fine Illumination Settings............................................................................................ 4-3

5 Display & Communication........................................................................................................ 5-15.1 Communication Management............................................................................................ 5-25.2 Virtuoso, Pipe Communication .......................................................................................... 5-35.3 Display/Graphics Communication...................................................................................... 5-3

Preliminary Table of Contents

MVS6000 System Level Manual/1.0/Dec-2001 iii

5.4 Message Communication .................................................................................................. 5-4

6 Tools and Troubleshooting ...................................................................................................... 6-16.1 PCITerm ............................................................................................................................ 6-2

6.1.1 To launch PCITerm..................................................................................................... 6-36.1.2 To Capture a Text File ................................................................................................ 6-56.1.3 To Send a Text File..................................................................................................... 6-66.1.4 Error Messages........................................................................................................... 6-7

6.2 Exchanging Boards............................................................................................................ 6-86.3 Language Setting in Windows2000 ................................................................................... 6-96.4 Reinstalling with an Empty Hard Disk.............................................................................. 6-106.5 Troubleshooting............................................................................................................... 6-11

6.5.1 Windows2000 Problems ........................................................................................... 6-116.5.2 MVS600x Problems .................................................................................................. 6-13

6.5.2.1 Boot problems................................................................................................... 6-136.5.2.2 MMI Problems................................................................................................... 6-14

A. Appendix..................................................................................................................................A-1A.1 SlotMapping.reg.................................................................................................................A-2A.2 Incompatible Communication Messages ...........................................................................A-3

Index ............................................................................................................................................. I-1

MVS6000

iv MVS6000 System Level Manual/1.0/Dec-2001

MVS6000 System Level Manual/1.0/Dec-2001 v

MVS6000

PrefaceThis manual describes the MVS600x boards, their installation and their use.

� Chapter 1, Introduction, briefly gives the advantages of this new vision board.

� Chapter 2, Hardware, gives an overview of the board layout.

� Chapter 3, Software, explains how to update the software.

� Chapter 4, Image Acquisition, explains the differences in the image acquisition between the

MVS3x0 boards and the MVS600x boards.

� Chapter 5, Display and Communication, describes how the communication of messages and

images with graphics is managed.

� Chapter 6, Tools and Troubleshooting, introduces new tools and gives information for

troubleshooting.

� the appendix contains some extra information.

A basic knowledge of Windows 2000 is assumed.

MVS6000

vi MVS6000 System Level Manual/1.0/Dec-2001


MVS6000

chapternumber

1 Introduction

Introduction

The MVS600x boards belong to the new generation of ICOS

MVS3x0 series (that is the MVS340 or the MVS360), provi

standstill time, accuracy, …) and use the Plug & Play co

parameters are stored in the registry and application-specific se

anymore.

These boards should no longer be booted prior to starting u

launched inside the MMI. Graphics and video are sent over the

hardware or extra monitor is needed.

The “SEEPROM” parameters, which were stored on board for the

on the PC and read by the MVS600x board at startup. This way

correct after boards are exchanged.

1-1

vision boards. They replace the

de higher performances (speed,

ncept for hardware installation:

ttings are not stored on the board

p the MMI. The board can be

PCI to the VGA card. No extra

MVS3x0, are now stored in a file

, the settings will automatically be

MVS6000

1-2 MVS6000 System Level Manual/1.0/Dec-2001


MVS6000

2 Hardware

Hardware

This chapter provides more information about the hardware connections.

2-1

of the MVS600x board and its

MVS6000


2.1 MVS600x Board

The MVS6000 family consists of three boards: the MVS6000 board, the MVS6001 board and the

MVS6002 board.

The differences between the three board types are the camera connections:

� The MVS6000 board supports two analog cameras

� the MVS6001 board supports one analog and one digital camera

� the MVS6002 board supports two digital camera

For detailed information (see page 2-12).

In the following two sections, you get an overview of the main hardware blocks and you see the

layout of the MVS6000 board and the MVS6002 board.

2.1.1 Main Hardware Blocks

� 2 DSP chips: TI320C6202 - 250Mhz

� SDRAM: 32 MB, used for application software, models, images,…

� Xilinx programmable components used, for example, for the timing generators of the cameras

� PLX driver for PCI communication (which gives the board read/write access to the hard disk)

� 3 SEEPROMS: for board-specific initial settings only

� 2 independent parallel video input channels

� PCI or RS232 communication

� Digital camera support as an option

Hardware

2.1.2 General Layout of the MVS6000 Family

This section shows the layout of the MVS6000 and the MVS6002 board.

Each board has different camera connectors, see page 2-12.

MVS6000

confo

c

inputFIFOs

flash/trigger LI2 LI1 PIO test
Activity LED
MVS6

nectorsr analogameras

12 analog inputs

DSP activity LEDs

DSPDSP

IOCTRL

CTRL CTRL

32 MB

PCICTRL

cameraCTRL

input 2 LED

2

000 System Level

connector forcamera module

connector forcamera module

input 1 LED

Manual/1.0/Dec-2001 2-3

MVS6000

2-4

MVS6002

2.1.3

The po

� +5V

� +12

� -12

2.1.4

� min

� min

� min

� vide

� � �

� for

digital input


Power Consumption

wer consumption is lying within the PCI specifications:

: max. 4A

V: 200mA + power of all connected cameras

V: 150mA.

Minimum PC Requirements

imum Pentium III 600Mhz

imum 133Mhz front side bus

imum 64MB SDRAM

o graphics card:

minimum AGP*4resolution 1280*1024 with 64K colors should be supported8 MB display memory: avoid using UMA (sharing SDRAM as display memory)

each board one full length PCI slot must be available.

Hardware

MVS6000 System Level Manual/1.0/Dec-2001 2-5

2.1.5 Communication

� PCI pipe communication

� RS232 communication:

The following baud rates are supported: 110, 300, 600, 1200, 2400, 4800, 9600, 14400,19200, 38400, 57600, 115200.

Note: 1. ICOS provides the WinCommDll.dll for the communication (see page 5-2). Thisdriver is available for WinNT4.0 and Win2000 (and can also be used for the ISAand HS3L communication on MVS3xx and MVS100/200).

2. When no serial communication is used, the baud rate should be set to 0. Thiswill improve the performance of the system.

2.1.6 Flat Cable Connectors

The connectors at the topside of the board are labeled:

Each connector is explained in detail on the next page.

C1 C2 C3 C4 C5 C6 C7 C8 C9 C10C11

xilinx

plx

SW2

SW1

JF4

JF3

MVS6000


C1: flash trigger connector

Pin assignments: Pin # Signal name Function Direction

8-141234567

GNDFLASH1TRRDY1TRIN1FLASH2TRRDY2TRIN2NC

GroundFlash channel 1Trigger ready channel 1Trigger input channel 1Flash channel 2Trigger ready channel 2Trigger input channel 2Not Connected

-outputoutputinputoutputoutputinput-

Note: A Flash trigger board, using SMB snap-on connectors, is available for easy connection.

1 2 3 4 5 6 7

8 9 10 11 12 13 14

Hardware


C2 & C3: LI1 and LI2

These connectors are serial connections to the ICOS light interface (LI) boards.

C4: PIO

This connector supports four groups of 8 bit PIO that can be programmed as an input or output.

The MVS software does not yet support this.

C5: JTag

This connector is used for in circuit emulation, programming primary software for testing in

production environment or for boundary scan to check the processors.

C6 & C7: MCBSp2 and MCBSp1

This is a multi-channel buffered serial port: it is a standard serial port for connecting multiple

TMS320C6202 DSP processors. The MVS software does not yet support this port.

C8 & C9: Duart B and Duart A

These ports are used for serial communication with the board and can be set in menu mode,

message mode or host mode.

Pin assignments: Pin # Signal name Function

235891,4,6,7,10

RXDTXDGNDCTSRTSNC

Receive dataTransmit dataGroundClear to sendRequest to sendNot connected

C10: Can Bus

This is not supported.

C11:

Connector used for diagnostics purposes in production (at ICOS).

1 2 3 4 5

8 9 10 7 6

MVS6000

2-8M

VS6000 System Level M

anual/1.0/Dec-2001

2.1.7 Block D

iagram M

VS600x

PCI_V2.2

Input LUT

1kByteSEEPROM

CTRLI/O - INT

2 x Med Resor

McBSP

McBSP

32

ANALOG

32

INT INT

10 bit40 MHz

A/D conv.

32

SyncFIFO

32

XBIEMI

DSPTMS320C6202250 MHz

PCI master I.F.

1kByteTMS320C6202

32 MByteSDRAM

250 MHz

(125 MHz)(2 banks)

TRANSXBOOT FEPROM

16

40 MHz10 bitA/D conv.

32 32

INT

Camera module( Second slot )

INT

INT

INT

SyncFIFO

32

32

Digital output

DSP

CTRL

CON 1

CON 2

1 x HR

8

32

SEEPROM

Transfer

SC28L92A1BTQFP44

33 MHz

XBIEMI

JTAG

McBSP

McBSP

16

1 x HR

1 x Med Res

1 x Med Res

2 x Med Resor

PLX9054

JTAG

JTAG emulatorCROSS-BAR

PIO : 32 I/O

Expansion bus module

RS-232 RS-232

Mux

Mux

Input LUT4x4Kx9

4x4Kx9

McBSP1 McBSP2

32

32

8

DUART

CameraCon

CameraCTRL

Flash/Trigger

Light InterfaceSerial

10

10

512 KByte

( IEEE-1394, Flash EPROM, ... )

Hardware


2.2 Racks

Two types of racks are planned: standard and small.

standard rack (16 slots) small rack (7 slots)4 PCI slots (� max 4 MVS) 3 PCI slots (� max 3 MVS)2 PICMG slots (for a PC board) 1 PICMG slot8 ISA slots (for LIs, PIO, Atos, power) 3 ISA slotsPentium III 600E Pentium III 600E128 MB memory 128 MB memoryH: 178 mm - W: 448/483 mm - D: 460 mm H: 177 mm - W: 268/318 mm - D: 425 mm

The PC board is a Microbus MAT915 with Ethernet and SVGA on board.

A 17-inch monitor is advised. Only one monitor is used, as well on the CI as for SL products.

The rack dimensions are the same as the MVS3x0-racks, but the position of the mounting holes is

different on the small rack.

The back plane is different from that of the MVS3x0-racks.

The distinction between the different MVS6000s is based on their positions in the rack (slot 1, slot

2, ... see below). They have no address anymore (any more jumpers).

Configuration of the Standard Rack

front side

CPU

pow

er4 PCI slots 8 ISA slots

MVS

6000

(slo

t 1)

ATO

S

PIO

pow

er b

rack

et

light

inte

rface

light

inte

rface

MVS

6000

(slo

t 2)

MVS

6000

(slo

t 3)

MVS

6000

(slo

t 4)

2 PICMG slots

MVS6000


Configuration of the Small Rack

front side

CPU

pow

er

3 PCI slots 3 ISA slots

MVS

6000

(slo

t 1)

PIO

light

inte

rface

MVS

6000

(slo

t 2)

MVS

6000

(slo

t 3)

1 PICMG slot

Tip: Slot 1 is always the closest to the PC board.

Hardware


2.3 Camera Connections and Cables

Camera timing kits are programmable on the board. For each board two different timing kits can

be programmed.

Up to four standard resolution (SR) cameras or two high resolution (HR) cameras (ADIMEC), can

be connected to the MVS6000 board.

A combination of two SR cameras with one HR camera is also possible. In this configuration, the

same types of SR cameras must be connected to connector 1 and the HR camera must be

connected to connector 2.

Following figure summarizes the allowed combinations for the MVS6000 board:

Connector 1

Connector 2

SR sametypeSR

SR sametypeSR

HR

HR

SR sametypeSR

HR

Note: Cameras may be missing in these configurations.

To connect:

� two SR cameras to one of the MVS connectors of the MVS600 board, a breakout box must beused.

� four SR cameras to a MVS6000 board, two symmetrical breakout boxes must be used.

An example of two symmetrical breakout boxes (see also page 2-13).

to connector 1of MVS6000

camera 2

camera 1

camera 4

camera 3 to connector 2of MVS6000

camera numbering onMVS6000 board (seealso page 3-23).

MVS6000

2-12

2.3.1 Connectors and Cables

2.3.1.1 Connectors

� MVS6000: the bracket has two connectors, each for either two standard resolution cameras orone high resolution camera.

� MVS6001: the bracket has two connectors, one for the IVC-1000 camera and one for eithertwo standard resolution cameras or one high resolution camera.

� MVS6002: the bracket has two connectors for the IVC-1000 camera.

15 p

connector 1

2connector

for
connector
IVC-1000

paper clip reset

in connector of

12345678

15 p2MVS6001

(mounted in a rack)
MVS6000in connectors
MVS6000 System Level

the MVS6000: Pin # Signal

1514131211109

123456789101112131415

Video Cam 1HD Cam 1VD TTL cam 1Video 2 GNDGNDClock signal ADIMEHD Cam 212 V DC .75 A maxVideo Cam 1 GNDGNDVideo Cam 2Shutter Control CamShutter Control CamClock signal ADIMEVD TTL cam 2

MVS600

Manual/1.0/Dec-2001

C MX12P +

out

1 2

C MX12P -

Hardware


2.3.1.2 Breakout Boxes and Cables

Breakout Boxes

To connect two or more SR cameras to an MVS board, a breakout box must be used. A breakout

box has a SubD15 connector In and two or three Hirose connectors Out.

For the Hirose connector of the STxx Sony cameras and the Teli camera, a new connector

standard (EIAJ standard) has been introduced in which Pin 11 is no longer used as 12V input but

as trigger input. See the following table for more details.

Hirose connector Pin Nr Old Pin Layout New EIAJ standard

1 GND GND

2 + 12 V DC + 12 V DC

3 Video Out (GND) Video Out (GND)

4 Video Out (signal) Video Out (signal)

5 HD in (GND) HD in (GND)

6 HD in (Signal) HD in (Signal)

7 VD in (Signal) VD in (Signal)

8 TRIG in (GND) GND

9 Trig In (Signal) /

10 GND WEN output (Signal)

11 + 12 V DC Trig In (Signal)

12 VD in (GND) VD in (GND)

Warning: New cables must be used for the connector with the new EIAJ standard.The problem is that the connectors are physically “compatible”, but if you use oldcables with the new connectors or the new cables with the old connectors, either thecamera or the MVS board will be seriously damaged.To avoid confusion:� The cameras with the new EIAJ standard connector will get a blue label.� The breakout boxes compatible with the old camera connectors are gray.

The breakout boxes with the new EIAJ standard Hirose connectors have a bluelabel or a blue housing.An example of a blue label for a breakout box:

ICOS Vision SystemsMVS 966R

Product of BELGIUM

REV : 0/0/0New EIAJ Standard

ICOS Vision SystemsMVS 966L

Product of BELGIUM

REV : 0/0/0New EIAJ Standard

� The cables will get a blue label.

MVS6000


An overview of the available breakout boxes:

MVS number connector In connectors out Connectors out: pin layout color

MVS962 SubD15 3 x Hirose Old pin layout gray

MVS963 SubD15 2 x Hirose old pin layout gray

MVS964 SubD15 2 x Hirose new EIAJ pin layout blue

MVS966 SubD15 3 x Hirose new EIAJ pin layout blue

Cables

there are three types of cables to connect the camera with the MVS6000 board:

� SR cables to connect with the standard Hirose connector

� SR cables to connect with the new EIAJ standard Hirose connector (blue label)

� HR cables

Note: For the SR cameras, the same cables are used as for connecting to the MVS3x0.For the HR cameras (ADIMEC), other cables are used than for connecting to the MVS3x0.

The next two tables give an overview of the cables that must be used with and without a videosplitter.

Note: A video splitter transmits the output of the two cameras to the two “twin” MVS boards.

Camera connections without video splitter:

camera type

connection

HR camera SR cameraold standard

SR cameraEIAJ standard

blue label

camera to MVS3x0

SL:

CI:

CW4448 (2m)CW4449 (5m)CW4450 (10m)CW4332 (3m)

camera to MVS6000

SL:

CI:

CW4703 (2m)CW4704 (5m)CW4705 (10m)CW4642 (3m)

SL:

CI:

CW4473 (2m)CW4474 (5m)CW4475 (10m)CW4603 (5.5m)

CW4711 (2m)CW4712 (5m)CW4713 (10m)

camera to breakout box - - -

CW4430 (2m)CW4431 (5m)CW4432 (10m)

Hardware


Camera connections with video splitter:

camera type

connection

HR camera SR cameraold standard

SR cameraEIAJ standard

blue label

camera to video splitter

SL:CI:

CW4559 (0.3m)CW4332 (3m) - - - - - -

video splitter to MVS3x0

SL:

CI::

CW4560 (2m)CW4595 (5m)CW4596 (10m)CW4616 (3m)

- - - - - -

video splitter to MVS6000

SL:

CI:

CW4707 (2m)CW4682 (5m)CW4709 (10m)CW4708 (3m)

- - - - - -

When using the acceleration kit on a 3D STEREO system, the connections are as follows:

MVS6000


2.3.2 Supported Cameras

With MVS Software 24.0.0:

Only analog cameras are supported with MVS software 24.0.0:

XC75CE_2 � interlaced� no restart reset� frame integration� resolution 752X574� ID is 1

XC75CE_6 � interlaced� restart reset� frame integration� resolution 752X574� ID is 2

XC75CE_7 � interlaced� restart reset� field integration� resolution 752X574� ID is 3

ST50CE_6 � interlaced� restart reset� frame integration� resolution 752X574� ID is 23

ST50CE_7 � interlaced� restart reset� field integration� resolution 752X574� ID is 24

Sony


Hardware


ST30CE_7 � Interlaced� restart reset� field integration� resolution 752X574� ID is 31


ST70CE_7 � interlaced� restart reset� field integration� resolution 752X574� ID is 28

XC55E_5 � progressive scan,� restart reset� field integration� resolution640X492� ID is 21

XC8500M_5 � progressive scan,� restart reset� field integration� resolution 752X576� ID is 14

Teli CS8531_5 � progressive scan,� restart reset� field integration� resolution 640X492� ID is 25

ADIMEC 40M50PC � progressive scan,� restart reset� field integration� resolution 10240X1024� ID is 2

MVS6000


With MVS Software 24.1.0:

The IVC-1000 camera is supported with the MVS software 24.1.0.

This digital camera can only be used on the MVS6001 and MVS6002 boards.

IVC-1000 � 30 fps at full resolution� camera link� 1004x1004 active pixels (1000X1000 guaranteed uniformity)


MVS6000

3 Software

Software

This chapter gives an overview of the software you need to

explains how to install it.

3-1

run the MVS600x systems and

MVS6000


3.1 Software

To run the MVS600x system you need the following software:

� Windows 2000 and PLX PCI

� Virtuoso

� MVS hardware and software files

� CNF_edit and MMI version 5.0 or higher.

3.1.1 Windows 2000

MVS6000-based systems are designed to run with Windows NT-based technology. The official

version is Windows 2000, which allows:

� scalable fonts

� FAT32, NTFS

� parallel booting of the MVS6000 boards

� multiple languages (optionally).

3.1.2 Virtuoso

Virtuoso is the operating system of the MVS6000 boards.

It is used to open the communication pipes towards the boards.

Note: This software is automatically installed in the MVS6000 folder when the MVS hardwarefiles will be installed (see page 3-3).

3.1.3 PLX PCI

On the MVS6000 board, a PLX chip takes care of the PCI communication. The PLX driver will

give all the other drivers (communication driver, display driver,…) access to the board.

Note: The install shield of the MVS Software will automatically install The PLX driver (see page 3-12).

Software


3.2 Installation of the Software

The following software is already installed on systems that leave the factory:

� Windows 2000, with the correct Ethernet, video and PLX PCI drivers.� MVS6000 Hardware files and utilities.

You only have to install or upgrade the MVS software and the MMI software, as explained in on

page 3-12 and 3-19.

Note: The installation and the upgrade of MVS and MMI software are always with InstallShield.No support is given for configurations obtained by copying files.

Tip: To be able to install the board you need administrator rights on the system.

3.2.1 Install the Plug & Play Driver

When starting from a clean Windows 2000 installation, Windows will warn you that new hardware

has been found if an MVS6000 has been inserted in one of the PCI slots.

The Found New Hardware Wizard helps you to install the driver, as is explained here:

MVS6000


1 In the Found New Hardware Wizard, click Next to continue the installation.

The next page of the wizard opens:

2. Select the radio button Display a list of the known drivers for this device so that… and click

Next.

The next page of the wizard, showing the list of hardware types, opens:

Software


3. Select Other devices in the hardware types list and click Next.

The next page of the wizard opens.

4. Click Have Disk….

The Install From Disk dialog box opens.

MVS6000


5. Click Browse… to open the Locate File dialog box. Here you can select the folder that

contains the mvs6000.inf file.

Note: The folder that contains the mvs6000.inf file is stored on the ICOS Installation CD thatis delivered with your system. The folder is “\ Drivers \ Icos MVS6000 for Win2000”.

6. Select the mvs6000.inf file and click Open.

The Locate File dialog box closes. The folder containing the mvs6000. inf file is added to the

drop-down list in the Install From Disk dialog box.

Software


7. Click OK to close the Install From Disk dialog box and to return to the wizard.

8. Select ICOS MVS6000 Board and click Next.

The next page of the wizard opens.

MVS6000


9. Click Next to continue.

10. Click Finish to close the wizard.

11. If you have more than one board, repeat this procedure for all other boards.

Software


3.2.2 Install the MVS6000 Hardware Files

The Setup files for hardware installation can be found on the ICOS Installation CD that is delivered

with your system. These files are stored in the folder \Software\MVS6000 Hardware Setup\Disk1.

Tip: When you install the MVS6000 hardware files, virtuoso is installed automatically in theMVS6000 folder on your hard disk.

1. Run Setup.exe from the folder \Software\MVS6000 Hardware Setup\Disk1 on the ICOS

Installation CD.

The MVS6000 hardware Setup wizard starts:

After a few seconds the Welcome page opens:

MVS6000


2. Click Next to continue the wizard.

3. Use the Browse button to select the folder with the slotmapping.reg file in the Choose Folder

dialog box.

Notes: 1. The slotmapping.reg file is stored in the \Software\MVS6000 Hardware Setupfolder on the ICOS Installation CD

2. When the warning “There is no disk in the drive. Please insert a disk into drive A”appears, click Cancel to open the Choose Folder dialog box.

3 The slotMapping.reg file contains the bus number and the PCI slot ID. Thesenumbers are reserved by the motherboard and can change from the onemanufacturer to the other. You can find this information in the manual of themotherboard or on the screen when starting up the system. Once you pluggedin an MVS board the PC will show (depending on the BIOS settings) on one ofthe first screens (after showing the PC hardware settings) the bus number andthe PCI ID of every used slot. The file slotMapping.reg for the Microbus MAT915PC is described in the Appendix (see page A-2).If necessary, copy this file to a floppy disk and edit the fields: PCIBusNumberand PCISlotNumber.


Windows opens the Registry Editor message box, an example is shown here.

Software


5. Click Yes to continue the installation.

Windows informs you that the registry is updated. An example is shown here.

6. Click OK to continue.

7. Select the radio button Yes, I want to restart my computer now.

8. Click Finish to complete the installation and to restart your computer.

MVS6000


3.2.3 Install the MVS Software

The MVS software 24.0.0 will be installed in the C:\Mvs6000 folder.

Recommendation: All the software is automatically installed in this folder and you are stronglyadvised not to alter its contents.

The setup for MVS software is available on:

� the ICOS Installation CD in the folder \Software\MVS6000 SW install 24.0.0� the ICOS ftp server.

This is true for official releases as well as for special versions.

The next two sections explain the steps in the installation:

� when no MVS6000 folder exists (see next page)� or when a MVS6000 folder already exists and you want to do an upgrade (see page 3-15).

Software


3.2.3.1 Install MVS6000 Software when No MVS6000 Folder Exists

1. Run Setup.exe from the folder \Software\MVS6000 SW install 24.0.0\Disk 1 on the ICOS

Installation CD.

The InstallShield Wizard starts.



The installation starts.

The InstallationShields always installs the software for four slots, even if these boards are not

present. This means that when you add a board to the system you do not have to reinstall the

software.

MVS6000


The software of slot 1 is installed first, followed by slot 2, slot 3 and slot 4:

…

The system starts updating the NLI files and creates folders and Icons on the desktop.

When the installation is done, the following page is shown:

3. Click Finish to complete the installation.

Software


3.2.3.2 Upgrade the MVS6000 Software

1. Run Setup.exe from the first floppy or from the folder \Software\MVS6000 SW install

24.0.0\Disk 1 on the ICOS Installation CD.

The InstallShield Wizard starts.


MVS6000



The wizard asks you to backup or to overwrite the existing MVS6000 folder.

3. Select the option you want (backup/overwrite)

4. Click Next.

The Wizard asks you if you want the default or the existing system configuration.

5. Select the radio button Use existing system config (recommended).

Software


6. Click Next.

� When you selected the option Overwrite existing MVS6000 folder in step 3, the installation

procedure continues with the message Setup is checking for the necessary disk space in

step 8.

� When you selected the option Backup existing MVS6000 folder, the wizard continues:

7. Enter a backup folder.

8. Click Next.

Note: When the backup folder already exists you get the message that the folder alreadyexists. If you click Yes, the folder will be overwritten, if you click No, the backup folderpage of the wizard is re-displayed and you can specify another location.

The following messages are displayed:

MVS6000


The installation starts.

The InstallationShields always installs the software for four slots, even if these boards are not

present. This means that when you add a board to the system you do not have to reinstall the

software.

The software of slot 1 is installed first, followed by slot 2, slot 3 and slot 4:

…

The system starts updating the NLI files and creates folders and Icons on the desktop.

When the installation is done, the following page is shown:

Software


9. Click Finish to complete the installation.

3.2.4 Install the MMI Software

This installation is the same as for MVS3x0-based systems.

Notes: 1. The installation files are available on the ICOS Installation CD.2. When you upgrade the MMI Software, the files in the C:\Icos folder are automatically

converted to the correct version.

MVS6000


3.3 System Configuration

After you updated the MMI software, you must configure the system.

Camera settings and SIO port settings are saved in a file called Param_file.txt. Each slot has his

own Param_file.txt file. The Param_file.txt file for a specific slot is stored in the slot folder for that

specific slot (for example: C:\Mvs6000\Slot1).

Warning: Do not try to edit this file manually.

To configure the system, use the configuration file CNF_edit.exe. The most important steps in

CNF_edit will be explained here.

3.3.1 CNF_edit - General:

System_

In the System group box, the MVS100/200 series is not supported anymore, you can select either

the MVS3x0 series or the MVS600x series.

#MVS_

Here you specify the number of MVS 600x boards in your rack.

Software


Hardware_

By default, you run CNF_edit with hardware check, that is, it checks whether the selected

configuration is compatible with the hardware that is installed in your system, that is:

� you can not specify more boards than present in your rack

� you can not configure a board for an empty slot.

Applications_

In MMI 5.0, the Lead Frame Check, Dambar Check and Mark Absence/Presence applications are

not available on MVS6000-based systems.

3.3.2 CNF_edit - MVS <n>:

Note: If you specified n board in the #MVS group box of the CNF_edit - General dialog box (seepage 3-20) the system shows n CNF_edit - MVS<n> dialog boxes.

In this dialog box, you specify the relation between the physical boards and the MVS1, MVS2,

MVS3 ... numbering used by CNF_edit.

For each CNF_edit - MVS<n> dialog box you have to specify:

� the slot of the board� the type of cameras connected to each connector.

MVS6000

3-22

3.3.2.1 Slots

By default, MVS1 is supposed to be in the first non-empty slot 1, but you can select another slot

(see page 3-21). The slots that are empty or the slots from which a board is already defined are

disabled. For the next board(s), the default is slot 2. Select the correct slot and enter the camera

definitions.

3.3.2.2 Camera Type for a Specific Connector

For each connector on the MVS6000 board, you have two lists. In the upper list you can select

between:

� <None>� ADIMEC 40M50PC (progressive scan) � HR camera� Sony XC75CE_2:� Sony XC75CE_6� Sony XC75CE_7� Sony XC55CE_5� Sony ST50CE_6� Sony ST50CE_7� Sony ST30CE_6� Sony ST30_CE_7� Sony ST70CE_6� Sony ST70_CE_7� Sony XC8500M_5� Teli CS8531_5

s
� SR camera

Software


When specifying the cameras for the lower list, you must take into account the following

restrictions (see also page 2-11):

� If you select a HR camera

(Adimec40M50PC) in the upper list, you

cannot select another camera in the lower

list.

� If you have selected a SR camera in the

upper list, you can only select the same

camera type, or <None> in the lower list.

MVS6000


3.3.2.3 Camera Numbering

The numbering of the cameras on the MVS6000 board is as follows:

� the SR cameras are camera 1, camera 2, camera 3 and camera 4:

cam 1 cam 2 cam 3 cam 4connector 1 X Xconnector 2 X X

Connector 1:

� if there is only one camera, it is camera 1� if two cameras are connected (by using a breakout box), camera 1 is connected above

camera 2 (see page 2-11).Note: this is the opposite of the MVS3x0 board where camera 2 was connected

above camera 1.

Connector 2:

� if there is only one camera, it is camera 3� if two cameras are connected (by using a breakout box), camera 3 is connected above

camera 4 (see page 2-11)Note: this is the opposite of the MVS3x0 board where camera 4 was connected

above camera 3.

� the HR cameras are camera 1 and camera 3:

cam 1 cam 3connector 1 Xconnector 2 X

Software


3.3.3 CNF_edit - Camera <n> of MVS<m>:

This dialog box is similar to the corresponding one for MVS3x0-based systems.

Note: The text below the camera definition gives the camera resolution.

MVS6000


3.4 MMI

On the MVS600x, the MMI behaves differently regarding:

� the illumination settings (see page 4-3)

� the booting of the boards (see below).

Pool Parameters

A new section is added in pool.txt, namely the [MVS6000Boot] section:

[MVS6000Boot]BootOnStartup=1TimeoutOnPollingForSyncFile=30

BootOnStartup is set to 1, which means that the MVS6000 boards are booted at MMI startup (and

are reset when MMI exits).

TimeoutOnPollingForSyncFile is the time the MMI waits for the MVS6000 boards to boot. In case

other software is running on the same PC, you may increase this parameter.


MVS6000

4 Image Acquisition

Image Acquisition

This chapter explains the image acquisition on the MVS600x

acquire two images in parallel.

The following changes in the image acquisition compared to the M

� memory storage� timing kits� camera selection� illumination settings.

4-1

board. The MVS600x is able to

VS3x0 board are explained:

MVS6000


4.1 Memory Storage

Data fields are not used anymore on the MVS600x board. The images are not stored at a

predefined location, but in a dynamically allocated memory. This way, no space is lost.

The images are identified by means of their “tag”. The algorithms use these tags instead of the

data field number to specify the image to be processed or shown.

4.2 Timing Kits

On the MVS600x board, there is only one timing kit per camera/mode. The integration time is set

by software and linked to the illumination time. This is different compared to the MVS3x0 board.

4.3 Camera Selection

The CNF_edit program (see pages 3-21 and 3-25) is the only place where you can specify the

camera configuration (type and mode) in the ICOS software. This means that there can be no

incompatible settings.

Note: ADIMEC cameras also has to be configured with their own m12pc32 program.

Image Acquisition


4.4 Illumination Settings

The illumination settings for the MVS600x board, are also set in the MMI software.

4.4.1 Rough Illumination Settings

These settings have the same meaning for the MVS600x board as for the MVS3x0 board: they

represent the amplification of the analog signal from the camera by the MVS board.

4.4.2 Fine Illumination Settings

The fine illumination settings depend on four values that are selected in the CNF_edit program.

For the MVS600x board, the names are the same as for the MVS3x0 board but the illumination is

set to a percentage of the maximal illumination duration.

names (in CNF_edit)continuous 100 %long 40 %medium 10 %short 1 line

The above selection can be interpreted as the “resolution” of the illumination. The fine settings of

the MMI correspond to a percentage of this time.

Example (MX12 Progressive scan camera):

CNF_edit settings fine illumination in MMI resulting integration/illuminationContinuous 100% 40ms

10% 4msLong 100% 16ms

20% 3.2msMedium 100% 4ms

1% 40µsec

MVS6000


With the MVS3x0 board, the fine setting had no influence on the standstill time, so it was always

advised to set the rough settings as low as possible and to use the fine settings to increase the

illumination.

With the MVS6000 board and with progressive scan cameras, the fine illumination settingshave a direct influence on the standstill time and a trade-off must be made between the speedand the introduction of noise.

Note: The examples below do not allow for the overhead of the MMI protocol communication.They suppose there is enough light for a short illumination time.

Example 1: 3D STEREO

MVS3x0:

integration

standstill time = int1 + transfer

2D camera

3D cameraintegration

transfer

transfer

MVS6000:

integration

standstill time = int1 + int2

2D camera


transfer

transfer

Image Acquisition


Example 2: 3D STEREO and Between Balls Inspection

MVS3x0:

integration

integration

standstill time = int1 + 2*transfer

2D camera

2D camera


transfer

transfer

transfer

MVS6000:

integration

integration

standstill time = int1 + 1*transfer

2D camera

2D camera


transfer

transfer

transfer

MVS6000



MVS6000

5 Display & Communication

Display & Commu

This chapter describes how the communication of message

managed.

The display of video images and their graphics are now a PC

implies that the video images are always merged with the Win

“external monitor”.

Tip: On the MVS600x board it is possible to capture screenMVS graphics by using the PrintScrn key.

5-1

nication

s and images with graphics is

task (not a MVS600x task). This

dows menus. There is no more

s that include video images and

MVS6000


5.1 Communication Management

Three DLLs are in charge of managing the communication of messages and images with graphics:

Dll TaskDisplay.dll PC screen(zooming, graphics ...) already present with the

MVS3x0

Wincomm.dll message communication already present with theMVS3x0 since MMI4.10

Displaytask.dll display/graphics communication new with the MVS6000

The communication with the MVS600x boards is through the Virtuoso operating system. Each

MVS600x board has its own instance of it. Separate communication channels are used for:

� display/graphics communication

� message communication

� optionally, PCITerm for menu mode (see page 6-2)

Display & Communication


5.2 Virtuoso, Pipe Communication

All communication with MVS600x passes through the Virtuoso Operating System. Each board has

its own instance of Virtuoso, which is initialized by means of a batch file that is automatically

activated when starting up the MMI.

Each communication channel consists of two pipes: one pipe to send and another to receive data.

Separate pipes are opened for:

� display/graphics communication

� message communication.

Extra pipes can be opened to run for example PCITerm, the terminal emulation program using

PCI-communication, which will be used as a replacement for Hyperterminal.

5.3 Display/Graphics Communication

At initialization, MMI defines the video-window layout on the monitor by using the Display.dll.

The Displaytask.dll takes care of the link between the video windows and the actual video image

coming from the MVS boards. This link must also be defined by the MMI at initialization. For

example: window1 displays the video image coming from tag1 of MVS6000 in slot 1.

After startup, the Displaytask.dll is continuously checking with each MVS6000 board whether

images are available for display. When this is the case, the Displaytask.dll gets the image and

the corresponding graphics and sends it to the Display.dll who displays them on the monitor. MMI

is not involved in this action.

MVS6000


5.4 Message Communication

Standard message communication between interface and the MVS-boards passes via the

WinComm.dll. Here as well pipes are opened in order to communicate with Virtuoso.

Note: Incompatible messages are described in the Appendix on page A-3.


MVS6000

6 Tools and Troubleshooting

Tools and Trouble

This chapter describes the following topics:

� the PCITerm terminal emulator for menu mode (see page 6-2

� exchanging boards (see page 6-8)

� language settings in Windows 2000 (see 6-9)

� reinstalling from scratch on a new hard disk (see 6-10)

� possible problems (see 6-11).

6-1

shooting

)

MVS6000


6.1 PCITerm

This program is used to communicate with the board in menu mode or message mode. It is an

ICOS terminal emulation program that replaces the HyperTerminal program of Windows. There is

no need anymore for a serial cable.

PCITerm is installed together with the MVS software. The installation program creates shortcuts in

the Icos Tools folder on your desktop, like, pciterm MVS1_pci4.

� MVS<n> represents the board with which you want to communicate, <n> is the slot number� pci<m> represents a pipe, that is, a communication channel.

Notes: 1. Pipes 1 and 2 are reserved for communication with the MMI, so you can select pipe3 or 4 for PCITerm.

2. When the board is reset, you have to restart PCI Term.

Tools and Troubleshooting


6.1.1 To launch PCITerm

1. Make sure the board is booted, that is, MMI is running.

2. Double-click the shortcut in the Icos Tools folder on your desktop (for example “PciTerm

MVS1_pci4”).

A terminal window opens, telling you the pipes are opened (one pipe is open in each direction,

see page 5-3).

After a few seconds, the system shows the menu (see next page):

MVS6000


Notes: 1. The menu mode works in the same way as for the MVS3x0 boards.2. You can launch multiple instances of PCITerm to communicate simultaneously with

all boards.



6.1.2 To Capture a Text File

When you are in PCITerm, you can capture all the text given on the screen in a text file.

1. Press the F2 button.

The Capture Text dialog box opens. Here you can specify the name and the destination of the

text file.

2. Select the folder and give a file name for the .txt file.

3. Click Save to capture the text in a text file.

MVS6000


4. As indicated in the title bar of the terminal window, you can stop the capturing by pressing the

F2 button again.

6.1.3 To Send a Text File

With PCITerm, you can also send a text file to the MVS board.

1. Press the F3 button to send a text file.

The Send Text File dialog box opens.

2. Select the text file you want to send.

3. Click Open to send it to the MVS board.



6.1.4 Error Messages

If you try to restart PCITerm for the same board and with the same pipe when it is already active,

the system tells you the pipes are unavailable:

Note: You get the same message if you try to use PCITerm with pipes 1 or 2, because thesepipes are reserved for the communication with the MMI.

MVS6000


6.2 Exchanging Boards

Exchanging boards is very easy with MVS600x: you may move the boards to other slots, add a

board, take a board out of the rack and put another one into it. When the system is restarted, the

hardware wizard automatically detects where MVS600x boards are present and adapts its

configuration accordingly.

Most parameters are stored in a file on the PC and read by the MVS600x board at startup. This

way, the settings will automatically be correct after boards are exchanged.

Note: On the MVS3x0 boards, these parameters where stored in a SEEPROM.

The MVS keys are still stored on each board, in a SEEPROM, as previously. This means that you

must set these keys correctly to allow the software to run.

Recommendation: KeyUtil is adapted, use version 3.0 or higher.



6.3 Language Setting in Windows2000

Two versions of Windows 2000 can be used:

� English only

� Multilingual (for Japanese customers).

If you have the multilingual version, go to the Regional Options in the Control panel to:

� install other languages

� select the language for the menus and dialog boxes

Tip: You can find more detailed information on how to install and select languages in the Helpof Windows 2000. Select Start > Help and search for the keyword “language”.The help topics you need are:

� Installing > Install additional languages� Changing for dialogs and menus.

MVS6000


6.4 Reinstalling with an Empty Hard Disk

To reinstall the software on an empty hard disk, the following installation CD-ROMs are available:

� Windows 2000

� VirusScan

� Easy - CD creator

� ICOS Installation CD

More information on the reinstallation procedure can be found on the ICOS Installation CD.



6.5 Troubleshooting

This section lists some problems and their solution related to Windows2000 and to MVS600x.

6.5.1 Windows2000 Problems

The Typed Characters do not Correspond with the Keyboard Keys

With Windows 2000, you can select the keyboard layout (that is, the correspondence between the

keys you press and the characters that appear on the screen) per application. Normally, there is

only one keyboard connected to the system and you do not need to change it, but it could happen

somebody has unwillingly modified the keyboard layout for a program.

How to select the correct keyboard layout, or how to uninstall a keyboard layout you do not use is

explained in the following sections.

How to select the correct keyboard layout

In the bottom right corner, you have a blue square with your keyboard settings:

1. Click on it, to get the list of installed keyboards:

2. Select the keyboard that must be used for the current application.

Note: This selection will also be used the next time you open this application.

MVS6000


How to uninstall the keyboard layout you do not use:

You can also uninstall the keyboard layout you do not use:

1. Select Start > Settings > Control Panel.

2. Select the Keyboard icon

The Keyboard Properties dialog box opens.

3. Select the Input Locales tab:

4. Select the keyboard layout you do not use and click Remove.

5. Click OK to apply these settings and to close the dialog box.



6.5.2 MVS600x Problems

This section lists some boot problems and MMI problems with their solution.

6.5.2.1 Boot problems

In case of boot problems, the MMI will display an error message that tells you what goes wrong.

For example:

Note: Check the Dos Window at startup to see if the MVS600x boards are found.

Tip: In case you need ICOS support, run the minimal backup tool in the C:\Icos\Tools folder andsend these files for troubleshooting to the ICOS engineer.

MVS6000


6.5.2.2 MMI Problems

Error message “MVS: system error” at startup

When a camera is not connected, the MMI displays the following error message at startup, while it

is trying to take input:

Video display seems zoomed

Only two resolutions are supported for the Windows display settings:

� 1280*1024� 800*600.

If you use other settings, the MMI will start without problems, but the video image will be displayed

incorrectly:



Very Slow Inspection Times

When the inspection times are abnormally slow, check if Virtchst.exe is in realtime priority.

When the boards are manually booted virtchst.exe is probably not in realtime priority.

How can you check and change this?

1. When MMI is running, press CTRL+ALT+DEL to open Windows Security.

2. Click Task Manager… to open the Windows Task Manager.

3. Select the Processes tab.

4. Choose View> Select Columns… in the menu.

The Select Columns dialog box opens.

5. Switch on the Base Priority check box.

6. Click OK.

The Base priority column is added to the list on the Processes tab.

7. Look for Virtchst.exe in the list and check if you find Realtime in the Base Priority column.

MVS6000


8. If the Base Priority is Normal, click with the right mouse button on Normal.

The following menu pops-up.

9. Instead of Normal, switch on Realtime in the Set Priority.

10. Close the Task Manager.

This will speed-up the inspection time.

Slow Mouse Movement

This is a known bug, which will be solved in the coming release. Meanwhile use another zoom

factor.

Hang-up of MMI

Make sure that the correct mode is selected for the ADIMEC MX12 camera, otherwise the MMI will

hang.

MVS6000 System Level Manual/1.0/Dec-2001 A-1

MVS6000

A. Appendix

Appendix

This appendix contains:

� the SlotMapping.reg file

� an overview of the incompatible communication messages

MVS6000

A-2 MVS6000 System Level Manual/1.0/Dec-2001

A.1 SlotMapping.reg

The file slotMapping.reg for the Microbus MAT915 PC looks as follows:

REGEDIT4

[HKEY_LOCAL_MACHINE\SOFTWARE\Icos Vision Systems\MVS6000]

[HKEY_LOCAL_MACHINE\SOFTWARE\Icos Vision Systems\MVS6000\General]"PCType"="Mat915"

[HKEY_LOCAL_MACHINE\SOFTWARE\Icos Vision Systems\MVS6000\Slot 1]"PCIBusNumber"=dword:00000000"PCISlotNumber"=dword:00000014




Appendix


A.2 Incompatible Communication Messages

Messages Not Supported Anymore

All graphics and display message are not supported anymore. They will be replaced by a *.dll

running on the PC.

Graphics00D0 Set image pixel00D1 Set 1 pixel00D2 Draw line00D3 Draw text00D4 Define full color00D5 Define overlay color00D7 Load user color00D9 Draw + &2box00A3 Make drawing00A5 Remove drawing00A6 Cursor manipulation00A7 Text manipulation00A8 Redraw

Display00A0 Teach window00A1 Delete window00A2 Change window00D6 Select RGB/BW00DA Set destination00B4 reply point00B6 reply line00B7 reply cross00B8 reply box00B9 reply matrix00BA reply profile00BB reply polyline00BC reply ellipse00BD reply ellipse arc00BE reply text00BF reply wnd fill000A get buffered graphics03A0 teach window

Memory00FF get model memory size00DB set flash programming channel

MVS6000


Debug00C3 get error log007F set write functions0010 upload error log entry00F0 time trace settings

Info0300 get configuration parameters

Communication00AC input transparent communication

Boot03F8 Boot MVS340 from Application SW0BF8 Boot MVS340 from Boot SW0BF5 clear flash0BF6 load flash0BF7 set flash start address0BFD load&program flash disc

Input0003 autogain calibration

Messages with Incompatibilities

General remarksSIP profile is not supported anymore and is mapped on the RIP profile typeNIP profile is mapped to a new profile type called SNIP.

Info00DD set setup parameters: most cases not supported anymore, still supportedare: 15, 16, 17, 11500DE get setup parameters: most cases not supported anymore, still supportedare: 1, 15, 16009E get package info: p11-p14 reply will be 0 (camera size, display size)

Processing00B0 1D data processingcase 2, cp9, value 3 and 4 minimum profile and maximum profile not supported inphase1, will return error00B2 2D data processingcase 2, cp10, value 1 and 2 minimum mosaic and maximum mosaic not supported inphase1, will return error.0096 get mosaicp17, value 1 and 2 minimum mosaic and maximum mosaic not supported in phase1,will return error

Appendix


New messages

Debug06c3 MVS6000 errorlog dump

06C3p1[px][p1[px]]

p0 | 2 bytes | message identifier for MVS p1 | 2 bytes | message length p2 | 1 byte | parameter modifier: | | 00 = no change of parameters .......................................... : CASE 0 | | 01 = full dump .................................................………..... : CASE 1 | | 02 = change field separator .................................…......... : CASE 2 | | 03 = dump in "error.log" .....................................…......... : CASE 3 | | 04 = dump in <filename> ...................................….......... : CASE 4 | | 05 = clear file ....................................................………... : CASE 5

| CASE 00 | No change | ------- | --------- px | 0 bytes | No further info. | | The default dump corresponds to an incremental dump of the error log to the virtuoso consolewindow

| CASE 01 | full dump | ------- | --------- px | 0 bytes | No further info. | | The total error info is dumped i.s.o. the changes in respect to the previous dump.

| CASE 02 | field separator | ------- | --------------- px | 1 byte | ASCII character to put between the individual fields of an error record | | following fields are dumped: | | ticket - type - nr of arguments - line number - file name - argument 1 type - argument 1 value - ...

| CASE 03 | dump in "error.log" | ------- | ------------------- px | 0 bytes | No further info.

| CASE 04 | dump in <filename> | ------- | ------------------- px | 1 byte | number of characters in <filename> | n bytes | <filename>

| CASE 05 | clear file | ------- | ---------- px | 0 bytes | No further info. | | overwriting the file i.s.o. appending. | |

The error log is an ASCII text file comprising records which are separated by a<CR> and chronologically ordered from oldest to newest. Each record starts with5 parameters followed by a variable number of arguments, each argument consistsof two elements. All fields are terminated by the field separator (default is'|').

MVS6000


record 1: field 1: param 1: error ticket ASCII string identifies the process which logged the event one of tree possible ticket formats are used: 01 or 02 : node id (only during startup) 000n00tt : n=node, tt=task uuvvaa.. : real process ticket, uu=user interface count vv=application request count aa=algo count field 2: param 1: error type number: 0 = info 1 = warning 2 = error 3 = interupt error 4 = start 5 = stop 6 = input_info 7 = input_warning 8 = input_error 9 = check/trace point field 3: param 1: nr of arguments number field 4: param 1: line number number source code identification field 5: param 1: file name ASCII string source code identification field 6: argument 1: type character format specifier: b = unsigned 8 field 7: argument 1: value w = unsigned 16 W = signed 16 d = unsigned 32 D = signed 32 s = string o = string (operator) p = pointer (written in hex) | . . . <CR> record 2: . .

MVS6000 System Level Manual/1.0/Dec-2001 I-1

MVS6000

IndexA

Acceleration kitconnections, 2-15

BBoot

at MMI startup, 3-26troubleshooting, 6-13

Breakout boxcamera connection, 2-11, 2-13

CCable connectors

hardware, 2-5Cables

camera connection, 2-14Camera

connections and cables, 2-11

image acquisition, 4-2numbering, 2-11, 3-24supported types, 2-16

CNF_edit, 3-20Communication

display/graphics, 5-3dll, 5-2hardware, 2-5incompatible messages, A-3message, 5-4pipes, 5-3Virtuoso, 5-3

DDisplay

communication, 5-3Display.dll

communication, 5-2, 5-3Displaytask.dll

communication, 5-2, 5-3

MVS6000

I-2 MVS6000 System Level Manual/1.0/Dec-2001

Dllcommunication, 5-2

EEIAJ standard

Hirose connector, 2-13Exchanging boards, 6-8

FFine illumniation settings

image acquisition, 4-3Flash trigger board

hardware, 2-6

GGraphics

communication, 5-3

HHardware

cable connectors, 2-5camera connections, 2-11cameras, 2-16communication, 2-5flash trigger board, 2-6minimum PC requirements, 2-4MVS6000, 2-3overview, 2-2power consumption, 2-4racks, 2-9

Hirose connector, 2-13

IIllumination settings

image acquisition, 4-3Image acquisition, 4-1

camera selection, 4-2illumination settings, 4-3memory storage, 4-2timing kits, 4-2

InstallationMMI software, 3-19MVS software, 3-12MVS6000 hardware files, 3-9plug & play driver, 3-3

reinstall from scratch, 6-10

LLanguage settings

Windows2000, 6-9

MMemory storage

image acquisition, 4-2Message

communication, 5-4Minimum PC requirements, 2-4MMI

install software, 3-19parameters, 3-26troubleshooting, 6-14

MVS software, 3-12MVS6000

hardware files, 3-9layout, 2-3

MVS6002layout, 2-4

NNumbering

cameras, 2-11, 3-24

PParam_file.txt, 3-20PCITerm

capture text file, 6-5error messages, 6-7launch, 6-3send text file, 6-6tools, 6-2

Pipescommunication, 5-3

Plug & play driver, 3-3PLX PCI

software, 3-2Power consumption

hardware, 2-4

Index

MVS6000 System Level Manual/1.0/Dec-2001 I-3

RRacks

16 slots, 2-97 slots, 2-9

Rough illumination settingimage acquisition, 4-3

SSlot, 2-9, 3-22SlotMapping.reg, 3-10, A-2Software

install MMI, 3-19install the plug & play driver, 3-3MMI, 3-26MVS software, 3-12MVS6000 hardware files, 3-9PLX PCI, 3-2system configuation, 3-20Virtuoso, 3-2Windows-2000, 3-2

System configurationCNF_edit, 3-20Param_file.txt, 3-20

TTiming kits

image acquisition, 4-2Tools

exchanging boards, 6-8language settings, 6-9PCITerm, 6-2reinstall from scratch, 6-10

Troubleshootingboot problems, 6-13MMI problems, 6-14Windows2000 problems, 6-11

VVirtuoso

communication, 5-3software, 3-2

WWinComm.dll

communication, 5-2, 5-4Windows2000

language settings, 6-9software, 3-2troubleshooting, 6-11

MVS6000 - MIMOT · MVS6000 System Level Manual/1.0/Dec-2001 MVS6000 System Level Manual

Documents

Transcript of MVS6000 - MIMOT · MVS6000 System Level Manual/1.0/Dec-2001 MVS6000 System Level Manual