PXI-8231 with LabVIEW RT

Hi,
I plan to use a PXI-8231 in a PXI-1042 chassis with PXI-8184 controller. The controller doesn't run Windows, it runs LabVIEW RT 7.1.
Let's say that in my code I do a TCP Open Connection - since I can't specify what Ethernet adapter to use (8231 or the on of the 8184) how does that work? Does the TCP layer looks for the specified address from both Ethernet adatpers and returns the right connection?
Now let's say I do the same thing with Open Application Reference (to use VI server), is the TCP layer looking for machine name from both Ethernet adatpers and return the right reference?
Patrick.

Hi Patrick,
So I would specify the IP address of the adapter you are attempting to communicate with. If you specified a static IP address for the 8231, then you would simply wire this as the input to your TCP or Open Application Reference vi's. If, on the other hand, you are using DHCP to specify the IP address, we can get a little tricky. I'll assume that you know the MAC address of both network adapters, since you verified that you know how to configure multiple adapters in MAX. You can then find out the IP address that is assigned to your network adapter by using the RT Ping Controllers.vi. This sends out a ping to your controller and returns a list of all devices that returned the communication, specifying both the MAC address and the corresponding IP address. So by knowing your MAC address, you can then see what IP address was assigned. Then simply use this as your input to your network communication vi's, as previously mentioned.
I hope this fleshes things out a bit.
Cheers,
Emilie

Similar Messages

I am using NI PXIe-1073 with Labview-2014.After deploying the VI how can i read the data through host computer?

sankar,new delhi

PIB. I want to read the data from the GPIB after the operation complete. I am using *opc? command, which should set the status register bit after the completion of the operation, but this is not working. How to know that the Operation is complete"-Thanks.The NI-488 global status variables ibsta, ibcnt, and iberr is what you are looking for. Look into the 4882 help file for details. Also NI-Spy, http://www.ni.com/support/gpib/nispy.htm, is a good debug util. There is a website that lists common GPIB error codes and solutions. You may check there for some things to try. You'll find the link at ni.com > Support > Troubleshooting > Installation/Getting Started > GPIB, titled "GPIB Error Codes and Common Solutions".
You could find a driver for this instrument at http://www.ni.com/devzone/idnet/default.htm . If it's not listed there, it leaves you with one of a couple options. First, I would like you to submit a request for this driver at: http://zone.ni.com/idnet97.nsf/instrumentdriverrequest/
We develop dri
vers based on demand and popularity so the more requests we have for it, the greater the possibility that we will develop one.
If you would like to try developing your own instrument driver (or modify the existing one), we have documentation, model instrument drivers, and driver templates to help at :
http://www.ni.com/devzone/idnet/development.htm
We also have a syndicate of third party vendors that specialize in National Instruments' products and services. Some of the vendors specialize in driver development. I would suggest contacting one of the Alliance members at:
http://www.ni.com/alliance
Hope this helps.

How to build FM radio receiver on PXI 5600 and PXI 5142 with help of labview

How to build FM radio receiver on PXI 5600 and PXI 5142 with help of labview?
PLZ TELL ME!
Solved!
Go to Solution.

Dude,
Your way of asking questions sucks!
- Do not use such fonts!
- Try to find things out yourself first (apparently GovBob was able to find info, so could you)
- Have you asked GovBob if he likes it that you mail him for more questions?
You ask for a complete solution on a project YOU have to do. (you dont learn of it if you dont try it yourself first)
Hopefully you will ask questions in a less DEMANDING way next time.
Good luck with your project

Documentation for programming a PXI card with VISA in LabVIEW.

Hi,
Where can I find a documentation for programming a PXI card with VISA in
LabVIEW?
Thanks.
Denys.

Dan,
Thank you for your answer, short but useful to start.
Denys.
"Dan Mondrik" a ecrit dans le message news:
[email protected]..
> Denys:
>
> Our NI-VISA documentation for PXI has been somewhat scarce. We are
> improving it in the next version. In the meantime...
>
> Call VISA Find Resources with "PXI?*INSTR" to find all PXI devices.
> Call VISA Open with a device string like "PXI::devicenum::INSTR" or
> "PXI[bus]::devicenum[::function]::INSTR". In LabVIEW, use the VISA
> class "PXI Instr", available since LV 5.0. (The generic "Instr" will
> also work but will also present GPIB and VXI options and may be too
> confusing.)
>
> The property node has all the available PXI properties such as
> BAR0-BAR5 base/s
ize/type, and also manufacturer ID and model code.
> You can use all the register based in/out/peek/poke methods, just make
> sure to use the appropriate address space for your device.
>
> Dan Mondrik
> Senior Software Engineer, NI-VISA
> National Instruments

