Jump to content

Phillip Brooks

Members
  • Posts

    899
  • Joined

  • Last visited

  • Days Won

    50

Everything posted by Phillip Brooks

  1. There is an example of this on the NI web site http://zone.ni.com/devzone/cda/tut/p/id/5321
  2. Bump! Just adding this post to get my question to appear in the RSS Feed where it might get noticed...
  3. QUOTE (Michael_Aivaliotis @ Oct 2 2008, 03:25 AM) Should these forums show up in the LAVA RSS feed? I don't see my post to the TestStand forum, and didn't notice the SCC posts (quick visual scan).
  4. Background: I'm upgrading a test system based on LabVIEW 7.0 and TestStand 3.0 to LV 8.6 and TS 4.1. Much of the customization to TestStand was originally done in TestStand 1.0 and simply upgraded to 3.0 about 4 years ago. I'm currently updating the FrontEnd Callbacks, specifically a Login / Logout customization that gets user account information from an MS Access database. The sequence and VIs have been updated and work. The problem is that the implimentation of the original login customizations and the behavior of TestStand 4.1 result in the 'dialogs' not being brought to the foreground. Define 'dialog'. In the original 1.0 TestStand implimentation, the dialog step called a wrapper VI that included the standard Sequence Contenxt, Input Buffer string and Test Data Cluster. The wrapper VI passed the Input Buffer to the actual Dialog SubVI, and used the Sequence Context and Dialog SubVI outputs to set TestStand variables. This worked OK in TestStand 3.0, but not in TestStand 4.1. When I start TestStand 4.1, it loads LabVIEW 8.6 and displays the dialog Login subvi properly. If I select Logout and then Login from the TestStand pulldown menus, I logout, but after selecting Login I have to use Alt+Tab to bring LabVIEW to the foreground and enter my user name and password. NI suggested using the TestStand - Start Modal Dialog and Stop Modal Dialog calls to bring the dialog to the front every time. I don't pass the Sequence Context into the actual Dialog VI, so now the wrapper VI AND the dialog SubVI are shown. This is marginally OK because the developers aren't concerned with seeing the wrapper's front panel. Unfortunately, the wrapper VI sticks out like a sore thumb when the LV RTOI is used. I could modify the dialog SubVI to pass in the Sequence Context and use the Modal VIs to bring just that forward, but the wrapper is sort of a waste at this point. There are numerous levels of dialogs throughout our test code that use the same technique (TestStand VI call to a wrapper VI that uses a dialog style SubVI ) I have to modify the TestStand sequence to call the actual dialog VI or modify the dialog SubVI to accept data passed in through a seemingly archaic method. I'm leaning towards changing the TestStand sequence to call the actual dialog directly. Many of the dialogs are also very old (LV 5.1.1) and use polling which is also a bit dated at this point. I'm probably going to be modifying both TestStand and LabVIEW code for each dialog type step. The plan has been to minimize code changes and just upgrade the tools. Much of this code has been running since ~2000 and is well tested. What the heck is my question again? Oh yeah... How do you configure and call your TestStand Dialog VIs? Do you have any suggestions or experience with respect to TestStand and VI dialogs that you can share?
  5. QUOTE (alfa @ Oct 4 2008, 03:12 AM) I think alfa suffers from one or more of the following: Martyr complex Superiority complex Malignant narcissism
  6. QUOTE (Jim Kring @ Oct 1 2008, 02:19 AM) Seems that this concept is a popular one; http://forums.ni.com/ni/board/message?board.id=130&thread.id=5309&jump=true' target="_blank">Laura has announced new features on the NI boards that replace the stars. You now give Kudos, and the original poster can select a response as the best answer...
  7. I would look at the NI GPIB+ products (I have the NI PCI-GPIB+). The data sheet indicates that you can configure the board to be non intrusive (listener only; does not participate as a bus device). I've never used it in this way, but the documentation states it can be done, so it must be true
  8. QUOTE (Pollux @ Sep 20 2008, 04:01 AM) You use Shift & Ctrl with sticky keys so that you can still use quick drop!
  9. QUOTE (alfa @ Sep 19 2008, 03:41 AM) SRI? Are you referring to Serviciul Român de Informaţii? At first I thought you were referring to Stanford Research Institute.
  10. QUOTE (PaulG. @ Sep 17 2008, 01:14 PM) Maybe so, but many of THEIR (NIs) customers ARE engineers I'm lucky that most of my projects have been instrumentation and data processing related; I've tinkered with XControls to help the front-end guys, but something (I don't know what) seems to be missing with them...
  11. I remembered this post after reading your question. NI apparently was experimenting with MDI/TDI at one point, but this post is from four years ago
  12. QUOTE (Aristos Queue @ Sep 17 2008, 12:54 AM) Does this mean that NI will finally replace those useless palettes with Quick Drop and the "LabVIEW Ribbon" (aka the garrote)? Will 'Spoolie' will finally make his debut? Where do I renew my SSP?! :laugh:
  13. QUOTE (shoneill @ Sep 17 2008, 04:04 AM) There is a http://forums.ni.com/ni/board/message?board.id=170&thread.id=319502' target="_blank">pioneer beta program for 64 bit LabVIEW that you can sign up for...
  14. I've confirmed this behavior in LV 7.0 and 8.6. I tried using some of the other structures (flat sequence and timed loop) and they seem to behave like the 'For Loop'. The conditional structure has the same problem. It seems that the ability of the scan from string function to see outside of a Boolean controlled structure is limited or somehow different. Don't know if it's a bug (present in 7.0 until today) but it's not necessarily a behavior that one would expect :thumbdown: Download File:post-949-1221563501.vi (LV 8.6) ( NOTE: A search of the dark side indicates that this is a known behavior, and NI does not necessarily consider it a bug. You could report it if it bothers you... )
  15. QUOTE (Jim Kring @ Sep 11 2008, 12:16 AM) AND VI Analyzer!
  16. I'll bet this company found our forums using sophisticated search queries such as "search engine sucks", then found one of these posts... Thanks Norm! :laugh:
  17. QUOTE (Yair @ Sep 2 2008, 12:16 PM) You may be sad when you switch to 8.5 / 8.6 LV 8.6 Release Notes, Page 14: Opening LLBs in LabVIEW The Enable Windows Explorer for LLB files option on the Environment page of the Options dialog box no longer exists. LabVIEW opens LLBs in the LLB Manager window. Refer to the National Instruments Web site at ni.com/info and enter the info code http://digital.ni.com/public.nsf/websearch/8209AD1184FF4851862572270054427A?OpenDocument' target="_blank">exvfc5 for more information about opening LLBs.
  18. QUOTE (Giseli Ramos @ Sep 1 2008, 04:13 PM) This may be and endian problem, http://forums.lavag.org/-t1993.html&view=findpost&p=6721' target="_blank">see here...
  19. QUOTE (gmart @ Aug 28 2008, 04:37 PM) I suspect it will be noted in the release notes. It would read similar to Patient: "Doctor, it hurts when I do this" Doctor: "Don't DO THAT!" Bud-dum-tish!
  20. Submit your current LabVIEW.INI and your suggestions on how to improve the Tools>>Options dialog in LabVIEW. http://forums.ni.com/ni/board/message?boar...age.id=405#M405
  21. QUOTE (yen @ Oct 8 2007, 03:56 PM) I just read the Noel's Feature Brainstorming entry here, submitted my INI file and suggested that Darren's example VI be incorporated into the Options Dialog. I also went looking in the WIKI for the defaultConPane setting and couldn't find it (As Norm often says "search sucks"). I added defaultConPane to the Misc options page Let's see what happens...
  22. QUOTE (Yair @ Aug 28 2008, 12:30 PM) Funny, when I tried to replace with a flat sequence, LabVIEW 8.6 crashed!?!
  23. QUOTE (normandinf @ Aug 19 2008, 04:27 PM) Or in the case of LabVIEW prospects, the NI Forums or most importantly, LAVA! (As Michael already indicated). I hope I'm not in trouble. Maybe I should stay away from the lounge and BreakPoint from now on...
  24. Paul, based on your avatar and numerous feline references, I just assumed you listen exclusively to "Cat" Stevens [/url]
  25. QUOTE (LV_FPGA_SE @ Aug 12 2008, 12:15 PM) Did they change the rules? I thought NI employees couldn't take the exams...
×
×
  • Create New...

Important Information

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