rpscott02

QUOTE (jgcode @ Mar 5 2009, 08:59 AM) Ok, my excellent typing skills may have made thing a bit unclear. I meant that the blinking node is working, just that it starts as soon as the program is run and not when I want it to. I want it to activate at a certain point in the program. I have currently a case structure that checks if there is an error in the program and if NOT then the blinking property node should begin blinking. For some reason, this is not working. Hope that clears things up

One more issue - i'm having trouble making the blinking property node activate on after an even happens (namely, a 'no error' signal from another subVI). For some reason, it blinks as soon as I begin running the program. I've tried event and case structures and neither worked. I thought simply putting the property node in the error flow would cause things to happen sequentially but no luck there either. Any suggestions?

QUOTE (jgcode @ Mar 2 2009, 05:26 PM) Thanks jdunham and jgcode! Both your suggestions worked and are greatly appreciated

I wanted to know if it were possible to store a property node in a sub Vi to have it activate an indicator in a main VI. For example, I want to have an indicator blink when a TCP connection is found. Can I store a blinking property node in a sub-VI and have the indicator in the main VI (that is connected to the sub-VI output) then blink? I've attached the VI below. Thanks

QUOTE (rpscott02 @ Apr 8 2008, 08:52 AM) Ok, I'm still a bit stuck on this. The ethernet device as about 9 different channels that I'd like to be able to monitor simultaneously. Fiveco (the manufacturer) doesn't have Labview drivers yet but has posted DLL libraries on their site with the commands for communicating with each channel. So lately I've been trying to communicate using the Call Library Function Node but still, to no avail. I've attached a test file that isn't working. Is it possible to use TCP Vi's with a library node like this or am I way off?

Thanks for the help. Still working on this but it's good to at least be able to use the TCP protocol VI's

ok, Not sure what happened to that first post...Anyway, I'm very much a newbie to Labview, running version 8.5. I'm trying to create a VI that can communicate with a TCP device [FMod-TCP (DB)]. There's currently no labview drivers for it. The device has 5 A/D ports, 19 I/O and 2 I2C, all of which I plan to use. I'd like to be able to monitor signals on each port on a waveform graph in Labview. However, just for development purposes I'd lke to get Labview just to recognize the device. My question is: Are the TCP protocol functions enough to allow me to communicate with this device or do I need to create a driver for it. If creating the driver is necessary, the Labview help hasn't helped me very much so far. Any suggestions?