-
Notifications
You must be signed in to change notification settings - Fork 52
NI DAQMX System Configuration
- DAQmxGetAnalogPowerUpStates
- DAQmxGetDigitalLogicFamilyPowerUpState
- DAQmxGetDigitalPowerUpStates
- DAQmxGetDigitalPullUpPullDownStates
- DAQmxSetAnalogPowerUpStates
- DAQmxSetDigitalLogicFamilyPowerUpState
- DAQmxSetDigitalPowerUpStates
- DAQmxSetDigitalPullUpPullDownStates
int32 DAQmxGetAnalogPowerUpStates (const char deviceName[], const char channelName[], float64 *state, int32 channelType, ...);
Gets the power-up states for analog physical channels.
Input | ||
---|---|---|
Name | Type | Description |
deviceName | const char [] | Specifies the name to assign to the device. If unspecified, NI-DAQmx chooses the device name. |
channelName | const char [] | The physical channel to get the power-up state from. You can specify a list or range of channels. |
Output | ||
state | float64 * | The power-up state for the channel in channelName. |
channelType | int32 | The channel type for the channel in channelName. |
Value | Description | |
---|---|---|
DAQmx_Val_ChannelVoltage | Voltage | |
DAQmx_Val_ChannelCurrent | Current |
moreChannelsAndStates | any type (passed by value) | Pairs of additional channels and the states to get when the device powers up or when the device is reset. You must pass NULL at the end of the argument list. If you do not want to pass additional channels and states, the function call can be similar to the following example: DAQmxGetAnalogPowerUpStates ("Dev1", "Dev1/ao0", &state, DAQmx_Val_ChannelVoltage, NULL); If you pass additional channels and states, the function call can be similar to the following example: DAQmxGetAnalogPowerUpStates ("Dev1", "Dev1/ao0", &state_ao0, DAQmx_Val_ChannelVoltage, "Dev1/ao1", &state_ao1, DAQmx_Val_ChannelCurrent, NULL); |
Name | Type | Description |
---|---|---|
status | int32 | The error code returned by the function in the event of an error or warning. A value of 0 indicates success. A positive value indicates a warning. A negative value indicates an error. |
int32 DAQmxGetDigitalLogicFamilyPowerUpState (const char deviceName[], int32 *logicFamily);
Gets the digital logic family for a device.
Input | ||
---|---|---|
Name | Type | Description |
deviceName | const char [] | Specifies the name to assign to the device. If unspecified, NI-DAQmx chooses the device name. |
Output | ||
logicFamily | int32 * | The logic family of the device when it powers up. A logic family corresponds to voltage thresholds that are compatible with a group of voltage standards. Refer to device documentation for information on the logic high and logic low voltages for these logic families. |
Value | Description | |
---|---|---|
DAQmx_Val_2point5V | 2.5 V (compatible with CMOS signals) | |
DAQmx_Val_3point3V | 3.3 V (compatible with LVTTL and LVCMOS signals) | |
DAQmx_Val_5V | 5 V (compatible with TTL and CMOS signals) |
Name | Type | Description |
---|---|---|
status | int32 | The error code returned by the function in the event of an error or warning. A value of 0 indicates success. A positive value indicates a warning. A negative value indicates an error. |
int32 DAQmxGetDigitalPowerUpStates (const char deviceName[], const char channelName[], int32 *state, ...);
Gets the power-up states for digital physical lines.
Input | ||
---|---|---|
Name | Type | Description |
deviceName | const char [] | Specifies the name to assign to the device. If unspecified, NI-DAQmx chooses the device name. |
channelName | const char [] | The digital line or port to get the power-up state from. You can specify a list or range of channels. |
Output | ||
state | int32 * | The power-up state for the channel in channelName. |
Value | Description | |
---|---|---|
DAQmx_Val_High | High logic | |
DAQmx_Val_Low | Low logic | |
DAQmx_Val_Tristate | High-impedance state. You can select this state only on devices with bidirectional ports, and you can select it only for entire ports. You cannot select this state for dedicated digital output lines. |
moreChannelsAndStates | any type (passed by value) | Pairs of additional channels and the states to get when the device powers up or when the device is reset. You must pass NULL at the end of the argument list. If you do not want to pass additional channels and states, the function call can be similar to the following example: DAQmxGetDigitalPowerUpStates ("Dev1", "Dev1/do0", &state, NULL); If you pass additional channels and states, the function call can be similar to the following example: DAQmxGetDigitalPowerUpStates ("Dev1", "Dev1/do0", &state_do0, "Dev1/do1", &state_do1, NULL); |
Name | Type | Description |
---|---|---|
status | int32 | The error code returned by the function in the event of an error or warning. A value of 0 indicates success. A positive value indicates a warning. A negative value indicates an error. |
int32 DAQmxGetDigitalPullUpPullDownStates (const char deviceName[], const char channelName[], int32 *state, ...);
Gets the resistor level for lines when they are in tristate logic.
Input | ||
---|---|---|
Name | Type | Description |
deviceName | const char [] | Specifies the name to assign to the device. If unspecified, NI-DAQmx chooses the device name. |
channelName | const char [] | The digital line or port to get the power-up state from. You can specify a list or range of channels. |
Output | ||
state | int32 * | The power-up state for the channel in channelName. |
Value | Description | |
---|---|---|
DAQmx_Val_PullUp | High logic | |
DAQmx_Val_PullDown | Low logic |
moreChannelsAndStates | any type (passed by value) | Pairs of additional channels and the states to get when the device powers up or when the device is reset. You must pass NULL at the end of the argument list. If you do not want to pass additional channels and states, the function call can be similar to the following example: DAQmxGetDigitalPullUpPullDownStates ("Dev1", "Dev1/do0", &state, NULL); If you pass additional channels and states, the function call can be similar to the following example: DAQmxGetDigitalPullUpPullDownStates ("Dev1", "Dev1/do0", &state_do0, "Dev1/do1", &state_do1, NULL); |
Name | Type | Description |
---|---|---|
status | int32 | The error code returned by the function in the event of an error or warning. A value of 0 indicates success. A positive value indicates a warning. A negative value indicates an error. |
int32 DAQmxSetAnalogPowerUpStates (const char deviceName[], const char channelNames[], float64 state, int32 channelType, ...);
Updates the states that analog physical channels on a device are set to when the device powers up or when the device is reset. Power-up states are stored in EEPROMs that you can write to only a limited number of times. Therefore, you should use this function as infrequently as possible. This function writes to the EEPROM only if a setting you request is different from the one currently stored on the EEPROM. This function writes power-up states in sequential order. Therefore, if a physical channel has multiple entries, the last entry is used.
Input | ||
---|---|---|
Name | Type | Description |
deviceName | const char [] | Specifies the name to assign to the device. If unspecified, NI-DAQmx chooses the device name. |
channelNames | const char [] | The physical channel to modify. You can specify a list or range of channels. |
state | float64 | The power-up state to set for the channel(s) in channelNames. |
channelType | int32 | The channel type for the channel(s) in channelNames. |
Value | Description | |
---|---|---|
DAQmx_Val_ChannelVoltage | Voltage output. You can set voltage power-up states only for physical channels that support voltage output. | |
DAQmx_Val_ChannelCurrent | Current output. You can set current power-up states only for physical channels that support current output. |
moreChannelsStatesAndTypes | any type (passed by value) | Combinations of additional channels and states and types to set the channels to when the device powers up or when the device is reset. You must pass NULL at the end of the argument list. If you do not want to pass additional channels and states, the function call can be similar to the following example: DAQmxSetAnalogPowerUpStates ("Dev1", "Dev1/ao0", 0.0, DAQmx_Val_ChannelVoltage, NULL); If you pass additional channels and states, the function call can be similar to the following example: DAQmxSetAnalogPowerUpStates ("Dev1", "Dev1/ao0", 0.0, DAQmx_Val_ChannelVoltage, "Dev1/ao1", 1.0, DAQmx_Val_ChannelCurrent, NULL); |
Name | Type | Description |
---|---|---|
status | int32 | The error code returned by the function in the event of an error or warning. A value of 0 indicates success. A positive value indicates a warning. A negative value indicates an error. |
int32 DAQmxSetDigitalLogicFamilyPowerUpState (const char deviceName[], int32 logicFamily);
Sets the digital logic family to use when the device powers up.
Input | ||
---|---|---|
Name | Type | Description |
deviceName | const char [] | Specifies the name to assign to the device. If unspecified, NI-DAQmx chooses the device name. |
logicFamily | int32 | Specifies the logic family to set the device to when it powers up. A logic family corresponds to voltage thresholds that are compatible with a group of voltage standards. Refer to device documentation for information on the logic high and logic low voltages for these logic families. |
Value | Description | |
---|---|---|
DAQmx_Val_2point5V | 2.5 V (compatible with CMOS signals) | |
DAQmx_Val_3point3V | 3.3 V (compatible with LVTTL and LVCMOS signals) | |
DAQmx_Val_5V | 5 V (compatible with TTL and CMOS signals) |
Name | Type | Description |
---|---|---|
status | int32 | The error code returned by the function in the event of an error or warning. A value of 0 indicates success. A positive value indicates a warning. A negative value indicates an error. |
int32 DAQmxSetDigitalPowerUpStates (const char deviceName[], const char channelNames[], int32 state, ...);
Updates the state that digital physical channels on static DIO devices are set to when the device powers up or when the device is reset. Power-up states are stored in EEPROMs that you can write to only a limited number of times. Therefore, you should use this function as infrequently as possible. This function writes to the EEPROM only if a setting you request is different from the one currently stored on the EEPROM. This function writes power-up states in sequential order. Therefore, if a physical channel has multiple entries, the last entry is used.
Input | ||
---|---|---|
Name | Type | Description |
deviceName | const char [] | Specifies the name to assign to the device. If unspecified, NI-DAQmx chooses the device name. |
channelNames | const char [] | The digital line or port to modify. You cannot set power-up states for dedicated digital input lines. You can specify a list or range of channels. |
state | int32 | The power-up state to set for the channel(s) in channelNames. |
Value | Description | |
---|---|---|
DAQmx_Val_High | High logic | |
DAQmx_Val_Low | Low logic | |
DAQmx_Val_Tristate | High-impedance state. You can select this state only on devices with bidirectional ports, and you can select it only for entire ports. You cannot select this state for dedicated digital output lines. |
moreChannelsAndStates | any type (passed by value) | Pairs of additional channels and the states to set the channels to when the device powers up or when the device is reset. You must pass NULL at the end of the argument list. If you do not want to pass additional channels and states, the function call can be similar to the following example: DAQmxSetDigitalPowerUpStates ("Dev1", "Dev1/do0", DAQmx_Val_High, NULL); If you pass additional channels and states, the function call can be similar to the following example: DAQmxSetDigitalPowerUpStates ("Dev1", "Dev1/do0", DAQmx_Val_High, "Dev1/do1", DAQmx_Val_Tristate, NULL); |
Name | Type | Description |
---|---|---|
status | int32 | The error code returned by the function in the event of an error or warning. A value of 0 indicates success. A positive value indicates a warning. A negative value indicates an error. |
int32 DAQmxSetDigitalPullUpPullDownStates (const char deviceName[], const char channelNames[], int32 state, ...);
Sets the resistor level to pull up or pull down for lines when they are in tristate logic. Power-up states are stored in EEPROMs that you can write to only a limited number of times. Therefore, you should use this function as infrequently as possible. This function writes to the EEPROM only if a setting you request is different from the one currently stored on the EEPROM. This function writes power-up states in sequential order. Therefore, if a physical channel has multiple entries, the last entry is used.
Input | ||
---|---|---|
Name | Type | Description |
deviceName | const char [] | Specifies the name to assign to the device. If unspecified, NI-DAQmx chooses the device name. |
channelNames | const char [] | The digital line or port to modify. You cannot set power-up states for dedicated digital input lines. You can specify a list or range of channels. |
state | int32 | The power-up state to set for the channel(s) in channelNames. |
Value | Description | |
---|---|---|
DAQmx_Val_PullUp | High logic | |
DAQmx_Val_PullDown | Low logic |
moreChannelsAndStates | any type (passed by value) | Pairs of additional channels and the states to set the channels to when the device powers up or when the device is reset. You must pass NULL at the end of the argument list. If you do not want to pass additional channels and states, the function call can be similar to the following example: DAQmxSetDigitalPullUpPullDownStates ("Dev1", "Dev1/do0", DAQmx_Val_PullUp, NULL); If you pass additional channels and states, the function call can be similar to the following example: DAQmxSetDigitalPullUpPullDownStates ("Dev1", "Dev1/do0", DAQmx_Val_PullUp, "Dev1/do1", DAQmx_Val_PullDown, NULL); |
Name | Type | Description |
---|---|---|
status | int32 | The error code returned by the function in the event of an error or warning. A value of 0 indicates success. A positive value indicates a warning. A negative value indicates an error. |
Creating and Setting Up a gRPC Server
Session Utilities API Reference
gRPC API Differences From C API
Sharing Driver Sessions Between Clients
C API Docs
NI-DAQmx
- gRPC API Differences From C API
- Task Configuration And Control
- Channel Configuration And Creation
- Timing
- Triggering
- Read Functions
- Write Functions
- Export Hardware Signals
- Scale Configuration
- Internal Buffer Configuration
- Advanced Functions
- System Configuration
- Error Handling
- Buffer Attributes
- Calibration Info Attributes
- Channel Attributes
- Device Attributes
- Export Signal Attributes
- Persisted Channel Attributes
- Persisted Scale Attributes
- Persisted Task Attributes
- Physical Channel Attributes
- Read Attributes
- Scale Attributes
- System Attributes
- Task Attributes
- Timing Attributes
- Trigger Attributes
- Watchdog Attributes
- Write Attributes
NI-DCPOWER
- Setup Functions
- Configure Functions
- Measurement Functions
- Control Functions
- Trigger And Event
- Attribute Functions
- Query Functions
- Calibration Functions
- Utility Functions
- Supported Device
- Source Attributes
- Transient Attributes
- Voltage Attributes
- Current Attributes
- Pulse Voltage Attributes
- Pulse Current Attributes
- Cutoff Attributes
- Measurement Attributes
- Trigger Attributes Functions
- Event Attributes
- Advanced Attributes
- Inherent Ivi Attributes
- Supported Device Attributes
NI-DIGITAL PATTERN DRIVER
- Init And Close Functions
- Session Locking Functions
- Utility Functions
- Error Handling Functions
- Calibration Functions
- Attributes Functions
- Pin Map Functions
- Low Level Functions
- Low Level Action Functions
- Pin Control Functions
- Static IO Functions
- Clock Generator Functions
- Levels And Timing Functions
- TDR Functions
- PPMU Configuration Functions
- DC Voltage Functions
- DC Current Functions
- PPMU Action Functions
- Pattern Configuration Functions
- Pattern Action Functions
- History Ram Functions
- Source Memory Functions
- Capture Memory Functions
- Triggers And Events Functions
- Conditional Jump Trigger Functions
- Sequencer Flag Functions
- Sequencer Register Functions
- Match Fail Combination Functions
- Pattern Results Functions
- Sort Results Functions
- Frequency Measurement Functions
- IVI Inherent Attributes
- Specific Driver Information Attributes, Read Only
- Driver Setup Information Attributes
- Device Attributes
- Pin Control Attributes
- Level Configuration Attributes
- Trigger Configuration Attributes
- PPMU Attributes
- Patterns Attributes
- Pattern Opcode Event Attributes
- Timing Offset Attributes
- Keep Alive Attributes
- Frequency Measurement Attributes
- Clock Generator Attributes
- History RAM
- Synchronization Attributes
- TDR Endpoint Termination Attributes
NI-FGEN
- Setup Functions
- Configuration Functions
- Standard Output Functions
- Arbitrary Waveform Output Functions
- Arbitrary Sequence Output Functions
- Incremental Waveform Write Functions
- Configure Clock Functions
- Trigger And Syncronizations Functions
- 5404 Routing Functions
- Script Output Functions
- Configure Onboard Signal Processing Functions
- Configure Peer To Peer Functions
- Attribute Functions
- Waveform Control Functions
- Error Functions
- Output Attributes
- Arbitrary Waveform Attributes
- Data Transfer Attributes
- Onboard Signal Processing Attributes
- Peer To Peer Attributes
- Standard Function Attributes
- Clock Attributes
- Event Attributes
- Triggering Attributes
- Instrument Specific Attributes
- Inherent IVI Attributes
- 5401 5411 5431
NI-RFmx Bluetooth
- gRPC API Differences From C API
- General Functions
- Configuration Functions
- Set And Get Attribute Functions
- Fetch Results Functions
- Utility Functions
- Build String Functions
- Advanced Functions
- General Attributes
- Trigger Attributes
- Packet Attributes
- Auto Detect Signal Attributes
- Modacc Attributes
- ACP Attributes
- Twenty dB Attributes
- Frequency Range Attributes
- TXP Attributes
- Advanced Attributes
NI-RFmx NR
- gRPC API Differences From C API
- General Functions
- Configuration Functions
- Set And Get Attributes Functions
- Fetch Results Functions
- Utility Functions
- Build String Functions
- Advanced Functions
- General Attributes
- Trigger Attributes
- Signal Detection Attributes
- Component Carrier Attributes
- List Attributes
- Modacc Attributes
- ACP Attributes
- CHP Attributes
- OBW Attributes
- SEM Attributes
- TXP Attributes
- Pvt Attributes
- Advanced Attributes
NI-RFmx LTE
- gRPC API Differences From C API
- General Functions
- Configuration Functions
- Ch Configuration Functions
- NB IoT Configuration Functions
- ModAcc Configuration Functions
- ACP Configuration Functions
- CHP Configuration Functions
- OBW Configuration Functions
- SEM Configuration Functions
- PVT Configuration Functions
- SlotPhase Configuration Functions
- SlotPower Configuration Functions
- Set And Get Attribute Functions
- ModAcc Fetch Functions
- ACP Fetch Functions
- CHP Fetch Functions
- OBW Fetch Functions
- SEM Fetch Functions
- PVT Fetch Functions
- SlotPhase Fetch Functions
- SlotPower Fetch Functions
- Utility Functions
- Build String Functions
- Advanced Functions
- General Attributes
- Trigger Attributes
- Component Carrier Attributes
- ModAcc Attributes
- ACP Attributes
- CHP Attributes
- OBW Attributes
- SEM Attributes
- PVT Attributes
- SlotPhase Attributes
- SlotPower Attributes
- Advanced Attributes
NI-RFmx SpecAn
- gRPC API Differences From C API
- General Functions
- Configuration Functions
- Set And Get Attribute Functions
- Read Functions
- Fetch Functions
- Utility Functions
- Marker Functions
- Build String Functions
- Advanced Functions
- General Attributes
- Trigger Attributes
- ACP Attributes
- Cdf Attributes
- CHP Attributes
- Fcnt Attributes
- Harm Attributes
- OBW Attributes
- SEM Attributes
- Spectrum Attributes
- Spur Attributes
- TXP Attributes
- AMPM Attributes
- Dpd Attributes
- IQ Attributes
- IM Attributes
- NF Attributes
- Phasenoise Attributes
- PAVT Attributes
- Advanced Attributes
NI-RFmx WLAN
- gRPC API Differences From C API
- General Functions
- Configuration Functions
- Set And Get Attribute Functions
- Fetch DSSS ModAcc Functions
- Fetch OFDM ModAcc Functions
- Fetch SEM Functions
- Fetch TXP Functions
- Fetch PowerRamp Functions
- Utility Functions
- Build String Functions
- Advanced Functions
- General Attributes
- Trigger Attributes
- OFDM Attributes
- Auto Detect Signal Attributes
- DSSS ModAcc Attributes
- OFDM ModAcc Attributes
- SEM Attributes
- TXP Attributes
- PowerRamp Attributes
- Advanced Attributes
NI-RFSA
- General Functions
- Configuration Functions
- Acquisition Functions
- Utility Functions
- Calibration Functions
- General Attributes
- Vertical Attributes
- Signal Path Attributes
- Acquisition Attributes
- Acquisition Attributes
- Triggers Attributes
- Events Attributes
- Device Characteristics Attributes
- Peer To Peer Streaming Attributes
- Configuration List Attributes
- Inherent IVI Properties Attributes
- De-embedding Attributes
- Self Calibration Attributes
- Factory Calibration Attributes
- External Alignment Attributes
- Device Specific Attributes
NI-RFSG
- General Functions
- Generation Configuration
- Utility Functions
- Calibration Functions
- Arb Attributes
- Clock Attributes
- Configuration List Attributes
- De-embedding Attributes
- Device Characteristics Attributes
- Device Specific Attributes
- Events Attributes
- External Calibration Attributes
- Inherent IVI Attributes Attributes
- IQ Impairment Attributes
- Load Configurations Attributes
- Modulation Attributes
- Obsolete Attributes
- Peer To Peer Attributes
- RF Attributes
- Self Calibration Attributes
- Triggers Attributes
NI-SCOPE
- Setup Functions
- Configure Functions
- Attribute Functions
- Acquisition Functions
- Measurement Functions
- Calibrate Functions
- Utility Funcitons
- Error Handling Functions
- IVI Compliance Or Obsolete Functions
- Vertical Attributes
- Horizontal Attributes
- Trigger Attributes
- Clocking Attributes
- Synchronization Attributes
- Acquisition Attributes
- Waveform Measurements Attributes
- Onboard Signal Processing Attributes
- Peer To Peer Streaming Attributes
- Device Attributes
- IVI Or Obsolete Attributes
- Instrument Capabilities Attributes
- If Digitizer Attributes
NI-XNET
- gRPC API differences from C APIs
- General Functions
- Cluster Properties
- Database Properties
- Device Properties
- ECU Properties
- Frame Properties
- Interface Properties
- LIN Schedule Entry Properties
- LIN Schedule Properties
- PDU Properties
- Session Ethernet Properties
- Session Frame Properties
- Session Interface Properties
- Session Properties
- Session SAE J1939 Properties
- Signal Properties
- Subframe Properties
- System Properties
- IP-Stack Functions
- Socket Options
- Socket Functions