Running LabView 7.1 with PCI-6251 in Windows 7

I am very new to Labview, and would appreciate any assistance on this issue. I was tasked with solving it and while I have made some progress I have now hit a wall.
A computer with a PCI-6251 data capture card, some custom built (external) hardware and LabView 7.1 has been used for many years for a single, specific task, to do verification testing in a manufacturing environment. The system works well and no additional features or functionality is required.
The computer failed and a new one with a PCI card slot was purchased to replace it. Of course as a new PC it has Windows 7 and hardware drivers for XP don’t exist. I therefore need to run LabView 7.1 on Windows 7 with a NI-DAQ card.
I installed the NI-DAQmx 9.5.1 driver and then installed LabView 7.1 (as discussed here). The driver would not install if LabView was already installed since it gave the “unsupported on this version of windows error”. MAX recognized the card, which it couldn’t when trying to use the 7.5 NI-DAQ driver.
Now LabView opens but when I try to run the .vi used for testing it complains of 19 missing sub .vis which I cannot locate and I can’t find on the old computer to try to point LabView towards.
I think something weird is occurring with trying to use the 9.5.1 driver with LabView 7.1. Are there any suggestion or is there any advice on getting a PCI-6251 working with Labview 7.1 on a Windows 7 machine?
Solved!
Go to Solution.

After much greif and trying a half dozen various drivers with various settings and other ideas the following procedure based on Caraval's advice worked first time with no errors and seemingly no functional issues. The system so far appears to be running in Windows 7 just as it was on Windows XP.
1. Install LabView from original install CDs, by opening the folder and right-clicking 'setup.exe' and clicking 'run as administrator'. Selected 'do not install drivers' during the install procedure. Rebooted computer.
2. Installed NI-DAQmx 8.9 from the self-extracting .zip file available here. Shutdown computer.
3. Removed power, pressed power button to completely discharge power supply. Installed PCI-6251 card.
4. Booted computer, and logged in. Waited a long time, Windows eventually saw new hardware and installed drivers. Verified MAX could see card.
5. Opened LabView and everything worked.
Looks like we bought the system a few more years. Will probably have to upgrade everything next time around though. Many thanks to everyone who commented on this thread.

Similar Messages

Data acquisition and frequency generation togather with PCI-6251 and LV8.2

Hi friends,
I am a new user of Labview. I am using LB8.2 with PCI-6251 .
I have to generate frequency and then measure the data and then for next frequency and so on.
i know that for this i have to use looping and that is not a problem. The real problem for measurement is to identify whether the frequency is been generated. if yes then measurements starts otherwise it should wait until it started. then after finishing the measurements send a signal to generator for changing the frequency and amplitude.
Now these two things {generation and measurement} togather are not working correctly for me. so i make 2 diff file, one for generation and other for measurements <by modifying the examples>. I can run both file togather and it works. But it need lots off effort and time. I have to measure from 10Hz to 1000Hz in 2Hz frequency step and i cannt leave in between .
can anyone help me how to syncronize these two togather .
Trying to attatch. both the files here ..
main_v1.1.vi --> for Measuring
Oscilloscope.vi --> for waveform generation
Attachments:
main_v1.1.vi ‏150 KB
Oscilloscope.vi ‏37 KB

Hay thnx dude..
I found the example and now it works
once again thanks a lot

Can I use Labview real time with PCI 6013?

How much does Labview real time cost?
Do i need to have some additional hardware to use labview real time with PCI 6013?

You can not use the PCI-6013 board with LabVIEW Real-Time.
We offer three platforms for LabVIEW Real-time. PXI embedded controllers, 7030 data-acquisition plug-in boards (7030/xxxx) and FieldPoint. For more information on these options go to www.ni.com/products and then choose Real-Time from the menu on the left. There are PCI versions of the 7030 boards. Each 7030 board has a data-acquistion board attached to it (6030E, 6040E or 6533). When you embed a LabVIEW Real-Time program on the 7030 you will be able to access the daughter board. You can not access other boards from the embedded program. If you want to use several daq cards in your real-time system I would recommend a PXI chassi and PXI daq boards.

PI controller with PCI 6251

Hi all,
I am using DAQ PCI6251. Can I use this card for creating PI controller ?
Basically, I think that we can analyze a PI controller into two phases, including the proportional and integral phases. I could do this easily with Labview library. But I am facing a difficulty how to build the saturation block for PI controller ?
Pls give me the solution.
Thanks so much for your helps and supports.
Best regards,
Duy

