--- title: "Q-SYS hardware and software compatibility table review" description: "Review Q-SYS hardware revisions and software support tables, then prepare a version-specific evidence handoff for the AV technician supporting a room." canonical: "https://scalewithsearch.com/articles/qsys-hardware-software-compatibility-table-review" --- ## Site navigation - [Scale With Search](https://scalewithsearch.com/) - Services - Services - [AI systems](https://scalewithsearch.com/ai-systems) - [Site build](https://scalewithsearch.com/work#site-build) - [Whole website fix](https://scalewithsearch.com/work#whole-website-fix) - [Content library with SEO](https://scalewithsearch.com/work#content-library) - [Working session](https://scalewithsearch.com/audit) - Start here - [Send your brief](https://scalewithsearch.com/work#send-your-brief) - [Example scope](https://scalewithsearch.com/work#review-the-example-scope) - [Prices and terms](https://scalewithsearch.com/work#prices-and-terms) - Industries - Real estate - [Real estate agents and teams](https://scalewithsearch.com/for/real-estate) - [Platforms, ownership, and IDX](https://scalewithsearch.com/for/real-estate/real-estate-website-platforms-ownership-idx) - [Search, content, and AI](https://scalewithsearch.com/for/real-estate/real-estate-search-content-ai) - [Inquiries, campaigns, and handoffs](https://scalewithsearch.com/for/real-estate/real-estate-website-inquiries-campaigns-handoffs) - [Buyer, seller, and local pages](https://scalewithsearch.com/for/real-estate/real-estate-buyer-seller-local-resources) - [Rules, privacy, and trust](https://scalewithsearch.com/for/real-estate/real-estate-website-rules-privacy-trust) - Browse by business - [Trades and home services](https://scalewithsearch.com/for/#group-trades) - [Health, wellness, and animal care](https://scalewithsearch.com/for/#group-practices) - [Law, finance, and IT](https://scalewithsearch.com/for/#group-professional) - [Marketing and SEO agencies](https://scalewithsearch.com/for/#group-agencies) - [Shops and manufacturers](https://scalewithsearch.com/for/#group-manufacturing) - [Restaurants, shops, studios, and nonprofits](https://scalewithsearch.com/for/#group-local-services) - Chiropractic practices - [Chiropractic and wellness practices](https://scalewithsearch.com/for/chiropractic-and-wellness-practices) - [Chiropractic and physical therapy clinics](https://scalewithsearch.com/for/chiropractic-and-physical-therapy-clinics) - [All industries](https://scalewithsearch.com/for/) - Resources - Free tools - [AI readiness check](https://scalewithsearch.com/check) - [Free tools](https://scalewithsearch.com/tools/) - [Free Starter Kit](https://scalewithsearch.com/kit/business-memory-starter-kit.zip) - Guides - [AI-native library](https://scalewithsearch.com/ai-native) - [Industry intelligence](https://scalewithsearch.com/intelligence) - [Office job guides](https://scalewithsearch.com/guides/) - [Business memory](https://scalewithsearch.com/articles/business-memory-for-ai-agents-guide) - [Agent governance](https://scalewithsearch.com/articles/ai-agent-governance-guide-small-business) - [Migration and ownership](https://scalewithsearch.com/articles/leaving-vendor-ai-memory-guide) - Articles - [All articles](https://scalewithsearch.com/articles/) - [What changed](https://scalewithsearch.com/changes/) - About - Evidence - [Proof](https://scalewithsearch.com/proof) - Scale With Search - [About](https://scalewithsearch.com/about) - [How it works](https://scalewithsearch.com/how-it-works) # Q-SYS compatibility tables: review installed hardware before a software change Start a Q-SYS software-change discussion with the room's exact equipment identities and the proposed version. Then read both manufacturer compatibility tables. One gives hardware-revision requirements. The other traces additions and removals by software release. A product-family match in one table cannot settle every device in a mixed room. This guide helps a managed service team prepare evidence for its AV technician. It does not provide firmware installation steps or approve a change. Use the [managed service provider overview](/for/it-and-managed-service-providers) for the wider service context. The useful output here is a version-specific handoff with unresolved combinations left visible. Choose the question before collecting screenshots. “Can the room move to the exact proposed release?” requires a different record from “When did this product first appear?” Give the reviewer the proposed destination and the current state together. ## Read the two tables in their actual directions The [compatibility overview](https://help.qsys.com/Content/Q-SYS_Compatibility/Q-SYS_Compatibility_Overview.htm), checked 2026.10.28 with footer Q-SYS 10.5.1, links both tables. Its short navigation descriptions do not fully match the detail of their destination pages. Read each linked page's heading, introduction, and column labels before interpreting it. The [Hardware Revision table](https://help.qsys.com/Content/Q-SYS_Compatibility/Hardware_Compatibility_Product.htm) starts from product changes. Its fields identify the change, first shipped serial or approximate date, and minimum mainline and LTS versions. The [Software Version table](https://help.qsys.com/Content/Q-SYS_Compatibility/Hardware_Compatibility_QDS_Version.htm) starts from a QDS release. Its fields identify release date, added hardware support, and removed hardware support. Both were checked on 2026.10.28 in the 10.5.1 help edition. Read from the installed device toward its revision requirements first. Then read from the proposed software version toward the hardware changes. Keep both findings in the same worksheet. Neither direction should disappear because the other produced an apparently favorable result. If an overview description and a table's columns seem inconsistent, preserve the discrepancy in your source notes. Use the actual cell and its footnote for the row under review. Ask the responsible technician to resolve any interpretation that affects the decision. ## Establish identities before assigning compatibility Ask the technician for the exact model, relevant hardware revision evidence, and observed installed software version. Record the collection date and evidence location. Separate the device's observed version from the version of an office copy of a design file. Use distinct fields for installed software, design-file version, proposed software, and documentation edition. “Current” is not a sufficient value for any of them. A later reader should know which numbered release the reviewer evaluated. Keep serial evidence in the approved private inventory. Your public worksheet template can say “restricted evidence reference.” Do not fabricate realistic serials for demonstrations or put customer identifiers in a shared article comment. When the revision is unknown, write which identification evidence is missing. A product name alone may leave several rows to consider. An approximate shipment date copied from documentation is not proof of when the particular unit shipped. Assign the missing identity check to a person with access to the room or approved records. Avoid asking an account manager to resolve a hardware revision through guesswork. The preparer's job is to make the unknown precise enough for the technician to answer. ## Preserve minimums, footnotes, and empty cells The hardware table's NV-32-H row identifies a DDR4 memory revision and gives v9.12 as its mainline minimum, with v9.13.1 in the LTS column. Its note says units with that revision cannot be downgraded below v9.12. The same page lists TSC-70-G3 LCD changes separately from its network-sensor changes. Those examples show why model and revision evidence belong together. [Hardware rows, checked 2026.10.28](https://help.qsys.com/Content/Q-SYS_Compatibility/Hardware_Compatibility_Product.htm). Record a minimum as a minimum. Do not relabel it “recommended target.” Preserve mainline and LTS in separate columns, and carry relevant notes with their row. A number without its branch or qualifying note is incomplete evidence. The hardware table's footnote says an empty LTS value means the product is not designed for any 9.4.x LTS branch. Preserve that narrow meaning. It does not define every blank as a universal absence of support. Keep a cell marked Pending exactly that way. [Table footnotes, checked 2026.10.28](https://help.qsys.com/Content/Q-SYS_Compatibility/Hardware_Compatibility_Product.htm). For an unresolved cell, record the source location and the unanswered question. Ask whether the missing value affects the particular proposed branch. Do not fill it from a neighboring model or from a different hardware change in the same family. ## Separate added support from continuing eligibility The software table lists Core 1100 among hardware removed in QDS 10.0. It also lists NV-21-HU under additions in 9.8.2. An introduction row does not resolve later revision requirements. Read the intervening release history and the hardware-revision table together. [Software-version rows, checked 2026.10.28](https://help.qsys.com/Content/Q-SYS_Compatibility/Hardware_Compatibility_QDS_Version.htm). Do not interpret “No changes” as a fresh approval for every installation. In your worksheet, treat it as the entry in that release's change columns. Retain any earlier applicable removal and any revision-specific requirement for the installed unit. Preserve the documentation's chronology carefully. On the access date, the software table gives the 10.5.1 release date as October 27, 2029. The official [Designer download page](https://www.qsys.com/resources/software-and-firmware/q-sys-designer-software/) gives October 27, 2026 for that version. Record the apparent date discrepancy and request clarification if chronology controls your decision. Do not silently correct the table or infer that the release is unavailable. This is also why a source record needs an access date and edition. A link to a moving help page cannot tell a later reviewer which wording you used. Preserve a permitted snapshot or a precise passage reference in the team's documentation. ## Walk through a fictional mixed-equipment room The following room and inventory state are synthetic. They illustrate review questions, not an approved combination or an operating installation. Assume Meeting Room Juniper has a proposed change discussion naming QDS 10.0. No installation is authorized by this example. The fictional inventory contains a Core 1100, an NV-32-H whose revision is unconfirmed, and a TSC-70-G3 with no shipment evidence attached. Installed versions remain unverified. The account owner has asked for a compatibility review before any technical recommendation. | Fictional inventory item | Evidence question | Handoff state | | --- | --- | --- | | Core 1100 | Does the proposed release remove this model? | Documented removal in the 10.0 row; technician review required | | NV-32-H | Which hardware revision is installed? | Identity incomplete; do not infer from the family name | | TSC-70-G3 | Which listed hardware changes apply to this unit? | Shipment and revision evidence needed | | Room design | What version created the approved design file? | File evidence not supplied | | Proposed destination | Is 10.0 the intended exact release? | Requester must confirm full version | The Core question already prevents a room-wide positive conclusion. It does not identify a replacement or prescribe a migration. Ask the technician to explain the implications for the actual design and the customer's request. The other two entries remain unresolved. A preparer should not mark them compatible merely because they do not carry the same removal entry. Obtain identity evidence, read the relevant cells, and ask the technician to review the proposed combination. After that review, retain each device's finding. A single summary sentence can identify the decision state, but it should link to the individual rows. Keep “documented removal,” “identity incomplete,” and “awaiting technical interpretation” distinct. ## Build a handoff the technician can inspect Put the intended decision at the top of the handoff. Name the room, request owner, observed current state, proposed exact version, and responsible technician. Include the documentation edition and the date you collected the source evidence. For each device, attach the private inventory reference and the exact table row. Preserve column labels. Add the relevant footnote and the unresolved question. If you cannot locate a matching row, state your search boundary and the missing identity evidence. Use separate fields for source finding and reviewer conclusion. A source finding can say that a row lists a minimum. The reviewer conclusion explains what that finding means for the specific proposed design. Do not write the conclusion on the reviewer's behalf. Carry conflicting evidence into an exception list. Give each exception an owner and a next step. Useful entries include an unidentified revision, an ambiguous branch, a removed device, and a document-date conflict. Avoid the vague label “needs checking” when you can name the exact question. Keep the service record alongside the handoff without merging the two. The companion [discontinued-equipment service-terms guide](/articles/qsys-discontinued-equipment-service-terms-review) addresses repair and warranty evidence. A supported software combination and a service entitlement answer different questions. ## Write useful exceptions instead of a blanket verdict A useful exception tells the technician what evidence would close it. For the fictional NV-32-H, request the revision evidence needed to select the applicable row. For the touchscreen, request the information needed to distinguish its listed changes. Do not ask whether either device is “fine” without specifying the proposed version. Include a short evidence trail with each question. State who recorded the model identity, which source row was read, and which condition remains unverified. That lets the reviewer challenge a single assumption without discarding the entire room inventory. If the technician supplies a correction, retain it with the affected row and the correction date. For example, an incorrect inventory model should change the identity record before it changes the compatibility conclusion. A correction to the proposed version should reopen every relevant device review. Before returning the packet, read its summary against the exception list. A room-level positive statement cannot coexist with an unresolved device row. Use a decision state such as “review incomplete” and name the remaining evidence. The customer-facing explanation can stay brief while the technician's worksheet retains the detail. ## Record the decision without turning it into instructions Ask the responsible technician to return a signed or attributed review result through the team's normal process. Record the exact scope reviewed and any conditions. If the proposed version changes, reopen the relevant rows rather than carrying the previous conclusion forward. The compatibility overview links separate [Upgrade Requirements](https://help.qsys.com/Content/Q-SYS_Compatibility/upgrade_path_requirements.htm) and [Downgrade Notices](https://help.qsys.com/Content/Q-SYS_Compatibility/downgrade_notices.htm). Both were checked on 2026.10.28 in the Q-SYS 10.5.1 help edition. Keep those version-specific requirements in the handoff without treating a table lookup as a complete change plan. Installation planning belongs with the technician and the applicable version-specific instructions. A completed worksheet does not authorize production work. The [business memory guide](/articles/business-memory-for-ai-agents-guide) describes how owned records preserve decisions and corrections. In this case, keep the inventory evidence, documentation snapshot, technician response, and customer decision connected. Preserve earlier versions so the team can explain why a previous conclusion changed. Use the [MSP intelligence overview](/intelligence/it-and-managed-service-providers) for broader research context and the [AV intelligence overview](/intelligence/av-and-led-video-walls) for the room-system perspective. This article's narrower task ends when the technician has a precise, source-backed review packet. Scale With Search can discuss the scope of that documentation handoff and its owned records. Start with the intended reader and the decision the record must support. Keep technical approval and any later software change with the responsible service team. [Discuss your scope](/work) Continue the website review: [AI-native IT providers: the first functions to build](/articles/ai-native-managed-service-providers-first-functions); [E-Rate allowable contract dates: distinguish the waiting period from the bid deadline](/articles/erate-allowable-contract-date-bid-deadline); [E-Rate Form 470 changes: keep the current RFP in your bid review](/articles/erate-form-470-rfp-amendment-review); [Managed IT pricing pages: explain what sets the quote](/articles/managed-it-pricing-website-page); [MSP AI rules: data, approvals, and spend](/articles/msp-ai-rules-data-approvals-spend); [MSP case studies: publish evidence without client names](/articles/msp-anonymous-case-study-website); [MSP onboarding pages: explain the first steps](/articles/msp-client-onboarding-website-page); [MSP contact form spam: inspect the receiving path](/articles/msp-contact-form-spam-controls); [MSP cybersecurity website claims: show the scope](/articles/msp-cybersecurity-website-claims); [Google Business Profile for an MSP: check eligibility](/articles/msp-google-business-profile-eligibility); [MSP service area pages: separate on-site and remote](/articles/msp-onsite-service-area-website-pages); [MSP status pages: publish approved incident updates](/articles/msp-public-status-page-website); [MSP buyer guides: make the download useful](/articles/msp-website-buyer-guide-download); [MSP inquiry emails missing: trace the delivery steps](/articles/msp-website-inquiry-email-not-arriving); [MSP website design: separate sales from support](/articles/msp-website-sales-and-support-paths); [Discontinued AV equipment: read Q-SYS service terms before recommending replacement](/articles/qsys-discontinued-equipment-service-terms-review). [IT and managed service providers](/for/it-and-managed-service-providers): website and search resources. ## Related: IT and managed service providers - [AI-native IT providers: the first functions to build](/articles/ai-native-managed-service-providers-first-functions) - [E-Rate allowable contract dates: distinguish the waiting period from the bid deadline](/articles/erate-allowable-contract-date-bid-deadline) - [E-Rate Form 470 changes: keep the current RFP in your bid review](/articles/erate-form-470-rfp-amendment-review) ---- ```text .|########||. .|########||. .|########||. |##||. .||##|. |##||. .||##|. |##||. .||##|. |#|. .|#|. |#|. .|#|. |#|. .|#|. |#| |#| |#| |#| |#| |#| .#| |#. .#| |#. .#| |#. .#. .#| .#. .#| .#. .#| |#. .#| |#. .#| |#. .#| |# ...... #| |# ...... #| |# ...... #| .# ||#########| #| .# ||#########| #| .# ||#########| #| .#. |######||######|. .#. .#. |######||######|. .#. .#. |######||######|. .#. #. .##|###|##|#|######| .# #. .##|###|##|#|######| .# #. .##|###|##|#|######| .# || |##|#||||||||||||#||#| || || |##|#||||||||||||#||#| || || |##|#||||||||||||#||#| || # |#||||||||||||||||||||#| #. # |#||||||||||||||||||||#| #. # |#||||||||||||||||||||#| #. || |#||||||||||||||||||||||#| || || |#||||||||||||||||||||||#| || || |#||||||||||||||||||||||#| || # .#||||||||||||||||||||||||#| # # .#||||||||||||||||||||||||#| # # .#||||||||||||||||||||||||#| # || ....|||#||||||##|#|||#|#||##||||....|. || || ....|||#||||||##|#|||#|#||##||||....|. || || ....|||#||||||##|#|||#|#||##||||....|. || #. . ....|# ....#||| ||| .#||| ....#. .# #. . ....|# ....#||| ||| .#||| ....#. .# #. . ....|# ....#||| ||| .#||| ....#. .# # . ||||#| .#####|| . .#| .#||| ||||# #. # . ||||#| .#####|| . .#| .#||| ||||# #. # . ||||#| .#####|| . .#| .#||| ||||# #. .| ||||| #. |#|||||. || #. |#||. .||||| || .| ||||| #. |#|||||. || #. |#||. .||||| || .| ||||| #. |#|||||. || #. |#||. .||||| || || |.... #. ....|#. |. ...|. ....|| || || |.... #. ....|#. |. ...|. ....|| || || |.... #. ....|#. |. ...|. ....|| || #. .||||||##||||||##||####|||||||#||||||#| .# #. .||||||##||||||##||####|||||||#||||||#| .# #. .||||||##||||||##||####|||||||#||||||#| .# # .||####|###########################|. # # .||####|###########################|. # # .||####|###########################|. # # .#||||||.#.|| # |. ..# #| #|||||#| # # .#||||||.#.|| # |. ..# #| #|||||#| # # .#||||||.#.|| # |. ..# #| #|||||#| # # .#|||||| .. |# ## |#| ...#|#|||#| # # .#|||||| .. |# ## |#| ...#|#|||#| # # .#|||||| .. |# ## |#| ...#|#|||#| # # .#|||#|# .# .#| #| ##|.#..#|||||#| # # .#|||#|# .# .#| #| ##|.#..#|||||#| # # .#|||#|# .# .#| #| ##|.#..#|||||#| # # .#||||||############|######|||||#| # # .#||||||############|######|||||#| # # .#||||||############|######|||||#| # # |...||#||||||#||||#|#||||||#|||||#||| |.| # # |...||#||||||#||||#|#||||||#|||||#||| |.| # # |...||#||||||#||||#|#||||||#|||||#||| |.| # #. .. ||||# .|||##|. |#| .|| || .|||#. #| # .# #. .. ||||# .|||##|. |#| .|| || .|||#. #| # .# #. .. ||||# .|||##|. |#| .|| || .|||#. #| # .# || | ...|| ...##| | #| .|. |. ##### .. .| || || | ...|| ...##| | #| .|. |. ##### .. .| || || | ...|| ...##| | #| .|. |. ##### .. .| || || ||||| || ||||#| . |. |. |#. ||||| |#| || || || ||||| || ||||#| . |. |. |#. ||||| |#| || || || ||||| || ||||#| . |. |. |#. ||||| |#| || || .# |.....#|....|#.||||.|||##.|#|....||.#||.#. #. .# |.....#|....|#.||||.|||##.|#|....||.#||.#. #. .# |.....#|....|#.||||.|||##.|#|....||.#||.#. #. #.|||||||#############################| ||| .# #.|||||||#############################| ||| .# #.|||||||#############################| ||| .# || ##||#||#||||||#||#||#||#||##. || || ##||#||#||||||#||#||#||#||##. || || ##||#||#||||||#||#||#||#||##. || # .#|||||||||#||#|||||||||||#| # # .#|||||||||#||#|||||||||||#| # # .#|||||||||#||#|||||||||||#| # || |#||||||||||||||||||||||#| || || |#||||||||||||||||||||||#| || || |#||||||||||||||||||||||#| || .# |#||||||||||||||||||||#| #. .# |#||||||||||||||||||||#| #. .# |#||||||||||||||||||||#| #. || |#||||||||||||||||||#| || || |#||||||||||||||||||#| || || |#||||||||||||||||||#| || #. .######|#|#########| .# #. .######|#|#########| .# #. .######|#|#########| .# .#. |#####||||#####| .#. .#. |#####||||#####| .#. .#. |#####||||#####| .#. |# ||########|| #. |# ||########|| #. |# ||########|| #. |# ...... #| |# ...... #| |# ...... #| |#. .#| |#. .#| |#. .#| |#. .#. |#. .#. |#. .#. .#| |#. .#| |#. .#| |#. |#| |#| |#| |#| |#| |#| .|#|. .|#|. .|#|. .|#|. .|#|. .|#|. |##||. .||##| |##||. .||##| |##||. .||##| .||########||. .||########||. .||########||. Scale With Search 2026 [scalewithsearch.com](https://scalewithsearch.com) ```