Write Delimited Spreadsheet without rows in blank

[jesusglzFELE]

Hi all!

I made a program that when a DAQ recieved a signal the Date and number are saved in a Spreadsheet

This just should save the values in true, but when I see the file, it have rows in blank

I would like save the records without rows in blank.

Can you help me?

I attached the code and the file

[altenbach]

Can you "save for previous" before attaching. (I cannot open LabVIEW 2021 VIs.)

[jesusglzFELE]

I attached the version 19, or what version do you need?

[Bob_Schor]

You asked (and I answered, I thought) an earlier Post regarding writing Delimited Spreadsheets.  Did you try the Example program I showed you?  If so, you would have seen a .CSV file with no blank spaces.

Did you use a Text Editor (not Excel) to open the CSV file you attached?  Did you see what was in the "blank lines"?

Your LabVIEW program is doing exactly what you told it to do.  You are putting an extra <CR><LF> in every input, and LabVIEW is writing both the line with three Entries and the line with 0 entries, which shows up as a Blank Line.

Try the following -- replace the Control "Number" with a String Constant, make it "Test" (it's a String, after all, it doesn't need to be a number).  Examine the resulting CSV file.  Now think about it, see if you can figure it out.

Incidentally, if you need more help on this problem, don't start another Message, but simply Reply to this one.

Bob Schor

[altenbach]

Works fine here...

Some comments:

1. Never delete the label of terminals (e.g. the stop button). If you don't want to see it on the front panel, do a "right-click..visible items...label" and uncheck it). Terminals without labels are a nightmare on the block diagram.
2. Your "message" terminal (Please don't hide the terminal label!) belongs after the case structure to be wired from within all cases. no local variables needed. Same for the "3.-wait" indicator
3. The "disabled" property node belongs after the case structure. Only one instance needed
4. Make sure your "2.-Number" control is set to single line (right-click...). If not, hitting enter after a number could give you additional linefeeds.
5. I don't quite see the logic in your overall code. seems fragile and convoluted.
6. Keep front panel and diagram to a reasonable size. Maximized to the screen is not reasonable. Don't set some gigantic minimum pane size for the front panel.

[jesusglzFELE]

I'll take in count your comments

I starting to learn the enviroment on Labview, thats why maybe my code can looks "seems fragile and convoluted"

Honestly I don't know why the size of he front panel is to big, for some reason turns in that size

And the comment 4 was the solution, I'll try to improve the code

Thanks!

[BertMcMahan]

---

@jesusglzFELE wrote:

Honestly I don't know why the size of he front panel is to big, for some reason turns in that size

Thanks!

---

I was about to say "Go to File, VI Properties, then Window Size and change it there" but then I looked and it's already set to a 0,0 minimum panel size. I dug in and found a new setting I didn't know was there- right click on one of the scrollbars, then click "Properties". You've somehow set the minimum pane size to 2539 x 950. Change that to 1x1 and you can now shrink the size of that pane.

(I've never needed a specific pane limited in size, only a panel- TIL you can control both. Neat :))

[altenbach]

Yes, Setting the minimum pane size for a single pane front panel window boggles the mind. I guess you found that somewhat hidden option when selecting the glaring background image tiles. You should only worry about cosmetics after the code is fully debugged and is near completion.. 😄

[jesusglzFELE]

I'll keep that in mind, thanks for the advice