Number of Events in Event Structure...limitations?

[Azazel]

Hello All,

I am using LV 7.1, XP Pro, USB I/O control.  With that out of the way I have a question about the actual number of events one can have in an event structure before it becomes detrimental.  My design task includes:  I have a series of micropumps (>32) and need to be able to turn each individual pump on/off at will.  My original thought (correct me if I am wrong) was to use an event structure with 32 events that comprises of a boolean that will send the turn on/off signal to each pump. Is there a cleverer way to accomplish the same task or will the event structure facilitate my requirements?

Thanks in advance,

Azazel

[GerdW]

Hi Azazel,

you can use an boolean array instead of individual boolean switches. So you need only one event case 🙂

You can also add several events to one event case. So you can try to minimize the number of event (when possible).

[Azazel]

Hello GerdW,

Thanks for the suggestion.  The boolean array is a great idea, however with my limited experience I am having trouble setting it up.  I figure it is probably a very easy task, could you post an example .vi?

Thanks,

Azazel

[Ben]

The attached example illustrates how to determine which boolean of a 2-d array changed value.

It uses an event configured for a value change of the control. When the event fires;

A) the old and new values are compared to determine which boolean changed states. This results in a 2-d array of booleans.

B) The array dimensions are used to re-shape the array.

C) The array is re-shaped and searched for the true boolean (indicating it has changed states).

D) The index of the changed boolean can be used to act on the physical devices as your application dicatates. The remander quotent function allows you address your devices by row and collumn of the array control.

Ben

Message Edited by Ben on 11-24-2006 12:09 PM

[Azazel]

Thanks Ben,

This is exactly what I wanted!  Off to the lab to hook it up to my micro-pump array.

Azazel