New VENUS Software Release - 6.3.2

I am happy to inform you all of the release of VENUS 6.3.2. This version is compatible with STAR, STAR V/VANTAGE, NIMBUS, and NIMBUS 96 and adds support for the new Fluid Motion arm and X1 Channels.

See links below for the latest manuals:

Features added since 6.2.1

.NET

  • Update VENUS for .NET 8 compatibility
    (still needs .NET 3.5 for the deck editor and legacy Run Control deck view)

GUI

  • Add a button to refresh the Trace Viewer & Run History lists

Installer

  • Added compatibility for Database Plus add-on installer
  • Option to not install SQL server if present

DeckWatch

  • Added .mp4 file format option to export automated recordings

Method Editor

  • Added ‘Disable Cleanup’ step to STAR and VANTAGE, to skip the instrument cleanup (park channels and grippers, unlock doors, open loading tray, etc.) at the end of the run
  • Assignment with Calculation’ method step to be executed in list order of entry.
    Note: The execution order will only be applied to newly created or edited steps. Existing steps in previous methods will keep their original calculation order if are not edited/modified.
  • Pkg Import: add category selection to Recovery mode

REST API

  • Add endpoint for instrument connection status and attached components
  • API Programmer´s manual and code samples (React, Angular and .NET)

STAR

  • Add ‘Disable cleanup routine’ step to skip the instrument cleanup (park channels and grippers, unlock doors, etc.) at the end of the run
  • Add method step to disable the instrument cleanup routine at the end of the run
  • Add step return error code for CO-RE tool eject error
  • Add step return error code for CO-RE tool pickup error
  • Add support for IPG on Fluid Motion arm
  • Add support for new Fluid Motion arm
  • Add support for new X1 Channels
  • Add support for QCG with X1 Channels
  • Weekly maintenance - optimized Autoloader position for easier access and cleaning

VANTAGE

  • Add ‘Disable cleanup routine’ step to skip the instrument cleanup (park channels and grippers, unlock doors, etc.) at the end of the run
  • Add Calibration Alignment as option in maintenance routine
  • Add support for new Fluid Motion arm
  • Add support for new X1 Channels
  • Add support for VANTAGE Plus instrument deck extension
  • Add Track Gripper Move method step
  • Reduce Track Gripper speed during maintenance routine
  • Run diagnostics file to include collision control 3D files
  • Updated Advanced settings in Load and Reload carrier steps
  • Weekly maintenance - optimized ID Loader position for easier access and cleaning

There were also numerous bug fixes. Refer to the release notes for more details.

If you are interested in upgrading, please get in touch with your local sales and support contacts.

Thank you,

Eric

9 Likes

@EricSindelar_Hamilton, if a method sets “Disable cleanup routine” and ends with the CO-RE Grippers on the channels, what happens the at the start of the next run? Does the Star remember that it still has the grippers loaded, or is there a way to detect that they are still on the channels?

Beautiful.

Hi @DCurrier,

Yes, the STAR will remember that the CO-RE Grippers are on the channels when the next run starts. When the Initialize command is reached in the next run, that is when the standard Clean Up procedure will take place (i.e. dialogs to Open Gripper, confirm Traverse is clear, and eject Grippers back to home). This Clean Up during Initialize cannot be skipped. Note that this behavior also holds true for the iSWAP, in that it will park during the Initialize of the following run.

This functionality is the same on the VANTAGE, with the added benefit of the Loading Tray remaining in whichever state it’s in at the end of the run (typically closed and locked).

Thank you,
Dan

2 Likes

@EricSindelar_Hamilton Could you provide a document with the release notes for VENUS 6.2.3 starting from version 6.0? Ideally, something similar to the one you shared before, including the full release history. I already have the individual release notes for both versions, but I’m missing a single document that compares them. Thank u in advance

Hello,

The release notes for the versions of VENUS 6 are uploaded to this folder. I do not have a single document comparing them. In general, we recommend using the latest version of VENUS, as it offers the most functionality, stability, and other benefits.

Thank you!

Eric

2 Likes

But I can’t see the release notes for version 6.2.3. We plan to leverage the validation of version 6.0.1 by comparing the differences between 6.2.3 and 6.0.1. That’s why I need to know exactly what changes have been made.

Yes, I see some gaps. I uploaded additional notes including 6.2.3.

2 Likes

would the New Venus 6.3.2 be compatible with legacy pkg files? We are using v4.3.5 and exported pkg files to be imported to the new version. After importing the legacy pkg to 6.3.2, and running the imported method in Run Control Simulation, it an error when running an HSLFileDirectoryLib, saying "Invalid class string (0x23 - 0x2 - 0x39). Not sure why? Is this library still compatible with V6.3.2?
Thank you!

Hi @mengwang ,

Yes, 6.3.2 is compatible with pkg files. The error you are seeing is because HSLFileDirectoryLib requires installation. You can download the installer from the link below:

https://download.hamiltonsupport.com/wl/?id=VQY0XAzTfcT7KY29A1YJtZVFwZ7GMOO2&path=Hamilton%20Libraries%2FHSLFileDirectory.zip&mode=grid&download=1

4 Likes

Hey Dan,

Is it still the case that the clean up during initialize cannot be skipped after a “disable clean up” step?

I would like to send several small methods through the .api (aspirate, move, dispense) without doing cleanup between. Is there a way to do this without a cleanup and initialize between each method?