Jump to content

Wire Warrior

Members
  • Posts

    226
  • Joined

  • Last visited

  • Days Won

    3

Posts posted by Wire Warrior

  1. 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

  2. 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. :ph34r:

    Jason

  3. 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

  4. 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.

  5. 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

  6. 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

  7. 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. :thumbup1:

    I was disappointed that crelf never wore a bow tie all week. Sigh....I guess we just can't have it all. :cool:

    Jason

  8. 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

  9. We stayed at the Hilton this year. It was right across from the convention center which made travel easy. The biggest downside was the fact that internet access costs $15 a day. Still all in all it was okay.

    There is also a Marriott Courtyard nearby as well.

    Jason

×
×
  • Create New...

Important Information

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