Solution
You can only see VBAI engines instances launched by the LabVIEW VBAI API. Not the instances opened manually of the VBAI interface.
VBAI API uses mDNS to discover VBAI engines available. You could verify that:
- Your Firewall is correctly configured or temporarily disabled.
- For this you could use Configuring Software and Hardware Firewalls to Support NI Products
- NI mDNS Responder Service is running
- Open Windows Services. Just type “service” inside your Windows 10 search bar
- Locate “NI mDNS Responder Service” and verify the running status
- UDP 5353 port is open
- Go to Control Panel --> Systems and Security --> Windows Defender Firewall
- Select Allow an App through Windows Firewall --> check if NI mDNS Responder is allowed for { Domain, Public, Private }
- Then come back and select Advanced Settings --> Inbound Rules
- Check if there is a NI mDNS responder rule and open the Protocol and port Tab to validate UDP 5353
- You can create a new rule for the UDP 5353 port
- From Inbound Rules --> Create a New Rule
- Port (click next) --> UDP
- Specify port 5353 (click next)
- Allow Connection (click next)
- Rule Applies should have { Domain, Public, Private } all checked (click next)
- Name this rule "NI mDNS open port"
- Click Finish