[26.0] Add CreateAICalculatedPowerChan API metadata#1214
Conversation
HSKhor-NI
requested review from
astarche,
maxxboehme and
reckenro
as code owners
| THERMOCOUPLE_TYPE1_A_TYPE_TC = 16208; | ||
| THERMOCOUPLE_TYPE1_C_TYPE_TC = 16209; |
There was a problem hiding this comment.
The thermocouple type additions are unrelated to the goal of this PR which is to add the CreateAICalculatedPowerChannel API. @maxxboehme , @astarche , is there an expected way to to limit the API additions to a specific feature or is the expected process to update the whole DAQmx API at once?
There was a problem hiding this comment.
@HSKhor-NI , if the other additions for the DAQmx API beyond Calculated Power Channel remain in this PR, I think the title should be changed to reflect that. Perhaps "Update DAQmx API metadata to 26.0 to pull in the Calculated Power Channel API"
There was a problem hiding this comment.
Renaming the PR was previously suggested for nidaqmx-python: ni/nidaqmx-python#876
| #define DAQmx_Dev_IDPin_PinNames 0x31F1 // Indicates the names of all the ID Pins on this device. | ||
| #define DAQmx_Dev_IDPin_PinStatuses 0x31F2 // Indicates status of each ID Pin. | ||
| #define DAQmx_Dev_IDPin_MemFamilyCodes 0x31F3 // Indicates the family code of the memory connected to each ID Pin. Each array element corresponds to an ID Pin. The array contains 0 for each ID Pin with no memory connected. | ||
| #define DAQmx_Dev_IDPin_MemSerialNums 0x31F4 // Indicates the serial number of the memory connected to each ID Pin. Each array element corresponds to an ID Pin. The array contains an empty string for each ID Pin with no memory connected. | ||
| #define DAQmx_Dev_IDPin_MemSizes 0x31F5 // Indicates the size in bytes of the memory connected to each ID Pin. Each array element corresponds to an ID Pin. The array contains 0 for each ID Pin with no memory connected. |
There was a problem hiding this comment.
Note: The update to the comments here are unrelated to the Calculated Power Channel API additions.
| #define DAQmx_Val_A_Type_TC 16208 // A | ||
| #define DAQmx_Val_C_Type_TC 16209 // C |
There was a problem hiding this comment.
Note: The addition of these thermocouple type enums are unrelated to the Calculated Power Channel API additions that led to this PR.
| int32 __CFUNC DAQmxAdjust4305Cal (CalHandle calHandle, float64 refVoltage); | ||
| int32 __CFUNC DAQmxAdjust4309Cal (CalHandle calHandle, float64 refVoltage); | ||
| int32 __CFUNC DAQmxAdjust4310Cal (CalHandle calHandle, float64 refVoltage); | ||
| int32 __CFUNC DAQmxAdjust4311Cal (CalHandle calHandle, float64 rangeMax, float64 rangeMin, float64 refVoltage); |
There was a problem hiding this comment.
The addition of the DAQmxAdjust4311Cal function is independent from the addition of the Calculated Power Channel API but was present in the 2025 Q4 DAQmx C API.
| int32 __CFUNC DAQmxGet9320CalAdjustPoints(CalHandle calHandle, float64* adjustmentPoints, uInt32 bufferSize); | ||
| int32 __CFUNC DAQmxAdjust9320Cal(CalHandle calHandle, const char channelNames[], float64 value); |
There was a problem hiding this comment.
These cal function additions are unrelated to the Calculated Power Channel API additions.
5 participants
What does this Pull Request accomplish?
Pull in new metadata file generated in
grpc-device-scrapigenthat contain metadata for DAQmxCreateCalculatedPower API.Why should this Pull Request be merged?
To support
DAQmxCreateCalculatedPowercall through grpc interpreter in python APIWhat testing has been done?
nidaqmx.protothat contain DAQmxCreateCalculatedPower APInidamx-pythonto generate grpc_interpretr with updated API.