Warning

You are reading an old version of this documentation. If you want up-to-date information, please have a look at 5.1 .

EYE+ Studio 4.3

EYE+ Studio 4.3.0

Released on 2024-05-08

New Features

Home page

EYE+ Studio has been enhanced with a new Home page that displays useful information and allows a quick access to most of the main functionalities.

The page is separated into two different areas: the upper area displays system status, useful resources and support information. The lower area acts as an easy way to set up your system during the first use of EYE+.

The Dashboard which served as the home page previously has been moved to a specific DASHBOARD menu and can also be accessed using the /dashboard endpoint.

Purge Tuning and advanced purge

The purge in EYE+ has been enhanced by adding three new features:

  • EYE+ is now able to detect when all the parts have been evacuated from the platform during a purge sequence. This new feature requires taking a picture of the empty platform. The 8. Purge Configuration (optional) step in the recipe wizard allows you to do that. Note that this step is only visible when the Asycube Purge is enabled.

    The purge <command> <duration> command as well as EtherCAT Purge Duration, EtherNet/IP Purge Duration and PROFINET Purge Duration have been modified to allow triggering the advanced purge.

  • The purge vibration is now independent from the directional vibration that goes in the same direction. The tuning of this vibration is done in the new 8. Purge Configuration (optional) recipe wizard step.

    For Asycube 530, the offset between the right and left actuators can be modified. This will allow better fine-tuning of the purge vibration on this Asycube size and prevent the cases where the parts were not able to leave the platform.

  • It is now possible to enable the Asycube Purge on Asycube 50 and 80.

Hopper Configuration

The configuration of the hoppers has been moved out of the recipe (7.2 Hopper Tuning) and placed into a new global configuration section (Hopper). This will save you from having to configure the hopper each time you create a new recipe by simply selecting the hopper you want to use in a drop-down menu in the recipe wizard.

The Asycube configuration and Hopper configuration has been regrouped in the Feeding Devices section.

Asyfill via TCP/IP

Asyfill are now supported via the TCP/IP interface which will allow advanced control of the Asyfill by EYE+.

The connection of the Asyfill is done through the Asyfill Ethernet port (or Robot port for users with EYE+ Controller cover rev.0).

Up to 4 Asyfill can be connected to a single EYE+ Controller using the Ethernet Switch and the configuration and calibration of each Asyfill can be done from the Asyfill configuration page.

Recipe Wizard

  • 3.3 Candidate Classification: Classification modes has been introduced in the candidate classification. You can now choose if you want to classify using the Focus Mode (one candidate at the time, selection done with keyboard) or the Overview Mode (whole picture visible, selection done with the mouse).

General

  • Recipes list: Inform the user about invalid recipes that were created and/or modified using a later version of EYE+.

Improvements

Configuration

  • Communication: The page has been adapted to display the correct Ethernet port names depending on the revision of the EYE+ Controller cover. See Ethernet Connections for more information about the cover revisions.

  • Asycube: Display the Serial Number of the Asycube if available (requires Firmware >=7.0.0)

Help

  • TCP terminal: Redundant commands are not saved in the history anymore. This makes the navigation of the history with the up and down keys more user-friendly.

  • Help: The About information has been updated to display the revision of the EYE+ Controller cover.

Documentation

Resolved issues

Configuration

  • Storage: Fixed an issue where the button for remote storage recipe migration was displayed when the remote recipe were created with a later version of EYE+ Studio.

Recipes

  • Import recipe: Add a proper error message when trying to import a recipe from a newer version of EYE+ into an older EYE+ system.

  • Import recipe: Fixed an issue where importing a recipe with classification from an older EYE+ Studio version into another EYE+ system could display wrong classification images and potentially corrupt other recipes on that system.

  • 7.1 Platform Tuning: (Asycube 50 and 80 only) Fixed an issue where the High Energy Mode amplitude was never applied on the vibrations.

  • Measure recipe performance: Fixed an issue where the vibrations were not properly set in the Asycube when loading a recipe for qualification.

Production

  • Fieldbus Integration: Fixed an issue where, when stopping the Purge or Production, the Stop State Done flag was raised before the internal processing was complete.

  • Fixed an issue where Start Production would fail and return various errors after having repeatedly stopped and restarted the production.

  • get_parameter <parameter> (<value>…): Fixed an issue where invalid values were accepted for the multi-feeding parameters if they started with the right letter.

  • Fieldbus Integration: Fixed an issue where changing the timeout to the value 0 would not be reported in the read-back value Command Timeout.

Breaking changes

With the introduction of the advanced purge feature, a few changes were required:

  • Using a purge plate command with 0 as an argument will use the advanced purge mode instead of using the vibration duration set in the recipe.

  • When running a start production, if the purge flap is unable to be closed after some time the system will now return an error code 517 (418 before). See Server error codes for more information.