Thread: Native call
View Single Post
  #6   Spotlight this post!  
Unread 18-12-2010, 12:09
Greg McKaskle Greg McKaskle is offline
Registered User
FRC #2468 (Team NI & Appreciate)
 
Join Date: Apr 2008
Rookie Year: 2008
Location: Austin, TX
Posts: 4,751
Greg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond repute
Re: Native call

I added your ZomB Init.vi to the cRIO portion of the 2010 project and it was still broken wanting a library name. I entered ZomB.*, closed, and it showed that it was no longer broken. I built and it didn't indicate any errors. Unfortunately, I don't have a cRIO at home, so I can't test the fix much more than that.

Since I didn't receive your project, are these VIs being loaded using a project setup for the cRIO? If so, I believe you will be able to use the library name statically typed into the library, and the exe will link up on the cRIO the way you want. I noticed that some of the CLF nodes use the path and others don't. Again, I don't know all of the RT details, so I can't say exactly why the authors did it different ways.

Make sure that your VIs are in the cRIO section of the project and that they list the cRIO context in the lower right of the window, put the ZomB.* in the dialog as the library name/path. Let me know how that works.

Greg McKaskle
Reply With Quote