Academic Company Events NI Developer Zone Support Solutions Products & Services Contact NI MyNI
This Document is not yet Rated  Rate this Document

Why do I experience time-outs during software installation on my remote target with a high latency network connection?

Primary Software: Utility Software>>Measurement & Automation Explorer
Primary Software Version: 4.0
Primary Software Fixed Version: N/A
Secondary Software: N/A

Problem:

I have a high latency or slow bandwidth network connection such as satellite or low speed wireless, and I am experiencing time-outs when configuring the Network or System Settings on my remote target, or during software installation on my remote target in MAX. Is there any way that I can adjust these time-outs?



Solution:

It is possible to adjust these time-outs by adding keys to the Windows registry. After making changes in the registry you will need to restart MAX. To edit the Windows Registry please go to:

Start » Run » regedit

Caution: Lowering the below time-outs could have adverse effects on the program functionality and even cause fatal errors on remote targets (in particular lowering mxTimeoutPhCfg*). Increasing these time-outs may cause MAX to wait longer on certain network operations, leading to a less responsive UI.

In order to adjust the remote time-out values in MAX the following keys must be added under:

HKEY_CURRENT_USER\Software\National Instruments\Measurement & Automation Explorer\Remote

DWORD Values to modify if experiencing general connection problems (in milliseconds):

mxTimeoutConnectTime-out for general TCP/IP connections, default 60000
mxTimeoutPhCfgConnectRemoteTime-out for Network Settings configuration on a remote subnet, default 5000

DWORD Values to modify if experiencing FTP transfer issues (e.g., aborted transfers of large files):

mxTimeoutFtpChunkSizeNumber of bytes to send/receive on TCP/IP socket, default 4096
mxTimeoutFtpRetriesNumber of TCP/IP retries during FTP command, default 5

Troubleshooting guidelines:
  • Check that your target is really up & running (try pinging it first)
  • Be aware that increasing the time-outs also increases the inaccessibility of MAX (it will be busy longer during network commands)

Problems during remote subnet target detection or configuration

  • First try increasing mxTimeoutPhCfgConnectRemote to 10000, 20000, or more, up to 60000 if needed
  • If there is still no success (very unlikely!) continue increasing it in steps up to 120000, along with mxTimeoutConnect
Problems installing files through the Real-Time Software Wizard
  • Decrease mxTimeoutFtpChunkSize to 2048, or 1024
  • Increase mxTimeoutFtpRetries to 10 or 20
  • increase mxTimeoutConnect to 120000 (but usually 60000 is plenty already)


Related Links:

Attachments:





Report Date: 02/20/2007
Last Updated: 03/06/2007
Document ID: 42GH3O00

Your Feedback! poor Poor  |  Excellent excellent   Yes No
 Document Quality? 
 Answered Your Question? 
  1 2 3 4 5
Please Contact NI for all product and support inquiries.submit