-107418650 error with PXI-4070 even W/O autorange.

I have a PXI-1033 that includes a PXI-4070 in slot 5. I am using a version of the Switch Scanning with DMM - Handshaking.vi but I changed it to read a fixed scan list and replaced the meter while loop with a fixed read of 144 samples.  After this VI runs approximately 47 times I get this error:
I have NI-DMM 3.0.4, NI-DAQmx 9.3.0f2 LabView 2101SP1 and am running Vista Business 32 bit. I am using 4 wire resistance and tried both auto and fixed range with the same results. Before this loop the only DMM related functions is to read 4 wire resistance readings and close the DMM. That seems to loop forever without any problems.
Rebooting dozens of times a day is getting old fast, any ideas?
Solved!
Go to Solution.

Here is the code that causes the error. I can run the Switch Scanning with DMM - Handshaking.VI all day without problems. It's the version I modified that I seem to be unable to fix. The test VI will run from for sometimes as few as 2 loops and hang the system.
Attachments:
Scan list and measure.vi ‏48 KB
Run switch to error.vi ‏15 KB

Similar Messages

  • Spectrum Frequency Error with PXIe-5641R and PXI-5600

    Hello,
    following situation: I am using the PXIe-5641R (in FPGA-mode) in combination with the PXI-5600 downconverter to get a spectrum.
    After trying out with different span widths I've experienced strange frequency errors in the range span <10M.
    To negotiate errors in my program I've evaluated also the NI example of http://zone.ni.com/devzone/cda/epd/p/id/6196 - unfortunately same error in frequency happens there.
    What is meant with frequency error, for example:  I have a transceiver which sends FSK with center frequency 443,92MHz. Readings with span-width = 12,5M shows overall good results.
    Reading with span width smaller 10M, eg. 3,125MHz, gives unexpected readings. 
    With a center frequency of 433MHz and a span of 3,125MHz the transmission is out of range of spectrum. When I add an offset of 2M to the calculated IF-frequency, I get right results.
    With a center frequency of 434M I've got readings at 434,92MHz, means at 1MHz too high (after adding an offset of 1M to IF freq readings are correct).
    With center frequency 435MHz readings are correct. The limit between correct and wrong is exact at 434,5MHz (resulting IF = 14,5MHz) readings at that center frequency are good, just one step below (434,49MHz) readings are 1MHz too high.
    Where is the error hidden? Like I said this behaviour happens also with the NI example.
    Thanks for helping!
    Message Edited by Lars.B on 05-20-2009 04:26 AM
    Message Edited by Lars.B on 05-20-2009 04:28 AM
    Message Edited by Lars.B on 05-20-2009 04:29 AM

    To get closer to the problem: I've managed to get constant right results in editing the VI which calculates the IF-frequency for the IF-RIO after setting center frequency and span of PXI-5600.
    But the new values make no sense at all. Documentation says that with spans higher 10MHz step size of center frequency is 1MHz, below it is 5MHz (with lower phase noise). After my modifications it seems that step size is 1MHz at all span widths higher 1MHz and 5MHz at span widths lower 1MHz. 
    Attachments:
    Get NCO Frequency.vi ‏8 KB

  • Error -1074117754 thrown when sequence tries to initialize PXI-4070

    My customer is reporting that when TestStand attempts to initialize hardware at the start of the product test sequences, the system throws an error -1074117754.  He believes that it's associated with the PXI-4070 DMM, as he also cannot talk to the card with the soft front panel.  Has anyone seen this code before?  Any ideas what it means?  Any known fixes?  Thanks!

    Issues concerning this error have typically indicated faulty hardware in the past, so you may have to RMA it.  However, before you try that, try the following troubleshooting steps:
    - Reboot
    - Re-install DMM drivers (make sure to use the newest version: 2.6)
    - Try the card in a different PXI slot
    - Try the card in a different PXI chassis
    - Try a different DMM in the same PXI chassis and see if it works
    Again, we've seen this issue before, so if it persists, contact support so you can send it in for repair.
    Elijah Kerry
    Senior Product Manager, LabVIEW
    Follow my Software Engineering for LabVIEW Blog

  • PXI-4070 with PXIe-1062Q+NIe-8360+Labtop Why? Max not found instrument.

    Dear all
    my condition
    PXI-4070 with PXIe-1062Q+NIe-8360+Labtop
    Window XP SP3
    NI-DMM 3.1
    Why? Max not found instrument.
    found PCI Device "PXI10:15::INSTR
    see picture
    How to fix this problem?
    Best Regard,
    Sermsak.
    Attachments:
    PXI-4070.jpg ‏42 KB

    Hello, 
    Is it possible to take another picture of MAX? That one is very pixilated and I can't quite make out the configuration/error. Does the chassis show up? Every now and then MXI compatibility software is needed for certain BIOS versions so this may be the cause. Did the system work ever before?
    Thanks,
    Eric E.

  • Internal error: "memory.cpp", line 593 with PXI 8175

    Hi,
    I have created a program with Labview RT 7.0 which makes acquisition, storage and display of data with PXI controllers 8175.
    I used Datasocket for the data display on a deported computer.
    Because of the number of the Datasocket tags used, instead of sending values all the time, I'm sending value for the deported computer only if the user needs to see it.
    For example : if the user needs to see data, so only Datasocket tags for data display will be active, and if the user needs to see parameters values, so only parameters datasockets tags will be active. And, if the display program is in "standby" mode, almost all datasocket aren't active.
    So when the user needs to see data values, he opens the data values window of the display program, and then, the datasockets tags for data value are now active, but : sometimes at this moment, the PXI stops with an "internal error "memory.cpp" line 593"!
    The only solution is to manually reboot the PXI, the programmatically reboot doesn't work in this case of error. But it is far away from the displaying computer.
    The error happens regularly after a 2 weeks period of standby. So I though about a memory overflow, I checked all the arrays, and none of them is growing to the infinity.
    If someone knows about this problem, I will be very happy to learn about how to get rid of it!!!
    Best Regards,
    G Liagre
    Best regards,
    G Liagre

    Hi Rob, Hi Matthieu,
    Thank you for your reply.
    I found in the database many reply about this error, but none of them were helpfull for me.
    I tryed your link to the knowledge data base, but the error described there is for dll association in LabView and interface nodes.
    I didn't used any interface node in my code.
    The problem is that I cannot test my program on the PXI because I don't have access to it rightnow (only by remote desktop, and with a 56k modem..)
    Let me give you a part of this huge code.
    I suspect this part of the code to be the one which create the problem, but it's not sure.
    If you find something obviously wrong, tell me!
    Best regards,
    G Liagre
    Best regards,
    G Liagre
    Attachments:
    Communication.zip ‏931 KB

  • Measuring digital signals coming from the HSDIO (PXI-6542) with the DMM (PXI-4070)

    Hello,
    in attachment you can find the program I'm using for my measurement: I'm generating and acquiring digital signals with the PXI-6542 and at some trigger point of one of those digital signals I'd like to capture the measured values on a plot with the Digital MultiMeter (PXI-4070).
    It does work if you configure the generation repeat mode as continuous, but if you do have a finite repetition (repeat count is 1) it doesn't react on the trigger, as if it can't find a trigger. On the other hand, if you have a finite repeat count of 30 or more it does react and triggers correctly again.
    First I though it had something to do with autocalibration before the measurement takes place, but If you do a highlight execution (stepping through the program) it looks like it measures before the generation session is initialized.
    Is there a way to measure correctly when the repeat count is only 1?
    Thanks in advance,
    Jürgen

    Hey Jürgen.  I apologize that you haven't gotten an answer yet to your post.  I looked at your code and had some questions.  What is the source of your trigger to your DMM?  I see that you're exporting the data active event to PFI1, and your comments indicate that PFI1 and PFI2 are connected to give you a start trigger for your digital acquisition.  Exporting the data active event with a finite or continuous pulse should only give you a single edge per run, though - you wouldn't get a pulse each time.  Is your trigger coming from a data line?  I didn't see any line in your included data that would indicate a single pulse.
    The other thing that I noticed is that you've got no timing dependency between your HSDIO code and your DMM code - they're in parallel with each other.  Thus you could get different results run-to-run, since it's not deterministic as to which parallel "thread" that LV will start on first.  LV may switch back and forth several times, but let's say that LV reaches the HSDIO Start command before reaching the DMM Start command - in that case, the HSDIO device may finish it's entire operation before the DMM ever starts looking for a trigger, and thus never get the trigger at all.  I'm not sure why this would explain why you're seeing the finite case work and the continuous case not, but I wanted to point it out because it could bite you down the road.
    I hope some of this this helps get you going in the right direction.  I'd also suggest posting HW-centric questions in the appropriate form.  There are Digital forums and DMM forums that might help you reach people that will be more familiar with your particular hardware.
    Chris

  • Driver install with PXI 8360 Error " This device cannot start - Code 10"

    While trying to instal PXI-6541 in PXI-1036 chassi with PXI 8360 controller[express-8360 on laptop side] , getting the error message "This device cannot start [Code 10]" Laptop is Lenovo T60 with latest BIOS
    Thanks
    Manu 
    Solved!
    Go to Solution.

    Hello Manu,
    I'm sorry to hear that you are having so many issues with getting your Expresscard 8360 working on your Lenovo. I recommend that we first look into Device Manager in more details. You mentioned that there were question marks (?) on certain devices. This usually means that there are devices on your PC that do not have any associated hardware drivers. For the Expresscard 8360, the drivers should be native to the Windows system, so I am unsure if those "?" do belong to this portion of the system. We can test this out by removing the expresscard 8360 and see if the "?" are still present. These "?" can be from the internals of the PC or modules that you've attached. If you've restored your operating system recently, it could be from the peripherals of your computer in which case you will need to find and install the chipset drivers. This can also be from the modules that you in your chassis, assuming that you haven't installed the necessary drivers for them, in which case you can find them on the Driver CD you have.
    The exclamation mark (!) in Device Manager usually signifies a problem with getting the hardware started/operational. From your earlier posts I believe that the "!" is related to the Error Code 10 that you are receiving. Assuming that the correct power sequence was performed, chassis then PC, this is representative of a BIOS compatibility issue. Essentially this is occuring because the BIOS of the motherboard is not correctly allocating the necessary resources to all the devices as it is supposed to. Since you already have the latest BIOS, I would recommend that you try using the MXI Express Compatibility Software, here ni.com/beta. This is something that National Instruments created in order to correct for the incorrect resource allocation of the PC. It is not a beta program, it is only on the site so that we can manage it more easily. I have seen Lenovo T60 laptops work with this software installed.
    Let me know if this helps
    Thanks
    Can W.
    PXI and VXI Platform PSE
    National Instruments

  • On my 3gs keep getting error message charging not supported with this accessory even when its not plugged in and i have done a restore anyone know how to fix

    on my 3gs keep getting error message charging not supported with this accessory even when its not plugged in and i have done a restore anyone know how to fix

    Clean the iPhone charging port with a clean dry toothbrush.

  • Use of PXI 4070 for calibration with CalExec

    I am running CalExec 3.1
    NI 5421 and 5422 cards need the DMM  NI PXI-4070 for the calibration. Can I use HP 34401A instead of that?
    Thankyou,
    Poornima

    Hi Poornima,
    Yes you can use the 34401a. Test Exec uses IVI so you can choose which IVI device you wish to use.
    Hope this helps,
    Nick

  • PXI 4070 use DAQmx Drivers

    I have replaced a PXI 4060 card with a PXI 4070 card in a PXI 1042 chassis that I use for resistance measurements.  I want to use DAQmx drivers instead of the traditional daq drivers.  How can I do this?
    My controlling software is VB6.  I have had issues with traditional daq on Windows XP machines with new NI installations.  Errors indicate there is an issue with the traditional daq drivers.  The sample applications installed with the niDMM 2.7 installation error with message "Error Loading Driver Module".  I have used the palbase utility in the past to work around this issue, however, the palbase utility is not failing to change the base address.  There is an error message associated with the failure, but I figure I may save myself the headache by switching to DAQmx drivers.

    I would recommend upgrading to the niDMM 3.0.4 drivers found here.  This version is still compatible with Visual Basic 6.0 and Windows XP.  niDMM 2.7 would have installed NI-DAQ 8.5.  The name indicates that it is traditional DAQ, but as far as I can tell, version 8.5 was only DAQmx.  3.0.4 will also install a newer version of DAQmx that is compatible with XP, as well as the examples.  It seems that the version you have should have worked, but there may be some corruption, or there may have been a version of traditional DAQ 8.5 at some time (we had some versions of NI-DAQ that included both traditional DAQ and DAQmx).  I hope this helps!
    Thanks,
    Sean
    Applications Engineering Specialist - Semiconductor Test
    National Instruments

  • IVI Configuration with PXI-4110 in TestStand

    Hello All,
    Set-Up:
    PXI-1033 connected through MXI to a PC running Windows 7. LabVIEW 2014. TestStand 2014 (32-bit). PXI-4110 Power Supply and PXI-4070 DMM.
    In MAX I can open both soft panels and control both units and they work great.  In LabVIEW I can control both cards as well. 
    In MAX I have set up a driver and logical name for my DMM. This unit works great within TestStand using an IVI DMM step.
    I then proceeded to setup the 4110 in MAX with an IVI driver and logical name. Here are my settings:
    Name: ni4410_PS
    Hardware: Added hardware asset and select the PS. This one is checked, no other assets are checked.
    Software Module: NI-DCPower, 4110 is listed as a device that is supported.
    Virtual Names: This is where I am confused, Under physical name there are four options that come up (0, 1, 2, and 3). This power supply only has 3 outputs so I am unsure why four come up. I have made 4 virtual names, one for each of the options. I named them ch0, ch1, ch2, and ch3 respectively.
    When I put an IVI Power Supply step in TestStand everything seems to be working. I open the configuration window and set my values for each channel. If I try to validate the setup by unchecking simulate and click on init I do not get an error.  As soon as I clic on 'Configure' or 'Show Soft Front Panel' I get the following error:
    "The IVI Configure operation failed for lgical name 'NI PS 1'. Details: Extention capability not supported by instrument driver. (Base) (-30717)"
    Any information would be appreciated.  I tried playing with it for a couple hours yesterday and had a couple co workers try to help.  We are all under the assumption that this should be working.  
    Thank You!!
    Jesse
    Solved!
    Go to Solution.

    Hi jesserzamora,
    Have you seen this link: http://digital.ni.com/public.nsf/allkb/331F2717DBCD1F858625758200745773?OpenDocument
    It discusses a similar failure with the IVI Power Supply step in TestStand. 
    Julia P.

  • Pxi 4070 input impedance

    I am trying to modify the input impedance of the pxi 4070 dmm with the NI DMM property node.  When I set the input impedance to greater than 10 giga ohms, I am getting an error outputted after running niDMM Configure Measurements Digits.vi.  The signal that I am measuring is 5V, so I should be able to use the 10 giga ohm input impedance.  I set the niDMM Configure Measurements Digits to autoscale. Could this be an issue that the pxi-4070 is not allowed to have its input impedance changed when the dmm is set to autoscale?

    You are correct.  When the range is selected, the API automatically selects the input impedence.  If you need to do this programmatically based on the measurement, then you could use a case structure that checks the range being used and then sets the input impedence based on this.  Do you know if the value you are trying to read at the time would set the range to a value that is compatible with the input impedence?
    Thanks,
    Sean Newton
    Applications Engineering Specialist - Semiconductor Test
    National Instruments

  • LV12 How to configure PXI-4070 DMM current function?

    Dear all
    I have a problem about LV12 software to config PXI-4070 DMM current function.
    my vi...NI DMM initial >>>NI DMM reset >>> NI DMM Configure Measurement (Current function) >>> NI DMM Reading >>>>
    When I testing with my vi, the calibrator (source) error "Current Compliance Voltage Exceeded".
    but when I testing with DMM front panel 3.0, the calibrator can generated current and PXI-4070 can reading.
    Please help me to solve this problem.
    Regard,
    Sermsak.
    Solved!
    Go to Solution.

    The error looks like it is related to a power supply or an SMU that is trying to source something out of its specified range.
    Info about compliance:
    http://zone.ni.com/reference/en-XX/help/370736L-01​/ni_dc_power_supplies_help/compliance/
    http://zone.ni.com/reference/en-XX/help/370736L-01​/nidcpowerviref/nidcpower_query_in_compliance/
    Things to consider:
    1) Where in the code is the error occurring?
    2) Can you run example NI-DMM code? (from Help>>find examples>>Hardware I/O>>Modular Instruments>>NI-DMM)

  • MXI-3 with PXI-7344 etc blue screens

    Dear support folk,
    This is a follow-on from unsolved problem discussed below. I have this problem on multiple computers now with varying severities. One machine is unuseable due to the frequency of blue screens. Is it our C-code perhaps? Please help - this problem is going to be the death of me!
    Old question:
    "Okay, this is driving me crazy! I've asked this question before and really didn't resolve the problem fully so here we go again. I have an MXI-3 card with PXI-6052E, 6508 and 7344 in cPCI chassis. Trouble is I get random bluescreen errors (especially towards the end of boot process but they can be anytime). This happens on just about every machine I install this hardware configuartion on. Disabling stuff like the c
    om ports and killing background processes such as virus scanners seem to help a little but have never solved the problem. The latest installation won't go at all and bluescreens every time. I tried a Win 2000 installation and the boot-up blue screens disappeared but our software would not work properly (this could well be our fault though so I will restrict my question to the boot-up bluescreens). Any help would be very much appreciated!"
    Old answer
    "Hi,
    There was a bug in the MXI-3 software that could cause a Windows page fault exception (0xE) on Windows 98. It is very rare, but there is a patch to fix it. I attached it below. If this does not solve the problem, please email us so that we can help you further. Go to http:\\www.ni.com\ask and select Email an Engineer. You will want to select PXI/VXI for the product.
    Thank you,
    Katie Shiels

    Marcus,
    The most common cause of problems with MXI-3 systems is simply not using the correct boot order. I would first verify the proper boot order (chassis first, then computer). Verify that the LINK LED comes on right after the computer boots, and that the LINK LED never, ever, blinks or strobes during operation. If the LINK LED goes out, strobes, blinks, etc, then a hardware problem with the link (PCI-MXI-3 board, PXI-MXI-3 board, or cable) is indicated.
    If you continue to have blue-screens at boot, then the next step is to "divide-and-conquor" the system. What we want to do is make sure that none of the cards in the PXI (or CompactPCI) chassis are themselves causing the problem (for example, if a card has a resource conflict). For troubleshooting purposes, remove all cards from the PXI chassis, shutdown, and then power-up again with the proper boot sequence (chassis first, computer second). If the problems disappear, then a problem or resource conflict with one of the PXI / cPCI cards is indicated.
    If the blue-screens continue, even with the hardware removed, then the next step would be to uninstall the MXI-3 Optimization software. What we are going after here is if it is during the run (every time at boot) of the MXI-3 optimization software that the blue screen occurs.
    If none of these indicate the problem, then the "divide-and-conquor" approach requires us to determine if the problem is with the MXI-3 kit itself, or something specific to that computer. Two things to try. The first is to try the MXI-3 kit on a different machine. The second is to try another MXI-3 kit (if available) with that machine.
    Through these steps, you should be able to isolate a single piece of hardware (a PXI card, the MXI-3 kit, the PC, etc) that is common to the problem.
    (note, the bug referred to by Katie was specific to running the MXI-3 optimization software, not the MXI-3 hardware in general - so if you are seeing the problem she referred to, you should see the blue-screens disappear when the MXI-3 Optimization software is uninstalled).
    As always, National Instruments Technical Support is only a phone-call away (7am - 7pm CST) if you want to work with a NI engineer on this procedure.
    Regards,
    Greg Caesar
    Applications Engineer

  • Odd Error with decode function in Order By Clause

    I am trying to compile a procedure and can't get around an error with a dynamic order by that doesn't make much sense to me. I can repoduce the error with a plain select statment in sql plus so I can rule out a declaration error. Here is an example with 2 numeric columns and a date column.
    select task_id, display_date, remark_id from task_list
    where task_id > 1000
    order by decode('Task_ID', 'Task_ID',Task_ID, 'Display_Date', Display_Date, 'Remark_ID',Remark_ID)
    returns the error:
    select task_id, display_date, remark_id from task_list
    ERROR at line 1:
    ORA-00932: inconsistent datatypes: expected NUMBER got DATE
    I'm not sure why this error is occuring, because it doesn't even hit the Display_Date field in the Decode statment. If I take the Display_date out of the statement, it runs properly. If I change Display_Date to To_Char(Display_Date) it also runs fine, but the sorting is incorrect. Also I'm running 9.2, and do not want to use dynamic sql to build my query. Any Ideas out there as to the cause of this error?

    I did find a workaround to this issue by breaking the decode statment into three separate statement, but I still think that the way it is written above should work, and may be a bug, or an error that I don't understand fully.
    The Order by was rewritten like this:
    order by decode(pSort, 'Task_ID',Task_ID), decode(pSort, 'Display_Date', Display_Date),
    decode(pSort, 'Remark_ID',Remark_ID);
    Thanks

Maybe you are looking for