Scale without the premium. Introducing VITARI™ 
Contact Us

      AVITI™ OS 4.0.2 Release Notes

      Summary of Changes

      AVITI OS v4.0.2

      Applies to AVITI Dx™ RUO MODE

      This release is the initial general availability (GA) of AVITI Dx software in RUO mode:

      • Dual-mode operation: A single AVITI Dx instrument can switch between IVD and RUO modes. Maintenance and wash tracking information are shared across both modes.
      • Local user accounts: When operating offline, administrators can create and manage local user accounts on the instrument, with Administrator and Regular User roles.
      • Light and dark display modes: The interface uses a light theme in IVD mode and a dark theme in RUO mode, so the current mode is clear at a glance.
      • Consumable validation: Consumables are checked against the current mode. Mismatched or IVD consumables are blocked.
      • Audit trail: User actions and consumable scans are recorded for full traceability. The audit log can be exported to a USB drive by an Administrator user.
      • Workflow and chemistry support: The software supports run setup, monitoring, washes (stand-by, maintenance, recovery, and service washes), and general instrument maintenance. For sequencing, Cloudbreak Freestyle™, Cloudbreak™, Trinity™, and UltraQ™ chemistries are supported.
      • End-user license agreement (EULA): The EULA is presented at first login and is unique per mode.
      • Data output: The instrument supports data output to SMB or USB, and if online in RUO mode, AWS and GCP.

      Known Issues, v4.0.2:

      • Simultaneous leak errors on both sides of the instrument prevent AVITI OS from unlocking the waste module door.
      • Runs can proceed even if polony map generation fails under specific undetected conditions.
      • The UI may begin to lag after several days of uptime. If this occurs, refresh the UI by pressing Ctrl+Shift+Z on a connected keyboard. Logging out and back in, or power cycling the instrument, will also resolve the issue. To help prevent this issue, power cycle the instrument once per week as recommended in the instrument user guide.

      Dependency Updates, v4.0.2: