You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
VeriStand Version: 2020R4
Target: PXI-8840QC with NI-Linux RT
When trying to deploy VeriStand projects to the target using a DNS-Name instead of the IP the deploy process fails. If the Scan-Engine Custom Device is removed, the project can be deployed, if the DNS-Name ist replaced with a normal IP, the project can be deployed.
Pinging the PXI with its DNS-Name is posible.
To Reproduce
Steps to reproduce the behavior:
Open "C:\Windows\System32\drivers\etc\hosts"
Add a Local-DNS Entry, example: "192.168.1.12 pxi.example"
Open a VeriStand project, set pxi.example as the Target IP in the System Definition File
Add a intance of the Scan Engine EtherCAT Custom Device and configure a Master ECAT
Try to deploy
Expected behavior
The project will be deployed to the target sucesfully
Screenshots
Desktop (please complete the following information):
OS: Windows Enterprise LTSC
Version: 2021-22-0002P
VeriStand Version: 2020R4
Target: PXI-8840QC with NI-Linux RT
Additional context
The configuration is correct and it can be deployed with a normal IP.
The text was updated successfully, but these errors were encountered:
Describe the bug
VeriStand Version: 2020R4
Target: PXI-8840QC with NI-Linux RT
When trying to deploy VeriStand projects to the target using a DNS-Name instead of the IP the deploy process fails. If the Scan-Engine Custom Device is removed, the project can be deployed, if the DNS-Name ist replaced with a normal IP, the project can be deployed.
Pinging the PXI with its DNS-Name is posible.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The project will be deployed to the target sucesfully
Screenshots
Desktop (please complete the following information):
Additional context
The configuration is correct and it can be deployed with a normal IP.
The text was updated successfully, but these errors were encountered: