Thanks. This new parameter '6000437' works on 4.8
I bought a new raspberry PI4, but I found 4.4 codesys runtime always stop shortly after I start it manually. I installed runtime 4.8. It works fine. May I have the reason behind? The MAC address of my new PI4 is 'link/ether d8:3a:dd:01:e7:d8 '
I have some problem on my raspberry PI license. Although I get green marks in ‘License manager’ of codesys. But a license checking appliance running on that raspberry PI shows no soft license (indicator is OFF). I’m using codesys runtime package 4.8 now since old versions does not work on my new raspberry PI. Device in the license checking application also in 4.8. Could you help me to figure out the reason? Thanks. I guess maybe the soft license checking parameter has been changed?
I think I need to generate a request file from my PI. But I don't have company name can be selected.
If both my codesys IDE computer and raspberry PI do not have internet access, can I activate the license of my PI through this website? http://license.codesys.com/index.php Could u show me the steps with screen snapshots? I don't want to destroy my license key by wrong manipulations. Thanks. If offline activation is impossbile from this site, is there any other methods?
I opened my old project in codesys SP18 IDE, but lamp elements in web visu becomes invisible. After I download my program to PLC lamps all over there as before. Actually lamps is fine on SP17 IDE for the same project.
Jira from codesys support team told me that I need to use 4.0.1.0 or higher version of runtime. And it solves my problem.
Plus both scan funtion fail to find my new PI 4B+ in codesys IDE.
my log file.
I have a very strange problem happens on my newly purchased raspberry PI 4B+. Codesys program always goes error several seconds after its service(codesyscontrol) restarted. It keeps going to the error status even I restart codesys service by shell command. “sudo systemctl restart codesyscontrol” I’ve tested the same SD card on another old PI 4B+ with the same 4GB RAM. It works fine without any problem. Is there any log files or config files I can supply so that you can help me on this problem?
not a chance.
Why I cannot find the unit ID on "Tab ‘ModbusTCP Slave Device - General’"? Is it because I'm using the latest version of the modbus TCP slave library? Without unit ID setting available, I have to set device ID to 255 when using modscan or other test softwares. Or is there any to ignore the unit ID for the modbus TCP slave device?