PicoScope 7 Software
Available on Windows, Mac and Linux
LabVIEW Examples Break Dataflow
LabVIEW Examples Break Dataflow
Hi,
The PicoScope5000aExampleRapidBlock.vi and PicoScope5000aExampleRapidBlockBulk.vi break the data flow paradigm in LabVIEW by the driver writing directly to LabVIEW memory instead of passing the buffer out of a DLL call. This is evident by putting a probe on the buffer wire before and after it leaves the for loop. Is there another way to get data out of the driver and into LabVIEW?
Here is more:
https://forums.ni.com/t5/LabVIEW/When-is-dataflow-not-data-flow-Updating-LabVIEW-Arrays-through/td-p/3620100
The PicoScope5000aExampleRapidBlock.vi and PicoScope5000aExampleRapidBlockBulk.vi break the data flow paradigm in LabVIEW by the driver writing directly to LabVIEW memory instead of passing the buffer out of a DLL call. This is evident by putting a probe on the buffer wire before and after it leaves the for loop. Is there another way to get data out of the driver and into LabVIEW?
Here is more:
https://forums.ni.com/t5/LabVIEW/When-is-dataflow-not-data-flow-Updating-LabVIEW-Arrays-through/td-p/3620100
Re: LabVIEW Examples Break Dataflow
Hi ,
I would also be interested in this to improve the current way this LV example work. Thx
L.
I would also be interested in this to improve the current way this LV example work. Thx
L.