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

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

  • Control PXI devices via PyVisa?

    Is it possible to control PXI devices via PyVisa in the same way as USB, and GPIB devices?
    Solved!
    Go to Solution.

    Hi k-rhyme,
    It should be possible to do. You can definitely control PXI devices using NI-VISA and since PyVISA is just a Python wrapper, it should be possible. It also depends on the version of VISA that PyVISA is using. I would recommend looking at the NI-VISA User Manual for more info PXI specific functions. 
    Using the NI-VISA Driver Wizard and NI-VISA to Develop a PXI(e)/PCI(e) Driver in Windows
    http://www.ni.com/tutorial/4713/en/
    NI-VISA User Manual
    http://www.ni.com/pdf/manuals/370423a.pdf
    Thanks,
    Frank
    Application Engineer
    National Instruments

  • 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/e​n
    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

  • 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

  • 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?

  • Motion control: PXI 7350 controller and UMI 7774 to interface with third-party driver UDK5114NW2

    Dear community,
    This is about Motion control in Labview: I try to control a step motor by using a PXI 7350 controller and UMI 7774 to interface with  third-party driver UDK5114NW2. The problem is 5 Disable LEDS on UMI 7774 board always lit even when I check "enable" on "Motion I/O setting" in configuration of PXI 7350 motion controller. Furthermore, when I start to control step motor, it is not working and I found disable LED on UMI board still lit. I don't know how to solve this problem. Can someone help me to figure out? Thank you in advance!
    Hau Nguyen.

    Dear Community,
    I said wrong, 4 disable LEDS on UMI 7774 Board instead of 5 as my previous post. Why nobody help me to solve this problem. I can not turn off disable LEDs on UMI 7774 Board so I can not start the strp motor. Please help me!
    Hau Nguyen. 

  • How could I control PXI-2567 from my C/C++ program?

    I need to control the PXI-2567 relay driver from inside my C/C++ programs.
    How could I do this, is there a dl, com, or something?
    Please tell me if there are any integration documents or user manuals for using whichever method if any.

    Hi BSA,
           You'll want to utilize the NI Switch Driver, which will install both example programs and the NI Switches Help.   There is a Function Reference Section in the NI Switches Help (which is installed with the NI Switch driver, and as well can be found on our website).  Example programs will be installed on your computer under Start»All Programs»National Instruments»NI-SWITCH»Examples»C .  You can also program your switch with2567 with DAQmx.  The differences between the two drivers can be found in this KB.  As well, additional resources for your switch are discussed here. 
    aNItaB
    Applications Engineer
    National Instruments
    Digital Multimeters

  • Controlling pxi 7350 using labview software

    Hi,
    So i am a complete newbie when it comes to labview having only used it to control virtual instruments before and now i am the point where i want it to interact with real world items. Ok so here goes..... i have the latest labview development software and have also purchased a pxi1033 with a pxi4065 digital multimeter and a pxi 7350 motion controller integrated within.
    my problem however is that i want to be able to control my motors via the umi7772 interface but cannot seem to find the correct symbols on the labview software to utilise them, i would like to use labview to create a program that will turn the stepper and evaluate what is on the dmm and then turn accordingly this is way above my level on labview currently but if anyone has any ideas then any information is greatly appreciated.
    cheers
    james

    Hello Jamest6, 
    I have found some useful documentation that will help you get started with you 7350 and LabVIEW. 
    First of all here is a community example that you can take a look at. It is possible to download the example itself from the bottom of the page.
    Read Analog Input (AI) values from NI-Motion device 73xx : https://decibel.ni.com/content/docs/DOC-5617
    Then you can access these knowledge base articles for some more guidance : 
    How Do I Use the Digital Input/Output Lines on my 7330, 7340, or 7350 Motion Controller Card? : http://digital.ni.com/public.nsf/allkb/2D238C3BF101620C862573A60081BFFE?OpenDocument
    How do I control the analog ouputs from an NI PCI motion controller in Measurement & Automation Explorer?: http://digital.ni.com/public.nsf/allkb/04B940903BDD987C862579320083C6FF?OpenDocument
    Also using these manuals for both prducts will be of help to you : 
    NI 7330/7340/7350 Motion Controllers and
    P7000 Series Stepper Drives: 
    http://www.ni.com/pdf/manuals/372324d.pdf
    NI UMI-7774/7772 : http://www.ni.com/pdf/manuals/373359c.pdf
    Another great source for looking at or using example VIs is the  LabVIEW's Example Finder.  Go to Help » Find Examples... When that window pops ups, double-click Toolkits & Modules in the folder list, then double-click NI Motion Assistant.  I'm guessing the "Straight Line Move.vi" or "Blended Move.vi" would be most helpful to you, but you could read the descriptions of each example listed for a little bit more information about what the examples are doing.
    Hope these are useful! 

  • Problem Controlling PXI-2503 Switch through the IVI-C Switch API

    Hi,
    I'm writing an application to control a PXI-2503 switch in 1-wire mode using the IVI-C Switch API in order to route signals to a PXI-4060 DMM.
    According to the programming instructions, I should be able to create a path from the "ab0" channel to a channel like "ch10" by calling IviSwtch_Connect( "ab0", "com0" ) to connect "ab0" to "com0" and then calling IviSwtch( "com0", "ch10" ) to connect "com0" to "ch10". However, after the program makes those 2 functon calls, the DMM doesn't get the correct signal.
    When I use the NI Switch Soft Front Panel application to connect "ab0" to "com0" and then connect "com0" to "ch10", then the DMM gets the correct signal. Does anyone know what the Soft Front Panel tool does differently?
    Thanks in advance to anyone who can help.
    VRMan

    VRMan,
    Make sure that you have configured your 2503 to be in the 1-wire 48x1 topology...
    Other relays that need to be closed for ch10 to make it to ab0
    are  "bc01" and "1-wire".  Check out the hardware diagram for
    the 2503 which can be found by going to
    Start>>Programs>>National
    Instruments>>NI-Switch>>Documentation>>NI Switches
    Help, then browse to Devices>>2503>>PXI-2503 Hardware
    Diagram.
    When you use the SFP or program with LabVIEW, you have the option to
    initialize a switch with a certain topology.  For the 2503 1-wire
    48x1 mode, this automatically changes "bc01"," bc02", "bc03", and
    "1-wire" to the correct positions.  Check to make sure that the
    same is done when using the IVI-C driver you are working with.
    Let me know if this doesn't solve the problem, or if you have any more questions.  Best of luck on your application.
    Regards,
    Travis W

  • Controlling PXI-2501 Switches in C#

    What is the best - prefered - way to control a PXI-2501/2503 Switch Matrix in C#.
    I have only been able to find examples showing SCXI switching units. Is it done in the same way?
    Code examples would be nice.
    Thanks

    I am assuming that the examples you are using are the DAQmx C# examples (Program Files\National Instruments\MeasurementStudio70\DotNET\Examples\DAQmx\Switches).
    These examples work for all SCXI and PXI switches that are supported in DAQmx. NI-DAQ 7.1, the currently released version of NI-DAQ driver software, does not support PXI-2501/2503 under DAQmx. These modules will be supported in DAQmx in the next version of the driver.

  • 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.

  • 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

  • PXIe-8101 Unable To Compile Code

    Hello,
    My system is a PXIe-1065 chassis (I've also had the same issue in the PXIe-1082 chassis), PXIe-8101 controller with Windows 7 installed by NI, and the following instruments:
    DMM PXI-4071, Power Supply PXI-4110, DAQ PXIe-6356, Timing Card PXIe-6674T, and Motion Control PXI-7332.
    I also have a PXIe-8361 which I will use on occasion and will be what I use in the long term.
    Now for the actual problem. What happens is I'll put together some code in labview using the instrument driver VI's and everything will work fine. I can make VI's that call subVI's that call the instrument VI's and it works great, but if I double click on an instruments VI and then try to look at the block diagram, for example, opening "DAQmx Create Channel (AI-Voltage-Basic).vi" it seems to break the code. Initially it won't say anything but once I hit the run button the arrow will change to the broken gray arrow and will state that the code failed to compile (this is without actually changing anything with the VI, I open it and look at what it is doing).
    Also any code I've written that called that VI will now get the same error, if I click show error it will bring up whatever window I was looking at last, so if I was looking at the front panel, then clicked show error it would just bring up the front panel again without highlighting anything. If I create a new file and build a small vi that uses the instrument drivers it works fine, if I copy the vi's from the broken code and paste it into the new file it will fail with the same error.
    It doesn't have this behavior with all the instrument VI's but will happen with some. I mentioned it happens with "DAQmx Create Channel (AI-Voltage-Basic).vi" but then it doesn't happen with "DAQmx Timing(Sample Clock).vi". I haven't gone through and checked exactly which VI's it happens with but it seems to happen with other instruments drivers as well, not just for the DAQ. It also only seems to happen when using the PXIe-8101. If I connect it to a computer this issue doesn't pop up. My company primarily controls the chassis using MXI cards so we don't have any available embedded controllers I could swap in to see if it still happens.
    It's not a big issue as looking into the instrument vi's isn't necessary for me to do my job, I just do it to try to better understand what exactly is happening but it is something I'm curious about.
    DISCLAIMER: I'm a hardware engineer so I may not be familiar with some concepts/terminology/best practices so... patience is appreciated
    Solved!
    Go to Solution.

    At the time I first noticed this error I was just starting to use labview, so I simply avoided opening that vi, now I've been working with labview for about 9 months. I haven't been working with it consistently, not all my projects require it, but I would say I've spent at least half my time working with it.
    Well I seem to have recorded it slightly off. So when I looked into the DAQmx vi it gave an error and when I clicked show details it gave the following:
    When I tried to exit it asked me if I wanted to save the changes, I chose defer decision and eventually chose do not save. I closed labview and reopened the VI, tried to run it and it gave the error:
    I selected show error and it gave:
    Then where it said it failed to compile was within another vi in the same project. When I first opened it it said SubVI is not executable. When I clicked show error it took me to a VI that had the DAQmx vi in it and it was saying VI failed to compile.
    I've attached the SubVI from which I opened the DAQmx. It's a basic vi to read analog data. Is that what you meant for screenshots?
    DISCLAIMER: I'm a hardware engineer so I may not be familiar with some concepts/terminology/best practices so... patience is appreciated
    Attachments:
    DAQaread.vi ‏27 KB

Maybe you are looking for