NicolaG_89

Hi, please check if "Support client animations and overlay of native elements" option is enabled. This option is very heavy to manage for the Webclients. 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. The same CPU is mounted also in their WebPanel "WP" series, so you can try one of them if you want.

Hi, please check if "Support client animations and overlay of native elements" option is enabled. This option is very heavy to manage for the Webclients.

Hi, please check if "Support client animations and overlay of native elements" option is enabled. This option is very heavy to manage for the Webclients.

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.

Hi, I'm using a Pixsys PL700 PLC (arm PLC based on BBB) on Codesys V3 and I'm trying to communicate with a custom CANopen device that has not EDS file. No problem with SDO, but what about PDO? The device has already some PDO mapped so I only need to use them, no need to configure them. Can somebody give me a suggestion? Thank you

Hi, I need to use EoE, do I need some Routing/Tap etc configuration on the device?

Hi, I'm trying to communicate with a MoviconCE HMI to a codesys PLC. During Movicon Codesys driver configuration I can check the communication with the PLC and it seems Ok, I can also import the variable, reading it from the PLC (the edge gateway is correctly running on it), but when I run the Movicon Project into the HMI, I get "communication error 87" and my variable remains to "0". Using a x86 PC (my developing PC) and the same Movicon project I can read the variable correctly. So it seems that...

Ok verified, with "export" button Codesys creates a zip file with the GSD file inside. Thank you.