LabVIEW
time loop... or how you call this ?
Solved!
Well, we cannot fully solve this unless we know how the rest of the program is architected.
Still, you could do a while loop that spins at a 1 second interval. Divide the interation terminal value by 58 using "quotient and remainder" and do a comparison on the remainder. If it is less or equal one: Heats, else: don't heat.
Or even simpler a squence with Heat and wait for 2 sec and then no heat and wait for 55 sec ... However i somehow dont think that's actually what you want to do.
/Y
@laurentiu wrote:
Look, the arhitecture is simple (check the attachament). The .VI is only for one sensor (lm35). I have to remind you all that I am new with Labview and I'm not intending to use it for complex opreation then this. If I made something wrong, please corect me by showing me in a .VI file. I learn fast only by seeing.
So, in order to achieve the set temperature measured with the LM35 sensor, the heating element must be 2 seconds ON and 50 seconds OFF . But this cicle I want to use it for each sensor separately.
Thankyou for your time!
You don't really provide enough information. How many heaters are there, how do you interact with them? If you have multiple sensors and heaters, do the same thing but with an array of heater readings and an array of heaters. Code would be almost identical.
Since your loop spins at a rate of 1Hz, easiest would be to use my method, but of course a more scalable state machine would be more appropriate. Here's a quick draft.
Some of the problems in your code:
- Your feedback node needs to be initialized, else it remembers the data from the previous run.
- I would suggest a shift register instead.
- It is really not a good idea to grow an array without bounds like this. What is the typical maximum array size?
- Place your array indicator and array output on the other side of the feedback node, else they lag one iteration behind.
- "Insert into array" is the wrong tool. Use "built array" to build an array.
- Why is the front panel and diagram maximised to the screen. That's an annoying habit.
- Should the loop stop when the temperature is reached? In this case wire the temperature comparison to the loop condition in the right logic.
