The subVI's you attached were named differently from the ones you actually used in you main VI. I relinked them into the code so I could see what they looked like. The colors you used on those subVI icons were horrible. Blue text on a black background was completely unreadable.
One problem you have is that you are not using a state machine architecture. Your last event case will fire only when the value of the numeric control changes. Then the next iteration will start and the event structure will wait again for something else to happen. There is nothing to advance the ramp to the next step.
An event structure is good to use for handling front panel events such as button presses. But embedded as part of your control loop means the control loop only ever runs if some event happens. There is nothing to allow the automatic ramp up to occur.
Go to File/ New..... and look for Producer/Consumer Design pattern using Events. Also, look at Standard State Machine architecutre. What you will need its a combination of both. You need the Event structure in its own while loop. It will pass commands onto the other loop that would be your state machine.
You have lots of coercion dots in your program where you use integer constants in places where the functions or VI's are expecting doubles. Change the representation of many of those constants and the coercion dots will go away. At best, they are a nuisance and extra data copies as LabVIEW converts the databytes. At worst, unexpected conversions could change the way the code operates.
