PXIe-8135 Watchdog

Hello,
I'm putting together a testing rack that will be used to control a system during testing. The heart of the rack is a PXIe-1065 chassis with PXIe-8135 controller. The rack will be controled remotely through Remote Desktoping into the controller (this is necessary because the test involves pressurizing sections of the system high enough that it is dangerous for any personnel to be in the room while the system is pressed up). The test control software will not be LabView, but our own software that interfaces with the modules in the PXIe chassis.
I would like a watchdog in the rack to monitor the PXIe controller and restart it without any need for someone to go in the room in the event that the system freezes up or otherwise becomes unresponsive. I'm aware of some possible solutions for a remote restart (Intel AMT, remote-controlled power strip), but response times on those could be too slow depending on the state of the rack when it goes unresponsive. I'm fairly certain I'm not the first to do this, so I was hoping to get some info and ideas.
From browsing the manual, it looks like there are watchdogs internal to the controller, but these are not accessible unless your using LabView RT. Anybody know if that is correct?
Are there any other options for a watchdog internal to the PXIe controller?
If not, any recommendations for getting an external watchdog? I assume it would have to connect up to the inhibit connector on the back and connect the proper pins in case it detects a problem.
Thanks!

Hi pghohnst,
It is possible to control the power of a PXI Chassis with the DB 9 connector that is found on the back of the chassis. More information can be found in the KnowledgeBase below.
Remote Power of a PXI Chassis: http://digital.ni.com/public.nsf/allkb/FF5AB8BB6A1157DB8625756D00502D55?OpenDocument
Regards,
Jason D
Applications Engineer
National Instruments

Similar Messages

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.

Problems directly connecting Windows 7 HP EliteBook to NI PXIe-8135 Embedded Controller

For some reason my computer cannot connect to the NI PXIe-8135 Embedded Controller in my PXIe-1082 chassis. My computer recognizes that there is something there, but it cannot communicate with it (no packets recieved back, but packets sent). I've already checked my firewall settings, network settings, and anything else I could think of that might be preventing me from connecting to it but I have not found a single thing that tells me why I cannot connect.
Any ideas on troubleshooting this problem, or if someone has run into the same problem please let me know - any help is greatly appreciated!
-flynneva

Hi flynneva,
Are you using an ethernet cable to connect to your PC? It sounds like you just want to add this chassis to your network just like any other computer (with the embedded controller is a computer). Here is a link to Microsoft's page on this type of connection in case you haven't tried these options:
http://support.microsoft.com/kb/305621
Also, is this embedded computer running Windows or is it a RT controller? What does your computer do to recognize the connection and what are you using to read the data? Can you ping the IP address of the controller and receive a response?
Thanks!
Stephanie S.
Application Engineer
National Instruments

How do I calculate the max latency of a PXI 8135 (controller) to PXI 6528 (DIO) output?

We are using a PXIe- 8135 Controller and a PXI-6528 DIO module in a PXIe-1082 chassis. We are sending DIO input and output commands using Powershell in Windows 7 on the controller. Due to tight requirements I need to know what is the max latency from when the Powershell command is issued to when the read input or write output command will take place in the DIO I/Os.
If this should be in a different Community Board Location please let me know.
Thanks for the help in advance,
Dan_F

Hello dan_f,
As the latency of Powershell and Windows are not tested, it is hard to determine the latency of your setup. The latency from the PXIe-8135 to the PXI-6528 should be in the realm of nanoseconds. The PXI-6528 does have a couple of latency numbers that can be found within the user manual on Page 24, and they are as follows:
Minimum pulse-width for change detection - 150 µs
Propagation delay - 65 µs, typical
You may be able to do some testing to ballpark the latency of the controller OS/software side of the input/output commands, but depending on how critical this latency is to your measurements, you may want to look into using a real-time OS instead.
Chris H
Applications Engineer
National Instruments

Can't find PXIe 8135 as a option in MAX

Hi
I am trying to setup a project with the PXIe 8135 controller and the PXIe 1085 chassis but can't find it in MAX. I am currently downloading the latest DAQmx drivers 9.6.1, so hopefully that helps. I am trying to run the setup the project with simulated hardware until we get the PXI that's on order.

NO Luck... Look DAQmx 9.6 is not installed yet and it look like I dont have support for the PXIe8135 yet I am running LABVIEW 2011
Attachments:
PXI8135.png ‏140 KB

Imaq RT Video Out using PXIe-8135

Hi all,
I am planning to get a PXIe-8135 RT controller and have a requirement to display the image out via the DP port. My questions are:
1. The IMAQ RT Video Out does support PXIe-8135, doesn't it? My concern is because the controller doesn't have VGA or DVI but DP (DisplayPort). Will it work the same?
2. PXIe-8135 has two DP's. Assuming the answer to Q1 above is positive, can I display two different images to both of the DP's?
Please advice.

