Jump to content

iayestaran

Members
  • Posts

    2
  • Joined

  • Last visited

  • Days Won

    1

iayestaran last won the day on May 25 2016

iayestaran had the most liked content!

LabVIEW Information

  • Version
    LabVIEW 2015
  • Since
    2014

iayestaran's Achievements

Newbie

Newbie (1/14)

1

Reputation

  1. 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.
  2. 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?
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.