With PCI-6229 NMI Parity error

Similar Questions

• NMI:Parity error blue screen

  I have problem with blue screen with any program at any time. It is as it should be a hardware problem. When I run the Diagnostics on my computer everything seems to check out OK.

  Hello drichardson3,

  ·         You get this error blue screen randomly on your computer?

  ·         What exactly is the diagnostic test that you have run on the computer?

  The checking of NMI Parity error is an error related to a defective hardware on your computer. This is mainly caused by a faulty RAM.

  To resolve this problem, you may need to check on the RAM, I suggest you contact the manufacturer of your computer to check the hardware that does not work properly.

  Thank you
  Irfan H, Engineer Support Microsoft Answers. Visit our Microsoft answers feedback Forum and let us know what you think.

• problems syncing multifunction with PCI-6229

  Hi, I use PCI-6229 and LabVIEW 8.0 for synchronized of the thermocouples and voltage measurements. The diagram is attached here. Here are my questions:

  (1) with the analog inputs of TC is ranked very first and followed with inputs analog voltage, as shown in the diagram, it works fine. But once the tension AIs are placed first and followed with AIs for thermocouples, thermocouple reading makes no sense, for example telling 25 deg C, the program shows strong fluctuating temperature 10-80 deg C.

  (2) the delay time using DAQmx Trigger, here I put the Start.Delay = 2, Start.DelayUnits = ticks. And sampling rate = 1000 Hz for sample clock VI. Then, is equal to 2 X (1/1000 second) delay time = 2ms? If no deadline is set, which is the time between the trigger signal and actural reading? Will it be the time device resolution 50 ns?

  All entries would be very appreciated.

  

  Hi Matt11,

  (1) the order that you specify strings in your task will affect the order of scanning.  In other words, when you add the channels voltage before channels of temperature, the material can enjoy the tension or s channels followed by the string (s) temperature.  Since the 6229 is multiplexed, it comes to each channel sequentially switching in a single ADC.  In your case, it seems that the tension on the ADC to measure voltage not had time to resolve completely prior to taking the measure of temperature.  We refer to this sometimes as ghosts in extreme cases where the value measured on channel b mimics the tension on the channel.

  I think that you have found that you can get this by adding the TC task first.  You could probably also get the same result by allowing more break-in between channels on your scan list.  You can set the time between the channels with a Timing DAQmx property node (you can set the property is the clock frequency convert, which is the opposite of a waiting time).  For slow sampling rates, sets DAQmx convert a default clock rate up to a minimum of 1/14 US (on the x 622).  If your overall sample rate is less than 1/14 us (about 71 kHz) then you should have room to lower the clock rate to convert more of this if you wish to allow more time to settle between the channels.

  I'm a little surprised that you see errors because of it (generally, the problem comes from a signal source of high imepdance measure or when sampling at higher rates), but then again, the temperature measurement would be very sensitive to small voltage fluctuations since you deal with thermocouple voltages at room temperature.  Given the order of scanning affects your measure the problem is almost certainly introduced leaving not enough time for the ADC to settle after reading your string tension.

  (2) ticks means actually timebase tick rather than the graduations to sample.  The minimum is always 2, but this match 2 graduations of 20 MHz (100 ns) time base from which the sample clock (unless you choose otherwise or specify a sampling rate less than 20 MHz / 2 ^ 32), instead of 2 graduations of the 1 kHz sample clock (2 ms).  In fact the trigger is probably performed asynchronously at the base of your time, if you are anywhere between the graduations of 1-2 the basis of delay time (50-100 ns) according to the relative phase of the trigger to the time base.  If no time limit is set, the default value according to me is still 2 ticks which is the minimum that allows hardware (you can check on your own by reading the property node if you wish).

  These points should be compatible between different driver versions, with the exception that DAQmx chose by default convert rate differently in earlier versions of 7.4.  Select the conversion rate is a compromise between the settling of deadlines and the channels are sampled how "simultaneously" on the MULTIPLEXED Board.  The final result in point 7.4 of DAQmx was a compromise apparently arbitrary add 10 US for the minimum conversion period and use this as the maximum by default between the channels.  The user can of course always set the clock to convert to all what best fits their application (in your case, you might want to allow a settlement more between each channel).

  Best regards

