Tagsurance 3 version 3.6.1 Download Page

Replaced by patch version 3.7.1

Release date: 11-SEP-2023

REST API version: 1.4.0
Async API version: 1.2.0

Installation Instructions

  1. 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.
  2. Close:
    • Tagsurance 3.exe
    • Recipe Builder
  3. Extract installer on Tagsurance Controller PC.
  4. Run setup.exe (reboot if requested).
  5. Note: if you have Tagsurance HF devices in the system and are updating from older version than Tagsurance 3.2.0, you will have to update the firmwares of those to the version 2.5.1 (see manual)
  6. 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)
  7. Restart the Tagsurance Controller PC
    • Keep the rack electrified all the time and restart the PC only

Release Notes

The version 3.6.1 is a patch version and replaces the version 3.6.0
See more detailed release notes of the version 3.6.0 from the version 3.6.0 download page.

Change log

  • Regarding Mühlbauer TAL15k and DDA narrow web (singe lane) machines’ RS-232 tester interface use case the unnecessary risk of crosstalk has been reduced.

Known Issues

  • Critical Bug: An issue with the Tagsurance SL UHF causing false fails (a test task in recipe fails incorrectly). The issue is visible in jobs utilizing the sensitivity test and the next test task after the sensitivity test is the one that in certain conditions may become a false fail. The bug has been fixed in 3.7.1 and it all customers using version 3.6.1 are highly recommended to upgrade to version 3.7.1 to ensure correct results.