Hi am trying to save Data into a write to measurement file vi using a NI PXI 1042Q with a real time mode but it is not working but when i run it with uploading it into the PXI it save in to the file

Hi am trying to save Data into a write to measurement file vi using a NI PXI 1042Q and DAQ NI PXI-6229 with a real time mode but it is not working but when i run it without uploading it into the PXI it save in to the file please find attached my vi
Attachments:
PWMs.vi ‏130 KB

other problem is that the channel DAQmx only works at real time mode not on stand alone vi using Labview 8.2 and Real time 8.2

How can I use the NI PXI-6508 with Lab View 7? what are the first steps to get started??How can I use the channels with lab view 7????

I have a 8 slot PXI system with 2 NI PXI 6508 and 1 DMM 4070 in it. I want to get started with programming the digital I/O cards (6508)! How can I use this cards with LabView 7?what is the best way to get started, or where can I get examples showing how to use the several channels?
Thanks!
Philipp

Philipp,
The best way to get started is to decide if you want to use traditional NI-DAQ or NI-DAQmx. Recently we released NI-DAQ 7.1 which provides NI-DAQmx support for the PXI-6508. In my opinion, NI-DAQmx is more efficient and much easier to use.
To get started with examples, simply launch LabVIEW and go to Help>>Find Examples. Then expand Hardware Input and Output>>DAQmx and select the appropriate digital group for your application. This should help get you started.
Please repost if you need addition assistance. Good luck with your application!

How can I set the SRQ bit on GPIB with LabView ?

Hello,
I am developping an application with LabView RT on a PXI RT system. This application acts as an instrument (non controller GPIB), and I need to assert the SRQ line. How can I do that ?
I know the ibrsv function, but I can't find it in LabView, and I can not use it through a DLL call since GPIB DLLs are not compatible with Real-Time.
Thank you.

Hello Alfonso,
It sounds like you might be getting errors -200279 and -200278. (In the future, if you post the actual error codes, it helps us to know exactly what is happening). Error -200279 happens when you are performing a hardware-timed acquisition (meaning the data is sampled according to a clock signal on your board), but your LabVIEW program is not reading the values from the buffer allocated for that task in computer memory fast enough. Basically it's a buffer overflow error. It means older samples have been overwritten before you attempted to read them out. As the error message suggests, "increasing the buffer size, reading the data more frequently, or specifying a fixed number of samples to read instead of reading all available samples might correct the problem." For more information on this error, please see the KB (DAQmx) Error -200279 During a Continuous, Buffered Acquisition.
Error -200278 happens most often when you have configured a finite acquisition, but are calling the DAQmx Read function in a loop. If you want to perform a finite acquisition, you should only call DAQmx Read once. For more information on this error, see the KB Error -200278 at DAQmx Read.
Finally, please refer to Abhinav's earlier post about the sample rate on the 9237 module. As he described, the NI-DAQmx 8.3 driver will only allow you to set the sample clock to integer divisions of 50k (50,000/n, where n can be 1, 2, 3...13). Since the maximum divisor is 13, the smallest sample rate that can be used is 3.846 kS/s. You can check what value the driver is actually using for the sample clock by reading from the SampClk.Rate property of the DAQmx Timing property node.
I hope this helps! Let me know if you have any questions about what I've described.
Best regards,

Problems getting started with LabVIEW FPGA

