Ah, now we are getting somewhere! You've put "units" on your values (a very helpful thing for the "human" looking at the code, and not at all a problem for LabVIEW, which can handle and interpret many representations of data).
So here's a question: Are your Time values (e.g. 18:00) meant as "time of day" (so it would be 6 p.m.) or as time invervals (where it might be "18 hours from some arbitrary starting point)? To me, the "sensible" answer is the first, but that has a direct input to what I'm about to suggest. A related question -- do you only have 4 fixed intensities (0%, 25%, 50%, and 100%)?
I'm going to assume "sensible" answers to both questions. I'm also going to assume that once you start this thing, it will run until you say "Stop" (i.e. it might run for a year or more without changing any parameters, and if you want to change a parameter, you'll stop the program, change, and start it again).
OK. So you need an association between "TOD" (Time of Day) and "LED %". Sounds like a Cluster to me. And you need several of these with different values. Sounds like an Array (of Clusters).
How should TOD be represented? By a TimeStamp, of course, that shows Time only, in 24-hour notation. How about LED %? The most "User-Friendly" way would be a control that takes on the values "0 %", "25 %", "50 %", "100 %". This is called an "enum" (for enumerated variable).
So I made a Cluster with a left element Time Stamp (called "When") showing HH:MM and a right element enum (called "LED %". I made an Array of this Cluster and made it 6 elements long with the "When/%LED" values you showed (leaving out 24:00, as it's the same as 00:00).
So now you have an Array of times you want to "do something", based on a 24-hour clock. What do you do? You periodically "check the time", and if its within (some distance) of one of your "When" values, you set the LED according to the corresponding LED %. How often do you check? How about once a minute? How do you (easily) compare two times, "When" and the current time? Ah, that's a little tricky.
Oh, dear. I think I might have found a "flaw" in the LabVIEW Time routines (and it was going so well, why did I have to try it out, myself?). I'll tell you where the problem lies -- I made "When" a TimeStamp, but didn't specify the date, so it made it "0", or 1 Jan 1904 UTC. 00:00 become (for me) 19:00 31 Dec 1903, which is fine. But when I ask LabVIEW to take the TimeStamp and give me the Hour and Minute, instead of 0 and 0, it gives 19 and 0. That's a bug. I'm thinking how to program around it (the easiest way is probably to add a days-worth of seconds to the time, but now it is super-messy, and dinner is almost ready).
Otherwise, the code is simply this: Have a While Loop that "runs until you push Stop" (or almost "forever"). Put a "Wait 1000 ms" clock inside so you waste very little time. When it "ticks", convert seconds to Date/Time, which will give you a Cluster, one element of which is Seconds, one is Minutes, one is Hours. If Seconds = 0, see if Minutes and Hours are in your list of Times (if you make "When" not a Time Stamp, but "Hours" and "Minutes", or just "Hours" if you don't need minutes, the Problem in the preceding paragraph goes away!). If they are, use the corresponding value of LED %.
Whew. Dealing with "Clock Time" is always tricky, even in LabVIEW. Have fun, good luck.
Bob Schor