Hi Shazlan,
1- Yes PXIe-8135 RT controller do support IMAQRT Video Out function.
2- I'm not sure if it's possible since the 2nd DP is just an extended display of the 1st DP
Regards,
Laila
Applications Engineer | National Instruments
Singapore (65) 6226 5886 | Malaysia (60) 3 7948 2000 | Thailand (66) 2 298 4800
Philippines (63) 2 659 1722 | Vietnam (84) 8 3911 3150 | Indonesia (62) 21 2924 1911

PXIe 8135 GPIB

I am trying to connect an ENA series Agilent network analyser to my PXIe 8135 controller, the connectors however are different sizes, is this some sort of mini GPIB port or a national instruments specific port?
Do you know where I can get the correct cable or find the right information about this communication.
Regards

Yes I did but only to check if it was a standard GPIB port, not through the accesories.
So the cable to purchase is the 'X13 GPIB Cable, MicroD25 to Shielded cable/Standard connector, 2M' for £98
Thanks

PXI-6528 Watchdog Timer parameters

I am using the PXI-6528 DIO on PXI chassis. This board is an opto-isolated TTL DIO. The card has an on-board Watchdog timer. I have DAQmx Generate - Digital Line Output (PXI-6528) steps in Sequence steps with "reuse hardware" permitted which set lines high or low as needed for commanding solid state relays (SSR). When the project runs, the behavior non-deterministically sets all lines to low when transitioning to the next Sequence step. If I run each DO step independently it works perfectly every time.
To investigate this phenomenon, I did a simple bench check to rule-out SE software errors. I simply patched from the DO port to the DI port on the same card. Then I added a DI Acquire step just after every DO step to electrically read the states. The result is that the DO port really is going low when the SE software is programmed for high or low! It seems to me that the only thing that can override the SE logic is the Watchdog timer.
Reading this NI White paper:
http://www.ni.com/white-paper/14616/en/#toc4
It seems that it is critical to configure the Watchdog timer to achieve stable behavior from the 6528 card. BUT, neither MAX, DAQ Assistant, or SE have an obvious way to configure the Watchdog timer.
QUESTION: Within SE-DAQmx-Generate-Digital Line Output step what are the parameters that control or disable the Watchdog timer for the PXI-6528?

Update:
I have found more information at this URL:
http://zone.ni.com/reference/en-XX/help/370471AC-01/cdaqmxsupp/pci-6528/
This is the C programming reference specific to the PXI-6528. Reviewing the Watchdog timer properties we find that the "Timeout" property can disable the timer with a value of -1. On the DAQmx Assistant GUI for DO, the Advanced Timing tab does have a Timeout property which will accept a value of -1; however, one must set the Generation Mode to N-Samples to activate the Timeout input field. As the 6528 fundamentally cannot generate samples, then we must reset the Generation mode back to 1-Sample (On Demand) with the effect that the Timeout property is greyed out on the GUI - does this signify that the -1 value for Timeout is ignored?

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

PXIe-8135 Displayport & USB

Hi,
I hope to upgrade my current controller to PXIe-8135RT. My application requires me to have at least four display output (VGA, DVI or HDMI). So now, I have these questions:
1. Since the controller will run in RT, how do I make use of the two displayports on the controller? I don't need to display fancy graphic, just some custom black & white shapes. Can I use the tools in NI Vision, or is there a more suitable tool to do this?
2. The controller also have four USB ports as well as two super-speed USB ports. Besides for connecting USB thumbdrives, can I use the super-speed USB ports to connect to my USB-to-VGA video adapter?
3. Assuming that the answers to the above two questions are NO, will the circumstances change if I use NI HyperVisor (I've seen demos but haven't used one myself)? Perhaps, 3 cores and 3 GB of RAM for RT and 1 core and 1GB of RAM for Windows.
Please advice.
Shazlan

For #1 and #2, I am not aware of a way that you can use four monitors with distinct output on a dedicated PXI RT controller, and I don't think that USB-VGA adapters are supported.
For #3, RT Hypervisor might be a solution for your application, but there are some caveats. Different I/O resources (like the video output, the USB ports, or the PXIe slots) are dedicated to each of the two OSs, and video is typically routed to the Windows OS. However, the basis for determing what resources can go to which OS gets complicated, so I would encourage you to review some of the existing white papers on RT Hypervisor if you are still interested in this approach. See here, here, or here.
To give you an example, Hypervisor is intended for applications where you wish to do a portion of the I/O on each OS, and I think that at a minimum 25% of your PXIe slots must be assigned to the Windows OS. If all you need Windows for is to provide multi-monitor support, you might want to consider alternatives that keep the real-time processing and display on separate controllers.

PXI Watchdog

I'd like some information on the PXI-8108 watchdog. Namely, is it an independent piece of hardware? If so what can it do if it trips? Also, is there any undervoltage lockout capability on the PXI-8108?
Phillip Marks
Solved!
Go to Solution.

