I've got problem with TwinCAT3 (Win10 64bit) when I try to active TC3.
Error message is :
Severity Code Description Project File Line Suppression State Error
19-Jan-19 11:42:34 AM 545 ms | 'TwinCAT System' (10000): Sending ams
command >> Init4\RTime: Start Interrupt: Ticker started >> AdsWarning:
4115 (0x1013, RTIME: system clock setup fails. Hint: On Windows8
system and above execute win8settick.bat in TwinCAT\3.1\System as
administrator and reboot.) << failed!
I also try to run "win8settick.bat" and reboot TC but it doesn't work!
Is there any recommend to solve this ? Thanks a lot!
I have had the problem few times. In all those situations, the BIOS settings have been OK. Executing the .bat file didn't help, until I ran it as an administrator and rebooted. Few times I have had to do it couple of times before it started working.
So try this
Open start menu and search for "Command prompt"
Right click it and select run as administrator
Navigate to "C:\TwinCAT\3.1\System" by writing "cd C:\TwinCAT\3.1\System"
Execute .bat by writing "win8settick.bat"
Reboot - Repeat if not working
For me, this has always fixed the problem. If you have incorrect BIOS settings, you would get different error that states something about virtualization (as far as I know).
You need to adjust your BIOS-settings according to:
http://www.contactandcoil.com/twincat-3-tutorial/quick-start/
(read chapter BIOS settings).
I suspect you may have Hyper-V enabled. Because of the way that 64-bit TwinCAT interacts with the processor (using Intel VT-x), it doesn't play well when hypervisors are running at the same time. Most hypervisors, like VMware, stop running when you close their window. However, Hyper-V (if enabled) is always running in the background so it must be disabled before using TwinCAT.
To Enable or Disable Hyper-V:
Right click on the Windows button and select ‘Apps and Features’.
Select Programs and Features on the right under related settings.
Select Turn Windows Features on or off.
Check or Uncheck Hyper-V and click OK.
source
In my case, installing TwinCAT 2 on top of an existing TwinCAT 3 installation was the problem.
According to Beckhoff, you need to "deactivate" TwinCAT 3 via "SwitchRuntime.exe" before installing TwinCAT 2, if installed in this order. In case of installing TwinCAT 3 on top of TwinCAT 2, you don't need this step.
https://infosys.beckhoff.com/english.php?content=../content/1033/tc3_installation/179471755.html&id=
If forgot this, which probably destroyed parts of my TwinCAT 3 installation in the background.
Even tough I set the installation directory to a new folder "C:\TwinCAT\TwinCAT_2" and not the default "C:\TwinCAT".
The installation process locked fine at first, only after trying to set a project into RUN while having TwinCAT 3 active as runtime, I got the above mentioned "AdsWarning: 4115".
Running "win8settick.bat" as admin and rebooting did not help, neither via explorer or command line.
Only re-installing TwinCAT3 did the trick for me.
What worked for me was to disable the Virtual machine platform in Windows Features.
In addition to the other answers, you'll get this error if you haven't setup the real-time cores to match the computer you're activating to:
I got the same issues. But I didn't try any of the above methods.
bcz I am scared about warning 'BitLocker trigger' from a user above!
Then I changed the real-time system settings:
error :
Severity Code Description Project File Line Suppression State
Error 27/08/2022 16:40:58 279 ms | 'TwinCAT System' (10000): Sending ams command >> Init4\RTime: Start Interrupt: Ticker started >> AdsError: 4115 (0x1013, RTIME: system clock setup fails.
Hint: On Windows8 system and above execute win8settick.bat in TwinCAT\3.1\System as administrator and reboot.) << failed!
settings: shared core 80%
new real-time setting: Isolated core 100 %
No error:
I didn't know the reason behind this!
Related
I was trying to use OMNeT++ earlier today but I was unable to get any simulation to run. I tried numerous model simulations but they began hanging at the same place during initialization. I deleted and re-installed OMNeT++, but the problem persists. So even after a fresh install of OMNeT++ v5.5.1 on a Windows 10 v1903 machine, I am unable to run any simulation. This is what I saw when I ran the Aloha sample simulation executable directly after following all the OMNeT++ installation steps:
The Qtenv simulation window starts up but it's completely blank, and I can't actually focus on it, which leads me to believe there's something up with Qt. The program hangs indefinitely at this point. OMNeT++ was configured using the default values found in configure.user.
Any suggestions?
EDIT:
This is the last console output I receive after running QT_LOGGING_RULES="*.debug=true" ./aloha.
This is the last console output I receive after running QT_DEBUG_PLUGINS=1 ./aloha.
Did you connect additional monitor to your computer? Sometimes Windows remember position of an application on non-existed screen. Try to change your screen properties or connect second screen and look for Qtenv window of Aloha simulation.
Besides the above, delete .qtenvrc from samples/aloha.
I am trying to start a twincat project on my pc in order to debug it. I've disabled the EtherCAT device and isolated a CPU on my windows 10 with an 8-core ADM processor. After trying to start the run mode, I get a fatal error on the target system. With following message:
'TwinCat System' (10000): Sending ams command >> Init4
RTime: Start Interrupt: Ticker started >> AdsWarning: 4131 (0x1023, RTIME: Intel CPU required) << failed!
I've searched the internet and am not able to find a solution to this problem. There seems to be little information about this. Anyone of you having an idea?
Answering my own question, just in case anyone else would come across the same problem: make sure when you isolate a CPU to emulate the PLC on that you also check it as the default one to be used. Just isolating isn't enough, you have to explicitly indicate the one to use.
Your answer appears to be right there in the message: Intel CPU required, but you stated you're trying to run it on an ADM (I assume AMD) processor.
today I found that my laptop's fan is worked in full level. after checking performance tab in task manager I see CPU usage is 100% and not change. I see webproxy.exe process in top of resource monitor list and everytime I end this process, after 1 second it run again.
I searched for it but can't find any help. I just suspend it for help my dear CPU.
OS : windows 7 Professional
Arch. : x64
create a zip code, name it webproxy.exe, replace it with the real webproxy.exe file in C:/windows/syswow64 folder or where ever that is, in the safe mode.
I faced the same problem since I installed the "Web Freer".
It also copied the "webproxy.exe" file in the "C:\Windows\SysWOW64" location and even when I uninstalled the program, it ran it from there, so you may need to delete it by yourself from there too. It may help preventing the same problem again.
I've recently started seeing this line in my Visual Studio 2005 output window when launching my application:
FTH: (7156): *** Fault tolerant heap shim applied to current process. This is usually due to previous crashes. ***
I've tried turning off the fault tolerant heap using the instructions here:
http://msdn.microsoft.com/en-us/library/dd744764(VS.85).aspx
I'm running Windows 7 64-bit edition, so I have made the changes to both the 32-bit and 64-bit registries, and run the "Rundll32.exe fthsvc.dll,FthSysprepSpecialize" command using both the 32-bit and 64-bit versions of Rundll32.exe.
However, after rebooting I am still getting the fault tolerant heap when trying to debug my application!
This is a real problem since it masks the bug I am trying to reproduce, and it also kills performance.
Does anyone have any other suggestions how to disable the fault tolerant heap?
To disable it for a single application
Go to the HKEY_LOCAL_MACHINE and HKEY_CURRENT_USER versions of
Software\Microsoft\Windows
NT\CurrentVersion\AppCompatFlags\Layers\your_application.exe and
delete the FaultTolerantHeap entry.
From here (actually here)
Set this registry value to 0:
HKEY_LOCAL_MACHINE\Software\Microsoft\FTH\Enabled
You can add the name of your executable to the ExclusionList.
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\FTH\ExclusionList
Works for me.
You can edit the application manifest to excluding your program from PCA
see also:How to reset Program Compatibility Assistant for testing
you can clear the list of applications tracked by FTH without stopping this service by following these steps:
Click the Start menu.
Right-click Computer and click Manage.
Click Event Viewer -> Applications and Services Logs -> Microsoft ->
Windows -> Fault-Tolerant-Heap.
View FTH Events.
you will find file named operational by right click and choose clear log,
then you can run you program again and warning message will disappear,
it worked with me without restarting operating system.
On Windows 10 the registry location is:
Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\FTH
You can remove you executable from the list in:
Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\FTH\State
or you can run this command from an elevated command prompt
Rundll32.exe fthsvc.dll,FthSysprepSpecialize
You may need to reboot your machine
"Rundll32.exe fthsvc.dll,FthSysprepSpecialize" looks to only clear the list of currently flagged applications. if your application still causes oddities, the FTH should still step in and take over.
as already mentioned:
Set this registry value to 0: HKEY_LOCAL_MACHINE\Software\Microsoft\FTH\Enabled
this should disable FTH for the whole system.
I had to rename the file as well because the registry entries associated with this key were empty of applicable data. I expect that they populate if you have a misbehaving application. But in my case I was debugging my own application within Visual Studio. So in that case, it was my process that was somehow loading the FTH whether the FTH Service was running or not. And in fact I had no applications listed that were previously tagged as misbehaving.
But I had to follow these instructions:
http://billroper.livejournal.com/960825.html
because it wouldn't let me rename the file until I took ownership and made sure I had full control.
I had similar issue when running a Unit test using (Microsoft::VisualStudio::CppUnitTestFramework).
Somehow I had violated some heap allocation, and next time I tried to debug I received the message : "Fault tolerant heap shim applied to current process. This is usually due to previous crashes. " and the debug environment froze.
To get it to work again, I had to remove test case, recompile and add it again and recompile, then I could set breakpoint and step into the test.
Also ran into this. Renaming/deleting AcXtrnal.dll inside Windows\AppPatch seems to work for me. I like how this Microsoft recommended action (which I did first) does nothing.
I'm debugging plugins on Windows 7 and of course the plugin host (Cubase5.exe) occasionally crashes because of errors in the plugin. On XP or Vista, I could always restart it immediately and continue working. But on Windows 7, even though Cubase appears to close, it is still visible in Task Manager and I cannot kill it by any means. After a minute or two, it disappears by itself. In the mean time, I can't work because the plugin DLL is still locked by the process.
Does anyone know why this happens on Windows 7? I've already tried disabling Automatic Error Reporting but that didn't help. I've tried attaching cdb to Cubase, but I get:
Cannot debug pid 5252, NTSTATUS 0xC0000001
"{Operation Failed} The requested operation was unsuccessful."
Debuggee initialization failed, NTSTATUS 0xC0000001
"{Operation Failed} The requested operation was unsuccessful."
I tried following the instructions here but it appears this is only possible if I connect a second machine to my computer to debug it remotely.
I finally found the solution, using this article:
http://blogs.technet.com/b/markrussinovich/archive/2005/08/17/unkillable-processes.aspx
This required installing the Windows Debugging Tools for Windows (nice name) and LiveKd, but by following the steps outlined I was able to track which driver was causing the process to hang: it turned out to be the 64-bit driver for the M-Audio Oxygen 8 V2 controller I'm using. Unfortunately no driver update is available.
Anyway, if anyone encounters a similar problem, this is the way to solve it.
Have you tried Process Explorer by Mark Russinovich? It is really useful for "killing":)
If you have error reporting enabled, it's possible that werfault.exe has Cubase open to write a minidump for crash reporting purposes.
This is just a stab in the dark but it might be your problem.
One thing you can try is to check with Process Monitor what Cubase is doing. Set a filter so that everything with a process name containing "cubase" will be recorded. It could be that you are facing some timeout issue when Cubase wants to exit.
you can end the process the service is running under. You can find this process by going to the Services tab of the Task Manager, right-clicking, and selecting Go To Process(you need to click the Show processes from all users button.). Note that one process may host multiple services (especially if it's svchost.exe), and ending the process will kill all those services. Also, this is an unclean exit, and may cause data corruption depending on what the service(s) was doing when you killed it.
Depending on which specific service you are trying to stop, there may be a cleaner way to simulate failure.