Two (probably) related questions:
1. I am trying to get started with LabVIEW FPGA, and I am having trouble using a host VI to test my FPGA VI. I started with a basic QAM modulator VI, to be run on the FPGA, and I have reached the point where I need to verify the logic and timing with this VI running on the development computer with simulated IO. I have tried various combinations of putting the code inside single-cycle timed loops vs not; putting the modulator block directly into the host VI, and using the "FPGA reference" block. When neither the host VI nor the modulator VI use a single-cycle timed loop, I see correct behavior. In every other case, the output of the VI is either absent or incorrect. I need to use a single-cycle timed loop in the FPGA VI to properly verify timing behavior (as far as I know), so the one functioning case is not enough for me.
I'm sure there is a key step I'm missing or misunderstanding, but I have not been able to figure it out myself yet. I've attached my modulator diagram as well as two different attempts at host VIs. I can share other information, but I'm not sure what is most relevant.
2. I am also trying to test a simple wrapper VI for the Xilinx FFT block, and I am having trouble accessing FIFOs inside the host VI. I thought this would be relatively straightforward, but when I tried to change the "method" on an "invoke method" block, there were no options for accessing FIFOs, as I understood there should be. This is a total roadblock for me. These two diagrams are also attached, the test diagram shows the options available to me for the "invoke method" block.
Labview 2013, PXIe-7965R, PXIe-8133 controller.
I had to combine the diagram images; in case they are hard to follow this way, see the individual images here: http://imgur.com/a/oB6OD .
Thanks in advance for any suggestions.
Attachments:
mod_all.png ‏68 KB
fft_all.png ‏52 KB

Hello Monguin61
If you are having problems reading from DMA FIFO's you should test them using a very simple code to understand their behavior. First, you could start taking a look to the linked documents:
Reading DMA FIFOs from Host VIs (FPGA Interface)
Using DMA FIFO to Develop High-Speed Data Acquisition Applications for Reconfigurable I/O Devices
FIFO.Read (Invoke Method)
Then you could test and analyze a simple example to understand how it works, for example this one: Simple DMA FIFO Example for FPGA.
Check the references when you are using DMA FIFO's, I noticed you did not connect them in the second picture attached.
Regards
Frank R.

How come you can not use more than 126GB of a 1.5TB diskdrive with LabVIEW Real Time?

How come you can not use more than 126GB of a 1.5TB diskdrive with LabVIEW Real Time?
This is only 8.3% of the available disk drive space!
http://digital.ni.com/public.nsf/allkb/E7E2F5657B6026358625750B007201A6?OpenDocument
National Instrument's solution is either reformat you drive to less than 126GB or replace the drive with one less than that size.
Please NI, tell me you are going to fix your LabVIEW Real Time soon, and that we won't have to wait for LabVIEW RT 9.2.1 in 2011 for this one to be fixed.
http://upload.wikimedia.org/wikipedia/commons/9/90/Hard_drive_capacity_over_time.svg
Drives as large as 126GB or more have been around since about mid 2002. That's about 7 Years now and LabVIEW Real Time STILL can't use drives larger that 126GB! Please NI. Do something.
We deserve fixes to the old versions of LabVIEW RT. How about updates to LabVIEW RT. Such as 7.0.2, 7.1.2, 7.6.2, 8.0.2, 8.2.2, 8.6.2.
We don't need new features or versions of LabVIEW RT such as 9.0 until we have some of bugs fixed in the existing versions.
Kevin.
Message Edited by kmcdevitt on 05-29-2009 03:39 PM
Solved!
Go to Solution.

Coq rouge wrote:
NI is not making the Real Time OS in house. I do not remember which firm that is making it. Anyway you are allowed to use a hard drive that has been partitioned. And 126GB is some space is it not? I remember Bill Gates declared one time that 640Kb ram should be more than enough for any PC application also in the future
Coq Rouge (formerly t06afre),
The RealTime OS is an NI Product that is purchased from NI.
NI may or may not outsource design, developement, or manufacturing of the products that it sells under its own Company name.
For this reason I would be concerned if I were a PXI Embedded Controller designer/developer in the United States.
Yes, 126GB is some space. I see that there are now 2TB drives available. 126GB would be 6.3% of a new 2TB drive. Should we all be happy with being able to use 6.3% of the available drive space. Moore's Law seams to be alive and well. Drives larger than 126GB have been readily available for 5 or 6 Years. This should not be a surprise to NI. Why don't they do something about it.
Thanks for the trivia on Bill Gates. I must have missed that one since I don't try to keep up with Microsoft. I believe that he is a wonderful person and he and his family are doing wonders for the world in their "retirement". The world needs more like him.
What I do remember is Steve Jobs telling us that we would never need more that 128MB and that we would never to need to do anymore software development because everything was already in the "ToolBox".
McKevin.

How to synchronize the system time/date of a PXI controller with a GPS or time server?

