Tagsurance 3 version 3.7.1 Download Page
Release date: 27-OCT-2023
REST API version: 1.5.0
Async API version: 1.2.0
Installation Instructions
- Close:
- Tagsurance 3.exe
- Recipe Builder
- Extract installer on Tagsurance Controller PC.
- Run setup.exe to update the system
- 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:
- 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.
- 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
The version 3.7.1 is both a new feature version but also contains a patch for a critical bug and hence replaces the version 3.6.1; updating from 3.6.1 is safe in regards of backwards compatibility
See more detailed release notes of the version 3.6.0 from the version 3.6.0 download page.
See more detailed release notes of the version 3.6.1 from the version 3.6.1 download page.
Note that version 3.7.0 was never relased.
New Feautures:
- Last 50 jobs (as long as 200 M results in total is not exceeded) are now stored and listed in the Operator UI and their CSV exports can be downloaded; note that system automatically cleans up jobs from the oldest when the total number of jobs exceeds 50 or total number of stored results exceeds 200 million.
Bug Fixes:
- Critical Bug Fix: Resolved 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. All customers using version 3.6.1 should upgrade to version 3.7.1 to ensure correct results.
- The yield action trigger with windowSize >0 will now take an action only after the window is fulfilled, e.g. if the yield requirement is 99.95 in a windows of size 1000 and the first tag is a failure, the window will not fail until there are 1000 results
- Operator UI: lot list was sometimes missing last lot
- JOB scoped action triggers did discard the “window” if it was configured in “mb-serial-interface” type jobs
- lot stats are no longer shown when the lot counting is disabled
- Data export failed if job label contained prohibited charactes in file names in Windows systems: \ / : * ? “ < > |
- Operator UI: Sensitivity test: Negative 2 digit values were shown without minus sign
Known Issues:
- The EPC data of Tagsurance SL UHF’s inventory test is padded with zeros to meet the expected length. If the expected word count is 8 in the task configuration, and the tag replies EPC of 6 words, the result will have zeros padded to the end.
- The Recipe Builder’s default values for power levels of Tagsurance SL UHF sensitivity test exceeds the range the device can perform. The recipe made based on default values won’t work and the system refuces to start a job.
- 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.
- Server version 1.2 and later are not supported. The server version 1.2 is delivered since March 2024 and it requires Tagsurance 3 version 3.8.1 or later.
