Jump to content

Wire Warrior

Members
  • Posts

    226
  • Joined

  • Last visited

  • Days Won

    3

Posts posted by Wire Warrior

  1. Configure the 1st loop as a state machine and create a "pause" state for the state machine that automatically calls itself. Use a queue or other messaging structure to pass the pause command from the processing loop to the acq. loop.

    That would be one way.

    Jason

  2. Is this true for *all* controls or just "modern" controls?

    Yes it is true for all controls. Of course some require processing that others.

    The important component when overlaying is the rate of update. How often do your graphs update? Once a data run would likely not be a noticeable issue. At 1000 Hz it maybe an issue.

    Probably the best thing to do would be to test your system as early in the build as you can and measure the performance time.

    Jason

  3. NI talks about this particular issue in the LabVIEW Performance class. When you overlay controls, the LabVIEW execution engine must "redraw" ALL overlaid controls every time either of the controls are updated. It the situation you mentioned I would suspect one or both of the overlaid controls were updated frequently. If so, then the Google Earth ActiveX would be executed at the same frequency. I can see where that might chew up some serious processor cycles.

    If you could move those controls to a different area of the UI, you would likely see an improvement in the performance.

    Jason

  4. The DETT will allow you insight into the memory behavior of your program. Among other peices of information you can see every memory allocation call made by the program. The DETT also allows the inclusion of custom user events that can assist isolation of the program.

    You can also use VI Profiler (located in the Tools Menu under the Profile >> Performance and Memory option) in the development environment that can assist in tracking down a memory leak one a per VI basis.

    Jason

  5. OK, I picked up some gloves thrown in this topic and here is Weird Wires RCF Edition:

    post-7450-126087844858_thumb.png

    And little video.

    Rounding corners was quite challenging... This is for you, Jim :)

    License for this code is DWYL (do whatever you like).

    :thumbup1: Excellent yet another peice of code to taunt the text based programmers at the office with!

    Jason

  6. I am trying to write a program by labview 8.2 that will send pulses to output inorder to rotate a motor till the input voltage to the labview becomes zero. then it will stop the movement of the stepper motor. I will be very thankful if you can help me.

    thanks

    Well, to start with your going to need some type of analog input/digital output hardware as part of your system.

    I would imagine the best place to start is with some of the examples which ship with LabVIEW. If you look under the Help tab on the menu, you will see the "Find Examples..." option. This will bring up a dialog that will allow you to look at a variety of solutions to some of the basic problems. You would probably find lots of help looking at the Digital Output examples and the Analog Input examples.

    Jason

  7. :thumbup1:

    I have solved the problem I think (at least as far as testing to this point has revealed). After I added in the ability to log the states passed to the QDSM's, I was able to determine that the program was "crashing" after I dynamically closed the front panel of the launcher. My program was designed to close the front panel of the launcher then pop-up the front panel of the main UI. My EXE is built on to contain the launcher with my other QDSM files being maintained externally in specific directories. What appeared to be happening is that when the launcher closed its front panel and before the UI opened up the run-time engine would decide since there were no windows open it would close itself down. This is my supposition about what may be happening any way. I modified my code to changed the launcher window to hidden and delay for 1/2 a second to give the main UI a chance to start fully running. This fixed the problem, or at least worked around it.

    If someone out there can explain to me exactly what is happening I sure would appreciate it.

    Thanks for all the help those of you who responded. Your advice was very beneficial and certainly led me to a resolution faster.

    Jason

×
×
  • Create New...

Important Information

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