Using a PXI system with a NI-PXI 8196 controller and LabVIEW RTOS, I am searching for a solution to set or reset the on board timeclock of the controller trough a external signal like a GPS or a time server (ntp).
Do an easy way exist to do this?
Any response will be greatly appreciated.
Philippe D.

Hello Philippe,
combining those examples should resolve your request:
http://sine.ni.com/apps/we/niepd_web_display.display_epd4?p_guid=DB0882E37369122DE034080020E74861&p_...
and
http://sine.ni.com/apps/we/niepd_web_display.display_epd4?p_guid=EE349DC00D8D5E08E0340003BA7CCD71&p_...
or
http://sine.ni.com/apps/we/niepd_web_display.display_epd4?p_guid=B45EACE3E23356A4E034080020E74861&p_...
Hope this helps,
Regards Thomas Bl.

SpaceX is looking for engineers with LabVIEW experience in Hawthorne CA (LA area)

SpaceX is looking for engineers with LabVIEW programming experience for our Launch group. Our responsibilities include:
Controlling launch pad equipment via PXI/LabVIEW
Commanding and monitoring our Falcon 1 and Falcon 9 rockets via a LabVIEW-based Vehicle control system
Commanding and monitoring our Dragon capsules via a LabVIEW-based Mission Operation system
Ocean recovery of Falcon 1 and Falcon 9 stages after liftoff and Dragon capsules after splashdown
Cargo configuration of Dragon capsules going to resupply the International Space Station
Maintenance of Mission Control Centers with the help of our IT department
With the exception of the launch pad equipment program, most of our LabVIEW programs do not interact with DAQ hardware (unusual, I know). The Vehicle control and Mission Operations software get their data via Ethernet from 'black boxes' that connect to NASA & Commercial RF ground stations. We also create several utility programs in LabVIEW that also don't interact with hardware. So, this is mostly a software gig, not a hardware/software gig.
Ideal candidates will have the following qualities:
CLD-level LabVIEW experience
A good understanding of basic computer networking (TCP/IP, UPD, firewalls, VPN)
Must be enthusiastic about space (What year did we land on the moon? How many men walked on the moon? How many Space Shuttles do we currently have? etc.)
Must be willing to travel. Common destinations include Houston (NASA Johnson Space Center), McGregor TX (test site), Cape Canaveral FL (launch site), Kwajalein Marshall Islands (launch site)
Must be able to work without supervision. We have a very flat management structure, no one will be telling you what you need to do. If you don’t know, ask. If you do know, get it done.
About the job:
Job is located in Hawthorne, CA in the Los Angeles area.
This is not a 9-5 job. There will be some late nights.
You won't be LabVIEW only. Everyone chips in as needed. Our group has done Javascript, C++, MATLAB, configuring of TELEX comm systems, cutting of metal with bandsaws, welding, Unigraphics CAD, etc. If we need it and you don't know it, grab a book and learn.
We are only hiring full time employees. Contractors need not apply.
To conform to U.S. Government space technology export regulations, SpaceX hires only U.S. citizens and U.S. Permanent Residents.
Apply at SpaceX.com. Click the Careers button and fill out the general application. Mention this posting in the cover letter field. Don’t reply to this forum. You need to go to SpaceX.com to get your information into our system.
Message Edited by Lavezza on 03-31-2010 03:59 PM

There is a job posting up now at SpaceX.com. Go to the careers tab and search for LabVIEW.
Look for the position called: Mission Control Software Engineers (LabVIEW).

Fetch and peak detection all channels of PXI-5105 with 4M record... HELP!

Dear collegaues!
Please help me to improve performance my application, see attachment, and sorry for my English.
So, my task is to fetch and peak detection all (eight) channels of PXI-5105 with 4M record and sample rate 4M with loop 1 sec...
Inputs of all my channels are wiring to NaI detectors with 0,5...1 microsec of pulse width (really) and freq from 0 kHz to no more than 40 kHz.
Why I've selected 4M record and 4M sample rate namely? Answer is that I've tested PXI-5105 previously by generator 40 kHz and 0,5 microsec width pulse. It is working fine and peak detection indicate for me 40000 pulses/sec. If I set lower than 4M record and 4M sample rate it is no working. In my honest opinion 4M record and 4M sample rate are very min settings.
In the present time peak detection working only 6 channels... When I've connected to diagram more than 6 "peak detector.vi" - I see the error "...out of memory...".
Please advise me, what is to be done for that is all working fine.
Solved!
Go to Solution.
Attachments:
consumer-producer7.vi ‏44 KB

