02-15-2006 03:21 PM
02-15-2006 03:24 PM
Tables expect a 2D array as input. You can use the shift register with a couple of Build Array functions to accomplish what you need. First of all, use a Build Array to build the message, timestamp, and whatever else you want to store into a 1D array. This will be the new row for your table. Then use another Build Array to take the existing array in the shift register and add the new 1D array row to that...now you'll have a 2D array with a new row...specifically, your latest message that you want to display in the log.
Hopefully this makes sense. Check out the array examples or the LabVIEW Help for the array functions if you need more info.
-D
02-16-2006 12:13 PM
02-16-2006 12:34 PM
02-16-2006 12:57 PM
hi - sorry but im still getting broken wires....how do i enter the data and a time stamp in the next column properly? thanks...
i attached my vi to see what i did wrong
@AndrewAlford wrote:
Right click on the Table indicator and select Create-> Constant. Take the constant and wire it to the the shift register on the left side of the loop (outside). This fixes the broken wire as well as will initialize the shift register to zeros on startup.
02-16-2006 01:00 PM - edited 02-16-2006 01:00 PM
Here's a screenshot showing how to use a couple of Build Array functions to suit your purposes. I think you should take a look at some of the LabVIEW array examples to get a better handle on how to deal with array dimensions and building arrays.

-D
Message Edited by Darren on 02-16-2006 01:00 PM
02-16-2006 01:10 PM
02-21-2006 12:36 PM
02-21-2006 04:01 PM
02-22-2006 06:24 PM
i have a problem because all the text that is being input and output is in hex, and when the command log is displaying all the archived commands, it shows up as the weird characters. does this mean i need to make some kind of conversion first? i couldn't find a way to change it to hex display in the properties of the table
thanks!
@tbob wrote:
Here is the 7.0 version. I didn't have some of your subvi's so my version has a broken arrow. It may load correctly on your system. Even if it don't, you can still look at the changes made in the block diagram.