{"id":33410,"date":"2026-07-23T19:58:19","date_gmt":"2026-07-23T11:58:19","guid":{"rendered":"https:\/\/pxisource.com\/?p=33410"},"modified":"2026-07-23T20:57:35","modified_gmt":"2026-07-23T12:57:35","slug":"ni-daqmx-functions-missing-in-labview","status":"publish","type":"post","link":"https:\/\/pxisource.com\/ru\/blog\/ni-daqmx-functions-missing-in-labview\/","title":{"rendered":"NI-DAQmx Functions Missing in LabVIEW: Causes and Solutions"},"content":{"rendered":"
\n\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t
\n\t\t\t\n\t\t\t
\n\n
\n Problem:<\/strong> After installing LabVIEW or updating NI-DAQmx, the DAQ device may appear correctly in Windows Device Manager and NI Measurement & Automation Explorer (NI MAX), but the NI-DAQmx functions, palettes, subVIs, or configuration options are missing or unavailable.\n <\/div>\n\n

NI-DAQmx Functions Are Missing or Unavailable in LabVIEW<\/h3>\n\n

\n You may be able to see your NI data acquisition device or module under Devices and Interfaces<\/strong> in NI MAX, while LabVIEW cannot find or use the NI-DAQmx functions required to develop and run a data acquisition application.\n <\/p>\n\n

\n This problem does not necessarily mean that the DAQ hardware is defective. In most cases, it is caused by software compatibility, missing LabVIEW support components, an incorrect installation order, or an incomplete NI-DAQmx installation.\n <\/p>\n\n

\n The most common symptoms include:\n <\/p>\n\n

\n\n
\n 1<\/span>\n Missing DAQmx Palette<\/strong>\n

\n NI-DAQmx functions or subVIs do not appear under the LabVIEW Measurement I\/O palette.\n <\/p>\n <\/div>\n\n

\n 2<\/span>\n Version-Specific Problem<\/strong>\n

\n DAQmx functions appear in one LabVIEW version or bitness but are missing from another.\n <\/p>\n <\/div>\n\n

\n 3<\/span>\n Broken or Missing SubVIs<\/strong>\n

\n Existing VIs show a broken Run arrow or prompt LabVIEW to search for missing DAQmx subVIs.\n <\/p>\n <\/div>\n\n <\/div>\n\n

Common Symptoms<\/h3>\n\n

NI-DAQmx Is Missing from the Measurement I\/O Palette<\/h4>\n\n

\n When you right-click the LabVIEW block diagram and open the Measurement I\/O<\/strong> palette, the NI-DAQmx VIs and functions are not available.\n <\/p>\n\n

DAQmx Appears in One LabVIEW Version but Not Another<\/h4>\n\n

\n NI-DAQmx functions may appear correctly in one LabVIEW release but remain unavailable in another installed release. A similar problem may occur when the functions are installed for 32-bit LabVIEW but not for 64-bit LabVIEW, or the reverse.\n <\/p>\n\n

Existing VIs Have a Broken Run Arrow<\/h4>\n\n

\n When opening an existing project, LabVIEW may display a broken Run arrow or ask you to locate missing DAQmx subVIs. This usually indicates that the application development support files were not installed for the LabVIEW version currently opening the project.\n <\/p>\n\n

NI MAX Configuration Features Are Missing<\/h4>\n\n

\n An incomplete NI-DAQmx installation may also cause features to disappear from NI MAX. Examples include:\n <\/p>\n\n

    \n
  • \u0417\u0435\u043c\u043b\u044f Test Panels<\/strong> option is missing when right-clicking a DAQ device.<\/li>\n
  • The option to find network NI-DAQmx devices is unavailable.<\/li>\n
  • \u0417\u0435\u043c\u043b\u044f Data Neighborhood<\/strong> section does not appear under My System.<\/li>\n
  • There is no option to create NI-DAQmx virtual channels or tasks.<\/li>\n
  • Device connection diagrams or configuration options are unavailable.<\/li>\n <\/ul>\n\n

    Why Can LabVIEW Not Find the NI-DAQmx Functions?<\/h3>\n\n

    \n The NI-DAQmx device driver and the LabVIEW development support files are separate software components. Windows may recognize the DAQ hardware and NI MAX may display the device even when NI-DAQmx support for a particular LabVIEW installation is missing.\n <\/p>\n\n

    \n The problem is commonly caused by one of the following:\n <\/p>\n\n

      \n
    • The installed NI-DAQmx version does not support the DAQ hardware.<\/li>\n
    • NI-DAQmx is incompatible with the operating system or LabVIEW release.<\/li>\n
    • Support for the installed LabVIEW version was not selected during NI-DAQmx installation.<\/li>\n
    • NI-DAQmx was installed before LabVIEW.<\/li>\n
    • Only an NI-DAQmx Runtime package was installed.<\/li>\n
    • The NI-DAQmx LabVIEW palette or menu files are missing.<\/li>\n
    • The NI-DAQmx installation is incomplete or corrupted.<\/li>\n
    • The required support was installed for 32-bit LabVIEW but not for 64-bit LabVIEW.<\/li>\n <\/ul>\n\n

      How to Restore Missing NI-DAQmx Functions in LabVIEW<\/h3>\n\n

      1. Confirm NI-DAQmx Compatibility<\/h4>\n\n

      \n First, confirm that the installed NI-DAQmx version is compatible with all parts of the system:\n <\/p>\n\n

        \n
      • The specific NI DAQ device or module<\/li>\n
      • The Windows operating system<\/li>\n
      • The installed LabVIEW version<\/li>\n
      • The LabVIEW bitness: 32-bit or 64-bit<\/li>\n
      • Other NI software installed on the computer<\/li>\n <\/ul>\n\n

        \n Review the NI-DAQmx ReadMe, supported hardware list, operating system support information, and LabVIEW compatibility documentation for the driver version.\n <\/p>\n\n

        \n Important:<\/strong> Do not install the newest NI-DAQmx release without first checking compatibility. The newest driver may not support an older LabVIEW release or operating system.\n <\/div>\n\n

        2. Check NI-DAQmx Support for Your LabVIEW Version<\/h4>\n\n

        \n NI-DAQmx must install application development environment support for each compatible LabVIEW version. If this component is not selected, the hardware driver may work while the LabVIEW DAQmx palette remains missing.\n <\/p>\n\n

        \n Recommended procedure:<\/strong>\n\n
          \n
        1. Close LabVIEW, NI MAX, and all other NI applications.<\/li>\n
        2. Open NI Package Manager<\/strong> as an administrator.<\/li>\n
        3. Locate the installed NI-DAQmx package.<\/li>\n
        4. Review the related or additional package selections.<\/li>\n
        5. Confirm that NI-DAQmx Support for LabVIEW 20xx<\/strong> is installed for your LabVIEW release.<\/li>\n
        6. Install the missing LabVIEW support component.<\/li>\n
        7. Restart the computer after the installation finishes.<\/li>\n
        8. Open LabVIEW and check the Measurement I\/O palette again.<\/li>\n <\/ol>\n <\/div>\n\n

          \n The exact package name may include the year of the supported LabVIEW release. If the installed LabVIEW version is not offered as an available NI-DAQmx support component, the selected NI-DAQmx release may not support that LabVIEW version.\n <\/p>\n\n

          3. Check 32-Bit and 64-Bit LabVIEW Separately<\/h4>\n\n

          \n Installing NI-DAQmx support for 32-bit LabVIEW does not always mean that the required support is also installed for 64-bit LabVIEW. Treat the two LabVIEW installations as separate development environments.\n <\/p>\n\n

          \n Verify the following:<\/strong>\n\n
            \n
          • Which LabVIEW bitness is currently running<\/li>\n
          • Whether the VI was originally developed in 32-bit or 64-bit LabVIEW<\/li>\n
          • Whether NI-DAQmx development support is installed for that environment<\/li>\n
          • Whether all additional toolkits and dependencies support the selected bitness<\/li>\n <\/ul>\n <\/div>\n\n

            \n If DAQmx functions appear in 32-bit LabVIEW but not in 64-bit LabVIEW, modify or reinstall NI-DAQmx and select the appropriate 64-bit LabVIEW support when available.\n <\/p>\n\n

            4. Correct the NI Software Installation Order<\/h4>\n\n

            \n NI recommends installing the application development environment, such as LabVIEW or LabWindows\/CVI, before installing the hardware driver.\n <\/p>\n\n

            \n The preferred installation order is:\n <\/p>\n\n

              \n
            1. Install LabVIEW or another supported development environment.<\/li>\n
            2. Install the required LabVIEW modules and toolkits.<\/li>\n
            3. Install NI-DAQmx and select support for the installed development environment.<\/li>\n
            4. Restart the computer.<\/li>\n
            5. Connect or install the DAQ hardware.<\/li>\n <\/ol>\n\n

              \n If NI-DAQmx was installed before LabVIEW, the driver installer could not detect the LabVIEW installation and may not have installed the required VIs, libraries, examples, menu files, or palette integration.\n <\/p>\n\n

              \n If LabVIEW was installed after NI-DAQmx:<\/strong>\n\n
                \n
              1. Open NI Package Manager.<\/li>\n
              2. Locate NI-DAQmx and its related development support packages.<\/li>\n
              3. Add support for the installed LabVIEW version when available.<\/li>\n
              4. If modification is unavailable, repair or reinstall NI-DAQmx.<\/li>\n
              5. Restart Windows after completing the repair or reinstallation.<\/li>\n <\/ol>\n <\/div>\n\n

                5. Confirm the Required NI-DAQmx Components Are Installed<\/h4>\n\n

                \n A complete development installation generally requires three types of NI-DAQmx components.\n <\/p>\n\n

                \n\n
                \n 1<\/span>\n Device Driver<\/strong>\n

                \n Enables Windows and NI software to communicate with supported NI data acquisition hardware.\n <\/p>\n <\/div>\n\n

                \n 2<\/span>\n MAX Configuration<\/strong>\n

                \n Provides test panels, connection diagrams, device configuration, tasks and virtual channels in NI MAX.\n <\/p>\n <\/div>\n\n

                \n 3<\/span>\n ADE Support<\/strong>\n

                \n Installs the VIs, APIs, libraries and palette integration required by LabVIEW and other development environments.\n <\/p>\n <\/div>\n\n <\/div>\n\n

                \n You can review the installed software in NI Package Manager. Depending on the software generation, relevant components may also appear under My System \u2192 Software<\/strong> in NI MAX.\n <\/p>\n\n

                6. Make Sure the Correct NI-DAQmx Package Type Is Installed<\/h4>\n\n

                \n Different NI-DAQmx distributions provide different levels of functionality. The exact package names may vary by driver generation, but the installations generally fall into the following categories:\n <\/p>\n\n

                \n Full development installation<\/strong>\n\n

                \n Includes the device drivers, NI MAX configuration support and application development environment support. Choose this type when developing DAQ applications in LabVIEW.\n <\/p>\n <\/div>\n\n

                \n Runtime with configuration support<\/strong>\n\n

                \n Includes the device driver and NI MAX configuration components. It is suitable for a test computer that needs NI MAX hardware access but is not used to develop LabVIEW applications.\n <\/p>\n <\/div>\n\n

                \n Minimal Runtime installation<\/strong>\n\n

                \n Primarily includes the components required to run a deployed application. It may not include LabVIEW development palettes or complete NI MAX configuration functionality.\n <\/p>\n <\/div>\n\n

                \n Important:<\/strong> A Runtime installation may allow an existing executable to communicate with the DAQ device, but it does not necessarily install the NI-DAQmx functions required to develop or edit an application in LabVIEW.\n <\/div>\n\n

                7. Check the LabVIEW VI and Menu Files<\/h4>\n\n

                \n NI-DAQmx support installs VIs and menu files into the supported LabVIEW directory. The menu files connect the installed DAQmx VIs to the LabVIEW Functions palette.\n <\/p>\n\n

                \n Depending on the LabVIEW and NI-DAQmx versions, the files are typically located in directories similar to:\n <\/p>\n\n

                \n LabVIEW VI library:<\/strong>\n\n

                \n C:\\Program Files\\National Instruments\\LabVIEW 20xx\\vi.lib\n <\/p>\n\n LabVIEW palette menu files:<\/strong>\n\n

                \n C:\\Program Files\\National Instruments\\LabVIEW 20xx\\menus\\default\n <\/p>\n <\/div>\n\n

                \n For 32-bit LabVIEW installed on 64-bit Windows, the LabVIEW directory may instead be located under:\n <\/p>\n\n

                \n

                \n C:\\Program Files (x86)\\National Instruments\\LabVIEW 20xx\\\n <\/p>\n <\/div>\n\n

                \n Do not manually copy DAQmx VIs from another LabVIEW installation as the first solution. The files may depend on additional libraries, registry entries, services, or version-specific components. Modifying or repairing NI-DAQmx through NI Package Manager is safer.\n <\/p>\n\n

                8. Check the LabVIEW Palette Settings<\/h4>\n\n

                \n If the NI-DAQmx files are installed but the palette is still not visible, check the LabVIEW palette configuration.\n <\/p>\n\n

                  \n
                1. Open LabVIEW.<\/li>\n
                2. Select Tools \u2192 Options<\/strong>.<\/li>\n
                3. Open the Controls\/Functions Palettes<\/strong> settings.<\/li>\n
                4. Confirm that the expected palette categories are not hidden.<\/li>\n
                5. Restart LabVIEW and check Measurement I\/O again.<\/li>\n <\/ol>\n\n

                  9. Repair NI-DAQmx<\/h4>\n\n

                  \n If the driver type and compatibility are correct but the functions remain unavailable, repair the NI-DAQmx installation.\n <\/p>\n\n

                  \n Repair procedure:<\/strong>\n\n
                    \n
                  1. Close all NI applications.<\/li>\n
                  2. Open NI Package Manager as an administrator.<\/li>\n
                  3. Locate NI-DAQmx and its related packages.<\/li>\n
                  4. Use the repair option when available.<\/li>\n
                  5. Confirm that LabVIEW support and MAX configuration components are selected.<\/li>\n
                  6. Allow the repair process to finish.<\/li>\n
                  7. Restart the computer.<\/li>\n
                  8. Open LabVIEW and test the NI-DAQmx palette.<\/li>\n <\/ol>\n <\/div>\n\n

                    10. Reinstall NI-DAQmx if the Installation Is Corrupted<\/h4>\n\n

                    \n If all compatibility, package and installation-order checks are correct, the NI-DAQmx installation may be corrupted.\n <\/p>\n\n

                    \n Remove and reinstall the compatible NI-DAQmx packages through NI Package Manager. Make sure LabVIEW is already installed before reinstalling the driver, and select development support for the required LabVIEW release.\n <\/p>\n\n

                    \n Before removing NI software:<\/strong> Record the installed versions and back up important NI MAX tasks, virtual channels, scales, aliases and device configurations. Removing or reinstalling related packages may affect existing applications.\n <\/div>\n\n

                    Recommended Troubleshooting Order<\/h3>\n\n
                    \n\n
                      \n
                    1. Confirm the DAQ device appears correctly in Windows Device Manager.<\/li>\n
                    2. Confirm the device is supported by the installed NI-DAQmx version.<\/li>\n
                    3. Verify compatibility with Windows and the installed LabVIEW release.<\/li>\n
                    4. Check whether you are using 32-bit or 64-bit LabVIEW.<\/li>\n
                    5. Confirm that NI-DAQmx support for the specific LabVIEW version is installed.<\/li>\n
                    6. Confirm that the full development components are installed, not only Runtime.<\/li>\n
                    7. Check the LabVIEW Measurement I\/O palette settings.<\/li>\n
                    8. Repair NI-DAQmx through NI Package Manager.<\/li>\n
                    9. Restart the computer and test LabVIEW again.<\/li>\n
                    10. Reinstall a compatible NI-DAQmx package if the problem remains.<\/li>\n <\/ol>\n\n <\/div>\n\n

                      Frequently Asked Questions<\/h3>\n\n

                      Why does NI MAX detect my DAQ device while LabVIEW does not show DAQmx?<\/h4>\n\n

                      \n NI MAX hardware detection and LabVIEW development support are separate components. The device driver and MAX configuration files may be installed while NI-DAQmx support for your LabVIEW version is missing.\n <\/p>\n\n

                      Why is NI-DAQmx available in one LabVIEW version but not another?<\/h4>\n\n

                      \n NI-DAQmx development support must be compatible with and installed for each LabVIEW version. A driver may support one LabVIEW release but not an older or newer installation on the same computer.\n <\/p>\n\n

                      Why does DAQmx appear in 32-bit LabVIEW but not in 64-bit LabVIEW?<\/h4>\n\n

                      \n The required development support may only be installed for one LabVIEW bitness. Verify NI-DAQmx compatibility and install the appropriate support for the LabVIEW environment you are using.\n <\/p>\n\n

                      Can NI-DAQmx Runtime add the DAQmx palette to LabVIEW?<\/h4>\n\n

                      \n A minimal Runtime package is intended primarily for running deployed applications. To develop or edit NI-DAQmx code in LabVIEW, install an NI-DAQmx package that includes application development environment support.\n <\/p>\n\n

                      Should LabVIEW be installed before NI-DAQmx?<\/h4>\n\n

                      \n Yes. Installing LabVIEW first allows the NI-DAQmx installer to detect the development environment and offer the correct LabVIEW support components.\n <\/p>\n\n

                      Does a missing DAQmx palette mean the hardware is damaged?<\/h4>\n\n

                      \n Usually not. If Windows Device Manager or NI MAX detects the device, a missing palette is more likely related to NI-DAQmx compatibility, package selection, development support, or installation integrity.\n <\/p>\n\n

                      Related Information for Older LabVIEW Systems<\/h3>\n\n
                      \n\n

                      \n Very old LabVIEW and Traditional NI-DAQ installations have strict version limitations. Installing a newer legacy NI-DAQ driver may remove support for an older LabVIEW release, while installing an older driver may remove support for a newer release.\n <\/p>\n\n

                      \n Traditional NI-DAQ and NI-DAQmx are different driver architectures. When maintaining legacy systems, confirm the exact hardware, LabVIEW release, operating system and required driver before changing the installation.\n <\/p>\n\n

                      \n For modern systems, use NI-DAQmx whenever it is supported by the hardware and application. Avoid modifying a stable legacy installation without recording the existing versions and creating a recovery plan.\n <\/p>\n\n <\/div>\n\n<\/div>\n\t\t\t\t\t<\/div>\n\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>","protected":false},"excerpt":{"rendered":"

                      Learn how to fix missing NI-DAQmx functions, palettes, subVIs and MAX features after installing or upgrading LabVIEW and the NI-DAQmx driver.<\/p>","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[559],"tags":[],"class_list":["post-33410","post","type-post","status-publish","format-standard","hentry","category-knowledge-base"],"acf":[],"yoast_head":"\nNI-DAQmx Functions Missing in LabVIEW: Causes and Solutions - PXI Source<\/title>\n<meta name=\"description\" content=\"Learn how to fix missing NI-DAQmx functions, palettes, subVIs and MAX features after installing or upgrading LabVIEW and the NI-DAQmx driver.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/pxisource.com\/ru\/blog\/ni-daqmx-functions-missing-in-labview\/\" \/>\n<meta property=\"og:locale\" content=\"ru_RU\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"NI-DAQmx Functions Missing in LabVIEW: Causes and Solutions\" \/>\n<meta property=\"og:description\" content=\"Learn how to fix missing NI-DAQmx functions, palettes, subVIs and MAX features after installing or upgrading LabVIEW and the NI-DAQmx driver.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/pxisource.com\/ru\/blog\/ni-daqmx-functions-missing-in-labview\/\" \/>\n<meta property=\"og:site_name\" content=\"PXI Source\" \/>\n<meta property=\"article:publisher\" content=\"https:\/\/www.facebook.com\/profile.php?id=61582573040385\" \/>\n<meta property=\"article:published_time\" content=\"2026-07-23T11:58:19+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2026-07-23T12:57:35+00:00\" \/>\n<meta name=\"author\" content=\"pxisource\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"\u041d\u0430\u043f\u0438\u0441\u0430\u043d\u043e \u0430\u0432\u0442\u043e\u0440\u043e\u043c\" \/>\n\t<meta name=\"twitter:data1\" content=\"pxisource\" \/>\n\t<meta name=\"twitter:label2\" content=\"\u041f\u0440\u0438\u043c\u0435\u0440\u043d\u043e\u0435 \u0432\u0440\u0435\u043c\u044f \u0434\u043b\u044f \u0447\u0442\u0435\u043d\u0438\u044f\" \/>\n\t<meta name=\"twitter:data2\" content=\"9 \u043c\u0438\u043d\u0443\u0442\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/pxisource.com\\\/blog\\\/ni-daqmx-functions-missing-in-labview\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/pxisource.com\\\/blog\\\/ni-daqmx-functions-missing-in-labview\\\/\"},\"author\":{\"name\":\"pxisource\",\"@id\":\"https:\\\/\\\/pxisource.com\\\/#\\\/schema\\\/person\\\/bf03a76c93aa10f3b902e0131e55d3d0\"},\"headline\":\"NI-DAQmx Functions Missing in LabVIEW: Causes and Solutions\",\"datePublished\":\"2026-07-23T11:58:19+00:00\",\"dateModified\":\"2026-07-23T12:57:35+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/pxisource.com\\\/blog\\\/ni-daqmx-functions-missing-in-labview\\\/\"},\"wordCount\":1980,\"commentCount\":0,\"articleSection\":[\"knowledge base\"],\"inLanguage\":\"ru-RU\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\\\/\\\/pxisource.com\\\/blog\\\/ni-daqmx-functions-missing-in-labview\\\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/pxisource.com\\\/blog\\\/ni-daqmx-functions-missing-in-labview\\\/\",\"url\":\"https:\\\/\\\/pxisource.com\\\/blog\\\/ni-daqmx-functions-missing-in-labview\\\/\",\"name\":\"NI-DAQmx Functions Missing in LabVIEW: Causes and Solutions - PXI Source\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/pxisource.com\\\/#website\"},\"datePublished\":\"2026-07-23T11:58:19+00:00\",\"dateModified\":\"2026-07-23T12:57:35+00:00\",\"author\":{\"@id\":\"https:\\\/\\\/pxisource.com\\\/#\\\/schema\\\/person\\\/bf03a76c93aa10f3b902e0131e55d3d0\"},\"description\":\"Learn how to fix missing NI-DAQmx functions, palettes, subVIs and MAX features after installing or upgrading LabVIEW and the NI-DAQmx driver.\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/pxisource.com\\\/blog\\\/ni-daqmx-functions-missing-in-labview\\\/#breadcrumb\"},\"inLanguage\":\"ru-RU\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/pxisource.com\\\/blog\\\/ni-daqmx-functions-missing-in-labview\\\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/pxisource.com\\\/blog\\\/ni-daqmx-functions-missing-in-labview\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/pxisource.com\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"NI-DAQmx Functions Missing in LabVIEW: Causes and Solutions\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/pxisource.com\\\/#website\",\"url\":\"https:\\\/\\\/pxisource.com\\\/\",\"name\":\"PXI Systems\",\"description\":\"PXI, PXIe and Modular Test Equipment\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/pxisource.com\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"ru-RU\"},{\"@type\":\"Person\",\"@id\":\"https:\\\/\\\/pxisource.com\\\/#\\\/schema\\\/person\\\/bf03a76c93aa10f3b902e0131e55d3d0\",\"name\":\"pxisource\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"ru-RU\",\"@id\":\"https:\\\/\\\/pxisource.com\\\/wp-content\\\/litespeed\\\/avatar\\\/8285ca5b8d55d8ac1a1b67cca2d6fd2a.jpg?ver=1788090123\",\"url\":\"https:\\\/\\\/pxisource.com\\\/wp-content\\\/litespeed\\\/avatar\\\/8285ca5b8d55d8ac1a1b67cca2d6fd2a.jpg?ver=1788090123\",\"contentUrl\":\"https:\\\/\\\/pxisource.com\\\/wp-content\\\/litespeed\\\/avatar\\\/8285ca5b8d55d8ac1a1b67cca2d6fd2a.jpg?ver=1788090123\",\"caption\":\"pxisource\"},\"sameAs\":[\"https:\\\/\\\/pxisource.com\"],\"url\":\"https:\\\/\\\/pxisource.com\\\/ru\\\/blog\\\/author\\\/fuzhiqiang\\\/\"}]}<\/script>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"NI-DAQmx Functions Missing in LabVIEW: Causes and Solutions - PXI Source","description":"Learn how to fix missing NI-DAQmx functions, palettes, subVIs and MAX features after installing or upgrading LabVIEW and the NI-DAQmx driver.","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/pxisource.com\/ru\/blog\/ni-daqmx-functions-missing-in-labview\/","og_locale":"ru_RU","og_type":"article","og_title":"NI-DAQmx Functions Missing in LabVIEW: Causes and Solutions","og_description":"Learn how to fix missing NI-DAQmx functions, palettes, subVIs and MAX features after installing or upgrading LabVIEW and the NI-DAQmx driver.","og_url":"https:\/\/pxisource.com\/ru\/blog\/ni-daqmx-functions-missing-in-labview\/","og_site_name":"PXI Source","article_publisher":"https:\/\/www.facebook.com\/profile.php?id=61582573040385","article_published_time":"2026-07-23T11:58:19+00:00","article_modified_time":"2026-07-23T12:57:35+00:00","author":"pxisource","twitter_card":"summary_large_image","twitter_misc":{"\u041d\u0430\u043f\u0438\u0441\u0430\u043d\u043e \u0430\u0432\u0442\u043e\u0440\u043e\u043c":"pxisource","\u041f\u0440\u0438\u043c\u0435\u0440\u043d\u043e\u0435 \u0432\u0440\u0435\u043c\u044f \u0434\u043b\u044f \u0447\u0442\u0435\u043d\u0438\u044f":"9 \u043c\u0438\u043d\u0443\u0442"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/pxisource.com\/blog\/ni-daqmx-functions-missing-in-labview\/#article","isPartOf":{"@id":"https:\/\/pxisource.com\/blog\/ni-daqmx-functions-missing-in-labview\/"},"author":{"name":"pxisource","@id":"https:\/\/pxisource.com\/#\/schema\/person\/bf03a76c93aa10f3b902e0131e55d3d0"},"headline":"NI-DAQmx Functions Missing in LabVIEW: Causes and Solutions","datePublished":"2026-07-23T11:58:19+00:00","dateModified":"2026-07-23T12:57:35+00:00","mainEntityOfPage":{"@id":"https:\/\/pxisource.com\/blog\/ni-daqmx-functions-missing-in-labview\/"},"wordCount":1980,"commentCount":0,"articleSection":["knowledge base"],"inLanguage":"ru-RU","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/pxisource.com\/blog\/ni-daqmx-functions-missing-in-labview\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/pxisource.com\/blog\/ni-daqmx-functions-missing-in-labview\/","url":"https:\/\/pxisource.com\/blog\/ni-daqmx-functions-missing-in-labview\/","name":"NI-DAQmx Functions Missing in LabVIEW: Causes and Solutions - PXI Source","isPartOf":{"@id":"https:\/\/pxisource.com\/#website"},"datePublished":"2026-07-23T11:58:19+00:00","dateModified":"2026-07-23T12:57:35+00:00","author":{"@id":"https:\/\/pxisource.com\/#\/schema\/person\/bf03a76c93aa10f3b902e0131e55d3d0"},"description":"Learn how to fix missing NI-DAQmx functions, palettes, subVIs and MAX features after installing or upgrading LabVIEW and the NI-DAQmx driver.","breadcrumb":{"@id":"https:\/\/pxisource.com\/blog\/ni-daqmx-functions-missing-in-labview\/#breadcrumb"},"inLanguage":"ru-RU","potentialAction":[{"@type":"ReadAction","target":["https:\/\/pxisource.com\/blog\/ni-daqmx-functions-missing-in-labview\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/pxisource.com\/blog\/ni-daqmx-functions-missing-in-labview\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/pxisource.com\/"},{"@type":"ListItem","position":2,"name":"NI-DAQmx Functions Missing in LabVIEW: Causes and Solutions"}]},{"@type":"WebSite","@id":"https:\/\/pxisource.com\/#website","url":"https:\/\/pxisource.com\/","name":"\u0421\u0438\u0441\u0442\u0435\u043c\u044b PXI","description":"PXI, PXIe and Modular Test Equipment","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/pxisource.com\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"ru-RU"},{"@type":"Person","@id":"https:\/\/pxisource.com\/#\/schema\/person\/bf03a76c93aa10f3b902e0131e55d3d0","name":"pxisource","image":{"@type":"ImageObject","inLanguage":"ru-RU","@id":"https:\/\/pxisource.com\/wp-content\/litespeed\/avatar\/8285ca5b8d55d8ac1a1b67cca2d6fd2a.jpg?ver=1788090123","url":"https:\/\/pxisource.com\/wp-content\/litespeed\/avatar\/8285ca5b8d55d8ac1a1b67cca2d6fd2a.jpg?ver=1788090123","contentUrl":"https:\/\/pxisource.com\/wp-content\/litespeed\/avatar\/8285ca5b8d55d8ac1a1b67cca2d6fd2a.jpg?ver=1788090123","caption":"pxisource"},"sameAs":["https:\/\/pxisource.com"],"url":"https:\/\/pxisource.com\/ru\/blog\/author\/fuzhiqiang\/"}]}},"_links":{"self":[{"href":"https:\/\/pxisource.com\/ru\/wp-json\/wp\/v2\/posts\/33410","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/pxisource.com\/ru\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/pxisource.com\/ru\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/pxisource.com\/ru\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/pxisource.com\/ru\/wp-json\/wp\/v2\/comments?post=33410"}],"version-history":[{"count":12,"href":"https:\/\/pxisource.com\/ru\/wp-json\/wp\/v2\/posts\/33410\/revisions"}],"predecessor-version":[{"id":33423,"href":"https:\/\/pxisource.com\/ru\/wp-json\/wp\/v2\/posts\/33410\/revisions\/33423"}],"wp:attachment":[{"href":"https:\/\/pxisource.com\/ru\/wp-json\/wp\/v2\/media?parent=33410"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/pxisource.com\/ru\/wp-json\/wp\/v2\/categories?post=33410"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/pxisource.com\/ru\/wp-json\/wp\/v2\/tags?post=33410"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}