Hello guys,
I have the following problem with the Codesys visualization (4.6.0) and Codesys V3.5.20.20.
I would like to use my own HTML5 elements for my visualization. To do this, I have to select the option “Support client animations and overlay of native elements” in the visualization manager. But with the selection of this option, the visu has a massive loading delay when changing frame content. This happens even if I have not even added HTML5 elements. However, if this option is deactivated, then changing the content of the frames works without any problems, it loads instantly. I have already tried to change various refresh rates but without success. Have any of you experienced this and been able to fix it?
👍
2
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi,
the option "Support client animations and overlay of native elements" needs a very powerful graphics accelerator in the system. I'm using the Pixsys srl "TC series" HMI with the code "P3" (so a 4+4 cores CPU) that runs very well also with this option active.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hey NicolaG_89,
thanks for the tip. But I have seen in the developer tools of the Webclient that a multiple fetching of the image and script data occurs when changing frames (HTTP code 304 NOT Modified), although these are already in the clients cache, which leads to unnecessary loading of resources from the web server. This behavior can also be found if the option “Support client animations and overlay of native elements” is deactivated, but this does not lead to such long delays.
I had already tested loading all Visu elements so that everything was fetched once before they could be used. But that didn't help either.
To prevent this behavior (permanent fetching), I have used a different way of switching the Visu elements in the VisuDemo Project, which also uses HTML5 control elements. I implemented this with the visibility of entire Visu elements. As a result, it only has to be fetched once and does not have to be fetched again when reloading. But I am still unsure about this implementation if the scope of the visualization becomes larger, as the Codesys visualization documentation advises against using many invisible elements.
Best regards
Etienne
Hello guys,
I have the following problem with the Codesys visualization (4.6.0) and Codesys V3.5.20.20.
I would like to use my own HTML5 elements for my visualization. To do this, I have to select the option “Support client animations and overlay of native elements” in the visualization manager. But with the selection of this option, the visu has a massive loading delay when changing frame content. This happens even if I have not even added HTML5 elements. However, if this option is deactivated, then changing the content of the frames works without any problems, it loads instantly. I have already tried to change various refresh rates but without success. Have any of you experienced this and been able to fix it?
more posts ...
Hey etiennenneu,
I have the same problem with our prototype cell application. Do you have found a workaround for it?
Best regards,
Markus
Hello Markus,
Unfortunately, I haven't been able to find a suitable solution to the problem yet.
Best regards,
Etienne
Hi,
the option "Support client animations and overlay of native elements" needs a very powerful graphics accelerator in the system. I'm using the Pixsys srl "TC series" HMI with the code "P3" (so a 4+4 cores CPU) that runs very well also with this option active.
Hey NicolaG_89,
thanks for the tip. But I have seen in the developer tools of the Webclient that a multiple fetching of the image and script data occurs when changing frames (HTTP code 304 NOT Modified), although these are already in the clients cache, which leads to unnecessary loading of resources from the web server. This behavior can also be found if the option “Support client animations and overlay of native elements” is deactivated, but this does not lead to such long delays.
I had already tested loading all Visu elements so that everything was fetched once before they could be used. But that didn't help either.
To prevent this behavior (permanent fetching), I have used a different way of switching the Visu elements in the VisuDemo Project, which also uses HTML5 control elements. I implemented this with the visibility of entire Visu elements. As a result, it only has to be fetched once and does not have to be fetched again when reloading. But I am still unsure about this implementation if the scope of the visualization becomes larger, as the Codesys visualization documentation advises against using many invisible elements.
Best regards
Etienne
Last edit: etienneneu 2 days ago