Why won't my charts continually update while running a case structure?

[altenbach]

---

Robert Cole wrote:

Altenbach, I'm shocked! When I look at mine it says that it was converted to 8.5.1f4. Have you not installed the LabVIEW bug fixes?

Amazing (if it's true).

---

I must be completely in the dark, because I have never heard of 8.5.1f4. 😄

Are you sure you're not talking about 8.2.1f4?

[RobCole]

---

altenbach wrote:

I must be completely in the dark, because I have never heard of 8.5.1f4. 😄

Are you sure you're not talking about 8.2.1f4?

---

Quite sure. I have 8.2.1f6. Here is the link to the update for 8.5.1:

http://joule.ni.com/nidu/cds/view/p/id/1137/lang/en

Part of my job here is to ensure that all of the developers' systems are kept up to date for all the fixes and drivers, so I watch the update site regularly.

      Rob

[B Keith]

OK, I'm having a new set of problems that I can't tackle, now.  Because I'm such a frosh with LabVIEW, I'm just sitting here for hours trying to figure out why I can't get waveform chart to display the actual motor position rather than the voltage it reads out.  I'm certain this involves a conversion factor that would consist of multiplying the data by a calculated value.  I already have the value I thought it should be, considering it has worked on another VI written for the same instrument, but it has only produced much smaller values.  For instance, with a change in motor position of 10mm, the graph displays a change of about 0.04.  So, I thought I would just find this scaling factor and multiply, but when I do this all that happens is the curve gets thicker, and more inconsistent with the actual position. 

I have a feeling the VI doesn't run properly, because I don't have anything in the false case of the case structure.  What do you think?  I don't necessarily need anything in there do I?  I'll attach the file again just in case.

Keith

[Mohammed.Ashraf]

Dear Keith, Actually this is a linear multiplication which might raise the curve upwards (Curve X (constant >1)) or downwards (Curve X (constant<1)).

in your case the Distance Constant will raise the Motor Position Chart upwards (check the axis values before and after the multiplication). the same will be the case for the Force conversion constant and the Load Cell Chart.

that's why you are getting something looking similar to the old curves but shifted upwards.

and for the Case structure with no code in the False case, it will not make a problem or be responsible for the results you are no satisfied with.

another approach is to use custom scales , which is configured in the MAX and you can choose it from inside the DAQ Assistant Express VI rather than using numeric constants multiplied to the results of the DAQ assistant VI. using Custom scales will make the scalling factors applied in the Acquisiton process and returns the adjsuted data as a final result

Regards...

Message Edited by MAshraf on 12-17-2008 02:07 AM