Having a boolean switch/button turn-off automatically

[mrbebu]

Well, yours looks very clean and streamlined compared to my barbaric beast:)  However, mine does work but i do not have a "kill" switch like you mentioned.  I do have a progress update though so i don't know if i'm thinking of the same thing.  

Also, how did you get your LED to light red when they are not running? 

edit: It's not letting my attach my .vi  

It's pretty much like the sequence structure above. 

[altenbach]

---

mrbebu wrote:

Also, how did you get your LED to light red when they are not running?

---

Well, al LED has a true state and a FALSE state. (By default FALSE=dark green and TRUE=bright green).

In my case, FALSE=Red and TRUE=Green. Use the coloring tool. No need for two LEDs. 🙂

[tbd]

Hi altenbach,

---

altenbach wrote:

I don't think we really disagree here, because a state machine can mean many different things to many people...

Since it has states and conditions to switch between them, it is already a "state machine" in the most general interpretation of the term. That's all I meant. 🙂

---

I had to think about that one!  Still (to me) a [LabVIEW] "state-machine" is a loop wrapping a case-structure where at least one output of each case leads (directly or indirectly) to a shift-register and where the left-side shift register leads (directly or indirectly) to the case selector.

More generic than that and we'll be talking about Turing Machines and FSMs soon!

Cheers!

[tbd]

Hi mrbebu, (sorry for late reply)

      I think basic NI-DAQ functionality must be supported on the MAC, but I don't know whether that includes "simulated devices".

If it looks useful, I'd be tempted to ask (post a question to) the hardware forum - somebody there will know.

"MAX" is short for Measurement and Automation Explorer, it's installed with (Windows) NI-DAQ and NI-DAQmx (free).

Here's a link re: simulated devices.

Cheers!

[johnsold]

mrbebu,

DAQ on the Mac (and Linux) is handled through DAQmx Base.  This is written completely in LabVIEW as opposed to DAQmx which uses some Windows only dlls.  The MAX program is not implemented for DAQmx Base.  So anything you read here about MAX, you can just ignore because it will not be available on the Mac.

The mx Base functionality does not have any "simulated devices" capability, but you can rather easily write your own.  I often did that back in the LV 2 and 3 days before any NI provided "simulated devices" were available.  Take the DAQmx Base VI you wish to simulate, make a copy with a different name (such as DAQmx Base Read.sim.vi), then open the simulation VI and replace all the internal code with code which generates a signal with the same number of samples and timing as the original but with the values being generated by your code rather than by external hardware. Put the .sim. VIs in your code in place of the comparable DAQmx Base VIs and you can run your program without hardware.  Since the connector panes are the same they drop right in.  The diagram disable structure can be useful if you want to have both VIs in your program.  These VIs can be simple or as complex as you want to make them.  NI's simulated devices code allows only a very limited set of choice for the kind of signals generated, but when you "roll your own," you are limited only by your imagination and coding skills.

Lynn 

[mrbebu]

Lynn, thanks very much for your informative reply.  Luckily i have parallels and run a windows XP virtual machine that i just installed labview onto and it runs flawlessly so far.  However, it is still good information to know.

Thanks!