iayestaran

Thanks for the info @Antoine Chalons. My code is now too mature to start replacing my indicators by QControls, but anyway it is a good advice for the future. Since the only stuff I needed to copy was the value of the table and the color of the cells, I opted out doing a specific VI that does that : Anyway, if someone knows a simpler way to do it, I am here to learn

Hi, I have indicator that looks like this : The table is automatically filled in live depending on the results of some test that are carried out by the labview program. Depending on the values measured during the tests, each cell will get a different background color (also live). So in the end, I am getting a table whose values and colors are slightly modified. At the end of the test, another tab will automatically be displayed, showing the summary of all the tests that have been carried out. What I would like is to just make an exact copy of my table that has been automatically filled in, respecting the values and the colors of the table, in the second tab. I am looking for the best way of doing this. Any ideas? Just defining the table outside the tabs and showing/hiding it dependin on the tab is not a good option, since I have too many tabs and indicators, and they are placed in different places in each tab, so showing/hiding and moving them should be a mess. Thanks!

FIXED: The problem was inside the Open UDP Conn VI. It seems the behavior of the 'UDP Open' is different in Windows and Linux machines (cRIO). The solution is to leave the 'net address' terminal unwired.

Hi everyone, I am perceiving some strange behavior in my UDP connections. Every time I re-start my cRIO 9063, the UDP Write block outputs ERROR 66 (LabVIEW: The network connection was closed by the peer. If you are using the Open VI Reference function on a remote VI Server connection, verify that the machine is allowed access by selecting Tools>>Options>>VI Server on the server side.) and it does not transmit. The most bizarre thing is that if I simply stop the execution and re-launch it again (given that I am executing the code of the cRIO in Debug mode from a Windows laptop), the UDP connection behaves perfectly well. The only time it fails is the first time I launch the program after I reset the cRIO. For me, it looks like some service is not properly initialized when the cRIO is started. I attach a picture with the UDP connections of my LabVIEW RT program. The 'Comms RX' VI simply calls the 'UDP Read' function, and the 'Comms TX' calls the 'UDP Write'. The 'Open UDP Conn' also simply calls 'UDP Open'. Can anyone help me?