DEP — DEVlink Engineering PlatformUser Guide
ChargeLink docs ↗
Developed byDEVlink

HIL Runtime and NI VeriStand

Runs → HIL runtime connects a project to a hardware-in-the-loop bench through the NI VeriStand Gateway. You select VeriStand as the project's HIL execution provider and discover the Gateway. You can then deploy a reviewed VeriStand system definition, or attach to a running one to observe its channels.

DEP does not connect to or drive hardware. The HIL bench runs on NI VeriStand, which owns real-time execution and all I/O. From DEP you can discover the Gateway, deploy a reviewed system definition and observe its channels. DEP never writes VeriStand channels, so use HIL runtime to prepare and inspect a bench, not to drive actuators. The DEP HIL Runtime licence (a USB key per target) is required.

HIL through NI VeriStand: DEP on Windows talks to the VeriStand Gateway through the NI Client API; the Gateway manages the real-time controller and its I/O DEP Studio (Windows)Runs → HIL runtimeDiscover Gateway NI VeriStand GatewayVeriStand 2024 Q4 on Windowslocalhost or the Gateway PC RT controller and I/Odiscovered throughthe Gateway NI Client API DEP does not drive outputs. It deploys reviewed systems and observes channels; it never writes channels.
DEP talks to the VeriStand Gateway through the NI Client API. The Gateway manages the real-time controller and its I/O.

The HIL runtime page

The status cards at the top of Runs → HIL runtime.
The status cards at the top of Runs → HIL runtime.
  • Banner: Physical outputs locked. DEP does not drive outputs.
  • Saved System profile: the profile and the number of assigned models.
  • Deployment compatibility: shows Review required until you review it. Compatibility is reviewed separately from connection and deployment.
  • Connection evidence: shows Not verified this visit until you connect.
  • HIL execution provider: select NI VeriStand Gateway, then Save provider. Selecting a provider does not deploy a model or enable outputs.

Requirements

  • NI VeriStand 2024 Q4 with its Gateway, installed and running. DEP does not start the Gateway.
  • The NI Client API on the DEP PC, with Windows PowerShell 5.1 and .NET Framework 4.6.2.
  • Network access and NI peer authorisation between the DEP PC and the Gateway PC.
  • Your own NI licences.

Only the 2024 Q4 client is enabled. Other NI versions need a compatibility review by DEVlink.

Discover the Gateway

Gateway connection: Gateway host, NI Client API, Save provider and Discover Gateway.
Gateway connection: Gateway host, NI Client API, Save provider and Discover Gateway.
  1. PrepareOpen an initialised project. Stop, release or reconcile any previous execution owner.
  2. Select the providerIn Runs → HIL runtime, select NI VeriStand Gateway.
  3. Gateway connectionIn Gateway host, enter localhost or the hostname or IP of the Windows PC that runs the Gateway. Do not enter the real-time controller's address: the controller is discovered through the Gateway. For NI Client API, choose VeriStand 2024.
  4. SaveSelect Save provider. Discovery is available only after you save.
  5. DiscoverSelect Discover Gateway. Discovery waits at most 12 seconds.

The result Idle means the Gateway is reachable but has no deployed system. That is not an error, and it is not a completed HIL test.

Reviewed deployment and observation

For a prepared VeriStand system definition, select Choose and review definition. Review the definition and its dependencies, and tick the review confirmation. Then choose one of:

  • Deploy reviewed Windows system: DEP deploys the reviewed definition through the Gateway.
  • Attach observation only: DEP attaches to a system that is already deployed and only reads it.

Channel observations use the Windows receive time. Stop owned deployment stops only a deployment that DEP started. DEP never writes channels in this workflow. Synchronised acquisition and channel commands are not available.

Recovery and timeouts

If DEP loses an acknowledgement from the Gateway, it records the request as UNKNOWN rather than assuming success or failure. Inspect and reconcile the session in Runs → HIL runtime before you retry. A timeout (DEP-TGT-TIMEOUT) does not prove that the bench has stopped. Check the VeriStand side as well.

HomeTop