Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

UnpackFromAny.vim throws error '1097' when unpacking the packed data for a larger number of controls #392

Closed
varshini-senthil opened this issue Oct 15, 2024 · 1 comment
Assignees

Comments

@varshini-senthil
Copy link

varshini-senthil commented Oct 15, 2024

Bug Report

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:
image

Unpacking for less controls:
image

Unpacking for more controls:
image

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
  • Run the 'Unpack.vi' and 'Unpack-error.vi'.

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

  • OS & Device: Windows 10
  • Measurement Plug-In SDK Service version: 3.1.0.5
  • LabVIEW version: 2021 SP1

cc: @jasonmreding

AB#2905586

@jasonmreding
Copy link
Collaborator

This should be fixed in #387

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants