Device Firmware Release Notes
...
Enclosure Firmware Releases
Firmware v5.x

20231215 Enclosure FW v5.2.16 / OS 11.7.12.2 Release

7min

Enclosure Firmware Version 5.2.16 Release Notes

Release Dates:

  • Production go-live: December 15, 2023
  • Field, Auto-Update go-live: Week of January 8, 2024

Platforms: IRIS, IRIS Quad

Affected Models: This firmware (FW) update affects the following enclosure models with an IRIS or IRIS Quad SBCs that are currently running FW v5.x.

  • TS030 - Large RFID Cabinet
  • TS032 - Compact RFID Cabinet
  • TS035 - Compact RFID Cabinet (Europe)
  • TS047e – Compact RFID Freezer (Europe)
  • TS056 – Large RFID Cabinet (Europe)
  • TS060 – Compact RFID Refrigerator (Europe)
  • TS074e - Large RFID Refrigerator
  • TS088 - Ultra Low Temperature RFID Freezer
  • TS092 - Large Secure Access Cabinet
  • TS093 - Midsize RFID Freezer
  • TS096 - Undercounter RFID Freezer
  • TS097 - Undercounter RFID Refrigerator
  • TS098 - Countertop RFID Refrigerator
  • TS099 - Midsize RFID Refrigerator
  • TS105 – Countertop RFID Freezer (Europe)

Firmware Version: FW v5.2.16 / OS 11.7.12.2

Application:

Production: FW v5.2.16 should be installed on all new production enclosure models with IRIS or IRIS Quad SBCs.

Field: FW v5.2.16 should be installed on all field-installed enclosure models with IRIS or IRIS Quad SBCs that are currently running v5.0.XX.

Overview of changes: This version adds new functionality pertaining to how I2C communication loss is handled. Enhancements for specific customer applications are merged into this version. There are also important fixes for bugs that can cause boot loops and excessive flash usage.

Adds:

  • I2C failures do not trigger a reboot
    – This is a sweeping change to how temperature reading is performed through I2C. With previous versions of firmware, a failure to read I2C would cause the unit to reboot which was causing difficulties for technical support, CSEs, and customers. The changes are as follows:
  1. The unit will not reboot because of an I2C communication loss.
  2. An I2C communication loss that continues less than 3 seconds will result in the moving average being cleared but no notification will be sent.
  3. An I2C communication loss that continues for 1 minute will result in a LogEntry called “I2CFailure” including a message noting that temperature data could not be read
  4. This LogEntry will be sent every “I2CFailLogentryInterval” minutes
  5. If the I2C communication resumes for 1 minute, the “I2CRestore” LogEntry will be sent
  6. If the temperature reading is outside of the temperature table for less than 3 seconds, these values are ignored
  7. If the temperature reading is outside the temperature table for 1 minute, the “I2CFail” LogEntry will be sent with a message indicating the temperature is out of range of the table
  8. If the temperature reading returns back to within range of the table the “I2CRestore” LogEntry is sent
  • Delay bouncing of ethernet interface when there is a failure to communicate –
    With previous versions of firmware if the device lost connection with DWS for any reason, the ethernet interface would “bounce”, and continue to do so constantly until communication to DWS was restored. In this version, the interface will not be bounced until after “CommsInterfaceRestart” minutes. It will continue to try to re-establish a connection to DWS during this time.
  • Customer-specific enhancements merge
    – The following features that were previously added as versions for specific customers are incorporated into this version:
  1. “DoorDebounceTime” has been added as a parameter to allow this to be set to a lower value
  2. Fixed bug that caused the unit to lock up and reboot with fast successive barcode reads
  3. Added “RemoveEvent” parameter to allow an aggregate event without “removes”
  4. Allow just object events to be shut off by setting “ObjectEventScanCount” to 0
  • Firmware update will look for minimum Operating System (OS) version
    – When there is a firmware update, it will look for a minimum allowed OS version. The firmware update will only proceed if the OS version meets the minimum criteria. This is optional in the package.
  • OS update will look for minimum Firmware version
    – When there is an OS update, it will look for a minimum FW version running. The update will only proceed if the firmware version meets the minimum criteria. This is optional in the package.
  • OS patches
    – With previous versions of firmware, there was no way to do a simple patch through the OS update path. Now a package can be created as a patch so it doesn’t look for an entire image to update. It will just run a script.
  • 5 passes presented without door open
    – With previous versions of firmware, if you presented 5 valid passes in a row without opening the door, a “DoorSensorFailure” LogEntry was sent. This list of 5 can now be any combination of valid or invalid passes

Removes:

  • None

Changes:

  • HID brand pass reader reconnection
    – With previous versions of firmware, when a HID brand pass reader lost connection, it would reconnect as a barcode reader. This is resolved in this version.
  • Updated messages for display
    – The language files for tsi-en-us and pro-en-us have been updated. These changes primarily include text indicating “door(s)” vs “door” the text indicating where a pass should be presented.
  • Blank access key causing a boot loop
    – A situation that has occurred in production has to do with a blank access key. In previous versions of firmware, when an access key is blank the device would go into a boot loop. The firmware now catches this scenario and prevents this from happening.
  • Flash usage by OS
    – This version of OS (11.7.12.2) fixes a flash usage issue that affects all FW v5 units in the field.
  • Null or Undefined EPC value
    - If a tag is reported internally by the Impinj firmware that is an undefined tag “type” or is a completely undefined tag report, the Null or Undefined value is removed from the list. Previously, this undefined data could have been included in the reported tag list with empty (null) or undefined data.
  • Binary or Unicode data included in StatusEvent
    - The StatusEvent is now “cleansed “before sending to make sure no binary or Unicode data ends up in any of the fields. Any fields containing binary or Unicode data will now report “NA”.

Known issues:

  • None

Device Configuration Parameters:

Adds:

  • CommsInterfaceRestart
  • The time in
  • Integer
  • Min:1
  • Max:480
  • Default:15
  • 
  • RemoveEvent
  • When this is set to “true”, EPC tags removed are included in AggregateEvent. When set to false they are omitted from the event.
  • Boolean
  • “true” (“1”)
  • “false” (“0”)
  • Default: “true” (“1”)
  • DoorDebounceTime
  • This is the time in
  • Integer
  • Min:0
  • Max:20
  • Default:4 (2 seconds as in previous versions)
  • I2CFailLogentryInterval
    • This is the time in
  • Integer
  • Min: 0 (off)
  • Max:1440
  • Default: 240

Removes:

  • None

Changes:

  • None

Device Definitions:

Current device definitions for the previous version are still valid.

It is recommended that customers use the most current device definitions available unless instructed otherwise by the Terso Customer Success team.

  • FW v5.2.x, Ambient Cabinet
  • FW v5.2.x, Standard Refrigerator
  • FW v5.2.x, Standard Freezer
  • FW v5.2.x, ULT



Updated 02 Feb 2024
PREVIOUS
20240717 Enclosure FW v5.2.37 / OS 11.7.12.2 Release
NEXT
20221201 Enclosure FW v5.1.16 / OS 11.4.10 Release
Docs powered by Archbee