LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Bug in "Unflatten from String" (LV7)

I have binary files with different versions of a certain datatype. When loading a file, I try to unflatten the data using the newest dataversion. If I get an error, I try the 2nd newest dataversion and so on until I found the right datatype. This methode was ok up to LV6.01.
Now I updated to LV7.0ger and I found following bug:
When unflatting certain binary datas from string I get an error msg window "Nicht genügend Speicher zum Abschließen dieser Operation". The error-output of the vi is incorrect.
Does anybody know a workaround of that bug?
You can test the bug with the attached vi. Include also the two typedefs.
0 Kudos
Message 1 of 4
(2,922 Views)
Hello Albertz,

This definitely looks interesting.

As with any potential bug, I would recommend contacting National Instruments tech support directly via email or phone (www.ni.com/ask) so that they can document and take action on the problem.

Liz F
0 Kudos
Message 2 of 4
(2,922 Views)
I allready told this to a NI tech support in Germany. They told me, the bug is known, but they do´nt have a workaround.
So I hope for LV7.1 or maybe LV7.01.
0 Kudos
Message 3 of 4
(2,922 Views)
Hi,

From the LV's help: "National Instruments recommends reworking any
application that uses the Convert 4.x Data mode as a long term solution.".

Data types may vary with differenct versions of LabVIEW. So, if types are
not the same, this does not need to be a bug. Right click the Unflatten From
String, and select Convert 4.x Data. This might not work, because the data
is stored with Lv 5 or 6, but when you get it working, it will keep working
for future versions of LV.

The attached VI shows that a sting in a cluster does not convert to the same
type string for lv4.x and lv7. Perhaps they are the same for lv4.x and lv6.
If so, using convert 4.x data would be sufficient. If not, you need to read
the data in 6, save the binary 4.x strings
, and use 4.x from then on.

You might also do the following: (also from the help) "If you use this
function to flatten data from a custom control or indicator that you saved
as a type definition, the function strips the type definition of its type
definition wrapper. If you do not want to strip this wrapper, right-click
the function and select Expose Typedefs from the shortcut menu."

Regards,

Wiebe.


"albertz" wrote in message
news:506500000005000000F84C0100-1073519706000@exchange.ni.com...
I allready told this to a NI tech support in Germany. They told me,
the bug is known, but they do?nt have a workaround.
So I hope for LV7.1 or maybe LV7.01.



[Attachment Different Types.vi, see below]
0 Kudos
Message 4 of 4
(2,922 Views)