Labview Exe acts different than Vi

Hey everyone,
I recognized a strange behavior while Testing an old application i build some timne ago.
The LV Project ist build up with .NET Objects as Models and Calculationroutines. Everthing runs fine in the LabView IDE. Calculation and Models are running well.
When I compile this Project with the LV Builder, it starts fine. But i do recognize some strange thing.
In .net I have defined a Class A like:
class A
function_one( x,y,z)
function_two(c,a)
Where x,y,z,c,a are all numerics.
And now it comes. As i mentioned in the Vi (LV IDE) everthing works fine.
The call of function_one() and funktion_two() works perfect. In the Exe-Application function_one() works, but functuion_two is not even called, as I debugg the exe-App with Visual Studio.
So whats the deal here `??? Why does funtion_two not work??? not even called?
Solved!
Go to Solution.

Thanks for the fast reply.
@altenbach:
As the complete Modell is a complex agregation of different objects, it's not able to prepare in short time an example. But there are some screenshots of code and results.(see attachment)
@Hooovahh:
I prepared the client runnigmachine as described in http://digital.ni.com/public.nsf/allkb/8DA679805915DE40862572D5007B2F70
Starting Debugging on developer enginge results in a crash of the debugging LV IDE on the developer engine. And the the Clients still does everthing else shown in the main Vi. Everting except for the function_a of course ;|
The .Net Elements are used in different simulations like the one described here. I didbt see such behavior befor or in other following applikations.
Screenshots:

Similar Messages

ODI Execute Button Acting Different than Right-Click - Execute in Diagram

We have noticed that clicking the 'Green Arrow' Execute button in ODI to begin the Execution using First Step with only one Procedure is acting differently than simply right-clicking and selecting 'Execute' within the Diagram tab. We have noticed this issue with only a SQL Procedure.
In other words, when clicking the 'Green Arrow', ODI compiles the package together before executing which seems to make the procedure execute differently than right-clicking and executing the procedure individually.
Has anyone else noticed this issue?

Executing with Green arrow means the entire package would be compiled and executed. In such case if you have any special configuration for that step then that would be effective and thus might show different behavior.
Running a particular step by right clicking on it would be equivalent to running the procedure or interface directly.
Do you see difference in behavior if you run the procedure directly v/s running it within package too?

Is Labview Bitmap format different than Windows?

I have an issue with my bitmap images (depth bit of 1) saved with LabView and a brady printer I'm sending them too with a Serial VISA.
I have a VI to create a barcode image and save it as a bitmap. I'm just using the simple graphics Write BMP File VI after a Picture to Pixmap VI. The file looks just fine if opened in MS Paint. Yet when I send it to the printer as a file, it's all garbage.
If I use the same VI to save the bitmap (depth bit of 4) then open it with MS Paint, then save it as depth bit of 1. I use the same print VI as before, the file prints beautifully.
If I open the bitmap created by my VI (depth bit 1) and the equal on saved by MS Paint in Notepad I see they are not the same.
Admittedly I don't know a lot about file structure so probably don't know that I'm doing but any friendly advice would be appreciated. I'll attach the files with a .txt extension so that I can post them.
Attachments:
LabView and Paint Bitmaps.zip ‏1 KB

I see a couple differences in the files.
The LV bitmap is almost twice as large as the MS Paint bitmap. Opening them up in Notepad, the crazy characters look different. The LV bitmap has a long line of spaces at the end of the file, probably why the file is longer.
I opened both images in LV using the Read Bitmap File and looked at the image cluster. Both have the same number of pixels (1872) and both have 2 image colors and an image depth of 1. However for the colors, LV has color 0 as 1677721 and color 1 as 0. MS paint bitmap is the reverse. LV pixel 0 is 0 and MS Paint pixel 0 is 255. (Possibly explained by the different order in the colors?)
The 2 images look a lot alike in a LabVIEW picture control and in Paint, but the MS paint bitmap has more black pixels making up the characters as compared to the LV bitmap.
Why the 2 files are inherently different, I don't know. But perhaps those differences explain why the printer is treating them differently.

Selection tool acting differently than expected, what did I press?

I must have selected a preference inadvertently, because I'm getting some different behavior from the selection tool. When selecting a box, for example, I get two sets of handles instead of one, and this makes resizing and snapping to where you want it to go want almost impossible.
I've attaced an image. Can anyone provide some guidance?
Thanks!

You toggled "use preview bounds" on, which will include the stroke in the size of an object. Look in the flyout menu of your align panel for the toggle to turn it back off.

Forms on 10g act different than on 9i

Hello.
We installed database 10g and imported (full) database 9i.
We also installed new AS (same version as with 9i) - so difference is only with database version and ip numbers.
Now we have problems with RLS - role level security - so it seems. RLS worked great in 9i, but now it doesn't.
Users can't update their records from forms, but can update them in database through sqldeveloper.
When user wants to change some field, new entry just shows for a moment and then deletes. So user can't even write new data into forms field.
When we disable RLS everything works.
We use sys_context in RLS. Could there be a problem with sys_context becuse of new AS?
Any idea?
Thanks.

hi
I have read oracle 9i. written by ivan bayross..
but i don't know about the connectivity with database.
just know some creation table and ulter data.
Polywrapping

How do I troubleshoot installation/distribution of a LabVIEW .exe which processes data using Matlab when it works on some computers but not others?

I've been given the unenviable task of troubleshooting and installing/distributing software written by a former co-worker. I've modified the LabVIEW code and built an .exe file. I've successfully installed the Labview .exe file on several computers, but it won't work on some others. What's more baffling is that I installed it successfully on one computer, uninstalled it, and tried reinstalling it with no success. In fact, it's a new error (Dr. Watson for Windows NT application error). It doesn't help that I have different versions of LabVIEW and Matlab on the target computers. Some have LabVIEW 5.1, some
have 5.0, and some don't have it at all. Some have Matlab 5.2, some have 5.3 (R11) and some have 6.0 (R12). It's also not clear to me where the Matlab m files should be located. I'm not sure if it's a LabVIEW Runtime Engine problem, or if it's a Matlab problem. I've also wondered how LabVIEW and Matlab talk to each other. When LabVIEW calls Matlab, it seems that Matlab is running in the background. In other words, clicking on the Matlab Command Window and typing "whos" or any other command/variable doesn't work.

Jay del Rosario wrote:
>
> How do I troubleshoot installation/distribution of a LabVIEW .exe
> which processes data using Matlab when it works on some computers but
> not others?
Poke around zone.ni.com and
http://digital.natinst.com/public.nsf/$$Search/ .
Good luck, Mark

How to send a command from a vc++.exe to LABVIEW.exe in order to control the button on the LABVIEW.exe

Hello, everyone. Using VC++, I have gotten the handle of a *.exe(built by Labview), but I cannot get the button handle. I want to get the button handle and post the message to control the button. How can I do that? When I use the SPY++, the *.exe(built by Labview) have not any child windows which is very different from the *.exe(built by VC++). In SPY++, what is the LVDChild class? How can I send the message to control the button on *.exe(built by Labview)???
That is to send a command from a vc++.exe to LABVIEW.exe in order to control the button on the LABVIEW.exe. How can I get it ?
Thank you!

hummingbird wrote:
Thank you! But I dont kown how to use vi server to raise a value signalling event. Can we put vi server into the vc program? Can you give me some more information or some examples, hehe!
hummingbird
Checkout the LabVIEW ActiveX server interface in the User Manual in Chapter 20, Windows Connectivity and the VI Server Reference in Chapter 17, Programmatically Controlling VIs.
There is a sample for Visual Basic under examples/comm/VBtoLV.frm, which should be quite simple to translate to Visual C as long as you can figure out the basics of ActiveX programming in VC (I have never done anything with ActiveX in VC). For those basics I would recommend some text book or MSDN.
Rolf Kalbermatter
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

FPGA: compilation error: size of concat operation is different than size of the target

Today I got an error, for which I couldn't find a solution.
I use the PXI-7813R FPGA, with Xilinx tools 10.1
At compilation, the error I get is:
Compilation failed due to a Xilinx error.
Details:
ERROR:HDLParsers:804 - "C:/NIFPGA/jobs/TESY1S8_X4PR8hn/NiFpgaAG_000000ce_CaseStructureFrame_0000.vhd" Line 301. Size of concat operation is different than size of the target.
ERROR:HDLParsers:804 - "C:/NIFPGA/jobs/TESY1S8_X4PR8hn/NiFpgaAG_000000ce_CaseStructureFrame_0000.vhd" Line 372. Size of concat operation is different than size of the target.
-->
Total memory usage is 185944 kilobytes
Number of errors : 2 ( 0 filtered)
Number of warnings : 0 ( 0 filtered)
Number of infos : 0 ( 0 filtered)
Process "Synthesis" failed
Start Time: 18:25:26
End Time: 18:28:54
Total Time: 00:03:27
What can cause a concat size difference?

This is by the way the configuration:
Project: FPGAWrapperMG100125AOD.lvproj
Target: FPGA Target (RIO0, PXI-7813R)
Build Specification: fpga_integrator_AOD_random_access
Top level VI: fpga_integrator_AOD_random_access.vi
Compiling on LabVIEW FPGA Compile Cloud Service
Compilation Tool: Xilinx 10.1
Start Time: 05.07.2011 19:06:12
Run when loaded to Fpga: FALSE
Xilinx Options
Design Strategy: Custom
Synthesis Optimization Goal: Area
Synthesis Optimization Effort: Normal
Map Overall Effort Level: Default Xilinx setting
Place and Route Overall Effort Level: High
JobId: FNW72uPWorking Directory: C:\NIFPGA\compilation\FPGAWrapperMG100_FPGATarget_fpgaintegratorAO_9D5B4237
The Xilinx log is attached.
Attachments:
XilinxLog.txt ‏80 KB

Is there a way I can save switch settings so when I reopen a Labview exe it remembers how I set my switches?

We are using Labview to create a exe file. However when a user reopens the exe all the user settings in the labview exe are lost. These settings are mostly switches either turned on or off. I would like to find a way so that once the switches are set each time you reopen the exe file the switches are as you left them set.
I am very new to Labview so any help would be very much appreciated.

I think your best bet is go to the File I/O>Configuration File VIs and create an .ini file. When you program starts, it would read the file and set the controls using local variables. Then, prior to exiting, get the control values and write them to the file. You could even read and write different files - allowing for a whole lot of different configurations to be saved. In the shipping examples, go to Fundamentals>File Input and Output>Read Configuration Settings File.vi and Write Configuration Settings File.vi to get a basic idea of how the functions are used.

Embedded Labview exe in a LabView program

Is it possible to integrate an exisiting LabView *.exe file in another LabView vi or LabView project?
The existing LabView *.exe does output some measurement data on the front panel, but I would need this data written e.g. to an Excel sheet. So I thought it must be possible to embed the LabView *.exe file into another LabView vi, that reads data from the *.exe file and writes the data into a data file.
I don't have access to the original LabView program, before it was converted to an *.exe file and I don't know the settings used to built the *.exe.
Toodles,
Optimike

Without testing I'm not sure if it is working.
Maybe you should be able to open an application reference to the application. You should add the entries for VI Server in the configuration file to listen on a specific port. In LV 8.6.1 you can open the application with this port. With this reference you can try to open a VI reference for the VI from which you want the data. Use Get CTRL Value to read the data from the control.
The application must be running before you can do this. For the final solution you must make any error handling on errors by the Open Application Reference primitive.
The thing I'm not sure about is if this will work across different versions of LV.
Waldemar
Using 7.1.1, 8.5.1, 8.6.1, 2009 on XP and RT
Don't forget to give Kudos to good answers and/or questions

Customized setup for deployment of Firefox 4 : How to integrate addons & prefs (seems different than 3.6.x)

I'd like to silently install Firefox 4 using customized prefs, but it's seems different than the 3.6.x versions.
How does it work with the new "folder architecture" used in Firefox ?
* For 3.6.x, using the -ms switch install Firefox silently, and i integrated addons & prefs by :
- copying pref.js + localstore.rdf + mimeTypes.rdf + content-prefs.sqlite + bookmarks.html to "localized\defaults\profile".
- extracting all *.xpi addons into the extensions install folder "nonlocalized\extensions".
* For FF 4 the -ms still works, and i tried to copy my addons in "core\distribution\extensions\", but all of them do not install, and I don't see any "localized" or "profile" folder for the prefs..
Thx a lot in advance !

Hi guys, here are some informations that i found and combined. These preferences/customisations ARE TESTED and WORKING!!
First of all, extract your "Firefox Setup 4.0.exe"
'''Silent installation without desktop icon:'''
Create a "nodesktop.ini" at the same place you can find the setup.exe (root directory after extraction) containing following text:
[Install]
DesktopShortcut=false
'''Run''': Installationfolder\setup.exe -ms /INI="CompletePathToInstallationFolder\nodesktop.ini"
'''Disable Import Wizard:'''
Create: InstallationFolder\core\override.ini containing:
[XRE]
EnableProfileMigrator=false
Many options have to be set in InstallationsFolder\core\defaults\profile\prefs.js These directories and the prefs.js File have to be created first. Then make following entries:
'''Use wpad:'''
user_pref("network.proxy.autoconfig_url", "YourWpad.dat");
user_pref("network.proxy.type", 2);
'''Set startup homepage:'''
user_pref("browser.startup.homepage", "http://www.YourPage.com/");
'''Don't show browser rights:'''
user_pref("browser.rights.3.shown", true);
'''Don't ask if FF should be default browser:'''
user_pref("browser.shell.checkDefaultBrowser", false);
'''Dont't show FF welcome homepage at first run:'''
user_pref("startup.homepage_welcome_url", "");

Error in LabView.exe after each start

I installed LabView 7.0 in an older computer (Pentium III, 500 MHz, 512M RAM, Windows 2k sp4) along with GPIB and E-series PCI cards. Each time I open LabView it crashes and says "LabView.exe has generated errors and will be closed by Windows. An error log is being generated." The error log is attached, but means nothing to me. It crashes with regularity within 30 sec of opening LabView but I seem to be able to run .vi's during that time. I've tried:
1) Reinstalling
2) updating video card driver and ActiveX
3) installing on a different drive
none of these help.
Any help you may have would be appreciated.
Attachments:
LabVIEWlog.txt ‏1 KB

Hello,
The file you attached is a LabVIEW.ini file, where the configuration settings are stored. Please find the error log file, and this should give you a better idea what might have caused the error.
There are two types of log files. There are those created by LabVIEW and those created by Windows.
The log file created after internal LabVIEW errors is called LabVIEW_Failure_Log.txt and it is stored in your temporary LabVIEW directory. By default, this directory is located at C:\Documents and Settings\(User Name)\Local Settings\Temp (Windows 2000).
NOTE: By default, the Local Settings folder is a hidden folder. In order to view hidden files and folders in Windows Explorer, select Tools » Folder Options » View. In the Advanced Settings field, select Show
hidden files and folders.
If you have modified the location of you temporary directory, the log file will be located there. To view or change LabVIEW's temporary directory path, go to Tools » Options » Paths » Temporary Directory. For more information on the error information contained in the LabVIEW_Failure_Log.txt file, visit the LabVIEW Internal Error Support Page linked below.
If you receive an error message saying that LabVIEW has generated errors and will be closed by Windows, there will be a different log file created. This is a log file created by Windows, and by default it is a Dr. Watson's error log file. These log files are saved as .log file under ...\WINNT folder for NT based systems, and as .wlg under ...\Windows\Drwatson folder for Windows 9.x systems.
If you open just LabVIEW, without trying to open a VI, will you still receive the crash? If so, can you create a new simple VI similar to the VIs that crash LabVIEW and run it? Do you call any hardware driver or o
ther dlls with the VIs that cause LabVIEW to crash?
Zvezdana S.
National Instruments

Labview.exe error is generating

It is giving me labview.exe has generated error message, when I am trying to generate, data log file with time stamp, to find last run of my program. I have attached the vi here.
Message Edited by Support on 04-13-2006 10:46 AM
Attachments:
get_last_run.vi ‏69 KB

I'm assuming that the VI you posted is running as a subVI in your main and that you are getting the path somewhere else. If that's the case, then you should know that the path to a folder is different when you build a executable. For example, if you use something like Current VI's Path, in the development environment, it might be something like c:\folder\example.vi. In an executable, the path would be c:\folder\application.exe\example.vi. You need to do an extra strip path in an executable. You can use the Application property called Application.Type to determine whether or not you are working with an exe or development system to decide whether or not to do an extra strip path. There have been numerous postings on this exact same topic and if you need example code, you can search the forum.
p.s. It's not a good idea to post your phone number and email address in a public forum unless you enjoy spam and unsolicited phone calls. It's also a bit unreasonable to expect the users of this forum (most of whom do not work for NI) to respond directly to you.
Message Edited by Dennis Knutson on 04-13-2006 09:22 AM

Unpluggin the Ethernet is Different Than Turning Off The Server!

Hi All,
I am working with a cFP2020 with a 4 space backplane. I am running Labview 8.0 RT. Have not gotten around to putting in the latest set of CD's I just got sent. I have the whole setup on my desk here and am noticing a potential problem for my application. Was hoping that someone could explain this to me?
I am building a vehicle, with the cFP on the vehicle and a PC controlling the vehicle. Mostly Im turning on lights and reading sensors on the vehicle, but I am transmitting some commands.
My perfect world would be that if I lost communication between the vehicle and the PC, that the vehicle would recognize this within a reasonable ammount of time (1-2 seconds) and stop itself. I would like a whole routine for "com failure" to run if that is the case.
My questions:
It does not look like I want to use the fieldpoint watchdog because everything I have read indicates that on a watchdog com error, the fieldpoint shuts down. Am I wrong? Should I look further into this?
I wrote my own watchdog. It sends messages back and forth on shared variables. If a message is late, it turns off a light (using cFP led's on the main module.) The PC VI is running as part of the project. The Vehicle VI (on the cFP) is compiled as an application that runs on startup. I have experimented alot with failure situations. The following work fine:
- Stopping the PC VI that communicates with the vehicle VI. The light on the cFP turns off fine.
- Stopping the Shared Varaible Engine. "Undeploy" on the shared varaible in the project. The light turns off fine. Infact both the PC and the Vehicle VI's register the dissconnect with their lights.
The following does not work right:
- Unplugging the ethernet link! The VI on the vehicle (cFP) is still running (got another blinking light going), however it takes 11-16 seconds for the light to turn off, indicating the disconnect. This is quite a bit longer than the other methods that work fine (those are about 1-3 seconds). Can anyone think what is going on?
I know this seems like an essoteric question, but it gets to the protocal for the cFP. Should I be running my PC VI as an application? I am running it in the project.
Thanks
Kevan -
As an aside, is there a way to deploy an application and have it run immediatly upon deploy. I am having to reboot to run the application. I notice different performance if its running from the project v. it running as an app. Since I will be using it as an app in the final product, I want to test it that way.
Thanks Again -

Kevan,
The quick answer is that most NI ethernet protocols are implemented with 10 second timeouts. This is different than the undeploy in that stopping the shared variable engine will send unsubscribe messages rather than timing out. (Note: I am making an assumption on how the shared variable protocol works because it is partially based on the older Logos protocol used in Fieldpoint, and that is how the closing works for Logos).
As for the watchdogs, there are two watchdogs in [c]FP RT modules; the RT watchdog (which can reboot the controller) and the network communications watchdog (which can set one or more outputs to a desired state on loss of communication).
For a very rapid communication link disconnect, implement the shared variable as a boolean that has it's state inverted every half second. Have the [c]FP controller read the variable and look for changes in the state of the variable. If the variable does not change at the update rate (with some small margin for timing), then you have probably lost the link prior to getting a full network timeout.
Regards,
Aaron

Open Independent Mulitple sessions with oracle in a LabVIEW exe

Is it possible to maintain different sessions to same database from within a labVIEW exe. I need to have a server to which multiple clients connect. Server starts handler for each client and each handler needs to connect to the database and transact on its own and get some data for the client. This is basically to achieve concurrency. But the operations are happening only sequentially. Please help.

Your two other postings:
"Parsing an SQL statement coming in the way of reentrancy."
"NEW!! Parsing an SQL statement coming in the way of reentrancy."
I put a link to all your postings here to help others on the discussion forum to follow your questions.
The problem may be that your server has a single CPU and that it can only do one thing at a time. Another limitation may be the abstraction layer for your database. What version of the Oracle d
b are you using? Do you have this problem across computers or just on a single machine?

Labview Exe acts different than Vi

Similar Messages

Maybe you are looking for