I am able to save data to a file (csv), but my data does not look right? Can someone please help?

[GRCK5000]

My goal is to create a file every whatever time I set (in seconds).

Everything works fine, the problem is just the data structure on my file does not look good. What am I doing wrong? I have attached my vi

P.S.: I would like to use "Write to text file" block. I'm not trying to use a different VI/block such "write delimited spreadsheet"

[mcduff]

Write the header just once, when you make the file for example.

[Jacobson-ni]

In the VI you attached, you are generating new data ever 1 second and appending it to the end of your 2-D array but you are also writing the entire header + 2-D array to your text file every single iteration.

One way you could fix this would be to write the header when you create the file and then in your write data to file loop only write the array of three random numbers each iteration so you're basically adding a row to your file every iteration.

[GRCK5000 · Accepted solution]

I think I solved the problem.

[billko]

---

@GRCK5000 wrote:

I think I solved the problem.

---

Remember this is a forum where people come to get answers.  How does your solution help others?  Consider that you wouldn't mark a post like that from someone else as the solution.

Would you mark mine as a solution if I merely posted, "Hey I have the solution for you."  Of course not.

[GRCK5000]

Sorry about that, Billko. You are so right. Not showing others what to do would be very selfish of me. I'm not like that. I love helping and sharing with others because I've been helped so many times as well. So I attached the code.

[GerdW]

Hi GRCK,

why do you need to use a local for the file ref? Why not use a shift register?

[GRCK5000]

Hi GerdW,

I am so used to local variable because I think it's a shortcut. Shift register can be annoying something especially if you have a state machine with multiple states. 

[GerdW]

Hi GRCK,

---

@GRCK5000 wrote:

I am so used to local variable because I think it's a shortcut

---

They are no "shortcut". And you should have learned that from all your previous threads…

---

@GRCK5000 wrote:

Shift register can be annoying something especially if you have a state machine with multiple states. 

---

Why?

• All you need is one (1) shift register to hold all relevant information, no matter how many states you will have…
• You can even create linked tunnels for your shift register wire to minimze wiring work…
• Shift registers create very efficient LabVIEW code…

[GRCK5000]

Thanks GerdW,

I’ve been thinking about staying away from local variables. I noticed it is not as efficient as shift shifters when passing data. 

also not as good as queues when passing data between two parallel loops. Local variables have the tendency to lose some data; whereas queues will make sure you get all your data. I definitely should stay away from local variables. I remember being yelled at so many times about avoiding using local variables unnecessarily.