Windows 7 with labview 8.5 and NI-8451

Hello,
I am using LabVIEW 8.5 with NI-8451 device on Windows 7. I installed 1.1 driver for NI-8451, but I am unnable to access any subVI connected with NI-8451. Can you advise?
Thank you.

Hi miso2562,
The issue is most likely compatibility between the drivers, LabVIEW, and the OS. LabVIEW 8.5 is not supported on Windows 7 (only up to Vista), and NI-845X 1.1 is not supported on Windows 7 either (only up to XP). Also, NI-845X 1.1 does not support LabVIEW 8.5 either (only up to 8.2).
Ideally, if you use Windows 7 you should have LabVIEW 2009 SP1 or newer and NI-845X 2.1 or newer (1.1.4 could work as well). If you can move to XP, LabVIEW 8.5 and NI-845X 1.1.1 should work.
References for compatibility:
http://digital.ni.com/public.nsf/allkb/B972242574D4BB99862575A7007520CB
http://download.ni.com/support/softlib//i2c_spi/ni-845x/1.1/readme.htm
As for your main question "unable to access any subVI connected with NI-8451", do you mean they do not show on the function pallete?
- FCTesting

Similar Messages

On my mac when i click on pages, a new document doesn't open instantly but a window with my files open and then have to click on the left bottom new document in order to open one. How can i have directly a new document when i click on pages icon

On my mac when i click on pages, a new document doesn't open instantly but a window with my files open and then have to click on the left bottom < new document> in order to open one. How can i have directly a new document when i click on pages icon

How to open an existing Pages document?
Click Pages icon in the Dock to launch Pages.
When Pages is open, click File menu in the Pages menu bar.
Select “Open”.
When the select document dialog box opens up, highlight/select the document and click “Open”
at the bottom right corner of the dialog box.
s
https://support.apple.com/kb/PH15304?locale=en_US

I am using report generation toolkit 1.1 with Labview 7.0 and Office 2003 professional. The create new report VI opens Excel but throws error (-2147167262- from automation open VI) when I try to open MS word. please help...

I am using report generation toolkit 1.1 with Labview 7.0 and Office 2003 professional. The create new report VI opens Excel but throws error (-2147167262- from automation open VI) when I try to open MS word. please help...

