Using JSONtext in a packed library for RT.

[bbergdoll]

Has anyone attempted and been successful in using JSONtext within a packed library on RT? Building the same vi targeted for Windows works fine and using a vi with JSONtext in RT development also works. However, we are getting LabVIEW: (Hex 0x2A) Generic error when attempting to deploy any packed libraries which contain JSONtext vi's. Believe this is a LV issue and NI support has duplicated the issue, but is pointing the finger at the Pretty Print function. Since this library is so useful and used by so many, we are hoping that someone has run into the same issue and maybe come up with a solution. 

Versions:

JSONtext - 1.7.0.118

LV and LVRT - 2021 SP1 

[sekel]

Yes, I was able to work around this issue. I was getting the same error message on deployment (although sometimes the error occurred and did not report on deployment). The error would always post to the display port. Hint: The number of posts to the display port closely resembles the number of instances that you will need to look for in your code. 

It seems the problem is using a malleable VI (VIM) that has a class input (LVClass Serializer). If you right-click on the malleable VIMs after you wire them on your block diagram and convert them to a standard VI, you should have success deploying the PPL to the real-time target. 

Note: This issue has been reproduced with other malleable VIMs (not in the JSON add-on) that have a LV class input ("Search Unsorted 1D Array.vim" for example). In all instances, so far, converting to a standard VI has yielded success.

[nwford_he]

I am also having issues with using the json toolkit in a RT environment. I am trying to use the "From json text" VI on the processor side of a cRIO. The code deploys fine, but when I hand this block a json string it just spits out default data. However, if the processor is running by itself, and no other VIs on the computer are running, it seems to work fine. But once I run a VI on the PC that is meant to send the json string down to the processor, the processor can no longer parse the string, and just spits out the default. I tried converting the "from .json text" block to a Standard VI, but that seemed to have the same behavior. Images attached to show the behavior I am talking about.