12-28-2022 02:22 PM
Hi, I updated LabVIEW 2022 Q3 over the past couple of months, and the One Element Stream-str library's Channel.vi in 32-bit LabVIEW seems to now be broken from what was working in LabVIEW 2021. I tried today to update to Q3 Patch 1, and it's still broken. I'm running it on Windows 10. Could someone look into this or provide a workaround?
Solved! Go to Solution.
12-28-2022 03:07 PM
In order to try to reproduce (and understand) the problem, please provide us with your LabVIEW code that (a) works in LabVIEW 2021 and (b) fails in LabVIEW 2022. Seeing the code that LabVIEW generated doesn't allow (I was going to say "us", but I'll say) me to "guess how you did this".
Bob Schor
12-29-2022 12:12 AM
I created a one element stream channel from a string and it is not broken in my LV2022Q3. I would mass compile and check if the outcome shows any corrupt VIs and fix them.
Or are you getting this if you create a channel writer from an empty VI, with ExtraVILIb empty? First, in your documents folder delete \LabVIEW Data\<version>\ExtraVILib\ChannelInstances and then start LabVIEW, then, create a new VI, and in it create a one element stream channel to see if that works at least.
12-29-2022 12:28 PM
I tried deleting the ChannelInstances folder, but now it's gone and I can't create a new VI with a One Element Channel. I'm trying to rebuild it with LabVIEW package repair.
The VI I'm referencing is a subVI to Read Endpoint - NI . The VI should be available in your LabVIEW 2022 Examples in \National Instruments\LabVIEW 2022\examples\Channels\Basics\
I think the issue is tied to a new Windows profile configuration on my computer that puts the Windows account profile on a server rather than the local machine. Now, the same VI in my LabVIEW 2021 folder is broken too. Does LabVIEW 2022 recreate this "\LabVIEW Data\<version>\ExtraVILib\ChannelInstances" folder every time the "My Documents" folder is accessed, or is it created during the LabVIEW 2022 install?
12-30-2022 12:14 AM
01-03-2023 07:43 AM
I still ran the LabVIEW repair tool to repair my LabVIEW core libraries, but it appeared to rebuild ChannelInstances as you described when I reloaded the project. Thanks for your help!