DAQ-6024Eの割り込みレベルのエラー

使用アプリケーション 
 NI-DAQ　6.9.3
 NI-Measurement　&　Automation Explprer 2.2.0
 OS　 Windows2000
Measurement & Automation ExplorerからDAQCard6024Eのテストパネルを実行すると
『デバイスは指定された1つ目の割り込みレベルにて応答がありません』とエラーが表示されます。
しかしそのエラー表示のあと　テストパネルは実行され　最新のエラーも0　と表示されています。
この状態の時、DAQCard6024Eは正しく動作していないのでしょうか？ 
現在のIRQ割込みレベルは７となっています。

すみません。やはりくカード正しく動作していないようです。
http://forums.ni.com/ni/board/message?board.id=1170&message.id=2248
こちらに似た症状の物がありましたが
VISA　ランタイムエンジンという物を入れても解決しませんでした。

Similar Messages

  • HOW CAN I ACQUIRE AND DEPLOY DATA IN REAL TIME WITH DAQ 6024E?

    HI ENGINEER,
    I'M PROGRAMING AN APLICATION WHICH I NEED ACUIRING AND DEPLOYING AN ANALOGOUS SIGNAL IN REAL TIME.
    I HAVE:
    LabVIEW 7.0
    WINDOWS 2000
    DAQ CARD 6024E
    THE SIGNAL I WANT TO ACQUIRE IS 0-10 Vcd FROM A SENSOR, THE PROBLEM I HAVE, IS THAT I AM ACQUIERING THE DATA AND IT SEEM THAT THEY ARE UPDATING EACH SECOND, BUT I HAVE BEEN MOVING THE PARAMETERS SUCH AS TASK TIMING IN THE DAQ ASSISTANT VI AND NOTHING HAPPENS.
    CAN YOU TELL ME WHICH PARAMETERS I HAVE TO MOVE TO AQUIRE AND DEPLOY DATA IN REAL TIME

    Hi barron,
    If you want to see the data update quicker, you can decrease the value in the "Samples to Read" field of your DAQ Assistant. This number controls when data is transferred from the DAQ buffer to the PC. If the sampling frequency remains the same, but this field decreases, it means the buffered data will be returned more quickly.
    Hope this helps.
    Thanks,
    Lesley Y.

  • NI-DAQ 6024E Error code 10401

    Hi,
    after installing LabView 6.i on my PC (Windows XP) my NI PCI-6024E card
    does not work properly anymore... I can see it in the MAX, but it does
    not pass the device test. Error code is -10401 - Unknown device error.
    I'm using NI-DAQ software version 6.9.3.
    Can anybody help me?
    Thanks.

    "The following has happened: Some months ago the DAQ (PCI6024E) card from the customer was broken and NI sended us an other card (other repaired card). We shipped it to the customer, but he is still trying to use this card"
    Do you mean the card at one time was used error free ?
    I assume, it has.
    The first thing to do is to check on the card from measurement and automation (Max), and see if Max recognizes it. If not, then it is either that the driver got corrupted, or that the card is bad.
    If you decide to reinstall Nidaq, the you have to first uninstall the existing Nidaq/Max, the reinstall Nidaq (same version that existed on the computer or the most recent one)

  • RDA with DAQ 6024E

    Hi all!
    We are having a school project, where we are trying out remote data aquisition. We are running a computer with a PCI 6024E DAQ-card and using RDA-server to access it from another computer on the network using LabVIEW.
    The program itself works rather well, but we are concerned about one thing; if the LabVIEW-client looses connection with the RDA-server (faulty connection, PC crashing etc), the DAQ-card retains its output values. Is there a way to make the card return to some pre-defined default-settings when the RDA-server looses its connection? (In our case, turning off the pumps and valves so we don't flood the room =) )
    Thanks,
    Siggen
    Edit: spelling...
    Message Edited by Siggen on 12-01-2005 07:04 AM

    Hi Siggen,
    Are you using  TCP/IP for achieving RDA ?
    If , Yes, You can do this.
    Any loss of connection between client and server will result in and error being given by TCP/IP connection section of your program( If You are not using wait forever condition for time out)
    Whenever this error comes, connect it a Boolean case condition
    No error: Blank case
    Error reported: Just set your DAQ card Analog and digital channels to default values programatically( do suitable AO and DO write to achieve this) and stop your server program(if needed)
    Hope this helps
    Regards
    Dev

  • Daq 6024e + IR encoder

    Hi,
    I am using IR sensor to calculate the rpm of my wheel-- my problem is when I am using "low freq with one counter" initially it gives me rpm but then as I increase the rpm it gives me message that "data was overwritten before it could be read try using DMA or divide the signal before measurement" now I can not divide the signal in this method I assume-- now when I change the counter to other method like "high range or large range with with 2 ctr" it tells me immediately your signal is too slow for this type of method and increase the measurement time-- I even did that increased the time to upto 50.0 but same problem
    My Vi is attached -- How should I resolve this issue. As my wheel will move from rest and will gain some rpm and then stop-- so it will go from low to high to low.
    Thanks
    Attachments:
    counterencoder.vi ‏59 KB

    Hi tmdar,
    Were you able to see any changes upon changing the "samples per channel" parameter? You're right, it is possible that noise in the signal is being picked up as an event as well. Also, avoid running any unnecessary applcations on your computer while running this, or try running on a different machine to see if the results vary.
    LabVIEW comes with a Filter Express VI (Express >> Analysis >> Filter) which you can experiment with to perform different types of filtering. However, since this filtering is performed after the data has been acquired, it may not help with the data acquisition issue. You may need an external filter. Before taking this step, you should verify if the problem is in fact signal noise. Since you're using one counter for "Low Frequency with 1 Counter", you can use the other counter to generate a pulse train, which you can feed as the input for your counting, to see if you can get up to a higher frequency. If this works, the problem is likely with the signal source. Otherwise, the issue would likely be the system or the code (please verify that you're using the shipping example, "Measure Dig Frequency - Low Freq 1 Ctr")
    Thanks,
    Lesley Y.

  • Help required with DAQ and waveform generation

    Hi,
    I'm using DAQ 6024E card for waveform acquisition using LabVIEW 8.2 version. I've also attached my vi for your reference.
    My next step is , I want to add another waveform to the acquired waveform, i.e. I mean to say if the acquired waveform is a sine wave with 60 Hz frequency and amplitude of 8V peak-to-peak, I want to finally display a wave which is 8V peak-to-peak with sinusoidally changing freuency.
    To be more clear...I want a sine wave with frequency =  60 Hz + 1*sin( 2*pie**t).
    As cane bveen seen in my vi, I can extract the phase and magnitude of the original acquired signal.
    Can anyone help me out with this...as I'm not able to figureout how should I proceed next.
    Looking forward to hear soon,
    Regards,
    Rohit
    Attachments:
    test_analog.vi ‏162 KB

    You'd probably want to use the DAQmx VI's instead of the Express VIs, when doing something more exotic. You can start by converting the existing Express VIs to code by opening their front panels and saving them as a VI.
    Regards,
    André
    Using whatever version of LV the customer requires. (LV5.1-LV2012) (www.carya.nl)

  • 6024E - Error 10846: Unable to retrieve data fast enough error?

    I am using a PCMCIA DAQ 6024E on a Dell Latitude C610 (1Ghz) - I'm trying to do Double buffered analog acquisition over 4 channels
    Whenever I try to run the application (VC++6) i get "Error 10846 - Unable to retrieve data from the backgound acquisition buffer fast enough..."
    I have tried the sample program "Double-Buffered Asynchronous Scanning in Microsoft Visual C++ with NI-DAQ" downloaded from the NI website - has the same result: Error 10846...
    I just need to sample 4 channels at 1kHz continuously, extracting the data every 250ms max - are the following settings sensible:
    i16 iChan = 0;
    i16 iNumChans = 4;
    u32 ulCount = 2000
    i16 iUnits = 0;
    f64 dSampRate = 4000.0;
    f64 d
    ScanRate = 1000.0;
    static i16 piBuffer[2000] = {0};
    static i16 piHalfBuffer[1000] = {0};
    Tried loads of different variations - as well as stopping all other apps running and removing everything from inside the acquisition loop - don't know what to try next. Can anyone help? Cheers!

    Hi,
    The error you are getting is due to the fact that your application is not emptying the PC buffer fast enough so new data overwrites old data before they are copied to the application allocated memory. You can try increasing the buffer size and/or reducing the Scan rate, whichever possible.
    Regards,
    RamziH.

  • Daq with PocketPC any speed limit ??

    Hi ! HELP NEEDED !!!
    i need to sample 12 chanels with 16ksamples/s ....
    so its something like ... 200,000 ksamles/s ...
    and make some Min/Max calculations ...
    i want to use it with the PocketPC and the Daq 6024E .. and ofcourse LabView 7 ...
    the speet limit of daq .. is 200,000 ks/s .. so its ok ..
    but what PocketPC speed i need ??? (200Mhz, 300Mhz, 400Mhz) ... and if its actually possible to sample this speed on the PocketPC aplication ....
    anybody tried ???
    any body worked near the limits ???
    what amount of memory needed ??? 64 mb enought ??
    anybody ?? plz ??? :-)
    its too pity to buy and to find that its not working ...
    u can answere also to [email protected]

    200KS/s on the 6024E should work fine on 200Mhz StrongARM and 400Mhz XScale CPUs. 200/300Mhz XScales will probably not be fast enough. You will need to download the 7.0f1 patch for LabVIEW and the PDA module to get this level of performance (and to support multichannel).
    Due to various factors from both Windows CE and LabVIEW PDA, using the high-level multichannel acquisition VIs in a default PDA install you should expect to be able to acquire somewhere around 10s of contiguous data at 200KS/s. This can be improved to 50s by various means including a lower-level usage of the DAQ driver code. If you require continuous acquisition, this is achievable but more difficult to program, and may not be able to operate stably at 200KS/s.
    If you need more information a
    bout said lower-level programming please msg me privately.

  • How I use 2 AI with 1 AO in the same program without hardware errors?

    I have a machine with a Motor (velocity controled with PWM), a Strain Gauge, and a Encoder (inner the motor). This machine is controled with a LabVIEW 6.1 program in a computer with Intel Celeron 1.5Gb 360 Mb RAM and DAQ 6024E.
    In my program I have two AI Adquisition Waveform blocks with AI different ranged Channel (the firts in my Strain Gauge ranged -9 to +9 V) and the second in my encoder ranged 0 to +5 V), and one AO Generate Waveform (the PWM signal ranged 0 to +5 V). When I put on the program, the motor Glitches an my computer turns slow. It´s cause me problems!
    Whats the problem?

    You would probably get more info on this in the DAQ Discussion Forums, but I can help you out a bit here. The VIs that you are using are very high level VIs so there is a lot going on behind the scenes that you do not see. More importantly, they are synchronous, meaning that you have to wait until they're finished to do anything else. This is probably why your computer is slowing down. The UI may even freeze until you have acquired all the points you requested. I would suggest using the more advanced DAQ VIs to control your system. There are many examples that ship with LabVIEW which demonstrate how to use these. They allow you to build an asynchronous acquisition system so that other tasks may operate while the DAQ board is acquiring data.
    J.R. Allen

  • Difference between input and output values

    I am using NI DAQ 6024E and SCB 68.
    I have shorted one anlog output and input channel
    in the SCB 68 board itself.(differential connection). that is whatever ouput voltage
    i am giving at o/p channel 22 and 55 should come at i/p
    channel 68 and 34. But when i read the values in my VI,
    the input voltage is higher than o/p. why is the difference.
    I used default buffer size 1000 and AI Single scan and AO Single Update.

    There doesn't seem to be a problem with your pin connections.
    The SCB-68 has a temperature sensor that can be used as cold-junction compensation for thermocouple measurements. If the temperature sensor is enabled, it will use channel 0 of the DAQ device.
    Since you are connecting to channel 0 of the 6024E, I would make sure you have the temperature sensor of the SCB-68 disabled. You can disable the temperature sensor by using the switched of the SCB-68. The User Manual of the SCB-68 is linked below and provides the information on how to disable the temperature sensor (page 2-4).
    SCB-68 68-Pin Shielded Connector Block User Manual
    http://digital.ni.com/manuals.nsf/webAdvsearch/74C86ADEF0E4813F86256C84007CB3AB?OpenDocument&vid=niwc&node=132100_US
    I hope t
    his helps.
    Regards,
    Todd D.

  • Trouble creating a circular buffer

    I am using a DAQ-6024E multifunction IO card with LabVIEW 6.1. I am trying to play out encoded signals that are in a database. These signals are encoded in binary and decoded by a previous portion of the VI. This decoded data is then normalized at the start of the code that I provided, then sent to the DAQ card. I have tried several implimentations and this is the only one that seems to work properly for the most part. I am getting glitches, however every couple of thousand samples where it seems to drop about 100 samples or so. I am new to this and am sure that I am doing something incorrectly. If someone could take a quick peek and tell me what the problem might be, I would greatly appreciate it.
    Attachments:
    sample.vi ‏43 KB

    I tried running your VI, but there were many broken lines and missing controls, so it was kind of difficult to see what was happening. One thing I would suggest is using AO Configure to configure the system for Analog Output first. Also, try keeping a count of the number of updates done so that you can compare that with what you should have done. This may give you an idea of what's going on. Let us know what you find out.
    J.R. Allen

  • Alternative to PCI-6023E + PCI-6602

    Hello,
    I am already using a system to acquire 16 analog inputs data (at 50Hz) and 100Hz PWM signals (counters) and to send 100Hz PWM signals to external devices. Because it deals with 12 concurrent counters I bought 2 x PCI-6602 counter boards on top of a PCI-6023E for the 16 analog inputs (through a SC2345 box). This works all well.
    I now have to build a simplified and portable solution that has to run on a laptop. I was thinking about a DAQ-6036E or DAQ-6024E (or even DAQ-6062E) and keep a SC2345 but do not know if I will get the same functionalities particularly for the PWM counting (in and out). I have to be able to count the high edge of the square signal at 100Hz while acquiring my analog inputs; also be able to generate those 100Hz signals. Will I be able to connect my counter in and counter out (one of each) to the SC2345 to do that?
    Thanks for your comments,
    Christophe

    Hello Christ0phe,
    Looking at your current specifications and hardware, the best suitable solution for a portable appication with >2 counters would be the Compact RIO Platform.
    As this is an FPGA based platform, you can implement (theoretically) as much counters for PWM generation and reading as you want.
    As you are an existing DAQ user, you will not be able to reuse your existing code.  The cRIO platform uses the NI-RIO driver which is using some different program logic than the NI-DAQmx driver.
    Why is the Compact RIO platform the best solution?
    Well, the cRIO chassis can be powered by a simply DC power supply. Depending which chassis this is between 9 and 30 VDC.
    The cRIO platform also has a dedicated controller inside which will run your LabVIEW code.  The PWM logic itself can run on the FPGA integrated in the cRIO chassis.
    So, the laptop will not be use for any calculation, only for monitoring and control of your application.
    If you want to stay with the NI DAQ plaform I see two other portable solutions:
    The first one is to make the swtich to the PXI platform.
    There is a small chassis (PXI-1033) which has an integrated MXI-interface. Using MXI technology, you can control a PXI chassis from another PC, including a laptop (using ExpressCard, not PCMCIA).
    For the PXI platform you can use identical or similar DAQ boards as you have now, reusing your existing LabVIEW code.
    Drawback of the PXI-1033 is that it can only be powered by 230VAC, you will have to provide a DC-to 230VAC converter yourself to be able to use it in the field.
    For your information. It's becoming harder and harder to find laptops with PCMCIA slots, ExpressCard is the successor available on most new laptops.
    But please have a look at following article concerning laptop compatibility: http://zone.ni.com/devzone/cda/tut/p/id/5035
    A last solution is to use the cDAQ plaform.
    Again a fully portable DAQ solution, but as it uses the same technology as the 'normal' DAQ boards, it only has 2 counters on board.
    As your PWM speeds are quite slow, it may although be possible to use this platform for multiple PWM signal generation and reading.  All will depend on the desired PWM accuracy (resolution) and if they all share the same signal period.
    It is possible to use the 2 on-board counters as a known sample clock to generate and read the PWM pulses using correlated DIO.
    Correlated DIO means that your digital input and output signals are hardware clocked (synchronized with other available clock source). On the cDAQ platform, your I/O modules must be placed in slot 1-4 of the cDAQ chassis to be able to use correlated DIO.  Possible I/O modules are in the C-series 940x range.
    Drawback: all your calculations have to be done on the fly in LabVIEW.  You will need to write code to generate an array
    of digital waveform data, then output it using hardware timed DIO
    synchronized to generate counter clock.  For the readout of the PWM signal, you will have to count (within the LV application) the number of tick (of pulses) of the sample clock during which the PWM signal was 'high' and calculate based on the known timing information the PWM on-time, period (and if needed duty cycle). 
    More info about cDAQ and Correlated DIO:
    NI-DAQmx: Correlated Digital I/O with NI CompactDAQ and LabVIEW
    Can I Use Different Sample Clocks for Correlated DI and DO?
    Some examples exist:
    CompactDAQ - Generating More Than 2 Pulse Trains
    NI-DAQmx: Digital Channel Pulse Width Modulation (PWM)
    This info should already help you make a selection.
    But please contact you local National Instruments office if you need more information.
    Best regards,
    Best regards,
    Joeri
    National Instruments
    Applications Engineering
    http://www.ni.com/ask
    Make our forums great:
    If you like the answer, don't forget to "Kudos!".
    "Accept the Solution" if your question is answered!

  • Ground loop + BNC 2120 behaving like antenna(pr​oblem)

    Hi,
    I am using DAQ 6024E, and using two sensors and one error message "data is overwritten before it could be read
    by the system try divide the signal before measurement" --it took me whole day as to what data is going inside that my computer with 900Mhz processor is unable to handle. I started tearing my hardware step by step. I looked at my range sensor which has one LED which blinks as it throws waves out - but the moment my motors gains speed all of a sudden my labview generates error that "data overwritten before it could be read by the system", now at the same time I looked at my range sensor and instead of blinking slowly like persec it was blinking continuously without break so I took the wire out which was going into the BNC 2120 and the sensor becomes stable again.
    I thought that may be the wire is picking up RF signal from motors so I changed all the wires with shielded insulated wire but again as I switched my motors on labview generates the same error. If motors stays off there is no error. I felt my BNC is acting like antenna and is catching motor RF signals. I took motor out of the circuit and supplied separate voltage from another power supplier and it confirmed me that moment my motor speeds up the range sensor speed of blinking increases but If I take out the signal wire going into BNC 2120 then there is no effect on range sensor and it works fine steady. moment I connect BNC with sensor and motors ON then sensor behave erratically with led blinking extremely rapidly.
    So it is confirmed that nothing is wrong with hard ware of computer but some strange phenomenon.
    Now next I powered my controller with a battery and motors with another power supply to break the loop but problem not solved, I think there is some ground loop thing going on and that is making BNC 2120 as antenna for RF signal created by motor.
    That's why initially at less voltage/speed VI works fine but as motors speed up VI stops working and generating the error " data is overwritten before it could be read
    by the system try divide the signal before measurement"
    I hope now you are in better situation to understand what is happening and how can I stop BNC wire to act like this, remember I am using good insulated shielded wire.
    Thanks

    I've got fast fingers, I play lead guitar in a rock n roll band (nah, just wish I did, but I do play lead guitar - just a bit rusty at it right now). I've spent the last 20+ years being a test engineer at various places. I learned from some of the best at AT&T and Bell Labs (when they were a big dog in the 80's). Before that I was a mobile radio repair technician for 8 years. Learned RF and electronic repair on the job. Troubleshooting background has helped me tremendously in the test engineering world. Also spent three years doing SCADA engineering so I am familiar with PLCs (Motorola, Allen Bradley, and GE Fanuc) and HMI software (Wonderware and GE Cimplicity). SCADA was fun, but I prefer the RF world.
    Getting back to the problem, you give good advice about grounding only one end of the shielded cables. Grounding both ends does cause problems with non RF signals. A scope will go a long way to determine where the problem is coming from. But since he mentioned ultra sonic sensors, I am wondering if the problem is actual sonic noise from the motor. I would not be able to hear it because I lost all hearing above 12KHz from all that loud guitar playing when I WAS in a rock n roll band.
    BTW, your name reminds me of the Rush song, Analog Kid, and also of the progression of analog synthesizers to digital ones, and now there is a movement back to the analog dinosaurs again.
    - tbob
    Inventor of the WORM Global

  • I want to increase the range of the current that my program can measure.

    I have NI-DAQ 6024E and CB-68LP connector.I'm using pins 68 & 67 for input current that is to be measured.It somehow reads 20 mA when it's 200 and 30 mA when it's 300!! Also please tell me how can I increase the current range that can be read by this program and hardware as it currently reads upto 500 mA and I need to read upto 1 A.

    Hi Mark, basically if I connect the terminals of my valve to ACH0 and ACH8,then it'll be a parallel connection.Here surely I'll get the voltage to read and i can divide by my resistance to calculate the current, but I dont want to do that.That is possible even with a regular calculator.Here I have a program that reads current directly but somehow I'm not able to read proper current.And my valve is a current controlled device so the more current I pass through it, more does it open.Now with the attached program,I want to know how to exactly wire my valve with the CB-68LP connector so that I can read the current.Please also suggest me how exactly to put the resistance in the circuit.
    Attachments:
    cont_current_meas.vi ‏58 KB

  • Measurement studio expired first day I install

    Hi,
    I download Measurement Studio 2009 for Visual Studio Evaluation yesterday. I installed it with Labview 2009 and DAQmx 9.2.1. My OS is XP sp3. I have a DAQ card DAQ-6024E. And I tried to output a analog signal using the card. So, I found out there is an example from NI after installation named "GenVoltageUpdate" in the folder  \NI-DAQ\Examples\MStudioVC2008\Analog Out\Generate Voltage\. I used VS 2008 to try to run this program in debug mode. There was a box popped up "The Measurement studio evaluation has expired". I checked the Measurement Studio>> License, and it shown as the figure attached. None of them has expired yet.
    I don't know why there is such message about expiration. I hope someone can help me.
    Thank you very much.
    Attachments:
    新图片.jpg ‏246 KB

    Hi, I installed today (02-12-2011) the evaluation version of Measurement studio 2010 for Visual Studio 2008.
    Checking the licence page from the Measuremt studio menu I get thet all the components I installed should expire on 13/03/2011.
    The problem is that if I try to execute any sample code provided I get the following error:
    System.ComponentModel.LicenseException was unhandled
      Message="NationalInstruments.UI.WindowsForms.WaveformGraph evaluation period has expired."
      Source="NationalInstruments.Common"
      StackTrace:
           at NationalInstruments.Restricted.EvalReleaseLicense.ShowEvalBehavior(Type type, Object instance, String licenseString)
           at NationalInstruments.Restricted.EvalReleaseLicense.ComponentRunTimeCheck(Type type, Object instance, String licenseString)
           at NationalInstruments.Restricted.LicenseBase.PerformRunTimeCheck(Type type, Object instance, String runTimeLicense)
           at NationalInstruments.Restricted.LicenseBase.RunTimeCheck(LicenseContext context, Type type, Object instance)
           at NationalInstruments.Restricted.LicenseProviderBase.GetLicense(LicenseContext context, Type type, Object instance, Boolean allowExceptions)
           at System.ComponentModel.LicenseManager.ValidateInternalRecursive(LicenseContext context, Type type, Object instance, Boolean allowExceptions, License& license, String& licenseKey)
           at System.ComponentModel.LicenseManager.ValidateInternal(Type type, Object instance, Boolean allowExceptions, License& license)
           at System.ComponentModel.LicenseManager.Validate(Type type, Object instance)
           at NationalInstruments.UI.WindowsForms.WaveformGraph..ctor()
           at NationalInstruments.Examples.Plotting.MainForm.InitializeComponent() in C:\Documents and Settings\All Users\Documenti\National Instruments\MStudioVS2008\DotNET\Examples\UI\WindowsForms\Graph\Plotting\cs\MainForm.cs:line 64
           at NationalInstruments.Examples.Plotting.MainForm..ctor() in C:\Documents and Settings\All Users\Documenti\National Instruments\MStudioVS2008\DotNET\Examples\UI\WindowsForms\Graph\Plotting\cs\MainForm.cs:line 37
           at NationalInstruments.Examples.Plotting.MainForm.Main() in C:\Documents and Settings\All Users\Documenti\National Instruments\MStudioVS2008\DotNET\Examples\UI\WindowsForms\Graph\Plotting\cs\MainForm.cs:line 274
           at System.AppDomain._nExecuteAssembly(Assembly assembly, String[] args)
           at System.AppDomain.ExecuteAssembly(String assemblyFile, Evidence assemblySecurity, String[] args)
           at Microsoft.VisualStudio.HostingProcess.HostProc.RunUsersAssembly()
           at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
           at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
           at System.Threading.ThreadHelper.ThreadStart()
    I tried using the Measurement studio active-X License fixer. In the Licensed controls list there is "3D Graph control 8.0" but in the Elvaluation Licenses list and the Broken Licenses list the is no controls at all.
    Is there something else I can do?
    Best regards, 
    Mark

Maybe you are looking for