Jump to content

george seifert

  • Posts

  • Joined

  • Last visited

  • Days Won


Everything posted by george seifert

  1. If I pass a reference to a subVI and close it there is it really closed or do I need to close it in the calling VI? George
  2. Irene's links no longer work. How can I get to them? It looks like information I could really use. George
  3. Agreed. I'm on the SSP plan, but I think it stinks to charge for bug fixes. And are we supposed to be impressed that it took 3000 hours to fix the bugs? George
  4. I was getting a weird error about a null window from an executable that worked fine under LV2009. The VI that caused the problem was setup with the subVI node setup in my main VI to load when called and then close when done. I ended up having to specifically include the VI in the executable build. I never had to do that before. Something to watch out for in your builds. George
  5. No to the JKI RCF and I don't really understand the second part of the question. I'm not doing anything funny with VIs like dynamic launching or subpanels. George
  6. Well yeah I made changes to the code, but I think the point is that the code runs fine. The only thing the error says is to make sure the VI isn't broken and that it runs. Let's see, nothing too fancy in the top-level VI, no classes or Mathscript. I do use some DAQmx VIs. I built an executable in another project that uses similar DAQ calls. George
  7. I had built this VI several times with LV 2009. Now since I loaded Service Pack 1 I'm getting an error when I build an executable that says this: The VI is broken. Open the VI in LabVIEW and fix the errors. Error 1003 occurred at AB_Application.lvclass:Open_Top_Level_VIs.vi -> AB_Build.lvclass:Build.vi -> AB_Application.lvclass:Build.vi -> AB_EXE.lvclass:Build.vi -> AB_Build.lvclass:Build_from_Wizard.vi -> AB_UI_Frmwk_Build.lvclass:Build.vi -> AB_UI_FRAMEWORK.vi -> AB_Item_OnDoProperties.vi -> AB_Item_OnDoProperties.vi.ProxyCaller Possible reason(s): LabVIEW: The VI is not executable. Most likely the VI is broken or one of its subVIs cannot be located. Select File>>Open to open the VI and then verify that you are able to run it. Well my VI isn't broken and it runs fine in the development system. I've shut down and restarted LV with no luck. I can't see anything odd in the project. Any ideas? I just know NI is going to tell me to rebuild the project if I call them. BTW, I am able to build other executables. <br><br>George<br><br>PS. I just rebuilt the Exe builder with no luck.<br>
  8. The last test I did was on a PC with exactly the same monitor. All the settings I could find were the same. It's done the same thing on different monitors too. George
  9. Interesting. Thanks. I think there's something screwy with my setup, but danged if I can figure out what it is. George
  10. I double checked all the settings on both computers and they're exactly the same. I've attached a Word doc that shows how the screens differ on a little example screen. I also included the VI in case anybody would care to load it and see if it looks right on their screen. font test.doc font test.vi George
  11. Thanks, but I don't think that's it. I don't even have that entry in my ini file. Also it happens when I build an exe and use it on another PC. George
  12. Since I switched to LV 2009 the controls on my front panel display differently on PCs other than mine. For instance, in a text box the character spacing is different. The system font size and the display settings are exactly the same. Also all the alignments for text boxes on my block diagram are off since switching to 2009. I'm not sure where to start looking for the source of this issue. Any ideas? George
  13. I've been rooting around awhile and haven't found an answer yet, so it's time to ask the experts. I want to trigger a PXI-4071 DMM to start a waveform acquisition when my PXI-6254 DAQ acquisition starts from an analog trigger. I assume that maybe I have to tell the 6254 to output the trigger signal to one of the PXI trigger lines on the PXI bus. From there it looks like it straightforward to tell the DMM to use that trigger line as the source of the trigger. I just don't know how the have the DAQ tell the trigger line to activate when it starts acquiring due to an analog trigger. Any hints would be welcome. Thanks, George
  14. The best place to start is with the examples that ship with LV. You'll probably find one that does something very similar to what you want. If you don't find exactly what you want you're sure to get some hints about how to get started. George
  15. Has anyone created an envelope detector? I have a 300 KHz signal that will be on for varying amounts of time (20 to 40 msec) with a gap between the pulses of about 10 msec. I'd need to figure out the actual on time of the signal. I suppose I could use a peak detector to find all the peaks in the burst and then determine when the peaks drop out, but that just seems kind of clumsy. Any better ideas? George
  16. This has happened twice now in the last few days. I double click on a subVI in my app or in the Project Explorer and I get the following error: Unable to display the front panel of the VI. The VI's front panel may have been removed. I just had the subVI open a bit ago and now it can't find the front panel. What's going on? George<br><br>PS<br>I just closed LV and reopened and the front panel was back. Kind of spooky.<br>
  17. Yes, it is. Thanks. I thought I tried histogram mode, but now I'm not sure. I wonder why the auto mode doesn't pick the right method. George
  18. Has anybody else had trouble with the Pulse Measurements VI? See the attached VI to show that it clearly gives the wrong answer. I know I don't have a really well defined pulse, but it's not that bad. Seems like it should be able to find the rise and fall of each pulse. Pulse measurement VI problem.vi George
  19. What happened to the LV option to make a new connector required? It was there in 8.6.1, but I can't find it in 2009. George
  20. I ended up using the GetArrayInfo VI to get the data for one element of the array. From there I got type descriptor string from the Variant to Flattened String. I fed the type descriptor to the Get Type Code from I16 Array VI which gave me the element type that I wanted. George
  21. Yeah, I think ShaunR got it. The GetTypeInfo VI doesn't return the Info data within the variant that I wanted. It returns the overall type of data within the variant - like Enum or Array. George
  22. How can I get the 'Info' data contained in a variant? I want to get the variable type of the elements in an array. For example, I used the GetArrayInfo VI to get the following info from my array and want to extract the U32 info contained in it. George
  23. That's what I think, but not reality for me. It often takes at least 10 minutes. George
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.