I have a test application and use Codesys Control for Rasp Pi SL. I made a mistake and updated device from MSL to MC SL, and now if I try to go online with archived version of the project I gett error message that IDs are different between project device and target device. Of course, I can go online if I changed device in the project from SL to MC SL, but I'm not sure that is correct. So I have two questions: 1. What is the actual difference between MC SL device and standard SL device when it comes...
I have a test application and use Codesys Control for Rasp Pi SL. I made a mistake and updated device from MSL to MC SL, and now if I try to go online with archived version of the proejct I gett error message that IDs are different between proejct device and target device. Of course, I can go online if I changed device in the project from SL to MC SL, but I'm not sure that is correct. So I have two questions: 1. What is the actual difference between MC SL device and standard SL device when it comes...
Thanks Tim, I suspected this is the reason, but want to confirm this.
I have noticed that Codesys doesn't provide option to Export any Visualization objects even though there is option to check to export VISU_TASK, which is strange because when Import in another empty project, user will end up with build errors. I understand that probable reason for this is that PLCOpenXML specification includes only "PLC" parts of the project (POU, PRG, variable lists, device ....), but not sure about it. Perhaps, there is some option to include visu objects also in the plcopen xml...
Hello, by searching the forum, I have found an example of batch script that can be used to start codesys projct by temporarily setting env variables. However, I'm not sure how to modify this to start Codesys 3.5.20 and whether or not I need to specify "profile" with Codesys version at all. @echo off SET PROJECT=D:\TestScripts\Data\OnlineTest.project SET VARIABLES=POU.testint,POU.testoutput start /wait CoDeSys.exe --profile="CoDeSys V3.4 SP3" --noUI --runscript="D:\TestScripts\Forum_Environment.py"...
Hello, by searching the forum, I have found an example of batch script that can be used to start codesys projct by temporarily setting env variables. However, I'm not sure how to modify this to start Codesys 3.5.20 and whether or not I need to specify "profile" with Codesys version at all. @echo off SET PROJECT=D:\TestScripts\Data\OnlineTest.project SET VARIABLES=POU.testint,POU.testoutput start /wait CoDeSys.exe --profile="CoDeSys V3.4 SP3" --noUI --runscript="D:\TestScripts\Forum_Environment.py"...
Hello, by searching the forum, I have found an example of batch script that can be used to start codesys projct by temporarily setting env variables. However, I'm not sure how to modify this to start Codesys 3.5.20 and whether or not I need to specify "profile" with Codesys version at all. @echo off SET PROJECT=D:\TestScripts\Data\OnlineTest.project SET VARIABLES=POU.testint,POU.testoutput start /wait CoDeSys.exe --profile="CoDeSys V3.4 SP3" --noUI --runscript="D:\TestScripts\Forum_Environment.py"...
Hello, I have just went through all steps shown on Codesys YT channel https://www.youtube.com/watch?v=RPoPscbo3Kc And it works, I have installed PI OS 32 bit and choose Single Core. However, immediattely when I create standard project with Raspberrz pi device, "Application" is underlined, like there is an error, but in reality there are no errors, and I cannot see what are these 3 messages like shown in attachment. Aside for this red underline, everything seems to work fine. How to correct this?...