LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Re: How to call other events while being in one event

then any suggestions , i want to check an alarm in middle of the resister write and read and come back to the stage of
write and read ,any time base suggestions .i dont want to exit the event or process i want that the process stop for some
time and run form same step of stop after the alarm check ,i am using Modbus to communicate with board

0 Kudos
Message 1 of 6
(273 Views)

Note that events are not 'called', they are triggered.

 

The events handled by an event structure are processed serially; one cannot be processed in the middle of another.

However you can have the same sub VI called by multiple events.

 

I seems like you want to check the status of something while processing an event.  Is that correct?

Checking the status of something should not require that an event be triggered.

0 Kudos
Message 2 of 6
(261 Views)

You can use User-Events to trigger an event (or several ones) while being in another event. As Paul stated, they are executed sequentially.

If you want to execute the triggered event asynchonously, you can trigger an event in another, independent loop.

 

Greets, Dave
0 Kudos
Message 3 of 6
(233 Views)

akhairnar609@gmail.com wrote:

then any suggestions , i want to check an alarm in middle of the resister write and read and come back to the stage of
write and read ,any time base suggestions .i dont want to exit the event or process i want that the process stop for some
time and run form same step of stop after the alarm check ,i am using Modbus to communicate with board


Sound to me that "check an alarm" should be a VI.

 

If it was, you could call it when there's a "check the alarm" event, and in the middle of "the resister write and read".

 

It also sound like "the resister write and read" should not be handled in an event. If you do this, you typically lock event handling for that event. The consequence is the event structure is locked and (user) events are not handled until the current event is done. That can be OK or even desirable, but for long processes it usually is not OK.

 

If there's an event that should start the "the resister write and read", you usually that that process in a parallel loop. There are many ways to synchronize the two loops...

 

Without seeing any code, it seems you probably want to dive into some popular architectures. 

0 Kudos
Message 4 of 6
(197 Views)

Also: don't make your account name your email address..

 

Fix this ASAP.

0 Kudos
Message 5 of 6
(195 Views)

akhairnar609@gmail.com wrote:

then any suggestions , i want to check an alarm in middle of the resister write and read and come back to the stage of
write and read ,any time base suggestions .i dont want to exit the event or process i want that the process stop for some
time and run form same step of stop after the alarm check ,i am using Modbus to communicate with board


It is impossible to answer your question until you give more detail. For example the term "event" can mean an event structure, or generically something happening somewhere. There are way too many different ways to understand your vague question.

 

Please exactly define all terms used: "event", "process", "stage", "resister" (register? Resistor?), "any time", "time base", "some time", "same step" (same as what?), "alarm check", etc.

 

It would be easiest to attach a simplified VI that shows the overall code architecture. LabVIEW allow for highly parallel code where many independent things can happen concurrently.

0 Kudos
Message 6 of 6
(180 Views)