Automatic control NI6363

[Venus stride]

I have added experimental logic for controlling NI_PCIe_6363  , the code compiles successfully on the runmanager, it creates shot file but does not show any output on the multimeter.

[dihm....@gmail.com]

This type of issue is typically due to how the clocking terminal is wired up to the master pseudoclock (ie the NI board is not seeing clock ticks). That sort of thing can be tricky to debug remotely. Best I can suggest right now is ensuring that your master pseudoclock is putting out pulses at the correct times, that you can toggle the DAQ outputs using NI-MAX as expected, very carefully ensuring you have wired up the clock input as described in the docs, and finally very carefully ensuring you have written the correct commands (ie use runviewer or check the shot file to make sure what is getting programmed is what you expected).

-David

[Puzzle]

Can we bypass use of pseudoclock to run the experiment logic automatically by using Dummypseudoclock?

[Venus stride]

Can we bypass use of pseudoclock to run the experiment logic automatically by using Dummypseudoclock?

???

[dihm....@gmail.com]

Sort of. A dummy pseudoclock will allow the script to run without BLACS errors, but it won't function fully. The DAQ driver requires the external timing triggers of the pseudoclock to work correctly. It is more or less the foundational operating principle of labscript. If you just need to get something working quick and cheap, I highly recommend the prawnblaster (based on the Raspberry Pi Pico). I also know there is an arduino-based pseudoclock out there somewhere as well (though I can't find it at the moment).

-David