Professional Documents
Culture Documents
MVS6000 Manual
MVS6000 Manual
0/Dec-2001
MVS6000
System Level Manual
COPYRIGHT
DISCLAIMER
TRADEMARKS
technical.writers@icos.be
ORDERING INFORMATION
Table of Contents
Preface ..............................................................................................................................................v
1 Introduction.............................................................................................................................. 1-1
A. Appendix.................................................................................................................................. A-1
A.1 SlotMapping.reg................................................................................................................. A-2
A.2 Incompatible Communication Messages ........................................................................... A-3
Preface
This manual describes the MVS600x boards, their installation and their use.
· Chapter 1, Introduction, briefly gives the advantages of this new vision board.
· 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.
chapter
number
1 Introduction
Introduction
The MVS600x boards belong to the new generation of ICOS vision boards. They replace the
MVS3x0 series (that is the MVS340 or the MVS360), provide higher performances (speed,
standstill time, accuracy, …) and use the Plug & Play concept for hardware installation:
parameters are stored in the registry and application-specific settings are not stored on the board
anymore.
These boards should no longer be booted prior to starting up the MMI. The board can be
launched inside the MMI. Graphics and video are sent over the PCI to the VGA card. No extra
hardware or extra monitor is needed.
The “SEEPROM” parameters, which were stored on board for the MVS3x0, are now 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.
2 Hardware
Hardware
This chapter provides more information about the hardware of the MVS600x board and its
connections.
The differences between the three board types are the camera connections:
· the MVS6001 board supports one analog and one digital camera
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.
· 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)
This section shows the layout of the MVS6000 and the MVS6002 board.
MVS6000
input
FIFOs
CTRL CTRL
connector for
camera module
camera DSP activity LEDs
CTRL
input 1 LED
1 32 MB DSP
connectors 2 analog inputs DSP
for analog
cameras input 2 LED PCI IO
CTRL
CTRL
2
connector for
camera module
MVS6002
digital input
· +5V: max. 4A
· -12V: 150mA.
2.1.5 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). This
driver is available for WinNT4.0 and Win2000 (and can also be used for the ISA
and HS3L communication on MVS3xx and MVS100/200).
2. When no serial communication is used, the baud rate should be set to 0. This
will improve the performance of the system.
C1 C2 C3 C4 C5 C6 C7 C8 C9 C10
C11
SW2
xilinx
JF4
SW1 plx
JF3
Note: A Flash trigger board, using SMB snap-on connectors, is available for easy connection.
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.
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.
These ports are used for serial communication with the board and can be set in menu mode,
message mode or host mode.
C11:
MVS6000
1 x HR
1 x Med Res ANALOG A/D conv. McBSP1 McBSP2 JTAG emulator
10 Mux SyncFIFO 32
or CROSS-
2 x Med Res 10 bit Input LUT
BAR
CON 1 40 MHz 4x4Kx9
32 PCI master I.F. 32
1 x HR
1 x Med Res
or
PLX9054
PCI_V2.2
2 x Med Res A/D conv.
10 SyncFIFO 32 33 MHz
CON 2 Mux
10 bit
Input LUT
40 MHz 4x4Kx9
McBSP JTAG
INT
DSP
32
TMS320C6202 SEEPROM
INT
32 MByte 250 MHz 1kByte
SDRAM 32 32 Transfer
EMI XBI
(2 banks) CTRL
McBSP
(125 MHz)
TRANSX
BOOT FEPROM
512 KByte
16
8 8
INT
PIO : 32 I/O DUART INT
I/O - INT SC28L92A1B
TQFP44
CTRL
32 32
16
Camera SEEPROM
Con 1kByte
Hardware
2.2 Racks
Two types of racks are planned: standard and small.
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 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).
light interface
MVS6000 (slot 4)
MVS6000 (slot 3)
MVS6000 (slot 2)
MVS6000 (slot 1)
ATOS
PIO
CPU
front side
1 PICMG
3 PCI slots slot 3 ISA slots
power
light interface
MVS6000 (slot 3)
MVS6000 (slot 2)
MVS6000 (slot 1)
CPU PIO
front side
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:
SR same SR same
Connector 1 HR
type type
SR SR
SR same
Connector 2 HR HR
type
SR
To connect:
· two SR cameras to one of the MVS connectors of the MVS600 board, a breakout box must be
used.
· four SR cameras to a MVS6000 board, two symmetrical breakout boxes must be used.
camera 1 to connector 1
of MVS6000
camera 2
camera 3
to connector 2
of MVS6000
camera 4
camera numbering on
MVS6000 board (see
also page 3-23).
2.3.1.1 Connectors
· MVS6000: the bracket has two connectors, each for either two standard resolution cameras or
one high resolution camera.
· MVS6001: the bracket has two connectors, one for the IVC-1000 camera and one for either
two standard resolution cameras or one high resolution camera.
· MVS6002: the bracket has two connectors for the IVC-1000 camera.
connector 1
connector
connector 2 for
IVC-1000
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.
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 old
cables with the new connectors or the new cables with the old connectors, either the
camera 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 blue
label or a blue housing.
An example of a blue label for a breakout box:
ICOS Vision Systems ICOS Vision Systems
MVS 966R MVS 966L
REV : 0/0/0 REV : 0/0/0
New EIAJ Standard New EIAJ Standard
Product of BELGIUM Product of BELGIUM
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 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 video
splitter.
Note: A video splitter transmits the output of the two cameras to the two “twin” MVS boards.
When using the acceleration kit on a 3D STEREO system, the connections are as follows:
ST30CE_7 · Interlaced
· restart reset
· field integration
· resolution 752X574
· ID is 31
ST70CE_6 · interlaced
· restart reset
· frame integration
· resolution 752X574
· ID is 27
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
This digital camera can only be used on the MVS6001 and MVS6002 boards.
3 Software
Software
This chapter gives an overview of the software you need to run the MVS600x systems and
explains how to install it.
3.1 Software
To run the MVS600x system you need the following software:
· Virtuoso
MVS6000-based systems are designed to run with Windows NT-based technology. The official
version is Windows 2000, which allows:
· scalable fonts
· FAT32, NTFS
3.1.2 Virtuoso
Note: This software is automatically installed in the MVS6000 folder when the MVS hardware
files will be installed (see page 3-3).
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).
· 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.
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:
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:
3. Select Other devices in the hardware types list and click Next.
The next page of the wizard opens.
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 that
is delivered with your system. The folder is “\ Drivers \ Icos MVS6000 for Win2000”.
7. Click OK to close the Install From Disk dialog box and to return to the wizard.
11. If you have more than one board, repeat this procedure for all other boards.
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 the
MVS6000 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:
3. Use the Browse button to select the folder with the slotmapping.reg file in the Choose Folder
dialog box.
6. Click OK to continue.
Recommendation: All the software is automatically installed in this folder and you are strongly
advised not to alter its contents.
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 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.
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.
4. Click Next.
The Wizard asks you if you want the default or the existing system configuration.
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:
8. Click Next.
Note: When the backup folder already exists you get the message that the folder already
exists. If you click Yes, the folder will be overwritten, if you click No, the backup folder
page of the wizard is re-displayed and you can specify another location.
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.
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.
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).
To configure the system, use the configuration file CNF_edit.exe. The most important steps in
CNF_edit will be explained here.
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.
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
Applications_
In MMI 5.0, the Lead Frame Check, Dambar Check and Mark Absence/Presence applications are
not available on MVS6000-based systems.
Note: If you specified n board in the #MVS group box of the CNF_edit - General dialog box (see
page 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.
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.
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
Þ SR cameras
· Sony ST50CE_7
· Sony ST30CE_6
· Sony ST30_CE_7
· Sony ST70CE_6
· Sony ST70_CE_7
· Sony XC8500M_5
· Teli CS8531_5
When specifying the cameras for the lower list, you must take into account the following
restrictions (see also page 2-11):
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.
cam 1 cam 3
connector 1 X
connector 2 X
This dialog box is similar to the corresponding one for MVS3x0-based systems.
Note: The text below the camera definition gives the camera resolution.
3.4 MMI
On the MVS600x, the MMI behaves differently regarding:
Pool Parameters
[MVS6000Boot]
BootOnStartup=1
TimeoutOnPollingForSyncFile=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.
4 Image Acquisition
Image Acquisition
This chapter explains the image acquisition on the MVS600x board. The MVS600x is able to
acquire two images in parallel.
The following changes in the image acquisition compared to the MVS3x0 board are explained:
· memory storage
· timing kits
· camera selection
· illumination settings.
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.
Note: ADIMEC cameras also has to be configured with their own m12pc32 program.
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.
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.
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.
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 settings
have a direct influence on the standstill time and a trade-off must be made between the speed
and 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:
2D camera
integration
transfer
3D camera
integration
transfer
MVS6000:
2D camera
integration
transfer
3D camera
integration
transfer
MVS3x0:
2D camera
integration
transfer
3D camera
integration
transfer
2D camera
integration
transfer
MVS6000:
2D camera
integration
transfer
3D camera
integration
transfer
2D camera
integration
transfer
The display of video images and their graphics are now a PC task (not a MVS600x task). This
implies that the video images are always merged with the Windows menus. There is no more
“external monitor”.
Tip: On the MVS600x board it is possible to capture screens that include video images and
MVS graphics by using the PrintScrn key.
Dll Task
Display.dll PC screen(zooming, graphics ...) already present with the
MVS3x0
Wincomm.dll message communication already present with the
MVS3x0 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
Each communication channel consists of two pipes: one pipe to send and another to receive data.
· 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.
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.
· the PCITerm terminal emulator for menu mode (see page 6-2 )
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 pipe
3 or 4 for PCITerm.
2. When the board is reset, you have to restart PCI Term.
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):
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.
When you are in PCITerm, you can capture all the text given on the screen in a text file.
2. Select the folder and give a file name for the .txt file.
4. As indicated in the title bar of the terminal window, you can stop the capturing by pressing the
F2 button again.
With PCITerm, you can also send a text file to the MVS board.
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 these
pipes are reserved for the communication with the MMI.
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.
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.
· English only
If you have the multilingual version, go to the Regional Options in the Control panel to:
Tip: You can find more detailed information on how to install and select languages in the Help
of 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.
· 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.
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.
In the bottom right corner, you have a blue square with your keyboard settings:
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.
You can also uninstall the keyboard layout you do not use:
4. Select the keyboard layout you do not use and click Remove.
This section lists some boot problems and MMI problems with their solution.
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 and
send these files for troubleshooting to the ICOS engineer.
When a camera is not connected, the MMI displays the following error message at startup, while it
is trying to take input:
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:
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.
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.
8. If the Base Priority is Normal, click with the right mouse button on Normal.
The following menu pops-up.
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.
A. Appendix
Appendix
This appendix contains:
A.1 SlotMapping.reg
The file slotMapping.reg for the Microbus MAT915 PC looks as follows:
REGEDIT4
All graphics and display message are not supported anymore. They will be replaced by a *.dll
running on the PC.
Graphics
00D0 Set image pixel
00D1 Set 1 pixel
00D2 Draw line
00D3 Draw text
00D4 Define full color
00D5 Define overlay color
00D7 Load user color
00D9 Draw + &2box
00A3 Make drawing
00A5 Remove drawing
00A6 Cursor manipulation
00A7 Text manipulation
00A8 Redraw
Display
00A0 Teach window
00A1 Delete window
00A2 Change window
00D6 Select RGB/BW
00DA Set destination
00B4 reply point
00B6 reply line
00B7 reply cross
00B8 reply box
00B9 reply matrix
00BA reply profile
00BB reply polyline
00BC reply ellipse
00BD reply ellipse arc
00BE reply text
00BF reply wnd fill
000A get buffered graphics
03A0 teach window
Memory
00FF get model memory size
00DB set flash programming channel
Debug
00C3 get error log
007F set write functions
0010 upload error log entry
00F0 time trace settings
Info
0300 get configuration parameters
Communication
00AC input transparent communication
Boot
03F8 Boot MVS340 from Application SW
0BF8 Boot MVS340 from Boot SW
0BF5 clear flash
0BF6 load flash
0BF7 set flash start address
0BFD load&program flash disc
Input
0003 autogain calibration
General remarks
SIP profile is not supported anymore and is mapped on the RIP profile type
NIP profile is mapped to a new profile type called SNIP.
Info
00DD set setup parameters: most cases not supported anymore, still supported
are: 15, 16, 17, 115
00DE get setup parameters: most cases not supported anymore, still supported
are: 1, 15, 16
009E get package info: p11-p14 reply will be 0 (camera size, display size)
Processing
00B0 1D data processing
case 2, cp9, value 3 and 4 minimum profile and maximum profile not supported in
phase1, will return error
00B2 2D data processing
case 2, cp10, value 1 and 2 minimum mosaic and maximum mosaic not supported in
phase1, will return error.
0096 get mosaic
p17, value 1 and 2 minimum mosaic and maximum mosaic not supported in phase1,
will return error
New messages
Debug
06c3 MVS6000 errorlog dump
06C3p1[px][p1[px]]
| 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 console
window
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 with
5 parameters followed by a variable number of arguments, each argument consists
of two elements. All fields are terminated by the field separator (default is
'|').
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:
.
.
Index
image acquisition, 4-2
A numbering, 2-11, 3-24
supported types, 2-16
Acceleration kit CNF_edit, 3-20
connections, 2-15
Communication
display/graphics, 5-3
B dll, 5-2
Boot hardware, 2-5
at MMI startup, 3-26 incompatible messages, A-3
troubleshooting, 6-13 message, 5-4
pipes, 5-3
Breakout box Virtuoso, 5-3
camera connection, 2-11, 2-13
D
C
Display
Cable connectors communication, 5-3
hardware, 2-5
Display.dll
Cables communication, 5-2, 5-3
camera connection, 2-14
Displaytask.dll
Camera communication, 5-2, 5-3
connections and cables, 2-11
R T
Racks Timing kits
16 slots, 2-9 image acquisition, 4-2
7 slots, 2-9 Tools
Rough illumination setting exchanging boards, 6-8
image acquisition, 4-3 language settings, 6-9
PCITerm, 6-2
S reinstall from scratch, 6-10
Troubleshooting
Slot, 2-9, 3-22 boot problems, 6-13
SlotMapping.reg, 3-10, A-2 MMI problems, 6-14
Software Windows2000 problems, 6-11
install MMI, 3-19
install the plug & play driver, 3-3 V
MMI, 3-26
Virtuoso
MVS software, 3-12
MVS6000 hardware files, 3-9 communication, 5-3
PLX PCI, 3-2 software, 3-2
system configuation, 3-20
Virtuoso, 3-2 W
Windows-2000, 3-2
WinComm.dll
System configuration communication, 5-2, 5-4
CNF_edit, 3-20
Param_file.txt, 3-20 Windows2000
language settings, 6-9
software, 3-2
troubleshooting, 6-11