Timeout Error -307672 in VeriStand

Updated Apr 24, 2019

Reported In

Software

  • VeriStand

Issue Details

When I try to deploy my VeriStand project, I get the following error in the deploy log:

Error -307672 occurred at NI VeriStand Gateway.lvlib:Veristand Server Wrapper.vi >> NI VeriStand Server.lvlib:NI VeriStand Server.vi
Possible reason(s):
NI VeriStand:  One or more targets failed to start within the specified timeout. Verify that any start trigger or clock signals are configured correctly.


and I also get the following error from a running status dialog box in VeriStand:

Details:
Error -307663 occurred at Project Window.lvlib:Project Window.vi >> Project Window.lvlib:Command Loop.vi >> Project Window.lvlib:Connect to System.vi
Possible reason(s):
NI VeriStand:  One or more targets failed to start within the specified timeout. Verify that any start trigger or clock signals are configured correctly.
=========================
NI VeriStand: DataServices.lvlib:ERunConfiguration.vi.ProxyCaller >> DataServices.lvlib:ERunConfiguration.vi:2

Solution

This error is can be caused by a hardware timeout. Following these steps can help extend the timeout period and may help overcome the error.
  1. Open your project in VeriStand.
  2. Right Click on your main project and select Properties.
  3. Click VeriStand Gateway and find Wait for specified timeout Timeout.
  4. Change the value of Wait for specified timeout Timeout 120000 ms (Default) to 180000 ms or more.

Additional Information

This timeout error can also be caused when your hardware goes into a bad state. You will see this deployment timeout error because your project cannot correctly communicate with hardware it is trying to communicate with. To determine if this your behavior:
  • Examine your hardware. 
    • If you have CAN or XNET cards, are any ports showing as active when they should not be? Consult your user device manual for what LED signals mean.
  • Narrow down your project to include fewer pieces of hardware.
    • Start with a blank system definition file and see if you can successfully deploy that.
    • Add in pieces of hardware, models, or custom devices to the sysdef one at a time until the error returns. 

WAS THIS ARTICLE HELPFUL?

Not Helpful