LabVIEW
Event Driven State Machine Infinite Run Error
@User002 wrote:
I've tried making this program for three weeks and have 3 large projects with multiple files from various attempts. At this point, I'm of sick of it.
So we're not going to do your homework for you; if you're sick of it, then we are, too. Engage your brain one more time tonight (or later, when you have time to take a deep breath and look at the homework again). Why do you think those original values were there? Surely not just to set the next state for your state machine. Look at all the places where the wire goes. Do you think all the places where the wire goes would like the changes that you made?
And in case you think I should feel sorry for you, I don't. If you want to potentially take my place when I retire, I want my replacement to be competent. I'm just trying to prepare you for a world when there won't be anyone to do your homework for you. Harsh? Maybe. I'm just trying to prepare you for the real world.
@User002 wrote:
I didn't ask you to do my homework. Nor am I asking you to feel sorry for me. You told me to think about it and I'm just implicitly mentioning that I have. And I never wanted your test job or whatever doing LabVIEW in the first place. This was just a class to fill up my last credit requirements.
It doesn't even have anything to do with LabVIEW, really. It's critical thinking. A critical thinker can troubleshoot any system, but the more information they have, the more specific they can get. I gave you quite a head start on the information part. If you don't want to take it further, quite frankly, that's not my problem.
LabVIEW has fantastic debugging tools (execution highlighting, probes, breakpoints, single stepping, etc.) That basically lets you do open brain surgery while the VI is running.
Once you become more familiar with them, finding most bugs is a cakewalk. 😄
