09-06-2007 01:43 AM
09-06-2007 11:37 AM
09-09-2007 12:51 PM
Hello Luis,
Your suggestions works fine. Although I am lazy and used a variation on option 2: CONSTANT NAME LENGTH
But for you and others: I am still looking. Because after finding the control, I tried to dimm it - together with other acuisition-parameter-controls - when I start the actual NI-DAXmx task. Where all the other parameter-controls are dimmed, this NewPhysChannelAICtrl is not dimmed and is active.
Thanks Jos
09-10-2007 04:09 PM
09-11-2007 10:23 AM
09-11-2007 01:39 PM
Sorry Jeff,
I have changed my source code as suggested by Luis and this works. And as I just installed DAQmx 8.5, yous suggestion won't work. So Luis does get the top grade.
For both and all others, I have a portable at home with only virtual devices. I have a desktop at work with some virtual devices, sometimes a PCI-6110 but always its virtual version, and sometimes an USB device. And when I port an application to a laboratory, I only have the real hardware. So the use of 'Dev#' becomes very confusing. I advise developers to make for themselves a drop-down that gives a choice from all available interfaces by product type (i.e. PCI-6110 and PCI-6111 and PCI-6032E). And from the choice for one interface, you can add a second for selection of input or output channels. I just made a start and found already 'DAQmxGetSystemInfoAttribute' for a getting a string with 'Dev' identifiers, and 'DAQmxGetDeviceAttribute (DAQmx_Dev_ProductType)' for conversion of each 'Dev' to a 'readable' identifier.
Thanks all, Jos
07-19-2017 09:40 AM
Anyone who is using DAQmx version 16.1, the following code worked for me:
NIDAQmx_SetPhysChanCtrlAttribute(panelHandle,controlName, NIDAQmx_IOCtrl_Dimmed, 1); // dims the control