10-06-2013 11:25 AM
I am guessing that you need a solution quickly. Delete the bad wires and create an indicator. Let us know if the indicator matches your expectations.
10-06-2013 11:39 AM
Hi,
I tried what you say the indicator....and I need a quickly solution :S
But I want the table.. because the indicator I couldn't tried if it's works the same as the table.
Srry for my english and sometimes I couldn't undertood so good because I'm learning too.
thanks
10-06-2013 11:43 AM
Now wire the first build array into the second.
Change the empty array constant that initializes the shift register from a double datatype to a string datatype. Wire up to the table. (And get rid of the double array indicator.)
10-06-2013 12:22 PM
Thanks a lot, now i give you a kudo,
can you pass me the link of the tutorials please?
thanks for the help 😄
10-06-2013 12:23 PM
Sure. I'm glad you've got it worked out.
LabVIEW Introduction Course - Three Hours
LabVIEW Introduction Course - Six Hours
10-07-2013 12:27 PM
Hi Ravens,
One little question, why in the excel don't separate with two columns?
I use this.. http://zone.ni.com/devzone/cda/pub/p/id/1339
10-07-2013 12:53 PM
Your file opens up with data in 4 columns for me. I looked at your raw .csv in notepad. It appears to me that you might be using a comma as a decimal point rather than a true decimal point. Is that so?
If so, then your "decimal comma" is being confused as separator since you are using a comma as a separator.
I'd recommend converting your numbers to strings using a decimal point. Alternatively, you could use another separator besides a comma (perhaps a tab) when using the Write to Spreadsheet File VI.
10-07-2013 01:12 PM
No, the file opens data in One column I put you a picture about this, and I want to in two columns
The "Bad" picture is what happens now.
The "I want" Is what I want to do...
I tried different methods and this works better than the others but I don't know how to separate in two columns :S
10-07-2013 01:50 PM
Well, you still have that decimal comma problem to solve. You can't use a comma as a delimiter if you are also using it as your decimal point.
The second problem is actually a problem with Excel. If you just open up a text file in Excel, it makes an assumption as to what the delimiter is and how many columns to display. I usually find that Excel guesses wrong. If you open up a blank Excel sheet and Import the file in, it gives you a dialog box where you can go through and say it is delimited, and say the comma is the delimiter, then it will put it in separate columns.
After the fact, you can use Data menu, Text to Columns menu choice to convert what you have now into multiple columns.
If you can fix your number to string conversion to use a period for a decimal point, that will help a lot.
Perhaps you need to try to set the tab character as the delimiter. You'll wind up with a "tab separated value" file rather than a "comma separated value" file. But I think in this case, Excel makes a better guess on the default importing functions and will separate it into columns.
10-07-2013 02:03 PM
Yes I agree with you...I use the Tab (/t)
and pass the same as the coma and point.
"But I think in this case, Excel makes a better guess on the default importing functions and will separate it into columns"
I tried to do this with a property node with export to data from table and the result is bad because only takes the first row the fisrt column :S