Labview mobile & 3 graphs on multiscreens

[philcbr]

Hi All,

I have a problem that I can't solve and I hope some bright spark on the forum can lead me to a solution. I have 3 graphs to display (amplitude vs time) and when I use labview on the PC I can use tabs to select between the graphs with no problems. When I download it to the mobile emulator or the device (Windows Mobile 5) it doesn't like it and gives me errors.

I need these tabs as having 3 graphs in a row makes the resolution on the mobilephone screen unreadable.

I got these tab functions from the front panel -> Controls -> Classic -> Classic containers -> Tab control

The error message on the mobile reads "App failed. Error code 70878003. Unable to lock memory chunk", whatever that means

Is there a solution to this? (remembering I am quite new to Labview and inherited most of the code I am now working with!!)

Many thanks,

Phil

[Sriram_Iyer]

Hi Phil,

Have you installed LabVIEW Mobile Module on your computer? 

Regards,

Sriram N

[philcbr]

Yeah, got the latest version installed.

Update: I have got the tabs working (I honestly don't know what I did to make it work!) although it appears that I can only press one button, then I have to close the program and restart to press another button. Starting to wish I hadn't went down the Labview route for mobile designing!! 

[AEwing]

Thanks for the note on this problem.  I just got the same error.

Am working with LV8.6 and associated LV Mobile.

Am setting up a base template for future acquisition.  Started from the example from NI, which allows Landscape to Portrait switching.

Have been adding piece by piece and building/testing on actual WM 6 device (IPAQ 210). 

Created pair (portrait and landscape) of vi's with a tab control with 5 pages, and associated menu.  Works fine.

To one of the tabs, I experimented with another 3 page tab control, without showing the tabs themselves.  Works fine.

Then created a set of 5 small buttons, with intent to make them quick links to the second tabcontrol pages (bear in mind I'm just experimenting with UI approaches).  These button are not acted on (yet) but are active.  Builds OK.  But gives the same error you mention, on running.

That's interesting, as this is just an addition of buttons (albeit 5 each on two vi's, ie. portrait and landscape).

Will reply when I get more info.

Al

[AEwing]

Actually I was wrong above.  I had not tested after adding the nested tabcontrol.

I removed the buttons and still got the error (equiv. to test after nexted tabcontrol addition, prev. mentioned).

I peeled back the pages (to 1) on the nested tab control and still got the error.

I removed 1 tab control, but not the other (of the paired portrait and landscape vi's), and the error removed. works fine.

Somehow this must be related to the number of objects (or nested objects) or events from such, allowed on the mobile executable.

Would like to know what limit is being exceeded and how to change or avoid.  This app by comparison to actual mobile data acq. apps is not large nor seems to be burdening the device.

Al