05-07-2010 06:53 AM - edited 05-07-2010 06:56 AM
What development version of LabVIEW are you using? Student Edition, Base Package, Professional?
When you open LabVIEW, simply look at the splash screen, you should see a message like this one:
Some versions do not support what I may propose..
So far it does look like a State Machine is what I would recommend. Will there be much interaction from the Operator (other than selecting which screen to look at?)
05-07-2010 01:16 PM
Thanks agian for both your comments, Ya same message pops up, LabView Pro Development System.
Sorry for late reply i'm going to be locked into study till monday evening, big exam 😞
Will have to put this project on pause until then....
I'm gonna need a few 10 day weeks for the next month !! 🙂
Talk soon...
05-07-2010 02:23 PM
Simone 27 wrote:Thanks agian for both your comments, Ya same message pops up, LabView Pro Development System.
Sorry for late reply i'm going to be locked into study till monday evening, big exam 😞
Will have to put this project on pause until then....
I'm gonna need a few 10 day weeks for the next month !! 🙂
Talk soon...
10 day weeks are no problem Simone. But I'm afraid you'll only get 3 of them per month.
05-10-2010 07:11 AM
That's good that you have the Pro version.
That means we can consider Event Structures.
Good luck on the exam.
05-12-2010 09:11 AM
Thanks Ray,
Exam was ok, lots to do for next week though....ah well it'll all be over soon 🙂
Event structures?
05-13-2010 07:19 AM
Event Structures are great to handle user events (such as making a selection or entry, press a button), while other portions of the code execute. I would not necessarily use it if the User interaction is simply selecting different screen, but then again, I might 😉
I can explain how to use Event Structures. They are easy to use.
05-13-2010 07:50 AM
Ya they sound like the way to go then 🙂
The project will be tested by changing some of the values out of tolerance and seeing if the right alarms go off on the client panels.
Sorry i disappear for a few days, got like 8 other subjects in my full time course and 3 in a part time one i've been doing all year to either study for exams or finish off projects for, aaahhhhhh 🙂
Two courses in the same year turned out to be a bit too much.....
05-13-2010 09:16 AM
So far, you've got the Requirements Specs.
So now it's time to define the architecture.
It appears that an Event Structure as the Producer in a Producer / ConsumerDesign Pattern would be the way to go.
You can have a look at the template (File menu > New > Template > Producer Consumer Design Pattern (Events) ).
At this time, you should also identify the subVI (functions) which are listed in your Requirements Specs.
You can also mention "hooks" (sub-vi templates) that are optional to this project.
You can even have pseudo code or a state machine that describes the behavior.
Prepare this, and we'll go to the next step. We're getting closer to the coding part.
05-13-2010 10:01 AM - edited 05-13-2010 10:02 AM
Will the fact that i only have the DSC module make any difference to this method, up until now i've been just creating I/O server panels and using shared variables to create a different client panels in a project.
By identifying functions do you mean just list what i want the vi to do on paper. That probably sounds like a daft question....
05-13-2010 10:23 AM