PVI transfer 3.2 can't access variable

Dear support

I have created a simple PLC simulator based on PC simulation with AS V3.09

The problem is PVI Transfer 3.2.3.8 could connect to the simulator, but it can’t read the variables, global variables list is empty to be precise.

But Runtime Utility Center V4.0 works well and could list the global variables.

I need the low version because the HMI software’s driver can only work with PVI 2.x

I have a PLC program based on X20 but the program is compiled with AR J3.09, both PVI Transfer 3.2 and RUC V4.x could connect to it, and read the variables.

So I guess I probably need to change some setting for compiling or missing some kind of library.

Many thanks in advance for your support.

Hello and welcome to the Community,

You’ve written you need PVI 2.x. Check the compatibility of Windows OS and PVI version. Couldn’t there be an issue?

Dear Pavel

Thanks very much for your prompt reply, actually I was asking how to compile a plc with AS V3.09 and then the program could be accessed by PVI 2.x. I have a X20CP1485 with AR J3.09, I could use PVI Transfer 3.2 and RUC V4 to list its variables, but when I created my own program with AR J3.09, PVI Transfer 3.2 can connect to the PLC but could not list its variables, the real PVI used on my machine is PVI 2.5. PVI 2.5 seems has no PVI Transfer, but PVI Transfer 3.2 comes with the software package of PVI 2.6.

So, there is no error in the Output window (seen in your screenshot) while getting the VariableListGlobal. The file is created but is empty, and you have global variables in the PLC since it’s possible to read them with PVI Transfer 3.2 and RUC V4?

Dear Pavel

RUC V4 could read the variable list but PVI Transfer 3.2 does not, thus PVI V2.x does not work neither.

But I have to use PVI V2.x to access the variables.

PVI replied with error 4813 if I open HMI software to browse variables, 4813 is identification error

It seems the driver sent wrong variable format request to PLC, but the real PLC on the machine with AR J3.09 has no problem, really strange.


Maybe if you make a PVI Snapshot you have more information, please check this post and the guidelines for troubleshooting provided by Alexander:

Last note: Do you have problem to access to all global PV or one in particular? Can you access to your local PVs?

Ciao
Valerio

Dear Valerio

I have tried to read global and local variable list, nothing received, and today I receive a new PVI error #1052, it is strange because it does not exist in the error number list of PVI

The driver based on PVI is from copa-data, and I can browse the variables from the real PLC X20CP1485, I read the AR version in this PLC is J309

So I think the error comes from the compiling of Automation studio 3.0.90 which I am using.

Anyway thanks for your time, and also many thanks to Pavel.

I checked again and found an error when typing the task name, and the error changes to 4813 after correct this typing error

Hi @jimlgb ,
I have found the zenon driver manual BUR20032 (attached in my answer).
At the page 30 they described how to configure PVI Monitor and I see your configuration and version of PVI are correct:

In the section 6.2.3 “Driver dialog PVI browser“ there are few pages with guidelines how to enter variables names, double check all steps you did, maybe it’s possible you did a small typo mistake.
In your PVI Monitor there is an error, you need to find the cause of that:

I have found only this information in the help for the error 1052, but it’s not related to PVI:

I don’t have an answer at the moment why you get that error when you select a variable.

BUR20032.pdf (1.6 MB)

Ciao
Valerio

Thanks for your concern Valerio

The PVI error #1052 is from external, and that’s why I used PVI Transfer 3.2 to test to avoid configuration or typing error.

What puzzled me is that RUC V4 could retrieve global and local variables while PVI Transfer 3.2 failed without error

RUC V4 screenshot:

PVI Transfer 3.2 screenshot:

So I am wondering if there is compatibility setting for compiling AS 3.0.90 project to be compatible with PVI 2.x

I have to check that, in the mean time could you ask a zenon updated driver for B&R? The version 2.x is quite old, it’s hard to believe the 2 systems can only communicate with a driver developed more or less 20 years ago:

Ciao
Valerio

maybe I have found something (AS Help 4.12.8.71 Automation Net: 2.6.0 > 3.0.0 Guid: f48ff5b3-b966-4662-a7f8-40a22481daf8):

In your prj with AS 3.0.90 you have selected AR J3.09, so you need to follow the workaround (with some limitations as multi-dimensional arrays and structure) reported above on red rectangle to keep the compatibility with the “Old“ module format.
Thanks
Ciao
Valerio

Compatibility_AN_2.6.0_to_3.0.0_E.pdf (32.5 KB)

Many thanks Valerio, you help find the root cause. Both Transfer PVI 3.2 and Zenon software could access the variables after adding optional switch “-limit2” for building

For sure Zenon has new driver to communicate with PVI, but it comes with new version.

Great @jimlgb thanks for the feedback!

Could you mark as solution the note we found in AS Help?
Thanks
Ciao
Valerio