My Scaling VI running slow

[Bob_Schor]

---

@GOB34 wrote:

Each of my channels has a different scale factor. It seems really messy and cluttered to have to use this approach for many channels.  

---

If each channel has a different scale factor, you have (however you choose to handle it) a "messy situation".  You are going to have to apply "scaling" to the data at some point, either before acquiring/saving it or after acquiring, applying the scaling when you attempt to analyze the data.

I've tried both ways, and strongly support figuring out the scale factors before starting acquisition and applying scaling in defining the various A/D channels, so that what I saved were are all in the same units, able to immediately be plugged into analysis routines because they were all in physical units.  You will, of course, want to save a small "configuration" file that allows you to "track" the calibration data that you (should have) used to set the scale factors.  If you are using Sensor A, then all of the Calibration files should be consistent, allowing you to trust the data saved as "Gallons/minjute" or "Degrees Celsius" or "Acceleration in g's".

Bob Schor

[GOB34]

This is a great help, thanks Doug.

One question - are the Min and Max values going into the "daqMX create channel" in the raw units (i.e. Volts) or the scaled units (i.e. pressure)?

Thanks!

[altenbach]

Compared to anything else going on in a typical program, a simple linear scaling of data is virtually never a bottleneck, so I don't understand what's going on here.

I still don't know what these indicators are (they look like scalars), so why manipulate all these raw waveforms if we are not even interested in t0, dt, and most of the [Y] except one? (They can't be charts, else they would be brown)

[dsb@NI]

One question - are the Min and Max values going into the "daqMX create channel" in the raw units (i.e. Volts) or the scaled units (i.e. pressure)?

scaled units

[GOB34]

Hi Altenbach-

I appreciate the question-

I use the timing data elsewhere in the VI, like for logging.

[altenbach]

---

@GOB34 wrote:

I use the timing data elsewhere in the VI, like for logging.

---

I was not asking about timing, just about these indicators.

[GOB34]

Yes, these are just indicators.

[GOB34]

Thanks for the continued help.

One stumbling block I am running into is assigning all the channel names, slopes etc to the cluster - see the attached VI.

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.

Thanks for the help!

[UliB]

---

@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.

[GOB34]

I appreciate the reply UliB -

Sorry if I need a little more help implementing what you say - 

this is what I want my "ChannelsAndCalibrations" to be, with values filled in:

So right now it is a 1D array of a cluster of 7 elements.

Can you explain a bit more to help me change this setup?

Thanks!