Waveform Global Variable FAILURE

[bradj0]

I am having problems using analog waveforms as a global variable. I am using OS9 and Labview Express 7.0.

First, I tried to add a Analog Waveform to a global variable VI and this would not work. There is a 'waveform' icon in my toolbox, yet it will not drag to the global variable (or any VI) file. The "digital waveform" variable works fine.

Second. I have LabView 6.0 on another OS9 machine. I did the same proceedure and it worked. I saved the VI and copied it to the LV 7.0 machine. When I tried to access the waveform LV7 runs strange: it doesnt save into the variable, or will crash (more often) LV7. If I double click on the global variable to startup LV7, the program fails to launch and hangs at the startup screen. If I delete the w
aveform variables then it will load up. Is there a patch for this bug? or has NI removed a functional component?

As well, LV7 takes FOREVER to load even when just executing from the app icon. Forever as in 2-3 minutes. LV6 takes about 10 seconds. Any ideas? Furthermore, and I think this is because I have only the full development and not prof development version, but when I tried to load a polyVI LabView will hang for several minutes and everytime I try to move the front panel around it hangs again! what an annoying way of preventing editing of polyVIs, is there somewhat to stop this?

And one final note: I am VERY disappointed by NI lack of committment to Mac. I placed an order for ~7 cards with cables and shielded boxes and LabView7.0 (~25k$) and was NEVER told that this would not work on OSX. I was under the complete impression that it would-- that was until it never worked and I searched on the NI website. The infamous, yes DAQ works on OSX, BUT you need to buy all new hardwar
e. It isnt a big deal to run OS9 over OSX, but it sure is shady the way NI promotes NI7 be for OSX and for OSX to support DAQ but then only if you use LV RT.


thanks for any help-
brad

[Philip_Courtois]

Hi Brad,

I tried to reproduce your issue on OS9.1, OS9.2.2 and OSX without luck. It was never a problem for me to create a Waveform Graph inside a global variable, and to read rfom and write to it within a VI. Also, I could not reproduce the polymorhic VI issue.

The issue about LabVIEW taking forever to load could be caused by the following:

On Mac OS 9 the network connection to Localhost causes an internet connection. Because Point to Point Protocol (PPP) connections can auto connect on network traffic, when LabVIEW tries to communicate through the localhost, a PPP connection is initiated. In order to prevent this you can:

1. Turn off Auto connect in your network settings control panel



2. Change your network configuration temporally to be
   your internal ethernet card.



3. Add or change this token to your LabVIEW Preferences File: SkipAutoLaunchVIs:[TAB]True

Note:Options 1 and 3 will disable some help and example finder functionality.


4. Disable TCP/IP support for the operating system. This setting can be found at Control Panels » TCP/IP » Options...

I hope this helps to make your LabVIEW fast and reliable. If not, please post a Support email on http://www.ni.com/support with your detailed system information, and we will have a better chance of troubleshooting your system.

Best regards,
Philip C.
National Instruments

[bradj0]

Hi Phillip, thanks for the suggestions. I fixed the slow loading problem, is was due to the webserver.

Second, I have narrowed down this 'polymorphic VI' problem. It isnt due to the VIs being polymorphic, it is due to the presence of the "Traditional DAQ Channel" object. If I load any VI that holds such an object, LabVIEW hangs for 2-3 minutes and then if I try to move the VI's window or edit anything in the VI it hangs again. I started a new VI and placed one of these objects in the VI and it hung immediately. My DAQ system is set to not use channel naming (just address them by number). I need to look through all the setting sand in NI-DAQ to make sure there are no conflicts and hopefully that will solve the problem. Any suggestions for a quick fix though?


thanks-
brad