Jump to content

vinayk

Members
  • Posts

    7
  • Joined

  • Last visited

    Never

vinayk's Achievements

Newbie

Newbie (1/14)

0

Reputation

  1. QUOTE(rolfk @ Oct 21 2007, 02:08 PM) As suggested I created a path constant and moved the sub-VI to the same location as the main-VI. Well...that solved the error problem but now the execution stops and is waiting at the 'call by reference node'. I do not see any errors. What should I do ? Download File:post-9618-1193846344.zip
  2. As suggested, I used a parallel while loop to seperate the calling of the sub-VI and it was working great, like said in the above posts, for very small applications. But for my actual application this method of calling sub-VIs is not working great. So I was trying to implement the 'Call by reference' method as suggested. But my 'Open VI reference' is giving an error 4001 which I could not figure out why. This is what I did to the 'Open VI reference': 1. created a constant at 'Type specifier VI refnum' by right clicking at that terminal 2. right clicked on the constant -> 'select VI server class' -> 'browse..' -> selected the sub-VI that was supposed to be opened 3. created a constant at 'file path' terminal and specified the location of the sub-VI This is the sample application... Download File:post-9618-1192817648.zip
  3. Thank you all. I was banging my head all evening yesterday trying to figure out how to get the main tasks running on my NI Panel PC. Your replies were very helpful. Vinay
  4. I have a VI with tasks that need to be running continuously no matter what as these tasks control the valves on a machine. But when I try to open a sub-VI to show the status of all the components on the machine, my main VI tasks were paused until I close the sub-VI window which hinders my application purpose. So I set the main VI priority to 'Time Critical' and the sub-VI to 'Background' but still doesn't work, moreover LabVIEW hung up on me when I called the sub-VI. Then I noticed in the help file this quote: "If another VI with higher priority calls this VI, the priority of this VI rises to match the priority of the calling VI." So when I called the sub-VI its priority is also raised to 'time critical' as that of the main VI. How else can I call sub-VIs without pausing the tasks in the calling VI? I created this simple example so that I can explain better. Block Diag of main VI : Block Diag of Sub VI : Main VI Front panel : Sub VI Front panel :
  5. After refering to the LabView Help, I figured out that when I call a low priority VI from a high priority VI, the low prioirty VI's proirity rises to match that of the calling VI. By doing so my math tasks that were supposed to be running on the actual high priority VI were paused which does not serve my purpose. Any suggestions please... I created this simple example to better explain what I am doing. I set the main VI priority to Time-Critical and the Sub-VI priority to Background. LabVIEW Task Manager Application.zip
  6. Hello I have an application where when I push 'open' button on the main application screen, a window should pop up and when I click 'close' on the sub window it should close. I created and saved a VI for the sub window and when I try to add this VI to the main application block diagram by selecting the 'Select a VI...' from the right click menu bar, the icon does not show any terminals. I have gone through the 'Dialog Box Demo.vi' and 'Acquire-Analyze-Present.vi' examples which have similar pop up windows but the sub-vi icons look different and they have input and output terminals. I matched the file -> 'VI Properties' of my sub-vi exactly to the sub-vi's in the examples, but still no use. Please expalin what else am I missing here? Thank you, Vinay
  7. I have an industrial application involving NI Panel PC with a DAQ card as a replacement to a standard touch screen HMI. I would like to know is it possible to have multi screens (for eg: when you push a button named 'Setup' on the 'Main Screen', the 'Setup' screen should be opened) and security levels (for eg: an operator should not have access to changing some values while the maintenance personnel should have entire access) like in a standard HMI on this Panel PC using LabView8.5. Please note that I started using LabView less than 10 days ago. I somehow finished the actual core logic for my application by referencing to examples, but the above mentioned cosmetic stuff is what matters to the customer and it has to be operator friendly. Please advice.....
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.