• Impossible to get CB-68LP play nicely with PCI-6229

  Hi, I am using a PCI-6229 for 4 analog outputs (call them AO0 - AO3) and 4 inputs analog (call them AI0 - AI3), where I have 2 blocks of connection are the BNC-2110 and CB-68LP.

  For now, they are wired like this:

  1 BNC-2110 inserted in slot 0 (HAVE 0-15) of the PCI-6229

  2 CB-68LP plugged into the connector 1 (HAVE 16-31) of the PCI-6229

  The BNC-2110 things part works perfectly. I use it with success for all 4 of the analog inputs and 2 analog outputs. The connection was intuitively simple, by choosing the PCI-6229 s AO0 and AO1 channel assignments in the DAQ Assistant of LabVIEW and simply by plugging in my wiring in terminals AO0 and AO1 BNC to BNC-2110 connector block.

  However, I can't understand how to wire the CB-68LP for analog output for AO2 and AO3 channels.

  My basic, stripped stable approach to used the NOR Measurement & Automation Explorer:

  -J' opened the dialog box indicating "Test panels: NI PCI-6229: 'Dev 1'.

  -I click the "Analog output" section and choose from the drop-down list "Channel Name"

  -J' I "Dev1/ao0" channels and "Dev1/ao1" working with terminals AO0 and AO1 BNC - 2110, respectively

  - but can't figure out how to wire the CB-68LP to work with the 'Dev1/ao2' and ' Dev1/ao3' channels

  I think at least part of my problem is that I can't find a pinout for the CB-68LP naming scheme.

  Never mind, figured out that list of pins of the PCI-6229 22 and 55 on connector 1 match 22-55 CB-68LP screw terminals, allowing an AO2 (i.e. physical channel "Dev1/ao2"). Similar to AO3 idea. In retrospect, quite simple really problem solved.

• Hardware malfunction: NMI Parity error

  Screen blue/hardware malfunction/call your provider of support material / parity memory check error / NMI:parity / this happens more frequently

  The RAM in your computer seems to be failing. Run the memory in memory diagnostic tool by typing in the search box of the start menu by pressing Enter.

  Use the scanner on this site http://www.crucial.com/ to find out what type of memory, you have to buy if it needs to be replaced.

• 200170 with PCI-MIO-16XE-10 error

  Hello

  I work in a lab and one of our machines had to be updated in Labview 8.5 in 2011 to implement a new box to tools.  I changed any code and have not yet implemented any changes for the new box to tools.  In addition, the program worked before the upgrade. Now, when I run the program I can not run a test because some parameters that indicate that everything is ready are not fulfilled, these parameters are read by the PCI-MIO-16XE-10 (Dev3).  Then, when I stop the program I get the following error:

  

  I use the DAQ assistant to read a Digital-In.

  After you have upgraded, I assume this problem is either bettween compatibility 2011 (probably DAQmx) and the card PCI, or that the driver for the PCI card does not work right (even if it says that the device works properly on the 'Self Test' max).

  While the above issues likely causing the problem?  The PCI-MIO-16XE is only compatible with traditional and not DAQmx?  How can I check to see if it is set up right if it is compatible with DAQmx?

  Thank you

  Link

  The problem is exactly what this message says. The device has only port0. He could never have worked with port1.

