DAQmx Physical Channels Missing

[frasier.mike@dwpenergysolutions.com]

Any DAQmx module that I install into the cDAQ-9174 are not visible in the DAQmx Physical Channel control on the front panel.  The installed modules ARE visible and controllable in NI MAX however.  What makes this even stranger is that there are 2 modules (9211 & 9205) that I have been using on my most recent program that ARE visible to LV on the front panel as physical channels.  But any others I plug in don't show up.  I've tried multiple 9174's, USB cables and even computers, rebooted PC and reset 9174.  The symptom is always the same.  I've done a lot of cDAQ programming and never seen this before.  I recently upgraded to NI-DAQmx 14.5 and I'm using LabView 2012.  Maybe I should uninstall 14.5 and go back to whatever version was running before?

Any help would be greatly appreciated.

Thank You-

[protocoled]

Try right clicking on the physical channel control and select 'I/O Name Filtering' and make sure something didn't get deselected accidentally. If that doesn't work, I'd do a driver reinstall. 

[Bob_Schor]

---

frasier.mike@dwpenergysolutions.com wrote:

Any DAQmx module that I install into the cDAQ-9174 are not visible in the DAQmx Physical Channel control on the front panel.  ...  I recently upgraded to NI-DAQmx 14.5 and I'm using LabView 2012.  Maybe I should uninstall 14.5 and go back to whatever version was running before?

---

LabVIEW is (un?)-reasonably Version-Specific.  You seemed to be working find with LabVIEW 2012 and the 2012 Drivers, and when you upgraded the Drivers to those shipping with LabVIEW 2014 (and maybe even 2014 SP1), "things broke".

I've not done much with RIOs, but I do run LabVIEW RT with PXI systems, and know that if I change a LabVIEW Version, I also need to change the software on my PXIs to match the LabVIEW Version I'm using for Development.  If I have multiple LabVIEW Versions installed, I can't develop in (say) LabVIEW 2012 and deploy to a PXI configured for LabVIEW 2014, and vice versa.

The "bad news" is that you might find that trying to "uninstall 14.5 and go back to whatever version was running before" might not work, and might leave you with a system that is "more broken" than before.  Should that happen, open Control Panel, go to Programs and Features, find NI Software, and do "Remove All".  You will then need to (re-)install LabVIEW 2012, the LabVIEW 2012 Drivers, and any other "LabVIEW Pieces" and try again.  This usually works (and I've done quite a few of these, both for myself and my colleagues) -- only rarely will you have to resort to the "Guaranteed To Fix All LabVIEW Installation Problems" method that begins "Step 1 -- Format the C: Drive." (LabVIEW 2017 installation on two of my Windows 10 systems necessitated this Method for me ...).

Bob Schor

[frasier.mike@dwpenergysolutions.com]

Thank you both for your insight.  It turns out I need to apply an I/O naming filter to the physical channel control in order for the control to see the new module.  And every new control I put on the front panel defaults Analog Input.  I don't remember having to do this before v14.5.  The physical channel control was always polymorphic in that it would see all modules.  I also don't see an option in the filter menu for all types of modules.  Maybe this is a new "feature" with 14.5 or just LV2012 not playing nicely with 14.5.  Either way I now have a workaround.

Thanks again for your help!

[tsf2018]

Thanks for your response - couple of hours of shaking my fist at the screen was put to rest here. However, this "non-polymorphic" issue is really puzzling.  I had a built a program structure using an array of channels (AI, AO, DI, DO) which works during testing. ie. One can manually input any channel to the control, rather it is the auto-populate list that doesn't fill. Developer side, no problems, I know the channel addresses. User side? Huge problem. Any idea of a way to auto-populate those lists with my 4 different devices to save me rebuilding the entire structure? Is there any way to disable I/O name filtering?

[tsf2018]

Found a workaround - ChanSigType is the driving control property.  This can be programmatically adjusted (eg via a property node). In my case a value of "7" added AI, AO, DI, DO channels to the list. Apologies for the res, and thanks for the tips.