Trouble Connecting to X20CP1483 via PVI / ANSL – Port 11169 Visible but Unable to Establish Connection

Ask Questions B&R Software & Runtime
, ,
1

Hello everyone,

I’m currently working on a system using a B&R X20CP1483 CPU, and I’m trying to establish a reliable connection from a C# application in order to pull production data continuously (24/7 monitoring of a critical process).

Goal

Use C# (PVI / ANSL) to connect to the PLC and read production-related variables throughout the day.

Current Situation

Hardware / Network

  • PLC: X20CP1483

  • Communication via Ethernet

  • PLC is reachable on the network (ping works)

  • Web interface is accessible

  • Firewall rules have been updated

  • TCP port 11169 is now visible/open

  • UDP port 11159 is still not visible

  • Network connectivity has been verified by IT

Software

  • Automation Studio available

  • PVI previously provided by B&R (license/security files were sent to us a few years ago)

  • PVI currently appears to still be in trial mode

  • Attempting to connect via:

    • Automation Studio

    • C# application using PVI

Where I’m Stuck

From my understanding:

  • Port 11159 (UDP) → Legacy INA protocol

  • Port 11169 (TCP) → Current ANSL protocol (used by X20 / Automation Runtime)

Currently:

  • Port 11169 (TCP) is reachable and visible via port scan

  • Port 11159 (UDP) does not appear to respond

  • The last configuration file I have references 11159, which makes me think it may be outdated or tied to an older communication method

At this point I’m unsure whether:

  1. The PLC is still configured for legacy INA

  2. The ANSL service is not fully enabled on the PLC

  3. PVI licensing is preventing communication

  4. There is a mismatch between Automation Studio version, runtime, and PVI version

What I’m Looking For Help With

  1. Confirmation of the correct communication method

    • For X20CP1483, should I be using:

      • ANSL over TCP (11169)?

      • Or INA / UDP (11159)?

  2. What must be enabled on the PLC side

    • Required Automation Runtime settings

    • Services that must be active

    • Whether the PLC needs to be in RUN mode

  3. PVI Licensing

    • How to confirm whether PVI is properly licensed vs trial

    • Whether an expired PVI license would prevent connection entirely

  4. Networking Requirements

    • Any special routing or port forwarding considerations

    • Whether UDP 11159 is still required at all

    • Expected behavior when everything is configured correctly

  5. Best Practice for C# Connectivity

    • Recommended approach for stable 24/7 data acquisition

    • Whether PVI is still the best option or if OPC UA is preferred

End Goal

A stable, supported way to:

  • Connect to the X20 PLC

  • Read production data continuously

  • Use C# for monitoring and reporting

  • Avoid trial-mode or licensing issues

Any guidance from someone who has successfully implemented this (especially with X20 + PVI/ANSL) would be greatly appreciated.

Thank you in advance.

2

Hi @alx_mcqueen ,
welcome to the community!
I worked almost 10 years ago with a customer that used our system with an HMI developed in c# with PVI Services.
When you download the PVI Development Setup

image
image2552×553 8.27 KB

There is a folder with list of help files, please check in particular the PviServices one

image
image1684×731 32.9 KB

Whether PVI is still the best option or if OPC UA is preferred
I guess now we recommend OPC UA communication.

Ciao
Valerio

3

Hi,

can you tell us the Automation Runtime version in use?
I’m asking because the CP1483 is quite old and discontinued, so I assume the AR version has some restrictions / differences compared to todays functionality ( for example if ANSL is already available for variable communication, if a older PVI version is needed, and so on).

Best regards!

1 Like
4

Hello,

Thanks for the response.

I have Automation Runtime 3.0.80