Dear Jochen,
Thank you very much for your reply.
I can describe what I am doing as follows:
I would like to control the induction motor drive system with vector control approach.
The equipments in my system include the induction motor drive system, inverter, PCI 6251 Labview card, block connector BNC2110. I am using Labview 7.1.
I will gather the stator currents and voltages from the induction motor under analog signals. Then I will make some calculations on Labview with available Labview library. After that I will output two analog signals. PCI 6251 has two analog signals. I will use two analog signals from PCI6251 Labview card as input signals for PWM generating board which I could bulid. This PWM generating board will create signals to trigger IGBTs of inverter. And the inverter will create signals to control the induction motor drive system.
In this drive system, we need to use two PI controller as the requirement of vector control approach.
I hope that my description is clear.
The expected sample rate is 10 kHz.
I am using XP Window OS.
I attach the diagram what I need to do as well.
Thanks so much for your great ideas.
Best regards,
Duy
Attachments:
Practical_diagram_Labview_NI.pdf ‏27 KB

Run BI Publisher report (with Excel template) on Windows 7

Hi, All.
Sorry for my English :)
I have some problem:
I use BIP standalone for my reports. Some reports are in Excel (with Excel template). When I run it on PC with WinXP - all is OK. But, when I try to run it on PC with Win7, then Excel is opening and writing this "Native file format and file extension does not mismatch. Before open be sure of file does not damage" (this is my translation). If I try save file on the hard disk, then file is 0 kb. But if a report has RTF-template, then it opening normaly on Win7's PC.
Have you any ideas?
Thanks!

option1:
The query should be same @ detail level, only the template has to be different for summary and details.
@runtime, user can choose to see the detail/summary
Disadvantage, if the data is huge,
advantage , only one report.
option2:
create two separate reports summary and details
and create diff data and diff layout and keep it as different report
Advantage, query will perform based on the user run report, summary/detail, so that you can write efficient query.
Dis advantage , two reports query/template to be maintained.

Using PCI-6251 with Labview 6.1

I recently purchased a PCI-6251 multifucntion DAQ board to get a higher sampling rate than my old PCI-MIO-16E-4 board. However I have existing software that I want to run on the new board. The board came with NI-DAQmx which will only work with Labview 7 or above. I am currently running NI-DAQ 6.9.3 and the Measurement and Automation program does not recognize the new PCI-6251 board. Is there anyway to get Labview 6.1/NI-DAQ 6.9.3 to recognize and configure the new board? Or will I be forced to upgrade my Labview?

The M-series boards (PCI-62xx are M-series) require NI-DAQmx driver. The NI-DAQmx driver requires a newer Labview. No way around it.
John Weeks
WaveMetrics, Inc.
Phone (503) 620-3001
Fax (503) 620-6754
www.wavemetrics.com

How to generate a pulse of 5 V -ve polarity in synchronisation with a 10 v input using PCI 6251 DAQ board

HI
I want to generate a 5V -ve polarity pulse to trigger my IEEE 1394 camera using an PCI 6251 (scb68 pin E) device, furthermore I am reading a standard Vsync signal from a SVGA port which is 10 v.
Now I want to synchronise the image capture of an IEEE 1394 camera with the Vsync signal so that camera is triggered to capture at every 4th Vsync signal (which is 50HZ.). Presently I am able to read the Vsync signal and also generate the -5 v signal But the Daq board generates a continues -5v signal while I want a 1 ms pulse (for every 4th Vsync).
Also this 5 v signal is generated even if the vi is stopped running.
Can anybody guide me so this problem can be solved.
Thanks a lot in advance
Shri

