Jump to content

davidcli

Members
  • Posts

    2
  • Joined

  • Last visited

davidcli's Achievements

Newbie

Newbie (1/14)

  • First Post Rare

Recent Badges

0

Reputation

  1. Have you tried using the SMO.lvclass:Stop.vi and then SMO.lvclass:Destroy.vi?
  2. In the SMO Editor Tool, there is a "Create New Event" button with a satellite icon (top right). The official description for a Public Event states the following: For Private Events: For Public Methods: Public methods are for the SMO to broadcast some sort of data or some sort of event. Example; data from a voltage reading in the double datatype could be continuously read and broadcasted (You physically route the data wire into the Public Method which generates a user event). An external SMO can subscribe to the user event in their own user event handler and do something with the data. The event isn't limited to just values. Maybe the pressure for a boiler trips a threshold. In this case, an "over-pressure event" can be triggered by sending the corresponding Public Event, and you don't really need to send any value (it defaults to a Boolean control). You could make use of it though by having the threshold trigger the event and send a True. And when it comes back down it triggers a False. But note, in this case the event is not broadcasted continuously. I haven't used Private Events as much as Public Events and Public Methods. But in theory the Private Event would be able to change the internal state of the state machine from within itself. From what I've read, it is best practice to prevent external VIs from modifying the state of a state machine directly, maybe this mechanism allows for that. I am more used to Queued Message Handler structure, so what I would do to modify the state machine internally is by modifying the string queue itself. Would be nice for someone from JKI to explain Private Events and the intention :]
×
×
  • Create New...

Important Information

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