| FORUM | LATEST POST | # TOPICS |
|---|---|---|
|
General Discussion Forum about anything you want to talk about. |
How to turn on a GPIO from a device function block by lwalbert 2022-09-29 |
1 |
Hello everyone, I am trying to create a routine in CODESYS to export a report to a CSV file using the CAA.File library. The file is created successfully, but I am getting some unexpected/unknown characters in the generated CSV. The problem seems to be related to the SIZEOF() function. I am using it for the szSize parameter of File.Write, as recommended in the CODESYS documentation. However, when I use SIZEOF(), the CSV contains extra characters and parts of previous strings. I also tried using LEN(),...
Hello everyone, I am trying to create a routine in CODESYS to export a report to a CSV file using the CAA.File library. The file is created successfully, but I am getting some unexpected/unknown characters in the generated CSV. The problem seems to be related to the SIZEOF() function. I am using it for the szSize parameter of File.Write, as recommended in the CODESYS documentation. However, when I use SIZEOF(), the CSV contains extra characters and parts of previous strings. I also tried using LEN(),...
Da war keine Log Datei vorhanden. Nachdem ich die IP-Adresse für den Lizenzserver aus der SafeControl-Instanz entfernt habe, startet die Instanz wieder.
I updated the runtime to CODESYS Control for Raspberry Pi SL 4.22.0.0, SDK 3.5.22.30. Same outcome as before. Now I study if migrating to PFC100 is ok or to change to Siemens PLC because of this issue.
I updated the runtime to CODESYS Control for Raspberry Pi SL 4.22.0.0, SDK 3.5.22.30. Same outcome as before. Now I study if migrating to PFC100 is ok or to change to Siemens PLC because of this issue.
I ran into a similar issue, albeit not the exact same conditions nor the same file if I recall correctly. As a workaround I have used an elevated account to give my regular user account write access to the specific directory where the failure occurred. It is not pretty and I am not happy with it. It does work.
Using Codesys 3.5.21.5. Tried installing both by full .exe file and using codesys installer. Installation requires elevation and completes just fine. However when running Codesys and closing the IDE, options-files are not written: Seems regular users are only given read-access to these files: Running Codesys as admin works as admins have full access. Haven’t been necessary before to run as admin. Don’t think I have the issue on my work-laptop, but have experienced this on a number of other computers....
..kannst du mal ins log auf dem Zielsystem schauen? VirtualControlAPI.log Danach könnte man den Start mal auf der Kommandozeile ausprobieren: python3 VirtualControlAPI.py -r <name></name> am besten noch mit verbose: "--verbose"