event not triggering

[JeffOverton]

Ok, so the basic premise is as follows:

I have a control panel with fifteen or so boolean controls.  All of them operate properly, except one.

They all trigger the same event, which uses the event source data to determine which boolean triggers and what to do in some case structures.

All the code operates as it should, except for this one odd control that operates properly the first time it is set to True (default is False).  After toggling this boolean to True, neither it nor any of the other booleans will trigger their events.  They will toggle, the event will take almost a full second to trigger, nothing inside the event structure will occur (the Event Data still appears properly, though), and they will toggle back to the state they were in when the problem boolean went True.

However, I have my sensors update the screen on the timeout, so I know the events are all occurring, just none of the code is executing.

Any ideas?

edit - oops, forgot to attach. 

Message Edited by JeffOverton on 02-08-2008 02:26 PM

[JeffOverton]

Upon further inspection, if I have highlight execution on, the controls respond properly and their events happen.  Also, if I double click any control, it executes properly.  All other event cases in the structure execute properly.

The highlight makes me think it might be a race, but I thought events were buffered.

[Pnt]

You should post a simlified version of your problem.

Many vis are mising...

[MikeS81]

Hi Jeff,

can you upload the missing vi´s?

Some points for you:

• control references don´t need to be closed
• in the timeout case, you use the control reference of your cluster and at the end you overwrite the value (what do you make there??)

Mike

[JeffOverton]

---

Pnt wrote:

You should post a simlified version of your problem.

Many vis are mising...

---

The simplified version is that a boolean triggers an event, and thereafter that specific event won't execute.  The trouble is that all the booleans execute under the same event case.

---

MikeS81 wrote:

Hi Jeff,

can you upload the missing vi´s?

Some points for you:

• control references don´t need to be closed
• in the timeout case, you use the control reference of your cluster and at the end you overwrite the value (what do you make there??)

Mike

---

The missing VIs are the proprietary ones

In the timeout, the first missing VI is me reading my various pressure sensors.  The second missing VI is enabling or disabling various valves based on what pressures exist and what valves are open.  However, they are either enabled or disabled and grayed out, so I know that's the not the source of my problem.  Also, if the booleans were disabled and not grayed out, the event itself wouldn't trigger (which it does, just no code executes).

[Pnt]

         JeffOverton wrote:

---

Pnt wrote:

You should post a simlified version of your problem.

Many vis are mising...

---

     The simplified version is that a boolean triggers an event, and thereafter that specific event won't execute.  The trouble is that all the booleans execute under the same event    case.

---

If you can replace your missing vi's with dummy ones (which will do nothing), maybe we can help.

Events are buffered and you can't miss one. I also don't remember any bug like this. The most possible reason is your code, somewhere.

[JeffOverton]

Yeah, the actual event is triggering.  The boolean immediately appears to toggle, and about 3/4 of a second later, the event source (User Interface) and control reference of the event source are available, but no code is executed inside the event structure.

I also discovered this morning that double clicking will properly execute the event, so I have no idea what that might mean in terms of memory or stacking or what have you.

[altenbach]

---

JeffOverton wrote:

...I have a control panel with fifteen or so boolean controls.  All of them operate properly, except one.

---

You need to help us out a bit here and be more specific:

• If you attach a truckload of VIs, please tell us which one is the toplevel.
• Why don't you give us the name of the boolean that does not work! This will immediately lower our search efforts to 1/15th. 😄

[JeffOverton]

Woops, sorry.  These are all called by a general function, but they're all operable on their own.

Man1.vi will launch a standalone manual valve control program, and it's in the folder Manual 1.  Necessary SubVIs are in Manual Common, and all typedefs and controls are in Typedefs.

The program will run fine until 3g (in the bottom right, it's a water fill valve) is toggled, and then no control will operate properly except for "Default State" (because it uses a separate event).  The trouble only happens when 3g is True.  If you hit Default State it will return all valves to their unenergized state and reset the controls, and the program will work properly again.

As of this morning, I know that if 3g is true and the controls are semi-unresponsive (they will toggle, no code executes, and they toggle back), a double click will accurately switch the control.

Message Edited by JeffOverton on 02-11-2008 10:31 AM