Have an idea for new PXI hardware or software features?
Browse by label or search in the PXI and Instrumentation Idea Exchange to see if your idea has previously been submitted. If your idea exists be sure to vote for the idea by giving it kudos to indicate your approval!
If your idea has not been submitted click Post New Idea to submit a product idea. Be sure to submit a separate post for each idea.
Watch as the community gives your idea kudos and adds their input.
As NI R&D considers the idea, they will change the idea status.
Give kudos to other ideas that you would like to see implemented!
Using RT Utilities or RAD works well to image and deploy when you have like systems. What about when there are many deployments to maintain, each with the same RTEXE and same driver sets, but there are many different models of PXI RT embedded controllers throughout these deployments? What if it was possible to install software to a SIMULATED PXI in MAX as well as to deploy executables and support files to? This would allow for the creation of an image for a specific model controller, without having that controller directly in hand. (BTW, I'm still on LV2013 SP1 for the next few months. I have 42 RT embedded targets that include a mix of the following models: 8196, 8104, 8102, 8115, 8100, 8135, 8820, 8840, and 9139. The same RTEXE runs on all of these. The end-user can customize I/O at run-time and therefore these deployments range quite widely in performance needs and these deployments were created over several years, hence the wide range of embedded controller vintages and performance levels. And, for my scenario, these controllers are not directly accessible through the network, as they are connected to a local network specific to that deployment location. There is a Windows host machine that has access to this local network as well as to the building network.)
I have an upcoming requirement for connecting two test equipment racks so that one contains a control computer and PXI chassis and the second rack contains another PXI chassis. The control computer will include a two-port MXI Master PXIe card, and each PXI chassis an MXI Slave card.
The problem arises that there is no means to bring out an MXI cable from one rack to the other, except through a hole, rather than a proper feed-through connector.
I can design and build a back-to-back pair of MXI matching Molex connectors on a small PCB, but a qualified, tested, and approved OEM solution would be much better.
Proposition: make an SLSC chassis controlled over EtherCAT. Would be a great addition to a realtime HiL system with a lot of IO to be switched/faulted by providing deterministic switch capabilities. It's not always feasible to buy that many PXI switch cards...
E.g. our DUTs have usually about 100 IO lines (some even over 150), each of which have to be tested for open, short to another one, self-short (in case of differential lines) etc. We usually don't have a requirement to switch very fast, but we'll welcome a possibility to switch in predictable time.
It would be great if NI could release a multiplexer (at least 1:8 ideally) based on MEMS switches, which allow for signals from real DC to ~ 10GHz (I'm thinking Analog Devices ADGM1304) and have ~ 1e9 endurance, about 100 times better than standard relays.
I would like to request a pass-through connector for mounting on a panel of a test fixture or a screen room. This connector would be similar to the connector on the CB-68LPR breakout board and would mount to a panel. The other side of the connector would be either wirewrap/solder pins or another connector for connecting another cable.
Please submit your feedback regarding our existing PXI products and ideas for new products as well. If your idea has been previously submitted, be sure to vote for the idea by giving it kudos to indicate your approval!