LabVIEW 7.1, RDA Bug?!

[nealpederson]

Has anyone else noticed the following using LabVIEW 7.1 and RDA (remote data
acquisition)?



Setup one or more RDA devices on the local machine to control hardware on a
remote machine using Traditional DAQ (RDA is not supported with DAQmx).
Create a VI in LabVIEW 7.1 that calls any Traditional DAQ function and save
it. Close LabVIEW 7.1. Double click on the created VI to start LabVIEW 7.1
and the VI simultaneously. What happens on the computers I've tried this on
is that the LabVIEW startup hangs up. I can load LabVIEW and then the VI
but not both at the same time. More importantly, if I build an application
I have the same problem so presently I am unable to build an application
from LabVIEW 7.1 that uses RDA. This does not occur in LabVIE
W 7.0 or
earlier.



Has anyone else seen or not seen this behavior? Are there any work arounds
or bug fixes that anyone knows of? NI Tech support had not heard of the
problem but it is very repeatable for me on all the machines I have tried it
on.

[Spencer S.]

Neal,

I have a quick question. Which version of NI-DAQ do you have installed on the server and client machines?

Spencer S.

[nealpederson]

I've tried the following NI-DAQ cominations with the same result:

7.2 client - 7.2 server (this is the main setup I want to use)
7.3 client - 7.2 server
7.3 client - 7.0 server
7.2 client - 7.0 server

"Spencer S." wrote in message
news:506500000005000000E8C10100-1079395200000@exchange.ni.com...
> Neal,
>
> I have a quick question. Which version of NI-DAQ do you have
> installed on the server and client machines?
>
> Spencer S.

[Spencer S.]

Neal,

Thanks for the additional information. I tested the procedure you have described with NI-DAQ 7.3 installed on both the client and server machines. Everything functioned correctly. It does not appear that you have tested this particular setup. Could you try it?

Spencer S.

[nealpederson]

Spensor,

That is difficult for me right now. The big system I was working on that
has several PXI chassis has gone back to my customer. On that system I had
to create my application with LabVIEW 7.0 as a temporary solution. In my
office I my RDA server machine runs Windows 98 and NI-DAQ 7.3 is no longer
supported with that OS.

Were you able to reproduce the problem with NI-DAQ 7.2? I would be
supprised if 7.3 would fix the issue because I don't believe traditional DAQ
has changed in the last couple of NI-DAQ releases but I could be wrong.

"Spencer S." wrote in message
news:5065000000050000005CC30100-1079395200000@exchange.ni.com...
> Neal,
>
> Thanks for the additional information. I tested the procedure you
> ha
ve described with NI-DAQ 7.3 installed on both the client and server
> machines. Everything functioned correctly. It does not appear that
> you have tested this particular setup. Could you try it?
>
> Spencer S.

[LA 75]

Neal,

NI-DAQ 7.2 does not support Windows 98 either, maybe that's why you were having that problem. Try using NI-DAQ 7.1, which is supported by your OS and by LabVIEW 7.1. Remember that both computers (the server and the client) MUST have the same version of NI-DAQ installed on them when doing RDA.

Please let me know how everthing works out.

Thanks,

LA

[nealpederson]

In my office I actually have NI-DAQ 7.0 on my Windows 98 machine and NI-DAQ
7.3 on my Win XP laptop. I've had this problem since LabVIEW 7.1 was
released so my laptop has had previous versions of NI-DAQ too.

The main system that I was trying to make this work on had NI-DAQ 7.2 on Win
XP PXI controllers and NI-DAQ 7.2 on the Win XP laptops. All of these
computers and PXI chassis were brand new systems. I no longer have these in
my office to test with so I am trying to setup another computer that has Win
XP and NI-DAQ 7.3 but haven't had time to install DAQ cards on it yet.

"LA" wrote in message
news:50650000000500000077C80100-1079395200000@exchange.ni.com...
> Neal,
>
> NI-DAQ 7.2 does not support W
indows 98 either, maybe that's why you
> were having that problem. Try using NI-DAQ 7.1, which is supported by
> your OS and by LabVIEW 7.1. Remember that both computers (the server
> and the client) MUST have the same version of NI-DAQ installed on them
> when doing RDA.
>
> Please let me know how everthing works out.
>
> Thanks,
>
> LA

[LA 75]

Hello Neal,

The new system that you are trying to setup should work (Having Win XP in your PC connected to the PXI chassis, having NI-DAQ 7.3 installed on it, and having the Client PC with NI-DAQ 7.3 installed on it too.)

Please let me know if it works, otherwise we'll do some troubleshooting to get this to work.

Thanks,

LA

[Ben]

Possible clue?

I believe I read about a INI setting that controlled if LV went out and verified all of the virtual channel names in MAX at start-up. With remote system configured, LV may be trying to verify the connections to the other machines.

Ignore this post if this does not help,

Ben

[nealpederson]

LA,

I now have a DAQ card in my WinXP computer. It has NI-DAQ 7.3 with RDA
running and my notebook has NI-DAQ 7.3 installed.

On my notebook if I double click on a VI that has traditional DAQ I
eventually get the message "The executable file "c:\..(path to my VI)"
cannot be found". The VI does eventually load after a very long time but I
still get the error message. I then tried running a LabVIEW 7.1 built
application with the new DAQ driver. It also took a really long time to
load but eventually came up.

Can you look into the possible clue that Ben sent abou the INI setting or
anything else that might be causing the slow load? I am further than I used
to be but don't like the really slow lo
ad time and am worried things will be
worse when I try my customer's system that has 3 PXI chassis with 5 cards on
each chassis.

"LA" wrote in message
news:5065000000050000005DC90100-1079395200000@exchange.ni.com...
> Hello Neal,
>
> The new system that you are trying to setup should work (Having Win XP
> in your PC connected to the PXI chassis, having NI-DAQ 7.3 installed
> on it, and having the Client PC with NI-DAQ 7.3 installed on it too.)
>
> Please let me know if it works, otherwise we'll do some
> troubleshooting to get this to work.
>
> Thanks,
>
> LA