Bug? LabVIEW-2009: Boolean wire missing some dots

I opened a VI from someone asking a question on this forum and noticed some missing dots on two boolean wires.
This was opened using LV 2009.  It's an Evaluation installation (in case someone is wondering about specifics).
I minimized and maximized the block diagram and the dots were okay.
I don't know if this was already reported.
R
Message Edited by Ray.R on 10-08-2009 06:06 PM
Attachments:
missingLine.PNG ‏45 KB

Ray.R wrote:
LOL!  Imagine all the people that would need help if we came up with wireless wires... 
Of course we could also ask for underground wires that could be threaded below the diagram for some busy areas where they are not needed.
Message Edited by altenbach on 10-09-2009 02:07 PM
LabVIEW Champion . Do more with less code and in less time .
Attachments:
WireTunnel.png ‏2 KB

Similar Messages

  • BUG: LabView 2009 WebServer crash

    Here is a simple VI containing no controls, functions or libraries in LabView 2009 f3.
    WebServer
    settings are default. After Tools->Web Publishing Tool operation
    from other PC we are connecting to this panel (IE6 for example) and
    putting a finger to F5-button not raising it.
    Web page with the VI is refreshing continiously.
    There are 3 results.
    1. In DevEnv: LabView die.
    2. In DevEnv: Need to restart LabView so WebServer reloads and connection restores.
    3. In App.exe: die
    4. In App.exe: LabView interpreter loose some while-cycles in case they exist but connection stored.
    5. In App.exe: connection lost but the application working good.

    Link to original post
    Justin Parker
    National Instruments
    Product Support Engineer

  • Partial clean up needs wires (BUG LabVIEW 2009)

    The new partial clean up feature of LabVIEW has a little glitch, it needs a wire to be selected to actually perform a clean up.
    For isntance the following VI:
    Where I have selected the top and bottom primitives, when I hit the LabVIEW clean up button, the selection will not be cleaned up.
    Ton
    Free Code Capture Tool! Version 2.1.3 with comments, web-upload, back-save and snippets!
    Nederlandse LabVIEW user groep www.lvug.nl
    My LabVIEW Ideas
    LabVIEW, programming like it should be!

    altenbach wrote:
    Looks pretty clean to me. What do you expect it to do?
    I expect LabVIEW to align the code.
    I don't have LabVIEW currently active, but if you add a wire between two of the nodes but not select the wire the clean up will be a no-op as well.
    Only with a wire selection it will actually clean up. 
    TST:
    I have seen no difference between the toolbar button and the 'cleanup' invoke node.
    Ton
    Free Code Capture Tool! Version 2.1.3 with comments, web-upload, back-save and snippets!
    Nederlandse LabVIEW user groep www.lvug.nl
    My LabVIEW Ideas
    LabVIEW, programming like it should be!

  • In block diagram connecting wire getting blur while saving the VI in LabVIEW 2009

    Hello,
    I am using Labview 2009, And while I am saving  a simple VI connecting wires are getting blurry. What could be the problem?? Is it affect my program while running?
    Solved!
    Go to Solution.

    Go into Tools>>Options, select the Block Diagram page and find the section called Constant Folding. If the CF for wires check box is checked, then this is most likely the reason. You can uncheck the check box and it won't affect the way your code runs.
    If this isn't the case, you should upload an image of what it looks like.
    Try to take over the world!

  • Download Presenter trial in your website but when I published object scorm in zip file miss some important file such as ismmanifest.xml. In fact Moodle upload is wrong! Is it a bug or what? Thank you.

    Download Presenter trial in your website but when I published object scorm in zip file miss some important file such as ismmanifest.xml. In fact Moodle upload is wrong! Is it a bug or what? Thank you.

    You can publish Adobe Presenter Projects to your Moodle LMS (this will work for many other LMS’ too.)Please follow the steps as mentioned in the blog linked below.
    https://blogs.adobe.com/presenter/2013/08/step-by-step-how-do-i-publish-my-presenter-cours e-to-my-learning-management-system.html#more-6260
    Regards,
    Rajeev.

  • Translated wire message missing some values

    Hi,
    I am enqueuing an EDIFACT xml to B2B out queue (IP_OUT_QUEUE) which is getting converted to wire message and delivered correctly. But the translated wire message is missing some values:
    UNH segment of EDIFACT xml:
    <Segment-UNH>
    <Element-0062>1</Element-0062>
    <Composite-S009>
    <Element-0065>ORDERS</Element-0065>
    <Element-0052>D</Element-0052>
    <Element-0054>07B</Element-0054>
    <Element-0051>UN</Element-0051>
    </Composite-S009>
    </Segment-UNH>
    Starting part of wire message:
    UNA:+.? 'UNB+UNOB:1+ + +100407:2354+1003'UNG+ORDERS+ + +100407:2354+1003+UN+D:07B'UNH+1+ORDERS'BGM+105:::?' ?'+GSIAP.WORLD?:oracle.apps.po.event.xm::?'
    In wire message, 'UNH+1+ORDERS' - this portion is not having values of Element-0052, Element-0054 and Element-0051. Why are this values ('D','07B','UN') missing in the translated wire message?
    How can I make them appear in wire message?
    Appreciate your help.
    Thanks in Advance,
    Siddhesh

    Hi Siddhesh,
    Check your ecs file. Possibly you have not defined these params in ecs file.
    Enable the validation then you will come to know exact issue.
    Rgds,
    Nitesh Jain

  • 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

  • Quanser DC Motor Control Trainer missing VI's for labview 2009

    Hi my name is phillip, a student developer working with labview 2009 and the Quanser DC Motor Control trainer with ELVIS II. I have failed to run the VI for speed control, it appears to be broken and says four sub-vi's are missing and they are "Intergrator.VI," "Integrator (DBL).VI," "Transfer Function.VI," "and "Transfer Function (DBL).VI.". I happen to have installed the control design and simulation toolkit but this has not solved the problem. Please help!!!!

    Hi Phillk, I have the exact same problem with the missing VIs for the Quanser DC motor control with the NIELVIS also for Labview 2009.
    Can you please tell me where I can find these VIs? Can you send them to me if it is possible?
    I would really appreciate it, 
    I need the Transfer Function.vi,  Transfer Function (DBL).vi and the integrators too.
    Thank you, 
    Carlos M. Rodriguez  
    [email protected] 

  • Potential Bug with LabVIEW 2009, Report Generation Toolkit, and MS Office 2003

    We have discovered an issue with the above listed software.  Specifically this pertains to Print Report.vi in the Report Gen palette.  Basically, we have discovered that with Office 2003 installed the VI will error out.  We've been using it in an executable, and the executable physically fails (and asks us to report an error to Microsoft).  With Office 2007 we don't have a problem.  We've tried building the examples into executables, and those work because they are printing HTML reports.
    Also, we have converted back to LabVIEW 8.6 and rebuilt the executable and installed and it works perfectly.  Its on the combination of LabVIEW 2009 and Office 2003 that seems to fail.

    yeah, we had seen that, and been told about it by another user.  we tried, to no avail.  we still have ended up having to migrate back to 8.6.1 to get the executable to run properly.

  • Favor to ask : can you open this labview 2009 Vi and save it for me in a Labview 8.6 readable vi ?

    Hi guys, 
    I have a favor to ask : May somebody would be nice enough to open this Labview 2009 VI and save it in a Labview 8.6 readable VI  ? You'll probably have some missing blocks cause I use specials ones but I don't want to have to re-make all the VI.
    Thanks you very much
    G.
    Solved!
    Go to Solution.
    Attachments:
    Control3.vi ‏29 KB

    notimperial wrote:
    Probably not the right place to do this, but could someone onpen this in labview 2010 and save it in a format compatible with labview 2009?
    Thank you in advance
    You are right we have a thread for this here.
    http://forums.ni.com/t5/LabVIEW/Downconvert-VI-Req​uests/m-p/1067229
    Here is your vi please use the downconvert thread next time.
    Tim
    Johnson Controls
    Holland Michigan
    Attachments:
    WFMreaderIII.vi ‏53 KB

  • Migrating large project from DSC 7.1 to LabView 2009 Shared Variables ... What's the next step after recreating my variables?

    I am in the process of migrating a large distributed (multi-workstation) automation system from the LabVIEW 7.11 DSCEngine on Windows XP to the LabVIEW 2009 Shared Variable Engine on Windows 7.
    I have about 600 tags which represent data or IO states in a series of Opto22 instruments, accessible via their OptoOPCServer. There are another 150 memory tags which are used so the multiple workstations can trade requests and status information to coordinate motion and process sequencing.  Only one workstation may be allowed to run the Opto22 server, because otherwise the Opto22 instruments are overwhelmed by the multiple communications requests; for simplicity, I'll refer to that workstation as the Opto22 gateway.
    The LabVIEW 2009 migration tool was unable to properly migrate the Opto22 tags, but with some help from NI support (thank you, Jared!) and many days of pointing and clicking, I have successfully created a bound shared-variable library connecting to all the necessary data and IO.  I've also created shared variables corresponding to the memory tags. All the variables have been deployed.
    So far, so good. After much fighting with Windows 7 network location settings,  I can open the Distributed System Manager on a second W7/LV2009 machine (I'll refer to it as the "remote" machine henceforth) and see the processes and all those variables on the Opto22 gateway workstation. I've also created a few variables on the remote workstation and confirmed that I can see them from the gateway workstation.
    Now I need to be able to use (both read and write) the variables in VIs running on the remote workstation machine. (And by extension, on more remote workstations as I do the upgrade/migration).
    I have succeeded in reading and writing them by creating a tag reader pointed at the URL for the process on the Opto22 gateway. I can see a way I could replace the old DSC tag reads and writes in my applications using this technique, but is this the right way to do this? Is this actually using the Shared Variable Engine, or is it actually using the DataSocket? I know for a fact that attempting to manipulate ~800 items via Datasocket will bog down the systems.
    I had the impression that I should be able to create shared variables in my project on the remote workstation that link to those on the Opto22 gateway workstation. When, however, I try to browse to find the processes on that workstation, I get an error saying that isn't possible.
    Am I on the right track with the tag reader? If not, is there some basic step I'm missing in trying to access the shared variables I created on the gateway workstation?
    Any advice will be greatly appreciated.
    Kevin
    Kevin Roche
    Advisory Engineer/Scientist
    Spintronics and Magnetoelectronics group
    IBM Research Almaden

    I have found the answer to part of my question -- an relatively easy way to create a "remote" library of shared variables that connect to the master library on my gateway workstation.
    Export the variables from the master library as a csv file and copy that to the remote machine.
    Open the file on the remote machine (in excel or the spreadsheet app of your choice) and (for safety's sake) immediately save it with a name marking it as the remote version.
    Find the network path column (it was "U" in my file).
    replace the path for each variable (which will be either a long file path or a blank, depending on the kind of variable) with \\machine\'process name'\variable name
    where machine is the name or ip address of the master (gateway) workstation (I used the ip address to make sure it uses my dedicated automation ethernet network rather than our building-wide network)
    and process name is the name of the process with the deployed variables visible in the Distributed System Manager on the gateway machine.
    NOTE the single quotes around the process name; they are required.
    The variable name is in the first ("A") column, so in Excel, I could do this for line 2 with the formula =CONCATENATE("\\machine\'process name'\",A2)
    Once the formula worked on line 2, I could copy it into all the other lines.
    Save the CSV file.
    Import the CSV into the remote library to create the variables.
    Note: at this point, if you attempt to deploy the variables, it will fail. The aliases are not quite set properly yet.
    Open the properties for the first imported variable.
    There is probably an error message at the bottom saying the alias is invalid.
    In the alias section, you'll see it is set to "Project Variable" with the network path from step 4.
    Change the setting to "PSP URL" with the same path and the error message should disappear.
    Close the properties box, save the library, and then export the variables to a new CSV file.
    Open the new CSV file in Excel, and scroll sideways to the NetworkrojectBound field.
    You'll notice it is False for the first variable, and true for the rest. Set the field FALSE for all lines in the spreadsheet.
    Scroll sideways... you'll notice there are two new columns between NetworkrojectPath and Network:UseBinding
    The first one is NetworkingleWriter; it should already be FALSE for all lines.
    The second one is Network:URL. That needs to be set equal to the value for each line of NetworkrojectPath.
    You can accomplish this with a formula like in step 4. In Excel it was =U2 for line 2, and then cut and paste into all lines below it.
    There is a third new field, Path, which should already be set to the location of the variable library. You don't need to do anything with it.
    Save the edited CSV file.
    Go back to the remote library, and import variables from the just-edited remote library CSV file.
    Once you have imported them and the Multiple Variable Editor opens, click on done.
    You should now be able to deploy the remote variable library without error. (Make sure to open the Distributed System Manager and start the local variable engine. It took me a few failures before I realized I had to do that before attempting a deployment).
    Voila! You now have a "remote" library of shared variables that references all the shared variables on the master machine, and which should be deployable on other machines with very little difficulty.
    It actually took longer to write out the process here than to perform these steps once I figured it out.
    Kevin Roche
    Advisory Engineer/Scientist
    Spintronics and Magnetoelectronics group
    IBM Research Almaden

  • Labview 2009 32 bit not running on xp 64 bit

    Hi all,
    I tried to upgrade to LabVIEW 2009 from LabVIEW 8.6 on 64-bit windows XP machine. Following about a 2 hour removal of 8.6 and subsequent installation of LV 2009 it turns out that the device drivers are not compatible with a 64-bit machine. On launching LabVIEW 2009 (32-bit) an error box appears stating that it is corrupt or missing files and to correct this using control panel etc. I have tried this and still the same error occurs and LV refuses to start.
    All the license files are correct and the compnents are activated.
    Anyone know how to fix this? Or should I go back to 8.6 and cancel my upgrade subscription?
    Secondly, I am using a firewire camera and was informed that Ni-IMAQ legacy are no longer supported and to go to ni.com/ifo and enter legacy1394 to see how to download drivers etc for this. I end up on a page that says "not authorized".
    Any help gratefully appreciated. 
    Solved!
    Go to Solution.

    Leeser wrote:
    I agree that XP64 and LV 2009 are not compatible as I installed LV 2009 on another 32-bit machine with no problems. I was just surprised as there were no problems or issues that I came across for 8. on XP64. Ah well, a uninstallation and reinstallation lies in wait for me on Monday morning!!  
    As an aside why call it LV 2009 instead of LV 8.7 or even LV9.0...sounds reminiscent of an operating system!!
    Regards,
    Leeser
    LabVIEW 2009 is according to the internal version scheme actually equivalent to LabVIEW 9.0. Why they changed the naming? I guess marketing told them to do so. Why then? Well marketing has some funny ideas sometimes. I guess since THE software provider in this world has started to do this since about Windows 2000 someone must have thought it to be the best idea since sliced bread and decided to do it for LabVIEW too.
    Another guess is that in about 2010 there would have been something like 9.1, and 10.0 would then come out in 2011 and that sounded somehow to someone like a bad scheme so they decided to change it now. But maybe it will be forgotten and everybody returns to the old versioning at the begin of next year when 9.0.1 will come out, which would then otherwise be LV 2009.1??? Or maybe LV2009 SP1?
    It has already happened with LabVIEW 6i (iMacs, iPhones, iAnything), LabVIEW 7 Express and LabVIEW 8.20 (following 8.0.1 and marking the 20th anniversary of LabVIEW, and being internally LabVIEW 8.2). All some marketing fun or hysteria.
    Rolf Kalbermatter
    Message Edited by rolfk on 08-17-2009 11:08 AM
    Rolf Kalbermatter
    CIT Engineering Netherlands
    a division of Test & Measurement Solutions

  • Enum in a Typedef Reverts to Default (LabVIEW 2009)

    When I add additional items to a typedef'd enum, constants of that enum on some BD's revert back to the default zero index enum value. In the past (8.6.1 and previous), adding items to an enum in no way would ever change constants that were already dropped on a BD. Now, in LabVIEW 2009, when I add items, about 60-70% of the constants dropped on different block diagrams will be changed to default value.
    This happens in a "large" enum (~400 elements) that spans about 3 dozen VI's between RT and HMI block diagrams (a total of about 300 instances). This is a mature project that has never had this problem with 8.2, 8.5, 8.6, or 8.6.1...
    I cannot post an example, because in the process of stripping down the VI, the problem goes away. It is extremely repeatable in the context of the project, but I cannot repeat it on an individual VI basis.
    The current workaround is to edit the typedef'd enum while all referencing VI's are in memory. If the VI's that use the typedef are in memory, they will always properly recompile and maintain the correct constant value. However, if the VI is not in memory, and the typedef is changed, the next time the VI is opened, when it recompiles it will change the constants back to the zero index default value of the enum in only about 60-70% of VI's. Unfortunately, we cannot yet find a common thread in the VI's that recompile wrong, and the ones that recompile correctly. 
    Has anyone ever seen this problem? Suggestions?
    Best regards,
    Jack
    a.lia-user-name-link[href="/t5/user/viewprofilepage/user-id/88938"] {color: black;} a.lia-user-name-link[href="/t5/user/viewprofilepage/user-id/88938"]:after {content: '';} .jrd-sig {height: 80px; overflow: visible;} .jrd-sig-deploy {float:left; opacity:0.2;} .jrd-sig-img {float:right; opacity:0.2;} .jrd-sig-img:hover {opacity:0.8;} .jrd-sig-deploy:hover {opacity:0.8;}

    We just realized a flaw in our "workaround", as partially pointed out by Ben (he was probably typing his response as we were confirming it here). If the constant is inside of a cluster on the BD, even if it is in memory, it will null out the enum inside of the constant. Therefore, the "workaround" is to rewrite the clustered enum constants from scratch (in other words, there's no workaround). Two of us spent a decent portion of the morning finally nailing this as the source of what we thought was an unrelated bug... and that's after spending a long day yesterday trying to find a fix. Yes, we feel Ben's angst of reverting back to previous SCC editions and manually editing dozens of VIs.
    The severity of this bug is a showstopper for us. We cannot risk adding elements to an enum and consequently have referencing VIs changing their constants.
    Force compiling a VI one at a time is not an option for us. I know this bug manifests itself even after a mass compile. So, is there a way to "mass force re-compile" that we could test?
    a.lia-user-name-link[href="/t5/user/viewprofilepage/user-id/88938"] {color: black;} a.lia-user-name-link[href="/t5/user/viewprofilepage/user-id/88938"]:after {content: '';} .jrd-sig {height: 80px; overflow: visible;} .jrd-sig-deploy {float:left; opacity:0.2;} .jrd-sig-img {float:right; opacity:0.2;} .jrd-sig-img:hover {opacity:0.8;} .jrd-sig-deploy:hover {opacity:0.8;}

  • Support in LabVIEW 2009 for IMAQ legacy drivers on 64-bit windows

    Hi,
    I have been trying to use a VI that was created in LabVIEW 7.0 that makes use of IMAQ 1394 VI's in LabVIEW 2009.   When I first tried to run the VI an error told me that the VI's in question were missing, to overcome this problem I thought I should attempt to replace them with legacy VI'.  After downloading the legacy installer, I then realised that these VI's would not function on a 64-bit version of windows even though I have a 32-bit version of LabVIEW.
    I was wondering if there is an alternative way of replacing these VI's or a way of implementing the lagacy VI's?  Would it be suitable to replace the IMAQ 1394 VI's with IMAQdx VI's?
    Thanks for your time,
    Alistair Martin

    Hi Alistair,
    The following KB states that it should be possible to do what you require: http://digital.ni.com/public.nsf/allkb/3358528DF8648DC2862571F500586140?OpenDocument
    The KB also links to some development articles for upgrading and using IMAQdx to acquire from 1394 cameras.
    I hope this helps, 
    Kind Regards, 
    Applications Engineer

  • LabVIEW 2009 SP1 - Incorrect icon in connector pane palette

    In LabVIEW 2009 SP1 (I don't have 2010 yet to check it) there seems to be a minor bug in the connector pane palette.
    One of the connector patters appears twice, but when you select the second one, it shows up as the missing pattern.
    I'd post an image, but that function seems to be broken getting through my company's proxy server. So image attached (I hope).
    In LabVIEW 2009 SP1 (I don't have 2010 yet to check it) there seems to be a minor bug in the connector pane palette.
    One of the connector patterns appears twice, but when you select the second one, it shows up as the missing pattern.
    Troy
    CLDEach snowflake in an avalanche pleads not guilty. - Stanislaw J. Lec
    I haven't failed, I've found 10,000 ways that don't work - Thomas Edison
    Beware of the man who won't be bothered with details. - William Feather
    The greatest of faults is to be conscious of none. - Thomas Carlyle
    Solved!
    Go to Solution.
    Attachments:
    Connector pane.PNG ‏4 KB

    Troy K wrote:
    I guess everyone else is using "proper" connector patterns instead of these crazy non-standard ones.
    So you must be using crazy non-standard connector panes, or you would not have discovered this bug.  Right?   Actuall this is a good catch for it to go unnoticed for this long.
    - tbob
    Inventor of the WORM Global

Maybe you are looking for

  • BSP to IIS with SSO

    Hi, Is it possible to go from a BSP to a IIS with SSO? Can I use ISAPI for it or are there better solutions? And is there some documentation about it? KR Steven

  • Error occured during installation of iTunes...

    During installation of iTunes i got the following message: An error occurred during the installation of assembly "Microsoft.VC80.CRT, version="8.0.50727.4053", type="win32", publicKeyToken="1fc8b3b9a1e18e3b",processor Architecture="x86". Please refer

  • Text From Info Record

    Hi, We maintain warehouse instruction  text in Purchase Order header level on TEXT tab manully. To maintain it for each purchase order is time consuming. So we are looking for, like  it should come by default on header level. As we require it for Ven

  • Trouble upgrading in App Store

    I have been trying to upgrade iMovie and iPhoto from the App Store and I keep on receiving a message that says the following, "We could not complete your request. There was an error in the App Store. Please try again later. (4)" My computer is up to

  • Safari problem opening pages

    why the heck safari on and off have problems opening secure pages of bank sites. I previously had problems with bank.marksandspensers.com and now with bank.barclays.com, when at the same time these pages could be opened in chrome. The error displayed