Jump to content

Recommendations for work with PXI Systems.

Óscar Gómez

By Óscar Gómez,
in LabVIEW General

Followers 1

Recommended Posts

Óscar Gómez

Óscar Gómez 0

Posted
Posted (edited)

In a few days my team and me will start a project and I'm a little anxious because I've never work with PXI Systems... If anyone want to tell me a tip, recommendation or something about your experience with this systems, you'll welcome. I'm one of the developers in the crew!.

I've experience with cRIO and cDAQ. :thumbup1:

OG

CLAD.png

Edited by Óscar Gómez
Link to post
hooovahh

hooovahh 773

Posted
Posted

You didn't specify the operating system on your PXI but I assume it is RT, it can be Windows as well at which point developing on the system should be pretty easy.  If you're already familiar with RT on cRIO and cDAQ, then PXI should be no problem.  You configure the devices in MAX just like any other remote device, and can setup virtual channels or other basic things there.  Then in the project you add your target, write your VIs and run them there which get deployed.  There really isn't any other considerations between a cRIO and PXI.  If anything I'd say the cRIO can be more complicated due to the FPGA in the mix.  Afterwards you create a build of your application and deploy it.

EDIT:  Oh and if you really want to test deploying to RT devices you can load up a virtual machine and deploy to it as if it were a PXI with no hardware.

Link to post

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
Followers 1
Go to topic listing

  • Similar Content

    • SayMaster
      3rd party PXI chassis problem NI MAX
      By SayMaster
      Hello fellow LabVIEWers,
      I am trying to get a self developed PXI chassis up and running - with some problems.
       
      As this is this my first time developing a chassis, some general questions about 3rd party chassis:
      If I want to get a 3rd party PXI chassis up and running with MAX I just need to add the right description files into the right folder? otherwise the chassis will be recognized as "undefined"? but will still work - except triggers?  
      Whats my status right now?
      Chassis is connected via PCIe 8361 - PXIe 8360 and the Connection seems to work Chassis seems to work and inserted cards get recognized by MAX and "self test" works Chassis seems to get recognized with the Keysight Resource Manager (I installed it and selected it in NI MAX) no unknown devices in windows device manager (so the NI SMBus Controller gets recognized correctly)  
      btw my actual SW installation:
      PXI Services 17.5.1
      MAX 17.5
      VISA 17.5
      DAQ 17.5
      LV 17f2


      I am open for any suggestions and tipps!
       
       
      br
      SayMaster
    • danren924
      AIT MIL-STD-1553 PXI card not talking to LabVIEW
      By danren924
      I have an AIT MIL-STD-1553 PXI card, and I am trying to control it using LabVIEW. The card shows up in MAX, and a Test Panel is able to communicate with it, as shown in the attached images. Further, if I open a VISA session with the instrument, it seems to be okay. (I have only tried doing a VISA Open and VISA Close, resulting in no error. Since I don't know any other VISA commands to this instrument, and since it does not seem to speak SCPI, I have been limited to simply opening and closing the VISA session.) However, when I try to do a simple Initialize using the AIT LabVIEW vis, I get an error code -1, stating that there is "No Hardware Found". This simple vi is shown in the other attachment. I have also tried different "network path in", and "board index in" values, without success. Any time I change the network path in to anything but "local", I get an error code -5, stating that "Remote network connection not supported by this hardware".
      I have verified that the latest AIT firmware is loaded on the card. I'm running the AIT LabVIEW vilib components, and LabVIEW 2015.
      Any help would be greatly appreciated.
      Thanks.
      Dan



    • Manudelavega
      Choosing an RT Solution : cRIO or PXI
      By Manudelavega
      Hi,
       
      My company has been developing and maintaining its own SCADA software in LabVIEW for a few years. It is fairly comprehensive: datalogging, graphing, alarm monitoring, automation, loops for equations and PIDs, and so on. It is a PC-based solution and communicates with many different kinds of hardware through the COM(RS232), USB, and Ethernet ports of the PC. This solution works well and allows keeping the costs low for most of our customers. Most of the loops run around 10Hz (100ms).
       
      However, more and more we are running into customer specifications that require high control rate (few milliseconds), high determinism (to the millisecond), and high reliability. Not surprisingly, the PC solution becomes unacceptable. We feel it is time to look into a real-time, embedded solution for those customers. That's why I'm currently investigating the different NI embedded RT solutions (namely PXI and cRIO).
       
      I can find plenty of resources on each of them, but close to nothing when it comes to comparing the 2 solutions and choosing which one to go with. Would you mind giving me some guidance? I guess you'll need more information, which I'll be happy to provide.
       
      A few elements already:
      - There is no request for MHz loops, so the FPGA side of the cRIO is not required I believe
      - Our application contains many VIs that are both the engine and the HMI, so there will be some decoupling effort if we need to split it into an HMI application on the PC and an RT application on the cRIO. Would a PXI solution avoid this issue by plugging a monitor directly to the display port of the controller? But then if I have all the code in the PXI controller, is it likely that I will lose my control rate and determinism?
       
      Thanks!
      Emmanuel
       
       
    • photovalve
      Deploying OOP to a PXI Chassis
      By photovalve
      Hello,
       
      I am developing a PXI system and thought I would use OOP to do all the DAQmx calls for all the different cards in my chassis.  It all looks nice and neat and works a treat when running in LabVIEW 2013.  All my Network Shared Variables are updated on my host application and the host can happily control the PXI chassis.
       
      However, as soon as I try and create an executable to run at startup the code stops working, it simply appears not to deploy.  There are no errors or warnings, the PXI executable simply no longer works.
       
      I presume I am missing something simple, like a missed check box or an automated deploy command.
       
      If anyone can see what I might be doing wrong then I'd be mighty grateful.
       
      My class structure is fairly simple
       
      LabVIEW Class >> DAQmx Class >> PXIe 6363 AI, PXIe 6363 DI, etc
       
      Thanks
       
      Malcolm
    • Astronautics Careers
      Test Engineering Supervisor Position at Astronautics!
      By Astronautics Careers
      This post has been promoted to an article
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.

  I accept