How to adjust a "control array" size

Question

I have a program that creates a digital PWM signal with variable duty cycle. The duty cycle changes every 50 ms, but the overall wave frequency stays at a frequency determined by the user. I have the VI attatched.
My problem is this...I need to be able to control the overall cycle time. This means the size of my array of duty cycles needs to adjust based on the cycle time (i.e. a cycle time of 1 second would require 20 of the 50 ms slots, while a 1.3 second cycle would need 26).
I currently have only 4 slots in my array, meaning the total cycle time is .2 s. I understand how to manually add and remove elements to the array, but I can't figure out how to add a control to it so that the array size changes automatically, allowing much quicker entry of data. As of now I can make it work, it just takes super long to add or delete array elements. The ideal situaton would have a constant control for cycle time divided by 50 that would change the array size.
I can't find any info on this, and I think I even saw a post asking that this kind of feature be added. I'm relatively new to this program.
Thanks
Solved!
Go to Solution.
Attachments:
var_duty_cycle.vi ‏25 KB

Answer 1

Currently, your VI is a one-shot deal. What you need is a state machine that updates the pct duty cycle array control as a function of the frequency while the current I/O code is idle.
I would use an array of clusters, where each cluster contains e.g. a sequence number, a duty cycle, and a string as element label. Show the scrollbar and set the size whenever the relevant inputs change. Do you want to reset the current setting when the number changes or do you want to retain the current settings as much as possible? You could just use the existing values, reshape to the larger or smaller size, and write it back to the control via a local variable. Set all elements  except the percent to disabled so they act as indicators and cannot be changed by the user.
(You also need to program around it if the operator tries to manually add more elements. A better solution would be this idea, so vote for it .)
Some more general comments bout your code:
Why do you use extended precision floating point. All your waits are internally just integers. EXT makes no sense
There is a primitive for 1/x. However, you could just do a 1000/x and eliminate the multiplication afterwards. SInce you are dealing with integers, you can even do the division using quotient&remainder. Depending on the allowed frequency range there are possibly no orange data needed at all.
Make the diagram constant representation match the rest of the code.
The pulses/50ms indicator belongs before the loop. No need to recalculate and refresh it over and over from the same input values.
LabVIEW Champion . Do more with less code and in less time .