Hi, I am trying to create a log in my application. Since I cannot find any documentation regarding modifying the codesys configuration file to be able to log in ms, i tried to create a new log via CmpLog.LogCreate. Below is the part of the code where I create the logger and write a test string. In the log tab of codesys I actually see the new log that was created, but it is empty, and in the folder I cannot find any files. I can't find any detailed documentation. Can you guys give me support? Are...
Hi, I am trying to create a log in my application. Since I cannot find any documentation regarding modifying the codesys configuration file to be able to log in ms, i tried to create a new log via CmpLog.LogCreate. Below is the part of the code where I create the logger and write a test string. In the log tab of codesys I actually see the new log that was created, but it is empty, and in the folder I cannot find any files. I can't find any detailed documentation. Can you guys give me support? Are...
Hi, I cannot find any documentation regarding the codesys configuration file. I modified this part to have log files saved to disk: [CmpLog] Logger.0.Name=LOGS/PlcLog Logger.0.Filter=0xFFFFFFFF Logger.0.Enable=1 Logger.0.MaxEntries=20000 Logger.0.MaxFileSize=5000 Logger.0.MaxFiles=10 Logger.0.Backend.0.ClassId=0x0000010B ;sends logger messages to SysOut Logger.0.Backend.1.ClassId=0x00000104 ;writes logger messages in a file Logger.0.Backend.2.ClassId=0x00000135 ;sends logger messages as UDP syslog...
Hello, is it possible to retrieve the hash of the current GIT commit hash from runtime? I would like to show it on hmi in a service section. Thank you
Hello, is it possible to retrieve the hash of the current GIT hash commit from runtime? I would like to show it on hmi in a service section. Thank you
Hello, is it possible to retrieve the hash of the current GIT commit from runtime? I would like to show it on hmi in a service section. Thank you
Hello, I encountered similar problems, and it appears they were linked to certain add-ons. Resolving this issue turned out to be quite complex. However, we managed to find a solution by downgrading both the "CODESYS Communication" and "CODESYS Recipes" components via the CODESYS Installer, accessible under the "Tools" section.