Thanks Hermsen, Let me try to explain it briefly. CODESYS products(RUNTIME, CONTORL, FEILDBUS...etc.) got widely range to combine. We'd like to understand the purchasing package detail and difference which like WAGO or Beckhoff did for their new development IDE and platform. Just feel free to share any ideas and thoughts from your experience.
Hello experts in Forge, I was always confused about the difference purchasing package on these brands. Since lots of customer in China bought CODESYS RTE to run their application in windows( the IDE remain CODESYS original style), every time when we talk about these fashionable IDE We don't get it at all with what they bought for packaging their IDE like that. Would somebody give any explanation on it?
Here to clarify the testing result： CPU - Intel Atom E3940 Test platform - Win10 Enterprice LTSC_x86 CODESYS RTE V3.5 SP16 Patch1 EtherCAT_Task - Cyclic 200us setuped Result - Aver. cycletime 45us Max. cycletime 134us jitter -1us* jitter Min. -60us jitter Max. 63us From our understanding the real Jitter in this case should be 63-(-60)= 123us. this value was higher than all cases we met before, which was usually <70us in previous cases with Win7. (* BTW, is "Jitter value" showup concept changed in...
Here to clarify the testing result： CPU - Intel Atom E3940 Test platform - Win10 Enterprice LTSC_x86 CODESYS RTE V3.5 SP16 Patch1 EtherCAT_Task - Cyclic 200us setuped Result - Aver. cycletime 45us Max. cycletime 134us jitter -1us* jitter Min. -60us jitter Max. 63us From our understanding the real Jitter in this case should be 63-(-60)= 123us. this value was higher than all cases we met before, which was usually <70us in previous cases for in Win7. (* BTW, is "Jitter value" showup concept changed...
Thanks for the reply. EtherCAT bus control performance we configured 200us to test jitter, and we got 200us ± 130us for min/max value. However, let's discuss the root cause from the issue, Through comparing with several CPU platform we found the ApoloLake(E3940) clock rate was decreased too much due to we closing the EIST function in BIOS. Please discussed with your colleague that is closing EIST function a "must" configuration? What would it happen if we enabled EIST function in BIOS for running...
Hello CODESYS Support team, Our company build an IPC product with CPU spec which title mentioned. From RTE Toolkit instruction for Win10 installation, we adjusted BIOS setting included disabled EIST, Turbo,C state ,Hyperthread Suspend...etc. We found when EIST was disabled that lead to this CPU clock rate down to 800MHz, which was suffering even general operation in clean Win10. Don't even think the target is running ECAT on CODESYS RTE and do simple softmotion, that performance might put a question...