Hi Leo22,
Does this error occur if you use any of the example programs that come shipped with LabVIEW? I would try opening one of the examples that write data to Word and see if those give you an error. Also, have you tried just putting down a New Report.VI and change the report type to Word? If this simple vi (that's all you need to open Word) breaks, I would check to see if there are any instances of Word still open. Check the task manager to see if any word processes are still open. There should not be a problem accessing Word 2003 from LabVIEW 7.0. If neither of these solutions work, please give some more detail about your application and we can research further. Thanks!
Jeremy L.
National Instruments
Jeremy L.
National Instruments

Problems with LabVIEW 7.1 and lock-in amplifier Stanford SR530?

Does has anybody had problems with LabVIEW 7.1 and the instrument driver for the lock-in amplifier Stanford SR530?
With LabVIEW 6 there are no problems at all, but with LabVIEW 7.1 it is impossible to communicate with the instrument.

amr_attia wrote: (Private message, no need to private message)
My problem is to get the data out from the divice x and y readings . Can you help me
Here is the code and snippet. I had it from before. It reads Channel 1 and Channel 2 from the SR530, that is whatever the display is for Channel 1 & 2. You set the display manually or programmatically, I let you figure that part out.
Cheers,
mcduff

Windows 7 Compatability with Labview 8.0 and missing files while interfacing the FPGA with LV

I am trying to use an FPGA (PCI-7830R) with Labview 8.0. The computer has Windows 7 OS. I installed LV 8.0 in the proper order with the FPGA Module and labview is able to see the FPGA when I open a .lvproj (the FPGA is in the tree) however there is a warning symbol next to the FPGA selection and when I try to open a .vi file that is used on the other stations in my lab (it works on all the other stations), labview is unable to find a whole bunch of files. There are some pictures.
Missing File (there are a bunch more but this is the fist one).

According to this LabVIEW Compatibility LabVIEW 8.0 is NOT compatible with Windows 7
Visualize the Solution
CLA
LabVIEW, LabVIEW FPGA

Acquire images with labview via firewire and TWAIN

Hi,
I have a camera from optronics. This camera is plugged to my computer
via a FireWire IEEE-1394 connection. The company optronics offers a
TWAIN driver for this camera: some files like TWAIN.dll and
TWAIN_32.dll. I would like to acquire images with labview and
communicate with the camera but I have no idea on how I should get
started.
The 3 main things I'd like to do are: 1) change the exposure time 2) snap images 3) see the images in labview.
I will really appreciate if someone could give me some ideas to get started...
Michael

AESulzer wrote:
Michael, From a
more general standpoint, what you'll need to do is use a Call
Library Function Node (located in the All Functions>>Advanced
palette) to call the necessary functions out of those DLLs. Before you
can do this, you'll need to know some specifics about what functions
are available in those DLLs and what parameters/outputs are associated
with them. This information is typically available in the product
manual or perhaps someone else with experience with your specific
device can speak to that. Once you know the functions necessary to
execute the desired operations, you simply configure a Call Library
Function Node for each of them and place them in your LabVIEW code.
Just
saw this and want to clarify on this. This is a total no-go! The Twain
interface is a very old technology from the days when Windows was a
cooperative multitasking environment without real tasks or threads. In
order for Twain to allow for some sort of multitasked integration into
an application it requires you to integrate the Twain handling into the
message loop of your application. As you do not have direct control
over the source code LabVIEW is written from, this is a very tedious
operation, with Windows message hooks and such, lots and lots of
semaphore protection to avoid race conditions etc. etc.
There is simply no way that you can do anything even remotely workable
just by using the Call Library Node. You will need a (rather complex)
external shared library that goes in between Twain and LabVIEW and
takes care of all the subtleties. I know for sure because I wrote such
a beast in the past.
Now there is a Toolkit from the French Alliance member Alliance Vision http://www.alliancevision.com/us/index.html that
does this. If you need Twain I would definitely go for this. My own
library is only to the point of what I had needed for a particular
project, (meaning it supports two specific scanners without issues) and
without any documentation for external users and I couldn't give it
away for free either.
Just want to warn you but there is a good chance that the Alliance
Vision Twain Toolkit does not really give you full programmatic control
of all the parameters of non-scanner devices and you won't be able to
avoid letting the Twain driver show the device specific configuration
dialog to manipulate specific settings.
In my own library I have low level functions to directly manipulate
Twain attributes but in order to be able to use that you would need a
through knowledge of the Twain specifications down to the API. That
together with the difficulties to support other devices I don't have
available, made us decide to not try to sell this Toolkit yet.
Rolf Kalbermatter
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

Using multiple motion driver versions on one system...(with Labview 6.1 and Labview 8.0)

Using Labview 6.1 and Labview 8.0 on same PC computer (my development system).
Labview 8.0 applications, I would want to use the motion 7.x drivers
Labview 6.1 applications, I want to use motion 6.x drivers
(Of course, Labview 6.1 can not use motion 7.x drivers).
When I installed Labview 8.0 and motion 7.x drivers, it removed my motion 6.1
drivers (and all the vi's) and installed motion 7.x drivers (with vi's).
Of course, Labview 6.1 applications can not run with motion 7.x drivers.
How can I keep my Labview 6.1 applications running and building
with motion 6.x drivers while still having Labview 8.0 applications
with motion 7.x drivers (all on the same system).
And then, of course, the executables, on other systems with the 6.x and 7.x drivers.

Unfortunately there is no way to install multiple versions of a
hardware driver on a single operating system. This is not only true for
NI Motion but for any type of peripheral hardware. Windows can only
assign a single driver to a specific piece of hardware.
From my point of view the best solution would be to upgrade your
LabVIEW 6.1 application to LabVIEW 8.0. If this is not possible for
some reason you could install a second Windows on another harddrive or
partition and install LabVIEW 6.1 and NI-Motion 6.x on this system and
LabVIEW 8.0 and NI-Motion 7.x on the other one.
Best regards,
Jochen Klier
National Instruments Germany

I believe a website has attached itself to Firefox, such that once a day when I bring Firefox up, it opens a window with it's website and I can't get rid of it.

In the morning, after I bring up the computer (An Apple), I launch Firefox. Inevitably, another window opens up behind the Firefox window with advertisements. It goes by "Pulse 360" and if you Google it, people are always complaining about how to get rid of it. It's possible it's not connected to Firefox, but it always comes up after I launch it, even if I have used other applications prior to Firefox. I would reinstall Firefox, but hate to lose all the bookmarks I have. Any help would be appreciated.

Reply: Cor-el > Excellent!! Thank You. In Tools, Add Ons, Extensions there was a Default Tab enntry which was the culprit. Am running W7 so the XP Tools, Options, Advanced , Use Hardware acceleration when available, wasn't of much help here, however I did fix a problem on another computer running XP with that same fix. Thank You very much! HD

Using RSLinx OPC with Labview 2009 SP1 and Getting Wierd Problem

I have a small test system with 4 analog inputs and 4 analog outputs. Oddly, I can use the Labview Distributed Systems Manager and read the input (level) changes and stroke the analog outputs (valves). However, when I go into a VI, I can get the level readings (only the first time I enter, after that not), but can never stroke the valves. Looking at the shared variable setup in both the project I am using and the Distributed Systems Manager, I have them both set up the same as a PSP with the same OPC reference, although formerly the project used project-attached shared variables.

Using the timed structure set at the same acquisition rate as the OPC interface corrected the problem.

How close can I come to Realtime with Labview student edition and an Arduino project?

Hey everyone,
I'm really new to Labview and just recieved the Labview 2012 student edition and I plan to do a project. It came to my concern that after asking the Labview interface for arduino forums, they suggested that it cannot provide realtime.My project in generalwill consist of two arduinos, one with many sensors close to 30 and the second will have many actuators. My question is whether I can come to develop a realtime crucial system or fast processing speeds. Please provide any input.Your time and responses are much appreciated.

MustafaMX5 wrote:
Thanks for replying, but if I may ask, are you implying that when the arduino is programmed it will run in realtime, however when labview interfaces with it isn't. Then if so would you suggest I just program the arduino and then monitor the system using Labview as my GUI.Lastly say I had the two arduinos already programmed with sensors and actuators and they communicate independently without labview, would labview impede on this time critical system.
Thanks A Lot
Anything on a Windows machine is not real-time. The micro on the arduino is. You can still program in communications between the micro and LabVIEW and not impede on the real-time operation. It will take some cycles away, but probably not enough to worry.
There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Unofficial Forum Rules and Guidelines

How to open a new window with no Portal Header and Portal Navigation bar

Hi,
I am working with the EPCM.doNavigate() method and passing the value "1" for the mode parameter in order to open it in a seperate window without the Portal header.
For some reason, the Portal header is still seen in the new window.
Do anyone know the reason?
Thanks,
Aviad
int openType = 1;
"EPCM.doNavigate(\""Url"\", "openType"); \n"

Hi Aviad,
Try out the command
EPCM.doNavigate(\""Url"\", "openType",'toolbar=no','status=no','menubar=no');
<b>Put opentype=1</b>
I think it will work
Thanx & Regards
Anish

Backward Compatibility with Labview 6.0 and 6.1

Hello,
I am having the same problem as discussed in the following message board of yours:
"how to open a vi (made in version 6.1 labview) in version 6.0"
One of your support staff offered to take a user's version 6.1 vi, open it and Save As a version 6.0 vi.
Could you please do the same thing for me? I have attached a vi that was created using version 6.1, however, I am trying to do some work at home. Unfortunately, I only have version 6.0 at home. Version 6.1 was only installed in my research lab.
In case simply saving the vi as a 6.0 version will not sole the problem, could you take screen shots of the front-panel and block-diagram and then just attach the jpeg's?
Thank you,
Charles
Attachments:
chuckmot_6p0.vi ‏72 KB

Hey Chuck:
I think I sent you the wrong file…
These are the ones that the program created, after converting to 6.0 (I hope)
Best wishes and Fight on!
Santiago
Attachments:
chuckmot_6p0.vi ‏67 KB
AI0.vi ‏35 KB
AI1.vi ‏37 KB

Switch windows with Finnish keyboard (cmd- and )

Has anyone gotten it to work? It works with US keyset, but not finnish.

Yes, that's what I'm using. Neither "cmd-<" work with finnish (or finnish extended) keyboard layout.

Fieldpoint Hardware Drivers that are compatible with LV 8.5 and Windows Vista

I trying to develop in LabVIEW for some Fieldpoint hardware. I was going to download the hardware drivers from NI, but only see drivers that are compatible with Windows XP and LV 8.2
Or, am I just misinterpreting this?
Also, are there any potential conflicts with me developing on Vista, if my end-user, is uding another OS?
Daddy-O
One should welcome adversity as an opportunity to excel.

Hi Daddy-O,
Thank you for contacting National Instruments. This is a little misleading, and unfortunately the driver you are looking for is currently not directly searchable. In order to use your FieldPoint hardware with LabVIEW 8.5 and Windows Vista, you will need the FieldPoint 6.0 driver. This can be found within the disk that is distributed with new FieldPoint hardware, and any Device Drivers CD from August 2007 forward. Unfortunately, a standalone installer is not available for this driver, and if you do not have a hard copy of the Device Drivers, you can download this here. From this installer, you should be able to select FieldPoint 6.0 and install this software.
I hope this helps! Let me know if there is anything else I can clarify. Have a great day!
Jason W.
National Instruments
Applications Engineer

Windows virtual machine with labview on a Mac

I am about to buy a Mac laptop with virtualization software (either VMware or Parallels), then create a Windows 7 virtual machine and put Labview for Windows Professional on it.
I searched the board and found some discussion of this configuration but it is several years old.
I would just like to hear from people who have done this and learn from their experiences. Are there any pitfalls, features that don't work, performance problems, setup difficulties, whatever. Also, do you prefer VMware or Parallels.
One other thing: I would like to create at least four virtual machines (Windows with Labview development, Windows without LV to test the applications in a non-labview environment, and similar for MacOS}. Is this a reasonable thing to do?
Regards,
David

Hi David,
As indicated above I have been running a windows virtual machine using VMware on a 17 inch macbook pro for quite a while now. I have not experienced significant problems. Labview and labview generated apps work fine in the virtual environment.
But would I do it again? I think not. The economics don't work. You can buy a quite capable Windows laptop for less than $500. The virtual machine alternative costs $200 for a copy of Windows, $80 for virtualization software (Parallels or VMware) plus extra memory on the Mac (I have 8 gb) plus a more powerful machine, etc. I ended up paying over $3,000 for the Mac hardware and extra software. The alternative would have been $1,500 for a 15 inch Mac plus $500 for a Windows laptop.
Also, there is definitely a performance penalty. Virtualization is not free. Start up and shutdown times for Windows are more than twice as long under VMware than with a cheap HP laptop.
It is nice having all my files (Mac and Windows) on the same machine but I could have easily networked the Mac and Windows and had effectively the same result. Expected benefits, such as a single backup disk for both operating systems didn't work out. Apple's time machine software views the entire Windows environment as a single lump, so I am still stuck with two backup drives.
So the good news is that it works. The bad news is that the costs (in my opinion) exceed the benefits.
David'

Windows 7 with labview 8.5 and NI-8451

Similar Messages

Maybe you are looking for