LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

My Scaling VI running slow

Solved!
Go to solution

@UliB wrote:

@GOB34 wrote:

I have what I think is the correct structure for the overall VI but I am running into what I think is a basic indexing issue where I am not filling the cluster in the first for loop.

Try to change 'ChannelsAndCalibrations' constant from array to element. 

Right now you have 8 indexing input tunnels and the one with the lowest number of elements controls the loop count, which is 0 from the array constant.


right on!

Doug
NI Sound and Vibration
0 Kudos
Message 21 of 36
(216 Views)

pull the cluster out of the array

dsbNI_0-1726073777503.png

 

Doug
NI Sound and Vibration
0 Kudos
Message 22 of 36
(214 Views)

Thanks Doug - could you see my question on how to properly do this - I replied just as you were replying!

0 Kudos
Message 23 of 36
(210 Views)

@GOB34 wrote:

Thanks Doug - could you see my question on how to properly do this - I replied just as you were replying!


It is tough to describe as it is a finesse mouse gesture. Try selecting the cluster in the array constant. Ctrl drag the cluster out of the array.

Alternative:
Drop a new instance of your cluster typedef on the diagram and use that as the template when bundling the configuration cluster.

Doug
NI Sound and Vibration
0 Kudos
Message 24 of 36
(202 Views)

like this?

 

GOB34_0-1726074023370.png

 

0 Kudos
Message 25 of 36
(200 Views)

@GOB34 wrote:

like this?

 

GOB34_0-1726074023370.png


yes

Doug
NI Sound and Vibration
Message 26 of 36
(199 Views)

EDIT;

 

disregard, I had forgot to wire something!

0 Kudos
Message 27 of 36
(179 Views)

I am running into a problem in that after I create these channels with the custom scaling, I get an error that the read has no physical channels specified.

GOB34_2-1726078083140.png

 

Shouldn't the physical channels I specify when I create channels carry over to the start task via the task reference?

 

GOB34_1-1726078037991.png

GOB34_0-1726078453652.png

 

PID scale SubVI:

 

 

GOB34_0-1726078009409.png

 

0 Kudos
Message 28 of 36
(174 Views)

Figured it out!

 

Had to update my Hardware cluster with the new task info in order to send all that new configuration to the acquire VI!

 

GOB34_0-1726078862865.png

 

0 Kudos
Message 29 of 36
(162 Views)

Hi Altenbach -

 

Would you recommend changing the method of indicators?

 

Thanks

0 Kudos
Message 30 of 36
(68 Views)