Pivotware 7.5 - Duplicate Stations, Improved Deployment, Dynamic Parameters & more


A new major version of Pivotware just released. See here for the latest additions.


New Features

Copy Stations with steps

Users can now copy a station by itself or choose to also copy all associated steps. In doing so, all associated Unique steps have a new copy created and all Common/Shared steps are reused in the newly created station.


Improved 'Previous Step Result' Display

In CVI Fusion, parameters liked to 'Previous Step Result' parameters have had their display improved in order to be more explicit without entering the parameters directly.


Improvements

Dynamic Time Allocation

The Time Allocation field accessible inside of Step Properties [Common>Step Timing] is now accessible by previous step properties. Input parameters must be given in seconds.


Dynamic Tooling Asset Control

Users can now give a "label" value to a tooling asset. In Action Tool properties, users can now use this value to dynamically call a tooling asset allowing greater flexibility within processes.


Dynamic Socket Tray and Socket Control

Users can now give a "label" value to a socket tray asset. In Action Tool properties, users can now use this value to dynamically call a socket tray asset allowing greater flexibility within processes. A socket tray linked to a dynamic value (lookup table or previous step result) can then have the required sockets dynamically defined.


Dynamic Positioning Control

  • The 'Use Positioning' field accessible inside of Action Tool properties is now accessible by previous step properties. Input parameters must be as a Boolean.
  • The positions used by a positioning arm asset within an Action Tool step are now accessible by previous step properties. Users can define a position using the format [x1,y1,z1]. Multiple positions can be defined by separating entries with a comma like [x1,y1,z1],[x2,y2,z2]. 


Improved Deployment Performance

Deployment of process files and media has been improved considerably. See below for comparison between 7.4 and 7.5 when using a particularly large configuration:


[Advanced Users] Definable Step UID in lookup tables 

Due to how Infinity Client certain functionalities and lookup tables. Some GUID in the backend of the software are reused. This is fine in most cases but poses an issue when users need to reference lookup generated steps in functionality like Positioning Teaching or validating step status with QMS.


A new advanced functionality has been added to Lookup Manager allowing create a specific GUID for these steps. This will allow links to be retained following deployment.


Bug Fixes

[#550] Concurrent Tooling Screen slows down over time

Several memory leaks on Infinity Client have been fixed. These memory leaks were causing freezes and crashes when using QMS, Videos, Concurrent Tool mode, Ignition or any Feature.


[#550] Some boxes are not displayed in Concurrent Tooling Screen

In Concurrent Tool mode, when an Action Tool step was executed, some boxes could not be displayed (Pset, Batch, etc.).


[#550/548] QMS not functioning due to deadlocks in Core Service functionality - QMS not compatible with Concurrent mode

QMS was not compatible with Infinity Client in Concurrent Tool mode. However, in some situation where the server may be overloaded, Core Service and QMS could get deadlocks when requesting the SQL server. Such deadlock may cause QMS not answering to Infinity Client and Infinity not filtering the shared steps.


10Mb limit for the file managed by the Logic File Function move step

When Infinity Client was executing a Logic File Function step in Move mode, it was checking that the file was not exceeding the limit of 10Mb. This limit has been set to 50Mb.


Management of errors in Traceability

In some situation where 2 errors were raised on a same step, or when an error and a comment on deviation were raised, CVI Fusion and Infinity Client were not able to display both errors or the error and the comment on the reports.


Data missing in tightening operation with a synchronous TWINCVI3

When offline results were done by a synchronous TWINCVI3, Infinity Client was not able to retrieve all the offline results of every spindle. Infinity Client can now retrieve the offline results of both spindles of a synchronous TWINCVI3. - This is not managed for system with more than 2 spindles.


Lookups not enabled in Logic File Function but were in Logic File Search

It was not possible anymore to activate the lookup mode of the Logic File Function since the search mode was moved to that new step.


Crash of Infinity Client when using a Positioning arm

When Infinity Client was loading a configuration with a Positioning arm, the application was crashing.


Persistence not working

When the persistence was activated (‘Restart from last step’ option), Infinity Client was always starting a new cycle from the beginning instead of resuming the last cycle.


Fix Korean translation in Infinity

Some translations were not correct for Korean language.


Cannot use Logic File Function result as UID SEQ DATA

CVI Fusion and Infinity Client were not able to use the Logic File Function Search result as UID, SEQ or DATA.


Conversion error when using the Logic File Function Search result as Pset source

Infinity Client raised an error when using the Logic File Function Search result as Pset.


UID/SEQ/DATA can be set to 0

In CVI Fusion, menu Process Configuration, it was possible to set the UID/SEQ/DATA Portion Start to 0. The minimum value has been set to 1.


Installation issue (InfinityClient.msi) with Error 0x80070643

It was not possible to install again Infinity Client after having uninstall it, if starting the installer from a different location.


Installation issue (InfinityModule.msi) with Error 0x80070643

It was not possible to install again Infinity Module after having uninstall it, if starting the installer from a different location.


For more information about the new functionality or bug fixes, please contact support here 

Login to post a comment