Jump to content

Phillip Brooks

Members
  • Posts

    908
  • Joined

  • Last visited

  • Days Won

    53

Everything posted by Phillip Brooks

  1. QUOTE (Aristos Queue @ Dec 8 2008, 03:04 PM) Based on the content of http://forums.lavag.org/How-do-you-imagine-you-Will-recognize-God-as-a-person-t12585.html&st=30&p=55405#entry55405' target="_blank">this post, I believe that this is a bot...
  2. QUOTE (crelf @ Dec 8 2008, 07:13 PM) ... but can be measured accurately with the PXI-4071! Congratulations Norm! (And thanks for the bottle of water) I didn't care for it that much, but my kids started jumping up and down, yelling "Mindstorms NXT! Mindstorms NXT!"
  3. I have not used their drivers, but Hytek Automation might have something for you... http://www.hytekautomation.com/Products/PTPCam.html
  4. You can get access to the raw socket using vi.lib\Utility\tcp.llb\TCP Get Raw Net Object.vi I did something similar to get access to the UDP socket. I used this to increase the default OS buffer size for a UDP receiver that was overflowing the default size (8kB as I remember). http://forums.ni.com/ni/board/message?boar...ssage.id=232025 Just be aware that LabVIEW doesn't know what you're doing to the socket, so tread lightly
  5. QUOTE (Jim Kring @ Nov 29 2008, 04:32 PM) Out of curiosity, is the "::" path constant input to the Build Path function a Mac specific value? LabVIEW for Windows automatically replaces "::" with "C:\:"
  6. Under Tools, select Edit VI Library... Select the LLB of interest Select the file you want to delete and use the button on the right...
  7. QUOTE (neB @ Nov 19 2008, 02:54 PM) I make balloon animals to distract them
  8. I'm not a user of NI vision products, but I thought this announcement of a new camera using the Atom processor was interesting. It appears to include some software that can be used for metrology. If the software is included or offered cheap, I wonder if this might affect NI products or pricing? http://www.windowsfordevices.com/news/NS73...963.html?kc=rss
  9. I Googled 'labview PID example' and the first entry I got was for this LAVA post. http://forums.lavag.org/Closed-Loop-Contro...lkit-t3797.html
  10. I Googled 'labview PID example' and the first entry I got was for this LAVA post. http://forums.lavag.org/Closed-Loop-Contro...lkit-t3797.html
  11. QUOTE (Phillip Brooks @ Oct 29 2008, 07:46 AM) QUOTE (alfa @ Nov 1 2008, 04:07 AM) The Great News is that from here somebody will be CEO at Colgate! brushing your teeth - Colgate - Hah! :thumbup: Humor! Even god is thought to have a sense of humor...
  12. QUOTE (Aristos Queue @ Oct 22 2008, 07:11 PM) OK. I'm in; sourcenders sounds good. This issue has bugged me for the last few days while driving to and from work. I've been researching a bit and concluded that this is contributing to the taxonomy for the 'project' in question. It might be a good idea to consider other toxonomic elements and use a consistent naming convention that will reinforce a term such as sourcender. Adding train terminal, bridge or other metiphorical terms might create a folk taxonomy. ( I've gotta stop reading all this janky Wikipedia stuff! )
  13. QUOTE (alfa @ Oct 29 2008, 04:19 AM) While brushing you teeth and looking in a mirror?
  14. I hear the lemon sherbet is to die for!
  15. QUOTE (Thang Nguyen @ Oct 27 2008, 05:08 PM) I remembered this LAVA post; it might be of some help to you. Norm mentions achieving higher refresh rates on slow computers without much overhead... http://forums.lavag.org/LVOOP-wrapper-arou...ions-t8841.html
  16. QUOTE (bbean @ Oct 25 2008, 04:27 PM) Yikes! Now we need to merge this thread with http://forums.lavag.org/Alfa-String-t10485.html' target="_blank">Alfa String
  17. QUOTE (Aristos Queue @ Oct 24 2008, 01:07 AM) Fo' shizzle! Da' Q man is da' bomb! No http://www.urbandictionary.com/define.php?term=janky' rel='nofollow' target="_blank">janky responses, please... Pojundery, Phillip Brooks
  18. QUOTE (Aristos Queue @ Oct 22 2008, 07:11 PM) QUOTE (Yair @ Oct 23 2008, 03:00 PM) Philip, while terminus is a great word (and you just brought back some nice Asimov memories), I don't think it accurately describes these, as they are NOT end points. More often than not they are probably in the middle of the call chain and the only thing making them special is that they are at "the end" of the project. I think that terminus applies exactly because they are end points w/r/t the project as Stephen described it. A train terminus is "the end of the line" w/r/t the context of the mode of transportation, but that does not mean that the traveler is now unable to continue; only the mode of travel changes. It is a very generic term. I wonder if there is an existing appropriate term that can be reused from graphing theory, petri nets (transition?) etc... I'm guessing that this new pop-up might have something to do with the VI Hierarchy or LV Project...
  19. What about the word "terminus"? While checking for the word terminus on Wikipedia, I found this interesting little piece of text: I never looked up perforce until today. "by physical coercion; by force of circumstances" "That problem is algorithmically equivalent to finding all the termini of a given subVI." "Our school chose the name for our new mascot. We're going to be the Termini!" "All your termini are belong to us."
  20. There is an example of this on the NI web site http://zone.ni.com/devzone/cda/tut/p/id/5321
  21. Bump! Just adding this post to get my question to appear in the RSS Feed where it might get noticed...
  22. 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).
  23. 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?
  24. 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
  25. 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...
×
×
  • Create New...

Important Information

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