My Scaling VI running slow

[GOB34]

Hi All,

I am using a structure similar to the QMH Continuous Acquisiton / Logging (DaqMX) template.

My data getting acquired goes into the display loop via a notifier.

When the data come in, I am scaling the analog ins with the subVI shown below:

The issue is is that this causes "hiccups" in my data being displayed - it is choppy.

Is there a better way to do this?

Thanks

Adding: this is the display loop showing the scaling subVI:

[altenbach]

We can rarely debug images.

What are these orange indicators in the display loop? (Just scalars?)

How big are these waveforms and other data structures?

How often does data "come in"?

[dsb@NI]

If the analog data is acquired using DAQmx, you can use scales to have the DAQmx driver scale the data to engineering units for you.

[GOB34]

Thanks Doug - I hate using max for anything.

i read in scale data from an external file that gets updated.

[dsb@NI]

---

@GOB34 wrote:

Thanks Doug - I hate using max for anything.

i read in scale data from an external file that gets updated.

---

You don't have to use MAX. You can programmatically create scales.


You could continue sourcing slope and intercept from the same file you use now. 

[GOB34]

I will try that!

if that is done, is it still possible to access the raw, unscaled data? 
I usually like to record both.

[dsb@NI]

---

@GOB34 wrote:

I will try that!

if that is done, is it still possible to access the raw, unscaled data? 
I usually like to record both.

---

You will only have access to the scaled data returned by DAQmx. Rather than record both scaled and unscaled waveforms, I recommend recording scaled waveforms along with sensitivity (slope) and offset.

[GOB34]

Really appreciate the help-

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

[dsb@NI · Accepted solution]

---

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

---

This implementation is better suited for multichannel applications.

and instead of "1X" or "10X" you might consider putting the sensor serial number (or some other identifier) as the scale name.

[santo_13]

My recommendation also follows Doug's. Using DAQmx's scales at the driver level is the best performant, scalable and robust, compared to recreate it yourself.