Hello,
I am having difficulty with sharedlibraries and the communication between real-time VIs and host VIs. Here is what I am attempting to do and the problemsI am encountering:
I have a main real-time VI on mycRIO that I am using for an engine control system. It communicates with the fpga correctly andalso communicates through modbus with remote devices. The modbus communications are assigned toshared variables. On the main RT VI I have a separate while loop that connect theshared variables to various indicators/controls for display on the front panel. This system as it is worksperfectly. The problem arises when Istart incorporating a host VI. I need tohave a host VI in the system so I can make a deployable application and runthis program on a separate laptop. My host VI that I created is a basic whileloop that connects shared variables to indicators or controls. When the real-time VI is running and I try torun the host VI on my development computer, I run into problems. During the “deployment process” phase withthe popup window displayed, the “calculating dependencies” step takes approximately20 seconds to complete. Once the VI starts running I receive “Error -1950679035occurred at Shared Variable”. I canacknowledge this error and continue running, then about 10 seconds after noresponse, it will start communicating with the shared variables. During thistime of no response, the shared variables on my real-time system do not updateeither. Does anyone have any ideas whatcould be causing this?
One item to note also: If I am opening labview for the first time,open the project, open and run my real-time VI, then open and run the host VI,I do not have any problems. Both VIs workcorrectly and communicate with my shared variable library perfectly. After Istop my host VI and try to restart it, that is when this problem occurs, thenon all future attempts restarting the host VI this problem repeats.
I followed the knowledge basearticle on configuring the firewall (http://digital.ni.com/public.nsf/websearch/0D7B86F4B4D19A5E86256F9A006EECB1?OpenDocument)but it did not solve this problem.
Any help would be greatlyappreciated.
Dan
