Tab Control Property Node gives a build error when used in a VI for LabVIEW PDA

Hello,
Iam new to LabVIEW development & need help regarding this:
We are trying to port a LabVIEW application from desktop to a Windows Mobile PDA. Please note that the LabVIEW application works fine on the desktop. In one of the VIs, a Tab control property node is used which gives a build error with LabVIEW PDA project. A sample VI which shows the problem & the error list snapshot is attached with this post. Can anyone please suggest an alternate approach to achieve the same functionality with LabVIEW PDA? Waiting for an early response from anyone...
Thanks & Regards,
Subhashini
Attachments:
VI_Error.zip ‏31 KB

Hello Ton,
    Am glad that i got a response, thanks. The following links indicate that Tab control is supported on PDA target:
http://digital.ni.com/public.nsf/allkb/CBA335641E27B858862571490015EA88?OpenDocument
http://forums.ni.com/ni/board/message?board.id=170&message.id=221507&requireLogin=False
    I feel that the Tab control property node that has been used in the VI (which is attached earlier) may not be supported on the PDA target. Can u (or any LabVIEW expert) suggest an alternate approach to achieve the same goal with LabVIEW PDA (changing colour of Tab control pages programatically)??
    I had missed out some details earlier: We are using LabVIEW 8.5 PDA module on a Windows Mobile PDA.
Thanks & Regards,
Subhashini

Similar Messages

PDA build error when using a 'value change' event on two controls

I get a build error when I use a 'value change' event on controls of a different type or even a different numeric representation. I'm using LV 7.1 PDA with no other modules installed. Attached is a picture of the entire code and the error message.
Try to take over the world!
Attachments:
PDA Error.jpg ‏48 KB

Hi,
I verified the error that you are seeing. It appears to be a bug hence I have reported it to our developers. Hopefully this bug would be fixed in the next relaese of the PDA module.
Thank you for pointing this to us. It is through feedback that we can make LabVIEW PDA module even better.
Regards,
Ankita A.
National Instruments

Tab Control Property Node unknown error on TPC

I am using Lab View 8.6. I am programming an HMI onto a TPC 2106. I am using a Tab Control and it workls fine. The problem is when I add a property node for the tab control to the block diagram. I get an unknown error no matter which property I choose or if it is read or write. I tried it on a vi destined for the computer and it works fine. It seems to be an issue with the TPC 2106 as the destination.

Hi vrundquist,
When compiling a VI for a TPC, there are many properties of controls and indicators that will not be supported. Which properties specifically have you tried? I want to be sure you are choosing a property that should be OK. For example, try the Visible property. Also, is there anything else going on in your code, or can you reproduce this with a VI that has nothing but a tab control?
Regards,
Brian A.
National Instruments
Applications Engineer

Build error when using custom error codes

When I try to build my application using custom error codes I receive the following error:
Error 1 occurred at Copy in AB_Engine_Copy_Error_Files.vi->AB_Application.lvclass:Copy_Error_Files.vi->AB_Application.lvclass:Copy_Files.vi->AB_Build.lvclass:Build.vi->AB_EXE.lvclass:Build.vi->AB_Engine_Build.vi->AB_Build_Invoke.vi->AB_Build_Invoke.vi.ProxyCaller
Possible reason(s):
LabVIEW: An input parameter is invalid. For example if the input is a path, the path might contain a character not allowed by the OS such as ? or @.
=========================
NI-488: Command requires GPIB Controller to be Controller-In-Charge.
C:\Program Files\National Instruments\LabVIEW 8.5\user.lib\errors\BPMS-errors.txt
This only occurs the first time I attempt to build my application. If I build again immediately after receiving the error, everything works fine. My custom error codes were created using the provided editor, and I have included the file in my project. I have also checked the "Copy error codes" box in the advanced build specification settings.

Hi Donovan,
The attached project is giving me the error previously discussed. Thanks for your help.
Attachments:
BuildError.zip ‏10 KB

Error when using SAP Exit Variable for Current Fiscal Period (0FPER)

Hi Friendz,
My requirement is to execute a query for the current fiscal period. I am using the SAP Exit Variable 0FPER.
I placed this variable on char. Fiscal year/period 0FISCPER.
When I execute the Query, it is returning the error: No value could be determined for variable ZVBSYCUR; Variables Contain Invalid Values.
Please give inputs on how to use this variable.
Regards...
Ganesh

