Mike,
I'm a bit curious why you chose to implement
your application this way. Is there a particular
reason you need to call the NI-DAQ API layer
through a DLL call from LV?? Is there a
particular function not exported through a
LabVIEW VI that you need? Based on what you are
trying to achieve, this should be very easy to do
using the LabVIEW DAQ VI's for Digital I/O. The
advantage of using the VI's is they typically
combine several NI-DAQ functions into a single
VI... not to mention saving yourself a ton of
work by not having to configure a call-library
node for each function call.
I suspect the root of your problems stem from the
fact that the NI-DAQ code changed substantially
between versions of 6.x and 6.5.x. Prior to
version 6.5.x, we did not support incremental
buffer reading of the input transfer buffer, but
rather only supported true "double bufferring"...
allowing you to only read in half-buffer
increments. This changed in 6.5.x, which ships
on your LabVIEW 5.1 CD. This is all very
transparent if you use the LabVIEW DAQ VI's. I
highly recommend this. For your application, it
should require no more than 4 VI's (Config,
Start, Read, and Clear) for the pattern
generation, and only a single VI for toggling the
individual line. Extremely easy. We have example
programs, that show off each of these, that ship
with LabVIEW. Additionally there is a 32HS
dedicated support section of our website, with
example code and everything. It is available
from: http://www.natinst.com/support/
Best Regards,
Brian Johnson
National Instruments
DAQ Product Support Engineer
In article <7miu3l$sa0$1@nnrp1.deja.com>,
mike wrote:
> I would like to know if anyone can help with
this problem. NI tech
> support has flat out not answered my questions.
Their "solutions"
> haven't worked either. I want to try this
before I pay them more money
> for a service contract.
>
> I had been using various applications that used
the "Call Library
> Function VI" to access NI-DAQ functions in the
nidaq32.dll. It worked
> great until we started upgrading to LabVIEW
5.0.1f1 and 5.1. Has anybody
> else had problems with NI-DAQ functions when
upgrading LabVIEW?
>
> Here are some details: an example application
first configures the
> AT-DIO-32HS using Init_DA_Brds, DIG_Grp_Config,
DIG_Block_PG_Config, and
> DIG_Trigger_Config in that order. This sets up
the board for pattern
> generation, input, on group 1, ports 0 and 1,
with a start trigger on
> ACK1, with an internal clock on REQ1.
(DIG_Grp_Config is called again to
> un-configure group 2 so that port 4 pin 3 can
be used as an output.)
> After the board is configured I loop data
capture using DIG_Block_In,
> DIG_Out_Line (for the trigger on port 4 pin 3),
and the DIG_Block_Check
> is in a while loop to make sure the data
capture is finished before
> continuing.
>
> This worked great on LabVIEW 5.0 or older.
>
> When machines were upgraded to 5.0.1 or newer
here is an example of what
> went wrong:
>
> On LabVIEW 5.0.1f1, if DIG_Block_In was set to
read 8192 vectors, it
> would read a seemingly random number instead
such as 4000 and then stop
> (resulting in an endless while loop from
DIG_Block_Check). When I forced
> the while loop and looked at the 4000 vectors,
the first 2000 would be
> zeros, and the second 2000 would be accurate.
This problem was fixed by
> installing an older version of NI-DAQ (6.0.0
instead of 6.1.0 ?).
>
> On LabVIEW 5.1, the data capture works only if
the configure is repeated
> everytime. If the config is only done once, the
second data capture does
> the above. That was fixed by running the config
everytime but it is not
> a good fix because it wastes too much time.
>
> LabVIEW 5.1 seems to have other problems like a
memory leak and
> sometimes when I click FILE -> OPEN nothing
happens. The memory leak
> takes a whole system reboot to fix, the FILE
OPEN gets fixed after
> re-starting LabVIEW. But one thing at a time I
guess.
>
> Can anyone help with this?
>
> Thanks in advance - Mike
>
> Sent via Deja.com http://www.deja.com/
> Share what you know. Learn what you don't.
>
Sent via Deja.com http://www.deja.com/
Share what you know. Learn what you don't.
