PXI-2564 RLP

I'm trying to find RLP information for the PXI-2564 and PXI-2570 relay cards, can someone point me in the right direction?
I'm trying to run in RedHat 6 64-bit.
Thanks

Johnbull,
The short answers is yes, but due to its ability to potentially damage the hardware if used incorrectly we generally try to keep this as internal as possible.
Normally we would suggest you to attempt to use Linux NI-DAQmx 8.0.2 to program your device [as both the 2564 and 2570 are supported]. There may be some changes you might need to make in the installer as this is designed for Red Hat Enterprise Linux WS 4 but this has been done by many others in the past.
That being said if this does not work for you, and you NEED Register Level Programming, it would be best to call in to NI Support (1-866-ASK-MYNI) as we have some options* for you.
*These options are officially unsupported by R&D, and can not be published externally [hence the need to call in for support].
Frank,
National Instruments
Staff Software Project Engineer

Similar Messages

PXI 2564 how to

I am trying to power a solenoid valve that needs 24V supply. I have a PXI 2564 slot which I am planning on using to supply the voltage and then turn it off (or relay) when I want the valve opened and closed. My question is to how I am supposed to (or how it is conventionally done) connect everything. I was planning on getting the 37 pin dsub connector to pin connector piece (shown in the link). Would I then just need to buy a 24V DC power supply and strip the output wires and put them into 2 of the pins on the connector? Also, is there any way to monitor/change current and voltage or does the 2564 simply just relay??
http://sine.ni.com/nips/cds/view/p/lang/en/nid/210164

Hi lvuser333,
Conceptually, what you are saying seems correct. You will have to be careful with the Dsub connector you choose. Not all of them are rated to withstand 24V, but the one you linked should be compatible with your application, assuming you aren't pushing more than 5A through it.
What do you mean by strip the two output lines?
It should be fairly simple. For instance, you could feed 24V to Channel 0 and connect your solenoid to COM 0. Then, when the switch closes the connection, you are powered on, and when it opens, you are powered off. A module like the PXI-4142 would likely be suitable for you.
I am not sure I understand your last question. The 2564 is simply a relay card, but you can modify what power is output by the power module.
I hope this helps.
Best Regards,
Thomas B.
National Instruments
Applications Engineer

Where i can find exemples for PXI-2564 relay module

hello,
I'm beginner in PXI module using.
I bought a PXI solution for use it as a custom instrument.
My aim is to read RTDs and command some line using relays.
So i take the system below:
NI PXIe 1071
    PXI-8100
    PXIe-4357
    PXI-2564
I can see all the material on NI MAX.
In MAX, i can read RTD a channel value and can operate relays.
i have read and practice exercice on "Getting started with Labview RT module" and all it works,But i don't find any resources or exemple to deal with relay card or read RTD.
I have try to access it using "visa connect" and this step works, but what must i do to go further.
In a first time i want to swap relay position, by reading position, invert value ,set position and return the value.
And for RDT i'll want to make a simple measure and make a average a N measure for 1 or all input.
Can you give me some exemple or trick?
Best regards

Hello,
What software do you use? what version?
Have you look into the LabVIEW Example Research with KeyWord "Relay". There are examples with NI-DAQmx and niSwitch drivers.
Thanks
Brice S.
National Instruments France

NI PXI-2564 115Vac 400Hz max current 4 amps

Can the NI PXI-2564 handle 115Vac 400Hz max current 4 amps?

RFB-AIS,
My apologies, on further examination, it turns out you should be all set. The maximum relay operate time is not actually associated with the frequency of your signal. The important characteristics are the switching current and voltage, and combined power, which a"must not exceed 30 W at 150 VDC, 150 W at 30 VDC, or 150 VAC, 5 A" according to the product manual--http://www.ni.com/pdf/manuals/373963h.pdf
All of your signal characteristics satisfy those requirements, and you shouldn't have any issues operating at 400 Hz.

Solenoid valve baseline