Hello Dipika,
I am also getting the same error.
ERROR: Variable 0FPER could not be replaced.
Yesterday we created one customer exit. But this should not affect the SAP Exit right? Till yesterday the 0FPER variable was working fine. I tried re-installing from BI content, but still getting the same error. If anybody has a clue please let me know.
Thanks,
Harshal

Why does the Summary function give a datatype error when opening a data model for editing?

I have two datasets (G1 and G2) within a data model; i've used a field in G2 and placed it into G1 as a Summary Function of G2. The datatype of this field in G2 is Integer, however if you set the Summary field in G1 to the same datatype - Integer, an error appears.

Oracle have provided a patch.
We are running OBIEE at patchset 11.1.1.7.140715, Oracle have provided us with a patch p17563277 backported to the 140715 patchset.
This fix will presumably be incorporated in later releases.

Error when using sort variant 0005 for RABEWG01 (tcode za353)

Hi SAP experts,
I have a problem with program RABEWG01 (tcode za353). When I use sort variant 0005 and execute it, I get this error:
Table ANLV is not supported in the requested report
Message no. AB066
Diagnosis
You requested sort version 0005 for the current report. The sort version contains a field in table ANLV. However, the report does not process this table. Therefore the sort version cannot access this table and this field.
System Response
The report is not executed with sort version 0005.
Procedure
Enter a sort version that uses only valid tables. The following tables are supported in the current report:
ANLAV ANLB
Can someone help me to explain why ANLV is not supported in the requested report? If we can't use sort variant 0005, why is it there in the first place?
==========================================
Field:
Company code: 001
Report date: 30.03.2011
Dep area: 01
do I need to add any more entries in the field so that i can use sort variant 0005? thanks!

Hi,
note 21719 explains the reason for he error:
" Fields from tables ANLP and ANLV can only be used in a sort version if
the same tables are used in the relevant report (currently only the case
with reports RAGAFA01 and RAVERS01). If these fields are used in other
reports, runtime error GET_WA_NOT_ASSIGNED could occur..."
regards Bernhard

Errors when using the Call statement for MS SQL Server

I've tried executing a Stored Procedure using the Call method of Portal 2 Go. But it gets an internal error b/c of it. Any Ideas why and how to resolve?

Hello,
Which version of SAP BOBJ XI3.1 you are using?
What I am aware is BEGIN_SQL was very well working for SQLServer2005 in case of ODBC connection.
Can you try one thing for SQLServer2008 have a Native driver installed on your client machine and use ODBC connection rather than OLEDB connection.
If that works fine, its good
Otherwise you can raise a message for resolving this problem with the support team.
Thanks,
Vivek

#1009 Flash error when using the hideclosebox widget for Slidelets

Hi,
I have slidelets in my project (CP 6) and have included the widget "hideslideletclosebox" I found here on this forum. From
Chris Dorma e-Learning. I am receiving errors and they are different per user, depending on their flash version. Most are #1009 errors. They all relate the to the widgetbox having a run time error.
Thoughts?
Gillian

Most likely Chris's widget is not compatible with Captivate 6. Go to his website (http://www.dorna.nl/) and check if there is an update for your widget.
BTW: Chris is not very happy with Adobe at the moment...

Property Node in VI throws Error 7 in LV 7.1 but runs OK in LV80 and LV86

Hi everybody
I build a custom IVI instrument driver and using the LV tool <Generate VI Interface from Instrumnet CVI Driver> I was able to get a LV wrapper for each driver method. From LV86 I saved first in LV80 and from LV80 I saved as LV71. I have all these LV versions on installed on my PC.
I have no trouble in using these LV wrappers in any of these LV versions as they work OK.
Now my IVI driver has also Properties that the Import Driver Tool does not convert as a wrapper and for that reason I had to create a Property Node Warpper myself and saved in the same LLB under LV/instr.lib folder.
Once I have all these method wrappers and the property node wrappers I made a small VI
1. Initialize IVI With Options on a TCPIP instrument
2. Set-Get an IVI Timeout property
3 Close IVI driver on TCPIP instrument.
Good part is that in LV 86 and in LV 80 the VI is running fine when I use these LV version wrappers from their coresponding instr.lib folder.
As soon as I am going to use the LV 71 wrappers in LV 71 I could create the same small VI to Set/Get Timeout and the VI look OK nothing is broken but when I run it the Initialization is OK but as soon as is reaching the Timeout Set Property Node gets out an Error Code 7.
To run this VI the user need to install the jdCMR IVI driver then add the LV71 jdCMR wrappers inside LV71/instr.lib and then he may build any VI using these LV warppers.
The only problem is that the Property Node get out an Error Code 7 and the same error code get out from Property Node if I am picking the Property Node from VISA Advanced Pallette, connect this node to jdCMR driver, set Timeout property inside the node and after connecting the input and output references plus the input and output error to Initialize and Close LV wrappers I still get this error at running time.
The same LV 71 VI if I open in LV80 or in LV 86 runs without any problem?
Does anybody knows why LV 71 is not working the same way as LV80 and LV86 with respect to Property Node?
Btw When I save my VI from LV 80 to LV 71 I get this warning...
IVI Error Message Builder.vi
    Cannot save VI from VI.LIB to previous version.
