New VENUS Software Release

Hi all,

My apologies - in hindsight, I should have provided some information on known incompatibilities.

  • VENUS 6 methods will not open in previous versions of VENUS
  • VENUS 6 liquid classes will not open in previous versions as the VENUS 6 liquid class dataset now incorporates a new field for MagPip parameters.

Legacy libraries:

  • ASW 3.1 (obsolete) does not work with the new Run Control GUI
  • ASW Custom Vector Dialogs <=1.1.2 does not work with the new Run Control GUI. A compatible v1.1.4 version is available.
  • HSLDeckVisualize - UpdateLoadedLabware to blink an item does not work with the new Run Control GUI. This will be fixed in an upcoming patch.
  • Step Tracker <=1.61 does not work with the new Run Control GUI. A new compatible v1.62 version is available.

I’ll work on getting more clarification on the lack of forward/upward compatibility, but historically with VENUS, it’s been discouraged as there may have been updates to core libraries and functions in newer versions that weren’t compatible with older versions.

-Eric

4 Likes

I also wanted to add when using the shell command, Venus 6 will not open the command prompt when using /K. There’s no way to continue without having to reboot the computer.

2 Likes

Happy Friday, everyone!

As others already alluded to in the thread, there was a reformatting in the med and smt structure with VENUS 6 that prevents them from opening in earlier revisions. Good news is that a patch is forthcoming that will address this and in the interim, @BrandonBare_Hamilton created a method to convert the files.

This method isn’t “official” and neither the method or the patch will address all compatibility concerns. For new functions such as the expanded If/Else command, there will be syntax errors when importing into earlier versions.

I should note that the patch is different than the planned service pack. As soon as I get more info on those, I will be sure to share the news on the forum!

-Eric

6 Likes

I am encountering a bug with the Deck Layout Editor. I am unable to select desired labware that are stacked on each other. I’ve tried sending the undesired labware backwards, but still unable to select it. Is this a known bug?

Hi Hoai,

In 3D mode, if you right-click anywhere off-deck, you can select Select Labware, which shows a list of all labware on the deck. Select the labware you want and it will highlight it and from there you can adjust it.

image

I’m seeing issues with the send to forward/back functions though in 2D mode so I will follow up internally.

1 Like

That works. Thanks Eric. I was using 2D before.

1 Like

Hi Eric,
we are planning to switch from COM interface to the Venus WebAPI. Is there more documentation available than in the swagger html?
Best regards
Wolfgang

Hi Wolfgang,

Yes, there is now an available draft of the API manual, as well as several code examples. This is posted and discussed in a separate thread, which you can find here:

Thanks.

-Nick

3 Likes

Hi Nick,
thank you for very fast response. I did some testing with the Rest API. It worked fine so far. I used “Put api/v1/vector/execution/input” to set variables in Venus. That worked great. Now my questions.

  1. Is there a possibilty to read variable values during or after the run ?
  2. I tried “Get api/v1/vector/file-management/runtime-data” with boolan switch false. But I always get “Runtime data results not returned.” The idea was to get the runGuid which I need in “Get api/v1/vector/file-management/trace-file”
    Thank you very much and best regards
    Wolfgang

Hi Wolfgang,

if running VENUS 6.2 or higher, it´s recommended to use v2 of the API, check the selector on the top right of the Swagger UI:

  1. There is currently no built-in API function to GET method variables at runtime, but the method could be written to have a parallel function running at all times to listen for new requests (either with cURL or using the custom HTTP library) from your controlling software and send back any requested variable information.

  2. To get the runGUID, once the run has started call /api/vector/v2/files/runtime-data

The last entry will be the current run, including its runGUID.

You can set a custom date range filter when calling runtime-data:

Alvaro

2 Likes

In 6.2, you can also call /api/vector/v2/execution/current-run-data
to get the run GUID:

1 Like

Hi Alvaro,

that is my problem. I have selected WebAPIHost V2. I have a methde running.

I used the call /api/vector/v2/files/runtime-data

But I get no response with data. What I observed is, that the time in the response ist 2 hours wrong. That means made the call 18:35:12

Do you have an idea?

Best regards

Wolfgang

Hi Wolfgang,

Can you confirm that you have sample tracking enabled and a functional SQL server Vector database instance?

The runtime data functionality you are attempting to use requires the Vector database to be active during runs. You can check these settings in the system configuration editor:

Thanks.

-Nick

Yes

I found the problem. It’s related to my Venus installation. On my notebook, Trace Viewer and Run History show an error message. On an installation where Trace Viewer and Run History work, the REST API also works perfectly. Sorry to bother you with this problem.
Best regards
Wolfgang


Hi Eric,

I noticed the link to release notes in this thread, and links in other threads to downloads are no longer working. Is there a new path for the shared folders?

Thank you!

The site is currently down and we’ve been working on getting it set back up - it’s taking more time as we want to maintain the original links. My apologies for the delay and inconvenience.

2 Likes