Jump to content

Messenger Library LV2019 compatibility

Recommended Posts

Since upgrading to LV 2019 I am seeing issues with an existing application running on a Linux based cRIO.  The deployment process itself seems to be much slower and 

this initial section of code is causing the cRIO to disconnect from the development system.


When the execution gets to the TCPEventMessenger Create subvi I get this popup and execution is aborted.


Any thoughts?

Edited by viSci
Link to comment

That node starts the TCP Listener; can you try some simple example code that creates a TCP listener and see if it has the same issue?

Note: if you change the "TCP Listener"  Actor to non-reentrant and to open front panel, I think you can debug it on RT.

Link to comment

Yes it appears to get hosed up inside the TCP Listener Actor.  The funny thing is that I can compile an exe and run on my cRIO just fine, it is only via the IDE that there is a problem.

This has been working with LV 2018 for many months without issue so it appears something has changed in LV2019.


Link to comment

Did you try a non-Messenger Library TCP example to see if it has the same issue?

Another test would be to launch a basic actor (not the TCP communication ones) and see if that causes the same disconnect (if so it could by the ACBR stuff). 

Unfortunately I'm not on 2019 yet, so can't look into it.

Link to comment
  • 1 month later...
  • 11 months later...

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

  • Create New...

Important Information

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