|
|
|
|
|
|
|
|
|
|
Q1 :
|
What operating systems does DAQNavi support?
|
|
|
DAQNavi can support Windows 8, Windows 7, Windows Vista, Windows XP, Windows Server (32-bit and 64-bit), Windows CE 5.0/6.0/7.0 and Linux.
|
|
▲TOP
|
|
|
|
|
|
|
Q2 :
|
Does DAQNavi offer example codes? If so, for which programming language and development tools?
|
|
|
DAQNavi provides many types of examples, including
1. C++ Console mode examples for VC6, VS2005, BCB6.
2. C++ with MFC UI example for VC6, VS2005.
3. Java examples for Eclipse 3.6
4. C# console mode example for VS2005
5. C# with .NET control for VS2005
6. VB.NET with .NET control for VS2005
7. OCX control for VB6 and Delphi 7
|
|
▲TOP
|
|
|
|
|
|
|
Q3 :
|
Is DAQNavi free and where can I get it?
|
|
|
DAQNavi is free for any user. You can download it from Advantech's website at www.advantech.com
and search using "DAQNavi" as the keyword and there will be a download
link.
|
|
▲TOP
|
|
|
|
|
|
|
Q4 :
|
What is the difference between the new DAQNavi driver and the old Adsapi32 driver?
|
|
|
(A) DAQNavi supports both 32-bit and 64-bit OS's, and Adsapi32 only supports 32-bit
OS.
(B) DAQNavi supports Windows 7 while Adsapi32 does not.
(C) DAQNavi provides object-oriented programming for users to develop programs.
(D) DAQNavi provides .NET control components for users to easily develop programs.
(E) DAQNavi provides the same API for different OS's; it is easy to migrate programs
between different OS's.
(F) DAQNavi supports Java and Qt programming.
(G) DAQNavi drivers are thread-safe.
|
|
▲TOP
|
|
|
|
|
|
|
Q5 :
|
The driver has been installed successfully on the device manager of the PC, but
I can't find any example for testing?
|
|
|
The reason is that you have only installed an individual device driver that includes
the driver and DLL to run executive files (after the development is complete).
If you want to develop applications and need an example, you should install the
DAQNavi SDK (you can also download it from the Advantech website), which includes
a device driver, examples, manual and tools.
|
|
▲TOP
|
|
|
|
|
|
|
Q6 :
|
Why can’t I run DAQNavi on a Windows XP Embedded environment?
|
|
|
.NET Framework 2.0 or newer needs to be installed on Windows XP Embedded to run
DAQNavi. DAQNavi needs .NET Framework, but it is not installed in XPE by default.
Note: It is suggested not to develop programs on Windows XP Embedded, because DAQNavi
SDK needs more resources from the operating system. The best way is to install the
individual device driver only and run executives on Windows XP Embedded.
|
|
▲TOP
|
|
|
|
|
|
|
Q7 :
|
I have written a program using the Adsapi32 driver. Can I run that same program
using the DAQNavi driver?
|
|
|
No. Users need to create a new program if they move from the old Adsapi32 driver
to the new DAQNavi driver. The API used by Adsapi32 and DAQNavi are totally different.
|
|
▲TOP
|
|
|
|
|
|
|
Q8 :
|
Using the Adsapi32 driver, my application runs correctly but after installing DAQNavi,
my application doesn’t run any more. Why?
|
|
|
You need to install the Adsapi32 driver again. The installation of DAQNavi will
delete the Adsapi32 system file. To recover the Adsapi32 system file, you should
install the Adsapi32 driver again.
|
|
▲TOP
|
|
|
|
|
|
|
Q9 :
|
I installed both Adsapi32 and DAQNavi drivers on my computer, why I can’t see my
module on the Device Manager Utility?
|
|
|
You need to uninstall DAQNavi and then assign Adsapi32 driver to the module. The
module is using the DAQNavi driver, that's why the old Device Manager Utility can't
detect the module. However, we suggest you change to use the new DAQNavi driver
for new project.
|
|
▲TOP
|
|
|
|
|
|
|
Q10 :
|
What parameters can be used to open the data acquisition and control device?
|
|
|
|
"Device Number" and "Description" can both be used to open the
device. "Description" can be renamed in the SDK or Device Manager settings.
See the picture below.
|
|
|
click to enlarge >>
|
|
|
▲TOP
|
|
|
|
|
|
|
Q11 :
|
Why doesn’t DAQNavi provide a thermocouple measurement example?
|
|
|
Use the "AI_instant" example as the thermocouple example. In the example,
configure AI input range as thermocouple type.
|
|
▲TOP
|
|
|
|
|
|
|
Q12 :
|
When I am running a DAQNavi example, why does the example always show the following
error message “Error Privilege Not Available”?
|
|
|
Check if your "Advantech Navigator" (utility) is under testing. To ensure
safety for driver usage, only one AP can have authority to perform write operation
for one device. Therefore, you cannot run "Advantech Navigator" and example
at the same time.
|
|
▲TOP
|
|
|
|
|
|
|
Q13 :
|
Which version of Visual Studio supports DAQNavi examples?
|
|
|
DAQNavi examples were built in Visual Studio 2005.
(Visual Studio 2003 or older versions aren't suitable for opening DAQNavi examples.
Users should use Visual Studio 2005 or above.)
|
|
▲TOP
|
|
|
|
|
|
|
Q14 :
|
Can I run examples without installing a hardware device?
|
|
|
Yes. In the examples, the default setting uses a virtual device, called "Demo
Device". If you want to run a "real" hardware device, you can change
the "Description" or "Device Number" to the values representing
your hardware device.
|
|
▲TOP
|
|
|
|
|
|
|
Q15 :
|
When I select "streaming AI" for continuous buffered AI acquisition application,
there is one parameter called: "interval count." What does it mean? and
what is the recommended way to set the value for that parameter?
|
|
|
Advantech DAQNavi driver will create a buffer in memory to receive AI data transferred
from DAQ device. Data from DAQ device will continuously be written to the buffer.
Every time the accumulated data number reaches a specific number (defined as "interval
count"), an event will be generated immediately. At the same time, you can
use API to move the data from that buffer to another memory or save it to hard disk
for following analysis or processing.
Note: It is suggested that "data count" value = "interval count"
value x N.
For example: Half-FIFO size is 2048, set interval count = 2048, data count = 4096.
|
|
▲TOP
|
|
|
|
|