Tagsurance 3 version 3.8.0 Download Page

Replaced by patch version 3.8.1

Release date: 19-DEC-2023

REST API version: 1.6.0
Async API version: 1.2.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 Feautures:

  • API trigger enables the API users to trigger any active device at any time. This feature is enabled only when a new type of a job is running. When the API trigger is enabled, all other trigger sources are disabled and only limited feature set is enabled.
  • Tagsurance SL UHF has improved tag response detection which can consider a tag as bad if the tag response is significantly weaker than the responses used to be for good tags tested by the same Tagsurance SL UHF tester. This response level detection, also called backscatter strength detection, improves the test result quality especially in multilane processes. In the multilane process, the tester’s sensitive receiver may hear a tag response from the simultaneously tested neighbor tags, but this feature prevents a weak response from being interpreted as a good tag response.

Bug Fixes:

  • Tagsurance HF device got stuck in testing state if connection was not closed by client.
  • Fine-tuning offset was applied only with increments of 1 mm although even more precise values could be set.
  • The EPC data was padded with zeros to meed the expected length.

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.
  • 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.
  • The “Export Data” button disappears for the time the export is processed instead of showing the proggress.
  • 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.