...
| Parameter | Meaning | Unit | Default value |
|---|
| --- PVI Parameters --- |
| Parameter for the PviXInitialize function (PVI interface initialization).
Communication timeout for the client/server communication in seconds The value specified with this parameter serves as the default setting of the initialization parameter COMT. If no particular presetting is desired, the default value 0 should be entered. | sec | 0 |
| Parameter for the PviXInitialize function (PVI interface initialization).
Retry time for PVICOM user messages in seconds. The value specified with this parameter serves as the default setting of the initialization parameter RETR. If no particular presetting is desired, the default value 0 should be entered. | sec | 0 |
Initialization parameter string | Parameter for the PviXInitialize function (PVI interface initialization).
String with initialization parameters. According to the PVI documentation, the following parameters are supported: | Parameter | Description |
|---|
| COMT | Communication timeout for the client/server (application/PVI Manager) communication in seconds
The timeout also defines the time for the life sign monitor. An additional period is needed to detect a disruption in the client/server connection. To determine the total time where a communication disruption would be detected (at the latest), the timeout value specified here has to be doubled. If the timeout is 5, then an interruption in the connection can be detected as early as 5 seconds and as late as 10 seconds. Connection interrupts are not recognized as such by the PVICOM interface if they occur within the timeout period. Data transfer simply continues once the connection is reestablished. Often used values are 3 - 10 seconds for local communication and 5 - 30 seconds for remote communication.
Value: 1 - 3600, = 0 ... Default value of 30 s used.
The value specified in the function argument "Timeout" serves as a presetting for this parameter. | | RETR | Retry time for PVICOM user messages is seconds.
The default setting ("RetryTime=0") should normally be used for this parameter. See the User Message Operations section for more information about this parameter.
Value: 1 - 3600, <= 0 ... no repetition.
The value specified in the function argument "RetryTime" serves as a presetting for this parameter. | | LM | Limit on user messages. Default: "LM=1".
PVICOM applications basically do not need to change the default setting of this parameter. However, if an application is able to respond quickly to PVICOM user messages, then a higher limit value ("LM=100", "LM=500") can speed up user message execution. See the User Message Operations section for more information about this parameter.
Value: 1 - 65535, <= 0 -> No limiting. | | PT | Process timeout in seconds. Default: "PT=0".
This timeout can be used to monitor the time between requests and responses. This parameter is only intended for PVICOM applications that carry out particular tasks. Standard applications do not need to be monitored and should use the default setting (no timeout monitoring).
Value: 1 - 3600, <=0 -> No timeout monitoring | | IP | TCP/IP address or hostname.
If the IP initialization parameter is specified, then the Remote communication type is used for PVICOM communication. Either the TCP/IP address (e.g. "IP=10.43.50.62") or the hostname ("IP=SystemPC1") of the server (PVI Manager) is specified with this parameter. If the hostname is given, then the IP address assigned to the name is determined by the system | | PN | TCP/IP port number. Default: "PN=20000".
This parameter is only required in conjunction with the IP parameter. The port number assigned to the PVI Manager needs to be specified here (PVI Manager Properties).
Value: 1024 - 32767. | | AS | Auto-Start (only for the local communication type).
1 ... PVI Manager is started (default).
0 ... PVI Manager is not started automatically and must be started already when the function is called.
More information about the startup procedure can be found in the PVI Manager section. |
| - | - |
| ObjectDescriptor parameter for the PviXCreate function when creating a Line object.
The parameter specifies the line description. The default value CD=LnIna2 creates an INA2000 line, which is used for communication with B&R SG3, SGC, and SG4 controllers via INA2000 protocol (Industrial Network Architecture).
| - | CD=LnIna2 |
| ObjectDescriptor parameter for the PviXCreate function when creating a Device object.
The parameter gives a description of the device. The default value CD="/IF=tcpip /SA=1" creates a connection using TCP/ IP (UDP), the source address (the D2000 KOM address) will be 1. The PVI documentation describes the parameters for individual device types (Serial, Ethernet UDP, Modem, CAN device, Profibus FDL device). | sec | 30 |
| --- Other Parameters --- |
| The parameter affects the scope of browsing used to configure the I/O tags.
If the parameter is set to YES, when browsing the I/O tag, global variables, all Task variables defined within the CPU, as well as all local variables defined in all tasks will be searched. If the parameter is set to NO, the global variables and local variables of the task defined by the Task object definition protocol parameter are searched.
Note: this feature is disabled because, on a station, it only makes sense to configure global variables and local variables of the task defined by the Task object definition protocol parameter. Local variables of other tasks will not work. | YES/NO | NO |
| If the value of the parameter is non-zero, then within the periodic reading of values within the station, it is checked whether any value was received by any station on the line during the last "Inactivity timeout" seconds. If not, the connection to the PVI Manager will be disconnected and re-established.
Note: this parameter can be used to speed up the detection of communication problems. If the values of the I/O tags change infrequently, we recommend creating an output I/O tag to which the value will be written every few seconds. | sec | 0 |
| This parameter allows the batch file to be started at the (re)start of communication. This batch file can e.g. restart the PVI Manager process (PviMan.exe) - e.g. using the pskill.exe utility or using the Windows utility "sc" if PVI Manager is running as a service. Restarting helps if, for example, the PVI Manager stays in the "Locked" state.
The symbolic constant #APPDIR# may be used in the command name, which will be substituted by the application directory name, e.g. #APPDIR#cleanup.bat | - | - |
| The time limit in seconds for the batch file specified by the Cleanup command parameter to finish execution. After this time elapses, the command will be terminated. | sec | 10 |
| Delay after creating each object. This parameter is used to slow down the start of communication for debugging and diagnostics. | sec | 0,0 |
Asynchronous write/create | The parameter determines the method of communication with the PVI Manager when creating objects and writing values. The asynchronous method is recommended, the synchronous method is implemented only for debugging and diagnostics. In addition, the synchronous mode of operation is not supported by the PVI Manager from several threads, so it can only be used with a single B&R line. | YES/NO | YES |
| Logging of values being read and written, together with names of /O tags. | YES/NO | NO |
| Logging of additional debug information about communication. | YES/NO | NO |
...
| Parameter | Meaning | Unit | Default value |
|---|
Station object definition | Definition of an object of Station type. It is not necessary to configure for the INA2000 line (the parameter is used on NET2000, DCAN, MODBUS, and SNMP lines). | - | - |
| Definition of an object of CPU type. The default value CD="/DAIP=127.0.0.1 /REPO=11160 /RT=1000" creates a connection to the locally running (/DAIP=127.0.0.1) virtual PLC on port 11160 (/REPO=11160), with a response timeout of 1000 ms (/RT=1000). According to the PVI documentation, there are the following usable parameters for UDP communication: | Parameter | Values | Setting | Description |
|---|
| /DA | 1-255 | 7 | Station number of the target station.
Automatic identification of the target station from the station number. The station number must be unique within the INA2000 network. The highest station number is 99 for SG3 and SGC with AR Version < 2.00, or 255 for SG4 and SGC with AR Version >= 2.00.
Example: "/DA=56". | | /DAIP | IP address,
Host name | None | The IP address of the target station.
Manual identification of the target station from the IP address or identification from the hostname (DNS, only possible for SG4).
Examples: "/DAIP=68.10.10.27" ... IP address, "/DAIP=CP340su" ... Hostname.Specifying the parameter /DA depends on whether the parameter /DAIP is specified:
If the parameter /DAIP is not specified, then the parameter /DA must always be specified. If the parameter /DAIP is specified as an IP address, the parameter /DA is optional. If /DA is specified, however, the defined station number must be correct. If the /DAIP parameter is specified as a hostname, the /DA parameter is ignored. | | /RT | 0 - 65535 | 275 | Response timeout in ms.
If a response to a sent frame is not received with this time, then the frame is transferred again. After the third retry, the connection is deemed canceled. The time in which an interrupted connection is detected is a result of ResponseTimeout * 4.
Setting /RT=0 uses the INA2000 default value (275 ms).
Example: "/RT=400".
Recommended values: | 20 - 250 | ... | For simple point-point connections, or connections via a local network with pure variable communication on SG4 controllers with sufficient idle time, with AR 3.00 and higher. | | 250 - 500 | ... | For connections via a local network with pure variable communication to any target systems / AR versions. | | 500 - 750 | ... | For connections via a local network with PLC services running (e.g. Automation Studio project transfer). | | 750 - 1500 | ... | For connections via an in-house network. | | 1500 - 5000 | ... | For connections via Intranet/Internet. |
| | REPO | 1025 - 32767 | 11159 | IP port number of the target station.
If the value is specified in Hexadecimal, then "0x" must be used to introduce the value (e.g. "/LOPO=0x2b97").
The port number must match the setting on the target station (PLC).
Example: "/REPO=11159". | | /CKDA | 0 / 1 | 1 | Enables or disables the check to see if the target station number (parameter /DA) is unique.
The parameter /CKDA is irrelevant if used together with the parameter /DAIP (check is always disabled).
Example: "/CKDA=0" ... Checking is disabled. | | /ANSL | 0 / 1 | *) | Turn on/off fast TCP download/upload via ANSL.
Example: "/ANSL=0" ... Download/upload via ANSL is turned off. | | /APN | 1025 - 32767 | 11169 | ANSL IP port number of the target station (peer station) for fast TCP download/upload.
Example: "/APN=11169". |
| - | CD="/DAIP=127.0.0.1 /REPO=11160 /RT=1000" |
| Definition of object of Module type. The parameter allows the creation of a connection to the module within the PLC.
Syntax of CD parameter: /RO=[<Name of application module>::]<Module name>
or
[<Name of application module>::]<Module name> Examples: - CD="/RO=Module1"
- CD="/RO=Generator::Module1"
- CD=Module2
- CD=Generator::Module2
| - | - |
| Definition of an object of Task type. The parameter allows the creation of a connection to a task (program) within the PLC. The I/O tags that are children of the station represent global variables of the PLC and local variables of the task specified by this parameter. It is, therefore, necessary to configure a separate station for each task within the PLC. If no parameter is specified, only global PLC variables are available. | - | - |
...
Mandatory parameters are CD=variable_name VT=value_type.
Parameter VL=element_length is mandatory for strings and wide strings (VT=string and VT=wstring).
Parameter VN=number_of_elements is mandatory for array values.
Note: the the I/O tag is ignored if its address starts with with %IGNORE
According to the PVI documentation, the following parameters are supported:
...
PVI Base system - B&R documentation
| Info |
|---|
|
You can read blogs about the B&R PVI protocol |
Changes and modifications
...