Hi, I know there is a lot of info on solenoid valves on the forums, but I am looking to establish myself a starting point. I need a solenoid valve (or any valve that can be controlled, really) that will allow me to open and close the valve fairly rapidly (less than 1 second) so I can control the level of liquid in a container. There will constantly be liquid on one side (the top side of the valve when in vertical position), and the valve will open for a short amount of time until a few mL are dispensed and then close. I read alot about needing a DAQ or a relay board, but is there anything out there that I can just plug into the wall to power and then have a usb or other wire run to my PXI to easily open and close it? I have PXI card slots 4130,2564,8232,4065,8101.
For example, could I just use something like the coleparmer valve below and just supply 24V from the PXI 4130 to open it and then remove voltage to close it?
http://www.coleparmer.com/Product/Cole_Parmer_Low_Flow_Direct_Lift_Proportioning_Solenoid_Valve_0_02...
http://www.grainger.com/Grainger/RED-HAT-Solenoid-Valve-6WTP4?Pid=search
Solved!
Go to Solution.

The PXI-4130 is capable of sourcing 20V at 2 amp which should be more than adequate to drive the valve (the current requirements are missing from the spec sheet on the website) but it's kind of like bringing a bazooka to a fist fight. The PXI-2564 is better suited becuase its' a simple bank of contacts but you will need an external 24 V supply.
Going USB could add a whole other layer of complexity depending on the device driver. If you have labview and access to the hardware you listed then this type of application is relatively simple to create.
Here is a great article on implementing a closed loop on/off controller: https://decibel.ni.com/content/docs/DOC-16199.
And to answer your orignal question...yes, solenoids usually work as you described - apply power to open, remove it to close.
Philip
CLD

Power control switch for 115VAC wall outlet to operate resistance heating element.

I am very new to LabView software as well as hardware
interfacing, so don't presume that I know anything. My problem seems
simple, I want to be able to control and automate via LabView software a resistance
heating element that can plug into a standard 115VAC wall outlet. I
searched through the Knowledge Base and found this comment:
http://digital.ni.com/public.nsf/allkb/855AF9CBDAACE3018625725A00638653
The PXI 2564 seemed ideal but I have no clue how to connect the serial port to
my heating element, or even if this is enough current (5A, do heating elements
need a certain wattage?) I had originally envisioned a simple surge
protector like device that had computer control options. Many devices
like this are available, however all the ones I have found are web-accessed via IP address
and I am unsure how to interface this type of device with LabView if it has its
own GUI. Obviously I have no idea what I am doing here so any help would
be much appreciated. The heating element requires 115VAC or DC it does
not matter, and all I need to do is turn the power on and off, no variance is
required, although that could be very useful. I have implemented a NI
CompactDAQ for other control and measurement (24VDC Digital I/O and Thermocouple) if this
could somehow play into my solution, but I believe the limits on voltage for
this device are much lower. Thanks!