You can use the Write function, that is you can use the 10 volt signal as a trigger for the task, and when you get this trigger, the task starts and generate (writes) a waveform you defined in an array ("data", in the example).
Something like this..
DAQmxCreateTask("",&taskHandle);
DAQmxCreateAOVoltageChan (taskHandle, clokSource, your_sampling_freq, -10.0, 10.0,
DAQmx_Val_Volts, "");
DAQmxCfgSampClkTiming (taskHandle, clockSource, SAMPLING_RATE,
DAQmx_Val_Rising, DAQmx_Val_FiniteSamps,
samp_to_read);
DAQmxCfgAnlgEdgeStartTrig (taskHandle, input_channel, DAQmx_Val_RisingSlope, 9.0);
DAQmxWriteAnalogF64 (taskHandle, 1000, 0, 10.0,
DAQmx_Val_GroupByChannel, data, //data contain a pulse
&samp_per_channel, 0);
DAQmxStartTask(taskHandle);
// and then you create a loop....
For example you can specify data to be like this:
data[0] = -5;
for(i=1;i<1000; i++){
data[i] = 0;
Tell me if you need more help.....
bye

Running VI's on Labview 7.1 with Windows 7

Hi,
So I know that Labview 7.1 is not support by Windows 7, but I have noticed people on these forums have been getting it to work (sort of).
I have managed to get our PCI 6221 card to work on our Windows 7 x86 machine with NI-DAQmx 9.4 installed, and I have installed Labview 7.1 on the machine as well. But my issue is when I try to load any of our VI's (ones that we run from Windows XP) it starts to load them but it then wants to find various VI's such as "DAQmx Create Task.vi", "DAQmx Create Virtual Channel.vi" etc. And when I hit cancel and then stop (as I cannot locate these VI's) Labview will not operate properly.
Is there something I am missing or are our VI's not compatible with Win 7?
Cheers,
Tim

nathand wrote:
DAQmx 9.4 does not include support for LabVIEW 7.1. You could try uninstalling, and going back to a much earlier version of DAQmx.
But that version is likely not able to support Windows 7. DAQmx contains a lot of kernel space components, and a kernel driver originally written for Windows XP, quite likely won't work without issues under Windows 7.
What I have gotten away with once, was to install LabVIEW 7.1 on an older XP PC, then a DAQmx version that supports 7.1, and then do the same on the Windows 7 PC but with the newer DAQmx, and then copy all the DAQmx VIs from the XP PC into your new LabVIEW installation. A tedious work and with a high chance that some of the VIs won't be compatible with the new DAQmx driver. It worked for a simple DIO application but your mileage may vary greatly.
Another approach might be to backsave the VIs in a supported LabVIEW version to 8.0 and then using LabVIEW 8.0 to backsave it to 7.1 but that is even more tedious if you want to get all DAQmx VIs backsaved, and likely will require some additional editing on the VIs to cater for unsupported features in 7.1.
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

PCI-6251 into LABVIEW DAQ Assist block interruptions and resets

Signals being received from PCI-6251 into a LABVIEW DAQ Assist block interrupts and resets every 10 seconds after 1 minute of data acquisition. Would this be a memory buffer problem or is it something related to the hardware? I am using a BNC-2110 hardware connector. Please view the attached image.
Attachments:
Interuption1a.GIF ‏4 KB

Hey Peter,
Ahh, I understand the graph now! Hmm, this is very strange behavior. Instead of using the DAQ Assistant, try to use the explicit DAQmx VIs (see picture). You have more explicit control over what is going on with the DAQmx VIs and keep as much as you can out of the loop.
Regards,
Erik
Attachments:
analoginput.JPG ‏23 KB

Why does LabView crash when I run it in parallel with a temp/ RH logging probe?

I am running LabView 6.1 on windows 95. Up till now I have had no problems. However, we recently acquired a Temperature / Humidity probe which plugs into the Com1 port of the computer and logs the data using it's own software. Since then, when the two programs are used together, eventually LabView crashes with the following error message: Failure, 'image.cpp, line 5793.
Can you tell me why this occurs and what the solution is?

Taking a shot at this. It could be because the two programs are trying to access the same type of logging program(excel??). Only one link can be active at a time or they crash. Try running it without saving the data and see if it crashes.

How to run Labview apps in tablet with android os

How to run Labview application in tablet with android operating system?
Can we use Labview mobile module or we must use google play data dashboard for labVIEW? how to install it in PC?
Solved!
Go to Solution.

If you had looked at data dashboard and some of the other links on Android, you would see that you cannot run a LabVIEW app on Android. Nor can you use a serial port. With Data Dashboard, you have a pc running LabVIEW and it publishes to network shared variables. Data Dashboard on the Android allows you to view those variables.

Is it possible to run Labview ver 6.5 with PowerPC as the target CPU and VxWorks as the target operating system? If version 6.5 does not support this configuration, do any of the later versions support it?

Is it possible to run Labview ver 6.5 with PowerPC as the target CPU and VxWorks as the target operating system?
If version 6.5 does not support this configuration, do any of the later versions support it?
I have an Ada executable that's creating a buffer of data that's being fed to a Labview executable that's displaying the data in a GUI. We're re-architecting some legacy system hardware and I'm just trying to figure out if this configuration is even possible.
Thanks

Hi,
I never heard of LabVIEW6.5. I only know of LV6i, LV6.1 and LV7.0...
Why don't you just call your next/regional NI sales rep?
Best regards,
GerdW
CLAD, using 2009SP1 + LV2011SP1 + LV2014SP1 on WinXP+Win7+cRIO
Kudos are welcome

Is it possible to run Labview ver 6.5 with PowerPC as the target CPU and VxWorks as the target operating system? If Labview ver 6.5 does not support this configuration, do any of the later versions support it?

Is it possible to run Labview version 6.5 with PowerPC as the target CPU and VxWorks as the target operating system?
If version 6.5 does not support this configuration, do any of the later versions support it?
I basically have an Ada executable and Labview executable that currently run on a Sun Machine with Solaris as the operating system. I'm re-architecting the system hardware and will be getting rid of the Sun Machine and Solaris. I'm don't have any issues with the Ada executable, but I'm not sure what configurations Labview supports.

duplicate post
In the future, please don't try to stuff your message in the subject line. Thanks.

Running LabVIEW 7.1 on Windows 2003 Server with Terminal Services

We are setting up a newtork based solution with LabView. I have looked for documentation on installing LV 7.1 on a Windows 2003 server to run the applications and then have destkops connect to it. Can this be done with a Terminal Services Access solution? Another words, if we were to purchase the LV Volume License Manager, can you install LV 7.1 onto a Windows 2003 server and run the application through TS across a 1GB backbone from the desktop, which makes the server do all the processing?

On Fri, 29 Oct 2004 07:42:13 -0500, ITIQ wrote:
> By running a session through Terminal Services you are NOT running
> anything on the desktop it all runs on the server. So if the software
> was installed on the server and you had the correct number of licenses
> that you allow to connect through Terminal Services, would this not be
> allowed under the EULA?
Sorry for the delay. I'm surprised Philip didn't get back to us... Phil
are you there? Based on his comments, I think he misunderstands your
situation (no offense Phil).
You and I are both talking about the same thing. You basically want a
terminal server license. NI will not provide it. They told me (over the
phone) to get a multi-seat license (MSL). IMO, that's unacceptable. I
expect a LV license taylored specifically for thin client networks. A
multi-seat license is for -->installing<-- on multiple machines. It
conforms to a totally different set of rules. One big one, an MSL assumes
that you intend to run LV locally to interact with DAQ hardware. Since
this won't be done with the thin client, you shouldn't have to pay for it.
> I am not sure if the question is if the license is valid or not, I am
> first just trying to figure out if you can even install LV on a Windows
> 2003 server and run it through a Terminal Services Session.
Since you are talking about a Microsoft operating system, I would say this
cannot be done without some additional/costly junk installed.
Here's another option. If the people you're supporting don't have any
platform dependent things like ActiveX in their LV applications, you
should consider using a Linux-based terminal server. I know for a fact it
works.
I've assisted in setting up a network like this before:
* One Linux terminal server with LabVIEW for Linux (Full Dev)
* One WinXP box on the network with LabVIEW for Win (Prof Dev)
* 5 cheap thin clients
They developed LabVIEW source code on the thin clients and then compiled
packages on the WinXP box for distribution to their customers. The WinXP
was only used for compiles so they just hopped on when necessary. The
eventual plan is for the thin clients to simply open a RemoteDesktop
(using RDP) terminal session and do the compiles from there. I'm not sure
how to do that yet... on the Windows side.
> I see the comments on calling VIs through LV. I am a Network Engineer
> not a LV Developer, so unfortunately I do not know what a VI is. All I
> am looking to do is run low end PCs with LV if I have to, but use the
> server as the workhorse to process all sims etc.
Phil must have thought you needed a LV application to access the front
panel controls of another LV application running on a remote machine. The
VI server is handy in that area but useless in your case.
Hey, you wanna hear about cheap network infrastructure? We bought our
thin client boxes for $15 each! Go to ltsp.org if you want more info on
configuring Linux as a terminal server.
You, and anyone else, can also email me at gnu_voodoo [at] netzero [dot]
com for questions/comments.

Is LabView good at precise motion control for things like running an assembly line with lots of cars moving about?

Is LabView good at precise motion control for things like running an
assembly line with lots of cars moving about? Precise speed and
acceleration control? Safety interlocks?
Thanks for any help you can offer!
Sent via Deja.com http://www.deja.com/
Before you buy.

If you are a long time Nokia/Symbian fan then you will Know full well that Nokia phones ALWAYS improve with software updates, Symbian will not be abandoned and will not be replaced by WP7, it will continue to evolve and improve, as will the handsets. Anyone who desires or wants a different OS should try one, because it's a free world, but really, the 'perfect' OS doesn't exist, and Symbian suits me for now and I will rely on Nokia to keep it up to date, and reliable.
If I have helped at all, a click on the White Star is always appreciated :
you can also help others by marking 'accept as solution'

Running LabView 7.1 with PCI-6251 in Windows 7

Similar Messages

Maybe you are looking for