Tagsurance 3 version 3.9.1 Download Page

Tagsurance3_installer_3.9.1

Release date: 22-Apr-2024

REST API version: 1.7.0
Async API version: 1.3.0

Installation Instructions

  1. Close:
    1. Tagsurance 3.exe
    2. Recipe Builder
  2. Extract installer on Tagsurance Controller PC.
  3. Run setup.exe to update the system
  4. Restart the Tagsurance 3 Controller PC
    • Keep the rack powered up and restart the PC only

IMPORTANT!!! if you are updating from older version than 3.3, read before you start:

  1. If your Tagsurance Controller rack does not have a router (white small box with 5 ethernet sockets), you will need to first request one from support@voyantic.com; this software version and the ones succeeding it will not work without the router.
  2. If you have a router (white small box with 5 ethernet sockets) you will need to update it; request the update SW from support@voyantic.com. Note that it is system serial number specific, with the request send the serial numbers of all the Tagsurance 3 systems you update.
    • After updating the Tagsurance 3 software (step 3 above), update the router as instructed by support@voyantic.com when you requested the router update SW from them (only for updates from older than Tagsurance 3.3)

Release Notes

New Features:

  • Tagsurance 3 supports an external signal for a lot change. Now it is possible for the production machine, e.g. turret rewinder, to give an IO signal when the liner is cut and the lot is changed. The lot change position is parametric in Tagsurance 3 and the position can be set according to the location where, for example, the liner is cut. The lot number is added to the tag results as before. When an external lot control is enabled, only a limited set of action triggers are available.
  • The Units Per Hour value is displayed in the operator UI. The UPH is calculated based on the past time window which can be configured in Tagsurance 3 settings.
  • The delay compensation for IO-only devices added. For now, the configuration is only available at API.
  • In operator UI, users can increase step size by 0.5 mm (instead of the current 0.1 mm).
  • Only the supported device types in TAL15k and DDA job settings are shown.

 

Bug Fixes:

  • The progress was not shown in the operator UI during the data export
  • The populated device list looked empty in the Action Trigger settings
  • The transmit power values were incorrectly rounded in Recipe Builder
  • The axis values were not rounded in the measured pitch graph in the operator UI
  • Data communication improved between the lane controller and the server
  • The yield value had too few decimals in the summary of the exported data
  • The job type was always reset to standard when a recipe was loaded
  • Some lots are not shown on the list of completed lots in the operator UI
  • The Recipe Builder downloaded from the operator UI didn’t work
  • The sensitivity test created with default values in the Recipe Builder didn’t work
  • Incorrect sensitivity test configuration was accepted for Tagsurance HF which eventually caused the FW crash

Known Issues:

  • The Inventory test and the EPC retrieving in Read test are failing if the defined EPC length in the test definition is not matching to the length of EPC in the tag response.
  • Action trigger for system status “Idle” doesn’t work. Instead, you can use the status “Stopping”, which in practice almost the same. This would be recommended anyway in a case where the machine should be stopped via digital IO signal via Machine IO as then it gets the stop signal as soon as possible after testing has been stopped.
  • The API spec doesn’t explicitly state that the property “triggerMode”: “API_TRIGGER” must be included in the job payload in order to start the job in API-trigger mode.