- From: Frank Mori Hess <fmhess_at_speakeasy.net>
- Date: Wed, 12 Jul 2006 20:32:12 -0400
On Wednesday 12 July 2006 02:51 am, you wrote: > Thanks for the idea, Frank, but I don't think that will work for my > application on the NI PXI-6031E (at least not conveniently or easily). > I may not be understanding your idea fully/correctly, but it sounds like > you're suggesting using GPTC resources to divide the external clock > frequency to generate timing signals rather than using the existing > frequency dividers already present in the various subdevices (e.g. > analog in, analog out, etc). That's not so great for me since I would > need to use both of the 6031E's GPTCs (one for scan_begin and one for > convert). Please let me know if this is an incorrect interpretation. No, that's not what I'm saying. I'm saying I don't want different drivers coming up with different configuration instructions to perform the same function. > > AFAICT, INSN_CONFIG_TIMER_1 is not implemented in the NI drivers (it > seems to only be implemented in cb_pcidas64.c), so it would still > require a patch to the NI drivers. Since I would need to use two GPTCs > (again, please correct me if I've misinterpreted your idea), I think I > would also need an INSN_CONFIG_TIMER_2. Finally, if I use TRIG_OTHER > for both scan_begin and convert, how would I tell the driver which timer > to use for which? That is what the data[1] element of INSN_CONFIG_TIMER_1 is for. It specifies which trigger you are setting the divisor for. -- Frank
Attachments
- application/pgp-signature attachment: stored
Received on 2006-07-12Z23:32:12