Jump to content

Wire Warrior

Members
  • Posts

    226
  • Joined

  • Last visited

  • Days Won

    3

Everything posted by Wire Warrior

  1. Exploring some of the latest LAVA content for LabVIEW

  2. Hmmm...I wonder which of those is Daklu's favorite.... Jason
  3. :lightbulb:Seems like a perfect item for the Idea Exchange. Jason
  4. Cool. A modifying JonKokott's Coding Madness 2011 entry would make this a programmatic function. Jason
  5. That's what I had in mind as the "take them out option". My thoughts for leaving them in are that a DETT trace could be initated without having to do a recompile. Jason
  6. Good catch, jgcode. Actually, these are new additions to our re-use library to answer an issue we've had on the MFG floor and these components will be included in all new apps and retro-fitted into some portion of existing apps. That's why I asked this question. Trying to identify the final version of these VI's. The company standard for DETT is a good point. On our development machines we have it installed but on the deployment machines we prefer not to have any development tools (as learned from painful lessons) and that means we would not take the step of installing DETT. Any other thoughts? jason
  7. I am in the process of debugging an issue that only shows up on a built application. Obviously the Desktop Execution Trace Toolkit is ideal for the job particularly after I sprinkle in some user defined messages. The question comes on the heels of my realizing that some of these messages needed to be placed in our re-use library VI's. For long term I can see where making these custom messages part of the re-use library could be useful should future issues arise but what is the unforeseen impact of leaving these messages in? Is there any worth worrying about? Jason
  8. ME! ME! ME! It was great fun last year (my first NI Week ever) and I can't wait to see what tops the limericks. Jason
  9. :thumbup1: This is great to know! I can see it being very useful. Jason
  10. Sounds like you might be better of to have Scan Validation step which determines whether or not the scanner data is worth putting on the stack in the first place. Just guessing from your stated direction i.e. the LIFO, are you getting multiple scans returned by the scanner and only the final one in the set is good? Jason
  11. When I want a "borderless" appearance for a VI I use a transparent background. Have you checked out this document http://decibel.ni.com/content/docs/DOC-1086#comment-5644 in the NI Developer community? Jason
  12. SWEET! Just think of how much LabVIEW awesome that means LAVA has! Jason
  13. Can you share the answer you found? Jason
  14. Okay this brings up a question I was having the other day. I can see how the treat read-only VI's as locked would solve this problem but how are you setting the VI's to read-only when you emplace them? We use VIPM to distribute our reuse libraries but I see no way to set them to read only on import. I have considered generating a VI that could be run post install of the VI package that would set the VI's properties to read only. Is there a better way that I am missing? Thanks Jason
  15. Okay....Here's another me too on the upload problem. Was trying to upload a snippet from the code capture tool. File size 18 kB, png image. I tried on Firefox 3.16 and IE8. I figured I was doing something wrong on my reply until I saw this thread. Jason
  16. I don't know the answer to the Windows OS installer exception question. I would like to as well. I do wonder though why you need the individual users install the software on the machines? It seems like your IT folks want to control the installs/uninstalls of the programs on the machines. Why not let them manage the installs? That's the structure they've set up. Sometimes the easiest way to get a rule changed is to follow it. Jason
  17. Hello All, Seeing that one version works and one doesn't and one major difference is the change from the "Run in UI Thread" to "Run in Any Thread". I don't understand why that would make the difference? Jason
  18. Maybe you could use a packed library instead of a dll. If you are looking to do like something we have been talking about around here, your goal is to encapsulate a specific sub-set of the code that can be easily swapped out/upgraded when necessary. We were looking at a method for plug-in distribution, yours seems to be machine dependent code. We are thinking that a packed library will be able to do what we sought. Still haven't "tried it" though. jason
  19. All, The company I work for, BEI Precision System & Space Co., is looking to hire a Test Engineer II. Yes this is a 2nd job posting. You can find the the posting on our website by clicking HERE. You can also contact me for more information. Here's the posted information: Position Title: Test Engineer II Job Description Arkansas' finest aerospace company has the opportunity for students to learn from and support its engineering staff. This staff is involved in the design, manufacture and test of high-precision sensors and subsystems for spacecraft, military craft, astronomical observatories, and scientific laboratories. Participants will be expected to draw upon their knowledge of mathematics, physics, optics, electrical engineering, mechanical engineering, computer engineering, computer science, or instrumentation science as necessary to solve problems in a business environment. Basic Qualifications Must be a US citizen with the completion of a 4 year collegiate program in or related to one of the following areas: Electrical Engineering, Mechanical Engineering, Physics, Computer Science along with at least 3 years of applicable experience and three years of LabView experience in the last five years. LabVIEW RT and Lab VIEW FPGA a plus.
  20. All, The company I work for, BEI Precision System & Space Co., is looking to hire a Test Engineer. You can find the the posting on our website by clicking HERE. You can also contact me for more information. Here's the posted information: Position Title: Test Engineer Job Description Arkansas' finest aerospace company has the opportunity for students to learn from and support its engineering staff. This staff is involved in the design, manufacture and test of high-precision sensors and subsystems for spacecraft, military craft, astronomical observatories, and scientific laboratories. Participants will be expected to draw upon their knowledge of mathematics, physics, optics, electrical engineering, mechanical engineering, computer engineering, computer science, or instrumentation science as necessary to solve problems in a business environment. Basic Qualifications Must be a US citizen with the completion of a 4 year collegiate program in or related to one of the following areas: Electrical Engineering, Mechanical Engineering, Physics, Computer Science along with at least 3 years of applicable experience Familiarity with databases, test instrumentation and LabView a plus. Thanks, Jason Willis
  21. Sorry about that. I should have looked more closely at the example I posted. It's obviously not the one I was looking for. Thanks for pointing that out Fabiola. Jason
  22. So....what your saying is "There is no spoon?" Jason
  23. I built a system on a sbRIO (basically a unpackaged cRIO) earlier this year that used a state machine no problem. Matter of I used a modified version of the JKI state machine for the basis for the code. Not having a front panel meant some of the open close VI code was not needed. Based on my experiences you should have no issues building a state machine based architecture on an RT system. Jason
  24. I'm just excited I got to put faces with names of so many of the people from the board. Of course meeting the Fabulous Fabiola was one of the highlights of my week. I was disappointed that crelf never wore a bow tie all week. Sigh....I guess we just can't have it all. Jason
  25. LabVIEW has most of the functions you need to do this build right in though sometimes the hard part is finding the VI you need. This is a link to a page of functions that specifically support the type of signal analysis you are needing to do. Combine this with one basic signal analysis demos that NI ships with LabVIEW and you will be up and running in no time at all. Good luck with your project. Jason
×
×
  • Create New...

Important Information

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