Jump to content

Roderic

Members
  • Posts

    123
  • Joined

  • Last visited

  • Days Won

    6

Posts posted by Roderic

  1. Hi,

    Firstly, I think you should clean up your code (a bit)

    Secondly, if you just want to stop if the amplutude is too high you can use a threshold detector (already existing in LabVIEW) and a case structure.

    Lastly, you have a problem with your stop condition (in the acquisition loop) and you do not handle errors while looping this may be a problem...

    Hope this helps.

    • Like 1
  2. hi cat,

    You shouldn't worry about CLAD, even I passed CLAD easily and I'm still a student. So if you are coding since 1994 this will be easy! just review the basics and work with the sample exam. You can also take the CLAD exam for free at NI local expo.

    My guess is you have to start the certification pyramid from scratch, like going to the university you need a bachelor to go to master degree, then PhD(Even though you don't need to know everything you learned when you were working towards a bachelor's degree).

    @crelf: I doubt an Architect would fail at CLAD (if he works a little bit)

  3. I'm an intern myself, if I had to recruit someone I would give him a coding exam, and look for someone independent. Maybe you should ask for someone who already worked with labview in a project or in a previous internship. Dedication to the task is the most important skill I would be looking for.

  4. Hello everyone,

    I need help on a project. A VI launches testStand sequences, if the project is closed (only the VI is Open) everything works fine. But, if the project is open

    or Vi compiled as an .exe application I receive an error from TestStand, it could not return the FIFO reference. It seems somehow the reference is private to the project or something...

    I also get the same behavior using the Full featured UI shipped with TS2010. (I also have LV 2010).

    This issue is also present if I try to use my Vi and sequences on another computer.

    Do anyone encontered this problem, or has any clue about how to solve this problem?

    Best regards,

    Rodéric L

    Certified LabVIEW Associate developer

    post-18392-0-29167200-1302695750_thumb.j

  5. Indeed, there's different ways to do this. and I dont think this is the simpler way, but if it works then...

    You seem to use an indicator as a control for the file path... or maybe I dont have the whole picture.

    Your design is a bit weird to me.

  6. Hi,

    I'm trying to launch different sub-sequences in different executions( I intend them to run in parallel this way I can stop and re-launch a sequence as needed). My problem is the sub-sequences do not seem to execute, I tryed to use a prompt message dialog box, but it doesn't show up... (it works fine if I launch it in the same execution, or new thread)

    in the report, I can see the call sequence step is "done"...

    How can I configure TestStand to get the intended behavior???

    can I launch a sub sequence in parallele mode if my main sequence is in a sequential mode?

    Best regards,

    Rodéric L'EXACT

    Ps: I need them to run in parallel for data acquisition

×
×
  • Create New...

Important Information

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