Hi everybody~
I'm used to working with Rockwell/ Siemens/ Mitsubishi and new to CoDeSys. Since we have considered to change to CoDeSys control system, we are trying to build a clean testing environment using existing hardware before we purchase the normal runtime license and hardware.
Below is the Hardware and Operating system information:
OS: Windows 7 Ultimate SP1 Build 7601, 64 Bit
CPU: Intel Q9400 Core2 Quad @ 2.66 GHz
Installed memory: 8GB
Ethernet card: Intel 82567LM-3
Since the ethernet chipset driver signature problem, we run win7 in testing mode(bcdedit /set testsigning on) currently.
We could run control win x64 without any problem but when we change to run control rte(click start from system tray), it never starts normally.
We have checked the rte manual and find out there are some key-values in system reg. missing(please check attached file "System_register.png").
We also find out some value in control rte configuration was not correct like kernel version...etc(please check attached file "RTE_Configuration.png").
I also attached control rte config file(please check attached file "CODESYSControl_cfg.png").
I'm wondering if anybody could give me some comment or help to solve this issue and help the testing step forward.
Thanks in advance.
James
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
It is working.....Thanks...
BTW, is there any place we could find it out the issue and solution by ourself instead of bring up question in this forum?
Or you guys want us to bring up all the issues here?
James
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
check:
1. Core assignment is ok? (-> becdedit on CLI) for your system
2. Hyper V disabled ( bcdedit - > bcdedit /set hypervisorlaunchtype off
3. secure boot on Windows disabled
Best Regards
Edwin
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi everybody~
I'm used to working with Rockwell/ Siemens/ Mitsubishi and new to CoDeSys. Since we have considered to change to CoDeSys control system, we are trying to build a clean testing environment using existing hardware before we purchase the normal runtime license and hardware.
Below is the Hardware and Operating system information:
OS: Windows 7 Ultimate SP1 Build 7601, 64 Bit
CPU: Intel Q9400 Core2 Quad @ 2.66 GHz
Installed memory: 8GB
Ethernet card: Intel 82567LM-3
Installed CoDeSys package:
1. CODESYS Control Win 64 V3.5SP12Patch4 Setup.exe
2. Setup_CODESYSControlRTE64V3.5SP12Patch4.exe
Since the ethernet chipset driver signature problem, we run win7 in testing mode(bcdedit /set testsigning on) currently.
We could run control win x64 without any problem but when we change to run control rte(click start from system tray), it never starts normally.
We have checked the rte manual and find out there are some key-values in system reg. missing(please check attached file "System_register.png").
We also find out some value in control rte configuration was not correct like kernel version...etc(please check attached file "RTE_Configuration.png").
I also attached control rte config file(please check attached file "CODESYSControl_cfg.png").
I'm wondering if anybody could give me some comment or help to solve this issue and help the testing step forward.
Thanks in advance.
James
Hi,
according the signing problem on Windows 7 - 64Bit
You need to install this security patch:
https://technet.microsoft.com/en-us/lib ... ty/3033929
BR
Edwin
Hi Edwin,
Got it and thanks for the information.
I would try it and update you.
James
Hi Edwin,
It is working.....Thanks...
BTW, is there any place we could find it out the issue and solution by ourself instead of bring up question in this forum?
Or you guys want us to bring up all the issues here?
James
Hi Edwin,
I encountered the same situation
On the Windows 10 system
Have any solution?
youdo
check:
1. Core assignment is ok? (-> becdedit on CLI) for your system
2. Hyper V disabled ( bcdedit - > bcdedit /set hypervisorlaunchtype off
3. secure boot on Windows disabled
Best Regards
Edwin