BLT for LabVIEW communicates with LabVIEW through VI Server.

For some reasons, the LabVIEW VI Server connection might become unresponsive, depending on the performances of your computer, or the size in memory of your LabVIEW Project.

This would typically result in the following error thrown by BLT when trying to communicate with LabVIEW:


Error 1130: LabVIEW: (Hex 0x46A) The VI Server connection peer is unresponsive. Refer to the Connection Responsiveness: Check Method topic in the LabVIEW Help for more information about connection polling.


Fortunately, BLT for LabVIEW allows you to configure LabVIEW VI Server Connection Responsiveness information to prevent this error from happening.

To do this, you'll need to edit the file at: 


%ProgramData%\STUDIO BODs\BLT for LabVIEW\LVconnectionResponsiveness.ini


The contents of the file look like this:


[CONNECTION RESPONSIVENESS INFO]

PingDelay.ms = 10000

PingTimeout.ms = 180000


where:

- PingDelay.ms: Specifies how long between queries LabVIEW waits, in milliseconds. If you specify a value of –1 (infinity) LabVIEW does not check the connection

- PingTimeout.ms: Specifies how long in milliseconds before LabVIEW times out after LabVIEW sends a query to prompt the VI Server network connection for a message. If a timeout occurs, all VIs and functions waiting on the connection return a connection unresponsive error.


For example, if you set PingDelay.ms to 3000 and PingTimeout.ms to 1000, LabVIEW sends a query to verify the status of the VI Server network connection every time 3 seconds elapse without LabVIEW receiving a message over the connection. If LabVIEW does not receive a reply from the network, LabVIEW waits 1 second before all VIs and functions waiting on the connection return network connection error 1130, which you can handle on the block diagram.