Impact of using Custom Scale, Table type

[Broken_Arrow]

I recently ran across a program that had many custom scales seup in MAX. Some of these custom scales were simple two values making straight linear lines (which in that case I don't know why you'd use a custom scale, but that's another story). However, some of the scales are the the "tabled" variety, containing 40 or more values. My question is, what is the impact on the code when using these type of scales? Where do those 40+ values end up in the code? I guess DAQmx ends up using what equates to a lookup table with curve fitting between the values. This can't be free.  Is this an array that LabVIEW has to carry around?

thanks for any insight.

Message Edited by Broken Arrow on 03-18-2009 11:00 AM

[Smootastic]

Hi Broken Arrow,

That's a great question.  I took a look at the DAQmx Create Channel VI (where you specify the custom scale) and it gets passed to a Call Library Function Node.  So what's probably happening is that the array remains in memory while the task is running.

[Broken_Arrow]

Thanks for responding, Kyle.

That's sounds reasonable, and not too horribly expensive if the array size is reasonable.

So, besides carying around the array, it (DAQmx) also has to do curve fitting. It works fine and is certainly handy, but there's a lot going on behind the curtain.

Message Edited by Broken Arrow on 03-20-2009 09:24 AM