• Intermittent failure with PCIe-6251

  We had a power outage intermitant which was worse.  It seems to be due to the card PCIe-6251.  We have Labview 7.0 and DAQmx 8.1 the system as well as a PCI-GPIB and a PCI-6711.  Periodically, computer would lock up and reset either not conclude card, or not able it to reset it until the power of the full test system was cut long enough for + 5V standby to drain.  The problem seemed to be exacerbated by the ambient temperature.  When the test system has been moved from other external heat sources (Ie the cooler for the laser), the problem seems to disappear or has been reduced to less than 1 time per week usually when labview program was executed.

  The test case itself has recently been rebuilt and the problem returned with a vengeance.  After additional cooling was added, and the problem persists, we started checking temperatures of housing.  The internal system temperature is 42 C worst such case reported by the chipset.  We have improved the power supply to make sure it wasn't a collapse of power line causing the problems.  When we catch the problem in the error log, it is an ATI video driver or NIPALK.sys because the production chain continues to go down to this we charge software is installed on a different machine and moved the cards and installed.  It seemed to work perfectly for maybe 2 hours and then started throwing memory parity errors.  The computer is outside the grid of test and cold.  If we draw the PCIe card, the parity errors go away and all is well.  The problem is, is that it is the heart of the control system.  The original computer is not plant 2 or 3 times a day, so it takes a good amount of time trying to verify a fix.

  Unless I'm mistaken, DAQmx 8.1 is the latest driver that supports labview 7.0 DAQmx 8.01 is the other driver that supports the card and labview 7.

  Are there known problems with this card that I'm not find?

  The chassis that has had some parity errors to date had a best time of execution of 20 hours between grave down.  If it generates a parity error, there is no entry in the registry so that I'm not sure that a kernel image will be generated.  Accident yesterday morning, the computer will not re-start until the PCIe card was off for a good amount of time and case open to cool (it was the hottest part of the system by empirical methods, no part was what I considered warm) so the first case has been modernized with casefans directly cool the PCIe card.  This system comes to pass in a few minutes.  If that doesn't work we'll go to labview 8.6 on this system to see if the newer drivers help and finally throw the PCIe and move/o down in the VXI chassis.  The latter may be constrained according to the when the system crashes then.  I'm a bit wary of permutation of 7.0 to 8.6 on a production line with no available time to debug the old software with the new version of Labview.

  External connections make you refernce to?  The power of auxillery connection or the connection to the BNC-2090?  At this point, we are only the e/s digital used on this card.

• Hardware malfunction NMI: parity check / memory parity error * the system stopped *.

  I installed ENLWI-G2 802.11 g Wireless PCI Adapter in my Dell Optiplex 760 with XP SP3 32-bit Windows. But it gives me a blue screen with the error:

  Hardware malfunction NMI: parity check / memory parity error * the system stopped *.

  How to solve this error?

  Try to switch on the memory modules. Ask the MS site for more information on the specific error.

• Satellite Pro A100 - NMI memory parity error parity check

  Sometimes I get this BSOD error during 2 months.
  Hardware malfunction call your provider for support NMI: Parity Check / Memory Parity Error * the system stopped *.

  It can occur if the laptop is asleep, or even refreshing a screen save or Stand-By condition.
  Model PSAAPE - 00s00KEN 2 GB installed. I checked that the memory is installed correctly. It's a laptop very clean with no dust clutter things. Aside from the Ram "goes wrong" and developing a fault, can anyone suggest another cause? It doesn't seem to be an obvious solution to this problem on a forum I've seen so far. Maybe it's my RAM that fails (but it seems to do it when he is not be underlined!) It could be the video drivers... who knows? I hope somebody.

  Hello!

  In your case, I would check the RAM, I think that's the problem.

  You can do this with Memtest86:
  http://Memtest86.com/
  Memtest86 is a diagnostic tool to check the RAM. Here, you can also download a CD image.
  It s easy to use. Run the test of 3-4 hours and then you will see if the RAM has some errors.

  Good bye

