From Friday, April 19th (11:00 PM CDT) through Saturday, April 20th (2:00 PM CDT), 2024, ni.com will undergo system upgrades that may result in temporary service interruption.
We appreciate your patience as we improve our online experience.
From Friday, April 19th (11:00 PM CDT) through Saturday, April 20th (2:00 PM CDT), 2024, ni.com will undergo system upgrades that may result in temporary service interruption.
We appreciate your patience as we improve our online experience.
12-16-2015 01:19 PM - last edited on 12-16-2015 01:33 PM by LiliMcDonald
labview bug Recently while I was going to create a vi to convert labview grapg into trend I find a small bug in labview graph and waveform that is not possible for solve unless national instrument correct it roots codes
bug is that in invert mood of graph if your minimum data is not zero, start point of grid is not work well and then you loos your grids.
any body else have same problem? you can find more explain in my linkdin hatef fouladi
Solved! Go to Solution.
12-16-2015 01:41 PM
12-16-2015 01:42 PM
Can you attach information to this message thread? (No one is going to login to linked in to find you).
Attach a VI that demonstrates the problem. Any special data for controls or indicators should be saved as the default values of those controls before saving and uploading the VI.
12-16-2015 03:35 PM
This makes perfect sence.
You have inverted the graph.
The start can't be smaller that the max value, it can't even be smaller than the minimum value, because your graph starts at the highest number.
How did you think the graph should have looked like? 5 then 23 then 15?
Your entry on the min and max has also changed, if you take a look.
12-16-2015 06:57 PM - edited 12-16-2015 07:12 PM
Hello agian
thank you for answer I made simple example vi to show the bug you can run this vi see the problem
12-18-2015 03:31 AM
Hatef,
This isn't really a bug, but I agree it can look a bit surprising. What must be said to understand what you see with this VI is that setting a Min value smaller than the Max value in the axis Xscale.Range properties cluster isn't actually enough to revert back the axis in the correct direction... You must first set the appropriate axis direction with the "XScale.Flipped" boolean property.
I have slightly edited your VI to show how it could be done. This way both graphs will behave in the same way, and according to your expectations :
Best regards,
Vincent
12-18-2015 01:36 PM
Dear Vincent Berseth as I menstion before in linkden the bug is not fixed and still remain and your vi just hide it
I made a simple vi to show that bug still remain
12-18-2015 01:43 PM
I see what you are talking about. Something doesn't seem right.
But there is one thing I don't understand. What is the difference between your two waveform graphs? They behave identically. They both get the same property values written to them. Yet you are getting different results in your "bug" and "no bug" indicators. Something must be different between them.
12-18-2015 01:54 PM
hi and thank you for your answer
if you look for first comment I attach the file with name of hatef bug in this file this a vi that show bug in one of the graph and show no bug in other
after that one of your friend change the some code in vi to show that there is no bug but after that i make some more code to show that bug is still remain
those two graph remain from first vi and are same in last on( in hatef bug fixed and in hatef bug not fixed) so there is no difference in two graph in last vi ( just difference in first vi )
12-18-2015 02:14 PM
Waveform Graph Scale "Inverted" Property is False and the same property is True for Waveform Graph 2.
Without speaking as to if the behavior seen is "Expected" or not, there clearly is a difference between the two indicators. And a difference in a propery the OP may have failed to note.