start stop event structure queue

[nousername]

Thanks again Lucither,

However, when I try to open, it still says its v9 - could you have zipped up the wrong files?

Ill keep plugging away at the LabVIEW design patterns - I actually enjoy it quite a bit. Other SW engineers Ive spoken to are quite polarized re: LabVIEW and traditional coding languages (C/C++) but so far, I can appreciate both.

[Lucither · Accepted solution]

Hi Nouse,

Sorry for the problems. Not fully sure what i did wrong that time. Lets try again, dont hesitate to get back to me if its still not working. There is a thread on here that you can go to to downconvert your vi's if it continues to have a problem. Im sure we can work it out though.

I have experienced the same feelings from other SW engineers also. I personally have used both forms of 'C' for many years as and electronic engineer designing embedded controllers. I started using VB.Net many years back when i needed to interface any boards i had designed with a computer. I had heard of Labview but never really tried it until one day i decided to try an evaluation copy as i was bored one weekend. At first, like many SW engineers i suspect, I tried to use it without really learning about it and was trying to write code the same way as i was used to in 'C'. I met with the same frustrations you have experienced. That week i ordered 'Labview for Everyone' and also the 'Labview Style Book' by Peter Blume. The first book proved an excellent place to start and the second book i still go through on a regular basis as it has proven to be full of good advice. Even though a book just on coding Style might not seem as important as others this book has actually helped me the most out of everything i have read and would highly recommend it.

Let me know if you have the code this time. We will get it right eventually. Worst case scenario is that i can send you jpegs of all the other cases. There isnt that much so it wont take me long.

Rgs,

Lucither

[nousername]

Thanks again Lucither,

It loads now, however seems to want the Event Data Nodes in each case of the event structure to be wired to something: Error message "Event data node contains unwired or bad terminal". Im rather new to event structures so am not sure what to do there. The last error refers to the event structure and says "one or more event cases have no events defined". I fear that something did not translate back to 8.5.1 correctly, as the event structure appears to have 3 cases but their names are blank. There appears to be an even case which is not doing anything (in btwn the "open file" case and the exit case) - the error dissappears if I remove this case. Any ideas?

Sorry to keep bothering you!

[nousername]

OK - I was a bit quick to reply on the last one. I just re-added the start/stop value changes as "events handled by this case" and removed the extra event case. It works great now. Your help is much appreciated!!!
Thanks, too, for the book recommendations - Ill check 'em out.

[Lucither]

Its no problem. I have experienced this before, when i save a version to an earlier version it sometimes omitts the event case handlers. Basically you have 3 events in the event case. All you will see is [0], [1] and [2]. in :

[0], make this case the 'Timeout' handler. Right click on the event number. Goto 'Edit events handled by this case', then select <Application>, then Timeout.

[1], make this the 'Start' button event handler, select 'Value change' event

[2], make this the 'Exit' Event handler, select the 'Value change' event.

I have tried to correct and attach to this post but if fails again follow the above directions. Dont worry about bothering me, i lead a fairly uneventful life, Unfortunately though i wont be able to get back to you for about 8 hours as i am just off to sleep.

I have just attached what i beleive to be a working version of the Main Datalogger VI. Just replace this with the Datalogger VI in the project i sent you. 

Rgs,

Lucither

[Lucither]

Thats great. Just a quick point though. Its ok i suppose to get rid of the Timeout case as it should never execute but the 'Stop' event case is actually the 'Exit' button event case. I changed the stop button function in your vi to stop collecting data. If you use the stop button in this event it will Stop and Exit the Vi. The Stop button does not have an event case as the button is only enabled whilst the data acquiring is running. Change it to see what i mean. if you dont like it then just change it back to how you want.

Rgs,

Lucither