Lot of bugs & Crash labview 2012 SP1 in Table control

 Run applied vi.
We see lot of bugs in Table control. I fixed some on the right table, but not all. 
How fix other?
Thanks in advance, Alex.
Attachments:
NI_BugReport_in_Table.vi ‏30 KB

The attached modification includes a workaround for the ctrl+z bug on the Data Mixer (Not Table).  It basically keeps a history of your deleted headers and adds them back in when the user types ctrl+z.  Not the most elegant solution, but gives you an example of what you can do to work around it.
You could clean it up by using functional globals instead of shift registers.
www.movimed.com - Custom Imaging Solutions
Attachments:
NI_BugReport_in_Table (Modified).vi ‏49 KB

Similar Messages

  • Measurement Computing USB-DIO96H driver issue with Labview 2012 SP1 on Windows 7 x64

    Is anyone else having issues with measuremetn Computing's USB-DIO96H driver in Labview 2012 SP1. It throws warnings in Labview when loaded that are unresolvable as you can't save to the DLL driver file. Also it regularily crashes Labview randomly. I am not impressed with their driver. Anyone have any suggestion other than replacing with NI-DAQ solution, which I am working on?

    I've taken a look and I don't see any drivers available for that device on ni.com. There are two potential workarounds that would both involve building your own driver:
    1. Write a LabVIEW application that calls functions on the DLL you downloaded from Measurements Group
    2. Write a LabVIEW application that addresses the device using NI-VISA and serial communication.
    Some resources if you choose to go down that path:
    http://www.ni.com/devzone/idnet/development.htm
    http://www.ni.com/white-paper/3271/en/
    http://www.ni.com/white-paper/3009/en/
    Hope this helps!
    Rob B
    FlexRIO Product Manager

  • Force LabView 2012 SP1 f4 patch installation

    Hi,
    it was necessary to repair my LabView 2012 SP1 installation. When I start LV now
    it has the version 12.0.1. I had installed also f4-Patch. When I try to install the f4 patch
    now after my repair installation it doesn't work.
    How can i force the installation of LV2012 SP1 f4 patch?
    Regards

    Hi Chris,
    no, i don't get any error message. The installer told me only "nothing to update" as text message
    inside of the installer window.
    1. i have had installed LV 2012 SP1 f4
    2. than LabView crashed sometimes
    3. than i made a repair installation of LabView 2012 SP1 (from DVD)
    4. tried to install the f4 Patch afterwards (as download and via update service, tried both)
    I don't know where the patch setup gets it's information about
    the installed LV 2012 version, but it seems that a repair installation
    doesn't reset that information and let that info still on patch level f4.
    However, i deinstalled all developer editions and removed everything from
    NI and reinstalled my developer editions. That was, for me, the only way
    to get my LabView back on patch level f4.
    I didn't find any setup switch to force the installation (the info was shown with "/?" as parameter)
    Stefan

  • Can I get MJD (date and time) in LabVIEW 2012 SP1?

    I need to time stamp my data before sending it to the file.  I have been doing this with the standard calendar date and time but MJD is what we prefer to use.  How can I get an MJD timestamp in LabVIEW 2012 SP1?
    Solved!
    Go to Solution.

    Hello Brad_Henry,
    The Format Date/Time String will return the day of the year when the %j argument is used, as per this help document:
    LabVIEW Help: Format Codes for the Time Format String
    http://zone.ni.com/reference/en-XX/help/371361J-01/glang/codes_for_time_format_str/
    If you're looking for the actual MJD, I'm not aware of a built-in function that generates this so you'll probably need to create or find a function to calculate it manually.  This should pretty basic arithmetic, and it looks like people have already made a few public examples, the first two search results here look to be just about what you need:
    ni.com search:
    http://search.ni.com/nisearch/app/main/p/bot/no/ap/tech/lang/en/pg/1/sn/catnav:ex/q/julian/
    Regards,
    Tom L.

  • Vlm 3.0 LabVIEW 2012 SP1 disabled in Installer

    Hello folks,
    i have a Problem with die build Installer with my new updatet vlm 3.0.
    I already get the the new license file for vlm 3.0 and installed it, then i made the installer for
    LabVIEW 2012 SP1 like i have done it with the previous versions of LabVIEW 2009 2010 2011
    In the produkt list of the installer LabVIEW and the DriverDVD is disabled by default (see Screenshot).
    Solved!
    Go to Solution.

    Today i was looking on the server and i have seen that the licenses are LabVIEW 2012 licenses.
    I want to install LabVIEW 2012 SP1.
    So that's normal, i think i have to wait until i get the new license file for the new version.
    Thanks BRennhofer for this idea.
    I will report here.

  • Simple Math VI crashes LabVIEW 2009 SP1

    Hi,
    We previously filed a related issue, (ref #: 7302858). The last problem was resolved by 
    Andy Hertzka from NI re-compiled the VI and send it back to us. That re-compilation solved the LabVIEW crashing.
    However, the interesting crash happens again.
    I attached a working VI before the change and a non working VI after the change and save. All the change I applied to the VI is
    1. Add the "Word bits" as a connector on the diagram
    2. Save it Then the VI begin to crash LabVIEW 2009 SP1.
    Before the change, the VI was functioning all right.
    Any idea why this might be happening? Can you try to recompile the non_working version and send it back to me for a try?
    Thanks,
    Tian
    Attachments:
    Non_working_AfterChange_RECOMPILED LRSample_U32in_U32output.vi ‏110 KB
    Working_B4Change_RECOMPILED LRSample_U32in_U32output.vi ‏110 KB

    Tian,
    Like Andy I was unable to see why this code is unstable on your machine. I am able to run the code fine on my computer without any problems. Looking at the code on the block diagram I do not see any major "crash worthy" issues with it. 
    I have resaved the VIs like Andy had in order to fix your issue. By the way what OS are you using, windows 7? It might be helpful to save the log file for the LabVIEW crash. You should get this option when LabVIEW is restarted. 
    <Joel Khan | Applications Engineering | National Instruments | Rice University BSEE> 
    Attachments:
    Non_working_AfterChange_RECOMPILED LRSample_U32in_U32output1.vi ‏108 KB
    Working_B4Change_RECOMPILED LRSample_U32in_U32output1.vi ‏108 KB

  • Labview 2012 sp1 Linux No Help ?

    Hi all, my help is not working in Labview 2012 sp1 (Linux edition).
    I keep reading that i need to change a .lvbrowser file, but this file does not exist anywhere on my system ( i have searched everywhere).  When i first selected help it asked me to select a browser ( i chose firefox), but now when i click help nothing happens...
    Any ideas?

    Hi,
    It sounds like the help file may not have been installed whenever you installed LabVIEW. I would try reinstalling and be sure to install any help file listed in the command prompts.
    -Erik S
    Applications Engineer
    National Instruments

  • XYGraph Cursor legend bug instantly crashes LabView 2012

    Hi!
    I am just facing a very annoying bug.
    Please find my example VI attached, I would like to know wheather you can confirm the bug? Run the VI if you wish to see some curve (actually the bug appears even if you do not put any data on the graph, if you do, just the same) and after that try to click on the cursor legend vertical scrollbar to scroll up or down to see the cursor names.
    It instantly crashes my LabView 2012 Full version:  12.0.1f2 (32-bit). This XYGraph always crashes LabView... I cannot go on with my project, now I will just try to bypass the error, I will try to delete the cursors, and add them again...
    Anyhow, very strange and annoying behaviour...
    Anyone could repeat the same bug?
    Thanks for support!
    Solved!
    Go to Solution.
    Attachments:
    XYGraph_bug_test1.vi ‏149 KB

    hello,
    please find attached my example VI, where I would like to programmatically set the label position of a cursor. Why my code does create at every run a new cursor with the same name?
    thanks!
    Attachments:
    cursor_offset_label_via_propertynode.vi ‏12 KB

  • LabVIEW 2012 SP1, Can't get correct mechanical action on boolean buttons

    I am trying to use boolean buttons and events to programatically change the properties of a graph.  I basically want to click a button on the FP, and have the graph change the desired property.  All the property changing is fine, but I am really struggling with the mechanical action of the buttons.
    I'll preface this by apologizing that I cannot post my code, as the computers with LV installed are isolated. My code is basically OK buttons, a while loop, and an event structure with a value change event for each button.
    I want the user to click and release the button. After the click and release, I want the button to be in the same state it started, and I want the value change event to only trigger once.  Sounds to me like I want the Latch When Released mechanical action.  The problem is that this isn't working.  I cannot create buttons that behave like this.  None of the 6 mechanical actions exhibit the desired behavior.
    To make matters worse, I have two OK buttons both set to Latch when released.  Both buttons are True before the click. One button behaves as intended (button is true again after the click and release) and the other button doesn't switch back.  I tried to copy the correctly working button, but still the copied button does not work the same as the original.  Both buttons fire a single value change event, dispite behaving differently.
    To answer the question "Where did I get the working button from?"  A while back I made a simple button test vi that tested all 6 of the mechanical actions and kept track of how many times they fired a value change event for a single click.  My buttons worked when I made this vi...eventually, i remember having trouble with this back then too.  The results of that trouble had me using switch until released buttons with mouse down events for a long time, until I got the button test VI working properly and learned how buttons actually work. But now buttons are being funny again.  I tried to copy working Latch when released button into my current program, but for some reason only one of the two copied buttons work as intended, despite them being copies of the same button.
    Is there some bug in LV2012 SP1 (64 bit) where mechanical actions don't work consistently?  Am I just being dumb?  I'm sorry I can't post the code.  I have this issue on both Windows 7 and Linux.
    A bit more info, as I wanted to make sure I tried eveyrthing before posting.  I tried to make a new button test VI.  The old one still works, but I cannot get the buttons in the new button test vi to behave the same as in the old one I made.  In the new one, Latch when pressed behaves the same as switch when pressed, and latch when relased behaves the same as switch when released.  Switch until released and latch until released behave slightly differently.  They both fire two value change events, but SuR actually switches twice (there and back again), where LuR just switches state once but still fires two value change events anyway.  I have checked to make sure the mechanical actions are set properly at least a dozen times.
    Pretty confused over here.  My old button test vi works as I expect it to, and the Latch when released button works like I want, but I can't for the life of me reproduce it.

    To Bob_Schor
    I realize the folly of mouse down events, and I'm trying to move away from them.  I originally started using them because I couldn't get the desired button behavior out of value change events and any other mechanical action.
    I use LabVIEW 64 bit because I was hitting the RAM limits with the 32 bit version.  I hit the limit when I try to plot a great deal of data in 3D, which I do fairly often. I get away with this because I don't interface with any equipment or use any of the specialized modules, but maybe I should consider only using 64 when it's absolutely necesary and get 32 bit on there as well.  But I have the same issue on Linux, which only has a 32 bit labview version (still 2012 SP1)
    There is only one event structure in the program.  I have two buttons because I'm just using them to fire two separate events.  My current situation is that I am plotting 9 plots on a single graph.  One of these buttons is a "check all" button for the visibility check boxes.  I click the check all button, and all 9 plots become visible.  The other button is an "Uncheck all" button, which does the opposite.
    That's for my current program.  I also have a button test vi which has 6 boolean buttons, each set to a different mechanical action.  A single event stucture in a while loop has a value change event for each button.  I made this so that I could see for myself how the buttons worked (i.e. I see that the switch when released mechanical action produced two value change events.).  I have an old version of this program which works as I expect it to.  This morning I tried to remake it (it's very simple) and it does not behave the same, despite the block diagram being pretty much identical.  I described the differences in the OP.
    I can reporduce the behavior on a second computer that is restricted.  Which is 32 bit labview for Linux. I don't have an unrestricted machine with LabVIEW installed.  If I did, I would have tried to rebuild my button test VI  (again) to see if it works.
    At it's most basic, create an OK button on the FP and set in the True state.  It defaults to the Latch when released mechanical action.  Throw an event structure in a while loop.  Give the ES a value change event for the button.  In this even just increment some counter to indicate how many times the value change has been triggered.  I did this using a shift register.  Run it.  For me, when I click the Latch when released button it fires one value change event and doesn't reset to true when after the click.  I can change the mechanical action of the button, and none of the 6 give me what I want.
    So my issue just boils down to Latch when released not behaving properly.
    In my original button test vi (which was this with 5 more buttons and 5 more value change events in the ES), the latch when released button DOES reset to true after my click.  Copy and pasting this button creates a new button which does not behave the same way, despite still being set to latch when released.
    My problem is not so much with the events, but the behavior of the button.  Am I correct that Latch when released is what I want?  A single click, and the button fires one VC event and returns to the same state before the click?

  • LabVIEW 2012 SP1?

    Is there a plan when or if LV2012 SP1 should be released?
    Labview 2012 f5patch was released on 2013-01-05.
    Labview 2013Beta was announced for one week.
    Labview 2011 SP1 was released in December 2011.
    I expected 2012SP1 in December2012 or January 2013. We are now February 2013 and I cannot find it...
    Will 2012SP be skipped?

    I had an application working fine withe LV 8.5 FDS
    I migrated to LV 2012  PDS yesteardy in since that time at any restart of the PC , when I lanch my appplication  I get  a message of the installer and then an error otf the MIcrosoft Installer
    As you can see in the attached word file, the window event log tell that cwdss.exe.manifest does not exist
    It is the case , but I llok to another thread of ni.com called
    Why Does DataSocket Server Fail to Launch After Installing LabVIEW 2012? it is told to supress this file ....
    So What should I do ?
    For information on  other PC where no Pb occur , the cwdss.exe.manifest does  exist
    Attachments:
    Journal Evenement associé au PB Msg Installer.doc ‏161 KB

  • Labview 2012 SP1 f5 halting on Win 6 x64

    I am using the latest Labview 2012 x64 SP1 with f5 update and am finding that it halts and forces me to close labview and restart. Anyone else having the issue or knows what might be causing the issue?

    I regularly get 2012 SP1 f5 shut-downs but these tend to only occur when I am working on a project with a nested LVOOP hierachy and I'm making changes to that hierachy.
    I don't know what activities you are doing that cause the re-start but it might help to know what you are working on when it happens; or post your LV internal error report to NI (I assume NIER is doing it's job).

  • Find Control in Event Structure doesn't show the object when it is not in the frontmost Tab page [Bug Report, LabVIEW 2012]

    When you are looking for the control/indicator handled by a case in the Event structure, you can use the contextual menu item "Find Control" (doesn't distinguish between control and indicator, BTW).
    The result is that the control/indicator is highlighted on the FP. The problem is, if that control is in a Tab and specifically in a page of that Tab that happens to not be the frontmost, the only thing you'll see is marching ants, but no control:
    <=========== the wrong TAB page was shown. LV did not bother to switch to the relevant one....
    In other words, "Find Control" in the Event Structure doesn't switch the tab to the owning page. This is contrary to what happens if you right-click, say, the terminal of this control: the FP will switch to the owning Tab page.
    I'd call this a bug and this is definitely an annoyance (which most likely has been around since the creation of the Event Structure).

    I did not. Is there any better chance for it to be caught there by a NI eye than it is in the LV forum? I though these threads were deemed to gather bugs/features that had been already acknowledged by NI with a CAR number.
    I (and others!) wished there was something like this: http://bugs.sun.com/ or http://bugs.python.org/ for LabVIEW...
    I am just coming back from a short conference of scientists who quite uninamously ended up with the conclusion that LabVIEW was to be disregarded as a lab development environment because of maintenance problems (which could have been argued for any language in my opinion, although I think they meant spaghetti diagrams are the natural tendency of students who could not care less as they are not going graduate because of their LV skills or lack thereof), but I guess I could have added my grain of salt and added the complete opacity on bug and feature handling by NI.

  • LabVIEW 2012 SP1 takes ages to install

    Just wondering - why on earth should the SP1 patch to LV2012 take 45 minutes to install on a 2.8 Ghz multi core PC with 8 GB ram ?
    I get a feeling that I am saddled with quite a massive amount of unwanted universal stuff - like the zillion printer drivers that install with a Windows OS - just so that it can be called plug and play !
    Gone are the days when programs used to come in minimum foot print code ;-)
    Raghunathan
    LV2012 to Automate Hydraulic Test rigs.

    Raghunathan wrote:
    Just wondering - why on earth should the SP1 patch to LV2012 take 45 minutes to install on a 2.8 Ghz multi core PC with 8 GB ram ?
    I get a feeling that I am saddled with quite a massive amount of unwanted universal stuff - like the zillion printer drivers that install with a Windows OS - just so that it can be called plug and play !
    Gone are the days when programs used to come in minimum foot print code ;-)
    I'm sure this post was just a rant to vent some frustration, but I'm going to take it at face value, hoping this doesn't annoy you.
    LabVIEW has always taken a long time to install.  I remember having the task of installing the new fangled LabVIEW 6.1 on our machine and mass compile our reuse library.  I was told it would likely take a couple days.  I was pleased when I did it in one day.  The install took many hours and I think it was done around 2 or 3 in the afternoon.  This was without any toolkits or add-ons just LabVIEW and the Device Drivers.  Then I set it up to mass compile our library and I'm unsure how long into the night it took but it was done by morning.
    I've gotten good a streamlining the process of setting up a development environment.  When a new set of developer suite DVDs come in I combine them so it doesn't prompt me to swap disks during the install.  I do still get prompted for the Device Drivers after the Developer Suite is installed.  Then I have a VI Package Configuration in Package Manager which install all internal/external reuse, add quick drop shortcuts, templates, LabVIEW.INI settings, and other settings with just a single prompt at the start.
    It isn't fast by any means, but I'd guess I can go from a fresh Window image to having a PC setup, including a SVN repository checkout in 3 hours or so.
    Oh but I do appreciate a minimal footprint program.  I heard Doom was originally written in assembly.  And that the full binary of Doom 1 takes up less space on disk, than a save file of Doom 3.  Also .kkrieger blew my mind when I first saw it in 2004.
    Unofficial Forum Rules and Guidelines - Hooovahh - LabVIEW Overlord
    If 10 out of 10 experts in any field say something is bad, you should probably take their opinion seriously.

  • Bug Fix: SSMS 2012 SP1 CU7 generates deprecated Execute code

    Please correct a problem with code that was likely written many years ago.
    I tried to find source of the Deprecated Feature error in my code unsuccessfully, when I finally realized that the source of the problem is in code that SSMS generated.
    SQL Azure will not run this code generated in SSMS when you right-click a stored procedure, and select "Execute Stored Procedure". It will generate the following:
    USE [MyDB]
    GO
    DECLARE @return_value int
    EXEC @return_value = [dbo].[usp__MyRoutine]
    SELECT 'Return Value' = @return_value
    GO
    When you execute this, SQL Azure returns:
    Error #: 40512 — Deprecated feature ‘String literals as column aliases’ is not supported in this version of SQL Server.
    Please have SSMS always, regardless of Azure or Local database, modify the output line containing the SELECT to read as follows:
    SELECT @return_value AS [Return Value]
    Microsoft has solved bigger challenges than this, please ensure that it is corrected in the next bug fix / new version.

    Hello,
    The error occurs in the usage in this string: SELECT 'Return Value' = @return_value.
    This syntax is no longer supported, please try to use 'AS name' instead. For example,
    SELECT @return_value AS [Return Value]
    Regards,
    Fanny Liu
    If you have any feedback on our support, please click here.
    Fanny Liu
    TechNet Community Support

  • Bug report: on LabVIEW 2011 SP1 and Windows 8 'Open URL in default browser.vi'

    Dear colleagues,
    Here is a bug report.
    Culprit: 'Open URL in default browser.vi'.
    System: Windows 8, Professional. LabVIEW 2011 SP1.
    Abnormal behaviour and steps to reproduce:
    Above mentioned VI doesn't work when LabVIEW was started with administrator privilegies. And it works as expected when LabVIEW running in normal (non-administrator) mode. 
    Looking forward to see this fixed.
    Best regards,
    Igor Titov.
    CLD.
    =========================
    Igor Titov, CLA
    WebPager - put LabVIEW front panels into the web page
    Labicom.net

    Hi Igor,
    Unfortunately LabVIEW 2011 SP1 does not support Windows 8. I tested this behavior with LabVIEW 2012 SP1 on Windows 8 and everything worked correctly. 
    Regards,
    Jeff Peacock 
    Product Support Engineer | LabVIEW R&D | National Instruments 

Maybe you are looking for