Hello @pascal37,
please check the dmesg around the time it freezes. It will tell you if the HW is disconnecting.

Best regards,
Martin

Hi @sindyk,
no, your PLC will work as expected. These messages are not valid and they are meant to be valid in next version of MervisIDE, where the licensing of the PLC will be mandatory. You can ignore those for now.

Best regards,
Martin

Hello @rajeshannad,
as the technical documentation says "External voltage must be connected to the AOV connector with maximum voltage of 35V DC.".

If you want to have analog output between 0-10V, you need to apply >= 10V between AOV and AOG. Then set the AO to 100% via software and lower the value to match the 10V via blue on-board trimmer.

Best regards,
Martin

Hello @mmcreativ,
there isn't a reboot counter per-se, but you can work with the PLC uptime. This is provided by block "PLC Time (B99)".

Best regards,
Martin

Hi @roberts_lando, do you have any progress on this? Typically this type of debugging requires oscilloscope to see what the voltage levels look like. Do you have some USB-RS485 converter to test the communication?

Best regards,
Martin

Dobrý den @beny44,
zatím bohužel ne.

Hello @christophev,
please send the Mervis project to support@unipi.technology, I'll take a look at it.

Best regards,
Martin

Hi @pmandeli,
not yet, but the change is available for testing here: https://repo.unipi.technology/debian/pool/test/u/unipi-kernel-modules/unipi-kernel-modules-dkms_1.37.test.20200122161658_all.deb

Hi @matt,
this is described in the MervisIDE help (F1):

Sorry @jaros for the mystification. The blocks for PLC runtime are indeed called ''getevaltime" and "getevaltime4", depending on which data type you need.

Best regards,
Martin