Merge Errors.vi
    Cannot save VI from VI.LIB to previous version.
Thanks
Sorin

Hi
For further testing of the IVI driver Property Node bug with LabVIEW 7.1 IVI drivers I download and installed two different IVI drivers from two very known instrument companies, Rodhe-Schwarz and Agilent Technologies.
I have to mention that both these companies releasead their IVI NI LabVIEW 7.1 drivers under NI Instrument Driver Network and ready to be installed and used by any customer of these two instruments.
The bug is present only in LabVIEW 7.1 version as if I take the same VI that breaks in LabVIEW 7.1 I could run it without any problem in LabVIEW 8.0 or LabVIEW 8.6 versions.
Anybody could test this bug for these two NI released IVI drivers in simulation in LabVIEW 7.1 by following these links below.
Agilent ag81150ni IVI Driver for LabVIEW 7.1 install from here. Run in simulation only by setting Simulate=1
http://sine.ni.com/apps/utf8/niid_web_display.download_page?p_id_guid=55798957B1A633BDE0440003BA7CCD...
   Rodhe Schwarz rsngpt IVI Driver for LabVIEW 7.1 install from here. Run in simulation only by setting Simulate=1
http://sine.ni.com/apps/utf8/niid_web_display.download_page?p_id_guid=E3B19B3E91D6659CE034080020E748...
After installation complete close LabVIEW 7.1 if was open, then restart LabVIEW 7.1 and now you may see under the LabVIEW Instrument Driver Palette two new IVI drivers ready to be used as LabVIEW 7.1 wrappers.
Open a new blank VI and from Instrument Driver Palette use two well known Vis that are Initialize With Options.vi and Close.vi add them on your blank VI block diagram and connect thm together. Accept all default parameters except Simulate that must be Simulate=1.
Both Vis run OK in simulation mode without errors. Now pick a Property Node from VISA Advanced Panel and squeeze this between the Initialize With Options VI and Close VI and make the instrument reference in-out and error in-out connections.
Now run these two simple Vis in simulation
I run Rodhe Schwarz IVI driver and Property Node passes OK until the end
I run Agilent IVI driver but Property Node is getting out Error Code 7 that is the same as my own driver error.
Both these IVI drivers are under NI Instrument Driver Networks and have been built and integrated as native NI IVI instrument drivers.
Question is why they behave so different with respect to Property Node from the VISA Advanced Panel?
I attached the screen shots as PNG files that show clearly the difference of VISA Property Node behaviour when used under the same circumstances.
Thanks  Sorin
Attachments:
ScreenTestShots.zip ‏152 KB

LV 6.0.2: an App-built dll gives a runtime error when called by C

I want to use Labview 6.0.2 VIs as DLL's in a Borland C++ Project.
Starting with the simple I have made a VI that returns a constant int32 then built a dll with the Application Builder and put the dll and include file in a BC++ project directory. Compile and link seems to run well. But when excuting the call to the LV fuction gives Fatal Error: labview.lib was not called from a Labview process.
It seems this question was posted before, but answer didn't help me, Sorry.
7.1 -- 2013
CLA

Hi Gabriela -
This question is answered in the KB article entitled : "LabVIEW.LIB Error When Calling a DLL Built with LabVIEW"
The link for this document is -> http://ae.natinst.com/operations/ae/public.nsf/fca7838c4500dc10862567a100753500/a4c3aef93240280a86256931006fb66c?OpenDocument
Or you can go directly to www.ni.com/support and search for this document and others to help.
The reason for this is that the old labview.lib does not know how to correctly locate the LabVIEW Run-Time Engine when called.
From the document I posted ->
Your dll is most likely making a call If you want to call a Windows DLL or CIN built with a version of cintools before LabVIEW 6.0, you must relink the DLL with the labview.lib from 6.0. If you call an old DLL or CIN in your LabVIE
W DLL, you receive the aforementioned error and the application terminates, because the old labview.lib does not know how to correctly locate the LabVIEW Run-Time Engine when called in this situation.
Good luck-
ben schulte
national instruments