What you are running into is an out of memory error in LabVIEW. You have enough onboard memory to capture 4M samples per channel on the digitizer. The issue is with fetching and manipulating that data in your LabVIEW application. You will want to step back and take a look at how you are handling your data to understand why that is happening.
1) 4M samples/ch = 4M Samples x 2Bytes/sample/ch = 8M Bytes/ch
2) Expanding to 8 channels creates 64M Bytes of data in the raw binary format
3) You are scaling your data by fetching in a 1D WDT format. This stores each sample in a 32 bit double, expanding the memory to 256M Bytes (in addition to timing information)
4) By splitting up the array of waveforms and branching data it you can easily create copies of this data, and if your consumer loop is not completed with the last data, you may be trying to capture a whole new set, creating yet another copy.
So you can see that while you have 1.5GB of controller memory, when dealing with large arrays of data you can easily eat up that memory. There are several things you can try to make your application more efficient. You could work with an unscaled binary data format, you can wire the array of waveform directly to the peak detect vi (instead of creating 8 copies, you will have a single copy with arrays of output) or you could revisit the record size you have chosen (experimenting with your threshold and width settings might help you to get the results you want with smaller record lengths).
-Jennifer O.

Interfacing a piezioelectric actuator with Labview

im looking at controlling a Melles Griot piezoelectirc actuator with Labview to obtain real time data of voltage vs displacement. However, i do not know how to write the program for a closed loop function block. Ie, i need to ask the actuator to move a distance by applying a suitable voltage when there is resistance to motion.

Unless you are using LabVIEW RT on a PXI system it's not a good idea to do control loops in LabVIEW or any other Windows based software. On Windows the timing behavior is not deterministic. That means the loop cycle time varies. The loop cycle time directly influences the control algorithm. The faster a PID loop runs, the lower your Kp, Kd, Ki values need to be. Thus on a system like Windows without deterministic timing it's hard or even impossible to get a stable system.
A much better choice is the use of a motion control board, e. g. the PCI-7344 or PCI-7342 board. These devices run the PID loop onboard in realtime and you only need to set parameters like travel distance, speed and acceleration. You can use quadrature encoders or analog signals as feedback signals and
with the latest release of the driver software, NI-Motion 6.0 there is also an assistant included that helps you to eliminate the effects caused by static friction that are immanent to piezo systems.
Please visit the following link to get more information:
http://www.ni.com/motion
Best regards,
Jochen Klier
Applications Engineering Group Leader
National Instruments GERmany GMbH

Labview 7.0 is compatable with Labview Imaq6.1 , vision builder 6.0 and Imaq run time engine 6.0.

Sir,
My system is PXI 8174 and i an using NI 1411 card for my application. I want to know the compatability of the softwares. Whether Labview 7 is compatable with Labview Imaq 6.1 , vision builder 6.0 and Imaq run time engine 6.0.

Hi,
Assuming you meant IMAQ Vision 6.1 instead of IMAC 6.1, this software was intended to run on LabVIEW 5.1, 6.0, and 6.1. I have heard of it being used with LabVIEW 7 on occasion, so it may be possible to make it work, but this has not been tested and is not officially supported. Vision Builder 6.0 should run; however, it was developed long before LabVIEW 7.x and will not generated code for LabVIEW 7.0 and later. The Vision RTE version should correspond to the version of Vision you are using. For instance, if the program was developed with Vision 6.1, the computer should have the Vision 6.1 RTE installed. With this being said, if you plan to use LabVIEW 7, I recommend updating your other software.
Regards,
Ryan M.
Applications Engineer

How can I access CAPI 2.0 methods with LabView ?

I must use CAPI 2.0 (common ISDN interface) method with LabView (graphical interface), the work is to command a ISDN S/T card on PXI Bus, and this card support CAPI 2.0.

This depends upon what type of interface you have to the ISDN. I assume you have either Basic Rate Interface (BRI) or Primary Rate Interface (PRI). Do you have a DLL to control it? If so, you can use the "Call Library Function Node" VI to access this DLL and just make calls to it. If you have an ActiveX Server, you can use the LabVIEW ActiveX Automation VIs to access it.
J.R. Allen

PXI-8231 with LabVIEW RT

Similar Messages

Maybe you are looking for