Matlab *.mat / LabView *.mlv

Question

Comparison:
test code in Matlab: 
AA = [1 2 3 4 5];
save AA-matlab.mat AA; 
and test code in LabView MathScript Node
AA = [1 2 3 4 5];
save 'AA-LV-matlab.mat' AA;
Both scripts make a file, but different files.
File made using LabView is NOT readable in Matlab! Save in LabView is not same as save in Matlab. Why this incompatibility? How to make compatible files?
Check Spelling in this editor gives suggestion LabView > Labile.  True?

Answer 1

Danigno wrote:
VesaU,
actually what I think he tried to say is that you can still use MatLab, but save your data from LabVIEW in txt files (which can be read by MatLab later). Then you won't need to use the MathScript, just regular LabVIEW coding...
Yup, that was exactly what I was saying. Thanks for the clarification. 
VesaU wrote:
Just saving a vector to a .mat file? Yes this is
my target. Why? Let's assume that we have raw data files from two
NI6259. We may get 2 million samples/second. A short test gives me
100MB or more data. Saving data to text file for exporting to
Matlab-analysis is not very good idea. Why Matlab? Matlab is widely
used for mathematical analysis. We use Matlab and our partners use it.
I tried to say that TXT file method is not a
method for today or tomorrow. I have used that 1990's. It is almost
same as pen and paper. Something better I want for tomorrow.
TXT file is OK, if it is used once in a year or month. For daily work it is not a solution.
Solutions for tomorrow may be:
1. Matlab reading directly LabView data files.
2. Converting
LabView data files (TDM/TDX files) to MAT files. Mat file with all
relevant data from TDM/TDX file into a Matlab Struct.
You're starting to be a little defensive here for no reason. You had provided NO information as to what you were saving, or how much data you were saving, and to belittle a suggestion that was based on virtually no facts is like biting the hand that tries to feed you. Not a very good way to make friends.
As pointed out by Danigno, I wasn't telling you NOT to use Matlab, but rather to change how you were saving the file since the data was apparently (though I'm wasn't sure since you provided no information) being saved in LabVIEW. Obviously, saving data as a text file for that amount of data is not warranted. If you were still going to collect the data in LabVIEW then a binary file would be something that can be used by both LabVIEW and Matlab, though you have to watch the endianness since LabVIEW defaults to big endian, and I believe Matlab defaults to little endian. 
2. Change from NIDAQ to NIDAQmx was not a success
story. Now we have four times bigger datafiles in Matlab
because NIDAQmx uses longer numerical expression than earlier. Old
NIDAQ we use with PCI and PCMCIA cards but new USB hardware forces us
to use NIDAQmx.
I don't understand what you mean by this. What functions were you using, and how were you saving the data? 
I have asked help from MathWorks and National
Instruments to solve the problem. Both companies say that the fault is
on the other side. I think that both companies should face the truth.
It should not be end user's problem. It may happen that end user find a
third software + hardware which is working. I think that it is easier
to change DAQ than analysis package.
I'm not here to defend either NI or Mathworks, but I think that's debatable.