Hi Anfu,
LabVIEW gives you the power to control and automate all National Instruments hardware using NI drivers (i.e. NI-DAQmx).  I have a couple of NI hardware suggestions, but it's up to you to decide on the hardware that will best fit your application. Even if you end up using third-party hardware, I think you will find LabVIEW is a great interface to control and/or automate your hardware.
The resistance heating element you want to control...you state it is powered via wall voltage, but you did not state the required current. This is important information you should be able to find in the heating element's data sheet. The amount of current you need at 115 VAC (or DC) will determine your desired relay characteristics. Once you know the voltage and current (or power) the heating element requires, you can calculate the hardware specifications that are necessary for your application - and can confidently select the correct hardware.
Starting from the fact you need to switch wall voltage, you will want a switch rated for Measurement Category II (CAT II). This classification ensures you will be kept safe from the high voltages being switched.  National Instruments has PXI hardware that can switch wall voltages, as you mentioned previously, and one of these switches is the PXI-2564.  Your computer would communicate with the PXI-2564 through its PCI bus, not its serial port. Several methods to connect your PCI bus to PXI is to purchase a MXI-4 card (this would fit in one of your computer's PCI slots) that cables to a PXI chassis (in which the PXI-2564 is located). Also, you can purchase an embedded PXI controller (then you wouldn't need a separate computer, as the embedded PXI controller houses a laptop-like computer). In total, you would need a PXI-2564, a PXI chassis, and either a MXI-4 or embedded PXI controller.
If PXI doesn't seem ideal, instead you could create a Plug-and-Play (PnP) SCXI system!  First, choose a SCXI switch module (such as a SCXI-1127). Then, you can purchase a USB-1357 to control the SCXI-1127 module from one of your computer's USB slots. In total, you would need a SCXI-1127 module, a 4-slot SCXI chassis, and a USB-1357.
Another option is the SCXI-1161. Unfortunately, the USB-1357 doesn't connect to the rear of the SCXI-1161, but there is there are two additional options available for controlling the SCXI-1161. One is to purchase a PCI DAQ module (or use one if you already have one) and connect it to the SCXI-1161 using the SCXI-1349. The other is to purchase a SCXI-1600 (which is a DAQ board, SCXI form factor) that you control via USB. In total, you would need a SCXI-1161, a 4-slot SCXI chassis, and a SCXI-1600 or a DAQ board and a SCXI-1349.
Either way, the PXI and SCXI options both give you the full functionality of a modular, LabVIEW-controlled switch. Upon purchasing the switch module, you also get the required drivers, getting-started and troubleshooting tools (such as the NI-SWITCH Soft Front Panel), and examples to get you up and running quickly.
In reference to the simple surge protector like device that has computer control options - I'm sure someone from the LabVIEW forum could assist you in communicating to one of these devices via the web. Don't worry, if the device can be controlled via the web, you're good to go.
Lastly, in response to your final statements, it is important to find out how much current or power the heating element requires because that will directly determine your required switch hardware specifications. You mention no variance is required, which is good, because the switch will simply turn on or off the power to the heating element. I agree a NI CompactDAQ option could be very useful for an application such as this, however there are no CAT II relay or switch modules for this form factor at this time.
Hope this helps!
Chad Erickson
Switch Product Support Engineer
NI - USA

NISwitch

Hi,
I am using Labview 2010 (10.0 32 bits) and TestsTand 4.2.1 with a PXI 1033 chssis. In the chassis, there are a PXI-6733, a PXI-7852R, a PXI-2564 and a PXI-2569.
The PC sometimes freezes with a "blue error screen" (look at the attached file).
The file niswdk.dll is in the NI SWITCH files, it is located at C:\Windows\System32\drivers. The version of the dll file is 2.0.1.49152. NI Switch version is 4 .0 .2
I had uninstall the NI Switch software and then I install again the NI Switch sofware but the problems still occurs.
Regards,
Attachments:
IMG_2013.jpg ‏132 KB

Hi Romain,
When you said "the PC sometimes freezes with a blue screen error", could you give more details about it?
I mean, are you executing specific LabVIEW code or are you doing others tasks before the blue screen occured?
This blue screen is quite strange, so it's important to know what make it happened.
Regards,
Celine
National Instruments France
#adMrkt{text-align: center;font-size:11px; font-weight: bold;} #adMrkt a {text-decoration: none;} #adMrkt a:hover{font-size: 9px;} #adMrkt a span{display: none;} #adMrkt a:hover span{display: block;}
Journées Techniques LabVIEW
Du 15 octobre au 7 novembre : Strasbourg - Lyon - Lille - Toulouse - Mar...

Is there any DDK, RLP or examples programming Relay cards PXI-2567?

I am trying to write a Device Driver for PXI-2568 Relay card. I can not find any Device Driver Kit (DDK) or Register level Programming (RLP) information. I program in Visual studio C++ using RTX. I have diver for M and E series ADC cards as well as DIO cards, but can not find any help for the relay cards. Where can I find any examples or other info?
Thanks,
Tony

Hi Tony,
I have RLP information on the PXI-2568, but the information is limited and may not give you all the desired functionality that you're looking for. If possible, can you provide me an email address to contact you personally? Because the information is somewhat limited, additional support may be required, so I would rather not make the RLP manual public. Also, I would like to discuss the caveats to the existing RLP manual and verify the information I have will make you successful. Please note the email address you provide will be public information (at least initially), so you may not want to use your primary email address.
Another option is requesting support through phone or email via http://www.ni.com/support/, however phone and email requests require a valid service contract.
Thanks in advance!
Chad Erickson
Switch Product Support Engineer
NI - USA

PXI-2800 Switch Block Register Level Programming

