08-22-2006 09:25 PM
08-23-2006 08:22 AM
The typical way to approach a feedback control system problem is to have a good mathematical model of the system in question. The system characteristics will dictate the best approach toward the sweep & detect algorithm.
For example: As 3 of the 4 outputs are held constant and the other is swept, will you expect to see exactly 1 peak output? Or could it be more? Does it depend on the specific values of the other 3 outputs? Etc.
The answers to these kinds of questions put some constraints on the expected output behavior, and help to dictate the kind of algorithm to use for sweep & detect.
-Kevin P.
08-28-2006 02:23 AM
thank you.
i want to do a hill climbing algorithm , each channel at one time. i'm coding it now.
how to store the initial power into the loop? (for comparative with the updated power value as i execute the hill-climbing loop)...
08-28-2006 06:39 AM
You'll want to learn about the use of Shift Registers, not only for the initial value of power, but also so each cycle through the loop gives you access to the power value from the prior cycle -- this lets you know if you've increased or decreased it. Odds are, you'll need to expand the left-hand-side shift register to give you access to info from 2+ cycles in the past. This is because once you see a power decrease, you'll probably want to "roll back" to where you were 2 cycles earlier.
-Kevin P.
09-03-2006 10:49 AM
i decided to use a master/slave with state diagram. I'm studying some examples and Below is an example files i downloaded from ni LabVIEW Application Design Patterns at http://zone.ni.com/devzone/learningcenter.nsf/03f7c60f17aad210862567a90054a26c/338ee44cb1c3450986256... it is a zip file, and this is the example BuckRogers laser. one things i cannot comprehend is the operation of the "while loop"(smaller loop) within the "state" while loop.
if i not understand wrongly, the "i" of the smaller loop with iterate through the enumerated "conditions" (namely: manual shutdown, too hot, a bit warm, fire, needs power, default). if certain parameters are met, for example within the "too hot" condition, if temperature>80, the boolean condition will end that loop and trigger the next state to be Active Cooling on the "state" while loop.
however, i cannot comprehend a portion:, the "default" condition under the "check status" state, as in the figure pasted below. it seems to me that the while loop will be forever trapped within this sequence, as there is no way to letting pass this "default" loop , as a True is defined to end the loop everytime, and forcing it to reenter another "check status" state. How exactly the "FIRE" condition is even reached ? (and stopping the loop there after the user click on the FIRE button on the GUI?
09-03-2006 11:02 AM
09-03-2006 11:31 AM
here is the state diagram i would like to code in the slave loop (hope it provides enough clarification to make my question clear)
my algorithm is suppose to check the power (check DOP), if DOP less than threshold voltage, then it simply control the voltage (up or down) until the DOP is back to normal. it will sweep to the next voltage channel (4 of them total) if the prior voltage channel control fail
09-06-2006 12:57 AM
09-06-2006 01:15 AM
09-06-2006 08:01 AM