LabVIEW PDA reports COREDLL.DLL error when using Call Library Function Node

I'm trying to build a LV PDA app that calls an external DLL file built using embedded visual C. When configuring the Call Library Function node I select the stub DLL, configure the I/O parameters and select OK. When the configuration dialog closes I get the following error:
LabVIEW: LabVIEW.exe - Unable to Locate Component
This application has failed to start because COREDLL.DLL was not found. Re-installing the application may fix this problem.
I do not get this error when using the configuration dialog in the example VIs.
Any suggestions as to the cause and/or the solution?
Thanks,
Ryan

Hello -
When you create a PDA VI that calls a DLL, you must include the .c or .lib file that corresponds to the DLL. Take a look at these documents:
LabVIEW PDA Module Build Errors with VIs that Call DLLs
Why Do I Receive Errors When Calling a C++ DLL from a Call Library Node Using the LabVIEW PDA Module...
How To Call External Code in LabVIEW PDA for Palm OS
H
ow To Call External Code in LabVIEW PDA for Pocket PC
Hope this helps!
S Vences
Applications Engineer
National Instruments

Error message when building an application for Labview PDA

When using LabView PDA module to build an application for a PDA target, I receive the following message: "Error building executable. Unable to create file". Why is this happening?
When looking at the error log, it reads "The system cannot find the file specified."
This happens even when looking at one of the Labview PDA example VI's, so it is not a result of the VI containing functions of features not supported by Labview PDA.
When installing Labview PDA, I installed files as follows, and in this order:
(i) Labview 7.1 (installed previously)
(ii) Microsoft eMbedded Visual C++ 4.0
(iii) Microsoft eMbedded Visual C++ 4.0 SP 3.0
(iv) Microsoft SDK for Windows Mobile 2003-based Pocket PCs
(v) Microsoft ActiveSync 3.8
(vi) NI Labview 7.1 PDA module for PocketPC
(vii) DAQmx Base 1.0 for PDA or later
Any ideas?

Did you attempt to add the _wordsub.llb and _excelsub.llb files to the application as support files? I believe in LabVIEW 8.0 instead of adding the entire LLBs you should just add the _Word Dynamic VIs.vi and _Excel Dynamic VIs.vi as dynamic VIs. I think I've seen a similar post on the discussion forums in the past that recommended this.
If this suggestion doesn't help, please reply, and attach a simple VI and .lvproj file demonstrating the problem so I can investigate further.
Good luck,
-D
Darren Nattinger, CLA
LabVIEW Artisan and Nugget Penman

Oracle warehouse builder error when I execute any mapping

oracle warehouse builder error when I execute any mapping:
I have installed OWB successfuly, It still no longer working correctly: it executed all the mappings, but it suddenly becomes incapable to execute any mappings in any project. It validates successfuly the mappings but in the execution it show the message :
" ora-06550 : ligne1 colonne19..."
please help me to correct this error.
thank you.

Make sure that there is no primary key or index on this table who exceed the limit.
For more information see
http://download-west.oracle.com/docs/cd/B10501_01/appdev.920/a96612/d_wm2.htm#105677

Getting the below error when running the Baseline.grf for the first time

