Daryl

Ok, I just updated XNET to 17.0.1 and this seems to be resolved. Thanks again!

Oh man, you mean to tell me I KNEW ABOUT THIS A FEW YEARS AGO and forgot about it? LOL, sucks getting old!!!! I will try your fix and see what happens, thanks!!

Labview 2016 XNET signal control does not fire change event. Is this a known issue? XNET event issue.vi

Actually yes. This is a good idea -thanks. (I don't know why I didnt think of it )

Is it possible to make a cluster icon small (on the block diagram) like the error constant when you select "View Cluster as Icon"? Doing it the same way as a regular VI does not work.

It also happens with the waveform datatype, so it is not exclusive to the Dynamic data type.

This one is driving me nuts. Add digital display to Waveform Graph and the digital display will intermittently spike to 0 even though the data feeding it does not. The plot on the graph will actually spike to 0 also but it does not always drop when the digital display does. For some reason the example I have attached does not show the issue on the plot, only the legend digital display, but it does happen on the application I am working on. The Waveform Array indicator does not display this same behavior. What am I dong wrong here? Using Labview version 2014 If you change the loop rate to 200ms it is much easier to see waveform graph issue.vi

I have to send 1 diagnostic request (CAN Frame) within a few milliseconds of an analog trigger to reproduce an issue. I am not trying to use this as a timing mechanism for a periodic message. The work around VI I posted does what I need it to do but I was wondering if this was some kind of issue.

So the 1st time you write a frame to the function "XNET Write (Frame CAN).vi", it takes about 16ms for the function to write to the bus. Subsequent calls to this function will not have this delay. Is this a known issue? Is it a handy feature of this function? Or am I just doing it wrong (this is usually the case)? Please see the attached VI's and let me know what you think. (Labview 2014, XNET 14.0) Thanks. delayed write issue.vi work around.vi

bbean - thanks for the help! I was able to get remote panels to work with Firefox by following the instructions in this link you provided. http://digital.ni.com/public.nsf/allkb/CF91AE26198992A686257B79006959C0 Thanks again!

Thanks for the reply. I will try those tricks for Firefox and if they dont work, I will try Opera. I just need this to work for 1 simple demo and I will never have to worry about ti again.

I'm trying to open a remote panel in Internet Explorer from a cRIO-9014 running Labview 2014. Whenever I try to connect, the panel begins to open then IE crashes (see attached image). I have tried using Firefox and I get a message "plugin needed" but I have the latest plugin installed. Any ideas how to get either browser to work for remote panels? I'm at the end of my rope with this one. Also - I have tried from 2 different computers on the network with the same results so I assume it is a problem with my real time web server configuration?

Thank you for your help and ideas. I have come up with a similar solution by polling the value and if it is changes, write the new value to the Value(signaling) property. It's kind of ugly but it will work for now. I just got an e-mail from NI Applications Engineer and there is a CAR #426378 for this issue.

I just tried this as far back as Labview 8.5 and the issue existed even in that version. It is only an issue with the "NI Terminal" control. I have tried with DAQmx Global cannel control and DAQmx Physical Channel control and the events are fired from the "browse" menu as expected. I contacted my local Rep and he is escalating the issue. I'm struggling to come up with an easy work around in the mean time. I guess I can poll the value for changes in the timeout case of the event structure. This is the least "ugly" solution I can think of for now.

Please look at the attached Labview 2014 vi. Press the arrow on the control and select a different value from the drop down list and the event is fired as expected. Now, press the arrow, then click on "browse" and select a different channel, the event does not fire. Is this a bug in Labview? Is there a workaround to get the event to fire? event issue.vi