PXI-8110 Windows 7

Hey Folks!
IT keeps nagging me with my Windows XP on my PXI-8110 + Hypervisor.
I've to install Window 7 on it. Is anybody here, who did this before? Any complains about it, or caveats I've to take care of? Instructions maybe?
Thanks,
Stefan
Yet is not alldays evening

Hi Stefan,
unfortunately, we cannot provide you the instructions, since it is not trivial to do as I mentioned before. Hence, we cannot guarantee anything what would happen if you decide to install Windows 7. Moreover, if you go to the NI support page for your PXI 8110
http://sine.ni.com/psp/app/doc/p/id/psp-876/lang/en
you will notice that drivers and all support materials are based on the XP version. Consequently, we do not recommend you to change the O/S.
Best regards
Anoj Mubarak
National Instruments

Similar Messages

Multiple (3 or more) monitors for PXI 8110 controller?

I'm just fishing for help from the NI community out there to help a customer: has anyone had success using the PXI 8110 with multiple (3 or more) monitors? I believe it can inherently support 2 monitors. We've tried ADlink and Peritek cPCI cards without success.
If so, please share how you accomplished it. Thanks!
Daniel Lin
Field Sales Engineer - Western New England

The Apple OS hates unmatched video cards.. and Photoshop CS4 shows you that clearly.
I started with 2 nVidia 7300s... upgraded to 1 nVidia 8800 and kept 1 nVidia 7300... crashed every 10 minutes it seems.
Then upgraded to 2 nVidia 8800s. I still get 1 or 2 crashes a day but nothing near what I got with unmatched video cards.
Based on all my research and the crash reports posted it seems clear that the primary cause of the issue is Apple video drivers and their inability to tell the cards apart.In many cases my crashes were occurring because the drivers were asking the 7300 to do things it simply could not do. I found with the matched 8800 cards most days things run fairly smoothly. I will get a crash or two a day, but I can tell immediately when Photoshop is going to crash. Not that that is any help. But I can at least work now. I just must relaunch PS a couple times and save often.
From what I've found there's little you can do. Basically matched video cards help a great deal but they aren't perfect. Remove one card so you are only using a single video card, or wait for Apple to fix drivers (OS10.6 in Sept maybe???). This is clearly a case where Apple embedding drivers in the OS can be an issue because you can't simply download an ATI or nVidia update and install it.
The one thing I haven't tested with the matched 8800 cards is to turn off OpenGL since that's a primary reason for my upgrading (rotating canvas is a life saver). Turning off all Open GL features may make PS more stable on my system with matched cards. I'm not certain. I can definitively tell you that unmatched video cards are a nightmare and matching 8800s are pretty good. Nothing I'm up in arms about and I have the GL features to use.

PXI-8110 Available IRQ Lines

Can anybody tell me now many IRQ lines are available for the PXI bus on a PXI-8110? Specifically, I would like to manually assign numbers in the BIOS for particular slots.
Thanks.

Hi Jodye,
IRQ lines are generally not specified in the user manuals. What kind of application are you look for with this information? Is it essential for you to set the IRQ lines manually?
Best Regards,
Jignesh P

Pxi-8106のwindowsアップデート

お世話になります。
PXI-8016を使用しております。
OSはwindows xpなのですが、
この度windows7へとアップデートを予定しております。
外付けCD/DVDドライバを利用し、普通のPCのように、アップデート出来ますでしょうか?
よろしくお願いします。

t3さん
ドライバは、以下のとおりVista用までしか入手できないようです。
NI PXI-8106 Peripheral Drivers - Windows Vista/XP
http://www.ni.com/download/ni-pxi-8106-peripheral-drivers/1442/en/
ここで以下によるとVista用のドライバを使用してWinodows 7のインストールを試みたがだめだったとのことでした。PXIではなくPXIeであったり他の詳しい状況はわかりませんが。ただ以下のBIOSアップデートを行えばうまくいかもしれません。
Windows 7 drivers for PXIe-8106
http://forums.ni.com/t5/PXI/Windows-7-drivers-for-PXIe-8106/td-p/2576511
NI PXI-8106 BIOS 2.0 - USB Drive Image - Windows 7/Vista/XP 32-bit/2000 (こちらはWindows 7との記載があります)
http://www.ni.com/download/ni-pxi-8106-bios-2.0/3788/en/
BIOSアップデート > Winodows 7インストール > Vista用のドライバインストール
でうまくいく可能性もあるかもしれませんね。

