Writing 2D double precision data to binary file broke upgrading from 8.2.1 to 8.5?

[MF]

Just to add my woes to this scenario, I had code that I thought would write binary files correctly when the files became too big for excel (about 64k lines). Time, data1, data2 for each line. After many months, I finally had files big enough that they went into binary mode. Unfortunately, all I received were zeros in the data file.

When using any type of array manipulation (transpose, index array, array subset, etc.), only zeros were output. Very surprising that this bug crept into 8.5 and still no fixes. What happened to my favorite support company on the planet? Anyway, i have included a simple example. I know it repeats other people's work but another sample might get a company moving to fix this problem.

froeh

[MF]

Just to add my woes to this scenario, I had code that I thought would write binary files correctly when the files became too big for excel (about 64k lines). Time, data1, data2 for each line. After many months, I finally had files big enough that they went into binary mode. Unfortunately, all I received were zeros in the data file.

When using any type of array manipulation (transpose, index array, array subset, etc.), only zeros were output. Very surprising that this bug crept into 8.5 and still no fixes. What happened to my favorite support company on the planet? Anyway, i have included a simple example. I know it repeats other people's work but another sample might get a company moving to fix this problem. The fix with a flattened string worked great. Thanks for those that posted this work-over.

froeh

[altenbach]

An simpler fix is the insertion of "always copy" as described. Have you tried?

[TCPlomp]

If I run your example I have 3 files of 4.000.000 bytes with actual data inside it.

Ton

[altenbach]

---

TonP wrote:

If I run your example I have 3 files of 4.000.000 bytes with actual data inside it.

---

Actually, here too. I guess this got fixed in 8.5.1 😄

[MF]

Ok,

I have checked into upgrading top LV 8.5.1. Unfortunately, NI has decided to charge for version upgrades that fix problems in their release versions. I will go to 8.6 in the future. I have looked at the"always Copy" function and have included it in the example code attached. It works great and looks better that the "Flatten to String" function but is a little more mysterious because it is so new. It does gets you looking at the "Memory Control" panel however and that is a good thing. Have a great LabVIEW day!

Michael