Only first plot of waveform chart has run-time menu

[jmorris]

---

@carlos O wrote:

Hey Jmorris!

You are perfectly sane, changing the LegNumRows is what you need to do. Also, I've tried your VIs and both work just fine in LV 2011.

Best Regards

Carlos O

---

Hi Carlos,

Thanks for the confirmation of the LegNumRows property.  And that is kind of strange that the problem isn't a problem in LV 2011.  Ironically, I have that version, I just haven't installed it yet, and I don't think doing so at this point and going through all of the official upgrade integration procedures here is going to save me time.  😉

Can someone confirm that the "not working" VI does not work for them in LV 2010 (which is what I'm using)?  And if so, does that mean digging through the upgrade notes / bug fix list between 2010 and 2011 might provide some insight?  Hmm...

-Joe

[Carlos_O]

Hi Jmorris,

I've tried both codes on LV2010 and by changing the LegNumRows value I'm able to add plots to the legend. That's what you're to accomplish right?

Cheers!

Carlos O

[jmorris]

---

@carlos O wrote:

Hi Jmorris,

I've tried both codes on LV2010 and by changing the LegNumRows value I'm able to add plots to the legend. That's what you're to accomplish right?

Cheers!

Carlos O

---

Hi Carlos,

Actually, I'm trying to be able to change the plot properties via the user interface while the VI is running, for plots beyond the first one.  Can you please give that a try and let me know if you are able to change the (for example) color of the second plot by left-clicking on its line in the plot legend while the VI is running?

Thanks a bunch!

-Joe

[Ryan_S]

Hey Joe,

    I took a look at your code and can confirm that the "working" VI does work in LV 2010 while the "not working" VI does not work in LV 2010. However, as previously mentioned, both VI's work in LV 2011. The issue, and only difference between the two VI's, seems to be the type of data the Waveform Chart is expecting. The "working" VI is expecting an array of doubles while the "not working" VI seems to be expecting a cluster. So, first, I'd like to verify that you are in fact sending a cluster into the Waveform Chart. Next, clusters are used for many reasons. Are you using it to group items with unique data types? If not, a possible workaround may be to place each cluster element into a array since that seems to work. If they are unique data types, what are the different data types? In the meantime, I'll continue researching this behavior. 

--Ryan S.

[Ryan_S]

And to correct myself, the "Not Working" VI is looking for an array of waveforms, not a cluster. Sorry for any confusion.

--Ryan

[jmorris]

Ryan,

As you discovered, I am using a waveform in my actual VI to provide the time stamp for the x-axis.  I suspect it would be easier for me to just disable the selecting of plot properties entirely than to change that implementation to an array of floating point numbers while still retaining time as the x-axis.

Unfortunately, without any progress in this area, I may have to go the disabling route.  I hate to lose the ability to change plot colors and styles, but that's better than only being able to change the first plot. 

Thank you for taking a look at it, please let me know if you figure out how to get it working again in 2010!

-Joe

[Ryan_S]

Hey Joe,

     Just wanted to give you an update. I'm continuing to research this issue but haven't yet found a way to get the expected behavior.

--Ryan S.

[sparkysquared · Accepted solution]

Hey Joe,

     I've looked further into this issue and I believe one of two things are occurring. Either your chart is corrupted, or some combination of your custom chart settings is causing this behavior. I've attached two VI's, one where I've opened your provided "Not Working" VI in 2011 and then saved as a 2010 VI, and the other uses a new chart that is expecting an array of waveforms. Both of them work as expected (You can change the color, line style, etc. of each channel). The VI that was opened in 2011 then saved in 2010 retained all of the chart properties as the VI you originally posted. I'd like you to verify that it works for you, then take that chart and place it into your more complicated VI. If the chart was simply corrupted, this should resolve the issue. If the issue persists, then the issue is most likely caused by the combination of chart properties you've modified. In that case, take my second VI, which works for each channel as expected, and expects an array of waveforms and insert that graph into your program. Then check if the chart still operates as expected.  If the chart no longer works, then the issue is related to your input signal and I'll need more information. If everything still works, then the issue is a combination of modified chart settings. In that case, start modifying the chart back to how you want it to perform, checking after each modification if it still performs as expected. Either you'll find a point where it stops working, or the issue won't show up. Either way, we'll know how to move forward.

--Ryan S.

[jmorris]

Ryan,

I have replaced my strip chart with the one you opened in LabVIEW 2011 and then saved as LabVIEW 2010, and so far it seems to be working.  So it looks like your theory of a corrupt chart was the correct one. I will let you know if anything else happens to disprove that theory, but in the meantime I'm calling this solved!  Thank you very much for your time and assistance, along with everyone else who tried to help in this thread.

I'm not sure why you have two different screen names in your last two posts, but I'm giving Kudos to each of them just in case.  🙂

Cheers,

-Joe

[Ryan_S]

Hey Joe,

      I'm glad to hear that it's working! What most likely happened is that at some point your chart became corrupted. When I opened it in LV 2011, it recompiled the chart (because it was an older version) and fixed the issue. And I apologize for the different screen names, I accidentally logged into the wrong account.

--Ryan S.