Data Not Executing

[sambpk]

Hello,

I am having an issue with my code after adding in the section with the two for loops and the two case structures. The code compiles and then executes only once then I probe the wires and it says not executed for everything. I tried probing multiple wires but the DAQ assistant itself is not being executed after the first sample. I also probed the column headers after adding two new ones and they show up on the probe but not on the table or the spreadsheet. I had no issue before with collecting data and then after I added that portion of the program it will on execute once. Does anyone have troubleshooting tips? The probing isn't necessarily working because the program isn't executing after the first sample. I attached an HTML because the program is too large to fit in one screenshot. 

[GerdW]

Hi Sam,

attaching a HTML file containing just a list of VI names is nonsense.

Attach the VI & attach example data files!

Use ZIP to easy up- and downloads!

(You should have learned this after all your other posts!)

[sambpk]

---

@GerdW wrote:

Hi Sam,

attaching a HTML file containing just a list of VI names is nonsense.

Attach the VI & attach example data files!

Use ZIP to easy up- and downloads!

(You should have learned this after all your other posts!)

---

Hi,

When I originally opened the HTML on my computer it showed the entire program and the front panel, not just a list of VIs. I attempted to do it this way because I have LabView 2020 and I often see a comment saying people with older versions can't open it. However, here is the zip of my program. I don't know what you mean by example data files. Again, I've never used this program before so I'm not an expert and I believed this forum was for people who aren't experts to ask questions without being yelled at for a mistake. 

[FireFist-Redhawk]

Hi sambpk,

We were all new at this once, no worries. The first that you probably want to do is make a project and add all those VIs into it. I personally prefer auto-populating folders for my project's structure. 

You are correct that people with versions less than 2020 will not be able to open it or therefore help you, so the next thing you want to do is go to File -> Save for Previous Version... in your project explorer window. Do all that (save for 2017 version) and zip and share, and you'll get the help you need.

[sambpk]

---

@FireFist-Redhawk wrote:

Hi sambpk,

We were all new at this once, no worries. The first that you probably want to do is make a project and add all those VIs into it. I personally prefer auto-populating folders for my project's structure. 

You are correct that people with versions less than 2020 will not be able to open it or therefore help you, so the next thing you want to do is go to File -> Save for Previous Version... in your project explorer window. Do all that (save for 2017 version) and zip and share, and you'll get the help you need.

---

Thank you, I tried this but the only options for previous versions are 2010, 2011, 2012, 8.6 and 8.0. Can I save it as an older version to be opened on a newer one or will this not work?

[FireFist-Redhawk]

Saving for 2012 should work

[sambpk]

---

@FireFist-Redhawk wrote:

Saving for 2012 should work

---

[GerdW]

Hi Sam,

---

@sambpk wrote:

I am having an issue with my code after adding in the section with the two for loops and the two case structures. The code compiles and then executes only once then I probe the wires and it says not executed for everything. I tried probing multiple wires but the DAQ assistant itself is not being executed after the first sample.

---

You VI does what you have it programmed to do. Unfortunately that is something different than what you want it to do…

THINK DATAFLOW! You really need to learn this mantra to master LabVIEW!

There are several loops set to run forever. Those loops are even stacked inside of each other.

This will prevent any DATAFLOW!

Btw. this VI (aka its block diagram) is way too big!

• Clean up.
• Use more (senseful) subVIs. (Some of your current subVIs are pretty senseless with only having one function in their block diagram!)
• Create a project file to organize all those VIs.
• And read the LabVIEW help entry on "DATAFLOW"!
• Learn to use the AutoCleanup tool: start with your current subVIs in using it.
• Remove all those silly nonsense sequence frames.
• so much more to improve…

[sambpk]

---

@GerdW wrote:

Hi Sam,

---

@sambpk wrote:

I am having an issue with my code after adding in the section with the two for loops and the two case structures. The code compiles and then executes only once then I probe the wires and it says not executed for everything. I tried probing multiple wires but the DAQ assistant itself is not being executed after the first sample.

---

You VI does what you have it programmed to do. Unfortunately that is something different than what you want it to do…

THINK DATAFLOW! You really need to learn this mantra to master LabVIEW!

There are several loops set to run forever. Those loops are even stacked inside of each other.

This will prevent any DATAFLOW!

Btw. this VI (aka its block diagram) is way too big!

• Clean up.
• Use more (senseful) subVIs. (Some of your current subVIs are pretty senseless with only having one function in their block diagram!)
• Create a project file to organize all those VIs.
• And read the LabVIEW help entry on "DATAFLOW"!
• Learn to use the AutoCleanup tool: start with your current subVIs in using it.
• Remove all those silly nonsense sequence frames.
• so much more to improve…

---

I unpacked several subVIs after having an issue so that I could easily see where everything was going as it was confusing me with the subVIs and the sequence frames showed up when I did that and I have been deleting them after I fix any problems associated with the subVI.

I have a user input for the timing control because my boss wants it to be different each time, I can't set a timing limit on anything because my boss told me not to.

I know how to use the cleanup tool, but I press it and it crosses or hides some wires that I needed to see so I leave it the way it is until I fix the issue at hand. I think we all have different preferences on how to code and how we learn from looking at things, I don't understand why you have to be so rude to me about every little thing. You make me worried to post a question, I sure hope you don't actually teach people because I don't think you believe in the no question is a stupid one.

I'm trying to learn what mistakes I'm making, I have read the file but I'm not going to be a professional at it by reading a file rather than doing. If you want to be rude to me every time I post something, I would rather you not respond at all and someone who is level headed can help.

[GerdW]

Hi Sam,

I'm sorry when you misunderstood my words, but my intention wasn't to be "rude"…

The main point of my last message was:

There are several loops set to run forever. Those loops are even stacked inside of each other.

This will prevent any DATAFLOW!