I am getting the below error when running the Baseline.grf for the first time.
Appreciate your support in resolving it.
Error below:
INFO [main] - *** CloverETL framework/transformation graph, (c) 2002-2012 Javlin a.s, released under GNU Lesser General Public License ***
INFO [main] - Running with CloverETL library version 3.2.1 build#63 compiled 04/01/2012 12:53:21
INFO [main] - Running on 4 CPU(s), OS Windows 7, architecture amd64, Java version 1.6.0_20, max available memory for JVM 901120 KB
INFO [main] - Loading default properties from: defaultProperties
INFO [main] - Graph definition file: graph/Baseline.grf
INFO [main] - Graph revision: 1.114 Modified by: mkressirer Modified: Thu Apr 12 13:27:18 EDT 2012
INFO [main] - Checking graph configuration...
INFO [main] - Graph configuration is valid.
INFO [main] - Graph initialization (Baseline)
INFO [main] - [Clover] Initializing phase: 0
INFO [main] - [Clover] phase: 0 initialized successfully.
INFO [main] - register MBean with name:org.jetel.graph.runtime:type=CLOVERJMX_1306871483270_0
INFO [WatchDog] - Starting up all nodes in phase [0]
INFO [WatchDog] - Successfully started all nodes in phase!
INFO [RUN_GRAPH1_0] - Running graph ./graph/InitDataStore.grf in the same instance.
INFO [RUN_GRAPH1_0] - Checking graph configuration...
INFO [RUN_GRAPH1_0] - Graph configuration is valid.
INFO [RUN_GRAPH1_0] - Graph initialization (InitDataStore)
INFO [RUN_GRAPH1_0] - [Clover] Initializing phase: 0
WARN [RUN_GRAPH1_0] - WS messenger cleanup failed.
java.lang.NullPointerException
     at org.apache.axis2.client.Stub.cleanup(Stub.java:134)
     at com.opensys.cloveretl.component.WebServiceClient.free(Unknown Source)
     at org.jetel.graph.Phase.free(Phase.java:487)
     at org.jetel.graph.TransformationGraph.freeResources(TransformationGraph.java:681)
     at org.jetel.graph.TransformationGraph.free(TransformationGraph.java:955)
     at org.jetel.graph.runtime.PrimitiveAuthorityProxy.executeGraph(PrimitiveAuthorityProxy.java:149)
     at org.jetel.component.RunGraph.runGraphThisInstance(RunGraph.java:511)
     at org.jetel.component.RunGraph.runSingleGraph(RunGraph.java:409)
     at org.jetel.component.RunGraph.execute(RunGraph.java:302)
     at org.jetel.graph.Node.run(Node.java:414)
     at java.lang.Thread.run(Thread.java:619)
WARN [RUN_GRAPH1_0] - Some graphs wasn't executed (because graph "./graph/InitDataStore.grf" finished with error).
WARN [RUN_GRAPH1_0] - Some graph(s) finished with error.
ERROR [WatchDog] - Graph execution finished with error
ERROR [WatchDog] - Node RUN_GRAPH1 finished with status: ERROR caused by: Graph './graph/InitDataStore.grf' failed!
ERROR [WatchDog] - Node RUN_GRAPH1 error details:
org.jetel.exception.JetelException: Graph './graph/InitDataStore.grf' failed!
     at org.jetel.component.RunGraph.execute(RunGraph.java:324)
     at org.jetel.graph.Node.run(Node.java:414)
     at java.lang.Thread.run(Thread.java:619)
INFO [WatchDog] - [Clover] Post-execute phase finalization: 0
INFO [WatchDog] - [Clover] phase: 0 post-execute finalization successfully.
INFO [WatchDog] - Execution of phase [0] finished with error - elapsed time(sec): 2
ERROR [WatchDog] - !!! Phase finished with error - stopping graph run !!!
INFO [WatchDog] - -----------------------** Summary of Phases execution **---------------------
INFO [WatchDog] - Phase# Finished Status RunTime(sec) MemoryAllocation(KB)
INFO [WatchDog] - 0 ERROR 2 20132
INFO [WatchDog] - ------------------------------** End of Summary **---------------------------
WARN [exNode_0_1306871483270_RUN_GRAPH1] - Attempt to unregister non-registered thread in the ContextProvider.
./graph/InitDataStore.grf: Execution of graph failed! Error during graph initialization: Phase 0 can't be initilized.
INFO [WatchDog] - WatchDog thread finished - total execution time: 2 (sec)
INFO [main] - Freeing graph resources.
ERROR [main] - Execution of graph failed !

It can't find an Endeca specific class when running via the clover command line utility. Thus, the classpath being set in that shell script is not incorporating the .jar files where the endeca-specific classes are packaged. I would start by adding an line to see what your classpath is set to. There are actually already some lines of shell script in clover that you can uncomment to see what .jars are getting loaded:
#echo $CLOVER_LIB/*
for i in $CLOVER_LIB/*.jar $CLOVER_LIB/*.zip; do
     LOCAL_CLASSPATH="$LOCAL_CLASSPATH:$i"
done;
#for i in `ls $CLOVER_LIB/*.jar`; do
#echo $i
#done;
You could also echo LOCAL_CLASSPATH to see what is getting set there. At the end of the day, you will need the endeca-specific jars to load which can be found here: /Endeca/Discovery/2.3.0/Integrator/plugins/com.endeca.latitude_1.0.0/*
HTH,
Dan
http://branchbird.com

Tab Control Property Node gives a build error when used in a VI for LabVIEW PDA

Similar Messages

Maybe you are looking for