vcTrend and vScreen in AS6 [downloader]

Ask Questions HMI & Visualization
, ,
1

Hi Visualization Community,

Is anyone aware of a solution for the vcTrend and vScreen libraries in AS6? They are pre-compiled libraries available for download on the B&R website here:
VC Screen handling (vScreen) | B&R Industrial Automation

Trend Library (vcTrend) | B&R Industrial Automation

However, there are no versions compiled for AS 6 on those pages.

For context, I am looking into upgrading an AS4 C70 VC4 application to an AS6 C650 VC4 application.

Said VC4 application uses the following vcTrend functions: TR_init, TR_deinit, TR_addGrid, TR_addChart, TR_draw

Best,

Isaac

2

Hi @beani ,
I got the source code last year from Application Team in AT. I used them with AS 4.12, but never with AS 6.
I’ll send you as soon as I find them.

@phaehnel Could you please send those libraries to Isaac, thanks!
Ciao

Valerio

3

That is the project that contains the last version of the libraries in non binary format.
We are not really supporting the vScreen and vcTrend libary anymore, so anyone can now just take and build them from there.

VScreen_DevProject.zip (918.1 KB)

4

Thank you Philipp! I tested the source files building and graphing in AS6 ARSim. For anyone using this zip in AS6, after extracting ensure to use the source libraries for vcTrend and vScreen located in 2_8bpp_AS4\2_Source\source\Logical\Libraries not the libraries located in 2_8bpp_AS4\5_LibBinary, which are precompiled binary libraries for AS4.

5

For anyone that takes these libraries into AS6 for use on the new C650 panel, initially this library does not work in its current state:

I found that library is designed for 8 bit lookup table colors where the C650 expects 32bit ARGB colors. This resulted in scattered pixels and occasional memory access violations, as the visapi was indexing the pdata by 32bits rather than the expected 8 bits given by the library.

To remedy this, I modified the vspaint.c file to run VA_GetDisplayInfo to find the number of bits per pixel, and then create 32bit data arrays with a lookup table if the bits per pixel is 32 (rather than 8).

This results in a decent amount of processing since each trend line gets completely reinitialized on every cyclic. I get 30% CPU usage increase running 4 360-pixel trend lines in a 200ms task class.

I believe the best solution would be to remake the library to take in 32bit data arrays (maybe it does already support this in some way that I am unaware), but this solution works for my current use-case as the trend lines are not often displayed and the overall project is not resource intensive.

Note, this may not work with other function calls in the library but is currently working with TR_draw and TR_addChart, but other functions that utilize vspaintdb.c may need updating to that c code as well.

To implement, overwrite vspaint.c in the above library with the contents of vspaint.txt and use at your own risk.

vspaint.txt (3.1 KB)