• Measurement of the temperature with the PCI-6229

  I was announced in an old thread and do not receive and answer, so I thought I try a new.

  Link to the old thread: http://forums.ni.com/ni/board/message?board.id=250&thread.id=14920&view=by_date_ascending&page=1

  I'm trying to measure temperatures using thermocouples using the PCI-6229 and I use two SBC-68LPR to make the connection.  They are not reference on them joints.

  After moving down from enugh to careful reading of the old thread I mentioned above and I think I knew what I should do.  Here's what I do now:

  Create a task - DAQmxCreateTask

  Create a channel for this task - DAQmxCreateAIThrmstrChanVex thermistor

  Create a number of channels of thermocouple for this task (DAQmxCreateAIThrmcplChan) using the cjcsource DAQmx_Val_Chan option and specifying the string thermistor as the source channel

  Start this task - DAQmxStartTask

  Get the temperatures - DAQmxReadAnalogF64

  Stop the task - DAQmxStopTask

  Disable the task - DAQmxClearTask

  I have not yet hooked, but I doubt that it is the cause of the error.

  A few more details (pardon my Delphi):

  Create the channel of the thermistor

  TmPcName: = ' Dev1/IA.19 ";

  Secret: = DAQmxCreateAIThrmstrChanVex)
  TcTaskHandle, / / task handle
  @TmPcName, / / physical channel name
  @TmChName, / / name of channel
  -80,                                   // Min range
  80,                                    // Max range
  DAQmx_Val_DegC, / / units, ° C
  DAQmx_Val_ResistanceConfiguration_4Wire, / / 2-wire, 4-wire, etc.
  DAQmx_Val_ExcitationSource_External, / / source of excitement, external
  1, / / value of excitement
  9.376e-4,                         // a
  2.208e-4,                         // b
  1.276e-7,                         // c
  30000);                            Resistance of reference

  Creation of the channel of thermocouple:

  TcPcName: = ' Dev1/ai23;

  Secret: = DAQmxCreateAIThrmcplChan)
  TcTaskHandle, / / task handle
  @TcPcName, / / physical channel name
  '',                                     // Channel name
  0,                                    // Min range
  1000, / / Max range
  DAQmx_Val_DegC, / / units
  DAQmx_Val_DegC, / / type of Thermocouple
  DAQmx_Val_Chan, / / source CJC
  25, / / value of CYC, so DAQxm_Val_ConstVal
  @TmPcName);             CJC channel, so DAQxm_Val_Chan

  It looks like 4 scales is required for voltage excitement thermistor measurements.

  In addition, it seems that external excitation is necessary in my case, PCI-6229.

  Everything works if I use a CJCConstant.  When I do this I use the same code to create channels of thermocouple, but I spend creating the channel of the thermistor.  When I try to use a CJCChannel I get an error saying "value required is not supported for this property value," which occurs when I call DAQmxStartTask.  I don't have no idea of what this message refers to and the best I can tell the properties that I've specified sense.  The constant termistor are from actual thermistor, that I found on travailleursduweb.com.

  I could also use some help to know how to connect the thermistor.  Looks like I need to fab, a thermistor circuit myself, with a stable voltage to power the termistor and use a double-ended analog and reference to the channel.

  Thank you

  Mike

  The error of thermocouple type was a type-o in the post.   Thanks for catching it.

  I think I found the problem.

  I wrote a small program to test for Thermistors and I went to using the routine exctation of tension for a common routine of excitement (... IEX instead of... Vex).  I had been by specifying a minimum value less than 0.  I changed it from-80 to 0, and it works now.  However, I got an error in division by zero, intermittently, when you read a thermistor channel.  The error is not in my code.  It occurs when you call DAQmxReadAnalogF64 for the first time and I'm not all mathematical related to this call.  I'm still looking into it.

