10-17-2019 11:59 AM
@dadest100 wrote:
The VI it's been running for 5 days now with no problems. I agree, a small delay would reduce the CPU % and I should probably add it, but if you want to check the time using labview then there's no other way around it. The VI has to run continuously checking the current time so you can compare it. Only other way to do it is using the Task Scheduler but I want to only have labview running and not rely on another app.
At the moment, the VI has a window of 0.5secs to react to the triggering signal. If you increase this range too much and you only want to run your program once, it might run a few times within this window depending on how much you need to process. I am comparing a rounded decimal = integer to zero. No problems with that.
What you should do ... ,
mcduff
10-17-2019 12:27 PM
@dadest100 wrote:
The VI it's been running for 5 days now with no problems. I agree, a small delay would reduce the CPU % and I should probably add it, but if you want to check the time using labview then there's no other way around it. The VI has to run continuously checking the current time so you can compare it. Only other way to do it is using the Task Scheduler but I want to only have labview running and not rely on another app.
I don't know what you mean by this. Task Scheduler is not another app. It is built into Windows and is always there running whether you realize it or not. Complie your LabVIEW program into an .exe, and set up Task Scheduler to call that weekly at a specific time. Then you won't have to worry about if someone accidentally closes your LabVIEW program.