Example vi with no Code - Only controls

[K_seeker]

Hi

I received my ARM evaluation toolkit and I am very excited about this technology.

After going through Quick startup lessons I wanted to run some example projects that came with the toolkit. To my amazement I the driver VIs I opened from the project file were empty. I could only see controls placed on the block diagram. I have attached an screen shot for your review. I looked into couple of different project files and found out that basically all the dependent sub vis had the main code missing. Only the control and indicator icons were present.

In short every vi in the following folder is the same way - Front panel present but no real code in the background, only icons

D:\Program Files\National Instruments\LabVIEW 8.5\vi.lib\Embedded\ARM\MCB2300\

I am little confused. I initially thought I had a corrupted install. So I repeated the installation and I still see the same thing. Can some one shine some light on it please.

Thanks in advance.

[K_seeker]

Here is the screen shot I mentioned in the post.

[Jaidev]

Hi K_seeker,

This is not unexpected. Let me explain why:

For VIs that control hardware and board related functionality, we dont need any LabVIEW logic. All we need to know if what LED (or IO). Using this input, the C Code generator can create code for executing that action. So you will find many such VIs in the embedded module, the code for these VIs is generated under the covers. 

Thanks You,

Jaidev

National Instruments 

[K_seeker]

Thanks Jaidev. I realized this yeaterday when I decided to download the program anyway. To my amazement the program ran as mentioned in the help file. Later when I dug deeper into documents for embedded LabVIEW I realized this behaviour of embedded LabVIEW environment.

I am new with this and really excited about this technology. Thanks again.

[StuB]

Hi Jaidev,

OK, I'd figured out that LabVIEW Embedded knows how to find the related driver C code, but how do I adapt that behavior for porting to a related platform? For instance, the "EKLM3S8962 Display Init.vi" obviously knows to find the "EKLM3S8962_Display_Init(long lErrIn, long *plErrOut)" function inside the "EKLM3S8962_Display.c" driver source code file.

I'm assuming that  any display driver C code for a non-Tier-1 board will not be LabVIEW specific, so after I fix that, using the example above as a reference, how do I make the connection to the related VI? Is it as simple as overlapping the names of the source file and function, and swapping underscores for spaces, or is there more to it than that? I have skimmed the documentation for porting to a non-Tier-1 target, and don't recall anything specifically addressing this.

Thanks,

StuB 

[Jaidev]

Hi StuB,

An easier way to implement IO for your non-tier 1 board is to create your own driver code in C and then use an inline C noce to invoke it in your VI. Once you have that down, you can wrap it in an Elemental IO node and we have detailed instructions for it here:

http://zone.ni.com/devzone/cda/tut/p/id/7119

Thanks,

Jaidev