Vision Q.400 V10

README for Vision Q.400 Software Version 10.0.0.70 

for the Q.400 Image Processing System

 

 

31.07.2024

==========

 

(C) Q.VITEC GmbH 2024

 

This document contains a summary of the important changes in all Q.400 versions. Please note that changes that occur

in patch releases are generally not mentioned in the latest manual until the next major release.

 

_______________________________________________________________________________

IMPORTANT NOTES

 

If you have found a software error or if you have a proposal

for an improvement, please use the error reporting form on our website

www.qvitec.de and send this form to our development engineers (support@qvitec.de).

——————————————————————————-

Version 10.0

———————

– Installer:

  – Vision Q.400 now comes with a brand new msi based installer.

  – All common Hardware Plugins are included now and can be selected optionally for installation.

– Documentation

  – All documentation files are installed in the subdirectory “Documentation” of the installation directory of Vision Q.400 now.

  – Information: the Vision Q.400 manuals are currently not fully updated. If you need information about a special feature, which is

    not described in the currently installed manual, please contact your technical support. 

– General

  – New Halcon Version: Halcon 20.11-Steady.

  – 32-bit is not supported anymore.

  – There is only one Full Version of Vision Q.400 now. Users can choose either to use GigE-Vision, CameraLink or Q.Cam Interface.

    This can be done on starting Vision Q.400.

    (QCam Plugins and/or SiliconSoftware Runtime have to be installed separately when using specific Hardware).

  – In the simulation version, the emulated camera type can be switched on starting Vision Q.400.

  – Possibility to easily create support info with the menu item “Tools->Create Support Info…”. The support info is written into a directory, which can be selected.

    Please attach the content of this directory to every support request, otherwise we cannot give you the necessary support. (Or send it to us by an other way.)

  – If the mouse cursor is moved in the camera window, it can be select if the pixel value of the original image data is displayed, or

    if the pixel value of the camera window is displayed.(Press >Crtl> while moving the mouse to display the pixel value of the camera window.)

– Licensing:

  – New Dongles:

    – Switching from MARX XS Dongles to MARX SC Dongles.

– Since the internal data structure changed, a new dongle is required when upgrading a system to Vision Q.400 V10.

– If you have lisenced e.g. a Q.HI script written by you with the help of the Vision Q.400 dongle,

  you have to update the new dongle.

  – Vision Q.400 versions before V10 cannot be licensed with the new dongles.

  – New Options: 

    – Expert Mode: The Expert Mode gives access to some extra features. E.g. Adjustment of Checker Parameters while in Run-Mode.

– Online Halcon Debug: Possibility to Debug HDevelop-Checkers while executing them with Vision Q.400.

  – License files such as license_limited.dat and Licini.dll are no longer supported.

  – Time limited and Hardware-Bound Licenses can be provided on a License Dongle.

  – Simulation Version can be unlocked via License Dongle now.

– Vision Q.400:

  – The loader (Vision Q.400 full version) and starting Vision Q.400 are reviesd.

– Cameras:

  – Rescan function for detecting new cameras without restarting Vision Q.400.

  – GigE Vision:

    – The Halcon GigEVision interface is replaced by the Halcon GigEVision2 interface.

    – The subnet mask of a camera can be changed to the sub net mask of the network connection of the camera.

    – Simulation Version: it is possible to deselect camera series. (By default all camera series are selected.)

      Only camera types, which belongs to a selected series are inserted in the camera selection combo box.

  – Simulation Version:

    – Bugfix in the search order for the camera image file.

– Checker:

  – The shape of a checker can be copied to an other checker. For object shapes, the shape cannot be copied but replaced.

  – Possibilty to list the cecker types and the number of checkers of a type used in an application.  

  – White Balance Checker:

    – The shape of the White Balance can be hidden now.

  – Q.HI Checker:

    – The results of a Q.HI checker can be easily copied into the used results of an other Q.HI checker.

    – The handling of handles in the script language used by a Q.HI checker was changed. Therefore it may be possible

      that a Q.HI checker script has to be adapted to the new handle handling. This may be especially true for scripts not dvelopped by Q.VITEC.

  – Position and Rotation Adjustment:

    – The Reference Values can be edited in the graphical user interface.

  – Gray image filters:

    – The border treatment at the border of a shape is revised.

  – Object shape:

    – Bug fix: if a checker using an object shape was copied into an other sequence, a crash occurred.

– Interfaces:

    – Redesign of the “Interface Exit Options” property page. For details see the manual. (On version up,

      the old settings are correctly transferred.

    – The interface settings are stored in the application and can easily transferred to an other PC.

– There is no need to restart Vision Q.400 to apply changes in the interface settings.  

– Ethernet Interface

  – There is a new Command to Read Spreadsheet Registers via Ascii-Protocol.

– Serial Interface

  – There is a new Command to Read Spreadsheet Registers via Ascii-Protocol.

– Parallel I/O

  – Pin Assignment can be modified “online”.

– Fieldbus Interface

  – The Fieldbus Interface optionally communicates via…

-…Hilscher CifX (as usual)

-…Ethernet (new)

    – Bug fix, only Vision Q.400 [plus]: it is not allowed that two data objects, which belong to different projects,

      share the same variable.

– File Interface

  – New option to limit the file size: the file size can be limited by the number of rows written into the file.

  – New option to use Spreadsheet results in Filenames via Drag&Drop.

    – The MEWTOCOL-protocol is depreciated. It cannot be selected furthermore, but it is supported for existing systems.

    – The OLE interface is depreciated. It is recommented not to use it for new systems. 

– Execution Group Controller:

  – Possibility to create, delete, insert or remove multiple items at once.

  – Execution Groups 1-12 are now independent from corresponding camera number.

– Spreadsheet:

  – Bug-fix Action: Depending on the file name settings for saving images or the spreadsheet, it could happen, that

    more than one file belonging to the same file number was stored if “Numerate file names” was selected.

  – New Script Engine, supporting AngelScript for custom code execution inside Spreadsheet (e.g. advanced string handling).

 – Error Handling:

  – The settings for writing into the error text file are available in the graphical uther interface.

  – Possibility to select the type of errors shown in the error log.

– Application:

  – Execution Times:

    – the times shown in the “Execution Times” dialog are newly arranged, but the total inspection time has not changed by this new arrangement.

    – In the simulation version the “Grab Image” is the time needed to read the images from the image files. Therefore these times can

      never used in the full version, because in the full version an image is always grabbed by a camera.

  – Lock grabbing:

    – Revised. Because the storing of the backup image for lock grabbing needs time, the storing of the backup image can be switched off seperately

      for the setup and the run mode. For the setup mode storing ist the default, for the run mode not storing. If the backup image is not

      stored in the run mode it is not possible to start an application with locked grabbing.

– Known bugs:

  – Moving the mouse over the camera window, the pixel values are sometimes not displayed. The reason is zooming out with the mouse wheel.

    Workouround: clicking with the right mouse button into the camera window.

  – Q.HI Checker: Sometimes not all Q.HI checkers loaded by Vision Q.400 on starting are accessible in the Vision Q.400 user interface.

    You can fix this by reseting the Vision Q.400 menu, toolbar and docking window settings to their defaults. If you do this, you have to restart Vision Q.400.

  – Vision Q.400 [plus], Vision Q.400 standard: If you change between the two Vision Q.400 editions, it may happen that the “Project” menu item

    is shown in the standard edition’s Vision Q.400 user interface, (or not shown in the [plus] edition’s. You can fix this bug as decribed under

    “Q.HI Checker” above.