I have a PXI-2800 with 2815A and B wand was wondering if there are RLP specs that I can drive with the Linux NIMHDDK?
I have been successful with the Switch RPL, and was thinking this would be an extension. That does not appear to be the case, this card is a bit different.
Thanks

I'm a few steps down the learning curve from plosio so bear with me here. I'm trying to control a pair of PCI 6259 multifunction cards which live in a mac (G5, OS X 10.4.4) using the NI-VISA package and xcode. I have run the driver wizard, and put the inf file it created where the inf file said it wanted to go, and modified the find-resource example code so that the PCI macros get defined. Still the viFindRsrc function can't find my cards. I know they are there because mac's system profiler can see them. one thing that makes me nervous is that inf file lists WindowsNT for the operating system. Another thing that makes me nervous is that i was under the impression that the wizard was also supposed to make new VISA readable drivers (.kext files if i am not mistaken) for each card, and I don't see any new kernel extensions when I search the hard drive. Thanks in advance for any help.

FF answer for Register ID PXI 6509

Hi All,
I am using register level programming to program my PXI 6509. I am using a chassis with a PXI 8106 controller.
I manage to initialize the device, to read the manufacturer ID and the model. But when I reads the ID Register, I always get the answer "FF". Moreover, when I configure the P0 port for output and tries to update the value of the port to 1, the outputs are not at the value 5V.
I have linked my C code (I am using CVI).
Do you have any idea why I am getting the answer "FF"? Why are the values of the outputs not changing?
Many thanks in advance for your help,
Charlotte
Charlotte F. | CLAD
National Instruments France
#adMrkt{text-align: center;font-size:11px; font-weight: bold;} #adMrkt a {text-decoration: none;} #adMrkt a:hover{font-size: 9px;} #adMrkt a span{display: none;} #adMrkt a:hover span{display: block;}
>> "Du 11 octobre au 17 novembre, 2 sessions en parallèle : bien démarrer - approfondir vos connais...
Attachments:
CMD_PXI_6509_VISA.c ‏4 KB

