Waveform chart Y scale overlap problem

[Kousy]

Hi all,

Attached vi (in LV8) tells my problem.

Hope I will get solution.Thanks in adv.

Kousy

[David_B]

Copied from your Problem Description in your VI:

I have had this kind of chart with nine plots earlier. - That chart functions Ok when Im running it as separate VI.
But when I call this from Main and load onto my subpanel, THESE Y Sclaes getting into mess (overlapping one
scale on the other), even with selection of 2-3 check boxes itself. I thought 'Use Minimum field width" in Format
& Precision tab will help. Even then its getting overlapped. - This is one problem.

Now I have created the same kind of chart for 7 channels'plot, shown above.
I have done like this - I have created one plot with name of Temp. And i added reqd. no. of plots
and duplicated the Y scales relevant. So now I have chart with 7 Plots. So far so good.
Now I like to add minimum field width for all 7 plots & precision for Channel 4 as mentioned in (**) But it shows the min.
field width to all plots, once i proceed with that and go on to change the precision for 4th channel, causes confusion by
showing the precision to 7th channel (Torque). I dont know where im making mistake & how should i correct it

[David_B]

I looked at your VI and the scales weren't overlapping when I brought them into a subpanel.  Which version of LV are you using?

[Kousy]

Hi David,

"I have had this kind of chart with nine plots earlier. - That chart functions Ok when Im running it as separate VI.
But when I call this from Main and load onto my subpanel, THESE Y Sclaes getting into mess (overlapping one
scale on the other), even with selection of 2-3 check boxes itself. I thought 'Use Minimum field width" in Format
& Precision tab will help. Even then its getting overlapped. - This is one problem." - This VI developed in LV7.1

I cannot run the application without hardware, hence i run it as separate vi and captured the attached images.

Update plot button value change event, reads the waveform file from disk and depends on the selected check box, it makes  visible or invisible the corresponding Y scales and shows the actual plot onto the chart.

&

"Now I have created the same kind of chart for 7 channels'plot, shown above.
I have done like this - I have created one plot with name of Temp. And i added reqd. no. of plots
and duplicated the Y scales relevant. So now I have chart with 7 Plots. So far so good.
Now I like to add minimum field width for all 7 plots & precision for Channel 4 as mentioned in (**) But it shows the min.
field width to all plots, once i proceed with that and go on to change the precision for 4th channel, causes confusion by
showing the precision to 7th channel (Torque). I dont know where im making mistake & how should i correct it" - This is developed in LV8.0, attached VI of my earlier post.

[David_B]

I found a few related posts that may help out:

Will Labview 7.1 fix scale overlap problem?
Re: chart y axes overlap

Let me know if either of these help out.

[Kousy]

Hi David,

Thansk for the links. I have seen. Its working fine as separate vis. but I need to call it in sub panel. If I find time I’ll try simulating and letting you know.

I have also tried like this. First of all I have made invisible all the y scales, and then make it visible depends on the selected check boxes. (Earlier I did on the fly of making visible/invisible the relevant y scales depends on the check box selection). Its working fine on my desktop as separate VI and in sub panel mode. This is similar to the links you have attached, but simple way. Once if this also creates confusion I can try using any of the other methods and let you know.

Thanks david. But the second problem I have mentioned in LV8 is random I think & need to fix it hopefully.

 

Kousy

[Neilo]

I ran into this problem recently. I was getting overlapping Y scales in my executable but not while running in source code. It turns out I had this item in my application INI file:

EnableAutoScales=False

Once I set it to True, the plot resized and scales were correctly spaced.

This was using LV2011 SP1.