On 01/27/2015 03:48 AM, Yann Sionneau wrote: > Actually I was thinking about using the PyDAQmx project ( > http://pythonhosted.org/PyDAQmx/ ) and provide a direct access to the PyDAQmx > API through the ARTIQ RPC mechanism. > The PyDAQmx API being itself a direct wrapping/binding of the NI DAQ mx ANSI > C driver API. > > So for instance you would be able in your ARTIQ client to directly call the > following methods of the RPC'd object: > - DAQmxCreateTask() > - DAQmxCreateAIVoltageChan() > - DAQmxCfgSampClkTiming() > - DAQmxStartTask() > - DAQmxReadAnalogF64() > - DAQmxStopTask() > - DAQmxClearTask() > ... and so on. > > Would this be acceptable?
That should be fine for the controller part of the driver. Experiments using it will need another (local) class to provide higher level functions (that look like the PDQ API) and integration with the core device to generate the precisely timed waveform advance pulses. Sébastien _______________________________________________ ARTIQ mailing list https://ssl.serverraum.org/lists/listinfo/artiq
