Skip to content

B&R PVI

Couples B&R controllers running Automation Runtime, on a real CPU or ArSim, through B&R PVI. Variables are read and written by name. Platform: Windows only.

The connection runs through PVI on the gateway PC.

CONNECT reaches B&R controllers through PVI on the gateway PC CONNECT runs on a Windows PC together with your own B&R PVI installation and its PVI Manager service. PVI connects to the controller or to ArSim, by default with ANSL on TCP port 11169, or with INA2000 for older CPUs. Variables are read and written by name. Gateway PC (Windows) CONNECTB&R PVI interfacevariables by nameProg1:localCnt B&R PVIyour installationPVI Manager servicemust be running B&R controllerAutomation Runtimereal CPU or ArSim ANSLTCP 11169(INA2000: older CPUs)
The B&R files are not part of CONNECT: the interface uses the PVI installation on the gateway PC.
ParameterExample
ConnectionANSL (default) or INA2000
Host / Port192.168.0.10 / empty = PVI default (ANSL 11169)
Timeout1500 ms (ANSL)
User / Passwordoptional ANSL login (Automation Runtime A4.61 and newer)
Refresh100 ms per variable
CPU poll2 s
Source / destination station1 / 2 (INA2000 only)

CONNECT connects to B&R controllers running Automation Runtime on a real CPU or ArSim through B&R’s PVI. Variables are read and written by name, so nothing has to be released in the PLC project, unlike OPC UA. Use ANSL for Automation Runtime 4.08 and newer and for ArSim. INA2000 is available for older CPUs but has not yet been verified against real hardware.

Addresses take four forms, each followed by structure members and array elements as needed:

AddressMeaning
gCounterglobal variable
Prog1:localCnttask-local variable of task Prog1
Mod1::gSpeedglobal variable of an application module
Mod1::Prog1:cnttask-local variable inside an application module
stData.Speed, arr[3], Prog1:st.arr[2].xa structure member or array element

Every signal is a single value. For structures and arrays, address the member or element you need. BOOL becomes a Boolean, and integer types become integers. A value beyond 32 bits shows as a signal issue instead of being wrapped. REAL and LREAL become floats, STRING and WSTRING become text, and TIME becomes an integer in milliseconds. Date and time values are read as text.

Browse lists the tasks and variables with their types and expands structures and arrays into single signals — up to Max browse variables (default 5000) and 1000 elements per array. Discovered signals arrive as PLC outputs (read); switch a signal to PLCInput to write it. Each interface also publishes the CPU state as <interface>.cpu.state (0 Run, 1 Service, 2 Stop, 256 offline) and <interface>.cpu.running; the PVI licence state is shown in the interface status.

Writing needs Allow web to PLC. CONNECT writes only the addressed member or element, never a whole structure, and only when the viewer changes a value. Nothing is written when the interface connects or reconnects, so the PLC keeps its own values. A change made while write access is off is discarded and not sent later.

  • Manually. Enter the variable name: gCounter (global), Prog1:localCnt (task-local), Mod1::gSpeed (module), stData.Speed or arr[3] (member or element).
  • Browse. Yes. Browse lists the tasks and variables with their types and expands structures and arrays into single signals, up to Max browse variables (default 5000) and 1000 elements per array. Discovered signals arrive as PLC outputs; switch one to PLCInput to write it.
  • File import. No protocol-specific file import. Use Addresses → Import address table… for a prepared list.
  • From the model. When the model already has its PLC signals, Addresses → Fill from controller… in the signal-mapping section of the CONNECT panel previews matches by exact name against what Browse finds and then writes the addresses. Addresses → Import address table… takes a CSV or TSV with name;address[;dataType[;topic]] rows. New signals take direction and type from the same-named model signal; signals that already exist keep their configured type. See Configuring interfaces.

How direction, data types and write access are decided is explained in Common concepts and Configuring interfaces.