LabView 2010: Any improvement in Resolution Independence?

Hi Everyone,
My last project I did in LabView was Way back in LV8.5.  Back then, I posted a question concerning screen resolution independence in LabView. Specifically, making a form resizable at run time and properly scaling controls / text properly:
http://forums.ni.com/t5/LabVIEW/Labview-resizing-control/m-p/577438
Have any improvements been made on this front in either 2009 or 2010?  I'm getting ready to start another project where the UI must be able to scale (resolution wise) properly, and will probably use VS2008 if not much progress has been made in labview in this area.....
Thanks for your input!

tartan5 wrote:
In this day and age of widely varying (and constantly changing) screen resolutions, you would think this would be a bit higher on the priority list.
You might, but consider that many programs written in LV (including those built into EXE) are probably run on one or few stations, where it's easier to tell the users "don't change resolution" than to write any code which will handle this.
I don't have the experience with VS necessary to compare the two, but I assume that VS is still better at this.
NI is certainly aware of the demand for something like this, but they also announced that LV 2011 would focus on stability and performance improvements, so I wouldn't expect to see any progress in this area in the next couple of years.
Also, if you go to the idea exchange, search it first. I believe people already posted related ideas.
Try to take over the world!

Similar Messages

  • 3D graphs cause LabVIEW 2010 to hang

    I've been using LabVIEW  2010 for several weeks without any problems, but today I noticed that it doesn't work at all with anything related to the 3D picture control. Today was the first time that I tried doing anything with the 3D picture tool since installing LV 2010. Dropping any of the 3D Graphs on the front panel of a new VI causes LV2010 to hang. (By hang, I mean the VI window remains open but most UI things no longer work.  Right-clicking on the window does not show a context menu.  The main menu doesn't work.  The X button does not close the VI front panel window nor the diagram window. Control-Q does not cause LabVIEW to quit.  I have to kill the process in Task Manager.)  It is the same story with just a plaing 3D picture indicator.  Also, the solarsystem.vi example does not work either.  The problems start as soon as I open the solarsystem.vi.  After killing LV with Task Manager and relaunching LV10, I do not get the LV message about a previous crash.
    The problem I am talking about is for LabVIEW 2010 with the f2 patch running in Win7.  I am actually running it using VMware Fusion 3.1.3 on a 2009 Mac Pro running Lion.  The Mac drivers are all updated.  Since it is VMware Fusion machine, the video driver on the Windows side is part of the VMware Tools installation, which is up to date.
    After searching the forums, I've tried all the other potential solutions I could find:  1) repaired LV2010 using add/remove programs and 2) tried using the compatibilty mode settings to turn off Aero. 
    Interestingly, 3D graphs work fine on the Mac side for LV2010 for Mac.  
    Even more insterestingly, 3D graphs work fine on Win7 for LV 8.5, which I still have installed.  The fact that it works fine for LV 8.5 would seem to indicate that Lion did not introduce the problem and that the video driver is working fine.
    Solved!
    Go to Solution.

    Yep, it's the same virtual machine.  I set it up almost 2 years ago and it has been extremely stable.  Both LabVIEW 8.5 and 2010 have been perfectly happy on it.  It's a great way to do LabVIEW on Win7.  I didn't notice any changes at all to the VM when I upgraded from Snow Leopard to Lion.  I installed LabVIEW 2010 before upgrading to Lion, but I didn't have occasion to work with 3D controls before the upgrade to Lion so I don't know if it would have worked on Snow Leopard.  The Mac versions of both LabVIEW 8.5 and LabVIEW 2010 also work great on the both Snow Leopard and Lion.
    I happen to have an XP virtual machine too, but I haven't installed LabVIEW there.  Let me know if that would be a worthwhile test.
    You might check with Marc Page--unless he has already upgraded again I think he has a similar machine to mine.
    The video card is the original stock:
    NVIDIA GeForce GT 120:
    Chipset Model: NVIDIA GeForce GT 120
    Type: GPU
    Bus: PCIe
    Slot: Slot-1
    PCIe Lane Width: x16
    VRAM (Total): 512 MB
    Vendor: NVIDIA (0x10de)
    Device ID: 0x0640
    Revision ID: 0x00a1
    ROM Revision: 3386
    Displays:
    Cinema HD Display:
    Resolution: 2560 x 1600
    Pixel Depth: 32-Bit Color (ARGB8888)
    Main Display: Yes
    Mirror: Off
    Online: Yes
    Rotation: Supported
    Display Connector:
    Status: No Display Connected

  • Labview 2010 crashes XP while looking for webserver

    Hi,
    I am using a Windows 7 laptop with LV 2010 to compile my 32-bit executable.  I've copied it to my target Windows XP, SP3 computer and after running it for a short while it rebooted the computer automatically (I believe the reboot was caused by a BSOD).
    I've gone into the Windows Event Viewer and there is an event that says "Labview information:  Error: 404 "Not Found" for "national instruments/ni-rpc/interface/eadfc80d-1e6f-425b-8986-12ccef98f646/ncalrpc", file "c:/program files/national instruments/shared/ni webserver/www/national instruments/ni-rpc/interface/eadfc80d-1e6f-425b-8986-12ccef98f646/ncalrpc": Can't access URL     ."
    I'm attaching a jpg of the Event in case I typed it incorrectly.  There is another post that mentions this error but there is no resolution and the discussion went in a different direction:  http://forums.ni.com/t5/LabVIEW/LabVIEW-2010-unstable-on-Windows-7/m-p/1247366/highlight/true
    Neither my Win 7 development laptop or my target Win XP system have this www folder.
    Has anyone seen this before or know the cause?  Thanks.
    Steve
    Attachments:
    Event Viewer small.jpg ‏69 KB

    Altenbach,
    Thanks for the quick reply.
    Yes, the time stamp of this error coincides with the crash.  I guess I assumed that it caused the crash because I see about 20-25 instances of it in the Event Viewer.  Immediately before these errors appear there are two instances of the NI Configuration Manager with the Description saying "Opening configuration database".
    This only happened on time and I have not been able to reproduce it again.
    I'll need to explain to my customer why this Error has appeared so many times in the Event Viewer, and also how I can get it to not happen again.  Do you have any suggestions?  Once I isolate this error and prevent it from happening again then I can monitor the computer for future crashes.
    Thanks.
    Steve

  • Howto fix Labview 2010 delays

    My Labview 2010 causes huge delays ~30-40s when compiling and when using its restore function.
    It is blocking the pc (unusable) for that time.
    I tried several times now but development work with that pauses is not possible.
    The System: MS XP32, Athlon64 3800+ with 2GB RAM is not recent, but clearly within the min. Requirements: Pentium 4 and 1GB
    The app is first written under LV 6.4/8.0 and its using very less express vi stuff.
    Howto solve the delay problems coming with LV 2010?
    1. Do I need to rewrite my whole program using express Vis...
    2. Can I deactivate some features to reach LV 8.0 performance....
    3. Do I need faster cpu and more RAM...
    4. Can I give this program back to NI because of a) missing compatibility and b) wrong minimum requirements
    btw...can  Labview be completely deinstalled at all...?
    sorry for asking a bit agressive but this "NI program" cost me several days now for nothing
    Hints esp. to Question 2 would be very appreciated...
    Solved!
    Go to Solution.

    mwo wrote:
    is that much...?
    Yes, 1MB for code and 3MB for diagram objects for a single VI seems a lot. How complicated is that VI? I would recommend to modularize it a bit.
    In any case, you might want to submit the code to NI, maybe there is a bottleneck in the compiler that could be improved. The 2010 compiler is much better, and I never have speed issues, even with large projects.
    LabVIEW Champion . Do more with less code and in less time .

  • Labview 2010 icon editor extremely slow

    Working on a medium size project in LabVIEW 2010.  Out of the blue the icon editor slows down.  So slow that typing in one text character takes 20 seconds.  After closing the editor there is about 3 to 5 second lag on every action I make in LabVIEW. 
    Restarting LabVIEW sets things back to normal until I open the Icon Editor.  Opening any SubVI results in this problem.  And this occurs in any project or even if no project is open and I try to edit icon in an Untitled 1 subVI.
    Anyone else seen this behavior.  I really don't want to re-install LabVIEW 2010. 
    Thanks
     

    I'd almost suggest using the old icon editor, then edit and save the VI, then try the new icon editor again.  One issue could be with keeping track of all that layer information and one of them having bad data or something.  By using the old icon editor and saving, it might save the icon as the flat image it is, and wipe away all that layer information the new icon editor uses.  
    Of course before there was an improved icon editor developers made their own, and I'm curious to know if they still work, and if they would load faster.
    https://lavag.org/files/file/100-mark-ballas-icon-editor-v24-lv2010/
    https://lavag.org/files/file/91-improved-lv-2009-icon-editor/

  • Application crashes in Windows 7 64bit made in Labview 2010 sp1 f2 with Fault module name%3A lvrt.dll%2C version 10.0.0.4033 and exception code c0000005

    I build an application exe and then its installer along with run time environment.
    The installers instals the application correctly but when I try to execute the application, I get an error that application has crashed and Windows must close it down or search for solutions online with this additional information for the crash. 
    Problem signature:
    Problem Event Name: APPCRASH
    Application Name: AGMS.exe
    Application Version: 1.3.0.0
    Application Timestamp: 4c24e8f5
    Fault Module Name: lvrt.dll
    Fault Module Version: 10.0.0.4033
    Fault Module Timestamp: 4c9273f4
    Exception Code: c0000005
    Exception Offset: 00005310
    OS Version: 6.1.7601.2.1.0.256.1
    Locale ID: 1033
    Additional Information 1: 0a9e
    Additional Information 2: 0a9e372d3b4ad19135b953a78882e789
    Additional Information 3: 0a9e
    Additional Information 4: 0a9e372d3b4ad19135b953a78882e789
    Read our privacy statement online:
    http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409
    If the online privacy statement is not available, please read our privacy statement offline:
    C:\Windows\system32\en-US\erofflps.txt
    I am using labview 2010 sp1 32 bit on a 64-bit machine, with the following specs
    Operating System: Windows 7 Home Premium 64-bit (6.1, Build 7601) Service Pack 1 (7601.win7sp1_gdr.130318-1533)
    Language: English (Regional Setting: English)
    System Manufacturer: Dell Inc.
    System Model: Dell System XPS L502X
    BIOS: Default System BIOS
    Processor: Intel(R) Core(TM) i7-2630QM CPU @ 2.00GHz (8 CPUs), ~2.0GHz
    Memory: 8192MB RAM
    Available OS Memory: 8106MB RAM
    Page File: 3457MB used, 12753MB available
    Windows Dir: C:\Windows
    DirectX Version: DirectX 11
    DX Setup Parameters: Not found
    User DPI Setting: Using System DPI
    System DPI Setting: 96 DPI (100 percent)
    DWM DPI Scaling: Disabled
    DxDiag Version: 6.01.7601.17514 32bit Unicode
    The exe /application runs fine on my PC but when I try to run it on another PC it crashes. The other PC has similar specs as given below
    Operating System: Windows 7 Ultimate 64-bit (6.1, Build 7601) Service Pack 1 (7601.win7sp1_gdr.140303-2144)
    Language: English (Regional Setting: English)
    System Manufacturer: LENOVO
    System Model: HuronRiver Platform
    BIOS: Default System BIOS
    Processor: Intel(R) Core(TM) i3-2330M CPU @ 2.20GHz (4 CPUs), ~2.2GHz
    Memory: 4096MB RAM
    Available OS Memory: 4010MB RAM
    Page File: 1359MB used, 6658MB available
    Windows Dir: C:\Windows
    DirectX Version: DirectX 11
    DX Setup Parameters: Not found
    User DPI Setting: Using System DPI
    System DPI Setting: 96 DPI (100 percent)
    DWM DPI Scaling: Disabled
    DxDiag Version: 6.01.7601.17514 32bit Unicode
    I tried another machine, 64 bit of course, as I want to deploy my application on a 64bit PC, but still got the same problem.
    This other machine was from HP, iCore 3 (4 CPUs) 2.2GHz, 4GB RAM and running Windows Professional 64 bit.
    Now as I see it, it could be a Run-time environment mis-match error.
    For this I tried installing a 64 bit LVRTE from NI, but still no sucess.
    I checked DEP, for all 3 PCs and it was set to the following
    Turn on DEP for essential Windows programs and services only (first option).
    I am confused. I can not find a solution for this and it is really frustrating.

    But I am assuming that when I make the installer, the 32-bit Run Time Engine is appened with the installer, as show below
    Since from the picture you can see its including the support installers from '\Program Files (x86)\'
    The application runs queries to fetch data from database in SQL server 2008, and for that I am using a Microsoft SQL Native Client 2008 R2 64 bit ( this is the only version that installs on either PC, even the one on which I developed my LV Application).
    I am not using any driver, only toolkits for reports - and for that I un-checked the "Remove unused polymorphic VI instances" when making the executable, otherwise LV throws up an exception that share variable are not being included.
    Yes I did reboot every time after I ran the installation.
    Still getting the same error.

  • Run-time engine problem in Labview 2009 and Labview 2010

    I have a problem with Labview 2009 and Labview 2010. I updated my Labview 2009 into 2010. But it turned out to be a trial one, because i did not have the serial number. So I uninstalled the Labview 2010. however, the funny stuff came over. I cannot use my Labview 2009. So i uninstalled Labview 2009 again. But eventually, I could not reinstall Labview 2009. Every time i had a runtime error and i could not proceed with the installation. in addition, any installation  related to Labview is not permitted and the same error came up every time. it is very annoying.
    So, What is the deal?
    I attached the error here. Any comments or advice are welcomed and appreciated.
    Attachments:
    error.docx ‏2305 KB

    By chance is this machine's language set to any non-English locale?  You would check the locale setting by:
    Opening Control Panel.
    Opening "Regional and Language Options".
    Looking Under "Regional Options" >> "Standards and Formats"
    If it is set to something besides English, trying setting it to English and please report back what locale it was set to (or if this even solves the problem).
    Regards,
    - WesW

  • Building App Gives Error 6 about 50 - 80 - 99% of the time. Windows7, LabVIEW 2010 SP1

    Hi
    First off here is a link to a discussion of the problem.  http://forums.ni.com/t5/LabVIEW/Error-6-occurred-when-building-an-Executable-in-Labview-2009/m-p/997...
    I have tried all the suggestions on this link with no luck.
    Background:   have been using LabVIEW 2010 without problems since Sept, then I started getting the error 6 with the following message.
    " Error 6 occurred at Delete in AB_Engine_Delete_Internal_Files.vi->AB_EXE.lvclass:Build.vi
    ->AB_Engine_Build.vi->AB_Build_Invoke.vi->AB_Build_Invoke.vi.ProxyCaller "
    This started on one project and is now occurring on another project.  Sometimes it builds 50% of the time, other times I can't get it to build at all.  I have upgraded to SP1, no change.
    Here are some things I have tried.
    Moved build directory to c:\a
    Renamed project, moved project right under c:\
    Disabled Google , disabled Win indexing, disabled Win7 user acct. Control, run LabVIEW as Admit all the time, win explorer closed
    mass compiling, closing the project, closing LabVIEW, re-booting
    Unistalled LabVIEW 2010 SP1 and re-install, twice.
    I believe I rebuilt my project in a new project.
    I moved my projects to a WinXP system laptop I have, and they never get Error 6 !  Short term fix, but I have to use Win7.  So I hope this means it is not my code.
    The funny thing is that this is totally random.  The unfunny thing is having to explain to a client I can't get my code to compile during a frustrating 95% of the time failure episode, yikes!
    Any help and suggestions would be welcome.
    BTW, the next step is to totally uninstall LabVIEW with a 'special' procedure and piece of code sent to me.  Don't want to, but am really at wits end.  Also waiting to hear back from my service ticket, but am desperate to have parallel solutions to try.
    Thanks
    Mark Ramsdale

    Thanks for the clarify.
    I also meant to post this link.  It has a lot of info, this is the link I tried most if not all of the suggestions for.
    http://forums.ni.com/t5/LabVIEW/Get-Error-6-about-50-of-time-when-building-Application/td-p/1242634
    By the way, I was told that uninstalling LabVIEW will not resolve the issue, dodged a time killer :-)
    It seems the error is caused by Win7 and file reserving.  Waiting to hear back on that.  Have an SR.
    Again, any suggestions welcomed, maybe some Win7 ideas from those who know more about it.
    mr
    Mark Ramsdale

  • Labview 2010 run-time engine silent install

    I am having trouble with installing the run-time engine for LabVIEW 2010 with the silent option.
    I am using the minimum version of the run-time engine.
    Before I used the LV7 run-time engine. Then I could install it silently using LVRunTimeEng.exe /qb!
    In LabVIEW 2010 the run-time engine is no longer a single file but a directory that contains the installation files. There are two files that can be used to launch the installer Setup.exe and LV2010runtime.msi.
    Setup.exe does not seem to accept any command-line arguments. LV2010runtime.msi however accepts the command-line arguments and can be installed silently.
    Now my problem is that I am building a windows installer using a third party application and it is only possible to launch exe files after the installation completes. Before I could launch the LVRunTimeEng.exe /qb! to install the labview 7 run-time engine but now when I have upgraded to labview 2010 I cannot do the same for Setup.exe.
    My question is if it is possible to use the Setup.exe file to install the Labview 2010 run-time engine (minumum) silently?

    Setup.exe runs a number of other .exe files during its execution.  This article looks like it will allow you to run setup.exe silently by supressing all messages and windows:
    http://digital.ni.com/public.nsf/allkb/878FC4C374013ADF8625733D00688F67

  • LabView 2010 Applicatio​n Builder for EXE Always Included files are not Included

    In LabVIEW 2010 F2, When I am using the Application Builder to build an EXE file, I have listed 10 or so files to Be "Always Included". But when I Explore the directory where the EXE was built, those "Always Included" files are not there or in any subdirectory under the EXE file.
    This frequently makes my EXE file not work properly because important files are missing. I have to spend extra debugging time to find out the the cause of my problem is missing files that the Application Builder should have transferred "Always".
    Why did the Application Builder, when building an EXE target, not include the files that should be "Always Included"?
    Why does the Application Builder ignore these files specifications?

    Dennis Knutson wrote:
    The build does include files you select. Post an example project with a small VI and some separate files where this does not happen.
    No, it does not appear that all of the files that I listed in the "Always Include" list are copied during the Build process to the Build directory or any subdirectory under that.
    The Build Source Files.jpg file shows most of the list of the files that should be "Always Included". Notice the .VI and .ctl files that are listed
    The Build Directory.jpg file shows the file in the Build directory that were built.
    The Data Directory.jpg file shows the data directory under the Build directory and may include some of the files listed in the "Always Include", but not all of them.
    The other subdirectories under the Build directory were created by me and do not include any files that were copied during the Build process.
    So not ALL of the files that were included in the "Always Include" list were copied into the Build directory area as expected. ALL of the files that are listed as "Always Include" should be copied, if they exist. Those files existed when then were selected for the List and they existed at the time of the Build.
    I can not include an example project that demonstrates this. I am prevented from doing so by the terms of an NDA. You are going to have to take my word that this event is real and happens the same way every time. This information should be sufficient for someone to investigate why do not ALL of the files listed in the "Always Include" list are copied into the Build directory area regardless of the file type or contents.
    Attachments:
    Build Source Files.jpg ‏151 KB
    Build Directory.jpg ‏125 KB
    Data Directory.jpg ‏131 KB

  • Strange problem of calling library function node in labview 2010 and 2011

    one year ago,I develop a program to usb device data and it works well,in labview 8.6 or 2009(win xp).Recently, When I test
    the program in labview 2010 and labview 2011(win xp).,the program always crash immediately.I check the program and find main
    problem is in call library function node. In my program,I use labview 2009 library for the USBExpress driver for
    Silicon Labs USB MCU's from:https://decibel.ni.com/content/docs/DOC-9522,for example, 2 functions SI_OPEN and SI_READ
    can not work well.
    the header definition of SI_OPEN and SI_READ is:
    SI_STATUS WINAPI SI_Open(
    DWORD dwDevice,
    HANDLE* cyHandle
    SI_STATUS WINAPI SI_Read(
    HANDLE cyHandle,
    LPVOID lpBuffer,
    DWORD dwBytesToRead,
    LPDWORD lpdwBytesReturned,
    OVERLAPPED* o = NULL
    the SI_STATUS is equivalent to int type.
    orignally, for HANDLE * in SI_Open, the parameter type in call library function node is numeric, data format is unsigned 32 bit integer ,and pass pointer to value.
    for HANDLE in SI_Read, the parameter type in call library function node is numeric, data format is unsigned 32 bit integer ,and pass value.The program works well in labview 8.6&2009,however,crash in labview 2010 &2011.
    later,I debug the program, for HANDLE *, I choose parameter type in call library function node as adapt to type, data format is point to Handles.for HANDLE, I choose parameter type in call library function node as adapt to type, data format is Handles by Value.Crash not happend in labview 2010&2011,however,it cannot read any data from from USB device correctly as before.I can not find the reason.
    Dear friends,I need your help to answer the problem. Thank you.

    Based on the help page it looks like it should execute asynchronously.
    The thing in the description that leads me to believe they execute asynchronously is that you can configure the library to run as a multi-threaded operation.
    Please take a look here to see the difference between synchronous and asynchronous execution.
    Since the code even has the ability to be multi-threaded, you can consider it as running in parallel to your other code.
    Any data returned is passed to the thread that called that function.
    Cory K

  • LabVIEW 2010 SP1 may not cleanly shut down

    Occasionally LabVIEW 2010 SP1 (32-bit, running on Windows 7) will appear to "hang" when the "Getting Started" window is closed.  The window disappears but the shortcut icon still appears in the Windows toolbar in the bottom of the screen.  Right-clicking and selecting "Close Program" does not work and Windows seems to think any VIs that have been recently closed are still open.  The program is still in the list in Task Manager and it can successfully be shut down all the way from there.
    This is more of an annoyance than an operational issue (I think) - is there something I am doing (or failing to do) that causes this problem? 
    Thanks in advance.

    Hello Unplugnow,
    Deleting the .ini file will not cause any issues in terms of being able to reload Labview it will simply restore the default settings for Labview which will insure that there were be no data corruption issues. I have tried this procedure on my side with no issue although I would recommend copying the .ini file to another directory in case you need to recover this information at a later time. 
    To another note, does this issue arise when you are opening a particular VI, or does it occur when you are simply opening and closing Labview?
    Best,
    Blayne Kettlewell

  • LabVIEW 2010 App Builder: Registry editor has issue with keys of the same name at the same level in registry tree

    This is a bug report for an NI application engineer.  Please file a CAR. 
    In a LabVIEW 2010 project, create a new installer build and go to the Registry editor.
    Enter some keys like the following
    Click OK to close the installer wizard.
    Now reopen the build specification and go to the Registry editor.  The registry editor comes up blank and non functional.
    I believe the registry entries are still written when the installer executes, but you cannot edit the registry any further in LabVIEW 2010.  This was not an issue in LV 2009. The issue seems to stem from having two keys with the same name at the same level in the registry tree (in this case, the two "Test" keys). 

    Hi sensor_daniel,
    This was reported to R&D (#305026) for further investigation.
    Thanks for the feedback! 
    Have a great day,
    Chris V
    Applications Engineer
    National Instruments

  • Bug in Formula node under LabVIEW 2010

    appendix is my test project.
    there is a test.vi in the project.  The test.vi contains only a case structure with 5 SAME subdiagrams. Each subdiagram contains a formula mode. The formula code does some calculation with an 2d array of double.
    If i run the test.vi under LabVIEW 2010(or SP1), it may cause  LabVIEW 2010 corrupt occasionally. If I build application form the test.vi, and run the application ,the application will definitely corrupt.
    if I delete one subdiagram of the case structure , the test.vi and the application both run well.
    however, the same project works well under LabVIEW 2009.
    so is it a bug with LabVIEW 2010?
    Attachments:
    Test.zip ‏7 KB

    'corrupt' means the program exit unexpectedly without any warning or error message. it just disappeared and you can't find it in the 'process' tab of windows task manager after that.
    If LabVIEW corrupted, once i reopened it, there may be a error message dialog pop-uped before the LabVIEW interface appeared. The dialog said something wrong with 'undo.cpp'. I zipped the failure long to the appendix. I can't find any other error or warning message from LabVIEW or Windows ( I checked the Windows Event Viewer).
    If the built exe corrupted, There isn't any message for  LabVIEW or Windows neither.
    I tested the project on my own laptop with Windows XP(SP3) Chinese Version and NI PXI-8810 with Windows XP(SP3) English Version which is my target machine.
    Appendix also contain a exe build in my laptop. If I run the exe file, once I click the run button , it will corrupt. I wonder if it works the same on your computer.
    Thanks for your concern.
    Attachments:
    lvlog2011-05-13-23-23-35.zip ‏150 KB

  • Bug? LabVIEW 2009 Enum in Datalog Refnum Loses Data in LabVIEW 2010+

    Hi 
    Can I please get support from an AE?
    Attached is a LabVIEW 2009 VI with a Control of an Enum in a Datalog Refnum.
    Whereby the Enum's FP Object is represented as an image.
    In LabVIEW 2009 this works fine however, in any higher version (I have definitely tested with LabVIEW 2011, but have been told LabVIEW 2010 is the same) the image is blank.
    Is this a bug - is data being lost?
    Interestingly enough, if I remove the LabVIEW 2009 Enum from the Datalog Refnum then load in LabVIEW 2011 this image displays correctly.
    Is there anything I can do (setting? etc...) in LabVIEW 2009 that will correct this problem so it displays correctly in later versions?
    This issue originated in this LAVA thread.
    Cheers
    -JG
    Certified LabVIEW Architect * LabVIEW Champion
    Attachments:
    Datalog Refnum Enum_LV2009.vi ‏10 KB

    This was reported to R&D (# 311354) for further investigation. 
    As a possible workaround, if you move the enum control out of the datalog refnum before saving in LV 2009, when you open your VI in LV 2011 the image will still show up for the enum control. You can then move the enum control back into the datalog refnum and it should work fine. 
    Thanks for the feedback,
    Daniel H. 
    Customer Education Product Support Engineer
    National Instruments
    Certified LabVIEW Developer

Maybe you are looking for