..this happens since a Windows Update,
you need to upate the Control RTE version.
(Keep in mind it is always possible just to update the runtime and keep CODESYS and your project in exact your tested machine proved and runnning version of youir application).
So I would chose latest SP16 RTE or SP17 - both is possible.
Last edit: eschwellinger 2022-02-27
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi,I've installed CODESYS Control RTE 64 3.5.16.50. But still no information is displayed in diagnostics. PLC not starting even after clicking on start from system tray icon. But system reboot issue when trying start PLC is not there now.
I've disabled secure boot and hyperv launch also. Still no luck.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I would suggest the follwoing:
1. check if the drivers are loaded:open Command line with admin rights and then "net start 3srte3".
Expected response: Successfully loaded.
If signature error occurs: Secure Boot active. No way, must be deactivated in BIOS.
2 Check if with numproc at least 1 core is reserved for RTE:
Same command line : "bcdedit".
Check in "current" if the setup has set numproc. If not, (e.g. it is a real 4 core) with
bcdedit /set numproc 3
reserve a core for RTE ( this is usually done by the setup)
3. check if CmpDrvSchedulerAMP starts correctly. with (also same command line) "net start CmpDrvSchedulerAMP".
This takes about 20 seconds the first time, because of the measurements.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
use latest version, disable hyperthrading check amout of real cores. If this does not solve it - it is a bug need to investigated - use my question in the CODESYS store
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi,
PC with CODESYS Control RTE V3 (version 3.5.7) is restarting whenever I try to start PLC.
Target name, address, type, ID are n/a and version is 0.0.0.0 in diagnostics.
Windows OS: Windows Server 2019
Processor: Intel Xeon E3-1505M Quad Core
Hyper-threading, SpeedStep and C-State are disabled in BIOS.
What would be the reason behind system reboot when starting Control RTE V3 PLC? Also, why no information is displayed in diagnostics of PLC?
Screenshot of diagnostics is attached for reference.
..this happens since a Windows Update,
you need to upate the Control RTE version.
(Keep in mind it is always possible just to update the runtime and keep CODESYS and your project in exact your tested machine proved and runnning version of youir application).
So I would chose latest SP16 RTE or SP17 - both is possible.
Last edit: eschwellinger 2022-02-27
Hi,I've installed CODESYS Control RTE 64 3.5.16.50. But still no information is displayed in diagnostics. PLC not starting even after clicking on start from system tray icon. But system reboot issue when trying start PLC is not there now.
I've disabled secure boot and hyperv launch also. Still no luck.
I would suggest the follwoing:
1. check if the drivers are loaded:open Command line with admin rights and then "net start 3srte3".
Expected response: Successfully loaded.
If signature error occurs: Secure Boot active. No way, must be deactivated in BIOS.
2 Check if with numproc at least 1 core is reserved for RTE:
Same command line : "bcdedit".
Check in "current" if the setup has set numproc. If not, (e.g. it is a real 4 core) with
bcdedit /set numproc 3
reserve a core for RTE ( this is usually done by the setup)
3. check if CmpDrvSchedulerAMP starts correctly. with (also same command line) "net start CmpDrvSchedulerAMP".
This takes about 20 seconds the first time, because of the measurements.
Eschwellinger,
what is the work around if "net start CmpDrvSchedulerAMP" returns the details below?:
Stop Code: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
What failed: CmpDrvSchedulerAMP.
This is after the steps 1 and 2 you mentioned above were successful.
Thanks.
use latest version, disable hyperthrading check amout of real cores. If this does not solve it - it is a bug need to investigated - use my question in the CODESYS store
I am currently investigating this problem as I have tried all the above to no success yet.
I am currently investigating this problem as I have tried all the above to no success yet.