PXI and Instrumentation Idea Exchange

Community Browser
cancel
Showing results for 
Search instead for 
Did you mean: 
Post an idea

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.

HI,

I want to exchange opinions to evaluate a possible solution for my project. 
The system consists of a PC (NI LabVIEW 2017, with a certain IP address) to
which the PXI is connected (with its own IP address). A Programmable Logic
device, perhaps an S7 PLC, will be connected to the PXI via an Ethernet port
(No acquisition module, like NI-Profibus) with which it is possible to
communicate with the TCP/IP protocol. Since the PLC is recognized as a
Network Device (and not as a Physical Device), I ask: - How can I interface Labview with the PLC if through NI MAX I can't create
Acquisition Tasks that I can import into the project? - Are there any solutions for Network Devices? - Or, can it be correct to instantiate the TCP/IP protocol from Labview, and
using the IP address and Port, try to communicate directly with the PLC (which
will still be connected to the PXI)? Thank you in advance.
Best Regards

Giuseppe_Vitolo_NI

 

 

A Tunderbolt 3 PXIe controller card for direct connection to a PC based Thunderbolt 3 port, functioning much as the MXIe interfacing does now.