LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

LRESULT missing error

I'm new to the PDA Module.  I keep getting "return is missing..." and "LRESULT is missing..." error messages when I go to compile and run my LV 8.5 app on a Pocket PC 2003 device.
 
The shipping examples, like the Calculator one, work just fine.
 
Any advice?
 
Rich
0 Kudos
Message 1 of 6
(3,527 Views)

Hi Rich,

Since you are able to successfully deploy the example, my first inclination is that there is something within the LabVIEW code that is not supported on the PDA; hence, it gives you an error when you compile it. This problem is often a result of editing the VI while targeted to Windows. When editing a VI that is intended to be built into a PDA application using the LabVIEW PDA module, it is helpful if you switch to that execution target prior to making any changes to the VI. Changing to that execution target changes the palettes so that only items supported for that context are available. This will prevent you from using a function that is not supported which may cause an error when attempting to build for PDA. Can you post a screenshot of the actual error and then also maybe a screenshot of your block diagram? That would help us determine if there is something that we could change to make it work. Thanks!

 

Carla

 

National Instruments
Applications Engineer
Message 2 of 6
(3,507 Views)

I've found the problem.  It was with the formula node I was using.

Not sure if the compile error was caused by a specific "PDA incompatible" expression within the formula node or formula nodes in general.  My solution was to replace it with LabVIEW math operators.

Rich

 

0 Kudos
Message 3 of 6
(3,499 Views)

I am having this same error, along with uint8, dVal, initializing, int, and return all as missing VI or C files. I also had a formula node that I got rid of, but I'm still having the same error. Is there any way now that my VI is created to do some sort of compatibility check to find out what if any incompatible items I have in my VI?

 

Thanks!

0 Kudos
Message 4 of 6
(3,332 Views)

Ajpodge,

 

As Carla suggested, when you target a PDA, the functions palette will change according to what functions are supported.  After targeting your PDA, go through the palettes and make sure that everything you are using is also on the palette.  I can't think of a programatic way to do this, but I would recommend taking a look at the mobile module help files, it gives a nice list of limitations of mobile devices.
Rob K
Measurements Mechanical Engineer (C-Series, USB X-Series)
National Instruments
CompactRIO Developers Guide
CompactRIO Out of the Box Video
Message 5 of 6
(3,303 Views)

Hi Rob,

 

Thanks for the answer. I figured it out, but just by sheer luck--I printed out the block diagram for the VI and made a brand new one FROM SCRATCH bit by bit until I got the error again.  Clearly, it would be very nice if this could be fixed in a future version of LabView.

 

The problem was a slider. I added it when I was working with the correct target, and of course it was still available in the palette once I switched back to the PDA target. Moreover, the reason that the slider wasn't working was because I added a second slider (I am using the slider as an indicator).

 

***Even when I am working on the VI with the PDA target correctly chosen, it still gives me the option to add a second slider, even though this is not compatible with LabView PDA.***

 

Hopefully this post helps someone else in the future with their PDA application!

 

Ajit 

0 Kudos
Message 6 of 6
(3,290 Views)