LabWindows/CVI

cancel
Showing results for 
Search instead for 
Did you mean: 

Labview Windows: Byte-order issues (little and big "endian")

Can someone explain or answer the following:

1) When Labview was ported to Windows (or intel-based systems) why
didn't they change the byte-order for variable storage to be
compatible with the low-byte/high-byte order that was (is) the
standard for representing numbers on systems using Intel-based CPU's
???

2) Is there a "switch" or meta-command or some other statement for
telling Labview-windows to use low-byte / high-byte order when
compiling or running a labview program?

3) Is it just me, or does National Instruments fail to mention or
discuss this glaring incompatibility (in such terms) caused by this
byte-order issue in it's various on-line documents / faq's /
Knowledgebase?
0 Kudos
Message 1 of 5
(4,632 Views)
There is a shipping document with LabVIEW help that discusses this called LabVIEW Data Storage Formats. There is also many things in our Knowledgebase about this. This was also discussed a while ago in the LabVIEW forum on this site, you can read that discussion here.

Best Regards,

Chris Matthews
National Instruments
0 Kudos
Message 2 of 5
(4,632 Views)
Chris Matthews wrote
> There is a shipping document with LabVIEW help that discusses this
> called LabVIEW Data Storage Formats. There is also many things in our
> Knowledgebase about this. This was also discussed a while ago in the
> LabVIEW forum on this site, you can read that discussion
> (etc)...

It seems that the thread you mention was not concluded satisfactorily
for Greg McKaskle or Eric (the OP).

What I read from it is that people have to impliment cumbersome and
in-elegant solutions to overcome the bone-head decision by National
Instruments to keep the Motorola/Apple byte-order sequence when LV was
ported to Intel-based computers running Windows.

Dumb Dumb Dumb.
0 Kudos
Message 3 of 5
(4,632 Views)
One of the drawbacks of designing LabVIEW for multi-platform is we can only have one of these formats and still have the files and VIs transferrable between platforms.
0 Kudos
Message 4 of 5
(4,632 Views)
Okay, but how about an easy conversion vi so data files can be saved in a format that other windows programs can read?
0 Kudos
Message 5 of 5
(4,632 Views)