An example of a ChangeEvent is, for motion on an axis, the move completes (so, inPositionIsTrue=T, or movingIsTrue=F, or some other similar attribute). (Prior to the event, of course, the values of these attributes were different.)
In a state machine model, you can add a transition between two states, define the transition Type as Change, define a specification for the trigger (in v 10.0.1009--I don't remember being able to do this before), and save this newly defined trigger.
I don't see a way to show the specification on the diagram, unfortunately. (We found it more expressive in the past to define a transition with only a guard instead (e.g., [inPositionIsTrue=T], in order to distinguish visually between SignalEvents and ChangeEvents. This was OK for us since we weren't trying to generate code, but a ChangeEvent is more proper UML. It is legal to name the ChangeEvent inPositionIsTrue=T, but there may be a better way to express that. I'd like to hear some ideas on this.)
Paul