GregG

QUOTE (PeterB @ Jan 12 2009, 04:24 PM)

I installed LV v8.6 PDS (under/with a VLA/VLM) and the first time I went to build my application I got the error. I don't have LVRT installed.

My local NI app'n engineer told me there is already an associated CAR# but will get it to me later.

Greg are you an NI employee ? What is your motivation for fixing the problem e.g. are you experiencing it too ?

regards

Peter

Yes, I am an NI employee, and I specifically work on the code related to nilvce.dll.

thanks for the reply,

greg

QUOTE (PeterB @ Jan 12 2009, 04:24 PM)

I installed LV v8.6 PDS (under/with a VLA/VLM) and the first time I went to build my application I got the error. I don't have LVRT installed.

My local NI app'n engineer told me there is already an associated CAR# but will get it to me later.

Greg are you an NI employee ? What is your motivation for fixing the problem e.g. are you experiencing it too ?

regards

Peter

Yes, I am an NI employee, and I specifically work on the code related to nilvce.dll.

thanks for the reply,

greg

QUOTE (gleichman @ Jan 11 2009, 08:32 PM)

I had the same error, but it was fatal for my build. Same solution as yours.

What were you using that required that dll? Some scan engine related VI? Did you have real-time installed? I'm trying to figure out how you got into this situation so that perhaps I can fix it.

thanks,

greg

What techniques have you learned for wrapping by value GOOP to get a by reference "feel"?

One technique I've seen in general for using "by reference" semantics is to use a single element LV queue. The basic idea is you create a queue of length one, and everytime you want to use the data, you dequeue it with an infinite timeout (so in case someone else is using the element you wait until it is your turn) and then once you are done with the object, you enqueue it again. Unfortunately, this approach does create a lot of clutter on your diagram everytime you access your object, and if you're dealing with multiple objects, you have to be careful not to deadlock.

There are functions in LV to stop individual VIs/application and a function in the LV RT utilities to restart a RT controller (shutdown/retsart), but short of pulling the power plug or controlling a robot to flip the power switch on the front of the PXI chassis you can not shutdown a RT controller to an OFF state programatically.

Strangely, there is only one clean way to fully shut down an RT box: do a software reboot, either from MAX or the LV project, or with the Reboot Controller VI that ships with RT. If you wait until the target gets to the BIOS screen and then turn it off before it boots RT, that is the cleanest way to shutdown, because RT will have given everything running on the target (such as drivers, etc) a chance to cleanly shutdown and cleanup whatever it is doing. The disk cache will be flushed, and things will be as clean as they can get.

I have a project that has about 1500 vis. Several of them are set up as reentrant.

When I double click on a reentrant SubVI from the block diagram LabView creates a clone vi.

The problem is that clone vis are not changeable.

So what is the quickest way to get to the clones source vi in a huge project so It can be change.

Here are the methods I know of.

• Open it via the project
  (trying to remember where it is and finding it can take a while)
  
• Open it via windows explorer
  (same as above)
  
• Open Vi Hierarchy of calling vi find SubVI and double click
  (Hierarchy can take a long time to open and doesn't work if calling vi is reentrant)
  
• Open clone Menu>>File>>VI Properties (Right clicking on icon doesn't work for clones).
  Go to execution category and uncheck Reentrant execution.
  After OK is pressed the clone FP will close.
  Now when the SubVI is re opened it is the source vi and not a clone.
  Go back and make Reentrant.
  (lots of clicks and its easy to forget to make reentrant)
  

Has any one found a quicker way to get to the source of a reentrant clone vi.

I believe you can get to the original from the clone by pressing Ctrl+M.