> Vee is only single thread, ...
That's not completely true, or at least it didn't use to be. IIRC, Direct I/O to VXI Register based devices were separate threads - and it was the way to create a scanning voltmeter with separate switch cards and voltmeter. Think about it - a scanning voltmeter has a voltmeter that waits for the switch card to say "ready" before it takes a measurement, and the switch card waits for the voltmeter to say "next" before it advances. Without separate threads it can't do that under software control (you would need external hardware trigger instead). But with the DVM and switch under separate threads they run just fine. (And this is the reason why the non-Direct IO didn't work -- they don't use a separate thread and therefore lock each other out.)
~~Les
---
You are currently subscribed to vrf as: ming_meng@agilent.com
To subscribe please send an email to: "vrf-request@lists.it.agilent.com" with the word subscribe in the message body.
To unsubscribe send a blank email to "leave-vrf@it.lists.it.agilent.com".
To send messages to this mailing list, email "vrf@agilent.com".
If you need help with the mailing list send a message to
"owner-vrf@it.lists.it.agilent.com".
Search the "unofficial vrf archive" at "http://www.vrfarchive.com/vrf_archive".
Search the Agilent vrf archive at "http://vee.engineering.agilent.com".
That's not completely true, or at least it didn't use to be. IIRC, Direct I/O to VXI Register based devices were separate threads - and it was the way to create a scanning voltmeter with separate switch cards and voltmeter. Think about it - a scanning voltmeter has a voltmeter that waits for the switch card to say "ready" before it takes a measurement, and the switch card waits for the voltmeter to say "next" before it advances. Without separate threads it can't do that under software control (you would need external hardware trigger instead). But with the DVM and switch under separate threads they run just fine. (And this is the reason why the non-Direct IO didn't work -- they don't use a separate thread and therefore lock each other out.)
~~Les
---
You are currently subscribed to vrf as: ming_meng@agilent.com
To subscribe please send an email to: "vrf-request@lists.it.agilent.com" with the word subscribe in the message body.
To unsubscribe send a blank email to "leave-vrf@it.lists.it.agilent.com".
To send messages to this mailing list, email "vrf@agilent.com".
If you need help with the mailing list send a message to
"owner-vrf@it.lists.it.agilent.com".
Search the "unofficial vrf archive" at "http://www.vrfarchive.com/vrf_archive".
Search the Agilent vrf archive at "http://vee.engineering.agilent.com".
I was reading a NI newsletter about using LV with multicore processors (see url), and I was wondering if anyone has tried this with Vee, or if it is possible? I have a process that reads two laser heads, and with this type of processing I could really speed up the testing.
http://zone.ni.com/devzone/cda/tut/p/id/6421
Thanks,
Steve
---
You are currently subscribed to vrf as: ming_meng@agilent.com
To subscribe please send an email to: "vrf-request@lists.it.agilent.com" with the word subscribe in the message body.
To unsubscribe send a blank email to "leave-vrf@it.lists.it.agilent.com".
To send messages to this mailing list, email "vrf@agilent.com".
If you need help with the mailing list send a message to
"owner-vrf@it.lists.it.agilent.com".
Search the "unofficial vrf archive" at "http://www.vrfarchive.com/vrf_archive".
Search the Agilent vrf archive at "http://vee.engineering.agilent.com".