07-11-2013 09:27 AM
See attached screenshots. I have a VI that outputs data to a table, with more data than visible rows in the table, so I want it to scroll automatically as the data is sent to it. I do this by wiring the index of the test, MINUS 18, to the Index Values Row property. This works PERFECLY on my computer as shown in front panel screen shot attached. But it DOESN'T work on other computers with the same Labview (2011) and the same operating system (WinXP). On other computers it halts on the first execution when the value input to the Row property is -18, saying it's an illegal value. Intuitively row "-18" shouldn't make sense, but IT WORKS on my computer. Any idea why this is?ut
07-11-2013 09:33 AM
What is the representation of the numbers you are sending for the Row numbers, U[8,16,32] or I[8,16,32]? The screenshots you show don't tell us, but the VI would have, had you attached it.
Cameron
07-11-2013 10:19 AM
I32
07-11-2013 10:34 AM
Does it come up as I32 on the other computers also?
Cameron
07-11-2013 10:59 AM
I bet you do not have Automatic Error Handling turned on on your machine, but it is on on the others.
Regardless, you should use the In Range Coerce function to make 0 the minimum value possible.
07-11-2013 11:01 AM
YES
07-11-2013 11:11 AM - edited 07-11-2013 11:13 AM
Looking at the coersion dots (and duplicating them in the snip) you arnen't going to be sending a negative integer to row.
As Tim said you need a In Range and coerce in there
07-11-2013 11:11 AM
@hammer3 wrote:
YES
Yes, what?
07-12-2013 07:39 AM
crossrulz: I was answering YES to camerond's question "Does it come up as I32 on the other computers also?"
Yes, there is a difference in Automatic Error Handling, and that is what made the difference in behavior. I now have it turned ON on my computer.
It doesn't make sense to coerce to make 0 the minimum value. The row input to the Index Values propertry MUST start at -18, and increasing through zero and on to positive numbers in order for the table scrolling to work properly.
I found two solutions to this problem, with Error Handling turned ON:
1) change the Representation in the Index Values property cluster type def from U32 to I32, or
2) add an Error indicator on the output of the Index Values property (which shows no error).
Thank you all for your inputs.
07-12-2013 08:01 AM
hammer3 wrote:It doesn't make sense to coerce to make 0 the minimum value. The row input to the Index Values propertry MUST start at -18, and increasing through zero and on to positive numbers in order for the table scrolling to work properly.
You are contradicting yourself. In our original post you said setting the index value to -18 doesn't make sense. And it doesn't. The minimum value is 0. What will happen if you coerce to 0 is the table will fill up before it starts scrolling. This is the desired functionality. Once you get 19 elements, then the index will be set to 1. Your last item in the table will always be at the bottom.