Hi @eschwellinger, can you confirm whether version V4.0.1.0 has been released already?
Now that's what I call a quick answer..! Thanks for your confirmation. We will eagerly wait till 17 February. Have a nice day.
I just received a new Raspberry Pi 4B. The old Raspberry PI 4B's can be found using the 'scan' feature in CODESYS and work just fine. But the new one can't be found anymore, unless you connect by it manually using it's IP address. Now, aside from it being it harder to find the device on the network, it's not really a big issue. The real issue is that the runtime stops after a while, 10 seconds, (oops.. this runtime is made for RASPBERRYPI). The MAC address of the new Raspberry Pi is E4:5F:01:00:AD:47...
The "Application.alarmstorage.1.sqlite" has last been modified over a month ago, while new entries are being registered daily. How is this possible? Did CODESYS catch the error and changed from in-file storage to in-memory storage? At the end of the day I don't mind how it's processed, as long as the entries are retained AND the error mentioned above is gone. Can I safely delete the journal-file (which is used for rollbacks), and will CODESYS revert to in-file storage again then? How can this be...
The "Application.alarmstorage.1.sqlite" has last been modified over a month ago, while new entries are being registered daily. How is this possible? Did CODESYS catch the error and changed from in-file storage to in-memory storage? At the end of the day I don't mind how it's processed, as long as the entries are retained AND the error mentioned above is gone. How can this be achieved? Should I contact support directly?
Hi, We have a CODESYS application running on a VM node in a Windows Hyper-V cluster. The application is thus shared on 2 different physical servers. The reason this is done is to update the servers with little to no downtime. The setup works really well, only the sqlite database of the AlarmStorage is throwing an error. This is probably due to the fact that it is being switched from server to server and detects something unexpected happened. The AlarmStorage still works, but is showing the error...
I am still looking for a possibility to export alarms without logging into the IDE. The user who said they already made this piece of software isn't replying to messages. At least I know it is possible (out of the box). I have too less experience to work with the interfaces provided by CODESYS (it also isn't documented). Any help is appreciated. Reno
Yes, the news is that it is working with the recently released patch 2 (CODESYS V3.5 SP16 Patch 2).