VeriStand

cancel
Showing results for 
Search instead for 
Did you mean: 

Custom Workspace Object "Forgets" Its Channel Mapping...

Solved!
Go to solution

Implemented changes for the custom data change. Worked. Now the channel mapping are saved once set. Thanks...

0 Kudos
Message 11 of 17
(2,608 Views)

Channels are saved, but now dial changes are not triggering channel changes...

0 Kudos
Message 12 of 17
(2,606 Views)

One needs to have all signals for CAN messages mapped to channel for the tranmission to work.

0 Kudos
Message 13 of 17
(2,599 Views)

Hello,

 

I'm having the same issue that you faced.

While creating a custom control for NIVS, I cannot save the bindings of the channels when I close the workspace of NIVS.

 

It seems that now you succeed to save channels mapping.

Could you please share an updated version of your VI in order to see how you did it?

 

Thanks in advance.

 

Regards.

 

PS : I attached my VI for information purpose (LV/NIVS 2013 SP1)

0 Kudos
Message 14 of 17
(2,156 Views)

Hello,

 

I'm new in VeriStand and Custome Objects and I have the same issue as described here. When I close the workspace an re-open it, all channel bindings gets lost. I have the same VI structure as gaetanR has prvided here.

 

Are there any solutions what's wrong in the VI? I'm using LabView 2015 / Veristand 2015 SP1

 

Thanks in advance!

Regards

0 Kudos
Message 15 of 17
(1,699 Views)

Hello,

 

I noticed that while you seem to be trying to do the same that is exposed in this tutorial, you have several differences, including initialization and user events usage. Can you try with the steps from the document?

 

You can actually upload the code and it would be easier for us to provide advice that with a screenshot. Smiley Happy

 

Regards,

Camilo V.
National Instruments
0 Kudos
Message 16 of 17
(1,682 Views)

Webserver81 maybe you already fixed your problem as your post is 1 month old. I upload here what I did to solve this issue.

 

I changed my Custom Data cluster to vehiculate the channel names in order to retrieve them from the initialization part of the vi. In the state machine part, the Custom Data shift register starts with the saved values. I just focused on the channel binding part, so I get rid of min/max parameters, etc.

 

It seems to work well like that except one point : I found out that when I deploy straight after adding my workspace object, only the first channel works properly. Then if I close the workspace and open it again everything works fine... This is strange (maybe you'll find out why when looking at my code) but not such annoying...

 

I hope it will help!

 

0 Kudos
Message 17 of 17
(1,603 Views)