Controlling PXI-8110 watchdog

We are running a resource intensive application on the PXI-8110 and during the operation, the 8110 reboots. I believe this may be a built-in watchdog function? Is there any way to control this? Thanks.

Hi Wirehead,
You're right that the 8110 includes an onboard watchdog timer device, but this device won't reboot the system unless you explicitly arm it to do so. In other words, the timer must be enabled by software (using LabVIEW VIs), otherwise it cannot restart the system.
What OS are you using, and what is your application doing when it restarts? Does it always restart at the same point of execution?
Thanks,
Eric G.
National Instruments R&D

Running a PXI with Windows 7

Hey,
I have access to three NI machines (PXI-1042 chassis, PXI-8186 controller) that can dual-boot with Windows XP and Labview RT. Previously, these machines were used in the following setup: two computers attached via ethernet port, one running Windows XP and Labview 8.2 controlling the other running Labview RT. However, I recently obtained a set of Dell Optiplex 780s, all running Windows 7, and have since installed Labview 2010 on each. I have attempted to replace the Windows XP computer in the above setup with a new Windows 7 machine (with both the latest DAQmx drivers and the latest pxi drivers), and labview always tells me I don't have the correct plugins installed. Are there better drivers out there? If not, how can I control a PXI machine with a Windows 7 machine?
Many thanks

Hello bjw5,
At what point does this error pop up, when you click on Add device in the project>>existing devices>>and then choose the PXI? Was this project originally built in LabVIEW 8.2 and now saved to 2010? Do you have any other hardware you can try adding to the project? There should be no compatibility problems having a Windows 7 host computer. What version of the PXI platform software and DAQ mx drivers do you have?
Researching this error dialog it usually occurs when the project contains .dlls or DAQmx custom scales or tasks. Are all three PXI systems exhibiting this behavior, or are you just setting up this one to start? I appreciate your answers to these questions. On a side note, please keep your posts to one forum, this helps us focus our resources on the support side. This most likely has to do with the network/RT setup versus the actual LabVIEW project.
Thank you,
Deborah Y.
LabVIEW Real-Time Product Marketing Manager
Certified LabVIEW Architect
National Instruments

TCP server/client - PXI RT - Windows - Linux

Dear all,
I'm sorry in advance for such a newbie-question, but I could not figure it out with the help of the existing posts here.
My situation: LV 7.1 installed on Win XP and running on the RT target PXI 1031. In this PXI I have the NI PXI 8146 RT module. To this module I have connected a Fluke DMM via GPIB (btw changing to ISA driver instead of PCI was necessary for the 8146 module), all that works OK and I can read the voltage from DMM with no problem.
Now I have an Ethernet switch between the PXI, Win XP box and a Linux laptop. I can ping from Win box and Linux laptop to the PXI and to each other, connection is OK. What I want to do now is to get the voltage from the DMM via PXI into my laptop at least twice per second. The laptop will then be replaced by some fast data acquisition system running (independently from LV) on Linux so now I'm just trying to get the voltage value into Linux...
I tried "Simple Data Client" and "...Server" vi-s but no success yet. My networking skills are at "ping" level... :-)
Any hint would be appreciated. M.

Hello miraz,
there is a very powerful library for your exact use case:
http://zone.ni.com/devzone/cda/tut/p/id/4095
Alas, it requires at least LabVIEW 8.2.1.
Maybe the RT FIFO Example which is also available for LabVIEW 7.1 will help you:
http://zone.ni.com/devzone/cda/epd/p/id/1898
Regards,
Johannes
NI Germany 629650

PXI not showing up properly in MAX

Hey everyone,
I'm new to setting up remote systems in MAX and I'm having some difficulty. I'm using all LabVIEW 2011 versions of software with FPGA and RT modules. I'll start by listing the hardware I am using:
PXI-1042 Chassis
PXI-8110 Embeeded Controller
PXI-8231 Ethernet
PXI-6704 Analog Output
PXI-6602 Timing I/O
PXI-7813R Reconfigurable I/O
Of this list I am using the 8231 to connect to the chassis and I am primarily interested in using and getting working the RIO more so than the other cards right now. Here is what I have done so far and what has happened.
When I first plugged it in nothing showed up in MAX and so I did some searching and found that if I change the BIOS options and set them to LabVIEW RT and set the 'Reset IP Address' to 'Yes' that I could see the NI-PXI8110 in the remote systems directory. Under this is says that it is connected but there is no software installed. If you click on the software directory, a list of software appears so I'm not sure why it says nothing is installed but there is software listed.
Now even though there are all these cards in the PXI, nothing shows up under Devices and Interfaces. I tried to 'Create New...' by right clicking on it and then clicking on PXI Chassis, but I get an error that the the host only supports PXI Platform Services 2.0.0 or greather and that the target has earlier version. So I made sure that I had the latest PXI Platform Services (3.0.3) and I then I tried to follow the instructions by updating the VISA software it should update the PXI Platform Services on the target. Now it won't let me do this without updating a bunch of other software on the target such as LabVIEW RT - current it has 10 and it needs 11. This wouldn't be a big deal but then another error comes up where I need a newer version of Hypervisor (target currently has 1.1). I downloaded Hypervior 2.0 and tried to install on my host and then subsequently add to target. I am running Windows 7 64-bit and there seams to be a support issue because it doesn't show up and the installer says it can't install certain parts due to incompatibility issues. Then I thought I'd try to install it directly to the embedded controller on the target by hooking up a monitor/keyboard/mouse. Even though the keyboard works in the BIOS, when at the Windows login screen I have no USB keyboard or mouse support therefore, I cannot login.
So there are a bunch of problems it seems that are plaguing me getting this system set up and running. I'm not sure where else to look and hopeully someone more knowledgable can give me some guidance. Thanks in advance for the help.

Hypervisor systems are a relatively new thing for NI as well, it allows you to run Windows and RT on the same system concurrently (one core goes to Windows, other cores assigned to RT). One interesting tidbit is that Windows and RT use different disk partitions, and the other tidbit is that when you're in "Hypervisor Mode" versus "RT Mode" you will have some collisions with software on the target.
It's unclear as to what you're trying to do with the system, are you trying to run Windows on the PXI controller and program/use the FPGA from the Windows environment, or are you wanting to use the PXI controller as an RT system and use the FPGA on the RT system in a "headless system" environment?
If you're going to use the system in RT mode, by setting the BIOS option to "LabVIEW RT" in the boot options, you must install LabVIEW RT. In the previous Hypervisor mode, Hypervisor RT + all the components were probably installed, but in this LabVIEW RT mode you need "Normal LabVIEW RT" + all the components. The system telling you there's no software installed is because none of the drivers are being loaded because you elected to boot "Normal RT" and the "Hypervisor RT" OS is on the system (instead of the "Normal RT OS").
There is an easy and safe thing to do here. Instead of booting "LabVIEW RT", boot "LabVIEW RT Safe Mode" and then go to MAX and right-click the device in MAX and say "Format Disk". This will safely format the RT partition, bringing it to a clean slate, and you can then install software and LabVIEW Real-Time to the controller. Then you can put it back into "LabVIEW RT" mode and use the controller like a regular RT controller. When your colleagues want to use it as hypervisor, they can put it back into "Windows/Other" mode and then reinstall Hypervisor onto the controller.
-Danny

Can't replace PXI onboard clock with PXI-6682 oscillator clock on PXI back plane

I have installed a PXI-6682 timing module in slot 2 of a PXI-1031chassis with a PXI-8110 controller running Hypervisor and RT. The 6682 is installed on the RT system under Hypervisor for GPS timing during measurements but I would like to put the TCXO on the PXI-1031 chassis backplane (replacing the PXI onboard clock). When I try to run the "Route Clock.vi" that I found in the example finder, all I get are error messages indicating that a parameter for this operation is invalid. The source terminal is "Oscillator" and the destination terminal is "PXI-Clk10_In". How do I determine which parameter is invalid? Any suggestions? Thanks
Solved!
Go to Solution.

Hi vugt,
I tested this out and have what I believe to be your final answer.
The short answer: The PXI-6682 can be used with NI-Hypervisor on the Windows side, but not on the Real-Time side.
The long answer:
While the NI-Hypervisor Manager allow you to put the PXI-6682 on two different systems, it is still only one PXI card on the PCI bus, so really only one system can access it at a time.
Therefore we need to assign both "devices" to either Windows or Real-Time. For our purposes, let's assume we assign it to Real-Time.
On an NI-Hypervisor system, each PCI interrupt line can only be assigned to one operating system. Either it can be assigned to Windows, or it can be assigned to RT.
Here is where the problem arises: The PXI-6682 needs to be located in a System Timing slot (generally slot 2). However, this slot (at least in the 1000B chassis I tested in) is located on the same PCI interrupt line as the chipset. Windows is required to have access to this PCI interrupt line, so devices used by Real-Time cannot be located on this interrupt line.
This prevents us from being able to use the PXI-6682 in Real-Time.
The NI-Hypervisor Manager will try to tell you to resolve this conflict by moving the PXI-6682 to slot 3, however, now the System Timing slot requirement is not met.
This does not prevent the card from being used on the Windows side of an NI-Hypervisor system, or on a purely Real-Time system.
Have a great day,
Chris V
Applications Engineer
National Instruments

Pxi-8106 driver

Hi,
I need to install windows 7 in a PXI-8106. I found this link with XP/Vista drivers :
http://digital.ni.com/public.nsf/allkb/E4503CC7E8BB41BA86256F7F006CBE8D
Can I install this on windows 7 ?
Thanks
Juan
Solved!
Go to Solution.

Hello
1) DEV C801 = GPIB Controller Interface Board
Should be resolved by installing the GPIB drivers:
http://www.ni.com/download/ni-488.2-3.1.2/4360/en/
2) Hardware ID ACPI\NIC7019
Should be resolved by installing the driver at the bottom of this post:
http://forums.ni.com/t5/PXI/Update-PXI-8110-image-to-Windows-7/td-p/1127928
3) Hardware ID Vendor 1093 = NI and DEV 71B9
I'm not a 100% sure, but this could be resolved by installing this driver:
http://www.ni.com/download/pxi-platform-services-3.2.3/4186/en/
Kind Regards,
Thierry C - Applications Engineering Specialist Northern European Region - National Instruments
CLD, CTA
If someone helped you, let them know. Mark as solved and/or give a kudo.

Simultaneously triggered acquisition: Multiple PXIe-7962R + NI-5734 cards, across multiple PXIe-1085 chasses

Hi all,
I need to do high-frequency, high-channel-count acquisition.
Specs
Signals: 10 MHz, 60 channels
Controller: PXIe-8135 (Windows 7)
Chasses: PXIe-1085 (2x)
Input cards: PXIe-7962R FlexRIO base with NI-5734 digitizer (15x)
Description
Each FlexRIO card will store data in circular buffers, and continuously monitor the voltage levels. When any one channel exceeds the user-defined threshold, all 60 channels need to be triggered simultaneously to pass waveform data (200 μs pre-trigger, 300 μs post-trigger) to the host OS for logging.
In other words, every FlexRIO card needs the ability to fire the trigger, which is then received by all 15 FlexRIO cards (the card that fires the trigger also needs to receive the trigger).
Question
Can I achieve this with only a single PFI line? Or do I need some other technique?
I've found some examples, but they only show single-source and single-card triggering, e.g. https://decibel.ni.com/content/docs/DOC-30182 uses one analogue input to trigger the acquisition of 2 channels on the same card.
Any advice would be much appreciated. Thanks!

Assuming you are using LV 2013 or 2014 you should download version 1.3.4 of the FlexRIO Instrument Development Library (FIDL). This will install 5734 Acquisition Engine examples which use the MultiRecord Library to stream data to the DRAM in a circular buffer, allowing you to recover pre-trigger samples. The example also demonstrate how to implement the Syncrhonization Library that synchronizes triggered acquisition to within a single sample period across multiple devices.
Getting the example to work across two chassis' may be difficult, but I believe it is possible. Though to do so you will need a timing and sync module in each chassis to distribute the triggers and reference clock that the sycnrhonization library requires.
National Instruments
FlexRIO Product Support Engineer

FTP and Windows 7

Looking for a little help. It's something I've had working with LabVIEW 2009 and Windows XP but just upgraded to LabVIEW 2011 and Windows 7. Trying to upload data files from a PXI to windows PC using ftp. I've set up the windows ftp server using IIS. I keep getting the following error from an ftp put file.vi:
Error 15550 occurred at FTP Transaction:
550 Cannot create a file when that file already exists.
There shouldn't be any permission problems and folder onto which they are writing is empty, I'm assuming it's more an issue with how I've set up the ftp server on Windows rather LabVIEW but if anyone has any suggestions what I may be doing wrong, it'd be appreciated.

