"Howard, John" <[EMAIL PROTECTED]> write:
>It lets you create state machine based LabVIEW programs by 'simply' drawing a
>state diagram. You can switch between diagram view and code view. It
>probably mostly useful for documentation, where state diagrams are needed.
>
>It is not part of any vers
Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Behalf Of [EMAIL PROTECTED]
Sent: Friday, January 16, 2004 7:48 AM
To: [EMAIL PROTECTED]
Cc: Info LabVIEW (E-mail); 'John'
Subject: Re: State machine diagram editor
Rolf K. wrote:
> I have looked at th
It lets you create state machine based LabVIEW programs by 'simply' drawing a
state diagram. You can switch between diagram view and code view. It
probably mostly useful for documentation, where state diagrams are needed.
It is not part of any version of LabVIEW, you have to pay for it separatel
Rolf K. wrote:
> I have looked at the State Machine Toolkit and believe that it is fine
for
> the standard state machines a lot of users usually encounter but my state
> machines usually always tend to be just a tiny little bit more involved
so
> that I would have to hand edit the generated sta
quot;LabVIEW -Info" <[EMAIL
PROTECTED]> |
| cc:
At 14:25 -0600 01/16/2004, Scott Serlin wrote:
>I do not have any controls to access in my vi state machine. As an
>example, I control a piece of equipment that labview turns on, gets some
>measurements, logs those measurements to a database, and then shuts
>down. I do not access any front panel
PROTECTED]
Sent: Friday, January 16, 2004 7:48 AM
To: [EMAIL PROTECTED]
Cc: Info LabVIEW (E-mail); 'John'
Subject: Re: State machine diagram editor
Rolf K. wrote:
> I have looked at the State Machine Toolkit and believe that it is fine
for
> the standard state machines a lot
better?
Scott
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Behalf Of Howard, John
Sent: Friday, January 16, 2004 12:49 PM
To: [EMAIL PROTECTED]; Scott Serlin; Thorpe, R. Mark
Subject: RE: State machine diagram editor
One tip that I would offer is to consider using a
2:18 PM
> To: Info LabVIEW (E-mail)
> Subject: RE: State machine diagram editor
>
>
> Thanks for the info. I was hoping for a faster way to add
> and modify states to the state machine. Also, does anyone
> have any state machine tips that they can share? I typically
> u
s.com
Subject: RE: State machine diagram editor
From: "Scott Serlin" <[EMAIL PROTECTED]>
Date: Fri, 16 Jan 2004 11:17:53 -0600
Thanks for the info. I was hoping for a faster way to add and modify states
to the state machine. Also,
An important point is that any state diagram (and logic) that you use to
control a process should be related to the process and not to internal
computer program states or actions. Make the state names represent states
of the process being controlled and name them accordingly. For example,
Purging
This is in answer to comments by Paul F. Sullivan
This is just a programming style preference, either way will work. I put a
pop-up error message in the default case to catch misspellings or bad cases.
The message displays the incorrect case string which makes it very easy to
troubleshoot. I pr
Paul et all,
>The OpenG toolkit has a "Set Enum String Value" VI that would allow a >text script to run an enum-based sate machine. I didn't know about >the OpenG VI when I first needed this capability so I built a "Set >Enum with String" VI that works with control references. If you'd >like that
I also use files to define the state transition logic plus I use a second
text file to define the outputs (actuator values) that change at state
transitions. If you write your state logic properly, you can completely
control the state transitions and the analog and digital output changes at
stat
Mark,
You wrote:
... I use string driven
state machines instead of enum type defs when I want to create a scriptable
state machine. That is, the state sequence is driven by a text file that
has information about what order the states are executed. This means the
test sequence can be modified in
Lew,
I really like your premise and architecture:
An important point is that any state diagram (and logic) that you use to
control a process should be related to the process and not to internal
computer program states or actions...
In the most general case, I use 4 asynchronous loops running in p
At 10:31 AM -0800 1/18/04, PJ M wrote:
...>The OpenG toolkit has a "Set Enum String Value" VI ...
One can also just use the "Scan From String" primitive with the enum
type def constant as the "default value 1" and the string you want
to set as "input string". This way "output 1" will return the
>>> Lewis Drake 01/18/04 03:02PM >>>
... when I added a new value to the enum, the state case structure case
labels would sometimes shift to ones which were incorrect, and I'd have to
continually check every case and manually adjust the case names. Perhaps
this is not a problem in LV7.0, I haven't
A few more state machine options to add:
- use an array to manage the task list as Uwe mentioned
- use a queue to do the same thing, but with a little different 'flavor'
- a slightly 'odd ball' implementation I have experimented with is with user
defined events (using the state machine's type def
the upgrade. I usually end up leap-frogging
my versions. I take big jumps rather than little steps.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Behalf Of Paul F. Sullivan
Sent: Sunday, January 18, 2004 6:11 AM
To: Mark Smith
Cc: [EMAIL PROTECTED]
Subject: RE: State
At 9:59 AM -0600 1/19/04, Scott Serlin wrote:
Can you elaborate further on where the OpenG toolkit can be found with
the "Set Enum String Value" VI?
It's not an NI package. It's available through http://www.openg.org/,
where you'll find the information. In the box on the right side of
the screen
Paul,
You wrote:
>Beware though that if you have enum items set {"da","moo"} and
>supply a string "dada" or "mooable", no error is returned...
I handle this problem via the case structure's Default case. With string
driven state machines, my default case is always "invalid case." If a
string
> >One can also just use the "Scan From String" primitive with
> >the enum type def constant as the "default value 1" and the
> >string you want to set as "input string". This way "output 1"
> >will return the enum type def with the "input string" value.
>
> Ouch! How could I have missed that?
Scott and all,
I am a bit late here, but...
"Scott Serlin" <[EMAIL PROTECTED]> wrote on Fri, 16 Jan 2004
11:17:53 -0600
...
> Also, does anyone have any state machine
> tips that they can share? I typically use a string driven state
> machine. I then call out each state from other states. I al
>Beware though that if you have enum items set {"da","moo"} and
>supply a string "dada" or "mooable", no error is returned. You'll
>have to test the if the remaining string is empty. But even when
>doing that it might not be wise to rely on enum item sets such
>as {"bah","ba"} to lead to non-am
nd Windows 98...
Johann Junginger.
-Original Message-
From: Scott Serlin [mailto:[EMAIL PROTECTED]
Sent: Monday, January 19, 2004 10:59
To: Paul F. Sullivan
Cc: [EMAIL PROTECTED]
Subject: RE: State machine diagram editor
Paul,
Can you elaborate further on where the OpenG toolkit can be fo
26 matches
Mail list logo