• Pavilion DV2000 - NMI: parity check / memory parity error

  My laptop was working fine and all of a sudden I got this blue screen with this message:

  Hardware malfunction
  Call your provider of support material
  NMI Parity Check / Memory Parity Error
  The system is shut down

  I have try the recovery disk and the computer back to its factory setting. It will be fine for about a day and then the blue screen light up again. I have try that 3 times now with no luck.

  Can someone please? I'm getting really annoyed that I run my business using my computer every day and I can't continue to recover and reinstall everything every two days.

  The laptop has 150 GB of memory with two 1 GB of Ram.

  What do you mean by delete a module?

  The computer cannot even load into the window before it crashes with blue screen.

  * Just realized there is the notebook section. I have post the same problem on this article and close this one here *.

• Satellite P200 - Parity Check / Memory Parity Error

  Hi all experts!

  After updating a driver, I get this above mentioned message.
  + Message ' hardware malfunction NMI Parity Check / Memory Parity Error.

  But just at the moment where the P200 falls in sleep mode. I can't wake up and have to do a hard reboot. Windows is starting and works perfectly and everything seems to be okay!

  Any idea?

  Thanks in advance!
  YB

  Hello

  This behavior can occur if a hardware component malfunctions, or if it has installed the damaged or incompatible drivers.
  I think that you should remove the driver updated or installed first.
  If this does not work, test the laptop with preinstalled system cool.

  Finally if this is insufficient, a hardware malfunction might be possible.
  In this case the RAM modules need to be tested as the first part.

• Minimum requirements of DAQmx PCI 6229

  I am currently converting our are configured to use a PCI-6229 for the analog inputs.  We have LABView 7.1 on a Windows XP operating system.  I looked at the latest version of DAQmx that would work with LABView 7.1 and found it DAQmx 8.9.  When I run the DAQ Assistant I gen an ERROR of INITIALIZATION:

  Some components required for publishing are missing.  For more information, please contact National Instruments.

  Article OR suggest that I put to update to the latest version of the software driver, DAQmx 9.3, to solve this problem, but I do not think that this version works with LABView 7.1.

  Does anyone know if the PCI-6229 will work with DAQmx 8.9?

  Any newer version of DAQmx will work with LABView 7.1?

  And if there is another way to fix the DAQ Assistant error?

  Thank you Ahead of time,

  WindResearcher

  
  

• 6229 OR causes error-50202 on Fujitsu/Siemens Celsius PC

  Hello!

  With the help of MAX Self test or test causes error-50202. I use a PC Celsius Fujitsu/Siemens, model W370 E85 + with LabView 8.6.1. The PC uses an Intel motherboard and an Intel Dual core processor. The PC is new.

  I tried to test another PC but the USB startup utility seems to work only with the above PC. On the other PC, I get the error pharsys and the boot process stops.

  I also have a full equipped PXI dual core system RT that works without any problems with my host LabView 8.6.1 installation.

  How to solve this problem?

  NEWS! I was testing a card PCI-6229 second and identical, but the map did not, too. And while I was there, I simply changed the slot inside the PC Celsius PCI: and the self test successful!

  Here is a screenshot after changing the slot. You can even see the 'Phantom' 1 unit (where one of the cards was before).

  

  I have to do more tests, but I was sure, that these IRQ problems are history (if it was such a problem).

• Problem of clock sample e/s digital PCI-6229

  Hello

  I use PCI-6229. I need to use the digital output channel to generate pulses of 20 kHz 30% duty cycle.

  The datasheet shows the sample clock frequency can be 1 M Hz. But in may, only 100KHzTimebase may work to generate. But acctually I need at least 200K Hz.

  I've done the Vi is attached. Can someone help me with this problem?

  Thank you

  Hello ossoo,

  The PCI-6229 is not a timing engine digital to create a digital task which runs at 1 MHz, you must use an external sample clock.  However, one thing you can do is generate a pulse train at your desired frequency using a meter integrated 6229 and then using this output meter as the sample for your task digital clock.  Take a look at the attached amendment, I made to your VI which shows how to build your digital task to 1 MHz using the meter on board.  You can change the frequency of the train of impulses of the meter in order to change the frequency of your outputs digital.  Please let me know if you have any questions.

  Kind regards