error 200290 with 6361

[STM99]

John, 50150 is correct code It can run at 1 KHz but fails at 2 KHz I will try the delay STM

[STM99]

John, Jesse said I had the latest version I don't stop it because it crashes STM

[John_P1]

Hi STM,

If something is crashing other than the behavior you have previously described, then this sounds like yet another issue.  I'm assuming when you say it "crashes" you mean that you are receiving error -50150.  Could you please be more descriptive about what is happening and how to reproduce the behavior you are seeing? 

Assuming that you are receiving error -50150 due to previously having aborted the VI in the middle of the generation, you will need to reset the device.  This can be done in Measurement and Automation Explorer or in the DAQmx API.  Unplugging/Plugging the device back in is another option.

       

The next time you run the code, it should function properly.  If you exit the code by hitting the "Stop" button you now will have properly cleared the task.  On the next iteration, you would not run into -50150.  I can only reproduce error -50150 if I abort the VI, which it sounds like you are in fact doing.  After aborting the VI, -50150 would occur on all subsequent runs of the program until the device is reset.

Best Regards,

[STM99]

John, When I wrote "crash" I meant that before I learned to reset the device with MAX I had to reboot Windows to get it to run again at 1 KHz. It is behaving as you describe. I set to 1 KHz, run successfully. Press STOP button. Set to 2 KHz, run successfully. Press STOP button. Set to 5 KHz, run, get 50150 error. Set to 1 KHz, run, get 50150 error. Reset with MAX. Run successfully at 1 KHz. Back to 5 KHz, get 50150 error. Etc. STM

[Jesse_D]

Hi Steve, 

What happens when you run your code? Can you still hit above a megahertz? 

Even if your device is defective it seems weird to me that there is such a large discrepancy in what speeds it can hit. 

[STM99]

My code still runs just fine up to 6 MHz.

[John_P1]

Hi STM99,

Can you try the following VI (it's attached below as well in LV 2010):

I can't reproduce the behavior you are seeing for the life of me.  The VI below resets the device before configuring the task, and also has the abort button removed from the front panel.  Does running the VI as it is configured (just select your device) produce the -50150 error?

Best Regards,

[STM99]

John, It would not run as 8 bit but ran OK as 32 bit. BUT it did not actually make output pulses from the 6361. STM

[John_P1]

Hi STM99,

Are you using a 6361?  If so, the 8-bit should work, but not the 32-bit.  If you are using a 6363 then you would use the 32-bit instead of 8-bit.  What error do you get on the 8-bit example?
Ignore that comment--I sent the wrong VI, my mistake.

The output is just an array of 0s so you shouldn't expect to see any pulses.  The example is just to confirm that you can in fact update at higher rates.

This is the exact example that I posted earlier with two changes:

1. The device is reset before running the task (also the abort button has been removed).
2. I am writing a larger number of samples to the on-board FIFO.
   
   
   

What happens if you change the array size to 2 samples?  Assuming this works, then the only difference is that the device is now being reset before use.  This is the way to recover from the error after aborting the task prematurely.

Best Regards,

[John_P1]

Also, does the code I posted work at 10 M?  If so, just replace my array of 0s with the data that you actually want to generate.

Best Regards,