The issue is probably on the IIS side.
http://support.microsoft.com/kb/969061
550 - The command is not executed because the specified file is not available. For example, this status code occurs when you try to GET a file that does not exist, or when you try to PUT a file in a directory for which you do not have Write access.
It may be related to your computer's firewall settings.
http://www.bunkerhollow.com/blogs/matt/archive/2010/06/16/tmg-2010-ftp-client-error-access-is-denied...
Now is the right time to use %^<%Y-%m-%dT%H:%M:%S%3uZ>T
If you don't hate time zones, you're not a real programmer.
"You are what you don't automate"
Inplaceness is synonymous with insidiousness

Non-windows tcp/ip

Hi,
I have a PXI 8184RT with LabView Real time 8.0. Also a have an instrument called Insensys that sense fiber optics strain sensors and send me an array of double values by TCP/IP. I have developed a software that works properly when I run it in a windows XP PC with LabView but when I download it to the PXI it works properly for some seconds and then the TCP/IP connection hangs. First I thought it was a RAM problem (128 M) but before installing the real time OS I used the PXI with windows XP and I didn’t have any problem getting the data from the Ethernet TCP/IP.
Does the TCP/IP functions need a windows PC somewhere to manage the communication?
thanks,
Juli

hola Juli:
Gracias por utilizar el foro. LabVIEW RT tiene una interfaz que se llama Real Time Sytem Manager (RTSM) que corre en el host y reporta la utilizacion del sistema usando RT. Si tu programa se traba puede ser porque tu Time Critical Loop esta mal temporizado y no está dando tiempo a que el Normal Time Loop se comunique con tu computadora ( esta puede ser una de las tantas razones)
con esa herramienta puedes descartar que sea un problema de memoria y puedes determinar qué tan bien temporizados estan tus ciclos.
te mando una liga donde puedes ver un poco mas de informacion al respecto:
http://ae.natinst.com/operations/ae/public.nsf/web/searchinternal/EEBB8194446EFC3386257186005314CD?O...
te marca algun tipo de error cuando ejecutas el programa?
Si quieres tambien podemos revisar tu codigo para ver de qué forma se puede optimizar para evitar tu problema.
Espero que algo de esto te haya servido y estoy a tus órdenes para cualquier otra cosa.
Saludos
Erwin Franz R.

PXI CPU usage

I am using PXI-8110 to develop in real-time an automotive application using a PXI-8513 CAN board and a relay controller board PXI-2567. When my application runs, I see that only one of the four CPUs seems to be used with a load near to 100%. How can I divide the load between the available CPUs?
Is it also possible to change the clock used by the PXI controller to execute my applciation (this could be useful to reduce execution time)?
Regards,
Claudio

Hi Claudio,
Depending on your application, you can distribute your tasks within LabVIEW between multiple loops to achieve parallelism. This will natively divide the processing between your available CPU cores. There is a lot of useful information on Multicore programming with LabVIEW here.
The other thing you mentioned was the CPU was running to near 100% while your application was running. Are you providing a source of timing within your execution structures (loops)? Unless you really need to run the execution flat out, it's important you give some time back to the processor. Even a ms per execution cycle should see a significant drop in it's load while the application is running.
Unfortunately it's also not possible to change the clock speed of the PXI controller, but you can use timing within your software to vary the execution time for certain tasks.
Let me know if this helps.
Paul
http://www.paulharris.engineering

PXI invalid sytem disk

最近PXIシステムを購入したのですが、PXI-8186にWIndows OSをインストールしようとすると、"Invalid system disk"というエラーが出てきてうまくいきません。CD-ROMドライブはNIが推奨しているTEAC社製のものを使用しているので、CD-ROMの相性の悪さが原因とは思えません。どうしたらOSをインストールできるようになるでしょうか。

お世話になっております。
日本ナショナルインスツルメンツ、湯田と申します。
Leorge様
ご返答ありがとうございました。
MNaka様
OSをインストールする際に表示される"PXI Invalid System Disk"の問題についてですが、
ハードドライブよりもCD-ROMが先にブートすることで、
正常にドライブを認識し、CD-ROMからインストールすることができるかと思いますので、
以下の方法で今一度ご確認のほどよろしくお願いします。
１．起動画面にて、"Delete"キーを押し、BIOS画面に入る
２．"Boot"タブに移動し、USB CD-ROMが認識されているか確認する
３．USBデバイスをハイライトし、＋キーでUSBデバイスを一番上に移動する
４．F10キーを押してBIOSでの変更を保存する
上記の設定を行いますと、CD-ROMが一番最初のブートデバイスとして認識されるため
インストールできるかと思います。
以上ご確認よろしくお願いいたします。

PXI-8110 Windows 7

Similar Messages

Maybe you are looking for