Annotation Label Offset Explanation

[meshaal]

hi i want help
i have project  for (( Remote On-line Monitoring of Temperature ))
pleas  if any body have some onformation  pless send to me
<a href="mailto:***@hotmail.com" target="_blank">***@hotmail.com</a>
&nbsp;
and i want&nbsp; know how Temperature measurement application on LabVIEW by VI

[Meghan M]

Hi Chris,
I ran your VI and I was able to successfully create annotations where the label was displayed on peaks.&nbsp; Is there something that I missed?&nbsp; I ran this in LabVIEW 8.5.&nbsp; I attached a screenshot of the VI I worked on.&nbsp; Let me know, thanks!


Annotations.jpg:
Loading Image...

[C. Minnella]

This post might be inappropriate. Click to display it.

[Meghan M]

This post might be inappropriate. Click to display it.

[Kjell-Edmund]

Here is a stripped (no functions or sub-vi's left, only a property node read/write and a graph) vi that also illustrates the problem, only for me, the y-offset seems to work, but the x-offset is mirrored (or negated) around the y-axis. Instead of apearing at relative X-position of 0, it goes to absolute x-position of (-1)*X-cursor position. I too find it is related to the scaling of the x-axis, in my case the scale is 2E-5 to bring my 50k samples into the time domain.The VI is some 35kB, written in 8.5 Pro and running on Windows XP. We are currently closing in on a delivery to a customer, and the only acceptable fix we have found is to turn the lables off for now.(We generate the cursors and the lables based on peaks as data comes in, using a for-loop which iterates over the peak-X locations).


cursor bug2.vi:
http://forums.ni.com/attachments/ni/170/315467/1/cursor bug2.vi

[C. Minnella]

Kjell-Edmund, I see the problem you mentioned. I thought I had sorted all that stuff out before, but I don't have time to dig into it right now. Definitely a bug. Anyway, I'd suggest using a waveform datatype instead of dbl's to pass into the graph. That way the dt can be specified in the datatype and you don't have to scale the x axis. Hopefully that will help you avoid the problem.good luck!Chris

[Kjell-Edmund]

[edit] I have not tried to build it to a waveform fix that was suggested yet. [\edit] Update:There might be more to this bug than first meets the eye.During the day, I've run my app' on and off probably a couple of hundred times, modifying and changing things. During one(!) of the runs, 2 of the 3 labels were displayed at the correct location, while the rest were not.(Note that I generated a bunch of invalid markers due to a threshold level that was set to low.)When I re-ran, (after changing the incorrect threshold), it was back to the way it used to be, i.e. labels are all in incorrect positions.Figured I'd let whoever reads here know that the bug is non-constant and has some odd behavior.Message Edited by Kjell-Edmund on 04-11-2008 05:26 PMMessage Edited by Kjell-Edmund on 04-11-2008 05:26 PM


inconsistent cursor label bug.PNG:
http://forums.ni.com/attachments/ni/170/315751/1/inconsistent cursor label bug.PNG

[CheeRIO]

Thank you for&nbsp;bringing this to our attention.&nbsp; I will add your notes to the existing CAR.&nbsp; Please let us know if you notice any other unusual behavior or potential bugs&nbsp;when using LabVIEW.&nbsp; We&nbsp;are working&nbsp;hard to resolve these issues&nbsp;for future versions of LabVIEW.&nbsp; Have a great day!

[ASTDan]

Was this bug fixed in the new version of LabVIEW?
I couldn't find it in the bug list.
Thanks
Dan

[FieldKam]

Hello, I am glad to inform you that the issue related to Corrective Action Request (CAR) 4GIEK3TP has in fact been fixed in LabVIEW 8.6.Have a great day!