When you say that it doesn't change, do you mean that your event structure doesn't trigger indicating a change? The cluster in the sub-vi should change, but your event structure won't trigger on that change in the sub-vi. When I say that event structures react to user changes on the front panel I mean an event structure in the same vi as the control the user is changing, not that a change on the higher level vi's front panel cluster will trigger and event on the called vi. If you are passing a value from the calling vi, through the interface connector pane, the lower level vi's cluster will change, but it won't trigger the event. Even at the top level vi, if something in your program changes the value of a control that is "monitored" by an event structure, in that vi, it won't trigger the event, unless the program is changing the "Value(Signalling)" of that control (by using a property node). The event structure is mostly used to detect when you change a control, using the mouse or keyboard, on the front panel of the vi it is in. To trigger events programmatically (by passing different values to lower level vi's) requires more code/complexity.
What is it that you are trying to do, it is quite probable that the event structure isn't what you need. If you are just trying to trigger something in the sub-vi when the cluster value changes that can be done with saving the last cluster value in a shift register and comparing it to the new one.
Tell us what you are trying to actually do in the sub-vi when the value changes and we can probably show you how. Events have only existed for the last few versions of LabVIEW. A LOT of code was written before them. They have made many things easier, but not much can be done with events that couldn't be done without it (although it might have taken a lot of code!)
P.M.
PutnamCertified LabVIEW Developer
Senior Test Engineer North Shore Technology, Inc.
Currently using LV 2012-LabVIEW 2018, RT8.5
LabVIEW Champion