RDA slow connection

[JD2]

I am using RDA to configure and measure using a PCI-6025E. Here is the problem, when I
compile and run my application it takes about 1.5 minutes before the applications
front panel is displayed (it appears on the task bar minimized). When it is finally
displayed everything works fine.


Now with MAX open and the following expanded:
My System\Devices and Interfaces\Traditional NI-DAQ Devices\PCI-6025E
I can run the program again and it connects instantly.

Is there a way to stop this 1.5 minute delay without MAX having to be opened and
the device list expanded?

I am using LabView 7.1 and both the client and server are using NI-DAQ 7.3.1

Any help would be greatly appreciated.

JD

[George M.]

Hi,

I tried to duplicate your problem with no success. I used RDA in LV 7.1 and DAQ 7.3.1, using both an executable and standalone VI. In both cases, there was a 1-2 second lag before the acquisition began, and this was not dependent on whether or not MAX was open. Is it only when MAX is open that you don't experience the lag? Once you do it with MAX open, have you tried closing down MAX and trying it again? Is this lag independent of when you open MAX? Is there a lag when you initially open up MAX? What kind of computer are you using, as well as, what type of ethernet connection do you have. Let me know more specifically when and how you experience the lag, and we can go from there. Have a Great Day!

George

[JD2]

Hello George,

To answer some of your questions:

> Is it only when MAX is open that you don't experience the lag?

The lag does not exist when MAX is runngin BUT ONLY if I have expanded the tree to the following;
"My System\Devices and interfaces\Traditional NI-DAQ Devices\...device list..."

If I only expand the tree to "My System\Devices and Interfaces" and run the program
I get the 1.5 minute delay.

> Is this lag independent of when you open MAX?

No, as I stated above I must expand to "..\..\Traditional NI-DAQ Devices\..."
before the lag disappears.


> Is there a lag when you initially open up MAX?

Only a couple of seconds within MAX to expand the "..\..\Traditional NI-DAQ Devices" tree node.


> What kind of computer are you using?
Dell/Celeron and XP Professional

> What type of ethernet connection do you have?
100Mbps Ethernet


It even gets a little deaper than this. If I create my own program using Visual C++ and link to
nidaq32.dll and run the program I get the same 1.5 minute delay. When I run the debugger and break
the program during this delay and look at the call stack it displays the following:

NTDLL! 7c90eb94()
MSWSOCK! 71a557c9()
WS2_32! 71ab4379()
WSOCK32! 71ad2ea3()

It's hung up in Microsoft Proprietary WinSock API. Now I do beleive that I read somewhere that
nidaq32 polls the network for remote devices when it loaded into memory and I think this is
where the delay is occuring.


Thanks,
JD

[sergesl]

Hellow JD2,

I am wondering if the problem is network related or PC related. Have you tried this on a different computer?

Serges L.

[JD2]

Serges,

Yes this happens on several computers on our LAN as well as the LAN at a
customers site.

Best Regards,
John

[JoeSavage]

Hi JD, in your Visual C++ program where you link to nidaq32.dll, do you see nidaq32.dll (or any other ni*.dll's) on the call stack during the 1.5 minute delay? If you can give me the complete call stack with addresses, I can probably figure out where the delay is coming from.

Also, have you experimented at all with firewall settings to see if perhaps a software firewall is involved at all in causing this delay?

Thanks,
Joe

[sergesl]

Hello JDA,

I am guessing that you have several configurations saved in MAX and during this delay, MAX is polling every device and possibly the network to make sure that everything installed is detected. If you do not need any configuration that you have in MAX other than running your program, one thing you might want to try is to erase everything in C:\Program Files\National Instruments\MAX\Data . Bare in mind that this will erase all your configurations. However, this usually speeds up the process.

[jstipes]

I'm seeing the exact same problem. Is there any definitive solution yet, or are we still groping in the dark?

[nealpederson]

I didn't see the beginning of this post but I've had major and consistent
problems with RDA ever since LabVIEW 7.1 was released. If I have RDA setup
and between computers and I try to load a VI that traditional DAQ without
loading LabVIEW 7.1 by itself first (i.e. double click on VI before opening
LabVIEW) LabVIEW 7.1 will crash. I believe this is because of the slow RDA
loading in LabVIEW 7.1.

LabVIEW RDA is also not supported with DAQmx. I'm hoping NI will fix the
problems and support RDA with DAQmx. It is extremely valuable, especially
if you develop programs on a notebook but use a networked PC to hold your
PCI DAQ cards.

"jstipes" <x@no.email> wrote in message
news:1129034435543-276267@exchange.ni.com...
> I'm seeing the exact same problem. Is there any definitive solution yet,
> or are we still groping in the dark?

[Ryan_V[DE]]

jstipes,

What exactly is your network topology? Have you tried a crossover cable between your two computers? Perhaps you could try an NI-Spy capture (Start->Programs->National Instruments->NI Spy) to observe network activity during the load. Please let me know the results of this testing.

Thanks,
 

Message Edited by Ryan V on 10-12-2005 03:50 PM