Jump to content

lewdrake

Members
  • Content Count

    2
  • Joined

  • Last visited

    Never

Community Reputation

0

About lewdrake

  • Rank
    I've come back for more.
  1. This LabVIEW V6.1 example State Diagram illustrates how to make any VI startup with the same control settings that it had when it last was closed. It also shows a technique for creating a State machine with states that are defined by a text file and that therefore can be easily changed without recoding. Analog and digital outputs (called actuators in the example) are generted that are a function of each state. These are also defined by a text file to meke programming changes easy. The example uses 3 digital inputs to effect state changes. For convenience though, the example uses the numbers 0 - 7 as inputs to change states and the 3 digital inputs are simply shown as outputs. See the code for more details. Start the program and click on the DI simulator (0 - 7) to effect a change of state. The diagram will display the results. You can edit the State Transition Table to reconfigure the State diagram or edit the Actuator Table to change the outputs associated with a State. Lew Drake Process Automation Corporation 908 359-1011 Download File:post-12-1081709930.zip
  2. It seems that my LabVIEW program diagrams are getting too large to fit my screen and I find myself using the windows scrolling feature a lot to move around. This is mainly due to my use of multiple while loops and autonomous subVIs. For example, I might have: a user interface loop containing the event structure; a task loop; a state diagram loop; a loop to pop-up-other VIs; device control/driver loops;... the list goes on. I know I can change my coding techniques to reduce this proliferation, but other methods all have tradeoffs that I don't like. So please, don't respond to this note by advising me on how to revise my coding techniques to eliminate the problem. I'd like to make things easier for myself by suggesting the following future LabVIEW enhancement. NI, please provide a Tab Control (or something similar) that can be used to consolidate loops, subVIs and other items that run autonomously. With this, I could place one or more related autonomous loops and subVIs on a diagram window Tab labeled with a descriptive function name. No data need be wired directly between these loops and VIs, so wiring between different Tabs would be no problem (they communicate using queues and globals). It would be quite easy to navigate between functions by just clicking on a Tab rather than by trying to scroll vertically and/or horizontally. I'd like to hear your opinions of this suggestion, and any better suggestions you might have that would, in effect, increase the available diagram screen size.
×
×
  • Create New...

Important Information

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