Skip to content

NI DAQMX Getting And Setting Attributes

Jump to bottom
astarche edited this page Sep 16, 2021 · 4 revisions

Getting and Setting Attributes

Unlike the C API, the DAQmx gRPC API only supports generic functions for getting and setting attributes. You can see a sample of getting an attribute in this Python example that uses GetTaskAttributeUInt32(), and a sample of setting an attribute in this Python example that uses SetTimingAttributeString().

Undefined attributes

The DAQmx gRPC API only allows accessing attributes defined in the proto file for the given category and datatype. This behavior can be overridden by adding "feature_toggles": { "nidaqmx.allow_undefined_attributes": true } to the server configuration file. This can be used to access attributes added in a later version. CAUTION: when allow_undefined_attributes is enabled, the client can request attributes for the incorrect datatype. The implementation of this is undefined behavior in the server's C API implementation. Only use this toggle when you can ensure that clients only access attributes by the correct datatype.

Table of Contents

Home

Internal Development

Creating and Setting Up a gRPC Server

Server Security Support

Creating a gRPC Client

gRPC Client Examples

Session Utilities API Reference

Driver Documentation

gRPC API Differences From C API

Sharing Driver Sessions Between Clients

C API Docs
NI-DAQmx
NI-DCPOWER
NI-DIGITAL PATTERN DRIVER
NI-DMM
NI-FGEN
NI-FPGA
NI-RFmx Bluetooth
NI-RFmx NR
NI-RFmx WCDMA
NI-RFmx GSM
NI-RFmx CDMA2k
NI-RFmx Instr
NI-RFmx LTE
NI-RFmx SpecAn
NI-RFmx TD-SCDMA
NI-RFmx WLAN
NI-RFSA
NI-RFSG
NI-SCOPE
NI-SWITCH
NI-TCLK
NI-XNET
Clone this wiki locally