Tagsurance 3 version 3.10.0 Download Page

Tagsurance3_installer_3.10.0

Release date: 8-May-2024

REST API version: 1.8.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 now supports configuring if an IO only station should return only a pass or fail signal. We have introduced a new configuration option for IO only stations under lane configuration where an IO only station can be configured to pulse on passing tags or pulse on failing tags. Users have the flexibility to set the deadline for waiting for a pulse. This can be either until the next trigger or a user-defined timeout value.

Bug Fixes:

  • Fix router reboot dialogue box which was disappearing too quickly when router settings are changed.
  • Fix an issue which was causing lot stats to be combined in UI with previous job if the previous job was stopped during testing on first lot

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 is almost the same in practice. This is recommended anyway if the machine is 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.
  • In operator UI, when a sensitivity test fails for a tag, the sensitivity result is not shown in the graph. only the sensitivity test specifications (test range and acceptance criteria) are shown.
  • API server loses track of tag counts if it crashes or restarts while a job is running. Consequently, there is result data missing from job export report and summary.