You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have 2 sample python measurements. One measurement has minimum controls (7), and the other measurement has more controls (23).
I converted the measurement configuration cluster in the measurements to gRPC message using Cluster to gRPC LabVIEW Message.vi and registered the messages using Register Message Metadata.vi and Register Enum Metadata.vi.
Then I packed the measurement configuration cluster using PackToAny.vim and tried unpacking the packed data using UnpackFromAny.vim.
The unpacking is successful when there are less controls, and it fails with '1097' error code when there are more controls.
Logic in the VI:
Unpacking for less controls:
Unpacking for more controls:
Repro or Code Sample
Run the python measurements in 'sample_measurement' (less controls) and 'sample_measurement - Copy' (more controls) folder. - Refer the below link to find the steps to run a python measurement: Steps to Run/Debug the Measurement Service
Bug Report
I have 2 sample python measurements. One measurement has minimum controls (7), and the other measurement has more controls (23).
measurement configuration
cluster in the measurements to gRPC message usingCluster to gRPC LabVIEW Message.vi
and registered the messages usingRegister Message Metadata.vi
andRegister Enum Metadata.vi
.measurement configuration
cluster usingPackToAny.vim
and tried unpacking the packed data usingUnpackFromAny.vim
.Logic in the VI:
Unpacking for less controls:
Unpacking for more controls:
Repro or Code Sample
Steps to Run/Debug the Measurement Service
Code to reproduce:
Test.zip
Expected Behavior
Unpack the packed data with no error for any number of controls in the cluster.
Current Behavior
Unpacking fails with '1097' error for a cluster with larger number of controls.
Your Environment
cc: @jasonmreding
AB#2905586
The text was updated successfully, but these errors were encountered: