From Friday, April 19th (11:00 PM CDT) through Saturday, April 20th (2:00 PM CDT), 2024, ni.com will undergo system upgrades that may result in temporary service interruption.
We appreciate your patience as we improve our online experience.
From Friday, April 19th (11:00 PM CDT) through Saturday, April 20th (2:00 PM CDT), 2024, ni.com will undergo system upgrades that may result in temporary service interruption.
We appreciate your patience as we improve our online experience.
05-11-2020 04:46 AM
I encountered unexpected behavior when trying to access Map values with For Loop. This is simplified code.
As you see, one value is added to empty map then read in two different ways. Surprisingly for me indicator value by loop receives no data while the map contains expected member and indicator key by loop receives correct key value.
LabVIEW 2019 64-bit
What do I do wrong?
Thank you.
Solved! Go to Solution.
05-11-2020 05:23 AM
I opened the same VI with LabVIEW 2019 32-bit. It works as expected.
Shall I conclude that 64-bit LabVIEW has a bug?
05-11-2020 08:43 AM
I have seen something similar when trying to use a maps on compactRIO. I am not sure if it is the same problem, but I got a hard crash of the application when running the following on a cRIO:
I did not dive into it any deeper, but the following work around solved the issue for me:
05-11-2020 08:49 AM
Yes, I solved the problem in exactly the same way. But it is a workaround that probably works at expense of performance☹️
06-04-2020 07:43 AM - edited 06-04-2020 07:44 AM
Seems the question is buried among pages of the forum.
I resurrect it reformulating the question.
Is it a LabVIEW 2019 64-bit bug?
06-04-2020 05:01 PM
It works for me in LabVIEW 2019 64-bit (SP1 f1).
06-05-2020 08:08 AM
Reading the 2019 SP1 Readme, it appears to have been fixed (ID 741225).
06-08-2020 10:50 AM
Probably this is the answer while LabVIEW did not crush in my case.