Hi gtg811q-
     The purpose of the Watchdog Timer is to provide software-independent means of recovery upon failure of a system or device. The Watchdog Timer is comprised of a binary counter and control registers that assert fixed control signals, upon timeout of the counter. Here is another KnowledgeBase article that discusses what a watchdog timer does.
     In terms of undervoltage lockout capability, I think what you are asking is whether or not the 8108 will shut down if the power supply is below spec? If so, then yes, the 8108 will shut down without proper minimum voltage.
     I hope this helps. Best of luck with your application!
Gary P.
Applications Engineer
National Instruments
Visit ni.com/gettingstarted for step-by-step help in setting up your system.

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

Analog signal from PXI

Hi everybody,
I have a problem: I cannot acquire 6 analog signals with a PXIe 8135 with 4MS/s. I use two boards with 4 MS/s, 16 bits and 8 Analog Inputs. I use a subVI of SAMPLE CLOCK for configuration with this parameters, Continuous SIGNAL, SAMPLE RATE = 4MS/s ( see attachment ). With one signal is ok, but with 2 signals, i have an overload Memory Message.
Where is the problem in the VI?
Thanks for your help.
Attachments:
acq_and_graph.zip ‏165 KB
acquire&loggdata.png ‏230 KB

Quickly looking through your code now, try removing the "Number of Samples analog". Since you are using Continuous Samples, you are just limiting the buffer and also limiting how many samples you can read at a time.
But you might want to think about using Finite Samples. You know how long you want to log for and you know your sample rate. So why not just do the simple math and tell DAQmx to get that many samples? You can use the DAQmx Task Done? VI to see if it is done. That would be much simpler than checking the time that has elapsed.
There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Unofficial Forum Rules and Guidelines

Letter of volatility for PXIe-1071

I'm looking for a Letter (certificate) of Volatility for the following, please:
PXIe-1071
PXIe-8135
PXIe-8234

Hey,
This is the type of request that would be better suited for an official service request via our support system. Since there was a nearly identical request submitted recently, I am going to assume that it pertains to the same incident and handle it via that channel.
Matt W.
Applications Engineer
National Instruments

How to use PXI Star Trigger for PXIe-5663 in PXIe-1075 chassis

HI all,
I have this sytem configuration:
PXIe-8135 controller. Windows 7 64-bit, RFSA 2.7.5. NI-SYNC 3.4.1
PXIe-1075 chassis
PXIe-5663 (2x)
PXIe-6672 Timing & Sync Card (slot #10)
I want to trigger the recording of my Digitizer with an external trigger.
The External Trigger is connected to PFI0 of the PXIe-6672 Timing card.
Then, the PXIE-6672 card routes the trigger to the backplane of the PXIe-1072 (Destination "NISYNC_VAL_PXITRIG0")
The PXIe-5663 are triggered with “NIRFSA_VAL_PXI_TRIG0_STR” as the source.
The trigger fires my PXIe-5663 correctly, but the timing is not tight (> 5ns).
I would like to use the PXI Star trigger instead, I think that I should be able to acheive much better synchronization with this.
But NI-RFSA won't let me do this:
When I try to call
"niRFSA_ConfigureDigitalEdgeStartTrigger(rfsa_session, NIRFSA_VAL_PXI_STAR_STR , NIRFSA_VAL_RISING_EDGE)", I get the error:
"Specified Route Cannot Be Satisfied, Because the Hardware Does Not Support It"
I don't understand why the PXIe-5663E would not be able to use that Route.
Any idea?
Regards,
Serge
Serge Malo, ing.
Concepteur logiciel
Software Developer
T (514) 842-7577 x648 | [email protected]

That explanation isn't quite right. Usually, even PXIe modules have a connection to PXI_Star. The PXIe standard added the PXIe_DStar trigger buses, and it also preserved the PXI_Star bus from the PXI standard.
However, there is an additional twist in this situation. I'm assuming that your PXIe-5663 includes a PXIe-5622 as the digitizer. It turns out that a synchronization technique called NI-TClk has eliminated the need for our more recent digitizers to rely on triggering from PXI_Star. I was able to find some documentation that includes this information, here and here. Given that, I think you have two options that should result in better synchronization.
The first option is to use TClk; I found an example program that demonstrates using TClk to acheive phase coherent signal acquisition across two 5663s. The second option is to use cables of matched length to connect two PFI front panel terminals of the timing board (6672) to the PFI1 front panel terminals of the digitizers (5622). The timing board would accept the external trigger on PFI0 and then issue triggers on PFI1 and PFI2 with around 500 ps of skew (manual, page A-4) . The digitizers would use NIRFSA_VAL_PFI1_STR as the trigger. I hope one of these solutions will meet the demands of your particular application.
I will also follow up with the owners of the RFSA product documentation to see if we can include a note about why PXI_Star is not supported in some cases.
James Blair
NI R&D

PXIe-8135 Watchdog

Similar Messages

Maybe you are looking for