Please see my reply here -- http://forums.ni.com/t5/Driver-Development-Kit-DDK/FF-answer-for-Register-ID-PXI-6509/m-p/1211487#M1...
Joe Friedchicken
NI VirtualBench Application Software
Get with your fellow hardware users :: [ NI's VirtualBench User Group ]
Get with your fellow OS users :: [ NI's Linux User Group ] [ NI's OS X User Group ]
Get with your fellow developers :: [ NI's DAQmx Base User Group ] [ NI's DDK User Group ]
Senior Software Engineer :: Multifunction Instruments Applications Group
Software Engineer :: Measurements RLP Group (until Mar 2014)
Applications Engineer :: High Speed Product Group (until Sep 2008)

PXI 7813R Register Level Programmer Manual available

Is the Register Level Programmer Manual available for the PXI 7813R module? Does a code example exist using Microsoft Visual C++ 6.0?
Thanks!!!

The RLP manual for the 7813R is identical to that of the 7831R, which you can get on the MHDDK page (go to the download link). The only difference is that you will need to use a different PCI device ID to identify the device, the PXI-7813R device ID is 0x7193. There are MSVC++ examples at the download link as well.
-Alan A.

Poor PXI IO performance on Latitude E6410 with ExpressCard 8360

Hello,
I have a Dell Latitude E6410 with a Core-i5 M520 which is giving me very poor io performance when using an ExpressCard 8360 card to connect to a PXI Rack.
The sustained IO rate that I can get appears to be about 1/3 of that that I can get using the same ExpressCard on a Dell Latitude E6400 (with a Core2Duo processor).
I am using the A05 bios (latest at time of writing) on the E6410.
Wade.

I am running Windows XP (32 bit) sp3 in both cases.
The E6410 has 4GByte of memory fitted.
The E6400 has 2GByte of memory fitted.
I have also use the same ExpressCard 8360 via a PXIe to ExpressCard Adaptor in a Desktop machine with similar performance figures to the E6400 - i.e. much better than the E6410.
The Desktop Machine is an HP Compaq D7900 with 4GByte of memory, Core2Duo E8500 also running Windows XP sp3 (32 bit).
Also, on the Desktop, I am running NI PXI Platform Services 2.3.2 and NI-Visa runtime version 4.3.
On the E6410, I am running NI PXI Platform Services 2.5.2 and NI-Visa runtime version 4.6.
I no longer have access to the E6400 so I am not sure what sofware versions were installed. However, they are unlikely to be new than the versions installed on the E6410.
Wade.

Choosing a PXIe controller for streaming 200 MBps

Warning: This is a long post with several questions. My appologies in advance.
I am a physics professor at a small liberal-arts college, and will be replacing a very old multi-channel analyzer for doing basic gamma-ray spectroscopy. I would like to get a complete PXI system for maximum flexability. Hopefully this configuration could be used for a lot of other experiments such as pulsed NMR. But the most demanding role of the equipment would be gamma-ray spectroscopy, so I'll focus on that.
For this, I will need to be measuring either the maximum height of an electrical pulse, or (more often) the integrated voltage of the pulse. Pulses are typically 500 ns wide (at half maximum), and between roughly 2-200 mV without a preamp and up to 10V after the preamp. With the PXI-5122 I don't think I'll need a preamp (better timing information and simpler pedagogy). A 100 MHz sampling rate would give me at least 50 samples over the main portion of the peak, and about 300 samples over the entire range of integration. This should be plenty if not a bit of overkill.
My main questions are related to finding a long-term solution, and keeping up with the high data rate. I'm mostly convinced that I want the NI PXIe-5122 digitizer board, and the cheapest (8-slot) PXIe chassis. But I don't know what controller to use, or software environment (LabView / LabWindows / homebrew C++). This system will likely run about $15,000, which is more than my department's yearly budget. I have special funds to accomplish this now, but I want to minimize any future expenses in maintenance and updates.
The pulses to be measured arrive at random intervals, so performance will be best when I can still measure the heights or areas of pulses arriving in short succession. Obviously if two pulses overlap, I have to get clever and probably ignore them both. But I want to minimize dead time - the time after one pulse arrives that I become receptive to the next one. Dead times of less than 2 or 3 microseconds would be nice.
I can imagine two general approaches. One is to trigger on a pulse and have about a 3 us (or longer) readout window. There could be a little bit of pileup inspection to tell if I happen to be seeing the beginning of a second pulse after the one responsible for the trigger. Then I probably have to wait for some kind of re-arming time of the digitizer before it's ready to trigger on another pulse. Hopefully this time is short, 1 or 2 us. Is it? I don't see this in the spec sheet unless it's equivalent to minimum holdoff (2 us). For experiments with low rates of pulses, this seems like the easiest approach.
The other possibility is to stream data to the host computer, and somehow process the data as it rolls in. For high rate experiments, this would be a better mode of operation if the computer can keep up. For several minutes of continuous data collection, I cannot rely on buffering the entire sample in memory. I could stream to a RAID, but it's too expensive and I want to get feedback in real time as pulses are collected.
With this in mind, what would you recommend for a controller? The three choices that seem most reasonable to me are getting an embedded controller running Windows (or Linux?), an embedded controller running Labview real-time OS, or a fast interface card like the PCIe8371 and a powerful desktop PC. If all options are workable, which one would give me the lowest cost of upgrades over the next decade or so? I like the idea of a real-time embedded controller because I believe any run-of-the-mill desktop PC (whatever IT gives us) could connect and run the user interface including data display and higher-level analysis. Is that correct? But I am unsure of the life-span of an embedded controller, and am a little wary of the increased cost and need for periodic updates. How are real-time OS upgrades handled? Are they necessary? Real-time sounds nice and all that, but in reality I do not need to process the data stream in a real-time environment. It's just the computer and the digitizer board (not a control system), and both should buffer data very nicely. Is there a raw performance difference between the two OSes available for embedded controllers?
As for live processing of the streaming data, is this even possible? I'm not thinking very precisely about this (would really have to just try and find out), but it seems like it could possibly work on a a 2 GHz dual-core system. It would have to handle 200 MBps, but the data processing is extremely simple. For example one thread could mark the beginnings and ends of pulses, and do simple pile-up inspection. Another thread could integrate the pulses (no curve fitting or interpolation necessary, just simple addition) and store results in a table or list. Naievely, I'd have not quite 20 clock cycles per sample. It would be tight. Maybe just getting the data into the CPU cache is prohibitively slow. I'm not really even knowledgeable enough to make a reasonable guess. If it were possible, I would imagine that I would need to code it in LabWindows CVI and not LabView. That's not a big problem, but does anyone else have a good read on this? I have experience with C/C++, and some with LabView, but not LabWindows (yet).
What are my options if this system doesn't work out? The return policy is somewhat unfriendly, as 30 days may pass quickly as I struggle with the system while teaching full time. I'll have some student help and eventually a few long days over the summer. An alternative system could be built around XIA's Pixie-4 digitizer, which should mostly just work out of the box. I prefer somewhat the NI PXI-5122 solution because it's cheaper, better performance, has much more flexability, and suffers less from vendor lock-in. XIA's software is proprietary and very costly. If support ends or XIA gets bought out, I could be left with yet another legacy system. Bad.
The Pixie-4 does the peak detection and integration in hardware (FPGAs I think) so computing requirements are minimal. But again I prefer the flexibility of the NI digitizers. I would, however, be very interested if data from something as fast as the 5122 could be streamed into an FPGA-based DSP module. I haven't been able to find such a module yet. Any suggestions?
Otherwise, am I on the right track in general on this kind of system, or badly mistaken about some issue? Just want some reassurance before taking the plunge.

drnikitin,
The reason you did not find the spec for the rearm time for
the 5133 is because the USB-5133 is not capable of multi-record acquisition. The rearm time is a spec for the reference
trigger, and that trigger is used when fetching the next record. So every time you want to do another fetch
you will have to stop and restart your task.
To grab a lot of data increase your minimum record size. Keep in mind that you have 4MB of on board
memory per channel.
Since you will only be able to fetch 1 record at a time,
there really isn’t a way to use streaming.
When you call fetch, it will transfer the amount of data you specify to
PC memory through the USB port (up to 12 MB/s for USB 2.0 – Idealy).
Topher C,
We do have a Digitizer that has onboard signal processing
(OSP), which would be quicker than performing post processing. It is
the NI 5142
and can perform the following signal
processing functions. It is
essentially a 5122 but with built in OSP.
It may be a little out of your price range, but it may be worth a
look.
For more
information on streaming take a look at these two links (if you havn’t
already).
High-Speed
Data Streaming: Programming and Benchmarks
Streaming Options for PXI
Express
When dealing with different LabVIEW versions
it is important to note that previous versions will be compatible with new
versions; such as going from 8.0 to 8.5.
Keep in mind that if you go too far back then LabVIEW may complain, but
you still may be able to run your VI. If
you have a newer version going to an older version then we do have options in
LabVIEW to save your VI for older versions.
It’s usually just 1 version back, but in LabVIEW 8.5 you can save for
LabVIEW 8.2 and 8.0.
ESD,
Here is the link
I was referring to earlier about DMA transfers. DMA is actually done every time you call a
fetch or read function in LabVIEW or CVI (through NI-SCOPE).
Topher C and ESD,
LabVIEW is a combination of a compiled
language and an interpreted language.
Whenever you make a change to the block diagram LabVIEW compiles
itself. This way when you hit run, it is
ready to execute. During execution LabVIEW
uses the run-time engine to reference shared libraries (such as dll’s). Take a look at this DevZone article about
how LabVIEW compiles it’s block diagram (user code).
I hope all of this information helps!
Ryan N
National Instruments
Application Engineer
ni.com/support

Convert PXIe-8135 controller to dual-boot Windows 7 and LabVIEW RT

Hello. I have a PXIe-8135 controller that originally was just running Windows 7. We are trying to convert it to a dual boot system to also run LabView Real Time. (There is host computer that will run LabVIEW 2014 with the RT module, and the controller will become a target).
I have created a FAT32 partition on the hard drive of the controller. Now, I’m trying to install the real-time OS with a USB flash drive made using the MAX utility, but I cannot boot using the USB drive for some reason. I keep getting the message “waiting for USB device to initialize”.
In BIOS, legacy USB support is [ENABLED] and boot configuration is set to [Windows/other OS]. I’ve tried removing the drive, waiting, and reinserting. I’ve tried two different USB drives (both 8 GB, different brands).
I’m not sure what to do next. Apart from the USB boot issue, is converting the PXIe-8135 even possible? I read about SATA/PATA hard drive issues with older controllers, but I don't know about this one.
Thanks, in advance, for your help!
-Jeff
Solved!
Go to Solution.

Per Siana's licensing comment, more information on purchasing a deployment license if you do not have one for this target can be found here.
The RT Utility USB key is used to set up non-NI hardware with LabVIEW Real-Time, but you should not need it in this situation to convert to dual-boot (*). Try this:
1. Since you already have a FAT32 partion created, go into BIOS setup and change to booting 'LabVIEW RT'.
2. The system will attempt to boot LabVIEW RT, see that the partition is empty, and switch over into LabVIEW RT Safe Mode. (this safemode is built into the firmware, which is why you don't really need the USB key).
3. The system should come up correctly and be detectable from MAX, and you can proceed with installing software.
4. To switch back to Windows, go back to BIOS setup and choose 'Windows/Other OS'
(*) One area where the USB key is helpful on a dual boot system is with formatting the disk. If you want to convert from FAT32 to Reliance on the partition designated for LabVIEW RT, the USB key lets you attempt to format a single parition and leave the rest of the disk untouched. If you format from MAX, the standard behavior is to format only one RT partition if found, but if not found, it will format the entire disk. Formatting from MAX on a dual boot system is consequently riskier and you could lose your Windows partition.

Start and Stop Trigger using PXI-6120 and DigitalStartAndStopTrigger.vi not working :-(

Hello,
I've been trying for a while now to get my PXI unit to capture a waveform between a Start and Stop (Reference) Trigger using the NI example DigitalStartAndStopTrigger.vi downloaded from the NI website. However, whilst the start trigger and stop trigger seem to be working i.e. the VI runs and stops at the correct times there is never any data read from my DAQmx compatible PXI-6120 card. So I can see the VI is running around the aquisition loop but the Property Node AvailSampPerChan is always returning zero... this has me slightly puzzled. I thought this might just be a driver issue so I've updated my box to the following software versions (see below) and installed the latest drivers e.g. DCDNov07.exe (also from the NI site) but nothing has changed.
my software as of now.
Labview 7.1 (with the 7.1.1 upgrade applied)
Max 4.3.0.49152
DAQmx 8.6.0f12
Trad DAQ 7.4.4f7
before I updated I had the same problem but with the following versions:
Labview 7.1 (with the 7.1.1 upgrade applied)
Max 4.2.1.3001
DAQmx 8.5.0f5
Trad DAQ 6.9.3f4
So to cut a long story short I still have the same problem with the triggers... does anybody have any ideas what is going wrong?
To add insult to injury it the traditional DAQ example ai_start-stop_d-trig.vi was almost working correctly before I did the upgrade. It had the strange behaviour of capturing the AI0 channel but on the wrong edges (e.g. if I set Start on Rise and Stop on Fall it would do the opposite, Start on Fall and Stop on Rise).
I'm going to leave my box doing a mass compile over night but i'd really like it if someone could suggest a solution or point me in the right direction.
Many thanks,
Mike

Hi Graham
I'm out of the lab today but I'll try and answer your questions as best I can...
1) What are the values you have set for Buffer size, Rate, samples per read and post trigger Samples?
At the moment I have all the values (e.g. sample rate, buffer size etc) unchanged apart from the ones I mentioned in my previous post (see above). I have in the past played around with changing the buffer sizes and rates in the example VI but as this appeared to have no effect on the behaviour I now have them setup as in the download.
2) Does the program end after the stop trigger is implemented?
Yep, if I toggle the trigger line high then low I see the program exits the read loop and the VI stops running as expected.
3) Lastly can you give me the details of triggering method. Are you
using a digital train of users set digital pulses? how long is the
program running.I'm using the WriteDigChan.vi to manually toggle the first digital line of the PXI-6733 card which is wired directly to PFI0 of the PXI-6120 card. Generally, I just start the VI running and then toggle the line high, wait a couple of seconds and then toggle it low.
To me it all looks like it should be acquiring samples but as I said yesterday it just refuses to fill the buffer with any data (and hence no samples are read).
Any ideas? and thanks for you help,
Mike

PXI-2564 RLP

Similar Messages

Maybe you are looking for