Still can't export CRIO-9002 configuration from NI-Max.

[Penny]

Hi,

We have a CRIO-9002 and are running LabView 8.01
and DAQmx 8.1 .  We recently upgraded to these packages
from LabView 8.0 and DAQmx 8.0, and then mass-
recompiled everything.  We have been using the CRIO-9002
to run our X-ray machines from my desktop computer.  As a
next step, we would like to build a stand-alone executable
to run the X-ray machine from a different computer.

There seems to be one small remaining difficulty in building
the stand-alone executable for a different computer.  So far
I have built a stand-alone executable for my desktop machine,
and run it.  Everything looks great.  It talks to the RT VI that
is running on the CRIO-9002, via the shared variables.

The problem arises when I try to build an installer for the
executable.  In the last step of the build configuration, I try
to include the CRIO-9002 hardware configuration in the
installer.  Before the upgrades it crashed with error -50150;
after the upgrades a dialog box pops up saying "no exportable
data".  The end result is an installer that installs and runs our
host.vi on another computer, but can't talk to the RT VI on the
CRIO-9002.

So, I shut down LabView entirely, and looked at the CRIO in
NI-Max.  I tried to export the CRIO hardware configuration using
NI-Max's File->Export->CRIO9002, and got the same dialog box
saying "no exportable data".

We are wondering if NI-Max is supposed to support the CRIO-9002
for File->Export.  If it doesn't, we are wondering how we can put
our CRIO-9002 hardware configuration into the installer to build
the executable for a different computer.

Any thoughts would be appreciated.

Thanks,
Penny

[JMota]

Hi Penny,

I can answer one of your questions (unfortunately it does not tell how to solve the problem, but at least it gives a bit of guidance).

>We are wondering if NI-Max is supposed to support the CRIO-9002 for File->Export.

No, there is no configuration in NI-MAX to be exported for a cRIO-9002 controller.

Seems that the problem is lying in how the executable/installer will get built into it information about the variables that the cRIO-9002 exports. My guess this is a "variable configuration" problem and not a "hardware configuration" one, which is beyond my expertise.

JMota